The TRACE parameter specifies the Client components to trace when tracing is enabled.
Configuration tool fields | ctg.ini file trace parameters | Description |
---|---|---|
ALL | Trace everything | |
Client API level 1 | API | Client API layer level 1 |
Client API level 2 | API.2 | Client API layer level 1 and 2 |
CICSCLI command line | CLI | cicscli command interface |
CICSTERM and CICSPRINT | EMU | cicsterm and cicsprnt emulators |
CPP classes | CPP | C++ class libraries |
Client daemon | CCL | Client daemon |
Transport layer level 1 | TRN.1 | Interprocess communication. The TRN.1 component traces the internal interprocess transport between Client processes. Use it if entries in the Client log refer to functions such as FaarqStart, FaarqStop. |
Transport layer level 2 | TRN.2 | Interprocess communication. The TRN.2 component traces the internal interprocess transport between Client processes. Use it if entries in the Client log refer to functions such as FaarqGetMsg, FaarqPutMsg. TRN.2 is the most verbose tracing component. |
Protocol drivers level 1 | DRV | Protocol drivers, for example, TCP. This traces data sent and received and provides supplementary information about failures. |
Protocol drivers level 2 | DRV.2 | This traces internal flows through the protocol drivers and interactions with other software components. This enhanced tracking level currently has the same functionality as level 1. |
Workload manager | LMG | Workload Manager |
This parameter is in the CLIENT section of the configuration file.