SYSjes2 component trace

Before using this component trace

This topic assumes you have read:

The following summarizes information for requesting a SYSjes2 component trace for the JES2 subsystem. For ease of explanation here, this component trace is referred to as SYSjes2 although you might need to replace jes2 with the name you assigned to your JES2 subsystem (primary or secondary). For example, to obtain trace information for JESA, a name you might have used to name your secondary JES2 in a poly-JES environment, use SYSJESA as the component name.

Information	For SYSjes2:
Parmlib member	n/a
Default tracing	Yes; full tracing for sublevels JQE and JOE
Trace request OPTIONS parameter	None
Buffer	Default: N/A Range: N/A Size set by: JES2 Change size after IPL: No Location: In the component address space
Trace records location	Address-space buffer
Request of SVC dump	By the component, or DUMP or SLIP
Trace formatting by IPCS	CTRACE COMP(SYSjes2)
Trace format OPTIONS parameter	Yes

SYSjes2 tracing is started automatically during initialization. SYSjes2 contains 2 sublevel traces, which run continuously and concurrently. The sublevels are:

JQE service tracing: JQE records all job queue service calls (to include: $QADD, $QPUT, $QREM, $QMOD, $QJIX, $GETJLOK, $QRBDCHK, $QBUSY, $GETLOKW, $FREJLOK, and $FRELOKW).
JOE service tracing: JOE records all job output element service calls (to include: $#ADD, $#PUT, $#REM, $#MOD, $#RBDCHK, $#BUSY, $#GET, and $#CAN).