NET/MASTER RMS Management and Operations Guide

Message Handlers
Message Handlers, Timers, Rulesets, and Rules
115415 NonStop NET/MASTER RMS Management and Operations Guide 2–5
Queuing of Rule Actions
RMS queues the following rule actions: issuing a NonStop NET/MASTER MS
command and starting an NCL procedure. The message handler invokes separate
NCL processes to handle each of these actions.
The rule actions are placed on the NCL queue specified in the rule definition. The
NCL queue execution limit determines the number of rule actions that can execute
concurrently. See Section 3, “Planning for, Installing, and Managing RMS,” for more
information on limiting the number of concurrent rule actions. See Section 5,
“Creating and Developing Rulesets and Rules,” for information about specifying an
NCL queue for rule actions.
After NCL queuing, RMS serially executes rule actions for the same subject. Subjects
that have queued rule actions are called active subjects.
Message-Independent
Actions
If you use the message handler as a MSGPROC, you can (using the ruleset) instruct the
handler to modify the profile of the current execution environment and the function
key settings for the OCS window. If you use the INT-type message handler, you can
(using the ruleset) instruct the handler to modify the profile of its own dependent
processing environment.
You can also (using the ruleset) instruct the message handler to perform specified
initialization tasks before the handler starts to process messages.
Dynamic Changes You can change the characteristics of an active message handler dynamically; that is,
the changes you make to the ruleset are available to the handler immediately. Do this
using either the RMS panel interface or variables. The message handler has access to
NonStop NET/MASTER MS system variables and RMS variables.