IBM z13s Technical Manual page 368

Sysplex-wide data aggregation and propagation occur in the RMF Distributed Data Server
(DDS). The RMF Common Information Model (CIM) providers and associated CIM models
publish the RMF Monitor III data.
The CPM, a function inside z/OS, retrieves critical metrics from one or more z/OS systems
through the CIM structures and protocol. CPM communicates to (local or remote) SEs and
HMCs through Simple Network Management Protocol (SNMP).
CPM has visibility of the resources in the individual offering records, and the capacity tokens.
When CPM decides to activate resources, a check is performed to determine whether enough
capacity tokens remain for the specified resource to be activated for at least 24 hours. If
insufficient tokens remain, no resource from the On/Off CoD record is activated.
If a capacity token is completely consumed during an activation driven by the CPM, the
corresponding On/Off CoD record is deactivated prematurely by the system. This deactivation
occurs even if the CPM has activated this record, or parts of it. Warning messages are issued
when capacity tokens are getting close to being fully consumed. The messages start being
generated five days before a capacity token is fully consumed. The five days are based on the
assumption that the consumption will be constant for the five days.
Put operational procedures in place to handle these situations. You can either deactivate the
record manually, let it happen automatically, or replenish the specified capacity token by using
the Resource Link application.
The Capacity Provisioning Control Center (CPCC), which runs on a workstation, provides an
interface to administer capacity provisioning policies. The CPCC is not required for regular
CPM operation. The CPCC will over time be moved into the z/OS Management Facility
(z/OSMF). Parts of the CPCC have been included in z/OSMF V1R13.
340
IBM z13s Technical Guide