CORBA 2.3.7 Programmer's Guide for C++

Services Shell and Utilities Reference Manual.
Most OSS commands have direct counterparts in UNIX, although some commands and utilities are unique to OSS.
In some cases, OSS extends a UNIX command to provide access to features of the NonStop Kernel.
To get online information about OSS commands and utilities, use the man command (an abbreviation for manual).
For example, to get more information about the gtacl command, type:
man gtacl
Using Guardian Commands and Files Through OSS
NonStop CORBA applications can run as OSS processes or as Pathway server-class processes. The OSS gtacl
command provides access to the Guardian environment from the OSS environment. NonStop CORBA shell scripts
use the gtacl command to access the Guardian environment from the OSS environment. Interactive users can use
TACL in a Guardian window as an alternative to using gtacl.
The following examples show how you would run the Guardian fileinfo and status commands using gtacl:
gtacl -c fileinfo
gtacl -c 'status $ztc0'
You can also use Guardian files from the OSS environment by following a standard naming convention: in OSS, the
string /G designates the Guardian file system. You can also access OSS files systems on other Expand nodes by
using /E/node. The following example shows how you would use the OSS ls command to list the contents of the
Guardian subvolume $data1.nsdom:
ls /G/data1/nsdom
The OSS run command lets you run a process with specific attributes. For example, you could use the following
syntax to run a named process:
run -name=Guardian-process-name program-name
For example,
run -name=/G/svr Test_DII_SVR -ORBprofile tcp_sample_svr
In this example, svr is an arbitrary location. tcp_sample_svr is passed when ORB_init() is called.
OSS Environment Variables and the env.sh File
A shell implements environment variables that you can set and display. Processes started from the OSS shell can
access exported environment variables. For example, NonStop CORBA processes and utilities use environment
variables when you configure the system, develop a component, or run an application. The
$NSD_ROOT/etc/env.sh file stores shell commands that set environment variables. The env.sh shell script
must be executed during shell initialization by using .profile, or by using the dot (.) command to execute the
env.sh shell script in the current shell. If you log on only for NonStop CORBA work, it is often easier to set the
environment variables using .profile. However, if you use many application environments, it may be easier to
execute the env.sh script.
A subset of the environment variables set in the env.sh file are relevant for compiling and building NonStop
CORBA applications:
> export NSD_ROOT=/usr/tandem/nsdoms