Retrieve information about CICS system tracing.
The INQUIRE TRACETYPE command tells you which levels of tracing are currently in effect for particular CICS system 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 ask about either type in an INQUIRE TRACETYPE command, and for any number of components, but you can ask about only one type in a single command.
For each component that you specify, the trace levels are returned as a 32-bit string (in a 4-character data area). The bits are read from left to right; that is, the first bit is on if trace level 1 is in effect, bit 2 corresponds to trace level 2, and so on. A value of X'80000000' thus represents trace level 1. Bits for trace levels that are not defined are set to zero.
The SJ component uses higher trace levels than most other components. 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 view the current settings and options for JVM trace.
CICS components can be identified by a 2-character identifier or, in some cases, a descriptive keyword. For example, to determine the trace levels for the directory manager component of CICS, you can specify either:
INQUIRE TRACETYPE DD(data-area)
or
INQUIRE TRACETYPE DIRMGR(data-area)
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 |