CA MICS Hardware and SCP Analyzer (RMF) Queries › Mainframe CPC Configuration

Mainframe CPC Configuration

This section contains the following topics:

RMFCFG - CPC LPAR Engine Configuration

RMFCFH - CPC LPAR Engine Configuration by Hour

RMFSTO - CPC LPAR Storage Allocation

RMFWGT - CPC LPAR Relative Weight by Engine Pool

RMFCFG – CPC LPAR Engine Configuration

Overview

The RMFCFG query generates a chart for each Central Processing Complex (CPC) that shows the physical engine configuration for the CPC and the logical engine assignments for each LPAR. One data extract shows the engine distribution for the shared engine pools, and the other for the dedicated engine pools.

The example shows the chart generated for the shared engine pools of an IBM z/10 2097-712 CPC. The five vertical bars for the leftmost LPAR, named ##CPC##, show 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. Notice that Coupling Facility LPARs have only one engine type assigned (ICFs) while the z/OS LPARs (for example, ‘CA11’ and ‘CA31’) typically have three engine types assigned (CPs, zIIPs, and zAAPs). One of the VM LPARs ‘VMZ’ has IFL engines only, while another, ‘SYSC’, has CPs, IFLs, and ICFs.

Uses

This query helps you see the LPAR configuration at a glance—and serve 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 required to manage the workload to an LPAR.

Data Extracts

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

Note: If there are no dedicated engines for a CPC, a chart is produced showing a single LPAR, named "NODED".

CPC Shared Engine Pool LPAR Configuration

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

Note: If there are no shared engines for a CPC, a chart is produced showing a single LPAR, named "NOSHARE".

Query Defaults

• HARLPC DAYS timespan file: Cycle 01
• User code selects yesterday’s data (IF DATEPART(ENDTS) EQ TODAY()-1 ;
• User code overwrites LPAR=’PHYSICAL’ to represent values for CPC level LPAR: ‘##CPC##’
• Derivations:

  DATE

  DATEPART(ENDTS)
  

  CPCID

  TRIM(LPCMOD)||'-'||TRIM(CPCMODID)||'-Serial: '||SUBSTR(CPCSEQNB,12,5);
  

Modifications

The following modifications can be made to the RMFCFG query:

• You can add filter statements to select only a single CPC, or set of CPCs using some of the identifying data elements shown in the CPCID derivation.
• If you do not have the DAYS timespan HARLPC file active, you can run the query against the DETAIL timespan, cycle 01.
• If you have no dedicated engines, you can delete the data extract step for the dedicated engine pool.