                           H                     Compaq_ACMS_for_OpenVMS_____________________________2                     Version 4.4 Installation Guide    -                     Order Number: AA-N686P-TE                          July 2001   G                     This document provides information about installing F                     the Compaq ACMS for OpenVMS, Version 4.4 software.              H                     Revision/Update Information:  This manual supersedesE                                                   the Compaq ACMS for E                                                   OpenVMS Version 4.3 E                                                   Installation Guide.   G                     Operating System:             Compaq OpenVMS Alpha, ?                                                   Version 6.2,  ?                                                   7.2-1, or 7.3 E                                                   Compaq OpenVMS VAX, C                                                   Version 6.2, 7.2, 8                                                   or 7.3  A                     Software Version:             Compaq ACMS for F                                                   OpenVMS, Version 4.4        /                     Compaq Computer Corporation "                     Houston, Texas                 J           ________________________________________________________________  ,            2001 Compaq Computer Corporation  B           Compaq and the Compaq logo Registered in U.S. Patent and           Trademark Office.   A           ACMS, DECforms, DECnet, DECset, OpenVMS, PATHWORKS, and E           Tru64 are trademarks of the Compaq Information Technologies ?           Group, L.P. in the United States and other countries.   B           Motif is a registered trademark of The Open Group in the,           United States and other countries.  =           All other product names mentioned herein may be the 3           trademarks of their respective companies.   C           Confidential computer software. Valid license from Compaq C           required for possession, use, or copying. Consistent with >           FAR 12.211 and 12.212, Commercial Computer Software,A           Computer Software Documentation, and Technical Data for D           Commercial Items are licensed to the U.S. Government under/           vendor's standard commercial license.   ?           Compaq shall not be liable for technical or editorial ?           errors or omissions contained herein. The information ?           in this document is provided "as is" without warranty B           of any kind and is subject to change without notice. TheE           warranties for Compaq products are set forth in the express @           limited warranty statments accompanying such products.?           Nothing herein should be construed as constituting an            additional warranty.  E                                                                ZK6613   ?           The OpenVMS documentation set is available on CD-ROM.                                  C   _________________________________________________________________   C                                                            Contents       C   Preface...................................................    vii   #   1  Planning the ACMS Installation   C         1.1   Types of ACMS Kits............................    1-1 C         1.2   ACMS Licenses.................................    1-2 C         1.3   Required Operating System Components..........    1-3 C         1.4   Layered Product Requirements..................    1-3 C         1.4.1     Determining Software Version Numbers......    1-3 C         1.4.2     Requirements for Oracle CDD...............    1-5 C         1.4.3     Requirements for LSE......................    1-6 C         1.4.4     Requirements for TP Desktop Connector.....    1-6 2         1.4.5     Recommended Order for InstallingC                   Software..................................    1-6 C         1.5   Upgrading Software in a Distributed System....    1-7 C         1.5.1     Configuration Issues......................    1-7 C         1.6   Product Dependencies..........................    1-8      2  Preparing to Install ACMS  C         2.1   Backing Up Your System Disk...................    2-1 C         2.2   Software Versions.............................    2-1 C         2.2.1     Installed Images..........................    2-2 C         2.3   Privileges....................................    2-3 C         2.4   Disk Space....................................    2-3 C         2.4.1     Disk Space for a Normal Installation......    2-3 C         2.4.2     Installing on a Disk with Limited Space...    2-5 C         2.5   Disk Quotas...................................    2-6 C         2.6   System Parameters.............................    2-6 C         2.6.1     Checking System Parameter Values..........    2-9 9         2.6.2     Calculating the Values for GBLPAGES and C                   GBLSECTIONS...............................    2-9     C                                                                 iii                    9           2.6.3     Changing System Parameter Values with E                     AUTOGEN...................................   2-10 8           2.6.4     Setting the CLISYMTBL Dynamic SystemE                     Parameter.................................   2-10 E           2.7   Process Account Quotas........................   2-11 E           2.8   Time Required for Installation................   2-13 E           2.9   ACMS$IVP User Authorization...................   2-13        3  Installing ACMS  E           3.1   Installation Log..............................    3-1 E           3.2   Installation Procedure........................    3-1 E           3.2.1     Invoking VMSINSTAL (First Phase)..........    3-3 6           3.2.2     Product-Specific Questions (SecondE                     Phase)....................................    3-8 E           3.2.3     Informational Messages (Third Phase)......   3-18 :           3.2.4     Running the Postinstallation ProcedureE                     (Fourth Phase)............................   3-19 9           3.2.5     Running the Installation Verification E                     Procedure (Fifth Phase)...................   3-23 E           3.2.6     Completing the Installation...............   3-24 7           3.3   Recovering from System and Installation E                 Failures......................................   3-24 E           3.3.1     System Failures...........................   3-24 E           3.3.2     ACMS Installation Failures................   3-25 E           3.3.3     Recovering from Errors....................   3-26 E           3.4   Accessing the Online Release Notes............   3-26 E           3.5   Files Installed on Your System................   3-27        4  After Installing ACMS  3           4.1   Executing the ACMS Postinstallation E                 Procedure.....................................    4-1 3           4.2   Editing System Startup and Shutdown E                 Procedures....................................    4-2 E           4.2.1     Editing the System Startup Procedure......    4-2 9           4.2.2     Installing ACMS Images as Resident on E                     OpenVMS Alpha.............................    4-3 6           4.2.3     ACMSTART.COM Installs DECC$SHR andE                     ACMS$TRACE_SHR.EXE........................    4-4 E           4.2.4     Editing the System Shutdown Procedure.....    4-4 E           4.3   Editing ACMS_SETUP.COM........................    4-5 E           4.3.1     Optional ACMS Logical Names...............    4-5          iv                   :               4.3.2     Installing Application DevelopmentI                         Shareable Images..........................    4-6 I               4.3.3     ACMS System Management Commands...........    4-7 I               4.4   Modifying ACMS Parameters.....................    4-8 A               4.5   Authorizing Applications, Devices, Users, and I                     Processes.....................................   4-10 I               4.5.1     Authorizing New Applications..............   4-10 I               4.5.2     Authorizing New Terminals.................   4-10 I               4.5.3     Authorizing New Users.....................   4-11 I               4.5.4     Authorizing ACMS Processes................   4-11 I               4.6   Creating and Modifying ACMS User Accounts.....   4-13 I               4.6.1     Privileges................................   4-13 I               4.6.2     Quotas....................................   4-13 9               4.7   Setting up ACMS on an OpenVMS Cluster I                     System........................................   4-15 I               4.8   Enabling Distributed ACMS Processing..........   4-16 I               4.9   Rebuilding the LSE Environment................   4-16 I               4.10  Installing ACMS Menu Form Files...............   4-16 @               4.11  Preparing Language-Specific ACMS DevelopmentI                     Environments..................................   4-16 I               4.11.1    BLISS Agents..............................   4-17 I               4.11.2    Pascal Agents.............................   4-17 I               4.12  Determining and Reporting Problems............   4-18            5  Running the ACMS IVP   I               5.1   Functions of the IVP..........................    5-1 I               5.2   Running the IVP...............................    5-2 I               5.3   Errors Running the IVP........................    5-3 I               5.4   Sample IVP Execution..........................    5-4            6  Deinstalling ACMS  I               6.1   Starting the Deinstallation Procedure.........    6-1 I               6.2   Completing the Deinstallation.................    6-2                     I                                                                         v                         A  Sample Installations   4           A.1   OpenVMS Alpha Development Kit SampleE                 Installation..................................    A-1 2           A.2   OpenVMS VAX Development Kit SampleE                 Installation..................................   A-14   0     B  Registering and Loading Your ACMS License  E           B.1   Sample ACMS License PAK.......................    B-1 E           B.2   Using VMSLICENSE.COM..........................    B-2 E           B.3   Using LICENSE DCL Commands....................    B-3   +     C  Modifying ACMS Help and Message Text   4     D  Creating Transaction Logs for DECdtm Services  8           D.1   Prerequisites for Creating a TransactionE                 Log...........................................    D-1 =           D.2   Planning the Size and Location of Transaction E                 Logs..........................................    D-1 7           D.2.1     Determining the Size of Transaction E                     Logs......................................    D-2 <           D.2.2     Determining the Location for TransactionE                     Logs......................................    D-3 E           D.3   Setting Up and Creating Transaction Logs......    D-4 E           D.3.1     Setting Up the Transaction Logs...........    D-4 E           D.3.2     Creating the Transaction Logs.............    D-5 >           D.4   Example of Setting Up and Creating TransactionE                 Logs .........................................    D-5   	     Index     
     Tables  E           1-1       ACMS Licenses.............................    1-2   7           1-2       Compatible Products Image Files for E                     OpenVMS Alpha.............................    1-4   7           1-3       Compatible Products Image Files for E                     OpenVMS VAX...............................    1-4   E           2-1       Privilege Requirements....................    2-3        vi                   A               2-2       Disk Space Requirements for OpenVMS Alpha I                         by Kit....................................    2-3   B               2-3       Disk Space Requirements for OpenVMS VAX byI                         Kit.......................................    2-4   A               2-4       Disk Space Requirements for OpenVMS Alpha I                         by Component..............................    2-4   B               2-5       Disk Space Requirements for OpenVMS VAX byI                         Component.................................    2-4   <               2-6       Required System Parameter Values forI                         OpenVMS Alpha.............................    2-7   <               2-7       Required System Parameter Values forI                         OpenVMS VAX...............................    2-8   I               2-8       Process Account Quotas....................   2-12   I               2-9       Timetable for Installing ACMS.............   2-13   @               3-1       ACMS-Related Files Checked For in SystemI                         Roots.....................................   3-16   I               4-1       Optional ACMS Logical Names...............    4-5   >               4-2       Global Sections and Pages Required forI                         Shared Utility Images (Alpha).............    4-6   >               4-3       Global Sections and Pages Required forI                         Shared Utility Images (VAX)...............    4-7   I               4-4       User Account Quotas.......................   4-13   I               5-1       ACMS IVP Tests............................    5-2   I               B-1       Product Authorization Key Fields..........    B-2   I               B-2       LICENSE LOAD Parameters and Qualifiers....    B-4   I               D-1       Transaction Log Requirements..............    D-5       I                                                                       vii                              I         _________________________________________________________________   I                                                                   Preface       C               This installation guide describes how to install kits F               for the following Compaq ACMS for OpenVMS (ACMS) product               packages:   (               o  ACMS Development System  %               o  ACMS Run-Time Option   *               o  ACMS Remote Access Option           Intended Audience   H               Read this manual if you are responsible for installing andH               maintaining software for ACMS. To perform the installationG               procedures described in this manual, you must have access B               to a privileged OpenVMS system manager's account andB               be familiar with the OpenVMS installation procedure,               VMSINSTAL.           Document Structure  D               This manual has the following chapters and appendixes:  ?               Chapter 1   Describes ACMS kits and licenses, the I                           recommended order for updating layered products F                           used with ACMS, and special dependencies and)                           considerations.   A               Chapter 2   Explains how to prepare your system for *                           installing ACMS.        I                                                                       vii                      D           Chapter 3   Describes how to install the ACMS software andB                       sample applications and run the InstallationA                       Verification Procedure (IVP). It also tells E                       you how to recover from system and installation                        failures.   C           Chapter 4   Describes postinstallation steps that prepare ;                       your OpenVMS system for running ACMS.   B           Chapter 5   Describes how to run the ACMS IVP separately6                       from the installation procedure.  6           Chapter 6   Describes how to deinstall ACMS.  B           Appendix A  Contains a sample installation for each ACMS&                       development kit.  E           Appendix B  Contains information on registering and loading (                       your ACMS license.  C           Appendix C  Describes how to modify ACMS help and message ?                       text, for example, to translate them to as2                       language other than English.  B           Appendix D  Describes considerations for creating DECdtm                        log files.                                         viii                            Related Documentsq  I               Consult the OpenVMS System Manager's Manual for information G               about installing or upgrading layered product software one+               the OpenVMS operating system.   I               Three other manuals contain information about managing your /               ACMS system once it is installed:   >               o  Compaq ACMS for OpenVMS Managing Applications  H                  Explains how to start and stop the ACMS system, monitorH                  system performance, and perform some tuning operations.H                  This manual also discusses installing applications, and>                  authorizing users, applications, and devices.  B               o  Compaq ACMS for OpenVMS Version 4.4 Release Notes  D                  Contains information about new features and currentG                  restrictions for ACMS. Compaq ACMS for OpenVMS Version E                  4.4 Release Notes are available to you on line. TheytA                  are stored in the file SYS$HELP:ACMS044.RELEASE_fB                  NOTES during the ACMS installation procedure. TheG                  installation procedure allows you to print Compaq ACMSlF                  for OpenVMS Version 4.4 Release Notes at the start of"                  the installation.  H               o  Compaq ACMS for OpenVMS Remote Systems Management Guide  D                  Describes how to install and use the Remote ManagerI                  (and Remote Manager web agent) to manage Compaq ACMS fori3                  OpenVMS software systems remotely.   C               Compaq ACMS for OpenVMS Systems Interface Programming F               gives directions for building the BLISS library file and4               an environment file for Pascal agents.  F               For additional information on the compatibility of otherG               software products with this version of ACMS, refer to thetG               Compaq ACMS for OpenVMS Software Product Description (SPDt               25.50.xx).  H               For additional information about the Open Systems SoftwareF               Group (OSSG) products and services, access the following-               OpenVMS World Wide Web address:i  +               http://www.compaq.com/openvmsm  I                                                                        ixd    s                   Reader's Commentsr  7           Compaq welcomes your comments on this manual.   <           Print or edit the online form SYS$HELP:OPENVMSDOC_4           COMMENTS.TXT and send us your comments by:  +           Internet    openvmsdoc@compaq.com_  B           Fax         603 884-0120, Attention: OSSG Documentation,                        ZKO3-4/U08  1           Mail        Compaq Computer Corporation.:                       OSSG Documentation Group, ZKO3-4/U08(                       110 Spit Brook Rd.+                       Nashua, NH 03062-2698C  )     How To Order Additional Documentation   B           Use the following World Wide Web address for information6           about how to order additional documentation:  '           http://www.compaq.com/openvmse  ?           To reach the OpenVMS documentation website, click thee           Documentation link..  B           If you need help deciding which documentation best meets)           your needs, call 1-800-ATCOMPA.m       Conventions   <           The following conventions are used in this manual:  C           Ctrl/x           A sequence such as Ctrl/x indicates that.B                            you must press and hold the key labeled@                            Ctrl while you press another key or a2                            pointing device button.  @           <Return>         In examples, a key name enclosed in a@                            box indicates that you press a key onD                            the keyboard. (In text, a key name is not.                            enclosed in a box.)  E                            In the HTML version of this document, this.E                            convention appears as brackets rather than.!                            a box.        xS e  r                I               .                A vertical ellipsis indicates the omissionpF               .                of items from a code example or commandD               .                format; the items are omitted becauseH                                they are not important to the topic being)                                discussed.   I               Monospace text   Monospace type indicates code examples and.;                                interactive screen displays.   G                                In the C programming language, monospacenD                                type in text identifies the following?                                elements: keywords, the names of H                                independently compiled external functions?                                and files, syntax summaries, andsE                                references to variables or identifierst8                                introduced in an example.  I                                In the HTML version of this document, this @                                text style may appear as italics.  F               -                A hyphen at the end of a command formatF                                description, command line, or code lineF                                indicates that the command or statement?                                continues on the following line.   D               numbers          All numbers in text are assumed to beI                                decimal unless otherwise noted. NondecimaluH                                radixes-binary, octal, or hexadecimal-are4                                explicitly indicated.  >               italic text      Italic text indicates important>                                information, complete titles ofG                                manuals, or variables. Variables includerG                                information that varies in system outputtB                                (Internal error number), in commandE                                lines (/PRODUCER=name), and in command F                                parameters in text (where dd representsH                                the predefined code for the device type).            I                                                                        xi     .                A           UPPERCASE        Uppercase text indicates the name of a.E                            routine, the name of a file, the name of adD                            file protection code, or the abbreviation2                            for a system privilege.  D           <lowercase>      In command format descriptions, lowercase=                            text in angle brackets indicates a.5                            required clause or phrase.A       References to Products  A           The ACMS documentation set to which this manual belongs @           often refers to certain products by abbreviated names:  E           ___________________________________________________________ E           AbbreviatioProduct_________________________________________   C           ACMS       Compaq ACMS for OpenVMS Alpha, and Compaq ACMSi$                      for OpenVMS VAX  E           Ada        Compaq Ada for OpenVMS Alpha Systems, and Compaq 0                      Ada for OpenVMS VAX Systems  C           BASIC      Compaq BASIC for OpenVMS, and Compaq BASIC for.                      OpenVMS  E           C          Compaq C for OpenVMS Alpha Systems, and Compaq C ,                      for OpenVMS VAX Systems  9           CDD        Oracle CDD/Administrator, and Oraclec#                      CDD/Repository   @           COBOL      Compaq COBOL for OpenVMS Alpha Systems, and9                      Compaq COBOL for OpenVMS VAX Systems.  D           DATATRIEVE Compaq DATATRIEVE for OpenVMS Alpha, and Compaq/                      DATATRIEVE for OpenVMS VAXa  (           DBMS       Oracle CODASYL DBMS  0           DECforms   Compaq DECforms for OpenVMS           xii. 4               I               ___________________________________________________________ I               AbbreviatioProduct_________________________________________m  F               FORTRAN    Compaq Fortran for OpenVMS Alpha Systems, and?                          Compaq Fortran for OpenVMS VAX Systems   G               OpenVMS    The Compaq OpenVMS Alpha operating system, and @                          the Compaq OpenVMS VAX operating system  D               Pascal     Compaq Pascal for OpenVMS Alpha, and Compaq/                          Pascal for OpenVMS VAX.  1               PL/I       PL/I for OpenVMS Systems.  #               Rdb        Oracle Rdb   8               SQL        The SQL interface to Oracle Rdb  I               TDMS_______Compaq_TDMS_for_OpenVMS_VAX_____________________.  F                 ________________________ Note ________________________  >                 The DECtrace product is the predecessor to theB                 Oracle Trace product. Some information in the ACMSD                 documentation, particularly in some examples, refers?                 to DECtrace. Except where version specific, the.B                 information applies to the Oracle Trace product asF                 well and, as you read the information, you can use theE                 product name Oracle Trace instead of the product name C                 DECtrace with no significant difference in meaning.   F                 ______________________________________________________                            I                                                                      xiii.    -                    I                                                                         1.I         _________________________________________________________________L  I                                            Planning the ACMS Installation-    E               This chapter describes the available ACMS kits. It also D               discusses the dependencies among ACMS Version 4.4, theG               OpenVMS operating system, and other layered products, andaH               considerations for upgrading and using these products in a&               distributed environment.  F               The Part List, found in the transparent plastic envelopeD               in your kit, specifies the number and contents of yourD               media. Be sure to verify the contents of your kit with@               this information. If your kit is damaged or if youD               find that parts of it are missing, contact your Compaq               representative.            1.1 Types of ACMS Kits  8               ACMS is available in three different kits:  %               o  ACMS Development Kit-  D                  This kit provides all the features of ACMS. You canC                  define, build, and debug multiple-step tasks, task H                  groups, menus and applications, as well as use the ACMSF                  task queuing facilities. You can use DECforms or TDMSF                  as standard presentation services, or use the RequestD                  Interface (RI) and Systems Interface (SI) to accessC                  other presentation services. You are provided with.I                  samples of ACMS applications using standard presentationo4                  services and the Request Interface.  H                  The development kit also includes the features provided8                  by the run-time and remote-access kits.  "               o  ACMS Run-Time Kit  D                  This kit allows you to use existing applications orC                  programs under the control of ACMS. It also allowsiB                  you to define and debug menus, applications, taskD                  groups, and single-step tasks that use DCL servers,  I                                        Planning the ACMS Installation 1-1. .  .      "     Planning the ACMS Installation     1.1 Types of ACMS Kits    D              if Oracle CDD is present when this kit is installed. ItC              allows ACMS users to sign in and select tasks that are C              implemented on the local node as well as remote nodes..D              The run-time kit allows you to use the ACMS Queued TaskE              Initiator (QTI) to submit tasks to run on the local node.%              as well as remote nodes.   D              The run-time kit also includes the features provided by#              the remote-access kit.l  #           o  ACMS Remote-Access Kit   D              This kit is suitable for installation on a network node@              that does not have any ACMS applications running onD              it, but requires access to ACMS applications running onE              another network node. The remote-access kit allows users E              to sign in to ACMS and select tasks on remote nodes, and-B              handles the terminal I/O associated with those tasks.D              The remote access kit allows you to use the ACMS QTI to1              submit tasks to run on remote nodes.a       1.2 ACMS Licenses   D           Each ACMS kit has an unlimited-use ACMS license associatedC           with it. Table 1-1 shows the licenses that are applicablel           to each ACMS kit.   E           Table_1-1_ACMS_Licenses____________________________________   )                                 UnlimitedmE           ACMS_Kit______________Use___________Concurrent_Use_________   ;           Development System    ACMS          Not available   :           Run-Time Option       ACMS-RT       ACMS-RT-USER  E           Remote-Access_Option__ACMS-REM______ACMS-REM-USER__________   B           For more information about these ACMS licenses, refer to8           Compaq ACMS for OpenVMS Managing Applications.  C           To install an ACMS Version 4.4 kit, you must register and B           load an ACMS software license, using the OpenVMS LicenseD           Management Facility (LMF). You must register and load your;           ACMS license before you perform the installation.   C           For more information on registering and loading your ACMSf'           license, refer to Appendix B.   &     1-2 Planning the ACMS Installation ,  u      I                                            Planning the ACMS InstallationtI                                  1.3 Required Operating System Components     0         1.3 Required Operating System Components  H               Compaq ACMS for OpenVMS Alpha Version 4.4 requires OpenVMS0               Alpha Version 6.2,  7.2-1, or 7.3.  F               Compaq ACMS for OpenVMS VAX Version 4.4 requires OpenVMS,               VAX Version 6.2,  7.2, or 7.3.  H               For distributed processing with ACMS, you must have DECnet!               software installed.   F                 ________________________ Note ________________________  B                 If you install ACMS Version 4.4 on an Alpha systemE                 running a version of OpenVMS Alpha lower than OpenVMS F                 Alpha Version 7.x, you must reinstall ACMS Version 4.4?                 after you upgrade to OpenVMS Alpha Version 7.x.   F                 ______________________________________________________  (         1.4 Layered Product Requirements  A               The ACMS Version 4.4 installation procedure and IVP F               interact with a number of OpenVMS layered products. SomeH               of these products are required, while others are optional.  I               Each of these layered products has a minimum version (based.I               on the OpenVMS version) that is supported with ACMS VersioneD               4.4. The ACMS Version 4.4 Software Product DescriptionC               (SPD) identifies the minimum layered product versionsoG               required to successfully install ACMS Version 4.4 and run                the IVP.  I               If a product is required, you must make the minimum versionxD               available before you can install ACMS. If a product isG               not required, you do not need to make it available beforenB               installing ACMS, however, you must upgrade it to theA               minimum required version before using it with ACMS.t  2         1.4.1 Determining Software Version Numbers  D               Before installing ACMS Version 4.4, identify the otherH               products that you need to upgrade. The ACMS SPD contains aI               complete list of the products that are compatible with thisuF               version of ACMS, including information about the minimumH               version of OpenVMS and layered products that interact with               ACMS Version 4.4.s  I                                        Planning the ACMS Installation 1-3o a  n      "     Planning the ACMS Installation$     1.4 Layered Product Requirements    C           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  1           SEARCH ACMS_VERSION.TMP "image file id"   @           In the ANALYZE/IMAGE command, substitute for file-nameA           the file name listed in Table 1-2 or Table 1-3 for eachA           product.  E           Table_1-2_Compatible_Products_Image_Files_for_OpenVMS_Alphas  E           Product___________File_Name________________________________r  9           DECforms          SYS$LIBRARY:FORMS$MANAGER.EXE   1           LSE (DECset)      SYS$SYSTEM:LSEDIT.EXEC  2           Oracle CDD        SYS$LIBRARY:CDDSHR.EXE  2           Oracle CODASYL    SYS$LIBRARY:DBMSHR.EXE           DBMS  2           Oracle Rdb        SYS$LIBRARY:RDBSHR.EXE  8           Oracle Trace      SYS$LIBRARY:EPC$FUNCSHRP.EXE  8           TP Desktop        SYS$SYSTEM:ACMSDI$SERVER.EXEE           Connector__________________________________________________   E           Table_1-3_Compatible_Products_Image_Files_for_OpenVMS_VAX__t  E           Product___________File_Name________________________________h  9           DECforms          SYS$LIBRARY:FORMS$MANAGER.EXE,  1           LSE (DECset)      SYS$SYSTEM:LSEDIT.EXE   2           Oracle CDD        SYS$LIBRARY:CDDSHR.EXE  2           Oracle CODASYL    SYS$LIBRARY:DBMSHR.EXE           DBMS  2           Oracle Rdb        SYS$LIBRARY:RDBSHR.EXE  8           Oracle Trace      SYS$LIBRARY:EPC$FUNCSHRP.EXE  2           TDMS              SYS$LIBRARY:TSSSHR.EXE  E                                              (continued on next page)   &     1-4 Planning the ACMS Installation e  r      I                                            Planning the ACMS Installation I                                          1.4 Layered Product RequirementsT    C               Table 1-3 (Cont.) Compatible Products Image Files foraI               __________________OpenVMS_VAX______________________________,  I               Product___________File_Name________________________________o  <               TP Desktop        SYS$SYSTEM:ACMSDI$SERVER.EXEI               Connector__________________________________________________h  F               The line that OpenVMS displays in response to the SEARCHC               command shows the current version of the product. The E               following example shows that the system has LSE Versionc               4.2 installed:  L               $ ANALYZE/IMAGE SYS$SYSTEM:LSEDIT.EXE /OUTPUT=ACMS_VERSION.TMP7               $ SEARCH ACMS_VERSION.TMP "image file id"uJ                                image file identification: "LSEDIT V4.2-17"  )         1.4.2 Requirements for Oracle CDDn  D               Oracle CDD/Repository Version 7.0 is supported by ACMS               Version 4.4.  C               The following paragraphs discuss the requirements for F               Oracle CDD when installing the different ACMS kit types.  F               If you are installing the ACMS development kit, at leastF               the minimum version of CDD as identified in the ACMS SPDG               must be installed on your system. If CDD is not installednB               or if a lower version of CDD is installed, VMSINSTAL4               terminates the installation procedure.  A               If you are installing the ACMS run-time kit, CDD isrG               optional; however, the minimum version of CDD is required H               for the run-time kit to be fully functional. Specifically,F               if you install the ACMS run-time kit with CDD available,B               you can create new applications and menus and modifyD               existing applications and menus, on your ACMS run-timeF               system. If you install the ACMS run-time kit without CDDC               available, you can use only existing applications andaH               menus; you cannot create new ones on your run-time system.I               If you subsequently install CDD, you can make the ACMS run- E               time CDD-related features available by reinstalling the H               ACMS Version 4.4 run-time kit and choosing the CDD-related@               files option at the beginning of the installation.  F               If you are installing the ACMS remote-access kit, CDD is               not required.e  I                                        Planning the ACMS Installation 1-5a x  l      "     Planning the ACMS Installation$     1.4 Layered Product Requirements         1.4.3 Requirements for LSE  B           LSE is an optional layered product for all ACMS kits. IfC           the minimum version (or a higher, allowed version) of LSEsA           as identified in the ACMS SPD is not available when you B           install ACMS, LSE templates for ACMS Version 4.4 are notC           provided on your system. If you subsequently install LSE, C           you can make the ACMS Version 4.4 LSE templates available C           by reinstalling the ACMS Version 4.4 kit and choosing the A           LSE update option at the beginning of the installation.   /     1.4.4 Requirements for TP Desktop Connector   @           Compaq TP Desktop Connector for OpenVMS is an optionalD           layered product for ACMS. If you are installing TP DesktopD           Connector on a system with ACMS Version 4.0 or higher, youB           must have at least the minimum version of the TP Desktop2           Connector as identified in the ACMS SPD.  E           If the ACMS installation runs while TP Desktop Connector is C           running, the results are unpredictable. Use the followingnD           command to shut down TP Desktop Connector before you begin"           an installation of ACMS:  ,           $ @SYS$STARTUP:ACMSDI$SHUTDOWN.COM  3     1.4.5 Recommended Order for Installing Software   A           To ensure problem-free installation of software on your B           system, install the OpenVMS operating system and layered*           products in the following order:             1. OpenVMS             2. LSE             3. Oracle Rdb              4. Oracle Traceo             5. Oracle CDDe              6. Oracle CODASYL DBMS             7. TDMS (VAX only)             8. DECformsr             9. ACMSa  !          10. TP Desktop Connector   &     1-6 Planning the ACMS Installation    s      I                                            Planning the ACMS Installation:I                            1.5 Upgrading Software in a Distributed System     6         1.5 Upgrading Software in a Distributed System  H               Upgrading software in a distributed transaction processingE               system is complex because of the dependencies among themF               software products. The process becomes even more complexB               when you take into account the dependencies that areG               created from multiple versions that exist for each of the +               individual software products.a  C               Because you cannot upgrade all nodes in a distributed I               environment simultaneously, and because the upgrade processRF               might last several days, a clear methodology is requiredF               to ensure smooth and timely introduction of new software               versions.   "         1.5.1 Configuration Issues  I               A simple, distributed configuration in a TP system consistsOF               of an ACMS front-end node and an ACMS back-end node. YouC               can configure ACMS on each node for the processing of_I               specific tasks. Likewise, the roles of the layered products_G               on each node are distinct. For simple configurations, thea1               upgrade process is straightforward:   =               1. Upgrade the software on the front-end nodes.   <               2. Upgrade the software on the back-end nodes.  F               Upgrading in this order ensures that the system deliversH               the same version of software to the front-end node and the               back-end node.  >               However, this simple rule cannot be applied to aC               configuration in which a node is both a front end ande@               a back end. To successfully upgrade a more complex8               configuration, apply these two key points:  D               o  A component built by a previous software version isF                  compatible with the upgraded version of the software.  @                  For example, DECforms Version 1.4 can execute aB                  form created by DECforms Version 1.3, without anyF                  modification. You can also copy this component from aE                  node on which DECforms Version 1.3 is installed to asI                  node with DECforms Version 1.4. The DECforms Version 1.3aG                  form executes correctly, as long as you do not rebuilds,                  the form using Version 1.4.  I                                        Planning the ACMS Installation 1-7            "     Planning the ACMS Installation2     1.5 Upgrading Software in a Distributed System    >           o  Do not rebuild a component under the new software@              version until you upgrade all nodes to which it may!              possibly be shipped.   C           To upgrade software in a distributed system, follow theseo           steps:  >           1. Upgrade all software on the front-end-only nodes.  B           2. Upgrade all software on nodes that are both front-end               and back-end nodes.  9           3. Upgrade all software on back-end-only nodes.o  C              ________________________ Note ________________________e  ;              Do not modify by recompilation any applicationn<              components (unless required by the installation<              procedure) until you upgrade all the nodes that1              compose the distributed application.   C              ______________________________________________________i       1.6 Product Dependencies  @           Keep in mind the following dependencies when upgrading<           software, especially in a distributed environment:             o  ACMS   D              ACMS copies DECforms forms (.FORM) and shareable images@              (.EXE), TDMS request library files (.RLB), and ACMS?              application database files (.ADB) from back-end to,C              front-end nodes, if the versions or dates of the filess-              on the back end are more recent.D             o  Oracle CDDn  <              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 ofC              module recompilation. However, do not recompile or add 4              features until the upgrade is complete.             o  DECformsg  <              See the DECforms SPD for DECforms dependencies.  &     1-8 Planning the ACMS Installation t  e      I                                            Planning the ACMS InstallationpI                                                  1.6 Product Dependenciesn    /               o  OpenVMS Alpha operating systemn  C                  When upgrading major versions of the OpenVMS Alpha H                  operating system, you must reinstall ACMS. This appliesG                  when upgrading the OpenVMS Alpha operating system frome,                  Version 6.x to Version 7.x.  E                  It is not necessary to reinstall ACMS on OpenVMS VAX I                  systems that have been upgraded from OpenVMS VAX Version $                  6.x to Version 7.x.  $               o  Oracle CODASYL DBMS  C                  Remote access between different versions of Oracle D                  CODASYL DBMS is possible as long as features uniqueE                  to the newer version are not requested of a previousn                  version.                  o  Oracle Rdbe  B                  Rdb modules are upwardly compatible; for example,I                  modules compiled under Rdb Version 6.0 execute correctly H                  if Rdb is upgraded to Version 7.0 on the system. RemoteE                  access between different versions of Rdb is possiblelH                  as long as features unique to the newer version are not3                  requested of the previous version.A  A                  Because Rdb is the base data repository for manyiA                  products, particularly CDD and Oracle Trace in aeD                  transaction processing system, you must convert allI                  databases (RMU/CONVERT) used by these products after you G                  upgrade Rdb. Refer to the product-specific information "                  for more details.                        I                                        Planning the ACMS Installation 1-9c _  i      "     Planning the ACMS Installation     1.6 Product Dependencies               o  Oracle Trace   E              Oracle Trace depends on Oracle Rdb since it provides the C              base data repository, as mentioned above. Refer to the ;              product-specific information for more details.e  '           o  Pascal and PL/I (VAX only)m  =              Changes were made to the Pascal and PL/I includefB              files after ACMS Version 3.1. Some changes may not beD              compatible with existing programs. If you are upgradingC              from ACMS Version 3.1, save a copy of the ACMS Version >              3.1 definition files, SYS$LIBRARY:ACMSPLI.TLB andD              SYS$LIBRARY:ACMSPAS.PAS, before installing ACMS VersionB              4.4, and use these files until you make the necessary:              modifications to use the correct definitions.             o  TDMS (VAX only)  B              TDMS request libraries generated since the release ofD              TDMS Version 1.7 are compatible with all later versions              of TDMS.                                               '     1-10 Planning the ACMS Installationd                         I                                                                         2iI         _________________________________________________________________o  I                                                 Preparing to Install ACMSu    F               This chapter discusses the preparations and requirements8               necessary for installing ACMS Version 4.4.  B               ACMS provides online release notes and gives you theG               option of printing or displaying the release notes during D               the installation procedure. Compaq strongly recommendsD               that you read the release notes before proceeding withB               the installation in case they contain some important?               information regarding the installation procedure.h  E               The sections in this chapter describe requirements that.B               are checked by the ACMS installation procedure. WithE               the exception of optional layered products, your systemyF               must meet these requirements before you can install ACMS               successfully.   '         2.1 Backing Up Your System Disk   B               At the beginning of the installation, VMSINSTAL asksA               whether you have backed up your system disk. Compaq A               recommends that you back up your system disk before &               installing any software.  E               Use the backup procedures that have been established atmI               your site to do this backup. For details about performing arG               system disk backup, see the section on the Backup Utilitya/               in the OpenVMS documentation set.t           2.2 Software Versions   D               As discussed in Section 1.4, ACMS Version 4.4 requiresC               minimum versions of a number of layered products. The G               installation procedure lists all layered products that doPG               not meet or exceed the required minimum version. The ACMSnG               Software Product Description (SPD) identifies the minimumtB               software versions of required and optional products.  I                                             Preparing to Install ACMS 2-1  N  Z           Preparing to Install ACMSN     2.2 Software VersionsM    A           If any required products are below minimum version, thed           installation fails.        2.2.1 Installed Images  ;           In order to use other layered products during the A           installation of ACMS, certain executable images related C           to those products must be installed using the DCL command C           INSTALL. These images are normally installed by executing >           the startup procedure for the product. These startupE           procedures should be executed automatically when the systemIB           is started. Startup procedures are found in SYS$STARTUP.  A           To determine whether an image is installed, execute theC            following DCL command:  +           $ INSTALL LIST file-specificationo  D           If an image is not installed, you must execute the relatedB           product startup procedure; also ensure that this startupD           procedure is executed automatically during system startup.  A           If you are installing the ACMS development kit, the CDD @           image SYS$LIBRARY:CDDSHR.EXE must be installed. If youA           are installing the ACMS run-time kit, this is optional;IC           however, if the image is not installed, CDD-related filesIB           will not be made available. The CDD startup procedure is           CDDSTRTUP.COM.  C           To use CDD, Rdb must also be available. Therefore, if you D           are installing the ACMS development kit, or if you plan toD           use the CDD-related function of the ACMS run-time kit, theE           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_9           during the installation, the Oracle Trace image_D           SYS$LIBRARY:EPC$FUNCSHRP.EXE must be installed. The Oracle5           Trace startup procedure is EPC$STARTUP.COM._          !     2-2 Preparing to Install ACMS            I                                                 Preparing to Install ACMSmI                                                            2.3 Privileges              2.3 Privileges  B               To install ACMS, you must be logged in to the SYSTEMB               account, or any account with similar privileges. TheD               SYSTEM account has all the privileges required for the               installation.i  H               Table 2-1 lists the privileges required to execute various(               steps of the installation.  I               Table_2-1_Privilege_Requirements___________________________l  I               Step____________________Required_Privileges________________   ,               Installation procedure  BYPASS  E               Postinstallation        BYPASS, SYSPRV, SYSNAM, CMEXEC, *               procedure               OPER  B               Installation            OPER, SYSPRV, SYSNAM, CMKRNLI               Verification_Procedure_____________________________________t           2.4 Disk Space  H               The following sections describe the approximate disk spaceC               requirements for a normal installation, and an optioneE               for installing ACMS on a system disk with limited spacei               available.  2         2.4.1 Disk Space for a Normal Installation  G               Installing ACMS requires a certain amount of free storageiD               space during the installation. Once ACMS is installed,E               less storage space is required. Table 2-2 and Table 2-3AE               summarize the approximate storage requirements for ACMS E               during and after installation. These tables reflect theoC               installation of full kits, with all options selected.l  I               Table_2-2_Disk_Space_Requirements_for_OpenVMS_Alpha_by_Kit_v  F                                          Blocks During    Blocks AfterI               Kit________________________Installation_____Installation___f  @               Development                70,000           42,000  @               Run-time                   38,000           33,000  I               Remote-access______________27,000___________24,000_________   I                                             Preparing to Install ACMS 2-3     .           Preparing to Install ACMS      2.4 Disk Space    E           Table_2-3_Disk_Space_Requirements_for_OpenVMS_VAX_by_Kit___i  B                                      Blocks During    Blocks AfterE           Kit________________________Installation_____Installation___   <           Development                43,000           30,000  <           Run-time                   28,000           25,000  E           Remote-access______________21,000___________18,000_________V  E           If you are installing only some parts of the ACMS kits, younB           need less disk space for the installation. Table 2-4 andE           Table 2-5 list the approximate amount of space required forp3           each optional component of the ACMS kits.e  @           Table 2-4 Disk Space Requirements for OpenVMS Alpha byE           __________Component________________________________________i  B                                      Blocks During    Blocks AfterE           Component__________________Installation_____Installation___r  <           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,500r  ;           ACMS Request Interface     6,000            3,900e           samplesf  ;           CDD-related files          6,000            5,500   9           LSE-related files          6,200            600:E           [1]Includes_CDD-related_files______________________________   E           ___________________________________________________________.  >           Table 2-5 Disk Space Requirements for OpenVMS VAX byE           __________Component________________________________________   B                                      Blocks During    Blocks AfterE           Component__________________Installation_____Installation___   <           Development software[1]    30,000           17,200  E           [1]Includes_CDD-related_files______________________________   E                                              (continued on next page)   !     2-4 Preparing to Install ACMSe p  e      I                                                 Preparing to Install ACMScI                                                            2.4 Disk Space     G               Table 2-5 (Cont.) Disk Space Requirements for OpenVMS VAX I               __________________by_Component_____________________________t  F                                          Blocks During    Blocks AfterI               Component__________________Installation_____Installation___y  @               Run-time software          21,000           12,600  @               Remote-access software     18,000           11,000  ?               ACMS samples               1,900            1,300i  ?               ACMS Request Interface     2,900            2,700C               samplesn  ?               CDD-related files          6,000            3,600n  I               LSE-related_files__________600______________100____________   H               To determine the number of free disk blocks on your system0               disk, enter the following command:  )               $ SHOW DEVICE SYS$SYSDEVICEU  5         2.4.2 Installing on a Disk with Limited Space   B               If your system disk has less space than indicated inI               Section 2.4.1, and if you have previously installed ACMS onaG               your system disk, you may be able to install ACMS VersioneG               4.4 by using the VMSINSTAL Alternate Working Device (AWD)a               option.r  I               The AWD option allows you to specify another disk device onsF               which VMSINSTAL creates its temporary working directory.  ?               For a normal Compaq ACMS for OpenVMS, Version 4.4vA               development kit installation, VMSINSTAL creates thea4               following temporary working directory:  0               SYS$SPECIFIC:[SYSUPD.ACMSDEVA_044]  D               For an AWD installation of the same kit, the VMSINSTAL-               temporary working directory is:n  <               alternate-working-device:[000000.ACMSDEVA_044]  A               The space required during installation indicated inTF               Section 2.4.1 must be available on the alternate workingB               device; this space will be available again after theD               installation is complete. You must still have at leastE               5000 blocks available on the system disk to use the AWD                option.   I                                             Preparing to Install ACMS 2-5  t  e           Preparing to Install ACMSa     2.4 Disk Space    C              ________________________ Note ________________________w  C              The AWD installation assumes that the ACMS Version 4.4 A              is no more than 5000 blocks larger than the ACMS kit 0              currently installed on your system.  <              If the AWD installation does not work, you must@              make the required disk space available for a normal1              installation before installing ACMS.   C              ______________________________________________________c  D           To determine the number of free disk blocks on your systemB           disk and alternate working device, execute the following           commands:   %           $ SHOW DEVICE SYS$SYSDEVICE_0           $ SHOW DEVICE alternate-working-device       2.5 Disk Quotas   A           If disk quotas are enabled on the system disk, the ACMSt>           Installation Verification Procedure (IVP) fails. TheC           ACMS installation procedure normally schedules the IVP to D           execute automatically after the installation is completed.?           However, if disk quotas are enabled, the installationtD           procedure cancels the IVP and notifies you. You can chooseE           to stop the installation and address the issue, or continuelB           the installation and execute the IVP manually at a later           time.e  C           To determine whether disk quotas are enabled, execute thet            following DCL command:  )           $ SHOW QUOTA/DISK=SYS$SYSDEVICEd       2.6 System Parameterse  B           Table 2-6 and Table 2-7 list the minimum required systemA           parameter values for the installation. Depending on the B           kinds of programs and applications running at your site,9           you might need higher values for some settings.       !     2-6 Preparing to Install ACMSD o         I                                                 Preparing to Install ACMS I                                                     2.6 System Parameterst    D               Table 2-6 Required System Parameter Values for OpenVMSI               __________Alpha____________________________________________   I               System_Parameter______Value________________________________e  '               CLISYMTBL[1]          500s  -               GBLPAGES[2]           n + 6,000n  )               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,000I               [1]The_CLISYMTBL_dynamic_system_parameter_must_be_set_to___   D               a minimum value of 500 during the installation. If theD               CLISYMTBL setting is set to a value less than 500, youI               must reset the value to 500 or more before installing ACMS. F               You can lower the setting to its original value once the'               installation is finished.tE               [2]The n variable refers to the system parameter values G               that are currently in use. To install ACMS, the allocated H               system parameter value must be less than the sum of n plusG               the number indicated. The numbers indicated represent the F               unused portion of these parameters. (See Section 2.6.2.)H               [3]These dynamic system parameters must be set permanentlyF               to values equal to or greater than the values listed. Do<               not lower these values after the installation.I               ___________________________________________________________               I                                             Preparing to Install ACMS 2-7     a           Preparing to Install ACMS      2.6 System ParametersA    E           Table_2-7_Required_System_Parameter_Values_for_OpenVMS_VAX_c  E           System_Parameter______Value________________________________h  #           CLISYMTBL[1]          500a  )           GBLPAGES[2]           n + 3,500   %           GBLPAGFIL             2,048t  &           GBLSECTIONS[2]        n + 55  "           PQL_DASTLM[3]         20  "           PQL_DBIOLM[3]         12  "           PQL_DDIOLM[3]         20  "           PQL_MDIOLM[3]         20  &           VIRTUALPAGECNT        19,000E           [1]The_CLISYMTBL_dynamic_system_parameter_must_be_set_to___t  @           a minimum value of 500 during the installation. If the@           CLISYMTBL setting is set to a value less than 500, youE           must reset the value to 500 or more before installing ACMS.tB           You can lower the setting to its original value once the#           installation is finished. A           [2]The n variable refers to the system parameter valuesfC           that are currently in use. To install ACMS, the allocatedsD           system parameter value must be less than the sum of n plusC           the number indicated. The numbers indicated represent the B           unused portion of these parameters. (See Section 2.6.2.)D           [3]These dynamic system parameters must be set permanentlyB           to values equal to or greater than the values listed. Do8           not lower these values after the installation.E           ___________________________________________________________   =           The following sections describe how to check systemeA           parameter values, calculate values for the GBLPAGES ando@           GBLSECTIONS system parameters, change parameter valuesA           with the OpenVMS AUTOGEN command procedure, and set therD           CLISYMTBL dynamic system parameter with the OpenVMS System&           Generation Utility (SYSGEN).  !     2-8 Preparing to Install ACMSn h  n      I                                                 Preparing to Install ACMSuI                                                     2.6 System Parameterse    .         2.6.1 Checking System Parameter Values  F               To check the values of your system parameters, enter theC               following command at the DCL prompt to invoke SYSGEN:   %               $ RUN SYS$SYSTEM:SYSGEN                SYSGEN>   F               At the SYSGEN> prompt, enter the SHOW command to display@               the value of each system parameter. Make sure thatD               the values displayed equal or exceed the value of eachG               parameter listed in Table 2-6 or Table 2-7. The following F               command displays the value for the VIRTUALPAGECNT system               parameter:  )               SYSGEN> SHOW VIRTUALPAGECNTlT               Parameter Name       Current   Default    Min.    Max.   Unit  DynamicT               --------------       -------   -------   ------  ------  ----  -------L               VIRTUALPAGECNT        270144      9216    512    1200000 Pages  ;               This example shows that the current value for '               VIRTUALPAGECNT is 270144.i  D               After you finish checking the parameters with the SHOWF               command, enter the EXIT command at the SYSGEN> prompt to"               return to DCL level.  A         2.6.2 Calculating the Values for GBLPAGES and GBLSECTIONSZ  F               To install and run ACMS, you must set the correct valuesA               for the GBLPAGES and GBLSECTIONS system parameters.   F               The values for GBLPAGES and GBLSECTIONS in Table 2-6 andF               Table 2-7 (excluding the value of n) indicate the numberD               of unused pages or sections you must have available onG               your system for the installation to process successfully.aF               To calculate whether your system has a sufficient numberE               of unused global pages and global sections, perform thee               following steps:  G               1. Show the current free global pages and global sections 2                  using the following DCL commands:  =                  $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES")L                  3420o=                  $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS")t                  72   I                                             Preparing to Install ACMS 2-9  e  u           Preparing to Install ACMSu     2.6 System Parametersi    =           2. Determine if the number of unused pages (3420 inI@              the example) is equal to or greater than the number?              specified in Table 2-6 or Table 2-7. If the numberiB              of unused pages is less than the number listed in the?              table, increase the allocation value for GBLPAGES.R  B           3. Determine if the number of unused global sections (72C              in the example) is equal to or greater than the numberyA              specified in Table 2-6 or Table 2-7. If the value istC              less than the number required, increase the allocationa0              value of the GBLSECTIONS parameter.  ?           Section 2.6.3 describes the procedures for increasingrC           these values as well as those of other system parameters._E           Refer to the OpenVMS documentation on system management and *           operations for more information.  7     2.6.3 Changing System Parameter Values with AUTOGENA  <           Use the AUTOGEN command procedure to change systemC           parameters. To change system parameters with AUTOGEN, youI'           must edit the following file:   "           SYS$SYSTEM:MODPARAMS.DAT  D           For example, to change the setting for the GBLPAGES system/           parameter, add this line to the file:              GBLPAGES = 100000m  C           Now, run the AUTOGEN procedure to recalculate your systemeD           parameters. Enter the following command at the DCL prompt:  ;           $@SYS$UPDATE:AUTOGEN SAVPARAMS SETPARAMS FEEDBACK   ;           For more information about using AUTOGEN, see thevD           instructions on modifying system parameters in the OpenVMS<           documentation on system management and operations.  8     2.6.4 Setting the CLISYMTBL Dynamic System Parameter  D           If the CLISYMTBL system parameter value for your system isE           less than 500, change the setting by entering the followingR           series of commands:   "     2-10 Preparing to Install ACMS _  _      I                                                 Preparing to Install ACMSeI                                                     2.6 System Parametersa    %               $ RUN SYS$SYSTEM:SYSGEN                 SYSGEN> USE ACTIVE'               SYSGEN> SET CLISYMTBL 500 "               SYSGEN> WRITE ACTIVE               SYSGEN> EXIT  D               CLISYMTBL is a dynamic parameter, which means that youF               do not have to reboot the system to make the change takeH               effect. The new value for CLISYMTBL becomes effective when8               you enter the SYSGEN command WRITE ACTIVE.  D               If you do nothing further, the new value for CLISYMTBLB               remains in effect until the next time you reboot theB               system, at which time the old value for CLISYMTBL is               restored.K  D               If you want to make the new CLISYMTBL value permanent,1               enter the following SYSGEN command:s  #               SYSGEN> WRITE CURRENT   @               The WRITE CURRENT command writes the new value forD               CLISYMTBL into the SYSGEN database on disk, so that it7               is available when the system is rebooted._  ?               To exit from SYSGEN, enter the following command:o                 SYSGEN> EXIT  F                 ________________________ Note ________________________  F                 If you changed the value of CLISYMTBL, log out and log>                 back in so that the new value can take effect.  F                 ______________________________________________________  "         2.7 Process Account Quotas  F               The account you use to install ACMS must have sufficientI               quotas to enable you to perform the installation. Table 2-8VC               summarizes the process quotas required to perform the                installation.k      I                                            Preparing to Install ACMS 2-11a a  n           Preparing to Install ACMSa     2.7 Process Account Quotas    E           Table_2-8_Process_Account_Quotas___________________________y  E           Account_Quota_________Required_Value_______________________   "           ASTLM                 24  "           BIOLM                 18  &           BYTLM                 32,768  "           DIOLM                 18  %           ENQLM                 2,000   #           FILLM                 200   "           PRCLM                 10  E           PGFLQUO_______________12,800_______________________________S  D           User account quotas are stored in the file SYSUAF.DAT. UseA           the OpenVMS Authorize Utility (AUTHORIZE) to verify and A           change user account quotas. First set your directory to ,           SYS$SYSTEM and then run AUTHORIZE:  "           $ SET DEFAULT SYS$SYSTEM           $ RUN AUTHORIZE_           UAF>  E           At the AUTHORIZE prompt (UAF>), enter the SHOW command with E           an account name to check a particular account. For example:_             UAF> SHOW SYSTEM  A           To change a quota, enter the MODIFY command at the UAF>B2           prompt. MODIFY has the following format:  -           MODIFY account-name/quota-name=nnnn   ?           The following example changes the FILLM quota for the C           SYSTEM account and then exits from the Authorize Utility:   &           UAF> MODIFY SYSTEM/FILLM=200           UAF> EXITx  =           After you exit from the utility, the OpenVMS system B           displays messages indicating whether or not changes wereE           made. Once the changes have been made, you must log out and 9           log in again for the new quotas to take effect.i  ?           For more information on modifying account quotas, seeeA           the description of the Authorize Utility in the OpenVMS <           documentation on system management and operations.  "     2-12 Preparing to Install ACMS l  i      I                                                 Preparing to Install ACMS I                                        2.8 Time Required for Installation     *         2.8 Time Required for Installation  ?               Table 2-9 lists the approximate time required for,'               installing each ACMS kit.   F                 ________________________ Note ________________________  A                 Installation time depends heavily on installation B                 options, system load, hardware, and kit media. The@                 times listed in Table 2-9 were measured for fullE                 installations on a standalone DEC 3000 (Alpha) systemi<                 with disk-resident kits. Your time may vary.  F                 ______________________________________________________  I               Table_2-9_Timetable_for_Installing_ACMS____________________s  +                                InstallationtI               Kit______________Time[1]__________IVP_Time_________________   9               Development      7 minutes        2 minutese  9               Run-time         4 minutes        2 minutes   8               Remote-access    2 minutes        1 minuteI               [1]If_you_are_using_the_VMSINSTAL_option_AWD,_multiply_____I                 these times by 3.oI               ___________________________________________________________A  '         2.9 ACMS$IVP User Authorizations  B               The ACMS installation checks for the presence of theE               OpenVMS user account ACMS$IVP. If this account does notMG               exist, you are asked for information needed to create it.tG               The ACMS$IVP account is used to run the ACMS Installationr%               Verification Procedure.w  A               Among the information requested for this account iseA               a unique user identification code (UIC) in the formlG               [ggggg,nnnnnn], where ggggg is an octal user group number I               in the range 1-37776, and nnnnnn is an octal user number in G               the range 1-177776. Additionally, the group number cannot_'               be a system group number._  I                                            Preparing to Install ACMS 2-13o .              Preparing to Install ACMSc#     2.9 ACMS$IVP User Authorization     D           Enter the following commands to list the UICs currently in           use on your system:              $ MCR AUTHORIZEd           UAF> LIST * /BRIEF  A           The result of these commands is that all UICs in use on @           your system are listed in the file SYSUAF.LIS, in yourA           default directory. You can then examine this listing to :           determine a unique UIC for the ACMS$IVP account.  C           On your system, a certain range of group numbers has been E           reserved for system users. To determine this range, execute !           the following commands:l  ,           $ 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 ofA           the symbol MAXSYS. The following example shows that thebA           maximum system group number is octal 10; therefore, youiE           must specify a group number for the ACMS$IVP UIC that is ins           the range 11-37776:   ,           $ MAXSYS = F$GETSYI("MAXSYSGROUP")           $ SHOW SYMBOL MAXSYS=             MAXSYS = 8   Hex = 00000008   Octal = 00000000010t                                  "     2-14 Preparing to Install ACMS Y  Y                    I                                                                         3qI         _________________________________________________________________   I                                                           Installing ACMS     F               This chapter describes how to install the ACMS software.D               Section 3.2 contains a step-by-step description of the%               installation procedure.            3.1 Installation Log  G               A log of your installation is kept in the following file:e  9               SYS$COMMON:[SYSUPD]ACMS044_INSTALLATION.LOG_  C               In particular, if the ACMS installation fails because E               prerequisites were not met, this log contains a list of D               those prerequisites. You can use it as a check list of9               items to address before you reinstall ACMS.   F               In addition, after the installation is completed, a listG               of the files created by the installation is stored in the                following file:   2               SYS$COMMON:[SYSEXE]ACMS044_FILES.DAT  "         3.2 Installation Procedure  G               ACMS provides online release notes. The prompt to display H               or print the release notes before the installation appearsI               in the installation procedure, if you invoke VMSINSTAL withtG               the OPTIONS N parameter. For information on accessing theoI               release notes after the installation, refer to Section 3.4.l  H               The ACMS installation process is divided into five phases:  C               o  The first phase consists of invoking VMSINSTAL andCD                  supplying information such as which kit to install,G                  where the kit resides, and other installation options.n8                  Section 3.2.1 explains the first phase.  I                                                       Installing ACMS 3-1a e  s           Installing ACMS      3.2 Installation Procedure    @           o  The second phase consists of a series of questions,@              checks, and informational messages related to ACMS.A              This phase ensures that the installation environment B              is sufficient to support the actual installation workB              that occurs in the third phase. The second phase ends@              when you are shown a summary of what happens in theD              third phase and are asked whether you want to continue.=              Chapter 2 has information to help you answer the A              questions asked in the second phase; if you have not D              read Chapter 2 in preparation for this installation, doE              so now. Section 3.2.2 takes you step by step through theQ.              second phase of the installation.  B           o  The third phase is the actual installation work. This?              usually includes restoring kit savesets, providing D              files to system directories, creating the ACMS$IVP userE              account, updating the LSE and Oracle Trace environments,rD              updating DCL tables and help libraries, and other stepsB              as enumerated at the end of the second phase. No userE              interaction is required during this phase. Section 3.2.3mA              explains the messages that you might see during this               phase.   E           o  The fourth phase is the ACMS postinstallation procedure. ?              This procedure, which executes automatically after A              the ACMS software is installed, performs the minimum E              system management operations that are necessary to allow D              ACMS to be used on the system. Section 3.2.4 guides you0              through the postinstallation phase.  B           o  The fifth phase is the ACMS Installation VerificationA              Procedure (IVP). This procedure performs a series ofe@              exercises to ensure that ACMS is properly installedC              and usable on your system. Section 3.2.5 discusses thes"              execution of the IVP.  @           To abort the installation procedure at any time, press=           <Ctrl/Y>. When you press <Ctrl/Y>, the installationyE           procedure deletes all files it has created up to that point ?           and exits. You can then start the installation again.u               3-2 Installing ACMS            I                                                           Installing ACMSuI                                                3.2 Installation Proceduree    .         3.2.1 Invoking VMSINSTAL (First Phase)  F               To start the installation, log in to the SYSTEM account,:               and set default to the SYS$UPDATE directory:                 Username: SYSTEM               Password:y&               $ SET DEFAULT SYS$UPDATE  H               Next, invoke VMSINSTAL. Use the following syntax to invoke               VMSINSTAL:  B               @VMSINSTAL product-name device-name [OPTIONS option-         1[,...]]                 product-nameG               The installation name for the component. Enter one of the                following:  ?               o  ACMSDEVA_044 - if you are installing the Alpha-!                  development kit.-  H               o  ACMSRTOA_044 - if you are installing the Alpha run-time                  kit.P  G               o  ACMSREMA_044 - if you are installing the Alpha remote-                   access kit.  I               o  ACMSDEVV_044 - if you are installing the VAX development                   kit.e  F               o  ACMSRTOV_044 - if you are installing the VAX run-time                  kit..  E               o  ACMSREMV_044 - if you are installing the VAX remote-o                  access kit.                 device-name C               The name of the device on which you plan to mount the E               media. For example, CDROM is the device name for a tape                drive.                 OPTIONSiI               An optional parameter indicating that one or more VMSINSTAL D               options are being supplied. This parameter is followedE               by a space, and then the requested options. If multiplesF               options are requested, separate them with commas (,); do5               not include spaces in the options list.   I                                                       Installing ACMS 3-3                 Installing ACMSm     3.2 Installation Procedure    B           The following are VMSINSTAL options that you can use for            the ACMS installation:  B           o  N-The release notes option causes VMSINSTAL to promptB              you to display or print the ACMS release notes duringB              the installation. (Release notes are always copied toA              SYS$HELP during an installation, whether or not this "              option is specified.)  ?           o  AWD-The alternate working device option allows you2D              specify an alternate disk device on which to create theC              temporary working directory used by VMSINSTAL during aoD              product installation. This option allows you to performA              an installation with fewer free blocks on the systemh.              disk than are otherwise required.  ?              Specify the AWD option using the following format:e                AWD=devicel  C              ________________________ Note ________________________   ;              Use the AWD option only if you have previously @              installed ACMS and you do not have sufficient spaceB              on your system disk to perform a normal installation.@              If you have not previously installed ACMS, you mustA              have the disk space listed in Table 2-2 or Table 2-3o8              available to accommodate the ACMS software.  C              ______________________________________________________o  D              See Section 2.4.2 for more information on using the AWD              option.  C           VMSINSTAL has several other options; for information, seeh=           the OpenVMS documentation on software installation.t  C              ________________________ Note ________________________   ?              ACMS does not support option R, the alternate rootP              option.  C              ______________________________________________________G  ?           On Alpha, the following command invokes VMSINSTAL and A           installs ACMS from the CD-ROM reader. This example useseD           the N option for printing or displaying release notes, andB           the AWD option to use disk DISK1 as an alternate working           device:t       3-4 Installing ACMS  e  r      I                                                           Installing ACMSlI                                                3.2 Installation Procedurer    L               $ @SYS$UPDATE:VMSINSTAL ACMSDEVA_044 CDROM OPTIONS N,AWD=DISK1  L                     OpenVMS AXP Software Product Installation Procedure V7.3  )               It is 22-JUN-2001 at 11:00.M=               Enter a question mark (?) at any time for help.G  H               If you do not supply either the product name or the deviceG               name, VMSINSTAL prompts you for this information later ona,               in the installation procedure.                 1. System backup  E                  VMSINSTAL asks the following question to ensure thatf8                  your system disk is properly backed up:  O                  * Are you satisfied with the backup of your system disk [YES]?m  E                  Always back up your system disk before performing an F                  installation. If you are satisfied with the backup ofG                  your system disk, press <Return>. Otherwise, answer NONH                  to stop the installation. After you back up your system8                  disk, you can restart the installation.                                            I                                                       Installing ACMS 3-5e r  e           Installing ACMS      3.2 Installation Procedure               2. Mounting the mediat  B              VMSINSTAL instructs you to mount the ACMS Version 4.4@              distribution media on the device you specified whenD              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.t              * Are you ready? Yu  B              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 <Ctrl/Y>.p  :              VMSINSTAL then reads the media and begins theE              installation of ACMS. A message similar to the following               appears:_  C              %MOUNT-I-MOUNTED, ACMSDEVA_044 MOUNTED ON _$200$DISK1:   6              The following products will be processed:                  ACMSDEVA_ V4.48  F                      Beginning installation of ACMSDEVA_ V4.4 at 11:01  A              %VMSINSTAL-I-RESTORE, Restoring product saveset A...              3. Release notes  C              If you specified OPTIONS N when you invoked VMSINSTAL, @              you are now given several options for reviewing the              release notes.l  T                  Release notes included with this kit are always copied to SYS$HELP.  2                  Additional Release Notes Options:  -                      1. Display release notes +                      2. Print release notes $                      3. Both 1 and 2)                      4. None of the aboveu  !              * Select option [2]:.  C              If you select option 1, VMSINSTAL displays the releaseuD              notes immediately. You can terminate the display at anyE              time by pressing <Ctrl/C>. Because the release notes arenC              lengthy, it is recommended that you choose option 2 to        3-6 Installing ACMSa t         I                                                           Installing ACMS I                                                3.2 Installation Procedures    F                  print the release notes rather than reviewing them on                  line.  F                  If you select option 2, VMSINSTAL prompts you for the>                  name of the print queue that you want to use:  *                  * Queue name [SYS$PRINT]:  B                  You can enter a queue name or just press <Return>C                  to send the file to the default output print queuei                  SYS$PRINT.   G                  If you select option 3, VMSINSTAL displays the releaseMH                  notes immediately and then prompts you for a queue name)                  for the printed version.t  F                  If you select option 4, VMSINSTAL does not display orE                  print the release notes. Use the DCL command TYPE or_G                  PRINT to view the release notes in the following file:a  /                  SYS$HELP:ACMS044.RELEASE_NOTES   G                  The release notes are copied to the SYS$HELP directory H                  under all circumstances, regardless of your choice from                  the menu.  F                 ________________________ Note ________________________  >                 The release notes for each version of ACMS areB                 uniquely named so that release notes from multipleD                 versions can be maintained. To facilitate comparisonB                 of various versions of ACMS, Compaq recommends notE                 deleting release notes for previous versions of ACMS.e  F                 ______________________________________________________  ,               4. Continuing the installation  C                  The installation procedure now asks if you want to_D                  continue the installation. To continue, answer YES.D                  Otherwise, press <Return> to stop the installation:  C                  * Do you want to continue the installation [N]?: YtR                  %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to'                               SYS$HELP.d  I                                                       Installing ACMS 3-7  d              Installing ACMS      3.2 Installation Procedure    B              After you read the release notes, you can restart theD              installation without being questioned about the releaseD              notes by removing OPTIONS N from the VMSINSTAL command.              For example:e  8              $ @SYS$UPDATE:VMSINSTAL ACMSDEVA_044 CDROM:  3     3.2.2 Product-Specific Questions (Second Phase)u  @           This section discusses the questions and messages thatE           apply specifically to the installation of ACMS Version 4.4. C           Depending on the kit and options that you choose, some ofzE           the steps listed here might not apply to your installation.rE           This discussion assumes that you are installing the OpenVMS D           Alpha development kit (ACMSDEVA_044). See Appendix A for aC           sample installation of the ACMS OpenVMS Alpha development :           kit and of the ACMS OpenVMS VAX development kit.  =           Each question in the installation is marked with anCD           asterisk (*)  at the beginning of the line. Some questionsD           show the default response in brackets, for example, [YES].9           To choose the default response, press <Return>.m  +           1. Selecting installation optionsG  ?              The product-specific installation procedure beginsu;              execution. The following message is displayed:C  A              The results of this installation are being logged in.:                SYS$COMMON:[SYSUPD]ACMS044_INSTALLATION.LOG  4              Installing ACMS V4.4-0, development kit  9              The procedure then asks what portions of thesD              installation you want to perform. It lists the optionalB              parts of the installation, and asks if you want to do?              the full installation. If you answer YES, the full B              installation is done; if you answer NO, you are askedC              individually whether you want to perform each optional &              part of the installation.  @              In this example, the full installation is selected:           3-8 Installing ACMS     n      I                                                           Installing ACMSsI                                                3.2 Installation Proceduret    X                  There are five optional parts to the ACMS development kit installation:  /                      o  ACMS component softwarei'                      o  ACMS LSE updateA$                      o  ACMS samples6                      o  ACMS Request Interface samples/                      o  ACMS WBEM related filess  @                  The full installation includes all these parts.Y                  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 mustT                  install, or have previously installed, the ACMS component software.  B                  * Do you want the full ACMS installation [NO]?: Y  4               2. Checking installation prerequisites  G                  The installation now checks that all ACMS installation I                  prerequisites are met. These prerequisites are discussed B                  in Chapter 2. The following message is displayed:  4                  CHECKING INSTALLATION PREREQUISITES4                  -----------------------------------  B                  A message is also displayed for any prerequisitesE                  that are not met. For example, the following messagelE                  indicates that the optional DECtrace software is nott                  installed:t  \                  The following software products are not available, or are below the minimum"                  required version:  S                    Product               Required  Minimum version  Current versionuS                    --------------------  --------  ---------------  --------------- K                    LSE                   No        V4.3             V4.2-17   [                  If products marked as nonrequired are to be used with ACMS, they should besO                  upgraded to at least the minimum version displayed before use.s  9                  (required and optional software checked)n  +                  (product licenses checked)e  +                  (installed images checked)r  %                  (privileges checked)   %                  (disk space checked)o  I                                                       Installing ACMS 3-9i n  l           Installing ACMS      3.2 Installation Procedure    "              (disk quotas checked)  (              (system parameters checked)  -              (process account quotas checked)k  B              These messages are also logged in the following file:  0              SYS$UPDATE:ACMS044_INSTALLATION.LOG  >              If any of the prerequisites are not met (with theB              exception of those related to optional software), theA              installation is aborted and a message similar to the $              following is displayed:  U              //////////////////////////////////////////////////////////////////////// O              Installation of ACMS is aborting because prerequisites are not mete&                at 12:00 on 22-JUN-2001U              ////////////////////////////////////////////////////////////////////////   C              At this point, address all the prerequisites that were @              not met, and then restart the installation of ACMS.  5           3. Checking for previous ACMS installationsd  A              The installation procedure checks to see if you have A              previously installed ACMS. If you have, some cleanup D              from the previous installation might be necessary; thisD              is the case, for example, if you previously installed aC              development kit, and you are now installing a run-timee              kit.   ;              The following message shows that no cleanup ise              necessary:h  '              ACMS PREVIOUS INSTALLATION '              --------------------------s  X                  (previous installation of ACMS is compatible with current installation)  A              If cleanup is necessary, you are given the option to E              see a list of files that will be removed from the system *              disk during the installation.  4           4. Reviewing the LSE informational message  C              If you chose the LSE update option at the beginning ofSE              the installation, or if you chose the full installation,r?              the installation advises you whether or not it can A              perform the LSE update. LSE cannot be updated if theV       3-10 Installing ACMS t  t      I                                                           Installing ACMSeI                                                3.2 Installation Procedure     G                  optional LSE software is not present or if it is below %                  the minimum version.M  F                  The following message advises you that the LSE update.                  will take place as requested:                    ACMS LSE CHECK                   --------------   D                      (LSE available -- LSE will be updated for ACMS)  C                  Later on you are asked if you want to continue thesF                  installation. If you were informed that LSE would notD                  be updated, you can continue the installation, thenD                  install LSE and reinstall ACMS at your convenience,A                  using the LSE update option; or you can stop thenI                  installation, install LSE, and then restart the complete #                  ACMS installation.O  )               5. Reviewing the WBEM Files   F                  The installation advises you whether or not the filesI                  necessary for the Compaq Web-Based Enterprise ManagementiC                  (WBEM) environment are already present. The RemoteeA                  Manager web agent software cannot be used if theeE                  appropriate WBEM software is not present or if it isi+                  below the minimum version.   H                  The following message advises you that the verification3                  of the WBEM files will take place:                      ACMS WBEM CHECK$                  -------------------  A               6. Reviewing the Oracle Trace informational messages  C                  The installation advises you whether or not it caneE                  perform the Oracle Trace update. Oracle Trace cannotlH                  be updated if the optional Oracle Trace software is not?                  present or if it is below the minimum version.T  H                  The following message advises you that the Oracle Trace(                  update will take place:  (                  ACMS Oracle Trace CHECK$                  -------------------  J                      (Oracle Trace available and will be updated for ACMS)  I                                                      Installing ACMS 3-11h i  r           Installing ACMSe     3.2 Installation Procedure    ?              Later on you are asked if you want to continue the_A              installation. If you were informed that Oracle TracetE              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 tonC              Oracle Trace, which is used to update the Oracle TraceaB              facility database when Oracle Trace is installed. YouB              do not have to reinstall ACMS after installing Oracle              Trace._  4           7. Reviewing the CDD informational message  C              If you are installing a run-time kit, the installationaC              advises you whether CDD is available. The availability A              of CDD affects the features provided by the run-time_?              kit. See Section 1.4.2 for an explanation of these               features.  E              The following message advises you that CDD is available:_                ACMS CDD CHECK_              --------------p  G                  (CDD available -- CDD-related files will be installed)r  ?              Later on you are asked if you want to continue ther?              installation. If you were informed that ACMS filesiD              related to CDD would not be installed, you can continueB              the installation, then install CDD and reinstall ACMSE              at your convenience, using the CDD related files option; D              or you can stop the installation, install CDD, and then4              restart the complete ACMS installation.  A           8. Reviewing the old sample files informational messageo  E              If you chose the ACMS samples option at the beginning of E              the installation, or if you chose the full installation,f;              the installation checks for old samples from a ?              previous installation. These samples are stored ino<              SYS$COMMON:[SYSHLP.EXAMPLES.ACMS], and they are@              superseded by examples supplied with this kit. They?              are deleted automatically during the installation.s  B              The following message advises you that no old samples              were found:       3-12 Installing ACMS w         I                                                           Installing ACMS I                                                3.2 Installation Proceduree    &                  ACMS OLD SAMPLE FILES&                  ---------------------  0                      (no old sample files found)  C                  Later on you are asked if you want to continue the I                  installation. If you want to preserve these old samples,-D                  stop the installation, rename the sample files to a>                  different directory, and then reinstall ACMS.  B               9. Reviewing the ACMS shutdown informational message  C                  If you chose the ACMS component software option atNG                  the beginning of the installation, or if you chose theeH                  full installation, the installation checks for the ACMS$                  shutdown procedure:  (                  SYS$STARTUP:ACMSTOP.COM  B                  If this procedure is found, the ACMS installation@                  procedure executes it to ensure that previouslyB                  installed ACMS software is not running during theD                  installation. This shutdown occurs after you chooseC                  to continue the installation in a subsequent step.s  G                  The following message advises you that ACMSTOP.COM wasO                  found:E  $                  ACMS SHUTDOWN CHECK$                  -------------------  V                      (ACMSTOP.COM found -- ACMS will be shut down during installation)  F                 ________________________ Note ________________________  E                 If you have previously installed ACMS on this system,e@                 and if ACMSTOP.COM is not found, ensure that theC                 ACMS system is shut down before continuing with thel                 installation.t  F                 ______________________________________________________  G              10. Reviewing the postinstallation procedure informationale                  message  I                                                      Installing ACMS 3-13                 Installing ACMS      3.2 Installation Procedure    <              If you chose the ACMS component software at the?              beginning of the installation, or if you chose the B              full installation, the installation procedure advisesC              you whether or not it can execute the postinstallationcD              procedure automatically. The postinstallation procedure?              cannot be executed if you do not have the required                privileges enabled.  <              The following message advises you that the ACMS8              postinstallation procedure will be executed              automatically:   ,              ACMS POSTINSTALLATION PROCEDURE,              -------------------------------  Z                  (postinstallation procedure will be run automatically after installation)  C              ________________________ Note ________________________   B              Refer to Chapter 4 for important information on other<              steps to take before using ACMS on your system.  C              ______________________________________________________e  C          11. Reviewing the system roots check informational messagen  >              The installation checks for ACMS files in system->              specific roots. If you previously installed ACMS,E              certain files might exist in system-specific roots. With C              a few exceptions (for example, ACMSPAR.ACM) ACMS filesE@              should reside in cluster-common directories such asE              SYS$COMMON:[SYSLIB]. Some ACMS files might have migratedoC              to system-specific roots as a result of maintenance or_B              other activities performed on the previous version ofB              ACMS. If ACMS files have migrated in this manner, andD              you then upgrade to a higher version of ACMS, you mightB              subsequently encounter problems running ACMS across aD              cluster, such as problems related to a version mismatchA              or the inability to access new functionality on some_              nodes._  C              The installation checks for ACMS files that might havelA              migrated inadvertently to system-specific roots, andoA              lists any files it finds. Compaq recommends that you,>              check any files listed to ensure that they do not       3-14 Installing ACMS           I                                                           Installing ACMSAI                                                3.2 Installation Procedure     C                  interfere with the proper operation of ACMS in the E                  cluster. Table 3-1 lists the files that are checked.                                                                                       I                                                      Installing ACMS 3-15a                Installing ACMSO     3.2 Installation Procedure    E           Table_3-1_ACMS-Related_Files_Checked_For_in_System_Roots___M  E           Directory_______Files______________________________________   8           SYS$SYSTEM      ACM*.EXE, ACM*.DAT, SYSUAF.DAT  ,           SYS$LIBRARY     ACM*.EXE, ACM*.COM  "           SYS$MANAGER     ACM*.COM  E           SYS$STARTUP_____ACM*.COM___________________________________   @              This example shows that no ACMS files were found in#              system-specific roots:a  $              ACMS SYSTEM ROOTS CHECK$              -----------------------  G                  (no ACMS-related files found in system-specific roots)   (          12. Choosing to execute the IVP  C              You are now asked whether you want to execute the ACMStE              Installation Verification Procedure (IVP). This question E              is asked if you are installing ACMS software (as opposedfC              to installing samples or updating the LSE environment,R              for example).  A              Compaq recommends that you run the IVP automaticallytD              after the installation, to ensure that the installationC              was successful. Chapter 5 contains more information onrE              the IVP, including how to execute it manually at a laterI              time.  A              The following question is asked to determine whetheruE              you want to run the IVP automatically; press <Return> tot,              accept the default answer, YES:                ACMS IVPn              --------t  T              * Do you want to execute the Installation Verification Procedure [YES]?  C              If you choose to execute the IVP, the installation nowdE              checks for the IVP user account ACMS$IVP. If the accounttD              ACMS$IVP does not exist, you are asked to supply a userE              identification code (UIC) and password for this account. E              The information you supply is used to create the account 4              in the third phase of the installation.       3-16 Installing ACMS           I                                                           Installing ACMS I                                                3.2 Installation ProcedureE    H                  This example shows how to supply a UIC and password for&                  the ACMS$IVP account:  O                  The ACMS$IVP account used to execute the IVP is not available.e  X                    You must supply a UIC and password for this account so that it can beM                    created; this must be done before the IVP can be executed.t  \                    Please enter the UIC for the ACMS$IVP account, in the form [ggggg,nnnnnn]  !                  * UIC: [400,200]S  O                    Please enter a password of at least 8 characters, using onlyNS                    the following characters: ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789$_e                    * Password:                   * Verification:  F                 ________________________ Note ________________________  E                 The password and verification are not echoed when you                  type them.  F                 ______________________________________________________  I                  Refer to Section 2.9 for more information on selecting a 4                  valid UIC for the ACMS$IVP account.  6              13. Choosing to continue the installation  I                  At this time, the installation procedure lists the stepsgF                  to complete the installation, and an approximate timeF                  for the rest of the installation. It then asks if youI                  want to continue. If issues remain that you must address-I                  before the installation continues, answer NO to stop theE                  installation.  H                  The following example shows the work list for a typicalE                  development installation; the lists for run-time ando;                  remote-access installations are different.   2                  SUMMARY OF THIS ACMS INSTALLATION2                  ---------------------------------  Q                  The following steps will be taken to complete this installation:   I                                                      Installing ACMS 3-17                 Installing ACMS      3.2 Installation Procedure    O              o  The ACMS system will be shut down (via SYS$STARTUP:ACMSTOP.COM) 9              o  ACMS component software will be installedc9              o  WBEM environment will be updated for ACMS 8              o  LSE environment will be updated for ACMSG              o  Oracle Trace facility database will be updated for ACMSt8              o  CDD-related ACMS files will be installed.              o  ACMS samples will be installed@              o  ACMS Request Interface samples will be installedD              o  The ACMS postinstallation procedure will be executed-              o  The ACMS IVP will be executed   M              The rest of this installation will take approximately 7 minutes. D              Execution of the IVP will take approximately 2 minutes.  P              Note that this time is heavily dependent your system load, hardwareU              and kit media. The time mentioned was measured on a stand-alone DEC 3000eK              (Alpha)  system with a disk-resident kit.  Your time may vary.n  >              * Do you want to continue the installation [YES]?  9              Press <Return> to continue the installation.s  .     3.2.3 Informational Messages (Third Phase)  A           In the third installation phase, the actual work of thel>           installation takes place; restoring savesets, movingA           files, updating databases, and so on. This phase has no D           user interaction. At the beginning of the phase, a message0           similar to the following is displayed:  *               Installation of ACMS started'                 at 11:02 on 22-JUN-2001o  E           Following this message, the installation procedure displaysa?           a number of informational messages that report on thea'           progress of the installation.t  :           If any errors are encountered in this phase, theD           installation aborts and a message similar to the following           is displayed:t  V               ////////////////////////////////////////////////////////////////////////N               Installation of ACMS is aborting because errors were encountered'                 at 13:25 on 22-JUN-2001 V               ////////////////////////////////////////////////////////////////////////  B           If you receive this message, use information in previousE           error messages and the installation log to fix the problem, "           and then reinstall ACMS.       3-18 Installing ACMS           I                                                           Installing ACMSuI                                                3.2 Installation Procedure     G               When the third phase is successfully completed, a message 4               similar to the following is displayed:  =                   Installation of ACMS completed successfullyi+                     at 11:07 on 22-JUN-2001o  \               %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...  H               During the ACMS installation, VMSINSTAL operates in safetyD               mode, which means that it defers file operations untilH               the third phase has successfully completed. The VMSINSTAL-D               I-MOVEFILES message indicates that these deferred file1               operations are now being performed.o  C         3.2.4 Running the Postinstallation Procedure (Fourth Phase)t  A               If you were informed during the second phase of thenI               installation that the ACMS postinstallation procedure wouldeH               be executed, it is done at this time. A message similar to)               the following is displayed:   9                   ACMS postinstallation procedure startedl+                     at 11:09 on 22-JUN-2001i  C               The postinstallation procedure performs the following                steps:  9               1. Checking the ACMS$DIRECTORY logical namee  E                  The procedure checks for the presence of the logicalaF                  name ACMS$DIRECTORY. If this logical name is defined,D                  it must be in /SYSTEM /SUPERVISOR mode, and it mustI                  point to an existing directory. If ACMS$DIRECTORY is not I                  defined or is improperly defined, the procedure asks youaH                  for information so that it can define the logical name.  C                  The following message shows that ACMS$DIRECTORY is-"                  properly defined:  G                      ACMS$DIRECTORY is defined as MGR$:[ACMS.DIRECTORY] 9                      ACMS$DIRECTORY logical is acceptable   3               2. Converting ACMSGEN parameter filesn  C                  The procedure asks if you want to convert existingiE                  ACMSGEN parameter files. If you answer YES, or pressrE                  <Return> to accept the default answer, the procedureiD                  searches for all ACMSGEN parameter files located inI                  SYS$SYSDEVICE:[SYS*.SYSEXE] and SYS$COMMON:[SYSEXE], and F                  converts them to be compatible with ACMS Version 4.4.  I                                                      Installing ACMS 3-19  e              Installing ACMSl     3.2 Installation Procedure    <              The following message shows the ACMSGEN convert=              question, and typical output from the conversion               process:u  I              Do you want to convert existing ACMSGEN parameter files [Y]?   =                  Converting SYS$SYSDEVICE:[SYSEXE]ACMSPAR.ACM   M              The ACMSGEN parameter files listed above have been converted; iflP              other parameter files exist on your system, they must be updated as              follows:-  -                      $ RUN SYS$SYSTEM:ACMSGENr4                      ACMSGEN> USE file-specification6                      ACMSGEN> WRITE file-specification"                      ACMSGEN> EXIT                                                               3-20 Installing ACMS n         I                                                           Installing ACMSaI                                                3.2 Installation Procedureo    2               3. Converting ACMS UDF and DDF files  C                  The procedure asks if you want to convert existingiE                  ACMS UDF and DDF parameter files. If you answer YES,hD                  or press <Return> to accept the default answer, theC                  procedure searches for the files pointed to by theiE                  logical names ACMSUDF and ACMSDDF, if these logicalslI                  are defined, and then for ACMSUDF.DAT and ACMSDDF.DAT inLG                  SYS$SYSROOT:[SYS*], and converts them to be compatible '                  with ACMS Version 4.4.a  A                  The following message shows the ACMS UDF and DDFmI                  convert question, and typical output from the conversion2                  process:   L                  Do you want to convert existing ACMS UDF and DDF files [Y]?  G                      Converting UDF file SYS$COMMON:[SYSEXE]ACMSUDF.DAT G                      Converting DDF file SYS$COMMON:[SYSEXE]ACMSDDF.DAT-  4               4. Checking for ACMS UDF and DDF files  B                  The procedure checks for the presence of ACMS DDFD                  and UDF files. It first tries to locate these filesI                  through the /SYSTEM /EXECUTIVE logical names ACMSUDF andeF                  ACMSDDF, if they exist. The procedure then checks forG                  ACMSUDF.DAT and ACMSDDF.DAT in SYS$COMMON:[SYSEXE]. If H                  the files are not found in either manner, the procedure                  creates them.  C                  The following message shows that the logical names ?                  do not exist, but that the files were found inr%                  SYS$COMMON:[SYSEXE]:P  @                      No /SYSTEM /EXECUTIVE logical ACMSUDF found6                      SYS$COMMON:[SYSEXE]ACMSUDF exists  @                      No /SYSTEM /EXECUTIVE logical ACMSDDF found6                      SYS$COMMON:[SYSEXE]ACMSDDF exists  ,               5. Checking for ACMS_SETUP.COM  H                  The procedure checks for the presence of ACMS_SETUP.COMB                  in SYS$STARTUP. If the file does not exist, it isG                  created. This is a template for site-specific commands B                  related to the startup of ACMS. ACMS_SETUP.COM isE                  executed by ACMSTART.COM, which is normally executed_B                  during system startup to start the ACMS software.  I                                                      Installing ACMS 3-21A T  C           Installing ACMSt     3.2 Installation Procedure    >              Chapter 4 explains how to modify this template to@              address your specific needs regarding ACMS startup.  E              If ACMS_SETUP.COM already exists, the ACMS_SETUP_NEW.COMrE              template file is created. After the installation, review A              this template file to see if you need to add any new 6              commands to your existing ACMS_SETUP.COM.  @              The following message shows that the ACMS_SETUP.COMC              already exists, and that the template file ACMS_SETUP_ &              NEW.COM is being created:  F                  SYS$COMMON:[SYS$STARTUP]ACMS_SETUP.COM already exists  D                  Creating SYS$COMMON:[SYS$STARTUP]ACMS_SETUP_NEW.COM  X              Please review the contents of ACMS_SETUP_NEW.COM to determine whether thereM              are any commands you should add to your existing ACMS_SETUP.COM.S  )           6. Checking for ACMS menu filesl  @              The procedure checks in ACMS$DIRECTORY for the ACMS@              command menu ACMSCMD.MDB, and the default user menuB              ACMS.MDB, and copies them into that directory if theyD              do not exist. The following message shows that the menu3              files already exist in ACMS$DIRECTORY:t  H                  ACMS$DIRECTORY:ACMSCMD.MDB already exists -- not copiedE                  ACMS$DIRECTORY:ACMS.MDB already exists -- not copied_  /           7. Checking for ACMS$MGMT_SETUP filesv  @              The procedure checks for ACMS$MGMT_SETUP and RemoteD              Manager configuration files and asks if you want to set1              up and configure the Remote Manager.   S              Do you want to SETUP and CONFIGURE the ACMS Remote System Manager [Y]?c9                  Creating SYS$STARTUP:ACMS$MGMT_SETUP.COM   C              If you respond yes, the procedure asks you a series ofCE              questions concerning Remote Manager configuration. ReferyE              to the Compaq ACMS for OpenVMS Remote Systems ManagementaC              Guide for more information about Remote Manager setup.   @              When the postinstallation procedure is completed, a;              message similar to the following is displayed:s       3-22 Installing ACMS r  i      I                                                           Installing ACMSmI                                                3.2 Installation Procedure     K                      ACMS postinstallation procedure completed successfullyg.                        at 11:10 on 22-JUN-2001  F                 ________________________ Note ________________________  ?                 See Chapter 4 for information on tasks that your@                 perform manually after ACMS is installed on your                 system.   F                 ______________________________________________________  D         3.2.5 Running the Installation Verification Procedure (Fifth               Phase)  A               If you were informed during the second phase of the B               installation that the ACMS Installation VerificationI               Procedure (IVP) would be executed, it is done at this time. >               A message similar to the following is displayed:  B                   ACMS Installation Verification Procedure started+                     at 11:10 on 22-JUN-2001m  H               The IVP is then invoked. It displays several informationalH               messages to inform you of its progress. Refer to Chapter 53               for more information on the ACMS IVP.   F                 ________________________ Note ________________________  C                 If the ACMS IVP is not invoked automatically duringCE                 the installation, invoke it manually at your earliest 3                 convenience after the installation.-  F                 ______________________________________________________  F               When the ACMS IVP is completed, a message similar to the%               following is displayed:e  Q                   ACMS Installation Verification Procedure completed successfullyo+                     at 11:12 on 22-JUN-2001n            I                                                      Installing ACMS 3-23v n  t           Installing ACMSe     3.2 Installation Procedure    %     3.2.6 Completing the Installation   >           The following message indicates that the entire ACMS#           installation is complete:r  ;           Installation of ACMSDEVA_ V4.4 completed at 11:12n  ?           You can now log out of the privileged SYSTEM account:              $ LOGOUT:           SYSTEM     logged out at 22-JUN-2001 11:13:01.55  D           VMSINSTAL deletes or changes entries in the process symbol?           tables during the installation. Therefore, if you are A           going to continue using the SYSTEM account and you wantn=           to restore these symbols, log out and log in again.   8     3.3 Recovering from System and Installation Failures  ?           An unsuccessful installation can result from a systemM?           failure or errors encountered during the installation @           procedure. In some cases, you must correct the problemD           and reinstall ACMS. In other cases, you can continue where?           you left off. The following sections describe variousaC           failure scenarios and the recommended procedure to follow            to recover from them.        3.3.1 System Failures   B           If you experience a system failure, such as a power loss?           during installation, VMSINSTAL automatically attempts B           to continue the installation when you reboot the system.A           Depending on the point in the installation at which them8           system failed, one of three conditions exists:  C           o  The system disk did not undergo any changes before thenC              system failure. VMSINSTAL instructs you to restart theS              installation.  D           o  The system disk used by the installation was corrupted.D              VMSINSTAL instructs you to restore the system disk from:              the backup copy and restart the installation.  @           o  VMSINSTAL continues the installation and then mightC              tell you to manually purge replaced files, even if you_A              requested that they be purged automatically. You canoC              purge files, but remember that purging deletes all but D              the latest version of all files on your system disk. IfE              you have multiple versions of system files that you want        3-24 Installing ACMS A  $      I                                                           Installing ACMS I                      3.3 Recovering from System and Installation Failures     E                  to save, you can delete just the ACMS files you want H                  to remove from system directories. If you want to purgeH                  files, reboot the system, log in to the SYSTEM account,H                  and purge all system files using the following command:  2                  $ PURGE/LOG SYS$SYSROOT:[*...]*.*  G                  When you have performed this task, the installation iss                  complete.  @               If the system fails after you see the message thatD               indicates the beginning of the ACMS IVP, VMSINSTAL hasA               already completed the installation of the componentlB               software. In this case, when you reboot your system,7               VMSINSTAL displays the following message:   _               %VMSINSTAL-I-RECOVER, ACMSDEVA_ V4.4 was being installed when the system crashed.   8               The installation completed satisfactorily.  @               This message indicates that VMSINSTAL has finishedA               successfully, not that the installation of ACMS was                successful.b  G               VMSINSTAL does not automatically restart the IVP. You canuH               run the IVP independently by following the steps described               in Chapter 5.s  (         3.3.2 ACMS Installation Failures  E               If the installation of the ACMS software fails for somesB               reason other than a system failure, the installationC               procedure displays a message telling you the cause ofaF               the failure. To continue with the installation, you mustE               correct the condition causing the error and restart thel8               installation procedure from the beginning.  D               Errors can occur during the installation if any of the)               following conditions exist:d  7               o  Operating system version is incorrect.t  <               o  Prerequisite software version is incorrect.  A               o  Quotas necessary for successful installation ares                  insufficient.  H               o  System parameter values for successful installation are                  insufficient.  I                                                      Installing ACMS 3-25                 Installing ACMSb8     3.3 Recovering from System and Installation Failures    6           o  OpenVMS help library is currently in use.  C           For descriptions of the error messages generated by thesew=           conditions, see the OpenVMS documentation on system =           messages, recovery procedures, and OpenVMS software >           installations. If you are notified that any of theseD           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.) ForB           information on installation requirements, see Chapter 2.  A           If the installation of the component software completes2B           satisfactorily, but a test or operation fails during theD           IVP, the IVP displays a message describing the failure andC           suggests a course of action. In most cases, the suggestedoB           course of action is to reinstall ACMS. The failure couldD           be due to low settings for the SYSGEN parameters GBLPAGES,A           GBLSECTIONS, GBLPAGFIL, or to an insufficient number of @           process slots. Check the ACMS Software Event Log for aB           message that indicates the source of the problem. If the@           IVP fails after you reinstall ACMS, contact your local)           Compaq Customer Support Center.u        3.3.3 Recovering from Errors  D           You can run the ACMS IVP separately after you install ACMS@           by following the instructions in Chapter 5. As the IVPD           executes, it checks the success of each test and operation>           it performs. If any test or operation fails, the IVPB           displays a message describing the failure and suggests aA           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 runsE           automatically if you answer YES to the IVP question. If younC           still cannot successfully run the IVP, contact your local )           Compaq 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:ACMS044.RELEASE_NOTES         3-26 Installing ACMS    l      I                                                           Installing ACMScI                                    3.4 Accessing the Online Release Noteso    E               Online help also directs you to the release notes file.eA               After the installation, you can enter the following                command:  '               $ HELP ACMS RELEASE_NOTESC  >               Hardcopy release notes are not included with the)               documentation set for ACMS.r  *         3.5 Files Installed on Your System  I               The files added to your system by the ACMS installation are-               listed in:  *               SYS$SYSTEM:ACMS044_FILES.DAT  H               You can display or print this file after you install ACMS.  C               ACMS Version Identification File (ACMS_ECO_LEVEL.DAT)e  E               Starting with the ACMS Version 4.0 ECO Kit 1 release, aiH               file named ACMS_ECO_LEVEL.DAT is distributed with the kit.D               This file is placed in the SYS$SYSTEM directory during               installation.c  H               ACMS_ECO_LEVEL.DAT contains the version identifier for theE               ACMS release that is currently installed on the system.tG               This file is distributed for all releases, including full F               releases, that have an ECO level of 0. If you report anyE               problems with ACMS, refer to this file to determine thelC               current ACMS version number. The version in this filetF               may be more current than the version numbers that appearI               throughout the ACMS system, especially when running with an                ECO release.                      I                                                      Installing ACMS 3-27v e  i                    I                                                                         4 I         _________________________________________________________________   I                                                     After Installing ACMS     E               This chapter describes system management tasks that you G               perform manually after installing ACMS Version 4.4. These "               tasks might include:  >               o  Executing the ACMS postinstallation procedureF                  manually (if it was not executed automatically during                  installation)  B               o  Editing system startup and shutdown procedures to                  include ACMSD  G               o  Editing the ACMS site-specific startup procedure ACMS_R                  SETUP.COM  *               o  Modifying ACMS parameters  H               o  Authorizing applications, devices, users, and processes  :               o  Creating and modifying ACMS user accounts  =               o  Setting up ACMS on an OpenVMS Cluster systemS  5               o  Enabling distributed ACMS processing   /               o  Rebuilding the LSE environment   =               o  Preparing language-specific ACMS development                   environmentst  :               The following sections describe these tasks.  9         4.1 Executing the ACMS Postinstallation Procedure   H               If you were notified during the ACMS installation that theH               postinstallation procedure would not be run automatically,               execute it now.   I                                                 After Installing ACMS 4-1c k  o           After Installing ACMS 5     4.1 Executing the ACMS Postinstallation Proceduree    E           To execute the postinstallation procedure manually, use theD           following commands:F  #           $ SET DEFAULT SYS$MANAGERc"           $ @ACMS_POST_INSTALL.COM  =           See Section 3.2.4 for more information on the stepse6           performed by the postinstallation procedure.  6     4.2 Editing System Startup and Shutdown Procedures  ?           You must edit the OpenVMS system startup and shutdown B           procedures to provide for automatic startup and shutdownE           of ACMS when your system is rebooted. (This step is usuallyU-           not necessary for system upgrades.)X  .     4.2.1 Editing the System Startup Procedure  =           Add the following DCL command to the system startupO           procedure:  %           $ @SYS$STARTUP:ACMSTART.COMS  =           For sites that have modularized startup procedures,e>           be sure to add the command to the correct procedure.?           The default startup command procedure for OpenVMS VAXaA           starting with Version 6.x and for OpenVMS Alpha systemsr+           is SYS$MANAGER:SYSTARTUP_VMS.COM.   C           Position the ACMS startup command after the commands that C           start software on which ACMS relies. In particular, start C           ACMS after the network, DECdtm, and DECforms are started, B           and before TP Desktop Connector is started. For example:  %           $ @SYS$STARTUP:STARTNET.COM +           $ @SYS$STARTUP:DECDTM$STARTUP.COMp*           $ @SYS$STARTUP:FORMS$STARTUP.COM%           $ @SYS$STARTUP:ACMSTART.COMt+           $ @SYS$STARTUP:ACMSDI$STARTUP.COMl  C              ________________________ Note ________________________   C              The network must be running before ACMS is started, if >              you are going to use distributed ACMS processing.  C              ______________________________________________________t       4-2 After Installing ACMS            I                                                     After Installing ACMS_I                        4.2 Editing System Startup and Shutdown ProceduresU    A         4.2.2 Installing ACMS Images as Resident on OpenVMS Alpha_  D               On OpenVMS Alpha systems, your application performanceG               may improve by installing certain ACMS images as resident D               with the OpenVMS Install utility. Installing images asI               resident allows them to take advantage of the OpenVMS Alphau$               image-slicing feature.  H               The code sections of an image installed as resident resideE               in huge pages called granularity hint regions (GHRs) inCI               memory. The Alpha hardware can consider a set of pages as asG               single GHR. This GHR can be mapped by a single page table-D               entry (PTE) in the translation buffer (TB). The resultF               is a reduction in TB miss rates. For more information onD               improving the performance of shareable images, see the,               OpenVMS Linker Utility Manual.  I               The following ACMS images have been linked to allow them tor'               be installed as resident:R                 For all kits:   '               o  SYS$LIBRARY:ACMSHR.EXEa  *               o  SYS$LIBRARY:ACMTWPSHR.EXE  )               o  SYS$LIBRARY:ACMRRSHR.EXEy  )               o  SYS$LIBRARY:ACMVFSHR.EXE   H               For development and run-time kits only (in addition to the               preceding):   *               o  SYS$LIBRARY:ACMIWPSHR.EXE  '               o  SYS$SYSTEM:ACMSIWP.EXEr  E               To install images as resident, execute the ACMS startup G               command procedure with the RESIDENT parameter as follows:M  0               @SYS$STARTUP:ACMSTART.COM RESIDENT  D               On OpenVMS VAX, the RESIDENT parameter is ignored when*               specified with ACMSTART.COM.  I               Installing images as resident may require that you increase_H               the GBLPAGES, GBLSECTIONS, and NPAGEDYN system parameters.B               Refer to Section 2.6.3 for more information on using2               AUTOGEN to change system parameters.  I                                                 After Installing ACMS 4-3                 After Installing ACMSV6     4.2 Editing System Startup and Shutdown Procedures    A           For OpenVMS Alpha Version 6.x, you may need to increase E           the GH_RSRVPGCNT SYSGEN parameter to install ACMS images as            resident.o  ?     4.2.3 ACMSTART.COM Installs DECC$SHR and ACMS$TRACE_SHR.EXE   D           ACMSHR.EXE links with ACMS$TRACE_SHR.EXE, which links withA           DECC$SHR.EXE. ACMSTART.COM has been modified to installoC           both DECC$SHR.EXE and ACMS$TRACE_SHR.EXE. It is necessarys2           to leave both of these images installed.  @           If DECC$SHR is not installed on the system, you get an<           error similar to the following when starting ACMS:             $ ACMS/START SYS:           %DCL-W-ACTIMAGE, error activating image DECC$SHR(               -CLI-E-IMGNAME, image fileB                $100$DUA253:[SYS4.SYSCOMMON.][SYSLIB]DECC$SHR.EXE;1G               -SYSTEM-F-PRIVINSTALL, shareable images must be installed_&                to run privileged image  C           If ACMS$TRACE_SHR.EXE is not installed on the system, youe5           get the following error when starting ACMS:              $ ACMS/START SYSD           %DCL-W-ACTIMAGE, error activating image ACMS$TRACE_SHR.EXE$           -CLI-E-IMGNAME, image fileF                $100$DUA253:[SYS4.SYSCOMMON.][SYSLIB]ACMS$TRACE_SHR.EXEG               -SYSTEM-F-PRIVINSTALL, shareable images must be installed.&                to run privileged image  /     4.2.4 Editing the System Shutdown Procedurer  E           Add the following DCL commands to the system shutdown file, $           SYS$MANAGER:SYSHUTDWN.COM:  $           $ ACMS/STOP SYSTEM /CANCEL$           $ @SYS$STARTUP:ACMSTOP.COM  C           The first command cancels all active tasks and shuts down D           the ACMS system. It ensures that the ACMS system processes0           are run down properly and immediately.  >           The second command invokes the ACMS shutdown command@           procedure, ACMSTOP.COM. This procedure deinstalls ACMS8           images (using the Install Utility of OpenVMS).       4-4 After Installing ACMSu c  s      I                                                     After Installing ACMSeI                                                4.3 Editing ACMS_SETUP.COMr    "         4.3 Editing ACMS_SETUP.COM  I               During the installation of ACMS, ACMS_SETUP.COM, a templateoE               for site-specific ACMS startup operations, is placed in C               SYS$STARTUP. If ACMS_SETUP.COM already existed from a F               previous installation, the template is named ACMS_SETUP_               NEW.COM.  F               The next sections describe modifications you can make to8               ACMS_SETUP.COM, based on your use of ACMS.  )         4.3.1 Optional ACMS Logical Namesn  F               Table 4-1 lists optional ACMS logical names that you can;               define in ACMS_SETUP.COM, and their defaults.c  I               Table_4-1_Optional_ACMS_Logical_Names______________________e  I               Logical_Name_____Default___________________________________y  9               ACMS$AUDIT_      SYS$ERRORLOG:ACMSAUDIT.LOGr               LOG[1]  3               ACMS$SWL_LOG[1]  SYS$ERRORLOG:SWL.LOGs  %               ACMS$NOTICE[2]   (none)S  >               ACMS$EDIT[3]     SYS$COMMON:[SYSEXE]TDMSEDIT.COM  (               ADU$EDIT[4]      ACMS$EDIT  (               SWLUP$EDIT[5]    ACMS$EDITI               [1]See_Compaq_ACMS_for_OpenVMS_Managing_Applications_for___a  4               more information on this logical name.C               [2]Used to display the text in the file pointed to bypE               the logical name whenever an ACMS user signs in through E               the terminal subsystem. If defined, it must point to an +               existing, nonempty text file.c9               [3]If TDMS is not installed, the default is .               SYS$COMMON:[SYSEXE]ACMSEDIT.COM.F               [4]Defines the editor to be used for the EDIT command to               ACMSADU.F               [5]Defines the editor to be used for the EDIT command to               SWLUP.I               ___________________________________________________________L  F               For each of these logical names, a DCL command exists in*               ACMS_SETUP.COM. For example:  D               $! DFN_SUPER ACMS$AUDIT_LOG SYS$ERRORLOG:ACMSAUDIT.LOG  I                                                 After Installing ACMS 4-5                 After Installing ACMSl     4.3 Editing ACMS_SETUP.COM    A           (DFN_SUPER is also defined in ACMS_SETUP.COM, to create C           the logical name in the mode required by ACMS.) To equateNB           an optional ACMS logical to a nondefault value, edit theD           appropriate command line by removing the exclamation pointD           (!) and providing a new equivalence string for the logical           name. For example:  =           $ DFN_SUPER ACMS$AUDIT_LOG AUDIT_DISK:ACMSAUDIT.LOG   =     4.3.2 Installing Application Development Shareable Imageso  D           If you have installed the development kit, or the run-time@           kit with CDD installed, the shareable images listed inD           Table 4-2 and Table 4-3 are in SYS$SHARE. If you installed@           the remote-access kit, or the run-time kit without CDD3           installed, these images are not supplied.a  ?           If you do a lot of ACMS application development work,T@           consider installing these shareable images. Installing>           these images increases the number of global sectionsA           and global pages required by ACMS, but decreases memoryc>           requirements if many users are running ADU, and alsoB           decreases image activation time. Table 4-2 and Table 4-3=           show the number of global sections and global pagesr-           required for installing each image.e  A           Table 4-2 Global Sections and Pages Required for SharednE           __________Utility_Images_(Alpha)___________________________i  4                            GBLSECTIONS      GBLPAGESE           Utility_Image____Used_____________Used_____________________   /           ACMADUSHR        3                 63y  /           ACMCDUSHR        3                383e  /           ACMCMUSHR        1                331   E           ACMTDUSHR________3________________650______________________d                 4-6 After Installing ACMSs           I                                                     After Installing ACMSiI                                                4.3 Editing ACMS_SETUP.COMe    E               Table 4-3 Global Sections and Pages Required for SharedeI               __________Utility_Images_(VAX)_____________________________a  8                                GBLSECTIONS      GBLPAGESI               Utility_Image____Used_____________Used_____________________w  3               ACMADUSHR        3                 22   3               ACMCDUSHR        1                169l  3               ACMCMUSHR        1                145g  I               ACMTDUSHR________1________________299______________________c  H               For each of these images, the following DCL commands exist                in ACMS_SETUP.COM:  %               $! IMAGE_NAME = "image"r$               $! GOSUB INSTALL_IMAGE  H               To install these images during the next ACMS startup, editH               the command lines by removing the exclamation point (!) in               each line.  -         4.3.3 ACMS System Management Commandsr  D               ACMS_SETUP.COM can also be used to execute ACMS systemB               management commands that prepare the ACMS system forG               work. These commands might include starting applications,kH               enabling ACMS operator terminals, starting the Queued Task,               Initiator (QTI), and so forth.  I               Examples of these commands are included at the end of ACMS_i               SETUP.COM:                      I                                                 After Installing ACMS 4-7  i  y           After Installing ACMS      4.3 Editing ACMS_SETUP.COM    S           $!** Start the ACMS system (delay terminal startup until applications are            $!** started)a+           $! ACMS/START SYSTEM /NOTERMINALS            $!S           $!** Set ACMS operator terminals; if more than one, place them within theaC           $!** parentheses and separate with commas, eg (OPA0,TTA2)Y6           $! ACMS/SET SYSTEM /OPERATOR/TERMINAL=(OPA0)           $!.           $!** Start the Queued Task Initiator           $! ACMS/START QTIc           $!I           $!** Start task queues; if more than one, separate with commas, !           $!** eg QUEUE_1,QUEUE_2t$           $! ACMS/START QUEUE QUEUE1           $!O           $!** Start ACMS applications; if more than one, separate with commas, -           $!** eg APPLICATION_1,APPLICATION_2a1           $! ACMS/START APPLICATION APPLICATION_1            $!#           $!** Start ACMS terminals.!           $! ACMS/START TERMINALS   >           Edit this section of ACMS_SETUP.COM by inserting theA           commands necessary to complete the startup of your ACMS0           system.   !     4.4 Modifying ACMS Parametersi  :           After installing ACMS, run the ACMSPARAM.COM andD           ACMEXCPAR.COM command procedures to determine ACMS quotas,=           parameters, and privileges. There is no need to runeC           ACMEXCPAR.COM after a new installation until applications            have been installed.  C              ________________________ Note ________________________C  B              Compaq strongly recommends that you use ACMSPARAM.COMC              and ACMEXCPAR.COM. Otherwise, you might not be able to               start ACMS.  C              ______________________________________________________   ?           These command procedures perform the following tasks:C  B           o  Calculate the minimum settings for the OpenVMS SYSGEN*              parameters that ACMS affects.       4-8 After Installing ACMSh t  v      I                                                     After Installing ACMSwI                                             4.4 Modifying ACMS Parameters     E               o  Assign privileges and quotas required for user names =                  under which the ACMS run-time processes run.   E               o  Assign privileges and quotas required for user names_.                  under which applications run.  I               ACMSPARAM.COM and ACMEXCPAR.COM do not support logical name ;               search lists for the TDB file specifications.o  D               Refer to Compaq ACMS for OpenVMS Managing ApplicationsG               for information on how to use the ACMSPARAM and ACMEXCPARe!               command procedures.   A               Certain conditions require attention to adjust ACMS                parameter values:   D               o  ACMSPARAM.COM might generate an excessive PGFLQUOTA*                  value for the CP account.  H                  The current formula for calculating the PGFLQUOTA valueG                  of the CP account is liberal. The formula assumes that E                  each exchange step involves the sending or receiving D                  of the largest message. (See the description of theD                  LARGEST_MESSAGE variable in Compaq ACMS for OpenVMS(                  Managing Applications.)  C                  After executing ACMSPARAM.COM, review the value ofgE                  CP_PGFLQUOTA. If its value appears to be excessively F                  large, then replace the LARGEST_MESSAGE variable withG                  the average size of workspaces used in exchange steps,wE                  or with the size of the workspace most often used inn                   exchange steps.  F                  The formula for calculating the CP_PGFLQUOTA providesF                  only a rough approximation of the quota. To fine-tuneE                  your system, calculate the quota for your particularr                  system.  C               o  ACMS operator commands may fail with the INVACMPARo                  error.   D                  During a new installation of ACMS, the installationA                  procedure resets the ACMSGEN parameters to their E                  default values. If the value of the SYSGEN parameteryE                  MAXPROCESSCNT is too large, the default size of MSS_nD                  POOLSIZE can be too low to allow ACMS to start. TheC                  following error is reported when any ACMS operator $                  command is entered:  I                                                 After Installing ACMS 4-9a p  o           After Installing ACMSw!     4.4 Modifying ACMS Parametersu    H              -ACMSMSS-E-INVACMPAR, The system MSS parameters are invalid  E              Enter the following commands to reset MSS_POOLSIZE - you C              might need to set MSS_POOLSIZE to be larger, dependingt+              on the value of MAXPROCESSCNT:                 $ MCR ACMSGEN              USE CURRENT"              SET MSS_POOLSIZE 1024              WRITE CURRENT  ?     4.5 Authorizing Applications, Devices, Users, and Processes   @           ACMS provides utilities to specify which applications,B           terminals, users, and agent programs can access the ACMSB           system. The following sections describe these utilities.  &     4.5.1 Authorizing New Applications  >           Run the ACMS Application Authorization Utility (AAU)A           to authorize any new ACMS applications that you plan to D           install. AAU allows you to authorize applications, specify@           application user name restrictions, and define who canA           install those applications. You must restart ACMS aftere*           installing any new applications.  ;           Users who have been authorized by AAU can use the_B           ACMS/INSTALL operator command to install applications inD           ACMS$DIRECTORY. By default, no users are authorized to use,           the ACMS/INSTALL operator command.  C           Use of AAU is optional; however, it can simplify and easeiC           the application management process during the developmentr*           and maintenance of applications.  C           For information on using AAU, see Compaq ACMS for OpenVMSi            Managing Applications.  #     4.5.2 Authorizing New Terminalse  C           If you have new terminals to authorize or modify, run themA           Device Definition Utility (DDU) to authorize either all B           terminals (with $ALL) or individual terminals (by device#           name) for access to ACMS:        4-10 After Installing ACMS c  c      I                                                     After Installing ACMS I               4.5 Authorizing Applications, Devices, Users, and ProcessesT    &               $ SET DEFAULT SYS$SYSTEM               $ RUN ACMSDDUn               DDU> ADD $ALLm               DDU> EXITf  G               For information on using DDU, see Compaq ACMS for OpenVMS $               Managing Applications.  F                 ________________________ Note ________________________  E                 Users on your system cannot sign in to ACMS until youH5                 authorize $ALL or specific terminals.   F                 ______________________________________________________  #         4.5.3 Authorizing New Userse  C               If you have new users to authorize, run the ACMS UserdG               Definition Utility (UDU) to authorize ACMS users. You canSH               either authorize all users (with $ALL) or individual users               (by name):  &               $ SET DEFAULT SYS$SYSTEM               $ RUN ACMSUDU                UDU> ADD $ALLA               UDU> EXIT   G               For information on using UDU, see Compaq ACMS for OpenVMS $               Managing Applications.  F                 ________________________ Note ________________________  E                 Users on your system cannot sign in to ACMS until you.6                 authorize $ALL or specific user names.  F                 ______________________________________________________  (         4.5.4 Authorizing ACMS Processes  E               You must authorize the user name of any task-submitting.E               agent program that submits a task for processing with anG               user name other than the user name of that agent. Use theCI               /AGENT qualifier with the UDU ADD command to authorize this F               type of agent. For example, use the following command to;               authorize an agent with the user name SYSTEM:   I                                                After Installing ACMS 4-11  h  C           After Installing ACMS ?     4.5 Authorizing Applications, Devices, Users, and Processese               $ RUN ACMSUDUs            UDU> ADD SYSTEM /AGENT5           User SYSTEM  has been added to the databaset  @           Both the ACMS Command Process (CP) and the Queued TaskC           Initiator (QTI) must be authorized as agents. By default,gA           ACMS assigns the user name SYSTEM to the CP and QTI. IfRE           you change the user name of the CP or QTI with ACMSGEN, younD           must run the UDU again, using the RENAME command to change6           the user name in the UDU authorization file.  =           For information on UDU, see Compaq ACMS for OpenVMS             Managing Applications.                                                                     4-12 After Installing ACMS           I                                                     After Installing ACMS-I               4.5 Authorizing Applications, Devices, Users, and Processesv    F                 ________________________ Note ________________________  D                 The ACMSPARAM.COM procedure automatically authorizesE                 the user names of the CP and QTI as agents (using the E                 /AGENT qualifier) in the ACMS user authorization filelB                 ACMSUDF.DAT. The ACMSPARAM command procedure takesE                 either the user name you supply or supplies a defaultnD                 user name. The default user name supplied for the CPF                 is ACMS$CP. The default user name supplied for the QTI                 is ACMS$QTI.  F                 ______________________________________________________  5         4.6 Creating and Modifying ACMS User Accounts   A               Each person who uses ACMS on your system must be an B               authorized OpenVMS user, with certain privileges andI               quotas. The following sections describe these requirements.lD               (See Compaq ACMS for OpenVMS Managing Applications forH               quotas required for users running the ACMS Task Debugger.)           4.6.1 Privileges  F               To use ACMS, each user account must have at least TMPMBXF               and NETMBX privileges. Those persons who are responsibleF               for starting the ACMS system, starting applications, andG               using other ACMS operator commands must have OpenVMS OPERAG               privilege. Use the OpenVMS Authorize Utility to determinen=               whether users have the privileges they require.i           4.6.2 Quotas  ?               Make sure that the appropriate user accounts have_A               sufficient quotas to be able to use ACMS. Table 4-4C:               summarizes the required user account quotas.  I               Table_4-4_User_Account_Quotas______________________________   I               Account_Quota____Value_( )_________________________________   &               ASTLM                 24  &               BIOLM                 18  I                                                  (continued on next page)   I                                                After Installing ACMS 4-13e x  n           After Installing ACMS 1     4.6 Creating and Modifying ACMS User Accountsi    E           Table_4-4_(Cont.)_User_Account_Quotas______________________   E           Account_Quota____Value_( )_________________________________   "           BYTLM             10,240  "           DIOLM                 22  "           ENQLM                100  "           FILLM                 50  "           PRCLM                  2  "           WSDEF                256  "           WSEXT              1,024  "           WSQUO                512  E           PGFLQUO___________12,800___________________________________h  D           User account quotas are stored in the file SYSUAF.DAT. UseA           the Authorize Utility to verify and change user accountYE           quotas. First set your directory to SYS$SYSTEM and then run            AUTHORIZE:  "           $ SET DEFAULT SYS$SYSTEM           $ RUN AUTHORIZEn           UAF>  E           At the AUTHORIZE prompt (UAF>), enter the SHOW command with E           an account name to check a particular account. For example:              UAF> SHOW SMITHc  A           To change a quota, enter the MODIFY command at the UAF>e>           prompt. The MODIFY command has the following format:  -           MODIFY account-name/quota-name=nnnn   E           The following example changes the FILLM quota for the SMITHC2           account and then exits from the utility:  $           UAF> MODIFY SMITH/FILLM=50           UAF> EXIT   =           After you exit from the utility, the OpenVMS systemaB           displays messages indicating whether or not changes wereD           made. Once you have finished making the changes, the usersB           must log out and log in again for the new quotas to take           effect.a       4-14 After Installing ACMS    l      I                                                     After Installing ACMS I                             4.6 Creating and Modifying ACMS User Accounts     C               For more information on modifying account quotas, see E               the description of the Authorize Utility in the OpenVMSr@               documentation on system management and operations.  8         4.7 Setting up ACMS on an OpenVMS Cluster System  D               Because ACMS treats an OpenVMS Cluster system as if itG               were a local area network, you must perform the following(5               operations on each node of the cluster:   F               o  Define proxy accounts for users on other nodes of the                  cluster._  F                  ACMS does not recognize the common security domain ofH                  a homogeneous OpenVMS Cluster system. As a consequence,F                  you must define proxy accounts on each node for usersF                  on other nodes of the cluster. You can use ACMSGEN toE                  assign a default proxy user name (with the USERNAME_AB                  DEFAULT parameter of ACMSGEN), or use the ACMSUDUG                  utility to define individual ACMS proxy user names forrF                  submitters. Refer to Compaq ACMS for OpenVMS ManagingF                  Applications for more information on using ACMSUDU to*                  create submitter proxies.  H               o  Issue a LICENSE LOAD command on each node that will run                  ACMS.  G                  If you are installing ACMS in a cluster, you must loadHI                  the ACMS license on each node that will use the product._                  For example:c  $                  $ LICENSE LOAD ACMS  B               o  Replace the DCL tables on each node. For example:  6                  $ INSTALL REPLACE SYS$SHARE:DCLTABLES  F               o  Execute ACMS startup procedure on each node that will'                  run ACMS. For example:h  -                  $ @SYS$STARTUP:ACMSSTART.COM   8               o  Set up node-specific ACMSPAR.ACM files.  B                  If you are installing ACMS in a cluster, you mustA                  make sure that the ACMSPAR.ACM parameter file iseD                  in the directory SYS$SPECIFIC:[SYSEXE], rather thanA                  SYS$COMMON:[SYSEXE] before setting the NODE_NAMEt@                  parameter. Do this on each node of the cluster,C                  because each node has a different DECnet node namee  I                                                After Installing ACMS 4-15                 After Installing ACMS 4     4.7 Setting up ACMS on an OpenVMS Cluster System    A              and, therefore, each must have its own node-specifictC              ACMSPAR.ACM file. See Section 4.8 for more information 0              on setting the NODE_NAME parameter.  ,     4.8 Enabling Distributed ACMS Processing  B           By default, ACMS does not enable distributed processing.E           If submitters on your node need to select tasks in a remote C           application, or if remote submitters need to select tasks @           in an application on your node, you must set the NODE_D           NAME parameter in ACMSGEN to your node name. (This step isB           usually necessary only for new installations, not system!           upgrades.) For example:   "           $ RUN SYS$SYSTEM:ACMSGEN%           ACMSGEN> SET NODE_NAME DOVEa9           ACMSGEN> WRITE SYS$SPECIFIC:[SYSEXE]ACMSPAR.ACMO  ;           For more information about using ACMSGEN and ACMS =           distributed processing, see Compaq ACMS for OpenVMS/            Managing Applications.  &     4.9 Rebuilding the LSE Environment  <           If the DECtp Implementation Toolkit for OpenVMS isB           installed on your system, you must rebuild the toolkit'sA           LSE environment and section files after installing ACMS E           Version 4.4. See the toolkit documentation for instructions 0           on how to rebuild the LSE environment.  (     4.10 Installing ACMS Menu Form Files  D           If you have customized the ACMS menu form definition file,E           you must rebuild the form image file. Use the following DCL E           command file to rebuild and install the new form image file            on the system:  2           $  @SYS$MANAGER:ACMS_BUILD_MENU_FORM.COM  B     4.11 Preparing Language-Specific ACMS Development Environments  :           The following sections describe how to set up anD           environment for developing ACMS agents in BLISS or Pascal.         4-16 After Installing ACMS    t      I                                                     After Installing ACMS I            4.11 Preparing Language-Specific ACMS Development Environments              4.11.1 BLISS Agentsi  I               ACMS Version 4.4 supplies the ACMSBLI.R32 file. If you planuE               to use BLISS agents, see the BLISS-32 documentation foroI               directions on building the BLISS library file (ACMSBLI.L32)uG               from the ACMSBLI.R32 file, and for general information on I               creating library files, and using library files and require                files.  1               ACMSBLI.R32 contains the following:C  D               o  Keyword macros for all the services. The macro nameE                  is the service name prefixed with a dollar sign ($).rD                  The keyword macro for ACMS$SIGN_IN, for example, is                  $ACMS$SIGN_IN.e  C               o  Structure definitions for all IDs. The name of theeI                  structure is the same as the name given in the structureTB                  layouts listed in Compaq ACMS for OpenVMS SystemsD                  Interface Programming. Use these IDs in declaration                  definitions.o  F               o  Miscellaneous symbolic constants used in service call                  arguments.            4.11.2 Pascal Agents  D               ACMS Version 4.4 supplies the ACMSPAS.PAS file. If youH               plan to use Pascal agents, you must compile this file intoG               an environment file. See the VAX Pascal documentation for I               directions on building the environment file (.PEN) from the E               ACMSPAS.PAS file, and on using environment definitions.   1               ACMSPAS.PAS contains the following:s  :               o  Routine definitions for all the services.  G               o  Record definitions for all IDs. The name of the record D                  is the same as the name given in the structure listA                  in the Compaq ACMS for OpenVMS Systems Interface <                  Programming. Use these IDs in declarations.  F               o  Miscellaneous symbolic constants used in service call                  arguments.   F                 ________________________ Note ________________________  E                 If you use the nonpositional syntax form of parameterS@                 association, you must use PROCEDURE_ rather than  I                                                After Installing ACMS 4-17t t  .           After Installing ACMSeB     4.11 Preparing Language-Specific ACMS Development Environments    A              PROCEDURE as the formal parameter name for ACMS$GET_tA              PROCEDURE_INFO, because PROCEDURE is a reserved word @              in Pascal. See VAX Pascal Reference Manual for more              information.a  C              ______________________________________________________O  +     4.12 Determining and Reporting ProblemsS  B           Installing ACMS changes the state of your system. RecordB           any changes to the system in your system management log.E           If an error occurs while ACMS is being used and you believe.D           that the error is caused by a problem with ACMS, contact a?           Compaq Customer Support Center to report the problem.                                                                    4-18 After Installing ACMS o  d                    I                                                                         5pI         _________________________________________________________________p  I                                                      Running the ACMS IVPa    A               This chapter describes how to run the ACMS software B               Installation Verification Procedure (IVP) separatelyF               from the installation procedure. The IVP checks that theH               installation procedure has successfully installed the ACMSE               software, and that the software can create and run ACMS                applications.o  F               The IVP can be run as a part of the normal installation.I               However, if the automatic IVP fails for any reason, correctl3               the error and then run the IVP again.   A               You can also execute the IVP to verify that ACMS is D               functioning properly after your system environment hasH               changed; for example, after you have installed or upgradedI               another layered product that ACMS uses, such as DECforms ort               Rdb.            5.1 Functions of the IVP  B               Table 5-1 lists the tests performed by the ACMS IVP.E               The full set of tests is performed if you installed the E               development kit; subsets are performed for the run-time I               kit with CDD, the run-time kit without CDD, and the remote-                access kit.L  F                 ________________________ Note ________________________  >                 If disk quotas are enabled, the IVP fails. The<                 installation procedure checks to see if disk?                 quotas are enabled. If disk quotas are enabled,_D                 the installation procedure displays an informationalE                 message to that effect and continues. See Section 2.5i4                 for more information on disk quotas.  F                 ______________________________________________________  I                                                  Running the ACMS IVP 5-1  e  i           Running the ACMS IVP     5.1 Functions of the IVP    E     Table_5-1_ACMS_IVP_Tests_________________________________________   6                                                   Run-E                                       Run-Time    Time Kit    Remote- D                             DevelopmenKit with    Without     AccessE     Test_Description________Kit[1]____CDD[1]______CDD_________Kit____   ?     Check ACMS files        +         +           +           +        Define tasks and task   +n
     groups  '     Define application      +         +z  3     Link procedure server   +         +           +_	     image_  ?     Update DDF and UDF      +         +           +           +C	     filess  ?     Create ACMSPAR file     +         +           +           +i  ?     Start ACMS system       +         +           +           +i  3     Start application       +         +           +   3     Select tasks            +         +           +i       Test ACMS debugger      +a  ?     Test Queued Task        +         +           +           +o
     Initiator   ?     Test queue manager      +         +           +           +   ?     Stop ACMS system        +         +           +           +SE     [1]The_IVP_may_fail_if_a_DECdtm_log_file_is_not_present_on_the___p  D     system. CDD uses DECdtm, and, therefore, that portion of the IVPD     that builds the IVP task group and application is subject to theB     requirements of CDD and DECdtm. If you are installing the ACMS@     Remote-Access kit or the ACMS Run-Time kit without CDD, thisA     error cannot occur. If the IVP fails, refer to Appendix D forE2     directions on how to create a transaction log.E     _________________________________________________________________U       5.2 Running the IVPm  E           To run the IVP independently of the installation procedure,            follow these steps:U  <           1. Log in to the system manager's account, SYSTEM:       5-2 Running the ACMS IVP           I                                                      Running the ACMS IVP I                                                       5.2 Running the IVP     "                  Username:  SYSTEM                  Password:                  2. Shut down ACMS.  I                  You cannot run the IVP if ACMS is active on your system.cF                  To shut down ACMS, enter the following command at the                  DCL prompt:  *                  $ ACMS/STOP SYSTEM/CANCEL  @               3. Set your default to SYS$SYSROOT:[SYSTEST.ACMS]:  9                  $ SET DEFAULT SYS$SYSROOT:[SYSTEST.ACMS]a  B               4. Run the ACMS Installation Verification Procedure,                  ACMSIVP.COM.h  ?                  To start the IVP, enter the following command:r                    $ @ACMSIVPM  A               The IVP checks for the presence of the user account_C               ACMS$IVP. If the account does not exist, the IVP asks F               you for a user identification code (UIC) and password soF               that it can create the account. Refer to Section 2.9 andI               Section 3.2.2 for more information on creating the ACMS$IVP                account.  G               Section 2.8 contains information on the time necessary tos               execute the IVP.  "         5.3 Errors Running the IVP  G               When the IVP is run automatically during the installation ;               of ACMS, all output from the IVP is logged inbG               SYS$UPDATE:ACMSIVP.LOG. When the IVP is run manually, alld2               output is displayed on the terminal.  E               If the IVP detects an error, it provides an appropriateeF               error message. This message includes a suggested action,F               such as stopping the ACMS system and reinvoking the IVP.I               If the suggested action does not fix the problem, reinstallb               ACMS.   I                                                  Running the ACMS IVP 5-3     l           Running the ACMS IVP     5.3 Errors Running the IVP    D           IVP Can Fail with INVACMPAR Error When MSS_POOLSIZE Is Too
           LowS  D           When you run the IVP, it resets all the ACMSGEN parameters=           to their default values. If the value of the SYSGEN B           parameter MAXPROCESSNT is too large, the default size ofA           MSS_POOLSIZE can be too low to allow ACMS to start. The D           following error is reported when any ACMS operator command           is entered:a  E           -ACMSMSS-E-INVACMPAR, The system MSS parameters are invalid_  B           To run the IVP, include the following in the ACMSIVP.COMB           file, which is located in the subdirectory [.ACMS] underD           SYS$TEST - you might need to set the value of MSS_POOLSIZE@           to be larger, depending on the value of MAXPROCESSCNT:             $ MCR ACMSGEN            USE DEFAULT5           SET MSS_POOLSIZE 1024_#           SET ACC_USERNAME ACMS$IVP_              .              .              .       5.4 Sample IVP Execution  E           This section contains a sample manual execution of the ACMS 1           IVP for the ACMS Alpha development kit.d  D         Starting the ACMS V4.4-0 Installation Verification Procedure!           at 11:13 on 22-JUN-2001   5         The IVP is testing a development installation                            5-4 Running the ACMS IVP e  a      I                                                      Running the ACMS IVPcI                                                  5.4 Sample IVP Execution     !             (Checking privileges):2             (Checking for existing ACMS processes)4             (Checking for execution of ACMSTART.COM)$             (Checking ACMS logicals)(             (Checking ACMS system files)>             (Checking CDD directory CDD$TOP.ACMS$DIR.ACMS$IVP)1             (Defining IVP's tasks and task group)e(         %ACMSTDU-I-WRITETDB, Writing TDB4         -ACMSTDU-I-BYTESWRIT,  3584 bytes (7 blocks)U         %ACMSTDU-I-OBJMODCRE, Procedure server 'GROUP1_SERVER1' object module createdo?         in file 'SYS$COMMON:[SYSTEST.ACMS]GROUP1_SERVER1.OBJ;3's(             (Defining IVP's application)(         %ACMSCDU-I-WRITEADB, Writing ADB4         -ACMSCDU-I-BYTESWRIT,  1824 bytes (4 blocks)"             (Linking server image)%             (Updating IVP's DDF file)a%             (Updating IVP's UDF file) )             (Creating IVP's ACMSPAR file)i"             (Starting ACMS system)/             (Starting ACMS application ACMSIVP)a%             (Checking ACMS processes)n#             (Selecting IVP's tasks) S         ACMS V4.4-0   Current System State: STARTED   Time: 22-JUN-2001 11:15:19.65c  ,         Terminal Subsystem State:    STARTED,         Queued Task Initiator State: STOPPED,         System Auditing State:       ENABLED           Active ACMS Userse  @         User Name      Submitter ID        Agent PID      Device?         SYSTEM         00010014            28A00CBB       RTA5:m  $         Active Execution Controllers  U         Application Name                   Process Name        User Name      Exc PID V         ACMSIVP                            ACMS01EXC001000     ACMS$IVP       28A00CD9  '             (Testing the ACMS Debugger)A4             (Testing the ACMS Queued Task Initiator),             (Testing the ACMS Queue Manager)&             (Stopping the ACMS system)  E             ACMS V4.4-0 Installation Verification Procedure completeda0             successfully at 11:15 on 22-JUN-2001               (Cleaning up)   I                                                  Running the ACMS IVP 5-5L    m           Running the ACMS IVP     5.4 Sample IVP Execution         $ LOGOUT8       SYSTEM       logged out at 22-JUN-2001 11:16:07.07                                                                                           5-6 Running the ACMS IVP    L                    I                                                                         6 I         _________________________________________________________________e  I                                                         Deinstalling ACMSr    F               This chapter describes the process of deinstalling ACMS.  G                 _______________________ Caution _______________________   F                 The deinstallation of ACMS removes all ACMS files fromD                 your system, including customer-written applications"                 in ACMS$DIRECTORY.  F                 ______________________________________________________  I               Deinstallation is necessary only if you no longer need ACMScG               on your system and you want to release the disk space for                other use.  G               Deinstallation is not necessary if you are upgrading to a.H               new version of ACMS. When you upgrade, obsolete ACMS filesG               are deleted and superseded files are purged automaticallyl,               by the installation procedure.  1         6.1 Starting the Deinstallation Procedure.  F               To invoke the ACMS deinstallation procedure, execute the                following command:  .               $ @SYS$UPDATE:ACMS_DEINSTALL.COM  H               The deinstallation procedure asks if you want to continue.G               The default answer is NO; you must answer YES <Return> tot               continue.p  C               The deinstallation procedure then does the following:   '               1. Stops the ACMS system.y  6               2. Deinstalls all ACMS installed images.  I               3. Deletes all files and directories known to be created byE'                  the ACMS installation.O  I                                                     Deinstalling ACMS 6-1i i  e           Deinstalling ACMS -     6.1 Starting the Deinstallation Procedure     E           4. Checks the system disk for any other files that might bet              related to ACMS.   ?           If files are found that might be related to ACMS, the C           deinstallation procedure lists them on your terminal. You D           can review any files listed in this manner and delete themD           manually, or you can reinvoke the deinstallation procedureE           to delete them automatically. Execute the following commandf.           to delete these files automatically:  F           $ @SYS$UPDATE:ACMS_DEINSTALL.COM DELETE_SUSPECTED_ACMS_FILES  %     6.2 Completing the Deinstallation   =           The ACMS deinstallation procedure removes all filesDC           related to ACMS from the system. However, to complete thenE           deinstallation of ACMS, you might also want to perform someu0           or all of the following cleanup steps:  C           o  Deassign all ACMS logical names (on each node if in an *              OpenVMS Cluster environment).  B           o  Delete the ACMS$IVP account from the SYSUAF database.  B           o  Remove any OpenVMS proxies granted to former users of:              ACMS who no longer need access to the system.  @           o  Delete the ACMS deinstallation command procedure by-              executing the following command:t  5              $ DELETE SYS$UPDATE:ACMS_DEINSTALL.COM;*                                  6-2 Deinstalling ACMSi r  i                    I                                                                         A I         _________________________________________________________________   I                                                      Sample Installationsi    E               This appendix contains sample installations of the ACMSk               development kits.r  A               These samples represent typical installations. ManyrG               variations are possible, based on the OpenVMS version anduD               the presence of other layered products on your system.  =         A.1 OpenVMS Alpha Development Kit Sample Installation   E               This section contains a sample installation of the ACMSfH               Version 4.4 for OpenVMS Alpha development kit. The detailsD               of your actual installation may be somewhat different.  >               $ @sys$update:vmsinstal ACMSDEVA_044 dua0:[kits]  G                OpenVMS AXP Software Product Installation Procedure V7.3l  )               It is 22-JUN-2001 at 09:22.e  =               Enter a question mark (?) at any time for help.uL               %VMSINSTAL-W-ACTIVE, The following processes are still active:                      _RTA2:n8               * Do you want to continue anyway [NO]? YESL               * Are you satisfied with the backup of your system disk [YES]?  7               The following products will be processed:c                 ACMSDEVA_ V4.4  @                Beginning installation of ACMSDEVA_ V4.4 at 09:22  D               %VMSINSTAL-I-RESTORE, Restoring product save set A ...Y               %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.i  >               COPYRIGHT (c) 1999  Compaq Computer Corporation.#                All Rights Reserved._>                Unpublished rights reserved under the copyright)                laws of the United States.s  I                                                  Sample Installations A-1                 Sample Installations9     A.1 OpenVMS Alpha Development Kit Sample InstallationP    >            The software contained on this media is proprietary9            to and embodies the confidential technology oft9            Compaq Computer Corporation.  Possession, use,v;            duplication or dissemination of the software andn?            media is authorized only pursuant to a valid written_4            license from Compaq Computer Corporation.  @            RESTRICTED RIGHTS: Use, duplication, or disclosure by@            the U.S. Government is subject to restrictions as setB            forth in Subparagraph (c)(1)(ii) of DFARS 252.227-7013,.            or in FAR 52.227-19, as applicable.  ?           The results of this installation are being logged in:t7             SYS$COMMON:[SYSUPD]ACMS044_INSTALLATION.LOGe  1           Installing ACMS V4.4-0, development kit   U               There are five optional parts to the ACMS development kit installation:   ,                   o  ACMS component software$                   o  ACMS LSE update!                   o  ACMS samples_3                   o  ACMS Request Interface samples ,                   o  ACMS WBEM related files  =               The full installation includes all these parts.rQ               If ACMS component software is selected, the ACMS WBEM related files "               will also be copied.  Y               To install the ACMS samples or the ACMS Request Interface samples, you mustCQ               install, or have previously installed, the ACMS component software.   <           * Do you want the full ACMS installation [NO]? YES  -           CHECKING INSTALLATION PREREQUISITESe-           -----------------------------------   U           The following software products are not available, or are below the minimuml           required version:t  L             Product               Required  Minimum version  Current VersionL             --------------------  --------  ---------------  ---------------D             LSE                   No        V4.3             V4.2-17  X               If products marked as nonrequired are to be used with ACMS, they should beL               upgraded to at least the minimum version displayed before use.  6               (required and optional software checked)  (               (product licenses checked)       A-2 Sample Installations    -      I                                                      Sample Installations I                     A.1 OpenVMS Alpha Development Kit Sample Installation     5               The following images are not installed:   W                 Product          Image                      Required  Startup ProceduredZ                 ---------------  -------------------------  --------  --------------------U                 DECtrace         VMI$ROOT:[SYSLIB]EPC$FUNC  No        EPC$STARTUP.COM   ^                   The images marked as required must be installed before this installation can\                   be successfully completed. These images are usually installed by executingY                   the product's startup procedure. For more information, refer to productCL                   specific documentation and the VMS INSTALL Utility Manual.  ,                   (installed images checked)  &                   (privileges checked)  &                   (disk space checked)  '                   (disk quotas checked)s  -                   (system parameters checked)_  2                   (process account quotas checked)  (               ACMS PREVIOUS INSTALLATION(               --------------------------  :                   (no previous installation of ACMS found)                 ACMS LSE CHECK               --------------  >                   (LSE available and will be updated for ACMS)                 ACMS WBEM CHECK                ---------------i  %               ACMS Oracle Trace CHECK !               -------------------t  ]                   Oracle Trace is not being updated for ACMS because it is not available, not 1                   started, or Rdb is not started.Q  \                   The ACMS facility definition will be stored in SYS$SHARE:EPC$FACILITY.TLB.Y                   For more information on inserting this definition into the Oracle Trace S                   administrative database, refer to the Oracle Trace documentation.e  #               ACMS OLD SAMPLE FILESd#               ---------------------   -                   (no old sample files found)n  I                                                  Sample Installations A-3     S           Sample Installations9     A.1 OpenVMS Alpha Development Kit Sample Installation                ACMS SHUTDOWN CHECK            -------------------o  Q               ACMSTOP.COM was not found. If ACMS was previously installed on this_K               system, make sure it is shut down before proceeding with thise               installation.e  )           ACMS POSTINSTALLATION PROCEDURE )           -------------------------------o  W               (postinstallation procedure will be run automatically after installation)   U               Please read the chapter After Installing ACMS, in the ACMS Installation U               Guide, for manual tasks that you should consider after installing ACMS.P  !           ACMS SYSTEM ROOTS CHECKn!           -----------------------o  D               (no ACMS-related files found in system-specific roots)             ACMS IVP           --------  Q           * Do you want to execute the Installation Verification Procedure [YES]?   0               Checking IVP user account ACMS$IVP  J             The ACMS$IVP account used to execute the IVP is not available.  S               You must supply a UIC and password for this account so that it can beMH               created; this must be done before the IVP can be executed.  W               Please enter the UIC for the ACMS$IVP account, in the form [ggggg,nnnnnn]e             * UIC: [11,100]   J               Please enter a password of at least 8 characters, using onlyN               the following characters: ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789$_             * Password:S           * Verification:   +           SUMMARY OF THIS ACMS INSTALLATIONg+           ---------------------------------   N               The following steps will be taken to complete this installation:       A-4 Sample Installations r  s      I                                                      Sample InstallationssI                     A.1 OpenVMS Alpha Development Kit Sample Installation     T                   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 P                   o  Oracle Trace facility text library will be updated for ACMS=                   o  CDD-related ACMS files will be installed 3                   o  ACMS samples will be installed E                   o  ACMS Request Interface samples will be installedII                   o  The ACMS postinstallation procedure will be executedA2                   o  The ACMS IVP will be executed  Q                   The rest of the installation will take approximately 7 minutes.eI                   Execution of the IVP will take approximately 2 minutes.E  U                   Note that this time is heavily dependent your system load, hardwareMZ                   and kit media. The time mentioned was measured on a stand-alone DEC 3000O                   (Alpha) system with a disk-resident kit.  Your time may vary.r  ?               * Do you want to continue the installation [YES]?e  \               The interactive portion of this installation is complete; no further questions8               will be asked until the post installation.  .                   Installation of ACMS started,                     at 09:30 on  22-JUN-2001  $                   Restoring savesetsD               %VMSINSTAL-I-RESTORE, Restoring product save set J ...D               %VMSINSTAL-I-RESTORE, Restoring product save set K ...D               %VMSINSTAL-I-RESTORE, Restoring product save set L ...D               %VMSINSTAL-I-RESTORE, Restoring product save set M ...D               %VMSINSTAL-I-RESTORE, Restoring product save set N ...D               %VMSINSTAL-I-RESTORE, Restoring product save set O ...D               %VMSINSTAL-I-RESTORE, Restoring product save set P ...D               %VMSINSTAL-I-RESTORE, Restoring product save set R ...                    I                                                  Sample Installations A-5  C  k           Sample Installations9     A.1 OpenVMS Alpha Development Kit Sample Installation     0               Checking/creating ACMS directoriesI           %VMSINSTAL-I-SYSDIR, This product creates system disk directoryk0             VMI$ROOT:[SYSHLP.EXAMPLES.ACMSMGMT].I           %VMSINSTAL-I-SYSDIR, This product creates system disk directory,$             VMI$ROOT:[SYSTEST.ACMS].I           %VMSINSTAL-I-SYSDIR, This product creates system disk directoryr.             VMI$ROOT:[SYSHLP.EXAMPLES.ACMSSI].I           %VMSINSTAL-I-SYSDIR, This product creates system disk directoryf,             VMI$ROOT:[SYSHLP.EXAMPLES.ACMS].I           %VMSINSTAL-I-SYSDIR, This product creates system disk directory /             VMI$ROOT:[SYSHLP.EXAMPLES.ACMS.RI].U               Updating LSE;               Updating Oracle Trace definition text libraryV;               Deleting old CDD$TOP.ACMS$DIR.ACMS$WORKSPACES 7               Creating CDD$TOP.ACMS$DIR.ACMS$WORKSPACESC1               Deleting old RI sample CDD nodes...P:               Restoring RI sample application CDD nodes...T           %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named ACMS$IVP.7           %UAF-I-ADDMSG, user record successfully addedtV           %UAF-I-RDBADDMSGU, identifier ACMS$IVP value [000011,000100] added to rights             database  &               Account ACMS$IVP created  =               Updating account ACMS$IVP to current parameterseT           %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named ACMS$IVP.0           %UAF-I-MDFYMSG, user record(s) updatedT           %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named ACMS$IVP.0           %UAF-I-MDFYMSG, user record(s) updatedT           %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named ACMS$IVP.0           %UAF-I-MDFYMSG, user record(s) updatedT           %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named ACMS$IVP.0           %UAF-I-MDFYMSG, user record(s) updated  &               Account ACMS$IVP updated  E               ACMS$IVP account created/updated -- IVP selected to run.               Providing files 0               Provided DCL command file ACMS.CLD1               Provided DCL help file ACMSHELP.HLP 3               All other files provided - list is in H                 JDIDIT$DKB200:[SYS0.SYSCOMMON.][SYSEXE]ACMS044_FILES.DAT  9               Installation of ACMS completed successfully (                 at 09:34 on  22-JUN-2001       A-6 Sample Installations           I                                                      Sample Installations I                     A.1 OpenVMS Alpha Development Kit Sample Installation     \               %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...  >               COPYRIGHT (c) 1999  Compaq Computer Corporation.#                All Rights Reserved.o>                Unpublished rights reserved under the copyright)                laws of the United States._  B                The software contained on this media is proprietary=                to and embodies the confidential technology ofa=                Compaq Computer Corporation.  Possession, use, ?                duplication or dissemination of the software and C                media is authorized only pursuant to a valid written 8                license from Compaq Computer Corporation.  D                RESTRICTED RIGHTS: Use, duplication, or disclosure byD                the U.S. Government is subject to restrictions as setF                forth in Subparagraph (c)(1)(ii) of DFARS 252.227-7013,2                or in FAR 52.227-19, as applicable.  9                   ACMS postinstallation procedure startedy,                     at 09:36 on  22-JUN-2001  U                        ************************************************************** U                        *                                                            *AU                        *  NOTE: Refer to Chapter 4 in the ACMS Installation Guide   * U                        *         for other important postinstallation work.         * U                        *                                                            * U                        **************************************************************r  6               Checking/creating logical ACMS$DIRECTORY6               ----------------------------------------  Z                 The procedure checks for the logical ACMS$DIRECTORY, which must be definedQ                 /SYSTEM /SUPERVISOR and must point to an existing disk directory.t  G                   ACMS$DIRECTORY is defined as SYS$SYSDEVICE:[ACMS.ADB]n9                   SYS$SYSDEVICE:[ACMS.ADB] does not existy  +               Do you want to create it [Y]?d  <                   Created directory SYS$SYSDEVICE:[ACMS.ADB]  G                   ACMS$DIRECTORY is defined as SYS$SYSDEVICE:[ACMS.ADB]a6                   ACMS$DIRECTORY logical is acceptable  0               Converting ACMSGEN parameter files0               ----------------------------------  I                                                  Sample Installations A-7o h  o           Sample Installations9     A.1 OpenVMS Alpha Development Kit Sample Installationa    N             This procedure searches for all ACMSGEN parameter files located inM             SYS$SYSDEVICE:[SYS*.SYSEXE] and SYS$COMMON:[SYSEXE], and convertsnN             them to be compatible with the current version of ACMS. If you areL             upgrading from a version of ACMS prior to V4.0, you must perform             this conversion.  F           Do you want to convert existing ACMSGEN parameter files [Y]?  7               Converting SYS$COMMON:[SYSEXE]ACMSPAR.ACM   T               The ACMSGEN parameter files listed above have been converted; if otherT               parameter files exist on your system, they must be updated as follows:  *                   $ RUN SYS$SYSTEM:ACMSGEN1                   ACMSGEN> USE file-specifications3                   ACMSGEN> WRITE file-specification                    ACMSGEN> EXIT   ?                                    (press <RETURN> to continue)r  +           Converting ACMS UDF and DDF fileso+           ---------------------------------   V             The procedure searches for the files pointed to by the ACMSUDF and ACMSDDFO             logicals, if they exist, and then for AMCSUDF.DAT or ACMSDDF.DAT inlS             SYS$SYSROOT:[SYS*], and converts them to be compatible with the currentdW             version of ACMS. If you are upgrading from a version of ACMS prior to V3.1, -             you must perform this conversion.k  E           Do you want to convert existing ACMS UDF and DDF files [Y]?e  '               No files found to convertt  ?                                    (press <RETURN> to continue)   2           Checking/creating ACMS UDF and DDF files2           ----------------------------------------  S             The procedure checks for ACMSUDF.DAT and ACMSDDF.DAT, first through the N             logicals ACMSUDF and ACMSDDF, and then in SYS$COMMON:[SYSEXE], andU             creates them if they're not already present from a previous installation.B  9               No /SYSTEM /EXECUTIVE logical ACMSUDF found 6               SYS$COMMON:[SYSEXE]ACMSUDF.DAT not found5               Creating SYS$COMMON:[SYSEXE]ACMSUDF.DATa  9               No /SYSTEM /EXECUTIVE logical ACMSDDF foundI6               SYS$COMMON:[SYSEXE]ACMSDDF.DAT not found5               Creating SYS$COMMON:[SYSEXE]ACMSDDF.DATg  ?                                    (press <RETURN> to continue)        A-8 Sample Installations           I                                                      Sample InstallationstI                     A.1 OpenVMS Alpha Development Kit Sample Installation     .               Checking/creating ACMS_SETUP.COM.               --------------------------------  Z                 The procedure checks for site-specific startup procedure ACMS_SETUP.COM inT                 SYS$COMMON:[SYS$STARTUP], and creates a template if the file doesn't                 already exist.  A                   Creating SYS$COMMON:[SYS$STARTUP]ACMS_SETUP.COME  H                 ACMS_SETUP.COM will be executed the next time you invokeW                 SYS$STARTUP:ACMSTART.COM. Please review ACMS_SETUP.COM and adjust it to2U                 reflect the needs of your ACMS environment. It can be used to performf2                 these site-specific startup steps::                   - define the ACMS logical ACMS$DIRECTORY>                   - install ACMS utilities as shareable imagesN                   - define ACMS logicals such as ACMS$AUDIT_LOG, ACMS$SWL_LOG,C                     ACMS$NOTICE, ACMS$EDIT, ADU$EDIT and SWLUP$EDITa:                   - start the ACMS system and applications  C                                        (press <RETURN> to continue)d  .               Checking/copying ACMS menu files.               --------------------------------  W                 The procedure checks for the ACMS command menu and default user menu ineW                 ACMS$DIRECTORY, and copies them from SYS$COMMON:[SYSEXE] if they're notuG                 already in ACMS$DIRECTORY from a previous installation.p  ;                   Copying new ACMSCMD.MDB to ACMS$DIRECTORYl8                   Copying new ACMS.MDB to ACMS$DIRECTORY  U                        **************************************************************aU                        *                                                            * U                        *  NOTE: Refer to Chapter 4 in the ACMS Installation Guide   * U                        *         for other important postinstallation work.         * U                        *                                                            *aU                        **************************************************************a  3               Checking/creating ACMS$MGMT_SETUP.COM 3               -------------------------------------           I                                                  Sample Installations A-9                 Sample Installations9     A.1 OpenVMS Alpha Development Kit Sample Installationp    Q                    **************************************************************sQ                    *                                                            * Q                    *  NOTE: Refer to the Managing the Remote Manager chapter    *-Q                    *  in the ACMS Remote Systems Management Guide for more      *SQ                    *  information.                                              *rQ                    *                                                            *sQ                    **************************************************************   P           Do you want to SETUP and CONFIGURE the ACMS Remote System Manager [Y]?  6               Creating SYS$STARTUP:ACMS$MGMT_SETUP.COM  7           Do you want to allow Proxy Authorization [Y]?   Y           (ACMS$MGMT_CONFIG) Enter the file specification for the configuration file used &             by the ACMS Remote ManagerJ           Equivalence string [ SYS$SYSROOT:[SYSEXE]ACMS$MGMT_CONFIG.ACM ]:  X           (ACMS$MGMT_TEMP) Enter the directory where the temp command procedures will be             created <           Equivalence string [ SYS$SPECIFIC:[ACMS_RM.TMP] ]:8                SYS$SPECIFIC:[ACMS_RM.TMP] does not exist  '           Do you want to create it [Y]?u  <                 Created directory SYS$SPECIFIC:[ACMS_RM.TMP]  T           (ACMS$MGMT_LOG) Enter the directory for the ACMS Remote Manager's Log file<           Equivalence string [ SYS$SPECIFIC:[ACMS_RM.LOG] ]:8                SYS$SPECIFIC:[ACMS_RM.LOG] does not exist  '           Do you want to create it [Y]?   <                 Created directory SYS$SPECIFIC:[ACMS_RM.LOG]  O           (ACMS$MGMT_CREDS_DIR) Enter the directory for the ACMS Remote Managers           Credential's>           Equivalence string [ SYS$SPECIFIC:[ACMS_RM.CREDS] ]::                SYS$SPECIFIC:[ACMS_RM.CREDS] does not exist  '           Do you want to create it [Y]?-  >                 Created directory SYS$SPECIFIC:[ACMS_RM.CREDS]  Y           (ACMS$MGMT_SNAPSHOT) Enter the directory where the snapshot data will be storedeA           Equivalence string [ SYS$SPECIFIC:[ACMS_RM.SNAPSHOT] ]:l=                SYS$SPECIFIC:[ACMS_RM.SNAPSHOT] does not exist-  '           Do you want to create it [Y]?        A-10 Sample Installations  t  e      I                                                      Sample InstallationshI                     A.1 OpenVMS Alpha Development Kit Sample InstallationC    E                     Created directory SYS$SPECIFIC:[ACMS_RM.SNAPSHOT]s  ]               (ACMS$MGMT_ERR_LOG) Enter the directory where the Error Log data will be storedhD               Equivalence string [ SYS$SPECIFIC:[ACMS_RM.ERR_LOG] ]:@                    SYS$SPECIFIC:[ACMS_RM.ERR_LOG] does not exist  +               Do you want to create it [Y]?n  D                     Created directory SYS$SPECIFIC:[ACMS_RM.ERR_LOG]  N                 SYS$STARTUP:ACMS$MGMT_SETUP.COM will be executed the next timeV                 SYS$STARTUP:ACMSTART.COM is invoked. Please review ACMS$MGMT_SETUP.COMY                 and adjust it to reflect the needs of your ACMS Remote Systems Managemente                 environment.  D                Creating/Checking the RM Identifiers and SNMP account  5                   Checking for user account ACMS$SNMPo  ?                    Identifier for ACMS$MGMT_READ does not existe  c               %UAF-I-RDBADDMSG, identifier ACMS$MGMT_READ value %X80010087 added to rights database @                    Identifier for ACMS$MGMT_WRITE does not exist  d               %UAF-I-RDBADDMSG, identifier ACMS$MGMT_WRITE value %X80010088 added to rights database?                    Identifier for ACMS$MGMT_OPER does not existA  c               %UAF-I-RDBADDMSG, identifier ACMS$MGMT_OPER value %X80010089 added to rights databaseeA                    Identifier for ACMS$MGMT_SYSUPD does not existr  e               %UAF-I-RDBADDMSG, identifier ACMS$MGMT_SYSUPD value %X80010090 added to rights database   ]                 The ACMS$SNMP account used to execute ACMSMGR SNMP commands is not available.m  W                   You must supply a UIC and password for this account so that it can beaN                   created; this must be done before the $MGMT can be executed.  \                   Please enter the UIC for the ACMS$SNMP account, in the form [ggggg,nnnnnn]                 * UIC: [256,256]  N                   Please enter a password of at least 8 characters, using onlyR                   the following characters: ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789$_                 * Password:l               * Verification:   Y               %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named ACMS$SNMP. ;               %UAF-I-ADDMSG, user record successfully addeda[               %UAF-I-RDBADDMSGU, identifier ACMS$SNMP value [000256,000256] added to rightsp                 database  I                                                 Sample Installations A-11h w  M           Sample Installations9     A.1 OpenVMS Alpha Development Kit Sample Installation0    '               Account ACMS$SNMP createdk  >               Updating account ACMS$SNMP to current parametersU           %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named ACMS$SNMP. 0           %UAF-I-MDFYMSG, user record(s) updatedU           %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named ACMS$SNMP.n0           %UAF-I-MDFYMSG, user record(s) updatedU           %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named ACMS$SNMP.E0           %UAF-I-MDFYMSG, user record(s) updatedU           %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named ACMS$SNMP.O0           %UAF-I-MDFYMSG, user record(s) updated  '               Account ACMS$SNMP updateda  K               Checking config file SYS$SYSROOT:[SYSEXE]ACMS$MGMT_CONFIG.ACM.]           Creating a new Remote Mananger config file SYS$SYSROOT:[SYSEXE]ACMS$MGMT_CONFIG.ACMT  1           %ACMSMGMT-S-NORMAL, Operation completed 1           %ACMSMGMT-S-NORMAL, Operation completede1           %ACMSMGMT-S-NORMAL, Operation completed 1           %ACMSMGMT-S-NORMAL, Operation completed-1           %ACMSMGMT-S-NORMAL, Operation completed 1           %ACMSMGMT-S-NORMAL, Operation completed 1           %ACMSMGMT-S-NORMAL, Operation completeds1           %ACMSMGMT-S-NORMAL, Operation completede1           %ACMSMGMT-S-NORMAL, Operation completedH1           %ACMSMGMT-S-NORMAL, Operation completedI1           %ACMSMGMT-S-NORMAL, Operation completed 1           %ACMSMGMT-S-NORMAL, Operation completedT1           %ACMSMGMT-S-NORMAL, Operation completedt1           %ACMSMGMT-S-NORMAL, Operation completed.1           %ACMSMGMT-S-NORMAL, Operation completede1           %ACMSMGMT-S-NORMAL, Operation completedH1           %ACMSMGMT-S-NORMAL, Operation completedT  W           Entity                                           Entity   Coll     CollectionUR           Name                                             Type     Class    StateW           -----------------------------------------------------------------------------iU            *                                                *        id       enabledPU            *                                                *        config   enabledCV            *                                                *        runtime  disabledV            *                                                *        pool     disabledV            *                                                *        error    disabled  8             The ACMS Remote Manager has been configured.       A-12 Sample InstallationsI C  T      I                                                      Sample Installations I                     A.1 OpenVMS Alpha Development Kit Sample Installationp    U                 The command procedure SYS$STARTUP:ACMS$MGMT_ENV.COM should be invoked V                 to define the symbols for starting the ACMS Remote Manager and running)                 the Remote Manager client   T               Do you want to invoke ACMS$MGMT_SETUP.COM to define the Remote Manager               logicals [Y]?r  0               ACMS Remote Manager Setup Complete  V                        ***************************************************************V                        *                                                             *V                        * If you want to use the WBEM interface for the ACMS Remote   *V                        * Manager, you need to invoke SYS$STARTUP:ACMS$WBEM_SETUP.COM *V                        *                                                             *V                        ***************************************************************  H                   ACMS postinstallation procedure completed successfully,                     at 09:36 on  22-JUN-2001  K               %RUN-S-PROC_ID, identification of created process is 0001AB29r  >               COPYRIGHT (c) 1999  Compaq Computer Corporation.#                All Rights Reserved.e>                Unpublished rights reserved under the copyright)                laws of the United States.t  B                The software contained on this media is proprietary=                to and embodies the confidential technology ofo=                Compaq Computer Corporation.  Possession, use,,?                duplication or dissemination of the software andrC                media is authorized only pursuant to a valid writtenr8                license from Compaq Computer Corporation.  D                RESTRICTED RIGHTS: Use, duplication, or disclosure byD                the U.S. Government is subject to restrictions as setF                forth in Subparagraph (c)(1)(ii) of DFARS 252.227-7013,2                or in FAR 52.227-19, as applicable.  B                   ACMS Installation Verification Procedure started,                     at 09:37 on  22-JUN-2001          I                                                 Sample Installations A-13*                Sample Installations9     A.1 OpenVMS Alpha Development Kit Sample Installation     W           ACMS V4.4-0    Current System State: STARTED   Time:  22-JUN-2001 09:38:19.90 .           Terminal Subsystem State:    STARTED.           Queued Task Initiator State: STOPPED.           System Auditing State:       ENABLED           Active ACMS Users B           User Name      Submitter ID        Agent PID      DeviceA           SYSTEM         00010014            0001AB26       RTA3: &           Active Execution ControllersW           Application Name                   Process Name        User Name      Exc PIDhX           ACMSIVP                            ACMS01EXC001000     ACMS$IVP       0001AB2E  M               ACMS Installation Verification Procedure completed successfullyA(                 at 09:38 on  22-JUN-2001  B               Results of IVP are in SYS$COMMON:[SYSUPD]ACMSIVP.LOG  <            Installation of ACMSDEVA_ V4.4 completed at 09:38  H               Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY  T               Creating installation data file:VMI$ROOT:[SYSUPD]ACMSDEVA_044.VMI_DATA  ,            VMSINSTAL procedure done at 09:38             $ lo?             SYSTEM       logged out at  22-JUN-2001 09:40:56.34n  7     A.2 OpenVMS VAX Development Kit Sample Installation   A           This section contains a sample installation of the ACMS E           Version 4.4 for OpenVMS VAX development kit. The details of =           your actual installation may be somewhat different.,  !           $ @sys$update:vmsinstale  C            OpenVMS VAX Software Product Installation Procedure V7.1p  %           It is 22-JUN-2001 at 09:51.4  9           Enter a question mark (?) at any time for help. H           * Are you satisfied with the backup of your system disk [YES]?G           * Where will the distribution volumes be mounted: DUA0:[KITS]S           A-14 Sample Installations  n  n      I                                                      Sample InstallationseI                       A.2 OpenVMS VAX Development Kit Sample Installation     X               Enter the products to be processed from the first distribution volume set.&               * Products: ACMSDEVV_044B               * Enter installation options you wish to use (none):7               The following products will be processed:-                 ACMSDEVV_ V4.4  @                Beginning installation of ACMSDEVV_ V4.4 at 09:52  D               %VMSINSTAL-I-RESTORE, Restoring product save set A ...Y               %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.o  >               COPYRIGHT (c) 1999  Compaq Computer Corporation.#                All Rights Reserved.i>                Unpublished rights reserved under the copyright)                laws of the United States.C  B                The software contained on this media is proprietary=                to and embodies the confidential technology ofn=                Compaq Computer Corporation.  Possession, use, ?                duplication or dissemination of the software and C                media is authorized only pursuant to a valid written 8                license from Compaq Computer Corporation.  D                RESTRICTED RIGHTS: Use, duplication, or disclosure byD                the U.S. Government is subject to restrictions as setF                forth in Subparagraph (c)(1)(ii) of DFARS 252.227-7013,2                or in FAR 52.227-19, as applicable.  C               The results of this installation are being logged in: ;                 SYS$COMMON:[SYSUPD]ACMS044_INSTALLATION.LOGd  5               Installing ACMS V4.4-0, development kit   Y                   There are four optional parts to the ACMS development kit installation:t  0                       o  ACMS component software(                       o  ACMS LSE update%                       o  ACMS samples 7                       o  ACMS Request Interface samplesh  A                   The full installation includes all these parts.-]                   To install the ACMS samples or the ACMS Request Interface samples, you must.U                   install, or have previously installed, the ACMS component software.e  @               * Do you want the full ACMS installation [NO]? YES  1               CHECKING INSTALLATION PREREQUISITES 1               -----------------------------------o  I                                                 Sample Installations A-15C a  a           Sample Installations7     A.2 OpenVMS VAX Development Kit Sample Installationt    U           The following software products are not available, or are below the minimumt           required version:Y  L             Product               Required  Minimum version  Current VersionL             --------------------  --------  ---------------  ---------------L             DECtrace              No        2.0              (not available)  X               If products marked as nonrequired are to be used with ACMS, they should beL               upgraded to at least the minimum version displayed before use.  6               (required and optional software checked)  (               (product licenses checked)  1           The following images are not installed:R  S             Product          Image                      Required  Startup ProceduredV             ---------------  -------------------------  --------  --------------------Q             DECtrace         VMI$ROOT:[SYSLIB]EPC$FUNC  No        EPC$STARTUP.COMY  Z               The images marked as required must be installed before this installation canX               be successfully completed. These images are usually installed by executingU               the product's startup procedure. For more information, refer to product H               specific documentation and the VMS INSTALL Utility Manual.  (               (installed images checked)  "               (privileges checked)  "               (disk space checked)  #               (disk quotas checked)*  )               (system parameters checked)c  .               (process account quotas checked)  $           ACMS PREVIOUS INSTALLATION$           --------------------------  6               (no previous installation of ACMS found)             ACMS LSE CHECK           --------------  =               (LSE available -- LSE will be updated for ACMS)*  !           ACMS Oracle Trace CHECK*!           -----------------------   Y               Oracle Trace is not being updated for ACMS because it is not available, notE-               started, or Rdb is not started.t       A-16 Sample Installationsn e  M      I                                                      Sample InstallationstI                       A.2 OpenVMS VAX Development Kit Sample Installation     \                   The ACMS facility definition will be stored in SYS$SHARE:EPC$FACILITY.TLB.Y                   For more information on inserting this definition into the Oracle TraceUS                   administrative database, refer to the Oracle Trace documentation.T  #               ACMS OLD SAMPLE FILESa#               ---------------------   -                   (no old sample files found)t  !               ACMS SHUTDOWN CHECK !               -------------------g  U                   ACMSTOP.COM was not found. If ACMS was previously installed on this O                   system, make sure it is shut down before proceeding with this                    installation.q  -               ACMS POSTINSTALLATION PROCEDURE -               -------------------------------n  [                   (postinstallation procedure will be run automatically after installation)P  Y                   Please read the chapter After Installing ACMS, in the ACMS InstallationaY                   Guide, for manual tasks that you should consider after installing ACMS.   %               ACMS SYSTEM ROOTS CHECKt%               -----------------------[  W                   The following ACMS-related files were found in system-specific roots:T  8                     AMAMA$DKA500:[SYS0.SYSEXE]SYSUAF.DAT  ]                   The files listed above, found in system-specific roots, may have an adverse Y                   effect in the installation of ACMS, execution of the IVP, or subsequent]Z                   execution of applications. If you encounter problems during or after theZ                   installation, Compaq advises you to review the list and delete or rename]                   these files, or move them to cluster-common directories, and then reinstalld=                   ACMS. The list of files is also recorded in >                   SYS$COMMON:[SYSUPD]ACMS044_INSTALLATION.LOG.                 ACMS IVP               --------  U               * Do you want to execute the Installation Verification Procedure [YES]?   4                   Checking IVP user account ACMS$IVP  N                 The ACMS$IVP account used to execute the IVP is not available.  W                   You must supply a UIC and password for this account so that it can beGL                   created; this must be done before the IVP can be executed.  I                                                 Sample Installations A-17t    $           Sample Installations7     A.2 OpenVMS VAX Development Kit Sample Installationc    W               Please enter the UIC for the ACMS$IVP account, in the form [ggggg,nnnnnn]G             * UIC: [400,200]  J               Please enter a password of at least 8 characters, using onlyN               the following characters: ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789$_             * Password:            * Verification:u  +           SUMMARY OF THIS ACMS INSTALLATIONe+           ---------------------------------   N               The following steps will be taken to complete this installation:  P               o  The ACMS system will be shut down (via SYS$STARTUP:ACMSTOP.COM):               o  ACMS component software will be installed9               o  LSE environment will be updated for ACMS L               o  Oracle Trace facility text library will be updated for ACMS9               o  CDD-related ACMS files will be installed /               o  ACMS samples will be installedoA               o  ACMS Request Interface samples will be installedGE               o  The ACMS postinstallation procedure will be executed .               o  The ACMS IVP will be executed  N               The rest of the installation will take approximately 15 minutes.E               Execution of the IVP will take approximately 3 minutes.   Q               Note that this time is heavily dependent your system load, hardware V               and kit media. The time mentioned was measured on a stand-alone VAX 8530C               system with a disk-resident kit.  Your time may vary.   ;           * Do you want to continue the installation [YES]?l  X           The interactive portion of this installation is complete; no further questions4           will be asked until the post installation.  *               Installation of ACMS started(                 at 09:54 on  22-JUN-2001                 A-18 Sample Installations            I                                                      Sample InstallationspI                       A.2 OpenVMS VAX Development Kit Sample Installation     $                   Restoring savesetsD               %VMSINSTAL-I-RESTORE, Restoring product save set J ...D               %VMSINSTAL-I-RESTORE, Restoring product save set K ...D               %VMSINSTAL-I-RESTORE, Restoring product save set L ...D               %VMSINSTAL-I-RESTORE, Restoring product save set M ...D               %VMSINSTAL-I-RESTORE, Restoring product save set N ...D               %VMSINSTAL-I-RESTORE, Restoring product save set O ...D               %VMSINSTAL-I-RESTORE, Restoring product save set P ...4                   Checking/creating ACMS directoriesM               %VMSINSTAL-I-SYSDIR, This product creates system disk directory 4                 VMI$ROOT:[SYSHLP.EXAMPLES.ACMSMGMT].R               %CREATE-I-EXISTS, VMI$ROOT:[SYSHLP.EXAMPLES.ACMSMGMT] already exists                   Updating LSE?                   Updating Oracle Trace definition text libraryG?                   Deleting old CDD$TOP.ACMS$DIR.ACMS$WORKSPACESi;                   Creating CDD$TOP.ACMS$DIR.ACMS$WORKSPACESM5                   Deleting old RI sample CDD nodes...M>                   Restoring RI sample application CDD nodes...X               %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named ACMS$IVP.U               %UAF-I-PWDLESSMIN, new password is shorter than minimum password length ;               %UAF-I-ADDMSG, user record successfully added Z               %UAF-I-RDBADDMSGU, identifier ACMS$IVP value [000400,000200] added to rights                 database  *                   Account ACMS$IVP created  A                   Updating account ACMS$IVP to current parameterstX               %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named ACMS$IVP.4               %UAF-I-MDFYMSG, user record(s) updatedX               %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named ACMS$IVP.4               %UAF-I-MDFYMSG, user record(s) updatedX               %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named ACMS$IVP.4               %UAF-I-MDFYMSG, user record(s) updatedX               %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named ACMS$IVP.4               %UAF-I-MDFYMSG, user record(s) updated  *                   Account ACMS$IVP updated  I                   ACMS$IVP account created/updated -- IVP selected to runc!                   Providing files 4                   Provided DCL command file ACMS.CLD5                   Provided DCL help file ACMSHELP.HLP 7                   All other files provided - list is in K                     AMAMA$DKA500:[SYS0.SYSCOMMON.][SYSEXE]ACMS044_FILES.DAT   I                                                 Sample Installations A-19  t  a           Sample Installations7     A.2 OpenVMS VAX Development Kit Sample Installationa    9               Installation of ACMS completed successfullya(                 at 10:03 on  22-JUN-2001  X           %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...  :           COPYRIGHT (c) 1999  Compaq Computer Corporation.            All Rights Reserved.n:            Unpublished rights reserved under the copyright%            laws of the United States.r  >            The software contained on this media is proprietary9            to and embodies the confidential technology of*9            Compaq Computer Corporation.  Possession, use, ;            duplication or dissemination of the software and ?            media is authorized only pursuant to a valid writtenM4            license from Compaq Computer Corporation.  @            RESTRICTED RIGHTS: Use, duplication, or disclosure by@            the U.S. Government is subject to restrictions as setB            forth in Subparagraph (c)(1)(ii) of DFARS 252.227-7013,.            or in FAR 52.227-19, as applicable.  5               ACMS postinstallation procedure started (                 at 10:07 on  22-JUN-2001  Q                    **************************************************************sQ                    *                                                            * Q                    *  NOTE: Refer to Chapter 4 in the ACMS Installation Guide   *eQ                    *         for other important postinstallation work.         *rQ                    *                                                            *eQ                    **************************************************************,  2           Checking/creating logical ACMS$DIRECTORY2           ----------------------------------------  V             The procedure checks for the logical ACMS$DIRECTORY, which must be definedM             /SYSTEM /SUPERVISOR and must point to an existing disk directory.   L               ACMS$DIRECTORY is not defined as a /SYSTEM /SUPERVISOR logical  M           Please supply an equivalence string for the ACMS$DIRECTORY logical..:           Equivalence string [ SYS$SYSDEVICE:[ACMS.ADB] ]:  C               ACMS$DIRECTORY is defined as SYS$SYSDEVICE:[ACMS.ADB]U2               ACMS$DIRECTORY logical is acceptable  ?                                    (press <RETURN> to continue)I       A-20 Sample Installationsh e  o      I                                                      Sample Installations:I                       A.2 OpenVMS VAX Development Kit Sample Installationa    0               Converting ACMSGEN parameter files0               ----------------------------------  R                 This procedure searches for all ACMSGEN parameter files located inQ                 SYS$SYSDEVICE:[SYS*.SYSEXE] and SYS$COMMON:[SYSEXE], and converts3R                 them to be compatible with the current version of ACMS. If you areP                 upgrading from a version of ACMS prior to V4.0, you must perform                  this conversion.  J               Do you want to convert existing ACMSGEN parameter files [Y]?  B                   Converting SYS$SYSDEVICE:[SYS0.SYSEXE]ACITVE.ACM;                   Converting SYS$COMMON:[SYSEXE]ACMSPAR.ACMI  X                   The ACMSGEN parameter files listed above have been converted; if otherX                   parameter files exist on your system, they must be updated as follows:  .                       $ RUN SYS$SYSTEM:ACMSGEN5                       ACMSGEN> USE file-specification 7                       ACMSGEN> WRITE file-specificationJ#                       ACMSGEN> EXITM  C                                        (press <RETURN> to continue)n  /               Converting ACMS UDF and DDF files /               ---------------------------------d  Z                 The procedure searches for the files pointed to by the ACMSUDF and ACMSDDFS                 logicals, if they exist, and then for AMCSUDF.DAT or ACMSDDF.DAT inVW                 SYS$SYSROOT:[SYS*], and converts them to be compatible with the currenta[                 version of ACMS. If you are upgrading from a version of ACMS prior to V3.1, 1                 you must perform this conversion.m  I               Do you want to convert existing ACMS UDF and DDF files [Y]?   D                   Converting UDF file SYS$COMMON:[SYSEXE]ACMSUDF.DATD                   Converting DDF file SYS$COMMON:[SYSEXE]ACMSDDF.DAT  C                                        (press <RETURN> to continue)s  6               Checking/creating ACMS UDF and DDF files6               ----------------------------------------  W                 The procedure checks for ACMSUDF.DAT and ACMSDDF.DAT, first through the R                 logicals ACMSUDF and ACMSDDF, and then in SYS$COMMON:[SYSEXE], andY                 creates them if they're not already present from a previous installation.V  =                   No /SYSTEM /EXECUTIVE logical ACMSUDF foundY7                   SYS$COMMON:[SYSEXE]ACMSUDF.DAT existsu  I                                                 Sample Installations A-21i d  g           Sample Installations7     A.2 OpenVMS VAX Development Kit Sample Installation     9               No /SYSTEM /EXECUTIVE logical ACMSDDF found 3               SYS$COMMON:[SYSEXE]ACMSDDF.DAT existso  ?                                    (press <RETURN> to continue)   *           Checking/creating ACMS_SETUP.COM*           --------------------------------  V             The procedure checks for site-specific startup procedure ACMS_SETUP.COM inP             SYS$COMMON:[SYS$STARTUP], and creates a template if the file doesn't             already exist.  =               Creating SYS$COMMON:[SYS$STARTUP]ACMS_SETUP.COMh  D             ACMS_SETUP.COM will be executed the next time you invokeS             SYS$STARTUP:ACMSTART.COM. Please review ACMS_SETUP.COM and adjust it tobQ             reflect the needs of your ACMS environment. It can be used to perform .             these site-specific startup steps:6               - define the ACMS logical ACMS$DIRECTORY:               - install ACMS utilities as shareable imagesJ               - define ACMS logicals such as ACMS$AUDIT_LOG, ACMS$SWL_LOG,?                 ACMS$NOTICE, ACMS$EDIT, ADU$EDIT and SWLUP$EDIT 6               - start the ACMS system and applications  ?                                    (press <RETURN> to continue)o  *           Checking/copying ACMS menu files*           --------------------------------  S             The procedure checks for the ACMS command menu and default user menu in S             ACMS$DIRECTORY, and copies them from SYS$COMMON:[SYSEXE] if they're notLC             already in ACMS$DIRECTORY from a previous installation.-  E               ACMS$DIRECTORY:ACMSCMD.MDB already exists -- not copiedsB               ACMS$DIRECTORY:ACMS.MDB already exists -- not copied  Q                    **************************************************************rQ                    *                                                            * Q                    *  NOTE: Refer to Chapter 4 in the ACMS Installation Guide   *-Q                    *         for other important postinstallation work.         *eQ                    *                                                            *tQ                    **************************************************************r  /           Checking/creating ACMS$MGMT_SETUP.COMr/           -------------------------------------f       A-22 Sample Installationsp u  l      I                                                      Sample Installations I                       A.2 OpenVMS VAX Development Kit Sample Installationd    U                        ************************************************************** U                        *                                                            * U                        *  NOTE: Refer to the Managing the Remote Manager chapter    * U                        *  in the ACMS Remote Systems Management Guide for more      *gU                        *  information.                                              * U                        *                                                            * U                        **************************************************************d  T               Do you want to SETUP and CONFIGURE the ACMS Remote System Manager [Y]?  :                   Creating SYS$STARTUP:ACMS$MGMT_SETUP.COM  ;               Do you want to allow Proxy Authorization [Y]?-  ]               (ACMS$MGMT_CONFIG) Enter the file specification for the configuration file usedE*                 by the ACMS Remote ManagerN               Equivalence string [ SYS$SYSROOT:[SYSEXE]ACMS$MGMT_CONFIG.ACM ]:  \               (ACMS$MGMT_TEMP) Enter the directory where the temp command procedures will be                 createds@               Equivalence string [ SYS$SPECIFIC:[ACMS_RM.TMP] ]:<                    SYS$SPECIFIC:[ACMS_RM.TMP] does not exist  +               Do you want to create it [Y]?l  @                     Created directory SYS$SPECIFIC:[ACMS_RM.TMP]  X               (ACMS$MGMT_LOG) Enter the directory for the ACMS Remote Manager's Log file@               Equivalence string [ SYS$SPECIFIC:[ACMS_RM.LOG] ]:<                    SYS$SPECIFIC:[ACMS_RM.LOG] does not exist  +               Do you want to create it [Y]?   @                     Created directory SYS$SPECIFIC:[ACMS_RM.LOG]  S               (ACMS$MGMT_CREDS_DIR) Enter the directory for the ACMS Remote Manageru               Credential'sB               Equivalence string [ SYS$SPECIFIC:[ACMS_RM.CREDS] ]:>                    SYS$SPECIFIC:[ACMS_RM.CREDS] does not exist  +               Do you want to create it [Y]?t  B                     Created directory SYS$SPECIFIC:[ACMS_RM.CREDS]  ]               (ACMS$MGMT_SNAPSHOT) Enter the directory where the snapshot data will be stored-E               Equivalence string [ SYS$SPECIFIC:[ACMS_RM.SNAPSHOT] ]:oA                    SYS$SPECIFIC:[ACMS_RM.SNAPSHOT] does not exist   +               Do you want to create it [Y]?a  E                     Created directory SYS$SPECIFIC:[ACMS_RM.SNAPSHOT]d  I                                                 Sample Installations A-23     -           Sample Installations7     A.2 OpenVMS VAX Development Kit Sample Installationn    Y           (ACMS$MGMT_ERR_LOG) Enter the directory where the Error Log data will be stored @           Equivalence string [ SYS$SPECIFIC:[ACMS_RM.ERR_LOG] ]:<                SYS$SPECIFIC:[ACMS_RM.ERR_LOG] does not exist  '           Do you want to create it [Y]?e  @                 Created directory SYS$SPECIFIC:[ACMS_RM.ERR_LOG]  J             SYS$STARTUP:ACMS$MGMT_SETUP.COM will be executed the next timeR             SYS$STARTUP:ACMSTART.COM is invoked. Please review ACMS$MGMT_SETUP.COMU             and adjust it to reflect the needs of your ACMS Remote Systems Managementi             environment.  @            Creating/Checking the RM Identifiers and SNMP account  1               Checking for user account ACMS$SNMP   ;                Identifier for ACMS$MGMT_READ does not existi  _           %UAF-I-RDBADDMSG, identifier ACMS$MGMT_READ value %X8001074D added to rights database <                Identifier for ACMS$MGMT_WRITE does not exist  `           %UAF-I-RDBADDMSG, identifier ACMS$MGMT_WRITE value %X8001074E added to rights database;                Identifier for ACMS$MGMT_OPER does not existe  _           %UAF-I-RDBADDMSG, identifier ACMS$MGMT_OPER value %X8001074F added to rights database =                Identifier for ACMS$MGMT_SYSUPD does not exist   a           %UAF-I-RDBADDMSG, identifier ACMS$MGMT_SYSUPD value %X8001074G added to rights databaseg  Y             The ACMS$SNMP account used to execute ACMSMGR SNMP commands is not available.s  S               You must supply a UIC and password for this account so that it can beTJ               created; this must be done before the $MGMT can be executed.  X               Please enter the UIC for the ACMS$SNMP account, in the form [ggggg,nnnnnn]             UIC: [400,201]  J               Please enter a password of at least 8 characters, using onlyN               the following characters: ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789$_             * Password:            * Verification:   '               Account ACMS$SNMP created   >               Updating account ACMS$SNMP to current parameters  '               Account ACMS$SNMP updatedA       A-24 Sample Installations            I                                                      Sample InstallationspI                       A.2 OpenVMS VAX Development Kit Sample Installatione    O                   Checking config file SYS$SYSROOT:[SYSEXE]ACMS$MGMT_CONFIG.ACMha               Creating a new Remote Mananger config file SYS$SYSROOT:[SYSEXE]ACMS$MGMT_CONFIG.ACMw  5               %ACMSMGMT-S-NORMAL, Operation completedt5               %ACMSMGMT-S-NORMAL, Operation completedr5               %ACMSMGMT-S-NORMAL, Operation completed 5               %ACMSMGMT-S-NORMAL, Operation completedy5               %ACMSMGMT-S-NORMAL, Operation completed 5               %ACMSMGMT-S-NORMAL, Operation completedE5               %ACMSMGMT-S-NORMAL, Operation completedl5               %ACMSMGMT-S-NORMAL, Operation completedl5               %ACMSMGMT-S-NORMAL, Operation completed 5               %ACMSMGMT-S-NORMAL, Operation completedo5               %ACMSMGMT-S-NORMAL, Operation completedn5               %ACMSMGMT-S-NORMAL, Operation completed 5               %ACMSMGMT-S-NORMAL, Operation completed 5               %ACMSMGMT-S-NORMAL, Operation completed 5               %ACMSMGMT-S-NORMAL, Operation completed 5               %ACMSMGMT-S-NORMAL, Operation completed.5               %ACMSMGMT-S-NORMAL, Operation completed   [               Entity                                           Entity   Coll     Collection V               Name                                             Type     Class    State[               -----------------------------------------------------------------------------cY                *                                                *        id       enabled Y                *                                                *        config   enabledrZ                *                                                *        runtime  disabledZ                *                                                *        pool     disabledZ                *                                                *        error    disabled  C                 The ACMS Remote System Manager has been configured.   U                 The command procedure SYS$STARTUP:ACMS$MGMT_ENV.COM should be invokedaV                 to define the symbols for starting the ACMS Remote Manager and running)                 the Remote Manager clientl  H                   ACMS postinstallation procedure completed successfully,                     at 10:40 on  22-JUN-2001  K               %RUN-S-PROC_ID, identification of created process is 3C600125   >               COPYRIGHT (c) 1999  Compaq Computer Corporation.#                All Rights Reserved.a>                Unpublished rights reserved under the copyright)                laws of the United States.p  I                                                 Sample Installations A-25A U  n           Sample Installations7     A.2 OpenVMS VAX Development Kit Sample InstallationN    >            The software contained on this media is proprietary9            to and embodies the confidential technology of 9            Compaq Computer Corporation.  Possession, use,n;            duplication or dissemination of the software andr?            media is authorized only pursuant to a valid writtenl4            license from Compaq Computer Corporation.  @            RESTRICTED RIGHTS: Use, duplication, or disclosure by@            the U.S. Government is subject to restrictions as setB            forth in Subparagraph (c)(1)(ii) of DFARS 252.227-7013,.            or in FAR 52.227-19, as applicable.  >               ACMS Installation Verification Procedure started(                 at 10:41 on  22-JUN-2001  W           ACMS V4.4-0    Current System State: STARTED   Time:  22-JUN-2001 10:43:21.94 .           Terminal Subsystem State:    STARTED.           Queued Task Initiator State: STOPPED.           System Auditing State:       ENABLED           Active ACMS Users B           User Name      Submitter ID        Agent PID      DeviceA           SYSTEM         00010014            3C600121       RTA1:F&           Active Execution ControllersW           Application Name                   Process Name        User Name      Exc PID X           ACMSIVP                            ACMS01EXC001000     ACMS$IVP       3C60012A  M               ACMS Installation Verification Procedure completed successfully (                 at 10:43 on  22-JUN-2001  B               Results of IVP are in SYS$COMMON:[SYSUPD]ACMSIVP.LOG  <            Installation of ACMSDEVV_ V4.4 completed at 10:43  S           Enter the products to be processed from the next distribution volume set.t           * Products: exit,            VMSINSTAL procedure done at 10:44                       A-26 Sample Installations                          I                                                                         B(I         _________________________________________________________________a  I                                 Registering and Loading Your ACMS License     I               You must register and load your ACMS license before you can*I               install or use ACMS. This appendix explains how to register $               and load your license.  I               Section B.1 describes an ACMS License Product Authorizationu               Key (PAK).  F               Section B.2 describes how to load and register your ACMSA               license using the command procedure VMSLICENSE.COM.   F               Section B.3 describes how to load and register your ACMS5               license using the LICENSE DCL commands.a  D               For more information on OpenVMS licensing, see OpenVMSI               License Management Utility Manual, and the DCL command HELP                LICENSE.  #         B.1 Sample ACMS License PAKn  D               The ACMS License PAK is a paper document that containsI               information about your ACMS license. When you register youreI               ACMS license on your system, information from this documentS2               is loaded into the license database.  G               Each PAK has fourteen fields of information. Depending onlE               your license agreement, some fields might contain data,R*               while others might be blank.  I               Table B-1 lists all the fields on a PAK, along with typicalm#               data for an ACMS PAK.             I                             Registering and Loading Your ACMS License B-1A G  p      -     Registering and Loading Your ACMS License-     B.1 Sample ACMS License PAKs    E           Table_B-1_Product_Authorization_Key_Fields_________________   E           Field_Name_________________Typical_ACMS_Information________   (           ISSUER:                    DEC  0           AUTHORIZATION NUMBER:      US-10-THM-0  ,           PRODUCT NAME:              ACMS[1]  (           PRODUCER:                  DEC  )           NUMBER OF UNITS:           1200e  (           VERSION:                   4.4  +           PRODUCT RELEASE DATE:      (none)0  +           KEY TERMINATION DATE:      (none)g  &           AVAILABILITY CODE:         F  +           ACTIVITY TABLE CODE:       (none)a  .           KEY OPTIONS:               MOD_UNITS  +           PRODUCT TOKEN:             (none)m  +           HARDWARE I.D.:             (none)   :           CHECKSUM:                  1-NTIN-DCIN-TCTA-NYMRE           [1]This_is_the_license_name;_one_of_the_following:_ACMS,___f  9           ACMS-RT, ACMS-RT-USER, ACMS-REM, ACMS-REM-USER. E           ___________________________________________________________        B.2 Using VMSLICENSE.COM  ?           You can register and load your ACMS license using the B           OpenVMS command procedure VMSLICENSE.COM. To invoke thisB           procedure, first log in to the system manager's account,9           SYSTEM, and then execute the following command::  "           $ @SYS$UPDATE:VMSLICENSE  E           The procedure displays a menu; press <Return> to choose thedB           default menu item, registering a PAK. The procedure thenA           asks if you have your PAK; press <Return> to choose thee           default answer, YES.  @           The procedure now asks you to supply the data for eachE           field on your PAK. For each field, type in the data exactlyD#           as it appears on the PAK.   1     B-2 Registering and Loading Your ACMS License     c      I                                 Registering and Loading Your ACMS License-I                                                  B.2 Using VMSLICENSE.COMD    F                 ________________________ Note ________________________  >                 A PAK cannot have both a version and a productA                 release date. If you provide version information, F                 the procedure does not ask for a product release date.  F                 ______________________________________________________  A               When you have supplied all the PAK information, theaE               procedure displays the information you provided, in thetC               same form as it appears on the PAK, and asks if it is H               correct. If all the information is correct, press <Return>0               to choose the default answer, YES.  A               The procedure then registers the PAK in the license-G               database, and asks if you want to load the license. Pressa9               <Return> to choose the default answer, YES.Y  F                 ________________________ Note ________________________  A                 The license must be registered and loaded on your.;                 system before you can install and use ACMS.t  F                 ______________________________________________________  I               When you are finished, select menu item 99 to exit from then               procedure.  &         B.3 Using LICENSE DCL Commands  G               You can register and load your ACMS license using the DCL G               commands LICENSE REGISTER and LICENSE LOAD. Log in to theiF               system manager's account, SYSTEM, before executing these               commands.D  A               The LICENSE REGISTER command accepts parameters andlG               qualifiers that correspond to the fields on your PAK. Thee1               general syntax for this command is:   9               LICENSE REGISTER product-name [/qualifiers]r  G               Table B-2 lists all the fields on a PAK, along with their 5               LICENSE LOAD parameters and qualifiers.S    I                             Registering and Loading Your ACMS License B-3t a  n      -     Registering and Loading Your ACMS Licensey"     B.3 Using LICENSE DCL Commands    E           Table_B-2_LICENSE_LOAD_Parameters_and_Qualifiers___________   E           Field_Name_________________LICENSE_REGISTER_Qualifier______   5           ISSUER:                    /ISSUER="string"   :           AUTHORIZATION NUMBER:      /AUTHORIZATION=string  =           PRODUCT NAME:              (product-name parameter)   7           PRODUCER:                  /PRODUCER="string"   2           NUMBER OF UNITS:           /UNITS=number  2           VERSION:                   /VERSION=nn.m  7           PRODUCT RELEASE DATE:      /RELEASE_DATE=date   ;           KEY TERMINATION DATE:      /TERMINATION_DATE=date-  :           AVAILABILITY CODE:         /AVAILABILITY=code orB                                      /AVAILABILITY=CONSTANT=number  6           ACTIVITY TABLE CODE:       /ACTIVITY=code or>                                      /ACTIVITY=CONSTANT=number  4           KEY OPTIONS:               /OPTION=keyword  2           PRODUCT TOKEN:             /TOKEN=string  8           HARDWARE I.D.:             /HARDWARE_ID=string  E           CHECKSUM:__________________/CHECKSUM=string________________r  C           For example, the following DCL commands register and load 4           the PAK information supplied in Table B-1:  #           $ LICENSE REGISTER ACMS -            _$ /ISSUER="DEC" -)           _$ /AUTHORIZATION=US-10-THM-0 -            _$ /PRODUCER="DEC" -           _$ /UNITS=1200 -           _$ /VERSION=4.4 -*           _$ /AVAILABILITY=F -            _$ /OPTION=MOD_UNITS -,           _$ /CHECKSUM=1-NTIN-DCIN-TCTA-NYMR           $  LICENSE LOAD ACMS  1     B-4 Registering and Loading Your ACMS Licenseo u  n                    I                                                                         CcI         _________________________________________________________________M  I                                      Modifying ACMS Help and Message TextI    I               This appendix describes how to modify ACMS help and messageoE               text, for example, to translate them to languages othera               than English.A  F               The ACMS kit includes a save set that contains the filesI               you can use to translate the contents of ACMS message filesrI               and help text to languages other than English. This section F               provides information on how to restore the save set from               the kit.  H               All source files for the messages and help text are storedI               in a BACKUP save set in the kit. Restore this save set to a I               directory and modify it there. Follow these instructions toM#               restore the save set:                  1. Mount the kit.   G                  If the kit is on disk, mount it using the /OVERRIDE=ID_E                  qualifier. For example, to mount a kit on RA90 drivee8                  $100$DUA31:, use the following command:  0                  $ MOUNT/OVERRIDE=ID $100$DUA31:  &               2. Restore the save set.  H                  To restore the save set, use the DCL command BACKUP and;                  the save set name in the following format:]  9                  BACKUP/LOG kit-device:<kit-name>.I /SAVEo         disk:[directory]  F                  The <kit-name> parameter denotes the software kit you                   are installing:  B                  o  ACMSDEVA_044 - if you are installing the Alpha$                     development kit.  G                  o  ACMSRTOA_044 - if you are installing the Alpha run-                      time kit.h  I                                  Modifying ACMS Help and Message Text C-1t g  S      (     Modifying ACMS Help and Message Text      >              o  ACMSREMA_044 - if you are installing the Alpha"                 remote-access kit.  <              o  ACMSDEVV_044 - if you are installing the VAX                  development kit.  E              o  ACMSRTOV_044 - if you are installing the VAX run-time                  kit.  D              o  ACMSREMV_044 - if you are installing the VAX remote-                 access kit.g  E              Restore the save set to an empty directory. For example,d>              if you have an ACMS Alpha development kit that is@              mounted on DKA1: and you have created the directoryB              DISK1:[MESSAGES] to hold the files, use the following8              DCL command BACKUP to restore the save set:  F              $ BACKUP/LOG DKA1:ACMSDEVA_044.I/SAVESET DISK1:[MESSAGES]  A              The ACMS save sets are stored in the [0,0] directoryaB              on disk kits. If, for example, you have an ACMS AlphaA              run-time kit that is mounted on $100$DUA31:, and you0D              have created the directory DISK1:[MESSAGES] to hold theC              files, use the following DCL BACKUP command to restoreA              the save set:  B              $ BACKUP/LOG $100$DUA31:[0,0]ACMSRTOA_044.I/SAVESET -!              _$ DISK1:[MESSAGES]*   '           3. Make changes to the files.t  <              After restoring the kit, you can print the fileB              CHANGING_MESSAGES.MEM, which contains instructions onB              how to change the help text files, change the message@              files, and install the modified files on the targetC              system. This file also includes instructions to changey@              the character ordering sequence used by the CONTROL/              FIELD and SELECT FIRST statements.             ,     C-2 Modifying ACMS Help and Message Text                         I                                                                         DMI         _________________________________________________________________   I                             Creating Transaction Logs for DECdtm Services     D               If you want to use DECdtm services on a node, you mustC               create a transaction log for that node. In an OpenVMS H               Cluster system, you must create a transaction log for eachI               node in the cluster. This appendix describes the following:p  =               o  Prerequisites for creating a transaction log   C               o  Planning the size and location of transaction logsM  9               o  Setting up and creating transaction logs-  C               o  Example of creating transaction logs for a clustert  I               For more information about DECdtm services and the commands G               described in this appendix, see the OpenVMS documentation-               set.  8         D.1 Prerequisites for Creating a Transaction Log  A               Before you create a transaction log for a node, the 2               following prerequisites must be met:  4               o  You must have the SYSPRV privilege.  F               o  The node must be running OpenVMS Alpha Version 6.2 or/                  higher, excluding Version 7.0.   D               o  The node must be running OpenVMS VAX Version 6.2 or/                  higher, excluding Version 7.0.   >         D.2 Planning the Size and Location of Transaction Logs  F               The size and location of transaction logs can affect theG               performance of your system. Before you create transaction-@               logs, plan how big to make the logs, and where youB               are going to put them. Although you can later move aI               transaction log and change the size to improve performance,i<               careful planning reduces the need for changes.  I                         Creating Transaction Logs for DECdtm Services D-1            1     Creating Transaction Logs for DECdtm Services :     D.2 Planning the Size and Location of Transaction Logs    A           If the performance of your system is adversely affectedrB           by either the location or size of the logs, refer to the>           OpenVMS documentation for the following information:  A           o  Checking whether or not the transaction logs are the               correct sizeM  2           o  Changing the size of transaction logs  $           o  Moving transaction logs  2     D.2.1 Determining the Size of Transaction Logs  C              ________________________ Note ________________________   ;              These guidelines for determining the size of a ;              transaction log are approximate. When planningh8              transaction logs, overestimate, rather than<              underestimate, the size of the transaction log.  C              ______________________________________________________a  C           When you create transaction logs, you specify the size of E           the log in blocks. By default, the size of each transaction @           log is 4000 blocks. This default size gives acceptable&           performance on most systems.  B           If you know the rate of transactions and their duration,B           use the following algorithm to calculate the transaction           log size:o  %           size = 40 * rate * durationR             In this algorithm:  A           o  size is the size (in blocks) of the transaction log.s  D           o  rate is the average number of transactions executed per              second.  B           o  duration is the average duration (in seconds) of each              transaction.s  D           For example, if the rate is 10 transactions per second andD           the duration is 12 seconds, the calculation is as follows:  +           size = 40 * 10 * 12 = 4800 blocks   C           In this example, the recommended size for the transactionn           log is 4800 blocks.   5     D-2 Creating Transaction Logs for DECdtm ServicesI           I                             Creating Transaction Logs for DECdtm Services I                    D.2 Planning the Size and Location of Transaction Logse    G               If you do not know the rate and duration of transactions,S6               accept the default value of 4000 blocks.  ;         D.2.2 Determining the Location for Transaction Logsi  H               When deciding where to put the transaction log for a node,-               consider the following factors:O                 o  Speed  F                  Select a high performance disk, such as a solid state0                  disk, that is not heavily used.                 o  Availability   E                  High availability is achieved when you have multiple A                  access paths to the data. Use a disk that can be I                  accessed by the other nodes in the cluster when the node G                  is down. This reduces the time that other transactions_F                  in the cluster are blocked while waiting for recovery'                  from the node failure.g                 o  Reliability  F                  Reliability is achieved when you have multiple copiesE                  of the data. A shadowed disk is more reliable than a G                  nonshadowed disk, but may be slower than a nonshadowed E                  disk because transaction logs are almost exclusivelye                  write-only.  D               You may have to choose which of these factors are mostC               important. For example, if the node is a workstation, B               you may choose to give up speed for availability andG               reliability, by putting the transaction log on a shadowedaI               HSC-based disk, instead of on a faster disk attached to the                workstation.  E               If you have an OpenVMS Cluster, each node must have itsoD               own transaction log. To improve the performance of theH               transactions, distribute the logs among different disks on               the system.   F                 ________________________ Note ________________________  >                 Ensure that the disk has sufficient contiguousB                 space to hold the transaction log. A discontiguous;                 transaction log results in poor transactionh                 performance.  F                 ______________________________________________________  I                         Creating Transaction Logs for DECdtm Services D-3  e  t      1     Creating Transaction Logs for DECdtm Services :     D.2 Planning the Size and Location of Transaction Logs        0     D.3 Setting Up and Creating Transaction Logs  E           This section describes how to set up and create transaction ?           logs. Before creating a transaction log, consider the0=           recommendations for sizing and locating the log, asR@           described in Section D.2. For an example of how to setA           up and create transaction logs for a three-node OpenVMSR(           Cluster, refer to Section D.4.  1           To set up and create a transaction log:V  ?           1. Identify the directories where you want to put the(              transaction logs.  4           2. Create the log file in the directories.  )     D.3.1 Setting Up the Transaction Logs   @           DECdtm services uses the logical SYS$JOURNAL to locate>           transaction logs. For a single node, you must defineA           SYS$JOURNAL to point to the directory that will containA@           the transaction log. In an OpenVMS Cluster, you defineB           SYS$JOURNAL on each node as a search list that points toD           all the directories that will contain the transaction logsD           for the cluster. If you put transaction logs for all nodesC           in one directory, SYS$JOURNAL on each node points to thatn           directory.  @           You must define SYS$JOURNAL in the system logical name#           table, in executive mode.<  C              ________________________ Note ________________________   7              Remember to define SYS$JOURNAL in both thee5              common and node-specific versions of theE:              SYS$STARTUP:SYLOGICALS.COM command procedure.  C              ______________________________________________________t          5     D-4 Creating Transaction Logs for DECdtm Servicest n  n      I                             Creating Transaction Logs for DECdtm ServicestI                              D.3 Setting Up and Creating Transaction Logs     +         D.3.2 Creating the Transaction Logs   F               To create a transaction log file, use the CREATE LOGFILEH               command of the Log Manager Control Program (LMCP) Utility:  #               $ RUN SYS$SYSTEM:LMCPr8               LMCP>  CREATE LOGFILE file-spec /SIZE=size               LMCP>  EXIT                  In this example:  @               o  file-spec is the full file specification of the>                  transaction log. The name of the file must beE                  SYSTEM$node-name, where node-name is the name of thesE                  node. The file extension must be .LM$JOURNAL. If youlF                  omit the file extension in the command line, the fileH                  specification has the extension .LM$JOURNAL by default.  F               o  size is the size of the transaction log in blocks. IfE                  you omit the /SIZE qualifier, the transaction log is,>                  created with the default size of 4000 blocks.  ?         D.4 Example of Setting Up and Creating Transaction Logsa  I               This section shows you how to set up and create transactionSC               logs for a three-node OpenVMS Cluster system. In this_F               example, cluster members and transaction log details are"               listed in Table D-1.  I               Table_D-1_Transaction_Log_Requirements_____________________r  I                             _______________Transaction_Log_______________G  I               Node_Name_____Location___________________Size_(In_Blocks)__t  ;               ORANGE        DISK$USER1:[LOGFILES]      5000   ;               RED           DISK$USER3:[LOGFILES]      4000l  I               GREEN_________DISK$LOG:[LOGFILES]________6000______________   F               To set up and create the transaction logs for the three-H               node OpenVMS Cluster, follow these steps. Before starting,I               ensure that all three disks are mounted on all three nodes.r  F               1. For each node, define the logical SYS$JOURNAL to be aF                  search list of all the directories in Table D-1, with'                  the following command:   I                         Creating Transaction Logs for DECdtm Services D-5_ _         1     Creating Transaction Logs for DECdtm Servicesu;     D.4 Example of Setting Up and Creating Transaction LogsR    7              $  DEFINE /SYSTEM /EXECUTIVE SYS$JOURNAL -T(              _$ DISK$USER1:[LOGFILES], -(              _$ DISK$USER3:[LOGFILES], -#              _$ DISK$LOG:[LOGFILES]D  C              ________________________ Note ________________________   <              You can enter all of the commands to set up the=              cluster from one node, using the SYSMAN Utility.   C              ______________________________________________________Y  :           2. Edit the common and node-specific versions of<              SYS$STARTUP:SYLOGICALS.COM files to include the'              definition of SYS$JOURNAL.   C           3. Enter the following commands to create the transaction               log files:   "              $ RUN SYS$SYSTEM:LMCPN              LMCP> CREATE LOGFILE DISK$USER1:[LOGFILES]SYSTEM$ORANGE/SIZE=5000A              LMCP> CREATE LOGFILE DISK$USER3:[LOGFILES]SYSTEM$REDrK              LMCP> CREATE LOGFILE DISK$LOG:[LOGFILES]SYSTEM$GREEN/SIZE=6000i              LMCP> EXIT   ?              If you omit the /SIZE qualifier (for example, whenE@              creating the log for node RED), the transaction log=              is created with the default size of 4000 blocks.                                   5     D-6 Creating Transaction Logs for DECdtm Services  $  P                            F      _________________________________________________________________  F                                                                  Index      2      A                                 ACMSIVP.COM7      _______________________________     location,  5-4_2      AAU                                 modifyingE        See Application Authorization        avoiding IVP failure with C          Utility                               INVACMPAR error, 5-4g2      ACMEXCPAR.COM,  4-8               ACMSPAR.ACMC        restrictions using, 4-9           requirements on a cluster, 0      ACMS                                   4-15:        deinstalling, 6-1               ACMSPARAM.COM,  4-8A        development kit, 1-1              restrictions using,  4-9h>        remote-access kit, 1-2               avoiding excessive=        run-time kit, 1-1                       PGFLQUOTA, 4-9 6        sample installations, A-1       ACMS parameters8      ACMS$AUDIT_LOG                      modifying,  4-8>        defining as a logical name,          certain conditions=          4-5                                   requiring, 4-9 2      ACMS$EDIT                         ACMS system1        defining as a logical name,       startingoD          4-5                                allowing after INVACMPAR:      ACMS$IVP account                          error, 4-103        user authorization, 2-13        ACMSTART.COMM<      ACMS$NOTICE                         execution of,  3-21D        defining as a logical name,       for automatic startup,  4-2D          4-5                             installing resident OpenVMS=      ACMS$SWL_LOG                           Alpha images, 4-3S?        defining as a logical name,       positioning in startup :          4-5                                procedure, 4-22      ACMSEDIT.COM                      ACMSTOP.COM<        as value for ACMS$EDIT, 4-5       checking for,  3-13A      ACMSGEN                             execution of,  3-13, 4-4t?        MSS_POOLSIZE parameter, 4-9,    ACMS_BUILD_MENU_FORM.COM B          5-4                             for rebuilding form image6                                             file, 4-16  F                                                                Index-1    o              =     ACMS_DEINSTALL.COM                 Authorization (cont'd)X8       actions performed,  6-1           new users,  4-11       deleting after executing,tF          6-2                           B______________________________3       executing,  6-1                  Backups, 2-1 8          to delete suspected ACMS      BIOLM, 2-12, 4-13,             files, 6-2                 BLISSA     ACMS_POST_INSTALL.COM               compiling the ACMSBLI.L32t=       executing manually,  4-1             library file, 4-17S8     ACMS_SETUP.COM                     BYTLM, 2-12, 4-14       checking for,  3-21o(       creation of,  3-21               CF       defining logical names in,       _______________________________*          4-5                           CDD6       editing,  4-5                     See Oracle CDD@       executing ACMS management        CLISYMTBL, 2-7, 2-8, 2-106          commands with, 4-7             setting,  2-104       execution of,  3-21              Command files;       installing shared images          ACMEXCPAR.COM,  4-8 :          with, 4-7                      ACMSEDIT.COM,  4-59     ACMS_SETUP_NEW.COM                  ACMSIVP.COM,  5-4E;       creation of,  3-22                ACMSPARAM.COM,  4-8 E       editing,  4-5                     ACMSTART.COM,  3-21, 4-2, 4-3N?       review of,  3-22                  ACMSTOP.COM,  3-13, 4-4tA     .ADB file                           ACMS_BUILD_MENU_FORM.COM,s/       See Application database             4-16 E     ADU                                 ACMS_DEINSTALL.COM,  6-1, 6-2 C       See Application Definition        ACMS_POST_INSTALL.COM,  4-1 C          Utility                        ACMS_SETUP.COM,  3-21, 4-5,n.     ADU$EDIT                               4-7A       defining as a logical name,       ACMS_SETUP_NEW.COM,  3-22 6          4-5                           Command Process:     Application Authorization           authorizing,  4-12:                                        Commands (Operator)E        Utility, 4-10                    failure with INVACMPAR error, .     Application database                   4-9)       .ADB file,  1-8                  CPy;     Application Definition Utility      See Command Process 3       installing shared images,        CP_PGFLQUOTAl6          4-6                            ACMS parameterB     ASTLM,  2-12, 4-13                     correcting by modifying=     Authorization,  4-10                      LARGEST_MESSAGEi;       ACMS processes,  4-11                   variable, 4-9t       new applications,  4-10        new devices,  4-10       Index-2t C                 ;                                           GBLSECTIONS,  4-6h<         D______________________________     calculating, 2-9I         DBMS                                requirements for installationt>          See Oracle CODASYL DBMS              ,  2-7, 2-8, 2-9B         DDU                               Granularity hint regionsB                                             and resident images onA          See Device Definition Utility        OpenVMS Alpha,  4-3          DECdtm servicesn+          and logical SYS$JOURNAL,  D-4    HrI          transaction logs                 _______________________________t.             See Transaction logs          HelpC         DECforms                            modifying the file, C-1   +          dependencies,  1-8               IyI         DECtrace                          _______________________________a0          See also Oracle Trace            ImagesE          predecessor to Oracle Trace,       resident on OpenVMS Alphae>             xiii                               installing, 4-3D         Development kit                           using ACMS startupC          description,  1-1                          procedure,  4-3T<         Device Definition Utility,             lists of, 4-36           4-10                            Installation9         DIOLM, 2-12, 4-14                   aborting, 3-2 <         Disk quotas, 2-6                    completing, 3-24:         Disk space, 2-3                     failures, 3-24C          limited space,  2-5, 3-4              error recovery, 3-26 ?          normal requirements,  2-3             parameters, 3-25 =                                                software, 3-25 ;         E                                      system, 3-24 H         _______________________________     informational messages, 3-18@         ENQLM, 2-12, 4-14                   kit information, 1-1  4                                             log, 3-1:         F______________________________     new files, 3-1<         FILLM, 2-12, 4-14                   preparation, 2-1:                                             questions, 3-89         G                                   starting, 3-1 ?         _______________________________     time required, 2-13cC         GBLPAGES, 4-6                     Installation Verification ;          calculating,  2-9                   Procedure, 5-1 A          requirements for installation      avoiding failure with C             ,  2-7, 2-8, 2-9                  INVACMPAR error,  5-4 <         GBLPAGFIL                           description, 5-1D          requirements for installation      run during installation,2             ,  2-7, 2-8                       3-23  C                                             starting independent of @                                               installation,  5-2  I                                                                   Index-3i                   3     IVP                                MAXPROCESSNTs8       See Installation Verification     SYSGEN parameterE          Procedure                         effect on MSS_POOLSIZE ando?                                               ACMS startup, 5-4n4     K______________________________    Message files6     Kits                                changing,  C-28                                         retrieving,  C-19       See ACMS                          translating,  C-1n  3                                        MSS_POOLSIZE =     L______________________________     ACMS system parametere@     Language-Sensitive Editor              setting to allow ACMS@       rebuilding environment and              startup, 4-10, 5-4            section files, 4-16F       requirements for ACMS kits,      N______________________________  0          1-6                           NODE_NAME@     LARGEST_MESSAGE                     settings for distributed;       variable required for                processing, 4-16m          ACMSPARAM.COMF          modifying to correct CP_      O______________________________.             PGFLQUOTA parameter,       OpenVMS2             4-9                         parameters  D     LCMP                                   prerequisite values,  2-6  3       See Log Manager Control           system diskh;          Program Utility                   backing up,  2-1 A     License Management Facility         user authorization,  2-13 B        (LMF), 1-2                      OpenVMS Alpha image-slicing0     License registration,  1-2, B-1      featureB     LMF                                 with resident images,  4-3>       See License Management           OpenVMS Cluster systemsD          Facility                       requirements for using ACMS,/     Log Manager Control Program            4-15w>        Utility                          transaction logs,  D-1/       creating transaction logs,       Operatoru0          D-6                            commands;                                            and ACMS startup D     LSE                                       failure with INVACMPAR  ;       See Language-Sensitive Editor              error, 4-9t  1                                        Oracle CDD :     M______________________________     dependencies,  1-8C     MAXPROCESSCNT                       requirements for ACMS kits,_.       SYSGEN parameter                     1-5:          effect on MSS_POOLSIZE and    Oracle CODASYL DBMS:             ACMS startup, 4-9           dependencies,  1-9       Index-4  r  a              4         Oracle Rdb                        PQL_DDIOLMI          dependencies,  1-9                 requirements for installation 9         Oracle Trace                          ,  2-7, 2-8d4          See also DECtrace                PQL_MDIOLMI          dependencies,  1-10                requirements for installationn9          successor to DECtrace,  xiii         ,  2-7, 2-8a5                                           PRCL,  2-12e6         P______________________________   PRCLM,  4-141         Page table entry                  Processe@          and resident images on             account quotas, 2-11I             OpenVMS Alpha,  4-3           Product Authorization Key,  B-1   I         PAK                               Q______________________________o  -          See Product Authorization Key    QTIcE         Parameters                          See Queued Task Initiatoru?          SYSGEN,  4-9, 5-4                Queued Task Initiator E             changing for resident           agent authorization, 4-12g0                images,  4-4               Quotas:          system                             disk, 2-6, 5-1A             changing                        process account, 2-11e#                for resident images,h+                   4-3                     R I                with AUTOGEN,  2-10        _______________________________ -         Pascal                            Rdb :          compiling the ACMSPAS.PAS          See Oracle Rdb7             file,  4-17                   Release notesyB          dependencies,  1-10                display options duringE         Performance                           installation,  3-1, 3-4 :          improving                          location, 3-26B             possible with resident          previous versions, 3-7I                images,  4-3                 printing during installation,e1         PGFLQUO, 2-12, 4-14                   3-6.;         PL/I                              Remote-access kit_<          dependencies,  1-10                description, 1-2=         Postinstallation procedure        Remote Manager,  ix <          executing manually,  4-1           installing, 3-226          running automatically during     RequirementsA             installation,  3-19             layered products, 1-3gH         PQL_DASTLM                          operating system components,1          requirements for installation        1-3l;             ,  2-7, 2-8                     privileges, 2-3CB         PQL_DBIOLM                          system parameters, 2-6E          requirements for installation         changing with AUTOGEN, 5             ,  2-7, 2-8                          2-10   <                                                checking, 2-9  I                                                                   Index-5     n              2     Resident images on OpenVMS         Task groups:        Alpha                            databases (cont'd)  ;       See Images                           restriction with ?     Run-time kit                              ACMSPARAM.COM andl@       description,  1-1                       ACMEXCPAR.COM, 4-9  +     S                                  TDMSdD     _______________________________     See Terminal Data Management1     Software                               System ?       determining version numbers,     Terminal Data Management /          1-3                             System ;       layered product requirements,     dependencies,  1-10t;          1-3                           TP Desktop Connector.C       operating system components,      requirements for ACMS kits,_.          1-3                               1-6@       recommended installation          shutting down to install4          order, 1-6                        ACMS, 1-6<       requirements for LSE,  1-6       Transaction logs, D-29       requirements for Oracle CDD,     Translation buffer0>          1-5                            and resident images on=       requirements for TP Desktop          OpenVMS Alpha, 4-3s6          Connector, 1-6                TroubleshootingE     Startup                             sources for assistance,  4-18        ACMS proceduresnF          editing,  4-5                 U______________________________*       system procedures                UDUC          editing,  4-2                  See User Definition Utility 0     SWLUP$EDIT                         UpgradingE       defining as a logical name,       on a distributed system,  1-8 3          4-5                           User account 9     SYS$JOURNAL                         privileges,  4-13 5       defining as a logical name,       quotas,  4-13 ;          D-4                            requirements,  4-13   D     SYSGEN parameters                  User Definition Utility, 4-11         See OpenVMS, parametersoF     System management                  V______________________________5       commands                         VIRTUALPAGECNTeE          in ACMS_SETUP.COM,  4-7        requirements for installation_  5     T______________________________        , 2-7, 2-8m5     Task groups                        VMSINSTAL, 3-3T6       databases                         invoking,  3-3:                                        VMSLICENSE.COM, B-2       Index-6e                     '         W______________________________R           WSDEF, 4-14          WSEXT, 4-14          WSQUO, 4-14O                                                                              I                                                                   Index-7S