VAX Rdb/ELN Installation Guide Order Number: AA-AD76H-TE Revision/Update Information: This manual supersedes the VAX Rdb/ELN Installation Guide, AA-AD76F-TE Operating System and Version: VMS Versions 5.1, 5.2, 5.3, or 5.4 Software Version: VAX Rdb/ELN Version 2.3 Target Environment: VAXELN Versions 4.1 or 4.2 Digital Equipment Corporation Maynard, Massachusetts _____________________________________________________________ Revised, February 1991 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. Any 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 or 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, 1990, 1991 All rights reserved. Printed in U.S.A. The Reader's Comments form at the end of this document re- quests your critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: DEC, DECnet, VAX, VAX DOCUMENT, VAX Rdb/ELN, VAX Rdb/VMS, VAXcluster, VAXELN, VMS, and the DIGITAL logo. ML-S1541 This document was prepared with VAX DOCUMENT, Version 1.2. Contents ________________________________________________________________ __________________________________________________________ PREFACE vii ________________________________________________________________ CHAPTER 1 PLANNING THE INSTALLATION 1-1 1.1 PREREQUISITE SOFTWARE 1-1 1.1.1 Rdb/ELN Host Development Environment 1-1 1.1.2 The VAXELN Toolkit 1-2 1.1.3 Installing Rdb/ELN and Rdb/VMS on the Same Host System 1-2 1.2 DIRECTORIES AND FILES REQUIRED FOR INSTALLATION ON THE HOST SYSTEM 1-4 1.2.1 Library Files 1-4 1.2.2 System Files 1-5 1.3 DISK STORAGE REQUIREMENTS FOR INSTALLATION 1-5 1.3.1 Storage Requirements for One Disk 1-5 1.3.2 Storage Requirements for Two Disks 1-6 1.3.3 VMS Tailoring Kits 1-6 1.4 ACCOUNT AND SYSTEM REQUIREMENTS 1-6 1.4.1 Account Privileges and Quotas 1-6 1.4.2 System Parameter Requirements 1-8 1.5 PRELIMINARY INSTALLATION STEPS 1-10 1.5.1 Purge and Back Up the Installation (Target) Disk 1-10 1.5.2 Stop Interactive and Batch Processes 1-10 1.5.3 Stop Network Activity 1-11 iii 1.6 TIME REQUIRED FOR INSTALLATION 1-11 ________________________________________________________________ CHAPTER 2 INSTALLATION PROCEDURE 2-1 2.1 INSTALLATION INFORMATION 2-1 2.1.1 Files Installed on Your System 2-2 2.1.2 Release Notes 2-2 2.2 STEPS IN THE INSTALLATION PROCEDURE 2-2 2.3 INSTALLATION PROCEDURE EXAMPLE 2-6 ________________________________________________________________ CHAPTER 3 POSTINSTALLATION PROCEDURE 3-1 3.1 POSTINSTALLATION TASKS 3-1 3.2 RUNNING THE IVP IN A STANDALONE ENVIRONMENT 3-3 ________________________________________________________________ APPENDIX A INSTALLATION PROCEDURE EXAMPLE A-1 ________________________________________________________________ APPENDIX B SOFTWARE INSTALLATION KIT FILES B-1 iv ________________________________________________________________ APPENDIX C INSTALLATION MESSAGES C-1 C.1 INSTALLATION PROCEDURE MESSAGES C-2 C.2 IVP MESSAGES C-5 ________________________________________________________________ TABLES 1-1 Account Privileges and Quotas Required for Installation 1-7 B-1 Files Created or Copied by VAX Rdb/ELN Installation B-1 v Preface ________________________________________________________________ __________________________________________________________ Purpose of This Manual VAX Rdb/ELN, also referred to as Rdb/ELN in this manual, is a realtime relational database management system designed for use by applications running on networks of dedicated VAX/VMS computers. Like all Digital relational product family members, VAX Rdb/ELN is an implementation of the Digital Standard Relational Interface (DSRI) architecture. This manual describes the procedure for installing Rdb/ELN on a host development VAX/VMS system. __________________________________________________________ Intended Audience This manual is intended for individuals who are responsible for installing and maintaining VAX Rdb/ELN. __________________________________________________________ Operating System Information VAX Rdb/ELN applications are developed on the VMS operating system and run in the VAXELN realtime environment. For VAX Rdb/ELN V2.3, you need VMS Version 5.1, 5.2, 5.3, or 5.4 as well as VAXELN Version 4.1 or 4.2. vii Contact your Digital representative if you have questions about the compatibility of other software products with VAX Rdb/ELN. You can request the most recent copy of the VAX System Software Order Table/Optional Cross Reference Table, which will verify those versions of your operating system that are compatible with this version of VAX Rdb/ELN. __________________________________________________________ Structure of This Manual This manual consists of three chapters and three appendixes as follows: Chapter 1 tells how to plan for installing VAX Rdb/ELN. It describes the necessary software, system resources, process quotas, and so on required for the installation. Chapter 2 describes the installation procedure. Chapter 3 describes the postinstallation tasks. Appendix A provides a sample installation of VAX Rdb/ELN using the VAX/VMS V5.1 operating system. Appendix B lists the files installed on your system during the VAX Rdb/ELN installation. Appendix C lists the error messages that might appear during the installation. There is an explanation and user action provided for each message. viii __________________________________________________________ Conventions The following conventions for syntax and symbols are used throughout this manual in the presentation of interactive examples: ix _____________________________________________________________ Convention__Meaning__________________________________________ WORD An uppercase word in a syntax format is a key- word. You must include it in the statement if the clause is used. word A lowercase word in a syntax format indicates a syntax element that you supply. Italics Italics indicate a reference, in text, to a term(s) used in an example. Color Color in examples indicates user input. This symbol indicates the RETURN key. Unless otherwise indicated, end all user input lines in examples by pressing the RETURN key. This symbol indicates the TAB key. This symbol tells you to depress the CTRL (con- trol) key while pressing a letter key. $ The dollar sign represents the VMS system prompt. This symbol indicates that the VMS command inter- preter is ready for input. . . . A horizontal ellipsis means you can repeat the previous item. . . . A vertical ellipsis in an example means that information not directly related to the example ____________has_been_omitted.________________________________ x Chapter 1 Planning the Installation ________________________________________________________________ This chapter describes the requirements for installing VAX Rdb/ELN on the host development VMS system. Installation of the VAXELN target system is covered later. Before proceeding with the installation, read this chapter carefully and ensure that your system meets the requirements. This chapter covers: prerequisite software, directories and files required for installation, disk storage requirements for installation, and account and system requirements. If you are using a DECnet link between the VMS host and VAXELN target system, you must have compatible DECnet ver- sions installed on the host and the target. This manual does not describe the installation of VMS, VAXELN, or DECnet. __________________________________________________________ 1.1 Prerequisite Software The following sections describe the needed software for Rdb /ELN. __________________________________________________________ 1.1.1 Rdb/ELN Host Development Environment The VAX Rdb/ELN V2.3 host development environment can be installed and run on any VAX processor that supports the VMS Operating System Version 5.1, 5.2, 5.3, or 5.4. Planning the Installation 1-1 __________________________________________________________ 1.1.2 The VAXELN Toolkit The correct version of the VAXELN Toolkit must be installed on the host development system before you can install Rdb /ELN. Rdb/ELN V2.3 requires VAXELN Versions 4.1 or 4.2. To support Rdb/ELN, the VAXELN toolkit libraries should be configured to make G_FLOATING the default representation of double-precision floating-point numbers. This is done by executing the following command file: $ @ELN$:GFLOATRTL.COM System privilege is required to execute this command proce- dure (see Section 1.4 for the exact privileges needed). When you compile application programs, you will use the compiler's /G_FLOATING qualifier. See the VAX Rdb/ELN Guide to Application Development for further information. __________________________________________________________ 1.1.3 Installing Rdb/ELN and Rdb/VMS on the Same Host System VAX Rdb/VMS is not required in order to run Rdb/ELN. However, Rdb/VMS and Rdb/ELN can be installed on the same system without difficulty. If you have Rdb/VMS on your system, it must be Version 3.0 or later. If Rdb/VMS is installed on your system, you need to check whether SYS$SHARE:RDMSHR.EXE is a known installed image: $ INSTALL :== $INSTALL/COMMAND ! define foreign command to simplify typing $ INSTALL INSTALL> LIST SYS$SHARE:RDMSHR.EXE 1-2 Planning the Installation If SYS$SHARE:RDMSHR.EXE is a known image, you will receive output similar to the following: DISK$WORK4:.EXE RDMSHR;2 Open Shar Prot Lnkbl If SYS$SHARE:RDMSHR.EXE is not a known image, messages simi- lar to the following will appear: %INSTALL-W-FAIL, failed to LIST entry for DISK$WORK4:RDMSHR.EXE -INSTALL-E-NOKFEFND, Known File Entry not found If Rdb/VMS is installed on your system and you receive error messages as described above, you must make SYS$SHARE:RDMSHR.EXE a known image before installing Rdb/ELN. You can do this in one of two ways: 1. Execute the following commands before running any Rdb/ELN programs or utilities (including the Rdb/ELN installation procedure) each time you log onto the system: $ @SYS$MANAGER:RMONSTART.COM $ INSTALL INSTALL> LIST SYS$SHARE:RDMSHR.EXE DISK$WORK4:.EXE RDMSHR;2 Open Shar Prot Lnkbl INSTALL> EXIT $ 2. Have the system manager edit SYS$MANAGER:SYSTARTUP.COM to include the following command so RDMSHR.EXE is installed as a known image each time the system is rebooted: $ @SYS$MANAGER:RMONSTART.COM Planning the Installation 1-3 __________________________________________________________ 1.2 Directories and Files Required for Installation on the Host System The installation procedure creates the various files included in your VAX Rdb/ELN software installation kit (see Appendix B). These files can be classified as either library files or system files. __________________________________________________________ 1.2.1 Library Files The Rdb/ELN installation procedure creates some library files and copies them to the library directory [RDBB] on the disk you specify. If the [RDBB] directory does not already exist, the installation procedure creates it. The installation procedure also assigns the system logical name RDBB$LIBRARY to the [RDBB] directory. NOTE If the system logical name RDBB$LIBRARY already exists for software other than Rdb/ELN, you should use a different logical name for that software. The Rdb/ELN installation procedure also creates several li- brary files that are placed in the VAXELN directory [ELN], which has the system logical name ELN$. This directory and the logical name that points to it were created by the in- stallation of the VAXELN Toolkit on the host development system. Rdb/ELN automatically uses this directory; the files Rdb/ELN copies to the ELN$ directory might or might not be on the same disk or disks as the RDBB$LIBRARY files and the system files. See Appendix B for a complete list of the library files placed in the RDBB$LIBRARY and ELN$ directories. 1-4 Planning the Installation __________________________________________________________ 1.2.2 System Files The system files are created by the installation procedure and copied to several system directories on the system disk you specify. All files not installed as library files (that is, in the RDBB$LIBRARY or ELN$ directories) are installed as system files and placed in the appropriate directory. The system directories are: o [SYSMSG], which has the system logical name SYS$MESSAGE o [SYSEXE], which has the system logical name SYS$SYSTEM o [SYSLIB], which has the system logical name SYS$LIBRARY o [SYSHLP], which has the system logical name SYS$HELP See Appendix B for a list of the system files in these direc- tories. __________________________________________________________ 1.3 Disk Storage Requirements for Installation Depending on the available disk space on your VMS system, you will need at least one and possibly two disks to store the library and system files during the installation procedure. __________________________________________________________ 1.3.1 Storage Requirements for One Disk If there is enough space on one disk in your VMS system, you can use the same disk for both the library files and the system files. If one disk is used, it should have a peak of 9,132 free blocks, of which approximately 600 blocks are freed when the installation procedure completes. You can use the VMS command SHOW DEVICE to determine how much free space is available on the target disk. Planning the Installation 1-5 __________________________________________________________ 1.3.2 Storage Requirements for Two Disks If two disks are used (one for the library files and one for the system files), the library disk must be mounted and write-enabled before you begin the installation. o The disk the library files are copied to must have 3,300 free blocks. o The disk the system files are copied to must have 9,132 free blocks. Approximately 4,000 of these blocks are freed on the system disk when the installation procedure completes. You can use the VMS command SHOW DEVICE to determine how much free space is available on the target disks. __________________________________________________________ 1.3.3 VMS Tailoring Kits The VMS Tailoring Kits contain files (classes) which allow you to subset VMS for your particular requirements. Refer to the System Support Addendum (SSA) for more information. __________________________________________________________ 1.4 Account and System Requirements The following sections describe the process privileges and quotas and the system parameters needed to install and run VAX Rdb/ELN. __________________________________________________________ 1.4.1 Account Privileges and Quotas Typically, layered product installations are performed from a privileged system manager's account. In any case, the account from which you install Rdb/ELN should have the characteris- tics listed in Table 1-1. Use the VMS command SHOW PROCESS /QUOTA to list the quotas for the account. 1-6 Planning the Installation Table 1-1: Account Privileges and Quotas Required for ____________Installation_____________________________________ Privilege or Quota____________Description___________Minimum_Quota_Value___ SETPRV Allows you to set NA any privilege bit ASTLM AST queue limit 10 BIOLM Buffered I/O count 6 limit BYTLM Buffered I/O byte 8192 count limit DIOLM Direct I/O count 6 limit ENQLM Enqueue quota 70 FILLM Open file limit 10 PGFLQUOTA________Paging_file_size______3500__________________ NOTE All VAX Rdb/ELN users need SYSLCK privilege to lock system-wide resources. Make sure the account from which you will be installing Rdb /ELN has these privileges and quotas. If it does not, you can change these values with the AUTHORIZE utility. For example: Planning the Installation 1-7 $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> MODIFY SYSTEM/DIOLM=12 UAF> EXIT $ You must then log out and log in again for the changes to take effect. __________________________________________________________ 1.4.2 System Parameter Requirements If your system's working set (WSMAX) or process section count parameter (PROCSECTCNT) is too low, you might receive the error "Process/Global section table full" when you run the IVP. You might also receive errors if your system's symbol table limit (CLISYMTBL) is too low. To avoid such errors, make sure these parameters have at least the following values: o Both PROCSECTCNT and WSMAX system parameters should be set to at least the default value assigned by the SYSGEN utility. (The value might be greater than the default assigned by SYSGEN.) o The CLISYMTBL value should be at least 500. To determine the current value of these parameters, enter the following command: $ RUN SYS$SYSTEM:SYSGEN To check the process section count parameter, enter the following command at the SYSGEN> prompt: SYSGEN> SHOW PROCSECTCNT 1-8 Planning the Installation The following display should appear on the screen: Parameter_Name Current Default Minimum Maximum Unit -------------- ------- ------- ------- ------- -------- PROCSECTCNT 32 32 5 1024 Sections To check the working set, enter: SYSGEN> SHOW WSMAX The following display appears: Parameter_Name Current Default Minimum Maximum Unit -------------- ------- ------- ------- ------- ----- WSMAX 512 1024 60 64000 Pages To check the symbol table limit, enter: SYSGEN> SHOW CLISYMTBL The following display appears: Parameter_Name Current Default Minimum Maximum Unit -------------- ------- ------- ------- ------- ----- CLISYMTBL 500 500 10 500 Pages In the preceding examples, the CLISYMTBL is adequate, and PROCSECTCNT is set to the default (the Current and Default values are the same), but WSMAX is not. To modify these values, edit the file SYS$SYSTEM:MODPARAMS.DAT to include the correct values. Now you must run AUTOGEN to recompute the system parameters. Enter the following commands: $ @SYS$UPDATE:AUTOGEN SAVPARAMS GENPARAMS $ @SYS$UPDATE:AUTOGEN SETPARAMS REBOOT Since PROCSECTCNT and WSMAX are not dynamic parameters, you must reboot the system. AUTOGEN will perform an automatic shutdown and reboot when it has finished. Planning the Installation 1-9 __________________________________________________________ 1.5 Preliminary Installation Steps Before you run VMSINSTAL, you must perform the tasks de- scribed in the following sections. __________________________________________________________ 1.5.1 Purge and Back Up the Installation (Target) Disk To purge and back up the installation disk, perform these steps: 1. Log in to the system manager's account at the console terminal. 2. Remove all unwanted or redundant files from the installa- tion disk. 3. Back up the installation disk: $ BACKUP/IMAGE install-disk backup-device __________________________________________________________ 1.5.2 Stop Interactive and Batch Processes The steps to stop interactive and batch processes follow: 1. Make sure all users are logged out and all batch jobs are complete. If users are still on the system, notify them to log out. $ SHOW USERS $ SHOW SYSTEM/BATCH $ REPLY/BELL/ALL "" 2. Prevent users from gaining access to the system by dis- abling interactive logins. First check how many interac- tive logins are normally allowed on your system by typing: $ SET LOGINS/INTERACTIVE 1-10 Planning the Installation Note the displayed number so that you can reenable logins after the installation is complete. Now disable logins by typing: $ SET LOGINS/INTERACTIVE=0 __________________________________________________________ 1.5.3 Stop Network Activity 1. To stop network activity, make sure DECnet-VAX is inopera- tive: $ SHOW NETWORK If you receive the response "Network Unavailable," con- tinue with the installation procedure described in Chapter 2. If your DECnet is up and running, shut it down using the following commands: $ RUN SYS$SYSTEM:NCP NCP> SET EXECUTOR STATE SHUT NCP> EXIT $ __________________________________________________________ 1.6 Time Required for Installation Installing the VAX Rdb/ELN host development system should take approximately 20 minutes on a VAX system running VMS Version 5.0 or later. Planning the Installation 1-11 Chapter 2 Installation Procedure ________________________________________________________________ This chapter describes how to install Rdb/ELN: o It gives the steps you must take before beginning the installation. o It guides you through the steps for running the VMSINSTAL command procedure. VMSINSTAL moves the Rdb/ELN software from the distribution media to your system disk. Appendix A contains a sample installation dialogue. During the installation procedure, VMSINSTAL prompts you as described below. The default answer for each prompt is enclosed by square brackets [ ]. To take the default answer, press RETURN. You can obtain help information at any time during the execution of VMSINSTAL by entering a question mark (?). NOTE Perform all of the following steps in the given order. __________________________________________________________ 2.1 Installation Information The following sections contain information about files installed on your system and about accessing the Rdb/ELN Release Notes before completing the installation. Installation Procedure 2-1 __________________________________________________________ 2.1.1 Files Installed on Your System During the Rdb/ELN installation, a number of files are placed in various locations on your system. Appendix B lists these files. __________________________________________________________ 2.1.2 Release Notes Online release notes for Rdb/ELN are provided in the media kit. Once you have installed Rdb/ELN, the online release notes are stored in the file SYS$HELP:RDBB023.RELEASE_NOTES. __________________________________________________________ 2.2 Steps in the Installation Procedure The installation procedure follows: 1. Verify that you have enough space on the system (target) disk to carry out the installation procedure (see Chapter 1 for disk space requirements): $ SHOW DEVICE system-disk If you do not have enough space, remove some files from the target disk before you continue the installation. 2. VMS V5 supports the License Management Facility (LMF), a software product that makes supporting various features of the Digital Distributed Software Licensing Architecture (DDSLA) possible on Rdb/ELN V2.3. You are required to reg- ister a Product Authorization Key (PAK). To obtain and register your PAK, contact your Digital representative. Refer to the VMS License Management Utility Reference Manual for information pertaining to this command proce- dure, explanations of any messages or errors, any corre- sponding user actions required, and management features of LMF. 2-2 Installation Procedure NOTE In a VAXcluster environment, you should load the registered license on each node of the cluster from which the software is to be run. 3. Physically load the Rdb/ELN distribution media (tape or disk), but do not mount it (do not execute the MOUNT command). 4. Invoke the installation procedure with the following commands: $ SET DEFAULT SYS$UPDATE $ @VMSINSTAL RDBBnnn source-device: OPTIONS N o SYS$UPDATE is the directory name associated with the VMSINSTAL command procedure file. o RDBBnnn is the product name, or identifier, for the VAX Rdb/ELN development system. The string "nnn" represents the number of the Rdb/ELN version being installed. If you invoke VMSINSTAL without providing a product name, VMSINSTAL will prompt you for the product name. o Source-device is the disk or tape where VMSINSTAL mounts the distribution media, for example, MTA0:. Note that you must include the colon (:) with the source- device name. You can let VMSINSTAL prompt you for the source-device name. o Specify OPTIONS N to receive prompts about reviewing and/or printing the online Release Notes. 5. Check any warning messages that ask if you want to con- tinue. Correct any problems before continuing the instal- lation procedure. Otherwise, Digital might not support the resulting installation. For example: %VMSINSTAL-W-DECNET, Your DECnet network is up and running. * Do you want to continue anyway [NO]? Installation Procedure 2-3 If you answer no, VMSINSTAL returns you to Digital Command Language (DCL) command level. After you shut down the network, you must return to Step 3 and invoke VMSINSTAL again. 6. VMSINSTAL asks a series of questions: * Are you satisfied with the backup of your system disk [YES]? * Do you want to purge files replaced by this installation [YES]? * Do you want to run the IVP after the installation [YES]? 7. If the library disk is different from the system disk, the next prompt allows you to specify it. The library disk must be mounted. * Specify device for the RDBB library directory [system_device:]: If you only press RETURN, the library device will be the same as the system device. If the logical name RDBB$LIBRARY already exists (for in- stance, if you have an earlier version of Rdb/ELN in- stalled on your system), you will see a message to that effect. The installation procedure will ask if you want to con- tinue. If RDBB$LIBRARY exists because your system has an earlier version of Rdb/ELN installed, answer yes. If you are using the logical name RDBB$LIBRARY to refer to something else, you probably will have to discontinue the installation, remove the logical name from your system, and start the installation again. You will be prompted for, and must supply, a password for the RDB$REMOTE account. The installation procedure will not continue until a valid password is entered. You will have three chances to enter a valid password and correctly confirm it. The entire installation will fail if you do not enter and confirm the password correctly after three opportunities. 2-4 Installation Procedure The password you provide will be used for the RDB$REMOTE account and in the DECnet-VAX Network Control Program (NCP) object database on your VAX node. That is, the RDB$REMOTE password and the password assigned to the RDBSERVER.EXE image will be the same. RDBSERVER.EXE is the image supplied by Rdb/ELN that manages remote database access. In a VAXcluster environment, the installation procedure assigns the same password to RDB$REMOTE and RDBSERVER.EXE only on the node from which the installation took place. Note that when a process using the RDB$REMOTE account starts, it executes the RDB$REMOTE_LOGIN.COM proce- dure in SYS$COMMON:[RDB$REMOTE]. This procedure now includes security checks to ensure that the user is run- ning the RDBSERVER.EXE image (DECnet-VAX object number 35). RDBSERVER.EXE is the image supplied by Rdb/VMS that manages remote database access. 8. VMSINSTAL will now proceed with the installation auto- matically, including running the IVP if the default was specified. The IVP copies the Rdb/ELN sample databases to RDBB$LIBRARY and verifies the installation was successful. You might see a series of informational messages indi- cating that certain components whose names begin with the prefix VMI$ were not installed. Ignore these messages. When the IVP checks the error message facilities, it will display a series of error messages. Ignore these messages, which indicate that the message facility is working correctly. 9. Read the console log carefully. Look for error and warning messages that indicate manual tasks you must perform. Installation Procedure 2-5 The installation checks for any files named SYS$SYSTEM:EPRE.EXE. If it finds any files with this name, it prints a message warning you that an unsupported EPRE preprocessor is still installed on your system. You should use RDML instead. See Appendix C for more information about messages. __________________________________________________________ 2.3 Installation Procedure Example Appendix A contains a sample installation of VAX Rdb/ELN. The installation procedure was carried out on a VMS operating system, Version 5.1. It takes about 20 minutes after the tape is loaded. 2-6 Installation Procedure Chapter 3 Postinstallation Procedure ________________________________________________________________ This chapter contains information about activities to perform after the installation is complete. The first section de- scribes the postinstallation tasks. The second section tells how to run the IVP at a later time. __________________________________________________________ 3.1 Postinstallation Tasks After the installation is finished and you have checked the console log, you will need to perform the following tasks: 1. When the installation is finished, the logical name RDBB$LIBRARY will be defined system-wide. Edit the system start-up command procedure so RDBB$LIBRARY is defined each time the system is booted: $ DEFINE/SYSTEM/EXECUTIVE RDBB$LIBRARY disk:[RDBB] Note that SYSNAM privilege is required for this; other- wise, the /EXECUTIVE qualifier is ignored. 2. Restart DECnet by invoking the following command proce- dure: SYS$MANAGER:STARTNET.COM. Depending on the size of your network, this procedure may require several minutes. Postinstallation Procedure 3-1 3. Restore interactive logins to the number you noted at the beginning of the installation: $ SET LOGINS/INTERACTIVE=saved-number 4. For security reasons, the RDBSERVER_NCP.COM procedure now prompts you for the password to assign to the RDBSERVER object. For remote database access to work, you must as- sign the password entered during the installation pro- cedure. For example, if you assigned the password XBIG_ SECRETZ to the RDB$REMOTE account during the installation procedure on VAXcluster node JGLENN, you must log into nodes ALDRIN and YEAGER and enter: $ SET DEFAULT SYS$COMMON:[SYSMGR] $ @RDBSERVER_NCP Please enter the password for object name RDBSERVER: Please verify password: As with the DCL SET PASSWORD command, your input does not appear (echo) on the terminal. To protect against nonecho typing errors, you must enter the password twice. If you fail to input and verify the password correctly after three attempts, the RDBSERVER_NCP.COM procedure fails and the RDBSERVER object is not inserted into the node's DECnet object database. If this happens, you must repeat this fourth postinstallation task step again. Again, you do not have to run the RDBSERVER_NCP.COM proce- dure on the node from which the Rdb/ELN installation took place. The installation procedure executing on that node performed the RDBSERVER insertion into that node's DECnet object database. 5. When a process using the RDB$REMOTE account starts up, it executes the RDB$REMOTE_LOGIN.COM procedure written to your system by the installation procedure. The installa- tion guide states that this login procedure is written to SYS$COMMON:[RDB$REMOTE]. After the installation guide was 3-2 Postinstallation Procedure printed, the location for this login procedure changed to SYS$COMMON:[SYSEXE]. This login procedure now includes security checks to ensure that the user is running the RDBSERVER.EXE image (DECnet-VAX object number 35). To run product-specific files during the RDB$REMOTE ac- count login step, you must edit SYS$COMMON:[SYSEXE]RDB$REMOTE_ LOGIN.COM and insert the appropriate DCL commands. __________________________________________________________ 3.2 Running the IVP in a Standalone Environment The installation verification procedure (IVP) can be run after the installation procedure completes (that is, in a standalone environment) by typing the following command: $ @SYS$TEST:RDBELN$IVP.COM During the installation procedure, all the files needed to run the IVP are copied to the [RDBB] directory that has the logical name RDBB$LIBRARY. Because RDBB$LIBRARY is defined system-wide, you can execute the IVP from any directory in a standalone environment. Postinstallation Procedure 3-3 Appendix A Installation Procedure Example ________________________________________________________________ This appendix contains a sample installation for VAX Rdb/ELN. The installation was performed using VMS Version 5.1. This sample installation includes the Installation Verification Procedure (IVP) and Product Authorization Key (PAK). $ DIR/SIZE RDBB023 Directory DJB0:[KITS] RDBB023.A;7 630 RDBB023.B;3 3024 RDBB023.C;3 2934 RDBB023.D;3 1350 Total of 4 files, 7938 blocks. $ @SYS$UPDATE:VMSINSTAL VAX/VMS Software Product Installation Procedure V5.1 It is 25-JUN-1989 at 15:43. Enter a question mark (?) at any time for help. %VMSINSTAL-W-DECNET, Your DECnet network is up and running. * Do you want to continue anyway [NO]? YES * Are you satisfied with the backup of your system disk [YES]? YES * Where will the distribution volumes be mounted: djb0:[kits] Installation Procedure Example A-1 Enter the products to be processed from the first distribution volume set. * Products: rdbb023 * Options: The following products will be processed: RDBB V2.3 Beginning installation of RDBB V2.3 at 15:43 %VMSINSTAL-I-RESTORE, Restoring product saveset A ... %VMSINSTAL-I-REMOVED, The product's release notes have been successfully moved to SYS$HELP. ****************************************************************************** * * * VAX Rdb/ELN T2.3 * * ------------------ * * * ****************************************************************************** ****************************************************************************** * * * Rdb/ELN will allow you to have help displayed in one of two ways. * * 1. Type a ? anytime to any prompt. * * 2 Answer yes to the next question and you will get help * * printed before each prompt. * * * ****************************************************************************** * Do you want help displayed before each prompt [YES]? YES ****************************************************************************** During this installation, new files will be provided to replace existing versions. You may purge these older versions to save disk space, or keep them if you feel they may be of use. Purging is recommended. * Do you want to purge files replaced by this installation [YES]? YES ****************************************************************************** Most products provide an Installation Verification Procedure (IVP) which verifies the completeness and accuracy of the installation. You may wish to run the IVP immediately after installation. * Do you want to run the IVP after the installation [YES]? YES A-2 Installation Procedure Example ****************************************************************************** A product authorization key specific to the following reference items should be registered and loaded: Product: RDB-ELN Producer: DEC Version: 2.3 Release Date: 15-FEB-1989 * Does this product have an authorization key registered and loaded? YES ****************************************************************************** ***************************************************************************** * * * Rdb/ELN needs a device for RDBB$LIBRARY. This device can be any valid * * disk on the system. If you have previously installed Rdb/ELN you * * should already have this device defined. The device shown in the * * brackets is your current one. If you want to keep it then type carriage * * return. If you want to select a new one or this is your first Rdb/ELN * * installation then enter a valid device. Please note this device must be * * mounted and writeable. In the case of the first time installation a * * carriage return will select the system disk. * * * ***************************************************************************** * Specify device for the RDBB library directory [DJB0:]: %RDBB-I-LIBRARY, The logical name RDBB$LIBRARY is defined for DJB0:[RDBB] %VMSINSTAL-I-SYSDIR, This product creates system disk directory DJB0:[RDBB]. ************************************************************* This installation requires the creation of the RDB$REMOTE account. You MUST choose a UIC and password for this account. PLEASE NOTE that your password for the RDB$REMOTE account and the network object RDBSERVER MUST be exactly the same. The password you supply for the RDB$REMOTE account will be used for the network object as well IF the account is created by this installation. Installation Procedure Example A-3 ************************************************************** ************************************************************* The installation procedure will not proceed until you enter a valid user identification code (UIC) for the RDB$REMOTE account. ************************************************************* * Enter UIC to be used for RDB$REMOTE account (e.g. [300,2]): [300,2] ************************************************************* The entire installation will FAIL if you do not enter a valid password for the RDB$REMOTE account. You will be given 3 chances to verify your password. This installation procedure requires at least 6 characters for the RDB$REMOTE password. Valid characters for a password are: A through Z a through z 0 through 9 $ (dollar sign) _ (underscore) As with the DCL SET PASSWORD command, your input will not appear on the terminal. And to protect against typing errors that are not seen when entering the password, you must enter the password twice. ************************************************************* * Please enter PASSWORD to be used for RDB$REMOTE account: * Please verify the PASSWORD entered for RDB$REMOTE: A-4 Installation Procedure Example ****************************************************************************** * * * The installation procedure requires no further input. * * * * Informational messages will be output to indicate the * * progress of the installation procedure. * * * ****************************************************************************** ****************************************************************************** * * * IMPORTANT * * --------- * * * * When this installation procedure is finished, you must: * * ------------------------------------------------------- * * * * Add the startup procedure SYS$MANAGER:RDBB$STARTUP.COM to * * SYS$MANAGER:SYSTARTUP_V5.COM * * * ****************************************************************************** %VMSINSTAL-I-RESTORE, Restoring product saveset B ... %VMSINSTAL-I-RESTORE, Restoring product saveset C ... %VMSINSTAL-I-RESTORE, Restoring product saveset D ... %RDBB-I-BLDHELP, Building the ERQL HELP library... %RDBB-I-RDBVER, Checking current versions of RDB... %RDBB-I-ACCOUNT, This installation creates an account named RDB$REMOTE. %RDBB-I-ADDNETDB, RDBSERVER has been placed in the DECnet object database as number 35. ************************************************************* In order to have remote access on another node which shares this cluster common root directory, you must insert RDBSERVER into that node's DECnet object database by: a) Logging into that node, and b) Invoking SYS$COMMON:[SYSMGR]RDBSERVER_NCP.COM. Installation Procedure Example A-5 This command procedure inserts RDBSERVER into the node's permanent DECnet object database. This procedure only needs to be executed ONCE per node. ************************************************************* %RDBB-I-RDML, Checking for any existing RDML components %RDBB-I-RDML, Installing RDML components %RDBB-I-INSTALL, Inserting module ERDBSHR in ELN$:RTLSHARE.OLB... %RDBB-I-HELP, Inserting Rdb/ELN HELP into the system HELP library... %RDBB-I-SYSFILES, Moving files into the SYSTEM directories... %RDBB-I-LIBFILES, Moving the LIBRARY files into the RDBB$LIBRARY directory... %RDBB-I-LINKERQL, Linking the image RDBBRQL %RDBB-I-IVPFILES, Moving the IVP files into the RDBB$LIBRARY directory... %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... ****************************************************************************** * * * Rdb/ELN T2.3 Installation Verification Procedure * * * * * * * * Recreate and populate the database with EBRP * * * A-6 Installation Procedure Example $ $ EBRP RESTORE RDBB$LIBRARY:PERSONNEL RDBB$LIBRARY:PERSONNEL Backed up by VAX Rdb/ELN Backup/Restore Processor (EBRP) V2.1-0 Source database was _$222$DUA6:[RDBELN.DEMO]PERSONNEL.RDB;4 An Rdb/ELN V2.0-0 database Page size was 1024 bytes It was logically backed up on 18-NOV-1987 02:08:54.38 Database DJB0:[RDBB]PERSONNEL.RDB;1 has been created. Page size is 1024 bytes. Now processing relation WORK_STATUS Now processing relation DEPARTMENTS Now processing relation COLLEGES Now processing relation SALARY_HISTORY Now processing relation RESUMES Now processing relation JOB_HISTORY Now processing relation JOBS Now processing relation EMPLOYEES Now processing relation DEGREES Now processing relation SALARY_REVIEW Now processing view CURRENT_SALARY Now processing view CURRENT_JOB Now processing view INFO EBRP Command Done $ * * * Access the database using ERQL * $ $ ERQL Rdb/ELN Query Language Interpreter Version T2.3 Type "HELP" or "?" for help Installation Procedure Example A-7 READY RDBB$LIBRARY:PERSONNEL FOR R IN RDB$RELATIONS SORTED BY R.RDB$RELATION_NAME PRINT R.RDB$RELATION_NAME END_FOR COLLEGES CURRENT_JOB CURRENT_SALARY DEGREES DEPARTMENTS EMPLOYEES INFO JOBS JOB_HISTORY RDB$CONSTRAINTS RDB$CONSTRAINT_RELATIONS RDB$DATABASE RDB$FIELDS RDB$IDS RDB$INDEX_SEGMENTS RDB$INDICES RDB$PAGES RDB$RELATIONS RDB$RELATION_FIELDS RDB$TUPLE_VERSIONS RDB$VIEW_RELATIONS RESUMES SALARY_HISTORY A-8 Installation Procedure Example SALARY_REVIEW WORK_STATUS FINISH EXIT $ $ * * Build and run an EPASCAL DML program to access the database * $ $ RDML/EPASCAL/OUTPUT=RDBB$LIBRARY:DEMO RDBB$LIBRARY:DEMO %RDML-I-GFLOATING, G_Floating datatypes detected in this module; use /G_FLOATING qualifier when compiling %RDML-I-SUMMARY, Completed with 0 Errors, 0 warnings, and 1 informational message Installation Procedure Example A-9 $ EPASCAL/G_FLOATING/NOLIST/OBJECT=RDBB$LIBRARY:DEMO RDBB$LIBRARY:DEMO $ LINK/EXECUTABLE=RDBB$LIBRARY:DEMO - RDBB$LIBRARY:DEMO,SYS$LIBRARY:RDMLRTL/LIB, - RDBB$LIBRARY:RDBELNLNK/OPT SYS$LIBRARY:VAXCRTLG.EXE/SHARE $ RUN RDBB$LIBRARY:DEMO Employee Id Employee City Degree 00187 Lasch Acworth BA 00198 Gehr Alstead BA 00218 Hall Alstead BA 00226 Boyd Alton BA 00185 Stadecker Alton BA 00174 Myotte Bennington BA 00249 Rodrigo Bennington BA 00166 Dietrich Boscawen BA 00223 Foote Boscawen BA 00214 Mellace Boscawen BA 00267 Saninocencio Boscawen BA 00228 Harrison Boston BA 00209 Smith Bristol BA 00232 McElroy Cambridge BA 00231 Clairmont Chocorua BA 00358 Lapointe Chocorua BA 00245 Roberts Chocorua BA 00239 Sarkisian Chocorua BA 00217 Siciliano Chocorua BA 00165 Smith Chocorua BA 00319 Silver Colebrook BA 00276 Watters Colebrook BA 00236 Gramby Etna BA 00169 Gray Etna BA 00177 Kinmonth Etna BA 00211 Gutierrez Farmington BA 00175 Siciliano Farmington BA 00196 Clarke Fremont BA 00204 Myotte Fremont BA 00183 Nash Fremont BA 00190 O'Sullivan Fremont BA A-10 Installation Procedure Example 00188 Clarke Jefferson BA 00206 Stornelli Jefferson BA 00170 Wood Jefferson BA 00234 Robinson Keene BA 00230 Tarbassian Keene BA 00219 Villari Keene BA 00186 Watters Keene BA 00191 Pfeiffer Marlborough BA 00167 Kilpatrick Marlow BA 00199 Nunez Meadows BA 00193 Reitchel Meadows BA 00325 Eiser Merrimack BA 00359 Crain Milan BA 00233 Mathias Milan BA 00213 Mercier Milan BA 00240 Johnson Milford BA 00354 Belliveau Milton BA 00287 Brown Milton BA 00184 Frydman Milton BA 00181 Reynolds Milton BA 00208 Sciacca Munsonville BA 00237 Burton Penacook BA 00192 Connolly Penacook BA 00471 Herbener Penacook BA 00242 Vormelker Rochester BA 00222 Lasch Salisbury BA 00221 Sullivan Sandown BA 00173 Bartlett Troy BA 00224 Manning Troy BA 00241 Keisling Twin Mountain BA 00210 Dietrich Whitefield BA 00238 Flynn Whitefield BA 00172 Peters Whitefield BA 00247 Ulrich Whitefield BA 00180 Canonica Wilmot BA 00195 Emery Wilmot BA 00227 Johnston Wolfeboro BA 00201 Clinton Wonalancet BA Installation Procedure Example A-11 00225 Jackson Wonalancet BA 00194 Morrison Wonalancet BA 00244 Boyd Acworth MA 00197 Danzig Acworth MA 00218 Hall Alstead MA 00416 Ames Alton MA 00226 Boyd Alton MA 00185 Stadecker Alton MA 00415 Mistretta Bennington MA 00174 Myotte Bennington MA 00369 Lapointe Boscawen MA 00267 Saninocencio Boscawen MA 00228 Harrison Boston MA 00217 Siciliano Chocorua MA 00164 Toliver Chocorua MA 00243 Dement Etna MA 00203 Gaudet Fremont MA 00202 Harrington Fremont MA 00190 O'Sullivan Fremont MA 00229 Robinson Fremont MA 00188 Clarke Jefferson MA 00206 Stornelli Jefferson MA 00230 Tarbassian Keene MA 00219 Villari Keene MA 00435 MacDonald Marlborough MA 00167 Kilpatrick Marlow MA 00205 Bartlett Meadows MA 00246 Lonergan Meadows MA 00168 Nash Meadows MA 00179 Dallas Milan MA 00233 Mathias Milan MA 00248 Klein Milford MA 00354 Belliveau Milton MA 00287 Brown Milton MA 00220 Gehr Milton MA 00237 Burton Penacook MA 00235 Clinton Penacook MA 00192 Connolly Penacook MA A-12 Installation Procedure Example 00471 Herbener Penacook MA 00374 Andriola Salisbury MA 00189 Lengyel Salisbury MA 00405 Dement Sanbornton MA 00207 Babbin Sanbornville MA 00212 Clarke Sandown MA 00171 D'Amico Sandown MA 00182 Iacobone Sandown MA 00221 Sullivan Sandown MA 00238 Flynn Whitefield MA 00176 Hastings Whitefield MA 00345 Stornelli Whitefield MA 00247 Ulrich Whitefield MA 00180 Canonica Wilmot MA 00195 Emery Wilmot MA 00200 Ziemke Winnisquam MA 00227 Johnston Wolfeboro MA 00201 Clinton Wonalancet MA 00225 Jackson Wonalancet MA 00244 Boyd Acworth PhD 00418 Blount Alstead PhD 00198 Gehr Alstead PhD 00416 Ames Alton PhD 00415 Mistretta Bennington PhD 00166 Dietrich Boscawen PhD 00232 McElroy Cambridge PhD 00164 Toliver Chocorua PhD 00169 Gray Etna PhD 00211 Gutierrez Farmington PhD 00203 Gaudet Fremont PhD 00204 Myotte Fremont PhD 00183 Nash Fremont PhD 00229 Robinson Fremont PhD 00234 Robinson Keene PhD 00186 Watters Keene PhD 00435 MacDonald Marlborough PhD 00246 Lonergan Meadows PhD 00168 Nash Meadows PhD Installation Procedure Example A-13 00359 Crain Milan PhD 00184 Frydman Milton PhD 00220 Gehr Milton PhD 00242 Vormelker Rochester PhD 00374 Andriola Salisbury PhD 00405 Dement Sanbornton PhD 00182 Iacobone Sandown PhD 00241 Keisling Twin Mountain PhD 00345 Stornelli Whitefield PhD * * Test help facilities * $ $ HELP EBRP RESTORE EBRP RESTORE Restores a database from a file created with BACKUP. Format: EBRP RESTORE backupfile dbfile Example: EBRP RESTORE RDBDEMO.RBR RDBDEMO.Rdb A-14 Installation Procedure Example $ * * Testing error facilities, DISREGARD any error messages * --------- $ EBRP RESTORE RDBB$LIBRARY:UNKNOWN_DB RDBB$LIBRARY:UNKNOWN_DB %PAS-F-FILNOTFOU, file not found File "BACKUP_FILE" Filename "DJB0:[RDBB]UNKNOWN_DB.;" -RMS-E-FNF, file not found $ $ ERDL RDBB$LIBRARY:UNKNOWN_RDL %RDBBUTL-F-BADFOPEN, Error opening input file 'DJB0:[RDBB]UNKNOWN_RDL.RDL;'. $ $ ERQL Rdb/ELN Query Language Interpreter Version T2.3 Type "HELP" or "?" for help READY RDBB$LIBRARY:UNKNOWN_DB %RDBBUTL-E-READYERR, Error readying database 'RDBB$LIBRARY:UNKNOWN_DB' $ $ RDML/EPASCAL RDBB$LIBRARY:UNKNOWN_FILE %RDML-F-ERROR_OPENING, Cannot open file 'DJB0:[RDBB]UNKNOWN_FILE.REP;' $ * * * Error facility testing COMPLETED * * * * * * Rdb/ELN T2.3 IVP Completed Successfully * * * ****************************************************************************** Restoring rdmlivp database Installation Procedure Example A-15 Backed up by Rdb/VMS V2.2-0 Backup/Restore utility An Rdb/VMS V2.2-0 database Source database was RDMLIVP.RDB It was logically backed up on 1-MAY-1987 14:05:52.85 Ignoring database access control information. Database DJB0:[RDBB]RDMLIVP.RDB;1 has been created. Page size is 1024 bytes. Ignoring access control information. Now processing relation EMPLOYEES EBRP Command Done Running the RDML/EPASCAL preprocessor test. Test completed successfully Running the RDML/PASCAL preprocessor test. Test completed successfully Installation of RDBB V2.2 completed at 16:24 Enter the products to be processed from the next distribution volume set. * Products: VMSINSTAL procedure done at 16:33 A-16 Installation Procedure Example Appendix B Software Installation Kit Files ________________________________________________________________ This appendix contains information about logical names and files that are installed on your system during the VAX Rdb /ELN installation. The following logical names are installed on your system: ELN$ == SYS$SYSDEVICE:[ELN] RDBB$LIBRARY == SYS$SYSDEVICE:[RDBB] Except for the sample databases, all of the files listed in Table B-1 are created or copied during the VAX Rdb/ELN installation procedure. You must run the Rdb/ELN Installation Verification Procedure (IVP) to install the sample database files. Table_B-1:__Files_Created_or_Copied_by_VAX_Rdb/ELN_Installation_ Files Added to RDBB, ELN, and SYSO (System) Directories____________________________________Block_Size_______ SYS$SYSDEVICE:[RDBB]DEMO.REP;1 11 SYS$SYSDEVICE:[RDBB]ERDBSHR.OLB;1 2063 SYS$SYSDEVICE:[RDBB]ERQLHELP.HLP;1 67 Software Installation Kit Files B-1 Table B-1 (Cont.): Files Created or Copied by VAX Rdb/ELN ____________________Installation________________________________ Files Added to RDBB, ELN, and SYSO (System) Directories____________________________________Block_Size_______ SYS$SYSDEVICE:[RDBB]ESORTLIB.OLB;1 93 SYS$SYSDEVICE:[RDBB]PERSONNEL.RBR;1 123 SYS$SYSDEVICE:[RDBB]PRODUCT_IDENT.OPT;1 1 SYS$SYSDEVICE:[RDBB]RDBBBRP.EXE;1 514 SYS$SYSDEVICE:[RDBB]RDBBHELP.HLP;1 28 SYS$SYSDEVICE:[RDBB]RDBBLOCK.EXE;1 98 SYS$SYSDEVICE:[RDBB]RDBBMSGS.OBJ;1 19 SYS$SYSDEVICE:[RDBB]RDBBRQL.EXE;1 535 SYS$SYSDEVICE:[RDBB]RDBBRQL.OPT;1 2 SYS$SYSDEVICE:[RDBB]RDBBSINIT.EXE;1 21 SYS$SYSDEVICE:[RDBB]RDBBSRVR.EXE;1 152 SYS$SYSDEVICE:[RDBB]RDBBUTL.OBJ;1 59 SYS$SYSDEVICE:[RDBB]RDBELN$IVP.COM;1 19 SYS$SYSDEVICE:[RDBB]RDBELNLNK.OPT;1 1 SYS$SYSDEVICE:[RDBB]RDBELNMSG.MAP;1 206 B-2 Software Installation Kit Files Table B-1 (Cont.): Files Created or Copied by VAX Rdb/ELN ____________________Installation________________________________ Files Added to RDBB, ELN, and SYSO (System) Directories____________________________________Block_Size_______ SYS$SYSDEVICE:[RDBB]RDBELNMSG.OPT;1 1 SYS$SYSDEVICE:[RDBB]RDBELN_STARLET.OLB;1 285 SYS$SYSDEVICE:[RDBB]RDB_MESSAGE.OBJ;1 18 SYS$SYSDEVICE:[RDBB]RDMLIVP.ANS;1 1 SYS$SYSDEVICE:[RDBB]RDMLIVP.COM;1 15 SYS$SYSDEVICE:[RDBB]RDMLIVP.RBR;1 1 SYS$SYSDEVICE:[RDBB]RDMLIVP.RC;1 1 SYS$SYSDEVICE:[RDBB]RDMLIVP.REP;1 1 SYS$SYSDEVICE:[RDBB]RDMLIVP.RPA;1 1 SYS$SYSDEVICE:[RDBB]SORMSG.OBJ;1 15 SYS$SYSDEVICE:[RDBB]WINGSTRUT.RBR;1 25 SYS$SYSDEVICE:[ELN]ERDBSHR.EXE;1 421 SYS$SYSDEVICE:[ELN]ERDBSHR.MAP;1 627 SYS$SYSDEVICE:[SYS0]RDB$REMOTE.DIR;1 1 SYS$SYSDEVICE:[SYS0.SYSEXE]EBRP.EXE;1 156 Software Installation Kit Files B-3 Table B-1 (Cont.): Files Created or Copied by VAX Rdb/ELN ____________________Installation________________________________ Files Added to RDBB, ELN, and SYSO (System) Directories____________________________________Block_Size_______ SYS$SYSDEVICE:[SYS0.SYSEXE]ERDL.EXE;1 608 SYS$SYSDEVICE:[SYS0.SYSEXE]ERQL.EXE;1 471 SYS$SYSDEVICE:[SYS0.SYSEXE]RDB$REMOTE_ 2 LOGIN.COM;1 SYS$SYSDEVICE:[SYS0.SYSEXE]RDBSERVER.COM;1 1 SYS$SYSDEVICE:[SYS0.SYSEXE]RDBSERVER.EXE;1 19 SYS$SYSDEVICE:[SYS0.SYSEXE]RDML.EXE;1 492 SYS$SYSDEVICE:[SYS0.SYSHLP]ERQLHELP.HLB;1 75 SYS$SYSDEVICE:[SYS0.SYSHLP]HELPLIB.HLB;4 1050 SYS$SYSDEVICE:[SYS0.SYSHLP]RDBB023.RELEASE_ 368 NOTES;1 SYS$SYSDEVICE:[SYS0.SYSHLP]RDBERROR_ 103 HELP.HLP;1 SYS$SYSDEVICE:[SYS0.SYSHLP]RDB_MSG.DOC;1 211 SYS$SYSDEVICE:[SYS0.SYSHLP]RDMLHELP.HLP;1 439 SYS$SYSDEVICE:[SYS0.SYSHLP]RDML_MSG.DOC;1 50 SYS$SYSDEVICE:[SYS0.SYSLIB]RDBBSHR.EXE;1 234 B-4 Software Installation Kit Files Table B-1 (Cont.): Files Created or Copied by VAX Rdb/ELN ____________________Installation________________________________ Files Added to RDBB, ELN, and SYSO (System) Directories____________________________________Block_Size_______ SYS$SYSDEVICE:[SYS0.SYSLIB]RDBSHR.EXE;1 152 SYS$SYSDEVICE:[SYS0.SYSLIB]RDMLEPAS.PAS;1 21 SYS$SYSDEVICE:[SYS0.SYSLIB]RDMLRTL.OLB;1 69 SYS$SYSDEVICE:[SYS0.SYSLIB]RDMLVAXC.H;1 38 SYS$SYSDEVICE:[SYS0.SYSLIB]RDMLVPAS.PAS;1 42 SYS$SYSDEVICE:[SYS0.SYSLIB]RDMMSGSHR.EXE;1 20 SYS$SYSDEVICE:[SYS0.SYSMGR]RDBB$STARTUP.COM;1 3 SYS$SYSDEVICE:[SYS0.SYSMGR]RDBSERVER_ 1 NCP.COM;1 SYS$SYSDEVICE:[SYS0.SYSMGR]VAXINFO$NETOBJ_ 12 INSERT.COM;1 SYS$SYSDEVICE:[SYS0.SYSMSG]RDBBMSGS.EXE;1 15 SYS$SYSDEVICE:[SYS0.SYSMSG]RDBELNMSG.EXE;1 158 SYS$SYSDEVICE:[SYS0.SYSMSG]RDBMSGS.EXE;1 16 SYS$SYSDEVICE:[SYS0.SYSMSG]RDBMSGS.MSG;1 155 SYS$SYSDEVICE:[SYS0.SYSMSG]RDMLMSG.EXE;1 17 Software Installation Kit Files B-5 Table B-1 (Cont.): Files Created or Copied by VAX Rdb/ELN ____________________Installation________________________________ Files Added to RDBB, ELN, and SYSO (System) Directories____________________________________Block_Size_______ SYS$SYSDEVICE:[SYS0.SYSMSG]RDMSMSG.EXE;1 54 SYS$SYSDEVICE:[SYS0.SYSMSG]VIDA_MESSAGE.EXE;1__33_______________ B-6 Software Installation Kit Files Appendix C Installation Messages ________________________________________________________________ This appendix describes messages that may appear during installation. Three different types of messages may appear, each with a different prefix: o RDBB-I- is the prefix for informational messages that do two things: - Provide you with information about the installation process - Alert you to problems, such as a write-locked disk, that you can fix without stopping the installation Installation will continue after you correct the error condition. o RDBB-W- is the prefix for warning messages. These messages may occur even in a successful installation to warn you of some condition that may affect the system adversely. o RDBB-E- is the prefix for error messages. These messages report fatal errors arising from the IVP, from the user exiting the installation process with , and from unexpected installation failures. All fatal errors automatically terminate the installation. Installation Messages C-1 The following section lists messages you might receive. Many of them contain substitution parameters. For example: No such device The token is replaced automatically with the device name, such as DUA1:. __________________________________________________________ C.1 Installation Procedure Messages The following messages are displayed if problems occur during the installation process. The prompt is repeated so you can correct the problem. RDBB-E-BADELNVER, RDBELN Vxxx requires VAXELN Vxxx or higher Explanation: The indicated VAXELN version is the prerequisite software for this version of Rdb/ELN. The installation has been aborted. Action: Install the correct version of VAXELN and re-try the installation. RDBB-E-BADVMSVER, RDBELN must be installed on VMS version xxx or higher Explanation: The indicated version of VMS (or higher) is the prerequisite software for this version of Rdb/ELN. The installation has been aborted. Action: Upgrade your VMS system to the indicated VMS version or higher and re-try the installation. RDBB-I-DEVNOTMOUNT, Device is not mounted Explanation: The library device is not mounted. Action: Mount the library device and reenter the name. RDBB-E-DISKSPACE, Insufficient space for installation-needs blocks C-2 Installation Messages Explanation: There is not enough space on the target disk. The installation has been aborted. Action: Clear space on the target disk by deleting, purging, or moving files. RDBB-E-NOVAXELN, VAXELN is not installed or the ELN$ logical is undefined Explanation: VAXELN is not installed on the system or the ELN$ logical name has not been defined. The installation has been aborted. Action: VAXELN must be installed before Rdb/ELN can be in- stalled. Re-try the installation after you have installed VAXELN. Once VAXELN is installed, define the ELN$ logical name. RDBB-I-INSTALL, Inserting module in ... Explanation: This message informs you the installation pro- cess is modifying either an object or shareable image library in ELN$. The installation modifies RTL.OLB and RTLSHARE.OLB. RDBB-I-INVDEVNAM, Invalid device name ) Explanation: The name supplied for the library device is invalid. Action: Reenter the name for the library device. RDBB-I-IVP, Now saving the IVP files into RDBB$LIBRARY:... Explanation: This message informs you that the installation process is saving the files needed to run the IVP. RDBB-I-LIBRARY, The logical name RDBB$LIBRARY is defined for [RDBB] Installation Messages C-3 Explanation: This message tells you where the library has been installed. RDBB-I-LOGNAMREP, The logical name RDBB$LIBRARY is already defined Explanation: The logical name RDBB$LIBRARY already exists and will be replaced if you proceed. Action: Consult with your system users to be sure that RDBB$LIBRARY can be deleted safely from the system logical name tables. RDBB-I-NOPRINT, Unable to print RELEASE NOTES, check SYS$PRINT queue Explanation: The installation procedure was unable to print the release notes. Action: Take corrective action on any error messages gen- erated just before this one. If you still cannot print the release notes, ask your system manager to check the SYS$PRINT queue. RDBB-I-NOSUCHDEV, No such device Explanation: The name supplied for the library device is invalid. Action: Reenter the name for the library device. RDBB-I-WRITELOCK, Volume on is write locked Explanation: The library device is write-locked. Action: Write-enable and physically mount the library device, then reenter the name. C-4 Installation Messages __________________________________________________________ C.2 IVP Messages The following messages are displayed if problems occur while the installation verification procedure runs. RDBB-E-NORDBB, can't translate RDBB$LIBRARY--Rdb/ELN may not be installed Explanation: Rdb/ELN may not have been installed on the system. The IVP checks to see if RDBB$LIBRARY is defined. Action: Make sure Rdb/ELN was installed successfully and that RDBB$LIBRARY is a system-defined logical name. RDBB-E-NOVAXELN, VAXELN is not installed or the ELN$ logical is undefined Explanation: VAXLEN is not installed on the system or the ELN$ logical name has not been defined. The IVP has been aborted. Action: You cannot run the IVP without VAXELN because the IVP checks to see if the ELN$ logical is defined and if the VAXELN PASCAL compiler is in SYS$SYSTEM. Make sure VAXELN is installed and ELN$ is defined. Re-try the IVP. RDBB-E-QUOTA_TOO_LOW, this account's quota is too low to run this IVP Explanation: The named account quota is too low. The IVP has been aborted. Action: Use AUTHORIZE to make certain the account has enough resources to run the IVP. If any changes are made, you must log out and log back in for the changes to take effect. Re- try the IVP. Installation Messages C-5