DEC_DB_Integrator_for_OpenVMS_________________ Installation Guide Part Number: AA-Q1SQB-TK November 1994 This guide describes how to install DEC DB Integrator on a VAX processor running the OpenVMS operating system, or on an AXP processor running the OpenVMS operating system. Revision/Update Information: This guide supersedes Versions 1.0, 1.0A, and 1.0B. Operating System: OpenVMS VAX OpenVMS AXP Software Version: DEC DB Integrator Version 3.1 Digital Equipment Corporation Maynard, Massachusetts __________________________________________________________ Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. © Digital Equipment Corporation 1994. All rights reserved. The following are trademarks of Digital Equipment Corporation: ACMS, ALL-IN-1, AlphaGeneration, AXP, Bookreader, CDD/Plus, CDD/Repository, CI, DEC, DEC Rdb, DEC TCP/IP, DECdecision, DECdtm, DECforms, DECintact, DECnet, DECnet-DOS, DECplan, DECpresent, DECtp, DECtrace, DECwindows, Digital, HSC, MASSBUS, MicroVAX, OpenVMS, PATHWORKS, RA, Rdb Language Translator, Rdb/VMS, SPM, ULTRIX, UNIBUS, VAX, VAX Ada, VAX BASIC, VAX C, VAX CDD, VAX COBOL, VAX DATATRIEVE, VAX DBMS, VAX DOCUMENT, VAX FMS, VAX FORTRAN, VAX MACRO, VAX Pascal, VAX Performance Advisor, VAX RALLY, VAX Rdb/ELN, VAX RMS, VAX SCAN, VAX 6000, VAX TEAMDATA, VAX Xway, VAXcluster, VAXELN, VAXset, VAXstation, VIDA, VMS, VMScluster, and the DIGITAL logo. The following are third-party trademarks: PostScript is a registered trademark of Adobe Systems Incorporated. Apple is a registered trademark of Apple Computer, Inc. CA-ACF2 is a trademark of Computer Associates International, Inc. Interbase is a registered trademark of Borland International, Inc. Cincom is a registered trademark of Cincom Systems, Inc. SequeLink is a trademark and is licensed by Digital Equipment Corporation, Maynard, Massachusetts, from GnOsIs NV 1990, and TechGnosis Incorporated 1991. TechGnosis is a registered trademark of GnOsIs NV. All rights reserved. HP and HP-UX are registered trademarks of Hewlett-Packard Company. API/SQL, EDA/Link, EDA/SQL, Enterprise Data Access, and Enterprise Data Access/SQL are trademarks of Information Builders, Inc. INFORMIX is a registered trademark of Informix Software, Inc. INGRES is a registered trademark of Ingres Corporation. IBM is a registered trademark of International Business Machines Corporation. DB2, CICS, CICS/ESA, CICS/MVS, MVS/ESA, MVS/XA, RACF, and VTAM are trademarks of International Business Machines Corporation. ACCESS, Microsoft, MS, and MS-DOS are registered trademarks of Microsoft Corporation. Windows is a trademark of Microsoft Corporation. OSF and OSF/1 are registered trademarks of the Open Software Foundation, Inc. ORACLE, SQL*Net, and SQL*Plus are registered trademarks of the Oracle Corporation. Pro*C is a trademark of Oracle Corporation. Powersoft is a registered trademark of Powersoft Corporation. PowerBuilder is a trademark of Powersoft Corporation. PROGRESS is a registered trademark of Progress Software Corp. GemBase is a registered trademark of Ross Systems. SmartStar is a registered trademark of SmartStar Corporation. ADABAS is a registered trademark of Software AG of North America, Inc. SYBASE is a registered trademark of Sybase, Inc. DB-Library, Open Client, SYBASE Open Server, and SYBASE SQL Server are trademarks of Sybase, Inc. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Ltd. All other trademarks and registered trademarks are the property of their respective holders. This document is available on CD-ROM. This document was prepared using VAX DOCUMENT Version 2.1. ________________________________________________________________ Contents Send Us Your Comments.................................... vii Preface.................................................. xi 1 Preparing for DBI Installation 1.1 Registering Your Software License............ 1-1 1.2 Required Hardware............................ 1-2 1.3 Required and Optional Software............... 1-2 1.3.1 Common Components Installation Requirement.............................. 1-4 1.3.1.1 Why You Must Install Common Components............................. 1-5 1.3.1.2 Checking for Common Components......... 1-6 1.3.2 DECdtm Services.......................... 1-7 1.3.3 Database Product Requirements............ 1-8 1.4 Installation Procedure Requirements.......... 1-10 1.4.1 Privileges............................... 1-10 1.4.2 Process Account Quotas................... 1-10 1.4.3 Required System Parameters............... 1-11 1.4.4 Required Disk Space...................... 1-12 1.4.5 System Disk Backup....................... 1-13 1.4.6 OpenVMS Help Library Use................. 1-13 1.5 Performing Standard System Maintenance Procedures................................... 1-13 1.5.1 Checking and Setting Process Account Quotas................................... 1-14 1.5.2 Checking System Parameter Values......... 1-14 1.5.3 Calculating the Values for Global Pages, Global Pagelets, and Global Sections..... 1-15 iii 1.5.4 Changing System Parameter Values with AUTOGEN.................................. 1-16 2 Installing DBI 2.1 Installation Procedure....................... 2-1 2.2 Error Recovery............................... 2-7 3 After Installation 3.1 Creating the Image for Use with ORACLE....... 3-1 3.2 Setting Up User Account Requirements......... 3-2 3.2.1 Granting Privileges...................... 3-2 3.2.2 Setting User Account Quotas.............. 3-2 3.2.3 Setting Up User Accounts................. 3-3 3.3 Running the Installation Verification Procedure Separately......................... 3-3 3.4 Editing the System Files..................... 3-3 3.5 Making the Product Usable on a VMScluster.... 3-4 A Prerequisite Installation of Common Components A.1 Common Components............................ A-1 A.1.1 Media Required........................... A-2 A.1.2 Version Variants and Existing Databases................................ A-2 A.2 Disk Space Required.......................... A-3 A.3 OpenVMS Privileges Required.................. A-3 A.4 Unlocking the Process Account Password....... A-5 A.5 Installing Common Components................. A-6 A.6 Installing Common Components Images as Shared....................................... A-8 A.6.1 Editing the Startup and Shutdown Procedures for Shared Images............. A-10 A.6.2 Verifying Global Pages and Sections...... A-12 A.6.3 Removing Installed Images................ A-14 A.7 Installing SQL Images for Privileged Applications................................. A-17 A.7.1 Editing the Startup and Shutdown Procedures for Privileged Applications... A-18 A.8 Using Different Versions of the Common Components................................... A-19 A.9 Deleting Versions of the Common Components... A-21 iv B Sample DBI Installation C List of Files on DBI Kit D How to Order Additional Documentation Tables 1-1 Required and Optional Software........... 1-2 1-2 Process Account Quotas for the Installing Account.................................. 1-10 1-3 Minimum Required System Parameter Values for OpenVMS VAX.......................... 1-11 1-4 Minimum Required System Parameter Values for OpenVMS AXP.......................... 1-12 1-5 Disk Space Requirements.................. 1-12 3-1 User Account Quotas for Using DBI........ 3-2 A-1 Global Pages and Sections Required for Common Components OpenVMS VAX Images .... A-13 A-2 Global Pagelets and Sections Required for Common Components OpenVMS AXP Images .... A-14 C-1 DBI Installed Files for OpenVMS VAX...... C-1 C-2 ORACLE Files Installed for OpenVMS VAX... C-3 C-3 DBI Installed Files for OpenVMS AXP...... C-3 C-4 ORACLE Files Installed for OpenVMS AXP... C-5 v ________________________________________________________________ Send Us Your Comments We welcome your comments on this manual or any DEC DB Integrator product manual. If you have suggestions for improvement or find any errors, please indicate the chapter, section, and page number (if available). Your input is valuable in improving future releases of our documentation. You can send comments to us in the following ways: o Electronic mail - DATABASE_DOC@WEORG.ENET.DEC.COM o FAX - 603-881-0120 Attn: DBI Documentation o Postal service Digital Equipment Corporation DEC DB Integrator Products Documentation 110 Spit Brook Road, ZKO2-1/R34 Nashua, NH 03062-2698 USA You can use the following questionnaire to give us information. vii Name _____________________________Title_______________________ Company __________________________Department ________________ Mailing Address __________________Telephone_Number __________ ________________________________________________________________________ Book Title _______________________Version_Number ____________ viii 1. How does the DBI documentation compare to documentation from other vendors that you have used? What do you like about other vendors' documentation that you would like the DBI documentation to implement? 2. What other topics or examples would you like to see included in this documentation set? 3. Do you use the online help for the DBI products? Are there other topics you would like to see included in the online help? 4. Interviews, telephone surveys, user observation, questionnaires, and other similar activities help us to improve our documentation. May we contact you about participating in future efforts? 5. If you have suggestions for improving particular sections or find any errors, please indicate the title of the manual and include the section number. 6. Please include any other comments or suggestions you have. ix ________________________________________________________________ Preface DEC DB Integrator (DBI) allows you to access heterogeneous databases through a single database view. This guide describes how to install DBI on VAX and AXP processors that are running the OpenVMS operating system. Keep this guide with your distribution kit. You will need it to install maintenance updates or to reinstall DBI for any other reason. Who Should Use This Guide This guide is intended for individuals familiar with network and system management, who install the DBI software, and who may provide information and guidance to others about using the software. Structure of This Guide This guide contains the following chapters and appendixes: Chapter 1 Describes what you must do before installing the software. Chapter 2 Describes how to install the DBI software. Chapter 3 Describes what you must do after installing DBI. Appendix A Describes how to install the Common Components. Appendix B Contains a log of a sample installation. Appendix C Lists the files installed on your system by DBI. xi Appendix D Describes how to order additional documenta- tion from Digital Equipment Corporation. Conventions In examples, an implied carriage return occurs at the end of each line, unless otherwise noted. You must press the Return key at the end of each input line. Often in examples, the prompts are not shown. Generally, they are shown where it is important to depict an interactive sequence exactly; otherwise, they are omitted in order to focus full attention on the statements or commands themselves. This section explains the conventions used in this guide: . . . Horizontal ellipsis points in statements or commands mean that parts of the statement or command not directly related to the example have been omitted. . Vertical ellipsis points in an example mean . that information not directly related to the . example has been omitted. italic Italic text indicates emphasis and complete text manual titles. boldface Boldface text indicates the first instance of text terms defined in the text. In online versions, bold is used to show user input. UPPERCASE Uppercase text indicates the name of an SQL TEXT statement or an SQL logical name. lowercase Lowercase text indicates an operating system text command or the name of a file. input entered by the user. DBADM References to DBADM, unless specifically qualified, refer to that database privilege having been granted or received either with or without the WITH GRANT OPTION clause. xii monospaced Monospaced text indicates example programs and text examples of user interfaces. $ Dollar signs represent the default DIGITAL Command Language (DCL) prompt. This symbol indicates that the system is ready for input. The OpenVMS icon denotes the beginning of information specific to the OpenVMS VAX and OpenVMS AXP operating systems. The DEC OSF/1 icon denotes the beginning of information specific to the DEC OSF/1 AXP operating system. The VAX icon denotes the beginning of information specific to the OpenVMS VAX operating system. The AXP icon denotes the beginning of information specific to the OpenVMS AXP operating system. The diamond symbol (<>) denotes the end of information specific to an operating system. For More Information This section describes where to find information about the DEC DB Integrator product family, RdbAccess products, and SQL. For each of the products listed in the section, the following information is available: o Before You Install Lists hardware and software required to install the product. o Software Product Description (SPD) Provides information on the compatibility of other software products. Use the SPD to verify which versions of your operating system are compatible with which versions of the DEC DB Integrator (DBI) product family software. o Release Notes Provide information about a specific release of the product. Available in online format only. xiii DEC DB Integrator Product Family Information Information about the DEC DB Integrator product family is available in the following manuals: o DEC DB Integrator Product Family User's Guide Describes how to use the DBI Gateway software and DEC DB Integrator software to access and integrate data stored in relational and nonrelational databases. o DEC DB Integrator Handbook Describes how to use DEC DB Integrator to set up and maintain a multidatabase management system. The system provides the capability to access and update data stored in multiple databases, in distributed locations, and with multiple data formats. o DEC DB Integrator for OpenVMS Installation Guide Provides detailed software installation instructions for hardware systems that support DEC DB Integrator on OpenVMS VAX and OpenVMS AXP operating systems. Also provides detailed information about the hardware, operating system versions, and software packages that are compatible with this version of DBI. o DEC DB Integrator Gateway installation and configura- tion guides for the following gateway products: - DEC DB Integrator Gateway for DB2 - DEC DB Integrator Gateway for DSM - DEC DB Integrator Gateway for EDA/SQL - DEC DB Integrator Gateway for ORACLE - DEC DB Integrator Gateway for SequeLink - DEC DB Integrator Gateway for SYBASE o DEC DB Integrator Gateway for DBMS Accessing DEC DBMS Data with SQL Describes how to use the DEC DBMS data driver with the Non-SQL Data Server to access DEC DBMS data. o DEC DB Integrator Gateway for RMS Accessing RMS and VSAM Files with SQL xiv Describes how to use the RMS data driver with the Non- SQL Data Server to access nonrelational files. o Accessing Nonrelational Data with SQL Describes how to use SQL with the Non-SQL Data Server to access nonrelational files. o DEC DB Integrator Gateway for Custom Drivers Driver Development Guide Describes how to write data and metadata drivers to handle data and metadata sources that are not explicitly supported by DEC DB Integrator Gateway for RMS. o DEC DB Integrator Gateway for Custom Drivers/DEC DB Integrator Gateway for RMS Installation Guide Describes how to install and maintain DEC DB Integrator Gateway for Custom Drivers and DEC DB Integrator Gateway for RMS software on the OpenVMS operating system. RdbAccess Information Information about RdbAccess products is available from the following guides: ________________________Note ________________________ The following guides have been superseded by the corresponding DEC DB Integrator Gateway guides. The information is provided for the benefit of users who have not upgraded their RdbAccess software products. _____________________________________________________ o DEC RdbAccess Client for DB2 User's Guide o DEC RdbAccess Server for DB2 Installation and Administration Guide o DEC RdbAccess Client for DB2 Installation Guide o DEC RdbAccess for ORACLE User's Guide o DEC RdbAccess for ORACLE Installation Guide xv SQL Information Information about SQL is available in the following manuals: o DEC Rdb SQL Reference Manual Provides reference material and a complete description of the statements, the interactive, dynamic, and module language interfaces, and the syntax for SQL. o DEC Rdb Introduction to SQL Introduces the interactive and programming components of ANSI/ISO SQL and presents a tutorial of the SQL language elements for designing, creating, modifying, and retrieving data through interactive SQL. o DEC Rdb Guide to SQL Programming Describes how to write database application programs that use ANSI/ISO SQL. o DEC Rdb Guide to Distributed Transactions Describes the two-phase commit protocol and distributed transactions, and explains how to use DEC Rdb with distributed transactions. References to Products The DBI documentation set often refers to the following Digital products by their abbreviated names: o The CDD/Repository for OpenVMS AXP and CDD/Repository for OpenVMS VAX products are referred to as CDD/Repository, the data dictionary, dictionary, or, more commonly, repository. o The DEC Data Distributor for OpenVMS AXP and DEC Data Distributor for OpenVMS VAX products are referred to as Data Distributor. o The DEC DATATRIEVE for OpenVMS AXP and DEC DATATRIEVE for OpenVMS VAX products are referred to as DATATRIEVE. o The DEC DB Integrator product is referred to as DBI. It is available on the OpenVMS AXP, OpenVMS VAX, and DEC OSF/1 AXP systems. xvi o The DEC DB Integrator Gateway for DB2, DEC DB Integrator Gateway for EDA/SQL, DEC DB Integrator Gateway for ORACLE, DEC DB Integrator Gateway for SequeLink, and DEC DB Integrator Gateway for SYBASE, products are referred to as the relational gateways. o The DEC DB Integrator Gateway for Custom Drivers, DEC DB Integrator Gateway for DBMS, DEC DB Integrator Gateway for DSM, and DEC DB Integrator Gateway for RMS products are referred to as the nonrelational gateways. o The DEC DB Integrator Gateway family of data access products is often referred to as DBI Gateway. The DEC DB Integrator Gateway family is made up of the following products. Each product is often referred to as the gateway for [identifying product name]. For example, the DEC DB Integrator Gateway for Custom Drivers is often referred to as the gateway for Custom Drivers. - DEC DB Integrator Gateway for Custom Drivers[1] - DEC DB Integrator Gateway for DB2 Client[1], [2] - DEC DB Integrator Gateway for DB2 Server[3] - DEC DB Integrator Gateway for DBMS[1] - DEC DB Integrator Gateway for DSM[1] - DEC DB Integrator Gateway for EDA/SQL[1], [2] - DEC DB Integrator Gateway for ORACLE[1], [2] - DEC DB Integrator Gateway for RMS[1] - DEC DB Integrator Gateway for SequeLink[1], [2] - DEC DB Integrator Gateway for SYBASE[1], [2] o The DEC RdbExpert for OpenVMS AXP and DEC RdbExpert for OpenVMS VAX products are referred to as RdbExpert. ___________________ [1]This product is available on the OpenVMS AXP and OpenVMS VAX systems. [2]This product is available on the DEC OSF/1 AXP system. [3]This product is only available on the IBM system. xvii o The Digital gateways to SNA networks are referred to as the DEC SNA gateway products. These products include: - OpenVMS SNA - DECnet SNA Gateway for Channel Transport - DECnet SNA Gateway for Synchronous Transport - DEC SNA Domain Gateway - DEC SNA Peer Server o The DECnet/SNA Data Transfer Facility product is referred to as DTF. o The DECtrace for OpenVMS AXP and DECtrace for OpenVMS VAX products are referred to as DECtrace. o The DEC Rdb for OpenVMS AXP and DEC Rdb for OpenVMS VAX products are both referred to as DEC Rdb. Prior to DEC Rdb Version 5.0, this product was called VAX Rdb/VMS. o The OpenVMS RMS (Record Management Services) product is referred to as RMS. o SQL refers to the SQL interface to DEC Rdb and to the DBI family of products. SQL is Digital Equipment Corporation's implementation of the SQL standard ANSI X3.135-1992, ISO 9075:1992, commonly referred to as ANSI/ISO SQL. xviii 1 ________________________________________________________________ Preparing for DBI Installation Your distribution kit includes a letter titled Before You Install DEC DB Integrator. This letter discusses important information that might not be included in this guide. You should read this letter now. 1.1 Registering Your Software License Before you install and run DEC DB Integrator (DBI) Version 3.1 on a newly licensed node or cluster, you must first register a Product Authorization Key (PAK) license using the License Management Facility (LMF). If you are installing DBI as an update on a node or cluster already licensed for this software, you have already completed the License PAK registration requirements. The PAK may be shipped along with the kit if you ordered the license and media together; otherwise, it is shipped separately. If you are installing prerequisite or optional software along with DBI, review the PAK status and install the PAKs for any prerequisite or optional software before you install DBI. In order to run the Installation Verification Procedure (IVP) and use the software, you must register and load your DBI license before you start its installation. To register a license under OpenVMS, first log in to the system manager's account, SYSTEM. You then have a choice of two ways to perform the registration: o Invoke the SYS$UPDATE:VMSLICENSE.COM procedure. When it prompts you for information, respond with data from your PAK. o At the DCL prompt, enter the LICENSE REGISTER command with the appropriate qualifiers that correspond to the information contained in your PAK. Preparing for DBI Installation 1-1 If you plan to use DBI on more than one node in a VMScluster, you must load a license on each of the other nodes after you complete this installation. See Section 3.5 for more information. 1.2 Required Hardware DBI works with all VAX and AXP hardware. Installing DBI requires the following minimum disk space: o 13,300 available blocks on a VAX processor. <> o 23,700 available blocks on an AXP processor. <> If you are installing from tape, a TK50, TK70, or DAT tape drive is required. 1.3 Required and Optional Software This section provides information on the software you must have installed on your system before running DBI. These requirements are summarized in Table 1-1, which also lists some of the many software tools that work with DBI. Table_1-1_Required_and_Optional_Software__________________ Required_Software__________________Purpose________________ Common Components Provides SQL and Rdb/Dispatch software, as described in Section 1.3.1 DECdtm services Provides two-phase commit transactional integrity, as described in Section 1.3.2 (continued on next page) 1-2 Preparing for DBI Installation Table_1-1_(Cont.)_Required_and_Optional_Software__________ Required_Software__________________Purpose________________ Any one or more of: Act as a DBI database VAX Rdb/VMS Version 4.1 manager as described in VAX Rdb/VMS Version 4.2 Section 1.3.3 DEC Rdb Version 5.1 DEC Rdb Version 6.0 ORACLE V7 RDMS SYBASE Open Client Version 4.6.2[1] SYBASE Open Server Version 4.9.1[1] OpenVMS VAX Version 5.5-2 or Operating system higher, or OpenVMS AXP Version 6.1 __________________________________________________________ Optional_Software__________________Purpose________________ DEC DB Integrator Gateway for DB2 Provide access to DB2 Client for OpenVMS Version 3.1 databases DEC DB Integrator Gateway for DB2 Server Version 3.1 DEC DB Integrator Gateway for Provide access to EDA/SQL for OpenVMS Version 3.1 EDA/SQL data sources EDA/Link and EDA/SQL Server for OpenVMS DEC DB Integrator Gateway for Provide access to ORACLE for OpenVMS Version 3.1 ORACLE RDBMS databases ORACLE SQL*net DEC DB Integrator Gateway for RMS Provides relational Version 3.1 access to RMS files [1]To_use_the_SYBASE_catalog_image,_SYBASE_Open_Client____ Version 4.6.2 must be installed on the same node as DEC DB Integrator. SYBASE Server Version 4.9.1 must be installed on a node accessible by the SYBASE Open Client software. (continued on next page) Preparing for DBI Installation 1-3 Table_1-1_(Cont.)_Required_and_Optional_Software__________ Optional_Software__________________Purpose________________ DEC DB Integrator Gateway for Provide access to SequeLink for OpenVMS Version 3.1 SequeLink data sources SequeLink server DEC DB Integrator Gateway for Provide access to SYBASE for OpenVMS Version 3.1 SYBASE databases SYBASE Open Client and Server Version 4.9.2[1] [1]To_use_the_SYBASE_catalog_image,_SYBASE_Open_Client____ Version 4.6.2 must be installed on the same node as DEC DB Integrator. SYBASE Server Version 4.9.1 must be installed on a node accessible by the SYBASE Open Client software. __________________________________________________________ 1.3.1 Common Components Installation Requirement The Common Components are software components that provide relational database functions for several Digital products. The Common Components consist of: o SQL interface o SQL/Services server o Rdb/Dispatch interface and Rdb/Remote server The Common Components are required in order to use the following products: o DEC DB Integrator (DBI) o DEC DB Integrator Gateway products o DEC Rdb DBI requires Common Components in the following ways: o Any process that runs the DBI software or that accesses a DBI logical database, locally or remotely, requires Rdb/Dispatch. For example, if a DBI application is running on a local node and attaches to a DBI logical database on a remote node, both nodes must have Rdb/Dispatch installed. o Creating a DBI logical database requires SQL. 1-4 Preparing for DBI Installation A Common Components kit is provided with each product. The Common Components kit is part of the DEC Rdb media kit and the Common Components have the same version number as DEC Rdb. However, you can install the Common Components separately from the other components of DEC Rdb and they do not require a DEC Rdb license. 1.3.1.1 Why You Must Install Common Components Each product that requires Common Components requires a specific version of Common Components. In the case of DEC Rdb, the product installation automatically includes the Common Components installation. For DBI or a DBI gateway installation, however, you must separately install the Common Components. If the required version of Common Components is not installed on your system, you can install DBI or a DBI gateway, but you cannot successfully use the product. The DBI or gateway installation procedure prints a warning and completes, but the Installation Verification Procedure (IVP) fails. Because each product requires a specific version of Common Components, you may need to have more than one version of Common Components installed on a system at any given time. For example, suppose you want to install DBI on a system running VAX Rdb/VMS Version 4.2 with a critical set of databases and applications. The Version 4.2 Common Components cannot be disturbed. However, to use DBI Version 3.1, you must install Common Components Version 6.0. The solution is to install the multiversion variant of Common Components Version 6.0, as described in Section A.1.2. This variant allows multiple versions of Common Components, or DEC Rdb itself, to coexist on the same system without affecting each other, and does not significantly add to the tasks of system or database administration. Preparing for DBI Installation 1-5 1.3.1.2 Checking for Common Components It is not necessary to install a single version of Common Components more than once per system. Use the following procedure to determine whether or not the correct version of Common Components has already been installed on a system. If Version 6.0 has not been installed, you must perform the procedure described in Appendix A in order to use Version 3.1 of DBI or any DBI gateway product. To find out if the Common Components have been installed on your OpenVMS system, enter: $ DIR SYS$LIBRARY:SQL$SETVER.COM If the file SYS$LIBRARY:SQL$SETVER.COM does not exist, you must install Common Components. If the file does exist, enter: $ @SYS$LIBRARY:SQL$SETVER 6.0 If you see any of the following messages, you must install Common Components: %SQL-E-SETVER SQL Version 6.0 does not exist on your system. %SQL-E-SETVER SYS$COMMON:[SYSLIB]SQL$SHR.EXE Image Ident Problem %SQL-E-SETVER IMAGE IDENT = n.n, VERSION = 6.0 The last two messages indicate that standard (nonmul- tiversion) DEC Rdb software has been installed on the system. If you see the following messages, with or without the word MULTIVERSION, Common Components have already been installed. You do not need to install the Common Components software again. Current PROCESS SQL environment is version V6.0-nn (MULTIVERSION) Current PROCESS Rdb/Dispatch environment is version V6.0-nn (MULTIVERSION) 1-6 Preparing for DBI Installation 1.3.2 DECdtm Services DECdtm services must be started on all nodes where DBI is running as well as all nodes on which link databases reside. To ensure that DECdtm is running: 1. Check for processes named TP_SERVER and IPCACP on the node. If these processes are not running, then DECdtm has not been started. Use the SYS$STARTUP:DECDTM$STARTUP.COM procedure to start DECdtm services. 2. If DECdtm is running, check that a valid log file is available on the node. You can use the log manager control program (LMCP) to check this: $ MCR LMCP LMCP> SHOW LOG SYSTEM$ If you are using a cluster alias in specifying the location of the remote database, perform this check for all nodes that participate in the cluster alias. There needs to be one log file per node, not one per cluster. If the file is not found, you can create it using the LMCP CREATE command: LMCP> CREATE LOGFILE SYSTEM$/OWNER=SYSTEM/SIZE=2000 The minimum log file size is 100 blocks. If you omit this qualifier, the transaction log is created with the default size of 4000 blocks. For more information about managing DECdtm services, refer to the OpenVMS System Manager's Manual. 3. If you have problems starting DECdtm services: a. Make sure the system logical name SYS$DECDTM_INHIBIT is not defined. If it is, remove the definition from the SYS$STARTUP:SYLOGICALS.COM procedure and deassign the logical name. b. Check using SYSGEN to make sure the SCSNODE and SCSSYSTEMID system parameters are defined and are correct. Preparing for DBI Installation 1-7 c. Check to make sure that logical name SYS$JOURNAL is either: - Defined as a valid device and directory, or - Not defined at all. If this logical name is not previously defined, it is defined by the DECdtm startup procedure. 1.3.3 Database Product Requirements Running DBI requires that one or more of the following products be licensed, installed, running, and available on either the node or the network: o DEC Rdb o ORACLE V7 o SYBASE Version 4.9.2 If you are using ORACLE V7 on the network, then SQL*net software must also be available. DBI installation options allow you to install the metadata storage files required for DEC Rdb, ORACLE V7, or SYBASE Version 4.9.2. If you choose to install DBI with metadata storage capabilities using ORACLE V7, you must also build the necessary support image. The additional space you need to use these images is as follows: o 6100 disk blocks on an OpenVMS VAX system o 9620 disk blocks on an OpenVMS AXP system This increases the total blocks required to the following: o 19,400 disk blocks on an OpenVMS VAX system o 33,320 disk blocks on an OpenVMS AXP system Using ORACLE V7 requires a post-installation step to build the image, as documented in Section 3.1. The Installation Verification Procedure (IVP) runs only if VAX Rdb/VMS Version 4.1, VAX Rdb/VMS Version 4.2, DEC Rdb Version 5.1, or DEC Rdb Version 6.0 is installed on the system. The IVP requires 6000 blocks of disk space. If you cannot run the IVP or choose not to run the IVP, you may ignore the rest of this section. 1-8 Preparing for DBI Installation If you are using DEC Rdb, then you must run the command procedure, SYS$LIBRARY:RDBVMS_SETVER (for VAX Rdb/VMS Version 4.1, VAX Rdb/VMS Version 4.2, or DEC Rdb Version 5.1). If you are running DEC Rdb Version 6.0, then you must execute the SYS$LIBRARY:DECRDB$SETVER command procedure. For example, to run the VAX Rdb/VMS Version 4.2 multiversion software, enter the following: $ @SYS$LIBRARY:RDBVMS_SETVER 4.2 In addition, you must be using the monitor that is associated with the version of DEC Rdb you are running. For example, if the DEC Rdb version is set to 4.2, a process named RDMS_MONITOR42 must be started. To check that the appropriate monitor is started, enter: $ SHOW SYSTEM Scan the output for a process named RDMS_MONITOR. If you have not enabled the DEC Rdb multiversion installation, a process called RDMS_MONITOR should exist. If you have enabled the DEC Rdb multiversion installation, the translation of RDMS$VERSION_VARIANT is appended to the process name. If the RDMS_MONITOR process does not exist and you have not enabled the DEC Rdb multiversion installation, enter: $ @SYS$STARTUP:RMONSTART If the RDMS_MONITOR process does not exist and you have enabled the DEC Rdb multiversion installation, enter: $ @SYS$STARTUP:RMONSTARTversion-variant In this example, VERSION-VARIANT represents the number of the version that you want installed. Choose from the following: Rdb/VMS Version 4.1 Rdb/VMS Version 4.2 DEC Rdb Version 5.1 DEC Rdb Version 6.0 You must choose one of these versions for the IVP to run. Preparing for DBI Installation 1-9 1.4 Installation Procedure Requirements This section describes the privileges, process quotas, and other system requirements for installing DBI. 1.4.1 Privileges To install DBI, you must be logged in to an account that has the SETPRV privilege. The privileges required to use DBI are defined in Section 3.2.1. 1.4.2 Process Account Quotas The account used to install DBI must have sufficient quotas to enable you to perform the installation. Table 1-2 summarizes the requirements. Quotas required to use DBI are defined in Section 3.2.2. Standard procedures for checking and setting various parameters are described in Section 1.5. Table 1-2 Process Account Quotas for the Installing __________Account_________________________________________ Account_Quota____Value____________________________________ ASTLM 24 BIOLM 22 BYTLM 32,768 DIOLM 22 ENQLM 1000 FILLM 100 PRCLM 1 JTQUOTA 1024 PGFLQUO[1] 40,000 WSDEF 256[2] [1]On_an_OpenVMS_AXP_system,_the_PGFLQUO_parameter_should_ be doubled at least. [2]The values for WSEXT and WSQUO must be equal to or greater than the WSDEF value. __________________________________________________________ 1-10 Preparing for DBI Installation 1.4.3 Required System Parameters Table 1-3 and Table 1-4 list the minimum required system parameter values for the OpenVMS VAX and OpenVMS AXP installations. Depending on the kinds of programs and applications running at your site, you might need higher values for some settings. Table 1-3 Minimum Required System Parameter Values for __________OpenVMS_VAX_____________________________________ GBLPAGES GBLSECTIONS Images________(GBLPAGES)[1]_(GBLSECTIONS)[VIRTUALPAGECNT__ DBI base 3710 8 40,000 images Rdb image 10 1 (DBI$CI_ RDBSHR.EXE)[2] ORACLE image 10 2 (DBI$CI_ ORASHR.EXE)[2] SYBASE image 10 2 (DBI$CI_ SYBSHR.EXE)[2] <> [1]These_values_represent_the_number_of_available_global__ pages and global sections required for the DBI and associated database image installation, not the total number you need to run your system and other software. [2]You must install at least one database image; you can install any or all of them. __________________________________________________________ Preparing for DBI Installation 1-11 Table 1-4 Minimum Required System Parameter Values for __________OpenVMS_AXP_____________________________________ GBLPAGES GBLSECTIONS Images________(GBLPAGES)[1]_(GBLSECTIONS)[VIRTUALPAGECNT__ DBI base 4740 6 80,000 images Rdb image 2380 1 (DBI$CI_ RDBSHR.EXE)[2] ORACLE image 2900 1 (DBI$CI_ ORASHR.EXE)[2] SYBASE image 450 1 (DBI$CI_ SYBSHR.EXE)[2] <> [1]These_values_represent_the_number_of_available_global__ pagelets and global sections required for the DBI and associated database image installation, not the total number you need to run your system and other software. [2]You must install at least one database image; you can install any or all of them. __________________________________________________________ 1.4.4 Required Disk Space Table 1-5 summarizes the storage requirements during and after installation. When the IVP is run during installation, the disk space requirements are greater than after installation. Table_1-5_Disk_Space_Requirements_________________________ Blocks Hardware During Blocks After Kit___________________System______InstallationInstallation (continued on next page) 1-12 Preparing for DBI Installation Table_1-5_(Cont.)_Disk_Space_Requirements_________________ Blocks Hardware During Blocks After Kit___________________System______InstallationInstallation DBI Version 3.1 VAX 19,300 13,300 DBI_Version_3.1_______AXP_________29,700______23,700______ To determine the number of available disk blocks on the current system disk, enter the following command at the DCL prompt: $ SHOW DEVICE SYS$SYSDEVICE 1.4.5 System Disk Backup At the beginning of the installation, the VMSINSTAL procedure asks if you have backed up your system disk. Digital recommends that a system disk backup be completed 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 OpenVMS System Management documentation. 1.4.6 OpenVMS Help Library Use Errors can occur during installation if the OpenVMS Help Library is in use. Instruct system users to avoid using the help library while software installation is in progress. 1.5 Performing Standard System Maintenance Procedures Before you install DBI, you need to perform these standard maintenance procedures, described in the following sections: o Check and set process account quotas o Check system parameter values o Calculate values for global pages and global sections Preparing for DBI Installation 1-13 o Change system parameter values with the OpenVMS AUTOGEN utility 1.5.1 Checking and Setting Process Account Quotas User account quotas are stored in the file SYSUAF.DAT. Use the OpenVMS 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 To change a quota, enter the MODIFY command. The following example changes the FILLM quota for the SMITH account and then exits from the utility: UAF> MODIFY SMITH /FILLM=50 UAF> EXIT After you exit from the utility, the system displays messages indicating whether or not changes were made. Once the changes have been made, the user whose account was modified 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 OpenVMS System Management documentation. 1.5.2 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> 1-14 Preparing for DBI Installation At the SYSGEN> prompt, enter the SHOW command to display the value of a system parameter. For example, the following command displays the value for the WSMAX system parameter: SYSGEN> SHOW WSMAX After checking the parameters with the SHOW command, enter the EXIT command at the SYSGEN> prompt to return to DCL level. To change system parameters, refer to Section 1.5.4. 1.5.3 Calculating the Values for Global Pages, Global Pagelets, and Global Sections To install and run DBI, you must have sufficient global pages and global sections. First, find out how many available global pages and sections you have on your system. Then, use the AUTOGEN utility if you need to increase the global pages and sections system parameters. You can use the WRITE command with the F$GETSYI lexical function to find the number of available global pages and global sections. The following example shows how to display this information at your terminal (the default for SYS$OUTPUT): $ WRITE SYS$OUTPUT F$GETSYI("CONTIG_GBLPAGES") 15848 $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS") 24 If the values displayed by the system are greater than the values in Table 1-3 or Table 1-4, you do not need to increase the values for these parameters. If the value of available global pages or global sections is less than the value in Table 1-3, you must increase the system parameter settings. Section 1.5.4 describes the procedures for increasing these values using the AUTOGEN utility. Preparing for DBI Installation 1-15 1.5.4 Changing System Parameter Values with AUTOGEN Use the AUTOGEN utility to change system parameters. The AUTOGEN utility 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 To change a parameter value listed in this file, delete the current value associated with that parameter and enter the new value. To add a new parameter, add a line to the file that includes both the name of the parameter and its value, for example: WSMAX = 8096 To modify incremental parameters such as available global pages and global sections, use the ADD_ prefix. The following example increases the global page setting by 2000: ADD_GBLPAGES = 2000 After all changes have been made, exit from the editor and execute the AUTOGEN utility to recalculate your system parameters. The following command recalculates your system parameters and reboots (restarts) the system: $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT When you specify REBOOT, the AUTOGEN utility performs an automatic system shutdown and then reboots the system. Any users logged on to the system have their processes 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 the AUTOGEN utility, see the OpenVMS System Management documentation. 1-16 Preparing for DBI Installation 2 ________________________________________________________________ Installing DBI Installing DBI takes approximately 30 minutes on a standalone VAX 6400. This time can vary based on system load, backup media, and hardware. Please read Section 3.5 in Chapter 3 for important post- installation information if you are installing DBI in a VMScluster environment. 2.1 Installation Procedure If it is not already inserted, place the DBI media into the appropriate drive. You can terminate installation at any time during the procedure by pressing Ctrl/Y. When you press Ctrl/Y, the installation procedure deletes all the files it has created up to that point and exits. You can then start the installation again. When the system prompts you with a question during the installation procedure, the default answer is often listed in brackets ([]). To accept the default answer, press the Return key. To install DBI: 1. Log in to a privileged account and set your default device and directory to SYS$UPDATE. Username: SYSTEM Password: $ SET DEFAULT SYS$UPDATE 2. Invoke VMSINSTAL. @VMSINSTAL saveset-name device-name option-list Installing DBI 2-1 The VMSINSTAL procedure is in the SYS$UPDATE directory. The elements that you specify when you invoke the VMSINSTAL command procedure are as follows. saveset-name The installation name for the component. For DBI, enter the following installation name: DBI031 device-name The name of the device on which you plan to mount the media and the directory containing the DBI save set. For example, MUA0: is the device name used in examples in this guide. To specify the device name on the @VMSINSTAL command line, enter: @VMSINSTAL DBI031 MUA0: option-list The word OPTIONS followed by one or more of the following option designators: 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 re-installation (typically after upgrading your system). o Get saveset option (G) Lets you store product save sets temporarily on a magnetic tape or in a disk directory. o File log option (L) Logs all activity to the terminal during installa- tion. o Display or print the release notes (N) Indicates that you want to see the installation question on release notes. If you do not include the N option, VMSINSTAL does not ask you about the release notes. Review the release notes 2-2 Installing DBI 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 the N option. Even if you omit the N option when you invoke VMSINSTAL, the DBI release notes are copied automatically to the SYS$HELP directory. ________________________Note ________________________ The alternative root option (R) that lets you install a product to a system root other than that of the operating system is not supported for use with DBI. _____________________________________________________ For detailed information on these software installation options, see the OpenVMS operating system documenta- tion. If you specify more than one option, separate the options with commas, for example: OPTIONS A,N The following example invokes VMSINSTAL to install DBI and shows the system response: $ @VMSINSTAL DBI031 MUA0: OpenVMS AXP Software Product Installation Procedure V6.1 It is 10-NOV-1994 at 16:23. Enter a question mark (?) at any time for help. When you invoke VMSINSTAL, it checks the following: o Whether or not you are logged in to a privileged account. Digital recommends that you install software from the system manager's account with your default device and directory set to SYS$UPDATE. o Whether or not you have adequate quotas for installation. The VMSINSTAL procedure checks for the quota values shown in Table 1-2. Installing DBI 2-3 The VMSINSTAL procedure then checks to determine whether or not any users are logged into the system. If users are logged in, VMSINSTAL asks if you want to continue the installation: * Do you want to continue anyway [NO]? If you want to continue, enter YES. If you want to stop the installation, press the Return key. 3. Confirm the system backup. * Are you satisfied with the backup of your system disk [YES]? If you are satisfied with the backup of your system disk, press the Return key. Otherwise, enter NO to discontinue the installation. After you back up your system disk, you can restart the installation. If you omitted the device name on the VMSINSTAL command line, VMSINSTAL prompts you for the device name: * Where will the distribution volumes be mounted: In response to this prompt, enter the name of the device that will contain the DBI kit (save set). For example, if the kit is on a TK50 that will be located on unit MUA0:, enter MUA0: in reply to this question. Depending on the type of device and whether or not the device is already mounted, VMSINSTAL may prompt you to mount the device: Please mount the first volume of the set on MUA0:. * Are you ready? YES %MOUNT-I-MOUNTED, MUA0: mounted If you have not already done so, mount the distribution media on the specified device. The VMSINSTAL procedure asks if you are ready to continue with the installation. If you respond YES, the VMSINSTAL procedure displays a message that the media containing DBI 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. 2-4 Installing DBI 4. Verify the product being installed. The VMSINSTAL procedure displays the product being installed: The following products will be processed: DBI V3.1 Beginning installation of DBI 3.1 at 16:12 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. 5. Print the installation guide. The VMSINSTAL procedure moves the installation guide to the SYS$HELP directory, and asks you if you would like to print it: The DBI Installation Guide has been provided in SYS$HELP. * Would you like to print the DBI Installation Guide? [NO]: If you enter YES, the files will be queued to the SYS$PRINT print queue. Installing DBI 2-5 6. Load required files for metadata storage. DBI metadata can be stored in a DEC Rdb, ORACLE V7, or SYBASE database. You can install the files required for any or all of the databases: * Do you want the capability to store metadata in a DEC Rdb database [YES]? YES * Do you want the capability to store metadata in an ORACLE database [YES]? YES * Do you want the capability to store metadata in a SYBASE database [YES]? YES 7. Run the Installation Verification Procedure. The VMSINSTAL procedure now asks if you want to run the Installation Verification Procedure (IVP). The IVP checks to be sure that the installation is successful; it requires 6000 extra disk blocks during the installation. The default answer is YES. Digital recommends that you run the IVP. * Do you want to run the IVP after the installation [YES]? 8. Purge files. The directories SYS$HELP, SYS$LIBRARY, SYS$MESSAGE, SYS$SYSTEM, and SYS$TEST may contain previous versions of DBI files. These files are replaced during the installation with new files, but the old files are not automatically purged. Purging is recommended. In response to the purging prompt, press the Return key or enter YES to purge the files, or enter NO to keep them. * Do you want to purge files replaced by this installation [YES]? Depending on whether or not you specified parameters on the VMSINSTAL command line, the * Products: prompt or the DCL prompt ($) may appear. If the * Products: prompt appears, you can return to the DCL prompt ($) by pressing Ctrl/Z. The VMSINSTAL procedure deletes or changes entries in the process symbol tables during the installation. Therefore, if you plan to continue using the installation account (such as SYSTEM) and you want to restore these symbols, you should log out and log in again. 2-6 Installing DBI 2.2 Error Recovery Errors can occur during the installation if any of the following conditions exists: o The operating system version is incorrect. o Quotas necessary for successful installation are insufficient. o System parameter values for successful installation are insufficient. o The OpenVMS Help Library is currently in use. For descriptions of the error messages generated by these conditions, see the OpenVMS documentation on system messages, recovery procedures, and OpenVMS software installation. If you are notified that any of these conditions exists, you should take the appropriate action as described in the message. For information on installation requirements, see Chapter 1. Installing DBI 2-7 3 ________________________________________________________________ After Installation You can perform the following tasks after installing DBI: o Create the required image for storage of DBI metadata in an ORACLE V7 database o Complete required changes to user accounts o Run the Installation Verification Procedure (IVP) separately o Edit the system startup files o Make the product available on a VMScluster system 3.1 Creating the Image for Use with ORACLE If you chose during the installation to store metadata files in an ORACLE database, you must perform one additional step after installation. You must build the image for use with the ORACLE database on a node on which the ORACLE software is licensed to run. This is a two-step process: 1. Execute the ORAUSER command file provided by the ORACLE software, for example: $ @ORA$DISK:[ORACLEV7.DB_ORAV7P.DB_SYSTEM]ORAUSER.COM 2. Execute the command file supplied by Digital to create the required image: $ @SYS$LIBRARY:DBI_ORABLD.COM After Installation 3-1 3.2 Setting Up User Account Requirements To enable users to work with DBI on your system, you must give user accounts certain privileges and quotas, and users must set up their accounts to run DBI. The subsections that follow describe your tasks as the installer and those of DBI users to set up their accounts. 3.2.1 Granting Privileges Give each DBI user's account at least the TMPMBX and NETMBX privileges. Use the OpenVMS Authorize utility (AUTHORIZE) to determine if users have the privileges they require. 3.2.2 Setting User Account Quotas Make sure that the user accounts have sufficient quotas to be able to use DBI. Table 3-1 summarizes the required user account quotas. Table_3-1_User_Account_Quotas_for_Using_DBI_______________ Account_Quota____Value____________________________________ ASTLM 24 BIOLM 22 BYTLM 20,480 DIOLM 22 ENQLM 1000 FILLM 50 PRCLM 1 JTQUOTA 1024 WSDEF 256[1] PGFLQUO 40,000 TQELM 10 [1]The_values_for_WSEXT_and_WSQUO_must_be_equal_to_or_____ greater than the WSDEF value. __________________________________________________________ Section 1.5.1 describes how to verify and change account quotas. Some quotas may need to be higher based on other applications or layered product requirements. 3-2 After Installation 3.2.3 Setting Up User Accounts All users who want to use DBI must put the following command in their LOGIN.COM file or ensure that the command is invoked before DBI is run: $ @SYS$LIBRARY:DBI_USER_SETUP To create a DBI logical database or use DBI data definition language, users must set up both SQL and Rdb/Dispatch environments: $ @SYS$LIBRARY:SQL$SETVER 6.0 Otherwise, to use DBI, users only need to set up an Rdb/Dispatch environment: $ @SYS$LIBRARY:SQL$SETVER 6.0 DISPATCH Check that you have the databases set up properly. For example, if you are using DEC Rdb, the version must be set as explained in Section 1.3.3. 3.3 Running the Installation Verification Procedure Separately The Installation Verification Procedure (IVP) is usually run during installation. If you want to run the IVP separately to ensure the integrity of installed files, enter: $ @SYS$COMMON:[SYSTEST]DBI$IVP The IVP uses the DBI sample database provided for use by all DBI users. To invoke the sample directly, enter: $ @DBI$EXAMPLES:DBI_SAMPLE 3.4 Editing the System Files Edit the system startup files to enable automatic startup of DBI when your system is restarted. Add the following command line, which starts DBI, to the system startup file, SYS$MANAGER:SYSTARTUP_V5.COM: $ @SYS$STARTUP:DBI$STARTUP.COM After Installation 3-3 3.5 Making the Product Usable on a VMScluster To prevent failures running DEC Rdb applications on cluster nodes, you must run the SYS$STARTUP:DBI$STARTUP command file on all cluster nodes that share the system disk on which DBI was installed. You can accomplish this by using the SYSMAN utility to install the required images on each node. $ RUN SYS$SYSTEM:SYSMAN SYSMAN> SET ENVIRONMENT/CLUSTER %SYSMAN-I-ENV, current command environment: Clusterwide on local cluster Username SYSTEM will be used on nonlocal nodes SYSMAN> DO @SYS$STARTUP:DBI$STARTUP %SYSMAN-I-OUTPUT, command execution on node NODE1 %SYSMAN-I-OUTPUT, command execution on node NODE2 SYSMAN> EXIT The DBI$STARTUP command file calls SYS$LIBRARY:SQL$STARTUP to install the following Rdb/Dispatch images into memory: RDBSHR.EXE RDB$SHARE.EXE COSI$MSG.EXE 3-4 After Installation A ________________________________________________________________ Prerequisite Installation of Common Components This chapter describes how to install the Common Components, a prerequisite for installation of DEC DB Integrator (DBI) and the DEC DB Integrator Gateway products (DB Integrator Gateways, also referred to as the gateway products). Please note the following requirements: o If you have an existing DEC Rdb kit on your system, you must install the Common Components or install DEC Rdb Version 6.0 before you can use any member of the DBI product family. o If you choose not to upgrade to DEC Rdb Version 6.0, Digital recommends that you install the multiversion Common Components. Installing the multiversion Common Components will not break applications or production systems that require previous versions of DEC Rdb. For more information, see Section A.1.2. o If you do not have DEC Rdb on your system, and do not plan to install it, you must install the Common Components before you can use the DBI product family. A.1 Common Components The Common Components provides support for relational database functions for Digital database products. These components are common to DBI, the DBI gateway products, and DEC Rdb. The Common Components are: o SQL interface o SQL/Services server Prerequisite Installation of Common Components A-1 o Rdb/Dispatch and Rdb/Remote server These components must be present on a system in order to run SQL applications. A.1.1 Media Required When you purchase any of the Digital database access products (DBI, DB Integrator Gateways, or DEC Rdb), you receive the kit for that product, plus an entire DEC Rdb software kit, which contains the Common Components. You only need to install the Common Components from the DEC Rdb kit, not the entire kit to use the Common Components with DBI or the gateway products. Install the Common Components using the DEC Rdb installation procedure by choosing the Common Components option during the installation. The Common Components must be present on your system before you can install DBI or a gateway product. A.1.2 Version Variants and Existing Databases If you have a version of DEC Rdb prior to Version 6.0 installed, you do not need to upgrade DEC Rdb in order to install members of the DBI product family, but you must install the Common Components from the DEC Rdb media. Digital recommends that you install the multiversion Common Components if you expect to maintain more than one version of Rdb. The Common Components have two possible variants: o Standard Use when you have only one version of DEC Rdb on your system. o Multiversion Use when you have multiple versions of DEC Rdb or a version DEC Rdb that is different from the version of the Common Components being installed. Installing the multiversion variant will not write over any existing DEC Rdb images from previous versions, such as the Online Help. If you install the multi- version variant of Common Components, you can use the SYS$LIBRARY:SQL$SETVER.COM procedure to control the A-2 Prerequisite Installation of Common Components version of Common Components whenever your database environment requires a particular version of SQL or Rdb/Dispatch. For more information about SQL$SETVER, see Section A.8. A.2 Disk Space Required The following tables summarize the storage requirements for installing the Common Components. The values in the lists are approximate. The disk space requirements for OpenVMS AXP are: __________________________________________________________ Needed for Used After Kit______________Installation_________Installation________ Full Development 62,000 62,000 Run-Time_________62,000_______________39,000<>____________ The disk space requirements for OpenVMS VAX are: __________________________________________________________ Used After Kit______________Needed_for_Installation_Installation_____ Full Development 40,000 40,000 Run-Time_________40,000__________________28,000<>_________ A.3 OpenVMS Privileges Required The VMSINSTAL command procedure is located in SYS$UPDATE, which is a restricted directory. To install the Common Components, you must use an account that has the SETPRV privilege authorized. As one of its first actions, the VMSINSTAL command procedure grants all privileges except BYPASS to the process that invokes it. The VMSINSTAL command succeeds only if the installing account has SETPRV privilege. To check the default privileges of the installing account, log in and enter this DCL command: $ SHOW PROCESS/PRIVILEGES Prerequisite Installation of Common Components A-3 If the installing account lacks the SETPRV privilege, you cannot install the Common Components. You have two options: o Ask your system manager to use the OpenVMS Authorize utility (AUTHORIZE) to modify the default privileges of the account to include the SETPRV privilege. A-4 Prerequisite Installation of Common Components o Run AUTHORIZE and make the changes yourself, if the installing account has the SYSPRV privilege: $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> MODIFY /PRIVILEGES=(SETPRV) UAF> EXIT To activate the change in privileges, you must log out and then log in. ________________________Note ________________________ When installing the Common Components on systems with DECnet/OSI, the installing account must also have the NET$MANAGE identifier. _____________________________________________________ A.4 Unlocking the Process Account Password The installing account cannot have a locked password. If this is the initial installation of the Common Components, the installation procedure creates an account called RDB$REMOTE, or RDB$REMOTEnn for a multiversion installation. If the installing account has a locked password, the installation procedure will be unable to automatically generate a password for this account, and will abort with the following message: ************************************************************* Error generating password for remote account. ************************************************************** To modify an account with a locked password, enter: $ MCR AUTHORIZE UAF> MODIFY /FLAGS=NOLOCKPWD Prerequisite Installation of Common Components A-5 A.5 Installing Common Components To install Common Components: 1. Invoke the VMSINSTAL command procedure from a privileged account, using the following syntax: @SYS$UPDATE:VMSINSTAL variant-name device-name OPTIONS N Supply the appropriate name for the variant you want to install from the following table: _______________________________________________________ Name_____________Variant__________OpenVMS______________ DECRDBA060 standard AXP DECRDBAMV060 multiversion AXP DECRDB060 standard VAX DECRDBMV060______multiversion_____VAX__________________ Digital recommends that you install the multiversion kit. This avoids possible problems in writing over existing files and images for a different version of the Common Components or DEC Rdb. For example, to install the Common Components OpenVMS AXP multiversion kit on device ddcu, enter: $ @SYS$UPDATE:VMSINSTAL decrdbamv060 ddcu: OPTIONS N To install the Common Components OpenVMS VAX standard kit on device ddcu, enter: $ @SYS$UPDATE:VMSINSTAL decrdb060 ddcu: OPTIONS N 2. Type CC (for COMMON COMPONENTS) when prompted for the kit type to install. The menu and response should appear as follows: *********************************************************************** From the following menu, please select the type of DEC Rdb kit to install. Choice CC (COMMON COMPONENTS) is included in all 3 DEC Rdb installations and should only be selected when installing a product, other than DEC Rdb, that requires the common components. *********************************************************************** A-6 Prerequisite Installation of Common Components Please select the type of DEC Rdb kit you wish to install: Enter DEV for DEC Rdb DEVELOPMENT (the default) Enter INT for DEC Rdb INTERACTIVE Enter RTO for DEC Rdb RUNTIME-ONLY Enter CC for COMMON COMPONENTS * Enter the kit type to install [DEV]: CC Prerequisite Installation of Common Components A-7 When you enter CC, only the Common Components save set (B) will be restored. The following submenu will be displayed: *********************************************************************** The COMMON COMPONENTS option should be selected only when installing a product other than Rdb. It is not intended for use with any Rdb installation. *********************************************************************** Please select the type of COMMON COMPONENTS kit you wish to install: Enter DEV for DEVELOPMENT Enter RTO for RUNTIME-ONLY (the default) * Enter the type of COMMON COMPONENTS to install [RTO]: 3. Press the Return key to select the default option, RUNTIME-ONLY. Do not select the DEVELOPMENT option unless you have purchased one of the following development licenses: o DEC SQL development license o DEC Rdb development license o DEC DB Integrator (DBI) development license Selecting the DEVELOPMENT option provides the addi- tional SQL files needed for development: SQL$PREnn.EXE, SQL$MODnn.EXE; a small number of related files; and all the Rdb/Dispatch and SQL files installed with the RTO default. A.6 Installing Common Components Images as Shared The Common Components installation procedure does not install any images as shared. If you expect Common Components images to be used extensively on your system, you can reduce the system overhead and memory requirements by installing images as shared. When images are not installed as shared, multiple users who access the images at the same time must each have his or her own copy of those images in memory. When the images are installed as shared, everyone uses the same copy of the image, A-8 Prerequisite Installation of Common Components eliminating duplicate copies of an image and improving performance. Prerequisite Installation of Common Components A-9 A.6.1 Editing the Startup and Shutdown Procedures for Shared Images The separate startup and shutdown procedures, which are provided to install and remove the SQL and Rdb/Dispatch images, are as follows: o SYS$STARTUP:SQL$STARTUP.COM o SYS$MANAGER:SQL$SHUTDOWN.COM DBI and the DBI Gateways will call these procedures from their own startup and shutdown procedures. The following Rdb/Dispatch images are automatically installed by the SQL$STARTUP.COM procedure: o SYS$LIBRARY:RDBSHR.EXE o SYS$LIBRARY:RDB$SHARE.EXE o SYS$MESSAGE:RDBMSGS.EXE o SYS$MESSAGE:COSIMSG.EXE SQL files are not currently installed by the SQL$STARTUP.COM procedure. However, subroutines to install or to remove these images are included in the SQL$STARTUP.COM proce- dure. To activate the subroutines for the installation and/or removal of SQL images, remove the comment character (!) from the following lines in the SQL$STARTUP.COM and SQL$SHUTDOWN.COM procedures: $ ! GOSUB INSTALL_SQL_IMAGES $ ! GOSUB REMOVE_SQL_IMAGES If you invoke the INSTALL_SQL_IMAGES subroutine, the SQL$STARTUP.COM procedure installs the following SQL images: o SYS$LIBRARY:SQL$INT.EXE o SYS$LIBRARY:SQL$SHR.EXE o SYS$MESSAGE:SQL$MSG.EXE The INSTALL_SQL_IMAGES subroutine also includes code to install the SQL$UTL_SHARE60.EXE image and the development images, SQL$.EXE, SQL$MOD.EXE, and SQL$PRE.EXE. To execute the installations, remove the comment character preceding the code. The SQL$STARTUP.COM procedure provides an A-10 Prerequisite Installation of Common Components explanation why these images are not included in the default installations. Prerequisite Installation of Common Components A-11 Because SQL$UTL_SHAREnn.EXE is a variant image for both standard and multiversion Common Components, you must add additional lines of code to install images for each Common Components version you install as shared. Development images are not typically installed as shared images. A.6.2 Verifying Global Pages and Sections Table A-1 and Table A-2 show the remaining Common Components images not installed as shared on your system. SQL images not installed as shared during Common Components installation are also included in these tables to show the global page and global section requirements. If you install some or all of these images as shared, you must verify that you have enough global pages and global sections to accommodate the shared images. Use the following DCL F$GETSYI lexical function to determine the number of available global pages and global sections: $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES") $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS") If the number of unused global pages or global sections is less than the number specified in Table A-1 and Table A-2, increase the value using the AUTOGEN utility. Table A-1 lists the approximate number of global pages and global sections required for each Common Components OpenVMS VAX image that you install as shared. <> Table A-2 lists the approximate number of global pagelets and global sections required for each Common Components OpenVMS AXP image that you install as shared. On OpenVMS AXP systems, the size of a page can differ on different systems. Pagelets are 512 bytes and correspond to OpenVMS VAX pages; they are not system-specific. <> A-12 Prerequisite Installation of Common Components Table A-1 Global Pages and Sections Required for Common __________Components_OpenVMS_VAX_Images_________________________ GlobalGlobal Component_____________Image_Name[1]___________________Pages[Sections[2] SQL images SYS$LIBRARY:SQL$INT.EXE[3] 3 2 * SYS$LIBRARY:SQL$SHR.EXE 16 2 SYS$LIBRARY:SQL$UTL_ 142 3 SHARE60.EXE * SYS$MESSAGE:SQL$MSG.EXE 329 1 * SYS$SYSTEM:SQL$.EXE 1635 2 * SYS$SYSTEM:SQL$PRE.EXE 4911 3 * SYS$SYSTEM:SQL$MOD.EXE 4768 3 [1]If_you_have_installed_the_multiversion_variant_of_the_Common_ Components, some images have the version number added to the end of the image name. Those images are marked with an asterisk next to the image name. [2]Values supplied are approximate. If you have installed the multiversion variant of the Common Components, multiply the supplied values by the number of versions of the Common Components running on your system. [3]SQL$INT calls either SQL$SHR, or a version-specific variant (such as SQL$SHR60), depending on what version you have specified. ________________________________________________________________ Prerequisite Installation of Common Components A-13 Table A-2 Global Pagelets and Sections Required for Common __________Components_OpenVMS_AXP_Images_________________________ GlobalGlobal Component_____________Image_Name[1]___________________PageleSections[2] SQL images SYS$LIBRARY:SQL$INT.EXE[3] 65 1 * SYS$LIBRARY:SQL$SHR.EXE 2394 2 SYS$LIBRARY:SQL$UTL_ 431 2 SHARE60.EXE * SYS$MESSAGE:SQL$MSG.EXE 329 1 * SYS$SYSTEM:SQL$.EXE 3237 1 * SYS$SYSTEM:SQL$PRE.EXE 8461 2 * SYS$SYSTEM:SQL$MOD.EXE 8166 2 [1]If_you_have_installed_the_multiversion_variant_of_the_Common_ Components, some images have the version number added to the end of the image name. Those images are marked with an asterisk next to the image name. [2]Values supplied are approximate. If you have installed the multiversion variant of the Common Components, multiply the supplied values by the number of versions of the Common Components running on your system. [3]SQL$INT calls either SQL$SHR, or a version-specific variant (such as SQL$SHR60), depending on what version you have specified. ________________________________________________________________ A.6.3 Removing Installed Images The SQL$SHUTDOWN.COM procedure removes Common Components images that have been installed. By default, the SQL$SHUTDOWN.COM procedure removes only the images installed by Rdb/Dispatch. However, a subroutine is included that removes the SQL images. To activate this subroutine, remove the comment character (!) from the following line in the SQL$SHUTDOWN.COM procedure where this subroutine is invoked: $ ! GOSUB REMOVE_SQL_IMAGES ! In SQL$SHUTDOWN.COM A-14 Prerequisite Installation of Common Components The SQL$SHUTDOWN.COM procedure only removes images when no other client requiring the Common Components is installed on the system. Consequently, it requires that you pass a calling-client parameter, which is also referred to as P1, to determine if any other clients are still present on the system. You must execute the SQL$SETVER.COM procedure before you execute the SQL$SHUTDOWN.COM procedure. Otherwise, you receive an error message indicating that the logical names were not set. For more information about SQL$SETVER.COM, see Section A.8. The syntax for using the SQL$SHUTDOWN.COM procedure is as follows: $ @SYS$LIBRARY:SQL$SETVER $ @SYS$MANAGER:SQL$SHUTDOWN In the preceding example, is the Common Components version shipped with the client, and is one of the following: o DBI-use for DBI and the relational gateway products o NSDS-use for the nonrelational gateway products o RDBB-use for Rdb/ELN o RDM-use for DEC Rdb o VIDA-use for VIDA for IDMS/R o VIDA2-use for RdbAccess for DB2 Version 1.0 or Version 2.0 o VIDAO-use for RdbAccess for ORACLE Version 1.0 or Version 2.0 The relational gateway products are: o DEC DB Integrator Gateway for DB2 o DEC DB Integrator Gateway for EDA/SQL o DEC DB Integrator Gateway for ORACLE o DEC DB Integrator Gateway for SequeLink o DEC DB Integrator Gateway for SYBASE Prerequisite Installation of Common Components A-15 The nonrelational gateway products are: o DEC DB Integrator Gateway for Custom Drivers o DEC DB Integrator Gateway for DBMS o DEC DB Integrator Gateway for DSM o DEC DB Integrator Gateway for RMS The following example sets the Common Components to Version 6.0, then removes the images for the nonrelational gateway products: $ @SYS$LIBRARY:SQL$SETVER 6.0 $ @SYS$MANAGER:SQL$SHUTDOWN NSDS By default, the removal of images from the INSTALL utility is triggered by the logical names SQL$VERSION_VARIANT and RDB$DISPATCH_VERSION_VARIANT, which are defined by the SYS$LIBRARY:SQL$SETVER.COM procedure. ________________________Note ________________________ It is possible to set these logical names to different versions for the process, job, group, and system tables, if necessary. However, be very careful to avoid creating incompatibilities if you do so. Do this only when advised that it is absolutely necessary to solve a particular problem. _____________________________________________________ You can override the SQL$VERSION_VARIANT and RDB$DISPATCH_ VERSION_VARIANT logical names by passing a valid calling- client name as parameter P1, and the Common Components version to remove as P2. To override the use of the logical names to determine which Common Component images to remove, pass the version as P2. The following command removes Version 6.0 images: $ @SYS$MANAGER:SQL$SHUTDOWN DBI 6.0 If the DEC Rdb multiversion Version 6.0 software is installed, only the Version 6.0 images will be removed; otherwise the standard images, if they are Version 6.0 images, will be removed. A-16 Prerequisite Installation of Common Components A.7 Installing SQL Images for Privileged Applications Applications that use SQL and are installed with privileges require that you install the following images: o SYS$LIBRARY:SQL$INT.EXE o SYS$LIBRARY:SQL$SHR.EXE (or SYS$LIBRARY:SQL$SHR60.EXE) None of the SQL images supplied as part of the Common Components is installed unless you modify the SQL$STARTUP.COM procedure to permit it. Unless you install these images, applications installed with privileges will encounter the following error: %SQL-F-NOENTRYPT, Older SQL version not compatible with compiled SQL It is not necessary to install the SQL images as shared or with privileges to avoid this error. Installing in any manner will avoid the error. The separate startup and shutdown procedures, which are provided to install and remove the SQL and Rdb/Dispatch images, are as follows: o SYS$STARTUP:SQL$STARTUP.COM o SYS$MANAGER:SQL$SHUTDOWN.COM DBI and the DBI Gateways will call these procedures from their own startup and shutdown procedures. The following Rdb/Dispatch images are automatically installed by the SQL$STARTUP.COM procedure: o SYS$LIBRARY:RDBSHR.EXE o SYS$LIBRARY:RDB$SHARE.EXE o SYS$MESSAGE:RDBMSGS.EXE o SYS$MESSAGE:COSI$MSG.EXE Prerequisite Installation of Common Components A-17 A.7.1 Editing the Startup and Shutdown Procedures for Privileged Applications SQL files are not currently installed by the SQL$STARTUP.COM procedure. However, a subroutine to install these images is included in the SQL$STARTUP.COM procedure. To activate the installation and/or removal of SQL images, remove the comment character (!) from the following lines in the SQL$STARTUP.COM and SQL$SHUTDOWN.COM procedures: $ ! GOSUB INSTALL_SQL_IMAGES $ ! GOSUB REMOVE_SQL_IMAGES The INSTALL_SQL_IMAGES subroutine in the SQL$STARTUP.COM procedure installs the following SQL images: o SYS$LIBRARY:SQL$INT.EXE o SYS$LIBRARY:SQL$SHR.EXE (or SYS$LIBRARY:SQL$SHR60.EXE) o SYS$MESSAGE:SQL$MSG.EXE (or SYS$MESSAGE:SQL$MSG60.EXE) The subroutine also includes code to install the development images SQL$.EXE, SQL$MOD.EXE, and SQL$PRE.EXE, and the internal SQL utilities image SQL$UTL_SHARE60.EXE. To execute the installations, you must remove the comment character that precedes the code. The SQL$STARTUP.COM procedure provides an explanation of why these images are not included in the default installations. Because the SQL$UTL_SHAREnn.EXE image is a variant image for both standard and multiversion Common Components, you must add additional lines for each Common Components version you install as shared. Development images are not typically installed as shared images. If you install some or all of these images as shared, you must verify that you have enough global pages and global sections to accommodate the shared images. Table A-1 lists the approximate number of global pages and global sections required for each Common Components for OpenVMS VAX image that you install as shared.<> Table A-2 provides the global pagelets and sections required for the Common Components for OpenVMS AXP images. On OpenVMS AXP systems, the size of a page can differ on A-18 Prerequisite Installation of Common Components different CPUs. Pagelets are 512 bytes and correspond to OpenVMS VAX pages; they are not CPU-specific. <> A.8 Using Different Versions of the Common Components Certain environments may require a specific version of the Common Components, or may need to set each component to a different version. The SYS$LIBRARY:SQL$SETVER.COM and SYS$LIBRARY:SQL$SHOVER.COM procedures are provided with the Common Components installation to set up the logical names and symbols necessary for using a particular version of SQL and/or Rdb/Dispatch. ________________________Note ________________________ To use the DBI Gateway products or DEC DB Integrator, the Common Components' environment must be set to 6.0. This can be done at the system, group, or process level, as described in the following section. _____________________________________________________ The SQL$SETVER.COM procedure will accept the following three parameters: o P1 = (REQUIRED) version (that is, S for STANDARD, 6.0 for MULTIVERSION) or RESET to reset SQL symbols or REMOVE to remove SQL and DISPATCH logical names. o P2 = (OPTIONAL) Logical name table qualifier (PROCESS, GROUP, JOB, or SYSTEM). The default is PROCESS. o P3 = (OPTIONAL) Common Components logical names to set (SQL, DISPATCH, or ALL). The default is ALL. This can go in P2 or P3 as the last parameter. The following example sets both SQL and Rdb/Dispatch to multiversion Version 6.0. If multiversion Version 6.0 is not installed and a standard version is found, the standard version will be set. $ @SYS$LIBRARY:SQL$SETVER 6.0 Current PROCESS SQL environment is version 6.0-0 (MULTIVERSION) Current PROCESS Rdb/Dispatch environment is version 6.0-0 (MULTIVERSION) Prerequisite Installation of Common Components A-19 The following examples show other possible parameters: ! To set only Rdb/Dispatch $ @SYS$LIBRARY:SQL$SETVER 6.0 DISPATCH ! To set only SQL $ @SYS$LIBRARY:SQL$SETVER 6.0 SQL ! To set only SQL in group table $ @SYS$LIBRARY:SQL$SETVER 6.0 /GROUP SQL ! To set both SQL and Rdb/Dispatch to standard version $ @SYS$LIBRARY:SQL$SETVER S ! To set only Rdb/Dispatch to standard version $ @SYS$LIBRARY:SQL$SETVER S DISPATCH ! To set only SQL to standard version $ @SYS$LIBRARY:SQL$SETVER S SQL The SQL$SHOVER.COM procedure has the following two functions: o To show the current settings for each logical name table: $ @SYS$LIBRARY:SQL$SHOVER Current PROCESS SQL environment is version 6.0-0 (MULTIVERSION) Current PROCESS DISPATCH environment is version 6.0-0 (MULTIVERSION) o To show all the versions installed on the system. You can use this to determine what the highest version of Rdb/Dispatch or SQL is installed on the system. $ @SYS$LIBRARY:SQL$SHOVER VERSIONS "SQL$INSTALLED_VERSIONS" = "*6.0-0" (LNM$PROCESS_TABLE) "RDB$DISPATCH_INSTALLED_VERSIONS" = "V4.0-5" (LNM$PROCESS_TABLE) "*6.0-0" The * in the preceding output indicates a multiversion kit. The following examples show other possible parameters: ! To show only Rdb/Dispatch $ @SYS$LIBRARY:SQL$SHOVER VERSIONS DISPATCH ! To show only SQL $ @SYS$LIBRARY:SQL$SHOVER VERSIONS SQL ! To show only 6.0 Rdb/Dispatch $ @SYS$LIBRARY:SQL$SHOVER VERSIONS DISPATCH 6.0 ! To show only 6.0 SQL and suppress output $ @SYS$LIBRARY:SQL$SHOVER VERSIONS SQL 6.0 NOSHOW A-20 Prerequisite Installation of Common Components A.9 Deleting Versions of the Common Components For your convenience, the Common Components kit provides a command procedure, SYS$MANAGER:SQL$DEINSTALL_DELETE.COM, to delete current or previous versions of the Common Components. You must run this command procedure from an account that has SETPRV privileges, or from an account that has SYSPRV, CMKRNL, SYSNAM, and WORLD privileges. You can use this command file to delete previous versions of the Common Components when you have installed a newer version and determine that prior versions are no longer needed. ________________________Note ________________________ The SQL$DEINSTALL_DELETE.COM procedure will not execute if multiple products requiring Common Components are found on the system or DEC Rdb of the same version is found on the system. _____________________________________________________ When you run the command procedure, you may choose to pass a single parameter that indicates the output location for all messages generated while the command procedure processes. This parameter can either be the name of a file (for example, SQL$DEINSTALL_DELETE.LOG) or the logical name SYS$OUTPUT (which displays messages on your screen). To run the SQL$DEINSTALL_DELETE command procedure and have messages sent to a file named SQL$DEINSTALL_DELETE.LOG, enter: $ @SYS$MANAGER:SQL$DEINSTALL_DELETE.COM SQL$DEINSTALL_DELETE.LOG The command procedure checks for the existence of the different versions of the Common Components on your system, and then displays a menu listing each version found (standard first, and then the oldest to the most current multiversion): Prerequisite Installation of Common Components A-21 SQL versions currently installed on your system * Version 5.1 (Multiversion) 1 Version 6.0 (Multiversion) 0 Quit (* This version cannot be deinstalled by this procedure) Enter Choice to deinstall (0...1) : 0 If the command procedure displays an asterisk (*) next to a version entry on the menu, it means that version cannot be deleted by the SQL$DEINSTALL_DELETE.COM procedure because it is prior to Version 6.0. Enter the menu number for the version you want to delete. For example, to delete Version 6.0 multiversion, enter the following: Enter Choice to deinstall (0...1) : 1 The command procedure displays the following message: You are about to deinstall SQL 6.0 (Multiversion) If your system is a cluster member, this procedure creates the SYS$SCRATCH:SQL$CLUSTER_DEINSTALL60.COM procedure. Use this command procedure to remove the Common Components Version 6.0 (multiversion) from other nodes in the cluster. You must either run this command procedure on each node that has Common Components Version 6.0 (multiversion) installed, or use the SYSMAN utility to run it clusterwide. Next, the command procedure asks you to confirm that you want to continue with the deinstallation (whether or not your system is part of a cluster): Enter Y(ES) to continue to deinstall SQL 6.0 (Multiversion): YES The final prompt asks you whether or not you want to delete the RDB$REMOTE account for the version you specified (keep this account if, for example, you plan to use it as a template to build other accounts): Do you want to delete RDB$REMOTE60? [N]: YES A-22 Prerequisite Installation of Common Components When the command procedure completes the deletion of the appropriate files, it displays the following message: %SQL-I-END Deinstallation of SQL 6.0 (Multiversion) now complete Prerequisite Installation of Common Components A-23 B ________________________________________________________________ Sample DBI Installation The following is a sample installation of DBI on an OpenVMS VAX system. The installation of DBI on an OpenVMS AXP system would be very similar. In this example, the save set has been copied to the SYS$SYSROOT:[SYSMGR] directory before the installation. The sample also includes the running of the IVP. $ @SYS$UPDATE:VMSINSTAL VAX/VMS Software Product Installation Procedure V5.5-2 It is 28-OCT-1994 at 11:07. Enter a question mark (?) at any time for help. %VMSINSTAL-W-ACTIVE, The following processes are still active: SERVER_007C * Do you want to continue anyway [NO]? Y * Are you satisfied with the backup of your system disk [YES]? Y * Where will the distribution volumes be mounted: SYS$COMMON:[SYSMGR] Enter the products to be processed from the first distribution volume set. * Products: DBI031 * Enter installation options you wish to use (none): The following products will be processed: DBI V3.1 Beginning installation of DBI V3.1 at 11:08 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. ******************************************************************* © Digital Equipment Corporation 1993, 1994. All rights reserved. Sample DBI Installation B-1 Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. ******************************************************************* DEC DB Integrator for OpenVMS VAX installation procedure for: DBI V3.1-00 *******************************************************************" The DBI Installation Guide will be provided in SYS$HELP upon completion of a successful installation. * Would you like to print the DBI Installation Guide on SYS$PRINT [NO]? N %DBI-I-CHECK_SYS_REQ, Checking system requirements... Product: DBI-DEV Producer: DEC Version: 3.1 Release Date: 01-JAN-1994 * Does this product have an authorization key registered and loaded? Y DBI V3.1 metadata can be stored in a DEC Rdb database or an ORACLE V7 database or a SYBASE V4.9.2 database. You will be asked below if you would like the capability to store metadata in the above database types. You must answer yes to at least one of these options, but you may answer yes to two or more of these options. If you answer yes to the option of storing metadata in an ORACLE V7 database, you must have ORACLE V7 installed on the node where this installation is being performed so that the necessary images can be built in the post-installation phase. Please see the Installation Guide for more details. * Do you want the capability to store metadata in a DEC Rdb database [YES]? Y * Do you want the capability to store metadata in an ORACLE database [YES]? N * Do you want the capability to store metadata in a SYBASE database [YES]? Y * Do you want to run the IVP after the installation [YES]? Y B-2 Sample DBI Installation * Do you want to purge files replaced by this installation [YES]? Y ************************************************************** There are no more questions. The installation and IVP take between 10 and 45 minutes depending on processor type and machine load. ************************************************************** ************************************************************** Installing DEC DB Integrator for OpenVMS VAX V3.1-00 under OpenVMS V5.5-2 - 28-OCT-1994 11:09 ************************************************************** %VMSINSTAL-I-RESTORE, Restoring product save set B ... ************************************************************** Adding DBI help to the DCL help library ************************************************************** ************************************************************** DBI$STARTUP.COM has been placed in SYS$STARTUP. The following line should be placed in your system startup file. $ @SYS$STARTUP:DBI$STARTUP.COM ************************************************************** The IVP has been placed in SYS$COMMON:[SYSTEST]. You may run this procedure separately at any time. To execute it, type: $ @SYS$COMMON:[SYSTEST]DBI$IVP ************************************************************** %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... ________________________Note ________________________ If you chose not to run the IVP, the installation ends here. If you chose to run the IVP, the installation continues. _____________________________________________________ Sample DBI Installation B-3 Copyright © 1994 Digital Equipment Corporation All Rights Reserved. Current PROCESS SQL environment is version V6.0-0 (MULTIVERSION) Current PROCESS Rdb/Dispatch environment is version V6.0-1 (MULTIVERSION) This procedure creates 3 Rdb databases, each of which will hold tables from the PERSONNEL database. After the databases are created and loaded, a DBI database will be created. The PERSONNEL databases will then be linked with the DBI database. All the tables in the three PERSONNEL databases will be imported into the DBI database. The final result, when viewed through the DBI database, will be that the PERSONNEL databases will look like they are one single database by virtue of the integration capabilities provided by DBI. Creating the PERSONNEL databases... Granting database privileges... Creating domains for the PERSONNEL databases... Creating tables for the PERSONNEL databases... Completed definition of the PERSONNEL databases... Loading the tables in the PERSONNEL databases... Completed the population of the PERSONNEL databases... Now creating the DBI database... The DBI database has been successfully created. Now creating LINKs to PERSONNEL databases and importing tables... User tables in database with filename SQL$DATABASE CANDIDATES COLLEGES DEGREES DEPARTMENTS EMPLOYEES JOBS JOB_HISTORY RESUMES SALARY_HISTORY WORK_STATUS The PERSONNEL databases have been successfully integrated - now creating the views... B-4 Sample DBI Installation User tables in database with filename SQL$DATABASE CANDIDATES COLLEGES CURRENT_INFO A view. CURRENT_JOB A view. CURRENT_SALARY A view. DEGREES DEPARTMENTS EMPLOYEES JOBS JOB_HISTORY RESUMES SALARY_HISTORY WORK_STATUS The PERSONNEL databases have been successfully created and integrated and a set of sample queries have executed successfully. Installation of DBI V3.1 completed at 11:23 Enter the products to be processed from the next distribution volume set. * Products: Exit VMSINSTAL procedure done at 11:24 The VMSINSTAL procedure deletes or changes entries in the process symbol tables during the installation. Therefore, if you are going to continue using the installation account (such as SYSTEM) and you want to restore these symbols, you should log out and log in again. Sample DBI Installation B-5 C ________________________________________________________________ List of Files on DBI Kit The following tables show the files created on your system by the DBI installation and the directories to which they are moved. Table C-1 shows the files created on OpenVMS VAX systems. Table_C-1_DBI_Installed_Files_for_OpenVMS_VAX_____________ Directory_______________________File______________________ SYS$COMMON:[SYSHLP] DBI031_INSTALL_GUIDE.TXT DBI031.RELEASE_NOTES DBI_MSG.DOC SYS$COMMON:[SYSHLP.EXAMPLES.DBI]ATTACH_ALL_PERS.SQL CREATE_DBI_VIEWS.SQL CREATE_LINKS.SQL CREATE_PERS_TABLES.SQL DATABASE_PRIVS.SQL DBI_DB_CREATE.COM DBI_LICENSE_VAX.COM DBI_SAMPLE.COM DOMAIN_CREATE.SQL IMPORT_TABLES.SQL POPULATE_CANDIDATES.SQL POPULATE_COLLEGES.SQL POPULATE_DEGREES.SQL (continued on next page) List of Files on DBI Kit C-1 Table_C-1_(Cont.)_DBI_Installed_Files_for_OpenVMS_VAX_____ Directory_______________________File______________________ POPULATE_DEPTS.SQL POPULATE_EMPLOYEES.SQL POPULATE_JOBHIST.SQL POPULATE_JOBS.SQL POPULATE_SALHIST.SQL POPULATE_WORK_STATUS.SQL SYS$COMMON:[SYSLIB] DBI$CI_RDBSHR.EXE DBI$CI_SYBSHR.EXE DBI$DDRV_SHR.EXE DBI$SHR.EXE DBI_CCCHECK.COM DBI_CI_RDB_CONVERT.COM DBI_CI_RDB_CONVERT.SQL DBI_USER_SETUP.COM DBI$SQLSHR.EXE SYS$COMMON:[SYSMGR] DBI$SHUTDOWN.COM DBI$SHUTDOWN_COMMON.COM SYS$COMMON:[SYSMSG] DBI$DDRV_MSG.EXE DBI_MSG.EXE SYS$COMMON:[SYS$STARTUP] DBI$STARTUP.COM DBI$STARTUP_COMMON.COM DBI_DELETE_FILES.COM SYS$COMMON:[SYSTEST]____________DBI$IVP.COM_______________ If you chose to allow for ORACLE catalog creation during installation, the files shown in Table C-2 are included in your system. C-2 List of Files on DBI Kit Table_C-2_ORACLE_Files_Installed_for_OpenVMS_VAX__________ Directory_______________________File______________________ SYS$COMMON:[SYSLIB] DBI_CI_ORA_CONVERT.COM DBI_CI_ORA_CONVERT.COM DBI_CI_ORA_CONVERT.SQL DBICI_COMMON_GLOBALS.OBJ DBICI_COMMON_IDENT.OPT DBICI_ORA.OLB DBICI_ORASHR_VAX.OPT ________________________________DBI_ORABLD.COM____________ <> Table C-3 shows the files created on OpenVMS AXP systems. Table_C-3_DBI_Installed_Files_for_OpenVMS_AXP_____________ Directory_______________________File______________________ SYS$COMMON:[SYSHLP] DBI031_INSTALL_GUIDE.TXT DBI031.RELEASE_NOTES DBI_MSG.DOC SYS$COMMON:[SYSHLP.EXAMPLES.DBI]ATTACH_ALL_PERS.SQL CREATE_DBI_VIEWS.SQL CREATE_LINKS.SQL CREATE_PERS_TABLES.SQL DATABASE_PRIVS.SQL DBI_DB_CREATE.COM DBI_LICENSE_ALPHA.COM DBI_SAMPLE.COM DOMAIN_CREATE.SQL IMPORT_TABLES.SQL POPULATE_CANDIDATES.SQL POPULATE_COLLEGES.SQL POPULATE_DEGREES.SQL POPULATE_DEPTS.SQL POPULATE_EMPLOYEES.SQL (continued on next page) List of Files on DBI Kit C-3 Table_C-3_(Cont.)_DBI_Installed_Files_for_OpenVMS_AXP_____ Directory_______________________File______________________ POPULATE_JOBHIST.SQL POPULATE_JOBS.SQL POPULATE_SALHIST.SQL POPULATE_WORK_STATUS.SQL SYS$COMMON:[SYSLIB] DBI$CI_RDBSHR.EXE DBI$CI_SYBSHR.EXE DBI$DDRV_SHR.EXE DBI$SHR.EXE DBI_CCCHECK.COM DBI_CI_RDB_CONVERT.COM DBI_CI_RDB_CONVERT.SQL DBI_USER_SETUP.COM DBI$SQLSHR.EXE SYS$COMMON:[SYSMGR] DBI$SHUTDOWN.COM DBI$SHUTDOWN_COMMON.COM SYS$COMMON:[SYSMSG] DBI$DDRV_MSG.EXE DBI_MSG.EXE SYS$COMMON:[SYS$STARTUP] DBI$STARTUP.COM DBI$STARTUP_COMMON.COM DBI_DELETE_FILES.COM SYS$COMMON:[SYSTEST]____________DBI$IVP.COM_______________ If you chose to allow for ORACLE catalog creation during installation, the files shown in Table C-4 are included in your system. C-4 List of Files on DBI Kit Table_C-4_ORACLE_Files_Installed_for_OpenVMS_AXP__________ Directory_______________________File______________________ SYS$COMMON:[SYSLIB] DBI_CI_ORA_CONVERT.COM DBI_CI_ORA_CONVERT.COM DBI_CI_ORA_CONVERT.SQL DBICI_COMMON_GLOBALS.OBJ DBICI_COMMON_IDENT.OPT DBICI_ORA.OLB DBICI_ORASHR_ALPHA.OPT ________________________________DBI_ORABLD.COM____________ <> List of Files on DBI Kit C-5 D ________________________________________________________________ How to Order Additional Documentation Technical Support If you need help deciding which documentation best meets your needs, call 800-DIGITAL (800-344-4825) and press 2 for technical assistance. Electronic Orders If you wish to place an order through your account at the Electronic Store, dial 800-234-1998, using a modem set to 2400- or 9600-baud. You must be using a VT terminal or terminal emulator set at 8 bits, no parity. If you need assistance using the Electronic Store, call 800-DIGITAL (800-344-4825) and ask for an Electronic Store specialist. Telephone and Direct Mail Orders __________________________________________________________ From__________Call______________Write_____________________ U.S.A. DECdirect Digital Equipment Phone: 800- Corporation DIGITAL P.O. Box CS2008 (800-344-4825) Nashua, New Hampshire FAX: (603) 884- 03061 5597 Puerto Rico Phone: (809) Digital Equipment 781-0505 Caribbean, Inc. FAX: (809) 749- 3 Digital Plaza, 1st 8377 Street Suite 200 Metro Office Park San Juan, Puerto Rico 00920 How to Order Additional Documentation D-1 __________________________________________________________ From__________Call______________Write_____________________ Canada Phone: 800-267- Digital Equipment of 6215 Canada Ltd. FAX: (613) 592- 100 Herzberg Road 1946 Kanata, Ontario, Canada K2K 2A6 Attn: DECdirect Sales International -- Local Digital subsidiary or approved distributor Internal DTN: 264-3030 U.S. Software Supply Orders[1] (603) 884-3030 Business (SSB) (for Digital Equipment software Corporation and hardware 10 Cotton Road documentation) Nashua, New Hampshire 03063-1260 [1]Call_to_request_an_Internal_Software_Order_Form_(EN-___ 01740-07).________________________________________________ D-2 How to Order Additional Documentation