HP_ACMS_for_OpenVMS_________________________________ Installation Guide July 2006 This document provides information about installing the HP ACMS for OpenVMS, Version 5.0A software. Revision/Update Information: This manual supersedes the HP ACMS for OpenVMS Version 5.0 Installation Guide. Operating System: OpenVMS Alpha Version 8.2 or later OpenVMS I64 Version 8.2-1 or later Software Version: HP ACMS for OpenVMS, Version 5.0A Hewlett-Packard Company Palo Alto, California ________________________________________________________________ © Copyright 2006 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. Motif is a registered trademark of The Open Group. Oracle is a registered US trademark of Oracle Corporation, Redwood City, California. Oracle CODASYL DBMS, Oracle CDD/Administrator, Oracle CDD/Repository, Oracle Rdb, Oracle SQL/Services, Oracle Trace, and Oracle Trace Collector are registered US trademarks of Oracle Corporation, Redwood City, California. Printed in the US _________________________________________________________________ Contents Preface................................................... vii 1 Planning the ACMS Installation 1.1 Types of ACMS Kits............................ 1-1 1.2 ACMS Licenses................................. 1-2 1.3 Required Operating System Components.......... 1-3 1.4 Layered Product Requirements.................. 1-3 1.4.1 Determining Software Version Numbers...... 1-3 1.4.2 Requirements for Oracle CDD............... 1-4 1.4.3 Requirements for LSE...................... 1-5 1.4.4 Requirements for TP Desktop Connector..... 1-5 1.4.5 Recommended Order for Installing Software.................................. 1-5 1.5 Upgrading Software in a Distributed System.... 1-6 1.5.1 Configuration Issues...................... 1-6 1.6 Product Dependencies.......................... 1-7 2 Preparing to Install ACMS 2.1 Backing Up Your System Disk................... 2-1 2.2 Software Versions............................. 2-1 2.2.1 Installed Images.......................... 2-2 2.3 Privileges.................................... 2-3 2.4 Disk Space.................................... 2-3 2.4.1 Disk Space for a Normal Installation...... 2-3 2.4.2 Installing on a Disk with Limited Space... 2-5 2.5 Disk Quotas................................... 2-6 2.6 System Parameters............................. 2-6 2.6.1 Checking System Parameter Values.......... 2-8 2.6.2 Calculating the Values for GBLPAGES and GBLSECTIONS............................... 2-8 iii 2.6.3 Changing System Parameter Values with AUTOGEN................................... 2-9 2.6.4 Setting the CLISYMTBL Dynamic System Parameter................................. 2-9 2.7 Process Account Quotas........................ 2-10 2.8 Time Required for Installation................ 2-12 2.9 ACMS$IVP User Authorization................... 2-12 3 Installing ACMS 3.1 Installation Log.............................. 3-1 3.2 Installation Procedure........................ 3-1 3.2.1 Invoking VMSINSTAL (First Phase).......... 3-3 3.2.2 Product-Specific Questions (Second Phase).................................... 3-8 3.2.3 Informational Messages (Third Phase)...... 3-18 3.2.4 Running the Postinstallation Procedure (Fourth Phase)............................ 3-19 3.2.5 Running the Installation Verification Procedure (Fifth Phase)................... 3-22 3.2.6 Completing the Installation............... 3-23 3.3 Recovering from System and Installation Failures...................................... 3-23 3.3.1 System Failures........................... 3-24 3.3.2 ACMS Installation Failures................ 3-25 3.3.3 Recovering from Errors.................... 3-26 3.4 Accessing the Online Release Notes............ 3-26 3.5 Files Installed on Your System................ 3-26 4 After Installing ACMS 4.1 Executing the ACMS Postinstallation Procedure..................................... 4-1 4.2 Editing System Startup and Shutdown Procedures.................................... 4-2 4.2.1 Editing the System Startup Procedure...... 4-2 4.2.2 Installing ACMS Images as Resident on OpenVMS Alpha............................. 4-3 4.2.3 ACMSTART.COM Installs DECC$SHR and ACMS$TRACE_SHR.EXE........................ 4-4 4.2.4 Editing the System Shutdown Procedure..... 4-4 4.3 Editing ACMS_SETUP.COM........................ 4-5 4.3.1 Optional ACMS Logical Names............... 4-6 iv 4.3.2 Installing Application Development Shareable Images.......................... 4-7 4.3.3 ACMS System Management Commands........... 4-8 4.4 Modifying ACMS Parameters..................... 4-10 4.5 Authorizing Applications, Devices, Users, and Processes..................................... 4-11 4.5.1 Authorizing New Applications.............. 4-12 4.5.2 Authorizing New Terminals................. 4-12 4.5.3 Authorizing New Users..................... 4-13 4.5.4 Authorizing ACMS Processes................ 4-13 4.6 Creating and Modifying ACMS User Accounts..... 4-14 4.6.1 Privileges................................ 4-14 4.6.2 Quotas.................................... 4-14 4.7 Setting up ACMS on an OpenVMS Cluster System........................................ 4-16 4.8 Enabling Distributed ACMS Processing.......... 4-17 4.9 Rebuilding the LSE Environment................ 4-17 4.10 Installing ACMS Menu Form Files............... 4-17 4.11 Preparing Language-Specific ACMS Development Environments.................................. 4-17 4.11.1 BLISS Agents.............................. 4-18 4.11.2 Pascal Agents............................. 4-18 4.12 Determining and Reporting Problems............ 4-19 5 Running the ACMS IVP 5.1 Functions of the IVP.......................... 5-1 5.2 Running the IVP............................... 5-2 5.3 Errors Running the IVP........................ 5-3 5.4 Sample IVP Execution.......................... 5-4 6 Deinstalling ACMS 6.1 Starting the Deinstallation Procedure......... 6-1 6.2 Completing the Deinstallation................. 6-2 v A Sample Installations A.1 OpenVMS Alpha Development Kit Sample Installation.................................. A-1 A.2 OpenVMS I64 Development Kit Sample Installation.................................. A-14 B Registering and Loading Your ACMS License B.1 Sample ACMS License PAK....................... B-1 B.2 Using VMSLICENSE.COM.......................... B-2 B.3 Using LICENSE DCL Commands.................... B-3 C Modifying ACMS Help and Message Text D Creating Transaction Logs for HP DECdtm Services D.1 Prerequisites for Creating a Transaction Log........................................... D-1 D.2 Planning the Size and Location of Transaction Logs.......................................... D-2 D.2.1 Determining the Size of Transaction Logs...................................... D-2 D.2.2 Determining the Location for Transaction Logs...................................... D-3 D.3 Setting Up and Creating Transaction Logs...... D-4 D.3.1 Setting Up the Transaction Logs........... D-4 D.3.2 Creating the Transaction Logs............. D-5 D.4 Example of Setting Up and Creating Transaction Logs ......................................... D-5 Index Tables 1-1 ACMS Licenses............................. 1-2 1-2 Compatible Products Image Files for OpenVMS Alpha............................. 1-4 2-1 Privilege Requirements.................... 2-3 2-2 Disk Space Requirements for OpenVMS Alpha by Kit.................................... 2-3 vi 2-3 Disk Space Requirements for OpenVMS I64 by Kit....................................... 2-4 2-4 Disk Space Requirements for OpenVMS Alpha by Component.............................. 2-4 2-5 Disk Space Requirements for OpenVMS I64 by Component................................. 2-4 2-6 Required System Parameter Values for OpenVMS Alpha............................. 2-7 2-7 Process Account Quotas.................... 2-11 2-8 Timetable for Installing ACMS............. 2-12 3-1 ACMS-Related Files Checked For in System Roots..................................... 3-15 4-1 Optional ACMS Logical Names............... 4-6 4-2 Global Sections and Pages Required for Shared Utility Images (Alpha)............. 4-8 4-3 User Account Quotas....................... 4-14 5-1 ACMS IVP Tests............................ 5-2 B-1 Product Authorization Key Fields.......... B-2 B-2 LICENSE LOAD Parameters and Qualifiers.... B-4 D-1 Transaction Log Requirements.............. D-5 vii _________________________________________________________________ Preface This installation guide describes how to install kits for the following HP ACMS for OpenVMS (ACMS) product packages: o ACMS Development System o ACMS Run-Time Option o ACMS Remote Access Option Intended Audience Read this manual if you are responsible for installing and maintaining software for ACMS. To perform the installation procedures described in this manual, you must have access to a privileged OpenVMS system manager's account and be familiar with the OpenVMS installation procedure, VMSINSTAL. Document Structure This manual has the following chapters and appendixes: Chapter 1 Describes ACMS kits and licenses, the recommended order for updating layered products used with ACMS, and special dependencies and considerations. Chapter 2 Explains how to prepare your system for installing ACMS. Chapter 3 Describes how to install the ACMS software and sample applications and run the Installation Verification Procedure (IVP). It also tells you how to recover from system and installation failures. vii Chapter 4 Describes postinstallation steps that prepare your OpenVMS system for running ACMS. Chapter 5 Describes how to run the ACMS IVP separately from the installation procedure. Chapter 6 Describes how to deinstall ACMS. Appendix A Contains a sample installation for each ACMS development kit. Appendix B Contains information on registering and loading your ACMS license. Appendix C Describes how to modify ACMS help and message text, for example, to translate them to a language other than English. Appendix D Describes considerations for creating HP DECdtm log files. viii Related Documents Consult the OpenVMS System Manager's Manual for information about installing or upgrading layered product software on the OpenVMS operating system. Three other manuals contain information about managing your ACMS system once it is installed: o HP ACMS for OpenVMS Managing Applications Explains how to start and stop the ACMS system, monitor system performance, and perform some tuning operations. This manual also discusses installing applications, and authorizing users, applications, and devices. o HP ACMS Version 5.0A for OpenVMS Release Notes Contains information about new features and current restrictions for ACMS. HP ACMS Version 5.0A for OpenVMS Release Notes are available to you on line. They are stored in the file SYS$HELP:ACMS050AA.RELEASE_NOTES during the ACMS installation procedure. The installation procedure allows you to print HP ACMS Version 5.0A for OpenVMS Release Notes at the start of the installation. o HP ACMS for OpenVMS Remote Systems Management Guide Describes how to install and use the Remote Manager (and Remote Manager web agent) to manage HP ACMS for OpenVMS software systems remotely. HP ACMS for OpenVMS Systems Interface Programming gives directions for building the BLISS library file and an environment file for Pascal agents. For additional information on the compatibility of other software products with this version of ACMS, refer to the HP ACMS for OpenVMS Software Product Description (SPD 82.40.xx). For additional information about the Open Systems Software Group (OSSG) products and services, access the following OpenVMS World Wide Web address: http://h71000.www7.hp.com/openvms ix Reader's Comments HP welcomes your comments on this manual. Print or edit the online form SYS$HELP:OPENVMSDOC_ COMMENTS.TXT and send us your comments by: Internet openvmsdoc@hp.com Mail Hewlett-Packard Company OSSG Documentation Group, ZKO3-4/U08 110 Spit Brook Rd. Nashua, NH 03062-2698 How To Order Additional Documentation Use the following World Wide Web address for information about how to order additional documentation: http://www.hp.com/go/openvms/doc To reach the OpenVMS documentation website, click the Documentation link. If you need help deciding which documentation best meets your needs, call 1-800-ATCOMPA. Conventions The following conventions are used in this manual: Ctrl/x A sequence such as Ctrl/x indicates that you must press and hold 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.) In the HTML version of this document, this convention appears as brackets rather than a box. x . 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 discussed. Monospace text Monospace type indicates code examples and interactive screen displays. In the C programming language, monospace type in text identifies the following elements: keywords, the names of independently compiled external functions and files, syntax summaries, and references to variables or identifiers introduced in an example. In the HTML version of this document, this text style may appear as italics. - 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. italic text Italic text indicates important information, complete titles of manuals, or variables. Variables include information that varies in system output (Internal error number), in command lines (/PRODUCER=name), and in command parameters in text (where dd represents the predefined code for the device type). xi UPPERCASE Uppercase text indicates the name of a routine, the name of a file, the name of a file protection code, or the abbreviation for a system privilege. In command format descriptions, lowercase text in angle brackets indicates a required clause or phrase. xii References to Products The ACMS documentation set to which this manual belongs often refers to certain products by abbreviated names: ___________________________________________________________ AbbreviatioProduct_________________________________________ ACMS HP ACMS for OpenVMS Alpha, and HP ACMS for OpenVMS I64 Ada HP Ada for OpenVMS Alpha Systems, and HP Ada for OpenVMS I64 Systems BASIC HP BASIC for OpenVMS C HP C for OpenVMS Alpha Systems, and HP C for OpenVMS I64 Systems CDD Oracle CDD/Administrator, and Oracle CDD/Repository COBOL HP COBOL for OpenVMS Alpha Systems, and HP COBOL for OpenVMS I64 Systems DATATRIEVE HP DATATRIEVE for OpenVMS Alpha, and HP DATATRIEVE for OpenVMS I64 DBMS Oracle CODASYL DBMS DECforms HP DECforms FORTRAN HP Fortran for OpenVMS Alpha Systems, and HP Fortran for OpenVMS I64 Systems OpenVMS The OpenVMS Alpha operating system, and the OpenVMS I64 operating system Pascal HP Pascal for OpenVMS Alpha, and HP Pascal for OpenVMS I64 Rdb Oracle Rdb SQL________The_SQL_interface_to_Oracle_Rdb_________________ ________________________ Note ________________________ The HP DECtrace product is the predecessor to the Oracle Trace product. Some information in the ACMS documentation, particularly in some examples, refers to HP DECtrace. Except where version specific, the information applies to the Oracle Trace product as well and, as you read the information, you can use the xiii product name Oracle Trace instead of the product name HP DECtrace with no significant difference in meaning. ______________________________________________________ xiv 1 _________________________________________________________________ Planning the ACMS Installation This chapter describes the available ACMS kits. It also discusses the dependencies among ACMS Version 5.0A, the OpenVMS operating system, and other layered products, and considerations for upgrading and using these products in a distributed environment. The Part List, found in the transparent plastic envelope in your kit, specifies the number and contents of your media. Be sure to verify the contents of your kit with this information. If your kit is damaged or if you find that parts of it are missing, contact your HP representative. 1.1 Types of ACMS Kits ACMS is available in three different kits: o ACMS Development Kit This kit provides all the features of ACMS. You can define, build, and debug multiple-step tasks, task groups, menus and applications, as well as use the ACMS task queuing facilities. You can use HP DECforms or TDMS as standard presentation services, or use the Request Interface (RI) and Systems Interface (SI) to access other presentation services. You are provided with samples of ACMS applications using standard presentation services and the Request Interface. The development kit also includes the features provided by the run-time and remote-access kits. o ACMS Run-Time Kit This kit allows you to use existing applications or programs under the control of ACMS. It also allows you to define and debug menus, applications, task groups, and single-step tasks that use DCL servers, if Oracle CDD is present when this kit is installed. It Planning the ACMS Installation 1-1 Planning the ACMS Installation 1.1 Types of ACMS Kits allows ACMS users to sign in and select tasks that are implemented on the local node as well as remote nodes. The run-time kit allows you to use the ACMS Queued Task Initiator (QTI) to submit tasks to run on the local node as well as remote nodes. The run-time kit also includes the features provided by the remote-access kit. o ACMS Remote-Access Kit This kit is suitable for installation on a network node that does not have any ACMS applications running on it, but requires access to ACMS applications running on another network node. The remote-access kit allows users to sign in to ACMS and select tasks on remote nodes, and handles the terminal I/O associated with those tasks. The remote access kit allows you to use the ACMS QTI to submit tasks to run on remote nodes. 1.2 ACMS Licenses Each ACMS kit has an unlimited-use ACMS license associated with it. Table 1-1 shows the licenses that are applicable to each ACMS kit. Table_1-1_ACMS_Licenses____________________________________ Unlimited ACMS_Kit______________Use___________Concurrent_Use_________ Development System ACMS Not available Run-Time Option ACMS-RT ACMS-RT-USER Remote-Access_Option__ACMS-REM______ACMS-REM-USER__________ For more information about these ACMS licenses, refer to HP ACMS for OpenVMS Managing Applications. To install an ACMS Version 5.0A kit, you must register and load an ACMS software license, using the OpenVMS License Management Facility (LMF). You must register and load your ACMS license before you perform the installation. For more information on registering and loading your ACMS license, refer to Appendix B. 1-2 Planning the ACMS Installation Planning the ACMS Installation 1.3 Required Operating System Components 1.3 Required Operating System Components HP ACMS for OpenVMS Alpha Version 5.0A requires OpenVMS Alpha Version 8.2 or later. HP ACMS for OpenVMS I64 Version 5.0A requires OpenVMS I64 Version 8.2-1 or later. For distributed processing with ACMS, you must have DECnet software installed. 1.4 Layered Product Requirements The ACMS Version 5.0A installation procedure and IVP interact with a number of OpenVMS layered products. Some of these products are required, while others are optional. Each of these layered products has a minimum version (based on the OpenVMS version) that is supported with ACMS Version 5.0A. The ACMS Version 5.0A Software Product Description (SPD) identifies the minimum layered product versions required to successfully install ACMS Version 5.0A and run the IVP. If a product is required, you must make the minimum version available before you can install ACMS. If a product is not required, you do not need to make it available before installing ACMS, however, you must upgrade it to the minimum required version before using it with ACMS. 1.4.1 Determining Software Version Numbers Before installing ACMS Version 5.0A, identify the other products that you need to upgrade. The ACMS SPD contains a complete list of the products that are compatible with this version of ACMS, including information about the minimum version of OpenVMS and layered products that interact with ACMS Version 5.0A. To check the current version of the products, execute the DCL commands ANALYZE/IMAGE and SEARCH in the following formats: ANALYZE/IMAGE file-name /OUTPUT=ACMS_VERSION.TMP SEARCH ACMS_VERSION.TMP "image file id" Planning the ACMS Installation 1-3 Planning the ACMS Installation 1.4 Layered Product Requirements In the ANALYZE/IMAGE command, substitute for file-name the file name listed in Table 1-2 for each product. Table_1-2_Compatible_Products_Image_Files_for_OpenVMS_Alpha Product___________File_Name________________________________ HP DECforms SYS$LIBRARY:FORMS$MANAGER.EXE LSE (HP DECset) SYS$SYSTEM:LSEDIT.EXE Oracle CDD SYS$LIBRARY:CDDSHR.EXE Oracle CODASYL SYS$LIBRARY:DBMSHR.EXE DBMS Oracle Rdb SYS$LIBRARY:RDBSHR.EXE Oracle Trace SYS$LIBRARY:EPC$FUNCSHRP.EXE TP Desktop SYS$SYSTEM:ACMSDI$SERVER.EXE Connector__________________________________________________ The line that OpenVMS displays in response to the SEARCH command shows the current version of the product. The following example shows that the system has LSE Version 5.0 installed: $ ANALYZE/IMAGE SYS$SYSTEM:LSEDIT.EXE /OUTPUT=ACMS_VERSION.TMP $ SEARCH ACMS_VERSION.TMP "image file id" image file identification: "LSEDIT V5.0-0" 1.4.2 Requirements for Oracle CDD Oracle CDD/Repository Version 7.2 is supported by ACMS Version 5.0A. The following paragraphs discuss the requirements for Oracle CDD when installing the different ACMS kit types. If you are installing the ACMS development kit, at least the minimum version of CDD as identified in the ACMS SPD must be installed on your system. If CDD is not installed or if a lower version of CDD is installed, VMSINSTAL terminates the installation procedure. If you are installing the ACMS run-time kit, CDD is optional; however, the minimum version of CDD is required for the run-time kit to be fully functional. Specifically, if you install the ACMS run-time kit with CDD available, you can create new applications and menus and modify 1-4 Planning the ACMS Installation Planning the ACMS Installation 1.4 Layered Product Requirements existing applications and menus, on your ACMS run-time system. If you install the ACMS run-time kit without CDD available, you can use only existing applications and menus; you cannot create new ones on your run-time system. If you subsequently install CDD, you can make the ACMS run- time CDD-related features available by reinstalling the ACMS Version 5.0A run-time kit and choosing the CDD-related files option at the beginning of the installation. If you are installing the ACMS remote-access kit, CDD is not required. 1.4.3 Requirements for LSE LSE is an optional layered product for all ACMS kits. If the minimum version (or a higher, allowed version) of LSE as identified in the ACMS SPD is not available when you install ACMS, LSE templates for ACMS Version 5.0A are not provided on your system. If you subsequently install LSE, you can make the ACMS Version 5.0A LSE templates available by reinstalling the ACMS Version 5.0A kit and choosing the LSE update option at the beginning of the installation. 1.4.4 Requirements for TP Desktop Connector HP TP Desktop Connector for OpenVMS is an optional layered product for ACMS. If you are installing TP Desktop Connector on a system with ACMS Version 4.0 or higher, you must have at least the minimum version of the TP Desktop Connector as identified in the ACMS SPD. If the ACMS installation runs while TP Desktop Connector is running, the results are unpredictable. Use the following command to shut down TP Desktop Connector before you begin an installation of ACMS: $ @SYS$STARTUP:ACMSDI$SHUTDOWN.COM 1.4.5 Recommended Order for Installing Software To ensure problem-free installation of software on your system, install the OpenVMS operating system and layered products in the following order: 1. OpenVMS 2. LSE 3. Oracle Rdb Planning the ACMS Installation 1-5 Planning the ACMS Installation 1.4 Layered Product Requirements 4. Oracle Trace 5. Oracle CDD 6. Oracle CODASYL DBMS 7. HP DECforms 8. ACMS 9. TP Desktop Connector 1.5 Upgrading Software in a Distributed System Upgrading software in a distributed transaction processing system is complex because of the dependencies among the software products. The process becomes even more complex when you take into account the dependencies that are created from multiple versions that exist for each of the individual software products. Because you cannot upgrade all nodes in a distributed environment simultaneously, and because the upgrade process might last several days, a clear methodology is required to ensure smooth and timely introduction of new software versions. 1.5.1 Configuration Issues A simple, distributed configuration in a TP system consists of an ACMS front-end node and an ACMS back-end node. You can configure ACMS on each node for the processing of specific tasks. Likewise, the roles of the layered products on each node are distinct. For simple configurations, the upgrade process is straightforward: 1. Upgrade the software on the front-end nodes. 2. Upgrade the software on the back-end nodes. Upgrading in this order ensures that the system delivers the same version of software to the front-end node and the back-end node. However, this simple rule cannot be applied to a configuration in which a node is both a front end and a back end. To successfully upgrade a more complex configuration, apply these two key points: 1-6 Planning the ACMS Installation Planning the ACMS Installation 1.5 Upgrading Software in a Distributed System o A component built by a previous software version is compatible with the upgraded version of the software. For example, HP DECforms Version 1.4 can execute a form created by HP DECforms Version 1.3, without any modification. You can also copy this component from a node on which HP DECforms Version 1.3 is installed to a node with HP DECforms Version 1.4. The HP DECforms Version 1.3 form executes correctly, as long as you do not rebuild the form using Version 1.4. o Do not rebuild a component under the new software version until you upgrade all nodes to which it may possibly be shipped. To upgrade software in a distributed system, follow these steps: 1. Upgrade all software on the front-end-only nodes. 2. Upgrade all software on nodes that are both front-end and back-end nodes. 3. Upgrade all software on back-end-only nodes. ________________________ Note ________________________ Do not modify by recompilation any application components (unless required by the installation procedure) until you upgrade all the nodes that compose the distributed application. ______________________________________________________ 1.6 Product Dependencies Keep in mind the following dependencies when upgrading software, especially in a distributed environment: o ACMS ACMS copies HP DECforms forms (.FORM) and shareable images (.EXE), TDMS request library files (.RLB), and ACMS application database files (.ADB) from back-end to front-end nodes, if the versions or dates of the files on the back end are more recent. o Oracle CDD Planning the ACMS Installation 1-7 Planning the ACMS Installation 1.6 Product Dependencies CDD versions are interoperable in a distributed environment as long as features of the new version are not requested when using the previous version. CDD is not referenced in the run-time system by the layered products (except possibly by Rdb and DBMS, although this is not advised) except in the case of module recompilation. However, do not recompile or add features until the upgrade is complete. o HP DECforms See the HP DECforms SPD for HP DECforms dependencies. o OpenVMS Alpha operating system When upgrading major versions of the OpenVMS Alpha operating system, you must reinstall ACMS. This applies when upgrading the OpenVMS Alpha operating system from Version 6.x to Version 7.x. o Oracle CODASYL DBMS Remote access between different versions of Oracle CODASYL DBMS is possible as long as features unique to the newer version are not requested of a previous version. o Oracle Rdb Rdb modules are upwardly compatible; for example, modules compiled under Rdb Version 6.0 execute correctly if Rdb is upgraded to Version 7.0 on the system. Remote access between different versions of Rdb is possible as long as features unique to the newer version are not requested of the previous version. Because Rdb is the base data repository for many products, particularly CDD and Oracle Trace in a transaction processing system, you must convert all databases (RMU/CONVERT) used by these products after you upgrade Rdb. Refer to the product-specific information for more details. o Oracle Trace Oracle Trace depends on Oracle Rdb since it provides the base data repository, as mentioned above. Refer to the product-specific information for more details. 1-8 Planning the ACMS Installation 2 _________________________________________________________________ Preparing to Install ACMS This chapter discusses the preparations and requirements necessary for installing ACMS Version 5.0A. ACMS provides online release notes and gives you the option of printing or displaying the release notes during the installation procedure. HP strongly recommends that you read the release notes before proceeding with the installation in case they contain some important information regarding the installation procedure. The sections in this chapter describe requirements that are checked by the ACMS installation procedure. With the exception of optional layered products, your system must meet these requirements before you can install ACMS successfully. 2.1 Backing Up Your System Disk At the beginning of the installation, VMSINSTAL asks whether you have backed up your system disk. HP recommends that you back up your system disk before installing any software. Use the backup procedures that have been established at your site to do this backup. For details about performing a system disk backup, see the section on the Backup Utility in the OpenVMS documentation set. 2.2 Software Versions As discussed in Section 1.4, ACMS Version 5.0A requires minimum versions of a number of layered products. The installation procedure lists all layered products that do not meet or exceed the required minimum version. The ACMS Software Product Description (SPD) identifies the minimum software versions of required and optional products. Preparing to Install ACMS 2-1 Preparing to Install ACMS 2.2 Software Versions If any required products are below minimum version, the installation fails. 2.2.1 Installed Images In order to use other layered products during the installation of ACMS, certain executable images related to those products must be installed using the DCL command INSTALL. These images are normally installed by executing the startup procedure for the product. These startup procedures should be executed automatically when the system is started. Startup procedures are found in SYS$STARTUP. To determine whether an image is installed, execute the following DCL command: $ INSTALL LIST file-specification If an image is not installed, you must execute the related product startup procedure; also ensure that this startup procedure is executed automatically during system startup. If you are installing the ACMS development kit, the CDD image SYS$LIBRARY:CDDSHR.EXE must be installed. If you are installing the ACMS run-time kit, this is optional; however, if the image is not installed, CDD-related files will not be made available. The CDD startup procedure is CDDSTRTUP.COM. To use CDD, Rdb must also be available. Therefore, if you are installing the ACMS development kit, or if you plan to use the CDD-related function of the ACMS run-time kit, the Rdb image SYS$LIBRARY:RDBSHR.EXE must be installed. The Rdb startup procedure is RMONSTART.COM. If you have Oracle Trace installed on your system and you want the ACMS facility definition updated during the installation, the Oracle Trace image SYS$LIBRARY:EPC$FUNCSHRP.EXE must be installed. The Oracle Trace startup procedure is EPC$STARTUP.COM. 2-2 Preparing to Install ACMS Preparing to Install ACMS 2.3 Privileges 2.3 Privileges To install ACMS, you must be logged in to the SYSTEM account, or any account with similar privileges. The SYSTEM account has all the privileges required for the installation. Table 2-1 lists the privileges required to execute various steps of the installation. Table_2-1_Privilege_Requirements___________________________ Step____________________Required_Privileges________________ Installation procedure BYPASS Postinstallation BYPASS, SYSPRV, SYSNAM, CMEXEC, procedure OPER Installation OPER, SYSPRV, SYSNAM, CMKRNL Verification_Procedure_____________________________________ 2.4 Disk Space The following sections describe the approximate disk space requirements for a normal installation, and an option for installing ACMS on a system disk with limited space available. 2.4.1 Disk Space for a Normal Installation Installing ACMS requires a certain amount of free storage space during the installation. Once ACMS is installed, less storage space is required. Table 2-2 summarize the approximate storage requirements for ACMS during and after installation. These tables reflect the installation of full kits, with all options selected. Table_2-2_Disk_Space_Requirements_for_OpenVMS_Alpha_by_Kit_ Blocks During Blocks After Kit________________________Installation_____Installation___ Development 70,000 42,000 Run-time 48,000 33,000 Remote-access______________37,000___________29,000_________ Preparing to Install ACMS 2-3 Preparing to Install ACMS 2.4 Disk Space Table_2-3_Disk_Space_Requirements_for_OpenVMS_I64_by_Kit___ Blocks During Blocks After Kit________________________Installation_____Installation___ Development 110,000 80,000 Run-time 88,000 73,000 Remote-access______________67,000___________50,000_________ If you are installing only some parts of the ACMS kits, you need less disk space for the installation. Table 2-4 lists the approximate amount of space required for each optional component of the ACMS kits. Table 2-4 Disk Space Requirements for OpenVMS Alpha by __________Component________________________________________ Blocks During Blocks After Component__________________Installation_____Installation___ Development software[1] 35,000 23,000 Run-time software 27,000 16,000 Remote-access software 22,000 14,000 ACMS samples 3,300 1,500 ACMS Request Interface 6,000 3,900 samples CDD-related files 6,000 5,500 LSE-related files 6,200 600 [1]Includes_CDD-related_files______________________________ ___________________________________________________________ Table 2-5 Disk Space Requirements for OpenVMS I64 by __________Component________________________________________ Blocks During Blocks After Component__________________Installation_____Installation___ Development software[1] 75,000 53,000 [1]Includes_CDD-related_files______________________________ (continued on next page) 2-4 Preparing to Install ACMS Preparing to Install ACMS 2.4 Disk Space Table 2-5 (Cont.) Disk Space Requirements for OpenVMS I64 __________________by_Component_____________________________ Blocks During Blocks After Component__________________Installation_____Installation___ Run-time software 77,000 56,000 Remote-access software 62,000 44,000 ACMS samples 3,300 1,500 ACMS Request Interface 6,000 3,900 samples CDD-related files 6,000 5,500 LSE-related_files__________6,200____________600____________ To determine the number of free disk blocks on your system disk, enter the following command: $ SHOW DEVICE SYS$SYSDEVICE 2.4.2 Installing on a Disk with Limited Space If your system disk has less space than indicated in Section 2.4.1, and if you have previously installed ACMS on your system disk, you may be able to install ACMS Version 5.0A by using the VMSINSTAL Alternate Working Device (AWD) option. The AWD option allows you to specify another disk device on which VMSINSTAL creates its temporary working directory. For a normal HP ACMS for OpenVMS, Version 5.0A development kit installation, VMSINSTAL creates the following temporary working directory: SYS$SPECIFIC:[SYSUPD.ACMSDEVA_MAA050] For an AWD installation of the same kit, the VMSINSTAL temporary working directory is: alternate-working-device:[000000.ACMSDEVA_MAA050] The space required during installation indicated in Section 2.4.1 must be available on the alternate working device; this space will be available again after the installation is complete. You must still have at least 5000 blocks available on the system disk to use the AWD option. Preparing to Install ACMS 2-5 Preparing to Install ACMS 2.4 Disk Space ________________________ Note ________________________ The AWD installation assumes that the ACMS Version 5.0A is no more than 5000 blocks larger than the ACMS kit currently installed on your system. If the AWD installation does not work, you must make the required disk space available for a normal installation before installing ACMS. ______________________________________________________ To determine the number of free disk blocks on your system disk and alternate working device, execute the following commands: $ SHOW DEVICE SYS$SYSDEVICE $ SHOW DEVICE alternate-working-device 2.5 Disk Quotas If disk quotas are enabled on the system disk, the ACMS Installation Verification Procedure (IVP) fails. The ACMS installation procedure normally schedules the IVP to execute automatically after the installation is completed. However, if disk quotas are enabled, the installation procedure cancels the IVP and notifies you. You can choose to stop the installation and address the issue, or continue the installation and execute the IVP manually at a later time. To determine whether disk quotas are enabled, execute the following DCL command: $ SHOW QUOTA/DISK=SYS$SYSDEVICE 2.6 System Parameters Table 2-6 lists the minimum required system parameter values for the installation. Depending on the kinds of programs and applications running at your site, you might need higher values for some settings. 2-6 Preparing to Install ACMS Preparing to Install ACMS 2.6 System Parameters Table 2-6 Required System Parameter Values for OpenVMS __________Alpha____________________________________________ System_Parameter______Value________________________________ CLISYMTBL[1] 500 GBLPAGES[2] n + 6,000 GBLPAGFIL 2,048 GBLSECTIONS[2] n + 55 PQL_DASTLM[3] 20 PQL_DBIOLM[3] 12 PQL_DDIOLM[3] 20 PQL_MDIOLM[3] 20 VIRTUALPAGECNT 19,000 [1]The_CLISYMTBL_dynamic_system_parameter_must_be_set_to___ a minimum value of 500 during the installation. If the CLISYMTBL setting is set to a value less than 500, you must reset the value to 500 or more before installing ACMS. You can lower the setting to its original value once the installation is finished. [2]The n variable refers to the system parameter values that are currently in use. To install ACMS, the allocated system parameter value must be less than the sum of n plus the number indicated. The numbers indicated represent the unused portion of these parameters. (See Section 2.6.2.) [3]These dynamic system parameters must be set permanently to values equal to or greater than the values listed. Do not lower these values after the installation. ___________________________________________________________ The following sections describe how to check system parameter values, calculate values for the GBLPAGES and GBLSECTIONS system parameters, change parameter values with the OpenVMS AUTOGEN command procedure, and set the CLISYMTBL dynamic system parameter with the OpenVMS System Generation Utility (SYSGEN). Preparing to Install ACMS 2-7 Preparing to Install ACMS 2.6 System Parameters 2.6.1 Checking System Parameter Values To check the values of your system parameters, enter the following command at the DCL prompt to invoke SYSGEN: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> At the SYSGEN> prompt, enter the SHOW command to display the value of each system parameter. Make sure that the values displayed equal or exceed the value of each parameter listed in Table 2-6 . The following command displays the value for the VIRTUALPAGECNT system parameter: SYSGEN> SHOW VIRTUALPAGECNT Parameter Name Current Default Min. Max. Unit Dynamic -------------- ------- ------- ------ ------ ---- ------- VIRTUALPAGECNT 270144 9216 512 1200000 Pages This example shows that the current value for VIRTUALPAGECNT is 270144. After you finish checking the parameters with the SHOW command, enter the EXIT command at the SYSGEN> prompt to return to DCL level. 2.6.2 Calculating the Values for GBLPAGES and GBLSECTIONS To install and run ACMS, you must set the correct values for the GBLPAGES and GBLSECTIONS system parameters. The values for GBLPAGES and GBLSECTIONS in Table 2-6 (excluding the value of n) indicate the number of unused pages or sections you must have available on your system for the installation to process successfully. To calculate whether your system has a sufficient number of unused global pages and global sections, perform the following steps: 1. Show the current free global pages and global sections using the following DCL commands: $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES") 3420 $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS") 72 2-8 Preparing to Install ACMS Preparing to Install ACMS 2.6 System Parameters 2. Determine if the number of unused pages (3420 in the example) is equal to or greater than the number specified in Table 2-6 . If the number of unused pages is less than the number listed in the table, increase the allocation value for GBLPAGES. 3. Determine if the number of unused global sections (72 in the example) is equal to or greater than the number specified in Table 2-6 . If the value is less than the number required, increase the allocation value of the GBLSECTIONS parameter. Section 2.6.3 describes the procedures for increasing these values as well as those of other system parameters. Refer to the OpenVMS documentation on system management and operations for more information. 2.6.3 Changing System Parameter Values with AUTOGEN Use the AUTOGEN command procedure to change system parameters. To change system parameters with AUTOGEN, you must edit the following file: SYS$SYSTEM:MODPARAMS.DAT For example, to change the setting for the GBLPAGES system parameter, add this line to the file: GBLPAGES = 100000 Now, run the AUTOGEN procedure to recalculate your system parameters. Enter the following command at the DCL prompt: $@SYS$UPDATE:AUTOGEN SAVPARAMS SETPARAMS FEEDBACK For more information about using AUTOGEN, see the instructions on modifying system parameters in the OpenVMS documentation on system management and operations. 2.6.4 Setting the CLISYMTBL Dynamic System Parameter If the CLISYMTBL system parameter value for your system is less than 500, change the setting by entering the following series of commands: Preparing to Install ACMS 2-9 Preparing to Install ACMS 2.6 System Parameters $ RUN SYS$SYSTEM:SYSGEN SYSGEN> USE ACTIVE SYSGEN> SET CLISYMTBL 500 SYSGEN> WRITE ACTIVE SYSGEN> EXIT CLISYMTBL is a dynamic parameter, which means that you do not have to reboot the system to make the change take effect. The new value for CLISYMTBL becomes effective when you enter the SYSGEN command WRITE ACTIVE. If you do nothing further, the new value for CLISYMTBL remains in effect until the next time you reboot the system, at which time the old value for CLISYMTBL is restored. If you want to make the new CLISYMTBL value permanent, enter the following SYSGEN command: SYSGEN> WRITE CURRENT The WRITE CURRENT command writes the new value for CLISYMTBL into the SYSGEN database on disk, so that it is available when the system is rebooted. To exit from SYSGEN, enter the following command: SYSGEN> EXIT ________________________ Note ________________________ If you changed the value of CLISYMTBL, log out and log back in so that the new value can take effect. ______________________________________________________ 2.7 Process Account Quotas The account you use to install ACMS must have sufficient quotas to enable you to perform the installation. Table 2-7 summarizes the process quotas required to perform the installation. 2-10 Preparing to Install ACMS Preparing to Install ACMS 2.7 Process Account Quotas Table_2-7_Process_Account_Quotas___________________________ Account_Quota_________Required_Value_______________________ ASTLM 24 BIOLM 18 BYTLM 32,768 DIOLM 18 ENQLM 2,000 FILLM 200 PRCLM 10 PGFLQUO_______________12,800_______________________________ User account quotas are stored in the file SYSUAF.DAT. Use the OpenVMS Authorize Utility (AUTHORIZE) to verify and change user account quotas. First set your directory to SYS$SYSTEM and then run AUTHORIZE: $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> At the AUTHORIZE prompt (UAF>), enter the SHOW command with an account name to check a particular account. For example: UAF> SHOW SYSTEM To change a quota, enter the MODIFY command at the UAF> prompt. MODIFY has the following format: MODIFY account-name/quota-name=nnnn The following example changes the FILLM quota for the SYSTEM account and then exits from the Authorize Utility: UAF> MODIFY SYSTEM/FILLM=200 UAF> EXIT After you exit from the utility, the OpenVMS system displays messages indicating whether or not changes were made. Once the changes have been made, you must log out and log in again for the new quotas to take effect. For more information on modifying account quotas, see the description of the Authorize Utility in the OpenVMS documentation on system management and operations. Preparing to Install ACMS 2-11 Preparing to Install ACMS 2.8 Time Required for Installation 2.8 Time Required for Installation Table 2-8 lists the approximate time required for installing each ACMS kit. ________________________ Note ________________________ Installation time depends heavily on installation options, system load, hardware, and kit media. The times listed in Table 2-8 were measured for full installations on a standalone HP 3000 (Alpha) system with disk-resident kits. Your time may vary. ______________________________________________________ Table_2-8_Timetable_for_Installing_ACMS____________________ Installation Kit______________Time[1]__________IVP_Time_________________ Development 7 minutes 2 minutes Run-time 4 minutes 2 minutes Remote-access 2 minutes 1 minute [1]If_you_are_using_the_VMSINSTAL_option_AWD,_multiply_____ these times by 3. ___________________________________________________________ 2.9 ACMS$IVP User Authorization The ACMS installation checks for the presence of the OpenVMS user account ACMS$IVP. If this account does not exist, you are asked for information needed to create it. The ACMS$IVP account is used to run the ACMS Installation Verification Procedure. Among the information requested for this account is a unique user identification code (UIC) in the form [ggggg,nnnnnn], where ggggg is an octal user group number in the range 1-37776, and nnnnnn is an octal user number in the range 1-177776. Additionally, the group number cannot be a system group number. 2-12 Preparing to Install ACMS Preparing to Install ACMS 2.9 ACMS$IVP User Authorization Enter the following commands to list the UICs currently in use on your system: $ MCR AUTHORIZE UAF> LIST * /BRIEF The result of these commands is that all UICs in use on your system are listed in the file SYSUAF.LIS, in your default directory. You can then examine this listing to determine a unique UIC for the ACMS$IVP account. On your system, a certain range of group numbers has been reserved for system users. To determine this range, execute the following commands: $ MAXSYS = F$GETSYI("MAXSYSGROUP") $ SHOW SYMBOL MAXSYS The value you supply for the octal group number in the ACMS$IVP UIC must be greater than the octal value of the symbol MAXSYS. The following example shows that the maximum system group number is octal 10; therefore, you must specify a group number for the ACMS$IVP UIC that is in the range 11-37776: $ MAXSYS = F$GETSYI("MAXSYSGROUP") $ SHOW SYMBOL MAXSYS MAXSYS = 8 Hex = 00000008 Octal = 00000000010 Preparing to Install ACMS 2-13 3 _________________________________________________________________ Installing ACMS This chapter describes how to install the ACMS software. Section 3.2 contains a step-by-step description of the installation procedure. 3.1 Installation Log A log of your installation is kept in the following file: SYS$COMMON:[SYSUPD]ACMS050AA_INSTALLATION.LOG In particular, if the ACMS installation fails because prerequisites were not met, this log contains a list of those prerequisites. You can use it as a check list of items to address before you reinstall ACMS. In addition, after the installation is completed, a list of the files created by the installation is stored in the following file: SYS$COMMON:[SYSEXE]ACMS050AA_FILES.DAT 3.2 Installation Procedure ACMS provides online release notes. The prompt to display or print the release notes before the installation appears in the installation procedure, if you invoke VMSINSTAL with the OPTIONS N parameter. For information on accessing the release notes after the installation, refer to Section 3.4. The ACMS installation process is divided into five phases: o The first phase consists of invoking VMSINSTAL and supplying information such as which kit to install, where the kit resides, and other installation options. Section 3.2.1 explains the first phase. Installing ACMS 3-1 Installing ACMS 3.2 Installation Procedure o The second phase consists of a series of questions, checks, and informational messages related to ACMS. This phase ensures that the installation environment is sufficient to support the actual installation work that occurs in the third phase. The second phase ends when you are shown a summary of what happens in the third phase and are asked whether you want to continue. Chapter 2 has information to help you answer the questions asked in the second phase; if you have not read Chapter 2 in preparation for this installation, do so now. Section 3.2.2 takes you step by step through the second phase of the installation. o The third phase is the actual installation work. This usually includes restoring kit savesets, providing files to system directories, creating the ACMS$IVP user account, updating the LSE and Oracle Trace environments, updating DCL tables and help libraries, and other steps as enumerated at the end of the second phase. No user interaction is required during this phase. Section 3.2.3 explains the messages that you might see during this phase. o The fourth phase is the ACMS postinstallation procedure. This procedure, which executes automatically after the ACMS software is installed, performs the minimum system management operations that are necessary to allow ACMS to be used on the system. Section 3.2.4 guides you through the postinstallation phase. o The fifth phase is the ACMS Installation Verification Procedure (IVP). This procedure performs a series of exercises to ensure that ACMS is properly installed and usable on your system. Section 3.2.5 discusses the execution of the IVP. To abort the installation procedure at any time, press . When you press , the installation procedure deletes all files it has created up to that point and exits. You can then start the installation again. 3-2 Installing ACMS Installing ACMS 3.2 Installation Procedure 3.2.1 Invoking VMSINSTAL (First Phase) To start the installation, log in to the SYSTEM account, and set default to the SYS$UPDATE directory: Username: SYSTEM Password: $ SET DEFAULT SYS$UPDATE Next, invoke VMSINSTAL. Use the following syntax to invoke VMSINSTAL: @VMSINSTAL product-name device-name [OPTIONS option- 1[,...]] product-name The installation name for the component. Enter one of the following: o ACMSDEVA_MAA050 - if you are installing the Alpha development kit. o ACMSRTOA_MAA050 - if you are installing the Alpha run- time kit. o ACMSREMA_MAA050 - if you are installing the Alpha remote-access kit. o ACMSDEVI_MAA050 - if you are installing the I64 development kit. o ACMSRTOI_MAA050 - if you are installing the I64 run-time kit. o ACMSREMI_MAA050 - if you are installing the I64 remote- access kit. device-name The name of the device on which you plan to mount the media. For example, CDROM is the device name for a tape drive. OPTIONS An optional parameter indicating that one or more VMSINSTAL options are being supplied. This parameter is followed by a space, and then the requested options. If multiple options are requested, separate them with commas (,); do not include spaces in the options list. Installing ACMS 3-3 Installing ACMS 3.2 Installation Procedure The following are VMSINSTAL options that you can use for the ACMS installation: o N-The release notes option causes VMSINSTAL to prompt you to display or print the ACMS release notes during the installation. (Release notes are always copied to SYS$HELP during an installation, whether or not this option is specified.) o AWD-The alternate working device option allows you specify an alternate disk device on which to create the temporary working directory used by VMSINSTAL during a product installation. This option allows you to perform an installation with fewer free blocks on the system disk than are otherwise required. Specify the AWD option using the following format: AWD=device ________________________ Note ________________________ Use the AWD option only if you have previously installed ACMS and you do not have sufficient space on your system disk to perform a normal installation. If you have not previously installed ACMS, you must have the disk space listed in Table 2-2 available to accommodate the ACMS software. ______________________________________________________ See Section 2.4.2 for more information on using the AWD option. VMSINSTAL has several other options; for information, see the OpenVMS documentation on software installation. ________________________ Note ________________________ ACMS does not support option R, the alternate root option. ______________________________________________________ On Alpha, the following command invokes VMSINSTAL and installs ACMS from the CD-ROM reader. This example uses the N option for printing or displaying release notes, and the AWD option to use disk DISK1 as an alternate working device: 3-4 Installing ACMS Installing ACMS 3.2 Installation Procedure $ @SYS$UPDATE:VMSINSTAL ACMSDEVA_MAA050 CDROM OPTIONS N,AWD=DISK1 OpenVMS Software Product Installation Procedure V8.2 It is 16-JUN-2006 at 05:17. Enter a question mark (?) at any time for help. If you do not supply either the product name or the device name, VMSINSTAL prompts you for this information later on in the installation procedure. 1. System backup VMSINSTAL asks the following question to ensure that your system disk is properly backed up: * Are you satisfied with the backup of your system disk [YES]? Always back up your system disk before performing an installation. If you are satisfied with the backup of your system disk, press . Otherwise, answer NO to stop the installation. After you back up your system disk, you can restart the installation. Installing ACMS 3-5 Installing ACMS 3.2 Installation Procedure 2. Mounting the media VMSINSTAL instructs you to mount the ACMS Version 5.0A distribution media on the device you specified when you invoked VMSINSTAL. When you have mounted the media, answer YES to the question, "Are you ready?": Please mount the first volume of the set on CDROM. * Are you ready? Y If you entered the wrong device name when you invoked VMSINSTAL and need to restart the installation, answer NO in response to the question. To abort the installation for any other reason, press . VMSINSTAL then reads the media and begins the installation of ACMS. A message similar to the following appears: %MOUNT-I-MOUNTED, ACMSDEVA_MAA050 MOUNTED ON _$200$DISK1: The following products will be processed: ACMSDEVA_MAA V5.0 Beginning installation of ACMSDEVA_MAA 050 at 05:17 %VMSINSTAL-I-RESTORE, Restoring product saveset A... 3. Release notes If you specified OPTIONS N when you invoked VMSINSTAL, you are now given several options for reviewing the release notes. Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: If you select option 1, VMSINSTAL displays the release notes immediately. You can terminate the display at any time by pressing . Because the release notes are lengthy, it is recommended that you choose option 2 to 3-6 Installing ACMS Installing ACMS 3.2 Installation Procedure print the release notes rather than reviewing them on line. If you select option 2, VMSINSTAL prompts you for the name of the print queue that you want to use: * Queue name [SYS$PRINT]: You can enter a queue name or just press to send the file to the default output print queue SYS$PRINT. If you select option 3, VMSINSTAL displays the release notes immediately and then prompts you for a queue name for the printed version. If you select option 4, VMSINSTAL does not display or print the release notes. Use the DCL command TYPE or PRINT to view the release notes in the following file: SYS$HELP:ACMS050AA.RELEASE_NOTES The release notes are copied to the SYS$HELP directory under all circumstances, regardless of your choice from the menu. ________________________ Note ________________________ The release notes for each version of ACMS are uniquely named so that release notes from multiple versions can be maintained. To facilitate comparison of various versions of ACMS, HP recommends not deleting release notes for previous versions of ACMS. ______________________________________________________ 4. Continuing the installation The installation procedure now asks if you want to continue the installation. To continue, answer YES. Otherwise, press to stop the installation: * Do you want to continue the installation [N]?: Y %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. Installing ACMS 3-7 Installing ACMS 3.2 Installation Procedure After you read the release notes, you can restart the installation without being questioned about the release notes by removing OPTIONS N from the VMSINSTAL command. For example: $ @SYS$UPDATE:VMSINSTAL ACMSDEVA_MAA050 CDROM: 3.2.2 Product-Specific Questions (Second Phase) This section discusses the questions and messages that apply specifically to the installation of ACMS Version 5.0A. Depending on the kit and options that you choose, some of the steps listed here might not apply to your installation. This discussion assumes that you are installing the OpenVMS Alpha development kit (ACMSDEVA_ MAA050). See Appendix A for a sample installation of the ACMS OpenVMS Alpha development kit and of the ACMS OpenVMS I64 development kit. Each question in the installation is marked with an asterisk (*) at the beginning of the line. Some questions show the default response in brackets, for example, [YES]. To choose the default response, press . 1. Selecting installation options The product-specific installation procedure begins execution. The following message is displayed: The results of this installation are being logged in SYS$COMMON:[SYSUPD]ACMS050AA_INSTALLATION.LOG It will display the message ACMS Version 5.0A is supported on OpenVMS Alpha Version 8.2 and 8.3, OpenVMS I64 Version 8.2-1 and 8.3 Do you want to continue [yes] Press Return to select the default option and the installation proceeds Installing ACMS on OpenVMS V8.2 Installing ACMS V5.0A, development kit The procedure then asks what portions of the installation you want to perform. It lists the optional parts of the installation, and asks if you want to do the full installation. If you answer YES, the full installation is done; if you answer NO, you are asked 3-8 Installing ACMS Installing ACMS 3.2 Installation Procedure individually whether you want to perform each optional part of the installation. In this example, the full installation is selected: There are five optional parts to the ACMS development kit installation: o ACMS component software o ACMS LSE update o ACMS samples o ACMS Request Interface samples o ACMS WBEM related files The full installation includes all these parts. If ACMS component software is selected, the ACMS WBEM related files will also be copied. To install the ACMS samples or the ACMS Request Interface samples, you must install, or have previously installed, the ACMS component software. * Do you want the full ACMS installation [NO]?: Y 2. Checking installation prerequisites The installation now checks that all ACMS installation prerequisites are met. These prerequisites are discussed in Chapter 2. The following message is displayed: CHECKING INSTALLATION PREREQUISITES ----------------------------------- A message is also displayed for any prerequisites that are not met. For example, the following message indicates that the optional HP DECtrace software is not installed: The following software products are not available, or are below the minimum required version: Product Required Minimum version Current version -------------------- -------- --------------- --------------- LSE No V4.3 V5.0 If products marked as nonrequired are to be used with ACMS, they should be upgraded to at least the minimum version displayed before use. (required and optional software checked) (product licenses checked) (installed images checked) Installing ACMS 3-9 Installing ACMS 3.2 Installation Procedure (privileges checked) (disk space checked) (disk quotas checked) (system parameters checked) (process account quotas checked) These messages are also logged in the following file: SYS$UPDATE:ACMS050AA_INSTALLATION.LOG If any of the prerequisites are not met (with the exception of those related to optional software), the installation is aborted and a message similar to the following is displayed: //////////////////////////////////////////////////////////////////////// Installation of ACMS is aborting because prerequisites are not met at 05:30 on 16-JUN-2006 //////////////////////////////////////////////////////////////////////// At this point, address all the prerequisites that were not met, and then restart the installation of ACMS. 3. Checking for previous ACMS installations The installation procedure checks to see if you have previously installed ACMS. If you have, some cleanup from the previous installation might be necessary; this is the case, for example, if you previously installed a development kit, and you are now installing a run-time kit. The following message shows that no cleanup is necessary: ACMS PREVIOUS INSTALLATION -------------------------- (previous installation of ACMS is compatible with current installation) If cleanup is necessary, you are given the option to see a list of files that will be removed from the system disk during the installation. 4. Reviewing the LSE informational message 3-10 Installing ACMS Installing ACMS 3.2 Installation Procedure If you chose the LSE update option at the beginning of the installation, or if you chose the full installation, the installation advises you whether or not it can perform the LSE update. LSE cannot be updated if the optional LSE software is not present or if it is below the minimum version. The following message advises you that the LSE update will take place as requested: ACMS LSE CHECK -------------- (LSE available -- LSE will be updated for ACMS) Later on you are asked if you want to continue the installation. If you were informed that LSE would not be updated, you can continue the installation, then install LSE and reinstall ACMS at your convenience, using the LSE update option; or you can stop the installation, install LSE, and then restart the complete ACMS installation. 5. Reviewing the WBEM Files The installation advises you whether or not the files necessary for the HP Web-Based Enterprise Management (WBEM) environment are already present. The Remote Manager web agent software cannot be used if the appropriate WBEM software is not present or if it is below the minimum version. The following message advises you that the verification of the WBEM files will take place: ACMS WBEM CHECK ------------------- Installing ACMS 3-11 Installing ACMS 3.2 Installation Procedure 6. Reviewing the Oracle Trace informational message The installation advises you whether or not it can perform the Oracle Trace update. Oracle Trace cannot be updated if the optional Oracle Trace software is not present or if it is below the minimum version. The following message advises you that the Oracle Trace update will take place: ACMS Oracle Trace CHECK ------------------- (Oracle Trace available and will be updated for ACMS) Later on you are asked if you want to continue the installation. If you were informed that Oracle Trace would not be updated, you can continue the installation. If Oracle Trace is not available, the ACMS facility definition is stored in a text library specific to Oracle Trace, which is used to update the Oracle Trace facility database when Oracle Trace is installed. You do not have to reinstall ACMS after installing Oracle Trace. 7. Reviewing the CDD informational message If you are installing a run-time kit, the installation advises you whether CDD is available. The availability of CDD affects the features provided by the run-time kit. See Section 1.4.2 for an explanation of these features. The following message advises you that CDD is available: ACMS CDD CHECK -------------- (CDD available -- CDD-related files will be installed) Later on you are asked if you want to continue the installation. If you were informed that ACMS files related to CDD would not be installed, you can continue the installation, then install CDD and reinstall ACMS at your convenience, using the CDD related files option; or you can stop the installation, install CDD, and then restart the complete ACMS installation. 8. Reviewing the old sample files informational message 3-12 Installing ACMS Installing ACMS 3.2 Installation Procedure If you chose the ACMS samples option at the beginning of the installation, or if you chose the full installation, the installation checks for old samples from a previous installation. These samples are stored in SYS$COMMON:[SYSHLP.EXAMPLES.ACMS], and they are superseded by examples supplied with this kit. They are deleted automatically during the installation. The following message advises you that no old samples were found: ACMS OLD SAMPLE FILES --------------------- (no old sample files found) Later on you are asked if you want to continue the installation. If you want to preserve these old samples, stop the installation, rename the sample files to a different directory, and then reinstall ACMS. Installing ACMS 3-13 Installing ACMS 3.2 Installation Procedure 9. Reviewing the ACMS shutdown informational message If you chose the ACMS component software option at the beginning of the installation, or if you chose the full installation, the installation checks for the ACMS shutdown procedure: SYS$STARTUP:ACMSTOP.COM If this procedure is found, the ACMS installation procedure executes it to ensure that previously installed ACMS software is not running during the installation. This shutdown occurs after you choose to continue the installation in a subsequent step. The following message advises you that ACMSTOP.COM was found: ACMS SHUTDOWN CHECK ------------------- (ACMSTOP.COM found -- ACMS will be shut down during installation) ________________________ Note ________________________ If you have previously installed ACMS on this system, and if ACMSTOP.COM is not found, ensure that the ACMS system is shut down before continuing with the installation. ______________________________________________________ 10. Reviewing the postinstallation procedure informational message If you chose the ACMS component software at the beginning of the installation, or if you chose the full installation, the installation procedure advises you whether or not it can execute the postinstallation procedure automatically. The postinstallation procedure cannot be executed if you do not have the required privileges enabled. The following message advises you that the ACMS postinstallation procedure will be executed automatically: 3-14 Installing ACMS Installing ACMS 3.2 Installation Procedure ACMS POSTINSTALLATION PROCEDURE ------------------------------- (postinstallation procedure will be run automatically after installation) ________________________ Note ________________________ Refer to Chapter 4 for important information on other steps to take before using ACMS on your system. ______________________________________________________ 11. Reviewing the system roots check informational message The installation checks for ACMS files in system- specific roots. If you previously installed ACMS, certain files might exist in system-specific roots. With a few exceptions (for example, ACMSPAR.ACM) ACMS files should reside in cluster-common directories such as SYS$COMMON:[SYSLIB]. Some ACMS files might have migrated to system-specific roots as a result of maintenance or other activities performed on the previous version of ACMS. If ACMS files have migrated in this manner, and you then upgrade to a higher version of ACMS, you might subsequently encounter problems running ACMS across a cluster, such as problems related to a version mismatch or the inability to access new functionality on some nodes. The installation checks for ACMS files that might have migrated inadvertently to system-specific roots, and lists any files it finds. HP recommends that you check any files listed to ensure that they do not interfere with the proper operation of ACMS in the cluster. Table 3-1 lists the files that are checked. Table_3-1_ACMS-Related_Files_Checked_For_in_System_Roots___ Directory_______Files______________________________________ SYS$SYSTEM ACM*.EXE, ACM*.DAT, SYSUAF.DAT SYS$LIBRARY ACM*.EXE, ACM*.COM (continued on next page) Installing ACMS 3-15 Installing ACMS 3.2 Installation Procedure Table 3-1 (Cont.) ACMS-Related Files Checked For in System __________________Roots____________________________________ Directory_______Files______________________________________ SYS$MANAGER ACM*.COM SYS$STARTUP_____ACM*.COM___________________________________ This example shows that no ACMS files were found in system-specific roots: ACMS SYSTEM ROOTS CHECK ----------------------- (no ACMS-related files found in system-specific roots) 12. Choosing to execute the IVP You are now asked whether you want to execute the ACMS Installation Verification Procedure (IVP). This question is asked if you are installing ACMS software (as opposed to installing samples or updating the LSE environment, for example). HP recommends that you run the IVP automatically after the installation, to ensure that the installation was successful. Chapter 5 contains more information on the IVP, including how to execute it manually at a later time. The following question is asked to determine whether you want to run the IVP automatically; press to accept the default answer, YES: ACMS IVP -------- * Do you want to execute the Installation Verification Procedure [YES]? If you choose to execute the IVP, the installation now checks for the IVP user account ACMS$IVP. If the account ACMS$IVP does not exist, you are asked to supply a user identification code (UIC) and password for this account. The information you supply is used to create the account in the third phase of the installation. 3-16 Installing ACMS Installing ACMS 3.2 Installation Procedure This example shows how to supply a UIC and password for the ACMS$IVP account: The ACMS$IVP account used to execute the IVP is not available. You must supply a UIC and password for this account so that it can be created; this must be done before the IVP can be executed. Please enter the UIC for the ACMS$IVP account, in the form [ggggg,nnnnnn] * UIC: [400,200] Please enter a password of at least 8 characters, using only the following characters: ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789$_ * Password: * Verification: ________________________ Note ________________________ The password and verification are not echoed when you type them. ______________________________________________________ Refer to Section 2.9 for more information on selecting a valid UIC for the ACMS$IVP account. 13. Choosing to continue the installation At this time, the installation procedure lists the steps to complete the installation, and an approximate time for the rest of the installation. It then asks if you want to continue. If issues remain that you must address before the installation continues, answer NO to stop the installation. The following example shows the work list for a typical development installation; the lists for run-time and remote-access installations are different. SUMMARY OF THIS ACMS INSTALLATION --------------------------------- The following steps will be taken to complete this installation: Installing ACMS 3-17 Installing ACMS 3.2 Installation Procedure o The ACMS system will be shut down (via SYS$STARTUP:ACMSTOP.COM) o ACMS component software will be installed o WBEM environment will be updated for ACMS o LSE environment will be updated for ACMS o Oracle Trace facility database will be updated for ACMS o CDD-related ACMS files will be installed o ACMS samples will be installed o ACMS Request Interface samples will be installed o The ACMS postinstallation procedure will be executed o The ACMS IVP will be executed The rest of this installation will take approximately 7 minutes. Execution of the IVP will take approximately 2 minutes. Note that this time is heavily dependent your system load, hardware and kit media. The time mentioned was measured on a stand-alone HP 3000 (Alpha) system with a disk-resident kit. Your time may vary. * Do you want to continue the installation [YES]? Press to continue the installation. 3.2.3 Informational Messages (Third Phase) In the third installation phase, the actual work of the installation takes place; restoring savesets, moving files, updating databases, and so on. This phase has no user interaction. At the beginning of the phase, a message similar to the following is displayed: Installation of ACMS started at 05:18 on 16-JUN-2006 Following this message, the installation procedure displays a number of informational messages that report on the progress of the installation. If any errors are encountered in this phase, the installation aborts and a message similar to the following is displayed: //////////////////////////////////////////////////////////////////////// Installation of ACMS is aborting because errors were encountered at 05:30 on 16-JUN-2006 //////////////////////////////////////////////////////////////////////// If you receive this message, use information in previous error messages and the installation log to fix the problem, and then reinstall ACMS. 3-18 Installing ACMS Installing ACMS 3.2 Installation Procedure When the third phase is successfully completed, a message similar to the following is displayed: Installation of ACMS completed successfully at 05:20 on 16-JUN-2006 %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... During the ACMS installation, VMSINSTAL operates in safety mode, which means that it defers file operations until the third phase has successfully completed. The VMSINSTAL- I-MOVEFILES message indicates that these deferred file operations are now being performed. 3.2.4 Running the Postinstallation Procedure (Fourth Phase) If you were informed during the second phase of the installation that the ACMS postinstallation procedure would be executed, it is done at this time. A message similar to the following is displayed: ACMS postinstallation procedure started at 05:21 on 16-JUN-2006 The postinstallation procedure performs the following steps: 1. Checking the ACMS$DIRECTORY logical name The procedure checks for the presence of the logical name ACMS$DIRECTORY. If this logical name is defined, it must be in /SYSTEM /SUPERVISOR mode, and it must point to an existing directory. If ACMS$DIRECTORY is not defined or is improperly defined, the procedure asks you for information so that it can define the logical name. The following message shows that ACMS$DIRECTORY is properly defined: ACMS$DIRECTORY is defined as MGR$:[ACMS.DIRECTORY] ACMS$DIRECTORY logical is acceptable 2. Converting ACMSGEN parameter files The procedure asks if you want to convert existing ACMSGEN parameter files. If you answer YES, or press to accept the default answer, the procedure searches for all ACMSGEN parameter files located in SYS$SYSDEVICE:[SYS*.SYSEXE] and SYS$COMMON:[SYSEXE], and converts them to be compatible with ACMS Version 5.0A. Installing ACMS 3-19 Installing ACMS 3.2 Installation Procedure The following message shows the ACMSGEN convert question, and typical output from the conversion process: Do you want to convert existing ACMSGEN parameter files [Y]? Converting SYS$SYSDEVICE:[SYSEXE]ACMSPAR.ACM The ACMSGEN parameter files listed above have been converted; if other parameter files exist on your system, they must be updated as follows: $ RUN SYS$SYSTEM:ACMSGEN ACMSGEN> USE file-specification ACMSGEN> WRITE file-specification ACMSGEN> EXIT 3. Converting ACMS UDF and DDF files The procedure asks if you want to convert existing ACMS UDF and DDF parameter files. If you answer YES, or press to accept the default answer, the procedure searches for the files pointed to by the logical names ACMSUDF and ACMSDDF, if these logicals are defined, and then for ACMSUDF.DAT and ACMSDDF.DAT in SYS$SYSROOT:[SYS*], and converts them to be compatible with ACMS Version 5.0A. The following message shows the ACMS UDF and DDF convert question, and typical output from the conversion process: Do you want to convert existing ACMS UDF and DDF files [Y]? Converting UDF file SYS$COMMON:[SYSEXE]ACMSUDF.DAT Converting DDF file SYS$COMMON:[SYSEXE]ACMSDDF.DAT 4. Checking for ACMS UDF and DDF files The procedure checks for the presence of ACMS DDF and UDF files. It first tries to locate these files through the /SYSTEM /EXECUTIVE logical names ACMSUDF and ACMSDDF, if they exist. The procedure then checks for ACMSUDF.DAT and ACMSDDF.DAT in SYS$COMMON:[SYSEXE]. If the files are not found in either manner, the procedure creates them. 3-20 Installing ACMS Installing ACMS 3.2 Installation Procedure The following message shows that the logical names do not exist, but that the files were found in SYS$COMMON:[SYSEXE]: No /SYSTEM /EXECUTIVE logical ACMSUDF found SYS$COMMON:[SYSEXE]ACMSUDF exists No /SYSTEM /EXECUTIVE logical ACMSDDF found SYS$COMMON:[SYSEXE]ACMSDDF exists 5. Checking for ACMS_SETUP.COM The procedure checks for the presence of ACMS_SETUP.COM in SYS$STARTUP. If the file does not exist, it is created. This is a template for site-specific commands related to the startup of ACMS. ACMS_SETUP.COM is executed by ACMSTART.COM, which is normally executed during system startup to start the ACMS software. Chapter 4 explains how to modify this template to address your specific needs regarding ACMS startup. If ACMS_SETUP.COM already exists, the ACMS_SETUP_NEW.COM template file is created. After the installation, review this template file to see if you need to add any new commands to your existing ACMS_SETUP.COM. The following message shows that the ACMS_SETUP.COM already exists, and that the template file ACMS_SETUP_ NEW.COM is being created: SYS$COMMON:[SYS$STARTUP]ACMS_SETUP.COM already exists Creating SYS$COMMON:[SYS$STARTUP]ACMS_SETUP_NEW.COM Please review the contents of ACMS_SETUP_NEW.COM to determine whether there are any commands you should add to your existing ACMS_SETUP.COM. Installing ACMS 3-21 Installing ACMS 3.2 Installation Procedure 6. Checking for ACMS menu files The procedure checks in ACMS$DIRECTORY for the ACMS command menu ACMSCMD.MDB, and the default user menu ACMS.MDB, and copies them into that directory if they do not exist. The following message shows that the menu files already exist in ACMS$DIRECTORY: ACMS$DIRECTORY:ACMSCMD.MDB already exists -- not copied ACMS$DIRECTORY:ACMS.MDB already exists -- not copied 7. Checking for ACMS$MGMT_SETUP files The procedure checks for ACMS$MGMT_SETUP and Remote Manager configuration files and asks if you want to set up and configure the Remote Manager. Do you want to SETUP and CONFIGURE the ACMS Remote System Manager [Y]? Creating SYS$STARTUP:ACMS$MGMT_SETUP.COM If you respond yes, the procedure asks you a series of questions concerning Remote Manager configuration. Refer to the HP ACMS for OpenVMS Remote Systems Management Guide for more information about Remote Manager setup. When the postinstallation procedure is completed, a message similar to the following is displayed: ACMS postinstallation procedure completed successfully at 05:22 on 16-JUN-2006 ________________________ Note ________________________ See Chapter 4 for information on tasks that you perform manually after ACMS is installed on your system. ______________________________________________________ 3.2.5 Running the Installation Verification Procedure (Fifth Phase) If you were informed during the second phase of the installation that the ACMS Installation Verification Procedure (IVP) would be executed, it is done at this time. A message similar to the following is displayed: ACMS Installation Verification Procedure started at 05:22 on 16-JUN-2006 3-22 Installing ACMS Installing ACMS 3.2 Installation Procedure The IVP is then invoked. It displays several informational messages to inform you of its progress. Refer to Chapter 5 for more information on the ACMS IVP. ________________________ Note ________________________ If the ACMS IVP is not invoked automatically during the installation, invoke it manually at your earliest convenience after the installation. ______________________________________________________ When the ACMS IVP is completed, a message similar to the following is displayed: ACMS Installation Verification Procedure completed successfully at 05:24 on 16-JUN-2006 3.2.6 Completing the Installation The following message indicates that the entire ACMS installation is complete: Installation of ACMSDEVA_MAA V5.0 completed at 05:24 You can now log out of the privileged SYSTEM account: $ LOGOUT SYSTEM logged out at 16-JUN-2006 05:25:01.55 VMSINSTAL deletes or changes entries in the process symbol tables during the installation. Therefore, if you are going to continue using the SYSTEM account and you want to restore these symbols, log out and log in again. 3.3 Recovering from System and Installation Failures An unsuccessful installation can result from a system failure or errors encountered during the installation procedure. In some cases, you must correct the problem and reinstall ACMS. In other cases, you can continue where you left off. The following sections describe various failure scenarios and the recommended procedure to follow to recover from them. Installing ACMS 3-23 Installing ACMS 3.3 Recovering from System and Installation Failures 3.3.1 System Failures If you experience a system failure, such as a power loss during installation, VMSINSTAL automatically attempts to continue the installation when you reboot the system. Depending on the point in the installation at which the system failed, one of three conditions exists: o The system disk did not undergo any changes before the system failure. VMSINSTAL instructs you to restart the installation. o The system disk used by the installation was corrupted. VMSINSTAL instructs you to restore the system disk from the backup copy and restart the installation. o VMSINSTAL continues the installation and then might tell you to manually purge replaced files, even if you requested that they be purged automatically. You can purge files, but remember that purging deletes all but the latest version of all files on your system disk. If you have multiple versions of system files that you want to save, you can delete just the ACMS files you want to remove from system directories. If you want to purge files, reboot the system, log in to the SYSTEM account, and purge all system files using the following command: $ PURGE/LOG SYS$SYSROOT:[*...]*.* When you have performed this task, the installation is complete. If the system fails after you see the message that indicates the beginning of the ACMS IVP, VMSINSTAL has already completed the installation of the component software. In this case, when you reboot your system, VMSINSTAL displays the following message: %VMSINSTAL-I-RECOVER, ACMSDEVA_MAA 050 was being installed when the system crashed. The installation completed satisfactorily. This message indicates that VMSINSTAL has finished successfully, not that the installation of ACMS was successful. VMSINSTAL does not automatically restart the IVP. You can run the IVP independently by following the steps described in Chapter 5. 3-24 Installing ACMS Installing ACMS 3.3 Recovering from System and Installation Failures 3.3.2 ACMS Installation Failures If the installation of the ACMS software fails for some reason other than a system failure, the installation procedure displays a message telling you the cause of the failure. To continue with the installation, you must correct the condition causing the error and restart the installation procedure from the beginning. Errors can occur during the installation if any of the following conditions exist: o Operating system version is incorrect. o Prerequisite software version is incorrect. o Quotas necessary for successful installation are insufficient. o System parameter values for successful installation are insufficient. o OpenVMS help library is currently in use. For descriptions of the error messages generated by these conditions, see the OpenVMS documentation on system messages, recovery procedures, and OpenVMS software installations. If you are notified that any of these conditions exist, take the appropriate action as described in the message. (For example, you might need to change a system parameter or increase a quota value.) For information on installation requirements, see Chapter 2. If the installation of the component software completes satisfactorily, but a test or operation fails during the IVP, the IVP displays a message describing the failure and suggests a course of action. In most cases, the suggested course of action is to reinstall ACMS. The failure could be due to low settings for the SYSGEN parameters GBLPAGES, GBLSECTIONS, GBLPAGFIL, or to an insufficient number of process slots. Check the ACMS Software Event Log for a message that indicates the source of the problem. If the IVP fails after you reinstall ACMS, contact your local HP Customer Support Center. Installing ACMS 3-25 Installing ACMS 3.3 Recovering from System and Installation Failures 3.3.3 Recovering from Errors You can run the ACMS IVP separately after you install ACMS by following the instructions in Chapter 5. As the IVP executes, it checks the success of each test and operation it performs. If any test or operation fails, the IVP displays a message describing the failure and suggests a course of action. Follow the suggested course of action and then restart the IVP as described in Chapter 5. If the action you take is to reinstall ACMS, the IVP runs automatically if you answer YES to the IVP question. If you still cannot successfully run the IVP, contact your local HP Customer Support Center. 3.4 Accessing the Online Release Notes After ACMS has been installed, the release notes are located in the following file: SYS$HELP:ACMS050AA.RELEASE_NOTES Online help also directs you to the release notes file. After the installation, you can enter the following command: $ HELP ACMS RELEASE_NOTES Hardcopy release notes are not included with the documentation set for ACMS. 3.5 Files Installed on Your System The files added to your system by the ACMS installation are listed in: SYS$SYSTEM:ACMS050AA_FILES.DAT You can display or print this file after you install ACMS. ACMS Version Identification File (ACMS_ECO_LEVEL.DAT) Starting with the ACMS Version 4.0 ECO Kit 1 release, a file named ACMS_ECO_LEVEL.DAT is distributed with the kit. This file is placed in the SYS$SYSTEM directory during installation. 3-26 Installing ACMS Installing ACMS 3.5 Files Installed on Your System ACMS_ECO_LEVEL.DAT contains the version identifier for the ACMS release that is currently installed on the system. This file is distributed for all releases, including full releases, that have an ECO level of 0. If you report any problems with ACMS, refer to this file to determine the current ACMS version number. The version in this file may be more current than the version numbers that appear throughout the ACMS system, especially when running with an ECO release. Installing ACMS 3-27 4 _________________________________________________________________ After Installing ACMS This chapter describes system management tasks that you perform manually after installing ACMS Version 5.0A. These tasks might include: o Executing the ACMS postinstallation procedure manually (if it was not executed automatically during installation) o Editing system startup and shutdown procedures to include ACMS o Editing the ACMS site-specific startup procedure ACMS_ SETUP.COM o Modifying ACMS parameters o Authorizing applications, devices, users, and processes o Creating and modifying ACMS user accounts o Setting up ACMS on an OpenVMS Cluster system o Enabling distributed ACMS processing o Rebuilding the LSE environment o Preparing language-specific ACMS development environments The following sections describe these tasks. 4.1 Executing the ACMS Postinstallation Procedure If you were notified during the ACMS installation that the postinstallation procedure would not be run automatically, execute it now. After Installing ACMS 4-1 After Installing ACMS 4.1 Executing the ACMS Postinstallation Procedure To execute the postinstallation procedure manually, use the following commands: $ SET DEFAULT SYS$MANAGER $ @ACMS_POST_INSTALL.COM See Section 3.2.4 for more information on the steps performed by the postinstallation procedure. 4.2 Editing System Startup and Shutdown Procedures You must edit the OpenVMS system startup and shutdown procedures to provide for automatic startup and shutdown of ACMS when your system is rebooted. (This step is usually not necessary for system upgrades.) 4.2.1 Editing the System Startup Procedure Add the following DCL command to the system startup procedure: $ @SYS$STARTUP:ACMSTART.COM For sites that have modularized startup procedures, be sure to add the command to the correct procedure. The default startup command procedure for OpenVMS Alpha systems is SYS$MANAGER:SYSTARTUP_VMS.COM. Position the ACMS startup command after the commands that start software on which ACMS relies. In particular, start ACMS after the network, HP DECdtm, and HP DECforms are started, and before HP TP Desktop Connector is started. For example: $ @SYS$STARTUP:STARTNET.COM $ @SYS$STARTUP:DECDTM$STARTUP.COM $ @SYS$STARTUP:FORMS$STARTUP.COM $ @SYS$STARTUP:ACMSTART.COM $ @SYS$STARTUP:ACMSDI$STARTUP.COM ________________________ Note ________________________ The network must be running before ACMS is started, if you are going to use distributed ACMS processing. ______________________________________________________ 4-2 After Installing ACMS After Installing ACMS 4.2 Editing System Startup and Shutdown Procedures 4.2.2 Installing ACMS Images as Resident on OpenVMS Alpha On OpenVMS Alpha systems, your application performance may improve by installing certain ACMS images as resident with the OpenVMS Install utility. Installing images as resident allows them to take advantage of the OpenVMS Alpha image-slicing feature. The code sections of an image installed as resident reside in huge pages called granularity hint regions (GHRs) in memory. The Alpha hardware can consider a set of pages as a single GHR. This GHR can be mapped by a single page table entry (PTE) in the translation buffer (TB). The result is a reduction in TB miss rates. For more information on improving the performance of shareable images, see the OpenVMS Linker Utility Manual. The following ACMS images have been linked to allow them to be installed as resident: For all kits: o SYS$LIBRARY:ACMSHR.EXE o SYS$LIBRARY:ACMTWPSHR.EXE o SYS$LIBRARY:ACMRRSHR.EXE o SYS$LIBRARY:ACMVFSHR.EXE For development and run-time kits only (in addition to the preceding): o SYS$LIBRARY:ACMIWPSHR.EXE o SYS$SYSTEM:ACMSIWP.EXE To install images as resident, execute the ACMS startup command procedure with the RESIDENT parameter as follows: @SYS$STARTUP:ACMSTART.COM RESIDENT Installing images as resident may require that you increase the GBLPAGES, GBLSECTIONS, and NPAGEDYN system parameters. Refer to Section 2.6.3 for more information on using AUTOGEN to change system parameters. For OpenVMS Alpha Version 6.x, you may need to increase the GH_RSRVPGCNT SYSGEN parameter to install ACMS images as resident. After Installing ACMS 4-3 After Installing ACMS 4.2 Editing System Startup and Shutdown Procedures 4.2.3 ACMS