The STNTRxx system initialization parameter specifies the level of standard tracing you require for a particular CICS component.
Code | Component name |
---|---|
AP | Application domain |
BA | Business application manager |
BM* | Basic mapping support |
BR* | 3270 bridge |
CP* | Common programming interface |
DC* | Dump compatibility layer |
DD | Directory manager domain |
DH | Document handling domain |
DM | Domain manager domain |
DP | Debugging profiles domain |
DS | Dispatcher domain |
DU | Dump domain |
EC* | Event capture and emission |
EI* | Exec interface |
EJ | Enterprise Java™ domain |
EM | Event manager domain |
EP | Event processing domain |
FC* | File control |
GC | Global catalog domain |
IC* | Interval control |
IE | ECI over TCP/IP domain |
IS* | ISC or IRC |
KC* | Task control |
KE | Kernel |
LC | Local catalog domain |
LD | Loader domain |
LG | Log manager domain |
LM | Lock domain |
ME | Message domain |
ML | Markup language domain |
MN | Monitoring domain |
MP | Managed platform domain |
NQ | Enqueue domain |
OT | Object transaction domain |
PA | Parameter domain |
PC* | Program control |
PG | Program manager domain |
PI | Pipeline domain |
PT | Partner domain |
RA | Resource manager adapters |
RI* | Resource manager interface (RMI) |
RL | Resource life-cycle domain |
RM | Recovery manager domain |
RS | Region status domain |
RX | RRS-coordinated EXCI domain |
RZ | Request streams domain |
SC* | Storage control |
SH | Scheduler services domain |
SJ | JVM domain |
SM | Storage manager domain |
SO | Sockets domain |
ST | Statistics domain |
SZ* | Front End Programming Interface (FEPI) |
TC* | Terminal control |
TD* | Transient data |
TI | Timer domain |
TR | Trace domain |
TS | Temporary storage domain |
UE* | User exit interface |
US | User domain |
WB | Web domain |
WU | CICS® Management Client Interface (CMCI) domain |
W2 | Web 2.0 domain |
XM | Transaction manager domain |
XS | Security manager domain |
Most CICS components only use levels 1, 2, and 3, and some do not have trace points at all these levels. The exception is the SM component (storage manager domain), which also has level 4 tracing. This level of tracing is intended for IBM® field engineering staff.
SM trace flag 3 deactivates the quickcell mechanism, and SM trace flag 4 forces subpool element chaining on every CICS subpool. Furthermore, after these settings have been activated during system initialization, they cannot be unset, either through a PLTPI program or by using the CETR trace transaction, because they are not used for tracing as such. Thus, a significant performance overhead is incurred if these storage manager trace levels are selected for standard tracing.
For information about the effects of trace levels 3 and 4, see CICS trace.
Selecting ALL for standard tracing for the JVM domain (SJ) component is not recommended. JVM trace can produce a large amount of output, so activate JVM trace only for special transactions (using the SPCTRSJ system initialization parameter), rather than turning it on globally for all transactions.