The NonStop DOM PAX Files
Installation Locations
Installing NonStop DOM Into the Default File Locations
Specifying Custom Installation Locations
Installation Subdirectories
This topic details the steps used to install the NonStop DOM product on a Tandem NonStop Kernel system. While an installation utility is provided with NonStop DOM (in script format), this topic can be used as a reference to the installation process.
NonStop DOM version 2.0 is released in two different product packages. One package contains the NonStop DOM Software Development Kit (SDK) and the other package contains the Runtime-only version of the product. If you are going to develop NonStop DOM client or server applications, you will need the SDK release of the product. The Runtime release is needed if you are only going to run existing NonStop DOM applications.
The SDK and the Runtime product releases are each delivered on a different Compact Disc (CD). Each CD contains three different editions of NonStop DOM; one for each of the supported operating systems: D42, D45, D46, G05, and G06. Each edition is contained in a PAX file, which is a compressed container file consisting of text and binary files. You use the Open System Services (OSS) pax utility to unpack the NonStop DOM files and install the software on your OSS system.
The location and filenames of the PAX files for both the SDK and the Runtime versions of NonStop DOM are outlined in the following table:
| NonStop DOM Release CD |
Product Version |
Supported Platforms |
PAX File SOFTDOC File |
Notes |
|---|---|---|---|---|
| NonStop DOM SDK CD |
T7888D43 | D42 and above (no G-series support) |
D43\T7888PAX D43\T7888D43 |
Does not support C++ exceptions |
| T7888D46 | D45, G05, and above | D46\T7888PAX D46\T7888D46 |
Supports C++ exceptions, but does not support exceptions for threading. |
|
| T7888G06 | D46, G06, and above | G06\T7888PAX G06\T7888G06 |
Full support of C++ exceptions | |
| NonStop DOM Runtime CD |
T7889D43 | D42 and above (no G-series support) |
D43\T7889PAX D43\T7889D43 |
|
| T7889D46 | D45, G05, and above | D46\T7889PAX D46\T7889D46 |
||
| T7889G06 | D46, G06, and above | G06\T7889PAX G06\T7889G06 |
Note: Although the T7888D46 product release (supported on D45 and G05 platforms) supports C++ exception handling with the catch and throw C++ keywords, it is recommended that you use the native C++ exception handling in single-threaded environments only. In all scalable and mulit-threaded NonStop DOM applications, use the environment exceptions supported through the use of the CATCH and THROW macros. The T7888G06 product release lifts this restriction.
Each product CD contains three separate versions of the SOFTDOC file, one for each edition of the product. The SOFTDOC file for each product edition is located on the CD in the same directory as its related PAX file. Each SOFTDOC file is named after the product version to which it is related.
The SOFTDOC files contain up-to-date information related to the product. Before proceeding with the software installation, review the SOFTDOC file to see if it contains any updated installation instructions. After completing your NonStop DOM installation, copy the SOFTDOC file to your NonStop DOM docs subdirectory for easy reference.
To install NonStop DOM, the appropriate PAX file must be transferred from the CD to the target Tandem system. FTP is the most convenient and widely used way to transfer files between two computers. To use FTP, run an FTP client application on the computer containing the NonStop DOM CD. In addition, you must also run Tandem's FTP server product on the target Tandem system.
In the steps that follow, it is assumed that the system containing the product CD is a Windows-based system running a command-line FTP client. If you are using an FTP application that has a graphic user interface (GUI), ignore the commands given here and navigate using the graphical commands of your FTP tool.
To copy the pax file:
> ftp
The FTP prompt displays:
ftp>
ftp> open <tandem system host name> | <IP address>
oss so that you can use the OSS syntax for directory naming:
ftp> quote oss
ftp> cd /G/SYSTEM/ZDOMSD20
To install the Runtime version of NonStop DOM, change to the /G/SYSTEM/ZDOMRT20 directory on the remote (Tandem) system:
ftp> cd /G/SYSTEM/ZDOMRT20
ftp> lcd D:\G05
ftp> binary
ftp> put NSDFWPAX
ftp> quit
Before proceeding, decide if you want to install the product into the default NonStop DOM file locations or into custom file locations that you specify when you unpack the files.
For example, if you want to have multiple NonStop DOM installations on a single system, you will need to use custom file locations to specify the different setups. Also, if you do not have write access to $SYSTEM , you will need to use a customized installation.
To install into a customized location, follow the instructions in Specifying a Custom Installation Location.
By default, the unpax command installs NonStop DOM in the following locations:
| File Type | Location |
|---|---|
| OSS files | /usr/tandem/nsdoms/ |
| Guardian files | /G/SYSTEM/ZDOMSD20(SDK version of NonStop DOM) |
| Guardian files | /G/SYSTEM/ZDOMRT20(Runtime version of NonStop DOM) |
With the appropriate pax file copied from the CD to your system, follow these steps to extract the NonStop DOM files into the default file locations:
> osh
/usr/tandem exists and that that the current userid has write access to the /usr directory.
<NSDFW_Path> refers to the full file path where the NonStop DOM pax file exists:
> pax -rvf <NSDFW_Path>NSDFWPAX -W clobber
For example, if you are installing the SDK version and have copied the pax file to the /G/SYSTEM/ZDOMSD20 directory, you would issue the following command to unpack the file:
> pax -rvf /G/SYSTEM/ZDOMSD20/NSDFWPAX -W clobber
Caution: The -W clobber switch tells the pax utility to overwrite any previously existing Guardian system files. Without this switch, existing Guardian files on your system will not be updated with the new NonStop DOM system files.
The installation procedures for NonStop DOM installs files in both the Guardian file space and the OSS file space. By default, the files are installed into the locations described in Table 2.
To specify a custom installation location, use the -s option of the pax program. With the -s option, you can redirect the target directories for both the NonStop DOM OSS files and Guardian files.
Use the following command to unpack the NonStop DOM system files, where <NSDFW_Path> refers to the full file path where the NonStop DOM pax file resides:
> pax -rvf <NSDFW_Path>NSDFWPAX
[-s:/usr/tandem/nsdoms:<your-dir>:]
[-s:<default-subvolume>:/G/<your-vol-subvol>:] -W clobber
In this command, the parameter <your-dir> specifies the base OSS directory where you want the files installed. The parameter <default-subvolume> specifies the default Guardian file location which is ZDOMSD20 for the SDK version and ZDOMRT20 for the Runtime version. The parameter <your-vol-subvol> specifies the Guardian file location where you want the Guardian files to reside.
For example, if you are installing the SDK version of the product, and have copied the pax file to the /G/SYSTEM/ZDOMSD20 directory, you would issue the following command to unpack the file:
> pax -rvf /G/SYSTEM/ZDOMSD20/NSDFWPAX
[-s:/usr/tandem/nsdoms:<your-dir>:]
[-s:/G/SYSTEM/ZDOMSD20:/G/<your-vol-subvol>:] -W clobber
To install the Runtime version, use this command:
> pax -rvf /G/SYSTEM/ZDOMRT20/NSDFWPAX
[-s:/usr/tandem/nsdoms:<your-dir>:]
[-s:/G/SYSTEM/ZDOMRT20:/G/<your-vol-subvol>:] -W clobber
When you unpack the NonStop DOM files, the pax utility places the files into several subdirectories that it creates during the unpacking process. These directories are all created below the main NonStop DOM directory, which is /usr/tandem/nsdoms/ by default.
The subdirectories created in the installation process are outlined in the following table:
| Subdirectories | Directory Contents |
|---|---|
| bin | Contains executable programs, including all configuration related tools described in this and other sections. |
| docs | This directory is empty at first; it is a place-holder for the NonStop DOM documentation set. |
| etc | Contains miscellaneous system files, such as the env.sh and default.db files. |
| idl | Contains the nsdidl.jar file. |
| include | Contains C++ header files, which you use when compiling NonStop DOM applications. |
| include_env | Created only with the D46 and G06 editions, this directory contains header files specific to programs that use environment exceptions. (In the D43 edition, these files are contained in the include directory.) |
| lib | Contains object files required for clients of the Naming and Event services. The Event service sample application shows how to use these files. |
| lib_env | Created only with the D46 and G06 editions, this directory contains library files specific to programs that use environment exceptions. (In the D43 edition, these files are contained in the lib directory.) |
| log | This is a placeholder for generated log files. |
| samples | Contains the source code for all the sample programs shipped with the product. |
| /G/vol/subvol | Contains the NonStop DOM files that reside on the Guardian file system, such as the SRL and ems template files. |