Using the sysplex feature

This feature provides the ability to measure jobs, started tasks and TSO address spaces, and to view the resultant reports on any system in a sysplex, regardless of the system on which the user is currently logged. To accommodate this feature during customization, Application Performance Analyzer must be defined with the ability to communicate with other instances of Application Performance Analyzer on different systems in a sysplex.

The communication between Application Performance Analyzer instances on different systems is facilitated by the use of an Application Performance Analyzer sysplex group. A unique instance of Application Performance Analyzer must be installed on every system in a sysplex and each of these instances must be defined to the same Application Performance Analyzer sysplex group. Only one instance of Application Performance Analyzer on the same system can be a member in the same Application Performance Analyzer sysplex group.

An Application Performance Analyzer sysplex group is defined during customization using the “SPXGroupName” configuration setting on the CONFIG BASIC statement. This parameter is coded as "SPXGroupName=apaspxgp". All Application Performance Analyzer instances that you want to communicate with each other must code an identical "SPXGroupName=apaspxgp". The value of apaspxgp must be unique to Application Performance Analyzer and must not be the sysplex name of the system.

All Application Performance Analyzer instances defined in the same Application Performance Analyzer sysplex group must share a common checkpoint file and Common Data Store (CDS). Therefore, it is critical that the HLQ, UNIT, CheckpointDSN, and CDS parameters are identical. Failure to do so causes the started task to fail upon startup with an appropriate error message. The Application Performance Analyzer sysplex feature requires that all systems in a sysplex participate in DASD sharing. It is important that you choose an HLQ, UNIT, CheckpointDSN, and CDS that will allow Application Performance Analyzer to allocate all new data sets to volumes that are shared across the systems in the sysplex. For more information, see CONFIG BASIC statement.

In summary, it is a good practice to define identical CONFIG BASIC statements for every Application Performance Analyzer instance participating in the same Application Performance Analyzer sysplex group, with the exception of the STCID, which might be unique.