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

7.2.3 EXCI pipe usage
154 CICS Transaction Gateway V5
► noinput=no
This means the ctgstart script is able to read input if it is started from the
UNIX System Services shell. If ctgstart is run as a started task, this parm has
no effect.
► nonames=on
This controls whether client host names are resolved via the DNS server. This
should be set to on to prevent delays.
► notime=off
This shows the timestamps in the message log. This should be set to off,
since timestamps are very useful in problem determination.
► tfile=/ctg/scsctg5/logs/ctg.trc
This is the location of the trace file. We set it to our CICS TG logging directory
we created in 7.2, “Configuration” on page 146.
► workertimeout=1000
This is the time in milliseconds a connection manager thread waits to obtain a
thread from the worker thread pool. This timeout prevents remote Java client
from hanging if all worker threads are in use.
The EXCI is used by the CICS TG for z/OS to send requests to the CICS region
specified in the ECI request. To make an ECI call, the CICS TG for z/OS uses the
EXCI CALL interface. The EXCI CALL interface provides a low-level API for
calling a CICS program using a COMMAREA, and consists of the following six
commands:
1. Initialize_User
2. Allocate_Pipe
3. Open_Pipe
4. DPL_Request
5. Close_Pipe
6. Deallocate_Pipe
The CICS TG does not perform a Deallocate_Pipe after it performs the initial ECI
request from any given thread. This means that a pipe stays allocated for the
lifetime of the thread and is not deallocated until one of the following occurs:
► An error is received by the CICS TG worker thread on an Open_Pipe call
► The CICS TG worker thread terminates
► The CICS TG address space terminates
► The CICS connection is placed out of service or IRC is closed
► The CICS region terminates