The ctgenvvar script

Use the ctgenvvar script if the Gateway daemon is to be started via the USS command line for example, in a test environment.

The ctgenvvar script can be executed alone or referenced by the ctgstart script to set the variables. You can create the ctgenvvar script by editing the supplied ctgenvvarsamp script, and then copying or renaming to ctgenvvar, see Configuration parameter reference.

Because the files under <install_path>/bin are managed by SMP/E, this area is regarded as read-only. Therefore, the customized ctgenvvar script is likely to be located under a user-writable HFS path.

When running the Gateway daemon via the ctgstart script, the environment variable CTGENVVAR, if set, will be used to define the fully qualified location of a ctgenvvar script (including the file name of the script). If CTGENVVAR is not set, ctgstart will check for the script ctgenvvar under the HFS path <install_path>/bin (for compatibility with previous versions). For example,

export CTGENVVAR=/u/ctgusr/ctg910cfg/ctgenvvar

If neither of these locations contains a script, ctgstart will assume that the environment variables are already in place, and attempt to start the Gateway daemon.

The target script itself must have the '+x' executable file attribute set at the appropriate level for the current user.

After you have installed the product, you can use ctgenvvar to establish the environment that Java™ Client applications running in local mode will use, for example:

<config_path>/ctgenvvar

where <config_path> is the HFS location of the customized configuration script.

By default, ctgenvvar searches for ctgstart, so you must ensure that <install_path>/bin is in the path for the current environment. You can edit ctgenvvar to define where ctgstart is installed.

Information

Feedback

Timestamp icon

Last updated: Wednesday, 27 August 2014

https://ut-ilnx-r4.hursley.ibm.com/tgzos_latest/help/topic/com.ibm.cics.tg.zos.doc//configuring/topics/cclaicus.html