Corrective action:
An unexpected error occurred.
If the same error is output again when you re-execute, collect debugging data and then contact field engineers.
Corrective action:
Confirm how to specify the option and option argument, and then execute the command correctly.
Corrective action:
Execute the command with system administrator authority.
Corrective action:
The operation environment file does not exist.
Re-install the "FJSVwvucw" package.
Corrective action:
This message could be output when the state of the system is unstable such as when there is insufficient memory.
If this message is displayed for any other reason, follow the instructions given as the corrective action.
If the same error is output even when you re-execute the command, collect the debugging information and then contact field engineers.
Corrective action:
Confirm the specified keyword, and then execute the command with the correct keyword.
Corrective action:
Confirm that CRM is running on all cluster nodes including the node on which the command was executed. Activate CRM on all nodes if necessary, and then execute the command.
Check whether the state of any cluster node is unstable because of insufficient memory, and then re-execute the command. If you specify the "-v" option at this time, you can determine the node on which the failure occurred.
If the same error is output again, collect debugging information and then contact field engineers.
Corrective action:
Confirm that CRM is running on all cluster nodes including the node on which the command was executed. Activate CRM on all nodes if necessary, and then execute the command. Check whether the state of any cluster node is unstable because of insufficient memory. Correct the problem if necessary, and then execute the command again.
If you specify the "-v" option at this time, you can determine the node on which a failure occurred. If the same error is output repeatedly, collect debugging data and then contact field engineers.
Corrective action:
A signal is received during the execution of the command.
If the same error is output again when you re-execute, collect debugging data and then contact field engineers.
