| 5025-001 | Node -- fewer processes configured at this boot than before. |
Explanation: Detailed data for SYSMAN700_ER errlog record. When the node booted, the number of processors configured for the node is less than what was recorded in the SDR. This information is in the processors_installed attribute in the Node class for the node.
User Response: Follow the recommended actions in the error log entry.
| 5025-002 | Fewer processors configured. |
Explanation: Error description field for SYSMAN001_ER errlog record.
User Response: Follow the recommended actions in the error log entry.
| 5025-003 | Processor deconfigured due to errors. |
Explanation: Probable cause field for error log records.
User Response: Follow the recommended actions in the error log entry.
| 5025-004 | Processor varied offline by user. |
Explanation: Probable cause and failure cause field for error log records.
User Response: Follow the recommended actions in the error log entry.
| 5025-005 | Processor hardware errors detected. |
Explanation: Probable cause field for error log records.
User Response: Follow the recommended actions in the error log entry.
| 5025-006 | Run diagnostics, problem determination. |
Explanation: Recommended action field for error log records.
User Response: Run diagnostics and perform problem determination procedures on the failing hardware component.
| 5025-007 | Contact service representative. |
Explanation: Recommended action field for error log records.
User Response: Report failing hardware component to your IBM Support Center.
| 5025-008 | Reenable processor and reboot. |
Explanation: Recommended action field for error log records. Take this action if the processor was manually deconfigured.
User Response: Reenable the deconfigured processor and reboot the node.
| 5025-501 | No alphanumeric characters, command not issued. |
Explanation: You entered a command to the program without any valid characters.
User Response: Enter the corrected command.
| 5025-502 | Extraneous option - option. |
Explanation: You specified an extraneous option on the command.
User Response: Enter the corrected command.
| 5025-503 | Incorrect argument - argument. |
Explanation: You specified an invalid argument to the command.
User Response: Enter the corrected command.
| 5025-504 | Missing argument. |
Explanation: You specified an option that requires an argument without supplying the argument.
User Response: Enter the corrected command.
| 5025-505 | Incorrect option - option. |
Explanation: You specified an option which was not valid on the command.
User Response: Enter the corrected command.
| 5025-506 | Missing option. |
Explanation: You omitted an option on the command.
User Response: Enter the corrected command.
| 5025-507 | Working collective environment variable not set |
Explanation: The command expects the WCOLL environment variable to exist, since no working collective was specified on the command line.
User Response: Set WCOLL to the name of a file containing the working collective.
| 5025-508 | Cannot open working collective file file name: system message |
Explanation: The working collective file could not be opened
User Response: Check the system message, fix the problem, and enter the command again.
| 5025-509 | hostname command had exit code return code. |
Explanation: The command to the specified hostname was unsuccessful and produced the specified exit code.
User Response: Determine why the command is not working to the host, fix the problem, and retry the command.
| 5025-510 | Caught SIGsignal - terminating the child processes |
Explanation: The command has caught the specified signal and will issue SIGTERMs to any outstanding remote command child processes.
User Response: None
| 5025-511 | No hosts in working collective. |
Explanation: There are no hosts in the working collective. A possibility is that the program has removed the last hosts from the collective, since the remote command to it has failed
User Response: Ensure that the hosts in the working collective are responding and retry the command.
| 5025-512 | Could not pipe. |
Explanation: The program could not issue a pipe system call.
User Response: Contact system support.
| 5025-513 | Cannot redirect file name. |
Explanation: The command could not redirect file output.
User Response: Contact system support.
| 5025-514 | System Data Repository down |
Explanation: The System Data Repository is not working. The program cannot obtain needed information from the SDR.
User Response: Contact system support.
| 5025-515 | Hostname hostname unresolvable |
Explanation: The program could not find the specified hostname.
User Response: If the hostname is correct, contact system support. Otherwise, correct the hostname and reissue the program.
| 5025-516 | Attention - Specified node not in cluster. |
Explanation: The node number specified is not in the cluster.
User Response: If the node is specified correctly, contact system support. Otherwise, specify the node correctly and reissue the program command.
| 5025-517 | File file name contains POE pools, not supported. |
Explanation: The POE file contained a POE pool specification.
User Response: Use a POE file without the pool specification.
| 5025-518 | Cannot open host file file name. |
Explanation: The host file specified could not be opened.
User Response: If the host file name is correct, contact system support. Otherwise, correct the host file name and reissue the program command.
| 5025-519 | No working collective or POE file found. |
Explanation: No working collective file or POE file exists.
User Response: Check the WCOLL or MP_HOSTFILE environment variables to see if they specify a valid file of hostnames.
| 5025-520 | Conflicting arguments. |
Explanation: No working collective file or Parallel Operating Environment file exists.
User Response: Check the WCOLL or MP_HOSTFILE environment variables to see if they specify a valid file of hostnames.
| 5025-521 | Could not resolve node group node group name. |
Explanation: The first operand was not a number, so the operands are assumed to be node groups. The specified node group could not be resolved.
User Response: Use the nglist command to see if the desired node group exists.
| 5025-522 | Node node_number does not have an initial_hostname in the Node object class of the System Data Repository (SDR). The object is ignored. |
Explanation: The specified node does not have an initial_hostname in the SDR. This may be an unconfigured node. No processing will occur for this node.
User Response: Check the information in the Node object class in the SDR.
| 5025-550 | Only allowable flag is -b |
Explanation: You specified an option or flag which was not valid.
User Response: Correct the command and enter it again.
| 5025-551 | Uninitialized field in SDR record: record. |
Explanation: The System Data Repository has incomplete information. The command cannot continue.
User Response: Contact system support.
| 5025-552 | System Data Repository down. |
Explanation: The System Data Repository is not working. The seqfile command cannot obtain needed information from it.
User Response: Contact system support.
| 5025-553 | Node node_number does not have a reliable_hostname in the Node object class of the System Data Repository (SDR). The object is ignored. |
Explanation: The specified node does not have a reliable_hostname in the SDR. This may be an unconfigured node. No processing will occur for this node.
User Response: Check the information in the Node object class in the SDR.
| 5025-600 | Multiple occurrences of flag found. |
Explanation: You can specify only -kill, -nice, or -print flags.
User Response: Enter the command again with an appropriate flag.
| 5025-601 | One of -print, -kill, or -nice flags must be specified. |
Explanation: One of -kill, -nice, or -print flags is required.
User Response: Enter the command again with an appropriate flag.
| 5025-602 | Parentheses unbalanced. |
Explanation: Unequal number of left and right parentheses in expression.
User Response: Enter the command again with matching left and right parentheses.
| 5025-603 | Error in input line: |
Explanation: Input line to filter is in improper form.
User Response: Correct input to hostname: command.
| 5025-604 | Missing argument for option: |
Explanation: An option that expects an argument does not find one.
User Response: Correct the input.
| 5025-605 | Incorrect argument for option. |
Explanation: User has specified an incorrect argument for the specified option.
User Response: Enter the command again using valid options.
| 5025-606 | Missing string within parenthesis. |
Explanation: When using parenthesis, specify an expression.
User Response: Enter the command again correctly.
| 5025-607 | Incorrect hostlist specified. |
Explanation: There is an error in the hostlist arguments supplied on the pdf command line.
User Response: Correct the hostlist arguments and enter the command again.
| 5025-608 | No arguments specified. |
Explanation: No arguments (file system names) were specified on the pfck command line.
User Response: Enter the pfck command again with one or more file system name arguments.
| 5025-609 | Incorrect hostlist specified. |
Explanation: Error in the hostlist arguments supplied on the pfck command line.
User Response: Correct the hostlist arguments and enter the command again.
| 5025-610 | File specified is not valid: file_name |
Explanation: The file specified is incorrect. The file is either missing, or the file has the wrong type of permissions.
User Response: Correct the hostlist arguments and enter the command again.
| 5025-700 | Flag syntax: command flag, command flag argument is not valid. |
Explanation: A program flag argument is not correct.
User Response: Enter the command again with the correct flag argument.
| 5025-701 | Unknown command option: command option. |
Explanation: A program option is incorrect.
User Response: Enter the command again with the correct option.