CA MICS Hardware and SCP Analyzer (RMF) Queries › Mainframe CPC Specialty Engine Focus › RMFZAS – Daily zAAP Engine Use and Demand by Service Class

RMFZAS – Daily zAAP Engine Use and Demand by Service Class

Overview

The RMFZAS query charts the hourly total zAAP engine demand (actual zAAP engine use plus zAAP engine eligible use), by WLM Report Class, for the Central Processing Complex (CPC) and individual z/OS LPARs using the shared engine pools of a CPC. Only PR/SM managed z/OS LPARs contribute to these charts because the data containing zAAP engine demand, extracted from the WLMSEC Report Class Resource Consumption file, is derived from RMF type 72-3 records, which only record zAAP engine demand for PR/SM managed z/OS LPARs.

The example shows the CPC level chart (top) for an IBM z/10 2097-712 CPC, and one of the individual LPAR charts for an LPAR defined to that CPC.

Both the CPC level and SYSID level charts show total hourly zAAP engine demand, using vertical bars, stacked by WLM Report Class.

Note: A fake Report class named ‘*NO ZAP*’ is created, showing no usage, for hours where there was no zAAP engine demand. This class prevents charts from being produced where hours are missing from the X-axis.

Uses

This query is used to examine the WLM Report Classes that execute zAAP engine eligible work. If zAAP usage appears for an LPAR that does not have zAAP engines assigned, then the work is actually executing on expensive CP engines. You may want to reconfigure the LPAR with one or more zAAP engines, or reroute the Report Class workload to execute on an LPAR with zAAP engines. The charts as delivered show total demand—which is the sum of zAAP engine actual use plus any zAAP engine eligible use that executed on CP engines. The two components—actual use and eligible use are available for charting, and can be selected as the Y-axis chart variables if desired. Additionally, you can review the RMFZAC - Daily zAAP Engine Use and Demand by CPC and SYSID query charts. These charts show the breakdown of actual and eligible zAAP engine demand in a single chart.

Note: If a CPC has one or more zIIP engines and no zAAP engines, and has specified ZAAPZIIP=YES in SYS1.PARMLIB, zIIP engines process all specialty engine work—including work that would normally run on zAAP engines. In this environment, all SMF and RMF metrics treat zAAP and zIIP eligible workloads as zIIP eligible. No zAAP actual or eligible demand appears.

Data Extracts

Daily Total zAAP Demand by Service Class

Left Y-axis

ZAPENGT – Total zAAP Engine Demand Actual+Eligible

The vertical bars show total zAAP usage (zAAP actual+eligible CPU time) at the CPC level and for each PR/SM managed z/OS LPAR. For each CPC, the CPC level chart is produced first, with a SYSID value of ‘#CPC’, and is followed by the PR/SM managed z/OS LPARs for that CPC. The CPU times are divided by 3600 to convert from seconds to hours to create the chart variable ZAPENGT. Because one engine can be dispatched a maximum of one hour, per hour, this conversion allows the zAAP engine demand to be represented as physical engine hour equivalents. For example, two zAAP engines could, at full utilization, provide two hours of CPU time in one hour.

X-axis

HOUR – Hour of Day

Query Defaults

• HARCPU DAYS timespan file: Cycles 01 -02
• WLMSEC DAYS timespan file: Cycles 01-02
• Filters: PRSMUSCT GT 0 (only PR/SM managed LPARs)
• User code selects yesterday's data (IF DATEPART(ENDTS) EQ TODAY()-1 ;
• Derivations:

  CPCID

  TRIM(LPCMOD)||'-'||TRIM(CPCMODID)||'-Serial: '||SUBSTR(CPCSEQNB,12,5);
  

  ZAPENGT

  SUM(ZAPENGA,ZAPENGE) ;
  

  ZAPENGA

  ROUND((SECZAPTM/3600),.001);
  

  ZAPENGE

  ROUND((SECZAPCT/3600),.001) ;
  

Modifications

The following modifications can be made to the RMFZAS query:

• You can increase the number HARCPU and WLMSEC DAYS timespan cycles input, but comment out the user code in each file selection step that selects yesterday's data.
• You can use a filter statement to restrict data to focus on a particular time range (for example, HOUR GE 8 AND HOUR LE 17) or particular time zone (for example, ZONE EQ 1)
• You can add filter statements to select only a single CPC, or set of CPCs using the identifying data elements shown in the CPCID derivation.
• If you want to generate these charts to see either the zAAP engine actual use or zAAP engine eligible use, change the Y-axis variable charted. The default is ZAPENGT, but ZAPENGA or ZAPENGE can be selected.