US 6,658,646 B1Grant
Multiple interface scripting language
Issue Date:2003-12-02
•26 Claims
•4 Drawing Sheets
Abstract
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.
Metadata
Assignee
- Lucent Technologies Inc.
Inventor
- Gaspar Hernandez, III
Application Information
Application Number:US 09/407,890
Filing Date:1999-09-29
Priority Date:1999-09-29
Art Unit:7
Classifications
IPC:
G06F 944
Field of Search:
717141
Patent Drawings (4 sheets)
Description
FIELD OF THE INVENTION
[0002] The invention is directed toward a scripting language especially well adapted for writing scripts that (when run on a machine) generate, e.g., a liaison interface between a user and an existing user interface, and more particularly to such a scripting language that includes an integration construct data structure that permits commands from discrete user interfaces to be integrated in a single script (that when executed by a machine isolate the user from direct interaction with the discrete interfaces).
BACKGROUND OF THE INVENTION
[0003] A script is a sequence of commands that are to be interpreted, i.e., executed by a program running on a processor, as contrasted with a program that is compiled into the machine code of a processor and then directly executed by that processor. A script can be generated using a text editor or a Graphical User Interface (GUI) adapted to the scripting language.
[0004] Large systems often include monitoring systems that permit one or more users to monitor the performance of the system in general, and to specifically monitor the state of one or more parameters of the large system. In some instances, the manner in which the monitoring system delivers information to the user can be a burden.
[0005] An example of the large system discussed above is a wireless communication network that provides wireless communications service to a wireless unit that is situated within a geographic region. A Mobile Switching Center (MSC) is responsible for, among other things, establishing and maintaining calls between wireless units and calls between a wireless unit and a wireline unit . As such, the MSC interconnects the wireless units within its geographic region with a public switched telephone network (PSTN). The geographic area serviced by the MSC is divided into spatially distinct areas called “cells.” In a schematic block diagram, each cell could be schematically represented by one hexagon in a honeycomb pattern. But, in practice, each cell has an irregular shape that depends on the topography of the terrain surrounding the cell. Typically, each cell contains a base station, which comprises the radios and antennas that the base station uses to communicate with the wireless units in that cell. The base stations also comprise the transmission equipment that the base station uses to communicate with the MSC in the geographic area via communication links. One cell site may sometimes provide coverage for several sectors. Here, cells and sectors are referred to interchangeably.
[0006] In a wireless cellular communications system, a base station and a wireless unit communicate voice and/or data over a forward link and a reverse link, wherein the forward link carries communication signals over at least one forward channel from the base station to the wireless unit and the reverse link carries communication signals on at least one reverse channel from the wireless unit to the base station. There are many different schemes for determining how wireless units and base stations communicate in a cellular communications system. For example, wireless communications links between the wireless units and the base stations can be defined according to different radio protocols, including time-division multiple access (TDMA), Frequency Division Multiple Access (FDMA), Code Division Multiple Access (CDMA) and others.
[0007] Within the geographic region, the MSC switches a call between base stations in real time as the wireless unit moves between cells, referred to as a handoff. Currently, in FDMA, TDMA, CDMA and GSM, cell site planning to determine the geographic coverage for a cell is a manually intensive task that needs constant adjustment. In planning a cell, the topology of the geographic area and a suitable antenna site is selected based on availability and zoning rules. Such a selection is typically not optimal but adequate. Drive tests and manually collecting signaling data are then performed mostly on the perimeter of the coverage area. Transmit and receive antennas and power are then adjusted in a manually iterative manner to improve the call quality. Sometimes, frequencies are swapped with neighbor cells and/or transmit power is readjusted to improve the coverage. Over time, the cell site engineers review customer complaints and cell site dropped call reports and again try to manually optimize the RF performance.
[0008] Lucent Technologies Inc. has developed a monitoring system that a user can use to change parameters of the wireless communication system as well as to extract data about it. This monitoring system can generate the TIpdunix (TI) interface, the Status Display Page (SDP) interface and/or the AUTOPLEX Recent Change & Verification Database (APXRCV) interface. These interfaces can be used individually. But typically, information extracted from one of the interfaces is used to make a decision to use a second one of the interfaces in one way or another. To use an interface, a user must start a discrete process. In a windows-based environment, each interface session has its own window.
[0009] These discrete or non-integrated interfaces to the monitoring systems pose problems for the user. Each interface has its own set of commands as well as formats for returning information to the user. These command sets and display formats are extensive. This burdens the user's memory. Moreover, the SDP interface returns information in a manner that requires the user to interpret a combination of the foreground and background colors, as well as whether the associated text is blinking or not, in a particular region of the screen in order to determine the state of a component of a large system.
[0010] Based upon the information extracted from a first interface, the user must make a decision about whether it is appropriate to use a second interface and if so, the user must appropriately form the command to be submitted. Often, the first interface is used merely to verify that the large system is operating correctly. The user must inspect the data returned by the first interface to confirm that it is consistent with normal operation of the large system. If there is some discrepancy, it must be recognized by the user. Then, the user must determine the problem that is indicated by the discrepancy. Then, the user must take appropriate action, typically via one of the other interfaces.
[0011] While the user has the responsibility of confirming via one of the interfaces that the operation of the large system is normal, the user is essentially a prisoner to that interface. The user must continually confirm that the operation of the large system is normal by repeatedly extracting data from the large system. If the user fails to recognize a discrepancy in the data that is returned, then the user will have failed to recognize that there is a problem for which action must be taken.
[0012] In another instance, the user might use one of the interfaces to change a parameter in the large system. To confirm that the parameter change has taken effect, the user typically has to use a second interface. But there is typically a delay between the requested change of parameter and the time at which it takes effect in the large system.
[0013] To confirm that the change has taken effect, the user must repeatedly extract information from the large system via the second interface. Again, the user becomes a prisoner of the second interface until the user recognizes something in the data returned by the second interface that indicates the desired change has taken place.
[0014] Again, the TI, SDP and APXRCV interfaces each require a great deal of direct user interaction. An example of this is depicted in the unified modeling diagram of FIG. 1. FIG. 1 depicts interactions between a user 101 and a monitoring system 304 (to be discussed in more detail below concerning FIG. 3), to be discussed in more detail below. Communication from the user originate from a line 102, while communications from the monitoring system 304 originate from a line 104. The monitoring system 304 can generate the TI, SDP and/or APXRCV interfaces discussed above.
[0015] In the unified modeling diagram of FIG. 1, a user desires the result of executing an inventory command via the TI interface. To do so, the user might have to manipulate a field in the APX database in order to enable the use of an inventory command of the TI interface. First, the user must initiate an interface session with the APXRCV interface.
[0016] Then, the user must make a backup copy of the APXRCV database for the cell in consideration. Making the backup copy represents the first action requested by the user and it is requested via the APXRCV interface, i.e., the first interface. This is a prudent step to prevent unwanted changes to the database. Then, the user must request data from a particular field within the database. This represents the first data request by the user. Again, it is requested via the first interface. This also requires the user to remember the relevant command and its arguments. Then, the user must wait to find out if the data request is successful or if it failed.
[0017] If the first data request is successful, then the user must evaluate the data returned from the field in the database and determine whether it is necessary to modify that data so that the later TI command will be enabled. If the content of the field in the database must be altered, then the user must remember the relevant command and its arguments as well as construct and submit the command. In other words, the user must request a second action, again, via the APXRCV interface. Once the particular field in the database stores the desired value, the user must initiate a TI session. Then, the user must determine whether the TI session has been successfully established. If not, then the user must restore the APXRCV database to its original values. Otherwise, the user must remember the desired TI command and its arguments. In other words, the user must request a third action, but this time it is requested via a second interface (the TI interface). Then the user should terminate the TI session. Then the user should restore the previous values of the APXRCV database, i.e., request a fourth action, again, via the first interface.
SUMMARY OF THE INVENTION
[0018] A motivation, among others, for the invention is a recognition that the amount of direct user interaction with the monitoring systems can be greatly reduced by providing a liaison interface between the user and the existing interfaces by way of running a script on a machine, e.g., as a retrofit liaison interface. This solves the excessive direct user interaction problems suffered by the known interfaces while avoiding the great costs associated with revising the interfaces per se. The liaison interface automatically interacts with the existing interfaces, i.e., the liaison interface interacts with the existing interfaces without the direct involvement of the human user.
[0019] The invention, in part, provides a scripting language for writing scripts that when run on a machine generate such a liaison interface.
[0020] The invention, in part, provides 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.
[0021] The invention, in part, also provides a computer-readable medium embodied script that includes at least two of the integration construct data structures.
[0022] The invention, at least in part, is embodied by providing a computer-readable medium having embodied thereon a script to be processed by a machine connected to a system, the system having at least a first interface for interacting with a user, the computer-readable-medium-embodied script causing the machine to generate a second interface for interacting differently with the user than the first interface, each of the interfaces having at least a set of commands. Such a computer-readable-medium-embodied script comprises: a sequence of executable statements including at least two integration constructs. Each of the integration constructs includes: a first field to identify one of the first interface and the second interface; and a second field to identify at least a command from the corresponding set for the interface identified in the first field.
[0023] The invention is also embodied, at least in part, by providing an integration construct data structure readable by a machine, the machine operating upon commands from at least two domains, the integration construct associating a command with a domain where the command is valid. Such an integration construct comprises: a first data object to identify at least a command; and a second data object, linked to the first data object, to identify one of at least a first domain and a second domain as the domain in which the command of the first data object is valid.
[0024] The invention is also embodied, at least in part, by providing a method of parsing an executable statement, the executable statement being readable by a machine, the machine operating upon commands from at least two domains. Such a method comprises: examining the executable statement to identify one of at least a first domain and a second domain as the domain in which a command embedded in the executable statement is valid; and examining said executable statement to identify at least said command.
[0025] Objectives, features and advantages of the invention will be more fully apparent from the following detailed description of the preferred embodiments, the appended claims and the accompanying drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
[0026] The accompanying drawings are intended to depict example embodiments of the invention and should not be interpreted to limit the scope thereof.
[0027] FIG. 1 is a unified modeling diagram for interactions between a human user and Background Art interfaces to a Background Art monitoring system.
[0028] FIG. 2 is a unified modeling diagram for interactions between a liaison interface according to the invention and Background Art interfaces to a Background Art monitoring system, as well as interactions between the liaison interface and a user.
[0029] FIG. 3 depicts the system in which the device according to the invention forms a part.
[0030] FIGS. 4A and 4B are schematic depictions of an integration construct data structure of the scripting language according to the invention.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0031] FIG. 3 depicts an overall system 300 of which the liaison interface 306 (that is preferably generated using the scripting language according to the invention) forms a part. The other parts of the overall system 300 are the large system 302 and the monitoring system 304, examples of each of which were discussed above in the Background Section. Again, an example of the large system 302 is a wireless telephony system and an example of the interfaces generated by the monitoring system 304 are the TIpdunix (TI) interface, the Status Display Page (SDP) interface and/or the AUTOPLEX Recent Change & Verification DataBase (APXRCV) interface, all of which are marketed by Lucent Technologies Inc.
[0032] A monitoring system 304 includes processing circuitry 308, a part of which is a video display driver circuit card 310. The video card 310 drives a video display device (VDD) 312. In the case of generating the SDP interface, the VDD 312 is driven with non-text, typically hexadecimal code, display-generation data supplied over a connection 314. An input device in the form of a keyboard 316 is connected to the processing circuitry 308 via a signal line 318.
[0033] The liaison interface 306 (that is preferably generated using the scripting language according to the invention) includes a processor 320, an output device in the form of a video display device (VDD) 328 connected via a signal line 330, and an input device preferably in the form of a keyboard 332 connected via a signal line 334. The processor 320 has a memory 326 for storing a program or script that causes the processor 320 to generate the liaison interface 306 according to the invention. The processor 320 can communicate with, e.g., an input/output (I/O) port of the processing circuitry 308 via a bidirectional link 324.
[0034] The scripting language according to the invention has been disclosed in terms of a specific embodiment of the Wireless Automation Manager Interface Language (WAMIL). But many variations of the WAMIL language, having different combinations of commands, IF-construct elements and (optionally) WHILE-construct elements, as well as other languages, could embody the scripting language according to the invention.
[0035] An embodiment of the interpreter for the scripting language according to the invention, for example, has been written in two languages, the Tool Command Language (TCL) and C. Of the portion of the code directed toward dealing with the SDP interface, about 10% is written in C to take advantage of the hexadecimal and bits translation capability of C.
[0036] The computer-readable memory 326 can include RAM, ROM, a fixed hard disk drive, and/or a removable storage medium for a non-fixed disk drive such as a floppy disk or a CDROM. The program which causes the processor 320 to generate the liaison interface 306 according to the invention can be downloaded to the processor 320 from the remote host 336 over the optional connection 338. As the program is downloaded through the optional connection 338, the computer-readable medium in which the program is embodied takes the form of a propagated signal.
[0037] Generation of the liaison interface (using scripts written in the scripting language according to the invention) involves many sorting and comparison operations as well as accesses to look-up tables (LUTs). As such, the processor 320 should be of sufficient processing power to assure reasonably quick results. Examples of adequate processors are those from the Pentium family of processors marketed by Intel Inc.
[0038] FIG. 2 is a unified modeling diagram depicting an example of interactions by a liaison interface 306 generated by a script preferably written in the scripting language according to the invention. In FIG. 2, communications from the liaison interface 306 originate from a line 204. The liaison 306 interacts with a user 201, be it a human user, a calling script user or calling program user. Communications from the user 201 originate from a line 202. The liaison interface 306 also interacts with the monitoring system 304. Communications from the monitoring system 304 emanate from a line 206. As will be discussed below, interposing the liaison interface 306 between the user and the monitoring system 304 greatly reduces the amount of direct interaction that the user must have with any interface.
[0039] FIG. 2 depicts interactions necessary to achieve the same result as in the example of FIG. 1. Again, the user 201 desires the result of executing an inventory command via the TI interface without having to be concerned with checking if certain parameters are in their required states. But in FIG. 2, only two interactions, namely 208 and 226, require direct interaction by the user. The other fourteen actions or interactions involve only the liaison 306 or the liaison 306 and the monitoring system 304, respectively. At Item 207, the user must construct a request for a result and submit it to the liaison interface 306 at element 208. The phrase “request a result” is intended to indicate that the user runs a script to produce the desired result by operation of the liaison interface 306.
[0040] The desired result can simply be a notification that the script has run successfully. Alternatively, the indication that the script has run successfully can be communicated in the form of a display of a desired parameter of the system. At Item 228, the user must review this prompt to confirm that the result was accomplished or to make use of the result.
[0041] The WAMIL language includes commands and statements that are elements of IF-constructs and while-constructs. A WAMIL command or integration construct data structure has the format of “interface:command,” e.g., “TI:OP:CELL, NUMERAL,” “WAM:CONNECT SDP,” or “WAM:GETSDP.” As depicted in FIG. 4A, a WAMIL command 400 preferably has a first field 402 that identifies an interface and a second field 406 that identifies a command. The interface identified by the first field 402 is the interface in which the command of the second field 406 is valid. Preferably, the first field 402 precedes, or is a header for, the second field 406 and is separated by a third field 404, e.g., an alphanumeric character such as a colon (:) 410 (FIG. 4B). Alternatively, the second field 406 could precede the first field 402.
[0042] All WAMIL commands, i.e., WAM:COMMAND, can (in this embodiment of the WAMIL language) be uppercase letters. Also, each alphanumeric text string in the field 402, e.g., TI, can (in this embodiment of the WAMIL language) be in uppercase letters. But commands from other interfaces can be in lowercase letters. For information, refer to the WAM Interface Commands section below.
[0043] The invention has been described, for convenience, in terms of the TI interface, the SDP interface and/or the APXRCV interface to the monitoring system for the large wireless system described in the Background Section above. However, the scripting language according to the invention is applicable to integrate commands of discrete interfaces from other domains or to write scripts to generate liaison interfaces to other user interfaces such as those found in the air traffic control arts, train and subway control arts, chemical processing plant control arts, power generation plant control arts, etc. Again, common characteristics of these interfaces include (1) that they hold the user captive by requiring a great deal of direct user interaction and (2) that they are mature products for which research and development efforts have been greatly diminished, making substantive redesigns, e.g., software rewrites, (to obtain more user-friendly output) prohibitively expensive. Thus, a liaison interface written using the scripting language according to the invention does not disturb the existing monitoring system and yet achieves a desired goal of greatly reducing the amount of direct interaction between the user and user-interface without redesigning the software of the dedicated non-text-variable-output systems.
[0044] Details of the Liaison Interface are contained in a first copending U.S. patent application entitled “Liaison Interface,” by the same inventor, Gaspar Hernandez, III, filed on the same date, Sep. 29, 1999, that is assigned to the same assignee, Lucent Technologies Inc. The entire contents of this first copending application are hereby incorporated by reference.
[0045] One of the commands in the WAMIL scripting language is the “GETSDP” command. More details of this command can be found in a second copending U.S. patent application, entitled “Technology to Translate Non-Text Display Generation Data Representing An Indicator Into Text Variables,” by the same inventor, Gaspar Hernandez, III, filed on the same date, Sep. 29, 1999, that is assigned to the same assignee, Lucent Technologies Inc. The entire contents of this second copending application are hereby incorporated by reference.
[0046] The programmed processor 320 preferably has one or more programs to generate a script interpreter that will interpret each line in a script. The interpreter can be executed from a command line or by way of a Graphical User Interface (GUI). The program processor 320 preferably also includes a program to generate a scriptor by which a user can write a script and/or debug an existing script.
[0047] Details of a Scriptor and an Interpreter especially suited to the WAMIL language are contained in a third copending U.S. patent application entitled “Scriptor and Interpreter,” filed by the same inventor, Gaspar Hernandez, III, filed on the same date, Sep. 29, 1999, that is assigned to the same assignee, Lucent Technologies Inc. The entire contents of this third copending application are hereby incorporated by reference.
[0048] Details of a Comand Line Generator to ease the burden on a user represented by command line execution are contained in a fourth copending application, entitled “Command Line Generator,” by the same inventor, Gaspar Hernandez, III, filed on the same date, Sep. 29, 1999, that is assigned to the same assignee, Lucent Technologies Inc. The entire contents of this fourth copending application are hereby incorporated by reference.
[0049] Some example scripts written in the WAMIL language follow. After that discussions of the WAMIL Interpreter environment, WAMI key global variables, WAM VAR variables, WAM lists, control flow for WAMIL script execution and the WAM Linker are provided to help establish a context to appreciate the capabilities and flexibility of a script written in the WAMIL language. Then, a general discussion of the IF THEN ELSE type of IF-construct, the IF THENDO ELSEDO ENDIF type of IF-construct and the WHILE ENDWHILE variation of an IF-construct are presented, followed by a detailed glossary of commands that can be embedded in the integration construct data structure according to the invention. That will be followed by a detailed glossary of IF-construct elements. Then is general discussion of the Linker, followed by a detailed glossary of linker commands are presented.
[0050] An example of a script used to generate the liaison interface 306 that corresponds to the interactions depicted in FIG. 2 is listed below in Script #1.
| SCRIPT #1 |
[0051] Script #1 is written in the Wireless Automation Manager Interface Language (WAMIL). A brief discussion of the lines in the script will be presented.
[0052] 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.”
[0053] 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.
[0054] 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.
[0055] 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.
[0056] 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.
[0057] 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.
[0058] Another example script, namely Script #2, follows. Script #2 uses the SDP interface and the TI interface.
| SCRIPT #2 |
[0059] 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.
[0060] 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.
[0061] 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.
[0062] 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.
[0063] 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.
[0064] 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.
[0065] Line 39 of Script #2 terminates the TI interface session. Line 40 terminates the SDP interface session. Line 41 terminates execution of Script #2.
[0066] 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 |
[0067] 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 |
WAMIL Interpreter Environment
[0068] 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
[0069] Again, a WAMIL script is passed to an interpreter, preferably the WAM Interpreter (WAMI), for execution.
[0070] 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:
[0071] WAM21 AUTO1
WAMIL Script Output File
[0072] All WAMIL scripts generate an output file. all (in this embodiment of the WAMIL language) output files have a .rpt extension.
[0073] Default script output location is ˜myhome/WAMfiles/Scripts.dir, else -rpt switch is used.
[0074] WAM21 AUTO1 -rpt ˜some/place/else
[0075] Output files are overwritten unless the append option is specified as follows:
[0076] WAM21 AUTO1 -rpt ˜some/place/else -opt a -endopt
[0077] For example, the above script when executed as the script name AUTO1 would generate the following output:
[0078] Test Script Name: AUTO1
[0079] Test Script Location: /phoenix/h47/ghernand/WAMfiles/wam.wamil
[0080] Test Script Report Name: AUTO1
[0081] Test Script Report Location: phoenix/h47/ghernand/WAMfles/Scripts.dir
[0082] Test On MSC 5
[0083] FStart Test Cell: 49
[0084] Connect To TIpdunix on MSC 5
[0085] Executed TI: op:cell 49
[0086] op:cell 49
[0087] IP all specified cells ACT
[0088] M 45 OP:CELL 49 BBA 6, OOS, FRCELL, RMVD
[0089] 12/08/98 45 #073412
[0090] M 45 OP:CELL 49 CCC 6, ACTIVE
[0091] BLOCKING FROM CELL, NO ACU ON CCC SHELF
[0092] BLOCKING FROM SECTOR 3, NO BBA IN SERVICE
[0093] 12/08/98 45 #073414
[0094] M 45 OP:CELL 49 CCC 4, CCU 3, OOS, FRCELL, RMVD
[0095] 12/08/98 45 #073415
[0096] M 46 OP:CELL 49 PROG CONTROL OFF-NORMAL
[0097] INTERRUPTS INHIBITED:
[0098] CSC 0 PROCID:
[0099] MWPER
[0100] MPARF
[0101] NCIOCF
[0102] CPIST
[0103] CPIMS
[0104] CPUADRV
[0105] CPUMTX
[0106] ANTFT INHIBITED
[0107] OCFT INHIBITED
[0108] PLFT INHIBITED
[0109] TPFT INHIBITED
[0110] RTDIAG INHIBITED
[0111] 12/08/98 46 #073417
[0112] M 46 OP:CELL 49 COMPLETED
[0113] 12/08/98 46 #073418
[0114] M 46 OP:CELL 49 DL 0 CONNECTED
[0115] 12/08/98 46 #073427
[0116] M 46 OP:CELL 49 DL 1 CONNECTED
[0117] 12/08/98 46 #073428
[0118] M 46 OP:CELL 49 STATUS & CONTROLS
[0119] BOOT ALW, CP ALW, PH MON ALW, PH STATE ACTIVE, DL(S) UP
[0120] FORWARD SETUP CHANNEL CONTROL NORMAL (INH)
[0121] 12/08/98 46 #073430
[0122] Disconnect From TIpdunix on MSC 5
[0123] ENDTEST MSC 5 CELL 49
[0124] END OF TEST SCRIPT EXECUTION
WAMIL Commands Output
[0125] 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
[0126] 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
[0127] 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.
[0128] 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 |
Key Variables in a WAMIL Script
[0129] Key variables already exist with default values.
[0130] Interface commands reference key global variables.
[0131] WAM Interpreter commands alter, act upon, or perform functions based upon the current values of the key global variables.
[0132] 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
[0133] WAMI key global variables can be altered with WAM Interpreter assignment commands. An example script follows:
| MSC | CELL | |
|---|---|---|
Referencing WAMI Key global variables Within Strings
[0134] To reference a WAMI key global variable within a string the suffix VAR is added to the key global variable name.
[0135] WAM:PRINT The script CELL number is CELLVAR.
[0136] If CELL was set to the value of 49, the above would print to the WAMIL script output file as follows:
[0137] The script CELL number is 49.
WAM Interpreter Script Parsing & Execution
[0138] Each line of a WAMIL script is parsed and then executed. The interpreter parser and executor each have a four step process:
[0139] PARSER
[0140] 1) Check command syntax.
[0141] 2) Verify against key global variables if interface command.
[0142] 3) Check for Parser required flags or states.
[0143] 4) Set Parser & Executor required flags & states.
[0144] EXECUTOR
[0145] 1) Check for Executor required flags or states.
[0146] 2) Perform key global variable & keyword substitutions.
[0147] 3) Execute command.
[0148] 4) Set Parser & Executor required flags & states.
WAM Interpreter Keywords & Operators
[0149] 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 |
[0150] 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 | |
[0151] 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
[0152] 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.
[0153] 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
[0154] 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.
[0155] 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
[0156] 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 | |
|---|---|---|---|
[0157] The above script if named AUTO1 could be executed from the command line as follows:
[0158] WAM21 AUTO1 -cell 49
Inheritance
[0159] 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 |
|---|---|---|---|---|---|
[0160] The above script if named AUTO1 could be executed from the command line as follows:
[0161] WAM21 AUTO1 -ccc 2
Association Transfers
[0162] 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 |
[0163] 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 |
[0164] The above script if named AUTO1 could be executed from the command line as follows:
[0165] WAM21 AUTO1 -msc 5 -cell 49 -ccc 2 -ccu 4
Referencing WAMI VAR Variables Within Strings
[0166] 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.
[0167] For example, the following example script lines print the value of CELL which has been assigned 49.
[0168] WAM:CELL 49
[0169] WAM:PRINT The script CELL number is CELLVAR.
[0170] If the cell number is passed as an argument during command line execution, for example -cell 101, the following script lines,
[0171] WAM:CELLVAR
[0172] WAM:PRINT The script CELL number is CELLVAR.
[0173] will generate output to the script WAMIL report file as follows:
[0174] The script CELL number is 101.
Creating WAMI VAR Variables
[0175] WAMI VAR variables can be created with the CREATEVAR command.
[0176] The new VAR variable created will be of type integer.
[0177] The new VAR variable can be associated with any (in this WAMIL language embodiment) WAMI global variable.
[0178] A complimentary WAMI global variable is also created simultaneously, but it is not a key global variable (key variable).
WAMI VARn LIST
[0179] 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
[0180] 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).
[0181] WAMI VARn variables do not support Inheritance nor Association Transfers because they are elements of a list.
LIST Declaration Commands
[0182] 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.
[0183] A LIST can be declared anywhere within a WAMIL script.
[0184] The LIST size is provided as an argument with a LIST declaration command.
VARn Variables
[0185] 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 | |
|---|---|---|
[0186] The above script if named AUTO1 could be executed from the command line as follows:
[0187] WAM21 AUTO1 -bbalist 2 4 6 -endlist
VARn Type Commands
[0188] 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 | |
[0189] In line 4 of this example script, the key global variable BBA is associated with the first variable in the complimentary/auxiliary BBA list.
[0190] 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
[0191] A VARn variable can be directly referenced within a string, no association needs to be established.
[0192] WAM:PRINT The script BBA number is BBAVAR1.
WAMLIST
[0193] WAMLIST is a special WAM Interpreter LIST of infinite size.
[0194] No LIST size can (in this embodiment of the WAMIL language) be stated upon the declaration of a WAMLIST.
[0195] 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.
[0196] WAMLIST VARn variables referenced outside the LIST return a blank value.
[0197] 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 |
[0198] The above script if named AUTO1 could be executed from the command line as follows:
[0199] WAM21 AUTO1 -wamlist 2 4 -endlist
WAMIL Control Flow
[0200] Some aspect of the flow control that takes place during execution of a WAMIL script will now be discussed.
WAM Interpreter Buffer
[0201] Always holds output of the last interface command executed, unless altered.
[0202] Flushed prior to the execution of an interface command.
[0203] Can be flushed with WAM Interpreter command WAM:FLUSHBUFF
[0204] Can be appended to with WAITQUERY command execution.
[0205] Can be overwritten with execution of WAM:INPUT command.
[0206] Can be output to a file with execution of the WAM:OUTPUT or WAM:PUTS command.
CONNECT Command
[0207] Establishes a session between the WAM Interpreter and the interface provided as an argument.
[0208] WAM:CONNECT interface
[0209] Sets LFAIL flag if server login attempt fails.
[0210] Sets TFAIL flag if an interface command execution times out.
[0211] Sets CFAIL flag if an active session unexpectedly disconnects.
[0212] 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
[0213] Terminates the WAMIL script.
[0214] WAM:ENDTEST
[0215] Terminates all (in this embodiment of the WAMIL language) active sessions upon execution.
[0216] 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
[0217] Searches the WAM Interpreter buffer for the string provided as an argument.
[0218] IF:OMSG string
[0219] Argument string can include global-style matching patterns (*, ?, [ ], \).
[0220] It can include references to WAMI key global variables and VARn variables.
[0221] A match evaluates as TRUE, while no match evaluates as FALSE. An example script follows.
[0222] WAM:MSC 5
[0223] WAM:CELL 49
[0224] WAM:CCC 4
[0225] WAM:CONNECT TI
[0226] TI:op:cell 49
[0227] IF:OMSG OP:CELL CELLVAR CCC CCCVAR, ACTRVE
[0228] THEN:CONTINUE
[0229] ELSE:PRINT CCC CCCVAR is not active.
[0230] WAM:DISCONNECT TI
[0231] WAM:ENDTEST
IF THEN ELSE Construct
[0232] Can (in this embodiment of the WAMIL language) be complete and include an IF, and at a minimum one THEN and one ELSE.
[0233] Multiple THEN and ELSE command can exist within a construct.
[0234] Supports the WAM Interpreter WAITQUERY command which camps on the TI interface. An example script follows.
[0235] WAM:MSC 5
[0236] WAM:CELL 49
[0237] WAM:CCC 4
[0238] WAM:CONNECT TI
[0239] TI:rst:cell 49, ccc 4
[0240] TI:op:cell 49
[0241] IF:OMSG OP:CELL CELLVAR CCC CCCVAR, ACTIVE
[0242] THEN:CONTINUE
[0243] THEN:PRINT CCC CCCVAR is active.
[0244] ELSE:WAITQUERY 5 TI 10
[0245] WAM:DISCONNECT TI
[0246] WAM:ENDTEST
IF THENDO ELSEDO ENDIF Construct
[0247] 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.
[0248] 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.
[0249] 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
[0250] Continuously loops through the execution of a group of commands until WHILE TEST_EXPR evaluates false.
[0251] Supports the BREAK: command to break out of the loop at any (in this WAMIL language embodiment) time. An example script follows.
[0252] WHILE:TEST_EXPR CELLVAR LT 223
[0253] TI:op:cell CELLVAR
[0254] WAM:INCRVAR CELLVAR 1
[0255] ENDWHILE:
An example WAML Script That Illustrates Control Flow
[0256] WAM:MSC 5
[0257] WAM:CELL 49
[0258] WAM:CCC 4
[0259] WAM:CONNECT TI
[0260] TI:rst:cell 49, ccc 4
[0261] TI:op:cell 49
[0262] IF:OMSG OP:CELL CELLVAR CCC CCCVAR, ACTIVE
[0263] THENDO:
[0264] WAM:PRINT CCC CCCVAR is active script will continue.
[0265] ELSEDO:
[0266] IF:OMSG OP:CELL CELLVAR CCC CCCVAR, ACTIVE
[0267] THEN:CONTINUE
[0268] ELSE:WAITQUERY 5 TI 10
[0269] IF:OMSG OP:CELL CELLVAR CCC CCCVAR, ACTIVE
[0270] THENDO:
[0271] ELSEDO:
[0272] WAM:PRINT CCC CCCVAR never became active.
[0273] WAM:ENDTEST
[0274] ENDIF:
[0275] ENDIF:
[0276] TI:dgn:cell 49, ccc 4
[0277] IF:OMSG COMPLETED
[0278] THEN:CONTINUE
[0279] ELSE:WAITQUERY 5 TI 10
[0280] WAM:DISCONNECT TI WAM:ENDTEST
SPOOL Command
[0281] The WAMIL SPOOL command which adjust the pause of the spooler.
GET_TI Command
[0282] The WAMIL GET_TI command which allows assignment of an output message value to a script VAR variable.
TRACE Command
[0283] TRACE command with specified options allows low level tracing of WAMIL commands and variables during a script execution.
[0284] 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.
[0285] Opens a TRACE display window to allow viewing of actual TRACE during script execution.
[0286] 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.
[0287] 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
[0288] The WAMIL PAUSE command can be used for semi-automation, or to prompt the user for a decision.
[0289] 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
[0290] 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.
[0291] WAM:MSCVAR
[0292] WAM:CELLVAR
[0293] WAM:ANTVAR
[0294] WAM:WAMLIST Enter a value for t_add and a value for t_drop
[0295] WAM:PUTS HOME TEMP.dbf t_add=WAMVAR1
[0296] WAM:PUTS HOME TEMP.dbf t_drop=WAMVAR2
[0297] WAM:PUTAPX ceqface TEMP
[0298] WAM:UNIX rm TEMP.dbf
[0299] WAM:ENDTEST
Script Looping
[0300] A WAMIL script can be looped using the -loop option. In the following example the script AUTO1 is looped 10 times.
[0301] WAM21 AUTO1 -loop 10
UNIX Command
[0302] The WAMIL UNIX command allows the execution of any (in this WAMIL language embodiment) UNIX executable from within a WAMIL script.
[0303] 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:
[0304] WAM:MSCVAR
[0305] WAM:CELLVAR
[0306] WAM:ANTVAR
[0307] WAM:WAMLIST Enter a value for t_add and a value for t_drop
[0308] WAM:PUTS HOME TEMP.dbf t_add=WAMVAR1
[0309] WAM:PUTS HOME TEMP.dbf t_drop=WAMVAR2
[0310] WAM:PUTAPX ceqface TEMP
[0311] WAM:UNIX rm TEMP.dbf
[0312] WAM:UNIX WAM21 jt1234 -msc MSCVAR -cell CELLVAR &
[0313] WAM:WAIT 180
[0314] WAM:UNIX kill −9 WAMVAR
[0315] WAM:ENDTEST
WAMI Linker
[0316] 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.
[0317] A detailed glossary of WAMI Link commands is presented later in this document.
Serial or Parallel Execution
[0318] A linked script can be executed in a serial or parallel fashion.
[0319] 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.
[0320] 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
[0321] An example WAMIL Linker script below links four WAMIL scripts together. Two of the scripts are executed in a serial fashion:
[0322] LINK:EXEC PARALLEL
[0323] LINK:SCRIPT HOME jt1234
[0324] LINK:SCRIPT HOME jt2023
[0325] LINK:EXEC SERIAL
[0326] LINK:SCRIPT HOME jt4567
[0327] LINK:SCRIPT HOME jt9988
[0328] WAM:ENDTEST
[0329] The above Linker script if named AUTO1 could be executed from the command line as follows: WAM21 AUTO1 -link.
Linker Script Output
[0330] 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.
[0331] If the above Linker script was named LINKAUTO, execution of the script would generate five separate output files:
[0332] LINKAUTO.rpt, jt1234.rpt, jt2023, jt4567.rpt, jt9988.rpt
Commands Embeddable Within Integration Construct Data Structure
[0333] 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 |
|---|
[0334] 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.
[0335] 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
[0336] 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.
[0337] Again, a WAM interface command is structured as, e.g.,
[0338] WAM:CELL 93
[0339] where CELL is the actual WAM interface command and the value of 93 is the command argument.
[0340] The glossary begins with the command, ADDCE, and ends with the command, XMITC.
ADDCE
[0341] The ADDCE command can be embedded in the integration construct data structure according to the invention.
[0342] PURPOSE: This command changes the WAMI global number of channel elements to add the variable, ADDCE, to the value provided as an argument.
[0343] SYNTAX: WAM:ADDCE value
[0344] EXAMPLE CALL: WAM:ADDCE 2
[0345] 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.
[0346] 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.
[0347] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution of an ADDCE command:
[0348] Set Number Of Channel Elements to Add To 2
[0349] ERRORS: None.
[0350] ALTERS: ADDCE
[0351] 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.
[0352] SEE ALSO: WAM:INITIALIZE
ADRS
[0353] The ADRS command can be embedded in the integration construct data structure according to the invention.
[0354] PURPOSE: Changes the WAMI global memory address number variable, ADRS, to the value provided as an argument.
[0355] SYNTAX: WAM:ADRS value
[0356] EXAMPLE CALL: WAM:ADRS X′500be020,18
[0357] 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.
[0358] 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.
[0359] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution of an ADRS command:
[0360] Set Memory Address To X′500be020,18
[0361] ERRORS: None.
[0362] ALTERS: ADRS
[0363] 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.
[0364] SEE ALSO: WAM:INITIALIZE
[0365] EXAMPLE: The following script lines will set the WAMIL script ADRS variable to X500be020,18 and then execute a TI interface command:
[0366] WAM:CELL 49
[0367] WAM:CCC 2
[0368] WAM:ADRS X500be020,18
[0369] TI:dump:cell 49, ccc 2; adrs X500be020,18
ANT
[0370] The ANT command can be embedded in the integration construct data structure according to the invention.
[0371] PURPOSE: Changes the WAMI global antenna face variable, ANT, to the value provided as an argument.
[0372] SYNTAX: WAM:ANT value
[0373] EXAMPLE CALL: WAM:ANT 1
[0374] 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.
[0375] 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.
[0376] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution an ANT command:
[0377] Set Antenna Face 1
[0378] ERRORS: None.
[0379] ALTERS: ANT
[0380] 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.
[0381] SEE ALSO: WAM:INITIALIZE
[0382] EXAMPLE: The following script lines will set the WAMIL script ANT variable to 1 and then execute a TI interface command:
[0383] WAM:CELL 49
[0384] WAM:ANT 1
[0385] TI:op:cell 49, sg 0, ant 1, all!
ANTVAR
[0386] The ANTVAR command can be embedded in the integration construct data structure according to the invention.
[0387] PURPOSE: Declares to the WAM Interpreter, that a value for the WAMI VAR variable ANTVAR will be supplied to the script.
[0388] SYNTAX: WAM:ANTVAR
[0389] EXAMPLE CALL: WAM:ANTVAR
[0390] 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.
[0391] 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.
[0392] 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.
[0393] 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.
[0394] 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.
[0395] 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.
[0396] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution a ANTVAR command:
[0397] Set ANT To Argument Value of 2
[0398] ERRORS: If no command line value has been provided, the WAM Interpreter will generate an error and script execution will be aborted.
[0399] ALTERS: ANTVAR
[0400] 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.
[0401] SEE ALSO: WAM:ANT value
[0402] EXAMPLE: The following script executes a TI command for the ANT number supplied:
[0403] WAM:MSC 5
[0404] WAM:CELL 49
[0405] WAM:SG 0
[0406] WAM:ANTVAR
[0407] WAM:CONNECT TI
[0408] TI:op:cell 49, sg 0, ant ANTVAR, all!
[0409] WAM:DISCONNECT TI
[0410] WAM:ENDTEST
APXVAR
[0411] The APXVAR command can be embedded in the integration construct data structure according to the invention.
[0412] PURPOSE: Declares to the WAM Interpreter, that a value or string for the WAMI VAR variable APXVAR will be supplied to the script.
[0413] SYNTAX: WAM:APXVAR prompt string
[0414] EXAMPLE CALL: WAM:APXVAR Enter Neighbor Cell Number
[0415] 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.
[0416] 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.
[0417] 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.
[0418] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution an APXVAR command:
[0419] Set APXVAR To Argument Value of 173
[0420] ERRORS: The prompt_string argument, although not used by the WAM Interpreter, will generate a syntax error if omitted.
[0421] If no command line value or string has been provided, the WAM Interpreter will generate an error and script execution will be aborted.
[0422] ALTERS: APXVAR
[0423] 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.
[0424] SEE ALSO: WAM:WAMVAR prompt_string
[0425] EXAMPLE: The following script adds a neighbor to cell 49:
[0426] WAM:MSC 5
[0427] WAM:CELL 49
[0428] WAM:ANT 1
[0429] WAM:SG 0
[0430] WAM:APXVAR Enter Neighbor Cell Number
[0431] WAM:PUTAPXFLD fci cdmanbr_listl.ncs_c[1]=APXVAR
[0432] WAM:ENDTEST
AU
[0433] The AU command can be embedded in the integration construct data structure according to the invention.
[0434] PURPOSE: Changes the WAMI global cell amplifier unit number variable, AU, to the value provided as an argument.
[0435] SYNTAX: WAM:AU value
[0436] EXAMPLE CALL: WAM:AU 1
[0437] 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.
[0438] 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.
[0439] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution an AU command:
[0440] Set Amplifier Unit 1
[0441] ERRORS: None.
[0442] ALTERS: AU
[0443] 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.
[0444] SEE ALSO: WAM:INITIALIZE
[0445] EXAMPLE: The following script lines will set the WAMIL script AU variable to 1 and then execute a TI interface command:
[0446] WAM:CELL 49
[0447] WAM:AU 1
[0448] TI:op:cell 49, au 1
BBA
[0449] The BBA command can be embedded in the integration construct data structure according to the invention.
[0450] PURPOSE: Changes the WAMI global BCR-BIU-ACU trio variable, BBA, to the value provided as an argument.
[0451] SYNTAX: WAM:BBA value
[0452] EXAMPLE CALL: WAM:BBA 4
[0453] 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.
[0454] 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.
[0455] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution an BBA command:
[0456] Set BCR-BIU-ACU Trio 4:
[0457] BCR (BaseBand Combiner/Radio)
[0458] BIU (Bus Interface Unit)
[0459] ACU (Analog Conversion Unit)
[0460] ERRORS: None.
[0461] ALTERS: BBA
[0462] 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.
[0463] SEE ALSO: WAM:INITIALIZE
[0464] EXAMPLE: The following script will set the WAMIL script BBA variable to 4 and then execute a TI interface command:
[0465] WAM:MSC 5
[0466] WAM:CELL 49
[0467] WAM:CONNECT TI
[0468] WAM:BBA 4
[0469] TI:op:cell 49, bba 4
[0470] WAM:DISCONNECT TI
[0471] WAM:ENDTEST
BBALIST
[0472] The BBALIST command can be embedded in the integration construct data structure according to the invention.
[0473] PURPOSE: Declares to the WAM Interpreter, that a list of WAMI VARn BBA numbers will be supplied to the script.
[0474] SYNTAX: WAM:BBALIST value
[0475] EXAMPLE CALL: WAM:BBALIST 3
[0476] 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.
[0477] 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.
[0478] 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.
[0479] 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.
[0480] 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.
[0481] 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.
[0482] The Scriptor will only (in this embodiment of the WAMIL language) allow insertion of one BBALIST command into the current script.
[0483] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a BBALIST command:
[0484] Total Number of BBA List Values Set To 4
[0485] BBA List Values: 2 4 6 8
[0486] ERRORS: If a value larger than 30 is used the WAM Interpreter will generate an error and script execution will be aborted.
[0487] Any references within a script to a WAMIVARn variable prior to the declaration of the list will generate a syntax error.
[0488] 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.
[0489] ALTERS: WAMIVARn BBA List.
[0490] 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.
[0491] SEE ALSO: WAM:BBAVARn, WAM:INITIALIZE
[0492] EXAMPLE: The following script sets the WAMIVARn BBA List length to 2, and executes a TI command for each BBA number in the list:
[0493] WAM:MSC 5
[0494] WAM:CELL 49
[0495] WAM:BBALIST 2
[0496] WAM:CONNECT TI
[0497] WAM:BBAVAR1
[0498] TI:op:cell 49, bba BBAVAR1
[0499] WAM:BBAVAR2
[0500] TI:op:cell 49, bba BBAVAR2
[0501] WAM:DISCONNECT TI
[0502] WAM:ENDTEST
BBAVAR
[0503] The BBAVAR command can be embedded in the integration construct data structure according to the invention.
[0504] PURPOSE: Declares to the WAM Interpreter, that a value for the WAMIVAR variable BBAVAR will be supplied to the script.
[0505] SYNTAX: WAM:BBAVAR
[0506] EXAMPLE CALL: WAM:BBAVAR
[0507] 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.
[0508] 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.
[0509] 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.
[0510] 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.
[0511] 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.
[0512] 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.
[0513] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution a BBAVAR command:
[0514] Set BBA To Argument Value of 8
[0515] ERRORS: If no command line value has been provided, the WAM Interpreter will generate an error and script execution will be aborted.
[0516] ALTERS: BBAVAR
[0517] 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.
[0518] SEE ALSO: WAM:BBA value
[0519] EXAMPLE: The following script executes a TI command for the BBA number supplied:
[0520] WAM:MSC 5
[0521] WAM:CELL 49
[0522] WAM:BBAVAR
[0523] WAM:CONNECT TI
[0524] TI:op:cell 49, bba BBAVAR
[0525] WAM:DISCONNECT TI
[0526] WAM:ENDTEST
BBAVARn
[0527] The BBAVARn command can be embedded in the integration construct data structure according to the invention.
[0528] 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.
[0529] SYNTAX: WAM:BBAVARn
[0530] EXAMPLE CALL: WAM:BBAVAR2
[0531] 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.
[0532] 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.
[0533] 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.
[0534] 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.
[0535] 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:
[0536] Set BBA To BBAVAR2 Value Of 4
[0537] 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.
[0538] 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.
[0539] 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.
[0540] ALTERS: BBA
[0541] DEFAULT VALUE: None (in this WAMIL language embodiment).
[0542] SEE ALSO: WAM:BBA value, WAM:BBALIST value
[0543] 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:
[0544] WAM:MSC 5
[0545] WAM:CELL 49
[0546] WAM:BBALIST 2
[0547] WAM:CONNECT TI
[0548] WAM:BBAVAR1
[0549] TI:op:cell 49, bba BBAVAR1
[0550] WAM:BBAVAR2
[0551] TI:op:cell 49, bba BBAVAR2
[0552] WAM:DISCONNECT TI
[0553] WAM:ENDTEST
CAT
[0554] The CAT command can be embedded in the integration construct data structure according to the invention.
[0555] PURPOSE: Changes the WAMI global clock and tone board number variable, CAT, to the value provided as an argument.
[0556] SYNTAX: WAM:CAT value
[0557] EXAMPLE CALL: WAM:CAT 6
[0558] 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.
[0559] 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.
[0560] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution a CAT command:
[0561] Set Clock and Tone Board 6
[0562] ERRORS: None.
[0563] ALTERS: CAT
[0564] 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.
[0565] SEE ALSO: WAM:INITIALIZE
[0566] EXAMPLE: The following script lines set the WAMIL script CAT variable to 6 and then execute a TI interface command:
[0567] WAM:CELL 49
[0568] WAM:CAT 6
[0569] TI:op:cell 49, cat 6
CATLIST
[0570] The CATLIST command can be embedded in the integration construct data structure according to the invention.
[0571] PURPOSE: Declares to the WAM Interpreter, that a list of WAMI VARn CAT numbers will be supplied to the script.
[0572] SYNTAX: WAM:CATLIST value
[0573] EXAMPLE CALL: WAM:CATLIST 3
[0574] 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.
[0575] 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.
[0576] 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.
[0577] 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.
[0578] 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.
[0579] 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.
[0580] The Scriptor will only (in this embodiment of the WAMIL language) allow insertion of one CATLIST command into the current script.
[0581] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a CATLIST command:
[0582] Total Number of CAT List Values Set To 3
[0583] CAT List Values: 0 6 7
[0584] ERRORS: If a value larger than 10 is used the WAM Interpreter will generate an error and script execution will be aborted.
[0585] Any references within a script to a WAMI VARn variable prior to the declaration of the list will generate a syntax error.
[0586] 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.
[0587] ALTERS: WAMI VARn CAT List.
[0588] 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.
[0589] SEE ALSO: WAM:CATVARn, WAM:INITIALIZE
[0590] 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:
[0591] WAM:MSC 5
[0592] WAM:CELL 49
[0593] WAM:CATLIST 2
[0594] WAM:CONNECT TI
[0595] WAM:CATVAR1
[0596] TI:op:cell 49, cat CATVAR1
[0597] WAM:CATVAR2
[0598] TI:op:cell 49, cat CATVAR2
[0599] WAM:DISCONNECT TI
[0600] WAM:ENDTEST
CATVARn
[0601] The CATVARn command can be embedded in the integration construct data structure according to the invention.
[0602] 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.
[0603] SYNTAX: WAM:CATVARn
[0604] EXAMPLE CALL: WAM:CATVAR2
[0605] 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.
[0606] 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.
[0607] 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.
[0608] 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.
[0609] 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:
[0610] Set CAT To CATVAR2 Value Of 7
[0611] 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.
[0612] 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.
[0613] 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.
[0614] ALTERS: CAT
[0615] DEFAULT VALUE: None (in this WAMIL language embodiment).
[0616] SEE ALSO: WAM:CAT value, WAM:CATLIST value
[0617] 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:
[0618] WAM:MSC 5
[0619] WAM:CELL 49
[0620] WAM:CATLIST 2
[0621] WAM:CONNECT TI
[0622] WAM:CATVAR1
[0623] TI:op:cell 49, cat CATVAR1
[0624] WAM:CATVAR2
[0625] TI:op:cell 49, cat CATVAR2
[0626] WAM:DISCONNECT TI
[0627] WAM:ENDTEST
CCC
[0628] The CCC command can be embedded in the integration construct data structure according to the invention.
[0629] PURPOSE: Changes the WAMI global CDMA Cluster Controller number variable, CCC, to the value provided as an argument.
[0630] SYNTAX: WAM:CCC value
[0631] EXAMPLE CALL: WAM:CCC 2
[0632] 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.
[0633] 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.
[0634] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution a CCC command:
[0635] Set CCC 2
[0636] ERRORS: None.
[0637] ALTERS: CCC
[0638] 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.
[0639] SEE ALSO: WAM:INITIALIZE
[0640] EXAMPLE: The following script will set the WAMIL script CCC variable to 2 and then execute a TI interface command:
[0641] WAM:CELL 49
[0642] WAM:CCC 2
[0643] TI:op:cell 49, ccc 2, ccu 1
CCCLIST
[0644] The CCCLIST command can be embedded in the integration construct data structure according to the invention.
[0645] PURPOSE: Declares to the WAM Interpreter, that a list of WAMI VARn CCC numbers will be supplied to the script.
[0646] SYNTAX: WAM:CCCLIST value
[0647] EXAMPLE CALL: WAM:CCCLIST 3
[0648] 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.
[0649] 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.
[0650] 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.
[0651] 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.
[0652] 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.
[0653] 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.
[0654] The Scriptor will only (in this embodiment of the WAMIL language) allow insertion of one CCCLIST command into the current script.
[0655] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a CCCLIST command:
[0656] Total Number of CCC List Values Set To 3
[0657] CCC List Values: 2 4 6
[0658] ERRORS: If a value larger than 30 is used the WAM Interpreter will generate an error and script execution will be aborted.
[0659] Any references within a script to a WAMI VARn variable prior to the declaration of the list will generate a syntax error.
[0660] 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.
[0661] ALTERS: WAMI VARn CCC List.
[0662] 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.
[0663] SEE ALSO: WAM:CCCVARn, WAM:INITIALIZE
[0664] 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:
[0665] WAM:MSC 5
[0666] WAM:CELL 49
[0667] WAM:CCCLIST 2
[0668] WAM:CONNECT TI
[0669] WAM:CCCVAR1
[0670] TI:op:cell 49, ccc CCCVAR1, ccu 1
[0671] WAM:CCCVAR2
[0672] TI:op:cell 49, ccc CCCVAR2, ccu 1
[0673] WAM:DISCONNECT TI
[0674] WAM:ENDTEST
CCCVAR
[0675] The CCCVAR command can be embedded in the integration construct data structure according to the invention.
[0676] PURPOSE: Declares to the WAM Interpreter, that a value for the WAMI VAR variable CCCVAR will be supplied to the script.
[0677] SYNTAX: WAM:CCCVAR
[0678] EXAMPLE CALL: WAM:CCCVAR
[0679] 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.
[0680] 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.
[0681] 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.
[0682] 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.
[0683] 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.
[0684] 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.
[0685] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution a CCCVAR command:
[0686] Set CCC To Argument Value of 8
[0687] ERRORS: If no command line value has been provided, the WAM Interpreter will generate an error and script execution will be aborted.
[0688] ALTERS: CCCVAR
[0689] 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.
[0690] SEE ALSO: WAM:CCC value
[0691] EXAMPLE: The following script executes a TI command for the CCC number supplied:
[0692] WAM:MSC 5
[0693] WAM:CELL 49
[0694] WAM:CCCVAR
[0695] WAM:CONNECT TI
[0696] TI:op:cell 49, ccc CCCVAR, ccu 1
[0697] WAM:DISCONNECT TI
[0698] WAM:ENDTEST
CCCVARn
[0699] The CCCVARn command can be embedded in the integration construct data structure according to the invention.
[0700] 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.
[0701] SYNTAX: WAM:CCCVARn
[0702] EXAMPLE CALL: WAM:CCCVAR2
[0703] 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.
[0704] 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.
[0705] 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.
[0706] 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.
[0707] 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:
[0708] Set CCC To CCCVAR2 Value Of 4
[0709] 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.
[0710] 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.
[0711] 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.
[0712] ALTERS: CCC
[0713] DEFAULT VALUE: None (in this WAMIL language embodiment).
[0714] SEE ALSO: WAM:CCC value, WAM:CCCLIST value
[0715] 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:
[0716] WAM:MSC 5
[0717] WAM:CELL 49
[0718] WAM:CCCLIST 2
[0719] WAM:CONNECT TI
[0720] WAM:CCCVAR1
[0721] TI:op:cell 49, ccc CCCVAR1, ccu 1
[0722] WAM:CCCVAR2
[0723] TI:op:cell 49, ccc CCCVAR2, ccu 1
[0724] WAM:DISCONNECT TI
[0725] WAM:ENDTEST
CCU
[0726] The CCU command can be embedded in the integration construct data structure according to the invention.
[0727] PURPOSE: Changes the WAMI global CDMA Channel Unit number variable, CCU, to the value provided as an argument.
[0728] SYNTAX: WAM:CCU value
[0729] EXAMPLE CALL: WAM:CCU 2
[0730] 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.
[0731] 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.
[0732] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution a CCU command:
[0733] Set CCU 2
[0734] ERRORS: None.
[0735] ALTERS: CCU
[0736] 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.
[0737] SEE ALSO: WAM:INITIALIZE
[0738] EXAMPLE: The following script will set the WAMIL script CCU variable to 2 and then execute a TI interface command:
[0739] WAM:CELL 49
[0740] WAM:CCU 2
[0741] TI:op:cell 49, ccc 1, ccu 2
CCULIST
[0742] The CCULIST command can be embedded in the integration construct data structure according to the invention.
[0743] PURPOSE: Declares to the WAM Interpreter, that a list of WAMI VARn CCU numbers will be supplied to the script.
[0744] SYNTAX: WAM:CCULIST value
[0745] EXAMPLE CALL: WAM:CCULIST 3
[0746] 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.
[0747] 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 the command. This value declares to the WAM Interpreter the exact size of the CCU List. The CCU numbers within the CCU List can then be referenced within the script as WAMI VARn variables, according to their index position in the list. For example, CCUVAR2 refers to the second CCU number in the CCU List. The order of the CCU numbers provided determine the order of their placement within the CCU List.
[0748] Up to 12 CCU numbers can be passed as an argument with this command. Therefore, the maximum acceptable size for the CCUList is 12. If a value larger than 12 is used the WAM Interpreter will generate an error and script execution will be aborted.
[0749] 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.
[0750] WAMI GUI PLATFORM: Prior to execution of a WAMIL script, the WAMI GUI platform searches the script for special commands. If a WAM:CCULIST command is encountered the WAMI GUI platform will prompt the user for the quantity of CCU numbers defined by the command argument value. Subsequent WAM:CCULIST commands encountered will not cause additional prompting.
[0751] SCRIPTOR: If this command is deleted from the current script, the WAMIL Scriptor will delete all (in this embodiment of the WAMIL language) reference CCUVARn commands existing in the script also. The script WAMI global CCU variable will then beset to the default value of 1.
[0752] The Scriptor will only (in this embodiment of the WAMIL language) allow insertion of one CCULIST command into the current script.
[0753] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a CCULIST command:
[0754] Total Number of CCU List Values Set To 3
[0755] CCU List Values: 2 4 6
[0756] ERRORS: If a value larger than 12 is used the WAM Interpreter will generate an error and script execution will be aborted.
[0757] Any references within a script to a WAMI VARn variable prior to the declaration of the list will generate a syntax error.
[0758] If more than one CCULIST 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 CCULIST commands have no effect.
[0759] ALTERS: WAMI VARn CCU List.
[0760] DEFAULT VALUE: The WAMI VARn CCU 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.
[0761] SEE ALSO: WAM:CCUVARn, WAM:INITIALIZE
[0762] EXAMPLE: The following script sets the WAMI VARn CCU List length to 2, and executes a TI command for each CCU number in the list:
[0763] WAM:MSC 5
[0764] WAM:CELL 49
[0765] WAM:CCULIST 2
[0766] WAM:CONNECT TI
[0767] WAM:CCUVAR1
[0768] TI:op:cell 49, ccc CCUVAR1, ccu 1
[0769] WAM:CCUVAR2
[0770] TI:op:cell 49, ccc CCUVAR2, ccu 1
[0771] WAM:DISCONNECT TI
[0772] WAM:ENDTEST
CCUVAR
[0773] The CCUVAR command can be embedded in the integration construct data structure according to the invention.
[0774] PURPOSE: Declares to the WAM Interpreter, that a value for the WAMI VAR variable CCUVAR will be supplied to the script.
[0775] SYNTAX: WAM:CCUVAR
[0776] EXAMPLE CALL: WAM:CCUVAR
[0777] DESCRIPTION: The WAM:CCUVAR 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 CCUVAR.
[0778] Like standard WAMI VAR variable declaration commands, the execution of this command also enables an association with the WAMI global CCU variable. Therefore, until the WAMI global CCU variable association is transferred to another WAMI VAR variable, or disabled, all (in this embodiment of the WAMIL language) references to the WAMI global CCU variable will use the CCUVAR variable value.
[0779] For script syntax, until an actual CCU number is passed as an argument, when a CCLVAR command is used the CCU number within a script shall be referenced as CCUVAR from that point forward.
[0780] 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.
[0781] WAMI GUI PLATFORM: Prior to execution of a WAMIL script, the WAMI GUI platform searches the script for special commands. If a WAM:CCUVAR is encountered the WAMI GUI platform will prompt the user for the script CCUVAR value. Subsequent WAM:CCUVAR commands encountered will not cause additional prompting.
[0782] SCRIPTOR: If a CCUVAR command is deleted from the current script, the Scriptor will prompt the user for a CCU number and then insert a WAM:CCU value command in place of the CCUVAR command deleted.
[0783] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution a CCUVAR command:
[0784] Set CCU To Argument Value of 2
[0785] ERRORS: If no command line value has been provided, the WAM Interpreter will generate an error and script execution will be aborted.
[0786] ALTERS: CCUVAR
[0787] DEFAULT VALUE: CCUVAR 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.
[0788] SEE ALSO: WAM:CCU value
[0789] EXAMPLE: The following script executes a TI command for the CCU number supplied:
[0790] WAM:MSC 5
[0791] WAM:CELL 49
[0792] WAM:CCUVAR
[0793] WAM:CONNECT TI
[0794] TI:op:cell 49, ccc 1, ccu CCUVAR
[0795] WAM:DISCONNECT TI
[0796] WAM:ENDTEST
CCUVARn
[0797] The CCUVARn command can be embedded in the integration construct data structure according to the invention.
[0798] PURPOSE: Instructs the WAM Interpreter to set the WAMI global CCU variable to the value of the referenced WAMI VARn CCU variable, in position n, of the CCU List passed as an argument.
[0799] SYNTAX: WAM:CCUVARn
[0800] EXAMPLE CALL: WAM:CCUVAR2
[0801] DESCRIPTION: The WAM:CCUVARn command is an assignment command.
[0802] This command can only (in this embodiment of the WAMIL language) be executed if a CCU List has been declared in the script. Upon execution, this command assigns a CCU List variable value to the WAMI global CCU variable.
[0803] The value n, can (in this embodiment of the WAMIL language) be a valid index into the CCU List. Any (in this WAMIL language embodiment) CCU List value can be assigned to the WAMI global CCU variable by execution of this command, where n is the CCU value location within the CCU List. Upon execution, the CCU number within a script is referenced as CCUVARn from that point forward.
[0804] Like standard WAMI VARn variable assignment commands, the execution of this command also enables an association with the WAMI global CCU variable. Therefore, until the WAMI global CCU variable association is transferred to a WAMI VAR variable, or disabled, all (in this embodiment of the WAMIL language) references to the WAMI global CCU variable will use the CCUVARn variable value.
[0805] For script syntax, until actual CCU List values are passed as an argument, when a CCUVARn command is used the CCU number within a script shall be referenced as CCUVARn from that point forward.
[0806] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a CCUVARn command, when a CCU List of 3 was previously declared, and the CCU List numbers passed as an argument are 1 2 3:
[0807] Set CCU To CCUVAR2 Value Of 2
[0808] SCRIPTOR: If a CCUVARn command is deleted from the current script, the Scriptor will prompt the user for a CCU number and then insert a WAM:CCU value command in place of the CCUVARn command deleted.
[0809] ERRORS: An invalid CCUVARn command used within a script, where n refers to a CCU List index outside the list range, will generate an error. Script execution will then be aborted.
[0810] If a CCUVARn command is used within a script in which no CCU List has been declared, the WAM Interpreter will generate an error and terminate execution of the script.
[0811] ALTERS: CCU
[0812] DEFAULT VALUE: None (in this WAMIL language embodiment).
[0813] SEE ALSO: WAM:CCU value, WAM:CCULIST value
[0814] EXAMPLE: The following script sets the WAMI VARn CCU List length to 2, and executes a TI command for each CCU number in the list:
[0815] WAM:MSC 5
[0816] WAM:CELL 49
[0817] WAM:CCULIST 2
[0818] WAM:CONNECT TI
[0819] WAM:CCUVAR1
[0820] TI:op:cell 49, ccc 1, ccu CCUVAR1
[0821] WAM:CCUVAR2
[0822] TI:op:cell 49, ccc 1, ccu CCUVAR2
[0823] WAM:DISCONNECT TI
[0824] WAM:ENDTEST
CDMADPC
[0825] The CDMADPC command can be embedded in the integration construct data structure according to the invention.
[0826] PURPOSE: Changes the WAMI global BCR-BIU-ACU power control option number variable, CDMADPC, to the value provided as an argument.
[0827] SYNTAX: WAM:CDMADPC value
[0828] EXAMPLE CALL: WAM:CDMADPC 150
[0829] DESCRIPTION: The CDMADPC command sets the WAMI global BCR-BIU-ACU power control option 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 power control option number, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script BCR-BIU-ACU power control option number, will reference the new value.
[0830] 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.
[0831] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution a CDMADPC command:
[0832] Set BBA Power Control Option To 150
[0833] ERRORS: None.
[0834] ALTERS: CDMADPC
[0835] DEFAULT VALUE: CDMADPC is set to 0 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 0.
[0836] SEE ALSO: WAM:INITIALIZE
CE
[0837] The CE command can be embedded in the integration construct data structure according to the invention.
[0838] PURPOSE: Changes the WAMI global Channel Element number variable, CE, to the value provided as an argument.
[0839] SYNTAX: WAM:CE value
[0840] EXAMPLE CALL: WAM:CE 2
[0841] DESCRIPTION: The WAM:CE command sets the WAMI global Channel Element 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 Channel Element number, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script Channel Element number, will reference the new value.
[0842] 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.
[0843] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution a CE command:
[0844] Set Channel Element To 2
[0845] ERRORS: None.
[0846] ALTERS: CE
[0847] DEFAULT VALUE: CE is set to 0 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 0.
[0848] SEE ALSO: WAM:INITIALIZE
CELL
[0849] The CELL command can be embedded in the integration construct data structure according to the invention.
[0850] PURPOSE: Changes the WAMI global cell number variable, CELL, to the value provided as an argument.
[0851] SYNTAX: WAM:CELL value
[0852] EXAMPLE CALL: WAM:CELL 49
[0853] DESCRIPTION: The WAM:CELL command sets the WAMI global CELL 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 number, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script cell number, will reference the new value.
[0854] 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.
[0855] SCRIPTOR: If the LOOPCELL, LOOPCELLVARS, or CELLVAR commands already exist in a script, the Scriptor will not allow a user to add any (in this WAMIL language embodiment) CELL commands.
[0856] If the last CELL command is deleted from the current script, the Scriptor will display an error message notifying the user that no CELL number has been defined for the script.
[0857] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution an CELL command:
[0858] Start Test Cell: 49
[0859] ERRORS: None.
[0860] ALTERS: CELL
[0861] DEFAULT VALUE: CELL is set to 0 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 0.
[0862] SEE ALSO: WAM:CELLVAR, WAM:LOOPCELL cells . . . , WAM:LOOPCELLVARS, WAM:INITIALIZE
[0863] EXAMPLE: The following script will set the WAMIL script CELL variable to 49 and then execute a TI interface command:
[0864] WAM:MSC 5
[0865] WAM:CELL 49
[0866] WAM:CONNECT TI
[0867] TI:op:cell 49
[0868] WAM:DISCONNECT TI
[0869] WAM:ENDTEST
CELLVAR
[0870] The CELLVAR command can be embedded in the integration construct data structure according to the invention.
[0871] PURPOSE: Declares to the WAM Interpreter, that a value for the WAMI VAR variable CELLVAR will be supplied to the script.
[0872] SYNTAX: WAM:CELLVAR
[0873] EXAMPLE CALL: WAM:CELLVAR
[0874] DESCRIPTION: The WAM:CELLVAR 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 CELLVAR.
[0875] Like standard WAMI VAR variable declaration commands, the execution of this command also enables an association with the WAMI global CELL variable. Therefore, until the WAMI global CELL variable association is transferred to another WAMI VAR variable, or disabled, all (in this embodiment of the WAMIL language) references to the WAMI global CELL variable will use the CELLVAR variable value.
[0876] For script syntax, until an actual CELL number is passed as an argument, when a CELLVAR command is used the CELL number within a script shall be referenced as CELLVAR from that point forward.
[0877] NOTE: For backwards compatibility purposes, CELLVAR can be referenced within TI and SDP interface commands as X. Thus a TI interface command would be written as TI:op:cell X instead of as follows, TI:op:cell CELLVAR
[0878] 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.
[0879] WAMI GUI PLATFORM: Prior to execution of a WAMIL script, the WAMI GUI platform searches the script for special commands. If a WAM:CELLVAR is encountered the WAMI GUI platform will prompt the user for the script CELLVAR value.
[0880] Subsequent WAM:CELLVAR commands encountered will not cause additional prompting.
[0881] SCRIPTOR: If a CELLVAR command is deleted from the current script, the Scriptor will prompt the user for a CELL number and then insert a WAM:CELL value command in place of the CELLVAR command deleted.
[0882] Upon insertion of this command, the Scriptor will remove all (in this embodiment of the WAMIL language) CELL commands, if any, from the script and any cell looping commands, and set the default cell number to the value CELLVAR.
[0883] The Scriptor automatically places this command below any (in this WAMIL language embodiment) existing WAM:DISPLAY or WAM:MSCVAR command.
[0884] The CELLVAR command upon insertion automatically replaces any (in this WAMIL language embodiment) LOOPCELL, or LOOPCELLVARS command in the script, if any.
[0885] The Scriptor will only (in this embodiment of the WAMIL language) allow one CELLVAR command to be inserted into the current script.
[0886] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a CELLVAR command, when cell 49 is passed as an argument:
[0887] Set CELL To Argument Value of 49
[0888] Start Test Cell: 49
[0889] ERRORS: If no command line value has been provided, the WAM Interpreter will generate an error and script execution will be aborted.
[0890] If CELLVAR is included in a script with the LOOPCELL or LOOPCELLVARS command, unpredictable errors may result.
[0891] ALTERS: CELLVAR
[0892] DEFAULT VALUE: CELLVAR 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.
[0893] SEE ALSO: WAM:CELL value, WAM:LOOPCELL cells . . . , WAM:LOOPCELLVARS
[0894] EXAMPLE: The following script executes a TI command for the CELL number supplied:
[0895] WAM:MSC 5
[0896] WAM:CELLVAR
[0897] WAM:CONNECT TI
[0898] TI:op:cell CELLVAR
[0899] WAM:DISCONNECT TI
[0900] WAM:ENDTEST
CGSA
[0901] The CGSA command can be embedded in the integration construct data structure according to the invention.
[0902] PURPOSE: Changes the WAMI global cellular geographic service area number variable, CGSA, to the value provided as an argument.
[0903] SYNTAX: WAM:CGSA value
[0904] EXAMPLE CALL: WAM:CGSA 2
[0905] DESCRIPTION: The CGSA command sets the WAMI global cellular geographic service area number variable to the value provided as an argument. After execution of this command, all (in this embodiment of the WAM IL language) subsequent commands which require use of the cellular geographic service area number, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script cellular geographic service area number, will reference the new value.
[0906] 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.
[0907] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution a CGSA command:
[0908] Set Cellular Geographic Service Area To 2
[0909] ERRORS: None.
[0910] ALTERS: CGSA
[0911] DEFAULT VALUE: CGSA is set to 0 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 0.
[0912] SEE ALSO: WAM:INITIALIZE
CLOSE
[0913] The CLOSE command can be embedded in the integration construct data structure according to the invention.
[0914] PURPOSE: Causes the WAM Interpreter to stop saving OutBuff to the filename provided as an argument, and close the file.
[0915] SYNTAX: WAM:CLOSE filename
[0916] EXAMPLE CALL: WAM:CLOSE BuffStore
[0917] DESCRIPTION: The CLOSE command closes a file opened with the OPEN command. After execution of this command, the WAM Interpreter OutBuff will no longer be appended to the filename provided as an argument.
[0918] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a CLOSE command:
[0919] Close the WAMI OutBuff Redirection File: BuffStore
[0920] ERRORS: If an error is encountered in execution of the CLOSE command, the error message will be output to the WAMIL report file.
[0921] If the argument filename is for a file which has not been opened, or is already closed, the WAM Interpreter will generate an error message.
[0922] ALTERS: None (in this WAMIL language embodiment).
[0923] DEFAULT VALUE: None (in this WAMIL language embodiment).
[0924] SEE ALSO: WAM:OPEN filename
[0925] EXAMPLE: The following script lines will open an OutBuff Redirection file and save the output of a TI command prior to closing the file:
[0926] WAM:OPEN buffstore
[0927] TI:opcell 49, ccc 2, ccu 1
[0928] WAM:OUTPUT buffstore
[0929] WAM:CLOSE buffstore
COMMENT
[0930] The COMMENT command can be embedded in the integration construct data structure according to the invention.
[0931] PURPOSE: Adds a comment line to the WAMIL script.
[0932] SYNTAX: WAM:COMMENT string
[0933] EXAMPLE CALL: WAM:COMMENT This is test case jt1234
[0934] DESCRIPTION: The COMMENT command adds a comment line to the WAMIL script. The string given is ignored by the WAM Interpreter and not printed in the WAMIL log file. Alternatively, “#:” can be used in the same manner place of “WAM:COMMENT”, but it is less intuitive.
[0935] OUTPUT: None (in this WAMIL language embodiment).
[0936] ERRORS: None.
[0937] ALTERS: None (in this WAMIL language embodiment).
[0938] DEFAULT VALUE: None (in this WAMIL language embodiment).
[0939] SEE ALSO: WAM:PRINT string
CONFIG
[0940] The CONFIG command can be embedded in the integration construct data structure according to the invention.
[0941] PURPOSE: Changes the WAMI global cell configuration option number variable, CONFIG, to the value provided as an argument.
[0942] SYNTAX: WAM:CONFIG value
[0943] EXAMPLE CALL: WAM:CONFIG 350
[0944] DESCRIPTION: The WAM:CONFIG command sets the WAMI global CONFIG 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 configuration option number, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script cell configuration option number, will reference the new value.
[0945] 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.
[0946] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution an CONFIG command:
[0947] Set Cell Configuration Option To 350
[0948] ERRORS: None.
[0949] ALTERS: CONFIG
[0950] DEFAULT VALUE: CONFIG is set to 0 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 0.
[0951] SEE ALSO: WAM:INITIALIZE
[0952] EXAMPLE: The following script lines will set the script CONFIG option number to 350 and then execute a TI interface command:
[0953] WAM:CELL 49
[0954] WAM:BBA 4
[0955] WAM:CONFIG 350
[0956] TI:cfr:cell 49, multi bba 4; config 350
CONNECT
[0957] The CONFIG command can be embedded in the integration construct data structure according to the invention.
[0958] PURPOSE: Instructs the WAM Interpreter to initiate a connection to the interface specified as an argument.
[0959] SYNTAX: WAM:CONNECT interface
[0960] EXAMPLE CALL: WAM:CONNECT TI
[0961] DESCRIPTION: The CONNECT command instructs the WAM Interpreter to initiate a connection between the WAM Interpreter and the interface specified as an argument. The argument provided can (in this embodiment of the WAMIL language) be a valid interface supported by WAMIL.
[0962] After successful execution of the CONNECT command, the WAM Interpreter will open an xterm window for the interface specified as an argument. From that point forward until a DISCONNECT command for the same interface is executed, all (in this embodiment of the WAMIL language) corresponding interface commands when executed will be echoed to this window. The output or results of such execution will also be echoed to this window, and printed in the WAMIL report file.
[0963] Upon successful execution of the CONNECT command, the WAMI Interface flag will be set for the interface provided as an argument.
[0964] INTERFACES: The following interfaces are supported by the CONNECT command:
| INTERFACE | DESCRIPTION | |
|---|---|---|
| TI | TIpdunix | |
| SDP | Status Display Page | |
[0965] SCRIPTOR: A CONNECT command can (in this embodiment of the WAMIL language) exist in a WAMIL script prior to any interface command or a syntax error will occur.
[0966] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a CONNECT command for a TI interface:
[0967] Connect To TIpdunix on MSC 5
[0968] The following is an example of the output generated to the WAMIL report file upon execution of a CONNECT command for an SDP interface:
[0969] Connect To SDP on MSC 5
[0970] ERRORS: If the connection attempt fails due to lack of system or server response, the WAM Interpreter LFAIL flag will be set. The WAM Interpreter will then, for example, generate the following output to the WAMIL report file:
[0971] WAMI TIpdunix Connection Login Attempt Failed!
[0972] A user can test the LFAIL flag within a WAMIL script to check if a login attempt was successful prior to the execution of any (in this WAMIL language embodiment) interface commands for such interface.
[0973] Once a connection is established, if during the login attempt, or the execution of any (in this WAMIL language embodiment) WAMIL interface commands for such interface, the connection is lost, the WAM Interpreter will set the CFAIL flag. The WAM Interpreter will then, for example, generate the following output to the WAMIL report file:
[0974] WAMI TIpdunix Connection Lost!
[0975] A user can test the CFAIL flag within a WAMIL script to check if a connection was lost prior to the execution of any (in this WAMIL language embodiment) interface commands for such interface.
[0976] After successful execution of the CONNECT command, if the connection times out at any point during the execution of any (in this WAMIL language embodiment) interface commands for such interface, meaning no response is received from the interface within the time specified by the WAM Interpreter TimeOut variable, the WAM Interpreter TFAIL flag will be set. The WAM Interpreter will then, for example, generate the following output to the WAMIL report file:
[0977] TI Command Time Out!
[0978] A user can test the TFAIL flag at any (in this WAMIL language embodiment) time within a WAMIL script to check if an attempt did time out prior to the execution of any subsequent interface commands for such interface.
[0979] If a CONNECT command is executed for an SDP interface, and after a successful login attempt to the system or server no SDP port is available during the connection process, the WAM Interpreter SDPPORT flag will be set. The WAM Interpreter will then generate the following output to the WAMIL report file:
[0980] No SDP VTTY Ports! Try Again Later!
[0981] A user can test the SDPPORT flag within a WAMIL script to check if a port is available upon a login attempt, prior to the execution of any (in this WAMIL language embodiment) interface commands for the SDP interface.
[0982] If during an SDP connection attempt, or the execution of an SDP interface command, the WAM Interpreter detects an error on transmission or a page capture. The WAM Interpreter will then generate the following output to the WAMIL report file:
[0983] SDP Page Capture Error.
[0984] Redundant CONNECT commands for the same interface executed within a WAMIL script will generate an error if the interface is already connected to the WAM, unless the LOOPCELL command has been integrated into the script, and the script being executed is a Linker script.
[0985] ALTERS: WAM Interpreter interface flag for specified interface.
[0986] DEFAULT VALUE: The corresponding WAM Interpreter interface flag is always disabled upon initial startup and remains set after successful execution of a CONNECT command until a DISCONNECT or ENDTEST command is executed, or an unexpected disconnect occurs.
[0987] SEE ALSO: IF:SDPPORT, IF:CFAIL, IF:LFAIL, IF:TFAIL, WAM:DISCONNECT interface, WAM:ENDTEST, WAM:LOOPCELL cells . . . , WAM:LOOPCELLVARS
[0988] EXAMPLE: The following script will login to a TI interface, execute a TI command, and then log out:
[0989] WAM:MSC 5
[0990] WAM:CELL 49
[0991] WAM:CONFIG 150
[0992] WAM:CONNECT TI
[0993] IF:LFAIL
[0994] THENDO:
[0995] WAM:PRINT TI Connection Failed!
[0996] WAM:ENDTEST
[0997] ELSEDO:
[0998] TI:cfr:cell 49, multi bba 4; config 150
[0999] ENDIF:
[1000] WAM:DISCONNECT TI
[1001] WAM:ENDTEST
CREATEVAR
[1002] The CRATEVAR command can be embedded in the integration construct data structure according to the invention.
[1003] PURPOSE: Instructs the WAM Interpreter to create a new VAR variable provided by the argument new_var_name.
[1004] SYNTAX: WAM:CREATEVAR new_var_name
[1005] EXAMPLE CALL: WAM:CREATEVAR TEMPVAR
[1006] DESCRIPTION: The CREATEVAR command causes the WAMI to create a new interpreter VAR variable with the name new_var_name. The new VAR variable created will be of type integer. The new VAR variable can then be associated with any (in this WAMIL language embodiment) WAMI global variable by use of the SET command. The new VAR variable can then be referenced and operated upon like any (in this
[1007] WAMIL language embodiment) WAMI VAR variable. The new VAR variable name can (in this embodiment of the WAMIL language) have the suffix VAR. An auxiliary/complimentary non-key global variable is also created automatically.
[1008] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution a CREATEVAR command:
[1009] Created VAR variable TEMPVAR
[1010] ERRORS: If the VAR variable already exists an error is generated and script execution is terminated.
[1011] If an illegal VAR variable name is provided an error is generated and script execution is terminated.
[1012] ALTERS: None (in this WAMIL language embodiment)
[1013] DEFAULT VALUE: None (in this WAMIL language embodiment).
[1014] EXAMPLE: The following script will create a new VAR variable to hold the old generic name of the current cell:
[1015] WAM:MSCVAR
[1016] WAM:CELLVAR
[1017] WAM:GETAPXFLD cell2 Icelver
[1018] WAM:CREATEVAR OLD_GENVAR
[1019] WAM:SETVAR OLD_GENVAR APXVAR
[1020] WAM:ENDTEST
CSC
[1021] The CSC command can be embedded in the integration construct data structure according to the invention.
[1022] PURPOSE: Changes the WAMI global cell site controller variable, CSC, to the value provided as an argument.
[1023] SYNTAX: WAM:CSC value
[1024] EXAMPLE CALL: WAM:CSC 1
[1025] DESCRIPTION: The WAM:CSC command sets the WAMI global CSC 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 site controller number, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script cell site controller number, will reference the new value.
[1026] 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.
[1027] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution a CSC command:
[1028] Set Cell Site Controller 1
[1029] ERRORS: None.
[1030] ALTERS: CSC
[1031] DEFAULT VALUE: CSC is set to 0 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 0.
[1032] SEE ALSO: WAM:INITIALIZE
[1033] EXAMPLE: The following script will set the WAMIL script CSC variable to 1 and then execute a TI interface command:
[1034] WAM:CELL 49
[1035] WAM:CSC 1
[1036] TI:op:cell 49, csc 1
CSCVAR
[1037] The CSCVAR command can be embedded in the integration construct data structure according to the invention.
[1038] PURPOSE: Declares to the WAM Interpreter, that a value for the WAMI VAR variable CSCVAR will be supplied to the script.
[1039] SYNTAX: WAM:CSCVAR
[1040] EXAMPLE CALL: WAM:CSCVAR
[1041] DESCRIPTION: The WAM:CSCVAR 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 CSCVAR.
[1042] Like standard WAMI VAR variable declaration commands, the execution of this command also enables an association with the WAMI global CSC variable. Therefore, until the WAMI global CSC variable association is transferred to another WAMI VAR variable, or disabled, all (in this embodiment of the WAMIL language) references to the WAMI global CSC variable will use the CSCVAR variable value.
[1043] For script syntax, until an actual CSC number is passed as an argument, when a CSCVAR command is used the CSC number within a script shall be referenced as CSCVAR from that point forward.
[1044] 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.
[1045] WAMI GUI PLATFORM: Prior to execution of a WAMIL script, the WAMI GUI platform searches the script for special commands. If a WAM:CSCVAR is encountered the WAMI GUI platform will prompt the user for the script CSCVAR value. Subsequent WAM:CSCVAR commands encountered will not cause additional prompting.
[1046] SCRIPTOR: If a CSCVAR command is deleted from the current script, the Scriptor will prompt the user for a CSC number and then insert a WAM:CSC value command in place of the CSCVAR command deleted.
[1047] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution a CSCVAR command:
[1048] Set CSC To Argument Value of 1
[1049] ERRORS: If no command line value has been provided, the WAM Interpreter will generate an error and script execution will be aborted.
[1050] ALTERS: CSCVAR
[1051] DEFAULT VALUE: CSCVAR 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.
[1052] SEE ALSO: WAM:CSC value
[1053] EXAMPLE: The following script executes a TI command for the CSC number supplied:
[1054] WAM:MSC 5
[1055] WAM:CELL 49
[1056] WAM:CSCVAR
[1057] WAM:CONNECT TI
[1058] TI:op:cell 49, csc CSCVAR
[1059] WAM:DISCONNECT TI
[1060] WAM:ENDTEST
DATE
[1061] The DATE command can be embedded in the integration construct data structure according to the invention.
[1062] PURPOSE: Prints the current system date in the WAMIL report file.
[1063] SYNTAX: WAM:DATE
[1064] EXAMPLE CALL: WAM:DATE
[1065] DESCRIPTION: The DATE command prints the current system date to the WAMIL report file.
[1066] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a DATE command:
[1067] Date: 08/12/98
[1068] ERRORS: Any system errors generated during execution of the DATE command are printed to the WAMIL report file.
[1069] ALTERS: None (in this WAMIL language embodiment)
[1070] DEFAULT VALUE: None (in this WAMIL language embodiment).
[1071] SEE ALSO: WAM:TIME
DCCH
[1072] The DCCH command can be embedded in the integration construct data structure according to the invention.
[1073] PURPOSE: Changes the WAMI global dedicated/digital control channel number variable, DCCH, to the value provided as an argument.
[1074] SYNTAX: WAM:DCCH value
[1075] EXAMPLE CALL: WAM:DCCH 1
[1076] DESCRIPTION: The WAM:DCCH command sets the WAMI global dedicated/digital control channel 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 a dedicated/digital control channel number, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script dedicated/digital control channel 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.
[1077] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution of a DCCH command:
[1078] Set Dedicated/Digital Control Channel To 1
[1079] ERRORS: None.
[1080] ALTERS: DCCH
[1081] DEFAULT VALUE: DCCH is set to 0 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 0.
[1082] SEE ALSO: WAM:INITIALIZE
[1083] EXAMPLE: The following will set the WAMIL script DCCH variable to 1 and then execute a TI interface command:
[1084] WAM:CELL 49
[1085] WAM:DCCH 1
[1086] TI:op:cell 49, dcch 1
DCS
[1087] The DCS command can be embedded in the integration construct data structure according to the invention.
[1088] PURPOSE: Changes the WAMI global digital cellular switch number variable, DCS, to the value provided as an argument.
[1089] SYNTAX: WAM:DCS value
[1090] EXAMPLE CALL: WAM:DCS 1
[1091] DESCRIPTION: The WAM:DCS command sets the WAMI global digital cellular switch 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 a digital cellular switch number, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script digital cellular switch number, will reference the new value.
[1092] 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.
[1093] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution of a DCS command:
[1094] Set Digital Cellular Switch To 1
[1095] ERRORS: None.
[1096] ALTERS: DCS
[1097] DEFAULT VALUE: DCS is set to 0 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 0.
[1098] SEE ALSO: WAM:INITIALIZE
[1099] EXAMPLE: The following script lines set the WAMIL script DCS variable to 1 and then execute a TI interface command:
[1100] WAM:CELL 49
[1101] WAM:DCS 1
[1102] TI:rmv:dcs 1, dl 0
DECR
[1103] The DECR command can be embedded in the integration construct data structure according to the invention.
[1104] PURPOSE: Instructs the WAM Interpreter to decrement the WAMI global variable provided, by the value given.
[1105] SYNTAX: WAM:DECR global_variable value
[1106] EXAMPLE CALL: WAM:DECR BBA 2
[1107] DESCRIPTION: The DECR command decrements the current value of the WAMI global variable provided by the argument global_variable, by the value given. This command performs a straightforward subtraction. The WAMI global variable can (in this embodiment of the WAMIL language) be of type integer. The value given can (in this embodiment of the WAMIL language) be a valid integer number.
[1108] This command only (in this embodiment of the WAMIL language) operates on WAMI global variables. To decrement the value of a WAMI VAR variable use the DECRVAR command.
[1109] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution an DECR command:
[1110] Decrement BBA from 4 to 2
[1111] ERRORS: None.
[1112] ALTERS: WAMI global variable provided.
[1113] DEFAULT VALUE: None (in this WAMIL language embodiment).
[1114] SEE ALSO: WAM:INCR global_variable value
[1115] EXAMPLE: The following script decrements BBA by two and then executes a TI command using the new BBA value.
[1116] WAM:CELL 49
[1117] WAM:BBA 4
[1118] TI:op:cell 49, bba 4
[1119] WAM:DECR BBA 2
[1120] TI:op:cell 49, bba 2
DECRVAR
[1121] The DECRVAR command can be embedded in the integration construct data structure according to the invention.
[1122] PURPOSE: The DECRVAR command instructs the WAM Interpreter to decrement the WAMI VAR variable provided as an argument by the value given.
[1123] SYNTAX: WAM:DECRVAR var_variable value
[1124] EXAMPLE CALL: WAM:DECRVAR BBAVAR 1
[1125] DESCRIPTION: The DECRVAR command decrements the current value of the WAMI VAR variable provided by the argument var_variable, by the value given. This command performs a straightforward subtraction. The WAMI VAR variable can (in this embodiment of the WAMIL language) be of type integer. The value given can (in this embodiment of the WAMIL language) be a valid integer number.
[1126] This command only (in this embodiment of the WAMIL language) operates on WAMI VAR variables. To decrement the value of a WAMI global variable use the DECR command.
[1127] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution an DECRVAR command:
[1128] Decrement BBAVAR by 1
[1129] ERRORS: None.
[1130] ALTERS: WAMI VAR variable provided.
[1131] DEFAULT VALUE: None (in this WAMIL language embodiment).
[1132] SEE ALSO: WAM:INCRVAR var_variable value
[1133] EXAMPLE: The following script decrements BBAVAR by two and then executes a TI command using the new BBAVAR value.
[1134] WAM:CELL 49
[1135] WAM:BBAVAR
[1136] TI:op:cell 49, bba BBAVAR
[1137] WAM:DECRVAR BBAVAR 2
[1138] TI:op:cell 49, bba BBAVAR
DELCE
[1139] The DELCE command can be embedded in the integration construct data structure according to the invention.
[1140] PURPOSE: Changes the WAMI global number of channel elements to delete variable, DELCE, to the value provided as an argument.
[1141] SYNTAX: WAM:DELCE value
[1142] EXAMPLE CALL: WAM:DELCE 1
[1143] DESCRIPTION: The DELCE command sets the WAMI global number of channel elements to delete 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 the number of channel elements to delete variable, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script number of channel elements to delete variable, will reference the new value.
[1144] 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.
[1145] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution of a DELCE command:
[1146] Set Number Of Channel Elements To Delete To 1
[1147] ERRORS: None.
[1148] ALTERS: DELCE
[1149] DEFAULT VALUE: DELCE is set to 0 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 0.
[1150] SEE ALSO: WAM:INITIALIZE
DISCONNECT
[1151] The DISCONNECT command can be embedded in the integration construct data structure according to the invention.
[1152] PURPOSE: Instructs the WAM Interpreter to disconnect from the interface given, and terminate all (in this embodiment of the WAMIL language) its associated processes.
[1153] SYNTAX: WAM:DISCONNECT interface
[1154] EXAMPLE CALL: WAM:DISCONNECT TI
[1155] DESCRIPTION: The DISCONNECT command instructs the WAM Interpreter to disconnect from the interface specified as an argument. The argument provided can (in this embodiment of the WAMIL language) be a valid interface supported by WAMIL.
[1156] After successful execution of the DISCONNECT command, the WAM Interpreter will close the interface xterm window.
[1157] Upon execution of the DISCONNECT command, the WAMI interface flag will be reset for the interface provided as an argument.
[1158] If the WAMIL script is looping through multiple cells, meaning the LOOPCELL or LOOPCELLVARS command has been executed in the script, the DISCONNECT command is not executed until the script has been executed for the last cell.
[1159] INTERFACES: The following interfaces are supported by the DISCONNECT command:
| INTERFACE DESCRIPTION |
|---|
[1160] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a DISCONNECT command for a TI interface:
[1161] Disconnect From TIpdunix on MSC 5
[1162] ERRORS: If a DISCONNECT command is executed for an interface which is not active, the WAM Interpreter will generate an error.
[1163] If during the execution of a DISCONNECT command an associated process cannot be terminated, the WAM Interpreter will generate an error and terminate the WAMIL script.
[1164] If a DISCONNECT or ENDTEST command is not executed for an interface which is active, and the WAMIL script is terminated, the associated processes and xterm window will not be recognized by any (in this WAMIL language embodiment) subsequent WAMIL script execution, and the connection will exist indefinitely. Thus, it is always good practice to terminate any (in this WAMIL language embodiment) WAM Interpreter connections prior to termination of any script.
[1165] Errors which cause a WAMIL script execution to be terminated, close all (in this embodiment of the WAMIL language) xterm windows and terminate all (in this embodiment of the WAMIL language) active processes for all (in this embodiment of the WAMIL language) interfaces prior to termination of the WAMIL script.
[1166] ALTERS: WAM Interpreter interface flag for specified interface.
[1167] DEFAULT VALUE: The corresponding WAM Interpreter interface flag is always disabled upon initial startup and remains set after successful execution of a CONNECT command until a DISCONNECT or ENDTEST command is executed, or an unexpected disconnect occurs.
[1168] SEE ALSO: WAM:CONNECT interface, WAM:ENDTEST, WAM:LOOPCELL cells . . .
[1169] EXAMPLE: The following script will login to a TI interface, execute a TI command, and then log out:
[1170] WAM:MSC 5
[1171] WAM:CELL 49
[1172] WAM:CONFIG 150
[1173] WAM:CONNECT TI
[1174] TI:cfr:cell 49, multi bba 4; config 150
[1175] WAM:DISCONNECT TI
[1176] WAM:ENDTEST
DISPLAY
[1177] The DISPLAY command can be embedded in the integration construct data structure according to the invention.
[1178] PURPOSE: Instructs the WAM Interpreter to open an xterm window which allows a user to monitor the WAMIL script progress.
[1179] SYNTAX: WAM:DISPLAY seconds
[1180] EXAMPLE CALL: WAM:DISPLAY 2
[1181] DESCRIPTION: Execution of the DISPLAY command automatically opens an xterm window in which the output for each WAMIL command for the current script is printed. This output mimics the WAMIL report file.
[1182] The argument seconds allows the user to slow down the script execution to allow the viewing of progress. Thus an argument of 2 is interpreted as follows: execute a WAMIL command every 2 seconds.
[1183] The DISPLAY command is used as a debugging command. It is not recommended for a final script since each script line execution is slowed down by the number of seconds provided as an argument. Thus, an argument of 2 seconds for a script which has 100 commands, will add 200 seconds to the script total execution time.
[1184] Placement of the DISPLAY command can be in any (in this WAMIL language embodiment) location of a WAMIL script. The execution of the command itself generates no output to the WAMIL report file. Upon execution of a script, the WAM Interpreter first loads the entire script and checks each command for syntax errors prior to initiating execution. At this point, detection of the DISPLAY command causes the WAM Interpreter to immediately open a display xterm window. Thus, for clarity the DISPLAY command should be placed at the top of the script because the window is always opened prior to execution of the first script command.
[1185] Inclusion of a DISPLAY command in a linker script causes the WAM Interpreter Linker to open a display window to allow viewing of the execution of the linker script. This window is independent of any (in this WAMIL language embodiment) display windows opened by execution of linked WAMIL scripts which include the DISPLAY command. For differentiating purposes, the WAM Interpreter Linker display window color is green with yellow text, as opposed to the standard display window of an executed WAMIL script.
[1186] OUTPUT: Execution of the DISPLAY command does not generate any (in this WAMIL language embodiment) output to the WAMIL report file.
[1187] SCRIPTOR: The Scriptor automatically places this command at the top of the script. If the command already exists the current seconds is replaced with the new seconds, even if the command is edited or re-inserted.
[1188] ERRORS: If any (in this WAMIL language embodiment) system errors occur which do not permit a display window to be opened, the WAMIL script execution will continue nonetheless.
[1189] More than one DISPLAY command in a WAMIL script has no effect. However, the last DISPLAY command executed changes the display seconds if the argument is different.
[1190] ALTERS: DISPLAY command delay.
[1191] DEFAULT VALUE: The DISPLAY command delay is set to 1 upon initial startup. The WAM:INITIALIZE command also sets this variable to 1.
[1192] SEE ALSO: WAM:INITLALIZE
[1193] EXAMPLE: The following script opens a display window:
[1194] WAM:DISPLAY 1
[1195] WAM:MSC 5
[1196] WAM:CELL 49
[1197] WAM:CONNECT TI
[1198] TI:op:cell 49
[1199] WAM:DISCONNECT TI
[1200] WAM:ENDTEST
[1201] The DL command can be embedded in the integration construct data structure according to the invention.
[1202] PURPOSE: Changes the WAMI global cell site data link number variable, DL, to the value provided as an argument.
[1203] SYNTAX: WAM:DL value
[1204] EXAMPLE CALL: WAM:DL 1
[1205] DESCRIPTION: The WAM:DL command sets the WAMI global cell site data link 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 a cell site data link number, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script cell site data link number, will reference the new value.
[1206] 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.
[1207] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution of a DL command:
[1208] Set Cell Site Data Link To 1
[1209] ERRORS: None.
[1210] ALTERS: DL
[1211] DEFAULT VALUE: DL is set to 0 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 0.
[1212] SEE ALSO: WAM:INITIALIZE
[1213] EXAMPLE: The following script lines set the WAMIL script DL variable to 1 and then execute a TI interface command:
[1214] WAM:CELL 49
[1215] WAM:DCS 1
[1216] WAM:DL 1
[1217] TI:rmv:dcs 1, dl 1
DS1
[1218] The DS 1 command can be embedded in the integration construct data structure according to the invention.
[1219] PURPOSE: Changes the WAMI global digital service 1 variable, DS1, to the value provided as an argument.
[1220] SYNTAX: WAM:DS1 value
[1221] EXAMPLE CALL: WAM:DS1 1
[1222] DESCRIPTION: The WAM:DS1 command sets the WAMI global digital service 1 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 a digital service 1 number, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script digital service 1 number, will reference the new value.
[1223] 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.
[1224] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution of a DS1 command:
[1225] Set DS1 (Digital Service 1) To 1
[1226] ERRORS: None.
[1227] ALTERS: DS1
[1228] DEFAULT VALUE: DS1 is set to 0 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 0.
[1229] SEE ALSO: WAM:INITIALIZE
[1230] EXAMPLE: The following script lines set the WAMIL script DS1 variable to 1 and then execute a TI interface command:
[1231] WAM:CELL 49
[1232] WAM:DS1 1
[1233] TI:op:cell 49, ds1 1
ECP
[1234] The ECP command can be embedded in the integration construct data structure according to the invention.
[1235] PURPOSE: Changes the WAMI global executive cellular processor number variable, ECP, to the value provided as an argument.
[1236] SYNTAX: WAM:ECP value
[1237] EXAMPLE CALL: WAM:ECP 1
[1238] DESCRIPTION: The WAM:ECP command sets the WAMI global executive cellular processor 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 a executive cellular processor number, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script executive cellular processor number, will reference the new value.
[1239] 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.
[1240] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution of a ECP command:
[1241] Set Executive Cellular Processor To 1
[1242] ERRORS: None.
[1243] ALTERS: ECP
[1244] DEFAULT VALUE: ECP is set to 0 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 0.
[1245] SEE ALSO: WAM:INITIALIZE
[1246] EXAMPLE: The following script lines set the WAMIL script ECP variable to 1 and then performs a backup of the ecp translation form:
[1247] WAM:CELL 49
[1248] WAM:ECP 1
[1249] WAM:GETAPX ecp ECPBACKUP
EMAILME
[1250] The EMAILME command can be embedded in the integration construct data structure according to the invention.
[1251] PURPOSE: Instructs the WAM Interpreter to email the string provided as an argument to the user.
[1252] SYNTAX: WAM:EMAILME string
[1253] EXAMPLE CALL: WAM:EMAILME Test Has Completed!
[1254] DESCRIPTION: Execution of the EMAILME command automatically emails the string provided to the user. The subject matter in the email message is always the script name.
[1255] The string provided can include references to WAMI global variables, or WAMI VARn variables. To reference a WAMI global variable the suffix VAR is simply added to the WAMI global variable name. For example, the following string, CCC CCCVAR is OOS, will be interpreted and emailed as follows for a WAMI global CCC variable with a value of 4:
[1256] CCC 4 is OOS
[1257] This is not to be mistaken with WAMI VAR variables. Although when referencing WAMI global variables within strings to be printed the names resemble WAMI VAR variables, this naming convention was chosen to allow references to WAMI global variables and still be able to print the variable name. In the above example the WAMI global name CCC was printed along with the value of the WAMI global variable. To print the value of a WAMI VAR variable, a WAMI global variable can (in this embodiment of the WAMIL language) first be associated. Then references to the WAMI global variable will yield the value of the WAMI VAR variable it is associated with.
[1258] OUTPUT: Execution of the EMAILME command does not generate any (in this WAMIL language embodiment) output to the WAMIL report file.
[1259] ERRORS: If any (in this WAMIL language embodiment) system errors occur which do not permit a string to be emailed to a user, the string will simply not be emailed.
[1260] ALTERS: None (in this WAMIL language embodiment).
[1261] DEFAULT VALUE: None (in this WAMIL language embodiment).
[1262] SEE ALSO: WAM:EMAILRPT
[1263] EXAMPLE: The following script will email messages to a user during execution of the script:
[1264] WAM:MSC 5
[1265] WAM:CELL 49
[1266] WAM:CONNECT TI
[1267] IF:LFAIL
[1268] THENDO:
[1269] WAM:EMAILRPT
[1270] WAM:ENDTEST
[1271] ELSEDO:
[1272] WAM:EMAILME TI Connection Initiated! Test Started.
[1273] ENDIF:
[1274] TI:op:cell 49
[1275] WAM:DISCONNECT TI
[1276] WAM:EMAILME SCRIPT_NAME Execution Completed!
[1277] WAM:ENDTEST
EMAILRPT
[1278] The EMAILRPT command can be embedded in the integration construct data structure according to the invention.
[1279] PURPOSE: Instructs the WAM Interpreter to email the entire WAMIL report file to the user after the script execution has been completed or terminated.
[1280] SYNTAX: WAM:EMAILRPT
[1281] EXAMPLE CALL: WAM:EMAILRPT
[1282] DESCRIPTION: Execution of the EMAILRPT command automatically sets a flag which instructs the WAM Interpreter to email the user the entire WAMIL report file upon completion of the script execution, or its termination. The subject matter in the email is always the script name.
[1283] Placement of the EMAILRPT command can be in any (in this WAMIL language embodiment) location of a WAMIL script. Therefore execution of the command can occur as needed. If the command is executed the email flag is set and upon completion of the script the WAM Interpreter will email the entire WAMIL report file to the user.
[1284] OUTPUT: Execution of the EMAILRPT command does not generate any (in this WAMIL language embodiment) output to the WAMIL report file.
[1285] ERRORS: If any (in this WAMIL language embodiment) system errors occur which do not permit a WAMIL report file to be emailed to a user, the WAMIL report file will simply not be emailed.
[1286] Multiple EMAILRPT commands in a WAMIL script have no effect.
[1287] ALTERS: WAM Interpreter email flag.
[1288] DEFAULT VALUE: The WAM Interpreter email flag is always disabled upon startup.
[1289] SEE ALSO: WAM:EMAILME string
[1290] EXAMPLE: The following script will email the WAMIL report file to the user if a TI connection attempt fails:
[1291] WAM:MSC 5
[1292] WAM:CELL 49
[1293] WAM:CONNECT TI
[1294] IF:LFAIL
[1295] THENDO:
[1296] WAM:PRINT Cannot Connect To TI!!!!
[1297] WAM:EMAILRPT
[1298] WAM:ENDTEST
[1299] ELSEDO:
[1300] TI:op:cell 49
[1301] ENDIF:
[1302] WAM:DISCONNECT TI
[1303] WAM:ENDTEST
ENDTEST
[1304] The ENDTEST command can be embedded in the integration construct data structure according to the invention.
[1305] PURPOSE: Instructs the WAM Interpreter to terminate the WAMIL script.
[1306] SYNTAX: WAM:ENDTEST
[1307] EXAMPLE CALL: WAM:ENDTEST
[1308] DESCRIPTION: The ENDTEST command instructs the WAM Interpreter to immediately terminate the current WAMIL script in execution.
[1309] Upon execution, the ENDTEST command will close all (in this embodiment of the WAMIL language) active WAM Interpreter xterm windows and terminate all (in this embodiment of the WAMIL language) associated processes. The WAMIL report file will then be closed and saved and the WAMIL script will be terminated, along with the script status display window.
[1310] If the WAMIL script is looping through multiple cells, meaning the LOOPCELL or LOOPCELLVARS command has been executed in the script, the ENDTEST command is not executed until the script has been executed for the last cell.
[1311] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of an ENDTEST command:
[1312] ENDTEST MSC 5 CELL 49
[1313] END OF TEST SCRIPT EXECUTION
[1314] SCRIPTOR: The Scriptor will generate a syntax error if no ENDTEST command is inserted at the end of a script.
[1315] ERRORS: See DISCONNECT.
[1316] If no ENDTEST command is included at the end of a WAMIL script, the script will still terminate but connections established will remain nailed up, and associated processes will not be terminated.
[1317] ALTERS: None (in this WAMIL language embodiment).
[1318] DEFAULT VALUE: None (in this WAMIL language embodiment).
[1319] SEE ALSO: THEN:ENDTEST, WAM:DISCONNECT interface, WAM:LOOPCELL cells, WAM:LOOPCELLVARS
[1320] EXAMPLE: The following script will execute a TI command and then end:
[1321] WAM:MSC 5
[1322] WAM:CELL 49
[1323] WAM:BBA 4
[1324] WAM:CONFIG 150
[1325] WAM:CONNECT TI
[1326] TI:cfr:cell 49, multi bba 4; config 150
[1327] WAM:DISCONNECT TI
[1328] WAM:ENDTEST
EXEC
[1329] The EXEC command can be embedded in the integration construct data structure according to the invention.
[1330] PURPOSE: Instructs the WAM Interpreter to execute the WAMIL script provided as an argument.
[1331] SYNTAX: WAM:EXEC path wamil_script
[1332] EXAMPLE CALL: WAM:EXEC HOME jt1234
[1333] DESCRIPTION: The EXEC command instructs the WAM Interpreter to execute the WAMIL script, provided by the argument wamil_script, located at path.
[1334] Upon execution of this command the WAM Interpreter will load the sub-WAMIL script, and additional interface sessions if necessary will be established. Interface sessions already existing from the calling WAMIL script will not be re-opened but used during the execution of the called sub-WAMIL script, if needed.
[1335] Once the sub-WAMIL script starts execution, the calling script will halt in progress. The calling script will not continue to be executed until the sub-WAMIL script has completed, or been terminated. Once the sub-WAMIL script has completed, execution in the calling script will resume at the next line after the EXEC command which was executed.
[1336] All WAMI global and WAMI VAR variables can be altered by a sub-WAMIL script since all (in this embodiment of the WAMIL language) these variables are visible to all (in this embodiment of the WAMIL language) sub-WAMIL scripts. To avoid inadvertent altering of WAMI global and WAMI VAR variables, a user can execute the SAVEWAMI command prior to any (in this WAMIL language embodiment) EXEC command execution, and then return the WAMI global and WAMI VAR variables to their initial states by executing the RESTOREWAMI command after the EXEC command.
[1337] The argument path can be any (in this WAMIL language embodiment) valid, complete UNIX pathname. The EXEC command supports WAM Interpreter path keywords which can be used for the path argument.
[1338] OUTPUT: All output from a sub-WAMIL script is printed in the calling script WAMIL report file. The following is an example of the output generated to the WAMIL report file upon execution of an EXEC command:
[1339] Execute sub-WAMILjt1234 From HOME.
[1340] Upon completion of the sub-WAMIL script, the following is an example of the output generated to the WAMIL report file.
[1341] Sub-WAMIL jt1234 Execution Completed.
[1342] ERRORS: If an invalid path is provided as an argument, the WAM Interpreter will generate an error and the sub-WAMIL script will not be executed.
[1343] If an invalid WAMIL script name is provided as an argument, the WAM Interpreter will generate an error and no sub-WAMIL script will be executed.
[1344] ALTERS: All WAMI global and WAMI VAR variables which are altered in the sub-WAMIL script executed.
[1345] DEFAULT VALUE: All WAMI global and WAMI VAR variables values prior to the sub-WAMIL script execution.
[1346] SEE ALSO: WAM:LAUNCH path wamil_script -options . . .
[1347] EXAMPLE: The following script will execute a sub-WAMIL script:
[1348] WAM:MSC 5
[1349] WAM:CELL 49
[1350] WAM:CONNECT TI
[1351] TI:init:cell 49: boot; sw
[1352] WAM:DISCONNECT TI
[1353] WAM:EXEC SHARE jt1234_wrapup
[1354] WAM:ENDTEST
FLUSHBUFF
[1355] The FLUSHBUFF command can be embedded in the integration construct data structure according to the invention.
[1356] PURPOSE: Instructs the WAM Interpreter to flush OutBuff.
[1357] SYNTAX: WAM:FLUSHBUFF
[1358] EXAMPLE CALL: WAM:FLUSHBUFF
[1359] DESCRIPTION: The FLUSHBUFF command instructs the WAM Interpreter to immediately flush the contents of the internal main buffer OutBuff. Upon execution of this command, OutBuff will be empty.
[1360] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a FLUSHBUFF command:
[1361] Flush WAMI Buffer
[1362] ERRORS: None.
[1363] ALTERS: OutBuff.
[1364] DEFAULT VALUE: None (in this WAMIL language embodiment).
[1365] SEE ALSO: FLUSHIP
[1366] EXAMPLE: The following script lines will execute a TI command and then flush OutBuff:
[1367] WAM:CELL 49
[1368] WAM:BBA 4
[1369] WAM:CONFIG 150
[1370] TI:cfr:cell 49, multi bba 4; config 150
[1371] WAM:FLUSHBUFF
FLUSHIP
[1372] The FLUSHIP command can be embedded in the integration construct data structure according to the invention.
[1373] PURPOSE: Instructs the WAM Interpreter to flush OutBuff up to the next incoming IP output message of the TI interface messages.
[1374] SYNTAX: WAM:FLUSHIP
[1375] EXAMPLE CALL: WAM:FLUSHIP
[1376] DESCRIPTION: The FLUSHIP command exists as a means of removing unwanted messages from OutBuff which may have been generated from any (in this WAMIL language embodiment) previously executed TI command. This command can (in this embodiment of the WAMIL language) be executed prior to execution of the desired TI interface command from which output messages from any previously executed TI command need to be removed from.
[1377] The FLUSHIP command when executed sets a flag. After execution of the next TI interface command, this flag setting instructs the WAM Interpreter to remove messages in OutBuff up to but not including the first IP message in OutBuff. If no IP message is encountered nothing is removed from OutBuff. After the removal of any or no messages the flag is reset.
[1378] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a FLUSHIP command:
[1379] Flush WAMI Buffer To Next IP Message Upon Input
[1380] ERRORS: None.
[1381] ALTERS: OutBuff.
[1382] DEFAULT VALUE: None (in this WAMIL language embodiment).
[1383] SEE ALSO: FLUSHBUFF
[1384] EXAMPLE: The following script lines execute a TI command, and then flushes OutBuff up to the next IP message after execution of a second TI command:
[1385] WAM:CELL 49
[1386] WAM:BBA 4
[1387] TI:init:cell 49: boot; sw
[1388] WAM:FLUSHIP
[1389] TI:op:cell 49
FLUSHTAGS
[1390] The FLUSHTAGS command can be embedded in the integration construct data structure according to the invention.
[1391] PURPOSE: Instructs the WAM Interpreter to flush the internal TAGS FIFO buffer.
[1392] SYNTAX: WAM:FLUSHTAGS
[1393] EXAMPLE CALL: WAM:FLUSHTAGS
[1394] DESCRIPTION: The FLUSHTAGS command instructs the WAM Interpreter to immediately flush the contents of the internal TAGS FIFO buffer. Upon execution of this command the TAGS FIFO buffer will be empty.
[1395] The TAGS FIFO buffer holds unique tag numbers for each TI command executed in the script. These tag numbers are included in output messages generated by TI commands, and are unique for each message. The TAGS FIFO buffer is a First-In-First-Out buffer. Therefore the order of the tag numbers in the buffer is the same order as the TI commands executed within the script.
[1396] The TAGS FIFO buffer is used by the GETROP command. To retrieve ROP information refer to the GETROP command.
[1397] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a FLUSHTAGS command:
[1398] Flush TAGS FIFO Buffer
[1399] ERRORS: None.
[1400] ALTERS: TAGS FIFO buffer.
[1401] DEFAULT VALUE: None (in this WAMIL language embodiment).
[1402] SEE ALSO: GETROP get_rop_keyword range pattern
GEN
[1403] The GEN command can be embedded in the integration construct data structure according to the invention.
[1404] PURPOSE: Changes the WAMI global generic load number variable, GEN, to the value provided as an argument.
[1405] SYNTAX: WAM:GEN value
[1406] EXAMPLE CALL: WAM:GEN a34Y012t
[1407] DESCRIPTION: The WAM:GEN command sets the WAMI global generic load 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 a generic load number, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script generic load number, will reference the new value.
[1408] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution of a GEN command:
[1409] Set Generic To a34Y012t
[1410] ERRORS: None.
[1411] ALTERS: GEN
[1412] DEFAULT VALUE: GEN is set to 0 upon initial startup, and is of type string. The WAM:INITIALIZE command also sets this variable to 0.
[1413] SEE ALSO: WAM:GETGEN, WAM:INITIALIZE
[1414] EXAMPLE: The following script lines set the WAMIL script GEN variable to a34Y012t and then executes TI command:
[1415] WAM:CELL 49
[1416] WAM:GEN a34Y012t
[1417] TI:upd:cell, generic a34Y012t, dlt; uc1
GENVAR
[1418] The GENVAR command can be embedded in the integration construct data structure according to the invention.
[1419] PURPOSE: Declares to the WAM Interpreter, that a value for the WAMI VAR variable GENVAR will be supplied to the script.
[1420] SYNTAX: WAM:GENVAR
[1421] EXAMPLE CALL: WAM:GENVAR
[1422] DESCRIPTION: The WAM:GENVAR 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 GENVAR.
[1423] Like standard WAMI VAR variable declaration commands, the execution of this command also enables an association with the WAMI global GEN variable. Therefore, until the WAMI global GEN variable association is transferred to another WAMI VAR variable, or disabled, all (in this embodiment of the WAMIL language) references to the WAMI global GEN variable will use the GENVAR variable value.
[1424] For script syntax, until an actual GEN number is passed as an argument, when a GENVAR command is used the GEN number within a script shall be referenced as GENVAR from that point forward.
[1425] 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.
[1426] WAMI GUI PLATFORM: Prior to execution of a WAMIL script, the WAMI GUI platform searches the script for special commands. If a WAM:GENVAR is encountered the WAMI GUI platform will prompt the user for the script GENVAR value. Subsequent WAM:GENVAR commands encountered will not cause additional prompting.
[1427] SCRIPTOR: If a GENVAR command is deleted from the current script, the Scriptor will prompt the user for a GEN number and then insert a WAM:GEN value command in place of the GENVAR command deleted.
[1428] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution a GENVAR command:
[1429] Set Generic To Argument Value of a3412Y.0T
[1430] ERRORS: If no command line value has been provided, the WAM Interpreter will generate an error and script execution will be aborted.
[1431] ALTERS: GENVAR
[1432] DEFAULT VALUE: GENVAR 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.
[1433] SEE ALSO: WAM:GEN value
[1434] EXAMPLE: The following script verifies if the generic for the current cell is equal to a generic number supplied by the user:
[1435] WAM:MSCVAR
[1436] WAM:CELLVAR
[1437] WAM:GENVAR
[1438] WAM:CONNECT TI
[1439] TI:op:cell, generic
[1440] WAM:DISCONNECT TI
[1441] IF:GENERIC GENVAR
[1442] THEN:PRINT Generic is valid.
[1443] ELSE:PRINT Generic is NOT valid.
[1444] WAM:ENDTEST
GETAPX
[1445] The GETAPX command can be embedded in the integration construct data structure according to the invention.
[1446] PURPOSE: Instructs the WAM Interpreter to save the APXRCV DB form provided as an argument.
[1447] SYNTAX: WAM:GETAPX db_form_name db_file_name
[1448] EXAMPLE CALL: WAM:GETAPX fci FCIBACKUP
[1449] DESCRIPTION: The GETAPX command is a special WAMI functional command which instructs the WAM Interpreter (WAMI) to save the APXRCV DB form, provided by the argument db_form_name, in the current script output directory under the name db_file_name.
[1450] The current script output directory is set through the WAMI GUI platform via the user configuration options, or by command line execution of the WAM Interpreter with the -rpt switch, and defaults to Scripts.dir if no sub-directory is specified.
[1451] The DB form filename is automatically given the extension .dbf
[1452] The APXRCV DB form saved will depend on the current values of the WAMI global variables prior to execution of the GETAPX command. For example, if the WAMI global variable CELL is set to 49, and SG is set to 1, and ANT is set to 1, and the following command is executed:
[1453] WAM:GETAPX fci FCIBACKUP
[1454] The fci translation DB form for cell 49, server group 1, antenna face 1 will be saved in the filename FCIBACKUP.
[1455] If the filename provided as an argument already exists when the GETAPX command is executed, the pre-existing file will be overwritten.
[1456] DB FORMS: The following is a list of APXRCV DB forms supported by the GETAPX command:
| DB FORM NAME |
|---|
[1457] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a GETAPX command:
[1458] Get APXRCV DB Form fci and Save in FCIBACKUP File.
[1459] Upon completion of the GETAPX command, the following is an example of the output generated to the WAMIL report file:
[1460] WAMI AXPRCV fci Data Retrieved.
[1461] ERRORS: If during the initial login attempt the connection attempt fails due to lack of system response, the WAM Interpreter LFAIL flag will be set. The WAM Interpreter will then, for example, generate the following output to the WAMIL report file:
[1462] WAMI OMP 5 Timeout. Login Attempt Failed!
[1463] A user can test the LFAIL flag within a WAMIL script to check if a login attempt was successful prior to the execution of any (in this WAMIL language embodiment) subsequent WAMIL commands.
[1464] If during the initial login attempt the connection once established is lost, the WAM Interpreter CFAIL flag will be set. The WAM Interpreter will then, for example, generate the following output to the WAMIL report file:
[1465] WAMI OMP 5 Connection Lost!
[1466] A user can test the CFAIL flag within a WAMIL script to check if a connection was lost prior to the execution of any (in this WAMIL language embodiment) subsequent WAMIL commands.
[1467] Once a connection is established, if during the APXRCV session the connection is lost, the WAM Interpreter will set the CFAIL flag also. The WAM Interpreter will then, for example, generate the following output to the WAMIL report file:
[1468] WAMI APXRCV Session Connection Lost!
[1469] If the connection times out at any (in this WAMIL language embodiment) point during the retrieval of data from the APXRCV, meaning no response is received from the APXRCV within the time specified by the WAMI global TimeOut variable, the WAM Interpreter TFAIL flag will be set. The WAM Interpreter will then, for example, generate the following output to the WAMIL report file:
[1470] WAMI APXRCV Timeout!
[1471] A user can test the TFAIL flag within a WAMIL script to check if the data retrieval did not time out prior to the execution of any (in this WAMIL language embodiment) subsequent WAMIL commands.
[1472] If an invalid, or not supported, DB form is provided as an argument, the WAM Interpreter will generate an error.
[1473] If an error occurs in saving the APXRCV DB form file, the WAM Interpreter will generate an error and the form will not be saved.
[1474] During execution of the GETAPX command, all (in this embodiment of the WAMIL language) APXRCV errors and messages will be printed to the WAMIL report file.
[1475] ALTERS: None (in this WAMIL language embodiment).
[1476] DEFAULT VALUE: None (in this WAMIL language embodiment).
[1477] SEE ALSO: WAM:GETAPXFLD db_form_name db_field_name, WAM:PUTAPX db_form_name db_file_name
[1478] EXAMPLE: The following script will save the fci DB form for all antenna faces, for cell 49, server group 1:
[1479] WAM:MSC 5
[1480] WAM:CELL 49
[1481] WAM:SG 1
[1482] WAM:ANT 1
[1483] WAM:GETAPX fci FCIBACKUP1
[1484] WAM:ANT 2
[1485] WAM:GETAPX fci FCIBACKUP2
[1486] WAM:ANT 3
[1487] WAM:GETAPX fci FCIBACKUP3
[1488] WAM:ENDTEST
GETAPXFLD
[1489] The GETAPXFLD command can be embedded in the integration construct data structure according to the invention.
[1490] PURPOSE: Instructs the WAM Interpreter to get the APXRCV DB form field name, provided as an argument, and set the WAMI VAR variable APXVAR to the field value.
[1491] SYNTAX: WAM:GETAPXFLD db_form_name db_field_name
[1492] EXAMPLE CALL: WAM:GETAPXFLD ceqsu2 rmi_thresh
[1493] DESCRIPTION: The GETAPXFLD command instructs the WAM Interpreter to get the APXRCV DB form field name, provided by the argument db_field_name, located in the DB form db_form_name, and set the WAMI VAR variable APXVAR to the field value.
[1494] The APXRCV DB form field retrieved will depend on the current value of the WAMI global variables prior to execution of the GETAPXFLD command. For example, if the WAMI global variable CELL is set to 49, and ANT is set to 1, and the following command is executed:
[1495] WAM:GETAPXFLD ceqsu2 rmi_thresh
[1496] The WAMI VAR variable APXVAR will be set to the ceqsu2 DB form rmi_thresh field value, for cell 49, antenna face 1.
[1497] If the DB form field name provided as an argument does not exist, the APXVAR variable will be set to INVALID.
[1498] DB FORMS: For a list of APXRCV DB forms supported by this command refer to the GETAPX command.
[1499] OUTPUT: The GETAPXFLD command automatically executes a GETAPX command, in the process creating a default DB filename. Therefore the initial output generated by this command is the same as execution of the GETAPX command to retrieve an entire DB form. Once the entire DB form has been retrieved, the GETAPXFLD command will search through the file and locate the desired field. The output generated upon completion of this process will then be the following:
[1500] Get APXRCV DB Form ceqsu2 Field rmi_thresh:
[1501] Field rmi_thresh=0
[1502] The DB form filename is given the name GET_db_form_name.dbf. For example, the command, WAM:GETAPXFLD cell2 vssw, will create a default DB file called GET_cell2.dbf in the script output directory. If this default file already exists in the script output directory, the GETAPXFLD command will simply search the file for the desired db_field_name.
[1503] ERRORS: See GETAPX command.
[1504] If an error occurs in retrieving the APXRCV DB form field value, the WAM Interpreter will generate an error and the field will not be retrieved. The APXVAR variable will then be set to ERROR.
[1505] ALTERS: APXVAR.
[1506] DEFAULT VALUE: APXVAR is set to NULL upon initial startup, and is of type string. The WAM:INITIALIZE command does not alter this variable.
[1507] SEE ALSO: WAM:GETAPX db_form_name db_file_name, WAM:PUTAPXFLD db_form_name db_field_name
[1508] EXAMPLE: The following script will retrieve a field value from an APXRCV DB form, set the value to zero, and at the end restore the DB form to its original state:
[1509] WAM:MSC 5
[1510] WAM:CELL 49
[1511] WAM:ANT 1
[1512] WAM:GETAPXFLD ceqsu2 rmi_thresh
[1513] IF:APXVAR NE 0
[1514] THENDO:
[1515] WAM:SETVAR APXVAR 0
[1516] WAM:PUTAPXFLD ceqsu2 rmi_thresh
[1517] ELSEDO:
[1518] ENDIF:
[1519] WAM:PUTAPX ceqsu2 GET_ceqsu2
[1520] WAM:ENDTEST
GETCELLS
[1521] The GETCELLS command can be embedded in the integration construct data structure according to the invention.
[1522] PURPOSE: Instructs the WAM Interpreter to retrieve all (in this embodiment of the WAMIL language) the cell numbers for the current MSC.
[1523] SYNTAX: WAM:GETCELLS
[1524] EXAMPLE CALL: WAM:GETCELLS
[1525] DESCRIPTION: The GETCELLS command is a special function command. When executed it automatically loads all (in this embodiment of the WAMIL language) the cell numbers for the current MSC into the WAMI VARn CELL List. Upon successful execution the GETCELLS command will set the WAMI VAR variable WAMVAR to the total number of cells on the current MSC.
[1526] This command is only (in this embodiment of the WAMIL language) effective if the previously executed TI interface command was the TI:op:cell, generic command, and OutBuff holds the output of such command. Otherwise, WAMVAR will be set to 0, and the WAMI VARn List will remain unchanged.
[1527] The GETCELLS command is a multi-operational command. Upon successful execution, the CELL numbers retrieved are assigned to the WAMI VARn CELL List, meaning a CELL List is automatically declared within the script. The CELL numbers within the CELL List can then be referenced within the script as WAMI VARn variables, according to their index position in the list. For example, CELLVAR2 refers to the second CELL number in the CELL List. The GETCELLS command assigns the CELL numbers in numerical order.
[1528] Also, like standard WAMI VARn variable assignment commands, the execution of this command also enables an association with the WAMI global CELL variable. Therefore, until the WAMI global CELL variable association is transferred to a WAMI VAR variable, or disabled, all (in this embodiment of the WAMIL language) references to the WAMI global CELL variable will use the CELLVAR1 value. Thus upon successful execution of the GETCELLS command the WAMI global CELL variable is immediately associated with CELLVAR1, as if a WAM:CELLVAR1 command had also been executed. Therefore this command not only (in this embodiment of the WAMIL language) retrieves cell numbers but acts as if a WAM:CELLLIST and WAM:CELLVAR1 command had been executed sequentially.
[1529] For script syntax, upon successful execution of the GETCELLS command, the CELL number within a script shall be referenced as CELLVAR1 from that point forward.
[1530] If more than one GETCELLS command is used in a WAMIL script, the new cell numbers retrieved will overwrite the pre-existing cell numbers in the CELL List.
[1531] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a GETCELLS command:
[1532] Total Number Of Cells on MSC 5 is 4
[1533] CELL List Values: 2 49 101 160
[1534] ERRORS: If the GETCELLS command is executed, and the previous TI interface command executed was not TI:op:cell, generic the WAM Interpreter will print the following warning message to the WAMIL report file:
[1535] WARNING:
[1536] Current MSC Cell Numbers Not Retrieved.
[1537] Must Execute TI:op:cell, generic Command First!
[1538] Any references within a script to a WAMI VARn CELL List variable prior to the declaration of the CELL List, in this case the successful execution of the GETCELLS command, will generate a syntax error.
[1539] ALTERS: WAMI VARn CELL List, WAMVAR
[1540] DEFAULT VALUE: The WAMI VARn CELL List variable is set to 0 upon initial startup, and is of type integer, meaning only (in this embodiment of the WAMIL language) CELLVAR1 has a value of zero. The WAM:INITIALIZE command does not reset this list.
[1541] SEE ALSO: WAM:GETGEN
[1542] EXAMPLE: The following script executes a TI command on all the MSC cells:
[1543] WAM:MSC 5
[1544] WAM:CONNECT TI
[1545] TI:op:cell, generic
[1546] WAM:GETCELLS
[1547] IF:WAMVAR NE 0
[1548] THENDO:
[1549] WAM:SET WAMI 1
[1550] WAM:SET CELL CELLVAR
[1551] WHILE:TEST_EXPR WAMI LTE WAMVAR
[1552] WAM:GETLISTVAR CELLVAR CELLLIST WAM
[1553] TI:op:cell CELLVAR
[1554] IF:OMSG COMPLETED
[1555] THEN:CONTINUE
[1556] ELSE:WAITQUERY 10 TI 2
[1557] INCR WAMI 1
[1558] ENDWHILE:
[1559] ELSEDO:
[1560] WAM:PRINT No Cells on MSC MSCVAR
[1561] ENDIF:
[1562] WAM:DISCONNECT TI
[1563] WAM:ENDTEST
GETGEN
[1564] The GETGEN command can be embedded in the integration construct data structure according to the invention.
[1565] PURPOSE: Instructs the WAM Interpreter to retrieve the generic value for the current cell number and set the WAMI global variable GEN to that value.
[1566] SYNTAX: WAM:GETGEN
[1567] EXAMPLE CALL: WAM:GETGEN
[1568] DESCRIPTION: The GETGEN command when executed automatically sets the WAMI global variable GEN to the generic value for the current cell number defined by the WAMI global variable CELL.
[1569] Successful 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.
[1570] This command is only (in this embodiment of the WAMIL language) effective if the previously executed TI interface command was the TI:op:cell, generic command, and OutBuff holds the output of such command. Otherwise, the WAMI global variable GEN will remain unchanged.
[1571] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a GETGEN command:
[1572] Current Cell 49 Generic: a34Y012t
[1573] ERRORS: If the GETGEN command is executed, and the previous TI interface command executed was not TI:op:cell, generic the WAM Interpreter will print the following warning message to the WAMIL report file:
[1574] WARNING:
[1575] Current Cell Generic Not Retrieved.
[1576] Must Execute TI:op:cell, generic Command First!
[1577] ALTERS: GEN.
[1578] DEFAULT VALUE: None (in this WAMIL language embodiment).
[1579] SEE ALSO: WAM:GEN value
[1580] EXAMPLE: The following script will execute a sub-WAMIL script on all cells with the generic value specified by the user:
[1581] WAM:MSC 5
[1582] WAM:WAMLIST Enter Generic Value For Cells To Be Tested
[1583] WAM:CONNECT TI
[1584] TI:op:cell, generic
[1585] WAM:GETCELLS
[1586] IF:WAMVAR NE 0
[1587] THENDO:
[1588] WAM:SET WAMI 1
[1589] WAM:SET CELL CELLVAR
[1590] WHILE:TEST EXPR_WAMVAR NE 0
[1591] WAM:GETLISTVAR CELLVAR CELLLIST WAM
[1592] WAM:GETGEN
[1593] IF:GENERIC WAMVAR1
[1594] THENDO:
[1595] WAM:EXEC CERT jt1234
[1596] ELSEDO
[1597] ENDIF:
[1598] WAM:INCR WAMI 1
[1599] WAM:DECRVAR WAMVAR 1
[1600] ENDWHILE:
[1601] ELSEDO:
[1602] WAM:PRINT No Cells on MSC MSCVAR Tested
[1603] ENDIF:
[1604] WAM:DISCONNECT TI
[1605] WAM:ENDTEST
GETLISTVAR
[1606] The GETLISTVAR command can be embedded in the integration construct data structure according to the invention.
[1607] PURPOSE: Instructs the WAM Interpreter to assign the WAMI VARn List, var_list_name, variable value, in the position indicated by the argument index, to the WAMI VAR variable var_variable.
[1608] SYNTAX: WAM:GETLISTVAR var_variable var_list_name index
[1609] EXAMPLE CALL: WAM:GETLISTVAR CELLVAR CELLLIST 2
[1610] DESCRIPTION: GETLISTVAR is an assignment command which automatically assigns the var_list_name variable value in the position indicated by the argument index to the WAMI VAR variable var_variable. This command can only (in this embodiment of the WAMIL language) be executed if the WAMI VARn List has been declared in the script. Upon execution, this command performs a straightforward assignment of the WAMI VARn List variable value to the WAMI VAR variable var_variable.
[1611] The index argument can (in this embodiment of the WAMIL language) be a valid index into the WAMI VARn List. Any List value can be assigned to any (in this WAMIL language embodiment) WAMI VAR variable by execution of this command, where index is the variable value location within the WAMI VARn List.
[1612] The index argument can also reference to a WAMI global variable, WAMI VAR variable, or WAMI VARn List variable name. In such a case the current value of the referenced variable is used as the index position.
[1613] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a GETLISTVAR command, when a CCC List of 3 was previously declared, and the CCC List numbers passed as an argument are 2 4 6:
[1614] Set CCCVAR To CCCVAR2 Value Of 4
[1615] ERRORS: An invalid index argument, where the index refers to a VARn List index outside the list range, will generate an error. Script execution will then be aborted.
[1616] If a GETLISTVAR command is used within a script in which no corresponding WAMI VARn List has been declared, the WAM Interpreter will generate an error and terminate execution of the script.
[1617] ALTERS: WAMI VAR variable given.
[1618] DEFAULT VALUE: None (in this WAMIL language embodiment).
[1619] SEE ALSO: WAM:SETVAR var_variable value
[1620] EXAMPLE: The following script executes a TI command for each CCU number in a list:
[1621] WAM:MSC 5
[1622] WAM:CELL 49
[1623] WAM:WAMLIST Enter Two CCU Numbers
[1624] WAM:SET CCU CCUVAR
[1625] WAM:CONNECT TI
[1626] WAM:GETLISTVAR CCUVAR WAMLIST 1
[1627] TI:op:cell 49, ccc 1, ccu CCUVAR
[1628] WAM:GETLISTVAR CCUVAR WAMLIST 2
[1629] TI:op:cell 49, ccc 1, ccu CCUVAR
[1630] WAM:DISCONNECT TI
[1631] WAM:ENDTEST
GETROP
[1632] The GETROP command can be embedded in the integration construct data structure according to the invention.
[1633] PURPOSE: Instructs the WAM Interpreter to retrieve all (in this embodiment of the WAMIL language) the ROP information specified by the arguments.
[1634] SYNTAX: WAM:GETROP range pattern
[1635] EXAMPLE CALL: WAM:GETROP 0 *
[1636] DESCRIPTION: The GETROP command is a special function command. When executed the WAM Interpreter automatically retrieves all (in this embodiment of the WAMIL language) the ROP information specified by the arguments for the current MSC.
[1637] The GETROP commands acts per the contents of the TAGS FIFO buffer. The TAGS FIFO buffer holds unique tag numbers for each TI command executed in the script. These tag numbers are included in output messages generated by TI commands, and are unique for each message. The TAGS FIFO buffer is a First-In-First-Out buffer. Therefore the order of the tag numbers in the buffer is the same order as the TI commands executed within the script. The TAGS FIFO buffer is never flushed unless a FLUSHTAGS command is executed, and is continuously appended to with the execution of TI commands.
[1638] Upon execution, GETROP retrieves all (in this embodiment of the WAMIL language) messages within the ROP which correspond to the tag numbers stored in the TAGS FIFO buffer. If the range argument is 0, and the pattern argument is *, then all (in this embodiment of the WAMIL language) the ROP messages from the first tag number in the TAGS FIFO buffer, up to and including the messages with the last tag number in the TAGS FIFO buffer, will be retrieved and printed in the script WAMIL report file.
[1639] The pattern argument can be any (in this WAMIL language embodiment) string and include glob-style matching characters. For example, if the pattern REPT* is used, with a range of 0, then only (in this embodiment of the WAMIL language) messages between the tag numbers in the TAGS FIFO buffer which include the string REPT will be printed in the script output file.
[1640] The range argument can be used to specify a range within or outside the tag numbers held in the TAGS FIFO buffer. For example, a range of +100, will print all (in this embodiment of the WAMIL language) ROP messages which start 100 numbers before the first tag number in the TAGS FIFO buffer, and up to and including 100 numbers after the last tag number in the TAGS FIFO buffer. A range argument of −100 will do the opposite. That is print ROP messages from 100 numbers after the first message in the TAGS FIFO buffer, up to and including 100 numbers before the last tag number in the TAGS FIFO buffer.
[1641] The GETROP pattern argument also supports keywords. These keywords are translated into specific actions. For example, when the WAM Interpreter starts execution of a test the start and end of the test is stamped on the ROP. Therefore to retrieve all (in this embodiment of the WAMIL language) the output messages from the ROP which pertain to the execution of a script a user can use the ALLWAMI keyword. Below is a list of GETROP keywords. This list will grow as needed:
| GETROP KEYWORD | DESCRIPTION |
|---|---|
| ALLWAM | All ROP output from the start of script |
| execution until the end. | |
| ALLDAY | All ROP messages which pertain to the |
| same day as script execution start date. | |
| ALLHOUR | ALL ROP messages which pertain to the |
| same hour as script execution start hour. | |
[1642] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a GETROP command:
[1643] ROP Output Retrieved:
[1644] 11/16/98 08:33:45 #106612
[1645] M 33 OP:CELL 1 LC 20, UCL, VERSION
[1646] MAIN NVM 231198
[1647] MAIN ROM 082294
[1648] ANGEL 11
[1649] ENC ROM 010491
[1650] DEC NVM 040790
[1651] DEC ROM 090193
[1652] BASEBAND 0827942
[1653] ROP Output End:
[1654] ERRORS: If the GETROP command is executed, and the TAGS FIFO buffer is empty. Nothing will be printed to the script output file.
[1655] If an error is generated during retrieval of information from the ROP, such errors will be printed in the script output file.
[1656] ALTERS: None (in this WAMIL language embodiment).
[1657] DEFAULT VALUE: None (in this WAMIL language embodiment).
[1658] EXAMPLE: The following script executes two TI commands and then retrieves all the corresponding ROP information prior to terminating:
[1659] WAM:MSC 5
[1660] WAM:CELL 49
[1661] WAM:CONNECT TI
[1662] TI:op:cell 49, ccc 1, ccu 1
[1663] WAM:CCU 2
[1664] TI:op:cell 49, ccc 1, ccu 2
[1665] WAM:DISCONNECT TI
[1666] WAM:GETROP 0 ALLWAM
[1667] WAM:ENDTEST
GETSDP
[1668] The GETSDP command can be embedded in the integration construct data structure according to the invention.
[1669] PURPOSE: Retrieves an indicator STATE, COLOR, and VALUE from the current SDP in the WAMI OutBuff for the WAMI global variable associated with the indicator name, SDPVAR, provided as an argument.
[1670] SYNTAX: WAM:GETSDP indicator_name
[1671] EXAMPLE CALL: WAM:GETSDP CCCOOS
[1672] DESCRIPTION: The GETSDP command is a special function command which sets the WAMI variables SDPVAR_STATE, SDPVAR_COLOR, and SDPVAR_VALUE to the respective STATE, COLOR, and VALUE of the indicator name, SDPVAR, provided as an argument. The STATE, COLOR, and VALUE is retrieved from the current SDP held in the WAMI OutBuff. The specific indicator for which the STATE, COLOR, and VALUE is retrieved is determined by using the indicator name provided in conjunction with the numerical value of its associated WAMI global variable, if any.
[1673] Almost all (in this embodiment of the WAMIL language) supported indicator names have an associated WAMI global variable. For example, indicator name CCCOOS is associated with the WAMI global variable CCC, and indicator name CHANL is associated with the WAMI global variable BBA, on SDP 2138.
[1674] Upon execution of the GETSDP command, SDPVAR_VALUE can be set to any (in this WAMIL language embodiment) text, numerical, or alphanumerical string retrieved from the current SDP which represents the desired indicator. This is usually the alphanumeric string displayed with the indicator. SDPVAR_STATE and SDPVAR_COLOR are fixed pre-defined states and colors. The list of pre-defined states is extensive and SDP dependent. These indicator states which are mapped to a color are described in the Operations, Administration, and Maintenance Guide, Vol. 1, 401-610-160, Issue 9, manual and will not be explained here. Colors are mapped to a state by the GETSDP command depending on the SDP, per the above mentioned document.
[1675] A list of valid STATE words which SDPVAR_STATE can be set to is given in the GETSDP States Table provided below. A list of all (in this embodiment of the WAMIL language) valid GETSDP indicator names supported by the GETSDP command, along with their respective SDP and associated WAMI global variable, if any, and WAMI version in which they are supported is given in the GETSDP Indicator Names Table below.
[1676] Below is a list of valid COLOR words which SDPVAR_COLOR can be set to:
| COLOR |
|---|
[1677] Since an SDP can be cell site equipment dependent, the WAMI global variable CELL_TYPE can (in this embodiment of the WAMIL language) first be set to the correct type prior to the execution of the GETSDP command. The default value for CELL_TYPE is SERIESII.
[1678] OUTPUT: The following is an example of the output generated to the WAMIL report file for the PAF indicator name, upon execution of a WAM:GETSDP PAF command for SDP 2138:
[1679] SDP Page 2138 Query results:
[1680] BBA 19 Physical Antenna Face
[1681] NOPAGE BLACK_ON_YELLOW 1
[1682] Where SDPVAR_STATE has been set to NOPAGE, SDPVAR_COLOR has been set to BLACK_ON_YELLOW, and SDPVAR_VALUE has been set to 1.
[1683] Since there is an extensive list of possible indicator names example outputs will not be shown here for each indicator. all (in this embodiment of the WAMIL language) indicator outputs follow the same format as above, the second line being a description of the indicator. After the execution of the GETSDP command, the variables SDPVAR_STATE, SDPVAR_COLOR, and SDPVAR_VALUE can then be tested.
[1684] ERRORS: An SDP interface command can (in this embodiment of the WAMIL language) be executed prior to the execution of the GETSDP command or the SDPVAR_STATE, SDPVAR_COLOR, and SDPVAR_VALUE variables will each be set to INVALID, and an error will be generated.
[1685] The SDPVAR_STATE for the corresponding SDPVAR_COLOR retrieved is release dependent. Therefore, the WAMI global variable REL can (in this embodiment of the WAMIL language) first be set to the correct software release value prior to the execution of the GETSDP command or invalid results may be returned. The default value for the REL variable is 8.0.
[1686] The SDPVAR_STATE, SDPVAR_COLOR, and SDPVAR_VALUE variables remain unchanged within a script until the execution of a subsequent GETSDP command.
[1687] Using indicator names not valid for the current SDP will also set the SDPVAR_STATE, SDPVAR_COLOR, and SDPVAR_VALUE variables each to INVALID, and generate an error.
[1688] If a valid indicator name is used for the current SDP, and the indicator name is not currently displayed, the SDPVAR_STATE, SDPVAR_COLOR, and SDPVAR_VALUE variables will each be set to NOTSHOWN.
[1689] If a new, or undefined, STATE or COLOR are retrieved for the indicator name, the GETSDP command will set SDPVAR_COLOR and SDPVAR_STATE to UNDEFINED.
[1690] Execution of the GETSDP command after the execution of any (in this WAMIL language embodiment) other SDP command will set the SDPVAR_STATE, SDPVAR_COLOR, and SDPVAR_VALUE variables to INVALID, and generate an error.
[1691] ALTERS: SDPVAR, SDPVAR_STATE, SDPVAR_COLOR, SDPVAR_VALUE
[1692] DEFAULT VALUE: SDPVAR_STATE, SDPVAR_COLOR, and SDPVAR_VALUE, are all (in this embodiment of the WAMIL language) set to INVALID upon initial startup. SDPVAR is set to NULL. The WAM:INITIALIZE command does not alter these variables.
[1693] EXAMPLE: The following script will set the variables SDPVAR_STATE, SDPVAR_COLOR, and SDPVAR_VALUE to the respective STATE, COLOR, and VALUE of the CCC 19 indicator on SDP 2138, and then test if the SDPVAR_STATE variable is ACT:
[1694] WAM:MSC 5
[1695] WAM:CELL 49
[1696] WAM:CCC 19
[1697] WAM:CONNECT SDP
[1698] SDP:2138,49
[1699] WAM:DISCONNECT SDP
[1700] WAM:GETSDP CCC
[1701] IF:TEST_EXPR SDPVAR_STATE EQ ACT
[1702] THENDO:
[1703] WAM:PRINT CCC CCCVAR is Active!
[1704] ELSEDO:
[1705] WAM:PRINT CCC CCCVAR is NOT Active!
[1706] ENDIF:
[1707] WAM:ENDTEST
[1708] Although the VALUE of the CCC 19 indicator is in fact the number 19, SDPVAR_VALUE is more useful when a GETSDP command is executed to retrieve the number of CE's OOS for a specific CCC, or a specific BBA frequency. For example, the following script tests to see if any Channel Elements are OOS for CCC 19, and then sets SDPVAR_VALUE to the VALUE of the BBA 19 channel frequency indicator and tests if the frequency is 150. If no CEs are OOS, and the frequency is correct, the script then executes another WAMIL script:
[1709] WAM:MSC 5
[1710] WAM:CELL 49
[1711] WAM:BBA 19
[1712] WAM:CCC 19
[1713] WAM:OUTPUTOFF
[1714] WAM:CONNECT SDP
[1715] SDP:2138,49
[1716] WAM:DISCONNECT SDP
[1717] WAM:GETSDP CCCOOS
[1718] IF:TEST_EXPR SDPVAR_VALUE NE NOTSHOWN
[1719] THENDO:
[1720] WAM:PRINT CCC CCCVAR CEs OOS, /w
[1721] a total of SDPVAR_VALUE
[1722] WAM:ENDTEST
[1723] ELSEDO:
[1724] ENDIF:
[1725] WAM:GETSDP CHANL
[1726] IF:TEST_EXPR SDPVAR_VALUE EQ 150
[1727] THENDO:
[1728] ELSEDO:
[1729] WAM:PRINT Channel Frequency is Not Correct, /w
[1730] it is SDPVAR_VALUE
[1731] WAM:ENDTEST
[1732] ENDIF:
[1733] WAM:UNIX WAMI30jt1234 -msc MSCVAR -cell CELLVAR
[1734] WAM:ENDTEST
[1735] Below is an example of an SDP 2138 query for FLEXENT cell site equipment:
[1736] WAM:MSC 5
[1737] WAM:CELL 38
[1738] WAM:SET MICROCELL 1
[1739] WAM:SET CELL_TYPE MICRO
[1740] WAM:CONNECT SDP
[1741] SDP:2138,38
[1742] WAM:DISCONNECT SDP
[1743] WAM:GETSDP CRCSTAT
[1744] WAM:ENDTEST
[1745] Below is an example of an SDP 2121 query for the status of every cell on an MSC:
[1746] WAM:OUTPUTOFF
[1747] WAM:MSC 5
[1748] WAM:CONNECT SDP
[1749] SDP:2121
[1750] WAM:DISCONNECT SDP
[1751] WAM:SET CELL CELLVAR
[1752] WAM:SETVAR CELLVAR 1
[1753] WHILE:TEST_EXPR CELLVAR LT 223
[1754] WAM:GETSDP CELL
[1755] WAM:INCRVAR CELLVAR 1
[1756] ENDWHILE:
[1757] WAM:ENDTEST
[1758] GETSDP Support Commands Table:
| SDP COMMAND | CELL_TYPE |
|---|---|
| 2121 | SERIESII |
| 2132 | SERIESII |
| 2134 | SERIESII |
| 2138 | SERIESII |
| 2138 | MICRO 3.0 |
| 2139 | SERIESII |
| 2140 | SERIESII |
| 2141 | SERIESII |
[1759] GETSDP States Table:
| STATE | DESCRIPTION |
|---|---|
| ACT | Active |
| ALARM | Alarm |
| ALLOWED | Allowed |
| ARR_ACTIVE | Automatic radio reconfiguration active |
| BLKD | Blocked |
| BUSY_ACTIVE | Traffic, activc state |
| CAMP_ON | Camp on |
| CE_FAIL | Overhead CE failed pilot level FT |
| CP_I | Call processing inhibited |
| GROW | Growth |
| IDLE | Traffic |
| INDETMNT | Indeterminate |
| INH | Inhibited |
| INHIBITED | Inhibited |
| INIT | Transient clear, stable clear, or boot initialization |
| phase | |
| LIMIT_EX | Limit Exceeded |
| MAJOR | Major Alarm |
| MINOR | Minor Alarm |
| NONE | No State |
| NOPAGE | No Page |
| NORMAL | Normal |
| OFF | Off |
| ON | On |
| OOS | Out Of Service |
| OOS_EX | Out Of Service EX |
| OVLD | Processor Overload |
| PILOTDG | Pilot DG |
| PSA_ALARM | PSA Alarm |
| STBY | Standby |
| TRBL | Trouble |
| UNDEFINED | GETSDP TOOL Undefined State |
| UNEQ | Unequipped |
| UNKNOWN | Unknown State |
| WARNING | Warning |
[1760] GETSDP Indicator Names Table:
| DESCRIP- | ||||
|---|---|---|---|---|
| INDICATOR | CELL_TYPE | SDP | GLOBAL | TION |
| 5EDCS_CRITICAL | SERIESII | 2141 | 5E DCS | |
| Critical | ||||
| Alarm State | ||||
| 5EDCS_MAJOR | SERIESII | 2141 | 5E DCS | |
| Major Alarm | ||||
| State | ||||
| 5EDCS_MINOR | SERIESII | 2141 | 5E DCS | |
| Minor Alarm | ||||
| State | ||||
| 5EDCS_STATUS | SERIESII | 2141 | 5E DCS | |
| Status | ||||
| AFAC | SERIESII | 2141 | DCS AUTO- | |
| PLEX | ||||
| Facility | ||||
| Status | ||||
| AUDITS | SERIESII | 2132 | Cell Site | |
| Audits Status | ||||
| AUDIT_HEH_OUT | SERIESII | 2132 | Audits Out- | |
| put/HEH | ||||
| Messages | ||||
| State | ||||
| BBA | SERIESII | 2138 | BBA | BBA |
| BDTYPE | SERIESII | 2134 | DS1 | DS1 Trunk |
| Signaling | ||||
| Board Type | ||||
| BFC | SERIESII | 2139 | Blocked | |
| From Cell | ||||
| Bit | ||||
| BFD | SERIESII | 2139 | Blocked | |
| From DCS | ||||
| Bit | ||||
| BFM | SERIESII | 2139 | Blocked | |
| From MSC | ||||
| Bit | ||||
| BLK_RSN1 | SERIESII | 2139 | Sector I | |
| Blocked | ||||
| Reason | ||||
| BLK_RSN2 | SERIESII | 2139 | Sector 2 | |
| Blocked | ||||
| Reason | ||||
| BLK_RSN3 | SERIESII | 2139 | Sector 3 | |
| Blocked | ||||
| Reason | ||||
| BOOT | SERIESII | 2132 | Cell Site | |
| Automatic | ||||
| Boot State | ||||
| CALL_PRO- | SERIESII | 2132 | Call Process- | |
| CESSING | ing State | |||
| CBRSTAT | MICRO | 2138 | MICRO- | MICRO- |
| CELL | CELL CBR | |||
| Status | ||||
| CC0 | SERIESII | 2140 | DCS | DCS Com- |
| mon Con- | ||||
| troller 0 | ||||
| Status | ||||
| CC1 | SERIESII | 2140 | DCS | DCS Com- |
| mon Con- | ||||
| troller 1 | ||||
| Status | ||||
| CCC | SERIESII | 2138 | CCC | CCC |
| CCCOOS | SERIESII | 2138 | CCC | CCC OOS |
| CEs | ||||
| CCURSN | SERIESII | 2139 | CCU | CCU State |
| Reason | ||||
| CCUSRC | SERIESII | 2139 | CCU | CCU State |
| Source | ||||
| CCUCEPAF | SERIESII | 2139 | CCU, CE | CCU CE |
| Antenna | ||||
| Face | ||||
| CCUCESTAT | SERIESII | 2139 | CCU, CE | CCU CE |
| Status | ||||
| CDMA_INV_CTL | SERIESII | 2132 | CDMA In- | |
| ventory Con- | ||||
| trol State | ||||
| CDMACNUM | SERIESII | 2139 | CDMA | |
| Carrier | ||||
| Number | ||||
| CDN | SERIESII | 2121 | CDN | CDN Status |
| Block | ||||
| CELL | SERIESII | 2121 | CELL | CELL Site |
| Status | ||||
| CEOOS | MICRO | 2138 | MICRO- | MICRO- |
| CELL | CELL OOS | |||
| CEs | ||||
| CHANL | MICRO | 2138 | MICRO- | MICRO- |
| CELL | CELL | |||
| Channel | ||||
| Frequency | ||||
| CHANL | SERIESII | 2138 | BBA | BBA |
| Channel | ||||
| Frequency | ||||
| COMM | SERIESII | 2141 | DCS Com- | |
| munications | ||||
| Status | ||||
| CRCSTAT | MICRO | 2138 | MICRO- | MICRO- |
| CELL | CELL CRC | |||
| Status | ||||
| CTRMSTAT | MICRO | 2138 | MICRO- | MICRO- |
| CELL | CELL | |||
| CTRM | ||||
| Status | ||||
| DCS | MICRO | 2138 | MICRO- | |
| CELL DCS | ||||
| Serving | ||||
| DCS | SERIESII | 2121 | DCS | DCS Status |
| DCS | SERIESII | 2140 | DCS | DCS Status |
| DCSTG | SERIESII | 2121 | DCS | DCS Trunk |
| Group | ||||
| DIVERR_OUT | SERIESII | 2132 | Diversity | |
| Error Im- | ||||
| balance Out- | ||||
| put State | ||||
| DL0 | SERIESII | 2140 | DCS | DCS Data |
| Link 0 Status | ||||
| DL1 | SERIESII | 2140 | DCS | DCS Data |
| Link 1 Status | ||||
| DLN1 | SERIESII | 2121 | Direct Link | |
| Node 1 | ||||
| DLN2 | SERIESII | 2121 | Direct Link | |
| Node 2 | ||||
| DIVALRM | MICRO | 2138 | MICRO- | MICRO- |
| CELL | CELL DIV | |||
| ALRM | ||||
| DS1 | SERIESII | 2134 | DS1 | DS1 |
| ECP_AUD | SERIESII | 2121 | ECP Audits | |
| State | ||||
| ECP_OVLD | SERIESII | 2121 | ECP Over- | |
| load Indi- | ||||
| cator State | ||||
| EQP | SERIESII | 2140 | DCS | DCS Equip- |
| ment Status | ||||
| FWD_SET- | SERIESII | 2132 | Forward Set- | |
| UP_CHANL | up channel | |||
| Control State | ||||
| FUNC_TESTS | SERIESII | 2132 | Cell Site | |
| Routine | ||||
| Functional | ||||
| Tests State | ||||
| GPSSTAT | MICRO | 2138 | MICRO- | MICRO- |
| CELL | CELL GPS | |||
| Status | ||||
| IMS | SERIESII | 2121 | IMS Status | |
| INCMDS1 | MICRO | 2138 | MICRO- | MICRO- |
| CELL | CELL In- | |||
| Coming DS1 | ||||
| INTERRUPTS | SERIESII | 2132 | Cell Site | |
| Hardware In- | ||||
| terrupts State | ||||
| LINERATE | SERIESII | 2134 | DS1 | DS1 Facility |
| MICROCELL | MICRO | 2138 | MICRO- | MICRO- |
| CELL | CELL | |||
| MSC | SERIESII | 2121 | MSC | Direct Net- |
| worked MSC | ||||
| State | ||||
| OFD_CAP | SERIESII | 2132 | OFD-CAP | |
| State | ||||
| OFD_MS | SERIESII | 2132 | OFD-MS | |
| State | ||||
| OFD_PG | SERIESII | 2132 | OFD-PG | |
| State | ||||
| OMP | SERIESII | 2121 | OMP and | |
| FLA_OMP | ||||
| State | ||||
| OMP_COM | SERIESII | 2121 | DCI Link, | |
| Inter- | ||||
| processor | ||||
| Communica- | ||||
| tions State | ||||
| OMPLK0 | SERIESII | 2121 | DCI Link 0 | |
| State | ||||
| OMPLK1 | SERIESII | 2121 | DCI Link 1 | |
| State | ||||
| OPMSG | SERIESII | 2121 | Output | |
| Message | ||||
| Direction | ||||
| Status | ||||
| OUTGDS1 | MICRO | 2138 | MICRO- | MICRO |
| CELL | CELL Out- | |||
| Going DS1 | ||||
| PAF | SERIESII | 2138 | BBA | BBA |
| Physical | ||||
| Antenna | ||||
| Face | ||||
| PAFSTATE | MICRO | 2138 | MICRO- | MICRO- |
| CELL | CELL Phys- | |||
| ical Antenna | ||||
| Face State | ||||
| PAFSTATENUM | MICRO | 2138 | MICRO- | MICRO- |
| CELL | CELL Phys- | |||
| ical Antenna | ||||
| Face | ||||
| Number | ||||
| PRASE_MONITOR | SERIESII | 2132 | Automatic | |
| Cell Site | ||||
| Removal on | ||||
| Repeated | ||||
| Phasing | ||||
| PPG | MICRO | 2138 | MICRO- | Packet Pipe |
| CELL | Group | |||
| PPTGMEMNUM | SERIESII | 2139 | Packet Pipe | |
| Trunk Group | ||||
| Member | ||||
| PPW | MICRO | 2138 | MICRO- | MICRO- |
| CELL | CELL | |||
| Packet Pipe | ||||
| Width | ||||
| PPW | SERIESII | 2138 | CCC | CCC Packet |
| Pipe Width | ||||
| RECVAMP | MICRO | 2138 | MICRO- | MICRO- |
| CELL | CELL | |||
| RECV AMP | ||||
| RTDIAG | SERIESII | 2132 | Cell Site | |
| Routine | ||||
| Hardware | ||||
| Diagnostics | ||||
| SECTNUM1 | SERIESII | 2139 | Sector Item | |
| 1 Number | ||||
| SECTNUM2 | SERIESII | 2139 | Sector Item | |
| 2 Number | ||||
| SECTNUM3 | SERIESII | 2139 | Sector Item | |
| 3 Number | ||||
| STATE | SERIESII | 2134 | DS1 | DS1 State |
| SUMMARY | SERIESII | 2141 | DCS Com- | |
| munications | ||||
| Status | ||||
| Summary | ||||
| TFUSTAT | MICRO | 2138 | MICRO- | MICRO- |
| CELL | CELL TFU | |||
| Status | ||||
| TRKGRP | SERIESII | 2140 | DCS | DCS Trunk |
| Group Status | ||||
| XMITAMP | MICRO | 2138 | MICRO- | MICRO- |
| CELL | CELL XMIT | |||
| AMP | ||||
GET_TI
[1761] The GET_TI command can be embedded in the integration construct data structure according to the invention.
[1762] PURPOSE: Instructs the WAM Interpreter to assign to var_variable the value located in position index relative to the string provided.
[1763] SYNTAX: WAM:GET_TI var_variable index string
[1764] EXAMPLE CALL: WAM:GET_TI MCRVAR 1 MCR
[1765] DESCRIPTION: The GET_TI command is a special function command which allows a user to retrieve a specific value from any (in this WAMIL language embodiment) TI output message, and assign that value to a specific WAMI VAR variable.
[1766] Execution of this command causes the WAM Interpreter to search the WAMI buffer for the first occurrence which matches the argument string. The index argument then specifies the location of the desired value relative to the string matched. The WAMI VAR variable specified by the argument var_variable is then set to that value.
[1767] For example, consider the following TI output message:
[1768] M 28 REPT:CP, DN 2019567291 MIN 2019567291
[1769] MOBILE SERIAL NUMBER X198e13b
[1770] DCS 5
[1771] CGSA 1
[1772] CDN 2
[1773] MCR 647
[1774] ISR NONE
[1775] Execution of the command WAM:GET_TI MCRVAR 1 MCR, will set the WAMI VAR variable MCRVAR to the value of 647, and execution of the command WAM:GET_TI MOBILEVAR 1 DN will set the WAMI VAR variable MOBILEVAR to the value of 2019567291. Execution of either of the following commands will set the VAR variable WAMVAR to the value of X198e13b:
[1776] WAM:GET_TI WAMVAR 1 MOBILE SERIAL NUMBER
[1777] WAM:GET_TI WAMVAR 2 SERIAL
[1778] Execution of this command causes a direct assignment to the WAMI VAR variable specified. It does not establish an association between the WAMI VAR variable specified and its complementary WAMI global variable.
[1779] If the string provided is not matched, the WAMI VAR variable specified by the argument var_variable will remain unchanged.
[1780] If the index position provided yields no value, the WAMI VAR variable specified by the argument var_variable will remain unchanged.
[1781] The string argument can also include references to WAMI global variables, or WAMI VARn variables. To reference a WAMI global variable the suffix VAR is simply added to the WAMI global variable name. This is not to be mistaken with WAMI VAR variables. Although when referencing WAMI global variables within strings the names resemble WAMI VAR variables, this naming convention was chosen to allow references to WAMI global variables and still be able to print the variable name. To include the value of a WAMI VAR variable, a WAMI global variable can (in this embodiment of the
[1782] WAMIL language) first be associated. Then references to the WAMI global variable will yield the value of the WAMI VAR variable it is associated with.
[1783] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution an GET_TI command:
[1784] Set MCRVAR to 647 per TI output message.
[1785] ERRORS:. The argument var_variable can (in this embodiment of the WAMIL language) be a valid WAMI VAR variable name or a syntax error will be generated and script execution will be aborted.
[1786] The argument index can (in this embodiment of the WAMIL language) be a valid positive integer number or a syntax error will be generated and script execution will be aborted.
[1787] If this command is executed and the WAMI buffer does not contain any (in this WAMIL language embodiment) TI output message, an error will be generated during execution of the script. Such error will be printed in the script output file. The WAMI VAR variable specified by the argument var_variable will remain unchanged.
[1788] If the value retrieved is not of the same type as the WAMI VAR variable specified, an error will be generated, the error message printed in the script output file, and the WAMI VAR variable specified by the argument var_variable will remain unchanged.
[1789] ALTERS: WAMI global variable provided.
[1790] DEFAULT VALUE: None (in this WAMIL language embodiment).
[1791] EXAMPLE: The following WAMIL script determines the CCC, CCU and CE a mobile call is on:
[1792] WAM:MSCVAR
[1793] WAM:CELLVAR
[1794] WAM:WAMLIST Enter A Mobile Phone Number
[1795] WAM:SET MOBILE WAMVAR1
[1796] WAM:SET MCR MCRVAR
[1797] WAM:SETVAR MCRVAR 0
[1798] WAM:CONNECT TI
[1799] TI:op:dn “WAMVAR1”
[1800] WAM:GET_TI MCRVAR 1 MCR
[1801] IF:TEST_EXPR MCRVAR EQ 0
[1802] THENDO:
[1803] WAM:PRINT Call on MOBILE WAMVAR1 is Not Up!
[1804] WAM:ENDTEST
[1805] ELSEDO:
[1806] ENDIF:
[1807] WAM:SET CDN CDNVAR
[1808] WAM:GET_TI CDNVAR 1 CDN
[1809] TI:op:mcr MCRVAR, cdn CDNVAR
[1810] WAM:DISCONNECT TI
[1811] WAM:SET CCC CCCVAR
[1812] WAM:SET CCU CCUVAR
[1813] WAM:SET CE CEVAR
[1814] WAM:GET_TI CCCVAR 1 CELL CELLVAR CCC
[1815] WAM:GET_TI CCUVAR 1 CELL CELLVAR CCC CCCVAR, CCU
[1816] WAM:GET_TI CEVAR 1 CELL CELLVAR CCC CCCVAR, CCU
[1817] CCUVAR, CE
[1818] WAM:PRINT Mobile Call is on CCC CCCVAR, CCU CCUVAR, CE
[1819] CEVAR.
[1820] WAM:ENDTEST
INCR
[1821] The INCR command can be embedded in the integration construct data structure according to the invention.
[1822] PURPOSE: Instructs the WAM Interpreter to increment the WAMI global variable provided, by the value given.
[1823] SYNTAX: WAM:INCR global_variable value
[1824] EXAMPLE CALL: WAM:INCR BBA 2
[1825] DESCRIPTION: The INCR command increments the current value of the WAMI global variable provided by the argument global_variable, by the value given. This command performs a straightforward addition. The WAMI global variable can (in this embodiment of the WAMIL language) be of type integer. The value given can (in this embodiment of the WAMIL language) be a valid integer number.
[1826] This command only (in this embodiment of the WAMIL language) operates on WAMI global variables. To increment the value of a WAMI VAR variable use the INCRVAR command.
[1827] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution an INCR command:
[1828] Increment BBA from 2 to 4
[1829] ERRORS: None.
[1830] ALTERS: WAMI global variable provided.
[1831] DEFAULT VALUE: None (in this WAMIL language embodiment).
[1832] SEE ALSO: WAM:DECR global variable value
[1833] EXAMPLE: The following script increments BBA by two and then executes a TI command using the new BBA value.
[1834] WAM:CELL 49
[1835] WAM:BBA 4
[1836] TI:op:cell 49, bba 4
[1837] WAM:INCR BBA 2
[1838] TI:op:cell 49, bba 6
INCRVAR
[1839] The INCRVAR command can be embedded in the integration construct data structure according to the invention.
[1840] PURPOSE: The INCRVAR command instructs the WAM Interpreter to increment the WAMI VAR variable provided as an argument by the value given.
[1841] SYNTAX: WAM:INCRVAR var_variable value
[1842] EXAMPLE CALL: WAM:INCRVAR BBAVAR 1
[1843] DESCRIPTION: The INCRVAR command increments the current value of the WAMI VAR variable provided by the argument var_variable, by the value given. This command performs a straightforward addition. The WAMI VAR variable can (in this embodiment of the WAMIL language) be of type integer. The value given can (in this embodiment of the WAMIL language) be a valid integer number.
[1844] This command only (in this embodiment of the WAMIL language) operates on WAMI VAR variables. To increment the value of a WAMI global variable use the INCR command.
[1845] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution an INCRVAR command:
[1846] Increment BBAVAR by 1
[1847] ERRORS: None.
[1848] ALTERS: WAMI VAR variable provided.
[1849] DEFAULT VALUE: None (in this WAMIL language embodiment).
[1850] SEE ALSO: WAM:DECRVAR var variable value
[1851] EXAMPLE: The following script increments BBAVAR by two and then executes a TI command using the new BBAVAR value.
[1852] WAM:CELL 49
[1853] WAM:BBAVAR
[1854] TI:op:cell 49, bba BBAVAR
[1855] WAM:INCRVAR BBAVAR 2
[1856] TI:op:cell 49, bba BBAVAR
INITIALIZE
[1857] The INITIALIZE command can be embedded in the integration construct data structure according to the invention.
[1858] PURPOSE: Sets all (in this embodiment of the WAMIL language) WAMI global variables to an initial state.
[1859] SYNTAX: WAM:INITIALIZE
[1860] EXAMPLE CALL: WAM:INITIALIZE
[1861] DESCRIPTION: The INITIALIZE command sets all (in this embodiment of the WAMIL language) WAMI global variables to an initial default state.
[1862] GLOBALS: The following is a complete list all (in this embodiment of the WAMIL language) the WAMI global variables set by the INITIALIZE command, and the default value they are set to upon execution of such command:
| WAMI | |||
|---|---|---|---|
| VARIABLE | VALUE | TYPE | |
| ADDCE | 0 | Integer | |
| ADRS | NULL | String | |
| ANT | 0 | Integer | |
| AU | 1 | Integer | |
| BBA | 1 | Integer | |
| CAT | 0 | Integer | |
| CCC | 1 | Integer | |
| CCU | 1 | Integer | |
| CDMADPC | 0 | Integer | |
| CELL | 0 | Integer | |
| CFAIL | 0 | Integer | |
| CGSA | 0 | Integer | |
| CONFIG | 0 | Integer | |
| CSC | 0 | Integer | |
| DCCH | 0 | Integer | |
| DCS | 0 | Integer | |
| DisplayDelay | 1 | Integer | |
| DL | 0 | Integer | |
| DS1 | 0 | Integer | |
| ECP | 0 | Integer | |
| GEN | 0 | String | |
| INACT | 60 | Integer | |
| LAC | 0 | Integer | |
| LC | 0 | Integer | |
| LFAIL | 0 | Integer | |
| LMT | 0 | Integer | |
| MICROCELL | 0 | Integer | |
| MSC | 0 | Integer | |
| OC | 0 | Integer | |
| PH | 0 | String | |
| PL | 0 | Integer | |
| RA | 0 | Integer | |
| RG | 0 | Integer | |
| RPT | 0 | Integer | |
| RptName | None | String | |
| SG | 0 | Integer | |
| SPOOL | 10 | Integer | |
| SU | 0 | Integer | |
| SW | 0 | Integer | |
| TFAIL | 0 | Integer | |
| TimeOut | 30 | Integer | |
| TP | 0 | Integer | |
| TRACE | 0 | Integer | |
| TRKGRP | 0 | Integer | |
| TRKMBR | 0 | Integer | |
| VRADPC | 0 | Integer | |
| VRN | 0 | Integer | |
| Wait | 10 | Integer | |
| XMITC | 0 | Integer | |
[1863] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a INITIALIZE command:
[1864] Initialize All WAMI Variables.
[1865] ERRORS: None.
[1866] ALTERS: All WAMI global variables.
[1867] DEFAULT VALUE: None (in this WAMIL language embodiment).
[1868] SEE ALSO: All WAMIL commands which modify WAMI variables.
INPUT
[1869] The INPUT command can be embedded in the integration construct data structure according to the invention.
[1870] PURPOSE: Replaces the WAM Interpreter OutBuff with the contents of filename.
[1871] SYNTAX: WAM:INPUT filename
[1872] EXAMPLE CALL: WAM:INPUT RESULTS.txt
[1873] DESCRIPTION: The INPUT command instructs the WAM Interpreter to load the contents of the file specified by filename into OutBuff. If OutBuff contains any (in this WAMIL language embodiment) previous data, the data will be overwritten and lost.
[1874] The argument filename can (in this embodiment of the WAMIL language) include the complete path to the file. If no path is given, the WAM Interpreter will assume the file is located in the current script output directory.
[1875] The INPUT command filename argument can include references to WAMI global variables, or WAMI VARn variables. To reference a WAMI global variable the suffix VAR is simply added to the WAMI global variable name. For example, the following filename, CELLVAR.txt, will be interpreted as, 101.txt, if the script cell number is 101 upon execution of the INPUT command.
[1876] OUTPUT: The following is an example of the output generated to the script WAMIL report file upon execution of an INPUT command:
[1877] Load File RESULTS.txt
[1878] ERRORS: If any (in this WAMIL language embodiment) errors occur in opening or locating the filename specified, such errors will be printed in the WAMIL report file.
[1879] If the file to be loaded is too large, unpredictable errors may result.
[1880] ALTERS: OutBuff.
[1881] DEFAULT VALUE: None (in this WAMIL language embodiment).
[1882] SEE ALSO: All OutBuff related WAMIL commands.
LAC
[1883] The LAC command can be embedded in the integration construct data structure according to the invention.
[1884] PURPOSE: Changes the WAMI global linear amplifier circuit number variable, LAC, to the value provided as an argument.
[1885] SYNTAX: WAM:LAC value
[1886] EXAMPLE CALL: WAM:LAC 1
[1887] DESCRIPTION: The WAM:LAC command sets the WAMI global linear amplifier circuit 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 a linear amplifier circuit number, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script linear amplifier circuit number, will reference the new value.
[1888] 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.
[1889] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution of a LAC command:
[1890] Set Linear Amplifier Circuit To 1
[1891] ERRORS: None.
[1892] ALTERS: LAC
[1893] DEFAULT VALUE: LAC is set to 0 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 0.
[1894] SEE ALSO: WAM:INITIALIZE
[1895] EXAMPLE: The following script lines set the WAMIL script LAC variable to 1 and then executes a TI command:
[1896] WAM:CELL 49
[1897] WAM:LAC 1
[1898] TI:op:cell 49, lac 1
LAUNCH
[1899] The LAUNCH command can be embedded in the integration construct data structure according to the invention.
[1900] PURPOSE: Instructs the WAM Interpreter to launch the WAMIL script provided as argument.
[1901] SYNTAX: WAM:LAUNCH path wamil_script -switch . . .
[1902] EXAMPLE CALL: WAM:LAUNCH HOME jt1234 -msc 5 -cell 101
[1903] DESCRIPTION: The LAUNCH command instructs the WAM Interpreter to launch the WAMIL script, provided by the argument wamil script, located at path.
[1904] The launched WAMIL script will be executed independently from the launching script, and not alter any (in this WAMIL language embodiment) WAMI global variables or flags of such script The launched script will generate its own status display window, associated interface sessions, and WAMIL report file. The launching script will continue with execution of the next script line and not wait for the launched script to be completed.
[1905] The argument path can be any (in this WAMIL language embodiment) valid, complete UNIX pathname. The LAUNCH command allows supports WAM Interpreter path keywords which can be used for the path argument.
[1906] The -switch arguments can be any (in this WAMIL language embodiment) valid WAM Interpreter command line switch.
[1907] The -switch arguments can also include references to WAMI global variables, or WAMI VARn variables. To reference a WAMI global variable the suffix VAR is simply added to the WAMI global variable name. This is not to be mistaken with WAMI VAR variables. Although when referencing WAMI global variables within strings the names resemble WAMI VAR variables, this naming convention was chosen to allow references to WAMI global variables and still be able to print the variable name. To include the value of a WAMI VAR variable, a WAMI global variable can (in this embodiment of the WAMIL language) first be associated. Then references to the WAMI global variable will yield the value of the WAMI VAR variable it is associated with.
[1908] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a LAUNCH command:
[1909] Launch Script jt1234
[1910] ERRORS: If an invalid path is provided as an argument, the WAM Interpreter will generate an error and the WAMIL script will not be launched.
[1911] If an invalid WAMIL script name is provided as an argument, the WAM Interpreter will generate an error and no WAMIL script will be launched.
[1912] ALTERS: None (in this WAMIL language embodiment).
[1913] DEFAULT VALUE: None (in this WAMIL language embodiment).
[1914] SEE ALSO: WAM:EXEC path wamil_script
[1915] EXAMPLE: The following script will launch a WAMIL script:
[1916] WAM:MSC 5
[1917] WAM:CELL 49
[1918] WAM:BBA 4
[1919] WAM:CONFIG 150
[1920] WAM:LAUNCH SHARE jt1234
[1921] WAM:CONNECT TI
[1922] TI:cfr:cell 49, multi bba 4; config 150
[1923] WAM:DISCONNECT TI
[1924] WAM:ENDTEST
LC
[1925] The LC command can be embedded in the integration construct data structure according to the invention.
[1926] PURPOSE: Changes the WAMI global locate radio number variable, LC, to the value provided as an argument.
[1927] SYNTAX: WAM:LC value
[1928] EXAMPLE CALL: WAM:LC 1
[1929] DESCRIPTION: The WAM:LC command sets the WAMI global locate radio 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 a locate radio number, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script locate radio number, will reference the new value.
[1930] 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.
[1931] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution of a LC command:
[1932] Set Locate Radio To 1
[1933] ERRORS: None.
[1934] ALTERS: LC
[1935] DEFAULT VALUE: LC is set to 0 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 0.
[1936] SEE ALSO: WAM:INITIALIZE
[1937] EXAMPLE: The following script lines set the WAMIL script LC variable to 1 and then execute a TI command:
[1938] WAM:CELL 49
[1939] WAM:LC 1
[1940] TI:op:cell 49, lc 1
LMT
[1941] The LMT command can be embedded in the integration construct data structure according to the invention.
[1942] PURPOSE: Changes the WAMI global lightwave microcell transceiver number variable, LMT, to the value provided as an argument.
[1943] SYNTAX: WAM:LMT value
[1944] EXAMPLE CALL: WAM:LMT 1
[1945] DESCRIPTION: The WAM:LMT command sets the WAMI global lightwave microcell transceiver 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 a lightwave microcell transceiver number, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script lightwave microcell transceiver number, will reference the new value.
[1946] 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.
[1947] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution of a LMT command:
[1948] Set Lightwave Microcell Transceiver To 1
[1949] ERRORS: None.
[1950] ALTERS: LMT
[1951] DEFAULT VALUE: LMT is set to 0 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 0.
[1952] SEE ALSO: WAM:INITIALIZE
[1953] EXAMPLE: The following script lines set the WAMIL script LMT variable to 1 and then execute a TI command:
[1954] WAM:CELL 49
[1955] WAM:LMT 1
[1956] TI:op:cell 49, lmt 1
LOOPCELL
[1957] The LOOPCELL command can be embedded in the integration construct data structure according to the invention.
[1958] PURPOSE: Instructs the WAM Interpreter to execute the entire WAMIL script once per cell number provided in the command arguments.
[1959] SYNTAX: WAM:LOOPCELL cells . . .
[1960] EXAMPLE CALL: WAM:LOOPCELL 85 49 160
[1961] DESCRIPTION: The LOOPCELL command is a special function looping command. LOOPCELL instructs the WAM Interpreter to execute the entire WAMIL script once for each cell number listed in the argument cells, in effect creating a script looping effect. The first cell number given in the LOOPCELL command list becomes the default cell number for the script.
[1962] The list of cells provided as an argument can (in this embodiment of the WAMIL language) have the following format:
[1963] cell1 cell2 cell3 . . .
[1964] Where each cell number is separated by a blank space. The cell numbers will be executed in the order listed in the argument.
[1965] Upon execution of a script, the WAM Interpreter first loads the entire script and checks each command for syntax errors prior to initiating execution. At this point, detection of the LOOPCELL command causes the WAM Interpreter to automatically enable script looping. The WAM Interpreter also at this point determines how many times the script will be looped by counting the number of cells in the list.
[1966] For script syntax, when a LOOPCELL command is inserted the script CELL number shall be the first cell number in the list of cells provided.
[1967] The list of cells provided by the LOOPCELL command can only (in this embodiment of the WAMIL language) be altered by execution of the GETCELLS command. In such a case, the next cell number executed will depend on which loop the script execution is currently in.
[1968] If the list of cells provided is greater than one cell number, the WAM Interpreter will ignore all (in this embodiment of the WAMIL language) DISCONNECT commands, and the last script ENDTEST command, until the script has been executed for the last cell. In this manner all (in this embodiment of the WAMIL language) interface sessions will remain nailed up until the script has been looped the correct number of times, to avoid login failures during the execution of any cell. The THEN:ENDTEST command, and any (in this WAMIL language embodiment) embedded WAM:ENDTEST commands, will however not be ignored.
[1969] Execution of a WAM:CELL command within a script with LOOPCELL will cause the WAM Interpreter to stop looping the script.
[1970] SCRIPTOR: Upon insertion of this command, the Scriptor will remove all (in this embodiment of the WAMIL language) CELL commands, if any, from the script and any cell looping commands, and set the default cell number to the first cell number provided in the cells list. The Scriptor will then regenerate the script using the first cell number as the default cell number.
[1971] The Scriptor automatically places this command below any (in this WAMIL language embodiment) existing DISPLAY or MSCVAR command. If these commands do not exist, LOOPCELL with be placed at the top of the script.
[1972] If a CELLVAR or a LOOPCELLVARS command exists in the script, upon insertion of the LOOPCELL command they are automatically removed from the script.
[1973] A syntax error will occur if this command is placed after any (in this WAMIL language embodiment) CONNECT command.
[1974] If the LOOPCELL command is deleted from the script, the first cell number in the list takes precedence for the entire script. The Scriptor will then insert a CELL command in place of the LOOPCELL command. The argument for the CELL command will be the first cell number in the LOOPCELL cells list.
[1975] If the LOOPCELL command already exists in a script, insertion of any (in this WAMIL language embodiment) additional LOOPCELL commands causes the existing cell numbers to be replaced with the new list of cell numbers.
[1976] The Scriptor will only (in this embodiment of the WAMIL language) allow one LOOPCELL command to be inserted into a script.
[1977] OUTPUT: Execution of the LOOPCELL command generates the following output to the script WAMIL report file:
[1978] Cell Loop: 1
[1979] Start Test Cell: 49
[1980] ERRORS: If more than one LOOPCELL command is used in a WAMIL script, the cells list from the last LOOPCELL command will take precedence. Thus all (in this embodiment of the WAMIL language) preceding LOOPCELL commands have no effect.
[1981] If LOOPCELL is included in a script with the CELLVAR or LOOPCELLVARS command, unpredictable errors may result.
[1982] ALTERS: CELL
[1983] DEFAULT VALUE: None (in this WAMIL language embodiment).
[1984] SEE ALSO: WAM:CELL value, WAM:GETCELLS, WAM:LOOPCELLVARS
[1985] EXAMPLE: The following script will loop three times, once for each cell number provided
[1986] WAM:LOOPCELL 85 49 160
[1987] WAM:MSC 5
[1988] WAM:CONNECT TI
[1989] TI:op:cell 85
[1990] WAM:DISCONNECT TI
[1991] WAM:ENDTEST
LOOPCELLVARS
[1992] The LOOPCELLVARS command can be embedded in the integration construct data structure according to the invention.
[1993] PURPOSE: Instructs the WAM Interpreter to execute the entire WAMIL script once per cell number supplied to the script.
[1994] SYNTAX: WAM:LOOPCELLVARS
[1995] EXAMPLE CALL: WAM:LOOPCELLVARS
[1996] DESCRIPTION: The LOOPCELLVARS command is a special function looping command which instructs the WAM Interpreter that the list of cells for the script will be supplied as a command line argument. Upon detection of this command, the WAM Interpreter will search the command line arguments for the script cell numbers. The WAM Interpreter also at this point determines how many times the script will be looped by counting the number of cells in the list. The WAMIL script will then be executed once for each cell number passed as an argument, in effect creating a WAMIL script looping effect. The cell numbers will be executed in the order listed in the argument.
[1997] Since the first cell number given in the argument is undetermined prior to execution of a WAMIL script, the first cell number can (in this embodiment of the WAMIL language) be referenced as X. Thus for script syntax, when a LOOPCELLVARS command is used the CELL number within a script shall be referenced as X from that point forward.
[1998] NOTE:
[1999] For backwards compatibility CELLVAR can be referenced within TI and SDP interface commands as X. Thus a TI interface command would be written as TI:op:cell X instead of as follows, TI:op:cell CELLVAR
[2000] The list of cells can only (in this embodiment of the WAMIL language) be altered by execution of the GETCELLS command. In such a case, the next cell number executed will depend on which loop the script execution is currently in.
[2001] If the list of cells provided is greater than one cell number, the WAM Interpreter will ignore all (in this embodiment of the WAMIL language) DISCONNECT and ENDTEST commands, until the script has been executed for the last cell. In this manner all (in this embodiment of the WAMIL language) interface sessions will remain nailed up until the script has been looped the correct number of times, to avoid login failures during the execution of any cell.
[2002] Execution of a WAM:CELL command within a script with LOOPCELLVARS command will cause the WAM Interpreter to stop looping the script.
[2003] 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.
[2004] WAMI GUI PLATFORM: Prior to execution of a WAMIL script, the WAMI GUI platform searches the script for special commands. If a WAM:LOOPCELLVARS command is encountered the WAMI GUI platform will prompt the user for the script cell numbers. Subsequent WAM:LOOPCELLVARS commands encountered will not cause additional prompting.
[2005] SCRIPTOR: Upon insertion of this command, the Scriptor will remove all (in this embodiment of the WAMIL language) CELL commands, if any, from the script and any cell looping commands, and set the default cell number to the value X. The Scriptor will then regenerate the script using the value X as the default cell number.
[2006] The Scriptor automatically places this command below any (in this WAMIL language embodiment) existing DISPLAY or MSCVAR command. If these commands do not exist, LOOPCELLVARS with be placed at the top of the script.
[2007] If a CELLVAR or a LOOPCELL command exists in the script, upon insertion of the LOOPCELLVARS command they are automatically removed from the script.
[2008] If the LOOPCELLVARS command is deleted from the script, the Scriptor will prompt the user for a cell number and then insert a WAM:CELL command in place of the LOOPCELLVARS command.
[2009] The Scriptor will only (in this embodiment of the WAMIL language) allow one LOOPCELLVARS command to be inserted into a script.
[2010] A syntax error will occur if this command is placed after any (in this WAMIL language embodiment) CONNECT command.
[2011] OUTPUT: Execution of the LOOPCELLVARS command generates the following output to the script WAMIL report file:
[2012] Cell Loop: 1
[2013] Start Test Cell: 49
[2014] ERRORS: Multiple LOOPCELLVARS commands in a script have no additional effects.
[2015] If LOOPCELLVARS is included in a script with the CELLVAR or LOOPCELL command, unpredictable errors may result.
[2016] ALTERS: CELL
[2017] DEFAULT VALUE: None (in this WAMIL language embodiment).
[2018] SEE ALSO: WAM:CELL value, WAM:GETCELLS, WAM:LOOPCELL cells . . .
[2019] EXAMPLE: The following script will loop once for each cell number supplied to the script:
[2020] WAM:MSC 5
[2021] WAM:LOOPCELLVARS
[2022] WAM:CONNECT TI
[2023] TI:op:cell X
[2024] WAM:DISCONNECT TI
[2025] WAM:ENDTEST
[2026] MATHVAR
MATHVAR
[2027] The MATHVAR command can be embedded in the integration construct data structure according to the invention.
[2028] PURPOSE: Causes the WAM Interpreter to perform simple mathematics, per the type of operator provided, on the WAMI VAR variable provided by the argument var_variable.
[2029] SYNTAX: WAM:MATHVAR var_variable operator value
[2030] EXAMPLE CALL: WAM:MATHVAR CELLVAR +500
[2031] DESCRIPTION: The MATHVAR command instructs the WAMI to perform the mathematical operation, provided by the argument operator, on the VAR variable name given by the argument var_variable. The argument value can be any (in this WAMIL language embodiment) positive or negative integer value, or reference any (in this WAMIL language embodiment) existing WAMI VAR variable.
[2032] Valid operators are + for addition, − for subtraction, * for multiplication, and / for division.
[2033] After the execution of this command, all (in this embodiment of the WAMIL language) subsequent commands which require use of a var_variable number will reference the new value.
[2034] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a MATHVAR command:
[2035] CELLVAR is equal to 38+500
[2036] ERRORS: If the argument var_variable is an invalid VAR variable name an error will be generated and script execution will be aborted.
[2037] If an invalid operator is provided an error will be generated and script execution will be aborted.
[2038] If the argument value references an invalid VAR variable name an error will be generated and script execution will be aborted.
[2039] If the argument value is an invalid integer number an error will be generated and script execution will be aborted.
[2040] ALTERS: VAR variable provided by argument var_variable.
[2041] DEFAULT VALUE: None (in this WAMIL language embodiment).
[2042] EXAMPLE: The following script performs an OP CELL on all the even numbered cells on an MSC:
[2043] WAM:MSCVAR
[2044] WAM:SET CELL CELLVAR
[2045] WAM:SETVAR CELLVAR 2
[2046] WAM:CONNECT TI
[2047] WHILE:TEST_EXPR CELLVAR LT 223
[2048] TI:opcell CELLVAR
[2049] WAM:MATHVAR CELLVAR +2
[2050] ENDWHILE:
[2051] WAM:DISCONNECT TI
[2052] WAM:ENDTEST
MICROCELL
[2053] The MICROCELL command can be embedded in the integration construct data structure according to the invention.
[2054] PURPOSE: Changes the WAMI global rcs number variable, MICROCELL, to the value provided as an argument.
[2055] SYNTAX: WAM:MICROCELL value
[2056] EXAMPLE CALL: WAM:MICROCELL 38
[2057] DESCRIPTION: The MICROCELL command sets the WAMI global rcs 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 a rcs number, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script rcs number, will reference the new value.
[2058] 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.
[2059] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution of a MICROCELL command:
[2060] Set RCS To 38
[2061] ERRORS: None.
[2062] ALTERS: MICROCELL
[2063] DEFAULT VALUE: MICROCELL is set to 0 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 0.
[2064] SEE ALSO: WAM:INITIALIZE
MSC
[2065] The MSC command can be embedded in the integration construct data structure according to the invention.
[2066] PURPOSE: Changes the WAM Interpreter global mobile switching center number variable, MSC, to the value provided as an argument.
[2067] SYNTAX: WAM:MSC value
[2068] EXAMPLE CALL: WAM:MSC 5
[2069] DESCRIPTION: The MSC command sets the WAMI global mobile switching center 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 mobile switching center number, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script mobile switching center number, will reference the new value.
[2070] 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.
[2071] SCRIPTOR: If the last MSC command is deleted from the current script, the Scriptor will display an error message notifying the user that no MSC number has been defined for the script.
[2072] If an MSCVAR command is included in the script, the Scriptor will not add an MSC command to the script.
[2073] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of an MSC command:
[2074] Test On MSC 5
[2075] ERRORS: None.
[2076] ALTERS: MSC
[2077] DEFAULT VALUE: MSC is set to 0 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 0.
[2078] SEE ALSO: WAM:MSCVAR, WAM:INITIALIZE
[2079] EXAMPLE: The following script performs an OP CELL on two cells on different mobile switching centers:
[2080] WAM:MSC 5
[2081] WAM:CELL 49
[2082] WAM:CONNECT TI
[2083] TI:opcell 49
[2084] WAM:DISCONNECT TI
[2085] WAM:MSC 1
[2086] WAM:CELL 72
[2087] WAM:CONNECT TI
[2088] TI:opcell 72
[2089] WAM:DISCONNECT TI
[2090] WAM:ENDTEST
MSCVAR
[2091] The MSCVAR command can be embedded in the integration construct data structure according to the invention.
[2092] PURPOSE: Declares to the WAM Interpreter, that a value for the WAMI VAR variable MSCVAR will be supplied to the script.
[2093] SYNTAX: WAM:MSCVAR
[2094] EXAMPLE CALL: WAM:MSCVAR
[2095] DESCRIPTION: The WAM:MSCVAR 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 MSCVAR.
[2096] Like standard WAMI VAR variable declaration commands, the execution of this command also enables an association with the WAMI global MSC variable. Therefore, until the WAMI global MSC variable association is transferred to another WAMI VAR variable, or disabled, all references to the WAMI global MSC variable will use the MSCVAR variable value.
[2097] For script syntax, until an actual MSC number is passed as an argument, when a MSCVAR command is used the MSC number within a script shall be referenced as MSCVAR from that point forward.
[2098] NOTE: For backwards compatibility MSCVAR can be referenced as Y.
[2099] 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.
[2100] WAMI GUI PLATFORM: Prior to execution of a WAMIL script, the WAMI GUI platform searches the script for special commands. If a WAM:MSCVAR is encountered the WAMI GUI platform will prompt the user for the script MSCVAR value. Subsequent WAM:MSCVAR commands encountered will not cause additional prompting.
[2101] SCRIPTOR: If a MSCVAR command is deleted from the current script, the Scriptor will prompt the user for an MSC number and then insert a WAM:MSC value command in place of the MSCVAR command deleted.
[2102] Upon insertion of this command, the Scriptor will remove all (in this embodiment of the WAMIL language) MSC commands, if any, from the script land any cell looping commands, and set the default msc number to the value MSCVAR.
[2103] The Scriptor automatically places this command below any (in this WAMIL language embodiment) existing WAM:DISPLAY command.
[2104] The Scriptor will only (in this embodiment of the WAMIL language) allow one MSCVAR command to be inserted into the current script.
[2105] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a MSCVAR command, when msc 5 is passed as an argument:
[2106] Set MSC To Argument Value of 5
[2107] Start On MSC 5
[2108] ERRORS: If no command line value has been provided, the WAM Interpreter will generate an error and script execution will be aborted.
[2109] ALTERS: MSCVAR
[2110] DEFAULT VALUE: MSCVAR 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.
[2111] SEE ALSO: WAM:MSC value
[2112] EXAMPLE: The following executes a TI command on the msc number supplied:
[2113] WAM:MSCVAR
[2114] WAM:CELL 49
[2115] WAM:CONNECT TI
[2116] TI:op:cell 49
[2117] WAM:DISCONNECT TI
[2118] WAM:ENDTEST
OC
[2119] The OC command can be embedded in the integration construct data structure according to the invention.
[2120] PURPOSE: Changes the WAMI global overhead channel number variable, OC, to the value provided as an argument.
[2121] SYNTAX: WAM:OC value
[2122] EXAMPLE CALL: WAM:OC 1
[2123] DESCRIPTION: The WAM:OC command sets the WAMI global overhead channel 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 a overhead channel number, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script overhead channel number, will reference the new value.
[2124] 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.
[2125] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution of a OC command:
[2126] Set Overhead Channel To 1
[2127] ERRORS: None.
[2128] ALTERS: OC
[2129] DEFAULT VALUE: OC is set to 0 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 0.
[2130] SEE ALSO: WAM:INITIALIZE
[2131] EXAMPLE: The following script lines set the WAMIL script OC variable to 1 and then execute a TI command:
[2132] WAM:CELL 49
[2133] WAM:OC 1
[2134] TI:exc:cell 49, ft oc 1
OPEN
[2135] The OPEN command can be embedded in the integration construct data structure according to the invention.
[2136] PURPOSE: Instructs the WAM Interpreter to open a file to which OutBuff will be saved.
[2137] SYNTAX: WAM:OPEN filename
[2138] EXAMPLE CALL: WAM:OPEN BuffStore
[2139] DESCRIPTION: The OPEN command opens a file, provided by the filename argument, to which OutBuff will continually be appended to until the file is closed with the CLOSE command. If the filename already exists upon initial opening it is overwritten. The file specified by filename is created in the scripts current output directory.
[2140] OutBuff will still continue to be printed in the script WAMIL report file, along with other data, in addition to the filename provided by this command.
[2141] A maximum of only (in this embodiment of the WAMIL language) six OutBuff redirection files can exist at one time within a script.
[2142] The execution of subsequent OPEN commands using the same filename, prior to the execution of a CLOSE command for such filename, causes the file to be closed, overwritten and then re-opened.
[2143] OUTPUT: The following is an example of the output generated to the script WAMIL report file upon execution of an OPEN command:
[2144] Open the WAMI OutBuff Redirection File: BuffStore
[2145] ERRORS: If an error is encountered in execution of the OPEN command, the error message will be output to the WAMIL report file.
[2146] If more than six OutBuff redirection files are opened in a script, the WAM Interpreter will generate an error.
[2147] ALTERS: None (in this WAMIL language embodiment).
[2148] DEFAULT VALUE: None (in this WAMIL language embodiment).
[2149] SEE ALSO: WAM:CLOSE filename
[2150] EXAMPLE: The following script lines will open an OutBuff Redirection file and save the output of a TI command prior to closing the file:
[2151] WAM:OPEN buffstore
[2152] TI:opcell 49, ccc 1, ccu 1
[2153] WAM:OUTPUT buffstore
[2154] WAM:CLOSE buffstore
OUTPUT
[2155] The OUTPUT command can be embedded in the integration construct data structure according to the invention.
[2156] PURPOSE: Instructs the WAM Interpreter to append OutBuff to the file specified.
[2157] SYNTAX: WAM:OUTPUT filename
[2158] EXAMPLE CALL: WAM:OUTPUT BuffStore
[2159] DESCRIPTION: Upon execution of the OUTPUT command the contents of the WAM Interpreter OutBuff will be appended to the filename specified. The file can (in this embodiment of the WAMIL language) have been previously opened using the OPEN command.
[2160] OUTPUT: Execution of the OUTPUT command generates no output messages to the script WAMIL report file.
[2161] ERRORS: If an error is encountered in execution of the OUTPUT command, the error message will be output to the script WAMIL report file.
[2162] If OUTPUT is executed for a filename which has not been previously opened, or has been closed, or does not exist, the WAM Interpreter will generate an error.
[2163] ALTERS: None (in this WAMIL language embodiment)
[2164] DEFAULT VALUE: None (in this WAMIL language embodiment).
[2165] SEE ALSO: WAM:CLOSE filename, WAM:OPEN filename
[2166] EXAMPLE: The following script lines will open an OutBuff Redirection file and save the output of a TI command prior to closing the file:
[2167] WAM:OPEN buffstore
[2168] TI:opcell 49, ccc 1, ccu 1
[2169] WAM:OUTPUT buffstore
[2170] WAM:CLOSE buffstore
OUTPUTOFF
[2171] The OUTPUTOFF command can be embedded in the integration construct data structure according to the invention.
[2172] PURPOSE: Causes the WAM Interpreter to not generate any output messages to the script WAMIL report file for all (in this embodiment of the WAMIL language) general WAM Interpreter commands executed within the script.
[2173] SYNTAX: WAM:OUTPUTOFF
[2174] EXAMPLE CALL: WAM:OUTPUTOFF
[2175] DESCRIPTION: The OUTPUTOFF command provides a means of disabling WAM Interpreter command output messages. Almost all (in this embodiment of the WAMIL language) WAM Interpreter commands generate output messages to the script output file. Execution of the OUTPUTOFF command will disable the generation of these output messages. The only (in this embodiment of the WAMIL language) remaining messages in the script output file will then be those generated by special function WAM Interpreter commands, and messages returned from interface commands.
[2176] Below is a list of WAM Interpreter (WAMI) commands whose output messages are not disabled by execution of the OUTPUTOFF command:
| WAMI COMMAND |
|---|
[2177] OUTPUT: Execution of the OUTPUTOFF command generates no output.
[2178] ERRORS: None.
[2179] ALTERS: None (in this WAMIL language embodiment).
[2180] DEFAULT VALUE: None (in this WAMIL language embodiment).
[2181] SEE ALSO: WAM:OUTPUTON
OUTPUTON
[2182] The OUTPUTON command can be embedded in the integration construct data structure according to the invention.
[2183] PURPOSE: Causes the WAM Interpreter to generate all (in this embodiment of the WAMIL language) output messages to the script WAMIL report file for all (in this embodiment of the WAMIL language) WAM Interpreter commands executed within the script.
[2184] SYNTAX: WAM:OUTPUTON
[2185] EXAMPLE CALL: WAM:OUTPUTON
[2186] DESCRIPTION: The OUTPUTON command enables WAM Interpreter command output messages. Almost all (in this embodiment of the WAMIL language) WAM Interpreter commands generate output messages to the script output file. Execution of the OUTPUTON command will enable the generation of these output messages.
[2187] WAM Interpreter output messages are enabled as default, upon the start of script execution. To disable these output messages the OUTPUTOFF display command can (in this embodiment of the WAMIL language) be executed.
[2188] OUTPUT: Execution of the OUTPUTON command generates no output.
[2189] ERRORS: None.
[2190] ALTERS: None (in this WAMIL language embodiment).
[2191] DEFAULT VALUE: None (in this WAMIL language embodiment).
[2192] SEE ALSO: WAM:OUTPUTOFF
PAUSE
[2193] The PAUSE command can be embedded in the integration construct data structure according to the invention.
[2194] PURPOSE: Instructs the WAM Interpreter to stop execution of the WAMIL script and prompt the user for continuation or termination.
[2195] SYNTAX: WAM:PAUSE string
[2196] EXAMPLE CALL: WAM:PAUSE Go Pull Board
[2197] DESCRIPTION: The PAUSE command instructs the WAM Interpreter to stop execution of the WAMIL script and display a message to the user. The message displayed is provided by the argument string, and is displayed in a WAMI PAUSE window which allows the user to either continue with execution of the WAMIL script, or abort the script. As many PAUSE commands as desired can be included in a WAMIL script.
[2198] To abort the WAMIL script execution, the user simply selects the “ABORT” command button displayed in the WAMI PAUSE window. To continue execution of the WAMIL script, the user simply selects the “CONTINUE” command button displayed in the WAMI PAUSE window.
[2199] If the user aborts the script, the script will be terminated and the WAMI Status Display window will show the status “Aborted”. The WAMI Status Display window, will however, not be destroyed.
[2200] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a PAUSE command with the string “Go Pull Board” provided as an argument:
[2201] Manual Pause: Go Pull Board
[2202] If a user selects the ABORT command button, the following message will be printed in the WAMIL report file:
[2203] SCRIPT ABORTED!
[2204] WAMI WINDOW: Below is an example of a WAMI PAUSE window generated upon execution of a PAUSE command with the string “Go Pull Board” provided as an argument:
[2205] ERRORS: None.
[2206] ALTERS: None (in this WAMIL language embodiment).
[2207] DEFAULT VALUE: None (in this WAMIL language embodiment).
[2208] EXAMPLE: The following script prompts the user for continuation:
[2209] WAM:MSC 5
[2210] WAM:CELL 49
[2211] WAM:PAUSE IF CELL IS DOWN ABORT SCRIPT!!!
[2212] WAM:CONNECT TI
[2213] TI:op:cell, generic
[2214] WAM:DISCONNECT TI
[2215] WAM:ENDTEST
PH
[2216] The PH command can be embedded in the integration construct data structure according to the invention.
[2217] PURPOSE: Changes the WAMI global phase number variable, PH, to the value provided as an argument.
[2218] SYNTAX: WAM:PH value
[2219] EXAMPLE CALL: WAM:PH 5
[2220] DESCRIPTION: The PH command sets the WAMI global phase 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 a phase number, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script phase number, will reference the new value.
[2221] 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.
[2222] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution of a PH command:
[2223] Set Phase Number To 1
[2224] ERRORS: None.
[2225] ALTERS: PH
[2226] DEFAULT VALUE: PH is set to 0 upon initial startup, and is of type string. The WAM:INITIALIZE command also sets this variable to 0.
[2227] SEE ALSO: WAM:INITIALIZE
[2228] EXAMPLE: The following script lines set the WAMIL script PH variable to 16 and then execute a TI command:
[2229] WAM:CELL 49
[2230] WAM:CSC 1
[2231] WAM:RPT 3
[2232] WAM:PH 16
[2233] TI:dgn:cell 49, csc 1; rpt 3, raw, uc1: ph 16
PL
[2234] The PL command can be embedded in the integration construct data structure according to the invention.
[2235] PURPOSE: Changes the WAMI global pilot level number variable, PL, to the value provided as an argument.
[2236] SYNTAX: WAM:PL value
[2237] EXAMPLE CALL: WAM:PL 6
[2238] DESCRIPTION: The PL command sets the WAMI global pilot level 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 a pilot level number, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script pilot level number, will reference the new value.
[2239] 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.
[2240] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution of a PL command:
[2241] Set Pilot Level To 1
[2242] ERRORS: None.
[2243] ALTERS: PL
[2244] DEFAULT VALUE: PL is set to 0 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 0.
[2245] SEE ALSO: WAM:INITIALIZE
[2246] EXAMPLE: The following script lines will change the WAMIL script PH variable to 6 and then execute a TI command:
[2247] WAM:CELL 49
[2248] WAM:PL 6
[2249] TI:exc:cell 49, ft pl 6
[2250] The PRINT command can be embedded in the integration construct data structure according to the invention.
[2251] PURPOSE: Instructs the WAM Interpreter to print the string provided in the script WAMIL report file.
[2252] SYNTAX: WAM:PRINT string
[2253] EXAMPLE CALL: WAM:PRINT This is test case jt1234
[2254] DESCRIPTION: The PRINT command prints the string provided as an argument in the script WAMIL report file.
[2255] The string provided can include references to WAMI global variables, or WAMI VARn variables. To reference a WAMI global variable the suffix VAR is simply added to the WAMI global variable name. For example, the following string, CCC CCCVAR is OOS, will be interpreted and printed as follows for a WAMI global CCC variable with a value of 4:
[2256] CCC 4 is OOS
[2257] This is not to be mistaken with WAMI VAR variables. Although when referencing WAMI global variables within strings to be printed the names resemble WAMI VAR variables, this naming convention was chosen to allow references to WAMI global variables and still be able to print the variable name. In the above example the WAMI global name CCC was printed along with the value of the WAMI global variable. To print the value of a WAMI VAR variable, a WAMI global variable can (in this embodiment of the WAMIL language) first be associated. Then references to the WAMI global variable will yield the value of the WAMI VAR variable it is associated with.
[2258] OUTPUT: The string provided is printed in the script WAMIL report file as given. Variable substitution is performed if WAMI global variables are referenced within the string provided.
[2259] The following is an example of the output generated to the WAMIL report file upon execution of a PRINT command which includes reference to a WAMI global variable:
[2260] This test Is For Antenna Face 1.
[2261] ERRORS: None.
[2262] ALTERS: None (in this WAMIL language embodiment).
[2263] DEFAULT VALUE: None (in this WAMIL language embodiment).
[2264] EXAMPLE: The following script lines print the antenna face and cell number to the script WAMIL report file:
[2265] WAM:CELL 49
[2266] WAM:ANT 1
[2267] WAM:PRINT Test Antenna Face ANTVAR, on Cell CELLVAR.
PUTAPX
[2268] The PUTAPX command can be embedded in the integration construct data structure according to the invention.
[2269] PURPOSE: Instructs the WAM Interpreter to replace the APXRCV DB form, provided as an argument, with the DB filename provided.
[2270] SYNTAX: WAM:PUTAPX db_form_name db_file_name
[2271] EXAMPLE CALL: WAM:PUTAPX fci FCIBACKUP
[2272] DESCRIPTION: The PUTAPX command is a special WAMI functional command which instructs the WAM Interpreter to replace the APXRCV DB form, provided by the argument db_form_name, with the db_file_name located in the current script output directory.
[2273] The current script output directory is set through the WAMI GUI platform via the user configuration options, or by command line execution of the WAM Interpreter with the -rpt switch, and defaults to Scripts.dir if no sub-directory is specified.
[2274] The DB form filename is automatically assumed the extension .dbf The APXRCV DB form replaced will depend on the current values of the WAMI global variables prior to execution of the PUTAPX command. For example, if the WAMI global variable CELL is set to 49, and SG is set to 1, and ANT is set to 1, and the following command is executed:
[2275] WAM:PUTAPX fci FCIBACKUP
[2276] The fci translation DB form for cell 49, server group 1, antenna face 1 will be replaced by the filename FCIBACKUP located in the current script output directory.
[2277] DB FORMS: For a list of APXRCV DB forms supported by this command refer to the GETAPX command.
[2278] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a PUTAPX command:
[2279] Replace APXRCV DB Form fci With DB File FCIBACKUP
[2280] ERRORS: If during the initial login attempt the connection attempt fails due to lack of system response, the WAM Interpreter LFAIL flag will be set. The WAM Interpreter will then, for example, generate the following output to the WAMIL report file:
[2281] WAMI OMP 5 Timeout. Login Attempt Failed!
[2282] A user can test the LFAIL flag within a WAMIL script to check if a login attempt was successful prior to the execution of any (in this WAMIL language embodiment) subsequent WAMIL commands.
[2283] If during the initial login attempt the connection once established is lost, the WAM Interpreter CFAIL flag will be set. The WAM Interpreter will then, for example, generate the following output to the WAMIL report file:
[2284] WAMI OMP 5 Connection Lost!
[2285] A user can test the CFAIL flag within a WAMIL script to check if a connection was lost prior to the execution of any (in this WAMIL language embodiment) subsequent WAMIL commands.
[2286] Once a connection is established, if during the APXRCV session the connection is lost, the WAM Interpreter will set the CFAIL flag also. The WAM Interpreter will then, for example, generate the following output to the WAMIL report file:
[2287] WAMI APXRCV Session Connection Lost!
[2288] If the connection times out at any (in this WAMIL language embodiment) point during the update of data to the APXRCV, meaning no response is received from the APXRCV within the time specified by the WAMI global TimeOut variable, the WAM Interpreter TFAIL flag will be set. The WAM Interpreter will then, for example, generate the following output to the WAMIL report file:
[2289] WAMI APXRCV Timeout!
[2290] A user can test the TFAIL flag within a WAMIL script to check if the data update did not time out prior to the execution of any (in this WAMIL language embodiment) subsequent WAMIL commands.
[2291] If an invalid, or not supported, DB form is provided as an argument, the WAM Interpreter will generate an error.
[2292] If an error occurs in replacing the APXRCV DB form file, the WAM Interpreter will generate an error and the form will not be replaced.
[2293] During execution of the PUTAPX command, all (in this embodiment of the WAMIL language) APXRCV errors and messages will be printed to the WAMIL report file.
[2294] ALTERS: None (in this WAMIL language embodiment).
[2295] DEFAULT VALUE: None (in this WAMIL language embodiment).
[2296] SEE ALSO: WAM:GETAPX db_form_name db_file_name, WAM:PUTAPXFLD db_form_name db_field_name
[2297] EXAMPLE: The following script will replace the fci DB form for all antenna faces for cell 49, server group 1:
[2298] WAM:MSC 5
[2299] WAM:CELL 49
[2300] WAM:SG 1
[2301] WAM:ANT 1
[2302] WAM:PUTAPX fci FCIBACKUP1
[2303] WAM:ANT 2
[2304] WAM:PUTAPX fci FCIBACKUP2
[2305] WAM:ANT 3
[2306] WAM:PUTAPX fci FCIBACKUP3
[2307] WAM:ENDTEST
PUTAPXFLD
[2308] The PUTAPXFLD command can be embedded in the integration construct data structure according to the invention.
[2309] PURPOSE: Instructs the WAM Interpreter to replace the APXRCV DB form field name, provided as an argument, with the current value of the WAMI VAR variable APXVAR.
[2310] SYNTAX: WAM:PUTAPXFLD db_form_name db_field_name
[2311] EXAMPLE CALL: WAM:PUTAPXFLD ceqsu2 rmi_thresh
[2312] DESCRIPTION: The PUTAPXFLD command instructs the WAM Interpreter to replace the APXRCV DB form field name, provided by the argument db_field_name, located in the DB form db_form_name, with the current value of the WAMI VAR variable APXVAR.
[2313] The APXRCV DB form field replaced will depend on the current value of the WAMI global variables prior to execution of the PUTAPXFLD command. For example, if the WAMI global variable CELL is set to 49, and ANT is set to 1, and the following command is executed:
[2314] WAM:PUTAPXFLD ceqsu2 rmi_thresh
[2315] The ceqsu2 DB form rmi_thresh field value, for cell 49, antenna face 1, will be replaced with the current value of the WAMI VAR variable APXVAR.
[2316] DB FORMS: For a list of APXRCV DB forms supported by this command, refer to the GETAPX command.
[2317] OUTPUT: The PUTAPXFLD command automatically executes a PUTAPX command. Therefore the initial output generated by this command is the same as execution of the PUTAPX command. Once the DB form field has been replaced, the output generated upon completion of this process will then be the following:
[2318] Replaced APXRCV DB Form cell2 Field rmi_thresh With Value 0
[2319] ERRORS: See PUTAPX command.
[2320] If APXVAR is set to INVALID, ERROR, or NULL upon execution of the PUTAPXFLD command, the field value will not be replaced, and the WAM Interpreter will generate an error.
[2321] If an error occurs in replacing the APXRCV DB form field value, the WAM Interpreter will generate an error and the field will not be replaced.
[2322] During execution of the PUTAPXFLD command, all (in this embodiment of the WAMIL language) APXRCV errors and messages will be printed to the WAMIL report file.
[2323] ALTERS: APXVAR.
[2324] DEFAULT VALUE: APXVAR is set to NULL upon initial startup, unless altered by execution of the GETAPXFLD command, and is of type string. The WAM:INITIALIZE command does not alter this variable.
[2325] SEE ALSO: WAM:GETAPXFLD db_form_name db_field_name, WAM:PUTAPX db_form_name db_file_name
[2326] EXAMPLE: The following script will replace a field value in an APXRCV DB form, only if the value is not set to zero:
[2327] WAM:MSC 5
[2328] WAM:CELL 49
[2329] WAM:ANT 1
[2330] WAM:GETAPXFLD ceqsu2 rmi_thresh
[2331] IF:APXVAR NE 0
[2332] THENDO:
[2333] WAM:SETVAR APXVAR 0
[2334] WAM:PUTAPXFLD ceqsu2 rmi_thresh
[2335] ELSEDO:
[2336] ENDIF:
[2337] WAM:ENDTEST
PUTS
[2338] The PUTS command can be embedded in the integration construct data structure according to the invention.
[2339] PURPOSE: Instructs the WAM Interpreter to append the string provided to the filename located at path.
[2340] SYNTAX: WAM:PUTS path filename string
[2341] EXAMPLE CALL: WAM:PUTS HOME TestsResults jt1234 FAIL
[2342] DESCRIPTION: The PUTS command instructs the WAM Interpreter to append the string provided to the filename located at path.
[2343] The argument path can be any (in this WAMIL language embodiment) valid, complete UNIX pathname. The PUTS command allows the WAM Interpreter path keywords to be used for the path argument. When the SHARE or CERT path keywords are used, the file location will default to the wam.results sub-directory.
[2344] If the file does not exist upon execution of the PUTS command it is created. If the file already exists the string given is appended to the end of the file.
[2345] The PUTS command filename and string arguments can also include references to WAMI global variables, or WAMI VARn variables. To reference a WAMI global variable the suffix VAR is simply added to the WAMI global variable name. For example, the following string, CCC CCCVAR is OOS, will be interpreted and printed as follows for a WAMI global CCC variable with a value of 4:
[2346] CCC 4 is OOS
[2347] This is not to be mistaken with WAMI VAR variables. Although when referencing WAMI global variables within strings to be printed the names resemble WAMI VAR variables, this naming convention was chosen to allow references to WAMI global variables and still be able to print the variable name. In the above example the WAMI global name CCC was printed along with the value of the WAMI global variable. To print the value of a WAMI VAR variable, a WAMI global variable can (in this embodiment of the WAMIL language) first be associated. Then references to the WAMI global variable will yield the value of the WAMI VAR variable it is associated with.
[2348] The PUTS command also supports WAM Interpreter print keywords which if included in the string argument will be substituted with the corresponding character or information.
[2349] If the keyword STDOUT is used as the path argument, the WAM Interpreter will print the remaining arguments as a string to standard output.
[2350] OUTPUT: The string provided is printed in the filename given. Variable substitution is performed if WAMI global variables or keywords are referenced within the string provided.
[2351] ERRORS: If any (in this WAMIL language embodiment) errors occur in opening the filename specified, such errors will be printed in the WAMIL report file.
[2352] ALTERS: None (in this WAMIL language embodiment).
[2353] DEFAULT VALUE: None (in this WAMIL language embodiment).
[2354] SEE ALSO: WAM:PRINT string
[2355] EXAMPLE: The following script generates a DB file which is then used to change a specific cell neighbor list up to Six neighbors cells total:
[2356] WAM:MSCVAR
[2357] WAM:CELLVAR
[2358] WAM:WAMLIST Enter Up To Six Cells For Neighbor List
[2359] WAM:PUTS HOME SIXNEIGH.dbf cdmanbr_list1.ncs_c[1]=WAMVAR1
[2360] WAM:PUTS HOME SIXNEIGH.dbf cdmanbr_list1.ncs_c[2]=WAMVAR2
[2361] WAM:PUTS HOME SIXNEIGH.dbf cdmanbr_list1.ncs_c[3]=WAMVAR3
[2362] WAM:PUTS HOME SIXNEIGH.dbf cdmanbr_list1.ncs_c[4]=WAMVAR4
[2363] WAM:PUTS HOME SIXNEIGH.dbf cdmanbr_list1.ncs_c[5]=WAMVAR5
[2364] WAM:PUTS HOME SIXNEIGH.dbf cdmanbr_list1.ncs_c[6]=WAMVAR6
[2365] WAM:PUTS HOME SIXNEIGH.dbf cdmanbr_list1.ncs_c[7]=WAMVAR7
[2366] WAM:PUTS HOME SIXNEIGH.dbf cdmanbr_list1.ncs_c[8]=WAMVAR8
[2367] WAM:PUTS HOME SIXNEIGH.dbf cdmanbr_list1.ncs_c[9]=WAMVAR9
[2368] WAM:PUTS HOME SIXNEIGH.dbf cdmanbr_list1.ncs_c[10]=WAMVAR10
[2369] WAM:PUTS HOME SLXNEIGH.dbf cdmanbr_list1.ncs_c[11]=WAMVAR11
[2370] WAM:PUTS HOME SIXNEIGH.dbf cdmanbr_list1.ncs_c[12]=WAMVAR12
[2371] WAM:PUTAPX fci SIXNEIGH
[2372] WAM:ENDTEST
RA
[2373] The RA command can be embedded in the integration construct data structure according to the invention.
[2374] PURPOSE: Changes the WAMI global radio number variable, RA, to the value provided as an argument.
[2375] SYNTAX: WAM:RA value
[2376] EXAMPLE CALL: WAM:RA 39
[2377] DESCRIPTION: The RA command sets the WAMI global radio 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 a radio number, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script radio number, will reference the new value.
[2378] 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.
[2379] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution of a RA command:
[2380] Set Cell Radio To 1
[2381] ERRORS: None.
[2382] ALTERS: RA
[2383] DEFAULT VALUE: RA is set to 0 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 0.
[2384] SEE ALSO: WAM:INITIALIZE
[2385] EXAMPLE: The following script lines set the WAMIL script RA variable to 39 and then execute a TI command:
[2386] WAM:CELL 49
[2387] WAM:RA 39
[2388] TI:op:cell 49, ra 39
RALIST
[2389] The RALIST command can be embedded in the integration construct data structure according to the invention.
[2390] PURPOSE: Declares to the WAM Interpreter, that a list of WAMI VARn RA numbers will be supplied to the script.
[2391] SYNTAX: WAM:RALIST value
[2392] EXAMPLE CALL: WAM:RALIST 3
[2393] DESCRIPTION: The RALIST command is a WAMIL declaration command which instructs the WAM Interpreter that a list of RA numbers will be supplied to the script. This command executes the assignment of the RA numbers provided to the WAMI VARn RA List.
[2394] Upon detection of this command, the WAM Interpreter will search the command line arguments for the RA numbers. The total number of RAs to assign is determined by the value argument of the command. This value declares to the WAM Interpreter the exact size of the RA List. The RA numbers within the RA List can then be referenced within the script as WAMI VARn variables, according to their index position in the list. For example, RAVAR2 refers to the second RA number in the RA List. The order of the RA numbers provided determine the order of their placement within the RA List.
[2395] Up to 200 RA numbers can be passed as an argument with this command. Therefore, the maximum acceptable size for the RA List is 200. If a value larger than 200 is used the WAM Interpreter will generate an error and script execution will be aborted.
[2396] 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.
[2397] WAMI GUI PLATFORM: Prior to execution of a WAMIL script, the WAMI GUI platform searches the script for special commands. If a WAM:RALIST command is encountered the WAMI GUI platform will prompt the user for the quantity of RA numbers defined by the command argument value. Subsequent WAM:RALIST commands encountered will not cause additional prompting.
[2398] SCRIPTOR: If this command is deleted from the current script, the WAMIL Scriptor will delete all (in this embodiment of the WAMIL language) reference RAVARn commands existing in the script also. The script WAMI global RA variable will then be set to the default value of 0.
[2399] The Scriptor will only (in this embodiment of the WAMIL language) allow insertion of one RALIST command into the current script.
[2400] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a RALIST command:
[2401] Total Number of RA List Values Set To 4
[2402] RA List Values: 2 4 6 8
[2403] ERRORS: If a value larger than 200 is used the WAM Interpreter will generate an error and script execution will be aborted.
[2404] Any references within a script to a WAMI VARn variable prior to the declaration of the list will generate a syntax error.
[2405] If more than one RALIST 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 RALIST commands have no effect.
[2406] ALTERS: WAMI VARn RA List.
[2407] DEFAULT VALUE: The WAMI VARn RA 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.
[2408] SEE ALSO: WAM:RAVARn, WAM:INITIALIZE
[2409] EXAMPLE: The following script sets the WAMI VARn RA List length to 2, and executes a TI command for each RA number in the list:
[2410] WAM:MSC 5
[2411] WAM:CELL 49
[2412] WAM:RALIST 2
[2413] WAM:CONNECT TI
[2414] WAM:RAVAR1
[2415] TI:op:cell 49, ra RAVAR1
[2416] WAM:RAVAR2
[2417] TI:op:cell 49, ra RAVAR2
[2418] WAM:DISCONNECT TI
[2419] WAM:ENDTEST
RAVAR
[2420] The RAVAR command can be embedded in the integration construct data structure according to the invention.
[2421] PURPOSE: Declares to the WAM Interpreter, that a value for the WAMI VAR variable RAVAR will be supplied to the script.
[2422] SYNTAX: WAM:RAVAR
[2423] EXAMPLE CALL: WAM:RAVAR
[2424] DESCRIPTION: The WAM:RAVAR 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 RAVAR.
[2425] Like standard WAMI VAR variable declaration commands, the execution of this command also enables an association with the WAMI global RA variable. Therefore, until the WAMI global RA variable association is transferred to another WAMI VAR variable, or disabled, all (in this embodiment of the WAMIL language) references to the WAMI global RA variable will use the RAVAR variable value.
[2426] For script syntax, until an actual RA number is passed as an argument, when a RAVAR command is used the RA number within a script shall be referenced as RAVAR from that point forward.
[2427] 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.
[2428] WAMI GUI PLATFORM: Prior to execution of a WAMIL script, the WAMI GUI platform searches the script for special commands. If a WAM:RAVAR is encountered the WAMI GUI platform will prompt the user for the script RAVAR value. Subsequent WAM:RAVAR commands encountered will not cause additional prompting.
[2429] SCRIPTOR: If a RAVAR command is deleted from the current script, the Scriptor will prompt the user for a RA number and then insert a WAM:RA value command in place of the RAVAR command deleted.
[2430] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution a RAVAR command:
[2431] Set RA To Argument Value of 8
[2432] ERRORS: If no command line value has been provided, the WAM Interpreter will generate an error and script execution will be aborted.
[2433] ALTERS: RAVAR
[2434] DEFAULT VALUE: RAVAR 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.
[2435] SEE ALSO: WAM:RA value
[2436] EXAMPLE: The following script executes a TI command for the RA number supplied:
[2437] WAM:MSC 5
[2438] WAM:CELL 49
[2439] WAM:RAVAR
[2440] WAM:CONNECT TI
[2441] TI:op:cell 49, ra RAVAR
[2442] WAM:DISCONNECT TI
[2443] WAM:ENDTEST
RAVARn
[2444] The RAVARn command can be embedded in the integration construct data structure according to the invention.
[2445] PURPOSE: Instructs the WAM Interpreter to set the WAMI global RA variable to the value of the referenced WAMI VARn RA variable, in position n, of the RA List passed as an argument.
[2446] SYNTAX: WAM:RAVARn
[2447] EXAMPLE CALL: WAM:RAVAR2
[2448] DESCRIPTION: The WAM:RAVARn command is an assignment command. This command can only (in this embodiment of the WAMIL language) be executed if a RA List has been declared in the script. Upon execution, this command assigns a RA List variable value to the WAMI global RA variable.
[2449] The value n, can (in this embodiment of the WAMIL language) be a valid index into the RA List. Any RA List value can be assigned to the WAMI global RA variable by execution of this command, where n is the RA value location within the RA List. Upon execution, the RA number within a script is referenced as RAVARn from that point forward.
[2450] Like standard WAMI VARn variable assignment commands, the execution of this command also enables an association with the WAMI global RA variable. Therefore, until the WAMI global RA variable association is transferred to a WAMI VAR variable, or disabled, all (in this embodiment of the WAMIL language) references to the WAMI global RA variable will use the RAVARn variable value.
[2451] For script syntax, until actual RA List values are passed as an argument, when a RAVARn command is used the RA number within a script shall be referenced as RAVARn from that point forward.
[2452] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a RAVARn command, when a RA List of 3 was previously declared, and the RA List numbers passed as an argument are 2 4 6:
[2453] Set RA To RAVAR2 Value Of 4
[2454] SCRIPTOR: If a RAVARn command is deleted from the current script, the Scriptor will prompt the user for a RA number and then insert a WAM:RA value command in place of the RAVARn command deleted.
[2455] ERRORS: An invalid RAVARn command used within a script, where n refers to a RA List index outside the list range, will generate an error. Script execution will then be aborted.
[2456] If a RAVARn command is used within a script in which no RA List has been declared, the WAM Interpreter will generate an error and terminate execution of the script.
[2457] ALTERS: RA
[2458] DEFAULT VALUE: None (in this WAMIL language embodiment).
[2459] SEE ALSO: WAM:RA value, WAM:RALIST value
[2460] EXAMPLE: The following script sets the WAMI VARn RA List length to 2, and executes a TI command for each RA number in the list:
[2461] WAM:MSC 5
[2462] WAM:CELL 49
[2463] WAM:RALIST 2
[2464] WAM:CONNECT TI
[2465] WAM:RAVAR1
[2466] TI:op:cell 49, ra RAVAR1
[2467] WAM:RAVAR2
[2468] TI:op:cell 49, ra RAVAR2
[2469] WAM:DISCONNECT TI
[2470] WAM:ENDTEST
REPORT
[2471] The REPORT command can be embedded in the integration construct data structure according to the invention.
[2472] PURPOSE: Instructs the WAM Interpreter to name the script WAMIL report file as the string provided as an argument.
[2473] SYNTAX: WAM:REPORT string
[2474] EXAMPLE CALL: WAM:REPORT jt1234
[2475] DESCRIPTION: The REPORT command provides the WAM Interpreter with the script WAMIL report file name. If no REPORT command exists within a script, the script output report name will default to the script name with a .rpt extension. For example, a WAMIL script called jt1234.wamil, will generate a report file called jt1234.rpt, unless a REPORT command with a different report name is included in the WAMIL script. The .rpt extension is automatically added to the file name by the WAM Interpreter.
[2476] A WAMIL report file generated by execution of a script is placed in a user specified output directory. This output directory can be set through the WAMI GUI platform via the user configuration options, or by command line arguments by use of the -rpt switch. If no output directory is specified the WAM Interpreter will place the output file in the default HOME Scripts.dir directory.
[2477] If the script report name already exists the file is overwritten with the newly generated output, unless the WAM Interpreter append option is specified.
[2478] OUTPUT: The WAM Interpreter always prints the WAMIL script report file name in the generated report file, regardless of whether the REPORT command is included in the script or not.
[2479] ERRORS: None.
[2480] The report name and path are both printed in the WAMIL report file, along with the script name and path.
[2481] ALTERS: Report Name
[2482] DEFAULT VALUE: The Report Name is set to NONE upon initial startup, and defaults to the script name. The WAM:INITIALIZE command also sets this variable to None.
[2483] SEE ALSO: WAM:INITIALIZE
[2484] EXAMPLE: The following script includes a report name:
[2485] WAM:REPORT jt1234
[2486] WAM:MSC 5
[2487] WAM:CELL 49
[2488] WAM:RA 39
[2489] WAM:CONNECT TI
[2490] TI:op:cell 49, ra 39
[2491] WAM:DISCONNECT TI
[2492] WAM:ENDTEST
RESTOREWAM
[2493] The RESTOREWAM command can be embedded in the integration construct data structure according to the invention.
[2494] PURPOSE: Restores all (in this embodiment of the WAMIL language) WAM Interpreter variables, flags, and states to the values and states saved by the previous execution of the SAVEWAMI command.
[2495] SYNTAX: WAM:RESTOREWAM
[2496] EXAMPLE CALL: WAM:RESTOREWAM
[2497] DESCRIPTION: The RESTOREWAMI command restores all (in this embodiment of the WAMIL language) the WAMI global variables, WAMI VAR variables, WAMI VARn List variables, flags, and states to the values and states which had been saved by the previous SAVEWAMI command executed.
[2498] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a RESTOREWAMI command:
[2499] Restore All WAMI Variables, Flags, and States.
[2500] ERRORS: If the RESTOREWAMI command is executed in a WAMIL script, and a SAVEWAMI command was not previously executed, all (in this embodiment of the WAMIL language) the WAMI variables, flags, and states will be set to initial WAMI values and unpredictable errors may result.
[2501] ALTERS: All WAMI variables, flags, and states.
[2502] DEFAULT VALUE: Initial WAMI variables, flags, and states values.
[2503] SEE ALSO: WAM:INITIALIZE, WAM:SAVEWAM
[2504] EXAMPLE: The following script lines will save the WAM Interpreter states, execute a sub-WAMIL script, and then restore the WAM Interpreter states back after completion of the sub-WAMIL script execution:
[2505] WAM:SAVEWAM
[2506] WAM:EXEC SHARE jt1234_wrapup
[2507] WAM:RESTOREWAM
RG
[2508] The RG command can be embedded in the integration construct data structure according to the invention.
[2509] PURPOSE: Changes the WAMI global reference generator number variable, RG, to the value provided as an argument.
[2510] SYNTAX: WAM:RG value
[2511] EXAMPLE CALL: WAM:RG 1
[2512] DESCRIPTION: The RG command sets the WAMI global reference generator 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 a reference generator number, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script reference generator number, will reference the new value.
[2513] 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.
[2514] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution of a RG command:
[2515] Set Reference Generator To 1
[2516] ERRORS: None.
[2517] ALTERS: RG
[2518] DEFAULT VALUE: RG is set to 0 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 0.
[2519] SEE ALSO: WAM:INITLALIZE
[2520] EXAMPLE: The following script lines set the WAMIL script RG variable to 1 and then execute a TI command:
[2521] WAM:CELL 49
[2522] WAM:RG 1
[2523] TI:op:cell 49, rg 1
RPT
[2524] The RPT command can be embedded in the integration construct data structure according to the invention.
[2525] PURPOSE: Changes the WAMI global diagnostics repeat number variable, RPT, to the value provided as an argument.
[2526] SYNTAX: WAM:RPT value
[2527] EXAMPLE CALL: WAM:RPT 10
[2528] DESCRIPTION: The RPT command sets the WAMI global diagnostics repeat 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 a diagnostics repeat number, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script diagnostics repeat number, will reference the new value.
[2529] 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.
[2530] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a RPT command:
[2531] Set Diagnostics Repeat Number To 1
[2532] ERRORS: None.
[2533] ALTERS: RPT
[2534] DEFAULT VALUE: RPT is set to 0 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 0.
[2535] SEE ALSO: WAM:INITIALIZE
[2536] EXAMPLE: The following script lines set the WAMIL script RPT variable to and then execute a TI command:
[2537] WAM:CELL 49
[2538] WAM:RPT 10
[2539] TI:dgn:cell 49, bba 2; rpt 10
SAVEWAM
[2540] The SAVEWAM command can be embedded in the integration construct data structure according to the invention.
[2541] PURPOSE: Saves all (in this embodiment of the WAMIL language) current WAM Interpreter variables, flags, and states.
[2542] SYNTAX: WAM:SAVEWAM
[2543] EXAMPLE CALL: WAM:SAVEWAM
[2544] DESCRIPTION: The SAVEWAMI command saves all (in this embodiment of the WAMIL language) the current WAMI global variables, WAMI VAR variables, WAMI VARn List variables, flags, and states. This command is useful to perform a backup of the current state of your WAMIL script prior to changing any (in this WAMIL language embodiment) variables or executing any (in this WAMIL language embodiment) sub-WAMIL scripts.
[2545] Subsequent execution of additional SAVEWAMI commands overwrites the values saved from the previous execution of the command.
[2546] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a SAVEWAMI command:
[2547] Save All WAMI Variables, Flags, and States.
[2548] ERRORS: None.
[2549] ALTERS: None (in this WAMIL language embodiment).
[2550] DEFAULT VALUE: None (in this WAMIL language embodiment).
[2551] SEE ALSO: WAM:RESTOREWAM
[2552] EXAMPLE: The following script lines will save the WAM Interpreter values and states, execute a sub-WAMIL script, and then restore the WAM Interpreter values and states back after completion of the sub-WAMIL script execution:
[2553] WAM:SAVEWAM
[2554] WAM:EXEC SHARE jt1234_wrapup
[2555] WAM:RESTOREWAM
SEND
[2556] The SEND command can be embedded in the integration construct data structure according to the invention.
[2557] PURPOSE: Instructs the WAM Interpreter to send string to the interface provided as an argument.
[2558] SYNTAX: WAM:SEND interface string
[2559] EXAMPLE CALL: WAM:SEND TI:rst:cell CELLVAR, CCC CCCVAR; ucl
[2560] DESCRIPTION: The SEND command instructs the WAM Interpreter to send the command provided by the argument string, to the WAMI interface provided by the argument interface, as a straightforward interface command. The string provided is executed as if it were an acceptable command for the interface. The output of the interface in respect to the string sent is stored in the WAMI buffer upon completion of execution of the command.
[2561] WARNING: Execution of the SEND command does not include interface command expansion and syntax checking for verification of variables referenced within the string provided, to confirm if values are equal to the current script values. Straightforward variables substitution is performed and the string provided is sent as an interface command. Caution can (in this embodiment of the WAMIL language) be practiced in the use of this command to ensure the right values are sent to the interface provided.
[2562] The SEND command string argument can also include references to WAMI global variables, or WAMI VARn variables. To reference a WAMI global variable the suffix VAR is simply added to the WAMI global variable name. For example, the following string,
[2563] op:cell CELLVAR, ccc CCCVAR
[2564] will be interpreted and sent as follows for a WAMI global CELL and CCC variables set to values of 49 and 6:
[2565] op:cell 49, ccc 6
[2566] INTERFACES: The following interfaces are supported by the SEND command:
| INTERFACE | DESCRIPTION | |
|---|---|---|
| TI | TIpdunix | |
| SDP | Status Display Page | |
[2567] OUTPUT: The output generated by the SEND command is dependant upon the interface to which the command is sent.
[2568] ERRORS: If a SEND command is executed and no session has been established for the interface provided, the WAMI will generate a fatal error and execution of the script will be aborted. The error message will be printed in the WAMIL script output file.
[2569] ALTERS: WAM Interpreter buffer.
[2570] DEFAULT VALUE: None (in this WAMIL language embodiment).
[2571] EXAMPLE: The following script lines execute a DGN command on a cell CCC provided by the user:
[2572] WAM:MSC 5
[2573] WAM:CELL 49
[2574] WAM:CCCVAR
[2575] WAM:CONNECT TI
[2576] WAM:SEND TI:dgn:cell 49, ccc CCCVAR
[2577] WAM:DISCONNECT TI
[2578] WAM:ENDTEST
SET
[2579] The SET command can be embedded in the integration construct data structure according to the invention.
[2580] PURPOSE: Instructs the WAM Interpreter to assign the value given to the WAMI global variable, global_variable, and enable an association if value references a WAMI VAR variable.
[2581] SYNTAX: WAM:SET global_variable value
[2582] EXAMPLE CALL: WAM:SET BBA 8
[2583] DESCRIPTION: The SET command is a multi-functional command. This command not only (in this embodiment of the WAMIL language) performs straightforward assignment, but also allows a user to disable, enable, or transfer a WAMI global variable association.
[2584] If the value provided is numerical or a string, a straightforward assignment is performed and if the WAMI global variable given is associated the association is disabled.
[2585] If the value provided references a WAMI VAR variable name, for example, WAM:SET BBA BBAVAR, then a WAMI association between the WAMI global variable BBA and the WAMI VAR variable BBAVAR is enabled. With the SET command, an association between any (in this WAMIL language embodiment) WAMI global variable and any (in this WAMIL language embodiment) WAMI VAR variable can be enabled. For script syntax, the global_variable will then be referenced as the WAMI VAR variable from that point forward.
[2586] If the value provided references a WAMI VARn List variable name, for example, WAM:SET BBA BBAVAR2, then a straightforward assignment is performed and if the WAMI global variable given is associated the association is disabled. Thus, the SET command can be used to assign any (in this WAMIL language embodiment) WAMI VARn List value to any (in this WAMIL language embodiment) WAMI global variable, but cannot be used to create an association between a WAMI global variable and a WAMI VARn List. To create such an association a user can (in this embodiment of the WAMIL language) execute a specific VARn command.
[2587] If the value provided references another WAMI global variable a straightforward assignment is performed. If the WAMI global variable referenced by value is associated, then its association is inherited by global_variable. Thus, both WAMI global variables will be associated to the same WAMI VAR variable. For script syntax then, both WAMI global variables will be referenced as the inherited WAMI VAR variable from that point forward.
[2588] The SET command can only (in this embodiment of the WAMIL language) be used to perform the same type assignment, or disable and enable associations between the same type WAMI global variable and WAMI VAR variable. In other words a string cannot be assigned to an integer type WAMI global variable, and a integer type WAMI global variable cannot be associated to a string type WAMI VAR variable. A string type WAMI global variable however can be assigned an integer, or be associated with either an integer or string type WAMI VAR variable.
[2589] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a SET command which enables an association between a WAMI global and WAMI VAR variable, in which BBAVAR has been previously set to a value of 4:
[2590] Set BBA to BBAVAR Value Of 4
[2591] The following is an example of the output generated to the WAMIL report file upon execution of a SET command in which the value given references a WAMI global variable which is not associated:
[2592] Set BBA to CCC Value Of 4
[2593] The following is an example of the output generated to the WAMIL report file upon execution of a SET command in which inheritance is performed between two WAMI global variables:
[2594] Set BBA to CCC Value Of 4 Per BBAVAR
[2595] The following is an example of the output generated to the WAMIL report file upon execution of a SET command in which a straightforward assignment is executed:
[2596] Set BBA to 4
[2597] ERRORS: If an invalid WAMI global variable name is provided as the argument global_variable, the WAM Interpreter will generate a syntax error.
[2598] If a type mismatch between a WAMI global and WAMI VAR variable is used, the WAM Interpreter will generate a syntax error.
[2599] If value references a WAMI VARn List variable name for a List which has not been declared, the WAM Interpreter will generate a syntax error.
[2600] ALTERS: WAMI global variable given and its association status.
[2601] DEFAULT VALUE: None (in this WAMIL language embodiment).
[2602] SEE ALSO: VARn type commands.
[2603] EXAMPLE: The following script will set up an association between the WAMI global CCC and CCU variables, ensuring that they are always equal:
[2604] WAM:MSC 5
[2605] WAM:CELL 49
[2606] WAM:CCCVAR
[2607] WAM:SET CCU CCC
[2608] WAM:CONNECT TI
[2609] TI:op:cell 49, ccc CCCVAR, ccu CCCVAR
[2610] WAM:DISCONNECT TI
[2611] WAM:ENDTEST
SETLISTVAR
[2612] The SETLISTVAR command can be embedded in the integration construct data structure according to the invention.
[2613] PURPOSE: The SETLISTVAR command instructs the WAM Interpreter to assign the values of varlist2 to varlist1.
[2614] SYNTAX: WAM:SETLISTVAR varlist1 varlist2
[2615] EXAMPLE CALL: WAM:SETLISTVAR WAMLIST CELLLIST
[2616] DESCRIPTION: The SETLISTVAR command instructs the WAM Interpreter to perform a straightforward assignment. If varlist1 or varlist2 are associated with any (in this WAMIL language embodiment) WAMI global variable the association is not changed.
[2617] Upon execution of this command, the values of varlist1 will be lost and replaced with the values of varlist2.
[2618] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a SETLISTVAR command:
[2619] Assign CELL List Values To WAMI List:
[2620] New WAMI List Values: 100 49 173
[2621] ERRORS: The WAMI VARn List, varlist1, can (in this embodiment of the WAMIL language) be of the same type as varlist2, or a syntax error will be generated. However, if varlist1 is of type string, then varlist2 can be of type integer.
[2622] The total number of values in varlist1 can (in this embodiment of the WAMIL language) be less than or equal to the total number of values in varlist2 or the WAM Interpreter will generate an error.
[2623] ALTERS: WAMI VARn List varlist1
[2624] DEFAULT VALUE: None (in this WAMIL language embodiment).
[2625] EXAMPLE: The following script executes a TI command for each MSC cell number:
[2626] WAM:MSC 5
[2627] WAM:CONNECT TI
[2628] TI:op:cell, generic
[2629] WAM:GETCELLS
[2630] WAM:SETLISTVAR WAMLIST CELLLIST
[2631] WAM:SET CELL CELLVAR
[2632] WAM:SET WAMI 1
[2633] WHILE:TEST_EXPR WAMI LTE WAMVAR
[2634] WAM:GETLISTVAR CELLVAR WAMLIST WAM
[2635] TI:op:cell X
[2636] WAM:INCR WAMI 1
[2637] ENDWHILE:
[2638] WAM:DISCONNECT TI
[2639] WAM:ENDTEST
SETVAR
[2640] The SETVAR command can be embedded in the integration construct data structure according to the invention.
[2641] PURPOSE: The SETVAR command instructs the WAM Interpreter to assign the value provided as an argument to the WAMI VAR variable, var_variable.
[2642] SYNTAX: WAM:SETVAR var_variable value
[2643] EXAMPLE CALL: WAM:SETVAR BBAVAR 4
[2644] DESCRIPTION: The SETVAR command performs a straightforward assignment of a value to a WAMI VAR variable. The value can be any (in this WAMIL language embodiment) numerical or alphanumerical string.
[2645] NOTE: SETVAR only (in this embodiment of the WAMIL language) acts upon WAMI VAR variables. For assignment to WAMI global variables use the SET command.
[2646] The SETVAR command can only (in this embodiment of the WAMIL language) be used to perform the same type assignment. In other words a string cannot be assigned to an integer type WAMI VAR variable. A string type WAMI VAR variable however can be assigned an integer.
[2647] If value references a WAMI global variable which is not associated, the current value of the WAMI global variable is automatically assigned to the given WAMI VAR variable as a straightforward assignment.
[2648] If value references a WAMI VAR variable which is not associated, the current value of the WAMI VAR variable referenced is automatically assigned to the given WAMI VAR variable, var_variable, as a straightforward assignment.
[2649] The SETVAR command can perform association transfers. It does not enable or disable associations. If value references a WAMI VAR variable, and the complementary WAMI global variable of var_variable is currently associated, then the existing association of the complementary WAMI global variable for var_variable is transferred to the WAMI VAR variable defined by value.
[2650] The above means that if var_variable is CCUVAR which is currently associated to CCU, and value references CCCVAR. Then upon execution of the following command:
[2651] WAM:SETVAR CCUVAR CCCVAR
[2652] The WAMI global variable CCU will be associated to CCCVAR, in effect transferring its association from CCUVAR to CCCVAR. Thus from that point forward for script syntax CCU will always reference CCCVAR. The only (in this embodiment of the WAMIL language) exception to this rule is the WAMI WAMVAR variable. Although a complementary global variable called WAMI does exist no automatic association transfer occurs in the execution of a SETVAR command, even if it is associated to any (in this WAMIL language embodiment) WAMI global variable. In effect, WAMVAR will always be referenced as WAMVAR, and any (in this WAMIL language embodiment) WAMI global variable associated to WAMVAR will also always be referenced as WAMVAR no matter what WAMVAR is set to. This allows increased flexibility within a script with the effect of WAMVAR acting like a wild card.
[2653] The SETVAR value argument can also reference a WAMI VARn List variable name. Thus allowing assignment of the value of any (in this WAMIL language embodiment) WAMI VARn List variable to a WAMI VAR variable. This is a simple straightforward assignment.
[2654] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a SETVAR command in which a straightforward assignment is performed from another WAMI VAR variable:
[2655] Set BBAVAR to CCCVAR Value Of 4
[2656] The following is an example of the output generated to the WAMIL report file upon execution of a SETVAR command in which value references a WAMI global variable which is not associated:
[2657] Set BBAVAR to BBA Value Of 4
[2658] The following is an example of the output generated to the WAMIL report file upon execution of a SETVAR command in which value references a WAMI global variable which has an association:
[2659] Set BBAVAR to BBA Value Of 4 Per CCCVAR
[2660] The following is an example of the output generated to the WAMIL report file upon execution of a SETVAR command in which a straightforward assignment is executed:
[2661] Set BBA to 4
[2662] ERRORS: None.
[2663] ALTERS: WAMI VAR variable given.
[2664] DEFAULT VALUE: None (in this WAMIL language embodiment).
[2665] SEE ALSO: WAM:DECRVAR var_variable value, WAM:INCRVAR var_variable value
[2666] EXAMPLE: The following script demonstrates an association transfer between two variables:
[2667] WAM:MSC 5
[2668] WAM:CELL 49
[2669] WAM:CCCVAR
[2670] WAM:SET CCU CCUVAR
[2671] WAM:CONNECT TI
[2672] TI:op:cell 49, ccc CCCVAR, ccu CCUVAR
[2673] WAM:SETVAR CCUVAR CCC
[2674] TI:op:cell 49, ccc CCCVAR, ccu CCCVAR
[2675] WAM:DISCONNECT TI
[2676] WAM:ENDTEST
SG
[2677] The SG command can be embedded in the integration construct data structure according to the invention.
[2678] PURPOSE: Changes the WAMI global server group number variable, SG, to the value provided as an argument.
[2679] SYNTAX: WAM:SG value
[2680] EXAMPLE CALL: WAM:SG 1
[2681] DESCRIPTION: The SG command sets the WAMI global server group 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 a server group number, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script server group number, will reference the new value.
[2682] 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.
[2683] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a SG command:
[2684] Set Server Group To 1
[2685] ERRORS: None.
[2686] ALTERS: SG
[2687] DEFAULT VALUE: SG is set to 0 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 0.
[2688] SEE ALSO: WAM:INITIALIZE
[2689] EXAMPLE: The following script lines set the WAMIL script SG variable to 1 and then backs up a fci translation form:
[2690] WAM:CELL 49
[2691] WAM:SG 1
[2692] WAM:ANT 1
[2693] WAM:GETAPX fci BACKUP
SPOOL
[2694] The SPOOL command can be embedded in the integration construct data structure according to the invention.
[2695] PURPOSE: Changes the WAM Interpreter spooler input pause to the time provided, in seconds.
[2696] SYNTAX: WAM:SPOOL seconds
[2697] EXAMPLE CALL: WAM:SPOOL 12
[2698] DESCRIPTION: The SPOOL command causes the WAM Interpreter input spooler courtesy pause to be changed to the argument provided, in seconds. The input spooler pause is the total amount of seconds the WAM Interpreter will wait for additional input, from all (in this embodiment of the WAMIL language) active interface sessions, prior to returning the contents of OutBuff (messages already received) to the script.
[2699] It is recommended that this value only (in this embodiment of the WAMIL language) be changed by WAMIL programmers which fully understand the WAM Interpreter interface process. Changes to this value have significant effects on the WAM Interpreter input, message and page captures, and script execution time.
[2700] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a SPOOL command:
[2701] Spool Pause Changed To 12 Seconds
[2702] ERRORS: If SPOOL is set to a value less than zero, unpredictable errors may result.
[2703] If SPOOL is set to zero, the WAM Interpreter will return immediately, and no input will be captured.
[2704] ALTERS: SPOOL
[2705] DEFAULT VALUE: SPOOL is set to 10 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 10.
SU
[2706] The SU command can be embedded in the integration construct data structure according to the invention.
[2707] PURPOSE: Changes the WAMI global setup radio number variable, SU, to the value provided as an argument.
[2708] SYNTAX: WAM:SU value
[2709] EXAMPLE CALL: WAM:SU 7
[2710] DESCRIPTION: The SU command sets the WAMI global setup radio 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 a setup radio number, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script setup radio number, will reference the new value.
[2711] 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.
[2712] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a SU command:
[2713] Set Cell Setup Radio To 1
[2714] ERRORS: None.
[2715] ALTERS: SU
[2716] DEFAULT VALUE: SU is set to 0 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 0.
[2717] SEE ALSO: WAM:INITIALIZE
[2718] EXAMPLE: The following script lines set the WAMIL script SU variable to 7 and then execute a TI command:
[2719] WAM:CELL 49
[2720] WAM:SU 7
[2721] TI:op:cell 49, su 7
SW
[2722] The SW command can be embedded in the integration construct data structure according to the invention.
[2723] PURPOSE: Changes the WAMI global switch identification number variable, SW, to the value provided as an argument.
[2724] SYNTAX: WAM:SW value
[2725] EXAMPLE CALL: WAM:SW 1
[2726] DESCRIPTION: The SW command sets the WAMI global switch identification 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 a switch identification number, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script switch identification number, will reference the new value.
[2727] 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.
[2728] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a SW command:
[2729] Set Switch Identification Number To 1
[2730] ERRORS: None.
[2731] ALTERS: SW
[2732] DEFAULT VALUE: SW is set to 0 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 0.
[2733] SEE ALSO: WAM:INITIALIZE
[2734] EXAMPLE: The following script lines set the WAMIL script SW variable to 5 and then backs up the pptm translation form:
[2735] WAM:CELL 49
[2736] WAM:SW 5
[2737] WAM:GETAPX pptm BACKUP
TIME
[2738] The TIME command can be embedded in the integration construct data structure according to the invention.
[2739] PURPOSE: Prints the current system time in the script WAMIL report file.
[2740] SYNTAX: WAM:TIME
[2741] EXAMPLE CALL: WAM:TIME
[2742] DESCRIPTION: The TIME command prints the current system time to the script WAMIL report file.
[2743] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a TIME command:
[2744] Time: 07:35:56
[2745] ERRORS: Any system errors generated during execution of the TIME command are printed to the script WAMIL report file.
[2746] ALTERS: None (in this WAMIL language embodiment)
[2747] DEFAULT VALUE: None (in this WAMIL language embodiment).
[2748] SEE ALSO: WAM:DATE
TIMEOUT
[2749] The TIMEOUT command can be embedded in the integration construct data structure according to the invention.
[2750] PURPOSE: Changes the WAM Interpreter overall time out variable, TimeOut, to the value provided as an argument.
[2751] SYNTAX: WAM:TIMEOUT seconds
[2752] EXAMPLE CALL: WAM:TIMEOUT 60
[2753] DESCRIPTION: The TIMEOUT command sets the WAM Interpreter overall time out 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 the TimeOut variable will reference the new value.
[2754] The WAM Interpreter TimeOut variable plays a major role during execution of a CONNECT command. Setting this variable too small will cause frequent time outs if system response is slow.
[2755] The TimeOut variable is referenced during input from any (in this WAMIL language embodiment) active interface session. If nothing at all is received within the time specified by the variable, the WAM Interpreter TFAIL flag will be set.
[2756] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a TIMEOUT command:
[2757] TimeOut Changed To: 60 Seconds
[2758] ERRORS: Setting TimeOut to a negative number or zero will cause unpredictable results.
[2759] ALTERS: TimeOut
[2760] DEFAULT VALUE: TimeOut is set to 30 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 30.
[2761] SEE ALSO: IF:TFAIL, WAM:INITIALIZE
TIMER
[2762] The TIMER command can be embedded in the integration construct data structure according to the invention.
[2763] PURPOSE: Instructs the WAM Interpreter to perform a specified internal timer action, and update the TIMER variable accordingly.
[2764] SYNTAX: WAM:TIMER action
[2765] EXAMPLE CALL: WAM:TIMER START
[2766] DESCRIPTION: The TIMER command instructs the WAM Interpreter to perform the action specified as an argument, an update the TIMER variable accordingly.
[2767] The WAMI timer is an internal timer which can be started, stopped, or read at any time during script execution. Below is a list of valid actions which can be used with the TIMER command:
| ACTION | DESCRIPTION | |
|---|---|---|
| START | Start TIMER. | |
| STOP | Stop TIMER. | |
| READ | Read current elapsed time. | |
[2768] Upon execution of a START action, the WAMI timer is enabled and the TIMER variable is set to 0. The TIMER variable remains set at 0 until the execution of a READ action.
[2769] Upon execution of a STOP action, the WAMI timer is disabled, the TIMER variable is then updated with the final elapsed time, in seconds.
[2770] Upon execution of a READ action, the TIMER variable is updated with the currently elapsed time, in seconds, since the execution of a START action.
[2771] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a WAM:TIMER START command:
[2772] Internal Timer Started at 11:20:38
[2773] The following is an example of the output generated to the WAMIL report file upon execution of a WAM:TIMER STOP command:
[2774] Internal Timer Stopped At 11:20:58
[2775] Elapsed Time is 20 Seconds.
[2776] The following is an example of the output generated to the WAMIL report file upon execution of a WAM:TIMER READ command:
[2777] Internal Timer Currently At 12 Seconds.
[2778] ERRORS: None.
[2779] ALTERS: Timer
[2780] DEFAULT VALUE: Timer is set to 0 upon initial startup, and is of type integer. The WAM:INITIALIZE command does not reset this variable.
[2781] EXAMPLE: The following script lines time how long it takes for a DGN command to complete:
[2782] WAM:SPOOL 2
[2783] WAM:TIMER START
[2784] TI:dgn:cell X, CCC CCCVAR
[2785] IF:OMSG DGN:CELL CELLVAR CCC CCCVAR, ATP
[2786] THEN:CONTINUE
[2787] ELSE:WAITQUERY 2 TI 30
[2788] WAM:TIMER STOP
[2789] WAM:PRINT Command Execution Took TIMERVAR Seconds.
TP
[2790] The TP command can be embedded in the integration construct data structure according to the invention.
[2791] PURPOSE: Changes the WAMI global traffic path number variable, TP, to the value provided as an argument.
[2792] SYNTAX: WAM:TP value
[2793] EXAMPLE CALL: WAM:TP 6
[2794] DESCRIPTION: The TP command sets the WAMI global traffic path 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 a traffic path number, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script traffic path number, will reference the new value.
[2795] 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.
[2796] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a TP command:
[2797] Set Traffic Path Number To 1
[2798] ERRORS: None.
[2799] ALTERS: TP
[2800] DEFAULT VALUE: TP is set to 0 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 0.
[2801] SEE ALSO: WAM:INITIALIZE
[2802] EXAMPLE: The following script lines set the WAMIL script TP variable to 6 and then execute a TI command:
[2803] WAM:CELL 49
[2804] WAM:TP 6
[2805] TI:exc:cell 49, ft tp 6
TRACE
[2806] The TRACE command can be embedded in the integration construct data structure according to the invention.
[2807] PURPOSE: Activates the WAM Interpreter TRACE feature specified by the TRACE options.
[2808] SYNTAX: WAM:TRACE options
[2809] EXAMPLE CALL: WAM:TRACE x
[2810] DESCRIPTION: The TRACE command instructs the WAM Interpreter to open a WAMI TRACE xterm window to which TRACE output will be written. The TRACE output written will be dependant upon the TRACE options specified by the argument options.
[2811] TRACE output will not be written to the WAMI TRACE xterm window until the TRACEON command is executed. The output to the WAMI TRACE xterm window will stop when either a TRACEOFF command is executed, or the WAMIL script has been terminated.
[2812] The TRACE command is a debug tool to monitor all (in this embodiment of the WAMIL language) WAM Interpreter activity during the execution of a WAMIL script. For a detailed definition of all (in this embodiment of the WAMIL language) the TRACE options available, and an explanation of the trace output and features, refer to the WAMI TRACE section of this book.
[2813] The TRACE command appends all (in this embodiment of the WAMIL language) TRACE output to the wam.tracelog file located in the WAMI HOME wam.trace sub-directory. If the file does not exist it is created upon execution of this command.
[2814] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a TRACE command:
[2815] TRACE OPTION: x
[2816] ERRORS: None.
[2817] ALTERS: TRACE options
[2818] DEFAULT VALUE: TRACE is set to NULL upon initial startup, and is of type string. The WAM:INITIALIZE command resets TRACE.
[2819] SEE ALSO: WAM:TRACEOFF, WAM:TRACEON
TRACEOFF
[2820] The TRACEOFF command can be embedded in the integration construct data structure according to the invention.
[2821] PURPOSE: Stops output to the WAMI TRACE xterm window.
[2822] SYNTAX: WAM:TRACEOFF
[2823] EXAMPLE CALL: WAM:TRACEOFF
[2824] DESCRIPTION: The TRACEOFF command instructs the WAM Interpreter to stop output to the WAMI TRACE xterm window. The WAMI TRACE xterm window still remains open after execution of this command.
[2825] The TRACE command is a debug tool to monitor all (in this embodiment of the WAMIL language) WAM Interpreter activity during the execution of a WAMIL script. For a detailed definition of TRACE, refer to the WAMI TRACE section of this book.
[2826] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a TRACEOFF command:
[2827] TRACE OFF:
[2828] ERRORS: None.
[2829] ALTERS: TRACE flag
[2830] DEFAULT VALUE: The TRACE flag is set OFF upon initial startup. The WAM:INITIALIZE command resets this flag.
[2831] SEE ALSO: WAM:TRACE, WAM:TRACEON
TRACEON
[2832] The TRACEON command can be embedded in the integration construct data structure according to the invention.
[2833] PURPOSE: Starts output to the WAMI TRACE xterm window.
[2834] SYNTAX: WAM:TRACEON
[2835] EXAMPLE CALL: WAM:TRACEON
[2836] DESCRIPTION: The TRACEON command instructs the WAM Interpreter to start output to the WAMI TRACE xterm window.
[2837] The TRACE command is a debug tool to monitor all (in this embodiment of the WAMIL language) WAM Interpreter activity during the execution of a WAMIL script. For a detailed definition of TRACE, refer to the WAMI TRACE section of this book.
[2838] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a TRACEON command:
[2839] TRACE ON:
[2840] ERRORS: None.
[2841] ALTERS: TRACE flag
[2842] DEFAULT VALUE: The TRACE flag is set OFF upon initial startup. The WAM:INITIALIZE command resets this flag.
[2843] SEE ALSO: WAM:TRACE, WAM:TRACEOFF
TRKGRP
[2844] The TRKGRP command can be embedded in the integration construct data structure according to the invention.
[2845] PURPOSE: Changes the WAMI global trunk group number variable, TRKGRP, to the value provided as an argument.
[2846] SYNTAX: WAM:TRKGRP value
[2847] EXAMPLE CALL: WAM:TRKGRP 254
[2848] DESCRIPTION: The TRKGRP command sets the WAMI global trunk group 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 a trunk group number, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script trunk group number, will reference the new value.
[2849] 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.
[2850] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a TRKGRP command:
[2851] Set Trunk Group Number To 1
[2852] ERRORS: None.
[2853] ALTERS: TRKGRP
[2854] DEFAULT VALUE: TRKGRP is set to 0 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 0.
[2855] SEE ALSO: WAM:INITIALIZE
[2856] EXAMPLE: The following script lines set the WAMIL script TRKGRP variable to 538 and then execute a TI command:
[2857] WAM:CELL 49
[2858] WAM:DCS 1
[2859] WAM:TRKGRP 538
[2860] WAM:TRKMBR 38
[2861] TI:dgn:dcs 1, trkgrp 538, member 38
TRKMBR
[2862] The TRKMBR command can be embedded in the integration construct data structure according to the invention.
[2863] PURPOSE: Changes the WAMI global trunk member number variable, TRKMBR, to the value provided as an argument.
[2864] SYNTAX: WAM:TRKMBR value
[2865] EXAMPLE CALL: WAM:TRKMBR 190
[2866] DESCRIPTION: The TRKMBR command sets the WAMI global trunk member 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 a trunk member number, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script trunk member number, will reference the new value.
[2867] 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.
[2868] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a TRKMBR command:
[2869] Set Trunk Member Number To 1
[2870] ERRORS: None.
[2871] ALTERS: TRKMBR
[2872] DEFAULT VALUE: TRKMBR is set to 0 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 0.
[2873] SEE ALSO: WAM:INITIALIZE
[2874] EXAMPLE: The following script lines set the WAMIL script TRKMBR variable to 38 and then execute a TI command:
[2875] WAM:CELL 49
[2876] WAM:DCS 1
[2877] WAM:TRKGRP 538
[2878] WAM:TRKMBR 38
[2879] TI:dgn:dcs 1, trkgrp 538, member 38
UNIX
[2880] The UNIX command can be embedded in the integration construct data structure according to the invention.
[2881] PURPOSE: Instructs the WAM Interpreter to execute the command provided as a UNIX executable program.
[2882] SYNTAX: WAM:UNIX command
[2883] EXAMPLE CALL: WAM:UNIX 1s
[2884] DESCRIPTION: The UNIX command instructs the WAM Interpreter to execute the command given as an argument as a UNIX shell executable. The command can be any (in this WAMIL language embodiment) UNIX command or executable program.
[2885] This command allows a user to initiate a UNIX process from within a WAMIL script. Upon completion of execution of this command, the WAM Interpreter will set the WAMI VAR variable, WAMVAR, to the output, if any, of the command executed and also print the output to the script WAMIL report file.
[2886] Upon execution of the UNIX command, the WAMIL script will not continue execution until after the command given has completed. If the command given is executed in the background, then the UNIX command will return immediately and WAMVAR will hold the PID value returned by Unix.
[2887] The command argument can also include references to WAMI global variables, or WAMI VARn variables. To reference a WAMI global variable the suffix VAR is simply added to the WAMI global variable name. This is not to be mistaken with WAMI VAR variables. Although when referencing WAMI global variables within strings the names resemble WAMI VAR variables, this naming convention was chosen to allow references to WAMI global variables and still be able to print the variable name. To include the value of a WAMI VAR variable, a WAMI global variable can (in this embodiment of the WAMIL language) first be associated. Then references to the WAMI global variable will yield the value of the WAMI VAR variable it is associated with.
[2888] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a UNIX command:
[2889] Executed UNIX Command: 1s
[2890] ERRORS: Any errors generated by Unix upon execution are printed in the script WAMIL report file.
[2891] ALTERS: WAMVAR
[2892] DEFAULT VALUE: WAMVAR is set to NULL upon initial startup, and is of type string. The WAM:INITIALIZE command also sets this variable to NULL.
[2893] SEE ALSO: IF:WAMVAR
VRADPC
[2894] The VRADPC command can be embedded in the integration construct data structure according to the invention.
[2895] PURPOSE: Changes the WAMI global voice radio power control option number variable, VRADPC, to the value provided as an argument.
[2896] SYNTAX: WAM:VRADPC value
[2897] EXAMPLE CALL: WAM:VRADPC 150
[2898] DESCRIPTION: The VRADPC command sets the WAMI global voice radio power control option 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 a voice radio power control option number, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script voice radio power control option number, will reference the new value.
[2899] 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.
[2900] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a VRADPC command:
[2901] Set Voice Radio Power Control Option To 150
[2902] ERRORS: None.
[2903] ALTERS: VRADPC
[2904] DEFAULT VALUE: VRADPC is set to 0 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 0.
[2905] SEE ALSO: WAM:INITIALIZE
VRN
[2906] The VRN command can be embedded in the integration construct data structure according to the invention.
[2907] PURPOSE: Changes the WAMI global voice radio number variable, VRN, to the value provided as an argument.
[2908] SYNTAX: WAM:VRN value
[2909] EXAMPLE CALL: WAM:VRN 1
[2910] DESCRIPTION: The VRN command sets the WAMI global voice radio 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 a voice radio number, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script voice radio number, will reference the new value.
[2911] 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.
[2912] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a VRN command:
[2913] Set Voice Radio Number To 1
[2914] ERRORS: None.
[2915] ALTERS: VRN
[2916] DEFAULT VALUE: VRN is set to 0 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 0.
[2917] SEE ALSO: WAM:INITIALIZE
[2918] EXAMPLE: The following script lines set the WAMIL script VRN variable to 1 and then backs up the dcch translation form:
[2919] WAM:CELL 49
[2920] WAM:VRN 1
[2921] WAM:GETAPX dcch BACKUP
WAIT
[2922] The WAIT command can be embedded in the integration construct data structure according to the invention.
[2923] PURPOSE: Instructs the WAM Interpreter to wait a specified number of seconds before execution of the next WAMIL script command.
[2924] SYNTAX: WAM:WAIT seconds
[2925] EXAMPLE CALL: WAM:WAIT 10
[2926] DESCRIPTION: The WAIT command instructs the WAM Interpreter to wait a specified number of seconds before executing the next WAMIL script command.
[2927] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a WAIT command:
[2928] WAMIL Wait: 10 Seconds
[2929] ERRORS: Setting WAIT to a negative number or zero will have no effect.
[2930] ALTERS: Wait
[2931] DEFAULT VALUE: Wait is set to 10 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 10.
[2932] SEE ALSO: WAM:INITIALIZE
[2933] EXAMPLE: The following script lines execute a TI command, and then waits seconds before executing a subsequent TI command:
[2934] WAM:CELL 49
[2935] WAM:CAT 1
[2936] TI:rst:cell 49, cat 1
[2937] WAM:WAIT 20
[2938] TI:op:cell 49
[2939] The WAM command can be embedded in the integration construct data structure according to the invention.
[2940] PURPOSE: Changes the Interpreter global variable WAMI value, WAM, to the value provided as an argument.
[2941] SYNTAX: WAM:WAMI string
[2942] EXAMPLE CALL: WAM:WAMI 101
[2943] DESCRIPTION: The WAMI command sets the Interpreter global variable WAMI value 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 Interpreter global variable WAMI value, and all (in this embodiment of the WAMIL language) IF-construct commands which test the Interpreter global variable WAMI value, will reference the new value.
[2944] Execution of this command disables any (in this WAMIL language embodiment) association which exists between this WAMI global variable and any WAMI VAR variable.
[2945] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a WAMI command:
[2946] Set WAMI Variable 101
[2947] ERRORS: None.
[2948] ALTERS: WAM
[2949] DEFAULT VALUE: WAMI is set to 0 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 0.
[2950] SEE ALSO: WAM:INITIALIZE
[2951] EXAMPLE: The following script adds a neighbor to cell 49:
[2952] WAM:MSC 5
[2953] WAM:CELL 49
[2954] WAM:ANT 1
[2955] WAM:SG 0
[2956] WAM:WAMI 101
[2957] WAM:PUTAPXFLD fci cdmanbr_list1.ncs_c[1]=WAMVAR
[2958] WAM:ENDTEST
WAMLIST
[2959] The WAMLIST command can be embedded in the integration construct data structure according to the invention.
[2960] PURPOSE: Declares to the WAM Interpreter that a list of values will be supplied to the script.
[2961] SYNTAX: WAM:WAMLIST string
[2962] EXAMPLE CALL: WAM:WAMLIST Enter Three Cell Numbers To Test
[2963] DESCRIPTION: The WAMLIST command is a WAMIL declaration command which instructs the WAM Interpreter that a list of values will be supplied to the script. This command executes the assignment of the values provided to the WAM Interpreter WAMI List.
[2964] Upon detection of this command, the WAM Interpreter will search the command line arguments for the WAMI values. The WAMI List size will depend on the total number of values supplied to the script. Thus the WAMI List can be infinitely long. The WAMI values within the WAMI List can then be referenced within the script as WAMI VARn variables, according to their index position in the list. For example, WAMVAR2 refers to the second WAMI value in the WAMI List. The order of the WAMI values provided determine the order of their placement within the WAMI List.
[2965] If a WAMI VARn value outside the range of the WAMI List is referenced within the script, the value returned will be a WAMBLANK. This provides a means of determining when the end of the WAMI List has been reached.
[2966] If WAMIL scripts which include WAMLIST commands are included in a Linker script, and one set of variables is chosen for all (in this embodiment of the WAMIL language) the linked scripts, the first WAMLIST command detected by the Linker takes precedence over all (in this embodiment of the WAMIL language) or any subsequent WAMLIST commands in the remaining linked WAMIL scripts.
[2967] 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.
[2968] WAMI GUI PLATFORM: Prior to execution of a WAMIL script, the WAMI GUI platform searches the script for special commands. If a WAMLIST command is encountered the WAMI GUI platform will prompt the user for a quantity of WAMI values. The prompt displayed will be the string argument of the WAMLIST command within the script. Subsequent WAM:WAMLIST commands encountered will not cause additional prompting.
[2969] SCRIPTOR: If this command is deleted from the current script, the Scriptor will issue a warning that any (in this WAMIL language embodiment) remaining WAMI List variables referenced within the script will each default to a WAMBLANK value.
[2970] The Scriptor will only (in this embodiment of the WAMIL language) allow insertion of one WAMLIST command into the current script.
[2971] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a WAMLIST command:
[2972] Total Number of WAMI List Values Set To 4
[2973] WAMI List Values: 2 4 6 8
[2974] ERRORS: Any references within a script to a WAMI VARn variable prior to the declaration of the list will generate a WAMBLANK.
[2975] If more than one WAMLIST 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 WAMLIST commands have no effect.
[2976] ALTERS: WAMI List.
[2977] DEFAULT VALUE: The WAMI List is set to an unknown state upon initial startup, and is of type string. The WAM:INITIALIZE command does not reset this list.
[2978] SEE ALSO: WAM:WAMVARn
[2979] EXAMPLE: The following script executes a TI command for each cell number passed as a WAMI List:
| WAM:MSC 5 | |
| WAM:WAMLIST Enter Cell Numbers | |
| WAM:CONNECT TI | |
| WAM:SET WAMI 1 | |
| WHILE:TEST_EXPR WAMVAR NE WAMBLANK |
WAMVAR
[2980] The WAMVAR command can be embedded in the integration construct data structure according to the invention.
[2981] PURPOSE: Declares to the WAM Interpreter, that a value or string for the WAMI VAR variable WAMVAR will be supplied to the script.
[2982] SYNTAX: WAM:WAMVAR prompt_string
[2983] EXAMPLE CALL: WAM:WAMVAR Enter Neighbor Cell Number
[2984] DESCRIPTION: The WAMVAR 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 or string to assign to the WAMI VAR variable WAMVAR.
[2985] Like standard WAMI VAR variable declaration commands, the execution of this command also enables an association with the global variable WAM. Therefore, until the global variable WAMI association is transferred to another WAMI VAR variable, or disabled, all (in this embodiment of the WAMIL language) references to the global variable WAMI will use the WAMVAR variable value.
[2986] For script syntax, until an actual WAMI value is passed as an argument, when a WAMVAR command is used the WAMI value within a script shall be referenced as WAMVAR from that point forward.
[2987] 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_sting use refer to the WAMI GUI PLATFORM section below.
[2988] WAMI GUI PLATFORM: Prior to execution of a WAMIL script, the WAMI GUI platform searches the script for special commands. If a WAM:WAMVAR is encountered the WAMI GUI platform will prompt the user using prompt_string for the script WAMVAR value or string. Subsequent WAM:WAMVAR commands encountered will not cause additional prompting.
[2989] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution an WAMVAR command:
[2990] Set WAMVAR To Argument Value of 173
[2991] ERRORS: The prompt string argument, although not used by the WAM Interpreter, will generate a syntax error if omitted.
[2992] If no command line value or string has been provided, the WAM Interpreter will generate an error and script execution will be aborted.
[2993] ALTERS: WAMVAR
[2994] DEFAULT VALUE: WAMVAR is set to an unknown state upon initial startup, and is of type string. The WAM:INITIALIZE command does not reset this WAMI VAR variable.
[2995] SEE ALSO: WAM:WAMI string
[2996] EXAMPLE: The following script adds a neighbor to cell 49:
[2997] WAM:MSC 5
[2998] WAM:CELL 49
[2999] WAM:ANT 1
[3000] WAM:SG 0
[3001] WAM:WAMVAR Enter Neighbor Cell Number
[3002] WAM:PUTAPXFLD fci cdmanbr_list1.ncs_c[1]=WAMVAR
[3003] WAM:ENDTEST
WAMVARn
[3004] The WAMVARn command can be embedded in the integration construct data structure according to the invention.
[3005] PURPOSE: Instructs the WAM Interpreter to set the global variable WAMI to the value of the referenced WAMI VARn WAMI variable, in position n, of the WAMI List passed as an argument.
[3006] SYNTAX: WAM:WAMVARn
[3007] EXAMPLE CALL: WAM:WAMVAR2
[3008] DESCRIPTION: The WAMVARn command is an assignment command. This command can only (in this embodiment of the WAMIL language) be executed if a WAMI List has been declared in the script. Upon execution, this command assigns a WAMI List variable value to the global variable WAM.
[3009] The value n, can (in this embodiment of the WAMIL language) be a valid index into the WAMI List. Any (in this WAMIL language embodiment) WAMI List value can be assigned to the global variable WAMI by execution of this command, where n is the WAMI value location within the WAMI List. Upon execution, the WAMI global value within a script is referenced as WAMVARn from that point forward Like standard WAMI VARn variable assignment commands, the execution of this command also enables an association with the global variable WAM. Therefore, until the global variable WAMI association is transferred to a WAMI VAR variable, or disabled, all (in this embodiment of the WAMIL language) references to the global variable WAMI will use the WAMVARn variable value.
[3010] For script syntax, until actual WAMI List values are passed as an argument, when a WAMVARn command is used the WAMI global value within a script shall be referenced as WAMVARn from that point forward.
[3011] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a WAMVARn command, when a WAMI List of 3 was previously declared, and the WAMI List values passed as an argument are 2 4 6:
[3012] Set WAMI To WAMVAR2 Value Of 4
[3013] SCRIPTOR: If a WAMVARn command is deleted from the current script, the Scriptor will prompt the user for a WAMI global value and then insert a WAM:WAMI string command in place of the WAMVARn command deleted.
[3014] ERRORS: An invalid WAMVARn command used within a script, where n refers to a WAMI List index outside the list range, will default to assignment of WAMBLANK to the global variable WAM.
[3015] If a WAMVARn command is used within a script in which no WAMI List has been declared, a WAMBLANK will be assigned to the global variable WAM.
[3016] ALTERS: WAM
[3017] DEFAULT VALUE: None (in this WAMIL language embodiment).
[3018] SEE ALSO: WAM:WAMI string, WAM:WAMLIST string
[3019] EXAMPLE: The following script sets the WAMI VARn WAMI List length to 2, and then modifies the CEQFACE form t_add and t_drop values:
[3020] WAM:MSC 5
[3021] WAM:CELL 49
[3022] WAM:WAMLIST Enter t_add and t_drop values
[3023] WAM:WAMVAR1
[3024] WAM:PUTS HOME TEMP.dbf t_add=WAMVAR
[3025] WAM:WAMVAR2
[3026] WAM:PUTS HOME TEMP.dbf t_add=WAMVAR
[3027] WAM:PUTAPX ceqface TEMP
[3028] WAM:UNIX rm TEMP.dbf
[3029] WAM:ENDTEST
WMMI
[3030] The WMMI command can be embedded in the integration construct data structure according to the invention.
[3031] PURPOSE: Instructs the WAM Interpreter to generate paging messages to specified mobile units at a specified rate.
[3032] SYNTAX: WAM:WMMI start stop rate mobiles message
[3033] EXAMPLE CALL: WAM:WMMI 11:00:00:11:17:1998 12:00:001:17:1998360/home/mobiles Call Me Back
[3034] DESCRIPTION: The WMMI command instructs the WAM Interpreter to generate paging messages, via SMS (Short Messaging Service), at a specified rate per hour to a list of mobiles. The message sent is given in the argument message.
[3035] The list of mobiles is supplied in a text file which contains a list of mobile unit numbers, one mobile unit number per line. The filename and full pathname to the file is supplied in the argument mobiles.
[3036] The start and stop arguments define the actual start time of when the messages will begin, and the stop time for the last message. The start and end time formats are specified as follows:
[3037] HH:mm:SS:MM:DD:YYYY
[3038] Where, HH is the two digit hour, mm is the two digit minute, SS is the two digit seconds, MM is the two digit month, DD is the two digit day, and YYYY is the four digit year.
[3039] For example, if the user defines the following paging pattern:
[3040] “Call Me Back”
[3041] And a paging rate of 360 pages per hour. If the text file which contains a list of mobile unit numbers has a total of ten numbers, then the paging pattern “Call Me Back 1” will be sent to the first mobile number in the text file list, and “Call Me Back 2” will be sent to the second mobile number in the text file list, and so on every ten seconds until “Call Me Back 10” is transmitted to the tenth mobile number in the list. Once the tenth pattern has been sent, the process will wrap around to the first mobile and send “Call me Back 11” to that mobile unit.
[3042] Only (in this embodiment of the WAMIL language) one paging project can be active at one time within a WAMIL script.
[3043] This process will continue, in this wrap around fashion, until the specified end time is reached, or the process is terminated with the WMMI_STOP command.
[3044] The message argument can include references to WAMI global variables, or WAMI VARn variables, and WAM Interpreter keywords. To reference a WAMI global variable the suffix VAR is simply added to the WAMI global variable name. For example, the following message, Test SCRIPT_NAME Message MSC MSCVAR, will be interpreted and sent as follows for a script called jt1234, executed using MSC 5:
[3045] Test jt1234 Message MSC 5
[3046] This is not to be mistaken with WAMI VAR variables. Although when referencing WAMI global variables within strings to be printed the names resemble WAMI VAR variables, this naming convention was chosen to allow references to WAMI global variables and still be able to use the variable name. To use the value of a WAMI VAR variable, a WAMI global variable can (in this embodiment of the WAMIL language) first be associated. Then references to the WAMI global variable will yield the value of the WAMI VAR variable it is associated with.
[3047] The start, stop, and rate arguments can reference any (in this WAMIL language embodiment) WAMI VAR or WAMI VARn variable. Upon execution of the command, the argument value is replaced with the current value of the WAMI VAR or WAMI VARn variable referenced.
[3048] If the start argument is set to the value of 0, then the messaging project start time will be set to the current time.
[3049] If the end argument is set to the keyword TESTEND, then the messaging project will be terminated upon the execution of any (in this WAMIL language embodiment) WAM:ENDTEST command. Regardless of whether the TESTEND keyword is used, or the WMMI_STOP command is executed, the WAM Interpreter will always terminate the active WMMI project upon completion of a execution of the WAMIL script.
[3050] If the mobiles argument is the keyword HOME, then the WAM Interpreter will look in the WMMI home directory, wam.wmmi, for the MOBS.wmmi file.
[3051] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a WMMI command:
[3052] Start Mobile Messaging at 360 pages per hour.
[3053] Send Pattern: Call Me Back
[3054] ERRORS: If the mobile units file specified is not found the WAM Interpreter will generate an execution error.
[3055] If an invalid start or end time, or rate, is specified the WAM Interpreter will generate an execution error.
[3056] If the message length is greater than 150 characters, the WAM Interpreter will generate an execution error.
[3057] If no message is specified, the WAM Interpreter will generate a syntax error.
[3058] If a WMMI project is already active, the WAM Interpreter will generate a syntax error.
[3059] ALTERS: None (in this WAMIL language embodiment).
[3060] DEFAULT VALUE: None (in this WAMIL language embodiment).
[3061] SEE ALSO: WAM:WMMI_GET wmmi_parameter var_variable, WAM:WMMI_SEND wmmi_command argument
[3062] WAM:WMMI STOP
[3063] EXAMPLE: The following script lines initiate mobile messages for one hour: WAM:WMMI 11:00:00:11:17:1998 12:00:001:17:1998 360/home/mobiles Call Me Back
WMMI GET
[3064] The WMMI_GET command can be embedded in the integration construct data structure according to the invention.
[3065] PURPOSE: Instructs the WAM Interpreter to get the WMMI project parameter value, defined by the argument wmmi_parameter, and place the value in the WAMI VAR variable, var_variable.
[3066] SYNTAX: WAM:WMMI_GET wmmi_parameter var_variable
[3067] EXAMPLE CALL: WAM:WMMI_GET COUNT WAMVAR
[3068] DESCRIPTION: The WMMI_GET command provides a means of retrieving parameter values from the active WMMI project. Upon execution of this command, the WAMI VAR variable given by the argument var_variable, is set to the WMMI project parameter value.
[3069] The WMMI parameter, COUNT, can be retrieved by the WMMI_GET command: The parameter COUNT represents the value returned by the current message number transmitted by the active WMMI project. Note: all (in this embodiment of the WAMIL language) WMMI messages are numbered sequentially starting with the number one for the first message.
[3070] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a WMMI_GET command to retrieve the COUNT parameter value:
[3071] WMMI Project COUNT Currently At: 16
[3072] ERRORS: If the WAMI VAR variable name given is invalid, the WAM Interpreter will generate a syntax error.
[3073] If no WMMI project is active, the WAM Interpreter will generate a syntax error.
[3074] If an invalid WMMI parameter name is given, the WAM Interpreter will generate a syntax error.
[3075] If no parameter value is retrieved from the WMMI project within the time specified by the WAMI global variable TimeOut, the WAM Interpreter will generate an error message to the WAMIL report file. The WAMIL script execution, however, will continue.
[3076] ALTERS: WAMI VAR variable given.
[3077] DEFAULT VALUE: None (in this WAMIL language embodiment).
[3078] SEE ALSO: WAM:WMMI start stop rate mobiles message, WAM:WMMI_SEND wmmi_command argument
[3079] WAM:WMMI_STOP
[3080] EXAMPLE: The following script lines initiate mobile messages, and then after one minute prints the total number of messages sent:
[3081] WAM:WMMI 0 TESTEND 3600 HOME Call Me Back
[3082] WAM:WAIT 60
[3083] WAM:WMMI_GET COUNT WAMVAR
[3084] WAM:PRINT A total of WAMVAR messages have been sent.
[3085] WAM:ENDTEST
WMMI_SEND
[3086] The WMMI_SEND command can be embedded in the integration construct data structure according to the invention.
[3087] PURPOSE: Instructs the WAM Interpreter to send the specified WMMI command to the active WMMI project.
[3088] SYNTAX: WAM:WMMI_SEND wmmi_command value
[3089] EXAMPLE CALL: WAM:WMMI_SEND CHANGERATE 1200
[3090] DESCRIPTION: The WMMI_SEND command causes the WAM Interpreter to send the specified WMMI command, given by the argument wmmi_command, to the active WMMI project. The given value is the WMMI command argument.
[3091] The following is a list of WMMI commands which can be sent to an active project, along with a description and purpose of the command:
| COMMAND | DESCRIPTION | |
|---|---|---|
| CHANGEPAT | Causes the WMMI proj ect to | |
| change the pattern to the value | ||
| provided. | ||
| CHANGERATE | Causes the WMMI project to | |
| change the rate to the value | ||
| provided | ||
| SENDPAT | Causes the WMMI project to | |
| transmit the pattern provided by | ||
| value only (in this embodiment | ||
| of the WAMIL language) once, | ||
| and then return to the project | ||
| pattern. The project pattern | ||
| provided in the WMMI | ||
| command is not altered. | ||
[3092] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a WMMI_SEND command:
[3093] Send CHANGERATE Command To WMMI Project:
[3094] Argument: 1200
[3095] ERRORS: If the WMMI command is CHANGEPAT or SENDPAT, and the message length is greater than 150 characters, the WAM Interpreter will generate a syntax error.
[3096] If no WMMI project is active at the time of execution of this command, the WAM Interpreter will generate a syntax error.
[3097] If an invalid WMMI command is supplied, the WAM Interpreter will generate a syntax error.
[3098] If the WMMI command is CHANGERATE, and the value given is invalid, the WAM Interpreter will generate a syntax error.
[3099] ALTERS: WMMI project depending on command.
[3100] DEFAULT VALUE: None (in this WAMIL language embodiment).
[3101] SEE ALSO: WAM:WMMI start stop rate mobiles message, WAM:WMMI_GET wmmi_parameter var_variable, WAM:WMMI_STOP
[3102] EXAMPLE: The following script lines initiate mobile messages, and after execution of a sub-WAMIL script changes the paging rate:
[3103] WAM:WMMI 0 TESTEND 360 HOME Call Me Back
[3104] WAM:EXEC HOME jt1234
[3105] WAM:WMMI_SEND CHANGERATE 1200
WMMI_STOP
[3106] The WMMI_STOP command can be embedded in the integration construct data structure according to the invention.
[3107] PURPOSE: Instructs the WAM Interpreter to terminate the active WMMI paging project.
[3108] SYNTAX: WAM:WMMI_STOP
[3109] EXAMPLE CALL: WAM:WMMI_STOP
[3110] DESCRIPTION: The WMMI_STOP command upon execution terminates the script WMMI paging project. If the project is not active then the execution of this command has no effect.
[3111] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a WMMI_STOP command:
[3112] Mobile Messaging Project Terminated.
[3113] ERRORS: None.
[3114] ALTERS: None (in this WAMIL language embodiment).
[3115] DEFAULT VALUE: None (in this WAMIL language embodiment).
[3116] SEE ALSO: WAM:WMMI start stop rate mobiles message, WAM:WMMI_GET wmmi_parameter var_variable, WAM:WMMI_SEND wmmi_command argument
XMITC
[3117] The XMITC command can be embedded in the integration construct data structure according to the invention.
[3118] PURPOSE: Changes the WAMI global transmitter control action option number variable, XMITC, to the value provided as an argument.
[3119] SYNTAX: WAM:XMITC value
[3120] EXAMPLE CALL: WAM:XMITC 150
[3121] DESCRIPTION: The XMITC command sets the WAMI global transmitter control action option 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 a transmitter control action option number, and all (in this embodiment of the WAMIL language) IF-construct commands which test the current script transmitter control action option number, will reference the new value.
[3122] 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.
[3123] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a XMITC command:
[3124] Set Transmitter Control Action Option To 150
[3125] ERRORS: None.
[3126] ALTERS: XMITC
[3127] DEFAULT VALUE: XMITC is set to 0 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 0.
[3128] SEE ALSO: WAM:INITIALIZE
IF-Constructs
[3129] If-constructs are interwoven with the integration construct data structure according to the invention, i.e., WAM interface commands, to form a WAMIL script.
[3130] A table listing of the names of WAM Interpreter IF-Construct elements follows immediately. Then, a general discussion of the less robust IF THEN ELSE type of IF-construct is presented, then a general discussion of the more robust IF THENDO ELSEDO ENDIF type of IF-construct is presented. After that, a detailed glossary of IF-construct elements is provided.
| IF:ACTIVITY | IF:SDPVAR_STATE | |
| IF:AFAIL | IF:SDPVAR_VALUE | |
| IF:APXVAR | IF:TEST_EXPR | |
| IF:CFAIL | IF:TFAIL | |
| IF:COMPLETED | IF:WAMVAR | |
| IF:GENERIC | THEN/ELSE:CONTINUE | |
| IF:LASTTEST | THEN/ELSE:ENDTEST | |
| IF:LFAIL | THEN/ELSE:PRINT | |
| IF:OMSG | THEN/ELSE:TIMEOUT | |
| IF:SDPAIL | THEN/ELSE:WAIT | |
| IF:SDPPORT | THEN/ELSE:WAITQUERY | |
| IF:SDPVAR_COLOR | ||
IF THEN ELSE Type Of IF-Construct
[3131] This section describes the WAMIL scripting language IF-construct test expressions, and complementary THEN and ELSE commands. They can be used in a IF THEN ELSE construct or an IF THENDO ELSEDO ENDIF construct to test the results of a WAMIL interface command executed, and toperform certain actions based upon the results of the IF test expression.
[3132] All WAMIL IF THEN ELSE constructs 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 commands can exist within an IF THEN ELSE construct. For example the following is valid:
[3133] IF:OMSG COMPLETED
[3134] THEN:PRINT Command completed
[3135] THEN: CONTINUE
[3136] ELSE:PRINT Wait up to 100 seconds for command to complete
[3137] ELSE:WAITQUERY 10 TI 10
[3138] The IF THEN ELSE construct is an older type of IF-construct and is still supported for backwards compatibility. The WAMIL IF THENDO ELSEDO ENDIF scripting language constructs are more robust and can be nested, but cannot be inter-mixed with an IF THEN ELSE construct.
[3139] The WAM Interpreter will not accept incomplete IF THEN ELSE constructs. any (in this WAMIL language embodiment) incomplete IF THEN ELSE construct will generate a syntax error from the WAM Interpreter. The Scriptor will not load or save a script containing any (in this WAMIL language embodiment) incomplete IF THEN ELSE constructs.
IF THENDO ELSEDO ENDIF Type of IF-Construct
[3140] This section describes the WAMIL IF THENDO ELSEDO ENDIF type of IF-construct which can be used with any (in this WAMIL language embodiment) IF-construct commands to execute a group of commands based upon the results of the IF test expression.
[3141] A WAMIL IF THENDO ELSEDO ENDIF construct is structured as follows:
[3142] IF:GENERIC a34y12.0t
[3143] THENDO:
[3144] WAM:PRINT The generic for the cell is valid.
[3145] IF:ACTIVITY NO
[3146] THEN:PRINT No activity on current cell.
[3147] ELSE:ENDTEST
[3148] ELSEDO:
[3149] WAM:PRINT Generic on cell is incorrect.
[3150] WAM:ENDTEST
[3151] ENDIF:
[3152] All the commands between the THENDO and ELSEDO constructs are executed if the result of the IF command execution is TRUE, and all the commands between the ELSEDO and EN-DIF are executed if the result of the IF command execution is FALSE
[3153] 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. The WAM Interpreter will not accept incomplete constructs. Any (in this WAMIL language embodiment) incomplete construct will generate a syntax error from the WAM Interpreter. The Scriptor will not load or save a script containing any (in this WAMIL language embodiment) incomplete IF THENDO ELSEDO ENDIF constructs.
[3154] 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 Type of IF-Construct
[3155] This section describes the WAMIL WHILE ENDWHILE variation of an IF-construct which can be used to continuously loop through the execution of a group of commands until the WHILE test expression condition evaluates FALSE.
[3156] A WAMIL WHILE ENDWHILE construct is structured as follows:
[3157] WHILE:TEST_EXPR CELLVAR LT 223
[3158] TI:op:cell CELLVAR
[3159] WAM:INCRVAR CELLVAR 1
[3160] ENDWHILE:
[3161] All WAMILWHILE ENDWHILE constructs can (in this embodiment of the WAMIL language) be complete and include a WHILE and an ENDWHILE. The WAM Interpreter will not accept incomplete constructs. Any (in this WAMIL language embodiment) incomplete construct will generate a syntax error from the WAM Interpreter. The Scriptor will not load or save a script containing any (in this WAMIL language embodiment) incomplete WHILE ENDWHILE constructs.
[3162] WHILE ENDWHILE constructs can be nested within any (in this WAMIL language embodiment) other WHILE ENDWHILE construct.
Glossary of IF-Construct Elements
[3163] This section presents a detailed glossary of WAMIL IF test expressions, and THEN and ELSE commands. The glossary begins with the IF-construct element, IF:ACTIVITY, and ends with the IF-construct element, THEN/ELSE:WAITQUERY.
[3164] 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 the commands. Each example is simple, but serves as a basis to enhance understanding of the command in the context of a WAMIL script.
IF:ACTIVITY
[3165] The text string, IF:ACTIVITY, is a test expression, i.e., element, in an IF-construct.
[3166] PURPOSE: Tests if the activity for the current CELL is equal to the string provided as an argument.
[3167] SYNTAX: IF:ACTIVITY string
[3168] EXAMPLE CALL: IF:ACTIVITY NVM
[3169] DESCRIPTION: The IF:ACTIVITY construct tests if the activity for the current CELL is equal to the string given. Upon execution, the WAM Interpreter OutBuff is searched for the activity state for the current CELL.
[3170] If the activity is equal to the string provided the expression will evaluate to TRUE and the THEN commands, or THENDO part of the IF-construct, will be executed, otherwise the ELSE commands, or ELSEDO part of the IF-construct, will be executed.
[3171] This command is only (in this embodiment of the WAMIL language) valid if the previously executed TI interface command was the TI:op:cell, generic command, and OutBuff holds the output of such command. Otherwise, the IF expression is not evaluated and no results are executed.
[3172] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of an IF ACTIVITY command, in which the WAMI global CELL variable had been previously set to the value of 49:
[3173] IF:
[3174] Cell 49 ACTIVITY=NVM
[3175] RESULT:
[3176] ACTIVITY=NO
[3177] ERRORS: If the IF:ACTIVITY command is executed, and the previous TI interface command executed was not TI:op:cell, generic the WAM Interpreter will print the following warning message to the WAMIL report file:
[3178] WARNING:
[3179] Activity Not Tested . . .
[3180] Must Execute TI:op:cell, generic Command First!
[3181] ALTERS: None (in this WAMIL language embodiment)
[3182] DEFAULT VALUE: None (in this WAMIL language embodiment)
[3183] SEE ALSO: IF:GENERIC string
[3184] EXAMPLE: The following script lines will test if there is no activity on the current cell:
[3185] TI:op:cell, generic
[3186] IF:ACTIVITY NO
[3187] THEN:CONTINUE
[3188] ELSE:PRINT Cell Has Undetermined Activity.
[3189] ELSE:ENDTEST
IF:AFAIL
[3190] The text string, IF:AFAIL, is a test expression, i.e., element, in an IF-construct.
[3191] PURPOSE: Tests if the execution if the last WAMIL APXRCV command failed.
[3192] SYNTAX: IF:AFAIL
[3193] EXAMPLE CALL: IF:AFAIL
[3194] DESCRIPTION: The IF:AFAIL construct tests the AFAIL flag which is set if the execution of a WAMIL APXRCV command fails for any reason. This flag is always reset prior to the execution of a new WAMIL APXRCV command.
[3195] If the AFAIL flag is set, the expression will evaluate to TRUE and the THEN commands, or THENDO part of the IF-construct, will be executed, otherwise the ELSE commands, or ELSEDO part of the IF-construct, will be executed.
[3196] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution of an IF:LFAIL command:
[3197] IF:
[3198] APXRCV Access Failed
[3199] RESULT:
[3200] APXRCV Access Failed
[3201] ERRORS: None.
[3202] ALTERS: None (in this WAMIL language embodiment)
[3203] DEFAULT VALUE: AFAIL by default is set to FALSE.
[3204] SEE ALSO: WAM:GETAPX db_form_name db_file_name, WAM:GETAPXFLD db_form_name db_field_name, WAM:PUTAPX db_form_name db_file_name, WAM:PUTAPXFLD db_form_name db_field_name
IF:APXVAR
[3205] The text string, IF:APXVAR, is a test expression, i.e., element, in an IF-construct.
[3206] PURPOSE: Tests the value of the WAMI VAR variable APXVAR.
[3207] SYNTAX: IF:APXVAR operator string
[3208] EXAMPLE CALL: IF:APXVAR GT 0
[3209] DESCRIPTION: The IF:APXVAR construct tests if the current value of the APXVAR variable is equal to, greater than, less than, or not equal to the string provided as an argument. For example, if the EQ operator is used, and the current APXVAR value is equal to the string provided as an argument, the IF-construct expression will evaluate to TRUE. If the current value is not equal to the string provided as an argument the IF-construct expression will evaluate to FALSE.
[3210] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of an IF:APXVAR command:
[3211] IF:
[3212] APXVAR EQ 0
[3213] RESULT:
[3214] APXVAR=1
[3215] ERRORS: None.
[3216] ALTERS: None (in this WAMIL language embodiment)
[3217] DEFAULT VALUE: None (in this WAMIL language embodiment).
[3218] SEE ALSO: WAM:GETAPXFLD db_form_name db_field_name, WAM:PUTAPXFLD db_form_name db_field_name
[3219] EXAMPLE: The following script will retrieve a field value from an APXRCV DB form, and set the value to zero:
[3220] WAM:MSC 5
[3221] WAM:CELL 49
[3222] WAM:ANT 1
[3223] WAM:GETAPXFLD ceqsu2 rmi_thresh
[3224] IF:APXVAR NE 0
[3225] THENDO:
[3226] WAM:SETVAR APXVAR 0
[3227] WAM:PUTAPXFLD ceqsu2 rmi_thresh
[3228] ELSEDO:
[3229] ENDIF:
[3230] WAM:ENDTEST
IF:CFAIL
[3231] The text string, IF:CFAIL, is a test expression, i.e., element, in an IF-construct.
[3232] PURPOSE: Tests if a disconnect occurred during a CONNECT command execution, or a WAMI interface command execution.
[3233] SYNTAX: IF:CFAIL
[3234] EXAMPLE CALL: IF:CFAIL
[3235] DESCRIPTION: The IF:CFAIL construct tests the CFAIL flag which is set if a disconnect occurs during the execution of any (in this WAMIL language embodiment) WAMI interface command. This flag is always reset prior to execution of an interface command.
[3236] If the CFAIL flag is set the expression will evaluate to TRUE and the THEN commands, or THENDO part of the IF-construct, will be executed, otherwise the ELSE commands, or ELSEDO part of the IF-construct, will be executed.
[3237] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution of an IF:CFAIL command:
[3238] IF:
[3239] Connection Failed
[3240] RESULT:
[3241] Connection Valid
[3242] ERRORS: None.
[3243] ALTERS: None (in this WAMIL language embodiment)
[3244] DEFAULT VALUE: CFAIL by default is set to FALSE.
[3245] SEE ALSO: WAM:CONNECT interface, WAM:DISCONNECT interface
[3246] EXAMPLE: The following script lines test if a disconnect occurred after execution of a TI command:
[3247] TI:op:cell 49
[3248] IF:CFAIL
[3249] THEN:ENDTEST
[3250] ELSE:CONTINUE
IF: COMPLETED
[3251] The text string, IF:COMPLETED, is a test expression, i.e., element, in an IF-construct.
[3252] PURPOSE: Tests if a completion message was returned for the previous WAMIL interface command executed.
[3253] SYNTAX: IF:COMPLETED
[3254] EXAMPLE CALL: IF:COMPLETED
[3255] DESCRIPTION: The IF:COMPLETED construct tests if an output message in OutBuff, generated from the previous interface command executed, contains the text string COMPLETED.
[3256] If the COMPLETED message is present in OutBuff, the expression will evaluate to TRUE and the THEN commands, or THENDO part of the IF-construct, will be executed, otherwise the ELSE commands, or ELSEDO part of the IF-construct, will be executed.
[3257] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of an IF:COMPLETED command:
[3258] IF:
[3259] Output Message: COMPLETED
[3260] RESULT:
[3261] OMSG Matched
[3262] ERRORS: None.
[3263] ALTERS: None (in this WAMIL language embodiment)
[3264] DEFAULT VALUE: OutBuff is always flushed prior to execution of an interface command.
[3265] SEE ALSO: IF:OMSG string
[3266] EXAMPLE: The following script lines test if a COMPLETED message was received after execution of a TI command:
[3267] TI:op:cell 49
[3268] IF:COMPLETED
[3269] THEN:ENDTEST
[3270] ELSE:CONTINUE
IF:GENERIC
[3271] The text string, IF:GENERIC, is a test expression, i.e., element, in an IF-construct.
[3272] PURPOSE: Tests if the generic for the current CELL is equal to the string provided as an argument.
[3273] SYNTAX: IF:GENERIC string
[3274] EXAMPLE CALL: IF:GENERIC a34Y120t
[3275] DESCRIPTION: The IF:GENERIC construct tests if the generic for the current CELL is equal to the string given. Upon execution, the WAM Interpreter OutBuff is searched for the generic for the current CELL.
[3276] If the generic is equal to the string provided the expression will evaluate to TRUE and the THEN commands, or THENDO part of the IF-construct, will be executed, otherwise the ELSE commands, or ELSEDO part of the IF-construct, will be executed.
[3277] This command is only (in this embodiment of the WAMIL language) valid if the previously executed TI interface command was the TI:op:cell, generic command, and OutBuff holds the output of such command. Otherwise, the IF expression is not evaluated and no results are executed.
[3278] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of an IF:GENERIC command:
[3279] IF:
[3280] Cell 49 GENERIC=a34Y120t
[3281] RESULT:
[3282] GENERIC=a34Y120t
[3283] ERRORS: If the IF:GENERIC command is executed, and the previous TI interface command executed was not TI:op:cell, generic the WAM Interpreter will print the following warning message to the WAMIL report file:
[3284] WARNING:
[3285] Generic Not Tested . . .
[3286] Must Execute TI:op:cell, generic Command First!
[3287] ALTERS: None (in this WAMIL language embodiment)
[3288] DEFAULT VALUE: None (in this WAMIL language embodiment)
[3289] SEE ALSO: IF:ACTIVITY string, WAM:GEN string
[3290] EXAMPLE: The following script lines test if the generic given is for the current cell:
[3291] TI:op:cell, generic
[3292] IF:GENRIC a34Y120t
[3293] THEN: CONTINUE
[3294] ELSE:PRINT Cell Has Incorrect Generic.
[3295] ELSE:ENDTEST
IF:LASTTEST
[3296] The text string, IF:LASTTEST, is a test expression, i.e., element, in an IF-construct.
[3297] PURPOSE: Tests if the WAMIL script has been executed for the last cell.
[3298] SYNTAX: IF:LASTTEST
[3299] EXAMPLE CALL: IF:LASTTEST
[3300] DESCRIPTION: The IF:LASTTEST is a special construct which tests if the current WAMIL script has been executed for the last cell number given in the LOOPCELL or LOOPCELLVARS command, or the last cell number in the WAMI VARn CELL list.
[3301] If the script has been executed for the last cell, the expression will evaluate to TRUE and the THEN commands, or THENDO part of the IF-construct, will be executed, otherwise the ELSE commands, or ELSEDO part of the IF-construct, will be executed.
[3302] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution of an IF:LASTTEST command:
[3303] IF:
[3304] Last Cell Tested
[3305] RESULT:
[3306] Last Cell Not Tested
[3307] ERRORS: None.
[3308] ALTERS: None (in this WAMIL language embodiment)
[3309] DEFAULT VALUE: None (in this WAMIL language embodiment).
[3310] SEE ALSO: WAM:LOOPCELL cells . . . , WAM:LOOPCELLVARS
[3311] EXAMPLE: The following script prints a message after the script has been executed for the last cell number:
[3312] WAM:MSC 5
[3313] WAM:LOOPCELL 49 101
[3314] TI:op:cell 49
[3315] IF:LASTEST
[3316] THEN:PRINT Last cell Tested.
[3317] THEN:ENDTEST
[3318] ELSE:CONTINUE
IF:LFAIL
[3319] The text string, IF:LFAIL, is a test expression, i.e., element, in an IF-construct.
[3320] PURPOSE: Tests if a login attempt failed during execution of a CONNECT command.
[3321] SYNTAX: IF:LFAIL
[3322] EXAMPLE CALL: IF:LFAIL
[3323] DESCRIPTION: The IF:LFAIL construct tests the LFAIL flag which is set if a login attempt to establish a WAM Interpreter interface session connection fails during the execution of a CONNECT command. This flag is always reset prior to execution of a CONNECT command.
[3324] If the LFAIL flag is set, the expression will evaluate to TRUE and the THEN commands, or THENDO part of the IF-construct, will be executed, otherwise the ELSE commands, or ELSEDO part of the IF-construct, will be executed.
[3325] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution of an IF:LFAIL command:
[3326] IF:
[3327] Login Failed
[3328] RESULT:
[3329] Login Valid
[3330] ERRORS: None.
[3331] ALTERS: None (in this WAMIL language embodiment)
[3332] DEFAULT VALUE: LFAIL by default is set to FALSE.
[3333] SEE ALSO: WAM:CONNECT interface
[3334] EXAMPLE: The following script lines test if a failed login occurred while attempting to establish a TIpdunix session:
[3335] WAM:CONNECT TI
[3336] IF:LFAIL
[3337] THEN:ENDTEST
[3338] ELSE:CONTINUE
IF:OMSG
[3339] The text string, IF:OMSG, is a test expression, i.e., element, in an IF-construct.
[3340] PURPOSE: Tests if the string provided was returned for the previous WAMIL interface command executed.
[3341] SYNTAX: IF:OMSG string
[3342] EXAMPLE CALL: IF:OMSG BBA BBAVAR, COMPLETED
[3343] DESCRIPTION: The IF:OMSG construct tests if the string given as an argument is present in the WAM Interpreter OutBuff. This is the same as testing if the previous WAMIL interface command executed returned an output message equal to the string given, since the output of all (in this embodiment of the WAMIL language) WAMIL interface commands gets placed in OutBuff.
[3344] If the string given is present in OutBuff, the expression will evaluate to TRUE and the THEN commands, or THENDO part of the IF-construct, will be executed, otherwise the ELSE commands, or ELSEDO part of the IF-construct, will be executed.
[3345] The string argument can also include references to WAMI global variables, or WAMI VARn variables. To reference a WAMI global variable the suffix VAR is simply added to the WAMI global variable name. This is not to be mistaken with WAMI VAR variables. Although when referencing WAMI global variables within strings the names resemble WAMI VAR variables, this naming convention was chosen to allow references to WAMI global variables and still be able to print the variable name. To include the value of a WAMI VAR variable, a WAMI global variable can (in this embodiment of the WAMIL language) first be associated. Then references to the WAMI global variable will yield the value of the WAMI VAR variable it is associated with.
[3346] OUTPUT: The string provided is printed in the WAMIL report file as part of the IF-construct output message. Variable substitution is performed if WAM Interpreter variables are referenced within the string provided.
[3347] The following is an example of the output generated to the WAMIL report file upon execution of a IF:OMSG command which includes reference to a WAMI global variable:
[3348] IF:
[3349] Output Message: BBA 2, COMPLETED
[3350] RESULT:
[3351] OMSG Matched
[3352] ERRORS: None.
[3353] ALTERS: None (in this WAMIL language embodiment)
[3354] DEFAULT VALUE: OutBuff is always flushed prior to execution of an interface command.
[3355] SEE ALSO: IF:COMPLETED
[3356] EXAMPLE: The following script lines test if a COMPLETED message was received after execution of a TI command:
[3357] TI:op:cell 49
[3358] IF:OMSG COMPLETED
[3359] THEN:ENDTEST
[3360] ELSE:CONTINUE
IF:SDPFAIL
[3361] The text string, IF:SDPFAIL, is a test expression, i.e., element, in an IF-construct.
[3362] PURPOSE: Tests if an SDP interface command execution or connection attempt failed.
[3363] SYNTAX: IF:SDPFAIL
[3364] EXAMPLE CALL: IF:SDPFAIL
[3365] DESCRIPTION: The IF:SDPFAIL construct tests the SDP interface failure flag which is set if the execution of any (in this WAMIL language embodiment) SDP interface command fails in any manner. The SDPFAIL flag is also set when the execution of a WAM:CONNECT SDP command fails to establish an SDP session. To determine the cause of the failure the CFAIL, LFAIL, TFAIL, or SDPPORT flags can then be tested.
[3366] If the SDP interface failure flag is set, the expression will evaluate to TRUE and the THEN commands, or THENDO part of the IF-construct, will be executed, otherwise the ELSE commands, or ELSEDO part of the IF-construct, will be executed.
[3367] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution of an IF:SDPFAIL command:
[3368] IF:
[3369] SDP Interface Command Failure
[3370] RESULT:
[3371] SDP Interface Command Failed
[3372] ERRORS: None.
[3373] ALTERS: None (in this WAMIL language embodiment)
[3374] DEFAULT VALUE: None (in this WAMIL language embodiment)
[3375] SEE ALSO: WAM:CONNECT interface
[3376] EXAMPLE: The following script lines test if an executed SDP interface command failed, and if so the type of failure:
[3377] SDP:2138,49
[3378] IF:SDPFAIL
[3379] THENDO:
[3380] IF:TFAIL
[3381] THENDO:
[3382] WAM:PRINT SDP Command Timeout.
[3383] ELSEDO:
[3384] ENDIF
[3385] IF:CFAIL
[3386] THENDO:
[3387] WAM:PRINT SDP Connection Failure.
[3388] WAM:ENDTEST
[3389] ELSEDO:
[3390] ENDIF:
[3391] ELSEDO:
[3392] ENDIF:
[3393] The following script lines test if a CONNECT command failed to establish an SDP session, and if so the type of failure:
[3394] WAM:CONNECT SDP
[3395] IF:SDPFAIL
[3396] THENDO:
[3397] IF:LFAIL
[3398] THEN:PRINT SDP OMP Server Login Failure.
[3399] ELSE:CONTINUE
[3400] IF:CFAIL
[3401] THEN:PRINT SDP Connection Attempt Failure.
[3402] ELSE:CONTINUE
[3403] IF:SDPPORT
[3404] THEN:PRINT No SDP VTTY Ports Available.
[3405] ELSE:CONTINUE
[3406] WAM:ENDTEST
[3407] ELSEDO:
[3408] ENDIF:
IF:SDPPORT
[3409] The text string, IF:SDPPORT, is a test expression, i.e., element, in an IF-construct.
[3410] PURPOSE: Tests if a login attempt to an SDP port failed due to unavailable ports.
[3411] SYNTAX: IF:SDPPORT
[3412] EXAMPLE CALL: IF:SDPPORT
[3413] DESCRIPTION: The IF:SDPPORT construct tests the SDP port flag which is set if a login attempt to an SDP port fails due to unavailable ports. This flag is always set when the last WAM:CONNECT SDP command executed failed to access a port.
[3414] If the SDP port flag is set, the expression will evaluate to TRUE and the THEN commands, or THENDO part of the IF-construct, will be executed, otherwise the ELSE commands, or ELSEDO part of the IF-construct, will be executed.
[3415] The following is an example of the output generated to the WAMIL report file, upon execution of an IF:SDPORT command:
[3416] IF:
[3417] SDP Ports Are NOT Available
[3418] RESULT:
[3419] SDP Ports Are Available
[3420] ERRORS: None.
[3421] ALTERS: None (in this WAMIL language embodiment)
[3422] DEFAULT VALUE: None (in this WAMIL language embodiment)
[3423] SEE ALSO: WAM:CONNECT interface
[3424] EXAMPLE: The following script lines test if an SDP port is available upon a login attempt:
[3425] WAM:CONNECT SDP
[3426] IF:SDPPORT
[3427] THEN:ENDTEST
[3428] ELSE:CONTINUE
IF:SDPVAR_COLOR
[3429] The text string, IF:SDPVAR_COLOR, is a test expression, i.e., element, in an IF-construct.
[3430] PURPOSE: Tests if the COLOR of the SDPVAR indicator is equal to, or not equal to, a valid, pre-defined color.
[3431] SYNTAX: IF:SDPVAR_COLOR operator string
[3432] EXAMPLE CALL: IF:SDPVAR_COLOR EQ BLACK_ON_RED
[3433] DESCRIPTION: The IF:SDPVAR_COLOR construct tests if the COLOR of the current SDPVAR indicator is set to a valid, pre-defined color. For example, if the EQ operator is used, and the COLOR is equal to the string provided as an argument, the IF-construct expression will evaluate to TRUE. If the COLOR is not equal to the string provided as an argument, the IF-construct expression will evaluate to FALSE.
[3434] For a list of valid, pre-defined colors which SDPVAR_COLOR can be set to refer to the GETSDP command.
[3435] OUTPUT: The following is an example of the output generated to the WAMIL report file, for the BBA indicator name, upon execution of an IF:SDPVAR_COLOR EQ BLACK_ON_RED command:
[3436] IF:
[3437] BBA 19 COLOR EQ BLACK_ON_RED
[3438] RESULT:
[3439] BBA 19 COLOR=BLACK_ON_RED
[3440] The following is an example of the output generated to the WAMIL report file, for the CCC indicator name, upon execution of an IF:SDPVAR_COLOR EQ BLACK_ON_RED command:
[3441] IF:
[3442] CCC 19 COLOR EQ BLACK_ON_RED
[3443] RESULT:
[3444] CCC 19 COLOR=BLACK_ON_RED
[3445] The following is an example of the output generated to the WAMIL report file, for the CCCOOS indicator name, upon execution of an IF:SDPVAR_COLOR EQ WHITE_ON_BLACK command:
[3446] IF:
[3447] CCC 19 OOS CEs COLOR EQ WHITE_ON_BLACK
[3448] RESULT:
[3449] CCC 19 OOS CEs COLOR=WHITE_ON_BLACK
[3450] The following is an example of the output generated to the WAMIL report file, for the CHANL indicator name, upon execution of an IF:SDPVAR_COLOR EQ WHITE_ON_BLACK command:
[3451] IF:
[3452] BBA 19 Channel Frequency COLOR EQ WHITE_ON_BLACK
[3453] RESULT:
[3454] BBA 19 Channel Frequency COLOR=WHITE_ON_BLACK
[3455] The following is an example of the output generated to the WAMIL report file, for the PAF indicator name, upon execution of an IF:SDPVAR_COLOR EQ RED_ON_YELLOW command:
[3456] IF:
[3457] BBA 1 Physical Antenna Face COLOR EQ RED_ON_YELLOW
[3458] RESULT:
[3459] BBA 1 Physical Antenna Face COLOR=RED_ON_YELLOW
[3460] The following is an example of the output generated to the WAMIL report file, for the PPW indicator name, upon execution of an IF:SDPVAR_COLOR EQ BLUE_ON_YELLOW command:
[3461] IF:
[3462] CCC 1 Packet Pipe Width COLOR EQ BLUE_ON_YELLOW
[3463] RESULT:
[3464] CCC 1 Packet Pipe Width COLOR=BLUE_ON_YELLOW
[3465] ERRORS: None.
[3466] ALTERS: None (in this WAMIL language embodiment)
[3467] DEFAULT VALUE: SDPVAR_COLOR is set to INVALID upon initial startup. The WAM:INITIALIZE command does not alter this variable.
[3468] SEE ALSO: WAM:GETSDP indicator_name
[3469] EXAMPLE: The following script lines will test if the indicator color for the current CCC is set to BLACK_ON_GREEN:
[3470] WAM:CELL 49
[3471] WAM:CCC 19
[3472] SDP:2138,49
[3473] WAM:GETSDP CCC
[3474] IF:SDPVAR_COLOR EQ BLACK_ON_GREEN
[3475] THEN:CCC Is Active
[3476] ELSE:PRINT CCC Is Not Active
IF:SDPVAR STATE
[3477] The text string, IF:SDPVAR_STATE, is a test expression, i.e., element, in an IF-construct.
[3478] PURPOSE: Tests if the STATE of the SDPVAR indicator is equal to, or not equal to, a valid, pre-defined state.
[3479] SYNTAX: IF:SDPVAR_STATE operator string
[3480] EXAMPLE CALL: IF:SDPVAR_STATE EQ ACT
[3481] DESCRIPTION: The IF:SDPVAR_STATE construct tests if the STATE of the current SDPVAR indicator is set to a valid, pre-defined state. For example, if the EQ operator is used, and the STATE is equal to the string provided as an argument, the IF-construct expression will evaluate to TRUE. If the STATE is not equal to the string provided as an argument, the IF-construct expression will evaluate to FALSE.
[3482] For a list of valid, pre-defined text words which SDPVAR_STATE can be set to refer to the GETSDP command.
[3483] OUTPUT: The following is an example of the output generated to the WAMIL report file, for the BBA indicator name, upon execution of an IF:SDPVAR_STATE EQ ACT command:
[3484] IF:
[3485] BBA 19 STATE EQ ACT
[3486] RESULT:
[3487] BBA 19 STATE=ACT
[3488] The following is an example of the output generated to the WAMIL report file, for the CCC indicator name, upon execution of an IF:SDPVAR_STATE EQ ACT command:
[3489] IF:
[3490] CCC 19 STATE EQ ACT
[3491] RESULT:
[3492] CCC 19 STATE=ACT
[3493] The following is an example of the output generated to the WAMIL report file, for the CCCOOS indicator name, upon execution of an IF:SDPVAR_STATE EQ INDETMNT command:
[3494] IF:
[3495] CCC 19 OOS CEs STATE EQ INDETMNT
[3496] RESULT:
[3497] CCC 19 OOS CEs STATE=INDETMNT
[3498] The following is an example of the output generated to the WAMIL report file, for the CHANL indicator name, upon execution of an IF:SDPVAR_STATE EQ OFF command:
[3499] IF:
[3500] BBA 19 Channel Frequency STATE EQ OFF
[3501] RESULT:
[3502] BBA 19 Channel Frequency STATE=OFF
[3503] The following is an example of the output generated to the WAMIL report file, for the PAF indicator name, upon execution of an IF:SDPVAR_STATE EQ MINOR command:
[3504] IF:
[3505] BBA 1 Physical Antenna Face STATE EQ MINOR
[3506] RESULT:
[3507] BBA 1 Physical Antenna Face STATE=MINOR
[3508] The following is an example of the output generated to the WAMIL report file, for the PPW indicator name, upon execution of an IF:SDPVAR_STATE EQ OOS command:
[3509] IF:
[3510] CCC 1 Packet Pipe Width STATE EQ OOS
[3511] RESULT:
[3512] CCC 1 Packet Pipe Width STATE=OOS
[3513] ERRORS: None.
[3514] ALTERS: None (in this WAMIL language embodiment)
[3515] DEFAULT VALUE: SDPVAR_STATE is set to INVALID upon initial startup. The WAM:INITIALIZE command does not alter this variable.
[3516] SEE ALSO: WAM:GETSDP indicator_name
[3517] EXAMPLE: The following script lines will test if the indicator STATE for the current CCC is ACT:
[3518] WAM:CELL 49
[3519] WAM:CCC 19
[3520] SDP:2138,49
[3521] WAM:GETSDP CCC
[3522] IF:SDPVAR_STATE EQ ACT
[3523] THEN:CCC Is Active
[3524] ELSE:PRINT CCC Is Not Active
IF:SDPVAR_VALUE
[3525] The text string, IF:SDPVAR_VALUE, is a test expression, i.e., element, in an IF-construct.
[3526] PURPOSE: Tests the VALUE of the SDPVAR indicator.
[3527] SYNTAX: IF:SDPVAR_VALUE operator string
[3528] EXAMPLE CALL: IF:SDPVAR_VALUE GT 18
[3529] DESCRIPTION: The IF:SDPVAR_VALUE construct tests if the VALUE of the current SDPVAR indicator is equal to, greater than, less than, or not equal to the string provided as an argument. For example, if the EQ operator is used, and the VALUE is equal to the string provided as an argument, the IF-construct expression will evaluate to TRUE. If the VALUE is not equal to the string provided as an argument, the IF-construct expression will evaluate to FALSE.
[3530] SDPVAR_VALUE can be set to any (in this WAMIL language embodiment) text, numerical, or alphanumerical string.
[3531] For a list of relational operators supported, refer to the WAM Interpreter Keywords & Operators section.
[3532] OUTPUT: The following is an example of the output generated to the WAMIL report file, for the BBA indicator name, upon execution of an IF:SDPVAR_VALUE EQ 19 command:
[3533] IF:
[3534] BBA 19 VALUE EQ 19
[3535] RESULT:
[3536] BBA 19 VALUE=19
[3537] The following is an example of the output generated to the WAMIL report file, for the CCC indicator name, upon execution of an IF:SDPVAR_VALUE EQ 19 command:
[3538] IF:
[3539] CCC 19 VALUE EQ 19
[3540] RESULT:
[3541] CCC 19 VALUE=19
[3542] The following is an example of the output generated to the WAMIL report file, for the CCCOOS indicator name, upon execution of an IF:SDPVAR_VALUE EQ 40 command:
[3543] IF:
[3544] CCC 19 OOS CEs VALUE EQ 40
[3545] RESULT:
[3546] CCC 19 OOS CEs VALUE=40
[3547] The following is an example of the output generated to the WAMIL report file, for the CHANL indicator name, upon execution of an IF:SDPVAR_VALUE EQ 450 command:
[3548] IF:
[3549] BBA 19 Channel Frequency VALUE EQ 450
[3550] RESULT:
[3551] BBA 19 Channel Frequency VALUE=450
[3552] The following is an example of the output generated to the WAMIL report file, for the PAF indicator name, upon execution of an IF:SDPVAR_VALUE EQ 1 command:
[3553] IF:
[3554] BBA 1 Physical Antenna Face VALUE EQ 1
[3555] RESULT:
[3556] BBA 1 Physical Antenna Face VALUE=1
[3557] The following is an example of the output generated to the WAMIL report file, for the PPW indicator name, upon execution of an IF:SDPVAR_VALUE EQ 24-8 command:
[3558] IF:
[3559] CCC 1 Packet Pipe Width VALUE EQ 24-8
[3560] RESULT:
[3561] CCC 1 Packet Pipe Width VALUE=24-8
[3562] ERRORS: None.
[3563] ALTERS: None (in this WAMIL language embodiment)
[3564] DEFAULT VALUE: SDPVAR_VALUE is set to INVALID upon initial startup. The WAM:INITIALIZE command does not alter this variable.
[3565] SEE ALSO: WAM:GETSDP indicator_name
[3566] EXAMPLE: The following script lines will test if the channel frequency for the current BBA is 450:
[3567] WAM:CELL 49
[3568] WAM:BBA 19
[3569] SDP:2138,49
[3570] WAM:GETSDP CHANL
[3571] IF:SDPVAR_VALUE EQ 450
[3572] THEN:PRINT Channel Frequency is Correct
[3573] ELSE:PRINT Channel Frequency is Not Correct
IF:TEST_EXPR
[3574] The text string, IF:TEST_EXPR, is a test expression, i.e., element, in an IF-construct.
[3575] PURPOSE: Instructs the WAM Interpreter to perform a relational comparison between string1 and string2.
[3576] SYNTAX: IF:TEST_EXPR string1 operator string2
[3577] EXAMPLE CALL: IF:TEST_EXPR APXVAR EQ WAMVAR
[3578] DESCRIPTION: The IF:TEST_EXPR construct performs a relational comparison between any two values, strings, or WAM Interpreter variables. The arguments string1 and string2 can reference any (in this WAMIL language embodiment) WAMI global variable, WAMI VAR variable, WAMI VARn List variable name, and WAM Interpreter keyword.
[3579] For a list relational operators supported refer to the WAM Interpreter Keywords & Operators section.
[3580] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of an IF:TEST_EXPR command:
[3581] IF:
[3582] TEST_EXPR APXVAR EQ WAMVAR
[3583] RESULT:
[3584] TRUE: 0 EQ 0
[3585] ERRORS: None.
[3586] ALTERS: None (in this WAMIL language embodiment)
[3587] DEFAULT VALUE: None (in this WAMIL language embodiment).
[3588] SEE ALSO: WAMI VAR variables IF-constructs
[3589] EXAMPLE: The following script lines test if the results of an analysis program executed from within the script is PASS or FAIL:
[3590] WAM:UNIX analysis_script
[3591] IF:TEST_EXPR WAMVAR EQ PASS
[3592] THEN: CONTINUE
[3593] ELSE:ENDTEST
IF:TFAIL
[3594] The text string, IF:TFAIL, is a test expression, i.e., element, in an IF-construct.
[3595] PURPOSE: Tests if a no input message was received from the last WAMIL interface command executed.
[3596] SYNTAX: IF:TFAIL
[3597] EXAMPLE CALL: IF:TFAIL
[3598] DESCRIPTION: The IF:TFAIL construct tests the TFAIL flag which is set if the last interface command executed received no input messages within the time defined by the WAMI global variable TimeOut. This flag is always reset prior to execution of any (in this WAMIL language embodiment) interface command.
[3599] After successful execution of a CONNECT command, if the connection times out at any point during the execution of any (in this WAMIL language embodiment) subsequent WAMIL interface commands for such interface, meaning no response is received from the interface within the time specified by the WAMI global variable TimeOut, the WAM Interpreter TFAIL flag will be set. The WAM Interpreter will then, for example, generate the following output to the WAMIL report file:
[3600] TIpdunix Command Time Out!
[3601] If the TFAIL flag is set, the expression will evaluate to TRUE and the THEN commands, or THENDO part of the IF-construct, will be executed, otherwise the ELSE commands, or ELSEDO part of the IF-construct, will be executed.
[3602] OUTPUT: The following is an example of the output generated to the WAMIL report file, upon execution of an IF:TFAIL command:
[3603] IF:
[3604] TimeOut Occurred
[3605] RESULT:
[3606] No TimeOut Occurred
[3607] ERRORS: None.
[3608] ALTERS: None (in this WAMIL language embodiment)
[3609] DEFAULT VALUE: TFAIL by default is set to FALSE.
[3610] SEE ALSO: WAM:CONNECT interface
[3611] EXAMPLE: The following script lines test if a time out occurred during execution of a TI interface command:
[3612] TI:op:cell, generic
[3613] IF:TFAIL
[3614] THEN:ENDTEST
[3615] ELSE:CONTINUE
IF:WAMVAR
[3616] The text string, IF:WAMVAR, is a test expression, i.e., element, in an IF-construct.
[3617] PURPOSE: Tests the value of the WAMI VAR variable WAMVAR.
[3618] SYNTAX: IF:WAMVAR operator string
[3619] EXAMPLE CALL: IF:WAMVAR NE 1
[3620] DESCRIPTION: The IF:WAMVAR construct tests if the current value of the WAMVAR variable is equal to, greater than, less than, or not equal to the string provided as an argument. For example, if the EQ operator is used, and the current WAMVAR value is equal to the string provided as an argument, the IF-construct expression will evaluate to TRUE. If the current value is not equal to the string provided as an argument the IF-construct expression will evaluate to FALSE.
[3621] WAMVAR can be set to any (in this WAMIL language embodiment) text, numerical, or alphanumerical string.
[3622] A list of relational operators that are supported is found herein refer to the WAM Interpreter Keywords & Operators section.
[3623] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of an IF:WAMVAR command:
[3624] IF:
[3625] WAMVAR NE 1
[3626] RESULT:
[3627] WAMVAR=0
[3628] ERRORS: None.
[3629] ALTERS: None (in this WAMIL language embodiment)
[3630] DEFAULT VALUE: WAMVAR is set to NULL upon initial startup. The WAM:INITIALIZE command also sets this variable to NULL.
[3631] SEE ALSO: WAM:UNIX command
[3632] EXAMPLE: The following script executes a ksh script called Analyze Data, and checks the value returned from the script:
[3633] WAM:MSC 5
[3634] WAM:CELL 49
[3635] WAM:ANT 1
[3636] WAM:UNIX Analyze_Data
[3637] IF:WAMVAR EQ 1
[3638] THENDO:
[3639] WAM:PRINT All Tests Passed.
[3640] WAM:ENDTEST
[3641] ELSEDO:
[3642] WAM:PRINT Data Analysis Failed
[3643] WAM:ENDTEST
[3644] ENDIF:
[3645] WAM:ENDTEST
THEN/ELSE:CONTINUE
[3646] The text string, THEN/ELSE:CONTINUE, is an element in an IF-construct.
[3647] PURPOSE: Instructs the WAM Interpreter to execute the next WAMIL script command.
[3648] SYNTAX: THEN:CONTINUE
[3649] ELSE:CONTINUE
[3650] EXAMPLE CALL: THEN:CONTINUE
[3651] DESCRIPTION: The THEN:CONTINUE and ELSE:CONTINUE constructs instruct the WAM Interpreter to immediately execute the next WAMIL script command. This command exists as a means to have the effect to fall through to the next script command in the case a TRUE, or FALSE, evaluation of an IF-construct is not important.
[3652] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a THEN:CONTINUE construct:
[3653] THEN:
[3654] Continue Test
[3655] The following is an example of the output generated to the
[3656] WAMIL
[3657] report file upon execution of a ELSE:CONTINUE construct:
[3658] ELSE:
[3659] Continue Test
[3660] ERRORS: THEN and ELSE constructs can (in this embodiment of the WAMIL language) be used within IF THEN ELSE constructs. Including a THEN construct not preceded by an IF or THEN, or an ELSE construct not preceded by a THEN or ELSE, will generate a syntax error.
[3661] ALTERS: None (in this WAMIL language embodiment)
[3662] DEFAULT VALUE: None (in this WAMIL language embodiment).
[3663] SEE ALSO: All WAMIL IF-constructs.
THEN/ELSE:ENDTEST
[3664] The text string, THEN/ELSE:ENDTEST, is an element in an IF-construct.
[3665] PURPOSE: Instructs the WAM Interpreter to terminate the WAMIL script.
[3666] SYNTAX: THEN:ENDTEST
[3667] ELSE:ENDTEST
[3668] EXAMPLE CALL: THEN:ENDTEST
[3669] DESCRIPTION: The THEN:ENDTEST and ELSE:ENDTEST constructs instruct the WAM Interpreter to immediately terminate the current WAMIL script in execution.
[3670] If the WAMIL script is looping through multiple cells, meaning the LOOPCELL or LOOPCELLVARS command has been executed in the script, the THEN:ENDTEST and ELSE:ENDTEST constructs are executed if the evaluation of an IF-construct instructs the WAM Interpreter so, regardless of whether or not the last cell has been tested.
[3671] Upon execution, this construct will close all (in this embodiment of the WAMIL language) active WAM Interpreter xterm windows and terminate all (in this embodiment of the WAMIL language) associated processes. The WAMIL report file will then be closed and saved and the WAMIL script will be terminated, along with the script status display window.
[3672] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of an THEN:ENDTEST construct:
[3673] THEN:
[3674] End Test
[3675] The following is an example of the output generated to the WAMIL report file upon execution of an ELSE:ENDTEST construct:
[3676] ELSE:
[3677] End Test
[3678] If any (in this WAMIL language embodiment) interface sessions are active upon execution of this construct, the WAM Interpreter will print a corresponding disconnect message for each session that is closed in the WAMIL report file (See DISCONNECT command).
[3679] ERRORS: THEN and ELSE constructs can (in this embodiment of the WAMIL language) be used within IF THEN ELSE constructs. Including a THEN construct not preceded by an IF or THEN, or an ELSE construct not preceded by a THEN or ELSE, will generate a syntax error.
[3680] See DISCONNECT.
[3681] ALTERS: None (in this WAMIL language embodiment).
[3682] DEFAULT VALUE: None (in this WAMIL language embodiment).
[3683] SEE ALSO: WAM:DISCONNECT interface, WAM:ENDTEST
[3684] EXAMPLE: The following script lines will login to a TI interface, execute a TI command, and then end the test if the command is successful:
[3685] WAM:MSC 5
[3686] WAM:CELL 49
[3687] WAM:CONNECT TI
[3688] TI:cfr:cell 49, multi bba 4; config 15
[3689] IF:OMSG COMPLETED
[3690] THEN:ENDTEST
[3691] ELSE:CONTINUE
THEN/ELSE:PRINT
[3692] The text string, THEN/ELSE:PRINT, is an element in an IF-construct.
[3693] PURPOSE: Instructs the WAM Interpreter to print the string provided in the WAMIL report file.
[3694] SYNTAX: THEN:PRINT string
[3695] ELSE:PRINT string
[3696] EXAMPLE CALL: THEN:PRINT Test Case jt1234 Failed.
[3697] DESCRIPTION: The THEN:PRINT and ELSE:PRINT constructs print the string provided as an argument in the script WAMIL report file.
[3698] The string provided can include references to WAMI global variables, or WAMI VARn variables. To reference a WAMI global variable the suffix VAR is simply added to the WAMI global variable name. For example, the following string, CCC CCCVAR is OOS, will be interpreted and printed as follows for a WAMI global CCC variable with a value of 4:
[3699] CCC 4 is OOS
[3700] This is not to be mistaken with WAMI VAR variables. Although when referencing WAMI global variables within strings to be printed the names resemble WAMI VAR variables, this naming convention was chosen to allow references to WAMI global variables and still be able to print the variable name. In the above example the WAMI global name CCC was printed along with the value of the WAMI global variable. To print the value of a WAMI VAR variable, a WAMI global variable can (in this embodiment of the WAMIL language) first be associated. Then references to the WAMI global variable will yield the value of the WAMI VAR variable it is associated with.
[3701] OUTPUT: The string provided is printed in the WAMIL report file as given. Variable substitution is performed if WAM Interpreter variables are referenced within the string provided.
[3702] The following is an example of the output generated to the WAMIL report file upon execution of a THEN:PRINT construct which includes reference to a WAMI global variable:
[3703] THEN:
[3704] This test Is For Antenna Face 1.
[3705] The following is an example of the output generated to the WAMIL report file upon execution of a ELSE:PRINT construct which includes reference to a WAMI global variable:
[3706] ELSE:
[3707] This test Is For Antenna Face 1.
[3708] ERRORS: THEN and ELSE constructs can (in this embodiment of the WAMIL language) be used within IF THEN ELSE constructs. Including a THEN construct not preceded by an IF or THEN, or an ELSE construct not preceded by a THEN or ELSE, will generate a syntax error.
[3709] ALTERS: None (in this WAMIL language embodiment).
[3710] DEFAULT VALUE: None (in this WAMIL language embodiment).
[3711] EXAMPLE: The following script lines print to the script WAMIL report file, after successful execution of a TI interface command:
[3712] WAM:CELL 49
[3713] WAM:BBAVAR
[3714] TI:dgn:cell 49, bba BBAVAR
[3715] IF:OMSG COMPLETED
[3716] THEN:PRINT Diagnostics on Cell CELLVAR, for BBA BBAVAR
[3717] ELSE:ENDTEST
THEN/ELSE:TIMEOUT
[3718] The text string, THEN/ELSE:TIMEOUT, is an element in an IF-construct.
[3719] PURPOSE: Changes the WAM Interpreter global TimeOut variable, TimeOut, to the value provided as an argument.
[3720] SYNTAX: THEN:TIMEOUT seconds
[3721] ELSE:TIMEOUT seconds
[3722] EXAMPLE CALL: THEN:TIMEOUT 60
[3723] DESCRIPTION: The THEN:TIMEOUT and ELSE:TIMEOUT constructs set the WAM Interpreter global TimeOut variable to the value provided as an argument. After execution of this construct, all (in this embodiment of the WAMIL language) subsequent commands which require use the TimeOut variable will reference the new value.
[3724] The WAM Interpreter TimeOut variable plays a major role during execution of a CONNECT command. Setting this variable too small will cause frequent time outs if system response is slow.
[3725] The TimeOut variable is referenced during input from any (in this WAMIL language embodiment) active interface session. If nothing at all (in this embodiment of the WAMIL language) is received within the time specified by the variable, the WAM Interpreter TFAIL flag will be set.
[3726] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a THEN:TIMEOUT construct:
[3727] THEN:
[3728] TimeOut Changed To: 60 Seconds
[3729] ERRORS: Setting TimeOut to a negative number or zero will cause unpredictable results.
[3730] THEN and ELSE constructs can (in this embodiment of the WAMIL language) be used within IF THEN ELSE constructs. Including a THEN construct not preceded by an IF or THEN, or an ELSE construct not preceded by a THEN or ELSE, will generate a syntax error.
[3731] ALTERS: TimeOut
[3732] DEFAULT VALUE: TimeOut is set to 30 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 30.
[3733] SEE ALSO: IF:TFAIL, WAM:INITIALIZE
[3734] EXAMPLE: The following script lines change the TimeOut before execution of a TI command:
[3735] WAM:CAT 1
[3736] WAM:TIMEOUT 30
[3737] TI:rst:cell 49, cat 1
THEN/ELSE:WAIT
[3738] The text string, THEN/ELSE:WAIT, is an element in an IF-construct.
[3739] PURPOSE: Instructs the WAM Interpreter to wait a specified number of seconds before execution of the next WAMIL script command.
[3740] SYNTAX: THEN:WAIT seconds
[3741] ELSE:WAIT seconds
[3742] EXAMPLE CALL: THEN:WAIT 10
[3743] DESCRIPTION: The THEN:WAIT and ELSE:WAIT constructs instruct the WAM Interpreter to wait a specified number of seconds before executing the next WAMIL script command.
[3744] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a THEN:WAIT construct:
[3745] THEN:
[3746] WAMIL Wait: 10 Seconds
[3747] ERRORS: Setting WAIT to a negative number or zero will have no effect.
[3748] THEN and ELSE constructs can (in this embodiment of the WAMIL language) be used within IF THEN ELSE constructs. Including a THEN construct not preceded by an IF or THEN, or an ELSE construct not preceded by a THEN or ELSE, will generate a syntax error.
[3749] ALTERS: Wait
[3750] DEFAULT VALUE: Wait is set to 10 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 10.
[3751] SEE ALSO: WAM:INITLALIZE
[3752] EXAMPLE: The following script lines execute a TI command and then waits seconds before executing the next command:
[3753] TI:rst:cell 49, cat 1
[3754] IF:COMPLETED
[3755] THEN:WAIT 10
[3756] ELSE:WAITQUERY 5 TI 3
THEN/ELSE:WAITQUERY
[3757] The text string, THEN/ELSE:WAITQUERY, is an element in an IF-construct.
[3758] PURPOSE: Instructs the WAM Interpreter to wait a specified number of seconds and then query the TI interface up to a total amount of queries defined by value.
[3759] SYNTAX: THEN:WAITQUERY seconds TI value
[3760] ELSE:WAITQUERY seconds TI value
[3761] EXAMPLE CALL: THEN:WAITQUERY 5 TI 3
[3762] DESCRIPTION: The WAITQUERY construct instructs the WAM Interpreter to wait a specified number of seconds and then query the TI interface for additional output messages until either the IF-construct previously executed evaluates TRUE, or the total amount of queries defined by value have been met. During the query process, additional input messages received are appended to OutBuff. Thus, OutBuff is not flushed upon execution of a WAITQUERY construct.
[3763] The WAITQUERY construct allows a WAMIL script to camp on an executed TI interface command until a specified TI output message is received. If the message is never received, the WAITQUERY command allows a user to define how many times the TI interface will be queried before the script continues execution. Thus preventing the script from looping indefinitely.
[3764] If the input message is received prior to execution of the last query loop, the previously executed IF-construct will evaluate TRUE and the WAMIL script will continue execution.
[3765] The WAITQUERY command is only (in this embodiment of the WAMIL language) effective for an ELSE construct, execution of a THEN:WAITQUERY construct will have the same effect as the execution of a WAM:WAIT command.
[3766] OUTPUT: The following is an example of the output generated to the WAMIL report file upon execution of a ELSE:WAITQUERY construct:
[3767] ELSE:
[3768] Query TI In 10 Seconds
[3769] Repeat Query Up To 3 Times
[3770] The following is an example of the output generated to the WAMIL report file upon execution of a THEN:WAITQUERY construct:
[3771] THEN:
[3772] Query TI In 10 Seconds
[3773] Repeat Query Up To 3 Times
[3774] THEN Query NOT Executed After 10 Second Wait.
[3775] If any (in this WAMIL language embodiment) additional messages are received during any query, they are appended to OutBuff and also printed to the WAMIL report file.
[3776] If during execution of any (in this WAMIL language embodiment) ELSE query the IF-construct evaluates TRUE, the following is an example of the output generated to the WAMIL report file:
[3777] !!!!!! QUERY SUCCESSFUL ON ATTEMPT 2!!!!!!
[3778] If after execution of the last ELSE query the IF-construct evaluates FALSE, the following is an example of the output generated to the WAMIL report file:
[3779] !!!!!! QUERY NOT SUCCESSFUL AFTER ATTEMPT 3!!!!!!
[3780] ERRORS: Setting seconds to a negative number or zero will have no effect.
[3781] THEN and ELSE constructs can (in this embodiment of the WAMIL language) be used within IF THEN ELSE constructs. Including a THEN construct not preceded by an IF or THEN, or an ELSE construct not preceded by a THEN or ELSE, will generate a syntax error.
[3782] ALTERS: Wait
[3783] DEFAULT VALUE: Wait is set to 10 upon initial startup, and is of type integer. The WAM:INITIALIZE command also sets this variable to 10.
[3784] SEE ALSO: WAM:INITIALIZE, WAM:WAIT seconds
[3785] EXAMPLE: The following script lines execute a TI command, and then loops up to six times for a COMPLETED output message:
[3786] TI:rst:cell 49, cat 1
[3787] IF:COMPLETED
[3788] THEN:WAIT 10
[3789] ELSE:WAITQUERY 5 TI 6
WAMI LINK Commands
[3790] This section describes the WAMIL scripting language LINK commands which can be used to create a linker script to link WAMIL scripts together for serial or parallel execution. This section also briefly describes the WAM Interpreter Linker.
WAM Interpreter Linker
[3791] Upon execution of a linker script, the WAMI Linker will prompt the user for the option to assign variables for each linked script, or one set of variables for all (in this embodiment of the WAMIL language) the linked scripts. This process occurs when the linker script was executed via command line arguments by using the -link switch.
[3792] The WAMI Linker will search all (in this embodiment of the WAMIL language) linked scripts in a linker script. Linked WAMIL scripts which include WAMI VAR variables, or List declarations, will cause the WAMI Linker to prompt the user for input. If the user has chosen to assign variables to each individual linked script, the WAMI Linker will prompt for each linked script which includes declarations for WAMI VAR variables or Lists.
[3793] If the user has chosen to assign one set of variables for all (in this embodiment of the WAMIL language) linked WAMIL scripts, the WAMI Linker will search through all (in this embodiment of the WAMIL language) the linked scripts first and then prompt the user for only (in this embodiment of the WAMIL language) one set of variables. For example, if some of the linked scripts have a CELLVAR command, the WAMI Linker will only (in this embodiment of the WAMIL language) prompt once for a cell number and assign that cell number to all (in this embodiment of the WAMIL language) the linked scripts which require a cell number to be passed as an argument.
[3794] In the case of List declarations, if more than one linked script declares the same type List, and each List declared differs in size, then the WAMI Linker will prompt the user for input into the largest List. Therefore, the largest List declaration takes precedence.
[3795] Linked scripts can be executed in a serial or parallel fashion. For more details on these modes of execution refer to the WAMI Linker EXEC command. Upon execution of any (in this WAMIL language embodiment) linked script in serial mode, the WAMI Linker will ignore all (in this embodiment of the WAMIL language) WAM:PAUSE commands.
[3796] The WAMI Linker automatically generates a WAMIL report file for the linker script in execution. This WAMIL report file is placed depending on the option selected by the user via the WAMI GUI platform, or by command line execution using the -rpt switch. Linked WAMIL scripts executed also generate their own WAMIL report files which will be placed in the same location as the WAMIL Linker Report file.
[3797] Inclusion of a WAM:DISPLAY command in a linker script causes the WAMI Linker to open a display window to allow viewing of the execution of the linker script. This window is independent of any (in this WAMIL language embodiment) display windows opened by execution of linked WAMIL scripts which include the WAM:DISPLAY command. For differentiating purposes, the WAMI Linker display window color is green with yellow text, as opposed to the standard display window of an executed WAMIL script.
[3798] During execution of any (in this WAMIL language embodiment) linked WAMIL script, any WAMI interface sessions opened during the process will remain open until the last linked script has been executed. Therefore, a TI interface connection, as an example, will remain is essence nailed up until the last linked script which uses the connection has been executed. In this manner connections once established at the start of the first executed linked script will remain accessible during the remainder of the linker script for the execution of all (in this embodiment of the WAMIL language) subsequently linked WAMIL scripts.
[3799] Not all (in this embodiment of the WAMIL language) WAMIL commands are supported by the WAMI Linker. The use of any (in this WAMIL language embodiment) command not supported will cause a syntax error to be generated by the WAM Interpreter and immediate termination of the linker script to occur.
[3800] Below is a list of the WAMIL commands that the WAMI Linker supports:
| WAM:COMMENT | WAM:DATE | WAM:DISPLAY | |
| WAM:ENDTEST | WAM:INITIALIZE | WAM:PRINT | |
| WAM:REPORT | WAM:SPOOL | WAM:TIME | |
| WAM:TIMEOUT | WAM:TRACE | WAM:TRACEOFF | |
| WAM:TRACEON | WAM:WAIT | IF:TEST_EXPR | |
| THENDO: | ELSEDO: | ENDIF: | |
WAMIL SCRIPTOR
[3801] Upon loading a linker script, the Scriptor automatically activates an internal Linker window. All (in this embodiment of the WAMIL language) WAMIL commands not supported by the WAMI Linker are then disabled from the SCRIPTOR pull down menus.
[3802] While the SCRIPTOR Linker window is active only (in this embodiment of the WAMIL language) linked scripts can be loaded. To load a regular WAMIL script a user can (in this embodiment of the WAMIL language) first either save the linker script, or erase it, and then close the Linker window. The opposite also applies, in that a linker script cannot be loaded while a regular WAMIL script is currently loaded into the Scriptor. This ensures that commands which are not supported by the WAMI Linker will not be mistakenly placed into a linker script.
Glossary of WAMI Linker Commands
[3803] A detailed glossary of WAMI linker commands follows. It begins with the linker command, DISPLAYOFF, and ends with the linker command, SCRIPT.
[3804] 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.
DISPLAYOFF
[3805] The text string, DISPLAYOFF, is Linker command.
[3806] PURPOSE: Instructs the WAM Interpreter to suppress all (in this embodiment of the WAMIL language) WAM:DISPLAY commands execution within linked WAMIL scripts.
[3807] SYNTAX: LINK:DISPLAYOFF
[3808] EXAMPLE CALL: LINK:DISPLAYOFF
[3809] DESCRIPTION: The Linker DISPLAYOFF command causes suppression of WAM:DISPLAY commands within linked WAMIL scripts. Upon execution, linked WAMIL scripts which include the WAM:DISPLAY command will not open an xterm display window.
[3810] Upon execution of a linker script, the WAMI Linker first loads the entire script and checks each command for syntax errors prior to initiating execution. At this point, detection of the Linker DISPLAYOFF command causes the WAMI Linker to immediately set a flag to suppress linked WAMIL script WAM:DISPLAY commands execution.
[3811] ERRORS: More than one DISPLAYOFF command in a linker script has no effect.
[3812] ALTERS: None (in this WAMIL language embodiment).
[3813] DEFAULT VALUE: The DISPLAYOFF flag is set to OFF as default.
[3814] SEE ALSO: WAM:INITIALIZE
[3815] EXAMPLE: The following linker script disables the execution of WAM:DISPLAY commands within linked WAMIL scripts:
[3816] WAM:DISPLAY 1
[3817] LINK:DISPLAYOFF
[3818] LINK:EXEC SERIAL
[3819] WAM:DATE
[3820] WAM:TIME
[3821] LINK:SCRIPT HOME jt1234
[3822] LINK:SCRIPT SHARE jt5678
[3823] WAM:ENDTEST
EXEC
[3824] The text string, EXEC, is Linker command.
[3825] PURPOSE: Instructs the WAM Interpreter to execute the following linked scripts in a serial or parallel fashion.
[3826] SYNTAX: LINK:EXEC keyword
[3827] EXAMPLE CALL: LINK:EXEC SERIAL
[3828] DESCRIPTION: The Linker EXEC command instructs the WAM Interpreter to execute the following linked scripts per the keyword specified, until either another EXEC command is executed specifying a different keyword, or the linker script ends by execution of a WAM:ENDTEST command. The keyword provided can be either SERIAL or PARALLEL.
[3829] In SERIAL execution mode all (in this embodiment of the WAMIL language) linked scripts are executed serially, one after another, meaning that execution of a linked script will not begin until the previous linked script executed has completed. It is important to note that serially executed scripts can alter WAM Interpreter variables. For example, if at the end of executing a serially linked WAMIL script which has set the WAMI global CCC variable to the value of 2, the CCC variable will remain at that value during the execution of the next linked script, unless the next linked script alters the value. Thus syntax errors can occur for undefined variables within linked scripts.
[3830] In PARALLEL execution mode linked WAMIL scripts are launched and execute independently of the main Linker script. Therefore, parallel executed scripts complete almost instantaneously and the next WAMIL script is executed immediately. Parallel execution is good for launching WAMIL scripts which exercise a system in the background, for example call processing functions. Parallel execution of a linked WAMIL script does not alter WAM Interpreter variables.
[3831] The Linker EXEC command should proceed any (in this WAMIL language embodiment) linked scripts. If this command is not included in a Linker script the default execution mode is always SERIAL. Although the default is SERIAL, inclusion of the Linker EXEC command allows easier readability of a Linker script, and it is therefore good practice to leave in this command.
[3832] OUTPUT: The LINK:EXEC command used with the SERIAL or PARALLEL keyword does not generate any (in this WAMIL language embodiment) output to the Linker script WAMIL report file. Output is only (in this embodiment of the WAMIL language) generated upon execution of a LINK:SCRIPT command. For more details on this output refer to the LINK:SCRIPT command output section.
[3833] SCRIPTOR: This command cannot be selected from a pull down menu. The Scriptor however, automatically adds this command to the Linker script being generated upon the selection of the first linked script. Subsequent selections of linked scripts do not cause additional Linker EXEC commands to be added, unless the already existing Linker EXEC command has been deleted or moved from the top of the script.
[3834] If a WAM:DISPLAY command exists at the top of the Linker script being generated, the first Linker EXEC command is automatically added under this command.
[3835] Additional Linker EXEC commands can be added by typing the command into the “Current Selected Command” text entry box, and then executing the Insert command button.
[3836] A linked script can (in this embodiment of the WAMIL language) always have a previous Linker EXEC command, or a syntax error will be generated upon saving the script.
[3837] ERRORS: None.
[3838] ALTERS: Linked script execution mode.
[3839] DEFAULT VALUE: Linked script execution mode is set to SERIAL at default, and is not altered unless a Linker EXEC command using the keyword PARALLEL is executed.
[3840] SEE ALSO: LINK:SCRIPT path script_name
[3841] EXAMPLE: The following WAMIL Linker script links together two WAMIL scripts for serial execution:
[3842] WAM:DISPLAY 1
[3843] LINK:EXEC SERIAL
[3844] WAM:DATE
[3845] WAM:TIME
[3846] LINK:SCRIPT HOME jt1234
[3847] LINK:SCRIPT SHARE jt5678
[3848] WAM:ENDTEST
SCRIPT
[3849] The text string, SCRIPT, is Linker command.
[3850] PURPOSE: Instructs the WAM Interpreter to execute the linked WAMIL script, script_name, per the currently set execution mode.
[3851] SYNTAX: LINK:SCRIPT path script_name
[3852] EXAMPLE CALL: LINK:SCRIPT HOME jt1234
[3853] DESCRIPTION: The Linker SCRIPT command instructs the WAM Interpreter to execute the WAMIL script provided by the argument script_name, which is located in the location provided by the argument path, per the currently set execution mode.
[3854] The Linker SCRIPT command links WAMIL scripts together within a Linker script. The execution mode of the linked scripts can be altered by executing a Linker EXEC command prior to any (in this WAMIL language embodiment) execution. For more details refer to the Linker EXEC command.
[3855] The Linker SCRIPT command supports WAM Interpreter path keywords.
[3856] OUTPUT: The following is an example of the output generated to the Linker script WAMIL report file upon execution of a Linker SCRIPT command, in which the currently set execution mode is SERIAL:
[3857] Start Execution HOME WAMIL Script jt1234:
[3858] Upon completion of execution of the serially linked WAMIL script, the following output will be generated:
[3859] End Execution HOME WAMIL Script jt1234:
[3860] The following is an example of the output generated to the Linker script WAMIL report file upon execution of a Linker SCRIPT command, in which the currently set execution mode is PARALLEL:
[3861] Launched HOME WAMIL Script jt1234:
[3862] Output from all (in this embodiment of the WAMIL language) linked scripts executed serially is also added to the Linker script WAMIL report file. Linked scripts also generate their own output, therefore creating their own WAMIL report file. Thus, Linker script WAMIL report files contain all (in this embodiment of the WAMIL language) outputs from all (in this embodiment of the WAMIL language) linked scripts executed serially. The output from linked scripts executed in PARALLEL mode is not included in the Linker script WAMIL report file.
[3863] SCRIPTOR: The Scriptor automatically adds this command to the Linker script being generated upon the selection of a linked script. Depending from which location the WAMIL script is selected, the Scriptor will generate the correct path.
[3864] Additional Linker SCRIPT commands can be added by typing the command into the “Current Selected Command” text entry box, and then executing the Insert command button.
[3865] ERRORS: All errors generated by any (in this WAMIL language embodiment) linked script in serial execution mode is output to the Linker script WAMIL report file and processed in the standard WAM Interpreter manner. That is, the error is displayed in the WAMIL Script Status Display window.
[3866] Critical or fatal errors generated during the execution of a serially linked script causes the execution of such script to be terminated, and the WAMI Linker to proceed with execution of the next linked script, if any.
[3867] Errors generated upon the execution of a linked script in parallel mode are output to the Linker script WAMIL report file.
[3868] ALTERS: Any or all (in this embodiment of the WAMIL language) WAM Interpreter variables, depending on the linked WAMIL script executed.
[3869] DEFAULT VALUE: None (in this WAMIL language embodiment).
[3870] SEE ALSO: LINK:EXEC keyword
[3871] EXAMPLE: Refer to the example provided for the Linker EXEC command.
Acronyms
[3872] The following acronyms are used in this application.
[3873] ROP=Read Only Printer
[3874] SDP=Status Display Page
[3875] TI=Technician Interface
[3876] WAM=Wireless Automation Manager (GUI) Platform
[3877] WAMI=Wireless Automation Manager Interpreter
Conclusion
[3878] The invention may be embodied in other forms without departing from its spirit and essential characteristics. The described embodiments are to be considered only non-limiting examples of the invention. The scope of the invention is to be measured by the appended claims. All changes which come within the meaning and equivalency of the claims are to be embraced within their scope.
Claims
What is claimed is:
1. A computer-readable medium having embodied thereon a script of machine-executable statements to be executed by a machine connected to a system, said system having at least a first interface for interacting with a user, said computer-readable-medium-embodied script causing said machine to generate a second interface for interacting differently with said user than said first interface, said first interface having a first set of commands and a corresponding first syntax, said second interface having a second set of commands and a corresponding second syntax, respectively, the second set being different than the first set and the second syntax being different than the first syntax,
said computer-readable-medium-embodied script comprising:
a sequence of executable statements in which at least two of the executable statements are integration constructs, each of said integration constructs including
a first field, readable by said machine, to identify for said machine and so cause said machine to correspondingly engage one of said first interface and said second interface; and
a second field, readable by said machine, to identify for said machine at least a command from the first or second command set, respectively, for the interface identified in said first field and so correspondingly cause said machine to submit the identified command to the respective engaged interface.
2. The computer-readable-medium-embodied script of claim 1, wherein said first field of said integration construct is separated from said second field by an alphanumeric symbol.
3. The computer-readable-medium embodied script of claim 2, wherein said alphanumeric symbol is a colon.
4. The computer-readable-medium-embodied script of claim 1, wherein said first interface also includes a set of parameters that can be passed with said first set of commands, respectively, and said second field includes at least one parameter corresponding to said command contained therein.
5. The computer-readable-medium-embodied script of claim 1, wherein said system is a wireless communication network and said first interface is one of the TIpdunix (TI) interface and the Status Display Page (SDP) interface.
6. The computer-readable-medium-embodied script of claim 5, wherein said system comprises a third interface having a third set of commands and a corresponding third syntax, said first is said TI Interface and said third interface is said SDP interface.
7. The computer-readable-medium-embodied script of claim 1, wherein said second interface is the Wireless Application Manager (WAM) interface.
8. The computer-readable-medium-embodied script of claim 1, wherein said sequence of executable statements further includes at least one IF-THEN-ELSE decisional construct.
9. The computer-readable-medium-embodied script of claim 1, wherein said first field of said integration construct is a header for said second field.
10. An integration construct data structure readable by a machine, said machine operating upon commands from at least a first interface and a second interface, the first domain having a first command set and a corresponding first syntax, the second domain having a second command set and a corresponding second syntax, the second set being different than the first set and the second syntax being different than the first syntax, said integration construct associating a command with an interface where said command is valid, said integration construct comprising:
a first data object, readable by said machine, to identify for said machine at least a command to be executed; and
a second data object, readable by said machine and linked to said first data object, to identify for said machine one of said first interface and said second interface as the interface in which the identified command of said first data object is valid, contents of the first and second data object causing said machine to correspondingly engage the identified interface and submit the identified command to the engaged interface.
11. The integration construct data structure of claim 10, wherein said first data object also identifies a parameter to be operated upon by said command in said first data object.
12. The integration construct data structure of claim 10, wherein said second data object is linked to said first data object by an alphanumeric symbol.
13. The integration construct data structure of claim 12, wherein the alphanumeric symbol is a colon.
14. The integration construct data structure of claim 10, wherein the first interface is a first user interface to a system and the second interface is a second user interface to the same system, the second interface providing different interaction with the user than the first interface.
15. The integration construct data structure of claim 14, wherein said system is a wireless communication network and said first interface is one of the TInpdunix (TI) interface and the Status Display Page (SDP) interface.
16. The integration construct data structure of claim 14, wherein said second interface is the Wireless Application Manager (WAM) interface.
17. A method of parsing an executable statement, said executable statement being readable by a machine, said machine operating upon commands for use with one of at least a first interface and a second interface, said first interface having a first command set and a corresponding first syntax, said second interface having a second command set and a corresponding second command set, the first set being different than the second set and the first syntax being different than the second syntax, said method comprising:
examining said executable statement to identify one of at least said first interface and said second interface as the interface for which a command embedded in said executable statement is to be parsed;
examining said executable statement to identify at least said command; and
parsing the identified command according to the respective command set, and the respective syntax, of the identified interface.
18. The method of claim 17, further comprising examining said executable statement to identify a parameter to be operated upon by said command.
19. The method of claim 17, wherein the first interface is a first user interface to a system and the second interface is a second user interface to the same system, the second interface providing different interaction with the user than the first interface.
20. The method of claim 19, wherein said system is a wireless communication network and said first interface is one of the TInpdunix (TI) interface and the Status Display Page (SDP) interface.
21. The method of claim 19, wherein said second interface is the Wireless Application Manager (WAM) interface.
22. The method of claim 19, wherein the executable statement includes an integration construct, the integration construct including
a first field, readable by said machine, to identify for said machine and so cause said machine to correspondingly engage one of said first interface and said second interface, and
a second field, readable by said machine, to identify for said machine at least a command from the first or second command set, respectively, for the interface identified in said first field and so correspondingly cause said machine to submit the identified command to the respective engaged interface.
23. The method of claim 22, wherein said first field of said integration construct is separated from said second field by an alphanumeric symbol.
24. The method of claim 23, wherein said alphanumeric symbol is a colon.
25. The method of claim 22, wherein said first interface also includes a set of parameters that can be passed with said first set of commands, respectively, and said second field includes at least one parameter corresponding to said command contained therein.
26. The method of claim 22, wherein said first field of said integration construct is a header for said second field.
Patent Citations (1)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US6311320(B1) | 2001-10-01 | Jibbe | Examiner |
Non-Patent Literature (6)
- Jannink et al., “Efficient and Flexible Location Management Techniques for Wireless Communication Systems”, ACM, Oct. 1997.Applicant
- Francez et al., “Script: A communication Abstraction Mechanism”, ACM, pp.: 213-227.Applicant
- Louis lacona, “Take Command”, Linux Journal, vol. 1999, Issue: 62es, pp. 1-6, Jun. 1999.Applicant
- Brewer et al., “A Network Architecture for Heterogeneous Moblile Computing”, IEEE, Pages: 8-24, Oct. 1998.Applicant
- Aho et al., “Compilers, Principles, Techniques, and Tools”, Addison-Wesley Publishing Company, pp: 25-48, 1988.Applicant
- Hodes et al., “Composable ad-hoc mobile services for universal interaction”, ACM, pp.: 1-12, Sep. 1997.Examiner