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

74 CICS Transaction Gateway V5
► CTG_RRMNAME as a CICS TG environment variable
This is the name that the CICS TG registers with RRS for transactional EXCI
requests to CICS. You will only need to modify this if using transactional EXCI
requests. For further details on how we implemented transactional EXCI with
our CICS TG for z/OS, refer to Chapter 7, “TCP connections to the Gateway
daemon on z/OS” on page 133.
4.3 EXCI definitions for the CICS TG
The following environment variables are specific to the CICS TG for z/OS. We
specified these parameters in the PDS member named on our STDENV card in
the CICS TG started task, but they can also be set in the ctgenvvar HFS file,
among other places. For further details on how the settings of these variables are
controlled, refer to Figure 7-5 on page 149. For step-by-step details on how we
configured our CICS TG for z/OS, refer to Chapter 7, “TCP connections to the
Gateway daemon on z/OS” on page 133.
The parameters we used in our CICS TG for z/OS are as follows:
► DFHJVPIPE
This parameter names the EXCI pipe in use by the CICS TG (when using a
specific EXCI connection). If not specified, the CICS TG will use a generic
pipe. We set this parameter to the name of our CICS TG region (SCSCTG5),
to help with management and problem diagnosis.
Note: The DFHJVPIPE value must match the NETNAME parameter in the
CICS CONNECTION definition.
► EXCI_LOADLIB
This is the name of the library containing the EXCI load modules (without its
high-level qualifier). This will usually be SDFHEXCI, and so does not usually
need modifying.
► EXCI_OPTIONS
This is a user library that contains the EXCI options to be used if you have a
tailored version of the EXCI options table (DFHXCOPT). For more details,
refer to “SURROGAT security checking and DFHXCOPT” on page 125.