ACCESSWORKS DB Integrator Gateway for PC Data Client_for_OpenVMS____________________________ Installation and Configuration Guide Part Number: AA-QQDGA-TE September 1995 This guide describes how to install ACCESSWORKS DB Integrator Gateway for PC Data Client for OpenVMS. Revision/Update Information: This is a new guide. Operating System: OpenVMS VAX OpenVMS Alpha Software Version: Accessworks DB Integrator Gateway for PC Data Version 3.1A 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, 1995. All Rights Reserved. The following are trademarks of Digital Equipment Corporation: AIMS, ALL-IN-1, AlphaGeneration, Bookreader, CI, DEC, DEC TCP/IP, DECdecision, DECdtm, DECforms, DECintact, DECnet, DECnet-DOS, DECplan, DECpresent, DECtp, DECwindows, Digital, HSC, MASSBUS, MicroVAX, OpenVMS, PATHWORKS, RA, SPM, ULTRIX, UNIBUS, VAX, VAX Ada, VAX BASIC, VAX C, VAX COBOL, VAX DATATRIEVE, VAX DOCUMENT, VAX FMS, VAX FORTRAN, VAX MACRO, VAX Pascal, VAX Performance Advisor, VAX Rdb/ELN, VAX RMS, VAX SCAN, VAX 6000, VAX TEAMDATA, VAX Xway, VAXcluster, VAXELN, VAXset, VAXstation, VIDA, VMS, VMScluster, and the DIGITAL logo. Digital Operating Systems Name Changes Several of Digital's operating system names have changed. DEC OSF/1 is now known as Digital UNIX. OpenVMS AXP is now known as OpenVMS Alpha. Because of the recent occurrence of these name changes, the software and documentation may not reflect the new operating system names. Notice of Product Name Changes: The product DEC Rdb and a number of other related products were recently purchased from Digital Equipment Corporation by Oracle Corporation. DEC Rdb is now known as Oracle Rdb. Because the sale of these products was concluded recently, the software and documentation do not necessarily reflect the new names for all the products. 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 and Windows 95 are trademarks 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 Oracle Corporation. Oracle CDD/Repository, Oracle CODASYL DBMS, Oracle Expert for Rdb, Oracle RALLY, Oracle Rdb, Oracle TRACE, Pro*C, and SQL Multimedia for Oracle Rdb are trademarks 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 Configuring ACCESSWORKS DB Integrator Gateway for PC Data Client Client 1.1 Components of the Gateway for PC Data........ 1-1 1.1.1 Gateway for PC Data User Interface....... 1-2 1.1.2 Rdb/Dispatch Interface................... 1-2 1.1.3 Gateway for PC Data Client............... 1-2 1.1.4 Gateway for PC Data Server............... 1-3 1.1.5 Personal Computer Data Source............ 1-3 1.1.6 ODBC Administrator....................... 1-3 1.1.7 ODBC Driver Manager...................... 1-3 1.1.8 ODBC Driver for the Data Source.......... 1-3 1.2 Gateway for PC Data Configurations for Access to Target Data Sources....................... 1-3 1.2.1 Gateway for PC Data Network Access Configuration............................ 1-4 1.2.2 Remote Access............................ 1-4 1.3 Coordination with the Personal Computer System....................................... 1-5 1.3.1 Gateway Coordinator...................... 1-5 1.3.2 Gateway for PC Data Server Administrator............................ 1-6 1.3.3 Personal Computer ODBC Administrator..... 1-6 1.4 Setting Up the OpenVMS System................ 1-6 1.5 Gateway for PC Data Server System Setup...... 1-7 iii 2 Preparing for ACCESSWORKS DB Integrator Gateway for PC Data Client Installation 2.1 Prerequisite Hardware........................ 2-1 2.2 Prerequisite and Optional Software........... 2-1 2.2.1 Common Components Installation Requirement.............................. 2-2 2.2.1.1 Why You Must Install Common Components............................. 2-3 2.2.1.2 Checking for Common Components......... 2-3 2.3 License Registration......................... 2-4 2.4 Installation Procedure Requirements.......... 2-5 2.4.1 Privileges and Disk Space................ 2-5 2.4.2 System Parameters........................ 2-6 2.4.2.1 Calculating the Values for GBLPAGES and GBLSECTIONS............................ 2-7 2.4.2.2 Changing System Parameter Values with AUTOGEN................................ 2-8 2.4.3 VMSINSTAL Requirements................... 2-9 2.4.4 System Disk Backup....................... 2-9 3 Installing ACCESSWORKS DB Integrator Gateway for PC Data Client 3.1 Installation Procedure....................... 3-1 3.1.1 Invoking VMSINSTAL....................... 3-1 3.1.2 Steps of the Installation Procedure...... 3-4 4 After Installing ACCESSWORKS DB Integrator Gateway for PC Data Client 4.1 Distributing the Gateway for PC Data Server....................................... 4-1 4.2 Running the Installation Verification Procedure.................................... 4-3 4.2.1 Invoking the IVP......................... 4-4 4.2.2 Sample IVP Log........................... 4-4 4.3 Editing the System Startup Files............. 4-6 4.4 Editing the System Shutdown File............. 4-6 4.5 User Account Privileges Required............. 4-7 4.6 Determining and Reporting Problems........... 4-7 iv 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 B Sample Installation B.1 Sample Installation.......................... B-1 B.2 Sample Installation Verification Procedure... B-4 C Files Installed on Your System D How to Order Additional Documentation Tables 2-1 Disk Space Requirements.................. 2-6 2-2 Minimum Required System Parameter Values................................... 2-7 A-1 Global Pages and Sections Required for Common Components OpenVMS VAX Images .... A-13 v A-2 Global Pagelets and Sections Required for Common Components OpenVMS AXP Images .... A-14 vi ________________________________________________________________ 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 - TRAPASSO@ORION.ENET.DEC.COM o FAX - 603-881-1011 Attn: L.S. Trapasso, DBI Documentation o Postal service L.S. Trapasso 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 ACCESSWORKS DB Integrator Gateway for PC Data Client enables Digital users to access and modify data stored in data sources on personal computers. The gateway consists of two products: o The Gateway for PC Data client software running on a Digital OpenVMS or UNIX system. o The Gateway for PC Data server software running on a personal computer. This guide describes how to install the ACCESSWORKS DB Integrator Gateway for PC Data Client client. Who Should Use This Guide This guide is intended for individuals familiar with network and system management, who install the ACCESSWORKS DB Integrator Gateway for PC Data Client software, and those 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 how to configure ACCESSWORKS DB Integrator Gateway for PC Data Client. Chapter 2 Describes the prerequisites for installation. Chapter 3 Describes the installation procedure. xi Chapter 4 Describes what you must do after installing ACCESSWORKS DB Integrator Gateway for PC Data Client. Appendix A Describes how to install Common Components. Appendix B Contains a log from a sample installation. Appendix C Contains a list of the files that are installed on your system by ACCESSWORKS DB Integrator Gateway for PC Data Client. 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. xii 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. 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) xiii 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. 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 PC Data xiv - 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 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. _____________________________________________________ xv 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 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. xvi 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. 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] ___________________ [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 - 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. 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 ________________________________________________________________ Configuring ACCESSWORKS DB Integrator Gateway for PC Data Client Client The ACCESSWORKS DB Integrator Gateway for PC Data Client for OpenVMS enables Digital OpenVMS users to have access to data stored in data sources associated with PC Data servers. Programmers and end users can use one of many Digital or third-party tools with the gateway to have access to the data. The gateway for PC Data client works with a gateway for PC Data server and associated data sources to provide access to data. This chapter describes how the gateway for PC Data works and describes what you must do to configure the gateway for PC Data client. 1.1 Components of the Gateway for PC Data The following software products or components are needed to obtain access to the personal computer data sources: o A user interface, which can be a Digital or third-party product o Rdb/Dispatch, which is provided with ORACLE Rdb or Common Components (you must have ORACLE Rdb or Common Components installed to use the gateway for PC Data) o The gateway for PC Data client o The gateway for PC Data server o A personal computer data source o ODBC administrator o ODBC driver manager o ODBC driver for the data source ACCESSWORKS DB Integrator Gateway for PC Data Client Client 1-1 The following sections describe the functions of each of these components. Section 1.2 describes the possible configurations of these components. 1.1.1 Gateway for PC Data User Interface Users or programmers can use any of the supported Digital and third-party tools described in the DEC DB Integrator Product Family User's Guide. These tools are installed separately from the gateway for PC Data. With any user interface, users provide a set of attach specification qualifiers that determine what database is accessed, and how the database is accessed. The qualifiers are described fully in the DEC DB Integrator Product Family User's Guide. The user interface provides the means for a user to submit a request, which is passed to Rdb/Dispatch. The user interface also returns responses from Rdb/Dispatch to the user. 1.1.2 Rdb/Dispatch Interface All data requests made from user interfaces are routed through the Rdb/Dispatch interface. Rdb/Dispatch processes these requests and sends them to the DBI engine for further processing. When the DBI engine returns a response, Rdb/Dispatch sends that response back to the user interface. Rdb/Dispatch is installed as part of the ORACLE Rdb or Common Components installation. You must have ORACLE Rdb or Common Components installed to use the gateway for PC Data. 1.1.3 Gateway for PC Data Client The gateway for PC Data client includes a component called the DBI engine. The DBI engine receives the request from Rdb/Dispatch and optimizes it. The gateway then translates the request into a form that the gateway for PC Data server can understand. The gateway for PC Data client passes the request on to the appropriate gateway for PC Data server using a TCP/IP connection. 1-2 Configuring ACCESSWORKS DB Integrator Gateway for PC Data Client Client When a response is returned from the gateway for PC Data server, it is passed back through the gateway for PC Data. 1.1.4 Gateway for PC Data Server The gateway for PC Data server resides on a personal computer running Windows 3.1, Windows95 or Windows NT and manages communications and data access. 1.1.5 Personal Computer Data Source The personal computer data source is the data being accessed. For a list of data sources, see the Software Product Description. 1.1.6 ODBC Administrator The gateway for PC Data server uses the 16-bit ODBC Administrator. You may use an Administrator that is already installed on your system or you may set up the ODBC Pack 2 files that came with the gateway for PC Data server archive. Once an Administrator is installed it is used to install ODBC Data Drivers and to define data source names. 1.1.7 ODBC Driver Manager The ODBC Driver Manager is a program used by the gateway for PC Data server to load drivers. 1.1.8 ODBC Driver for the Data Source ODBC Data Drivers are programs used by the gateway for PC Data server to access a data source. Data Drivers are made available to the gateway for PC Data server by adding them into the set of drivers known to the ODBC Administrator and then defining a data source name that includes that driver. Because Data Drivers are usually tailored to a specific data source, it is common to install and maintain several Data Drivers, one for each data source. 1.2 Gateway for PC Data Configurations for Access to Target Data Sources The following sections describe the possible configura- tions for data access. In the most common configuration, personal computer data sources are accessed using the supplied ODBC driver. ACCESSWORKS DB Integrator Gateway for PC Data Client Client 1-3 1.2.1 Gateway for PC Data Network Access Configuration In network access, the user interface, Rdb/Dispatch, and the gateway for PC Data client are on one node, and the gateway for PC Data server and data source are on a different node. The gateway for PC Data client and the gateway for PC Data server communicate through a TCP /IP connection. For example, you might have the gateway running on an OpenVMS AXP system and the server and target data source on a personal computer. The following attach specification attaches to a gateway for PC Data server across the network: SQL> ATTACH 'FILENAME/TYPE=ODBC/NODE=MYPC/DATABASE=MY_DATABASE'; 1.2.2 Remote Access In remote access, the user interface and Rdb/Dispatch are located on a node remote from the system where Rdb/Dispatch and the gateway for PC Data client are installed. The user interface uses the local Rdb/Dispatch software to communicate with the remote Rdb/Dispatch software on the system where the gateway and other components are installed. For example, you might have the user working at an AXP workstation running the OSF/1 operating system, the gateway for PC Data client on an OpenVMS system, and the gateway for PC Data server and target database on a personal computer running Windows 3.1. For remote access, the user must provide the name of the remote node on which the gateway for PC Data client is running in the attach specification, and, if necessary, the user name and password for the server node. In the following example, the gateway for PC Data client is running on node QUILTS and the gateway for PC Data server is running on node MYPC: SQL> ATTACH 'FILENAME QUILTS::/TYPE=ODBC/NODE=MYPC- cont> /DATABASE=MY_DATABASE'; 1-4 Configuring ACCESSWORKS DB Integrator Gateway for PC Data Client Client 1.3 Coordination with the Personal Computer System Each site should have a gateway coordinator. This person is responsible for managing the gateway for PC Data software. The gateway coordinator must work with the database administrator (DBA) for the personal computer target data sources to ensure that gateway users have access to the data. The following sections describe the tasks the coordinator and DBA must perform. 1.3.1 Gateway Coordinator The gateway coordinator must obtain information from the personal computer DBA about the data gateway users will be accessing and how they will access it. The coordinator must provide this information to gateway users so they know which qualifiers to use in an attach specification. The gateway coordinator must tell the gateway users: o Which user interface product or products will be used with the gateway for PC Data o The name of the node on which DBI resides if users will be using network access o The name of the personal computer data source o Any required user name, password, transport, node, and database information o The names of the data source tables that users will be accessing If the target data source is case sensitive, users must be aware of it because they must enter certain attach specification qualifiers in the proper case so they will be recognized by the gateway for PC Data. Users may also need to consult ANSI quotation rules when importing tables to ensure that they use the proper case because SQL converts all names to uppercase before passing them to the gateway. ACCESSWORKS DB Integrator Gateway for PC Data Client Client 1-5 The attach specification qualifiers used to access personal computer data sources are described in the DEC DB Integrator Product Family User's Guide. The coordinator should be familiar with these qualifiers in order to provide information to gateway users. 1.3.2 Gateway for PC Data Server Administrator The DBA should provide the information listed in Section 1.3.1 to the gateway coordinator. For more information about administering the gateway for PC Data server system, see your gateway for PC Data server documentation. 1.3.3 Personal Computer ODBC Administrator The personal computer ODBC Administrator is responsible for managing drivers and data sources on the personal computer. 1.4 Setting Up the OpenVMS System Before using the gateway for PC Data, you must ensure that: o ORACLE Rdb or Common Components have been installed on the node on which the gateway for PC Data client is installed. o The gateway for PC Data client has been installed. o All post-installation procedures have been performed. o The Installation Verification Procedure (IVP) has run successfully. o The required gateway for PC Data server is running. o The required target database systems are running. The remainder of this guide describes how to: o Install the gateway for PC Data client for OpenVMS o Install Common Components o Perform the post-installation procedures o Run the IVP 1-6 Configuring ACCESSWORKS DB Integrator Gateway for PC Data Client Client 1.5 Gateway for PC Data Server System Setup Your gateway for PC Data server must be installed and properly configured. Refer to the gateway for PC Data server documentation for installation and configuration information. ACCESSWORKS DB Integrator Gateway for PC Data Client Client 1-7 2 ________________________________________________________________ Preparing for ACCESSWORKS DB Integrator Gateway for PC Data Client Installation This chapter discusses the preparations and requirements necessary for installing the gateway for PC Data client. Your bill of materials (BOM) and indented bills report (BIL) specify the number and contents of your media. Be sure to verify the contents of your kit with this information. If your kit is damaged or if you find that parts of it are missing, contact your Digital representative. The gateway for PC Data provides online release notes. Digital strongly recommends that you read the release notes before proceeding with the installation. 2.1 Prerequisite Hardware The gateway for PC Data client works with all VAX and AXP hardware. 2.2 Prerequisite and Optional Software You must have the following software installed on the same node on which you will install the gateway for PC Data Version 3.1A client. This software must be installed before you install the gateway for PC Data: o For VAX: OpenVMS Version 5.5-2 up to but not including Version 6.0 o For AXP: OpenVMS Version 6.1 o Common Components-Refer to Section 2.2.1 for instruc- tions ACCESSWORKS DB Integrator Gateway for PC Data Client Installation 2-1 You may also have DEC DB Integrator Version 3.1A installed and use it with the gateway for PC Data. You must have the following software installed on the system that will be the server system for the PC Data gateway: o Gateway for PC Data server Version 3.1A The Software Product Description (SPD) contains a complete list of prerequisite and optional software and their required version numbers. 2.2.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. 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. 2-2 Preparing for ACCESSWORKS DB Integrator Gateway for PC Data Client Installation 2.2.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. 2.2.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. ACCESSWORKS DB Integrator Gateway for PC Data Client Installation 2-3 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) 2.3 License Registration Before you install and run the gateway for PC Data client Version 3.1A on a newly licensed node or cluster, you must first register a Product Authorization Key (PAK) using the License Management Facility (LMF). The PAK may be shipped along with the kit if you ordered the license and media together; otherwise, it is shipped separately based on your license order. If you are installing the gateway for PC Data client as an update on a node or cluster already licensed for this software, you have already completed the PAK registration requirements. 2-4 Preparing for ACCESSWORKS DB Integrator Gateway for PC Data Client Installation If you are installing prerequisite or optional software along with the gateway for PC Data client, review the PAK status and install the PAKs for any prerequisite or optional software before you install the gateway for PC Data client. You must register and load your license for the gateway for PC Data before you can use the software. To register a license under OpenVMS, first log in to the system manager's account, SYSTEM. You then have a choice of two ways to perform the registration: 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 PAK information. For complete information on using LMF, see the OpenVMS License Management Utility Manual. 2.4 Installation Procedure Requirements This section and those that follow discuss various requirements for installing the gateway for PC Data client. The installation takes approximately 1 to 5 minutes. The actual time depends on the type of media, the processor type, and the system configuration. 2.4.1 Privileges and Disk Space To install the gateway for PC Data client, you must be logged in to an account that has the SETPRV privilege or at least the following privileges: o CMKRNL o WORLD o SYSPRV Note that the VMSINSTAL procedure turns off the BYPASS privilege at the start of the installation. ACCESSWORKS DB Integrator Gateway for PC Data Client Installation 2-5 Table 2-1 summarizes the storage requirements for the gateway for PC Data client during installation and after installation. Table_2-1_Disk_Space_Requirements_________________________ Blocks During Installation__________Blocks_After_Installation___________ ______________________For_AXP_systems_____________________ 15,000 14,000 __________________________________________________________ ______________________For_VAX_systems_____________________ 12,500________________11,500______________________________ 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 2.4.2 System Parameters Table 2-2 lists the minimum required system parameter values for the installation. Depending on the kinds of programs and applications running at your site, you might need higher values for some settings. Table 2-2 lists some parameters whose units are specified in pages. On OpenVMS AXP systems, the size of a page can differ on different CPUs. Read the values in Table 2-2 as 512-byte pagelets, which are not CPU-specific. 2-6 Preparing for ACCESSWORKS DB Integrator Gateway for PC Data Client Installation Table_2-2_Minimum_Required_System_Parameter_Values________ System_Parameter___________Minimum_Value__________________ _____________________For_AXP_systems______________________ GBLPAGES[1] 6000 GBLSECTIONS[1] 11 __________________________________________________________ _____________________For_VAX_systems______________________ GBLPAGES[1] 1376 GBLSECTIONS[1] 6 [1]The_values_listed_for_these_system_parameters_represent the number of available global pages and global sections required for the installation, not the total number you need to run your system and other software. __________________________________________________________ The following sections show you how to: o Calculate values for the GBLPAGES and GBLSECTIONS system parameters o Change parameter values with the OpenVMS AUTOGEN utility 2.4.2.1 Calculating the Values for GBLPAGES and GBLSECTIONS To install and run the gateway for PC Data client, you must have sufficient available global pages or pagelets and global sections. You must first find out how many available global pages or pagelets and sections you have on your system. Then, use AUTOGEN if you need to increase the GBLPAGES and GBLSECTIONS system parameters. To calculate how many unused global pagelets and global sections your system has, use the WRITE command with the F$GETSYI lexical function to find the number of available global pages or pagelets and global sections. The following example shows how to get this information at your terminal (the default for SYS$OUTPUT): ACCESSWORKS DB Integrator Gateway for PC Data Client Installation 2-7 $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES") 15848 $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS") 24 If the values displayed by the system are greater than the values in Table 2-2, you do not need to increase the values for these parameters. If the values of available global pages or pagelets or global sections are less than the values in Table 2-2, you must increase the system parameter setting. Section 2.4.2.2 describes the procedures for increasing these values using AUTOGEN. 2.4.2.2 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 Use an editor to access the file. To change a parameter value listed in this file, delete the current value associated with that parameter, and enter the new value. To add a new parameter, add a line to the file that includes both the name of the parameter and its value, for example: PROCSECTCNT = 90 To modify incremental parameters such as GBLPAGES and GBLSECTIONS, use the prefix ADD_. The following example increases the global page setting by 2000: ADD_GBLPAGES = 2000 After you make all your changes, exit from the editor and execute the AUTOGEN utility to recalculate your system parameters. Enter the following command at the DCL prompt: $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT 2-8 Preparing for ACCESSWORKS DB Integrator Gateway for PC Data Client Installation When you specify REBOOT, the AUTOGEN utility performs an automatic system shutdown and then reboots (restarts) the system. Any users logged on to the system are immediately disconnected during the shutdown. The automatic reboot puts the new parameter values into effect. The AUTOGEN utility automatically adjusts some of the SYSGEN parameters based on the consumption of resources since the last reboot. If you do not want to take advantage of this automatic adjustment, include the NOFEEDBACK qualifier on the AUTOGEN command line. For more information about using AUTOGEN, see the OpenVMS System Management documentation. 2.4.3 VMSINSTAL Requirements When you invoke the VMSINSTAL procedure, it checks the following: o If you are logged in to a privileged account o If you have adequate quotas for installation o If DECnet is running o If any users are logged in to the system If VMSINSTAL detects any problems during the installation, it notifies you and asks if you want to continue the installation. In some instances, you can enter YES to continue. To stop the installation process and correct the situation, enter NO or press the Return key. Then, correct the problem and restart the installation. 2.4.4 System Disk Backup At the beginning of the installation, VMSINSTAL asks if you have backed up your system disk. Digital recommends that you back up your system disk before installing any software. Use the backup procedures that are established at your site. For details on backing up a system disk, see the OpenVMS System Management documentation. ACCESSWORKS DB Integrator Gateway for PC Data Client Installation 2-9 3 ________________________________________________________________ Installing ACCESSWORKS DB Integrator Gateway for PC Data Client This chapter explains how to install the gateway for PC Data client. Section 3.1 contains a step-by-step description of the installation procedure. 3.1 Installation Procedure The gateway for PC Data client installation procedure consists of a series of questions and informational messages. See Appendix B for a sample installation. To abort the installation procedure at any time, press the Ctrl/Y keys. When you press Ctrl/Y, the installation procedure deletes all files it has created up to that point and exits. You can then start the installation again. Before invoking VMSINSTAL, mount the media (for VAX installations) or place the CD-ROM media into the CD-ROM drive (for Alpha installations). When the system prompts you with a question during the installation, the default answer, if there is one, is listed in brackets ([]). 3.1.1 Invoking VMSINSTAL Before invoking VMSINSTAL, log in to a privileged account and set your default device and directory to SYS$UPDATE. The VMSINSTAL procedure is located in SYS$UPDATE. Invoke VMSINSTAL using the following command: @VMSINSTAL saveset-name device-name OPTIONS N If you do not specify the parameters to the VMSINSTAL com- mand, you are prompted for them during the installation. The parameters to the VMSINSTAL command are as follows. Installing ACCESSWORKS DB Integrator Gateway for PC Data Client 3-1 saveset-name The installation name for the component. For the gateway for PC Data client, use the following installation name: LRED031 device-name The name of the device on which you plan to mount the media. o If the device is a magnetic tape drive, you need to specify only the device name, such as MTA0:. o If the device is a disk drive, such as a CD-ROM reader, you also need to specify a directory. For CD-ROM distribution, the directory name is the same as the saveset name, for example: DKA400:[LRED031.KIT] For Alpha installations, to determine the directory location of the gateway for PC Data client save set on the CD-ROM, see the OpenVMS AXP Layered Products Compact Disc User's Guide booklet that accompanies the CD-ROM distribution kit. OPTIONS N An optional parameter that indicates you want to see the question on release notes. If you do not include the OPTIONS N parameter, VMSINSTAL does not ask you about the release notes. You should review the release notes before proceeding with the installation in case they contain additional information about the installation. If you are restarting the installation and have already reviewed the release notes, you do not need to specify OPTIONS N. Whether or not you specify OPTIONS N, the VMSINSTAL procedure copies the release notes to the SYS$HELP directory. There are several other options you can select when you invoke VMSINSTAL. If you specify more than one option, separate the options with commas (OPTIONS A,N). 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 3-2 Installing ACCESSWORKS DB Integrator Gateway for PC Data Client file) to save time during a reinstallation (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 installation. o Alternate root option (R): Lets you install the product to a system root other than that of the operating system. This option makes it possible to test a new product without disturbing the operating system. See the OpenVMS operating system documentation for detailed information on these options. The following example invokes VMSINSTAL to install the gateway for PC Data client from tape drive MTA0: and shows the system response. This example uses the OPTIONS N release notes parameter. The example is a sample installation on a VAX system. An installation on an Alpha system would be similar. $ @SYS$UPDATE:VMSINSTAL LRED031 MTA0: OPTIONS N OpenVMS VAX Software Product Installation Procedure V1.5 It is 24-AUG-1995 at 14:14. Enter a question mark (?) at any time for help. If you do not supply either the product name or the device name, VMSINSTAL prompts you for this information later in the installation procedure. The VMSINSTAL procedure does not prompt you for any options, so be sure to include OPTIONS N on the VMSINSTAL command line to access the release notes during the installation. Installing ACCESSWORKS DB Integrator Gateway for PC Data Client 3-3 3.1.2 Steps of the Installation Procedure The following steps describe the installation procedure: 1. Note processes that are still running. %VMSINSTAL-W-ACTIVE, The following processes are still active: SQLSRV$SERVER _RTA3: * Do you want to continue anyway [NO]? YES The installation procedure notes which processes are still active and asks if you want to continue. 2. Confirm system backup. * Are you satisfied with the backup of your system disk [YES]? VMSINSTAL asks if you are satisfied with your system backup. You should always back up your system disk before performing an installation. If you are satisfied with the backup of your system disk, press the Return key. Otherwise, enter NO to discontinue the installation. After you back up your system disk, you can restart the installation. 3. Mount the media. Please mount the first volume of the set on MTA0:. * Are you ready? YES %MOUNT-I-MOUNTED, DEC DB Integrator Gateway for PC Data MOUNTED ON _$$MTA0: (NODE 1) The following products will be processed: LRED V3.1 Beginning installation of LRED V3.1 at 10:36 %VMSINSTAL-I-RESTORE, Restoring product save set A... You should now mount the first media volume on the device you specified when you invoked the VMSINSTAL procedure. The device name appears in the line preceding the question. VMSINSTAL then asks you if you are ready to continue with the installation. 3-4 Installing ACCESSWORKS DB Integrator Gateway for PC Data Client If you respond YES to indicate that you are ready, VMSINSTAL displays a message that the media containing the gateway for PC Data client 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 the Ctrl/Y keys. 4. Select a release notes option. If you specified OPTIONS N when you started the installation, VMSINSTAL asks a question on release notes. You have four options for handling the release notes. You see the following display: Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: If you select option 1, VMSINSTAL displays the release notes immediately on the terminal. You can terminate the display at any time by pressing Ctrl/C. If you select option 2, VMSINSTAL prompts you for the name of the print queue: * Queue name [SYS$PRINT]: You can press the Return key to send the file to the default output print device or you can enter another queue name. If you select option 3, VMSINSTAL displays the release notes immediately on the terminal and then prompts you for a queue name for the printed version. Installing ACCESSWORKS DB Integrator Gateway for PC Data Client 3-5 Select option 4 if you have already reviewed the release notes and are restarting the installation. Next, VMSINSTAL displays the following question: * Do you want to continue the installation [N]?: YES %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. To continue the installation, enter YES. Otherwise, press the Return key. In either case, the release notes are copied to the following files in the SYS$HELP directory: SYS$HELP:LRED031.RELEASE_NOTES SYS$HELP:LRED031_RELEASE_NOTES.PS ________________________Note ________________________ The name of the release notes file installed by VMSINSTAL consists of the current product facility code (LRED) and version number (031). _____________________________________________________ 5. Note the copyright notice. ************************************************************** The installation procedure for DEC DB Integrator Gateway for PC Data V3.1-1 for OpenVMS VAX © Digital Equipment Corporation 1995. All rights reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. ************************************************************** 3-6 Installing ACCESSWORKS DB Integrator Gateway for PC Data Client 6. Select the installation type. Select the desired type of installation from the list below: 1 - Full Install Client files installed and Server files made available for distribution 2 - Client Only Client file installed. Server files must be available elsewhere on the network. 3 - Server Files Server files made available for distribution. Client files not installed. ******************************************************************* * Enter selection [1]: 1 Select option '1' in order to complete a full gateway for PC Data installation. The gateway for PC Data server software and ODBC pack 2 files are distributed as a single archive file that must be copied to personal computer nodes, and then expanded. This software is not distributed on floppy diskettes, so you must install the server files on at least one node in your network and use it as a distribution point. When you answer this question remember that you do not need to install the server archive on every client node, but you must install it on at least one node so that the personal computer nodes can copy it. Refer to Section 4.1 for more information on distributing the gateway for PC Data server archive. 7. Print the installation guide. * Would you like to print the LRED installation guide [NO]? If you want to print the installation guide, answer YES to this question. If you answer YES and you want to use a print queue other than SYS$PRINT for printing the installation guide, enter the queue name after the following prompt: * Enter the printer queue name [SYS$PRINT]: print_queue * Do you want to continue the installation? [YES]: Y To continue the installation, enter YES. Otherwise, press the Return key. In either case, the installation Installing ACCESSWORKS DB Integrator Gateway for PC Data Client 3-7 guide is copied to the following files in the SYS$HELP directory: SYS$HELP:LRED031.INSTALL_GUIDE SYS$HELP:LRED031_INSTALL_GUIDE.PS 8. Respond to license registration queries. Product: DB-GATEWAY-PCDATA Producer: DEC Version: 3.1A Release Date: 13-SEP-1995 * Does this product have an authorization key registered and loaded? Y The installation procedure displays license information about your product and then asks if you have registered and loaded your Product Authorization Key (PAK). If you have not registered and loaded your PAK, you must answer NO to this question. You have to register and load your PAK to successfully complete the installation. If you have not done so, you should stop the installation, register and load your PAK, and then restart the installation. 9. Purge files. * Do you want to purge files replaced by this installation [YES]? You have the option to purge files from previous installations of the gateway for PC Data client that are superseded by this installation. Purging is recommended; however, if you need to keep files from a previous installation, enter NO in response to the question. 10.Read messages. At this point, the installation procedure displays a number of messages that report on the progress of the installation. One of the messages indicates that because the IVP is interactive, it is not run during installation. However, you can run the IVP after installation by executing the file @SYS$TEST:LRED$IVP. 3-8 Installing ACCESSWORKS DB Integrator Gateway for PC Data Client There are no further questions in the installation procedure. If the installation procedure has been successful up to this point, VMSINSTAL moves the new or modified files to their target directories, updates help files, and updates DCL tables, if necessary. If you chose to have files purged, that work is done now. The following messages are displayed: ************************************************************** There are no more questions. The installation takes approximately 1 to 10 minutes depending on the processor type. Because the Installation Verification Procedure is interactive, it will not be run as part of the installation. You may run the IVP separately any time you wish. To execute it, type: $ @SYS$TEST:LRED$IVP Remember to register and load your authorization key befor e attempting to execute the IVP. ************************************************************** ************************************************************** Beginning installation of DEC DB Integrator Gateway for PC Data V3.1-1 ************************************************************** %VMSINSTAL-I-RESTORE, Restoring product save set B ... ************************************************************** LRED$STARTUP.COM has been placed in SYS$STARTUP. The following line should be place in your system startup file. $ @SYS$STARTUP:LRED$STARTUP.COM ************************************************************** ************************************************************** LRED$SHUTDOWN.COM has been placed in SYS$MANAGER. The following line should be place in your system shutdown file. $ @SYS$MANAGER:LRED$SHUTDOWN.COM ************************************************************** Installing ACCESSWORKS DB Integrator Gateway for PC Data Client 3-9 The server file, PCDATASERVER31_WIN16.EXE, has been placed in SYS$LIBRARY. ************************************************************** Finishing installation of DEC DB Integrator Gateway for PC Data V3.1-1 ************************************************************** %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Installation of LREDVVA V3.1 completed at 14:17 VMSINSTAL procedure done at 14:17 The previous messages indicate that the entire installation procedure is complete. You can now log out of the privileged account: $ LOGOUT SYSTEM logged out at 11-MAY-1995 The VMSINSTAL procedure deletes or changes entries in the process symbol tables during the installation. If you want to continue using the system manager's account and you need to restore these symbols, you should log out and log in again. 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 2. 3-10 Installing ACCESSWORKS DB Integrator Gateway for PC Data Client 4 ________________________________________________________________ After Installing ACCESSWORKS DB Integrator Gateway for PC Data Client The following tasks take place after installing the gateway for PC Data: o Distributing the gateway for PC Data server to personal computer nodes o Running the Installation Verification Procedure (IVP) o Editing the system startup and shutdown files o Ensuring users have sufficient privileges o Reporting problems 4.1 Distributing the Gateway for PC Data Server The gateway for PC Data server can optionally be installed on any OpenVMS or UNIX node for the purpose of acting as a distribution center for personal computer nodes. The server software itself is a single self-extracting archive that must be copied to each personal computer node which will be used as a server. The location of the archive depends on the operating system of the client software. If a server install option was selected during the installation of the client: o On OpenVMS systems the archive is placed at sys$library:pcdataserver31_win16.exe after the server has been successfully installed. o On Digital UNIX systems the archive is placed at /usr/opt/PCGSRV311/shlib/pcdataserver31_win16.exe by setld after the client has been successfully installed. Installing ACCESSWORKS DB Integrator Gateway for PC Data Client 4-1 To distribute the server copy the pcdataserver31_win16.exe file from the directory on the client node to the personal computer by whatever means allows you to copy in image mode. Rename to a DOS format 8.3 name, such as dbipcgwy.exe. One such method would be to use FTP from the personal computer to move the file. The following example shows sample FTP commands: FTP> open (vms or UNIX node) USERNAME: PASSWORD: FTP> binary FTP> cd (VMS or UNIX directory) FTP> get pcdataserver31_win16.exe C:\pcdata\dbipcgwy.exe FTP> close FTP> bye Or, you can distribute the file from the client system to the personal computer with FTP commands similar to the following example: FTP> open USERNAME: PASSWORD: FTP> binary FTP> lcd (VMS or UNIX directory) FTP> put pcdataserver31_win16.exe c:\pcdata\dbipcgwy.exe FTP> close FTP> bye Once the self-extracting archive is copied to a personal computer hard disk, you must give the administrator of the personal computer the following information necessary to expand the archive: The administrator must extract the archive by running the just copied file from the DOS prompt. A sample command to do this is: C:\PCDATA>dbipcgwy The archive then expands into two subdirectories. The server subdirectory contains all the files necessary to set up the Gateway for PC Data server. The ODBC subdirectory contains all the optional files necessary to set up an ODBC environment on the personal computer. 4-2 After Installing ACCESSWORKS DB Integrator Gateway for PC Data Client The personal computer administrator must follow the steps in the readme file found in the server subdirectory in order to install the gateway for PC Data server. Acknowledgments The dbipcgwy.exe self-extracting executable file was built using LHA Version 2.13, Copyright [TM] Haruyasu Yoshizaki, 1988-91. 4.2 Running the Installation Verification Procedure The Installation Verification Procedure (IVP) connects to a gateway for PC Data server based on information you supply and executes an SQL SHOW TABLES statement. Because the IVP is interactive, it is not run during installation. You can run the IVP separately to ensure the integrity of installed files and to ensure that the gateway for PC Data can connect to gateway for PC Data target data sources. The IVP takes approximately 1 to 2 minutes to run. The actual time depends on the processor type and the server type and location. You must provide the following information in the form of an attach specification after starting the IVP: o The data source database type of ODBC for all versions of Common Components. o The name of the personal computer where the server is running. o The name of the personal computer data source, for example DEMO1. o If necessary, the server password needed to attach to the server node. o If necessary, the user name and password needed to access the gateway for PC Data target database. o The name of the gateway for PC Data table the IVP will access. Installing ACCESSWORKS DB Integrator Gateway for PC Data Client 4-3 If you do not provide a name, the default is all tables. Use the TABLES qualifier in the attach specification to specify the name of the table. 4.2.1 Invoking the IVP To invoke the IVP, enter the following command: $ @SYS$TEST:LRED$IVP.COM ________________________Note ________________________ When the IVP is run, the SQL and Rdb Dispatch environments are set to version 6.1. To reset both environments to version 6.0, enter the following command: $ @SYS$LIBRARY:SQL$SETVER 6.0 _____________________________________________________ 4.2.2 Sample IVP Log The following is a sample IVP log from a VAX system. Running the IVP on an AXP system would produce a similar log. $ @sys$test:lred$ivp ***************************************************************** Installation Verification Procedure (IVP) for DEC DB Integrator Gateway for PC Data V3.2-00 for OpenVMS VAX Copyright Digital Equipment Corporation 1993,1994,1995. All rights reserved. This IVP verifies that all the gateway images are in place and a simple query can be executed. ***************************************************************** Enter a SQL attach string terminated by a semi-colon. Example: /TYPE=ODBC/DATABASE=PERSONNEL/NODE=NODE1/DB_USER=SMITH/DB_PASSWORD=SECRET; attach string: /type=odbc/node=durace/database=pc_demo; 4-4 After Installing ACCESSWORKS DB Integrator Gateway for PC Data Client The current string is: /type=odbc/node=durace/database=pc_demo Are you satisfied with that? (Y/N): y Current PROCESS SQL environment is version V6.0-1 (MULTIVERSION) Current PROCESS Rdb/Dispatch environment is version V6.0-2 (MULTIVERSION) Current SYSTEM SQL environment is version V6.1-0 (MULTIVERSION) Current SYSTEM Rdb/Dispatch environment is version V6.1-0 (MULTIVERSION) Current version of SQL is: DEC SQL V6.0-1 Underlying versions are: Database with filename sql$database DEC DBI Gateway for PC Data X3.1 DBI Gateway for PC Data Server V3.1-0 Rdb/Dispatch V6.0-2 (OpenVMS VAX) User tables in database with filename sql$database ALL_DTPS ALL_DTPS_2 CANDIDATES COLLEGES CURRENT_INFO CURRENT_JOB CURRENT_SALARY DATE_DTPS DATE_DTPS_2 DEGREES DEPARTMENTS EMPLOYEES J JOBS JOB_HISTORY MSYSIMEXCOLUMNS MSYSIMEXSPECS MSYSMACROS P RESUMES S SALARY_HISTORY SCALED_DTPS SHORT_TEXT SPJ WORK_STATUS IVP completed successfully. Installing ACCESSWORKS DB Integrator Gateway for PC Data Client 4-5 4.3 Editing the System Startup Files You may want to edit the system startup files to provide for automatic startup of the gateway for PC Data client when your system is restarted. The installation procedure adds the following command file to the SYS$STARTUP directory: SYS$STARTUP:LRED$STARTUP.COM This command file starts the gateway for PC Data client. You must add this command to the system startup file, SYS$MANAGER:SYSTARTUP_V5.COM. The command file installs the gateway images as shared images. This reduces system overhead and memory requirements when running the gateway for PC Data client. You must position this new command line after the line that invokes the network startup command procedure. The following example shows the network startup command line followed by the gateway for PC Data startup command line: $ @SYS$MANAGER:STARTNET.COM . . . $ @SYS$STARTUP:LRED$STARTUP.COM 4.4 Editing the System Shutdown File The installation procedure adds the following command file to the SYS$MANAGER directory: LRED$SHUTDOWN.COM. You can use this command file to remove the images installed by the LRED$STARTUP.COM procedure. You should add the following line to the system shutdown file, SYS$MANAGER:SYSHUTDOWN.COM: $ @SYS$MANAGER:LRED$SHUTDOWN.COM 4-6 After Installing ACCESSWORKS DB Integrator Gateway for PC Data Client 4.5 User Account Privileges Required To use the gateway for PC Data, each account must have at least the TMPMBX and NETMBX privileges. Use the OpenVMS Authorize utility to determine whether or not users have the privileges they require. 4.6 Determining and Reporting Problems If you encounter a problem while using the gateway for PC Data, report it to Digital. Depending on the nature of the problem and the type of support you have, you can take one of the following actions: o Call Digital if your software contract or warranty agreement entitles you to telephone support. o Submit a Software Performance Report (SPR). o Fill out and submit a Send Us Your Comments form if the problem has to do with the gateway for PC Data documentation. There is a form at the front of each manual. Include the section and page number. Review the Software Product Description (SPD) and Warranty Addendum for an explanation of warranty. If you encounter a problem during the warranty period, report the problem as previously indicated or follow alternate instructions provided by Digital for reporting SPD nonconformance problems. Installing ACCESSWORKS DB Integrator Gateway for PC Data Client 4-7 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 PC Data o DEC DB Integrator Gateway for SequeLink Prerequisite Installation of Common Components A-15 o DEC DB Integrator Gateway for SYBASE 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 A-16 Prerequisite Installation of Common Components 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.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 Installation This appendix contains the log of an installation of ACCESSWORKS DB Integrator Gateway for PC Data Client on an OpenVMS VAX system and a log of the running of the Installation Verification Procedure (IVP). Installation on an AXP system would produce a similar log. The sample installation assumes that DECnet has been shut down and that no users are logged on to your system. B.1 Sample Installation OpenVMS VAX Software Product Installation Procedure V6.1 It is 24-AUG-1995 at 14:14. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? The following products will be processed: LREDVVA V3.1 Beginning installation of LREDVVA V3.1 at 14:14 %VMSINSTAL-I-RESTORE, Restoring product save set A ... Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above Sample Installation B-1 * Select option [2]: 4 * Do you want to continue the installation [NO]? y %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. ************************************************************** The installation procedure for DEC DB Integrator Gateway for PC Data V3.1-1 for OpenVMS VAX (C) Digital Equipment Corporation 1995. All rights reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. ************************************************************** ************************************************************** Select the desired type of installation from the list below: 1 - Full Install Client files installed and Server files made available for distribution 2 - Client Only Client file installed. Server files must be available elsewhere on the network. 3 - Server Files Server files made available for distribution. Client files not installed. ************************************************************** * Enter selection [1]: 1 * Do you want to continue the installation [YES]? * Would you like to print the LRED installation guide [NO]? * Do you want to continue the installation [YES]? Product: DB-GATEWAY-PCDATA Producer: DEC Version: 3.1 Release Date: 01-May-1995 B-2 Sample Installation * Does this product have an authorization key registered and loaded? no %LREDVVA-W-NO_LICENSE, No license is available for the product. * Do you want to continue the installation [NO]? y * Do you want to purge files replaced by this installation [YES]? ************************************************************** There are no more questions. The installation takes approximately 1 to 10 minutes depending on the processor type. Because the Installation Verification Procedure is interactive, it will not be run as part of the installation. You may run the IVP separately any time you wish. To execute it, type: $ @SYS$TEST:LRED$IVP Remember to register and load your authorization key before attempting to execute the IVP. ************************************************************** ************************************************************** Beginning installation of DEC DB Integrator Gateway for PC Data V3.1-1 ************************************************************** %VMSINSTAL-I-RESTORE, Restoring product save set B ... ************************************************************** LRED$STARTUP.COM has been placed in SYS$STARTUP. The following line should be placed in your system startup file. $ @SYS$STARTUP:LRED$STARTUP.COM ************************************************************** ************************************************************** LRED$SHUTDOWN.COM has been placed in SYS$MANAGER. The following line should be placed in your system shutdown file. $ @SYS$MANAGER:LRED$SHUTDOWN.COM ************************************************************** %LIBRAR-W-NOHLPTXT, no level 1 help text found in MOWMOW$DKA300:[SYS0.SYSUPD.LRE DVVA031]LDRVHELP.HLP;1 Sample Installation B-3 ************************************************************** The server file, PCDATASERVER31_WIN16.EXE, has been placed in SYS$LIBRARY. ************************************************************** ************************************************************** Finishing installation of DEC DB Integrator Gateway for PC Data V3.1-1 ************************************************************** %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Installation of LREDVVA V3.1 completed at 14:17 VMSINSTAL procedure done at 14:17 B.2 Sample Installation Verification Procedure $ @sys$test:lred$ivp ***************************************************************** Installation Verification Procedure (IVP) for DEC DB Integrator Gateway for PC Data V3.2-00 for OpenVMS VAX Copyright Digital Equipment Corporation 1993,1994,1995. All rights reserved. This IVP verifies that all the gateway images are in place and a simple query can be executed. ***************************************************************** Enter a SQL attach string terminated by a semi-colon. Example: /TYPE=ODBC/DATABASE=PERSONNEL/NODE=NODE1/DB_USER=SMITH/DB_PASSWORD=SECRET; attach string: /type=odbc/node=durace/database=pc_demo; The current string is: /type=odbc/node=durace/database=pc_demo Are you satisfied with that? (Y/N): y B-4 Sample Installation Current PROCESS SQL environment is version V6.0-1 (MULTIVERSION) Current PROCESS Rdb/Dispatch environment is version V6.0-2 (MULTIVERSION) Current SYSTEM SQL environment is version V6.1-0 (MULTIVERSION) Current SYSTEM Rdb/Dispatch environment is version V6.1-0 (MULTIVERSION) Current version of SQL is: DEC SQL V6.0-1 Underlying versions are: Database with filename sql$database DEC DBI Gateway for PC Data X3.1 DBI Gateway for PC Data Server V3.1-0 Rdb/Dispatch V6.0-2 (OpenVMS VAX) User tables in database with filename sql$database ALL_DTPS ALL_DTPS_2 CANDIDATES COLLEGES CURRENT_INFO CURRENT_JOB CURRENT_SALARY DATE_DTPS DATE_DTPS_2 DEGREES DEPARTMENTS EMPLOYEES J JOBS JOB_HISTORY MSYSIMEXCOLUMNS MSYSIMEXSPECS MSYSMACROS P RESUMES S SALARY_HISTORY SCALED_DTPS SHORT_TEXT SPJ WORK_STATUS IVP completed successfully. $ Sample Installation B-5 C ________________________________________________________________ Files Installed on Your System DEC DB Integrator Gateway for PC Data installs the following files on your system: o SYS$HELP:DBI_MSG.DOC o SYS$HELP:LDRV_MSG.DOC o SYS$HELP:LRED031.INSTALL_GUIDE o SYS$HELP:LRED031_INSTALL_GUIDE.PS o SYS$HELP:LRED031.RELEASE_NOTES o SYS$HELP:LRED031_RELEASE_NOTES.PS o SYS$LIBRARY:LDRV$ODBC_SHR.EXE o SYS$MANAGER:DBI$SHUTDOWN_COMMON.COM o SYS$MANAGER:LRED$SHUTDOWN.COM o SYS$MESSAGE:DBI_MSG.EXE o SYS$MESSAGE:LDRV_MSG.EXE o SYS$SHARE:DBI$SHR.EXE o SYS$SHARE:LDRV$PCDATA_SHR.EXE o SYS$STARTUP:DBI$STARTUP_COMMON.COM o SYS$STARTUP:LRED$STARTUP.COM o SYS$TEST:LRED$IVP.COM Files Installed on Your System C-1 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