CICS Transaction Gateway V5 The WebSphere ... - IBM Redbooks

9.4 Problem determination
9.4.1 Tips and utilities
9.4.2 Tracing
230 CICS Transaction Gateway V5
In this section, we document information we learned while configuring this
scenario, and further information on problem determination and tracing.
In this section, you will find useful commands and utilities for debugging
problems with your configuration. You will also find additional information about
topics discussed in this chapter.
Saving the CICS TG messages
If you wish to save the whole message log, issue the following commands to
redirect the output to a log file:
cd /opt/ctg/bin
ctgstart >ctg.log 2>&1
Note that you will now need to use another command prompt to view the log file,
as follows:
cat /opt/ctg/bin/ctg.log
Alternatively you can save the message log while having it output to the screen
using the tee utility as follows:
cd /opt/ctg/bin
ctgstart 2>&1 |tee ctg.log
Error messages
The Client daemon writes error messages to the file CICSCLI.LOG, located in
the /var/cicscli/ directory. This file is created or written to only in error situations
and can be viewed using any text editor. It is particularly useful as a first stop for
determining if problems have occurred with a TCP connection to a CICS server.
There are three ways to trace the CICS Transaction Gateway:
► Gateway daemon tracing, with various levels of tracing available.
► Gateway daemon Java Native Interface (JNI) trace.
► Java client tracing, which can be used to trace the Java method calls made
using the CICS TG Java classes in the Java client.