Requesting a SYSJES trace for problems during initialization

Use this procedure only when requested to by the IBM® Support Center. The procedure requests SYSJES tracing for JES XCF problems occurring during JES subsystem initialization. The procedure consists of using the default parmlib members CTIJES01, CTIJES02, and CTIJES04 to request tracing of these SYSJES sublevels. Note that parmlib member CTIJES03 contains module footprint tracing that is active, by default, on your system. Therefore, you do not need to take any action to modify this trace.

Activating all four traces can negatively impact system performance because of the heavy volume of trace data produced. For that reason, you should only use this procedure when requested by IBM, and you should not leave this full tracing on. The identical parmlib members are supplied with tracing set off, since you should only run with full tracing at IBM's request. The default contents of parmlib members CTIJES01, CTIJES02, and CTIJES04 is:

TRACEOPTS
OFF

The default contents of parmlib members CTIJES03 is:

TRACEOPTS
ON

IBM recommends that you keep this tracing sublevel on at all times.

1. Modify the CTIJES01, CTIJES02, and CTIJES04 parmlib members to turn tracing on: In parmlib members CTIJES01, CTIJES02, and CTIJES04, alter the parmlib members to return sublevel tracing on and connect the sublevel to the external writer. The parmlib members are supplied with tracing off and no connection to the writer.

When you initialize the JES subsystem with the modified parmlib members, full tracing for JES XCF starts automatically.

Figure 1 is an example of the CTIJESxx parmlib member after having been modified for gathering trace data during JES subsystem initialization at the direction of the IBM Support Center. The member turns tracing on for the sublevel and connects the sublevel to the external writer.

Figure 1. Example: Turning on tracing in a CTIJESxx member

TRACEOPTS
WTRSTART(IXZCTW)
ON
WTR(IXZCTW)

2. Create a CTIJESOF parmlib member to stop SYSJES tracing: Use the CTIJESOF parmlib member to stop the full SYSJES tracing turned on during initialization and to disconnect them from the external writer.

3. Stop SYSJES tracing after initialization tracing is complete: Enter a TRACE CT operator command referencing the CTIJESOF parmlib member on the console with master authority as follows:

TRACE CT,OFF,COMP=SYSJES,PARM=CTIJESOF

4. Remodify the CTIJES01, CTIJES02, and CTIJES04 parmlib members to return to default Tracing: In parmlib members CTIJES01, CTIJES02, and CTIJES04, alter the parmlib member to return sublevel tracing to off.

Figure 2 shows the CTIJES01, CTIJES02,and CTIJES04 parmlib members after having been returned to their original contents, with tracing set off.

Figure 2. Example: Return to default in a CTIJESxx member

TRACEOPTS
OFF