                                     C                      DECset________________________________________ ;                      Installation Guide for OpenVMS Systems   .                      Order Number: AA-PUPKD-TK                        May 1995   B                      This guide explains how to install DECset for%                      OpenVMS Systems, "                      Version 12.0.      C                      Revision/Update information: This is a revised 9                                                   manual.   G                      Operating System and Version: OpenVMS VAX, Version ?                                                   5.5 or higher @                                                   OpenVMS Alpha,G                                                   Version 1.5 or higher C                                                   DECwindows Motif, G                                                   Version 1.1 or higher   E                      Software Version:            DECset for OpenVMS, >                                                   Version 12.0          2                      Digital Equipment Corporation+                      Maynard, Massachusetts                  E            __________________________________________________________ $            First Printing, June 1993!            Revised, November 1993             Revised, May 1995  D            While Digital or EDS believes the information included inE            this publication is correct as of the date of publication, 2            it is subject to change without notice.  C            Possession, use, or copying of the software described in D            this documentation is authorized only pursuant to a validC            written license from Digital, an authorized sublicensor, &            or the identified licenser.  ?            Digital Equipment Corporation or EDS makes no repre- A            sentations that the interconnection of its products in B            the manner described in this document will not infringeD            existing or future patent rights, nor do the descriptionsD            contained in this document imply the granting of licensesD            to make, use, or sell equipment or software in accordance             with the description.  ,             EDS Defense Limited 1994, 1995.  A             Digital Equipment Corporation 1993, 1995. All rights             reserved.  <            The following are trademarks of Digital EquipmentA            Corporation: DEC, DEC Ada, DECnet, DECset, DECwindows, A            OpenVMS, VAX, VAX Ada, VAX BASIC, VAX BLISS-32, VAX C, G            VAXcluster, VAX COBOL, VAX DIBOL, VAX DOCUMENT, VAX FORTRAN, ;            VAX Pascal, VAX SCAN, VMS, and the DIGITAL logo.   4            The following are third-party trademarks:  ?            Motif is a registered trademark of the Open Software             Foundation, Inc. A            PostScript is a registered trademark of Adobe Systems,             Inc.   0            This document is available on CD-ROM.  E            This document was prepared using VAX DOCUMENT Version 2.1.                                C    ________________________________________________________________   C                                                            Contents     C    Preface..................................................    vii     +    1  Preparing to Install the DECset Tools   C          1.1   DECset Bill of Materials.....................    1-1 C          1.2   Prerequisite Software........................    1-2 C          1.3   Accessing Online Release Notes...............    1-2 C          1.4   Installation Procedure Requirements..........    1-3 ;          1.4.1     Requirements for the Environment Manager C                    System...................................    1-6 7          1.4.2     Requirements for DEC Code Management C                    System...................................    1-6 :          1.4.3     Requirements for DEC Language-SensitiveC                    Editor...................................    1-7 C          1.4.4     Requirements for Source Code Analyzer....    1-7 C          1.4.5     Requirements for DEC Test Manager........    1-8 7          1.4.6     Requirements for DEC Performance and C                    Coverage Analyzer........................    1-8 9          1.4.7     Requirements for DEC Module Management C                    System...................................    1-8 C          1.5   User Account Quotas and Privileges...........    1-9 C          1.5.1     Quotas and Privileges for CMS............   1-11 C          1.5.2     Quotas and Privileges for LSE............   1-11 C          1.5.3     Quotas and Privileges for SCA............   1-12 5          1.5.4     Quotas and Privileges for DEC Test C                    Manager..................................   1-12 C          1.5.5     Quotas and Privileges for PCA............   1-12 C          1.5.6     Quotas and Privileges for MMS............   1-13 C          1.6   OpenVMS License Management Facility..........   1-13 C          1.7   Using VMSINSTAL..............................   1-14       C                                                                 iii                  !      2  Installing the DECset Kit   E            2.1   Prerequisite Software........................    2-1 E            2.2   Accessing the DECset Online Release Notes....    2-2 E            2.3   Installation Procedure Requirements..........    2-2 E            2.4   Using VMSINSTAL..............................    2-3 /            2.5   Preparing for DECset Component E                  Installation.................................    2-5 E            2.6   Installing DECset Components.................    2-6 6            2.7   Running the Installation VerificationE                  Procedures...................................    2-9 E            2.8   Installing the DECset Online Documentation...   2-10   1      3  Installing the DEC Code Management System   E            3.1   Preparing to Install CMS.....................    3-1 E            3.1.1     Installation Procedure Requirements......    3-2 E            3.2   User Account Quotas and Privileges...........    3-2 E            3.3   Using CMS with Other Tools...................    3-3 E            3.4   Installing CMS...............................    3-3 E            3.4.1     Installing CMS on a VAXcluster...........    3-9   4      4  Installing the DEC Language-Sensitive Editor  E            4.1   Installation Procedure Requirements..........    4-1 E            4.1.1     User Account Quotas and Privileges.......    4-2 E            4.2   Installing LSE...............................    4-5 E            4.3   Installing LSE on a VAXcluster...............   4-12 E            4.4   After the Installation.......................   4-13   +      5  Installing the Source Code Analyzer   E            5.1   Installation Procedure Requirements..........    5-1 E            5.2   User Account Quotas and Privileges...........    5-2 E            5.3   SCA Server Installation......................    5-2 E            5.4   Installing SCA...............................    5-5 E            5.4.1     Installing SCA on a VAXcluster...........   5-19                       iv                  *         6  Installing the DEC Test Manager  H               6.1   Installation Procedure Requirements..........    6-1H               6.2   User Account Quotas and Privileges...........    6-2H               6.2.1     Special Requirements.....................    6-3H               6.3   Installing DEC Test Manager..................    6-38               6.3.1     Installing DEC Test Manager on aH                         VAXcluster...............................    6-8;               6.3.2     Running DEC Test Manager on a Mixed H                         VAXcluster...............................    6-9H               6.3.3     DEC Test Manager Files...................    6-9  ?         7  Installing the DEC Performance and Coverage Analyzer   H               7.1   Required Operating System Components.........    7-1H               7.2   Prerequisite Software........................    7-1H               7.3   Optional Software............................    7-1H               7.4   Installation Procedure Requirements..........    7-2H               7.5   User Account Quotas and Privileges...........    7-3H               7.6   Installing DEC PCA...........................    7-3H               7.6.1     Installing DEC PCA on a VAXcluster.......   7-10H               7.7   After the Installation.......................   7-10  6         8  Installing the DEC Module Management System  H               8.1   Prerequisite Software........................    8-1H               8.2   Installation Procedure Requirements..........    8-1H               8.3   User Account Quotas and Privileges...........    8-2H               8.4   Using MMS with Other Tools...................    8-2H               8.5   Installing MMS...............................    8-3H               8.5.1     Installing MMS on a VAXcluster...........    8-8  !         9  After the Installation   9               9.1   Running the Installation Verification H                     Procedure Separately.........................    9-1H               9.2   Error Conditions.............................    9-2H               9.3   Maintenance Updates..........................    9-3H               9.4   Reporting Problems...........................    9-3            H                                                                        v                 %      A  Sample Installation Procedure     :      B  Sample Online Documentation Installation Procedure          Tables   E            1         Conventions Used in this Guide...........     ix   E            1-1       DECset Online Release Notes File Names...    1-2   :            1-2       DECset for OpenVMS Alpha InstallationE                      Requirements.............................    1-5   8            1-3       DECset for OpenVMS VAX InstallationE                      Requirements.............................    1-6   <            1-4       DECset for OpenVMS Alpha Account QuotasE                      and Privileges...........................   1-10   >            1-5       DECset for OpenVMS VAX Account Quotas andE                      Privileges...............................   1-10   8            2-1       Disk Space Storage Requirements forE                      OpenVMS Alpha Systems....................    2-2   8            2-2       Disk Space Storage Requirements forE                      OpenVMS VAX Systems......................    2-2                                       vi                            H         ________________________________________________________________  H                                                                  Preface      C               This guide explains how to install DECset for OpenVMS C               systems, Version 12.0. Throughout this guide, OpenVMS E               systems refers to OpenVMS VAX and OpenVMS Alpha systems '               unless explicitly stated.   B               DECset for OpenVMS systems consists of the following               tools:  1               o  DEC Code Management System (CMS)   4               o  DEC Language-Sensitive Editor (LSE)  +               o  Source Code Analyzer (SCA)   !               o  DEC Test Manager   <               o  DEC Performance and Coverage Analyzer (PCA)  3               o  DEC Module Management System (MMS)   A               Included in the DECset kit are save sets containing 9               documentation in PostScript or text format.            Intended Audience   C               This guide is intended for system managers of OpenVMS                systems.           Document Structure  H               This guide contains the following chapters and appendices:  @               o  Chapter 1 gives preinstallation information for-                  installing the DECset tools.   G               o  Chapter 2 describes how to run the DECset installation >                  procedure to install any or all of the DECset                  components.  H                                                                      vii                 >            o  Chapter 3 tells how to install CMS individually.  >            o  Chapter 4 tells how to install LSE individually.  >            o  Chapter 5 tells how to install SCA individually.  =            o  Chapter 6 tells how to install DEC Test Manager                individually.   >            o  Chapter 7 tells how to install PCA individually.  >            o  Chapter 8 tells how to install MMS individually.  <            o  Chapter 9 gives post installation information.  E            o  Appendix A gives a sample script of installing a few of $               the DECset components.  @            o  Appendix B gives a sample script of installing the*               DECset online documentation.        Associated Documents   ;            The following documents may also be helpful when              installing DECset for            OpenVMS systems:   ?            o  Using DECset for OpenVMS Systems describes how to A               use the DEC Software Engineering Tools and platform B               software to create an effective software development               environment.  D            o  The DECset media also contains an online documentation@               kit that can be installed in a public area on yourD               system. For more information on the names and location?               of these online files, please refer to the DECset >               release notes. For information on installing the>               documentation kit, see Appendix B in this guide.              	      viii                           Conventions   ?               Table 1 lists the conventions used in this guide.   H               Table_1_Conventions_Used_in_this_Guide____________________  H               Convention__________Description___________________________  B               $                   A dollar sign ($) represents the<                                   OpenVMS DCL system prompt.  B               <Return>            In interactive examples, a labelB                                   enclosed in a box indicates thatF                                   you press a key on the keyboard, for4                                   example, <Return>.  F               Ctrl/x              The key combination Ctrl/x indicatesE                                   that you must press the key labeled E                                   Ctrl while you simultaneously press E                                   another key, for example, Ctrl/Y or )                                   Ctrl/Z.   H               KPn                 The phrase KPn indicates that you mustG                                   press the key labeled with the number G                                   or character n on the numeric keypad, :                                   for example, KP3 or KP-.  C               file-spec, ...      A horizontal ellipsis following a G                                   parameter, option, or value in syntax C                                   descriptions indicates additional H                                   parameters, options, or values you can(                                   enter.  D               boldface monospace  Boldface monospace text representsG               text                user input in interactive examples in E                                   the hardcopy and online versions of -                                   this guide.   F                . . .              A horizontal ellipsis in a figure orG                                   example indicates that not all of the 7                                   statements are shown.   H                                                 (continued on next page)    H                                                                       ix                 E            Table_1_(Cont.)_Conventions_Used_in_this_Guide____________   E            Convention__________Description___________________________   @            .                   A vertical ellipsis indicates theD            .                   omission of items from a code example?            .                   or command format; the items are E                                omitted because they are not important <                                to the topic being discussed.  D            ()                  In format descriptions, if you choose@                                more than one option, parenthesesA                                indicate that you must enclose the 6                                choices in parentheses.  ?            []                  In format descriptions, brackets A                                indicate that whatever is enclosed E                                is optional; you can select none, one, 5                                or all of the choices.   =            {}                  In format descriptions, braces E                                surround a required choice of options; A                                you must choose one of the options &                                listed.  ;            boldface text       Boldface text represents theo:                                introduction of a new term.  <            italic text         Italic represents parameters,B                                arguments, and information that canD                                vary in system messages (for example,A                                Internal error number), as well as +                                book titles.   >            UPPERCASE           Uppercase indicates the name of@                                a command, routine, the name of aB                                file, the name of a file protectionD                                code, or the abbreviation of a system)                                privilege.c  C            lowercase           Lowercase in examples indicates thateD                                you are to substitute a word or valueE            ____________________of_your_choice._______________________           x n  r                  H                                                                        1H         ________________________________________________________________  H                                    Preparing to Install the DECset Tools      @               This chapter presents the following information on4               preparing to install the DECset tools:  -               o  Your bill of materials (BOM)u  &               o  Prerequisite software  3               o  Accessing the online release notesA  4               o  Installation procedure requirements  3               o  User account quotas and privilegesR  :               o  OpenVMS License Management Facility (LMF)                  o  Using VMSINSTAL  H               Where appropriate, this chapter gives specific information               on each tool.   $         1.1 DECset Bill of Materials  C               Your bill of materials (BOM) specifies the number and F               contents of your media. Be sure to check the contents ofG               your kit against this information. If your kit is damaged D               or if you find that parts of it are missing, call your%               Digital representative.   H               Distribution media must be mounted in numerical order. TheF               installation procedure prompts you to mount the volumes.F               For more information on how to mount distribution media,H               see your processor-specific installation/operations guide.D               This guide details several options to the installation               procedure.  H                                Preparing to Install the DECset Tools 1-1 i  e                  1.2 Prerequisite Software  D            On OpenVMS Alpha systems, each DECset, Version 12.0, toolB            requires OpenVMS Alpha operating system, Version 1.5 or            higher.  B            If you are using the DECwindows interface for any tool,D            you must have OpenVMS Alpha operating system, Version 1.5E            or higher, and DECwindows Motif for OpenVMS Alpha, Versionz3            1.1 or higher, installed on your system.E  B            On OpenVMS VAX systems, each DECset, Version 12.0, tool2            requires OpenVMS Version 5.5 or higher.  B            If you are using the DECwindows interface for any tool,<            you must have OpenVMS, Version 5.5 or higher, and@            DECwindows Motif, Version 1.1 or higher, installed on            your system..  '      1.3 Accessing Online Release Notes   >            Each DECset tool provides online release notes. TheB            prompt to display or print the release notes during the4            installation is described in Section 1.7.  =            To obtain the release notes for each of the DECset A            tools after the installation, print the files shown in             Table 1-1.s  E            Table_1-1_DECset_Online_Release_Notes_File_Names__________r  E            Tool____________________File_Name_________________________i  B            DECset Component        SYS$HELP:DECSETDOCS120.RELEASE_(            Release Notes           NOTES  :            Environment Manager     ENVMGR010.RELEASE_NOTES  @            DEC Code Management     SYS$HELP:CMS037.RELEASE_NOTES            Systema  @            DEC Module Management   SYS$HELP:MMS030.RELEASE_NOTES            Systeme  @            DEC Test Manager        SYS$HELP:DTM036.RELEASE_NOTES  E                                              (continued on next page).  .      1-2 Preparing to Install the DECset Tools D  e            H               Table_1-1_(Cont.)_DECset_Online_Release_Notes_File_Names__  H               Tool____________________File_Name_________________________  C               DEC Language-Sensitive  SYS$HELP:LSE043.RELEASE_NOTESo               Editor  C               Source Code Analyzer    SYS$HELP:SCA043.RELEASE_NOTESl  C               DEC Performance and     SYS$HELP:PCA043.RELEASE_NOTESeH               Coverage_Analyzer_________________________________________  E               Online help also directs you to the release notes file..G               After the installation, enter the following command line:   0               $ HELP tool RELEASE_NOTES <Return>  C               In the previous command line, tool represents the DCL.C               command that invokes the tool on which you want help.V  /         1.4 Installation Procedure Requirementst  H               The installation of each tool takes approximately 10 to 45E               minutes, depending on the type of media and your systemsH               configuration. Before installing any DECset tool, you mustF               have the SETPRV privileges, or CMKRNL, WORLD, and SYSPRV               privileges.   D               When a DECset tool is started up within the DECwindowsF               interface, it will also start up the Environment ManagerB               interface, if the Environment Manager is not alreadyF               running. The Environment Manager comes up iconified when4               it is invoked in this indirect manner.  ?               Table 1-2 and Table 1-3 list the following system @               resources for each DECset tool you are installing:  G               o  The minimum amount of free disk space during and afterl                  installation.  @               o  The minimum number of free global pagelets plus@                  the size (in number of disk blocks) of the file;                  SYS$LIBRARY:DCLTABLES.EXE at installation..  >               o  The minimum number of free global sections at                  installation.  H                                Preparing to Install the DECset Tools 1-3    c            B            These resources reflect the amount of space needed when<            installing the DECwindows interface to each tool.  C               ________________________Note ________________________t  @               You must ensure that your system has the necessaryA               global pagelet and global section SYSGEN quotas foru@               the installation. Failure to do so could cause the<               DCL tables to be corrupted in some situations.  C               _____________________________________________________   B            To determine the number of available global pagelets onD            your system, invoke the OpenVMS Install Utility (INSTALL)+            and enter the following command:.  1            $ INSTALL LIST/GLOBAL/SUMMARY <Return>   :                    Summary of Local Memory Global Sections  K            nnn Global Sections Used,  nnnn/nnnn Global pagelets Used/UnusedI  E            When you enter this command, the system displays a summaryi?            of the number of global sections used, the number of B            global pagelets used, and the number of global pageletsB            unused. Exit from INSTALL by entering the EXIT command.  >            If there are not enough pagelets available, you can>            delete an existing known image with INSTALL, or in-@            crease the GBLPAGES system parameter with the OpenVMS<            System Generation Utility (SYSGEN) by editing the>            file SYS$SYSTEM:MODPARAMS.DAT and then invoking theA            SYS$UPDATE:AUTOGEN.COM procedure. For more information D            on the AUTOGEN.COM procedure, see your processor-specific)            installation/operations guide..  D            You can determine the number of available global sectionsB            by invoking SYSGEN and entering the following commands:  +            $ RUN SYS$SYSTEM:SYSGEN <Return> '            SYSGEN> USE CURRENT <Return>s,            SYSGEN> SHOW GBLSECTIONS <Return>R            Parameter Name   Current   Default   Minimum   Maximum   Unit   DynamicR            --------------   -------   -------   -------   --------  ----   -------L            GBLSECTIONS          nnn       nnn       nnn        nnn  Sections             SYSGEN> EXIT <Return>  .      1-4 Preparing to Install the DECset Tools                 H               The first number displayed is the current number of globalE               sections. Compare this to the number of global sectionsDG               in use as displayed by INSTALL. For example, CMS requireseD               14 global sections. Therefore, if the number of globalB               sections used (displayed by INSTALL) plus 14 exceedsF               the current number of global sections, you must increaseD               the number of available global sections before you canD               install CMS. To increase the number, you must increaseE               the GBLSECTIONS system parameter with SYSGEN by editing.E               the file SYS$SYSTEM:MODPARAMS.DAT and then invoking the D               SYS$UPDATE:AUTOGEN.COM procedure. For more informationG               on the AUTOGEN.COM procedure, see your processor-specific ,               installation/operations guide.  F               If the number of global sections used plus the number ofF               global sections needed by the tool you are installing isF               less than the current number of global sections, you can,               exit from SYSGEN and continue.  @               Table 1-2 lists the OpenVMS Alpha system resourcesH               required for each DECset tool. Table 1-3 lists the OpenVMSA               VAX system resources required for each DECset tool.a  H         Table_1-2_DECset_for_OpenVMS_Alpha_Installation_Requirements____  A                          Disk Space  Disk Space  Global    Global C                          During      After       Pagelets  SectionsaH         Tool_____________InstallationInstallationRequired__Required_____  <         ENVMGR           2,000       600         700       3  =         CMS              21,000      12,500      3,500     14y  =         LSE              42,000      20,000[1]   8,200     15c  =         SCA              18,000      14,000      8,700     15   <         DEC Test         25,000      16,500      1,200     8         Manager   =         PCA              21,000      8,000[2]    2,000     10   <         MMS              4,000       600         500       5H         [1]Includes_all_of_the_supported_LSE_languages._________________  )         [2]Includes the PCA demo package. H         ________________________________________________________________  @               LSE and SCA also require at least 2 MB of physical               memory.   H                                Preparing to Install the DECset Tools 1-5 h  e            E      Table_1-3_DECset_for_OpenVMS_VAX_Installation_Requirements______   >                       Disk Space  Disk Space  Global    Global@                       During      After       Pagelets  SectionsE      Tool_____________InstallationInstallationRequired__Required_____p  9      ENVMGR           2,000       600         700       3   :      CMS              9,000       7,000       1,500     14  :      LSE              40,000      13,500[1]   6,000     15  :      SCA              13,000      9,000       5,000     15  :      DEC Test         15,000      10,000      800       15      Manager  :      PCA              12,000      5,000[2]    1,305     10  9      MMS              2,800       300         500       5sE      [1]Includes_all_of_the_supported_LSE_languages._________________a  &      [2]Includes the PCA demo package.E      ________________________________________________________________   :      1.4.1 Requirements for the Environment Manager System  E            Before installing the Environment Manager System, you mustr(            have the following resources:  A            o  A minimum of 2,000 blocks of free disk space during                installation;i5               600 blocks are used after installation.s  B            o  A minimum of 700 free global pagelets, plus the sizeN               (in number of disk blocks) of the file SYS$LIBRARY:DCLTABLES.EXE               at installation.  B            o  A minimum of 3 free global sections at installation.  6      1.4.2 Requirements for DEC Code Management System  B            Before installing DEC Code Management System (CMS), you-            must have the following resources:M  A            o  A minimum of 9,000 blocks of free disk space duringi               installation; 7               7,000 blocks are used after installation.t  ;            o  A minimum of 1,500 free global pagelets, pluso=               the size (in number of disk blocks) of the file 8               SYS$LIBRARY:DCLTABLES.EXE at installation.  .      1-6 Preparing to Install the DECset Tools t  u            F               o  A minimum of 14 free global sections at installation.  D               o  The minimum number of OpenVMS classes necessary forD                  full functionality as described in the CMS Software+                  Product Description (SPD).d  <         1.4.3 Requirements for DEC Language-Sensitive Editor  H               Before installing DEC Language-Sensitive Editor (LSE), you0               must have the following resources:  E               o  A minimum of 40,000 blocks of free disk space during C                  the installation; 13,500 blocks of free disk space H                  after the installation of LSE. Approximately 300 blocksE                  of free disk space should be added to the disk space H                  after installation for each language that you choose to'                  have supported by LSE.e  6               o  A minimum of 2 MB of physical memory.  >               o  A minimum of 6,000 free global pagelets, plus@                  the size (in number of disk blocks) of the file?                  SYS$LIBRARY:DCLTABLES.EXE at installation. For @                  most efficient operation, you will need a total@                  of 8,000 free global pagelets, plus the size of>                  SYS$LIBRARY:DCLTABLES.EXE after installation.  F               o  A minimum of 15 free global sections at installation.  3         1.4.4 Requirements for Source Code Analyzer   D               Before installing Source Code Analyzer (SCA), you must+               have the following resources:n  E               o  A minimum of 13,000 blocks of free disk space during H                  installation; 9,000 blocks are used after installation.  6               o  A minimum of 2 MB of physical memory.  >               o  A minimum of 4,200 free global pagelets, plus@                  the size (in number of disk blocks) of the file?                  SYS$LIBRARY:DCLTABLES.EXE at installation. For @                  most efficient operation, you will need a total@                  of 4,200 free global pagelets, plus the size of>                  SYS$LIBRARY:DCLTABLES.EXE after installation.  F               o  A minimum of 15 free global sections at installation.  H                                Preparing to Install the DECset Tools 1-7    i            ,      1.4.5 Requirements for DEC Test Manager  @            Before installing DEC Test Manager, you must have the            following resources:s  A            o  A minimum of 9,000 blocks of free disk space during E               installation; 6,000 blocks are used after installation.   ;            o  A minimum of 1,200 free global pagelets, plusn=               the size (in number of disk blocks) of the filec<               SYS$LIBRARY:DCLTABLES.EXE at installation. For=               most efficient operation, you will need a totale=               of 2,100 free global pagelets, plus the size of ;               SYS$LIBRARY:DCLTABLES.EXE after installation.   C            o  A minimum of 15 free global sections at installation.   A      1.4.6 Requirements for DEC Performance and Coverage Analyzer   B            Before installing DEC Performance and Coverage Analyzer8            (PCA), you must have the following resources:  B            o  A minimum of 12,000 blocks of free disk space duringD               installation; 5,000 blocks are used after installation$               with the demo package.  ;            o  A minimum of 1,305 free global pagelets, plus =               the size (in number of disk blocks) of the file <               SYS$LIBRARY:DCLTABLES.EXE at installation. For=               most efficient operation, you will need a total ;               of 100 free global pagelets, plus the size of ;               SYS$LIBRARY:DCLTABLES.EXE after installation._  C            o  A minimum of 10 free global sections at installation.   8      1.4.7 Requirements for DEC Module Management System  D            Before installing DEC Module Management System (MMS), you-            must have the following resources:o  A            o  A minimum of 2,800 blocks of free disk space during C               installation; 300 blocks are used after installation.e  3            o  A minimum of 2 MB of physical memory.   B            o  A minimum of 500 free global pagelets, plus the sizeN               (in number of disk blocks) of the file SYS$LIBRARY:DCLTABLES.EXE               at installation.  .      1-8 Preparing to Install the DECset Tools r  i            E               o  A minimum of 5 free global sections at installation.     .         1.5 User Account Quotas and Privileges  F               To use any DECset tool, each account must have a minimumG               number of privileges and minimum requirements for each ofa"               the following areas:  "               o  AST limit (ASTLM)  6               o  Buffered I/O byte count quota (BYTLM)  &               o  Enqueue quota (ENQLM)  (               o  Open file limit (FILLM)  0               o  Timer queue entry limit (TQELM)  H               Table 1-4 and Table 1-5 list specific requirements in eachE               of these areas for each DECset tool you are installing. F               Use the OpenVMS Authorize Utility (AUTHORIZE) to compareF               the current values of these quotas with the requirementsF               for each tool. The account used in the following example$               is the SYSTEM account:  /               $ SET DEFAULT SYS$SYSTEM <Return>i&               $ RUN AUTHORIZE <Return>'               UAF> SHOW SYSTEM <Return>   C               To change the values of these quotas, use the OpenVMSyG               Authorize Utility's MODIFY command. For more information,iC               see the OpenVMS System Management Utilities Reference1               Manual.n                      H                                Preparing to Install the DECset Tools 1-9 q  e            E      Table_1-4_DECset_for_OpenVMS_Alpha_Account_Quotas_and_Privilegesr  (      Resource                   DEC TestE      Name_______LSE_____SCA_____Manager___CMS_____PCA___MMS__________i  :      ASTLM      24      24      100       14      30    14  >      BYTLM      4,096   18,000  60,000    14,000  4,096 13,000  9      ENQLM      30      30      10        1       -     -d  9      FILLM      20      20      9         6       20    6a  9      TQELM      -       5       -         1       -     -t  9      BIOLM      18      18      -         -       -     -t  9      DIOLM      18      18      -         -       -     -b  9      PRCLM      5       2       4         -       -     2F  9      WSDEF      1,024   600[2]  -         -       -     -l  9      PGFLQUOTA  20,000[120,000  -         -       -     -nE      [1]A_quota_of_40,000_pagelets_is_recommended_if_you_are_using___         the REPORT command.       [2]3000 pagelets (optimum).E      ________________________________________________________________E  E      Table_1-5_DECset_for_OpenVMS_VAX_Account_Quotas_and_Privileges__:  (      Resource                   DEC TestE      Name_______LSE_____SCA_____Manager___CMS_____PCA___MMS__________   :      ASTLM      24      24      100       14      30    14  >      BYTLM      4,096   18,000  60,000    14,000  4,096 13,000  9      ENQLM      30      30      10        1       -     -s  9      FILLM      20      20      9         6       20    6_  9      TQELM      -       5       -         1       -     -a  9      BIOLM      18      18      -         -       -     -d  9      DIOLM      18      18      -         -       -     -.  9      PRCLM      5       2       4         -       -     2E  9      WSDEF      1,024   600[2]  -         -       -     -_  9      PGFLQUOTA  20,000[120,000  -         -       -     -hE      [1]A_quota_of_40,000_pages_is_recommended_if_you_are_using_the__h        REPORT command.      [2]3,000 pages (optimum).E      ________________________________________________________________p  /      1-10 Preparing to Install the DECset Tools                  D               To use any of the DECset tools, each account must have+               TMPMBX and NETMBX privileges.h  +         1.5.1 Quotas and Privileges for CMS   B               To use CMS, it is recommended that each account haveE               TMPMBX and NETMBX privileges and the following require-o               ments:  (               o  AST limit (ASTLM) of 14  @               o  Buffered I/O byte count quota (BYTLM) of 14,000  +               o  Enqueue quota (ENQLM) of 1o  -               o  Open file limit (FILLM) of 6p  5               o  Timer queue entry limit (TQELM) of 1   +         1.5.2 Quotas and Privileges for LSE   B               To use LSE, it is recommended that each account haveE               TMPMBX and NETMBX privileges and the following require-n               ments:  /               o  AST quota (ASTLM) 24 (minimum)D  8               o  Buffered I/O limit (BIOLM) 18 (minimum)  F               o  Buffered I/O byte count quota (BYTLM) 4,096 (minimum)  6               o  Direct I/O limit (DIOLM) 18 (minimum)  3               o  Enqueue quota (ENQLM) 30 (minimum)   5               o  Open file quota (FILLM) 20 (minimum)L  H               o  Paging file quota (PGFLQUOTA) 20,000 pagelets (minimum)  F                  A paging file quota (PGFLQUOTA) of 40,000 pagelets isA                  recommended if you are using the REPORT command.   >               o  Subprocess creation quota (PRCLM) 5 (minimum)  C               o  Working set size (WSDEF) 1,024 pagelets (minimum); 2                  2,048 to 4,096 pagelets (optimum)  H                               Preparing to Install the DECset Tools 1-11 s  y            (      1.5.3 Quotas and Privileges for SCA  ?            To use SCA, it is recommended that each account haveuB            TMPMBX and NETMBX privileges and the following require-            ments:   ,            o  AST limit (ASTLM) 24 (minimum)  5            o  Buffered I/O quota (BIOLM) 18 (minimum)a  D            o  Buffered I/O byte count quota (BYTLM) 18,000 (minimum)  3            o  Direct I/O quota (DIOLM) 18 (minimum)g  0            o  Enqueue quota (ENQLM) 30 (minimum)  2            o  Open file limit (FILLM) 20 (minimum)  E            o  Paging file quota (PGFLQUOTA) 20,000 pagelets (minimum)l  ;            o  Subprocess creation quota (PRCLM) 2 (minimum)m  9            o  Timer queue entry limit (TQELM) 5 (minimum)r  D            o  Working set size (WSDEF) 600 pagelets (minimum); 3,000                pagelets (optimum)  5      1.5.4 Quotas and Privileges for DEC Test ManagerE  ?            To use DEC Test Manager, it is recommended that eachl<            account have TMPMBX and NETMBX privileges and the"            following requirements:  &            o  AST limit (ASTLM) of 100  =            o  Buffered I/O byte count quota (BYTLM) of 60,000   )            o  Enqueue quota (ENQLM) of 10e  *            o  Open file limit (FILLM) of 9  4            o  Subprocess creation quota (PRCLM) of 4  (      1.5.5 Quotas and Privileges for PCA  ?            To use PCA, it is recommended that each account haveuB            TMPMBX and NETMBX privileges and the following require-            ments:n  ,            o  AST limit (ASTLM) 30 (minimum)  C            o  Buffered I/O byte count quota (BYTLM) 4,096 (minimum)u  /      1-12 Preparing to Install the DECset Tools                  5               o  Open file limit (FILLM) 20 (minimum)D  +         1.5.6 Quotas and Privileges for MMS-  B               To use MMS, it is recommended that each account haveE               TMPMBX and NETMBX privileges and the following require-E               ments:  /               o  AST limit (ASTLM) 14 (minimum)   G               o  Buffered I/O byte count quota (BYTLM) 13,000 (minimum)   4               o  Open file limit (FILLM) 6 (minimum)  >               o  Subprocess creation quota (PRCLM) 2 (minimum)  /         1.6 OpenVMS License Management Facilityo  H               The OpenVMS License Management Facility (LMF) is available               withE               Version 1.5 (and higher) of the OpenVMS Alpha operatingnA               system and Version 5.5 or higher of the OpenVMS VAXsE               operating system. Before you install a DECset tool, youeG               must register your tool software license or an equivalent :               license such as the DECset software license.  H               The license registration information you need is containedD               in the Product Authorization Key (PAK) that is shippedA               with each tool. The PAK is a paper certificate that 5               contains information about the license.s  @               During the installation, you are asked if you haveD               registered the tool license and loaded the appropriateH               authorization key. You must register and load your licenseC               before you start the installation in order to run thesC               Installation Verification Procedure (IVP) and use thee               software.y  H               To register a license under OpenVMS Alpha, Version 1.5, orH               under OpenVMS VAX, Version 5.5, first log in to the systemF               manager's account, SYSTEM. You then have a choice of two/               ways to perform the registration:   E               o  Invoke the SYS$UPDATE:VMSLICENSE.COM procedure. When G                  it prompts you for information, respond with data from                   your PAK.  H                               Preparing to Install the DECset Tools 1-13    c            =            o  Enter the DCL command LICENSE REGISTER with the C               appropriate qualifiers that correspond to informatione               on the PAK.   =            For complete information on using the LMF, see the B            manual on the License Management Utility in the OpenVMS            documentation set._        1.7 Using VMSINSTAL  @            After you log in to a privileged account to install aA            DECset tool, set the default device to SYS$UPDATE: andlE            then invoke VMSINSTAL, the command procedure that installs <            this product. VMSINSTAL has the following format:  @            @SYS$UPDATE:VMSINSTAL toolmn device_name: [OPTIONS N]              tool_?            Represents the tool you are installing; for example, <            DECset. Note that the DECset kit has a collective@            installation procedure for the DECset components. The>            procedure will prompt you for which DECset tools to            install.               m<            Represents the version number of the tool you areB            installing; for example, 120 for Version 12.0. Refer toC            the DECset BIL or BOM for the version number of the tool             you are installing.              n@            Represents the maintenance update of the tool you are=            installing. Refer to the DECset BIL or BOM for thed1            maintenance update number of your kit._              device_nameB            Represents a device name on which you plan to mount theA            media. For example, SYS$SYSDEVICE:[KITS] is the devicem2            name used in examples in this document.              OPTIONS NC            Is an optional parameter you must provide if you want to D            be prompted to display or print the release notes. If youA            do not include the OPTIONS N parameter, VMSINSTAL doesa@            not prompt you to display or print the release notes.  /      1-14 Preparing to Install the DECset Tools)                 G               VMSINSTAL permits the use of several other options: A, G,iG               L, and R; for more information on these options, see your                 processor-specific,               installation/operations guide.  F               If you do not supply the first two parameters, VMSINSTALG               prompts you for the product and device names. If you want D               to be prompted for the product and device names and beG               prompted to display or print the release notes, enter the                 following command:  7               $ @SYS$UPDATE:VMSINSTAL OPTIONS N<Return>T  A               When you invoke VMSINSTAL, it checks the following:t  ?               o  Whether you logged in to a privileged account.lF                  Digital recommends that you install software from theF                  system manager's account with your default device and-                  directory set to SYS$UPDATE.P  C               o  Whether you have adequate quotas for installation.gA                  VMSINSTAL checks for the following quota values:S                    -  ASTLM = 24                    -  BIOLM = 18  "                  -  BYTLM = 32,768                    -  DIOLM = 18                    -  ENQLM = 30                    -  FILLM = 20  D               VMSINSTAL then checks whether the following conditionsF               exist. If so, discontinue the conditions before resuming)               the installation procedure.a  1               o  Whether DECnet is up and running   >               o  Whether any users are logged in to the system  G               If VMSINSTAL detects either of these conditions, you will H               be asked whether you want to continue the installation. IfE               you want to continue, type YES. If you want to stop the )               installation, press Return.,  H                               Preparing to Install the DECset Tools 1-15 e  z            A            You must register the information contained in the PAK B            that is shipped with DECset by using either the OpenVMSC            LICENSE command procedure (SYS$UPDATE:VMSLICENSE) or theeC            LICENSE REGISTER and LICENSE LOAD commands, as describeda<            in the OpenVMS License Management Utility Manual.                                                                                /      1-16 Preparing to Install the DECset Tools     m                  H                                                                        2H         ________________________________________________________________  H                                                Installing the DECset Kit      F               The purpose of the DECset installation procedure is two-H               fold: to provide the installer a single point of entry forF               installing any or all DECset components, and to minimize@               the need for user interaction during installation.  B               This collective procedure acts as a parent KITINSTALF               procedure to the individual component installations. TheF               procedure spawns off one subprocess per DECset componentH               with default instructions on how to install the respective               component.  C               The DECset installation procedure does the following:f  8               o  Queries for which components to install  C               o  Checks system resources required to perform serialB0                  installations of the components  E               o  Queries for responses to the questions asked as eachl'                  component is installed   C               o  Installs the selected DECset components one by one   H               Section 2.8 explains how to install the optional save setsD               that contain documentation for DECset. Please refer toH               the Online Documentation release notes for the contents of               these save sets.  !         2.1 Prerequisite Softwarel  H               To use the command-line interface, all DECset for OpenVMS,D               Version 12.0, components require OpenVMS VAX operating,               system, Version 5.5 or higher.  B               To use the DECwindows user interface, all DECset forD               OpenVMS, Version 12.0, components require both OpenVMS@               Alpha operating system, Version 1.5 or higher, and6               DECwindows Motif, Version 1.1 or higher.  H                                            Installing the DECset Kit 2-1    i            2      2.2 Accessing the DECset Online Release Notes  ;            DECset provides online release notes for all thef=            components when you invoke VMSINSTAL by specifying @            DECSET120. The prompt to display or print the release=            notes before installation appears in step 3 of thel@            installation procedure when you invoke VMSINSTAL with#            the OPTIONS N parameter.   D            To obtain the release notes after the installation, print            the following file:  +            SYS$HELP:DECSET120.RELEASE_NOTES   ,      2.3 Installation Procedure Requirements  D            Minimum free disk space, global pages, and global sectionE            requirements will depend on which components you choose tos4            install through the collective procedure.  @            DECset's requirements for free disk storage space are@            different during installation and after installation.A            Table 2-1 and Table 2-2 list the storage requirements.   @            Table 2-1 Disk Space Storage Requirements for OpenVMSE            __________Alpha_Systems___________________________________L  )                                    DuringtG            Kit_Component___________Installation______After_Installationn  ;            DECset complete kit     124,000           57,600o  <            DECset online           150,000           150,000E            documentation_kit_________________________________________u  D            Table 2-2 Disk Space Storage Requirements for OpenVMS VAXE            __________Systems_________________________________________   )                                    During G            Kit_Component___________Installation______After_Installatione  ;            DECset complete kit     85,800            37,800s  <            DECset online           150,000           150,000E            documentation_kit_________________________________________n  "      2-2 Installing the DECset Kit u  n            F                 ________________________Note  ________________________  B                 On systems with limited disk space, install two orD                 three DECset components then repeat the installationB                 procedure until you have installed the entire kit.D                 If you have all or part of DECset already installed,C                 your space requirements will be less. See Chapter 10B                 for individual component installation requirements>                 to calculate totals for system resource needs.  E                 _____________________________________________________   F               You will need 150,000 free blocks for the disk where youH               plan to copy the distribution kit. The 150,000 free blocks@               include the DECset online documentation save sets.  H               To install DECset you must be logged in to an account thatC               has the SETPRV privilege or the following privileges:_                 o  CMKRNLn                 o  WORLD                 o  SYSPRV_           2.4 Using VMSINSTAL_  A               After you log in to a privileged account to installnC               DECset, set the default directory to SYS$UPDATE. ThentD               invoke the VMSINSTAL command procedure to install thisG               product. An example of this procedure is shown in steps 1B#               and 2 of Section 2.6.4  G               The VMSINSTAL command procedure has the following syntax:   >               @SYS$UPDATE:VMSINSTAL DECSET120 ddn: [OPTIONS N]                 ddn:C               The name of the device where the distribution volumes8H               will be mounted for the DECset installation media. In thisE               format, dd is the device code and n is the unit number. A               You do not have to use the console drive to install H               DECset. If you do use the console drive, replace any mediaE               you removed from the drive. (The examples in this guide -               use MUA0: for the device name.).  H                                            Installing the DECset Kit 2-3    1                        OPTIONS N>            An optional parameter you provide if you want to beA            prompted to display or print the release notes. If yourB            omit the OPTIONS N parameter, VMSINSTAL does not prompt5            you to display or print the release notes.   B            If you omit the first two parameters, VMSINSTAL promptsB            you for the product and device names. If you want to beC            prompted for the product and device names and to display0:            or print the release notes, enter the following            DCL command:t  "            $ @SYS$UPDATE:VMSINSTAL                                                                "      2-4 Installing the DECset Kit u  L            ;               The VMSINSTAL procedure checks the following:T  C               o  Whether you are logged in to a privileged account. F                  Digital recommends that you install software from theD                  system manager account with your default device and-                  directory set to SYS$UPDATE.   C               o  Whether you have adequate quotas for installation.eG                  The VMSINSTAL procedure checks for the following quota)                  values:                       ASTLM = 18                     BIOLM = 20"                     BYTLM = 60,000                     DIOLM = 11                     ENQLM = 6d                     FILLM = 50$                     PGFLQUO = 30,000                     PRCLM = 18                     TQELM = 10                     WSDEF = 512(!                     WSQUO = 1,024t$                     WSEXTENT = 3,600  @                  The VMSINSTAL procedure then checks whether theC                  following conditions exist. If so, discontinue the G                  conditions before resuming the installation procedure.B  4                  -  Whether DECnet is up and running  A                  -  Whether any users are logged in to the system   A                  If VMSINSTAL detects either of these conditions,uD                  the procedure asks whether you want to continue theA                  installation. If you want to continue, enter YEStB                  and press the Return key. If you want to stop the,                  installation, press Return.  7         2.5 Preparing for DECset Component Installationo  B               Use the OpenVMS License Management Facility (LMF) toB               register your DECset component licenses. The licenseC               registration information you need is contained in the)B               Product Authorization Key (PAK) that is shipped withB               DECset. The PAK is a paper certificate that containsH               information about the license you have to load in order to  H                                            Installing the DECset Kit 2-5 r  I            C            run some of the DECset components. All DECset components1            require a license.i  %      2.6 Installing DECset Componentse  ?            This section contains excerpts from the installationf?            procedure and explains each step. Defaults appear inu@            brackets ([])  throughout the installation procedure.  A            To abort the installation procedure at any time, press(D            Ctrl/Y. When you press Ctrl/Y, the installation procedureD            deletes all the files it has created up to that point andB            then returns you to DCL level. If you want to retry theD            installation after pressing Ctrl/Y, you must proceed from            step 2.  >            Step 1: Log in to a privileged account and set your6            default device and directory to SYS$UPDATE.                 .                .)               . $            Username: SYSTEM <Return>            Password:  <Return>,            $ SET DEFAULT SYS$UPDATE <Return>    ;            Step 2: Invoking VMSINSTAL with a kit on CD-ROM.)  @            $ @VMSINSTAL DECSET120 SYS$SYSDEVICE:[KITS] OPTIONS N  E                  OpenVMS Software Product Installation Procedure Vn.n   &            It is 26-MAY-1995 at 09:00.:            Enter a question mark (?) at any time for help.  I            * Are you satisfied with the backup of your system disk [YES]?t  D            If you are satisfied with the backup of your system disk,E            press Return. Otherwise, enter NO and press the Return keye+            to discontinue the installation.         "      2-6 Installing the DECset Kit n  u            7               The following products will be processed:A                   DECset V12.0  A                   Beginning installation of DECset V12.0 at 09:03   C               %VMSINSTAL-I-RESTORE, Restoring product save-set A...sY               %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.t                  .                  .                  .  4               Step 3: Select a release notes option.  G               This step applies only if you specified OPTIONS N in stepf               2.  $               Release Notes Options:  *                   1. Display release notes(                   2. Print release notes!                   3. Both 1 and 253                   4. Copy release notes to SYS$HELP'A                   5. Do not display, print, or copy release notess  +               * Select option [2]: <Return>   D               If you select option 1, VMSINSTAL displays the releaseH               notes on line immediately. To terminate the display at any!               time, press Ctrl/C.   E               If you select option 2 (the default), VMSINSTAL prompts F               you for a queue name. You can then enter a queue name orG               press the Return key, which sends the file to the default "               output print device.  0               * Queue name [SYS$PRINT]: <Return>  D               If you select option 3, VMSINSTAL displays the releaseA               notes on line immediately. To terminate the displayr@               at any time, press Ctrl/C. The VMSINSTAL procedureC               prompts you for a queue name for printing the releasenB               notes. Either enter a queue name or press the Return>               key to send the file to the default output printA               device. The DECset release notes are then copied too/               SYS$HELP:DECSET120.RELEASE_NOTES.l  H               If you select option 4, VMSINSTAL copies the release notes&               to SYS$HELP immediately.  H                                            Installing the DECset Kit 2-7 D  e            E            If you select option 5, VMSINSTAL does not display, print, A            or copy the release notes, but moves them to SYS$HELP. E            Typically, you select this option when you want to end ther            installation.  9            Next, VMSINSTAL displays the following prompt:p  G            * Do you want to continue the installation [N]?: YES<Return>RE            %VMSINSTAL-I-RELMOVED, The product release notes have beenu.                successfully moved to SYS$HELP.  B            If you want to continue the installation, enter YES andC            press the Return key. If you enter NO (or press Return), C            VMSINSTAL discontinues the installation. In either case, 9            VMSINSTAL moves the release notes to SYS$HELP.   3            Step 4: Selecting components to install.e  D            Now you will get a menu selection to choose the component            you want to install.t                        .                      .                      .  F                      These are the options provided by this collective,                      installation procedure:  0                      - all the DECset components6                      - Language-Sensitive Editor (LSE)1                      - Source Code Analyzer (SCA) 3                      - Code Management System (CMS)m'                      - DEC Test Managero:                      - Performance Coverage Analyzer (PCA)5                      - Module Management System (MMS)   2                      Please choose your option(s):  D            You can either elect to choose all the options or you can+            select a combination of options.   ?              * Do you want all the DECset components [NO]?  YEStF              * Are you sure you want to install all the options [YES]?    "      2-8 Installing the DECset Kit i  a            F               For example, if you were to choose LSE, SCA, and CMS, it#               would look like this:s                          .                        .                        .G                 * Do you want Language-Sensitive Editor (LSE) [NO]? YESuB                 * Do you want Source Code Analyzer (SCA) [NO]? YESD                 * Do you want Code Management System (CMS) [NO]? YES4                 * Do you want DEC Test Manager [NO]?G                 * Do you want Performance Coverage Analyzer (PCA) [NO]?oB                 * Do you want Module Management System (MMS) [NO]?  ;                          These are the selections you made:e  ?                               - Language-Sensitive Editor (LSE) :                               - Source Code Analyzer (SCA)<                               - Code Management System (CMS)  L                 * Would you like a chance to select your options again [NO]?  C               You then need to answer the questions for each of theh7               DECset components that you have selected.   <         2.7 Running the Installation Verification Procedures  D               The Installation Verification Procedure (IVP) for eachG               DECset component checks the integrity of installed files.tD               We strongly urge you to run the IVPs after you installH               the components. Each component installation puts a commandD               procedure in SYS$TEST for you to invoke. The following3               list shows the DECset component IVPs:   H               __________________________________________________________H               Component_____________Procedure_Name______________________  .               ENVMGR                ENVMGR$IVP  +               CMS                   CMS$IVP_  +               DEC Test Manager      DTM$IVP   +               LSE                   LSE$IVP   +               MMS                   MMS$IVPu  +               PCA                   PCA$IVPi  H               SCA___________________SCA$IVP_____________________________  H                                            Installing the DECset Kit 2-9 u  g            <            The following example shows how to invoke the LSE            component IVP:r  "            $ @SYS$TEST:LSE$IVP.COM      3      2.8 Installing the DECset Online Documentationb  B            Many DECset components have online documentation files.?            The DECset kit provides separate save sets for these A            online documentation files allowing you to install the A            files independent of the DECset kit, and also provides @            an option to install the files on a device other thanA            the system disk. The DECset online documentation filese@            are provided by the save sets DECSETDOCS120.A throughE            DECSETDOCS120.F. The total number of free blocks needed toCD            install the online documentation files is 150,000 blocks.  C            To install the DECset online documentation files, invokei6            the VMSINSTAL command procedure as follows:  ?            @SYS$UPDATE:VMSINSTAL DECSETDOCS120 ddn: [OPTIONS N]s  B            For more information about the DECset online documenta-             tion, see Appendix B.                                      #      2-10 Installing the DECset KitV V  o                  H                                                                        3H         ________________________________________________________________  H                                Installing the DEC Code Management System      H               This chapter gives specific instructions on installing the/               DEC Code Management System (CMS).n  $         3.1 Preparing to Install CMS  D               Before installing CMS, Version 3.7, you must enter theD               CMS command VERIFY on all CMS pre-Version 3 libraries.F               To correct any problems displayed by the VERIFY command,E               enter the CMS command VERIFY/REPAIR. To use CMS VersionaD               3.7, you are required to convert any CMS pre-Version 3D               libraries. After CMS, Version 3.7 is installed, if youC               try to access a pre-Version 3 library you receive the                 following message:  Q               %CMS-E-CONVERTLIB, library is a pre-Version 3 library and cannot be -                       used without conversiong  F               After CMS, Version 3.7 is installed, use the CMS commandA               CONVERT LIBRARY to convert pre-Version 3 libraries.c  A               If you intend to use DEC Test Manager with CMS, seee               Section 3.3.  F                 ________________________Note  ________________________  =                 CMS release notes up to and including Version A                 3.7 can be found in SYS$HELP:CMSvvu.RELEASE_NOTESSB                 (where vv represents the major version number, andA                 u represents the update number). Also, the dollaroE                 sign ($)  was included in the release notes format in05                 Versions 3.1, 3.2, 3.3, and 3.4 only.   E                 ______________________________________________________    H                            Installing the DEC Code Management System 3-1 f  O            .      3.1.1 Installation Procedure Requirements  A            The installation takes approximately 10 to 45 minutes, D            depending on the type of media and your system configura-C            tion. Before installing CMS, you must have the following $            privileges and resources:  =            o  SETPRV privileges, or CMKRNL, WORLD, and SYSPRV_               privileges  A            o  A minimum of 9,000 blocks of free disk space during                installation;_7               7,000 blocks are used after installation.s  E            o  A minimum of 1,500 free global pages, plus the size (intJ               number of disk blocks) of the file SYS$LIBRARY:DCLTABLES.EXE               at installation.  C            o  A minimum of 14 free global sections at installation.   A            o  The minimum number of OpenVMS classes necessary for A               full functionality as described in the CMS Software (               Product Description (SPD).  B            These resources reflect the amount of space needed when>            installing the CMS DECwindows interface and the CMS            software.  +      3.2 User Account Quotas and Privilegess  E            To use CMS, each account must have a minimum of TMPMBX andoD            NETMBX privileges and the following minimum requirements:  %            o  AST limit (ASTLM) of 14   =            o  Buffered I/O byte count quota (BYTLM) of 14,000   (            o  Enqueue quota (ENQLM) of 1  *            o  Open file limit (FILLM) of 6  2            o  Timer queue entry limit (TQELM) of 1      2      3-2 Installing the DEC Code Management System                 &         3.3 Using CMS with Other Tools  H               The DECset Environment Manager is installed as part of theG               installation of the CMS component. The DECset Environment "               Manager consists of:  C               o  Run-time component used by DECset layered products                  o  DCL interface  %               o  DECwindows interfaced  G               The DCL and DECwindows interface components are optional.   J               DEC Test Manager requires the CMS files SYS$SHARE:CMSSHR.EXE?               and CMSPROSHR.EXE. Correct installation of CMS is D               necessary in order to use it with DEC Test Manager. BeC               aware that whenever you install or reinstall CMS (foraD               example, as the result of an incorrect installation orG               upgrading to a higher version of CMS), you will also need ,               to reinstall DEC Test Manager.  F                 ________________________Note  ________________________  @                 The file CMSPROSHR.EXE is no longer used by CMS,C                 and may not be supported in future versions of CMS. A                 CMSPROSHR.EXE is included in the CMS installationp4                 procedure only because it is used by!                 DEC Test Manager.o  E                 _____________________________________________________            3.4 Installing CMS  B               This section contains excerpts from the installationB               procedure and explains each step. Defaults appear in=               brackets throughout the installation procedure.   D               To abort the installation procedure at any time, pressG               Ctrl/Y. When you press Ctrl/Y, the installation procedure C               deletes all files it has created up to that point and F               then returns you to DCL level. To retry the installationC               procedure after pressing Ctrl/Y, proceed from step 2.     H                            Installing the DEC Code Management System 3-3 v  d            >            Step 1: Log in to a privileged account and set your6            default device and directory to SYS$UPDATE.  
      <Return>   %            Username: SYSTEM  <Return>L            Password: <Return>L,            $ SET DEFAULT SYS$UPDATE <Return>  $            Step 2: Invoke VMSINSTAL.  7            $ @VMSINSTAL CMS037 MUA0: OPTIONS N <Return>   E                  OpenVMS Software Product Installation Procedure Vn.n   &            It is dd-mmm-yyyy at hh:mm.:            Enter a question mark (?) at any time for help.  V            * Are you satisfied with the backup of your system disk [YES]? YES <Return>  D            If you are satisfied with the backup of your system disk,B            enter YES and press the Return key. Otherwise, enter NO<            and press Return to discontinue the installation.  <            Step 3: Insert the first installation kit volume.  =            Please mount the first volume of the set on MUA0:.t(            * Are you ready? YES <Return>4            The following products will be processed:                CMS V3.7   :                Beginning installation of CMS V3.7 at hh:mm  @            %VMSINSTAL-I-RESTORE, Restoring product save-set A...  B            To indicate that you want to continue the installation,>            mount volume 1, enter YES and press the Return key.  B            Step 4: Insert the subsequent installation kit volumes.  D            %BACKUP-I-READYREAD, mount volume 2 on _MUA0: for reading  /            Enter "YES" when ready: YES <Return>   A            The VMSINSTAL procedure prompts you to insert the next D            volume and waits for you to enter YES after inserting it.E            If you enter NO, VMSINSTAL displays the prompt again. This E            prompt is displayed only if your installation kit containst             more than one volume.  2      3-4 Installing the DEC Code Management System                 4               Step 5: Select a release notes option.  G               This step applies only if you specified OPTIONS N in stepk               2.  $               Release Notes Options:  *                   1. Display release notes(                   2. Print release notes!                   3. Both 1 and 2o&                   4. None of the above  +               * Select option [2]: <Return>   D               If you select option 1, VMSINSTAL displays the releaseF               notes on line immediately. You can terminate the display-               at any time by pressing Ctrl/C.   G               If you select option 2, VMSINSTAL prompts you for a queue.H               name. Either enter a queue name or press the Return key to:               send the file to the default output printer.  0               * Queue name [SYS$PRINT]: <Return>  D               If you select option 3, VMSINSTAL displays the releaseH               notes on line immediately and then prompts you for a queueE               name. Either enter a queue name or press the Return key-E               to send the file to the default output printer. The CMSrH               release notes are then copied to SYS$HELP:CMS$037.RELEASE_               NOTES.  C               If you select option 4, VMSINSTAL does not display or C               print the release notes, but copies them to SYS$HELP. @               Typically, you select this option to terminate the               installation.   <               Next, VMSINSTAL displays the following prompt:  K               * Do you want to continue the installation [NO]? YES <Return>EW               %VMSINSTAL-I-RELMOVED, The product's release notes have been successfully.                moved to SYS$HELP.  F                 ________________________Note  ________________________  @                 The release notes file installed by VMSINSTAL isA                 labeled with the current product name and versione  H                            Installing the DEC Code Management System 3-5 e  s            <               number (for example, CMS037). Take care not to@               delete release notes for previous versions of CMS.  C               _____________________________________________________   /            Step 6: Select installation options.   P            * Do you want to install the interface components [YES]? YES <Return>;            * Do you also wish to install the CMS DECwindowsn(            interface [YES]? YES <Return>Q            * Do you also wish to install the Server for CMS Client for Windows? -h              [YES]? YES <Return>Y            * Do you want to purge files replaced by this installation [YES]? YES <Return>h  >            The directories SYS$HELP, SYS$MANAGER, SYS$MESSAGE,?            SYS$SHARE, SYS$SYSTEM, SYS$STARTUP, and SYS$TEST mayRB            contain previous versions of CMS files. These files are?            replaced during the installation with new files, but A            the old files are not automatically purged. Purging isL@            recommended. In response to the purging prompt, press?            Return to purge the files, or enter NO to keep them.   ;            Step 7: Respond to license registration queries.a  ?            CMS supports the OpenVMS License Management Facilitye=            (LMF). The installation procedure displays licenseSC            information about your product and then asks if you haveaE            registered and loaded your product authorization key (PAK) D            for CMS. The following is an example of such information:              Product:       CMSo            Producer:      DEC,            Version:       3.7e%            Release Date:  dd-mmm-yyyyE  O            * Does this product have an authorization key registered and loaded?   >            If you have not registered and loaded your PAK, youB            must answer NO to this question. You must then stop theE            installation, register and load your PAK, and then restarte?            the installation. If you answer YES and you have notHE            registered and loaded your PAK, you are asked if you woulda@            like to complete the installation without running theB            Installation Verification Procedure (IVP). However, theE            next time you invoke CMS, you receive a message indicating 8            that you are not licensed to run the product.  2      3-6 Installing the DEC Code Management System c  o            8               You are then asked the following question:  U               * Do you want to run the IVP after the installation [YES]? YES <Return>p  B               The IVP runs tests to check whether the installationE               procedure was successful. If the installation procedure A               determines that you have insufficient quotas to runcE               the IVP, it tells you which quotas need to be increasedCE               and asks if you would like to complete the installationPH               without running the IVP. Press Return to run the IVP afterH               the installation. If you do not want to run the IVP, enter+               NO in response to the prompt.   6               Step 8: Read the informational messages.  A               The CMS installation procedure produces a number ofOG               informational messages that report on the progress of the H               installation. The success of the installation is indicated'               by the following message:e  M               %VMSINSTAL-I-MOVEFILES, files will now be moved to their target                directories...  B               If the installation procedure is successful, the new@               or modified files are moved to their target direc-?               tories. In addition, the SYS$HELP:HELPLIB.HLB and H               SYS$LIBRARY:DCLTABLES.EXE files are updated to include theH               new versions of the CMS help text and the CMS command-line               definition.   G               This installation will add or modify the following files:   0                  DECW$SYSTEM_DEFAULTS:CMS$DW.UID9                  DECW$SYSTEM_DEFAULTS:CMS$DW_DEFAULTS.DATE)                  SYS$HELP:CMS$DW_HELP.HLBC.                  SYS$HELP:CMS037.RELEASE_NOTES%                  SYS$HELP:HELPLIB.HLB -                  SYS$HELP:CMS_V37_COMMANDS.PS .                  SYS$HELP:CMS_V37_COMMANDS.TXT-                  SYS$HELP:CMS_V37_MESSAGES.PSh.                  SYS$HELP:CMS_V37_MESSAGES.TXT1                  SYS$HELP:CMS_V37_CALLROUTINES.PSV2                  SYS$HELP:CMS_V37_CALLROUTINES.TXT#                  SYS$MSG:CMSMSG.EXE /                  SYS$SHARE:CMS$EVENT_ACTION.EXEn(                  SYS$SHARE:CMSPROSHR.EXE%                  SYS$SHARE:CMSSHR.EXEa  H                            Installing the DEC Code Management System 3-7 s  c            %               SYS$SHARE:DCLTABLES.EXE )               SYS$STARTUP:CMS$STARTUP.COMt#               SYS$SYSTEM:CMS$DW.EXE                 SYS$SYSTEM:CMS.EXE"               SYS$TEST:CMS$IVP.COM-               VUE$LIBRARY:CMS$PROFILE.VUE$DATr-               VUE$LIBRARY:CMS$VUE_STARTUP.COMN  E            If you entered YES in response to the prompt that requests$E            a file purge in step 6, previous versions of the CMS filesS            are now purged.  C            Step 9: Observe the Installation Verification Procedure.   E            If you chose to run the IVP in step 7, VMSINSTAL now calls_A            the IVP to verify that CMS was successfully installed:   E            %CMS-I-IVPBEGIN, Begin Installation Verification Procedurel                   .h                   .                    .IA            %CMS-I-IVPEND, End Installation Verification Proceduren  3            Step 10: End the installation procedure.E  9               Installation of CMS V3.7 completed at hh:mmT  /               VMSINSTAL procedure done at hh:mm               $ LOGOUT <Return>;            SYSTEM     logged out at dd-mmm-yyyy hh:mm:ss.ssn  C            When the product installation procedure is complete, yout@            can choose to install more products or to log out (asA            shown here). If you removed any media from the consoletD            drive before beginning the installation, you must replace            it now.  D            The VMSINSTAL procedure deletes or changes entries in theD            process symbol tables during the installation. Therefore,B            if you are going to continue using the system manager'sB            account and you want to restore these symbols, you must$            log out and log in again.    2      3-8 Installing the DEC Code Management System e  p            ,         3.4.1 Installing CMS on a VAXcluster  G               If you want to run CMS on multiple nodes of a VAXcluster, G               first check to see that you have the appropriate software_E               license. Then, follow these steps after installing CMS:   G               1. Enter the LICENSE LOAD command to activate the license E                  on each node in the VAXcluster on which CMS is to be -                  executed as described in the ;                  OpenVMS License Management Utility Manual.n  D               2. Run SYS$STARTUP:CMS$STARTUP.COM on each node of theF                  cluster that has a software license. In addition, youC                  must add the following line to your system startupm9                  procedure, SYS$MANAGER:SYSTARTUP_V5.COM:y  /                  $ @SYS$STARTUP:CMS$STARTUP.COM   E                  To use the product on other nodes in the VAXcluster, G                  you must replace the version of the DCL tables that is E                  installed on the other VAXcluster nodes. To do this, -                  perform the following steps:   4                  a. Log in to a node on the cluster.  B                  b. Enter the following command at the DCL prompt:  H                     $ INSTALL REPLACE SYS$LIBRARY:DCLTABLES.EXE <Return>  F                  c. Repeat steps a and b for each node of the cluster.  @               See Chapter 9 for information on post installation               procedures.M                        H                            Installing the DEC Code Management System 3-9 E  _                  H                                                                        4H         ________________________________________________________________  H                             Installing the DEC Language-Sensitive Editor      D               This chapter explains how to install the DEC Language-%               Sensitive Editor (LSE).   /         4.1 Installation Procedure Requirementsn  A               LSE, Version 4.3 requires the OpenVMS VAX operatingeD               system, Version 5.5 or higher, OpenVMS Alpha operatingB               system, Version 1.5 or higher, and DECwindows Motif,F               Version 1.1. See the SPD for this product for additionalE               information about required and optional software. Also,VH               see the SPD for information about required OpenVMS classes               and tailoring.  H               The DECset Environment Manager is installed as part of theG               installation of the LSE component. The DECset Environment "               Manager consists of:  C               o  Run-time component used by DECset layered productsY                 o  DCL interface  %               o  DECwindows interfacef  G               The DCL and DECwindows interface components are optional.b  C               The installation takes approximately 5 to 30 minutes,aG               depending on the type of media and your system configura-.F               tion. Before installing LSE, you must have the following'               privileges and resources:i  @               o  SETPRV privileges, or CMKRNL, WORLD, and SYSPRV                  privileges.  E               o  A minimum of 40,000 blocks of free disk space during C                  the installation; 13,500 blocks of free disk space H                  after the installation of LSE. Approximately 300 blocksE                  of free disk space should be added to the disk space   H                         Installing the DEC Language-Sensitive Editor 4-1    i            E               after installation for each language that you choose to $               have supported by LSE.  3            o  A minimum of 2 MB of physical memory.g  E            o  A minimum of 6,000 free global pages, plus the size (inpJ               number of disk blocks) of the file SYS$LIBRARY:DCLTABLES.EXEE               at installation, For most efficient operation, you will D               need a total of 6,000 free global pages, plus the size>               of SYS$LIBRARY:DCLTABLES.EXE after installation.  C            o  A minimum of 15 free global sections at installation;H=               12 global sections are used after installation.l  C               ________________________Note ________________________e  @               You must ensure that your system has the necessaryB               global page and global section SYSGEN quotas for the@               installation. Failure to do so could cause the DCL8               tables to be corrupted in some situations.  C               ______________________________________________________  -      4.1.1 User Account Quotas and PrivilegesR  ?            To use LSE, each account must have TMPMBX and NETMBXs5            privileges and the following requirements:M  ,            o  AST quota (ASTLM) 24 (minimum)  5            o  Buffered I/O limit (BIOLM) 18 (minimum)   C            o  Buffered I/O byte count quota (BYTLM) 4,096 (minimum)_  3            o  Direct I/O limit (DIOLM) 18 (minimum)l  0            o  Enqueue quota (ENQLM) 30 (minimum)  2            o  Open file quota (FILLM) 20 (minimum)  B            o  Paging file quota (PGFLQUOTA) 20,000 pages (minimum)  @               A paging file quota (PGFLQUOTA) of 40,000 pages is>               recommended if you are using the REPORT command.  ;            o  Subprocess creation quota (PRCLM) 5 (minimum)   C            o  Working set size (WSDEF) 1,024 pages (minimum); 2,048h&               to 4,096 pages (optimum)  5      4-2 Installing the DEC Language-Sensitive Editorr ,  o            B               A FILLM of 20 is appropriate for a typical LSE usageC               pattern and allows LSE to exhibit full functionality.pF               It may be necessary to grant higher FILLM quotas to userC               accounts where LSE is frequently used to edit a largeuF               number of files simultaneously. Buffer-change journalingE               causes user accounts to consume increased quantities ofIE               FILLM. One buffer-change journal file is maintained forwH               each editing buffer. For example, 30 user buffers that are=               journaled require a total of 30 units of FILLM.h  D               The items in the following list all require additional?               units of FILLM. This list is provided to help youe0               determine your FILLM requirements.  ,               o  Buffer-change journal files                 o  SCA databases  4               o  Reading and writing of source files  7               o  Diagnostic file for the REVIEW commandn  %               o  Keystroke journaling   E               o  Image activation of other tools, such as Source CodetD                  Analyzer (SCA) and DEC Code Management System (CMS)  F               Use the OpenVMS Authorize Utility (AUTHORIZE) to compareF               the current values of these quotas with the requirementsE               for LSE. For example, the account used in the followingd,               example is the SYSTEM account:  /               $ SET DEFAULT SYS$SYSTEM <Return> &               $ RUN AUTHORIZE <Return>'               UAF> SHOW SYSTEM <Return>E  C               To change the values of these quotas, use the OpenVMSuG               Authorize Utility's MODIFY command. For more information,oC               see the OpenVMS System Management Utilities Reference A               Manual. After you log in to a privileged account tolG               install LSE, invoke VMSINSTAL, the command procedure that D               installs this product. An example of this procedure is4               shown in steps 1 and 2 of Section 4.2.  G               The VMSINSTAL command procedure has the following syntax:k  >               $ @SYS$UPDATE:VMSINSTAL LSE04n ddcu: [OPTIONS N]  H                         Installing the DEC Language-Sensitive Editor 4-3 s                           nE            Represents the maintenance update of LSE. Refer to the la-t            bel on the E            LSE distribution kit or LSE BOM for the maintenance update E            number of your kit. You can also enter an asterisk (*)  in E            place of LSE04n. If you are installing from magnetic tape,sB            you can use the asterisk to save installation time; theE            asterisk causes LSE to be installed with a minimum of tape             passes.              ddcu:B            Represents a device name where the distribution volumesC            will be mounted for the LSE installation media, where dd A            is the device code, c is the controller code, and u is B            the unit number. It is not necessary to use the consoleE            drive to install LSE. If you do use the console drive, yourE            should replace any media you removed from the drive. MUA0:S=            is the device name used in examples in this guide.4              OPTIONS N=            Is an optional parameter you should provide if youm>            want to be prompted to display or print the release@            notes. If you do not include the OPTIONS N parameter,@            VMSINSTAL does not prompt you to display or print the=            release notes. The VMSINSTAL procedure permits the =            use of several other options. For more informationv<            on the other options, see your processor-specific)            installation/operations guide._  C            If you do not supply the first two parameters, VMSINSTALlD            prompts you for the product and device names. If you wishA            to be prompted for the product and device names and tooB            display or print the release notes, enter the following            command:   +            $ @SYS$UPDATE:VMSINSTAL <Return>n  >            When you invoke VMSINSTAL, it checks the following:  <            o  Whether you logged in to a privileged account.C               Digital recommends that you install software from thehC               system manager's account with your default device andw*               directory set to SYS$UPDATE.    5      4-4 Installing the DEC Language-Sensitive Editorw    i            C               o  Whether you have adequate quotas for installation.>G                  The VMSINSTAL procedure checks for the following quotaY                  values:                    -  ASTLM = 24                    -  BIOLM = 18  "                  -  BYTLM = 18,000                    -  DIOLM = 18                    -  ENQLM = 30                    -  FILLM = 20  G               The VMSINSTAL procedure then checks whether the followingsH               conditions exist. If so, discontinue the conditions before2               resuming the installation procedure.  1               o  Whether DECnet is up and running   >               o  Whether any users are logged in to the system  G               If VMSINSTAL detects either of these conditions, you willMH               be asked whether you want to continue the installation. IfF               you want to continue, enter YES. If you want to stop the1               installation, press the Return key.            4.2 Installing LSE  B               This section contains excerpts from the installationB               procedure and explains each step. Defaults appear in=               brackets throughout the installation procedure.u  D               To abort the installation procedure at any time, pressG               Ctrl/Y. When you press Ctrl/Y, the installation procedure C               deletes all files it has created up to that point andgE               then returns you to DCL level. If you want to retry the.D               installation procedure after pressing Ctrl/Y, you must"               proceed from step 2.        H                         Installing the DEC Language-Sensitive Editor 4-5 a  t            >            Step 1: Log in to a privileged account and set your6            default device and directory to SYS$UPDATE.  
      <Return>i  %            Username: SYSTEM  <Return>s%            Password:         <Return>   E                Last interactive login on Wednesday,  6-JUL-1994 15:47o  ,            $ SET DEFAULT SYS$UPDATE <Return>  $            Step 2: Invoke VMSINSTAL.  7            $ @VMSINSTAL LSE043 MUA0: OPTIONS N <Return>h  E                  OpenVMS Software Product Installation Procedure Vn.no  &            It is dd-mmm-yyyy at hh:mm.:            Enter a question mark (?) at any time for help.  R            * Are you satisfied with the backup of your system disk [YES]? <Return>  D            If you are satisfied with the backup of your system disk,E            press Return. Otherwise, enter NO and press the Return key +            to discontinue the installation.   <            Step 3: Insert the first installation kit volume.  =            Please mount the first volume of the set on MUA0:.l(            * Are you ready? YES <Return>4            The following products will be processed:                LSE V4.3   P            Beginning installation of DEC Language-Sensitive Editor V4.3 at hh:mm  @            %VMSINSTAL-I-RESTORE, Restoring product save-set A...  B            To indicate that you want to continue the installation,?            mount volume 1, enter YES, and press the Return key.w  B            Step 4: Insert the subsequent installation kit volumes.  D            %BACKUP-I-READYREAD, mount volume 2 on _MUA0: for reading  .            Enter "YES" when ready: YES<Return>  5      4-6 Installing the DEC Language-Sensitive Editorp x  n            D               The VMSINSTAL procedure prompts you to insert the nextG               volume and waits for you to enter YES after inserting it.TH               If you enter NO, VMSINSTAL displays the prompt again. ThisH               prompt is displayed only if your installation kit contains#               more than one volume.   6               Step 5: Install LSE source files option.  C               The installation procedure prompts you if you wish to H               install LSE source files. These files occupy approximately%               15,000 blocks of space.H  4               Step 6: Select a release notes option.  G               This step applies only if you specified OPTIONS N in step                2.  U                   Release notes included with this kit are always copied to SYS$HELP.C  3                   Additional Release Notes Options:   *                   1. Display release notes(                   2. Print release notes!                   3. Both 1 and 2T&                   4. None of the above  +               * Select option [2]: <Return>   D               If you select option 1, VMSINSTAL displays the releaseF               notes on line immediately. You can terminate the display%               at any time by pressingp               Ctrl/C.   G               If you select option 2, VMSINSTAL prompts you for a queue H               name. Either enter a queue name or press the Return key to?               send the file to the default output print device.7  0               * Queue name [SYS$PRINT]: <Return>  D               If you select option 3, VMSINSTAL displays the releaseF               notes on line immediately. You can terminate the displayE               at any time by pressing Ctrl/C. The VMSINSTAL procedurelE               then prompts you for a queue name. Either enter a queueiB               name or press the Return key to send the file to theD               default output print device. The LSE release notes are;               then copied to SYS$HELP:LSE043.RELEASE_NOTES.d  H                         Installing the DEC Language-Sensitive Editor 4-7    p            ?            If you select option 4, VMSINSTAL neither prints nor @            displays the release notes. The LSE release notes are3            copied to SYS$HELP:LSE043.RELEASE_NOTES.   C               ________________________Note ________________________u  A               This version of the release notes file installed bys@               VMSINSTAL is labeled with the current product nameA               and version number. Take care not to delete releasew1               notes for previous versions of LSE.l  C               _____________________________________________________n  9            Next, VMSINSTAL displays the following prompt:   H            * Do you want to continue the installation [N]?: YES <Return>R            %VMSINSTAL-I-RELMOVED, The product release notes have been successfully!                moved to SYS$HELP.l  B            If you want to continue the installation, enter YES andA            press the Return key. If you enter NO or press Return,aC            VMSINSTAL discontinues the installation. In either case,e9            VMSINSTAL moves the release notes to SYS$HELP.e  /            Step 7: Select installation options.n  P            * Do you want to install the interface components [YES]? YES <Return>Y            * Do you also wish to install the LSE DECwindows interface [YES]? YES <Return>sU            * Do you want to purge files replaced by this installation [YES]? <Return>   <            The directories SYS$EXAMPLES, SYS$TEST, SYS$HELP,>            SYS$LIBRARY, SYS$MESSAGE, SYS$STARTUP, VUE$LIBRARY,D            LSE$EXAMPLE, and SYS$SYSTEM may contain previous versions<            of LSE files. These files are replaced during theA            installation with new files, but the old files are notaD            automatically purged. Purging is recommended. In responseD            to the purging prompt, press Return to purge the files or!            enter NO to keep them.t  N            * Do you want to run the IVP after the installation [YES]? <Return>  =            The Installation Verification Procedure (IVP) runs <            tests to check whether the installation procedure@            was successful. Press Return to run the IVP after theD            installation. If you do not want to run the IVP, enter NO%            in response to the prompt._  5      4-8 Installing the DEC Language-Sensitive Editor_                 >               Step 8: Respond to license registration queries.  B               LSE supports the OpenVMS License Management Facility@               (LMF). The installation procedure displays licenseF               information about your product and then asks if you haveH               registered and loaded your product authorization key (PAK)G               for LSE. The following is an example of such information:C                  Product:       LSE                Producer:      DEC                Version:       4.3(               Release Date:  dd-mmm-yyyy  R               * Does this product have an authorization key registered and loaded?  F               If you have not registered and loaded your PAK, you mustG               answer NO to this question. You have to register and loadoD               your PAK to successfully complete the installation. IfE               you have not done so, you should stop the installation, >               register and load your PAK, and then restart the               installation.h  .               Step 9: Select language support.  F               Templates for some languages are shipped in the LSE kit.B               The installation procedure displays the names of theB               language templates that are available in the LSE kitD               and then asks which ones should be installed. LanguageG               templates for other layered products that support LSE notpF               mentioned in this installation procedure are provided in?               the installation kits for those layered products.   X               Language templates for VAX Ada, BASIC, BLISS, C, C++, COBOL, DCL, FORTRAN,V               MACRO, Pascal and PL/I as well as templates for the LSE command languageV               are included in this kit. Templates for other languages that support LSES               and are not mentioned are provided in the installation kits for thosep               languages.  V               Please choose the languages for which you would like to install support:  S               * Do you want to install language support for VAX ADA [YES]? <Return>AU               * Do you want to install language support for VAX BASIC [YES]? <Return> U               * Do you want to install language support for VAX BLISS [YES]? <Return>fQ               * Do you want to install language support for VAX C [YES]? <Return>e  H                         Installing the DEC Language-Sensitive Editor 4-9 f               R            * Do you want to install language support for VAX COBOL [YES]? <Return>P            * Do you want to install language support for VAX DCL [YES]? <Return>T            * Do you want to install language support for VAX FORTRAN [YES]? <Return>R            * Do you want to install language support for VAX MACRO [YES]? <Return>S            * Do you want to install language support for VAX PASCAL [YES]? <Return>UP            * Do you want to install language support for VAX PLI [YES]? <Return>P            * Do you want to install language support for DEC LSE [YES]? <Return>Q            * Do you want to install language support for DEC PLSE [YES]? <Return>L  0            Step 10: Read informational messages.  >            The LSE installation procedure produces a number of@            informational messages that report on the progress of            the installation.  >            The success of the installation is indicated by the            following message:(  S      %VMSINSTAL-I-MOVEFILES, files will now be moved to their target directories...   B            If the installation procedure is successful, the new or@            modified files are moved to their target directories.                                              6      4-10 Installing the DEC Language-Sensitive Editor I  a            D               The SYS$HELP:HELPLIB.HLB and SYS$LIBRARY:DCLTABLES.EXEF               files are updated to include the new versions of the LSE?               HELP text and the LSEDIT command-line definition:y  F               This installation added or modified the following files:  /                       SYS$LIBRARY:DCLTABLES.EXE +                       SYS$SYSTEM:LSEDIT.EXEf,                       SYS$LIBRARY:LSESHR.EXE,                       SYS$MESSAGE:LSEMSG.EXE0                       SYS$LIBRARY:LSE$CCTSHR.EXE1                       SYS$LIBRARY:LSE$DECWSHR.EXEb2                       SYS$LIBRARY:PSE$COMMENTS.EXE2                       SYS$LIBRARY:LSE$DEFAULTS.DAT<                       SYS$LIBRARY:LSE$SYSTEM_ENVIRONMENT.ENV9                       SYS$LIBRARY:LSE$SECTION.TPU$SECTIONp1                       SYS$LIBRARY:LSE$WIDGETS.UIDF/                       SYS$LIBRARY:LSE$DEBUG.TPUn+                       SYS$HELP:LSE$HELP.HLBb+                       SYS$HELP:LSE$MENU.HLBo-                       SYS$HELP:LSE$KEYPAD.HLBi.                       SYS$HELP:LSE$CLIHELP.HLB1                       SYS$STARTUP:LSE$STARTUP.COMvC                       SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$USER.DIA G                       SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$USER.EXAMPLEMH                       SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$USER2.EXAMPLEH                       SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$USER3.EXAMPLE*                       SYS$TEST:LSE$IVP.COM:                       SYS$SYSROOT:[SYSTEST.LSE]LSE$IVP.TPUK                       SYS$SYSROOT:[VUE$LIBRARY.USER]LSE$EDIT_QUALIFIERS.EXE H                       SYS$SYSROOT:[VUE$LIBRARY.USER]LSE$EDIT_OPTIONS.UID@                       SYS$SYSROOT:[VUE$LIBRARY.USER]LSE$EDIT.COMG                       SYS$SYSROOT:[VUE$LIBRARY.USER]LSE$PROFILE.VUE$DAT   H               If you entered YES in response to the prompt that requestsH               a file purge at step 7, previous versions of the LSE files               are now purged.   G               Step 11: Observe the Installation Verification Procedure.   H               If you chose to run the IVP in step 7, VMSINSTAL now callsD               the IVP to verify that LSE was installed successfully:  ?               ?? lines written to file DEV$:[USER]LSE$IVP.LIS;1   ?               DEC Language-Sensitive Editor IVP was successful.   H                        Installing the DEC Language-Sensitive Editor 4-11                 3            Step 12: End the installation procedure.L  S               Installation of DEC Language-Sensitive Editor V4.3 completed at hh:mmn  /               VMSINSTAL procedure done at hh:mmy              $ LOGOUT <Return>;            SYSTEM     logged out at dd-mmm-yyyy hh:mm:ss.ssi  C            When the product installation procedure is complete, youi@            can choose to install more products or to log out (asA            shown here). If you removed any media from the consolew>            drive before beginning the installation, you should            replace it now.  D            The VMSINSTAL procedure deletes or changes entries in theD            process symbol tables during the installation. Therefore,B            if you are going to continue using the system manager'sD            account and you want to restore these symbols, you should$            log out and log in again.  '      4.3 Installing LSE on a VAXclustera  D            If you want to run LSE on multiple nodes of a VAXcluster,D            first check to see that you have the appropriate softwareB            license. Then, follow these steps after installing LSE:  D            1. Enter the LICENSE LOAD command to activate the licenseB               on each node in the VAXcluster on which LSE is to beE               executed as described in the OpenVMS License Management                Utility Manual.o  A            2. Run SYS$STARTUP:LSE$STARTUP.COM on each node of thes2               cluster that has a software license.  B               To ensure that LSE is installed each time the system<               is bootstrapped, include the following line in*               SYS$STARTUP:SYSTARTUP_V6.COM/               (the site-specific startup file):L  *               @SYS$STARTUP:LSE$STARTUP.COM  B            3. To use the product on other nodes in the VAXcluster,D               you must replace the version of the DCL tables that isB               installed on the other VAXcluster nodes. To do this,*               perform the following steps:  1               a. Log in to a node on the cluster.h  6      4-12 Installing the DEC Language-Sensitive Editor                 F                  b. Run INSTALL and enter the following command at the$                     INSTALL> prompt:  G                     INSTALL> REPLACE SYS$LIBRARY:DCLTABLES.EXE <Return>   F                  c. Repeat steps a and b for each node of the cluster.  "         4.4 After the Installation  G               LSE is now installed and can be invoked by all users with !               the LSEDIT command.t  G               The installation procedure modifies the DCL command tablecE               so that the LSEDIT command is recognized and processed. D               However, the previous command table is still in effectH               for those users who are currently logged in. All logged-inF               users who want to use the LSEDIT command must log out of*               the system and log in again.  @               You must take steps to ensure that the LSE startupE               command procedure is executed at system bootstrap time. C               If your site is using the STARTUP facility, enter thefD               proper STARTUP ADD command to execute LSE$STARTUP.COM.D               If the STARTUP facility is not used at your site, editC               SYS$MANAGER:SYSTARTUP_V6.COM to include the followinga               line:   *               @SYS$STARTUP:LSE$STARTUP.COM  F                 ________________________Note  ________________________  @                 The command procedure that should be executed atA                 system bootstrap time to make the LSE executablese=                 known images now resides in SYS$STARTUP. Make >                 sure that upon completion of the installation,;                 the file specification in the site-specifico=                 startup command procedure used to execute then?                 LSE startup command procedure is modified to bem,                 SYS$STARTUP:LSE$STARTUP.COM.  E                 _____________________________________________________J  C               You can use LSE to read and compose messages from the E               MAIL Utility. You can define the logical name MAIL$EDITOC               as CALLABLE_LSE in order to use the editor from MAIL.lD               Note that LSE must be installed as a known image. This  H                        Installing the DEC Language-Sensitive Editor 4-13 s  s            ?            is accomplished through the editor's startup command @            procedure. Also, the DEC Code Management System (CMS)>            and Source Code Analyzer (SCA) must be installed as?            known images to be used from LSE when LSE is invokedrA            from the MAIL Utility. (See Chapter 5 for instructions             on installing SCA.)                                                                              6      4-14 Installing the DEC Language-Sensitive Editor    g                  H                                                                        5H         ________________________________________________________________  H                                      Installing the Source Code Analyzer      B               This chapter explains how to install the Source Code               Analyzer (SCA).   /         5.1 Installation Procedure Requirements:  H               The DECset Environment Manager is installed as part of theG               installation of the SCA component. The DECset Environment "               Manager consists of:  C               o  Run-time component used by DECset layered productse                 o  DCL interface  %               o  DECwindows interfacey  G               The DCL and DECwindows interface components are optional.s  G               The installation of SCA, Version 4.3, takes approximately F               5 to 40 minutes, depending on the type of media and yourH               system configuration. Before installing SCA, you must have5               the following privileges and resources:   @               o  SETPRV privileges, or CMKRNL, WORLD, and SYSPRV                  privileges.  E               o  A minimum of 13,000 blocks of free disk space during H                  installation; 9,000 blocks are used after installation.  6               o  A minimum of 2 MB of physical memory.  H               o  A minimum of 5,000 free global pages, plus the size (inM                  number of disk blocks) of the file SYS$LIBRARY:DCLTABLES.EXE H                  at installation. For most efficient operation, you willG                  need a total of 5,000 free global pages, plus the size A                  of SYS$LIBRARY:DCLTABLES.EXE after installation.l  F               o  A minimum of 15 free global sections at installation;@                  12 global sections are used after installation.  H                                  Installing the Source Code Analyzer 5-1                 +      5.2 User Account Quotas and Privileges7  ?            To use SCA, each account must have TMPMBX and NETMBX 5            privileges and the following requirements:e  ,            o  AST limit (ASTLM) 24 (minimum)  5            o  Buffered I/O quota (BIOLM) 18 (minimum)e  D            o  Buffered I/O byte count quota (BYTLM) 18,000 (minimum)  3            o  Direct I/O quota (DIOLM) 18 (minimum)a  0            o  Enqueue quota (ENQLM) 30 (minimum)  2            o  Open file limit (FILLM) 20 (minimum)  B            o  Paging file quota (PGFLQUOTA) 20,000 pages (minimum)  ;            o  Subprocess creation quota (PRCLM) 2 (minimum)e  9            o  Timer queue entry limit (TQELM) 5 (minimum)e  A            o  Working set size (WSDEF) 600 pages (minimum); 3,000e               pages (optimum)t  C            Use the OpenVMS Authorize Utility (AUTHORIZE) to compare C            the current values of these quotas with the requirements B            for SCA. For example, the account used in the following)            example is the SYSTEM account:n  ,            $ SET DEFAULT SYS$SYSTEM <Return>#            $ RUN AUTHORIZE <Return> $            UAF> SHOW SYSTEM <Return>  @            To change the values of these quotas, use the OpenVMSD            Authorize Utility's MODIFY command. For more information,@            see the OpenVMS System Management Utilities Reference            Manual.         5.3 SCA Server Installation  C            SCA provides a server that allows remote users to accessYD            your local SCA libraries. The installation of this server            is optional.s  E            You will be prompted during the installation as to whetherdD            you would like to install both the SCA server and the SCAD            client, or whether you would like to install only the SCA            client.  ,      5-2 Installing the Source Code Analyzer    p            G               If you elect to install only the SCA client, remote userswF               will not be able to access your local SCA libraries. SCAH               users on your local system will not be affected. They willF               have the ability to use local libraries and libraries onC               remote nodes where the SCA server has been installed.M  G               If you elect to install the optional SCA server, accountspF               named SCA$SERVER and SCA$DEFAULT are created for the SCAB               server. The accounts are given the following quotas:  E         Username: SCA$SERVER                       Owner:  SCA SERVERhS         Account:  DECNET                           UIC:    [370,355] ([SCA$SERVER]) D         CLI:      DCL                              Tables: DCLTABLES,         Default:  SYS$SYSDEVICE:[SCA$SERVER]-         LGICMD:   SYS$SYSTEM:SCA$SERVER_LOGINo(         Login Flags:  Dismail Restricted  +         Primary days:   Mon Tue Wed Thu Fria3         Secondary days:                     Sat Sun N         Primary   000000000011111111112222  Secondary 000000000011111111112222N         Day Hours 012345678901234567890123  Day Hours 012345678901234567890123N         Network:  ##### Full access ######            ##### Full access ######N         Batch:    -----  No access  ------            -----  No access  ------N         Local:    -----  No access  ------            -----  No access  ------N         Dialup:   -----  No access  ------            -----  No access  ------N         Remote:   -----  No access  ------            -----  No access  ------L         Expiration:            (none)    Pwdminimum:  8   Login Fails:     0C         Pwdlifetime:        180 00:00    Pwdchange:   (pre-expired)tN         Last Login:            (none) (interactive),  (none) (non-interactive)A         Maxjobs:         0  Fillm:       300  Bytlm:        32767 A         Maxacctjobs:     0  Shrfillm:      0  Pbytlm:           0 A         Maxdetach:       0  BIOlm:       120  JTquota:       1024 A         Prclm:          15  DIOlm:       120  WSdef:         1024 A         Prio:            4  ASTlm:       120  WSquo:         2232 A         Queprio:         0  TQElm:        10  WSextent:      4464uA         CPU:        (none)  Enqlm:       200  Pgflquo:      20480          Authorized Privileges:           TMPMBX         Default Privileges:e           TMPMBX          H                                  Installing the Source Code Analyzer 5-3 n  s            ;      Username: SCA$DEFAULT                      Owner:  SCArQ      Account:  DECNET                           UIC:    [371,345] ([SCA$DEFAULT])eA      CLI:      DCL                              Tables: DCLTABLESe#      Default:  SYS$SYSDEVICE:[USER]a      LGICMD:   LOGIN"      Login Flags:  Dismail Captive(      Primary days:   Mon Tue Wed Thu Fri0      Secondary days:                     Sat SunK      Primary   000000000011111111112222  Secondary 000000000011111111112222 K      Day Hours 012345678901234567890123  Day Hours 012345678901234567890123tK      Network:  -----  No access  ------            -----  No access  ------oK      Batch:    -----  No access  ------            -----  No access  ------ K      Local:    -----  No access  ------            -----  No access  ------ K      Dialup:   -----  No access  ------            -----  No access  ------uK      Remote:   -----  No access  ------            -----  No access  ------YI      Expiration:            (none)    Pwdminimum:  8   Login Fails:     0 @      Pwdlifetime:        180 00:00    Pwdchange:   (pre-expired)K      Last Login:            (none) (interactive),  (none) (non-interactive)t>      Maxjobs:         0  Fillm:         0  Bytlm:            0>      Maxacctjobs:     0  Shrfillm:      0  Pbytlm:           0>      Maxdetach:       0  BIOlm:         0  JTquota:       1024>      Prclm:           0  DIOlm:         0  WSdef:         1024>      Prio:            4  ASTlm:         0  WSquo:            1>      Queprio:         0  TQElm:        10  WSextent:         1>      CPU:        (none)  Enqlm:         0  Pgflquo:          0      Authorized Privileges:>      Default Privileges:  B            In addition, an access control list (ACL) is set on the            filenA            SYS$SYSTEM:NETPROXY.DAT, giving the SCA$SERVER accountS#            read and execute access.   D            If any problems occur at run time, the SCA server creates>            an error log file in SYS$SPECIFIC:[SCA$SERVER]. One?            possible error is server failure due to insufficientaE            virtual memory. If this occurs frequently, you may want toS7            increase PGFLQUO for the SCA$SERVER account.d  E            If you are reinstalling SCA, stop any previous SCA servers A            (network processes named SCA$SERVER_nnnn) so that theyeC            will be restarted using the new server code. Use the DCLt+            commands SHOW SYSTEM/NETWORK and -            STOP/IDENTIFICATION, respectively.L  ,      5-4 Installing the Source Code Analyzer    e                     5.4 Installing SCA  B               This section contains excerpts from the installationB               procedure and explains each step. Defaults appear in=               brackets throughout the installation procedure.X  D               To abort the installation procedure at any time, pressG               Ctrl/Y. When you press Ctrl/Y, the installation procedure C               deletes all files it has created up to that point andYE               then returns you to DCL level. If you want to retry theND               installation procedure after pressing Ctrl/Y, you must"               proceed from step 2.  A               Step 1: Log in to a privileged account and set yourT9               default device and directory to SYS$UPDATE.            <Return>  (               Username: SYSTEM  <Return>(               Password:         <Return>/               $ SET DEFAULT SYS$UPDATE <Return>   '               Step 2: Invoke VMSINSTAL.   :               $ @VMSINSTAL SCA043 MUA0: OPTIONS N <Return>  H                     OpenVMS Software Product Installation Procedure Vn.n  )               It is dd-mmm-yyyy at hh:mm.$=               Enter a question mark (?) at any time for help.   U               * Are you satisfied with the backup of your system disk [YES]? <Return>O  G               If you are satisfied with the backup of your system disk,EH               press Return. Otherwise, enter NO and press the Return key.               to discontinue the installation.  ?               Step 3: Insert the first installation kit volume.B  @               Please mount the first volume of the set on MUA0:.+               * Are you ready? YES <Return> 7               The following products will be processed:   -                 DEC Source Code Analyzer V4.3   R                   Beginning installation of DEC Source Code Analyzer V4.3 at hh:mm  C               %VMSINSTAL-I-RESTORE, Restoring product save-set A...O  H                                  Installing the Source Code Analyzer 5-5 t  u            B            To indicate that you want to continue the installation,?            mount volume 1, enter YES, and press the Return key.t  1            Step 4: Select a release notes option.   D            This step applies only if you specified OPTIONS N in stepD            2. 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]: <Return>  A            If you select option 1, VMSINSTAL displays the releaseeB            notes immediately. You can terminate the display at any            time by pressings            Ctrl/C.  D            If you select option 2, VMSINSTAL prompts you for a queueE            name. Either type a queue name or press Return to send thee3            file to the default output print device.e  -            * Queue name [SYS$PRINT]: <Return>t  A            If you select option 3, VMSINSTAL displays the releasehB            notes immediately. You can terminate the display at any            time by pressing A            Ctrl/C. The VMSINSTAL procedure then prompts you for asD            queue name. Either enter a queue name or press the ReturnC            key to send the file to the default output print device.o  ?            If you select option 4, VMSINSTAL neither prints norn@            displays the release notes. The SCA release notes are3            copied to SYS$HELP:SCA043.RELEASE_NOTES.u  C               ________________________Note ________________________O  A               This version of the release notes file installed by @               VMSINSTAL is labeled with the current product nameA               and version number. Take care not to delete releases1               notes for previous versions of SCA.   C               _____________________________________________________   ,      5-6 Installing the Source Code Analyzer t  p            <               Next, VMSINSTAL displays the following prompt:  K               * Do you want to continue the installation [N]?: YES <Return> U               %VMSINSTAL-I-RELMOVED, The product release notes have been successfullyo$                   moved to SYS$HELP.  E               If you want to continue the installation, enter YES andnD               press the Return key. If you enter NO or press Return,F               VMSINSTAL discontinues the installation. In either case,<               VMSINSTAL moves the release notes to SYS$HELP.  E               Step 5: Insert the subsequent installation kit volumes.e  G               %BACKUP-I-READYREAD, mount volume 2 on _MUA0: for readings  2               Enter "YES" when ready: YES <Return>  D               The VMSINSTAL procedure prompts you to insert the nextG               volume and waits for you to enter YES after inserting it.mH               If you enter NO, VMSINSTAL displays the prompt again. ThisH               prompt is displayed only if your installation kit contains#               more than one volume.   2               Step 6: Select installation options.  E         * Do you want to continue the installation [NO]? YES <Return>ud         %VMSINSTAL-I-RELMOVED, The product's release notes have been successfully moved to SYS$HELP.  Q                   Please indicate the components of SCA that you wish to install:   4                       1 - Both SCA client and server)                       2 - SCA client onlyP  W         * Enter the number corresponding to the SCA components to install [1]: <Return>   O         The DECset Environment Manager is installed as part of the installationw!         of this DECset component.   3         The DECset Environment Manager consists of:   =         A run-time component used by DECset layered products,          a DCL interface, and         a DECwindows interface.   A         The DCL and DECwindows interface components are optional.   M         * Do you want to install the interface components [YES]? YES <Return> R         * Do you want to purge files replaced by this installation [YES]? <Return>  H                                  Installing the Source Code Analyzer 5-7                 D            If you elect to install only the SCA client, remote usersC            will not be able to access your local SCA libraries. SCA_E            users on your local system will not be affected. They willnC            have the ability to use local libraries and libraries oni@            remote nodes where the SCA server has been installed.  C            The files in SYS$SYSTEM and SYS$LIBRARY contain previous A            versions of SCA files. These files are replaced duringnE            the installation with new files, but the old files are not D            automatically purged. Purging is recommended. In responseD            to the purging prompt, press Return to purge the files orC            enter NO to keep them. The system HELP files are updated             in either case.  C            Step 7: Choosing the Installation Verification Procedurer            (IVP) options.t  ?            The IVP runs tests to check whether the installation C            procedure was successful. There are two parts to the SCAvE            IVP: one that tests the character-cell version of SCA, and D            one that tests the DECwindows version. If you want to runD            the character cell or both parts of the IVP, press Return0            in response the following IVP prompt:  J            * Do you want to run the IVP after installation [YES]? <Return>  >            Entering YES to this prompt causes the following to            appear:  N            The IVP has two sections, a character cell section and a DECwindowsM            section. In order for the DECwindows section to run correctly, theeM            logical name DECW$DISPLAY must be appropriately set (using the SEToL            DISPLAY command). If at this time you are not prepared to run theK            DECwindows portion of the IVP, enter NO at the following prompt.l  >            You can rerun the IVP later by issuing the command:              @SYS$TEST:SCA$IVP  4            * Do you wish to run the whole IVP [YES]?  C            If you do not want to run the DECwindows part of the IVP ?            because, for example, you do not have an appropriate >            display device, enter NO to the previous prompt. It>            is highly recommended that you run the IVP not onlyA            to verify that the installation succeeded, but also to0C            set up a sample SCA library and to have the logical nameoE            SCA$EXAMPLE refer to that library. The installation placesg  ,      5-8 Installing the Source Code Analyzer m               E               the necessary files in the sample directory and the IVPaG               creates the sample SCA library in that directory. The IVPaD               also sets up an example library for the program designH               facility (PDF), referred to by the logical name SCA$2167A.H               If you choose not to run the IVP, enter NO at the previousC               prompt. You can run the IVP after the installation by -               entering the following command:   )               $ @SYS$TEST:SCA$IVP<Return>d                                                                        H                                  Installing the Source Code Analyzer 5-9                 ;            Step 8: Respond to license registration queries.)  ?            SCA supports the OpenVMS License Management FacilityM=            (LMF). The installation procedure displays license C            information about your product and then asks if you have E            registered and loaded your product authorization key (PAK)fD            for SCA. The following is an example of such information:              Product:       LSEm            Producer:      DECu            Version:       4.3m%            Release Date:  dd-mmm-yyyyS  O            * Does this product have an authorization key registered and loaded?t  C            If you have not registered and loaded your PAK, you mustr?            answer NO to this question. You have to register andrA            load your PAK in order to run the IVP. If you have notaE            registered the product, the installation may be completed;tE            however, Digital recommends you register and load your PAK -            and then restart the installation.t  &            Step 9: Server Installation  C            If you install the SCA server, two accounts are created:e&            SCA$SERVER and SCA$DEFAULT.  D            The server code itself runs under the SCA$SERVER account.A            This account has no special privileges, but is granted E            access to all SCA library directories by an access control D            list (ACL) that is added when libraries are created. ThisC            installation also grants READ and EXECUTE access for the @            SCA$SERVER account to the NETPROXY database, which it?            uses to verify remote users' access to SCA librariessA            where the server is running. The image executed by the D            SCA server, SCA$SERVER_MAIN, is installed with SYSPRV and            SYSNAM privileges.y  A            This installation defines the SCA$SERVER object in themB            network database. A password for the SCA$SERVER account>            is automatically generated and added to the NetworkB            Control Program (NCP) database. If you decide to changeB            the SCA$SERVER account password in the future, you mustD            remember to update the SCA$SERVER object password also by            using NCP.e  -      5-10 Installing the Source Code Analyzer  $  V            >               Another account, SCA$DEFAULT, is created by thisE               installation to grant access to remote users who do not F               have proxy access to the local node. This account has no!               special privileges.                                                                                   H                                 Installing the Source Code Analyzer 5-11                 C            Both these accounts must have unique User Identification0B            Codes (UICs). You are prompted to enter information for6            these accounts as in the following example:  N               In order to grant access to remote users who do not have a proxyN               account for the local node, SCA creates the SCA$DEFAULT account,N               which is used as a default proxy account for SCA library access.  5               This account has no special privileges.   H                  You must specify a unique UIC for this account in order=                  to ensure proper security of your libraries.a  S               SCA generates a long password for this account that is hard to guess.   N            * Enter UIC for SCA$DEFAULT account (include brackets) [[371,345]]:6            %SCA-I-CREACC, Creating account SCA$DEFAULTK            %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named             SCA$DEFAULT.l8            %UAF-I-ADDMSG, user record successfully addedQ            %UAF-I-RDBADDMSGU, identifier SCA$DEFAULT value: [000371,000345] added             to rights database A            %SCA-I-MODACC, Modifying account SCA$DEFAULT quotas... K            %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT namedh            SCA$DEFAULT. 1            %UAF-I-MDFYMSG, user record(s) updated K            %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named             SCA$DEFAULT. 1            %UAF-I-MDFYMSG, user record(s) updated   I               In order to ensure that the SCA server runs with the proper1P               quotas, this installation procedure will create an account for theM               server. This account, SCA$SERVER, has no special privileges andn3               is set up only for network operation.e  O               You must specify a unique UIC for this account in order to ensure0J               proper security of your libraries. The SCA server account isN               automatically granted access to each library created, via Access               Control Lists.  P            SCA generates a long password for this account that is hard to guess.  P            If you want to change the name of this account after the installationO            has completed, you must also change the password in the NCP databases;            with the SET OBJECT SCA$SERVER PASSWORD command.   -      5-12 Installing the Source Code Analyzer     n            P               * Enter UIC for SCA$SERVER account (include brackets) [[370,355]]:K               %SCA-I-CREACC, Creating account SCA$SERVER for the SCA servernN               %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named               SCA$SERVER.S;               %UAF-I-ADDMSG, user record successfully added V               %UAF-I-RDBADDMSGU, identifier SCA$SERVER value: [000370,000355] added to               rights data baseM               %VMSINSTAL-I-SYSDIR, This product creates system disk directory )               SYS$SYSDEVICE:[SCA$SERVER]. N               %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named               SCA$SERVER. 4               %UAF-I-MDFYMSG, user record(s) updatedC               %SCA-I-MODACC, Modifying account SCA$SERVER quotas... N               %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named               SCA$SERVER. 4               %UAF-I-MDFYMSG, user record(s) updatedN               %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named               SCA$SERVER.a4               %UAF-I-MDFYMSG, user record(s) updated  K                 The network object SCA$SERVER has been defined. If you wish F                 to view this, run SYS$SYSTEM:NCP and enter the command6                       NCP> LIST OBJECT SCA$SERVER CHAR  7               Step 10: Read the informational messages.e  A               The SCA installation procedure produces a number of C               informational messages that report on the progress ofh               the installation:   S         %SCA-I-NOMORQST, No further questions will be asked during the installationo>         %VMSINSTAL-I-RESTORE, Restoring product save-set B ...c         %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSTEST.SCA$IVP]. Y         %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.SCA].eI         %CREATE-I-EXISTS, VMI$COMMON:[SYSHLP.EXAMPLES.SCA] already existshK         %CREATE-I-EXISTS, VMI$SPECIFIC:[SYSHLP.EXAMPLES.SCA] already exists.  P             If you intend to execute this layered product on other nodes in yourO             VAXcluster, and you have the appropriate software license, you musttP             prepare the system-specific roots on the other nodes by entering theQ             following command on each node (using a suitably privileged account):   >         $ CREATE /DIRECTORY SYS$SPECIFIC:[SYSHLP.EXAMPLES.SCA]a         %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.SCA.EXAMPLE].4S         %CREATE-I-EXISTS, VMI$SPECIFIC:[SYSHLP.EXAMPLES.SCA.EXAMPLE] already existso  H                                 Installing the Source Code Analyzer 5-13 n               M          If you intend to execute this layered product on other nodes in yourcL          VAXcluster, and you have the appropriate software license, you mustM          prepare the system-specific roots on the other nodes by entering theeN          following command on each node (using a suitably privileged account):  C      $ CREATE /DIRECTORY SYS$SPECIFIC:[SYSHLP.EXAMPLES.SCA.EXAMPLE] \      %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.SCA.2167A].N      %CREATE-I-EXISTS, VMI$SPECIFIC:[SYSHLP.EXAMPLES.SCA.2167A] already exists  M          If you intend to execute this layered product on other nodes in yourlL          VAXcluster, and you have the appropriate software license, you mustM          prepare the system-specific roots on the other nodes by entering theIN          following command on each node (using a suitably privileged account):  A      $ CREATE /DIRECTORY SYS$SPECIFIC:[SYSHLP.EXAMPLES.SCA.2167A]mb      %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.SCA.UNSUPPORTED].T      %CREATE-I-EXISTS, VMI$SPECIFIC:[SYSHLP.EXAMPLES.SCA.UNSUPPORTED] already exists  M          If you intend to execute this layered product on other nodes in your L          VAXcluster, and you have the appropriate software license, you mustL          prepare the system-specific roots on the other nodes by issuing theN          following command on each node (using a suitably privileged account):  H       $ CREATE /DIRECTORY SYS$SPECIFIC:[SYSHLP.EXAMPLES.SCA.UNSUPPORTED]i      %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.SCA.UNSUPPORTED.RECOMP]. T      %CREATE-I-EXISTS, VMI$SPECIFIC:[SYSHLP.EXAMPLES.SCA.UNSUPPORTED.RECOMP] already      exists.  M          If you intend to execute this layered product on other nodes in yourfL          VAXcluster, and you have the appropriate software license, you mustL          prepare the system-specific roots on the other nodes by issuing theN          following command on each node (using a suitably privileged account):  O       $ CREATE /DIRECTORY SYS$SPECIFIC:[SYSHLP.EXAMPLES.SCA.UNSUPPORTED.RECOMP]   T      *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  K              Upon completion of this installation, please do the following:   K              - If this installation is being done on a cluster, you must doA?                      @SYS$STARTUP:SCA$STARTUP.COM on all nodes.N  =              - Be sure to edit the system startup file to add_1                      @SYS$STARTUP:SCA$STARTUP.COMe  T      *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *S      %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...   -      5-14 Installing the Source Code Analyzer                  H               If the installation procedure is successful, the following:               files are moved to their target directories:  *               o  SYS$LIBRARY:SCA$SHARE.EXE  (               o  SYS$SYSTEM:SCA$MAIN.EXE  .               o  SYS$LIBRARY:SCA$PRO_SHARE.EXE  (               o  SYS$SYSTEM:SCA$DECW.EXE  $               o  SYS$LIBRARY:SCA.UID  /               o  SYS$LIBRARY:SCA$CONVERTLIB.EXE   -               o  SYS$MESSAGE:SCA$MESSAGES.EXE   ,               o  SYS$STARTUP:SCA$STARTUP.COM  H               If the installation procedure is successful and the serverG               is installed, the following files are moved to its target.               directory:  0               o  SYS$SYSTEM:SCA$SERVER_LOGIN.COM  /               o  SYS$SYSTEM:SCA$SERVER_MAIN.EXEn  F               In addition, the file SYS$HELP:HELPLIB.HLB is updated toC               contain the new DCL level SCA help, and the followingeA               files containing the SCA internal help and context-t)               sensitive help are created:S  &               o  SYS$HELP:SCA$HELP.HLB  .               o  SYS$HELP:SCA$NEUTRAL_HELP.HLB  &               o  SYS$HELP:SCA$MENU.HLB  K               The release notes are also copied to SYS$HELP:SCA043.RELEASE_ B               NOTES. The SYS$LIBRARY:DCLTABLES.EXE file is updated@               to include the new version of the SCA command-line               definition.H  @               In addition, the installation procedure creates or+               modifies the following files:   B            SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.EXAMPLE]BUILDTABLE.ANA  @            SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.EXAMPLE]BUILDTABLE.C  @            SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.EXAMPLE]COPYFILE.ANA  H                                 Installing the Source Code Analyzer 5-15 t                 ;         SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.EXAMPLE]COPYFILE.Ce  A         SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.EXAMPLE]DESIGN_EXAMPLE.C,  C         SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.EXAMPLE]DESIGN_EXAMPLE.ANAs  A         SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.EXAMPLE]EXPANDSTRING.ANAa  ?         SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.EXAMPLE]EXPANDSTRING.Cw  <         SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.EXAMPLE]OPENFILES.H  =         SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.EXAMPLE]TRANSLIT.ANAn  ;         SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.EXAMPLE]TRANSLIT.Ca  ?         SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.EXAMPLE]TYPE_EXAMPLE.Co  ?         SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.EXAMPLE]TYPE_EXAMPLE.Hc  A         SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.EXAMPLE]TYPE_EXAMPLE.ANAt  8         SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.EXAMPLE]TYPES.H  B         SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.2167A]2167A_APPENDIX.SDML  >         SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.2167A]2167A_DATA.SDML  D         SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.2167A]2167A_DATA_FILES.SDML  @         SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.2167A]2167A_DESIGN.SDML  ?         SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.2167A]2167A_FRONT.SDMLt  ?         SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.2167A]2167A_NOTES.SDML   E         SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.2167A]2167A_PRELIMINARY.SDML   @         SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.2167A]2167A_PROFILE.RNO  A         SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.2167A]2167A_PROFILE.SDMLn  D         SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.2167A]2167A_REFERENCED.SDML  F         SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.2167A]2167A_REQUIREMENTS.SDML  >         SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.2167A]2167A_SCOPE.RNO  ?         SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.2167A]2167A_SCOPE.SDMLr  :         SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.2167A]TR1_ADA.ADA  :         SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.2167A]TR1_ADA.ANA  :         SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.2167A]TR2_ADA.ADA  :         SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.2167A]TR2_ADA.ANA  ;         SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.2167A]TR3_ADA_.ADAc  ;         SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.2167A]TR3_ADA_.ANAt  @         SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.UNSUPPORTED.RECOMP]LM.H  -      5-16 Installing the Source Code Analyzerh E                 E            SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.UNSUPPORTED.RECOMP]LM.OBJ   H            SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.UNSUPPORTED.RECOMP]PSE_STR.H  C            SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.UNSUPPORTED.RECOMP]PSE_             STR.OBJ  G            SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.UNSUPPORTED.RECOMP]RECOMP.C   I            SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.UNSUPPORTED.RECOMP]RECOMP.EXEx  G            SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.UNSUPPORTED.RECOMP]RECOMP.H   F            SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.UNSUPPORTED.RECOMP]RECOMP_            LINK.COM   -            SYS$LIBRARY:SCA$QUERY_CALLABLE.ADA   -            SYS$LIBRARY:SCA$QUERY_CALLABLE.BASa  -            SYS$LIBRARY:SCA$QUERY_CALLABLE.FORE  +            SYS$LIBRARY:SCA$QUERY_CALLABLE.Hp  -            SYS$LIBRARY:SCA$QUERY_CALLABLE.MARl  -            SYS$LIBRARY:SCA$QUERY_CALLABLE.PASs  -            SYS$LIBRARY:SCA$QUERY_CALLABLE.PLI   -            SYS$LIBRARY:SCA$QUERY_CALLABLE.R32t  -            SYS$LIBRARY:SCA$QUERY_CALLABLE.SDIa  -            SYS$LIBRARY:SCA$QUERY_CALLABLE.TPU   2            SYS$LIBRARY:SCA$REPORT_2167A_DESIGN.TPU  4            SYS$LIBRARY:SCA$REPORT_CUSTOMIZATIONS.TPU  ,            SYS$LIBRARY:SCA$REPORT_FORMAT.TPU  5            SYS$LIBRARY:SCA$REPORT_FORMAT_DOCUMENT.TPU   3            SYS$LIBRARY:SCA$REPORT_FORMAT_RUNOFF.TPU   1            SYS$LIBRARY:SCA$REPORT_FORMAT_TEXT.TPU   -            SYS$LIBRARY:SCA$REPORT_GLOBALS.TPU   *            SYS$LIBRARY:SCA$REPORT_HELP.TPU  /            SYS$LIBRARY:SCA$REPORT_INTERNALS.TPU   ,            SYS$LIBRARY:SCA$REPORT_OUTPUT.TPU  -            SYS$LIBRARY:SCA$REPORT_PACKAGE.TPUi  5            SYS$LIBRARY:SCA$REPORT_PORTABLE_SYNTAX.TPUa  /            SYS$LIBRARY:SCA$REPORT_UTILITIES.TPUa  H                                 Installing the Source Code Analyzer 5-17 o  d              +         SYS$LIBRARY:SCA$REPORT_VALIDATE.TPU            SYS$HELP:SCACOMMANDS.PS             SYS$HELP:SCACOMMANDS.TXT            SYS$HELP:SCA$VAX_VMS.TXT           SYS$TEST:SCA$IVP.COM  *         SYS$TEST:[SCA$IVP]SCA$IVP_TEST.COM  *         SYS$TEST:[SCA$IVP]SCA$IVP_TEST.LIS  A            If the server is installed, the installation procedurer3            creates or modifies the following files:a  +               SYS$SYSTEM:NETNODE_REMOTE.DAT   &               SYS$SYSTEM:NETOBJECT.DAT  %               SYS$SYSTEM:NETPROXY.DAT   '               SYS$SYSTEM:RIGHTSLIST.DATa  #               SYS$SYSTEM:SYSUAF.DATi  D            Step 11: Observe the Installation Verification Procedure.  E            If you chose to run the IVP in step 7, VMSINSTAL now calls A            the IVP to verify that SCA was installed successfully. =            If you answered YES to running the entire IVP, theo@            DECwindows portion requires user action. The SCA mainD            window appears on the screen. Use the mouse to choose theA            Exit menu option from the File pull-down menu. The IVPA            then continues.  C            Additionally, the following files are created by the IVPE0            for the SCA and PDF sample libraries:  D            o  SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.EXAMPLE]SCA$EVENT.DAT  B            o  SYS$SYSROOT:[SYSHLP.EXAMPLES.SCA.2167A]SCA$EVENT.DAT  @            Also, if you typed YES in response to the prompt thatD            requests a file purge, previous versions of SCA files are            now purged.  -      5-18 Installing the Source Code Analyzer  t  k            6               Step 12: End the installation procedure.  L                  Installation of Source Code Analyzer 4.3 completed at hh:mm  2                  VMSINSTAL procedure done at hh:mm                 $ LOGOUT <Return>e>               SYSTEM     logged out at dd-mmm-yyyy hh:mm:ss.ss  F               When the product installation procedure is complete, youC               can choose to install more products or to log out (asSD               shown here). If you removed any media from the consoleA               drive before beginning the installation, you shouldo               replace it now.a  G               The VMSINSTAL procedure deletes or changes entries in the G               process symbol tables during the installation. Therefore, E               if you are going to continue using the system manager's E               account and you want to restore these symbols, you must '               log out and log in again.t  ,         5.4.1 Installing SCA on a VAXcluster  G               If you want to run SCA on multiple nodes of a VAXcluster,oG               first check to see that you have the appropriate softwareeE               license. Then, follow these steps after installing SCA:a  G               1. Enter the LICENSE LOAD command to activate the licensetE                  on each node in the VAXcluster on which SCA is to beq-                  executed as described in the ;                  OpenVMS License Management Utility Manual.   D               2. Run SYS$STARTUP:SCA$STARTUP.COM on each node of the5                  cluster that has a software license.n  E                  To ensure that SCA is installed each time the systemS?                  is bootstrapped, include the following line ine-                  SYS$STARTUP:SYSTARTUP_V6.COMl2                  (the site-specific startup file):  -                  @SYS$STARTUP:SCA$STARTUP.COMS        H                                 Installing the Source Code Analyzer 5-19 %  -            B            3. To use the product on other nodes in the VAXcluster,D               you must replace the version of the DCL tables that isB               installed on the other VAXcluster nodes. To do this,*               perform the following steps:  1               a. Log in to a node on the cluster.   C               b. Run INSTALL and enter the following command at ther!                  INSTALL> prompt:   D                  INSTALL> REPLACE SYS$LIBRARY:DCLTABLES.EXE <Return>  C               c. Repeat steps a and b for each node of the cluster.V                                                                -      5-20 Installing the Source Code Analyzeru s  i                  H                                                                        6H         ________________________________________________________________  H                                          Installing the DEC Test Manager      H               This chapter explains how to install the DEC Test Manager.  /         6.1 Installation Procedure Requirementsi  H               The DECset Environment Manager is installed as part of theH               installation of the DEC Test Manager component. The DECset.               Environment Manager consists of:  C               o  Run-time component used by DECset layered products                  o  DCL interface  %               o  DECwindows interfaceS  G               The DCL and DECwindows interface components are optional.   F               The installation of DEC Test Manager, Version 3.6, takesF               approximately 10 to 20 minutes, depending on the type ofH               media and your system configuration. Before installing DECF               Test Manager, you must have the following privileges and               resources:  @               o  SETPRV privileges, or CMKRNL, WORLD, and SYSPRV                  privileges.  >               o  A minimum of 15,000 blocks of free disk spaceB                  during installation; 10,000 blocks are used after                  installation.  F               o  A minimum of 800 free global pages, plus the size (inM                  number of disk blocks) of the file SYS$LIBRARY:DCLTABLES.EXERH                  at installation. For most efficient operation, you willH                  need a total of 800 free global pages, plus the size of>                  SYS$LIBRARY:DCLTABLES.EXE after installation.  F               o  A minimum of 15 free global sections at installation;@                  12 global sections are used after installation.  H                                      Installing the DEC Test Manager 6-1                 A            o  The minimum number of OpenVMS classes necessary fortE               full functionality as described in the DEC Test Managere               SPD.    +      6.2 User Account Quotas and Privilegesn  E            To use DEC Test Manager, each account must have TMPMBX andtD            NETMBX privileges and the following minimum requirements:  &            o  AST limit (ASTLM) of 100  =            o  Buffered I/O byte count quota (BYTLM) of 60,000V  )            o  Enqueue quota (ENQLM) of 10c  *            o  Open file limit (FILLM) of 9  4            o  Subprocess creation quota (PRCLM) of 4  C               ________________________Note ________________________P  =               DECwindows testing may require quotas for othere(               applications being tested.  C               _____________________________________________________i  @            A minimum required page file quota for using DEC Test>            Manager varies depending upon the application underD            test. If you encounter unexplained exceeded quota errors,C            increase your page file quota. One approach to determineSB            an appropriate value is to set the page file quota highB            (90,000 or more) and decrease it until the threshold at3            which the problem occurs is encountered.   C            Use the OpenVMS Authorize Utility (AUTHORIZE) to compare C            the current values of these quotas with the requirementsnE            for DEC Test Manager. For example, the account used in then3            following example is the SYSTEM account:o  #            $ SET DEFAULT SYS$SYSTEM             $ RUN AUTHORIZE            UAF> SHOW SYSTEM   @            To change the values of these quotas, use the OpenVMSD            Authorize Utility's MODIFY command. For more information,@            see the OpenVMS System Management Utilities Reference            Manual.  (      6-2 Installing the DEC Test Manager                 "         6.2.1 Special Requirements  G               The executable file SYS$LIBRARY:DECW$TERMINALSHR.EXE must D               be installed with the /OPEN and /SHARE qualifiers. DECE               Test Manager does this automatically during the startuph               procedure.  '         6.3 Installing DEC Test ManagerO  B               This section contains excerpts from the installationB               procedure and explains each step. Defaults appear in=               brackets throughout the installation procedure.A  D               To abort the installation procedure at any time, pressG               Ctrl/Y. When you press Ctrl/Y, the installation procedure C               deletes all files it has created up to that point andeE               then returns you to DCL level. If you want to retry thecD               installation procedure after pressing Ctrl/Y, you must"               proceed from step 2.  A               Step 1: Log in to a privileged account and set yourc9               default device and directory to SYS$UPDATE.C           <Return>  '               Username: SYSTEM <Return>A)               Password:          <Return> /               $ SET DEFAULT SYS$UPDATE <Return>p  '               Step 2: Invoke VMSINSTAL.X  :               $ @VMSINSTAL DTM03n MUA0: OPTIONS N <Return>  H                     OpenVMS Software Product Installation Procedure Vn.n  )               It is dd-mmm-yyyy at hh:mm. =               Enter a question mark (?) at any time for help.T  U               * Are you satisfied with the backup of your system disk [YES]? <Return>   G               If you are satisfied with the backup of your system disk,oH               press Return. Otherwise, enter NO and press the Return key.               to discontinue the installation.    H                                      Installing the DEC Test Manager 6-3 s               <            Step 3: Insert the first installation kit volume.  =            Please mount the first volume of the set on MUA0:. (            * Are you ready? YES <Return>4            The following products will be processed:                DTM V3.6   :                Beginning installation of DTM V3.6 at hh:mm  @            %VMSINSTAL-I-RESTORE, Restoring product save-set A...  B            To indicate that you want to continue the installation,D            mount volume 1, enter YES, and then press the Return key.  B            Step 4: Insert the subsequent installation kit volumes.  D            %BACKUP-I-READYREAD, mount volume 2 on _MUA0: for reading  /            Enter "YES" when ready: YES <Return>   A            The VMSINSTAL procedure prompts you to insert the nextMD            volume and waits for you to enter YES after inserting it.E            If you enter NO, VMSINSTAL displays the prompt again. This E            prompt is displayed only if your installation kit containss             more than one volume.  1            Step 5: Select a release notes option.   D            This step applies only if you specified OPTIONS N in step
            2.l  !            Release Notes Options:   '                1. Display release notes %                2. Print release notes                 3. Both 1 and 20                4. Copy release notes to SYS$HELP>                5. Do not display, print, or copy release notes  (            * Select option [2]: <Return>  A            If you select option 1, VMSINSTAL displays the release C            notes on line immediately. You can terminate the displayE*            at any time by pressing Ctrl/C.  (      6-4 Installing the DEC Test Manager o  h            G               If you select option 2, VMSINSTAL prompts you for a queueaH               name. Either enter a queue name or press the Return key to?               send the file to the default output print device.E  0               * Queue name [SYS$PRINT]: <Return>  D               If you select option 3, VMSINSTAL displays the releaseF               notes on line immediately. You can terminate the display%               at any time by pressing D               Ctrl/C. The VMSINSTAL procedure then prompts you for aG               queue name. Either enter a queue name or press the Return F               key to send the file to the default output print device.C               The DEC Test Manager release notes are then copied to ,               SYS$HELP:DTM036.RELEASE_NOTES.  H               If you select option 4, VMSINSTAL copies the release notes&               to SYS$HELP immediately.  H               If you select option 5, VMSINSTAL does not display, print,D               or copy the release notes, but moves them to SYS$HELP.G               Typically, this option is selected when the user wants toM#               end the installation..  F                 ________________________Note  ________________________  @                 The release notes file installed by VMSINSTAL isC                 labeled with the current product name and a versionA>                 number (for example, DTM036). Take care not toA                 delete release notes for previous versions of DECL                 Test Manager.   E                 _____________________________________________________   <               Next, VMSINSTAL displays the following prompt:  K               * Do you want to continue the installation [N]?: YES <Return> U               %VMSINSTAL-I-RELMOVED, The product release notes have been successfullyL$                   moved to SYS$HELP.  E               If you want to continue the installation, enter YES andLG               press the Return key. If you enter NO or press the ReturnLE               key, VMSINSTAL discontinues the installation. In either B               case, VMSINSTAL moves the release notes to SYS$HELP.    H                                      Installing the DEC Test Manager 6-5 S  L            ;            Step 6: Respond to license registration queries.S  C            DEC Test Manager supports the OpenVMS License ManagementT>            Facility (LMF). The installation procedure displaysB            license information about your product and then asks ifD            you have registered and loaded your product authorization>            key (PAK) for DEC Test Manager. The following is an'            example of such information:H              Product:       DTMP            Producer:      DECO            Version:       3.6R%            Release Date:  dd-mmm-yyyyS  O            * Does this product have an authorization key registered and loaded?   C            If you have not registered and loaded your PAK, you must D            answer NO to this question. You have to register and loadE            your PAK to successfully complete the installation. If youMB            answer YES to this question and you have not registeredA            and loaded the PAK, you are asked if you would like toYE            complete the installation without running the Installation ?            Verification Procedure (IVP). However, the next timeAA            you invoke DEC Test Manager you will receive a messageLC            indicating that you are not licensed to run the product.   /            Step 7: Select installation options.S  P            * Do you want to install the interface components [YES]? YES <Return>Y            * Do you also wish to install the DTM DECwindows interface [YES]? YES <Return>7U            * Do you want to purge files replaced by this installation [YES]? <Return>L  ?            The directories SYS$EXAMPLES, SYS$HELP, SYS$LIBRARY,OD            SYS$MANAGER, and SYS$SYSTEM may contain previous versions
            of B            DEC Test Manager files. These files are replaced duringE            the installation with new files, but the old files are not D            automatically purged. Purging is recommended. In responseD            to the purging prompt, press Return to purge the files or!            enter NO to keep them.S  R            * Do you want to run the IVP after the installation [YES]? YES <Return>      (      6-6 Installing the DEC Test Manager c  o            @               The IVP runs tests to verify that the installationA               was successful. If the IVP determines that you haveOE               insufficient quotas to run the IVP, you are notified asIE               to which quotas need to be increased and are then askedTD               if you would like to complete the installation withoutD               running the IVP. Press Return to run the IVP after theG               installation. If you do not want to run the IVP, enter NO                at the prompt.  6               Step 8: Read the informational messages.  B               The DEC Test Manager installation procedure producesC               a number of informational messages that report on the +               progress of the installation.p  A               The success of the installation is indicated by then                following message:  \               %VMSINSTAL-I-MOVEFILES, files will now be moved to their target directories...  E               If the installation procedure is successful, the new ormC               modified files are moved to their target directories.w  D               The SYS$HELP:HELPLIB.HLB and SYS$LIBRARY:DCLTABLES.EXEF               files are updated to include the new versions of the DECF               Test Manager Help text and the DEC Test Manager command-               line definition.  H               If you entered YES in response to the prompt that requestsG               a file purge at step 7, previous versions of the DEC Test +               Manager files are now purged.a  F                 ________________________Note  ________________________  ?                 When installing DEC Test Manager on OpenVMS VAX =                 Version 5.5, the following warning message isy                 displayed:  X                 %DECSET-I-LINKPCDRIVER, Linking PCDRIVER.EXE, ignore no transfer address                 warning.Y                 %LINK-W-USRTFR, image DKA200:[SYS0.SYSUPD.DECSET120]PCDRIVER.EXE;1 has no &                 user transfer address.      H                                      Installing the DEC Test Manager 6-7 e  e            >               This warning message can be ignored. It does not>               affect the performance of DEC Test Manager. ThisB               warning message is not displayed when installing DEC@               Test Manager on OpenVMS VAX Version 6.0 or higher,@               or when installing DEC Test Manager on any version               of OpenVMS Alpha.   C               _____________________________________________________   C            Step 9: Observe the installation verification procedure.   A            If you chose to run the IVP in step 6, VMSINSTAL callso@            the IVP to verify that DEC Test Manager was installed            successfully.  E            %DTM-I-IVPBEGIN, Begin Installation Verification Procedure.            .            .            .A            %DTM-I-IVPEND, End Installation Verification Procedurew  3            Step 10: End the installation procedure.b  F               Installation of DEC Test Manager V3.6 completed at hh:mm  /               VMSINSTAL procedure done at hh:mmo              $ LOGOUT <Return>5            SYSTEM     logged out at dd-mmm-yyyy hh:mm   D            The VMSINSTAL procedure deletes or changes entries in theD            process symbol tables during the installation. Therefore,B            if you are going to continue using the system manager'sB            account and you want to restore these symbols, you must$            log out and log in again.  6      6.3.1 Installing DEC Test Manager on a VAXcluster  @            If you want to run DEC Test Manager on multiple nodes@            of a VAXcluster, first check to see that you have theA            appropriate software license. Then, follow these steps -            after installing DEC Test Manager:t  D            1. Enter the LICENSE LOAD command to activate the license>               on each node in the VAXcluster on which DEC TestC               Manager is to be executed as described in the OpenVMSY0               License Management Utility Manual.  (      6-8 Installing the DEC Test Manager u  r            D               2. Run SYS$STARTUP:DTM$STARTUP.COM on each node of the5                  cluster that has a software license.   E                  To use the product on other nodes in the VAXcluster, G                  you must replace the version of the DCL tables that is_E                  installed on the other VAXcluster nodes. To do this,M-                  perform the following steps:n  4                  a. Log in to a node on the cluster.  B                  b. Enter the following command at the DCL prompt:  H                     $ INSTALL REPLACE SYS$LIBRARY:DCLTABLES.EXE <Return>  F                  c. Repeat steps a and b for each node of the cluster.  <         6.3.2 Running DEC Test Manager on a Mixed VAXcluster  G               Some users may want to run DEC Test Manager, Version 3.6,DE               on a mixed VAXcluster that supports various versions ofcG               OpenVMS software on different nodes. If DEC Test Manager,nA               Version 3.6, is to be used for interactive terminaltD               testing with a system running OpenVMS, Version 6.0, onG               the VAXcluster, then DEC Test Manager has to be installedv(               on the Version 6.0 system.  $         6.3.3 DEC Test Manager Files  D               The DEC Test Manager installation places the following?               files in the following directories on the system:e  H               __________________________________________________________H               Directory___________File_Name_____________________________  1               SYS$STARTUP         DTM$STARTUP.COMd  )               SYS$SYSTEM          DTM.EXE.2                                   DXDTMCONVERT.EXE2                                   DXDTMCOMPARE.EXE2                                   DXDTMPLAYREC.EXE2                                   DXDTMSCREDIT.EXE        H                                      Installing the DEC Test Manager 6-9               E            __________________________________________________________ E            Directory___________File_Name_____________________________   2            SYS$LIBRARY         DTM$DW_DEFAULTS.DAT)                                DTM$DW.UIDa4                                DTM_MASK_TEMPLATE.DAT,                                DTMIMGSHR.EXE-                                DTMPLAYREC.UIDg-                                DTMSCREDIT.UID .                                DTM_SCANSHR.EXE)                                DTMSHR.EXET  +            SYS$LOADABLE_       PCDRIVER.EXEo            IMAGESf  2            VUE$LIBRARY         DTM$PROFILE.VUE$DAT*                                VUE$DTM.COM  1            SYS$HELP            DTM$DW_HELPLIB.HLB 3                                DTM036.RELEASE_NOTES_-                                DTMCOMMANDS.PSo.                                DTMCOMMANDS.TXT-                                DTMMESSAGES.PS .                                DTMMESSAGES.TXT  E            SYS$TEST____________DTM$IVP.COM___________________________                                         )      6-10 Installing the DEC Test Managers I  o                  H                                                                        7H         ________________________________________________________________  H                     Installing the DEC Performance and Coverage Analyzer      F               This chapter explains how to install the DEC Performance*               and Coverage Analyzer (PCA).  0         7.1 Required Operating System Components  B               The OpenVMS operating system comes with a variety of?               support options, or classes. Classes include suchiG               features as networking and Record Management System (RMS) F               journaling. For a complete list of the required classes,9               see the Software Product Description (SPD).o  !         7.2 Prerequisite Softwarer  F               DEC PCA, Version 4.3, requires the OpenVMS VAX operatingD               system, Version 5.5 or higher; OpenVMS Alpha operatingB               system, Version 1.5 or higher; and DECwindows Motif,               Version 1.1.  B               The OpenVMS DECwindows Compute Server component mustB               be installed before PCA is installed. The DECwindowsE               compute server consists of the OpenVMS Run-Time Library D               (RTL) images DECW$DWTLIBSHR.EXE, DECW$XLIBSHR.EXE, and(               DECW$TRANSPORT_COMMON.EXE.           7.3 Optional Softwares  F               You can use the following optional software with DEC PCA               Version 4.3:  G               o  DEC Ada, Version 1.0, or VAX Ada, Version 2.0 or later   @               o  DEC BASIC, Version 3.2 and Version 3.3 or later  E               o  DEC BLISS-32 Implementation Language, Version 4.5 or                   later  @               o  DEC C, Version 2.4 through Version 4.0 or later  H                 Installing the DEC Performance and Coverage Analyzer 7-1                 -            o  DEC COBOL, Version 4.2 or lateru  -            o  DEC DIBOL, Version 4.0 or later   /            o  DEC Fortran, Version 5.5 or laters  3            o  DEC Fortran HPO, Version 1.0 or later   6            o  DEC Pascal, Version 3.9 and 4.0 or later  ,            o  DEC PL/I, Version 3.2 or later  .            o  DEC RPG II, Version 2.1 or later  ,            o  DEC SCAN, Version 1.1 or later  +            o  DEC Test Manager, Version 3.6   A            o  DEC Language-Sensitive Editor/Source Code Analyzer,n               Version 4.3e  =            All features of PCA are available to each of these @            languages. The DEC Test Manager and the DEC Language-?            Sensitive Editor/Source Code Analyzer can be used inn             conjunction with PCA.  ,      7.4 Installation Procedure Requirements  E            The DECset Environment Manager is installed as part of the D            installation of the PCA component. The DECset Environment            Manager consists of:   @            o  Run-time component used by DECset layered products              o  DCL interfacer  "            o  DECwindows interface  D            The DCL and DECwindows interface components are optional.  @            The installation takes approximately 5 to 25 minutes,A            depending on the type of media and your system config-o@            uration. Before installing DEC PCA, you must have the.            following privileges and resources:  =            o  SETPRV privileges, or CMKRNL, WORLD, and SYSPRV                privileges.E  B            o  A minimum of 12,000 blocks of free disk space duringD               installation; 5,000 blocks are used after installation$               with the demo package.  =      7-2 Installing the DEC Performance and Coverage Analyzer                  H               o  A minimum of 1,305 free global pages, plus the size (inM                  number of disk blocks) of the file SYS$LIBRARY:DCLTABLES.EXE H                  at installation. For most efficient operation, you willH                  need a total of 100 free global pages, plus the size of>                  SYS$LIBRARY:DCLTABLES.EXE after installation.  F               o  A minimum of 10 free global sections at installation.  .         7.5 User Account Quotas and Privileges  A               To use DEC PCA, it is recommended that each account A               have TMPMBX and NETMBX privileges and the followingt               requirements:   /               o  AST limit (ASTLM) 30 (minimum)   F               o  Buffered I/O byte count quota (BYTLM) 4,096 (minimum)  5               o  Open file limit (FILLM) 20 (minimum)            7.6 Installing DEC PCA  B               This section contains excerpts from the installationB               procedure and explains each step. Defaults appear in=               brackets throughout the installation procedure.   D               To abort the installation procedure at any time, pressG               Ctrl/Y. When you press Ctrl/Y, the installation proceduretC               deletes all files it has created up to that point andsE               then returns you to DCL level. If you want to retry therD               installation procedure after pressing Ctrl/Y, you must"               proceed from step 2.  A               Step 1: Log in to a privileged account and set yourt9               default device and directory to SYS$UPDATE.Y           <Return>  (               Username: SYSTEM  <Return>(               Password:         <Return>/               $ SET DEFAULT SYS$UPDATE <Return>         H                 Installing the DEC Performance and Coverage Analyzer 7-3 p  h            $            Step 2: Invoke VMSINSTAL.  7            $ @VMSINSTAL PCA043 MUA0: OPTIONS N <Return>w  E                  OpenVMS Software Product Installation Procedure Vn.n_  &            It is dd-mmm-yyyy at hh:mm.:            Enter a question mark (?) at any time for help.  R            * Are you satisfied with the backup of your system disk [YES]? <Return>  D            If you are satisfied with the backup of your system disk,E            press Return. Otherwise, enter NO and press the Return key +            to discontinue the installation._  <            Step 3: Insert the first installation kit volume.  =            Please mount the first volume of the set on MUA0:.o(            * Are you ready? YES <Return>4            The following products will be processed:                DEC PCA V4.3v  >                Beginning installation of DEC PCA V4.3 at hh:mm  @            %VMSINSTAL-I-RESTORE, Restoring product save-set A...  B            To indicate that you want to continue the installation,?            mount volume 1, enter YES, and press the Return key.n  B            Step 4: Insert the subsequent installation kit volumes.  D            %BACKUP-I-READYREAD, mount volume 2 on _MUA0: for reading  .            Enter "YES" when ready: YES<Return>  A            The VMSINSTAL procedure prompts you to insert the nextaD            volume and waits for you to enter YES after inserting it.E            If you enter NO, VMSINSTAL displays the prompt again. ThisnE            prompt is displayed only if your installation kit containsd             more than one volume.        =      7-4 Installing the DEC Performance and Coverage Analyzer     a            4               Step 5: Select a release notes option.  G               This step applies only if you specified OPTIONS N in stepa               2.  $               Release Notes Options:  *                   1. Display release notes(                   2. Print release notes!                   3. Both 1 and 2 3                   4. Copy release notes to SYS$HELPs@                   5. Do not display, print or copy release notes  +               * Select option [3]: <Return>i  D               If you select option 1, VMSINSTAL displays the releaseF               notes on line immediately. You can terminate the display-               at any time by pressing Ctrl/C.V  G               If you select option 2, VMSINSTAL prompts you for a queue H               name. Either enter a queue name or press the Return key to?               send the file to the default output print device.l  0               * Queue name [SYS$PRINT]: <Return>  D               If you select option 3, VMSINSTAL displays the releaseF               notes on line immediately. You can terminate the displayD               at any time by pressing Ctrl/C. VMSINSTAL then promptsF               you for a queue name. Either enter a queue name or pressC               the Return key to send the file to the default outputaH               print device. The DEC PCA release notes are then copied to,               SYS$HELP:PCA043.RELEASE_NOTES.  H               If you select option 4, VMSINSTAL copies the release notes&               to SYS$HELP immediately.  D               If you selected release note option 5, which specifiedH               that the release notes be copied to SYS$HELP, you will notH               be able to access the release notes without installing the                product kit again.  F                 ________________________Note  ________________________  C                 This version of the release notes file installed byhB                 VMSINSTAL is labeled with the current product nameC                 and version number. Take care not to delete releaset7                 notes for previous versions of DEC PCA.h  E                 _____________________________________________________n  H                 Installing the DEC Performance and Coverage Analyzer 7-5 V  e                9            Next, VMSINSTAL displays the following prompt:f  H            * Do you want to continue the installation [N]?: YES <Return>E            %VMSINSTAL-I-RELMOVED, The product release notes have beene0                  successfully moved to SYS$HELP.  B            If you want to continue the installation, enter YES andA            press the Return key. If you enter NO or press Return,TC            VMSINSTAL discontinues the installation. In either case,.9            VMSINSTAL moves the release notes to SYS$HELP.u  ;            Step 6: Respond to license registration queries.   C            DEC PCA supports the OpenVMS License Management FacilityL=            (LMF). The installation procedure displays licensee>            information about your product and then asks if you@            have registered and loaded your product authorizationE            key (PAK) for DEC PCA. The following is an example of suche            information:i              Product:       PCAi            Producer:      DEC             Version:       4.3d%            Release Date:  dd-mmm-yyyy_  O            * Does this product have an authorization key registered and loaded?n  B            You must have a PCA license installed and loaded on theE            system. If you do not have a license installed, answer NO.-E            The installation of PCA will continue but the Installation E            Verification Procedure (IVP) will not be executed. The IVPSC            will be placed on the system. It is recommended that youdC            execute the IVP upon completion of installation once you E            have registered and loaded the PCA license. See step 10 one"            how to execute the IVP.  /            Step 7: Select installation options.   R            The DECset Environment Manager is installed as part of the installation$            of this DECset component.  6            The DECset Environment Manager consists of:  @            A run-time component used by DECset layered products,            a DCL interface, and_"            a DECwindows interface.  =      7-6 Installing the DEC Performance and Coverage Analyzer                  G               The DCL and DECwindows interface components are optional.i  S               * Do you want to install the interface components [YES]? YES <Return>V\               * Do you also wish to install the PCA DECwindows collector [YES]? YES <Return>X               * Do you want to purge files replaced by this installation [YES]? <Return>K               * Do you want to install the PCA demo package [YES]? <Return>n  B               The directories SYS$EXAMPLES, SYS$HELP, SYS$LIBRARY,G               SYS$MANAGER, and SYS$SYSTEM may contain previous versionsoC               of DEC PCA files. These files are replaced during thesD               installation with new files, but the old files are notG               automatically purged. Purging is recommended. In response G               to the purging prompt, press Return to purge the files orm$               enter NO to keep them.  Q               * Do you want to run the IVP after the installation [YES]? <Return>   B               The IVP runs tests to check whether the installationC               procedure was successful. Press Return to run the IVPrH               after the installation. If you do not want to run the IVP,1               enter NO in response to the prompt.I  3               Step 8: Install the PCA demo package.   O               * Do you want to install the PCA demo package [YES]? YES <Return>eB               %VMS-I-SYSDIR, This product creates system directory)                     [SYSHLP.EXAMPLES.PCA]h  E               The VMSINSTAL procedure asks you if you want to installDF               the optional PCA demo package. If you enter YES (the de-               fault), then theD               SYS$COMMON:[SYSHLP.EXAMPLES.PCA] directory is created,C               and all the demo files are copied into it. The system G               logical name PCA$EXAMPLES, pointing to this directory, is G               also defined. After the installation, you will be able to 8               run the demos with @PCA$EXAMPLES:PCA_DEMO.  6               Step 9: Read the informational messages.  E               The DEC PCA installation procedure produces a number ofcG               informational messages that report on the progress of then               installation.e  A               The success of the installation is indicated by thea                following message:  M               %VMSINSTAL-I-MOVEFILES, files will now be moved to their targeto"                     directories...  H                 Installing the DEC Performance and Coverage Analyzer 7-7 t               B            If the installation procedure is successful, the new or@            modified files are moved to their target directories.  A            The SYS$HELP:HELPLIB.HLB and SYS$LIBRARY:DCLTABLES.EXErC            files are updated to include the new versions of the DECf=            PCA Help text and the PCA command-line definition.h  :            This installation will add the following files:  )            o  SYS$SYSTEM:PCA$ANALYZER.EXEt  +            o  SYS$LIBRARY:PCA$COLLECTOR.EXE_  %            o  SYS$LIBRARY:PCA$OBJ.OBJ   +            o  SYS$HELP:PCA043.RELEASE_NOTES   #            o  SYS$HELP:PCA$HELP.HLB   +            o  DECW$SYSTEM_DEFAULTS:PCAC.UID   +            o  DECW$SYSTEM_DEFAULTS:PCAA.UID   $            o  SYS$HELP:PCAA_HELP.HLB  $            o  SYS$HELP:PCAC_HELP.HLB  &            o  SYS$HELP:PCA_COMMANDS.PS  (            o  SYS$HELP:PCA_COMMANDS.LINE  /            o  SYS$HELP:PCA_COMMAND_REFERENCE.PS_  1            o  SYS$HELP:PCA_COMMAND_REFERENCE.LINED  &            o  SYS$HELP:PCA_MESSAGES.PS  (            o  SYS$HELP:PCA_MESSAGES.LINE  %            o  SYS$MESSAGE:PCA$MSG.MSG   )            o  SYS$STARTUP:PCA$STARTUP.COM   )            o  SYS$COMMON:[SYSTEST]PCA.DIR   /            o  VUE$LIBRARY:*.COM (PCA VUE Files)   )            o  SYS$COMMON:[SYSTEST.PCA]*.*   "            o  SYS$TEST:PCA$IVP.COM  @            The PCA, Version 4.3, installation optionally adds or            replaces the =            SYS$COMMON:[SYSHLP.EXAMPLES.PCA] directory and its             contents.  =      7-8 Installing the DEC Performance and Coverage AnalyzerE M  M            F               If you typed YES in response to the prompt that requestsF               a file purge at step 7, previous versions of the DEC PCA#               files are now purged.O  G               Step 10: Observe the Installation Verification Procedure.   H               If you chose to run the IVP in step 7, VMSINSTAL now callsD               the IVP to verify that PCA was successfully installed.  F               If PCA has been successfully installed, the IVP displays$               the following message:                  Running the IVP...  ;               The IVP ran successfully for PCA Version V4.3_  C               If you answered NO to the LMF question in step 6, you G               can run the IVP after installation, and after loading andC*               registering the PCA license.  G               To execute the IVP command procedure, enter the following                command:  *               $ @SYS$TEST:PCA$IVP <Return>  6               Step 11: End the installation procedure.  @                  Installation of DEC PCA V4.3 completed at hh:mm  2                  VMSINSTAL procedure done at hh:mm                 $ LOGOUT <Return> >               SYSTEM     logged out at dd-mmm-yyyy hh:mm:ss.ss  F               When the product installation procedure is complete, youC               can choose to install more products or to log out (asVD               shown here). If you removed any media from the consoleG               drive before beginning the installation, you must replace                it now.e  G               The VMSINSTAL procedure deletes or changes entries in theEG               process symbol tables during the installation. Therefore,iE               if you are going to continue using the system manager's,E               account and you want to restore these symbols, you mustS'               log out and log in again.   H                 Installing the DEC Performance and Coverage Analyzer 7-9                 -      7.6.1 Installing DEC PCA on a VAXcluster   <            If you want to run DEC PCA on multiple nodes of a;            VAXcluster, first check to see that you have the,A            appropriate software license. Then, follow these steps $            after installing DEC PCA:  D            1. Enter the LICENSE LOAD command to activate the licenseC               on each node in the VAXcluster on which DEC PCA is toa-               be executed as described in the 8               OpenVMS License Management Utility Manual.  A            2. Execute PCA$STARTUP.COM on each node of the cluster *               that has a software license.  B            3. To use the product on other nodes in the VAXcluster,D               you must replace the version of the DCL tables that isB               installed on the other VAXcluster nodes. To do this,*               perform the following steps:  1               a. Log in to a node on the cluster.   C               b. Run INSTALL and enter the following command at theg!                  INSTALL> prompt:C  D                  INSTALL> REPLACE SYS$LIBRARY:DCLTABLES.EXE <Return>  C               c. Repeat steps a and b for each node of the cluster.r        7.7 After the InstallationC  C            DEC PCA is now installed and can be invoked by all usersl             with the PCA command.  D            The installation procedure modifies the DCL command table?            so that the PCA command is recognized and processed.CA            However, the previous command table is still in effecteE            for those users who are currently logged in. All logged-ineD            users who want to use the PCA command must log out of the#            system and log in again.e  @            To reinstall PCA at system bootstrap time, modify theC            system-specific startup procedure. Include the following 9            line in the SYS$STARTUP:SYSTARTUP_V6.COM file:   '            @SYS$STARTUP:PCA$STARTUP.COMi  >      7-10 Installing the DEC Performance and Coverage Analyzer a  n            C               The PCA$STARTUP.COM file contains commands to install H               PCA$COLLECTOR.EXE. The PCA installation procedure puts the@               PCA$STARTUP.COM file in the SYS$STARTUP directory.                                                                                    H                Installing the DEC Performance and Coverage Analyzer 7-11 n  o                  H                                                                        8H         ________________________________________________________________  H                              Installing the DEC Module Management System      A               This chapter explains how to install the DEC Modulen&               Management System (MMS).  !         8.1 Prerequisite Softwareh  B               MMS, Version 3.0, requires the OpenVMS VAX operatingD               system, Version 5.5 or higher; OpenVMS Alpha operatingB               system, Version 1.5 or higher; and DECwindows Motif,               Version 1.1.  ?               For OpenVMS VAX, Version 5.5 (or higher) systems,eA               the following OpenVMS classes are required for fullc#               functionality of MMS:   *               o  OpenVMS required save set                 o  Utilities  $               o  Programming support  C               For more information on OpenVMS classes and tailoring E               them, see the OpenVMS Operating System Software Producto               Description.  /         8.2 Installation Procedure Requirementsr  C               The installation takes approximately 5 to 45 minutes, G               depending on the type of media and your system configura-rF               tion. Before installing MMS, you must have the following'               privileges and resources:   D               o  SETPRV privileges, or CMKRNL and SYSPRV privileges.  D               o  A minimum of 2,800 blocks of free disk space duringF                  installation; 300 blocks are used after installation.  6               o  A minimum of 2 MB of physical memory.  H                          Installing the DEC Module Management System 8-1 O  V            C            o  A minimum of 500 free global pages, plus the size (inaJ               number of disk blocks) of the file SYS$LIBRARY:DCLTABLES.EXE               at installation.  D            o  A minimum of 5 free global sections at installation; 5:               global sections are used after installation.  +      8.3 User Account Quotas and PrivilegesR  A            To use MMS, each account must have a minimum of TMPMBX A            privilege and have the following minimum requirements:e  ,            o  AST limit (ASTLM) 14 (minimum)  D            o  Buffered I/O byte count quota (BYTLM) 13,000 (minimum)  1            o  Open file limit (FILLM) 6 (minimum)v  ;            o  Subprocess creation quota (PRCLM) 2 (minimum):  #      8.4 Using MMS with Other ToolsR  E            The DECset Environment Manager is installed as part of the D            installation of the MMS component. The DECset Environment            Manager consists of:   @            o  Run-time component used by DECset layered products              o  DCL interface   "            o  DECwindows interface  D            The DCL and DECwindows interface components are optional.  B            MMS includes support for forms in VAX FMS libraries. IfD            FMS is not installed on your system, the procedure prints!            the following message:.  F            %MMS-I-NOFMSSUPP, MMS will not contain support for VAX FMS.  B            To use MMS to access forms stored in FMS libraries, youA            must have already installed FMS on your system. If you E            install or reinstall FMS after you have installed MMS, FMSeD            support will not be available. You must reinstall MMS for            FMS support.o  4      8-2 Installing the DEC Module Management System                          8.5 Installing MMS  G               This section contains excerpts from the installation pro-o               cedure andH               explains each step. Defaults appear in brackets throughout)               the installation procedure.f  D               To abort the installation procedure at any time, pressG               Ctrl/Y. When you press Ctrl/Y, the installation procedureyC               deletes all files it has created up to that point andME               then returns you to DCL level. If you want to retry theeD               installation procedure after pressing Ctrl/Y, you must"               proceed from step 2.  A               Step 1: Log in to a privileged account and set youru9               default device and directory to SYS$UPDATE.            <Return>  (               Username: SYSTEM  <Return>(               Password:         <Return>/               $ SET DEFAULT SYS$UPDATE <Return>   '               Step 2: Invoke VMSINSTAL.e  :               $ @VMSINSTAL MMS030 MUA0: OPTIONS N <Return>  H                     OpenVMS Software Product Installation Procedure Vn.n  )               It is dd-mmm-yyyy at hh:mm.S=               Enter a question mark (?) at any time for help.i  U               * Are you satisfied with the backup of your system disk [YES]? <Return>c  G               If you are satisfied with the backup of your system disk,nH               press Return. Otherwise, enter NO and press the Return key.               to discontinue the installation.  ?               Step 3: Insert the first installation kit volume._  @               Please mount the first volume of the set on MUA0:.+               * Are you ready? YES <Return> 7               The following products will be processed:e                   MMS V3.0  =                   Beginning installation of MMS V3.0 at hh:mm   C               %VMSINSTAL-I-RESTORE, Restoring product save-set A..._  H                          Installing the DEC Module Management System 8-3 o  n            B            To indicate that you want to continue the installation,?            mount volume 1, enter YES, and press the Return key.o  B            Step 4: Insert the subsequent installation kit volumes.  D            %BACKUP-I-READYREAD, mount volume 2 on _MUA0: for reading  /            Enter "YES" when ready: YES <Return>   A            The VMSINSTAL procedure prompts you to insert the next D            volume and waits for you to enter YES after inserting it.E            If you enter NO, VMSINSTAL displays the prompt again. ThisrE            prompt is displayed only if your installation kit containsi             more than one volume.  1            Step 5: Select a release notes option.t  D            This step applies only if you specified OPTIONS N in step
            2.i  !            Release Notes Options:f  '                1. Display release notes %                2. Print release notesk                3. Both 1 and 20                4. Copy release notes to SYS$HELP=                5. Do not display, print or copy release notes   (            * Select option [2]: <Return>  A            If you select option 1, VMSINSTAL displays the releasev            notes on lineA            immediately. You can terminate the display at any timea            by pressing Ctrl/C.  D            If you select option 2, VMSINSTAL prompts you for a queueE            name. Either enter a queue name or press the Return key to 7            send the file to the default output printer.   -            * Queue name [SYS$PRINT]: <Return>   A            If you select option 3, VMSINSTAL displays the releaseo            notes on lineE            immediately, and then prompts you for a queue name. Either             enter a queue?            name or press the Return key to send the file to the A            default output printer. The MMS release notes are then 3            copied to SYS$HELP:MMS030.RELEASE_NOTES.   4      8-4 Installing the DEC Module Management System                 H               If you select option 4, VMSINSTAL copies the release notes&               to SYS$HELP immediately.  C               If you select option 5, VMSINSTAL does not display or C               print the release notes, but copies them to SYS$HELP.o@               Typically, you select this option to terminate the               installation.Y  F                 ________________________Note  ________________________  @                 The release notes file installed by VMSINSTAL isA                 labeled with the current product name and version >                 number (for example, MMS030). Take care not toB                 delete release notes for previous versions of MMS.  E                 _____________________________________________________n  5               Next, VMSINSTAL displays the following:c  G               * Do you want to continue the installation ? YES <Return>sW               %VMSINSTAL-I-RELMOVED, The product's release notes have been successfully                 moved to SYS$HELP.  E               If you want to continue the installation, enter YES and F               press Return. If you enter NO or press Return, VMSINSTALF               discontinues the installation. In either case, VMSINSTAL2               moves the release notes to SYS$HELP.  >               Step 6: Respond to license registration queries.  B               MMS supports the OpenVMS License Management Facility               (LMF). TheG               installation procedure displays license information aboutwC               your product and then asks if you have registered and F               loaded your product authorization key (PAK) for MMS. The:               following is an example of such information:                  Product:       MMS                Producer:      DEC                Version:       3.0(               Release Date:  dd-mmm-yyyy  R               * Does this product have an authorization key registered and loaded?  A               You must register and load your PAK to successfullyoE               complete the installation. If you have not done so, you E               must answer NO to this question. Register and load your 4               PAK and then restart the installation.  H                          Installing the DEC Module Management System 8-5 n  l            /            Step 7: Select installation options.t  R            The DECset Environment Manager is installed as part of the installation$            of this DECset component.  6            The DECset Environment Manager consists of:  @            A run-time component used by DECset layered products,            a DCL interface, and "            a DECwindows interface.  D            The DCL and DECwindows interface components are optional.  P            * Do you want to install the interface components [YES]? YES <Return>Y            * Do you also wish to install the MMS DECwindows interface [YES]? YES <Return>.U            * Do you want to purge files replaced by this installation [YES]? <Return>s  A            The directories SYS$EXAMPLES, SYS$HELP, and SYS$SYSTEMeB            may contain previous versions of MMS files. These filesC            are replaced during the installation with new files, butYA            the old files are not automatically purged. Purging isB@            recommended. In response to the purging prompt, press>            Return to purge the files or enter NO to keep them.  N            * Do you want to run the IVP after the installation [YES]? <Return>  =            The Installation Verification Procedure (IVP) runs <            tests to check whether the installation procedure@            was successful. Press Return to run the IVP after theD            installation. If you do not want to run the IVP, enter NO%            in response to the prompt.o  3            Step 8: Read the informational messages.G  >            The MMS installation procedure produces a number of@            informational messages that report on the progress of            the installation.  C            No further questions will be asked. The MMS installationAI            will now continue for approximately 5 to 45 minutes, dependingr?            on your type of media and your system configuration.S  A            %VMSINSTAL-I-RESTORE, Restoring product save-set B ... F            %MMS-I-NOFMSSUPP, MMS will not contain support for VAX FMS.*            %MMS-I-LINKIMAGE, Linking V3.0.  C               ________________________Note ________________________i  A               You see the previous message only if VAX FMS is not   4      8-6 Installing the DEC Module Management System e               )                 installed on your system.V  E                 _____________________________________________________u  A               The success of the installation is indicated by thed                following message:  V         %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...  B               If the installation procedure is successful, the new@               or modified files are moved to their target direc-?               tories. In addition, the SYS$HELP:HELPLIB.HLB andrD               SYS$LIBRARY:DCLTABLES.EXE files are updated to includeH               the new versions of MMS help text and the MMS command-line               definition.   @               The following files are created or modified by the%               installation procedure:e  %                  SYS$HELP:HELPLIB.HLBL.                  SYS$HELP:MMS030.RELEASE_NOTES*                  SYS$LIBRARY:DCLTABLES.EXE#                  SYS$SYSTEM:MMS.EXE %                  SYS$TEST:MMS$IVP.COMo;                  [SYSHLP.EXAMPLES.MMS]MMS$DEFAULT_RULES.MMStA                  [SYSHLP.EXAMPLES.MMS]MMS$DEFAULT_SHELL_RULES.MMS   H               If you entered YES in response to the prompt that requests               a file purge atlH               step 7, previous versions of the MMS files are now purged.  B               Step 9: Run the Installation Verification Procedure.  H               If you chose to run the IVP in step 7, VMSINSTAL now callsH               the IVP to verify that MMS was installed successfully, and%               displays the following:   2               %MMS-I-BEGINIVP, Beginning V3.0 IVP.1               %MMS-I-ENDIVP, V3.0 IVP SUCCESSFUL.9  6               Step 10: End the installation procedure.  <                  Installation of MMS V3.0 completed at hh:mm  2                  VMSINSTAL procedure done at hh:mm                 $ LOGOUT <Return>o>               SYSTEM     logged out at dd-mmm-yyyy hh:mm:ss.ss  H                          Installing the DEC Module Management System 8-7 i  e            C            When the product installation procedure is complete, youa@            can choose to install more products or to log out (asA            shown here). If you removed any media from the consoleCD            drive before beginning the installation, you must replace            it now.  D            The VMSINSTAL procedure deletes or changes entries in theD            process symbol tables during the installation. Therefore,B            if you are going to continue using the system manager'sB            account and you want to restore these symbols, you must$            log out and log in again.  )      8.5.1 Installing MMS on a VAXclusterm  D            To run MMS on multiple nodes of a VAXcluster, first checkA            to see that you have the appropriate software license..9            Then, follow these steps after installing MMS:   D            1. Enter the LICENSE LOAD command to activate the licenseB               on each node in the VAXcluster on which MMS is to be*               executed as described in the8               OpenVMS License Management Utility Manual.  =            2. Enter the following command on each node in thec8               VAXcluster on which MMS is to be executed:  M               $ CREATE/DIRECTORY SYS$SPECIFIC:[SYS$HLP.EXAMPLES.MMS] <Return>t  B            3. To use the product on other nodes in the VAXcluster,D               you must replace the version of the DCL tables that isB               installed on the other VAXcluster nodes. To do this,*               perform the following steps:  1               a. Log in to a node on the cluster.R  ?               b. Enter the following command at the DCL prompt:n  E                  $ INSTALL REPLACE SYS$LIBRARY:DCLTABLES.EXE <Return>n  C               c. Repeat steps a and b for each node of the cluster.l          4      8-8 Installing the DEC Module Management System    $                  H                                                                        9H         ________________________________________________________________  H                                                   After the Installation      G               Your DECset tools are now installed and can be invoked by_               all users.  G               The installation procedure modifies the DCL command tabletC               so that the tool invocation command is recognized andME               processed. However, the previous command table is stilliD               in effect for those users who are currently logged in.H               All logged-in users who want to use the updated version ofD               each tool must log out of the system and log in again.  D               You must edit SYS$MANAGER:SYSTARTUP_VMS.COM, the site-@               specific startup file, and add the following line:  +               @SYS$STARTUP:tool$STARTUP.COM   H               The DECset installation procedure puts the startup command>               file for each tool in the SYS$STARTUP directory.  F         9.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 separatelyB               to ensure the integrity of installed files if systemF               problems occur, execute the following command procedure:  /               $ @SYS$TEST:tool$IVP.COM <Return>y  F               The IVP creates a temporary subdirectory in your currentF               default directory, and places a library for each tool inD               this subdirectory. The IVP then creates two additionalG               levels of subdirectories; therefore, your current default B               directory must not be a subdirectory deeper than sixG               levels. Additionally, your current default directory must F               not be defined as a directory search list. The temporaryH               subdirectory is deleted at the end of the execution of the               IVP.  H                                               After the Installation 9-1 a  t                  9.2 Error Conditionsr  B            If the installation procedure fails for any reason, the*            following message is displayed:  G            %VMSINSTAL-E-INSFAIL, The installation of [tool] has failed.   @            Note that your default directory must not be set as a            search list.r  E            If the IVP fails during the installation, the IVP displaysl,            a message, such as the following:  2            %CMS-E-IVPFAILURE, CMS V3.7 IVP failed.  A            %VMSINSTAL-E-IVPFAIL, The IVP for CMS V3.7 has failed.   D            An error during the installation can occur if one or more-            of the following conditions exist:M  8            o  The operating system version is incorrect.  =            o  The prerequisite software version is incorrect.   >            o  Quotas necessary for successful installation are-               insufficient (see Section 2.3).   E            o  Process quotas required by VMSINSTAL are incorrect (seeF               Section 1.7).y  ;            o  The OpenVMS help library is currently in use.   C            o  The product license was registered incorrectly or not.$               registered and loaded.  D            For descriptions of the error messages generated by theseC            conditions, see the OpenVMS System Messages and Recoverye?            Procedures Reference Manual, your processor-specifica@            installation/operations guide, or the OpenVMS License%            Management Utility Manual.m  B            If you are notified that any of these conditions exist,C            you must take the appropriate action as described in the @            message. You may need to change a system parameter or.            increase an authorized quota value.  D            If the installation fails, you must restart the installa-            tion procedure fromB            step 2 for the installation procedure for each tool. IfE            the installation fails due to an IVP failure, contact your 0            Digital field service representative.        9-2 After the Installationn l  i                     9.3 Maintenance Updates   C               Digital may periodically issue maintenance updates of F               DECset. Each update consists of an installation kit. YouD               must install this kit as described in this document orE               in any documentation that may accompany the maintenance                update.E  E               Each time a maintenance update is released, the version D               number changes. For example, if the current version isE               1.0, the version number of the first maintenance update G               will be 1.1. In addition, the maintenance update includesmG               new release notes. The release notes describe the changes H               that have been made to each DECset tool since the previous               release.  E               The update release notes are provided on line. You mustuB               read the release notes before you install any DECsetC               tools; they are also accessible at any time after the B               product is installed. For information on reading theF               release notes before installing any DECset tools, followE               the installation procedure for each tool. To locate thenD               release notes after installation, display or print the=               release notes file as described in Section 1.3.            9.4 Reporting Problems  C               If an error occurs while you are using DECset and you G               believe that the error is caused by a problem with one of ;               the tools, take one of the following actions:u  E               o  If you purchased a DECset license within the past 90nG                  days and you think the problem is caused by a softwareSD                  error, contact your Digital support representative.  F               o  If you have a BASIC or DECsupport Software Agreement,G                  you must call your Customer Support Center. With theseTF                  services, you receive telephone support that providesA                  high-level advisory and remedial assistance. For E                  more information, contact your local Digital supporte                   representative.  C               o  If you have a Self-Maintenance Software Agreement,a=                  contact your Digital support representative.   H                                               After the Installation 9-3                       H                                                                        AH         ________________________________________________________________  H                                            Sample Installation Procedure      H               This appendix contains a sample script of installing a fewG               of the DECset components on an OpenVMS Alpha system. NoteeD               that this is only a sample. Sometimes the installationB               procedure is modified in maintenance updates of thisE               product. Because this installation guide is not usuallyhG               revised for maintenance updates, be sure to read the ReadoG               Before Installing or Using DECset Version 12.0 letter fornF               your system before you install this product. This letterD               notes any significant changes in the installation that$               vary from this sample.  !          Node EDSDSA Running V6.1g  !         Username: SYSTEM <Return>          Password:l  A             *****************************************************S             *       *              *   WELCOME.TXT   *5             *       *s>             * This is a placeholder file only. The true file *;             * is built by DISKITBLD.COM when building the *o$             * distribution kit.    *             *       * A             *****************************************************   G             Last interactive login on Thursday, 30-MAR-1995 17:57:19.22 K             Last non-interactive login on Thursday, 30-MAR-1995 18:00:00.25(              H                                        Sample Installation Procedure A-1 e  o            '      SYSTEM>set def sys$update <Return>_      SYSTEM>@vmsinstal <Return> \       OpenVMS AXP Software Product Installation Procedure V6.1 It is 31-MAR-1995 at 06:47. -Z       Enter a question mark (?) at any time for help. %VMSINSTAL-W-ACTIVE, The following -!       processes are still active: 
       DECW$FDo       DECW$SERVER_0        DECSET$EM_1w8      * Do you want to continue anyway [NO]? yes <Return>L      * Are you satisfied with the backup of your system disk [YES]? <Return>i      * Where will the distribution volumes be mounted : decset$:[decset.staging.decset.v12_0.alpha.ssb] -.       <Return>  O      Enter the products to be processed from the first distribution volume set.e       * Products: decset <Return>B      * Enter installation options you wish to use (none): <Return>.      The following products will be processed:        DECSET V12.0e5       Beginning installation of DECSET V12.0 at 06:48d  ;      %VMSINSTAL-I-RESTORE, Restoring product save set A ... P      %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.  U      ********************************************************************************s  9        - DECset V12.0 Collective Installation Procedure -e  O          This is a collective installation procedure for the DECset components. O          This procedure first asks which DECset components to install.  Then itaP          checks the system resources required to perform the installation of allP          the components selected.  If there are enough system resources, it willQ          perform serial installation for each of the component you have selected. R          If the system resources are not enough for all components, it will informQ          the user about insufficient system resources but continues to install as.Q          many components as possible.  This will allow user to later install only K          those components which were not installed in the previous attempt.   U      ********************************************************************************n  ?               These are the options provided by this collectivec%               installation procedure:   $                   DECset components:    &      A-2 Sample Installation Procedure                 /                 -     All the DECset componentso5                 -     Language-Sensitive Editor (LSE)A0                 -     Source Code Analyzer (SCA)2                 -     Code Management System (CMS)&                 -     DEC Test Manager=                 -     Performance and Coverage Analyzer (PCA)a4                 -     Module Management System (MMS)  '           Please choose your option(s):s  J         *     Do you want     All the DECset components [NO]? yes <Return>N         *     Are you sure you want to install all the options [YES]? <Return>  V         %DECSET-I-AGGREGATE, Checking resources required to install selected products.  W         %DECSET-I-START_AENVMGR, The following questions relate to ENVMGR installation.e  6            The DECset Environment Manager consists of:  >          A run-time component used by DECset layered products,          a DCL interface, and            a DECwindows interface.  D            The DCL and DECwindows interface components are optional.  G         * Do you want to install the interface components [Y]? <Return> K         * Do you want to run the IVP after the installation [YES]? <Return>l  Q         %DECSET-I-START_ACMS, The following questions relate to CMS installation.   R         * Do you also wish to install the CMS DECwindows interface [YES]? <Return>\         * Do you also wish to install the Server for CMS Client for Windows? [YES]? <Return>R         * Do you want to purge files replaced by this installation [YES]? <Return>  $                 Product:      VAXSET!                 Producer:     DECs"                 Version:      12.0)                 Release Date: 26-MAY-1995y  !                 Product:      CMS !                 Producer:     DEC !                 Version:      3.7_)                 Release Date: 26-MAY-1995   P         * Is one of these authorization keys registered and loaded? yes <Return>K         * Do you want to run the IVP after the installation [YES]? <Return>t  S         %DECSET-I-DONEASK, You have answered all the questions for CMS installationn  H                                        Sample Installation Procedure A-3                 [      %DECSET-I-START_ADTM, The following questions relate to DEC Test Manager installation.a  !              Product:      VAXSET               Producer:     DEC              Version:      12.0 &              Release Date: 26-MAY-1995         Product:      DTMd       Producer:     DEC        Version:      3.6e       Release Date: 26-MAY-1995P  N      * Is one of these authorization keys registered and loaded?: yes <Return>H      * Do you want to run the IVP after the installation [YES]? <Return>O      * Do you want to purge files replaced by this installation [YES]? <Return>M  ]      %DECSET-I-DONEASK, You have answered all the questions for DEC Test Manager installationt  N      %DECSET-I-START_ALSE, The following questions relate to LSE installation.  O      * Do you want to purge files replaced by this installation [YES]? <Return> H      * Do you want to run the IVP after the installation [YES]? <Return>  Q          Please note that the total system disk space consumed by the unsupportedoQ          LSE source files is approximately 16,000 blocks.  Digital recommends notiQ          to answer yes to the following prompt if you are constrained by the freeD-          space available on your system disk.p  T      * Would you like to install the unsupported LSE source files [NO]? yes <Return>  H          The LSE that is currently installed on your system contains twoJ          command languages:  the VMSLSE command language, and the PORTABLE          command language.  P          If you would like to continue with the same system-wide default commandM          language that you are currently using, you should accept the default 4          answer provided to you at the prompt below.  L          If you would like to have the new PORTABLE command language as yourN          system-wide default command language, you should specify the PORTABLE          language.  N          If you would like to have a system-wide default command language thatM          is compatible with the command language available in versions of LSE ?          prior to V4.0, you should specify the VMSLSE language.s  K          Individual users may override the system default command language.14          See the release notes for more information.  &      A-4 Sample Installation Procedure c  k            P         1 line written to file $12$DKB100:[SYS0.SYSUPD.DECSET120]COMM_LANG.OUT;1    ]         * Do you want default command language to be PORTABLE or VMSLSE  [PORTABLE]: <Return>l  T             Language templates for Ada, BASIC, BLISS, C, COBOL, CXX, FORTRAN, MACRO,V             Pascal, PL/I , and VAXC as well as templates for the LSE command languagesU             are included in this kit.  Templates for other languages that support LSEuQ             and are not mentioned are provided in the installation kits for thoseI             languages.  T             Please choose the languages for which you would like to install support:  I         * Do you want to install language support for ADA [YES]? <Return> K         * Do you want to install language support for BASIC [YES]? <Return>hK         * Do you want to install language support for BLISS [YES]? <Return> G         * Do you want to install language support for C [YES]? <Return> K         * Do you want to install language support for COBOL [YES]? <Return> I         * Do you want to install language support for CXX [YES]? <Return>8M         * Do you want to install language support for FORTRAN [YES]? <Return> K         * Do you want to install language support for MACRO [YES]? <Return>_L         * Do you want to install language support for PASCAL [YES]? <Return>I         * Do you want to install language support for PLI [YES]? <Return> I         * Do you want to install language support for LSE [YES]? <Return> J         * Do you want to install language support for PLSE [YES]? <Return>  Q         You have answered all the questions for LSE installation.  During the LSE L         installation the system environment file will be created or updated.U         Informational and success messages will be displayed indicating these events.i  Q         %DECSET-I-START_AMMS, The following questions relate to MMS installation.o  )           +-----------------------------+ )           | Installation of MMS V3.0-03 |O)           +-----------------------------+p  H          The installation can be aborted at any time by pressing CTRL/Y.  $                 Product:      VAXSET!                 Producer:     DECc"                 Version:      12.0)                 Release Date: 26-MAY-1995             Product:      MMS          Producer:     DEC          Version:      3.0"          Release Date: 26-MAY-1995  H                                        Sample Installation Procedure A-5    a            M      * Is one of these authorization keys registered and loaded? yes <Return>r    D       This kit contains an Installation Verification Procedure (IVP)?       to verify the correct installation of MMS.  It can be run E       prior to the conclusion of this procedure by answering "YES" torB       the IVP prompt or invoked after the installation as follows:          @SYS$TEST:MMS$IVP  H      * Do you want to run the IVP after the installation [YES]? <Return>O      * Do you want to purge files replaced by this installation [YES]? <Return>   ?       You have answered all the questions for MMS installation.m  N      %DECSET-I-START_APCA, The following questions relate to PCA installation.  3          *** PCA V4.3-3 installation procedure. ***c  !              Product:      VAXSET               Producer:     DEC              Version:      12.0n&              Release Date: 26-MAY-1995                Product:      PCA              Producer:     DEC              Version:      4.3&              Release Date: 26-MAY-1995  a      * Does this product have one of these authorization keys registered and loaded? yes <Return> H      * Do you want to run the IVP after the installation [YES]? <Return>O      * Do you want to purge files replaced by this installation [YES]? <Return>uJ      * Do you wish to install the PCA DECwindows collector [YES]? <Return>B      * Do you want to install the PCA demo package [YES]? <Return>  O          You have answered all the questions required for the PCA installation.   N      %DECSET-I-START_ASCA, The following questions relate to SCA installation.  !              Product:      VAXSETr              Producer:     DEC              Version:      12.0s&              Release Date: 26-MAY-1995         Product:      LSEe       Producer:     DEC        Version:      4.3t       Release Date: 26-MAY-1995r  &      A-6 Sample Installation Procedure                 d         * Does this product have one of these authorization keys registered and loaded? yes <Return>  R                 As well as verifying that the installation succeeded, the IVP alsoR                 creates the SCA example library.  It is therefore recommended that                  you run the IVP.  K         * Do you want to run the IVP after the installation [YES]? <Return>/  L          The IVP has two sections, a character-cell section and a DECwindowsL          section.  In order for the DECwindows section to run correctly, theK          logical name DECW$DISPLAY must be appropriately set (using the SETsK          DISPLAY command).  If at this time you are not prepared to run thetI          DECwindows portion of the IVP, enter NO at the following prompt.a  =          You can rerun the IVP later by entering the command:             @SYS$TEST:SCA$IVP  =         * Do you wish to run the whole IVP [YES]? no <Return> R         * Do you want to purge files replaced by this installation [YES]? <Return>  H          Please indicate the components of SCA that you wish to install:  +              1 - Both SCA client and servery               2 - SCA client only  W         * Enter the number corresponding to the SCA components to install [1]: <Return>s  T         %DECSET-I-NOMORQST, You have answered all the questions for SCA installation  W         *******************************************************************************a  O             If you are satisfied with your answers, answer YES to the following N             prompt.  If not, answer NO to start the auto-answer session again.             The default is YES.l  W         *******************************************************************************e  `         *   Are you satisfied with your answers to selected DECset components ?  [YES]? <Return>  X         ********************************************************************************  O             This parent installation procedure will now install selected DECsett"             components one by one.  X         ********************************************************************************  ?         %DECSET-I-START_ENVMGR, ENVMGR installation in progresst  H                                        Sample Installation Procedure A-7 t  h            ;      %VMSINSTAL-I-RESTORE, Restoring product save set B ... `      %VMSINSTAL-I-SYSDIR, This product creates system disk directory  VMI$ROOT:[SYSTEST.ENVMGR].?      %CREATE-I-EXISTS, VMI$ROOT:[SYSTEST.ENVMGR] already exists T      %DECSET-I-DELETED, Deleted old version of SYS$MANAGER:DECSET$ENVMGR_STARTUP.COMN      The installation of the DECset Environment Manager has added or modified:             SYS$TEST:ENVMGR$IVP.COM1          SYS$TEST:ENVMGR$SAMPLE.DECSET_CONTEXT_DBh.          SYS$TEST:ENVMGR$SAMPLE.DECSET_CONTEXT"          SYS$LIBRARY:DCLTABLES.EXE          SYS$HELP:HELPLIB.HLB (          SYS$SYSTEM:DECSET$ENVMGRCCT.EXE*          SYS$SHARE:DECSET$ENVMGRCCTSHR.EXE'          SYS$SHARE:DECSET$ENVMGRSHR.EXEt+          SYS$SYSTEM:DECSET$START_ENVMGR.EXEi%          SYS$SYSTEM:DECSET$ENVMGR.EXE $          SYS$SHARE:DECSET$ENVMGR.DAT$          SYS$SHARE:DECSET$ENVMGR.UID#          SYS$HELP:DECSET$ENVMGR.HLBo(          VUE$LIBRARY:DECSET$MENU.VUE$DAT.          SYS$STARTUP:DECSET$ENVMGR_STARTUP.COM  H      You should add the following line to your system startup procedure:  1          $ @SYS$STARTUP:DECSET$ENVMGR_STARTUP.COM   W      %DECSET-I-DONEENVMGR, The installation of the DECset Environment Manager completed   6      %DECSET-I-START_CMS, CMS installation in progress  ;      %VMSINSTAL-I-RESTORE, Restoring product save set C ..._P      %DECSET-I-ENDRESTORE, All required savesets have been successfully restored.      %DECSET-I-CMSSHR, Linking shareable image&      %DECSET-I-CMS, Linking main image7      %DECSET-I-EVENTACT, Linking the event action imagee&      %DECSET-I-PROHELP, Providing help)      %DECSET-I-PRODCL, Providing DCL verb '      %DECSET-I-PROEXE, Providing imagesn  E       ***************************************************************iE       *                                                             *uE       * The CMS IVP has been moved to the SYS$TEST directory.  To   *eE       * run it after the installation, enter @SYS$TEST:CMS$IVP.COM. *iE       *                                                             *tE       ***************************************************************N  &      A-8 Sample Installation Procedure    T            7         %DECSET-I-PROSTART, Providing startup procedure*  H          ***************************************************************H          *                                                             *L              * If this installation is performed on a cluster, you must    *H          * execute                                                     *H          *                                                             *H          *    $ @SYS$STARTUP:CMS$STARTUP.COM                           *H          *                                                             *H          * on all other nodes in the cluster.  In addition, you must   *H          * add the above line to your system startup procedure.        *H          *                                                             *H          ***************************************************************  <         %DECSET-I-DONECMS, The installation of CMS completed  F         %DECSET-I-START_DTM, DEC Test Manager installation in progress  >         %VMSINSTAL-I-RESTORE, Restoring product save set D ...O         %DECSET-I-ENDRESTORE, All DEC Test Manager savesets have been restored.iN         %DECSET-I-PROHELP, Providing DEC Test Manager DCL and DECwindows help.B         %DECSET-I-PRODCL, Providing DCL verb for DEC Test Manager.;         %DECSET-I-PROEXE, Providing DEC Test Manager files.tX         ********************************************************************************X         *                                                                              *X         *  The DEC Test Manager IVP has been moved to the SYS$TEST directory.  To run  *X         *  the IVP after installation, enter @SYS$TEST:DTM$IVP.COM.                    *X         *                                                                              *X         ********************************************************************************X         ********************************************************************************X         *                                                                              *X         *  If this installation is being performed on a cluster, you must execute      *X         *                                                                              *X         *                       $ @SYS$STARTUP:DTM$STARTUP.COM                         *X         *                                                                              *X         *  on all nodes in the cluster.  In addition, you must add the above line to   *X         *  your system startup procedure.                                              *X         *                                                                              *X         ********************************************************************************  I         %DECSET-I-DONEDTM, The installation of DEC Test Manager completedo  9         %DECSET-I-START_LSE, LSE installation in progress     H                                        Sample Installation Procedure A-9    g            ;      %VMSINSTAL-I-RESTORE, Restoring product save set E ...(j      %TPU-S-SAVEENV, environment written to $12$DKB100:[SYS0.SYSUPD.DECSET120]LSE$SYSTEM_ENVIRONMENT.ENV;1]      %VMSINSTAL-I-SYSDIR, This product creates system disk directory  VMI$ROOT:[SYSTEST.LSE].y<      %CREATE-I-EXISTS, VMI$ROOT:[SYSTEST.LSE] already existse      %VMSINSTAL-I-SYSDIR, This product creates system disk directory  VMI$ROOT:[SYSHLP.EXAMPLES.LSE].wD      %CREATE-I-EXISTS, VMI$ROOT:[SYSHLP.EXAMPLES.LSE] already exists=      This installation added or modified the following files:t    &              SYS$LIBRARY:DCLTABLES.EXE"              SYS$SYSTEM:LSEDIT.EXE#              SYS$LIBRARY:LSESHR.EXEe       SYS$LIBRARY:LSESHR.IIF#              SYS$MESSAGE:LSEMSG.EXE '              SYS$LIBRARY:LSE$CCTSHR.EXE (              SYS$LIBRARY:LSE$DECWSHR.EXE0              SYS$LIBRARY:LSE$SECTION.TPU$SECTION)              SYS$LIBRARY:LSE$DEFAULTS.DAT 3              SYS$LIBRARY:LSE$SYSTEM_ENVIRONMENT.ENV &              SYS$LIBRARY:LSE$DEBUG.TPU(              SYS$LIBRARY:LSE$WIDGETS.UID"       SYS$LIBRARY:PSE$COMMENTS.EXE$              SYS$HELP:LSE$KEYPAD.HLB"              SYS$HELP:LSE$MENU.HLB       SYS$HELP:LSE$HELP.HLBh       SYS$HELP:LSE$CLIHELP.HLB; (              SYS$STARTUP:LSE$STARTUP.COM>              SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$USER.EXAMPLE?              SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$USER2.EXAMPLE[?              SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$USER3.EXAMPLE :              SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$USER.DIA1              SYS$SYSROOT:[SYSTEST.LSE]LSE$IVP.TPU !              SYS$TEST:LSE$IVP.COM                         '      A-10 Sample Installation Procedure_                 E                 SYS$SYSROOT:[VUE$LIBRARY.USER]LSE$EDIT_QUALIFIERS.EXEsB                 SYS$SYSROOT:[VUE$LIBRARY.USER]LSE$EDIT_OPTIONS.UID:                 SYS$SYSROOT:[VUE$LIBRARY.USER]LSE$EDIT.COM:          SYS$SYSROOT:[VUE$LIBRARY.USER]LSE$PROFILE.VUE$DAT<          SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$DECWINDOWS.TPU9          SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$GRAMMAR.TPUSD          SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$GRAMMAR_ADJUSTMENT.TPU?          SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$GRAMMAR_ALIAS.TPUPB          SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$GRAMMAR_LANGUAGE.TPUE          SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$GRAMMAR_PLACEHOLDER.TPU ?          SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$GRAMMAR_TOKEN.TPU >          SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$GRAMMAR_UTIL.TPU8          SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$PROMPT.TPU8          SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$PARSER.TPU6          SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$SHOW.TPU;          SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$SHOW_LIST.TPUn;          SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$HIGHLIGHT.TPUA5          SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$KEY.TPU.<          SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$INITIALIZE.TPU>          SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$EVE_ADVANCED.TPU:          SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$EVE_CORE.TPU@          SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$EVE_DECWINDOWS.TPU:          SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$EVE_EDIT.TPU9          SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$EVE_EDT.TPUr<          SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$EVE_EXTEND.TPU<          SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$EVE_EXTRAS.TPU:          SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$EVE_FILE.TPU<          SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$EVE_FORMAT.TPU:          SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$EVE_HELP.TPU;          SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$EVE_MENUS.TPU ;          SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$EVE_MOUSE.TPUu<          SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$EVE_PARSER.TPU:          SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$EVE_SHOW.TPU?          SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$EVE_TERMINALS.TPUn=          SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$EVE_WINDOWS.TPUu8          SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$METHOD.TPU7          SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$MENUS.TPUs7          SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$MOUSE.TPUt9          SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$VMS_SCA.TPU 9          SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$VMS_CMS.TPUg:          SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$VMS_HELP.TPU<          SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$EDIT_ICONS.UIL>          SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$EDIT_OPTIONS.UIL    H                                       Sample Installation Procedure A-11 0  M            6       SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$WIDGETS.UIL8       SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$CONSTANTS.UIL8       SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]EVE$CONSTANTS.UIL.       SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]TPU.ENV7       SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]PACK_HEADERS.TXT ;       SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]PACK_HEADERS_CLI.TPUn<       SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]PACK_HEADERS_PORT.TPU    E       *************************************************************** E       *                                                             *lI           * If this installation is performed on a cluster, you must    *SE       * execute                                                     *IE       *                                                             *oE       *    $ @SYS$STARTUP:LSE$STARTUP.COM                           *pE       *                                                             *uE       * on all other nodes in the cluster.  In addition, you must   *uE       * add the above line to your system startup procedure.        *lE       *                                                             *iE       ***************************************************************n  9      %DECSET-I-DONELSE, The installation of LSE completed   6      %DECSET-I-START_MMS, MMS installation in progress  ;      %VMSINSTAL-I-RESTORE, Restoring product save set F ... *      %DECSET-I-LINKIMAGE, Linking V3.0-03.V      %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.MMS].F      %CREATE-I-EXISTS, VMI$COMMON:[SYSHLP.EXAMPLES.MMS] already exists  E       ***************************************************************oE       *                                                             *sI           * If this installation is performed on a cluster, you must    *nE       * execute                                                     * E       *                                                             *-E       *    $ @SYS$STARTUP:MMS$STARTUP.COM                           *CE       *                                                             *rE       * on all other nodes in the cluster.  In addition, you must   * E       * add the above line to your system startup procedure.        * E       *                                                             * E       ***************************************************************5  9      %DECSET-I-DONEMMS, The installation of MMS completedy  6      %DECSET-I-START_PCA, PCA installation in progress  '      A-12 Sample Installation Proceduree e  V            >         %VMSINSTAL-I-RESTORE, Restoring product save set G ...>         %VMSINSTAL-I-RESTORE, Restoring product save set H ...Q         %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSTEST.PCA].$A         %CREATE-I-EXISTS, VMI$COMMON:[SYSTEST.PCA] already existsa>         %VMSINSTAL-I-RESTORE, Restoring product save set I ...Y         %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.PCA]. I         %CREATE-I-EXISTS, VMI$COMMON:[SYSHLP.EXAMPLES.PCA] already exists   O             The name of the PCA startup command file is: PCA$STARTUP.COM in the '             SYS$STARTUP directory area.   O             In order to start up PCA when your system boots, you should add the2<             following line to your system startup procedure:  '          $ @SYS$STARTUP:PCA$STARTUP.COM4  T             The release notes are available online by typing HELP PCA RELEASE_NOTES.  A             A pointer to the DECset documentation can be found ino/             SYS$HELP:DECSETDOCS*.RELEASE_NOTES.]  <         %DECSET-I-DONEPCA, The installation of PCA completed  9         %DECSET-I-START_SCA, SCA installation in progressh  >         %VMSINSTAL-I-RESTORE, Restoring product save set J ...d         %VMSINSTAL-I-SYSDIR, This product creates system disk directory  VMI$ROOT:[SYSTEST.SCA$IVP].C         %CREATE-I-EXISTS, VMI$ROOT:[SYSTEST.SCA$IVP] already existsgY         %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.SCA].PI         %CREATE-I-EXISTS, VMI$COMMON:[SYSHLP.EXAMPLES.SCA] already existstK         %CREATE-I-EXISTS, VMI$SPECIFIC:[SYSHLP.EXAMPLES.SCA] already existse  P             If you intend to execute this layered product on other nodes in yourL             cluster, and you have the appropriate software license, you mustO             prepare the system-specific roots on the other nodes by issuing thesQ             following command on each node (using a suitably privileged account):h  ?          $ CREATE /DIRECTORY SYS$SPECIFIC:[SYSHLP.EXAMPLES.SCA] a         %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.SCA.EXAMPLE].nS         %CREATE-I-EXISTS, VMI$SPECIFIC:[SYSHLP.EXAMPLES.SCA.EXAMPLE] already exists   P             If you intend to execute this layered product on other nodes in yourL             cluster, and you have the appropriate software license, you mustO             prepare the system-specific roots on the other nodes by issuing theCQ             following command on each node (using a suitably privileged account):r  H                                       Sample Installation Procedure A-13                 D       $ CREATE /DIRECTORY SYS$SPECIFIC:[SYSHLP.EXAMPLES.SCA.EXAMPLE]\      %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.SCA.2167A].N      %CREATE-I-EXISTS, VMI$SPECIFIC:[SYSHLP.EXAMPLES.SCA.2167A] already exists  M          If you intend to execute this layered product on other nodes in yournI          cluster, and you have the appropriate software license, you mustOL          prepare the system-specific roots on the other nodes by issuing theN          following command on each node (using a suitably privileged account):  B       $ CREATE /DIRECTORY SYS$SPECIFIC:[SYSHLP.EXAMPLES.SCA.2167A]  T      *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  D       Upon completion of this installation, please do the following:  H           - If this installation is being done on a cluster, you must do1        @SYS$STARTUP:SCA$STARTUP.COM on all nodes.t  6       - Be sure to edit the system startup file to add'            @SYS$STARTUP:SCA$STARTUP.COM*  T      *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *  *9      %DECSET-I-EXISTS, SCA$DEFAULT account already exists >      %DECSET-I-MODACC, Modifying account SCA$DEFAULT quotas...R      %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named SCA$DEFAULT.+      %UAF-I-MDFYMSG, user record(s) updated R      %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named SCA$DEFAULT.+      %UAF-I-MDFYMSG, user record(s) updatedI8      %DECSET-I-EXISTS, SCA$SERVER account already exists=      %DECSET-I-MODACC, Modifying account SCA$SERVER quotas...SQ      %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named SCA$SERVER.M+      %UAF-I-MDFYMSG, user record(s) updatedsQ      %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named SCA$SERVER.T+      %UAF-I-MDFYMSG, user record(s) updatedSQ      %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named SCA$SERVER.S+      %UAF-I-MDFYMSG, user record(s) updatedE  C        The network object SCA$SERVER has been defined.  If you wishE=        to view this, run SYS$SYSTEM:NCP and enter the commandX-              NCP> LIST OBJECT SCA$SERVER CHARi  9      %DECSET-I-DONESCA, The installation of SCA completedD  S      %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories....  U      ********************************************************************************P  '      A-14 Sample Installation Procedurei t  o            R             The DECset V12.0 collective installation will now run the InstallationP             Verification Procedure for the each of the component you selected to             run the IVP.  X         ********************************************************************************  N                  +-----------------------------------------------------------+N                  |      Installation verification command procedure for      |N                  |               DECset Environment Manager                  |N                  +-----------------------------------------------------------+  6            Starting IVP for DECset Environment Manager  D            IVP for DECset Environment Manager completed successfully  M         %CMS-I-IVPBEGIN, Begin CMS V3.7-1 Installation Verification Procedurev         $ SET NOVERIFY         $ CMS SHOW VERSION         CMS Version V3.7-1M         $ CMS CREATE LIBRARY $12$DKB100:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST] \         %CMS-S-CREATED, CMS Library $12$DKB100:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST] createdQ         %CMS-I-LIBIS, library is $12$DKB100:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]R"         %CMS-S-LIBSET, library setJ         $ CMS SET LIBRARY $12$DKB100:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]Q         %CMS-I-LIBIS, library is $12$DKB100:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST] "         %CMS-S-LIBSET, library set1         -CMS-I-SUPERSEDE, library list supersedede1         $ CMS CREATE ELEMENT CMS$IVP_TEST.FILE "" i         %CMS-S-CREATED, element $12$DKB100:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]CMS$IVP_TEST.FILE createdC*         $ CMS RESERVE CMS$IVP_TEST.FILE ""c         %CMS-S-RESERVED, generation 1 of element $12$DKB100:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST] -e#          CMS$IVP_TEST.FILE reservedu         $ CMS SHOW RESERVATIONSl  T         Reservations in CMS Library $12$DKB100:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]                    H                                       Sample Installation Procedure A-15 *  *                  CMS$IVP_TEST.FILE8          (1)   SYSTEM     1      31-MAR-1995 07:00:46 ""'      $ CMS REPLACE CMS$IVP_TEST.FILE ""rb      %CMS-S-GENCREATED, generation 2 of element $12$DKB100:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST] -       CMS$IVP_TEST.FILE created !      -CMS-I-NOCHANGES, no changesE      $ CMS VERIFYi'      %CMS-I-VERCLS, class list verifiedl)      %CMS-I-VERCMD, command list verified )      %CMS-I-VERELE, element list verified-'      %CMS-I-VERGRP, group list verifieds-      %CMS-I-VERRES, reservation list verified*5      %CMS-I-VERFRE, internal free space list verified 5      %CMS-I-VERFRE, internal free space list verified 5      %CMS-I-VERFRE, internal free space list verified 5      %CMS-I-VERFRE, internal free space list verified*5      %CMS-I-VERFRE, internal free space list verifiedT5      %CMS-I-VERFRE, internal free space list verified 5      %CMS-I-VERFRE, internal free space list verified 2      %CMS-I-VERARC, archive control block verified4      %CMS-I-VER2, internal contiguous space verified)      %CMS-I-VERCON, control file verified*f      %CMS-I-VEREDF, element $12$DKB100:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]CMS$IVP_TEST.FILE verified0      %CMS-I-VEREDFS, element data files verifiedW      %CMS-S-VERIFIED, library $12$DKB100:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST] verified +      $ CMS FETCH CMS$IVP_TEST.FILE/GEN=1 "" _      %CMS-S-FETCHED, generation 1 of element $12$DKB100:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST] -        CMS$IVP_TEST.FILE fetched +      $ CMS FETCH CMS$IVP_TEST.FILE/GEN=2 "" i      %CMS-I-FILEXISTS, file already exists, $12$DKB100:[SYS0.SYSUPD.DECSET120]CMS$IVP_TEST.FILE;2 created _      %CMS-S-FETCHED, generation 2 of element $12$DKB100:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST] -        CMS$IVP_TEST.FILE fetched 8      $ CMS DIFF CMS$IVP_TEST.FILE;-1 CMS$IVP_TEST.FILE;0*      %CMS-S-IDENTICAL, files are identical      $ SET NOVERIFY*#      $ CMS CREATE CLASS CL1 "Test1"EV      %CMS-S-CREATED, class $12$DKB100:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]CL1 created;      $ CMS INSERT GENERATION CMS$IVP_TEST.FILE/GEN=1 CL1 "" c      %CMS-S-GENINSERTED, generation 1 of element $12$DKB100:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST] -s_       CMS$IVP_TEST.FILE inserted into class $12$DKB100:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]CL1P#      $ CMS CREATE CLASS CL2 "Test2"VV      %CMS-S-CREATED, class $12$DKB100:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]CL2 created;      $ CMS INSERT GENERATION CMS$IVP_TEST.FILE/GEN=2 CL2 ""e    '      A-16 Sample Installation Procedureo t  e            e         %CMS-S-GENINSERTED, generation 2 of element $12$DKB100:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]- a         CMS$IVP_TEST.FILE inserted into class $12$DKB100:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]CL2S0         $ CMS FETCH CMS$IVP_TEST.FILE/GEN=CL2 ""b         %CMS-S-FETCHED, generation 2 of element $12$DKB100:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST] -"          CMS$IVP_TEST.FILE fetched         $ SET NOVERIFY         $ CMS SHOW ELEMENT  P         Elements in CMS Library $12$DKB100:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]           CMS$IVP_TEST.FILE "";         $ CMS SHOW GENERATION/DESCENDANTS CMS$IVP_TEST.FILEL  *         Element generations in CMS Library@                 $12$DKB100:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]           CMS$IVP_TEST.FILE .           2     31-MAR-1995 07:00:48 SYSTEM "".           1     31-MAR-1995 07:00:45 SYSTEM ""           $ CMS SHOW CLASS  O         Classes in CMS Library $12$DKB100:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]            CL1             "Test1".         CL2             "Test2" /         $ CMS SHOW GENERATION *.*/GEN=CL2/BRIEFM  *         Element generations in CMS Library8         $12$DKB100:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]                              H                                       Sample Installation Procedure A-17 c  r                  CMS$IVP_TEST.FILE/25      $ CMS REMOVE GENERATION CMS$IVP_TEST.FILE CL2 ""sb      %CMS-S-GENREMOVED, generation 2 of element $12$DKB100:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST] -^       CMS$IVP_TEST.FILE removed from class $12$DKB100:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]CL2      $ CMS DELETE CLASS CL2 ""V      %CMS-S-DELETED, class $12$DKB100:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]CL2 deleted5      $ CMS REMOVE GENERATION CMS$IVP_TEST.FILE CL1 ""Tb      %CMS-S-GENREMOVED, generation 1 of element $12$DKB100:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST] -^       CMS$IVP_TEST.FILE removed from class $12$DKB100:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]CL1      $ CMS DELETE CLASS CL1 ""V      %CMS-S-DELETED, class $12$DKB100:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]CL1 deleted      $ CMS CREATE GROUP GR1 ""V      %CMS-S-CREATED, group $12$DKB100:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]GR1 created      $ CMS CREATE GROUP GR2 ""V      %CMS-S-CREATED, group $12$DKB100:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]GR2 created,      $ CMS INSERT GROUP/NOCONFIRM GR1 GR2 ""e      %CMS-S-INSERTED, group $12$DKB100:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]GR1 inserted into group - 9       $12$DKB100:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]GR2 "      $ CMS REMOVE GROUP GR1 GR2 ""c      %CMS-S-REMOVED, group $12$DKB100:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]GR1 removed from group -T9       $12$DKB100:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]GR2S1      $ CMS MODIFY GROUP GR1/NAME=GR3/READ_ONLY "" X      %CMS-S-MODIFIED, group $12$DKB100:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]GR1 modified      $ CMS SHOW GROUP */BRIEF   K      Groups in CMS Library $12$DKB100:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]Y        GR2                 GR3      $ SET NOVERIFYO  =      %CMS-S-IVPSUCCESS, CMS V3.7-1 IVP completed successfully[;      %CMS-I-IVPEND, End Installation Verification ProcedureY                          '      A-18 Sample Installation ProcedureE P  .            X         ********************************************************************************X         *                                                                              *X         *           Beginning the DEC Test Manager verification procedure              *X         *                                                                              *X         ********************************************************************************'         DEC Test Manager Version V3.6-3.c         %DTM-S-CREATED, DEC Test Manager library $12$DKB100:[SYS0.SYSUPD.DECSET120.DTMTEST] createdE\         %DTM-S-LIBIS, DEC Test Manager library is $12$DKB100:[SYS0.SYSUPD.DECSET120.DTMTEST]D         %DTM-I-DEFAULTED, benchmark file name defaulted to TESTX.BMK6         %DTM-S-CREATED, test description TESTX created8         %DTM-S-MODIFIED, test description TESTX modifiedD         %DTM-I-DEFAULTED, benchmark file name defaulted to DECWX.BMKG         %DTM-I-DEFAULTED, template file name defaulted to DECWX.SESSION 6         %DTM-S-CREATED, test description DECWX created  5         Test Descriptions in DEC Test Manager Library$2         $12$DKB100:[SYS0.SYSUPD.DECSET120.DTMTEST]  )         DECWX           "decwindows test"E+             Template        = DECWX.SESSION*'             Benchmark       = DECWX.BMK*,             Prologue        = None Specified,             Epilogue        = None Specified  $         TESTX           "first test")             Template        = DTM$IVP.COM )             Benchmark       = DTM$IVP.COM ,             Prologue        = None Specified,             Epilogue        = None Specified4         %DTM-S-CREATED, symbol variable VAR1 created/         %DTM-S-MODIFIED, variable VAR1 modified   X         Variables in DEC Test Manager Library $12$DKB100:[SYS0.SYSUPD.DECSET120.DTMTEST]  (         VAR1            "first variable"             Value = NEWVALUE,         %DTM-S-CREATED, group GROUP1 created  U         Groups in DEC Test Manager Library $12$DKB100:[SYS0.SYSUPD.DECSET120.DTMTEST]*  $         GROUP1          "test group",         %DTM-S-CREATED, group GROUP2 created@         %DTM-S-INSERTED, group GROUP1 inserted into group GROUP2>         %DTM-S-REMOVED, group GROUP1 removed from group GROUP2  U         Groups in DEC Test Manager Library $12$DKB100:[SYS0.SYSUPD.DECSET120.DTMTEST]S  H                                       Sample Installation Procedure A-19 e                     GROUP1              GROUP2*-      %DTM-S-CREATED, collection COLL1 created   ,      Collections in DEC Test Manager Library/      $12$DKB100:[SYS0.SYSUPD.DECSET120.DTMTEST]e  2      COLL1          1 test    31-MAR-1995 07:01:29M             Command: CREATE COLLECTION/NOVERIFY COLL1 TESTX "test collection"              Status: not run   -      %DTM-S-DELETED, collection COLL1 deletedT3      %DTM-I-DELETED, test_description DECWX deleted 3      %DTM-I-DELETED, test_description TESTX deleted ,      %DTM-S-DELETIONS, 2 deletions completed*      %DTM-I-DELETED, variable VAR1 deleted+      %DTM-S-DELETIONS, 1 deletion completed.)      %DTM-I-DELETED, group GROUP1 deleted )      %DTM-I-DELETED, group GROUP2 deleted ,      %DTM-S-DELETIONS, 2 deletions completed,      %DTM-I-VERFRE, free space list verified(      %DTM-I-VERSTR, string list verified,      %DTM-I-VERCOL, collection list verified'      %DTM-I-VERGRO, group list verifiedr1      %DTM-I-VERTD, test description list verifiedR+      %DTM-I-VERVAR, variables list verified )      %DTM-I-VERARC, archive list verified 5      %DTM-I-VERHEAD, user header information verifiedc/      %DTM-I-VERSPACE, contiguous space verified >      %DTM-I-VERCOLDIR, collection directory structure verifiedb      %DTM-S-VERIFIED, DEC Test Manager library $12$DKB100:[SYS0.SYSUPD.DECSET120.DTMTEST] verifiedU      ********************************************************************************MU      *                                                                              *mU      *           DEC Test Manager verification procedure successful                 * U      *                                                                              * U      ********************************************************************************.  K               +-----------------------------------------------------------+EK               |      Installation verification command procedure for      |dK               |               DEC Language-Sensitive Editor               |OK               +-----------------------------------------------------------+i  F      36 lines written to file $1$DIA1:[VMS$COMMON.SYSMGR]LSE$IVP.LIS;1  7       DEC Language-Sensitive Editor IVP was successful.   '      A-20 Sample Installation ProcedureS T  A                       Beginning IVP for MMSY  /         %MMS-I-BEGINIVP, Beginning V3.0-03 IVP.I.         %MMS-I-ENDIVP, V3.0-03 IVP SUCCESSFUL.             MMS IVP successful  =             Starting the IVP procedure for PCA Version V4.3-3t  @             The IVP procedure is complete for PCA Version V4.3-3  =               The IVP ran successfully for PCA Version V4.3-3r  5         ****  Beginning IVP for DEC SCA V4.3-03  ****u  +         ****  Client testing complete  ****t7         %SCA-I-CONNECTING, Requesting connection to 0::h7         %SCA-S-LIB, your SCA Library is 0::SCA$EXAMPLE:n7         %SCA-I-CONNECTING, Requesting connection to 0:: +         ****  Server testing complete  ****.>         ****  IVP for SCA V4.3-03 completed successfully  ****  8          Installation of DECSET V12.0 completed at 07:02  F             Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY  P             Creating installation data file: VMI$ROOT:[SYSUPD]DECSET120.VMI_DATA  Q         Enter the products to be processed from the next distribution volume set. !         * Products: exit <Return> *          VMSINSTAL procedure done at 07:09         SYSTEM>logout <Return><           SYSTEM       logged out at 31-MAR-1995 07:09:31.29                        H                                       Sample Installation Procedure A-21 I  T                  H                                                                        BH         ________________________________________________________________  H                       Sample Online Documentation Installation Procedure      F               This appendix contains a sample script of installing theG               DECset online documentation save sets on an OpenVMS AlphaaG               system. This is only a sample. Sometimes the installationfB               procedure is modified in maintenance updates of this               product.    !          Node EDSDSA Running V6.1.  !         Username: SYSTEM <Return>          Password:*  A             *****************************************************              *       *              *   WELCOME.TXT   *t             *       *n>             * This is a placeholder file only. The true file *;             * is built by DISKITBLD.COM when building the *a$             * distribution kit.    *             *       * A             *****************************************************                             H                   Sample Online Documentation Installation Procedure B-1 f  g            B          Last interactive login on Friday, 31-MAR-1995 07:08:45.94H          Last non-interactive login on Thursday, 30-MAR-1995 18:00:00.25'      SYSTEM>set def sys$update <Return>n      SYSTEM>@vmsinstal <Return>e\       OpenVMS AXP Software Product Installation Procedure V6.1 It is 31-MAR-1995 at 10:08. -5       Enter a question mark (?) at any time for help.iC      %VMSINSTAL-W-ACTIVE, The following processes are still active:t
       DECW$FDs       DECW$SERVER_0$       DECSET$EM_1-8      * Do you want to continue anyway [NO]? yes <Return>L      * Are you satisfied with the backup of your system disk [YES]? <Return>h      * Where will the distribution volumes be mounted: decset$:[decset.staging.decset.v12_0.alpha.ssb] -
      <Return>A  O      Enter the products to be processed from the first distribution volume set.e$      * Products: decsetdocs <Return>B      * Enter installation options you wish to use (none): <Return>.      The following products will be processed:        DECSETDOCS V12.0n9       Beginning installation of DECSETDOCS V12.0 at 10:08l    ;      %VMSINSTAL-I-RESTORE, Restoring product save set A ...*P      %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.O      * Do you want to purge files replaced by this installation [YES]? <Return>0  R      * Enter a directory where selected documents to be put? [SYS$HELP:]: <Return>  b      * Do you want DECset documentation installed (enter All, Some, or None)? [ALL]: some <Return>  M      * Do you want to install the DECset installation guides? [YES]? <Return>   E      * Do you want to install the DECset user guides? [YES]? <Return>   K      * Do you want to install the DECset reference manuals? [YES]? <Return>   X      * Do you want to install DECset documentation in PostScript format? [YES]? <Return>  X      * Do you want to install DECset documentation in Bookreader format? [YES]? <Return>  Y      * Do you want to install DECset documentation in MAIL (.TXT) format? [YES]? <Return>f  I      * Do you want Common DECset documentation installed? [YES]? <Return>r  ?      * Do you want CMS documentation installed? [YES]? <Return>   ?      * Do you want DTM documentation installed? [YES]? <Return>.  ;      B-2 Sample Online Documentation Installation Procedurei r  1            B         * Do you want LSE documentation installed? [YES]? <Return>  B         * Do you want MMS documentation installed? [YES]? <Return>  B         * Do you want PCA documentation installed? [YES]? <Return>  B         * Do you want SCA documentation installed? [YES]? <Return>  X         ********************************************************************************  [         %DECSETDOCS-I-DONEASK, No further questions will be asked during this installation. >         %VMSINSTAL-I-RESTORE, Restoring product save set B ...R         %DECSETDOCS-I-ENDRESTORE, The CMS Documentation saveset has been restored.>         %VMSINSTAL-I-RESTORE, Restoring product save set C ..._         %DECSETDOCS-I-ENDRESTORE, The DEC Test Manager Documentation saveset has been restored.R>         %VMSINSTAL-I-RESTORE, Restoring product save set D ...R         %DECSETDOCS-I-ENDRESTORE, The LSE Documentation saveset has been restored.>         %VMSINSTAL-I-RESTORE, Restoring product save set E ...R         %DECSETDOCS-I-ENDRESTORE, The PCA Documentation saveset has been restored.>         %VMSINSTAL-I-RESTORE, Restoring product save set F ...R         %DECSETDOCS-I-ENDRESTORE, The SCA Documentation saveset has been restored.<          Installation of DECSETDOCS V12.0 completed at 10:16  F             Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY  T             Creating installation data file: VMI$ROOT:[SYSUPD]DECSETDOCS120.VMI_DATA  Q         Enter the products to be processed from the next distribution volume set. !         * Products: exit <Return> *          VMSINSTAL procedure done at 10:22         SYSTEM>logout <Return><           SYSTEM       logged out at 31-MAR-1995 10:22:48.21                          H                   Sample Online Documentation Installation Procedure B-3