NET/MASTER RMS Management and Operations Guide

Adding a Message Action Rule
Creating and Developing Rulesets and Rules
5–22 115415 NonStop NET/MASTER RMS Management and Operations Guide
Specifying the Message ID. RMS regards the first word of a message as the message ID.
You use a message ID as a criterion by specifying a value in the Message ID field (for
example, NNM0001). The field accepts up to 32 characters. Use the wild-card
characters, question mark (?) and asterisk (*), to match multiple messages. An asterisk
must follow at least one character and must be the last character in the field. A
question mark must follow at least one character and can appear in any other position
in the field. Use a variable to allow the message ID criterion to change dynamically
(for example, you can set the value of the variable by using another rule). If you use a
variable and the message ID is also the primary trigger, the rule becomes a dynamic
rule.
Note NonStop NET/MASTER MS constructs the message ID for messages that come from other subsystems.
The format is the short form of the subsystem ID followed by the event number padded with zeros. For
example, event number 7 from the Expand subsystem has the message ID EXP0007.
Specifying the Subsystem ID. Use the ID of the subsystem that generates the message as a
criterion by specifying the long form of the subsystem ID in the SS ID field (for
example, TANDEM.NNM.D30 is the NonStop NET/MASTER MS subsystem). The
field accepts up to 32 characters. Use the wild-card characters, question mark (?) and
asterisk (*), to match multiple subsystems. An asterisk must follow at least one
character and must be the last character in the field. A question mark must follow at
least one character and can appear in any other position in the field. Use a variable to
allow the subsystem ID to change dynamically (for example, you can set the value of
the variable by using another rule). If you use a variable, the rule becomes a dynamic
rule if the subsystem ID is also the primary trigger.
Specifying the Message Profile Variable. Use a message profile variable as a criterion by
specifying values in the MDO Element Name and MDO Element Value fields. Two
examples are MSGATTR.DISPLAY.COLOR with a value of BLUE and
SPI.TANDEM.ZEMS_TKN_EMPHASIS with a value of 1. Refer to the NonStop
NET/MASTER NCL Reference Manual for details on message profile variables.
Each field accepts up to 78 characters. Use the wild-card characters, question mark (?)
and asterisk (*), in the Value field to match multiple values. An asterisk must follow at
least one character and must be the last character in the field. A question mark must
follow at least one character and can appear in any other position in the field. Use a
variable to allow the value criterion to change dynamically (for example, you can set
the value of the variable by using another rule). If you use a variable and the message
profile variable is also the primary trigger, the rule becomes a dynamic rule.