Server includes sample EXCI connection and session definitions (EXCG
and EXCS). These are in the sample group DFH$EXCI.
You can use the supplied definitions without modification, you
can copy and modify the supplied definitions, or you can create completely
Here are two examples of a connection definition:
The key parameters are shown in bold in the examples, these are:
If you enter a Netname, the connection uses
a specific pipe. If you leave it blank, the EXCI connection uses a
generic pipe. You should ideally use a specific pipe because this
helps to manage multiple connections, and to identify problems.
you use specific pipes, set Netname to be the same as the pipe specified
in the EXCI client program. You specify this on the user_name parameter
of an Initialize_User EXCI call. Set the DFHJVPIPE environment variable
to allow CICS Transaction Gateway
to pass this value to the EXCI. For more information see Setting environment variablesSetting environment variables. If you use the
sample DFH$EXCI, set the DFHJVPIPE environment variable to BATCHCLI
to use the specific pipe.
If CICS Transaction
Gateway is configured to connect to more than one CICS server, use the same Netname for all EXCI
Specify IRC (interregion
This defines the type of EXCI connection used
for jobs that are not CICS to
communicate with a CICS server
on IBM® z/OS®.
This is a type of multiregion operation (MRO) request and can be either
Generic or Specific.
Generic: An MRO link with multiple sessions to be shared by multiple
EXCI users. Only one generic EXCI connection can be installed in each
server. Specify Generic if you left the Netname attribute blank.
Specific: An MRO link with one or more sessions dedicated to
a single user in a client program. Specify Specific if you completed
the Netname attribute.
This determines whether a check is to be made
against the flowed user ID. Specify Local or Identify.
Local: CICS Transaction
Gateway does not flow a user identifier; just the link user ID (if
specified) is used. If no link user ID is supplied, all requests are
run under the CICS default
user ID as specified in the DFLTUSER SIT parameter.
Identify: A user ID is flowed on every request, but a password
is not expected, because CICS trusts
the user ID as having been already authenticated.
For security reasons, consider enabling user ID and password
verification within CICS Transaction
Gateway, before the EXCI request is made. The user ID is either the
user named in the ECIRequest object (if null), or the user ID of the
thread under which the ECI request runs.