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

6.3 Problem determination
6.3.1 Tips and utilities
126 CICS Transaction Gateway V5
It is unlikely any implementation will be totally error free the first time you try
things. In this section, we provide some hints and tips based on the experience
we gained during this redbook project.
In this section, we provide some useful commands and utilities for debugging
problems with your configuration, as well as some additional information about
topics discussed in this chapter.
EXCI sign-on/sign-off message suppression
When running any application that connects to CICS through the EXCI (such as
the CICS TG for z/OS), CICS will write one DFHSN1400/DFHSN1500 message
pair to the CICS joblog. With the CICS TG for z/OS, this will occur each time an
ECI request is flowed to the CICS TG. It may be desirable to suppress these
sign-on messages, since so many can be produced. This could be done either by
making the system equivalent (specifying a link user ID on the CICS SESSIONS
definition) or by using the CICS user exit XMEOUT. An assembler sample of this
program can be found in SDFHSAMP(DFH$SXP1).
Error messages
There are several pieces of software involved in securing CICS TG access to
CICS. Because of this, error messages required for problem determination are
seen in different locations. Below is a list of locations to look for error messages
dealing with security problems:
CICS MSGUSR DD This DD, located in the active CICS region, can provide
error messages having to do with VTAM connections
to CICS. This also shows many security errors not
shown anywhere else.
JES SYSLOG General security errors are displayed here. If you
suspect a RACF error, search for the message
ICH408.
Gateway daemon trace This provides an indication of the errors the Gateway
daemon itself encounters.
CICS TG JNI logs These log files are automatically created in the
$HOME/ibm/ctg directory and contain a log of all the
EXCI errors received by the CTG JNI module.
CICS TG JNI trace This provides tracing of the EXCI calls made by the
CICS TG JNI module libCTGJNI.so, and can be very