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

178 CICS Transaction Gateway V5
TG started task. We chose the STDENV method and added the following
parameter to the PDS member referenced on our STDENV DD statement:
CTG_JNI_TRACE=/ctg/scsctg5/logs/jni.trace
This caused the JNI trace to be written out to the HFS file specified. The JNI
trace includes information about the ECI requests and the EXCI flows the CICS
TG creates. Example 7-29 shows the output of the JNI trace.
Example 7-29 CICS TG trace table
CICS Transaction Gateway JNI Trace file for z/OS Version 5.0 Service Level 00 , Build Level
c000-20020621
04:30:50.745 CM-0 ¨ : CCL6806I: CcicsInit: Register with RRS. Return code = 768.
04:30:53.172 Worker-0 ¨ : CCL6800I: CcicsECI: ECI parameters on entry. Call_Type = 1,
Extend_Mode = 1, Luw_Token = 0, Commarea_Length = 80, Cics_Rc = 0, Flags = 0.
04:30:53.190 Worker-0 ¨ : CCL6801I: CcicsECI: Performed parameter conversion. parameter
name = jstrServer, parameter value = SCSCPJA1.
04:30:53.206 Worker-0 ¨ : CCL6801I: CcicsECI: Performed parameter conversion. parameter
name = jstrProgram, parameter value = EC02 .
04:30:53.219 Worker-0 ¨ : CCL6802I: CcicsECI: Input commarea information. commarea length =
80, commarea address = 11517c78.
04:30:53.234 Worker-0 ¨ : CCL6818E: CcicsECI: Begin Context failed. RRM Return code = 1878.
04:30:53.248 Worker-0 ¨ : CCL6805I: CcicsECI: ECI parameters on exit. Call_Type = 1,
Extend_Mode = 1, Luw_Token = 0, Commarea_Length = 80, Cics_Rc = -9, AV = 0.
We begin reading our trace from the bottom up. The last line shows the output
we pass back to the CICS TG. The next line up shows we received a return code
1878 from RRS.
In looking at the MVS Programming: Resource Recovery, GC28-1739, we see
that error codes must be converted from decimal to hexadecimal. Decimal 1878
is hex 756, which translates to CRG_AUTH_FAILURE. The text of a 756 error
tells us the program encountered an error registering with the resource manager.
At this point, we should start to suspect RRS and thus the setting of the CICS TG
CTG_RRMNAME variable.
A further confirmation of this lies in the second line from the top. This shows the
CICS TG trying to register its RRMNAME with RRS. It receives a 768 return
code, which is a hex 300. The MVS Programming: Resource Recovery,
GC28-1739 shows the 300 error to be a CRG_RM_NAME_INV and the help text
of the message details that the resource manager name specified in the call is
incorrect.
Knowing this information, we changed the CTG_RRMNAME to a valid name
(CCL.CTG.IBM.UA), restarted the CICS TG, and the example started working.