Component names and abbreviations lists the components for which you can select trace levels for standard and special tracing. You can reference this list online through CETR, by pressing PF1 on the component screen (see Figure 22).
You need to decide for each component the trace levels to be used for both standard and special tracing. You can define this either during system initialization, or online using the CETR transaction.
The component codes BF, BM, BR, CP, DC, DI, EI, FC, IC, IS, KC, PC, SC, SZ, TC, TD, TS, UE, and WB are subcomponents of the AP domain. The corresponding trace entries are produced with a point ID of AP nnnn.
For example, trace point AP 0471 is a file control level-1 trace point and AP 0472 is a file control level-2 trace point. These trace points are produced only if the trace setting for the FC component is "(1,2)" or "ALL". The component code AP is used for trace points from the AP domain that do not fall into any of the subcomponent areas listed above.
The SJ domain, which controls JVM tracing, is a special case. As well as using the normal trace levels, the SJ domain uses trace levels 29-32, which are reserved to indicate the JVM trace levels 0, 1, and 2, plus a user-definable JVM trace level. You can activate trace levels 29-32 using the normal system initialization parameters that you would use to set trace levels for components, but to activate these trace levels using the CETR transaction, you need to use the JVM Trace screens, rather than the Component Trace screens. The JVM trace options are set using a "free-form" 240-character field, and you can set these using the JVM tracing system initialization parameters, or the JVM Trace CETR screens. Defining tracing for JVMs describes how to define JVM tracing.
Code | Component name |
---|---|
AP | Application domain |
BA | Business application manager |
BF | Built-in function |
BM | Basic mapping support |
BR | 3270 bridge |
CP | Common programming interface |
DC | Dump compatibility layer |
DD | Directory manager domain |
DH | Document Handler |
DI | Batch data interchange |
DM | Domain manager domain |
DP | Debugging profiles domain |
DS | Dispatcher domain |
DU | Dump domain |
EI | Exec interface |
EJ | Enterprise Java™ domain |
EM | Event manager domain |
FC | File control |
GC | Global catalog domain |
IC | Interval control |
IE | ECI over TCP/IP domain |
II | IIOP 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 |
MN | Monitoring domain |
NQ | Enqueue domain |
OT | Object transaction domain |
PA | Parameter domain |
PC | Program control |
PG | Program manager domain |
PI | Pipeline domain |
PT | Partner domain |
RI | RMI |
RM | Recovery manager 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 |
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 interface domain |
XM | Transaction manager domain |
XS | Security manager domain |
You can code any of the following parameters to define component tracing at CICS system initialization time:
For more information about system initialization parameters, see the CICS® System Definition Guide.
You can use the CETR transaction to define component tracing dynamically on the running CICS system.
Figure 22 shows you what the CETR Component Trace Options screen looks like. To make changes, you overtype the settings shown on the screen, and then press ENTER.
CETR Component Trace Options Overtype where required and press ENTER. PAGE 1 OF 3 Component Standard Special -------- ------------------------------- --------------------------- AP 1 1-2 BA 1 1-2 BM 1 1 BR 1 1-2 CP 1 1-2 DC 1 1 DD 1 1-2 DH 1 1-2 DM 1 1-2 DS 1 1-2 DU 1 1-2 EI 1 1-2 EM 1 1-2 FC 1 1-2 GC 1 1-2 IC 1 1-2 IS 1 1-2 PF: 1=Help 3=Quit 7=Back 8=Forward 9=Messages ENTER=Change
With the settings shown, trace entries are made as follows:
This CETR screen should not be used to define trace levels 29-32 for the SJ domain, which are used to control JVM tracing. Defining tracing for JVMs tells you about the screens that you should use for these trace levels.