For additional PSSP installation messages, see messages beginning with the prefix 0016.
| 2552-050 | Nodecond Status: Invoking directory path to node type process , node type. |
Explanation: Notifying the user of the node type selected and invoking the process to condition the nodes
User Response: No action required.
| 2552-051 | Option option flag incorrect. |
Explanation: The option flag entered on the command line is incorrect.
User Response: Check the correct option in the usage statement and enter the command again.
| 2552-052 | You have entered an incorrect frame_ID. |
Explanation: The frame ID entered on the command line is incorrect.
User Response: Select the correct frame ID and enter the command again.
| 2552-053 | You have entered an incorrect slot_ID. |
Explanation: The slot ID entered on the command line is incorrect.
User Response: Select the correct slot ID and enter the command again.
| 2552-054 | You must specify a frame_Id and a slot_Id. |
Explanation: Both frame ID and slot ID must be entered on the command line.
User Response: Enter the command again with the correct frame and slot IDs.
| 2552-055 | Unable to determine node type for frame_ID frame_ID, slot_ID slot_ID. |
Explanation: The program had a problem obtaining the correct value of the node type for the frame ID and slot ID entered.
User Response: If you have determined that the frame ID and slot ID entered are correct, follow standard problem resolution procedures.
| 2552-056 | Unrecognized node type found for frame_ID frame_ID, slot_ID slot_ID, and Card type=node type value. |
Explanation: The value returned for the node type is not recognized in the data base.
User Response: Follow standard problem resolution procedures.
| 2552-057 | Nodecond Not Successfull: Unable to create logfile logfile. |
Explanation: The trace information logfile was not created.
User Response: Follow standard problem resolution procedures.
| 2552-058 | Nodecond Not Successful: Trace information has been placed in the file logfile. |
Explanation: The error trace Information has been placed in the logfile.
User Response: Refer to the logfile for more information on the error condition.
| 2552-059 | Nodecond Not Successful: A return code of return code was returned which may indicate that the file system is full. |
Explanation: The return code value returned may indicate a full file system.
User Response: Follow standard problem resolution procedures.
| 2552-060 | You may not use the -a flag with any of the -n, -p, or -P flags. |
Explanation: The -a flag should not be used in combination with any of the -n, -p, or -P flags.
User Response: Re-issue the command with the correct flag syntax.
| 2552-061 | You may not use the -p flag with the -P flag. |
Explanation: The -p flag should not be used in combination with the -P flag.
User Response: Re-issue the command with the correct flag syntax.
| 2552-062 | You may not use the -a flag, the -p flag, or the -P flag in connection with nodes that do not support the CHRP interface. |
Explanation: Only CHRP nodes support the list physical location codes and ping functions.
User Response: Re-issue the command with the correct flag syntax.
| 2552-063 | No SPLAN adapter found. Run spadaptrs to define an SPLAN adapter. |
Explanation: There is no SPLAN adapter defined in the SDR. Before a node can be conditioned, the SPLAN adapter must be defined in the SDR.
User Response: Run the spadaptrs command to define an SPLAN adapter and issue the nodecond command again.
| 2552-064 | Configuration error. Multiple SPLAN adapters found. |
Explanation: There is more than one SPLAN adapter defined in the SDR. This is a configuration error.
User Response: Record the above information and contact the IBM Support Center.
| 2552-065 | Unable to find an adapter at physical location code in device tree. Quitting. |
Explanation: The physical location code defined in the SDR does not match with an adapter in the device tree list.
User Response: Verify that the physical location code defined in the SDR has the correct value and issue nodecond again.