Environment settings
To run WebSphere® Transformation Extender for z/OS®, a set of environment variables must be set.
They are usually established by running a shell script from the UNIX command line. Since there is no UNIX command line being used in this case, an environment-variable file is used to configure the settings for the local administration interfaces.
File location
The sample environment variable file location resides in DTX.SDTXCNFG(DTXENVAR). It contains pre-specified default values that are included in the WebSphere Transformation Extender for z/OS installation.
The location of the DTXENVAR must also be specified in a CLIST or REXX EXEC to start the ISPF interface. A sample REXX EXEC is included in the installation-defined data set, DTX.SDTXCLST(DTXCLIST).
DTXENVAR environment variable file
The contents of DTXENVAR include settings for the following variables:
- Environment Variable
- Description
- _CEE_RUNOPTS
- Language Environment® runtime
options for the Launcher process.
This is an optional field that you can override. See the IBM® z/OS Language Environment Programming Reference, SA22-7562 for a description of the valid runtime options.
- CENTRAL_MGMT
- Configuration value indicating whether
to use centralized (global) or local resource management.
Valid values are YES for centralized (global) resource management and NO for local.
Centralized (global) indicates that resource management will allow multiple processes to share common resources properly.
Default value is NO.
- CONNECTION_RETRY_COUNT
- The maximum number of times the z/OS
native interface is allowed to attempt the TCP/IP connection to the Launcher control port before an error condition, if
attempts are not successful, is raised.
Default value is 10.
Note: If the CONNECTION_RETRY_COUNT value is reached before the z/OS native interface can start or detect the Launcher, the "TX is not active..." message will appear. - DEBUG
- Enable debug option. Valid values are YES to
enable the debug option and NO to disable it.
Default value is NO.
- INI_FILE
- config.yaml file
Override the default location and name of the config.yaml file.
Uncomment the line by removing the # character in front of INI_FILE and replace <configuration directory>/<ini file> with a valid file location of the .ini file to be used.
- LAUNCHER_NAME
- Symbolic name assigned to the current Launcher. It uniquely
identifies the Launcher instance
and is also used to prefix the Launcher and debug
logs when running the multiple-process Launcher.
The name is displayed in the ISPF DTXEVNT window.
Default value is Launcher-Name.
Note: Maximum length is 19 characters and the name should not contain any spaces. - DTX_CONTROL_PORT
- TCP/IP port number used for control
information when communicating with the Launcher process.
Default value is 7002.
- DTX_HOME_DIR
- Installation location for the Launcher)
Default value is /u/dtx/Launcher.
- DTX_MONITOR_PORT
- TCP/IP port number used for monitoring
information when communicating with the Launcher process.
Default value is 7001.
- DTX_STATUS_PORT
- TCP/IP port number used for status
information when communicating with the Launcher process.
Default value is 7000.
- SYSTEM_FILE
- Location of a single system (.MSL)
to be used in a multiple-process Launcher configuration.
Uncomment the line by removing the # character in front of SYSTEM_FILE. Replace <deployment directory>/<system name>.msl with the valid file location of the system to be executed.
- TIME_ZONE
- Time zone used.
This is required only if the locale defined to z/OS UNIX System Services (z/OS UNIX) does not contain a valid LC_TOD category.
Default value is EST5EDT.
- VIPA_HOSTNAME
- The host name for the Virtual IP Address (VIPA) where the Launcher is running. This environment variable is required only when the ports used by the Launcher are defined as VIPA ports.