Application Performance Analyzer for z/OS, Version 11.1, Customization Guide

Using the sysplex feature

This feature provides the ability to observe or sample and report on application programs that execute on an MVS™ system in a sysplex other than the one on which the user has started the Application Performance Analyzer user interface. To accommodate this feature, the Application Performance Analyzer started task will communicate with other instances of the Application Performance Analyzer started task on different MVS systems in the sysplex.

The communication between Application Performance Analyzer instances is facilitated by the implementation of an Application Performance Analyzer sysplex group. It is assumed that all images in a sysplex participate in DASD sharing. To take advantage of the sysplex support in Application Performance Analyzer, a unique instance of Application Performance Analyzer must be installed on every MVS system in the sysplex. Each of these instances must be defined to the same Application Performance Analyzer sysplex group during the installation of Application Performance Analyzer. Only one instance of Application Performance Analyzer on the same MVS system can be a member in the same Application Performance Analyzer sysplex group. You cannot have two or more instances of Application Performance Analyzer on the same MVS system as members of the same Application Performance Analyzer sysplex group.

See parameter "SPXGroupName" on the CONFIG BASIC statement in the member CAZCNFG0 in hlq.SCAZSAMP. This parameter is coded as "SPXGroupName=Sysplexname" and identifies the Application Performance Analyzer sysplex group of which the Application Performance Analyzer instance will be a member. The parameter can be a maximum of eight alphanumeric characters. All Application Performance Analyzer instances that will communicate with each other must code an identical "SPXGroupName=Sysplexname". The Application Performance Analyzer instances in an Application Performance Analyzer sysplex group must be from different MVS systems.

All Application Performance Analyzer instances defined in the same Application Performance Analyzer sysplex group must share a common checkpoint file and common data store file (if enabled). Therefore, it is important that the HLQ, UNIT, CheckpointDSN and CDS (common data store) parameters are identical. Failure to do so causes the started task to fail upon startup with an appropriate error message. Application Performance Analyzer's checkpoint file and common data store file use shared DASD on a sysplex to synchronize all the started tasks. It is important that you choose an HLQ that will allow Application Performance Analyzer to allocate all new data sets to volumes that are shared across the sysplex. These data sets include the checkpoint file, common data store file, sample files, and optional log files. For more information , see CONFIG BASIC statement.

In summary, the CONFIG BASIC statement for every Application Performance Analyzer instance defined in the same Application Performance Analyzer sysplex group must be coded identically, with the exception of the STCID, which might be unique.




Rate this page

[ Top of Page | Previous Page | Next Page | Contents | Index ]