The STDENV file can be used if the Gateway daemon is
to be started in batch mode using CTGBATCH to define the required
environment variables.
When using CTGBATCH to start the Gateway daemon, if
a ctgenvvar file exists in the default install
directory, the settings in the ctgenvvar file
are used in preference to those defined in the STDENV file.
This is because the ctgenvvar file is referenced
within the ctgstart script.
Use the conversion script ctgconvenv, to convert
environment variables, previously set by the ctgenvvar script,
into a STDENV file that can then be used by the
CTGBATCH program.
The
STDENV file can be an MVS™ sequential
file, a PDS member, or an HFS file and has the following syntax rules:
- Any line with a hash (#) in column one is interpreted as a comment.
- Blank lines are ignored.
- Leading spaces are removed from a line.
- An entry for a name/value pair can start in any column.
- A valid entry for a name/value pair must not have
spaces between the name, equals sign or value.
- Use backslash (\) as a continuation character.
- Trailing spaces after a continuation character are removed.
- A continuation character can be placed in any column.
- A continuation character must be the last non-whitespace character
on a line.
- A value containing continuation characters is deemed to be completed
by the first line that omits the continuation character.
- Trailing spaces are removed from single-line data and from the
end of concatenated multi-line data.
- Do not enclose value strings in single or double quotes. Every
character, after the first equals sign, that is not a trailing space
or continuation character is assumed to be part of the value data.
A sample STDENV file is in the SCTGSAMP library
as a member CTGENV.
Information
Last updated: Wednesday, 27 August 2014