NET/MASTER RMS Management and Operations Guide

Adding a Message Action Rule
Creating and Developing Rulesets and Rules
5–44 115415 NonStop NET/MASTER RMS Management and Operations Guide
A message triggers rule A. Twenty seconds later, a second message triggers
rule C. Another twenty seconds later, a third message triggers rule B. Because
rule C has expired when rule B is triggered, the message group rule is not
triggered.
To register the rule, you must specify both the Message Group ID and the Purge After
fields as follows:
Specify the name of the message group rule in the Message Group ID field. If the
message group rule does not exist in the ruleset, you get a warning when RMS
validates the field. If you receive this warning, ensure that you create the message
group rule later by using option 2 on the RMS : Rule Maintenance panel. If the
message group rule exists in the ruleset, RMS updates the message group rule to
include this rule as a member. (Similarly, if you remove the name of the message
group rule from the Message Group ID field, RMS updates the message group rule
to remove this rule from the membership list.)
Specify the time interval within which the rule is regarded by the message group
rule as having been triggered (trigger life) in the Purge After field. The value must
be in the range 00:00:00 through 23:59:59 (you can omit the 00 strings; for example,
::01 is the same as 00:00:01).
Using the Correlation Key
You can further restrict the trigger for a message group rule by requiring some or all of
the messages that trigger the rule members to contain a key that is the same. For
example, if the arrival of a group of messages constitutes an event, but the messages
contain a key that varies (for example, user ID), you can restrict the trigger to the
arrival of messages with the same key. If the key is the third word of a message, then
the key is &WORD3.
To use this feature, specify the key in the Correlation Key field on the RMS : System
Action panel (page 5 of the message action rule definition panels). The key can contain
any characters except the vertical bar (|). Also, it can contain the names of variables,
for example, the RMS message variables (see “RMS Message Variables” in Section 11).
The field can accommodate up to 49 characters.
Implementing a %INCLUDE
Rule
Use the %INCLUDE rule to load an additional ruleset when you start a message
handler. The rule allows a message handler to use more than one ruleset. The rule has
the following features:
You can nest up to 60 %INCLUDE rules.
With nested %INCLUDE rules, the message handler loads the records of the
innermost ruleset first. For example, if Ruleset A contains a %INCLUDE rule that
specifies ruleset B and ruleset B contains a %INCLUDE rule that specifies ruleset
C, RMS loads the records in ruleset C first, ruleset B second, and ruleset A last.
The additional ruleset merges with the loaded ruleset with overlay; that is, new
records are added and duplicate records are replaced. A record can be, for
example, a rule or the control options.