Starting client tracing

You can control Client daemon tracing using the cicscli command. You can improve performance while tracing by using memory mapped tracing.

To start tracing the Client daemon, enter:
        cicscli -d[=size]
Where size is an optional parameter which specifies the maximum size of data, in bytes, to be traced with any individual trace message. The default is 512 bytes.
To trace the Client daemon from startup on UNIX and Linux, enter the -s and -d options together:
        cicscli -d -s

To trace the Client daemon from startup on Windows, set the trace options as startup parameters. For more information, see Setting CICS Transaction Gateway startup override options

The Client daemon writes trace entries to a file, the default file name is cicscli.bin. On UNIX and Linux systems the trace file is created in the /var/cicscli directory. On Windows systems the trace file is created the <product_data_path> directory.

Performance while tracing is on can be improved by using memory mapped tracing. With memory mapped tracing, data is stored initially in memory, and flushed to disk by the operating system's paging mechanism. For more information, see Memory mapped tracing. For important security information, see Security considerations for UNIX and Linux systems.

To use memory mapped tracing, do the following:
  1. Turn on wrapping trace by setting the Client trace file wrap size in the configuration file to a value greater than 0.
  2. When you turn on tracing, specify the -b option as well as the other options, for example:
    cicscli -d -b
    or
    cicscli -d -m=component_list -b

Use the cicsftrc utility to format the trace file; see Formatting the binary trace file.


Information Information

Feedback


Timestamp icon Last updated: Tuesday, 19 November 2013


https://ut-ilnx-r4.hursley.ibm.com/tg_latest/help/topic/com.ibm.cics.tg.doc//ctgunx/ccltraceon.html