CORBA 2.6 Administration Guide

. /usr/tandem/nsdoms/etc/env.sh
Customizing the env.sh file
You might want to customize the env.sh file to reflect a special NonStop CORBA setup. For example, if you
wanted to move the NonStop CORBA files from one Guardian subvolume to another, you need to make a change
to the NSD_DIR and NSD_SUBVOL environment variables in env.sh. Use a text editor to modify env.sh.
After editing the file, you must execute the script (as described in Setting Environment Variables) in order for the
new settings to take effect.
Note: While you can freely move your application files, you should not move NonStop CORBA files to a
different Guardian subvolume or OSS directory if you use the Distributed Systems
Management/Software Configuration Manager (DSM/SCM) to manage your NonStop CORBA
Installation. DSM/SCM will not be aware of the location of any files you move.
The following table gives a brief description of each environment variable set in the env.sh script. The table
also shows the default script settings.
Variable Default Setting* Description
NSD_ROOT /usr/tandem/nsdoms
Sets the root OSS
directory for your
NonStop CORBA
installation.
MY_ROOT $NSD_ROOT
Sets up a custom
NSD_ROOT variable
to allow for multiple
custom installations.
By default, the
value is the same as
NSD_ROOT.
NSD_DIR
/G/SYSTEM/ZORBSDK or /G/SYSTEM/ZORBRTK
Specifies the
NonStop CORBA
Guardian volume
and subvolume for
NonStop Kernel
files; must be
expressed in OSS
directory format.
NSD_SUBVOL
"\$SYSTEM.ZORBSDK" or "\$SYSTEM.ZORBRTK"
Same as NSD_DIR,
but expressed in
NonStop Kernel
(Guardian) format
(a backslash before
the dollar sign and a
double-quoted
directory location).