Tuxedo 8.0 Supplement for H-Series RVUs

Chapter 2. Installation

Installing NonStop Tuxedo

The steps to install NonStop Tuxedo on TNS/E systems are listed in the Readme file for this

independent product. This section contains information beyond the checklist items in the

Readme file.

A step when installing NonStop Tuxedo is running the shell script Install.sh after the

product pax files are copied to the target system. This is necessary in TNS/R and TNS/E

systems. When the core product is installed (including T8351), Install.sh checks the

validity of the required TS/MP 3.0 software, such as the ROUT, DIST, and other files. The

checks have changed to match the way that TS/MP 3.0 differs on TNS/E systems. Also,

checking for the correct TS/MP 3.0 installation can now be done independently of

Install.sh, using these new scripts:

$TUXDIR/bin/tsmp3_check

tsmp3_check checks that all required TS/MP 3.0 files are present and usable.

$TUXDIR/bin/rout_check

rout_check checks that the TS/MP 3.0 ROUT process is usable.

$TUXDIR/bin/rout_add

rout_add makes the TS/MP 3.0 ROUT process a persistent generic process. This operates

only on the current SYSnn.

On TNS/R systems, ROUT starts as part of the system cold load. On TNS/E, ROUT does not

require a cold load. Instead, ROUT is a persistent generic process as described in Section 3,

"Configuring and Managing Generic Processes" of the SCF Reference Manual for the Kernel

Subsystem. ROUT must be configured with SCF only once on a system, making it a generic

process with startmode KERNEL. Install.sh does this for you by calling the new

rout_add script.

After installing NonStop Tuxedo, two major changes can be observed in the installed files. One

change is that the $TUXDIR/lib directory contains DLLs as well as library archives. Those

DLLs have filenames ending with .so and are used at run time by NonStop Tuxedo

executables. The other change is that there are no NonStop Tuxedo libraries in