The CPCs to be managed and the systems to be observed are specified in the domain configuration. You can create and edit the domain configuration by using the Capacity Provisioning Management Console (CPMC). For more information about the CPMC see page Capacity Provisioning Management Console. Before you can activate the domain configuration, you must add it to the domain configuration repository of the domain. You can store multiple domain configurations for different purposes in the repository of the domain, but only one domain configuration can be active in the domain.
To get information about the workload that is running on a system or to manage the number of processors on that system, the Provisioning Manager must be connected to the system. The information is provided by a CIM server on the system. The domain configuration includes attributes that describe how to connect to each system. One attribute is the host address of the system, another attribute is the protocol to be used, and a third specifies the port on which the CIM server is listening.
Each system has an enabled attribute that specifies whether the Provisioning Manager is allowed to connect to the system and retrieve the information. You can switch this attribute on or off at runtime by using the Provisioning Manager commands ENABLE CONFIGURATION and DISABLE CONFIGURATION described on pages ENABLE CONFIGURATION and DISABLE CONFIGURATION.
CPCs are the target for the management of temporary capacity, Defined Capacity, and Group Capacity by the Provisioning Manager.
Temporary capacity must be installed on a CPC before it can be activated. Installed capacity is described in a capacity record, as described in System z10™ Enterprise Class Capacity on Demand User’s Guide, SC28-6871, and zEnterprise System Capacity on Demand User's Guide, SC28-2605. The Provisioning Manager can activate the residual capacity only in this record within limits that are defined during the order process of the record. Some CPCs in a domain might not have temporary capacity. In this case, the Provisioning Manager still reports resource shortages on these CPCs.
The provisioning domain contains a set of logical partitions (LPARs). They can be part of a stand-alone system (a monoplex), or can be part of a sysplex. A z/OS® system runs within each LPAR. When you define the domain configuration, you specify the set of z/OS systems to be observed. Each z/OS system is identified by name. If the system is part of a sysplex, the name also includes the name of the sysplex. A system can be observed and considered for capacity changes only if it runs on a CPC in the provisioning domain.
Each CPC in the domain configuration is identified by its logical name, which defines it on the support element (SE) of that processor complex. Each CPC has an enabled attribute that specifies whether the CPC is to be considered for capacity changes. If it is enabled, the Provisioning Manager can change the capacity of that CPC. If it is disabled, only manual capacity changes by using Provisioning Manager commands are allowed. You can switch the enabled attribute on or off at runtime by using Provisioning Manager commands. For more information about the commands, see ENABLE CONFIGURATION and DISABLE CONFIGURATION described on pages ENABLE CONFIGURATION and DISABLE CONFIGURATION.
The temporary capacity on a CPC includes multiple capacity records that are identified with unique record IDs. Only one of these records can be used by the Provisioning Manager at any one time. You can specify the ID of the record to use in the domain configuration, or if there is only one record, you can let the Provisioning Manager find it.
Defined Capacity and Group Capacity can be managed by the Provisioning Manager when they are defined with positive values in the respective LPAR or LPAR Group controls on the HMC or SE. As soon as they are turned off (set to 0), the management of Defined Capacity is stopped by the Provisioning Manager.
For CPCs that support static power save mode, the Provisioning Manager does not add temporary capacity based on the active policy while static power save is enabled. However, already activated temporary capacity can be deactivated by the Provisioning Manager based on your policy. ACTIVATE RESOURCE and DEACTIVATE RESOURCE commands are not affected by power save mode. Defined Capacity and Group Capacity management are also not impacted by power save mode.
You can enable or disable static power save mode by using the Provisioning Manager commands ENABLE POWERSAVE or DISABLE POWERSAVE or by using the Support Element or Hardware Management Console application.