RMFOD6 - Daily CPC MSU Use with Stacked LPARs

The RMFOD6 inquiry shows the average MSU usage for the Central Processing Complex (CPC) at an hourly or RMF interval level, with the individual LPAR usage broken out in each vertical bar.
micsrm140
All LPAR MSU usage is accounted for with the exception of LPARs that have only specialty engines, such as Coupling Facility LPARs with ICF engines only or Linux LPARs with IFL engines only. If an LPAR uses at least one general-purpose CP engine, it contributes to the chart. Two MSU utilization files are provided. One file generates daily charts for each CPC, and another extract generates a single chart for each CPC showing multiple days of activity if multiple HARLPC file cycles are input.
The inquiry produces a stacked vertical bar chart where each bar represents the average number of consumed MSUs stacked by interval for each LPAR.
The first example shows the average MSU usage for one day of an IBM z196 2817-715 CPC.
The second example shows three days of activity on the same CPC model. Notice that the X-axis label is expanded to show both the DATE, HOUR, and MINUTE of the vertical bars.
RMFOD6  -  Daily CPC MSU Use with Stacked LPARs
RMFOD6  -  Daily CPC MSU Use with Stacked LPAR2
Uses
The processing capacity of mainframe CPCs is expressed in MSUs (Millions of Service Units per Hour). This inquiry provides a CPC level view of MSU usage. The generated MSU charts have the same pattern as the daily CP engine utilization chart by hour generated by inquiry RMFODD because MSU usage is a derivative of CP engine usage. These charts help you see LPAR usage patterns relative to each other throughout the day. These charts can be compared to the MSU capacity of the CPC to help determine when an upgrade (or downgrade) is considered.
Charts
Daily MSU Use by CPC Stacked LPARs
A sample of RMFOD6 Daily MSU Use by CPC Stacked LPARs
Left Y-axis
LPCAVMSU
Avg Number of Consumed MSUs
X-axis
HHMM
Hour : Minute
Data element HHMM is derived by concatenating the HOUR and MINUTE of each RMF interval together, separated by a colon, HH:MM (for example, 14:59 meaning hour 14, 59th minute).
Multiday MSU Use by CPC Stacked LPARs
A sample of RMFOD6 Multiday MSU Use by CPC Stacked LPARs
Left Y-axis
LPCAVMSU
Avg Number of Consumed MSUs
X-axis
DATEHHMM
Date Hour Minute
Data element DATEHHMM is derived by concatenating the DATE, HOUR and MINUTE of each RMF interval together in the format YYYY.MM.DD-HH:MM.
Inquiry Defaults
  • HARLPC at the DAYS timespan file: Cycles 01 - 03
  • Filters: PRSMLPTP EQ ‘CP’ or PRSMLPTP EQ ‘PHY’ (select LPARs using CP engines)
  • Derivations:
CPCID
%CPCID ;
DATE
DATEPART(ENDTS);
HHMM
PUT(HOUR(ENDTS),Z2.) || ':' || PUT(MINUTE(ENDTS),Z2.);
DATEHOUR
PUT(DATEPART(ENDTS),YYMMDDD10.) || ':' || PUT(HOUR,Z2.) ;
DATEHHMM
PUT(DATEPART(ENDTS),YYMMDDP10.) || '-' || HHMM ;
Modifications
Modification considerations:
  • If you want to see hourly, rather than interval level MSU usage averages, you can change use the HARLPC DAYS timespan. If so, you may want to substitute the DATEHOUR element for the DATEHHMM element in the SUMMARIZATION and RMFOD6B macro.
  • If you want to see only yesterday’s data, a Common Data Selection Step after the file selection step to select the Previous Day.
  • You can increase or decrease the number of HARLPC file cycles to see more or fewer days of average MSU utilization.
  • Using the following CPC Identification data elements 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