The long report format provides a considerable amount of information about each message and the patterns it matched. The long report format generates the following:
Input message and the line number on which it can be found in the input file
Input message characteristics
Detailed pattern-match information
Optional action information
For CP-AMS and SMART AMS databases, the actions generated by AMS can be displayed by specifying attended, casual, or unattended along with the long option. For SP-AMS databases, the actions generated can be displayed by specifying normal with the long option.
If the selected options are summary and long, output like the following might be created. The input message information is displayed first, followed by the pattern-match information. The lines of equal signs separate the processed results of each input message, and the broken line of hyphens indicates the start of the pattern-match information.
===========================================================
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, each set of pattern-match information is separated from the next by a short line of ten hyphens. When multiple patterns are matched, the first pattern-match information displayed is the pattern that would be matched at run time by AMS.
The actions that are generated by AMS can be displayed by specifying attended, casual, unattended, or any combination of the three. For example, if all three are specified with long output format, 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.
If you specify the long output format and no pattern match is found, 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 line truncation is in use, a plus sign (+) is placed in the last column of the output field. This indicates that the text is continued, but 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) -- xRx (x.x) -- xx/xx/xx
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