Multiple interface scripting language6658646Abstract For a large system having an associated monitoring system with one or more user interfaces that each requires a large amount of direct user interaction, a scripting language especially well suited to write a script (that generates liaison interface between the user and the existing user interfaces) is provided. The liaison interface requires much less direct user interaction by taking the place of the user in the extensive direct interaction required by the existing user interfaces. Such a scripting language that includes an integration construct data structure that permits commands of discrete interfaces to be integrated in a single script that is to be executed by a machine. Also provided are scripts according to the scripting language, that include at least two of the integration construct data structures. Claims What is claimed is: Description FIELD OF THE INVENTION
SCRIPT #1
LINE # COMMAND
01 WAM:MSC 5
02 WAM:CELL 49
03 WAM:GETAPX cell2 BACKUP
04 IF:AFAIL
05 THENDO:
06 WAM:PRINT APXRCV cell2 form backup failed,
script aborted.
07 WAM:ENDTEST
08 ELSEDO:
09 ENDIF:
10 WAM:GETAPXFLD cell2 f_list4.c_feat[2]
11 IF:AFAIL
12 THENDO:
13 WAM:PRINT APXRCV cell2 field retrieval failed,
script aborted
14 WAM:ENDTEST
15 ELSEDO:
16 ENDIF:
17 IF:TEST_EXPR APXVAR EQ n
18 THENDO:
19 WAM:SETVAR APXVAR y
20 WAM:PUTAPXFLD cell2 f_list.c_feat[2]
21 IF:AFAIL
22 THENDO:
23 WAM:PRINT APXTCV field update failed, script aborted
24 WAM:ENDTEST
25 ELSEDO:
26 WAM:PRINT Inventory feature enabled
27 ENDIF:
28 ELSEDO:
29 ENDIF:
30 WAM:CONNECT TI
31 IF:LFAIL
32 THENDO:
33 WAM:PRINT TI login attempt failed, script aborted
34 WAM:PUTAPX cell2 BACKUP
35 WAM:ENDTEST
36 ELSEDO:
37 ENDIF:
38 TI:op:cell 49, inventory
39 WAM:DISCONNECT TI
40 WAM:PUTAPX cell2 BACKUP
41 WAM:ENDTEST
Script #1 is written in the Wireless Automation Manager Interface Language (WAMIL). A brief discussion of the lines in the script will be presented. In line 1 of Script #1, the Mobile Switching Center (MSC) variable is set to the value 5. In line 2, the cell variable, CELL, is set to the value 49. In line 3, the GETAPX command is recited, which makes a copy of the database corresponding to the APXRCV database named cell2 and names the copy as "backup." Line 3 of Script #1 corresponds to Item 210 of FIG. 2. Lines 4-9 are included in Script #1 to account for the possibility that there might be a failure in making a backup of the APXRCV database named cell2 database. Lines 4-9 define an IF-construct that tests for whether there has been a failure in making the backup copy. Line 5 indicates the commands to be executed if there is a failure, namely the commands in lines 6 and 7. Line 6 lists the print command to print a text string that notifies of the failure. Line 7 recites the command ENDTEST that terminates interpretation of the script. Line 8 indicates the commands to be interpreted if the tested condition is false, i.e., if the APXRCV database named cell2 is backed up successfully. When the backup copy is made successfully, then the IF-construct terminates at line 9 with the command "ENDIF." At line 10, the command to retrieve the value of a field in the cell2 database is recited. This corresponds to Item 212 of FIG. 2. Lines 11-16 recite an IF-construct that is similar to lines 4-9. But in lines 11-16, the error message to be printed refers to the failure to retrieve a field in the database rather than a failure to backup the entire database. Lines 17-29 recite a third IF-construct. The third IF-construct of Script #1 corresponds to Item 214 and 216 of FIG. 2. At line 17, the value of the field retrieved in line 10 is tested. To reiterate, this corresponds to Item 214 of FIG. 2. The value of this field is tested to determine if it enables the use of a desired command from the TI interface. If the condition is true, namely, if the field value equals n (meaning that the feature is disabled), then the commands denoted by line 18 are interpreted. Line 19 recites a command to set the WAM Interpreter (WAMI) variable APXVAR to the value y. Line 20 recites a command to put the value of APXVAR into the desired field in the APXRCV database named cell2. This corresponds to Item 2 of FIG. 2. Line 21-24 correspond to lines 11-14, which account for the possibility that the requested change to the value in the database will not be made successfully. The text string recited in line 23 is a notification that the field update failed and that interpretation of the script has been terminated. Lines 25-26 correspond to the condition that the field in the database was changed successfully. Line 26 recites a command to print a text string that notifies of the successful field change. In line 30 of Script #1, a TI session is initiated. Lines 31-37 correspond to an IF-construct to account for the possibility that a TI interface session might not be successfully initiated. Line 33 recites the print command to print a text string that indicates that the TI interface session could not be established. Line 34 recites a command to restore the APXRCV database named cell2 database to the values in the copy named BACKUP. Line 38 of Script #1 recites the TI interface command to perform an inventory on cell 49. This corresponds to Item 220 of FIG. 2. Line 39 recites the command to terminate the TI interface session. Line 40 recites the command to restore the database for the APXRCV database named cell2 to the value stored in the copy named BACKUP. This corresponds to item 224 of FIG. 2. Lastly, the script terminates with line 41. Another example script, namely Script #2, follows. Script #2 uses the SDP interface and the TI interface.
SCRIPT #2
LINE
# COMMAND
01 WAM:MSC 5
02 WAM:CONNECT SDP
03 IF:LFAIL
04 THENDO:
05 WAM:PRINT SDP OMP login attempt failed, script aborted
06 WAM:ENDTEST
07 ELSEDO:
08 ENDIF:
09 IF:SDPPORT
10 THENDO:
11 WAM:PRINT SDP vtty ports not available script aborted
12 WAM:ENDTEST
13 ELSEDO:
14 ENDIF:
15 WAM:CELL 49
16 WAM:BBAVAR
17 SDP:2138,49
18 WAM:GETSDP BBA
19 IF:TEST_EXPR SDPVAR_COLOR EQ BLACK_ON_GREEN
20 THENDO:
21 WAM:PRINT BBA BBAVAR is ACTIVE
22 WAM:SET WAMI 1
23 ELSEDO:
24 WAM:PRINT:BBA BBAVAR is NOT ACTIVE
25 ENDIF:
26 WAM:CONNECT TI
27 IF:LFAIL
28 THENDO:
29 WAM:PRINT TI login attempt failed, script aborted
30 WAM:ENDTEST
31 ELSEDO:
32 ENDIF:
33 IF:TEST_EXPT WAMI EQ 1
34 THENDO:
35 TI:dgn:cell 49, bba BBAVAR
36 ELSEDO:
37 TI:rst:cell 49, bba BBAVAR
38 ENDIF:
39 WAM:DISCONNECT TI
40 WAM:DISCONNECT SDP
41 WAM:ENDTEST
In line 1 of Script #2, the Mobile Switching Center Variable, MSC, is set to the value 5. Line 2 recites the command to connect to the SDP interface. Lines 3-8 correspond to an IF-construct for dealing with a first kind of possible failure to establish an SDP interface session. Lines 9-14 present another IF-construct to deal with a second kind of failure to establish an SDP interface session could not be established. Line 15 of Script #2 sets the cell variable, CELL, to the value 49. Line 16 recites the BBVAR command, which indicates that the value for the variable BBA will be supplied by the user to the script as an argument appended to the command line. Line 17 of Script #2 is a command for the SDP interface to return an arrangement of screen indicators identified by screen 2138, for the cell 49. Line 18 recites the GETSDP command to convert the nontext attributes of an indicator corresponding to the value of the variable BBA into text variables. Again, the GETSDP command is explained in detail in the second copending application that has been incorporated by reference, as discussed above. Lines 19-25 of Script #2 represent an IF-construct for testing the condition of whether the indicator is in a particular state. If so, i.e., if the condition is satisfied, then the commands in lines 21 and 22 are to be interpreted. If not, i.e., if the condition is not satisfied, then the command in line 24 is to be interpreted. Line 26 of Script #2 recites the command to establish a second interface session, namely a TI interface session. Lines 27-32 account for the possibility that the TI interface session can not be established. Lines 33-38 of Script #2 represent an IF-construct for deciding whether to perform diagnostics on a cell BBA (line 35) (which take the cell out of service for the duration of the diagnostics) or restore the cell BBA (line 37) depending upon the value of the general WAMIL variable, WAM, that is tested in line 33. It is noted that the value of the WAMIL variable, WAM, corresponds to the state of the indicator, as determined in lines 21-22. The default value for the WAMIL variable WAMI is zero. Hence, no WAM:SET WAMI 0 command is included after line 24, whereas it is necessary in line 22 because it is changing the default value. Line 39 of Script #2 terminates the TI interface session. Line 40 terminates the SDP interface session. Line 41 terminates execution of Script #2. A third example of a script follows. Script #3 emphasizes flow control using the "IF:OMSG" statement as the basis of a second form of an IF-construct. In light of the more detailed discussion of WAMIL commands and IF-construct elements provided below, as well as the discussion above, Script #3 is considered to be self-explanatory.
SCRIPT #3
LINE # COMMAND
01 WAM:MSC 5
02 WAM:CELL 49
03 WAM:CCC 4
04 WAM:CONNECT TI
05 TI:rst:cell 49, ccc 4
06 TI:op:cell 49
07 IF:OMSG OP:CELL CELLVAR CCC CCCVAR, ACTIVE
08 THENDO:
09 WAM:PRINT CCC CCCVAR is active script will continue
10 ELSEDO:
11 IF:OMSG OP:CELL CELLVAR CCC CCVAR, ACTIVE
12 THEN:CONTINUE
13 ELSE:WAITQUERY 5 TI 10
14 IF:OMSG OP:CELL CELLVAR CCC CCCVAR, ACTIVE
15 THENDO:
16 ELSEDO:
17 WAM:PRINT CCC CCVAR never became active
18 WAM:ENDTEST
19 ENDIF:
20 ENDIF:
21 TI:dgn:cell 49, ccc 4
22 IF:OMSG COMPLETED
23 THEN:CONTINUE
24 ELSE:WAITQUERY 5 TI 10
25 WAM:DISCONNECT TI
26 WAM:ENDTEST
A fourth example script follows, namely Script #4. Script #4 emphasizes the WAM:WMMI suite of commands and its related commands. For similar reasons as those presented in the discussion of Script #3, Script #4 is considered to be self-explanatory.
SCRIPT #4
LINE
# COMMAND
01 WAM:WAMLIST Please Enter Paging Rate
02 WAM:WMMIO TESTEND WAMVAR 1 HOME This is
Our Message
03 WAM:WAIT 20
04 WAM:WMMI_GETCOUNT WAMVAR
05 IF:TEST_EXPR WAMVAR GT 3
06 THENDO:
07 WAM:PRINT Paging rate is WAMVAR, to fast! Reduce to
default 1200 per hour.
08 WAM:WMMI_SEND CHANGERATE 1200
09 WAM:WAIT 10
10 WAM:WMMI_GET COUNT WAMVAR
11 IF:TEST_EXPR WAMVAR LT 20
12 THENDO:
13 WAM:PRINT Paging rate is good now!
14 ELSEDO:
15 WAM:PRINT Paging rate still too fast! Script aborted!
16 WAM:WMMI_STOP
17 WAM:ENDTEST
18 ENDIF:
19 ELSEDO:
20 WAM:PRINT Paging rate is not bad!
21 ENDIF:
22 WAM:WMMI_SEND SENDPAT Send this message only once!
23 WAM:WAIT 5
24 WAM:WMMI_SEND CHANGERPAT This is our new message.
25 WAM:WAIT 10
26 WAM:WMMI_STOP
27 WAM:ENDTEST
WAMIL Interpreter Environment The Wireless Application Manager (WAM) Interface Language (WAMIL) Interpreter environment is the preferred, but not the only, environment to execute WAMIL scripts that include the integration construct data structure according to the invention. This environment will now be discussed in more detail. Command Line Script Execution Again, a WAMIL script is passed to an interpreter, preferably the WAM Interpreter (WAMI), for execution. All WAMIL scripts can (in this embodiment of the WAMIL language) have a .wamil extension. For example, the above script if named AUTO1.wamil would be executed as follows, the .wamil extension is understood: WAM21 AUTO1 WAMIL Script Output File All WAMIL scripts generate an output file. all (in this embodiment of the WAMIL language) output files have a .rpt extension. Default script output location is .about.myhome/WAMfiles/Scripts.dir, else -rpt switch is used. WAM21 AUTO1 -rpt .about.some/place/else Output files are overwritten unless the append option is specified as follows: WAM21 AUTO1 -rpt .about.some/place/else -opt a -endopt For example, the above script when executed as the script name AUTO1 would generate the following output: Test Script Name: AUTO1 Test Script Location: /phoenix/h47/ghernand/WAMfiles/wam.wamil Test Script Report Name: AUTO1 Test Script Report Location: phoenix/h47/ghernand/WAMfles/Scripts.dir Test On MSC 5 FStart Test Cell: 49 Connect To TIpdunix on MSC 5 Executed TI: op:cell 49 op:cell 49 IP all specified cells ACT M 45 OP:CELL 49 BBA 6, OOS, FRCELL, RMVD 12/08/98 45 #073412 M 45 OP:CELL 49 CCC 6, ACTIVE BLOCKING FROM CELL, NO ACU ON CCC SHELF BLOCKING FROM SECTOR 3, NO BBA IN SERVICE 12/08/98 45 #073414 M 45 OP:CELL 49 CCC 4, CCU 3, OOS, FRCELL, RMVD 12/08/98 45 #073415 M 46 OP:CELL 49 PROG CONTROL OFF-NORMAL INTERRUPTS INHIBITED: CSC 0 PROCID: MWPER MPARF NCIOCF CPIST CPIMS CPUADRV CPUMTX ANTFT INHIBITED OCFT INHIBITED PLFT INHIBITED TPFT INHIBITED RTDIAG INHIBITED 12/08/98 46 #073417 M 46 OP:CELL 49 COMPLETED 12/08/98 46 #073418 M 46 OP:CELL 49 DL 0 CONNECTED 12/08/98 46 #073427 M 46 OP:CELL 49 DL 1 CONNECTED 12/08/98 46 #073428 M 46 OP:CELL 49 STATUS & CONTROLS BOOT ALW, CP ALW, PH MON ALW, PH STATE ACTIVE, DL(S) UP FORWARD SETUP CHANNEL CONTROL NORMAL (INH) 12/08/98 46 #073430 Disconnect From TIpdunix on MSC 5 ENDTEST MSC 5 CELL 49 END OF TEST SCRIPT EXECUTION WAMIL Commands Output All WAMIL commands, when executed, generate output messages to the script output file. These messages can be monitored to track script progress. To turn WAMIL commands output messages off the WAM:OUTPUTOFF command can be used. WAMIL DISPLAY Command All WAMIL scripts are executed in the background. To slow execution of the script and monitor its progress the WAM:DISPLAY <seconds> command can be included in the script. This command will open a display window in which the script will be executed. WAMI Key Global Variables The WAMIL scripting language has a predefined set of global variables, known as key global variables or key variables. They anticipate most of the parameters, settings and/or preferences related to a wireless system that a user might wish to manipulate. Because they are predefined, these key global variables also have default values and do not need to be created. Non-key global variables are not predetermined. Rather, they are created by the user with the CREATEVAR command (to be discussed below) to help solve the particular problem for which the script has been written. Global variables will be discussed further below after the table listing the WAM global variables. Below is a list of all (in this embodiment of the WAMIL language) WAMI key global variables. The list also shows the variable type, default value and a brief description.
TABLE 1
WAMI Key Global Variables
VAR- DE- VALUE
IABLE FAULT TYPE DESCRIPTION
ADDCE 0 Integer Number of Channel Elements
to add.
ADRS NULL String Memory Address
AFAIL 0 Integer APXRCV failure flag
ANT 0 Integer Antenna face Number
AU 1 Integer Cell Amplifier Unit Number
BBA 1 Integer BCR-BIU-ACU Trio Number
CAT 0 Integer Clock and Tone Board
Number
CCC 1 Integer CDMA Cluster Controller
Number
CCU 1 Integer CDMA Channel Unit Number
CDMADPC 0 Integer BBA Power Control Option
CELL 0 Integer Cell Site Number
CELL.sub.-- SER- Alphanumeric Cell Site Equipment Type
TYPE IESII
CFAIL 0 Integer Interface Connection Flag
CGSA 0 Integer Cellular Geographic Service
Area
CONFIG 0 Integer Cell Configuration Option
CSC 0 Integer Cell Site Controller
DCCH 0 Integer Dedicated/Digital Control
Channel
DCS 0 Integer Digital Cellular Switch
Number
Display- 1 Integer Script Display Window Delay
Delay
DL 0 Integer Cell Site Data Link
DS1 0 Integer Digital Service 1 Number
ECP 0 Integer Executive Cellular Processor
Number
ERR 0 Integer WAM Interpreter exit value
GEN 0 Alphanumeric Generic Number/Name
INACT 60 Integer Interface Session Inactivity
(Minutes)
LAC 0 Integer Cell Linear Amplifier Circuit
Number
LC 0 Integer Cell Locate Radio Number
LFAIL 0 Integer Interface Login Flag
LMT 0 Integer Lightwave Microcell
Transceiver Number
LOOPERcnt 1 Integer WAMI script looping counter
LOOPER 1 Integer WAMI script looping limit
MICRO- 0 Integer FLEXANT RCS Number
CELL
MSC 0 Integer Mobile Switching Center
Number
OC 0 Integer Overhead Channel Number
PH 0 Alphanumeric TI Specified Phase Number(s)
PL 0 Integer Pilot Level Number
RA 0 Alphanumeric Cell Radio Number
REL 8.0 Alphanumeric Current software release
RG 0 Integer Cell Reference Generator
Number
RPT 0 Integer TI Repeat Diagnostics Number
RptName None Alphanumeric Script Report Name
SDPFAIL 0 Integer SDP interface failure flag
SDPPORT 0 Integer SDP port flag
SG 0 Integer Server Group Number
SPOOL 10 Integer WAMI Spooler Pause
(Seconds)
SU 0 Integer Cell Setup Radio Number
SW 0 Integer Switch Identification Number
TFAIL 0 Integer Interface Command Time Out
Flag
TimeOut 30 Integer WAMI Interface Time Out
(Seconds)
TP 0 Integer Traffic Path Number
TRACE 0 Integer WAMI TRACE Flag
TRKGRP 0 Integer Trunk Group Number
TRKMBR 0 Integer Trunk Member Number
VRADPC 0 Integer Voice Radio Power Control
Option
VRN 0 Integer Voice Radio Number
Wait 10 Integer WAMI Script Execution Pause
(Seconds)
WAM 0 Alphanumeric WAMI Interpreter global
variable
XMITC 0 Integer Transmitter Control Action
Option
Key Variables in a WAMIL Script Key variables already exist with default values. Interface commands reference key global variables. WAM Interpreter commands alter, act upon, or perform functions based upon the current values of the key global variables. Below are a few examples of key global variables. A complete discussion follows later.
WAMI GLOBAL VARIABLE DEFAULT VALUE
MSC 0
CELL 0
CCC 1
CCU 1
RA 0
Direct Assignment Commands WAMI key global variables can be altered with WAM Interpreter assignment commands. An example script follows:
MSC CELL
SCRIPT 0 0
WAM:MSC 5 5 0
WAM:CELL 49 5 49
WAM:CONNECT TI 5 49
TI:op:cell 49 5 49
WAM:CELL 101 5 101
TI:op:cell 101 5 101
WAM:SET CELL 60 5 60
TI:op:cell 60 5 60
WAM:DISCONNECT TI 5 60
WAM:ENDTEST 5 60
Referencing WAMI Key global variables Within Strings To reference a WAMI key global variable within a string the suffix VAR is added to the key global variable name. WAM:PRINT The script CELL number is CELLVAR. If CELL was set to the value of 49, the above would print to the WAMIL script output file as follows: The script CELL number is 49. WAM Interpreter Script Parsing & Execution Each line of a WAMIL script is parsed and then executed. The interpreter parser and executor each have a four step process: PARSER 1) Check command syntax. 2) Verify against key global variables if interface command. 3) Check for Parser required flags or states. 4) Set Parser & Executor required flags & states. EXECUTOR 1) Check for Executor required flags or states. 2) Perform key global variable & keyword substitutions. 3) Execute command. 4) Set Parser & Executor required flags & states. WAM Interpreter Keywords & Operators The WAM Interpreter (WAMI) supports path keywords which can be used for the path argument on most commands. Below is a list of these keywords along with a description of their meaning:
PATH KEYWORD DESCRIPTION
CERT Script located in certified directory.
HOME Script located in user's HOME directory.
SHARE Script located in WAMI SHARE directory
The WAM Interpreter also supports print character keywords which can be inserted in strings to print special characters or WAMI information. Below is a list of these keywords along with the character, or information, substituted with when referenced with a string:
KEYWORD CHARACTER
REPORTNAME The WAMIL script report name.
REPORTPATH The WAMIL script output file location.
SCRIPT_NAME The WAMIL script name.
SCRIPTPATH The WAMIL script location
WAMBLANK A blank space
WAMBUFFER WAM Interpreter buffer
WAMHOME The user's current HOME
WAMNL new line
WAMTAB tab
The WAM Interpreter also supports the use of relational operators within IF-constructs and WHILE-constructs, and mathematical operators with the MATHVAR command. Below is a list of all (in this embodiment of the WAMIL language) the relational operators supported:
OPERATOR NAME DESCRIPTION
+ Plus
- Minus
* Multiply
/ Divide
EQ Equal To
GT Greater Than
GTE Greater Than Or Equal To
LT Less Than
LTE Less Than Or Equal To
NE Not Equal To
WAMI VAR Variables WAMI Key Variables In addition to the predefined WAM global variables that have default values, the WAMIL language also supports auxiliary/complimentary global values that are created as needed by the user via the CREATEVAR command. All key variables have complimentary/auxiliary storage locations, also known as VAR variables. A WAMI key global variable can be set to a value or point to an auxiliary WAMI VAR variable, i.e., storage location. Associations When a WAMI key global variable points to a WAMI VAR variable within a script, the WAMI key global variable value is then the current value of the WAMI VAR variable. In such a case, the WAMI key global variable has an association with a WAMI VAR variable. Thus, all (in this embodiment of the WAMIL language) references to the WAMI key global variable will yield the value of the WAMI VAR variable it is associated with. A key global variable can only (in this embodiment of the WAMIL language) be referenced in an interface command that expects it as an argument. But the WAMI VAR variable can be referenced by any (in this WAMIL language embodiment) command so long as it has been associated with a key global variable. In this sense, WAMI key global variables are private and protected, while WAMI VAR variables are public. VAR Type Commands This is a dual function command that will also illicit a response from the WAM GUI platform. An argument passed to script is assigned to a WAMI VAR variable, and an association with the corresponding WAMI key global variable is automatically established. An example script, with an indication of variable values, follows.
MSC CELL CELLVAR
SCRIPT 0 0 ?
WAM CELLVAR 0 CELLVAR 49
WAM:MSC 5 5 CELLVAR 49
WAM:CONNECT TI 5 CELLVAR 49
TI:op:cell CELLVAR 5 CELLVAR 49
WAM:DISCONNECT TI 5 CELLVAR 49
WAM:ENDTEST 5 CELLVAR 49
The above script if named AUTO1 could be executed from the command line as follows: WAM21 AUTO1 -cell 49 Inheritance A WAMI key global variable can inherit the association of another WAMI key global variable by use of the WAM:SET command. An example script, with an indication of variable values, follows.
SCRIPT MSC CELL CCC CCU CCCVAR
0 0 1 1 ?
WAM:MSC5 5 0 1 1 ?
WAM:CELL 49 5 49 1 1 ?
WAM:CCCVAR 5 49 CCCVAR 1 2
WAM:SET CCU 5 49 CCCVAR CCCVAR 2
CCC
WAM:CONNECT 5 49 CCCVAR CCCVAR 2
TI
TI:op:cell 49, ccc 5 49 CCCVAR CCCVAR 2
CCVAR, ccu
CCCVAR
WAM:DISCON- 5 49 CCCVAR CCCVAR 2
NECT TI
WAM:ENDTEST 5 49 CCCVAR CCCVAR 2
The above script if named AUTO1 could be executed from the command line as follows: WAM21 AUTO1 -ccc 2 Association Transfers A WAMI key global variable association can be transferred to another WAMI key global variable by use of the WAM:SETVAR command. An example script, with an indication of variable values, follows.
SCRIPT CCC CCU CCCVAR CCUVAR
1 1 ? ?
WAM:MSC 5 1 1 ? ?
WAM:CELL 49 1 1 ? ?
WAM:CCCVAR CCCVAR 1 2 ?
WAM:CCUVAR CCCVAR CCUVAR 2 4
WAM:CONNECT TI CCCVAR CCUVAR 2 4
TI:op:cell 49, CCCVAR CCUVAR 2 4
ccc CCCVAR,
ccu CCUVAR
WAM:SETVAR CCCVAR CCCVAR 2 CCCVAR
CCUVAR CCC
TI:op:cell 49, CCCVAR CCCVAR 2 CCCVAR
ccc CCCVAR,
ccu CCCVAR
WAM:DISCONNECT TI CCCVAR CCCVAR 2 CCCVAR
WAM:ENDTEST CCCVAR CCCVAR 2 CCCVAR
The above script if named AUTO1 could be executed from the command line as follows: WAM21 AUTO1 -ccc 2 -ccu 4.
A example WAMIL Script With VAR Variables
SCRIPT MSC CELL CCC CCU
0 0 1 1
WAM:MSCVAR MSCVAR 0 1 1
WAM:CELLVAR MSCVAR CELLVAR 1
WAM:CCCVAR MSCVAR CELLVAR CCCVAR CCUVAR
WAM:CCUVAR MSCVAR CELLVAR CCCVAR CCUVAR
WAM:CONNECT TI MSCVAR CELLVAR CCCVAR CCUVAR
TI:op:cell CELLVAR,
ccc CCCVAR,
ccu CUVAR
WAM:DISCONNECT MSCVAR CELLVAR CCCVAR CCUVAR
TI
WAM:ENDTEST MSCVAR CELLVAR CCCVAR CCUVAR
The above script if named AUTO1 could be executed from the command line as follows: WAM21 AUTO1 -msc 5 -cell 49 -ccc 2 -ccu 4 Referencing WAMI VAR Variables Within Strings To reference an auxiliary WAMI VAR variable within a string it can (in this embodiment of the WAMIL language) be associated to a WAMI key global variable first. There is no way to directly reference it. For example, the following example script lines print the value of CELL which has been assigned 49. WAM:CELL 49 WAM:PRINT The script CELL number is CELLVAR. If the cell number is passed as an argument during command line execution, for example -cell 101, the following script lines, WAM:CELLVAR WAM:PRINT The script CELL number is CELLVAR. will generate output to the script WAMIL report file as follows: The script CELL number is 101. Creating WAMI VAR Variables WAMI VAR variables can be created with the CREATEVAR command. The new VAR variable created will be of type integer. The new VAR variable can be associated with any (in this WAMIL language embodiment) WAMI global variable. A complimentary WAMI global variable is also created simultaneously, but it is not a key global variable (key variable). WAMI VARn LIST Not only (in this embodiment of the WAMIL language) can single variables be set in the WAMIL language, but an interface command can access an entry in any (in this WAMIL language embodiment) array of variables, i.e., a list. Auxiliary/Complementary WAMI Global Variable LIST A WAMI key global variable can be set to a value, set to point to a WAMI VAR variable, or set to point to a WAMI VARn variable (an element in a list, i.e., a one-dimensional array). WAMI VARn variables do not support Inheritance nor Association Transfers because they are elements of a list. LIST Declaration Commands A LIST can (in this embodiment of the WAMIL language) first be declared before WAMI VARn variables from a LIST can be used within a script. A LIST can be declared anywhere within a WAMIL script. The LIST size is provided as an argument with a LIST declaration command. VARn Variables LIST VARn variables are referenced using a numerical index into the LIST that is appended to the text string, VAR. The first VARn variable has an index of 1. An example script with an indication of variable values, follows.
BBA BBALIST
SCRIPT 1 ?
WAM:MSC 5 1 ?
WAM:CELL 49 1 2 4 6
WAM:BBALIST 3 1 2 4 6
WAM:CONNECT TI 1 2 4 6
WAM:SET BBA BBAVAR1 2 2 4 6
TI:op:cell 49, bba BBAVAR1 2 2 4 6
WAM:SET BBA BBAVAR2 4 2 4 6
TI:op:cell 49, bba BBAVAR2 4 2 4 6
WAM:SET BBA BBAVAR3 6 2 4 6
TI:op:cell 49, bba BBAVAR3 6 2 4 6
WAM:DISCONNECT TI 6 2 4 6
WAM:ENDTEST 6 2 4 6
The above script if named AUTO1 could be executed from the command line as follows: WAM21 AUTO1 -bbalist 2 4 6 -endlist VARn Type Commands VARn variable referenced is automatically associated to the key global variables in the script. An example script, with an indication of variable values, follows.
SCRIPT BBA BBALIST
1 ?
WAM:MSC5 1 ?
WAM:CELL 49 1 2 4 6
WAM:BBALIST 3 1 2 4 6
WAM:BBAVAR1 BBAVAR1 2 4 6
WAM:CONNECT TI BBAVAR1 2 4 6
TI:op:cell 49, bba BBAVAR1 BBAVAR1 2 4 6
WAM:DISCONNECT TI BBAVAR1 2 4 6
WAM:ENDTEST BBAVAR1 2 4 6
In line 4 of this example script, the key global variable BBA is associated with the first variable in the complimentary/auxiliary BBA list. The above script if named AUTO1 could be executed from the command line as follows: WAM21 AUTO1 -bbalist 2 4 6 -endlist Referencing VARn Variables Within Strings A VARn variable can be directly referenced within a string, no association needs to be established. WAM:PRINT The script BBA number is BBAVAR1. WAMLIST WAMLIST is a special WAM Interpreter LIST of infinite size. No LIST size can (in this embodiment of the WAMIL language) be stated upon the declaration of a WAMLIST. The WAMLIST string, e.g. (in the script below), "Enter Two BBA Numbers," provided as an argument can be used by other applications to prompt a user, or simply as a comment field. WAMLIST VARn variables referenced outside the LIST return a blank value. A WAMLIST can be declared anywhere within a WAMIL script. An example script, with an indication of variable values, follows.
SCRIPT BBA WAMLIST
1 ?
WAM:MSC5 1 ?
WAM:CELL 49 1 ?
WAM:WAMLIST Enter Two BBA Nos. 1 2 4
WAM:CONNECT TI 1 2 4
WAM:SET BBA WAMVAR1 2 2 4
TI:op:cell 49, bba WAMVAR1 2 2 4
WAM:SET BBA WAMVAR2 4 2 4
TI:op:cell 49, bba WAMVAR2 4 2 4
WAM:DISCONNECT TI 4 2 4
WAM:ENDTEST 4 2 4
The above script if named AUTO1 could be executed from the command line as follows: WAM21 AUTO1 -wamlist 2 4 -endlist WAMIL Control Flow Some aspect of the flow control that takes place during execution of a WAMIL script will now be discussed. WAM Interpreter Buffer Always holds output of the last interface command executed, unless altered. Flushed prior to the execution of an interface command. Can be flushed with WAM Interpreter command WAM:FLUSHBUFF Can be appended to with WAITQUERY command execution. Can be overwritten with execution of WAM:INPUT command. Can be output to a file with execution of the WAM:OUTPUT or WAM:PUTS command. CONNECT Command Establishes a session between the WAM Interpreter and the interface provided as an argument. WAM:CONNECT interface Sets LFAIL flag if server login attempt fails. Sets TFAIL flag if an interface command execution times out. Sets CFAIL flag if an active session unexpectedly disconnects. For SDP interface, sets SDPPORT flag if no vtty ports are available after a successful login, and SDPFAIL for any failure during the execution of an SDP interface command. ENDTEST Command Terminates the WAMIL script. WAM:ENDTEST Terminates all (in this embodiment of the WAMIL language) active sessions upon execution. Can (in this embodiment of the WAMIL language) be included at the end of a script or a syntax error will be generated. IF:OMSG Construct Searches the WAM Interpreter buffer for the string provided as an argument. IF:OMSG string Argument string can include global-style matching patterns (*, ?, [ ], .backslash.). It can include references to WAMI key global variables and VARn variables. A match evaluates as TRUE, while no match evaluates as FALSE. An example script follows. WAM:MSC 5 WAM:CELL 49 WAM:CCC 4 WAM:CONNECT TI TI:op:cell 49 IF:OMSG OP:CELL CELLVAR CCC CCCVAR, ACTRVE THEN:CONTINUE ELSE:PRINT CCC CCCVAR is not active. WAM:DISCONNECT TI WAM:ENDTEST IF THEN ELSE Construct Can (in this embodiment of the WAMIL language) be complete and include an IF, and at a minimum one THEN and one ELSE. Multiple THEN and ELSE command can exist within a construct. Supports the WAM Interpreter WAITQUERY command which camps on the TI interface. An example script follows. WAM:MSC 5 WAM:CELL 49 WAM:CCC 4 WAM:CONNECT TI TI:rst:cell 49, ccc 4 TI:op:cell 49 IF:OMSG OP:CELL CELLVAR CCC CCCVAR, ACTIVE THEN:CONTINUE THEN:PRINT CCC CCCVAR is active. ELSE:WAITQUERY 5 TI 10 WAM:DISCONNECT TI WAM:ENDTEST IF THENDO ELSEDO ENDIF Construct All the commands between the THENDO and ELSEDO constructs are executed if the result of the IF command execution is TRUE, and all (in this embodiment of the WAMIL language) the commands between the ELSEDO and ENDIF are executed if the result of the IF command execution is FALSE. All WAMIL IF THENDO ELSEDO ENDIF constructs can (in this embodiment of the WAMIL language) be complete and include an IF, a THENDO, an ELSEDO, and an ENDIF. Any WAMIL IF THEN ELSE construct can be nested within any (in this WAMIL language embodiment) THENDO ELSEDO, or ELSEDO ENDIF construct. Also, IF THENDO ELSEDO ENDIF constructs can be nested within other IF THENDO ELSEDO ENDIF constructs, as desired. WHILE ENDWHILE Construct Continuously loops through the execution of a group of commands until WHILE TEST_EXPR evaluates false. Supports the BREAK: command to break out of the loop at any (in this WAMIL language embodiment) time. An example script follows. WHILE:TEST_EXPR CELLVAR LT 223 TI:op:cell CELLVAR WAM:INCRVAR CELLVAR 1 ENDWHILE: An example WAML Script That Illustrates Control Flow WAM:MSC 5 WAM:CELL 49 WAM:CCC 4 WAM:CONNECT TI TI:rst:cell 49, ccc 4 TI:op:cell 49 IF:OMSG OP:CELL CELLVAR CCC CCCVAR, ACTIVE THENDO: WAM:PRINT CCC CCCVAR is active script will continue. ELSEDO: IF:OMSG OP:CELL CELLVAR CCC CCCVAR, ACTIVE THEN:CONTINUE ELSE:WAITQUERY 5 TI 10 IF:OMSG OP:CELL CELLVAR CCC CCCVAR, ACTIVE THENDO: ELSEDO: WAM:PRINT CCC CCCVAR never became active. WAM:ENDTEST ENDIF: ENDIF: TI:dgn:cell 49, ccc 4 IF:OMSG COMPLETED THEN:CONTINUE ELSE:WAITQUERY 5 TI 10 WAM:DISCONNECT TI WAM:ENDTEST SPOOL Command The WAMIL SPOOL command which adjust the pause of the spooler. GET_TI Command The WAMIL GET_TI command which allows assignment of an output message value to a script VAR variable. TRACE Command TRACE command with specified options allows low level tracing of WAMIL commands and variables during a script execution. TRACE can be turned on with TRACEON command, or off with TRACEOFF command, at any (in this WAMIL language embodiment) time during execution of a script. Opens a TRACE display window to allow viewing of actual TRACE during script execution. Creates a trace log file called, wam.tracelog, which is located in the user's HOME wam.trace sub-directory and is appended to during the execution of any (in this WAMIL language embodiment) TRACE. The following table indicates arguments that can be passed to the TRACE command. It is noted that every (in this embodiment of the WAMIL language) WAM Interpreter command can be traced by substituting the name of the command for the argument, x, that can be appended to the TRACE command.
TRACE OPTION
WAMI command execution level x
WAMI executor states i
WAMI session states f
WAMI variables v
WAMI stack s
WAMI buffer o
PAUSE Command The WAMIL PAUSE command can be used for semi-automation, or to prompt the user for a decision. Upon execution of the PAUSE command, a box is displayed, prompting the user to decide whether the script execution should be continued or aborted: File Creation The WAMIL PUTS command can be used to create files from within a script. The following example script creates a file used to update an APXRCV DB form. WAM:MSCVAR WAM:CELLVAR WAM:ANTVAR WAM:WAMLIST Enter a value for t_add and a value for t_drop WAM:PUTS HOME TEMP.dbf t_add=WAMVAR1 WAM:PUTS HOME TEMP.dbf t_drop=WAMVAR2 WAM:PUTAPX ceqface TEMP WAM:UNIX rm TEMP.dbf WAM:ENDTEST Script Looping A WAMIL script can be looped using the -loop option. In the following example the script AUTO1 is looped 10 times. WAM21 AUTO1 -loop 10 UNIX Command The WAMIL UNIX command allows the execution of any (in this WAMIL language embodiment) UNIX executable from within a WAMIL script. The following example script executes another WAMIL script using the UNIX command, after using the UNIX command to delete a temporary file. The executed WAMIL script process is then stopped after three minutes: WAM:MSCVAR WAM:CELLVAR WAM:ANTVAR WAM:WAMLIST Enter a value for t_add and a value for t_drop WAM:PUTS HOME TEMP.dbf t_add=WAMVAR1 WAM:PUTS HOME TEMP.dbf t_drop=WAMVAR2 WAM:PUTAPX ceqface TEMP WAM:UNIX rm TEMP.dbf WAM:UNIX WAM21 jt1234 -msc MSCVAR -cell CELLVAR & WAM:WAIT 180 WAM:UNIX kill -9 WAMVAR WAM:ENDTEST WAMI Linker WAMIL scripts can be linked by creation of a Linker script. The WAM Interpreter LINK:EXEC command can be used to define the execution mode of the linked scripts. A detailed glossary of WAMI Link commands is presented later in this document. Serial or Parallel Execution A linked script can be executed in a serial or parallel fashion. In a serial fashion execution of the next Linker script command does not start until the linked script has completed execution. WAMI key global variables can be altered by a serially executed linked script. In a parallel fashion the linked script is launched and becomes independent of the Linker script. WAMI key global variables CANNOT be altered by a script executed in a parallel fashion. A WAMIL Linker Script An example WAMIL Linker script below links four WAMIL scripts together. Two of the scripts are executed in a serial fashion: LINK:EXEC PARALLEL LINK:SCRIPT HOME jt1234 LINK:SCRIPT HOME jt2023 LINK:EXEC SERIAL LINK:SCRIPT HOME jt4567 LINK:SCRIPT HOME jt9988 WAM:ENDTEST The above Linker script if named AUTO1 could be executed from the command line as follows: WAM21 AUTO1 -link. Linker Script Output WAMIL Linker scripts generate their own output files. Linker output files also include output from serially executed linked scripts. Linked WAMIL scripts also generate their own output file. If the above Linker script was named LINKAUTO, execution of the script would generate five separate output files: LINKAUTO.rpt, jt1234.rpt, jt2023, jt4567.rpt, jt9988.rpt Commands Embeddable Within Integration Construct Data Structure A table listing the names of WAMI Interface Commands that can be embedded in the integration construct data structure, according to the invention, follows immediately. More detailed discussions of each of the commands are provided after the table.
WAMI Interface Commands
ADDCE CGSA FLUSHTAGS OC SG
ADRS CLOSE GEN OPEN SPOOL
ANT COMMENT GENVAR OUTPUT SU
ANTVAR CONFIG GETAPX OUTPUTOFF SW
APXVAR CONNECT GETAPXFLD OUTPUTON TIME
AU CREATEVAR GETCELLS PAUSE TTMEOUT
BBA CSC GETGEN PH TIMER
BBALIST CSCVAR GETLISTVAR PL TP
BBAVAR DATE GETROP PRINT TRACE
BBAVARn DCCH GETSDP PUTAPX TRACEOFF
CAT DCS GET_TI PUTAPXFLD TRACEON
CATLIST DECR INCR PUTS TRKGRP
CATVARn DECRVAR INCRVAR RA TRKMBR
CCC DELCE INITIALIZE RALIST UNIX
CCCLIST DISCONNECT INPUT RAVAR VRADPC
CCCVAR DISPLAY LAC RAVARn VRN
CCCVARn DL LAUNCH REPORT WAIT
CCU DSI LC RESTOREWAM WAM
CCULIST ECP LMT RG WAMLIST
CCUVAR EMAILME LOOPCELL RPT WAMVAR
CCUVARn EMAILRPT LOOPCELLVARS SAVEWA WMMI
CDMADPC ENDTEST MATHVAR SEND WMMI_GET
CE EXEC MICROCELL SET WMMI_SEND
CELL FLUSHBUFF MSC SETLISTVAR WMMI_STOP
CELLVAR FLUSHIP MSCVAR SETVAR XMITC
Each WAMIL command in this section will be explained in detail. A quick purpose is presented along with its syntax and an example of the command. There is also a detailed description along with errors generated, if any, and the output generated by the command to the WAMIL report file. If the command alters key variables, these key variables are stated. An example script is also provided for almost all (in this embodiment of the WAMIL language) the commands. Each example is simple, but serves as a basis to enhance understanding of the command in the context of a WAMIL script. For execution of WAMIL scripts via the WAMI GUI Platform, WAMIL commands with dual functions that also generate a response from the WAMI GUI Platform have a section which discusses how the platform handles the command. Glossary of WAMI Interface Commands This section presents a detailed glossary of commands that can be embedded in the integration construct data structure according to the invention. The integration construct data structure, again, is also known as a WAM interface command. These commands are best suited to the WAM Interpreter. They commands can be used in WAMIL scripts to change script variables, input/output parameters, or perform specific functions or capabilities. Again, a WAM interface command is structured as, e.g., WAM:CELL 93 where CELL is the actual WAM interface command and the value of 93 is the command argument. The glossary begins with the command, ADDCE, and ends with the command, XMITC. ADDCE The ADDCE command can be embedded in the integration construct data structure according to the invention. PURPOSE: This command changes the WAMI global number of channel elements to add the variable, ADDCE, to the value provided as an argument. SYNTAX: WAM:ADDCE value EXAMPLE CALL: WAM:ADDCE 2 DESCRIPTION: The ADDCE command sets the WAMI global number of channel elements to add variable to the value provided as an argument. After execution of this command, all (in this embodiment of the WAMIL language) subsequent commands which require use of the global number of channel elements to add variable, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script global number of channel elements to add variable, will reference the new value. Execution of this command also disables any (in this WAMIL language embodiment) association which exists between this WAMI global variable and any WAMI VAR variable. OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution of an ADDCE command: Set Number Of Channel Elements to Add To 2 ERRORS: None. ALTERS: ADDCE DEFAULT VALUE: ADDCE is set to 0 upon initial startup, and is of type string. The WAM:INITIALIZE command also sets this variable to 0. SEE ALSO: WAM:INITIALIZE ADRS The ADRS command can be embedded in the integration construct data structure according to the invention. PURPOSE: Changes the WAMI global memory address number variable, ADRS, to the value provided as an argument. SYNTAX: WAM:ADRS value EXAMPLE CALL: WAM:ADRS X'500be020,18 DESCRIPTION: The WAM:ADRS command sets the WAMI global memory address number variable to the value provided as an argument. After execution of this command, all (in this embodiment of the WAMIL language) subsequent commands which require use of an memory address number, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script memory address number, will reference the new value. Execution of this command also disables any (in this WAMIL language embodiment) association which exists between this WAMI global variable and any WAMI VAR variable. OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution of an ADRS command: Set Memory Address To X'500be020,18 ERRORS: None. ALTERS: ADRS DEFAULT VALUE: ADRS is set to NULL upon initial startup, and is of type string. The WAM:INITIALIZE command also sets this variable to NULL. SEE ALSO: WAM:INITIALIZE EXAMPLE: The following script lines will set the WAMIL script ADRS variable to X500be020,18 and then execute a TI interface command: WAM:CELL 49 WAM:CCC 2 WAM:ADRS X500be020,18 TI:dump:cell 49, ccc 2; adrs X500be020,18 ANT The ANT command can be embedded in the integration construct data structure according to the invention. PURPOSE: Changes the WAMI global antenna face variable, ANT, to the value provided as an argument. SYNTAX: WAM:ANT value EXAMPLE CALL: WAM:ANT 1 DESCRIPTION: The WAM:ANT command sets the WAMI global antenna face variable to the value provided as an argument. After execution of this command, all (in this embodiment of the WAMIL language) subsequent commands which require use of an antenna face number, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script antenna face number, will reference the new value. Execution of this command also disables any (in this WAMIL language embodiment) association which exists between this WAMI global variable and any WAMI VAR variable. OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution an ANT command: Set Antenna Face 1 ERRORS: None. ALTERS: ANT DEFAULT VALUE: ANT is set to 0 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 0. SEE ALSO: WAM:INITIALIZE EXAMPLE: The following script lines will set the WAMIL script ANT variable to 1 and then execute a TI interface command: WAM:CELL 49 WAM:ANT 1 TI:op:cell 49, sg 0, ant 1, all! ANTVAR The ANTVAR command can be embedded in the integration construct data structure according to the invention. PURPOSE: Declares to the WAM Interpreter, that a value for the WAMI VAR variable ANTVAR will be supplied to the script. SYNTAX: WAM:ANTVAR EXAMPLE CALL: WAM:ANTVAR DESCRIPTION: The WAM:ANTVAR command is a WAMIL declaration command which executes an assignment function. Upon detection of this command, the WAM Interpreter will search the command line arguments for a value to assign to the WAMI VAR variable ANTVAR. Like standard WAMI VAR variable declaration commands, the execution of this command also enables an association with the WAMI global ANT variable. Therefore, until the WAMI global ANT variable association is transferred to another WAMI VAR variable, or disabled, all (in this embodiment of the WAMIL language) references to the WAMI global ANT variable will use the ANTVAR variable value. For script syntax, until an actual ANT number is passed as an argument, when a ANTVAR command is used the ANT number within a script shall be referenced as ANTVAR from that point forward. This command has a dual function and will initiate prompting by the WAMI GUI platform if the script is executed via the platform. For WAMI GUI platform information refer to the WAMI GUI PLATFORM section below. WAMI GUI PLATFORM: Prior to execution of a WAMIL script, the WAMI GUI platform searches the script for special commands. If a WAM:ANTVAR is encountered the WAMI GUI platform will prompt the user for the script ANTVAR value. Subsequent WAM:ANTVAR commands encountered will not cause additional prompting. SCRIPTOR: If a ANTVAR command is deleted from the current script, the Scriptor will prompt the user for a ANT number and then insert a WAM:ANT value command in place of the ANTVAR command deleted. OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution a ANTVAR command: Set ANT To Argument Value of 2 ERRORS: If no command line value has been provided, the WAM Interpreter will generate an error and script execution will be aborted. ALTERS: ANTVAR DEFAULT VALUE: ANTVAR is set to an unknown state upon initial startup, and is of type integer. The WAM:INITIALIZE command does not reset this WAMI VAR variable. SEE ALSO: WAM:ANT value EXAMPLE: The following script executes a TI command for the ANT number supplied: WAM:MSC 5 WAM:CELL 49 WAM:SG 0 WAM:ANTVAR WAM:CONNECT TI TI:op:cell 49, sg 0, ant ANTVAR, all! WAM:DISCONNECT TI WAM:ENDTEST APXVAR The APXVAR command can be embedded in the integration construct data structure according to the invention. PURPOSE: Declares to the WAM Interpreter, that a value or string for the WAMI VAR variable APXVAR will be supplied to the script. SYNTAX: WAM:APXVAR prompt string EXAMPLE CALL: WAM:APXVAR Enter Neighbor Cell Number DESCRIPTION: The WAM:APXVAR command is a WAMIL declaration command which executes an assignment function. Upon detection of this command, the WAM Interpreter will (for this embodiment of the WAMIL language) search the command line arguments for a value or string to assign to the WAMI VAR variable APXVAR. Unlike other WAMI VAR variable declaration commands, the execution of this command does not enable an association with a WAMI global variable since there is no complementary APX WAMI global variable. This command has a dual function. The prompt_string argument, although not used by the WAM Interpreter, will generate a syntax error if omitted. For prompt_string use refer to the WAMI GUI PLATFORM section below. WAMI GUI PLATFORM: Prior to execution of a WAMIL script, the WAMI GUI platform searches the script for special commands. If a WAM:APXVAR is encountered the WAMI GUI platform will prompt the user, using prompt_string, for the script APXVAR value or string. Subsequent WAM:APXVAR commands encountered will not cause additional prompting. OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution an APXVAR command: Set APXVAR To Argument Value of 173 ERRORS: The prompt_string argument, although not used by the WAM Interpreter, will generate a syntax error if omitted. If no command line value or string has been provided, the WAM Interpreter will generate an error and script execution will be aborted. ALTERS: APXVAR DEFAULT VALUE: APXVAR is set to an unknown state upon initial startup, and is of type string. The WAM:INITLALIZE command does not reset this WAMI VAR variable. SEE ALSO: WAM:WAMVAR prompt_string EXAMPLE: The following script adds a neighbor to cell 49: WAM:MSC 5 WAM:CELL 49 WAM:ANT 1 WAM:SG 0 WAM:APXVAR Enter Neighbor Cell Number WAM:PUTAPXFLD fci cdmanbr_listl.ncs_c[1]=APXVAR WAM:ENDTEST AU The AU command can be embedded in the integration construct data structure according to the invention. PURPOSE: Changes the WAMI global cell amplifier unit number variable, AU, to the value provided as an argument. SYNTAX: WAM:AU value EXAMPLE CALL: WAM:AU 1 DESCRIPTION: The WAM:AU command sets the WAMI global cell amplifier unit number variable to the value provided as an argument. After execution of this command, all (in this embodiment of the WAMIL language) subsequent commands which require use of the cell amplifier unit number, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script cell amplifier unit number, will reference the new value. Execution of this command also disables any (in this WAMIL language embodiment) association which exists between this WAMI global variable and any WAMI VAR variable. OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution an AU command: Set Amplifier Unit 1 ERRORS: None. ALTERS: AU DEFAULT VALUE: AU is set to 1 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 1. SEE ALSO: WAM:INITIALIZE EXAMPLE: The following script lines will set the WAMIL script AU variable to 1 and then execute a TI interface command: WAM:CELL 49 WAM:AU 1 TI:op:cell 49, au 1 BBA The BBA command can be embedded in the integration construct data structure according to the invention. PURPOSE: Changes the WAMI global BCR-BIU-ACU trio variable, BBA, to the value provided as an argument. SYNTAX: WAM:BBA value EXAMPLE CALL: WAM:BBA 4 DESCRIPTION: The WAM:BBA command sets the WAMI global BBA number variable to the value provided as an argument. After execution of this command, all (in this embodiment of the WAMIL language) subsequent commands which require use of the BCR-BIU-ACU trio number, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script BCR-BIU-ACU trio number, will reference the new value. Execution of this command also disables any (in this WAMIL language embodiment) association which exists between this WAMI global variable and any WAMI VAR variable. OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution an BBA command: Set BCR-BIU-ACU Trio 4: BCR (BaseBand Combiner/Radio) BIU (Bus Interface Unit) ACU (Analog Conversion Unit) ERRORS: None. ALTERS: BBA DEFAULT VALUE: BBA is set to 1 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 1. SEE ALSO: WAM:INITIALIZE EXAMPLE: The following script will set the WAMIL script BBA variable to 4 and then execute a TI interface command: WAM:MSC 5 WAM:CELL 49 WAM:CONNECT TI WAM:BBA 4 TI:op:cell 49, bba 4 WAM:DISCONNECT TI WAM:ENDTEST BBALIST The BBALIST command can be embedded in the integration construct data structure according to the invention. PURPOSE: Declares to the WAM Interpreter, that a list of WAMI VARn BBA numbers will be supplied to the script. SYNTAX: WAM:BBALIST value EXAMPLE CALL: WAM:BBALIST 3 DESCRIPTION: The BBALIST command is a WAMIL declaration command which instructs the WAM Interpreter that a list of BBA numbers will be supplied to the script. This command executes the assignment of the BBA numbers provided to the WAMI VARn BBA List. Upon detection of this command, the WAM Interpreter will search the command line arguments for the BBA numbers. The total number of BBAs to assign is determined by the value argument of the command. This value declares to the WAM Interpreter the exact size of the BBA List. The BBA numbers within the BBA List can then be referenced within the script as WAMI VARn variables, according to their index position in the list. For example, BBAVAR2 refers to the second BBA number in the BBA List. The order of the BBA numbers provided determine the order of their placement within the BBA List. Up to 30 BBA numbers can be passed as an argument with this command. Therefore, the maximum acceptable size for the BBA List is 30. If a value larger than 30 is used, the WAM Interpreter will generate an error and script execution will be aborted. This command has a dual function and will initiate prompting by the WAMI GUI platform if the script is executed via the platform. For WAMI GUI platform information refer to the WAMI GUI PLATFORM section below. WAMI GUI PLATFORM: Prior to execution of a WAMIL script, the WAMI GUI platform searches the script for special commands. If a WAM:BBALIST command is encountered the WAMI GUI platform will prompt the user for the quantity of BBA numbers defined by the command argument value. Subsequent WAM:BBALIST commands encountered will not cause additional prompting. SCRIPTOR: If this command is deleted from the current script, the WAMIL Scriptor will delete all (in this embodiment of the WAMIL language) reference BBAVARn commands existing in the script also. The script WAMIglobal BBA variable will then be set to the default value of 1. The Scriptor will only (in this embodiment of the WAMIL language) allow insertion of one BBALIST command into the current script. OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a BBALIST command: Total Number of BBA List Values Set To 4 BBA List Values: 2 4 6 8 ERRORS: If a value larger than 30 is used the WAM Interpreter will generate an error and script execution will be aborted. Any references within a script to a WAMIVARn variable prior to the declaration of the list will generate a syntax error. If more than one BBALIST command is used in a WAMIL script, only (in this embodiment of the WAMIL language) the first list declaration is used, and therefore takes precedence. Thus subsequent BBALIST commands have no effect. ALTERS: WAMIVARn BBA List. DEFAULT VALUE: The WAMIVARn BBA List variable is set to an unknown state upon initial startup, and is of type integer. The WAM:INITIALIZE command does not reset this list. SEE ALSO: WAM:BBAVARn, WAM:INITIALIZE EXAMPLE: The following script sets the WAMIVARn BBA List length to 2, and executes a TI command for each BBA number in the list: WAM:MSC 5 WAM:CELL 49 WAM:BBALIST 2 WAM:CONNECT TI WAM:BBAVAR1 TI:op:cell 49, bba BBAVAR1 WAM:BBAVAR2 TI:op:cell 49, bba BBAVAR2 WAM:DISCONNECT TI WAM:ENDTEST BBAVAR The BBAVAR command can be embedded in the integration construct data structure according to the invention. PURPOSE: Declares to the WAM Interpreter, that a value for the WAMIVAR variable BBAVAR will be supplied to the script. SYNTAX: WAM:BBAVAR EXAMPLE CALL: WAM:BBAVAR DESCRIPTION: The WAM:BBAVAR command is a WAMIL declaration command which executes an assignment function. Upon detection of this command, the WAM Interpreter will search the command line arguments for a value to assign to the WAMI VAR variable BBAVAR. Like standard WAMI VAR variable declaration commands, the execution of this command also enables an association with the WAMI global BBA variable. Therefore, until the WAMI global BBA variable association is transferred to another WAMI VAR variable, or disabled, all (in this embodiment of the WAMIL language) references to the WAMI global BBA variable will use the BBAVAR variable value. For script syntax, until an actual BBA number is passed as an argument, when a BBAVAR command is used the BBA number within a script shall be referenced as BBAVAR from that point forward. This command has a dual function and will initiate prompting by the WAMI GUI platform if the script is executed via the platform. For WAMI GUI platform information refer to the WAMI GUI PLATFORM section below. WAMI GUI PLATFORM: Prior to execution of a WAMIL script, the WAMI GUI platform searches the script for special commands. If a WAM:BBAVAR is encountered the WAMI GUI platform will prompt the user for the script BBAVAR value. Subsequent AM:BBAVAR commands encountered will not cause additional prompting. SCRIPTOR: If a BBAVAR command is deleted from the current script, the Scriptor will prompt the user for a BBA number and then insert a WAM:BBA value command in place of the BBAVAR command deleted. OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution a BBAVAR command: Set BBA To Argument Value of 8 ERRORS: If no command line value has been provided, the WAM Interpreter will generate an error and script execution will be aborted. ALTERS: BBAVAR DEFAULT VALUE: BBAVAR is set to an unknown state upon initial startup, and is of type integer. The WAM:INITIALIZE command does not reset this WAMI VAR variable. SEE ALSO: WAM:BBA value EXAMPLE: The following script executes a TI command for the BBA number supplied: WAM:MSC 5 WAM:CELL 49 WAM:BBAVAR WAM:CONNECT TI TI:op:cell 49, bba BBAVAR WAM:DISCONNECT TI WAM:ENDTEST BBAVARn The BBAVARn command can be embedded in the integration construct data structure according to the invention. PURPOSE: Instructs the WAM Interpreter to set the WAMI global BBA variable to the value of the referenced WAMI VARn BBA variable, in position n, of the BBA List passed as an argument. SYNTAX: WAM:BBAVARn EXAMPLE CALL: WAM:BBAVAR2 DESCRIPTION: The WAM:BBAVARn command is an assignment command. This command can only (in this embodiment of the WAMIL language) be executed if a BBA List has been declared in the script. Upon execution, this command assigns a BBA List variable value to the WAMI global BBA variable. The value n, can (in this embodiment of the WAMIL language) be a valid index into the BBA List. any (in this WAMIL language embodiment) BBA List value can be assigned to the WAMI global BBA variable by execution of this command, where n is the BBA value location within the BBA List. Upon execution, the BBA number within a script is referenced as BBAVARn from that point forward. Like standard WAMI VARn variable assignment commands, the execution of this command also enables an association with the WAMI global BBA variable. Therefore, until the WAMI global BBA variable association is transferred to a WAMI VAR variable, or disabled, all (in this embodiment of the WAMIL language) references to the WAMI global BBA variable will use the BBAVARn variable value. For script syntax, until actual BBA List values are passed as an argument, when a BBAVARn command is used the BBA number within a script shall be referenced as BBAVARn from that point forward. OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a BBAVARn command, when a BBA List of 3 was previously declared, and the BBA List numbers passed as an argument are 2 4 6: Set BBA To BBAVAR2 Value Of 4 SCRIPTOR: If a BBAVARn command is deleted from the current script, the Scriptor will prompt the user for a BBA number and then insert a WAM:BBA value command in place of the BBAVARn command deleted. ERRORS: An invalid BBAVARn command used within a script, where n refers to a BBA List index outside the list range, will generate an error. Script execution will then be aborted. If a BBAVARn command is used within a script in which no BBA List has been declared, the WAM Interpreter will generate an error and terminate execution of the script. ALTERS: BBA DEFAULT VALUE: None (in this WAMIL language embodiment). SEE ALSO: WAM:BBA value, WAM:BBALIST value EXAMPLE: The following script sets the WAMI VARn BBA List length to 2, and executes a TI command for each BBA number in the list: WAM:MSC 5 WAM:CELL 49 WAM:BBALIST 2 WAM:CONNECT TI WAM:BBAVAR1 TI:op:cell 49, bba BBAVAR1 WAM:BBAVAR2 TI:op:cell 49, bba BBAVAR2 WAM:DISCONNECT TI WAM:ENDTEST CAT The CAT command can be embedded in the integration construct data structure according to the invention. PURPOSE: Changes the WAMI global clock and tone board number variable, CAT, to the value provided as an argument. SYNTAX: WAM:CAT value EXAMPLE CALL: WAM:CAT 6 DESCRIPTION: The WAM:CAT command sets the WAMI global CAT variable to the value provided as an argument. After execution of this command, all (in this embodiment of the WAMIL language) subsequent commands which require use of the clock and tone board number, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script clock and tone board number, will reference the new value. Execution of this command also disables any (in this WAMIL language embodiment) association which exists between this WAMI global variable and any WAMI VAR variable. OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution a CAT command: Set Clock and Tone Board 6 ERRORS: None. ALTERS: CAT DEFAULT VALUE: CAT is set to 0 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 0. SEE ALSO: WAM:INITIALIZE EXAMPLE: The following script lines set the WAMIL script CAT variable to 6 and then execute a TI interface command: WAM:CELL 49 WAM:CAT 6 TI:op:cell 49, cat 6 CATLIST The CATLIST command can be embedded in the integration construct data structure according to the invention. PURPOSE: Declares to the WAM Interpreter, that a list of WAMI VARn CAT numbers will be supplied to the script. SYNTAX: WAM:CATLIST value EXAMPLE CALL: WAM:CATLIST 3 DESCRIPTION: The CATLIST command is a WAMIL declaration command which instructs the WAM Interpreter that a list of CAT numbers will be supplied to the script. This command executes the assignment of the CAT numbers provided to the WAMI VARn CAT List. Upon detection of this command, the WAM Interpreter will search the command line arguments for the CAT numbers. The total number of CATs to assign is determined by the value argument of the command. This value declares to the WAM Interpreter the exact size of the CAT List. The CAT numbers within the CAT List can then be referenced within the script as WAMI VARn variables, according to their index position in the list. For example, CATVAR2 refers to the second CAT number in the CAT List. The order of the CAT numbers provided determine the order of their placement within the CAT List. Up to 10 CAT numbers can be passed as an argument with this command. Therefore, the maximum acceptable size for the CAT List is 10. If a value larger than 10 is used the WAM Interpreter will generate an error and script execution will be aborted. This command has a dual function and will initiate prompting by the WAMI GUI platform if the script is executed via the platform. For WAMI GUI platform information refer to the WAMI GUI PLATFORM section below. WAMI GUI PLATFORM: Prior to execution of a WAMIL script, the WAMI GUI platform searches the script for special commands. If a WAM:CATLIST command is encountered the WAMI GUI platform will prompt the user for the quantity of CAT numbers defined by the command argument value. Subsequent WAM:CATLIST commands encountered will not cause additional prompting. SCRIPTOR: If this command is deleted from the current script, the WAMIL Scriptor will delete all (in this embodiment of the WAMIL language) reference CATVARn commands existing in the script also. The script WAMI global CAT variable will then be set to the default value of 0. The Scriptor will only (in this embodiment of the WAMIL language) allow insertion of one CATLIST command into the current script. OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a CATLIST command: Total Number of CAT List Values Set To 3 CAT List Values: 0 6 7 ERRORS: If a value larger than 10 is used the WAM Interpreter will generate an error and script execution will be aborted. Any references within a script to a WAMI VARn variable prior to the declaration of the list will generate a syntax error. If more than one CATLIST command is used in a WAMIL script, only (in this embodiment of the WAMIL language) the first list declaration is used, and therefore takes precedence. Thus subsequent CATLIST commands have no effect. ALTERS: WAMI VARn CAT List. DEFAULT VALUE: The WAMI VARn CAT List variable is set to an unknown state upon initial startup, and is of type integer. The WAM:INITIALIZE command does not reset this list. SEE ALSO: WAM:CATVARn, WAM:INITIALIZE EXAMPLE: The following script sets the WAMI VARn CAT List length to 2, and executes a TI command for each CAT number in the list: WAM:MSC 5 WAM:CELL 49 WAM:CATLIST 2 WAM:CONNECT TI WAM:CATVAR1 TI:op:cell 49, cat CATVAR1 WAM:CATVAR2 TI:op:cell 49, cat CATVAR2 WAM:DISCONNECT TI WAM:ENDTEST CATVARn The CATVARn command can be embedded in the integration construct data structure according to the invention. PURPOSE: Instructs the WAM Interpreter to set the WAMI global CAT variable to the value of the referenced WAMI VARn CAT variable, in position n, of the CAT List passed as an argument. SYNTAX: WAM:CATVARn EXAMPLE CALL: WAM:CATVAR2 DESCRIPTION: The WAM:CATVARn command is an assignment command. This command can only (in this embodiment of the WAMIL language) be executed if a CAT List has been declared in the script. Upon execution, this command assigns a CAT List variable value to the WAMI global CAT variable. The value n, can (in this embodiment of the WAMIL language) be a valid index into the CAT List. any (in this WAMIL language embodiment) CAT List value can be assigned to the WAMI global CAT variable by execution of this command, where n is the CAT value location within the CAT List. Upon execution, the CAT number within a script is referenced as CATVARn from that point forward. Like standard WAMI VARn variable assignment commands, the execution of this command also enables an association with the WAMI global CAT variable. Therefore, until the WAMI global CAT variable association is transferred to a WAMI VAR variable, or disabled, all (in this embodiment of the WAMIL language) references to the WAMI global CAT variable will use the CATVARn variable value. For script syntax, until actual CAT List values are passed as an argument, when a CATVARn command is used the CAT number within a script shall be referenced as CATVARn from that point forward. OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a CATVARn command, when a CAT List of 2 was previously declared, and the CAT List numbers passed as an argument are 6 7: Set CAT To CATVAR2 Value Of 7 SCRIPTOR: If a CATVARn command is deleted from the current script, the Scriptor will prompt the user for a CAT number and then insert a WAM:CAT value command in place of the CATVARn command deleted. ERRORS: An invalid CATVARn command used within a script, where n refers to a CAT List index outside the list range, will generate an error. Script execution will then be aborted. If a CATVARn command is used within a script in which no CAT List has been declared, the WAM Interpreter will generate an error and terminate execution of the script. ALTERS: CAT DEFAULT VALUE: None (in this WAMIL language embodiment). SEE ALSO: WAM:CAT value, WAM:CATLIST value EXAMPLE: The following script sets the WAMI VARn CAT List length to 2, and executes a TI command for each CAT number in the list: WAM:MSC 5 WAM:CELL 49 WAM:CATLIST 2 WAM:CONNECT TI WAM:CATVAR1 TI:op:cell 49, cat CATVAR1 WAM:CATVAR2 TI:op:cell 49, cat CATVAR2 WAM:DISCONNECT TI WAM:ENDTEST CCC The CCC command can be embedded in the integration construct data structure according to the invention. PURPOSE: Changes the WAMI global CDMA Cluster Controller number variable, CCC, to the value provided as an argument. SYNTAX: WAM:CCC value EXAMPLE CALL: WAM:CCC 2 DESCRIPTION: The WAM:CCC command sets the WAMI global CCC number variable to the value provided as an argument. After execution of this command, all (in this embodiment of the WAMIL language) subsequent commands which require use of the CDMA Cluster Controller number, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script CDMA Cluster Controller number, will reference the new value. Execution of this command also disables any (in this WAMIL language embodiment) association which exists between this WAMI global variable and any WAMI VAR variable. OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution a CCC command: Set CCC 2 ERRORS: None. ALTERS: CCC DEFAULT VALUE: CCC is set to 1 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 1. SEE ALSO: WAM:INITIALIZE EXAMPLE: The following script will set the WAMIL script CCC variable to 2 and then execute a TI interface command: WAM:CELL 49 WAM:CCC 2 TI:op:cell 49, ccc 2, ccu 1 CCCLIST The CCCLIST command can be embedded in the integration construct data structure according to the invention. PURPOSE: Declares to the WAM Interpreter, that a list of WAMI VARn CCC numbers will be supplied to the script. SYNTAX: WAM:CCCLIST value EXAMPLE CALL: WAM:CCCLIST 3 DESCRIPTION: The CCCLIST command is a WAMIL declaration command which instructs the WAM Interpreter that a list of CCC numbers will be supplied to the script. This command executes the assignment of the CCC numbers provided to the WAMI VARn CCC List. Upon detection of this command, the WAM Interpreter will search the command line arguments for the CCC numbers. The total number of CCCs to assign is determined by the value argument of the command. This value declares to the WAM Interpreter the exact size of the CCC List. The CCC numbers within the CCC List can then be referenced within the script as WAMI VARn variables, according to their index position in the list. For example, CCCVAR2 refers to the second CCC number in the CCC List. The order of the CCC numbers provided determine the order of their placement within the CCC List. Up to 30 CCC numbers can be passed as an argument with this command. Therefore, the maximum acceptable size for the CCC List is 30. If a value larger than 30 is used the WAM Interpreter will generate an error and script execution will be aborted. This command has a dual function and will initiate prompting by the WAMI GUI platform if the script is executed via the platform. For WAMI GUI platform information refer to the WAMI GUI PLATFORM section below. WAMI GUI PLATFORM: Prior to execution of a WAMIL script, the WAMI GUI platform searches the script for special commands. If a WAM:CCCLIST command is encountered the WAMI GUI platform will prompt the user for the quantity of CCC numbers defined by the command argument value. Subsequent WAM:CCCLIST commands encountered will not cause additional prompting. SCRIPTOR: If this command is deleted from the current script, the WAMIL Scriptor will delete all (in this embodiment of the WAMIL language) reference CCCVARn commands existing in the script also. The script WAMI global CCC variable will then be set to the default value of 1. The Scriptor will only (in this embodiment of the WAMIL language) allow insertion of one CCCLIST command into the current script. OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a CCCLIST command: Total Number of CCC List Values Set To 3 CCC List Values: 2 4 6 ERRORS: If a value larger than 30 is used the WAM Interpreter will generate an error and script execution will be aborted. Any references within a script to a WAMI VARn variable prior to the declaration of the list will generate a syntax error. If more than one CCCLIST command is used in a WAMIL script, only (in this embodiment of the WAMIL language) the first list declaration is used, and therefore takes precedence. Thus subsequent CCCLIST commands have no effect. ALTERS: WAMI VARn CCC List. DEFAULT VALUE: The WAMI VARn CCC List variable is set to an unknown state upon initial startup, and is of type integer. The WAM:INITLALIZE command does not reset this list. SEE ALSO: WAM:CCCVARn, WAM:INITIALIZE EXAMPLE: The following script sets the WAMI VARn CCC List length to 2, and executes a TI command for each CCC number in the list: WAM:MSC 5 WAM:CELL 49 WAM:CCCLIST 2 WAM:CONNECT TI WAM:CCCVAR1 TI:op:cell 49, ccc CCCVAR1, ccu 1 WAM:CCCVAR2 TI:op:cell 49, ccc CCCVAR2, ccu 1 WAM:DISCONNECT TI WAM:ENDTEST CCCVAR The CCCVAR command can be embedded in the integration construct data structure according to the invention. PURPOSE: Declares to the WAM Interpreter, that a value for the WAMI VAR variable CCCVAR will be supplied to the script. SYNTAX: WAM:CCCVAR EXAMPLE CALL: WAM:CCCVAR DESCRIPTION: The WAM:CCCVAR command is a WAMIL declaration command which executes an assignment function. Upon detection of this command, the WAM Interpreter will search the command line arguments for a value to assign to the WAMI VAR variable CCCVAR. Like standard WAMI VAR variable declaration commands, the execution of this command also enables an association with the WAMI global CCC variable. Therefore, until the WAMI global CCC variable association is transferred to another WAMI VAR variable, or disabled, all (in this embodiment of the WAMIL language) references to the WAMI global CCC variable will use the CCCVAR variable value. For script syntax, until an actual CCC number is passed as an argument, when a CCCVAR command is used the CCC number within a script shall be referenced as CCCVAR from that point forward. This command has a dual function and will initiate prompting by the WAMI GUI platform if the script is executed via the platform. For WAMI GUI platform information refer to the WAMI GUI PLATFORM section below. WAMI GUI PLATFORM: Prior to execution of a WAMIL script, the WAMI GUI platform searches the script for special commands. If a WAM:CCCVAR is encountered the WAMI GUI platform will prompt the user for the script CCCVAR value. Subsequent WAM:CCCVAR commands encountered will not cause additional prompting. SCRIPTOR: If a CCCVAR command is deleted from the current script, the Scriptor will prompt the user for a CCC number and then insert a WAM:CCC value command in place of the CCCVAR command deleted. OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution a CCCVAR command: Set CCC To Argument Value of 8 ERRORS: If no command line value has been provided, the WAM Interpreter will generate an error and script execution will be aborted. ALTERS: CCCVAR DEFAULT VALUE: CCCVAR is set to an unknown state upon initial startup, and is of type integer. The WAM:INITIALIZE command does not reset this WAMI VAR variable. SEE ALSO: WAM:CCC value EXAMPLE: The following script executes a TI command for the CCC number supplied: WAM:MSC 5 WAM:CELL 49 WAM:CCCVAR WAM:CONNECT TI TI:op:cell 49, ccc CCCVAR, ccu 1 WAM:DISCONNECT TI WAM:ENDTEST CCCVARn The CCCVARn command can be embedded in the integration construct data structure according to the invention. PURPOSE: Instructs the WAM Interpreter to set the WAMI global CCC variable to the value of the referenced WAMI VARn CCC variable, in position n, of the CCC List passed as an argument. SYNTAX: WAM:CCCVARn EXAMPLE CALL: WAM:CCCVAR2 DESCRIPTION: The WAM:CCCVARn command is an assignment command. This command can only (in this embodiment of the WAMIL language) be executed if a CCC List has been declared in the script. Upon execution, this command assigns a CCC List variable value to the WAMI global CCC variable. The value n, can (in this embodiment of the WAMIL language) be a valid index into the CCC List. Any (in this WAMIL language embodiment) CCC List value can be assigned to the WAMI global CCC variable by execution of this command, where n is the CCC value location within the CCC List. Upon execution, the CCC number within a script is referenced as CCCVARn from that point forward. Like standard WAMI VARn variable assignment commands, the execution of this command also enables an association with the WAMI global CCC variable. Therefore, until the WAMI global CCC variable association is transferred to a WAMI VAR variable, or disabled, all (in this embodiment of the WAMIL language) references to the WAMI global CCC variable will use the CCCVARn variable value. For script syntax, until actual CCC List values are passed as an argument, when a CCCVARn command is used the CCC number within a script shall be referenced as CCCVARn from that point forward. OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a CCCVARn command, when a CCC List of 3 was previously declared, and the CCC List numbers passed as an argument are 2 4 6: Set CCC To CCCVAR2 Value Of 4 SCRIPTOR: If a CCCVARn command is deleted from the current script, the Scriptor will prompt the user for a CCC number and then insert a WAM:CCC value command in place of the CCCVARn command deleted. ERRORS: An invalid CCCVARn command used within a script, where n refers to a CCC List index outside the list range, will generate an error. Script execution will then be aborted. If a CCCVARn command is used within a script in which no CCC List has been declared, the WAM Interpreter will generate an error and terminate execution of the script. ALTERS: CCC DEFAULT VALUE: None (in this WAMIL language embodiment). SEE ALSO: WAM:CCC value, WAM:CCCLIST value EXAMPLE: The following script sets the WAMI VARn CCC List length to 2, and executes a TI command for each CCC number in the list: WAM:MSC 5 WAM:CELL 49 WAM:CCCLIST 2 WAM:CONNECT TI WAM:CCCVAR1 TI:op:cell 49, ccc CCCVAR1, ccu 1 WAM:CCCVAR2 TI:op:cell 49, ccc CCCVAR2, ccu 1 WAM:DISCONNECT TI WAM:ENDTEST CCU The CCU command can be embedded in the integration construct data structure according to the invention. PURPOSE: Changes the WAMI global CDMA Channel Unit number variable, CCU, to the value provided as an argument. SYNTAX: WAM:CCU value EXAMPLE CALL: WAM:CCU 2 DESCRIPTION: The WAM:CCU command sets the WAMI global CCU number variable to the value provided as an argument. After execution of this command, all (in this embodiment of the WAMIL language) subsequent commands which require use of the CDMA Channel Unit number, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script CDMA Channel Unit number, will reference the new value. Execution of this command also disables any (in this WAMIL language embodiment) association which exists between this WAMI global variable and any WAMI VAR variable. OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution a CCU command: Set CCU 2 ERRORS: None. ALTERS: CCU DEFAULT VALUE: CCU is set to 1 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 1. SEE ALSO: WAM:INITIALIZE EXAMPLE: The following script will set the WAMIL script CCU variable to 2 and then execute a TI interface command: WAM:CELL 49 WAM:CCU 2 TI:op:cell 49, ccc 1, ccu 2 CCULIST The CCULIST command can be embedded in the integration construct data structure according to the invention. PURPOSE: Declares to the WAM Interpreter, that a list of WAMI VARn CCU numbers will be supplied to the script. SYNTAX: WAM:CCULIST value EXAMPLE CALL: WAM:CCULIST 3 DESCRIPTION: The CCULIST command is a WAMIL declaration command which instructs the WAM Interpreter that a list of CCU numbers will be supplied to the script. This command executes the assignment of the CCU numbers provided to the WAMI VARn CCU List. Upon detection of this command, the WAM Interpreter will search the command line arguments for the CCU numbers. The total number of CCUs to assign is determined by the value argument of | ||||||