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 Create a Binary Trace File
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 value of size must
be in the range 0 - 32767. The default is 512 bytes. - Enter the trace parameters into the CTGD_PARAMS variable
in the ctgd.conf file. For example, to set the
trace to Protocol driver tracing level 2 enter:
When you start the Client with the commandCTGD_PARAMS="-c-d -c-m=DRV.2"ctgd start, trace starts automatically. - Using the ctgstart command. For example, to
set the trace to Protocol driver tracing level 2 enter:
ctgstart -c-d -c-m=DRV.2
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.
Memory Mapped Tracing
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.
- Turn on wrapping trace by setting the Client trace file wrap size in the configuration file to a value greater than 0.
- When you turn on tracing, specify the
-boption as well as the other options, for example:
orcicscli -d -bcicscli -d -m=component_list -b
Use the cicsftrc utility to format the
trace file; see Formatting the binary trace file.