NET/MASTER RMS Management and Operations Guide

11 RMS Variables
108106 Tandem Computers Incorporated 11–1
This section describes the RMS variables that you can use in your rules.
RMS variables enable the transfer of data within a message handler (for example,
between rules) and the extraction of information on a message. Being able to transfer
data allows one rule in a message handler to affect another rule in the message handler
(for example, the activation of a dynamic rule). Being able to extract information on a
message allows the message handler to determine if a message triggers a rule and to
base the actions on the extracted information.
You can also use global variables that are visible throughout the NonStop
NET/MASTER system to facilitate communication between NCL procedures and
message handlers.
Using variables, the characteristics of a rule or a message handler can dynamically
change in response to messages on your system. Section 5, “Creating and Developing
Rulesets and Rules,” describes how to use the fields on the rule definition panels and
identifies those fields that accept variables.
The variables are of the following two types:
Ruleset variables consist of variables that pertain to a rule: for example, a variable
that can be set using a rule or a variable that contains information on a rule.
RMS message variables consist of variables that contain information on a message
that arrives at a message handler.
Ruleset Variables Ruleset variables are of the following three types: global variables, user variables,
and rule contents variables.
Global Variables Global variables are of the form &GLBL*, where the asterisk represents a string of up
to eight characters. You can define up to three global variables in a message action
rule using the RMS : Set Ruleset Variables panel. The values of the variables are set
only if a message triggers the rule. Global variables are visible throughout the
NonStop NET/MASTER system and can be shared with other NCL procedures.
User Variables User variables are of the form &$UV*, where the asterisk represents a string of up to
nine characters. You can define up to ten user variables in a message action rule. The
values of the variables are set only if a message triggers the rule. User variables are
local, that is, they are only visible to the current message handler and the exit NCL
procedures. User variables are not visible to message group rules and time-based
rules.