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......................... 1-1 1.3 Accessing Online Documentation............... 1-2 1.4 Installation Procedure Requirements.......... 1-4 1.4.1 Privileges............................... 1-4 1.4.2 System Parameters and Disk Space......... 1-4 1.4.3 VMSINSTAL Requirements................... 1-5 1.4.4 Backing Up Your System Disk.............. 1-5 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. 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 Before you install any DECset components on the OpenVMS I64, OpenVMS Alpha or OpenVMS VAX platform, you must use the OpenVMS License Management Facility (LMF) to register the DECset software or component software licenses. Preparing to Install the DECset Components 1-1 Preparing to Install the DECset Components 1.2 License Registration 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.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. 1-2 Preparing to Install the DECset Components Preparing to Install the DECset Components 1.3 Accessing Online Documentation 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 Source Code Analyzer SYS$HELP:SCAnnn.RELEASE_NOTES Release Notes Performance and SYS$HELP:PCAnnn.RELEASE_NOTES Coverage Analyzer 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. __________________________________________________________ Online help also provides a pointer to the release notes file. After the installation, enter the following command line: Preparing to Install the DECset Components 1-3 Preparing to Install the DECset Components 1.3 Accessing Online Documentation $ HELP component RELEASE_NOTES In the previous command line, component represents the DECset component for which you want help, for example: $ HELP DECset RELEASE_NOTES 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.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 1-4 Preparing to Install the DECset Components Preparing to Install the DECset Components 1.4 Installation Procedure Requirements 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. 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. Preparing to Install the DECset Components 1-5 Preparing to Install the DECset Components 1.5 User Account Quotas and Privileges 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 $ 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 For more information, see the OpenVMS System Management Utilities Reference Manual. 1-6 Preparing to Install the DECset Components Preparing to Install the DECset Components 1.6 Standard System Maintenance Procedures 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 UAF> SHOW SYSTEM 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. 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: Preparing to Install the DECset Components 1-7 Preparing to Install the DECset Components 1.6 Standard System Maintenance Procedures $ INSTALL LIST/GLOBAL/SUMMARY 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 SYSGEN> USE CURRENT SYSGEN> SHOW GBLSECTIONS Parameter Name Current Default Minimum Maximum Unit Dynamic -------------- ------- ------- ------- -------- ---- ------- GBLSECTIONS 512 250 60 4095 Sections SYSGEN> EXIT 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. Section 1.6.3 describes the procedures for increasing these values using AUTOGEN. 1-8 Preparing to Install the DECset Components Preparing to Install the DECset Components 1.6 Standard System Maintenance Procedures 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 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]? 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 Password: $ SET DEFAULT SYS$UPDATE 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]: 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]: 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 %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 $ 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 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]? 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]? 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]? If you are installing CMS on an OpenVMS I64, 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]? 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]? 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 I64, 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. 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 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 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]? If you are installing DTM on an OpenVMS I64, 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]? 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]? 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 I64, 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. 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 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 $ 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 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]? If you are installing LSE on an OpenVMS I64, 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]? 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]? 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]? 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]? 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]? * Do you want to install language support for ADA95 [YES]? * Do you want to install language support for BASIC [YES]? * Do you want to install language support for BLISS [YES]? * Do you want to install language support for C [YES]? * Do you want to install language support for COBOL [YES]? * Do you want to install language support for CXX [YES]? * Do you want to install language support for FORTRAN [YES]? * Do you want to install language support for F90 [YES]? * Do you want to install language support for HTML [YES]? * Do you want to install language support for Java [YES]? 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]? * Do you want to install language support for PASCAL [YES]? * Do you want to install language support for PLI [YES]? * Do you want to install language support for LSE [YES]? * Do you want to install language support for PLSE [YES]? 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 I64, 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. 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 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. Installing the Language-Sensitive Editor for OpenVMS 5-7 Installing the Language-Sensitive Editor for OpenVMS 5.4 Installing LSE on an OpenVMS Cluster b. Run INSTALL, then enter the following command: INSTALL> REPLACE SYS$LIBRARY:DCLTABLES.EXE 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 $ 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 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]? If you are installing MMS on an OpenVMS I64, 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]? 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]? %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 I64, 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. 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 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