This topic contains tables that provide criterion for selecting a tool or service aid, depending on the problem or need. The tables show the problem or need, the corresponding tool or service aid, and the topic or document that covers it in complete detail. (Most of the detailed information on tools and service aids is in this document.) Use these tables to quickly find a tool or service aid.
Table 1 provides guidance on how to select the type of dump to use for a specific problem.
| What is the problem or need? | Type of dump to use |
|---|---|
| Testing of an authorized program or a problem program while it is running, especially for 64-bit applications | Transaction dump (see Transaction dump) |
| Testing of a problem program while it is running | SNAP dump (see SNAP dump) |
| Abnormal end of an authorized program or a problem program | ABEND dump (see ABEND dump) |
| System problem when the system continues processing | SVC dump (see SVC dump) |
| System problem when the system stops processing or is stopped by the operator because of slowdown or looping | Stand-alone dump (see Stand-alone dump) |
Table 2 provides guidance on how to select the type of trace to use for a specific problem.
| What is the problem or need? | Type of trace to use |
|---|---|
| System problem: diagnosis requires checking of component events | Component trace (see Component trace) |
| System problem: diagnosis requires detailed checking of one or two system events | Generalized trace facility (GTF) trace (see The Generalized Trace Facility (GTF)) |
| System or authorized program problem: diagnosis requires the messages related to a dump | Master trace (see Master trace) |
| System problem: diagnosis requires checking many system events | System trace (see System trace) |
| System or problem program: diagnosis requires information about allocation of virtual storage. | GETMAIN, FREEMAIN, STORAGE (GFS) trace (see GETMAIN, FREEMAIN, STORAGE (GFS) trace) |
Table 3 provides guidance on how to select the service aid to use for a specific problem.
| What is the problem or need? | Type of service aid to use |
|---|---|
| System or hardware problem: need a starting point for diagnosis or when diagnosis requires an overview of system and hardware events in chronological order. | Logrec data set (see Recording logrec error records) |
| Information about the content of load modules and program objects or problem with modules on system. | AMBLIST (see AMBLIST: Map load modules and program objects) |
| Diagnosis requires dynamic change to a program, such as fixing program errors, inserting a SLIP trap match, or altering a program to start component trace. | SPZAP (see SPZAP: Modify data in programs and VTOCs) |
| Need to pack the diagnostic materials for transmission to another site, and create similar data sets at the receiving site. | AMATERSE (see AMATERSE: Pack and unpack a data set) |
| Need to eliminate duplicate or unneeded dumps. | DAE (see Dump suppression) |
| Diagnosis requires a trap to catch problem data while a program is running. | SLIP (see z/OS MVS System Commands ) |
| Diagnosis requires formatted output of problem data, such as a dump or trace. | IPCS (see z/OS MVS IPCS User's Guide) |