Update a Capacity Provisioning Manager parameter to avoid a defined capacity WTOR

Description

In z/OS V2R2, the Provisioning Manager can detect when a manual change to defined capacity or group capacity would interfere significantly with Capacity Provisioning management. In such cases, the Provisioning Manager suspends its management of defined capacity or group capacity and issues one of the following write-to-operator-with-reply (WTOR) messages:

CPO4218I: New DC for systemName/sysplexName. Previous base previousLimit MSU. Enter 1 to set base to currentLimit or 2 to set to newLimit MSU
CPO4219I: New GC for groupName/CPCname. Previous base previousLimit MSU. Enter 1 to set base to currentLimit or 2 to set to newLimit MSU.

In response, the operator can choose to reinitialize the capacity management by setting the management base to the new capacity value and its managed capacity to 0, or continue the capacity management by adapting the management base to the manual change.

If you want the Provisioning Manager to continue managing the defined capacity or group capacity, regardless of manual changes, you can suppress the WTOR by setting the key DefinedCapacity.BaseToleration to 100 in the Capacity Provisioning Manager parameter file.

In z/OS V2R2, the default value of this key is 15, meaning that while Capacity Provisioning is managing a defined capacity, any concurrent manual reduction in defined capacity by more than 15% causes the WTOR to be issued.

Table 1 provides more details about the migration action. Use this information to plan your changes to the system.

Table 1. Information about this migration action
Element or feature:	BCP
When change was introduced:	z/OS® V2R2.
Applies to migration from:	z/OS V2R1 and z/OS V1R13.
Timing:	Before installing z/OS V2R2.
Is the migration action required?	Yes, if you use Capacity Provisioning for managing defined capacity or group capacity and you want to avoid a WTOR for large manual reductions of defined capacity or group capacity.
Target system hardware requirements:	None.
Target system software requirements:	None.
Other system (coexistence or fallback) requirements:	None.
Restrictions:	None.
System impacts:	None.
Related IBM® Health Checker for z/OS check:	None.

Steps to take

Follow these steps:

Add the entry DefinedCapacity.BaseToleration=100 to the Capacity Provisioning parameter file.
By default, the parameter file is named CPO.DOMAIN1.PARM(PARM).

Reference information

For information about how to define the new key to the Capacity Provisioning Manager parameters, see z/OS MVS Capacity Provisioning User's Guide.