HSCL 02xx

This section lists the HSCL 02xx error codes.

Note: The following error messages and recovery actions might include procedures that are not available on the DS8000® management console. If in doubt, contact the next level of support. If you are instructed to shut down the management console, then you must first verify that the customer is not currently performing DS8000 actions through the management console ESSNI connection.
Table 1. HSCL: 02xx error codes
Error code Message Recovery action
0201 Service Processor command failed after {0} attempts: Invalid response. Wait several minutes and try the task again.
0203 Command sent to Service Processor failed. Error response {0}.
  1. Try the task again.
  2. Check the state of the managed system. Refer to MAP6650 Correcting the CEC enclosure operating state and perform the appropriate procedure to put the managed system in the correct state.
  3. If the problem persists, contact your next level of support.
0204 Command failed. Unknown error.
  1. Shut down and restart the management console.
  2. If the problem persists, contact your next level of support.
0205 The managed system is in the error state and is unable to continue with the task.
The recovery partition data task cannot be run
until the managed system is no longer in error
state.

  1. Record the error message.
  2. Check the state of the managed system. Refer to MAP6650 Correcting the CEC enclosure operating state and perform the appropriate procedure to put the managed system in the correct state.
0206 Failed to power on the managed system. Unable to continue with the power on task.
  1. Check the Operator Panel Value field for the managed system to verify it is in the no power state and that the managed system is not in the error state.
  2. If the managed system is in the error state, refer to MAP6650 Correcting the CEC enclosure operating state and perform the appropriate procedure to put the managed system in the correct state.
  3. Verify that no other task is being performed, and then retry the task.
  4. If the problem persists, contact your next level of support.
0208 Failed to power on the managed system. Could not continue with the power on task.
  1. Check the Operator Panel Value field for the managed system to verify it is in the no power state and that the managed system is not in the error state.
  2. If the managed system is in the error state, refer to MAP6650 Correcting the CEC enclosure operating state and perform the appropriate procedure to put the managed system in the correct state.
  3. Verify that no other task is being performed, and then retry the task.
  4. If the problem persists, contact your next level of support.
0209 Remote virtual terminal sessions are not allowed. Check the remote virtual terminal settings. Virtual terminal cannot open remotely at this time. If this feature is needed, use the Enable/Disable Remote Virtual Terminal task in the System Configuration menu to enable remote connections.
020A The power on system profile operation timed out. Activate the system profile manually after the managed system is powered on. Activate the system profile manually after the managed system is powered on.
020D The command you issued contained incorrect data. Contact IBM support.
0211 The requested function is currently disabled. Shut down the managed system, and start it again.
0212 The managed system is not Capacity on Demand (CoD) capable at the present time.
  1. Ensure that the managed system is powered on.
  2. If it is powered on, check the managed system's properties window to verify that the system is not CoD capable.
  3. Contact your local representative for more information about this feature.
0213 The managed system does not support Capacity on Demand upgrades for processors. Contact your local representative for more information about this feature.
0214 The managed system does not support Capacity on Demand upgrades for memory. Contact your local representative for more information about this feature.
0215 There was an error trying to save processor order information to a diskette. Verify that the diskette is writable, and retry the operation again. If the error persists, contact your next level of support.
0222 The operation cannot be done because the managed system is not LPAR capable.
  1. If you believe that the managed system should be capable of logical partitioning, restart the management console and retry the operation.
  2. If the problem persists, contact your next level of support.
0223 Firmware is not ready to accept the specified command. Try again later.
  1. Retry the task.
  2. If the problem persists, contact your next level of support.
0224 There was an error dumping the LPAR configuration. Please check the console event log.
  1. Retry the task.
  2. If the problem persists, contact your next level of support.
0225 There was an error clearing the LPAR configuration. Please check the console event log.
  1. Retry the task.
  2. If the problem persists, contact your next level of support.
0226 Invalid firmware power off policy returned from the service processor. Unable to determine whether the firmware should power off or stay running after last partition powers off.
  1. Check that the inputs are correct.
  2. Retry the task.
  3. If the problem persists, contact your next level of support.
0228 The managed system could not be found in the database. Perform a rebuild managed system operation, and try again.
  1. Shut down and restart the management console.
  2. Rebuild the managed system. See MAP6620 Rebuilding managed system information for details.
  3. If the problem persists, contact your next level of support.
0229 Memory specified, {0}, is not a multiple of the system memory region size, {1}. Please modify the value to be a multiple of the memory region size and try again.
  1. Modify the value of the memory specified to be a multiple of the memory region size and try the operation again.
  2. If the problem persists, contact your next level of support.
022A The operation cannot be done since the managed system is not OS/400 capable.
  1. The managed system is not capable of creating or managing i5/OS partitions.
  2. If you believe that the managed system should be i5/OS capable, restart the management console and retry the operation.
  3. If the problem persists, contact your next level of support.
022C The managed system is not in a valid state to perform the operation. Check the state of the managed system and retry the operation.
  1. Try the task again.
  2. Refer to MAP6650 Correcting the CEC enclosure operating state and perform the appropriate procedure to put the managed system in the correct state.
  3. If the problem persists, contact your next level of support.
022D Unable to perform a get or a set operation on the managed system's platform IPL parameters.
  1. Try the task again.
  2. If the managed system is not in the correct state, refer to MAP6650 Correcting the CEC enclosure operating state and perform the appropriate procedure to put the managed system in the correct state.
  3. If the problem persists, contact your next level of support.
022E Unable to restore the profile data when the managed system is not in the Operating or Standby state.
  1. Verify that the managed system is in the Operating or Standby state, and retry the operation.
  2. If the managed system is not in the correct state, refer to MAP6650 Correcting the CEC enclosure operating state and perform the appropriate procedure to put the managed system in the correct state.
  3. If the problem persists, contact your next level of support.
022F Unable to delete the profile data backup file, {0}.
  1. Try the task again.
  2. Rebuild the managed system and try the task again. See MAP6620 Rebuilding managed system information for details.
  3. If the problem persists, contact your next level of support.
0230 Unable to get managed system credential information.
  1. Rebuild the managed system. See MAP6620 Rebuilding managed system information for details. Then try the task again.
  2. Restart the management console and then retry the operation.
  3. If the problem persists, contact your next level of support.
0231 Unable to set managed system credential information.
  1. Rebuild the managed system. See MAP6620 Rebuilding managed system information for details. Then try the task again.
  2. Restart the management console and then retry the operation.
  3. If the problem persists, contact your next level of support.
0233 Unable to change the service partition to the partition with ID of {0}. Please check your current setting(s) and ensure this change is allowed.
The service partition is not able to be changed.

  1. Check current settings and verify that this change is in fact allowed.
  2. Rebuild the managed system and try the operation again. See MAP6620 Rebuilding managed system information for details.
  3. If the problem persists, contact your next level of support.
0234 Failed to transition out of standby state. Rebuild the managed system and try again.
  1. Rebuild the managed system. See MAP6620 Rebuilding managed system information for details. Then try the task again.
  2. If the problem persists, contact your next level of support.
0235 Cannot change service partition from one partition to another if either one of them are not in the Not Activated state.
  1. Ensure that the current service partition is Not Activated.
  2. Ensure the partition user who tried to assigned the server authority is Not Activated.
  3. Rebuild the managed system. See MAP6620 Rebuilding managed system information for details. Then try the task again.
  4. If the problem persists, contact your next level of support.
0236 The name specified contain unprintable or invalid characters listed: {0}. Remove the invalid characters and try again.
  1. Ensure not to use any invalid characters specified in the message.
  2. Retry the task.
  3. If the problem persists, contact your next level of support.
0240 The {0} password is locked and cannot be changed while it is locked. The password has been locked, contact your hardware service provider to unlock the password.
0241 The {0} password is locked. The password has been locked, contact your hardware service provider to unlock the password.
0250 The managed system MTMS is empty.  
0251 Service processor command {0} failed. The connection to the hardware server is broken. Ensure the network connection is working. If the problem persists, contact your next level of support.
0252 Service processor command {0} failed. The connection to service processor is not available. Ensure the network connection is working. If the problem persists, contact your next level of support.
0253 Service processor command {0} failed. The managed system has been deleted. Ensure the network connection is working. If the problem persists, contact your next level of support.
0254 Hardware server command {0} failed. No response package.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
0255 Hardware server command {0} failed. The request ID has been deleted from the ID table.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
0256 Issuing a service processor pass through failed. management console server is trying to reconnect to the hardware server.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
0257 Issuing a service processor pass through failed. management console server reestablished a connection to the hardware server after this command was issued.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
0258 Issuing a service processor pass through failed. An expected exception with message {0} was thrown.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
0259 Service processor lock failed. The lock manager is not active. Restart the management console. If the problem persists, contact your next level of support.
025A Service processor lock failed. The conflict lock is owned by management console: {0}. Its request ID is {1}.
  1. Another management console might be performing this operation.
  2. Try again later.
  3. If the problem persists, contact your next level of support.
025B Query service processor data failed. The error code is {0}.  
025C Service processor command {0} failed. Service processor authentication needs to be done first.
  1. Ensure to authenticate with managed system first.
  2. Retry the task.
  3. If the problem persists, contact your next level of support.
025D Service processor command {0} failed. System firmware is not ready to accept command.
  1. Wait and then try the operation again.
  2. If the problem persists, contact your next level of support.
025E The lock table in the managed system is full. Please try again. Wait and then try the operation again.
025F There is a managed system lock. Wait and then try the operation again.
0260 Unexpected error happened when trying to acquire a managed system lock. The command return status is {0}. Wait and then try the operation again.
0261 Unexpected error happened when trying to acquire a managed system lock. Report the problem to your next level of support.
0262 Supplement lock operation is failed. Check the input and permission and try the task again.
0263 Service processor does not support more than one management console connection. No Service processor lock is needed. Contact your next level of support.
0264 The console command manager is not active.
  1. Try the operation again.
  2. If the problem persists, contact your next level of support.
0265 No destination was specified for command {0}. The command cannot be sent.
  1. Try the operation again.
  2. If the problem persists, contact your next level of support.
0266 The request to query data on the managed system failed with error code {0}.
  1. Try the operation again.
  2. If the problem persists, contact your next level of support.
0267 The connection to the service processor has been lost. A long-running task was stopped. Verify the completion of the long-running task. If the task did not complete successfully, try the task again
0268 An unexpected error occurred in a long-running task. Verify the completion of the long-running task. If the task did not complete successfully, try the task again.
0269 Managed system with IP address {0} cannot be found. Verify the specified IP address. Specify a valid IP address and try the request again.
026A The specified managed system name {0} is not valid with the specified IP address {1}. The managed system cannot be removed. Specify a valid managed system name and a valid IP address. Then try the request again.
026B Cannot find a managed system with the specified name {0}. Verify the specified system name. Specify a valid managed system name and try the request again.
026C The request to add a new managed system with IP address {0} failed. Verify the specified IP address. Specify a valid IP address and try the request again.
026D Lock type {0} is not valid for the managed system.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
026E The lock manager for managed system {0} is not active. Try the request again later. If the problem persists, contact your service provider.
026F Either the managed system name or the IP address is not specified in the request to remove the managed system. Specify both the managed system name and the IP address. Then try the request again.
0270 The specified command destination {0} cannot be found. The command {1} cannot be sent.
  1. Retry the operation.
  2. If the problem persists, contact your next level of support.
0271 The connection state of the specified command destination {0} is not valid. The command {1} cannot be sent. The connection to the managed system has been lost. Try the request again later.
0280 The service processor managed system state is not valid. The power state is {0}. The run state is {1}.
  1. Retry the task.
  2. If the problem persists, contact your next level of support.
0281 The operation cannot be done because the managed system is not shared processor capable. No recovery action is required.
0282 The virtual Ethernet adapter in virtual I/O slot {0} cannot be defined because the partition with ID {1} already defines a trunk adapter in its virtual I/O slot {2}. Please modify the profile accordingly and reactivate the partition. Please modify the profile accordingly and reactivate the partition.