RMFODG - CPC and LPAR Daily Shared IFL Engine Dispatch by Hour

The RMFODG inquiry creates a series of charts showing hourly CPC and LPAR level dispatch percentages for the shared IFL (Integrated Facility for Linux) engine pool.
micsrm140
For each Central Processing Complex (CPC) in the DAYS timespan HARLPC file, the inquiry generates a CPC level chart. The chart uses vertical bars to show the total and effective dispatch percentage of the physical IFL engines for each hour of the day -- plus a horizontal reference line showing the total number of physical engines in the shared IFL processor pool. Individual charts are also created for each LPAR in the CPC. These LPAR level charts show the dispatch percentages of the logical IFL engines that are assigned to the LPAR. For the LPAR level charts, the horizontal reference line shows the number of logical IFL engines active for the LPAR.
The difference between total and effective dispatch represents the amount of the engine resource pool that is required for multiprocessing management overhead.
RMFODG  -  CPC and LPAR Daily Shared IFL Engine Dispatch by Hour
RMFODG  -  CPC and LPAR Daily Shared IFL Engine Dispatch by Hour 2
Uses
This inquiry is used to monitor the overall shared IFL pool engine utilization of each CPC at an hour granularity. The individual LPAR views show to what extent each LPAR is using the logical IFL engines available for its use. Even though the CPC level and LPAR level charts use the same chart variables, the actual values charted are different.
Charts
CPC and LPAR Daily IFL Engine Dispatch
A sample of RMFODG CPC and LPAR Daily IFL Engine Dispatch
A series of charts are created for each CPC, with the first chart showing CPC level information and the remaining charts in the series showing information for each LPAR. The following information is presented in two parts: one describing the element values plotted for the CPC level chart, and the other describing the element values plotted for the individual LPARs.
CPC level chart
For the CPC level chart, CPC level PR/SM data element values are substituted for the LPAR data elements:
Left Y-axis
ENGDISPT
Total IFL Engine Dispatch (Set to PRSMTNST - Total IFL Dispatch Time - Shared / 3600)
ENGDISPE
Effective IFL Engine Dispatch (Set to PRSMTNET - Total IFL Dispatch Time - Effective / 3600)
These vertical bars, for the CPC level LPAR ##CPC##, show the total and effective dispatch of the physical processors in the entire shared IFL engine pool. For this chart, a user data step takes the following actions before the ENGDISPT and ENGDISPE derivations:
  • Overwrite the ‘PHYSICAL’ LPAR observation.
  • Change the LPAR name to ‘##CPC##’.
  • Substitute PRSMTNST and PRSMTNET values for the LPAR equivalent data elements.
This process permits a CPC level view of the physical shared IFL engine pool dispatch activity. The total and effective dispatch times are divided by 3600 to convert from seconds of dispatch to hours of dispatch. Since one engine can be dispatched a maximum of one hour, per hour, this conversion allows the dispatch of the engine pool to be represented as physical engine dispatch hour equivalents. For example, three IFL engines could, at full utilization, provide three hours of dispatch time in one hour.
LPCAVIFL
Avg Number of Active IFL Processors (Set to PRSMANSP - Avg IFL Sharable Processors)
This horizontal reference line, for the CPC level LPAR ##CPC##, shows the average number of physical processors in the shared IFL engine pool. While the data extract plots data element LPCAVIFL, which is the average number of logical CP engines assigned to an LPAR - for the ##CPC## chart, a user data step populates LPCAVIFL with the value for PRSMANSP - which is the average number of physical engines in the shared IFL engine pool. The actual dispatch engine equivalents, charted with the vertical bars, can reach, but should never exceed this line. IBM features like capacity provisioning and on/off capacity on demand can activate and deactivate physical processors -- so this line may not reflect a constant value over the entire day.
X-axis
HOUR
Hour of Day
LPAR level charts
The LPAR level charts use standard HARLPC file data elements, to derive the dispatch variables:
Left Y-axis
ENGDISPT
Total IFL Engine Dispatch (Set to LPCSNDTM - Total shared IFL Proc. Dispatch Time / 3600)
ENGDISPE
Effective IFL Engine Dispatch (Set to LPCSNEDT - Total Shr IFL Proc. Effec. Dispatch Time / 3600)
The vertical bars, for the LPAR level charts, show the total and effective dispatch of the logical IFL processors assigned to the LPAR. The total and effective dispatch times are divided by 3600 to convert from seconds of dispatch to hours of dispatch. Because one engine can be dispatched a maximum of one hour, per hour, this conversion allows the dispatch of the engine pool to be represented as logical engine dispatch hour equivalents. For example, three logical IFL engines could, at full utilization, provide three hours of dispatch time in one hour.
LPCAVIFL
Avg Number of Active IFL Processors
This horizontal reference line, for the LPAR level charts, shows the average number of logical IFL processors assigned to the LPAR. The actual dispatch engine equivalents, charted with the vertical bars, can reach, but should never exceed this line. IBM features like the Intelligent Resource Director (IRD) can activate and deactivate logical processors at the LPAR level -- so this line may not reflect a constant value over the entire day.
X-axis
HOUR
Hour of Day
Inquiry Defaults
  • HARLPC DAYS timespan file: Cycles 01 and 02
  • Filters:
    • LPCSNEDT or LPCSNDTM GT 0 or PRSMLPNM="PHYSICAL" (Non-zero dispatch times for IFL engines or the "PHYSICAL" LPAR)
    • LPCDEDCT EQ 0 ; (no dedicated LPARS)
    • PRSMTNSP GT 0 ; (at least one active physical IFL engine in shared engine pool)
  • A Common Data Selection step selects yesterday’s data
  • Derivations:
DATE
DATEPART(ENDTS) ;
CPCID
%CPCID ;
ENGDISPE
ROUND((LPCSNEDT/3600),.1) ;
ENGDISPT
ROUND((LPCSNDTM/3600),.1) ;
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