# hp Reliable Transaction Router
Installation Guide

Previous | Contents | Index

1. Kit name, version and number.
2. All RTR processes must be stopped before a successful installation.
3. Optional request to run IVP after installation.
4. Answer yes if you need definition files required for programming to the V2 API. Otherwise, answer no.
5. The destination defaults to the logical defined for SYS$COMMON.
6. Indicates that the installation verification procedure (IVP) has started.
7. Add the indicated lines for automatic startup and shutdown of RTR.
8. See Section 3.3.1.1 for information on use of the optional P1 parameter.

## 3.2.2 Read Release Notes

To access the Reliable Transaction Router Release Notes, type the command:

    $ PRODUCT EXTRACT RELEASE_NOTES RTR /file=rtr_relnotes.txt

You should read the Release Notes before using Reliable Transaction Router.

# 3.3 Complete RTR Setup

After completing the installation, you can:

- Edit system files
- Verify user account requirements

## 3.3.1 Edit System Files

You must edit the system startup and shutdown files to provide for automatic startup and the installation of Reliable Transaction Router images when your system is rebooted.

Add the command line that starts Reliable Transaction Router to the system startup file, SYS$MANAGER:SYSTARTUP_VMS.COM. Reliable Transaction Router cannot start until after the network has started. You must position this new command line after the lines that invoke the network startup command procedures.

Add the command line that stops Reliable Transaction Router to the system shutdown file, SYS$MANAGER:SYSHUTDWN.COM.

### 3.3.1.1 Establishing Protocol Preference

In RTR$STARTUP.COM, the symbol RTR_PREF_PROT defines the preferred network protocol. There are four choices:

> RTR_DNA_FIRST (DECnet first)
> RTR_DNA_ONLY (DECnet only)
> RTR_TCP_FIRST (TCP first)
> RTR_TCP_ONLY (TCP only)

By default, protocol preference depends on whether DECnet has been installed as follows:

Table 3-4 RTR Protocol Preference
If SYS$NODE is defined (DECnet installed), the default is: | If SYS$NODE is not defined, the default is:
--- | ---
RTR_DNA_FIRST | RTR_TCP_ONLY

This default behavior is the same as in previous versions of RTR and is backwards compatible with previous versions of RTR.

Previously the RTR system manager could override this default behavior by removing the comment character (!) from the appropriate DEFINE statement in RTR$STARTUP.COM. This is no longer valid or supported. To override the default behavior, add the following line to SYS$MANAGER:SYSTARTUP_VMS.COM:

    @sys$startup:rtr$startup.com preferred_protocol (P1)

Set the optional preferred protocol to one of the values in Table 3-5.

Table 3-5 Preferred Protocol Values
To use the following protocol: | Set the value as:
--- | ---
DECnet first | RTR_DNA_FIRST
DECnet only | RTR_DNA_ONLY
TCP/IP first | RTR_TCP_FIRST
TCP/IP only | RTR_TCP_ONLY

For example, the following line in SYS$SYSMANAGER:SYSTARTUP_VMS.COM sets the preferred protocol as TCP/IP first:

     @sys$startup:rtr$startup.com RTR_TCP_FIRST

Setting the prefered protocol eliminates the need to change the RTR$STARTUP.COM file on every system after each RTR upgrade or install. In addition, RTR$SHUTDOWN.COM internally detects the preferred protocol and shuts down RTR accordingly. In the unlikely event that RTR$SHUTDOWN.COM does not correctly detect the preferred protocol, the RTR system manager can explictly pass the value by adding the following line to
SYS$MANAGER:SYSHUTDWN.COM:

     @sys$startup:rtr$shutdown.com preferred_protocol

where the optional preferred protocol is taken from Table 3-5. For example, the following command would ensure that RTR detects the preferred protocol:

     @sys$startup:rtr$shutdown.com RTR_TCP_FIRST

## 3.3.2 Verify User Account Requirements

To work with Reliable Transaction Router, user accounts on your system must have certain quotas and privileges. The next two sections contain information on these requirements. If current settings are less than those required, increase them to the amounts required.

### 3.3.2.1 Check User Account Quotas

Table 3-6 summarizes the required user account quotas.

Table 3-6 User Account Quotas for Using Reliable Transaction Router
Account Quota | Value
--- | ---
ASTLM | At least 2000
BIOLM | At least 2000
BYTLM | At least 150000 1
DIOLM | At least 2000
TQELM | At least 2000

1At least 80000 for accounts running RTR applications. At least 150000 for accounts running the RTR ACP. This may need to be increased to accommodate large numbers of application programs and/or users. The formula to use is: 32K + 32K * n where n equals the number of application processes plus the number of users in the ACP's group.

### 3.3.2.2 Check User Account Privileges

To use the features of Reliable Transaction Router, each account must have the following privileges:

- NETMBX
- TMPMBX
- SYSLCK

In addition, the Rights Identifier RTR$INFO is required.

On Identifiers A fresh installation of RTR adds RTR$INFO and RTR$OPERATOR identifiers to those on your system (they are removed during an uninstall).

### 3.3.2.3 Check System Manager Account Privileges

The RTR System Manager (that is, the account that starts up RTR and creates facilities) must also have either OPER privilege or have the Rights Identifier RTR$OPERATOR.

## 3.3.3 Check Installed Files

To see the files installed on your system by the installation process, use the following command:

    $ PRODUCT LIST RTR/SOURCE=[pcsi kit location]

## 3.3.4 Enable RTR Remote Commands

To make it possible to execute RTR commands on remote systems, enable the capability with the SYSMAN Utility. See the documentation for SYSMAN in the OpenVMS documentation set for information on this utility. You can also execute remote commands with /NODE qualifiers on certain RTR commands, and in conjunction with the RTR SET ENVIRONMENT command. For more information on executing RTR commands remotely, refer to the Reliable Transaction Router System Manager's Manual.

## 3.3.5 Display CONOLD Documentation

Documentation for Reliable Transaction Router is available on the OpenVMS Online Documentation Library CD-ROM in hypertext (.html) file format. You can display the hypertext files on your workstation or PC using any HTML browser such as Internet Explorer or Netscape.

## 3.3.6 Run RTR

To run RTR, enter the following command at the OpenVMS system prompt:

    $ run SYS$COMMON:[SYSEXE]RTR
    RTR>

or

    $ RTR
    RTR>

You can then enter commands at the RTR prompt to configure RTR facilities and partitions, and run applications that use RTR.

### 3.3.6.1 Configure RTR Facilities and Partitions

For information on configuring RTR facilities and setting up partitions, refer
to the Reliable Transaction Router Getting Started and the Reliable Transaction Router System Manager's Manual.

## 3.3.7 Install and Run Applications

Once applications that use RTR have been designed and tested, they can be deployed on the systems configured for use with RTR. For information on designing RTR applications, refer to the Reliable Transaction Router Application Design Guide; for information on deployment and use, refer to
the Reliable Transaction Router System Manager's Manual.

# Chapter 4
Full Installation on Tru64 UNIX

This chapter describes how to install Reliable Transaction Router on Tru64 UNIX systems. It includes steps for:

- Preparing for installation
- Installing RTR
- Completing RTR setup

# 4.1 Prepare for Installation

Before you start the installation, complete the preparation tasks outlined in this section.

User-Changed Monitor Files If you have changed any RTR monitor (*.mon) files, you must rename them or they will be overwritten during installation. To avoid this, always work from renamed copies of RTR monitor files when making local modifications.

## 4.1.1 Check Software Distribution Kit

RTR software is distributed on CD-ROM. Use the Bill of Materials (BOM) to check the contents of your RTR software distribution kit.

## 4.1.2 Register Your Software License

RTR includes support for the License Management Facility (LMF). You must register your License Product Authorization Key (License PAK) in the License Database (LDB) in order to use RTR on a newly licensed node. The License PAK may be shipped along with the kit if you ordered the license and media together; otherwise, it is shipped separately to a location based on your license order.

If you are installing RTR as an update on a node already licensed for this software, you have already completed the License PAK registration requirements.

If you are installing prerequisite or optional software along with RTR, review the PAK status and install the PAKs for any prerequisite or optional software before you install RTR.

To register a license under the Tru64 UNIX operating system, first log in as superuser.

At the superuser prompt, edit an empty PAK template with the `lmf register` command as follows, and include all the information on your License PAK:

    #  lmf register

After you register your license, use the following `lmf reset` command to copy the license details from the License Database (LDB) to the kernel cache:

    #  lmf reset

For complete information on using the License Management Facility, see the Guide to Software License Management and the `lmf(8)` reference page.

Installing RTR, including running the Installation Verification Procedure (IVP), takes approximately 10 to 15 minutes, depending on your type of media and system configuration.

## 4.1.3 Check Login Privileges

You must have superuser privileges to install the RTR software.

## 4.1.4 Check Required Hardware

To install RTR, you need the following hardware:

- Software distribution device (if installing from media)
  Locate the CD-ROM drive for the CD-ROM software distribution media. The CD booklet or the documentation for the CD-ROM drive you are using explains how to load the CD-ROM media.
- Terminal
  You can use a hardcopy or video terminal or a workstation to communicate with the operating system and respond to prompts from the installation procedure.

See the RTR Software Product Description (SPD) for additional hardware requirements.

## 4.1.5 Check Required Software

RTR requires that the following Tru64 UNIX software subset be loaded on the system where you install RTR:

- OSFBASE---the Base System subset

One of the following is required:

- DECnet-Plus for Tru64 UNIX, for DECnet configurations
- TCP/IP as provided for Tru64 UNIX

The following Tru64 UNIX software subsets are optional on the system where you install RTR:

- OSFCLINET200---Basic Networking Services (TCP/IP) subset
- DNABASE110---DECnet/OSI Base Components subset, together with
- DNANETMAN110---DECnet/OSI Network Management subset

To check whether these subsets are loaded:

1. Log in to the system where you will install RTR.
2. Enter the following command:

       # setld -i | egrep 'OSFBASE|DNA'

If your path is not set as `/usr/sbin/` , you must enter the full path of the command. For example:

    % /usr/sbin/setld -i | egrep 'OSFBASE|DNA'

Check the displayed rows for the name of the relevant subset and any related patches. The word "installed" appears after the subset identifier when a subset is loaded. If the word "installed" does not appear (the second column in a row is blank), the subset or patch is not loaded. In this case, you must load the missing Tru64 UNIX software before installing RTR. (For information on how to load the operating system software, see the Guide to Installing Tru64 UNIX.)

## 4.1.6 Determine Which Subsets to Load

RTR has only one subset:

- rtrbase420
  RTR runtime and system management.

## 4.1.7 Check Required Disk Space

Table 4-1 lists the disk space requirements for loading the RTR software subset. These requirements apply to the disks where you load the RTR subset. The requirements are listed by directory for convenience if you are doing installations on systems where these directories are mount points for different disk partitions.

Table 4-1 RTR Subset Size (in Kilobytes) for Tru64 UNIX
Subset Title | Subset Name | /usr/opt/ | /rtr
--- | --- | --- | ---
RTR | rtrbase420 | 21000 | 5600
Total: |  | 26600 |

Using these disk space requirements, calculate the total values for the subsets you will load in each directory. You will also require at least 2MB disk space for the RTR journal, which defaults to `/rtrjnl` .

Compare the space required for the subset with the free space currently on the disks where RTR files will reside.

### 4.1.7.1 Check Current Disk Space

To check the current amount of free space for a directory path, log in to the system where you will install RTR. You can check which directories are mounted and where they are by viewing the `/etc/fstab` file. For example:

    # more /etc/fstab
    /dev/rd0a:/:rw:1:1:ufs::
    /dev/rd0g:/usr:rw:1:2:ufs::
    /usr/staff/r1/leslie@bigsys:/usr/staff/r1/leslie:rw:0:0:nfs:bg:
    /usr/man@bigsys:/usr/man:ro:0:0:nfs:bg:

The display indicates that `/usr` (mounted to `/dev/rd0g` ) is the only mount point that affects where RTR files will reside; the system has only one local disk drive, and the `/usr/lib` and file system resides in the `g` partition of the disk on that drive.

To check the total space and the free space for the directories where RTR will reside, enter the `df` command. Given the previous display of the `/etc/fstab` file, which shows that only `/usr` is a mount point, you need to check free space only in the `/usr` file system. For example:

    # df -k /usr
    Filesystem   1024-blocks    Used   Available  Capacity Mounted on
    /dev/rd0g         122598   54447       55892     49%   /usr

This display shows that there are 55,892 Kbytes (55 MB) free. This free space is sufficient to accommodate the subset requirements listed in Table 4-1, RTR Subset Size (in Kilobytes) for Tru64 UNIX.

On systems where `/usr/lib` and `/usr/man` are mounted to different devices from `/usr` , enter the following command:

    #  df /usr/lib /usr/man

In this case, you compare space required for RTR files in `/usr/lib` to the free space displayed in the first line of the `df` output list, and compare the space required for RTR files in `/usr/man` to the free space displayed in the second line of that list.

### 4.1.7.2 Increase Disk Space

The RTR installation procedure creates the following directory and loads files into subordinate directories:

    /usr/opt/RTR420

If the `/usr/opt/rtr420` directory in the previous path does not exist, the installation procedure creates it.

If the `rtr420` directory does exist, the installation procedure uses it.

If you find that there is insufficient disk space for the RTR subsets and you know that you have additional space on alternative disks or disk partitions for your system, perform the following steps before installing RTR:

1. Log in as superuser.
2. Create the directory `/usr/lib/rtr420` .
3. Specify in the `/etc/fstab` file that one or more of the newly created directories are mount points to new disk partitions where there is additional space.
4. Enter the `mount -a` command so that the new mount points take effect.

## 4.1.8 Check System Parameters

Installing RTR for Tru64 UNIX may mean that you have to increase the values for some system parameters.

### 4.1.8.1 Check Shared Memory Requirements

RTR has basic memory requirements. For information on how much shared memory to allocate, refer to the Reliable Transaction Router System Manager's Manual, RTR Shared Memory Sizing.

### 4.1.8.2 Check Virtual Memory Requirements

For information on how much virtual memory to allocate, refer to the Reliable Transaction Router System Manager's Manual, RTRACP Virtual Memory Sizing for All Systems.

### 4.1.8.3 TCP Services File

RTR uses TCP/IP port number 46000 for the network communication daemon `rtr rtrd` . On UNIX platforms, edit the `/etc/services` file to add the following line:

     rtracp 46000/tcp

This informs the system administrator that port number 46000/tcp is reserved for RTR. Note that the RTR daemon is started by the RTRACP, not by `inetd.`

## 4.1.9 Back Up Your System Disk

HP recommends that you back up your system disk before installing any software. For information about backing up your system disk, see the Tru64 UNIX system documentation.

# 4.2 Install RTR

Before you start the installation, read Section 4.1, Prepare for Installation to ensure that you are prepared to complete the installation.

You can install RTR locally (using CD-ROM media) or from a server area. If you encounter any failures during installation, see Appendix A.

## 4.2.1 Install from Media or RIS

Someone from your site must perform at least one RTR installation from the distribution medium. Your site system manager can then decide whether or not to make a RTR distribution kit available online so that subsequent installations of RTR can use the Remote Installation Service (RIS). For information on extracting RTR subsets to a RIS distribution area, see the Guide to Sharing Software on a Local Area Network.

If you expect to use RTR subsets from the RIS area of a remote system for installation on your local system, first check with your site system manager to ensure that:

- A RTR network kit is available for use.
- Your system is registered as a RIS client.

If RTR subsets are available to you on a RIS server system, you must know the name of that system.

For more information on installing RTR from a RIS distribution area, see Section 4.2.1.2.

Note on Cluster Installation To support TruCluster Server 5, the `/rtr` directory is now a symbolic link to a target directory, which is a context-dependent symbolic link (CDSL), so that it is a different physical directory on each cluster member. Before installing RTR on a TruCluster Server, you must first remove any existing `/rtr` directory or `/rtr` symbolic link, its target directory and the directory's contents on all member nodes. If you do not need the previous journal, HP recommends that you remove `/rtrjnl` and its contents; it will then be recreated as a symbolic link to a shared directory in `/var` , which usually has more space than the `/ filesystem` . Note that although the `/rtrjnl` directory can also be replaced by a symbolic link, the target should be an ordinary cluster-wide directory and not a member-specific CDSL so that each member can access the journal files belonging to the other members. Similarly, any other devices that you may specify when creating journals should normally also refer to cluster-wide shared directories. To create a subdirectory within a suitable existing member-specific directory using the following commands:
    # mkdir /var/run/rtr
    # cp -pr /rtr/* /var/run/rtr/
    # rm -fr /rtr
    # ln -s /var/run/rtr /rtr
The rtr directory still contains a mixture of temporary and permanent files, so whichever directory is chosen must not be cleared on reboot.

Previous | Next | Contents | Index