Refer to the RMFSRV – z/OS Service Class Analysis by SYSPLEX, CPCID, and SYSID query description for information about the use of this RMFRPT query. The chart views and individual chart content for the RMFSRV and this RMFRPT queries 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 a sub-set of the workloads belonging to a Service Class, or may span two or more Service Classes.
To be efficient, the number of Service Classes 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 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 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.
While CPU time is the default resource usage metric plotted in the CPU and PI view, the Data Extract CSV provides a number of other resource usage metrics that can be alternatively selected for charting. These metrics include DASD Service time, paging rates, and average storage used.
Note: By design, SYSPLEXES can span Central Processing Complexes. If your SYSPLEXES do not span CPCs, then the first two data extracts 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.
|
Copyright © 2014 CA.
All rights reserved.
|
|