                                     ?                  DEC_Ada_______________________________________ =                  Installation Guide for OpenVMS Alpha Systems   *                  Order Number: AA-PW1VC-TE                      May 1999   @                  This guide contains instructions for installingA                  DEC Ada Version 3.5 on OpenVMS Alpha systems. It C                  also explains how to read the online release notes C                  before or after installing the product. This guide C                  applies to DEC Ada Version 3.5 and all maintenance 1                  updates throughout that version.             C                  Revision/Update Information:  This is a new guide.   D                  Operating System & Version:   OpenVMS Alpha Version>                                                6.2 through 7.2  B                  Software Version:             DEC Ada Version 3.5        .                  Digital Equipment Corporation'                  Maynard, Massachusetts                  A        __________________________________________________________ #        First Printing, January 1993         Revised, May 1999  =        Digital Equipment Corporation makes no representations >        that the use of its products in the manner described in?        this publication will not infringe on existing or future ?        patent rights, nor do the descriptions contained in this ?        publication imply the granting of licenses to make, use, ;        or sell equipment or software in accordance with the         description.   <        Possession, use, or copying of the software described;        in this publication is authorized only pursuant to a :        valid written license from Digital or an authorized        sublicensor.   =         Digital Equipment Corporation 1992, 1999. All Rights         Reserved.  >        The postpaid Reader's Comments forms at the end of this=        document request your critical evaluation to assist in &        preparing future documentation.  7        Compaq, the Compaq logo and the DIGITAL logo are <        registered trademarks of Compaq Computer Corporation.  >        Bookreader, DEC, DEC Ada, DEC C, DECdocument, Debugger,?        DECnet, DECset, DECstation, DECthreads, DIGITAL, DIGITAL <        Fortran, DIGITAL FUSE, DIGITAL Ladebug, Digital UNIX,A        OpenVMS, ULTRIX, VAX, VAXcluster, VAX DOCUMENT, VMScluster 8        are trademarks of Digital Equipment Corporation.)  ;        Compaq Ada was formerly known as DEC Ada. References >        to DEC Ada in product components should be construed as         references to Compaq Ada.  A                                                            ZK6255   ,        This document is available on CD-ROM.  A        This document was prepared using VAX DOCUMENT Version 2.1.                                > ______________________________________________________________  ?                                                        Contents     ? ..................................................            v     $   Preparing for DEC Ada Installation  5      1.1   Required Operating System and Prerequisite ?            Hardware and Software........................    1-1 ?      1.2   License Registration.........................    1-2 ?      1.3   VMScluster Considerations....................    1-3 ?      1.4   Installation Procedure Requirements..........    1-3 ?      1.4.1     Privileges and Disk Space................    1-3 ?      1.4.2     System Parameters........................    1-4 ?      1.4.2.1     Checking UAF Parameters................    1-5 8      1.4.2.2     Calculating the Values for GBLPAGES and?                  GBLSECTIONS............................    1-5 6      1.4.2.3     Changing System Parameter Values with?                  AUTOGEN................................    1-6 ?      1.4.3     Process Account Quotas...................    1-7 ?      1.4.4     VMSINSTAL Requirements...................    1-8 ?      1.4.5     Checking for RTL Locked Open.............    1-8 ?      1.4.6     Backing Up Your System Disk..............    1-9      Installing DEC Ada  ?      2.1   The Installation Procedure...................    2-1 ?      2.1.1     Invoke VMSINSTAL.........................    2-1 ?      2.1.2     Confirm System Backup ...................    2-3 ?      2.1.3     Mount the Media..........................    2-3 ?      2.1.4     Select a Release Notes Option............    2-4 3      2.1.5     Choose the Installation Verification ?                Procedure Option.........................    2-5 ?      2.1.6     Select Installation Options .............    2-5 ?      2.1.7     Read Informational Messages..............    2-6   ?                                                             iii                  6        2.1.8     Observe the Installation VerificationA                  Procedure................................    2-7 A        2.1.9     End the Installation Procedure...........    2-8 A        2.2   Error Recovery ..............................    2-8 4        2.3   Keeping the Currently Existing CompilerA              Available....................................    2-9 8        2.3.1     Saving the Currently Existing Help FileA                  .........................................   2-12 7        2.3.2     Saving the Currently Existing Examples A                  Directory................................   2-13 A        2.4   Installing DEC Ada on a VMScluster...........   2-13 A        2.5   Postinstallation Notes.......................   2-14       3  After Installing DEC Ada  2        3.1   Running the Installation VerificationA              Procedure Separately.........................    3-1 A        3.2   Error Conditions.............................    3-1 A        3.3   Installing Updates...........................    3-2 A        3.4   Determining and Reporting Problems...........    3-3     A  Sample Installation   %  B  Files and Logical Names Installed   A        B.1   File Names...................................    B-1 A        B.2   Logical Names................................    B-2       Tables   A        1         Conventions Used in This Guide...........     vi   +        1-1       Disk Space Requirements at A                  Installation.............................    1-4   2        1-2       Minimum Required System ParameterA                  Values...................................    1-4   :        1-3       Process Account Quotas for the InstallingA                  Account..................................    1-7   A        B-1       DEC Ada Logical Names and Locations......    B-2     iv                            D     ________________________________________________________________  D                                                              Preface      C           This guide explains how to install DEC Ada Version 3.5 on             OpenVMS Alpha systems.  D           Keep this guide with your distribution kit. You need it toA           install maintenance updates or to reinstall DEC Ada for            any other reason.   B             ________________________Note  ________________________  9             Digital Equipment Corporation is now owned by @             Compaq Computer Corporation. Compaq Ada was formerly>             known as DEC Ada. References to DEC Ada in product;             components should be construed as references to              Compaq Ada.   A             _____________________________________________________        Intended Audience   D           This guide is intended for the system manager who installs           DEC Ada software.                           D                                                                    v                   Document Structure   A        This guide contains the following chapters and appendixes:   ?        o  Chapter 1 describes the operating system and hardware ;           requirements for DEC Ada installation and related <           procedures that you complete before installing DEC           Ada.  ?        o  Chapter 2 describes the step-by-step instructions for            the installation.   :        o  Chapter 3 describes postinstallation actions and           considerations.   >        o  Appendix A contains the output from a sample DEC Ada           installation.   ;        o  Appendix B contains a list of files installed and :           logicals defined as a result of the installation           procedure.    Conventions  8        Table 1 shows the conventions used in this guide.  A        Table_1_Conventions_Used_in_This_Guide____________________   A        Convention_______Description______________________________   @        $                A dollar sign ($) represents the VMS DCL&                         system prompt.  A        <Return>         In interactive examples, a label enclosed ?                         in a box indicates that you press a key ?                         on the terminal, for example, <Return>.   A        Ctrl/x           The key combination Ctrl/x indicates that A                         you must press the key labeled Ctrl while A                         you simultaneously press another key, for 2                         example, Ctrl/Y or Ctrl/Z.  9        boldface         In interactive examples, boldface =        monospace text   monospace text represents user input.   A                                          (continued on next page)     vi                  D           Table_1_(Cont.)_Conventions_Used_in_This_Guide____________  D           Convention_______Description______________________________  <           file-spec . . .  A horizontal ellipsis following a@                            parameter, option, or value in syntaxA                            descriptions indicates that additional @                            parameters, options, or values can be#                            entered.   =           n                A lowercase italic n indicates the 3                            generic use of a number.   B            . . .           A horizontal ellipsis in a code exampleB                            or figure indicates that not all of the0                            statements are shown.  @           .                A vertical ellipsis in an interactiveC           .                figure or example indicates that not all C           .                of the commands and responses are shown.   ;           italic text      Italic text emphasizes important @                            information, indicates variables, and@                            indicates complete titles of manuals.B                            Italic text also represents information@                            that can vary in system messages (for;                            example, Internal error number.)   <           UPPERCASE TEXT   Uppercase indicates the name of aB                            command, routine, parameter, procedure,B                            utility, file, file protection code, orD           _________________the_abbreviation_for_a_system_privilege._                          D                                                                  vii                       D                                                                    1D     ________________________________________________________________  D                                   Preparing for DEC Ada Installation      B           This chapter discusses the preparations and requirementsD           necessary for installing DEC Ada on OpenVMS Alpha systems.  C           The information in the installation guide pertains to the @           DEC Ada Version 3.5 for OpenVMS Alpha release only. ItA           is required that you review carefully the release notes B           for each version because they capture important release-@           oriented information and advise you of changes between           versions.   @           Your bill of materials (BOM) and indented bills report>           (BIL) specify the number and contents of your media.>           Be sure to verify the contents of your kit with this<           information. If your kit is damaged or if you find<           that parts of it are missing, contact your DIGITAL           representative.   B             ________________________Note  ________________________  ;             DEC Ada provides online release notes. They are :             contained in the kit with the compiler and its>             associated components. DIGITAL strongly recommends=             that you read the release notes before proceeding ?             with the installation. For information on accessing 6             the online release notes, see Section 2.1.  A             _____________________________________________________   ?     1.1 Required Operating System and Prerequisite Hardware and          Software  B           DEC Ada Version 3.5 supports OpenVMS Version 6.2 through           7.2.    D                               Preparing for DEC Ada Installation 1-1           &     Preparing for DEC Ada Installation    C           For a complete list of the required operating system com- B           ponents, current hardware requirements, and prerequisiteC           and optional software and their required version numbers, D           see the Software Product Description (SPD), that is on the/           DEC Ada kit in SYS$HELP:ADA03n_SPD.*.        1.2 License Registration  >           If you are installing DEC Ada Version 3.5 on a newly=           licensed node or cluster, you must first register a ?           License Product Authorization Key (License PAK) using @           the License Management Facility (LMF). The License PAKD           can be shipped with the kit if you ordered the license andB           media together. Otherwise, the PAK is shipped separately4           to a location based on your license order.  C           If you are installing DEC Ada Version 3.5 as an update on ?           a node or cluster already licensed for this software, =           you must register the Service Update PAK (SUP) that @           is included in your Service Update Kit. If you alreadyD           registered a License PAK or a SUP for this product on this?           node or cluster, you do not need to register the SUP.   ?           If you are installing an update of DEC Ada but lack a @           service contract, call your DIGITAL representative for3           instructions on how to get a License PAK.   A           If you are installing prerequisite or optional software B           with DEC Ada, review the PAK status and install the PAKs>           for any prerequisite or optional software before you           install DEC Ada.  D           You must register and load your license for DEC Ada beforeA           you start the installation. To register a license under @           OpenVMS, first log in to the system manager's account,C           SYSTEM. You then have a choice of two ways to perform the            registration:   A           o  Invoke the SYS$UPDATE:VMSLICENSE.COM procedure. When C              it prompts you for information, respond with data from               your License PAK.  >           o  At the DCL prompt ($), enter the LICENSE REGISTERD              command with the appropriate qualifiers that correspond(              to License PAK information.  *     1-2 Preparing for DEC Ada Installation           D                                   Preparing for DEC Ada Installation    ?           If you plan to use DEC Ada on more than one node in a ?           VMScluster, you need to perform a license load on the ;           other nodes after you complete this installation.   @           For complete information on using LMF, see the OpenVMS,           License Management Utility Manual.  !     1.3 VMScluster Considerations   ?           If you are running DEC Ada on a VMScluster, VMSINSTAL @           automatically installs new versions as known or shared>           images only on the machine on which the installation:           is actually performed. You must manually install=           new versions as known or shared images on other ma- <           chines using the OpenVMS Install Utility or invokeB           SYS$STARTUP:ADA$STARTUP.COM on each of the other cluster           members.  +     1.4 Installation Procedure Requirements_  <           This section and those that follow discuss various>           requirements for installing DEC Ada on OpenVMS Alpha           systems.  #     1.4.1 Privileges and Disk Spaces  A           To install DEC Ada, you must be logged in to an accountn?           that has SETPRV or at least the following privileges:d             o  CMKRNLe             o  WORLD             o  SYSPRVn  B           VMSINSTAL turns off BYPASS privilege at the start of the           installation.   B           The installation checks the system disk for the space itC           requires to install DEC Ada. For a summary of the storage )           requirements, refer to the SPD.   D           To determine the number of free disk blocks on the currentD           system disk, enter the following command at the DCL prompt           ($):  %           $ SHOW DEVICE SYS$SYSDEVICEt  D                               Preparing for DEC Ada Installation 1-3           &     Preparing for DEC Ada Installation    A           Table 1-1 identifies the various installation scenarios 8           and the corresponding disk space requirements.    D           Table_1-1_Disk_Space_Requirements_at_Installation_________  &                                 DuringD           Scenario______________Installation_____After_Installation_  >           DEC Ada never         140,000 blocks   80,000 blocks           previously installed  >           DEC Ada previously    100,000 blocks   15,000 blocks           installed, not           saving previous D           product___________________________________________________       1.4.2 System Parametersi  >           Installing DEC Ada requires certain system parameter?           settings. Table 1-2 lists the minimum required system A           parameter values for the installation. Depending on thetA           type of programs and applications running at your site, 9           you might need higher values for some settings.   D           Table_1-2_Minimum_Required_System_Parameter_Values________  D           System_Parameter___________Minimum_Value__________________  6           GBLPAGES[1]                11500 + DCLTABLES  '           GBLSECTIONS[1]             41 D           [1]The_values_listed_for_these_system_parameters_represent  =           the number of free global pages and global sections A           required for the installation, not the total number you 5           need to run your system and other software.tD           __________________________________________________________  :           To use DEC Ada, each account or batch queue thatB           invokes the DEC Ada compiler must have TMPMBX and NETMBX           privileges.o  1           The following sections show you how to:   !           o  Check UAF parameters_  >           o  Calculate values for the GBLPAGES and GBLSECTIONS              system parameters  *     1-4 Preparing for DEC Ada Installation .  .      D                                   Preparing for DEC Ada Installation    =           o  Change parameter values with the AUTOGEN command               procedure  #     1.4.2.1 Checking UAF Parameters-  C           Before you install DEC Ada, you should check whether your D           account has sufficient quotas to perform the installation.D           You can check the quotas by entering the following command<           at the DCL prompt to invoke the AUTHORIZE Utility:  $           $ RUN SYS$SYSTEM:AUTHORIZE           UAF> SHOW SYSTEM  C           After checking your quotas, enter the EXIT command at the -           UAF> prompt to return to DCL level.   ?     1.4.2.2 Calculating the Values for GBLPAGES and GBLSECTIONS1  C           To install and run DEC Ada, you must have sufficient freeG?           global pages and global sections. You must first findsA           out how many free global pages and sections you have onLC           your system. Then use AUTOGEN if you need to increase the 5           GLBPAGES and GBLSECTIONS system parameters.c  =           For example, you can use the WRITE command with theC>           F$GETSYI lexical function to find the number of freeA           global pages and global sections. The following example A           shows how to get this information at your terminal (the "           default for SYS$OUTPUT):  6           $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES")           15848p6           $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS")           24  ?           If the returned values are greater than the values in ?           Table 1-2, you do not need to increase the values for D           these parameters. If the value of either free global pagesA           or global sections is less than the value in Table 1-2,i:           you must increase that system parameter setting.  A           Section 1.4.2.3 describes the procedures for increasing.%           these values using AUTOGEN.t    D                               Preparing for DEC Ada Installation 1-5 .  .      &     Preparing for DEC Ada Installation    9     1.4.2.3 Changing System Parameter Values with AUTOGEN.  <           Use the AUTOGEN command procedure to change system>           parameters. AUTOGEN automatically adjusts values forB           parameters that are associated with the values you resetB           manually. To change system parameters with AUTOGEN, edit           the following file:   "           SYS$SYSTEM:MODPARAMS.DAT  A           To change a parameter value listed in this file, delete.D           the current value associated with that parameter and enter           the new value.  =           To add a new parameter, add a line to the file that.@           includes both the name of the parameter and its value.           For example:             WSMAX = 1024  ?           To modify incremental parameters such as GBLPAGES andaA           GBLSECTS, use ADD_. The following example increases the &           global page setting by 2000:             ADD_GBLPAGES = 2000.  C           When you set the page file quota, be careful not to use a.D           value that exceeds the amount of page file space available           on the system.  C           After you make all your changes, exit from the editor and B           execute the AUTOGEN procedure to recalculate your systemD           parameters. Enter the following command at the DCL prompt:  .           $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT  @           When you specify REBOOT, AUTOGEN performs an automatic@           system shutdown and then reboots the system. Any users>           logged in to the system are immediately disconnected@           during the shutdown. The automatic reboot puts the new'           parameter values into effect._  B           The AUTOGEN command procedure automatically adjusts some>           of the SYSGEN parameters based on the consumption of@           resources since the last reboot. If you do not want toB           take advantage of this automatic adjustment, include the;           NOFEEDBACK qualifier on the AUTOGEN command line.   *     1-6 Preparing for DEC Ada Installation _  _      D                                   Preparing for DEC Ada Installation    B           For more information about using AUTOGEN, see the systemD           management documentation for the OpenVMS operating system.        1.4.3 Process Account Quotas  A           The account you use to install DEC Ada must have suffi- A           cient quotas to enable you to perform the installation. B           Table 1-3 summarizes the minimum process quotas required<           for the installation account. Larger quotas may be7           required for other work done by this account.   =           Table 1-3 Process Account Quotas for the Installing D           __________Account_________________________________________  D           Account_Quota_____Value___________________________________              ASTLM               24              BIOLM               18              BYTLM            18000              DIOLM               18              ENQLM              300  D           FILLM______________100____________________________________  @           User account quotas are stored in the file SYSUAF.DAT.=           Use the Authorize Utility (AUTHORIZE) to verify and ?           change user account quotas. First, set your directoryB0           to SYS$SYSTEM and then, run AUTHORIZE:  "           $ SET DEFAULT SYS$SYSTEM           $ RUN AUTHORIZEc           UAF>  D           At the UAF> prompt, enter the SHOW command with an account:           name to check a particular account. For example:             UAF> SHOW SMITH_  D           To change a quota, enter the MODIFY command. The followingC           example changes the FILLM quota for the SMITH account andt&           then exits from the utility:  %           UAF> MODIFY SMITH /FILLM=50            UAF> EXIT   D                               Preparing for DEC Ada Installation 1-7 t  i      &     Preparing for DEC Ada Installation    >           After you exit from the utility, the system displaysA           messages indicating whether changes were made. Once the C           changes have been made, you must log out and log in again ,           for the new quotas to take effect.  ?           For more information on modifying account quotas, seee@           the description of the Authorize Utility in the systemD           management documentation for the OpenVMS operating system.        1.4.4 VMSINSTAL Requirements  7           When you invoke VMSINSTAL, it checks whether:v  6           o  You are logged in to a privileged account  2           o  Any users are logged in to the system  6           o  You have adequate quotas for installation  ?           If problems are detected during installation, in someh@           instances you can enter Yes to continue. If you do not@           want to continue, enter No or press Return to stop theD           installation process. Then correct the problem and restart           the installation.u  &     1.4.5 Checking for RTL Locked Open  C           Installing the DEC Ada RTL when an Ada program is runninge>           can result in more than one version of the RTL image>           residing on the system as a shared image. If this is>           a concern, enter the following command, look for oldB           versions of ADARTL files locked open, and identify which"           process has them locked.  0           $ SHOW DEVICE /FILE /SYSTEM <DISKNAME>  C           If possible, stop the identified process and then restart C           it. For example, the OpenVMS Security Server uses the DEC =           Ada RTL. Enter the following command to restart it:   (           $ SET SERVER SECURITY /RESTART        *     1-8 Preparing for DEC Ada Installation e  n      D                                   Preparing for DEC Ada Installation    %     1.4.6 Backing Up Your System Diska  A           At the beginning of the installation, VMSINSTAL asks ifyA           you have backed up your system disk. DIGITAL recommendsb@           that you do a system disk backup before installing any           software.   =           Use the backup procedures established at your site. =           For details on performing a system disk backup, see A           the section on the OpenVMS Backup Utility in the system_D           management documentation for the OpenVMS operating system.                                                                    D                               Preparing for DEC Ada Installation 1-9    h                  D                                                                    2D     ________________________________________________________________  D                                                   Installing DEC Ada      A           This chapter explains how to install DEC Ada on OpenVMSd<           Alpha systems. Section 2.1 contains a step-by-step4           description of the installation procedure.  "     2.1 The Installation Procedure  B           DEC Ada Version 3.5 (ADA035) contains four save sets (A,B           B, C and D). The DEC Ada installation procedure consistsB           of a series of questions and informational messages. See?           Appendix A for the output from a sample installation.   C           The procedure takes approximately 15 minutes to complete.   D           If it is not already inserted, place the compact disk (CD)"           media into the CD drive.  @           To abort the installation procedure at any time, pressC           Ctrl/Y. When you press Ctrl/Y, the installation procedure D           deletes all files that it has created up to that point and;           exits. You can then start the installation again.   @           When the system prompts you with a question during theD           installation procedure, the default answer is often listed           in brackets ([ ]).       2.1.1 Invoke VMSINSTAL  A           To start the installation, invoke the VMSINSTAL commandrA           procedure from a privileged account, such as the SYSTEME4           account. The command format is as follows:  =           SYS$UPDATE:VMSINSTAL saveset-name device:[pathname]t
     OPTIONS Nr  B           VMSINSTAL is in the SYS$UPDATE directory. To install DEC+           Ada, enter the following command:o  :           $ @SYS$UPDATE:VMSINSTAL ADA03n DKA100: OPTIONS N  D                                               Installing DEC Ada 2-1                Installing DEC Ada    =           The elements of the VMSINSTAL command procedure areu           defined as follows:              saveset-nameC           The installation name for the component. For DEC Ada, uset'           the installation name ADA03n.e             nhD           The letter n represents the maintenance update of DEC Ada.C           See the label on the DEC Ada distribution kit or the billy@           of materials for the maintenance update number of yourD           kit. For DEC Ada Version 3.5, the maintenance update is 5.             device:[pathname] ?           The name of the device on which you plan to mount thes           media.             OPTIONS NyB           An optional parameter that indicates that you want to beC           asked to choose one of the four options for reviewing thetC           release notes. (See Section 2.1.4). If you do not includelC           the OPTIONS N parameter, VMSINSTAL does not ask you aboutf           the release notes.  ?           You should review the release notes before proceedingq?           with the installation in case they contain additionalPC           information about the installation. If you are restartingi@           the installation and have already reviewed the release6           notes, you do not need to specify OPTIONS N.  B           You can select several other options when you invoke the&           VMSINSTAL command procedure:  $           o  Option (A): Auto_answer  A              Initially, creates a file that contains your answerseA              to VMSINSTAL questions and prompts. You can then userC              the option (and the answer file) to save time during awD              reinstallation (typically after upgrading your system).  %           o  Option (G): Get save setR  >              Lets you store product save sets temporarily on a2              magnetic tape or in a disk directory.  !           o  Option (L): File logi       2-2 Installing DEC Ada           D                                                   Installing DEC Ada    C              Logs all activity to the terminal during installation.d  @           See the software installation in the system management<           documentation for the OpenVMS operating system for?           detailed information on these options. If you specifyU@           more than one option, separate each option name with a+           comma (for example, OPTIONS A,N).M  @           The following example invokes VMSINSTAL to install DECD           Ada from disk drive DKA100: and shows the system response.A           This example uses the OPTIONS N release note parameter.   :           $ @SYS$UPDATE:VMSINSTAL ADA03n DKA100: OPTIONS N  H                 OpenVMS AXP Software Product Installation Procedure Vm.n  %           It is dd-mmm-yyyy at hh:mm.c9           Enter a question mark (?) at any time for help.e  D           If you do not supply either the product name or the device2           name, VMSINSTAL prompts you for options.       2.1.2 Confirm System Backupm  >           VMSINSTAL asks if you are satisfied with your system           backup.b  H           * Are you satisfied with the backup of your system disk [YES]?  ;           You should always back up your system disk before ?           performing an installation. If you are satisfied withiB           the backup of your system disk, press Return. Otherwise,B           enter No to discontinue the installation. After you back@           up your system disk, you can restart the installation.       2.1.3 Mount the MediaS  A           If you omitted the device name on the VMSINSTAL commandc-           line, the following prompt appears:i  ;           * Where will the distribution volumes be mounted:W  D           If this prompt appears, enter the name of the distributionD           (media) device and directory that contains the DEC Ada kitD           (save set). For example, if the media is contained on a CDD           located on unit DKA100:, enter DKA100:[ADA03n] in reply to>           this question (where n is the minor version number).  D                                               Installing DEC Ada 2-3 _  _           Installing DEC Ada    '     2.1.4 Select a Release Notes Option4  @           If you specified OPTIONS N when you invoked VMSINSTAL,A           you are now asked to choose one of the four options for &           reviewing the release notes.  M           Release notes included with this kit are always copied to SYS$HELP.   +           Additional Release Notes Options:g  $            1.  Display release notes"            2.  Print release notes            3.  Both 1 and 2e             4.  None of the above             * Select option [2]:  @           If you select option 1, VMSINSTAL displays the release<           notes immediately on the console terminal. You can?           terminate the display at any time by pressing Ctrl/C._  ?           If you select option 2, VMSINSTAL prompts you for the_C           name of the print queue that you want to use to print the            release notes:  #           * Queue name [SYS$PRINT]:e  >           You can press Return to send the file to the defaultB           output print device or you can enter another queue name.  @           If you select option 3, VMSINSTAL displays the releaseD           notes immediately on the console terminal and then prompts7           you for a queue name for the printed version.C  B           Select option 4 if you have already reviewed the release4           notes and are continuing the installation.  9           Next VMSINSTAL displays the following question:   >           * Do you want to continue the installation [N]?: YESF           %VMSINSTAL-I-RELMOVED, The product's release notes have been?                                              moved to SYS$HELP.   C           To continue the installation, enter Yes. Otherwise, press A           Return if you want to stop the installation to read the >           release notes. In either case, the release notes are5           copied to a file in the SYS$HELP directory:y       2-4 Installing DEC Ada c  t      D                                                   Installing DEC Ada    '           SYS$HELP:ADA03n.RELEASE_NOTESt  D           The release notes are also available in POSTSCRIPT format.<           The file name is SYS$HELP:ADA03n.RELEASE_NOTES_PS.  ?     2.1.5 Choose the Installation Verification Procedure Option>  D           The installation procedure now asks if you want to run the4           Installation Verification Procedure (IVP).  D           * Do you want to run the IVP after the installation [YES]?  >           The IVP for DEC Ada checks that the installation was=           successful. It is recommended that you run the IVP.e  @           After installing DEC Ada, you can run the IVP indepen-A           dently to verify that the software is available on yourc>           system. You might need to run the IVP after a system=           failure to make sure that users can access DEC Ada.g  7           For more information on IVP, see Section 3.1.   %     2.1.6 Select Installation Options(  C           DEC Ada provides support for the DEC Source Code AnalyzerT@           (SCA). SCA is an optional, interactive, multilanguage,C           source code cross-reference and static analysis tool. TherA           information in the SCA library for the predefined units,B           allows you to query SCA about symbols, declarations, and8           subprograms contained in the predefined units.  @           If you have SCA installed on your system and intend toB           use it to analyze DEC Ada programs, type Yes in responseC           to the prompt. If you are not going to use SCA or you areaC           concerned about saving disk space, type No in response to            the prompt.5  L           * Do you want to include SCA analysis data file for the predefined              units [YES]?<Return>  C           If you need to know how much disk space this library will @           take before you can answer the prompt, type a question@           mark (?)  to obtain specific information on disk space/           requirements before typing Yes or No.h  D                                               Installing DEC Ada 2-5 A  S           Installing DEC Ada    B           If you typed Yes or pressed Return, an SCA analysis dataH           file for the DEC Ada predefined units (ADA$SCA_PREDEFINED.ANA)A           is copied to the SYS$LIBRARY directory during installa- C           tion. To make this information available, you must create A           an SCA library and load the data from the file into them           library.  =           If the current version of DEC Ada on your system isx<           different from the version you are installing, theA           installation procedure allows you to save the currently =           existing version. If you want to save the currentlyeA           existing compiler, answer Yes. If not, answer No to the.           prompt.   E           * Do you want to save the currently existing compiler [NO]?h  A           If you need to know exactly which files are saved, then B           type a question mark (?)  to obtain specific information;           before typing Yes or No. For more information seeB           Section 2.3.  D           The installation procedure will ask if you want to installC           an IEEE floating-point predefined library. The default is A           "no", but if you wish to install an IEEE floating-point 1           library, simply type "y" at this point.   R           * Do you want to install an IEEE floating point Predefined Library [NO]?  %     2.1.7 Read Informational Messages   >           At this point, the installation procedure displays a=           number of informational messages that report on the <           progress of the installation. There are no further           questions.  A           If the installation procedure has been successful up to B           this point, VMSINSTAL moves the new or modified files toC           their target directories, updates help files, and updatesa"           DCL tables if necessary.  /           The following messages are displayed:              2-6 Installing DEC Ada m         D                                                   Installing DEC Ada    1               There will be no further questions.s  @           %VMSINSTAL-I-RESTORE, Restoring product save set B ...  O               After the installation is complete, you need to add the followingaG               command to the site-specific system startup command file,c,               SYS$MANAGER:SYSTARTUP_VMS.COM:  %            $ @SYS$STARTUP:ADA$STARTUP_  @           %VMSINSTAL-I-RESTORE, Restoring product save set C ...  =           The success of the installation is indicated by the1           following message:  I           %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target_L                                                               directories...  D           If the installation procedure is successful, the procedure>           moves the files created to their target directories.  C           At this point, an informational message notifies you whenZA           the new files are moved to their target directories. Ifc?           you are installing DEC Ada on a system that has closec?           to the minimum amount of free disk space, the createduA           files are moved to their target directories as they areg?           processed and no message is issued when the files arem           moved.  <           For information on the files that the installation8           procedure creates or modifies, see Appendix B.  9     2.1.8 Observe the Installation Verification Procedure   @           If you chose to run the IVP, VMSINSTAL runs it at this<           point. When the IVP runs successfully, you see the           following display:  F           Beginning the (DEC Ada) installation verification procedure.  P           %ACS-I-CL_LIBCRE, Library CDD$DJA0:[SYS0.SYSUPD.ADA035.ADALIB] created5           %ACS-I-CL_LIBIS, Current program library iso:                       CDD$DJA0:[SYS0.SYSUPD.ADA035.ADALIB]4           DEC Ada 3.n installation verification testN           Testing, testing,           1,           2,           3,           4           Testing, testing6           DEC Ada 3.n installation verification PASSED  D                                               Installing DEC Ada 2-7 e  n           Installing DEC Ada    A           After the IVP has completed successfully, the temporary D           program library and any files generated during the IVP are           deleted.  (     2.1.9 End the Installation Procedure  C           The following messages indicate that the entire installa-h%           tion procedure is complete.   ;              Installation of DEC Ada 3.5 completed at hh:mmp  .              VMSINSTAL procedure done at hh:mm  8           You can now log out of the privileged account:             $ LOGOUT <Return> :           SYSTEM     logged out at dd-mmm-yyyy hh:mm:ss.ss  B           When the product installation procedure is complete, you?           can choose to install more products or to log out (as @           shown here.) If you removed any media from the console=           drive before beginning the installation, you shouldd           replace it now.   =           VMSINSTAL deletes or changes entries in the processED           symbol tables during the installation. If you are going toB           continue using the system manager's account and you wantA           to restore these symbols, you should log out and log in            again.       2.2 Error Recovery  @           If errors occur during the installation itself or whenC           the Installation Verification Procedure (IVP) is running, B           VMSINSTAL displays failure messages. If the installation/           fails, you see the following message:   K           %VMSINSTAL-E-INSFAIL, The installation of DEC Ada 3.n has failed.   ;           If the IVP fails, you see the following messages:   E           The DEC Ada 3.n Installation Verification Procedure failed.   C           %VMSINSTAL-E-IVPFAIL, The IVP for DEC Ada 3.n has failed.   @           Errors can occur during the installation if any of the%           following conditions exist:d  7           o  The operating system version is incorrect.        2-8 Installing DEC Ada           D                                                   Installing DEC Ada    :           o  A prerequisite software version is incorrect.  =           o  Quotas necessary for successful installation arei              insufficient.  D           o  System parameter values for successful installation are              insufficient.  :           o  The OpenVMS Help library is currently in use.  D           o  The product license has not been registered and loaded.  C           For descriptions of the error messages generated by thesea=           conditions, see the OpenVMS documentation on system =           messages, recovery procedures, and OpenVMS software =           installation. If you are notified that any of these ;           conditions exist, you should take the appropriated@           action as described in the message. For information on3           installation requirements, see Chapter 1.   9     2.3 Keeping the Currently Existing Compiler Available   >           The installation procedure installs the compiler andD           program library manager on the kit as the default compilerC           and program library manager. When you enter an ADA or ACS C           command, the newly installed compiler and program library A           manager are invoked. The DEC Ada kit is designed to let ?           you have continued access to your previously existing D           compiler while you are using the newly installed compiler.  ?           During the installation, you are asked if you want toV=           save the currently existing compiler. If you answer @           Yes and the version of the currently existing compiler=           is not the same as the version of the compiler thatU@           you are installing, the installation procedure creates;           a subdirectory of SYS$SYSTEM. The subdirectory is ?           named ADA$ident_string.DIR, where ident_string is theAD           identifying string of the currently existing compiler. TheC           installation procedure then copies the currently existingD?           versions of the following files to that subdirectory:              o  Compiler (ADA.EXE)e  .           o  Program library manager (ACS.EXE)  1           o  Command definition file (ADACLD.CLD)b  *           o  Run-time library (ADARTL.EXE)  D                                               Installing DEC Ada 2-9 e  c           Installing DEC Ada    &           o  Message file (ADAMSG.EXE)  5           o  Library of predefined units (ADALIB.DIR)   <           In addition, the installation procedure places the5           following command procedures in SYS$SYSTEM:n  %           o  ADA$USE_ident_string.COM   "           o  ADA$USE_INSTALLED.COM  <           When invoked, ADA$USE_ident_string.COM defines theC           appropriate logical names needed to access the previously >           existing compiler. ADA$USE_INSTALLED.COM defines the;           appropriate logical names to access the installedo           compiler.m  @           For example, if you install Version 3.5 as the defaultC           compiler and you want to access the Version 3.4 compiler,y*           you enter the following command:  (           $ @SYS$SYSTEM:ADA$USE_V3_4.COM  =           Subsequently, when you enter an ADA or ACS command, @           the Version 3.4 compiler or program library manager is           invoked.  @           If you want the old version of the DEC Ada compiler to?           be the default, modify SYS$STARTUP:ADA$STARTUP.COM byoA           replacing the current logical definitions with the onesuD           from SYS$SYSTEM:ADA$USE_ident_string.COM, where the ident_@           string represents the old version of the compiler. UseC           the /SYSTEM and /EXECUTIVE qualifiers in the logical name            definitions.  =           When you are using a version of the program library ?           manager (ACS.EXE) that is not the default version and ?           an ACS command creates a command procedure to performhA           an operation, unexpected results from using a differentt>           version of DEC Ada may occur in the following cases:  C           o  If the command procedure is submitted to a batch queuep6              by a /SUBMIT qualifier on the ACS command  A           o  If you later submit the command procedure to a batche/              queue using the DCL SUBMIT commands       2-10 Installing DEC Aday m  s      D                                                   Installing DEC Ada    ?           Because the program library manager does not transmit B           knowledge about the current version of the compiler whenA           the command procedure is created, the submitted commandn@           procedure (by default) uses the default version of theC           compiler. For example, if you invoke @SYS$SYSTEM:ADA$USE_mB           INSTALLED.COM and then use an ACS command that creates aA           command procedure for batch submission, the Version 3.4aC           compiler will be used during the execution of the commandm           procedure.  A           To override this default, modify your LOGIN.COM file sofB           that it invokes the command procedure that redefines the+           desired compiler and environment.w  ?           If you expect to switch frequently between compilers, ?           you may want to modify SYS$STARTUP:ADA$STARTUP.COM ortB           SYS$STARTUP:SYLOGIN.COM to define global OpenVMS symbolsD           to represent the invocations of the command procedure. For           example:  1           $ V34 == "@SYS$SYSTEM:ADA$USE_V3_4.COM"t6           $ V35 == "@SYS$SYSTEM:ADA$USE_INSTALLED.COM"  B           Program libraries generated or modified by a Version 3.57           compiler are not accepted by older compilers.i  ;           During the installation, the system command table1?           (SYS$LIBRARY:DCLTABLES.EXE) is updated to include thew=           new command files associated with the version being A           installed. Because the changes in the command files aretA           upward compatible, Version 3.n commands are accepted by ?           previous versions of the compiler and program library C           manager. If you use a new Version 3.n qualifier or option C           with a previous version of the compiler, the qualifier orw           option is ignored.  >           If this is not acceptable, remember that the command@           definition file (ADACLD.CLD) associated with the savedC           compiler is also in the subdirectory that holds the savede>           compiler. You can use the DCL SET COMMAND command to@           modify your process's command tables so that the saved>           compiler's command file is used. For example, if the>           system command table contains the command definitionA           associated with Version 3.4 but you have redefined yourn?           environment so that the Version 3.5 compiler is beinge  D                                              Installing DEC Ada 2-11 n              Installing DEC Ada    >           used, you can enter the following command to use the2           Version 3.5 compiler command definition:  >           $ SET COMMAND SYS$COMMON:[SYSEXE.ADA$V3_4]ADACLD.CLD  @           This technique works only as long as you remain in the?           current process context. When a spawned subprocess isd?           created, the process's current command tables are not.=           copied from the parent process. Instead, the system =           command table that contains the installed version'sS@           command files is used. A spawned subprocess is created;           when you enter, for example, one of the following            commands:              o  DCL SPAWN             o  LSEDIT COMPILEs             o  ACS COMPILE             o  ACS COMPILE/WAITr             o  ACS RECOMPILE             o  ACS RECOMPILE/WAITt             o  ACS LOADt  "           o  ACS LOAD/WAIT command  C           To reinstall an older version of the compiler, you should =           perform the installation using the original kit andPB           VMSINSTAL, even if the older version of the compiler has?           been saved in a subdirectory. Unexpected problems mayDD           occur if the files saved in the subdirectory are copied or,           renamed to the appropriate places.  1     2.3.1 Saving the Currently Existing Help File   >           If you chose to keep the currently existing compilerA           available (in Section 2.1.6), you may also want to savehD           the currently existing Help file. The DEC Ada installation=           procedure does not automatically save the currently A           existing Help file. To save the currently existing HelptA           file, you need to extract the file from the system Help @           library (SYS$LIBRARY:HELPLIB.HLB) and insert it into aC           newly created user Help library before installing the newr!           Help file. For example:        2-12 Installing DEC Adap n         D                                                   Installing DEC Ada    D           $ LIBRARY/EXTRACT/ADA/OUTPUT=USER:[SMITH]V3_nADAHELP.HLP -!           _$ SYS$HELP:HELPLIB.HLBc=           $ LIBRARY/CREATE/HELP USER:[SMITH]V3_nADAHELP.HLB -f(           _$ USER:[SMITH]V3_nADAHELP.HLP  D           Once you have saved the existing Help file, you can accessB           it by using the /LIBRARY qualifier with the Help command=           and specifying the user Help library instead of thez.           default system library. For example:  4           $ HELP/LIBRARY=USER:[SMITH]V3_nADAHELP.HLB  :     2.3.2 Saving the Currently Existing Examples Directory  >           If you chose to keep the currently existing compilerA           available (in Section 2.1.6), you may also want to saven?           the currently existing examples directory. To save an B           existing examples directory, you must copy it to another@           location before installing the new version of DEC Ada.  *     2.4 Installing DEC Ada on a VMScluster  ;           If you want to run DEC Ada on multiple nodes of a :           VMScluster, first check to see that you have the?           appropriate software license. Then follow these stepsn#           after installing DEC Ada:r  C           1. Enter the LICENSE LOAD command to activate the licensepB              on each node in the VMScluster on which DEC Ada is toB              be run as described in the OpenVMS License Management              Utility Manual.  :           2. If the other nodes share a common system disk;              with the installation node, install DEC Ada onf=              the other nodes by running the command procedurelD              SYS$STARTUP:ADA$STARTUP.COM on each node of the clusterB              that has a software license. You must also update the@              SYS$LIBRARY:DCLTABLES.EXE file on each of the otherD              nodes by entgering the following commands on each node:                $ INSTALL7              INSTALL> REPLACE SYS$LIBRARY:DCLTABLES.EXE   @              These commands modify the DCL command tables on the=              other nodes so that the ADA and ACS commands aree&              recognized and processed.  D                                              Installing DEC Ada 2-13 t  e           Installing DEC Ada    A           3. If the other nodes do not share a common system disk @              with the installation node, you must run a separate'              installation on each node.o         2.5 Postinstallation Notes  @           DEC Ada is now installed, and the DEC Ada compiler canC           be invoked by all users with the ADA command. The DEC AdaeC           program library manager can be invoked with ACS commands.h  =           The installation procedure modifies the DCL commanda?           table so that the ADA and ACS commands are recognizedt?           and processed. However, the previous command table isaB           still in effect for those users who are currently loggedD           in. Users who want to use the ADA or ACS commands must log-           out of the system and log in again.   L           Be sure to add the following command to the SYS$MANAGER:SYSTARTUP_6           VMS.COM file, as requested in Section 2.1.7:  "           @SYS$STARTUP:ADA$STARTUP  ;           To ensure device independence when backing up andi:           restoring DEC Ada program libraries, verify that>           concealed-device logical names have been assigned to?           all public devices on your system. For information onU=           concealed device logical names, see the OpenVMS DCLd@           Dictionary and the Guide to OpenVMS File Applications.  A           For information on using concealed device logical namesT<           with DEC Ada program libraries, see Developing Ada&           Programs on OpenVMS Systems.                             2-14 Installing DEC Adai a  t                  D                                                                    3D     ________________________________________________________________  C                                            After Installing DEC Ada       D           This chapter discusses the following tasks, which can take)           place after installing DEC Ada:f  <           o  Running the Installation Verification Procedure              separatelye  (           o  Diagnosing error conditions  +           o  Installing maintenance updates   /           o  Determining and reporting problemsn  B     3.1 Running the Installation Verification Procedure Separately  B           The Installation Verification Procedure (IVP) is usuallyD           run at installation. If you want to run the IVP separatelyB           to ensure the integrity of installed files should system<           problems occur, enter following command procedure:  !           $ @SYS$TEST:ADA$IVP.COM        3.2 Error Conditions  >           If the DEC Ada installation procedure or DEC Ada IVPB           fails for any reason when you are running VMSINSTAL, the)           following message is displayed:   L           %VMSINSTAL-E-INSFAIL, The installation of DEC Ada V3.5 has failed.  C           An error during the installation can occur if one or more ,           of the following conditions exist:  3           o  Operating system version is incorrect.l  8           o  Prerequisite software version is incorrect.  =           o  Quotas necessary for successful installation are .              insufficient (see Section 1.4.2).  D                                        After Installing DEC Ada  3-1 n  o           After Installing DEC Ada    D           o  Process quotas required by VMSINSTAL are incorrect (see              Section 1.4.3).  :           o  The OpenVMS Help library is currently in use.  :           o  The product was registered incorrectly or not              registered.  C           For descriptions of the error messages generated by thesedB           conditions, see the OpenVMS System Messages and Recovery>           Procedures Reference Manual, your processor-specific?           installation guide, or the OpenVMS License Management            Utility Manual.   A           If you are notified that any of these conditions exist, D           you should take the appropriate action as described in theB           message. You may need to change a system parameter or to-           increase an authorized quota value.e  A           If the installation fails, you must restart the instal-mB           lation procedure from the beginning. If the installation?           fails due to an IVP failure and the product's License B           PAK has been registered and loaded, contact your DIGITAL           representative.        3.3 Installing Updates  <           DIGITAL may periodically issue updates of DEC Ada.A           Each update consists of an installation kit. You should B           install this kit as described in this document or in anyB           documentation that may accompany the maintenance update.  =           Each time an update is released, the version number >           changes. For example, if the current version is 3.4,@           the version number of the next update may be 3.5. EachC           update also includes new release notes. The release notes C           describe the changes that have been made to DEC Ada since            the previous release.i  A           The release notes for the updates are provided on line.rB           You should read the release notes when you first installA           DEC Ada. They are also accessible at any time after theu           product is installed.e  =           For information on reading the release notes at ther@           time that you install DEC Ada, follow the installation#           procedure through step 6.         3-2 After Installing DEC Ada s  s      C                                            After Installing DEC Adan    A           To locate the release notes after DEC Ada is installed, A           display or print the file SYS$HELP:ADA03n.RELEASE_NOTES 8           (where n is the number of the current update).  *     3.4 Determining and Reporting Problems  C           If you encounter a problem while using DEC Ada, report it1           to DIGITAL.h  D           You may call DIGITAL if your software contract or warranty6           agreement entitles you to telephone support.  D           Review the Software Product Description (SPD) and Warranty=           Addendum for an explanation of the warranty. If youn@           encounter a problem during the warranty period, reportA           the problem as indicated previously or follow alternateo<           instructions provided by DIGITAL for reporting SPD"           nonconformance problems.  ?           When you prepare to report a problem, please take thea           following steps:  A           1. Describe as accurately as possible the circumstances ?              and state of the system when the problem occurred. A              Include in the description the version number of DECoB              Ada being used. Demonstrate the problem with specific              examples.  ?           2. Reduce the problem to as small a size as possible.   ?           3. Remember to include listings of any command files, ,              relevant data files, and so on.  .           4. Provide a listing of the program.  B           5. If the program is longer than 50 lines, submit a copyC              of the program on machine-readable media (for example,(D              magnetic tape). If necessary, also submit a copy of theC              program library used to build the application. Use the B              OpenVMS Backup Utility to copy the program library to(              the machine-readable media.  C           6. Report only one problem per report. This facilitates a !              more rapid response.l  D                                        After Installing DEC Ada  3-3 Y  M           After Installing DEC Ada    0           7. Mail the problem report to DIGITAL.  C           Experience shows that many problem reports do not containrB           enough information to duplicate or identify the problem.=           Complete and concise information helps DIGITAL givep;           accurate and timely service to software problems.o                                                                                    3-4 After Installing DEC Ada c                     D                                                                    AD     ________________________________________________________________  D                                                  Sample Installation      A           This appendix contains a sample installation of DEC Adas>           on an OpenVMS Alpha system. This sample was run on aC           system that had no previous version of DEC Ada installed.i>           Depending on which layered products you have on yourA           system, you might see additional messages and questionsh-           when you perform your installation.h  C           The sample installation assumes that DECnet has been shutiD           down, that no users are logged in to your system, and that@           OPTIONS N is specified to print the release notes. TheC           Installation Verification Procedure (IVP) runs at the endh           of the installation.  ;           This is only a sample. Sometimes the installationA>           procedure is modified in maintenance updates of thisA           product. Because this installation guide is not usuallyBC           revised for maintenance updates, be sure to read the ReadtC           Before Installing or Using DEC Ada Version 3.5 on OpenVMSBD           Alpha Systems letter before you install this product. ThisB           letter notes any significant changes in the installation%           that vary from this sample.e  U                  @sys$update:vmsinstal ada035 BYRON$DKA500:[ADA_RELEASE.AVMS_V35.kit]   J                   OpenVMS AXP Software Product Installation Procedure V7.1  %           It is 19-MAR-1999 at 13:08.e  9           Enter a question mark (?) at any time for help.@            D                                              Sample Installation A-1 s              Sample Installation     N           %VMSINSTAL-W-NOTSYSTEM, You are not logged in to the SYSTEM account.H           %VMSINSTAL-W-ACTIVE, The following processes are still active:                  SERVER_0011                  WILLETT2           * Do you want to continue anyway [NO]? yH           * Are you satisfied with the backup of your system disk [YES]?  3           The following products will be processed:a               ADA V3.5  =                   Beginning installation of ADA V3.5 at 13:08f  @           %VMSINSTAL-I-RESTORE, Restoring product save set A ...U           %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.$  M               Digital Equipment Corporation 1992, 1999. All rights reserved.   K              Restricted Rights: Use, duplication, or disclosure by the U.S.aO              Government is subject to restrictions as set forth in subparagraphsO              (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FARh/              52.227-14 Alt. III, as applicable.h  J              This software is proprietary to and embodies the confidentialM              technology of Digital Equipment Corporation. Possession, use, or P              copying of this software and media is authorized only pursuant to aM              valid written license from Digital or an authorized sublicensor.s  D           * Do you want to run the IVP after the installation [YES]?T           * Do you want to include SCA analysis data for the predefined units [YES]?E           * Do you want to save the currently existing compiler [NO]?iR           * Do you want to install an IEEE floating point Predefined Library [NO]?  6               There will not be any further questions.  Q               Installation will take 15 minutes or less, depending on your system                configuration.  @           %VMSINSTAL-I-RESTORE, Restoring product save set B ...  O               After the installation is complete, you need to add the following G               command to the site-specific system startup command file,s,               SYS$MANAGER:SYSTARTUP_VMS.COM;  ,                   $ @SYS$STARTUP:ADA$STARTUP  @           %VMSINSTAL-I-RESTORE, Restoring product save set C ...X           %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...       A-2 Sample Installation  l         D                                                  Sample Installation    F             Beginning the DEC Ada installation verification procedure.  M               Digital Equipment Corporation 1992, 1999. All rights reserved.n  K              Restricted Rights: Use, duplication, or disclosure by the U.S..O              Government is subject to restrictions as set forth in subparagraphhO              (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FARI/              52.227-14 Alt. III, as applicable.   J              This software is proprietary to and embodies the confidentialM              technology of Digital Equipment Corporation. Possession, use, or P              copying of this software and media is authorized only pursuant to aM              valid written license from Digital or an authorized sublicensor.t  N             Please note that this installation verification procedure requiresO             that a valid license for DEC Ada has been installed on your system.c  T           %ACS-I-CL_LIBCRE, Library BYRON$DKA300:[SYS0.SYSUPD.ADA035.ADALIB] created5           %ACS-I-CL_LIBIS, Current program library ist:                   BYRON$DKA300:[SYS0.SYSUPD.ADA035.ADALIB]0           DEC Ada installation verification testN           Testing, testing,           1,           2,           3,           4           Testing, testing2           DEC Ada installation verification PASSEDT           %ACS-I-CL_LIBDEL, Library BYRON$DKA300:[SYS0.SYSUPD.ADA035.ADALIB] deleted  =                   Installation of ADA V3.5 completed at 13:16e  H               Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY  O               Creating installation data file: VMI$ROOT:[SYSUPD]ADA035.VMI_DATA   3                   VMSINSTAL procedure done at 13:17                         D                                              Sample Installation A-3                       D                                                                    BD     ________________________________________________________________  C                                   Files and Logical Names Installedh      B           The installation procedure installs a number of files onA           your system and defines some logical names. Section B.1 B           lists the files installed. Section B.2 lists the logical@           names that are added to the system logical name table.       B.1 File Names  <           The installation procedure creates or modifies the=           following files. However, they do not appear in ther            installation messages.  9              SYS$SYSTEM:ADA.EXE                     (new)   9              SYS$SYSTEM:ACS.EXE                     (new)n  9              SYS$STARTUP:ADA$STARTUP.COM            (new)c  >              SYS$LIBRARY:DCLTABLES.EXE              (modified)  9              SYS$SHARE:ADACLD.CLD                   (new)t  9              SYS$COMMON:[SYSLIB.ADALIB] and         (new)            contents  9              SYS$COMMON:[SYSLIB]ADA$SCA_            (new)A           PREDEFINED.ANA[1]e  9              SYS$COMMON:[SYSHLP.EXAMPLES.ADA] and   (new)C           contents  9              SYS$HELP:ADA03n_SPD                    (new)   9              SYS$HELP:ADA03n.RELEASE_NOTES_PS       (new)   9              SYS$HELP:ADA03n.RELEASE_NOTES          (new)n  9              SYS$TEST:ADA$IVP.COM                   (new)u  9              SYS$LIBRARY:ADARTL.EXE[2]              (new)A  D           [1]Optional.______________________________________________  B           [2]Not installed if the system already has a copy with a:           higher version number than provided by this kit.  D                               Files and Logical Names Installed  B-1    I      %     Files and Logical Names Installed       D           [2]Not$installedDifStheXsystem_already_has(aecopy_with_a__  :           higher version number than provided by this kit.  H           If you saved the currently existing compiler in Section 2.1.6,?           the installation procedure also creates the following            files:  9              SYS$COMMON:[SYSEXE.ADA$ident_          (new) !           string[1]] and contentsu  9              SYS$SYSTEM:ADA$USE_ident_string[1].COM (new)o  9              SYS$SYSTEM:ADA$USE_INSTALLED.COM       (new)nD           [1]ident_string_represents_the_version_number_of_the______  /           currently installed DEC Ada compiler.        B.2 Logical Names   A           Table B-1 lists the logical names that are entered intoeA           the system logical name table when you install DEC Ada. D           These names are stored in the product's startup file. They@           are automatically entered into the system logical nameD           table whenever the system reboots or whenever the software           is invoked.l  D           Table_B-1_DEC_Ada_Logical_Names_and_Locations_____________  D           Logical_Name__________Location____________________________  @           ADA$EXAMPLES          SYS$COMMON:[SYSHLP.EXAMPLES.ADA]  <           ADA$PREDEFINED        ADA$PREDEFINED_ROOT:[ADALIB]  =           ADA$PREDEFINED_ROOT   Defined as a concealed devicef?                                 logical name that is equivalenteD           ______________________to_SYS$COMMON:[SYSLIB]._____________            )     B-2 Files and Logical Names Installedn