                                   C                      DEC_Ada_______________________________________ '                      Installation Guide ,                      for OpenVMS VAX Systems  .                      Order Number: AA-EF85G-TE    "                      December 1998  H                      This guide contains instructions for installing DECF                      Ada Version 3.5 or higher on OpenVMS VAX systems.D                      It also explains how to read the online releaseB                      notes before or after installing the product.            D                      Revision/Update Information: This revised guideD                                                   supersedes the DECB                                                   Ada InstallationG                                                   Guide for OpenVMS VAX E                                                   Systems (Order No.: ?                                                   AA-EF85F-TE).   E                      Operating System & Version:  OpenVMS VAX Version E                                                   6.2 through Version 5                                                   7.2   E                      Software Version:            DEC Ada Version 3.5   2                      Digital Equipment Corporation+                      Maynard, Massachusetts                  E            __________________________________________________________             December 1998  A            Digital Equipment Corporation makes no representations B            that the use of its products in the manner described inC            this publication will not infringe on existing or future C            patent rights, nor do the descriptions contained in this C            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 authorizied only pursuant to@            a valid written license from DIGITAL or an authorized            sublicensor.   ;             Digital Equipment Corporation 1998. All Rights             Reserved.  <            The following are trademarks of Digital Equipment>            Corporation: Bookreader, DEC, DEC Ada, DEC Ada PDO,C            DECnet, DECwindows, DIGITAL, OpenVMS, VAX, VAX DOCUMENT, 9            OpenVMS Cluster, XD Ada, and the DIGITAL logo.   4            The following are third-party trademarks:  =            IEEE is a registered trademark of the Institute of /            Electronic and Electrical Engineers.   @            Intel is a registered trademark of Intel Corporation.  A            Motif, OSF, and OSF/1 are registered trademarks of the )            Open Software Foundation, Inc.   3            POSIX is a registered trademark of IEEE.   A            POSTSCRIPT is a registered trademark of Adobe Systems,             Inc.   >            UNIX is a registered trademark in the United StatesB            and other countries licensed exclusively through X/Open            Company Ltd.   >            VADS is a registered trademark of Rational Software            Corporation.   ;            X/Open is a trademark of X/Open Company Limited.   >            X Window System is a trademark of the Massachusetts#            Institute of Technology.   A            All other trademarks and registered trademarks are the 0            property of their respective holders.  5            This document is also available on CD-ROM.   E            This document was prepared using VAX DOCUMENT Version 2.1.                                C    ________________________________________________________________   C                                                            Contents     C    Preface..................................................    vii     (    1  Preparing for DEC Ada Installation  9          1.1   Required Operating System and Prerequisite C                Hardware and Software........................    1-2 C          1.2   License Registration.........................    1-2 C          1.3   OpenVMS Cluster Considerations...............    1-3 C          1.4   Installation Procedure Requirements..........    1-3 C          1.4.1     Privileges and Disk Space................    1-3 C          1.4.2     System Parameters........................    1-4 C          1.4.2.1     Checking UAF Parameters................    1-5 <          1.4.2.2     Calculating the Values for GBLPAGES andC                      GBLSECTIONS............................    1-5 :          1.4.2.3     Changing System Parameter Values withC                      AUTOGEN................................    1-6 C          1.4.3     Process Account Quotas...................    1-7 C          1.4.4     VMSINSTAL Requirements...................    1-8 C          1.4.5     Backing Up Your System Disk..............    1-8       2  Installing DEC Ada  C          2.1   The Installation Procedure...................    2-1 C          2.1.1     Invoke VMSINSTAL.........................    2-1 C          2.1.2     Confirm System Backup ...................    2-3 C          2.1.3     Mount the Media..........................    2-4 C          2.1.4     Select a Release Notes Option............    2-4 7          2.1.5     Choose the Installation Verification C                    Procedure Option.........................    2-5 C          2.1.6     Select Installation Options .............    2-6 C          2.1.7     Read Informational Messages..............    2-7     C                                                                 iii                  :            2.1.8     Observe the Installation VerificationE                      Procedure................................    2-8 E            2.1.9     End the Installation Procedure...........    2-8 E            2.2   Error Recovery ..............................    2-9 8            2.3   Keeping the Currently Existing CompilerE                  Available....................................    2-9 <            2.3.1     Saving the Currently Existing Help FileE                      .........................................   2-13 ;            2.3.2     Saving the Currently Existing Examples E                      Directory................................   2-13 E            2.4   Installing DEC Ada on an OpenVMS Cluster.....   2-14 E            2.5   Postinstallation Notes.......................   2-14            3  After Installing DEC Ada  6            3.1   Running the Installation VerificationE                  Procedure Separately.........................    3-1 E            3.2   Error Conditions.............................    3-1 E            3.3   Installing Updates...........................    3-2 E            3.4   Determining and Reporting Problems...........    3-3         A  Sample Installation   )      B  Files and Logical Names Installed   E            B.1   File Names...................................    B-1 E            B.2   Logical Names................................    B-2   "      C  Tuning OpenVMS VAX Systems  E            C.1   General Tuning of OpenVMS Systems............    C-1 E            C.2   Improving Product Performance................    C-1 E            C.2.1     ASTLM....................................    C-2 E            C.2.2     ENQLM....................................    C-3 E            C.2.3     FILLM....................................    C-4 E            C.2.4     PRCLM....................................    C-4 E            C.2.5     TQELM....................................    C-5 E            C.2.6     Virtual Memory Usage.....................    C-5 E            C.2.7     Batch Queue Parameters...................    C-8 E            C.2.8     WSMAX Parameter .........................    C-8 E            C.2.9     Channel Count Parameters.................    C-8 E            C.2.10    Program Library Networking Effects.......    C-9           iv                  H               C.3   Relevant File Quotas and Cache Sizes.........   C-10H               C.3.1     Caching Files............................   C-10H               C.3.2     Caching File Headers.....................   C-11H               C.3.3     Caching Directory Files..................   C-13H               C.4   Using DECram on OpenVMS Systems..............   C-13             Figures   >               1         Documentation Reading Path for RelatedH                         Documents................................    vii  >               2         Documentation Reading Path for DEC AdaH                         Documentation............................   viii           Tables  2               1-1       Disk Space Requirements atH                         Installation.............................    1-4  9               1-2       Minimum Required System Parameter H                         Values...................................    1-4  A               1-3       Process Account Quotas for the Installing H                         Account..................................    1-7  H               B-1       DEC Ada Logical Names and Locations......    B-2                                    H                                                                        v                           H         ________________________________________________________________  H                                                                  Preface      G               This guide explains how to install DEC Ada Version 3.5 or ,               higher on OpenVMS VAX systems.  H               Keep this guide with your distribution kit. You need it toE               install maintenance updates or to reinstall DEC Ada for                any other reason.            Intended Audience   H               This guide is intended for the system manager who installs               DEC Ada software.   "         Documentation Reading Path  >               Figures 1 and 2 show the relationship of the AdaB               documentation set to other documentation that may be               helpful.  G               Figure 1 Documentation Reading Path for Related Documents                               H                                                                      vii                 H            Figure 2 Documentation Reading Path for DEC Ada Documentation                                                                                        	      viii                           Document Structure  H               This guide contains the following chapters and appendixes:  F               o  Chapter 1 describes the operating system and hardwareB                  requirements for DEC Ada installation and relatedC                  procedures that you complete before installing DEC                   Ada.   F               o  Chapter 2 describes the step-by-step instructions for"                  the installation.  A               o  Chapter 3 describes postinstallation actions and                    considerations.  E               o  Appendix A contains the output from a sample DEC Ada                   installation.  B               o  Appendix B contains a list of files installed andA                  logicals defined as a result of the installation                   procedure.   G               o  Appendix C describes how to tune your system after you (                  have installed DEC Ada.  !         Getting Help from DIGITAL   G               If you have a customer support contract and have comments F               or questions about DEC Ada software, you can contact theE               DIGITAL Customer Support Center (CSC), preferably using E               electronic means such as DSNlink. In the United States, ;               customers can call the CSC at 1-800-354-9000.   I               In addition, DIGITAL now provides access to Web Information F               and Support (WIS), a new electronic delivery applicationG               that allows you to submit electronic service requests, to C               access databases, to download patch kits, to transfer @               files from DIGITAL, and to connect to global notesH               conferences via the World Wide Web. If you are an entitledF               service customer with access to the Web, you can now useE               your favorite browser to connect to electronic services :               through an easy-to-use, graphical interface.  G               If you are already a DIA user, you can gain access to WIS                by openingD               http://www.service.digital.com/wis. Click on the words?               "United States," and enter your DIA Access ID and   H                                                                       ix                 @            password. WIS and DIA use the same underlying accountD            and directory on the DIGITAL Customer Support Center host            system.  =            If you are not already registered for DIA, you can A            register for a WIS account by contacting your Customer :            Support Center or local DIGITAL representative.        Conventions  @            The name of the OpenVMS AXP operating system has beenE            changed to OpenVMS Alpha. Any references to OpenVMS AXP or :            AXP are synonymous with OpenVMS Alpha or Alpha.  @            References to OpenVMS refer to both OpenVMS Alpha andB            OpenVMS VAX. Specific references to either platform are            noted.   >            The name of the DEC OSF/1 operating system has been<            changed to the DIGITAL UNIX operating system. AnyC            references to DEC OSF/1 are synonymous with DIGITAL UNIX &            unless specified otherwise.  B            References to the ULTRIX operating system are to ULTRIX0            MIPS systems, not ULTRIX VAX systems.  A            The following conventions are also used in this guide:   E            __________________________________________________________ E            Convention__________Description___________________________   ?            $                   A dollar sign ($) represents the 9                                OpenVMS DCL system prompt.   B            Ctrl/x              A sequence such as Ctrl/x indicates>                                that you must hold down the keyD                                labeled Ctrl while you simultaneouslyE                                press another key or a pointing device &                                button.  B            <Return>            In examples, a key name enclosed inC                                brackets or a box indicates that you ;                                press a key on the keyboard.   @            boldface monospace  In interactive examples, boldfaceD            text                monospace text represents user input.        x               H               __________________________________________________________H               Convention__________Description___________________________  H               Monospace type      Monospace type indicates code examplesB                                   and interactive screen displays.D                                   This typeface is also used in textA                                   to indicate the exact name of a C                                   command, routine, partition, path ;                                   name, directory, or file.   C               file-spec . . .     A horizontal ellipsis following a G                                   parameter, option, or value in syntax H                                   descriptions indicates that additionalG                                   parameters, options, or values can be *                                   entered.  A                . . .              A horizontal ellipsis in an Ada F                                   example or figure indicates that notB                                   all of the statements are shown.  G               .                   A vertical ellipsis in an interactive F               .                   figure or example indicates that notG               .                   all of the commands and responses are (                                   shown.  B               italic text         Italic text emphasizes importantC                                   information, indicates variables, B                                   and refers to complete titles ofF                                   manuals. Italic text also representsE                                   information that can vary in system G                                   messages (for example, Internal error *                                   number.)  D               n                   A lowercase italic n indicates the:                                   generic use of a number.  D               Variable            This typeface is used in syntax to;                                   indicate variable values.   A               UPPERCASE TEXT      Uppercase indicates the name of @                                   a command, routine, parameter,@                                   procedure, utility, file, fileF                                   protection code, or the abbreviation9                                   for a system privilege.   A               boldface text       Boldface text indicates DEC Ada 1                                   reserved words.   H                                                                       xi               E            __________________________________________________________uE            Convention__________Description____________________________  B            type_name           Italicized words in syntax descrip-B                                tions indicate descriptive prefixesC                                that are intended to give additional B                                semantic information rather than toD                                define a separate syntactic category.  @            [expression]        Square brackets indicate that the9                                enclosed item is optional.   E            {, mechanism_name   Braces in DEC Ada syntax indicate thataE            }                   the enclosed item can be repeated zeron-                                or more times.I  ?            |                   A vertical bar in DEC Ada syntaxgA                                separates alternative items unless E                                it occurs immediately after an opening A                                brace, in which case it stands forDE            ____________________itself._______________________________e                                                        xii f  o                  H                                                                        1H         ________________________________________________________________  H                                       Preparing for DEC Ada Installation      F               This chapter discusses the preparations and requirementsF               necessary for installing DEC Ada on OpenVMS VAX systems.  C               The information in the installation guide pertains to D               DEC Ada Version 3.5 or higher for OpenVMS VAX systems.E               DIGITAL suggests that you upgrade your DEC Ada compilerpE               and compilation environment incrementally with each newrF               release, but there is no technical requirement to do so.H               It is required that you review carefully the release notesF               for each version because they capture important release-D               oriented information and advise you of changes between               versions.e  D               Your bill of materials (BOM) and indented bills reportB               (BIL) specify the number and contents of your media.B               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..  F                 ________________________Note  ________________________  ?                 DEC Ada provides online release notes. They are >                 contained in the kit with the compiler and itsB                 associated components. DIGITAL strongly recommendsA                 that you read the release notes before proceeding.C                 with the installation. For information on accessing.:                 the online release notes, see Section 2.1.  E                 _____________________________________________________.          H                                   Preparing for DEC Ada Installation 1-1                 @      1.1 Required Operating System and Prerequisite Hardware and          Software.  ?            DEC Ada Version 3.5 supports OpenVMS VAX Version 6.2r            through Version 7.2.   ?            For a complete list of the required operating system4A            components, current hardware requirements, and prereq-1B            uisite and optional software and their required versionE            numbers, see the Software Product Description (SPD), whichnB            is shipped on the DEC Ada kit in SYS$HELP:ADA03n_SPD.*.        1.2 License Registration1  A            If you are installing DEC Ada on a newly licensed node1@            or cluster, you must first register a License Product<            Authorization Key (License PAK) using the LicenseD            Management Facility (LMF). The License PAK can be shippedB            along with the kit if you ordered the license and mediaB            together. Otherwise, the PAK is shipped separately to a0            location based on your license order.  @            If you are installing an update of DEC Ada but lack aA            service contract, call your DIGITAL representative for 4            instructions on how to get a License PAK.  B            If you are installing prerequisite or optional softwareD            along with DEC Ada, review the PAK status and install theD            PAKs for any prerequisite or optional software before you            install DEC Ada..  E            You must register and load your license for DEC Ada beforepB            you start the installation. To register a license underA            OpenVMS, first log in to the system manager's account,iD            SYSTEM. You then have a choice of two ways to perform the            registration:  B            o  Invoke the SYS$UPDATE:VMSLICENSE.COM procedure. WhenD               it prompts you for information, respond with data from               your License PAK..  ?            o  At the DCL prompt ($), enter the LICENSE REGISTER.E               command with the appropriate qualifiers that correspond )               to License PAK information.   +      1-2 Preparing for DEC Ada Installation. .  .            D               If you plan to use DEC Ada on more than one node in anH               OpenVMS Cluster, you need to perform a license load on the?               other nodes after you complete this installation.   D               For complete information on using LMF, see the OpenVMS0               License Management Utility Manual.  *         1.3 OpenVMS Cluster Considerations  ?               If you are running DEC Ada on an OpenVMS Cluster, D               VMSINSTAL automatically installs new versions as known?               or shared images only on the machine on which theoC               installation is actually performed. You must manually.E               install new versions as known or shared images on other.B               machines using the OpenVMS Install utility or invokeF               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 VAX               systems.  '         1.4.1 Privileges and Disk Space2  E               To install DEC Ada, you must be logged in to an account9C               that has SETPRV or at least the following privileges:2                 o  CMKRNLo                 o  WORLD                 o  SYSPRV   F               VMSINSTAL turns off BYPASS privilege at the start of the               installation.   F               The installation checks the system disk for the space itG               requires to install DEC Ada. For a summary of the storage -               requirements, refer to the SPD.   H               To determine the number of free disk blocks on the currentH               system disk, enter the following command at the DCL prompt               ($):  )               $ SHOW DEVICE SYS$SYSDEVICE.  H                                   Preparing for DEC Ada Installation 1-3 f  D            B            Table 1-1 identifies the various installation scenarios9            and the corresponding disk space requirements.q    E            Table_1-1_Disk_Space_Requirements_at_Installation_________.  0                                  Blocks RequiredA                                  During           Blocks Required.E            Scenario______________Installation_____After_Installation_u  8            DEC Ada never         105,000          76,000            previously installed   8            DEC Ada Version        69,000          15,000            3.4 previously             installed, not             saving previousE            product___________________________________________________         1.4.2 System Parameters  ?            Installing DEC Ada requires certain system parameter @            settings. Table 1-2 lists the minimum required systemB            parameter values for the installation. Depending on theB            type of programs and applications running at your site,:            you might need higher values for some settings.  E            Table_1-2_Minimum_Required_System_Parameter_Values________   E            System_Parameter___________Minimum_Value__________________   7            GBLPAGES[1]                11000 + DCLTABLES   (            GBLSECTIONS[1]             10E            [1]The_values_listed_for_these_system_parameters_representl  >            the number of free global pages and global sectionsB            required for the installation, not the total number you6            need to run your system and other software.E            __________________________________________________________   ;            To use DEC Ada, each account or batch queue thatFC            invokes the DEC Ada compiler must have TMPMBX and NETMBX             privileges.  2            The following sections show you how to:  "            o  Check UAF parameters  +      1-4 Preparing for DEC Ada Installationi c  a            B               o  Calculate values for the GBLPAGES and GBLSECTIONS"                  system parameters  A               o  Change parameter values with the AUTOGEN command                   procedure  '         1.4.2.1 Checking UAF Parameters   G               Before you install DEC Ada, you should check whether youreH               account has sufficient quotas to perform the installation.H               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  G               After checking your quotas, enter the EXIT command at thei1               UAF> prompt to return to DCL level.   C         1.4.2.2 Calculating the Values for GBLPAGES and GBLSECTIONSr  G               To install and run DEC Ada, you must have sufficient freetC               global pages and global sections. You must first findtE               out how many free global pages and sections you have onsG               your system. Then use AUTOGEN if you need to increase thee9               GLBPAGES and GBLSECTIONS system parameters.s  A               For example, you can use the WRITE command with theaB               F$GETSYI lexical function to find the number of freeE               global pages and global sections. The following exampleSE               shows how to get this information at your terminal (the &               default for SYS$OUTPUT):  :               $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES")               15848 :               $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS")               24  D               If the values the system displays are greater than the@               values in Table 1-2, you do not need to change theC               settings. If the value of free global pages or global D               sections is less than the value in Table 1-2, you must4               increase the system parameter setting.  E               Section 1.4.2.3 describes the procedures for increasings)               these values using AUTOGEN.   H                                   Preparing for DEC Ada Installation 1-5                 :      1.4.2.3 Changing System Parameter Values with AUTOGEN  =            Use the AUTOGEN command procedure to change systemd?            parameters. AUTOGEN automatically adjusts values forsC            parameters that are associated with the values you resetaC            manually. To change system parameters with AUTOGEN, edit             the following file:  #            SYS$SYSTEM:MODPARAMS.DATn  B            To change a parameter value listed in this file, deleteE            the current value associated with that parameter and enterA            the new value.s  >            To add a new parameter, add a line to the file thatA            includes both the name of the parameter and its value.p            For example:e              WSMAX = 1024n  @            To modify incremental parameters such as GBLPAGES andB            GBLSECTS, use ADD_. The following example increases the'            global page setting by 2000:n              ADD_GBLPAGES = 2000  D            When you set the page file quota, be careful not to use aE            value that exceeds the amount of page file space available             on the system.f  D            After you make all your changes, exit from the editor andC            execute the AUTOGEN procedure to recalculate your systemeE            parameters. Enter the following command at the DCL prompt:   /            $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT   A            When you specify REBOOT, AUTOGEN performs an automatic A            system shutdown and then reboots the system. Any users ?            logged on to the system are immediately disconnected A            during the shutdown. The automatic reboot puts the new (            parameter values into effect.  C            The AUTOGEN command procedure automatically adjusts some ?            of the SYSGEN parameters based on the consumption of A            resources since the last reboot. If you do not want to C            take advantage of this automatic adjustment, include the <            NOFEEDBACK qualifier on the AUTOGEN command line.  +      1-6 Preparing for DEC Ada Installationn u               F               For more information about using AUTOGEN, see the systemH               management documentation for the OpenVMS operating system.  $         1.4.3 Process Account Quotas  E               The account you use to install DEC Ada must have suffi- E               cient quotas to enable you to perform the installation. F               Table 1-3 summarizes the minimum process quotas required@               for the installation account. Larger quotas may be?               required for other work done by this account. For A               more information about these process quotas and thei7               relationships among them, see Appendix C.   A               Table 1-3 Process Account Quotas for the Installing H               __________Account_________________________________________  H               Account_Quota_____Value___________________________________  $               ASTLM               24  $               BIOLM               18  $               BYTLM            18000  $               DIOLM               18  $               ENQLM              300  H               FILLM______________100____________________________________  D               User account quotas are stored in the file SYSUAF.DAT.A               Use the Authorize utility (AUTHORIZE) to verify and C               change user account quotas. First, set your directory 4               to SYS$SYSTEM and then, run AUTHORIZE:  &               $ SET DEFAULT SYS$SYSTEM               $ RUN AUTHORIZE                UAF>  H               At the UAF> prompt, enter the SHOW command with an account>               name to check a particular account. For example:                 UAF> SHOW SMITH   H               To change a quota, enter the MODIFY command. The followingG               example changes the FILLM quota for the SMITH account and *               then exits from the utility:  H                                   Preparing for DEC Ada Installation 1-7                 &            UAF> MODIFY SMITH /FILLM=50            UAF> EXIT  ?            After you exit from the utility, the system displaysi@            messages indicating whether or not changes were made.D            Once the changes have been made, you must log out and log6            in again for the new quotas to take effect.  @            For more information on modifying account quotas, seeA            the description of the Authorize utility in the system E            management documentation for the OpenVMS operating system.a  !      1.4.4 VMSINSTAL Requirements   >            When you invoke VMSINSTAL, it checks the following:  ?            o  Whether you are logged in to a privileged account   ;            o  Whether any users are logged in to the system_  ?            o  Whether you have adequate quotas for installation_  @            If problems are detected during installation, in someA            instances you can enter Yes to continue. If you do notiA            wish to continue, enter No or press Return to stop the E            installation process. Then correct the problem and restarta            the installation.  &      1.4.5 Backing Up Your System Disk  B            At the beginning of the installation, VMSINSTAL asks ifB            you have backed up your system disk. DIGITAL recommendsA            that you do a system disk backup before installing anye            software.  >            Use the backup procedures established at your site.>            For details on performing a system disk backup, seeB            the section on the OpenVMS Backup utility in the systemE            management documentation for the OpenVMS operating system.             +      1-8 Preparing for DEC Ada Installation                        H                                                                        2H         ________________________________________________________________  H                                                       Installing DEC Ada      E               This chapter explains how to install DEC Ada on OpenVMS_>               VAX systems. Section 2.1 contains a step-by-step8               description of the installation procedure.  &         2.1 The Installation Procedure  F               DEC Ada Version 3.5 (ADA035) contains three savesets (A,D               B, and C). The DEC Ada installation procedure consistsF               of a series of questions and informational messages. SeeC               Appendix A for the output from a sample installation.o  G               The procedure takes approximately 15 minutes to complete.l  D               To abort the installation procedure at any time, pressG               Ctrl/Y. When you press Ctrl/Y, the installation proceduretH               deletes all files that it has created up to that point and?               exits. You can then start the installation again.   D               When the system prompts you with a question during theH               installation procedure, the default answer is often listed                in brackets ([ ]).           2.1.1 Invoke VMSINSTAL  E               To start the installation, invoke the VMSINSTAL commandrE               procedure from a privileged account, such as the SYSTEMi8               account. The command format is as follows:  B               @SYS$UPDATE:VMSINSTAL saveset-name device:[pathname]         OPTIONS N   F               VMSINSTAL is in the SYS$UPDATE directory. To install DEC/               Ada, enter the following command:   >               $ @SYS$UPDATE:VMSINSTAL ADA03n DKA100: OPTIONS N  H                                                   Installing DEC Ada 2-1 i  t            >            The following defines the elements of the VMSINSTAL            command procedure:               saveset-name_D            The installation name for the component. For DEC Ada, use(            the installation name ADA03n.              nE            The letter n represents the maintenance update of DEC Ada.tD            See the label on the DEC Ada distribution kit or the billA            of materials for the maintenance update number of your E            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 theD            media. For example, DKA100: is the device name for a diskB            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 thed$            installation is complete.              OPTIONS NC            An optional parameter that indicates that you want to be D            asked to choose one of the four options for reviewing theD            release notes. (See Section 2.1.4). If you do not includeD            the OPTIONS N parameter, VMSINSTAL does not ask you about            the release notes.i  @            You should review the release notes before proceeding@            with the installation in case they contain additionalD            information about the installation. If you are restartingA            the installation and have already reviewed the releasee7            notes, you do not need to specify OPTIONS N.d  C            You can select several other options when you invoke the '            VMSINSTAL command procedure:   %            o  Option (A): Auto_answero  B               Initially, creates a file that contains your answersB               to VMSINSTAL questions and prompts. You can then useD               the option (and the answer file) to save time during aE               reinstallation (typically after upgrading your system).   &            o  Option (G): Get save set        2-2 Installing DEC Adao s  u            B                  Lets you store product save sets temporarily on a6                  magnetic tape or in a disk directory.  %               o  Option (L): File logp  G                  Logs all activity to the terminal during installation.i  E               See the material on software installation in the system G               management documentation for the OpenVMS operating system G               for detailed information on these options. If you specify D               more than one option, separate each option name with a/               comma (for example, OPTIONS A,N).e  D               The following example invokes VMSINSTAL to install DECH               Ada from disk drive DKA100: and shows the system response.E               This example uses the OPTIONS N release note parameter.n  >               $ @SYS$UPDATE:VMSINSTAL ADA03n DKA100: OPTIONS N  L                     OpenVMS VAX Software Product Installation Procedure Vm.n  )               It is dd-mmm-yyyy at hh:mm. =               Enter a question mark (?) at any time for help.h  H               If you do not supply either the product name or the device6               name, VMSINSTAL prompts you for options.  #         2.1.2 Confirm System Backupn  B               VMSINSTAL asks if you are satisfied with your system               backup.   L               * Are you satisfied with the backup of your system disk [YES]?  ?               You should always back up your system disk before C               performing an installation. If you are satisfied with F               the backup of your system disk, press Return. Otherwise,F               enter No to discontinue the installation. After you backD               up your system disk, you can restart the installation.            H                                                   Installing DEC Ada 2-3 o  h                  2.1.3 Mount the Media  @            You should now mount the first distribution volume onC            the device you specified when you invoked VMSINSTAL. ThefB            device name appears in the line preceding the question.D            VMSINSTAL then asks you if you are ready to continue with            the installation.  =            If you respond Yes to indicate that you are ready,tA            VMSINSTAL displays a message that the media containinghD            DEC Ada has been mounted on the specified device and that&            the installation has begun.  @            If you entered the wrong device name when you invokedC            VMSINSTAL and need to restart the installation, enter No E            in response to the "Are you ready?" question. To abort the_8            installation for other reasons, press Ctrl/Y.  ?            Please mount the first volume of the set on DKA100:.n            * Are you ready? YESrD            %MOUNT-I-MOUNTED, DEC Ada MOUNTED ON _$$DKA100:  (NODE 1)4            The following products will be processed:               DEC Ada Version 3.5  E                Beginning installation of DEC Ada Version 3.n at 20:01   (      2.1.4 Select a Release Notes Option  A            If you specified OPTIONS N when you invoked VMSINSTAL,iB            you are now asked to choose one of the four options for'            reviewing the release notes.n  N            Release notes included with this kit are always copied to SYS$HELP.  ,            Additional Release Notes Options:  %             1.  Display release notes #             2.  Print release notes_             3.  Both 1 and 2!             4.  None of the above               * Select option [2]:   A            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.        2-4 Installing DEC Ada  b  y            C               If you select option 2, VMSINSTAL prompts you for the_G               name of the print queue that you want to use to print the                release notes:  '               * Queue name [SYS$PRINT]:m  B               You can press Return to send the file to the defaultF               output print device or you can enter another queue name.  D               If you select option 3, VMSINSTAL displays the releaseH               notes immediately on the console terminal and then prompts;               you for a queue name for the printed version.   F               Select option 4 if you have already reviewed the release8               notes and are continuing the installation.  =               Next VMSINSTAL displays the following question:   B               * Do you want to continue the installation [N]?: YESJ               %VMSINSTAL-I-RELMOVED, The product's release notes have beenC                                                  moved to SYS$HELP.   G               To continue the installation, enter Yes. Otherwise, press E               Return if you want to stop the installation to read the B               release notes. In either case, the release notes are9               copied to a file in the SYS$HELP directory:   +               SYS$HELP:ADA03n.RELEASE_NOTESv  H               The release notes are also available in POSTSCRIPT format.@               The file name is SYS$HELP:ADA03n.RELEASE_NOTES_PS.  C         2.1.5 Choose the Installation Verification Procedure Optionn  H               The installation procedure now asks if you want to run the8               Installation Verification Procedure (IVP).  H               * Do you want to run the IVP after the installation [YES]?  D               The IVP for DEC Ada checks to be sure that the instal-F               lation is successful. It is recommended that you run the               IVP.  D               After installing DEC Ada, you can run the IVP indepen-E               dently to verify that the software is available on yourPB               system. You might need to run the IVP after a systemA               failure to make sure that users can access DEC Ada.a  ;               For more information on IVP, see Section 3.1.   H                                                   Installing DEC Ada 2-5 i  e            &      2.1.6 Select Installation Options  D            DEC Ada provides support for the DEC Source Code AnalyzerA            (SCA). SCA is an optional, interactive, multilanguage,aD            source code cross-reference and static analysis tool. TheB            information in the SCA library for the predefined unitsC            allows you to query SCA about symbols, declarations, andc9            subprograms contained in the predefined units.A  A            If you have SCA installed on your system and intend toaC            use it to analyze DEC Ada programs, type Yes in responsenD            to the prompt. If you are not going to use SCA or you areD            concerned about saving disk space, type No in response to            the prompt.  M            * Do you want to include SCA analysis data file for the predefinedn!              units [YES]?<Return>s  D            If you need to know how much disk space this library willA            take before you can answer the prompt, type a question A            mark (?)  to obtain specific information on disk spaceo0            requirements before typing Yes or No.  C            If you typed Yes or pressed Return, an SCA analysis data I            file for the DEC Ada predefined units (ADA$SCA_PREDEFINED.ANA) @            is copied to the SYS$LIBRARY directory during instal-?            lation. To make this information available, you musti@            create an SCA library and load the data from the fileC            into the library. Previously, a complete SCA library forG.            the predefined units was installed.  >            If the current version of DEC Ada on your system is=            different from the version you are installing, the B            installation procedure allows you to save the currently>            existing version. If you want to save the currentlyB            existing compiler, answer Yes. If not, answer No to the            prompt.  G            * Do you want to save the currently existing compiler [YES]?f  D            For more information about keeping the currently existing/            compiler available, see Section 2.3.n  B            If you need to know exactly which files are saved, thenC            type a question mark (?)  to obtain specific informationt#            before typing Yes or No.B        2-6 Installing DEC Adam d  n            )         2.1.7 Read Informational Messages   B               At this point, the installation procedure displays aA               number of informational messages that report on thee@               progress of the installation. There are no further               questions.  E               If the installation procedure has been successful up totF               this point, VMSINSTAL moves the new or modified files toG               their target directories, updates help files, and updatesa&               DCL tables if necessary.  G               If you chose to have files purged, that work is done now. 3               The following messages are displayed:   :                   There will not be any further questions.  D               %VMSINSTAL-I-RESTORE, Restoring product save set B ...  S                   After the installation is complete, you need to add the followingoK                   command to the site-specific system startup command file, 0                   SYS$MANAGER:SYSTARTUP_VMS.COM:)                $ @SYS$STARTUP:ADA$STARTUP0  H               %VMSINSTAL-I-SYSDIR, This product creates system directoryM                                                        [SYSHLP.EXAMPLES.ADA]._D               %VMSINSTAL-I-RESTORE, Restoring product save set C ...D               %ACS-I-CL_VFYOK, VMI$ROOT:[SYSLIB.ADALIB$NEW] verified  A               The success of the installation is indicated by ther                following message:  M               %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target P                                                                   directories...  H               If the installation procedure is successful, the procedureB               moves the files created to their target directories.  G               At this point, an informational message notifies you whenxE               the new files are moved to their target directories. If C               you are installing DEC Ada on a system that has closepC               to the minimum amount of free disk space, the createdFE               files are moved to their target directories as they areeC               processed and no message is issued when the files area               moved.  H                                                   Installing DEC Ada 2-7 a  l            =            For information on the files that the installationr9            procedure creates or modifies, see Appendix B.   :      2.1.8 Observe the Installation Verification Procedure  A            If you chose to run the IVP, VMSINSTAL runs it at this =            point. When the IVP runs successfully, you see theo            following display:l  U            %ACS-I-CL_LIBCRE, Library XDFRZ$DKB100:[SYS0.SYSUPD.ADA03n.ADALIB] createdo6            %ACS-I-CL_LIBIS, Current program library is;                    XDFRZ$DKB100:[SYS0.SYSUPD.ADA03n.ADALIB] 6            DEC Ada V3.n installation verification testO            Testing, testing,           1,           2,           3,           4             Testing, testingt8            DEC Ada V3.n installation verification PASSEDU            %ACS-I-CL_LIBDEL, Library XDFRZ$DKB100:[SYS0.SYSUPD.ADA03n.ADALIB] deleted1>                    Installation of ADA V3.n completed at 11:18  B            After the IVP has completed successfully, the temporaryE            program library and any files generated during the IVP arei            deleted.a  )      2.1.9 End the Installation Procedure   D            The following messages indicate that the entire installa-&            tion procedure is complete.  <               Installation of DEC Ada 3.n completed at hh:mm  /               VMSINSTAL procedure done at hh:mmh  9            You can now log out of the privileged account:f              $ LOGOUT <Return>;            SYSTEM     logged out at dd-mmm-yyyy hh:mm:ss.ss   C            When the product installation procedure is complete, you_@            can choose to install more products or to log out (asA            shown here.) If you removed any media from the consoles>            drive before beginning the installation, you should            replace it now.  >            VMSINSTAL deletes or changes entries in the processE            symbol tables during the installation. If you are going to C            continue using the system manager's account and you want B            to restore these symbols, you should log out and log in            again.         2-8 Installing DEC Adam a  .                     2.2 Error Recovery  D               If errors occur during the installation itself or whenG               the Installation Verification Procedure (IVP) is running,aF               VMSINSTAL displays failure messages. If the installation3               fails, you see the following message:   O               %VMSINSTAL-E-INSFAIL, The installation of DEC Ada 3.n has failed.u  ?               If the IVP fails, you see the following messages:s  I               The DEC Ada 3.n Installation Verification Procedure failed.e  G               %VMSINSTAL-E-IVPFAIL, The IVP for DEC Ada 3.n has failed.   D               Errors can occur during the installation if any of the)               following conditions exist:   ;               o  The operating system version is incorrect.   >               o  A prerequisite software version is incorrect.  A               o  Quotas necessary for successful installation are                   insufficient.  H               o  System parameter values for successful installation are                  insufficient.  >               o  The OpenVMS Help library is currently in use.  H               o  The product license has not been registered and loaded.  G               For descriptions of the error messages generated by theseTA               conditions, see the OpenVMS documentation on system A               messages, recovery procedures, and OpenVMS software A               installation. If you are notified that any of theseT?               conditions exist, you should take the appropriate D               action as described in the message. For information on7               installation requirements, see Chapter 1.u  =         2.3 Keeping the Currently Existing Compiler Availablet  B               The installation procedure installs the compiler andH               program library manager on the kit as the default compilerG               and program library manager. When you enter an ADA or ACSoG               command, the newly installed compiler and program library E               manager are invoked. The DEC Ada kit is designed to letrC               you have continued access to your previously existingOH               compiler while you are using the newly installed compiler.  H                                                   Installing DEC Ada 2-9                 @            During the installation, you are asked if you want to>            save the currently existing compiler. If you answerA            Yes and the version of the currently existing compilert>            is not the same as the version of the compiler thatA            you are installing, the installation procedure createso<            a subdirectory of SYS$SYSTEM. The subdirectory is@            named ADA$ident_string.DIR, where ident_string is theE            identifying string of the currently existing compiler. ThenD            installation procedure then copies the currently existing@            versions of the following files to that subdirectory:               o  Compiler (ADA.EXE)  /            o  Program library manager (ACS.EXE)p  2            o  Command definition file (ADACLD.CLD)  +            o  Run-time library (ADARTL.EXE)   '            o  Message file (ADAMSG.EXE)n  6            o  Library of predefined units (ADALIB.DIR)  =            In addition, the installation procedure places the 6            following command procedures in SYS$SYSTEM:  &            o  ADA$USE_ident_string.COM  #            o  ADA$USE_INSTALLED.COM   =            When invoked, ADA$USE_ident_string.COM defines thenD            appropriate logical names needed to access the previously?            existing compiler. ADA$USE_INSTALLED.COM defines thei<            appropriate logical names to access the installed            compiler.  A            For example, if you install Version 3.5 as the defaultaD            compiler and you want to access the Version 3.4 compiler,+            you enter the following command:   )            $ @SYS$SYSTEM:ADA$USE_V3_4.COM   >            Subsequently, when you enter an ADA or ACS command,A            the Version 3.4 compiler or program library manager is             invoked.S        2-10 Installing DEC Ada T  S            D               If you want the old version of the DEC Ada compiler toC               be the default, modify SYS$STARTUP:ADA$STARTUP.COM by E               replacing the current logical definitions with the ones H               from SYS$SYSTEM:ADA$USE_ident_string.COM, where the ident_D               string represents the old version of the compiler. UseG               the /SYSTEM and /EXECUTIVE qualifiers in the logical name                definitions.  A               When you are using a version of the program library C               manager (ACS.EXE) that is not the default version and C               an ACS command creates a command procedure to perform E               an operation, unexpected results from using a different B               version of DEC Ada may occur in the following cases:  G               o  If the command procedure is submitted to a batch queue :                  by a /SUBMIT qualifier on the ACS command  E               o  If you later submit the command procedure to a batch 3                  queue using the DCL SUBMIT commandv  C               Because the program library manager does not transmitLF               knowledge about the current version of the compiler whenE               the command procedure is created, the submitted commandhD               procedure (by default) uses the default version of theG               compiler. For example, if you invoke @SYS$SYSTEM:ADA$USE_tD               INSTALLED.COM and then use an ACS command that createsC               a command procedure for batch submission, the current G               Version 3.n compiler will be used during the execution ofS$               the command procedure.  E               To override this default, you can modify your LOGIN.COM.@               file so that it invokes the command procedure that=               redefines the desired compiler and environment.n  C               If you expect to switch frequently between compilers,EC               you may want to modify SYS$STARTUP:ADA$STARTUP.COM orpF               SYS$STARTUP:SYLOGIN.COM to define global OpenVMS symbolsH               to represent the invocations of the command procedure. For               example:  5               $ V34 == "@SYS$SYSTEM:ADA$USE_V3_4.COM"u:               $ V35 == "@SYS$SYSTEM:ADA$USE_INSTALLED.COM"  F               Program libraries generated or modified by a Version 3.5H               or higher compiler may not be accepted by older compilers.  H                                                  Installing DEC Ada 2-11    e            <            During the installation, the system command table@            (SYS$LIBRARY:DCLTABLES.EXE) is updated to include the>            new command files associated with the version beingB            installed. Because the changes in the command files areB            upward compatible, Version 3.n commands are accepted by@            previous versions of the compiler and program libraryD            manager. If you use a new Version 3.n qualifier or optionD            with a previous version of the compiler, the qualifier or            option is ignored.   B            If this is not acceptable, you can make use of the factC            that the command definition file (ADACLD.CLD) associatedtC            with the saved compiler is also in the subdirectory thatsD            holds the saved compiler. You can use the DCL SET COMMANDB            command to modify your process's command tables so thatE            the saved compiler's command file is used. For example, iftC            the system command table contains the command definitionnB            associated with Version 3.5 but you have redefined your@            environment so that the Version 3.4 compiler is being?            used, you can enter the following command to use theR3            Version 3.4 compiler command definition:   ?            $ SET COMMAND SYS$COMMON:[SYSEXE.ADA$V3_4]ADACLD.CLD   A            This technique works only as long as you remain in the @            current process context. When a spawned subprocess is@            created, the process's current command tables are not>            copied from the parent process. Instead, the system>            command table that contains the installed version'sA            command files is used. A spawned subprocess is created <            when you enter, for example, one of the following            commands:              o  DCL SPAWNa              o  LSEDIT COMPILE              o  ACS COMPILEe              o  ACS COMPILE/WAIT              o  ACS RECOMPILEV               o  ACS RECOMPILE/WAIT              o  ACS LOAD              o  ACS LOAD/WAITt        2-12 Installing DEC Ada                 G               To reinstall an older version of the compiler, you should A               perform the installation using the original kit andfF               VMSINSTAL, even if the older version of the compiler hasC               been saved in a subdirectory. Unexpected problems mayyH               occur if the files saved in the subdirectory are copied or0               renamed to the appropriate places.  5         2.3.1 Saving the Currently Existing Help File   B               If you chose to keep the currently existing compilerE               available (in Section 2.1.6), you may also want to save H               the currently existing Help file. The DEC Ada installationA               procedure does not automatically save the currently E               existing Help file. To save the currently existing Help E               file, you need to extract the file from the system HelpaD               library (SYS$LIBRARY:HELPLIB.HLB) and insert it into aG               newly created user Help library before installing the newS%               Help file. For example:t  H               $ LIBRARY/EXTRACT/ADA/OUTPUT=USER:[SMITH]V3_nADAHELP.HLP -%               _$ SYS$HELP:HELPLIB.HLBgA               $ LIBRARY/CREATE/HELP USER:[SMITH]V3_nADAHELP.HLB -s,               _$ USER:[SMITH]V3_nADAHELP.HLP  H               Once you have saved the existing Help file, you can accessF               it by using the /LIBRARY qualifier with the Help commandA               and specifying the user Help library instead of thee2               default system library. For example:  8               $ HELP/LIBRARY=USER:[SMITH]V3_nADAHELP.HLB  >         2.3.2 Saving the Currently Existing Examples Directory  B               If you chose to keep the currently existing compilerE               available (in Section 2.1.6), you may also want to save C               the currently existing examples directory. To save an F               existing examples directory, you must copy it to anotherD               location before installing the new version of DEC Ada.              H                                                  Installing DEC Ada 2-13 t  e            1      2.4 Installing DEC Ada on an OpenVMS Clustere  E            If you want to run DEC Ada on multiple nodes of an OpenVMS D            Cluster, first check to see that you have the appropriateE            software license. Then follow these steps after installingi            DEC Ada:r  D            1. Enter the LICENSE LOAD command to activate the licenseB               on each node in the OpenVMS Cluster on which DEC AdaC               is to be executed as described in the OpenVMS License (               Management Utility Manual.  ;            2. If the other nodes share a common system diskh<               with the installation node, install DEC Ada on>               the other nodes by running the command procedureE               SYS$STARTUP:ADA$STARTUP.COM on each node of the clusterMC               that has a software license. You must also update theiA               SYS$LIBRARY:DCLTABLES.EXE file on each of the othertE               nodes by executing the following commands on each node:h                 $ INSTALL.8               INSTALL> REPLACE SYS$LIBRARY:DCLTABLES.EXE  A               These commands modify the DCL command tables on ther>               other nodes so that the ADA and ACS commands are'               recognized and processed.   B            3. If the other nodes do not share a common system diskA               with the installation node, you must run a separateg(               installation on each node.        2.5 Postinstallation Notesn  A            DEC Ada is now installed, and the DEC Ada compiler canBD            be invoked by all users with the ADA command. The DEC AdaD            program library manager can be invoked with ACS commands.  >            The installation procedure modifies the DCL command@            table so that the ADA and ACS commands are recognized@            and processed. However, the previous command table isC            still in effect for those users who are currently loggedAE            in. Users who want to use the ADA or ACS commands must loge.            out of the system and log in again.          2-14 Installing DEC Ada                 P               Be sure to add the following command to the SYS$MANAGER:SYSTARTUP_:               VMS.COM file, as requested in Section 2.1.7:  &               @SYS$STARTUP:ADA$STARTUP  ?               To ensure device independence when backing up and >               restoring DEC Ada program libraries, verify thatB               concealed-device logical names have been assigned toC               all public devices on your system. For information oniA               concealed device logical names, see the OpenVMS DCL D               Dictionary and the Guide to OpenVMS File Applications.  E               For information on using concealed device logical names @               with DEC Ada program libraries, see Developing Ada*               Programs on OpenVMS Systems.                                                            H                                                  Installing DEC Ada 2-15 a  7                  H                                                                        3H         ________________________________________________________________  G                                                After Installing DEC Adat      H               This chapter discusses the following tasks, which can take-               place after installing DEC Ada:y  @               o  Running the Installation Verification Procedure                  separately   ,               o  Diagnosing error conditions  /               o  Installing maintenance updatesA  3               o  Determining and reporting problemsf  F         3.1 Running the Installation Verification Procedure Separately  F               The Installation Verification Procedure (IVP) is usuallyH               run at installation. If you want to run the IVP separatelyF               to ensure the integrity of installed files should systemF               problems occur, execute the following command procedure:  %               $ @SYS$TEST:ADA$IVP.COM            3.2 Error Conditions  B               If the DEC Ada installation procedure or DEC Ada IVPF               fails for any reason when you are running VMSINSTAL, the-               following message is displayed:t  P               %VMSINSTAL-E-INSFAIL, The installation of DEC Ada V3.n has failed.  G               An error during the installation can occur if one or moreu0               of the following conditions exist:  7               o  Operating system version is incorrect.t  <               o  Prerequisite software version is incorrect.  A               o  Quotas necessary for successful installation arel2                  insufficient (see Section 1.4.2).  H                                            After Installing DEC Ada  3-1 n               E            o  Process quotas required by VMSINSTAL are incorrect (seel               Section 1.4.3).p  ;            o  The OpenVMS Help library is currently in use.u  ;            o  The product was registered incorrectly or nota               registered.   D            For descriptions of the error messages generated by theseC            conditions, see the OpenVMS System Messages and Recovery ?            Procedures Reference Manual, your processor-specifics@            installation guide, or the OpenVMS License Management            Utility Manual.  B            If you are notified that any of these conditions exist,E            you should take the appropriate action as described in the C            message. You may need to change a system parameter or tod.            increase an authorized quota value.  B            If the installation fails, you must restart the instal-C            lation procedure from the beginning. If the installation @            fails due to an IVP failure and the product's LicenseC            PAK has been registered and loaded, contact your DIGITALo            representative.        3.3 Installing Updatese  =            DIGITAL may periodically issue updates of DEC Ada.vB            Each update consists of an installation kit. You shouldC            install this kit as described in this document or in any C            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.2,sA            the version number of the next update may be 3.3. EachoD            update also includes new release notes. The release notesD            describe the changes that have been made to DEC Ada since             the previous release.  B            The release notes for the updates are provided on line.C            You should read the release notes when you first install B            DEC Ada. They are also accessible at any time after the             product is installed.  >            For information on reading the release notes at theA            time that you install DEC Ada, follow the installationi$            procedure through step 6.  !      3-2 After Installing DEC Adaa h  e            E               To locate the release notes after DEC Ada is installed, E               display or print the file SYS$HELP:ADA03n.RELEASE_NOTESi<               (where n is the number of the current update).  .         3.4 Determining and Reporting Problems  G               If you encounter a problem while using DEC Ada, report itu               to DIGITAL.m  D               Depending on the nature of the problem and the type ofE               support you have, you can call DIGITAL if your software F               contract or warranty agreement entitles you to telephone               support.  H               Review the Software Product Description (SPD) and WarrantyG               Addendum for an explanation of warranty. If you encounteraF               a problem during the warranty period, report the problemF               as indicated previously or follow alternate instructionsB               provided by DIGITAL for reporting SPD nonconformance               problems.   C               When you prepare to report a problem, please take thei               following steps:  E               1. Describe as accurately as possible the circumstances C                  and state of the system when the problem occurred.oE                  Include in the description the version number of DECDF                  Ada being used. Demonstrate the problem with specific                  examples.  C               2. Reduce the problem to as small a size as possible.e  C               3. Remember to include listings of any command files, 0                  relevant data files, and so on.  2               4. Provide a listing of the program.  F               5. If the program is longer than 50 lines, submit a copyG                  of the program on machine-readable media (for example,TH                  magnetic tape). If necessary, also submit a copy of theG                  program library used to build the application. Use thelF                  OpenVMS Backup utility to copy the program library to,                  the machine-readable media.  G               6. Report only one problem per report. This facilitates a %                  more rapid response.   H                                            After Installing DEC Ada  3-3 m  g            1            7. Mail the problem report to DIGITAL.T  D            Experience shows that many problem reports do not containC            enough information to duplicate or identify the problem.S>            Complete and concise information helps DIGITAL give<            accurate and timely service to software problems.  @            Also see the Getting Help from DIGITAL section in the            Preface.e                                                                        !      3-4 After Installing DEC Adai i  .                  H                                                                        AH         ________________________________________________________________  H                                                      Sample Installation      A               This appendix contains a sample installation of DECaD               Ada on an OpenVMS VAX system. This sample was run on aG               system that had no previous version of DEC Ada installed.uB               Depending on which layered products you have on yourE               system, you might see additional messages and questionsS1               when you perform your installation.   G               The sample installation assumes that DECnet has been shutnH               down, that no users are logged in to your system, and thatD               OPTIONS N is specified to print the release notes. TheG               Installation Verification Procedure (IVP) runs at the end "               of the installation.  ?               This is only a sample. Sometimes the installation B               procedure is modified in maintenance updates of thisE               product. Because this installation guide is not usually G               revised for maintenance updates, be sure to read the ReadfG               Before Installing or Using DEC Ada Version 3.n on OpenVMSeF               VAX Systems letter before you install this product. ThisF               letter notes any significant changes in the installation)               that vary from this sample.   3               $  @sys$update:vmsinstal ada035 MTA0:   N                       OpenVMS VAX Software Product Installation Procedure V6.2  )               It is 20-OCT-1998 at 16:14.d  =               Enter a question mark (?) at any time for help.S  E               * Are you satisfied with the backup of your system diskT               [YES]? <Return>g  7               The following products will be processed:                    ADA V3.5  H                                                  Sample Installation A-1                 >                    Beginning installation of ADA V3.5 at 16:14  A            %VMSINSTAL-I-RESTORE, Restoring product save set A ...EV            %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.  H                Digital Equipment Corporation 1998. All rights reserved.  L               Restricted Rights: Use, duplication, or disclosure by the U.S.P               Government is subject to restrictions as set forth in subparagraphP               (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR0               52.227-14 Alt. III, as applicable.  K               This software is proprietary to and embodies the confidentialaN               technology of Digital Equipment Corporation. Possession, use, orQ               copying of this software and media is authorized only pursuant to aeN               valid written license from Digital or an authorized sublicensor.  N            * Do you want to run the IVP after the installation [YES]? <Return>H            * Do you want to include SCA analysis data for the predefined             units [YES]? <Return>I            * Do you want to save the currently existing compiler [YES]? Nn  7                There will not be any further questions.u  R                Installation will take 15 minutes or less, depending on your system                configuration.   A            %VMSINSTAL-I-RESTORE, Restoring product save set B ...   P                After the installation is complete, you need to add the followingH                command to the site-specific system startup command file,-                SYS$MANAGER:SYSTARTUP_VMS.COM;e  -                    $ @SYS$STARTUP:ADA$STARTUP   A            %VMSINSTAL-I-RESTORE, Restoring product save set C ... Y            %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...e  G              Beginning the DEC Ada installation verification procedure.W  N                Digital Equipment Corporation 1992, 1998. All rights reserved.  L               Restricted Rights: Use, duplication, or disclosure by the U.S.P               Government is subject to restrictions as set forth in subparagraphP               (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR0               52.227-14 Alt. III, as applicable.        A-2 Sample Installation i  n            N                  This software is proprietary to and embodies the confidentialQ                  technology of Digital Equipment Corporation. Possession, use, orlT                  copying of this software and media is authorized only pursuant to aQ                  valid written license from Digital or an authorized sublicensor.f  R                 Please note that this installation verification procedure requiresS                 that a valid license for DEC Ada has been installed on your system.                   .                  .                  .Q               %ACS-I-CL_LIBCRE, Library DISK$:[SYS0.SYSUPD.ADA035.ADALIB] createdr9               %ACS-I-CL_LIBIS, Current program library isc7                       DISK$:[SYS0.SYSUPD.ADA035.ADALIB]S4               DEC Ada installation verification testR               Testing, testing,           1,           2,           3,           4               Testing, testing6               DEC Ada installation verification PASSEDQ               %ACS-I-CL_LIBDEL, Library DISK$:[SYS0.SYSUPD.ADA035.ADALIB] deletedL  A                       Installation of ADA V3.5 completed at 16:21A  7                       VMSINSTAL procedure done at 16:21H                                              H                                                  Sample Installation A-3 i  t                  H                                                                        BH         ________________________________________________________________  G                                       Files and Logical Names Installedo      F               The installation procedure installs a number of files onE               your system and defines some logical names. Section B.1iF               lists the files installed. Section B.2 lists the logicalD               names that are added to the system logical name table.           B.1 File Names  @               The installation procedure creates or modifies theA               following files. However, they do not appear in then$               installation messages.  =                  SYS$SYSTEM:ADA.EXE                     (new)M  =                  SYS$SYSTEM:ACS.EXE                     (new)o  =                  SYS$STARTUP:ADA$STARTUP.COM            (new)r  B                  SYS$LIBRARY:DCLTABLES.EXE              (modified)  =                  SYS$SHARE:ADACLD.CLD                   (new)i  =                  SYS$COMMON:[SYSLIB.ADALIB] and         (new)e               contents  =                  SYS$COMMON:[SYSLIB]ADA$SCA_            (new)                PREDEFINED.ANA[1]a  =                  SYS$COMMON:[SYSHLP.EXAMPLES.ADA] and   (new)e               contents  =                  SYS$HELP:ADA03n_SPD                    (new)   =                  SYS$HELP:ADA03n.RELEASE_NOTES_PS       (new)M  =                  SYS$HELP:ADA03n.RELEASE_NOTES          (new)   =                  SYS$TEST:ADA$IVP.COM                   (new)   =                  SYS$LIBRARY:ADARTL.EXE[2]              (new)n  H               [1]Optional.______________________________________________  F               [2]Not installed if the system already has a copy with a>               higher version number than provided by this kit.  H                                   Files and Logical Names Installed  B-1 f  e              E            [2]Not$installedDifStheXsystem_already_has(aecopy_with_a__o  ;            higher version number than provided by this kit.h  I            If you saved the currently existing compiler in Section 2.1.6,l@            the installation procedure also creates the following            files:o  :               SYS$COMMON:[SYSEXE.ADA$ident_          (new)"            string[1]] and contents  :               SYS$SYSTEM:ADA$USE_ident_string[1].COM (new)  :               SYS$SYSTEM:ADA$USE_INSTALLED.COM       (new)E            [1]ident_string_represents_the_version_number_of_the______   0            currently installed DEC Ada compiler.        B.2 Logical Names  B            Table B-1 lists the logical names that are entered intoB            the system logical name table when you install DEC Ada.E            These names are stored in the product's startup file. TheydA            are automatically entered into the system logical nameeE            table whenever the system reboots or whenever the software             is invoked.  E            Table_B-1_DEC_Ada_Logical_Names_and_Locations_____________g  E            Logical_Name__________Location____________________________h  A            ADA$EXAMPLES          SYS$COMMON:[SYSHLP.EXAMPLES.ADA].  @            ADA$HTML              DEC Ada manuals in .HTML formatF                                  SYS$COMMON:[SYSHLP.EXAMPLES.ADA.HTML]  =            ADA$PREDEFINED        ADA$PREDEFINED_ROOT:[ADALIB]e  >            ADA$PREDEFINED_ROOT   Defined as a concealed device@                                  logical name that is equivalentE            ______________________to_SYS$COMMON:[SYSLIB.]_____________       *      B-2 Files and Logical Names Installed                       H                                                                        CH         ________________________________________________________________  H                                               Tuning OpenVMS VAX Systems      G               When configuring a system to handle DEC Ada compilations,sF               you need to consider all of the activities that you wishF               to perform. For example, you need to consider the amountD               of parallel compilation that the system can support as@               well as considering the amount of memory you need.  G               In general, a process used for compiling DEC Ada programsiH               should have a WSEXTENT quota of at least 8,000. If you areF               performing compilations interactively, this quota should-               be specified as a SYSUAF quota.   H               For compilations done in a batch queue, it is possible forF               the system manager to set the WSEXTENT attribute for theH               batch queue. In that case, the system should be configuredE               with enough memory to let the maximum desired number of E               concurrent compilations reach their maximum working set G               simultaneously. Otherwise, the system may start paging orh#               swapping excessively.i  -         C.1 General Tuning of OpenVMS Systemsa  C               An optional DIGITAL product, the Disk File Optimizer,nD               can be used to reorder fragmented files online withoutH               requiring any system downtime or affecting disk availabil-G               ity. This product can also migrate files to their optimal                places on a disk.2  )         C.2 Improving Product Performance   G               This section gives detailed information on how to improve A               the performance of the DEC Ada compiler and programtC               library manager. Every effort was made to provide thenE               appropriate parameters for tuning your system. However, F               you may gain better performance by adjusting some of theE               parameters upwards or downwards to suit your particulare#               system configuration.P  H                                           Tuning OpenVMS VAX Systems C-1 u  ,            C            Also in this section, System Generation utility (SYSGEN)o;            and user authorization file (UAF) parameters are A            described, and suggested minimum values are noted. The D            parameters discussed are those for which DEC Ada requiresC            larger values than the OpenVMS defaults or for which theaB            values are larger than those required for other OpenVMS!            programming languages.l  ?            The OpenVMS operating system controls resource usagec=            through two primary sets of parameters: systemwideuA            parameters and per-process parameters. You can use theeD            SYSGEN utility to define and modify systemwide parametersE            (SYSGEN parameters). Per-process parameters are controlled C            on a per-user-name basis by quotas and defaults that are E            contained in the user authorization file (UAF parameters). ?            You use the Authorize utility to modify UAF entries.   ?            A complete description of OpenVMS resources, SYSGEN, @            and UAF parameters is contained in the OpenVMS SystemC            Manager's Manual. You should be familiar with the proce- A            dures described there for modifying SYSGEN parameters.   <            The recommended procedure is to add site-specific>            parameters to the file SYS$SYSTEM:MODPARAMS.DAT andD            then invoke the SYS$UPDATE:AUTOGEN command procedure. TheC            AUTOGEN command procedure computes the optimal value foreB            all parameters. See the OpenVMS System Manager's ManualC            for information on how to use AUTOGEN and how to specify 4            parameter values before invoking AUTOGEN.  @            DIGITAL recommends that you run AUTOGEN with feedbackC            about one week after installing DEC Ada or after the DECrD            Ada load changes significantly. Whenever possible, modifyB            the MODPARAMS.DAT file to include MIN_parameter or ADD_B            parameter instead of hard-coding values into this file.        C.2.1 ASTLM  C            The UAF AST queue limit (ASTLM) parameter limits the sumn            of the following:  C            o  The number of asynchronous system trap (AST) requestsfD               that a user's process can have outstanding at one time  C            o  The number of scheduled wakeup requests that a user'sr6               process can have outstanding at one time  #      C-2 Tuning OpenVMS VAX Systems     o            E               The DEC Ada delay statement is implemented as a call to F               the OpenVMS SYS$SETIMR system service, which executes anG               AST routine. DEC Ada also provides facilities for calling D               OpenVMS system routines that execute AST routines. ForG               example, the package STARLET provides the system servicesrC               SYS$QIO and SYS$QIOW both of which let you specify andG               AST service routine. The routines in the package TASKING_eG               SERVICES execute ASTs as well (although the execution andg=               handling of the ASTs is hidden by the package).e  F               The suggested OpenVMS value for ASTLM is 24. This shouldG               be sufficient for most DEC Ada programs. If your programslD               involve tasks that could execute many delay statementsD               simultaneously or if you use a high number of calls toH               OpenVMS system routines that execute AST routines, you may*               want to increase this value.  C               See the DEC Ada Run-Time Reference Manual for OpenVMSeG               Systems for more information on ASTs in DEC Ada programs,l1               especially programs that use tasks.h           C.2.2 ENQLM   G               The UAF enqueue quota (ENQLM) parameter limits the numberoC               of locks that a process and its subprocesses can own.iD               OpenVMS Record Management Services (RMS) uses locks to=               synchronize access to shared files and records.p  B               The DEC Ada compiler and program library manager useC               RMS to access the DEC Ada program library index file,aH               ADALIB.ALB. Up to eight locks can be used for each libraryF               or sublibrary that is open. When a sublibrary is opened,C               usually its parent and its ancestors are also opened. A               If you are using a sublibrary that has a parent and B               a grandparent, up to 24 (3 * 8) locks may be needed.C               Commands such as ACS COPY UNIT can have two libraries F               or sublibraries open at the same time, which doubles the               number of locks.  F                 ________________________Note  ________________________  A                 The suggested OpenVMS value for ENQLM is 30. Thiso=                 value is not sufficient for using the DEC Ada     H                                           Tuning OpenVMS VAX Systems C-3 l  u            ;               program library manager and sublibraries. The 8               recommended value for DEC Ada users is 60.  C               _____________________________________________________         C.2.3 FILLM  ?            The UAF open file limit (FILLM) parameter limits thehE            number of files that a user's process can have open at oneNB            time. This limit includes the number of network logical5            links that can be active at the same time.   E            The DEC Ada compiler, the DEC Ada program library manager,.E            and the OpenVMS Linker use the value of FILLM to limit theiC            total number of files open at one time. If a compilationaD            involves a large number of units and FILLM is set too lowC            to allow all the files involved to be opened at the sameiC            time, the compilation can take a long time. For example,bD            if a unit depends directly or indirectly on 99 additionalE            units and if FILLM is set to 20, the compilation is sloweri-            than if FILLM had been set to 100.n  E            FILLM is a pooled limit with a suggested value of 20. ThisIA            value is not sufficient for most DEC Ada compilations.:E            The recommended minimum value for DEC Ada users is 50. The D            value of FILLM must always be lower than the value of the7            SYSGEN channel count (CHANNELCNT) parameter.o  @            If you increase the value of the FILLM parameter, you?            may also want to increase the value of the UAF BYTLMiC            parameter. The general rule for the relationship between D            these two parameters is that the value of BYTLM should be1            at least 100 times the value of FILLM.V        C.2.4 PRCLM  E            The UAF subprocess creation limit (PRCLM) parameter limits ?            the number of subprocesses that a user's process cand            create.  C            The DEC Ada program library manager creates a subprocesso@            to run the linker or the DEC Ada compiler for the ACSA            LINK/WAIT, COMPILE/WAIT, LOAD/WAIT, and RECOMPILE/WAIT E            commands. Only one subprocess is created, and the creating ?            process waits for the termination of the subprocess.e  #      C-4 Tuning OpenVMS VAX Systemso P  e            @               The suggested value for PRCLM is 2. This should beC               sufficient for the DEC Ada program library manager asl               well.l           C.2.5 TQELM*  F               The UAF timer queue entry limit (TQELM) parameter limits'               the sum of the following:s  H               o  The number of entries that a user's process can have in                   the timer queue  D               o  The number of temporary common flag clusters that a(                  user's process can have  E               The DEC Ada delay statement is implemented as a call tocH               the OpenVMS SYS$SETIMR system service, which adds an entry!               to the timer queue.t  E               The suggested OpenVMS value for TQELM is 20. This value A               should be sufficient for most Ada programs. If your B               programs involve tasks that could execute many delayF               statements simultaneously, you may want to increase this               value.  C               See the DEC Ada Run-Time Reference Manual for OpenVMStD               Systems for more information on the interaction of the<               TQELM parameter with DEC Ada tasking programs.  "         C.2.6 Virtual Memory Usage  F               Various SYSGEN and user parameters should be set so thatB               a DEC Ada compilation can use up to 20,000 pages (10B               megabytes) of virtual memory. The following sectionsH               describe working set parameters that should be adjusted toE               provide good performance for such large virtual address                spaces.a  )               o  VIRTUALPAGECNT parametern  E                  The SYSGEN VIRTUALPAGECNT parameter sets the maximumsC                  number of virtual pages that can be mapped for anysF                  one process. The OpenVMS default (65,536 pages, or 32G                  megabytes) should be adequate for compilations of most "                  DEC Ada programs.  $               o  PGFLQUOTA parameter  H                                           Tuning OpenVMS VAX Systems C-5    .            =               The UAF paging file quota (PGFLQUOTA) parameteriB               limits the number of pages that your process can use@               in the system paging file. It limits the amount ofC               read/write working storage that the compiler can use.v@               PGFLQUOTA should be set to a value consistent with               VIRTUALPAGECNT.   D               The suggested OpenVMS value of 12,800 for PGFLQUOTA isD               too low. A value of at least 17,000 is recommended. ItB               is unnecessary to raise the value of PGFLQUOTA above%               (VIRTUALPAGECNT-3,000).   @               If the value of PGFLQUOTA or the system's value ofC               VIRTUALPAGECNT is too low, large DEC Ada compilations 5               fail and you see the following message:   -               %F, Insufficient virtual memory                o  System Paging File  >               The system paging file (SYS$SYSTEM:PAGEFILE.SYS)A               determines the amount of paging space available for 6               system processes and RMS global buffers.  E               The paging file size should be greater than the maximumo@               paging file quota (UAF PGFLQUOTA parameter) for anD               individual. It should also be greater than the virtual?               page count (SYSGEN VIRTUALPAGECNT parameter). For E               example, if the value of VIRTUALPAGECNT is 20000 pages, D               then a paging file of at least 30000 blocks is needed.  C               If the paging file size is not properly adjusted with @               respect to these two parameters, system processingE               could appear to be suspended and the following messages                is displayed:   O               %SYSTEM-W-PAGEFRAG, Page file badly fragmented, system continuingAI               %SYSTEM-W-PAGECRIT, Page file space critical, system tryingI                to continue  A               It is recommended that you use the DIGITAL-suppliedC>               AUTOGEN command procedure to suggest the size ofB               the system paging file after adjusting the values ofC               VIRTUALPAGECNT and PGFLQUOTA. See Section 1.4.2.3, or D               the OpenVMS System Manager's Manual for information onD               how to use AUTOGEN and how to specify parameter values&               before invoking AUTOGEN.  #      C-6 Tuning OpenVMS VAX Systems     S            H                  See the OpenVMS System Manager's Manual for informationG                  on the OpenVMS default value of PGFLQUOTA. See the VMShF                  System Generation Utility Manual for more information@                  on the OpenVMS default value of VIRTUALPAGECNT.  0               o  WSQUOTA and WSEXTENT parameters  H                  The UAF working set quota (WSQUOTA) parameter specifiesC                  the maximum size to which a user's physical memory G                  size can grow on a typically loaded system. The systemlD                  guarantees the user that WSQUOTA physical pages are1                  available to the user's process.E  @                  The UAF working set extent (WSEXTENT) parameterF                  specifies the maximum size to which a user's physicalF                  memory can grow, independent of system load. WSEXTENT<                  should be greater than or equal to WSQUOTA.  A                  If WSEXTENT is greater than WSQUOTA, the OpenVMS @                  operating system attempts to provide additionalB                  physical pages to a process that is page-faultingH                  heavily. On a lightly loaded system, the user's working<                  set can grow beyond WSQUOTA up to WSEXTENT.  C                  A DEC Ada compilation should have a working set of A                  2500 pages or more. If a user is going to do DECmB                  Ada compilations interactively or in a subprocessD                  (COMPILE/WAIT), the user's UAF entry should specify                  WSQUOTA=2500.  A                  Many sites may not permit large working sets formE                  interactive jobs. In this case, a batch queue shouldME                  be established for DEC Ada compilations. The DEC Ada G                  batch queue can define values for WSQUOTA and WSEXTENT C                  that override the UAF values. Compilations done in_C                  the batch queue can have much larger working sets,BD                  resulting in better compile times and better use of"                  system resources.              H                                           Tuning OpenVMS VAX Systems C-7 _  _            !      C.2.7 Batch Queue Parameters   D            A batch queue with large working set parameters should be            provided for ?            DEC Ada compilations. This batch queue minimizes the A            number of concurrent DEC Ada compilations so that eachu=            compilation completes efficiently without inducingt%            excessive system overhead.   E            You should define the logical name ADA$BATCH in the system B            logical name table. The DEC Ada program library managerB            submits ACS COMPILE and RECOMPILE commands to the queueA            named by ADA$BATCH. If ADA$BATCH is not defined, theseh+            jobs are submitted to SYS$BATCH.q  C            A typical DEC Ada batch queue that is designed to handleoE            two concurrent compilations should be initialized with theu            following values:  #            $INITIALIZE/QUEUE/BATCH-d(            /BASE_PRIORITY=4/JOB_LIMIT=2-4            /WSQUOTA=2500/WSEXTENT=4000     ADA_BATCH  .            $ ASSIGN/SYSTEM ADA_BATCH ADA$BATCH        C.2.8 WSMAX Parameter  A            The SYSGEN working set maximum number of pages (WSMAX) E            parameter sets the maximum number of pages for any workingmE            set on a systemwide basis. The value of WSMAX should be asrC            great as the maximum WSEXTENT value assigned to any usero            or batch queue.  E            The OpenVMS default WSMAX of 1024 pages is too low for DEC 8            Ada. A value of at least 4000 is recommended.  #      C.2.9 Channel Count Parameters   D            The SYSGEN channel count (CHANNELCNT) parameter specifies@            the maximum number of channels for each process in an>            OpenVMS system. The UAF file and logical link limitB            (FILLM) parameter specifies the maximum number of filesA            that can be open at one time, including active networka            logical links.y  #      C-8 Tuning OpenVMS VAX Systemsa e  s            D               The DEC Ada compiler, DEC Ada program library manager,H               and the OpenVMS Linker use the value of FILLM to limit theF               total number of open files at one time. They close files9               as necessary to avoid exceeding that value.i  F               The compiler and program library manager assume that theF               value of FILLM (which has a default value of 20) is lessE               than the value of CHANNELCNT (which has a default value B               of 127). You may need to raise the value of FILLM toC               accommodate DEC Ada compilations that involve a largeOG               number of compilation units. You should be careful not topE               raise the value of FILLM above the value of CHANNELCNT.r  1         C.2.10 Program Library Networking Effects   @               There are several SYSGEN and DECnet parameters (onB               both the local and remote nodes) that can affect theF               availability of compilation units or files accessed overC               DECnet. For example, every time a file is opened on aYC               remote node, a temporary connection, called a logicalcC               link, is made from the local node to the remote node.FF               The total number of logical links allowed at one time isH               controlled by DECnet and can be set by the Network Control?               Program (NCP) utility with the following command:d  +               NCP> SET EXECUTOR MAX LINKS X   D               The X in this command is the maximum number of logicalD               links. This number represents the system (not process)G               quota. Each connection between two nodes deducts one fromtF               the quota total. When setting this value, note that bothF               the DEC Ada compiler and program library manager use theH               per-process FILLM (file and logical link limit) quota, notG               the system quota, to limit the total number of open files                at one time.  F               Limiting the total number of files open at one time alsoF               reduces the potential number of logical links created toH               the remote node. A logical link is required only for files,               that are not accessed locally.  E               Because the creation of a logical link may also involvebH               the creation of a process on the remote node, you may needH               to increase (or at least monitor) the values of the SYSGENF               parameters MAXPROCESSCNT and BALSETCNT. This allows more  H                                           Tuning OpenVMS VAX Systems C-9                 D            processes to be created for libraries for network servers            (FALs).  >            If you are expecting to access a number of files orB            compilation units over DECnet, you may want to increase@            the value of the UAF buffered input-output byte count?            limit (BYTLM) parameter on your system. The value of C            this parameter affects the efficiency of program library A            operations performed over DECnet. Other parameters mayeC            also have an effect. DECnet parameters are documented in 6            the DECnet for OpenVMS Guide to Networking.  -      C.3 Relevant File Quotas and Cache SizesM  D            The following sections describe how to estimate the sizes<            that the various OpenVMS caches should be set to.  A            The relevant system manuals should be consulted to de-nD            termine whether the resulting cache sizes are supportable;            (perhaps after installing more physical memory).   E            The major classes of data that must be read from the diskse            are as follows:  E            o  The files themselves, especially the ADALIB.ALB and thes               .ACU files  C            o  The file headers from within INDEXF.SYS that describeh/               where the files themselves residen  >            o  The directory files that describe where the file/               headers reside, given a file namen        C.3.1 Caching Files  E            Each time DEC Ada performs a compilation or ACS operation, E            the following disk files are cached into memory as needed:               o  DEC Ada compiler  -            o  DEC Ada program library managerA  2            o  Contents of all necessary .ACU files  C            For both small and large programs, caching can save time E            when performing compilations or ACS operations by avoiding C            unnecessary disk accesses. You can maximize the benefits             of caching by:o  $      C-10 Tuning OpenVMS VAX Systems                 H               o  Invoking the program library manager interactively. For                  example:h                    $ ACS                  ACS>   F               o  Specifying more than one unit with the DCL ADA or ACS9                  command, whenever possible. For example:T  1                  ACS> COMPILE UNITA, UNITB, UNITCn  "         C.3.2 Caching File Headers  C               The OpenVMS system uses file header caches to greatly C               reduce the time needed to open files. The size of the G               cache is controlled by the SYSGEN parameter ACP_HDRCACHE._I               OpenVMS sets a default value of 128 pages for ACP_HDRCACHE, E               but this value may be too small for the typical DEC Ada -               program running on your system.v  D               Because of the way the DCL ADA and ACS commands accessC               files, it is important that the value of ACP_HDRCACHE C               is large enough to keep all the accessed file headers.E               cached. If the cache is not large enough, the potentialiA               performance benefits of the cache are generally noto               realized.   @               To estimate the value needed for ACP_HDRCACHE, youB               need to sum the total number of files that a typicalC               DEC Ada program may require to compile, link, and runnG               successfully. The following lists the files that you needi7               when estimating a value for ACP_HDRCACHE:   C               o  Total number of .ACU files in your program libraryl  C               o  Total number of .OBJ files in your program libraryc  B               o  Total number of .ADA source files in your program  C               o  Total number of .ALB files in your program librarya  C               o  Total number of directories that must be accessed,C?                  including any subdirectories that are accessed   H               o  Total number of system files that your program accesses  G               o  Total number of other files that your program accesses   3               o  Some for other users on the systema  H                                          Tuning OpenVMS VAX Systems C-11    C            E            You must include units from the predefined library in your E            estimates. You do not need to add the total number of .ADC D            files (copied source files) to your estimate because they&            are typically not accessed.  C            Suppose the typical DEC Ada program on your system is asL            follows:d  C            o  Contains 220 .ACU files, 220 .OBJ files, and 100 .ADAa@               files. (For this example, the predefined units are5               considered part of the 220 .ACU files.)o  @            o  Located in two sublibraries and one parent library3               (making for a total of 3 .ALB files).D  %            o  Accesses 5 directories.   '            o  Accesses 15 system files.   %            o  Accesses 8 other files.i  >            The following example shows the calculation for the            preceding program:e                   220    .ACU files                 220    .OBJ files                 100    .ADA files                   3    .ALB files!                  5    Directoriese"                 15    System files!             +    8    Other filesp"            -----------------------/                571    Estimate for ACP_HDRCACHEd  ;            It is not unusual to have an estimated value for )            ACP_HDRCACHE that is over 500..  E            One way to increase the value of ACP_HDRCACHE is to modifyf?            the MODPARAMS.DAT file and run AUTOGEN. For example,aC            suppose you wanted to increase the value of ACP_HDRCACHEcC            by more than the amount you estimated. To do this, enter-8            the following line in the MODPARAMS.DAT file:  !            ADD_ACP_HDRCACHE = 600o  $      C-12 Tuning OpenVMS VAX Systems h  C            C               For the new value of ACP_HDRCACHE to take effect, youiD               must run AUTOGEN. If you run AUTOGEN with feedback, itB               increases the size of the file header cache in smallG               increments if the header cache is too small. However wheneF               the system load can be predicted, it is better to modifyG               the MODPARAMS.DAT file than to use AUTOGEN with feedback.a  %         C.3.3 Caching Directory Filese  H               In general, the program library manager accesses directoryE               files in a random order. Consequently, the ACP_DIRCACHEsD               parameter should be set to the sum of the sizes of allB               the directories needed to be accessed when compilingF               and linking your programs. Unlike the ACP_HDRCACHE, thisG               number gives steady improvement as it gets better, ratherVD               than a dramatic improvement as it crosses a threshold.  +         C.4 Using DECram on OpenVMS Systemsi  E               Using pseudo-disks, such as DECram, can be an effectivesG               way of reducing disk traffic. For example, you can locategC               your current program library and any other frequentlyb4               accessed libraries on the DECram disk.  C               You can also use a DECram disk to place the copy (useGG               ACS COPY) of a library so that you can access those filesdE               quickly. Once you create a copy of the units in the newoD               library, any updates to the original library can causeC               the new library and the original library to be out ofT               synchronization.  E               If you do not have enough space on your DECram disk for E               all the units in your DEC Ada program, consider placing F               only the specifications of the units on the DECram disk.F               Most of the units that are accessed during a compilation!               are specifications.g  F                 ________________________Note  ________________________  B                 DECram for OpenVMS does not support long-term dataD                 storage because data in a DECram device is volatile.  E                 _____________________________________________________o    H                                          Tuning OpenVMS VAX Systems C-13