HSCL04xx logical partition error codes

These error codes can be displayed in a window that is displayed on the HMC screen during system configuration and operations.
Back to HSCL error codes page
HSCL04xx error codes Message Recovery action
HSCL0400 Failed to determine the minimum amount of memory required for the amount of maximum specified.
  1. Retry the task.
  2. If the problem persists, contact your next level of support or your service provider.
HSCL0401 Failed to determine the valid 5250 CPW range with the amount of processing given.
  1. Retry the task.
  2. If the problem persists, contact your next level of support or your service provider.
HSCL0402 Not enough system firmware memory is available to perform this task. The managed system needs an additional {0} MB of memory. You can free memory resources by removing memory through dynamic logical partitioning or by deleting partitions that are not being used. The managed system needs additional memory. Remove memory through dynamic logical partitioning or deleting unused partitions to release memory resources.
HSCL0403 The number of processors available for i5/OS® partitions is not sufficient: Obtained - {0}, Required - {1}. You can create a new profile or modify the existing profile to use the number of obtained processors, and then activate the partition. If the partition must be activated with the required number of processors, first shut down the active i5/OS partitions that are using the required processors, and then activate this partition.
  1. Create a new profile or modify the existing profile for the partition to use the number of obtained processors.
  2. Alternatively, shut down other i5/OS partitions or use Dynamic Logical Partitioning to remove processing resources from other i5/OS partitions to release enough processors for this partition.
    Note: The number of i5/OS processors in use by an uncapped i5/OS partition is equivalent to the number of virtual processors in use by that partition. Therefore, in order to release i5/OS processors from an uncapped i5/OS partition, you must release virtual processors from that partition. Releasing one virtual processor from an uncapped i5/OS partition will release one physical i5/OS processor.
  3. Try the task again.
HSCL0404

The number of shared processing resources available for i5/OS partitions is not sufficient: Obtained virtual processors - {0}, Required virtual processors - {1}, Obtained processing units - {2}, Required processing units - {3}. You can create a new profile or modify the existing profile to use the number of obtained processing resources, and then activate the partition. If the partition must be activated with the required number of processing resources, first shut down the active i5/OS partitions that are using the required processing resources, and then activate this partition.

  1. Create a new profile or modify the existing profile for the partition to use the number of obtained processing resources.
  2. Alternatively, shut down other i5/OS partitions or use Dynamic Logical Partitioning to remove processing resources from other i5/OS partitions to release enough processing resources for this partition.
    Note: The number of i5/OS processors in use by an uncapped i5/OS partition is equivalent to the number of virtual processors in use by that partition. Therefore, in order to release i5/OS processors from an uncapped i5/OS partition, you must release virtual processors from that partition. Releasing one virtual processor from an uncapped i5/OS partition will release one physical i5/OS processor. Likewise, to assign one virtual processor to an uncapped i5/OS partition, one physical i5/OS processor must be available.
  3. Try the task again.
HSCL0406 The maximum memory setting exceeds the maximum system memory capacity. Please check the capacity and modify the maximum memory setting in the profile accordingly. Check the capacity and modify the maximum memory setting in the profile accordingly.
HSCL0407 Not enough huge page memory regions resources to meet the allocation setting.
  1. Ensure there is enough pages of huge page memory to start the partition.
  2. Rebuild the managed system. For details, see Updating managed system or frame information.
  3. If the problem persists, contact your next level of support or your service provider.

Send feedback | Rate this page