This chapter includes information about CallCoordinator- supplied batch processes. These processes produce batch listings from data collected on the CallCoordinator MIS Log. This data is collected on the Log by CallCoordinator processes and your business application programs using the Write MIS Log API ("Write MIS Record API (CAMI700C)"). This chapter has the following sections:
This describes the general organization of the CallCoordinator MIS Log and the batch processes that use it to produce CallCoordinator-supplied listings.
This is a CallCoordinator-supplied job stream used to extract processed records from the CallCoordinator MIS Log user journal and create the Processed Event file. This file is used in the following job streams to produce the other files and listings.
This program extracts error records from the Processed Event File and prints the Error listing.
This job stream extracts records from the processed Event file and prints the Multiple Party Event listing.
This job stream creates a file of Individual Party Event Records and prints the Individual Party Event listing.
This job stream creates the Call Analysis (Totals) file and prints the Totals listing.
If you customize the MIS log by adding your own business records to the MIS Log (see "Write MIS Record API (CAMI700C)"), or by customizing the CallCoordinator MIS Interface Module (see "MIS Log Exit"), you cannot use the programs in the above job streams. In this case, you will need to customize the programs or write your own.
The MIS Log is defined as a product-sensitive programming interface. See "Programming Interfaces" for a definition of a product-sensitive programming interface.
+-------------Product-sensitive programming interface information--------------+
The CallCoordinator Call Tracking Manager writes event records created from the messages it receives (from CallPath/CICS and other CallCoordinator modules) to the MIS Log, together with error records that detail problems encountered in message processing. The Write MIS Log API allows your application programs to add records to the log.
The records are designed to be used by batch programs for batch reports. A CallCoordinator-supplied batch program extracts a data file for the preparation of off-line batch listings (see "Extract Processed Event File Job Stream (CAMJEXTR)"). During the batch extract, information in different record types is aligned in fixed positions to make it easy to use standard sorts and report-writing tools. Some of the CallCoordinator-supplied listings can be used to help manage the operation of the call center; others help with problem determination.
CallCoordinator provides a number of batch programs that extract data into files for report generation and print an error listing. These can be used as illustrations of the use of the MIS Log.
This section describes CallCoordinator indices, the general organization of the MIS Log, the formats of the MIS records, and the functions of the batch jobs and programs.
At any one moment, hundreds of calls may be active in a large call center. Records are written to the MIS Log as event messages indicate parties going off- or on-hook, transferring, entering queues, and so on. Therefore, the messages for the active calls will be interleaved.
To be able to correlate the records for calls, and parties in calls, CallCoordinator creates a number of call indices. Sort utility programs can use the indices to collect all the records for a call, or all the records for a party in a call. For more information about these indices, see "About Call Indices".
The formats of the various records in the MIS Log have been designed to make it easy to use standard utilities to sort and extract data records. Each record type has a consistent format, and uses only character data. All record types have the same length - 460 bytes. The length of the MIS record could be reduced by changing the design to use packed or binary fields for numeric data. However, records with fixed-position character fields (sometimes called "flat files") are more easily converted into report-writer files, or be down-loaded to personal computers for processing by spreadsheet programs.
Each record type has a six-character header. The first four characters indicate the source of the record. Records created by CallCoordinator contain "Cxxx" as the source code, where xxx represents three letters or numbers assigned by CallCoordinator processes. Records written by your application programs must have a source code that begins with a letter other than "C". The fifth character indicates the record type; all records of the same type have the same format. The sixth character is a version flag if a future release adds data to a record. This ensures that processing programs will be able to distinguish the old data from the new data.
The records written by CallCoordinator contain the following record types:
All the above record types, except for the status change, can result from the processing of event messages. To make matching and sorting easier, all record types for calls and message processing have been assigned a common section. (Error records that originate outside of event message processing use blanks for the message and call data fields). The common section includes:
All record types follow the common section with a message-related section that contains:
The messages from CallCoordinator all have "P", "R", or "S" as the first character of the message type, and two digits that identify the actual CallCoordinator message.
The message types are defined in the following tables:
The processed event record contains data from messages that were processed normally by the CallCoordinator Call Tracking Manager. The record format for this event record is shown in Table 36. After the common and message-related sections, the record has a section with attributes of the call, followed by data for up to three parties. The data for the calling party is followed by the data for the called party. The third position is used for an additional party that was involved with the telephony action. If there are more than three parties (perhaps because a conference call ended), the additional parties are written in continuation records which repeat the call-related data.
The Party Structure contains the most significant data about one of the parties to a call. Some of the fields will be blank or zero, if the information is not known. For example, an Inactive agent will not have a Class, Function, or ID, and if the data is for a party whose call cannot be found, the Party Index will be blank.
The record format for this event record is shown in Table 36.
This layout is provided
in the CallCoordinator SEZPCOPY target library, member name
CAMR002.
Refer to the library member for the actual field names.
Table 36. Processed Event Record Format (CAMR002)
| Field | Bytes | Type | Comments |
|---|---|---|---|
| RECORD HEADER | |||
| RECORD CREATED BY | 4 | Alpha | Cxxx |
| RECORD TYPE | 1 | Alpha | P |
| VERSION | 1 | Alpha | Blank |
| COMMON DATA | |||
| DATE FROM HOST | 8 | Numeric | YYYYMMDD |
| TIME FROM HOST | 9 | Numeric | HHMMSSNNN |
| SEQUENCE NUMBER | 2 | Numeric | Assigned by the CallCoordinator Call Tracking Manager |
| RECORD COUNTER | 3 | Numeric | |
| UNIT OF WORK APPLICATION ID | 8 | Alpha | |
| UNIT OF WORK INDEX | 12 | Alpha | |
| CALL APPLICATION ID | 8 | Alpha | |
| CALL INDEX | 12 | Alpha | |
| APPLICATION CONNECT INDEX | 9 | Numeric | |
| MESSAGE-RELATED DATA | |||
| DATE FROM SUBSYSTEM | 8 | Numeric | YYYYMMDD |
| TIME FROM SUBSYSTEM | 9 | Numeric | HHMMSSNNN |
| MESSAGE TYPE | 3 | Alpha |
|
| SWITCH ID | 8 | Alpha | |
| CALL-RELATED DATA | |||
| CALL SOURCE | 1 | Alpha |
|
| CALL PARENTAGE | 1 | Alpha |
|
| CALL STATE | 1 | Alpha |
|
| END CODE | 1 | Alpha |
|
| CALL PURPOSE | 1 | Alpha |
|
| PARTY MIX INDEX | 3 | Numeric | Increments when parties are added or dropped. |
| CONTROL NUMBER | 30 | Alpha | |
| BUSINESS VALUE | 12 | Numeric | |
| BUSINESS VALUE SIGN | 1 | Alpha | + or -
|
| ORIGINAL GROUP (pilot) | 10 | Alpha | |
| DNIS | 32 | Alpha | |
| TRANSACTION ID | 8 | Alpha | |
| USER MODE TRANSACTION ID | 8 | Alpha | |
| AGENT FUNCTION | 10 | Alpha | |
| AGENT ID | 10 | Alpha | |
| CLIENT NUMBER SOURCE | 2 | Alpha |
|
| CLIENT NUMBER | 32 | Alpha |
|
| SPM-DISABLE-XFER-FLAG | 01 | Alpha | Disable transfer flag (Y/N) |
| PREV-CALL-STATE | 01 | Alpha | Previous Call State:
|
| FILLER | 02 | Alpha | Spaces. Reserved for future use. |
| PARTY COUNT | 2 | Numeric | More than 2 for conference calls. |
| PARTY DATA | |||
| PARTY 1 - SWITCH ID | 8 | Alpha | Party data contains data about one of the call parties. Some fields will be blank or zero if the information is not known. For example, inactive agents have no class, function, or ID. If the data is for a party whose call cannot be found, the party index will be blank. Party 1 is the calling party. |
| PARTY 1 - PARTY NUMBER TYPE | 1 | Alpha |
|
| PARTY 1 - PARTY NUMBER | 10 | Alpha | |
| PARTY 1 - PARTY INDEX | 10 | Alpha | |
| PARTY 1 - AGENT CLASS | 1 | Alpha | User-defined value. |
| PARTY 1 - AGENT FUNCTION | 10 | Alpha | |
| PARTY 1 - AGENT ID | 10 | Alpha | |
| PARTY 1 - AGENT STATUS | 1 | Alpha |
|
| PARTY 1 - ROLE | 1 | Alpha |
|
| PARTY 1 - SERVER | 1 | Alpha |
|
| PARTY 1 - CONNECTION STATE | 1 | Alpha |
|
| FILLER | 8 | Alpha | Spaces. Reserved for future use. |
| PARTY 2 - SAME FIELDS AS PARTY 1 | 62 | Party structure | Party 2 is the called party. See above. |
| PARTY 3 - SAME FIELDS AS PARTY 1 | 62 | Party structure | Party 3 is any other party in the call. See above. |
The processed event continuation record is written after a
processed event record. It contains the data for additional
parties that changed state as a result of the event message.
The first continuation record contains the data for
the 4th, 5th, and 6th parties; the second contains data
for 7th, 8th, and 9th, and so on.
The record format for this event record is shown in Table 37.
Table 37. Processed Event Continuation Record Format (CAMR002)
| Field | Bytes | Type | Comments |
|---|---|---|---|
| RECORD HEADER | |||
| RECORD CREATED BY | 4 | Alpha | Cxxx |
| RECORD TYPE | 1 | Alpha | Q |
| VERSION | 1 | Alpha | |
| COMMON DATA | |||
| DATE FROM HOST | 8 | Numeric | YYYYMMDD |
| TIME FROM HOST | 9 | Numeric | HHMMSSNNN |
| SEQUENCE NUMBER | 2 | Numeric | Assigned by the CallCoordinator Call Tracking Manager |
| RECORD COUNTER | 3 | Numeric | |
| UNIT OF WORK APPLICATION ID | 8 | Alpha | |
| UNIT OF WORK INDEX | 12 | Alpha | |
| CALL APPLICATION ID | 8 | Alpha | |
| CALL INDEX | 12 | Alpha | |
| APPLICATION CONNECT INDEX | 9 | Numeric | |
| MESSAGE-RELATED DATA | |||
| DATE FROM SUBSYSTEM | 8 | Numeric | YYYYMMDD |
| TIME FROM SUBSYSTEM | 9 | Numeric | HHMMSSNNN |
| MESSAGE TYPE | 3 | Alpha |
|
| SWITCH ID | 8 | Alpha | |
| CALL-RELATED DATA | |||
| CALL SOURCE | 1 | Alpha |
|
| CALL PARENTAGE | 1 | Alpha |
|
| CALL STATE | 1 | Alpha |
|
| END CODE | 1 | Alpha |
|
| CALL PURPOSE | 1 | Alpha |
|
| PARTY MIX INDEX | 3 | Numeric | Increments when parties are added or dropped. |
| CONTROL NUMBER | 30 | Alpha | |
| BUSINESS VALUE | 12 | Numeric | |
| BUSINESS VALUE SIGN | 1 | Alpha | + or -
|
| ORIGINAL GROUP (pilot) | 10 | Alpha | |
| DNIS | 32 | Alpha | |
| TRANSACTION ID | 8 | Alpha | |
| USER MODE TRANSACTION ID | 8 | Alpha | |
| AGENT FUNCTION | 10 | Alpha | |
| AGENT ID | 10 | Alpha | |
| CLIENT NUMBER SOURCE | 2 | Alpha |
|
| CLIENT NUMBER | 32 | Alpha | |
| FILLER | 04 | Alpha | Spaces. Reserved for future use. |
| PARTY COUNT | 2 | Numeric | More than 2 for conference calls. |
| PARTY DATA | |||
| PARTY 4, 7, (Switch ID) | 8 | Alpha | Party Data contains data about one of the call parties. Some fields will be blank or zero if the information is not known. For example, inactive agents have no class, function, or ID. If the data is for a party whose call cannot be found, the party index will be blank. |
| PARTY 4, 7, (Party number type) | 1 | Alpha |
|
| PARTY 4, 7, (party number) | 10 | Alpha | |
| PARTY 4, 7, (party index) | 10 | Alpha | |
| PARTY 4, 7, (agent class) | 1 | Alpha | User-defined value. |
| PARTY 4, 7, (agent function) | 10 | Alpha | |
| PARTY 4, 7, (agent ID) | 10 | Alpha | |
| PARTY 4, 7, (agent status) | 1 | Alpha |
|
| PARTY 4, 7, (role) | 1 | Alpha |
|
| PARTY 4, 7, (server) | 1 | Alpha |
|
| PARTY 4, 7 (connection state) | 1 | Alpha |
|
| FILLER | 8 | Alpha | Spaces. Reserved for future use. |
| PARTY 5, 8 (same fields as party 4, 7) | 62 | Party structure | See above. |
| PARTY 6, 9, (same fields as party 4, 7) | 62 | Party structure | See above. |
A Non-Processed event record results when a message did not
contain enough information for the CallCoordinator Call Tracking Manager
to process, or referenced
one or more calls that were not in the current Call Management Control Table(CMCT).
If a Disconnected message is processed for a call that is not
current, the party data is written in Non-Processed records, but
no error message is written. Other Non-Processed records are
accompanied by Error records, giving the reason(s) for the
processing failure.
The record format for this event record is shown in Table 38.
Table 38. Non-processed Event Record Format (CAMR002)
| Field | Size | Type | Comments |
|---|---|---|---|
| RECORD HEADER | |||
| RECORD CREATED BY | 4 | Alpha | Cxxx |
| RECORD TYPE | 1 | Alpha | N |
| VERSION | 1 | Alpha | |
| COMMON DATA | |||
| DATE FROM HOST | 8 | Numeric | YYYYMMDD |
| TIME FROM HOST | 9 | Numeric | HHMMSSNNN |
| SEQUENCE NUMBER | 2 | Numeric | Assigned by the CallCoordinator Call Tracking Manager |
| RECORD COUNTER | 3 | Numeric |
|
| UNIT OF WORK APPLICATION ID | 8 | Alpha | |
| UNIT OF WORK INDEX | 12 | Alpha | |
| CALL APPLICATION ID | 8 | Alpha | |
| CALL INDEX | 12 | Alpha | |
| APPLICATION CONNECT INDEX | 9 | Numeric | |
| MESSAGE-RELATED DATA | |||
| DATE FROM SUBSYSTEM | 8 | Numeric | YYYYMMDD |
| TIME FROM SUBSYSTEM | 9 | Numeric | HHMMSSNNN |
| MESSAGE TYPE | 3 | Alpha |
|
| SWITCH ID | 8 | Alpha | |
| NON-PROCESSED MESSAGE DATA | |||
| EVENT MESSAGE TOTAL TEXT LENGTH | 4 | Numeric | Total length of the message. Might be greater than the space provided in this record. |
| MESSAGE TEXT LENGTH | 3 | Numeric | Length of the message data in this record. |
| MESSAGE CONTINUATION FIELD | 1 | Alpha |
|
| EVENT MESSAGE TEXT | 347 | Alpha | Up to 347 characters of the message text.
If more than this, another record follows. |
The Call-Combining record is written when telephony action
results in adding parties from an original Unit of Work into
another Unit of
Work. The record allows one of the batch programs to replace the
Unit of Work fields in the added call, so that the records
will sort together in a subsequent processing step. The Date and
Time from Host computer are set to zero, so that the combine record will
be found before any other records for the Unit of Work that is to
be changed.
The record format for this event record is shown in Table 39.
Table 39. Call-Combining Record Format (CAMR002)
| Field | Bytes | Type | Comments |
|---|---|---|---|
| RECORD HEADER | |||
| RECORD CREATED BY | 4 | Alpha | Cxxx |
| RECORD TYPE | 1 | Alpha | C |
| VERSION | 1 | Alpha | Blank |
| COMMON DATA | |||
| DATE FROM HOST | 8 | Numeric | Zeros |
| TIME FROM HOST | 9 | Numeric | Zeros |
| SEQUENCE NUMBER | 2 | Numeric | Assigned by the CallCoordinator Call Tracking Manager |
| RECORD COUNTER | 3 | Numeric | |
| UNIT OF WORK APPLICATION ID | 8 | Alpha | |
| UNIT OF WORK INDEX | 12 | Alpha | |
| CALL APPLICATION ID | 8 | Alpha | |
| CALL INDEX | 12 | Alpha | |
| APPLICATION CONNECT INDEX | 9 | Numeric | |
| NEW UNIT OF WORK | |||
| CHANGE TO UNIT OF WORK APPLICATION ID | 8 | Alpha | |
| CHANGE TO UNIT OF WORK INDEX | 12 | Alpha | |
| FILLER | 363 | Alpha | Spaces. Reserved for future use. |
An Error record is written to the MIS Log to indicate problems
that result from processing event data. The Error
records are written near the messages that caused them, and can
be sorted to stay with call-related records,
to make problem determination easier.
The record format for this event record is shown in Table 40.
Table 40. Error Record Format (CAMR002)
| Field | Bytes | Type | Comments |
|---|---|---|---|
| RECORD HEADER | |||
| RECORD CREATED BY | 4 | Alpha | Cxxx |
| RECORD TYPE | 1 | Alpha | E |
| VERSION | 1 | Alpha | Blank |
| COMMON DATA | |||
| DATE FROM HOST | 8 | Numeric | YYYYMMDD |
| TIME FROM HOST | 9 | Numeric | HHMMSSNNN |
| SEQUENCE NUMBER | 2 | Numeric | Assigned by the CallCoordinator Call Tracking Manager |
| RECORD COUNTER | 3 | Numeric | |
| UNIT OF WORK APPLICATION ID | 8 | Alpha | |
| UNIT OF WORK INDEX | 12 | Alpha | |
| CALL APPLICATION ID | 8 | Alpha | |
| CALL INDEX | 12 | Alpha | |
| APPLICATION CONNECT INDEX | 9 | Numeric | |
| MESSAGE-RELATED DATA | |||
| DATE FROM SUBSYSTEM | 8 | Numeric | YYYYMMDD |
| TIME FROM SUBSYSTEM | 9 | Numeric | HHMMSSNNN |
| MESSAGE TYPE | 3 | Alpha |
|
| SWITCH ID | 8 | Alpha | |
| ERROR-RELATED DATA | |||
| TEXT LENGTH | 3 | Numeric | |
| MESSAGE TEXT | 120 | Alpha |
|
| FILLER | 232 | Alpha | Spaces. Reserved for future use. |
The Status Change record reflects a notification from CallPath/CICS that
the status of a switch link, or the CallPath/CICS Subsystem has changed.
The record format for this event record is shown in Table 41.
Table 41. Status Change Record Format (CAMR002)
| Field | Bytes | Type | Comments |
|---|---|---|---|
| RECORD HEADER | |||
| RECORD CREATED BY | 4 | Alpha | Cxxx |
| RECORD TYPE | 1 | Alpha | S |
| VERSION | 1 | Alpha | |
| STATUS DATA | |||
| DATE FROM HOST | 8 | Numeric | YYYYMMDD |
| TIME FROM HOST | 9 | Numeric | HHMMSSNNN |
| SEQUENCE NUMBER | 2 | Numeric | Assigned by the CallCoordinator Call Tracking Manager |
| RECORD COUNTER | 3 | Numeric | |
| DATE FROM SUBSYSTEM | 8 | Numeric | YYYYMMDD
|
| TIME FROM SUBSYSTEM | 9 | Numeric | HHMMSSNNN
|
| STATUS CHANGED | 1 | Alpha |
|
| SWITCH ID | 8 | Alpha | Blank if not from switch. |
| CHANGE | 1 | Alpha |
|
| SEVERITY | 1 | Alpha | 0 through 9 |
| FILLER | 404 | Alpha | Spaces. Reserved for future use. |
The account code record is written when CallCoordinator receives a Feature Invoked message that records data entered by an agent through his telephone. If the agent is involved with a call at the time of the data entry, the call-related sections of the MIS record will reference the most recent call If the agent is not involved with a call the alphabetic fields will be set to spaces, and the numeric fields to zeros in the call-related data. Similarly, in the Common Data, the following fields are set to spaces:
Table 42. Account Code Record Format (CAMR002)
| Field | Size | Type | Comments |
|---|---|---|---|
| RECORD HEADER | |||
| RECORD CREATED BY | 4 | Alpha | Cxxx |
| RECORD TYPE | 1 | Alpha | A |
| VERSION | 1 | Alpha | Blank |
| COMMON DATA | |||
| DATE FROM HOST | 8 | Numeric | YYYYMMDD |
| TIME FROM HOST | 9 | Numeric | HHMMSSNNN |
| SEQUENCE NUMBER | 2 | Numeric | Assigned by the CallCoordinator Call Tracking Manager |
| RECORD COUNTER | 3 | Numeric |
|
| UNIT OF WORK APPLICATION ID | 8 | Alpha | |
| UNIT OF WORK INDEX | 12 | Alpha | |
| CALL APPLICATION ID | 8 | Alpha | |
| CALL INDEX | 12 | Alpha | |
| APPLICATION CONNECT INDEX | 9 | Numeric | |
| MESSAGE-RELATED DATA | |||
| DATE FROM SUBSYSTEM | 8 | Numeric | YYYYMMDD |
| TIME FROM SUBSYSTEM | 9 | Numeric | HHMMSSNNN |
| MESSAGE TYPE | 3 | Alpha | 'C07' |
| SWITCH ID | 8 | Alpha | |
| CALL-RELATED DATA | |||
| CALL SOURCE | 1 | Alpha |
|
| CALL PARENTAGE | 1 | Alpha |
|
| CALL STATE | 1 | Alpha |
|
| END CODE | 1 | Alpha |
|
| CALL PURPOSE | 1 | Alpha |
|
| PARTY MIX INDEX | 3 | Numeric | Increments when parties are added or dropped. |
| CONTROL NUMBER | 30 | Alpha | |
| BUSINESS VALUE | 12 | Numeric | |
| BUSINESS VALUE SIGN | 1 | Alpha | |
| ORIGINAL GROUP (pilot) | 10 | Alpha | |
| DNIS | 32 | Alpha | |
| TRANSACTION ID | 8 | Alpha | |
| USER MODE TRANSACTION ID | 8 | Alpha | |
| AGENT FUNCTION | 10 | Alpha | |
| AGENT ID | 10 | Alpha | |
| CLIENT NUMBER SOURCE | 2 | Alpha |
|
| CLIENT NUMBER | 32 | Alpha | |
| FILLER | 04 | Alpha | Spaces. Reserved for future use. |
| PARTY COUNT | 2 | Numeric | |
| ACCOUNT CODE DATA | |||
| SWITCH ID | 8 | Alpha | Switch ID of the agent who entered the data. |
| PARTY NUMBER TYPE | 1 | Alpha | For the agent who entered the data.
|
| PARTY NUMBER | 10 | Alpha | For the agent who entered the data. |
| PARTY INDEX | 10 | Alpha | For the agent who entered the data. |
| AGENT CLASS | 1 | Alpha | User-defined value. |
| AGENT FUNCTION | 10 | Alpha | For the agent who entered the data. |
| AGENT ID | 10 | Alpha | For the agent who entered the data. |
| AGENT STATUS | 1 | Alpha | For the agent who entered the data.
|
| ROLE | 1 | Alpha | For the agent who entered the data.
|
| SERVER | 1 | Alpha | For the agent who entered the data.
|
| CONNECTION STATE | 1 | Alpha | For the agent who entered the data.
|
| FILLER | 8 | Alpha | Spaces. Reserved for future use. |
| ACCOUNT CODE | 32 | Alpha | The data entered. |
| FILLER | 92 | Alpha | Spaces. Reserved for future use. |
This job stream extracts event records from the CallCoordinator MIS Log user journal and creates the Processed Event file. This file is used by subsequent job streams to produce other files and listings.
This program extracts error records from the Processed Event file and prints the Event Message Error Listing.
This job stream extracts records from the Processed Event file and prints the Multiple Party Event listing.
This job stream extracts records from the Processed Event file, creates a file of Individual Party Event Records and prints the Individual Party Event listing.
This job stream extracts records from the Processed Event file, creates the Call Analysis (totals) file, and prints the Totals listing.
The file is an 80-character fixed-length file. The first record defines the format for date and time. The following nine records provide the text for the heading lines. The format of record 1 is:
The codes are:
0 = 24, not 0 = 12
Note: The fields are not edited. If you specify the month in all 3 date fields, that is what will print. If the code is not 1-4, XX will print.
The heading record usage is:
This job stream extracts event records from the MIS Log and creates the Processed Event file. The records in this file are in the same formats as the MIS Log event records (see "MIS Log Exit" for a description of standard MIS log formats). This file is used by the following CallCoordinator-supplied batch listings job streams:
Use this job stream whenever you require up-to-date batch listings.
Run this job stream after running the extract program, CAMM490B.
Before running this job stream, modify the appropriate parameters in the JCL for the desired heading date and time (see "Selecting Your Own Listing Heading and Date/Time Formats").
The JCL for this job stream is provided in the CallCoordinator target library SEZPSAMP.
This job stream requires that the records in the MIS log are in standard MIS log format. See "MIS Log Exit" for a description of standard MIS log format. You must customize this job stream or write your own job stream if the records in the MIS log are not in standard MIS log format.
The program extracts MIS records from a CICS user journal into a sequential file with a record length of 460 bytes. This file is used as input to the CAMJEXTR job stream.
The program can be run either during auto-archiving of the user journal or at the start of CAMJEXTR. It ensures that the records are in standard MIS log format.
This program is CallCoordinator-supplied batch program. You can use it to extract call records from the MIS Log. It extracts the records based on CallCoordinator criteria. It processes the Unit of Work Index in each record and makes corrections for combined calls. It changes the Unit of Work Index of the added call to that of the original call. It extracts event records from the MIS Log and generates a Processed Event file that has processed the Unit of Work Index corrections.
This program requires that the records in the MIS log are in standard MIS log format. See "MIS Log Exit" for a description of standard MIS log format. You must customize this program or write your own program if the records in the MIS log are not in standard MIS log format. You write your own MIS log records to the MIS Log user journal, or if you want the extraction of records to be based on non-CallCoordinator criteria.
This program formats a listing while extracting the event records to produce the Processed Event file.
If you have customized the MIS Log, you might also need to customize this program or write your own program.
Figure 10 shows the layout of the listing.
Figure 10. CAMM415 CallPath CallCoordinator Extract Event Listing
This job stream extracts error records from the Processed Event file and prints the Event Message Error listing. The records in the Processed Event file are in the same formats as the MIS Log event records (see "MIS Log Exit" for a description of standard MIS log formats).
Use this job stream whenever you require an up-to-date listing of error records from the MIS Log in order to analyze errors occurring with CallCoordinator events.
Run this job stream after running the extract program, CAMMEXTR.
Before running this job stream, modify the appropriate parameters in the JCL for the desired heading date and time (see "Selecting Your Own Listing Heading and Date/Time Formats").
The JCL for this job stream is provided in the CallCoordinator target library SEZPSAMP.
This job stream requires that the records in the MIS log are in standard MIS log format. See "MIS Log Exit" for a description of standard MIS log format. You must customize this job stream or write your own job stream if the records in the MIS log are not in standard MIS log format.
This program extracts error records from the Processed Event file to be printed in the Error Listing. The Event Message Error records are the processed Event Message records from the MIS Log which have been flagged with an error code.
If you have customized the MIS Log, you might also need to customize this program or write your own program.
This program uses the records extracted by CAMM420B and generates a listing of MIS Log error message records.
If you have customized the MIS Log, you might also need to customize this program or write your own program.
Figure 11 shows the format of the Event Message Error Listing. Party numbers are shown as a 1-character type, followed by the 8-character local number.
Figure 11. CAMM425 CallPath CallCoordinator Event Message Error Listing
The date and time in the heading of the listing is the run time of the print program. In the body of the listing, the date and time are the host computer date and time from the message. The message date is printed for as the first body line of each page, and when the date changes. The '--' in the date and time fields do not print. They indicate that some formatting options take two more print positions.
This job stream extracts error records from the Processed Event file and prints the Multiple Party Event listing. The records in the Processed Event file are in the same formats as the MIS Log event records (see "MIS Log Exit" for a description of standard MIS log formats).
Use this job stream whenever you require an up-to-date listing of multiple party event records from the MIS Log in order to analyze calling parties.
Run this job stream after running the extract program, CAMMEXTR.
Before running this job stream, modify the appropriate parameters in the JCL for the desired heading date and time (see "Selecting Your Own Listing Heading and Date/Time Formats").
The JCL for this job stream is provided in the CallCoordinator target library SEZPSAMP.
This job stream requires that the records in the MIS log are in standard MIS log format. See "MIS Log Exit" for a description of standard MIS log format. You must customize this job stream or write your own job stream if the records in the MIS log are not in standard MIS log format.
This extract program extracts multiple party call event records from the Processed Event File. These records are then used to print the Multiple Party Event listing.
If you have customized the Multiple Party Event Message file in any way, you must also customize this program or write your own program.
If you have customized the Multiple Party Event Message file in any way, you must also customize this program or write your own program.
Figure 12 shows the format of the listing. Party numbers are shown as a 1-character type, followed by the 8-character local number.
Figure 12. CAMM435 CallPath Multiple Party Event Listing
This job stream extracts Individual Party Event records from the Processed Event file and prints the Individual Party Event listing. The records in the Processed Event file are in the same formats as the MIS Log event records (see "MIS Log Exit" for a description of standard MIS log formats).
Use this job stream whenever you require an up-to-date listing of individual party event records from the MIS Log in order to analyze call events.
Run this job stream after running the extract program, CAMMEXTR.
Before running this job stream, modify the appropriate parameters in the JCL for the desired heading date and time (see "Selecting Your Own Listing Heading and Date/Time Formats").
The JCL for this job stream is provided in the CallCoordinator target library SEZPSAMP.
This job stream requires that the records in the MIS log are in standard MIS log format. See "MIS Log Exit" for a description of standard MIS log format. You must customize this job stream or write your own job stream if the records in the MIS log are not in standard MIS log format.
The Individual Party Event File contains a record for each party that is in a Processed Event record in the MIS Log. It can be sorted to follow the actions of a party within a call, or the actions of an agent within a day.
The following table shows the layout of fields in the Individual-Party Event Message File. The Party-Position in the original record is 1, 2, or 3, to show the location of the party in the MIS record. The remaining fields are the same as those defined in the MIS Log user journal.
The Individual Party Event Records file contains records for each individual party in a call. See Table 43 for the record layout of this file. Except for the field called "Party position in original record", the layout of records in this file is the same as those defined in the MIS Log.
This layout is provided
in the CallCoordinator SEZPCOPY target library, member name
CAMMIND1.
Refer to the library member for the actual field names.
Table 43. Individual Party Event Record Format (CAMMIND1)