NET/MASTER RMS Management and Operations Guide

RMS Rules
Message Handlers, Timers, Rulesets, and Rules
2–10 115415 NonStop NET/MASTER RMS Management and Operations Guide
Message Action Rules A message action rule governs how a message handler acts when a message arrives.
The identification of the message is either specific or generic (generic identification
uses wild-card characters). A message action rule contains the following information:
Criteria that determine if a message can trigger the rule
Criteria that govern the delivery of the message that triggers the rule
Information that determines what is delivered when a message triggers the rule
Rule actions to take
Characteristics of the rule when used as a trigger for a message group rule
Criteria That Trigger a Message Action Rule
There are seven types of criteria that determine if a message can trigger a message
action rule. When a message handler receives a message, the handler validates the
message against these criteria. The rule is triggered when the message satisfies the
criteria. The message handler then processes the message according to the rule. Use
the criteria as follows:
Use the following message trigger elements to set the primary characteristics of
the triggering message:
Message ID
ID of the subsystem that generates the message
Value of a message profile variable
You specify one of the above elements as the primary trigger for the rule. For
example, you can use a &$xxx.SPI.-prefixed message profile variable (which is a
translated SPI token in an event message) as the primary trigger. The primary
trigger is the first criterion the message handler checks to determine if a message is
a candidate for rule trigger.
Restrict the triggering message to those messages that originate from specified
sources as determined by the following:
ID of the domain from which the message originates
Name of the Guardian process that generates the message
Restrict the triggering message to those messages that arrive at specified days
within specified time ranges.
Restrict the triggering message by the text of the message. You can test any
portion of the text using relational and logical operators.
Set a rule trigger priority that determines how the message handler processes the
rule when the message that triggers the rule also triggers other rules. You use the
priority in conjunction with the control options that govern multiple rule triggers
by a message.