System z integrated information processor (ziip)

Enhancements in z/OS components now enable both projected and actual zIIP usage reporting, aiding in zIIP planning efforts. The PROJECTCPU function specifically aims to collect data on CPU time for code that could potentially run on zIIPs.

Capacity Planning

For detailed guidance, refer to the Capacity Planning for zAAP and zIIP Specialty Engines documentation.

Configuration Note

Activating the PROJECTCPU=YES option in the IEAOPTxx parmlib member instructs z/OS to log work that could be processed by zIIP (and zAAP) processors. This data feeds into the RMF post processor through SMF Record Type 72 subtype 3. The resulting Workload Activity Report, which organizes workloads by WLM service class, includes the APPL% IIPPCP field to show the percentage of a processor's work that is zIIP eligible. Similarly, APPL% AAPCP reflects zAAP eligibility. For more granular insights, SMF Record Type 30 delves into specific address spaces. Notably, even a 25% eligibility in either APPL% AAPCP or APPL% IIPPCP could justify investing in new zAAP or zIIP processors.

For those already utilizing zIIPs, these reporting capabilities offer valuable data for refining current setups or forecasting future needs.

zIIP Assisted IPSec Planning

For initial sizing guidance tailored to your workload, consult the technical papers available in the underResources section.