NeuMICS zAAP Processor Support

Document ID : KB000055604
Last Modified Date : 14/02/2018
Show Technical Document Details

The IBM S/390 Generation 6 Enterprise Servers (and some models of Generation 5) and later models like the zSeries provide the ability to configure their processors either as standard CP processors (CP) or as special purpose processors (ICF). The special purpose category includes the following types of engines: Integrated Coupling Facility (ICF), Integrated Facility for Linux (IFL), and Integrated Facility for Applications (IFA), also known as zSeries Application Assist Processor (zAAP).

With the advent of these lower cost, special purpose processors that are able to process workloads that were traditionally executed on standard CP processors, the measurements historically used to analyze PR/SM in LPAR mode have changed. In addition, zAAP processor utilization impacts Resource Accounting and Chargeback, as lower cost requires lower CPU rates for equitable charging. zAAP processors also need to be accounted for separately when performing capacity planning, as zAAPs can only be used for JAVA work, whereas standard processors can be used for all work, including JAVA. Thus, to properly address zAAP processors across the NeuMICS family, the following products required modification:

  • NeuMICS Hardware and SCP Analyzer
  • NeuMICS MVS Batch and Operations Analyzer
  • NeuMICS MVS Performance Manager
  • NeuMICS Accounting and Chargeback

Prior to the introduction of zAAP engines, CPU capacity tracking and planning for z/OS dealt with only one processor type, the standard CP (or general purpose) processor. We now have two types of processors that can be used by z/OS, and NeuMICS separates the measurements of each type to permit accurate LPAR utilization analysis.

NeuMICS Hardware and SCP Analyzer

Because zAAP processors have different operating characteristics compared to standard CPs (they basically run 100% busy, continuously looking for work), zAAP utilization metrics must be kept separate from standard CP processors' utilization metrics. The NeuMICS Hardware and SCP Analyzer therefore required substantial modification to:

  • Identify where work was performed (on a standard CP processor or on a IFA (or zAAP) processor)
  • Create new zAAP related data elements in order to provide the precision required for accurate performance and capacity planning decision-making
  • Clearly document the impact of zAAP processors when analyzing system performance

NeuMICS MVS Batch and Operations Analyzer

New data elements were added to multiple NeuMICS MVS Batch and Operations Analyzer files to support zAAP processors. Because the zAAP processor speed can differ from standard processor speed on certain z/Series models, CPU time as captured, as well as a computed "normalized" zAAP CPU time, has been made available. Additionally, CPU time for work that was eligible for zAAP processor execution, but instead executed on a standard processor, was captured and made available. zAAP eligible work may execute on a standard processor when the system level parameter IFACROSSOCER is set to YES.

NeuMICS Accounting and Chargeback

Normalization of zAAP processor CPU time and retention of standard CPU time for zAAP eligible work provides the ability to compute repeatable CPU times. Computation codes for these zAAP related CPU time data elements were added to the Chargeback and Accounting product, providing the ability to charge for zAAP processor use and produce repeatable charges in an environment where zAAP eligible work is allowed to execute on a standard CPU.

NeuMICS MVS Performance Manager

The NeuMICS MVS Performance Manager was modified to support planning for future zAAP deployment by determining how much zAAP eligible Java work is currently running on CP engines.

For environments with zAAP engines installed, reports show how the zAAP engines are performing, and indicate whether additional zAAP engines are needed to process the current workload.

The effect of zAAP processing on individual workloads can also be quantified, providing important input to the future growth planning process.

NeuMICS MVS Capacity Planner

zAAP processor data elements can also be valuable input to the NeuMICS Capacity Planning product. These elements can be used to gauge current and plan for future zAAP processor requirements.