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

incorrect CTG_RRMNAME (CCL.IBM.CTG5.XX) as the CICS TG environment
variable. This caused an ECI_ERR_SYSTEM_ERROR (-9) return code on the
ECI call.
Tip: The error in our CTG_RRMNAME variable was that it did not end in UA.
For further details on using transactional EXCI and defining the
CTG_RRMNAME, refer to 7.2.1, “Defining CICS TG environmental variables”
on page 148.
EXCI trace
The first trace we illustrate is an EXCI trace of the Gateway daemon started task
on z/OS. This trace is more complicated to set up than the other traces, but has
the advantage that the trace table is stored in the Gateway region address space,
and so can be analyzed after the error (providing the trace is still in the buffer).
The process for getting an EXCI trace is outlined in the manual z/OS Gateway
Administration, SC34-5935, and is repeated here for clarity.
1. Use the following command to display all OMVS tasks:
/D OMVS,A=ALL
2. Find the Gateway address space, and note the address space ID (ASID).
Tip: By default the Gateway started task uses two address spaces, one for the
UNIX System Services shell running the ctgstart script and one for the
address space running the JVM for the Gateway daemon. In our configuration,
the ctgstart address space was called SCSCTG5 and the JVM address space
was called SCSCTG55. We dumped the JVM address space SCSCTG55,
because this is the address space that performs EXCI calls.
3. Enter the DUMP command with a suitable comment. For example:
/DUMP COMM=(JGATE DUMP RRS)
4. Reply to the message with the ASID as follows:
/R 495,ASID=401,END
where 495 is the message number for the reply, and 401 is the ASID.
5. The system will dump as shown in Example 7-22. Note the dump name
created. In our example, the dump name was
DUMP.D0529.H17.SC66.#MASTER#.S00072.
Example 7-22 Dumping the Gateway address space in SDSF
R 495,ASID=401,END
IEE600I REPLY TO 495 IS;ASID=401,END
Chapter 7. TCP connections to the Gateway daemon on z/OS 171