NET/MASTER RMS Management and Operations Guide

RMS1014
RMS Messages
A–22 115415 NonStop NET/MASTER RMS Management and Operations Guide
RMS1014 handler-type PROC( ncl-id ) RULESET REFRESH REQUESTED BY
( user-id ) ACCEPTED
Cause. There are two possible causes as follows:
A group of messages triggered a message group rule in the ruleset associated with
a message handler. One of the group rule actions is to load a new ruleset, and the
request to do so was made.
A user modified the Rule Overlap Control field or the order of the ranking
elements of the ruleset associated with a message handler, and made the
modifications available to the handler immediately. To make these modifications
effective, a complete reload of the ruleset is required.
The message handler is executing as an NCL process with NCL ID, ncl-id .
handler-type is the type of message handler and can have one of the following
values:
EMS The message handler is executing as an EMSPROC.
LOG The message handler is executing as a LOGPROC.
MSG The message handler is executing as a MSGPROC.
INT The message handler is executing in a user's current environment or in a
background environment.
user-id is the user ID of the user that owns the environment in which the message
handler is executing.
Effect. The request to load a new ruleset is accepted and enacted.
Recovery. This message is informational only; no recovery action is necessary.
RMS1015 handler-type PROC( ncl-id ) RULESET SWAP REQUEST BY ( user-id )
ACCEPTED
Cause. A user selected a message handler on the Active Message Handlers panel and
changed the name in the Ruleset field on the displayed Control Options Definition—
Suppression panel. The change was filed to request that the ruleset associated with
the message handler be changed. The request to load the new ruleset was accepted.
The message handler is executing as an NCL process with NCL ID, ncl-id .
handler-type is the type of message handler and can have one of the following
values:
EMS The message handler is executing as an EMSPROC.
LOG The message handler is executing as a LOGPROC.
MSG The message handler is executing as a MSGPROC.