Change the tracing levels of CICS components.
The SET TRACETYPE command allows you to change the levels of tracing for one or more CICS components.
Each CICS component has trace levels defined separately for standard CICS tracing and special tracing (see the CICS® Problem Determination Guide for definitions of these terms and for information about CICS tracing in general). You can set either type for any number of components in a SET TRACETYPE command, but you can set only one type per command.
For each component that you specify, you define the trace levels as a bit string. The bits are read from left to right; that is, the first bit corresponds to trace level 1, the second to trace level 2, and so on. A value of 1 turns on the trace level; 0 turns it off. For example, X'C0000000' turns trace levels 1 and 2 on and all others off.
Although most components define only a few trace levels, you must provide a 32-bit (4-byte) data value. CICS ignores bits that do not correspond to trace levels, and thus it does not matter whether you specify 0 or 1 for them.
The SJ component does use higher trace levels. Trace levels 29-32 for the SJ component correspond to JVM Level 0 trace, JVM Level 1 trace, JVM Level 2 trace and JVM User trace respectively. The CICS-supplied transaction CETR includes screens that provide a better way to set these trace levels, and to change the JVM trace options associated with them.
CICS components can be identified by a 2-character designation or, in some cases, a descriptive keyword. For example, to set the trace levels for the storage manager component of CICS, you can specify either:
SET TRACETYPE SM(data-value)
or
SET TRACETYPE STORAGE(data-value)
The following list shows all the 2-character identifiers, and the keywords for those components that have them.
AP | APPLICATION | Application |
BA | BUSAPPMGR | Business applications manager |
BF* | Built-in functions | |
BM* | Basic mapping support | |
BR* | BRIDGE | 3270 Bridge |
CP* | CPI | Common programming interface |
DC* | Dump control | |
DD | DIRMGR | Directory manager |
DH | Document handling | |
DI* | Batch data interchange | |
DM | DOMAINMGR | Domain manager |
DP | Debugging Profiles domain | |
DS | DISPATCHER | Dispatch manager |
DU | DUMP | Dump manager |
EI* | EXEC interface | |
EJ | ENTJAVA | Enterprise Java domain |
EM | EVENTMGR | Event manager |
FC* | File control and DL/I | |
GC | GLOBALCATLG | CICS global catalog manager |
IC* | Interval control | |
IE | ECI over TCP/IP domain | |
II | IIOP | IIOP domain |
IS* | Intersystem communication | |
KC* | Task control | |
KE | KERNEL | Kernel |
LC | LOCALCATLG | CICS local catalog manager |
LD | LOADER | Program load manager |
LG | LOGMGR | Log manager |
LM | LOCKMGR | Lock manager |
ME | MESSAGE | Message manager |
MN | MONITOR | Monitoring manager |
NQ | Enqueue domain | |
OT | OBJECTTRAN | Object Transaction Service (OTS) domain |
PA | PARAMGR | Parameter manager |
PC* | Program control | |
PG | PROGMGR | Program manager |
![]() ![]() |
![]() ![]() |
|
PT | PARTNER | Partner manager |
RI* | Resource manager interface (RMI) | |
RM | Recovery manager | |
RX | RRS | Resource recovery services |
RZ | REQUESTSTRM | Request streams domain |
SC* | Storage control | |
SH | Scheduler services domain for BTS | |
SJ | SJVM | CICS JVM domain |
SM | STORAGE | Storage manager |
SO | SOCKETS | Sockets |
ST | STATISTICS | Statistics manager |
SZ* | Front-end programming interface | |
TC* | Terminal control | |
TD* | Transient data | |
TI | TIMER | Timer manager |
TR | TRACE | Trace manager |
TS | Temporary storage | |
UE* | User exit interface | |
US | USER | User interface |
WB | WEB | Web interface |
XM | TRANMGR | Transaction manager |
XS | SECURITY | Security manager |
Components marked * are subcomponents of the AP domain, and the trace entries for these components are produced with a trace point ID of AP nnnn.