This chapter describes where Application Performance Analyzer for z/OS messages are
logged, and lists the message IDs and descriptions.
The Application Performance Analyzer for z/OS started task logs informational, error and diagnostic
messages to various JES destinations The contents of these output
files are described here by their ddnames:
- JESMSGLG
- All critical messages will appear in JES Message Log. If the
started task fails to start successfully, look in JES Message Log
for messages reporting the failure.
- COMMANDS
- Any commands processed by the started task (external or internal)
are logged to this file. The command text is displayed here, as well
any message associated with the command.
- LOGR, MAIN, LOAD, CMDP, CHKP
- Each of these represents a single subtask attached by the Application Performance Analyzer for z/OS started
task and contains messages logged by that task. These are primarily
informational messages and during normal operations you need not be
concerned with the contents of these files. They can be useful during
problem diagnosis.
- REQ#request_number, DATWrequest_number,
ESDErequest_number, HVXTrequest_number
- The Application Performance Analyzer for z/OS started task will allocate up to four sysout
data sets for each sampling request submitted by a user. These data
sets have the following format:
REQ#request_number
DATWrequest_number
ESDErequest_number
HVXTrequest_number
Where request_number represents
the sampling request number. These are primarily informational messages
and during normal operations you need not be concerned with the contents
of these files. They can be useful during problem diagnosis.
- REQ#request_number
- Contain messages related to the sampling phase of a sampling
request.
- DATWrequest_number
- Contain messages related to the sample file creation phase of
the sampling request.
- ESDErequest_number
- Contain messages related to the load module analysis phase of
the sampling request.
- HVXTrequest_number
- Contain messages related to the SQL host variable name resolution
phase of the sampling request. This sysout is allocated when the DB2V
Extractor is selected.
Messages are sorted in alphanumeric order.