Previous Topic: Configuring CA IDMSNext Topic: Specifying Environment Variables for IPv6


Specifying Environment Variables

You must specify the locations of the executables, DLLs, and Java class files for a z/OS application to use CA IDMS Server in the USS environment. Set the standard UNIX environment variables to specify these locations:

PATH

Specifies the locations of executable files.

LIBPATH

Specifies the locations of DLL files.

CLASSPATH

Specifies the locations of Java class files.

For example, to run a JDBC application that uses the JDBC driver, these variables could be set as follows:

set PATH=$JAVA_HOME/bin:$PATH
export PATH
set LIBPATH=/idmsdir/mvs:$LIBPATH
export LIBPATH
set CLASSPATH=/idmsdir/classes:/idmsdir/lib/idmsjdbc.jar:$CLASSPATH
export CLASSPATH

In this case, $JAVA_HOME identifies the directory where Java is installed, and /idmsdir represents the directory chosen when CA IDMS Server was installed. Note that it is not necessary to include the /idmsdir/bin directory in the PATH to run a Java application. It is not necessary to set the PATH, LIBPATH, and CLASSPATH environment variables when using the supplied shell scripts to run the JDBC server. These environment variables are automatically set in the shell scripts installed in the /idmsdir/bin directory, equivalent to the following:

set PATH=$JAVA_HOME/bin/idmsdir/bin:$PATH
export PATH
set LIBPATH=/idmsdir/lib/mvs:$LIBPATH
export LIBPATH
set CLASSPATH=/idmsdir/classes:/idmsdir/lib/idmsjsrv.jar:$CLASSPATH
export CLASSPATH

Note: The shell scripts assume that JAVA_HOME has been set, typically in a user profile.

Optional environment variables specific to CA IDMS Server include:

IDMS_CFG_PATH

Specifies the configuration file name or path.

IDMS_CFG_RELOAD

Forces reloading of the configuration file.

Important! When invoking Unix scripts and programs using the BPXBATCH utility, it is possible to set environment variables using the STDENV DD statement. This is particularly useful when scheduled batch jobs are used to automate startup and shutdown of the JDBC server.