VIDA*_for_DB2**______________________________________ VIDA* Client for DB2** Installation Guide AA-MH84A-TE June 1989 This book describes how to install VIDA Client for DB2 on a VMS system and run the Installation Verification Procedure (IVP). OPERATING SYSTEM: VMS SOFTWARE VERSION: VIDA for DB2 Version 1.0 * VIDA is a trademark of Digital Equipment Corporation. ** DB2 is a trademark of International Business Machines Corporation. digital equipment corporation maynard, massachusetts The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. © Digital Equipment Corporation 1989. All Rights Reserved. Printed in U.S.A. The Reader's Comments forms at the end of this document request your critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: ACMS MASSBUS UNIBUS ALL-IN-1 PDP VAX DATATRIEVE P/OS VAX CDD/Plus DEC Professional VAX FMS DEC/CMS Rainbow VAXstation DEC/MMS RALLY VIDA DECforms Rdb/ELN VMS DECintact Rdb/VMS VT DECnet ReGIS Work Processor DECmate RSTS DECUS RSX DECwindows RT DECwriter TDMS DIBOL ULTRIX DIGITAL The following are third-party trademarks: IBM[R] is a registered trademark of International Business Machines Corporation. DB2 is a trademark of International Business Machines Corporation. This document was prepared using VAX DOCUMENT, Version 1.2 ________________________________________________________________ Contents Preface.................................................. vii 1 Preparing to Install VIDA Client for DB2 1.1 Required Operating System Components............ 1-2 1.2 Prerequisite Software........................... 1-2 1.2.1 Software Requirements for VIDA Client for DB2 Installation................................. 1-2 1.2.2 Software Requirements for VIDA Client for DB2 Use.......................................... 1-2 1.3 Prerequisite Hardware........................... 1-3 1.4 VMS License Management Facility................. 1-3 1.5 VAXcluster Considerations....................... 1-4 1.6 Installation Procedure Requirements............. 1-5 1.6.1 Time ......................................... 1-5 1.6.2 Privileges ................................... 1-6 1.6.3 Disk Space ................................... 1-6 iii 1.6.4 System Parameters ............................ 1-7 1.6.4.1 Checking System Parameter Values........... 1-8 1.6.4.2 Calculating the Values for GBLPAGES and GBLSECTIONS................................ 1-8 1.6.4.3 Changing System Parameter Values with AUTOGEN.................................... 1-9 1.6.4.4 Setting the CLISYMTBL Dynamic System Parameter.................................. 1-10 1.6.5 Process Account Quotas ....................... 1-10 1.6.6 VMSINSTAL Requirements ....................... 1-12 1.6.7 Backing Up Your System Disk .................. 1-12 1.6.8 VIDA Client for DB2 Requirements ............. 1-13 2 Installing VIDA Client for DB2 2.1 General Information............................. 2-1 2.1.1 Accessing the Online Release Notes ........... 2-1 2.1.2 Determining the Files Added to the System .... 2-2 2.1.3 Running the Installation Verification Procedure (IVP).............................. 2-2 2.1.4 Aborting the Installation .................... 2-3 2.2 The Installation Procedure...................... 2-3 2.2.1 Invoking VMSINSTAL ........................... 2-3 2.2.2 Answering Installation Questions ............. 2-4 2.2.3 Understanding Informational Messages ......... 2-10 2.2.4 Running the Installation Verification Procedure.................................... 2-12 2.2.5 Completing the Installation Procedure ........ 2-13 2.3 Error Recovery.................................. 2-13 iv 3 After Installing VIDA Client for DB2 3.1 Modifying System Parameters..................... 3-1 3.2 Setting User Account Requirements............... 3-1 3.2.1 Privileges ................................... 3-2 3.2.2 User Account Quotas .......................... 3-2 3.3 Installing Licenses on All Nodes in a Cluster... 3-3 3.4 Executing RDBSERVER_NCP.COM in VAXclusters...... 3-3 3.5 Meeting ALL-IN-1 Requirements................... 3-4 3.6 Ensuring VIDA Client for DB2 Works with Data Distributor..................................... 3-4 3.7 Installing VIDA Client for DB2 as a Shared Image........................................... 3-5 3.8 Testing the VIDA Client for DB2 Installation and the Link to IBM................................. 3-6 3.9 Determining and Reporting Problems.............. 3-7 4 Running the Live Installation Verification Procedure 4.1 General Information............................. 4-1 4.1.1 Using the Live IVP ........................... 4-1 4.1.2 Accessing Online Help Files .................. 4-1 4.1.3 Aborting the IVP ............................. 4-2 4.2 Required Components for Running the Live IVP.... 4-2 4.2.1 Prerequisite Hardware ........................ 4-2 4.2.2 Prerequisite Software ........................ 4-2 4.2.3 User Account Requirements .................... 4-2 4.3 The Live IVP Procedure.......................... 4-3 4.3.1 Invoking the Live IVP ........................ 4-3 4.3.2 Reading the Informational Messages ........... 4-4 4.3.3 Answering the Live IVP Questions ............. 4-5 4.3.4 Completing the Live IVP ...................... 4-7 4.4 Error Recovery.................................. 4-8 v A Sample Installation B Files Installed on Your System B.1 Files Transferred to SYS$SYSTEM................. B-1 B.2 Files Transferred to SYS$HELP................... B-1 B.3 Files Transferred to SYS$SHARE.................. B-2 B.4 Files Transferred to SYS$MESSAGE................ B-4 B.5 Files Transferred to SYS$COMMON:[SYSTEST]....... B-4 B.6 Files Transferred to SYS$MANAGER................ B-5 B.7 File Transferred to SYS$COMMON.................. B-5 C Sample Live Installation Verification Procedure Tables 1-1 Disk Space Requirements......................... 1-6 1-2 Required System Parameter Values................ 1-7 1-3 Process Account Quotas for the Installing Account......................................... 1-10 vi ________________________________________________________________ Preface VIDA for DB2 is a software facility that lets VMS users retrieve data from IBM Database 2 (DB2) data tables on an IBM system. VIDA for DB2 is composed of two software products: VIDA Client for DB2 and VIDA Server for DB2. These two component products are installed on two different hardware platforms. VIDA Client for DB2 resides on a Digital VAX computer system and uses SNA gateway software to communicate with VIDA Server for DB2 which resides on an IBM mainframe. Purpose of This Manual This manual tells you how to install VIDA Client for DB2 Version 1.0 and is the only manual you need to install this product. vii Intended Audience Read this manual if you are responsible for: _ Planning the installation of VIDA Client for DB2 on your Digital network _ Preparing the system on which VIDA Client for DB2 will be installed _ Installing VIDA Client for DB2 Operating System Information Your VAX system must be running Version 5.0 or higher of the VMS operating system before you can use VIDA Client for DB2 Version 1.0. Other Software Requirements VIDA Client for DB2 Version 1.0 must have access to the following software to complete data retrieval operations: _ VIDA Server for DB2 Version 1.0 _ DECnet/SNA VMS APPC/LU 6.2 Programming Interface Version 2.1 _ Gateway Products: DECnet/SNA Gateway or VMS/SNA _ Digital Interface product such as VAX SQL or VAX DATATRIEVE _ IBM applications and database software: ACF/VTAM, CICS/OS/VS Version 1 Release 7, and DB2 Version 1 Release 3 viii Structure This manual contains four chapters and three appendixes: Chapter 1 Explains how to plan the VIDA Client for DB2 installation and prepare your system. Chapter 2 Explains how to install the VIDA Client for DB2 software. Chapter 3 Discusses what to do after installing VIDA Client for DB2. Chapter 4 Explains how to run the Live Installation Verification Procedure. Appendix A Provides a sample VIDA Client for DB2 installation procedure. Appendix B Lists the files transferred from the distribution kit to your system. Appendix C Provides a sample Live Installation Verification Procedure. Related Documents You can find additional information about VIDA for DB2 and VIDA Client for DB2 in the following manuals: _ VIDA Client for DB2 Handbook Describes how to use VIDA Client for DB2 to access IBM DB2 data tables. The handbook also contains information about different VAX products that you can use as interfaces to the IBM data. _ VIDA Client for DB2 Release Notes ix Discusses restrictions, problems, and workarounds for VIDA Client for DB2 Version 1.0. 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 a line of input. The special symbols used in this book are: _____________________________________________________________ Symbol_____________Meaning___________________________________ $ The dollar sign is used to indicate the DCL prompt. This prompt might be different on your system. COLOR Color in examples shows user input. Vertical ellipsis in an example means that . information not directly related to the . example has been omitted. ____.________________________________________________________ References to Products The VIDA Client for DB2 documentation to which this book belongs often refers to other Digital products by their abbreviated names: _ VAX CDD/Plus software is referred to as CDD/Plus. _ VAX DATATRIEVE software is referred to as DATATRIEVE. _ VAX Rdb/VMS software is referred to as Rdb/VMS. _ VAX SQL software is referred to as SQL. x 1 ________________________________________________________________ Preparing to Install VIDA Client for DB2 This chapter discusses the preparations and requirements necessary for installing VIDA Client for DB2. VIDA for DB2 provides access to an IBM relational database product, Database 2 (DB2), from a VMS based environment. One component of VIDA for DB2 is VIDA Client for DB2, client software running on the VMS operating systems on VAX hardware. VIDA Client for DB2 communicates with the server product, VIDA Server for DB2, which is running on IBM hardware. VIDA Client for DB2 uses Digital supported communications products, such as DECnet/SNA Gateway, VMS/SNA, and DECnet/SNA VMS APPC/LU6.2 Programming Interface for the VAX to IBM communications link. 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. VIDA Client for DB2 provides online release notes. Digital strongly recommends that you read the release notes before proceeding with the installation. For information on accessing online release notes, see Section 2.1.1. Preparing to Install VIDA Client for DB2 1-1 1.1 Required Operating System Components The VMS operating system comes with a variety of support options, or classes. Classes include such features as networking and RMS journaling. To use VIDA Client for DB2, your system should be running a version of VMS that includes the following classes: _ Program development _ Network support _ Secure user environment _ Utilities 1.2 Prerequisite Software This section discusses the software you must have installed on your system before installing VIDA Client for DB2. The section also includes information about software that you can use together with VIDA Client for DB2. Please refer to the System Software Addendum (SSA) for a complete list of compatible products and their required version numbers. The SSA is part of the Software Product Description (SPD). 1.2.1 Software Requirements for VIDA Client for DB2 Installation You can install VIDA Client for DB2 only after the software products listed below have been successfully installed. The VIDA Client for DB2 installation procedure checks for the prerequisite software and stops if either has not been installed: _ VMS Version 5.0 or higher _ DECnet/SNA VMS APPC/LU6.2 Programming Interface Version 2.1 or higher 1.2.2 Software Requirements for VIDA Client for DB2 Use VIDA Server for DB2, which is the IBM side of VIDA for DB2, is not required for VIDA Client for DB2 installation. However, VIDA Server for DB2 is needed for VIDA Client for DB2 use. VIDA Server for DB2 installation is covered in the VIDA Server for DB2 Handbook. 1-2 Preparing to Install VIDA Client for DB2 The VIDA Client for DB2 Distribution Kit does not include a user interface through which you can retrieve data from an IBM system. Therefore, although the following products are not required for VIDA Client for DB2 installation, you cannot use VIDA Client for DB2 as part of the VIDA for DB2 product until you successfully install at least one of the following: _ VAX SQL Version 2.0 or higher. _ VAX DATATRIEVE Version 4.2 or higher. _ VAX Data Distributor Version 2.0 or higher. _ A programming language supported by the Rdb DML precom- piler. If a programming language is your user interface to VIDA for DB2, then VAX Rdb/VMS Version 3.0 or higher must be installed on the same system as the programming language software. _ VAX TEAMDATA Version 1.3 or higher. 1.3 Prerequisite Hardware You can install VIDA Client for DB2 only when your system meets or exceeds the minimum hardware requirements shown in the Software Product Description (SPD). 1.4 VMS License Management Facility The VMS License Management Facility (LMF) is available with Version 5.0 of the VMS operating system. You can only install VIDA Client for DB2 on a VMS Version 5.0 system; therefore, you must register your software license. The license registration information you need is contained in the Product Authorization Key (PAK) that is shipped with VIDA Client for DB2. The PAK is a paper certificate that contains information about the license you have that runs a particular piece of software. You must register your VIDA Client for DB2 license before you perform the installation. During the installation, you are asked if you have registered and loaded the VIDA Client for DB2 license. If you have not already done so, answer "NO". Once you perform the license registration and load, you can restart the installation and choose to run the IVP. Preparing to Install VIDA Client for DB2 1-3 To register a license under VMS Version 5.0, first log in to the system manager's account, SYSTEM. You then have a choice of two ways to perform the registration: _ Invoke the SYS$UPDATE:VMSLICENSE.COM procedure. When it prompts you for information, respond with data from your Product Authorization Key (PAK). _ Issue the LICENSE REGISTRATION DCL command with the appropriate qualifiers that correspond to information on the PAK. If you plan to use VIDA Client for DB2 on more than one node in a VAXcluster, you will need to perform a license load on the other nodes after you complete this installation. See Section 3.3 for information on installing licenses on all nodes in a cluster. For complete information on using LMF, see the manual on the License Management Utility in the VMS documentation set. 1.5 VAXcluster Considerations The VIDA Client for DB2 installation procedure creates an account called RDB$REMOTE on your system, if the account does not already exist. Programs executing on remote nodes and accessing a VIDA for DB2 database on your node through DECnet can log on to your system through the RDB$REMOTE account. Invoking a database at a remote node requires the network to log in to an account and execute the RDBSERVER.EXE image. The VIDA Client for DB2 installation procedure defines RDB$REMOTE as the default DECnet account for the RDBSERVER object. This definition supersedes (if RDB$REMOTE exists) any previous assignment you might have made in the Network Control Program (NCP) for RDBSERVER. The RDB$REMOTE account includes a password that you assign during the installation procedure. The password you provide is used for the RDB$REMOTE account and in the DECnet NCP object database on your VAX system. This means that the RDB$REMOTE password and the password assigned to the RDBSERVER.EXE image must be the same. The RDBSERVER.EXE image manages remote database access. In a VAXcluster environment, the installation procedure assigns the same password to RDB$REMOTE and RDBSERVER.EXE only on the node from which the installation took place. After the installation procedure finishes and if your DECnet 1-4 Preparing to Install VIDA Client for DB2 object database is not configured to be in the cluster common directory, you must run the RDBSERVER_NCP.COM procedure from the SYS$COMMON:[SYSMGR] account on each of the remaining VAXcluster nodes to insert the RDBSERVER object in the DECnet object database for those nodes. The RDB$REMOTE account is assigned the proper process quotas and privileges to work with VIDA for DB2. Users can encounter problems with remote database access because the default DECnet account commonly does not have sufficient process quotas. The RDB$REMOTE captive account does not require a SYLOGIN.COM procedure in the SYS$MANAGER account. However, if you encounter any errors using the RDB$REMOTE account, make sure that the SYS$SYLOGIN logical name (if defined) points to a working SYLOGIN.COM procedure. As a captive account, RDB$REMOTE does, however, require its own login procedure. The login procedure for RDB$REMOTE is RDB$REMOTE_LOGIN.COM and is written to SYS$COMMON:[SYSEXE]. This login procedure includes security checks that ensure that the user is running the RDBSERVER.EXE image (DECnet object number 35). If you want any procedures executed during the RDB$REMOTE account login step, you must edit RDB$REMOTE_ LOGIN.COM in the SYS$COMMON:[SYSEXE] directory after the installation and insert the appropriate DCL commands. DECnet does not need to be running for a successful installation of VIDA Client for DB2. See your VAX DECnet manuals for additional information. 1.6 Installation Procedure Requirements The following sections discuss various requirements for installing VIDA Client for DB2. 1.6.1 Time The installation takes approximately five to twenty minutes, depending on your type of media and your system configuration. Installing VIDA Client for DB2 and running the IVP on a standalone VAX 8200 system takes five minutes. Preparing to Install VIDA Client for DB2 1-5 1.6.2 Privileges To install VIDA Client for DB2 you must be logged in to an account that has SETPRV or at least the following privileges: _ CMKRNL _ EXQUOTA _ NETMBX _ OPER _ SYSNAM _ SYSPRV _ TMPMBX _ WORLD Note that VMSINSTAL turns off the BYPASS privilege at the start of the installation. 1.6.3 Disk Space Installing VIDA Client for DB2 requires a certain amount of free storage disk space during the installation. Once VIDA Client for DB2 is installed, less storage space is required. Table 1-1 summarizes the storage requirements for VIDA Client for DB2. Table 1-1 Disk Space Requirements _____________________________________________________________ Blocks During Blocks After Kit______________Installation__________Installation__________ VIDA Client for 3000 1900 DB2_Version_1.0______________________________________________ To determine the number of free disk blocks on the current system disk, enter the following command at the DCL prompt: $ SHOW DEVICE SYS$SYSDEVICE 1-6 Preparing to Install VIDA Client for DB2 1.6.4 System Parameters Installing VIDA Client for DB2 requires certain system parameter settings. Table 1-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 1-2 Required System Parameter Values _____________________________________________________________ System_Parameter___________Value_____________________________ CLISYMTBL[1] 250 GBLPAGES[2] n + 36 GBLSECTIONS[2] n + 2 _____________________________________________________________ [1]The CLISYMTBL dynamic system parameter must be set to a minimum value of 250 during the installation procedure. If the current CLISYMTBL setting is less than 250, you can lower the setting to its original value once the installation is finished. [2]The n variable refers to the system parameter values that are currently in use. To install VIDA Client for DB2 you must raise those values by the number indicated. (See Section 1.6.4.2.) _____________________________________________________________ The following sections show you how to: _ Check system parameter values _ Calculate values for the GBLPAGES and GBLSECTIONS system parameters _ Change parameter values with the VMS AUTOGEN command procedure _ Set the CLISYMTBL dynamic system parameter with the VMS System Generation Utility (SYSGEN) Preparing to Install VIDA Client for DB2 1-7 1.6.4.1 Checking System Parameter Values To check the values of your system parameters, enter the following command at the DCL prompt to invoke the System Generation Utility: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> At the SYSGEN> prompt, enter the SHOW command to display the value of a system parameter. The values displayed should equal or exceed the value of each parameter listed in Table 1-2. The following command displays the value for the CLISYMTBL system parameter: SYSGEN> SHOW CLISYMTBL After you finish checking the parameters with the SHOW command, you can enter the EXIT command at the SYSGEN> prompt to return to DCL level. 1.6.4.2 Calculating the Values for GBLPAGES and GBLSECTIONS To install and run VIDA Client for DB2, you must have sufficient free global pages and global sections. You must first find out how many free global pages and sections you have on your system. You use AUTOGEN to increase the GBLPAGES and GBLSECTIONS system parameters. Use the WRITE command with the F$GETSYI lexical function to find the number of free global pages and global sections. The following example shows how to get this information at your terminal (the default for SYS$OUTPUT): $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES") 15848 $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS") 24 If the numbers displayed by the system are greater than the numbers in Table 1-2, you do not need to increase the values for these parameters. If the number of free global pages or global sections is less than the value in Table 1-2, you must increase the system parameter setting. Section 1.6.4.3 describes the procedures for increasing these values using AUTOGEN. Refer to the VMS System Management Subkit for information on using AUTOGEN. 1-8 Preparing to Install VIDA Client for DB2 1.6.4.3 Changing System Parameter Values with AUTOGEN You use the AUTOGEN command procedure to change system parameters. AUTOGEN automatically adjusts values for parameters that are associated with the ones you reset manually. To change system parameters with AUTOGEN, you must edit the following file: SYS$SYSTEM:MODPARAMS.DAT Use an editor to access the file. If you need to change a pa- rameter value that is already in the SYS$SYSTEM:MODPARAMS.DAT file, simply delete the current value associated with that parameter and enter the new value. To add a new value, add a line to the MODPARAMS.DAT file. The line contains the name of the parameter and its value. For example: WSMAX = 1024 To modify incremental parameters such as GBLPAGES and GBLSECTS, use ADD_. The following example increases the global page setting by 2000: ADD_GBLPAGES = 2000 After you have made all your changes, exit from the editor and run the AUTOGEN procedure to recalculate your system parameters. Enter the following command at the DCL prompt: $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT When you specify REBOOT, AUTOGEN performs an automatic system shutdown and reboots when it has finished. Any users logged on to the system are immediately disconnected during the shutdown. The automatic reboot puts the new parameter values into effect. The Autogen Utility automatically adjusts some of the SYSGEN parameters based on the consumption of resources since the last reboot. If you do not want to take advantage of this automatic adjustment, include the /NOFEEDBACK qualifier on the AUTOGEN command line. For more information about using AUTOGEN, see the VMS System Management Subkit. Preparing to Install VIDA Client for DB2 1-9 1.6.4.4 Setting the CLISYMTBL Dynamic System Parameter If the CLISYMTBL system parameter value for your system is less than 250, change the setting by using the following series of commands: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> USE ACTIVE SYSGEN> SET CLISYMTBL 250 SYSGEN> WRITE ACTIVE SYSGEN> EXIT Dynamic parameters changed with the System Generation Utility's WRITE ACTIVE command become active immediately without any need to reboot your system. In fact, rebooting returns dynamic system parameter values to their previous settings. Once you set the CLISYMTBL value, you should complete the installation before rebooting the system. After the installation is complete, you can reset CLISYMTBL to its previous setting or let it be reset automatically when you reboot your system. 1.6.5 Process Account Quotas The account you use to install VIDA Client for DB2 must have sufficient quotas to enable you to perform the installation. Table 1-3 summarizes the process quotas required for the installation account. Table 1-3 Process Account Quotas for the Installing Account _____________________________________________________________ Account_Quota____Value_______________________________________ ASTLM 24 BIOLM 18 BYTLM 18,000 DIOLM 18 ENQLM 30 (continued on next page) 1-10 Preparing to Install VIDA Client for DB2 Table 1-3 (Cont.) Process Account Quotas for the Installing Account _____________________________________________________________ Account_Quota____Value_______________________________________ FILLM 20 PRCLM 2 WSDEF 200[1] _____________________________________________________________ [1]The values for WSEXT and WSQUO must be equal to or greater than the WSDEF value. _____________________________________________________________ User account quotas are stored in the file SYSUAF.DAT. You use the VMS Authorize Utility to verify and change user account quotas. First set your directory to SYS$SYSTEM and then run AUTHORIZE: $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> At the Authorize Utility prompt (UAF>), use the SHOW command with an account name to check a particular account. For example: UAF> SHOW SMITH To change a quota, use the MODIFY command at the UAF> prompt. MODIFY has the following format: MODIFY account-name /quota-name=nnnn The following example changes the FILLM quota for the SMITH account and then exits from the Authorize Utility: UAF> MODIFY SMITH /FILLM=50 UAF> EXIT After you exit from the utility, the VMS system displays messages indicating whether or not changes were made. Once the changes have been made, you must log out and log in again for the new quotas to take effect. For more information on modifying account quotas, see the description of the Authorize Utility in the VMS documentation set. Preparing to Install VIDA Client for DB2 1-11 1.6.6 VMSINSTAL Requirements When you invoke VMSINSTAL, it checks the following: _ Whether you have set your default device and directory to SYS$UPDATE _ Whether you are logged in to a privileged account _ Whether you have adequate quotas for installation _ Whether DECnet is up and running _ Whether any users are logged in to the system Note that the VMSINSTAL requires that the installation account have a minimum of the following quotas: ASTLM = 24 BIOLM = 18 BYTLM = 18,000 DIOLM = 18 ENQLM = 30 FILLM = 20 If VMSINSTAL detects any problems during the installation, it notifies you of the problem and asks if you want to continue the installation. In some instances, you can enter YES to continue. To stop the installation process and correct the situation, enter NO or press RETURN. Then correct the problem and restart the installation. 1.6.7 Backing Up Your System Disk At the beginning of the installation, VMSINSTAL asks if you have backed up your system disk. Digital recommends that you do a system disk backup before installing any software on top of the operating system. Use the backup procedures that have been established at your site. For details on performing a system disk backup, see the section on the Backup Utility in the VMS documentation set. 1-12 Preparing to Install VIDA Client for DB2 1.6.8 VIDA Client for DB2 Requirements VIDA Client for DB2 checks for the DECnet/SNA VMS APPC/LU6.2 Programming Interface Version 2.1 or higher. The Programming Interface enables a VMS application and an SNA application to take part in a distributed transaction environment that uses IBM Advanced Program-to-Program Communication. DECnet/SNA VMS APPC/LU6.2 release notes are available in the following directory: SYS$HELP:SNALU62021.RELEASE_NOTES Preparing to Install VIDA Client for DB2 1-13 2 ________________________________________________________________ Installing VIDA Client for DB2 This chapter describes how to install VIDA Client for DB2. Section 2.2 contains a step-by-step description of the installation procedure. 2.1 General Information This section includes information about the following topics: _ Accessing release notes _ Determining files added to your system _ Running the Installation Verification Procedure (IVP) _ Aborting the installation 2.1.1 Accessing the Online Release Notes VIDA for DB2 provides online release notes. You must specify OPTIONS N when you invoke VMSINSTAL to see the question about online release notes. This question comes near the beginning of the installation. You should review the release notes in case they contain any information about changes in the installation procedure. If you are starting the installation over again and have already reviewed the release notes, you do not need to specify OPTIONS N. Once VIDA Client for DB2 has been installed, the release notes are located in the following file: SYS$HELP:VIDA2$010.RELEASE_NOTES Installing VIDA Client for DB2 2-1 Online help also directs you to the release notes file. After the installation, you can enter the following command to review the release notes through the Help facility: $ HELP VIDA_DB2 RELEASE_NOTES Note that hardcopy release notes are included with the documentation set for VIDA Client for DB2. 2.1.2 Determining the Files Added to the System The files added to the system during VIDA Client for DB2 installation are listed and described in Appendix B of this installation guide. 2.1.3 Running the Installation Verification Procedure (IVP) The Installation Verification Procedure (IVP) for VIDA Client for DB2 verifies the installation. During the installation, you are asked if you want to run the IVP as part of the installation. If you respond YES, VMSINSTAL automatically runs the IVP. It is recommended that you run this IVP to be sure that VIDA Client for DB2 is installed correctly. After VIDA Client for DB2 is installed, you can run the installation IVP independently to verify that the software is available on your system. Run the installation IVP procedure at any time. Execute this IVP procedure with the following: $ SET DEF SYS$COMMON:[SYSTEST.VIDA2$TEST] $ @VIDA2$IVP The VIDA Client for DB2 installation offers a second IVP, VIDA2$LIVE_IVP. The installation IVP, VIDA2$IVP, only verifies the installation of VIDA Client for DB2. It does not test the hardware link from the VAX to the IBM system, nor does it test the software link from VIDA Client for DB2 to VIDA Server for DB2. The second, or Live IVP, does test the hardware and software links from the VAX to the IBM system. After the VIDA Server for DB2 installation is complete and the gateway system is set up, you can run the Live IVP. This command procedure checks the installation of VIDA Client for DB2, sets up the user environment, invokes SQL to enter a query, compares the result of the query to expected results and reports the differences, and indicates if the Live IVP completed successfully. Invoke the Live IVP with the following: 2-2 Installing VIDA Client for DB2 $ SET DEF SYS$COMMON:[SYSTEST.VIDA2$TEST] $ @VIDA2$LIVE_IVP Refer to Chapter 4 for information on running the Live IVP. 2.1.4 Aborting the Installation To abort the installation procedure at any time, press CTRL/Y. When you press CTRL/Y, the installation procedure deletes all files it has created up to that point and exits. You can then start the installation again. 2.2 The Installation Procedure The VIDA Client for DB2 installation process consists of a series of questions and informational messages. 2.2.1 Invoking VMSINSTAL To start the installation, invoke the VMSINSTAL command procedure from a privileged account, such as the SYSTEM account. VMSINSTAL is in the SYS$UPDATE directory. You use the following syntax to invoke VMSINSTAL: @SYS$UPDATE:VMSINSTAL product-name device-name OPTIONS N product-name The installation name for the component. For VIDA Client for DB2 use the following installation name: VIDA2 device-name The name of the device on which you plan to mount the media. For example, MTA0: is the device name for a tape drive. It is not necessary to use the console drive for this installation. However, if you do use the console drive, you should replace any media you removed once the installation is complete. OPTIONS N An optional parameter that indicates you want to see the release notes question. 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 new information about the installation. Note that there are several other options you can select when you invoke VMSINSTAL. See the VMS documentation on software installation in the VMS System Management Subkit for information on these options. Installing VIDA Client for DB2 2-3 The following example displays the command to invoke VMSINSTAL to install VIDA Client for DB2 from tape drive MTA0: and shows the system response. This example uses the OPTIONS N release note parameter. $ @SYS$UPDATE:VMSINSTAL VIDA2 MTA0: OPTIONS N VAX/VMS Software Product Installation Procedure V5.0-1 It is 30-AUG-1989 at 09:18. Enter a question mark (?) at any time for help. If you do not supply either the product name or the device name, VMSINSTAL prompts you for this information later in the installation procedure. VMSINSTAL does not prompt you for any options, so be sure to include OPTIONS N on the VMSINSTAL command line to access the release notes during the installation. 2.2.2 Answering Installation Questions This section discusses the questions that are displayed during the installation. Appendix A contains a sample installation procedure showing how the questions can be answered. Each question in the installation is marked with an asterisk (*) at the beginning of the line. Some questions show the default response in brackets, for example [YES]. If you want to use the default response, press the RETURN key. 1 DECnet status If you are operating under VMS Version 5.0-1 or higher, VMSINSTAL notifies you if DECnet is running and displays a list of all active processes. It then asks if you want to continue the installation. NO is the default response to the question. Under VMS Version 5.2, the network status is no longer checked when VMSINSTAL begins. Therefore, you are not asked if you would like to continue the installation. The display for VMS Version 5.0-1 is as follows: 2-4 Installing VIDA Client for DB2 %VMSINSTAL-W-DECNET, Your DECnet network is up and running. . . . * Do you want to continue anyway [NO]? 2 System backup VMSINSTAL asks if you are satisfied with your system backup. You should always back up your system disk before performing an installation. If you are satisfied with the backup of your system disk, press RETURN. Otherwise, enter NO to discontinue the installation. After you back up your system disk, you can restart the installation. * Are you satisfied with the backup of your system disk [YES]? 3 Mounting the media You should now mount the first distribution volume on the device you specified when you invoked VMSINSTAL. The device name appears in the line preceding the question. VMSINSTAL then asks where the distribution volumes will be mounted. If you respond YES to indicate that you are ready, VMSINSTAL displays a message stating the media containing VIDA Client for DB2 has been mounted on the specified device and the installation has begun. For example: Please mount the first volume of the set on MTA0:. * Are you ready? YES %MOUNT-I-MOUNTED, VIDA2 MOUNTED ON _$$MTA0: (NODE1) The following products will be processed: VIDA2 V1.0 Beginning installation of VIDA2 V1.0 at 09:19 %VMSINSTAL-I-RESTORE, Restoring product saveset A... 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 any reason, press CTRL/Y. 4 Release Notes If you specified OPTIONS N when you started the instal- lation, VMSINSTAL asks a release note question. You have five options for handling the release notes under VMS Installing VIDA Client for DB2 2-5 Version 5.0-1 or higher, four options under VMS Version 5.2. Under VMS Version 5.2, release notes are always copied to SYS$HELP. For VMS Version 5.0-1 or higher, you see the following display: Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. Copy release notes to SYS$HELP 5. Do not display, print or copy release notes * Select option [2]: The display for VMS Version 5.2 is as follows: 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 console 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 that you want to use: * Queue name [SYS$PRINT]: You can press RETURN to send the file to the default output print device or you can enter another queue name. If you select option 3, VMSINSTAL displays the release notes immediately on the console terminal and then prompts you for a queue name for the printed version. Option 4, under VMS Version 5.0-1 or higher, causes the installation to copy the release notes to the help directory. (Even if you do not select option 4, the release notes for VIDA for DB2 are copied to the SYS$HELP directory.) 2-6 Installing VIDA Client for DB2 Select option 5 if you are running VMS Version 5.0-1 and have already reviewed the release notes and are restarting the installation. 5 Continuing the installation The installation procedure now asks if you want to continue the installation. To continue, enter YES. Otherwise, press RETURN. In either case, the release notes are copied to a file in the SYS$HELP directory. For example: * Do you want to continue the installation [N]?: YES %VMSINSTAL-I-RELMOVED, The product's release notes have been successfully moved to SYS$HELP. The release notes are located in the following file: SYS$HELP:VIDA2$010.RELEASE_NOTES 6 Checking system requirements While the installation procedure checks several system requirements, the following messages are displayed: ******************************************************* Installation procedures for: VIDA/DB2 V1.0 ******************************************************* ******************************************************* Checking system requirements ... ******************************************************* The installation procedure displays an error message and aborts if the procedure finds that your system does not have the following software and hardware requirements: _ VMS Version 5.0 or higher _ DECnet/SNA VMS APPC/LU6.2 Programming Interface Version 2.1 or higher _ DECnet/SNA VMS APPC/LU6.2 Programming Interface Version 2.1 license _ Adequate disk space _ Adequate free global pages and global sections Installing VIDA Client for DB2 2-7 If you encounter an error at this point, take the steps necessary to meet your system requirements and restart the installation procedure. 7 License registration The installation procedure displays license information about your product and then asks if you have registered and loaded your authorization key for VIDA Client for DB2. For example: Product: VIDA Producer: DEC Version: 1.0 Release Date: 30-JUN-1989 * Does this product have an authorization key registered and loaded? If you have not registered and loaded your authorization key, you must answer "NO" to this question. You have to register and load your product authorization key to successfully complete the installation. If you have not done so, you should stop the installation, register and load your product authorization key, and then restart the installation. If you encounter any LMF error messages, refer to the VMS License Management Utility Manual. Note The installation procedure checks for the DECnet/SNA VMS APPC/LU6.2 Programming Interface registration. However, no questions prompt you for information on the registration. 8 Entering the UIC and password for the RDB$REMOTE account. The installation procedure displays a series of messages and questions about the RDB$REMOTE account: ************************************************************ This installation requires the creation of the RDB$REMOTE account. You MUST choose a UIC and password for this account. PLEASE NOTE that your password for the RDB$REMOTE account and the network object RDBSERVER MUST be exactly the same. The password you supply for the RDB$REMOTE account will be used for the network object as well IF the account is created by this installation. ************************************************************* 2-8 Installing VIDA Client for DB2 ************************************************************* The installation procedure will not proceed until you enter a valid user identification code (UIC) for the RDB$REMOTE account. ************************************************************* * Please enter UIC to be used for RDB$REMOTE account (e.g. [ggg,mmm]): You must supply a valid UIC or the installation procedure cannot continue. When a valid UIC has been provided, the installation procedure then displays an informational message about entering password information: ************************************************************* The entire installation will FAIL if you do not enter a valid password for the RDB$REMOTE account. You will be given 3 chances to verify your password. This installation procedure requires at least 6 characters for the RDB$REMOTE password. Valid characters for a password are: A through Z a through z 0 through 9 $ (dollar sign) _ (underscore) As with the DCL SET PASSWORD command, your input will not appear on the terminal. And to protect against typing errors that are not seen when entering the password, you must enter the password twice. ************************************************************** * Please enter PASSWORD to be used for RDB$REMOTE account: * Please verify the PASSWORD entered for RDB$REMOTE: 9 Choosing to purge files You have the option to purge files from previous versions of VIDA Client for DB2 that are superseded by this installation. Purging is recommended; however, if you need to keep files from the previous version, enter NO in response to the question. If this is a Version 1 software, enter the default response [YES]. * Do you want to purge files replaced by this installation [YES]? Installing VIDA Client for DB2 2-9 10 Choosing to run the Installation Verification Procedure (IVP) The installation procedure now asks if you want to run the Installation Verification Procedure. This question is in reference to the installation IVP. This IVP for VIDA Client for DB2 checks to be sure that the installation is successful. It is recommended that you run the installation IVP. * Do you want to run the IVP after the installation [YES]? 2.2.3 Understanding Informational Messages At this point, the installation procedure displays a number of informational messages that report on the progress of the installation. There are no further questions. If the installation procedure has been successful up to this point, VMSINSTAL moves the new or modified files to their target directories, updates help files, and updates DCL tables, if necessary. If you asked for files to be purged, that work is done now. The following messages are displayed: **************************************************************** There are no more questions. The installation takes ap- proximately 5 minutes on a stand-alone VAX 8200. **************************************************************** **************************************************************** Beginning installation ... **************************************************************** **************************************************************** Installing under VMS V5.0-1 - 30-AUG-1989 09:21 **************************************************************** %VMSINSTAL-I-RESTORE, Restoring product saveset B ... %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSTEST.VIDA2$TEST] **************************************************************** The VIDA2 IVP has been placed in SYS$COMMON:[SYSTEST.VIDA2$TEST]. You may run this procedure separately any time you wish. To execute it, type: 2-10 Installing VIDA Client for DB2 $ SET DEF SYS$COMMON:[SYSTEST.VIDA2$TEST] $ @VIDA2$IVP **************************************************************** **************************************************************** The live VIDA2 IVP has been placed in SYS$COMMON:[SYSTEST.VIDA2$TEST]. You may run this procedure separately after the environment has been set up. To execute it, type: $ SET DEF SYS$COMMON:[SYSTEST.VIDA2$TEST] $ @VIDA2$LIVE_IVP **************************************************************** **************************************************************** Adding VIDA2 help to the DCL help library **************************************************************** %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[RDB$REMOTE]. %VIDA2-I-ACCOUNT, This installation creates an account named RDB$REMOTE. RDBSERVER has been placed in the DECnet object database as number 35. **************************************************************** SYSTEM MANAGER: If your DECnet object database is not configured to be in the cluster common directory, then you will need to perform the following: In order to have remote access on another node which shares this cluster common root directory, you must insert RDBSERVER.EXE into that node's DECnet object database by: a) Logging into that node, and b) Invoking SYS$COMMON:[SYSMGR]RDBSERVER_NCP.COM. This command procedure inserts RDBSERVER into the node's permanent DECnet object database. This procedure only needs to be executed ONCE per node. This command procedure will prompt for a password for the object RDBSERVER. This password must match the password established for the account. Installing VIDA Client for DB2 2-11 **************************************************************** %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... **************************************************************** ****************************************************************** The VIDA Client for DB2 IVP verifies that all files are properly in place. It does not test the hardware link from the VAX to the IBM system, nor does it test the software link from VIDA Client to VIDA Server for DB2. Once the VIDA Server for DB2 software has been installed on your IBM system and your communications environment has been set up, you should try running the VIDA2$LIVE_IVP. If the VIDA2$LIVE_IVP completes successfully, then everything is installed properly. **************************************************************** **************************************************************** Performing VIDA/DB2 IVP for: VIDA/DB2 V1.0 **************************************************************** Some common images are provided with all DSRI-compliant database products. During the VIDA Client for DB2 instal- lation, common images are not replaced, for example, if the version on the system is more recent that the image being installed. The messages displayed in this case are as follows: %VIDA2-I-NOTINSTALLED, VMI$KWD:RDBSHR.EXE was not installed by this kit %VIDA2-I-REASON, Image ident version of new file is the same as current file VIDA Client for DB2 displays messages of this type just before the message about moving files to other directories. 2.2.4 Running the Installation Verification Procedure If you chose to run the IVP, VMSINSTAL runs it now. When the IVP runs successfully, you see the following display: **************************************************** VIDA/DB2 V1.0 IVP completed successfully **************************************************** 2-12 Installing VIDA Client for DB2 2.2.5 Completing the Installation Procedure The following messages indicate that the entire installation procedure is complete: Installation of VIDA2 V1.0 completed at 09:28 VMSINSTAL procedure done at 09:28 You can now log out of the privileged account: $ LOGOUT SYSTEM logged out at 30-AUG-1989 at 09:41:36:50 Note that VMSINSTAL deletes or changes entries in the process symbol tables during the installation. Therefore, if you are going to continue using the system manager's account and you want to restore these symbols, you should log out and log in again. 2.3 Error Recovery If errors occur during the installation itself or when the IVP is running, VMSINSTAL displays failure messages. If the installation fails, you see the following message: %VMSINSTAL-E-INSFAIL, The installation of VIDA2 V1.0 has failed. If the IVP fails, you see these messages: The VIDA/DB2 V1.0 Installation Verification Procedure failed. %VMSINSTAL-E-IVPFAIL, The IVP for VIDA/DB2 V1.0 has failed. Errors can occur during the installation if any of the following conditions exist: _ The operating system version is incorrect. _ A prerequisite software version is incorrect or not installed. _ A prerequisite software license has not been registered and loaded. _ Quotas necessary for successful installation are insufficient. _ System parameter values for successful installation are insufficient. _ The VMS help library is currently in use. Installing VIDA Client for DB2 2-13 _ The product license has not been registered and loaded. For descriptions of the error messages generated by these conditions, see the VMS documentation on system messages, recovery procedures, and VMS software installation. If you are notified that any of these conditions exist, you should take the appropriate action as described in the message. (You might need to change a system parameter or increase an authorized quota value.) For information on installation requirements, see Chapter 1. 2-14 Installing VIDA Client for DB2 3 ________________________________________________________________ After Installing VIDA Client for DB2 After installing VIDA Client for DB2, you need to perform the following tasks: _ Modify system parameter settings _ Set user account quotas _ Install licenses on all nodes in a cluster _ Execute RDBSERVER_NCP.COM in VAXclusters _ Meet ALL-IN-1 requirements _ Ensure VIDA Client for DB2 works with Data Distributor _ Test the VIDA Client for DB2 installation and the link to the IBM system This chapter also explains how to run the automatic Installation Verification Procedure (IVP) independently after the software has been installed. 3.1 Modifying System Parameters The installation for VIDA Client for DB2 requires that you raise the value of the CLISYMTBL system parameter. Once the installation is complete, you should lower this value to ensure efficient system performance. 3.2 Setting User Account Requirements To work with VIDA Client for DB2, user accounts on your system must have certain privileges and quotas. The next two sections contain information on these requirements. After Installing VIDA Client for DB2 3-1 3.2.1 Privileges To use VIDA Client for DB2, each account must have at least the TMPMBX and NETMBX privileges. Use the VMS Authorize Utility to determine whether users have the privileges they require. 3.2.2 User Account Quotas In most cases, default values for system quotas (refer to Table 1-3) are adequate for VIDA for DB2 users. However, VIDA for DB2 users who submit batch jobs and who use VIDA for DB2 with VMS/SNA might need a FILLM quota greater than 20. If a VIDA for DB2 user encounters the error "quota exceeded," increase the user's FILLM quota to 30. User account quotas are stored in the file SYSUAF.DAT. You use the VMS Authorize Utility to verify and change user account quotas. First set your directory to SYS$SYSTEM and then run AUTHORIZE: $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> At the Authorize Utility prompt (UAF>), enter the SHOW command with an account name to check that particular account. For example: UAF> SHOW SMITH To change a quota, use the MODIFY command at the UAF> prompt. MODIFY has the following syntax: MODIFY account-name /quota-name=nnnn The following example changes the FILLM quota for the SMITH account and then exits from the utility: UAF> MODIFY SMITH /FILLM=30 UAF> EXIT After you exit from the utility, the VMS system displays messages indicating whether or not changes were made. Once you have finished making the changes, the users must log out and log in again for the new quotas to take effect. For more information on modifying account quotas, see the description of the Authorize Utility in the VMS documentation set. 3-2 After Installing VIDA Client for DB2 3.3 Installing Licenses on All Nodes in a Cluster A license should be installed on all the nodes in a cluster. If you try to run VIDA for DB2 on a clustered node that does not have the required licenses registered, you receive an error message. Complete the following steps to install the licenses on all nodes in your cluster: 1 Install the license on one node by entering the following command: $ @SYS$UPDATE:VMSLICENSE.COM 2 Load the license on the rest of the nodes in the cluster: $ LICENSE LOAD VIDA If you encounter any errors, refer to the VMS License Management Utility Manual. 3.4 Executing RDBSERVER_NCP.COM in VAXclusters If your DECnet object database is not configured to be in the cluster common directory (the default starting in VMS Version 4.4), you must insert the RDBSERVER object in each node's DECnet object database. This action enables remote database access on nodes sharing the cluster common directory. Follow these steps: 1 Log in to each node. 2 Invoke SYS$COMMON:[SYSMGR]RDBSERVER_NCP.COM. The RDBSERVER_NCP.COM procedure prompts for the password to assign to the RDBSERVER object. For remote database access to work, you must assign the password entered during the VIDA Client for DB2 installation procedure. For example, if PASSERBY_WORD was the password you assigned to the RDB$REMOTE account during the installation procedure on a VAXcluster node MOE, you must log in to each remaining node and perform the following procedures: $ SET DEFAULT SYS$COMMON:[SYSMGR] $ @RDBSERVER_NCP Please enter the password for object name RDBSERVER: PASSERBY_WORD Please verify password: PASSERBY_WORD After Installing VIDA Client for DB2 3-3 3.5 Meeting ALL-IN-1 Requirements If you do not have ALL-IN-1 installed on your system, proceed to the next section. VIDA Client for DB2 includes images that have to be installed with the VMS Install Utility (INSTALL) to ensure that ALL- IN-1 works properly. The VMS operating system requires that all image files activated by a privileged image be installed using the VMS Install Utility. ALL-IN-1 is a privileged image that activates all the images in the SYS$SHARE directory and the message file images that are subordinate to the images in SYS$SHARE. If you are installing VIDA Client for DB2 on a system that runs ALL-IN-1, you should use INSTALL to add any of the following images that were not installed for ALL-IN-1 before you installed VIDA Client for DB2: RUN SYS$SYSTEM:INSTALL INSTALL> ADD SYS$SHARE:VIDA2SHR.EXE INSTALL> ADD SYS$SHARE:RDBSHR.EXE INSTALL> ADD SYS$SHARE:SNALU62SH.EXE INSTALL> ADD SYS$MESSAGE:VIDA2$MESSAGE.EXE INSTALL> ADD SYS$MESSAGE:RDBMSGS.EXE INSTALL> ADD SYS$MESSAGE:RDBBMSGS.EXE INSTALL> ADD SYS$MESSAGE:RDMSMSG.EXE INSTALL> ADD SYS$MESSAGE:VIDA_MESSAGE.EXE Modify your system startup command file to include an INSTALL command for all of the preceding files. (Your system startup command file might already include INSTALL commands for RDBSHR.EXE and some of the message images, if Rdb/VMS or another DSRI product is installed on your system.) 3.6 Ensuring VIDA Client for DB2 Works with Data Distributor If you do not have Data Distributor installed on your system, proceed to the next section. The VIDA Client for DB2 installation includes images that you might need to install with the VMS Install Utility (INSTALL) to make sure that Data Distributor works properly with VIDA Client for DB2. The VMS operating system requires that all image files activated by a privileged image be installed using INSTALL. Data Distributor is a privileged image that activates some of the images in the SYS$SHARE directory and the message file images that are subordinate to the images in SYS$SHARE. 3-4 After Installing VIDA Client for DB2 If you are installing VIDA Client for DB2 on a system that runs Data Distributor, you should use INSTALL to add any of the following images that were not installed for Data Distributor before you installed VIDA Client for DB2: RUN SYS$SYSTEM:INSTALL INSTALL> ADD SYS$SHARE:VIDA2SHR.EXE INSTALL> ADD SYS$MESSAGE:VIDA2$MESSAGE.EXE INSTALL> ADD SYS$SHARE:SNALU62SH.EXE Modify your system startup command file to include an INSTALL command for each of these files. 3.7 Installing VIDA Client for DB2 as a Shared Image If you expect VIDA Client for DB2 to be used extensively on your system, you can reduce the system overhead and memory requirements by installing it as a shared image. To install VIDA Client for DB2 as a shared image on a system that is currently running, use the VMS Install Utility (INSTALL). It is recommended that you perform the install operation on a system that has just been rebooted because the available space in the global page table is less likely to be fragmented. To install VIDA Client for DB2 as a shared image, first determine the number of available global pages and global sections on your system. See Section 1.6.4.2 for information on how to verify and modify the number of global pages and global sections. Table 1-2 contains the required values for these parameters. Once you have reset the system parameter values, invoke the VMS Install Utility from a privileged account and then install VIDA Client for DB2 as a shared image: INSTALL :== "$SYS$SYSTEM:INSTALL /COMMAND_MODE" $ INSTALL INSTALL> ADD SYS$SHARE:VIDA2SHR.EXE /OPEN /SHARED INSTALL> ADD SYS$MESSAGE:VIDA2$MESSAGE.EXE /OPEN /SHARED INSTALL> EXIT You must now add the following lines to the appropriate system startup command file so that each time the system is started, VIDA Client for DB2 is available as a shared image. (If your site has modularized its startup procedures, be sure you add the lines to the correct file. The default startup After Installing VIDA Client for DB2 3-5 command file for VMS Version 5.0 is SYS$MANAGER:SYSTARTUP_ V5.COM.) $ INSTALL INSTALL> ADD SYS$SYSTEM:VIDA2SHR.EXE /OPEN /SHARED INSTALL> ADD SYS$MESSAGE:VIDA2$MESSAGE.EXE /OPEN /SHARED INSTALL> EXIT Note that when you install VIDA Client for DB2 as a shared image you may need to increase the global pages and global sections parameters. Increase global pages (GBLPAGES) by 36 pages and global sections (GBLSECTIONS) by 2 sections. Refer to Section 1.6.4 for information on changing these parameters. 3.8 Testing the VIDA Client for DB2 Installation and the Link to IBM The VIDA Client for DB2 Installation Verification Procedure (IVP) checks to ensure that the files copied during the VIDA Client for DB2 installation reside in the appropriate system directories. The installation IVP does not test the hardware and software link from VIDA Client for DB2 to your IBM system. Once VIDA Server for DB2 has been successfully installed on the IBM system and the communications environment has been set up, your site can use the VIDA Client for DB2 Live IVP to test the hardware and software link to the IBM system. Refer to Appendix C in this manual for a sample run of the Live IVP. You can also check the hardware and software link by using VAX user interface software, such as DATATRIEVE or the Relational Database Operator (RDO) utility of Rdb/VMS, to retrieve some data from the IBM system. Retrieving data tests the outermost software layers of your VAX to IBM link. On the Digital side, it verifies that your VAX user interface software works correctly with VIDA Client for DB2. The Live IVP verifies that data table definitions and user access to tables are set up correctly. 3-6 After Installing VIDA Client for DB2 3.9 Determining and Reporting Problems If you encounter a problem while using VIDA Client for DB2, 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: _ Call Digital if your software contract or warranty agreement entitles you to telephone support. _ Submit a Software Performance Report (SPR). _ Fill out and submit a Reader's Comment form if the problem has to do with the VIDA Client for DB2 documentation. There are Reader's Comments forms at the back of each manual. Use the form from the manual in which you found the error. 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 indicated above or follow alternate instructions provided by Digital for reporting SPD nonconformance problems. See the VIDA Client for DB2 Handbook for information on how to submit an SPR. After Installing VIDA Client for DB2 3-7 4 ________________________________________________________________ Running the Live Installation Verification Procedure This chapter describes how to run the Live Installation Verification Procedure (Live IVP). Section 4.3 contains a step-by-step description of the Live IVP. 4.1 General Information This section includes information on using the Live IVP, accessing online help, and aborting the IVP. 4.1.1 Using the Live IVP After all the components of VIDA for DB2 have been installed, you can run the Live IVP to test the hardware and software links from the VAX to IBM systems. This command procedure checks the installation of VIDA Client for DB2, sets up the user environment, invokes SQL to format a query to DB2, and indicates if the Live IVP completed successfully. 4.1.2 Accessing Online Help Files Online help files are available for the Live IVP. Enter the following command to access online help: $ HELP VIDA_DB2 IVP Running the Live Installation Verification Procedure 4-1 4.1.3 Aborting the IVP To abort the IVP at any time, press CTRL/Y. When you press CTRL/Y, the IVP stops running and aborts the SQL query, if the query is in progress. The following message is displayed: *********************************************** VIDA/DB2 V1.0 IVP aborted due to user activated Control-Y interrupt *********************************************** If the query was running when you pressed CTRL/Y, an incomplete query result file may now exist. If an incomplete query file does exist, you should delete it. The query file is named VIDA2$LIVE_IVP.RES. 4.2 Required Components for Running the Live IVP The Live IVP tests the hardware and software links from the VAX to the IBM systems. Therefore, all components of VIDA for DB2 must be running. 4.2.1 Prerequisite Hardware Verify with your system manager that the hardware required to use VIDA Client for DB2 is up and running. You should also also check with the IBM system manager to make sure that all VIDA Server for DB2 hardware pieces are operational. 4.2.2 Prerequisite Software As with the prerequisite hardware, the software for both VIDA Client for DB2 and VIDA Server for DB2 must be installed and working. Check with the IBM system manager to make sure all the needed software to access VIDA Server for DB2 is up and running. The Live IVP also requires that SQL software is installed on your system. Check with your system manager to make sure SQL is up and running before using the Live IVP. 4.2.3 User Account Requirements Your user account must have certain privileges and quotas to run the Live IVP. Refer to Section 1.6.2 for information on privileges and Section 1.6.5 for information on user account quotas. 4-2 Running the Live Installation Verification Procedure 4.3 The Live IVP Procedure The Live IVP consists of a series of interactive questions and informational messages. The following section discusses the Live IVP prompts and messages. 4.3.1 Invoking the Live IVP Execute the Live IVP with the following: $ SET DEF SYS$COMMON:[SYSTEST.VIDA2$TEST] $ @VIDA2$LIVE_IVP The Live IVP displays an informational message and indicates that the IVP has begun. ****************************************************************** * * * VIDA Client for DB2 Live IVP * * * * Note: This procedure must be run from the system test * * directory: SYS$TEST:[SYSTEST.VIDA2$TEST]. * * * * The VIDA2 Live IVP first verifies that all the VIDA2 * * files are in place. It then accesses the DB2 PERSONNL * * database (supplied with the VIDA Server for DB2 software), * * executes 2 queries, and compares the result with a * * supplied output file. Any differences in the outputs * * will cause this test to fail, and are reported in * * VIDA2$LIVE_IVP.DIF. The result of the queries is in * * VIDA2$LIVE_IVP.RES. * * * ****************************************************************** Please press the RETURN key to continue: ****************************************************************** The VIDA Client for DB2 IVP verifies that all files are properly in place. It does not test the hardware link from the VAX to the IBM system, nor does it test the software link from VIDA Client for DB2 to VIDA Server for DB2. Once the VIDA Server for DB2 software has been installed on your IBM system and your communications environment has been set up, you should try running the VIDA2$LIVE_IVP. If the VIDA2$LIVE_IVP completes successfully, then everything is installed properly. ***************************************************************** Running the Live Installation Verification Procedure 4-3 Performing VIDA/DB2 IVP for: VIDA/DB2 V1.0 ***************************************************************** VIDA/DB2 V1.0 IVP completed successfully ***************************************************************** Please press the RETURN key to continue: ****************************************************************** Performing VIDA2$LIVE_IVP for: VIDA/DB2 V1.0 ****************************************************************** Please press the RETURN key to continue: Please note that the Live IVP activates the VIDA Client for DB2 installation IVP. Refer to Section 2.1.3 for information on the installation IVP. 4.3.2 Reading the Informational Messages Once the Live IVP has been invoked, it displays a series of informational messages that explain about the installation IVP and explain how to use the Live IVP. You will now be asked several questions in order to set up the environment for the Live IVP. If you have already defined logical names which supply values required by VIDA Client, then you may use those names by answering YES or Y when asked if the environment has been set up. Otherwise, you will be prompted for VIDA Client for DB2 run-time parameters. NOTE: You will always be prompted for user account and password information. In the questions, the default response is shown in brackets, for example, [YES]. If you want to use the default response, press the RETURN key. For questions with no default response, press RETURN if you do not wish to supply a value. Please press the RETURN key to continue: 4-4 Running the Live Installation Verification Procedure 4.3.3 Answering the Live IVP Questions This section discusses the questions that the IVP displays. Appendix C contains a sample Live IVP showing how the questions can be answered. For more information on answering the following questions, refer to Chapter 2, VIDA Client for DB2 Data Access Parameters, in the VIDA Client for DB2 Handbook. Each question in the IVP is marked with an asterisk (*) at the beginning of the line. Some questions show the default response in brackets, for example [YES]. If you want to use the default response, press the RETURN key. 1 VIDA for DB2 Environment The Live IVP asks you to verify that the entire environ- ment for VIDA for DB2 is operational. Check with the IBM system manager to make sure all hardware and software components for VIDA Server for DB2 are working. NO is the default response to this question. * Is the environment set up to run VIDA2 ? (YES/NO) [NO]?: 2 CICS User Name The IVP asks for your CICS user name. This is your CICS user ID. See your CICS administrator for your CICS user name. If no name is required, take the none default. * Please type in CICS User Name [none]: 3 User Password The Live IVP now asks for your user password. This refers to your CICS password. Your CICS administrator supplies your user password. The default is none. * Please type in User Password [none]: 4 Server Password The server password refers to the CICS server password. The CICS server password is used to authenticate the connection to CICS. This password is supplied by your CICS administrator. * Please type in Server Password [none]: Running the Live Installation Verification Procedure 4-5 5 SNA Gateway Password The SNA Gateway Password authenticates access to the gateway. This password is supplied by the Gateway Administrator. * Please type in the SNA Gateway Password [none]: 6 SNA Gateway Node Name The IVP asks for the SNA gateway node name. This is the name of the gateway that VIDA Client for DB2 must use. The gateway administrator supplies this name. * Enter the SNA Gateway Node Name [none]: 7 Gateway Access Name The gateway access name identifies an access name that is defined in a gateway configuration file and contains a set of IBM access parameters. The gateway access name is supplied by the gateway administrator. * Enter the Gateway Access Name [none]: 8 Transaction Name for Degree2 Transactions This transaction ID identifies the CICS transaction ID needed to process transactions using the degree 2 (concurrency) option. The default is DEC2. This transaction ID is provided by the CICS administrator. * Enter Transaction ID for degree2 transactions [DEC2]: 9 Transaction ID for Degree3 Transactions This Transaction ID identifies the CICS transaction ID needed to process transactions using the degree 3 (consistency) option. The default is DEC3. This transaction ID is also provided by the CICS administrator. * Enter Transaction ID for degree3 transactions [DEC3]: 10 CICS Application Name The IVP asks you for the VTAM name of the CICS region. When the IVP asks for the application name, respond with the name supplied to you by the CICS administrator. * Enter the CICS Application Name [none]: 4-6 Running the Live Installation Verification Procedure 11 Gateway Circuit ID The Gateway Circuit ID identifies the name of the physical link from the gateway to the IBM host. The gateway administrator provides this ID. * Enter the Gateway Circuit ID [none]: 12 Gateway Session Number Next, the IVP requests the specific local session address to be used in communicating with the IBM host. The gateway administrator provides you with this number. * Enter the Gateway Session Number [none]: 13 Logon Mode Name Finally, the IVP requests the logon mode name. The logon mode name specifies a selected set of SNA protocol options. It is provided by the gateway administrator. * Enter the Logon mode name [none]: Once you complete the final question, the Live IVP responds by printing out the entire database name: **************************************** * * * The following is the database name * * * **************************************** "VIDA2_DATABASE" = "/TYPE=VIDA2/DATABASE=PERSONNL" (LNM$PROCESS_TABLE) 4.3.4 Completing the Live IVP The following message indicates that the Live IVP is complete: ****************************************************** VIDA/DB2 V1.0 LIVE IVP completed successfully ****************************************************** Running the Live Installation Verification Procedure 4-7 4.4 Error Recovery Errors can occur during the IVP. If the IVP fails, you see the following message: ************************************** VIDA/DB2 V1.0 LIVE IVP failed ************************************** The Live IVP fails if the run-time SQL query fails. If the run-time SQL query fails, the differences between the outputs are recorded in a file called VIDA2$LIVE_IVP.DIF. This file shows the differences between the run-time result file and the supplied benchmark file. The following message is displayed if the run-time SQL query fails: ***** RUN-TIME ONLY test failed ***** See VIDA2$LIVE_IVP.DIF for errors. In the event of an IVP failure, refer to the file called VIDA2$LIVE_IVP.RES. This file contains error messages explaining the reason of the SQL query failure. The file also describes the appropriate actions to take to correct the errors. 4-8 Running the Live Installation Verification Procedure A ________________________________________________________________ Sample Installation This appendix contains a sample installation of VIDA Client for DB2. This sample was run on a system that had no previous version of VIDA Client for DB2 installed. Depending on which layered products you have on your system, you might see additional messages and questions when you perform your installation. This sample installation was run under VMS Version 5.0-1. If you are installing under VMS Version 5.2, you will see a few variations from this sample. Refer to Section 2.2.2 for information on VMS Version 5.2 differences. The sample installation assumes that DECnet has been shut down, that no users are logged on to your system, and that OPTIONS N is specified to print the release notes. The Installation Verification Procedure (IVP) runs at the end of the installation. The sample VIDA installation procedure follows: $ SET DEFAULT SYS$UPDATE $ SHOW DEFAULT SYS$SYSROOT:[SYSUPD] $ @VMSINSTAL VIDA2010 MTA0: OPTIONS N VAX/VMS Software Product Installation Procedure V5.0-1 It is 30-AUG-1989 at 09:18. Enter a question mark (?) at any time for help. * Do you want to continue anyway [NO]? YES * Are you satisfied with the backup of your system disk [YES]? YES Sample Installation A-1 Please mount the first volume of the set on MTA0:. * Are you ready? YES %MOUNT-I-MOUNTED, VIDA2 MOUNTED ON _$$MTA0: (NODE1) The following products will be processed: VIDA2 V1.0 Beginning installation of VIDA2 V1.0 at 09:19 %VMSINSTAL-I-RESTORE, Restoring product saveset A ... Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. Copy release notes to SYS$HELP 5. Do not display, print or copy release notes * Select option [2]: 4 * Do you want to continue the installation? YES %VMSINSTAL-I-RELMOVED, The product's release notes have been successfully moved to SYS$HELP. ************************************************************* Installation procedures for: VIDA/DB2 V1.0 ************************************************************* ************************************************************* Checking system requirements ... ************************************************************* Product: VIDA Producer: DEC Version: 1.0 Release Date: 30-JUN-1989 * Does this product have an authorization key registered and loaded? ************************************************************* This installation requires the creation of the RDB$REMOTE account. You MUST choose a UIC and password for this account. PLEASE NOTE that your password for the RDB$REMOTE account and the network object RDBSERVER MUST be exactly the same. The password you supply for the RDB$REMOTE account will be used for the network object as well IF the account is created by this installation. ************************************************************** A-2 Sample Installation ************************************************************* The installation procedure will not proceed until you enter a valid user identification code (UIC) for the RDB$REMOTE account. ************************************************************** * Please enter UIC to be used for RDB$REMOTE account (e.g. [ggg,mmm]): [200,201] ************************************************************* The entire installation will FAIL if you do not enter a valid password for the RDB$REMOTE account. You will be given 3 chances to verify your password. This installation procedure requires at least 6 characters for the RDB$REMOTE password. Valid characters for a password are: A through Z a through z 0 through 9 $ (dollar sign) _ (underscore) As with the DCL SET PASSWORD command, your input will not appear on the terminal. And to protect against typing errors that are not seen when entering the password, you must enter the password twice. ************************************************************* * Please enter PASSWORD to be used for RDB$REMOTE account: VIDADB * Please verify the PASSWORD entered for RDB$REMOTE: VIDADB * Do you want to purge files replaced by this installation [YES]? YES * Do you want to run the IVP after the installation [YES]? YES ************************************************************* There are no more questions. The installation takes ap- proximately 5 minutes on a stand-alone VAX 8200. ************************************************************* Beginning installation ... ************************************************************* ************************************************************* Installing under VMS V5.0-1 - 30-AUG-1989 09:21 Sample Installation A-3 ************************************************************* %VMSINSTAL-I-RESTORE, Restoring product saveset B ... %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSTEST.VIDA2$TEST] ************************************************************* The VIDA2 IVP has been placed in SYS$COMMON:[SYSTEST.VIDA2$TEST]. You may run this procedure separately any time you wish. To execute it, type : $ SET DEF SYS$COMMON:[SYSTEST.VIDA2$TEST] $ @VIDA2$IVP ************************************************************* The live VIDA2 IVP has been placed in SYS$COMMON:[SYSTEST.VIDA2$TEST]. You may run this procedure separately after the environment has been set up. To execute it, type: $ SET DEF SYS$COMMON:[SYSTEST.VIDA2$TEST] $ @VIDA2$LIVE_IVP ************************************************************* ************************************************************* Adding VIDA2 help to the DCL help library ************************************************************* %VMSINSTAL-I-SYSDIR, This product creates a system disk directory VMI$ROOT:[RDB$REMOTE]. %VIDA2-I-ACCOUNT, This installation creates an account named RDB$REMOTE. RDBSERVER has been placed in the DECnet object database as number 35. ************************************************************* SYSTEM MANAGER: If your DECnet object database is not configured to be in the cluster common directory, then you will need to perform the following: In order to have remote access on another node which shares this cluster common root directory, you must insert RDBSERVER.EXE into that node's DECnet object database by: a) Logging into that node, and b) Invoking SYS$COMMON:[SYSMGR]RDBSERVER_NCP.COM. A-4 Sample Installation This command procedure inserts RDBSERVER into the node's permanent DECnet object database. This procedure only needs to be executed ONCE per node. This command procedure will prompt for a password for the object RDBSERVER. This password must match the password established for the account. ************************************************************* %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... ************************************************************* The VIDA Client for DB2 IVP verifies that all files are properly in place. It does not test the hardware link from the VAX to the IBM system, nor does it test the software link from VIDA Client for DB2 to VIDA Server for DB2. Once the VIDA Server for DB2 software has been installed on your IBM system and your communications environment has been set up, you should try running the VIDA2$LIVE_IVP. If the VIDA2$LIVE_IVP completes successfully, then everything is installed properly. ************************************************************* ************************************************************* Performing VIDA/DB2 IVP for: VIDA/DB2 V1.0 ************************************************************* ************************************************************* VIDA/DB2 V1.0 IVP completed successfully ************************************************************* Installation of VIDA2 V1.0 completed at 09:28 VMSINSTAL procedure done at 09:28 $ LO SYSTEM logged out at 30-AUG-1989 09:41:36.50 Sample Installation A-5 B ________________________________________________________________ Files Installed on Your System The following sections list the name of each file transferred to your system when you install VIDA Client for DB2. The sections divide files by the directories to which the installation procedure copies them. B.1 Files Transferred to SYS$SYSTEM The installation procedure transfers the following executable files to the directory SYS$COMMON:[SYSEXE]: RDB$REMOTE_LOGIN.COM The login command procedure for the RDB$SERVER account RDBSERVER.EXE Rdb/Remote Server image RDBSERVER.COM Rdb/Remote Server command file The command procedure starts the RDB server process to provide remote database access capability. B.2 Files Transferred to SYS$HELP The installation procedure transfers the following help files to the directory SYS$COMMON:[SYSHLP]: Files Installed on Your System B-1 RDB_MSG.DOC Documentation file for errors generated by the DIGITAL Standard Relational Interface (DSRI) DSRI error messages use the 3-letter facility code RDB. Print the file RDB_MSG.DOC when you want a hardcopy listing of the DSRI error messages. VIDA2$MESSAGE.DOC Documentation file for errors generated by the VIDA Client for DB2 software VIDA Client for DB2 error messages use the facility code VIDA2. Print the VIDA2$MESSAGE.DOC file when you want a hardcopy listing of all VIDA Client for DB2 error messages. VIDA2$HELP_DCL.HLP Source for the DCL help text that the installation procedure inserts into the library SYS$COMMON:[SYSHLP] If you want to customize the help on your system, or already have, you can edit this file and build a new help library. VIDA2$010.RELEASE_ VIDA for DB2 release notes NOTES The file that contains the VIDA for DB2 Version 1.0 release notes. B.3 Files Transferred to SYS$SHARE The installation procedure transfers the following library files to the directory SYS$COMMON:[SYSLIB]: B-2 Files Installed on Your System VIDA2$DMCS_TABLE.EXE Character set translation default VIDA for DB2 lets you use modified tables for translating between IBM character encoding (EBCDIC) and the character encoding used on VAX computers. This is the default translation table that implements a reversible translation from EBCDIC to the DIGITAL Multinational Character Set (DMCS) and back. VIDA2$DMCS_TABLE.MAR Source file for the preceding translation table You can edit this source file and build customized translation tables for your site. VIDA2$TRAPRE.MAR Source prefix file for the preceding translation table VIDA2$TRANS_ Command file for building translation TABLE.COM tables The installation procedure transfers the following shareable image files to the directory SYS$COMMON:[SYSLIB]. VIDA2SHR.EXE VIDA Client for DB2 shareable image The bulk of the VIDA Client for DB2 software resides in this shareable image. RDBSHR.EXE Generic (DSRI level) shared image This image processes all DIGITAL Standard Relational Interface (DSRI) calls and routes them to the appropriate subsystem (for example, routes calls to either Rdb/VMS or VIDA Client for DB2). RDMMSGSHR.EXE Rdb/VMS shareable image This file is a shareable, nonexecutable image of all Rdb/VMS error messages and is used by DSRI-compliant database products. Files Installed on Your System B-3 B.4 Files Transferred to SYS$MESSAGE The installation procedure transfers the following message files to the directory SYS$COMMON:[SYSMSG]: VIDA2$MESSAGE.EXE VIDA Client for DB2 message file image This image is activated along with VIDA2SHR and contains the run-time form of the error message text. VIDA_MESSAGE.EXE VIDA with IDMS/R message file image RDBMSGS.EXE Generic (DSRI level) message file RDMSMSG.EXE Rdb/VMS message file RDBBMSGS.EXE Rdb/ELN message file B.5 Files Transferred to SYS$COMMON:[SYSTEST] The installation procedure transfers the following IVP com- mand files to the directory SYS$COMMON:[SYSTEST.VIDA2$TEST]: VIDA2$IVP.COM VIDA Client for DB2 IVP command procedure You can run the IVP command procedure any time after VIDA Client for DB2 is installed to verify that the installation procedure installed the VIDA Client for DB2 software properly. VIDA2$IDENT.COMVIDA2 command procedure This command procedure simply provides the current VIDA Client for DB2 version number. VIDA2$LIVE_ VIDA for DB2 Live IVP command procedure IVP.COM You can run the LIVE IVP command procedure to verify that all components (hardware and software) of the VIDA for DB2 installation are properly working. B-4 Files Installed on Your System VIDA2$LIVE_ Live IVP benchmark file IVP.BMK This is the supplied benchmark file for the VIDA2 Live IVP. When VIDA2$LIVE_IVP.COM is run, the procedure's result file is compared to this benchmark file. Any differences between the files are reported in VIDA2$LIVE_ IVP.DIF. B.6 Files Transferred to SYS$MANAGER The installation procedure transfers the following command files to the directory SYS$MANAGER: RDBSERVER_NCP.COM Command procedure for RDB server process The command procedure inserts RDBSERVER objects into the DECnet object database for the node from which it is executed. VAXINFO$NETOBJ_INSERT.COM Command procedure The command procedure inserts objects into DECnet databases. B.7 File Transferred to SYS$COMMON The installation procedure transfers the following file to the directory named SYS$COMMON:[SYSMGR.VAXINFO$PRODUCTS]: VIDA2_ List of all files installed by VIDA Client for FILES.DAT DB2 Files Installed on Your System B-5 C ________________________________________________________________ Sample Live Installation Verification Procedure This appendix contains a sample run of the Live IVP. The sample Live IVP was run on a system that had no previous version of VIDA Client for DB2 installed. Depending on which layered products you have installed on your system, you might see additional messages and questions when you run the Live IVP. $ SET DEFAULT SYS$COMMON:[SYSTEST.VIDA2$TEST] $ @VIDA2$LIVE_IVP *************************************************************** * * * VIDA Client for DB2 Live IVP * * * * Note: This procedure must be run from the system test * * directory: SYS$TEST:[SYSTEST.VIDA2$TEST]. * * * * The VIDA2 Live IVP first verifies that all the VIDA2 * * files are in place. It then accesses the DB2 PERSONNL * * database (supplied with the VIDA Server for DB2 software), * * executes 2 queries, and compares the result with a * * supplied output file. Any differences in the outputs * * will cause this test to fail, and are reported in * * VIDA2$LIVE_IVP.DIF. The result of the queries is in * * VIDA2$LIVE_IVP.RES * * * *************************************************************** Please press the RETURN key to continue: **************************************************************** Sample Live Installation Verification Procedure C-1 The VIDA Client for DB2 IVP verifies that all files are properly in place. It does not test the hardware link from the VAX to the IBM system, nor does it test the software link from VIDA Client for DB2 to VIDA Server for DB2. Once the VIDA Server for DB2 software has been installed on your IBM system and your communications environment has been set up, you should try running the VIDA2$LIVE_IVP. If the VIDA2$LIVE_IVP completes successfully, then everything is installed properly. *************************************************************** ************************************************************** Performing VIDA/DB2 IVP for: VIDA/DB2 V1.0 ************************************************************** ************************************************************** VIDA/DB2 V1.0 IVP completed successfully ************************************************************** Please press the RETURN key to continue: ************************************************************** Performing VIDA2$LIVE_IVP IVP for: VIDA/DB2 V1.0 ************************************************************** Please press the RETURN key to continue: You will now be asked several questions in order to set up the environment for the Live IVP. If you have already defined logical names which supply values required by VIDA Client, then you may use those names by answering YES or Y when asked if the environment has been set up. Otherwise you will be prompted for VIDA Client for DB2 run-time parameters. NOTE: You will always be prompted for user account and password information. In the questions, the default response is shown in brackets, for example [YES]. If you want to use the default response, press the RETURN key. For questions with no default response, press RETURN if you do not wish to supply a value. Please press the RETURN key to continue: C-2 Sample Live Installation Verification Procedure * Is the environment set up to run VIDA2 (YES/NO) [NO]? YES * Please type in CICS User Name [none]: VIDA * Please type in User Password [none]: VIDADB * Please type in Server Password [none]: * Please type in SNA Gateway Password [none]: * Enter the SNA Gateway Node Name [none]: WICKET * Enter the Gateway Access Name [none]: CICSVIDA * Enter Transaction ID for degree2 transactions [DEC2]: TVXX * Enter Transaction ID for degree3 transactions [DEC3]: TVYY * Enter the CICS Application Name [none]: CICS * Enter the Gateway Circuit ID [none]: LC-1 * Enter the Gateway Session Number [none]: 28 * Enter the Logon mode name [none]: XL622048 *************************************** * * * The following is the database name * * * *************************************** "VIDA2_DATABASE" = "/TYPE=VIDA2/DATABASE=PERSONNL" (LNM$PROCESS_TABLE) ************************************************************* VIDA/DB2 V1.0 LIVE IVP completed successfully ************************************************************* Sample Live Installation Verification Procedure C-3