SYSJES component trace

Before using this component trace

This topic assumes you have read:

The following summarizes information for requesting a SYSJES component trace for the JES common coupling services component, also known as JES XCF.

Information	For SYSJES:
Parmlib member	CTnJESxx. Default members: CTIJES01, CTIJES02, CTIJES03, CTIJES04
Default tracing	Yes; detailed tracing for sublevel FLOW; minimal tracing of unexpected events for sublevels MSGTRC, USRXIT, XCFEVT
Trace request OPTIONS parameter	None
Buffer	Default: N/A Range: N/A Size set by: MVS™ system Change size after IPL: No Location: In the component address space
Trace records location	Address-space buffer, trace data set
Request of SVC dump	By the component
Trace formatting by IPCS	CTRACE COMP(SYSJES)
Trace format OPTIONS parameter	Yes

Note: To get a complete dump for JES XCF, request also the JES and JES XCF address spaces and data spaces, plus SDATA options RGN, SQA, and CSA.

SYSJES tracing is started during initialization. SYSJES contains 4 sublevel traces, which run concurrently. Each sublevel must be started individually. The sublevels are:

MSGTRC, message tracing: MSGTRC records message data sent by the IXZXIXSM service. The default tracing for this sublevel is minimal tracing of unexpected events only. You can optionally start and stop detailed MSGTRC tracing. Use the data from this sublevel in conjunction with USRXIT trace data to get information about message data modified by installation exits IXZXIT01 or IXZXIT02.
USRXIT, installation exit tracing: USRXIT records the exit parameter list (SPELL) passed to and returned from installation exits IXZXIT01, IXZXIT02, and IXZXIT03 processing. The default tracing for this sublevel is minimal tracing of unexpected events only. You can optionally start and stop detailed USRXIT tracing. Use the data from this sublevel in conjunction with MSGTRC trace data to get information about message processing through installation exits IXZXIT01, IXZXIT02, and IXZXIT03.
FLOW, module footprint tracing: FLOW records messages and events as they flow through the JES common coupling services component. By default, FLOW is always active and produces detailed tracing.
Note: IBM® recommends that this trace always remain active to record diagnostic data such as errors, system state changes, and processing events.
XCFEVT, system event (SYSEVENT) tracing: XCFEVT records SYSEVENT data processed by the JES common coupling services component. By default, XCFEVT always produces minimal tracing.

Tracing for SYSJES can run all 4 sublevels concurrently. USRXIT and MSGTRC trace only error events by default; you can turn on detailed tracing for these two sublevels.