CICS z/OS Communications Server exit trace destination

CICS® z/OS® Communications Server exit traces are sent to the GTF trace data set only, and not to any other currently active CICS trace destinations.

Table 1. Exit trace data fields for entries AP FC17 through AP FC4F
ID Description Field Length
BA BIND area (R14) variable
BR BIND response RPLAAREA RPLAARLN
CI z/OS Communications Server CID TCTECID 4
LE LUC extension TCTTELUC TCTTELUL
NI NIB descriptor TCTENIBA TCTENIBE-TCTENIB
RA RPL data area RPLAREA RPLRLEN
RF contents of register 15 R15 4
R1 first RPL (RPLBAR) ATCLEN+ZRPLAD
RV first RPL (RPLBAR) ATCLEN
R2 second RPL (RPLBAR) ATCLEN+ZRPLAD
SY symbolic name D4(R1) 8
T3 section of TCTTE TCTE_TRACE_3 TCTE_TRACE_3_LEN
T5 section of TCTTE TCTE_TRACE_5 TCTE_TRACE_5_LEN
UR UNBIND RU RPLAREA RPLRLEN
VP z/OS Communications Server parameter list (R1) 24
WE autoinstall work element DFHTCTWE TCTWELEN
Note:
  1. The exit trace data fields for each trace entry are the NETNAME, if any, followed by one or more other data fields in any order, depending on the path through CICS system code. The first two bytes of a data field hold the ID.
  2. BIND is described in BIND area format and DSECT in z/OS Communications Server: SNA Programming and Systems Network Architecture Formats (GA27-3136).
  3. The LUC extension (DFHTCTTE), the NIB descriptor (DFHTCTTE), and the autoinstall work element (DFHTCTWE) are described in Data areas.