|
|
|
|
|
Both the script and TSM collect call data during a transaction. The script can store application data in event memory and save any application-related data. The data might be response time, user ID, request types, number of invalid selections, and an event counter. TSM collects generic data such as the script name, channel number, start time, and stop time and stores it in a call data record.
At the end of a call, TSM copies the generic data it collected and the contents of event memory into a call data record and sends it to the call data handler (ORACDH/FILECDH) process. Call data is stored in ORACLE tables or ASCII files, depending on the system setting. If the ORACLE Integration (oraint) package is installed, the call data can be stored in the ORACLE database. If the ORACLE Integration (oraint) package is not installed, the call data is stored in the /oracle/add-on/calldata directory by default.
The reports generated are available to the system operator only if the ORACLE Integration package is installed and ORACLE is chosen as the storage location. If the ORACLE Integration package is installed, the call data is stored in the ORACLE database. If ORACLE is not installed, call data is stored in files as the default.
The .D file
The .D file provides descriptive labels for events when the events are displayed. The event counter array space may contain event counter integers, strings, or both. Records beginning with an integer between 0 and 99 are interpreted as valid event specification records. You do not have to use a 0 or 1 as the first event counter.
The following is an example of the .D file syntax, where WS refers to a tab or blank space and STR refers to the literal string STR:
event_number [WS STR] [WS label_string]
The following is an example of the .D file syntax, where event memory 1 stores string data and displays it under the label User Name:
1 STR User Name
A sufficient amount of event memory space for storage of the strings should be allocated. This includes 1 byte for the null character at the end. In addition, the contents of one event counter should not overlap the contents of another event counter. You should also make sure the script copies the string starting at the event counter specified in the .D file.
Event data is reported only if it is specified in the service script and the file /voice1/calldata/script_name.D exists in the proper format. Place all .D files in the /voice1/calldata directory. It is important to place strings in the call event space properly. You must know the length of the string and map it correctly onto the 4-bit events of the event space. Use the command /voice1/bin/cddrpt to view script events.
