NET/MASTER RMS Management and Operations Guide

RMS1006
RMS Messages
115415 NonStop NET/MASTER RMS Management and Operations Guide A–17
RMS1004 ENTER REGION NAME
Cause. You selected option B to start a message handler in a background environment
from the Start Message Handler panel, but failed to specify the owner of the
background environment in the Exec Region field.
Effect. The message handler is not started.
Recovery. Enter BLOG, BMON, BSYS, or EMSP in the Exec Region field and press
ENTER.
RMS1005 handler-type PROC( ncl-id ) MESSAGE HANDLER START COMMENCED
Cause. A user started a message handler. The handler is executing as an NCL process
with NCL ID, ncl-id . handler-type is the type of message handler started 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 the user's current environment or in a
background environment.
Effect. The message handler starts.
Recovery. This message is informational only; no recovery action is necessary.
RMS1006 handler-type PROC( ncl-id ) RULESET ( ruleset-name ) PARAMETER
OVERRIDE IN PROGRESS
Cause. A user started a message handler from the Start Message Handler panel with
the Parm Override field set to YES. Alternatively, a message handler was started
through the Event Simulation option where the Parm Override field is automatically
set to YES. This setting allows the user to override the control options of the ruleset to
be loaded.
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.