Compaq recommends that you back up your system disk before installing any software. For information about backing up your system disk, see the DEC OSF/1 AXP system documentation.

5.1.7 Stopping the Installation

To stop the installation procedure at any time, press Ctrl/C. You must then delete files created up to this point interactively. The directories and files created during the RTR installation are listed in the following file (on your :CD-ROM):

/RTR320/kit/instctrl/rtrbase320.inv

5.2 Installing RTR on Compaq Tru64 UNIX

Before you start the installation, read Section 5.1, Preparing forRTR Installation on Compaq Tru64 UNIX .

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

5.2.1 Distribution Media

You can obtain Reliable Transaction Router software on :CD-ROM or using RIS.

5.2.1.1 Using :CD-ROM Consolidated Distribution Media

This procedure loads RTR files on to a disk belonging to the system where you perform the installation. When RTR is run, its executable images are mapped into memory on your system.

Follow these steps to install RTR from :CD-ROM media:

1. Mount the media on the appropriate disk drive.
2. Log in as superuser (login name root ) to the system where you will install RTR.
3. Make sure you are at the root (/) directory by entering the following command:

   # cd /

4. Use the setld utility to check if you have a version of RTR already installed:

   # setld -i | grep RTR

5. If you have any previous version, make sure that it is not running:

   # rtr stop rtr # rtr disconnect server

6. De-install all previous versions that you find:

   # setld -d RTRBASE3xx

   
   Where "xx" is the version number.

7. Specify the /cdrom directory to be the mount point for the distribution file system on the drive. If your drive is rz0 , enter the following command:

   # mount -dr /dev/rz0c /cdrom

8. Enter a setld command that requests the load function ( -l ) and identifies the directory in the mounted file system where RTR subsets are located.
   For example, if the directory location for these subsets is /cdrom/axp/rtr314 , enter the following command:

   # setld -l /cdrom/AXP/RTR320

The installation procedure now displays the names of RTR subsets and asks you to specify the subsets you want to load.

See Section 5.2.2 to continue the installation.

5.2.1.2 Using a RIS Distribution Area

If you are installing RTR subsets that reside in an /etc/ris RIS distribution area on a remote system, follow these steps:

1. Log in as superuser (login name root ) to the system where you will install RTR.
2. Make sure you are at the root directory (/) by entering the following command:

   #cd /

3. Enter a setld command that requests the load function ( -l option) and identifies the system where the RTR subsets are located. For example, if you are loading RTR subsets from a RIS distribution area on node orion , enter the following:

   #setld -l orion:

Remote Installation Services now displays a menu that lists all the software subsets available to you and asks you to specify the subsets you want to load.

See Section 5.2.2 to continue the installation.

5.2.2 Responding to Installation Procedure Prompts

This section explains the installation procedure prompts and displays.

5.2.2.1 Selecting Subsets

You must specify which RTR subsets you want to load.

The subsets listed below are optional: There may be more optional subsets than can be presented on a single screen. If this is the case, you can choose subsets screen by screen or all at once on the last screen. All of the choices you make will be collected for your confirmation before any subsets are installed. 1) RTR API & Management Utility Or you may choose one of the following options: 2) ALL of the above 3) CANCEL selections and redisplay menus 4) EXIT without installing any subsets Enter your choices or press RETURN to redisplay menus. Choices (for example, 1 2 4-6):

If you specify more than one number at the prompt, separate each number with a space, not a comma.

Next, the script lets you verify your choice. For example, if you enter 1 in response to the previous prompt, you will see the following display:

You are installing the following optional subsets: RTR API & Management Utility Is this correct? (y/n):

If the displayed subsets are not the ones you intended to choose, enter n . In this case, the subset selection menu is again displayed and you can correct your choice of optional subsets.

If the displayed subsets are the ones you want to load, enter y .

5.2.2.2 Monitoring Displays During the Subset Loading Process

The installation procedure loads and verifies the selected RTR subset.

The following example shows a display where the RTR subset is being loaded from :CD-ROM:

Reliable Transaction Router V3.2 for Compaq Tru64 UNIX Installation started at Tue Jun 1 15:51:23 EDT 1999 Installation proceeds automatically, and will complete in approximately 1 minute. RTR API & Management Utility Copying from . (disk) Verifying 1 of 1 subset(s) installed successfully. Configuring "RTR API & Management Utility" (RTRBASE320) . . . Reliable Transaction Router V3.2 for Compaq Tru64 UNIX Installation completed at Tue Jun 1 15:51:23 EDT 1999

When you see the "Verifying" message during the subset installation, the installation procedure is checking to see that the files are copied correctly; it is not an Installation Verification Procedure (IVP) message.

During the installation, if you get errors from the setld utility, see the Diagnostics section of the setld(8) reference page for an explanation of the errors and the appropriate actions to take.

Section 5.3 explains how to run the IVP after installation, and how to delete old RTR subsets before installing a new version of RTR.

5.3 After Installation on Compaq Tru64 UNIX

This section explains what you need to do after the installation on Compaq Tru64 UNIX to make RTR ready for use.

5.3.1 Running the Installation Verification Procedure

After installing RTR, you can run the Installation Verification Procedure (IVP) independently to verify that the software is available on your system. You might also want to run the IVP after a system failure to be sure that users can access RTR.

Note that the Installation Verification Procedure (IVP) requires a working C language compiler to run.

The RTR IVP verifies the installation as follows:

• Starts RTR and creates a facility
• Creates an RTR journal
• Creates an RTR facility
• Stops RTR
• Compiles and links the example client and server programs

To run the IVP after an installation, enter the following command:

# setld -v RTRBASE320

For a sample RTR IVP, see Section 1.3.3.

If the verification process fails, look in the /var/adm/smlogs/fverify.log file for information to help diagnose the problem.

5.3.2 Deleting RTR from Your System

If you must remove a version of Reliable Transaction Router from your system, delete each subset that you previously installed.

To delete subsets:

1. Log in as superuser (login name root ).
2. Make sure you are at the root directory (/) by entering the following command:

   # cd /

3. Enter the following form of the setld command:

   # setld -i | grep RTRBASE

4. Look for the word "installed" in the listing produced, and then delete the installed subsets. For example:

   # setld -d RTRBASE320

The Reliable Transaction Router documentation is provided on the Compaq Tru64 UNIX Layered Products Online Documentation :CD-ROM in hypertext (.html) file format. You can display the hypertext files on your workstation using any HTML browser such as Netscape or Internet Explorer.

5.3.4 Enabling Remote RTR Commands

RTR supports the use of remote commands (described in Chapter 1 of the System Manager's Manual). To use this feature on Compaq Tru64 UNIX, check your operating system documentation for how to ensure access to a TCP/IP environment.

You may, for example, need to create an .rhosts file in the home directory of the RTR user on the target node or nodes, among other things. This file would contain the hostname (and, optionally, the username) of the node where the remote commands will be issued. For more information on the .rhosts file, see the rhosts(4) reference page.

5.4 Files Installed on Compaq Tru64 UNIX

This chapter lists the files, directories and symbolic links created by the installation on SunOS. The same files are installed on HP-UX, Compaq Tru64 UNIX, and AIX systems.

5.4.1 Symbolic Links Created

/usr/bin/rtr -> ../../usr/opt/RTR320/bin/rtr /usr/bin/rtr_remote -> ../../usr/opt/RTR320/bin/rtr_remote /usr/shlib/librtr.so -> ../../usr/opt/RTR320/shlib/librtr.so /usr/shlib/librtr_r.so -> ../../usr/opt/RTR320/shlib/librtr_r.so

5.4.2 Directories Created

/rtr

5.4.3 Files Created in /rtr

-rw-r--r-- 1 root system rtr.hlp -rw-r--r-- 1 root system accfail.mon -rw-r--r-- 1 root system acp2app.mon -rw-r--r-- 1 root system active.mon -rw-r--r-- 1 root system app2acp.mon -rw-r--r-- 1 root system broadcast.mon -rw-r--r-- 1 root system calls.mon -rw-r--r-- 1 root system channel.mon -rw-r--r-- 1 root system connects.mon -rw-r--r-- 1 root system ddtm.mon -rw-r--r-- 1 root system dtx.mon -rw-r--r-- 1 root system dtxrec.mon -rw-r--r-- 1 root system event.mon -rw-r--r-- 1 root system facility.mon -rw-r--r-- 1 root system flow.mon -rw-r--r-- 1 root system frontend.mon -rw-r--r-- 1 root system group.mon -rw-r--r-- 1 root system ipc.mon -rw-r--r-- 1 root system ipcrate.mon -rw-r--r-- 1 root system jcalls.mon -rw-r--r-- 1 root system journal.mon -rw-r--r-- 1 root system link.mon -rw-r--r-- 1 root system netbytes.mon -rw-r--r-- 1 root system netstat.mon -rw-r--r-- 1 root system partit.mon -rw-r--r-- 1 root system queues.mon -rw-r--r-- 1 root system quorum.mon -rw-r--r-- 1 root system rdm.mon -rw-r--r-- 1 root system recovery.mon -rw-r--r-- 1 root system rejects.mon -rw-r--r-- 1 root system rejhist.mon -rw-r--r-- 1 root system response.mon -rw-r--r-- 1 root system rfb.mon -rw-r--r-- 1 root system rolequor.mon -rw-r--r-- 1 root system routers.mon -rw-r--r-- 1 root system routing.mon -rw-r--r-- 1 root system rscbe.mon -rw-r--r-- 1 root system rtr.hlb -rw-r--r-- 1 root system rtr.mon -rw-r--r-- 1 root system stalls.mon -rw-r--r-- 1 root system system.mon -rw-r--r-- 1 root system tps.mon -rw-r--r-- 1 root system tpslo.mon -rw-r--r-- 1 root system traffic.mon -rw-r--r-- 1 root system trans.mon -rw-r--r-- 1 root system v2calls.mon -rw-r--r-- 1 root system xa.mon

5.4.4 Files Created in /usr/opt

/usr/opt/RTR320: drwxr-xr-x 2 bin bin bin drwxr-xr-x 3 bin bin examples drwxr-xr-x 2 bin bin hlp drwxr-xr-x 3 bin bin lib drwxr-xr-x 2 bin bin mon drwxr-xr-x 2 bin bin shlib /usr/opt/RTR320/bin: -rwsr-xr-x 1 root system rtr -rwxr-xr-x 1 bin bin rtr_remote -rwxr-xr-x 1 root system rtr_rqif -rwxr-xr-x 1 bin bin rtr_snapshot.sh /usr/opt/RTR320/examples: drwxrwxr-x 2 bin bin rtr /usr/opt/RTR320/examples/rtr: -rw-r--r-- 1 bin bin crtr.cxx -rw-r--r-- 1 bin bin crtr.hxx -rw-r--r-- 1 bin bin cslb.hxx -rw-r--r-- 1 bin bin example_cli.cxx -rw-r--r-- 1 bin bin example_cslb.hxx -rw-r--r-- 1 bin bin example_srv.cxx -rwxr-xr-x 1 bin bin rtr_ivp_osf.sh -rw-r--r-- 1 bin bin rtrreq.c -rw-r--r-- 1 bin bin rtrsrv.c /usr/opt/RTR320/hlp: -rw-r--r-- 1 bin bin copyright.txt -rw-r--r-- 1 bin bin license.txt -rw-r--r-- 1 bin bin rtr.hlb -rw-r--r-- 1 bin bin rtr.hlp /usr/opt/RTR320/lib: drwxrwxr-x 2 bin bin doclib -rw-r--r-- 1 bin bin rtr.h /usr/opt/RTR320/lib/doclib: total 0 /usr/opt/RTR320/mon: -rw-r--r-- 1 bin bin accfail.mon -rw-r--r-- 1 bin bin acp2app.mon -rw-r--r-- 1 bin bin active.mon -rw-r--r-- 1 bin bin app2acp.mon -rw-r--r-- 1 bin bin broadcast.mon -rw-r--r-- 1 bin bin calls.mon -rw-r--r-- 1 bin bin channel.mon -rw-r--r-- 1 bin bin connects.mon -rw-r--r-- 1 bin bin ddtm.mon -rw-r--r-- 1 bin bin dtx.mon -rw-r--r-- 1 bin bin dtxrec.mon -rw-r--r-- 1 bin bin event.mon -rw-r--r-- 1 bin bin facility.mon -rw-r--r-- 1 bin bin flow.mon -rw-r--r-- 1 bin bin frontend.mon -rw-r--r-- 1 bin bin group.mon -rw-r--r-- 1 bin bin ipc.mon -rw-r--r-- 1 bin bin ipcrate.mon -rw-r--r-- 1 bin bin jcalls.mon -rw-r--r-- 1 bin bin journal.mon -rw-r--r-- 1 bin bin link.mon -rw-r--r-- 1 bin bin netbytes.mon -rw-r--r-- 1 bin bin netstat.mon -rw-r--r-- 1 bin bin partit.mon -rw-r--r-- 1 bin bin queues.mon -rw-r--r-- 1 bin bin quorum.mon -rw-r--r-- 1 bin bin rdm.mon -rw-r--r-- 1 bin bin recovery.mon -rw-r--r-- 1 bin bin rejects.mon -rw-r--r-- 1 bin bin rejhist.mon -rw-r--r-- 1 bin bin response.mon -rw-r--r-- 1 bin bin rfb.mon -rw-r--r-- 1 bin bin rolequor.mon -rw-r--r-- 1 bin bin routers.mon -rw-r--r-- 1 bin bin routing.mon -rw-r--r-- 1 bin bin rscbe.mon -rw-r--r-- 1 bin bin rtr.mon -rw-r--r-- 1 bin bin stalls.mon -rw-r--r-- 1 bin bin system.mon -rw-r--r-- 1 bin bin tps.mon -rw-r--r-- 1 bin bin tpslo.mon -rw-r--r-- 1 bin bin traffic.mon -rw-r--r-- 1 bin bin trans.mon -rw-r--r-- 1 bin bin v2calls.mon -rw-r--r-- 1 bin bin xa.mon /usr/opt/RTR320/shlib: -rw-r-xr-x 1 bin bin 3563520 Nov 18 18:58 librtr.so -rw-r-xr-x 1 bin bin 3588096 Nov 18 18:52 librtr_r.so

This appendix provides information to help you deal with problems that might occur during product installation or product use.

If you find an error in the documentation, send an email message to the internet address on the last page of this appendix. Include the manual title, section and page numbers where the error occurred.

A.1 Problems During Product Installation

If errors occur during the installation, the system displays failure messages. For example, if the Compaq Tru64 UNIX installation fails due to insufficient disk space, the following message appears:

There is not enough space for subset RTRBASE320 Reliable Transaction Router for Compaq Tru64 UNIX (RTRBASE320) will not be loaded.

Errors can occur during the installation if any of the following conditions exist:

• The operating system version is incorrect.
• The prerequisite software version is incorrect.
• There is insufficient disk space.
• The system parameter values for successful installation are insufficient.

For descriptions of error messages generated by these conditions, see the operating system documentation on system messages, recovery procedures, and software installation. For information on system software requirements, see the software and disk space requirements for your operating system.

A.2 Problems After Installation

U.S. customers who encounter a problem while using Reliable Transaction Router can report it to Compaq by telephoning the Compaq Customer Support Center (CSC) at 1-800-354-9000. (Customers with service contracts can also use an electronic means such as DSNlink.)

Customers without a service contract can arrange for per-call support.

The CSC will need the following information:

• The name version number of the operating system you are using
• The Reliable Transaction Router version number you are using
• The hardware system you are using (such as a model number)
• A brief description of the problem (one sentence if possible)
• Whether or not the problem is critical
• Any other information that is helpful, such as the specific commands you used to run the software, the error messages displayed, and source listings of the relevant software module or lines of code

If the problem is related to Reliable Transaction Router documentation, send comments electronically to the following internet address:
rtrdoc@compaq.com.

If you are reporting a specific documentation error, be sure to include the manual title, section and page numbers where the error occurred.