CORBA 2.6.1 Programmer's Guide for C++

Chapter 2. NonStop CORBA Administrative Environment
Chapter 2. NonStop CORBA Administrative Environment
Working in the Open System Services (OSS) Development Environment
Using Guardian Commands and Files Through OSS
OSS Environment Variables and the env.sh File
OSS Development and Debugging Tools
Working in the NonStop CORBA Administrative Environment
Components of the NonStop CORBA Environment
Using the NonStop Distributed Component Console
Running NSDAdminServer and NSDEnvironServer
Application Profiles: Configuring and Managing an Application
Working in the Open System Services (OSS) Development
Environment
NonStop CORBA applications are implemented by Open System Services (OSS) processes in the OSS environment of the NonStop Kernel
operating system. The OSS environment coexists with the Guardian environment and provides an independent alternative to it. OSS conforms
to open computing industry standards, specifically to the POSIX.1 (API) and POSIX.2 (shell/commands) standards. The OSS environment
provides a UNIX® personality to the NonStop Kernel, but unlike UNIX, OSS is not an operating system. The NonStop Kernel is the operating
system for both the OSS and the Guardian environments.
OSS consists of the following major components:
File system: the OSS file system has a hierarchical structure similar to that of UNIX, composed of directories, subdirectories, files, and
pseudo-files such as links and pipes. The OSS file system uses the flat Guardian file system.
Application programming interfaces (APIs).
Run-time libraries.
Command interpreter (OSS shell): the OSS shell is a POSIX.2-compliant command shell that is based on the Korn shell.
User commands and utilities.
The osh command enters the OSS environment and starts an OSS shell process.
To work with NonStop CORBA, you need to have a basic understanding of the OSS environment and you need to know how to use some of
the OSS commands. A few of the commands most used in preparing a NonStop CORBA application are described in the following sections. For
more complete information about programming in the OSS environment and OSS commands, consult the Open System Services Programmer's
Guide and the Open System 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 TS/MP 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