The summary report format provides an easy way for message and pattern matches to be checked.

When you specify the summary option with no operating mode option, 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 patterns matched the message. The rest of the line contains the text of the input message.

Line # Matched Message text
   1       1   LOAD TAPE REEL XYZ123
   2       1   CMS ABORT FIN
   3            KPIPER*MSG: ARE WE THERE YET?
   4       1   ALL HOSTS IN THE SHARED ENVIRONMENT ARE GOING DOWN NOW!!!! +

For CP-AMS and SMART AMS databases, the actions generated by AMS can be displayed by specifying attended, casual, or unattended along with the summary option.  For SP-AMS databases, the actions generated can be displayed by specifying normal with the summary option. If multiple patterns match a message, only the action information for the first pattern matched is reported in the summary output. If the selected options are summary and casual, output like the following might be created:

Line #  Matched  Message text
1      1    LOAD TAPE REEL XYZ123
               ALARM      : 0
2      1    CMS ABORT FIN
              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.

Once a potential problem has been discovered and a quick glance at the available information does not uncover an obvious solution, proceed by examining the long report format.