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

4.2.1 EXCI CONNECTION definitions
68 CICS Transaction Gateway V5
Figure 4-2 shows the EXCI connection definition we used for the connection to
our CICS TG region, SCSCTG5.
OVERTYPE TO MODIFY CICS RELEASE = 0530
CEDA ALter Connection( CTG5 )
Connection : CTG5
Group : CTG5
DEscription ==>
CONNECTION IDENTIFIERS
Netname ==> SCSCTG5
INDsys ==>
CONNECTION PROPERTIES
ACcessmethod ==> IRc Vtam | IRc | INdirect | Xm
PRotocol ==> Exci Appc | Lu61 | Exci
Conntype ==> Specific Generic | Specific
SInglesess ==> No No | Yes
SECURITY
SEcurityname ==>
ATtachsec ==> Local Local | Identify | Verify
| Persistent | Mixidpe
Figure 4-2 EXCI connection definition
SYSID=PAA6 APPLID=SCSCPAA6
The important parameters in an EXCI connection definition are:
► CONNECTION
This is the name of the connection itself, as it is known to CICS. Any
four-character name can be used. It must match the CONNECTION
parameter specified in the SESSIONS definition. See Figure 4-3 on page 70.
► NETNAME
If this is specified, then the connection is configured to use a specific pipe. If it
is left blank, then the EXCI connection will use a generic pipe. If using specific
pipes, then this must correspond to the name of the pipe as also specified in
the EXCI client program. This is specified on the user_name parameter of an
Initialize_User EXCI call. When using the CICS TG for z/OS, this value is
passed to the EXCI using the DFHJVPIPE environment variable, the setting
of which is described in Figure 7-5 on page 149.
If the NETNAME parameter is not specified, then a generic pipe will be used,
which is essentially an unnamed pipe. Generally it is best to use a specific
pipe, since this aids in management of multiple connections and in problem
determination.