Requesting a SYSJES trace

IBM® recommends the following when requesting SYSJES TRACING:

Start and stop the four sublevels for a system all at once in one parmlib member. Request SYSJES component tracing in a CTnJESxx parmlib member which you specify on a TRACE CT command.
IBM provides two parmlib members, IXZCTION and IXZCTIOF, in SYS1.SAMPLIB as examples of how to start and stop SYSJES sublevels. Copy the members into parmlib, and rename them CTIJESON and CTIJESOF. The CTIJESON parmlib member starts all the sublevels and connects them to the external writer. The CTIJESOF parmlib member stops tracing in all sublevels and disconnects them from the external writer.
Use the external writer for gathering trace records, because SYSJES tracing produces a large volume of data. Create source JCL for the external writer, using the following guidelines:
- Code all TRCOUTnn DD statements with a SPACE parameter of at least 10 cylinders to accommodate the volume of SYSJES trace data.
- For traces larger than 10 cylinders, specify a unique volser for each TRCOUTnn statements if you need to reduce I/O contention on one volume.
- The data set name defined in the TRCOUT01 DD statement must be unique on each system.
- Use the IPCS COPYTRC command to merge records from multiple TRCOUTnn DD statements into one data set. See z/OS MVS IPCS Commands for information.
Example: Cataloged procedure for SYSJES
The following example shows an external writer procedure, IXZCTW, that sends SYSJES trace output to trace data sets.
```
//CTWDASD   PROC
//IEFPROC   EXEC  PGM=ITTTRCWR
//SYSPRINT  DD    SYSOUT=A
//TRCOUT01  DD    DSN=SYS1.JESXCF1,VOL=SER=TRACE6,UNIT=DASD,
//          SPACE=(CYL,10),DISP=(NEW,KEEP),DSORG=PS
//TRCOUT02  DD    DSN=SYS1.JESXCF2,VOL=SER=TRACE7,UNIT=DASD,
//          SPACE=(CYL,10),DISP=(NEW,KEEP),DSORG=PS
```
If you are tracing in a sysplex environment, the data set names on TRCOUTnn DD statements must be unique throughout the sysplex. An ENQUEUE error results if the data set names are not unique.