Pointing to listings with JCL DD statements
No DD statements are required to run Fault Analyzer in either batch or real time. However, for versions of z/OS® prior to z/OS® 2.2, a SYSMDUMP, SYSUDUMP or SYSABEND DD statement is needed for normal MVS™ dump processing in real time when using the MVS™ IEAVTABX change options/suppress dump exit, IDIXDCAP, unless the IDITABD USERMOD is applied (see Eliminating the need for a dump DD statement (++IDITABD) for details about the effect of this USERMOD).
You can specify the following DD statements in the JCL if appropriate. If they are not specified,
the definitions from the PARMLIB configuration member IDICNF00, the IDIOPTS user options file, or an Analysis Control user
exit are used to identify these data sets:
- IDILC
- PDS or PDSE data set containing C compiler listings
- IDILCOB
- PDS or PDSE data set containing COBOL compiler listings (other than OS/VS COBOL)
- IDILCOBO
- PDS or PDSE data set containing OS/VS COBOL compiler listings
- IDISYSDB
- PDS or PDSE data set containing COBOL or Enterprise PL/I SYSDEBUG, or XL C/C++ MDBG side files.
- IDILPLI
- PDS or PDSE data set containing PL/I compiler listings (other than Enterprise PL/I)
- IDILPLIE
- PDS or PDSE data set containing Enterprise PL/I compiler listings
- IDIADATA
- PDS or PDSE data set containing SYSADATA from Assembler compilations
- IDILANGX
- PDS or PDSE data set containing LANGX side files for all languages
Do not specify a member name on any of the above DD statements. See Providing compiler listings or Fault Analyzer side files for further details on the use of these files.