Selecting tracing by component

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.

About this task

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 1).

There are special considerations for the following CICS domains and their corresponding component codes:
AP (Application domain)
The component codes BF, BM, BR, CP, DC, DI, EC, EI, FC, IC, IS, KC, PC, RI, SC, SZ, TC, TD, TS, UE, WB, and WU are either entirely or partly 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.
Start of changeMP (Managed platform domain)End of change
Start of changeIn the Managed platform component (MP), one level of tracing, level 3, is intended for IBM field engineering staff. This trace level modifies the internal MP operation as follows:
MP level 3 trace
All updates to CICS Policy threshold counters are traced.
A significant performance overhead is introduced into your CICS system if this managed platform trace level is selected. Specifying MP =ALL activates MP trace levels 1, 2, and 3.End of change
SM (Storage manager domain)
In the storage manager component (SM), two levels of tracing, level 3 and level 4, are intended for IBM field engineering staff. These trace levels take effect only if specified in system initialization parameters and modify the internal SM operation for CICS subpools as follows:
SM level 3 trace
The quickcell mechanism is deactivated. Every CICS subpool, regardless of quickcelling requirements, will issue domain calls for getmain and freemain services, and these calls will be traced.
SM level 4 trace
Subpool element chaining on every CICS subpool is forced. Every CICS subpool, regardless of element chaining requirements, will use element chaining.
A significant performance overhead is introduced into your CICS system if these storage manager trace levels are selected. Specifying SM=ALL activates SM trace levels 1, 2, 3, and 4.


dfhs13s.html | Timestamp icon Last updated: Monday, 5 June 2017