Techdocs Library > Sizings > System zSeries zAAP Sizing Analysis

Document Author:	Robert Kohler		Document ID:	PRS2840
Doc. Organization:	Techline Americas		Document Revised:	04/15/2008
Product(s) covered:	# 2066; # 2084; # 2086; zSeries 800; zSeries 890; zSeries 900; zSeries 990; zSeries; z/OS

Abstract: zSeries zAAP Analysis sizing is a pre-sales effort to help you estimate the percentage of JAVA based workload and XML System Services that could be offloaded to zSeries zAAP processors. Various levels of sizing are available depending on the state of the customers applications, the customer's system software configuration and the customer's ability to produce, collect and submit actual performance data. The sizing information can then be used to estimate the number of zAAP engines necessary to support the targeted workload and the corresponding percentage of decrease in required general purpose processor resources.

Techline has multiple options for zAAP sizing depending on the customer's system software and application environment: The first step of the process is to clearly define the customer's environment to select the appropriate data collection process. In answering the following questions, they will guide you through the appropriate data collection and submission requirements. 1. Will this sizing be for a new application that is currently being designed? Yes or No For customers trying to estimate requirements for a new application being designed: IBM has developed standardized workloads that can be used to provide a rough estimate of the number of general purpose and zAAP processors. The customer must be able to characterize the makeup of the workload and have a rough application sizing in terms of MIPS requirements. We can then drive the customers parameters though the sample workload calculations to generate rough initial estimates of processor requirements. Requirements: Customer Sizing Questionnaire is needed to characterize the workload and provide MIPS requirements from the application sizing effort. Please contact me for information on obtaining the appropriate sizing documents. Reference: Techdocs WP100417 2. Will this sizing be for customers on z/OS 1.5 or older with JAVA applications currently in development? Yes or No For customers with Java applications in development and pre z/OS 1.6: Instrumented JAVA SDK's, either at version 1.3.1 at ptf UQ94379 or later or at version 1.4 and PTF UQ88783 or later can write projection data to the JAVA STDERR file. The targeted interval for data collection and subsequent projection should be after the application has stabilized and assumed a 'steady' state. Data should also be collected from each address space executing Java code by starting them with the Java start option - XIFA:projectx The data from the STDERR files which are then sent to IBM for analysis. These files are input to the zAAP Analysis worksheet, which will provide projections of the zAAP requirements for the measured workload(s). Requirements: Customer directions for data collection Techdocs - WP100431 Reference: Techdocs WP100417 & WP100431 3. Will this sizing be for customers on z/OS 1.5 or older with JAVA applications currently in production? Yes or No For customers with JAVA applications in production and pre z/OS 1.6 : Instrumented JAVA SDK's, either at version 1.3.1 at ptf UQ94379 or later or at version 1.4 and PTF UQ88783 will write projection data to the JAVA STDERR file. The period of data collection should be at least a 24 hour period consisting of a representative day and include processing peaks. Data should also be collected from each address space executing Java code by starting them with the Java start option - XIFA:projectx (where n is number of minutes in the log write interval). The statistics are written to the STDERR files, which are then sent to IBM for analysis. These files are input to the zAAP Analysis worksheet, which will provide projections of the zAAP requirements for the measured workload(s). Requirements: Customer directions for data collection Techdocs - WP100431 Reference: Techdocs WP100417 & WP100431 4. Will this sizing be for customers on z/OS 1.6 or newer with JAVA applications currently in production? Yes or No Customers with existing JAVA applications and z/OS 1.6 and later can submit SMF data for input to a more standardized capacity study utilizing CP3000 to project CP/zAAP requirements and also be able to demonstrate the effects of workload growth on these requirements. When zAAP processors are not already configured and active in the environment data should be collected from each address space executing Java code by starting the JVM's with the Java start option - Xifa:force. **** See note below **** Requirements: Customer requirements for Standard Data Collection for CP3000 Capacity Studies 5. Customers with existing JAVA applications and z/OS 1.6 and later can also submit RMF/CMF CPU and Workload Activity reports for input to zTPM to project CP/zAAP requirements and also be able to demonstrate the effects of workload growth on these requirements. When zAAP processors are not already configured and active in the environment data should be collected from each address space executing Java code by starting the JVM's with the Java start option - Xifa:force **** See note below **** Requirements: Customer requirements for Standard Data Collection for CP3000 Capacity Studies *** Note: z/OS V6 or V7 customer with the zIIP enabling FMID applied to their systems and PROJECTCPU enabled, and z/OS V8 customers who have *** PROJECTCPU enabled do not need to specify the Xifa:force JVM start parameter.

Classification:	Hardware; Software	Category:	Planning and Design
Platform(s):	IBM System z Family	S/W Pillar(s):	System z
O/S:	z/OS	Keywords:	z/OS, zAAP, JAVA, XML, Sizing, System z, z9