NET/MASTER RMS Management and Operations Guide

Adding a Message Action Rule
Creating and Developing Rulesets and Rules
5–26 115415 NonStop NET/MASTER RMS Management and Operations Guide
You may place the procedure in your NonStop NET/MASTER user procedure library
if you are the only person who will use this ruleset with a message handler. Your
NonStop NET/MASTER MS user ID definition contains the name of this library.
Specify the name of your message validation exit NCL procedure in the User Exit field
shown on the next partial panel (page 2 of the message action rule definition panels).
The procedure must exist. Furthermore, for the procedure to be valid in this field, the
procedure must contain no compilation errors.
046
User Exit ....
Specifying the UDP Ranking Element
UDP is a user-defined rule trigger priority that RMS uses as one of the ranking
elements that determine the rule selection criteria when a message triggers more than
one rule. You arrange the ranking elements using the RMS : Control Options
Definition—Ranking panel. If you use the default arrangement of the ranking
elements, UDP is the ranking element with the highest priority. You specify the
priority in the UDP field shown on the next partial panel (page 2 of the message action
rule definition panels). Valid values are 0 through 99 with a larger number giving the
rule a higher priority. The default is 0.
047
User Defined Priority (UDP) .... 0 (0-99)
For example, you may have two rules, rule 1 and rule 2, that can be simultaneously
triggered by the same message. Rule 1 has a UDP of 0, and rule 2 has a UDP of 1. If
UDP is the ranking element with the highest priority, then rule 2 has priority over
rule 1 when both rules are triggered.
Using Your Own Message Subject
You can define your own subject for a triggering message. If you do not define your
own message subject, the message subject is the value of the subject token in the
message. If the message contains no subject token, the message ID becomes the
message subject. The ability to define your own message subject provides you with
greater control on certain messages that you may not want to trigger rules. For
example, you have a rule that responds to the following message:
NNM0686 USER userid FAILED TO PROVIDE CORRECT PASSWORD, AFTER
TRYING n TIMES ON devname
You want to be able to prevent a message from triggering the rule when the message
comes from a particular device devname . You define &WORD14 as your message