RMFODD - CPC and LPAR Daily Shared CP Engine Dispatch by Hour
The RMFODD inquiry creates a series of charts showing hourly CPC and LPAR level dispatch percentages for the shared CP (Central Processor) engine pool.
mics142
For each Central Processing Complex (CPC) encountered 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 CP engines for each hour of the day -- plus a horizontal reference line showing the total number of physical engines in the shared CP processor pool. Individual charts are also created for each LPAR in the CPC. These LPAR level charts show the dispatch percentages of the logical CP engines that are assigned to the LPAR. For the LPAR charts, the horizontal reference line shows the number of logical CP 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.
Notice in the second example (the LPAR level chart), LPAR CA31 shows that the number of logical CP engines that are assigned to the LPAR was six. The number of logical engines that are assigned to an LPAR can be modified with an operator command, or by a dynamic facility such as the Intelligent Resource Director (IRD).


Uses
This inquiry is used to monitor the overall shared CP pool engine utilization of each CPC at an hour granularity. The individual LPAR charts show to what extent each LPAR is using the logical CP engines available for its use. Even though the CPC level and LPAR level charts use the same chart variables, the actual values that are charted are different.
Charts
CPC and LPAR Daily CP 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: inquiry 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 CP Engine Dispatch (Set to PRSMTCDT - Total CP Dispatch Time / 3600)
ENGDISPE
Effective CP Engine Dispatch (Set to PRSMTCET - Total CP 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 CP 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 PRSMTCDT and PRSMTCET values for the LPAR equivalent data elements.
These actions result in a CPC level view of the physical shared CP engine pool dispatch activity. 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 physical engine dispatch hour equivalents. For example, three CP engines could, at full utilization, provide three hours of dispatch time in one hour.
LPCAVCPU
Avg Number of Active CP Processors (Set to PRSMACSP - Avg CP Shareable Processors))
This horizontal reference line, for the CPC level LPAR ##CPC##, shows the average number of physical processors in the shared CP engine pool. While the data extract plots data element LPCAVCPU, which is the average number of logical CP engines assigned to an LPAR -- for the ##CPC## chart, a user data step populates LPCAVCPU with the value for PRSMACSP -- which is the average number of physical engines in the shared CP 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 CP Engine Dispatch (Set to LPCTODTM - Total CP Processors Dispatch Time / 3600)
ENGDISPE
Effective CP Engine Dispatch (Set to LPCTOEDT - Total CP Proc. Effective Dispatch Time / 3600)
The vertical bars, for the LPAR level charts, show the total and effective dispatch of the
logical
CP processors that are 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 CP engines could, at full utilization, provide three hours of dispatch time in one hour.LPCAVCPU
Avg Number of Active CP Processors
This horizontal reference line, for the LPAR level charts, shows the average number of logical CP processors that are 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
DATA SOURCE (file/timespan):
- HARLPC at the DAYS timespan
- Filters:
- LPCTOEDT or LPCTODTM GT 0 or PRSMLPNM="PHYSICAL" (Non-zero effective or total dispatch times or the "PHYSICAL" LPAR)
- LPCDEDCT EQ 0; (no dedicated LPARS)
- PRSMTSCP GT 0; (at least one active physical CP engine in shared engine pool)
- A Common Data Selection step selects yesterday’s data
- Derivations:
DATE
DATEPART(ENDTS);
CPCID
%CPCID ;
ENGDISPE
ROUND((LPCTOEDT/3600),.1) ;
ENGDISPT
ROUND((LPCTODTM/3600),.1) ;
Run-Time Execution Parameter Overrides:
- UNIT
- Select one or moreMICS databaseunits by entering the data base IDs. Enter multiple IDs with a blank following each ID value.
- CYCLE RANGE
- Enter range ofMICSonline file cycles or enter ARCHIVE for archive files.
- SELECT YESTERDAY
- Specify whether to report only on observations with a time stamp from yesterday.
- Available values:
Y
- Yes
N
- No (default)Recommended Execution Time parameter setting for daily executions:
Set Cycle range to 01-02
Set Select Yesterday to Y