Script development

The following information details defining header files and user memory, identifying events, and specifying source files.

Transaction control header files

Many parameters used in a script are defined in header files. The first two are defined already. The third and fourth files are defined by the application developer. The user directories and application names shown are only examples.

1. Defines generic messages to the DIP and their format:

   /att/msgipc/tsm_dip.h

2. Defines speech codestyle messages to TSM:

   /att/include/codestyle.h

3. Defines script variables and allocates user memory:

   /usr/var/appl N /trans/ application_name def.h
   or
   /att/trans/sb/ application_name/application_name def.h

4. Defines the application messages to the DIP and their format :

   /usr/var/appl N /dip N /tsmdipappl.h
   or
   /att/trans/sb/ application_name/application_name def.h

Defining user memory

User memory is defined by the mkheader command. The mkheader command allocates space for local, global, and database variables used by the script. The program is initiated by entering:

mkheader application_name

This command creates a header file called application_name def.h.

Identification of events

Once the information that is to be recorded during a transaction has been determined, then a number is assigned to each noteworthy event and a label is entered for that event.

When an event occurs during a transaction, the script can increment the event or load the appropriate value into it. When the transaction is complete, the contents of event memory are passed automatically to CDH, which puts this data in the call data and call summary tables in the database.

Events are recorded in three ways:

• A count event increments an integer into event memory.
• A store event loads an integer or string into event memory.
• A time event loads the time into event memory.

The following are examples for recording information about getinput:

After getting a yes or no reply and storing it in a field called YN, the program:

• Increments event 1, which represents the number of attempts to get a yes or no reply
• Saves the integer in event 2
• Saves the time of the response in event 3

Note that events are write-only variables. Current event values cannot be read. They must be saved in temporary variables to be examined.

Source file

The script instructions are initially stored as an application_name.t source file. This file is given as the argument to the TAS command to produce a machine readable application_name.T file. The application_name.T file is stored in the /vs/trans directory and is used by the TSM process.

© 2006 Avaya Inc. All Rights Reserved.