CBU

Purpose

The CBU command causes the target hardware processor to perform the specified capacity backup (CBU) function if available.

With the CBU command you can temporarily increase the central processor (CP) capacity of your central processor complex (CPC). In case of an outage, which may have reduced your overall processor capacity, additional workload can be processed on that CPC.

Note: HMC/SE Console version 2.17.0 discontinued support for the CBU command.

Syntax

Read syntax diagramSkip visual syntax diagramISQCCMDtarget_system_ProcOps_nametarget_hardware_name.LPAR_nametarget_hardware_nameCBU CMD(STATUS)CMD(UNDO)CMD(ACTIVATE)CMD(TESTACT)PW( password)

Requirements

The requirements for the CBU command to complete successfully are:

  • Processor operations must be active.
  • The addressed target system must be initialized, or, if the target hardware is addressed, at least one target system on that hardware must be initialized.
  • For UNDO, ACTIVATE, and TESTACT, the SE of the target hardware must have Capacity backup set to 'Enabled' in the Customize Console Services window. This applies to ACTIVATE and TESTACT regardless of whether the CBU activation password is provided or not.

    For ACTIVATE and TESTACT, the CBU records must be loaded on the SE of the target hardware. Multiple CBU records are supported.

  • For ACTIVATE, TESTACT and UNDO, the flag 'Allow capacity change API requests' must be set in 'Customize API Settings' on the SE.

Parameters

For a definition of target_system_ProcOps_name, target_hardware_name.LPAR_name, and target_hardware_name, see ISQCCMD.

CBU
Indicates the CBU command function to be executed.
CMD
The command to be executed
STATUS
Returns the current status of the CBU facility of the addressed CPC. The possible status values returned are:
AVAILABLE
CBU is installed on the CPC.
ACTIVATED
CBU is started through ACTIVATE command.
NOT_ACTIVATED
CBU is installed but not activated.
NOT_ENABLED
CBU is installed but not enabled.
NOT_INSTALLED
CBU is not installed on the CPC.
UNAVAILABLE
CBU is installed but no longer available.

In addition, if the CBU Status is ACTIVATED, the activation and expiration dates are returned. The expiration date corresponds to the capacity record expiration date.

The ISQCCMD response message ISQ464I contains the status report.

ACTIVATE
Activates the previously installed and enabled CBU.

Multiple CBU records can exist on the SE. In this case, the decision logic is as follows:

  • If one of the CBU records is marked as Default, CBU Activate works with this record.
  • If none of the CBU records is marked as Default, CBU Activate works with the 'oldest' CBU record.

This Logic applies for TESTACT as well. Note that with the CBU common command, it is NOT possible to select a specific CBU record.

TESTACT
Activates the previously installed and enabled CBU in test mode.
UNDO
Deactivates a previously activated CBU to the regular configuration. Note that this function is not available on all CPCs supporting CBU. If the UNDO command fails, the regular CPC configuration must be restored by performing a POWERON-RESET of the CPC.

Multiple CBU records can exist on the SE. In this case, the decision logic for the UNDO command is as follows:

  • If one of the CBU records is marked as Default, CBU Undo works with this record.
  • If none of the CBU records is marked as Default, CBU Undo works with the 'oldest' CBU record.
PW
The CBU activation password for ACTIVATE or TESTACT. It exists for compatibility reason. If provided, it's ignored.

Defaults

The default of the CBU command is CMD(STATUS).

Usage

Issue the CBU command to temporarily increase the central processor (CP) capacity of your central processor complex (CPC). The increased capacity may require to update your CPC's activation profiles, so that the additional processor resources can be used in your processor configuration.

For more information about CBU, see System z Capacity on Demand User's Guide or Capacity Backup User's Guide, available for the particular System z® on IBM® Resource Link®.

Restrictions and Limitations

The CBU common command is only supported for SNMP connections. When issuing a CBU request for another ProcOps connection type, it will be rejected.

Return Codes

The ISQCCMD command (see ISQCCMD) generates the return codes for common command processing.