The SMFDZI query 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 query 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 2817-615 CPC model, the normalization factor is 1.52734.
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. The second Q&R view for the address space type chart would show the breakdown for the eligible zIIP CPU time that executed on CP engines.
|
Copyright © 2014 CA.
All rights reserved.
|
|