NET/MASTER RMS Management and Operations Guide
Creating a Ruleset
Creating and Developing Rulesets and Rules
115415 NonStop NET/MASTER RMS Management and Operations Guide 5–5
develop your ruleset, you can include additional comments. A ruleset takes on the
comments you add to the control options record.
You have created a new ruleset. You can add rules to the ruleset and make changes to
the ruleset (for example, control options) to suit any new requirements. Remember to
update the comments as you do so.
Specifying the Message
Delivery Philosophy
The message delivery philosophy determines how the ruleset handles the delivery of
messages that are not accounted for by a rule. You specify the delivery philosophy in
the Delivery Philosophy field (RMS : Control Options Definition—Suppression panel)
using one of the following values:
Value Description
POSITIVE Delivers all messages that are not accounted for by a rule. This is the default.
NEGATIVE Suppresses all messages that are not accounted for by a rule.
The following example shows the delivery philosophy for the ruleset HYRLST02:
032
SDPL----------- RMS : Control Options Definition - Suppression -----Page 1 of 4
Command ===>
Ruleset ....
HYRLST02
Delivery Philosophy .....
POSITIVE (NEGATIVE or POSITIVE)
Note: Message Delivery Philosophy may be NEGATIVE or POSITIVE. That is
messages may be delivered unless explicitly suppressed (POSITIVE)
or suppressed unless explicitly delivered (NEGATIVE).
During a ruleset development cycle, you may want to initially leave the delivery
philosophy as POSITIVE while you develop the rules for the relevant messages. This
allows you to monitor the message flow when you test the ruleset and develop the
necessary rules to handle all relevant messages. When your ruleset is complete, you
can then set the delivery philosophy to NEGATIVE to suppress all messages that are
not accounted for by a rule; that is, messages that you have decided are irrelevant.
Implementing User-Defined Default Delivery Processing
You can use your own default delivery exit NCL procedure to process messages that
are not accounted for by a rule. You must use the EXIT core statement in your
procedure to return a value to RMS. If the return code is zero, RMS continues to
deliver or suppress the message according to the specified delivery philosophy. If the
return code is nonzero, RMS terminates the processing of the message. You cannot
pass parameters to the procedure.