RMFOD0 - CPC LPAR Engine Configuration
The RMFOD0 inquiry generates up to two charts for each Central Processing Complex (CPC).
micsrm140
One chart shows the physical engines available in the CPC shared engine pools, and the logical engine assignments for each LPAR that uses the CPC shared engine pools. If the CPC has any LPARs with dedicated processors, a second chart is produced. This chart shows that the CPC dedicated physical engine pool and the dedicated engines that are assigned to each LPAR defined with dedicated engines.
The example shows the chart that is generated for the shared engine pools of an IBM zEC12 2827-615 CPC. The five vertical bars for the left most LPAR, named ##CPC##, shows the number of active physical processors (engines) of each type (CP, zAAP, zIIP, IFL, and ICF) in the shared engine pools. The logical processor assignments for the active LPARs in the CPC follow to the right. A similar chart is generated for the dedicated engine pools.

Note:
Coupling Facility LPARs have only one engine type assigned (ICFs) while the z/OS LPARs (for example, ‘CA11’ and ‘CA31’) typically have two engine types assigned (CPs, and zIIPs). One of the LPARs ‘ZAWARE’ has IFL engines only, while another, ‘SYSC’, has CPs, zIIPs, and IFLs.Uses
This inquiry shows you your LPAR configuration at a glance -- and serves as a basis to compare against some of the queries that show actual engine utilization values to validate that logical processor assignments make sense. To minimize multiprocessor management overhead, assign the minimum number of engines that are required to manage the workload to an LPAR.
Charts

Left Y-axis
LPAR ##CPC##
PRSMACSP
Avg CP Shareable Processors
PRSMAISP
Avg ICF Shareable Processors
PRSMANSP
Avg IFL Shareable Processors
PRSMAZSP
Avg zAAP Shareable Processors
PRSMASSP
Avg zIIP Shareable Processors
Real LPARs
LPCAVCPU
Avg Number of Active CP Processors
LPCAVICF
Avg Number of Active ICF Processors
LPCAVIFL
Avg Number of Active IFL Processors
LPCAVZAP
Avg Number of Active zAAP Processors
LPCAVSUP
Avg Number of Active zIIP Processors
X-axis
PRSMLPNM
Logical Partition Name
CPC Dedicated Engine Pool LPAR Configuration

Left Y-axis
LPAR ##CPC##
PRSMACDP
Avg CP Dedicated Processors
PRSMAIDP
Avg ICF Dedicated Processors
PRSMANDP
Avg IFL Dedicated Processors
PRSMAZDP
Avg zAAP Dedicated Processors
PRSMASDP
Avg zIIP Dedicated Processors
Real LPARs
LPCAVCPU
Avg Number of Active CP Processors
LPCAVICF
Avg Number of Active ICF Processors
LPCAVIFL
Avg Number of Active IFL Processors
LPCAVZAP
Avg Number of Active zAAP Processors
LPCAVSUP
Avg Number of Active zIIP Processors
X-axis
PRSMLPNM
Logical Partition Name
Inquiry Details
- HARLPC DAYS timespan file: Cycle 01
- A Common Data Selection step selects yesterday’s data
- User code overwrites LPAR=’PHYSICAL’ to represent values for CPC level LPAR: ‘##CPC##’
- Derivations:
DATE
DATEPART(ENDTS) ;
CPCID
%CPCID ;
Modifications
The following modifications can be made to the RMFOD0 inquiry:
- You can add filter statements to filter.
- Using the following CPC Identification data elements that you can filter on CPC:
- fffMOD - Processor Model Family (where fff is the file identifier -- for example, CPU, LPC, and so on.).
- CPCMODID - CPC Model Identifier.
- CPCSEQNB - CPC Sequence Number.
- If you do not have the DAYS timespan HARLPC file active, you can run the inquiry against the DETAIL timespan, cycle 01.
- Remove the %RMFOD0B macro from the Charting Output Step.