                                     C                      DATATRIEVE____________________________________ '                      Installation Guide   .                      Order Number: AA-AJ56R-TE    "                      February 2000  E                      This manual describes the installation procedure @                      for Compaq[TM]DATATRIEVE [TM] Version 7.2A.            E                      Operating System:            OpenVMS[TM] VAX[TM] E                                                   Version 5.5-2, 6.2, ?                                                   7.1 or higher   G                                                   OpenVMS Alpha Version ?                                                   6.2 or higher   D                      Software Version:            DATATRIEVE Version6                                                   7.2A            0                      Compaq Computer Corporation                             February 2000B      Possession, use, or copying of the software described in thisA      documentation is authorized only pursuant to a valid written 6      license from Compaq or an authorized sublicensor.  @      Compaq conducts its business in a manner that conserves theE      environment and protects the safety and health of its employees, <      customers, and the community. While Compaq believes theB      information included in this publication is correct as of theA      date of publication, it is subject to change without notice. B      Compaq Computer Corporation makes no representations that theD      use of its products in the manner described in this publication?      will not infringe on existing or future patent rights, nor @      do the descriptions contained in this publication imply theE      granting of licenses to make, use, or sell equipment or software (      in accordance with the description.  E             Compaq Computer Corporation 2000. All rights reserved. . C            We welcome your comments on this book. Please use one of 4            the following ways to send your comments:  F            o  Send an electronic mail message to openvmsdoc@compaq.com  D            o  Send a fax to (+1) 603 884-0120, Attention: DATATRIEVE$               Documentation, REO2-J9  K            The following are trademarks of Compaq Computer Corporation:CDA, =            Compaq, DATATRIEVE, DEC, DEC Fortran, DECdecision, ?            DECdesign, DECforms, DECnet, DECpresent, DECwindows, B            DECwrite, DIGITAL, FMS, OpenVMS, PATHWORKS, PDP, ReGIS,@            VAX, VAX BASIC, VAX COBOL, VAX MACRO, VAX Pascal, VAXE            Rdb/ELN, VAXcluster, VIDA, VMS, VMS RMS, WPS-PLUS, and the             Compaq logo.   4            The following are third-party trademarks:  B            DB2 is a trademark and IBM is a registered trademark of0            International Business Machines Corp.E            LOTUS 1-2-3 is a registered trademark of Lotus Development             Corp.;            Motif is a registered trademark of Open Software             Foundation, Inc. G            ORACLE is a registered trademark, and Oracle CDD/Repository, H            Oracle CODASYL DBMS, Oracle Expert, Oracle Rdb, SQL/Services,;            Oracle Rdb Transparent Gateway, Oracle TRACE are ,            trademarks of Oracle Corporation.@            PostScript is a registered trademark of Adobe Systems            Corp.:            SYBASE is a registered trademark of SYBASE Inc.@            Windows is a trademark, and Excel, Microsoft, MS-DOS,@            Visual Basic, Visual C++ are registered trademarks of!            Microsoft Corporation.   A            All other trademarks and registered trademarks are the A            property of their respective holders. This document is !            available on CD-ROM. 1                      C                                                                  -3           C    ________________________________________________________________   C                                                            Contents       C    Preface..................................................    vii   $    1  Preinstallation Considerations  C          1.1   Prerequisite Hardware........................    1-1 4          1.2   OpenVMS Licensing Management FacilityC                (LMF)........................................    1-2 C          1.3   Prerequisite Software........................    1-3 C          1.3.1     Required Software Products...............    1-3 C          1.3.2     Optional Software Products...............    1-3 C          1.3.3     Order of Product Installation............    1-5 C          1.4   VAXcluster Consideration (VAX Only)..........    1-6 C          1.5   VMScluster Consideration.....................    1-6 7          1.6   Preparing Your System and the Installing C                Account......................................    1-7 C          1.6.1     Required Parameters......................    1-7 :          1.6.1.1     Global Pages (or pagelets) and Global7                      Sections (GBLPAGES and GBLSECTIONS C                      Parameters)............................    1-7 ;          1.6.2     Oracle CDD/Repository Considerations (if C                    support required)........................    1-9 8          1.6.2.1     Effect of Installation Procedure onC                      Existing DTR$LIB Directory.............    1-9 C          1.6.2.2     Required Privileges to CDD$TOP.........    1-9 :          1.6.3     Effect of Installation Procedure on theC                    Logical DTR$LIBRARY......................   1-11 5          1.6.4     More than One Installation of this C                    Version of DATATRIEVE....................   1-11 C          1.6.5     Check for Invalid DTRFUNxx.OLB...........   1-12       C                                                                   v                  )      2  DATATRIEVE Installation Procedure   E            2.1   Starting the Installation Procedure..........    2-1 E            2.2   Mounting the Distribution Medium.............    2-4 E            2.3   Answering Questions About Release Notes......    2-5 1            2.4   Answering Questions About Oracle E                  CDD/Repository...............................    2-6 9            2.5   Answering Questions About the DATATRIEVE 6                  object libraries (OpenVMS VAX systemsE                  only)........................................    2-6 8            2.6   Answering Questions About the LicensingE                  Management Facility (LMF)....................    2-7 :            2.7   Answering Questions During the DATATRIEVEE                  Installation.................................    2-8 ;            2.7.1     Installing DATATRIEVE with the Default E                      Answers..................................    2-9 E            2.7.2     Installing with LSE Support..............   2-11 6            2.7.3     Installing with Support for FormsE                      Products.................................   2-12 6            2.7.4     Specifying Suffixes for More than8                      One Installation of This Version ofE                      DATATRIEVE...............................   2-14 E            2.7.5     Defining the DATATRIEVE Remote Server....   2-17 8            2.7.6     Creating a DCL Command File for NewE                      Users....................................   2-18 E            2.7.7     Installing Shared Images.................   2-19 =            2.7.8     Installing Plot Definitions and Optional E                      Material.................................   2-20 E            2.7.9     Purging Files............................   2-21 E            2.7.10    Running the IVP..........................   2-21 E            2.8   Finishing the Installation...................   2-22   '      3  Postinstallation Considerations   E            3.1   Updating SYS$MANAGER:SYSTARTUP.COM...........    3-1 E            3.2   VAXcluster Considerations (VAX Only).........    3-1 :            3.3   Moving the DATATRIEVE Environment BetweenE                  Operating Systems............................    3-2 E            3.4   Updating Process Command Tables..............    3-2 E            3.5   Online DATATRIEVE Object Library.............    3-3 E            3.6   DECnet Considerations........................    3-3 E            3.6.1     Defining a DECnet Object.................    3-3             vi                  =               3.6.2     Creating a Default DECnet Account for H                         Distributed Access.......................    3-5H               3.7   Maintaining User-Defined Functions...........    3-84               3.8   Providing Control Information toH                     DATATRIEVE...................................   3-10>               3.9   Preparing to Install DATATRIEVE Client forH                     Windows......................................   3-118               3.10  Deleting Unused Files for DATATRIEVEH                     DECwindows Motif Support.....................   3-12H               3.11  Getting Help and Reporting Problems..........   3-13    )         4  User Environment Test Packages   H               4.1   Invoking DATATRIEVE..........................    4-2H               4.2   DATATRIEVE UETP..............................    4-3H               4.3   DATATRIEVE Graphics UETP.....................    4-6H               4.4   DATATRIEVE and Oracle CODASYL DBMS UETP......    4-8H               4.5   DATATRIEVE and Oracle Rdb UETP...............   4-10H               4.6   DATATRIEVE and Forms UETP....................   4-14  &         5  DATATRIEVE CBT Installation  1         A  Sample Installation Session (VAX Only)     3         B  Sample Installation Session (Alpha Only)   ;         C  List of Files Modified/Added by the Installation             Procedure                              H                                                                      vii                           H         ________________________________________________________________  H                                                                  Preface      A               This manual describes how to install the DATATRIEVE C               Version 7.2A software. This manual also describes how B               to use the DATATRIEVE User Environment Test PackagesA               (UETPs) and how to install the DATATRIEVE computer- F               based training (CBT). This manual covers both DATATRIEVED               for OpenVMS Alpha operating systems and DATATRIEVE forE               OpenVMS VAX operating systems, which are referred to by G               their abbreviated name DATATRIEVE. Sections specific to a E               particular platform are indicated using margin icons as #               shown in Conventions.            Intended Audience   A               This manual is intended for persons responsible for H               installing and maintaining DATATRIEVE software. To installF               the software, you should be familiar with VMSINSTAL, theH               command procedure used to install software products in theH               OpenVMS environment. For information on VMSINSTAL, see the$               OpenVMS documentation.  $         Operating System Information  D               Information about the versions of the operating systemG               and related software that is compatible with this version G               of DATATRIEVE is included in the DATATRIEVE media kit, in E               either this manual or the DATATRIEVE Before You Install                Letter.   D               For information on the compatibility of other softwareD               products with this version of DATATRIEVE, refer to theE               Software Product Description (SPD). You can use the SPD C               to verify which versions of your operating system are 9               compatible with this version of DATATRIEVE.   H                                                                      vii                       Related Documents  @            For further information on the topics covered in this@            manual, you can refer to the following documentation:  &            o  DATATRIEVE Release Notes  >               Describes corrections to software, restrictions,D               workarounds, and known problems for DATATRIEVE Version               7.2A.   %            o  DATATRIEVE User's Guide   <               Describes how to use DATATRIEVE interactively.  ,            o  DATATRIEVE Guide to Interfaces  D               Includes information on using DATATRIEVE to manipulateA               data with forms, relational databases, and database !               management systems.   )            o  DATATRIEVE Reference Manual   <               Contains reference information for DATATRIEVE.  =            o  DATATRIEVE Guide to Programming and Customizing   @               Explains how to use the DATATRIEVE Call Interface.B               The manual also describes how to create user-defined>               keywords and user-defined functions to customizeA               DATATRIEVE and how to customize DATATRIEVE help and                message texts.  @            o  Getting Started with DATATRIEVE Client for Windows  ;               Describes basic DATATRIEVE Client for Windows                functions.        Conventions  A            In this manual, every use of OpenVMS VAX indicates the C            OpenVMS VAX operating system, every use of OpenVMS Alpha B            indicates the OpenVMS Alpha operating system, and everyB            use of OpenVMS indicates both the OpenVMS VAX operating9            system and the OpenVMS Alpha operating system.   E            The following conventions are used to identify information 7            specific to OpenVMS Alpha or to OpenVMS VAX:   	      viii                  E               The following conventions are also used in this manual:   B               [ ] (brackets)   Square brackets in the installationE                                procedure enclose the default response 0                                value to a query.  H               ... (horizontal  A horizontal ellipsis in an example meansG               ellipsis)        that information not directly related to <                                the example has been omitted.  F               .                A vertical ellipsis in an example meansG               . (vertical      that information not directly related to <               . ellipsis)      the example has been omitted.  H               Bold type        Bold type is used for terms being definedH                                for the first time. Bold type in examples4                                indicates user input.           References to Products  A               DATATRIEVE was formerly known as DEC DATATRIEVE and @               as DIGITAL DATATRIEVE. All DATATRIEVE Version 7.2AA               documentation refers to this product as DATATRIEVE.   G               The DATATRIEVE documentation to which this manual belongs B               often refers to products by their abbreviated names.  H               o  DATATRIEVE refers to both Compaq DATATRIEVE for OpenVMSF                  Alpha and Compaq DATATRIEVE for OpenVMS VAX software.  E               o  Oracle Rdb[TM] refers to both Oracle Rdb for OpenVMS ?                  Alpha and Oracle Rdb for OpenVMS VAX software.   F               o  Oracle CODASYL DBMS[TM] refers to both Oracle CODASYLC                  DBMS for OpenVMS Alpha and Oracle CODASYL DBMS for &                  OpenVMS VAX software.  A               o  Compaq Fortran[TM] refers to both Compaq Fortran E                  for OpenVMS Alpha and Compaq Fortran for OpenVMS VAX                   software.  G               o  Compaq C refers to both Compaq C for OpenVMS Alpha and 3                  Compaq C for OpenVMS VAX software.   E               o  DEC TPU refers to both DEC TPU for OpenVMS Alpha and 2                  DEC TPU for OpenVMS VAX software.  H                                                                       ix                 C            o  DEC DB Integrator Gateway refers to DEC DB Integrator C               Gateway for DB2[TM] Client, DEC DB Integrator Gateway >               for ORACLE[R], and DEC DB Integrator Gateway for               SYBASE[R].  =            o  RMS[TM] refers to the OpenVMS Record Management                Services.   ;            This manual uses the term relational database or E            relational source to refer to all three of these products:               o  VAX Rdb/ELN[TM]               o  Oracle Rdb  '            o  DEC DB Integrator Gateway   C               ________________________Note ________________________   >               DEC DB Integrator Gateway is now owned by Oracle9               Corporation and has been renamed Oracle Rdb "               Transparent Gateway.  C               _____________________________________________________                                                 x                       H                                                                        1H         ________________________________________________________________  H                                           Preinstallation Considerations      B               This chapter includes important installation consid-C               erations that you must be aware of before you install B               DATATRIEVE Version 7.2A. Read this chapter carefullyF               before you proceed to Chapter 2, DATATRIEVE Installation               Procedure.  H               To prepare your system for installing DATATRIEVE, you must*               perform the following tasks:  H               o  Verify that your system has enough memory and available:                  disk space to install and use DATATRIEVE.  B               o  Register the Product Authorization Key (PAK) thatA                  is shipped with DATATRIEVE (if this is the first -                  installation of DATATRIEVE).   H               o  Verify that your system has the correct versions of theF                  optional and required software you will be using with                  DATATRIEVE.  @               o  Check your system and the installing account toE                  ensure that parameters and quotas are sufficient for 1                  installing and using DATATRIEVE.   D               This chapter tells you what actions to take to prepare4               your system for installing DATATRIEVE.  !         1.1 Prerequisite Hardware   @               Installing DATATRIEVE requires a certain amount ofC               free disk storage space during the installation. Once F               DATATRIEVE is installed, less storage space is required.  E               The following table summarizes the storage requirements 0               for OpenVMS VAX operating systems.  H                                       Preinstallation Considerations 1-1           #      Preinstallation Considerations       1.1 Prerequisite Hardware  E            __________________________________________________________ )                             Blocks During F            Kit______________Installation_____Blocks_After_Installation  3            DATATRIEVE       29,000           26,000 E            Version_7.2A______________________________________________   @            DATATRIEVE runs on all VAX processors except the VAX-            11/725 processor. <>   B            The following table summarizes the storage requirements/            for OpenVMS Alpha operating systems:   E            __________________________________________________________ )                             Blocks During F            Kit______________Installation_____Blocks_After_Installation  6            DATATRIEVE       50,000           35,000 <>E            Version_7.2A______________________________________________   E            To determine the number of free disk blocks on the current >            system disk, enter the following command at the DCL            prompt:  #            $ SHOW DEVICE SYS$DEVICE   4      1.2 OpenVMS Licensing Management Facility (LMF)  E            This version of DATATRIEVE supports the License Management C            Facility provided by OpenVMS. See the OpenVMS documenta- %            tion for more information.   @            If you receive a Product Authorization Key (PAK) withC            DATATRIEVE you should register the information contained @            in the PAK before you begin the installation. You canD            register by using the License command procedure using the            following command:   #            $ @SYS$UPDATE:VMSLICENSE   D            You can also use the LICENSE REGISTER command to registerA            the information contained in the PAK. Both methods are 2            described in the OpenVMS documentation.  B            DATATRIEVE asks you early in the installation procedure;            whether or not you have registered and loaded an =            authorization key. You can install this version of D            DATATRIEVE without the authorization key information, but  '      1-2 Preinstallation Considerations            H                                           Preinstallation ConsiderationsH                          1.2 OpenVMS Licensing Management Facility (LMF)  H               you cannot run DATATRIEVE or the Installation Verification               Procedure (IVP).  !         1.3 Prerequisite Software   @               You must have the correct versions of the optionalC               and required software products you will be using with G               DATATRIEVE. Install those products in the order specified >               in Section 1.3.3, Order of Product Installation.  .               1.3.1 Required Software Products  F               This version of DATATRIEVE is a complete kit. You do notE               need any previous versions of DATATRIEVE to install it.   B               On OpenVMS VAX operating systems, DATATRIEVE VersionD               7.2A requires Version 5.5-2, 6.2, 7.1 or higher of theH               operating system. For Fullname support OpenVMS VAX VersionF               6.2 is required. To check which version of the operatingH               system is currently installed on your system, use the SHOW2               SYSTEM command at the DCL prompt. <>  D               On OpenVMS Alpha operating systems, DATATRIEVE VersionB               7.2A requires Version 6.2 or higher of the operating               system. <>  .               1.3.2 Optional Software Products  D               The following optional products can be used along with               DATATRIEVE:   &               o  Oracle CDD/Repository  >                  If you plan to install DATATRIEVE with OracleC                  CDD/Repository support, the following requirements                   apply:   C                  -  On OpenVMS VAX operating systems, you must have F                     Version 5.0 or higher of Oracle CDD/Repository[TM]9                     before you can install DATATRIEVE. <>   E                  -  On OpenVMS Alpha operating systems, you must have B                     Version 5.3 or higher of Oracle CDD/Repository9                     before you can install DATATRIEVE. <>   H                                       Preinstallation Considerations 1-3           #      Preinstallation Considerations       1.3 Prerequisite Software  @               To check which version of Oracle CDD/Repository isB               currently installed on the system, use the following               command:  #               $ DICTIONARY OPERATOR   G               The CDO banner gives the version of Oracle CDD/Repository >               currently installed on your system. For example:  !               Welcome to CDO V6.1 4               The CDD/Repository V6.1 User Interface                Type HELP for help               CDO>  !            o  Oracle CODASYL DBMS               o  Oracle Rdb              o  VAX Rdb/ELN               o  VAX TDMS              o  Compaq FMS[TM]  !            o  Compaq DECforms[TM]   '            o  DEC DB Integrator Gateway               o  LSE   ,            o  Compaq DECwindows[TM] Motif[R]  ;            o  DECnet[TM]/OSI for OpenVMS VAX Version 5.7 or C               DECnet/OSI for OpenVMS Alpha Version 5.7 for Fullname                support.  ?            o  For using DATATRIEVE Version 7.2A with DATATRIEVE_;               Client for Windows, the following software is                required:N  !               *  DECnet or TCP/IP   "               *  Microsoft Windows  D               *  PATHWORKS[TM] for MS-DOS[R] and Windows (for DECnet                  use only).V  >               *  A compiler or interpreter that can access DLLC                  libraries (only required if you use the DATATRIEVE !                  Call Interface).6  '      1-4 Preinstallation Considerations            H                                           Preinstallation ConsiderationsH                                                1.3 Prerequisite Software  D               On OpenVMS Alpha operating systems VAX Rdb/ELN and VAX(               TDMS are not available. <>  B               Refer to the DATATRIEVE Before You Install Letter toA               determine which versions of these optional softwaresC               products are compatible with DATATRIEVE Version 7.2A.m  D               If an optional product is on the system but is not theH               version required by DATATRIEVE, the installation procedureG               will not install the User Environment Test Package (UETP)eD               for that product. (Note that not all optional software$               products have a UETP.)  H               If you want to ready domains that reside on a remote node,C               you must have Version 7.2A of the DATATRIEVE softwareC>               installed on the remote node you wish to access.  1               1.3.3 Order of Product Installation   F               When you install required and optional software productsG               with DATATRIEVE, you should install these products in thel               following order:                 o  Optional LSEo  C                  If you plan to use LSE with DATATRIEVE, you shouldn@                  install LSE before installing other required orC                  optional software products. However, if you chooses?                  to install LSE at a later date, the DATATRIEVEgD                  installation procedure provides you with the optionD                  of performing a modified DATATRIEVE installation toA                  provide DATATRIEVE support for LSE at that time.i  $               o  Optional Oracle Rdb  C                  If you plan to use Oracle Rdb with DATATRIEVE, youtE                  should follow the order-of-installation instructions B                  provided with Oracle CDD/Repository to insure theF                  proper operation of Oracle CDD/Repository with Oracle                  Rdb.   &               o  Oracle CDD/Repository  @               o  Optional forms products ( VAX TDMS, Compaq FMS,                  DECforms)  E               o  Optional database products (Oracle CODASYL DBMS, VAXL4                  Rdb/ELN, DEC DB Integrator Gateway)  H                                       Preinstallation Considerations 1-5 w         #      Preinstallation ConsiderationsO      1.3 Prerequisite Software  B               Install Oracle CODASYL DBMS, VAX Rdb/ELN, and DEC DB@               Integrator Gateway before installing DATATRIEVE toB               make sure the installation includes sample databasesA               and User Environment Test Packages. You do not haves@               to install these optional database products before=               DATATRIEVE to use the products with DATATRIEVE.   '            o  Optional DECwindows Motif,              o  DECnet              o  Microsoft Windowso  /            o  PATHWORKS for MS-DOS and Windows.   ;            o  A compiler or interpreter that can access DLLr               libraries.              o  DATATRIEVE  C               ________________________Note ________________________   B               DECforms, and DECwindows Motif can also be installed               after DATATRIEVE._  C               _____________________________________________________   ,      1.4 VAXcluster Consideration (VAX Only)  B            This installation procedure lets you install DATATRIEVEE            only on a system-rooted device. Whether you are installing.>            DATATRIEVE on a VAXcluster[TM] or in a nonclusteredC            environment, the installation procedure places the files @            that it generates in SYS$COMMON, not in SYS$SPECIFIC.C            The installation defines the logical name DTR$LIBRARY as.            SYS$COMMON:[DTR].  !      1.5 VMScluster Consideration.  >            If you are using a dual-architecture (VAX and AlphaA            systems) heterogeneous cluster, before executing these)A            commands, make sure the appropriate logical names have.B            been set to define the scope of the SYSMAN DO commands.A            For more information, see the OpenVMS System Manager's.            Manual.  '      1-6 Preinstallation Considerations. .  .      H                                           Preinstallation ConsiderationsH                     1.6 Preparing Your System and the Installing Account  <         1.6 Preparing Your System and the Installing Account  B               This section tells you which characteristics of yourE               system and installing account need to be checked before C               you install DATATRIEVE. These characteristics includeiB               process quotas, access control privileges to CDD$TOPB               (if you plan to install DATATRIEVE Version 7.2A withD               Oracle CDD/Repository support), and system parameters.C               Instructions are given for checking and modifying the D               relevant characteristics of your system and installing               account.  '               1.6.1 Required Parameters.  B               You must check that the value of your process quotasA               and system parameters are sufficient for installingoB               DATATRIEVE. You can check these values in the OracleB               CDD/Repository documentation (if you plan to install@               DATATRIEVE Version 7.2A with Oracle CDD/Repository               support).-  D               1.6.1.1 Global Pages (or pagelets) and Global Sections3               (GBLPAGES and GBLSECTIONS Parameters)   A               If you plan to install various DATATRIEVE images as B               SHARED, you need sufficient global pages (on OpenVMSF               VAX systems) or pagelets (on OpenVMS Alpha systems), andH               global sections. The installation procedure asks you aboutC               five images: DDMFxx, DTR32xx, DTRSHRxx, DTRAPIxx, andoH               DTRMSGS. (The xx at the end of the file name refers to theF               optional suffix that you can specify in the installationC               procedure. See Section 2.7.4, Specifying Suffixes for.F               More than One Installation of This Version of DATATRIEVEF               for more information.) You do not have to install all ofG               these images; you need sufficient global pages and global =               sections only for those you do wish to install.   A               DATATRIEVE automatically installs the DTRHELP imageDD               as SHARED. You need sufficient global pages and global&               sections for this image.          H                                       Preinstallation Considerations 1-7    U      #      Preinstallation Considerations29      1.6 Preparing Your System and the Installing Account.  A            The following table indicates the requirements for thedB            GBLPAGES and GBLSECTIONS parameters for the image filesE            that are part of this version of DATATRIEVE on OpenVMS VAX.            operating systems.1  E            __________________________________________________________FE            File__________Global_Sections_____Global_Pages____________t  1            DDMFxx         2                   102   1            DTR32xx        1                   184   1            DTRSHRxx       5                  1226.  1            DTRMSGS        1                   115r  1            DTRHELP        1                    40.  1            DTRAPIxx       2                    86d  E            __________________________________________________________n  E            Total:________12__________________1753_<>_________________   A            The following table indicates the requirements for theDB            GBLPAGES and GBLSECTIONS parameters for the image filesA            that are part of this version of DATATRIEVE on OpenVMS #            Alpha operating systems.   E            __________________________________________________________nE            File__________Global_Sections_____Pagelets________________r  1            DDMFxx         1                   273A  1            DTR32xx        1                   964   1            DTRSHRxx       2                  3970e  1            DTRMSGS        1                   115.  1            DTRHELP        1                    49i  1            DTRAPIxx       2                   282E  E            __________________________________________________________e  E            Total:_________8__________________5653<>__________________n  E            To find how many free global pages and global sections are.B            available on your system, issue the following commands:  7            $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES")R7            $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS")   '      1-8 Preinstallation ConsiderationsS T  .      H                                           Preinstallation ConsiderationsH                     1.6 Preparing Your System and the Installing Account  D               1.6.2 Oracle CDD/Repository Considerations (if support               required)y  H               If you plan to install DATATRIEVE Version 7.2A with OracleF               CDD/Repository support, you should perform the following               tasks:  ?               o  Check the contents of the dictionary directory E                  CDD$TOP.DTR$LIB for user definitions and subdirecto-_3                  ries. Back these up if they exist.   B               o  Make sure the installation account has all access'                  privileges to CDD$TOP.o  =               The next two sections explain these procedures..  B               1.6.2.1 Effect of Installation Procedure on Existing               DTR$LIB Directory   B               The directory CDD$TOP.DTR$LIB is reserved for use byE               Compaq. The installation procedure builds, or rebuilds, B               this directory each time you install DATATRIEVE. TheD               directory should contain only directories that containD               definitions for the plots and sample domains, records,H               and tables that are shipped with the product. Users shouldH               not create any dictionary objects or directories that have2               DTR$LIB as part of their path names.  B               When the installation procedure rebuilds DTR$LIB, itD               deletes the existing DTR$LIB hierarchy. Therefore, youF               should check that DATATRIEVE users have not placed theirE               own definitions either in DTR$LIB or in any part of itsnE               substructure. Extract user definitions you want to save 5               and redefine them in another directory.o  4               1.6.2.2 Required Privileges to CDD$TOP  C               Because the installation procedure builds or rebuilds D               DTR$LIB, the installation account must have all access@               control privileges to CDD$TOP. You can check these=               privileges with the following command sequence:e  "               $ RUN SYS$SYSTEM:DMU*               DMU> SHOW PROTECTION CDD$TOP  H                                       Preinstallation Considerations 1-9           #      Preinstallation Considerationss9      1.6 Preparing Your System and the Installing Accounte  ;            The resulting privileges list should include the             following:   )            CONTROL          GLOBAL_DELETE   #            DTR_EXTEND       HISTORYf  (            DTR_MODIFY       LOCAL_DELETE  %            DTR_READ         PASS_THRU               DTR_WRITE        SEE   "            EXTEND           UPDATE              FORWARD  B            After checking the privileges list, type EXIT and press9            the RETURN key to return to DCL command level.A  D            If any of the required privileges are not available or ifB            they are denied or banished, you must change the accessE            control list (ACL) entry to provide all privileges for theEC            duration of the installation. One way you can do this is,7            to enter the following sequence of commands:               $ RUN SYS$SYSTEM:DMUa3            DMU> SET PROTECTION/GRANT=ALL/UIC=[1,4]-r#            DMU> /POSITION=1 CDD$TOPE            DMU> EXIT  ?            If you are using an account other than [1,4] for theED            installation, replace [1,4] with the UIC of that account.  @            After the installation procedure is complete, you canD            remove the ACL entry with the following command sequence:              $ RUN SYS$SYSTEM:DMUe4            DMU> DELETE/PROTECTION/POSITION=1 CDD$TOP            DMU> EXIT  >            For your convenience during future installations of=            DATATRIEVE, you might want to create command filesm6            containing these two sequences of commands.  (      1-10 Preinstallation Considerations p  M      H                                           Preinstallation ConsiderationsH                     1.6 Preparing Your System and the Installing Account  C               1.6.3 Effect of Installation Procedure on the Logicall               DTR$LIBRARY   A               The installation defines the logical DTR$LIBRARY asOF               SYS$COMMON:[DTR]. If the installation fails, DTR$LIBRARYB               may be left deassigned, and you must redefine it. ToG               redefine the logical, use the DEFINE command, as follows:   ?               $ DEFINE/SYSTEM/EXEC DTR$LIBRARY SYS$COMMON:[DTR]   A               1.6.4 More than One Installation of this Version ofz               DATATRIEVE  D               You can install this version of DATATRIEVE a number ofH               times to produce different sets of images and files. Note,G               however, that you cannot install multiple versions of the E               product, such as both Version 7.2 and Version 7.2A. For D               example, the installation procedure could be run firstG               to install DATATRIEVE Version 7.2A with VAX TDMS. You can F               install DATATRIEVE Version 7.2A a second time to supportE               Compaq FMS. (Note that DECforms is supported by defaultsE               whenever available on the system.) The resulting imagesTH               and file names are differentiated by a suffix added to theF               default names. The installation procedure prompts you to!               choose this suffix.m  C               The suffix you specify will be given to the followingrF               files created during installation. The two letters xx atE               the end of a file name stand for the 1- to 26-charactera!               suffix you specify:r  '               o  SYS$SHARE:DTRSHRxx.EXEs  '               o  SYS$SHARE:DTRAPIxx.EXE   '               o  SYS$SHARE:DTRAPIxx.OLB   '               o  SYS$SYSTEM:DTR32xx.EXEY  &               o  SYS$SYSTEM:DDMFxx.COM  &               o  SYS$SYSTEM:DDMFxx.EXE  )               o  DTR$LIBRARY:DTRBLDxx.COMO  )               o  DTR$LIBRARY:DTRLIBxx.OLBa  )               o  DTR$LIBRARY:DTRFNDxx.MAR   )               o  DTR$LIBRARY:DTRFNDxx.OBJ   H                                      Preinstallation Considerations 1-11    e      #      Preinstallation Considerations 9      1.6 Preparing Your System and the Installing Account   &            o  DTR$LIBRARY:DTRFUNxx.OLB  '            o  SYS$STARTUP:DTRSTUPxx.COM   '            o  VUE$LIBRARY:VUE$DTRxx.COM   C               ________________________Note ________________________   ?               o  The installation procedure does not append theE@                  xx suffix to all images and files. For example,F                  DTR$LIBRARY:TERMSERVE.OLB and SYS$MESSAGE:DTRMSGS.EXE4                  do not get the installation suffix.  >               o  DTRAPIxx.EXE resides in SYS$SHARE and you can:                  copy it whenever you need to link it with:                  user programs to create DATATRIEVE client=                  applications. You can also copy DTRAPIxx.EXE ?                  to OpenVMS nodes that do not have a registereda$                  DATATRIEVE license.  A                  No DATATRIEVE license is required for the Cliento<                  application but only for the server. DTRAPI?                  libraries for the Windows environment are also.A                  provided by the DATATRIEVE kit as optional files_>                  and can be copied to a Windows environment to?                  create Windows DATATRIEVE Client applications.   C               ______________________________________________________  0            1.6.5  Check for Invalid DTRFUNxx.OLB  @            DATATRIEVE Version 6.1 distributed, and in some casesE            installed, an incorrect DTRFUNxx.OLB library which did not ,            contain the object module DTRFND.  E            To find out if this applies to your system, you must checklD            the DTRFUNxx.OLB library contained in DTR$LIBRARY. If theE            object module DTRFND is not found in the library, you mustfC            delete DTRFUNxx.OLB before installing DATATRIEVE Versionn            7.2A.  D            The following example shows how to check for the presence<            of the object module DTRFND in the DTRFUN.OLB and(            DTRFUNORIGINAL.OLB libraries.D            Since DTRFUNORIGINAL.OLB does not contain DTRFND, it will2            have to be deleted before installation.  (      1-12 Preinstallation Considerations y         H                                           Preinstallation ConsiderationsH                     1.6 Preparing Your System and the Installing Account  %         $ DIR DTR$LIBRARY:DTRFUN*.OLBn  "         Directory SYS$COMMON:[DTR]  <         DTRFUN.OLB;1             53  17-AUG-1993 13:59:39.37<         DTRFUNFMS.OLB;1          53   9-JUL-1993 14:34:50.57<         DTRFUNGRZ.OLB;1          62   9-JUL-1993 15:12:13.64<         DTRFUNMUPA1.OLB;1        53  12-OCT-1993 17:19:15.50         DTRFUNORIGINAL.OLB;1<                                  50  22-SEP-1993 11:11:01.06<         DTRFUNTDMS.OLB;1         53   9-JUL-1993 14:57:51.66  2         $ LIBRARY/LIST/NAME DTR$LIBRARY:DTRFUN.OLB  C         Directory of OBJECT library SYS$COMMON:[DTR]DTRFUN.OLB;1 ona         12-OCT-1993 17:58:08L         Creation date: 8-JUL-1993 12:11:37  Creator: VAX-11 Librarian V04-00A         Revision date: 8-JUL-1993 12:12:25  Library format:   3.0i@         Number of modules:      1           Max. key length:  31L         Other entries:          2           Preallocated index blocks:    49L         Recoverable deleted blocks:    0    Total index blocks used:       2L         Max. Number history records:  20    Library history records:       1           Module DTRFND_:         DTR$$FND_FUN_LAST                RTN_FN$GET_SYMBOL  :         $ LIBRARY/LIST/NAME DTR$LIBRARY:DTRFUNORIGINAL.OLB  H         Directory of OBJECT library SYS$COMMON:[DTR]DTRFUNORIGINAL.OLB;1         on 12-OCT-1993 17:58:50OL         Creation date: 21-MAY-1993 16:21:34 Creator: VAX-11 Librarian V04-00A         Revision date: 21-MAY-1993 16:21:34 Library format:   3.0r@         Number of modules:      0           Max. key length:  31I         Other entries:          0           Preallocated index blocks: 49 I         Recoverable deleted blocks:   0     Total index blocks used:    0 I         Max. Number history records: 20     Library history records:    0s                  H                                      Preinstallation Considerations 1-13 I  S                  H                                                                        2H         ________________________________________________________________  H                                        DATATRIEVE Installation Procedure      H               Before you install DATATRIEVE Version 7.2A, make sure thatE               your system meets all requirements listed in Chapter 1, -               Preinstallation Considerations.t  @               Your Version 7.2A installation kit consists of oneC               magnetic tape or TK50. This medium makes obsolete thePE               distribution media for any lower version of DATATRIEVE.m  ?               DATATRIEVE is also available on CDROM. If you areBH               installing DATATRIEVE from CDROM, follow the directions in<               the documentation packaged with the CDROM kit.  E               The installation procedure is described in the sections E               that follow. Note that as the procedure progresses, theTD               installation command procedure sends questions to yourG               screen to guide you through the installation process. The E               sections that follow explain these questions in detail.O  @               On OpenVMS VAX operating systems, after you answerH               questions from the installation procedure, installation ofA               DATATRIEVE takes approximately 20 to 40 minutes. <>   B               On OpenVMS Alpha operating systems, after you answerH               questions from the installation procedure, installation ofA               DATATRIEVE takes approximately 10 to 20 minutes. <>c  /         2.1 Starting the Installation Procedure   E               To start the installation, invoke the VMSINSTAL command F               procedure from a privileged account. VMSINSTAL is in theF               SYS$UPDATE directory. Use the following format to invoke               VMSINSTAL.  G               @SYS$UPDATE:VMSINSTAL save-set-name device-name OPTIONS N   H                                    DATATRIEVE Installation Procedure 2-1 n         &      DATATRIEVE Installation Procedure,      2.1 Starting the Installation Procedure              save-set-name  C            The name of the DATATRIEVE save set you want to install:   E            On OpenVMS VAX operating systems, enter DTRA072 to installn&            DATATRIEVE Version 7.2A. <>  B            On OpenVMS Alpha operating systems, enter DTRAXPA072 to.            install DATATRIEVE Version 7.2A. <>              device-name  @            The name of the device on which you plan to mount theB            media. For example, MTA0: is the device name for a tapeB            drive. It is not necessary to use the console drive for@            this installation. However, if you do use the consoleC            drive, you should replace any media you removed once the E            installation is complete. If you are installing DATATRIEVE D            from a CD, you must specify a device-name and a directoryB            name. The directory name should be the same as the save            set name.              OPTIONS N  B            An optional parameter that indicates you want to reviewB            the release notes questions (see Section 2.3, Answering?            Questions About Release Notes for more information).   B            The following example and the rest of this chapter showA            how to install DATATRIEVE Version 7.2A for OpenVMS VAXtE            from CDROM DKA400. This example uses the OPTIONS N release             note parameter.  E            $ @SYS$UPDATE:VMSINSTAL DTRA072 DKA400:[DTRA072] OPTIONS N   D            If you do not supply any parameter, VMSINSTAL prompts youC            for the information later in the installation procedure.I  >            Note that you can specify the AUTOANSWERBACK optionB            when you invoke VMSINSTAL. This option creates the fileB            SYS$UPDATE:DTRA072.ANS, which contains the installationC            questions and your responses. This file can then be used B            in subsequent installations. (The OpenVMS documentationC            on software installation contains more information aboutV            VMSINSTAL.)  *      2-2 DATATRIEVE Installation Procedure n  7      H                                        DATATRIEVE Installation ProcedureH                                  2.1 Starting the Installation Procedure  >               The AUTOANSWERBACK option is not recommended for>               DATATRIEVE installations. Questions asked duringA               the DATATRIEVE installation are based on the system D               environment. The system environment at the time of theB               original installation determines which questions theD               installation procedure will ask. When you proceed withG               a subsequent installation, the questions change according H               to changes in the system environment. Thus, if you specifyB               AUTOANSWERBACK during the original installation, youH               probably will not receive the appropriate questions during*               the subsequent installation.  A               The installation procedure prompts you for input atcE               various times. Whenever you are prompted for input, youa;               can type a question mark (?) symbol for help.p  E               Most installation prompts include a default response inuH               brackets. To enter the default bracketed response, you canG               either explicitly enter that response or press the RETURNo               key.  H               Before the installation procedure begins, VMSINSTAL checksE               if you are logged in to the system account. If not, you +               receive this warning message:E  B               %VMSINSTAL-W-NOTSYSTEM, You are not logged in to the               system account.r  D               In addition, before the installation procedure begins,E               VMSINSTAL checks for active processes on the system. IflF               your DECnet network is running, you receive this warning               message:  I               %VMSINSTAL-W-DECNET, Your DECnet network is up and running.   F               If there are still users on the system, you receive this;               warning message with a list of process names:   L               %VMSINSTAL-W-ACTIVE, The following processes are still active:  )                                         . )                                         .d)                                         .   ?               The list of the process names is followed by this                question:R  4               * Do you want to continue anyway? [NO]  H                                    DATATRIEVE Installation Procedure 2-3 s  c      &      DATATRIEVE Installation Procedure,      2.1 Starting the Installation Procedure  D            If you want to stop the installation process to allow allE            users to exit the system, enter N or press the RETURN key.t  ?            At the start of the VMSINSTAL procedure, you need too)            answer the following question:p  I            * Are you satisfied with the backup of your system disk [YES]?o  ?            After you have performed the necessary backup, enter >            Y or press the RETURN key. If you reply with N, the            installation stops.  )      2.2 Mounting the Distribution MediumL  D            You should now mount the first distribution volume on the;            device you specified when you invoked VMSINSTAL.a  4            VMSINSTAL displays the following message:  >            Please mount the first volume of the set on DKA400:              * Are you ready?u  :            Type Y after you mount the distribution medium.  B            The installation procedure then checks if the following>            necessary conditions for the installation have been            fulfilled:d  A            o  The target of the installation is SYS$COMMON on the #               system-rooted device.   ;            o  A compatible version of OpenVMS is installed.o  E            o  At least 29,000 blocks are available on the system disktC               (50,000 blocks are required if you install DATATRIEVE (               on OpenVMS Alpha systems).  A            If any of these conditions has not been fulfilled, the ?            installation procedure displays a message describingEA            the problem. After satisfying the requirement, you canlC            rerun the installation procedure by invoking the command %            procedure VMSINSTAL again.n  @            If you choose to install DATATRIEVE Version 7.2A withD            Oracle CDD/Repository support, the installation procedureC            checks whether Oracle CDD/Repository is available on theVC            system and if the required version and proper ACL accesse             rights are available.  *      2-4 DATATRIEVE Installation Procedure h  )      H                                        DATATRIEVE Installation ProcedureH                                     2.2 Mounting the Distribution Medium  F                 ________________________Note  ________________________  B                 Systems that do not have DECnet cannot support theD                 DATATRIEVE remote server. However on systems without=                 DECnet, but with TCP/IP software (see list of B                 optional software products), the DATATRIEVE remote@                 server image (DDMF) can behave as the DATATRIEVE?                 Server for DATATRIEVE Client applications usingf>                 the TCP/IP network transport. On such systems,B                 the installation procedure next displays a messageD                 noting that it cannot define a DECnet object for theD                 remote server. If you later install DECnet, you willB                 then need to define a DECnet object for the remoteB                 server. See Section 3.6, DECnet Considerations for!                 more information..  E                 _____________________________________________________e  D               This ends the initial series of questions generated byH               VMSINSTAL. If you have successfully completed this portionH               of the installation, a message similar to the following is               displayed:  7               The following products will be processed:i                 DTRA Version 7.2  A                Beginning installation of DTRA Version 7.2 at 8:15   A               VMSINSTAL-I-RESTORE, Restoring product saveset A...   E               The installation continues with questions about releaseD               notes.  3         2.3 Answering Questions About Release Notes   G               If you specified the qualifier OPTIONS N at the beginningeE               of the installation, the procedure offers these optionsxE               regarding DATATRIEVE Version 7.2A online release notes:   $               Release Notes Options:  '               1.  Display release notess%               2.  Print release notes                3.  Both 1 and 2=               4.  Do not display, print or copy release notesi  "               * Select option [2]:  H                                    DATATRIEVE Installation Procedure 2-5    h      &      DATATRIEVE Installation Procedure0      2.3 Answering Questions About Release Notes  C            Enter the number corresponding to the option you choose.aD            If you enter option 2 or 3, the procedure prompts you forC            the printer queue name. It then prints a message showing 5            that the job has been queued for printing.o  #            *Queue name [SYS$PRINT]:   F            Job DTROXX (queue YOURSYS_DQS$PRINT, entry 1248) started on            YOURSYS_DQS$PRINT  =            The procedure now asks if you want to continue the             installation.  9            *Do you want to continue the installation [N]?o  ,            If you want to continue, enter Y.  B            If you selected one of the print options, you must waitC            until the release notes finish printing before you entertC            N or press the RETURN key. If you did not select a print D            option and wish to exit, enter N or press the RETURN key.  8      2.4 Answering Questions About Oracle CDD/Repository  G            DATATRIEVE removed the dependency from Oracle CDD/Repository D            by supporting a new textfile-based dictionary in additionB            to Oracle CDD/Repository. At installation time you willC            be asked whether you want to link DATATRIEVE with Oracle5!            CDD/Repository or not:   A            * Do you want support for Oracle CDD/Repository [Yes]?G  A            If you type Yes you can dynamically enable and disableaD            Oracle CDD/Repository at run time. If you type No, Oracle@            CDD/Repository will not be supported and it cannot be            enabled at run time.   B      2.5 Answering Questions About the DATATRIEVE object libraries#          (OpenVMS VAX systems only)   @            DATATRIEVE Version 7.2A is built using several objectD            libraries which can also be used to customize DATATRIEVE.C            On OpenVMS VAX systems, up to DATATRIEVE version Version @            7.2A, the object modules in these libraries have beenD            built with the VAX C compiler. The installation procedureA            now asks whether you wish to install the product using_D            the object libraries built with the VAX C compiler or the  *      2-6 DATATRIEVE Installation Procedure o  s      H                                        DATATRIEVE Installation ProcedureH  About        the DATATRIEVE object libraries (OpenVMS VAX systems only)  G               DEC C compiler. There is no functional difference for the F               ordinary user. This only affects those users who programG               their own customizations in the C language on OpenVMS VAX ,               systems and relink DTRSHR.exe.  F                   The DATATRIEVE product is built using several objectJ                   libraries which can also be used to customize DATATRIEVEM                   to suit your needs (see theDATATRIEVE documentation manual,eS                   'Guide to Programming and Customizing').   These object librarieseM                   are now built using the DEC C compiler.    If you have beeniT                   programming your own customizations and wish to continue using theN                   VAX C compiler, you have the option of installing the objectN                   libraries which have been built using that compiler instead.  H                   If you answer YES to this question, DATATRIEVE will beR                   linked with the VAX C RTL, and the libraries in DTR$LIBRARY will@                   contain objects built with the VAX C compiler.  G                   If you answer NO to this question, DATATRIEVE will betR                   linked with the DEC C RTL, and the libraries in DTR$LIBRARY will<                   contain objects built with DEC C compiler.  I                   Unless you customize your use of DATATRIEVE and want toiP                   continue using the VAX C compiler for your own customizations,-                   answer NO to this question:B  S               * Do you want to install DATATRIEVE using object libraries built with '                 the VAX C compiler[NO]?   H         You should accept the default answer unless you wish to continue@         compiling your customizations with the VAX C compiler.<>  G         2.6 Answering Questions About the Licensing Management Facility              (LMF).  E               DATATRIEVE Version 7.2A supports the License ManagementiF               facility provided by OpenVMS. The installation procedureC               asks whether you have registered and loaded a ProductD2               Authorization Key (PAK) as required.            H                                    DATATRIEVE Installation Procedure 2-7    M      &      DATATRIEVE Installation ProcedureJ      2.6 Answering Questions About the Licensing Management Facility (LMF)  2                     Product:       DTR or DTR-USER  *                     Producer:      DIGITAL  /                     Version:       Version 7.2A   .                     Release Date:  22-OCT-1997  C            * Does this product have an authorization key registered             and loaded?  B            If you answer Y or YES, the procedure continues. If you=            answer N or NO, you receive the following message:   I            You have not registered the LMF authorization key as required.aC            The DATATRIEVE installation will continue.  However, you @            cannot run the product until you register the license            authorization key.d  @            When the DATATRIEVE installation is completed, pleaseF            register the authorization key using the following command:  #            $ @SYS$UPDATE:VMSLICENSEi  K            The IVP cannot be run until the authorization key is registered.NJ            However, the IVP command file will be put in the same directoryJ            as the UETPs.  Once you register the authorization key, you mayG            run the IVP by entering DATATRIEVE and issuing the followingr            command:   /            @SYS$COMMON:[SYSTEST.DTR]DTR$IVP.COMl  A            The installation continues with a series of DATATRIEVE             questions.a  ?      2.7 Answering Questions During the DATATRIEVE InstallationE  D            The installation procedure asks you a number of questions<            concerning default installation, forms management;            products, multiple DATATRIEVE installations, and A            DATATRIEVE files. The following sections give examplesa            of these questions.      *      2-8 DATATRIEVE Installation Procedure s  l      H                                        DATATRIEVE Installation ProcedureH               2.7 Answering Questions During the DATATRIEVE Installation  B               2.7.1 Installing DATATRIEVE with the Default Answers  H               The installation procedure now asks if you want to installA               DATATRIEVE using default answers for all questions.s  F                 ________________________Note  ________________________  A                 While this question may simplify the installation/=                 procedure, it may not be appropriate for yourtD                 situation. For example, if your system supports moreD                 than one installation of this version of DATATRIEVE,>                 you should not select the default installationA                 option. Read the summary of the default responsese@                 that follows the question before you choose this                 option.   E                 _____________________________________________________   G               The installation procedure prompts you with the following                question:r  J               *Do you want to use default answers for all questions [Yes]?  B               If you type Y, the DATATRIEVE installation procedure/               automatically does the following:   H               o  Performs a complete installation of DATATRIEVE; it willG                  not allow a partial installation to provide DATATRIEVEt!                  support for LSE.u  B               o  Checks your system for a forms management productA                  (Compaq FMS or VAX TDMS). If DATATRIEVE does noth@                  find either of them, the automatic installationF                  procedure provides support only for DECforms, if this,                  is available on the system.  G                  If either Compaq FMS or VAX TDMS already exists on thexD                  system, DATATRIEVE in addition to DECforms support:  F                  -  Supplies Compaq FMS support, if only Compaq FMS is!                     on the systemL  E                  -  Supplies VAX TDMS support, if only VAX TDMS is onL                     the system  E                  -  Supplies VAX TDMS support, if both Compaq FMS and 4                     VAX TDMS are found on the system  H                                    DATATRIEVE Installation Procedure 2-9 T  N      &      DATATRIEVE Installation Procedure?      2.7 Answering Questions During the DATATRIEVE Installation   C            o  Does not prompt you for the unique 1- to 26-character B               suffix that identifies the DTR32xx.EXE image of thisC               installation. Note that if you have already installedRD               this version of DATATRIEVE and did not supply a suffixA               during that installation, you will need a suffix to B               differentiate the image of the previous installation?               from the image currently being installed. In suche?               a case, the default installation procedure is noto               appropriate.  B            o  Does not prompt you for the default image to be used?               with the DATATRIEVE DCL command and DCL help. Thei*               default image will be DTR32.  =            o  Checks if the DATATRIEVE remote server has beenbC               defined by a previous installation of DATATRIEVE. TheeE               DATATRIEVE remote server is called the Distributed Data +               Manipulation Facility (DDMF).   E               When the installation procedure checks for a previously_               defined DDMF:_  E               -  If there is no remote server or if the remote serverBC                  is obsolete, the DDMF files from this installation 9                  become the remote server for DATATRIEVE.c  C               -  If there is a current remote server already on theT@                  system, the default installation procedure usesC                  that as the remote server for this installation of                   DATATRIEVE.  9            o  Copies the NEWUSER.COM file in DTR$LIBRARY.x  B            o  Checks the status of the DCL help for DATATRIEVE. If@               DCL help is unavailable or out-of-date, DATATRIEVE-               automatically updates DCL help.F  >            o  Installs DTRSHR.EXE, DTRMSGS.EXE, DTR32.EXE, and1               DDMF.EXE (if applicable) as SHARED.   )            o  Installs DTRHELP as SHARED.s  D            o  Supplies the plot definitions for the current version.  B            o  Does not supply the optional text and message files,E               sample programs, and callable programming aids that canu0               be tailored at the installed site.  +      2-10 DATATRIEVE Installation ProcedureF O  1      H                                        DATATRIEVE Installation ProcedureH               2.7 Answering Questions During the DATATRIEVE Installation  <               o  Purges files replaced by this installation.  F               If you type N, the installation procedure continues with&               the questions about LSE.  /               2.7.2 Installing with LSE Support   H               To use LSE with DATATRIEVE , LSE must already be installed@               and licensed on your system. If LSE is not alreadyH               installed on your system, you see the following message on               your screen:  K                   *********************************************************e  9                   The LSE Editor is not installed on youre9                   system.  To have LSE support, you must:   0                       1.  Install the LSE Editor;                       2.  Install or reinstall this product   K                   *********************************************************F  >               * Do you want to continue the installation [No]?  @               If you enter Y or YES, the installation continues;G               however, you will not be able to use LSE with DATATRIEVE.1B               If you enter the default value by entering N, NO, orB               by pressing the RETURN key, the installation aborts,G               giving you the opportunity to install LSE on your system.lA               Once LSE is installed, you can begin the DATATRIEVEdB               installation procedure from the beginning. If LSE isD               already installed on your system, you will be prompted!               with the following:   2                   LSE is installed on your system.  5                   You now have the following options:   J                        1.  Do a complete DATATRIEVE installation including6                            DATATRIEVE support for LSE.  E                        2.  Do only DATATRIEVE support for LSE withoutt1                            installing DATATRIEVE.i  I                        3.  Do a DATATRIEVE installation without includingt6                            DATATRIEVE support for LSE.  #               *  Select option [1]:   H                                   DATATRIEVE Installation Procedure 2-11 n  c      &      DATATRIEVE Installation Procedure?      2.7 Answering Questions During the DATATRIEVE InstallationR  =            If you want to install a new version of DATATRIEVE E            (including LSE support), select option 1. If you want onlyrD            to provide DATATRIEVE support for LSE (without installing@            a new version of DATATRIEVE), select option 2. If youB            want to install a new version of DATATRIEVE without LSEA            support, select option 3. If you select option 2, thisqC            installation will terminate after DATATRIEVE support forl            LSE is provided.   <            2.7.3  Installing with Support for Forms Products  B            Each installation of DATATRIEVE on a system can support)            two forms management products:               o  DECforms  >            o  Compaq FMS (Forms Management System) or VAX TDMS/               (Terminal Data Management System)s  A            DECforms software is dynamically loaded at runtime and >            no specific operations are required at installation@            time. This means that DECforms, whenever installed on@            the system, is always available, while Compaq FMS andC            VAX TDMS are optional and mutually exclusive. You selectc7            Compaq FMS or VAX TDMS at installation time.c  D            A series of questions determines which product DATATRIEVE@            will support for the image currently being installed.  C            The installation procedure checks which forms managementeE            products are on the system. If no forms products are found1@            (or only lower versions of VAX TDMS or Compaq FMS not?            supported by DATATRIEVE are found), the installationa4            procedure displays the following message:                      +      2-12 DATATRIEVE Installation Procedure            H                                        DATATRIEVE Installation ProcedureH               2.7 Answering Questions During the DATATRIEVE Installation  K                   *********************************************************M  H                   Neither Compaq FMS nor VAX TDMS product has been foundE                   on this system. If desired, the installation may beoG                   aborted at this point to install either Compaq FMS orr                   VAX TDMS.i  ;                   If the installation continues, DATATRIEVE ;                   will be built with DECforms support only.oG                   The DECforms support will be automatically available, E                   provided that DECforms is installed and licensed byr1                   the time DATATRIEVE is invoked.   K                   *********************************************************A  D               * Do you wish to continue with the installation [YES]?  E               If you type Y or press the RETURN key, the installationRD               continues with the series of questions about more thanB               one installation of this version of DATATRIEVE. (SeeB               Section 2.7.4, Specifying Suffixes for More than OneA               Installation of This Version of DATATRIEVE for morep               information.)f  C               If you type N, the installation aborts, giving you anyD               opportunity to install a forms product on your system.  D               If one or more forms products are found, you receive aC               listing of the products on your system, followed by ap<               message and question similar to the following:  <                   DATATRIEVE can be built to support any one?                   of these products, or, if desired, DATATRIEVETD                   can be built without support of any of these Forms&                   Management products.  >               * Do you want DATATRIEVE to support one of these               products [YES]?e  F               If you do not want forms support, enter N. The installa-H               tion procedure resumes with questions on suffixes and moreB               than one installation of this version of DATATRIEVE.  G               If you do want forms support, enter Y or press the RETURNgB               key. Then, for each forms product on the system, youD               are asked if you want DATATRIEVE to support this formsC               product. Remember each installation of DATATRIEVE can E               support only one forms product in addition to DECforms.   H                                   DATATRIEVE Installation Procedure 2-13 w         &      DATATRIEVE Installation Procedure?      2.7 Answering Questions During the DATATRIEVE Installationn  =            After you enter Y to specify support for one formsi@            product, you do not receive questions about the other            forms products.  C            For example, if you have both VAX TDMS and Compaq FMS on @            the system, you receive the following question first:  I            * Do you wish to have VAX TDMS Forms Management support [YES]?s  @            If you type Y or press the RETURN key, the DATATRIEVE@            image being installed will support VAX TDMS. Then theC            installation procedure moves on to a series of questions E            on suffixes and more than one installation of this versionY            of DATATRIEVE.   B            If you type N, you receive a question about support for            Compaq FMS.  ?            If you type N after each question in the series, youe)            receive the following message:C  >                There are neither Compaq FMS nor VAX TDMS FormsB                Management products on this system. If desired, theC                installation may be aborted at this point to installtA                either Compaq FMS or VAX TDMS. If the installationpF                continues, the questions pertaining to the selection of>                a Forms Management product will be asked again.  A            * Do you wish to continue with the installation [YES]?   B            If you type Y or press the RETURN key, you have anotherC            opportunity to answer questions about forms. If you typey0            N, the installation procedure aborts.  D            2.7.4  Specifying Suffixes for More than One Installation(            of This Version of DATATRIEVE  @            The installation procedure asks whether you intend toA            complete more than one installation of this version oft1            DATATRIEVE on your system, as follows:t          +      2-14 DATATRIEVE Installation Procedure     d      H                                        DATATRIEVE Installation ProcedureH               2.7 Answering Questions During the DATATRIEVE Installation  D                   It is possible to do more than one installation of>                   DATATRIEVE.  More than one installation of aI                   single version may be desirable for a number of reasons                    including:  K                       o  Use of multiple forms management products (such as J                          Compaq FMS and VAX TDMS; DECforms is available in?                          every image, if present on the system)r  I                       o  Use of multiple foreign language translations of >                          DATATRIEVE (such as French or German)  H               * Do you plan to install this version more than once [NO]?  E               If you type N or press the RETURN key, the installation @               procedure continues with questions about retainingC               DATATRIEVE files. (See Section 3.5, Online DATATRIEVE,H               Object Library for more information.) At a later date, youE               can decide to install DATATRIEVE using file names otheraG               than the defaults by typing Y in response to the previousd               question.l  @               If you type Y, the installation procedure displaysC               messages requesting that you specify a suffix for theiH               image you are installing and the default image for the DCL!               command DATATRIEVE.h  E               The following message and question about the suffix arei               displayed:  H                   To differentiate the files and images produced by this@                   installation from those produced by some otherF                   DATATRIEVE installation, it is necessary to append aF                   suffix to some of the file and image names. For eachI                   installation of this version of DATATRIEVE, this suffix.J                   should be unique. This suffix can be 1 to 26 characters.  =               * What is the suffix you intend to use for thisd"               installation [none]?  A               Only one set of DATATRIEVE images and files can uset>               the default file names that have no suffix. (SeeG               Section 1.6.4, More than One Installation of this Version B               of DATATRIEVE for a list of these images and files.)C               If you install this version of DATATRIEVE a second or G               subsequent time, you should identify the subsequent image E               and file names by a unique suffix. This step allows yout  H                                   DATATRIEVE Installation Procedure 2-15           &      DATATRIEVE Installation Procedure?      2.7 Answering Questions During the DATATRIEVE Installation   D            later to identify which version of DATATRIEVE you want to            run..  A            For example, on the first run through the installation_A            procedure, you could respond to the question about theeE            suffix by pressing the RETURN key. The result is that eachhB            of the DATATRIEVE file names includes no suffix. To run6            the image produced by this procedure, type:              $ DATATRIEVEw  ?            During the second or subsequent installation of this @            version of DATATRIEVE, for example, you might use VAXA            TDMS as the forms product supported by this image. You A            could identify the files and images by responding with E            VAX TDMS for the suffix. To run the image produced by thise.            procedure, type the following line:  "            $ DATATRIEVE/VARIANT=XX  B            For the remainder of this manual, the two letters xx atB            the end of a file name stand for the 1- to 26-character            suffix you specify.  C            If you specify the same suffix for a later installation,rB            the later image supersedes the previous image installedD            with the same suffix. If you choose to purge files duringB            the installation, those earlier images will be deleted.A            See Section 2.7.9, Purging Files for more information.P  <            The following message and question are displayed:  J                The DATATRIEVE DCL command allows you to choose which DTR32H                image to execute by means of the /VARIANT qualifier.  YouJ                may now choose an image to be executed by default, when theD                /VARIANT qualifier is not specified on the DATATRIEVEG                command. This default image will be the image referencede                by DCL HELP.P              DTR32, DTR32xxu  G            * Which of the above images should be the default [DTR32xx]:   D            The installation procedure checks which DATATRIEVE imagesE            are on the system. All existing image names, plus the namerE            of the image you are currently installing, are listed. TherD            current image name is provided as the default response to            the question.  +      2-16 DATATRIEVE Installation Procedurep s  e      H                                        DATATRIEVE Installation ProcedureH               2.7 Answering Questions During the DATATRIEVE Installation  D               Only one DATATRIEVE image can be chosen as the defaultG               for the DCL command DATATRIEVE. You must use the /VARIANTbF               qualifier to invoke any other DATATRIEVE image using the%               DCL command DATATRIEVE.   D               For example, on the first run through the installationE               procedure, you could respond to both the question about/B               the suffix and the question about the DCL default byH               pressing the RETURN key. The result is that the image nameD               is DTR32 and that image is the default when you invokeE               DATATRIEVE using the DCL command DATATRIEVE as follows:s                 $ DATATRIEVE  B               During the second or subsequent installation of thisE               version of DATATRIEVE, you might choose VAX TDMS as theeF               suffix. You might then choose DTR32 as the default imageC               name with the DCL command DATATRIEVE. You can use theeE               DCL command DATATRIEVE to invoke the DTR32TDMS image as                follows:  '               $ DATATRIEVE/VARIANT=TDMS   G               If, however, you choose DTR32TDMS as the default with the H               DATATRIEVE DCL command, you must use the VARIANT qualifier3               to invoke the DTR32 image as follows:l  "               $ DATATRIEVE/VARIANT  9               2.7.5 Defining the DATATRIEVE Remote Servera  H               The installation procedure checks if the DATATRIEVE remoteB               server has been defined by previous installations ofH               DATATRIEVE. The remote server for DATATRIEVE is called theE               Distributed Data Manipulation Facility (DDMF). AlthoughbA               there can be several shareable images of DATATRIEVEsH               installed on the same system, there can be only one remote%               server for each system.j  F                 ________________________Note  ________________________  A                 You do not receive the question discussed in thisa=                 section if you are installing DATATRIEVE on aoC                 OpenVMS system without DECnet. If you later install ?                 DECnet, you then need to define a DECnet object >                 for the remote server. See Section 3.6, DECnet  H                                   DATATRIEVE Installation Procedure 2-17 $  R      &      DATATRIEVE Installation Procedure?      2.7 Answering Questions During the DATATRIEVE InstallationO  ?               Considerations for more information on defining at               DECnet object.  C               _____________________________________________________D  B            If no remote server has been defined previously or if aA            previously-defined remote server is obsolete, the DDMFcD            files from this installation become the remote server forB            DATATRIEVE on the system. You do not receive a questionB            about the remote server, and the installation procedureE            continues with questions about the file for new users. SeehC            Section 2.7.6, Creating a DCL Command File for New Usersm             for more information.  C            However, if an up-to-date remote server has already been A            defined (by a previous installation of this DATATRIEVEm<            release, for example), the installation procedure?            asks if the remote server established by the currentdC            installation should be the remote server for the system..@            The DECnet object number for DDMF is defined as 30 by@            the installation procedure. You receive the following            question:  K            * Do you want DDMFxx.EXE to be used for distributed access [NO]?   B            Type Y if you want the remote server (DDMF) establishedB            by the current installation to be the remote server forC            your system. You might want to type Y if this image willh?            contain options that users on remote systems need tolA            access frequently, for example, user-defined functionssA            that PDP-11 users need to access. In such cases, it isaA            more efficient to make the remote server file for thisy3            image the remote server for your system.n  D            Type N or press the RETURN key if these considerations do8            not apply to this installation of DATATRIEVE.  ;            2.7.6  Creating a DCL Command File for New Usersa  =            The installation procedure now copies the new user ?            file, NEWUSER.COM, to DTR$LIBRARY. NEWUSER.COM helpseA            new users get started with DATATRIEVE by providing the D            necessary files to perform the examples in the DATATRIEVEB            documentation set. Users can invoke the NEWUSER command            file by entering:  +      2-18 DATATRIEVE Installation Procedurew r         H                                        DATATRIEVE Installation ProcedureH               2.7 Answering Questions During the DATATRIEVE Installation  $               $ @DTR$LIBRARY:NEWUSER  B               This procedure copies the DATATRIEVE data files fromF               DTR$LIBRARY to your directory and creates the DATATRIEVED               objects in your Oracle CDD/Repository dictionary (whenG               Oracle CDD/Repository support is available) or in a user-n*               specified OpenVMS directory.  ,               2.7.7 Installing Shared Images  F               DATATRIEVE runs most efficiently when all its executableH               images are installed as shareable images. The installationB               procedure lets you choose not to do so, however. TheC               installation procedure prompts you with the followingwG               question. Note that the file SYS$STARTUP:DTRSTUPxx.COM ise0               built according to your responses.  H               * Do you want DTRSHRxx.EXE and DTRMSGS.EXE to be installed               SHARED [YES]?s  ?               For best performance, the images DTRSHRxx.EXE andrH               DTRMSGS.EXE should be installed as SHARED. Type Y or pressH               the RETURN key if you want these images to be installed as               SHARED.u  B               The second question about shareable images refers toD               DTR32xx.EXE. For best performance, this should also be"               installed as SHARED.  E               * Do you want DTR32xx.EXE to be installed SHARED [YES]?_  F               Type Y or press the RETURN key if you want this image to"               be installed SHARED.  G               For best performance in environments where you anticipate F               extensive use of the distributed features of DATATRIEVE,F               the image DDMFxx.EXE should also be installed as SHARED.D               If the DDMF from this installation is to be the remote9               server, you receive the following question:e  D               * Do you want DDMFxx.EXE to be installed SHARED [YES]?  F               Type Y or press the RETURN key if you want this image to%               be installed as SHARED.h  H                                   DATATRIEVE Installation Procedure 2-19           &      DATATRIEVE Installation Procedure?      2.7 Answering Questions During the DATATRIEVE Installation   C               ________________________Note ________________________   A               You do not receive the question about DDMFxx.EXE if A               you are installing DATATRIEVE on a system that does ?               not have DECnet. If you later install DECnet, seesA               Section 3.6, DECnet Considerations for instructions 8               on running the DDMFxx.EXE image as SHARED.  C               _____________________________________________________y  C            2.7.8  Installing Plot Definitions and Optional Materiale  E            The installation procedure continues with a question aboutA?            plot definitions for DATATRIEVE graphics. DATATRIEVE ?            contains graphics features you can use with a VT125, B            VT240, VT330, or VT340 terminal or on a workstation. To@            use these features, you must request plot definitions            during installation.A  C               ________________________Note ________________________i  >               If this is your first installation of DATATRIEVE9               since Version 3.4, you must answer Y to thea;               following question. The plot definitions were B               modified with Version 4.0. Plot definitions provided@               with DATATRIEVE installations prior to Version 4.0>               are not compatible with DATATRIEVE Version 7.2A.  C               _____________________________________________________h  /            The following question is displayed:   <            * Do you wish to have the plot definitions [YES]?  A            Type Y or press the RETURN key if you want the instal-tA            lation procedure to include plot definitions. The plothC            definitions are installed in a Oracle CDD/Repository DMU C            dictionary, in CDD$TOP.DTR$LIB.PLOTS when DEC DATATRIEVE A            is installed with Oracle CDD/Repository support. Theiro>            textfile definitions to be used when CDD/Repository=            support is not available or disabled are copied tot8            SYS$SYSDEVICE:[VMS$COMMON.DTR.DTR$LIB.PLOTS].  A            The next question pertains to components of DATATRIEVE >            that can be tailored at the installation site. This>            optional material includes Data Access Blocks filesB            (used with Callable DATATRIEVE), the DATATRIEVE message  +      2-20 DATATRIEVE Installation Procedure- e  A      H                                        DATATRIEVE Installation ProcedureH               2.7 Answering Questions During the DATATRIEVE Installation  C               file (necessary for customizing DATATRIEVE messages), F               sample programs and the files necessary for creating and1               maintaining user-defined functions.e  ?               The following message and question are displayed:n  M                   Some optional material is available with this kit includingAF                   the components of DATATRIEVE that can be tailored at%                   the installed site.P  7               * Do you want the optional material [NO]?D  @               Type Y if you want this material. The installationC               procedure loads these files in DTR$LIBRARY. If you dorE               not want this material, type N or press the RETURN key.   B               After you respond to this question, the installationE               procedure continues with a question about purging filese5               replaced by the installation procedure.   !               2.7.9 Purging Filesh  E               The installation procedure continues with the following*               question:*  O               * Do you want to purge files replaced by this installation [YES]?   C               If you wish, you can have all files that were created B               by this installation procedure purged in the variousF               directories where they were created. No files are purgedH               except those created in this installation. Type Y or press0               the RETURN key to purge the files.  $               2.7.10 Running the IVP  C               The last question regarding the installation concernseF               the IVP. You can choose whether to run the IVP after theF               installation or not. The following message is displayed:              H                                   DATATRIEVE Installation Procedure 2-21           &      DATATRIEVE Installation Procedure?      2.7 Answering Questions During the DATATRIEVE Installationi  2              The DATATRIEVE IVP will be put in theD              SYS$COMMON:[SYSTEST.DTR] directory. You may run the IVPK              immediately after the completion of the installation procedure D              answering YES to the next question or later issuing the              following command:c  ;              @SYS$COMMON:[SYSTEST.DTR]DTR$IVP.COM DTRxx.EXE   E            * Do you want to run the IVP after the installation [YES]? 2            * Proceed with this installation [YES]?  C               ________________________Note ________________________d  A               The PAK must be registered before either the IVP or @               any of the UETPs can be run. If you answered no to@               the following question, the message about IVP willB               not be displayed and the IVP will not be run at this               time:t  F               * Does this product have an authorization key registered               and loaded?p  C               _____________________________________________________E  #      2.8 Finishing the Installation   ?            If you did not request the default installation, the *            following message is displayed:  L                All questions regarding the installation have now been asked.  C                The installation of DATATRIEVE will now continue forr(                20 minutes to 40 minutes.  A            If the DTRFNDxx.MAR file provided by this installation D            is newer than an existing one, the installation procedure.            will display the following message:  2            An existing DTRFNDxx.MAR has been found2            on the system, but its version does not9            match the current level for this installation.a5            The existing DTRFNDxx.MAR and DTRFUNxx.OLBo,            have been respectively renamed to'            DTR$LIBRARY:DTRFNDxx.OLD ande$            DTR$LIBRARY:DTRFUNxx.OLD.  B            See Section 3.7, Maintaining User-Defined Functions forB            more information on maintaining user-defined functions.  +      2-22 DATATRIEVE Installation Procedure  s  e      H                                        DATATRIEVE Installation ProcedureH                                           2.8 Finishing the Installation  C               During installation, you should receive the followinge               message:  8                   During the installation, a file called>                   DTRSTUPxx.COM has been added to SYS$STARTUP:M                   The site-dependent startup file, SYS$MANAGER:SYSTARTUP.COM, 7                   should have the following line added:r  3                        $ @SYS$STARTUP:DTRSTUPxx.COM   ?               Be sure to update SYS$MANAGER:SYSTARTUP.COM afters               installation.n  E               On OpenVMS VAX systems Version 5.4 or earlier, the file*:               SYSTARTUP.COM is called SYSTARTUP_V5.COM. <>  H               The installation procedure next displays information aboutF               User Environment Test Packages (UETPs). The installationB               provides up to five UETPs, depending on the optionalD               products already on the system ( VAX TDMS, Compaq FMS,D               Oracle CODASYL DBMS, Oracle Rdb) and your responses toC               the questions about forms products and plots. Besides D               a general test of DATATRIEVE, there are also UETPs for@               plots, forms, Oracle Rdb, and Oracle CODASYL DBMS.  G               The installation displays a message showing how to invokeu$               each UETP it provides:                                    H                                   DATATRIEVE Installation Procedure 2-23 t  s      &      DATATRIEVE Installation Procedure#      2.8 Finishing the Installationo  H            *************************************************************  <            DATATRIEVE User Environment Test Packages (UETPs)F            have been provided and can be run after the installation isB            complete.  They are invoked from DATATRIEVE as follows:  A            DTR> @sys$common:[systest.dtr]DTR   ! The general teste?            DTR> @sys$common:[systest.dtr]plots ! The plots testiM            DTR> @sys$common:[systest.dtr]dbms  ! The Oracle CODASYL DBMS test D            DTR> @sys$common:[systest.dtr]rdb   ! The Oracle Rdb test?            DTR> @sys$common:[systest.dtr]forms ! The Forms test,  E            Before invoking these files from a user's account you musto"            execute the procedure :%              @DTR$LIBRARY:NEWUSER.COM C            This procedure loads the DATATRIEVE definitions into the H            user's dictionary and the data files in the user's directory.?            This procedure must be executed by each user needingi#            the DATATRIEVE examples. H            *************************************************************  <            The file type for the UETP files in the directory,            SYS$COMMON:[SYSTEST.DTR] is .DTR.  B            Chapter 4, User Environment Test Packages discusses the            test packages.   C            The installation procedure now runs the general IVP test C            and, if you chose to run the IVP after the installation, -            it displays the following message:   6            Executing IVP for:  DATATRIEVE Version 7.2A  *            Running the general IVP test...*                Test completed successfully  4                *************************************  &                DATATRIEVE Version 7.2A  )                IVP COMPLETED SUCCESSFULLYt  4                *************************************  6            IVP completed for:  DATATRIEVE Version 7.2A  ?            When the installation procedure is finished, controlT6            returns to the command procedure VMSINSTAL.  +      2-24 DATATRIEVE Installation ProcedureE                       H                                                                        3H         ________________________________________________________________  H                                          Postinstallation Considerations      D               This chapter discusses some important postinstallationB               considerations concerning DECnet, operating systems,B               relational databases, Oracle CODASYL DBMS databases,D               and user-defined functions. This chapter also containsF               information on installing DATATRIEVE Client for Windows.  .         3.1 Updating SYS$MANAGER:SYSTARTUP.COM  H               During installation, a file called DTRSTUPxx.COM was addedC               to SYS$STARTUP. Note that xx represents the 1- to 26- E               character suffix you specify during installation. AfteroF               installation, you must update the site-dependent startupD               file SYS$MANAGER:SYSTARTUP.COM by adding the following               line:a  *               $ @SYS$STARTUP:DTRSTUPxx.COM  0         3.2 VAXcluster Considerations (VAX Only)  C               If you are installing DATATRIEVE on a VAXcluster, therH               shareable image created by this installation of DATATRIEVEG               is available only from the node where the installation isiF               done. Therefore, after the installation is complete, youD               should repeat the following steps on each of the otherD               nodes in the VAXcluster where DATATRIEVE will be used:  G               1. Issue the LICENSE LOAD command to activate the OpenVMS                   license.   H               2. Execute the DATATRIEVE startup command file as follows:  -                  $ @SYS$STARTUP:DTRSTUPxx.COMr      H                                      Postinstallation Considerations 3-1           $      Postinstallation Considerations-      3.2 VAXcluster Considerations (VAX Only)   D            3. Install the new version of DCLTABLES.EXE that has beenD               updated to include the DCL command DATATRIEVE. Install"               the file as follows:                 $ INSTALL 2               INSTALL> REPLACE SYS$SHARE:DCLTABLES  E            The second step is not necessary if you plan to reboot the[@            entire VAXcluster after the installation is complete.  D      3.3 Moving the DATATRIEVE Environment Between Operating Systems  B            To move your DATATRIEVE environment from an OpenVMS VAX?            system to an OpenVMS Alpha system, do the following:l  B            o  Copy all DATATRIEVE data files and procedures to the               other system.   B            o  If your application programs use the DATATRIEVE Call@               Interface, or if you have customized DATATRIEVE by@               modifying certain source files, you must recompileD               and relink the application programs and the DATATRIEVE)               customization source files.o  B            o  For DATATRIEVE related products (for example, Oracle@               CDD/Repository, DECforms), refer to their specific               documentation.  D            o  To migrate OpenVMS VAX applications calling DATATRIEVEB               via the DEC Migrate utility (VEST), refer to the DEC,               DATATRIEVE V7.1 Release Notes.  (      3.4 Updating Process Command Tables  ?            The DATATRIEVE installation creates a new version ofEA            DCLTABLES.EXE including the DCL command DATATRIEVE. Toa@            use the DCL command DATATRIEVE, users must log out ofB            their processes and log back in to update their process            command tables.            (      3-2 Postinstallation Considerations a         H                                          Postinstallation ConsiderationsH                                     3.5 Online DATATRIEVE Object Library  ,         3.5 Online DATATRIEVE Object Library  E               The installation keeps the library online in case it ist5               necessary to relink a DATATRIEVE image.   7               You may have to relink DATATRIEVE if you:o  G               o  Add a user-defined function (however it is possible to-F                  add user functions stored in shareable images without+                  relinking DEC DATATRIEVE).t  5               o  Customize the text file DTRTEXT.MAR.A  I               o  Install or patch a new version of Oracle CDD/Repository.rF                  (Check the Oracle CDD/Repository documentation to seeE                  if relinking is necessary.) This only applies if DEC H                  DATATRIEVE was installed with the Oracle CDD/Repository                  support.   G               o  Install a new version of the OpenVMS Run-Time Library.   5               o  Install a new version of Compaq FMS.   G               You may enter the following command to relink DATATRIEVE:   %               $ @DTR$LIBRARY:DTRBLDxxo  !         3.6 DECnet Considerationsc  C               This section describes what you need to do to run theTC               DATATRIEVE remote server if DECnet is installed afteroC               DATATRIEVE on a OpenVMS system. It also describes howXD               to create a default DECnet account for remote users of(               DATATRIEVE on your system.  ,               3.6.1 Defining a DECnet Object  F               DECnet is normally installed on a OpenVMS system. UnlessH               you install DATATRIEVE on a OpenVMS system without DECnet,G               the installation procedure automatically defines a DECnet 6               object for the DATATRIEVE remote server.  D               However, if you install DATATRIEVE on a OpenVMS systemC               that does not have DECnet, the installation procedure:A               cannot use the DECnet Network Control Program (NCP)w  H                                      Postinstallation Considerations 3-3    u      $      Postinstallation Considerations      3.6 DECnet Considerations  <            utility[1], or the Network Control Language (NCL)0            utility[2] to define a DECnet object.  D            This section describes how to use NCP and NCL to define aE            DECnet object for the remote server if DECnet is installedt8            on your system after DATATRIEVE is installed.  E            The remote server for DATATRIEVE is called the Distributedx>            Data Manipulation Facility (DDMF). The installationB            procedure creates two files, DDMFxx.EXE and DDMFxx.COM,A            in SYS$SYSTEM. In a DECnet Phase IV network, to defineoA            a DECnet object for DDMFxx.EXE and assign it an object 5            number of 30, type the following commands:a              $ NCP == "$NCP"-            $ NCP DEFINE OBJECT DDMF NUMBER 30n*            $ NCP SET OBJECT DDMF NUMBER 303            $ NCP DEFINE OBJECT DDMF FILE DDMFxx.COM 0            $ NCP SET OBJECT DDMF FILE DDMFxx.COM  A            In a DECnet/OSI network, to define a DECnet object foreD            DDMFxx.EXE and assign it an object number of 30, type the            following commands:              $ NCL == "$NCL"8            $ NCL CREATE SESSION CONTROL APPLICATION DDMFI            $ NCL SET SESSION CONTROL APPLICATION DDMF ADDRESS=(NUMBER=30) K            $ NCL SET SESSION CONTROL APPLICATION DDMF IMAGE NAME=DDMFxx.COM   B            Note that, in a DECnet/OSI network, if the account usedC            to perform the DATATRIEVE installation does not have the B            NET$MANAGE right identifier, you cannot create the DDMFB            session control application. Therefore you must use the@            Authorize Utility to grant the installing account the#            NET$MANAGE access right:   0            UAF> GRANT/ID NET$MANAGE account-name  C            In the example "account-name" is the name of the accountR7            used to perform the DATATRIEVE installation.               ___________________B            [1]       For DECnet Phase IV environments, you use theC                      Network Control Program to configure, control,i  3                      monitor, and test the network.sE            [2]       For DECnet/OSI environments, you use the Networkg  @                      Control Language to perform the same tasks.  (      3-4 Postinstallation Considerations           H                                          Postinstallation ConsiderationsH                                                3.6 DECnet Considerations  G               The procedure to grant the correct DECnet/OSI identifierss@               is explained in more details in DECnet/OSI Network               Management.   G               For best performance in environments where you anticipate F               extensive use of the distributed features of DATATRIEVE,@               you should run the remote server as SHARED. To runC               the image DDMFxx.EXE as a SHARED image, edit the file B               SYS$STARTUP:DTRSTUPxx.COM. This file begins with the               following lines:                 $!+ +               $!   DATATRIEVE Start-up Filei               $!-   G               Check the file for the following line and add it if it is                 not already there:  ?               $ DTR$INSTALL := $SYS$SYSTEM:INSTALL/COMMAND_MODEI  E               You will see a dollar sign and the word exit at the endnG               of the file. Enter the following text on the line above $_               exit:_  3               ADD/OPEN/SHARED SYS$SYSTEM:DDMFxx.EXE   E               3.6.2 Creating a Default DECnet Account for Distributeds               Access  G               The installation procedure defines a DECnet object called H               DDMF and assigns it the number 30. After the installation,C               you may want to create a default DECnet account, suchnA               as DTR$DECNET, for this DECnet object. Remote users D               can then omit the user name and password from the node@               specification when accessing domains on your node.  F                 ________________________Note  ________________________  ?                 This section applies to systems on which DECnetlA                 was installed before DATATRIEVE. If DATATRIEVE isb@                 installed on a OpenVMS system that does not haveC                 DECnet, you cannot define a default DECnet account.eB                 If DECnet is installed afterwards, you must define>                 a DECnet object (see Section 3.6.1, Defining aD                 DECnet Object before you can create a default DECnet                 account.  E                 _____________________________________________________e  H                                      Postinstallation Considerations 3-5 a  w      $      Postinstallation Considerations      3.6 DECnet Considerations      B            If you wish to set up such a default DECnet account for2            distributed access, follow these steps:  ?            1. Add an entry to the user authorization file (UAF)tB               on your system for DTR$DECNET. Specify the same fileE               limits and quotas as you would for any other DATATRIEVE                user.i  A            2. Invoke NCP (or NCL) to associate DDMF (known objectdE               30) with the default DECnet account DTR$DECNET. Use thesE               DEFINE OBJECT command in NCP (or the CREATE/SET SESSIONO?               CONTROL APPLICATION command in NCL) to modify thevE               object parameters for DDMF in the permanent database onA               your system.  B            You can use the following sample session as a model for?            your own system. Note that for security reasons, you A            should use a different password than the one provided.nD            Also note that the UIC used in the sample session is usedB            to illustrate the command; you should use a UIC that is'            appropriate for your system.d  !            $ auth == "$authorize"R#            $ set default sys$system             $ auth 1            UAF> ADD DTR$DECNET/OWNER="DATATRIEVE"a)            user record successfully addedr7            UAF> MODIFY DTR$DECNET/PASSWORD=ANY_PASSWORDc!            user record(S) updated M            UAF> MODIFY DTR$DECNET/DEVICE=SYS$SYSDEVICE/DIRECTORY=[DTR$DECNET]c!            user record(S) updated /            UAF> MODIFY DTR$DECNET/UIC=[376,376]s!            user record(S) updatedr5            UAF> MODIFY DTR$DECNET/FILLM=60/ENQLM=2000 !            user record(S) updatedo;            UAF> MODIFY DTR$DECNET/WSDEFAULT=350/WSQUOTA=350a!            user record(S) updatedM)            UAF> MODIFY DTR$DECNET/PRCLM=0 !            user record(S) updateduK            UAF> MODIFY DTR$DECNET/FLAGS=(DISCTLY, DEFCLI, LOCKPWD, CAPTIVE)]!            user record(S) updatedm)            UAF> MODIFY DTR$DECNET/NOBATCH !            user record(S) updatede  (      3-6 Postinstallation Considerations    U      H                                          Postinstallation ConsiderationsH                                                3.6 DECnet Considerations  "               UAF> SHOW DTR$DECNET  <         Username: DTR$DECNET              Owner:  DATATRIEVEG         Account:                          UIC:    [376,376] ([376,376]) ;         CLI:      DCL                     Tables: DCLTABLESm,         Default:  SYS$SYSDEVICE:[DTR$DECNET]         LGICMD:   LOGINr3         Login Flags: Disctly Defcli Lockpwd Captive +         Primary days:   Mon Tue Wed Thu Friu3         Secondary days:                     Sat SunEN         Primary   000000000011111111112222  Secondary 000000000011111111112222N         Day Hours 012345678901234567890123  Day Hours 012345678901234567890123N         Network:  ##### Full access ######            ##### Full access ######N         Batch:    -----  No access  ------            -----  No access  ------N         Local:    ##### Full access ######            ##### Full access ######N         Dialup:   ##### Full access ######            ##### Full access ######N         Remote:   ##### Full access ######            ##### Full access ######I         Expiration:            (none)    Pwdminimum:  6   Login Fails:  0 F         Pwdlifetime:        180 00:00    Pwdchange:      (pre-expired)H         Last Login: (none) (interactive),       (none) (non-interactive)A         Maxjobs:         0  Fillm:        60  Bytlm:        25000.A         Maxacctjobs:     0  Shrfillm:      0  Pbytlm:           0gA         Maxdetach:       0  BIOlm:        18  JTquota:       1024_A         Prclm:           0  DIOlm:        18  WSdef:          350gA         Prio:            4  ASTlm:        24  WSquo:          350tA         Queprio:         0  TQElm:        10  WSextent:      1000iA         CPU:        (none)  Enqlm:      2000  Pgflquo:      40000r         Authorized Privileges:           TMPMBX NETMBX2         Default Privileges:o           TMPMBX NETMBX                  UAF> EXIT,!               SYSUAF.DAT modified E               $ CREATE/DIR/OWN = [376,376] SYS$SYSDEVICE:[DTR$DECNET]_               $ NCP == "$NCP"i               $ NCPt#               NCP> LIST OBJECT DDMFA              H                                      Postinstallation Considerations 3-7    s      $      Postinstallation Considerations      3.6 DECnet Considerations  ?            Object Permanent Summary as of  01-OCT-1990 15:31:09n              Object = DDMF  (            Number                   = 30.            File id                  = DDMF.COM  H            NCP> DEFINE OBJECT DDMF USER DTR$DECNET PASSWORD ANY_PASSWORD             NCP> LIST OBJECT DDMF  ?            Object Permanent Summary as of  01-OCT-1990 15:31:09r              Object = DDMF  (            Number                   = 30.            File id                  = DDMF.COM0            User id                  = DTR$DECNET2            Password                 = ANY_PASSWORD  %            NCP> SET KNOWN OBJECTS ALL             NCP> EXIT            $  D            If after the command SHOW DTR$DECNET, you notice that theE            DISUSER flag is set, you must remove it with the followingi            command:S  -            UAF> SET DTR$DECNET/FLAG=NODISUSER   ?            For more information on NCP, NCL and DECnet, see the E            DECnet for OpenVMS Guide to Networking, the DECnet/OSI foroD            OpenVMS Programming and the DECnet for OpenVMS Networking            Manual.  =            As always, when working in a remote, or networking @            environment, follow the security guidelines described/            in the Guide to VMS System Security..  +      3.7 Maintaining User-Defined Functionst  A            If this is your first installation of DATATRIEVE sincemC            Version 4.1, and if your site maintains site-specific or D            user-defined functions, you should complete the following5            steps to re-enable user-defined functions.l  B            After an initial installation of DATATRIEVE Version 4.2A            or higher, DATATRIEVE will always use the DTRFNDxx.MARtB            and DTRFUNxx.OLB files that are on the system. You will  (      3-8 Postinstallation Considerations    ]      H                                          Postinstallation ConsiderationsH                                   3.7 Maintaining User-Defined Functions  B               no longer have to re-create and relink DATATRIEVE as(               described in this section.  ?               1. Transfer the user-defined function definitions C                  from DTRFNDxx.OLD (renamed during installation) toeH                  DTRFNDxx.MAR. To do this, edit DTRFNDxx.MAR and add theG                  appropriate definitions. (Merely renaming the old file D                  does not enable user-defined functions in the file.;                  They must be transferred to DTRFNDxx.MAR.)e  >               2. Assemble DTRFNDxx.MAR with the MACRO command:  1                  $ MACRO DTR$LIBRARY:DTRFNDxx.MARr  C                  This command creates the object file DTRFNDxx.OBJ.e  G               3. Replace the object module in the function library with /                  the newly created object file:t  @                  $ LIBRARY/REPLACE DTR$LIBRARY:DTRFUNxx DTRFNDxx  H               4. Skip to the next step if the user-defined functions forD                  your site consist only of calls to OpenVMS Run-TimeB                  Library routines. However, if your site has user-F                  defined functions that call their own routines, thereC                  is an additional step before relinking DATATRIEVE.lF                  The object files for those functions routines must beG                  inserted into the new version of the function library.i  /                  There are two ways to do this:   E                  o  If the object files (.OBJ files) for the routinesiF                     are still available, insert them directly into the%                     function library:   &                     $ LIBRARY/INSERT -?                     _$    DTR$LIBRARY:DTRFUNxx.OLB filename.OBJt  @                  o  If the object files for the routines are notH                     available, extract the modules from the old function?                     library before inserting them into the new:w  G                     $ LIBRARY/EXTRACT=module-name/OUTPUT=filename.OBJ -l2                     _$    DTR$LIBRARY:DTRFUNxx.OLD&                     $ LIBRARY/INSERT -?                     _$    DTR$LIBRARY:DTRFUNxx.OLB filename.OBJi  H                                      Postinstallation Considerations 3-9 _  _      $      Postinstallation Considerations+      3.7 Maintaining User-Defined Functionso               5. Relink DATATRIEVE:  %               $ @DTR$LIBRARY:DTRBLDxxp  C               ________________________Note ________________________n    B               o  If your site maintains no user-defined functions,9                  you may choose to delete the .OLD files.   ?               o  DATATRIEVE is no longer linked with the Compaq )                  Fortran Runtime Library.h  C               _____________________________________________________:  4      3.8 Providing Control Information to DATATRIEVE  <            The logical name DTR$ENVIRONMENT provides control/            information to the DATATRIEVE image.   C            The equivalence name of DTR$ENVIRONMENT is a string thateB            concatenates qualifiers. Currently, only the qualifiers>            /EXIT_ON_PRINT_ERROR and /NOCDD are defined. If theE            equivalence name of DTR$ENVIRONMENT exists and it containsoD            the string qualifier /EXIT_ON_PRINT_ERROR, the DATATRIEVED            interactive image exits when an abnormal condition is metB            while printing output lines. See the following example:  -            $ DATATRIEVE "SHOW CDD$DEFAULT.P1"               PROCEDURE P1o.            READY CDD$TOP.DTR$LIB.DEMO.YACHTS ;            FOR YACHTS                     BEGIN                    PRINT TYPE ;                     FN$WAIT(1) ;d                    END ;            END_PROCEDURE"            $ DIR [NOT_EXISTENT]T.t            )      3-10 Postinstallation Considerations  e  d      H                                          Postinstallation ConsiderationsH                          3.8 Providing Control Information to DATATRIEVE  D               Error opening DTRWRK$DISK:[NOT_EXISTENT]T.T;* as input!               Directory not found                No such fileS               $!-- In the following lines of code, the Interactive DATATRIEVE image U               $!-- continues the execution even if it cannot print to the output files8               $ DEFINE/USER SYS$OUTPUT [NOT_EXISTENT]T.T'               $ DATATRIEVE "EXECUTE P1"M               $ SHOW TIME   "               18-JAN-1996 17:19:528               $ DEFINE/USER SYS$OUTPUT [NOT_EXISTENT]T.T3               $ DATATRIEVE "EXECUTE CDD$DEFAULT.P1"a               $ SHOW TIME   "               18-JAN-1996 17:22:08S               $!-- In the following lines of code, the Interactive DATATRIEVE imagelN               $!-- stops the execution when it fails to print the output lines               $ SHOW TIME   "               18-JAN-1996 17:23:11L               $ DEFINE/USER DTR$ENVIRONMENT "/OPT1/EXIT_ON_PRINT_ERROR/OPT2"8               $ DEFINE/USER SYS$OUTPUT [NOT_EXISTENT]T.t3               $ DATATRIEVE "EXECUTE CDD$DEFAULT.P1"*  -               %RMS-E-DNF, directory not foundv               $ SHOW TIMEP  "               18-JAN-1996 17:23:35  F               If the equivalence name of DTR$ENVIRONMENT exists and itE               contains the string qualifier /NOCDD, DATATRIEVE startsdF               without using the Oracle CDD/Repository dictionary, evenE               if the DATATRIEVE image had been linked with the Oracle!8               CDD/Repository image at installation time.  >         3.9 Preparing to Install DATATRIEVE Client for Windows  J               During installation of DATATRIEVE a file called DTRWN11A.ZIPF               is added to SYS$COMMON:[DTR]. This zip file contains theC               image files required to install DATATRIEVE Client for                Windows.  H               To prepare the disks used to install DATATRIEVE client for/               Windows, use the following steps:b  C               1. Copy the zip file DTRWN11A.ZIP onto your PC drive.   H                                     Postinstallation Considerations 3-11           $      Postinstallation Considerations;      3.9 Preparing to Install DATATRIEVE Client for Windows   D            2. Unzip the file. This creates three image files and one"               DOS file as follows:                 o  DTRWDSK1.IMGt                 o  DTRWDSK2.IMGa                 o  DTRWDSK3.IMGf                 o  DOSIMAGE.EXE   B               You must copy each image file onto a separate floppy>               disk. These three disks are then used to install,               DATATRIEVE Client for Windows.  =            3. Insert a blank floppy disk into the disk drive.   =            4. From the MS-DOS command line run the following:T  0               $ DOSIMAGE RESTORE DTRWDSK1.IMG A:  D               This writes the first image file onto the first floppy               disk (Disk 1).  ?            5. Repeat this procedure by writing DTRWDSK2.IMG and ?               DTRWDSK3.IMG onto Disk 2 and Disk 3 respectively.t  E            Proceed to install DATATRIEVE Client for Windows using the E            steps outlined in Section 1.2 of the DATATRIEVE Client for_             Windows User's Guide.  ?      3.10 Deleting Unused Files for DATATRIEVE DECwindows Motifo           Support   >            If the DATATRIEVE DECwindows Motif interface is not>            required at your site, you can delete the followingC            files after the DATATRIEVE installation has successfullya            completed:   ,            o  SYS$COMMON:[SYSEXE]DTRHELP.EXE  A            o  SYS$COMMON:[DECW$BOOK]DTR_DECW_HELP_MOTIF.DECW$BOOK   F            o  SYS$COMMON:[DECW$BOOK]DTR_DECW_HELP_MOTIF.DECW$BOOKSHELF  3            o  SYS$COMMON:[SYSLIB]VAX_DATATRIEVE.UIDa  0            o  SYS$COMMON:[DTR]REMOTE_DECTERM.COM  ?            If you delete any of the DATATRIEVE DECwindows MotifdA            files, ensure that you delete all of the listed files.d  )      3-12 Postinstallation Considerations  e  S      H                                          Postinstallation ConsiderationsH       3.10 Deleting Unused Files for DATATRIEVE DECwindows Motif Support  G               After the DATATRIEVE DECwindows Motif interface files aretH               deleted, remove all references to these files from each of3               your SYS$STARTUP:DTRSTUPxx.COM files.d  0         3.11 Getting Help and Reporting Problems  G               If you encounter a problem while using DATATRIEVE, reportaE               it to Compaq. Depending on the type of support you haveVF               and the nature of the problem, take one of the following               actions:  @               o  If you have a Software Product Services SupportG                  Agreement, contact your Compaq Customer Support Center C                  (CSC), either by telephone or using the electronic A                  means provided with your support agreement (suchiD                  as DSNlink). The CSC provides telephone support forB                  high-level advisory and remedial assistance. WhenC                  you initially contact the CSC, please indicate the.                  following:i  H                  -  The name (e.g. OpenVMS Alpha) and the version number:                     of the operating system you are using.  H                  -  The product name (DATATRIEVE) and the version number0                     of DATATRIEVE you are using.  F                  -  The hardware system you are using, such as a model                     number.O  @                  -  A very brief description of the problem (one*                     sentence if possible).  0                  -  How critical the problem is.  B                  When you submit information electronically or areD                  speaking on the phone to the appropriate DATATRIEVEB                  support specialist, you can provide more detailedF                  information. This includes the specific commands usedD                  to compile and link the program, the error messagesG                  displayed, and relevant detailed information (possiblyiF                  including source program listings). Please attempt toH                  narrow the cause of the problem to a specific module or                  lines of code.t    H                                     Postinstallation Considerations 3-13    3      $      Postinstallation Considerations-      3.11 Getting Help and Reporting Problemsv  ?               CSC personnel may ask for additional information,T<               such as listings of any command files, INCLUDE>               files, relevant data files, and so forth. If the?               program is longer than 50 lines, submit a copy of3A               it electronically or provide machine-readable media 1               (floppy diskette or magnetic tape).o  D            o  If you have a Self-Maintenance Software Agreement, you=               can submit a Software Performance Report (SPR).   >            o  If you do not have any type of software servicesC               support agreement and you purchased DATATRIEVE within >               one year, you can submit an SPR if you think the4               problem is caused by a software error.  C            When you submit an SPR, please take the following steps:t  B            1. Describe as accurately as possible the circumstancesC               and state of the system when the problem occurred. Inc.               the description, please provide:  =               -  The version number of DATATRIEVE being used.e  D               -  The name and version number of the operating system                  being used.  C               -  A concise description of the problem with specific D                  examples. Include any error messages displayed, theC                  commands used to compile and link the program, and                   so on.   @            2. Reduce the problem to as small a size as possible.  /            3. Provide a listing of the program.i  E            4. When you submit an SPR, remember to include listings ofhD               any command files, INCLUDE files, relevant data files,               and so forth.o  C            5. When you submit an SPR, if the program is longer thaneE               50 lines, submit a copy of it on machine-readable mediaoD               (floppy diskette or magnetic tape). If necessary, alsoD               submit a copy of the program library used to build the               application.  E            6. Report only one problem per SPR. This will facilitate ao               faster response.  -            7. Mail the SPR package to Compaq.e  )      3-14 Postinstallation Considerations  t         H                                          Postinstallation ConsiderationsH                                 3.11 Getting Help and Reporting Problems  D               Many problem reports do not contain enough informationE               to duplicate or identify the problem. Concise, complete C               information helps Compaq give you accurate and timelyr+               service to software problems.2  H               If the problem is related to DATATRIEVE documentation, youF               can use one of the following ways to send your comments:  3               o  Send an electronic mail message toe  -                  comments@galvia.enet.dec.comt  0               o  Send a fax to +353 (0)91-754444  F               To obtain information about purchasing a Compaq SoftwareA               Product Services Support Agreement or other support >               services, please contact your local Compaq sales               representative..  H               Review the Software Product Description (SPD) and WarrantyG               Addendum for an explanation of warranty. If you encounterMF               a problem during the warranty period, report the problemA               as indicated above or follow alternate instructions A               provided by Compaq for reporting SPD nonconformancen               problems.                                         H                                     Postinstallation Considerations 3-15 L                     H                                                                        4H         ________________________________________________________________  H                                           User Environment Test Packages      E               Five User Environment Test Packages (UETPs), which showAE               examples and test product interfaces, are provided withnA               DATATRIEVE. You can run the UETPs after you installi?               DATATRIEVE. The following UETPs are provided witht               DATATRIEVE:u                 o  DATATRIEVEc  /               o  DATATRIEVE graphics capability   =               o  DATATRIEVE and Oracle CODASYL DBMS interfacea  4               o  DATATRIEVE and Oracle Rdb interface  @               o  DATATRIEVE and Compaq FMS or VAX TDMS interface  G               The DATATRIEVE User's Guide includes the data definitions /               and procedures used in the UETPs.   F                 ________________________Note  ________________________  C                 o  You must run the NEWUSER.COM file before running                     any UETP.  B                 o  You must run the DATATRIEVE UETP before runningC                    any other UETP. The DATATRIEVE UETP creates datas7                    definitions used by the other UETPs.   E                 _____________________________________________________r            H                                       User Environment Test Packages 4-1 t  k      #      User Environment Test Packages       4.1 Invoking DATATRIEVE        4.1 Invoking DATATRIEVE  D            To run the UETPs, you must first invoke DATATRIEVE in one!            of the following ways:m  9            o  Use the DCL command DATATRIEVE, as follows:E                 $ DATATRIEVE  E               The DCL command DATATRIEVE is useful if you are workinge?               in a DECwindows Motif environment. You should not A               run the UETPs using the DATATRIEVE DECwindows Motif >               interface, as you may get unexpected results. ByD               using the DATATRIEVE command to invoke DATATRIEVE, youA               can specify the /INTERFACE=CHARACTER_CELL qualifiera?               to invoke DATATRIEVE without the DECwindows MotifE               interface.  C               If you have installed more than one DATATRIEVE image,ED               you can specify the /VARIANT=image-suffix qualifier to;               run the image of DATATRIEVE you want to test.   D               To invoke DATATRIEVE using these qualifiers, enter the                following command:  >               $ DATATRIEVE/INTERFACE=CHARACTER_CELL/VARIANT=xx  @               The characters xx represent the 1- to 26-characterC               suffix added at installation to identify a particular /               image of DATATRIEVE Version 7.2A.   1            o  Use the DCL command RUN as follows:   *               $ RUN SYS$SYSTEM:DTR32xx.EXE  ?               The xx represents the 1- to 26-character optionaltE               suffix added to an image of DATATRIEVE at installation.I  @            o  Use a symbol you have defined to represent the RUN#               command. For example:                  $ DTR32   D            At the DTR> prompt, enter the command to execute the UETPE            you want to run. The UETPs and the commands to invoke them63            are described in the following sections.y  '      4-2 User Environment Test Packages     o      H                                           User Environment Test PackagesH                                                      4.2 DATATRIEVE UETP           4.2 DATATRIEVE UETPl  H               To run the DATATRIEVE UETP, invoke DATATRIEVE as describedH               in Section 4.1, Invoking DATATRIEVE and type the following               command:  /               DTR> @SYS$COMMON:[SYSTEST.DTR]DTRo  H               The DATATRIEVE UETP is approximately 20 pages long, so the/               entire UETP is not repeated here.y  D               You respond to prompts during the DATATRIEVE UETP. TheD               parts of the UETP that require a response are includedD               here along with suggested responses. The responses you.               enter are printed in bolded ink.  F                 ________________________Note  ________________________  >                 The DATATRIEVE UETP suggests at one point that@                 you use LP: to print a report directly to a lineA                 printer. The LP: option may not work unless LP ism.                 defined as the system printer.  E                 _____________________________________________________s                 !                ! TEST STORE               ! 3               ! PLEASE SUPPLY THE FOLLOWING VALUES: .               !    MANUFACTURER:       HINKLEY1               !    MODEL:              BERMUDA 40t+               !    RIG:                YAWL *               !  * LENGTH-OVER-ALL:    140)               !    LENGTH-OVER-ALL:    40e,               !    DISPLACEMENT:       20000)               !    BEAM:               12p7               !  * PRICE:              82000 AND XX/100E.               !    PRICE:              $82,000(               !    CONFIRM:            N               !6O               ! Values marked with "*" will generate an error and be repromptedL               !       H                                       User Environment Test Packages 4-3 /  U      #      User Environment Test PackagesM      4.2 DATATRIEVE UETP              STORE YACHTS :VERIFY &            Enter MANUFACTURER: HINKLEY"            Enter MODEL: BERMUDA 40            Enter RIG: YAWL%            Enter LENGTH_OVER_ALL: 140 6            Validation error for field LENGTH_OVER_ALL.'            Re-enter LENGTH-OVER-ALL: 40 $            Enter DISPLACEMENT: 20000            Enter BEAM: 12 (            Enter PRICE: 82000 AND XX/100I            Non-digit in string "82000 AND XX/100", ignoring character(S). "            Re-enter PRICE: $82,000  /                                          LENGTHA.                                           OVERB            MANUFACTURER   MODEL     RIG   ALL   WEIGHT BEAM  PRICE  C             HINKLEY     BERMUDA 40 YAWL   40    20,000  12  $82,000]3            DISPLAY: IF RECORD IS OK, CONFIRM WITH Yt            Enter CONFIRM: N               !9            ! Invoke report (suggest  TT:  as output file)             !            :LOA-REPORT            Enter FILE: TT   C            At this point, a report is displayed on the screen. When73            the report finishes, the UETP continues:e              !9            ! Invoke report (suggest  LP:  as output file)             !            :LOA-REPORT            Enter FILE: LP:  B            At this point, the procedure sends a report to the line*            printer and the UETP continues:              READY YACHTS MODIFY            !5            ! RESPOND WITH 47 (or any two digit value)             !            MODIFY BEAM            Enter BEAM: 47e            PRINT TYPE,BEAM  '      4-4 User Environment Test Packages  0         H                                           User Environment Test PackagesH                                                      4.2 DATATRIEVE UETP  *               MANUFACTURER   MODEL    BEAM  (               METALMAST   GALAXY      47               ! 8               ! RESPOND WITH 48 (or any two digit value)               !                MODIFY ALL BEAM                Enter BEAM: 48               !                PRINT ALL BEAM                 BEAM                  48                 48i                48                 48                 48                  !u1               ! Respond each time with 0 (please)                !l5               FOR CURRENT PRINT TYPE THEN MODIFY BEAME  "               MANUFACTURER   MODEL  !                METALMAST   GALAXY[               Enter BEAM: 0E                O'DAY       32"               Enter BEAM: 0 #                RYDER       S. CROSS                Enter BEAM: 0 #                TA CHIAO    FANTASIA                Enter BEAM: 0 %                WRIGHT      SEAWIND IIs               Enter BEAM: 0o               !O               SET ABORTs               READY YACHTS READ                PRINT ALL   3                                              LENGTH 2                                               OVERL               MANUFACTURER   MODEL     RIG    ALL   DISPLACEMENT BEAM  PRICE  H                                       User Environment Test Packages 4-5           #      User Environment Test Packages       4.2 DATATRIEVE UETP  A             METALMAST   GALAXY     SLOOP   32        9,500     00 J             O'DAY       32         SLOOP   32       11,000     00  $29,500J             RYDER       S. CROSS   SLOOP   31       13,600     00  $32,500A             TA CHIAO    FANTASIA   SLOOP   35       23,200     00hJ             WRIGHT      SEAWIND II SLOOP   32       14,900     00  $34,480  <            The installation is successful if you receive the4            following message at the end of the UETP:              !1            ! The DATATRIEVE User Environment Testt0            ! Package has completed successfully.            !  !      4.3 DATATRIEVE Graphics UETP   @            You must run the DATATRIEVE graphics UETP on a VT125,D            VT240, VT330, or VT340 terminal, or a workstation. To runC            the UETP, invoke DATATRIEVE as described in Section 4.1,3>            Invoking DATATRIEVE and type the following command:  .            DTR> @SYS$COMMON:[SYSTEST.DTR]PLOTS  B            The DATATRIEVE graphics UETP does not require any inputC            from you. There are pauses between plots. The DATATRIEVE D            graphics UETP displays the results of using the following            plot statements:A  1            o  PLOT WOMBAT - A picture of a wombatE  ?            o  PLOT DATE_Y - A scattergraph with dates along thee               horizontal axisi  A            o  PLOT SHADE - The previous scattergraph with shading   ?            o  PLOT DATE_Y - A scattergraph with dates along the                horizontal axis   ?            o  PLOT CONNECT - The previous scattergraph with thea               points connected  >            o  PLOT DATE_LOGY - A scattergraph with dates alongA               the horizontal axis and a logarithmic scale for the                vertical axis   ?            o  PLOT LR - The previous scattergraph with a linear,               regression line   '      4-6 User Environment Test PackagesM l  e      H                                           User Environment Test PackagesH                                             4.3 DATATRIEVE Graphics UETP  G               o  PLOT STACKED_BAR - A bar chart with stacked bars and a                   legendA  F               o  PLOT MULTI_BAR - A bar chart with multiple bars and a                  legend   *               o  PLOT X_Y - A scattergraph  D               o  PLOT TITLE - The previous scattergraph with a title  C               o  PLOT LIMITS_Y - The previous X_Y scattergraph with A                  maximum and minimum limits imposed on the Y axisr  C               o  PLOT LIMITS_X - The previous X_Y scattergraph with A                  maximum and minimum limits imposed on the X axis   H               o  PLOT REFERENCE_Y - The previous X_Y scattergraph with a3                  solid reference line on the Y axisA  H               o  PLOT REFERENCE_X - The previous X_Y scattergraph with a3                  solid reference line on the X axisn  B               o  PLOT LR - The previous scattergraph with a linear                   regression line  F               o  PLOT X_LOGY - A scattergraph with a logarithmic scale&                  for the vertical axis  )               o  PLOT HISTO - A histogram   D               o  PLOT PIE - A pie chart (with default title heading)  A               o  PLOT TITLE (pie) - The previous pie chart with aj                   multiline title  ?               o  PLOT BAR - A bar chart using builder and priceu  E               o  PLOT SORT_BAR - The previous bar chart with the bars ,                  sorted by descending height  <               o  PLOT BAR - A bar chart using type and price  F               When the DATATRIEVE graphics UETP finishes, you see this               message:                 !.C               ! End of User Environment Test Package for DATATRIEVEr               ! graphics               !t               EXIT  H                                       User Environment Test Packages 4-7 :         #      User Environment Test Packages 0      4.4 DATATRIEVE and Oracle CODASYL DBMS UETP  0      4.4 DATATRIEVE and Oracle CODASYL DBMS UETP  >            To run the DATATRIEVE and Oracle CODASYL DBMS UETP,B            invoke DATATRIEVE as described in Section 4.1, Invoking5            DATATRIEVE and type the following command:n  -            DTR> @SYS$COMMON:[SYSTEST.DTR]DBMS_  B            The DATATRIEVE and Oracle CODASYL DBMS UETP is long, so0            the entire UETP is not repeated here.  B            You respond to prompts during the DATATRIEVE and Oracle@            CODASYL DBMS UETP. The parts of the UETP that requireA            answers are included here with the suggested responsesr"            printed in colored ink.              SELECTO            PRINT  A            Part                                      Unit    Unit E            Number  ------Part Description------ St   Price   Cost  Sp   E            TI-6789-01    RK HOUSING             G     $300   $190  FSt            !8            ! Respond with 123 (or any three digit value)            !            MODIFY PART_PRICE             Enter PART_PRICE: 123$            PRINT PART_ID, PART_PRICE  !              Part            UnitT"              Number          Price  "            TI-6789-01         $123            !8            ! Respond with 321 (or any three digit value)            !             MODIFY ALL PART_PRICE             Enter PART_PRICE: 321            PRINT ALL PART_PRICE                      Unit                   Price     '      4-8 User Environment Test PackagesP i  g      H                                           User Environment Test PackagesH                              4.4 DATATRIEVE and Oracle CODASYL DBMS UETP                         $321                       $321                       $321                       $321                       $321               !a1               ! Respond each time with 0 (Please)I               !T               FOR CURRENT 4                 PRINT PART_ID THEN MODIFY PART_PRICE                   Part                 Number                 TI-6789-01!               Enter PART_PRICE: 0                BR-8901-23!               Enter PART_PRICE: 0                TE-2345-67!               Enter PART_PRICE: 0                TE-2178-90!               Enter PART_PRICE: 0I               TI-1334-56!               Enter PART_PRICE: 0i               PRINT ALLn  E               Part                                      Unit     Unit I               Number  ------Part Description------ St   Price    Cost  Sp   I               TI-6789-01    RK HOUSING             G       $0    $190  FSR  I               BR-8901-23    LA36                   G       $0    $750  FSn  I               TE-2345-67    RP05                   G       $0  $1,900  FS   I               TE-2178-90    RK06                   G       $0  $1,100  FS   I               TI-1334-56    RP HOUSING             G       $0    $300  FSh  A               If the DATATRIEVE and Oracle CODASYL DBMS UETP runsf:               successfully, you see the following message:                 !i5               ! End of DATATRIEVE/Oracle CODASYL DBMSn-               ! User Environment Test Package                !g  H                                       User Environment Test Packages 4-9 t  Y      #      User Environment Test Packages '      4.5 DATATRIEVE and Oracle Rdb UETPt  '      4.5 DATATRIEVE and Oracle Rdb UETPi  <            To run the DATATRIEVE and Oracle Rdb UETP, invoke;            DATATRIEVE as described in Section 4.1, Invokings5            DATATRIEVE and type the following command:I  ,            DTR> @SYS$COMMON:[SYSTEST.DTR]Rdb  B            The DATATRIEVE and Oracle Rdb UETP is 12 pages long, so0            the entire UETP is not repeated here.  B            You respond to prompts during the DATATRIEVE and OracleC            Rdb UETP. The parts of the UETP that require answers aree@            included here with the suggested responses printed in            colored ink.               !            ! Test Store             !0            ! Please supply the following values:            !%            !       WAGE_CLASS :     4 ,            !       JOB_TITLE:       ANYTHING)            !       MINIMUM_SALARY:  12000 *            !       MAXIMUM_SALARY:  123000            !              STORE JOBS USINGm                    BEGIN$                    JOB_CODE = "XXXX",                    WAGE_CLASS = *.WAGE_CLASS*                    JOB_TITLE = *.JOB_TITLE4                    MINIMUM_SALARY = *.MINIMUM_SALARY4                    MAXIMUM_SALARY = *.MAXIMUM_SALARY                    END            Enter WAGE_CLASS: 4$            Enter JOB_TITLE: ANYTHING&            Enter MINIMUM_SALARY: 12000'            Enter MAXIMUM_SALARY: 123000h            !          (      4-10 User Environment Test Packages 1  e      H                                           User Environment Test PackagesH                                       4.5 DATATRIEVE and Oracle Rdb UETP                 STORE JOBS USING                       BEGINl'                       JOB_CODE = "YYYY"s$                       WAGE_CLASS = 2.                       JOB_TITLE = "FILE CLERK"+                       MINIMUM_SALARY = 8000W,                       MAXIMUM_SALARY = 20000                       ENDL               !S7               PRINT JOBS WITH JOB_CODE = "XXXX", "YYYY"I  C               JOB  WAGE          JOB            MINIMUM     MAXIMUM B               CODE CLASS        TITLE           SALARY      SALARY  E               XXXX   4   ANYTHING              $12,000.00 $123,000.00lE               YYYY   2   FILE CLERK              $8000.00  $20,000.00                !l               ! Test Erase               !s4               FOR JOBS WITH JOB_CODE = "XXXX"  ERASE/               PRINT JOBS WITH JOB_CODE = "XXXX"                !r.               FIND JOBS WITH JOB_CODE = "YYYY"               [1 record found]               PRINT ALLT  C               JOB  WAGE          JOB            MINIMUM     MAXIMUMbB               CODE CLASS        TITLE           SALARY      SALARY  E               YYYY   2   FILE CLERK             $8,000.00  $20,000.00t                 SELECT LAST                ERASEb/               PRINT JOBS WITH JOB_CODE = "YYYY"i               !                ! Test Update                !S7               FIND EMPLOYEES WITH EMPLOYEE_ID = "00168"u               [1 record found]               SELECT               !u  ?               PRINT EMPLOYEE_ID, LAST_NAME, STREET, TOWN, STATEp    H                                      User Environment Test Packages 4-11 p  t      #      User Environment Test Packagesa'      4.5 DATATRIEVE and Oracle Rdb UETP               EMPLOYEE      LASTCJ               ID         NAME             STREET          TOWN       STATE  H             00168     Nash       87 West Rd.         Meadows          NH            !+            ! Change this employee's address             !/            ! Please supply the following value:             !"            ! STREET:  8 FLINT POND            !            MODIFY STREET%            Enter STREET: 8 FLINT POND <            PRINT EMPLOYEE_ID, LAST_NAME, STREET, TOWN, STATE              EMPLOYEE      LAST J               ID         NAME             STREET          TOWN       STATE  A             00168    Nash      8 FLINT POND   Meadows          NHr              !?            ! Don't really want to do this; rollback this change             !            ROLLBACKcH            ROLLBACK executed; collection CURRENT automatically released.              !?            PRINT EMPLOYEE_ID, LAST_NAME, STREET, TOWN, STATE OFo1              EMPLOYEES WITH EMPLOYEE_ID = "00168"t              EMPLOYEE      LAST K               ID         NAME            STREET           TOWN        STATE   I             00168    Nash        87 West Rd.         Meadows           NH               !/            FIND ALL EMPLOYEES WITH STATE = "MA"o            [8 records found]            PRINT ALL STATE              STATE        (      4-12 User Environment Test Packages m         H                                           User Environment Test PackagesH                                       4.5 DATATRIEVE and Oracle Rdb UETP                  MA                 MA                 MA                 MAi                MAo                MAt                MAp                MAa               ! M               ! Respond with VT (or another two-character state abbreviation)f               !w               MODIFY ALL STATE               Enter STATE: VTa               PRINT ALL STATE                  STATEa                  VTe                VT                 VT                 VTA                VT                 VTr                VT                 VTe                 !b$               ! Move them back to MA               !o               FOR CURRENTe)                 MODIFY USING STATE = "MA"c               PRINT ALL STATEt                 STATE                   MAt                MAp                MAc                MA                 MA                 MA                 MAn                MAV    H                                      User Environment Test Packages 4-13 y  m      #      User Environment Test Packages '      4.5 DATATRIEVE and Oracle Rdb UETPe  C            If the DATATRIEVE and Oracle Rdb UETP runs successfully, )            you see the following message:s              !@            ! End of DATATRIEVE/Rdb User Environment Test Package            !              ROLLBACKzH            ROLLBACK executed; collection CURRENT automatically released.            FINISH ALLi            DTR>r  "      4.6 DATATRIEVE and Forms UETP  E            You need a VT52-, VT100-, VT200-, or VT300-family terminalnA            or a workstation to run the DATATRIEVE and forms UETP.m  C            If DATATRIEVE was installed with support for VAX TDMS oreC            Compaq FMS, you can run the forms UETP to test the formsf            interface.   ?            To run the forms UETP, set your OpenVMS default to a >            directory that contains YACHT.DAT and OWNER.DAT. Be>            sure that you have WRITE access (W) to these files.B            You can copy YACHT.DAT and OWNER.DAT from the directoryA            DTR$LIBRARY if you do not have them in your directory. >            Then invoke DATATRIEVE as described in Section 4.1,>            Invoking DATATRIEVE and type the following command:  .            DTR> @SYS$COMMON:[SYSTEST.DTR]FORMS  C            When DATATRIEVE uses a form to print records, the screenoD            clears before the first record is printed. The DATATRIEVEA            and forms UETP asks you to enter a character and press E            RETURN before each statement, causing the forms product to             erase the screen.  A            The following is a summary of the DATATRIEVE and formse            UETP:  B            1. The UETP sends instructions to your screen and waitsB               for you to enter a character and press RETURN. AfterB               you respond, the UETP defines three domains that useA               the forms product: YACHTS, SAILBOATS, and FAMILIES.cE               The definitions use forms libraries that are located ine               DTR$LIBRARY.  (      4-14 User Environment Test Packages n         H                                           User Environment Test PackagesH                                            4.6 DATATRIEVE and Forms UETP  A               2. The UETP readies YACHTS and prints a few records E                  without using the forms product. Then the UETP sends F                  more instructions to your screen and waits for you toG                  enter a character and press RETURN. After you respond, H                  the UETP prints a record using the forms product. PressD                  RETURN after the forms product displays the record.  E               3. The UETP sends instructions to your screen and waitssE                  for you to enter a character and press RETURN. AfterTG                  you respond, the UETP prints several records using the D                  forms product. Press RETURN after the forms product&                  displays each record.  C               4. The UETP tests the STORE statement. The UETP sends G                  instructions to your screen and waits for you to enterlE                  a character and press RETURN. After you respond, the C                  forms product puts a form on the screen for you to G                  fill in. To move the cursor from one field to another, C                  use the TAB and BACK SPACE keys. The TAB key moves G                  the cursor to the next field; the BACK SPACE key moves_D                  the cursor back to the previous field. Help is alsoG                  available for some fields if you have trouble entering G                  an acceptable value. Position the cursor on that field D                  and press the HELP key. After you fill in the form,                  press RETURN.  D               5. The UETP tests the MODIFY statement controlling theD                  DISPLAY_FORM statement. The UETP sends instructionsF                  to your screen and waits for you to enter a characterG                  and press RETURN. After you respond, the forms productEE                  displays the first record for you to modify. Use theeB                  TAB and BACK SPACE keys to move from one field toD                  another. Modify only the BEAM field in each record.D                  Any other modifications are not written to the dataB                  file. After you modify each record, press RETURN.  @               6. The UETP tests the PRINT statement again, usingB                  the SAILBOATS view domain. The UETP waits for youB                  to enter a character and press RETURN before eachF                  PRINT statement. After the forms product displays theG                  SAILBOAT records, the UETP sends the following messagef                   to your screen:      H                                      User Environment Test Packages 4-15 A  i      #      User Environment Test Packages "      4.6 DATATRIEVE and Forms UETP                 ! E               ! End of DATATRIEVE/Forms User Environment Test Package                !n                                                                                    (      4-16 User Environment Test Packages a  t                  H                                                                        5H         ________________________________________________________________  H                                              DATATRIEVE CBT Installation      G               This chapter describes the installation procedure for the 7               DATATRIEVE computer-based training (CBT).                     1. Before Starting  D                     Before starting the DATATRIEVE CBT installation,E                     please completely review this chapter. Be sure to C                     gather information to answer the prompts beforee.                     starting the installation.  A                     If you already have a previous version of the F                     DATATRIEVE CBT installed, the CBT can remain. ThisF                     new kit will add to or overwrite the existing CBTs#                     as appropriate.   7               2. Pre-installation of the DATATRIEVE CBTV  B                     Perform the following steps before running the(                     VMSINSTAL procedure:  D                     -  Copy the new kit from the tape containing the7                        savesets, DTC010.A and DTC010.B.   :                     -  Set your process privileges to ALL.  3                                   SET PROC/PRIV=ALLT  H                     -  Check to see if the DATATRIEVE CBT was previously!                        installed:e  ;                                   SHOW LOGICAL EASY$MANAGER   D                        If the logical exists, the DATATRIEVE CBT hasE                        been installed before. Invoke shutdown command 4                        for each node in the cluster:  @                                   @SYS$MANAGER:EASY$SHUTDOWN.COM  H                                          DATATRIEVE CBT Installation 5-1                  DATATRIEVE CBT Installation    D                     Next, invoke the startup command for the node on-                     which you are installing:   <                                @SYS$MANAGER:EASY$STARTUP.COM  @                     If you find that the DATATRIEVE CBT has beenD                     previously installed, go on to Step 3, SITE WITHB                     A PREVIOUS EASYAUTHOR INSTALLATION, and do the(                     actual installation.  A                  -  Find a UIC (if EasyAuthor CBTs not previously )                     installed on system).E  @                     Find an available UIC to become the owner ofA                     the files to be installed. A new account nameeE                     (EASYMGR) is created during install. This account -                     has the DISUSER flag set.g  E                  -  Find a disk to use (if this is the first time youT+                     install on the system).   ?                     The installation will require approximatelyE"                     12,000 blocks.  0            3. Installation of the DATATRIEVE CBT  >                  Perform the install by running VMSINSTAL. The=                  following is a log file of the installation. A                  Notations (<<-) are included to show where entry D                  is required. These notations will not appear on the+                  screen during the install.   %               FIRST TIME INSTALLATIONT  !      $ @sys$update:vmsinstal <<-- 4       Software Product Installation Procedure V5.4-2       It is 20-DEC-1991 at 22:15.4      Enter a question mark (?) at any time for help.I      %VMSINSTAL-W-NOTSYSTEM, You are not logged in to the SYSTEM account. C      %VMSINSTAL-W-ACTIVE, The following processes are still active:s      Resourcemoniter4      * Do you want to continue anyway [NO]? YES <<--H      * Are you satisfied with the backup of your system disk [YES]? <<--F      * Where will the distribution volumes be mounted: SYS$LOGIN: <<--  $      5-2 DATATRIEVE CBT Installation g         H                                              DATATRIEVE CBT Installation    R         Enter the products to be processed from the first distribution volume set.         * Products: DTC010 <<--:A         * Enter installation options you wish to use (none): <<--O1         The following products will be processed:            DTC0104          Beginning installation of DTC V1.0 at 22:16  >         %VMSINSTAL-I-RESTORE, Restoring product save set A ...M         * Enter UIC value for EASYMGR account in [g,m] format: [666,666] <<-- .         Location for EASYMGR lesson directory:C         * >> [SYS$COMMON:[EASYMGR]]: EASYAUTHOR_KITS:[easymgr] <<-- 3         %DTC-I-CREATE, Creating the EASYMGR account E         %DTC-I-DISUSER, This account is initially DISABLED. (DISUSER) Q         %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named EASYMGR. 5         %UAF-I-ADDMSG, user record successfully added M         %UAF-I-RDBADDMSGU, identifier EASYMGR value: [000666,000666] added to          rights data base:         %DTC-I-CREATEDIR, Creating EasyAuthor directories.+         %DTC-I-LOADEXE, Loading executablesU=         %DTC-I-INSTLOK, EASY has been successfully installed.R  ?          +----------------------------------------------------+ ?          |          POST INSTALL INSTRUCTIONS !               |M?          |                                                    |E?          |  Add the EASY symbol definition to                 | ?          |  SYS$SYLOGIN.COM or user's LOGIN.COM as follows:   |n?          |         EASY :== $EASY$PROGRAM:SOLORTP.EXE         | ?          |         LOADDRAW :== $EASY$PROGRAM:SOLORTP.EXE     | ?          |                                                    | ?          |  IMMEDIATELY AFTER INSTALL RUN THE FOLLOWING       | ?          |                COMMAND FILE:                       | ?          |                                                    | ?          |         @EASY$PROGRAM:SETUP.COM                    | ?          |                                                    | ?          |                                                    | ?          +----------------------------------------------------+6  G         %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target2         directories...  4          Installation of DTC V1.0 completed at 22:46        H                                          DATATRIEVE CBT Installation 5-3 l  i             DATATRIEVE CBT Installation    N      Enter the products to be processed from the next distribution volume set.      * Products: <<--u'       VMSINSTAL procedure done at 22:46 #      $ @easy$program:setup.com <<--       $ logout <<--  :               SITE WITH A PREVIOUS EASYAUTHOR INSTALLATION        $ @sys$update:vmsinstal4       Software Product Installation Procedure V5.3-1       It is 20-DEC-1991 at 14:50.4      Enter a question mark (?) at any time for help.I      %VMSINSTAL-W-NOTSYSTEM, You are not logged in to the SYSTEM account.pC      %VMSINSTAL-W-ACTIVE, The following processes are still active:p       Resourcemonitore       EASY_DEV2      * Do you want to continue anyway [NO]? y <<--H      * Are you satisfied with the backup of your system disk [YES]? <<--E      * Where will the distribution volumes be mounted: sys$login <<--w  O      Enter the products to be processed from the first distribution volume set.T      * Products: DTC010 <<-->      * Enter installation options you wish to use (none): <<--.      The following products will be processed:        DTC V1.0T1       Beginning installation of DTC V1.0 at 14:50   ;      %VMSINSTAL-I-RESTORE, Restoring product save set A ...sA      *****%KELLY-I-INSTLOK, EASY has been successfully installed.   <       +----------------------------------------------------+<       |          POST INSTALL INSTRUCTIONS !               |<       |                                                    |<       |  Add the EASY symbol definition to                 |<       |  SYS$SYLOGIN.COM or user's LOGIN.COM as follows:   |<       |         EASY :== $EASY$PROGRAM:SOLORTP.EXE         |<       |         LOADDRAW :== $EASY$PROGRAM:LOADDRAW.EXE    |<       |                                                    |<       |  IMMEDIATELY AFTER INSTALL RUN THE FOLLOWING       |<       |                COMMAND FILE:                       |<       |                                                    |<       |         @EASY$PROGRAM:SETUP.COM                    |<       |                                                    |<       |                                                    |<       +----------------------------------------------------+  $      5-4 DATATRIEVE CBT Installation           H                                              DATATRIEVE CBT Installation    G         %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target          directories...  4          Installation of DTC V1.0 completed at 14:53  Q         Enter the products to be processed from the next distribution volume set.          * Products:  <<-- *          VMSINSTAL procedure done at 14:53  3               4. Post-install of the DATATRIEVE CBTr  3                     Run the following command file:   8                                  @EASY$PROGRAM:SETUP.COM  D                     Before any of the system's users can access thisD                     CBT, the EASY and LOADDRAW symbols must be addedE                     to SYS$MANAGER:SYLOGIN.COM or user's LOGIN.COM asT                     follows:  C                                  EASY :== $EASY$PROGRAM:SOLORTP.EXE H                                  LOADDRAW :== $EASY$PROGRAM:LOADDRAW.EXE  F                     Upon completion of the above steps, the DATATRIEVEB                     CBT is installed on a single node. To test theG                     installation, run it from a user account by typing:   %                                  EASY   F                     Edit the main course menu file to remove duplicateG                     lines (if the course was previously installed). TheE2                     file is EASY$PROGRAM:EASY.CAT.  .               5. Start-up in clustered systems  F                     To enable the lessons on all nodes in the cluster,@                     run the EASY$STARTUP command on EACH NODE as                     follows:  >                                  @SYS$MANAGER:EASY$STARTUP.COM  ?               6. De-installation of the DATATRIEVE CBT (if evert                  necessary)s  H                     A shutdown command file can be found in SYS$MANAGER.C                     The name of the file is EASY$SHUTDOWN.COM. ThiseC                     command file removes all logicals, logical namenB                     tables, and shared images associated with this                     package.  H                                          DATATRIEVE CBT Installation 5-5 s  S             DATATRIEVE CBT Installation    C                  To completely remove this package from the system:w  B                  o  Examine the EASY$LESSONS logical. This logicalC                     will tell you where the CBT has been installed.   >                  o  Execute the command file (for all nodes if                     clustered),T  8                               @SYS$MANAGER:EASY$SHUTDOWN  ?                  o  Remove the entire [EASYMGR] directory tree.   D                  o  Remove EASYMGR from the user authorization file.  +                               RUN AUTHORIZE ,                               REMOVE EASYMGR"                               EXIT  -                  o  Delete the command files,e  3                        SYS$MANAGER:EASY$STARTUP.COMT4                        SYS$MANAGER:EASY$SHUTDOWN.COM                                              $      5-6 DATATRIEVE CBT Installation    3                  H                                                                        AH         ________________________________________________________________  H                                   Sample Installation Session (VAX Only)      F               This appendix lists the hardcopy terminal output from anG               installation of DATATRIEVE Version 7.2A on an OpenVMS VAX2               system.n  ;         $ @sys$update:vmsinstal dtra072 disk$:[dtr.dtra072]e  H                 OpenVMS VAX Software Product Installation Procedure V7.1  "         It is 7-FEB-2000 at 14:32.  7         Enter a question mark (?) at any time for help.U  L         %VMSINSTAL-W-NOTSYSTEM, You are not logged in to the SYSTEM account.F         %VMSINSTAL-W-ACTIVE, The following processes are still active:                 UCX$FTPD                 _TNA110:0         * Do you want to continue anyway [NO]? yF         * Are you satisfied with the backup of your system disk [YES]?  1         The following products will be processed:              DTRA V7.2   <                 Beginning installation of DTRA V7.2 at 14:32  >         %VMSINSTAL-I-RESTORE, Restoring product save set A ...S         %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.i  ;                     DATATRIEVE V7.2A Installation Procedure   E               Compaq Computer Corporation 2000. All rights reserved.   B         * Do you want support for Oracle CDD/Repository [YES]? yes    H                               Sample Installation Session (VAX Only) A-1 T         +      Sample Installation Session (VAX Only)     =          The DATATRIEVE product is built using several objectDA          libraries which can also be used to customize DATATRIEVEIE          to suit your needs (see the DATATRIEVE documentation manual,SJ          'Guide to Programming and Customizing').   These object librariesD          are now built using the DEC C compiler.    If you have beenK          programming your own customizations and wish to continue using the.E          VAX C compiler, you have the option of installing the objecteE          libraries which have been built using that compiler instead.   ?          If you answer YES to this question, DATATRIEVE will bePI          linked with the VAX C RTL, and the libraries in DTR$LIBRARY willL7          contain objects built with the VAX C compiler.G  >          If you answer NO to this question, DATATRIEVE will beI          linked with the DEC C RTL, and the libraries in DTR$LIBRARY will 3          contain objects built with DEC C compiler.X  @          Unless you customize your use of DATATRIEVE and want toG          continue using the VAX C compiler for your own customizations,A$          answer NO to this question:  c      * Do you want to install DATATRIEVE using object libraries built with the VAX C compiler [NO]?E  *              Product:      DTR or DTR-USER"              Producer:     DIGITAL               Version:      V7.2A&              Release Date: 22-OCT-1997  M      * Does this product have an authorization key registered and loaded? yes E      * Do you want to use default answers for all questions [YES]? nol  ,          VAXLSE is installed on your system.  ,          You now have the following options:  A              1.   Do a complete DATATRIEVE installation including -                   DATATRIEVE support for LSE.   <              2.   Do only DATATRIEVE support for LSE without(                   installing DATATRIEVE.  @              3.   Do a DATATRIEVE installation without including-                   DATATRIEVE support for LSE.J      * Select option [1]: 1I  /      A-2 Sample Installation Session (VAX Only)  A  Y      H                                   Sample Installation Session (VAX Only)    J                 The following Forms Management products have been found on                 this system:6                 TDMS (Terminal Data Management System).                 FMS  (Forms Management System)  C                 DATATRIEVE can be built to support any one of theseJI                 products, or, if desired, DATATRIEVE can be built withoutRA                 support of any of these Forms Management products   M         * Do you want DATATRIEVE to support one of these products  [YES]? yes E         * Do you wish to have TDMS Forms Management support [YES]? notE         * Do you wish to have FMS Forms Management support [YES]? yesN  J             It is possible to do more than one installation of DATATRIEVE.K             More than one installation of a single version may be desirable .             for a number of reasons including:  D                 o Use of multiple forms management products (such asE                   FMS and TDMS; DECforms is available in every image,o+                   if present on the system)U  B                 o Use of multiple foreign language translations of7                   DATATRIEVE (such as French or German)   E         * Do you plan to install this version more than once [NO]? no6N         * Do you want DTRSHR.EXE and DTRMSGS.EXE to be installed SHARED [YES]?>         * Do you want DTRAPI.EXE to be installed SHARED [YES]?=         * Do you want DTR32.EXE to be installed SHARED [YES]?!<         * Do you want DDMF.EXE to be installed SHARED [YES]?9         * Do you wish to have the plot definitions [YES]?E  G             Some optional material is available with this kit including @             the components of DATATRIEVE that can be tailored at             the installed site. 5         * Do you want the optional material [NO]? yes I         * Do you want to purge files replaced by this installation [YES]?   J             The DATATRIEVE IVP will be put in the SYS$COMMON:[SYSTEST.DTR]M             directory. You may run the IVP immediatly after the completion ofTL             the installation procedure answering YES to the next question or0             later issuing the following command:  :             @SYS$COMMON:[SYSTEST.DTR]DTR$IVP.COM DTR32.EXE    H                               Sample Installation Session (VAX Only) A-3           +      Sample Installation Session (VAX Only)A    ?      * Do you want to run the IVP after the installation [YES]? ,      * Proceed with this installation [YES]?    F          All questions regarding the installation have now been asked.  =          The installation of DATATRIEVE will now continue for "          20 minutes to 40 minutes.  ;      %VMSINSTAL-I-RESTORE, Restoring product save set B ... U      %VMSINSTAL-I-SYSDIR, This product creates system disk directory  VMI$ROOT:[DTR]. 4      %CREATE-I-EXISTS, VMI$ROOT:[DTR] already exists]      %VMSINSTAL-I-SYSDIR, This product creates system disk directory  VMI$ROOT:[SYSTEST.DTR].O<      %CREATE-I-EXISTS, VMI$ROOT:[SYSTEST.DTR] already exists  1          Providing the following LSE language(s):                 DATATRIEVE   /          During the installation, a file called 3          DTRSTUP.COM has been added to SYS$STARTUP:   H          The site-dependent start-up file, SYS$MANAGER:SYSTARTUP_VMS.COM.          should have the following line added:  )                $ @SYS$STARTUP:DTRSTUP.COM   ;      %VMSINSTAL-I-RESTORE, Restoring product save set C ... ]      %VMSINSTAL-I-SYSDIR, This product creates system disk directory  VMI$ROOT:[DTR.DTR$LIB]. <      %CREATE-I-EXISTS, VMI$ROOT:[DTR.DTR$LIB] already existsa      %VMSINSTAL-I-SYSDIR, This product creates system disk directory  VMI$ROOT:[DTR.DTR$LIB.ADT].m@      %CREATE-I-EXISTS, VMI$ROOT:[DTR.DTR$LIB.ADT] already existsb      %VMSINSTAL-I-SYSDIR, This product creates system disk directory  VMI$ROOT:[DTR.DTR$LIB.DEMO].A      %CREATE-I-EXISTS, VMI$ROOT:[DTR.DTR$LIB.DEMO] already exists c      %VMSINSTAL-I-SYSDIR, This product creates system disk directory  VMI$ROOT:[DTR.DTR$LIB.FORMS].iB      %CREATE-I-EXISTS, VMI$ROOT:[DTR.DTR$LIB.FORMS] already existsc      %VMSINSTAL-I-SYSDIR, This product creates system disk directory  VMI$ROOT:[DTR.DTR$LIB.GUIDE].0B      %CREATE-I-EXISTS, VMI$ROOT:[DTR.DTR$LIB.GUIDE] already existsc      %VMSINSTAL-I-SYSDIR, This product creates system disk directory  VMI$ROOT:[DTR.DTR$LIB.PLOTS]. B      %CREATE-I-EXISTS, VMI$ROOT:[DTR.DTR$LIB.PLOTS] already existsf      %VMSINSTAL-I-SYSDIR, This product creates system disk directory  VMI$ROOT:[DTR.DTR$LIB.DEMO.RDB].E      %CREATE-I-EXISTS, VMI$ROOT:[DTR.DTR$LIB.DEMO.RDB] already existsvg      %VMSINSTAL-I-SYSDIR, This product creates system disk directory  VMI$ROOT:[DTR.DTR$LIB.DEMO.DBMS]. F      %CREATE-I-EXISTS, VMI$ROOT:[DTR.DTR$LIB.DEMO.DBMS] already existsH      %DCL-I-SUPERSEDE, previous value of DTR$LIBRARY has been superseded  /      A-4 Sample Installation Session (VAX Only)            H                                   Sample Installation Session (VAX Only)    J             **************************************************************=             DATATRIEVE User Environment Test Packages (UETPs) G             have been provided and can be run after the installation istB             complete. They are invoked from DATATRIEVE as follows:  E             DTR> @sys$common:[systest.dtr]dtr     ! The general test" B             DTR> @sys$common:[systest.dtr]plots   ! The plots testD             DTR> @sys$common:[systest.dtr]rdb     ! The DEC Rdb testB             DTR> @sys$common:[systest.dtr]forms   ! The Forms test  F             Before invoking these files from a user's account you must#             execute the procedure :r4                             @DTR$LIBRARY:NEWUSER.COMD             This procedure loads the DATATRIEVE definitions into theI             user's dictionary and the data files in the user's directory. @             This procedure must be executed by each user needing#             the DATATRIEVE examplesaJ             **************************************************************  1         Restoring UETP-related Oracle Rdb objectso  B         %RMU-I-AIJRSTAVL, 0 after-image journals available for useA         %RMU-I-AIJISOFF, after-image journaling has been disabledTL         %RMU-I-LOGCONVRT, database root converted to current structure levelj         %RMU-S-CVTDBSUC, database SYS$COMMON:[DTR]PERSONNEL.RDB;1 successfully converted from version V6.1	         t          o V7.0_         %RMU-I-CVTCOMSUC, CONVERT committed for SYS$COMMON:[DTR]PERSONNEL.RDB;1 to version V7.0 Z         %RMU-I-ACLADDED, RMU access added to SYS$COMMON:[DTR]PERSONNEL.RDB;1 for [311,300]V         %RMU-I-ACLADDED, RMU access added to SYS$COMMON:[DTR]PERSONNEL.RDB;1 for [*,*]V         %RMU-W-USERECCOM, Use the RMU Recover command. The journals are not available.=         UETP-related Oracle Rdb objects Successfully RestoredA  V         %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...  /         Node 0 Session Control Application DDMFo,         at 2000-02-07-14:52:26.723+00:00Iinf           Identifiers   4             Name                              = DDMF  /         Node 0 Session Control Application DDMF ,         at 2000-02-07-14:52:28.493+00:00Iinf           Characteristics   H                               Sample Installation Session (VAX Only) A-5 a  c      +      Sample Installation Session (VAX Only)     ,          Addresses                         =
             {r                number = 30
             }   ,      Node 0 Session Control Application DDMF)      at 2000-02-07-14:52:30.583+00:00IinfR        Characteristics  5          Image Name                        = DDMF.COMt  8                  DATATRIEVE V7.2A Installation Procedure  B            Compaq Computer Corporation 2000. All rights reserved.  )      Executing IVP for:  DATATRIEVE V7.2Ae  A           Compaq Computer Corporation 2000. All rights reserved.   $          Test completed successfully$          ***************************  #          IVP COMPLETED SUCCESSFULLYt#          **************************   )      IVP completed for:  DATATRIEVE V7.2AT  9              Installation of DTRA V7.2 completed at 14:53g  .              VMSINSTAL procedure done at 14:53                            /      A-6 Sample Installation Session (VAX Only)  U  b                  H                                                                        BH         ________________________________________________________________  H                                 Sample Installation Session (Alpha Only)      C               This appendix lists the hardcopy terminal output fromaF               an installation of DATATRIEVE Version 7.2A on an OpenVMS               Alpha system.            $ @sys$update:vmsinstal   H                 OpenVMS AXP Software Product Installation Procedure V7.1  "         It is 7-FEB-2000 at 15:42.  7         Enter a question mark (?) at any time for help.   L         %VMSINSTAL-W-NOTSYSTEM, You are not logged in to the SYSTEM account.F         %VMSINSTAL-W-ACTIVE, The following processes are still active:                SNS$WATCHDOG                 IMBUSY$SRV73i2         * Do you want to continue anyway [NO]? YESF         * Are you satisfied with the backup of your system disk [YES]?F         * Where will the distribution volumes be mounted: DKA100:[DTR]  R         Enter the products to be processed from the first distribution volume set.          * Products:   DTRAXPA072<         * Enter installation options you wish to use (none):  1         The following products will be processed:a             DTRAXPA V7.2  ?                 Beginning installation of DTRAXPA V7.2 at 15:42   >         %VMSINSTAL-I-RESTORE, Restoring product save set A ...S         %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.s  ;                     DATATRIEVE V7.2A Installation ProcedureT  E               Compaq Computer Corporation 2000. All rights reserved.i  >         * Do you want support for Oracle CDD/Repository [YES]?  H                             Sample Installation Session (Alpha Only) B-1 s  s      -      Sample Installation Session (Alpha Only)     *              Product:      DTR or DTR-USER"              Producer:     DIGITAL               Version:      V7.2A&              Release Date: 22-OCT-1997  K      * Does this product have an authorization key registered and loaded? y D      * Do you want to use default answers for all questions [YES]? n  )          LSE is installed on your system.   ,          You now have the following options:  A              1.   Do a complete DATATRIEVE installation including -                   DATATRIEVE support for LSE.S  <              2.   Do only DATATRIEVE support for LSE without(                   installing DATATRIEVE.  @              3.   Do a DATATRIEVE installation without including-                   DATATRIEVE support for LSE.       * Select option [1]:n  6          FMS  (Forms Management System) has been found;          on this system. DATATRIEVE can be built to supportD          this product.  @      * Do you want support for this product in DATATRIEVE [YES]?  G          It is possible to do more than one installation of DATATRIEVE. H          More than one installation of a single version may be desirable+          for a number of reasons including:   A              o Use of multiple forms management products (such as D                FMS; DECforms is available in every image, if present                on the system)   ?              o Use of multiple foreign language translations of 4                DATATRIEVE (such as French or German)  ?      * Do you plan to install this version more than once [NO]? K      * Do you want DTRSHR.EXE and DTRMSGS.EXE to be installed SHARED [YES]?a;      * Do you want DTRAPI.EXE to be installed SHARED [YES]?b:      * Do you want DTR32.EXE to be installed SHARED [YES]?9      * Do you want DDMF.EXE to be installed SHARED [YES]?.6      * Do you wish to have the plot definitions [YES]?  1      B-2 Sample Installation Session (Alpha Only)c e  o      H                                 Sample Installation Session (Alpha Only)    G             Some optional material is available with this kit including @             the components of DATATRIEVE that can be tailored at             the installed site.d1         * Do you want the optional material [NO]?EI         * Do you want to purge files replaced by this installation [YES]?,    J             The DATATRIEVE IVP will be put in the SYS$COMMON:[SYSTEST.DTR]M             directory. You may run the IVP immediatly after the completion oftL             the installation procedure answering YES to the next question or0             later issuing the following command:  :             @SYS$COMMON:[SYSTEST.DTR]DTR$IVP.COM DTR32.EXE  B         * Do you want to run the IVP after the installation [YES]?/         * Proceed with this installation [YES]?   I             All questions regarding the installation have now been asked.m  @             The installation of DATATRIEVE will now continue for%             20 minutes to 40 minutes.O  >         %VMSINSTAL-I-RESTORE, Restoring product save set B ...X         %VMSINSTAL-I-SYSDIR, This product creates system disk directory  VMI$ROOT:[DTR].7         %CREATE-I-EXISTS, VMI$ROOT:[DTR] already existsa`         %VMSINSTAL-I-SYSDIR, This product creates system disk directory  VMI$ROOT:[SYSTEST.DTR].?         %CREATE-I-EXISTS, VMI$ROOT:[SYSTEST.DTR] already existsy  4             Providing the following LSE language(s):                   DATATRIEVE  2             During the installation, a file called6             DTRSTUP.COM has been added to SYS$STARTUP:  G             The site-dependent start-up file, SYS$MANAGER:SYSTARTUP.COMd1             should have the following line added:   ,                   $ @SYS$STARTUP:DTRSTUP.COM            H                             Sample Installation Session (Alpha Only) B-3 A  E      -      Sample Installation Session (Alpha Only)h    ]      %VMSINSTAL-I-SYSDIR, This product creates system disk directory  VMI$ROOT:[DTR.DTR$LIB]. <      %CREATE-I-EXISTS, VMI$ROOT:[DTR.DTR$LIB] already existsa      %VMSINSTAL-I-SYSDIR, This product creates system disk directory  VMI$ROOT:[DTR.DTR$LIB.ADT].m@      %CREATE-I-EXISTS, VMI$ROOT:[DTR.DTR$LIB.ADT] already existsb      %VMSINSTAL-I-SYSDIR, This product creates system disk directory  VMI$ROOT:[DTR.DTR$LIB.DEMO].A      %CREATE-I-EXISTS, VMI$ROOT:[DTR.DTR$LIB.DEMO] already exists c      %VMSINSTAL-I-SYSDIR, This product creates system disk directory  VMI$ROOT:[DTR.DTR$LIB.FORMS].TB      %CREATE-I-EXISTS, VMI$ROOT:[DTR.DTR$LIB.FORMS] already existsc      %VMSINSTAL-I-SYSDIR, This product creates system disk directory  VMI$ROOT:[DTR.DTR$LIB.GUIDE]. B      %CREATE-I-EXISTS, VMI$ROOT:[DTR.DTR$LIB.GUIDE] already existsc      %VMSINSTAL-I-SYSDIR, This product creates system disk directory  VMI$ROOT:[DTR.DTR$LIB.PLOTS]. B      %CREATE-I-EXISTS, VMI$ROOT:[DTR.DTR$LIB.PLOTS] already existsf      %VMSINSTAL-I-SYSDIR, This product creates system disk directory  VMI$ROOT:[DTR.DTR$LIB.DEMO.RDB].E      %CREATE-I-EXISTS, VMI$ROOT:[DTR.DTR$LIB.DEMO.RDB] already exists g      %VMSINSTAL-I-SYSDIR, This product creates system disk directory  VMI$ROOT:[DTR.DTR$LIB.DEMO.DBMS].TF      %CREATE-I-EXISTS, VMI$ROOT:[DTR.DTR$LIB.DEMO.DBMS] already exists      G          **************************************************************c:          DATATRIEVE User Environment Test Packages (UETPs)D          have been provided and can be run after the installation is?          complete. They are invoked from DATATRIEVE as follows:t  B          DTR> @sys$common:[systest.dtr]dtr     ! The general test"?          DTR> @sys$common:[systest.dtr]plots   ! The plots test-B          DTR> @sys$common:[systest.dtr]dbms    ! The DEC DBMS testA          DTR> @sys$common:[systest.dtr]rdb     ! The DEC Rdb test ?          DTR> @sys$common:[systest.dtr]forms   ! The Forms testa  C          Before invoking these files from a user's account you musts           execute the procedure :1                          @DTR$LIBRARY:NEWUSER.COMnA          This procedure loads the DATATRIEVE definitions into thesF          user's dictionary and the data files in the user's directory.=          This procedure must be executed by each user needingg           the DATATRIEVE examplesI          ****************************************************************M  /      Restoring UETP-related Oracle DBMS objectss  M          ********************************************************************-      1      B-4 Sample Installation Session (Alpha Only)            H                                 Sample Installation Session (Alpha Only)    H             A database for the DATATRIEVE UETP that utilizes Oracle DBMSM             cannot be created because the Oracle DBMS monitor is not running. I             Although the installation has not been aborted, the UETP willOG             not function properly. It is recommended that you start the >             Oracle DBMS monitor then re-run this installation.  P             ********************************************************************  4         Cleanup the UETP-related Oracle DBMS objects  1         Restoring UETP-related Oracle Rdb objects     O             *******************************************************************   G             A database for the DATATRIEVE UETP that utilizes Oracle Rdb-I             cannot be created because the DEC Rdb monitor is not running.tI             Although the installation has not been aborted, the UETP willIG             not function properly. It is recommended that you start theb=             Oracle Rdb monitor then re-run this installation.s  O             *******************************************************************s  3         Cleanup the UETP-related Oracle Rdb objectsrV         %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...  /         Node 0 Session Control Application DDMFu/         at 2000-02-07-15:49:10.480+00:00I42.900            IdentifiersP  4             Name                              = DDMF  /         Node 0 Session Control Application DDMF /         at 2000-02-07-15:49:10.527+00:00I42.899d           CharacteristicsS  /             Addresses                         =                 {                   number = 30                 }  /         Node 0 Session Control Application DDMF /         at 2000-02-07-15:49:11.289+00:00I42.892            Characteristicsc  H                             Sample Installation Session (Alpha Only) B-5 l  o      -      Sample Installation Session (Alpha Only)t    5          Image Name                        = DDMF.COM   8                  DATATRIEVE V7.2A Installation Procedure  H            Compaq Computer Corporation 1982, 1999. All rights reserved.  )      Executing IVP for:  DATATRIEVE V7.2A   A           Compaq Computer Corporation 2000. All rights reserved.S  $          Test completed successfully$          ***************************  #          IVP COMPLETED SUCCESSFULLY #          **************************   )      IVP completed for:  DATATRIEVE V7.2A   <              Installation of DTRAXPA V7.2 completed at 15:49  C          Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY   N          Creating installation data file: VMI$ROOT:[SYSUPD]DTRAXPA072.VMI_DATA  .              VMSINSTAL procedure done at 15:49                                        1      B-6 Sample Installation Session (Alpha Only)l l  c                  H                                                                        CH         ________________________________________________________________  H               List of Files Modified/Added by the Installation Procedure      G               This appendix lists the files that were added or modified D               during the product installation. Such list can also beF               found in the following file created during installation:  C               SYS$COMMON:[SYSMGR.VAXINFO$PRODUCTS]DTR072A_FILES.DATs  2               The file has the following contents:  Q               !  File:      SYS$COMMON:[SYSMGR.VAXINFO$PRODUCTS]DTR072A_FILES.DAT 3               !  Product:   Compaq DATATRIEVE V7.2Ao-               !  Installed:  3-FEB-2000 12:03 #               !  License:   UNKNOWN ^               !*******************************************************************************W               !  This file is associated with the above product.  It must NOT be moved, $               !  edited, or deleted.^               !*******************************************************************************.               !  Flags: (for DIGITAL use only):               !     $D = Delete file when deleting product8               !     $I = File inserted into IMAGELIB.OLB8               !     $K = Keep file when deleting product6               !     $M = Multiple version/product file^               !-------------------------------------------------------------------------------:               SYS$COMMON:[SYSHLP]DTR072A.RELEASE_NOTES /$DG               SYS$COMMON:[SYSMGR.VAXINFO$PRODUCTS]DTR072A_FILES.DAT /$DaF               SYS$SYSROOT:[DECW$BOOK]DTR_DECW_HELP_MOTIF.DECW$BOOK /$DK               SYS$SYSROOT:[DECW$BOOK]DTR_DECW_HELP_MOTIF.DECW$BOOKSHELF /$DV/               SYS$SYSROOT:[DTR]ACCOUNTS.DAT /$Me-               SYS$SYSROOT:[DTR]ANNUAL.DAT /$MT:               SYS$SYSROOT:[DTR]DTR$DECTERM_DEFAULT.DAT /$M-               SYS$SYSROOT:[DTR]DTRAPI.OLB /$Dy-               SYS$SYSROOT:[DTR]DTRBLD.COM /$Dr/               SYS$SYSROOT:[DTR]DTREXTRE.OBJ /$Ms-               SYS$SYSROOT:[DTR]DTRLIB.OLB /$D .               SYS$SYSROOT:[DTR]DTRMSGS.MEM /$M/               SYS$SYSROOT:[DTR]DTRWN11a.ZIP /$D1  H           List of Files Modified/Added by the Installation Procedure C-1    S      ?      List of Files Modified/Added by the Installation Procedurei    *            SYS$SYSROOT:[DTR]FAMILY.DAT /$M+            SYS$SYSROOT:[DTR]FAMILY.FORM /$Mp+            SYS$SYSROOT:[DTR]FAMILY.IFDL /$M )            SYS$SYSROOT:[DTR]FORMS.FLB /$MC,            SYS$SYSROOT:[DTR]LOAD_ADT.DTR /$M,            SYS$SYSROOT:[DTR]LOAD_DAB.DTR /$M1            SYS$SYSROOT:[DTR]LOAD_DATA_CDO.COM /$MS1            SYS$SYSROOT:[DTR]LOAD_DATA_DMU.DTR /$Md-            SYS$SYSROOT:[DTR]LOAD_DBMS.DTR /$Mb.            SYS$SYSROOT:[DTR]LOAD_FORMS.DTR /$M,            SYS$SYSROOT:[DTR]LOAD_RDB.DTR /$M-            SYS$SYSROOT:[DTR]LOAD_UETP.DTR /$Md+            SYS$SYSROOT:[DTR]NEWUSER.COM /$Mb)            SYS$SYSROOT:[DTR]OWNER.DAT /$Mg)            SYS$SYSROOT:[DTR]OWNER.SEQ /$M ,            SYS$SYSROOT:[DTR]PAYABLES.DAT /$M*            SYS$SYSROOT:[DTR]PERSON.DAT /$M-            SYS$SYSROOT:[DTR]PERSONNEL.RDB /$Me-            SYS$SYSROOT:[DTR]PERSONNEL.SNP /$Mi'            SYS$SYSROOT:[DTR]PET.DAT /$M +            SYS$SYSROOT:[DTR]PROJECT.DAT /$MI2            SYS$SYSROOT:[DTR]REMOTE_DECTERM.COM /$M-            SYS$SYSROOT:[DTR]SAILBOAT.IFDL /$Mc)            SYS$SYSROOT:[DTR]SALES.DAT /$Mr-            SYS$SYSROOT:[DTR]TERMSERVE.OLB /$Mn)            SYS$SYSROOT:[DTR]YACHT.DAT /$Mt*            SYS$SYSROOT:[DTR]YACHT.FORM /$M*            SYS$SYSROOT:[DTR]YACHT.IFDL /$M)            SYS$SYSROOT:[DTR]YACHT.SEQ /$Mu+            SYS$SYSROOT:[DTR]dtrfnlb.mlb /$M +            SYS$SYSROOT:[DTR]idtrfnd.mar /$My3            SYS$SYSROOT:[SYS$STARTUP]DTRSTUP.COM /$Dq+            SYS$SYSROOT:[SYSEXE]DDMF.COM /$DA+            SYS$SYSROOT:[SYSEXE]DDMF.EXE /$DV5            SYS$SYSROOT:[SYSEXE]DEC_DATATRIEVE.CLD /$Do,            SYS$SYSROOT:[SYSEXE]DTR32.EXE /$D/            SYS$SYSROOT:[SYSEXE]DTREXTRE.EXE /$DR.            SYS$SYSROOT:[SYSEXE]DTRHELP.EXE /$D.            SYS$SYSROOT:[SYSHLP]DTRHELP.HLB /$M-            SYS$SYSROOT:[SYSLIB]DTRADT.DAT /$Mn/            SYS$SYSROOT:[SYSLIB]DTRGUIDE.DAT /$MX-            SYS$SYSROOT:[SYSLIB]DTRSHR.EXE /$Du5            SYS$SYSROOT:[SYSLIB]VAX_DATATRIEVE.UID /$Mo    C      C-2 List of Files Modified/Added by the Installation ProcedureE s  o      H               List of Files Modified/Added by the Installation Procedure    0               SYS$SYSROOT:[SYSMSG]DTRMSG.EXE /$M3               SYS$SYSROOT:[SYSTEST.DTR]DBMS.DTR /$M 6               SYS$SYSROOT:[SYSTEST.DTR]DTR$IVP.COM /$M2               SYS$SYSROOT:[SYSTEST.DTR]DTR.DTR /$M4               SYS$SYSROOT:[SYSTEST.DTR]FORMS.DTR /$M2               SYS$SYSROOT:[SYSTEST.DTR]IVP.DTR /$M4               SYS$SYSROOT:[SYSTEST.DTR]PLOTS.DTR /$M2               SYS$SYSROOT:[SYSTEST.DTR]RDB.DTR /$M;               SYS$SYSROOT:[VUE$LIBRARY.USER]VUE$DTR.COM /$M)                                                                        H           List of Files Modified/Added by the Installation Procedure C-3