NET/MASTER RMS Management and Operations Guide

RMS9904
RMS Messages
115415 NonStop NET/MASTER RMS Management and Operations Guide A–117
RMS9902 subsystem-name component-type component-name RECOVERY
COMPLETE. STATUS: current-state
Cause. A message triggered a message action rule in ruleset BASERULE associated
with a message handler and caused the message handler to perform recovery action
on the component, component-name . The component was recovered.
subsystem-name is the name of the subsystem that owns the component, and
component-type is the type of component. For example, subsystem-name can be
EXPAND, component-type can be LINE, and component-name can be the name of
the Expand line.
Effect. The recovery action ends and the component is operational again.
Recovery. In most cases, this message is informational only and no recovery action is
necessary. However, if current-state is not desirable (for example, Pending), you
must perform other required actions on component-name manually.
RMS9903 subsystem-name component-type component-name RECOVERY FAILED.
RETRYING AFTER delay-period DELAY
Cause. A message triggered a message action rule in ruleset BASERULE associated
with a message handler and caused the message handler to perform recovery action
on the component, component-name . The recovery failed. The rule retries the
recovery action after a time interval indicated by delay-period .
subsystem-name is the name of the subsystem that owns the component, and
component-type is the type of component. For example, subsystem-name can be
EXPAND, component-type can be LINE, and component-name can be the name of
the Expand line.
Effect. The recovery action is queued using a timer and will be executed again after
delay-period .
Recovery. This message is informational only; no recovery action is necessary. If you
want to cancel the recovery action, display the rule actions for the subject of the
message (typically component-name ) and delete highlighted action.
RMS9904 subsystem-name component-type component-name RECOVERY FAILED.
Recovery retries expired
Cause. A message triggered a message action rule in ruleset BASERULE associated
with a message handler and caused the message handler to perform recovery action
on the component, component-name . The recovery failed. The rule does not retry
the recovery action because the number of retries exceeded the maximum allowed.