VAX RALLY Installation Guide Order Number: AA-KZ25D-TE May 1991 This document contains instructions for installing VAX RALLY and the VAX RALLY Run-Time Option on the VMS operating sys- tem. It also explains how to read the online release notes before or after installing the product. This document applies to VAX RALLY and VAX RALLY Run-Time Option Version 2.3 and all maintenance updates throughout that version. Revision/Update Information: This revised manual supersedes the VAX RALLY Installation Guide (Order Number AA-KZ25C- TE). Operating System and Version: VMS Version 5.2 or higher. Future maintenance releases may require higher versions. Software Version: VAX RALLY Version 2.3 digital equipment corporation maynard, massachusetts ___________________________________________________ May 1991 The following are trademarks of Digital Equipment Corporation: ACMS, ALL-IN-1, DATATRIEVE, DEC, DECdecision, DECnet, DECtrace, Digital, MicroVAX, RALLY, Rdb/VMS, TEAMDATA, VAX, VAXcluster, VAX COBOL Generator, VAX DOCUMENT, VAX RALLY, VIDA, VMS, VT100, VT300, and the DIGITAL logo. ORACLE is a registered trademark of Oracle Corporation. DB2 is a registered trademark of International Business Machines Corporation. PostScript is a registered trademark of Adobe Systems, Inc. This document is available on CDROM. ZK5654 This document was prepared using VAX DOCUMENT, Version 1.2 Contents ________________________________________________________________ Preface ......................................................... vii ________________________________________________________________ Chapter 1 Preparing to Install VAX RALLY 1.1 Prerequisite Hardware............................. 1-2 1.2 Prerequisite and Optional Software.............. 1-2 1.2.1 Software for VAX RALLY Development Option....................................... 1-2 1.2.2 Software for VAX RALLY Run-Time Option....................................... 1-4 1.3 VAX Licensing Management Facility (LMF)........ 1-5 1.4 Installation Procedure Requirements............. 1-5 1.4.1 Disk Space.................................. 1-6 1.4.2 Privileges.................................. 1-6 1.4.3 System Parameters.......................... 1-8 1.4.3.1Checking System Parameter Values............................... 1-9 1.4.3.2Calculating the Values for GBLPAGES and GBLSECTIONS.......... 1-9 1.4.3.3Changing System Parameter Values with AUTOGEN........................ 1-10 iii 1.4.3.4Setting Dynamic System Parameter Values............................... 1-11 1.4.4 Process Account Quotas.................... 1-12 1.4.5 VMSINSTAL Requirements.................... 1-14 1.4.6 Backing Up Your System Disk.............. 1-14 ________________________________________________________________ Chapter 2 Installing VAX RALLY 2.1 The Installation Procedure ....................... 2-1 2.2 Error Recovery ..................................... 2-14 ________________________________________________________________ Chapter 3 After Installing VAX RALLY 3.1 Running the Installation Verification Procedure Separately .............................. 3-1 3.2 Editing the System Startup File ................. 3-1 3.3 Modifying System Parameters...................... 3-3 3.4 Installing VAX RALLY on a VAXcluster............ 3-3 3.5 User Account Requirements ........................ 3-3 3.5.1 Privileges.................................. 3-4 3.5.2 User Account Quotas ....................... 3-4 3.6 Customizing RALLY Error and Message Files...... 3-5 3.7 Shutting Down VAX RALLY........................... 3-7 iv ________________________________________________________________ Chapter 4 Maintaining VAX RALLY 4.1 Reading a Bugcheck Dump File..................... 4-1 4.2 Reporting Problems to Digital.................... 4-2 ________________________________________________________________ Appendix A Files and Logical Names Installed on Your System A.1 VAX RALLY Files.................................... A-1 A.2 VAX RALLY Run-Time Option Files ................. A-6 A.3 Logical Names ...................................... A-7 ________________________________________________________________ Appendix B Sample Installations B.1 Installing VAX RALLY .............................. B-1 B.2 Installing the VAX RALLY Run-Time Option....... B-5 ________________________________________________________________ Index ________________________________________________________________ Tables 1-1 Optional Software for VAX RALLY Development Option............................................... 1-3 1-2 Optional Software for VAX RALLY Run-Time Option............................................... 1-4 1-3 Disk Space Requirements........................... 1-6 1-4 Required Privileges ............................... 1-7 v 1-5 Minimum Required System Parameter Values....... 1-8 1-6 Process Account Quotas for the Installing Account ............................................. 1-12 vi Preface ________________________________________________________________ This manual describes how to install VAX RALLY and the VAX RALLY Run-Time Option on the VMS operating system. The VAX RALLY documentation refers to VAX RALLY by its abbre- viated name, RALLY. RALLY includes both the RALLY Definition System and the RALLY Run-Time System. This manual uses the term "VAX RALLY Development Option" instead of "RALLY" whenever the term "RALLY" might be ambiguous. The VAX RALLY Run-Time Option includes only the Run-Time System. You can use this option to run existing RALLY appli- cations, but you cannot use it to create new RALLY applica- tions or modify existing ones. The VAX RALLY Online Release Notes for Version 2.3 covers both options. Read the release notes before installing the product. vii ____________________________________________________________ Intended Audience This manual is intended for those who are responsible for any of the following: o Planning the installation of RALLY and preparing your system o Installing RALLY o Changing your system by adjusting parameters, startup files, and privileges required for running RALLY To install the software, you must: o Be familiar with VMSINSTAL, the command procedure used to install software products in the VMS environment. To locate the description of VMSINSTAL, see the master index of the VMS documentation set. o Have access to the SYSTEM account on your machine or to an account with the user privilege SETPRV. If you are responsible for installing RALLY on your system, read this entire manual before you begin the installation. This manual helps you make the required decisions and guides you through the correct sequence of actions. NOTE All RALLY installers and application definers should read the release notes. viii ____________________________________________________________ Operating System Information Information about the versions of the operating system and related software that are compatible with this version of RALLY is included in Chapter 1 of this manual, in the RALLY media kit, and the Before You Install VAX RALLY Letter. For information on the compatibility of other software products with this version of RALLY, refer to the System Support Addendum (SSA) that comes with the Software Product Description (SPD). You can use the SPD/SSA to verify which versions of your operating system are compatible with this version of RALLY. ____________________________________________________________ Structure of This Manual This manual includes four chapters and two appendixes: Chapter 1 Explains how to plan the installation and prepare your system for the installation. Chapter 2 Explains how to install the software. Chapter 3 Explains how to change your VMS system by ad- justing the required characteristics for running RALLY and the RALLY Run-Time Option. Chapter 4 Explains how to detect, solve, and report prob- lems you might encounter after installing RALLY and the RALLY Run-Time Option. ix Appendix A Lists the files transferred and logicals defined by the installation of RALLY and the RALLY Run- Time Option. Appendix B Presents the log of a sample installation of RALLY and of the RALLY Run-Time Option. ____________________________________________________________ Related Documents Refer to the following manuals for more information about RALLY: o Introduction to VAX RALLY-Provides an overview of RALLY. o VAX RALLY Application User's Guide-Provides step-by-step instructions on using a RALLY application at run time. o VAX RALLY Command Reference Manual-Describes RALLY com- mands. o VAX RALLY ADL User's Guide-Describes the RALLY Application Development Language (ADL). o VAX RALLY Definition System User's Guide-Provides step-by- step instructions on defining a RALLY application. o VAX RALLY Reference Manual and Master Index-Explains major RALLY terms and concepts. o VAX RALLY Guide to Application Development-Provides appli- cation development guidelines within the framework of a suggested development methodology. o VAX RALLY Online Release Notes-The online release notes describes problems and workarounds for this version of RALLY. x For further information on certain topics covered in this manual, you can refer to: o Guide to VAX/VMS Software Installation o VAX/VMS System Manager's Reference Manual o Guide to Networking on VAX/VMS o VAX Rdb/VMS Installation Guide ____________________________________________________________ Conventions This manual uses the following conventions: _____________________________________________________________ Convention_________Meaning___________________________________ RETURN Named keys appear in uppercase letters. CTRL/X The slash in the key name means that you press the two keys simultaneously. In this case, press the CTRL key (control) and, while holding down the CTRL key, press the character key, represented here by x. . Vertical ellipsis in an example means that . information not directly related to the . example has been omitted. $ The dollar sign is used to indicate the DCL prompt. This prompt can be different on your system. xi _____________________________________________________________ Convention_________Meaning___________________________________ $ RALLY EDIT Interactive examples show user input in _Application red letters and system output (such as File: prompts and messages) in black letters. The online Bookreader version of this document displays user input in a bold ___________________font._____________________________________ ____________________________________________________________ References to Products The RALLY documentation to which this manual belongs refers to the following products by their abbreviated names: o VAX CDD/Plus software is referred to as CDD/Plus. o VAX DATATRIEVE software is referred to as DATATRIEVE. o VAX DBMS software is referred to as VAX DBMS. o VAX Rdb/VMS software is referred to as Rdb/VMS. o VAX TEAMDATA software is referred to as TEAMDATA. o VAX ALL-IN-1 software is referred to as ALL-IN-1. o VAX Language-Sensitive Editor software is referred to as LSE. o VAX Application Control and Management System software is referred to as ACMS. o VAX DEC/Code Management System software is referred to as CMS. o VAX DEC/Module Management System is referred to as MMS. o VAX DEC/Test Manager software is referred to as DEC/Test Manager. o VAX DECtrace for VMS software is referred to as DECtrace. xii o DEC RdbExpert software is referred to as RdbExpert. xiii Chapter 1 Preparing to Install VAX RALLY ________________________________________________________________ This chapter discusses the preparations and requirements necessary for installing VAX RALLY. There are two RALLY options: o VAX RALLY-Includes both the RALLY Definition System and the RALLY Run-Time System. This manual sometimes refers to RALLY as the VAX RALLY Development Option. o VAX RALLY Run-Time Option-Includes only the RALLY Run- Time System. You can use this option to run existing RALLY applications, but you cannot use it to create new RALLY applications or modify existing applications. The procedures for installing RALLY and for installing the VAX RALLY Run-Time Option are similar. Where the procedures differ, the instructions note the differences. Your bill of materials (BOM) and indented bills report (BIL) specify the number and contents of your media. Be sure to verify the contents of your kit with this information. If your kit is damaged or if you find that parts of it are missing, contact your Digital representative. Preparing to Install VAX RALLY 1-1 VAX RALLY 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 Prerequisite Hardware VAX RALLY and the VAX RALLY Run-Time Option run on all VAX processors except VAX-11/725, VAX-11/782, MicroVAX I, and VAXstation I. For a complete list of processors, see the VAX RALLY Software Product Description. Installation and use of either option requires at least 4 MB of memory on your VAX system. RALLY applications will provide better response if given additional memory. In general, you should configure your system with an additional 0.75 MB for each RALLY user. ____________________________________________________________ 1.2 Prerequisite and Optional Software The software that is required or optional for RALLY depends on whether you are installing VAX RALLY or the VAX RALLY Run- Time Option. Sections 1.2.1 and 1.2.2 outline the software to be used with both options. The System Software Addendum (SSA) contains a complete list of prerequisite and optional software and their required version numbers. ____________________________________________________________ 1.2.1 Software for VAX RALLY Development Option RALLY requires the following software: o VMS Version 5.2 o VAX Rdb/VMS Version 3.1B (or higher) o VAX CDD/Plus Version 4.2 (or higher) 1-2 Preparing to Install VAX RALLY Table 1-1 lists the optional software for VAX RALLY. Table 1-1: Optional Software for VAX RALLY Development Option _____________________________________________________________ Optional_Products_________Purpose____________________________ VAX DATATRIEVE Version Required for use of DATATRIEVE at 5.1 (or higher) define time VAX DBMS Version 4.2 (or Required for use of DBMS at define higher) time VAX TEAMDATA Version 1.4 Required for use of TEAMDATA at (or higher) define time ALL-IN-1 Version 2.3 (or Required for use of ALL-IN-1 at higher) define time VAX Language-Sensitive Required for use of callable LSE as Editor (LSE) Version 3.0 the ADL editor (or higher) VAX ACMS Version 3.1 (or Required for use of ACMS at define higher) time and for use of the RALLY$ODI_ ACMS example VAX COBOL Version 4.2- Required for use of RALLY$ODI_ACMS 41A (or higher) example VAX VIDA for DB2 Version Required for use of DB2 at define 1.0A (or higher) time RdbAccess for ORACLE Required for use of ORACLE at run Version 1.0 (or higher) time RdbAccess for RMS Optional for use of RMS at define Version_1.0_(or_higher)___time_______________________________ Preparing to Install VAX RALLY 1-3 ____________________________________________________________ 1.2.2 Software for VAX RALLY Run-Time Option The only software required to run VAX RALLY Run-Time Option is VMS Version 5.2. Table 1-2 lists the optional software for the VAX RALLY Run- Time Option. Table 1-2: Optional Software for VAX RALLY Run-Time Option _____________________________________________________________ Optional_Products_________Purpose____________________________ VAX Rdb/VMS Version 3.1B Required for use of Rdb at run time (or higher) VAX DATATRIEVE Version Required for use of DATATRIEVE at 5.1 (or higher) run time VAX DBMS Version 4.2 (or Required for use of DBMS at run higher) time VAX TEAMDATA Version 1.4 Required for use of TEAMDATA at run (or higher) time ALL-IN-1 Version 2.3 (or Required for use of ALL-IN-1 at run higher) time VAX ACMS Version 3.1 (or Required for use of ACMS at run higher) time VAX VIDA for DB2 Version Required for use of DB2 at run time 1.0A (or higher) RdbAccess for ORACLE Required for use of ORACLE at run Version 1.0 (or higher) time RdbAccess for RMS Optional for use of RMS at run time Version 1.0 (or higher) DECtrace for VMS Version Required for use of DECtrace at run 1.0A_(or_higher)__________time_______________________________ 1-4 Preparing to Install VAX RALLY ____________________________________________________________ 1.3 VAX Licensing Management Facility (LMF) Before you install and run VAX RALLY Version 2.3 on a newly- licensed node or cluster, you must first register a License Product Authorization Key (License PAK) using the License Management Facility (LMF). The License PAK may be shipped along with the kit if you ordered the license and media to- gether; otherwise, it is shipped separately to a location based on your license order. If you are installing RALLY as an update on a node or cluster already licensed for this software, you have already completed the License PAK regis- tration requirements. You must register and load your license for VAX RALLY 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: o Invoke the SYS$UPDATE:VMSLICENSE.COM procedure. When it prompts you for information, respond with data from your License PAK. o At the DCL prompt, enter the LICENSE REGISTER command with the appropriate qualifiers that correspond to License PAK information. If you plan to use VAX RALLY 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. (See Section 3.4.) ____________________________________________________________ 1.4 Installation Procedure Requirements This section and those that follow discuss various require- ments for installing VAX RALLY. The installation takes approximately 5 to 40 minutes, depend- ing on your type of media and your system configuration. Preparing to Install VAX RALLY 1-5 ____________________________________________________________ 1.4.1 Disk Space VAX RALLY's requirements for free disk storage space are dif- ferent during installation and after installation. Table 1-3 summarizes the storage requirements. Table 1-3: Disk Space Requirements _____________________________________________________________ Blocks During Kit_________________Installation______Blocks_After_Installation VAX_RALLY_Development_Option_________________________________ With the example 28000 20500 files Without the exam- 21000 16000 ple files _____________________________________________________________ VAX_RALLY_Run-Time_Option____________________________________ With the example 11000 8500 files Without the exam- 9000 4000 ple_files____________________________________________________ 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 ____________________________________________________________ 1.4.2 Privileges The account you use to install RALLY must have the user privilege SETPRV. As one of the first actions, the VMSINSTAL command procedure grants all privileges (except BYPASS) to the process that invokes it. This command succeeds only if the account has SETPRV. On most systems, the SYSTEM account has SETPRV and is used to install software. The procedures described in this installation guide refer to the SYSTEM account, but they are the same for any account with SETPRV. 1-6 Preparing to Install VAX RALLY Before you start the VMSINSTAL command procedure, you might need to prepare your system for the installation. For ex- ample, you might have to run SYSGEN or AUTHORIZE. Some of these preparations require that your account have specific user privileges, which might not be among default privileges assigned to your account. Table 1-4 shows you what privileges you need for various installation tasks. Table 1-4: Required Privileges _____________________________________________________________ Privilege_Meaning____________________________________________ CMKRNL Change mode to kernel EXQUOTA Allow disk space to exceed established quotas NETMBX Allow user to perform network-related functions OPER Perform operator functions SETPRV Enable any privilege SYSNAM Insert system logical names in the name table SYSPRV Access resources as if process has a system UIC TMPMBX Create temporary mailbox WORLD_____Allow_access_to_other_processes____________________ To check the privileges of the installing account, use the SHOW PROCESS/ PRIVILEGES command. If the SYSTEM account does not have the privileges listed in Table 1-4, use AUTHORIZE to grant them permanently or SET PROCESS/PRIVILEGES to grant them for this installation. Preparing to Install VAX RALLY 1-7 ____________________________________________________________ 1.4.3 System Parameters Installing VAX RALLY requires certain system parameter set- tings. Table 1-5 lists the minimum required system parameter values for the installation. Table 1-5: Minimum Required System Parameter Values _____________________________________________________________ System_Parameter___________Minimum_Value_____________________ CLISYMTBL[1] 500 GBLPAGES[2] n[3] + 3000 GBLPAGFIL 2048 GBLSECTIONS[2] n[3] + 14 LOCKIDTBL[4] 256 LOCKIDTBL_MAX[4] 2048 RESHASHTBL[4] 512 VIRTUALPAGECNT 19000 [1]The_CLISYMTBL_dynamic_system_parameter_must_be_set_to_____ a minimum value of 500 during the installation procedure. You can change the setting to its original value once the installation is finished. [2]The values listed for these system parameters represent the number of additional free global pages and global sec- tions required for the installation, not the total number you need to run your system and other software. [3]n = current setting. [4]The setting is needed only for VAX RALLY or Rdb/RMS appli- cations. The setting does not apply to a VAX RALLY Run-Time Option that uses only RMS. _____________________________________________________________ The next sections show you how to do the following: o Check system parameter values o Calculate values for the GBLPAGES and GBLSECTIONS system parameters 1-8 Preparing to Install VAX RALLY o Change parameter values with the VMS AUTOGEN command procedure o Set dynamic parameters (such as CLISYMTBL) with the VMS System Generation Utility (SYSGEN) ____________________________________________________________ 1.4.3.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-5. The following example displays the value for the VIRTUALPAGECNT system parameter: SYSGEN> SHOW VIRTUALPAGECNT After checking the parameters with the SHOW command, enter the EXIT command at the SYSGEN> prompt to return to DCL level. ____________________________________________________________ 1.4.3.2 Calculating the Values for GBLPAGES and GBLSECTIONS To install and run VAX RALLY, 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. On a VMS Version 5.2 or higher system, 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): $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES") 15848 $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS") 24 Preparing to Install VAX RALLY 1-9 If the values displayed by the system are greater than the values in Table 1-5, 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-5, you must increase the system parameter setting. Section 1.4.3.3 describes the procedures for increasing these values using AUTOGEN. ____________________________________________________________ 1.4.3.3 Changing System Parameter Values with AUTOGEN Use the AUTOGEN command procedure to change system param- eters. 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: MIN_VIRTUALPAGECNT = 19000 To modify incremental parameters such as GBLPAGES and GBLSECTIONS, 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-10 Preparing to Install VAX RALLY 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 VMS System Management Subkit. ____________________________________________________________ 1.4.3.4 Setting Dynamic System Parameter Values Use the System Generation Utility (SYSGEN) to set dynamic parameters. Dynamic parameters changed with the SYSGEN WRITE ACTIVE command become active immediately without any need to reboot your system. In fact, rebooting returns dynamic system parameter values to their previous settings. Once you change dynamic parameter values, you should complete the installation before rebooting the system. After you finish with the installation, you can reset the dynamic parameters to their previous values or let them be reset automatically when you next reboot your system. VAX RALLY requires only the CLISYMTBL dynamic parameter value of 500. If the dynamic parameter value on your system is less than 500, use the following series of commands to change the value: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> USE ACTIVE SYSGEN> SET CLISYMTBL 500 SYSGEN> WRITE ACTIVE SYSGEN> EXIT Preparing to Install VAX RALLY 1-11 ____________________________________________________________ 1.4.4 Process Account Quotas The account you use to install VAX RALLY must have sufficient quotas to enable you to perform the installation. Table 1-6 summarizes the process quotas required for the installa- tion account. Also refer to the VMSINSTAL documentation for process account quotas requirements. NOTE Large or complex applications may require higher pro- cess account quotas. Table 1-6: Process Account Quotas for the Installing Account _____________________________________________________________ Minimum for VAX Account RALLY or Rdb Minumum for Run-Time Option Quota_________Applications________with_RMS_Applications______ BYTLM 20480 18000 ENQLM 1000 None FILLM 100 100 WSQUOTA 1024 1024 PGFLQUOTA_____20000_______________None_______________________ 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> At the UAF> prompt, enter the SHOW command with an account name to check a particular account. For example: UAF> SHOW SMITH 1-12 Preparing to Install VAX RALLY 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=60 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 Management Subkit. Preparing to Install VAX RALLY 1-13 ____________________________________________________________ 1.4.5 VMSINSTAL Requirements When you invoke VMSINSTAL, it checks the following: o Whether you are logged in to the SYSTEM account or an account with system privileges o Whether you have adequate quotas for installation o Whether any users are logged in to the system Note that VMSINSTAL requires that the installation account have a minimum of the following quotas. These quotas may vary depending on the version of VMS that is installed on your system. ASTLM = 24 BIOLM = 18 BYTLM = 32,768 DIOLM = 18 ENQLM = 200 FILLM = 100 If VMSINSTAL detects any problems during the installation, it notifies you and asks if you want to continue the instal- lation. In some instances, you can enter YES to continue. To stop the installation process and correct the situation, en- ter NO or press RETURN. Then correct the problem and restart the installation. ____________________________________________________________ 1.4.6 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 Management Subkit. 1-14 Preparing to Install VAX RALLY Chapter 2 Installing VAX RALLY ________________________________________________________________ This chapter explains how to install VAX RALLY. Section 2.1 contains a step-by-step description of the installation procedure. Chapter 3 covers postinstallation considerations. ____________________________________________________________ 2.1 The Installation Procedure This section explains how to install RALLY and the RALLY Run-Time Option using the VMSINSTAL command procedure. The VMSINSTAL command procedure moves the software from the distribution media to your system disk. The VAX RALLY installation procedure consists of a series of questions and informational messages. See Appendix B for sample installations. 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. NOTE RALLY includes the RALLY Definition System and the RALLY Run-Time System. The name of the RALLY kit is RALDO023. The RALLY Run-Time Option includes only the Run-Time System. The name of the Run-Time Option kit is RALRTO023. To invoke VMSINSTAL for the RALLY Run-Time Option, substitute RALRTO023 for RALDO023 in the command line. If you are installing the Run-Time Installing VAX RALLY 2-1 Option, you should substitute RALRTO023 every time RALDO023 appears in this example. 2-2 Installing VAX RALLY 1. Invoke VMSINSTAL. $ @SYS$UPDATE:VMSINSTAL saveset-name device-name OPTIONS N 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. The following list defines the elements of the VMSINSTAL command procedure: saveset-name The installation name for the component. For VAX RALLY, use one of the following installation names: VAX RALLY Development Option RALDO023 VAX RALLY Run-Time Option RALRTO023 device-name The name of the device on which you plan to mount the media. For example, MTA0: is the device name for a tape drive. It is not necessary to use the console drive for this installation. However, if you do use the console drive, you should replace any media you removed once the installation is complete. OPTIONS N An optional parameter that indicates you want to see the question about viewing the release notes. If you do not include the OPTIONS N parameter, VMSINSTAL does not ask you about the release notes. You should review the release notes before proceeding with the installation in case they contain additional information about the installation. If you are restarting the installation and have already reviewed the release notes, you do not need to specify OPTIONS N. Note that there are several other options you can select when you invoke VMSINSTAL. o Auto_answer option (A)-Initially creates a file that contains your answers to VMSINSTAL questions and prompts. You can then use the option (and the answer file) to save time during a reinstallation (typically after upgrading your system). Installing VAX RALLY 2-3 o Get save set option (G)-Lets you store product save sets temporarily on a magnetic tape or in a disk direc- tory. o File log option (L)-Logs all activity to the terminal during installation. See the VMS documentation on software installation in the VMS System Management Subkit for detailed information on these options. If you specify more than one option, separate the options with commas (OPTIONS A,N). The following example invokes VMSINSTAL to install VAX RALLY Development Option from tape drive MTA0: and shows the system response. This example uses the OPTIONS N release notes parameter. $ @SYS$UPDATE:VMSINSTAL RALDO023 MTA0: OPTIONS N VAX/VMS Software Product Installation Procedure V5.2-1 It is 29-MAY-1991 at 12:32. 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. VMSINSTAL does not prompt you for any options, so be sure to include OPTIONS N on the VMSINSTAL command line to access the release notes during the installation. 2. 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-4 Installing VAX RALLY 3. Mount the media. Please mount the first volume of the set on MTA0:. * Are you ready? YES %MOUNT-I-MOUNTED, RALDO mounted on _MTA0: The following products will be processed: RALDO 2.3 Beginning installation of VAX RALLY 2.3 at 12:36 %VMSINSTAL-I-RESTORE, Restoring product saveset A... You should now mount the first distribution volume on the device you specified when you invoked VMSINSTAL. The device name appears in the line preceding the question. VMSINSTAL then asks you if you are ready to continue with the installation. If you respond YES to indicate that you are ready, VMSINSTAL displays a message that the media containing RALDO023 has been mounted on the specified device and that the installation has begun. If you entered the wrong device name when you invoked VMSINSTAL and need to restart the installation, enter NO in response to the "Are you ready?" question. To abort the installation for other reasons, press CTRL/Y. 4. Mount additional media volumes. %BACKUP-I-READYREAD, mount volume 2 on _MTA0: for reading Enter "YES" when ready: If your installation kit contains more than one volume, VMSINSTAL prompts you to mount the additional volumes and then asks you to indicate that you are ready for the installation to proceed. 5. Select a release notes option. Installing VAX RALLY 2-5 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]: If you specified OPTIONS N when you invoked VMSINSTAL, you are now asked to choose one of the four options for reviewing the release notes. If you select option 1, VMSINSTAL displays the release notes immediately on the console terminal. You can termi- nate the display at any time by pressing CTRL/C. If you select option 2, VMSINSTAL prompts you for the name of the print queue that you want to use: * Queue name [SYS$PRINT]: You can press RETURN to send the file to the default output print device or you can enter another queue name. If you select option 3, VMSINSTAL displays the release notes immediately on the console terminal and then prompts you for a queue name for the printed version. Select option 4 if you have already reviewed the release notes and are restarting the installation. Next, VMSINSTAL displays the following question: * Do you want to continue the installation [N]?: YES %VMSINSTAL-I-RELMOVED, The product's release notes have been successfully moved to SYS$HELP. To continue the installation, enter YES. Otherwise, press RETURN. In either case, the following release notes file is copied to the SYS$HELP directory: SYS$HELP:RALLY023.RELEASE_NOTES 2-6 Installing VAX RALLY After the installation, you can enter the following com- mand to obtain the file specification for the online release notes. $ HELP RALLY RELEASE_NOTES NOTE The name of the release notes file installed by VMSINSTAL consists of the current product name and version number. Do not delete release notes for previous versions of VAX RALLY. 6. Respond to license registration queries. Product: RALLY Producer: DEC Version: 2.3 Release Date: 01-JUL-1990 * 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, regis- ter and load your PAK, and then restart the installation. 7. Respond to examples queries. If you are installing RALLY, you are asked the following questions: * Do you want to install the RALLY Run-Time System examples [YES]? * Do you want to install the RALLY Development System examples [YES]? If you are installing the RALLY Run-Time Option, you see the following question: * Do you want to install the RALLY Run-Time System examples [YES]? You have the option to install RALLY or RALLY Run-Time System examples. If you want to install the examples, enter YES in response to the questions. Installing VAX RALLY 2-7 8. Purge files. * Do you want to purge files replaced by this installation [YES]? You have the option to purge files from previous versions of VAX RALLY 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. 9. Check any system requirements error messages. At this point, VMSINSTAL displays the following message: ************************************************************ * * * Please wait while the system environment is validated. * * * ************************************************************ The installation procedure performs several checks of system requirements. It checks the following: o Duplicate RALLY installations (and, if there are any, de-installs any current RALLY images). o The number of blocks available on your system disk. o The VMS version your system is running. o The Rdb/VMS version your system is running. o The CDD/Plus version your system is running. o The current value of process quotas. o The current value of system parameters. o The LSE version your system is running. o The DATATRIEVE version your system is running. If any system requirement does not meet the minimum value, VMSINSTAL displays an error message and asks you if you want to continue with the installation. For example: 2-8 Installing VAX RALLY ************************************************************ * * * WARNINGS AND ERRORS * * =================== * * * * * * SYSGEN parameter LOCKIDTBL is too low. * * The current value is 128; it needs to be * * at least 256. * * * * * * Before the installation can succeed, you must correct * * the above problems. Note that some SYSGEN parameters * * require that the system be rebooted before they can * * take effect. * * * ************************************************************ If you use DATATRIEVE in your RALLY application, but have multiple DATATRIEVE shareable images on your system, the messages displayed at this step of the installation procedure will include one that asks you to choose a shareable image. For example: ************************************************************ * * * VAX RALLY can use DATATRIEVE, since it's available. * * * * You have multiple DATATRIEVE shareable images on your * * system, and you need to choose one of them as the * * default image for users. * * * ************************************************************ Here is a list of available DATATRIEVE shareable images: 1. DTRSHR50 VAX DTR V5.0 2. DTRSHR51 VAX DTR V5.1 * Enter the number of the version you want:1 Installing VAX RALLY 2-9 To select a version of DATATRIEVE, define RALLY$DTRSHR to point to the desired DATATRIEVE shareable image. For example: $ DEFINE RALLY$DTRSHR DTRSHR50 10.Correct any problems. You should correct any problems before continuing the installation procedure. If you continue without correct- ing the problem, Digital may not support the resulting installation. For example: ************************************************************ * * * The installation can proceed, but you will not be able * * to run VAX RALLY from this account. * * * ************************************************************ * Do you want to continue with the installation? [YES]? If you answer NO, you can fix any problems and begin again at step 1. 11.Read informational messages. At this point, the installation procedure displays a num- ber 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. If the Language-Sensitive Editor (LSE) is not installed on your system you receive an informational message stating that LSE is not installed, as follows: 2-10 Installing VAX RALLY ************************************************************ * * * WARNINGS AND ERRORS * * =================== * * * * * * NOTICE: * * Support for the use of ADL with the Language- * * Sensitive Editor (LSE) cannot be installed because * * LSE V3.0 is not installed on this system. If * * you want the LSE support, you must do the following: * * * * 1. Install LSE V3.0 (or greater) * * 2. Reinstall this product * * * * This action can be taken any time after this * * installation is completed; there is no need to * * abort this installation. * * * ************************************************************ If you prefer to use RALLY with LSE, you must first in- stall LSE, then reinstall RALLY. VMSINSTAL displays a message that reminds you to edit the system startup files to add a command that invokes RALLY$STARTUP and, if necessary, other commands. You must edit SYSTARTUP_V5.COM on all nodes that run RALLY. If you do not do this, RALLY will not be available when the system is rebooted. An example of messages that may be displayed follows: Installing VAX RALLY 2-11 ************************************************************* * * * SYSTEM MANAGER: * * * * Add the following command(s) to the system startup file * * (for clusters, add to the startup file for each node * * licensed to run RALLY): * * * * $ DEFINE/SYSTEM/EXEC RALLY$DTRSHR SYS$SHARE:DTRSHR50 * * $ @SYS$STARTUP:RALLY$STARTUP * * * * * ************************************************************* 12.Check the file transfer messages. The installation procedure displays messages telling you what it is doing as it continues. The procedure displays these messages when the files for the product are trans- ferred from the distribution medium to your system. If you are installing RALLY, you see some of the following messages: %VMSINSTAL-I-RESTORE, Restoring product saveset B... %VMSINSTAL-I-RESTORE, Restoring product saveset C... %VMSINSTAL-I-RESTORE, Restoring product saveset D... %VMSINSTAL-I-RESTORE, Restoring product saveset E... %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... VAX RALLY: Assigning System-wide RALLY Logicals VAX RALLY: Installing RALLY images Saveset C is restored only if you choose to install the Run-Time System examples. Saveset E is restored only if you choose to install the Definition System examples. If you are installing the RALLY Run-Time Option, the procedure displays the following messages: %VMSINSTAL-I-RESTORE, Restoring product saveset B... %VMSINSTAL-I-RESTORE, Restoring product saveset C... %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... VAX RALLY: Assigning System-wide RALLY Logicals VAX RALLY: Installing RALLY images 2-12 Installing VAX RALLY If the procedure cannot restore the database backup files for the example shipped with the kit, the procedure dis- plays the following message. ************************************************************* * * * *** WARNING *** * * * * The installation procedure was unable to restore the * * Rdb/VMS database backup files (*.RBR). The RBR files * * will be moved to RALLY$EXAMPLES so that you may attempt * * to restore them manually if you wish. Consult your * * Rdb/VMS documentation for instructions on how to perform * * this operation. * * * ************************************************************* %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... VAX RALLY: Assigning System-wide RALLY logicals VAX RALLY: Installing RALLY images If the procedure cannot restore the database example files, the IVP will fail. 13.Observe the Installation Verification Procedure (IVP). Next, VMSINSTAL runs the IVP. When the IVP runs success- fully, you see the following display: RALLY IVP succeeded RALLY T2.3 Definition System IVP Verifying the locations of all non-example files... Verifying idents of RALLY images... Copying RALLY$TAPES database to SYS$SCRATCH for testing... Exercising RALLY Definition System... Exercising RALLY Run-Time System... Cleaning up... RALLY IVP succeeded. NOTE If you answered NO to the following question, the IVP will not be run: * Does this product have an authorization key registered and loaded? Installing VAX RALLY 2-13 However, the IVP command file will be put into SYS$COMMON:[SYSTEST]RALLY$IVP.COM, and may be run once you register the authorization key. If you run the IVP separately, remember to log in to the SYSTEM account or an account that has SYSPRV. (See Chapter 3.) 14.End the installation procedure. Installation of VAX RALLY 2.3 completed at 13:51 VMSINSTAL procedure done at 13:51 The previous messages indicate that the entire installa- tion procedure is complete. You can now log out of the privileged account: $ LOGOUT SYSTEM logged out at 29-MAY-1991 13:53:17 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.2 Error Recovery If errors occur during the installation itself or when the Installation Verification Procedure (IVP) is running, VMSINSTAL displays failure messages. If the installation fails, you see the following message: RALLY IVP failed; RALLY verify utility failed. %VMSINSTAL-E-IVPFAIL, The IVP for RALDO V2.3 has failed. If the IVP fails, you see these messages: The VAX RALLY 2.3 Installation Verification Procedure failed. %VMSINSTAL-E-IVPFAIL, The IVP for VAX RALLY 2.3 has failed. 2-14 Installing VAX RALLY Errors can occur during the installation if any of the fol- lowing conditions exist: o The operating system version is incorrect. o A prerequisite software version is incorrect, not in- stalled, or not started. o Quotas necessary for successful installation are insuffi- cient. o System parameter values for successful installation are insufficient. o The VMS help library is currently in use. o The product license has not been registered and loaded. For descriptions of the error messages generated by these conditions, see the VMS documentation on system messages, recovery procedures, and VMS software installation. If you are notified that any of these conditions exist, you should take the appropriate action as described in the message. For information on installation requirements, see Chapter 1. Installing VAX RALLY 2-15 Chapter 3 After Installing VAX RALLY ________________________________________________________________ The following tasks take place after installing VAX RALLY: o Running the Installation Verification Procedure (IVP) separately. o Editing the system startup file. o Modifying system parameter settings. o Making the product usable on a VAXcluster. o Setting user account quotas. ____________________________________________________________ 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:RALLY$IVP.COM ____________________________________________________________ 3.2 Editing the System Startup File You must edit the system startup file to provide for auto- matic startup of VAX RALLY when your system is rebooted. After Installing VAX RALLY 3-1 Add the following command line to the system startup file, SYS$MANAGER:SYSTARTUP_V5.COM:. $ @ SYS$STARTUP:RALLY$STARTUP This command line starts VAX RALLY. If the installation procedure instructs you to add any other lines, be sure to add them. For example, you might be in- structed to add a line for the DATATRIEVE shareable image. The installation procedure also warns you if you have DATATRIEVE installed, but do not have a file called SYS$SHARE:DTRSHR.EXE. Some systems have multiple versions of DATATRIEVE running at the same time. On these sys- tems, instead of DTRSHR.EXE, there might be files such as DTRSHR50.EXE. In this case, RALLY asks you which file you want to use as your DATATRIEVE shareable image. It then de- fines a logical name RALLY$DTRSHR, pointing to the file you have chosen. You must place a line in SYSTARTUP_V5.COM to make this choice permanent. For example: DEFINE/SYSTEM/EXEC RALLY$DTRSHR SYS$SHARE:DTRSHR50 If you edit SYSTARTUP_V5.COM to include this line, RALLY uses DTRSHR50.EXE when RALLY users work with DATATRIEVE domains. If you have existing RALLY applications that use the BUFFER method (the Version 1 method) for invoking external program links and you wish to continue to use this method for invok- ing those links, then you must perform one of the following steps: o Modify SYSTARTUP_V5.COM to install your existing, buffer- method, 3GL link image as a shareable image. o Place your image in SYS$SHARE with the name RALLYEXT.EXE. o Define the logical RALLYEXT in SYSTARTUP_V5.COM to point to your shareable image. See the VAX RALLY Definition System User's Guide for more information about external program links. 3-2 After Installing VAX RALLY ____________________________________________________________ 3.3 Modifying System Parameters The installation for VAX RALLY requires that you raise the value of the CLISYMTBL system parameter. Once the installa- tion is complete, lower this value to ensure efficient system performance. ____________________________________________________________ 3.4 Installing VAX RALLY on a VAXcluster If you want to run RALLY on multiple nodes of a VAXcluster, first check to see that you have the appropriate software license. Refer to the VMS License Management Utility Manual for directions on how to load the license on nodes licensed to use RALLY. To install RALLY on a VAXcluster, log in to the SYSTEM ac- count or an account that has SYSPRV and repeat the following steps on each node in the cluster licensed to run RALLY: 1. Make sure that the SYSGEN parameters are properly set. 2. Issue the LICENSE LOAD command to activate the VMS li- cense. 3. Replace the DCLTABLES image using the INSTALL utility as follows: $ INSTALL REPLACE SYS$SHARE:DCLTABLES 4. Execute the RALLY startup file as follows: $ @SYS$STARTUP:RALLY$STARTUP 5. Execute the Installation Verification Procedure (IVP) to verify the installation as follows: $ @SYS$COMMON:[SYSTEST]RALLY$IVP.COM ____________________________________________________________ 3.5 User Account Requirements To work with VAX RALLY, user accounts on your system must have certain privileges and quotas. Sections 3.5.1 and 3.5.2 contain information on these requirements. After Installing VAX RALLY 3-3 ____________________________________________________________ 3.5.1 Privileges RALLY uses temporary mailboxes to communicate with users. To use VAX RALLY, each account must have at least TMPMBX priv- ilege. In addition, users who use RALLY to access databases on other nodes of a network need NETMBX privilege. Use the VMS Authorize Utility to determine whether users have the privileges they require. For example: $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> MODIFY WILLIAMSON/PRIV=(TMPMBX,NETMBX)/DEFPRIV=(TMPMBX,NETMBX) UAF> EXIT $ ____________________________________________________________ 3.5.2 User Account Quotas You must make sure that the appropriate user accounts have sufficient quotas to be able to use VAX RALLY. The process quotas listed in Table 1-6 apply to RALLY user accounts as well as to the installation account. Note that the value of BYTLM is not automatically checked when running a RALLY application. The values in Table 1-6, particularly the working set quotas, are minimum values. RALLY applications will provide better response if you provide additional memory. As a rule of thumb, you should set WSQUOTA to 1024 and WSEXTENT equal to (but not greater than) the value of the SYSGEN parameter WSMAX. In addition, RALLY users who have Rdb/VMS transactions that lock large numbers of records will need an enqueue limit (ENQLM) higher than the minimum shown in Table 1-6. Values of 1000 to 1200 or more may be required for defining and running complex RALLY applications that work with many relations and records at once. For optimal settings, refer to the VAX Rdb/VMS Installation Guide. See Section 1.4.4 for a description of how to verify and change account quotas. 3-4 After Installing VAX RALLY ____________________________________________________________ 3.6 Customizing RALLY Error and Message Files This section describes a method of making the run-time error and help messages support the following languages: o Danish o French o German o Hebrew o Spanish o Swedish If the RALLY run-time system example files are installed on the system, the following files will be in RALLY$EXAMPLES: o RALLY$ERRORS_DANISH.RGE o RALLY$MESSAGE_DANISH.EXE o RALLY$ERRORS_FRENCH.RGE o RALLY$MESSAGE_FRENCH.EXE o RALLY$ERRORS_GERMAN.RGE o RALLY$MESSAGE_GERMAN.EXE o RALLY$ERRORS_HEBREW.RGE o RALLY$MESSAGE_HEBREW.EXE o RALLY$ERRORS_SPANISH.RGE o RALLY$MESSAGE_SPANISH.EXE o RALLY$ERRORS_SWEDISH.RGE o RALLY$MESSAGE_SWEDISH.EXE For each language, there are two files: a RALLY error file (with file type .RGE) and a VMS message file (with file type .EXE). The RALLY error file contains error messages that appear within a RALLY error task. The VMS message file contains other error text. After Installing VAX RALLY 3-5 In addition to these files, RALLY$MESSAGE.MSG, the RALLY message source file, is copied to RALLY$EXAMPLES. You will need this file if you need to implement run-time error and help message support for languages other than those supplied in the RALLY kit. If your users require error and help message support in one of these languages, follow this procedure to customize the error and help message files. The VAX RALLY Definition System User's Guide describes how to create and install error and help message files for languages other than those supplied in the RALLY kit. 3-6 After Installing VAX RALLY NOTE The following procedure should be performed by the system manager. This procedure will affect all RALLY users on a system. 1. Copy the desired message file to SYS$MESSAGE and rename the file to RALLY$MESSAGE.EXE. For example: $ COPY RALLY$EXAMPLES:RALLY$MESSAGE_FRENCH.EXE - _$ SYS$MESSAGE:RALLY$MESSAGE.EXE 2. Copy the error file to SYS$LIBRARY and rename the file to RALLY$ERRORS.RGE. For example: $ COPY RALLY$EXAMPLES:RALLY$ERRORS_FRENCH.RGE - _$ SYS$LIBRARY:RALLY$ERRORS.RGE NOTE To use the Hebrew error and message files, you must have a Hebrew terminal. ____________________________________________________________ 3.7 Shutting Down VAX RALLY RALLY provides a shutdown procedure, RALLY$STOP.COM, that de-assigns logicals and de-installs images set up by RALLY$STARTUP.COM. The installation procedure copies the file to SYS$MANAGER. You do not need to run RALLY$STOP.COM every time you shut down your system, but you can run it manually to shut down RALLY. After Installing VAX RALLY 3-7 Chapter 4 Maintaining VAX RALLY ________________________________________________________________ This chapter explains the procedure to follow if problems arise after installing RALDO023 or the RALRTO023. The sec- tions that follow explain o How to read a bugcheck dump file. o How to report a problem to the Customer Support Center. ____________________________________________________________ 4.1 Reading a Bugcheck Dump File Occasionally, a RALLY internal error generates a file called a bugcheck dump file. This file contains essential informa- tion about the error that occurred and the state of the system at the time of the er- ror. This information becomes vital in tracking down the cause of the error; it is also important to Digital in fixing possible internal RALLY problems. If such an error occurs, the message reports that RALLY is creating a file called RALLYBUGCHK.DMP This file is normally created in the directory associated with the SYS$LOGIN logical name. To find the error that caused the dump, enter the following command: $ SEARCH/WIN RALLYBUGCHK.DMP "****" Maintaining VAX RALLY 4-1 Asterisks mark the location of the error message in the file. The /WIN qualifier results in a five-line window. For example: $ SEARCH/WIN RALLYBUGCHK.DMP "****" 2 7FF2548C: 00000003 03000001 00379120 00000000 0000000C 7FF25A90 00000004 ***** Exception at 0008618B : TUT$$SCR_W_COPY + 00000CCA %NONAME-W-NOMSG, Message number 00000000 You can use this information in three ways: o Sometimes, this information can help you determine the cause of the error and work around it. o You can use this information when you call the Customer Support Center. o You should always include the entire bugcheck dump file when you submit an SPR to Digital. (When you submit a RALLY-related SPR, please describe what happened preceding the error. Such contextual information is very useful to us in diagnosing a problem.) ____________________________________________________________ 4.2 Reporting Problems to Digital Make sure you know your access number before you call the Customer Support Center (CSC), and use the access number to identify yourself when you call. Treat the access number and the telephone numbers of the CSC confidentially. You should designate CSC contact people in your organization, and only these people should know the CSC access numbers. The contact people you designate can speak directly with a CSC team specialist. The CSC will call the contact people directly to deliver a solution, request more information, or confirm a solution previously delivered. The CSC will be able to respond faster and more accurately if you have complete information available when you call. Preparing a statement of the problem and thinking through the sequence of events that led to its occurrence can eliminate the need for calls from the CSC to gather more information. The specialist can focus immediately on isolating and analyz- ing the problem, rather than on defining it. 4-2 Maintaining VAX RALLY The following list of questions helps you collect supporting information that is often overlooked, but is essential to understanding a problem in its context. Try to write down an answer to each question and have the list of answers ready when you call the CSC. 1. What RALLY kit is installed on your system (VAX RALLY, which includes the Definition System and the Run-Time System, or the VAX RALLY Run-Time Option, which includes only the Run-Time System)? 2. What related software are you running and what are the version numbers (VMS operating system, prerequisite soft- ware, and any optional software)? Are these the most current versions available? 3. In what environment or under what conditions does the problem occur (for example, interactive, network, loaded or single user system)? 4. Have any changes occurred with the software or its usage that might correlate with the incidence of the problem such as: o Installing new prerequisite or optional software? o Upgrading existing software? 5. If the problem occurs in the Definition System environ- ment o What menu path did you take to get to the problem area? o What is the exact error you are receiving? 6. If the problem occurs in the Run-Time System environment o What is the exact error you are receiving? o What has changed since the application last worked suc- cessfully (for example, data, application definition, system parameters)? 7. If the Definition System or Run-Time System worked suc- cessfully before, but does not now, will it work under the old conditions? Have you saved a copy of the application file or generated application to check this? Maintaining VAX RALLY 4-3 8. Can you reproduce the problem with a short example? This will help the CSC team specialist in reproducing the prob- lem. It can be particularly helpful if you can reproduce the problem using the files supplied in the RALLY$EXAMPLES directory. 4-4 Maintaining VAX RALLY Appendix A Files and Logical Names Installed on Your System ________________________________________________________________ The VAX RALLY installation procedure installs a number of files on your system and defines some logical names. Sections A.1 and A.2 list the files installed. Section A.3 lists the logical names that are added to the system logical name table. Note that the RALDO023 kit contains all the files that are in the Run-Time Option kit. ____________________________________________________________ A.1 VAX RALLY Files When you install the RALLY development option, the following files are transferred to your system: SYS$HELP:RALLY023.RELEASE_NOTES Online Release Notes SYS$HELP:RALLY023_RELEASE_NOTES.LN03 Online Release Notes, LN03 format SYS$HELP:RALLY023_RELEASE_NOTES.PS Online Release Notes, POSTSCRIPT format SYS$LIBRARY:RALLY$ALLIN1.COM Runs RALLY from within ALL-IN-1 SYS$LIBRARY:RALLY$CI_DEFINITIONS.ADA Callable interface include file SYS$LIBRARY:RALLY$CI_DEFINITIONS.BAS Callable interface include file SYS$LIBRARY:RALLY$CI_DEFINITIONS.FOR Callable interface include file SYS$LIBRARY:RALLY$CI_DEFINITIONS.H Callable interface include file SYS$LIBRARY:RALLY$CI_DEFINITIONS.MAR Callable interface include file SYS$LIBRARY:RALLY$CI_DEFINITIONS.PAS Callable interface include file SYS$LIBRARY:RALLY$CI_DEFINITIONS.PLI Callable interface include file SYS$LIBRARY:RALLY$CI_DEFINITIONS.R32 Callable interface include file SYS$LIBRARY:RALLY$CI_DEFINITIONS.TLB Callable interface text library Files and Logical Names Installed on Your System A-1 SYS$LIBRARY:RALLY$CLD.EXE Command line processing SYS$LIBRARY:RALLY$EDT.RGK EDT key definitions SYS$LIBRARY:RALLY$EDT_NUMERIC.RGK EDT/numeric keypad SYS$LIBRARY:RALLY$EMPTY.RGA Empty application file SYS$LIBRARY:RALLY$ERRORS.RGE Non-fatal error messages SYS$LIBRARY:RALLY$EXTERNAL_TV.OBJ Buffer method 3GL exits - transfer vectors SYS$LIBRARY:RALLY$EXTERNAL.EXE External program stub SYS$LIBRARY:RALLY$HELP.RGH Internal command line help SYS$LIBRARY:RALLY$PRINTER.RGP Printer output formatting data file SYS$LIBRARY:RALLY$RDS.RGA Definer application file SYS$LIBRARY:RALLY$RDS_ERRORS.RGE Definer non-fatal error messages SYS$LIBRARY:RALLY$RDS_HELP.RGH Definer internal help messages SYS$LIBRARY:RALLY$SHARE.EXE RALLY shareable image SYS$LIBRARY:RALLY$TERMINALS.TXT Definition builder data file SYS$LIBRARY:RALLY$UTILITIES.DAT Definer utilities data file SYS$LIBRARY:RALLY$WPS.RGK WPS key definitions SYS$LIBRARY:RALLY$WPS_NUMERIC.RGK WPS/numeric keypad SYS$LIBRARY:RALLY_EDT.RGK Version 1 EDT key definitions SYS$LIBRARY:RALLY_EDT_132.RGK Version 1 EDT/132 column mode SYS$LIBRARY:RALLY_EDT_NUMERIC.RGK Version 1 EDT/numeric keypad SYS$LIBRARY:RALLY_EDT_VAXSTATION.RGK Version 1 EDT/132 columns, 60 lines SYS$LIBRARY:RALLY_WPS.RGK Version 1 WPS key definitions SYS$LIBRARY:RALLY_WPS_132.RGK Version 1 WPS/132 column mode SYS$LIBRARY:RALLY_WPS_NUMERIC.RGK Version 1 WPS/numeric keypad SYS$LIBRARY:RALLY_WPS_VAXSTATION.RGK Version 1 WPS/132 columns, 60 lines SYS$MESSAGE:RALLY$MESSAGE.EXE RALLY message file SYS$STARTUP:RALLY$STARTUP.COM Startup command procedure SYS$MANAGER:RALLY$STOP.COM Shutdown command procedure SYS$SYSTEM:RALLY$MAIN.EXE RALLY Run-Time image SYS$SYSTEM:RALLY$RDS_MAIN.EXE RALLY Definition System image SYS$SYSTEM:RALLYRDS.EXE Image stub required for TEAMDATA A-2 Files and Logical Names Installed on Your System SYS$TEST:RALLY$IVP.COM RALLY IVP command procedure SYS$LIBRARY:RALLY$ODI_DEFINITIONS.ADA ODI interface include file SYS$LIBRARY:RALLY$ODI_DEFINITIONS.BAS ODI interface include file SYS$LIBRARY:RALLY$ODI_DEFINITIONS.FOR ODI interface include file SYS$LIBRARY:RALLY$ODI_DEFINITIONS.H ODI interface include file SYS$LIBRARY:RALLY$ODI_DEFINITIONS.MAR ODI interface include file SYS$LIBRARY:RALLY$ODI_DEFINITIONS.PAS ODI interface include file SYS$LIBRARY:RALLY$ODI_DEFINITIONS.PLI ODI interface include file SYS$LIBRARY:RALLY$ODI_DEFINITIONS.R32 ODI interface include file SYS$LIBRARY:RALLY$ODI_DEFINITIONS.TLB Callable interface text library If you choose to install the Definition System examples, the following files are transferred to your system: RALLY$EXAMPLES:RALLY$3GL.BAS 3GL application example RALLY$EXAMPLES:RALLY$3GL.C 3GL application example RALLY$EXAMPLES:RALLY$3GL.COB 3GL application example RALLY$EXAMPLES:RALLY$3GL.COM 3GL application command procedure RALLY$EXAMPLES:RALLY$3GL.FOR 3GL application example RALLY$EXAMPLES:RALLY$3GL.RGA 3GL application example RALLY$EXAMPLES:RALLY$3GL_LINK.COM 3GL application link command procedure RALLY$EXAMPLES:RALLY$3GL_LINK_TV.MAR 3GL application transfer vectors RALLY$EXAMPLES:RALLY$APPLICATION_USERS_GUIDE.SDML Online Application User's Guide RALLY$EXAMPLES:RALLY$CI_FULL.COM Callable interface command procedure RALLY$EXAMPLES:RALLY$CI_FULL_BASIC.BAS Callable interface example RALLY$EXAMPLES:RALLY$CI_FULL_CC.C Callable interface example RALLY$EXAMPLES:RALLY$CI_COBOL.COB Callable interface example RALLY$EXAMPLES:RALLY$CI_SIMPLIFIED.COM Callable interface command procedure RALLY$EXAMPLES:RALLY$CI_SIMPLIFIED_BASIC.BAS Callable interface example RALLY$EXAMPLES:RALLY$CI_SIMPLIFIED_CC.C Callable interface example RALLY$EXAMPLES:RALLY$COMMERCE.RBR Commerce demo: Database backup file RALLY$EXAMPLES:RALLY$COMMERCE.RDB Commerce demo: Database file RALLY$EXAMPLES:RALLY$COMMERCE.RGA Commerce demo: Application file RALLY$EXAMPLES:RALLY$COMMERCE.SNP Commerce demo: Database snapshot file RALLY$EXAMPLES:RALLY$CREATE_TAPES.CDO CDO Command procedure RALLY$EXAMPLES:RALLY$EDT.RGC EDT-style key-to-command assignments RALLY$EXAMPLES:RALLY$SALES_INFO.RBR Sales demo: Database backup file RALLY$EXAMPLES:RALLY$SALES_INFO.RDB Sales demo: Database file RALLY$EXAMPLES:RALLY$SALES_INFO.RGA Sales demo: Application file RALLY$EXAMPLES:RALLY$SALES_INFO.SNP Sales demo: Database snapshot file RALLY$EXAMPLES:RALLY$WPS.RGC WPS-style key-to-command assignments Files and Logical Names Installed on Your System A-3 RALLY$EXAMPLES:RALLY$ODI_DIR.C ODI DSD directory demo: C code for ODI DSD functions RALLY$EXAMPLES:RALLY$ODI_DIR.CDO ODI DSD directory demo: CDO command procedure RALLY$EXAMPLES:RALLY$ODI_DIR.RGA ODI DSD directory demo: Application file RALLY$EXAMPLES:RALLY$ODI_DIR_LINK.COM ODI DSD directory demo: Link command procedure RALLY$EXAMPLES:RALLY$ODI_DIR.EXE ODI DSD directory demo: Shareable image RALLY$EXAMPLES:RALLY$COMMON_DSD_AGENT.COB ACMS example: DSD agent code RALLY$EXAMPLES:RALLY$CUST_DSD_AGENT.COB ACMS example: CUST_DSD agent code RALLY$EXAMPLES:RALLY$CUST_DSD_SERVER.COB ACMS example: CUST_DSD server code RALLY$EXAMPLES:RALLY$ODI_ACMS.RGA ACMS example: RALLY application file RALLY$EXAMPLES:RALLY$ODI_ACMS_APPL_BUILD.COM ACMS example: Build ACMS application procedure RALLY$EXAMPLES:RALLY$ODI_ACMS_COMPILE.COM ACMS example: Compile ACMS agent procedure RALLY$EXAMPLES:RALLY$ODI_ACMS_DICT_DEFN.COM ACMS example: CDD/Plus Dictionary Definitions RALLY$EXAMPLES:RALLY$ODI_ACMS_LINK.COM ACMS example: Link ACMS agent procedure RALLY$EXAMPLES:RALLY$ODI_ACMS_LOGICALS.COM ACMS example: Logicals RALLY$EXAMPLES:RALLY$ODI_ACMS_SERVER_LINK.COM ACMS example: Link ACMS server procedure RALLY$EXAMPLES:RALLY$RESV_DSD_AGENT.COB ACMS example: RESV_DSD agent code RALLY$EXAMPLES:RALLY$RESV_DSD_READ_SERVER.COB ACMS example: RESV_DSD server code RALLY$EXAMPLES:RALLY$RESV_DSD_UPD_SERVER.COB ACMS example: RESV_DSD server_code RALLY$EXAMPLES:RALLY$SQL_COMMIT.SQLMOD ACMS example: SQL module routine RALLY$EXAMPLES:RALLY$SQL_GET_CUST.SQLMOD ACMS example: SQL module routine RALLY$EXAMPLES:RALLY$SQL_GET_RESV.SQLMOD ACMS example: SQL module routine RALLY$EXAMPLES:RALLY$SQL_READ_TXN.SQLMOD ACMS example: SQL module routine RALLY$EXAMPLES:RALLY$SQL_ROLLBACK.SQLMOD ACMS example: SQL module routine RALLY$EXAMPLES:RALLY$SQL_RW_TXN.SQLMOD ACMS example: SQL module routine RALLY$EXAMPLES:RALLY$SQL_UPDATE_RESV.SQLMOD ACMS example: SQL module routine RALLY$EXAMPLES:ODI_ACMS_AGENT_LIB.TLB ACMS example: Text library RALLY$EXAMPLES:ODI_ACMS_APPL.ADF ACMS example: ACMS application definition file RALLY$EXAMPLES:ODI_ACMS_CUST_TASK.TDF ACMS example: ACMS task definition file A-4 Files and Logical Names Installed on Your System RALLY$EXAMPLES:ODI_ACMS_GROUP.GDF ACMS example: ACMS group definition file RALLY$EXAMPLES:ODI_ACMS_RESV_READ_TASK.TDF ACMS example: ACMS task definition file RALLY$EXAMPLES:ODI_ACMS_RESV_UPDATE_TASK.TDF ACMS example: ACMS task definition RALLY$EXAMPLES:RDS_WPS.RGC OLD WPS-style key-to-command assignments RALLY$EXAMPLES:RDS_EDT.RGC OLD EDT-style key-to-command assignments RALLY$EXAMPLES:TAPES_DEFINE.RGM Tapes demo: macro definitions RALLY$EXAMPLES:ODI_ACMS_STARTUP.COM ACMS startup RALLY$EXAMPLES:ODI_ACMS_SYSTEM_LOGICALS.COM ACMS system logicals RALLY$EXAMPLES:RALLY$DECTRACE_REPORTS.RGA DECtrace reports example: RALLY application file RALLY$EXAMPLES:RALLY$DECTRACE_TRANSACTION DECtrace reports example: FIX fix _TYPES.RGF RALLY$EXAMPLES:RALLY$DECTRACE_REPORTS_EXE.EXE DECtrace reports example: shareable image If you choose to install the Run-Time System examples, the following files are transferred to your system: RALLY$EXAMPLES:RALLY$DEMO.COM Text demo file RALLY$EXAMPLES:RALLY$TAPES.COM Tapes demo: Command file RALLY$EXAMPLES:RALLY$TAPES.RBR Tapes demo: Database backup file RALLY$EXAMPLES:RALLY$TAPES.RDB Tapes demo: Database file RALLY$EXAMPLES:RALLY$TAPES.RGA Tapes demo: Application file RALLY$EXAMPLES:RALLY$TAPES.SNP Tapes demo: Database snapshot file RALLY$EXAMPLES:RALLY$TAPES.TXT Tapes demo: Explanation of application RALLY$EXAMPLES:RALLY$TAPES_RUN.RGM Tapes demo: Macros for running Tapes RALLY$EXAMPLES:RALLY$ERRORS_DANISH.RGE Non-fatal error messages (Danish) RALLY$EXAMPLES:RALLY$ERRORS_FRENCH.RGE Non-fatal error messages (French) RALLY$EXAMPLES:RALLY$ERRORS_GERMAN.RGE Non-fatal error messages (German) RALLY$EXAMPLES:RALLY$ERRORS_HEBREW.RGE Non-fatal error messages (Hebrew) RALLY$EXAMPLES:RALLY$ERRORS_SPANISH.RGE Non-fatal error messages (Spanish) RALLY$EXAMPLES:RALLY$ERRORS_SWEDISH.RGE Non-fatal error messages (Swedish) RALLY$EXAMPLES:RALLY$MESSAGE_DANISH.EXE RALLY message file (Danish) RALLY$EXAMPLES:RALLY$MESSAGE_FRENCH.EXE RALLY message file (French) RALLY$EXAMPLES:RALLY$MESSAGE_GERMAN.EXE RALLY message file (German) RALLY$EXAMPLES:RALLY$MESSAGE_HEBREW.EXE RALLY message file (Hebrew) RALLY$EXAMPLES:RALLY$MESSAGE_SPANISH.EXE RALLY message file (Spanish) RALLY$EXAMPLES:RALLY$MESSAGE_SWEDISH.EXE RALLY message file (Swedish) RALLY$EXAMPLES:RALLY$MESSAGE.MSG RALLY message source file Files and Logical Names Installed on Your System A-5 ____________________________________________________________ A.2 VAX RALLY Run-Time Option Files When you install the RALLY Run-Time Option, the following files are transferred to your system: SYS$HELP:RALLY023.RELEASE_NOTES Online Release Notes SYS$HELP:RALLY023_RELEASE_NOTES.LN03 Online Release Notes, LN03 format SYS$HELP:RALLY023_RELEASE_NOTES.PS Online Release Notes, POSTSCRIPT format SYS$LIBRARY:RALLY$ALLIN1.COM Runs RALLY from within ALL-IN-1 SYS$LIBRARY:RALLY$CLD.EXE Command line processing SYS$LIBRARY:RALLY$EDT.RGK EDT key definitions SYS$LIBRARY:RALLY$EDT_NUMERIC.RGK EDT/numeric keypad SYS$LIBRARY:RALLY$ERRORS.RGE Non-fatal error messages SYS$LIBRARY:RALLY$EXTERNAL.EXE External program stub SYS$LIBRARY:RALLY$HELP.RGH Internal command line help SYS$LIBRARY:RALLY$PRINTER.RGP Printer output formatting data file SYS$LIBRARY:RALLY$SHARE.EXE RALLY shareable image SYS$LIBRARY:RALLY$WPS.RGK WPS key definitions SYS$LIBRARY:RALLY$WPS_NUMERIC.RGK WPS/numeric keypad SYS$LIBRARY:RALLY_EDT.RGK Version 1 EDT key definitions SYS$LIBRARY:RALLY_EDT_132.RGK Version 1 EDT/132 column mode SYS$LIBRARY:RALLY_EDT_NUMERIC.RGK Version 1 EDT/numeric keypad SYS$LIBRARY:RALLY_EDT_VAXSTATION.RGK Version 1 EDT/132 columns, 60 lines SYS$LIBRARY:RALLY_WPS.RGK Version 1 WPS key definitions SYS$LIBRARY:RALLY_WPS_132.RGK Version 1 WPS/132 column mode SYS$LIBRARY:RALLY_WPS_NUMERIC.RGK Version 1 WPS/numeric keypad SYS$LIBRARY:RALLY_WPS_VAXSTATION.RGK Version 1 WPS/132 columns, 60 lines SYS$MESSAGE:RALLY$MESSAGE.EXE VMS message file SYS$STARTUP:RALLY$STARTUP.COM Startup command procedure SYS$MAMAGER:RALLY$STOP.COM Shutdown command procedure SYS$SYSTEM:RALLY$MAIN.EXE RALLY Run-Time image SYS$SYSTEM:RALLYRDS.EXE Image stub required for TEAMDATA SYS$TEST:RALLY$IVP.COM RALLY IVP command procedure A-6 Files and Logical Names Installed on Your System If you decide to install the Run-Time System examples, the following files are transferred to your system: RALLY$EXAMPLES:RALLY$DEMO.COM Text demo file RALLY$EXAMPLES:RALLY$TAPES.COM Tapes demo: Command file RALLY$EXAMPLES:RALLY$TAPES.RBR Tapes demo: Database backup file RALLY$EXAMPLES:RALLY$TAPES.RDB Tapes demo: Database file RALLY$EXAMPLES:RALLY$TAPES.RGA Tapes demo: Application file RALLY$EXAMPLES:RALLY$TAPES.SNP Tapes demo: Database snapshot file RALLY$EXAMPLES:RALLY$TAPES.TXT Tapes demo: Explanation of application RALLY$EXAMPLES:RALLY$TAPES_RUN.RGM Tapes demo: Macros for running Tapes RALLY$EXAMPLES:RALLY$ERRORS_DANISH.RGE Non-fatal error messages (Danish) RALLY$EXAMPLES:RALLY$ERRORS_FRENCH.RGE Non-fatal error messages (French) RALLY$EXAMPLES:RALLY$ERRORS_GERMAN.RGE Non-fatal error messages (German) RALLY$EXAMPLES:RALLY$ERRORS_HEBREW.RGE Non-fatal error messages (Hebrew) RALLY$EXAMPLES:RALLY$ERRORS_SPANISH.RGE Non-fatal error messages (Spanish) RALLY$EXAMPLES:RALLY$ERRORS_SWEDISH.RGE Non-fatal error messages (Swedish) RALLY$EXAMPLES:RALLY$MESSAGE_DANISH.EXE RALLY message file (Danish) RALLY$EXAMPLES:RALLY$MESSAGE_FRENCH.EXE RALLY message file (French) RALLY$EXAMPLES:RALLY$MESSAGE_GERMAN.EXE RALLY message file (German) RALLY$EXAMPLES:RALLY$MESSAGE_HEBREW.EXE RALLY message file (Hebrew) RALLY$EXAMPLES:RALLY$MESSAGE_SPANISH.EXE RALLY message file (Spanish) RALLY$EXAMPLES:RALLY$MESSAGE_SWEDISH.EXE RALLY message file (Swedish) RALLY$EXAMPLES:RALLY$MESSAGE.MSG RALLY message source file ____________________________________________________________ A.3 Logical Names The following logical names are entered into the system log- ical name table when VAX RALLY is installed. These names are stored in the product's startup file. They are automati- cally entered into the system logical name table whenever the system reboots or whenever the software is invoked. RALLY$EXAMPLES SYS$SYSROOT:[SYSHLP.EXAMPLES.RALLY] RALLY$MESSAGE SYS$MESSAGE:RALLY$MESSAGE.EXE RALLY$ODI_DIR_EXE RALLY$EXAMPLES:RALLY$ODI_DIR.EXE RALLY$TAPES_DB RALLY$EXAMPLES:RALLY$TAPES.RDB RALLYEXT SYS$SHARE:RALLY$EXTERNAL.EXE RALLYSHR SYS$SHARE:RALLY$SHARE.EXE RALLY$DECTRACE_REPORTS_EXE RALLY$EXAMPLES:RALLY$DECTRACE_REPORTS_EXE.EXE Files and Logical Names Installed on Your System A-7 Appendix B Sample Installations ________________________________________________________________ This appendix illustrates sample installations of RALLY and the RALLY Run-Time Option. Your own installation might differ from these examples, because you can make different choices during the procedure. The first two examples show the installation procedure for RALLY. RALLY includes the RALLY Definition System and the RALLY Run-Time System. The last example shows the installation procedure for the RALLY Run-Time Option, which includes only the Run-Time System. ____________________________________________________________ B.1 Installing VAX RALLY The first example shows how to invoke the installation proce- dure for RALLY and get a copy of the release notes. In this example, the installer decides not to continue the installa- tion after retrieving the release notes. The second example shows how to invoke the installation for RALLY without the release notes option. It shows the installation of RALLY, the Definition System examples, and the Run-Time System examples. $ @SYS$UPDATE:VMSINSTAL RALDO023 MUA0: options n VAX/VMS Software Product Installation Procedure V5.3-1 It is 29-MAY-1991 at 17:44. Enter a question mark (?) at any time for help. Sample Installations B-1 * Are you satisfied with the backup of your system disk [YES]? Please mount the first volume of the set on MUA0:. * Are you ready? Y * %MOUNT-I-MOUNTED, RALDO mounted on _MUA0: The following products will be processed: RALDO V2.3 Beginning installation of RALDO V2.3 at 17:44 %VMSINSTAL-I-RESTORE, Restoring product saveset A... Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. Copy release notes to SYS$HELP 5. Do not display, print or copy release notes * Select option [2]:2 * Queue name [SYS$PRINT]: Job TMP (queue PRINT2_LP0, entry 658) started on PRINT2_LP0 * Do you want to continue the installation [N]? %VMSINSTAL-I-RELMOVED, The products release notes have been successfully moved to SYS$HELP. Installation of RALDO V2.3 completed at 17:48 VMSINSTAL procedure done at 17:48 In the following example, the installer invokes the installa- tion procedure without the release notes option. This example shows the installation of RALLY, the Definition System exam- ples, and the Run-Time System examples. $ @SYS$UPDATE:VMSINSTAL RALDO023 MUA0: VAX/VMS Software Product Installation Procedure V5.2-1 It is 29-MAY-1991 at 17:55. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? B-2 Sample Installations Please mount the first volume of the set on MUA0:. * Are you ready? Y * %MOUNT-I-MOUNTED, RALDO mounted on _MUA0: The following products will be processed: RALDO V2.3 Beginning installation of RALDO V2.3 at 17:56 %VMSINSTAL-I-RESTORE, Restoring product saveset A... %VMSINSTAL-I-RELMOVED, The products release notes have been successfully moved to SYS$HELP. ************************************************************ * * * VAX RALLY V2.3 * * Development Option Installation Procedure * * at 29-MAY-1991 17:57:06.65 * * * * Copyright (c) 1990, Digital Equipment Corporation * * * ************************************************************ * Do you want to install the RALLY Run-Time System examples [YES]? Y * Do you want to install the RALLY Definition System examples [YES]? Y * Do you want to purge files replaced by this installation [YES]? Y Product: RALLY Producer: DEC Version: 2.3 Release Date: 01-JUL-1990 * Does this product have an authorization key registered and loaded [YES]? Y ************************************************************ * * * Please wait while the system environment is validated. * * * ************************************************************ Sample Installations B-3 ************************************************************ * * * SYSTEM MANAGER: * * * * Add the following command(s) to the system startup file * * (for clusters, add to the startup file for each node * * licensed to run RALLY): * * * * $ @SYS$STARTUP:RALLY$STARTUP * * * ************************************************************ ************************************************************ * * * You've answered all of the questions. The installation * * will now continue for approximately 5 to 40 minutes. * * * ************************************************************ %VMSINSTAL-I-RESTORE, Restoring product saveset B... %VMSINSTAL-I-RESTORE, Restoring product saveset C... %VMSINSTAL-I-RESTORE, Restoring product saveset D... %VMSINSTAL-I-RESTORE, Restoring product saveset E... %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... VAX RALLY: Assigning System-wide RALLY Logicals VAX RALLY: Installing RALLY images RALLY V2.3 Definition System IVP Verifying the locations of all non-example files... Verifying idents of RALLY images... Copying RALLY$TAPES application and database to SYS$SCRATCH for testing... Exercising RALLY Definition System... Exercising RALLY Run-Time System... Cleaning up... RALLY IVP succeeded. Installation of RALDO V2.3 completed at 18:20 VMSINSTAL procedure done at 18:20 B-4 Sample Installations ____________________________________________________________ B.2 Installing the VAX RALLY Run-Time Option This example shows the installation of the RALLY Run-Time Option and the Run-Time System examples. $ @SYS$UPDATE:VMSINSTAL RALRTO023 MUA0: VAX/VMS Software Product Installation Procedure V5.2-1 It is 29-MAY-1991 at 15:21. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? Please mount the first volume of the set on MUA0:. * Are you ready? Y * %MOUNT-I-MOUNTED, RALRTO mounted on _MUA0: The following products will be processed: RALRTO V2.3 Beginning installation of RALRTO V2.3 at 15:22 %VMSINSTAL-I-RESTORE, Restoring product saveset A... %VMSINSTAL-I-RELMOVED, The products release notes have been successfully moved to SYS$HELP. ************************************************************ * * * VAX RALLY V2.3 * * Run-Time Option Installation Procedure * * at 29-MAY-1991 15:23:53.02 * * * * Copyright (c) 1990, Digital Equipment Corporation * * * ************************************************************ * Do you want to install the RALLY Run-Time System examples [YES]? Y * Do you want to purge files replaced by this installation [YES]? Y Product: RALLY-RT Producer: DEC Version: 2.3 Release Date: 01-JUL-1990 Sample Installations B-5 * Does this product have an authorization key registered and loaded? [YES]? Y ************************************************************ * * * Please wait while the system environment is validated. * * * ************************************************************ ************************************************************ * * * SYSTEM MANAGER: * * * * Add the following command(s) to the system startup file * * (for clusters, add to the startup file for each node * * licensed to run RALLY): * * * * $ @SYS$STARTUP:RALLY$STARTUP * * * ************************************************************ ************************************************************ * * * You've answered all of the questions. The installation * * will now continue for approximately 5 to 40 minutes. * * * ************************************************************ %VMSINSTAL-I-RESTORE, Restoring product saveset B... %VMSINSTAL-I-RESTORE, Restoring product saveset C... %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... VAX RALLY: Assigning System-wide RALLY Logicals VAX RALLY: Installing RALLY images RALLY V2.3 Run-Time System IVP Verifying the locations of all non-example files... Verifying idents of RALLY images... Copying RALLY$TAPES application and database to SYS$SCRATCH for testing... Exercising RALLY Definition System... Exercising RALLY Run-Time System... Cleaning up... RALLY IVP succeeded. Installation of RALRTO V2.3 completed at 15:36 VMSINSTAL procedure done at 15:37 B-6 Sample Installations Index ________________________________________________________________ B___________________________ External program link, Backing Up BUFFER method, 3-2 System Disk, 1-14 BUFFER method applications, F___________________________ 3-2 Files transferred during Bugcheck dump file, 4-1 installation C for VAX RALLY, A-1 ____________________________ for VAX RALLY Run-Time Calculating values Option, A-6 GBLPAGES, 1-9 GBLSECTIONS, 1-9 H___________________________ Customizing error and help Hardware required for message files, 3-5 installation, 1-2 D___________________________ Help message files DATATRIEVE, 2-9 customizing, 3-5 Definition System kit, 2-1 I___________________________ Development option kit, 2-1 Installation Disk space required for files transferred, A-1 installation, 1-6 logical names defined, A-7 E sample log ____________________________ for Run-Time Option, Error message files B-5 customizing, 3-5 for VAX RALLY, B-1, B-2 Error Recovery, 2-14 Installation Procedure, 2-1 to 2-14 Index-1 Installation Verification Prerequisite hardware, 1-2 Procedure Prerequisite software running for VAX RALLY Run-Time separately, 3-1 Option, 1-4 Installer privilege, 1-7t Privilege Installing VAX RALLY required for installation, On a VAXcluster, 3-3 1-6 L Privileges, 3-4 ____________________________ Problems License Management Facility, reporting to Digital, 4-2 1-5 Process Account Quotas, 1-12 License PAK, 1-5 installing account, 1-12 Registering, 1-5 R LMF ____________________________ Registering, 1-5 RALLYBUGCHK.DMP, 4-1 Logical names defined during Registering installation License Management for VAX RALLY, A-7 Facility, 1-5 M License Product ____________________________ Authorization Key, 1-5 Memory required for PAK, 1-5 installation, 1-2 Required hardware, 1-2 Required privilege O___________________________ for installation, 1-7 Optional software Required software for VAX RALLY development for VAX RALLY development option, 1-3 option, 1-2 for VAX RALLY run-time for VAX RALLY Run-Time option, 1-4 Option, 1-4 Run-Time Option kit, 2-1 P___________________________ S___________________________ PAK Sample installation log Registering, 1-5 for Run-Time Option, B-5 Post-installation procedure, for VAX RALLY, B-1, B-2 3-1 to 3-7 Saveset, 2-12 Preparing account for Shutting Down VAX RALLY, 3-7 installation, 1-5 Software Prequisite software required for VAX RALLY development option, 1-2 Index-2 Software System startup file required (Cont.) editing, 3-1 for VAX RALLY U development option, ____________________________ 1-2 User Account Quotas, 3-4 for VAX RALLY Run-Time User Account Requirements, Option, 1-4 3-3 System parameters V modifying, 3-3 ____________________________ System parameter values VAXcluster changing with AUTOGEN, VAX RALLY Installation, 1-10 3-3 checking, 1-9 VAX RALLY setting Shutting Down, 3-7 dynamic, 1-11 VMSINSTAL Requirements, 1-14 settings, 1-8 Index-3