Tracing

Tracing can be enabled and controlled for different components of the CICS® Transaction Gateway.

Note: Tracing, especially debug tracing, decreases performance.

Gateway daemon tracing
Gateway daemon tracing can be set in the Gateway daemon configuration file, or with a command option.
Client daemon tracing
Client daemon tracing is a useful problem determination tool for resolving communication problems.
Tracing in ECI V2 and ESI V2 applications
Applications should implement an option to enable trace. You can control tracing in ECI and ESI Version 2 applications using the functions and environment variables described here.
Tracing Java Client applications
You can enable tracing in the application by using a Java™ directive when you start the JVM, or by adding calls to the CICS Transaction Gateway tracing API.
JNI tracing
JNI trace can be enabled on start up of CICS Transaction Gateway or a local mode application. Alternatively, JNI trace can be enabled when the Gateway daemon is running using the ctgadmin command.
JEE tracing
A detailed trace mechanism is provided for both the ECI and EPI resource adapters. Trace is useful when problem solving for applications that use the CICS resource adapters.
Tracing for Microsoft NET Framework-based client programs
Trace is activated for the IBM.CTG.Client.dll either by specifying it as an application configuration file or by using the Trace class.

Parent topic: Resolving problems

Related reference

Transaction tracking