 

















                     DEC RdbAccess for
                     VAX_RMS_on_VMS________________________________
                     Installation Guide

                     Order Number: AA-PFF7A-TE


                     [0;1mMarch[m [0;1m1991[m

                     RdbAccess for VAX RMS emulates read-only relational
                     access to RMS data files and IBM VSAM data sets
                     through VAX SQL statements. The product emulates
                     relational access by associating data with data
                     definitions from the CDD/Plus data dictionary.
                     This guide describes how to install and maintain
                     RdbAccess for VAX RMS on a VMS system.





                     [0;1mRevision/Update[m [0;1mInformation:[m This is a new manual.

                     [0;1mOperating[m [0;1mSystem:[m            VMS Version 5.3 or
                                                  higher

                     [0;1mSoftware[m [0;1mVersion:[m            RdbAccess for VAX RMS
                                                  Version 1.0


                     [0;1mDigital[m [0;1mEquipment[m [0;1mCorporation[m
                     [0;1mMaynard,[m [0;1mMassachusetts[m

 






           __________________________________________________________
           [0;1mMarch[m [0;1m1991[m

           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 1991.

           All Rights Reserved.
           Printed in the U.S.A.

           The postpaid 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: CDA, CDD, DATATRIEVE, DDIF, DEC, DECalc,
           DECchart, DECdecision, DECnet, DECUS, DECwindows,
           DECwrite, DTIF, DX, LiveLink, MicroVAX, PDP, RALLY, Rdb
           /VMS, TEAMDATA, UNIBUS, VAX, VAX DBMS,
           VAX RMS, VAXcluster, VAXstation, VIDA, VMS, VT, WPS-PLUS,
           ULTRIX, and the DIGITAL logo.

           The following are third-party trademarks:
           IBM and OS/2 are registered trademarks of International
           Business Machines Corporation.
           MS-DOS is a registered trademark of Microsoft Corporation.

                                                               ZK5420

           This document is available on CDROM.

           This document was prepared using VAX DOCUMENT, Version 1.2

 


 











        ________________________________________________________________

                                                                 [0;1mPreface[m



              DEC RdbAccess for VAX RMS on VMS, referred to in this
              document as RdbAccess for VAX RMS, emulates read-
              only relational access to RMS data files and IBM VSAM
              data sets through VAX SQL statements. The product
              emulates relational access by associating data with data
              definitions from the CDD/Plus data dictionary.

        [0;1mPurpose[m [0;1mof[m [0;1mThis[m [0;1mGuide[m

              This guide describes how to install and maintain RdbAccess
              for VAX RMS on the VMS operating system. You should review
              the entire guide before you start the installation.

        [0;1mWho[m [0;1mShould[m [0;1mUse[m [0;1mThis[m [0;1mGuide[m

              This guide is for VMS system managers or others respon-
              sible for installing system software. To install the
              RdbAccess for VAX RMS software, you must have access to
              a privileged account such as the SYSTEM account, and you
              must be familiar with the VMS installation procedure,
              VMSINSTAL.COM.

        [0;1mStructure[m [0;1mof[m [0;1mThis[m [0;1mGuide[m

              The guide has three chapters and two appendixes.
              Chapter 1 describes installation prerequisites and
              pre-installation procedures. Chapter 2 describes the
              installation procedure. Chapter 3 describes required
              post-installation procedures. Appendix A shows a sample
              printout of an installation. Appendix B shows the files
              that are transferred to your system when you install
              RdbAccess for VAX RMS.


                                                                       v

 






     [0;1mFor[m [0;1mMore[m [0;1mInformation[m

           Refer to the following manual for more information about
           RdbAccess for
           VAX RMS:

           o  [0;4mDEC[m [0;4mRdbAccess[m [0;4mfor[m [0;4mVAX[m [0;4mRMS[m [0;4mon[m [0;4mVMS[m [0;4mUser's[m [0;4mGuide[m

           For more information about the VMSINSTAL command
           procedure, see one of the following manuals:

           o  [0;4mVMS[m [0;4mSystem[m [0;4mManager's[m [0;4mManual[m, in the VMS base documenta-
              tion set

           o  [0;4mGuide[m [0;4mto[m [0;4mSetting[m [0;4mUp[m [0;4ma[m [0;4mVMS[m [0;4mSystem[m, in the VMS system
              management kit

     [0;1mConventions[m

           The following conventions are used in this guide:

           <Return>        In procedures, key names are shown
                           enclosed to indicate that you press a
                           key on the keyboard.

           <Ctrl/x>        A sequence such as <Ctrl/x> indicates that
                           you must hold down the key labeled Ctrl
                           while you press another key or a pointing
                           device button.

           ()              In format descriptions, parentheses
                           indicate that, if you choose more than
                           one option, you must enclose the choices
                           in parentheses.

           []              In format descriptions, brackets indicate
                           that whatever is enclosed is optional;
                           you can select none, one, or all of the
                           choices.

           {}              In format descriptions, braces surround
                           a required choice of options; you must
                           choose one of the options listed.


     vi

 







              color           Color in examples indicates information
                              that you must enter from the keyboard. In
                              the Bookreader, information you must enter
                              from the keyboard is indicated by [0;1mboldface[m
                              text.

              [0;4mitalic[m [0;4mtext[m     Italic text represents information that
                              can vary in system messages (for example,
                              Internal error [0;4mnumber[m).

              UPPERCASE TEXT  Uppercase letters indicate that you must
                              enter a command (for example, enter OPEN
                              /READ). Uppercase letters also indicate
                              the name of a routine, the name of a file,
                              the name of a file protection code, or the
                              abbreviation of a system privilege.

              RdbAccess for   The term RdbAccess for VAX RMS refers to
              VAX RMS         the RdbAccess for VAX RMS[TM] software.

              SQL             The term SQL refers to the VAX Structured
                              Query Language software.

              RMS             The term RMS refers to the VAX Record
                              Management Services software.

              Rdb/VMS         The term Rdb/VMS refers to the VAX Rdb/VMS
                              software.

              CDD/Plus        The term CDD/Plus refers to the VAX
                              CDD/Plus software.













                                                                     vii

 









                                                                       [0;1m1[m
        ________________________________________________________________

                                              [0;1mPreparing[m [0;1mfor[m [0;1mInstallation[m



              This chapter describes tasks that you must complete before
              installing RdbAccess for VAX RMS. Installing RdbAccess
              for VAX RMS is similar to installing other VMS layered
              products. You must do the following:

              o  Take an inventory of the software distribution kit.

              o  Make sure that your system has the prerequisite
                 hardware, and that it has enough memory and available
                 disk space to install and run RdbAccess for VAX RMS.

              o  Make sure that your system has the required VMS
                 operating system components and the prerequisite
                 software.

              o  If you are installing on a VAXcluster, decide how best
                 to install RdbAccess for VAX RMS, depending on your
                 configuration.

              o  Register and load your RdbAccess for VAX RMS license.

              o  Check that the account you use to install the software
                 has the required privileges and quotas.

              o  Decide what values your VMS system parameters should
                 have.

              o  Back up your system disk.

              o  Advise your users when the installation will take
                 place and how long it will take. The full installation
                 takes approximately 15 minutes on a stand-alone VAX
                 8200. Your time may vary depending on your system
                 configuration and the type of installation media.

                                          Preparing for Installation [0;1m1-1[m

 






           Once you have prepared your system, you can then perform
           the installation procedure as described in Chapter 2, and
           any necessary post-installation procedures as described in
           Chapter 3.

     [0;1m1.1[m [0;1mChecking[m [0;1mthe[m [0;1mDistribution[m [0;1mKit[m

           Each RdbAccess for VAX RMS distribution kit contains:

           o  Bill of Materials and the Indented Bills Report

              Please read the Bill of Materials enclosed in the
              transparent plastic envelope. Check to see that all
              items listed there are in your kit. If any items are
              missing, contact your Digital representative.

           o  Distribution Media, labeled NSDS

           o  Software License, labeled RDBACCESS-RMS

           o  Documentation

              If you ordered a media-only kit, you have just the [0;4mDEC[m
              [0;4mRdbAccess[m [0;4mfor[m [0;4mVAX[m [0;4mRMS[m [0;4mon[m [0;4mVMS[m [0;4mInstallation[m [0;4mGuide[m.

              If you ordered a full kit or a documentation-only kit,
              you have an RdbAccess for VAX RMS documentation set,
              which includes the following manuals:

                 [0;4mDEC[m [0;4mRdbAccess[m [0;4mfor[m [0;4mVAX[m [0;4mRMS[m [0;4mon[m [0;4mVMS[m [0;4mUser's[m [0;4mGuide[m
                 [0;4mDEC[m [0;4mRdbAccess[m [0;4mfor[m [0;4mVAX[m [0;4mRMS[m [0;4mon[m [0;4mVMS[m [0;4mInstallation[m [0;4mGuide[m

           o  Software Product Description (SPD)

              The SPD provides an overview of RdbAccess for VAX RMS
              and its features.

           o  Software Performance Report (SPR)

              Use this form to report any problems with RdbAccess
              for VAX RMS (provided you have purchased warranty
              services).

     [0;1m1.2[m [0;1mPrerequisite[m [0;1mHardware[m

           RdbAccess for VAX RMS runs on VAX, MicroVAX, VAXstation
           or VAXserver configurations as specified in the System
           Support Addendum, 32.88.00-A.

     [0;1m1-2[m Preparing for Installation

 



                                               [0;1m1.3[m [0;1mPrerequisite[m [0;1mSoftware[m


        [0;1m1.3[m [0;1mPrerequisite[m [0;1mSoftware[m

              To install RdbAccess for VAX RMS, you must have:

              1. A valid VMS operating system configuration running VMS
                 Version 5.3 or higher

              2. Your RdbAccess for VAX RMS software license registered

                 See Section 1.5 for more information.



































                                          Preparing for Installation [0;1m1-3[m

 



     [0;1m1.3[m [0;1mPrerequisite[m [0;1mSoftware[m


           3. Rdb/VMS Version 4.0 or higher

           4. VAX CDD/Plus Version 4.2 or higher

           For more information, refer to your Software Product
           Description, 32.88.00, and your System Support Addendum,
           32.88.00-A.

     [0;1m1.4[m [0;1mRequired[m [0;1mOperating[m [0;1mSystem[m [0;1mComponents[m

           RdbAccess for VAX RMS requires the following VMS Version
           5.3 components:

           o  VMS required files

           o  Network support

           o  Programming support

           o  System programming support

           o  Secure user's environment

           o  Utilities

           If your system does not meet these requirements, the
           installation will fail. You must install the required
           software using VMSTAILOR before performing the RdbAccess
           for VAX RMS installation.

     [0;1m1.5[m [0;1mRegistering[m [0;1mYour[m [0;1mLicense[m

           You must register and load your RdbAccess for VAX RMS
           software license. The information you need is in the
           Product Authorization Key (PAK) shipped with the product.
           The PAK is a paper certificate that contains data about
           your license.

           You must register the license before you install RdbAccess
           for VAX RMS. If you do not, you are informed during the
           installation procedure that you have not registered it,
           and the installation fails.

              ________________________[0;1mNote[m ________________________

              If you are re-installing RdbAccess for VAX RMS
              Version 1.0, you do not need to re-register your
              license. Your current license is still active.

              _____________________________________________________

     [0;1m1-4[m Preparing for Installation

 



                                            [0;1m1.5[m [0;1mRegistering[m [0;1mYour[m [0;1mLicense[m


              To register the license for the initial installation,
              first log in to a privileged account such as the system
              manager's account, SYSTEM. Then use the License Management
              Facility to perform the registration, choosing one of
              the following procedures (the second method is faster for
              experienced users):

              o  Invoke the SYS$UPDATE:VMSLICENSE.COM procedure. When
                 prompted for information, respond with data from your
                 Product Authorization Key (PAK).

              o  Issue the DCL command LICENSE REGISTER with the
                 appropriate qualifiers that correspond to information
                 on the PAK.

              If you plan to use RdbAccess for VAX RMS on more than one
              node in a VAXcluster, you must perform a LICENSE LOAD on
              the other nodes after you complete this installation. See
              Section 3.2 for more information.

              For complete information on using the License Management
              Facility, see your VMS documentation set.

        [0;1m1.6[m [0;1mVAXcluster[m [0;1mConsiderations[m

              You can install RdbAccess for VAX RMS on a VAXcluster.

              In a common-environment VAXcluster, you can install
              RdbAccess for VAX RMS on the VAXcluster boot node. This
              allows more than one VAX processor to share the same
              RdbAccess for VAX RMS software.

              In a multiple-system VAXcluster, you can install RdbAccess
              for VAX RMS on each system disk in the cluster.

              You must make sure that each node where you plan to
              install or run RdbAccess for VAX RMS meets the minimum
              system parameter value requirements. See Section 1.7.4 for
              a list of required system parameter values.

              After you install RdbAccess for VAX RMS, you must run
              the RdbAccess for VAX RMS startup command procedure
              (SYS$STARTUP:NSDS$STARTUP.COM) and load the software
              license on every cluster node where you want to run
              RdbAccess for VAX RMS. See Section 3.1 and Section 3.2
              for more information.

                                          Preparing for Installation [0;1m1-5[m

 



     [0;1m1.7[m [0;1mPreparing[m [0;1mYour[m [0;1mSystem[m [0;1mand[m [0;1mthe[m [0;1mInstalling[m [0;1mAccount[m


     [0;1m1.7[m [0;1mPreparing[m [0;1mYour[m [0;1mSystem[m [0;1mand[m [0;1mthe[m [0;1mInstalling[m [0;1mAccount[m

           This section tells you which characteristics of your
           system and installing account you need to check before
           you install RdbAccess for VAX RMS. These characteristics
           include:

           o  Account privileges

           o  Account quotas

           o  Disk space requirements

           o  System parameters

           You must adjust those characteristics that do not match
           the minimum values required for installing and running
           RdbAccess for VAX RMS.

     [0;1m1.7.1[m [0;1mChecking[m [0;1mPrivileges[m [0;1mof[m [0;1mthe[m [0;1mInstalling[m [0;1mAccount[m

           The account you use to install RdbAccess for VAX RMS must
           have the user privilege SETPRV. As one of the first
           actions, the VMSINSTAL command procedure grants all
           privileges (except BYPASS) to the process that invokes
           it. This command succeeds only if the account has SETPRV.

           On most systems, the SYSTEM account has SETPRV and is
           used to install software. The procedures described in this
           installation guide refer to the SYSTEM account, but they
           are the same for any account with SETPRV.

     [0;1m1.7.2[m [0;1mChecking[m [0;1mQuotas[m [0;1mof[m [0;1mthe[m [0;1mInstalling[m [0;1mAccount[m

           The installing account must have sufficient quotas
           to perform the installation and run the Installation
           Verification Procedure (IVP). Table 1-1 summarizes the
           minimum account quotas required.

           [0;1mTable[m_[0;1m1-1[m_[0;1mMinimum[m_[0;1mInstalling[m_[0;1mAccount[m_[0;1mQuotas[m_______________

           [0;1mAccount[m_[0;1mQuota[m____[0;1mValue[m_______[0;1mDescription[m__________________

           PGFLQUO__________20,000______Paging_file_limit____________

           Account quotas are stored in the file SYSUAF.DAT. Use the
           VMS Authorize Utility to verify and change user account
           quotas. Follow these steps:

     [0;1m1-6[m Preparing for Installation

 



                    [0;1m1.7[m [0;1mPreparing[m [0;1mYour[m [0;1mSystem[m [0;1mand[m [0;1mthe[m [0;1mInstalling[m [0;1mAccount[m


              1. Set your directory to SYS$SYSTEM and then run AUTHORIZE
                 as follows:

                 $ SET DEFAULT SYS$SYSTEM
                 $ RUN AUTHORIZE
                 UAF>

              2. At the AUTHORIZE prompt (UAF>), use the SHOW command
                 with an account name to check your account. For
                 example:

                 UAF> SHOW SMITH

              3. To change a quota, use the MODIFY command at the UAF>
                 prompt. The MODIFY command uses the following format:

                 MODIFY account-name /quota-name=nnnn

                 For example, to change the PGFLQUO quota to 20,000
                 for the SMITH account, then exit from the Authorize
                 Utility, you would enter the following:

                 UAF> MODIFY SMITH /PGFLQUO=20000
                 UAF> EXIT

              After you exit from the utility, the VMS system displays
              messages indicating whether 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 [0;4mGuide[m [0;4mto[m
              [0;4mSetting[m [0;4mUp[m [0;4ma[m [0;4mVMS[m [0;4mSystem[m.

        [0;1m1.7.3[m [0;1mSystem[m [0;1mDisk[m [0;1mSpace[m [0;1mRequirements[m

              Your system disk must have sufficient disk storage space
              to accommodate the installation. Table 1-2 lists the
              required free disk blocks.






                                          Preparing for Installation [0;1m1-7[m

 



     [0;1m1.7[m [0;1mPreparing[m [0;1mYour[m [0;1mSystem[m [0;1mand[m [0;1mthe[m [0;1mInstalling[m [0;1mAccount[m


           [0;1mTable[m_[0;1m1-2[m_[0;1mSystem[m_[0;1mDisk[m_[0;1mRequirements[m________________________

           [0;1mInstallation[m
           [0;1mCondition[m________[0;1mBlocks[m___________________________________

           To install       3000

           To_run___________2000_____________________________________

           Use the DCL command SHOW DEVICE to determine the number
           of free blocks that are available on the system disk, as
           follows:

           $ SHOW DEVICE SYS$SYSDEVICE

           If the disk does not have enough free blocks, delete
           unnecessary files to provide the space required.

     [0;1m1.7.4[m [0;1mSystem[m [0;1mParameter[m [0;1mValues[m

           Table 1-3 lists the minimum system parameter values
           required for RdbAccess for VAX RMS installation and use.
           If your parameters are higher, do not lower them. Other
           applications on your system may require higher values than
           these minimum values.

           On a VAXcluster, you must adjust not only the system
           parameters of nodes on which you install RdbAccess for
           VAX RMS, but also the nodes on which you intend to run
           RdbAccess for VAX RMS.

           [0;1mTable[m_[0;1m1-3[m_[0;1mRequired[m_[0;1mMinimum[m_[0;1mSystem[m_[0;1mParameter[m_[0;1mValues[m________

           [0;1mSystem[m_[0;1mParameter[m____[0;1mMinimum[m_[0;1mValue[m_________________________

           GBLPAGES            186 (unused global pages)

           GBLSECTIONS         7 (unused global sections)

           VIRTUALPAGECNT______20,000________________________________





     [0;1m1-8[m Preparing for Installation

 



                    [0;1m1.7[m [0;1mPreparing[m [0;1mYour[m [0;1mSystem[m [0;1mand[m [0;1mthe[m [0;1mInstalling[m [0;1mAccount[m


        [0;1m1.7.4.1[m [0;1mChecking[m [0;1mParameter[m [0;1mValues[m

              To check the value of a system parameter, enter the
              following command at the DCL prompt:

              $ RUN SYS$SYSTEM:SYSGEN
              SYSGEN>

              At the SYSGEN> prompt, use the SHOW command to display the
              value of each system parameter. The value displayed in the
              Current column should equal or exceed the value of each
              parameter listed in Table 1-3. For example, the following
              command displays the value for the VIRTUALPAGECNT system
              parameter:

              SYSGEN> SHOW VIRTUALPAGECNT

              After you finish checking parameter values, use the EXIT
              command to return to DCL level.

        [0;1m1.7.4.2[m [0;1mCalculating[m [0;1mGBLPAGES[m [0;1mand[m [0;1mGBLSECTIONS[m [0;1mParameter[m [0;1mValues[m

              The values for GBLPAGES and GBLSECTIONS in Table 1-3
              indicate that you must have at least 186 unused global
              pages and 7 unused global sections available for the
              installation.

              To calculate the number of unused global pages and global
              sections on your system, perform these steps:

              1. Use the DCL F$GETSYI lexical function to determine the
                 number of free global pages and global sections:

                 $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES")
                 $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS")

              2. If the number of unused global pages or global sections
                 is less than the number specified in Table 1-3, you
                 must increase the value using the AUTOGEN command
                 procedure, as shown in Section 1.7.4.3.





                                          Preparing for Installation [0;1m1-9[m

 



     [0;1m1.7[m [0;1mPreparing[m [0;1mYour[m [0;1mSystem[m [0;1mand[m [0;1mthe[m [0;1mInstalling[m [0;1mAccount[m


     [0;1m1.7.4.3[m [0;1mChanging[m [0;1mParameter[m [0;1mValues[m [0;1mwith[m [0;1mAUTOGEN[m

           Use the AUTOGEN command procedure to change system
           parameters. To change system parameters with AUTOGEN:

           1. Edit the following file:

              SYS$SYSTEM:MODPARAMS.DAT

              For example, to increase the setting for the GBLPAGES
              system parameter by 2000, add this line to the file:

              ADD_GBLPAGES = 2000

           2. Run the AUTOGEN procedure to recalculate your system
              parameters and reboot the system. Enter the following
              command at the DCL prompt:

              $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT

              When you specify REBOOT, AUTOGEN performs an automatic
              system shutdown and reboot. Any users logged on to
              the system are immediately disconnected during the
              shutdown. The automatic reboot puts the new parameter
              values into effect.

              AUTOGEN 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
              parameter on the AUTOGEN command line as well. For
              example:

              $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT NOFEEDBACK

           For more information about using AUTOGEN, see the
           instructions on modifying system parameters in the [0;4mGuide[m
           [0;4mto[m [0;4mSetting[m [0;4mUp[m [0;4ma[m [0;4mVMS[m [0;4mSystem[m.

     [0;1m1.8[m [0;1mBacking[m [0;1mUp[m [0;1mYour[m [0;1mSystem[m [0;1mDisk[m

           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. If a system failure occurs at a critical point
           during the installation, some of the files could be
           corrupted. Therefore, you should back up your system disk
           before attempting any software installation.

     [0;1m1-10[m Preparing for Installation

 



                                         [0;1m1.8[m [0;1mBacking[m [0;1mUp[m [0;1mYour[m [0;1mSystem[m [0;1mDisk[m


              For more information on backing up your system disk,
              see the section on the Backup Utility in the [0;4mGuide[m [0;4mto[m
              [0;4mMaintaining[m [0;4ma[m [0;4mVMS[m [0;4mSystem[m.

        [0;1m1.9[m [0;1mDetermining[m [0;1mand[m [0;1mReporting[m [0;1mProblems[m

              If you encounter a problem while using RdbAccess for VAX
              RMS, report it to Digital. Depending on the nature of the
              problem and the type of support you have, you can take one
              of the following actions:

              o  Call Digital if your software contract or warranty
                 agreement entitles you to telephone support.

              o  Submit a Software Performance Report (SPR).

              o  Fill out and submit a Reader's Comments form if the
                 problem has to do with the RdbAccess for VAX RMS
                 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 number
                 and page number.

              Review the Software Product Description (SPD) and Warranty
              Addendum for an explanation of your 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.

        [0;1m1.10[m [0;1mPre-Installation[m [0;1mCheck[m [0;1mList[m

              Table 1-4 summarizes the tasks you must perform before
              installing RdbAccess for VAX RMS. Check to make sure that
              you have performed all these tasks before proceeding with
              the installation.









                                         Preparing for Installation [0;1m1-11[m

 



     [0;1m1.10[m [0;1mPre-Installation[m [0;1mCheck[m [0;1mList[m


           [0;1mTable[m_[0;1m1-4[m_[0;1mPre-Installation[m_[0;1mCheck[m_[0;1mList[m_____________________

           [0;1mTask[m____________________________[0;1mFor[m_[0;1mMore[m_[0;1mInformation[m______

           Check that you have the         See Section 1.2 and
           prerequisite hardware and       Section 1.3
           software

           Register and load your license  See Section 1.5

           Check privileges and quotas of  See Section 1.7.1 and
           the installing account          Section 1.7.2

           Check that you have enough      See Section 1.7.3
           disk space

           Check system parameters         See Section 1.7.4

           Back_up_your_system_disk________See_Section_1.8___________


























     [0;1m1-12[m Preparing for Installation

 









                                                                       [0;1m2[m
        ________________________________________________________________

                                        [0;1mInstalling[m [0;1mRdbAccess[m [0;1mfor[m [0;1mVAX[m [0;1mRMS[m



              This chapter describes the procedure for installing
              RdbAccess for VAX RMS and running the Installation
              Verification Procedure (IVP).

              Before you begin installing RdbAccess for VAX RMS, make
              sure that your system meets the requirements outlined in
              Chapter 1.

              The full installation takes approximately 15 minutes on a
              stand-alone
              VAX 8200. Your time may vary depending on the configu-
              ration of your system, the choices you make during the
              installation, and the type of media you use.

        [0;1m2.1[m [0;1mRunning[m [0;1mthe[m [0;1mVMSINSTAL[m [0;1mCommand[m [0;1mProcedure[m

              Use the VMSINSTAL command procedure to install RdbAccess
              for VAX RMS. For more information about VMSINSTAL, refer
              to the following books in your VMS documentation set:

              o  The [0;4mVMS[m [0;4mSystem[m [0;4mManager's[m [0;4mManual[m, in the VMS base
                 documentation set

              o  The [0;4mGuide[m [0;4mto[m [0;4mSetting[m [0;4mUp[m [0;4ma[m [0;4mVMS[m [0;4mSystem[m, in the VMS system
                 management subkit.

              If VMSINSTAL detects a problem during the installation
              procedure, it notifies you and asks if you want to
              continue. To stop the installation and correct the
              problem, enter NO or press RETURN. After you have made
              the correction, you can restart the installation.

              To stop the installation procedure at any time, press
              Ctrl/Y. The installation procedure deletes all the files
              it has created up to that point and exits. You can then
              restart the installation.

                                    Installing RdbAccess for VAX RMS [0;1m2-1[m

 



     [0;1m2.1[m [0;1mRunning[m [0;1mthe[m [0;1mVMSINSTAL[m [0;1mCommand[m [0;1mProcedure[m


           Follow these steps to install RdbAccess for VAX RMS:

           1. [0;1mLog[m [0;1min[m [0;1mto[m [0;1mthe[m [0;1mSYSTEM[m [0;1maccount.[m

              Log in at the operator's console terminal under the
              system manager's account, SYSTEM.

           2. [0;1mNotify[m [0;1mthe[m [0;1musers.[m

              Send a message requesting that all users log out. Use
              the DCL REPLY command to inform users of the schedule
              for the installation. Use the SET LOGINS command to
              prevent others from logging in:

              $ REPLY/USER "Installation starting in 5 minutes. Please log out."
              $ SET LOGINS/INTERACTIVE=0

           3. [0;1mInvoke[m [0;1mVMSINSTAL.[m

              Enter the following command line to run VMSINSTAL.COM:

              $ @SYS$UPDATE:VMSINSTAL NSDS ddcu: OPTIONS N

              where:

              o  [0;4m@SYS$UPDATE:VMSINSTAL[m invokes VMSINSTAL

              o  [0;4mNSDS[m is the save set name for the RdbAccess for VAX
                 RMS software

              o  [0;4mddcu:[m is the device specification for the distribu-
                 tion medium, for example, MUA0:.

              o  [0;4mOPTIONS[m [0;4mN[m is an optional parameter indicating that
                 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. Digital
                 recommends that you review the release notes before
                 proceeding with the installation.

              After you invoke VMSINSTAL, you see the following
              message:

                      VAX/VMS Software Product Installation Procedure V5.3

              It is 07-JAN-1991 at 13:51

              Enter a question mark (?) at any time for help.

           4. [0;1mAnswer[m [0;1mthe[m [0;1mbackup[m [0;1mquestion.[m

     [0;1m2-2[m Installing RdbAccess for VAX RMS

 



                             [0;1m2.1[m [0;1mRunning[m [0;1mthe[m [0;1mVMSINSTAL[m [0;1mCommand[m [0;1mProcedure[m


                 The installation procedure asks if you have backed up
                 your system disk:

                 * Are you satisfied with the backup of your system disk [YES]?

                 If you have not backed up your system disk, you should
                 not continue with the installation until you do so.
                 If you need to back up the system disk, enter NO.
                 VMSINSTAL exits and returns you to the DCL prompt.
                 Back up your system disk, and then start VMSINSTAL
                 again.

                 If you have already backed up the system disk, press
                 RETURN to continue.

              5. [0;1mMount[m [0;1mthe[m [0;1mmedia.[m

                 You receive instructions to mount the distribution
                 medium on the device you specified when you invoked
                 VMSINSTAL (MUA0: in this example):

                 Please mount the first volume of the set on MUA0:.
                 * Are you ready?

                 Mount the distribution medium and enter YES to indicate
                 that you are ready to continue.

                 The following messages appear on your terminal:

                 %MOUNT-I-MOUNTED,  NSDS mounted on _MUA0:

                 The following products will be processed:

                   NSDS V1.0

                         Beginning installation of NSDS V1.0 at 13:51

                 %VMSINSTAL-I-RESTORE, Restoring product save set A...

              6. [0;1mPrint[m [0;1mand[m [0;1mread[m [0;1mthe[m [0;1mRelease[m [0;1mNotes.[m

                 If you specified OPTIONS N when you invoked VMSINSTAL,
                 you are now asked to choose one of the four options for
                 reviewing the Release Notes:

                                    Installing RdbAccess for VAX RMS [0;1m2-3[m

 



     [0;1m2.1[m [0;1mRunning[m [0;1mthe[m [0;1mVMSINSTAL[m [0;1mCommand[m [0;1mProcedure[m


              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]:

              Review the Release Notes in case they contain any
              information about changes in the installation
              procedures. Selecting option 2 prints a copy of the
              Release Notes.

              You are prompted for a print queue:

              * Queue name [SYS$PRINT]:

              Press RETURN to print the Release Notes on SYS$PRINT,
              or type a different queue name and press RETURN. You
              receive a message similar to the following:

              Job 810 (queue SYS$PRINT, entry 1295) started on SYS$PRINT

              If you selected options 1 or 3, the Release Notes are
              displayed.

















     [0;1m2-4[m Installing RdbAccess for VAX RMS

 



                             [0;1m2.1[m [0;1mRunning[m [0;1mthe[m [0;1mVMSINSTAL[m [0;1mCommand[m [0;1mProcedure[m


              7. [0;1mDecide[m [0;1mwhether[m [0;1mor[m [0;1mnot[m [0;1mto[m [0;1mcontinue.[m

                 The installation procedure asks if you want to
                 continue:

                  * Do you want to continue the installation? [NO]?

                 %VMSINSTAL-I-RELMOVED, The product's release notes have been
                 successfully moved to SYS$HELP.

                 Enter YES to continue. Otherwise, press RETURN. In
                 either case, the Release Notes are moved to the
                 SYS$HELP directory. The Release Notes are contained
                 in the following file, which you may read or print
                 later:

                 SYS$HELP:NSDS010.RELEASE_NOTES.

                 You then see the following message:

                 *******************************************************

                 Installation procedures for: NSDS V1.0

                 *******************************************************

                 Checking system requirements ...

              8. [0;1mAnswer[m [0;1mthe[m [0;1mlicense[m [0;1mregistration[m [0;1mquestion.[m

                 The installation procedure asks if you have registered
                 a RdbAccess for VAX RMS product authorization key,
                 using the License Management Facility (LMF):

                         Product:      RDBACCESS-RMS
                         Producer:     DEC
                         Version:      1.0
                         Release Date: 1-JAN-1991

                  * Does this product have an authorization key registered and loaded?

                 You must have registered and loaded the product
                 authorization key or the installation fails. Enter YES
                 if your PAK is registered and loaded. The installation
                 then proceeds. If you enter NO, the installation
                 procedure exits and returns you to the DCL prompt.
                 See Section 1.5 for information about registering your
                 product authorization key.

                                    Installing RdbAccess for VAX RMS [0;1m2-5[m

 



     [0;1m2.1[m [0;1mRunning[m [0;1mthe[m [0;1mVMSINSTAL[m [0;1mCommand[m [0;1mProcedure[m


              ________________________[0;1mNote[m ________________________

              If you are re-installing RdbAccess for VAX RMS
              Version 1.0, you do not need to re-register your
              license. Your current license is still active.

              _____________________________________________________






































     [0;1m2-6[m Installing RdbAccess for VAX RMS

 



                             [0;1m2.1[m [0;1mRunning[m [0;1mthe[m [0;1mVMSINSTAL[m [0;1mCommand[m [0;1mProcedure[m


              9. [0;1mDecide[m [0;1mwhether[m [0;1mor[m [0;1mnot[m [0;1mto[m [0;1mpurge[m [0;1mfiles.[m

                 The installation procedure asks if you want to purge
                 (delete) old versions of files replaced by this
                 installation:

                  * Do you want to purge files replaced by this installation [YES]?

                 Purging is recommended. Press RETURN to purge the old
                 files. However, if you need to keep files from the
                 previous version, enter NO.

              10.[0;1mDecide[m [0;1mwhether[m [0;1mor[m [0;1mnot[m [0;1mto[m [0;1mrun[m [0;1mthe[m [0;1mIVP.[m

                 The installation procedure asks if you want to run the
                 Installation Verification Procedure (IVP):

                 * Do you want to run the IVP after the installation [YES]?

                 The RdbAccess for VAX RMS IVP checks to be sure the
                 installation is successful. Digital recommends that you
                 run the IVP. Press RETURN.

              11.[0;1mCheck[m [0;1minformational[m [0;1mmessages.[m

                 The installation procedure displays a series of
                 messages as it performs the rest of the installation:

                   ********************************************************

                   There are no more questions. The installation takes
                   approximately 10 minutes on a stand-alone VAX 8200.

                   ********************************************************

                   Beginning installation ...

                   ********************************************************

                   Installing under VMS V5.3 - 07-JAN-1991 13:56

                   ********************************************************

                 %VMSINSTAL-I-SYSDIR, This product creates system disk directory
                      VMI$ROOT:[SYSTEST.NSDS]

                   ********************************************************

                   The NSDS$STARTUP.COM file has been placed in
                   SYS$STARTUP:NSDS$STARTUP.COM.  The following line
                   should be placed in your system startup file.

                                    Installing RdbAccess for VAX RMS [0;1m2-7[m

 



     [0;1m2.1[m [0;1mRunning[m [0;1mthe[m [0;1mVMSINSTAL[m [0;1mCommand[m [0;1mProcedure[m


                $ @SYS$STARTUP:NSDS$STARTUP.COM

                *************************************************************










































     [0;1m2-8[m Installing RdbAccess for VAX RMS

 



                             [0;1m2.1[m [0;1mRunning[m [0;1mthe[m [0;1mVMSINSTAL[m [0;1mCommand[m [0;1mProcedure[m


                   ********************************************************

                   The NSDS IVP file has been placed in SYS$COMMON:[SYSTEST.NSDS$IVP].
                   You may run this procedure separately any time you wish. To
                   execute it, type:

                   $ SET DEFAULT SYS$COMMON:[SYSTEST.NSDS$IVP]
                   $ @NSDS$IVP

                   ********************************************************

                   Adding RdbAccess_RMS help to the DCL help library

                   ********************************************************

                   ********************************************************

                   The qualifier LGICMD for the RDB$REMOTE account in SYSUAF
                   is modified by this installation.

                   ********************************************************

              12.[0;1mCheck[m [0;1mRdb/VMS[m [0;1mmessages.[m

                 The RdbAccess for VAX RMS kit contains some Rdb/VMS
                 files. The installation procedure checks to make sure
                 you have the latest version of these files and replaces
                 them if necessary. See Appendix B for a full list of
                 the Rdb/VMS files.

                 If your system has the latest version of the Rdb/VMS
                 files, you see the following messages:

          ********************************************************

        %NSDS-I-NOTINSTALLED, VMI$KWD:RDBBMSGS.EXE was not installed by this kit
        %NSDS-I-REASON, Image ident version of new file is the same as current file
        %NSDS-I-NOTINSTALLED, VMI$KWD:VIDA_MESSAGE.EXE was not installed by this kit
        %NSDS-I-REASON, Image ident version of new file is the same as current file
        %NSDS-I-NOTINSTALLED, VMI$KWD:RDMSMSG.EXE was not installed by this kit
        %NSDS-I-REASON, Image ident version of new file is older than current file
        %NSDS-I-NOTINSTALLED, VMI$KWD:RDMMSGSHR.EXE was not installed by this kit
        %NSDS-I-REASON, Image ident version of new file is older than current file

                 After transferring the Rdb/VMS files, the installation
                 procedure moves all files to their directories.

        %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories.

                                    Installing RdbAccess for VAX RMS [0;1m2-9[m

 



     [0;1m2.1[m [0;1mRunning[m [0;1mthe[m [0;1mVMSINSTAL[m [0;1mCommand[m [0;1mProcedure[m


           13.[0;1mRun[m [0;1mthe[m [0;1mRdbAccess[m [0;1mfor[m [0;1mVAX[m [0;1mRMS[m [0;1mIVP.[m

              The installation procedure runs the RdbAccess for VAX
              RMS Installation Verification Procedure:

                ********************************************************

                The NSDS IVP verifies that all files are properly in place and that
                VAX SQL commands can be executed on RMS files.

                ********************************************************

                ********************************************************

                NSDS V1.0 IVP completed successfully

                ********************************************************

           14.[0;1mEnd[m [0;1mthe[m [0;1minstallation[m [0;1mprocedure.[m

              The installation procedure ends automatically with the
              following messages:

                      Installation of NSDS V1.0 completed at 14:06

                      VMSINSTAL procedure done at 14:06

           15.[0;1mMake[m [0;1mthe[m [0;1msystem[m [0;1mavailable[m [0;1mto[m [0;1musers.[m

              After the installation completes successfully, you
              should reset system logins to your system default (64
              in this example). Then send a message to all users
              stating that the system is again available. Use the
              following DCL commands:

              $ SET LOGINS/INTERACTIVE=64
              $ REPLY/USER "Installation complete. System is ready for use."








     [0;1m2-10[m Installing RdbAccess for VAX RMS

 









                                                                       [0;1m3[m
        ________________________________________________________________

                                            [0;1mPost-Installation[m [0;1mProcedures[m



              This chapter describes tasks that you must complete after
              RdbAccess for VAX RMS is installed.

        [0;1m3.1[m [0;1mEditing[m [0;1mthe[m [0;1mSystem[m [0;1mStartup[m [0;1mFile[m

              After the installation is complete, you must edit the
              system startup and shutdown files for all nodes that will
              be running RdbAccess for VAX RMS.

              Add the following line to your system startup file,
              SYS$MANAGER:SYSTARTUP_V5.COM:

              $ @SYS$STARTUP:NSDS$STARTUP.COM

        [0;1m3.2[m [0;1mActivating[m [0;1mRdbAccess[m [0;1mfor[m [0;1mVAX[m [0;1mRMS[m [0;1mon[m [0;1ma[m [0;1mVAXcluster[m

              To activate RdbAccess for VAX RMS on any type of
              VAXcluster, you must first install RdbAccess for VAX RMS
              on each system disk that is commonly shared among nodes in
              the cluster. Then you must perform the following procedure
              to start RdbAccess for VAX RMS, replace the DCL tables,
              and load the license on all other nodes in the cluster:

              $ RUN SYS$SYSTEM:SYSMAN
              SYSMAN> SET ENVIRONMENT/CLUSTER/USER=SYSTEM
              Remote Password: supply SYSTEM password here
              SYSMAN> DO LICENSE LOAD RDBACCESS-RMS
              SYSMAN> DO @SYS$STARTUP:NSDS$STARTUP
              SYSMAN> EXIT






                                        Post-Installation Procedures [0;1m3-1[m

 



     [0;1m3.3[m [0;1mUser[m [0;1mAccount[m [0;1mRequirements[m


     [0;1m3.3[m [0;1mUser[m [0;1mAccount[m [0;1mRequirements[m

           RdbAccess for VAX RMS users must have certain account
           privileges and quotas. The following two sections contain
           information about these requirements.

     [0;1m3.3.1[m [0;1mUser[m [0;1mAccount[m [0;1mPrivileges[m

           To use RdbAccess for VAX RMS, an account must have
           at least the TMPMBX and NETMBX privileges. Use the
           VMS Authorize Utility to determine if users have the
           privileges they require. See Section 1.7.2 for more
           information.

     [0;1m3.3.2[m [0;1mUser[m [0;1mAccount[m [0;1mQuotas[m

           To use RdbAccess for VAX RMS, an account must have
           sufficient quotas. Table 3-1 summarizes the minimum
           required user account quotas.

           [0;1mTable[m_[0;1m3-1[m_[0;1mMinimum[m_[0;1mUser[m_[0;1mAccount[m_[0;1mQuotas[m_____________________

           [0;1mAccount[m_[0;1mQuota[m____[0;1mValue[m_______[0;1mDescription[m__________________

           PGFLQUO__________20,000______Paging_file_limit____________

           Use the VMS Authorize Utility to verify and change user
           account quotas. See Section 1.7.2 for more information.

     [0;1m3.4[m [0;1mRebooting[m [0;1mthe[m [0;1mSystem[m

           You are not required to reboot the system to activate
           RdbAccess for VAX RMS. However, you may choose to reboot
           your system after you have installed RdbAccess for VAX
           RMS, edited the system startup and shutdown files, and
           reset the system parameters (if necessary). A system
           reboot establishes any new parameter settings and verifies
           that RdbAccess for VAX RMS is ready for use and that the
           edits to the system startup command file are correct.






     [0;1m3-2[m Post-Installation Procedures

 



          [0;1m3.5[m [0;1mRunning[m [0;1mthe[m [0;1mInstallation[m [0;1mVerification[m [0;1mProcedure[m [0;1mSeparately[m


        [0;1m3.5[m [0;1mRunning[m [0;1mthe[m [0;1mInstallation[m [0;1mVerification[m [0;1mProcedure[m [0;1mSeparately[m

              If you answered YES to the IVP question during the
              RdbAccess for VAX RMS installation, the Installation
              Verification Procedure ran automatically at the end of the
              installation. You received a message indicating whether
              the IVP succeeded or failed.

              You can also run the IVP separately. The account from
              which you run the IVP must have the same privileges and
              account quotas required to install RdbAccess for VAX RMS.
              See Section 1.7 for more information.

              To run the IVP, use the following DCL command:

              $ SET DEFAULT SYS$COMMON:[SYSTEST.NSDS$IVP]
              $ @NSDS$IVP

        [0;1m3.6[m [0;1mUsing[m [0;1mRdbAccess[m [0;1mfor[m [0;1mVAX[m [0;1mRMS[m

              To use RdbAccess for VAX RMS, follow these steps: To use
              VAX SQL with RdbAccess for VAX RMS for access to an RMS
              data source or VSAM data set, do the following:

              1. Create field and record definitions in the CDD/Plus
                 data dictionary for each data file.

              2. Create database definitions in the CDD/Plus data
                 dictionary.

              3. Insert the SQL statement DECLARE SCHEMA FILENAME into
                 the application source code or issue the statement
                 in an interactive SQL session, using the schema name
                 discussed in the [0;4mDEC[m [0;4mRdbAccess[m [0;4mfor[m [0;4mVAX[m [0;4mRMS[m [0;4mon[m [0;4mVMS[m
                 [0;4mUser's[m [0;4mGuide[m.

              Once these steps have been completed, you can do read-only
              access operations on the data using VAX SQL with RdbAccess
              for VAX RMS.

              For information on RdbAccess for VAX RMS usage and
              qualifiers, see the [0;4mDEC[m [0;4mRdbAccess[m [0;4mfor[m [0;4mVAX[m [0;4mRMS[m [0;4mon[m [0;4mVMS[m
              [0;4mUser's[m [0;4mGuide[m, or enter the following DCL command:

              $ HELP RDBACCESS_RMS

                                        Post-Installation Procedures [0;1m3-3[m

 



     [0;1m3.7[m [0;1mPost-Installation[m [0;1mCheck[m [0;1mList[m


     [0;1m3.7[m [0;1mPost-Installation[m [0;1mCheck[m [0;1mList[m

           Table 3-2 summarizes the tasks you must perform after
           installing RdbAccess for VAX RMS. Check to make sure that
           you have performed all these tasks before making RdbAccess
           for VAX RMS available to users.

           [0;1mTable[m_[0;1m3-2[m_[0;1mPost-Installation[m_[0;1mCheck[m_[0;1mList[m____________________

           [0;1mTask[m____________________________[0;1mFor[m_[0;1mMore[m_[0;1mInformation[m______

           Edit the system startup file    See Section 3.1

           Activate RdbAccess for VAX RMS  See Section 3.2
           on a VAXcluster

           Check privileges and quotas of  See Section 3.3
           the_user_accounts_________________________________________



























     [0;1m3-4[m Post-Installation Procedures

 









                                                                       [0;1mA[m
        ________________________________________________________________

                               [0;1mSample[m [0;1mRdbAccess[m [0;1mfor[m [0;1mVAX[m [0;1mRMS[m [0;1mInstallation[m



              This appendix shows a typical installation of RdbAccess
              for VAX RMS on a VMS Version 5.3 system that is running
              the latest version of Rdb/VMS.

              Table 1-4 summarizes the tasks you must perform before
              installing RdbAccess for VAX RMS. Check to make sure that
              you have completed all these tasks before proceeding with
              the installation.

                Welcome to node MYNODE

        Username: SYSTEM <Return>
        Password:        <Return>

           Welcome to VAX/VMS Version 5.3 on node MYNODE

           Last interactive login on Thursday,  07-JAN-1991 13:51
            Last non-interactive login on Thursday,  07-JAN-1991 13:51

        $ REPLY/USER "Installation starting in 5 minutes. Please log out." <Return>
        $ SET LOGINS/INTERACTIVE=0 <Return>
        $ @SYS$UPDATE:VMSINSTAL NSDS MUA0: OPTIONS N <Return>

            VAX/VMS Software Product Installation Procedure V5.3

        It is 07-JAN-1991 at 13:51.

        Enter a question mark (?) at any time for help.

        * Are you satisfied with the backup of your system disk [YES]? <Return>

        Please mount the first volume of the set on MUA0:.
        * Are you ready? YES <Return>

        %MOUNT-I-MOUNTED, NSDS mounted on _MUA0:

        The following products will be processed:
          NSDS V1.0

                Beginning installation of NSDS V1.0 at 13:51

                           Sample RdbAccess for VAX RMS Installation [0;1mA-1[m

 






     %VMSINSTAL-I-RESTORE, Restoring product save set A ...
     %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.

     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]: 2 <Return>

     * Queue name [SYS$PRINT]: <Return>
     Job 810 (queue SYS$PRINT, entry 1295) started on SYS$PRINT

     * Do you want to continue the installation [NO]? YES <Return>

     %VMSINSTAL-I-RELMOVED , The product's release notes have been
     successfully moved to SYS$HELP.

         *************************************************************

         Installation procedures for: NSDS T1.2

         *************************************************************

         Checking system requirements ...

              Product:      RDBACCESS-RMS
              Producer:     DEC
              Version:      1.0
              Release Date: 1-JAN-1991

     * Does this product have an authorization key registered and loaded?
      YES <Return>

     * Do you want to purge files replaced by this installation [YES]? <Return>

     * Do you want to run the IVP after the installation [YES]? <Return>

       ********************************************************

       There are no more questions. The installation takes
       approximately 15 minutes on a stand-alone VAX 8200

       ********************************************************

       Beginning installation ...

     [0;1mA-2[m Sample RdbAccess for VAX RMS Installation

 






          ********************************************************

          Installing under VMS V5.3 - 07-JAN-1991 13:56

          ********************************************************

          The NSDS$STARTUP.COM file has been placed in
          SYS$STARTUP:NSDS$STARTUP.COM.  The following line
          should be placed in your system startup file.

          $ @SYS$STARTUP:NSDS$STARTUP.COM

          ********************************************************

          The NSDS IVP file has been placed in SYS$COMMON:[SYSTEST.NSDS$IVP].
          You may run this procedure separately any time you wish. To
          execute it, type:

          $ SET DEFAULT SYS$COMMON:[SYSTEST.NSDS$IVP]
          $ @NSDS$IVP

          ********************************************************

          Adding RDBACCESS_RMS help to the DCL help library

          ********************************************************

          ********************************************************
          The qualifier LGICMD for the RDB$REMOTE account in SYSUAF
          is modified by this installation.

          ********************************************************

        %NSDS-I-NOTINSTALLED, VMI$KWD:RDBSERVER.EXE was not installed by this kit
        %NSDS-I-REASON, Image ident version of new file is the same as current file
        %NSDS-I-NOTINSTALLED, VMI$KWD:RDBSHR.EXE was not installed by this kit
        %NSDS-I-REASON, Image ident version of new file is the same as current file
        %NSDS-I-NOTINSTALLED, VMI$KWD:RDBMSGS.EXE was not installed by this kit
        %NSDS-I-REASON, Image ident version of new file is the same as current file
        %NSDS-I-NOTINSTALLED, VMI$KWD:RDBBMSGS.EXE was not installed by this kit
        %NSDS-I-REASON, Image ident version of new file is the same as current file
        %NSDS-I-NOTINSTALLED, VMI$KWD:VIDA_MESSAGE.EXE was not installed by this kit
        %NSDS-I-REASON, Image ident version of new file is the same as current file
        %NSDS-I-NOTINSTALLED, VMI$KWD:RDMSMSG.EXE was not installed by this kit
        %NSDS-I-REASON, Image ident version of new file is older than current file
        %NSDS-I-NOTINSTALLED, VMI$KWD:RDMMSGSHR.EXE was not installed by this kit
        %NSDS-I-REASON, Image ident version of new file is older than current file

                           Sample RdbAccess for VAX RMS Installation [0;1mA-3[m

 






     %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories.

       *************************************************************

       The NSDS IVP verifies that all files are properly in place and that
       VAX SQL commands can be executed on RMS files.

       *************************************************************

       *************************************************************

         Performing NSDS IVP for: NSDS V1.0

       *************************************************************

       *************************************************************

          Checking the existence of RdbAccess for VAX RMS files.

       *************************************************************

        *************************************************************

          Checking for a sample CDD/Plus Dictionary.

        *************************************************************

        *************************************************************

          The sample dictionary was not found.  Please wait while one
          is created.  Please ignore any CDO informational messages.

        *************************************************************

     %CDO-I-FILECRE, file SYS$COMMON:[SYSHLP.EXAMPLES.NSDS]NSDS$EMPLOYEES.DAT; created
     %CDO-I-FILECRE, file SYS$COMMON:[SYSHLP.EXAMPLES.NSDS]NSDS$JOBHIST.DAT; created
     %CDO-I-FILECRE, file SYS$COMMON:[SYSHLP.EXAMPLES.NSDS]NSDS$COLLEGES.DAT; created
     %CDO-I-FILECRE, file SYS$COMMON:[SYSHLP.EXAMPLES.NSDS]NSDS$DEGREES.DAT; created
     %CDO-I-FILECRE, file SYS$COMMON:[SYSHLP.EXAMPLES.NSDS]NSDS$DEPTS.DAT; created
     %CDO-I-FILECRE, file SYS$COMMON:[SYSHLP.EXAMPLES.NSDS]NSDS$JOBS.DAT; created
     %CDO-I-FILECRE, file SYS$COMMON:[SYSHLP.EXAMPLES.NSDS]NSDS$SALHIST.DAT; created

        *************************************************************

          Executing a SQL sample query against an RMS file.  The tuple

          00418 Blount Peter

          should be displayed.

     [0;1mA-4[m Sample RdbAccess for VAX RMS Installation

 






           *************************************************************

         EMPLOYEE_ID   LAST_NAME        FIRST_NAME
         00418         Blount           Peter
        1 row selected

           ********************************************************

          NSDS V1.0 IVP completed successfully

          ********************************************************

        Installation of NSDS V1.0 completed at14:06

                VMSINSTAL procedure done at 14:06

        $ SET LOGINS/INTERACTIVE=64
        $ REPLY/USER "Installation complete. System is ready for use."

              Table 3-2 summarizes the tasks you must perform after
              installing RdbAccess for VAX RMS. Check to make sure that
              you have completed all these tasks before making RdbAccess
              for VAX RMS available to users.






















                           Sample RdbAccess for VAX RMS Installation [0;1mA-5[m

 









                                                                       [0;1mB[m
        ________________________________________________________________

                                             [0;1mRdbAccess[m [0;1mfor[m [0;1mVAX[m [0;1mRMS[m [0;1mFiles[m



              This appendix lists all the files that are transferred to
              your system during a RdbAccess for VAX RMS installation.
              The files are organized by directory. The file name and
              approximate file size in blocks are listed for each file.

              In SYS$STARTUP:

              NSDS$STARTUP.COM               5

              In SYS$SYSTEM:

              RDB$REMOTE_LOGIN.COM           4
              RDBSERVER.COM                  1
              RDBSERVER.EXE                 27

              In SYS$HELP:

              NSDS$MESSAGES.DOC            107
              NSDS010.RELEASE_NOTES         56
              RDB_MSG.DOC                  258

              In SYS$COMMON:[SYSHLP.EXAMPLES.NSDS]:

              NSDS$COLLEGES.DAT             3
              NSDS$CREATE_DATABASE.CDO     24
              NSDS$DEGREES.DAT             12
              NSDS$DELETE_DATABASE.CDO      6
              NSDS$DEPTS.DAT                3
              NSDS$EMPLOYEES.DAT           24
              NSDS$JOBHIST.DAT             21
              NSDS$JOBS.DAT                 3
              NSDS$SALHIST.DAT             39
              NSDS$WORK_STATUS.DAT          3


                                         RdbAccess for VAX RMS Files [0;1mB-1[m

 






           In SYS$LIBRARY:

           NSDS$DDI_RMS_SHR.EXE         102
           NSDS$MDI_CDD_SHR.EXE          75
           NSDS$SHR.EXE                 813
           RDBSHR.EXE                   233

           In SYS$MANAGER:

           RDBSERVER_NCP.COM              1
           VAXINFO$NETOBJ_INSERT.COM     14

           In SYS$MESSAGE:

           NSDS$MESSAGE.EXE              30
           RDBMSGS.EXE                   18

           In SYS$SYSROOT:[SYSTEST.NSDS$IVP]:

           NSDS$IDENT.COM                 1
           NSDS$IVP.COM                  11
           NSDS$SAMPLE_QUERY.SQL          1

           In SYS$UPDATE:

           VAXINFOINSTALL.COM           138



















     [0;1mB-2[m RdbAccess for VAX RMS Files

 
