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

Tip: In CICS TG for z/OS V5.0 the EXCI JNI logs can also now be quickly and
easily used to identify the majority of EXCI problems. The logs are written to
unique files in the directory $HOME/ibm/ctgjnilog.
EXCI subreasons
Finally, we created an error to illustrate the use of EXCI subreasons. These
subreasons are helpful in that they provide another facet of problem diagnosis.
This time we forced an error by closing IRC on the CICS region. The EXCI and
Gateway traces simply provide a generic EXCI 203 (ECI_ERR_NO_CICS) error.
The 203 error also shows up on the JNI trace, so we skip the EXCI and Gateway
traces.
We ran our test application and Example 7-30 shows the significant line from the
JNI trace.
Example 7-30 JNI trace table, EXCI subreasons
01:05:11.721 Worker-0 ¨ : CCL6822E: CcicsECI: EXCI function error. Function
Call = 3, Response = 8, Reason = 203, Subreason field-1 = 92,
subreason field-2 = 0, Cics_Rc = -3
We see the 203 error that we would have seen on the EXCI trace table and the
Gateway trace. In addition, we see a Subreason field-1 of 92.
To find out the meaning of a subreason 92, we need to look in
CICSTS22.CICS.SDFHMAC(DFHIRSDS). After converting decimal 92 to a hex
5C, we see this equates to “SYSTEM NOT LOGGED ON”.
This is more specific than the general NO_CICS error and led us to check to see
the state of IRC on our target CICS region. Of course we knew this, since we
deliberately closed it in the first place.
GTF tracing
Both the EXCI and CICS itself support trace entries to be written to GTF. In the
following example, we give a brief explanation of how we debugged a simple
problem with the CICS TG for z/OS using GTF tracing. In this error scenario, the
call using EciB1 failed with ECI_ERR_TRANSACTION_ABEND (-7) and AEI0,
due to the disabling of the invoked program, EC01 within CICS.
Chapter 7. TCP connections to the Gateway daemon on z/OS 179