NET/MASTER RMS Management and Operations Guide

RMS1030
RMS Messages
115415 NonStop NET/MASTER RMS Management and Operations Guide A–29
RMS1029 handler-type PROC( ncl-id ) RULESET ( ruleset-name ) OPTIMIZED
Cause. The message handler loaded all message action rules in ruleset-name
(including the rules loaded through the %INCLUDE rules) into a vartable in memory.
The vartable entries were optimized to enable faster searching of the vartable for each
message read by the message handler.
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.
Effect. The ruleset is optimized in memory.
Recovery. This message is informational only; no recovery action is necessary.
RMS1030 handler-type PROC( ncl-id ) WARNING - COULD NOT OBTAIN LISTDEV
DATA
Cause. A user started a message handler, and the handler issued the OPSYS SEND
PUP LISTDEV command to obtain a list of the devices on the system. The command
failed.
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.
Effect. No list of devices is retrieved, and the starting of the message handler
continues.