RMFODP - z/OS Report Class Analysis by SYSPLEX, CPCID, and SYSID

The RMFODP inquiry displays resource usage, performance indicators, summary sampled state percentages, and detailed execution delay state information for each Workload Manager (WLM) Report Class or Report Class Period.
mics142
3
2
The inquiry produces vertical bar charts. The SYSID level shows the total CP, zIIP, and zAAP times stacked for each hour of the day.
The RMFODP information is provided by the following three data extracts at the z/OS LPAR (SYSID), Central Processing Complex (CPC), and SYSPLEX levels:
  • Report Class by SYSPLEX
  • Report Class by SYSPLEX CPCID
  • Report Class by SYSPLEX CPCID SYSID
Each data extract generates the following four chart views:
  • CPU and PI
  • Sampling Summary
  • Exec Delay States Group 1
  • Exec Delay States Group 2
Refer to the RMFODR - z/OS Service Class Analysis by SYSPLEX, CPCID, and SYSID inquiry description for information about each of these chart views. The chart views and individual chart content for the RMFODR and these RMFODP inquiries are almost identical. The only difference is in the title area and relates to the type of the charted Report Classes.
WLM Report Classes can be homogeneous or heterogeneous. Homogeneous Report Classes are defined to include workloads from a single Service Class. Heterogeneous Report Classes are defined to include workloads that span two or more Service Classes.
For both homogeneous and heterogeneous Report Classes, the title area of each chart shows the SYSPLEX name, Report Class Name, Relative Importance, Goal Type, and Report Class period charted. For homogeneous Report Classes, all of these fields will be populated.
For heterogeneous Report Classes, the Relative Importance and Goal Type values will be blank and the Report Class Period value will show a value of 1 (one). This is because heterogeneous Report Classes include workload information drawn from multiple Service Classes that could have different importance levels, goal types, and periods.
Both chart samples shown previously are charts that are generated from the data extract Report Class by SYSPLEX CPCID.
The first chart shows an example of a homogeneous Report Class, Report Class DATABASE. As you can see, all values in the chart title area are populated.
The second chart sample above shows an example of a heterogeneous Report Class, Report Class SYSTEST. You can see that the Relative Importance and Goal Type are blank, the period reported is 1, and the Performance Index is missing.
ch679.png
ch712.png
Uses
Refer to the RMFODR - z/OS Service Class Analysis by SYSPLEX, CPCID, and SYSID inquiry description for information about the use of this RMFODP inquiry. The chart views and individual chart content for the RMFODR and these RMFODP inquiries are almost identical.
While Service Classes must be defined, Report Classes are optional, user-defined reporting groups. Report Classes allow the analyst to report on a specific set of workloads. These workloads might be a sub-set of the workloads belonging to a single Service Class, or may span two or more Service Classes.  When the WLM Report Class is heterogeneous (spanning more than one Service Class), the Goal Type and Relative Importance are unreliable and therefore are missing values in the charts.
To be efficient, the number of Service Classes that are defined for a specific WLM Policy must be limited. A typical Service Policy may have only 30 to 40 Service Classes defined. But up to 999 Report Classes may be defined, providing the user with a powerful tool to track the performance of specific, mission critical applications.
When the workloads assigned to a Report Class are a subset of a single Service Class (for example, a Report Class that selects a single CICS region belonging to the Service Class PRODCICS), the Report Class is homogeneous. Information about the Report Class data includes Importance Level, Period level records, Goal, and Performance Index information.
In the CPU and PI chart, the CPU time for general processor CP, zIIP, and zAAP cores are charted, along with the Performance Index (PI) (for homogeneous report classes) are displayed for each Report Class Period. The CPU times used for each processor engine type are stacked and are scaled using the left Y-axis. The left Y-axis is delivered with fixed values over all charts, showing 0 to 5 hours of CPU time. The vertical bars show the total CPU time used by each Report Class for the three core types (CP, zIIP, and zAAP). By using a fixed axis, you can easily visually identify Service Classes that use significant amounts of CPU time. If the aggregate amount of CPU time used by Report Classes at your site exceeds 5 hours over one hour of clock time, you will want to adjust the left-Y axis max value higher. Similarly, if the Report Class using the most CPU time in your SYSPLEX uses significantly less than 5 hours of CPU time per clock hour, you will want to adjust the left-Y axis max value lower.
Two lines are plotted against the right Y-axis scale - the Performance Index (PI) for the SCP, and a Performance Index "goal met" reference line, set to 1. To prevent scaling issues, PI values greater than 5 are set to 5. PI values between zero (0) and one (1) mean that the Report Class exceeded the specified performance goal. A value equal to 1 means that the goal was met exactly. Values greater than 1 means that the specified performance goal was not met. The PI cannot be computed for certain goal types such as DISCRETIONARY and SYSTEM SPECIFIED.
By design, SYSPLEXes can span Central Processing Complexes. If your SYSPLEXES do not span CPCs, then the first chart sets are identical, with the exception that the second data extract, Report Class by SYSPLEX CPCID, identifies the CPC in each chart title. If your SYSPLEXes do span CPCs, then the Report Class by SYSPLEX CPCID data extract displays multiple charts for a Report Class that ran on multiple CPCs.
Charts
Report Class by SYSPLEX - CPU and PI
RMFODP Report Class by SYSPLEX - CPU and PI.png
Note:
RCP = Report Class Period
Left Y-axis
SECCPUTM
CPU Time on CP
SECSUPTM
CPU Time on zIIP (Normalized)
SECZAPTM
CPU Time on zAAP (Normalized)
Right Y-axis
SECPINDX
Performance Index
Performance Index Reference - value set to
X-axis
HHMM
Hour: Minute
Report Class by SYSPLEX - Sampling Summary
RMFODP Report Class by SYSPLEX - Sampling Summary.png
Left Y-axis
SEDPCUSE
Pct Total WLM Using Samples (derived in inquiry code)
SEDPCDUN
Pct Wait - Unknown
SEDPCSAM
Pct Total Execution Delay Samples (derived in inquiry code)
Right Y-axis
SECPINDX
Performance Index
Performance Index Reference - value set to 1
X-axis
HHMM
Hour: Minute
Report Class by SYSPLEX - Exec Delay States Group 1
RMFODP Report Class by SYSPLEX - Exec Delay States Group 1.png
Left Y-axis
SEDPCDCP
PCT Wait - CPU on CP
SEDPCSUD
PCT Wait - CPU on zIIP
SEDPCZPD
PCT Wait - CPU on zAAP
SEDPCAMD
PCT Wait - Crypto AM Processor
SEDPCAPD
PCT Wait - Crypto Assist Processor
SEDPCCRD
PCT Wait - Crypto Processors
SEDPCCOD
PCT Wait - Resource Contention
SEDPCDCC
PCT Wait - CPU Capping
SEDPCDQU
PCT Wait - Quiesce
SEDPCDMP
PCT Wait - MPL Delay
SEDPCSMP
PCT Wait - Server MPL
SEDPCDRG
PCT Wait - Resource Group Capping
SEDPCDSD
PCT Wait - DASD I/O Delay
SEDPCSQU
PCT Wait - Server Queue Delay
Right Y-axis
SECPINDX
Performance Index
Performance Index Reference - value set to 1
X-axis
HHMM
Hour: Minute
Report Class by SYSPLEX - Exec Delay States Group 2
RMFODP Report Class by SYSPLEX - Exec Delay States Group 2.png
Left Y-axis
SEDPCDES
Pct Wait - ESO Hiperspc Pg-In from Aux
SEDPCDHS
Pct Wait - Std Hiperspc Pg-In from Aux
SEDPCDPC
Pct Wait - CSA Page-In from Aux
SEDPCDPP
Pct Wait - Pvt Page-In from Aux
SEDPCDSI
Pct Wait - Swap-In
SEDPCDVI
Pct Wait - VIO Page-In from Aux
SEDPCDXM
Pct Wait - Cross Mem Page-In from Aux
SEDPCSHP
Pct Wait - Server Hiperspace Paging
SEDPCSPP
Pct Wait - Server Private Area Paging
SEDPCSSI
Pct Wait - Server Swap-In
SEDPCSVP
Pct Wait - Server Space VIO Paging
Right Y-axis
SECPINDX
Performance Index
Performance Index Reference - value set to 1
X-axis
HHMM
Hour: Minute
Report Class by SYSPLEX CPCID
At the Report Class by SYSPLEX CPCID level, charts are provided using the same Y and X axis charted data elements, as those described for data extract Report Class by SYSPLEX.
The only difference is that additional charts are generated if the SYSPLEX spans multiple CPCs. The chart granularity for the SYSPLEX level chats followed this pattern:
RMFODP Report Class by SYSPLEX CPCID 1.png
The chart granularity for the Report Class by SYSPLEX CPCID charts follows this pattern:
RMFODP Report Class by SYSPLEX CPCID 2.png
If a SYSPLEX spans two or more CPCs, more SYSPLEX CPCID level charts will be generated than at the SYSPLEX level.
If a SYSPLEX does not span CPCs, however, the number of unique charts generated by the SYSPLEX level and SYSPLEX CPCID level output is identical.
Report Class by SYSPLEX CPCID SYSID
Data extract Report Class by SYSPLEX CPCID SYSID provides the same four chart views, with charts displaying the same Y and X axis charted data elements, as those described for data extract Report Class by SYSPLEX.
The only difference is that additional charts are generated if the SYSPLEX spans multiple CPCs, or multiple z/OS LPARs.
The chart granularity for the SYSPLEX level data extract followed this pattern:
RMFODP Report Class by SYSPLEX CPCID SYSID 1.png
The chart granularity for the Report Class by SYSPLEX CPCID SYSID data extract follows this pattern:
RMFODP Report Class by SYSPLEX CPCID SYSID 2.png
With this data extract, you can examine the performance of each Report Class Period on each z/OS LPAR.
Inquiry Defaults
DATA SOURCE (file/timespan):
  • WLM_EC at the DAYS timespan
  • WLM_ED at the DAYS timespan
  • Filters: Empty Filter tasks provided as a placeholder for user WLM_EC and WLM_ED file filtering to exclude/select specific SYSPLEXs, SYSIDs, ZONEs, and so on.
  • 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 ;
SECFILE
1 ; Used after MERGE of WLM_EC and WLM_ED files to limit charting to observations that contained WLM_EC file data.
SEDPCSAM
100 * SEDTOSAM / SEDTOSST;
SEDPCUSE
100 * SEDTOUSE / SEDTOSST;
Run-Time Execution Parameter Overrides:
Unit
Select one or more
MICS database
units by entering the data base IDs. Enter multiple IDs with a blank following each ID value.
CYCLE RANGE
Enter range of
MICS
online 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)
SYSPLEX
Enter SYSPLEX name or leave blank to chart all SYSPLEX's.
LEFT-Y AXIS SCALE
Specify the maximum Left-Y axis chart value for the REPORT Class CPU and PI charts. The default is 5 hours. If you have report CPU time in an hour, you can increase the maximum scale, or lower the scale to a value that would be more representative of your workloads. Specifying a value of zero (0) removes the maximum scaling and lets SAS adjust the scale based on the data charted.
  • 5 - Maximum Left-Y axis (default)
  • 0 - SAS automatic scaling
Recommended Execution Time parameter setting for daily executions:
  • Set Cycle range to 01-02
  • Set Select Yesterday to Y
SASLOG WARNING messages and incomplete charts
Warning messages may appear for data elements SECPINDX and REFPINDX.  These data elements will contain missing values for heterogeneous report classes and certain goal types.                                          
Sample SAS Warning messages might include:
WARNING
Y='element name' is invalid. The option expects at least one non-missing value in the column.