Identify the program or component involved with the output from
one of the following steps:
- For output from a batch job, obtain the program name from the
PGM parameter on the JCL EXEC statement. In the following example
the program name is obtained from the JCL EXEC statement:
In
the following example, the name of a program involved with the output
is IKJEFT01. It can be found on the PGM parameter of the EXEC statement:
//*
//*====================================================
//* Batch TSO job (PGM=IKJEFT01)
//*====================================================
//IKJEFT01 EXEC PGM=IKJEFT01,REGION=4096K,DYNAMNBR=50
//*
Identify the program or component involved with the output
from one of the following:
- For output from interactive work, use the command being processed
to identify the program.
- For an error message, use the message prefix to identify the program
or component or look for the component listed in the message explanation.
Look at the preface of any of the z/OS MVS™ system messages books to find
the element or component that the message is associated with and the
book where you can find the explanation of the message:
For
example, if you have an incorrect message with message number AHL002A,
you can tell from the preface of
z/OS MVS System Messages, Vol 1 (ABA-AOM) that
the message was issued by GTF, and the explanation can be found in
the same book:
Table 1. Example of using the message prefix to identify
the componentPrefix |
Component |
Book Title |
Order Number |
AHL |
Generalized trace facility (GTF) |
|
|
- For a return or reason code accompanying an abend, see the component
listed in the explanation of the code. The following example identifies
the component issuing an abend:
00D
Explanation: An error occurred during processing of a
CTRACE or CTRACEWR macro. Register 15
contains xxnnnnxx where nnnn is a reason code that
further describes the error.
- Reason Code (hex)
- Explanation
- 0001
- For the CTRACE macro, the parameter list version number is incorrect.
- 0002
- For the CTRACE macro, the component name either does not begin
with an alphabetic or national character, or it contains one or more
characters that are not alphanumeric or national characters.
- Source:
- Component trace
- For a component of z/OS, continue
with Searching the problem reporting databases for an output problem.
- For an IBM® subsystem or
product, continue diagnosis with the subsystem or product.
- For an installation-provided program, including an installation
exit routine, continue diagnosis with that program.
Related information: - See z/OS MVS JCL Reference for
the EXEC statement.
- For message prefixes for IBM components,
subsystems, and products, see the following books:
- z/OS MVS System Messages, Vol 1 (ABA-AOM)
- z/OS MVS System Messages, Vol 2 (ARC-ASA)
- z/OS MVS System Messages, Vol 3 (ASB-BPX)
- z/OS MVS System Messages, Vol 4 (CBD-DMO)
- z/OS MVS System Messages, Vol 5 (EDG-GFS)
- z/OS MVS System Messages, Vol 6 (GOS-IEA)
- z/OS MVS System Messages, Vol 7 (IEB-IEE)
- z/OS MVS System Messages, Vol 8 (IEF-IGD)
- z/OS MVS System Messages, Vol 9 (IGF-IWM)
- z/OS MVS System Messages, Vol 10 (IXC-IZP)
- See z/OS MVS System Codes for
explanations of the abend codes.
- See z/OS MVS Diagnosis: Reference to
relate an IBM component, subsystem or product
to a program identifier or module prefix.