This section explains error messages output when the clrwzconfig command is executed in the order of message numbers.
Content:
The option specified to the command is incorrect.
Corrective action:
Specify the option correctly as instructed in how to use the command and re-execute.
Content:
The command is terminated abnormally, as the configuration management facility for cluster control is not running.
Corrective action:
Start configuration management facilities on all the nodes that constitute the cluster and then retry.
Content:
The command is terminated abnormally, as RMS has been started. To the %s, all node names (CF node names) that have been started by RMS are listed with commas as partitions.
Corrective action:
Stop RMS on all the nodes that constitute the cluster.
Content:
The command is terminated abnormally, as the RMS configuration file has not been distributed (Configuration-Active) or the cluster application does not exist.
Corrective action:
Execute distribution (Configuration-Activate) of the RMS configuration file, and then retry the command.
If the cluster application does not exist, this action is not necessary.
Content:
RMS configuration files specified by the -d option (currently inactive RMS configuration files) are displayed on %s (upper).
Already Generate/Activate, currently active RMS configuration definition files are displayed on %s (lower).
Corrective action:
Confirm if the currently active RMS configuration file needs to be deleted and then re-execute the command that specifies the currently active RMS configuration file.
Content:
The %d-%s-%s displays the phase code (internal definition code), function name, and command name to which errors occurred.
The %d displays the return value of the command to which an error occurred.
Corrective action:
Record this message and collect information for an investigation. Then, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
The %d-%s-%s displays the phase code (internal definition code), function name, and command name to which errors occurred.
The %d displays the return value of the command to which an error occurred.
Corrective action:
Record this message and collect information for an investigation. Then, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
The %d-%s-%s displays the phase code (internal definition code), function name, and command name to which errors occurred.
The %d displays the return value of the command to which an error occurred.
Corrective action:
Record this message and collect information for an investigation. Then, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
The %d-%s-%s displays the phase code (internal definition code), function name, and command name to which errors occurred.
The %d displays the return value of the command to which an error occurred.
Corrective action:
Record this message and collect information for an investigation. Then, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
Content:
The %d-%s-%s displays the phase code (internal definition code), function name, and command name to which errors occurred.
The %d displays the return value of the command to which an error occurred.
Corrective action:
Re-execute the command.
If the problem still remains, record this message and collect information for an investigation. Then, contact field engineers. For details on how to collect information, see "Troubleshooting" in "PRIMECLUSTER Installation and Administration Guide."
