NET/MASTER RMS Management and Operations Guide

RMS6104
RMS Messages
115415 NonStop NET/MASTER RMS Management and Operations Guide A–79
RMS6102 WARNING - MESSAGE GROUP DOES NOT EXIST FOR RULESET
ruleset-name
Cause. You were adding or modifying a message action rule in the ruleset,
ruleset-name , but the name in one or more of the Message Group ID fields on your
System Action panel did not refer to existing message group rules in the ruleset. The
action you requested requires either names of message group rules that exist in the
ruleset, or blanks in those fields.
Effect. The action is not performed. The names of the nonexistent message group rules
are highlighted.
Recovery. This message is a warning only—if you request the action a second time, the
action will be performed and you will have to create the nonexistent rules in the
ruleset.
RMS6103 ENTER AT LEAST ONE OF MESSAGE ID, SS ID OR MDO ELEMENT
Cause. While adding a message action rule, you left the Message ID field, the SS ID
field, and the MDO Element Name and Value fields on page 1 of the message action
rule definition panels blank. The action you requested requires you to specify a value
in at least one of the fields (the MDO Element Name and Value fields are treated as a
group).
Effect. The action is not performed. The first of the fields, the Message ID field, is
highlighted.
Recovery. Specify a value in at least one of the Message ID, SS ID, or MDO Element
Name and Value fields before requesting the action again. If you specify a value in the
MDO Element Name field, you must also specify a value in the MDO Element Value
field.
RMS6104 MESSAGE ACTION ID MUST BE ENTERED
Cause. While adding a message action rule, you left the Message Action ID field on
page 1 of the message action rule definition panels blank, and no default was available
to the field.
Effect. The action is not performed.
Recovery. Specify a valid value in the Message Action ID field before requesting the
action again. Valid values can contain up to twelve characters: alphanumeric, @, #,
and $. The value does not need to be unique within the ruleset or across the RMS
database.