CPC - CPC Capacity Report

The CPC Capacity (CPC) report provides the capability to monitor values that are relevant for software pricing as well as partition related processor activities.

Prior to z/OS, software products were typically priced based on the computing capacity of the central processor complex (CPC) on which the software is running. With z/OS running on a zSeries hardware, charging can be based on the capacity defined for workloads. WLM LPAR CPU management offers the support that allows pricing based on partition capacity. It will ensure that the average CPU consumption of a partition does not exceed a defined capacity value (in millions of unweighted CPU service units per hour - MSU/h) over a defined period of time. WLM allows the actual workload to rise above the defined MSU limit, but takes care that the four-hours average stays below. This is done by dynamically turning capping on and off. Prerequisites are uncapped partitions with shared CPs.

With this CPC capacity report, you can compare the defined capacity limits against the actual MSU consumption for all partitions of the CPC. In addition, the report contains MSU information related to the last four hours, for the partition RMF is running in, which clearly shows if the defined capacity limit is appropriate to the workload running in this partition or if WLM has to cap this partition's workload because the defined limit was set too low.

How to request this report

To request the CPC Capacity report, select 1 from the Primary Menu and then 3 on the Overview Report Selection Menu (shown in Figure 1), or enter the following command:

CPC

Contents of the report

The CPC Capacity report provides:

Header information which offers MSU related values with the scope of that partition which requested the report as well as the processor type, model, and capacity.
Partition data which displays the values for all partitions belonging to the CPC. If multithreading is enabled for a processor type (LOADxx PROCVIEW CORE parameter is in effect), processor data is reported at core granularity.

Figure 1. CPC Capacity report

                    RMF V2R4 CPC Capacity                          Line 1 of 58
 Command ===>                                              Scroll ===> HALF

 Samples: 120     System: TRX2  Date: 05/11/19  Time: 13.16.00  Range: 120   Sec

 Partition:   Z2         2817 Model 722                         Boost: Speed
 CPC Capacity:    2224   Weight % of Max: 74.2   4h Avg:   41   
 Image Capacity:    60   WLM Capping %:    5.4   4h Max:  185   Group:   CGRP0010
 MT Mode IIP:        1   Prod % IIP:       N/A   AbsMSUCap: Y   Limit:       100*

 Partition  --- MSU ---   Cap    Proc    Logical Util %   - Physical Util % -
              Def   Act   Def     Num    Effect   Total   LPAR  Effect  Total

 *CP                             14.0                      1.0    10.1   11.2
 TZ1          130   122   N N N   4.3      11.2    12.5    0.4     3.4    3.8
 Z1           150    89   N N N   5.2       9.3     9.6    0.1     3.5    3.6
 Z2            50    58   N N Y   2.1      11.5    12.8    0.2     1.7    1.9
 Z3           N/A     0   Y N N   2.4       8.8    10.6    0.3     1.5    1.8
 PHYSICAL                                                  0.1            0.2

 *ICF                             2.0                      0.1     7.1    7.2
  CF1                     N N N   1.0      99.9    99.9    0.0     7.1    7.1
  CF2                     N N N   1.0       0.0     0.0    0.0     0.0    0.0
  PHYSICAL                                                 0.1            0.1

Field descriptions

Table 1. Fields in the CPC Capacity Report
Field Heading	Meaning
All MSU-related values are measured in MSU/h (millions of service units per hour).
Values for the partition which requested the report
Partition	Partition name.
Processor/Model	Processor family and model number of the measured system.
Boost	The boost type that was active at the end of MINTIME: N Boost was inactive. zIIP zIIP boost. Speed Speed boost. All zIIP and speed boost were both active.
CPC Capacity	Effective processor capacity available to the central processor complex (CPC), measured in MSU/h.
Image Capacity	Processor capacity available to the z/OS image (partition) which requested the report, measured in MSU/h. The field is calculated as minimum of the following capacities: the capacity based on the partition's logical CP configuration (including CPs that are online or in standby state (not configured online)) the defined capacity limit of the partition, if available (image softcap) the capacity limit of the related WLM capacity group, if the partition belongs to a capacity group. the absolute physical hardware capping limit. the capacity based on the hardware group capping limit.
MT Mode IIP	The multithreading mode for processor type zIIP designates the number of active threads for each online logical zIIP core. If this value is greater than 1, multithreading becomes effective for zIIP cores. N/A is shown if the LOADxx PROCVIEW CPU parameter is in effect or no IIP is currently installed or online.
Prod % IIP	The multithreading IIP core productivity represents the percentage of the maximum IIP core capacity that was used while the IIP cores were dispatched to physical hardware. When this value equals 100% in multithreading mode, all threads on all IIP cores that were configured ONLINE for the complete MINTIME are being used. If the LOADxx PROCVIEW CPU parameter is in effect or no IIP is currently installed or online, no core productivity is calculated and N/A is reported.
Weight % of Max	Average weighting factor in relation to the maximum defined weighting factor for this partition. With 'Initial Capping ON', which the operator can set on the Hardware Management Console, this value is not available and therefore, this field shows '****' in this case.
WLM Capping %	Percentage of time when WLM capped the partition because the four-hours average MSU value exceeds the defined capacity limit.
4h Avg	Average value of consumed MSU/h during the last four hours.
4h Max	Maximum value of consumed MSUs during the last 4 hours (retrieved from 48 sample intervals of five minutes). This value can be greater than the defined capacity.
AbsMSUCap	Absolute MSU capping is active for the partition: Y or N.
Group	Name of the partition's capacity group. If the partition does not belong to a capacity group, N/A is displayed.
Limit	Capacity limit (in MSUs) defined for the partition's capacity group. An '*' following the limit value indicates that this partition started to be a member of this capacity group less than four hours ago. This partition will have a different view of unused group capacity and, therefore, might cap differently than existing group members.
Values for all configured partitions are grouped by general and special purpose processor types. The term logical processor refers to a logical core if the LOADxx PROCVIEW CORE parameter is in effect.
Partition	Partition name. Notes: Partitions identified by the name PHYSICAL are not configured partitions. Data reported in these lines includes the time during which a physical CPU was busy, but the time could not be attributed to a specific logical partition. The summary lines (for example, CP or ICF) show the total percentages for the indicated processor type. Starting with z9 processors, IFLs (Integrated Facility for Linux) and zAAPs are reported separately and no longer as ICFs (Internal Coupling Facility).
MSU	Millions of unweighted CPU service units per hour: Def Defined MSU capacity limit for the partition. Act Actual MSU consumption based on the logical processor effective dispatch time. These values are only provided for general purpose processors.
Cap Def	The hardware capping option of the partition. Each Cap Def value is a three position character string denoting which hardware capping mechanisms have or have not been applied in the logical partition controls of the Hardware Management Console (HMC) for the partition. The values in the first, second and third position of the string are either Y (Yes) or N (No) and have the following meaning: The first character (Y or N) indicates whether Initial Capping ON has been set. The second character (Y or N) indicates whether an absolute physical hardware capping limit (maximal number of CPUs) has been defined. The third character (Y or N) indicates whether an absolute hardware group capping limit (maximal number of CPUs) has been defined. An asterisk (*) to the right of a value indicates that the capping status changed during the report interval.
Proc Num	The number of logical processors which were online during the report interval.
Average Processor Utilization Percentages. The average utilization of logical processors is based on the total online time of all logical processors assigned to the partition. The average utilization of physical processors is based on the total interval time of all physical processors.
Logical Util % - Effect	The average partition effective dispatch time percentage. `Effective Dispatch Time ------------------------ *100 SUM Online Times`
Logical Util % - Total	The average partition total dispatch time percentage. `Total Dispatch Time -------------------- *100 SUM Online Times`
Physical Util % - LPAR	The average LPAR management time percentage. `Total Dispatch Time - Effective Dispatch Time ----------------------------------------------- 100 # Physical Processors Range Time` The calculation for the PHYSICAL partition is: `Time PHYSICAL ---------------------------------------- * 100 # Physical Processors * Range Time` Time PHYSICAL is the time that could not be attributed to a specific logical partition but was used by PR/SM to control the physical processor (LPAR management time).
Physical Util % - Effect	The effective utilization of the physical processor resource by the partition. `Effective Dispatch Time ---------------------------------------- 100 # Physical Processors Range Time`
Physical Util % - Total	The total utilization of the physical processor resource by the partition. `Total Dispatch Time ---------------------------------------- 100 # Physical Processors Range Time` The `Total Dispatch Time` for the PHYSICAL partition includes the time during which a physical CPU was busy, but the time could not be attributed to a specific logical partition. This time includes the time PR/SM was controlling the physical processor (LPAR management time), as well as any other time the processor was busy for any reason such as managing coupling facility traffic.