The Verify function in ADBM and the VADB utility help you test the pattern-matching and action generation capabilities of an autoaction database. With VADB you can
Check an autoaction database for internal consistency.
See that each message is matched.
Look for unexpected matches.
Check an autoaction database against test data.
Check an autoaction database against historical data.
Understand why a pattern matches a message.
By using an input file of messages along with an autoaction database, VADB can
Verify that the messages match, or do not match the autoaction database patterns you intended.
Identify messages that match a single pattern.
Identify messages that match multiple patterns. All patterns are listed in match order so you can predict AMS run-time behavior.
Provide an exceptions listing of messages that do not match the specified number of patterns.
Display the actions, by operation mode, which result from each pattern match.
VADB accepts the following types of message input files. See Figure 6–1.
BADB syntax files
Operations Sentinel log files
Straight message text files
VADB has two primary output formats, a summary and a long listing of pattern-match information. Summary output format is the default. Optionally, VADB can provide additional action information for either output format.
VADB can generate database activation and deactivation messages, simulating the internal messages that AMS generates, and the automation start and stop messages produced by SP‑AMS. The activation message is the first message processed by the database and the deactivation message is issued after the entire input file of messages has been processed. Two VADB call line options are available to control the generation of these AMS internal messages.
VADB uses an autoaction database generated by ADBM or BADB for pattern matching and action generation. The information contained in the message input files is used to create the messages and message characteristics. These messages are then matched against the patterns in the autoaction database.
Before using VADB to verify your database, you must first use ADBM or BADB to build a database and again later to apply any changes.
Calling VADB
From the Windows Start menu, select Programs, Operations Sentinel x.y.z, Automation Tools, Verify AMS Database.
A command prompt window appears, positioned to the folder containing the VADB program (installation-folder\spo\bin). Abbreviated instructions for calling VADB are displayed in this window.
VADB has a call line similar to BADB and DADB. By default, all output is formatted for viewing in an 80-column window; however, VADB can format output for line lengths from 70 to 3000 characters. VADB can also redirect output to a file for further reduction and analysis at your site.
Enter the following at the command prompt:
vadb [ option... ] database-name [ infile... ]
where option can be any of these:
-a
[SP-AMS]
generates the database activation message followed by the automation initialization message, simulating the initial activation performed by SP‑AMS when it is started.
[CP-AMS SMART AMS]
generates a database activation message simulating the initial activation that CP‑AMS performs when the console is booted and acquired by the OS 2200 system.
VADB processes these messages after it opens the database, but before it processes any messages from the input files. See Section 7.
-c[nnnn] [t|w]
sets the maximum output line length to the number that follows -c. Without this option, VADB truncates the text at 80 columns. This value must be between 70 and 3000. If you specify this option with no value, 3000 is assumed.
The -c option also controls whether VADB truncates a line or continues (wraps) text to the next line. Specify t (for truncation) or w (for wrapping) after -c. The default is to truncate lines. If a line is truncated, a plus sign (+) is placed at the point where the text is truncated. If a line is wrapped, a dotted arrow (…>) precedes the continued text on the next line.
Exceptions: Error messages are always displayed in their entirety. Matching token lines in long output format are always truncated, and truncated at the maximum output line length. To see more of the token text, increase the number of columns allowed by the -c option.
-d
[SP-AMS]
generates an automation termination message followed by a database deactivation message, simulating the database deactivation SP-AMS performs when a database is deactivated through automation control. See Section 7.
[CP-AMS]
generates a database deactivation message. For CP-AMS, this simulates the database deactivation CP-AMS performs when a database is activated using OS 2200 Console View. For SMART AMS, this simulates the database deactivation SMART AMS performs when the database is deactivated using the AMS Utility. This message is processed after all messages from the input file are processed.
-e
echoes the call line (you must specify this option first); for information only.
-fformat
denotes the format of the input file. If a format is not specified, BADB is the assumed input format.
Valid values for format are BADB (for a BADB syntax file), SPOLOG (for an Operations Sentinel log file), and TEXT (for straight message text, as seen on a system console).
-hhostname
[SP-AMS]
specifies the name of the host system whose automation is being verified. If a host name is not specified using the –h option or in the input file, VADB uses the “host” as the default host name.
-in
sets the level of information messages to display, where n is 0, 1, or 2 (0 being the least information, and 2 being the most information). See Appendix E for the different information messages. If you omit this option, the default level of 1 is used.
-l[a][c][u][n]
denotes long output format, which displays each input message and its characteristics, along with detailed message and pattern information for each matched message.
[SP-AMS]
To obtain action information for each pattern match, specify the n argument to indicate normal mode.
For an SP-AMS database, you cannot specify the arguments a, c , or u with the –l option.
[CP-AMS]
To obtain action information for each pattern match, specify one or more optional operation modes (attended, casual, or unattended). For each operation mode that you specify, the actions defined for that mode are displayed for each pattern match. For example, if you specify a, all actions to be performed in attended mode for each pattern match are displayed. You can specify any combination of the three operation modes.
For a CP-AMS or SMART AMS database, you cannot specify the n argument with the –l option.
-o
denotes single-pattern-match mode. VADB in single-pattern-match mode reports either the first pattern matched for each input message, or indicates that no match was found.
-p<partition-name>.<console-name>
[CP-AMS]
sets the partition name and console name for _PARTNAME and _CONSNAME variables. Both the partition and console name are expected and that the partition name is separated from the console name by a period “.”. Valid partition and console names consist of alphabetic characters (a – z) and numeric digits. Both the names are automatically uppercased by VADB.
-s[a|c|u | n]
denotes summary output format, which displays one line for each input message. This line includes the line number of the message in the message file, match notification (number of matches, if any) and the message text. The match notification is blank if there is no match for the input message.
Summary output is the default format, when you do not specify either the -l or -s option.
[SP-AMS]
To obtain action information for each pattern match, specify the n argument to indicate normal mode.
For an SP-AMS database, you cannot specify the arguments a, c , or u with the –s option.
[CP-AMS]
To obtain action information for each pattern match, specify an optional operation mode (attended, casual, or unattended). For the operation mode that you specify, the actions defined for that mode on the first pattern match are displayed. For example, if you specify a, all actions to be performed in attended mode for that pattern match are displayed. You can specify only one operation mode with the –s option.
For a CP-AMS or SMART AMS database, you cannot specify the n argument with the ‑s option.
-wn
sets the level of warning messages to display, where n is 0, 1, or 2 (0 being the least information and 2 being the most information). See Appendix E for the different warning messages. If you omit this option, the default level of 1 is used.
-xn
denotes the exceptions mode. The exceptions mode only reports irregularities in the matching of messages and patterns. Input messages that successfully match exactly n number of patterns (where n is a number from 0 to 9) are not reported. Any input message matching less than n or greater than n number of patterns is reported. The default value for n is 1.
database-name
is the name of the automation database. If you do not include an extension, VADB checks first for a CP-AMS database (.acp), a SMART AMS database (.ams), and then for an SP-AMS database (.asp). If there are databases with the same base name (for example, both dbl.acp and dbl.asp), you must specify the extension .acp to force VADB to process a CP-AMS database or .asp to force VADB to process an SP-AMS database.
[SP-AMS]
a legal database name is 1 to 128 characters, and cannot include slashes, backslashes, and spaces. SP-AMS database names are case sensitive.
AMS uses the database name as part of the file name for the database. When you define your database name, use only characters that are valid in a file name.
[CP-AMS]
a legal database name is 1 to 255 characters, and cannot include characters not allowed in a file name. CP-AMS database names are case-insensitive.
[SMART AMS]
a legal database name is 1 to 8 characters (letters, digits, and hyphens). SMART AMS database names are case insensitive.
infile
is the name of a file containing input messages. If you do not specify this file, VADB uses a default input file. The default base name of this file is the same as database-name. The extension of this default file is determined by the input format, as shown in the following table. You may specify multiple message input files, provided all have the same format.
| Input Format | Extension |
|---|---|
| BADB | .bld |
| SPOLOG | .slg, .spo |
| TEXT | .txt |
Input Formats
VADB accepts three different input formats, allowing flexibility when creating database test environments. The selection of the input format is controlled through the
-fformat option.
The following subsections explain the different types of input formats: BADB source files, Operations Sentinel log files, and straight message text files.
BADB Source Files
BADB source files are used to generate an autoaction database. Using these files as message input can also provide immediate feedback when verifying an AMS database. Potential problems or conflicts are identified when input text from a BADB MESSAGE command does not match the associated pattern definition or any other pattern in the database.
If you maintain multiple BADB source files to create and manage autoaction databases, using these files with VADB is especially helpful. For example, you could have a base source file for patterns that apply to every host system and individual host-specific source files that define host-specific patterns. When the base file and a host-specific file are blended to create an autoaction database, the chances of conflict increase because they generally evolve independently. Running the source files against the blended database can provide early detection of such problems.
VADB examines the DEFINE, MESSAGE, TYPE, and INSTANCE commands in each pattern in the input source file to determine the appropriate message text, message type, sender type, and instance type for each message it generates. CONSTRAINT commands are ignored. VADB assumes the same defaults as BADB if one or more of the various types are not specified.
[CP-AMS]
VADB also examines the TOKEN commands in each pattern looking for a RUNID token. If a RUNID token is specified in a pattern definition, it is used as the message run-id for the message generated for that pattern. If a RUNID token is not specified, a null string is used as the message run-id for that message. In this case, the generated message can only match a database pattern that does not have a RUNID defined.
[SP-AMS]
VADB examines the TOKEN commands in each pattern looking for a HOSTID token. If a HOSTID token is specified in a pattern, it is used as the hostname for the message generated for that pattern. If no HOSTID token is specified for a pattern, the hostname specified with the –h option is used as the hostname for each message. If neither the –h option nor a HOSTID token is specified, VADB uses “host” as the hostname.
Using VADB with BADB source files as input verifies the following conditions:
Database patterns do not have conflicts.
Any size autoaction database can have conflicts among its patterns. VADB helps to point out which patterns in the database may match differently than originally intended.
Database patterns match all intended messages.
Input messages that are not intercepted by the autoaction database are easily detectable and clearly marked in the output.
Note that VADB does not change the input message text before using it to match patterns in the generated database. If you are verifying a database against the BADB source file that was used to create it and masking is specified in the source file, the input message text may not match its own pattern in the generated database. See the following example.
The following BADB pattern is an example that includes masking:
DEFINE "A" 1 MESSAGE "ALL \*2\HOSTS IN THE SHARED SYSTEM ARE GOING DOWN NOW" TYPE PRIVILEGED-EXEC OTHER INSTANCE PRIMARY PRIORITY 128 TOKEN KEYWORD 10 "NOW" TOKEN FIXED 8 "GOING" TOKEN FIXED 5 "SHARED" TOKEN FIXED 1 "ALL" TOKEN MASKED 2 "\*2\HOSTS" ACTION ALL ALARM "0" END
When the masked token "\*2\HOSTS" from the generated message is compared to the MESSAGE text, they do not match because the pattern is looking for up to two characters preceding the characters HOSTS, while the generated message text has four characters: \*2\.
Similarly, if a generated message has a token that is 8 characters long because a masked token is specified as "\*1\\*5\" , which matches 6 characters, the input message does not match its own pattern in the database.
Operations Sentinel Log Files
Operations Sentinel log files are available as input to VADB to any site using Operations Sentinel to log messages from managed host systems.
The location of the logging folder on the Operations Sentinel server is specified during installation of Operations Sentinel. You can determine the name of this folder from the Help About window of Operations Sentinel Console. For more information concerning log files, see the online Help, or the Operations Sentinel Administration and Configuration Guide.
Comparing a compiled autoaction database against an Operations Sentinel log file from an actual system can provide the database administrator with an accurate assessment of which messages will be handled properly by the autoaction database on a daily basis.
[SP-AMS]
VADB processes each line in the log file as a message. It strips off the message source, message type, and time of the message at the front of the line. The rest of the line is used as the message to be processed. The host name you specify with the –h option is used as the source of each message in the log file. VADB uses “host” as the host name if you do not specify the –h option.
[CP-AMS]
VADB sets the type of each message according to information in the message. VADB assumes a default sender type of ANY-SENDER and a default instance type of ANY-INSTANCE for input messages from an Operations Sentinel log file.
Straight Message Text Files [SP-AMS]
Each line of text in the input file is assumed to be a message. VADB does not make any assumptions about each message.
The host name you specified with the –h option is used as the source of each message in the input file. VADB uses “host” as the host name if you did not specify the –h option.
VADB assumes that all messages have a message type of OTHER and a sender type of ANY-SENDER. An instance type is not assumed because it does not apply to SP-AMS databases.
Straight Message Text Files [CP-AMS]
This type of input is available from an OS 2200 system log file after it has been processed by the Log Analyzer (LA). Not only does this format help accurately assess the validity of a database against the actual messages provide by a system, it also is the easiest input format to create manually.
If an input message contains a valid read-and-reply number, VADB assumes the message type is READ-AND-REPLY. If an input message does not contain this number, VADB searches for matches with message types of OTHER, CONTINUOUS-DISPLAY, and SCF.
VADB assumes a default sender type of ANY-SENDER and a default instance type of ANY-INSTANCE for each message.
Use the following rules to create messages in this format:
Prefix read-and-reply messages with a single numeric digit followed by a hyphen:
0-ANSWER WITH REEL NO ON 7-A2 E,REEL 1-ARE WE THERE YET û YN
Prefix non-Exec messages with a 6-character, left-justified, space-padded field containing the run-id of the message sender followed by an asterisk as the seventh character and then the message text:
RUNABC*IS ANYONE AT THE CONSOLE? FTYBR *FOLLOW THE YELLOW BRICK ROAD
Any combination or absence of rules 1 and 2 is also allowed:
0-RUNABC*IS ANYONE AT THE CONSOLE? LOAD SS1107 7A8 IBACKUP1 - 2 ROLBAK
Note: CONTINUOUS-DISPLAY message types should not include a run-id.
Multiple Message Input Files
VADB allows you to process messages from multiple input files. The files must all have the same input format (BADB, SPOLOG, or TEXT).
The database remains active during processing of all input files. For example:
vadb -a -d -fBADB dbx db1.bld db2.bld db3.bld
Here, VADB activates the database dbx and then processes the database activation message (-a option), files db1.bld, db2.bld, db3.bld, in that order and then the database deactivation message (-d option).
Output Formats
VADB has two primary output formats. One provides quick message match notification. The second provides more detailed message and pattern matching information. Both output formats are based on an 80-column display, unless you indicate otherwise with the ‑c option.
Table 6–1 shows how much output VADB produces for each option for a representative example.
Table 6–1. VADB Output
| Processor Cell | Size of Verification Report |
|---|---|
| vadb –s –x1 xyz | 17 Lines |
| vadb –s xyz | 71 Lines |
| vadb –sc xyz | 389 Lines |
| vadb –lacu xyz | 2975 Lines |
Actions on variables (SET, RESET, CREATE, and DESTROY) and conditional logic actions (IF, ELSE, and ELSEIF) associated with the first pattern to match a message are executed.
All pattern matching is performed before any actions are executed so the actions executed as a result of the first pattern match do not affect the constraints on other patterns for this message. For each additional pattern that matches a message, the associated actions are displayed but are not executed.
Conditional logic actions are displayed in a nested format. Each level of nested conditional construction is indented, up to eight levels for summary output, and up to fifteen levels for long output. Nested conditional constructions beyond these levels are displayed directly beneath each other.
[CP-AMS]
In long output format, actions in attended mode are always executed when attended mode and any other modes are specified, actions in casual mode are executed if attended mode is not specified, and actions in unattended mode are executed only if no other operating modes are specified. Although the actions for the other specified modes are not executed, they are displayed.
For example, if you have specified attended, casual, and unattended modes using the option ‑lacu on the command line, VADB executes the actions for attended mode but displays the actions for casual and unattended mode regardless of the order in which you specified the modes. If you have specified casual and unattended modes only (‑lcu), VADB executes the actions for casual mode but displays the actions for unattended mode regardless of the order in which you specified the modes.
Summary Output Format
The summary output format provides an easy way for message and pattern matches to be checked. If you specify no output format, the -s option with no operating mode is assumed.
When you specify the -s option with no additional arguments, the output looks like the following example. The line number of the message in the input file is in the first column. The second column contains the number of patterns that matched the input message and is left empty in cases where no pattern matched the message. The rest of the line contains the text of the input message.
[SP-AMS Examples]
Line # Matched Message Text 142 1 Console Login: 187 1 Password: 685 1 MI002: Deactivating SP-AMS database <db-name> reque + 777 ALARM on/off 815 1 Log message
The actions generated by SP-AMS can be displayed by specifying n (normal) as an argument to the -s option. If multiple patterns match a message, only the action information for the first pattern matched is reported in the summary output. If the command line contains the option -sn, output like the following might be created:
Line # Matched Message Text 142 1 Console Login: COMMAND : console 187 1 Password PASSWORD : <password text> 685 1 MI002: Deactivating SP-AMS database <db-name> reque + IF (^\_TOKEN8[1,8]\ = "OPERATOR" & ?Databases:_DB + ENDIF 777 ALARM on/off 815 1 Log message EVENT-REPORT : TYPE = LG | CLASS = ansi_x3.64_hos +
After you discover a potential problem and an examination of the available information does not uncover an obvious solution, proceed by examining the long output format.
[CP-AMS Examples]
Line # Matched Message Text
1 1 LOADTAPEREELXYZ123
2 1 CMS ABORT FOADTAPEREELXYZ123
2 1 CMS ABORT FIN
3 KPIPER*MSG: ARE WE THERE YET?
2 1
ALL HOSTS IN THE SHARED ENVIRONMENT ARE GOING DOWN NOW!!!! +
You can specify the actions generated by CP-AMS by specifying a (attended), c (casual), or u (unattended) as an argument to the -s option. If multiple patterns match a message, only the action information for the first pattern matched is reported in the summary output. If the command line contains the option -sc, output like the following might be created:
Line # Matched Message Text
1 1 LOAD TAPE REEL XYZ123
ALARM :0
2 1 CMS ABORTFIN
ALARM :12
DISPLAY:\_TOKEN1\MUST BE RESTARTED
----------->CMS MUST BE RESTARTED
If an action contains substitution, a second line of output is displayed for the action. This second line of output consists of an arrow ( ----------->) followed by the expanded action text. In action output, substitution is not resolved for expressions. Therefore, this second line of output is not displayed for actions that contain substitution in an expression.
Long Output Format
This format provides considerable information about each message and the patterns it matched. The -l option and arguments, if specified, generate the following:
Input message and line number at which the message can be found in the input file
Input message characteristics
Detailed pattern-match information
Optional action information
When you specify the -l option without additional arguments, the output looks like the following. The input message information is followed by the pattern-match information. Lines of equal signs separate the processed results of each input message, and a broken line of hyphens indicates the start of the pattern-match information.
[SP-AMS Examples]
================================================
Message: Console Login:
Input line # : 142
Host-id : DP23
Sender type : ANY-SENDER
Message type : OTHER
---- ---- ---- ---- ---- ---- ---- ---- ---- ---
Match: group= LOGIN-MSGS number= 1
DB Text: Console Login:
Message total token count: 2
Pattern total token count: 2
Database Input
Pattern Token Message Token
------------- -------------
Host-id : DP23 DP23
Token 1: \?1\ONSOLE CONSOLE
Token 2: \?1\OGIN: LOGIN:
================================================
Specifying the n argument on the –l option displays the actions generated by SP-AMS.
If more than one pattern matches an input message, a short line of ten hyphens separates each set of pattern-match information. When multiple patterns are matched, the first information displayed is the pattern that would be matched at run time.
The actions that are generated by SP-AMS can be displayed by
specifying n (normal) as an argument to the -l option. If the
command line contains the option -ln, the output might look like
the following:
================================================
Message: SINGLE POINT AMS AUTOMATION
STARTED USING DATABASE <db> FOR +
Input line # : 270
Host-id : RSCSF?
Sender type : ANY-SENDER
Message type : OTHER
---- ---- ---- ---- ---- ---- ---- ---- ---- --
Match: group= C2 number= 2
DB Text: SINGLE POINT AMS AUTOMATION
STARTED USING DATABASE <db> FOR +
Message total token count: 11
Pattern total token count: 11
Database Input
Pattern Token Message Token
------------- -------------
Host-id : RSCSF\?1\ RSCSF?
Token 1: SINGLE SINGLE
Token 2: POINT POINT
Token 3: AMS AMS
Token 4: AUTOMATION AUTOMATION
Token 5: STARTED STARTED
----------
Match: group= C2 number= 1
DB Text: SINGLE POINT AMS AUTOMATION
STARTED USING DATABASE <db> FOR +
Message total token count: 11
Pattern total token count: 11
Database Input
Pattern Token Message Token
------------- -------------
Token 1: SINGLE SINGLE
Token 2: POINT POINT
Token 3: AMS AMS
Token 4: AUTOMATION AUTOMATION
Token 5: STARTED STARTED
======================================================
If you specify the -l option, with or without additional arguments, and no pattern is matched, the output looks like the following:
=========================================================== Message: runid ABORT FIN Input line #: 2 Sender type : PRIVILEGED-EXEC Message type : OTHER Instance type: PRIMARY ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- No match found! ===========================================================
If any of the text strings contained in the output cannot be displayed in the formatted output in their entirety and you have specified line truncation, a plus sign (+) is placed in the last column of the output field. This indicates that there is text continued, but it does not fit on the output line.
===========================================================
Message: ALL HOSTS IN THE SHARED ENVIRONMENT ARE GOING DOWN NOW!!!!!!!!!! +
Input line #: 32
Sender type : PRIVILEGED-EXEC
Message type : OTHER
Instance type: PRIMARY
---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ----
Match: group= A number= 1
DB Text: ALL HOSTS IN THE SHARED ENVIRONMENT ARE GOING DOWN NOW!!!!!!!!!! +
Message total token count: 10
Pattern total token count: 10
Database Input
Pattern Token Message Token
------------- ------------
Token 1: ALL ALL
Token 2: HOSTS HOSTS
Token 5: SHARED SHARED
Token 8: GOING GOING
Token 10: NOW!!!!!!!!!!!!!!!!!!! + NOW!!!!!!!!!!!!!!!!!!!!! +
Attended Mode Actions:
Casual Mode Actions:
Unattended Mode Actions:
ALARM : 12
===========================================================
The following is long output from a conditional construction nested to eight levels.
Verify AMS DataBase (VADB) -- x.y.z (x.y.z--) -- xx/xx/xxxx
Message: keyin* KEYIN NOT REGISTERED*arg1 arg2 arg3 arg4 arg5 arg6 . . .
Input line # : 2
Sender type : PRIVILEGED-EXEC
Message type : OTHER
Instance type: PRIMARY
---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ----
Match: group= MACROS number= 1
DB Text: keyin* KEYIN NOT REGISTERED*arg1 arg2 arg3 arg4 arg5 arg6 . . .
Message total token count: 12
Pattern total token count: 12
Database Input
Pattern Token Message Token
--------- -------------
Token 2: KEYIN KEYIN
Token 3: NOT NOT
Token 4: REGISTERED*\?1\\*25\ REGISTERED*ARG1
Attended Mode Actions:
SUPPRESS
TCOMMAND : \_TOKEN1 {*} 1\ \_TOKEN4 {*} 2\
-------------> KEYIN ARG1
IF _TOKENS > 4
TCOMMAND : \_TOKEN1 {*} 1\ \_TOKEN5\
-------------> KEYIN ARG2
IF _TOKENS > 5
TCOMMAND : \_TOKEN1 {*} 1\ \_TOKEN6\
-------------> KEYIN ARG3
IF _TOKENS > 6
TCOMMAND : \_TOKEN1 {*} 1\ \_TOKEN7\
-------------> KEYIN ARG4
IF _TOKENS > 7
TCOMMAND : \_TOKEN1 {*} 1\ \_TOKEN8\
-------------> KEYIN ARG5
IF _TOKENS > 8
TCOMMAND : \_TOKEN1 {*} 1\ \_TOKEN9\
-------------> KEYIN ARG6
IF _TOKENS > 9
TCOMMAND : \_TOKEN1 {*} 1\ \_TOKEN10\
-------------> KEYIN .
IF _TOKENS > 10
TCOMMAND : \_TOKEN1 {*} 1\ \_TOKEN11\
-------------> KEYIN .
IF _TOKENS > 11
TCOMMAND : \_TOKEN1 {*} 1\ \_TOKEN12\
-------------> KEYIN .
IF _TOKENS > 12
DISPLAY: AMS ignored arguments after \_TOKEN12\!
-------------> AMS ignored arguments .after!
ENDIF
ENDIF
ENDIF
ENDIF
ENDIF
ENDIF
ENDIF
ENDIF
ENDIF
ENDIF
===========================================================
END of Verify AMS Database (VADB) Errors - 0 Warnings û 0
[CP-AMS Examples]
===========================================================
Message: runid ABORT FIN
Input line #: 2
Sender type : PRIVILEGED-EXEC
Message type : OTHER
Instance type: PRIMARY
---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ----
Match: group= INST number= 2
DB Text: RUNABC ABORT FIN
Message total token count: 3
Pattern total token count: 3
CONSTRAINT : \_TOKEN3\ = "FIN"
Database Input
Pattern Token Message Token
------------- ------------
Token 1: RUN\*3\ RUNID
Token 2: ABORT ABORT
---------
Match: group= A number= 2
DB Text: runid ABORT FIN
Message total token count: 3
Pattern total token count: 3
Database Input
Pattern Token Message Token
------------- ------------
Token 2: ABORT ABORT
Token 3: FIN FIN
===========================================================
If more than one pattern matches an input message, a short line of ten hyphens separates each set of pattern-match information. When multiple patterns are matched, the first information displayed is the pattern that would be matched at run time.
The actions that are generated by CP-AMS can be displayed by specifying a (attended), c (casual), u (unattended), or any combination of the three as arguments to the -l option.
If the command line contains the option -lacu, the output might look like the following:
=========================================
Message: runid ABORT FIN
Input line #: 2
Sender type : PRIVILEGED-EXEC
Message type : OTHER
Instance type: PRIMARY
---- ---- ---- ---- ---- ---- ---- ----
Match: group= INST number= 2
DB Text: RUNABC ABORT FIN
Message total token count: 3
Pattern total token count: 3
CONSTRAINT : \_TOKEN3\ = "FIN"
Database Input
Pattern Token Message Token
------------- ------------
Token 1: RUN\*3\ RUNID
Token 2: ABORT ABORT
Attended Mode Actions:
Casual Mode Actions:
Unattended Mode Actions:
ALARM : 12
---------
Match: group= A number= 2
DB Text: runid ABORT FIN
Message total token count: 3
Pattern total token count: 3
Database Input
Pattern Token Message Token
------------- ------------
Token 2: ABORT ABORT
Token 3: FIN FIN
Attended Mode Actions:
ALARM : 0
Casual Mode Actions:
ALARM : 0
Unattended Mode Actions:
ALARM : 0
===================================================
If an action contains a substitution, a second line of output is displayed for the action. This second line of output consists of an arrow ( ----------->) followed by the expanded action text. In action output, substitution is not resolved for expressions. Therefore, this second line of output is not displayed for actions that contain substitution in an expression.