The SMFDZA query charts the hourly actual zAAP engine use per day, and eligible use, for both the Central Processing Complex (CPC) and the z/OS LPARs. In addition, the query shows zAAP engine actual and eligible use by address space type (batch, TSO, started tasks, and so on).
The examples show CPC level zAAP engine demand for an IBM z10 2097-407.
The first chart shows the total hourly zAAP engine CPU time demand with actual zAAP engine use (blue) and eligible (red) using stacked vertical bars. The peak zAAP engine demand occurred during hour 13. At that hour, 2.68 hours of normalized zAAP engine CPU time were used. The normalization of zAAP CPU time is important for this CPC model because the CP engines run slower than the specialty (zIIP/zAAP) engines. When zIIP or zAAP CPU time is normalized, the value is expressed as the CP engine equivalent by multiplying by a normalization factor. For the 2097-407 CPC model, the normalization factor is 4.210938.
The second chart shows the actual zAAP CPU time use, broken down by address space type. All zAAP engine demand on the CPC shown came from started task address spaces. The second Q&R view for the address space level chart would show the breakdown for any eligible zAAP CPU time that executed on CP engines.
|
Copyright © 2014 CA.
All rights reserved.
|
|