Additional information you might need

Depending on the complexity of the problem, you may need the following additional information:
  • Traces. Traces can complete the picture of the environment at the time of error. There are different types of traces you can run. See Table 1 for more information about JES2 traces. Traces include:
    • JES2 traces. The $TRACE facility creates JES2 traces. Different situations can be traced with different trace identifiers. Table 1 explains how to enable the traces, how the traces are related to specific functions, and the information in each trace.
    • CCWTRACE. These traces are useful for diagnosing I/O- or TP-related problems. For a hardware problem, CCWTRACE can supplement the information in logrec data set.
    • GTFTRACE. If a GTFTRACE is active for the area that gave you the problem, this trace can be helpful. The GTFTRACE is especially important for VTAM-related problems. If you must recreate the problem for any reason and you can trace the area with GTFTRACE, do so.
    • MTRACE. These traces are useful for diagnosing some problems, if SYSLOG is unavailable. However, MTRACE should not be used as a substitute for a copy of SYSLOG.
  • LIST output of the initialization process. When the error occurs during JES2 initialization, restart JES2 with LIST or LOG to help you locate the cause of the problem. It is probably the easiest way to trace the initialization statements.
  • Program event recording (PER) output. This is the information created from a SLIP trap. See z/OS Problem Management and z/OS MVS System Commands for information about using the MVS™ SLIP command to set SLIP traps.
  • Environmental, Reporting, Editing, and Printing Program (EREP) output. Use EREP to format and print logrec data set error records. See EREP User's Guide for more information about EREP.
  • Register contents when using the JES2 DEBUG facility. See Using the JES2 DEBUG facility for more information about the JES2 DEBUG facility.
  • Output from IPCS. See Using IPCS for diagnosis for more information about IPCS.
  • If you are experiencing JESXCF address space problems by system abend codes DC5 and EC5, JES2 $HASP501 or MVS IXZ0108E, see z/OS MVS Programming: JES Common Coupling Services for procedures on how to dump the JESXCF address space and all associated address spaces. That document also provides an example of how to end and restart the JESXCF address space.