Client daemon tracing

Client daemon tracing is a useful problem determination tool for resolving communication problems.

You can use the trace functions to collect detailed information on the execution of a particular function or transaction. A trace can show how the execution of a particular activity is affected by, for example, the execution of other tasks in a CICS® system. Each trace entry has a time stamp, which provides information on the time taken to perform certain activities.

To learn how to turn tracing on, see Starting client tracing.

For information on specifying the components of the Client daemon to be traced, see the cicscli -m command.

The output from the trace function is a binary trace file called, by default, cicscli.bin in the ⁄var⁄cicscli subdirectory on UNIX and Linux® or <product_data_path> subdirectory on Windows. You can specify a different name for this file, using the Configuration Tool. However, you cannot change the .BIN extension. Using the Client trace file wrap size (KB) configuration setting, you can specify that the binary trace file should wrap into a second trace file, and you can also specify the maximum size of these files.

See Formatting the binary trace file for information on the trace conversion utility.