Tracing

XCICS is can trace:

Core tracing is useful to check configuration issues or for debugging purpose. Two levels of core tracing are available:

Core tracing can be configured at startup time using the set core_trace directive in xcics.conf, or at run-time using xcicsadm utility or CETR transaction.

Task tracing can be used to keep track of all the activities performed by a single terminal in terminal or transaction and, according to the trace level, this trace can be used to perform program debugging.

By means of these logging features, all the call to XCICS performed by user transactions as well as the XCICS internals can be logged on a different file for each terminal. These files are written in the XCICS logs directory, and their name is deb<EIBTRMID>.<suffix>. The EIBTRMID part of the name refers to the name of terminal which generated the log; the suffix indicates the connection time for interactive terminals, and process number for background task.

Three different levels are available:

Terminal logging may be configured at start up time, for the whole application, directly from the XCICS configuration file, using the set core_trace directive, or at run-time using xcicsadm utility or CETR transaction.

Tracing may cause performance lacks, therefore it would be a good practice to start production regions with no traceing active, and directly activate them only if needed.