Documentation needed for an authorized program analysis report

If IBM® opens an authorized program analysis report (APAR) addressing your problem, be prepared to supply the following information:

Customer number
Version
Release and modification level
Keyword string used to search IBMLink/ServiceLink
Current maintenance level, obtained with the MODLEVEL parameter of the DISPLAY command described in DISPLAY: Displaying DFSMShsm storage locations.

You will also be asked to supply various types of information that describe the:

DFSMShsm functions used
Database used
Environment
Activities.

Applicable items of information from the following list may also be requested:

JCL listings (for a failure related to a BATCH job).
System console log.
The related FSRs, DSR, and VSRs from SMF. You can use the SETSYS SMF command to extract these records.
The command activity log, if appropriate.
The specific activity log, if appropriate.
PDA trace.
A copy of any traces or SYS1.DUMPs taken.
A DFSMSdss logical dump of the data set on tape, if the problem relates to a specific data set.
For a wait failure, a complete description of the resource being waited for and the program module that is waiting.
An MVS™ DUMP command must be issued prior to canceling DFSMShsm. Specify the DUMP options as follows:
jobname—

specifies the name of the job associated with the address space you want to dump (for example, DFHSM or DFHSMABR).

sdata—

specifies the specific storage areas you want to dump. The options are CSA, GRSQ, LSQA, PSA, RGN, SQA, SUM, SWA, and TRT.

For information about DUMP options and their definitions, see the section titled "DUMP Commands" in z/OS MVS System Commands.
For LOOP failures, an indication of the location of the loop. This information can be taken from console trace addresses or it can be one or more module names taken from the PDA trace. Try to get at least a partial trace of the loop.
For documentation failures, the location of the error in the manual and a description of the problem it caused.
For PERFM failures, a description of the actual performance, the expected performance, and the source of the performance specification.

Note: When you submit any of the requested documentation on tape, write it to a standard label tape. A hardcopy of the data control block (DCB) information for each data set and the JCL used to create the tape is also required.