Reliable_Transaction_Router Installation Guide Order Number: AA-Q88DE-TE This guide describes how to install Reliable Transaction Router for all operating systems on which RTR is supported. Revision/Update Information: This manual supersedes the Reliable Transaction Router Installation Guide for RTR Version 3.1D, and has been completely revised. Operating Systems: Windows NT Version 4.0 Windows 95 Windows 98 Compaq Tru64 UNIX Version 4.0D, 4.0E, 4.0F Sun Solaris Version 2.5, 2.6x IBM AIX Version 4.2 to 4.3.x Hewlett-Packard HP-UX Version 10.20 OpenVMS Version 6.2, 7.1, 7.2 Software Version: Reliable Transaction Router Version 3.2 Compaq Computer Corporation Houston, Texas ________________________________________________________________ June, 1999 COMPAQ COMPUTER CORPORATION SHALL NOT BE LIABLE FOR TECHNICAL OR EDITORIAL ERRORS OR OMISSIONS CONTAINED HEREIN, NOR FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES RESULTING FROM THE FURNISHING, PERFORMANCE, OR USE OF THIS MATERIAL. THIS INFORMATION IS PROVIDED "AS IS" AND COMPAQ COMPUTER CORPORATION DISCLAIMS ANY WARRANTIES, EXPRESS, IMPLIED OR STATUTORY AND EXPRESSLY DISCLAIMS THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR PARTICULAR PURPOSE, GOOD TITLE AND AGAINST INFRINGEMENT. This publication contains information protected by copyright. No part of this publication may be photocopied or reproduced in any form without prior written consent from Compaq Computer Corporation. © Digital Equipment Corporation 1999. All rights reserved. The software described in this guide is furnished under a license agreement or nondisclosue agreement. The software may be used or copied only in accordance with the terms of the agreement. Compaq and the Compaq logo are registered in the United States Patent and Trademark Office. The following are trademarks of Compaq Computer Corporation: AlphaGeneration, AlphaServer, AlphaStation, Compaq Internet Personal Tunnel, DEC, DECconnect, DECdtm, DECnet, DIGITAL, OpenVMS, PATHWORKS, POLYCENTER, Reliable Transaction Router, TruCluster, Tru64 UNIX, VAX, and VMScluster. The following are third-party trademarks: AIX and IBM are registered trademarks of International Business Machines Corporation. Encina is a registered trademark of Transarc Corporation. Hewlett-Packard and HP-UX are registered trademarks of Hewlett-Packard Company. InstallShield is a registered trademark of InstallShield Software Corporation. Intel is a trademark of Intel Corporation. Microsoft, Microsoft Access, Microsoft SQL Server, Internet Explorer, MS-DOS, Visual Basic, Visual C++, Windows, Windows 95, Windows 98, and Windows NT are trademarks or registered trademarks of Microsoft Corporation. Netscape, Netscape Communicator, and Netscape Navigator are registered trademarks of Netscape Communications Corporation. Oracle, ORACLE7, PL/SQL, SQL*Net, AND SQL*Plus are trademarks or registered trademarks of Oracle Corporation. Solaris, SPARCstation, SUN, SunOS, and Sunlink are trademarks or registered trademarks of Sun Microsystems, Inc. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company, Ltd. This document was prepared using VAX DOCUMENT Version 2.1. _________________________________________________________________ Contents Preface................................................... vii 1 Quick Installation 1.1 Installing RTR for OpenVMS.................... 1-1 1.1.1 Installation Procedure.................... 1-1 1.1.2 Sample OpenVMS Installation............... 1-2 1.1.3 Sample IVP Output......................... 1-4 1.2 Installing RTR for Windows NT, Windows 95, and Windows 98.................................... 1-5 1.2.1 Installation Procedure.................... 1-5 1.3 Installing RTR for Compaq Tru64 UNIX.......... 1-6 1.3.1 Installation Procedure.................... 1-6 1.3.2 Sample Compaq Tru64 UNIX Installation..... 1-7 1.3.3 Sample IVP Output......................... 1-9 1.4 Installing RTR for SunOS...................... 1-11 1.4.1 Installation Procedure.................... 1-11 1.4.2 Running the IVP........................... 1-12 1.4.3 Sample SunOS Installation................. 1-13 1.4.4 Sample IVP Output......................... 1-16 1.5 Installing RTR for AIX........................ 1-17 1.5.1 Installation Procedure.................... 1-18 1.5.2 Sample AIX Installation................... 1-19 1.5.3 Sample IVP Output......................... 1-24 1.6 Installing RTR for HP-UX...................... 1-26 1.6.1 Installation Procedure.................... 1-26 1.6.2 Running the IVP........................... 1-27 1.6.3 Sample IVP Output......................... 1-27 iii 2 Upgrade Process 2.1 Uninstalling RTR.............................. 2-1 2.1.1 Uninstalling on OpenVMS................... 2-1 2.1.2 Uninstalling on Windows NT, Windows 95, and Windows 98............................ 2-2 2.1.3 Uninstalling on Compaq Tru64 UNIX......... 2-2 2.1.4 Uninstalling on Sun....................... 2-3 2.1.5 Uninstalling on AIX....................... 2-3 2.1.6 Uninstalling on HP-UX..................... 2-3 3 Full Installation on OpenVMS 3.1 Preparing for Installation.................... 3-1 3.1.1 Prerequisite and Optional Software........ 3-1 3.1.2 Registering your Software License......... 3-2 3.1.3 Required Disk Space....................... 3-3 3.1.4 System Parameters......................... 3-3 3.2 Installation Procedure........................ 3-4 3.3 Running RTR and the IVP....................... 3-4 3.4 After Installing RTR ......................... 3-7 3.4.1 Accessing Release Notes................... 3-7 3.4.2 Editing System Files...................... 3-7 3.4.3 User Account Requirements................. 3-8 3.4.3.1 Quotas.................................. 3-8 3.4.3.2 Privileges.............................. 3-9 3.5 Files Installed on OpenVMS.................... 3-9 4 Full Installation on Windows NT 4.1 Installation Requirements..................... 4-1 4.1.1 Hardware Requirements..................... 4-1 4.1.2 Software Requirements..................... 4-2 4.1.3 Required Memory........................... 4-2 4.2 Installation Procedure........................ 4-2 4.3 After Installing.............................. 4-4 4.4 Files Installed on Microsoft Windows NT....... 4-5 iv 5 Full Installation on Compaq Tru64 UNIX 5.1 Preparing for RTR Installation on Compaq Tru64 UNIX ......................................... 5-1 5.1.1 Checking the Software Distribution Kit.... 5-1 5.1.2 Reading the Online Release Notes.......... 5-1 5.1.3 Registering Your Software License ........ 5-2 5.1.4 Checking Installation Requirements........ 5-3 5.1.4.1 Checking Login Privileges............... 5-3 5.1.4.2 Checking Hardware Requirements.......... 5-3 5.1.4.3 Checking Software Requirements.......... 5-3 5.1.4.4 Determining Which Subsets to Load....... 5-4 5.1.4.5 Determining Disk Space Requirements..... 5-4 5.1.4.5.1 Checking Current Disk Space............ 5-5 5.1.4.5.2 Increasing Disk Space by Using Alternative Disks ..................... 5-6 5.1.5 Installing from Media or Using RIS........ 5-6 5.1.6 Backing Up Your System Disk............... 5-7 5.1.7 Stopping the Installation................. 5-7 5.2 Installing RTR on Compaq Tru64 UNIX .......... 5-7 5.2.1 Distribution Media........................ 5-7 5.2.1.1 Using CD-ROM Consolidated Distribution Media................................... 5-7 5.2.1.2 Using a RIS Distribution Area .......... 5-9 5.2.2 Responding to Installation Procedure Prompts................................... 5-9 5.2.2.1 Selecting Subsets....................... 5-9 5.2.2.2 Monitoring Displays During the Subset Loading Process......................... 5-10 5.3 After Installation on Compaq Tru64 UNIX ...... 5-11 5.3.1 Running the Installation Verification Procedure ................................ 5-12 5.3.2 Deleting RTR from Your System............. 5-12 5.3.3 Displaying Documentation from CD-ROM...... 5-13 5.3.4 Enabling Remote RTR Commands.............. 5-13 5.4 Files Installed on Compaq Tru64 UNIX.......... 5-13 5.4.1 Symbolic Links Created.................... 5-13 5.4.2 Directories Created....................... 5-14 5.4.3 Files Created in /rtr .................... 5-14 5.4.4 Files Created in /usr/opt................. 5-15 v A Recovering from Errors A.1 Problems During Product Installation ......... A-1 A.2 Problems After Installation .................. A-2 B Using OOR B.1 Introduction to ODBC over RTR................. B-1 B.1.1 OOR Components............................ B-2 B.2 Installation Information...................... B-3 B.2.1 The OORO7 Server Installation Procedure... B-3 B.2.1.1 Before installing the OORO7 Server...... B-3 B.2.1.2 Installing the OORO7 Server............. B-3 B.2.2 OOR Client Installation................... B-4 B.2.2.1 Before Installing the OOR Client........ B-4 B.2.2.2 Installing The OOR Client............... B-4 B.2.2.3 Configuring The OOR Client.............. B-5 B.3 Starting and Configuring the OOR Server....... B-5 B.3.1 Starting the OOR Server................... B-5 B.4 Configuring OOR Clients....................... B-9 B.4.1 Contents of the ODBC.INI File............. B-10 B.4.2 Changing Global Options................... B-11 B.4.3 Optimizing OOR Performance and Memory Usage..................................... B-12 B.5 Using the ORACLE Database With OOR............ B-12 B.5.1 Defining ORACLE System ID Names........... B-12 B.5.2 No Server Available Behavior.............. B-13 B.5.3 Autocommit Behaviour...................... B-13 B.5.4 Values Returned by SqlGetInfo() .......... B-13 B.5.5 Using the Cursor Library.................. B-14 B.5.6 Setting Session Characteristics........... B-14 B.5.7 Using PL/SQL Procedures................... B-15 B.5.8 Changes and Corrections................... B-16 B.5.9 OOR Restrictions.......................... B-17 Tables 1 Conventions Used in this Guide ........... xi 3-1 Prerequisite and Optional Software........ 3-1 3-2 Disk Space Requirements................... 3-3 3-3 Minimum Required System Parameter Values.................................... 3-3 vi 3-4 User Account Quotas for Using Reliable Transaction Router........................ 3-8 5-1 RTR Subset Size (Kilobytes Required)...... 5-4 B-1 OORO7 Command Qualifiers.................. B-6 B-2 ODBC.INI Entries.......................... B-11 B-3 Values Returned by SqlGetInfo............. B-14 vii _________________________________________________________________ Preface This guide explains how to install Reliable Transaction Router (RTR) on supported platforms. If you are installing RTR on only one platform, you need only read the sections that apply to that platform. Keep this guide with your distribution kit. You may need it to install maintenance updates or to reinstall RTR for any other reason. Structure of this Document This guide contains the following chapters and appendixes: o Chapter 1 gives brief installation instructions for RTR on OpenVMS VAX, OpenVMS Alpha, Windows NT, Windows 95 (client only), Windows 98 (client only), Compaq Tru64 UNIX, SunOS, AIX and HP-UX. o Chapter 2 includes instructions on how to remove RTR from your system before doing an upgrade. o Chapter 3 describes a full installation for OpenVMS VAX and OpenVMS Alpha, including: - Preparing for installation - Installation procedure - Running RTR and the IVP - After Installing RTR - List of files installed during an OpenVMS installation vii o Chapter 4 describes a full installation for Windows NT, including: - Hardware and software requirements - Installation procedure - After Installing - List of files installed during a Windows NT installation o Chapter 5 describes a full installation for Compaq Tru64 UNIX, as an example of UNIX installation details, including: - Preparing for Installation - Installation procedure - After installation procedures, including the Installation Verification Procedure (IVP), how to remove RTR from your system, and description of the files you need to run RTR applications. - List of files installed during a UNIX installation o Appendix A contains information about recovering from errors. o Appendix B contains information about installing ODBC Associated Documents In addition to this guide, the RTR documentation set includes the following: o Reliable Transaction Router System Manager's Manual o Reliable Transaction Router Application Programmer's Reference Manual o Reliable Transaction RouterApplication Design Guide o Reliable Transaction Router Migration Guide o A letter titled Reliable Transaction Router - Cover Letter viii o Reliable Transaction Router Release Notes are provided in electronic form in the software kit in the files RELNOTES.PS and RELNOTES.TXT. You are strongly advised to read the Release Notes before using the product. o All product documentation is also provided in HTML format on the online documentation CD-ROM. You can use any browser such as Netscape Navigator, Netscape Communicator, or Microsoft Internet Explorer to access the online form of the documentation. o This installation guide is also available on the software kit as INS.PS and INS.TXT. ix Conventions Table 1 describes the conventions used in this guide. x Table_1_Conventions_Used_in_this_Guide_____________________ Convention_____Meaning_____________________________________ # A number sign (#) is the default superuser prompt. % A percent sign (%) is the default user prompt for many UNIX systems. $ A dollar sign ($) is the default user prompt for OpenVMS systems. In examples, a boxed symbol indicates that you must press the named key on the keyboard. Ctrl/C This symbol indicates that you must press the Ctrl key while you simultaneously press another key (in this case, C). user input In interactive examples, this typeface indicates input entered by the user. filesystem In text, this typeface indicates the exact name of a command, routine, partition, pathname, directory, or file. This typeface is also used in interactive examples and other screen displays. UPPERCASE The UNIX operating system differentiates lowercase between lowercase and uppercase characters. Examples, syntax descriptions, function definitions, and literal strings that appear in text must be typed exactly as shown. Commands typed to the RTR CLI are not case sensitive unless enclosed in quotation marks. setld(8) Cross-references to online reference pages include the appropriate section number in parentheses. For example, setld(8) indicates that you can find the material on the setld command in Section 8 of the reference pages (UNIX systems only). [y] In a prompt, square brackets indicate that the enclosed item is the default response. For example, [y] means the default response _______________is_Yes._____________________________________ xi 1 _________________________________________________________________ Quick Installation This chapter gives brief instructions for installing Reliable Transaction Router on the following platforms: o OpenVMS o Windows NT o Windows 95 o Windows 98 o Compaq Tru64 UNIX (formerly known as DIGITAL UNIX) o Sun Solaris o IBM AIX o HP-UX 1.1 Installing RTR for OpenVMS The installation of the RTR base product requires about 50000 blocks during installation, and about 36000 blocks after installation is done. The installation takes less than five minutes to complete. For more detailed instructions, see Chapter 3, Full Installation on OpenVMS . 1.1.1 Installation Procedure 1. Log on to the System Manager's account. 2. Define the logical name for the location of the software kit, for example: $ DEFINE PCSI$SOURCE DISK1:[KITS] 3. Register your software license. 4. Check disk space and system parameters GBLPAGES and GBLSECTIONS. Quick Installation 1-1 Quick Installation 1.1 Installing RTR for OpenVMS 5. Determine if you need to install ODBC Over RTR Oracle7 Server. 6. Stop all RTR processes on the system: $ RTR STOP RTR $ RTR DISCONNECT SERVER 7. Start the installation with the following command: $ PRODUCT INSTALL RTR 1.1.2 Sample OpenVMS Installation $ product install rtr/help 1 - DEC VAXVMS RTR V3.2-xxx Layered Product 2 - Exit Choose one or more items from the menu separated by commas: 1 The following product has been selected: DEC VAXVMS RTR V3.2-xxx Layered Product Do you want to continue? [YES] Configuration phase starting ... You will be asked to choose options, if any, for each selected product and for any products that may be installed to satisfy software dependency requirements. DEC VAXVMS RTR V3.2-xxx: Reliable Transaction Router for OpenVMS Software fault tolerant middleware for high performance distributed transaction processing. Also available for, and interoperable with the following platforms: o Compaq Tru64 UNIX o Windows NT o Solaris o AIX o with others in preparation Copyright Digital Equipment Corporation. 1994, 1999. All rights reserved. © 1994, 1999 Digital Equipment Corporation. All rights reserved. 1-2 Quick Installation Quick Installation 1.1 Installing RTR for OpenVMS Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Compaq Computer Corporation and Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Compaq or an authorized sublicensor. Compaq, the Compaq logo, and the Digital logo are registered in the U.S. Patent and Trademark Office. This product uses the PAKs RTR-CL and RTR-SVR. This software is furnished under the licensing provisions of Compaq Computer Corporation's Standard Terms and Conditions. For more in- formation about Compaq's licensing terms and policies, contact your local Compaq office. This product requires one of the following PAKS: RTR-CL - enables front end functionality RTR-SVR - additionally enables RTR router and back end roles. Do you want the defaults for all options? [YES] no Please delete all RTRACP*, RTRCSV* and RTRD processes, as well as any user processes showing the "RTR>" prompt. Have all RTR processes on the system been stopped? [YES] This option installs the Oracle7 server for use with ODBC Over RTR. If this server is installed, client software that uses the OOR (ODBC Over RTR) ODBC driver can access an Oracle7 database using RTR as the transport. Installing this option requires that Oracle7 is installed on the system. ODBC Over RTR Oracle7 Server [NO] Before running the IVP on a production system, first shut down all RTR applications and stop RTR on all nodes booting from this system disk. Run installation verification procedure [NO] yes Quick Installation 1-3 Quick Installation 1.1 Installing RTR for OpenVMS Please see your Compaq Representative about obtaining the ECO 5 patch to DECNet/OSI V6.3. Failure to do so may result in run-time problems with erroneous link shutdowns. If you plan to use only TCP as a transport or are installing RTR in a test environment, you can safely proceed with the intallation. DECnet Phase IV users can also ignore this warning. DECnet users:Have you read the Release Note regarding minimum version? [YES] Do you want to review the options? [NO] Execution phase starting ... The following product will be installed to destination: DEC VAXVMS RTR V3.2-xxx DISK$OVMSVAXSYS:[VMS$COMMON.] Portion done: 0%...10%...20%...30%...50%...60%...70%...80%...90%...100% The following product has been installed: DEC VAXVMS RTR V3.2-xxx Layered Product %PCSI-I-IVPEXECUTE, executing test procedure for DEC VAXVMS RTR V3.2-xxx ... %PCSI-I-PRCOUTPUT, output from subprocess follows ... %PCSI-I-IVPSUCCESS, test procedure completed successfully DEC VAXVMS RTR V3.2-xxx: Reliable Transaction Router for OpenVMS Insert the following lines in SYS$MANAGER:SYSTARTUP_VMS.COM: @sys$startup:rtr$startup.com Insert the following lines in SYS$MANAGER:SYSHUTDWN.COM: @sys$manager:rtr$shutdown 1.1.3 Sample IVP Output %PCSI-I-IVPEXECUTE, executing test procedure for DEC VAXVMS RTR V3.2-xxx ... %PCSI-I-PRCOUTPUT, output from subprocess follows ... %PCSI-I-IVPSUCCESS, test procedure completed successfully DEC VAXVMS RTR V3.2-xxx: Reliable Transaction Router for OpenVMS Insert the following lines in SYS$MANAGER:SYSTARTUP_VMS.COM: @sys$startup:rtr$startup.com Insert the following lines in SYS$MANAGER:SYSHUTDWN.COM: @sys$manager:rtr$shutdown For additional information, see Chapter 3. 1-4 Quick Installation Quick Installation 1.2 Installing RTR for Windows NT, Windows 95, and Windows 98 1.2 Installing RTR for Windows NT, Windows 95, and Windows 98 Your Reliable Transaction Router for Windows NT, Windows 95, or Windows 98 kit is supplied on CD-ROM. The Release Notes are also on the CD-ROM; you are advised to read the Release Notes before using RTR. The installation of the RTR base product requires about five megabytes of disk space. The installation procedure takes about two minutes to complete. 1.2.1 Installation Procedure 1. If you are installing on Windows NT, log in as the Administrator, or with administrator privileges. 2. If you have a version of RTR already installed, you must: o Stop all RTR processes: RTR STOP RTR RTR DISCONNECT SERVER/DAEMON o Delete the file RTRENVPS in the RTR root directory. o Logout and login again. o Eradicate RTR V3.1D from the disk: DELETE /S/Q C:\RTR o Delete existing icon 3. Insert the RTR CD-ROM into the drive. 4. From Windows Explorer, choose the drive letter of your CD-ROM and open the directory ALPHA or I386, depending on your processor type. 5. Double click on SETUP.EXE to start the InstallShield[[R]] that takes you through the setup process. Quick Installation 1-5 Quick Installation 1.3 Installing RTR for Compaq Tru64 UNIX 1.3 Installing RTR for Compaq Tru64 UNIX Your Reliable Transaction Router for Compaq Tru64 UNIX kit is supplied on CD-ROM. The Release Notes are also on the CD-ROM; you are advised to read the Release Notes before using RTR. The installation requires about 60KB on the partition given in response to the RTRbase directory prompt. The installation procedure takes about two minutes to complete. 1.3.1 Installation Procedure 1. Login as user root or su to root. 2. Use the setld utility to check if you have a version of RTR already installed: # setld -i | grep RTR 3. If you have any previous version, make sure that it is not running: # rtr stop rtr # rtr disconnect server 4. De-install all previous versions that you find: # setld -d RTRBASE3xx Where "xx" is the version number. 5. Install from the directory (disk or CD-ROM) where the kit is located, for example: # setld -l /cdrom/rtr3xx/kit Where "xx" is the version number. 6. Answer "1" and "y" to the questions from setld. 7. To run the IVP (Installation Verification Procedure) use the following command: ________________________ Note ________________________ Do not run the IVP program on a production system, as it may alter the RTR journal or interrupt processing of transactions. You will be prompted to abort the IVP 1-6 Quick Installation Quick Installation 1.3 Installing RTR for Compaq Tru64 UNIX before it can do any damage. Consider your situation carefully before running the IVP. ______________________________________________________ # setld -v RTRBASE3xx Where "xx" is the version number. Note that the Installation Verification Procedure requires a working C language compiler to run. 1.3.2 Sample Compaq Tru64 UNIX Installation # setld -l . Copyright 1994, 1999 Digital Equipment Corporation. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227- 19, or in FAR 52.227-14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Compaq Computer Corporation and Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Compaq or an authorized sublicensor. Compaq, the Compaq logo, and the Digital logo are registered in the U.S. Patent and Trademark Office. 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. Quick Installation 1-7 Quick Installation 1.3 Installing RTR for Compaq Tru64 UNIX Choices (for example, 1 2 4-6):1 You are installing the following optional subsets: RTR API & Management Utility Is this correct? (y/n): y Checking file system space required to install selected subsets: File system space checked OK. 1 subset(s) will be installed. Loading 1 of 1 subset(s).... Reliable Transaction Router V3.2 for Compaq Tru64 UNIX Installation started at Tue Jun 1 15:51:23 EDT 1999. Installation proceeds automatically, and should 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) reusing existing /rtr directory # Copyright 1994, 1999 Digital Equipment Corporation. # # Restricted Rights: Use, duplication, or disclosure by the U.S. Government # is subject to restrictions as set forth in subparagraph (c) (1) (ii) of # DFARS 252.227-7013, or in FAR 52.227- 19, or in FAR 52.227-14 Alt. III, as # applicable. # # This software is proprietary to and embodies the confidential technology # of Compaq Computer Corporation and Digital Equipment Corporation. # Possession, use, or copying of this software and media is authorized # only pursuant to a valid written license from Compaq or an # authorized sublicensor. # # Compaq, the Compaq logo, and the Digital logo are registered in the # U.S. Patent and Trademark Office. 1-8 Quick Installation Quick Installation 1.3 Installing RTR for Compaq Tru64 UNIX Reliable Transaction Router V3.2 for Compaq Tru64 UNIX Installation completed at Tue Jun 1 15:51:37 EDT 1999. You can run the Installation Verification Procedure using this command: setld -v RTRBASE320 1.3.3 Sample IVP Output # setld -v RTRBASE320 RTR API & Management Utility (RTRBASE320) Copyright 1994, 1999 Digital Equipment Corporation. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227- 19, or in FAR 52.227-14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Compaq Computer Corporation and Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Compaq or an authorized sublicensor. Compaq, the Compaq logo, and the Digital logo are registered in the U.S. Patent and Trademark Office. Starting Reliable Transaction Router V3.2 for Compaq Tru64 UNIX 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_ Quick Installation 1-9 Quick Installation 1.3 Installing RTR for Compaq Tru64 UNIX 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. Would you like to abort the IVP? (y/n) n IVP continuing ... keeping any existing log file settings (RTR_DBG not set) starting RTR . . . creating a journal, if not already created . . . creating test facility . . . stopping RTR. [OPTIONAL] attempting to compile and link rtr test applications . . . If this system is not configured with an application development environment, or the platform does not support threads, then some messages about application compilation not succeeding are normal. multithreaded server rtr application compiled single-threaded client rtr application compiled applications rtrreq and rtrsrv available starting rtr and creating default facility %RTR-S-RTRSTART, RTR started on node sarand.zko.dec.com %RTR-S-FACCREATED, facility RTR$DEFAULT_FACILITY created starting an rtr server application running an rtr client application, should complete in a few seconds stopping rtr %RTR-S-RTRSTOP, RTR stopped on node sarand.zko.dec.com Copyright 1994, 1999 Digital Equipment Corporation. All rights reserved. Reliable Transaction Router V3.2 for Compaq Tru64 UNIX Installation Verification Procedure successful 1-10 Quick Installation Quick Installation 1.4 Installing RTR for SunOS 1.4 Installing RTR for SunOS Your Reliable Transaction Router for SunOS kit is supplied on CD-ROM. The Release Notes are also on the CD-ROM; you are advised to read the Release Notes before using RTR. The installation requires about 2950 KB on the partition given in response to the package base directory prompt (usually /opt). The installation procedure takes about two minutes to complete. Note that the Installation Verification Procedure (IVP) requires a working C language compiler to run. 1.4.1 Installation Procedure o There are both an rtr and rtr_r (the latter is installed only on SunOS 5.6/Solaris 2.6 systems); a soft link is established to the proper one from /usr/bin/rtr. o The sample C++ application files have been added to the examples/rtr directory where formerly only rtrsrv.c and rtrreq.c resided. o Both librtr_r.so and librtr.so are provided for both SunOS 5.5 and 5.6, in case there is a need to link your application with the threaded version, but only on SunOS 5.6 will RTR itself use librtr_r.so, thus enabling asynchronous I/O (aio) support. 1. Login as user root or su to root. 2. First check whether RTR is already installed, stop, and disconnect rtr: # pkginfo -l rtr # rtr stop rtr # rtr disconnect server 3. If it is, deinstall using the following command. # pkgrm rtr 4. Insert the CD-ROM and mount the volume at a convenient mount point (for example, /cdrom). Quick Installation 1-11 Quick Installation 1.4 Installing RTR for SunOS 5. Install RTR from the CD-ROM directory where the kit is located, for example: # cd /cdrom/rtr_kit # pkgadd -d . o You can accept the defaults for most questions from the pkgadd utility. o When asked for the "base directory", answer /opt. o Ignore any warning about free blocks and answer "y" to the attached continue question. o When asked "Do you want to install these as setuid /setgid files [y,n,?,q]", answer "y". o When asked "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 [y,n,?]", answer "y". 6. RTR is now installed in /opt/rtr. Section 1.4.3 shows an example installation of RTR for the SunOS. 1.4.2 Running the IVP The Installation Verification Procedure (IVP) requires a working C language compiler to run. ________________________ Note ________________________ Do not run the IVP program on a production system, as it may alter the RTR journal or interrupt processing of transactions. You will be prompted to abort the IVP before it can do any damage. Consider your situation carefully before running the IVP. ______________________________________________________ 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 1-12 Quick Installation Quick Installation 1.4 Installing RTR for SunOS and then executing the file pkg/rtr/reloc/rtr/RTRxxx /examples/rtr/rtr_ivp_osf.sh. 1.4.3 Sample SunOS Installation sunbox# pkgadd -d . The following packages are available: 1 rtr Reliable Transaction Router (sun4u) 320 Select package(s) you wish to process (or 'all' to process all packages). (default: all) [?,??,q]: 1 Processing package instance from Reliable Transaction Router (sun4u) 320 COMPAQ Enter path to package base directory [?,q] /opt Using as the package base directory. ## Processing package information. ## Processing system information. 1 package pathname is already properly installed. ## 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 [y,n,?] Do you want to continue with the installation of [y,n,?] y Installing Reliable Transaction Router as Quick Installation 1-13 Quick Installation 1.4 Installing RTR for SunOS ## Installing part 1 of 1. /opt/rtr/RTR320/bin/rtr /opt/rtr/RTR320/bin/rtr_r /opt/rtr/RTR320/bin/rtr_remote /opt/rtr/RTR320/bin/rtr_rqif /opt/rtr/RTR320/bin/rtr_snapshot.sh /opt/rtr/RTR320/examples/rtr/crtr.cxx /opt/rtr/RTR320/examples/rtr/crtr.hxx /opt/rtr/RTR320/examples/rtr/cslb.hxx /opt/rtr/RTR320/examples/rtr/example_cli.cxx /opt/rtr/RTR320/examples/rtr/example_cslb.hxx /opt/rtr/RTR320/examples/rtr/example_srv.cxx /opt/rtr/RTR320/examples/rtr/rtr_ivp_osf.sh /opt/rtr/RTR320/examples/rtr/rtrreq.c /opt/rtr/RTR320/examples/rtr/rtrsrv.c /opt/rtr/RTR320/hlp/copyright.txt /opt/rtr/RTR320/hlp/license.txt /opt/rtr/RTR320/hlp/rtr.hlb /opt/rtr/RTR320/hlp/rtr.hlp /opt/rtr/RTR320/lib/rtr.h /opt/rtr/RTR320/mon/accfail.mon /opt/rtr/RTR320/mon/acp2app.mon /opt/rtr/RTR320/mon/active.mon /opt/rtr/RTR320/mon/app2acp.mon /opt/rtr/RTR320/mon/broadcast.mon /opt/rtr/RTR320/mon/calls.mon /opt/rtr/RTR320/mon/channel.mon /opt/rtr/RTR320/mon/connects.mon /opt/rtr/RTR320/mon/ddtm.mon /opt/rtr/RTR320/mon/dtx.mon /opt/rtr/RTR320/mon/dtxrec.mon /opt/rtr/RTR320/mon/event.mon /opt/rtr/RTR320/mon/facility.mon /opt/rtr/RTR320/mon/flow.mon /opt/rtr/RTR320/mon/frontend.mon /opt/rtr/RTR320/mon/group.mon /opt/rtr/RTR320/mon/ipc.mon /opt/rtr/RTR320/mon/ipcrate.mon /opt/rtr/RTR320/mon/jcalls.mon /opt/rtr/RTR320/mon/journal.mon /opt/rtr/RTR320/mon/link.mon /opt/rtr/RTR320/mon/netbytes.mon /opt/rtr/RTR320/mon/netstat.mon 1-14 Quick Installation Quick Installation 1.4 Installing RTR for SunOS /opt/rtr/RTR320/mon/partit.mon /opt/rtr/RTR320/mon/queues.mon /opt/rtr/RTR320/mon/quorum.mon /opt/rtr/RTR320/mon/rdm.mon /opt/rtr/RTR320/mon/recovery.mon /opt/rtr/RTR320/mon/rejects.mon /opt/rtr/RTR320/mon/rejhist.mon /opt/rtr/RTR320/mon/response.mon /opt/rtr/RTR320/mon/rfb.mon /opt/rtr/RTR320/mon/rolequor.mon /opt/rtr/RTR320/mon/routers.mon /opt/rtr/RTR320/mon/routing.mon /opt/rtr/RTR320/mon/rscbe.mon /opt/rtr/RTR320/mon/rtr.mon /opt/rtr/RTR320/mon/stalls.mon /opt/rtr/RTR320/mon/system.mon /opt/rtr/RTR320/mon/tps.mon /opt/rtr/RTR320/mon/tpslo.mon /opt/rtr/RTR320/mon/traffic.mon /opt/rtr/RTR320/mon/trans.mon /opt/rtr/RTR320/mon/v2calls.mon /opt/rtr/RTR320/mon/xa.mon /opt/rtr/RTR320/shlib/librtr.so /opt/rtr/RTR320/shlib/librtr_r.so [ verifying class ] ## Executing postinstall script. # Copyright 1994, 1999 Digital Equipment Corporation. # # Restricted Rights: Use, duplication, or disclosure by the U.S. Government # is subject to restrictions as set forth in subparagraph (c) (1) (ii) of # DFARS 252.227-7013, or in FAR 52.227- 19, or in FAR 52.227-14 Alt. III, as # applicable. # # This software is proprietary to and embodies the confidential technology # of Compaq Computer Corporation and Digital Equipment Corporation. # Possession, use, or copying of this software and media is authorized # only pursuant to a valid written license from Compaq or an # authorized sublicensor. # # Compaq, the Compaq logo, and the Digital logo are registered in the # U.S. Patent and Trademark Office. Quick Installation 1-15 Quick Installation 1.4 Installing RTR for SunOS This kit will only run on Sun Solaris 2.5 and higher. Installation should complete in approximately 1 minute. 1.4.4 Sample IVP Output Copyright 1994, 1999 Digital Equipment Corporation. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227- 19, or in FAR 52.227-14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Compaq Computer Corporation and Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Compaq or an authorized sublicensor. Compaq, the Compaq logo, and the Digital logo are registered in the U.S. Patent and Trademark Office. Starting Reliable Transaction Router V3.2 for SunOS Installation Verification Procedure IVP: This is not a clean start: IVP: Result may be affected by previous settings in shared memory. IVP: Result may be affected by existing processes. IVP: Result may be affected by locks held by existing processes. IVP: Existing pipe files will normally be recycled correctly. IVP: Any existing journal will be used and modified. IVP: Facilities RTR_IVP_FACILITY and RTR will be created. IVP: Result may be affected by size and contents of any existing journal. IVP: The sample client and server do not necessarily complete IVP: if they encounter previously journalled transactions. IVP: The following question is ignored in a non- interactive install IVP: unless NONABI_ SCRIPTS=TRUE, see man pkgadd for details... IVP: Would you like to abort the IVP? (y/n) n 1-16 Quick Installation Quick Installation 1.4 Installing RTR for SunOS keeping any existing log file settings (RTR_DBG not set) starting RTR . . . creating a journal, if not already created . . . creating test facility . . . stopping RTR. [OPTIONAL] attempting to compile and link rtr test applications . . . If this system is not configured with an application development environment, or the platform does not support threads, then some messages about application compilation not succeeding are normal. multithreaded server rtr application compiled single-threaded client rtr application compiled applications rtrreq and rtrsrv available starting rtr and creating default facility %RTR-S-RTRSTART, RTR started on node sunbox %RTR-S-FACCREATED, facility RTR$DEFAULT_FACILITY created starting an rtr server application running an rtr client application, should complete in a few seconds stopping rtr %RTR-S-RTRSTOP, RTR stopped on node sunbox © 1999 Compaq Computer Corporation and Digital Equipment Corporation. All rights reserved. Reliable Transaction Router V3.2 for SunOS Installation Verification Procedure successful 1.5 Installing RTR for AIX Your Reliable Transaction Router for AIX kit is supplied on CD-ROM. The Release Notes are also on the CD-ROM; you are advised to read the Release Notes before using RTR. The installation requires about 3000KB free disk space. The installation procedure takes about two minutes to complete. ________________________ Note ________________________ Running RTR on AIX requires that asynchronous I/O (aio) is available. If aio is not available, the following messages appear: Quick Installation 1-17 Quick Installation 1.5 Installing RTR for AIX 0509-037 System error - error data is: rtr 0509-023 Symbol kaio_rdwr in /usr/lib/libc_r.a is not defined. 0509-023 Symbol listio in /usr/lib/libc_r.a is not defined. 0509-023 Symbol acancel in /usr/lib/libc_r.a is not defined. 0509-023 Symbol iosuspend in /usr/lib/libc_r.a is not defined. 0509-022 Cannot load library librtr_r.a. 0509-026 System error: Cannot run a file that does not have a valid form To check for aio, issue the following command: $ lsdev -C | grep aio aio0 Defined Asynchronous I/O To configure aio, use one of the following methods: # smit aio Configure defined aio ... mkdev -l aio0 # lsdev -C | grep aio aio0 Available Asynchronous I/O or # mkdev -1 aio0 # chdev -1 aio0 -P -a autoconfig # lsattr -El aio0 -a autoconfig ______________________________________________________ 1.5.1 Installation Procedure 1. If you have any previous version of RTR, make sure that it is not running:- # rtr stop rtr # rtr disconnect server 2. Become root and invoke the SMIT system management interface tool. You can either type the command smit and navigate through the menus, or type the command with a parameter to start SMIT at a particular menu. 3. Type smit install_remove or navigate to Remove Software Product and select any previously installed versions of RTR; then remove them. (Check that the "Preview 1-18 Quick Installation Quick Installation 1.5 Installing RTR for AIX Only" field is set to "No" otherwise the remove does not execute.) 4. Type smit install_latest or navigate to Install New Software at Latest Level and then select the source media (i.e. the CD-ROM) from the list. Select RTR. After entering OK to the prompts, installation proceeds automatically. If successful, the output looks similar to that shown in Section 1.5.2. 1.5.2 Sample AIX Installation +---------------------------------------------------------- -------------------+ Pre-installation Verification... +---------------------------------------------------------- -------------------+ Verifying selections...done Verifying requisites...done Results... SUCCESSES --------- Filesets listed in this section passed pre- installation verification and will be installed. -- Filesets are listed in the order in which they will be installed. -- The reason for installing each fileset is indicated with a keyword in parentheses and explained by a "Success Key" following this list. RTR320.rte x.xx.xxx.x (Selected) Reliable Transaction Router Success Key: Selected -- Explicitly selected by user for installation. Maintenance -- Maintenance Level fileset update; being installed automatically to enable the level of the system to be tracked. Mandatory -- Considered to be important to the system; will always be installed when detected on the installation media. Requisite -- Quick Installation 1-19 Quick Installation 1.5 Installing RTR for AIX Requisite of other filesets being installed. P_Requisite -- Previously installed fileset's requisite; being installed automatically now to ensure system's consistency. (Only installed automatically when "auto- install" (-g flag) is specified.) Supersedes -- Superseding fileset update; not selected, chosen instead of an older, selected update. (Only chosen in this fashion when "auto-install" is specified (- g flag)). << End of Success Section >> FILESET STATISTICS ------------------ 1 Selected to be installed, of which: 1 Passed pre-installation verification ---- 1 Total to be installed +---------------------------------------------------------- -------------------+ Installing Software... +---------------------------------------------------------- -------------------+ installp: APPLYING software for: RTR320.rte x.xx.xxx.x . . . . . << Copyright notice for RTR320 >> . . . . . . . # Copyright 1994, 1999 Digital Equipment Corporation. # # Restricted Rights: Use, duplication, or disclosure by the U.S. Government # is subject to restrictions as set forth in subparagraph (c) (1) (ii) of # DFARS 252.227-7013, or in FAR 52.227- 1-20 Quick Installation Quick Installation 1.5 Installing RTR for AIX 19, or in FAR 52.227-14 Alt. III, as # applicable. # # This software is proprietary to and embodies the confidential technology # of Compaq Computer Corporation and Digital Equipment Corporation. # Possession, use, or copying of this software and media is authorized # only pursuant to a valid written license from Compaq or an # authorized sublicensor. # # Compaq, the Compaq logo, and the Digital logo are registered in the # U.S. Patent and Trademark Office. . . . . . << End of copyright notice for RTR320 >>. . . . New volume on /usr/users/zhang/kit238install/output/usr/sys/inst.images/RTR320: Cluster size is 51200 bytes (100 blocks). The volume number is 1. The backup date is: Fri May 28 14:31:21 EDT 1999 Files are backed up by name. The user is scrtest. The number of restored files is 73. x 0 ./usr/lpp/RTR320 x 0 ./usr/lpp/RTR320/bin x 2450 ./usr/lpp/RTR320/bin/rtr x 10083 ./usr/lpp/RTR320/bin/rtr_rqif x 4027 ./usr/lpp/RTR320/bin/rtr_snapshot.sh x 0 ./usr/lpp/RTR320/shlib x 8048187 ./usr/lpp/RTR320/shlib/librtr_r.a x 0 ./usr/lpp/RTR320/lib x 0 ./usr/lpp/RTR320/lib/doclib x 577269 ./usr/lpp/RTR320/lib/rtr.h x 0 ./usr/lpp/RTR320/examples x 0 ./usr/lpp/RTR320/examples/rtr x 11736 ./usr/lpp/RTR320/examples/rtr/rtrreq.c x 8317 ./usr/lpp/RTR320/examples/rtr/rtrsrv.c x 11464 ./usr/lpp/RTR320/examples/rtr/crtr.cxx x 6139 ./usr/lpp/RTR320/examples/rtr/crtr.hxx x 378 ./usr/lpp/RTR320/examples/rtr/cslb.hxx x 501 ./usr/lpp/RTR320/examples/rtr/example_ cslb.hxx x 897 ./usr/lpp/RTR320/examples/rtr/example_ srv.cxx x 933 ./usr/lpp/RTR320/examples/rtr/example_ Quick Installation 1-21 Quick Installation 1.5 Installing RTR for AIX cli.cxx x 13319 ./usr/lpp/RTR320/examples/rtr/rtr_ivp_osf.sh x 0 ./usr/lpp/RTR320/mon x 3477 ./usr/lpp/RTR320/mon/accfail.mon x 7657 ./usr/lpp/RTR320/mon/acp2app.mon x 1080 ./usr/lpp/RTR320/mon/active.mon x 3926 ./usr/lpp/RTR320/mon/app2acp.mon x 2295 ./usr/lpp/RTR320/mon/broadcast.mon x 10621 ./usr/lpp/RTR320/mon/calls.mon x 955 ./usr/lpp/RTR320/mon/channel.mon x 2633 ./usr/lpp/RTR320/mon/connects.mon x 6629 ./usr/lpp/RTR320/mon/ddtm.mon x 4953 ./usr/lpp/RTR320/mon/dtx.mon x 4681 ./usr/lpp/RTR320/mon/dtxrec.mon x 1847 ./usr/lpp/RTR320/mon/event.mon x 5596 ./usr/lpp/RTR320/mon/facility.mon x 4081 ./usr/lpp/RTR320/mon/flow.mon x 1432 ./usr/lpp/RTR320/mon/frontend.mon x 2546 ./usr/lpp/RTR320/mon/group.mon x 3150 ./usr/lpp/RTR320/mon/ipc.mon x 3398 ./usr/lpp/RTR320/mon/ipcrate.mon x 6375 ./usr/lpp/RTR320/mon/jcalls.mon x 4899 ./usr/lpp/RTR320/mon/journal.mon x 3873 ./usr/lpp/RTR320/mon/link.mon x 2561 ./usr/lpp/RTR320/mon/netbytes.mon x 3960 ./usr/lpp/RTR320/mon/netstat.mon x 15563 ./usr/lpp/RTR320/mon/rdm.mon x 1181 ./usr/lpp/RTR320/mon/partit.mon x 1289 ./usr/lpp/RTR320/mon/queues.mon x 1276 ./usr/lpp/RTR320/mon/quorum.mon x 1502 ./usr/lpp/RTR320/mon/recovery.mon x 1372 ./usr/lpp/RTR320/mon/rejects.mon x 9108 ./usr/lpp/RTR320/mon/rejhist.mon x 1284 ./usr/lpp/RTR320/mon/response.mon x 3265 ./usr/lpp/RTR320/mon/rfb.mon x 2444 ./usr/lpp/RTR320/mon/rolequor.mon x 1796 ./usr/lpp/RTR320/mon/routers.mon x 1390 ./usr/lpp/RTR320/mon/routing.mon x 48092 ./usr/lpp/RTR320/mon/rscbe.mon x 2444 ./usr/lpp/RTR320/mon/rtr.mon x 2859 ./usr/lpp/RTR320/mon/stalls.mon x 6271 ./usr/lpp/RTR320/mon/system.mon x 1786 ./usr/lpp/RTR320/mon/tps.mon 1-22 Quick Installation Quick Installation 1.5 Installing RTR for AIX x 1848 ./usr/lpp/RTR320/mon/tpslo.mon x 2844 ./usr/lpp/RTR320/mon/traffic.mon x 2018 ./usr/lpp/RTR320/mon/trans.mon x 5271 ./usr/lpp/RTR320/mon/v2calls.mon x 3873 ./usr/lpp/RTR320/mon/xa.mon x 0 ./usr/lpp/RTR320/hlp x 726615 ./usr/lpp/RTR320/hlp/rtr.hlb x 708 ./usr/lpp/RTR320/hlp/copyright.txt x 4425 ./usr/lpp/RTR320/hlp/license.txt x 700198 ./usr/lpp/RTR320/hlp/rtr.hlp x 0 ./usr/lpp/RTR320/inst_root The total size is 10339047 bytes. # Copyright 1994, 1999 Digital Equipment Corporation. # # Restricted Rights: Use, duplication, or disclosure by the U.S. Government # is subject to restrictions as set forth in subparagraph (c) (1) (ii) of # DFARS 252.227-7013, or in FAR 52.227- 19, or in FAR 52.227-14 Alt. III, as # applicable. # # This software is proprietary to and embodies the confidential technology # of Compaq Computer Corporation and Digital Equipment Corporation. # Possession, use, or copying of this software and media is authorized # only pursuant to a valid written license from Compaq or an # authorized sublicensor. # # Compaq, the Compaq logo, and the Digital logo are registered in the # U.S. Patent and Trademark Office. aio0 Available Asynchronous I/O autoconfig available STATE to be configured at system restart True aio0 Available aio0 changed aio0 Available Asynchronous I/O autoconfig available STATE to be configured at system restart True Installation of RTR V3.2 complete Finished processing all filesets. (Total time: 19 secs). +---------------------------------------------------------- -------------------+ Summaries: +---------------------------------------------------------- -------------------+ Quick Installation 1-23 Quick Installation 1.5 Installing RTR for AIX Installation Summary -------------------- Name Level Part Event Result ----------------------------------------------------------- -------------------- RTR320.rte x.xx.xxx.x USR APPLY SUCCESS RTR320.rte x.xx.xxx.x ROOT APPLY SUCCESS 1.5.3 Sample IVP Output The following shows output from an AIX IVP. ________________________ Note ________________________ Do not run the IVP program on a production system, as it may alter the RTR journal or interrupt processing of transactions. You will be prompted to abort the IVP before it can do any damage. Consider your situation carefully before running the IVP. ______________________________________________________ Copyright 1994, 1999 Digital Equipment Corporation. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Compaq Computer Corporation and Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Compaq or an authorized sublicensor. Compaq, the Compaq logo, and the Digital logo are registered in the U.S. Patent and Trademark Office. Starting Reliable Transaction Router V3.2 for AIX Installation Verification Procedure 1-24 Quick Installation Quick Installation 1.5 Installing RTR for AIX IVP: This is not a clean start: IVP: Result may be affected by previous settings in shared memory. IVP: Result may be affected by existing processes. IVP: Result may be affected by locks held by existing processes. IVP: Existing pipe files will normally be recycled correctly. IVP: Any existing journal will be used and modified. IVP: Facilities RTR_IVP_FACILITY and RTR will be created. IVP: Result may be affected by size and contents of any existing journal. IVP: The sample client and server do not necessarily complete IVP: if they encounter previously journalled transactions. IVP: Would you like to abort the IVP? (y/n) n keeping any existing log file settings (RTR_DBG not set) starting RTR . . . creating a journal, if not already created . . . creating test facility . . . stopping RTR. [OPTIONAL] attempting to compile and link rtr test applications . . . If this system is not configured with an application development environment, or the platform does not support threads, then some messages about application compilation not succeeding are normal. multithreaded server rtr application compiled single-threaded client rtr application compiled applications rtrreq and rtrsrv available starting rtr and creating default facility %RTR-S-RTRSTART, RTR started on node nodeA %RTR-S-FACCREATED, facility RTR$DEFAULT_FACILITY created starting an rtr server application running an rtr client application, should complete in a few seconds stopping rtr %RTR-S-RTRSTOP, RTR stopped on node nodeA © 1999 Compaq Computer Corporation and Digital Equipment Corporation. All rights reserved. Reliable Transaction Router V3.2 for AIX Installation Verification Procedure successful Quick Installation 1-25 Quick Installation 1.6 Installing RTR for HP-UX 1.6 Installing RTR for HP-UX Your Reliable Transaction Router for HP-UX kit is supplied on CD-ROM. The Release Notes are also on the CD-ROM; you are advised to read the Release Notes before using RTR. The installation requires about 3000KB free disk space. The installation procedure takes about two minutes to complete. 1.6.1 Installation Procedure o If you have any previous version of RTR, make sure that it is not running:- # rtr stop rtr # rtr disconnect server o Become root or superuser and mount the CD-ROM drive. (The following assumes that the mount point is /cdrom). To install RTR on HP-UX: (the kit will be in the form of a UNIX tar file, whether it is copied by FTP or directly from the CD-ROM) 1. Copy the file to a convenient location on the target machine, preferably /opt/rtr 2. Change directory to the location (for example, cd /opt/rtr and unpack the tar file: tar xvf RTR320.tar 3. Use the swinstall graphical utility provided by HP to install the software. o Specify the untarred location of the files as the source depot: /opt/rtr o The product name RTR320 should appear in the "SD Install" Window. Click this line with the cursor. o From the "Actions" pull-down menu, select "Install." o The Install Analysis phase will begin. When it completes, select OK. o You may see several warning windows. In each, select either Yes or OK. o When the installation is finished, the Done button is highlighted. You may first want to inspect the logfile by selecting the Logfile button. 1-26 Quick Installation Quick Installation 1.6 Installing RTR for HP-UX o Select the Done button to complete the installation. 1.6.2 Running the IVP ________________________ Note ________________________ Do not run the IVP program on a production system, as it may alter the RTR journal or interrupt processing of transactions. You will be prompted to abort the IVP before it can do any damage. Consider your situation carefully before running the IVP. ______________________________________________________ To run the IVP, execute the following command: /RTR320/rtr/examples/rtr/rtr_ivp_osf.sh or, if source depot is /opt/rtr: /opt/rtr/RTR320/rtr/examples/rtr/rtr_ivp_osf.sh 1.6.3 Sample IVP Output RTR API & Management Utility (RTRBASE320) Copyright 1994, 1999 Digital Equipment Corporation. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227- 19, or in FAR 52.227-14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Compaq Computer Corporation and Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Compaq or an authorized sublicensor. Compaq, the Compaq logo, and the Digital logo are registered in the U.S. Patent and Trademark Office. Starting Reliable Transaction Router V3.2 for HP-UX Installation Verification Procedure Quick Installation 1-27 Quick Installation 1.6 Installing RTR for HP-UX IVP: This is not a clean start: IVP: Result may be affected by previous settings in shared memory. IVP: Result may be affected by existing processes. IVP: Result may be affected by locks held by existing processes. IVP: Existing pipe files IVP: This is not a clean start: IVP: Any existing journal will be used and modified. IVP: Facilities RTR_IVP_FACILITY and RTR will be created. IVP: Result may be affected by size and contents of any existing journal. IVP: The sample client and server do not necessarily complete IVP: if they encounter previously journalled transactions. Would you like to abort the IVP? (y/n) n IVP continuing ... keeping any existing log file settings (RTR_DBG not set) starting RTR . . . creating a journal, if not already created . . . creating test facility . . . stopping RTR. [OPTIONAL] attempting to compile and link rtr test applications . . . If this system is not configured with an application development environment, or the platform does not support threads, then some messages about application compilation not succeeding are normal. multithreaded server rtr application compiled single-threaded client rtr application compiled applications rtrreq and rtrsrv available starting rtr and creating default facility %RTR-S-RTRSTART, RTR started on node hpnode %RTR-S-FACCREATED, facility RTR$DEFAULT_FACILITY created starting an rtr server application running an rtr client application, should complete in a few seconds stopping rtr %RTR-S-RTRSTOP, RTR stopped on node hpnode Copyright 1994, 1999 Digital Equipment Corporation. All rights reserved. Reliable Transaction Router V3.2 for Compaq Tru64 UNIX Installation Verification Procedure successful 1-28 Quick Installation 2 _________________________________________________________________ Upgrade Process To upgrade RTR, use the following process: 1. Shutdown RTR 2. Uninstall RTR 3. Install RTR 4. Run the IVP (optional) 2.1 Uninstalling RTR To uninstall RTR, enter a command of the following form: remove-command RTR320 ________________________ Note ________________________ Remove commands do not eradicate 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. ______________________________________________________ 2.1.1 Uninstalling on OpenVMS To remove RTR, use the following command: PRODUCT REMOVE RTR Upgrade Process 2-1 Upgrade Process 2.1 Uninstalling RTR 2.1.2 Uninstalling on Windows NT, Windows 95, and Windows 98 You must unregister RTR as a service before uninstalling RTR on these systems. Do this with the following menu picks from the Program menu: Compaq -> RTR -> Useful Batch Files -> Unregister Service You also need to delete all *.LCK files, and the file called RTRenvps (shared memory). To uninstall RTR, issue the following command at the MS-DOS prompt: RTR STOP RTR RTR DISCONNECT SERVER/DAEMON DELETE /S/Q C:\Program Files\Compaq\Reliable Transaction Router You can also use the Shutdown command, which executes Shutdown.bat. You can access the shutdown procedure with the following menu picks: Compaq -> RTR -> Useful Batch Files -> Shutdown 2.1.3 Uninstalling on Compaq Tru64 UNIX Use the following command: setld -d RTR320 Also 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 2-2 Upgrade Process Upgrade Process 2.1 Uninstalling RTR 2.1.4 Uninstalling on Sun Use the following command: pkgrm RTR320 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 2.1.5 Uninstalling on AIX Use the following command: smit install_remove Also 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/lpp/RTR320 2.1.6 Uninstalling on HP-UX Use the following command: swremove RTR320 You can also use the swremove graphical utility to accomplish the same thing. See the man pages and documentation provided by HP for details regarding swremove and swinstall. Upgrade Process 2-3 Upgrade Process 2.1 Uninstalling RTR To completely eradicate RTR from your system, enter the following additional commands (the last directory is user configurable, so verify its location before executing this last command): rm -rf /rtr rm -rf /rtrjnl rm -rf /opt/rtr 2-4 Upgrade Process 3 _________________________________________________________________ Full Installation on OpenVMS This chapter describes how to install Reliable Transaction Router on OpenVMS for both OpenVMS VAX and OpenVMS Alpha systems. A step-by-step description of the installation procedure is given. 3.1 Preparing for Installation Before you start the installation, complete the preparation tasks outlined in this section. 3.1.1 Prerequisite and Optional Software Table 3-1 provides information on the software that must be installed on your system before installing Reliable Transaction Router. The table also includes information about optional software that you can use with Reliable Transaction Router. The Software Product Description (SPD) contains a complete list of prerequisite and optional software and their required version numbers. Table_3-1_Prerequisite_and_Optional_Software_______________ Prerequisite_Products______Purpose_________________________ OpenVMS VAX Version System Software 6.2,7.1,7.2 or OpenVMS Alpha Version System Software 6.2,7.1,7.2 (continued on next page) Full Installation on OpenVMS 3-1 Full Installation on OpenVMS 3.1 Preparing for Installation Table_3-1_(Cont.)_Prerequisite_and_Optional_Software_______ Optional_Products__________Purpose_________________________ Compaq TCP/IP Services Network Transport for OpenVMS (Version 4.0 or higher) DECnet or DECnet-Plus Network Transport (Version 6.3 ECO5 or higher)____________________________________________________ The Installation Verification Procedure (IVP) will complete successfully only if at least one of the supported network protocols (DECnet or TCP/IP) is installed. 3.1.2 Registering your Software License You must register and load your license for Reliable Transaction Router before you start the installation in order to run the Installation Verification Procedure (IVP) and use the software. To register a license under OpenVMS, first log in to the system manager's account, SYSTEM. You then have a choice of two ways to perform the registration: 1. Invoke the SYS$UPDATE:VMSLICENSE.COM procedure. When it prompts you for information, respond with data from your License PAK. 2. At the DCL prompt, enter the LICENSE REGISTER command with the appropriate qualifiers that correspond to License PAK information. If you plan to use Reliable Transaction Router on more than one node in a VMScluster, you will need to perform a license load on the other nodes after you complete this installation (or reboot the cluster). For complete information on using LMF, see the OpenVMS License Management Utility Manual. 3-2 Full Installation on OpenVMS Full Installation on OpenVMS 3.1 Preparing for Installation 3.1.3 Required Disk Space Reliable Transaction Router's requirements for free disk storage space are different during installation and after installation. Table 3-2 summarizes the storage requirements. Table_3-2_Disk_Space_Requirements__________________________ Blocks During Blocks After Kit___________________Installation__________Installation___ Reliable Transaction 50000 36000 Router for OpenVMS VAX Reliable Transaction 50000 36000 Router for OpenVMS Alpha______________________________________________________ To determine the number of free disk blocks on the current system disk, enter the following command at the DCL prompt: $ SHOW DEVICE SYS$SYSDEVICE 3.1.4 System Parameters Installing Reliable Transaction Router for OpenVMS requires certain system parameter settings. Table 3-3 lists the minimum required system parameter values for the installation. Depending on the kinds of programs and applications running at your site, you may need higher values for some settings. Table_3-3_Minimum_Required_System_Parameter_Values_________ System_Parameter___________Minimum_Value___________________ GBLPAGES 4000 GBLSECTIONS________________4_______________________________ Full Installation on OpenVMS 3-3 Full Installation on OpenVMS 3.2 Installation Procedure 3.2 Installation Procedure Log on to the System Manager's account to do the installation. The Reliable Transaction Router installation procedure uses the POLYCENTER Software Installation Utility (PCSI). For details on using PCSI, refer to the OpenVMS System Manager's Manual, Section "Installing with the POLYCENTER Software Installation Utility." The logical name PCSI$SOURCE is used to define the location of the software kits you want to install. For example, if the Reliable Transaction Router software is located in DISK1:[KITS], enter the following at the DCL prompt (or include the line in the system manager's login command file): $ DEFINE PCSI$SOURCE DISK1:[KITS] When running the installation procedure for Reliable Transaction Router, you can choose whether to install the ODBC Over RTR Oracle7 Server. This is an RTR server used for supporting ODBC-enabled client applications on Windows. ________________________ Note ________________________ Do not install the ODBC Over RTR Oracle7 Server unless you already have Oracle7 installed. ______________________________________________________ 3.3 Running RTR and the IVP Before starting the installation, stop all RTR processes on the system. To do this, issue the following commands: $ RTR STOP RTR $ RTR DISCONNECT SERVER ________________________ Note ________________________ For information on installing ODBC over RTR, see Appendix B. ______________________________________________________ 3-4 Full Installation on OpenVMS Full Installation on OpenVMS 3.3 Running RTR and the IVP The installation prompts you with questions. Enter your response to each question and press the key. Defaults are shown in square brackets, for example, [YES]. To start the installation, enter the command: $ PRODUCT INSTALL RTR/HELP A display similar to the following appears: The following product has been selected: DEC VAXVMS RTR V3.2-xxx Layered Product Do you want to continue? [YES] Configuration phase starting ... You will be asked to choose options, if any, for each selected product and for any products that may be installed to satisfy software dependency requirements. DEC VAXVMS RTR V3.2-239: Reliable Transaction Router for OpenVMS Software fault tolerant middleware for high performance distributed transaction processing. Also available for, and interoperable with the following platforms: o Compaq Tru64 UNIX o Windows NT o Solaris o AIX o with others in preparation Copyright Digital Equipment Corporation. 1994, 1999. All rights reserved. © 1994, 1999 Digital Equipment Corporation. All rights reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Compaq Computer Corporation and Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Compaq or an authorized sublicensor. Full Installation on OpenVMS 3-5 Full Installation on OpenVMS 3.3 Running RTR and the IVP Compaq, the Compaq logo, and the Digital logo are registered in the U.S. Patent and Trademark Office. This product uses the PAKs RTR-CL and RTR-SVR. This software is furnished under the licensing provisions of Compaq Computer Corporation's Standard Terms and Conditions. For more in- formation about Compaq's licensing terms and policies, contact your local Compaq office. This product requires one of the following PAKS: RTR-CL - enables front end functionality RTR-SVR - additionally enables RTR router and back end roles. Do you want the defaults for all options? [YES] no Please delete all RTRACP*, RTRCSV* and RTRD processes, as well as any user processes showing the "RTR>" prompt. Have all RTR processes on the system been stopped? [YES] This option installs the Oracle7 server for use with ODBC Over RTR. If this server is installed, client software that uses the OOR (ODBC Over RTR) ODBC driver can access an Oracle7 database using RTR as the transport. Installing this option requires that Oracle7 is installed on the system. ODBC Over RTR Oracle7 Server [NO] Before running the IVP on a production system, first shut down all RTR applications and stop RTR on all nodes booting from this system disk. Run installation verification procedure [NO] yes Please see your Compaq Representative about obtaining the ECO 5 patch to DECNet/OSI V6.3. Failure to do so may result in run-time problems with erroneous link shutdowns. If you plan to use only TCP as a transport or are installing RTR in a test environment, you can safely proceed with the intallation. DECnet Phase IV users can also ignore this warning. DECnet users:Have you read the Release Note regarding minimum version? [YES] Do you want to review the options? [NO] 3-6 Full Installation on OpenVMS Full Installation on OpenVMS 3.3 Running RTR and the IVP Execution phase starting ... The following product will be installed to destination: DEC VAXVMS RTR V3.2-xxx DISK$OVMSVAXSYS:[VMS$COMMON.] Portion done: 0%...10%...20%...30%...50%...60%...70%...80%...90%...100% The following product has been installed: DEC VAXVMS RTR V3.2-xxx Layered Product %PCSI-I-IVPEXECUTE, executing test procedure for DEC VAXVMS RTR V3.2-xxx ... %PCSI-I-PRCOUTPUT, output from subprocess follows ... %PCSI-I-IVPSUCCESS, test procedure completed successfully DEC VAXVMS RTR V3.2-xxx: Reliable Transaction Router for OpenVMS Insert the following lines in SYS$MANAGER:SYSTARTUP_VMS.COM: @sys$startup:rtr$startup.com Insert the following lines in SYS$MANAGER:SYSHUTDWN.COM: @sys$manager:rtr$shutdown 3.4 After Installing RTR After completing the installation, you can: o Access Release Notes o Edit system files o Verify user account requirements 3.4.1 Accessing 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.4.2 Editing 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. Full Installation on OpenVMS 3-7 Full Installation on OpenVMS 3.4 After Installing RTR 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.4.3 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. 3.4.3.1 Quotas Table 3-4 summarizes the required user account quotas. Table 3-4 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 [1]At_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-8 Full Installation on OpenVMS Full Installation on OpenVMS 3.4 After Installing RTR 3.4.3.2 Privileges To use the features of Reliable Transaction Router, each account must have the following privileges: o NETMBX o TMPMBX o SYSLCK In addition, the Rights Identifier RTR$INFO is required. 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.5 Files Installed on OpenVMS This section lists the files added to your system by the installation on OpenVMS. [vms$common]rtr.dir [sys$startup]rtr$startup.com [sysexe]rtr.exe [sysexe]rtr$remote.com [sysexe]rtr_start_acp.com [syslib]rtr.h [syslib]librtr.exe [sysmgr]rtr$snapshot.com [sysmgr]rtr$shutdown.com [systest]rtr$ivp.com [syshlp]rtr_relnotes.txt [syshlp]rtr_relnotes.ps [syshlp]rtr.hlb [syshlp]rtr_migration_guide.ps Full Installation on OpenVMS 3-9 Full Installation on OpenVMS 3.5 Files Installed on OpenVMS [rtr]ACCFAIL.mon [rtr]ACP2APP.mon [rtr]ACTIVE.mon [rtr]APP2ACP.mon [rtr]BROADCAST.mon [rtr]CALLS.mon [rtr]CHANNEL.mon [rtr]CONNECTS.mon [rtr]DDTM.mon [rtr]DTX.mon [rtr]DTXREC.mon [rtr]EVENT.mon [rtr]FACILITY.mon [rtr]FLOW.mon [rtr]FRONTEND.mon [rtr]GROUP.mon [rtr]IPC.mon [rtr]IPCRATE.mon [rtr]JCALLS.mon [rtr]JOURNAL.mon [rtr]LINK.mon [rtr]NETBYTES.mon [rtr]NETSTAT.mon [rtr]PARTIT.mon [rtr]QUEUES.mon [rtr]QUORUM.mon [rtr]RDM.mon [rtr]RECOVERY.mon [rtr]REJECTS.mon [rtr]REJHIST.mon [rtr]RESPONSE.mon [rtr]RFB.mon [rtr]ROLEQUOR.mon [rtr]ROUTERS.mon [rtr]ROUTING.mon [rtr]RSCBE.mon [rtr]RTR.mon [rtr]STALLS.mon [rtr]SYSTEM.mon [rtr]TPS.mon [rtr]TPSLO.mon [rtr]TRAFFIC.mon [rtr]TRANS.mon 3-10 Full Installation on OpenVMS Full Installation on OpenVMS 3.5 Files Installed on OpenVMS [rtr]V2CALLS.mon [rtr]XA.mon [sysmsg]oormsg.exe (optional component) [syslib]oorcmp.exe (optional component) [sysexe]ooro7v2.exe (optional component) sys$examples:[rtr]crtr.cxx sys$examples:[rtr]crtr.hxx sys$examples:[rtr]cslb.hxx sys$examples:[rtr]example_cli.cxx sys$examples:[rtr]example_cslib.hxx sys$examples:[rtr]example_srv.cxx sys$examples:[rtr]rtr_ivp_osf.sh sys$examples:[rtr]rtrreq.c sys$examples:[rtr]rtrsrv.c Full Installation on OpenVMS 3-11 4 _________________________________________________________________ Full Installation on Windows NT This chapter describes a full installation on Windows NT to run RTR as a server. For information on installing RTR for client applications on Windows 95 or Windows 98, see Section 1.2. The installation of the RTR base product requires about five megabytes of disk space. The installation procedure takes about two minutes to complete. _____________ Note: Online Release Notes _____________ The release notes and README files provide information for RTR that could not be included in the printed documentation. The release notes are in the following files on the CD-ROM: RELNOTES.TXT RELNOTES.PS (PostScript) readmeNT.txt or readme95.txt ______________________________________________________ 4.1 Installation Requirements 4.1.1 Hardware Requirements o For full-function functionality, any Alpha or Intel architecture system that runs Windows NT Version 4.0. o For frontend functionality, any Alpha or Intel system that runs Windows NT Version 4.0, or any system that runs Windows 95 or Window 98. o A CD-ROM drive is required for installation. Full Installation on Windows NT 4-1 Full Installation on Windows NT 4.1 Installation Requirements 4.1.2 Software Requirements o Windows NT Operating System Version 4.0, or Windows 95 or Windows 98 Operating System (frontend only). o TCP/IP o For Windows NT, Microsoft Windows NT Service Pack 3 is required as a minimum. RTR has also been tested with Service Pack 4. 4.1.3 Required Memory o For Windows 95, Windows 98, and Windows NT Intel systems, a minimum of 16MB RAM is recommended. o For Windows NT Alpha systems, a minimum of 32MB RAM is recommended. 4.2 Installation Procedure 1. If you are installing on Windows NT, ensure that you are logged in as the Administrator, or have administrator privileges. 2. If you have installed a previous version of RTR you must: i Stop RTR and check that RTR is not in the startup program group. (Issue the following commands in an MS DOS window): RTR STOP RTR RTR DISCONNECT SERVER/DAEMON ii Delete the file RTRENVPS in the RTR root directory. iii Logout of your Windows NT session and login again. (This to ensure that no background RTR tasks are running.) iv To eradicate RTR V3.1D from the disk, issue the following command: DELETE /S/Q C:\RTR v Delete existing icon 3. Insert the RTR CD into the drive. 4-2 Full Installation on Windows NT Full Installation on Windows NT 4.2 Installation Procedure 4. Exit all Windows programs to run Setup. 5. From the Start button, invoke Windows Explorer to view files. 6. Choose the drive letter of your CD-ROM and open the directory ALPHA or I386, depending on your processor type (Alpha or Intel, respectively). Double click on the file SETUP.EXE. This starts the InstallShield that takes you through the setup process. 7. The InstallShield wizard steps you through the installation. Click on the Next button to continue installation or on the Cancel button to stop it. 8. Accept the terms of the License Agreement. If you reject the terms, installation is stopped. 9. Follow the screen instructions to enter the name of the directory where you want to install RTR. The default is C:\Program Files\Compaq\Reliable Transaction Router Compaq recommends that you install RTR on a local hard disk (NTFS or FAT). 10.Choose the Setup Type: Typical, Compact, or Custom by selecting a radio button. Choices are: o Typical: RTR is installed with the most common options. Recommended for most users. o Compact: RTR is installed with the minimum required options. Selecting compact installs RTR with no example files. o Custom: Choose the options to install (for advanced users only). Choose this to install an add-on such as ODBC Over RTR or RTR as a Service (NT only). If you select Custom, the components screen appears. Choose components to install. The screen display indicates how much disk space is required for each component. ________________________ Note ________________________ RTR as a Service runs only on Windows NT; the InstallShield does not register the service but Full Installation on Windows NT 4-3 Full Installation on Windows NT 4.2 Installation Procedure RTR provides batch procedures to do so in the target directory. ______________________________________________________ 11.Setup adds a program icon to the Program Folder you select, and installs files in the appropriate location. 12.The InstallShield completes the installation, displaying a progress graphic until installation is complete. 13.Click on Finish to complete the installation of RTR. 4.3 After Installing If you install RTR on an NTFS drive, you will need to give RTR users access to the RTR directories. Use Windows NT Explorer and select the RTR root directory. Pull down the Security menu and choose File permissions. Give the RTR root directory and all its subdirectories "Full Control" access for all RTR users. You may then restrict access on individual files to read only. (All RTR users require write access to the RTR journal directory.) The following examples are provided in the [EXAMPLES] directory: o rtrreq.c o rtrsrv.c o rtrw32rq.c The program rtrreq.c is a console mode client; the program rtrsrv.c is a console mode server. The program rtrw32rq.c is a sample GUI client that can run with rtrsrv.c. The example applications can be built by using the examples.mak file: NMAKE/f examples.mak ________________________ Note ________________________ The Windows registry will be modified slightly as a result of a RTR installation. ______________________________________________________ 4-4 Full Installation on Windows NT Full Installation on Windows NT 4.4 Files Installed on Microsoft Windows NT 4.4 Files Installed on Microsoft Windows NT . .. Accfail.mon Acp2app.mon Active.mon App2acp.mon Broadcast.mon Calls.mon Channel.mon Connects.mon Ddtm.mon Dtx.mon Dtxrec.mon examples Event.mon Facility.mon Flow.mon Frontend.mon Group.mon installservice.bat Ipc.mon Ipcrate.mon Jcalls.mon Journal.mon Link.mon Msvcrt.dll Oorcmp.dll Oorodb32.dll Ooroml32.dll Oorrot13.dll Oorstp32.dll Netbytes.mon Netstat.mon Partit.mon Queues.mon Quorum.mon Rdm.mon readment.txt Recovery.mon Rejects.mon Rejhist.mon Response.mon Full Installation on Windows NT 4-5 Full Installation on Windows NT 4.4 Files Installed on Microsoft Windows NT Rfb.mon Rolequor.mon Routers.mon Routing.mon Rscbe.mon rtr.exe Rtr.h Rtr.hlb Rtr.hlp rtr.ico Rtr.mon rtrdll.dll rtrdll.lib RTRSvc.exe shutdown.bat Stalls.mon System.mon Tps.mon Tpslo.mon Traffic.mon Trans.mon Uninst.isu uninstallservice.bat V2calls.mon xa.mon \examples doswin16.mak examples.mak rtrreq.c rtrsrv.c rtrw32rq.c rtrw32rq.def rtrw32rq.dlg rtrw32rq.h rtrw32rq.rc 4-6 Full Installation on Windows NT 5 _________________________________________________________________ Full Installation on Compaq Tru64 UNIX This chapter provides descriptions of all steps in doing a full installation including: o Preparing for installation o Installing o Verifying the installation 5.1 Preparing for RTR Installation on Compaq Tru64 UNIX 5.1.1 Checking the Software Distribution Kit RTR software is distributed on CD-ROM as part of Compaq's Layered Products Consolidated Distribution. Use the Bill of Materials (BOM) to check the contents of your RTR software distribution kit. In addition to this guide, the software distribution kit includes the following: o A CD-ROM for systems with CD-ROM drives o A CD-ROM booklet and CD-ROM read first letter If your software distribution kit is damaged or incomplete, contact your Compaq representative. 5.1.2 Reading the Online Release Notes RTR provides online release notes. Compaq strongly recommends that you read the release notes before using the product. The release notes may contain information about changes to the application. The release notes for RTR are in the following file on the CD-ROM: rtr3xx_relnotes.txt Where "xx" represents a revision level. Full Installation on Compaq Tru64 UNIX 5-1 Full Installation on Compaq Tru64 UNIX 5.1 Preparing for RTR Installation on Compaq Tru64 UNIX You can use the following command to read the release notes. more rtr3xx_relnotes.txt Where "xx" represents a revision level. 5.1.3 Registering 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 Compaq 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. 5-2 Full Installation on Compaq Tru64 UNIX Full Installation on Compaq Tru64 UNIX 5.1 Preparing for RTR Installation on Compaq Tru64 UNIX 5.1.4 Checking Installation Requirements This section discusses requirements for installing RTR. Installing RTR, including running the Installation Verification Procedure (IVP), takes approximately 10 to 15 minutes, depending on your type of media and system configuration. 5.1.4.1 Checking Login Privileges You must have superuser privileges to install the RTR software and to register the license PAK. 5.1.4.2 Checking Hardware Requirements To install RTR, you need the following hardware: o 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. o 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. 5.1.4.3 Checking Software Requirements RTR requires the Compaq Tru64 UNIX operating system shown on the cover of this manual. RTR also requires that the following Compaq Tru64 UNIX software subset be loaded on the system where you install RTR: o OSFBASE-the Base System subset The following Compaq Tru64 UNIX software subsets are optional on the system where you install RTR: o OSFCLINET200-Basic Networking Services (TCP/IP) subset o DNABASE110-DECnet/OSI Base Components subset, together with Full Installation on Compaq Tru64 UNIX 5-3 Full Installation on Compaq Tru64 UNIX 5.1 Preparing for RTR Installation on Compaq Tru64 UNIX o DNANETMAN110-DECnet/OSI Network Management subset To check whether these subsets are loaded, follow these steps: 1. Log in to the system where you will install RTR. 2. Enter the following command: # setld -i | egrep 'OSFBASE|DNA' If you do not log in as superuser (login name root), you must enter the full path of the command. For example: % /usr/sbin/setld -i | grep OSFBASE Check the displayed rows for the name of the relevant subset and any related patches. The word "installed" appears in a row 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 Compaq Tru64 UNIX software before installing RTR. (For information on how to load the operating system software, see the Guide to Installing Compaq Tru64 UNIX.) 5.1.4.4 Determining Which Subsets to Load RTR has only one subset: - rtrbase320 RTR runtime and system management. 5.1.4.5 Determining Disk Space Requirements Table 5-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_5-1_RTR_Subset_Size_(Kilobytes_Required)_____________ Subset Subset_Title_____Name________/usr/opt/___/rtr______________ RTR rtrbase320 57020 1050 Total:_______________________58070_________________________ 5-4 Full Installation on Compaq Tru64 UNIX Full Installation on Compaq Tru64 UNIX 5.1 Preparing for RTR Installation on Compaq Tru64 UNIX Using these disk space requirements, calculate the total values for the subsets you will load in each directory. You will also require 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. 5.1.4.5.1 Checking 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 /usr Filesystem Total kbytes kbytes % node kbytes used free used Mounted on /dev/rd0g 122598 54447 55892 49% /usr This display shows that there are 55,892 Kbytes free. This free space must accommodate the subset requirements listed in Table 5-1, RTR Subset Size (Kilobytes Required). On systems where /usr/lib and /usr/man are mounted to different devices from /usr, enter the following command: # df /usr/lib /usr/man Full Installation on Compaq Tru64 UNIX 5-5 Full Installation on Compaq Tru64 UNIX 5.1 Preparing for RTR Installation on Compaq Tru64 UNIX 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. 5.1.4.5.2 Increasing Disk Space by Using Alternative Disks The RTR installation procedure creates the following directory and loads files into subordinate directories: /usr/opt/RTR320 If the /usr/opt/RTR320 directory node in the previous path does not exist, the installation procedure creates it. If the RTR320 node 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/RTR320. 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. 5.1.5 Installing from Media or Using 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: o A RTR network kit is available for use. 5-6 Full Installation on Compaq Tru64 UNIX Full Installation on Compaq Tru64 UNIX 5.1 Preparing for RTR Installation on Compaq Tru64 UNIX o 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 5.2.1.2. 5.1.6 Backing Up Your System Disk 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 for RTR 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. Full Installation on Compaq Tru64 UNIX 5-7 Full Installation on Compaq Tru64 UNIX 5.2 Installing RTR on Compaq Tru64 UNIX 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-8 Full Installation on Compaq Tru64 UNIX Full Installation on Compaq Tru64 UNIX 5.2 Installing RTR on Compaq Tru64 UNIX 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. ________________________ Note ________________________ If you are installing from a RIS distribution area, the number of subsets can vary depending on what products are available in the RIS area and how many subsets they have. ______________________________________________________ Full Installation on Compaq Tru64 UNIX 5-9 Full Installation on Compaq Tru64 UNIX 5.2 Installing RTR on Compaq Tru64 UNIX 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: 5-10 Full Installation on Compaq Tru64 UNIX Full Installation on Compaq Tru64 UNIX 5.2 Installing RTR on Compaq Tru64 UNIX 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. Full Installation on Compaq Tru64 UNIX 5-11 Full Installation on Compaq Tru64 UNIX 5.3 After Installation on Compaq Tru64 UNIX 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: o Starts RTR and creates a facility o Creates an RTR journal o Creates an RTR facility o Stops RTR o 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 5-12 Full Installation on Compaq Tru64 UNIX Full Installation on Compaq Tru64 UNIX 5.3 After Installation on Compaq Tru64 UNIX 4. Look for the word "installed" in the listing produced, and then delete the installed subsets. For example: # setld -d RTRBASE320 5.3.3 Displaying Documentation from CD-ROM 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 Full Installation on Compaq Tru64 UNIX 5-13 Full Installation on Compaq Tru64 UNIX 5.4 Files Installed on Compaq Tru64 UNIX 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 5-14 Full Installation on Compaq Tru64 UNIX Full Installation on Compaq Tru64 UNIX 5.4 Files Installed on Compaq Tru64 UNIX -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 Full Installation on Compaq Tru64 UNIX 5-15 Full Installation on Compaq Tru64 UNIX 5.4 Files Installed on Compaq Tru64 UNIX /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 5-16 Full Installation on Compaq Tru64 UNIX Full Installation on Compaq Tru64 UNIX 5.4 Files Installed on Compaq Tru64 UNIX -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 Full Installation on Compaq Tru64 UNIX 5-17 A _________________________________________________________________ Recovering from Errors 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: o The operating system version is incorrect. o The prerequisite software version is incorrect. o There is insufficient disk space. o 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. Recovering from Errors A-1 Recovering from Errors A.2 Problems After Installation 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: o The name version number of the operating system you are using o The Reliable Transaction Router version number you are using o The hardware system you are using (such as a model number) o A brief description of the problem (one sentence if possible) o Whether or not the problem is critical o 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. A-2 Recovering from Errors B _________________________________________________________________ Using OOR OOR (ODBC over RTR) is a Compaq product that allows you to use ODBC (Open Data Base Connectivity) enabled applications with Reliable Transaction Router. Using OOR, the fault- tolerant features of Reliable Transaction Router can be used with existing applications without re-coding. The OOR kit is now part of the CD-ROM for RTR including documentation and installation instructions for the supported platforms as well as release notes. _________________ Note: New Features _________________ o ODBC translation functionality is now supported. The OOR Setup program now allows a translation option to be specified. o Encoding is now supported. Callouts can be made to an encoding library, which can be written to encode the data in any required format. OOR is now distributed with a compression library, OORCMP, that supports data compression and encryption. ______________________________________________________ B.1 Introduction to ODBC over RTR The OOR product supports a configuration consisting of one or more database servers, and one or more client personal computers. ________________________ Note ________________________ The following description applies to an OOR configuration for ODBC to connect to ORACLE7 databases hosted on OpenVMS/RTR systems. Please contact Compaq Using OOR B-1 Using OOR B.1 Introduction to ODBC over RTR and RTR Engineering for availability information about using OOR with different configurations or with databases from other vendors. ______________________________________________________ The personal computer client requirements: o Any ODBC-enabled application, such as ORACLE Forms (not supplied). o The OOR driver (32 bit). o RTR client software: RTR V3.2 for Windows 95, Windows 98, or Windows NT. o Network transport software, DECnet or TCP/IP. o Microsoft Windows 95, Windows 98, or Windows NT. Database server requirements: o ORACLE database (not supplied). o The OORO7 server; this accesses the ORACLE database and runs as an RTR server application. o Reliable Transaction Router Version 3.2 for Windows NT or Windows 95 or a minimum of Reliable Transaction Router V3.1D, ECO6 for OpenVMS or higher. o OpenVMS VAX or OpenVMS Alpha (includes DECnet). B.1.1 OOR Components OOR is supplied as two components: 1. The OOR driver; this component resides on the PC and requires Reliable Transaction Router V3.2 for Windows NT or Windows 95. The current version of the OOR driver (V1.4) is an ODBC V2.0 driver and is ODBC Level I compliant. 2. The OORO7 server; this is the RTR server component that accesses an ORACLE database. The server is supplied as a kit for OpenVMS Alpha Version 6.1 or higher and OpenVMS VAX 5.5-2 or higher. Prerequisites are a minimum of Reliable Transaction Router Version 3.1D, ECO6, for OpenVMS or higher and ORACLE 7.x. B-2 Using OOR Using OOR B.1 Introduction to ODBC over RTR For OpenVMS Alpha, the minimum supported version of ORACLE is Version 7.1. For OpenVMS VAX, ORACLE V7.0 is the minimum supported version. B.2 Installation Information This section covers installation of the OOR server and the client components. B.2.1 The OORO7 Server Installation Procedure The installation procedure builds a new version of the OORO7 server executable on the target OpenVMS system. B.2.1.1 Before installing the OORO7 Server 1. In order that the installation procedure correctly locates the ORACLE libraries, run the setup command procedure for the ORACLE instance that is running on your system. Typically, this is ORA_ROOT:[DB_ dbname]ORAUSER_dbname.COM. 2. Ensure that any older version of the OORO7 server has been stopped. B.2.1.2 Installing the OORO7 Server The OORO7 server may be installed using an option in the Reliable Transaction Router Version 3.2 for OpenVMS (PCSI) installation. See the Installation Guide Section 1.1 and Chapter 2 for further information. To install the OORO7 server for use with Reliable Transaction Router Version 3.2 without a full RTR installation, use the following instructions. 1. Your server kit is supplied as an installable OpenVMS saveset on CD-ROM. Install the server using the following command: $ PRODUCT INSTALL RTR 2. In response to the POLYCENTER Software Installation prompt that asks you whether to install the ODBC Over RTR Oracle7: Do you want to view the values? [NO] yes Reply with YES. Using OOR B-3 Using OOR B.2 Installation Information 3. Type YES in response to the following prompt: ODBC Over RTR Oracle7 Server: YES 4. Reply with YES to the prompt: Do you want to install the OOR Driver? Yes B.2.2 OOR Client Installation This section gives additional information about installing the OOR driver on a PC. Refer also to the README file and the previous sections of this guide. The OOR driver is delivered on the RTR CD-ROM as an installable kit with the Microsoft ODBC redistributable components and OOR. Five files are supplied for OOR: o OORCMP.DLL o OOROML32.DLL o OORODB32.DLL o OORROT13.DLL o OORSTP32.DLL B.2.2.1 Before Installing the OOR Client Start with operating system software only. Ensure that your network software, RTR client software, Windows NT or Windows 95 are installed, configured and functioning correctly. B.2.2.2 Installing The OOR Client Ensure that you have Administrator privileges on Windows NT systems before installing. 1. Put the CD-ROM in the drive and click on Setup.exe to install. 2. Select Custom Installation followed by ODBC over RTR and follow the instructions. 3. Complete the rest of the installation. B-4 Using OOR Using OOR B.2 Installation Information B.2.2.3 Configuring The OOR Client 1. Select Control Panel followed by ODBC followed by User DSN 2. You are presented with the "Data sources" list box. Add the driver to the Data sources list by selecting it and clicking on the "Add" button. 3. You are then prompted for a data source name and Server access string of the rtr_open_channel call. You can choose only RTR as a data source name. The Server access string must be the same as the access string used on the RTR open channel call. After entering this information, click on OK. B.3 Starting and Configuring the OOR Server Before starting the OOR server: 1. Ensure that RTR Version 3.1D, EC06, is configured and started on your OpenVMS system(s). 2. Ensure that ORACLE7 is configured and started on your OpenVMS system(s). 3. Create a facility for this application; use the command RTR> CREATE FACILITY {facname} /FRONT={nodename,..} ... Refer to the VMS System Manager's Manual if you need further information. B.3.1 Starting the OOR Server The OORO7 server is started with the command:- $ OORO7V2 Command qualifiers are shown in Table B-1 Using OOR B-5 Using OOR B.3 Starting and Configuring the OOR Server Table_B-1_OORO7_Command_Qualifiers_______________________________ Qualifiers____________Meaning____________________________________ /SHADOW Server type /CONCURRENT Server type (default) /STANDBY Server type If no server type qualifier is specified, a concurrent server is started. Shadow and standby are not defaulted; you can choose on type of server to start for OORO7. To start a pair of shadow servers, specify the /SHADOW qualifier to the OORO7 command when starting the server on each of the nodes in the shadow pair. (The same applies to STANDBY servers.) /FACILITY=facname RTR facility name. Defaults to RTR$DEFAULT_ FACILITY /ACCESS=string Access string parameter for the RTR open channel; default is none. /SERVER=n Server identifier; used as partition key to route messages from the client to the RTR servers for the target database. This value must match the Server entry in the client's ODBC.INI file. Default is 0. /GET_BUFFER=nnn Receive buffer size for server. By default, server pre-allocates 64Kbytes for receiving messages from clients. If the largest message size that can be sent by a client is known, and is well under 64Kbytes, then this parameter can be used to reduce the size of the pre-allocated receive buffer used by the OORO7 server and less memory is used. The OOR driver parameter UserBufferKB determines the maximum size of the messages that can be sent and received by the OOR client. (continued on next page) B-6 Using OOR Using OOR B.3 Starting and Configuring the OOR Server Table_B-1_(Cont.)_OORO7_Command_Qualifiers_______________________ Qualifiers____________Meaning____________________________________ /SEND_BUFFER=nnn Send buffer size for server. By default, the server pre-allocates 64K buffers for reply messages sent from server to client. If the largest message size that can be sent by the server is known, and is well under 64K, then this parameter can be used to reduce the size of the pre-allocated send buffer-less memory is used by the OORO7 server. The OOR driver parameter UserBufferKB determines the maximum size of the messages that can be sent and received by the OOR client. /RTRCHANNELS=nnn Number of RTR channels to open. By default, the server will open one RTR channel. Each RTR channel has a connection to the ORACLE database associated with it. Maximum number of channels is 16. /CONNECT_ By default, OORO7 will connect to the STRING="string" ORACLE database in single-task mode. Using the default connection string (none), only one connection to the database is possible (that is when /RTRCHANNELS=1). The /CONNECT_STRING parameter can be used to connect OORO7 to the database using either dedicated servers (two-task mode) or shared (multithreaded) servers. This gives multiple database connections per OORO7V2 invocation (that is when /RTRCHANNELS is greater than 1). Specify any legal ORACLE connection string as the parameter value. (continued on next page) Using OOR B-7 Using OOR B.3 Starting and Configuring the OOR Server Table_B-1_(Cont.)_OORO7_Command_Qualifiers_______________________ _________________________________________________________________ CONNECT_STRING_qualifier_examples________________________________ /CONNECT=2:[mbx_ Connects using mailbox driver (dedicated size] servers). The optional mbx_size specifies the size of the mailbox buffer (standard connect string using mailboxes) and defaults to the ORACLE default is (currently 512). /CONNECT=listener_ Connects using listener name defined in name LISTENER.ORA. /CONNECT=T:nodename Connects using TCP/IP to SQL*Net listener on node nodename. /CONNECT=(multi- threaded_server_ connect_string) Note that OORO7V2 always connects using default username and password verified by the operating system. By default, default username connections are disabled using SQL*Net, thus the only type of connections to use for OORO7V2 are the mailbox driver or the multithreaded server specification. _________________________________________________________________ /USERNAME=username Username to log on to the ORACLE database. This must be a valid ORACLE username. /PASSWORD=password Password for logging on to the ORACLE database. /ENCODE=encoding_ OORCMP is distributed as part of the library installation kit and can be specified to perform compression on incoming, outgoing or both types of messages. Use this to improve performance where RTR is configured in a WAN environment. If this option is used, then OOR clients must also be configured with the same encoding option ______________________enabled.___________________________________ Starting the server by entering the command OORO7 with no qualifiers on the command line starts the server using the B-8 Using OOR Using OOR B.3 Starting and Configuring the OOR Server default configuration. This is equivalent to executing the following command: $ OORO7V2/FACILITY=RTR$DEFAULT_FACILITY/NOACCESS/SERVER=0/CONCURRENT/NOSHADOW - _$ /NOSTANDBY/GET_BUFFER=64000/SEND_BUFFER=64000/RTRCHANNEL=1/V2 - _$ /NOCONNECT_STRING/NOUSERNAME/NOPASSWORD/NOENCODE If no username or password is specified, then the OORO7V2 server must be started from an account that has been set up with proxy access to the ORACLE database. That is, the server will attempt to connect to the database using the connect string "/". This means that a user account with the name "OPS$username" must have been set up in the ORACLE database; username is the OpenVMS username of the account that is used to run the server. In this case, the authorization for the ORACLE account must be "identified externally". Using the /USERNAME and /PASSWORD qualifiers, it is possible to specify explicitly the username and password for use when connecting to the ORACLE database. However, to automate server start-up using command procedures, it may be necessary to write the password in the command file itself. This practice is not recommended and one should generally use external authorization when connecting to the ORACLE database. Nevertheless, the option is available to specify username and password on the command line, or to use default authorization using the operating system authorization. It is up to the system administrator to choose the most appropriate method for any particular installation. B.4 Configuring OOR Clients The following sections provide information about client configuration and optimizing personal computer memory usage including the following: o Contents of ODBC.INI file o Changing Global Options o Optimizing OOR Performance and Memory Usage o General and late-breaking information about configuring is given in the README file for OOR on the RTR CD-ROM. Using OOR B-9 Using OOR B.4 Configuring OOR Clients B.4.1 Contents of the ODBC.INI File The example shows a typical configuration defined for OOR in \WINNT\ODBC.INI. These parameters are automatically written to the file when a data source is added. The section [Oracle RTR] is an example of an entry that is added after a data source has been added. ________________________ Note ________________________ Parameter name entries in Windows initialization files (.INI) are case-independent, but parameter values are case-sensitive for example Password=ORACLE. ______________________________________________________ [ODBC 32 Bit Data Sources] Oracle RTR =ODBC Over RTR (32 bit) [Oracle RTR] Driver=D:\RTR\oorodb32.dll Description=This is a valid description UserName=ORACLE Password=ORACLE Facility=RTRODBC Access=ODBCOVERRTR Server=2 The parameters in the section [ODBC Over RTR] are common to all data sources using the OORODBC driver and are written to \WINNT\ODBCINST.INI. The default settings if using RTR Version 3.2 Client are as follows: [ODBC Over RTR] WBUFSIZE=2000 RBUFSIZE=2000 USERBUFFERKB=9 AUTHORIZE=FALSE ASYNCHRONOUS=FALSE ENCODE= B-10 Using OOR Using OOR B.4 Configuring OOR Clients Table B-2 describes each of the entries in ODBC.INI for OOR is given in . Table_B-2_ODBC.INI_Entries_________________________________ Entry_________________Description__________________________ Driver=OORODBC.DLL Path/name of the RTR ODBC driver. Do not change this entry. Facility=RTRODBC The RTR facility name. Default is RTR$DEFAULT_FACILITY. Access=ACCESSSTR Required if the /ACCESS parameter is specified for the OORO7 server. ACCESSSTR is the ACCESS parameter required for the RTR open channel call. Case-sensitive. Server=2 Must match /SERVER parameter for the OORO7V2 server. Default is Zero. Description=My A user-specified description for the Description data source. Defaults to "ODBC Over ______________________RTR_Driver"._________________________ When adding an ODBC data source for the ODBC Over RTR driver, the minimum information that must be supplied is the data source name. The other fields default as follows: [data_source_name] Driver=D:\RTR\oorodb32.dll Description=ODBC Over RTR UserName= Facility=RTR$DEFAULT_FACILITY Access= Server=0 B.4.2 Changing Global Options When changing global options (the section [ODBC OVER RTR] in ODBCINST.INI) close all applications using OOR and restart them (effectively, the OOR driver is reloaded; it is at this time that the ODBCINST.INI is read). If changing only the datasource parameters (in ODBC.INI), then the new parameters take effect the next time that datasource is selected for an application. Using OOR B-11 Using OOR B.4 Configuring OOR Clients B.4.3 Optimizing OOR Performance and Memory Usage The performance of the OOR driver can be optimized by setting various parameters which define the buffer sizes used in the driver. The optimal settings for these parameters depend on the memory configuration of the PC and the configuration of RTR. The following information describes optimizations when running the OOR driver with Reliable Transaction Router for Windows NT or Windows 95. The internal cache table size can be changed using ODBC setup from the Control Panel and modifying the global options parameter "Cache Size (KBytes)". Keep in mind that the internal cache table size equals the RTR DEQ BUFFER SIZE which in turn equals 64 KBytes. The default internal cache table size is 2000 KBytes. B.5 Using the ORACLE Database With OOR This section provides important information about using an ORACLE database with OOR and ODBC including the following: o Defining the ORACLE System ID Names o No Server Available Behavior o Autocommit Behavior o Values Returned by SqlGetInfo o Using the Cursor Library o Setting Session Characteristics o Using PL/SQL Procedures B.5.1 Defining ORACLE System ID Names When defining a System ID (SID) name for the ORACLE database, do not use a name equivalent to a node name, or a name corresponding to an image name in SYS$SYSTEM. If an SQL*Net listener is started for this SID, then the listener will define a system-wide logical name equivalent to the SID. This can have unpleasant effects on other applications or users. More specifically, the listener will create a system-wide logical name for each IPC keyword defined in the address list for the listener (as defined by LISTENER.ORA). B-12 Using OOR Using OOR B.5 Using the ORACLE Database With OOR B.5.2 No Server Available Behavior If an ODBC application tries to open an RTR channel (SQLConnect, SQLDriverConnect) while there is no RTR server (for any key range) declared on the facility then the application will receive a notification that no server has been declared. If at least one server (any key-range) has been started for this facility, then the connect will succeed. B.5.3 Autocommit Behaviour Autocommit mode on the ORACLE database is disabled automatically by the OORO7V2 server at startup. The server itself will never be in autocommit mode. (Most ODBC applications on the client side disable autocommit at startup.) Normal behaviour (autocommit disabled) means that the OOR ODBC driver only issues an RTR Commit or Abort when the application calls SqlTransact(). If an application enables autocommit, then the OOR ODBC driver issues an RTR Commit after every logical database operation (for example, SqlParse() followed by SqlExecute()). Applications normally will not enable autocommit, since it means that they cannot maintain a cursor context in the database. However, some interactive SQL tools (used mainly for database maintenance, such as DDL, Data Definition Language) allow autocommit to be enabled. (For example, ORACLE's UBT enables autocommit if the command "SET AUTOCOMMIT ON" is entered, whereas ORACLE's SQL*Plus does not.) Note that errors will result if applications enable autocommit and attempt to maintain cursor context across successive database operations. B.5.4 Values Returned by SqlGetInfo() Section B.5.4 lists the parameter values returned by the ODBC call SqlGetInfo. Using OOR B-13 Using OOR B.5 Using the ORACLE Database With OOR Table_B-3_Values_Returned_by_SqlGetInfo____________________ Parameter____________________Value_________________________ SQL_DRIVER_ODBC_VER 02.00 SQL_CURSOR_COMMIT_BEHAVIOR SQL_CB_PRESERVE SQL_CURSOR_ROLLBACK_ SQL_CB_PRESERVE BEHAVIOR SQL_IDENTIFIER_CASE SQL_IC_MIXED SQL_ACTIVE_STATEMENTS 4 SQL_ODBC_API_CONFORMANCE SQL_OAC_LEVEL2 SQL_ODBC_SQL_CONFORMANCE SQL_OSC_CORE SQL_TXN_CAPABLE SQL_TC_DML SQL_SCROLL_CONCURRENCY 0x01000000 SQL_DRIVER_NAME OORODBC.DLL SQL_DBMS_NAME ODBC Over RTR SQL_DBMS_VER_________________1.4.629_______________________ B.5.5 Using the Cursor Library The OOR ODBC driver connect option SQL_ODBC_CURSORS is set to SQL_CUR_USE_ODBC. Attempting to change this with a call to SQLSetConnectOption is not supported and will return the message "Driver not capable". This ensures that the Driver Manager loads and uses the ODBC Cursor Library for functions requiring use of the cursor such as SQLExtendedFetch. B.5.6 Setting Session Characteristics The implementation model used by OOR is that there is an OORO7 server process continuously running on the host with access to the ORACLE database. (This process is an RTR server application.) The OORO7 server process establishes a connection to the database using a valid username and password when it is started, and maintains the same connection for the life of the process. When an OOR client (ODBC application under Windows) starts, it initiates an ODBC session by calling SQLConnect(); this opens an RTR client channel. All ODBC calls made by the application are subsequently converted to SQL and sent through RTR to the OORO7 server running on the host. They B-14 Using OOR Using OOR B.5 Using the ORACLE Database With OOR are then executed by the database running on the host. The the client application is accesses the database on the host (with the username under which the RTR server is running on the host). This model allows many OOR client applications to access one RTR server on the host, and all clients access the database as the user under which the RTR server is running. Thus, care should be taken if setting session-specific characteristics. These are set for the session that the RTR server has made to the database, and they are valid for every client that makes a connection to this server. For example, using SQL*Plus: SQL> ALTER SESSION SET SQL_TRACE=TRUE; This command enables tracing; since the command is executed on the session established by the RTR server on the database, it means tracing will remain in effect for every client that connects to the RTR server until a client specifically disables it. Typically, an OOR configuration is set up so that a normal unprivileged user would not be able to modify session characteristics. A server running on behalf of the database administrator (DBA) can be set up to handle database specific requests (for example, ALTER SYSTEM) that would not normally be available to the unprivileged user. B.5.7 Using PL/SQL Procedures When writing PL/SQL procedures for execution on the OOR server do not use the characters ":" or "?" within the comments. This is because the OOR driver would interpret these as placeholders for variables and the command to fail. For example: create table gc__charting ( owner varchar(30), /* owner ID */ x1_axis_type integer, /* axis data type:, date, or discr */ x1_scale_fnc integer /* scale function?, log, pct */ ) Using OOR B-15 Using OOR B.5 Using the ORACLE Database With OOR This will be interpreted by the OOR driver as: create table gc__charting ( owner varchar(30), /* owner ID */ x1_axis_type integer, /* axis data type:C1 , date, or discr */ x1_scale_fnc integer /* scale function:C2 , log, pct */ ) The OOR server will parse this statement, and then attempt to do a describe of columns C1 and C2, which will fail. B.5.8 Changes and Corrections o This version of OOR contains extensive optimizations that increase performance in a WAN environment. o The section [ODBC Over RTR] has been removed from ODBC.INI and merged with the same section in ODBCINST.INI. The section is now removed correctly if the OOR driver is removed. If you have been using a previous version of the OOR driver, then before running this version of the OOR driver, copy the section [ODBC Over RTR] from ODBC.INI to ODBCINST.INI and delete the section from ODBC.INI. o The CLOSE CURSOR calls sometimes resulted in cursors being left open on the OORO7 server, which could cause it to crash. This has now been fixed. o The install procedure on OpenVMS also installs a map file SYS$SYSTEM:OORO7V2.MAP. o A crash could sometimes occur if an ODBC application (illegally) called SQLParse with an SQL string of "COMMIT" or "ROLLBACK", due to a column variable not being initialized properly (for example, ORACLE's SQLPlus). This has been fixed. o Changes In OOR Driver Setup:- - The default values for configurable parameters are suitable for Reliable Transaction Router Version 3.1D, EC06. - The "Asynchronous" (global) option has been removed. - "Cache Size" has been added to the global option configurable parameters. B-16 Using OOR Using OOR B.5 Using the ORACLE Database With OOR - The (undocumented) TRACE=ALL keyword has been moved to [ODBC Over RTR] in ODBCINST.INI. - Problems with the usage of SQL functions CHR() and ASCII() when a translation DLL is specified have been fixed. B.5.9 OOR Restrictions User authorization is not supported. The impact of this is that anything typed in to the username and password fields is ignored for connection. However, the fields are used as an (implicit) qualifier when selecting tables by name, for example. Using OOR B-17