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

Choosing a high-level qualifier for the Application Performance Analyzer Listener data sets

Application Performance Analyzer Listener might create additional data sets as part of its normal operation. The table shown below lists these data sets and indicates the names assigned by Application Performance Analyzer Listener.

Table 5. Application Performance Analyzer Listener Additional Data Sets
Data set name Description
yourhlq.LSRV####.@yymmdd.@hhmms Trace data sets
yourhlq.LLG.LiId.Dyyddd.Thhmm### or yourhlq.LLG..gen# Optional log data sets
yourdatahlq.userid.Rnnnn.XMIT or userid.Rnnnn.XMIT Data set name created by GUI export requests

By default, the trace data sets and log data sets use the value in the HLQ parameter coded in the Application Performance Analyzer Listener CONFIG BASIC statement. Optionally, a different trace yourhlq (HLQ=) and log yourhlq (LogHLQ=) can be specified on the CONFIG BASIC and CONFIG LOGFILE statements, respectively.

Application Performance Analyzer Listener creates an export (XMIT) data set for each successful export request issued by an Application Performance Analyzer GUI plugin user. By default, the high-level qualifier for the GUI exported data set is set to the GUI user's user ID connected to z/OS. Optionally, you might choose to specify a single high-level qualifier for all GUI export data sets. To do this, you choose a prefix that replaces the yourdatalhq symbol above by coding a value for the DataHLQ setting in the Application Performance Analyzer Listener CONFIG BASIC statement.

You choose a prefix that replaces the yourhlq symbol shown above. However, it must comply with the JCL rule for specifying a data set name. In this case, your prefix can have a maximum of 17 characters. This can be the same prefix as used by Application Performance Analyzer.

In the event that you execute multiple Application Performance Analyzer Listener started tasks, each one must be assigned its own unique yourhlq value. Each creates its own set of data sets. It is a useful convention to include the started task instance identifier as part of this prefix.




Rate this page

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