SMFOD0 - Daily zIIP CPU Use and Demand
Hourly actual zIIP engine use per day, and eligible use, for both the Central Processing Complex (CPC) and the z/OS LPARs

The SMFOD0 inquiry charts the hourly actual zIIP engine use per day, and eligible use, for both the Central Processing Complex (CPC) and the z/OS LPARs. In addition, the inquiry shows zIIP engine actual and eligible use by address space type (batch, TSO, started tasks, and so on).
The examples show CPC level zIIP engine demand for an IBM z196 2817-615.
The first chart shows the total hourly zIIP engine CPU time demand with actual zIIP engine use (blue) and eligible (red) using stacked vertical bars. The peak zIIP engine demand occurred during hour 16. At that hour, 2.65 hours of normalized zIIP engine CPU time were used, and 0.11 hours of CP engine time was used to execute zIIP eligible work. The normalization of zIIP CPU time is important for this CPC model because the CP engines run slower than the specialty (zIIP/zIIP) engines. When zIIP or zIIP CPU time is normalized, the value is expressed as the CP engine equivalent by multiplying by a normalization factor. For the 8561-608 CPC model, the normalization factor is 1.71875.
The second chart shows the actual zIIP CPU time use, broken down by address space type. Most zIIP engine demand on the CPC shown came from started task address spaces (dark blue), with TSO sessions (cyan), batch (red), and USS workloads (green) accounting for the additional demand.
Uses
This inquiry is used to determine if the zIIP engines in a CPC are sufficient to handle the zIIP eligible workload running on z/OS LPARs. The inquiry also shows you what address space types in your workload mix execute zIIP engine eligible code. Even if no zIIP engines are present in a CPC, the charts show z/OS LPAR zIIP eligible work that executed on CP engines. zIIP engines are less expensive that CP engines. Reducing CP engines in a CPC can reduce software licensing fees. In general, if significant zIIP eligible work is executing on CP engines, it is cost effective to add zIIP engines to the CPC..
The sample charts were generated for a CPC that is configured with several zIIP engines, no zAAP engines, and has ZIIPZIIP=YES specified in SYS1.PARMLIB, With this configuration, zIIP engines process all specialty engine work—including work that would normally run on zAAP engines. In this environment, the operating system treats both zIIP and zAAP eligible workloads as zIIP eligible. No zAAP actual or eligible information is recorded in SMF and RMF workload activity records. Therefore, some portion of the zIIP actual and eligible demand shown in the sample charts may be associated with zAAP eligible workloads.
Charts
This inquiry produces the following charts:
SMF Daily Actual Normalized zIIP CPU Time Used

Left Y-axis
- PGMSPNTM
- Normalized zIIP CPU Time
X-axis
- HOUR
- Hour of Day
SMF Daily Eligible zIIP CPU Time Executed on CP Engines

Left Y-axis
- PGMSUCTM
- zIIP Eligible CPU Time on a CP
X-axis
- HOUR
- Hour of Day
SMF Daily zIIP CPU Use and Demand CPCID

Left Y-axis
- PGMSPNTM
- Normalized zIIP CPU Time
- PGMSUCTM
- zIIP Eligible CPU Time on a CP
X-axis
- HOUR
- Hour of Day
SMF Daily zIIP CPU Use and Demand SYSID

Data Source
- BAT_OE at the Detail Timespan
- BAT_SA at the Detail Timespan
- BAT_ST at the Detail Timespan
- BAT_TP at the Detail Timespan
- BAT_TS at the Detail Timespan
- BATPGM at the Detail Timespan
Inquiry Defaults
- Filters: PGMSUPTM GT 0 OR PGMSUCTM GT 0 (only zIIP actual or eligible CPU time)
- Derivations:
CPCID
%CPCID (macro CPCID generated by sp.MICS.MACAUTOS(CPCIDFMT))
Date
DATEPART(ENDTS) ;
ADDRTYP
IF PGMTYPE=1 THEN ADDRTYP='Batch' ; ELSE IF PGMTYPE=2 THEN ADDRTYP='TSO' ; ELSE IF PGMTYPE=3 THEN ADDRTYP='Started Task' ; ELSE IF PGMTYPE=4 THEN ADDRTYP='APPC' ; ELSE IF PGMTYPE=5 THEN ADDRTYP='Unix SysSrv' ; ELSE IF PGMTYPE=6 THEN ADDRTYP='System Addr' ; ELSE ADDRTYP= 'UNKNOWN' ;
Modifications
The following modifications can be made to the SMFOD0 inquiry:
- 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)