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.
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 Enable JNI trace by setting environment variables,
by using a ctgstart command override, or when starting
an application in local mode.
JEE tracing
A detailed trace mechanism is provided for the
ECI resource adapter. Trace is useful when problem solving for applications
that use the CICS resource
adapters.
EXCI trace
The CICS Transaction Gateway writes
trace entries to the EXCI trace. Entries are in the CICS trace
EXCI format.
Collecting SVC dumps of the Gateway daemon address space
The IBM® support organization
might request an SVC dump of the Gateway address space, or a problem
might cause an SVC dump to be generated. Options are available for
ensuring that information about the required components is captured.
Information
Last updated: Wednesday, 27 August 2014