Previous Topic: Prepare the Target EnvironmentNext Topic: How to Create and Test External Action Blocks on NonStop


Define OSS Environment Variables

The IT components that were installed to support NonStop SQL/MX use environment variables to specify paths and other configuration information necessary to build and use CA Gen applications. The environment variables set up macros, or aliases, referenced in several places, including the MAKE files, source code, and script files. Each user's .login file must set the variables to ensure that they are properly set during system logon, before invoking the Build Tool or the AEF.

When set, environment variables retain the new values until the end of the current logon session, or until they are dynamically changed. When a process spawns a new shell, environment variables revert to their original logon values. When exiting the new shell, the variables reset to the values they held before the new shell was spawned.

To display the current environment, use the env command. To view the current value of an environment variable, use the echo command as displayed in the following example:

echo $IEFH

Required OSS Variables

The following table describes the set of environment variables required to use the IT for NonStop SQL/MX:

Name

Description

IEFH

CA Gen IT home directory for NonStop SQL/MX. This is the directory used to locate the runtime libraries and the Build Tool.

Example:

export IEFH=/opt/gen85

IEFPLATFORM

Name of hardware platform. This needs to be set to IEF_NONSTOP.

IEFGXTP

Specifies the directory that contains the codepage translation files.

Example:

export IEFGXTP=$IEFH/translat

SQLMX_HOME

Location of the SQL MX Preprocessor.

Example:

export SQLMX_HOME=/usr/tandem/sqlmx

PATH

Search path for executables. This must include $IEFH/bin, $IEFH/bt, and SQLMX_HOME.

Example:

export PATH=$IEFH/bin":"$IEFH/bt":"$SQLMX_HOME/bin":"$PATH