Summary of trace identifiers

JES2 assigns each event eligible for tracing a numeric identifier used to reference the event. Each time an activated trace event occurs (such as processing of a $SAVE macro), JES2 writes information to the trace table. The standard trace table entry consists of the trace identifier, the time-of-day clock value, an 8-character symbol taken from the $TRACE macro, the job number or ASID (if available), and the processor control element (PCE) name and address (if available). The trace information is then produced in a formatted output. In addition, each trace event can record other unique information. For example, each traced $SAVE macro also records the contents of registers 14, 15, 0, and 1 the EBCDIC name of the routine that issued the $SAVE macro.

Tracing requires at least 3 trace tables of equal size, which must be in ECSA. Specify the number of trace tables on the TABLES parameter of the TRACEDEF initialization statement and the size of each trace table, in units of 4-kilobyte pages, on the PAGES parameter of the TRACEDEF statement. If a TRACEDEF initialization statement or operator command requests logging by specifying LOG=(START=YES), JES2 formats the contents of the filled trace table and writes the formatted entries to spool while writing the new entries to the next table. Formatting routines in the event trace log processor perform any required formatting for each trace identifier.

If a TRACEDEF initialization statement or operator command requests no logging by specifying LOG=(START=NO), JES2 wraps data from the active log to the oldest log.

Table 1 identifies the valid event identifiers and their meanings.

Table 1. Trace Identifiers and Their Meanings
Trace Identifier	Meaning
1	Trace JES2 $SAVE macro calls for the JES2 main task and FSS environments. This identifier traces all JES2 processors. See trace ID 11 and ID 18.
2	Trace JES2 $RETURN macro calls for the JES2 main task and FSS environments. This identifier traces all JES2 processors. See trace ID 12 and ID 19.
3	Trace JES2 disastrous errors ($DISTERR macro).
4	Trace channel-end completions for BSC lines. A line is eligible for tracing if the associated LINE(nnnn) initialization statement specifies TRaceio=YES.
5	Trace SNA events on VTAM® lines and the JES2/VTAM interface. A line or interface (LGNn) is eligible for tracing if the associated LINE(nnnn) initialization statement specifies TRaceio=YES.
6	Trace each time JES2 is initialized or reinitialized.
7	Trace each time JES2 ends along with the ending code.
8,9,10	These identifiers all perform the same function. They are provided so that local debugging may be done by tracing processor flow independently from other trace identifiers. Three identifiers are provided for independent tracing function. Unless JES2 $TRACE macros specifying these identifiers have been placed into JES2 modules, no tracing occurs as a result of enabling these trace identifiers.
11	Trace JES2 $SAVE macro calls. Only processors having TR=Yes option defined (see the $T PCE command), and device-related processors that have the TR=Yes option defined (see the device initialization statements and $T commands) are eligible for tracing with this identifier. The device-related TRACE setting also applies to tasks running in support of those devices in the FSS environment. In the user environment, tasks running with JES2 SSI function routines for which the SSI(nnn) setting is TRACE=YES are eligible for tracing with this identifier. See trace ID 1 and ID 18.
12	Trace JES2 $RETURN macro calls are to be traced. In the user environment, tasks running with JES2 SSI function routines for which the SSI(nnn) setting is TRACE=YES are eligible for tracing with this identifier. See trace ID 2 and ID 19.
13	Trace JES2 exit points. Exits to be traced are determined by the EXIT(nnn) initialization statement and the $T EXIT(nnn) operator command.
14	Trace the FSIREQs (GETDS, RELDS, SEND) on behalf of functional subsystems only when the $DCT for the printer allows tracing. Use the $T PRT(nnnn),TR=Yes command to enable the trace.
15	Trace the FSIREQs (GETREC, FREEREC, CHKPT) on behalf of functional subsystems only when the $DCT for the printer allows tracing. Use the $T PRT(nnnn),TR=Yes command to enable the trace.
16	Trace the functional subsystem CONNECTs and DISCONNECTs only when the $DCT for the printer allows tracing. Use the $T PRT(nnnn),TR=Yes command to enable the trace.
17	Trace statistics associated with checkpoint performance. Trace records include values for each phase of the checkpoint cycle.
18	Trace JES2 $SAVE macro calls for the user environment. This identifier traces all JES2 processors. See trace ID 1 and ID 11.
19	Trace JES2 $RETURN macro calls for the user environment. This identifier traces all JES2 processors. See trace ID 2 and ID 12.
20	Trace the $#GET calls.
21	Trace the interchange between the local node and another node when the 2 nodes are establishing a session. JES2 sends network connect control records (NCC) I, J, K, L, and M during the exchange. See Network Job Entry (NJE) Formats and Protocols for a description of NCC records.
22	Trace the NCC “M” records JES2 received that add a node into the network. See Network Job Entry (NJE) Formats and Protocols for a description of NCC records.
23	Trace the NCC “M” “N” records JES2 received that remove a node into the network. See Network Job Entry (NJE) Formats and Protocols for a description of NCC records.
24	Trace the NCC “M” or “N” records JES2 has rejected that attempted to update the network topography. See Network Job Entry (NJE) Formats and Protocols for a description of NCC records.
25	Trace information about the functional subsystem (FSS) checkpoint.
26	Trace the automatic restart manager requests processed by the JES2 main task.
27	Trace information about PSO external writer processing.
28	Trace SYSOUT Application Program Interface (SAPI) information between the user address space and the JES2 main task.
29	Trace SSI information between the user address space and the JES2 main task concerning the SAPI.
30	Trace identifier 30 traces all $#POST macro calls made by JES2 processing.
31	Trace identifier 31 traces all $QGET macro calls made by JES2 devices and initiators.
32	Trace identifier 32 traces all $#REM macro calls made by JES2 processing. It can be used to determine why a JOE was deleted.
33	Trace identifier 33 traces all NJE Headers, trailers and NMR records received and transmitted by JES2. A header is traced if tracing was requested for the line (TRACEIO=YES on the LINE statement) or for the adjacent node (TRACE=YES on the NODE statement).
34	Trace identifier 34 traces all data records passed between the JES2 address space and the NETSRV address space. These records are traced if tracing is requested on the line (TRACE=JES=YES on the LINE statement) or NETSRV (TRACE=JES=YES on the NETSRV statement).
35	Trace identifier 35 traces all control records passed between the JES2 address space and the NETSRV address space. These records are traced if tracing is requested on the line (TRACE=JES=YES on the LINE statement) or NETSRV (TRACE=JES=YES on the NETSRV statement).
36	Trace identifier 36 traces all data records passed between JES2 code in the NETSRV address space and IAZNJTCP. These records are traced if tracing is requested on the line (TRACE=JES=YES on the LINE statement) or NETSRV (TRACE=JES=YES on the NETSRV statement).
37	Trace identifier 37 traces all control records passed between JES2 code in the NETSRV address space and IAZNJTCP. These records are traced if tracing is requested on the line (TRACE=JES=YES on the LINE statement) or NETSRV (TRACE=JES=YES on the NETSRV statement).
38	Trace identifier 38 traces all data records passed between IAZNJTCP and TCP/IP. These records are traced if tracing is requested on the line (TRACE=COMMON=YES on the LINE statement) or NETSRV (TRACE=COMMON=YES on the NETSRV statement).
39	Trace identifier 39 traces TCP/IP API calls issued by IAZNJTCP. These records are traced if tracing is requested on the line (TRACE=JES=YES on the LINE statement) or NETSRV (TRACE=JES=YES on the NETSRV statement).
40	Trace identifier 40 traces the results of the WLM initiator balancing computation at the beginning of every checkpoint cycle.
41	Trace identifier 41 traces the results of the WLM initiator balancing computation at the end of every checkpoint cycle.
42	Trace identifier 42 traces all $CDCTDYN macro calls that are made by JES2 processing.
43	Trace identifier 43 traces every ENF58 event that is sent.
44	Trace identifier 44 traces every ENF58 event that is received.
45	Trace identifier 45 traces every ENF70 event that is sent.
46	Trace identifier 46 traces every ENF70 event that is received.
47	Trace identifier 47 traces every ENF78 event that is sent.
48-255	These trace identifiers are available for both IBM® and customer use. To avoid an overlap of identifiers, begin numbering identifiers with 255 and progress downward.