RMFOD3 - CPC LPAR Relative Weight by Engine Pool

The RMFOD3 inquiry shows the relative dispatch hierarchy for the shared LPARs defined to a CPC, based on the system programmer specified weights for each LPAR. LPAR weights are designated for each logical processor engine type assigned to each LPAR.
micsrm140
In the example, the fourth LPAR from the left, "CA31" has two logical processor engine types assigned -- CPs and zIIPs. Relative to the other LPARs defined to the CPC, the weights assigned to "CA31" tell PR/SM that when there is contention for the physical engines, "CA31" dispatches physical engines to handle its workloads about 25 percent of the time for both CP and zIIP processors. For the four LPARs that use IFL engines (green vertical bars), "SYSB" and "VMZ" are each dispatched about 32 percent of the time, while LPARS “SYSC” and “ZAWARE” are dispatched less frequently -- about 21 and 15 percent of the time, respectively.
RMFOD3  -  CPC LPAR Relative Weight by Engine Pool
Uses
This inquiry provides a useful overview of how PR/SM manages LPAR dispatching for the various LPARs when there is contention for the physical engines in the shared engine pools. The dispatch priority hierarchy, defined by these relative weight values, should be in agreement with the importance of the business critical applications dispatched on the various LPARs. If the shared engine pool for a particular processor type is heavily used, an LPAR that primarily runs discretionary workloads should not receive as large a percentage of engine dispatches as an LPAR that executes business critical workloads.
Charts
CPC LPAR Weights PCT by Engine Pool
A sample of RMFOD3 CPC LPAR Weights PCT by Engine Pool
Left Y-axis
PCTCPW
LPAR Pct CP Processor Weight Share
PCTZPAW
LPAR Pct zAAP Processor Weight Share
PCTZIPW
LPAR Pct zIIP Processor Weight Share
PCTIFLW
LPAR Pct IFL Processor Weight Share
PCTICFW
LPAR Pct ICF Processor Weight Share
X-axis
PRSMLPNM
Logical Partition Name
Inquiry Defaults
  • HARVPA DETAIL timespan file: Cycle 01
  • A Common Data Selection step selects yesterday’s data
  • Filters:
    • VPADEDCT EQ 0 - no dedicated LPARs
    • PRSMLPNM NE ‘PHYSICAL’ - eliminate physical (overhead) LPAR
    • PRSMLPTP EQ ‘CP’ or ‘ICF’ - only PR/SM managed LPARS
  • User code selects yesterday’s data (IF DATEPART(ENDTS) EQ TODAY()-1 ;
  • Derivations:
DATE
DATEPART(ENDTS);
CPCID
%CPCID ;
PCTCPW
IF PRSMTWGT AND CP_W THEN PCTCPW=ROUND((CP_W / PRSMTWGT * 100),0.1) ; ELSE PCTCPW=0 ;
PCTZAPW
IF PRSMZWGT AND ZAP_W THEN PCTZAPW=ROUND((ZAP_W / PRSMZWGT * 100),0.1) ; ELSE PCTZAPW=0 ;
PCTZIPW
IF PRSMSWGT AND ZIP_W THEN PCTZIPW=ROUND((ZIP_W / PRSMSWGT * 100),0.1) ; ELSE PCTZIPW=0 ;
PCTIFLW
IF PRSMNWGT AND IFL_W THEN PCTIFLW=ROUND((IFL_W / PRSMNWGT * 100),0.1) ; ELSE PCTIFLW = 0
PCTICFW
IF PRSMIWGT AND ICF_W THEN PCTICFW=ROUND((ICF_W / PRSMIWGT * 100),0.1) ; ELSE PCTICFW=0 ;
Note:
A user step sets CP_W, ZAP_W, ZIP_W, IFL_W, and ICF_W to the VPABPS (Partition Processor Weight) value for each individual engine type, per LPAR, in the HARVPA file. If an engine type is not present for an LPAR, the corresponding
xxx
_W element is set to zero.
Modifications
Modification considerations:
  • 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