DEC_Reliable_Transaction_Router_for_OpenVMS_________ Installation Guide Order Number: AA-PHWJD-TE September 1993 This manual describes how to install the DEC Reliable Transaction Router for OpenVMS. Revision/Update Information: This revised manual supersedes the DEC Reliable Transaction Router for OpenVMS Installation Guide, Version 2.0-2. Operating System and Version: OpenVMS Version 5.2 to 6.0 Software Version: DEC Reliable Transaction Router for OpenVMS, Version 2.1 Digital Equipment Corporation Maynard, Massachusetts ________________________________________________________________ August 17, 1993 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. © Digital Equipment Corporation 1989 - 1993. All Rights Reserved. Printed in Galway, Ireland The following are trademarks of Digital Equipment Corporation: DEC, DECnet, Digital, DNA, OpenVMS, PATHWORKS, Rdb/VMS, Reliable Transaction Router, VAX, VAX Document, VAX Pascal, VAX RMS, VAX Volume Shadowing, VMS, VMS logo, and the DIGITAL Logo. This document was prepared using VAX DOCUMENT, Version 2.1. _________________________________________________________________ Contents Preface................................................... v 1 Preparing for Reliable Transaction Router for OpenVMS Installation 1.1 Required Operating System Components.......... 1-1 1.2 Prerequisite and Optional Software............ 1-2 1.3 License Registration.......................... 1-2 1.4 Installation Procedure Requirements........... 1-3 1.4.1 Privileges and Disk Space................. 1-3 1.4.2 System Parameters......................... 1-4 1.4.2.1 Checking System Parameter Values........ 1-5 1.4.2.2 Calculating the Values for GBLPAGES and GBLSECTIONS............................. 1-5 1.4.2.3 Changing System Parameter Values with AUTOGEN................................. 1-6 1.4.3 Process Account Quotas.................... 1-7 1.4.4 VMSINSTAL Requirements.................... 1-8 1.4.5 Backing Up Your System Disk............... 1-9 1.4.6 Reliable Transaction Router for OpenVMS Requirements.............................. 1-9 2 Installing Reliable Transaction Router for OpenVMS 2.1 The Installation Procedure.................... 2-1 2.1.1 Log on to the Systems Manager's Account... 2-1 2.1.2 Invoke VMSINSTAL.......................... 2-1 2.1.3 Confirm Running Processes................. 2-2 2.1.4 Confirm system backup..................... 2-3 2.1.5 Mount the media........................... 2-3 2.1.6 Product Name and Options.................. 2-3 2.1.7 Product Name and Options Confirmation..... 2-4 2.1.8 Beginning Installation.................... 2-4 iii 2.1.9 Accessing Release Notes................... 2-5 2.1.10 Purge files............................... 2-5 2.1.11 Choose the IVP? .......................... 2-6 2.1.12 Respond to license type request........... 2-6 2.1.13 Respond to license registration queries... 2-6 2.1.14 Run-time Support Only..................... 2-7 2.1.15 Read informational messages............... 2-7 2.1.16 End the installation procedure............ 2-8 2.1.17 Log out of the Systems Manager's Account................................... 2-8 3 After Installing Reliable Transaction Router for OpenVMS 3.1 Running the Installation Verification Procedure Separately.......................... 3-1 3.2 Editing the System Files...................... 3-1 3.3 Modifying RTR Startup Files................... 3-2 3.4 Creating the RTR journal...................... 3-2 3.5 VAXcluster Considerations..................... 3-3 3.6 User Account Requirements..................... 3-3 3.6.1 Quotas.................................... 3-3 3.6.2 Privileges................................ 3-4 3.7 Error Conditions.............................. 3-4 3.8 Reporting Problems............................ 3-4 A Sample Installation B Sample Startup B.1 RTR$STARTUP.COM............................... B-1 B.2 RTR$NODE_SPECIFIC_STARTUP_TEMPLATE.COM........ B-3 C Files modified during the RTR installation iv Tables 1-1 Prerequisite and Optional Software........ 1-2 1-2 Disk Space Requirements................... 1-3 1-3 Minimum Required System Parameter Values.................................... 1-4 1-4 Process Account Quotas for the Installing Account................................... 1-7 3-1 User Account Quotas for Using Reliable Transaction Router for OpenVMS............ 3-3 C-1 Files modified during RTR installation.... C-2 v _________________________________________________________________ Preface Purpose of this manual This manual describes how to install DEC Reliable Transaction Router for OpenVMS. Intended Audience The manual is intended for system managers who install the Reliable Transaction Router for OpenVMS software on VAX/VMS systems. Structure of this Document This manual is organized as follows: o Chapter 1 describes the operating system and hardware requirements for the installation, and the procedures that must be completed before installing the software. o Chapter 2 describes the installation procedure. o Chapter 3 describes the actions necessary after a successful installation. o Appendix A contains a sample listing of an installation. o Appendix B describes a sample startup file. o Appendix C describes the files modified and added during the installation. v Related documentation o DEC Reliable Transaction Router for OpenVMS Release Notes o DEC Reliable Transaction Router for OpenVMS Application Programmer's Reference Manual o DEC Reliable Transaction Router for OpenVMS System Manager's Manual vi Conventions The following conventions are used in this guide: Conventions ___________________________________________________________ Convention________Meaning__________________________________ Ctrl/x A sequence such as Ctrl/x indicates that you must hold down the key labeled Ctrl while you press another key or a pointing device button. In examples, a key name enclosed in a box indicates that you press a key on the keyboard. (In text, a key name is not enclosed in a box.) . . . A horizontal ellipsis in examples indicates one of the following possibilities: o Additional optional arguments in a statement have been omitted. o The preceding item or items can be repeated one or more times. o Additional parameters, values, or other information can be entered. A vertical ellipsis indicates the . omission of items from a code example . or command format; the items are omitted . because they are not important to the topic being discussed. ( ) In format descriptions, parentheses indicate that, if you choose more than one option, you must enclose the choices in parentheses. vii ___________________________________________________________ Convention________Meaning__________________________________ [ ] In format descriptions, brackets indicate optional elements. You can choose one, none, or all of the options. (Brackets are not optional, however, in the syntax of a directory name in a VMS file specification, or in the syntax of a substring specification in an assignment statement.) { } In format descriptions, braces surround a required choice of options; you must choose one of the options listed. boldface text Boldface text represents the introduction of a new term or the name of an argument, an attribute, or a reason. Boldface text is also used to show user input in online versions of the manual. italic text Italic text emphasizes important information, indicates variables, and indicates complete titles of manuals. Italic text also represents information that can vary in system messages (for example, Internal error number), command lines (for example, /PRODUCER=name), and command parameters in text. UPPERCASE TEXT Uppercase text indicates a command, the name of a routine, the name of a file, or the abbreviation for a system privilege. - A hyphen in code examples indicates that additional arguments to the request are provided on the line that follows. numbers All numbers in text are assumed to be decimal, unless otherwise noted. Nondecimal radixes-binary, octal, or __________________hexadecimal-are_explicitly_indicated.____ viii 1 _________________________________________________________________ Preparing for Reliable Transaction Router for OpenVMS Installation Before you start the installation procedures decribed in Chapter 2, you must complete the preparation tasks outlined in this chapter. This chapter describes the following: o The OpenVMS classes required to install Reliable Transaction Router for OpenVMS o The prerequisite and optional software required for installing Reliable Transaction Router for OpenVMS o How to register your License Product Authorization Key (PAK) o Ensuring that your SYSGEN parameters will allow Reliable Transaction Router for OpenVMS to install Reliable Transaction Router for OpenVMS provides online release notes. Digital strongly recommends that you read the release notes before proceeding with the installation. For information on accessing the online release notes, see Section 2.1. 1.1 Required Operating System Components The OpenVMS operating system comes with a variety of support options, or classes. Classes include such features as networking and RMS journaling. For a complete list of the required classes, see the System Support Addendum (SSA), which comes with the Software Product Description (SPD). Preparing for Reliable Transaction Router for OpenVMS Installation 1-1 Preparing for Reliable Transaction Router for OpenVMS Installation 1.2 Prerequisite and Optional Software 1.2 Prerequisite and Optional Software Table 1-1 provides information on the software that must be installed on your system before installing Reliable Transaction Router for OpenVMS. The table also includes information about optional software that you can use with Reliable Transaction Router for OpenVMS. The System Support Addendum (SSA) contains a complete list of prerequisite and optional software and their required version numbers. Table_1-1_Prerequisite_and_Optional_Software_______________ Prerequisite_Products______Purpose_________________________ OpenVMS Version 5.2 to System Software 6.0 DECnet-VAX Version 5.0 Network Communications to 5.5 or DECnet/OSI for OpenVMS Version 5.6 ___________________________________________________________ Optional_Products__________Purpose_________________________ DEC TCP/IP Services for TCP/IP Connection for Desktop VMS Products Pathworks for DOS Connection for Desktop Products A_VAX_Language_Compiler____Application_Development_________ 1.3 License Registration You must register and load your license for Reliable Transaction Router for OpenVMS before you start the installation in order to run the Installation Verification Procedure (IVP) and use the software. To register a license under VMS, 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. 1-2 Preparing for Reliable Transaction Router for OpenVMS Installation Preparing for Reliable Transaction Router for OpenVMS Installation 1.3 License Registration 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 for OpenVMS on more than one node in a VAXcluster, you will need to perform a license load on the other nodes after you complete this installation (or reboot the VAXcluster). See Section 3.5. For complete information on using LMF, see the VMS License Management Utility Manual. 1.4 Installation Procedure Requirements Installing Reliable Transaction Router for OpenVMS and running the Installation Verification Procedure (IVP) on a standalone VAX system takes approximately ten minutes. 1.4.1 Privileges and Disk Space Reliable Transaction Router for OpenVMS's requirements for free disk storage space are different during installation and after installation. Table 1-2 summarizes the storage requirements. Table_1-2_Disk_Space_Requirements__________________________ Blocks During Blocks After Kit______________Installation__________Installation________ Reliable 20000 12000 Transaction Router for OpenVMS Version 2.1, including development support files (continued on next page) Preparing for Reliable Transaction Router for OpenVMS Installation 1-3 Preparing for Reliable Transaction Router for OpenVMS Installation 1.4 Installation Procedure Requirements Table_1-2_(Cont.)_Disk_Space_Requirements__________________ Blocks During Blocks After Kit______________Installation__________Installation________ Reliable 15000 7000 Transaction Router for OpenVMS Version 2.1, Run-time files_only_________________________________________________ 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 To install Reliable Transaction Router for OpenVMS successfully, your account must have SYSPRV, and either the OPER privilege or the RTR$OPERATOR rights identifier. Use the VMS Authorize Utility to determine whether you have these required privileges. 1.4.2 System Parameters Installing Reliable Transaction Router for OpenVMS requires certain system parameter settings. Table 1-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_1-3_Minimum_Required_System_Parameter_Values_________ System_Parameter___________Minimum_Value___________________ GBLPAGES 1200 + CACHE_PAGES [1] GBLPAGFIL Same as GBLPAGES GBLSECTIONS 20 [1]CACHE_PAGES_is_a_start-up_parameter_for_Reliable________ Transaction Router for OpenVMS; default 1024 ___________________________________________________________ The following sections show you how to: o Check system parameter values 1-4 Preparing for Reliable Transaction Router for OpenVMS Installation Preparing for Reliable Transaction Router for OpenVMS Installation 1.4 Installation Procedure Requirements o Calculate values for the GBLPAGES and GBLSECTIONS system parameters o Change parameter values with the VMS AUTOGEN command procedure 1.4.2.1 Checking System Parameter Values To check the values of your system parameters, enter the following command at the DCL prompt to invoke the System Generation Utility (SYSGEN): $ RUN SYS$SYSTEM:SYSGEN SYSGEN> At the SYSGEN> prompt, enter the SHOW command to display the value of a system parameter. The values displayed should equal or exceed the value of each system parameter listed in Table 1-3. The following example displays the value for the GBLPAGFIL system parameter: SYSGEN> SHOW GBLPAGFIL After checking the parameters with the SHOW command, enter the EXIT command at the SYSGEN> prompt to return to DCL level. SYSGEN> EXIT $ You may also use the following command to display the GBLPAGFIL system parameter: $ WRITE SYS$OUTPUT F$GETSYI("GBLPAGFIL") 65000 1.4.2.2 Calculating the Values for GBLPAGES and GBLSECTIONS To install and run Reliable Transaction Router for OpenVMS, you must have sufficient free global pages and global sections. You must first find out how many free global pages and sections you have on your system. Then use AUTOGEN if you need to increase the GLBPAGES and GBLSECTIONS system parameters. You can use the WRITE command with the F$GETSYI lexical function to find the number of free global pages and global sections. The following example shows how to get this information at your terminal (the default for SYS$OUTPUT): Preparing for Reliable Transaction Router for OpenVMS Installation 1-5 Preparing for Reliable Transaction Router for OpenVMS Installation 1.4 Installation Procedure Requirements $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES") 15848 $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS") 24 If the values displayed by the system are greater than the values in Table 1-3, you do not need to increase the values for these parameters. If the value of free global pages or global sections is less than the value in Table 1-3, you must increase the system parameter setting. Section 1.4.2.3 describes the procedures for increasing these values using AUTOGEN. 1.4.2.3 Changing System Parameter Values with AUTOGEN Use the AUTOGEN command procedure to change system parameters. AUTOGEN automatically adjusts values for parameters that are associated with the values you reset manually. To change system parameters with AUTOGEN, edit the following file: SYS$SYSTEM:MODPARAMS.DAT Use an editor to access the file. To change a parameter value listed in this file, delete the current value associated with that parameter and enter the new value. To add a new parameter, add a line to the file that includes both the name of the parameter and its value. For example: WSMAX = 1024 To modify incremental parameters such as GBLPAGES and GBLSECTS, use ADD_. The following example increases the global page setting by 2000: ADD_GBLPAGES = 2000 Note that when you set the page file quota, do not use a value that exceeds the amount of page file space available on the system. After you make all your changes, exit from the editor and execute the AUTOGEN procedure to recalculate your system parameters. Enter the following command at the DCL prompt: $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT 1-6 Preparing for Reliable Transaction Router for OpenVMS Installation Preparing for Reliable Transaction Router for OpenVMS Installation 1.4 Installation Procedure Requirements When you specify REBOOT, AUTOGEN performs an automatic system shutdown and then reboots the system. Any users logged on to the system are immediately disconnected during the shutdown. The automatic reboot puts the new parameter values into effect. The AUTOGEN Utility automatically adjusts some of the SYSGEN parameters based on the consumption of resources since the last reboot. If you do not want to take advantage of this automatic adjustment, include the NOFEEDBACK qualifier on the AUTOGEN command line. For more information about using AUTOGEN, see the Guide to Setting Up a VMS System. 1.4.3 Process Account Quotas The account you use to install Reliable Transaction Router for OpenVMS must have sufficient quotas to enable you to perform the installation. Table 1-4 summarizes the process quotas required for the installation account. (The installation account will usually be SYSTEM.) Table_1-4_Process_Account_Quotas_for_the_Installing_Account Account_Quota____Value_____________________________________ ASTLM 24 BIOLM 18 BYTLM 18000 DIOLM 18 ENQLM 30 FILLM 20 PGFLQUO__________20000_____________________________________ User account quotas are stored in the file SYSUAF.DAT. Use the VMS Authorize Utility (AUTHORIZE) to verify and change user account quotas. First set your directory to SYS$SYSTEM and then run AUTHORIZE: $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> Preparing for Reliable Transaction Router for OpenVMS Installation 1-7 Preparing for Reliable Transaction Router for OpenVMS Installation 1.4 Installation Procedure Requirements At the UAF> prompt, enter the SHOW command with an account name to check a particular account. For example: UAF> SHOW SMITH To change a quota, enter the MODIFY command. The following example changes the FILLM quota for the SMITH account and then exits from the utility: UAF> MODIFY SMITH /FILLM=50 UAF> EXIT After you exit from the utility, the system displays messages indicating whether or not changes were made. Once the changes have been made, you must log out and log in again for the new quotas to take effect. For more information on modifying account quotas, see the description of the Authorize Utility in the VMS System Manager's Manual. 1.4.4 VMSINSTAL Requirements When you invoke VMSINSTAL, it checks the following: o Whether you have set your default device and directory to SYS$UPDATE o Whether you are logged in to a privileged account o Whether you have adequate quotas for installation o Whether any processes are running o Whether any users are logged in to the system Note that the VMSINSTAL requires that the installation account have a minimum of the quotas shown in Table 1-4. If VMSINSTAL detects any problems during the installation, it notifies you and asks if you want to continue the installation. In some instances, you can enter YES to continue. To stop the installation process and correct the situation, enter NO or press RETURN. Then correct the problem and restart the installation. 1-8 Preparing for Reliable Transaction Router for OpenVMS Installation Preparing for Reliable Transaction Router for OpenVMS Installation 1.4 Installation Procedure Requirements 1.4.5 Backing Up Your System Disk At the beginning of the installation, VMSINSTAL asks if you have backed up your system disk. Digital recommends that you do a system disk backup before installing any software. Use the backup procedures that are established at your site. For details on performing a system disk backup, see the section on the Backup Utility in the VMS System Manager's Manual. 1.4.6 Reliable Transaction Router for OpenVMS Requirements The installation procedure for Reliable Transaction Router for OpenVMS checks to ensure the correct minimum applicable version of VMS is installed. Preparing for Reliable Transaction Router for OpenVMS Installation 1-9 2 _________________________________________________________________ Installing Reliable Transaction Router for OpenVMS This chapter explains how to install Reliable Transaction Router for OpenVMS. Section 2.1 contains a step-by-step description of the installation procedure. 2.1 The Installation Procedure The Reliable Transaction Router for OpenVMS installation procedure consists of a series of questions and informational messages. See Appendix A for a sample installation. Before you start, read Chapter 1, which describes the general options and requirements that apply to installing Reliable Transaction Router for OpenVMS. To abort the installation procedure at any time, press Ctrl/Y. When you press Ctrl/Y, the installation procedure deletes all files it has created up to that point and exits. You can then start the installation again. 2.1.1 Log on to the Systems Manager's Account It is recommended to log on to the System Manager's account to do the installation. 2.1.2 Invoke VMSINSTAL To start the installation, invoke the VMSINSTAL command procedure from a privileged account, such as the SYSTEM account. VMSINSTAL is in the SYS$UPDATE directory. You may enter parameters to the command procedure as shown below; if you omit them, VMSINSTAL prompts you for the information. @SYS$UPDATE:VMSINSTAL saveset-name device-name OPTIONS N Installing Reliable Transaction Router for OpenVMS 2-1 Installing Reliable Transaction Router for OpenVMS 2.1 The Installation Procedure The N option allows you to print or view the release notes. You should read the release notes before completing the installation. The following list defines the parameters of the VMSINSTAL command procedure: saveset-name The installation name for the component. For Reliable Transaction Router for OpenVMS, use the following installation name: RTRSFT021 device-name The name of the device on which you plan to mount the media. For example, MUA0: is the device name for a tape drive. The following example invokes VMSINSTAL to install Reliable Transaction Router for OpenVMS from tape drive MUA0: and shows the system response. $ @SYS$UPDATE:VMSINSTAL RTRSFT021 MUA0: OPTIONS N VAX/VMS Software Product Installation Procedure V5.5 It is 2-FEB-1993 at 14:08. Enter a question mark (?) at any time for help. If you do not supply either the product name or the device name, VMSINSTAL prompts you for this information later in the installation procedure. 2.1.3 Confirm Running Processes %VMSINSTAL-W-ACTIVE, The following processes are still active: _VTA108: * Do you want to continue anyway [NO]? VMSINSTAL displays a list of all active processes. It then asks if you want to continue the installation. _______________________ Caution _______________________ You should not install Reliable Transaction Router for OpenVMS on a system that has RTR running. If you have 2-2 Installing Reliable Transaction Router for OpenVMS Installing Reliable Transaction Router for OpenVMS 2.1 The Installation Procedure a VAXcluster environment, ensure that RTR is stopped on all nodes in the cluster. ______________________________________________________ NO is the default response to the question. 2.1.4 Confirm system backup * Are you satisfied with the backup of your system disk [YES]? VMSINSTAL asks if you are satisfied with your system backup. You should always back up your system disk before performing an installation. If you are satisfied with the backup of your system disk, press RETURN. Otherwise, enter NO to discontinue the installation. After you back up your system disk, you can restart the installation. 2.1.5 Mount the media * Where will the distribution volumes be mounted: MUA0: This question is omitted if you entered the device name as a parameter to the VMSINSTAL command. 2.1.6 Product Name and Options Enter the products to be processed from the first distribution volume set. * Products: RTRSFT021 * Enter installation options you wish to use (none): These questions are omitted if you entered the saveset name and options on the VMSINSTAL command. Installing Reliable Transaction Router for OpenVMS 2-3 Installing Reliable Transaction Router for OpenVMS 2.1 The Installation Procedure 2.1.7 Product Name and Options Confirmation The following products will be processed: RTRSFT V2.1 2.1.8 Beginning Installation Beginning installation of RTRSFT V2.1 at 14:17 %VMSINSTAL-I-RESTORE, Restoring product saveset A... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP Copyright Digital Equipment Corporation 1988,1993. 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 Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. 2-4 Installing Reliable Transaction Router for OpenVMS Installing Reliable Transaction Router for OpenVMS 2.1 The Installation Procedure 2.1.9 Accessing Release Notes Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: You should always read the release notes. If you accept the default to print them, you are prompted for a print queue. * Queue name [SYS$PRINT]: Job RTRSFT (queue PRINT$LN03, entry 929) started on PRINT$LN03 Continue the installation after you have read the release notes. * Do you want to continue the installation [NO]? YES %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. 2.1.10 Purge files * Do you want to purge files replaced by this installation [YES]? You have the option to purge files from previous versions of Reliable Transaction Router for OpenVMS that are superseded by this installation. Purging is recommended; however, if you need to keep files from the previous version, enter NO in response to the question. Installing Reliable Transaction Router for OpenVMS 2-5 Installing Reliable Transaction Router for OpenVMS 2.1 The Installation Procedure 2.1.11 Choose the IVP? * Do you want to run the IVP after the installation [YES]? The installation procedure now asks if you want to run the IVP. The IVP for Reliable Transaction Router for OpenVMS checks to be sure that the installation is successful. It is recommended that you run the IVP. After Reliable Transaction Router for OpenVMS is installed, you can run the IVP independently to verify that the software is available on your system. You might need to run the IVP after a system failure to make sure that users can access Reliable Transaction Router for OpenVMS. 2.1.12 Respond to license type request The RTR SERVER license allows the RTR Client, Router, and Server functionality of RTR to be utilized. The RTR CLIENT license allows only the Client functionality. * Please enter either CLIENT or SERVER for the installation type [SERVER]: Select the appropriate license type. 2.1.13 Respond to license registration queries * Does this product have an authorization key registered and loaded? The installation procedure displays license information about your product and then asks if you have registered and loaded your Product Authorization Key (PAK). If you have not registered and loaded your PAK, you must answer NO to this question. You have to register and load your PAK to successfully complete the installation. If you have not done so, you should stop the installation, register and load your PAK, and then restart the installation. 2-6 Installing Reliable Transaction Router for OpenVMS Installing Reliable Transaction Router for OpenVMS 2.1 The Installation Procedure 2.1.14 Run-time Support Only If you do not intend to do RTR development work, you can limit the installation of RTR to run-time support only. This will prevent the language support files being copied to your system. The default is ALL, which allows both run- time and development support. Please enter either ALL or RUNTIME_ONLY as support type [ALL] : 2.1.15 Read informational messages At this point, the installation procedure displays a number of informational messages that report on the progress of the installation. There are no further questions. If the installation procedure has been successful up to this point, VMSINSTAL moves the new or modified files to their target directories, updates help files, and updates DCL tables, if necessary. If you chose to have files purged, that work is done now. The following messages are displayed: This procedure includes/modifies the following files: All the modified and new files are listed, followed by informational messages. No futher questions will be asked. If you chose to run the IVP, messages associated with the IVP are also displayed. %VMSINSTAL-I-RESTORE, Restoring product save set B ... %VMSINSTAL-I-RESTORE, Restoring product save set C ... Note that the installation copies a number of RTR monitor files to the SYS$SYSTEM directory. As some sites may have customised their monitor display files, these files are not purged by the installation. You may want to do this yourself. The files are named: RTR*.MON. Installing Reliable Transaction Router for OpenVMS 2-7 Installing Reliable Transaction Router for OpenVMS 2.1 The Installation Procedure 2.1.16 End the installation procedure Installation of RTRSFT V2.1 completed at 14:26 Enter the products to be processed from the next distribution volume set. * Products: VMSINSTAL procedure done at 14:27 The previous messages indicate that the entire installation procedure is complete. 2.1.17 Log out of the Systems Manager's Account You can now log out of the privileged account: $ LOGOUT SYSTEM logged out at 2-FEB-1993 at 14:30:47. Note that VMSINSTAL deletes or changes entries in the process symbol tables during the installation. Therefore, if you are going to continue using the system manager's account and you want to restore these symbols, you should log out and log in again. 2-8 Installing Reliable Transaction Router for OpenVMS 3 _________________________________________________________________ After Installing Reliable Transaction Router for OpenVMS This chapter explains what you need to do following the installation to make Reliable Transaction Router for OpenVMS ready for use. o Running the IVP Separately o Editing the system startup and shutdown files. o Modifying the sample Startup command file. o Creating the RTR journal o VAXcluster Considerations o User Account Requirements o Privileges 3.1 Running the Installation Verification Procedure Separately You usually run the Installation Verification Procedure (IVP) during installation. If you want to run the IVP separately to ensure the integrity of installed files should system problems occur, execute the following command procedure: $ @SYS$TEST:RTR$IVP 3.2 Editing the System Files You must edit the system startup and shutdown files to provide for automatic startup and the installation of Reliable Transaction Router for OpenVMS images when your system is rebooted. After Installing Reliable Transaction Router for OpenVMS 3-1 After Installing Reliable Transaction Router for OpenVMS 3.2 Editing the System Files Add the command line that starts Reliable Transaction Router for OpenVMS to the system startup file, SYS$MANAGER:SYSTARTUP_V5.COM. Reliable Transaction Router for OpenVMS cannot start until after the network has started. You must position this new command line after the line that invokes the network startup command procedure. The following example shows the network startup command line followed by the Reliable Transaction Router for OpenVMS startup command line: $ @SYS$MANAGER:STARTNET.COM . . . $ @SYS$STARTUP:RTR$STARTUP.COM 3.3 Modifying RTR Startup Files RTR$STARTUP.COM is placed in SYS$COMMON:[SYS$STARTUP]. You will not normally need to edit this file. RTR$NODE_SPECIFIC_STARTUP_TEMPLATE.COM is provided in the SYS$COMMON:[SYSMGR] directory during the installation. You can use this template as a basis for a node-specific startup procedure. It shows how to issue the START RTR and ADD FACILITY commands that are needed for the applications to run on your system (see DEC Reliable Transaction Router for OpenVMS System Manager's Manual). 3.4 Creating the RTR journal Before RTR can be used, its journal has to be initialized and the location of the journal file(s) specified. To do this, use the RTR CREATE JOURNAL command described in DEC Reliable Transaction Router for OpenVMS System Manager's Manual. For example, the following command will instruct RTR to journal to a disk called MYDISK$: $ RTR CREATE JOURNAL MYDISK$ 3-2 After Installing Reliable Transaction Router for OpenVMS After Installing Reliable Transaction Router for OpenVMS 3.5 VAXcluster Considerations 3.5 VAXcluster Considerations To ensure the successful installation of Reliable Transaction Router for OpenVMS, run RTR$STARTUP.COM on every member of the cluster. If the license PAK has just been registered and the VAXcluster is not being rebooted, it is necessary to load the license on each member of the VAXcluster. This is best done using SYSMAN as follows: $ SYSMAN SYSMAN> SET ENVIRONMENT/CLUSTER SYSMAN> DO LICENSE LOAD RTR-CL or RTR-SVR SYSMAN> EXIT $ 3.6 User Account Requirements To work with Reliable Transaction Router for OpenVMS, user accounts on your system must have certain privileges and quotas. The next two sections contain information on these requirements. 3.6.1 Quotas Table 3-1 summarizes the required user account quotas. Table 3-1 User Account Quotas for Using Reliable __________Transaction_Router_for_OpenVMS___________________ Account_Quota____Value_____________________________________ ASTLM 24 BIOLM 18 BYTLM 18000 DIOLM 18 ENQLM 30 FILLM 20 PGFLQUO__________20000_____________________________________ After Installing Reliable Transaction Router for OpenVMS 3-3 After Installing Reliable Transaction Router for OpenVMS 3.6 User Account Requirements 3.6.2 Privileges To use all the features of Reliable Transaction Router for OpenVMS, each account must have either OPER privilege or the RTR$OPERATOR rights identifier. Use the VMS Authorize Utility to determine whether users have the privileges they require. 3.7 Error Conditions If the installation procedure fails for any reason, the following message is displayed: %VMSINSTAL-E-INSFAIL, The installation of RTRSFT021 V2.1 has failed. Reasons for failure may be any of the following: o Operating system version is incorrect o There is insufficient free space on the system disk o Quotas necessary for successful installation are insufficient o Process quotas required by VMSINSTAL are incorrect o The RTR license has not been installed o The VMS HELP library is currently in use o RTR has not been stopped If you are notified that any of these conditions exist, you should take the appropriate action as described in the message. You may need to change a system parameter or increase an authorized quota value. You should then restart the installation procedure from the beginning. 3.8 Reporting Problems If an error occurs while you are using Reliable Transaction Router for OpenVMS and you believe that the error is caused by a problem with Reliable Transaction Router for OpenVMS, take one of the following actions. o Call Digital if your software contract or warranty agreement entitles you to receive telephone support. 3-4 After Installing Reliable Transaction Router for OpenVMS After Installing Reliable Transaction Router for OpenVMS 3.8 Reporting Problems o If you think the problem is caused by a software error, you can submit a Software Performance Report (SPR). For more information, contact your local Digital representative. After Installing Reliable Transaction Router for OpenVMS 3-5 A _________________________________________________________________ Sample Installation This appendix contains a sample RTR installation session. $ @sys$update:vmsinstal VAX/VMS Software Product Installation Procedure V5.5 It is 16-AUG-1993 at 11:14. Enter a question mark (?) at any time for help. %VMSINSTAL-W-ACTIVE, The following processes are still active: _VTA108: _TWA18: * Do you want to continue anyway [NO]? yes * Are you satisfied with the backup of your system disk [YES]? * Where will the distribution volumes be mounted: MUA0: Enter the products to be processed from the first distribution volume set. * Products: rtrsft021 * Enter installation options you wish to use (none): The following products will be processed: RTRSFT V2.1 Beginning installation of RTRSFT V2.1 at 11:15 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. Copyright Digital Equipment Corporation 1988,1993. All rights reserved. Sample Installation A-1 Sample Installation 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 Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. * Do you want to purge files replaced by this installation [YES]? * Do you want to run the IVP after the installation [YES]? The RTR SERVER license allows the RTR Client, Router, and Server functionality of RTR to be utilized. The RTR CLIENT license allows only the Client functionality * Please enter either CLIENT or SERVER for the installation type [SERVER] : product: RTR-CL Producer: DEC Version: 2.0 Release Date: 7-OCT-1991 * Does this product have an authorization key registered and loaded? YES If you do not intend to do RTR development work, you can limit the installation of RTR to RUNTIME_SUPPORT only. This will prevent the language support files being copied to your system. The default is ALL, which allows both RUNTIME_SUPPORT and development. * Please enter either ALL or RUNTIME_ONLY as support type [ALL]: All This procedure includes/modifies the following files: A-2 Sample Installation Sample Installation SYS$SYSTEM:RTRACP.EXE (new) SYS$SYSTEM:RTRRCHACP.EXE (new) SYS$SYSTEM:RTR.EXE (new) SYS$SYSTEM:RTRCOMSERV.EXE (new) SYS$SYSTEM:RTRCOMSERV.COM (new) SYS$SYSTEM:RTR*.MON (new) SYS$SYSTEM:RTR_START_ACP.COM (new) SYS$SYSTEM:RTR_START_RCHACP.COM (new) SYS$MESSAGE:RTRMSG.EXE (new) SYS$COMMON:[SYS$STARTUP]RTR$STARTUP.COM (new) SYS$MANAGER:RTR$NODE_SPECIFIC_STARTUP_TEMPLATE.COM (new) SYS$MANAGER:RTR$SNAPSHOT.COM (new) SYS$EXAMPLES:RTR$*.* (new) SYS$HELP:HELPLIB.HLB (modified) SYS$HELP:RTRHLP.HLB (new) SYS$TEST:RTR$IVP.COM (new) SYS$LIBRARY:RTRSHR.EXE (new) SYS$LIBRARY:RTRRTL.EXE (new) SYS$LIBRARY:DCLTABLES.EXE (modified) SYS$LIBRARY:RTR.ADA (new) SYS$LIBRARY:RTR.BAS (new) SYS$LIBRARY:RTR.FOR (new) SYS$LIBRARY:RTR.H (new) SYS$LIBRARY:RTR.L32 (new) SYS$LIBRARY:RTR.MLB (new) SYS$LIBRARY:RTR.PAS (new) SYS$LIBRARY:RTR.PEN (new) SYS$LIBRARY:RTR.PLI (new) SYS$LIBRARY:RTR.REQ (new) No further questions will be asked. The installation should complete in approximately 10 minutes. %VMSINSTAL-I-RESTORE, Restoring product save set B ... %VMSINSTAL-I-RESTORE, Restoring product save set C ... The RTR installation procedure will provide you with a number of RTR monitor files - used to create the RTR utility MONITOR displays. These files will be moved to SYS$SYSTEM by the installation. As some sites may have customised their monitor display files, these files are NOT PURGED by the installation. You may want to do this yourself. The files are named: RTR*.MON (standard DCL wildcarding) %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Sample Installation A-3 Sample Installation Starting RTR installation verification procedure Copyright Digital Equipment Corporation 1988,1993. 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 Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. Stopping RTR if previously started %RTR-I-STACOMSRV, starting command server on node FLIMS %RTR-E-RTRNOTSTA, RTR not started %RTR-S-JOURNALINI, journal has been initialized on device $4$DUS0: %RTR-S-RTRSTART, RTR started %RTR-S-FACADDED, facility RTR$DEFAULT_FACILITY added %RTR-I-LOWBNDHEX, low bound is 00000000 (hex) %RTR-I-HIGBNDHEX, high bound is FFFFFFFF (hex) %RTR-I-SYSSRVCOM, $DCL_TX_PRC completed on channel S -SYSTEM-S-NORMAL, normal successful completion %RTR-I-SYSSRVCOM, $DCL_TX_PRC completed on channel R -SYSTEM-S-NORMAL, normal successful completion %RTR-I-SYSSRVCOM, $START_TX completed on channel R -SYSTEM-S-NORMAL, normal successful completion %RTR-I-SYSSRVCOM, $ENQ_TX completed on channel R -SYSTEM-S-NORMAL, normal successful completion %RTR-I-SYSSRVNOW, $COMMIT_TX posted with no wait on channel R %RTR-I-SYSSRVCOM, $DEQ_TX completed on channel S -RTR-S-STARTTX, a new transaction has started %RTR-I-DEQDATA, dequeued data (7 bytes) "RTR IVP" %RTR-I-SYSSRVCOM, $DEQ_TX completed on channel S -RTR-S-VOTETX, please issue $VOTE_TX for transaction %RTR-I-SYSSRVCOM, $VOTE_TX completed on channel S -RTR-S-COMMIT, transaction commit %RTR-I-SYSSRVCOM, $COMMIT_TX completed on channel R -SYSTEM-S-NORMAL, normal successful completion %RTR-S-RTRSTOP, RTR stopped %RTR-I-STACOMSRV, starting command server on node FLIMS The IVP has completed successfully Installation of RTRSFT V2.1 completed at 11:25 A-4 Sample Installation Sample Installation Enter the products to be processed from the next distribution volume set. * Products: VMSINSTAL procedure done at 11:26 Sample Installation A-5 B _________________________________________________________________ Sample Startup This appendix contains the RTR$STARTUP.COM to be called from SYSTARTUP.COM when the system is booted, and the RTR$NODE_SPECIFIC_STARTUP_TEMPLATE.COM. B.1 RTR$STARTUP.COM $!TITLE RTR$STARTUP.COM - RTR startup environment procedure $!********************************************************************** $! $! Copyright Digital Equipment Corporation 1988,1993. 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 Digital Equipment Corporation. Possession, use, or copying of this $! software and media is authorized only pursuant to a valid written license $! from Digital or an authorized sublicensor. $! $!********************************************************************** $! $! Sets up required local environment for running RTR. $! Intended to be called from SYSSTARTUP_V5.COM. $! $! The following definition is necessary if RTR is to be managed $! and monitored from a remote node. $! $ DEFINE/NOLOG/SYSTEM RTR$COMSERV SYS$SYSTEM:RTRCOMSERV $! $! The following commands install/replace the various RTR images $! Sample Startup B-1 Sample Startup B.1 RTR$STARTUP.COM $ VERB="ADD" $ FILNAM = "SYS$SHARE:RTRSHR.EXE" $ IF F$FILE( "''FILNAM'","KNOWN").EQS."TRUE" THEN VERB="REPLACE" $ INSTALL 'VERB' 'FILNAM' - /PROTECTED/HEADER_RESIDENT/SHARED $! $ VERB="ADD" $ FILNAM = "SYS$SHARE:RTRRTL.EXE" $ IF F$FILE( "''FILNAM'","KNOWN").EQS."TRUE" THEN VERB="REPLACE" $ INSTALL 'VERB' 'FILNAM' - /HEADER_RESIDENT/SHARED $! $ VERB="ADD" $ FILNAM = "SYS$SYSTEM:RTR.EXE" $ IF F$FILE( "''FILNAM'","KNOWN").EQS."TRUE" THEN VERB="REPLACE" $ INSTALL 'VERB' 'FILNAM' - /PRIVILEGE=(NETMBX,TMPMBX,DETACH,WORLD,SYSLCK,SYSGBL,SYSPRV,PRMGBL,PRMMBX,- CMEXEC,GROUP,GRPNAM,SHARE) $! $ VERB="ADD" $ FILNAM = "SYS$SYSTEM:RTRCOMSERV.EXE" $ IF F$FILE( "''FILNAM'","KNOWN").EQS."TRUE" THEN VERB="REPLACE" $ INSTALL 'VERB' 'FILNAM' - /PRIVILEGE=(NETMBX,TMPMBX,DETACH,WORLD,SYSLCK,SYSGBL,SYSPRV,PRMGBL,PRMMBX,- SYSNAM,CMEXEC,GROUP,GRPNAM,SHARE,ALTPRI) $! $ VERB="ADD" $ FILNAM = "SYS$SYSTEM:RTRACP.EXE" $ IF F$FILE( "''FILNAM'","KNOWN").EQS."TRUE" THEN VERB="REPLACE" $ INSTALL 'VERB' 'FILNAM' - /PRIVILEGE=(NETMBX,TMPMBX,WORLD,SYSLCK,SYSGBL,SYSPRV,SYSNAM,PRMGBL,GROUP,- GRPNAM,SHARE) $! $ VERB="ADD" $ FILNAM = "SYS$SYSTEM:RTRRCHACP.EXE" $ IF F$FILE("''FILNAM'","KNOWN").EQS."TRUE" THEN VERB="REPLACE" $ INSTALL 'VERB' 'FILNAM' - /PRIVILEGE=(NETMBX,TMPMBX,SYSNAM) $! $ RUN SYS$SYSTEM:NCP SET OBJECT RTR$COMSERV NUMBER 0 FILE RTR$COMSERV: USER ILLEGAL PASSWORD DISABLED DEF OBJECT RTR$COMSERV NUMBER 0 FILE RTR$COMSERV: USER ILLEGAL PASSWORD DISABLED EXIT B-2 Sample Startup Sample Startup B.2 RTR$NODE_SPECIFIC_STARTUP_TEMPLATE.COM. B.2 RTR$NODE_SPECIFIC_STARTUP_TEMPLATE.COM. $!TITLE RTR$NODE_SPECIFIC_STARTUP_TEMPLATE.COM $!********************************************************************** $! $! Copyright Digital Equipment Corporation 1993. 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 Digital Equipment Corporation. Possession, use, or copying of this $! software and media is authorized only pursuant to a valid written license $! from Digital or an authorized sublicensor. $! $!********************************************************************** $! $! Template for command procedure to set up required node specific $! environment for running RTR. $! $! -------------------------------------- Definition of RTR$DUMP_DIRECTORY $! The following definition tells RTR where dump files are to be created $! lines to enable production of RTR dump files when an error occurs. $! should a non-recoverable error occur. $! An RTR dump file typically uses about 5000 blocks, so enough space must $! be available on the defined disk. $! The logical name RTR$DUMP_DIRECTORY will be used by a detached process, $! so use of process- or job-local logical names within the dump_dev $! specification should be avoided. $! The RTR$DUMP_DIRECTORY logical name also may be redefined at the group $! level, if running RTR in group mode and it is desired to locate dumps $! in a different directory for a particular user-group. $! $ INSTALL REPLACE SYS$SHARE:IMGDMP $ DEFINE/NOLOG/SYSTEM RTR$DUMP_DIRECTORY SYS$SYSTEM: $! $! -------------------------------------- Example $! The following example is included to show how to start RTR and $! create an RTR facility. $! Sample Startup B-3 Sample Startup B.2 RTR$NODE_SPECIFIC_STARTUP_TEMPLATE.COM. $!- $!RTR STOP RTR ! Stop rtr if it is already running $!RTR START RTR $!RTR CREATE FACILITY facility_name /BACKEND=(node) /ROUTER=(node) /FRONTEND=(node) B-4 Sample Startup C _________________________________________________________________ Files modified during the RTR installation Table C-1 shows the files that are modified or created when RTR is installed: Files modified during the RTR installation C-1 Files modified during the RTR installation Table_C-1_Files_modified_during_RTR_installation___________ File______________________________Created/modified_________ SYS$SYSTEM:RTRACP.EXE Created SYS$SYSTEM:RTRRCHACP.EXE Created SYS$SYSTEM:RTR.EXE Created SYS$SYSTEM:RTRCOMSERV.EXE Created SYS$SYSTEM:RTRCOMSERV.COM Created SYS$SYSTEM:RTR*.MON Created SYS$SYSTEM:RTR_START_ACP.COM Created SYS$SYSTEM:RTR_START_RCHACP.COM Created SYS$MESSAGE:RTRMSG.EXE Created SYS$COMMON:[SYS$STARTUP]RTR$STARTUCreated SYS$MANAGER:RTR$NODE_SPECIFIC_ Created STARTUP_TEMPLATE.COM SYS$MANAGER:RTR$SNAPSHOT.COM Created SYS$EXAMPLES:RTR$*.* Created SYS$HELP:HELPLIB.HLB Modified SYS$HELP:RTRHLP.HLB Created SYS$TEST:RTR$IVP.COM Created SYS$LIBRARY:RTRSHR.EXE Created SYS$LIBRARY:RTRRTL.EXE Created SYS$LIBRARY:DCLTABLES.EXE Modified SYS$LIBRARY:RTR.ADA Created SYS$LIBRARY:RTR.BAS Created SYS$LIBRARY:RTR.FOR Created SYS$LIBRARY:RTR.H Created SYS$LIBRARY:RTR.L32 Created SYS$LIBRARY:RTR.MLB Created SYS$LIBRARY:RTR.PAS Created SYS$LIBRARY:RTR.PEN Created SYS$LIBRARY:RTR.PLI Created SYS$LIBRARY:RTR.REQ_______________Created__________________ C-2 Files modified during the RTR installation