This query 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 query 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.
Note: 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.
|
Copyright © 2014 CA.
All rights reserved.
|
|