The Installation Verification Procedure (IVP) requires a working C language compiler to run.

You may run the IVP separately from the installation procedure. If you are not using the C shell, start it by typing /usr/bin/csh and run the IVP by typing the following:-

# setenv BASEDIR /opt

and then executing the file
pkg/rtr/reloc/rtr/RTRxxx/examples/rtr/rtr_ivp_osf.sh .

1.4.3 Sample SunOS Installation

The following packages are available: 1 rtr Reliable Transaction Router (sun4u) 400 Select package(s) you wish to process (or all to process all packages). (default: all) [?,??,q]: all Processing package instance <rtr> from </usr/home/smith/kit> Reliable Transaction Router (sun4u) 400 Compaq Computer Corporation Using </opt> as the package base directory. ## Processing package information. ## Processing system information. ## Verifying disk space requirements. ## Checking for conflicts with packages already installed. ## Checking for setuid/setgid programs. This package contains scripts which will be executed with super-user permission during the process of installing this package. Do you want to continue with the installation of <rtr> [y,n,?] y Installing Reliable Transaction Router as <rtr> ## Installing part 1 of 1. /opt/rtr/RTR400/bin/rtr /opt/rtr/RTR400/bin/rtr_r /opt/rtr/RTR400/bin/rtr_remote /opt/rtr/RTR400/bin/rtr_rqif /opt/rtr/RTR400/bin/rtr_snapshot.sh /opt/rtr/RTR400/examples/ABCBook/ABCBook.cpp /opt/rtr/RTR400/examples/ABCBook/ABCBook.h /opt/rtr/RTR400/examples/ABCBook/ABCCHandlers.cpp /opt/rtr/RTR400/examples/ABCBook/ABCCHandlers.h /opt/rtr/RTR400/examples/ABCBook/ABCCommon.h /opt/rtr/RTR400/examples/ABCBook/ABCMagazine.cpp /opt/rtr/RTR400/examples/ABCBook/ABCMagazine.h /opt/rtr/RTR400/examples/ABCBook/ABCOrder.cpp /opt/rtr/RTR400/examples/ABCBook/ABCOrder.h /opt/rtr/RTR400/examples/ABCBook/ABCOrderProcessor.cpp /opt/rtr/RTR400/examples/ABCBook/ABCOrderProcessor.h /opt/rtr/RTR400/examples/ABCBook/ABCOrderTaker.cpp /opt/rtr/RTR400/examples/ABCBook/ABCOrderTaker.h /opt/rtr/RTR400/examples/ABCBook/ABCSClassFactory.cpp /opt/rtr/RTR400/examples/ABCBook/ABCSClassFactory.h /opt/rtr/RTR400/examples/ABCBook/ABCSHandlers.cpp /opt/rtr/RTR400/examples/ABCBook/ABCSHandlers.h /opt/rtr/RTR400/examples/ABCBook/SAMPLE1.COM /opt/rtr/RTR400/examples/ABCBook/Sample1.cpp /opt/rtr/RTR400/examples/ABCBook/Sample1.dsp /opt/rtr/RTR400/examples/ABCBook/Sample1.dsw /opt/rtr/RTR400/examples/ABCBook/Sample1.h /opt/rtr/RTR400/examples/ABCBook/Sample1.mk /opt/rtr/RTR400/examples/ABCBook/readme_abcbook.html /opt/rtr/RTR400/examples/rtr/rtr_ivp_osf.sh /opt/rtr/RTR400/examples/rtr/rtrreq.c /opt/rtr/RTR400/examples/rtr/rtrsrv.c /opt/rtr/RTR400/examples/rtradg/adg_client.c /opt/rtr/RTR400/examples/rtradg/adg_header.h /opt/rtr/RTR400/examples/rtradg/adg_server.c /opt/rtr/RTR400/examples/rtradg/adg_shared.c /opt/rtr/RTR400/hlp/copyright.txt /opt/rtr/RTR400/hlp/license.txt /opt/rtr/RTR400/hlp/rtr.hlb /opt/rtr/RTR400/hlp/rtr_relnotes.ps /opt/rtr/RTR400/hlp/rtr_relnotes.txt /opt/rtr/RTR400/lib/rtr.h /opt/rtr/RTR400/lib/rtr_v2.h /opt/rtr/RTR400/lib/rtrapi.h /opt/rtr/RTR400/mon/accfail.mon /opt/rtr/RTR400/mon/acp2app.mon /opt/rtr/RTR400/mon/active.mon /opt/rtr/RTR400/mon/app2acp.mon /opt/rtr/RTR400/mon/appdelay.mon /opt/rtr/RTR400/mon/broadcast.mon /opt/rtr/RTR400/mon/calls.mon /opt/rtr/RTR400/mon/channel.mon /opt/rtr/RTR400/mon/congest.mon /opt/rtr/RTR400/mon/connects.mon /opt/rtr/RTR400/mon/ctccalls.mon /opt/rtr/RTR400/mon/ddtm.mon /opt/rtr/RTR400/mon/downstream.mon /opt/rtr/RTR400/mon/dtx.mon /opt/rtr/RTR400/mon/dtxrec.mon /opt/rtr/RTR400/mon/event.mon /opt/rtr/RTR400/mon/facility.mon /opt/rtr/RTR400/mon/fastrecovery.mon /opt/rtr/RTR400/mon/flostalls.mon /opt/rtr/RTR400/mon/flow.mon /opt/rtr/RTR400/mon/frontend.mon /opt/rtr/RTR400/mon/group.mon /opt/rtr/RTR400/mon/ipc.mon /opt/rtr/RTR400/mon/ipcrate.mon /opt/rtr/RTR400/mon/jcalls.mon /opt/rtr/RTR400/mon/jnlhtml.mon /opt/rtr/RTR400/mon/journal.mon /opt/rtr/RTR400/mon/link.mon /opt/rtr/RTR400/mon/netbytes.mon /opt/rtr/RTR400/mon/netstat.mon /opt/rtr/RTR400/mon/ortr.mon /opt/rtr/RTR400/mon/partit.mon /opt/rtr/RTR400/mon/queues.mon /opt/rtr/RTR400/mon/quorum.mon /opt/rtr/RTR400/mon/rdm.mon /opt/rtr/RTR400/mon/recovery.mon /opt/rtr/RTR400/mon/rejects.mon /opt/rtr/RTR400/mon/rejhist.mon /opt/rtr/RTR400/mon/response.mon /opt/rtr/RTR400/mon/rfb.mon /opt/rtr/RTR400/mon/rolequor.mon /opt/rtr/RTR400/mon/routers.mon /opt/rtr/RTR400/mon/routing.mon /opt/rtr/RTR400/mon/rscbe.mon /opt/rtr/RTR400/mon/rtr.mon /opt/rtr/RTR400/mon/stalls.mon /opt/rtr/RTR400/mon/stccalls.mon /opt/rtr/RTR400/mon/system.mon /opt/rtr/RTR400/mon/tps.mon /opt/rtr/RTR400/mon/tpslo.mon /opt/rtr/RTR400/mon/traffic.mon /opt/rtr/RTR400/mon/trans.mon /opt/rtr/RTR400/mon/upstream.mon /opt/rtr/RTR400/mon/v2calls.mon /opt/rtr/RTR400/mon/xa.mon /opt/rtr/RTR400/shlib/librtr.so /opt/rtr/RTR400/shlib/librtr_r.so /opt/rtr/RTR400/shlib/librtrapicpp.so /opt/rtr/RTR400/shlib/librtrapicpp_r.so /opt/rtr/RTR400/wbi/graphics/blank.jpg /opt/rtr/RTR400/wbi/graphics/closedfolder.gif /opt/rtr/RTR400/wbi/graphics/doc.gif /opt/rtr/RTR400/wbi/graphics/lastnode.gif /opt/rtr/RTR400/wbi/graphics/link.gif /opt/rtr/RTR400/wbi/graphics/node.gif /opt/rtr/RTR400/wbi/graphics/openfolder.gif /opt/rtr/RTR400/wbi/graphics/vertline.gif /opt/rtr/RTR400/wbi/images/backend.gif /opt/rtr/RTR400/wbi/images/backgrndbur.gif /opt/rtr/RTR400/wbi/images/banner.gif /opt/rtr/RTR400/wbi/images/cmpnylogo.gif /opt/rtr/RTR400/wbi/images/configuration_example.gif /opt/rtr/RTR400/wbi/images/ext_configuration_example.gif /opt/rtr/RTR400/wbi/images/f-4orig.gif /opt/rtr/RTR400/wbi/images/f-6orig.gif /opt/rtr/RTR400/wbi/images/fail_backend.gif /opt/rtr/RTR400/wbi/images/fournode_shadow.gif /opt/rtr/RTR400/wbi/images/ie_animated.gif /opt/rtr/RTR400/wbi/images/newredbar.gif /opt/rtr/RTR400/wbi/images/noprog.gif /opt/rtr/RTR400/wbi/images/partition_states_shadow.gif /opt/rtr/RTR400/wbi/images/progress.gif /opt/rtr/RTR400/wbi/images/requester_states_shadow.gif /opt/rtr/RTR400/wbi/images/rtrscr.gif /opt/rtr/RTR400/wbi/images/rtrscrn.gif /opt/rtr/RTR400/wbi/images/security_html.gif /opt/rtr/RTR400/wbi/images/server_states_shadow.gif /opt/rtr/RTR400/wbi/images/zko-gs001-99ai.gif /opt/rtr/RTR400/wbi/images/zko-gs003-99ai.gif /opt/rtr/RTR400/wbi/images/zko-gs005-99ai.gif /opt/rtr/RTR400/wbi/images/zko-gs006-99ai.gif /opt/rtr/RTR400/wbi/images/zko-gs007-99ai.gif /opt/rtr/RTR400/wbi/images/zko-gs009-99ai.gif /opt/rtr/RTR400/wbi/images/zko-gs015-99ai.gif /opt/rtr/RTR400/wbi/rtr_accept_node.js /opt/rtr/RTR400/wbi/rtr_command_displ.js /opt/rtr/RTR400/wbi/rtr_command_form.js /opt/rtr/RTR400/wbi/rtr_create_fac.js /opt/rtr/RTR400/wbi/rtr_create_jou.js /opt/rtr/RTR400/wbi/rtr_create_par.js /opt/rtr/RTR400/wbi/rtr_create_tree.js /opt/rtr/RTR400/wbi/rtr_create_tree_sub.js /opt/rtr/RTR400/wbi/rtr_delete_fac.js /opt/rtr/RTR400/wbi/rtr_delete_par.js /opt/rtr/RTR400/wbi/rtr_extend_fac.js /opt/rtr/RTR400/wbi/rtr_left_frame.html /opt/rtr/RTR400/wbi/rtr_log_displ.js /opt/rtr/RTR400/wbi/rtr_main.html /opt/rtr/RTR400/wbi/rtr_modify_jou.js /opt/rtr/RTR400/wbi/rtr_monitor.js /opt/rtr/RTR400/wbi/rtr_set_btx.js /opt/rtr/RTR400/wbi/rtr_set_fac.js /opt/rtr/RTR400/wbi/rtr_set_lnk.js /opt/rtr/RTR400/wbi/rtr_set_log.js /opt/rtr/RTR400/wbi/rtr_set_par.js /opt/rtr/RTR400/wbi/rtr_trim_fac.js /opt/rtr/RTR400/wbi/smm.html /opt/rtr/RTR400/wbi/smm_contents.html /opt/rtr/RTR400/wbi/smm_contents_001.html /opt/rtr/RTR400/wbi/smm_contents_002.html /opt/rtr/RTR400/wbi/smm_index.html /opt/rtr/RTR400/wbi/smm_index_001.html [ verifying class <none> ] ## Executing postinstall script. # Copyright 1994 Compaq Computer Corporation. # # Confidential computer software. Valid license from Compaq required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendors standard commercial license. # # Compaq, the Compaq logo, and the Digital logo are registered in the U.S. Patent and Trademark Office. This kit will only run on Sun Solaris 2.5 and higher. Installation should complete in approximately 1 minute. Solaris 2.6 or higher: selecting multithreaded rtr to exploit aio Copyright 1994 Compaq Computer Corporation. Confidential computer software. Valid license from Compaq required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendors standard commercial license. Compaq, the Compaq logo, and the Digital logo are registered in the U.S. Patent and Trademark Office. Starting Reliable Transaction Router V4.0 for SunOS Installation Verification Procedure WARNING: This is not a first time install. WARNING: Please ensure that you have terminated *all* existing WARNING: rtr processes and rtr applications before continuing. Rtr will find and reuse any existing rtr journal files in the top level rtrjnl directory on each suitable filesystem, and will reuse any existing shared memory segment associated with /rtr/RTRENVPS Normally this is intended and should not cause any problems. WARNING: Any existing journal will be used and modified, otherwise WARNING: a new journal will be created on the default filesystem. WARNING: Facilities RTR_IVP_FACILITY and RTR will be created. WARNING: Result may be affected by size and contents of any existing journal. WARNING: The sample client and server do not necessarily complete if they WARNING: encounter previously journalled transactions for their facilities. NOTE: The following question is ignored in a non-interactive install NOTE:unless NONABI_SCRIPTS=TRUE, see man pkgadd for details... Would you like to abort the IVP? (y/n) IVP aborted Installation of <rtr> was successful. The following packages are available: 1 rtr Reliable Transaction Router (sun4u) 400 Select package(s) you wish to process (or all to process all packages). (default:all) script done on Wed Dec 13 16:43:06 2000 all packages). (default: all) [?,??,q]: q

To upgrade RTR, use the following process:

1. Shutdown RTR
2. Uninstall RTR
3. Install RTR
4. Run the IVP (optional)
5. Start RTR

Take note of the following restrictions if upgrading an RTR environment from RTR V3.2 to V4.0.

The RTR recovery protocol consists of messages sent from one backend, via a router, to the target backend. If either of the RTR backends is upgraded to RTR V4.0, then the router that will be used for recovery must also be running RTR V4.0. This generally means that any RTR router nodes should be upgraded to RTR V4.0 before any RTR backend nodes. There is no restriction in the order that RTR backends should be upgraded to V4.0.

The order in which RTR nodes should be upgraded for a rolling upgrade from V3.2 to V4.0 is as follows:

1. Frontend-only nodes can be upgraded at any time
2. Router-only and mixed frontend/router nodes
3. Mixed router/backend nodes
4. Router-only nodes
5. Backend-only nodes

For more complex configurations, where a node may have combinations of facilities with different backend/router groupings, use the command SET NODE/RECOVERY=V32 to set the recovery protocol to the V3.2 algorithm. Once RTR has been upgraded on all nodes, the recovery protocol can be reset to its default value (V4.0), and RTR restarted at a convenient time on each node. This need not be a simultaneous restart on all nodes. RTR can be restarted on each node one by one after resetting the default recovery protocol, so that continuous application availability is maintained.

2.2 Uninstalling RTR

Remove commands do not remove all RTR files from your disks. This is particularly important when you are upgrading from one version of RTR to another. You must eliminate all RTR files from your system, but must not discard any customized monitor files in /rtr or a journal containing recoverable transactions in /rtrjnl . Copy these to another directory before completing the uninstall instructions.

If /rtrjnl or /rtr is a symbolic link to another directory, first remove the target directory and all files contained in it, and then remove the symbolic link.

2.2.1 Uninstalling on OpenVMS

Complete the following steps to uninstall RTR from your system.

• Stop all RTR processes on the system:

  $ RTR STOP RTR $ RTR DISCONNECT SERVER

• Check for any surviving processes such as rtrd and applications programmed to handle RTR_STS_NOACP, and terminate any such processes until there are none left. Note that all the RTR ACP and comserver processes must be terminated before rtrd , otherwise they will create a new rtrd .
  The rtrd process can now be terminated with the STOP command or by issuing the following command:

  $ RTR DISC SERVER/DAEMON

• Terminate all application processes linked to RTR. If you are running in a cluster configuration, you must remove RTR application processes from all the cluster members that use the disk where RTR was installed.
  Processes can be terminated with the STOP command, or by a program that uses $FORCEX.
  To verify that no RTR-related processes are still running on a node or cluster member, use the SHOW DEVICE/FILES command to make sure that there are no remaining SYS$SHARE:LIBRTR*.EXE shareable images.
• Remove RTR from your system.

  $ PRODUCT REMOVE RTR

You must perform the following actions before uninstalling RTR on a Windows system:

• If RTR has previously been registered as a service, unregister RTR as a service. Do this with the following menu selections from the Program menu:
  Compaq -> RTR -> Unregister Service
• Delete all *.LCK files located in the directory used for the previous installation, and the RTRenvps file (shared memory).
• Stop all RTR processes on the system:

  RTR STOP RTR RTR DISCONNECT SERVER

  
  If you are uninstalling RTR Version 4.0, use the /DAEMON option:

  RTR DISCONNECT SERVER/DAEMON

  
  You can also use the Shutdown command, which executes Shutdown.bat .

  Programs-> Compaq -> RTR -> Shutdown

• Check for any surviving processes such as rtrd and applications programmed to handle RTR_STS_NOACP, and terminate any such processes until there are none left. Note that all the RTR ACP and comserver processes must be terminated before rtrd , otherwise they will create a new rtrd .
  The rtrd process can now be terminated with this command:

  $ RTR DISC SERVER/DAEMON

  
  To verify that no RTR-related processes are still running on a node or cluster member, check for the existence of the rtrdll.dll file. The rtrdll.dll file cannot be deleted if it is in use.

• To uninstall RTR, perform one of the following options:
  Programs -> Compaq -> RTR -> Uninstall
  or
  Control Panel -> Add/Remove Programs -> Reliable Transaction Router -> Add/Remove
• Terminate all application processes linked to RTR. If you are running in a cluster configuration, you must remove RTR application processes from all the cluster members that use the disk where RTR was installed.
• Remove previous versions of RTR from the disk:

  DEL /S/Q C:\RTR

Complete the following steps to uninstall RTR from your system.

• Stop all RTR processes on the system:

  # rtr stop rtr # rtr disconnect server

• Check for any surviving processes such as rtrd and applications programmed to handle RTR_STS_NOACP, and terminate any such processes until there are none left. Note that all the RTR ACP and comserver processes must be terminated before rtrd , otherwise they will create a new rtrd .
  The rtrd process can now be terminated with the KILL command or by issuing the following command:

  $ RTR DISC SERVER/DAEMON

  
  To verify that no RTR-related processes are still running on a node or cluster member, use the fuser or lsof command to make sure that the threaded or unthreaded librtr*.so shared libraries are not in use.

• Terminate all application processes linked to RTR. If you are running in a cluster configuration, you must remove RTR application processes from all the cluster members that use the disk where RTR was installed.
• Uninstall all previous versions that you find:

  # setld -d RTRBASE4xx

  
  where "xx" is the version number.

• Remove all RTR files with the following commands:

  Note The last directory is user configurable, so verify its location before executing the last command.

  rm -rf /rtr rm -rf /rtrjnl rm -rf /usr/opt/rtr

Complete the following steps to uninstall RTR from your system.

• Stop all RTR processes on the system:

  # rtr stop rtr # rtr disconnect server

• Check for any surviving processes such as rtrd and applications programmed to handle RTR_STS_NOACP, and terminate any such processes until there are none left. Note that all the RTR ACP and comserver processes must be terminated before rtrd , otherwise they will create a new rtrd .
  The rtrd process can now be terminated with the KILL command or by issuing the following command:

  $ RTR DISC SERVER/DAEMON

• Terminate all application processes linked to RTR. If you are running in a cluster configuration, you must remove RTR application processes from all the cluster members that use the disk where RTR was installed.
  To verify that no RTR-related processes are still running on a node or cluster member, use the fuser or lsof command to make sure that the threaded or unthreaded librtr*.so shared libraries are not in use.
• Uninstall all previous versions that you find:

  # pkgrm rtr

• Remove all RTR files with the following commands:

  Note The last directory is user configurable, so verify its location before executing the last command.

  rm -rf /rtr rm -rf /rtrjnl rm -rf /opt/rtr