Coding Each AOF Rule Type › Message Rules › )MSG—Event Specifier of MSG Rules

)MSG—Event Specifier of MSG Rules

The following is the format for coding the MSG event definition section:

)MSG msgidspec [MLWTO] [AUTO | NOAUTO] [NOOPSLOG] [SUPPRESS]

AUTO

(Optional) Sets the msg.autoflag variable of a multi-line message to 1. Only valid if the MLWTO optional keyword is used. AUTO and NOAUTO are mutually exclusive.

msgidspec

Specifies the message ID. Follow these guidelines when specifying the character string:

• Specify one to ten characters of the message ID.
• The string cannot contain embedded blank spaces.
• If the MLWTO keyword is not specified, you can use the wildcard (*) character. For example,
  • IEC* matches IEC234, IECTL56, IEC6705, and any other event identifier containing an IEC prefix.
  • IEC*05 matches IEC05, IECD05, IECDE05, and so on.
  • *05 matches any message ending with 05.* alone matches all messages.
• Lowercase letters are acceptable, but the AOF converts them to uppercase for event testing.

MLWTO

(Optional) To be specified when interrogating a multi-line message and each data line is needed to be stored in stemmed msg.text.n variables for further manipulation. Rule will process after the end-line of the multi-line message is received. Wildcarding is not allowed if utilizing this keyword. Therefore the msgidspec must be that of the complete message ID of the multi-line message. For more information see Execution Considerations for Msg Rules for details on processing multi-line messages.

NOAUTO

(Optional) Sets the msg.autoflag variable of a multi-line message to 0. Only valid if the MLWTO optional keyword is used. NOAUTO and AUTO are mutually exclusive.

NOOPSLOG

(Optional) Prevents a message (specified by msgidspec) from appearing in the OPSLOG. Specify the NOOPSLOG option before you enable a rule.

SUPPRESS

(Optional) Only valid if the MLWTO optional keyword is utilized, and causes the multi-line message to be suppressed.

More information:

Code and Debug AOF Rules