Configuring a remote mode topology

Configuring the Gateway daemon

The Gateway daemon is configured by creating a configuration file and a set of environment variable definitions, defined by the STDENV DD card of the Gateway daemon JCL CTGBATCH job step. See STDENV file for more information. The configuration file can reside on the USS file system or as an MVS™ data set on the MVS file system, with the path or MVS data set defined by the environment variable CICSCLI. If the environment variable CICSCLI is not defined, the Gateway daemon will look for a configuration file, ctg.ini, in the product \bin directory. This is the historical default location, however, it is recommended to use another location outside the SMP/E-managed product install path.

You can specify a different location and optionally change the name of the configuration file ctg.ini by setting the CICSCLI environment variable to point to a USS file:

CICSCLI=/u/userid/myconfig.ini

If the configuration is maintained in MVS and edited using ISPF, you can set the CICSCLI environment variable to point to the MVS data set name or data set location:

CICSCLI=//'HLQ.QUAL.PDS(MEMBER)'

Use the double forward slash symbol // to denote that the configuration is held in an MVS data set not a file. The CICS Transaction Gateway startup message CTG8400I indicates the location of the configuration if it is in a data set that uses the same notation. A sample configuration on MVS is provided in data set member CTGCONF, in the CTGSAMP data set which is installed as part of the product. If a value is not specified for this environment variable, the default path <install_path>/bin/ctg.ini is used during startup. The maximum field length is 100 characters.

At startup, the name and location of the configuration file being used is written to the Gateway information log.