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

13:40:51:040 : ConnectionManager-0: S-C: CCL6727I: ECIRequest: Commarea_Length = 80.
13:40:51:063 : ConnectionManager-0: S-C: CCL6720I: ECIRequest: Call_Type = ECI_ASYNC, Server =
SCSCPJA1, Program = EC02, Transid = , Extend_Mode = ECI_EXTENDED, Luw_Token = 0,
Message_Qualifier = 0, Callbackable = true.
13:40:51:069 : ConnectionManager-0: S-C: CCL6727I: ECIRequest: Commarea_Length = 80.
13:40:51:151 : ConnectionManager-0: S-C: CCL6512I: Waiting to receive a request.
ÝConnectionManager-0¨
13:40:51:166 : Worker-0: S-C: CCL6514I: Accepting work request. ÝWorker-0¨
ÝConnectionManager-0¨
13:40:51:389 : Worker-0: .TCPHandler:CCL6603I: # Dump: 32/32 bytes : Offset = 0 Reply flow
13:40:51:410 : Worker-0: S-C: CCL6523I: About to execute work request. ÝWorker-0¨
13:40:51:428 : Worker-0: S-C: CCL6695I: Before JNI CcicsECI(1) : Server=SCSCPJA1, Program=EC02,
Commarea.Length=80, ExtendMode=1, LUW=0.
13:40:51:514 : Worker-0: S-C: CCL6693I: After JNI CcicsECI(1) : Rc=-9, LUW/TermIndex=0
13:40:51:581 : Worker-0: S-C: CCL6721I: ECIRequest: Call_Type = ECI_ASYNC, Cics_Rc =
ECI_ERR_SYSTEM_ERROR, Abend_Code = , Luw_Token = 0, Message_Qualifier = 0.
176 CICS Transaction Gateway V5
This trace tells us the CICS TG is working normally but we need to look further
into the JNI. The next step is to the trace the CICS TG JNI module (libCTGJNI) to
determine what is causing the bad return code from the JNI call.
JNI trace
The third type of trace is the CICS TG Java Native Interface (JNI) trace. Like the
CICS TG trace, there are two ways of starting the JNI trace, dynamic and static.
Dynamic JNI tracing is new in CICS TG for z/OS V5.0 and requires the
TCPAdmin be set up in the CTG.INI. We demonstrate dynamic tracing, but used
static tracing for our problem diagnosis.
The static trace depends on parameters specified in the CICS TG startup JCL
and requires the CICS TG address space to be recycled.
New in CICS TG for z/OS V5.0 is the default logging of EXCI return codes. These
are written to unique files in the directory $HOME/ibm/ctgjnilog.* and are very
useful for quick problem determination.
Dynamic trace (JNI)
Here we assume the TCPAdmin client has been specified in the CTG.INI file.
1. From within TSO OMVS, we changed our directory to
/usr/lpp/ctg500/ctg/classes/. We entered the command to query the current
state of the trace:
java -jar ctgadmin.jar -ctg=tcp:\\wtsc66oe.itso.ibm.com:2810 -a=qtrace
Example 7-27 shows the result of this command. The tlevel in the JNI trace
settings is 0, indicating tracing is off.