 


                     HP DECset for OpenVMS_________________________
                     Installation Guide

                     Order Number: AA-PUPKG-TK

                     July 2005

                     This guide explains how to install the HP DECset
                     for OpenVMS software.








                     Revision/Update Information: This is a revised
                                                  manual.

                     Operating System Version:    OpenVMS I64 Version
                                                  8.2

                                                  OpenVMS Alpha Version
                                                  7.3-2 or 8.2

                                                  OpenVMS VAX Version
                                                  7.3

                     Windowing System Version:    DECwindows Motif for
                                                  OpenVMS I64 Version
                                                  1.5

                                                  DECwindows Motif for
                                                  OpenVMS Alpha Version
                                                  1.3-1 or 1.5

                                                  DECwindows Motif for
                                                  OpenVMS VAX Version
                                                  1.2-6

                     Software Version:            HP DECset Version
                                                  12.7 for OpenVMS

                     Hewlett-Packard Company
                     Palo Alto, California

 






           __________________________________________________________

            Copyright 2005 Hewlett-Packard Development Company, L.P.

           Confidential computer software. Valid license from HP
           required for possession, use or copying. Consistent with
           FAR 12.211 and 12.212, Commercial Computer Software,
           Computer Software Documentation, and Technical Data for
           Commercial Items are licensed to the U.S. Government under
           vendor's standard commercial license.

           The information contained herein is subject to change
           without notice. The only warranties for HP products
           and services are set forth in the express warranty
           statements accompanying such products and services.
           Nothing herein should be construed as constituting an
           additional warranty. HP shall not be liable for technical
           or editorial errors or omissions contained herein.

           Intel and Itanium are trademarks or registered trademarks
           of Intel Corporation or its subsidiaries in the United
           States and other countries.

           Java is a US trademark of Sun Microsystems, Inc.

           Microsoft, Windows, and Windows NT are U.S. registered
           trademarks of Microsoft Corporation.

           Printed in the US

 













   ________________________________________________________________

                                                           Contents


   Preface..................................................    vii


   1  Preparing to Install the DECset Components

         1.1   Required Operating System and Prerequisite
               Hardware and Software........................    1-1
         1.2   License Registration (Alpha and VAX Only)....    1-1
         1.3   Accessing Online Documentation...............    1-3
         1.4   Installation Procedure Requirements..........    1-4
         1.4.1     Privileges...............................    1-4
         1.4.2     System Parameters and Disk Space.........    1-5
         1.4.3     VMSINSTAL Requirements...................    1-5
         1.4.4     Backing Up Your System Disk..............    1-6
         1.5   User Account Quotas and Privileges...........    1-6
         1.6   Standard System Maintenance Procedures.......    1-7
         1.6.1     Checking UAF Parameters..................    1-7
         1.6.2     Calculating the Values for GBLPAGES and
                   GBLSECTIONS..............................    1-7
         1.6.3     Changing System Parameter Values with
                   AUTOGEN..................................    1-9

   2  Installing the DECset Kit

         2.1   Prerequisite Software........................    2-2
         2.2   Accessing the Online Release Notes...........    2-2
         2.3   Installation Procedure Requirements..........    2-3
         2.4   Backing Up Your System Disk..................    2-4
         2.5   Using VMSINSTAL..............................    2-4
         2.6   Installing DECset............................    2-8
         2.7   Installing the DECset Components.............   2-13



                                                                iii

 






     3  Installing the Code Management System for OpenVMS

           3.1   Installation Procedure Requirements..........    3-1
           3.2   User Account Quotas and Privileges...........    3-2
           3.3   Installing CMS...............................    3-2
           3.4   Installing CMS on an OpenVMS Cluster.........    3-8

     4  Installing the Digital Test Manager for OpenVMS

           4.1   Installation Procedure Requirements..........    4-1
           4.2   User Account Quotas and Privileges...........    4-2
           4.3   Installing DTM...............................    4-2
           4.4   Installing DTM on an OpenVMS Cluster.........    4-7
           4.5   Running DTM on a Mixed OpenVMS Cluster.......    4-8

     5  Installing the Language-Sensitive Editor for OpenVMS

           5.1   Installation Procedure Requirements..........    5-1
           5.2   User Account Quotas and Privileges...........    5-2
           5.3   Installing LSE...............................    5-2
           5.4   Installing LSE on an OpenVMS Cluster.........    5-7

     6  Installing the Module Management System for OpenVMS

           6.1   Installation Procedure Requirements..........    6-1
           6.2   User Account Quotas and Privileges...........    6-2
           6.3   Installing MMS...............................    6-2
           6.4   Installing MMS on an OpenVMS Cluster.........    6-6

     7  Installing the Performance and Coverage Analyzer for
        OpenVMS

           7.1   Installation Procedure Requirements..........    7-1
           7.2   User Account Quotas and Privileges...........    7-2
           7.3   Installing PCA...............................    7-2
           7.4   Installing PCA on an OpenVMS Cluster.........    7-6









     iv

 






        8  Installing the Source Code Analyzer for OpenVMS

              8.1   Installation Procedure Requirements..........    8-1
              8.2   User Account Quotas and Privileges...........    8-2
              8.3   Installing SCA...............................    8-2
              8.4   Installing SCA on an OpenVMS Cluster.........   8-10
              8.5   SCA Server Installation (Alpha and VAX
                    Only)........................................   8-11
              8.6   Installing SCA Server on an OpenVMS Cluster
                    (Alpha and VAX Only).........................   8-13

        9  After the Installation

              9.1   OpenVMS Cluster Setup........................    9-1
              9.2   OpenVMS Mail Utility.........................    9-2
              9.3   Running the Installation Verification
                    Procedure Separately.........................    9-2
              9.4   Product Updates..............................    9-3
              9.5   DECset as a Shared Image.....................    9-4

        A  Sample Installation Procedures

              A.1   Sample Installation on an OpenVMS I64
                    System.......................................    A-1
              A.2   Sample Upgrade on an OpenVMS Alpha System....   A-22

        B  Files Installed on Your System

              B.1   Logical Names Defined on Your System.........    B-1
              B.2   ENVMGR Files Installed.......................    B-2
              B.3   CMS Files Installed..........................    B-2
              B.4   DTM Files Installed..........................    B-3
              B.5   LSE Files Installed..........................    B-4
              B.6   MMS Files Installed..........................   B-11
              B.7   PCA Files Installed..........................   B-11
              B.8   SCA Files Installed..........................   B-13









                                                                       v

 






     C  Recovering from Errors

           C.1   Failures During DECset Installation..........    C-1


     Tables

           1-1       Online Documentation Files for DECset....    1-3

           2-1       Disk Space Storage Requirements..........    2-3

           2-2       Installation Option Designators..........    2-6

           9-1       DECset IVPs..............................    9-2































     vi

 











        ________________________________________________________________

                                                                 Preface



              This guide explains how to install the DECset for OpenVMS
              (DECset) software on OpenVMS systems. Throughout this
              guide, references to OpenVMS systems apply to all
              supported hardware platforms, unless explicitly stated.

              The DECset software consists of the following components:

              o  Code Management System for OpenVMS (CMS)

              o  Language-Sensitive Editor for OpenVMS (LSE)

              o  Source Code Analyzer for OpenVMS (SCA)

              o  Digital Test Manager for OpenVMS (DTM)

              o  Performance and Coverage Analyzer for OpenVMS (PCA)

              o  Module Management System for OpenVMS (MMS)

              o  DECset Environment Manager for OpenVMS (ENVMGR)

        Intended Audience

              This guide is intended for system managers of OpenVMS
              systems.

        Document Structure

              This guide contains the following chapters and appendices:

              o  Chapter 1 gives preparatory information for installing
                 the DECset components.

              o  Chapter 2 describes how to start the installation
                 procedure to install any or all of the DECset
                 components.

              o  Chapter 3 describes how to install CMS.

                                                                     vii

 






           o  Chapter 4 describes how to install DTM.

           o  Chapter 5 describes how to install LSE.

           o  Chapter 6 describes how to install MMS.

           o  Chapter 7 describes how to install PCA.

           o  Chapter 8 describes how to install SCA.

           o  Chapter 9 gives post-installation information.

           o  Appendix A provides sample scripts for installing and
              upgrading the DECset components.

           o  Appendix B lists the data files installed on your
              system by VMSINSTAL, grouped by component application.

           o  Appendix C provides information on dealing with errors
              during the installation or use of the DECset product.

     Related Documents

           The following documentation may be helpful when installing
           the DECset software:

           o  Guide to Detailed Program Design for OpenVMS Systems

           o  Guide to DIGITAL Performance and Coverage Analyzer for
              OpenVMS Systems

           o  DIGITAL Performance and Coverage Analyzer Command-Line
              Interface Guide

           o  DIGITAL Performance and Coverage Analyzer for OpenVMS
              Reference Manual

           o  HP DECset for OpenVMS Guide to the Module Management
              System

           o  Guide to DIGITAL Language-Sensitive Editor for OpenVMS
              Systems

           o  DIGITAL Language-Sensitive Editor/Source Code Analyzer
              for OpenVMS Reference Manual

           o  DIGITAL Language-Sensitive Editor Command-Line
              Interface and Callable Routines Manual

           o  Guide to DIGITAL Source Code Analyzer for OpenVMS
              Systems

     viii

 






              o  DIGITAL Source Code Analyzer Command-Line Interface and
                 Callable Routines Manual

              o  Guide to DIGITAL Test Manager for OpenVMS Systems

              o  DIGITAL Test Manager for OpenVMS Reference Manual

              o  HP DECset for OpenVMS Guide to the Code Management
                 System

              o  HP DECset for OpenVMS Code Management System Reference
                 Manual

              o  HP DECset for OpenVMS Code Management System Callable
                 Routines Reference Manual

              o  OpenVMS System Manager's Manual

              o  OpenVMS System Management Utilities Reference Manual

              o  OpenVMS License Management Utility Manual

              You may also find the following documents useful:

              o  Using DECset for OpenVMS Systems describes how to use
                 the DECset tools and platform software to create an
                 effective application development environment.

              o  HP DECset for OpenVMS Cookbook for an Integrated
                 Product Development Environment contains further
                 examples of how to use the DECset tools in specific
                 application development environments.

              For additional information about HP OpenVMS products and
              services, visit the following World Wide Web address:

              http://www.hp.com/go/openvms/doc/

        References to Other Products

              Some older products that DECset components worked with
              previously may no longer be available or supported by
              HP. References in this manual to such products serve
              as examples only and do not imply that HP has conducted
              recent interoperability testing.

              See the Software Product Description for a current list
              of supported products that are warranted to interact with
              DECset components.

                                                                      ix

 






     Reader's Comments

           HP welcomes your comments on this manual. Please send
           comments to either of the following addresses:

           Internet    openvmsdoc@hp.com

           Postal      Hewlett-Packard Company
           Mail        OSSG Documentation Group, ZKO3-4/U08
                       110 Spit Brook Rd.
                       Nashua, NH 03062-2698

     How to Order Additional Documentation

           For information about how to order additional documenta-
           tion, visit the following World Wide Web address:

           http://www.hp.com/go/openvms/doc/order

     Conventions

           The following typographic conventions may be used in this
           manual:

           __________________________________________________________
           Convention__________Description___________________________

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

           <Return>            In examples, a key name enclosed in a
                               box indicates that you press a key on
                               the keyboard. In text, a key name is
                               not enclosed in a box.

           KP n                A sequence such as KP1 indicates
                               that you must press the key labeled
                               with the number or character n on the
                               numeric keypad.




     x

 





              __________________________________________________________
              Convention__________Description___________________________

               . . .              A horizontal ellipsis in a figure
                                  or example indicates the following
                                  possibilities:

                                  o  Additional optional arguments in a
                                     statement have been omitted.

                                  o  The preceding item or items can be
                                     repeated one or more times.

                                  o  Additional parameters, values, or
                                     other information can be entered.

              .                   A vertical ellipsis indicates the
              .                   omission of items from a code example
              .                   or command format; the items are
                                  omitted because they are not important
                                  to the topic being described.

              ()                  In command format descriptions,
                                  parentheses indicate that you
                                  must enclose multiple choices in
                                  parentheses.

              []                  In commond format descriptions,
                                  brackets indicate optional choices.
                                  You can choose one or more items or
                                  no items. Do not type the brackets on
                                  the command line. However, you must
                                  include the brackets in the syntax for
                                  OpenVMS directory specifications and
                                  for a substring specification in an
                                  assignment statement.

              {}                  In command format descriptions, braces
                                  indicate required choices; you must
                                  choose at least one of the items
                                  listed. Do not type the braces on
                                  the command line.

              bold type           Bold type represents the introduction
                                  of a new term. It also represents the
                                  name of an argument, an attribute, or
                                  a reason.

                                                                      xi

 





           __________________________________________________________
           Convention__________Description___________________________

           Example             This typeface indicates code examples,
                               command examples, and interactive
                               screen displays. In text, this type
                               also identifies URLs, UNIX commands
                               and pathnames, PC-based commands and
                               folders, and certain elements of the C
                               programming language.

           italic type         Italic type indicates important
                               information, complete titles of
                               manuals or variables. Variables
                               include information that varies
                               in system output (for example,
                               Internal error number), in command
                               lines (/PRODUCER=name), and in
                               command parameters in text (where
                               dd represents the predefined code for
                               the device type).

           UPPERCASE TYPE      Uppercase indicates the name of
                               a command, routine, file, file
                               protection code, or the abbreviation
                               of a system privilege.

           -                   A hyphen at the end of a command
                               format description, command line,
                               or code line indicates that the
                               command or statement continues on
                               the following line.

           numbers             All numbers in text are assumed to
                               be decimal unless otherwise noted.
                               Nondecimal radixes-binary, octal, or
           ____________________hexadecimal-are_explicitly_indicated._









     xii

 









                                                                       1
        ________________________________________________________________

                              Preparing to Install the DECset Components



              This chapter describes the preparations and requirements
              necessary for installing one or more components of the
              DECset software.

                ________________________Note  ________________________

                DECset provides online release notes. HP strongly
                recommends that you read the release notes before
                proceeding with the installation. For information on
                accessing these release notes, see Section 1.3.

                When installing a DECset product update, read
                the Read Before Installing or Using HP DECset for
                OpenVMS Version n.nn letter before you begin.

                _____________________________________________________

        1.1 Required Operating System and Prerequisite Hardware and
            Software

              For a complete list of the required operating system
              components, current hardware requirements, and prereq-
              uisite and optional software and their required version
              numbers, see the HP DECset for OpenVMS Release Notes or
              the Software Product Description (SPD).

        1.2 License Registration (Alpha and VAX Only)

              A separate product license for DECset is not necessary
              on the OpenVMS I64 platform, as the product and its
              components are part of the base license for the Foundation
              Operating Environment (FOE).



                          Preparing to Install the DECset Components 1-1

 



     Preparing to Install the DECset Components
     1.2 License Registration (Alpha and VAX Only)

           However, before you install any DECset components on the
           OpenVMS Alpha or OpenVMS VAX platform, you must use the
           OpenVMS License Management Facility (LMF) to register the
           DECset software or component software licenses.

           The license registration information you need is contained
           in the Product Authorization Key (PAK) that is shipped
           with each component. The PAK is a paper certificate that
           contains information about the license.

           During the installation, you are asked if you have reg-
           istered the component license and loaded the appropriate
           authorization key. You must register and load your license
           before you start the installation in order to run the
           Installation Verification Procedure (IVP) and use the
           software.

              ________________________Note ________________________

              DECset components can be licensed individually, or a
              single license can encompass all components. The IVP
              requires that the applicable license be loaded.

              _____________________________________________________

           To register a license under OpenVMS, first log in to the
           system manager's account, SYSTEM. You then have a choice
           of two ways to perform the registration:

           o  Invoke the SYS$UPDATE:VMSLICENSE.COM procedure. When
              it prompts you for information, respond with data from
              your PAK.

           o  Enter the DCL command LICENSE REGISTER with the
              appropriate qualifiers that correspond to information
              on the PAK. Next, enter the LICENSE LOAD command with
              the appropriate qualifiers.

           For complete information on using the LMF, see the OpenVMS
           License Management Utility Manual.





     1-2 Preparing to Install the DECset Components

 



                              Preparing to Install the DECset Components
                                      1.3 Accessing Online Documentation

        1.3 Accessing Online Documentation

              Each DECset media kit includes online release notes for
              each component application as well as a journal of techni-
              cal notes entitled, the HP DECset for OpenVMS Cookbook for
              an Integrated Product Development Environment. The prompts
              to display or print this material during the installation
              are described in Section 2.5 and Section 2.6.

              To access this documentation, print the ASCII text files
              shown in Table 1-1, where nnn represents the version and
              update number (such as, 127 or 044).

              Table_1-1_Online_Documentation_Files_for_DECset___________

              Document________________File_Name_________________________

              HP DECset for           SYS$COMMON:[SYSHLP.EXAMPLES.DECSET]
              OpenVMS Cookbook        DECSET_COOKBOOK.TXT[1]
              for an Integrated
              Product Development
              Environment

              HP DECset Release       SYS$HELP:DECSETnnn.RELEASE_
              Notes[2]                NOTES[3]

              Environment Manager     SYS$HELP:ENVMGRnnn.RELEASE_NOTES
              Release Notes

              Code Management System  SYS$HELP:CMSnnn.RELEASE_NOTES
              Release Notes

              Module Management       SYS$HELP:MMSnnn.RELEASE_NOTES
              System Release Notes

              Digital Test Manager    SYS$HELP:DTMnnn.RELEASE_NOTES
              Release Notes

              Language-Sensitive      SYS$HELP:LSEnnn.RELEASE_NOTES
              Editor Release Notes

              [1]Alternate_formats_of_the_cookbook_(.PS,_.TXT,_and______

              .HTML) are also available.
              [2]This file is a pointer to the release notes for ENVMGR
              and all DECset elements or tools.
              [3]Alternate format of the release notes (.PS) is also
              available.

                                                (continued on next page)

                          Preparing to Install the DECset Components 1-3

 



     Preparing to Install the DECset Components
     1.3 Accessing Online Documentation

           Table_1-1_(Cont.)_Online_Documentation_Files_for_DECset___

           Document________________File_Name_________________________

           Source Code Analyzer    SYS$HELP:SCAnnn.RELEASE_NOTES
           Release Notes

           Performance and         SYS$HELP:PCAnnn.RELEASE_NOTES
           Coverage Analyzer
           Release_Notes_____________________________________________

           Online help also provides a pointer to the release notes
           file. After the installation, enter the following command
           line:

           $ HELP component RELEASE_NOTES <Return>

           In the previous command line, component represents the
           DECset component for which you want help, for example:

           $ HELP DECset RELEASE_NOTES <Return>

           In this example, DECset represents both DECset and the
           Environment Manager. The system displays a pointer to the
           release notes for each one.

     1.4 Installation Procedure Requirements

           This section describes various requirements for installing
           the DECset software on OpenVMS systems.

           If done individually, the installation of each component
           takes approximately 8 to 26 minutes, depending on the type
           of media, your system configuration, and whether you are
           performing a product upgrade or a new installation.

     1.4.1 Privileges

           Before installing any DECset component, you must be logged
           into an account that has either SETPRV or the following
           minimum privileges:

           o  CMKRNL

           o  WORLD

           o  SYSPRV

           Note that VMSINSTAL turns off BYPASS privilege at the
           start of the installation.

     1-4 Preparing to Install the DECset Components

 



                              Preparing to Install the DECset Components
                                 1.4 Installation Procedure Requirements

        1.4.2 System Parameters and Disk Space

              The HP DECset for OpenVMS Release Notes list the following
              system resources for each DECset component you are
              installing:

              o  The minimum amount of free disk space during and after
                 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

              These resources reflect the amount of space needed
              when installing all the options for each component. If
              some options are not installed, such as the DECwindows
              interface, the actual amount of space required may be
              reduced.

                ______________________ Caution ______________________

                Ensure that your system has the necessary global
                pagelet (Alpha/I64) or page (VAX) quotas and global
                section SYSGEN quotas prior to installation. In some
                situations, failure to do so can corrupt the DCL
                tables.

                _____________________________________________________

        1.4.3 VMSINSTAL Requirements

              When you invoke VMSINSTAL, it checks the following:

              o  Whether you are logged in to a privileged account (such
                 as SYSTEM)

              o  Whether any users are logged in to the system

              o  Whether you have adequate quotas for installation

              If VMSINSTAL detects any of these conditions, you will
              be asked whether you want to continue the installation.
              If you want to continue, type YES. If you want to stop
              the installation, press Return. See Section 2.5 for more
              details.

                          Preparing to Install the DECset Components 1-5

 



     Preparing to Install the DECset Components
     1.4 Installation Procedure Requirements

     1.4.4 Backing Up Your System Disk

           At the beginning of the installation, VMSINSTAL asks if
           you have backed up your system disk. HP recommends that
           you do a system backup before installing any software.

           Use the backup procedures established at your site. For
           details on performing a system disk backup, see the
           section on the OpenVMS Backup Utility in the OpenVMS
           System Manager's Manual.

     1.5 User Account Quotas and Privileges

           To use any DECset component, each account must meet
           minimum requirements for each of the following areas:

           o  AST limit (ASTLM)

           o  Buffered I/O byte count quota (BYTLM)

           o  Enqueue quota (ENQLM)

           o  Open file limit (FILLM)

           o  Timer queue entry limit (TQELM)

           o  Buffered I/O limit (BIOLM)

           o  Direct I/O limit (DIOLM)

           o  Subprocess limit (PRCLM)

           o  Working set default (WSDEF)

           o  Pagefile quota (PGFLQUOTA)

           o  Process privileges (TMPMBX and NETMBX)

           The HP DECset for OpenVMS Release Notes list specific
           requirements in each of these areas for each DECset
           component you are installing. Use the OpenVMS Authorize
           Utility (AUTHORIZE) to compare the current values of
           these quotas with the requirements for each component.
           The account used in the following example is the SYSTEM
           account:

           $ SET DEFAULT SYS$SYSTEM <Return>
           $ RUN AUTHORIZE <Return>
           UAF> SHOW SYSTEM <Return>

     1-6 Preparing to Install the DECset Components

 



                              Preparing to Install the DECset Components
                                  1.5 User Account Quotas and Privileges

              To change the values of these quotas, use the OpenVMS
              Authorize Utility MODIFY command. For example:

              UAF> MODIFY SYSTEM /ASTLM=100 <Return>

              For more information, see the OpenVMS System Management
              Utilities Reference Manual.

        1.6 Standard System Maintenance Procedures

              The following sections show how to do various standard
              procedures:

              o  Check UAF parameters.

              o  Calculate values for the GBLPAGES and GBLSECTIONS
                 system parameters.

              o  Change parameter values with the AUTOGEN command
                 procedure.

        1.6.1 Checking UAF Parameters

              Before you install DECset, you should check whether your
              account has sufficient quotas to perform the installation.
              You can check the quotas by entering the following command
              at the DCL prompt to invoke the AUTHORIZE utility:

              $ RUN SYS$SYSTEM:AUTHORIZE <Return>
              UAF> SHOW SYSTEM <Return>

              After checking your quotas, enter the EXIT command at the
              UAF> prompt to return to DCL level.

        1.6.2 Calculating the Values for GBLPAGES and GBLSECTIONS

              To install and run DECset, you must have sufficient shared
              memory space available. This memory space is expressed
              in terms of free global sections and free global pagelets
              (Alpha/I64) or pages (VAX). Each global section defines
              an area of virtual memory for shared use, and each global
              pagelet/page represents a set of contiguous-byte locations
              within a global section that is used for memory mapping
              and management.

                          Preparing to Install the DECset Components 1-7

 



     Preparing to Install the DECset Components
     1.6 Standard System Maintenance Procedures

           In order to determine whether there is adequate available
           memory, you must first find out how many free global
           pagelets/pages and global sections you have on your
           system. You can then use AUTOGEN if you need to increase
           the GBLSECTIONS or GBLPAGES system parameters.

           To determine the number of available global pagelets/pages
           and global sections on your system, invoke the OpenVMS
           Install Utility (INSTALL), and enter the following
           command:

           $ INSTALL LIST/GLOBAL/SUMMARY <Return>

                   Summary of Local Memory Global Sections

           393 Global Sections Used,  59856/33244 Global Pages Used/Unused

           When you enter this command, the system displays a
           summary of the number of global sections used, the number
           of global pages used, and the number of global pages
           available.

           You can then determine the number of available global
           sections by invoking SYSGEN, and entering the following
           commands:

           $ RUN SYS$SYSTEM:SYSGEN <Return>
           SYSGEN> USE CURRENT <Return>
           SYSGEN> SHOW GBLSECTIONS <Return>
           Parameter Name   Current   Default   Minimum   Maximum   Unit   Dynamic
           --------------   -------   -------   -------   --------  ----   -------
           GBLSECTIONS          512       250        60       4095  Sections
           SYSGEN> EXIT <Return>

           The first number displayed is the current number of global
           sections. Compare this to the number of global sections in
           use, as displayed by INSTALL. For example, CMS requires
           10 global sections. Therefore, if the number of global
           sections used (displayed by INSTALL) plus 10 exceeds the
           current number of global sections, you must increase the
           number of available global sections before you can install
           CMS.

           If the value of free global pagelets/pages and global
           sections is less than the recommended minimum values, you
           must increase the system parameter settings.

     1-8 Preparing to Install the DECset Components

 



                              Preparing to Install the DECset Components
                              1.6 Standard System Maintenance Procedures

              Section 1.6.3 describes the procedures for increasing
              these values using AUTOGEN.

        1.6.3 Changing System Parameter Values with AUTOGEN

              Use the AUTOGEN command procedure to change system
              parameters. AUTOGEN automatically adjusts values for
              parameters associated with the values you reset manually.
              To change system parameters with AUTOGEN, edit the
              following file:

              SYS$SYSTEM:MODPARAMS.DAT

              To add a new parameter, add a line to the file that
              includes both the name of the parameter and its value,
              as follows:

              WSMAX = 1024

              To modify incremental parameters such as GBLPAGES and
              GBLSECTIONS, use ADD_. The following example increases the
              global pagelet/pages setting by 2000:

              ADD_GBLPAGES = 2000

              When you set the page file quota, do not use a value that
              exceeds the amount of page file space available on the
              system.

              After you make all your changes, exit from the editor and
              execute the AUTOGEN procedure to recalculate your system
              parameters. Enter the following command at the DCL prompt:

              $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT <Return>

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

              For more information about using AUTOGEN, see the OpenVMS
              System Manager's Manual.


                          Preparing to Install the DECset Components 1-9

 









                                                                       2
        ________________________________________________________________

                                               Installing the DECset Kit



              The purpose of the DECset installation procedure is two-
              fold: to provide the installer a single point of entry for
              installing any or all DECset components, and to minimize
              the need for user interaction during installation.

              This collective procedure acts as a parent KITINSTAL
              procedure to the individual component installations. The
              procedure spawns off one subprocess per DECset component
              with default instructions on how to install the respective
              component.

              The DECset installation procedure does the following:

              o  Queries for which components to install

              o  Checks system resources required to perform serial
                 installations of the components

              o  Queries for responses to the questions asked as each
                 component is installed

              o  Installs each of the selected DECset components

              This chapter describes the preliminary installation
              steps performed for whatever installation you are
              planning. Whether you are performing a complete DECset
              installation, or any combination of components, these
              steps are completed first. The following chapters describe
              the subsequent installation steps for each of the DECset
              components.





                                           Installing the DECset Kit 2-1

 



     Installing the DECset Kit
     2.1 Prerequisite Software

     2.1 Prerequisite Software

           DECset requires a valid OpenVMS operating system
           configuration. If you plan to use the DECwindows interface
           for any component, you must also have the DECwindows Motif
           for OpenVMS software installed on your system.

           For detailed list of the supported combinations of
           operating system and windowing software, see the HP
           DECset for OpenVMS Release Notes. For a complete list
           of additional products compatible with this version
           of DECset, refer to the HP DECset for OpenVMS Software
           Product Description (SPD).

     2.2 Accessing the Online Release Notes

           When you invoke VMSINSTAL by specifying DECSETnnn, DECset
           copies online release notes for all the components to
           the SYS$HELP directory. If you invoke VMSINSTAL with the
           OPTIONS N parameter, DECset prompts you to display and
           print the release notes before installation begins.

           To obtain the release notes after the installation, print
           the following file, where nnn represents the version
           number (such as 127):

           $ PRINT SYS$HELP:DECSETnnn.RELEASE_NOTES

           This file provides an overview of the DECset release.
           See Section 1.3 for a listing of the individual component
           release note files.

              ________________________Note ________________________

              If you have not already, HP recommends that you
              read the release notes before continuing with the
              installation.

              _____________________________________________________






     2-2 Installing the DECset Kit

 



                                               Installing the DECset Kit
                                 2.3 Installation Procedure Requirements

        2.3 Installation Procedure Requirements

              Minimum free disk space, global pagelets, and global
              section requirements will depend on which components you
              choose to install through the collective procedure.

              The DECset requirements for free disk storage space are
              different during installation and after installation.
              Table 2-1 lists the storage requirements.

              Table_2-1_Disk_Space_Storage_Requirements_________________

                                      During
              Operating_System________Installation______After_Installation

              OpenVMS I64             200,000           100,500

              OpenVMS Alpha           200,000           100,500

              OpenVMS_VAX_____________123,000____________75,500_________

                ________________________Note  ________________________

                On systems with limited disk space, install two
                or three DECset components, then repeat the
                installation procedure until you have installed
                the entire kit. If you have all or part of DECset
                already installed, your space requirements may be
                less.

                _____________________________________________________

              In most cases, installation can be direct from the
              distribution media. If you need to copy the distribution
              kit onto disk, see Table 2-1 to determine how many free
              blocks you will need for the disk where you plan to copy
              the kit.

              To install DECset, you must be logged in to an account
              that has either SETPRV or the following minimum privi-
              leges:

              o  CMKRNL

              o  WORLD

              o  SYSPRV

                                           Installing the DECset Kit 2-3

 



     Installing the DECset Kit
     2.3 Installation Procedure Requirements

           Note that VMSINSTAL turns off BYPASS privileges at the
           start of installation.

     2.4 Backing Up Your System Disk

           At the beginning of the installation, VMSINSTAL asks if
           you have backed up your system disk. HP recommends that
           you do a system backup before installing any software.

           Use the backup procedures established at your site. For
           details on performing a system disk backup, see the
           section on the OpenVMS Backup Utility in the OpenVMS
           System Manager's Manual.

     2.5 Using VMSINSTAL

           After you log in to a privileged account to install
           DECset, set the default directory to SYS$UPDATE. Next,
           invoke the VMSINSTAL command procedure to install this
           product. An example of this procedure is shown in Steps 1
           and 2 of Section 2.6.

           The VMSINSTAL command procedure has the following syntax:

           @SYS$UPDATE:VMSINSTAL saveset-name device-name [option-
     list]

           VMSINSTAL is in the SYS$UPDATE directory. The elements
           that make up the VMSINSTAL command line are the VMSINSTAL
           command, saveset-name, device-name, and option-list. The
           elements that follow the command are defined as follows:

           saveset-name
           The installation name for the component. For DECset, use
           the following installation name:

           DECSETnnn

           The nnn represents the release number (such as DECSET127).

           To obtain the directory location of the DECset save sets
           on the CD, refer to the OpenVMS Software Product Library
           Master Index that accompanies the CD distribution kit.


     2-4 Installing the DECset Kit

 



                                               Installing the DECset Kit
                                                     2.5 Using VMSINSTAL

              Another method is to complete these steps before starting
              installation:

              1. Enter the following command to determine whether the CD
                 drive is already mounted:

                 $ SHOW DEVICE DKA400:

              2. If it is not mounted, enter the appropriate MOUNT
                 command to mount the CD (omit the /FOREIGN qualifier).

              3. To obtain the name of the save set, use a DIRECTORY
                 command specifying the directory file from the previous
                 command:

                 $ DIRECTORY DKA300:[DECSET127...]*.A

              device-name
              The name of the device on which you plan to mount the
              media and the directory containing the DECset save set.
              For example, DKA300: is the device name used in examples
              in this guide. The directory is [DECSETnnn], where nnn is
              the DECset release number.

              To specify the device name on the @VMSINSTAL command line,
              you might enter the following command:

              DKA300:[DECSET127.KIT]

              option-list
              The word OPTIONS followed by one or more of the option
              designators A, G, L, N, and R, as shown in Table 2-2. By
              default, none of these optional distribution, logging,
              or installation functions are activated unless the
              designators are specified with the OPTIONS key.










                                           Installing the DECset Kit 2-5

 



     Installing the DECset Kit
     2.5 Using VMSINSTAL

           Table_2-2_Installation_Option_Designators_________________

           Option_Name___________Description_________________________

           A      Auto_answer    Creates a file that contains
                                 your initial answers to VMSINSTAL
                                 questions and prompts. You can then
                                 use the option (and the answer file)
                                 to save time during a reinstallation
                                 (typically after upgrading your
                                 system).

           G      Get saveset    Copies kit save sets to DEVICE:[DIRECTORY].
                  G de-          Specifying a fast system storage
                  vice:[directory]evice can speed up installations,
                                 if you install from there. This can
                                 also serve as a group distribution
                                 resource.

           L      File Log       Logs all activity to the terminal
                                 during installation.

           N      Display or     Indicates that you want to see the
                  Print the      installation question on release
                  Release Notes  notes. If you do not include the
                                 N option, VMSINSTAL does not ask
                                 you about them. You should review
                                 the release notes before proceeding
                                 with an installation, in case they
                                 contain additional information about
                                 the installation.

                                 If you are restarting the instal-
                                 lation and have already reviewed
                                 the release notes, you can omit
                                 the N option. (The DECset release
                                 notes are available regardless,
                                 because VMSINSTAL copies them to the
                                 SYS$HELP directory.)

           R      Alternate      Lets you install DECset on a system
                  Root           other than that of the running
           ______________________system._____________________________

           For detailed information on these software installation
           options, see the OpenVMS System Manager's Manual. If you

     2-6 Installing the DECset Kit

 



                                               Installing the DECset Kit
                                                     2.5 Using VMSINSTAL

              specify more than one option, separate the options with
              commas. For example:

              OPTIONS A,N

              The following example invokes VMSINSTAL to install DECset
              and shows the system response. This example uses the
              OPTIONS N option to access the release notes during the
              installation.

              $ @VMSINSTAL DECSET127 DKA300:[DECSET127.KIT] OPTIONS N

                    OpenVMS Software Product Installation Procedure Version 8.2

              It is 10-JAN-2005 at 15:31.
              Enter a question mark (?) at any time for help.

              If you omit either the product name or device name,
              VMSINSTAL prompts you for them later in the installation
              procedure.

              When you invoke VMSINSTAL, it checks the following:

              o  Whether you are logged in to a privileged account. HP
                 recommends that you install software from the system
                 manager account with your default device and directory
                 set to SYS$UPDATE.

              o  Whether you have adequate quotas for installation.

              o  Whether the following conditions exist:

                 -  DECnet is up and running

                 -  Any users are logged into the system

                 If VMSINSTAL detects either of these conditions,
                 the procedure asks whether you want to continue the
                 installation. If you want to continue, enter YES
                 and press the Return key. If you want to stop the
                 installation, press Return. For example, you might
                 accept the default as follows:

                 %VMSINSTAL_W_ACTIVE, The following processes are still active:
                       DECW$SERVER_0
                       DECW$MWM
                 * Do you want to continue anyway [NO]? <Return>

                                           Installing the DECset Kit 2-7

 



     Installing the DECset Kit
     2.6 Installing DECset

     2.6 Installing DECset

           This section contains excerpts from the installation
           procedure and explains each step. Default values appear in
           brackets ([])  throughout the installation procedure. When
           you accept a default value or enter another selection,
           press Return to advance. You can obtain help information
           on any question by responding with a question mark (?).

              ________________________Note ________________________

              Whether you are installing one, several, or all
              DECset components, the installation process always
              starts with these steps. For details on the balance
              of the installation, see the chapters for the
              individual components you have selected. Other
              details can include language support, installation
              options, and so forth.

              _____________________________________________________

           To stop the installation procedure at any time, press
           Ctrl/Y. When you press Ctrl/Y, the installation procedure
           deletes all the files it has created up to that point
           and returns you to DCL level. If you want to retry the
           installation after pressing Ctrl/Y, you must proceed from
           Step 2.

           1. Log in to a privileged account and set your default
              device and directory to SYS$UPDATE.

                 .
                 .
                 .
              Username: SYSTEM <Return>
              Password:  <Return>
              $ SET DEFAULT SYS$UPDATE <Return>

           2. Invoke VMSINSTAL.

              In this example, DECset Version 12.7 is to be
              installed, and the release notes option is requested.



     2-8 Installing the DECset Kit

 



                                               Installing the DECset Kit
                                                   2.6 Installing DECset

                 $ @VMSINSTAL DECSET127 DKA300:[DECSET127.KIT] OPTIONS N

                       OpenVMS Software Product Installation Procedure Version 8.2

                 It is 10-JAN-2005 at 15:31.
                 Enter a question mark (?) at any time for help.

              3. Confirm system backup.

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

                 If you are satisfied with the backup of your system
                 disk, press Return. Otherwise, enter NO and press the
                 Return key to discontinue the installation.

                 * Where will the distribution volumes be mounted :

                 If you did not specify a device name when you invoked
                 VMSINSTAL (see Step 2), you are prompted for that
                 information. In either case, your answers enable the
                 installation to continue as follows:

                 The following products will be processed:

                   DECSET V12.7

                     Beginning installation of DECSET V12.7 at 15:31

                 %VMSINSTAL-I-RESTORE, Restoring product save set A...
                     Release notes included in this kit are always copied to SYS$HELP.
                    .
                    .
                    .

              4. Select a release notes option.

                 This step applies only if you specified OPTIONS N in
                 Step 2.

                 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>

                 o  Option 1-VMSINSTAL displays the release notes
                    online immediately. To terminate the display of a

                                           Installing the DECset Kit 2-9

 



     Installing the DECset Kit
     2.6 Installing DECset

                 component's release notes at any time, press Ctrl/C.

              o  Option 2 (the default)-VMSINSTAL prompts you for a
                 queue name. You can then enter a queue name or press
                 the Return key, which sends the file to the default
                 output print device.

                 * Queue name [SYS$PRINT]: <Return>

              o  Option 3-VMSINSTAL displays the release notes
                 online immediately. To terminate the display of a
                 component's release notes at any time, press Ctrl/C.
                 The VMSINSTAL procedure prompts you for a queue name
                 for printing the release notes. Either enter a queue
                 name or press the Return key to send the file to
                 the default output print device. The DECset release
                 notes are then copied to the SYS$HELP directory.

              o  Option 4-VMSINSTAL does not display or print the
                 release notes at this time. However, the release
                 notes are always copied to SYS$HELP, for future
                 use.

              Next, VMSINSTAL displays the following prompt:

              * Do you want to continue the installation [NO]?: YES <Return>
              %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to
              SYS$HELP.

              If you want to continue the installation, enter YES
              and press the Return key. If you enter NO (or press
              Return), VMSINSTAL discontinues the installation.
              In either case, VMSINSTAL moves the release notes to
              SYS$HELP.

           5. Select components to install.

              After displaying a component list and DECset copyright
              information, the installation program offers a menu
              selection to choose the components you want to install.

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

                        - DECset Collective Installation Procedure -

     2-10 Installing the DECset Kit

 



                                               Installing the DECset Kit
                                                   2.6 Installing DECset

                     This is the collective installation procedure for all of the
                     DECset components:
                     .
                     .
                     .
                     These are the options provided by this collective
                     installation procedure:

                     DECset components:

                                 - all the HP DECset for OpenVMS components
                                 - Language-Sensitive Editor (LSE)
                                 - Source Code Analyzer (SCA)
                                 - Code Management System (CMS)
                                 - Digital Test Manager (DTM)
                                 - Performance and Coverage Analyzer  (PCA)
                                 - Module Management System (MMS)
                                 - DECset Cookbook - PostScript Format
                                 - DECset Cookbook - HTML Format
                                 - DECset Cookbook - Text Format

                                 Please choose your option(s):

                 You can either elect to choose all the options, or you
                 can select a combination of options.

                   * Do you want all the DECset components [YES]?
                   * Are you sure you want to install all the options [YES]?

                 For example, if you choose LSE, SCA, and CMS, VMSINSTAL
                 displays the following:

                          .
                          .
                          .

                            These are the selections you made:

                                 - Language-Sensitive Editor
                                 - Source Code Analyzer
                                 - Code Management System

                   * Would you like a chance to select your options again [NO]?


                                          Installing the DECset Kit 2-11

 



     Installing the DECset Kit
     2.6 Installing DECset

              Note that the HP DECset for OpenVMS Cookbook for
              an Integrated Product Development Environment is
              also offered as an installation option. This guide
              provides examples of how to use the DECset tools in
              specific development environments and is provided
              online in ASCII text (.TXT), hypertext (.HTML), and
              PostScript (.PS) formats. If you choose to install the
              cookbook, the appropriate files are are placed in the
              SYS$COMMON:[SYSHLP.EXAMPLES.DECSET] directory after all
              of the selected component installations are complete.

           6. Install the ENVMGR component.

              No matter which components you selected for installa-
              tion, the ENVMGR component is installed:

              %DECSET-I-AGGREGATE, Checking resources required to install selected
              products.

              %DECSET-I-START_ENVMGR, The following questions relate to DECset ENVMGR
              installation

                 The DECset Environment Manager (ENVMGR) comprises:

                      . A run-time component used by DECset layered products,
                      . A DCL interface, and
                      . A DECwindows interface.

                 The DCL and DECwindows interface components are optional.

              * Do you want to install the interface components [YES]?

              Answer YES if you want DECset to install both the DCL
              and DECwindows interfaces for the ENVMGR component.

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

              The Installation Verification Procedure (IVP) procedure
              checks the integrity of the installed files. Choose
              YES to have VMSINSTAL perform the IVP automatically
              at the end of the installation procedure. If you
              choose NO, you can still run the IVP manually after
              the installation is complete.

              %DECSET-I-DONEASK, You have answered all the questions for DECset ENVMGR
              installation.

     2-12 Installing the DECset Kit

 



                                               Installing the DECset Kit
                                    2.7 Installing the DECset Components

        2.7 Installing the DECset Components

              After the Environment Manager installation is complete,
              the DECset installation procedure continues for the
              selected components. Details and examples for each DECset
              component can be found in the following chapters, such
              as Chapter 3, Installing the Code Management System for
              OpenVMS.

              The steps that follow are performed in order on each of
              the components for which you are licensed, whether you
              are installing the entire DECset product or just a few
              components. The installation performs the following steps:

              1. Prompts you for installation information for each
                 component you selected

              2. Performs the installation of each component

              3. Performs the IVP for each component

              4. Displays a summary of the IVP results for the selected
                 components

              See Appendix A for a sample full installation of DECset
              and its components.



















                                          Installing the DECset Kit 2-13

 









                                                                       3
        ________________________________________________________________

                       Installing the Code Management System for OpenVMS



              This chapter gives specific instructions on installing
              the Code Management System for OpenVMS (CMS) software. It
              continues the installation process from where it left off
              in Section 2.6 and describes how to run CMS on multiple
              nodes of an OpenVMS Cluster.

              For specific installation requirements related to CMS,
              such as account quotas and disk space, see the Code
              Management System for OpenVMS Release Notes. The CMS
              release notes, up to and including this version, can be
              found in SYS$HELP:CMSnnn.RELEASE_NOTES (where nnn is the
              version and update number, such as 044 for Version 4.4).

        3.1 Installation Procedure Requirements

              The DECset Environment Manager for OpenVMS (ENVMGR)
              is installed as part of the installation of the CMS
              component. ENVMGR
              consists of the following:

              o  Run-time component used by DECset layered products

              o  DCL interface

              o  DECwindows interface

              The DCL and DECwindows interface components are optional.

              If DTM is to be used with CMS, DTM requires the CMS files
              SYS$SHARE:CMSSHR.EXE and CMSPROSHR.EXE. Be aware that
              whenever you install or reinstall CMS (for example, as
              the result of an incorrect installation or upgrading to
              a higher version of CMS, you will also need to reinstall
              DTM.

                   Installing the Code Management System for OpenVMS 3-1

 



     Installing the Code Management System for OpenVMS
     3.1 Installation Procedure Requirements

           The CMS installation takes approximately 2 to 6 minutes,
           depending on the type of media, your system configuration,
           and whether you are performing a product upgrade or a new
           installation. Before installing CMS, you must have SETPRV
           privileges, or CMKRNL, WORLD, and SYSPRV privileges.

     3.2 User Account Quotas and Privileges

           To use CMS, each account must have a minimum of TMPMBX and
           NETMBX privileges, and the minimum user quota requirements
           listed in the Code Management System for OpenVMS Release
           Notes.

           Use the OpenVMS Authorize Utility (AUTHORIZE) to compare
           the current values of these quotas with the requirements
           for each component. The account used in the following
           example is the SYSTEM account:

           $ SET DEFAULT SYS$SYSTEM <Return>
           $ RUN AUTHORIZE <Return>
           UAF> SHOW SYSTEM <Return>

           To change the values of these quotas, use the OpenVMS
           Authorize Utility MODIFY command. For example:

           UAF> MODIFY SYSTEM /ASTLM=100 <Return>

           For more information, see the OpenVMS System Management
           Utilities Reference Manual.

     3.3 Installing CMS

           This section contains excerpts from the installation
           procedure and explains each step. Default values appear in
           brackets throughout the installation procedure.

           The following steps are performed as part of any DECset
           installation, and are accomplished before the subsequent
           component-specific steps described in this chapter:

           1. Log in to a privileged account and set your default
              device and directory to SYS$UPDATE.

           2. Invoke VMSINSTAL with a kit on CD-ROM.

           3. Confirm system backup.

           4. Select a release notes option.

     3-2 Installing the Code Management System for OpenVMS

 



                       Installing the Code Management System for OpenVMS
                                                      3.3 Installing CMS

              5. Select components to install.

              6. Install the ENVMGR component.

              See Section 2.6 for full descriptions of these universal,
              preliminary installation steps.

              To stop the installation procedure at any time, press
              Ctrl/Y. When you press Ctrl/Y, the installation procedure
              deletes all files it has created up to that point and
              returns you to DCL level. To retry the installation
              procedure after pressing Ctrl/Y, proceed from Step 2 in
              Section 2.6.

              7. Start the CMS installation.

                 %DECSET-I-START_CMS, The following questions relate to CMS
                 installation.
                 * Do you want to install the CMS DECwindows interface [YES]? <Return>

                 Answer YES if you want DECset to install interface.

                 If you are installing CMS on an OpenVMS Alpha or
                 OpenVMS I64 system, you are now asked if you want to
                 install support for the Extended File Specifications
                 feature.

                   On OpenVMS I64, CMS can support element names using Extended
                   File Specifications. The option exists to install CMS with or
                   without support for Extended File Specifications.

                 * Install Extended File Specifications support [YES]? <Return>

                 Answer YES if you want CMS to install the Extended File
                 Specifications support.

              8. Respond to license registration queries.

                 The installation procedure displays license information
                 about your product and then asks if you have registered
                 and loaded your product authorization key (PAK) for
                 CMS. The following is an example of such information:



                   Installing the Code Management System for OpenVMS 3-3

 



     Installing the Code Management System for OpenVMS
     3.3 Installing CMS

              Product:       VAXSET
              Producer:      DEC
              Version:       12.7

              Product:       CMS
              Producer:      DEC
              Version:       4.4

              * Is one of these authorization keys registered and loaded [YES]? <Return>

              If you are installing CMS on an OpenVMS Alpha or
              OpenVMS VAX system, and you have not registered and
              loaded your PAK, answer NO to this question. You must
              then stop the installation, register and load your PAK,
              then restart the installation.

              If you incorrectly answer YES, DECset enables you
              to complete the installation without running the
              Installation Verification Procedure (IVP). However,
              when you try to invoke CMS, you will receive a message
              indicating that you are not licensed to run the
              product.

           9. Select installation options.

              You are then asked the following question:

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

              The IVP runs tests to verify that the installation
              procedure was successful. Press Return to run the
              IVP after the installation. If you do not want to
              run the IVP, enter NO in response to the prompt. If
              the installation procedure determines that you have
              insufficient quotas to run the IVP, it tells you which
              quotas need to be increased and asks if you would like
              to complete the installation without running the IVP.
              For more IVP information, see Section 9.3.

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

              The directories SYS$HELP, SYS$MANAGER, SYS$MESSAGE,
              SYS$SHARE, SYS$SYSTEM, SYS$STARTUP, and SYS$TEST can
              contain previous versions of CMS files. These files are
              replaced during the installation with new files, but
              the old files are not automatically purged. Purging is

     3-4 Installing the Code Management System for OpenVMS

 



                       Installing the Code Management System for OpenVMS
                                                      3.3 Installing CMS

                 recommended. In response to the purging prompt, press
                 Return to purge the files, or enter NO to keep them.

             10. Read the informational messages.

                 The CMS installation procedure produces a number of
                 informational messages that report on the progress
                 of the installation. The success of this part of the
                 installation is indicated by the following message:

                 %DECSET-I-DONEASK, You have answered all the questions for CMS
                 installation

                 If CMS installation is successful, new or mod-
                 ified files are moved to their target directo-
                 ries. In addition, the SYS$HELP:HELPLIB.HLB and
                 SYS$LIBRARY:DCLTABLES.EXE files are updated to include
                 the new versions of the CMS help text and the CMS
                 command-line definition.

                ________________________Note  ________________________

                For a list of the CMS files installed (or modified)
                on your system, see Appendix B.

                _____________________________________________________

                 If you entered YES in response to the prompt that
                 requests a file purge in Step 7, previous versions
                 of the CMS files are now purged.

             11. Observe the Installation Verification Procedure.

                 If you chose to run the IVP, VMSINSTAL calls the IVP to
                 verify that CMS was successfully installed:

        %CMS-I-IVPBEGIN, Begin CMS V4.4 IVP
        %CMS-S-CREATED, CMS Library $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST] created
        %CMS-I-LIBIS, library is $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]
        %CMS-S-LIBSET, library set
        %CMS-I-LIBIS, library is $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]
        %CMS-S-LIBSET, library set
        -CMS-I-SUPERSEDE, library list superseded
        %CMS-S-CREATED, element $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]CMS$IVP_TEST.FILE created
        %CMS-S-RESERVED, generation 1 of element $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST] -
                CMS$IVP_TEST.FILE reserved

        Reservations in CMS Library $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]

                   Installing the Code Management System for OpenVMS 3-5

 



     Installing the Code Management System for OpenVMS
     3.3 Installing CMS

     CMS$IVP_TEST.FILE
         (1)   SYSTEM     1      10-JAN-2005 15:47:49 ""
     %CMS-S-GENCREATED, generation 2 of element $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]
             CMS$IVP_TEST.FILE created
     -CMS-I-NOCHANGES, no changes
     %CMS-I-VERCLS, class list verified
     %CMS-I-VERCMD, command list verified
     %CMS-I-VERELE, element list verified
     %CMS-I-VERGRP, group list verified
     %CMS-I-VERRES, reservation list verified
     %CMS-I-VERFRE, internal free space list verified
     %CMS-I-VERFRE, internal free space list verified
     %CMS-I-VERFRE, internal free space list verified
     %CMS-I-VERFRE, internal free space list verified
     %CMS-I-VERFRE, internal free space list verified
     %CMS-I-VERFRE, internal free space list verified
     %CMS-I-VERFRE, internal free space list verified
     %CMS-I-VERARC, archive control block verified
     %CMS-I-VER2, internal contiguous space verified
     %CMS-I-VERCON, control file verified
     %CMS-I-VEREDF, element $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]CMS$IVP_TEST.FILE verified
     %CMS-I-VEREDFS, element data files verified
     %CMS-S-VERIFIED, library $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST] verified
     %CMS-S-FETCHED, generation 1 of element $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST] -
             CMS$IVP_TEST.FILE fetched
     %CMS-I-FILEXISTS, file already exists, $2$DKA300:[SYS0.SYSUPD.DECSET127]CMS$IVP_TEST.FILE;2 created
     %CMS-S-FETCHED, generation 2 of element $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST] -
             CMS$IVP_TEST.FILE fetched
     %CMS-S-IDENTICAL, files are identical
     %CMS-S-CREATED, class $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]CL1 created
     %CMS-S-GENINSERTED, generation 1 of element $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST] -
             CMS$IVP_TEST.FILE inserted into class $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]CL1
     %CMS-S-CREATED, class $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]CL2 created
     %CMS-S-GENINSERTED, generation 2 of element $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST] -
             CMS$IVP_TEST.FILE inserted into class $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]CL2
     %CMS-S-FETCHED, generation 2 of element $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST] -
             CMS$IVP_TEST.FILE fetched

     Elements in CMS Library $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]

     CMS$IVP_TEST.FILE ""

     Element generations in CMS Library
             $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]

     3-6 Installing the Code Management System for OpenVMS

 



                       Installing the Code Management System for OpenVMS
                                                      3.3 Installing CMS

        CMS$IVP_TEST.FILE
          2     10-JAN-2005 15:47:50 SYSTEM ""
          1     10-JAN-2005 15:47:48 SYSTEM ""

        Classes in CMS Library $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]

        CL1             "Test1"
        CL2             "Test2"

        Element generations in CMS Library $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]

        CMS$IVP_TEST.FILE/2
        %CMS-S-GENREMOVED, generation 2 of element $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST] -
                CMS$IVP_TEST.FILE removed from class $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]CL2
        %CMS-S-DELETED, class $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]CL2 deleted
        %CMS-S-GENREMOVED, generation 1 of element $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST] -
                CMS$IVP_TEST.FILE removed from class $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]CL1
        %CMS-S-DELETED, class $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]CL1 deleted
        %CMS-S-CREATED, group $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]GR1 created
        %CMS-S-CREATED, group $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]GR2 created
        %CMS-S-INSERTED, group $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]GR1 inserted into group
        $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]GR2
        %CMS-S-REMOVED, group $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]GR1 removed from group
        $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]GR2
        %CMS-S-MODIFIED, group $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]GR1 modified

        Groups in CMS Library $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]

        GR2                 GR3

        %CMS-S-IVPSUCCESS, CMS V4.4 IVP completed successfully
        %CMS-I-IVPEND, End Installation Verification Procedure

             12. End the installation procedure.

                 If you selected only the CMS installation, the
                 VMSINSTAL procedure ends at the same time, as follows:

                 %DECSET-I-DONECMS, The installation of CMS V4.4 completed

                    VMSINSTAL procedure done at 15:49

                 When the product installation procedure is complete,
                 you can choose to install more products or log out.
                 If you removed any media from the console drive before
                 beginning the installation, you must replace it now.

                   Installing the Code Management System for OpenVMS 3-7

 



     Installing the Code Management System for OpenVMS
     3.3 Installing CMS

              The VMSINSTAL procedure deletes or changes entries in
              the process symbol tables during the installation.
              Therefore, if you are going to continue using the
              system manager's account and you want to restore these
              symbols, you must log out and log in again.


     3.4 Installing CMS on an OpenVMS Cluster

           If you want to run CMS on multiple nodes of an OpenVMS
           Cluster, first check to see that you have the appropriate
           software license. Then, follow these steps after
           installing CMS:

           1. On OpenVMS Alpha and OpenVMS VAX systems, enter the
              LICENSE LOAD command to activate the license on
              each node in the OpenVMS Cluster on which CMS is
              to be executed, as described in the OpenVMS License
              Management Utility Manual. On OpenVMS I64 systems,
              ensure that the appropriate Operating Environment (OE)
              has been installed.

           2. Run SYS$STARTUP:CMS$STARTUP.COM on each node of the
              cluster that has a software license. In addition, you
              must add the following line to your system startup
              procedure, SYS$MANAGER:SYSTARTUP_VMS.COM:

              $ @SYS$STARTUP:CMS$STARTUP.COM

              To use the product on other nodes in the OpenVMS
              Cluster, you must replace the version of the DCL tables
              installed on the other OpenVMS Cluster nodes. To do
              this, perform the following steps:

              a. Log in to a node on the cluster.

              b. Enter the following command at the DCL prompt:

                 $ INSTALL REPLACE SYS$LIBRARY:DCLTABLES.EXE <Return>

              c. Repeat Steps a and b for each node of the cluster.

           See Chapter 9 for information on post-installation
           procedures.

     3-8 Installing the Code Management System for OpenVMS

 









                                                                       4
        ________________________________________________________________

                         Installing the Digital Test Manager for OpenVMS



              This chapter gives specific instructions on installing
              the Digital Test Manager for OpenVMS (DTM) software. It
              continues the installation process from where it left off
              in Section 2.6 and describes how to run DTM on multiple
              nodes of an OpenVMS Cluster.

              For specific installation requirements related to DTM,
              such as account quotas and disk space, see the Digital
              Test Manager for OpenVMS Release Notes. The DTM release
              notes, up to and including this version, can be found in
              SYS$HELP:DTMnnn.RELEASE_NOTES (where nnn is the version
              and update number, such as 043 for Version 4.3).

        4.1 Installation Procedure Requirements

              The DECset Environment Manager for OpenVMS (ENVMGR)
              is installed as part of the installation of the DTM
              component. ENVMGR
              consists of the following:

              o  Run-time component used by DECset layered products

              o  DCL interface

              o  DECwindows interface

              The DCL and DECwindows interface components are optional.

              If DTM is to be used with CMS, DTM requires the CMS files
              SYS$SHARE:CMSSHR.EXE and CMSPROSHR.EXE. Be aware that
              whenever you install or reinstall CMS (for example, as
              the result of an incorrect installation or upgrading to a
              higher version of CMS), you will also need to reinstall
              DTM.

                     Installing the Digital Test Manager for OpenVMS 4-1

 



     Installing the Digital Test Manager for OpenVMS
     4.1 Installation Procedure Requirements

           The installation of DTM takes approximately 1 to 3
           minutes, depending on the type of media, your system
           configuration, and whether you are performing a product
           upgrade or a new installation. Before installing DTM, you
           must have SETPRV privileges, or CMKRNL, WORLD, and SYSPRV
           privileges.

     4.2 User Account Quotas and Privileges

           To use DTM, each account must have TMPMBX and NETMBX
           privileges, and the minimum user quota requirements listed
           in the Digital Test Manager for OpenVMS Release Notes.

           Use the OpenVMS Authorize Utility (AUTHORIZE) to compare
           the current values of these quotas with the requirements
           for DTM. For example, the account used in the following
           example is the SYSTEM account:

           $ SET DEFAULT SYS$SYSTEM
           $ RUN AUTHORIZE
           UAF> SHOW SYSTEM

           To change the values of these quotas, use the OpenVMS
           Authorize Utility MODIFY command. For example:

           UAF> MODIFY SYSTEM /ASTLM=100 <Return>

           For more information, see the OpenVMS System Management
           Utilities Reference Manual.

     4.3 Installing DTM

           This section contains excerpts from the installation
           procedure and explains each step. Default values appear in
           brackets throughout the installation procedure.

           The following steps are performed as part of any DECset
           installation, and are accomplished before the subsequent
           component-specific steps described in this chapter:

           1. Log in to a privileged account and set your default
              device and directory to SYS$UPDATE.

           2. Invoke VMSINSTAL with a kit on CD-ROM.

           3. Confirm system backup.

           4. Select a release notes option.

     4-2 Installing the Digital Test Manager for OpenVMS

 



                         Installing the Digital Test Manager for OpenVMS
                                                      4.3 Installing DTM

              5. Select components to install.

              6. Install the ENVMGR component.

              See Section 2.6 for full descriptions of these universal,
              preliminary installation steps.

              To stop the installation procedure at any time, press
              Ctrl/Y. When you press Ctrl/Y, the installation procedure
              deletes all files it has created up to that point and
              returns you to DCL level. If you want to retry the
              installation procedure after pressing Ctrl/Y, you must
              proceed from Step 2.

              7. Respond to license registration queries.

                 The installation procedure displays license information
                 about your product and then asks if you have registered
                 and loaded your product authorization key (PAK) for
                 DTM. The following is an example of such information:

                 Product:       VAXSET
                 Producer:      DEC
                 Version:       12.7

                 Product:       DTM
                 Producer:      DEC
                 Version:       4.3

                 * Is one of these authorization keys registered and loaded? [YES]? <Return>

                 If you are installing DTM on an OpenVMS Alpha or
                 OpenVMS VAX system, and you have not registered and
                 loaded your PAK, answer NO to this question. You must
                 register and load your PAK to successfully complete the
                 installation.

                 If you incorrectly answer YES, DECset enables you
                 to complete the installation without running the
                 Installation Verification Procedure (IVP). However,
                 when you try to invoke DTM, you will receive a message
                 indicating that you are not licensed to run the
                 product.

              8. Select installation options.

                     Installing the Digital Test Manager for OpenVMS 4-3

 



     Installing the Digital Test Manager for OpenVMS
     4.3 Installing DTM

              You are then asked the following question:

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

              The IVP runs tests to verify that the installation
              was successful. If the IVP determines that you have
              insufficient quotas to run the IVP, it tells you which
              quotas need to be increased and asks if you would like
              to complete the installation without running the IVP.
              Press Return to run the IVP after the installation. If
              you do not want to run the IVP, enter NO at the prompt.

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

              The directories SYS$EXAMPLES, SYS$HELP, SYS$LIBRARY,
              SYS$MANAGER, and SYS$SYSTEM might contain previous
              versions of DTM files. These files are replaced during
              the installation with new files, but the old files are
              not automatically purged. Purging is recommended. In
              response to the purging prompt, press Return to purge
              the files or enter NO to keep them.

           9. Read the informational messages.

              The DTM installation procedure produces a number of
              informational messages that report on the progress
              of the installation. The success of this part of the
              installation is indicated by the following message:

              %DECSET-I-DONEASK, You have answered all the questions for Digital Test
              Manager installation

              If the installation procedure is successful, the new or
              modified files are moved to their target directories.

              The SYS$HELP:HELPLIB.HLB and SYS$LIBRARY:DCLTABLES.EXE
              files are updated to include the new versions of the
              DTM Help text and the DTM command-line definition.

              If you entered YES in response to the prompt that
              requests a file purge, previous versions of the DTM
              files are now purged.

          10. Observe the installation verification procedure.

     4-4 Installing the Digital Test Manager for OpenVMS

 



                         Installing the Digital Test Manager for OpenVMS
                                                      4.3 Installing DTM

                 If you chose to run the IVP, VMSINSTAL calls the IVP to
                 verify that DTM was installed successfully:

        %DTM-I-BEGINIVP, Beginning DTM V4.3 IVP
        %DTM-S-CREATED, Digital Test Manager library $2$DKA300:[SYS0.SYSUPD.DECSET127.DTMTEST] created
        %DTM-S-LIBIS, Digital Test Manager  library is $2$DKA300:[SYS0.SYSUPD.DECSET127.DTMTEST]
        %DTM-I-DEFAULTED, benchmark file name defaulted to TESTX.BMK
        %DTM-S-CREATED, test description TESTX created
        %DTM-S-MODIFIED, test description TESTX modified
        %DTM-I-DEFAULTED, benchmark file name defaulted to DECWX.BMK
        %DTM-I-DEFAULTED, template file name defaulted to DECWX.SESSION
        %DTM-S-CREATED, test description DECWX created

        Test Descriptions in Digital Test Manager Library
        $2$DKA300:[SYS0.SYSUPD.DECSET127.DTMTEST]

        DECWX           "decwindows test"
            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 Specified
        %DTM-S-CREATED, symbol variable VAR1 created
        %DTM-S-MODIFIED, variable VAR1 modified

        Variables in Digital Test Manager Library $2$DKA300:[SYS0.SYSUPD.DECSET127.DTMTEST]

        VAR1            "first variable"
            Value = NEWVALUE
        %DTM-S-CREATED, group GROUP1 created

        Groups in Digital Test Manager Library $2$DKA300:[SYS0.SYSUPD.DECSET127.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

        Groups in Digital Test Manager Library $2$DKA300:[SYS0.SYSUPD.DECSET127.DTMTEST]

        GROUP1              GROUP2
        %DTM-S-CREATED, collection COLL1 created

                     Installing the Digital Test Manager for OpenVMS 4-5

 



     Installing the Digital Test Manager for OpenVMS
     4.3 Installing DTM

     Collections in Digital Test Manager Library $2$DKA300:[SYS0.SYSUPD.DECSET127.DTMTEST]

     COLL1          1 test    10-JAN-2005 15:48:20
            Command: CREATE COLLECTION/NOVERIFY COLL1 TESTX "test collection"
            Status: not run

     %DTM-S-DELETED, collection COLL1 deleted
     %DTM-I-DELETED, test_description DECWX deleted
     %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 verified
     %DTM-I-VERTD, test description list verified
     %DTM-I-VERVAR, variables list verified
     %DTM-I-VERARC, archive list verified
     %DTM-I-VERHEAD, user header information verified
     %DTM-I-VERSPACE, contiguous space verified
     %DTM-I-VERCOLDIR, collection directory structure verified
     %DTM-S-VERIFIED, Digital Test Manager library $2$DKA300:[SYS0.SYSUPD.DECSET127.DTMTEST]
     verified
     %DTM-I-ENDIVP, DTM V4.3 IVP completed successfully.

          11. End the installation procedure.

              If you selected only the DTM installation, the
              VMSINSTAL procedure ends at the same time, as follows:

                 Installation of DTM V4.3 completed at 15:49

                 VMSINSTAL procedure done at 15:49

              When the product installation procedure is complete,
              you can choose to install more products or log out.
              If you removed any media from the console drive before
              beginning the installation, you must replace it now.



     4-6 Installing the Digital Test Manager for OpenVMS

 



                         Installing the Digital Test Manager for OpenVMS
                                                      4.3 Installing DTM

                 The VMSINSTAL procedure deletes or changes entries in
                 the process symbol tables during the installation.
                 Therefore, if you are going to continue using the
                 system manager's account and you want to restore these
                 symbols, you must log out and log in again.


        4.4 Installing DTM on an OpenVMS Cluster

              If you want to run DTM on multiple nodes of an OpenVMS
              Cluster, first check to see that you have the appropriate
              software license. Then, follow these steps after
              installing DTM:

              1. On OpenVMS Alpha and OpenVMS VAX systems, enter the
                 LICENSE LOAD command to activate the license on each
                 node in the OpenVMS Cluster on which DTM is to be run,
                 as described in the OpenVMS License Management Utility
                 Manual. On OpenVMS I64 systems, ensure the appropriate
                 Operating Environment (OE) is installed.

              2. Run SYS$STARTUP:DTM$STARTUP.COM on each node of the
                 cluster that has a software license. In addition, you
                 must add the following line to your system startup
                 procedure, SYS$MANAGER:SYSTARTUP_VMS.COM:

                 $ @SYS$STARTUP:DTM$STARTUP.COM

                 To use the product on other nodes in the OpenVMS
                 Cluster, you must replace the version of the DCL tables
                 installed on the other OpenVMS Cluster nodes. To do
                 this, perform the following steps:

                 a. Log in to a node on the cluster.

                 b. Enter the following command at the DCL prompt:

                    $ INSTALL REPLACE SYS$LIBRARY:DCLTABLES.EXE <Return>

                 c. Repeat Steps a and b for each node of the cluster.

              See Chapter 9 for information on post-installation
              procedures.


                     Installing the Digital Test Manager for OpenVMS 4-7

 



     Installing the Digital Test Manager for OpenVMS
     4.5 Running DTM on a Mixed OpenVMS Cluster

     4.5 Running DTM on a Mixed OpenVMS Cluster

           You might want to run DTM on a mixed OpenVMS Cluster that
           supports various versions of OpenVMS software on different
           nodes. If so, you cannot install DTM on only one system.
           For example, if DTM is to be used for interactive terminal
           testing on an OpenVMS Cluster comprising two systems, DTM
           must be installed on both systems.





































     4-8 Installing the Digital Test Manager for OpenVMS

 









                                                                       5
        ________________________________________________________________

                    Installing the Language-Sensitive Editor for OpenVMS



              This chapter gives specific instructions on installing the
              Language-Sensitive Editor for OpenVMS (LSE) software. It
              continues the installation process from where it left off
              in Section 2.6 and describes how to run LSE on multiple
              nodes of an OpenVMS Cluster. This chapter also includes
              some post-installation information.

              For specific installation requirements related to LSE,
              such as account quotas and disk space, see the Language-
              Sensitive Editor for OpenVMS Release Notes. The LSE
              release notes, up to and including this version, can be
              found in SYS$HELP:LSEnnn.RELEASE_NOTES (where nnn is the
              version and update number, such as 050 for Version 5.0).

        5.1 Installation Procedure Requirements

              The DECset Environment Manager for OpenVMS (ENVMGR)
              is installed as part of the installation of the LSE
              component. ENVMGR consists of the following:

              o  Run-time component used by DECset layered products

              o  DCL interface

              o  DECwindows interface

              The DCL and DECwindows interface components are optional.

              The LSE installation takes approximately 3 to 10 minutes,
              depending on the type of media, your system configuration,
              and whether you are performing a product upgrade or a new
              installation. Before installing LSE, you must have SETPRV
              privileges, or CMKRNL, WORLD, and SYSPRV privileges.

                ______________________ Caution ______________________

                Ensure that your system has the necessary global
                page and global section SYSGEN quotas for the

                Installing the Language-Sensitive Editor for OpenVMS 5-1

 



     Installing the Language-Sensitive Editor for OpenVMS
     5.1 Installation Procedure Requirements

              installation. In some situations, failure to do
              so can corrupt the DCL tables.

              _____________________________________________________


     5.2 User Account Quotas and Privileges

           To use LSE, each account must have TMPMBX and NETMBX
           privileges, and the minimum user quota requirements listed
           in the Language-Sensitive Editor for OpenVMS Release
           Notes.

           Use the OpenVMS Authorize Utility (AUTHORIZE) to compare
           the current values of these quotas with the requirements
           for LSE. For example, the account used in the following
           example is the SYSTEM account:

           $ SET DEFAULT SYS$SYSTEM <Return>
           $ RUN AUTHORIZE <Return>
           UAF> SHOW SYSTEM <Return>

           To change the values of these quotas, use the OpenVMS
           Authorize Utility MODIFY command. For example:

           UAF> MODIFY SYSTEM /ASTLM=100 <Return>

           For more information, see the OpenVMS System Management
           Utilities Reference Manual.

           After you log in to a privileged account to install SCA,
           invoke VMSINSTAL, the command procedure that installs
           this product. For an example of this procedure and a
           description of its options, see Section 2.5.

     5.3 Installing LSE

           This section contains excerpts from the installation
           procedure and explains each step. Default values appear in
           brackets throughout the installation procedure.

           The following steps are performed as part of any DECset
           installation, and are accomplished before the component-
           specific steps described in this chapter:

           1. Log in to a privileged account and set your default
              device and directory to SYS$UPDATE.

           2. Invoke VMSINSTAL with a kit on CD-ROM.

     5-2 Installing the Language-Sensitive Editor for OpenVMS

 



                    Installing the Language-Sensitive Editor for OpenVMS
                                                      5.3 Installing LSE

              3. Confirm system backup.

              4. Select a release notes option.

              5. Select components to install.

              6. Install the ENVMGR component.

              See Section 2.6 for full descriptions of these universal,
              preliminary installation steps.

              To stop the installation procedure at any time, press
              Ctrl/Y. When you press Ctrl/Y, the installation procedure
              deletes all files it has created up to that point and
              returns you to DCL level. If you want to retry the
              installation procedure after pressing Ctrl/Y, you must
              proceed from Step 2.

              7. Respond to license registration queries.

                 The installation procedure displays license information
                 about your product and then asks if you have registered
                 and loaded your product authorization key (PAK) for
                 LSE. The following is an example of such information:

                 %DECSET-I-START_LSE, The following questions relate to LSE
                 installation.

                 Product:       VAXSET
                 Producer:      DEC
                 Version:       12.7

                 Product:       LSE
                 Producer:      DEC
                 Version:       5.0

                 * Is one of these authorization keys registered and loaded [YES]? <Return>

                 If you are installing LSE on an OpenVMS Alpha or
                 OpenVMS VAX system, and you have not registered and
                 loaded your PAK, answer NO to this question. You must
                 then stop the installation, register and load your PAK,
                 then restart the installation.

                 If you incorrectly answer YES, you will receive a
                 message indicating that you are not licensed to run
                 the product, and the installation procedure will be
                 terminated.

                Installing the Language-Sensitive Editor for OpenVMS 5-3

 



     Installing the Language-Sensitive Editor for OpenVMS
     5.3 Installing LSE

           8. Select installation options.

              * 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,
              LSE$EXAMPLE, and SYS$SYSTEM may contain previous
              versions of LSE files. These files are replaced during
              the installation with new files, but the old files are
              not automatically purged. Purging is recommended. In
              response to the purging prompt, press Return to purge
              the files or enter NO to keep them.

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

              The IVP runs tests to verify that the installation
              was successful. Press Return to run the IVP after the
              installation. If you do not want to run the IVP, enter
              NO in response to the prompt. For more IVP information,
              see Section 9.3.

           9. Install LSE source files option.

              The installation procedure asks you if you want to
              install LSE source files. The following OpenVMS I64
              example shows these files occupying approximately
              16,000 blocks of space.

               Please note that the total system disk space consumed by the unsupported
               LSE source files is approximately 16,000 blocks.  HP recommends not
               to answer yes to the following prompt if you are constrained by the free
               space available on your system disk.

              * Would you like to install the unsupported LSE source files [YES]? <Return>

               The files will be installed in SYS$SYSROOT[SYSHLP.EXAMPLES.LSE]

          10. Select default command language option.

              1 line written to file SYS$SYSDEVICE:[SYS0.SYSUPD.DECSET nnn]
              COMM_LANG.OUT;1

              * Do you want default command language to be VMSLSE or PORTABLE [VMSLSE]?
     <Return>

              To select the PORTABLE command language as your system-
              wide default command language, type PORTABLE and press
              Return.

     5-4 Installing the Language-Sensitive Editor for OpenVMS

 



                    Installing the Language-Sensitive Editor for OpenVMS
                                                      5.3 Installing LSE

                 To select the VMSLSE command language, which is
                 compatible with the command language available in
                 versions of LSE prior to Version 4.0, press Return
                 to accept the default.

                 Individual users can override the system default
                 command language. See the Guide to DIGITAL Language-
                 Sensitive Editor for OpenVMS Systems for more
                 information.

             11. Select language support.

                 Templates for some languages are shipped on the LSE
                 kit. The installation procedure displays the names
                 of the language templates available on the LSE kit
                 and asks which ones should be installed. Language
                 templates for other layered products that support
                 LSE not mentioned in this installation procedure are
                 provided in the installation kits for those layered
                 products.

                 Language templates for Ada, Ada95, BASIC, BLISS, C, COBOL, C++, FORTRAN,
                 FORTRAN 90, HTML, Java, MACRO, Pascal, and PL/I as well as templates for
                 the LSE command languages are included in this kit. Templates for other
                 languages that support LSE and are not mentioned are provided in the
                 installation kits for those languages.

                 Please choose the languages for which you would like to install support:

                 * Do you want to install language support for ADA [YES]? <Return>
                 * Do you want to install language support for ADA95 [YES]? <Return>
                 * Do you want to install language support for BASIC [YES]? <Return>
                 * Do you want to install language support for BLISS [YES]? <Return>
                 * Do you want to install language support for C [YES]? <Return>
                 * Do you want to install language support for COBOL [YES]? <Return>
                 * Do you want to install language support for CXX [YES]? <Return>
                 * Do you want to install language support for FORTRAN [YES]? <Return>
                 * Do you want to install language support for F90 [YES]? <Return>

                 * Do you want to install language support for HTML [YES]? <Return>
                 * Do you want to install language support for Java [YES]? <Return>




                Installing the Language-Sensitive Editor for OpenVMS 5-5

 



     Installing the Language-Sensitive Editor for OpenVMS
     5.3 Installing LSE

              * Do you want to install language support for MACRO [YES]? <Return>
              * Do you want to install language support for PASCAL [YES]? <Return>
              * Do you want to install language support for PLI [YES]? <Return>
              * Do you want to install language support for LSE [YES]? <Return>
              * Do you want to install language support for PLSE [YES]? <Return>

          12. Read the informational messages.

              The LSE installation procedure produces a number of
              informational messages that report on the progress of
              the installation.

              The success of this part of the installation is
              indicated by the following message:

              %DECSET-I-DONEASK, You have answered all the questions for LSE
              installation
                  .
                  .
                  .
              This installation added or modified the following files:

              If the installation procedure is successful, new or
              modified files are moved to their target directories.

              The SYS$HELP:HELPLIB.HLB and SYS$LIBRARY:DCLTABLES.EXE
              files are updated to include the new versions of the
              LSE HELP text and the LSEDIT command-line definition.
              For a list of the added or modified files, see
              Appendix B.

              If you entered YES in response to the prompt that
              requests a file purge at Step 8, previous versions
              of the LSE files are now purged.

          13. Observe the Installation Verification Procedure.

              If you chose to run the IVP, VMSINSTAL now calls the
              IVP to verify that LSE was installed successfully:

              %LSE-I-BEGINIVP, Beginning LSE V5.0 IVP
              36 lines written to file DISK:[SYSTEM.SCRATCH]LSE$IVP.LIS;1

              %LSE-I-ENDIVP, LSE V5.0 IVP completed successfully.
              36 lines written to file $1$DIA3:[VMS$COMMON.SYSMGR]LSE$IVP.LIS;1

          14. End the installation procedure.

     5-6 Installing the Language-Sensitive Editor for OpenVMS

 



                    Installing the Language-Sensitive Editor for OpenVMS
                                                      5.3 Installing LSE

                 If you selected only the LSE installation, the
                 VMSINSTAL procedure ends at the same time, as follows:

                 %DECSET-I-DONELSE, The installation of LSE completed

                    VMSINSTAL procedure done at 15:49

                 When the product installation procedure is complete,
                 you can choose to install more products or log out.
                 If you removed any media from the console drive before
                 beginning the installation, you should replace it now.

                 The VMSINSTAL procedure deletes or changes entries in
                 the process symbol tables during the installation.
                 Therefore, if you are going to continue using the
                 system manager's account and you want to restore these
                 symbols, you should log out and log in again.

        5.4 Installing LSE on an OpenVMS Cluster

              If you want to run LSE on multiple nodes of an OpenVMS
              Cluster, first check to see that you have the appropriate
              software license. Then, follow these steps after
              installing LSE:

              1. On OpenVMS Alpha and OpenVMS VAX systems, enter the
                 LICENSE LOAD command to activate the license on
                 each node in the OpenVMS Cluster on which LSE is
                 to be executed, as described in the OpenVMS License
                 Management Utility Manual. On OpenVMS I64 systems,
                 ensure the appropriate Operating Environment (OE) is
                 installed.

              2. Run SYS$STARTUP:LSE$STARTUP.COM on each node of the
                 cluster that has a software license.

                 To ensure that LSE is installed each time the system
                 is bootstrapped, include the following line in
                 SYS$STARTUP:SYSTARTUP_VMS.COM (the site-specific
                 startup file):

                 @SYS$STARTUP:LSE$STARTUP.COM



                Installing the Language-Sensitive Editor for OpenVMS 5-7

 



     Installing the Language-Sensitive Editor for OpenVMS
     5.4 Installing LSE on an OpenVMS Cluster

           3. To use the product on other nodes in the OpenVMS
              Cluster, you must replace the version of the DCL tables
              installed on the other OpenVMS Cluster nodes. To do
              this, perform the following steps:

              a. Log in to a node on the cluster.

              b. Run INSTALL, then enter the following command:

                 INSTALL> REPLACE SYS$LIBRARY:DCLTABLES.EXE <Return>

              c. Repeat Steps a and b for each node of the cluster.

              ________________________Note ________________________

              The installation procedure modifies the DCL command
              table so the LSEDIT command is recognized and
              processed. However, the previous command table is
              still in effect for those users who are currently
              logged in. All logged-in users who want to use the
              LSEDIT command must log out of the system and log in
              again.

              _____________________________________________________





















     5-8 Installing the Language-Sensitive Editor for OpenVMS

 









                                                                       6
        ________________________________________________________________

                     Installing the Module Management System for OpenVMS



              This chapter gives specific instructions on installing the
              Module Management System for OpenVMS (MMS) software. It
              continues the installation process from where it left off
              in Section 2.6 and describes how to run MMS on multiple
              nodes of an OpenVMS Cluster.

              For specific installation requirements related to MMS,
              such as account quotas and disk space, see the Module
              Management System for OpenVMS Release Notes. The MMS
              release notes, up to and including this version, can be
              found in SYS$HELP:MMSnnn.RELEASE_NOTES (where nnn is the
              version and update number, such as 037 for Version 3.7).

        6.1 Installation Procedure Requirements

              The DECset Environment Manager for OpenVMS (ENVMGR)
              is installed as part of the installation of the MMS
              component. ENVMGR consists of the following:

              o  Run-time component used by DECset layered products

              o  DCL interface

              o  DECwindows interface

              The DCL and DECwindows interface components are optional.

              MMS includes support for forms in HP Forms Management
              System for OpenVMS (FMS) libraries. If FMS is not
              installed on your system, the procedure prints a message
              similar to the following:

              %MMS-I-NOFMSSUPP, MMS will not contain support for FMS.


                 Installing the Module Management System for OpenVMS 6-1

 



     Installing the Module Management System for OpenVMS
     6.1 Installation Procedure Requirements

           To use MMS to access forms stored in FMS libraries, you
           must have already installed FMS on your system. If you
           install or reinstall FMS after you have installed MMS, FMS
           support will not be available. You must reinstall MMS for
           FMS support.

           The MMS installation takes approximately 1 to 3 minutes,
           depending on the type of media, your system configuration,
           and whether you are performing a product upgrade or a new
           installation. Before installing MMS, you must have SETPRV
           privileges, or CMKRNL, WORLD, and SYSPRV privileges.

     6.2 User Account Quotas and Privileges

           To use MMS, each account must have a minimum of TMPMBX
           privilege, and the minimum user quota requirements listed
           in the Module Management System for OpenVMS Release Notes.

           Use the OpenVMS Authorize Utility (AUTHORIZE) to compare
           the current values of these quotas with the requirements
           for each component. The account used in the following
           example is the SYSTEM account:

           $ SET DEFAULT SYS$SYSTEM <Return>
           $ RUN AUTHORIZE <Return>
           UAF> SHOW SYSTEM <Return>

           To change the values of these quotas, use the OpenVMS
           Authorize Utility MODIFY command. For example:

           UAF> MODIFY SYSTEM /ASTLM=100 <Return>

           For more information, see the OpenVMS System Management
           Utilities Reference Manual.

     6.3 Installing MMS

           This section contains excerpts from the installation
           procedure and explains each step. Default values appear in
           brackets throughout the installation procedure.

           The following steps are performed as part of any DECset
           installation, and are accomplished before the subsequent
           component-specific steps described in this chapter:

           1. Log in to a privileged account and set your default
              device and directory to SYS$UPDATE.

     6-2 Installing the Module Management System for OpenVMS

 



                     Installing the Module Management System for OpenVMS
                                                      6.3 Installing MMS

              2. Invoke VMSINSTAL with a kit on CD-ROM.

              3. Confirm system backup.

              4. Select a release notes option.

              5. Select components to install.

              6. Install the ENVMGR component.

              See Section 2.6 for full descriptions of these universal,
              preliminary installation steps.

              To stop the installation procedure at any time, press
              Ctrl/Y. When you press Ctrl/Y, the installation procedure
              deletes all files it has created up to that point and
              returns you to DCL level. If you want to retry the
              installation procedure after pressing Ctrl/Y, you must
              proceed from Step 2.

              7. Respond to license registration queries.

                 The installation procedure displays license information
                 about your product and then asks if you have registered
                 and loaded your product authorization key (PAK) for
                 MMS. The following is an example of such information:

                 %DECSET-I-START_MMS, The following questions relate to MMS
                 installation.

                 Product:       VAXSET
                 Producer:      DEC
                 Version:       12.7

                 Product:       MMS
                 Producer:      DEC
                 Version:       3.7

                 * Is one of these authorization keys registered and loaded [YES]? <Return>

                 If you are installing MMS on an OpenVMS Alpha or
                 OpenVMS VAX system, and you have not registered and
                 loaded your PAK, answer NO to this question. You must
                 then stop the installation, register and load your PAK,
                 and then restart the installation.

                 Installing the Module Management System for OpenVMS 6-3

 



     Installing the Module Management System for OpenVMS
     6.3 Installing MMS

              If you incorrectly answer YES, DECset enables you
              to complete the installation without running the
              Installation Verification Procedure (IVP). However,
              when you try to invoke MMS, you will receive a message
              indicating that you are not licensed to run the
              product.

           8. Select installation options.

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

              The IVP runs tests to verify that the installation
              was successful. Press Return to run the IVP after the
              installation. If you do not want to run the IVP, enter
              NO in response to the prompt.

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

              %DECSET-I-DONEASK, You have answered all the questions for MMS
              installation

              The directories SYS$EXAMPLES, SYS$HELP, and SYS$SYSTEM
              may contain previous versions of MMS files. These files
              are replaced during the installation with new files,
              but the old files are not automatically purged. Purging
              is recommended. In response to the purging prompt,
              press Return to purge the files or enter NO to keep
              them.

           9. Read the informational messages.

              The MMS installation procedure produces a number of
              informational messages that report on the progress of
              the installation.

              %DECSET-I-START_MMS, MMS V3.7 installation in progress

              %VMSINSTAL-I-RESTORE, Restoring product save set B ...
              %MMS-I-NOFMSSUPP, MMS will not contain support for FMS.
              %MMS-I-LINKIMAGE, Linking V3.7.

              ________________________Note ________________________

              You see the NOFMSSUPP message only if the FMS
              software is not installed on your system.

              _____________________________________________________

     6-4 Installing the Module Management System for OpenVMS

 



                     Installing the Module Management System for OpenVMS
                                                      6.3 Installing MMS

                 The success of the installation is indicated by the
                 following message:

                 %DECSET-I-DONEMMS, The installation of MMS V3.7 completed

                 If the installation procedure is successful, the new or
                 modified files are moved to their target directo-
                 ries. In addition, the SYS$HELP:HELPLIB.HLB and
                 SYS$LIBRARY:DCLTABLES.EXE files are updated to include
                 the new versions of MMS help text and the MMS command-
                 line definition.

                 If you entered YES in response to the prompt that
                 requests a file purge, previous versions of the MMS
                 files are now purged.

             10. Observe the Installation Verification Procedure.

                 If you chose to run the IVP, VMSINSTAL now calls the
                 IVP to verify that MMS was installed successfully, and
                 displays the following:

                 %MMS-I-BEGINIVP, Beginning MMS V3.7 IVP
                 %MMS-I-ENDIVP, MMS V3.7 IVP completed successfully.

             11. End the installation procedure.

                    Installation of MMS V3.7 completed at 15:49

                    VMSINSTAL procedure done at 15:49

                 When the product installation procedure is complete,
                 you can choose to install more products or log out.
                 If you removed any media from the console drive before
                 beginning the installation, you must replace it now.

                 The VMSINSTAL procedure deletes or changes entries in
                 the process symbol tables during the installation.
                 Therefore, if you are going to continue using the
                 system manager's account and you want to restore these
                 symbols, you must log out and log in again.




                 Installing the Module Management System for OpenVMS 6-5

 



     Installing the Module Management System for OpenVMS
     6.4 Installing MMS on an OpenVMS Cluster

     6.4 Installing MMS on an OpenVMS Cluster

           To run MMS on multiple nodes of an OpenVMS Cluster,
           first check to see that you have the appropriate software
           license. Then, follow these steps after installing MMS:

           1. On OpenVMS Alpha and OpenVMS VAX systems, enter the
              LICENSE LOAD command to activate the license on
              each node in the OpenVMS Cluster on which MMS will
              run, as described in the OpenVMS License Management
              Utility Manual. On OpenVMS I64 systems, ensure that the
              appropriate Operating Environment (OE) is installed.

           2. Run SYS$STARTUP:MMS$STARTUP.COM on each node in the
              cluster that has a software license. In addition, you
              must add the following line to your system startup
              procedure, SYS$MANAGER:SYSTARTUP_VMS.COM:

              $ @SYS$STARTUP:MMS$STARTUP.COM

           3. To use the product on other nodes in the OpenVMS
              Cluster, you must replace the version of the DCL tables
              installed on the other OpenVMS Cluster nodes. To do
              this, perform the following steps:

              a. Log in to a node on the cluster.

              b. Run INSTALL and enter the following command at the
                 INSTALL> prompt:

                 INSTALL> REPLACE SYS$LIBRARY:DCLTABLES.EXE <Return>

              c. Repeat Steps a and b for each node of the cluster.












     6-6 Installing the Module Management System for OpenVMS

 









                                                                       7
        ________________________________________________________________

            Installing the Performance and Coverage Analyzer for OpenVMS



              This chapter gives specific instructions on installing
              the Performance and Coverage Analyzer for OpenVMS (PCA)
              software. It continues the installation process from where
              it left off in Section 2.6 and describes how to run PCA on
              multiple nodes of an OpenVMS Cluster.

              For specific installation requirements related to PCA,
              such as account quotas and disk space, see the Performance
              and Coverage Analyzer for OpenVMS Release Notes. The PCA
              release notes, up to and including this version, can be
              found in SYS$HELP:PCAnnn.RELEASE_NOTES (where nnn is the
              version and update number, such as 049 for Version 4.9).

              PCA is compatible with a wide range of application
              development software and languages. All features of PCA
              are available to each of the supported languages. DTM,
              LSE, and SCA can also be used in conjunction with PCA. See
              the Software Product Description (SPD) for information on
              specific software and languages supported by PCA.

        7.1 Installation Procedure Requirements

              The DECset Environment Manager for OpenVMS (ENVMGR)
              is installed as part of the installation of the PCA
              component. ENVMGR consists of the following:

              o  Run-time component used by DECset layered products

              o  DCL interface

              o  DECwindows interface

              The DCL and DECwindows interface components are optional.


        Installing the Performance and Coverage Analyzer for OpenVMS 7-1

 



     Installing the Performance and Coverage Analyzer for OpenVMS
     7.1 Installation Procedure Requirements

           The PCA installation takes approximately 2 to 7 minutes,
           depending on the type of media, your system configuration,
           and whether you are performing a product upgrade or a new
           installation. Before installing PCA, you must have SETPRV
           privileges, or CMKRNL, WORLD, and SYSPRV privileges.

     7.2 User Account Quotas and Privileges

           To use PCA, each account must have a minimum of TMPMBX and
           NETMBX privileges, and the minimum user quota requirements
           listed in the Performance and Coverage Analyzer for
           OpenVMS Release Notes.

           Use the OpenVMS Authorize Utility (AUTHORIZE) to compare
           the current values of these quotas with the requirements
           for each component. The account used in the following
           example is the SYSTEM account:

           $ SET DEFAULT SYS$SYSTEM <Return>
           $ RUN AUTHORIZE <Return>
           UAF> SHOW SYSTEM <Return>

           To change the values of these quotas, use the OpenVMS
           Authorize Utility MODIFY command. For example:

           UAF> MODIFY SYSTEM /ASTLM=100 <Return>

           For more information, see the OpenVMS System Management
           Utilities Reference Manual.

     7.3 Installing PCA

           This section contains excerpts from the installation
           procedure and explains each step. Default values appear in
           brackets throughout the installation procedure.

           The following steps are performed as part of any DECset
           installation, and are accomplished before the subsequent
           component-specific steps described in this chapter:

           1. Log in to a privileged account and set your default
              device and directory to SYS$UPDATE.

           2. Invoke VMSINSTAL with a kit on CD-ROM.

           3. Confirm system backup.

           4. Select a release notes option.

     7-2 Installing the Performance and Coverage Analyzer for OpenVMS

 



            Installing the Performance and Coverage Analyzer for OpenVMS
                                                      7.3 Installing PCA

              5. Select components to install.

              6. Install the ENVMGR component.

              See Section 2.6 for full descriptions of these universal,
              preliminary installation steps.

              To stop the installation procedure at any time, press
              Ctrl/Y. When you press Ctrl/Y, the installation procedure
              deletes all files it has created up to that point and
              returns you to DCL level. If you want to retry the
              installation procedure after pressing Ctrl/Y, you must
              proceed from Step 2.

              7. Respond to license registration queries.

                 The installation procedure displays license information
                 about your product and asks if you have registered and
                 loaded your product authorization key (PAK) for PCA.
                 The following is an example of such information:

                 %DECSET-I-START_PCA, The following questions relate to PCA
                 installation.

                 Product:       VAXSET
                 Producer:      DEC
                 Version:       12.7

                 Product:       PCA
                 Producer:      DEC
                 Version:       4.9

                 * Is one of these authorization keys registered and loaded [YES]? <Return>

                 If you are installing PCA on an OpenVMS Alpha or
                 OpenVMS VAX system, and you have not registered and
                 loaded your PAK, you must answer NO to this question.
                 You must then stop the installation, register and load
                 your PAK, and restart the installation.

                 If you incorrectly answer YES, DECset enables you
                 to complete the installation without running the
                 Installation Verification Procedure (IVP). However,
                 when you try to invoke PCA, you will receive a message
                 indicating that you are not licensed to run the
                 product.

        Installing the Performance and Coverage Analyzer for OpenVMS 7-3

 



     Installing the Performance and Coverage Analyzer for OpenVMS
     7.3 Installing PCA

           8. Select installation options.

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

              The IVP runs tests to verify that the installation
              was successful. Press Return to run the IVP after the
              installation. If you do not want to run the IVP, enter
              NO in response to the prompt.

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

              The directories SYS$EXAMPLES, SYS$HELP, SYS$LIBRARY,
              SYS$MANAGER, and SYS$SYSTEM might contain previous
              versions of PCA files. These files are replaced during
              the installation with new files, but the old files are
              not automatically purged. Purging is recommended. In
              response to the purging prompt, press Return to purge
              the files or enter NO to keep them.

              * Do you wish to install the PCA DECwindows analyzer [YES]? <Return>
              * Do you wish to install the PCA DECwindows collector [YES]? <Return>

              The PCA product consists of two major components, which
              can be installed individually:

              o  The Collector-Gathers various performance and test
                 data on your running application

              o  The Analyzer-Processes and displays that data
                 graphically, as a standalone utility

           9. Install the PCA demo package.

              * Do you want to install the PCA demo package [YES]? <Return>

              %DECSET-I-DONEASK, You have answered all the questions for PCA
              installation

              The VMSINSTAL procedure asks if you want to install
              the optional PCA demo package. If you enter YES
              (the default), the SYS$COMMON:[SYSHLP.EXAMPLES.PCA]
              directory is created, and all the demo files are
              copied into it. The system logical name PCA$EXAMPLES
              that points to this directory is also defined.
              After the installation, you can run the demos with
              @PCA$EXAMPLES:PCA_DEMO.

          10. Read the informational messages.

     7-4 Installing the Performance and Coverage Analyzer for OpenVMS

 



            Installing the Performance and Coverage Analyzer for OpenVMS
                                                      7.3 Installing PCA

                 The PCA 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:

                 %DECSET-I-DONEPCA, The installation of PCA completed

                 If the installation procedure is successful, new or
                 modified files are moved to their target directories.

                 The SYS$HELP:HELPLIB.HLB and SYS$LIBRARY:DCLTABLES.EXE
                 files are updated to include the new versions of the
                 PCA Help text and the PCA command-line definition.

                 The PCA installation optionally adds or replaces the
                 SYS$COMMON:[SYSHLP.EXAMPLES.PCA] directory and its
                 contents.

                 If you typed YES in response to the prompt that
                 requests a file purge, previous versions of the PCA
                 files are now purged.

             11. Observe the Installation Verification Procedure.

                 If you chose to run the IVP, VMSINSTAL now calls the
                 IVP to verify that PCA was successfully installed.

                 If PCA has been successfully installed, the IVP
                 displays the following message:

                 %PCA-I-BEGINIVP, Beginning PCA V4.9 IVP

                     Saving previously defined PCA logical names...
                     Linking IVP image file...
                     Running Collector test...
                     Running Analyzer test...
                     Checking test results...

                 %PCA-I-IVPPASS, PCA V4.9 IVP completed successfully.

                     Deleting temporary files...
                     Restoring logical names...

             12. End the installation procedure.

                    Installation of PCA V4.9 completed at 15:49

                    VMSINSTAL procedure done at 15:49

        Installing the Performance and Coverage Analyzer for OpenVMS 7-5

 



     Installing the Performance and Coverage Analyzer for OpenVMS
     7.3 Installing PCA

              When the product installation procedure is complete,
              you can choose to install more products or log out.
              If you removed any media from the console drive before
              beginning the installation, you must replace it now.

              The VMSINSTAL procedure deletes or changes entries in
              the process symbol tables during the installation.
              Therefore, if you are going to continue using the
              system manager's account and you want to restore these
              symbols, you must log out and log in again.

     7.4 Installing PCA on an OpenVMS Cluster

           If you want to run PCA on multiple nodes of an OpenVMS
           Cluster, first check to see that you have the appropriate
           software license. Then, follow these steps after
           installing PCA:

           1. On OpenVMS Alpha and OpenVMS VAX systems, enter the
              LICENSE LOAD command to activate the license on
              each node in the OpenVMS Cluster on which PCA is
              to be executed, as described in the OpenVMS License
              Management Utility Manual. On OpenVMS I64 systems,
              ensure that the appropriate Operating Environment (OE)
              is installed.

           2. Execute PCA$STARTUP.COM on each node of the cluster
              that has a software license. In addition, you must add
              the following line to your system startup procedure,
              SYS$MANAGER:SYSTARTUP_VMS.COM:

              $ @SYS$STARTUP:PCA$STARTUP.COM

           3. To use the product on other nodes in the OpenVMS
              Cluster, you must replace the version of the DCL tables
              installed on the other OpenVMS Cluster nodes. To do
              this, perform the following steps:

              a. Log in to a node on the cluster.

              b. Run INSTALL and enter the following command at the
                 INSTALL> prompt:

                 INSTALL> REPLACE SYS$LIBRARY:DCLTABLES.EXE <Return>

     7-6 Installing the Performance and Coverage Analyzer for OpenVMS

 



            Installing the Performance and Coverage Analyzer for OpenVMS
                                7.4 Installing PCA on an OpenVMS Cluster

                 c. Repeat Steps a and b for each node of the cluster.

                ________________________Note  ________________________

                The installation procedure modifies the DCL
                command table so the PCA command is recognized and
                processed. However, the previous command table is
                still in effect for those users who are currently
                logged in. All logged-in users who want to use the
                PCA command must log out of the system and log in
                again.

                _____________________________________________________
































        Installing the Performance and Coverage Analyzer for OpenVMS 7-7

 









                                                                       8
        ________________________________________________________________

                         Installing the Source Code Analyzer for OpenVMS



              This chapter gives specific instructions on installing
              the Source Code Analyzer for OpenVMS (SCA) software. It
              continues the installation process from where it left off
              in Section 2.6 and describes how to run SCA on multiple
              nodes of an OpenVMS Cluster.

              For specific installation requirements related to SCA,
              such as account quotas and disk space, see the Source
              Code Analyzer for OpenVMS Release Notes. The SCA release
              notes, up to and including this version, can be found in
              SYS$HELP:SCAnnn.RELEASE_NOTES (where nnn is the version
              and update number, such as 049 for Version 4.9).

        8.1 Installation Procedure Requirements

              The DECset Environment Manager for OpenVMS (ENVMGR)
              is installed as part of the installation of the SCA
              component. ENVMGR consists of the following:

              o  Run-time component used by DECset layered products

              o  DCL interface

              o  DECwindows interface

              The DCL and DECwindows interface components are optional.

              The installation of SCA takes approximately 12 to 36
              minutes, depending on the type of media, your system
              configuration, and whether you are performing a product
              upgrade or a new installation. Before installing SCA, you
              must have SETPRV privileges, or CMKRNL, WORLD, and SYSPRV
              privileges.


                     Installing the Source Code Analyzer for OpenVMS 8-1

 



     Installing the Source Code Analyzer for OpenVMS
     8.2 User Account Quotas and Privileges

     8.2 User Account Quotas and Privileges

           To use SCA, each account must have TMPMBX and NETMBX
           privileges, and the minimum user quota requirements listed
           in the Source Code Analyzer for OpenVMS Release Notes.

           Use the OpenVMS Authorize Utility (AUTHORIZE) to compare
           the current values of these quotas with the requirements
           for SCA. For example, the account used in the following
           example is the SYSTEM account:

           $ SET DEFAULT SYS$SYSTEM <Return>
           $ RUN AUTHORIZE <Return>
           UAF> SHOW SYSTEM <Return>

           To change the values of these quotas, use the OpenVMS
           Authorize Utility MODIFY command. For example:

           UAF> MODIFY SYSTEM /ASTLM=100 <Return>

           For more information, see the OpenVMS System Management
           Utilities Reference Manual.

     8.3 Installing SCA

           This section contains excerpts from the installation
           procedure and explains each step. Default values appear
           in brackets throughout the installation procedure. The
           following steps are performed as part of any DECset
           installation, and are accomplished before the subsequent
           component-specific steps described in this chapter:

           1. Log in to a privileged account and set your default
              device and directory to SYS$UPDATE.

           2. Invoke VMSINSTAL with a kit on CD-ROM.

           3. Confirm system backup.

           4. Select a release notes option.

           5. Select components to install.

           6. Install the ENVMGR component.

           See Section 2.6 for full descriptions of these universal,
           preliminary installation steps.

     8-2 Installing the Source Code Analyzer for OpenVMS

 



                         Installing the Source Code Analyzer for OpenVMS
                                                      8.3 Installing SCA

              To stop the installation procedure at any time, press
              Ctrl/Y. When you press Ctrl/Y, the installation procedure
              deletes all files it has created up to that point and
              returns you to DCL level. If you want to retry the
              installation procedure after pressing Ctrl/Y, you must
              proceed from Step 2.

              7. Respond to license registration queries.

                 The installation procedure displays license information
                 about your product and then asks if you have registered
                 and loaded your product authorization key (PAK) for
                 SCA. The following is an example of such information:

                 %DECSET-I-START_SCA, The following questions relate to SCA
                 installation.

                         Product:       VAXSET
                         Producer:      DEC
                         Version:       12.7

                         Product:       LSE
                         Producer:      DEC
                         Version:       5.0

                         Note: LSE and SCA share the LSE license.

                 * Is one of these authorization keys registered and loaded [YES]?

                 If you are installing SCA on an OpenVMS Alpha or
                 OpenVMS VAX system, and you have not registered and
                 loaded your PAK, answer NO to this question. You must
                 then stop the installation, register and load your PAK,
                 then restart the installation.

                 If you incorrectly answer YES, DECset enables you
                 to complete the installation without running the
                 Installation Verification Procedure (IVP). However,
                 when you try to invoke SCA, you will receive a message
                 indicating that you are not licensed to run the
                 product.

              8. Choose the Installation Verification Procedure (IVP)
                 options.

                     Installing the Source Code Analyzer for OpenVMS 8-3

 



     Installing the Source Code Analyzer for OpenVMS
     8.3 Installing SCA

              The IVP runs tests to verify that the installation
              was successful. There are two parts to the SCA IVP:
              one that tests the character-cell version of SCA, and
              one that tests the DECwindows version. If you want to
              run the character cell or both parts of the IVP, press
              Return in response to the following IVP prompt:

                     As well as verifying that the installation succeeded, the IVP also
                     creates the SCA example library. It is therefore recommended that
                     you run the IVP.

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

              Entering YES to this prompt causes the following
              information to be displayed:

                    The IVP has two sections, a character cell section and a DECwindows
                    section. In order for the DECwindows section to run correctly, the
                    logical name DECW$DISPLAY must be appropriately set (using the SET
                    DISPLAY command). If at this time you are not prepared to run the
                    DECwindows portion of the IVP, enter NO at the following prompt.

                    You can rerun the IVP later by issuing the command:

                    @SYS$TEST:SCA$IVP

                * Do you wish to run the whole IVP [YES]?

              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. If you are running the installation at a remote
              node, set your DECwindows display using the following
              command:

              $ SET DISPLAY/CREATE/NODE=nodename <Return>

              The nodename is the name of your local node where the
              display should appear. See the online Help for more
              information on setting your DECwindows display device.

              HP recommends that you run the IVP not only to verify
              that the installation succeeded, but also to set up
              a sample SCA library and to have the logical name
              SCA$EXAMPLE refer to that library. The installation
              places the necessary files in the sample directory
              and the IVP creates the sample SCA library in that
              directory. The IVP also sets up an example library for

     8-4 Installing the Source Code Analyzer for OpenVMS

 



                         Installing the Source Code Analyzer for OpenVMS
                                                      8.3 Installing SCA

                 the program design facility (PDF), referred to by the
                 logical name SCA$2167A. If you choose not to run the
                 IVP, enter NO at the previous prompt. You can run the
                 IVP after the installation by entering the following
                 command:

                 $ @SYS$TEST:SCA$IVP<Return>

                 For more information on running the IVP manually after
                 the installation is complete, see Section 9.3.

              9. Select installation options. (Alpha and VAX Only)

                 If you are installing SCA on an OpenVMS Alpha or
                 OpenVMS VAX system, you are prompted to choose which
                 components to install. You can choose to install the
                 client component only or both the client and server
                 components. On OpenVMS I64 systems, only the client
                 component is available. As a result, the installation
                 options are not displayed.

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

                        Please indicate the components of SCA that you wish to install:

                           1 - Both SCA client and server
                           2 - SCA client only

                 * Enter the number corresponding to the SCA components to install [1]:

                 If you install the SCA server, two accounts are
                 created: SCA$SERVER and SCA$DEFAULT.

                 The server code itself runs under the SCA$SERVER
                 account. This account has no special privileges,
                 but is granted access to all SCA library directories
                 by an access control list (ACL) that is added when
                 libraries are created. This 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 libraries where the server
                 is running. The image executed by the SCA server,
                 SCA$SERVER_MAIN, is installed with SYSPRV and SYSNAM
                 privileges.

                     Installing the Source Code Analyzer for OpenVMS 8-5

 



     Installing the Source Code Analyzer for OpenVMS
     8.3 Installing SCA

              This installation defines the SCA$SERVER object in the
              network database. A password for the SCA$SERVER account
              can either be generated randomly or defined manually.
              In either case, the password is added to the Network
              Control Program (NCP) database. If you decide to change
              the SCA$SERVER account password in the future, you must
              remember to update the SCA$SERVER object password also
              by using NCP.

              Another account, SCA$DEFAULT, is created by the
              installation to grant access to remote users who do
              not have proxy access to the local node. This account
              has no special privileges.

              Both these accounts must have unique User Identification
              Codes (UICs). You are prompted to enter information for
              these accounts as in the following example:

                 In order to grant access to remote users who do not have a proxy
                 account for the local node, SCA creates the SCA$DEFAULT account,
                 which is used as a default proxy account for SCA library access.

                 This account has no special privileges.

                 The password for the account should normally be automatically
                 generated by SCA.  A user-supplied password may also be given
                 (minimum size 10).  If a user-supplied password is provided, it
                 will not be logged in the Auto Answer file and cannot be used for
                 automated installs.

                 If the account does not already exist you will be asked to specify a
                 unique UIC for the account.

                      You must specify a unique UIC for this account in order
                      to ensure proper security of your libraries.

              * Do you want to specify a password [NO]? yes

                 Please enter a password of at least 10 characters.

              * Password:
              * Verification:

              * Enter UIC for SCA$DEFAULT account (include brackets) [[371,345]]:

     8-6 Installing the Source Code Analyzer for OpenVMS

 



                         Installing the Source Code Analyzer for OpenVMS
                                                      8.3 Installing SCA

                 %SCA-I-CREACC, Creating account SCA$DEFAULT
                 %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named
                 SCA$DEFAULT.
                 %UAF-I-ADDMSG, user record successfully added
                 %UAF-I-RDBADDMSGU, identifier SCA$DEFAULT value: [000371,000345] added
                 to rights database
                 %SCA-I-MODACC, Modifying account SCA$DEFAULT quotas...
                 %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named
                 SCA$DEFAULT.
                 %UAF-I-MDFYMSG, user record(s) updated
                 %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named
                 SCA$DEFAULT.
                 %UAF-I-MDFYMSG, user record(s) updated

                    In order to ensure that the SCA server runs with the proper quotas,
                    this installation procedure will create an account for the server.  This
                    account, SCA$SERVER, has no special privileges and is set up only for
                    network operation.

                    The password for the account should normally be automatically generated by SCA
                    A user-supplied password may also be given (minimum size 10), a reason for
                    a user-supplied password is when multiple network databases need updating in
                    a cluster.  If a user-supplied password is provided it will not be logged in
                    the Auto Answer file and cannot be used for automated installs.

                    If the account does not already exist you will be asked to specify a
                    unique UIC for the account.

                        You must specify a unique UIC for this account in order to ensure
                        proper security of your libraries.  The SCA server account is
                        automatically granted access to each library created, via Access
                        Control Lists.

                    If you want to change the password of this account after the installation
                    has completed, you must also change the password in the NCP database
                    with the SET OBJECT SCA$SERVER PASSWORD command.

                 * Do you want to specify a password [NO]? yes

                    Please enter a password of at least 10 characters.

                 * Password:
                 * Verification:

                 * Enter UIC for SCA$SERVER account (include brackets) [[370,355]]:

                     Installing the Source Code Analyzer for OpenVMS 8-7

 



     Installing the Source Code Analyzer for OpenVMS
     8.3 Installing SCA

              %SCA-I-CREACC, Creating account SCA$SERVER for the SCA server
              %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named
              SCA$SERVER.
              %UAF-I-ADDMSG, user record successfully added
              %UAF-I-RDBADDMSGU, identifier SCA$SERVER value: [000370,000355] added to
              rights data base
              %VMSINSTAL-I-SYSDIR, This product creates system disk directory
              SYS$SYSDEVICE:[SCA$SERVER].
              %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named
              SCA$SERVER.
              %UAF-I-MDFYMSG, user record(s) updated
              %SCA-I-MODACC, Modifying account SCA$SERVER quotas...
              %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named
              SCA$SERVER.
              %UAF-I-MDFYMSG, user record(s) updated
              %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named
              SCA$SERVER.
              %UAF-I-MDFYMSG, user record(s) updated

                The network object SCA$SERVER has been defined. If you wish
                to view this, run SYS$SYSTEM:NCP and enter the command
                      NCP> LIST OBJECT SCA$SERVER CHAR

              See Section 8.5 for information on the SCA server
              installation and the quotas assigned to the SCA$SERVER
              and SCA$DEFAULT accounts.

          10. Read the informational messages.

              The SCA installation procedure produces a number of
              informational messages that report on the progress of
              the installation:

              %DECSET-I-DONESCA, The installation of SCA completed

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

              If the installation procedure is successful, new or
              modified files are moved to their target directories.

              The SYS$HELP:HELPLIB.HLB and SYS$LIBRARY:DCLTABLES.EXE
              files are updated to include the new versions of the
              SCA HELP text and the SCA command-line definition. For
              a list of the added or modified files, see Appendix B.

          11. Observe the Installation Verification Procedure.

     8-8 Installing the Source Code Analyzer for OpenVMS

 



                         Installing the Source Code Analyzer for OpenVMS
                                                      8.3 Installing SCA

                 If you chose to run the IVP, VMSINSTAL now calls the
                 IVP to verify that SCA was installed successfully.
                 If you answered YES to running the entire IVP, the
                 DECwindows portion requires user action. The SCA main
                 window appears on the screen. Use the mouse to choose
                 the Exit menu option from the File pull-down menu. The
                 IVP then continues. See Section C.1 to see what to do
                 in the event of a failure.

                 Event files are created by the IVP for the SCA and PDF
                 sample libraries.

                 %SCA-I-BEGINIVP, Beginning SCA V4.9 IVP.

                 ****  Client testing complete  ****

                 %SCA-I-CONNECTING, Requesting connection to 0::
                 %SCA-S-LIB, your SCA Library is 0::SCA$EXAMPLE:
                 %SCA-I-CONNECTING, Requesting connection to 0::
                 ****  Server testing complete  ****

                 The character cell portion of the IVP has completed successfully.
                 The DECwindows section will now execute.

                 The SCA main window should appear on your display.  It
                 will be set to the SCA Example library.  Verify that
                 this is the case, and then choose EXIT from the FILE menu.

                 If the DECset Environment Manager did not already appear on
                 your display, please verify that it appears as an icon as a
                 result of executing this IVP; then, restore the icon and
                 choose EXIT from the FILE menu.  (If the DECset Environment Manager
                 was on your display prior to the execution of this IVP and a
                 context had previously been applied via the DECset Environment
                 Manager's main window, that context will be applied to SCA as
                 part of SCA initialization.)

                 %SCA-I-ENDIVP, SCA V4.9 IVP completed successfully.

                 In addition, if you typed YES in response to the prompt
                 that requests a file purge, previous versions of SCA
                 files are now purged.



                     Installing the Source Code Analyzer for OpenVMS 8-9

 



     Installing the Source Code Analyzer for OpenVMS
     8.3 Installing SCA

          12. End the installation procedure.

                 Installation of SCA V4.9 completed at 15:49

               Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY

               Creating installation data file:  VMI$ROOT:[SYSUPD]SCA049.VMI_DATA

                 VMSINSTAL procedure done at 15:49

              When the product installation procedure is complete,
              you can choose to install more products or log out.
              If you removed any media from the console drive before
              beginning the installation, you should replace it now.

              The VMSINSTAL procedure deletes or changes entries in
              the process symbol tables during the installation.
              Therefore, if you are going to continue using the
              system manager's account and you want to restore these
              symbols, you must log out and log in again.

     8.4 Installing SCA on an OpenVMS Cluster

           If you want to run SCA on multiple nodes of an OpenVMS
           Cluster, first check to see that you have the appropriate
           software license. Then, follow these steps after
           installing SCA:

           1. On OpenVMS Alpha and OpenVMS VAX systems, enter the
              LICENSE LOAD command to activate the license on
              each node in the OpenVMS Cluster on which SCA is
              to be executed, as described in the OpenVMS License
              Management Utility Manual. On OpenVMS I64 systems,
              ensure that the appropriate Operating Environment (OE)
              is installed.

           2. Run SYS$STARTUP:SCA$STARTUP.COM on each node of the
              cluster that has a software license.

              To ensure that SCA is installed each time the system
              is bootstrapped, include the following line in
              SYS$STARTUP:SYSTARTUP_VMS.COM
              (the site-specific startup file):

              @SYS$STARTUP:SCA$STARTUP.COM

     8-10 Installing the Source Code Analyzer for OpenVMS

 



                         Installing the Source Code Analyzer for OpenVMS
                                8.4 Installing SCA on an OpenVMS Cluster

              3. To use the product on other nodes in the OpenVMS
                 Cluster, you must replace the version of the DCL tables
                 installed on the other OpenVMS Cluster nodes. To do
                 this, perform the following steps:

                 a. Log in to a node on the cluster.

                 b. Run INSTALL and enter the following command at the
                    INSTALL> prompt:

                    INSTALL> REPLACE SYS$LIBRARY:DCLTABLES.EXE <Return>

                 c. Repeat Steps a and b for each node of the cluster.

        8.5 SCA Server Installation (Alpha and VAX Only)

              SCA provides a server that enables remote users to access
              your local SCA libraries. The installation of this server
              is optional.

              You will be prompted during the installation as to whether
              you would like to install both the SCA server and the SCA
              client, or whether you would like to install only the SCA
              client.

              If you elect to install only the SCA client, remote users
              will not be able to access your local SCA libraries. SCA
              users on your local system will not be affected. They will
              have the ability to use local libraries and libraries on
              remote nodes where the SCA server has been installed.

              If you elect to install the optional SCA server, accounts
              named SCA$SERVER and SCA$DEFAULT are created for the SCA
              server. The accounts are given the following quotas:

              Username: SCA$SERVER                       Owner:  DEC_SCA_SERVER
              Account:  DECNET                           UIC:    [370,355] ([SCA$SERVER])
              CLI:      DCL                              Tables: DCLTABLES
              Default:  SYS$SYSDEVICE:[SCA$SERVER]
              LGICMD:   SYS$SYSTEM:SCA$SERVER_LOGIN
              Flags:  Restricted DisMail




                    Installing the Source Code Analyzer for OpenVMS 8-11

 



     Installing the Source Code Analyzer for OpenVMS
     8.5 SCA Server Installation (Alpha and VAX Only)

           Primary days:   Mon Tue Wed Thu Fri
           Secondary days:                     Sat Sun
           Primary   000000000011111111112222  Secondary 000000000011111111112222
           Day Hours 012345678901234567890123  Day Hours 012345678901234567890123
           Network:  ##### Full access ######            ##### Full access ######
           Batch:    -----  No access  ------            -----  No access  ------
           Local:    -----  No access  ------            -----  No access  ------
           Dialup:   -----  No access  ------            -----  No access  ------
           Remote:   -----  No access  ------            -----  No access  ------
           Expiration:    (none)    Pwdminimum:  6   Login Fails:     0
           Pwdlifetime:         90 00:00    Pwdchange:   (pre-expired)
           Last Login:    (none) (interactive), 1-JAN-2005 13:22 (non-interactive)
           Maxjobs:         0  Fillm:       300  Bytlm:        32767
           Maxacctjobs:     0  Shrfillm:      0  Pbytlm:           0
           Maxdetach:       0  BIOlm:       120  JTquota:       4096
           Prclm:           8  DIOlm:       120  WSdef:         1024
           Prio:            4  ASTlm:       120  WSquo:        15237
           Queprio:         4  TQElm:        10  WSextent:     30474
           CPU:        (none)  Enqlm:       200  Pgflquo:      20480
           Authorized Privileges:
           Default Privileges:

           Username: SCA$DEFAULT                      Owner:  DEC_SCA
           Account:  DECNET                           UIC:    [371,345] ([SCA$DEFAULT])
           CLI:      DCL                              Tables: DCLTABLES
           Default:  SYS$SYSDEVICE:[SCA$DEFAULT]
           LGICMD:
           Flags:  DisCtlY DefCLI LockPwd DisMail Captive
           Primary days:   Mon Tue Wed Thu Fri
           Secondary days:                     Sat Sun
           Primary   000000000011111111112222  Secondary 000000000011111111112222
           Day Hours 012345678901234567890123  Day Hours 012345678901234567890123
           Network:  -----  No access  ------            -----  No access  ------
           Batch:    -----  No access  ------            -----  No access  ------
           Local:    -----  No access  ------            -----  No access  ------
           Dialup:   -----  No access  ------            -----  No access  ------
           Remote:   -----  No access  ------            -----  No access  ------
           Expiration:            (none)    Pwdminimum:  6   Login Fails:     0
           Pwdlifetime:         90 00:00    Pwdchange:   (pre-expired)
           Last Login:            (none) (interactive),  (none) (non-interactive)
           Maxjobs:         0  Fillm:         0  Bytlm:            0
           Maxacctjobs:     0  Shrfillm:      0  Pbytlm:           0
           Maxdetach:       0  BIOlm:         0  JTquota:       4096


     8-12 Installing the Source Code Analyzer for OpenVMS

 



                         Installing the Source Code Analyzer for OpenVMS
                        8.5 SCA Server Installation (Alpha and VAX Only)

              Prclm:           0  DIOlm:         0  WSdef:         2000
              Prio:            4  ASTlm:         0  WSquo:            1
              Queprio:         4  TQElm:        10  WSextent:         1
              CPU:        (none)  Enqlm:         0  Pgflquo:          0
              Authorized Privileges:
              Default Privileges:

              In addition, an access control list (ACL) is set on the
              file
              SYS$SYSTEM:NETPROXY.DAT, giving the SCA$SERVER account
              read and execute access.

              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 insufficient
              virtual memory. If this occurs frequently, you might want
              to increase PGFLQUO for the SCA$SERVER account.

              If you are reinstalling SCA, stop any previous SCA servers
              (network processes named SCA$SERVER_nnnn) so they will be
              restarted using the new server code. Use the DCL commands
              SHOW SYSTEM/NETWORK and STOP/IDENTIFICATION, respectively.

        8.6 Installing SCA Server on an OpenVMS Cluster (Alpha and VAX
            Only)

              When the SCA server is installed, it creates or modifies
              the SCA$SERVER network object and the SCA$SERVER user
              account. If a password is not manually supplied during
              installation, a random password is generated and set
              on both the object and the account for each node in the
              cluster. If the SCA server is installed in a cluster with
              a common user authorization file but distinct network
              databases, then the password will not be set correctly in
              some of the network databases.

              To resolve this problem, you must manually set the
              password in the authorization file and in all network
              databases during the main SCA installation. Make sure to
              use the same account password for all subsequent nodes
              in the cluster. See the Section 8.3 for an example of
              supplying a user-defined password during installation.



                    Installing the Source Code Analyzer for OpenVMS 8-13

 









                                                                       9
        ________________________________________________________________

                                                  After the Installation



              Your DECset components are now installed and can be
              invoked by all users.

              The installation procedure modifies the DCL command table
              so the component invocation command is recognized and
              processed. However, the previous command table is still
              in effect for those users who are currently logged in.
              All logged-in users who want to use the updated version
              of each component must log out of the system and log in
              again.

        9.1 OpenVMS Cluster Setup

              After you install DECset in an OpenVMS Cluster, you must
              perform the following tasks on each licensed node that
              does not share common system files:

              o  Modify the SYS$MANAGER:SYSTARTUP_VMS.COM file and
                 execute the startup procedures for the installed
                 components.

              o  Install DCLTABLES.EXE.

              o  Register the licenses for DECset. (On OpenVMS Alpha and
                 OpenVMS VAX systems only)

              You must edit SYS$MANAGER:SYSTARTUP_VMS.COM, the site-
              specific startup file, and add the following lines for the
              Environment Manager and each of the installed components:

                 @SYS$STARTUP:ENVMGR$STARTUP.COM
                 @SYS$STARTUP:[component]$STARTUP.COM

              The DECset installation procedure puts the startup command
              file for each component in the SYS$STARTUP directory.

              For more details, see the section on OpenVMS Cluster
              installation in the appropriate component chapter.

                                              After the Installation 9-1

 



     After the Installation
     9.2 OpenVMS Mail Utility

     9.2 OpenVMS Mail Utility

           You can use LSE to read and compose messages from the
           Mail utility. You can define the logical name MAIL$EDIT as
           CALLABLE_LSE to use the editor from MAIL. Note that LSE
           must be installed as a known image. This is accomplished
           through the editor's startup command procedure. In
           addition, CMS and SCA must be installed as known images
           to be used from LSE when LSE is invoked from the Mail
           utility. (See Chapter 8 for instructions on installing
           SCA.)

     9.3 Running the Installation Verification Procedure Separately

           The Installation Verification Procedure (IVP) for each
           DECset component checks the integrity of installed files,
           either as part of the VMSINSTAL procedure or separately,
           as described here. HP strongly recommends that you run
           the IVPs after you install the components. Each component
           installation puts a command procedure in SYS$TEST for you
           to invoke. Table 9-1 lists the DECset component IVPs.

           Table_9-1_DECset_IVPs_____________________________________

           Component_____Procedure_Name______________________________

           ENVMGR        ENVMGR$IVP

           CMS           CMS$IVP

           DTM           DTM$IVP

           LSE           LSE$IVP

           MMS           MMS$IVP

           PCA           PCA$IVP

           SCA___________SCA$IVP_____________________________________

           The following command shows how to invoke the LSE
           component IVP:

           $ @SYS$TEST:LSE$IVP.COM

     9-2 After the Installation

 



                                                  After the Installation
          9.3 Running the Installation Verification Procedure Separately

              The IVP creates a temporary subdirectory in your current,
              default directory, and places a library for each component
              in this subdirectory. The IVP then creates two additional
              levels of subdirectories; therefore, your current default
              directory must not be a subdirectory deeper than six
              levels. In addition, your current default directory must
              not be defined as a directory search list. The temporary
              subdirectory is deleted at the end of the execution of the
              IVP.

              If the IVP fails, the IVP displays a message such as the
              following:

              %CMS-E-IVPFAILURE, CMS V4.4 IVP failed.

              %VMSINSTAL-E-IVPFAIL, The IVP for CMS V4.4 has failed.

              See Section C.1 for information on what to do when a
              failure occurs.

        9.4 Product Updates

              HP might periodically issue updates of DECset. Each update
              consists of an installation kit. You must install this
              kit as described in this document, or in any documentation
              that accompanies the update.

              In addition, the update includes new release notes.
              The release notes describe the changes made to each
              DECset component since the previous release. The release
              notes for each update are provided online. HP strongly
              recommends that you read the release notes before you
              install any DECset components. They are also accessible at
              any time after the product is installed. For information
              on accessing the release notes before installing any
              DECset components, follow the installation procedure
              for each component. To locate the release notes after
              installation, display or print the release notes file as
              described in Section 1.3.






                                              After the Installation 9-3

 



     After the Installation
     9.5 DECset as a Shared Image

     9.5 DECset as a Shared Image

           When you expect a product to be used extensively on your
           system, you would usually reduce the system overhead and
           memory requirements by installing the software as a shared
           image. However, this process is unnecessary for DECset,
           because the VMSINSTAL procedure automatically installs the
           following components as a shared image:

           o  DECset Environment Manager for OpenVMS

           o  Code Management System for OpenVMS

           o  Digital Test Manager for OpenVMS

           o  Language-Sensitive Editor for OpenVMS





























     9-4 After the Installation

 









                                                                       A
        ________________________________________________________________

                                          Sample Installation Procedures



              This appendix contains a sample log file from the
              following installation procedures:

              o  A new installation of all the DECset components on an
                 OpenVMS I64 system.

              o  A sample upgrade of all the DECset components on an
                 OpenVMS Alpha system.

              Note that the log files are for example purposes only; the
              actual log may vary depending on your system architecture.
              Sometimes the installation procedure is modified in
              updates of this product. Because this installation guide
              is not usually revised for updates, be sure to read the
              Read Before Installing or Using HP DECset for OpenVMS
              Version n.nn letter for your system before you install
              this product. This letter notes any significant changes in
              the installation that vary from these samples.

        A.1 Sample Installation on an OpenVMS I64 System

        @SYS$UPDATE:VMSINSTAL DKA300:[DECSET126.KIT]<Return>
         OpenVMS I64 Software Product Installation Procedure Version 8.2

        It is 10-JAN-2005 at 15:31.

        Enter a question mark (?) at any time for help.
        * Are you satisfied with the backup of your system disk [YES]? <Return>
        * Where will the distribution volumes be mounted: dka0:[decset] <Return>

        Enter the products to be processed from the first distribution volume set.
        * Products: decset126 <Return>
        * Enter installation options you wish to use (none): <Return>

        The following products will be processed:
          DECSET V12.7

         Beginning installation of DECSET V12.7 at 15:31

                                      Sample Installation Procedures A-1

 



     Sample Installation Procedures
     A.1 Sample Installation on an OpenVMS I64 System

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

               - DECset Collective Installation Procedure -

         This is the collective installation procedure for all of the
         DECset components:

               DECset Environment Manager for OpenVMS (ENVMGR)
               Code Management System for OpenVMS (CMS)
               Digital Test Manager for OpenVMS (DTM)
               Language-Sensitive Editor for OpenVMS (LSE)
               Module Management System for OpenVMS (MMS)
               Performance and Coverage Analyzer for OpenVMS (PCA)
               Source Code Analyzer for OpenVMS (SCA)

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

       Copyright 2005 Hewlett-Packard Development Company, L.P.

      Confidential computer software.  Valid license from HP required for
      possession, use, or copying.  Consistent with FAR 12.211 and 12.212,
      Commercial Computer Software, Computer Software Documentation, and
      Technical Data for Commercial Items are licensed to the U.S. Government
      under vendor's standard commercial license.

      Intel and Itanium are trademarks or registered trademarks of Intel
      Corporation or its subsidiaries in the United States and other countries.

      Microsoft, Windows, and Windows NT are U.S. registered trademarks
      of Microsoft Corporation.

              These are the options provided by this collective
              installation procedure:

              DECset components:

                      - all the HP DECset for OpenVMS components
                      - Language-Sensitive Editor (LSE)
                      - Source Code Analyzer (SCA)
                      - Code Management System (CMS)
                      - Digital Test Manager (DTM)
                      - Performance and Coverage Analyzer (PCA)
                      - Module Management System (MMS)
                      - DECset Cookbook - PostScript Format
                      - DECset Cookbook - HTML Format
                      - DECset Cookbook - Text Format

     A-2 Sample Installation Procedures

 



                                          Sample Installation Procedures
                        A.1 Sample Installation on an OpenVMS I64 System

           Please choose your option(s):

        * Do you want all the DECset components [YES]? <Return>
        * Are you sure you want to install all the options [YES]? <Return>

        %DECSET-I-AGGREGATE, Checking resources required to install selected products.

        %DECSET-I-START_ENVMGR, The following questions relate to ENVMGR installation.

           The DECset Environment Manager (ENVMGR) consists of:

                . A run-time component used by DECset layered products,
                . A DCL interface, and
                . A DECwindows interface.

           The DCL and DECwindows interface components are optional.

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

        %DECSET-I-START_CMS, The following questions relate to CMS installation.

        * Do you want to install the CMS DECwindows interface [YES]? <Return>

         On OpenVMS I64, CMS can support element names using Extended
         File Specifications.  The option exists to install CMS with or
         without support for Extended File Specifications.

        * Install Extended File Specification support [YES]? no <Return>
        * Do you want to run the IVP after the installation [YES]? <Return>
        * Do you want to purge files replaced by this installation [YES]? <Return>

        %DECSET-I-DONEASK, You have answered all the questions for CMS installation

        %DECSET-I-START_DTM, The following questions relate to DTM installation.

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

        %DECSET-I-DONEASK, You have answered all the questions for DTM installation

        %DECSET-I-START_LSE, The following questions relate to LSE installation.

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

            Please note that the total system disk space consumed by the unsupported
            LSE source files is approximately 16,000 blocks.  HP recommends not
            to answer yes to the following prompt if you are constrained by the free
            space available on your system disk.

        * Would you like to install the unsupported LSE source files [YES]? <Return>

                                      Sample Installation Procedures A-3

 



     Sample Installation Procedures
     A.1 Sample Installation on an OpenVMS I64 System

       The files will be installed in SYS$SYSROOT[SYSHLP.EXAMPLES.LSE]

         The version of LSE that is currently being installed has two command
         languages:  the VMSLSE command language, and the PORTABLE command
         language.  The VMSLSE command language is the original LSE command
         language that has always been present in LSE.  The PORTABLE command
         language is a later command language that was designed as LSE's command
         language on platforms other than OpenVMS.

         If you would like to have the PORTABLE command language as the system-

         wide default command language, you should specify PORTABLE as the
         default command language.

         If you would like to have the VMSLSE command language as the system-

         wide default command language, you should specify VMSLSE as the default
         command language.

         Individual users may override the system default command language.

     * Do you want default command language to be VMSLSE or PORTABLE  [VMSLSE]: VMSLSE <Return>

         Language templates for Ada, Ada95, BASIC, BLISS, C, COBOL, C++, FORTRAN,
         FORTRAN 90, HTML, Java MACRO, Pascal, and PL/I as well as templates for
         the LSE command languages are included in this kit.  Templates for other
         languages that support LSE and are not mentioned are provided in the
         installation kits for those languages.

         Please choose the languages for which you would like to install support:

     * Do you want to install language support for ADA [YES]? <Return>
     * Do you want to install language support for ADA95 [YES]? <Return>
     * Do you want to install language support for BASIC [YES]? <Return>
     * Do you want to install language support for BLISS [YES]? <Return>
     * Do you want to install language support for C [YES]? <Return>
     * Do you want to install language support for COBOL [YES]? <Return>
     * Do you want to install language support for CXX [YES]? <Return>
     * Do you want to install language support for FORTRAN [YES]? <Return>
     * Do you want to install language support for F90 [YES]? <Return>
     * Do you want to install language support for HTML [YES]? <Return>
     * Do you want to install language support for JAVA [YES]? <Return>
     * Do you want to install language support for MACRO [YES]? <Return>
     * Do you want to install language support for PASCAL [YES]? <Return>
     * Do you want to install language support for PLI [YES]? <Return>
     * Do you want to install language support for LSE [YES]? <Return>
     * Do you want to install language support for PLSE [YES]? <Return>

     A-4 Sample Installation Procedures

 



                                          Sample Installation Procedures
                        A.1 Sample Installation on an OpenVMS I64 System

        %DECSET-I-DONEASK, You have answered all the questions for LSE installation

        %DECSET-I-START_MMS, The following questions relate to MMS installation.

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

        %DECSET-I-DONEASK, You have answered all the questions for MMS installation

        %DECSET-I-START_PCA, The following questions relate to PCA installation.

        * Do you want to run the IVP after the installation [YES]? <Return>
        * Do you want to purge files replaced by this installation [YES]? <Return>
        * Do you wish to install the PCA DECwindows analyzer [YES]? <Return>
        * Do you wish to install the PCA DECwindows collector [YES]? <Return>
        * Do you want to install the PCA demo package [YES]? <Return>

        %DECSET-I-DONEASK, You have answered all the questions for PCA installation

        %DECSET-I-START_SCA, The following questions relate to SCA installation.

                As well as verifying that the installation succeeded, the IVP also
                creates the SCA example library.  It is therefore recommended that
                you run the IVP.

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

                The IVP has two sections, a character-cell section and a DECwindows
                section.  In order for the DECwindows section to run correctly, the
                logical name DECW$DISPLAY must be appropriately set (using the SET
                DISPLAY command).  If at this time you are not prepared to run the
                DECwindows portion of the IVP, enter NO at the following prompt.

         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>
        * Do you want to purge files replaced by this installation [YES]? <Return>

        %DECSET-I-DONEASK, You have answered all the questions for SCA installation

            ***********************************************************************
              If you are satisfied with your answers, answer YES to the following
              prompt.  If not, answer NO to start the auto-answer session again.
            ***********************************************************************

        * Are you satisfied with your answers to selected DECset components ?  [YES]? <Return>

        %DECSET-I-DONEASK, You have answered all the questions for DECset installation

                                      Sample Installation Procedures A-5

 



     Sample Installation Procedures
     A.1 Sample Installation on an OpenVMS I64 System

       The installation will complete in 11-33 minutes depending
       on the installation media and processor type.

          ********************************************************************
            The installation procedure will now install the selected
            DECset components one by one.

          DECset Environment Manager V1.7
          Code Management System V4.4
          Digital Test Manager V4.3
          Language-Sensitive Editor V5.0
          Module Management System V3.6
          Performance and Coverage Analyzer V4.9
          Source Code Analyzer V4.9
          DECset Cookbook - PostScript Format
          DECset Cookbook - HTML Format
          DECset Cookbook - Text Format
          ********************************************************************

     %DECSET-I-START_ENVMGR, DECset Environment Manager V1.7 installation in progress

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

       The ENVMGR IVP has been moved to the SYS$TEST directory.  To run it after
       the installation enter @SYS$TEST:ENVMGR$IVP.COM.

     The installation of DECset Environment Manager has added or modified:

                 SYS$HELP:ENVMGR017_RELEASE_NOTES.PS
                 SYS$TEST:ENVMGR$IVP.COM
                 SYS$TEST:ENVMGR$SAMPLE.DECSET_CONTEXT_DB
                 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.EXE
                 SYS$SYSTEM:DECSET$START_ENVMGR.EXE
                 SYS$SYSTEM:DECSET$ENVMGR.EXE
                 DECW$SYSTEM_DEFAULTS:DECSET$ENVMGR.DAT
                 DECW$SYSTEM_DEFAULTS:DECSET$ENVMGR.UID
                 SYS$HELP:DECSET$ENVMGR.HLB
                 VUE$LIBRARY:DECSET$MENU.VUE$DAT
                 SYS$STARTUP:DECSET$ENVMGR_STARTUP.COM

     A-6 Sample Installation Procedures

 



                                          Sample Installation Procedures
                        A.1 Sample Installation on an OpenVMS I64 System

            ****************************************************************
            *                                                              *
            * If this installation is performed on a cluster, you must     *
            * execute                                                      *
            *                                                              *
            *    $ @SYS$STARTUP:DECSET$ENVMGR_STARTUP.COM                  *
            *                                                              *
            * on all other nodes in the cluster.  In addition, you must    *
            * add the above line to your system startup procedure.         *
            *                                                              *
            ****************************************************************

        %DECSET-I-DONEENVMGR, The installation of DECset Environment Manager completed

        %DECSET-I-START_CMS, CMS V4.4 installation in progress

        %VMSINSTAL-I-RESTORE, Restoring product save set C ...
        %DECSET-I-ENDRESTORE, All required savesets have been successfully restored
        %DECSET-I-PROHELP, Providing help
        %DECSET-I-PRODCL, Providing DCL verb
        %DECSET-I-PROEXE, Providing images
        %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.CMS].

          The CMS IVP has been moved to the SYS$TEST directory.  To run it after
          the installation enter @SYS$TEST:CMS$IVP.COM.

        %DECSET-I-PROSTART, Providing startup procedure

                ***************************************************************
                *                                                             *
                * If this installation is performed on a cluster, you must    *
                * execute                                                     *
                *                                                             *
                *    $ @SYS$STARTUP:CMS$STARTUP.COM                           *
                *                                                             *
                * on all other nodes in the cluster.  In addition, you must   *
                * add the above line to your system startup procedure.        *
                *                                                             *
                ***************************************************************

        %DECSET-I-DONECMS, The installation of CMS V4.4 completed

        %DECSET-I-START_DTM, DTM 4.3 installation in progress


                                      Sample Installation Procedures A-7

 



     Sample Installation Procedures
     A.1 Sample Installation on an OpenVMS I64 System

     %VMSINSTAL-I-RESTORE, Restoring product save set D ...
     %DECSET-I-ENDRESTORE, All Digital Test Manager savesets have been restored.
     %DECSET-I-PROHELP, Providing Digital Test Manager DCL and DECwindows help.
     %DECSET-I-PRODCL, Providing DCL verb for Digital Test Manager.
     %DECSET-I-PROEXE, Providing Digital Test Manager files.

       The DTM IVP has been moved to the SYS$TEST directory.
       To run the IVP after installation, enter @SYS$TEST:DTM$IVP.COM.

           ***************************************************************
           *                                                             *
           * If this installation is performed on a cluster, you must    *
           * execute                                                     *
           *                                                             *
           *    $ @SYS$STARTUP:DTM$STARTUP.COM                           *
           *                                                             *
           * on all other nodes in the cluster.  In addition, you must   *
           * add the above line to your system startup procedure.        *
           *                                                             *
           ***************************************************************

     %DECSET-I-DONEDTM, The installation of Digital Test Manager V4.3 completed

     %DECSET-I-START_LSE, LSE V5.0 installation in progress

     %VMSINSTAL-I-RESTORE, Restoring product save set E ...
     %TPU-S-SAVEENV, environment written to $2$DKA300:[SYS0.SYSUPD.DECSET127]LSE$SYSTEM_
     ENVIRONMENT.ENV;1
     %TPU-S-FILEIN, 91 lines read from file $2$DKA300:[SYS0.SYSUPD.DECSET127]SET_
     DEF_COMM_LANG.TPU;4
     %TPU-I-PROCSUPERSEDED, definition of procedure LSE$$SYSTEM_MODE_
     SETTINGS superseded
     -TPU-I-SOURCELINE, at source line 1
     5 lines read from file $2$DKA300:[SYS0.SYSUPD.DECSET127]SAVE_DEF_
     COMM_LANG.LSE;4
     File $2$DKA300:[SYS0.SYSUPD.DECSET127]LSE$SECTION.TPU$SECTION;6 created
     2786 procedures, 1861 variables, 1129 keys saved

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

       The LSE IVP has been moved to the SYS$TEST directory.  To run it after
       the installation enter @SYS$TEST:LSE$IVP.COM.

     This installation added or modified the following files:

     A-8 Sample Installation Procedures

 



                                          Sample Installation Procedures
                        A.1 Sample Installation on an OpenVMS I64 System

                SYS$LIBRARY:DCLTABLES.EXE
                SYS$SYSTEM:LSEDIT.EXE
                SYS$LIBRARY:LSESHR.EXE
                SYS$LIBRARY:LSESHR.IIF
                SYS$MESSAGE:LSEMSG.EXE
                SYS$LIBRARY:LSE$CCTSHR.EXE
                SYS$LIBRARY:LSE$DECWSHR.EXE
                SYS$LIBRARY:LSE$SECTION.TPU$SECTION
                SYS$LIBRARY:LSE$DEFAULTS.DAT
                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.HLB
                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.DIA
                SYS$SYSROOT:[SYSTEST.LSE]LSE$IVP.TPU
                SYS$TEST:LSE$IVP.COM





















                                      Sample Installation Procedures A-9

 



     Sample Installation Procedures
     A.1 Sample Installation on an OpenVMS I64 System

             SYS$SYSROOT:[VUE$LIBRARY.USER]LSE$EDIT_QUALIFIERS.EXE
             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.TPU
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$GRAMMAR.TPU
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$GRAMMAR_ADJUSTMENT.TPU
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$GRAMMAR_ALIAS.TPU
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$GRAMMAR_LANGUAGE.TPU
             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.TPU
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$PROMPT.TPU
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$PARSER.TPU
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$PATTERNS.TPU
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$SHOW.TPU
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$SHOW_LIST.TPU
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$HIGHLIGHT.TPU
             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.TPU
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$EVE_EDT.TPU
             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.TPU
             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.TPU
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$EVE_WINDOWS.TPU
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$METHOD.TPU
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$MENUS.TPU
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$MOUSE.TPU
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$VMS_SCA.TPU
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$VMS_CMS.TPU
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$VMS_HELP.TPU
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$EDIT_ICONS.UIL


     A-10 Sample Installation Procedures

 



                                          Sample Installation Procedures
                        A.1 Sample Installation on an OpenVMS I64 System

                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$EDIT_OPTIONS.UIL
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$WIDGETS.UIL
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$CONSTANTS.UIL
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]EVE$CONSTANTS.UIL
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]TPU.ENV
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]PACK_HEADERS.TXT
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]PACK_HEADERS_CLI.TPU
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]PACK_HEADERS_PORT.TPU
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]PACKAGE_SUPPORT.TPU
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]C-SEM-BEGIN-END.LSE
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]C-SEM-COMMON.LSE
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]C-SEM-INDENTED-BEGIN-
        END.LSE
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]C-SEM-K-R.LSE
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]CDU.LSE
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]DCL.LSE
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]HELP.LSE
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LATEX.LSE
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]MAKE.LSE
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]MESSAGE.LSE
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]MMS.LSE
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]PERL.LSE
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]RUNOFF.LSE
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]SDL.LSE
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]SHELL.LSE
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]TABLE.LSE
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]TEXT.LSE
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]TPU.LSE
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]UNKNOWN.LSE
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]XLSE_COMMAND_HELP.HLP
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]XLSE_COMMANDS.TPU
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]XLSE_COMMON.TPU
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]XLSE_COMMON_KEYS.TPU
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]XLSE_EDT.TPU
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]XLSE_EDT_LK201_KEYS.TPU
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]XLSE_EDT_VT100_KEYS.TPU
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]XLSE_ENV.BUI
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]XLSE_HELP.BUI
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]XLSE_LK201_KEYS.TPU
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]XLSE_BUILD.COM
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]XLSE_SECTION.BUI
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]EMACS_SEARCH.TPU
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]RNF_DIFF.TPU


                                     Sample Installation Procedures A-11

 



     Sample Installation Procedures
     A.1 Sample Installation on an OpenVMS I64 System

             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]XLSE_READ_ME.TXT
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LATEX_HELPLIB.HLB

             ***************************************************************
             *                                                             *
             * If this installation is performed on a cluster, you must    *
             * execute                                                     *
             *                                                             *
             *    $ @SYS$STARTUP:LSE$STARTUP.COM                           *
             *                                                             *
             * on all other nodes in the cluster.  In addition, you must   *
             * add the above line to your system startup procedure.        *
             *                                                             *
             ***************************************************************

     %DECSET-I-DONELSE, The installation of LSE V5.0 completed

     %DECSET-I-START_MMS, MMS V3.7 installation in progress

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

     %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.MMS].

       The MMS IVP has been moved to the SYS$TEST directory.  To run it after
       the installation enter @SYS$TEST:MMS$IVP.COM.

             ***************************************************************
             *                                                             *
             * If this installation is performed on a cluster, you must    *
             * execute                                                     *
             *                                                             *
             *    $ @SYS$STARTUP:MMS$STARTUP.COM                           *
             *                                                             *
             * on all other nodes in the cluster.  In addition, you must   *
             * add the above line to your system startup procedure.        *
             *                                                             *
             ***************************************************************

     %DECSET-I-DONEMMS, The installation of MMS V3.7 completed

     %DECSET-I-START_PCA, PCA V4.9 installation in progress

     %VMSINSTAL-I-RESTORE, Restoring product save set G ...
     %VMSINSTAL-I-RESTORE, Restoring product save set H ...
     %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSTEST.PCA].

       The PCA IVP has been moved to the SYS$TEST directory.  To run it after
       the installation enter @SYS$TEST:PCA$IVP.COM.

     A-12 Sample Installation Procedures

 



                                          Sample Installation Procedures
                        A.1 Sample Installation on an OpenVMS I64 System

        %VMSINSTAL-I-RESTORE, Restoring product save set I ...
        %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.PCA].

                ***************************************************************
                *                                                             *
                * If this installation is performed on a cluster, you must    *
                * execute                                                     *
                *                                                             *
                *    $ @SYS$STARTUP:PCA$STARTUP.COM                           *
                *                                                             *
                * on all other nodes in the cluster.  In addition, you must   *
                * add the above line to your system startup procedure.        *
                *                                                             *
                ***************************************************************

        %DECSET-I-DONEPCA, The installation of PCA V4.9 completed

        %DECSET-I-START_SCA, SCA V4.9 installation in progress

        %VMSINSTAL-I-RESTORE, Restoring product save set J ...
        %VMSINSTAL-I-SYSDIR, This product creates system disk directory  VMI$ROOT:[SYSTEST.SCA$IVP].
        %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.SCA].
        %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.SCA.EXAMPLE].
        %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.SCA.2167A].

                ***************************************************************
                *                                                             *
                * If this installation is performed on a cluster, you must    *
                * execute                                                     *
                *                                                             *
                *    $ @SYS$STARTUP:SCA$STARTUP.COM                           *
                *                                                             *
                * on all other nodes in the cluster.  In addition, you must   *
                * add the above line to your system startup procedure.        *
                *                                                             *
                ***************************************************************

        %DECSET-I-DONESCA, The installation of SCA V4.9 completed

        DECset Cookbook installation in progress...

        %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSHLP.EXAMPLES.DECSET].
        %VMSINSTAL-I-RESTORE, Restoring product save set K...
        %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...

                                     Sample Installation Procedures A-13

 



     Sample Installation Procedures
     A.1 Sample Installation on an OpenVMS I64 System

         *********************************************************************
           The DECset collective installation will now run the Installation
           Verification Procedure for each of the components you selected to
           run the IVP.
         *********************************************************************

          +------------------------------------------------------------+
          |         Installation verification command procedure for    |
          |                  DECset Environment Manager                |
          +------------------------------------------------------------+

       Copyright 2005 Hewlett-Packard Development Company, L.P.

      Confidential computer software.  Valid license from HP required for
      possession, use, or copying.  Consistent with FAR 12.211 and 12.212,
      Commercial Computer Software, Computer Software Documentation, and
      Technical Data for Commercial Items are licensed to the U.S. Government
      under vendor's standard commercial license.

      Intel and Itanium are trademarks or registered trademarks of Intel
      Corporation or its subsidiaries in the United States and other countries.

      Microsoft, Windows, and Windows NT are U.S. registered trademarks
      of Microsoft Corporation.

     %ENVMGR-I-BEGINIVP, Beginning DECset Environment Manager V1.7 IVP.

     %ENVMGR-I-ENDIVP, DECset Environment Manager V1.7 IVP completed successfully.

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

       Copyright 2005 Hewlett-Packard Development Company, L.P.

      Confidential computer software.  Valid license from HP required for
      possession, use, or copying.  Consistent with FAR 12.211 and 12.212,
      Commercial Computer Software, Computer Software Documentation, and
      Technical Data for Commercial Items are licensed to the U.S. Government
      under vendor's standard commercial license.

      Intel and Itanium are trademarks or registered trademarks of Intel
      Corporation or its subsidiaries in the United States and other countries.

      Microsoft, Windows, and Windows NT are U.S. registered trademarks
      of Microsoft Corporation.

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

     A-14 Sample Installation Procedures

 



                                          Sample Installation Procedures
                        A.1 Sample Installation on an OpenVMS I64 System

        %CMS-I-IVPBEGIN, Begin CMS V4.4 Installation Verification Procedure
        %CMS-S-CREATED, CMS Library $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
        TEST] created
        %CMS-I-LIBIS, library is $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
        TEST]
        %CMS-S-LIBSET, library set
        %CMS-I-LIBIS, library is $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
        TEST]
        %CMS-S-LIBSET, library set
        -CMS-I-SUPERSEDE, library list superseded
        %CMS-S-CREATED, element $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
        TEST]CMS$IVP_TEST.FILE created
        %CMS-S-RESERVED, generation 1 of element $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
        TEST]
        CMS$IVP_TEST.FILE reserved

        Reservations in CMS Library $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
        TEST]

        CMS$IVP_TEST.FILE
            (1)   JONES     1      10-JAN-2005 15:47:49 ""
        %CMS-S-GENCREATED, generation 2 of element $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
        TEST]
        CMS$IVP_TEST.FILE created
        -CMS-I-NOCHANGES, no changes
        %CMS-I-VERCLS, class list verified
        %CMS-I-VERCMD, command list verified
        %CMS-I-VERELE, element list verified
        %CMS-I-VERGRP, group list verified
        %CMS-I-VERRES, reservation list verified
        %CMS-I-VERFRE, internal free space list verified
        %CMS-I-VERFRE, internal free space list verified
        %CMS-I-VERFRE, internal free space list verified
        %CMS-I-VERFRE, internal free space list verified
        %CMS-I-VERFRE, internal free space list verified
        %CMS-I-VERFRE, internal free space list verified
        %CMS-I-VERFRE, internal free space list verified
        %CMS-I-VERARC, archive control block verified
        %CMS-I-VER2, internal contiguous space verified
        %CMS-I-VERCON, control file verified
        %CMS-I-VEREDF, element $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
        TEST]CMS$IVP_TEST.FILE verified
        %CMS-I-VEREDFS, element data files verified
        %CMS-S-VERIFIED, library $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_

                                     Sample Installation Procedures A-15

 



     Sample Installation Procedures
     A.1 Sample Installation on an OpenVMS I64 System

     TEST] verified
     %CMS-S-FETCHED, generation 1 of element $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
     TEST]
     CMS$IVP_TEST.FILE fetched
     %CMS-I-FILEXISTS, file already exists, $2$DKA300:[SYS0.SYSUPD.DECSET127]CMS$IVP_
     TEST.FILE;2 created
     %CMS-S-FETCHED, generation 2 of element $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
     TEST]
     CMS$IVP_TEST.FILE fetched
     %CMS-S-IDENTICAL, files are identical
     %CMS-S-CREATED, class $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
     TEST]CL1 created
     %CMS-S-GENINSERTED, generation 1 of element $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
     TEST]
     CMS$IVP_TEST.FILE inserted into class $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
     TEST]CL1
     %CMS-S-CREATED, class $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
     TEST]CL2 created
     %CMS-S-GENINSERTED, generation 2 of element $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
     TEST]
     CMS$IVP_TEST.FILE inserted into class $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
     TEST]CL2
     %CMS-S-FETCHED, generation 2 of element $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
     TEST]
     CMS$IVP_TEST.FILE fetched

     Elements in CMS Library $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
     TEST]

     CMS$IVP_TEST.FILE ""

     Element generations in CMS Library
             $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]

     CMS$IVP_TEST.FILE
       2     10-JAN-2005 15:47:50 JONES ""
       1     10-JAN-2005 15:47:48 JONES ""

     Classes in CMS Library $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
     TEST]

     CL1             "Test1"
     CL2             "Test2"

     Element generations in CMS Library
     $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]

     A-16 Sample Installation Procedures

 



                                          Sample Installation Procedures
                        A.1 Sample Installation on an OpenVMS I64 System

        CMS$IVP_TEST.FILE/2
        %CMS-S-GENREMOVED, generation 2 of element $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
        TEST]
        CMS$IVP_TEST.FILE removed from class $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
        TEST]CL2
        %CMS-S-DELETED, class $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
        TEST]CL2 deleted
        %CMS-S-GENREMOVED, generation 1 of element $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
        TEST]
        CMS$IVP_TEST.FILE removed from class $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
        TEST]CL1
        %CMS-S-DELETED, class $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
        TEST]CL1 deleted
        %CMS-S-CREATED, group $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
        TEST]GR1 created
        %CMS-S-CREATED, group $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
        TEST]GR2 created
        %CMS-S-INSERTED, group $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
        TEST]GR1 inserted into group
        $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]GR2
        %CMS-S-REMOVED, group $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
        TEST]GR1 removed from group
        $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]GR2
        %CMS-S-MODIFIED, group $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
        TEST]GR1 modified

        Groups in CMS Library $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
        TEST]

        GR2                 GR3

        %CMS-S-IVPSUCCESS, CMS V4.4 IVP completed successfully.
        %CMS-I-IVPEND, End Installation Verification Procedure

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

          Copyright 2005 Hewlett-Packard Development Company, L.P.

         Confidential computer software.  Valid license from HP required for
         possession, use, or copying.  Consistent with FAR 12.211 and 12.212,
         Commercial Computer Software, Computer Software Documentation, and
         Technical Data for Commercial Items are licensed to the U.S. Government
         under vendor's standard commercial license.

         Intel and Itanium are trademarks or registered trademarks of Intel
         Corporation or its subsidiaries in the United States and other countries.

                                     Sample Installation Procedures A-17

 



     Sample Installation Procedures
     A.1 Sample Installation on an OpenVMS I64 System

      Microsoft, Windows, and Windows NT are U.S. registered trademarks
      of Microsoft Corporation.

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

     %DTM-I-BEGINIVP, Beginning Digital Test Manager V4.3 IVP.
     %DTM-S-CREATED, Digital Test Manager library $2$DKA300:[SYS0.SYSUPD.DECSET127.DTMTEST] created
     %DTM-S-LIBIS, Digital Test Manager library is $2$DKA300:[SYS0.SYSUPD.DECSET127.DTMTEST]
     %DTM-I-DEFAULTED, benchmark file name defaulted to TESTX.BMK
     %DTM-S-CREATED, test description TESTX created
     %DTM-S-MODIFIED, test description TESTX modified
     %DTM-I-DEFAULTED, benchmark file name defaulted to DECWX.BMK
     %DTM-I-DEFAULTED, template file name defaulted to DECWX.SESSION
     %DTM-S-CREATED, test description DECWX created

     Test Descriptions in Digital Test Manager Library
     $2$DKA300:[SYS0.SYSUPD.DECSET127.DTMTEST]

     DECWX           "decwindows test"
         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 Specified
     %DTM-S-CREATED, symbol variable VAR1 created
     %DTM-S-MODIFIED, variable VAR1 modified

     Variables in Digital Test Manager Library $2$DKA300:[SYS0.SYSUPD.DECSET127.DTMTEST]

     VAR1            "first variable"
         Value = NEWVALUE
     %DTM-S-CREATED, group GROUP1 created

     Groups in Digital Test Manager Library $2$DKA300:[SYS0.SYSUPD.DECSET127.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

     Groups in Digital Test Manager Library $2$DKA300:[SYS0.SYSUPD.DECSET127.DTMTEST]

     A-18 Sample Installation Procedures

 



                                          Sample Installation Procedures
                        A.1 Sample Installation on an OpenVMS I64 System

        GROUP1              GROUP2
        %DTM-S-CREATED, collection COLL1 created

        Collections in Digital Test Manager Library $2$DKA300:[SYS0.SYSUPD.DECSET127.DTMTEST]

        COLL1          1 test    10-JAN-2005 15:48:20
               Command: CREATE COLLECTION/NOVERIFY COLL1 TESTX "test collection"
               Status: not run

        %DTM-S-DELETED, collection COLL1 deleted
        %DTM-I-DELETED, test_description DECWX deleted
        %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 verified
        %DTM-I-VERTD, test description list verified
        %DTM-I-VERVAR, variables list verified
        %DTM-I-VERARC, archive list verified
        %DTM-I-VERHEAD, user header information verified
        %DTM-I-VERSPACE, contiguous space verified
        %DTM-I-VERCOLDIR, collection directory structure verified
        %DTM-S-VERIFIED, Digital Test Manager library $2$DKA300:[SYS0.SYSUPD.DECSET127.DTMTEST] verified
        %DTM-I-ENDIVP, DTM V4.3 IVP completed successfully.

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

          Copyright 2005 Hewlett-Packard Development Company, L.P.

         Confidential computer software.  Valid license from HP required for
         possession, use, or copying.  Consistent with FAR 12.211 and 12.212,
         Commercial Computer Software, Computer Software Documentation, and
         Technical Data for Commercial Items are licensed to the U.S. Government
         under vendor's standard commercial license.

         Intel and Itanium are trademarks or registered trademarks of Intel
         Corporation or its subsidiaries in the United States and other countries.

         Microsoft, Windows, and Windows NT are U.S. registered trademarks
         of Microsoft Corporation.

                                     Sample Installation Procedures A-19

 



     Sample Installation Procedures
     A.1 Sample Installation on an OpenVMS I64 System

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

     %LSE-I-BEGINIVP, Beginning Language-Sensitive Editor V5.0 IVP.

     36 lines written to file SYS$SYSROOT:[SYSMGR]LSE$IVP.LIS;1

     %LSE-I-ENDIVP, Language-Sensitive Editor V5.0 IVP completed sucessfully.

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

       Copyright 2005 Hewlett-Packard Development Company, L.P.

      Confidential computer software.  Valid license from HP required for
      possession, use, or copying.  Consistent with FAR 12.211 and 12.212,
      Commercial Computer Software, Computer Software Documentation, and
      Technical Data for Commercial Items are licensed to the U.S. Government
      under vendor's standard commercial license.

      Intel and Itanium are trademarks or registered trademarks of Intel
      Corporation or its subsidiaries in the United States and other countries.

      Microsoft, Windows, and Windows NT are U.S. registered trademarks
      of Microsoft Corporation.

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

     %MMS-I-BEGINIVP, Beginning Module Management System V3.7 IVP.
     %MMS-I-ENDIVP, Module Management System V3.7 IVP completed successfully.

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

       Copyright 2005 Hewlett-Packard Development Company, L.P.

      Confidential computer software.  Valid license from HP required for
      possession, use, or copying.  Consistent with FAR 12.211 and 12.212,
      Commercial Computer Software, Computer Software Documentation, and
      Technical Data for Commercial Items are licensed to the U.S. Government
      under vendor's standard commercial license.

      Intel and Itanium are trademarks or registered trademarks of Intel
      Corporation or its subsidiaries in the United States and other countries.

      Microsoft, Windows, and Windows NT are U.S. registered trademarks
      of Microsoft Corporation.

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

     %PCA-I-BEGINIVP, Beginning PCA V4.9 IVP

     A-20 Sample Installation Procedures

 



                                          Sample Installation Procedures
                        A.1 Sample Installation on an OpenVMS I64 System

            Saving previously defined PCA logical names...
            Linking IVP image file...
            Running Collector test...
            Running Analyzer test...
            Checking test results...

        %PCA-I-IVPPASS, PCA V4.9 IVP completed successfully.

            Deleting temporary files...
            Restoring logical names...

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

          Copyright 2005 Hewlett-Packard Development Company, L.P.

         Confidential computer software.  Valid license from HP required for
         possession, use, or copying.  Consistent with FAR 12.211 and 12.212,
         Commercial Computer Software, Computer Software Documentation, and
         Technical Data for Commercial Items are licensed to the U.S. Government
         under vendor's standard commercial license.

         Intel and Itanium are trademarks or registered trademarks of Intel
         Corporation or its subsidiaries in the United States and other countries.

         Microsoft, Windows, and Windows NT are U.S. registered trademarks
         of Microsoft Corporation.

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

        %SCA-I-BEGINIVP, Beginning Source Code Analyzer V4.9 IVP.

        ****  Client testing complete  ****
        %SCA-I-ENDIVP, Source Code Analyzer V4.9 IVP completed successfully.

         Installation Verification Procedure Summary
                *******************************************

         DECset Environment Manager V1.7           Passed
         Code Management System V4.4      Passed
         Digital Test Manager V4.3    Passed
         Language-Sensitive Editor V5.0           Passed
         Module Management System V3.7    Passed
         Performance and Coverage Analyzer V4.9    Passed
         Source Code Analyzer V4.9    Passed
         Installation of DECSET V12.7 completed at 15:57

            Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY

            Creating installation data file: VMI$ROOT:[SYSUPD]DECSET127.VMI_
        DATA

                                     Sample Installation Procedures A-21

 



     Sample Installation Procedures
     A.1 Sample Installation on an OpenVMS I64 System

      VMSINSTAL procedure done at 15:57


     A.2 Sample Upgrade on an OpenVMS Alpha System

     @SYS$UPDATE:VMSINSTAL DKA300:[DECSET124.KIT]<Return>
      OpenVMS Alpha Software Product Installation Procedure Version 8.2

     It is 10-JAN-2005 at 15:31.

     Enter a question mark (?) at any time for help.
     * Are you satisfied with the backup of your system disk [YES]? <Return>

     Enter the products to be processed from the first distribution volume set.
     * Products: decset127 <Return>
     * Enter installation options you wish to use (none): <Return>

     The following products will be processed:
       DECSET V12.7

      Beginning installation of DECSET V12.7 at 15:31

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

               - DECset Collective Installation Procedure -

         This is the collective installation procedure for all of the
         DECset components:

               DECset Environment Manager for OpenVMS (ENVMGR)
               Code Management System for OpenVMS (CMS)
               Digital Test Manager for OpenVMS (DTM)
               Language-Sensitive Editor for OpenVMS (LSE)
               Module Management System for OpenVMS (MMS)
               Performance and Coverage Analyzer for OpenVMS (PCA)
               Source Code Analyzer for OpenVMS (SCA)

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

       Copyright 2005 Hewlett-Packard Development Company, L.P.

      Confidential computer software.  Valid license from HP required for
      possession, use, or copying.  Consistent with FAR 12.211 and 12.212,
      Commercial Computer Software, Computer Software Documentation, and
      Technical Data for Commercial Items are licensed to the U.S. Government
      under vendor's standard commercial license.

     A-22 Sample Installation Procedures

 



                                          Sample Installation Procedures
                           A.2 Sample Upgrade on an OpenVMS Alpha System

         Intel and Itanium are trademarks or registered trademarks of Intel
         Corporation or its subsidiaries in the United States and other countries.

         Microsoft, Windows, and Windows NT are U.S. registered trademarks
         of Microsoft Corporation.

                 These are the options provided by this collective
                 installation procedure:

                 DECset components:

                         - all the DECset components
                         - Language-Sensitive Editor (LSE)
                         - Source Code Analyzer (SCA)
                         - Code Management System (CMS)
                         - Digital Test Manager (DTM)
                         - Performance and Coverage Analyzer (PCA)
                         - Module Management System (MMS)
                         - DECset Cookbook - PostScript Format
                         - DECset Cookbook - HTML Format
                         - DECset Cookbook - Text Format

           Please choose your option(s):

        * Do you want all the DECset components [YES]? <Return>
        * Are you sure you want to install all the options [YES]? <Return>

        %DECSET-I-AGGREGATE, Checking resources required to install selected products.

        %DECSET-I-START_ENVMGR, The following questions relate to DECset ENVMGR installation.

           The DECset Environment Manager (ENVMGR) consists of:

                . A run-time component used by DECset layered products,
                . A DCL interface, and
                . A DECwindows interface.

           The DCL and DECwindows interface components are optional.

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

        %DECSET-I-START_CMS, The following questions relate to CMS installation.

        * Do you want to install the CMS DECwindows interface [YES]? <Return>

         On OpenVMS Alpha CMS can support element names using Extended
         File Specifications.  The option exists to install CMS with or
         without support for Extended File Specifications.

        * Install Extended File Specification support [YES]? no <Return>

                                     Sample Installation Procedures A-23

 



     Sample Installation Procedures
     A.2 Sample Upgrade on an OpenVMS Alpha System

             Product:      VAXSET
             Producer:     DEC
             Version:      12.7

             Product:      CMS
             Producer:     DEC
             Version:      4.4

     * Is one of these authorization keys registered and loaded [YES]? <Return>
     * Do you want to run the IVP after the installation [YES]? <Return>
     * Do you want to purge files replaced by this installation [YES]? <Return>

     %DECSET-I-DONEASK, You have answered all the questions for CMS installation

     %DECSET-I-START_DTM, The following questions relate to DTM installation.

             Product:      VAXSET
             Producer:     DEC
             Version:      12.7

             Product:      DTM
             Producer:     DEC
             Version:      4.3

     * Is one of these authorization keys registered and loaded [YES]?: <Return>
     * Do you want to run the IVP after the installation [YES]? <Return>
     * Do you want to purge files replaced by this installation [YES]? <Return>

     %DECSET-I-CMSUSER, CMS concurrent use license found.

       With CMS capabilities installed, Digital Test Manager will have full
       CMS integration and perform more effectively.  If you install with CMS
       capabilities, Digital Test Manager will use a CMS concurrent use
       license unit.

       HP recommends you install Digital Test Manager with CMS capabilities.

     * Install Digital Test Manager with built-in CMS capabilities [YES]? <Return>

     %DECSET-I-DONEASK, You have answered all the questions for Digital Test Manager installation

     %DECSET-I-START_LSE, The following questions relate to LSE installation.

             Product:      VAXSET
             Producer:     DEC
             Version:      12.7

             Product:      LSE
             Producer:     DEC
             Version:      5.0

     A-24 Sample Installation Procedures

 



                                          Sample Installation Procedures
                           A.2 Sample Upgrade on an OpenVMS Alpha System

        * Is one of these authorization keys registered and loaded [YES]? <Return>
        * Do you want to purge files replaced by this installation [YES]? <Return>
        * Do you want to run the IVP after the installation [YES]? <Return>

            Please note that the total system disk space consumed by the unsupported
            LSE source files is approximately 16,000 blocks.  HP recommends not
            to answer yes to the following prompt if you are constrained by the free
            space available on your system disk.

        * Would you like to install the unsupported LSE source files [YES]? <Return>

          The files will be installed in SYS$SYSROOT[SYSHLP.EXAMPLES.LSE]

             The version of LSE that is currently being installed has two command
             languages:  the VMSLSE command language, and the PORTABLE command
             language.  The VMSLSE command language is the original LSE command
             language that has always been present in LSE.  The PORTABLE command
             language is a later command language that was designed as LSE's command
             language on platforms other than OpenVMS.

             If you would like to have the PORTABLE command language as the system-

             wide default command language, you should specify PORTABLE as the
             default command language.

             If you would like to have the VMSLSE command language as the system-

             wide default command language, you should specify VMSLSE as the default
             command language.

             Individual users may override the system default command language.

        * Do you want default command language to be PORTABLE or VMSLSE  [VMSLSE]: VMSLSE <Return>

            Language templates for Ada, Ada95, BASIC, BLISS, C, COBOL, C++, FORTRAN,
            FORTRAN 90, HTML, Java, MACRO, Pascal, and PL/I as well as templates for
            the LSE command languages are included in this kit.  Templates for other
            languages that support LSE and are not mentioned are provided in the
            installation kits for those languages.

            Please choose the languages for which you would like to install support:




                                     Sample Installation Procedures A-25

 



     Sample Installation Procedures
     A.2 Sample Upgrade on an OpenVMS Alpha System

     * Do you want to install language support for ADA [YES]? <Return>
     * Do you want to install language support for ADA95 [YES]? <Return>
     * Do you want to install language support for BASIC [YES]? <Return>
     * Do you want to install language support for BLISS [YES]? <Return>
     * Do you want to install language support for C [YES]? <Return>
     * Do you want to install language support for COBOL [YES]? <Return>
     * Do you want to install language support for CXX [YES]? <Return>
     * Do you want to install language support for FORTRAN [YES]? <Return>
     * Do you want to install language support for F90 [YES]? <Return>
     * Do you want to install language support for HTML [YES]? <Return>
     * Do you want to install language support for JAVA [YES]? <Return>
     * Do you want to install language support for MACRO [YES]? <Return>
     * Do you want to install language support for PASCAL [YES]? <Return>
     * Do you want to install language support for PLI [YES]? <Return>
     * Do you want to install language support for LSE [YES]? <Return>
     * Do you want to install language support for PLSE [YES]? <Return>

     %DECSET-I-DONEASK, You have answered all the questions for LSE installation

     %DECSET-I-START_MMS, The following questions relate to MMS installation.

             Product:      VAXSET
             Producer:     DEC
             Version:      12.7

             Product:      MMS
             Producer:     DEC
             Version:      3.7

     * Is one of these authorization keys registered and loaded [YES]? <Return>
     * Do you want to run the IVP after the installation [YES]? <Return>
     * Do you want to purge files replaced by this installation [YES]? <Return>

     %DECSET-I-DONEASK, You have answered all the questions for MMS installation

     %DECSET-I-START_PCA, The following questions relate to PCA installation.

             Product:      VAXSET
             Producer:     DEC
             Version:      12.7

             Product:      PCA
             Producer:     DEC
             Version:      4.9

     A-26 Sample Installation Procedures

 



                                          Sample Installation Procedures
                           A.2 Sample Upgrade on an OpenVMS Alpha System

        * Is one of these authorization keys registered and loaded [YES]? <Return>
        * Do you want to run the IVP after the installation [YES]? <Return>
        * Do you want to purge files replaced by this installation [YES]? <Return>
        * Do you wish to install the PCA DECwindows analyzer [YES]? <Return>
        * Do you wish to install the PCA DECwindows collector [YES]? <Return>
        * Do you want to install the PCA demo package [YES]? <Return>

        %DECSET-I-DONEASK, You have answered all the questions for PCA installation

        %DECSET-I-START_SCA, The following questions relate to SCA installation.

                Product:      VAXSET
                Producer:     DEC
                Version:      12.7

                Product:      LSE
                Producer:     DEC
                Version:      5.0

                Note: LSE and SCA share the LSE license.

        * Is one of these authorization keys registered and loaded [YES]? <Return>

                As well as verifying that the installation succeeded, the IVP also
                creates the SCA example library.  It is therefore recommended that
                you run the IVP.

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

                The IVP has two sections, a character-cell section and a DECwindows
                section.  In order for the DECwindows section to run correctly, the
                logical name DECW$DISPLAY must be appropriately set (using the SET
                DISPLAY command).  If at this time you are not prepared to run the
                DECwindows portion of the IVP, enter NO at the following prompt.

         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>
        * Do you want to purge files replaced by this installation [YES]? <Return>

                Please indicate the components of SCA that you wish to install:

                    1 - Both SCA client and server
                    2 - SCA client only

        * Enter the number corresponding to the SCA components to install [1]: <Return>

                                     Sample Installation Procedures A-27

 



     Sample Installation Procedures
     A.2 Sample Upgrade on an OpenVMS Alpha System

       In order to grant access to remote users who do not have a proxy account
       for the local node, SCA creates the SCA$DEFAULT account, which is
       used as a default proxy account for SCA library access.

       This account has no special privileges.

       The password for the account should normally be automatically generated by SCA.

       A user-supplied password may also be given (minimum size 10).  If a
       user-supplied password is provided it will not be logged in the
       Auto Answer file and cannot be used for automated installs.

       If the account does not already exist you will be asked to specify a
       unique UIC for the account.

          You must specify a unique UIC for this account in order
          to ensure proper security of your libraries.

     * Do you want to specify a password [NO]? <Return>
     * Enter UIC for SCA$DEFAULT account (include brackets) [[371,345]]: <Return>

       In order to ensure that the SCA server runs with the proper quotas,
       this installation procedure will create an account for the server.  This
       account, SCA$SERVER, has no special privileges and is set up only for
       network operation.

       The password for the account should normally be automatically generated by SCA.

       A user-supplied password may also be given (minimum size 10), a reason
       for a user-supplied password is when multiple network databases need updating
       in a cluster.  If a user-supplied password is provided it will not be logged
       in the Auto Answer file and cannot be used for automated installs.

       If the account does not already exist you will be asked to specify a
       unique UIC for the account.

          You must specify a unique UIC for this account in order to ensure
          proper security of your libraries.  The SCA server account is
          automatically granted access to each library created, via Access
          Control Lists.

       If you want to change the name of this account after the installation
       has completed, you must also change the password in the NCP database
       with the SET OBJECT SCA$SERVER PASSWORD command.

     * Do you want to specify a password [NO]? <Return>
     * Enter UIC for SCA$SERVER account (include brackets) [[370,355]]: <Return>

     %DECSET-I-DONEASK, You have answered all the questions for SCA installation

     A-28 Sample Installation Procedures

 



                                          Sample Installation Procedures
                           A.2 Sample Upgrade on an OpenVMS Alpha System

            ***********************************************************************
              If you are satisfied with your answers, answer YES to the following
              prompt.  If not, answer NO to start the auto-answer session again.
            ***********************************************************************

        * Are you satisfied with your answers to selected DECset components ?  [YES]? <Return>

        %DECSET-I-DONEASK, You have answered all the questions for DECset installation

          The installation will complete in 11-33 minutes depending
          on the installation media and processor type.

             ********************************************************************
               The installation procedure will now install the selected
               DECset components one by one.

             DECset Environment Manager V1.7
             Code Management System V4.4
             Digital Test Manager V4.3
             Language-Sensitive Editor V5.0
             Module Management System V3.7
             Performance and Coverage Analyzer V4.9
             Source Code Analyzer V4.9
             DECset Cookbook - PostScript Format
             DECset Cookbook - HTML Format
             DECset Cookbook - Text Format
             ********************************************************************

        %DECSET-I-START_ENVMGR, DECset Environment Manager V1.7 installation in progress

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

          The ENVMGR IVP has been moved to the SYS$TEST directory.  To run it after
          the installation enter @SYS$TEST:ENVMGR$IVP.COM.

        The installation of ENVMGR has added or modified:









                                     Sample Installation Procedures A-29

 



     Sample Installation Procedures
     A.2 Sample Upgrade on an OpenVMS Alpha System

                 SYS$HELP:ENVMGR017_RELEASE_NOTES.PS
                 SYS$TEST:ENVMGR$IVP.COM
                 SYS$TEST:ENVMGR$SAMPLE.DECSET_CONTEXT_DB
                 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.EXE
                 SYS$SYSTEM:DECSET$START_ENVMGR.EXE
                 SYS$SYSTEM:DECSET$ENVMGR.EXE
                 DECW$SYSTEM_DEFAULTS:DECSET$ENVMGR.DAT
                 DECW$SYSTEM_DEFAULTS:DECSET$ENVMGR.UID
                 SYS$HELP:DECSET$ENVMGR.HLB
                 VUE$LIBRARY:DECSET$MENU.VUE$DAT
                 SYS$STARTUP:DECSET$ENVMGR_STARTUP.COM

         ****************************************************************
         *                                                              *
         * If this installation is performed on a cluster, you must     *
         * execute                                                      *
         *                                                              *
         *    $ @SYS$STARTUP:DECSET$ENVMGR_STARTUP.COM                  *
         *                                                              *
         * on all other nodes in the cluster.  In addition, you must    *
         * add the above line to your system startup procedure.         *
         *                                                              *
         ****************************************************************

     %DECSET-I-DONEENVMGR, The installation of DECset Environment Manager V1.7 completed

     %DECSET-I-START_CMS, CMS V4.4 installation in progress

     %VMSINSTAL-I-RESTORE, Restoring product save set C ...
     %DECSET-I-ENDRESTORE, All required savesets have been successfully restored
     %DECSET-I-CMSSHR, Linking shareable image
     %DECSET-I-CMS, Linking main image
     %DECSET-I-EVENTACT, Linking the event action image
     %DECSET-I-PROHELP, Providing help
     %DECSET-I-PRODCL, Providing DCL verb
     %DECSET-I-PROEXE, Providing images
     %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.CMS].
     %CREATE-I-EXISTS, VMI$COMMON:[SYSHLP.EXAMPLES.CMS] already exists


     A-30 Sample Installation Procedures

 



                                          Sample Installation Procedures
                           A.2 Sample Upgrade on an OpenVMS Alpha System

          The CMS IVP has been moved to the SYS$TEST directory.  To run it after
          the installation enter @SYS$TEST:CMS$IVP.COM.

        %DECSET-I-PROSTART, Providing startup procedure

                ***************************************************************
                *                                                             *
                * If this installation is performed on a cluster, you must    *
                * execute                                                     *
                *                                                             *
                *    $ @SYS$STARTUP:CMS$STARTUP.COM                           *
                *                                                             *
                * on all other nodes in the cluster.  In addition, you must   *
                * add the above line to your system startup procedure.        *
                *                                                             *
                ***************************************************************

        %DECSET-I-DONECMS, The installation of CMS V4.4 completed

        %DECSET-I-START_DTM, DTM V4.3 installation in progress

        %VMSINSTAL-I-RESTORE, Restoring product save set D ...
        %DECSET-I-ENDRESTORE, All Digital Test Manager savesets have been restored.
        %DECSET-I-PROHELP, Providing Digital Test Manager DCL and DECwindows help.
        %DECSET-I-PRODCL, Providing DCL verb for Digital Test Manager.
        %DECSET-I-PROEXE, Providing Digital Test Manager files.

          The Digital Test Manager IVP has been moved to the SYS$TEST directory.
          To run the IVP after installation, enter @SYS$TEST:DTM$IVP.COM.

              ***************************************************************
              *                                                             *
              * If this installation is performed on a cluster, you must    *
              * execute                                                     *
              *                                                             *
              *    $ @SYS$STARTUP:DTM$STARTUP.COM                           *
              *                                                             *
              * on all other nodes in the cluster.  In addition, you must   *
              * add the above line to your system startup procedure.        *
              *                                                             *
              ***************************************************************

        %DECSET-I-DONEDTM, The installation of Digital Test Manager V4.3 completed

        %DECSET-I-START_LSE, LSE V5.0 installation in progress

                                     Sample Installation Procedures A-31

 



     Sample Installation Procedures
     A.2 Sample Upgrade on an OpenVMS Alpha System

     %VMSINSTAL-I-RESTORE, Restoring product save set E ...
     %TPU-S-SAVEENV, environment written to $2$DKA300:[SYS0.SYSUPD.DECSET127]LSE$SYSTEM_
     ENVIRONMENT.ENV;1
     %TPU-S-FILEIN, 91 lines read from file $2$DKA300:[SYS0.SYSUPD.DECSET127]SET_
     DEF_COMM_LANG.TPU;4
     %TPU-I-PROCSUPERSEDED, definition of procedure LSE$$SYSTEM_MODE_
     SETTINGS superseded
     -TPU-I-SOURCELINE, at source line 1
     5 lines read from file $2$DKA300:[SYS0.SYSUPD.DECSET127]SAVE_DEF_
     COMM_LANG.LSE;4
     File $2$DKA300:[SYS0.SYSUPD.DECSET127]LSE$SECTION.TPU$SECTION;6 created
     2786 procedures, 1861 variables, 1129 keys saved

     %VMSINSTAL-I-SYSDIR, This product creates system disk directory  VMI$ROOT:[SYSTEST.LSE].
     %CREATE-I-EXISTS, VMI$ROOT:[SYSTEST.LSE] already exists
     %VMSINSTAL-I-SYSDIR, This product creates system disk directory  VMI$ROOT:[SYSHLP.EXAMPLES.LSE].
     %CREATE-I-EXISTS, VMI$ROOT:[SYSHLP.EXAMPLES.LSE] already exists

       The LSE IVP has been moved to the SYS$TEST directory.  To run it after
       the installation enter @SYS$TEST:LSE$IVP.COM.

     This installation added or modified the following files:

             SYS$LIBRARY:DCLTABLES.EXE
             SYS$SYSTEM:LSEDIT.EXE
             SYS$LIBRARY:LSESHR.EXE
             SYS$LIBRARY:LSESHR.IIF
             SYS$MESSAGE:LSEMSG.EXE
             SYS$LIBRARY:LSE$CCTSHR.EXE
             SYS$LIBRARY:LSE$DECWSHR.EXE
             SYS$LIBRARY:LSE$SECTION.TPU$SECTION
             SYS$LIBRARY:LSE$DEFAULTS.DAT
             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.HLB
             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.DIA

     A-32 Sample Installation Procedures

 



                                          Sample Installation Procedures
                           A.2 Sample Upgrade on an OpenVMS Alpha System

                SYS$SYSROOT:[SYSTEST.LSE]LSE$IVP.TPU
                SYS$TEST:LSE$IVP.COM
                SYS$SYSROOT:[VUE$LIBRARY.USER]LSE$EDIT_QUALIFIERS.EXE
                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.TPU
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$GRAMMAR.TPU
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$GRAMMAR_ADJUSTMENT.TPU
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$GRAMMAR_ALIAS.TPU
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$GRAMMAR_LANGUAGE.TPU
                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.TPU
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$PROMPT.TPU
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$PARSER.TPU
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$PATTERNS.TPU
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$SHOW.TPU
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$SHOW_LIST.TPU
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$HIGHLIGHT.TPU
                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.TPU
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$EVE_EDT.TPU
                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.TPU
                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.TPU
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$EVE_WINDOWS.TPU
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$METHOD.TPU
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$MENUS.TPU
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$MOUSE.TPU
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$VMS_SCA.TPU
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$VMS_CMS.TPU


                                     Sample Installation Procedures A-33

 



     Sample Installation Procedures
     A.2 Sample Upgrade on an OpenVMS Alpha System

             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
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$WIDGETS.UIL
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LSE$CONSTANTS.UIL
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]EVE$CONSTANTS.UIL
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]TPU.ENV
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]PACK_HEADERS.TXT
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]PACK_HEADERS_CLI.TPU
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]PACK_HEADERS_PORT.TPU
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]PACKAGE_SUPPORT.TPU
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]C-SEM-BEGIN-END.LSE
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]C-SEM-COMMON.LSE
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]C-SEM-INDENTED-BEGIN-
     END.LSE
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]C-SEM-K-R.LSE
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]CDU.LSE
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]DCL.LSE
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]HELP.LSE
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LATEX.LSE
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]MAKE.LSE
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]MESSAGE.LSE
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]MMS.LSE
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]PERL.LSE
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]RUNOFF.LSE
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]SDL.LSE
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]SHELL.LSE
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]TABLE.LSE
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]TEXT.LSE
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]TPU.LSE
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]UNKNOWN.LSE
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]XLSE_COMMAND_HELP.HLP
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]XLSE_COMMANDS.TPU
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]XLSE_COMMON.TPU
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]XLSE_COMMON_KEYS.TPU
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]XLSE_EDT.TPU
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]XLSE_EDT_LK201_KEYS.TPU
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]XLSE_EDT_VT100_KEYS.TPU
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]XLSE_ENV.BUI
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]XLSE_HELP.BUI
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]XLSE_LK201_KEYS.TPU
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]XLSE_BUILD.COM
             SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]XLSE_SECTION.BUI


     A-34 Sample Installation Procedures

 



                                          Sample Installation Procedures
                           A.2 Sample Upgrade on an OpenVMS Alpha System

                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]EMACS_SEARCH.TPU
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]RNF_DIFF.TPU
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]XLSE_READ_ME.TXT
                SYS$SYSROOT:[SYSHLP.EXAMPLES.LSE]LATEX_HELPLIB.HLB

                ***************************************************************
                *                                                             *
                * If this installation is performed on a cluster, you must    *
                * execute                                                     *
                *                                                             *
                *    $ @SYS$STARTUP:LSE$STARTUP.COM                           *
                *                                                             *
                * on all other nodes in the cluster.  In addition, you must   *
                * add the above line to your system startup procedure.        *
                *                                                             *
                ***************************************************************

        %DECSET-I-DONELSE, The installation of LSE V5.0 completed

        %DECSET-I-START_MMS, MMS V3.7 installation in progress

        %VMSINSTAL-I-RESTORE, Restoring product save set F ...
        %DECSET-I-NOFMSIMG, FMS shareable image was not found.
        %DECSET-I-NOFMSSUPP, MMS will not contain support for FMS form libraries.
        %DECSET-I-LINKIMAGE, Linking MMS V3.7.
        %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.MMS].

        %CREATE-I-EXISTS, VMI$COMMON:[SYSHLP.EXAMPLES.MMS] already exists

          The MMS IVP has been moved to the SYS$TEST directory.  To run it after
          the installation enter @SYS$TEST:MMS$IVP.COM.

                ***************************************************************
                *                                                             *
                * If this installation is performed on a cluster, you must    *
                * execute                                                     *
                *                                                             *
                *    $ @SYS$STARTUP:MMS$STARTUP.COM                           *
                *                                                             *
                * on all other nodes in the cluster.  In addition, you must   *
                * add the above line to your system startup procedure.        *
                *                                                             *
                ***************************************************************

        %DECSET-I-DONEMMS, The installation of MMS V3.7 completed

        %DECSET-I-START_PCA, PCA V4.9 installation in progress

                                     Sample Installation Procedures A-35

 



     Sample Installation Procedures
     A.2 Sample Upgrade on an OpenVMS Alpha System

     %VMSINSTAL-I-RESTORE, Restoring product save set G ...
     %VMSINSTAL-I-RESTORE, Restoring product save set H ...
     %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSTEST.PCA].
     %CREATE-I-EXISTS, VMI$COMMON:[SYSTEST.PCA] already exists

       The PCA IVP has been moved to the SYS$TEST directory.  To run it after
       the installation enter @SYS$TEST:PCA$IVP.COM.

     %VMSINSTAL-I-RESTORE, Restoring product save set I ...
     %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.PCA].

     %CREATE-I-EXISTS, VMI$COMMON:[SYSHLP.EXAMPLES.PCA] already exists

             ***************************************************************
             *                                                             *
             * If this installation is performed on a cluster, you must    *
             * execute                                                     *
             *                                                             *
             *    $ @SYS$STARTUP:PCA$STARTUP.COM                           *
             *                                                             *
             * on all other nodes in the cluster.  In addition, you must   *
             * add the above line to your system startup procedure.        *
             *                                                             *
             ***************************************************************

     %DECSET-I-DONEPCA, The installation of PCA V4.9 completed

     %DECSET-I-START_SCA, SCA V4.9 installation in progress

     %VMSINSTAL-I-RESTORE, Restoring product save set J ...
     %VMSINSTAL-I-SYSDIR, This product creates system disk directory  VMI$ROOT:[SYSTEST.SCA$IVP].
     %CREATE-I-EXISTS, VMI$ROOT:[SYSTEST.SCA$IVP] already exists
     %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.SCA].
     %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.SCA.EXAMPLE].
     %VMSINSTAL-I-SYSDIR, This product creates system directory [SYSHLP.EXAMPLES.SCA.2167A].

             ***************************************************************
             *                                                             *
             * If this installation is performed on a cluster, you must    *
             * execute                                                     *
             *                                                             *
             *    $ @SYS$STARTUP:SCA$STARTUP.COM                           *
             *                                                             *
             * on all other nodes in the cluster.  In addition, you must   *
             * add the above line to your system startup procedure.        *
             *                                                             *
             ***************************************************************

     A-36 Sample Installation Procedures

 



                                          Sample Installation Procedures
                           A.2 Sample Upgrade on an OpenVMS Alpha System

        %DECSET-I-EXISTS, SCA$DEFAULT account already exists
        %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named SCA$DEFAULT.
        %UAF-I-MDFYMSG, user record(s) updated
        %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named SCA$DEFAULT.
        %UAF-I-MDFYMSG, user record(s) updated
        %VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[SCA$DEFAULT].
        %CREATE-I-EXISTS, SYS$SYSDEVICE:[SCA$DEFAULT] already exists
        %DECSET-I-MODACC, Modifying account SCA$DEFAULT quotas...
        %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named SCA$DEFAULT.
        %UAF-I-MDFYMSG, user record(s) updated
        %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named SCA$DEFAULT.
        %UAF-I-MDFYMSG, user record(s) updated
        %DECSET-I-EXISTS, SCA$SERVER account already exists
        %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named SCA$SERVER.
        %UAF-I-MDFYMSG, user record(s) updated
        %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named SCA$SERVER.
        %UAF-I-MDFYMSG, user record(s) updated
        %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[SCA$SERVER].
        %CREATE-I-EXISTS, SYS$SYSDEVICE:[SCA$SERVER] already exists
        %DCL-S-SPAWNED, process JONES_1 spawned
        %DCL-S-ATTACHED, terminal now attached to process JONES_1
             Configuration last run by SMITH on 31-DEC-2004 15:14:39.86
        %NET$CONFIGURE-I-USECOMMON, using cluster common APPLICATION script
        %NET$CONFIGURE-I-USECOMMON, using cluster common EVENT script
        %NET$CONFIGURE-I-USECOMMON, using cluster common MOP_CLIENT script
        %NET$CONFIGURE-I-MODCHECKSUM, checksumming NCL management scripts modified by
        NET$CONFIGURE
        %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration completed

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

             If an SCA server is currently running, you may get a message indicating
             that a command failed.  This message is displayed for informational
             purposes only and does not indicate that a problem exists; therefore,
             the message may be ignored.

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

             Configuration last run by JONES on 31-DEC-2004 15:43:40.79
        %NET$CONFIGURE-I-MAKEACCOUNT, this procedure creates user account SCA$SERVER
        $NCL @SYS$COMMON:[SYSMGR]NET$APPLICATION_STARTUP.NCL-TEMP;

        Node 0 Session Control Application SCA
        at 2004-12-31-15:43:56.500-04:00Iinf

                                     Sample Installation Procedures A-37

 



     Sample Installation Procedures
     A.2 Sample Upgrade on an OpenVMS Alpha System

     command failed due to:
      process failure

     Identifier already exists

     Node 0 Session Control Application SCA
     at 2004-12-31-15:43:57.070-04:00Iinf

     Characteristics

         Addresses                         =
            {
               name = SCA$SERVER
            }
         Client                            = <Default value>
         Incoming Alias                    = True
         Incoming Proxy                    = False
         Outgoing Alias                    = False
         Outgoing Proxy                    = False
         Node Synonym                      = True
         Image Name                        = SYS$SYSTEM:SCA$SERVER_
     LOGIN.COM
         User Name                         = "SCA$SERVER"
         Incoming OSI TSEL                 = <Default value>

     $vef = F$verify(vef)
     %NET$CONFIGURE-I-MODCHECKSUM, checksumming NCL management scripts modified by
     NET$CONFIGURE
     %NET$CONFIGURE-I-CONFIGCOMPLETED, DECnet-Plus for OpenVMS configuration completed
     %DCL-S-RETURNED, control returned to process JONES
     %DECSET-I-MODACC, Modifying account SCA$SERVER quotas...
     %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named SCA$SERVER.
     %UAF-I-MDFYMSG, user record(s) updated
     %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named SCA$SERVER.
     %UAF-I-MDFYMSG, user record(s) updated

     %DECSET-I-DONESCA, The installation of SCA V4.9 completed

     DECset Cookbook installation in progress...






     A-38 Sample Installation Procedures

 



                                          Sample Installation Procedures
                           A.2 Sample Upgrade on an OpenVMS Alpha System

        %VMSINSTAL-I-SYSDIR, This product creates system disk directory VMI$ROOT:[SYSHLP.EXAMPLES.DECSET].
        %CREATE-I-EXISTS, VMI$ROOT:[SYSHLP.EXAMPLES.DECSET] already exists
        %VMSINSTAL-I-RESTORE, Restoring product save set K...
        %VMSINSTAL-W-NOFILE, New file DECSET_COOKBOOK_001.HTML does not exist.
        %VMSINSTAL-W-NOFILE, New file DECSET_COOKBOOK_002.HTML does not exist.
        %VMSINSTAL-W-NOFILE, New file DECSET_COOKBOOK_003.HTML does not exist.
        %VMSINSTAL-W-NOFILE, New file DECSET_COOKBOOK_004.HTML does not exist.
        %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...

            *********************************************************************
              The DECset collective installation will now run the Installation
              Verification Procedure for each of the components you selected to
              run the IVP.
            *********************************************************************

             +------------------------------------------------------------+
             |         Installation verification command procedure for    |
             |                  DECset Environment Manager                |
             +------------------------------------------------------------+

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

          Copyright 2005 Hewlett-Packard Development Company, L.P.

         Confidential computer software.  Valid license from HP required for
         possession, use, or copying.  Consistent with FAR 12.211 and 12.212,
         Commercial Computer Software, Computer Software Documentation, and
         Technical Data for Commercial Items are licensed to the U.S. Government
         under vendor's standard commercial license.

         Intel and Itanium are trademarks or registered trademarks of Intel
         Corporation or its subsidiaries in the United States and other countries.

         Microsoft, Windows, and Windows NT are U.S. registered trademarks
         of Microsoft Corporation.

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

        %ENVMGR-I-BEGINIVP, Beginning DECset Environment Manager V1.7 IVP.

        %ENVMGR-I-ENDIVP, DECset Environment Manager V1.7 IVP SUCCESSFUL.

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

          Copyright 2005 Hewlett-Packard Development Company, L.P.

                                     Sample Installation Procedures A-39

 



     Sample Installation Procedures
     A.2 Sample Upgrade on an OpenVMS Alpha System

      Confidential computer software.  Valid license from HP required for
      possession, use, or copying.  Consistent with FAR 12.211 and 12.212,
      Commercial Computer Software, Computer Software Documentation, and
      Technical Data for Commercial Items are licensed to the U.S. Government
      under vendor's standard commercial license.

      Intel and Itanium are trademarks or registered trademarks of Intel
      Corporation or its subsidiaries in the United States and other countries.

      Microsoft, Windows, and Windows NT are U.S. registered trademarks
      of Microsoft Corporation.

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

     %CMS-I-IVPBEGIN, Begin CMS V4.4 Installation Verification Procedure
     %CMS-S-CREATED, CMS Library $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
     TEST] created
     %CMS-I-LIBIS, library is $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
     TEST]
     %CMS-S-LIBSET, library set
     %CMS-I-LIBIS, library is $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
     TEST]
     %CMS-S-LIBSET, library set
     -CMS-I-SUPERSEDE, library list superseded
     %CMS-S-CREATED, element $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
     TEST]CMS$IVP_TEST.FILE created
     %CMS-S-RESERVED, generation 1 of element $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
     TEST]
     CMS$IVP_TEST.FILE reserved

     Reservations in CMS Library $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
     TEST]

     CMS$IVP_TEST.FILE
         (1)   JONES     1      31-DEC-2004 15:47:49 ""
     %CMS-S-GENCREATED, generation 2 of element $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_









     A-40 Sample Installation Procedures

 



                                          Sample Installation Procedures
                           A.2 Sample Upgrade on an OpenVMS Alpha System

        TEST]
        CMS$IVP_TEST.FILE created
        -CMS-I-NOCHANGES, no changes
        %CMS-I-VERCLS, class list verified
        %CMS-I-VERCMD, command list verified
        %CMS-I-VERELE, element list verified
        %CMS-I-VERGRP, group list verified
        %CMS-I-VERRES, reservation list verified
        %CMS-I-VERFRE, internal free space list verified
        %CMS-I-VERFRE, internal free space list verified
        %CMS-I-VERFRE, internal free space list verified
        %CMS-I-VERFRE, internal free space list verified
        %CMS-I-VERFRE, internal free space list verified
        %CMS-I-VERFRE, internal free space list verified
        %CMS-I-VERFRE, internal free space list verified
        %CMS-I-VERARC, archive control block verified
        %CMS-I-VER2, internal contiguous space verified
        %CMS-I-VERCON, control file verified
        %CMS-I-VEREDF, element $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
        TEST]CMS$IVP_TEST.FILE verified
        %CMS-I-VEREDFS, element data files verified
        %CMS-S-VERIFIED, library $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
        TEST] verified
        %CMS-S-FETCHED, generation 1 of element $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
        TEST]
        CMS$IVP_TEST.FILE fetched
        %CMS-I-FILEXISTS, file already exists, $2$DKA300:[SYS0.SYSUPD.DECSET127]CMS$IVP_
        TEST.FILE;2 created
        %CMS-S-FETCHED, generation 2 of element $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
        TEST]
        CMS$IVP_TEST.FILE fetched
        %CMS-S-IDENTICAL, files are identical
        %CMS-S-CREATED, class $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
        TEST]CL1 created
        %CMS-S-GENINSERTED, generation 1 of element $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
        TEST]
        CMS$IVP_TEST.FILE inserted into class $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
        TEST]CL1
        %CMS-S-CREATED, class $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
        TEST]CL2 created
        %CMS-S-GENINSERTED, generation 2 of element $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
        TEST]
        CMS$IVP_TEST.FILE inserted into class $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_


                                     Sample Installation Procedures A-41

 



     Sample Installation Procedures
     A.2 Sample Upgrade on an OpenVMS Alpha System

     TEST]CL2
     %CMS-S-FETCHED, generation 2 of element $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
     TEST]
     CMS$IVP_TEST.FILE fetched

     Elements in CMS Library $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
     TEST]

     CMS$IVP_TEST.FILE ""

     Element generations in CMS Library
             $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]

     CMS$IVP_TEST.FILE
       2     31-DEC-2004 15:47:50 JONES ""
       1     31-DEC-2004 15:47:48 JONES ""

     Classes in CMS Library $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
     TEST]

     CL1             "Test1"
     CL2             "Test2"

     Element generations in CMS Library
     $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]

     CMS$IVP_TEST.FILE/2
     %CMS-S-GENREMOVED, generation 2 of element $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
     TEST]
     CMS$IVP_TEST.FILE removed from class $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
     TEST]CL2
     %CMS-S-DELETED, class $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
     TEST]CL2 deleted
     %CMS-S-GENREMOVED, generation 1 of element $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
     TEST]
     CMS$IVP_TEST.FILE removed from class $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
     TEST]CL1
     %CMS-S-DELETED, class $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
     TEST]CL1 deleted
     %CMS-S-CREATED, group $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
     TEST]GR1 created
     %CMS-S-CREATED, group $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
     TEST]GR2 created
     %CMS-S-INSERTED, group $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
     TEST]GR1 inserted into group
     $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]GR2
     %CMS-S-REMOVED, group $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_

     A-42 Sample Installation Procedures

 



                                          Sample Installation Procedures
                           A.2 Sample Upgrade on an OpenVMS Alpha System

        TEST]GR1 removed from group
        $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_TEST]GR2
        %CMS-S-MODIFIED, group $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
        TEST]GR1 modified

        Groups in CMS Library $2$DKA300:[SYS0.SYSCOMMON.SYSTEST.CMS$IVP_
        TEST]

        GR2                 GR3

        %CMS-S-IVPSUCCESS, CMS V4.4 IVP completed successfully
        %CMS-I-IVPEND, End Installation Verification Procedure

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

          Copyright 2005 Hewlett-Packard Development Company, L.P.

         Confidential computer software.  Valid license from HP required for
         possession, use, or copying.  Consistent with FAR 12.211 and 12.212,
         Commercial Computer Software, Computer Software Documentation, and
         Technical Data for Commercial Items are licensed to the U.S. Government
         under vendor's standard commercial license.

         Intel and Itanium are trademarks or registered trademarks of Intel
         Corporation or its subsidiaries in the United States and other countries.

         Microsoft, Windows, and Windows NT are U.S. registered trademarks
         of Microsoft Corporation.

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

        %DTM-I-BEGINIVP, Beginning Digital Test Manager V4.3 IVP.
        %DTM-S-CREATED, Digital Test Manager library $2$DKA300:[SYS0.SYSUPD.DECSET127.DTMTEST] created
        %DTM-S-LIBIS, Digital Test Manager library is $2$DKA300:[SYS0.SYSUPD.DECSET127.DTMTEST]
        %DTM-I-DEFAULTED, benchmark file name defaulted to TESTX.BMK
        %DTM-S-CREATED, test description TESTX created
        %DTM-S-MODIFIED, test description TESTX modified
        %DTM-I-DEFAULTED, benchmark file name defaulted to DECWX.BMK
        %DTM-I-DEFAULTED, template file name defaulted to DECWX.SESSION
        %DTM-S-CREATED, test description DECWX created

        Test Descriptions in Digital Test Manager Library
        $2$DKA300:[SYS0.SYSUPD.DECSET127.DTMTEST]

        DECWX           "decwindows test"
            Template        = DECWX.SESSION
            Benchmark       = DECWX.BMK
            Prologue        = None Specified
            Epilogue        = None Specified

                                     Sample Installation Procedures A-43

 



     Sample Installation Procedures
     A.2 Sample Upgrade on an OpenVMS Alpha System

     TESTX           "first test"
         Template        = DTM$IVP.COM
         Benchmark       = DTM$IVP.COM
         Prologue        = None Specified
         Epilogue        = None Specified
     %DTM-S-CREATED, symbol variable VAR1 created
     %DTM-S-MODIFIED, variable VAR1 modified

     Variables in Digital Test Manager Library $2$DKA300:[SYS0.SYSUPD.DECSET127.DTMTEST]

     VAR1            "first variable"
         Value = NEWVALUE
     %DTM-S-CREATED, group GROUP1 created

     Groups in Digital Test Manager Library $2$DKA300:[SYS0.SYSUPD.DECSET127.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

     Groups in Digital Test Manager Library $2$DKA300:[SYS0.SYSUPD.DECSET127.DTMTEST]

     GROUP1              GROUP2
     %DTM-S-CREATED, collection COLL1 created

     Collections in Digital Test Manager Library $2$DKA300:[SYS0.SYSUPD.DECSET127.DTMTEST]

     COLL1          1 test    31-DEC-2004 15:48:20
            Command: CREATE COLLECTION/NOVERIFY COLL1 TESTX "test collection"
            Status: not run














     A-44 Sample Installation Procedures

 



                                          Sample Installation Procedures
                           A.2 Sample Upgrade on an OpenVMS Alpha System

        %DTM-S-DELETED, collection COLL1 deleted
        %DTM-I-DELETED, test_description DECWX deleted
        %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 verified
        %DTM-I-VERTD, test description list verified
        %DTM-I-VERVAR, variables list verified
        %DTM-I-VERARC, archive list verified
        %DTM-I-VERHEAD, user header information verified
        %DTM-I-VERSPACE, contiguous space verified
        %DTM-I-VERCOLDIR, collection directory structure verified
        %DTM-S-VERIFIED, Digital Test Manager library $2$DKA300:[SYS0.SYSUPD.DECSET127.DTMTEST] verified
        %DTM-I-ENDIVP, Digital Test Manager V4.3 IVP SUCCESSFUL.

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

          Copyright 2005 Hewlett-Packard Development Company, L.P.

         Confidential computer software.  Valid license from HP required for
         possession, use, or copying.  Consistent with FAR 12.211 and 12.212,
         Commercial Computer Software, Computer Software Documentation, and
         Technical Data for Commercial Items are licensed to the U.S. Government
         under vendor's standard commercial license.

         Intel and Itanium are trademarks or registered trademarks of Intel
         Corporation or its subsidiaries in the United States and other countries.

         Microsoft, Windows, and Windows NT are U.S. registered trademarks
         of Microsoft Corporation.

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

        %LSE-I-BEGINIVP, Beginning Language-Sensitive Editor V5.0 IVP.

        36 lines written to file SYS$SYSROOT:[SYSMGR]LSE$IVP.LIS;1

        %LSE-I-ENDIVP, Language-Sensitive Editor V5.0 IVP SUCCESSFUL.

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

                                     Sample Installation Procedures A-45

 



     Sample Installation Procedures
     A.2 Sample Upgrade on an OpenVMS Alpha System

       Copyright 2005 Hewlett-Packard Development Company, L.P.

      Confidential computer software.  Valid license from HP required for
      possession, use, or copying.  Consistent with FAR 12.211 and 12.212,
      Commercial Computer Software, Computer Software Documentation, and
      Technical Data for Commercial Items are licensed to the U.S. Government
      under vendor's standard commercial license.

      Intel and Itanium are trademarks or registered trademarks of Intel
      Corporation or its subsidiaries in the United States and other countries.

      Microsoft, Windows, and Windows NT are U.S. registered trademarks
      of Microsoft Corporation.

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

     %MMS-I-BEGINIVP, Beginning Module Management System V3.7 IVP.
     %MMS-I-ENDIVP, Module Management System  V3.7 IVP SUCCESSFUL.

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

       Copyright 2005 Hewlett-Packard Development Company, L.P.

      Confidential computer software.  Valid license from HP required for
      possession, use, or copying.  Consistent with FAR 12.211 and 12.212,
      Commercial Computer Software, Computer Software Documentation, and
      Technical Data for Commercial Items are licensed to the U.S. Government
      under vendor's standard commercial license.

      Intel and Itanium are trademarks or registered trademarks of Intel
      Corporation or its subsidiaries in the United States and other countries.

      Microsoft, Windows, and Windows NT are U.S. registered trademarks
      of Microsoft Corporation.

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

     %PCA-I-BEGINIVP, Beginning PCA V4.9 IVP

         Saving previously defined PCA logical names...
         Linking IVP image file...
         Running Collector test...
         Running Analyzer test...
         Checking test results...

     %PCA-I-IVPPASS, PCA V4.9 IVP Successful

         Deleting temporary files...
         Restoring logical names...

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

     A-46 Sample Installation Procedures

 



                                          Sample Installation Procedures
                           A.2 Sample Upgrade on an OpenVMS Alpha System

          Copyright 2005 Hewlett-Packard Development Company, L.P.

         Confidential computer software.  Valid license from HP required for
         possession, use, or copying.  Consistent with FAR 12.211 and 12.212,
         Commercial Computer Software, Computer Software Documentation, and
         Technical Data for Commercial Items are licensed to the U.S. Government
         under vendor's standard commercial license.

         Intel and Itanium are trademarks or registered trademarks of Intel
         Corporation or its subsidiaries in the United States and other countries.

         Microsoft, Windows, and Windows NT are U.S. registered trademarks
         of Microsoft Corporation.

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

        %SCA-I-BEGINIVP, Beginning Source Code Analyzer V4.9 IVP.

        ****  Client testing complete  ****
        %SCA-I-CONNECTING, Requesting connection to 0::
        %SCA-S-LIB, your SCA Library is 0::SCA$EXAMPLE:
        %SCA-I-CONNECTING, Requesting connection to 0::
        ****  Server testing complete  ****

        %SCA-I-ENDIVP, Source Code Analyzer V4.9 IVP SUCCESSFUL.

         Installation Verification Procedure Summary
                *******************************************

         DECset Environment Manager V1.7  Passed
         Code Management System V4.4    Passed
         Digital Test Manager V4.3  Passed
         Language-Sensitive Editor V5.0  Passed
         Module Management System V3.7  Passed
         Performance and Coverage Analyzer V4.9 Passed
         Source Code Analyzer V4.9  Passed
         Installation of DECSET V12.7 completed at 15:57

            Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY

            Creating installation data file: VMI$ROOT:[SYSUPD]DECSET127.VMI_
        DATA

         VMSINSTAL procedure done at 15:57

                                     Sample Installation Procedures A-47

 









                                                                       B
        ________________________________________________________________

                                          Files Installed on Your System



              This appendix contains full listings of the files added
              or modified in the DECset installation. The files are
              grouped by logical names, Environment Manager files, and
              individual component files.

        B.1 Logical Names Defined on Your System

              The following logical names are defined by the component
              startup files:

              o  SCA_SORTSHR

              o  SCA$2167A

              o  PCA$EXAMPLES

              o  SCA$EXAMPLE

              o  SCA$ROOT

              o  LSE$EXAMPLE

              o  TPU$JOURNAL

              o  DTM$UFDEFINES

              The following logical names are defined on OpenVMS Alpha
              and OpenVMS I64 systems only:

              o  LSESHR_TV

              o  CMSSHR_TV

              o  SCA$SHARE_TV

                                      Files Installed on Your System B-1

 



     Files Installed on Your System
     B.2 ENVMGR Files Installed

     B.2 ENVMGR Files Installed

           The following table lists the files created or modified
           during the ENVMGR installation, where nnn represents the
           product version and update number (such as 017). These
           listings represent the files that are installed on OpenVMS
           Alpha and OpenVMS I64 systems. There might be slight
           differences in the sets of files installed on the OpenVMS
           VAX platform.

           __________________________________________________________
           Directory_____________ENVMGR_File_Name____________________

           DECW$DEFAULTS.USER    DECSET$ENVMGR.DAT
                                 DECSET$ENVMGR.UID

           SYS$STARTUP           DECSET$ENVMGR_STARTUP.COM

           SYS$SYSTEM            DECSET$ENVMGR.EXE
                                 DECSET$ENVMGRCCT.EXE
                                 DECSET$START_ENVMGR.EXE

           SYS$HELP              DECSET$ENVMGR.HLB
                                 ENVMGRnnn.RELEASE_NOTES
                                 ENVMGRnnn_RELEASE_NOTES.PS
                                 HELPLIB.HLB

           SYS$LIBRARY           DCLTABLES.EXE
                                 DECSET$ENVMGRCCTSHR.EXE
                                 DECSET$ENVMGRSHR.EXE

           SYS$TEST              ENVMGR$IVP.COM
                                 ENVMGR$SAMPLE.DECSET_CONTEXT
                                 ENVMGR$SAMPLE.DECSET_CONTEXT_DB

           VUE$LIBRARY.USER______DECSET$MENU.VUE$DAT_________________

     B.3 CMS Files Installed

           The following table lists the files created or modified
           during the CMS installation, where nnn represents the
           product version and update number (such as 044).

           __________________________________________________________
           Directory_____________CMS_File_Name_______________________

           SYS$STARTUP           CMS$STARTUP.COM

     B-2 Files Installed on Your System

 



                                          Files Installed on Your System
                                                 B.3 CMS Files Installed

              __________________________________________________________
              Directory_____________CMS_File_Name_______________________

              SYS$SYSTEM            CMS$DW.EXE
                                    CMS.EXE

              SYS$MSG               CMSMSG.EXE

              SYS$SHARE             CMS$EVENT_ACTION.EXE
                                    CMSPROSHR.EXE
                                    CMSSHR.EXE
                                    CMSSHR.IIF

              SYS$LIBRARY           DCLTABLES.EXE

              VUE$LIBRARY           CMS$PROFILE.VUE$DAT
                                    CMS$VUE_STARTUP.COM

              SYS$HELP              CMS$DW_HELP.HLB
                                    CMSnnn.RELEASE_NOTES
                                    CMSnnn_RELEASE_NOTES.PS
                                    HELPLIB.HLB

              SYS$TEST              CMS$IVP.COM

              DECW$SYSTEM_DEFAULTS  CMS$DW.UID
                                    CMS$DW_DEFAULTS.DAT

              SYSHLP.EXAMPLES.CMS___CMS$ROUTINES.SDL____________________

        B.4 DTM Files Installed

              The following table lists the files created or modified
              during the DTM installation, where nnn represents the
              product version and update number (such as 043).

              __________________________________________________________
              Directory_____________DTM_File_Name_______________________

              SYS$STARTUP           DTM$STARTUP.COM

              SYS$SYSTEM            DTM.EXE
                                    DXDTMCOMPARE.EXE
                                    DXDTMPLAYREC.EXE
                                    DXDTMSCREDIT.EXE

                                      Files Installed on Your System B-3

 



     Files Installed on Your System
     B.4 DTM Files Installed

           __________________________________________________________
           Directory_____________DTM_File_Name_______________________

           SYS$LIBRARY           DCLTABLES.EXE
                                 DTM$DW_DEFAULTS.DAT
                                 DTM$DW.UID
                                 DTM$UFDEFINES.TPU
                                 DTM_MASK_TEMPLATE.DAT
                                 DTMPLAYREC.UID
                                 DTMSCREDIT.UID
                                 DTMSHR.EXE
                                 DXDTMPLAYREC.DAT

           VUE$LIBRARY           DTM$PROFILE.VUE$DAT
                                 VUE$DTM.COM

           SYS$HELP              DTM$DW_HELPLIB.HLB
                                 DTMnnn_RELEASE_NOTES.PS
                                 DTMnnn.RELEASE_NOTES
                                 DTMPLAYREC.HLB
                                 DTMSCREDIT.HLB
                                 HELPLIB.HLB

           SYS$TEST______________DTM$IVP.COM_________________________

     B.5 LSE Files Installed

           The following table lists the files created or modified
           during the LSE installation, where nnn represents the
           product version and update number (such as 050).

           __________________________________________________________
           Directory_____________LSE_File_Name_______________________

           SYS$STARTUP           LSE$STARTUP.COM

           SYS$SYSTEM            LSEDIT.EXE

           SYS$MESSAGE           LSEMSG.EXE






     B-4 Files Installed on Your System

 



                                          Files Installed on Your System
                                                 B.5 LSE Files Installed

              __________________________________________________________
              Directory_____________LSE_File_Name_______________________

              SYS$LIBRARY           DCLTABLES.EXE
                                    LSESHR.EXE
                                    LSE$CCTSHR.EXE
                                    LSE$DECWSHR.EXE
                                    LSE$DEFAULTS.DAT
                                    LSE$SYSTEM_ENVIRONMENT.ENV
                                    LSE$SECTION.TPU$SECTION
                                    LSE$WIDGETS.UID
                                    LSE$DEBUG.TPU
                                    PSE$COMMENTS.EXE

              VUE$LIBRARY.USER      LSE$EDIT_FILE.EXE
                                    LSE$EDIT_QUALIFIERS.EXE
                                    LSE$EDIT_OPTIONS.UID
                                    LSE$EDIT.COM
                                    LSE$PROFILE.VUE$DAT

              SYS$HELP              HELPLIB.HLB
                                    LSEnnn_RELEASE_NOTES.PS
                                    LSEnnn.RELEASE_NOTES
                                    LSE$HELP.HLB
                                    LSE$MENU.HLB
                                    LSE$KEYPAD.HLB
                                    LSE$CLIHELP.HLB

              SYS$TEST              LSE$IVP.COM

              SYS$TEST.LSE          LSE$IVP.TPU














                                      Files Installed on Your System B-5

 



     Files Installed on Your System
     B.5 LSE Files Installed

           __________________________________________________________
           Directory_____________LSE_File_Name_______________________











































     B-6 Files Installed on Your System

 



                                          Files Installed on Your System
                                                 B.5 LSE Files Installed

              __________________________________________________________
              Directory_____________LSE_File_Name_______________________

              SYSHLP.EXAMPLES.LSE   C-SEM-BEGIN-END.LSE
                                    C-SEM-COMMON.LSE
                                    C-SEM-INDENTED-BEGIN-END.LSE
                                    C-SEM-K-R.LSE
                                    CDU.LSE
                                    DCL.LSE
                                    EMACS_SEARCH.TPU
                                    EVE$CONSTANTS.UIL
                                    HELP.LSE
                                    LATEX.LSE
                                    LATEX_HELPLIB.HLB
                                    LSE$CONSTANTS.UIL
                                    LSE$DECWINDOWS.TPU
                                    LSE$EDIT_ICONS.UIL
                                    LSE$EDIT_OPTIONS.UIL
                                    LSE$EVE_ADVANCED.TPU
                                    LSE$EVE_CORE.TPU
                                    LSE$EVE_DECWINDOWS.TPU
                                    LSE$EVE_EDIT.TPU
                                    LSE$EVE_EDT.TPU
                                    LSE$EVE_EXTEND.TPU
                                    LSE$EVE_EXTRAS.TPU
                                    LSE$EVE_FILE.TPU
                                    LSE$EVE_FORMAT.TPU
                                    LSE$EVE_HELP.TPU
                                    LSE$EVE_MENUS.TPU
                                    LSE$EVE_MOUSE.TPU
                                    LSE$EVE_PARSER.TPU
                                    LSE$EVE_SHOW.TPU
                                    LSE$EVE_TERMINALS.TPU
                                    LSE$EVE_WINDOWS.TPU
                                    LSE$GRAMMAR.TPU
                                    LSE$GRAMMAR_ADJUSTMENT.TPU
                                    LSE$GRAMMAR_ALIAS.TPU
                                    LSE$GRAMMAR_LANGUAGE.TPU
                                    LSE$GRAMMAR_PLACEHOLDER.TPU
                                    LSE$GRAMMAR_TOKEN.TPU
                                    LSE$GRAMMAR_UTIL.TPU
                                    LSE$HIGHLIGHT.TPU
                                    LSE$INITIALIZE.TPU
                                    LSE$KEY.TPU
                                    LSE$MENUS.TPU
                                    LSE$METHOD.TPU

                                      Files Installed on Your System B-7

 



     Files Installed on Your System
     B.5 LSE Files Installed

           __________________________________________________________
           Directory_____________LSE_File_Name_______________________











































     B-8 Files Installed on Your System

 



                                          Files Installed on Your System
                                                 B.5 LSE Files Installed

              __________________________________________________________
              Directory_____________LSE_File_Name_______________________











































                                      Files Installed on Your System B-9

 



     Files Installed on Your System
     B.5 LSE Files Installed


           SYSHLP.EXAMPLES.LSE   LSE$MOUSE.TPU
           (Cont.)               LSE$MULTI_WINDOW.TPU
                                 LSE$PARSER.TPU
                                 LSE$PATTERNS.TPU
                                 LSE$PROMPT.TPU
                                 LSE$SHOW.TPU
                                 LSE$SHOW_LIST.TPU
                                 LSE$USER.DIA
                                 LSE$USER.EXAMPLE
                                 LSE$USER2.EXAMPLE
                                 LSE$USER3.EXAMPLE
                                 LSE$VMS_CMS.TPU
                                 LSE$VMS_HELP.TPU
                                 LSE$VMS_SCA.TPU
                                 LSE$WIDGETS.UIL
                                 MAKE.LSE
                                 MESSAGE.LSE
                                 MMS.LSE
                                 PACKAGE_SUPPORT.TPU
                                 PACK_HEADERS.TXT
                                 PACK_HEADERS_CLI.TPU
                                 PACK_HEADERS_PORT.TPU
                                 PERL.LSE
                                 RNF_DIFF.TPU
                                 RUNOFF.LSE
                                 SDL.LSE
                                 SHELL.LSE
                                 TABLE.LSE
                                 TEXT.LSE
                                 TPU.ENV
                                 TPU.LSE
                                 UNKNOWN.LSE
                                 XLSE_BUILD.COM
                                 XLSE_COMMANDS.TPU
                                 XLSE_COMMAND_HELP.HLP
                                 XLSE_COMMON.TPU
                                 XLSE_COMMON_KEYS.TPU
                                 XLSE_EDT.TPU
                                 XLSE_EDT_LK201_KEYS.TPU
                                 XLSE_EDT_VT100_KEYS.TPU
                                 XLSE_ENV.BUI
                                 XLSE_HELP.BUI
                                 XLSE_LK201_KEYS.TPU
     B-10 Files Installed on YourXSystemAD_ME.TXT
           ______________________XLSE_SECTION.BUI____________________

 



                                          Files Installed on Your System
                                                 B.6 MMS Files Installed

        B.6 MMS Files Installed

              The following table lists the files created or modified
              during the MMS installation, where nnn represents the
              product version and update number (such as 037).

              __________________________________________________________
              Directory_____________MMS_File_Name_______________________

              SYS$STARTUP           MMS$STARTUP.COM

              SYS$SYSTEM            MAKEMMS.EXE
                                    MMS.EXE

              SYS$LIBRARY           DCLTABLES.EXE
                                    MMS$DW.UID
                                    MMS$DW_DEFAULTS.DAT

              SYS$HELP              HELPLIB.HLB
                                    MMSnnn_RELEASE_NOTES.PS
                                    MMSnnn.RELEASE_NOTES
                                    MMS$DW_HELP.HLB

              SYS$TEST              MMS$IVP.COM

              SYSHLP.EXAMPLES.MMS   MMS$DEFAULT_RULES.MMS
                                    MMS$DEFAULT_SHELL_RULES.MMS

              VUE$LIBRARY.USER      MMS$PROFILE.VUE$DAT
              ______________________MMS$VUE.COM_________________________

        B.7 PCA Files Installed

              The following table lists the files created or modified
              during the PCA installation, where nnn represents the
              product version and update number (such as 049).

              __________________________________________________________
              Directory_____________PCA_File_Name_______________________

              SYS$STARTUP           PCA$STARTUP.COM

              SYS$SYSTEM            PCA$ANALYZER.EXE

              SYS$LIBRARY           DCLTABLES.EXE
                                    PCA$COLLECTOR.EXE

              VUE$LIBRARY.USER      PCA$PROFILE.VUE$DAT
                                    PCA$VUE.COM

                                     Files Installed on Your System B-11

 



     Files Installed on Your System
     B.7 PCA Files Installed

           __________________________________________________________
           Directory_____________PCA_File_Name_______________________

           SYS$HELP              HELPLIB.HLB
                                 PCAnnn_RELEASE_NOTES.PS
                                 PCAnnn.RELEASE_NOTES
                                 PCA$HELP.HLB
                                 PCAA_HELP.HLB
                                 PCAC_HELP.HLB

           SYS$TEST              PCA$IVP.COM

           SYS$TEST.PCA          PCA$IVP.OBJ
                                 PCA$IVPA.LOG
                                 PCA$IVPC.LOG
                                 PCA$KITVERSION.COM
                                 PCA$SYSTEM_BUILDDEFS.COM

           SYS$HELP.EXAMPLES.PCA ALPHA_DEMO_USER_ROUTINE.OPT
                                 DEMO_USER_ROUTINE.C
                                 DEMO_USER_ROUTINE.COM
                                 DEMO_USER_ROUTINE.OBJ
                                 PCA$8QUEENS.C
                                 PCA$8QUEENS.PAS
                                 PCA$8QUEENS.PCA
                                 PCA$8QUEENS.PCAA
                                 PCA$8QUEENS.PCAC
                                 PCA$8QUEENS_C.EXE
                                 PCA$8QUEENS_C.OBJ
                                 PCA$8QUEENS_PAS.EXE
                                 PCA$8QUEENS_PAS.OBJ
                                 PCA$PRIMES.EXE
                                 PCA$PRIMES.FOR
                                 PCA$PRIMES.OBJ
                                 PCA$PRIMES.PCAA
                                 PCA$PRIMES.PCAC
                                 PRIMESIN.DAT
                                 VAX_DEMO_USER_ROUTINE.OPT

           SYS$MESSAGE           PCA$MSG.EXE

           DECW$SYSTEM_DEFAULTS  PCAC.UID
                                 PCAA.UID

           DECW$DEFAULTS.USER    PCAC.DAT
           ______________________PCAA.DAT____________________________

     B-12 Files Installed on Your System

 



                                          Files Installed on Your System
                                                 B.8 SCA Files Installed

        B.8 SCA Files Installed

              The following table lists the files created or modified
              during the SCA installation, where nnn represents the
              product version and update number (such as 049).

              __________________________________________________________
              Directory_____________SCA_File_Name_______________________

              SYS$STARTUP           SCA$STARTUP.COM

              SYS$SYSTEM            SCA$MAIN.EXE
                                    SCA$DECW.EXE
                                    SCA$SERVER_LOGIN.COM
                                    SCA$SERVER_MAIN.EXE

              SYS$LIBRARY           DCLTABLES.EXE
                                    SCA$SHARE.EXE
                                    SCA$PRO_SHARE.EXE
                                    SCA$QUERY_CALLABLE.ADA
                                    SCA$QUERY_CALLABLE.BAS
                                    SCA$QUERY_CALLABLE.FOR
                                    SCA$QUERY_CALLABLE.H
                                    SCA$QUERY_CALLABLE.MAR
                                    SCA$QUERY_CALLABLE.PAS
                                    SCA$QUERY_CALLABLE.PLI
                                    SCA$QUERY_CALLABLE.R32
                                    SCA$QUERY_CALLABLE.SDI
                                    SCA$QUERY_CALLABLE.TPU
                                    SCA$REPORT_2167A_DESIGN.TPU
                                    SCA$REPORT_CUSTOMIZATIONS.TPU
                                    SCA$REPORT_FORMAT.TPU
                                    SCA$REPORT_FORMAT_DOCUMENT.TPU
                                    SCA$REPORT_FORMAT_RUNOFF.TPU
                                    SCA$REPORT_FORMAT_TEXT.TPU
                                    SCA$REPORT_GLOBALS.TPU
                                    SCA$REPORT_HELP.TPU
                                    SCA$REPORT_INTERNALS.TPU
                                    SCA$REPORT_OUTPUT.TPU
                                    SCA$REPORT_PACKAGE.TPU
                                    SCA$REPORT_PORTABLE_SYNTAX.TPU
                                    SCA$REPORT_UTILITIES.TPU
                                    SCA$REPORT_VALIDATE.TPU


                                     Files Installed on Your System B-13

 



     Files Installed on Your System
     B.8 SCA Files Installed

           __________________________________________________________
           Directory_____________SCA_File_Name_______________________

           SYS$MESSAGE           SCA$MESSAGES.EXE

           SYS$HELP              HELPLIB.HLB
                                 SCA$HELP.HLB
                                 SCA$NEUTRAL_HELP.HLB
                                 SCA$MENU.HLB
                                 SCAnnn.RELEASE_NOTES.PS
                                 SCAnnn.RELEASE_NOTES

           SYS$TEST              SCA$IVP.COM

           SYSTEST.SCA$IVP       SCA$IVP_TEST.COM
                                 SCA$IVP_TEST.LIS

           SYSHLP.EXAMPLES.SCA.  BUILDTABLE.ANA
           EXAMPLE               BUILDTABLE.C
                                 COPYFILE.ANA
                                 COPYFILE.C
                                 DESIGN_EXAMPLE.C
                                 DESIGN_EXAMPLE.ANA
                                 EXPANDSTRING.ANA
                                 EXPANDSTRING.C
                                 OPENFILES.H
                                 SCA$EVENT.DAT
                                 TRANSLIT.ANA
                                 TRANSLIT.C
                                 TYPE_EXAMPLE.C
                                 TYPE_EXAMPLE.H
                                 TYPE_EXAMPLE.ANA
                                 TYPES.H












     B-14 Files Installed on Your System

 



                                          Files Installed on Your System
                                                 B.8 SCA Files Installed

              __________________________________________________________
              Directory_____________SCA_File_Name_______________________

              SYSHLP.EXAMPLES.SCA.212167A_APPENDIX.SDML
                                    2167A_DATA.SDML
                                    2167A_DATA_FILES.SDML
                                    2167A_DESIGN.SDML
                                    2167A_FRONT.SDML
                                    2167A_NOTES.SDML
                                    2167A_PRELIMINARY.SDML
                                    2167A_PROFILE.RNO
                                    2167A_PROFILE.SDML
                                    2167A_REFERENCED.SDML
                                    2167A_REQUIREMENTS.SDML
                                    2167A_SCOPE.RNO
                                    2167A_SCOPE.SDML
                                    SCA$EVENT.DAT
                                    TR1_ADA.ADA
                                    TR1_ADA.ANA
                                    TR2_ADA.ADA
                                    TR2_ADA.ANA
                                    TR3_ADA_.ADA
                                    TR3_ADA_.ANA

              VUE$LIBRARY.USER      SCA$PROFILE.VUE$DAT
                                    SCA$VUE.COM

              DECW$DEFAULTS.USER    SCA.DAT
              ______________________SCA.UID_____________________________
















                                     Files Installed on Your System B-15

 









                                                                       C
        ________________________________________________________________

                                                  Recovering from Errors



              This appendix provides information to help you with
              failures or errors that might occur during product
              installation or product use.

        C.1 Failures During DECset Installation

              If VMSINSTAL detects any problems during the installation,
              it notifies you and asks if you want to continue the
              installation. In some instances, you can enter Yes to
              continue. To stop the installation process and correct the
              situation, enter No and press return. Correct the problem
              and restart the installation.

              If errors occur during the installation itself, or when
              the Installation Verification Procedure (IVP) is running,
              VMSINSTAL displays failure messages. If the installation
              fails, you see a message such as the following:

              %VMSINSTAL-E-INSFAIL, The installation of CMS V4.4 has failed.

              If the IVP fails during the installation, the IVP displays
              a message such as the following:

              %CMS-E-IVPFAILURE, CMS V4.4 IVP failed.

              %VMSINSTAL-E-IVPFAIL, The IVP for CMS V4.4 has failed.

              If you have installed the SCA Server on an OpenVMS
              Cluster, authorization problems might cause an SCA IVP
              failure, such as the following:

              **** Client testing complete ****
              %SCA-I-CONNECTING, Requesting connection to 0::
              %SCA-E-LINKLOST, link to 0:: has been disconnected
              -SYSTEM-F-INVLOGIN, login information invalid at remote node

                                              Recovering from Errors C-1

 



     Recovering from Errors
     C.1 Failures During DECset Installation

           This system message indicates that the DECset Server will
           not start. The most common cause is that the password in
           the network database and the system authorization file are
           not the same. To verify this, enable privileges and issue
           the following NCP command:

           NCP> SHOW OBJECT SCA$SERVER CHAR

           After the password is displayed, use it to attempt to log
           in to the SCA$SERVER account. You should fail and receive
           the following message:

               You are not authorized to login from this source

           If instead the password is wrong, the system displays the
           following failure message:

               User authorization failure

           See Section 8.6 for an explanation of why the password
           might be in error, and the actions to correct this
           situation.

           Errors can occur during the installation if any of the
           following conditions exist:

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

           o  Process quotas required by VMSINSTAL are incorrect (see
              Section 2.5).

           o  The OpenVMS help library is currently in use.

           o  The product license was registered incorrectly, or not
              registered and loaded.

           For descriptions of the error messages generated by these
           conditions, see the OpenVMS System Messages: Companion
           Guide for Help Message Users, your processor-specific
           installation and operations guide, or the OpenVMS License
           Management Utility Manual.

     C-2 Recovering from Errors

 



                                                  Recovering from Errors
                                 C.1 Failures During DECset Installation

              If you are notified that any of these conditions exist,
              you must take the appropriate action as described in the
              message. You might need to change a system parameter, or
              increase an authorized quota value.

              If the installation fails, you must restart the installa-
              tion procedure from Step 2 of the installation procedure,
              as described in Section 2.6.





































                                              Recovering from Errors C-3
                                             9agW4parHH֟"
~ݳ!RI/\$Y)a%EFX =3? (%"Mj_o '="4(%NG*DMRJq*J)q*Z)q)W,#-V+4D(4a|oQ0h7Fx(r(M)q+)J;4Y=
i(E7=H?Q$
^Q@\dJ	r8i"
qKh8BCjix"(f.L{D<!Q(aQcL;-&3;ֈ'E(wb\6Ib _Kq:"J1s.(e[wW$KH|D+%EW@gGi:"EQ*ag"́8,ʙ`ISF~*. 
y&J7^j}^cItu0|ypG/XV-f\+"9(M|صѕ/K/Bojpg.P|{}θ`WPwDi6Jbf8ebqYezwSⷒhljp[tgɦД3;t)F5Nsb $r 3"h g.0&o#={-B8{
2pٱ
%iz4G
%]~4ۏ6;6o-s]FDu4g=8h(GFddޣH?h808}|b!W]<mV7Ķ"+F?ڬ?JMъ@S.lNѤ?۳yH:2$4Qhj4QXhP6c|43w:GFNfs od:s6&=:s27F|6K4;5{hz]Z~ywKG4_9Y.ٜ˹E*7._zgCӅBR2ZÖwBv= <և9Q3[l}{hA kȬ}ʊAgl}Nc֗W0xغ~3[g1[c[fI	'YG+Wh:E|/toip]i]_wG_D+Whd,|"̃wǢwhaExy87G}Sp4Opy42&=it4FCQĲcp*=
4-چfFY`9ӣfC ?h@]PfVI"]mn@!ha3͏fFw2qAM-?sm^h%Z/Fgnh]vx
VsmaMG>pRRUǿk8D˃.Ѹu\Wq^Sa|4_MXR̈hu fjq@NdV_fU.%:6}\1!'4KS羉BppRc~4DrߋFmzM%&}h13`qVZtAa}=.(r_D
MK
;iI)k U=(PW<v;{wFzt(k+k6 lx#U[S8/<~HF;{4yjd4ryYdKNFSxn#.C$"Aibhh6l{Qp!=kr 
@J(,Ǩ"~^^1/q"C#pjҾ'FM=b`zĘ'bl#'mzj},FqQm s<q勿/1^1ĝ+~54FйS	 o
F<
Qл4aM'^ (|WyZ5㬰 X
)=b/Eu|+d._엱7OƨbԷ=WN4k:؍ Y1ȌR<΍)&'F1a_-H7FZ)nh1Wa3'(ZNrc$7F0GwS\")n7Nqc4)1In?+FMbhʽ,Mߌ1O2K.Q#{@0ƨI@K]R=ag"́u8T9tw+m9tZkAX*W;choE&b~w%e9+~_dA1JA^QlǨ
ϣMA~ صb?CjPBb,IEK*	y8aCkk]v},mucM$j6nP,PUܠH25-tRW!FCAETg9#@oȵ6{WAbqՈ+͉%Wk#GTtjX֦)0+]z5X^7֤Wb,G!ZAa!tN9GA"bmB
7!i6K:\77:yBAZ֩:o:fhtl3cٔYYu>	XoB_͉uQ/t:#MŒ\x:GE|::u&y[K.k:_l"$ٳ}#^p'jb;lz_g{̬Yh81H:ʣx!s+;Jy#p?CXZi*ۈ?rƢJR4YXȬ~Pb:2k\|Ml,YC
Q7	pC58d@8u8y>HgAu$apOz>Q0
)'N={Uq[g=YASz(h={Bb~iֳ'iqqf={|ҳ'ܓzvMN"UϞi9qJϞgg#F˞qPԈW8ÙԖ8e88zWh
:#Z^ڲG[Eq&||Ϗ-B
.PZ	;q*Eqf8]ks YK"uE4ߋҳTgǪզf=8]zvt_}]Bw{#a)Ncii{g7bi3qJfjq@Ndwű+=sń,+lil!>Bpf`li#H-ƹlgpgp
)ZaNiqj
{_9qӥ88F\1x'd]<O~~.\ON 1k/xCʹx7c.Fi຦{Pk	h>DZqpS<R׾j7;[}l-}Ϻœbb_xX?(WDbpi&b>cJ?(J/* 4$^)+žu
!COs<{ 8&x*!-^2q 3ͫ<&x~I<JxWxJx&V	=||`OUDb_xMO;S`z@1 J=C&śtFФ؟œZؓ8)k<8	6,iN7Fx!Q}GbR|=~qQK\P?!^)'+`Hu^t,"vXKyjX)Zoj#y9FaEስ11z
.k/1pux:cgXg|픾q*^5wZk75ￋF5Bu<3ѠYZ)MwPZwG?xk5L55ٟ@$ߟ]M顆ƴFѐ氳kzfqkZҊViWZ<5. )\qh+.0&,f)-	э)BVL'-AH]|{sv"@)%~`8E7A	Ħz{)	x(B8q}=#^qHssNNՉ	6Չ	e!	(reߘBM(@7cTHOp~A?G'MOѫP VL01	V'ȷs@$$۹y	7O'".܃;Hxh!;:J/J`
+UPU.I0*'*V':($O,nbm{;H=ܝbp8ଚ