          H                     ____________________________________________________-                     OpenVMS Alpha Version 6.2 3                     Upgrade and Installation Manual     -                     Order Number: AA-PV6XC-TE                          May 1995  D                     This document contains step-by-step instructionsB                     for installing and upgrading the OpenVMS AlphaI                     operating system on Alpha computers. It also includes D                     information about booting, shutdown, backup, and)                     licensing procedures.               H                     Revision/Update Information:  This manual supersedesA                                                   the OpenVMS AXP I                                                   Version 6.1 Upgrade and F                                                   Installation Manual.  G                     Software Version:             OpenVMS Alpha Version 5                                                   6.2   1                     Digital Equipment Corporation *                     Maynard, Massachusetts                 J           ________________________________________________________________           May 1995  @           Digital Equipment Corporation makes no representationsA           that the use of its products in the manner described in B           this publication will not infringe on existing or futureB           patent rights, nor do the descriptions contained in thisB           publication imply the granting of licenses to make, use,>           or sell equipment or software in accordance with the           description.  B           Possession, use, or copying of the software described inA           this publication is authorized only pursuant to a valid D           written license from Digital or an authorized sublicensor.  B           Digital conducts its business in a manner that conservesC           the environment and protects the safety and health of its 2           employees, customers, and the community.  D            Digital Equipment Corporation 1995. All rights reserved.  ;           The following are trademarks of Digital Equipment @           Corporation: AXP, Bookreader, CI, DEC, DECdtm, DECnet,=           DECwindows, Digital, HSC, InfoServer, LAT, OpenVMS, D           PATHWORKS, POLYCENTER, RRD42, RZ, TURBOchannel, UETP, VAX,C           VAX DOCUMENT, VMS, VMScluster, XUI, and the DIGITAL logo.   3           The following are third-party trademarks:   ;           Microsoft, MS, MS-DOS, and Windows are registered .           trademarks of Microsoft Corporation.  >           Motif is a registered trademark of the Open Software           Foundation, Inc.  @           All other trademarks and registered trademarks are the/           property of their respective holders.   E                                                                ZK6439   /           This document is available on CD-ROM.   D           This document was prepared using VAX DOCUMENT Version 2.1.                                Send Us Your Comments   C               We welcome your comments on this or any other OpenVMS H               manual. If you have suggestions for improving a particularD               section or find any errors, please indicate the title,A               order number, chapter, section, and page number (if E               available). We also welcome more general comments. Your C               input is valuable in improving future releases of our                documentation.  @               You can send comments to us in the following ways:  E               o  Internet electronic mail: openvmsdoc@zko.mts.dec.com   F               o  Fax: 603-881-0120 Attn: OpenVMS Documentation, ZKO3-4                  /U08                  o  Online form  C                  Print or edit the online form SYS$HELP:OPENVMSDOC_ @                  COMMENTS.TXT. Send the completed online form byE                  electronic mail to our Internet address, or send the E                  completed hardcopy form by fax or through the postal                   service.   4                  Please send letters or the form to:  .                  Digital Equipment Corporation&                  OpenVMS Documentation0                  110 Spit Brook Road, ZKO3-4/U08'                  Nashua, NH  03062-2698                   USA                 Thank you.                  I                                                                       iii                    )     How To Order Additional Documentation   C           Use the following table to order additional documentation 9           or information. If you need help deciding which ?           documentation best meets your needs, call 800-DIGITAL            (800-344-4825).                                                                                    iv                                 C   _________________________________________________________________   C                                                            Contents       C   Preface...................................................     xv      1  Getting Started  C               Overview......................................    1-2 C                   Introduction..............................    1-2 C                   Key Terms.................................    1-2 C               Examining Software and Hardware Components....    1-4 C                   Introduction..............................    1-4 C                   Hardware Components.......................    1-4 C                   Software Components.......................    1-4 C                   Operating System CD-ROM...................    1-5 C                   Required PALcode..........................    1-5 C                   Device Naming Conventions.................    1-7 C               Using the Operating System CD-ROM.............    1-8 C                   Using the Menu............................    1-8 C                   Sample Menu Display.......................    1-9 C                   How the Install or Upgrade Option Works...   1-10 C                   How the Layered Products Options Work.....   1-12 C                   How the DCL Option Works..................   1-13 C                   How the Shutdown Option Works.............   1-13 C                   What to Do Next...........................   1-13   5   2  Preparing to Install in a VMScluster Environment   C               Overview......................................    2-2 C                   Where to Find More Information............    2-2 C                   VMScluster Information You Will Need......    2-3 C                   What to Do Next...........................    2-6           C                                                                   v                    4     3  Installing the OpenVMS Alpha Operating System  E                 Overview......................................    3-2 E                     Introduction..............................    3-2 :                 Preparing to Respond to Prompts During theE                 Installation..................................    3-3 E                     Introduction..............................    3-3 E                     Summary of Prompts........................    3-3 8                 Installing from CD-ROM or from a RunningE                 System........................................    3-6 E                     Introduction..............................    3-6 E                     How to Begin..............................    3-6 E                 Booting the Operating System CD-ROM...........    3-7 E                     Introduction..............................    3-7 E                     Booting from the Local Drive..............    3-7 E                     Booting from the InfoServer...............    3-7 E                 Creating the System Disk......................   3-11 E                     Installing from the CD-ROM................   3-11 E                     Installing from a Running System..........   3-12 E                     Choosing INITIALIZE or PRESERVE...........   3-12 E                     Specifying the Target Disk................   3-13 E                     Specifying the Volume Label...............   3-14 E                     Setting the SYSTEM Account Password.......   3-14 E                     Becoming a Cluster Member.................   3-15 E                     Setting System Parameters.................   3-16 E                 Registering Licenses..........................   3-17 E                     Introduction..............................   3-17 E                     Types of OpenVMS Alpha Licenses...........   3-17 E                     For More Information......................   3-19 E                     How to Register Licenses..................   3-19 E                     Using the Licensing Procedure.............   3-21 E                 Completing the Installation...................   3-22 E                     Choosing Descriptive Help Text............   3-22 E                     Selecting Components......................   3-22 E                     List of Components........................   3-24 E                     Completing the Procedure..................   3-25 E                     What to Do Next...........................   3-27 E                 Installing Layered Products...................   3-28 E                     Introduction..............................   3-28 E                     How to Install............................   3-28 E                 Booting the New System Disk...................   3-32 E                     Introduction..............................   3-32 E                     Preparing to Boot the New System Disk.....   3-32 E                     How to Boot the New System Disk...........   3-33        vi                   I                     Joining a VMScluster..........................   3-34 I                         Introduction..............................   3-34 I                         SCSI VMScluster Systems...................   3-34 I                         VMScluster Prompts........................   3-34 I                         What to Do Next...........................   3-37 I                     Running AUTOGEN...............................   3-38 I                         How AUTOGEN Works.........................   3-38 I                         AUTOGEN Messages..........................   3-38 I                     Rebooting the System..........................   3-40 I                         Introduction..............................   3-40 I                         Rebooting the System Manually.............   3-40 I                     Logging in to the SYSTEM Account..............   3-41 I                         Introduction..............................   3-41 I                         Logging in to a Character Cell Terminal...   3-41 I                         Logging in to a Workstation...............   3-42 I                         What to Do Next...........................   3-42   >         4  After Installing the OpenVMS Alpha Operating System  I                     Overview......................................    4-2 I                     Registering Your Licenses.....................    4-3 I                         Introduction..............................    4-3 I                         For More Information......................    4-3 I                     Creating Accounts.............................    4-4 I                         Introduction..............................    4-4 I                         For More Information......................    4-4 I                     Backing Up Your System Disk...................    4-5 I                         Introduction..............................    4-5 I                         How to Back Up the System Disk............    4-5 I                         When to Back Up the System Disk...........    4-5 I                         For More Information......................    4-5 I                     Customizing the System........................    4-6 I                         Introduction..............................    4-6 I                         For More Information......................    4-6 ?                     Configuring and Starting DECnet for OpenVMS I                     Alpha Software................................    4-7 I                     Testing the System with UETP..................    4-8 I                         Introduction..............................    4-8 I                         For More Information......................    4-8 I                     Decompressing the System Libraries............    4-9 I                         Introduction..............................    4-9 I                         Determining Disk Space....................    4-9 I                         Methods of Using LIBDECOMP.COM............    4-9     I                                                                       vii                    E                     Responding to LIBDECOMP.COM Prompts.......   4-10 E                     Using LIBDECOMP.COM Interactively.........   4-10 E                     Using LIBDECOMP.COM in Batch..............   4-12 E                 Adding and Removing Files.....................   4-13 E                     Introduction..............................   4-13 E                     How to Add and Remove Files...............   4-13 E                     For More Information......................   4-13 E                 Preparing to Use OpenVMS Management Station...   4-14 E                     Introduction..............................   4-14 E                     For More Information......................   4-14 E                     Removing Files............................   4-14 E                 Installing Layered Products...................   4-15 E                     Procedure.................................   4-15 E                     Alternate Procedure.......................   4-16 E                     DECwindows Support........................   4-16 E                     Monitoring Performance History............   4-17 E                     Additional Notes..........................   4-17 E                 Backing Up the Customized System Disk.........   4-18 E                     Introduction..............................   4-18 8                     How to Back Up the Customized SystemE                     Disk......................................   4-18 E                     For More Information......................   4-18 E                 Configuring a Multihead System................   4-19 E                     Definition................................   4-19 E                     Introduction..............................   4-19 E                     How to Set Up the System..................   4-19 E                     For More Information......................   4-20 E                 Running AUTOGEN...............................   4-21 E                     Introduction..............................   4-21 E                     When to Run AUTOGEN.......................   4-21 E                     Modifying Parameters......................   4-21 E                     For More Information......................   4-22 E                 Postinstallation Checklist....................   4-23   :     5  Before Upgrading the OpenVMS Alpha Operating System  E                 Overview......................................    5-2 E                     For More Information......................    5-2 E                 Cautions and Restrictions.....................    5-3 E                     Introduction..............................    5-3 E                     Required Operating System Version.........    5-3 E                     Files and Directories.....................    5-3 E                     Licenses and Layered Products.............    5-4          viii                   >                     Preparing to Upgrade in a Volume ShadowingI                     Environment...................................    5-5 I                         Introduction..............................    5-5 I                         Creating a Nonshadowed Target Disk........    5-5_I                         Changing the Label........................    5-6 I                         Setting the Boot Device...................    5-6rI                         What to Do Next...........................    5-6 I                     Backing Up the System Disk....................    5-7 I                         Introduction..............................    5-7nI                         How to Back Up the System Disk............    5-7tI                         For More Information......................    5-7cI                     Preparing the System Disk.....................    5-8hI                         Introduction..............................    5-8 I                         Examining the System Disk.................    5-8 I                         Checking the Size of the System Disk......    5-8nI                         Verifying System Parameters...............    5-9 I                         What to Do Next...........................    5-9 I                     Preupgrade Checklist..........................   5-11s  ;         6  Preparing to Upgrade in a VMScluster Environment_  I                     Overview......................................    6-2iI                         Types of Upgrades.........................    6-2eI                         Adding a New System to the Cluster........    6-2lI                         For More Information......................    6-3eI                     Concurrent Upgrade............................    6-4iI                         Introduction..............................    6-4 I                         How a Concurrent Upgrade Works............    6-4fI                         Notes and Restrictions....................    6-4uI                         Preparing for a Concurrent Upgrade........    6-4 I                     Rolling Upgrade...............................    6-6nI                         Introduction..............................    6-6 I                         How a Rolling Upgrade Works...............    6-6 I                         Notes and Restrictions....................    6-6 I                         Preparing for a Rolling Upgrade...........    6-7r                    I                                                                        ix     A              3     7  Upgrading the OpenVMS Alpha Operating System   E                 Overview......................................    7-2hE                     Introduction..............................    7-2-7                 Upgrading from CD-ROM or from a Running E                 System........................................    7-3tE                     Introduction..............................    7-3dE                     How to Begin..............................    7-3eE                 Booting the Operating System CD-ROM...........    7-4 E                     Introduction..............................    7-4 E                     Booting from the Local Drive..............    7-4.E                     Booting from the InfoServer...............    7-4 E                 Performing the Upgrade........................    7-8 E                     Upgrading from the CD-ROM.................    7-8 E                     Upgrading from a Running System...........    7-9 E                     Choosing INITIALIZE or PRESERVE...........    7-9vE                     Specifying the Target Disk................   7-10nE                     Specifying the Volume Label...............   7-10uE                     Choosing Descriptive Help Text............   7-10gE                     Selecting Components......................   7-11.E                     Completing the Upgrade....................   7-13iE                     What to Do Next...........................   7-14 E                 Installing Layered Products...................   7-15 E                     Introduction..............................   7-15 E                     How to Install............................   7-15 E                 What to Do After the Shutdown.................   7-19 E                     Standalone Upgrade........................   7-19:E                     Concurrent VMScluster Upgrade.............   7-19eE                     Rolling VMScluster Upgrade................   7-20   9     8  After Upgrading the OpenVMS Alpha Operating System   E                 Overview......................................    8-2 E                 Re-Forming the Shadow Set.....................    8-3 E                     Introduction..............................    8-3 E                     How to Add Shadow Set Members.............    8-3yE                     Example...................................    8-4eE                 Registering New Licenses......................    8-5 E                     Introduction..............................    8-5 E                     For More Information......................    8-5_E                 Examining the AUTOGEN Report File.............    8-6 E                     Introduction..............................    8-6.E                     Interpreting the Report File..............    8-6 E                 Modifying the System Parameters File..........    8-7        xc n  .              I                         Introduction..............................    8-7.I                         System File Sizes.........................    8-7.I                         VMScluster Parameters.....................    8-8-I                     Examining Your Command Procedures.............    8-9 I                         Introduction..............................    8-9 I                         Site-Specific Files.......................    8-9 I                     Decompressing the System Libraries............   8-10eI                         Introduction..............................   8-10pI                         Determining Disk Space....................   8-10uI                         Methods of Using LIBDECOMP.COM............   8-10.I                         Responding to LIBDECOMP.COM Prompts.......   8-10eI                         Using LIBDECOMP.COM Interactively.........   8-11sI                         Using LIBDECOMP.COM in Batch..............   8-12.I                     Testing the System with UETP..................   8-13 I                         Introduction..............................   8-13 I                         For More Information......................   8-13 I                     Adding and Removing Files.....................   8-14hI                         Introduction..............................   8-14tI                         How to Add and Remove Files...............   8-14xI                         For More Information......................   8-14 I                     Preparing to Use OpenVMS Management Station...   8-15aI                         Introduction..............................   8-15.I                         For More Information......................   8-15.I                         Removing Files............................   8-15 I                     Installing Layered Products...................   8-16.I                         Introduction..............................   8-16.I                         Procedure.................................   8-16 I                         Alternate Procedure.......................   8-17 I                         DECwindows Support........................   8-17 I                         Monitoring Performance History............   8-18 I                         Additional Notes..........................   8-18nI                     Backing Up the Customized System Disk.........   8-19dI                         Introduction..............................   8-19r<                         How to Back Up the Customized SystemI                         Disk......................................   8-19gI                         For More Information......................   8-19iI                     Rebooting Cluster Members.....................   8-20fI                         Introduction..............................   8-20LI                         For More Information......................   8-20eI                     Running AUTOGEN...............................   8-21aI                         Introduction..............................   8-21PI                         Running After the Upgrade.................   8-21.I                         Running Weekly............................   8-21.    I                                                                        xi  1                 E                     For More Information......................   8-21 E                 Postupgrade Checklist.........................   8-22   *     A  Halt, Boot, and Shutdown Procedures  E                 Overview......................................    A-2.  E           Booting Operations..................................    A-3 E                 Booting the Operating System CD-ROM...........    A-4 E                     Introduction..............................    A-4 E                     Booting from the Local Drive..............    A-4 E                     Booting from the InfoServer...............    A-5 E                 Booting Manually from the System Disk.........    A-8 E                     Introduction..............................    A-8 E                     How to Boot Manually......................    A-8 E                 Performing a Conversational Boot..............   A-10 E                     Introduction..............................   A-10 E                     How to Perform a Conversational Boot......   A-10 E                     For More Information......................   A-12 E                 Booting with Minimum Startup..................   A-13 E                     Introduction..............................   A-13 E                     How to Boot with Minimum Startup..........   A-13ME                 Booting with the XDelta Utility (XDELTA)......   A-14rE                     Introduction..............................   A-14 E                     Boot Command Qualifier Values.............   A-14 E                     How to Boot with XDELTA...................   A-14 E                     For More Information......................   A-15 E                 Booting from a Different Directory............   A-16 E                     Introduction..............................   A-16 E                     How to Boot from a Different Directory....   A-16 :                 Booting with a PMAZB or PMAZC TURBOchannelE                 Adapter.......................................   A-17.E                     Introduction..............................   A-17lE                     Displaying Devices........................   A-17cE                     How to Boot...............................   A-18.E                     How Adapters Are Identified...............   A-18 E                     Example...................................   A-18t:                 Booting Over the Network with an AlternateE                 TURBOchannel Adapter..........................   A-19tE                     Introduction..............................   A-19 E                     How to Boot...............................   A-19 E                 Booting in an Emergency.......................   A-21 E                     Introduction..............................   A-21 E                     Booting with Default System Parameters....   A-21        xii     a              9                         Booting without Startup and Login I                         Procedures................................   A-23 >                         Booting without the User AuthorizationI                         File......................................   A-24   I               Set, Show, and Writeboot Operations.................   A-29 I                     Setting the System for Automatic Booting......   A-30 I                         Introduction..............................   A-30 I                         When Systems Can Boot Automatically.......   A-30 I                         How to Set the System.....................   A-30 I                     Setting and Showing Boot Devices..............   A-32 I                         Introduction..............................   A-32 I                         Setting the Boot Device...................   A-32lI                         Showing the Boot Device...................   A-32eI                         Cancelling the Boot Device................   A-33 I                     Setting Boot Parameters.......................   A-34 I                         Introduction..............................   A-34eI                         List of Valid Parameters..................   A-34 9                         How to Enter the SET BOOT_OSFLAGS I                         Command...................................   A-35 I                         Displaying Parameters.....................   A-36 I                     Using the Writeboot Utility...................   A-37 I                         Introduction..............................   A-37.I                         Invoking WRITEBOOT........................   A-37.  I               Halt and Shutdown Operations........................   A-394I                     Halting the System............................   A-40 I                         Introduction..............................   A-40 I                         How to Halt Your Alpha Computer...........   A-40 I                     Shutting Down the System......................   A-42 I                         Introduction..............................   A-42 I                         Orderly Shutdown..........................   A-42 I                         Emergency Shutdown with OPCCRASH.EXE......   A-42eI                         Emergency Shutdown with Crash Commands....   A-43g  I               Troubleshooting Procedures..........................   A-45.I                     If the System Does Not Boot...................   A-46dI                         Introduction..............................   A-46.I                         For Hardware Problems.....................   A-46HI                         For Software Problems.....................   A-46.I                     Detecting and Responding to System Problems...   A-47sI                         Introduction..............................   A-47.I                         Detecting System Problems.................   A-47 I                         How to Respond............................   A-48   I                                                                      xiii     f              /     B  Backing Up and Restoring the System Disk   E                 Overview......................................    B-2 E                     Reasons for Backing Up the System Disk....    B-2 E                     Suggested Procedures......................    B-3 E                     VMScluster Caution........................    B-3 E                 Backing Up the System Disk....................    B-5 E                     Getting Started...........................    B-5 E                     Mounting Devices..........................    B-6 E                     Entering the BACKUP Command...............    B-6 E                     Examples..................................    B-6 E                     Changing the CLUSTER_SIZE Parameter.......    B-7rE                     What to Do Next...........................    B-7iE                 Restoring the System Disk.....................    B-8oE                     Getting Started...........................    B-8oE                     Mounting Devices..........................    B-9nE                     Entering the BACKUP Command...............    B-9eE                     Examples..................................    B-9iE                     What to Do next...........................   B-10iE                 Alternate Backup and Restore Procedure........   B-11 E                     Introduction..............................   B-11oE                     Preparing an Alternate Disk...............   B-11.E                     Using the Alternate Disk..................   B-13.  $     C  License Management Supplement  E                 Overview......................................    C-2 <                     Using the License Unit Requirement TableE                     (LURT)....................................    C-2 E                 License Management Facility (LMF) Notes.......    C-7 E                     Restrictions..............................    C-8 E                     For More Information......................   C-10   2     D  Preparing to Use OpenVMS Management Station  E                 Overview......................................    D-2.E                     Introduction..............................    D-2DE                     Required Files............................    D-2.E                     Checklist.................................    D-3   E           Preparing Your Systems..............................    D-5gE                 Preparing Your OpenVMS System.................    D-6iE                     Introduction..............................    D-6 E                     Files Installed on OpenVMS................    D-6        xivC k  t              I                         Editing System Files......................    D-7i>                         Starting OpenVMS Management Station onI                         Other Nodes...............................    D-8.I                     Preparing Your PC.............................    D-9CI                         Introduction..............................    D-9.I                         Required Memory and Disk Space............    D-9.I                         Media.....................................    D-9.I                         Required Software.........................   D-10rI                         PATHWORKS Client Requirements.............   D-10.I                         Creating the Installation Media...........   D-11U  >               Installing the OpenVMS Management Station ClientI               Software on Your PC.................................   D-13.I                     Overview......................................   D-14rI                     Installing the Client Software................   D-15tI                         Installation Procedure....................   D-15oI                         Recovering from Errors....................   D-16 I                     Defining DECnet Nodes.........................   D-17 I                         Introduction..............................   D-17rI                         Procedure for Defining DECnet Nodes.......   D-17rI                         Files Created on the PC...................   D-19rI                     Getting Started...............................   D-20.I                         Introduction..............................   D-20.I                         Accessing Online Help.....................   D-20.  I               PATHWORKS Installation Tips and Guidelines..........   D-21.I                     Overview......................................   D-22 I                         Required Disk Space.......................   D-22-I                         About Installing and Configuring..........   D-22 I                     Installing Using MS-DOS ......................   D-23 I                     Configuring Using Windows.....................   D-25 I                         Starting Windows..........................   D-28 I                         Deleting a Directory......................   D-28            Glossary  
         Index.                I                                                                        xv                    
     Tables  E           3-1       Prompts for VMScluster Configurations.....   3-34n  7           A-1       SYSGEN Commands Used in the SYSBOOTeE                     Procedure.................................   A-11t  E           A-2       Emergency Boot Procedures.................   A-21L  E           C-1       License Unit Requirement Table (LURT).....    C-3i  E           D-1       Prerequisite and Optional Software........   D-10a  E           D-2       Disk Space Requirements...................   D-22t                                                                   xvig e  .                        I         _________________________________________________________________e  I                                                                   Preface                  INTRODUCTIONH               This manual contains installation, upgrade, and operationsD               information for Alpha computers that run OpenVMS Alpha(               operating system software.  "         WHO SHOULD USE THIS MANUAL@               This manual is intended for anyone responsible forH               installing or upgrading the OpenVMS Alpha operating systemB               and for the startup, shutdown, and backup operations@               required on Alpha computers running this software.             WHEN TO USE THIS MANUAL H               If you received factory-installed software (FIS) with yourG               Alpha computer, refer to that user documentation to start G               up your system for the first time. Use this manual if you D               need to install or upgrade the OpenVMS Alpha operatingH               system software yourself or if you need to perform certain6               startup, shutdown, or backup operations.  $         HOW THIS MANUAL IS ORGANIZED2               This manual is organized as follows:  E               o  Chapter 1 defines key terms and provides information.D                  about hardware and software components. Review thisG                  chapter before performing any installation or upgrade..  A               o  Chapter 2 provides preliminary information aboute@                  installing the operating system in a VMScluster                  environment.s  I               o  Chapter 3 describes how to install the operating system..  I                                                                      xvii. .  .              A           o  Chapter 4 describes the tasks you must perform after1-              installing the operating system.C  B           o  Chapter 5 describes how to prepare your system for an              upgrade..  B           o  Chapter 6 supplements Chapter 5 with additional tasksC              you must perform before upgrading a VMScluster system..  E           o  Chapter 7 describes how to upgrade the operating system..  A           o  Chapter 8 describes the tasks you must perform afteri,              upgrading the operating system.  E           o  Appendix A contains instructions for halting the system, E              booting the operating system CD-ROM and the system disk, C              using console commands to set system parameters, using @              the Writeboot utility, and invoking system shutdown              procedures.  @           o  Appendix B describes how to back up and restore the              system disk.n  @           o  Appendix C contains supplementary information about"              registering licenses.  D           o  Appendix D describes how to prepare your OpenVMS systemE              and your PC to run the OpenVMS Management Station server.!              and client software.   @           o  The Glossary defines key terms used in this manual.       REQUIRED DOCUMENTSB           Before installing, upgrading, or using the OpenVMS AlphaC           operating system on your Alpha computer, be sure you have ,           access to the following documents:  6           o  All cover letters included with your kit.  B           o  The OpenVMS Version 6.2 Release Notes, which providesB              important supplementary information about the OpenVMS$              Alpha operating system.  >           o  VMScluster Systems for OpenVMS and Guidelines forC              VMScluster Configurations, if you plan to install youryE              system in a VMScluster environment. (For SCSI VMScluster.B              information, see the OpenVMS Version 6.2 New Features              Manual.)   	     xviii  o  n              I               o  OpenVMS Version 6.2 New Features Manual, which describes.E                  enhancements and new support included in the OpenVMSr.                  Version 6.2 operating system.  D               o  The most recent version of the DECwindows Motif forC                  OpenVMS Installation Guide and Managing DECwindows F                  Motif for OpenVMS Systems (if you plan to install andH                  customize DECwindows Motif for OpenVMS Alpha software).  G               o  The hardware manuals that are supplied with your Alpha E                  computer. These manuals provide detailed informationnG                  about your system hardware, including the operation of.>                  the system unit, the drives, and the monitor.           ADDITIONAL DOCUMENTSF               During the course of installing, upgrading, or using theH               OpenVMS Alpha operating system on your Alpha computer, youE               might need to refer to the following documents as well:   E               o  The OpenVMS License Management Utility Manual, which E                  contains detailed information about registering your #                  software licenses..  E               o  A Comparison of System Management on OpenVMS AXP and.I                  OpenVMS VAX, which explains similarities and differences H                  between managing OpenVMS Alpha and OpenVMS VAX systems.H                  If you have been responsible for installation, upgrade,H                  and related system management operations on OpenVMS VAXF                  systems, review that manual before performing similar9                  operations on your OpenVMS Alpha system..  D               o  The OpenVMS System Manager's Manual and the OpenVMSD                  System Management Utilities Reference Manual, whichG                  contain information about system management operations.B                  and utilities that you might need to use when youG                  install, upgrade, customize, and maintain your OpenVMS.G                  Alpha system. The OpenVMS System Manager's Manual also.C                  describes in more detail how to use the POLYCENTER.F                  Software Installation utility to add or remove files,H                  install other software, and perform related operations.  G               o  DECnet for OpenVMS Guide to Networking, which contains.H                  detailed information about using the DECnet for OpenVMS                   Alpha software.  I                                                                       xix. .  .              ?           o  Volume Shadowing for OpenVMS, which you might need.A              if you are installing or upgrading the OpenVMS Alpha.8              operating system on a shadowed system disk.  C           o  OpenVMS Management Station Overview and Release Notes,t>              which provides information about getting started,>              setting up, and using OpenVMS Management Station.       Conventions   ?           The name of the OpenVMS AXP operating system has been.A           changed to OpenVMS Alpha. Any references to OpenVMS AXP.<           or AXP are synonymous with OpenVMS Alpha or Alpha.  @           In this manual, every use of DECwindows and DECwindows@           Motif refers to DECwindows Motif for OpenVMS software.  A           The following conventions are also used in this manual:   C           Ctrl/x           A sequence such as Ctrl/x indicates that B                            you must hold down the key labeled CtrlD                            while you press another key or a pointing)                            device button.   @           <Return>         In examples, a key name enclosed in a@                            box indicates that you press a key onD                            the keyboard. (In text, a key name is not.                            enclosed in a box.)  8            . . .           Horizontal ellipsis points inA                            examples indicate one of the followingo)                            possibilities:   @                            o  Additional optional arguments in a:                               statement have been omitted.  @                            o  The preceding item or items can be9                               repeated one or more times.c  E                            o  Additional parameters, values, or otherv9                               information can be entered.c             xx i  .                D               .                Vertical ellipsis points indicate theD               .                omission of items from a code exampleG               .                or command format; the items are omitted.D                                because they are not important to the5                                topic being discussed..  G               [ ]              In command format descriptions, bracketsrB                                indicate optional elements. You canG                                choose one, none, or all of the options.iF                                (Brackets are not optional, however, inC                                the syntax of a directory name in andC                                OpenVMS file specification or in the E                                syntax of a substring specification in 8                                an assignment statement.)  H               boldface text    Boldface text represents the introductionH                                of a new term or the name of an argument,9                                an attribute, or a reason..  F                                Boldface text is also used to show userB                                input in Bookreader versions of the&                                manual.  >               italic text      Italic text indicates important>                                information, complete titles ofG                                manuals, or variables. Variables include.G                                information that varies in system output.B                                (Internal error number), in commandE                                lines (/PRODUCER=name), and in commandl@                                parameters in text (where device-D                                name contains up to five alphanumeric+                                characters).4  F               UPPERCASE TEXT   Uppercase text indicates a command, theH                                name of a routine, the name of a file, orG                                the abbreviation for a system privilege.   G               -                A hyphen in code examples indicates thatmF                                additional arguments to the request areA                                provided on the line that follows.k        I                                                                       xxi                      @           numbers          All numbers in text are assumed to beE                            decimal unless otherwise noted. Nondecimal D                            radixes-binary, octal, or hexadecimal-are0                            explicitly indicated.                                                                                     xxii                         I                                                                         1SI         _________________________________________________________________.  I                                                           Getting Started.                                                                            I                                                       Getting Started 1-1.    -           Overview    E     _________________________________________________________________        Overview         INTRODUCTIONB           This chapter defines key terms and describes preliminary?           procedures you must perform before an installation oro           upgrade.    
     KEY TERMS C           The following are a few key terms you need to know before ,           you install or upgrade the system:  E           ___________________________________________________________.E           Term__________________Definition___________________________r  A           Operating system      The CD-ROM containing the OpenVMS E           CD-ROM                Alpha operating system. This software.@                                 is supplied in a format that theE                                 computer cannot use until you performe;                                 an installation or upgrade.   C           HSx device            A self-contained, intelligent, masseE                                 storage subsystem that lets computers.A                                 in a VMScluster environment sharerD                                 disks. The disk on which you installC                                 or upgrade the operating system can D                                 be connected to one of these systems=                                 (for example, an HSC or HSD).   >           InfoServer            A general-purpose disk storageA                                 server that allows you to use the B                                 operating system CD-ROM to installE                                 the operating system on remote client C                                 systems connected to the same localt3                                 area network (LAN).   @           Local drive           A drive, such as an RRD42 CD-ROMA                                 drive, that is connected directly A                                 to an Alpha computer. If you have B                                 a standalone Alpha computer, it isC                                 likely that all drives connected to.<                                 the system are local drives.       1-2 Getting Started  1         I                                                                  Overview     I               ___________________________________________________________ I               Term__________________Definition___________________________a  F               Source drive          The drive that holds the operatingG                                     system CD-ROM during the upgrade or 1                                     installation.   C               System disk           The disk that contains (or will.H                                     contain) the OpenVMS Alpha operatingB                                     system in a usable format. TheE                                     installation or upgrade procedure.H                                     converts the OpenVMS Alpha operatingE                                     system to this usable format wheneF                                     transferring the software from theI                                     operating system CD-ROM to the system.)                                     disk.   H               Target drive          The drive that holds the system diskG                                     during the upgrade or installation. I               ___________________________________________________________                                                     I                                                       Getting Started 1-3g .  .      .     Examining Software and Hardware Components    E     _________________________________________________________________d  .     Examining Software and Hardware Components         INTRODUCTIONB           Before beginning an installation or upgrade, be sure youD           have all the required hardware and software components, as.           described in the following sections.         HARDWARE COMPONENTS =           Before you begin an installation or upgrade, do the            following:  @           o  Be sure the hardware has been installed and checkedD              for proper operation. For detailed information, see theD              hardware manuals you received with your Alpha computer.  <           o  Be sure you know how to turn on and operate theB              components of your system, including the system unit,B              console, monitor, drives, terminals, and printers. If@              necessary, read the hardware manuals that came with              these components.  D           o  Set up your system to record the installation procedureC              on either a hardcopy terminal or a printer attached to_A              the console terminal. (See your hardware manuals for C              more details about connecting those components to yourmE              system.) If you do not do this, the screen messages willoC              be lost. You will need a transcript in case there is ar-              problem during the installation.E       SOFTWARE COMPONENTS   =           Before you begin an installation or upgrade, do the            following:  A           o  Be sure you have all the items listed on the bill ofuD              materials in the distribution kit. If your distributionE              kit is incomplete, notify Multivendor Customer Services, @              and request priority shipment of any missing items.  A           o  Before installing the OpenVMS Alpha operating systemtB              software, review all cover letters and release notes.       1-4 Getting Started  e  t      I                                Examining Software and Hardware Componentso               OPERATING SYSTEM CD-ROMnH               Included in your kit is the OpenVMS Alpha operating systemG               CD-ROM, which you use to install or upgrade the operating:E               system, or to perform operations such as backing up theo<               system disk. The CD-ROM is labeled as follows:  9               CD-ROM Label:         OpenVMS[TM] Alpha[TM]s9                                     Operating System V6.2e>                                     Software and Documentation  ,               Volume Label:         ALPHA062  F               Note: The volume label is the machine-readable name thatG               the OpenVMS Alpha operating system and InfoServer systems '               use to access the CD-ROM.            REQUIRED PALCODEG               If your computer console does not have a specific minimumhA               version of the privileged architecture library codepG               (PALcode), you may not be able to boot your system duringsH               the installation or upgrade procedure. Digital recommends,G               therefore, that you do the following before performing ans&               installation or upgrade:  B               1. At the console prompt (>>>) on your running AlphaF                  system, enter the SHOW CONFIGURATION command (or SHOWC                  PAL command on DEC 7000 and DEC 10000 Alpha seriestI                  systems). The system display will indicate which versione5                  of PALcode your computer is running.   A               2. Refer to the most recent OpenVMS Alpha operatingoA                  system cover letter or release notes, or contactsE                  your Multivendor Customer Services representative tosI                  determine whether your system is running the required or 8                  recommended minimum version of PALcode.  D               3. If the PALcode is below the required or recommendedF                  minimum, upgrade your console by either following theG                  directions contained in the hardware manuals that came H                  with your Alpha computer or contacting your Multivendor2                  Customer Services representative.        I                                                       Getting Started 1-5i u         .     Examining Software and Hardware Components      E           Note: If you boot the operating system CD-ROM without firsti?           upgrading your console to the required or recommended =           minimum PALcode, the system will display one of the            following messages:o  A           o  If you do not have the required minimum PALcode, the A              system displays a fatal error message similar to theh              following:   I     APB-F-PALREV, PALcode revision 5.15 is below required minimum of 5.41              UNABLE TO CONTINUE  @           o  If you do not have the recommended minimum PALcode,A              the system displays a warning message similar to the2              following:   L     APB-W-PALREV, PALcode revision 5.25 is below recommended minimum of 5.48  9              Although you will still be able to boot your ?              system, contact your Multivendor Customer Services ?              representative about upgrading your console to thet>              recommended minimum version of the PALcode before:              installing or upgrading the operating system.  ?           Note that for AlphaServer 2100, 8200, and 8400 serieshA           computers, the required and recommended minimum PALcoden           version is 1.11.                                         1-6 Getting Startede u         I                                Examining Software and Hardware Componentst      !         DEVICE NAMING CONVENTIONS D               When you perform specific operations, you are asked toI               specify device names for the source drive and target drive. D               When specifying those device names, note the following!               naming conventions:   C               o  When the source drive is a local CD-ROM drive, the 9                  device name is similar to the following:i                    DKA400   I               o  When the source drive is a CD-ROM drive connected to the E                  InfoServer, the device name is always the following:a                    DAD1e  G               o  When the target drive is a local disk, the device nameb-                  is similar to the following:a                    DKA0:  0                  Note the following conventions:  <                  -  DK is the device code of the boot device  ?                  -  A is the boot device controller designationr  ;                  -  0 is the unit number of the boot deviced  I               o  On Alpha systems configured in certain VMScluster or HSxrI                  environments, the device naming convention is similar toT                  the following:l                    DUA20.14.0.2.0i  C                  The values you specify identify components such astE                  the boot device, controller, unit number of the bootrI                  device, HSx controller node number, and channel numbers.pE                  Because these values vary depending on your specificnF                  hardware configuration, refer to the owner, operator,B                  and technical service manuals that came with your3                  computer for detailed information.V      I                                                       Getting Started 1-7l g         %     Using the Operating System CD-ROMe    E     _________________________________________________________________   %     Using the Operating System CD-ROM          USING THE MENUC           The OpenVMS Alpha operating system CD-ROM includes a menugA           system that allows you to easily upgrade or install theaD           operating system and to perform related operations such asC           backing up the system disk and installing certain layeredsD           products that are included on the operating system CD-ROM.C           This command procedure starts automatically when you bootnA           the OpenVMS Alpha operating system CD-ROM, displaying aiE           menu from which you choose options to perform the followinge           tasks:  E           o  Install or upgrade the operating system from the CD-ROM,a?              using the POLYCENTER Software Installation utilityy  A           o  List the layered products that can be installed from B              the CD-ROM using the POLYCENTER Software Installation              utility  @           o  Install layered products from the CD-ROM, using the5              POLYCENTER Software Installation utility   ?           o  Enter a DCL environment from which you can perform B              preinstallation or maintenance tasks such as mountingD              or showing devices and backing up or restoring files on              the system disk  !           o  Shut down the system   B           Review the following sections to understand how the menuE           works. You will then be prepared to choose appropriate menu A           options when you are asked to do so before, during, and +           after an installation or upgrade.                        1-8 Getting Starteda e  t      I                                         Using the Operating System CD-ROMr               SAMPLE MENU DISPLAY 7          The following is a sample display of the menu:o  =              OpenVMS Alpha (TM) Operating System, Version 6.2   T              Copyright (c) 1995 Digital Equipment Corporation.  All rights reserved.  /              Installing required known files...s  #              Configuring devices...I  L              ***************************************************************  J              You can install or upgrade the OpenVMS Alpha operating systemM              or you can install or upgrade layered products that are includedo:              on the OpenVMS Alpha operating system CD-ROM.  H              You can also execute DCL commands and procedures to performD              "standalone" tasks, such as backing up the system disk.  0              Please choose one of the following:  B                  1)  Install or upgrade OpenVMS Alpha Version V6.2N                  2)  List layered product kits that this procedure can install:                  3)  Install or upgrade layered product(s)8                  4)  Execute DCL commands and procedures*                  5)  Shut down this system  8          Enter CHOICE or ? to repeat menu: (1/2/3/4/5/?)                                I                                                       Getting Started 1-9p a         %     Using the Operating System CD-ROMo      +     HOW THE INSTALL OR UPGRADE OPTION WORKSn@           When you choose the install or upgrade option (1) fromC           the menu, the system asks whether you want to preserve or C           initialize the system disk. The display is similar to the            following:  ;             There are two choices for Installation/Upgrade:t  F             INITIALIZE - removes all software and data files that wereI                 previously on the target disk and installs OpenVMS Alpha.   M             PRESERVE -- installs or upgrades OpenVMS Alpha on the target disk B                 and retains all other contents of the target disk.  P            * NOTE: You cannot use PRESERVE to install OpenVMS Alpha on a disk onM                 which OpenVMS VAX or any other operating system is installed.   >           Do you want to INITIALIZE or to PRESERVE? [PRESERVE]  *           Specifying_the_INITIALIZE_Option  ?           When you specify the INITIALIZE option, the following             operations take place:  D           o  All software and data files that were previously on the%              target disk are removed.l  =           o  The OpenVMS Alpha operating system is installed.r  :           Specify the INITIALIZE option and perform a full6           installation under the following conditions:  @           o  If your Alpha computer is new (it has never had anyE              version of the operating system running on it, including )              factory-installed software)._  ?           o  If your Alpha computer is running a version of the E              OpenVMS Alpha operating system and you want to overwrite B              the entire contents of the system disk (the operating;              system, application software, and user files).e  E           o  If you want to create a new system disk but keep the old_<              one (if you want to alternate between the two).  B           o  If you are running the OpenVMS Alpha operating system@              but cannot upgrade. For example, if you changed the@              names of system directories on the system disk, theB              upgrade procedure will not work correctly. Therefore,?              unless you chose to restore the system disk to its_       1-10 Getting Started _  _      I                                         Using the Operating System CD-ROM_      @                  original directory structure, you would have to0                  reinstall the operating system.                                                                                      I                                                      Getting Started 1-11r           %     Using the Operating System CD-ROMr      (           Specifying the PRESERVE_Option(           ------------------------------=           When you specify the PRESERVE option, the following.            operations take place:  E           ___________________________________________________________.F           IF ...                THEN ...                                D           the OpenVMS Alpha     the following operations take place:E           operating system      o  The OpenVMS Alpha operating systeme0           is not already           is installed.           installed on theC           target disk,          o  All other contents of the target 5                                    disk are retained.C  E           the OpenVMS Alpha     the OpenVMS Alpha operating system is 5           operating system      upgraded, as follows: E           is installed on the   o  Old operating system files and newo@           target disk,             files are merged or replaced.  C                                 o  All other contents of the targetd5                                    disk are retained.oE           ___________________________________________________________a  D           Note: If you intend to choose the PRESERVE option (because>           there are certain files on the disk that you want toB           retain), Digital recommends that you first make a backupB           copy of your system disk. If there is any problem during<           the installation or upgrade which might affect theA           integrity of the disk, you will have the backup copy as_           a safeguard.  )     HOW THE LAYERED PRODUCTS OPTIONS WORK D           After you have installed or upgraded the operating system,E           you can use the menu to install certain layered products aslD           well. The layered products options allow you to first viewB           the list of layered products that can be installed usingE           the POLYCENTER Software Installation utility (option 2) ande*           then to install them (option 3).  A           Note: When you boot the OpenVMS operating system CD-ROM A           and select the option to install layered products, that >           installation procedure does not run the Installation@           Verification Procedure (IVP) for each layered product.D           Because the operating system is booted from the CD-ROM and       1-12 Getting Started    i      I                                         Using the Operating System CD-ROM       F               the layered products are installed on a different deviceC               (the target disk), the IVPs cannot execute correctly. C               However, you can run the IVP for each layered product G               after you boot the target system (see the layered product I               installation documents for information on running the IVP)._            HOW THE DCL OPTION WORKSC               When you choose the DCL option (4) from the menu, you D               can use a subset of DCL commands (such as SHOW DEVICE,D               MOUNT, and BACKUP) to perform specific preinstallationE               and maintenance operations. Note, however, that this isDG               a restricted DCL environment in that certain DCL commandsdI               and utilities will not function as expected because you areiF               booting from read-only or write-locked media and because7               the full system startup is not performed.e  E               A triple dollar sign system prompt ($$$) indicates thatrI               you are in this restricted DCL environment, as shown in the                 following example:                 $$$ SHOW DEVICE   F               To exit from the DCL environment and return to the menu,'               enter the LOGOUT command.   %         HOW THE SHUTDOWN OPTION WORKShD               When you choose the shutdown option (5) from the menu,H               your system shuts down and you are returned to the consoleH               prompt (>>>). The system displays a message similar to the               following:  *                   Shutting down the system  .                       SYSTEM SHUTDOWN COMPLETE           WHAT TO DO NEXTeE               Now that you have reviewed key terms, examined hardwareCH               and software requirements, and learned how to use the menuG               system included on the OpenVMS Alpha operating system CD-i,               ROM, you can do the following:          I                                                      Getting Started 1-13M i  d      %     Using the Operating System CD-ROMe    E           ___________________________________________________________g7           IF ...                               THEN ...r  ?           you want to install the              go to Chapter 2.t*           operating system in a VMScluster           environment,  ?           you want to install the operating    go to Chapter 3.n"           system in a nonclustered           environment,  ?           you want to upgrade the operating    go to Chapter 5.p(           system in a standalone, Volume"           Shadowing, or VMScluster           environment,  @           you want only to back up or          go to Appendix B.#           restore_your_system_disk,lE           ___________________________________________________________                                                            1-14 Getting Started e  b                    I                                                                         2 I         _________________________________________________________________   I                          Preparing to Install in a VMScluster Environment                                                                             I                      Preparing to Install in a VMScluster Environment 2-1o ,  u           Overview    E     _________________________________________________________________r       Overview  D           This chapter contains information you should review beforeA           performing an installation in a VMScluster environment..?           This will help you have have a clear understanding of A           VMScluster systems so you can enter correct information )           when you are prompted to do so.0  D           Note: Before installing the OpenVMS Alpha operating system:           in a VMScluster environment, note the following:  A           o  If you enter incorrect VMScluster information duringlB              the installation, you might have to repeat the entireC              installation procedure. Therefore, review this chaptere9              carefully before beginning the installation.y  C           o  If you configure your OpenVMS Alpha Version 6.2 systemv@              in a mixed-architecture VMScluster environment that@              includes VAX computers, those VAX computers must beD              running only Version 5.5-2, Version 6.0, or Version 6.11              of the OpenVMS VAX operating system.   "     WHERE TO FIND MORE INFORMATION@           Before installing the operating system in a VMSclusterA           environment, be sure you review the relevant VMScluster <           information, contained in the following documents:  D           o  The cover letters and the software product descriptions0              included with your distribution kit  B           o  OpenVMS Version 6.2 New Features Manual, for detailedE              information about SCSI VMScluster configurations, setup,               and management.  2           o  The OpenVMS Version 6.2 Release Notes  A           o  If you are installing the operating system in a DSSIoD              VMScluster system, the DSSI VMScluster Installation and"              Troubleshooting Guide  D           Be sure the following sources of information are available           as well:  +           o  VMScluster Systems for OpenVMSt  5           o  Guidelines for VMScluster Configurationsc  3           o  DECnet for OpenVMS Guide to Networking   8     2-2 Preparing to Install in a VMScluster Environment           I                                                                  Overviewt      /               o  Your network or system manager   ,         VMSCLUSTER INFORMATION YOU WILL NEEDE               If during the installation you answer YES to the system C               prompt asking whether your system will be a member of B               a VMScluster, you will need to provide the following9               information after you boot the system disk:-  I               ___________________________________________________________f               RequiredI               Information___________Explanation__________________________r  H               Type of               Configuration types (CI, DSSI, SCSI,F               configuration         local area, or mixed-interconnect)I                                     are distinguished by the interconnect A                                     device that the VAX and Alpha F                                     computers in the VMScluster use toA                                     communicate with one another.   H               DECnet node name      See the network or system manager toH               and node address      obtain the DECnet node name and nodeE                                     address for the computer on which H                                     you are installing the OpenVMS AlphaD                                     operating system. See the DECnetG                                     for OpenVMS Guide to Networking forcC                                     additional information as well.                                       I                      Preparing to Install in a VMScluster Environment 2-3e r  e           Overview    E           ___________________________________________________________            RequiredE           Information___________Explanation__________________________a  B           Allocation class      During the installation procedure,D           value                 you will be asked for the allocationD                                 class value (ALLOCLASS) of the AlphaD                                 computer on which you are installingC                                 the OpenVMS Alpha operating system.a,                                 For example:  O                                 Enter a value for Alpha143 ALLOCLASS parameter:e  ?                                 Refer to VMScluster Systems for-C                                 OpenVMS for the rules on specifying_8                                 allocation class values.  A                                 Note that in a mixed-interconnectO;                                 VMScluster environment, they@                                 allocation class value cannot beB                                 zero if the nodes serve DSSI or CI@                                 disks. It must be a value from 1A                                 to 255. This is also true for anyeE                                 Alpha computer that is connected to at1                                 dual-pathed disk.o  D                                 After you enter the allocation classA                                 value, the installation procedureR@                                 uses it to automatically set the=                                 value of the ALLOCLASS systema*                                 parameter.  ?           Whether you want a    Refer to VMScluster Systems for =           quorum disk           OpenVMS to help you determine A                                 whether you want a quorum disk int,                                 the cluster.                    8     2-4 Preparing to Install in a VMScluster Environment    o      I                                                                  Overviewi    I               ___________________________________________________________i               RequiredI               Information___________Explanation__________________________n  F               Location of the       On a nonclustered system, the pageE               page and swap files   and swap files are on one or moreeB                                     local disks but on a clusteredC                                     system, the files are on one orAF                                     more local or clustered disks. SeeE                                     VMScluster Systems for OpenVMS toCI                                     help you determine where the page and F                                     swap files will be located for theF                                     system on which you are installingF                                     the OpenVMS Alpha operating system-                                     software.o  G               Systems that will     If you are going to set up either aoF               be MOP[1] servers,    local area or a mixed-interconnectH               disk servers, and     cluster, you will need to make these3               tape servers          determinations.   F               Cluster group         If you are going to set up a localH               number and cluster    area cluster or a mixed-interconnectF               password              cluster that is LAN-based, use theD                                     following rules to determine theF                                     cluster group number and password:  G                                     o  Cluster group number-A number in H                                        the range from 1 to 4095 or 61440/                                        to 65535   F                                     o  Cluster password-Must be from 1D                                        to 31 alphanumeric charactersG                                        in length and can include dollartD                                        signs ($) and underscores (_)I               ___________________________________________________________   N               [1]Servers that use the DECnet Maintenance Operations Protocol.                 I                      Preparing to Install in a VMScluster Environment 2-5n l  o           Overview           WHAT TO DO NEXT D           After you have completed all the tasks in this chapter, go1           to Chapter 3 to begin the installation.                                                                                     8     2-6 Preparing to Install in a VMScluster Environment    t                    I                                                                         3iI         _________________________________________________________________   I                             Installing the OpenVMS Alpha Operating System                                                                             I                         Installing the OpenVMS Alpha Operating System 3-1r    l           Overview    E     _________________________________________________________________        Overview         INTRODUCTION5           This chapter describes the following tasks:l  D           o  Preparing to respond to prompts during the installation  B           o  Installing from the operating system CD-ROM or from a              running system   %           o  Creating the system diskr  !           o  Registering licensese  2           o  Selecting operating system components  (           o  Installing layered products  (           o  Booting the new system disk  !           o  Rebooting the systemt  ,           o  Joining a VMScluster (optional)             o  Running AUTOGEN  -           o  Logging in to the SYSTEM accountF                                5     3-2 Installing the OpenVMS Alpha Operating Systemd ,  e      I                   Preparing to Respond to Prompts During the Installation     I         _________________________________________________________________d  ?         Preparing to Respond to Prompts During the Installationp             INTRODUCTIONC               At different points during the installation, you must >               respond to prompts asking you to supply specificI               information. This manual and the Help text available during G               the installation procedure tell you how to obtain most of H               this information and how to make decisions when responding"               to specific prompts.  G               However, Digital recommends that you review the followingiH               summary before you begin the installation so that you haveH               an understanding ahead of time of the types of information'               you will need to provide.            SUMMARY OF PROMPTSI               During the installation, the system will prompt you for thet$               following information:  A               o  The names of the source drive, target drive, and F                  local area network device (if you are booting from an$                  InfoServer system).  F               o  Whether you want to select the INITIALIZE or PRESERVE4                  option (as described in Chapter 1).  I               o  A volume label for the target disk (if you choose not toe/                  use the default volume label).s  H               o  A password for the SYSTEM account. You will be prompted>                  to enter a password of at least 8 characters.  I               o  Whether you want to join a VMScluster system and, if so,_7                  what kind (as described in Chapter 2).n  G               o  DECnet node name and address (or values for the system 6                  parameters, SCSNODE and SCSSYSTEMID).  G                  Important: These settings identify your system by namekG                  and number in a DECnet or cluster environment. Be surehE                  you can supply a node name and DECnet address beforeeE                  you begin the installation. Note as well that if youSG                  supply a DECnet address, the system will automaticallyiG                  calculate the SCSSYSTEMID value. If necessary, see thedF                  network or system manager to obtain this information.  I                         Installing the OpenVMS Alpha Operating System 3-3            ;     Preparing to Respond to Prompts During the Installation       D           o  Information listed on Product Authorization Keys (PAKs)B              for your OpenVMS licenses. To register your licenses,E              you will need to enter the information listed on the PAKo              for each license.                                                                                  5     3-4 Installing the OpenVMS Alpha Operating System2 t  g      I                   Preparing to Respond to Prompts During the Installationn      E               o  Operating system components that you want to install E                  (including DECwindows and OpenVMS Management StationuF                  files). You can install all components by default, or<                  you can select each component individually.  F                  (Note that you must install the DECwindows componentsE                  if you plan to install the separate DECwindows Motif I                  for OpenVMS Alpha layered product. You must also install H                  all of the OpenVMS Management Station server and clientI                  software files if you plan to use this product with youre                  PC.)                                                                     I                         Installing the OpenVMS Alpha Operating System 3-5  e  c      3     Installing from CD-ROM or from a Running Systemo    E     _________________________________________________________________n  3     Installing from CD-ROM or from a Running Systems         INTRODUCTIONA           The OpenVMS Alpha Version 6.2 operating system includestC           procedures that allow you to easily install the operating D           system using the POLYCENTER Software Installation utility.C           In console mode, you can boot the operating system CD-ROM B           to begin the installation procedure. On a system that isA           already running the OpenVMS Alpha Version 6.2 operatingt>           system, you can invoke the installation procedure by.           entering a command at the DCL level.         HOW TO BEGINC           Depending on whether you are installing the OpenVMS Alpha C           operating system from the operating system CD-ROM or from ?           a running OpenVMS Alpha Version 6.2 system, begin the            procedure as follows:e  H           ______________________________________________________________O           If installing from ...        Then ...                               :  I           the operating                 go to the section titled Booting tC           system CD-ROM,                the Operating System CD-ROM   J           a running Version             go to the section titled Creating 7           6.2 system,                   the System Disk H           ______________________________________________________________                              5     3-6 Installing the OpenVMS Alpha Operating System     r      I                                       Booting the Operating System CD-ROMm    I         _________________________________________________________________   +         Booting the Operating System CD-ROMh             INTRODUCTIONE               To get started, boot the OpenVMS Alpha operating systemgF               CD-ROM either from your local CD-ROM drive or from a CD-H               ROM drive connected to the InfoServer, as described in the!               following sections.     $         BOOTING FROM THE LOCAL DRIVE  G               To boot the operating system CD-ROM from the local CD-ROM (               drive, follow these steps:  I               1. Insert the operating system CD-ROM into the local CD-ROMa                  drive.l  C               2. At the console prompt (>>>), enter the SHOW DEVICE I                  command so you can identify the name of the CD-ROM drivel(                  (for example, DKA400:).  @               3. Enter the boot command in the following format:  -                  BOOT -flags 0,0 source-drives  C                  Substitute the device name of the CD-ROM drive (asrE                  listed in the SHOW DEVICE display) for source-drive.   I                  For example, if the SHOW DEVICE display lists the device I                  name of your CD-ROM drive as DKA400, enter the followingo2                  command and press the Return key:  +                  >>> BOOT -flags 0,0 DKA400e  #         BOOTING FROM THE INFOSERVER G               To boot the operating system CD-ROM using the InfoServer, !               follow these steps:v  D               1. At the console prompt, enter the following command:  =                  >>> BOOT -FL 0,0 -FI APB_062 lan-device-name   0                  Note the following conventions:  H                  o  APB_062 is the file name of the APB program used for?                     the initial system load (ISL) boot program.o  I                         Installing the OpenVMS Alpha Operating System 3-70 r  r      '     Booting the Operating System CD-ROMt      =              o  lan-device-name is the name of the local areaiC                 network (LAN) device identified with your computer.,A                 For information about the LAN devices your system,;                 supports, refer to the following table. Forv@                 additional information, see the hardware manualsB                 that you received with your Alpha computer and the5                 OpenVMS Software Product Description.a  E              ________________________________________________________g:                                         Ethernet      FDDIE              Alpha_Computer_____________Device________Device_________   :              AlphaServer 1000 series    ERA0, EWA0    FRA0  :              AlphaServer 2000 series    ERA0, EWA0    FRA0  :              AlphaServer 2100 series    ERA0, EWA0    FRA0  :              AlphaServer 8200 series    EXA0, EWA0    FXA0  :              AlphaServer 8400 series    EXA0, EWA0    FXA0  7              AlphaStation 200 series    EWA0          -   7              AlphaStation 400 series    EWA0          -   7              DEC 2000 series            ERA0          -   >              DEC 3000 series            ESA0          "n/ESA0"  7              DEC 4000 series            EZA0          -   :              DEC 7000 series            EXA0          FXA0  E              DEC 10000 series           EXA0          FXA0           oE              ________________________________________________________   >              Notes: If you are using a DEC 3000 or 4000 series(              system, note the following:  @              o  On DEC 3000 series systems, you can boot through>                 the InfoServer using an alternate TURBOchannelB                 device, such as a PMAD (Ethernet) or DEFTA (FDDI),D                 by specifying the device name as "n/ESA0". The valueD                 for n is the TURBOchannel slot number, which you canD                 obtain by entering the SHOW CONFIGURATION command atC                 the console prompt (>>>) and examining the display.lD                 For more information, see the section titled Booting?                 Over the Network with an Alternate TURBOchannel '                 Adapter, in Appendix A.o  5     3-8 Installing the OpenVMS Alpha Operating System            I                                       Booting the Operating System CD-ROM       E                  o  On DEC 4000 series, you must specify the ISL file E                     name in uppercase (APB_062). In addition, if your F                     system uses console firmware prior to Version 3.2,6                     enter the BOOT command as follows:  >                     >>> BOOT -FL 0,0 -start 0 -FI APB_062 EZA0  G               2. The InfoServer ISL program then displays the following                   menu:  5                  Network Initial System Load Functiond                  Version 1.1  ,                    FUNCTION         FUNCTION                      ID 0                      1     -        Display Menu(                      2     -        Help2                      3     -        Choose Service2                      4     -        Select Options(                      5     -        Stop  +                  Enter a function ID value:   G               3. Respond to the prompts as follows, pressing the Returnl&                  key after each entry:  0                  a. Enter 3 for the function ID.  .                  b. Enter 2 for the option ID.  6                  c. Enter the service name (ALPHA062).  *                  A sample display follows:  5                  Enter a function ID value: 3<Return>   '                  OPTION          OPTIONn                     ID/                     1     -       Find Services :                     2     -       Enter known Service Name  4                  Enter an Option ID value: 2<Return>=                  Enter a Known Service Name: ALPHA062<Return>   F               Note: If you boot the OpenVMS Alpha operating system CD-D               ROM from an InfoServer but lose your connection duringH               the installation procedure (the system is unresponsive andF               pressing Ctrl/Y does not return you to the menu), do the               following:  I                         Installing the OpenVMS Alpha Operating System 3-9m c  y      '     Booting the Operating System CD-ROM     E           ___________________________________________________________ G           IF ...                THEN ...                               u  1           you previously        do the following: E           chose the             1. Reboot the OpenVMS Alpha operating 1           INITIALIZE option,       system CD-ROM.   E                                 2. Choose the install option from the D                                    menu and perform the installation>                                    again, as described in this+                                    chapter.u  1           you previously        do the following:_E           chose the PRESERVE    1. Reboot the OpenVMS Alpha operatingn1           option,                  system CD-ROM.d  ?                                 2. Enter the DCL environment by C                                    choosing option 2 from the menu.   C                                 3. Mount the device containing your A                                    backup copy of the target disk E                                    and the device that is your target (                                    disk.  B                                 4. Restore the backup copy of your>                                    target disk by entering the?                                    appropriate BACKUP commands. ?                                    (See Appendix B for complete E                                    information using MOUNT and BACKUP ?                                    commands to restore a systemo)                                    disk.)s  D                                 5. Log out from the DCL environment.  E                                 6. Choose the install option from the D                                    menu and perform the installation>                                    again, as described in this+                                    chapter.eE           ___________________________________________________________               6     3-10 Installing the OpenVMS Alpha Operating System           I                                                  Creating the System Disk     I         _________________________________________________________________             Creating the System Disk    "         INSTALLING FROM THE CD-ROMD               After you boot the operating system CD-ROM, choose theG               install option (1) from the menu displayed on the screen.e               For example:  @                OpenVMS Alpha (TM) Operating System, Version V6.2  P      $!  Copyright (c) 1995 Digital Equipment Corporation.  All rights reserved.    4                   Installing required known files...  (                   Configuring devices...  P                 ****************************************************************  M                 You can install or upgrade the OpenVMS Alpha operating systemeP                 or you can install or upgrade layered products that are included=                 on the OpenVMS Alpha operating system CD-ROM.   K                 You can also execute DCL commands and procedures to perform G                 "standalone" tasks, such as backing up the system disk.   3                 Please choose one of the following:_  C                    1  Install or upgrade OpenVMS Alpha Version V6.2 P                    2)  List layered product kits that this procedure can install<                    3)  Install or upgrade layered product(s):                    4)  Execute DCL commands and procedures,                    5)  Shut down this system  @               Enter CHOICE or ? to repeat menu: (1/2/3/4/5/?)) 1  D               After you choose the install option, go to the sectionD               titled Choosing INITIALIZE or PRESERVE to continue the               procedure.          I                        Installing the OpenVMS Alpha Operating System 3-11                 Creating the System Disk      $     INSTALLING FROM A RUNNING SYSTEMB           If you are installing the operating system from an AlphaC           system that is already running Version 6.2 of the OpenVMS B           Alpha operating system, enter the following command from;           the SYSTEM account and then press the Return key:   +           $ @SYS$SYSTEM:AXPVMS$PCSI_INSTALL   ?           After you enter the command, go to the section titledSD           Choosing INITIALIZE or PRESERVE to continue the procedure.  #     CHOOSING INITIALIZE OR PRESERVE D           After you choose the install option (if you are installingE           from the operating system CD-ROM) or start the AXPVMS$PCSI_ ?           INSTALL command procedure (if you are installing fromiA           a running OpenVMS Alpha Version 6.2 system), the system 9           displays the following information and prompts:a  C         ***********************************************************e  B         The installation procedure will ask a series of questions.  .               () - encloses acceptable answers+               [] - encloses default answerso  =         Type your response and press the <Return> key.  Type:   *               ? - to repeat an explanation=               ^ - to change prior input (not always possible)e  7         There are two choices for Installation/Upgrade:o  B         INITIALIZE - removes all software and data files that wereE             previously on the target disk and installs OpenVMS Alpha.   I         PRESERVE -- installs or upgrades OpenVMS Alpha on the target disk >             and retains all other contents of the target disk.  F        * NOTE: You cannot install OpenVMS Alpha on an existing disk onI             which OpenVMS VAX or any other operating system is installed.   9     Do you want to INITIALIZE or to PRESERVE? [PRESERVE])e      6     3-12 Installing the OpenVMS Alpha Operating System e  e      I                                                  Creating the System Disko      F               Respond to the INITIALIZE or PRESERVE prompt as follows:  I               ___________________________________________________________ J               IF ...                THEN ...                                5               your system disk is   do the following:s8               new,                  1. Enter INITIALIZE.  <                                     2. Press the Return key.  5               you want to remove    do the following:r8               all files from an     1. Enter INITIALIZE.               existing systemd<               disk,                 2. Press the Return key.  F               you want to retain    press the Return key to accept the7               certain files on an   default (PRESERVE).SJ               existing_disk,                                              I               ___________________________________________________________e  "         SPECIFYING THE TARGET DISKD               The procedure next asks you for the name of the targetI               disk. If you enter a question mark (?), the system displaysPF               a list of devices on your system. Select the appropriate:               disk and respond to the prompt. For example:  M                   You must enter the device name for the target disk on which 2                   OpenVMS Alpha will be installed.  B               Enter device name for target disk: (? for choices) ?  P             Device        Device           Error    Volume       Free  Trans MntP             Name          Status           Count     Label      Blocks Count Cnt0             DKA100:       Online               00             DKA200:       Online               00             DKA400:       Online wrtlck        0  G               Enter device name for target disk: (? for choices) DKA200t                I                        Installing the OpenVMS Alpha Operating System 3-13C d              Creating the System Disk           SPECIFYING THE VOLUME LABELnC           The system then prompts you for the volume label and asks ?           if the information is correct. You can keep the labeli@           already assigned to the disk, accept the default labelD           assigned by the system (AXPVMSSYS), or specify a differentA           volume label (with a limit of 12 characters that can be C           letters A-Z, numbers 0-9, dollar signs ($),  hyphens (-),_E           or underscores (_)).  After you select the volume label andlE           choose to continue by answering Yes to the next prompt, the C           target disk is initialized and mounted, and page and swap )           files are created. For example:l  ,               DKA200: is now labeled SYSDISK  ;           Do you want to keep this label? (Yes/No) [Yes] NOd  @           Enter volume label for target system disk: [AXPVMSSYS]  E               You have chosen to install OpenVMS Alpha on a new disk.h  C               The target system disk, DKA200:, will be initialized.e+               It will be labeled AXPVMSSYS.eH               Any data currently on the target system disk will be lost.  "           Is this OK? (yes/No) YES  2               Initializing and mounting target ...  '     SETTING THE SYSTEM ACCOUNT PASSWORDuE           Before you respond to the system prompt asking you to enter @           a password for the SYSTEM account, note the following:  C           o  Passwords must be at least eight characters in length;./              they do not appear on the display.   ?           o  Press the Return key after you enter the password.   ?           o  After you enter the password, the procedure checks ?              to make sure it meets the requirements for a valide              password.  ,           The following is a sample display:  ?               You must enter a password for the SYSTEM account.   G               The password must be a minimum of 8 characters in length.g.               It will be checked and verified.N               The system will not accept passwords that can be guessed easily.  &           Password for SYSTEM account:  6     3-14 Installing the OpenVMS Alpha Operating System           I                                                  Creating the System Disks      8               Re-enter SYSTEM password for verification:  D               If you enter the password incorrectly or if the systemG               determines that the password is too easy for another user F               to guess, the system displays an error message and gives>               you the opportunity to specify a valid password.  !         BECOMING A CLUSTER MEMBERrE               The procedure now asks if your system will be part of a ?               cluster. The display is similar to the following:C  I               Will this system be a member of a VMScluster? (Yes/No) [No]l  H               If you answer Yes, you will be asked a series of questionsC               about the cluster after you boot the new system disk.0                                                            I                        Installing the OpenVMS Alpha Operating System 3-15l                Creating the System Disk           SETTING SYSTEM PARAMETERSyE           Next, you must set two parameters, SCSNODE and SCSSYSTEMID,0C           so that your system is identified by name and number in a B           DECnet or cluster environment. If you plan to use DECnet@           software, you must specify a DECnet address (which the>           system uses to calculate the SCSSYSTEMID value). TheA           following is an example of the system display and valid            responses:  O               For your system to operate properly, you must set two parameters:o*                   SCSNODE and SCSSYSTEMID.  P               SCSNODE can be from 1 to 6 letters or numbers.  It must contain at               least one letter.o  P               If  you  plan  to  use DECnet, SCSNODE must be the DECnet Phase IVB               node name, or the DECnet OSI (Phase V) node synonym.  P               If  you  have multiple OpenVMS systems, the SCSNODE on each system               must be unique.p             Enter SCSNODE: mynodet  P               If  you  plan  to use DECnet, SCSSYSTEMID must be set based on the               DECnet address.   5           Do you plan to use DECnet (Yes/No) [Yes]: Y   9               DECnet Phase IV addresses are in the format   7                   DECnet_area_number.DECnet_node_number   >               DECnet_area_number is a number between 1 and 63.8               DECnet_node_number is a number 1 and 1023.  I               If you plan to use DECnet OSI (Phase V), enter the Phase IV J               compatible address.  If you plan to use DECnet OSI (Phase V)?               WITHOUT Phase IV compatible addresses, enter 0.0.p  7           Enter DECnet (phase IV) Address [1.1]: 63.180A  F               SCSSYSTEMID will be set to 64692, calculated as follows:  C                   (DECnet_area_number * 1024) + DECnet_node_number)s  6     3-16 Installing the OpenVMS Alpha Operating System    W      I                                                      Registering Licenses     I         _________________________________________________________________4           Registering Licenses             INTRODUCTIONG               Before you can use the OpenVMS Alpha operating system andeF               its components, you must register all licenses in one of               two ways:_  D               o  During the installation (which Digital recommends),>                  by responding to the prompts displayed by the5                  SYS$UPDATE:VMSLICENSE.COM procedure.h  F               o  After the installation, by using the LICENSE REGISTERB                  command or by invoking SYS$UPDATE:VMSLICENSE.COM.  '         TYPES OF OPENVMS ALPHA LICENSES/D               The operating system uses one or more of the followingH               types of licenses, depending on your hardware and software               configuration.  C               Note: All OpenVMS Alpha licenses include the NO_SHAREoB               attribute and remain with the initial host computer.  I         _________________________________________________________________ I         Type_of_License____________Description___________________________   E         Operating System Base      Grants the right to noninteractivetB         License                    use of the remote batch, print,F                                    application, and computing servicesF                                    of the operating system on a singleF                                    processor and authorizes one directH                                    login (for system management purposesH                                    only). This license is a prerequisiteE                                    for OpenVMS Alpha Interactive UserF,                                    Licenses.                  I                        Installing the OpenVMS Alpha Operating System 3-17                 Registering Licenses    E     _________________________________________________________________eE     Type_of_License____________Description___________________________   =     Interactive User           Grant the right to interactivelA     Licenses                   use of the OpenVMS Alpha operatinggC                                system, provided you have previously @                                installed the appropriate OpenVMSE                                Alpha Operating System Base License on0C                                your Alpha computer. These licenses, B                                which are concurrent, are available?                                in any quantity desired or as an 6                                unlimited user license.  C                                You can add interactive users to the:A                                computer at any time by specifyingeC                                the same node name on the additional B                                Interactive User License PAK and by@                                following the license combinationA                                procedure described in the OpenVMS A                                License Management Utility Manual.   A     Symmetric                  Upgrades the Operating System Base ?     Multiprocessing            License and all Interactive User_@     (SMP) Extension to the     licenses (including Unlimited) toD     Operating System Base      the matching multiprocessing level ofE     License                    your DEC 4000 or DEC 7000 series Alpha (                                computer.  D                                Because the Symmetric MultiprocessingD                                (SMP) Extension grants all the rightsB                                the existing Base and User licensesC                                provided at the uniprocessing level, A                                you do not need to reinstall those =                                licenses when you upgrade to ah@                                multiprocessing system. Each time?                                you upgrade your system to a neweB                                multiprocessing level (for example,E                                from a DEC 7000 Model 620 Alpha system E                                to a DEC 7000 Model 630 Alpha system), ?                                you add an SMP Extension to yourhH                                existing_licenses.                       E     _________________________________________________________________           6     3-18 Installing the OpenVMS Alpha Operating System           I                                                      Registering Licenses                FOR MORE INFORMATIONG               In addition to reviewing the license information provided C               in this chapter, you can also refer to the following:   B               o  Appendix C, which contains notes and supplementalD                  information about licenses and licensing procedures  E               o  The OpenVMS License Management Utility Manual, which B                  contains complete, detailed information about the$                  licensing procedure            HOW TO REGISTER LICENSESG               After you install the OpenVMS Alpha operating system, the 4               system displays the following message:  L                   If you have Product Authorization Keys (PAKs) to register,,                   you can register them now.  T               Do you want to register any Product Authorization Keys? (Yes/No) [Yes]  /               Respond to the prompt as follows:   I               ___________________________________________________________nK               IF ...                THEN ...                               x  5               you choose to         do the following:tD               register your         1. Be sure you review Appendix CC               licenses at this         and have the OpenVMS Licensei@               time (which Digital      Management Utility Manual1               recommends),             available.*  E                                     2. Be sure you have a copy of theeF                                        Product Authorization Key (PAK)E                                        for each license that you willO0                                        register.  G                                     3. Type Y and press the Return key.   A                                     4. Register your licenses, as E                                        described in the next section.           I                        Installing the OpenVMS Alpha Operating System 3-19e    d           Registering Licenses    E           ___________________________________________________________ E           IF ...                THEN ...                                1           you choose not        do the following:HC           to register your      1. Type N and press the Return key.            licenses at this>           time,                 2. Skip the next section about;                                    registering licenses and ?                                    follow the directions in them@                                    section titled Completing the0                                    Installation.  E                                 3. After completing the installation,aC                                    register your licenses using the A                                    LICENSE REGISTER command or byuE                                    invoking SYS$UPDATE:VMSLICENSE.COMS>                                    before performing any other:                                    postinstallation tasks.E           ___________________________________________________________                                                       6     3-20 Installing the OpenVMS Alpha Operating System a  t      I                                                      Registering Licensesi      %         USING THE LICENSING PROCEDURE.C               Entering Y (Yes) to register your licenses during thea@               installation invokes the SYS$UPDATE:VMSLICENSE.COM>               procedure, which displays the following message:  5               VMS License Management Utility Options:c  9                   1. REGISTER a Product Authorization Keyo@                   2. AMEND an existing Product Authorization KeyA                   3. CANCEL an existing Product Authorization Keyo4                   4. LIST Product Authorization KeysA                   5. MODIFY an existing Product Authorization KeyIB                   6. DISABLE an existing Product Authorization KeyA                   7. DELETE an existing Product Authorization KeyR?                   8. COPY an existing Product Authorization Key ?                   9. MOVE an existing Product Authorization Key A                  10. ENABLE an existing Product Authorization Key :                  11. SHOW the licenses loaded on this node=                  12. SHOW the unit requirements for this nodeR  (                  99. Exit this procedure  L                  Type '?' at any prompt for a description of the informationN                  requested. Press Ctrl/Z at any prompt to return to this menu.  0               Enter one of the above choices [1]  E               1. Select the appropriate options (beginning with 1, as F                  indicated in the display) until you have successfully.                  registered all required PAKs.  D               2. After you register all your licenses, exit from theD                  License Management procedure by entering option 99.                        I                        Installing the OpenVMS Alpha Operating System 3-21L .              Completing the Installation     E     _________________________________________________________________t       Completing the Installationt    "     CHOOSING DESCRIPTIVE HELP TEXT0         Next, the system prompts you as follows:  D         The installation can provide brief or detailed descriptions.P         In either case, you can request the detailed descriptions by typing "?".  ?         Do you always want detailed descriptions? (Yes/No) [No]   =         If you answer Yes, the system will display additionala*         explanatory text with each prompt.       SELECTING COMPONENTSD           The system next displays the following message, indicating>           that the procedure is ready to install the operating           system:e  2           The following product has been selected:           DEC AXPVMS VMS V6.2   E           *** DEC AXPVMS VMS V6.2: VMS Operating System, Version V6.2e  >               COPYRIGHT (c) 29-MAR-1995 -- All rights reserved  +               Digital Equipment Corporation   D           After the system displays a series of additional messages,E           it asks if you want all the default values, meaning all the B           files and subgroups of files for each component included@           in the operating system. The display is similar to the           following:  G               Do you want all the default values for this product [YES]g  ?           Notes: When selecting components, note the following:   A           o  If you want all the default values, press the Return               key.i  B              If you want to select components individually, answerC              NO. The system will then prompt you for each group andV              subgroup of files.   @           o  If you are not sure whether you want certain files,@              request help by entering a question mark (?) at the6              prompt for that file (or group of files).  6     3-22 Installing the OpenVMS Alpha Operating System e  o      I                                               Completing the Installatione      G               o  After you select all the files you want, you will have H                  an opportunity to view your selections and make changes                   (if necessary).  H               o  You can select three OpenVMS reference manuals providedB                  online with the operating system in ASCII format:E                  OpenVMS Master Index, OpenVMS Glossary, and Overview *                  of OpenVMS Documentation.  E               o  If you plan to install the separate DECwindows Motif D                  for OpenVMS Alpha layered product, you must installH                  the DECwindows base support and workstation support (toE                  run windowing software on Alpha workstations or in aeE                  VMScluster that includes workstations or Xterminals)aB                  included with the OpenVMS Alpha operating system.  E               o  OpenVMS Management Station software is automaticallyhF                  installed on your OpenVMS system disk when you acceptI                  all the default values. If you do not accept the default G                  values, you must select the OpenVMS Management Station G                  component (server and client files) if you plan to use F                  that product. After the installation is complete, youD                  can then prepare your OpenVMS Alpha system and yourF                  PC to run OpenVMS Management Station by following the4                  procedures described in Appendix D.  E               o  If you decide after the installation to change which H                  OpenVMS Alpha operating system files you want installedD                  on your system, you can use the POLYCENTER SoftwareF                  Installation utility on your running system to add or                  remove files.  7               o  After you boot the new system disk andm9                  log in, you can obtain information abouti4                  individual system files by enteringA                  HELP SYSTEM_FILES at the dollar sign prompt ($).a                  I                        Installing the OpenVMS Alpha Operating System 3-23i t              Completing the Installations           LIST OF COMPONENTS?           Following is the list of components included with the 5           OpenVMS Alpha Version 6.2 operating system:i  1           Accounting Log Report Generator Utility '           Access Control List Utilitiesl)           Print and Batch Queue Utilitiesl0           DECdtm Distributed Transaction Manager.           DECnet Phase IV / DECnet/OSI Support               DECnet Phase IVS               DECnet/OSI0               DECnet Incoming Remote File Access-               DECnet Incoming Remote Terminal !               DECnet Network Testn(               DECnet Remote Task Loading           Programming Support                Debugger Utility7               Image Dump Utility (ANALYZE/PROCESS_DUMP)m2               RMS Analyze and FDL Editor Utilities               Message Utilityr@               System Shareable Image and Object Module Libraries               Macro librariesE)               Macro-32 Migration Compiler .               TLB intermediary form of STARLET#               Fortran Require Files                 C Object Libraries               C Header Files-               X/Open Transport Interface LibsE)           RMS Journaling Recovery Utility $           System Programming Support@               Support for ISO 9660 and High Sierra CDrom Formats               MONITORNI               Analyze Object File Utility (ANALYZE/IMAGE, ANALYZE/OBJECT)t               Delta DebuggerO               System Dump Analyzer Utility (ANALYZE/SYSTEM, ANALYZE/CRASH_DUMP) .               Miscellaneous Symbol Table Files9           OpenVMS Management Station Software -- PC files_0           Coordinated Universal Time Files (UTC)           Utilitiesa"               OpenVMS Mail Utility               Dump Utility:               DIGITAL Standard Runoff (DSR) Text Formatter               Phone Utility                Help Library  6     3-24 Installing the OpenVMS Alpha Operating System h         I                                               Completing the Installation       *                   Foreign Terminal Support7                   LAT-11 Terminal Server (via Ethernet) =                   Error Log Generator Utility (ANALYZE/ERROR)6,                   Terminal Fallback Facility.                   TECO Interactive Text Editor6                   National Character Set Utility (NCS)"                   DIAGNOSE Utility5                   XPG4 Internationalization Utilitiesi!               Bliss Require Files                Example Filese3               Message Facility Files (HELP/MESSAGE) &               Translated Image Support               UETP Files#               Documentation Manuals !                   Master Glossaryi                   Master INDEX3                   Overview of OpenVMS Documentation $               Support for DECwindows.                   DECwindows workstation files                   video fontsE3                       100 dots per inch video fontsP            COMPLETING THE PROCEDUREE               When you have answered all the prompts and selected thenE               components you want installed, the system gives you theoE               opportunity to review your selections (and make changes @               if necessary), then installs the product, providesB               informational messages, and returns you to the menu.,               Following is a sample display.  F               Note: If you are installing from a running OpenVMS Alpha@               Version 6.2 system, the system displays the dollarC               sign prompt ($) instead of the 5-option menu when the '               installation is complete.   6                   Do you want to view the values? [NO]                  I                        Installing the OpenVMS Alpha Operating System 3-25                 Completing the Installation       3         %PCSIUI-I-DONEASK, execution phase startingm0         The following product will be installed:         DEC AXPVMS VMS V6.2 N         %PCSI-I-VOLINFO, estimated space information for volume DISK$AXPVMSSYSE         -PCSI-I-VOLSPC, 265572 required; 811128 available; 545556 net P         Portion Done: 10%...20%...30%...40%...50%...60%...70%...80%...90%...100%1         The following product has been installed:_         DEC AXPVMS VMS V6.2_  -             The installation is now complete._  H               When the newly installed system is first booted, a specialB               startup procedure will be run.  This procedure will:  P                  o  Configure the system for standalone or VMScluster operation.8                  o  Run AUTOGEN to set system parametersD                  o  Reboot the system with the newly set parameters.  F               You can shut down now or continue with other operations.  C             Process SYSTEM_1 logged out at  29-MAR-1995 14:55:52.16e  N               ****************************************************************  K               You can install or upgrade the OpenVMS Alpha operating system N               or you can install or upgrade layered products that are included;               on the OpenVMS Alpha operating system CD-ROM.   I               You can also execute DCL commands and procedures to perform E               "standalone" tasks, such as backing up the system disk.   1               Please choose one of the following:   C                   1)  Install or upgrade OpenVMS Alpha Version T6.2 O                   2)  List layered product kits that this procedure can install ;                   3)  Install or upgrade layered product(s) 9                   4)  Execute DCL commands and procedureso+                   5)  Shut down this systemo  9           Enter CHOICE or ? to repeat menu: (1/2/3/4/5/?)           6     3-26 Installing the OpenVMS Alpha Operating System r         I                                               Completing the Installation                WHAT TO DO NEXTcD               If you want to install layered products, including theE               DECwindows Motif for OpenVMS layered product, go to thes               next section.   G               If you do not want to install layered products or performyH               any other operations prior to booting the new system disk,H               choose 5 from the menu to shut down the system. The system2               display is similar to the following:  A               Enter CHOICE or "?" to repeat menu: (1/2/3/4/5/?) 5r  *                   Shutting down the system  '                SYSTEM SHUTDOWN COMPLETEp  C               After you complete the installation and shut down theaE               system, go to the section titled Booting the New Systemy               Disk.                                                     I                        Installing the OpenVMS Alpha Operating System 3-27                 Installing Layered Productsh    E     _________________________________________________________________        Installing Layered Products          INTRODUCTION?           You can use the menu system included on the operatingf@           system CD-ROM to install certain layered products withD           the POLYCENTER Software Installation utility. You can viewA           a list of the layered products that can be installed in B           this way by choosing option 2 from the menu. (To installE           layered products that are not listed, see Chapter 4 and thea?           installation documentation for each layered product.)          HOW TO INSTALLC           To install layered products using the POLYCENTER SoftwarenD           Installation utility, choose option 2 to view the list and%           then option 3. For example:   +         Please choose one of the following:   =             1)  Install or upgrade OpenVMS Alpha Version V6.2 I             2)  List layered product kits that this procedure can install 5             3)  Install or upgrade layered product(s)_3             4)  Execute DCL commands and procedures_%             5)  Shut down this system   5     Enter CHOICE or ? to repeat menu: (1/2/3/4/5/?) 2   G         The following layered product kits are available on the OpenVMS B         operating system CD-ROM and can be installed at this time:  7     DEC AXPVMS AMDS V6.1 found in DKB400:[KITS.AMDS061]h<     DEC AXPVMS DWMOTIF V1.2-3 found in DKB400:[KITS.DWMOTIF]6     DEC AXPVMS POSIX V2.0 found in DKB400:[KITS.POSIX]>     DEC AXPVMS SOFTWIN V1.0 found in DKB400:[KITS.SOFTWINDOWS]:     DEC AXPVMS SWXCR V2.0 found in DKB400:[KITS.SWXCR$KIT]  H         ****************************************************************  E         You can install or upgrade the OpenVMS Alpha operating system H         or you can install or upgrade layered products that are included5         on the OpenVMS Alpha operating system CD-ROM.   C         You can also execute DCL commands and procedures to perform ?         "standalone" tasks, such as backing up the system disk.m  +         Please choose one of the following:   6     3-28 Installing the OpenVMS Alpha Operating System _  _      I                                               Installing Layered Products       A                 1)  Install or upgrade OpenVMS Alpha Version V6.2eM                 2)  List layered product kits that this procedure can install 9                 3)  Install or upgrade layered product(s)t7                 4)  Execute DCL commands and procedures )                 5)  Shut down this systeml  9         Enter CHOICE or ? to repeat menu: (1/2/3/4/5/?) 3   G             ***********************************************************t  D             If you choose to install or upgrade to DECwindows Motif,&             please note the following:  I               o If you did not select the OpenVMS DECwindows base supportNM                 and workstation files options, DECwindows Motif will not run.AC                 You must add these options to use DECwindows Motif.i  N               o If you are upgrading to DECwindows Motif from version V1.1 andK                 want to save the OSF/Motif Release 1.1.3 programming files, F                 DO NOT upgrade now.  Instead, see the DECwindows MotifK                 installation manual and follow the instructions for running &                 PCSI_INSTALLATION.COM.  G             You must enter the device name for the target disk on which 5             the layered product(s) will be installed.l  A         Enter device name for target disk: (? for choices) DKA200,  )             DKA200: is labeled AXPVMSSYS.   D         The installation can provide brief or detailed descriptions.P         In either case, you can request the detailed descriptions by typing "?".  ?         Do you always want detailed descriptions? (Yes/No) [No]r  #            1 - DEC AXPVMS AMDS V6.1 (            2 - DEC AXPVMS DWMOTIF V1.2-3$            3 - DEC AXPVMS POSIX V2.0&            4 - DEC AXPVMS SOFTWIN V1.0$            5 - DEC AXPVMS SWXCR V2.0(            6 - All products listed above            7 - Exitc           Desired Product(s): 2   0         The following product has been selected:!         DEC AXPVMS DWMOTIF V1.2-3t  &         Do you want to continue? [YES]  I                        Installing the OpenVMS Alpha Operating System 3-29. O  h           Installing Layered Products       L     *** DEC AXPVMS DWMOTIF V1.2-3: DECwindows Motif V1.2-3 for OpenVMS Alpha  P         Copyright Digital Equipment Corporation 1988, 1995. All rights reserved.  %         Digital Equipment Corporationr  +         This product uses the PAK: DW-MOTIF.  E         Do you want all the default values for this product? [YES] noS  4         DECwindows Motif runtime support files [YES]  .         Programming Support (C Language) [YES]  )         Fortran programming support [YES]e  (         PASCAL programming support [YES]  "         Programming examples [YES]  8         Translated Image Support (OSF/Motif V1.1.3) [NO]  /         Do you want to view the values? [NO] no   .    %PCSIUI-I-DONEASK, execution phase starting+    The following product will be installed:i    DEC AXPVMS DWMOTIF V1.2-3I    %PCSI-I-VOLINFO, estimated space information for volume DISK$AXPVMSSYSo?    -PCSI-I-VOLSPC, 96117 required; 478119 available; 382002 netTP    Portion Done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%,    The following product has been installed:    DEC AXPVMS DWMOTIF V1.2-3  )         The installation is now complete..  B       Process AXPVMS_INST_LP logged out at 20-DEC-1995 12:14:27.54  H         ****************************************************************  E         You can install or upgrade the OpenVMS Alpha operating systemhH         or you can install or upgrade layered products that are included5         on the OpenVMS Alpha operating system CD-ROM.   C         You can also execute DCL commands and procedures to perform ?         "standalone" tasks, such as backing up the system disk.S  +         Please choose one of the following:   6     3-30 Installing the OpenVMS Alpha Operating System           I                                               Installing Layered Productso      A                 1)  Install or upgrade OpenVMS Alpha Version V6.2uM                 2)  List layered product kits that this procedure can install 9                 3)  Install or upgrade layered product(s) 7                 4)  Execute DCL commands and proceduresy)                 5)  Shut down this systemd  F               If you do not want to perform any other operations priorF               to booting the new system disk, enter 5 to shut down theE               system. The system display is similar to the following:   A               Enter CHOICE or "?" to repeat menu: (1/2/3/4/5/?) 5u  *                   Shutting down the system  '                SYSTEM SHUTDOWN COMPLETEe  C               After you complete the installation and shut down the I               system, go to the next section to boot the new system disk.f                                                      I                        Installing the OpenVMS Alpha Operating System 3-31p i  t           Booting the New System Disk     E     _________________________________________________________________a       Booting the New System Diskn         INTRODUCTIONE           After you have successfully installed the operating system, A           boot the new system disk, as described in the followinge           sections.A    )     PREPARING TO BOOT THE NEW SYSTEM DISKn>           Before you boot the new system disk, you must do the           following:  B           1. Halt the system by entering Ctrl/P or by pressing the              Halt button.[1]  C           2. At the console prompt (>>>), enter the SET BOOTDEF_DEV -              command in the following format:   )              SET BOOTDEF_DEV target-driver  >              Substitute the device name of the system disk for@              target-drive. The SET BOOTDEF_DEV command tells the@              system which disk to boot from. For example, if the>              system disk has the device name DKA400, enter the8              following command and press the Return key:  '              >>> SET BOOTDEF_DEV DKA400c  >              If the system disk is connected to a hierarchicalA              storage device (HSx), the format for specifying thatiB              drive is different. For example, on a DEC 7000 seriesB              system connected to an HSC, the command is similar to              the following:n  /              >>> SET BOOTDEF_DEV DUA20.14.0.2.0n  ?              For more information about setting and showing then@              default boot device, see the section titled Setting4              and Showing Boot Devices in Appendix A.             ____________________C           [1]         For more information about halting your Alphao  /                       computer, see Appendix A.u  6     3-32 Installing the OpenVMS Alpha Operating System           I                                               Booting the New System Disku      '         HOW TO BOOT THE NEW SYSTEM DISK F               To boot the system disk, enter the following command and#               press the Return key:   !               >>> BOOT -FLAGS 0,0I  I               When the system finishes booting, it displays informationali-               messages that begin as follows:N  :          OpenVMS Alpha (TM) Operating System, Version V6.2  P      $!  Copyright (c) 1995 Digital Equipment Corporation.  All rights reserved.  +          Installing required known files...e            Configuring devices...                .                .                .D                                                    I                        Installing the OpenVMS Alpha Operating System 3-33E t  I           Joining a VMScluster    E     _________________________________________________________________        Joining a VMScluster         INTRODUCTIONA           If during the installation, you previously answered YeseD           to the question about joining a VMScluster, the system nowB           asks a series of questions about your configuration (CI,9           DSSI, SCSI, local area, or mixed-interconnect).d  C           You might need to refer to VMScluster Systems for OpenVMS E           or Guidelines for VMScluster Configurations to answer theseA           questions.       SCSI VMSCLUSTER SYSTEMS @           If you are joining a VMScluster system configured with@           Small Computer Systems Interface (SCSI) devices, refer<           to the OpenVMS Version 6.2 New Features Manual for@           detailed information about SCSI configurations, setup,           and management.        VMSCLUSTER PROMPTSA           Following is a list of VMScluster prompts and suggested ?           responses. Note that, depending on your responses and/A           particular cluster configuration, some prompts will not            be displayed.a    F     Table 3-1 Prompts for VMScluster Configurations                     E     Question__________________________How_to_Respond_________________   .     Will this node be a cluster       Enter Y.     member (Y/N)?t  E                                              (continued on next page)I                  6     3-34 Installing the OpenVMS Alpha Operating System           I                                                      Joining a VMSclustere      I         Table 3-1 (Cont.) Prompts for VMScluster Configurations             I         Question__________________________How_to_Respond_________________   I         What is the node's DECnet node    Enter the DECnet node name (for F         name?                             example, MYNODE). The DECnetF                                           node name may be from one toE                                           six alphanumeric characters F                                           in length and cannot includeF                                           dollar signs or underscores.  H         What is the node's DECnet node    Enter the DECnet node address-;         address?                          for example, 2.2.   H         Will the Ethernet be used for     Enter N for a CI-only or DSSI-E         cluster communications (Y/N)?     only VMScluster. Otherwise,r6                                           answer Y.[1]  E         Enter this cluster's group        Enter a number in the range D         number:                           from 1 to 4095 or 61440 to0                                           65535.  E         Enter this cluster's password:    Enter the cluster password.uH                                           The password must be from 1 toG                                           31 alphanumeric characters ineG                                           length and may include dollaroC                                           signs and underscores.[2]p  ?         Reenter this cluster's password   Reenter the password.a         for verification: I         _________________________________________________________________ F         [1]The Ethernet may not be required for communication within a  J         local area VMScluster system configured with FDDI devices. Within B         DSSI or CI mixed-interconnect configurations, neither     H         the Ethernet nor FDDI may be required for communication. If yourI         configuration fits either scenario, you can answer No (N) to thisr         prompt.v=         [2]If neither the Ethernet nor FDDI is being used for0F         communication in your cluster configuration, you many not need8         to supply the cluster group number and password.  I                                                  (continued on next page)a    I                        Installing the OpenVMS Alpha Operating System 3-35  .  h           Joining a VMScluster      H     Table 3-1 (Cont.) Prompts for VMScluster Configurations               E     Question__________________________How_to_Respond_________________o  ?     Will MYNODE be a disk server      Enter Y if you want locala?     (Y/N)?                            disks to be served to the B                                       cluster (mandatory for localA                                       area and mixed-interconnect*?                                       configurations). Refer tooD                                       VMScluster Systems for OpenVMS?                                       for information on servede4                                       cluster disks.  B     Will MYNODE serve RFxx disks      Enter a response appropriateB     (Y)?                              for your DSSI configuration,D                                       if such disks are available to2                                       your system.  D     Enter a value for MYNODE's        In a CI-only system (connected?     ALLOCLASS parameter:              to a dual-ported disk), a B                                       DSSI-only system, or a local@                                       area or mixed-interconnectE                                       configuration where nodes servehA                                       DSSI or CI disks, enter the B                                       appropriate allocation classB                                       value (1 to 255). Otherwise,>                                       enter 0. For informationC                                       about selecting the ALLOCLASSd?                                       parameter, see VMScluster :                                       Systems for OpenVMS.  E                                              (continued on next page)                           6     3-36 Installing the OpenVMS Alpha Operating System ?  o      I                                                      Joining a VMScluster       J         Table 3-1 (Cont.) Prompts for VMScluster Configurations             I         Question__________________________How_to_Respond_________________B  B         Does this cluster contain a       For CI-only, SCSI, localF         quorum disk (Y/N)?                area, and mixed-interconnectA                                           configurations, Enter YdA                                           or N, depending on your_8                                           configuration.  F                                           For most DSSI systems, enterI                                           Y. However, if you are adding ahG                                           two-system DSSI configuration D                                           to an existing cluster (inI                                           which case you might not need aaI                                           quorum disk), you can answer N.l  D                                           If you enter Y, the systemI                                           asks for the name of the quorum H                                           disk. Enter the device name of:                                           the quorum disk.  E                                           Refer to VMScluster SystemsrH                                           for OpenVMS for information on7                                           quorum disks.pI         _________________________________________________________________            WHAT TO DO NEXT F               After you respond to the VMScluster prompts, continue to.               the next section to run AUTOGEN.                                I                        Installing the OpenVMS Alpha Operating System 3-376 f  d           Running AUTOGEN     E     _________________________________________________________________S       Running AUTOGENB         HOW AUTOGEN WORKSX@           The system next runs AUTOGEN to evaluate your hardware@           configuration and estimate typical work loads. AUTOGENC           then sets system parameters, the sizes of page, swap, andoE           dump files, and the contents of VMSIMAGES.DAT. When AUTOGENr@           finishes and you reboot, the installation procedure is           complete.A         AUTOGEN MESSAGESE           The installation procedure displays messages similar to thef           following:  P        AUTOGEN will now be run to compute the new SYSGEN parameters.  The systemN        will then shut down and reboot, and the installation or upgrade will be        complete.  M        After rebooting you can continue with such system management tasks as:   6                     Decompressing the System Libraries&                     Configuring DECnetO                     Using SYS$MANAGER:CLUSTER_CONFIG.COM to create a VMSclusterrO                     Creating FIELD, SYSTEST and SYSTEST_CLIG accounts if needed   - %AUTOGEN-I-BEGIN, GETDATA phase is beginning.eL %AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:PARAMS.DAT has been created.(         You may wish to purge this file.9 %AUTOGEN-I-END, GETDATA phase has successfully completed.C/ %AUTOGEN-I-BEGIN, GENPARAMS phase is beginning.wP %AUTOGEN-I-NEWFILE, A new version of SYS$MANAGER:VMSIMAGES.DAT has been created.(         You may wish to purge this file.O %AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:SETPARAMS.DAT has been created.s(         You may wish to purge this file.; %AUTOGEN-I-END, GENPARAMS phase has successfully completed.1. %AUTOGEN-I-BEGIN, GENFILES phase is beginning.? %SYSGEN-I-EXTENDED, DKA200:[SYS0.SYSEXE]PAGEFILE.SYS;1 extendede? %SYSGEN-I-EXTENDED, DKA200:[SYS0.SYSEXE]SWAPFILE.SYS;1 extendeda< %SYSGEN-I-CREATED, SYS$SYSROOT:[SYSEXE]SYSDUMP.DMP;1 created  I %AUTOGEN-I-REPORT, AUTOGEN has produced some informational messages whichfL         have been stored in the file SYS$SYSTEM:AGEN$PARAMS.REPORT.  You may4         wish to review the information in that file.  6     3-38 Installing the OpenVMS Alpha Operating System M  S      I                                                           Running AUTOGEN       : %AUTOGEN-I-END, GENFILES phase has successfully completed./ %AUTOGEN-I-BEGIN, SETPARAMS phase is beginning.e .i .o .                                                                                 I                        Installing the OpenVMS Alpha Operating System 3-39A M  O           Rebooting the System    E     _________________________________________________________________E       Rebooting the System         INTRODUCTIONC           After AUTOGEN finishes, the system shuts down, displayingV,           messages similar to the following:  J           The system is shutting down to allow the system to boot with theB           generated site-specific parameters and installed images.  I           The system will automatically reboot after the shutdown and the (           installation will be complete.  @                   SHUTDOWN -- Perform an Orderly System Shutdown  G           %SHUTDOWN-I-BOOTCHECK, performing reboot consistency check... G           %SHUTDOWN-I-CHECKOK, basic reboot consistency check completedM           .s           .[           .   !     REBOOTING THE SYSTEM MANUALLYEA           If the system does not reboot automatically, reboot thep           system manually.  B           For example, if the system disk is on an RZ25 disk driveB           with a unit number of 1, enter the following command and           press the Return key:              >>> BOOT DKA1   A           After the system reboots, the system displays a message2#           similar to the following:c  @                OpenVMS Alpha (TM) Operating System, Version V6.2  P          Copyright (c) 1995 Digital Equipment Corporation.  All rights reserved.H           %STDRV-I-STARTUP, VMS startup begun at 15-JUL-1995 16:24:02.27           .D           .O           .       6     3-40 Installing the OpenVMS Alpha Operating System S  S      I                                          Logging in to the SYSTEM Account*    I         _________________________________________________________________O  (         Logging in to the SYSTEM Account             INTRODUCTIONA               The system next displays informational messages andeG               accounting information indicating that your OpenVMS Alphar7               operating system is running. For example:   P       %SET-I-INTSET, login interactive limit = 64, current interactive value = 0?         SYSTEM       job terminated at  29-MAR-1995 12:55:43.92         Accounting information:N      Buffered I/O count:            1733         Peak working set size:   3184N      Direct I/O count:               650         Peak page file size:    19440N      Page faults:                    974         Mounted volumes:            0P      Charged CPU time:           0 00:00:04.45   Elapsed time:     0 00:00:34.82  H               At this time, you can log in to the SYSTEM account (so youF               can perform postinstallation tasks), as described in the!               following sections.   /         LOGGING IN TO A CHARACTER CELL TERMINAL F               Log in to a character cell terminal by entering the userB               name SYSTEM followed by the password. The display is'               similar to the following:   P                     Welcome to OpenVMS Alpha (TM) Operating System, Version V6.2                 Username: SYSTEM               Password:f               .                .                . P                     Welcome to OpenVMS Alpha (TM) Operating System, Version V6.2  F               (If you forget your password, follow the instructions in:               Appendix A to perform an emergency startup.)              I                        Installing the OpenVMS Alpha Operating System 3-41e h  p      $     Logging in to the SYSTEM Account           LOGGING IN TO A WORKSTATIONeA           If you installed the DECwindows Motif for OpenVMS AlphaSB           software on your workstation, do the following after the/           login window displays on your screen:t  A           1. Enter the user name SYSTEM followed by the password.]  $           2. Click on the OK button.       WHAT TO DO NEXTTA           After you have successfully installed the OpenVMS Alpha C           operating system and logged in to the SYSTEM account, youiD           must perform certain postinstallation tasks before you canD           use the system. For complete information, go to Chapter 4.                                                              6     3-42 Installing the OpenVMS Alpha Operating System d  e                    I                                                                         4sI         _________________________________________________________________r  I                       After Installing the OpenVMS Alpha Operating SystemD                                                                            I                   After Installing the OpenVMS Alpha Operating System 4-1A 1  .           Overview    E     _________________________________________________________________b       Overview  >           After you have installed the OpenVMS Alpha operatingE           system, you must perform several important tasks to prepare B           the system for operation. These tasks, described in this@           chapter in the order in which you perform them, are as           follows:  !           o  Registering licenses              o  Creating accounts  '           o  Backing up the system diskB  #           o  Customizing the system   >           o  Configuring and starting DECnet for OpenVMS Alpha              softwarek  )           o  Testing the system with UETP   /           o  Decompressing the system librariesd  &           o  Adding and removing files  C           o  Preparing your OpenVMS Alpha system and your PC to runy'              OpenVMS Management Station(  >           o  Installing layered products, including DECwindows  2           o  Backing up the customized system disk  +           o  Configuring a multihead system              o  Running AUTOGEN  1           o  Using the postinstallation checklist               ;     4-2 After Installing the OpenVMS Alpha Operating Systemt I         I                                                 Registering Your Licenses_    I         _________________________________________________________________   !         Registering Your Licensesr             INTRODUCTIOND               The installation procedure gave you the opportunity toD               register any software product licenses. If you did notD               register your OpenVMS Alpha licenses at that time, youG               must do so before you can use the OpenVMS Alpha operatingiE               system. You must also register the licenses for OpenVMSiD               Alpha layered products such as the DECnet for Open VMS               Alpha software.h  H               You can invoke the OpenVMS License utility by entering the                following command:  &               $ @SYS$UPDATE:VMSLICENSE  >               (You can also use the LICENSE REGISTER command.)           FOR MORE INFORMATIONA               For information about registering licenses, see the                following:  E               o  The section titled Registering Licenses in Chapter 3i                 o  Appendix C   >               o  The OpenVMS License Management Utility Manual                                I                   After Installing the OpenVMS Alpha Operating System 4-3_                Creating Accounts     E     _________________________________________________________________        Creating Accounts          INTRODUCTIONB           During the installation, DEFAULT and SYSTEM accounts areA           created for you automatically. However, if plan to haveaD           Digital service representatives test your system or if youD           plan to run testing software such as UETP, you must createD           accounts for each representative and a SYSTEST (standaloneD           system) or SYSTEST_CLIG (VMScluster system) account to run           UETP.m         FOR MORE INFORMATION>           For complete information about creating accounts forC           Digital service representatives and UETP, see the OpenVMSt.           System Manager's Manual: Essentials.                                                      ;     4-4 After Installing the OpenVMS Alpha Operating Systemt           I                                               Backing Up Your System Disk     I         _________________________________________________________________n  #         Backing Up Your System Diskl             INTRODUCTIONG               After you install the operating system, protect your work I               by making a backup copy of the system disk in case you haver0               any problems while customizing it.    &         HOW TO BACK UP THE SYSTEM DISK;               To back up the system disk, do the following:s  @               1. Shut down the system (described in Appendix A).  F               2. Boot the operating system CD-ROM (locally or from the                  InfoServer).a  A               3. Use the menu system to enter the DCL environment                   (option 4).  I               4. Mount the system disk and the target device on which you +                  will make the backup copy.   D               5. Enter backup commands to back up the system disk to!                  supported media._  2               6. Log out from the DCL environment.  D               7. Shut down the system by selecting option 5 from the                  menu.  +               8. Boot from the system disk.c  '         WHEN TO BACK UP THE SYSTEM DISK F               In addition to backing up the system disk now before youE               customize it, you should back up your system disk again F               after you successfully complete your customization tasks+               and install layered products.f           FOR MORE INFORMATIONI               For complete information about backup operations, including H               a description of an alternate method that does not requireF               booting from the operating system CD-ROM and that allowsI               you to back up a shadowed disk without disabling the shadowc"               set, see Appendix B.  I                   After Installing the OpenVMS Alpha Operating System 4-5  i  M           Customizing the System    E     _________________________________________________________________v       Customizing the System         INTRODUCTIONA           You can customize the system to meet your site-specificr?           needs. In addition, if your Alpha computer is part of @           a VMScluster environment, you must prepare the cluster0           environment and configure the cluster.         FOR MORE INFORMATION@           For instructions on customizing the system, review the"           following documentation:  A           o  If the computer is part of a VMScluster environment, @              refer to VMScluster Systems for OpenVMS for further1              information on setting up a cluster.   =           o  The release notes, release notes addendum, and A ?              Comparison of System Management on OpenVMS AXP andaB              OpenVMS VAX, for notes and restrictions that might be2              relevant to your customization plans.  B           o  The OpenVMS System Manager's Manual, for instructions@              on customizing and using your system. You will find3              information about the following tasks:   8              o  Editing the template files SYCONFIG.COM,B                 SYLOGICALS.COM, SYLOGIN.COM, and SYSTARTUP_VMS.COM  ?              o  Starting the queue manager and creating a queueF                 database  (              o  Setting up user accounts  +              o  Adjusting system parameters   =              o  Setting up your system to run DECdtm services   ?           o  The section in this chapter titled Configuring and 8              Starting DECnet for OpenVMS Alpha Software.  @           Note: You can customize your DECwindows environment asB           well, but you must first install the separate DECwindowsB           Motif for OpenVMS Alpha layered product (see the section.           titled Installing Layered Products).  ;     4-6 After Installing the OpenVMS Alpha Operating System  o  t      I                Configuring and Starting DECnet for OpenVMS Alpha Software     I         _________________________________________________________________   B         Configuring and Starting DECnet for OpenVMS Alpha Software  G               If you plan to run DECnet for OpenVMS Alpha software, youf$               must do the following:  I               1. After you have registered the license for the DECnet for H                  OpenVMS Alpha software, execute the interactive commandE                  procedure SYS$MANAGER:NETCONFIG.COM to automatically I                  configure your system for networking. See the DECnet for F                  OpenVMS Guide to Networking for instructions on using                  NETCONFIG.COM.a  C               2. After you start the queue manager (see the OpenVMSY?                  System Manager's Manual), edit the commands intE                  SYS$COMMON:[SYSMGR]SYSTARTUP_VMS.COM that pertain to C                  networking so that the DECnet for OpenVMS softwarehH                  starts automatically when your system is booted. ChooseG                  one of the following commands to start the network and D                  remove the comment delimiter (!) from that command:  K $! IF F$SEARCH("SYS$SYSTEM:NETACP.EXE") .NES. "" THEN @SYS$MANAGER:STARTNET > $! IF F$SEARCH("SYS$SYSTEM:NETACP.EXE") .NES. "" THEN SUBMIT -    SYS$MANAGER:STARTNET.COMu  E                  Both of the previous commands perform the same task. A                  However, the first command executes STARTNET.COMrE                  and delays further processing until the procedure is_F                  completed; the second submits STARTNET.COM to a batchA                  queue and continues executing SYSTARTUP_VMS.COM.u  A               3. If you plan to run both DECnet for OpenVMS Alphai<                  and DECwindows software, you must also editF                  SYS$COMMON:[SYSMGR]SYSTARTUP_VMS.COM to add a commentD                  delimiter (!) immediately following the dollar sign.                  ($) in the following command:  1                  $ DEFINE DECW$IGNORE_DECNET TRUEn  E                  If you are not going to start the DECnet for OpenVMSnH                  Alpha software or have not yet started it, this commandI                  tells the DECwindows software not to wait for the DECnetr,                  for OpenVMS Alpha software.      I                   After Installing the OpenVMS Alpha Operating System 4-7                  Testing the System with UETP    E     _________________________________________________________________E        Testing the System with UETP         INTRODUCTIONA           The User Environment Test Package (UETP), is a software <           package designed to test whether the OpenVMS AlphaA           operating system is installed correctly. As part of the E           postinstallation procedure, Digital recommends that you run *           UETP to verify the installation.         FOR MORE INFORMATIOND           For complete information about using UETP, see the OpenVMS"           System Manager's Manual.                                                            ;     4-8 After Installing the OpenVMS Alpha Operating System  h         I                                        Decompressing the System LibrariesA    I         _________________________________________________________________S  *         Decompressing the System Libraries             INTRODUCTIONH               Decompressing the system libraries gives the system fasterH               access to them. The decompressed libraries require severalH               thousand additional blocks of disk space for all librariesH               to be decompressed. You use the LIBDECOMP.COM procedure to'               decompress the libraries.              DETERMINING DISK SPACEA               To find out how much disk space you have, enter theE9               following command and press the Return key:o  )               $ SHOW DEVICE SYS$SYSDEVICEs  G               If you have approximately 30,000 free blocks on the disk, H               you can decompress the libraries. Note that you can chooseH               to decompress only the libraries that are used frequently.  &         METHODS OF USING LIBDECOMP.COMC               You can use the LIBDECOMP.COM procedure to decompressN&               libraries in three ways:  F               o  Entering a command and responding to prompts from the                  procedure  0               o  Entering an interactive command  )               o  Entering a batch command   @               The following three sections describe each method.  G               Note: Before you use the LIBDECOMP.COM procedure, be surec6               you are logged in to the SYSTEM account.                I                   After Installing the OpenVMS Alpha Operating System 4-9k           &     Decompressing the System Libraries      '     RESPONDING TO LIBDECOMP.COM PROMPTS >           If you want to decompress libraries by responding toE           prompts from the LIBDECOMP.COM procedure, do the following:   B           1. Enter the following command and then press the Return              key:   (              $ @SYS$UPDATE:LIBDECOMP.COM  ?              The resulting display is similar to the following:   6                      VMS Library Decompression Utility                Options:2  P               1  HELPLIB.HLB          12  EDTHELP.HLB        22  EVE$KEYHELP.HLBL               2  STARLET.OLB          13  NCPHELP.HLB        23  UAFHELP.HLBH               3  ACLEDT.HLB           14  SDA.HLB            24  LIB.MLBL               4  ANLRMSHLP.HLB        15  SHWCLHELP.HLB      25  STARLET.MLBN               5  DBG$HELP.HLB         16  SYSGEN.HLB         26  STARLETSD.TLBP               6  DISKQUOTA.HLB        17  ANALAUDIT$HELP     27  DECC$RTLDEF.TLBN               7  EDFHLP.HLB           18  SYSMANHELP.HLB     28  VAXCCURSE.OLBL               8  INSTALHLP.HLB        19  TFF$TFUHELP.HLB    29  VAXCRTL.OLBM               9  LATCP$HELP.HLB       20  TPUHELP.HLB        30  VAXCRTLD.OLBnM              10  MAILHELP.HLB         21  EVE$HELP.HLB       31  VAXCRTLT.OLB.              11  MNRHELP.HLB  6              or   A   ALL libraries to be decompressed)                   E   EXIT this procedurea  H              * Enter letter or number(s) of libraries to be decompressed8                (Separate multiple entries with a comma):  ?           2. Enter the appropriate letter or the numbers of theaA              libraries you want to decompress. (To decompress all @              libraries, the process takes approximately one-half              hour.)a  %     USING LIBDECOMP.COM INTERACTIVELY C           You can execute LIBDECOMP.COM interactively to decompress A           up to eight libraries at a time by listing the names of C           the libraries you want to decompress as parameters on the            command line.     <     4-10 After Installing the OpenVMS Alpha Operating System           I                                        Decompressing the System Librariest      F               Be sure to separate the library names with commas and doI               not include the file extensions. For example, to decompressoD               VAXCRTL.OLB, DISKQUOTA.HLB, and LIB.MLB interactively,*               enter the following command:  =               $ @SYS$UPDATE:LIBDECOMP VAXCRTL, DISKQUOTA, LIBa                                                                              I                  After Installing the OpenVMS Alpha Operating System 4-11M l         &     Decompressing the System Libraries            USING LIBDECOMP.COM IN BATCH=           You can also execute LIBDECOMP.COM in batch mode toCC           decompress up to eight libraries at a time by listing theiE           names of the libraries you want to decompress as parameters =           on a command line that includes the SUBMIT command.   B           Be sure to separate the library names with commas and doE           not include the file extensions. For example, to decompresslA           VAXCRTL.OLB, DISKQUOTA.HLB, and LIB.MLB as a batch job,t&           enter the following command:  ?           $ SUBMIT/NOTIFY/PARAMETERS=(VAXCRTL, DISKQUOTA, LIB)- !           _$ SYS$UPDATE:LIBDECOMP   C           Note: When you enter the command for a batch job, be sure-C           you enclose the list of library names within parentheses.                                                           <     4-12 After Installing the OpenVMS Alpha Operating System _  _      I                                                 Adding and Removing FilesV    I         _________________________________________________________________   !         Adding and Removing Files              INTRODUCTIONB               If you decide after the installation to change whichE               OpenVMS Alpha operating system files you want installed A               on your system, you can use the POLYCENTER SoftwarepC               Installation utility on your running system to add ors               remove files.   C               Note that you can obtain information about individual F               system files by entering HELP SYSTEM_FILES at the dollar               sign prompt ($).  #         HOW TO ADD AND REMOVE FILES B               To add or remove operating system files, use the DCLC               command PRODUCT RECONFIGURE VMS. Note that if you addSE               files, you will need the OpenVMS Alpha operating systemU               CD-ROM.c           FOR MORE INFORMATIONF               For more information about using the POLYCENTER SoftwareB               Installation utility to add or remove files, see the.               OpenVMS System Manager's Manual.                                        I                  After Installing the OpenVMS Alpha Operating System 4-13g m  i      /     Preparing to Use OpenVMS Management Station     E     _________________________________________________________________t  /     Preparing to Use OpenVMS Management Station          INTRODUCTIONB           If you installed the OpenVMS Management Station softwareC           on your system (either by accepting all default values or E           by selecting the component manually during the installation D           procedure), you must perform several tasks on your OpenVMS=           Alpha system and your PC before you can use OpenVMS @           Management Station. These tasks include the following:  !           o  Editing system fileso  ?           o  Starting OpenVMS Management Station on other nodesu  C           o  Verifying that you have the proper memory, disk space, @              media, and the required software to install and run2              OpenVMS Management Station on your PC  ?           o  Creating installation media for PC client software   6           o  Installing the client software on your PC  "           o  Defining DECnet nodes       FOR MORE INFORMATION?           For complete information about preparing your OpenVMSeB           system and your PC to run the OpenVMS Management Station5           server and client software, see Appendix D.        REMOVING FILES=           Note that after you complete the tasks described inuD           Appendix D, which include transferring the client softwareA           files from your system to two floppy diskettes, you cang?           then remove those files from your system to save disk_A           space. (Use the PRODUCT RECONFIGURE command rather thanN           a delete operation.)              <     4-14 After Installing the OpenVMS Alpha Operating System H  v      I                                               Installing Layered Productso    I         _________________________________________________________________   #         Installing Layered Productsi             PROCEDUREaC               You can use the menu system included on the operatingoD               system CD-ROM to install certain layered products withF               the POLYCENTER Software Installation utility. If you didF               not install those layered products previously during theG               installation procedure, you can do so using the following                procedure.  F               Note: To use this procedure, the target system must haveC               the exact same version of the OpenVMS Alpha operating_B               system as the CD-ROM. If you need to install layeredI               products on a target system that has a different version of I               the operating system, use the alternate procedure describedy"               in the next section.  @               1. Shut down the system (described in Appendix A).  F               2. Boot the operating system CD-ROM (locally or from the                  InfoServer).i  D               3. Choose option 2 from the menu to view which layeredH                  products can be installed using the POLYCENTER Software&                  Installation utility.  E               4. Choose option 3 from the menu to install the layered                   products.  D               5. Shut down the system by selecting option 5 from the                  menu.  +               6. Boot from the system disk.c  D               If the layered product that you want to install is notG               listed in the display, see the documentation you received E               with that layered product for installation information.             I                  After Installing the OpenVMS Alpha Operating System 4-15H Y  M           Installing Layered Productsc           ALTERNATE PROCEDUREoE           Following is another method for installing layered products 9           from the OpenVMS Alpha operating system CD-ROM:c  @           1. From your running OpenVMS system (the target systemD              disk), mount the OpenVMS Alpha operating system CD-ROM.  <           2. Locate the directories and files containing theA              available layered products by entering the following B              command (where, in the example, DKA400: is the device!              name of the CD-ROM):d  7              $ DIRECTORY /NOHEAD/NOTRAIL DKA400:[*.KIT]   ?           3. To install layered products that require VMSINSTALe@              (indicated in the directories by saveset file names=              with file types of .A, .B, and so on), enter the ?              @SYS$UPDATE:VMSINSTAL command and then specify the 6              CD-ROM device and directory. For example:  "            $ @SYS$UPDATE:VMSINSTALP            * Where will the distribution volumes be mounted: DKB400:[UCX032.KIT]  D           4. To install layered products that require the POLYCENTER<              Software Installation utility (indicated in theB              directories by file names with file types of .PCSI or@              .PCSI$DESCRIPTION), use the PRODUCT INSTALL command>              or the Motif interface to the POLYCENTER SoftwareC              Installation utility to specify the CD-ROM device nameeB              and directory. Following is an example of the PRODUCT              INSTALL command:   B              $ PRODUCT INSTALL POSIX /SOURCE=DKB400:[POSIX020.KIT]       DECWINDOWS SUPPORTC           The DECwindows components provided with the OpenVMS Alphae=           Version 6.2 operating system supply only DECwindowssA           base support and workstation support files. To get fullf@           DECwindows support, you must also install the separateC           DECwindows Motif for OpenVMS Alpha layered product, whichP7           supports both the Motif and XUI environments.d        <     4-16 After Installing the OpenVMS Alpha Operating System p  e      I                                               Installing Layered Productst      &         MONITORING PERFORMANCE HISTORYH               The OpenVMS Alpha Version 6.2 operating system CD-ROM alsoI               includes a Monitoring Performance History (MPH) kit located E               in the [MPH] directory. See the OpenVMS AXP Version 6.1fE               Release Notes for more information about installing and +               using this optional software.i           ADDITIONAL NOTES!               Note the following:t  D               o  For additional information about installing layeredC                  products, see the OpenVMS System Manager's Manual._  F               o  Be sure you back up the system disk after you install+                  all your layered products.l                                                            I                  After Installing the OpenVMS Alpha Operating System 4-17            )     Backing Up the Customized System DiskD    E     _________________________________________________________________e  )     Backing Up the Customized System DiskG         INTRODUCTION?           After you have customized the OpenVMS Alpha operatingn@           system to your satisfaction and installed your layeredD           products, protect your work by making a backup copy of the           system disk.    -     HOW TO BACK UP THE CUSTOMIZED SYSTEM DISK 7           To back up the system disk, do the following:   <           1. Shut down the system (described in Appendix A).  B           2. Boot the operating system CD-ROM (locally or from the              InfoServer).t  =           3. Use the menu system to enter the DCL environment               (option 4).  E           4. Mount the system disk and the target device on which youi'              will make the backup copy.E  D           5. Enter backup commands to back up the system disk to the              target device..  .           6. Log out from the DCL environment.  @           7. Shut down the system by selecting option 5 from the              menu.  '           8. Boot from the system disk.c       FOR MORE INFORMATIONE           For complete information about backup operations, including D           a description of an alternate method that does not requireC           booting from the operating system CD-ROM, see Appendix B.             <     4-18 After Installing the OpenVMS Alpha Operating System    d      I                                            Configuring a Multihead SystemT    I         _________________________________________________________________o  &         Configuring a Multihead System             DEFINITIONH               A multihead configuration consists of a single workstationG               (such as a DEC 3000 Alpha Model 500 system) that supports F               multiple graphics options. A graphics option consists ofD               a graphics controller and a graphics display interface               (monitor).             INTRODUCTIONG               Your system can be automatically configured for multihead D               use if you rename the private server setup file from aB               template file type to a command procedure file type.F               The DECwindows Motif for OpenVMS Alpha server loads thisG               command procedure on startup or restart. This file alwayshF               configures the console as the primary head, or screen 0.H               The firmware always selects the lowest device found in theF               system (that is, the device with the lowest TURBOchannel2               slot address) as the console device.            HOW TO SET UP THE SYSTEMA               To set up your system for multihead support, do the                following:  H               1. After installing the DECwindows Motif for OpenVMS Alpha@                  software on your system, log in to your system.  E               2. Rename the private server setup file by entering the_#                  following command:s  H                  $ RENAME SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE?                  _To: SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COMc  H               3. Restart the DECwindows server by entering the following                  command:i  4                  $ @SYS$STARTUP:DECW$STARTUP RESTART          I                  After Installing the OpenVMS Alpha Operating System 4-19            "     Configuring a Multihead System           FOR MORE INFORMATION=           See the most recent version of the DECwindows Motifs@           for OpenVMS Installation Guide and Managing DECwindows>           Motif for OpenVMS Systems for more information about;           customizing your DECwindows environment using theo9           SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM file.e                                                                              <     4-20 After Installing the OpenVMS Alpha Operating System r  N      I                                                           Running AUTOGENn    I         _________________________________________________________________            Running AUTOGENm             INTRODUCTIONA               When you installed the operating system, the systemoE               executed the AUTOGEN.COM procedure to set the values ofED               system parameters and the sizes of the page, swap, andD               dump files according to the system configuration. As aI               postinstallation procedure, you need to run the AUTOGEN.COMy:               procedure again to properly tune the system.             WHEN TO RUN AUTOGENm%               Run AUTOGEN as follows:   E               1. After 24 hours of operation, run AUTOGEN in feedback ,                  mode and reboot the system.  G               2. Run AUTOGEN again in feedback mode two workdays later,C,                  and then reboot the system.  G               3. Digital recommends that you run AUTOGEN from SAVPARAMSUD                  through TESTFILES on a weekly basis thereafter, andE                  examine AGEN$PARAMS.REPORT to determine the need forT$                  additional changes.           MODIFYING PARAMETERSB               Based on your examination of AGEN$PARAMS.REPORT, youE               might need to modify parameter values in MODPARAMS.DAT. (               If so, note the following:  D               o  Hardcoded values in MODPARAMS.DAT should not hinderD                  AUTOGEN's ability to calculate feedback parameters.?                  AUTOGEN generally does not reduce the value of I                  parameters that allocate resources; it considers current H                  parameter values to be minimum values, which means thatG                  you do not have to add MIN_* symbols to MODPARAMS.DAT..  D               o  AUTOGEN does increase parameter values according toD                  its calculations unless you have specified explicit?                  or maximum values (by adding MAX_* symbols) ind                  MODPARAMS.DAT.l    I                  After Installing the OpenVMS Alpha Operating System 4-21m s              Running AUTOGENs           FOR MORE INFORMATIONE           For more information about the MODPARAMS.DAT file and aboutnD           using AUTOGEN in general, see the OpenVMS System Manager's           Manual.                                                                                   <     4-22 After Installing the OpenVMS Alpha Operating System    t      I                                                Postinstallation Checklistr    I         _________________________________________________________________   "         Postinstallation Checklist  F               Use the following checklist to make sure you perform all3               the necessary postinstallation tasks:   H               [] Register your licenses, if you did not do so during the(                  installation procedure.  !               [] Create accounts.n  >               [] Back up the system disk as a safeguard before(                  customizing the system.  &               [] Customize the system.  A               [] Configure and start the DECnet for OpenVMS Alpha1                  software.  F               [] Run the User Environment Test Package (UETP), to test                  the system.  E               [] Decompress the system libraries using LIBDECOMP.COM.a  &               [] Add and remove files.  E               [] Prepare your OpenVMS Alpha system and your PC to runmG                  OpenVMS Management Station by following the proceduresr)                  described in Appendix D.   *               [] Install layered products.  I               [] Back up the system disk after you have customized it anda,                  installed layered products.  A               [] Configure your multihead system (if applicable).I  I               [] After the system has been running for at least 24 hours,eG                  run AUTOGEN to collect feedback information and modifyr7                  the MODPARAMS.DAT file (if necessary).           I                  After Installing the OpenVMS Alpha Operating System 4-23  t                       I                                                                         5 I         _________________________________________________________________   I                       Before Upgrading the OpenVMS Alpha Operating Systemf                                                                            I                   Before Upgrading the OpenVMS Alpha Operating System 5-1m o  a           Overview    E     _________________________________________________________________d       Overview  E           This chapter describes which tasks you should perform prioraB           to beginning an upgrade. Tasks described in this chapter           include:  0           o  Reviewing cautions and restrictions  C           o  Preparing to upgrade in a volume shadowing environmenti  /           o  Backing up the current system diskO  6           o  Preparing the system disk for the upgrade  %           o  Shutting down the systems  +           o  Using the preupgrade checklistO       FOR MORE INFORMATIONC           In addition to reviewing the information in this chapter, =           you might need to refer to the following sources of            information as well:  2           o  The OpenVMS Version 6.2 Release Notes  C           o  OpenVMS System Manager's Manual, for information about @              using AUTOGEN, modifying the system parameters file4              (MODPARAMS.DAT), and related operations  B           o  OpenVMS System Management Utilities Reference Manual,D              for information about using system management utilities6              such as SYSMAN and ANALYZE/DISK_STRUCTURE  D           o  OpenVMS Guide to System Security, for information about?              reestablishing your security environment after thet              upgrade                ;     5-2 Before Upgrading the OpenVMS Alpha Operating SystemM           I                                                 Cautions and Restrictionsi    I         _________________________________________________________________o  !         Cautions and Restrictionso             INTRODUCTIONB               This section provides important information that canF               affect the success of your upgrade. Review the cautions,D               restrictions, and notes carefully before you begin the               upgrade.    )         REQUIRED OPERATING SYSTEM VERSION F               To upgrade to Version 6.2 of the OpenVMS Alpha operating?               system, you must be running at least Version 6.1.t  E               If you are upgrading in a cluster environment, also seeeF               Chapter 6 for information about required versions of the>               OpenVMS Alpha and OpenVMS VAX operating systems.           FILES AND DIRECTORIESt=               Note the following about files and directories:   D               o  If you choose not to install optional OpenVMS AlphaC                  software during the upgrade, the upgrade procedureNE                  removes existing files for those components from then                  system disk.y  G               o  If you have changed directory structure on your systemgE                  disk, the upgrade procedure will not work correctly._A                  Restore your system disk to a standard directory 9                  structure before you attempt an upgrade.s  @               o  The OpenVMS Alpha Version 6.2 upgrade procedureD                  provides new files and directories in the directoryH                  [VMS$COMMON...]. If you had any special protections andI                  access control lists (ACLs) before the upgrade, you needoH                  to reapply them to reestablish the security environmentF                  you had previously set up. For more information aboutG                  creating and maintaining a secure environment, see they6                  OpenVMS AXP Guide to System Security.          I                   Before Upgrading the OpenVMS Alpha Operating System 5-3     r           Cautions and Restrictionsd      !     LICENSES AND LAYERED PRODUCTS            Note the following:u  A           o  The upgrade procedure is designed so that you should >              not have to reinstall most layered products after>              the upgrade. However, you might need to reinstallA              certain layered products because of product-specificd%              installation procedures.   D           o  The upgrade procedure leaves your OpenVMS Alpha licenseD              and layered product licenses intact. You do not need to8              reinstall these licenses after you upgrade.                                                                  ;     5-4 Before Upgrading the OpenVMS Alpha Operating Systema t  n      I                    Preparing to Upgrade in a Volume Shadowing Environmenti    I         _________________________________________________________________   >         Preparing to Upgrade in a Volume Shadowing Environment             INTRODUCTIONB               Because you cannot upgrade the operating system on aG               shadowed system disk (the upgrade will fail), you need totI               disable shadowing on that disk and perform other operations :               before you can upgrade the operating system.  I               There are several methods for creating a nonshadowed target D               disk. This chapter describes how to change one of yourH               existing shadowed system disks in a multimember shadow setH               to a nonshadowed disk that you can use as your target disk               for the upgrade.  H               If you have a larger configuration with disks that you canI               physically access, you may want to use a copy of the systemeD               disk as your target disk. Volume Shadowing for OpenVMSC               describes two methods you can use to create this copy F               (using volume shadowing commands or BACKUP commands) and.               how to disable volume shadowing.  *         CREATING A NONSHADOWED TARGET DISKD               Change one of your existing shadowed system disks to a*               nonshadowed disk as follows:  F               1. Shut down all systems booted from the shadowed system                  disk.  A               2. Perform a conversational boot (see Appendix A ifdG                  necessary) on the system disk you have chosen for your *                  target disk. For example:  (                  >>> BOOT -FL 0,1 DKA100  G               3. At the SYSBOOT> prompt, enter the following command to 6                  disable volume shadowing on the disk:  /                  SYSBOOT> SET SHADOW_SYS_DISK 0   I               4. Enter the CONTINUE command to resume the boot procedure.                   For example:C  "                  SYSBOOT> CONTINUE  @               5. After the boot completes, log in to the system.  I                   Before Upgrading the OpenVMS Alpha Operating System 5-5A a  y      :     Preparing to Upgrade in a Volume Shadowing Environment           CHANGING THE LABELB           If you want to change the label on the upgrade disk, use?           the DCL command SET VOLUME/LABEL=volume-label device-P@           spec[:] to perform this optional task. (The SET VOLUMED           /LABEL command requires write access [W] to the index fileB           on the volume. If you are not the volume owner, you must<           have either a system UIC or the SYSPRV privilege.)  D           For VMScluster systems, be sure that the volume label is a)           unique name across the cluster.a  @           Note: If you need to change the volume label of a diskD           that is mounted across the cluster, be sure you change theD           label on all nodes in the VMScluster system. The followingD           example shows how you can use the SYSMAN utility to defineE           the environment as a cluster and propagate the volume label .           change to all nodes in that cluster:  )           SYSMAN> SET ENVIRONMENT/CLUSTERMA           SYSMAN> DO SET VOLUME/LABEL=new-label disk-device-name:s       SETTING THE BOOT DEVICE_B           Be sure your system is set to boot from the upgrade diskB           by default. Use the SHOW BOOTDEF_DEV and SET BOOTDEF_DEVC           console commands to accomplish this task. (See Appendix A             for more information.)       WHAT TO DO NEXTdC           After you have created a nonshadowed system disk that youeD           can use for the upgrade, perform the additional preupgrade>           procedures described in the balance of this chapter.                            ;     5-6 Before Upgrading the OpenVMS Alpha Operating System  r  n      I                                                Backing Up the System DiskU    I         _________________________________________________________________   "         Backing Up the System Disk             INTRODUCTIONE               Digital strongly recommends that you make a backup copycF               of the system disk and, if your configuration allows it,G               upgrade the backup copy. (If there are problems, you willu0               still have a working system disk.)    &         HOW TO BACK UP THE SYSTEM DISK;               To back up the system disk, do the following:   @               1. Shut down the system (described in Appendix A).  F               2. Boot the operating system CD-ROM (locally or from the                  InfoServer).D  A               3. Use the menu system to enter the DCL environmentn                  (option 4.)  I               4. Mount the system disk and the target device on which youd+                  will make the backup copy._  H               5. Enter backup commands to back up the system disk to the                  target device.   2               6. Log out from the DCL environment.  D               7. Shut down the system by selecting option 5 from the                  menu.  +               8. Boot from the system disk.c           FOR MORE INFORMATIONI               For complete information about backup operations, includingmH               a description of an alternate method that does not requireG               booting from the operating system CD-ROM, see Appendix B.r            I                   Before Upgrading the OpenVMS Alpha Operating System 5-7  e  p           Preparing the System Diskf    E     _________________________________________________________________a       Preparing the System Diskh         INTRODUCTIONC           The following sections describe how to prepare the system E           disk for the upgrade. The operations include the following:y  &           o  Examining the system disk  1           o  Checking the size of the system disko  (           o  Verifying system parameters       EXAMINING THE SYSTEM DISKsA           Examine and repair (if necessary) the system disk using E           the ANALYZE/DISK_STRUCTURE command. (See the OpenVMS System D           Management Utilities Reference Manual for more information;           about this command.) Use the following procedure:n  C           1. Analyze the system disk for inconsistencies and errorsME              in the file structure by entering the following command:   3              $ ANALYZE/DISK_STRUCTURE SYS$SYSDEVICE   *              Ignore the following message:  ;              %ANALDISK-I-OPENQUOTA, error opening QUOTA.SYS   D           2. If you find any other errors on the system disk, repair:              the errors by entering the following command:  :              $ ANALYZE/DISK_STRUCTURE/REPAIR SYS$SYSDEVICE  (     CHECKING THE SIZE OF THE SYSTEM DISKA           It is difficult to determine in advance how many blocksG@           of disk space you will need for the upgrade because it?           depends on how many files you have on the target disk B           already and on how many components you select during theD           upgrade procedure. However, the following information will           help:   >           o  The maximum amount of disk space you will need is@              approximately 360,000 blocks, but your system might$              use substantially less.  ;     5-8 Before Upgrading the OpenVMS Alpha Operating System_           I                                                 Preparing the System Diskd      C               o  After you select the components you want installedpE                  on the system for the upgrade, the upgrade procedure ?                  calculates whether you have enough disk space,tI                  displaying the number of available blocks and the number F                  required for the upgrade. If the procedure determinesE                  that your disk does not have enough space to performuH                  the upgrade, it displays a message alerting you to thatH                  fact and allows you to terminate the upgrade so you canB                  create more disk space and try the upgrade again.  F               To see how much space you have on the system disk, enter$               the following command:  )               $ SHOW DEVICE SYS$SYSDEVICEL  #         VERIFYING SYSTEM PARAMETERS A               Verify (and modify if necessary) system parameters,TI               described as follows. (If necessary, see the OpenVMS System C               Manager's Manual for more information about modifying A               system parameters.). Any system parameters that you D               modified and did not enter in SYS$SYSTEM:MODPARAMS.DATF               are lost during the upgrade. To retain these parameters,I               enter their names in SYS$SYSTEM:MODPARAMS.DAT and the valuedE               that AUTOGEN needs to add to the default minimum value. I               (When AUTOGEN runs after the upgrade, it uses the values ini(               SYS$SYSTEM:MODPARAMS.DAT.)  @               For example, if you modified GBLPAGES by 128 pages:               above the default, add the following line to'               SYS$SYSTEM:MODPARAMS.DAT:                  ADD_GBLPAGES=128           WHAT TO DO NEXTuD               Continue the preupgrade tasks as follows, depending onE               whether you are upgrading in a standalone or VMSclustery               environment:                I                   Before Upgrading the OpenVMS Alpha Operating System 5-9e D  A           Preparing the System Diskn    E           ___________________________________________________________ E           IF ...                THEN ...                                1           you are upgrading a   do the following: @           standalone system,    1. Log in to the SYSTEM account.  B                                 2. Enter the following command and=                                    then press the Return key:o  6                                 $ @SYS$SYSTEM:SHUTDOWN  @                                 3. When the procedure asks if anD                                    automatic system reboot should beD                                    performed, enter N (No) and press2                                    the Return key.  A                                 4. Go to the checklist at the end A                                    of this chapter to verify thateC                                    you have performed the necessaryhA                                    tasks; then go to Chapter 7 toi?                                    begin the upgrade procedure..  1           you are upgrading a   do the following:uE           VMScluster system,    1. Review the checklist at the end of   0                                    this chapter.  3                                 2. Go to Chapter 6.oE           ___________________________________________________________D                                  <     5-10 Before Upgrading the OpenVMS Alpha Operating System y  h      I                                                      Preupgrade Checklist     I         _________________________________________________________________t           Preupgrade Checklist  I               Use the following checklist to make sure you have performedr9               all the tasks before beginning the upgrade:   @               [] Review all cover letters and the release notes.  /               [] Review all cautions and notes.   F               [] If your system disk is part of a shadow set, create a4                  nonshadowed system disk to upgrade.  F               [] Set up your system to record the upgrade procedure onH                  either a hardcopy terminal or a printer attached to theD                  console terminal. If you do not do this, the screenB                  messages will be lost. You will need a transcriptC                  in case there is a problem during the upgrade. For_D                  information on how to record the procedure, see theE                  hardware manuals that came with your Alpha computer.s  7               [] Make a backup copy of the system disk.   H               [] Examine and repair (if necessary) the system disk using4                  the ANALYZE/DISK_STRUCTURE command.  3               [] Check the size of the system disk.a  *               [] Verify system parameters.  @               [] Shut down the system (if you are upgrading in a)                  standalone environment).   @               [] If you are upgrading a VMScluster system, go toI                  Chapter 6. If you are not upgrading a VMScluster system,n@                  go to Chapter 7 to begin the upgrade procedure.                  I                  Before Upgrading the OpenVMS Alpha Operating System 5-11u g  T                    I                                                                         6sI         _________________________________________________________________   I                          Preparing to Upgrade in a VMScluster Environment                                                                             I                      Preparing to Upgrade in a VMScluster Environment 6-1c t  n           Overview    E     _________________________________________________________________S       Overview  ?           This chapter describes how to prepare to upgrade in a B           VMScluster environment, depending on the type of upgradeC           you perform and whether you need to add any new computerss           to the cluster.R  ?           Note: Be sure you have performed the preupgrade tasks C           described in Chapter 5 before you upgrade your VMSclustere           system.        TYPES OF UPGRADESoA           There are two types of cluster upgrades: concurrent and A           rolling. The type of upgrade you use depends on whether E           you want to maintain the availability of the cluster duringuE           the upgrade and whether you have more than one system disk.iD           Review this chapter and then perform the preliminary tasksE           for the upgrade procedure (concurrent or rolling) that bestn#           suits your configuration.   &     ADDING A NEW SYSTEM TO THE CLUSTER@           If you need to add a new computer supported by OpenVMSD           Alpha Version 6.2 to an existing VMScluster configuration,?           Digital supports two options, listed in the following            preferred order:  E           1. Upgrade the entire cluster to Version 6.2 of the OpenVMS A              Alpha operating system and add the new computer as ag              member.  D           2. If you need to keep some systems in the cluster running?              the current version of the OpenVMS Alpha operatingsB              system, you must upgrade a system disk in the clusterC              to OpenVMS Alpha Version 6.2 using the rolling upgradee>              procedure and then boot the new computer into the5              cluster using that upgraded system disk.                 8     6-2 Preparing to Upgrade in a VMScluster Environment           I                                                                  Overviewy               FOR MORE INFORMATIONC               When you upgrade the operating system in a VMSclustereG               environment, be sure the following sources of informationt.               are available for you to review:  H               o  The cover letters and the software product descriptions4                  included with your distribution kit  6               o  The OpenVMS Version 6.2 Release Notes  /               o  VMScluster Systems for OpenVMS   9               o  Guidelines for VMScluster Configurations   F               o  OpenVMS Version 6.2 New Features Manual (for detailedI                  information about SCSI VMScluster configurations, setup,o                   and management)                                                        I                      Preparing to Upgrade in a VMScluster Environment 6-3     i           Concurrent Upgrade    E     _________________________________________________________________        Concurrent Upgrade         INTRODUCTION/           This section describes the following:P  +           o  How a concurrent upgrade workso  #           o  Notes and restrictions_  C           o  Tasks you need to perform to prepare your system for aU               concurrent upgrade.  "     HOW A CONCURRENT UPGRADE WORKSD           During a concurrent upgrade, you must shut down the entireB           cluster and upgrade each system disk. No one can use the?           cluster until you upgrade each system disk and rebooteC           each Alpha computer. When the cluster reboots, each Alpha >           computer will be running the upgraded version of the)           OpenVMS Alpha operating system.t       NOTES AND RESTRICTIONSE           Before performing a concurrent upgrade, note the following:   C           o  For OpenVMS Alpha Version 6.2 concurrent upgrades, allrB              nodes in the cluster must be running at least OpenVMS              Alpha Version 6.1.   ?           o  If all Alpha systems in the VMScluster environmento@              are booted from one system disk, you must perform a               concurrent upgrade.  &     PREPARING FOR A CONCURRENT UPGRADE@           To prepare for a concurrent upgrade, use the following           procedure:  2           1. Log in locally to the SYSTEM account.  D           2. Shut down all systems by entering the following commandD              on each system (satellites first, then the boot nodes):  #              $ @SYS$SYSTEM:SHUTDOWN.    8     6-4 Preparing to Upgrade in a VMScluster Environment           I                                                        Concurrent Upgrade       F               3. When the procedure asks if an automatic system rebootG                  should be performed, enter N (No) and press the Return                   key.   4               4. Choose the CLUSTER_SHUTDOWN option.  F               5. When the shutdown procedure is finished on all nodes,G                  halt each system by entering Ctrl/P or by pressing theU                   Halt button.[1]  I               6. If you have only one system disk for your cluster, go to :                  Chapter 7 to begin the upgrade procedure.  G                  If you have more than one system disk, select the disksH                  on which you already performed the preupgrade tasks andE                  then go to Chapter 7 to begin the upgrade procedure.   F                  After the upgrade is complete, you will be instructedF                  to reboot each computer in the VMScluster environment?                  before beginning other postupgrade procedures.e                                          "               ____________________G               [1]         For more information about halting your Alphae  3                           computer, see Appendix A.e  I                      Preparing to Upgrade in a VMScluster Environment 6-5o    y           Rolling Upgradee    E     _________________________________________________________________        Rolling Upgradea         INTRODUCTION/           This section describes the following:m  (           o  How a rolling upgrade works  #           o  Notes and restrictionss  C           o  Tasks you need to perform to prepare your system for ae              rolling upgrade.        HOW A ROLLING UPGRADE WORKS @           During a rolling upgrade, you upgrade each system disk<           individually, allowing old and new versions of the?           operating system to run together in the same cluster,hD           creating a mixed-version cluster. Because rolling upgradesD           allow mixed-version clusters, the systems that you are notC           upgrading remain available. During a rolling upgrade, youdE           keep some of the computers in the cluster running while youtC           upgrade others (you must have more than one system disk).c       NOTES AND RESTRICTIONSB           Before performing a rolling upgrade, note the following:  ;           o  During a rolling upgrade you must ensure that:   B              -  The upgraded system does not attempt to access anyA                 disk that is being accessed by one or more of thep-                 remaining VMScluster systems.   B              -  The remaining VMScluster systems do not attempt toD                 access the target disk of the system being upgraded.  E                 If the target disk being upgraded is locally attached @                 to the system performing the upgrade, then it isC                 not accessible to the remaining VMScluster systems. D                 (The OpenVMS system booted from the operating systemA                 CD-ROM does not MSCP serve local disks.) WheneverO=                 possible, Digital recommends that you perform A                 the upgrade on a local disk or that you perform a #                 concurrent upgrade.   8     6-6 Preparing to Upgrade in a VMScluster Environment           I                                                           Rolling Upgrades      H                     During the upgrade, be sure that the target disk youG                     select, as well as any disk you access from the DCLtF                     menu option, is either a local disk or one that isI                     not being accessed by any of the remaining VMScluster                      members.  E               o  Digital supports rolling upgrades on Alpha computersf?                  that belong to a mixed-architecture VMScluster D                  containing VAX computers running Versions 6.2, 6.1,C                  6.0, or 5.5-2 of the OpenVMS VAX operating system.   I               o  Digital recommends that all Alpha computers in a cluster_H                  run the same (and preferably the latest) version of the0                  OpenVMS Alpha operating system.  I               o  You cannot perform a rolling upgrade if all systems boot H                  from a single system disk. Perform a concurrent upgrade                  instead.k  D               o  The upgrade procedure affects the queuing system as                  follows:Y  G                  -  The queueing system is not active on the system younD                     are upgrading; do not attempt to execute a START,                     /QUEUE/ MANAGER command.  G                  -  You cannot create a queue database on the operatingi?                     system CD-ROM (because it is not writable).i  C                  -  The queue manager process on other nodes in theeI                     cluster can continue to run during the upgrade if the E                     queue database is not on the disk being upgraded.K  '         PREPARING FOR A ROLLING UPGRADE B               To prepare for a rolling upgrade follow these steps:  G               1. Log in to any node where the disk is mounted as a data$F                  disk, rather than as the system disk. (That disk mustI                  be the one on which you already performed the preupgradey/                  tasks described in Chapter 5.)o  E               2. Check the votes and make adjustments to maintain the E                  proper quorum so the cluster can continue to operatecH                  throughout the upgrade. (VMScluster Systems for OpenVMS5                  describes this procedure in detail.)a  I                      Preparing to Upgrade in a VMScluster Environment 6-7k b  y           Rolling Upgrade       A           3. Use the DCL command DISMOUNT/CLUSTER to dismount theOB              data disk. (You can also perform this operation using!              the SYSMAN utility.)s  C              Note that you can ignore messages from nodes where thetB              specified data disk is being used as the system disk.  :           4. Verify that the data disk has been dismounted=              successfully by entering the following commands:a                $ MCR SYSMAN ,              SYSMAN> SET ENVIRONMENT/CLUSTER-              SYSMAN> DO SHOW DEVICE disk-nameo  C              Examine the display to be sure the disk is not mountedgA              on any nodes as a data disk. Noting the value listedf<              in the Trans Count field can help you make thatB              determination: A value of less than 50 indicates thatB              the disk is mounted as a data disk rather than as the@              system disk; a much larger value (for example, 300)D              indicates that the disk most likely is the system disk.  @           5. If the disk is still mounted on any nodes as a data?              disk, use the SYSMAN utility to dismount the disk; 4              otherwise exit from the SYSMAN utility.  C           6. Shut down all nodes that boot from the system disk youtB              are upgrading, including the node from which you willE              perform the upgrade. Enter the following command on eachp              node:  #              $ @SYS$SYSTEM:SHUTDOWNO  B           7. When the procedure asks if an automatic system rebootC              should be performed, enter N (No) and press the Returnt              key.   +           8. Choose the REMOVE_NODE option.A  B           9. If proper quorum is not maintained at any time duringD              the upgrade procedure, the shutdown procedure will hangA              the cluster. If the cluster hangs during a shutdown,SD              enter the following commands on the system console of a3              system that is still a cluster member:e  8     6-8 Preparing to Upgrade in a VMScluster Environment    n      I                                                           Rolling UpgradeO                        $ <Ctrl/P>                   >>> D SIRR C                   >>> C                  IPC> Q_                  IPC> <Ctrl/Z>  G               10.After the shutdown procedure is finished on all nodes, @                  go to Chapter 7 to begin the upgrade procedure.                                                                          I                      Preparing to Upgrade in a VMScluster Environment 6-9t    s                    I                                                                         7 I         _________________________________________________________________   I                              Upgrading the OpenVMS Alpha Operating System                                                                             I                          Upgrading the OpenVMS Alpha Operating System 7-1                 Overview    E     _________________________________________________________________        Overview         INTRODUCTION5           This chapter describes the following tasks:C  C           o  Beginning the upgrade from the operating system CD-ROMe%              or from a running system   '           o  Specifying the target disks  (           o  Specifying the volume label  +           o  Choosing descriptive help text   #           o  Completing the upgrade   @           o  Performing postupgrade tasks (including booting the              upgraded system)   (           o  Installing layered products                                              4     7-2 Upgrading the OpenVMS Alpha Operating System           I                            Upgrading from CD-ROM or from a Running System_    I         _________________________________________________________________s  6         Upgrading from CD-ROM or from a Running System             INTRODUCTIONE               The OpenVMS Alpha Version 6.2 operating system includes G               procedures that allow you to easily upgrade the operatingdH               system using the POLYCENTER Software Installation utility.G               In console mode, you can boot the operating system CD-ROM I               to begin the upgrade procedure. On a system that is already I               running the OpenVMS Alpha Version 6.2 operating system, you G               can invoke the upgrade procedure by entering a command atm               the DCL level.             HOW TO BEGINF               Depending on whether you are upgrading the OpenVMS AlphaG               operating system from the operating system CD-ROM or from C               a running OpenVMS Alpha Version 6.2 system, begin the #               procedure as follows:s  L               ______________________________________________________________O               If upgrading from ...      Then ...                              C  M               the operating              go to the section titled Booting the @               system CD-ROM,             Operating System CD-ROM  L               a running Version          go to the section titled PerformingN               6.2 system,                the Upgrade                          L               ______________________________________________________________                              I                          Upgrading the OpenVMS Alpha Operating System 7-35 u  g      '     Booting the Operating System CD-ROM     E     __________________________________________________________________  '     Booting the Operating System CD-ROM_         INTRODUCTIONA           To get started, boot the OpenVMS Alpha operating system B           CD-ROM either from your local CD-ROM drive or from a CD-D           ROM drive connected to the InfoServer, as described in the           following sections.v          BOOTING FROM THE LOCAL DRIVE  E           1. Insert the operating system CD-ROM into the local CD-ROM               drive.s  ?           2. At the console prompt (>>>), enter the SHOW DEVICE E              command so you can identify the name of the CD-ROM drive #              (for example, DKA400:)   <           3. Enter the boot command in the following format:  )              BOOT -FLAGS 0,0 source-drive   ?              Substitute the device name of the CD-ROM drive (as A              listed in the SHOW DEVICE display) for source-drive.r  E              For example, if the SHOW DEVICE display lists the deviceeE              name of your CD-ROM drive as DKA400, enter the followingf.              command and press the Return key:  '              >>> BOOT -FLAGS 0,0 DKA400i       BOOTING FROM THE INFOSERVER C           To boot the operating system CD-ROM using the InfoServer,r           follow these steps:b  @           1. At the console prompt, enter the following command:  <              >>> BOOT -FLAGS 0,0 -FI APB_062 lan-device-name  ,              Note the following conventions:  D              o  APB_062 is the file name of the APB program used for;                 the initial system load (ISL) boot program.:  4     7-4 Upgrading the OpenVMS Alpha Operating System o  h      I                                       Booting the Operating System CD-ROM       A                  o  lan-device-name is the name of the local areaeG                     network (LAN) device Ethernet) identified with yourpH                     computer. For information about the LAN devices yourF                     system supports, refer to the following table. ForI                     additional information, see the hardware manuals that I                     you received with your Alpha computer and the OpenVMSr1                     Software Product Description.   I                  ________________________________________________________e>                                             Ethernet      FDDII                  Alpha_Computer_____________Device________Device_________   >                  AlphaServer 1000 series    ERA0, EWA0    FRA0  >                  AlphaServer 2000 series    ERA0, EWA0    FRA0  >                  AlphaServer 2100 series    ERA0, EWA0    FRA0  >                  AlphaServer 8200 series    EXA0, EWA0    FXA0  >                  AlphaServer 8400 series    EXA0, EWA0    FXA0  ;                  AlphaStation 200 series    EWA0          -   ;                  AlphaStation 400 series    EWA0          -   ;                  DEC 2000 series            ERA0          -n  B                  DEC 3000 series            ESA0          "n/ESA0"  ;                  DEC 4000 series            EZA0          -P  >                  DEC 7000 series            EXA0          FXA0  I                  DEC 10000 series           EXA0          FXA0           _I                  ________________________________________________________   B                  Notes: If you are using a DEC 3000 or 4000 series,                  system, note the following:  H                  o  On DEC 3000 series systems, you can boot through theI                     InfoServer with an Ethernet PMAD device or FDDI DEFTAAI                     device by specifying the device name as "n/ESA0". TheiF                     value for n is the TURBOchannel slot number, whichE                     you can obtain by entering the SHOW CONFIGURATION E                     command at the console prompt (>>>) and examining F                     the display. For more information, see the sectionE                     titled Booting Over the Network with an Alternateo8                     TURBOchannel Adapter, in Appendix A.  I                          Upgrading the OpenVMS Alpha Operating System 7-5     n      '     Booting the Operating System CD-ROMe      A              o  On DEC 4000 series, you must specify the ISL filemA                 name in uppercase (APB_062). In addition, if yoursB                 system uses console firmware prior to Version 3.2,2                 enter the BOOT command as follows:  :                 >>> BOOT -FL 0,0 -start 0 -FI APB_062 EZA0  C           2. The InfoServer ISL program then displays the following               menu:  1              Network Initial System Load Function               Version 1.1  (                FUNCTION         FUNCTION                  IDM,                  1     -        Display Menu$                  2     -        Help.                  3     -        Choose Service.                  4     -        Select Options$                  5     -        Stop  '              Enter a function ID value:o  C           3. Respond to the prompts as follows, pressing the Returnk"              key after each entry:  ,              a. Enter 3 for the function ID.  *              b. Enter 2 for the option ID.  2              c. Enter the service name (ALPHA062).  &              A sample display follows:  1              Enter a function ID value: 3<Return>   $               OPTION          OPTION                 ID+                 1     -       Find Services 6                 2     -       Enter known Service Name  0              Enter an Option ID value: 2<Return>9              Enter a Known Service Name: ALPHA062<Return>   B           Note: If you boot the OpenVMS Alpha operating system CD-@           ROM from an InfoServer system but lose your connectionB           during the upgrade procedure (the system is unresponsiveB           and pressing Ctrl/Y does not return you to the menu), do           the following:  4     7-6 Upgrading the OpenVMS Alpha Operating System           I                                       Booting the Operating System CD-ROMo      B               1. Reboot the OpenVMS Alpha operating system CD-ROM.  H               2. Enter the DCL environment by choosing option 2 from the                  menu.  D               3. Mount the device containing your backup copy of theE                  target disk and the device that is your target disk.   H               4. Restore the backup copy of your target disk by enteringE                  the appropriate BACKUP commands. (See Appendix B foreB                  complete information about using MOUNT and BACKUP4                  commands to restore a system disk.)  2               5. Log out from the DCL environment.  I               6. Perform the upgrade again by choosing the upgrade optioncI                  (1) from the menu and following the procedures describedd!                  in this chapter.l                                                      I                          Upgrading the OpenVMS Alpha Operating System 7-7f e  m           Performing the Upgrade    E     _________________________________________________________________c       Performing the Upgrade         UPGRADING FROM THE CD-ROMl@           After you boot the operating system CD-ROM, choose theC           upgrade option (1) from the menu displayed on the screen. 2           The display is similar to the following:  ?                OpenVMS Alpha (TM) Operating System, Version 6.2a  P      $!  Copyright (c) 1995 Digital Equipment Corporation.  All rights reserved.  +          Installing required known files...             Configuring devices...   N               ****************************************************************  K               You can install or upgrade the OpenVMS Alpha operating systemcN               or you can install or upgrade layered products that are included;               on the OpenVMS Alpha operating system CD-ROM.d  I               You can also execute DCL commands and procedures to perform E               "standalone" tasks, such as backing up the system disk.s  1               Please choose one of the following:u  B                   1  Install or upgrade OpenVMS Alpha Version V6.2O                   2)  List layered product kits that this procedure can installp;                   3)  Install or upgrade layered product(s) 9                   4)  Execute DCL commands and proceduresl+                   5)  Shut down this system   <           Enter CHOICE or ? to repeat menu: (1/2/3/4/5/?)) 1  @           After you choose the upgrade option, go to the section@           titled Choosing INITIALIZE or PRESERVE to continue the           procedure.            4     7-8 Upgrading the OpenVMS Alpha Operating System h  c      I                                                    Performing the Upgrade       '         UPGRADING FROM A RUNNING SYSTEMnC               If you are performing an upgrade from an Alpha systemtF               that is already running Version 6.2 of the OpenVMS AlphaD               operating system, enter the following command from the;               SYSTEM account and then press the Return key:l  /               $ @SYS$SYSTEM:AXPVMS$PCSI_INSTALLf  C               After you enter the command, go to the section titled H               Choosing INITIALIZE or PRESERVE to continue the procedure.  '         CHOOSING INITIALIZE OR PRESERVE G               After you choose the upgrade option (if you are upgrading I               from the operating system CD-ROM) or start the AXPVMS$PCSI_ D               INSTALL command procedure (if you are upgrading from aC               running OpenVMS Alpha Version 6.2 system), the systemC=               displays the following information and prompts:   M                   ***********************************************************t  L                   The installation procedure will ask a series of questions.  8                         () - encloses acceptable answers5                         [] - encloses default answersu  G                   Type your response and press the <Return> key.  Type:   4                         ? - to repeat an explanationG                         ^ - to change prior input (not always possible)n  A                   There are two choices for Installation/Upgrade:d  I                INITIALIZE - removes all software and data files that wereeK                   previously on the target disk and installs OpenVMS Alpha.n  P                PRESERVE -- installs or upgrades OpenVMS Alpha on the target diskD                   and retains all other contents of the target disk.       P            * NOTE: You cannot install OpenVMS Alpha on an existing disk on whichI                   OpenVMS VAX or any other operating system is installed.d  C               Do you want to INITIALIZE or to PRESERVE? [PRESERVE])i  H               For an upgrade, press the Return key to accept the default               (PRESERVE).e  I                          Upgrading the OpenVMS Alpha Operating System 7-9s                Performing the Upgrade           SPECIFYING THE TARGET DISKA           Next, the procedure asks you for the name of the targetME           disk. If you enter a question mark (?), the system displaysSB           a list of devices on your system. Select the appropriate6           disk and respond to the prompt. For example:  I               You must enter the device name for the target disk on whicho.               OpenVMS Alpha will be installed.  C           Enter device name for target disk: (? for choices) DKA200d       SPECIFYING THE VOLUME LABELrC           The system then prompts you for the volume label and askspC           if the information is correct. You can accept the defaultt?           label assigned by the system (AXPVMSSYS) or specify asD           different volume label (with a limit of 12 characters thatE           can be letters A-Z, numbers 0-9, dollar signs ($),  hyphens A           (-),  or underscores (_)).  After you select the volume C           label, the target disk is mounted and page and swap files #           are created. For example:o  /               DKA200: is now labeled AXPVMSSYS.   8           Do you want to keep this label? (Yes/No) [Yes]  8               OpenVMS Alpha will be upgraded on DKA200:.  "     CHOOSING DESCRIPTIVE HELP TEXT1           The system next prompts you as follows:C  D         The installation can provide brief or detailed descriptions.P         In either case, you can request the detailed descriptions by typing "?".  A           Do you always want detailed descriptions? (Yes/No) [No]n  ?           If you answer Yes, the system will display additionals,           explanatory text with each prompt.                5     7-10 Upgrading the OpenVMS Alpha Operating Systemr v  n      I                                                    Performing the Upgradel               SELECTING COMPONENTSD               As you begin the upgrade procedure, the system asks ifD               you want all the default values, meaning all the filesG               and subgroups of files for each component included in the H               operating system. The display is similar to the following:  6               The following product has been selected:5               DEC AXPVMS VMS V6.2         [Available]   I               *** DEC AXPVMS VMS V6.2: VMS Operating System, Version V6.2   B                   COPYRIGHT (c) 29-MAR-1995 -- All rights reserved  /                   Digital Equipment Corporation   M                    Do you want all the default values for this product? [YES]   E               During an upgrade, the POLYCENTER Software Installation E               utility defines "default values" as the values that you F               selected when you last installed or upgraded the OpenVMSF               Alpha operating system on your system. Therefore, before<               you respond to the prompt, note the following:  I               o  If you answer YES (by pressing the return key) to acceptoI                  the default values, you will receive the same components F                  that you selected when you last installed or upgradedD                  the system (instead of all the components currentlyH                  available) plus any new components that were not in theH                  previous version of the OpenVMS Alpha operating system.  A               o  If you want to include or exclude any componentsnI                  differently from how you did so in the last installation G                  or upgrade, you must answer NO and then respond to the_E                  prompts for each option, even those that you are not                   changing.  F               o  If you want to review the current defaults first, youG                  can answer NO. Then answer YES when the system asks if -                  you want to view the values.C  E                  If you review the defaults and are satisfied, answercG                  YES to the prompt asking if you are satisfied with thepE                  values. However, if you want to make changes, answerMH                  NO to that question and then answer YES when the system9                  asks if you want to re-enter the values.h  I                         Upgrading the OpenVMS Alpha Operating System 7-11u e  g           Performing the Upgrade      A           Notes: When selecting components, note the following as            well:p  @           o  Whether you choose all the default values or select;              individual files, the system will give you the_A              opportunity to view your selections and make changes               (if necessary).  @           o  If you are not sure whether you want certain files,@              request help by entering a question mark (?) at the6              prompt for that file (or group of files).  D           o  You can select three OpenVMS reference manuals provided>              online with the operating system in ASCII format:A              OpenVMS Master Index, OpenVMS Glossary, and Overview_&              of OpenVMS Documentation.  A           o  If you plan to install the separate DECwindows Motif-@              for OpenVMS Alpha layered product, you must installD              the DECwindows base support and workstation support (toA              run windowing software on Alpha workstations or in a A              VMScluster that includes workstations or Xterminals) >              included with the OpenVMS Alpha operating system.  A           o  OpenVMS Management Station software is automaticallyeB              installed on your OpenVMS system disk when you acceptE              all the default values. If you do not accept the default-C              values, you must select the OpenVMS Management Station)C              component (server and client files) if you plan to useeB              that product. After the installation is complete, you@              can then prepare your OpenVMS Alpha system and yourB              PC to run OpenVMS Management Station by following the0              procedures described in Appendix D.  D           o  If you decide after the upgrade to change which OpenVMSD              Alpha operating system files you want installed on yourE              system, you can use the POLYCENTER Software Installation C              utility on your running system to add or remove files.S  D           o  After you boot the upgraded system disk and log in, youA              can obtain information about individual system fileseD              by entering HELP SYSTEM_FILES at the dollar sign prompt              ($).     5     7-12 Upgrading the OpenVMS Alpha Operating System            I                                                    Performing the Upgradeh               COMPLETING THE UPGRADEE               When you have answered all the prompts and selected the E               components you want installed, the system gives you the H               opportunity to review your selections (and make changes ifH               necessary) and then displays messages about the following:  A               o  The amount of space on the disk required for the F                  upgrade, based on the components you have chosen. (IfD                  your disk does not have enough space to perform theG                  upgrade, the system displays a message alerting you to D                  that fact and allows you to terminate the upgrade.)  B               o  Notification that the upgrade has been completed.  3               o  Information about running AUTOGEN.                  o  The menu.  ,               Following is a sample display.  E               Note: If you are upgrading from a running OpenVMS Alpha E               Version 6.2 system, the system displays the dollar signpI               prompt ($) instead of the 5-option menu when the upgrade is2               complete.   2               Do you want to view the values? [NO]  9               %PCSIUI-I-DONEASK, execution phase startings6               The following product will be installed:!               DEC AXPVMS VMS V6.2 I    %PCSI-I-VOLINFO, estimated space information for volume DISK$AXPVMSSYS <    -PCSI-I-VOLSPC, 40 required; 185469 available; 185429 netP    Portion Done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%7               The following product has been installed:D!               DEC AXPVMS VMS V6.2   .                   The upgrade is now complete.  K                   When the newly upgraded system is first booted, a special_F                   startup procedure will be run.  This procedure will:  >                       o  Run AUTOGEN to set system parameters.I                       o  Reboot the system with the newly set parameters.t  J                   You can shut down now or continue with other operations.  L                 Process AXPVMS_INSTALL logged out at 29-MAR-1995 13:21:07.90  P                 ****************************************************************  I                         Upgrading the OpenVMS Alpha Operating System 7-13                 Performing the Upgrade      K               You can install or upgrade the OpenVMS Alpha operating systemcN               or you can install or upgrade layered products that are included;               on the OpenVMS Alpha operating system CD-ROM.   I               You can also execute DCL commands and procedures to performnE               "standalone" tasks, such as backing up the system disk.   1               Please choose one of the following:   C                   1)  Install or upgrade OpenVMS Alpha Version V6.2 O                   2)  List layered product kits that this procedure can installe;                   3)  Install or upgrade layered product(s)L9                   4)  Execute DCL commands and procedurese+                   5)  Shut down this system        WHAT TO DO NEXT @           If you want to install layered products, including theA           DECwindows Motif for OpenVMS layered product, go to the            next section.   >           If you do not want to to install layered products orD           perform any other operations prior to booting the upgraded!           disk, do the following:   E           1. Shut down the system by choosing the shutdown option (5)               from the menu.m  D           2. Go to the section titled What to Do After the Shutdown.                                  5     7-14 Upgrading the OpenVMS Alpha Operating Systemn .         I                                               Installing Layered Productsa    I         _________________________________________________________________   #         Installing Layered Products              INTRODUCTIONC               You can use the menu system included on the operatingeD               system CD-ROM to install certain layered products withH               the POLYCENTER Software Installation utility. You can viewE               a list of the layered products that can be installed in F               this way by choosing option 2 from the menu. (To installI               layered products that are not listed, see Chapter 4 and thenC               installation documentation for each layered product.)p             HOW TO INSTALLG               To install layered products using the POLYCENTER SoftwarenH               Installation utility, choose option 2 to view the list and)               then option 3. For example:   /             Please choose one of the following:   A                 1)  Install or upgrade OpenVMS Alpha Version V6.2cM                 2)  List layered product kits that this procedure can installc9                 3)  Install or upgrade layered product(s)e7                 4)  Execute DCL commands and procedures )                 5)  Shut down this systemA  9         Enter CHOICE or ? to repeat menu: (1/2/3/4/5/?) 2s  K             The following layered product kits are available on the OpenVMS F             operating system CD-ROM and can be installed at this time:  ;         DEC AXPVMS AMDS V6.1 found in DKB400:[KITS.AMDS061] @         DEC AXPVMS DWMOTIF V1.2-3 found in DKB400:[KITS.DWMOTIF]:         DEC AXPVMS POSIX V2.0 found in DKB400:[KITS.POSIX]B         DEC AXPVMS SOFTWIN V1.0 found in DKB400:[KITS.SOFTWINDOWS]>         DEC AXPVMS SWXCR V2.0 found in DKB400:[KITS.SWXCR$KIT]  L             ****************************************************************  I             You can install or upgrade the OpenVMS Alpha operating systemlL             or you can install or upgrade layered products that are included9             on the OpenVMS Alpha operating system CD-ROM.   G             You can also execute DCL commands and procedures to performSC             "standalone" tasks, such as backing up the system disk.1  /             Please choose one of the following:r  I                         Upgrading the OpenVMS Alpha Operating System 7-15d c  .           Installing Layered Products*      =             1)  Install or upgrade OpenVMS Alpha Version V6.2 I             2)  List layered product kits that this procedure can installu5             3)  Install or upgrade layered product(s)d3             4)  Execute DCL commands and procedurese%             5)  Shut down this systemo  5     Enter CHOICE or ? to repeat menu: (1/2/3/4/5/?) 3   C         ***********************************************************   @         If you choose to install or upgrade to DECwindows Motif,"         please note the following:  E           o If you did not select the OpenVMS DECwindows base supportcI             and workstation files options, DECwindows Motif will not run.t?             You must add these options to use DECwindows Motif.   J           o If you are upgrading to DECwindows Motif from version V1.1 andG             want to save the OSF/Motif Release 1.1.3 programming files,oB             DO NOT upgrade now.  Instead, see the DECwindows MotifG             installation manual and follow the instructions for runningn"             PCSI_INSTALLATION.COM.  C         You must enter the device name for the target disk on whicho1         the layered product(s) will be installed.R  =     Enter device name for target disk: (? for choices) DKA200o  %         DKA200: is labeled AXPVMSSYS.   D         The installation can provide brief or detailed descriptions.P         In either case, you can request the detailed descriptions by typing "?".  ;     Do you always want detailed descriptions? (Yes/No) [No]S          1 - DEC AXPVMS AMDS V6.1e$        2 - DEC AXPVMS DWMOTIF V1.2-3         3 - DEC AXPVMS POSIX V2.0"        4 - DEC AXPVMS SOFTWIN V1.0         5 - DEC AXPVMS SWXCR V2.0$        6 - All products listed above        7 - Exito       Desired Product(s): 2   ,     The following product has been selected:     DEC AXPVMS DWMOTIF V1.2-3P  "     Do you want to continue? [YES]  5     7-16 Upgrading the OpenVMS Alpha Operating System  n         I                                               Installing Layered Productsi      P         *** DEC AXPVMS DWMOTIF V1.2-3: DECwindows Motif V1.2-3 for OpenVMS Alpha  P         Copyright Digital Equipment Corporation 1988, 1995. All rights reserved.  )             Digital Equipment Corporation   /             This product uses the PAK: DW-MOTIF   I             Do you want all the default values for this product? [YES] noa  8             DECwindows Motif runtime support files [YES]  2             Programming Support (C Language) [YES]  -             Fortran programming support [YES]n  ,             PASCAL programming support [YES]  &             Programming examples [YES]  <             Translated Image Support (OSF/Motif V1.1.3) [NO]  3             Do you want to view the values? [NO] nos  3         %PCSIUI-I-DONEASK, execution phase starting 0         The following product will be installed:!         DEC AXPVMS DWMOTIF V1.2-3 I    %PCSI-I-VOLINFO, estimated space information for volume DISK$AXPVMSSYS ?    -PCSI-I-VOLSPC, 96117 required; 478119 available; 382002 netnP    Portion Done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%1         The following product has been installed: !         DEC AXPVMS DWMOTIF V1.2-3e  -             The installation is now complete.E  F           Process AXPVMS_INST_LP logged out at 20-DEC-1995 12:14:27.54  L             ****************************************************************  I             You can install or upgrade the OpenVMS Alpha operating systemeL             or you can install or upgrade layered products that are included9             on the OpenVMS Alpha operating system CD-ROM.r  G             You can also execute DCL commands and procedures to perform C             "standalone" tasks, such as backing up the system disk.   /             Please choose one of the following:   I                         Upgrading the OpenVMS Alpha Operating System 7-17G E  L           Installing Layered Productsr      =             1)  Install or upgrade OpenVMS Alpha Version V6.2nI             2)  List layered product kits that this procedure can instally5             3)  Install or upgrade layered product(s)u3             4)  Execute DCL commands and procedures %             5)  Shut down this systema  E           If you do not want to perform any other operations prior toe6           booting the upgraded disk, do the following:  E           1. Shut down the system by choosing the shutdown option (5)               from the menu.b  C           2. Go to the next section to perform specific tasks after[#              the system shuts down.i                                                              5     7-18 Upgrading the OpenVMS Alpha Operating System            I                                             What to Do After the Shutdown     I         _________________________________________________________________y  %         What to Do After the Shutdowns  F               After the system shuts down, you need to perform certainB               tasks, depending on the configuration of your systemF               and the type of upgrade you are performing. Refer to the"               appropriate section.  D               Note: When you boot your system following the shutdownI               (regardless of the type of upgrade and configuration), note F               that your system will automatically run AUTOGEN and boot               again.           STANDALONE UPGRADEI               If you are upgrading a standalone system, do the following:h  #               1. Reboot the system.w  &               2. Log in to the system.  B               3. Go to Chapter 8 to perform additional postupgrade                  procedures.  %         CONCURRENT VMSCLUSTER UPGRADE H               If you are performing a concurrent upgrade in a VMScluster,               environment, do the following:  I               ___________________________________________________________ K               IF ...                THEN ...                               t  5               you have one system   do the following: G               disk,                 1. Reboot each system that uses the   5                                        upgraded disk.e  7                                     2. Go to Chapter 8.                   I                         Upgrading the OpenVMS Alpha Operating System 7-19            !     What to Do After the Shutdown     E           ___________________________________________________________aE           IF ...                THEN ...                             n  1           you have multiple     do the following:nA           system disks,         1. Repeat the upgrade process foro  C                                    each system disk in the cluster,t@                                    beginning with the preupgrade@                                    tasks described in Chapter 5.  E                                 2. Reboot each system in the cluster.   @                                 3. Log in to an upgraded system.  =                                 4. Go to Chapter 8 to performeE                                    additional postupgrade procedures. E           ___________________________________________________________C       ROLLING VMSCLUSTER UPGRADEA           If you are performing a rolling upgrade in a VMSclusterh(           environment, do the following:  +           1. Log in to the upgraded system.w  >           2. Go to Chapter 8 to perform additional postupgrade@              procedures. (You will reboot the other systems thatA              boot from the upgraded disk after you complete those               tasks.)                                    5     7-20 Upgrading the OpenVMS Alpha Operating Systeme t                       I                                                                         8 I         _________________________________________________________________v  I                        After Upgrading the OpenVMS Alpha Operating System                                                                             I                    After Upgrading the OpenVMS Alpha Operating System 8-1r ?  t           Overview    E     _________________________________________________________________e       Overview  C           After you upgrade the OpenVMS Alpha operating system, youAD           need to perform several important tasks before you can useB           the system. These tasks, described in the order in which+           you perform them, are as follows:   6           o  Re-forming the shadow set (if applicable)  %           o  Registering new licensesw  .           o  Examining the AUTOGEN report file  A           o  Modifying the system parameters file (MODPARAMS.DAT)   .           o  Examining your command procedures  /           o  Decompressing the system librariesp  )           o  Testing the system with UETPM  &           o  Adding and removing files  C           o  Preparing your OpenVMS Alpha system and your PC to run '              OpenVMS Management Stationo  (           o  Installing layered products  2           o  Backing up the customized system disk  6           o  Rebooting cluster members (if applicable)             o  Running AUTOGEN  ,           o  Using the postupgrade checklist                  :     8-2 After Upgrading the OpenVMS Alpha Operating System P  o      I                                                 Re-Forming the Shadow Sete    I         _________________________________________________________________h  !         Re-Forming the Shadow Setg               INTRODUCTION?               If you have upgraded a disk in a volume shadowingtF               environment, you must now re-form the shadow set. Follow6               the procedure described in this section.    %         HOW TO ADD SHADOW SET MEMBERS 0               Re-form the shadow set as follows:  E               1. Enter the SHOW DEVICE D command to display a list ofm=                  disks available on your system. For example:a                     $ SHOW DEVICE D  P Device                  Device           Error    Volume         Free  Trans MntP  Name                   Status           Count     Label        Blocks Count CntP DSA54:                  Mounted             0  SHADOWDISK        918150  100   16 $11$DKB100:    (NODE1)  Online              0  SCRATCHP $11$DKB200:    (NODE1)  ShadowSetMember     0  ALPHA062          918150    1  31  9               2. Enter a command in the following format:h  P   $ MOUNT/CONFIRM/SYSTEM DSAn: /SHADOW=(upgraded-disk:,new-member:) volume-label  0                  Note the following conventions:  E                  o  DSAn: is the virtual unit name of the shadow set.l  E                  o  upgraded-disk: is the name of the shadowed system +                     disk you just upgraded.   G                  o  new-member: is the name of the disk you want to addr2                     as a member of the shadow set.  D                  o  volume-label is the volume label of the shadowed2                     system disk you just upgraded.  G                  Note: When you re-form the shadow set, the contents ofgH                  the new member are replaced by the contents of the diskH                  you upgraded. Specifying the /CONFIRM qualifier remindsI                  you of this fact, confirming that you are specifying the H                  correct name of a disk that either is blank or contains*                  files you no longer need.  I                    After Upgrading the OpenVMS Alpha Operating System 8-3d 8  9           Re-Forming the Shadow Setn           EXAMPLE.A           The following is an example of re-forming a shadow set:o  P         $ MOUNT/CONFIRM/SYSTEM DSA54: /SHADOW=($11$DKB200:,$11$DKB100:) ALPHA062  4           %MOUNT-F-SHDWCOPYREQ, shadow copy required4           Virtual Unit - DSA54 Volume label ALPHA062?                Member                    Volume label Owner UICp?                $11$DKB100:  (NODE1)      SCRATCH      [100,100]tA           Allow FULL shadow copy on the above member(s)? [N]: YES                                                                       :     8-4 After Upgrading the OpenVMS Alpha Operating System S  S      I                                                  Registering New Licenses*    I         _________________________________________________________________n            Registering New Licenses             INTRODUCTIONB               If you need to register new OpenVMS Alpha or layeredG               product licenses, you can do so by entering the followingo               command:  &               $ @SYS$UPDATE:VMSLICENSE  <               You can also use the LICENSE REGISTER command.           FOR MORE INFORMATIONA               For information about registering licenses, see thea               following:  E               o  The section titled Registering Licenses in Chapter 3                  o  Appendix CS  >               o  The OpenVMS License Management Utility Manual                                              I                    After Upgrading the OpenVMS Alpha Operating System 8-5  c         %     Examining the AUTOGEN Report File     E     _________________________________________________________________   %     Examining the AUTOGEN Report Filee         INTRODUCTION9           When AUTOGEN runs, it writes informational and,e4           if necessary, warning messages to the file?           SYS$SYSTEM:AGEN$PARAMS.REPORT. You should examine thep'           contents of this report file.i          INTERPRETING THE REPORT FILE>           To view AGEN$PARAMS.REPORT on your screen, enter the5           following command and press the Return key:i  .           $ TYPE SYS$SYSTEM:AGEN$PARAMS.REPORT  D           (You can also print this file or examine it using the EDIT           /READ_ONLY command.)  E           For more information on AGEN$PARAMS.REPORT, see the OpenVMS "           System Manager's Manual.  D           If the report includes a message similar to the following,A           you might need to modify the size of the page, swap, ors           dump file:  O             %AUTOGEN-W-DSKSPC, The disk on which DKA0:[SYS0.SYSEXE]PAGEFILE.SYS O                 resides would be over 95% full if it were modified to hold 2000                  blocks.   E           For more information about modifying the sizes of the page,t5           swap, and dump files, see the next section.                         :     8-6 After Upgrading the OpenVMS Alpha Operating System n  i      I                                      Modifying the System Parameters Filea    I         _________________________________________________________________u  ,         Modifying the System Parameters File             INTRODUCTIONC               Review the file SYS$SYSTEM:MODPARAMS.DAT. The upgrade C               procedure created a new version of this file. The old G               version is named SYS$SYSTEM:MODPARAMS.DAT_OLD. Modify thelH               parameters in the new file as necessary. The following twoI               sections are examples of instances where you need to modifyw*               parameters in MODPARAMS.DAT.             SYSTEM FILE SIZESsG               AUTOGEN sets the following files at sizes appropriate forp               your system:  $                  [SYSEXE]SYSDUMP.DMP%                  [SYSEXE]PAGEFILE.SYS6%                  [SYSEXE]SWAPFILE.SYS   G               If you have special work loads or configurations, you canXG               specify different sizes for these files by performing theV               following steps:  .               1. Log in to the SYSTEM account.  -               2. Enter the following command:*  :                  $ @SYS$UPDATE:AUTOGEN SAVPARAMS TESTFILES  A               3. If the file sizes displayed need to be adjusted, D                  add symbols to the MODPARAMS.DAT file (described inG                  detail in the OpenVMS System Manager's Manual: Tuning, I                  Monitoring, and Complex Systems) and repeat step 2 until 7                  you are satisfied with the file sizes.k  F               4. When you are satisfied with the file sizes, enter theE                  following command to ensure that the modified system A                  files are installed when the system is rebooted:r  7                  $ @SYS$UPDATE:AUTOGEN GENPARAMS REBOOTl      I                    After Upgrading the OpenVMS Alpha Operating System 8-7u a  l      (     Modifying the System Parameters File           VMSCLUSTER PARAMETERS <           If you are upgrading a VMScluster system, note the           following:  B           o  You must update the MODPARAMS.DAT file for each Alpha6              computer that boots from the system disk.  D           o  Be sure the EXPECTED_VOTES value is correct. That valueD              is the sum of all VOTES in the cluster. For example, ifC              there are five Alpha computers in the cluster and each *              has one VOTE, the value is 5.  <           o  As you reboot each Alpha computer, AUTOGEN runsB              automatically. The cluster forms when you have booted7              enough computers to attain cluster quorum.g                                                            :     8-8 After Upgrading the OpenVMS Alpha Operating System           I                                         Examining Your Command Procedurese    I         _________________________________________________________________e  )         Examining Your Command Procedures)             INTRODUCTIONF               This section describes how the upgrade procedure affects!               command procedures.n             SITE-SPECIFIC FILES I               The upgrade procedure retains the site-specific versions ofcH               the following files located in the [VMS$COMMON] directory:  '               [SYSMGR]LAT$SYSTARTUP.COMP               [SYSMGR]LOGIN.COMP"               [SYSMGR]SYCONFIG.COM$               [SYSMGR]SYLOGICALS.COM!               [SYSMGR]SYLOGIN.COM '               [SYSMGR]SYPAGSWPFILES.COMl$               [SYSMGR]SYSECURITY.COM#               [SYSMGR]SYSHUTDWN.COMy'               [SYSMGR]SYSTARTUP_VMS.COMg'               [SYSMGR]TFF$SYSTARTUP.COM !               [SYSMGR]WELCOME.TXT /               [SYS$STARTUP]ESS$LAST_STARTUP.DATu  F               The upgrade procedure provides new templates for some ofI               these files with the .TEMPLATE extension. The new templates G               might include features that are not in your site-specific I               files. Check the templates against your site-specific filesn/               and edit your files as necessary.n                            I                    After Upgrading the OpenVMS Alpha Operating System 8-9n g  [      &     Decompressing the System Libraries    E     _________________________________________________________________g  &     Decompressing the System Libraries         INTRODUCTIOND           Decompressing the system libraries gives the system fasterD           access to them. The decompressed libraries require severalD           thousand additional blocks of disk space for all librariesD           to be decompressed. You use the LIBDECOMP.COM procedure to#           decompress the libraries.9         DETERMINING DISK SPACE=           To find out how much disk space you have, enter the.5           following command and press the Return key:r  %           $ SHOW DEVICE SYS$SYSDEVICEX  C           If you have approximately 30,000 free blocks on the disk, D           you can decompress the libraries. Note that you can chooseD           to decompress only the libraries that are used frequently.  "     METHODS OF USING LIBDECOMP.COM?           You can use the LIBDECOMP.COM procedure to decompress "           libraries in three ways:  B           o  Entering a command and responding to prompts from the              procedure  ,           o  Entering an interactive command  %           o  Entering a batch commandd  <           The following three sections describe each method.  C           Note: Before you use the LIBDECOMP.COM procedure, be sured2           you are logged in to the SYSTEM account.  '     RESPONDING TO LIBDECOMP.COM PROMPTS >           If you want to decompress libraries by responding toE           prompts from the LIBDECOMP.COM procedure, do the following:n  B           1. Enter the following command and then press the Return              key:C  (              $ @SYS$UPDATE:LIBDECOMP.COM  ;     8-10 After Upgrading the OpenVMS Alpha Operating Systemr n  t      I                                        Decompressing the System Libraries       C                  The resulting display is similar to the following:   :                          VMS Library Decompression Utility                    Options:   O            1  HELPLIB.HLB          12  EDTHELP.HLB          22  EVE$KEYHELP.HLB K            2  STARLET.OLB          13  NCPHELP.HLB          23  UAFHELP.HLB G            3  ACLEDT.HLB           14  SDA.HLB              24  LIB.MLBtK            4  ANLRMSHLP.HLB        15  SHWCLHELP.HLB        25  STARLET.MLB_M            5  DBG$HELP.HLB         16  SYSGEN.HLB           26  STARLETSD.TLBfO            6  DISKQUOTA.HLB        17  ANALAUDIT$HELP       27  DECC$RTLDEF.TLBnM            7  EDFHLP.HLB           18  SYSMANHELP.HLB       28  VAXCCURSE.OLB K            8  INSTALHLP.HLB        19  TFF$TFUHELP.HLB      29  VAXCRTL.OLB L            9  LATCP$HELP.HLB       20  TPUHELP.HLB          30  VAXCRTLD.OLBL           10  MAILHELP.HLB         21  EVE$HELP.HLB         31  VAXCRTLT.OLB           11  MNRHELP.HLBi  :                  or   A   ALL libraries to be decompressed-                       E   EXIT this procedurea  L                  * Enter letter or number(s) of libraries to be decompressed<                    (Separate multiple entries with a comma):  C               2. Enter the appropriate letter or the numbers of the E                  libraries you want to decompress. (Decompressing allf>                  libraries takes approximately one-half hour.)  )         USING LIBDECOMP.COM INTERACTIVELY G               You can execute LIBDECOMP.COM interactively to decompress E               up to eight libraries at a time by listing the names of G               the libraries you want to decompress as parameters on the                command line.b  F               Be sure to separate the library names with commas and doI               not include the file extensions. For example, to decompress D               VAXCRTL.OLB, DISKQUOTA.HLB, and LIB.MLB interactively,*               enter the following command:  =               $ @SYS$UPDATE:LIBDECOMP VAXCRTL, DISKQUOTA, LIB_          I                   After Upgrading the OpenVMS Alpha Operating System 8-11            &     Decompressing the System Libraries            USING LIBDECOMP.COM IN BATCH=           You can also execute LIBDECOMP.COM in batch mode to C           decompress up to eight libraries at a time by listing the E           names of the libraries you want to decompress as parameters =           on a command line that includes the SUBMIT command.   B           Be sure to separate the library names with commas and doD           not include the file extension. For example, to decompressA           VAXCRTL.OLB, DISKQUOTA.HLB, and LIB.MLB as a batch job, &           enter the following command:  ?           $ SUBMIT/NOTIFY/PARAMETERS=(VAXCRTL, DISKQUOTA, LIB)-_!           _$ SYS$UPDATE:LIBDECOMPN  B           Note: When you type the command for a batch job, be sureC           you enclose the list of library names within parentheses.                                                           ;     8-12 After Upgrading the OpenVMS Alpha Operating Systemp e  e      I                                              Testing the System with UETPi    I         _________________________________________________________________   $         Testing the System with UETP             INTRODUCTIONE               Run the User Environment Test Package (UETP), to verify 3               that the upgrade completed correctly._             FOR MORE INFORMATIONF               For instructions on running UETP, see the OpenVMS System               Manager's Manual.                                                                   I                   After Upgrading the OpenVMS Alpha Operating System 8-13                 Adding and Removing Files_    E     _________________________________________________________________        Adding and Removing Filesp         INTRODUCTION>           If you decide after the installation to change whichA           OpenVMS Alpha operating system files you want installed =           on your system, you can use the POLYCENTER Software ?           Installation utility on your running system to add or            remove files.l  ?           Note that you can obtain information about individual B           system files by entering HELP SYSTEM_FILES at the dollar           sign prompt ($).       HOW TO ADD AND REMOVE FILESm>           To add or remove operating system files, use the DCLB           command PRODUCT RECONFIGURE VMS. Note that you will need4           the OpenVMS Alpha operating system CD-ROM.       FOR MORE INFORMATIONB           For more information about using the POLYCENTER Software>           Installation utility to add or remove files, see the*           OpenVMS System Manager's Manual.                                          ;     8-14 After Upgrading the OpenVMS Alpha Operating System- f         I                               Preparing to Use OpenVMS Management Station     I         __________________________________________________________________  3         Preparing to Use OpenVMS Management Station              INTRODUCTIONF               If you installed the OpenVMS Management Station softwareD               on your system (either by accepting all default valuesG               or by selecting the component manually during the upgradenH               procedure), you must perform several tasks on your OpenVMSA               Alpha system and your PC before you can use OpenVMSOD               Management Station. These tasks include the following:  %               o  Editing system files   C               o  Starting OpenVMS Management Station on other nodes   G               o  Verifying that you have the proper memory, disk space, D                  media, and the required software to install and run6                  OpenVMS Management Station on your PC  C               o  Creating installation media for PC client software   :               o  Installing the client software on your PC  &               o  Defining DECnet nodes           FOR MORE INFORMATIONC               For complete information about preparing your OpenVMSuF               system and your PC to run the OpenVMS Management Station9               server and client software, see Appendix D.t           REMOVING FILESA               Note that after you complete the tasks described in H               Appendix D, which include transferring the client softwareE               files from your system to two floppy diskettes, you cansC               then remove those files from your system to save disk E               space. (Use the PRODUCT RECONFIGURE command rather than "               a delete operation.)              I                   After Upgrading the OpenVMS Alpha Operating System 8-15t s              Installing Layered Products.    E     _________________________________________________________________c       Installing Layered Productsn         INTRODUCTION=           Except in certain instances, you should not have to @           reinstall layered products that you had on your system?           prior to the upgrade. However, if you need to install E           layered products, following the directions in this section.w      
     PROCEDUREr?           You can use the menu system included on the operating @           system CD-ROM to install certain layered products with>           the POLYCENTER Software Installation utility. If youB           did not install those layered products previously duringB           the upgrade procedure, you can do so using the following           procedure.  B           Note: To use this procedure, the target system must have?           the exact same version of the OpenVMS Alpha operating >           system as the CD-ROM. If you need to install layeredE           products on a target system that has a different version ofNE           the operating system, use the alternate procedure described_           in the next section.  <           1. Shut down the system (described in Appendix A).  B           2. Boot the operating system CD-ROM (locally or from the              InfoServer).o  @           3. Choose option 2 from the menu to view which layeredD              products can be installed using the POLYCENTER Software"              Installation utility.  A           4. Choose option 3 from the menu to install the layeredi              products.  @           5. Shut down the system by selecting option 5 from the              menu.  '           6. Boot from the system disk.   @           If the layered product that you want to install is notC           listed in the display, see the documentation you receivediA           with that layered product for installation information.n  ;     8-16 After Upgrading the OpenVMS Alpha Operating System_ _  _      I                                               Installing Layered Products                ALTERNATE PROCEDUREGI               Following is another method for installing layered productss=               from the OpenVMS Alpha operating system CD-ROM:s  D               1. From your running OpenVMS system (the target systemH                  disk), mount the OpenVMS Alpha operating system CD-ROM.  @               2. Locate the directories and files containing theE                  available layered products by entering the followinguF                  command (where, in the example, DKA400: is the device%                  name of the CD-ROM):f  ;                  $ DIRECTORY /NOHEAD/NOTRAIL DKA400:[*.KIT]t  C               3. To install layered products that require VMSINSTALlD                  (indicated in the directories by saveset file namesA                  with file types of .A, .B, and so on), enter theDC                  @SYS$UPDATE:VMSINSTAL command and then specify the :                  CD-ROM device and directory. For example:  "            $ @SYS$UPDATE:VMSINSTALP            * Where will the distribution volumes be mounted: DKB400:[UCX032.KIT]  H               4. To install layered products that require the POLYCENTER@                  Software Installation utility (indicated in theF                  directories by file names with file types of .PCSI orD                  .PCSI$DESCRIPTION), use the PRODUCT INSTALL commandB                  or the Motif interface to the POLYCENTER SoftwareG                  Installation utility to specify the CD-ROM device nameDF                  and directory. Following is an example of the PRODUCT!                  INSTALL command:o  F                  $ PRODUCT INSTALL POSIX /SOURCE=DKB400:[POSIX020.KIT]           DECWINDOWS SUPPORTG               The DECwindows components provided with the OpenVMS AlphawF               Version 6.2 operating system supply only DECwindows baseB               support and workstation support files. If you do notD               already have the separate DECwindows Motif for OpenVMSF               Alpha layered product installed on your system, you mustB               install that product to get full DECwindows support.        I                   After Upgrading the OpenVMS Alpha Operating System 8-17i                Installing Layered Products       "     MONITORING PERFORMANCE HISTORYD           The OpenVMS Alpha Version 6.2 operating system CD-ROM alsoE           includes a Monitoring Performance History (MPH) kit locatedSA           in the [MPH] directory. See the OpenVMS AXP Version 6.1dA           Release Notes for more information about installing ande'           using this optional software.V       ADDITIONAL NOTES           Note the following:M  @           o  For additional information about installing layered?              products, see the OpenVMS System Manager's Manual..  B           o  Be sure you back up the system disk after you install'              all your layered products.o                                                            ;     8-18 After Upgrading the OpenVMS Alpha Operating SystemG G  A      I                                     Backing Up the Customized System Diskg    I         _________________________________________________________________   -         Backing Up the Customized System Diska             INTRODUCTIONF               After you have upgraded and customized the OpenVMS AlphaI               operating system to your satisfaction and installed layeredtH               products, protect your work by making a backup copy of the               system disk.    1         HOW TO BACK UP THE CUSTOMIZED SYSTEM DISK F               To back up the system disk, use the following procedure.  @               1. Shut down the system (described in Appendix A).  F               2. Boot the operating system CD-ROM (locally or from the                  InfoServer).   A               3. Use the menu system to enter the DCL environment                   (option 4).  I               4. Mount the system disk and the target device on which you +                  will make the backup copy.   H               5. Enter backup commands to back up the system disk to the                  target device._  2               6. Log out from the DCL environment.  D               7. Shut down the system by selecting option 5 from the                  menu.  +               8. Boot from the system disk.            FOR MORE INFORMATIONI               For complete information about backup operations, including H               a description of an alternate method that does not requireF               booting from the operating system CD-ROM and that allowsI               you to back up a shadowed disk without disabling the shadow "               set, see Appendix B.        I                   After Upgrading the OpenVMS Alpha Operating System 8-19     S           Rebooting Cluster MembersS    E     _________________________________________________________________        Rebooting Cluster Members          INTRODUCTIONA           If you are performing a rolling upgrade in a VMSclustersB           environment and have completed all the postupgrade tasksD           required for your upgraded system disk, reboot each system+           that boots from that system disk.          FOR MORE INFORMATION=           For more information about booting your system, seey           Appendix A.n                                                              ;     8-20 After Upgrading the OpenVMS Alpha Operating System  o  e      I                                                           Running AUTOGEN_    I         _________________________________________________________________C           Running AUTOGENn             INTRODUCTIONC               Although AUTOGEN runs automatically at the end of theaH               upgrade procedure, Digital recommends that you run AUTOGENE               periodically after you perform an upgrade. This sectionOD               describes how often you should run AUTOGEN and what it               does.     !         RUNNING AFTER THE UPGRADE G               After 24 hours of operation, run AUTOGEN in FEEDBACK mode F               and reboot the system. Run AUTOGEN in this way again two               workdays later.h           RUNNING WEEKLYH               AUTOGEN sets the values of system parameters and the sizesB               of the page and swap files according to the system'sE               work load. Digital recommends that you run AUTOGEN fromoG               SAVPARAMS through TESTFILES on a weekly basis and examine E               AGEN$PARAMS.REPORT to determine the need for additional                changes.  A               Hardcoded values in MODPARAMS.DAT should not hinder I               AUTOGEN's ability to calculate feedback parameters. AUTOGEN D               generally does not reduce the value of parameters thatG               allocate resources; it considers current parameter valuesMF               to be minimum values, which means you do not have to addC               MIN_* symbols to MODPARAMS.DAT. AUTOGEN does increase G               parameter values according to its calculations unless you H               have specified explicit or maximum values (by adding MAX_*(               symbols) in MODPARAMS.DAT.           FOR MORE INFORMATIONI               For more information about the MODPARAMS.DAT file and about H               using AUTOGEN in general, see the OpenVMS System Manager's               Manual.L            I                   After Upgrading the OpenVMS Alpha Operating System 8-21                 Postupgrade Checklist$    E     _________________________________________________________________3       Postupgrade Checklist   E           Use the following checklist to make sure you have performed "           all the necessary tasks:  B           [] In a volume shadowing environment, re-form the shadow              set.6  #           [] Register new licenses.T  6           [] Examine AUTOGEN output stored in the file               AGEN$PARAMS.REPORT.  #           [] Examine MODPARAMS.DAT.S  B           [] Examine the command procedure templates supplied with<              the OpenVMS Alpha Version 6.2 operating system.  A           [] Decompress the system libraries using LIBDECOMP.COM.   B           [] Run the User Environment Test Package (UETP), to testB              the system (described in the OpenVMS System Manager's              Manual).t  "           [] Add and remove files.  A           [] Prepare your OpenVMS Alpha system and your PC to run C              OpenVMS Management Station by following the proceduresE%              described in Appendix D.e  ?           [] Install layered products, including DECwindows (ifo              necessary).  0           [] Back up the customized system disk.  <           [] Reboot each system that boots from the upgraded?              system disk (for a rolling upgrade in a VMScluster               environment).             [] Run AUTOGEN.s        ;     8-22 After Upgrading the OpenVMS Alpha Operating Systems                         I                                                                         AaI         _________________________________________________________________c  I                                       Halt, Boot, and Shutdown Procedures,                                                                            I                                   Halt, Boot, and Shutdown Procedures A-1d                Overview    E     _________________________________________________________________        Overview  ;           This appendix contains the following information:M  9           o  Booting operations, including the following:s  E              -  Booting the operating system CD-ROM, locally and fromd$                 an InfoServer system  5              -  Booting manually from the system disk   0              -  Performing a conversational boot  ,              -  Booting with minimum startup  8              -  Booting with the XDelta utility (XDELTA)  2              -  Booting from a different directory  B              -  Booting with a PMAZB or PMAZC TURBOchannel adapter  :              -  Booting over the network with an alternate$                 TURBOchannel adapter  '              -  Booting in an Emergencyo  ?           o  Set, Show, and Writeboot operations, including the               following:   8              -  Setting the system for automatic booting  0              -  Setting and showing boot devices  '              -  Setting boot parametersS  +              -  Using the Writeboot utility_  )           o  Halt and shutdown operations_  '           o  Troubleshooting procedures         +     A-2 Halt, Boot, and Shutdown ProceduresE r  e                        I         _________________________________________________________________   I                                                        Booting Operationsh                                                                          I                                   Halt, Boot, and Shutdown Procedures A-3n h  p      '     Booting the Operating System CD-ROM     E     __________________________________________________________________  '     Booting the Operating System CD-ROMi         INTRODUCTIOND           If you need to boot the OpenVMS Alpha operating system CD-A           ROM, either to perform an installation or upgrade or tou@           perform related operations such as mounting or backing?           up the system disk, follow the steps in the followings@           sections, depending on whether you are booting locally!           or from the InfoServer.v          BOOTING FROM THE LOCAL DRIVE/           Boot from the local drive as follows:i  E           1. Insert the operating system CD-ROM into the local CD-ROMe              drive.   ?           2. At the console prompt (>>>), enter the SHOW DEVICE E              command so you can identify the name of the CD-ROM drive.#              (for example, DKA400:)   <           3. Enter the boot command in the following format:  )              BOOT -flags 0,0 source-drivei  ?              Substitute the device name of the CD-ROM drive (as A              listed in the SHOW DEVICE display) for source-drive.S  E              For example, if the SHOW DEVICE display lists the devicepE              name of your CD-ROM drive as DKA400, enter the following_.              command and press the Return key:  '              >>> BOOT -flags 0,0 DKA400m  C           After you boot, the system displays a menu from which yout<           can choose options to perform the following tasks:  ?           o  Install or upgrade the operating system, using the 5              POLYCENTER Software Installation utility   ?           o  Enter a DCL environment from which you can performVB              preinstallation or maintenance tasks such as mountingD              or showing devices and backing up or restoring files on              the system disk  !           o  Shut down the systema  +     A-4 Halt, Boot, and Shutdown Procedures            I                                       Booting the Operating System CD-ROM       #         BOOTING FROM THE INFOSERVERsG               To boot the operating system CD-ROM using the InfoServer,                do the following:i  D               1. At the console prompt, enter the following command:  :                  >>> B -FL 0,0 -FI APB_061 lan-device-name  0                  Note the following conventions:  H                  o  APB_061 is the file name of the APB program used for?                     the initial system load (ISL) boot program.e  A                  o  lan-device-name is the name of the local area G                     network (LAN) device identified with your computer. E                     For information about the LAN devices your system ?                     supports, refer to the following table. ForsD                     additional information, see the hardware manualsF                     that you received with your Alpha computer and the9                     OpenVMS Software Product Description.   I                  ________________________________________________________ >                                             Ethernet      FDDII                  Alpha_Computer_____________Device________Device_________P  >                  AlphaServer 1000 series    ERA0, EWA0    FRA0  >                  AlphaServer 2000 series    ERA0, EWA0    FRA0  >                  AlphaServer 2100 series    ERA0, EWA0    FRA0  >                  AlphaServer 8200 series    EXA0, EWA0    FXA0  >                  AlphaServer 8400 series    EXA0, EWA0    FXA0  ;                  AlphaStation 200 series    EWA0          -   ;                  AlphaStation 400 series    EWA0          -   ;                  DEC 2000 series            ERA0          -   B                  DEC 3000 series            ESA0          "n/ESA0"  ;                  DEC 4000 series            EZA0          -   >                  DEC 7000 series            EXA0          FXA0  I                  DEC 10000 series           EXA0          FXA0            I                  ________________________________________________________   B                  Notes: If you are using a DEC 3000 or 4000 series,                  system, note the following:  I                                   Halt, Boot, and Shutdown Procedures A-5u o  t      '     Booting the Operating System CD-ROM       D              o  On DEC 3000 series systems, you can boot through theE                 InfoServer with an Ethernet PMAD device or FDDI DEFTAlE                 device by specifying the device name as "n/ESA0". ThetB                 value for n is the TURBOchannel slot number, whichA                 you can obtain by entering the SHOW CONFIGURATION A                 command at the console prompt (>>>) and examining B                 the display. For more information, see the sectionA                 titled Booting Over the Network with an Alternate 3                 TURBOchannel Adapter in Appendix A.u  A              o  On DEC 4000 series, you must specify the ISL filerA                 name in uppercase (APB_062). In addition, if yoursB                 system uses console firmware prior to Version 3.2,2                 enter the BOOT command as follows:  :                 >>> BOOT -FL 0,0 -start 0 -FI APB_062 EZA0  C           2. The InfoServer ISL program then displays the followingg              menu:  1              Network Initial System Load Functione              Version 1.1  (                FUNCTION         FUNCTION                  ID ,                  1     -        Display Menu$                  2     -        Help.                  3     -        Choose Service.                  4     -        Select Options$                  5     -        Stop  '              Enter a function ID value:   C           3. Respond to the prompts as follows, pressing the ReturnT"              key after each entry:  ,              a. Enter 3 for the function ID.  *              b. Enter 2 for the option ID.  2              c. Enter the service name (ALPHA062).  &              A sample display follows:    +     A-6 Halt, Boot, and Shutdown Procedures  -         I                                       Booting the Operating System CD-ROM       5                  Enter a function ID value: 3<Return>U  (                   OPTION          OPTION                     ID/                     1     -       Find Servicest:                     2     -       Enter known Service Name  4                  Enter an Option ID value: 2<Return>=                  Enter a Known Service Name: ALPHA062<Return>   G               After you boot, the system displays a menu from which you @               can choose options to perform the following tasks:  C               o  Install or upgrade the operating system, using the :                  POLYCENTER Software Installation utility.  C               o  Enter a DCL environment from which you can performPF                  preinstallation or maintenance tasks such as mountingH                  or showing devices and backing up or restoring files on!                  the system disk.k  &               o  Shut down the system.                                              I                                   Halt, Boot, and Shutdown Procedures A-7y m  o      )     Booting Manually from the System Disk     E     _________________________________________________________________n  )     Booting Manually from the System Disk          INTRODUCTIONA           This section describes how to manually boot the OpenVMSh6           Alpha operating system from the system disk.         HOW TO BOOT MANUALLY3           Boot the system disk manually as follows:   E           ___________________________________________________________sG           IF ...                          THEN ...                     o  7           the OpenVMS Alpha operating     go to step 1.t           system is running,  7           the OpenVMS Alpha operating     go to step 4. E           system is not running,                                        *           1. Log in to the SYSTEM account.  B           2. Enter the following command and press the Return key:  #              $ @SYS$SYSTEM:SHUTDOWN   ?           3. Answer the questions displayed by the system. WhenG=              the procedure asks if an automatic reboot shouldC@              be performed, press the Return key for NO. When the=              procedure is finished, it displays the followingC              message:   %              SYSTEM SHUTDOWN COMPLETEf  B           4. Halt the system by entering Ctrl/P or by pressing the              Halt button.[1]  <           5. Enter the BOOT command in the following format:                BOOT device-name              ____________________C           [1]         See the section titled Halting the System for C                       more information about how to halt your Alpha                        computer.s  +     A-8 Halt, Boot, and Shutdown Procedures     r      I                                     Booting Manually from the System Disk       B                  Substitute the device name of the system disk forF                  device-name. For example, to boot from a drive with aG                  device name of DKA400, enter the following command and &                  press the Return key:                     >>> BOOT DKA400  F                  To boot from the network, enter the following command*                  and press the Return key:                    >>> BOOT ESA0                                                                    I                                   Halt, Boot, and Shutdown Procedures A-9i a  t      $     Performing a Conversational Boot    E     _________________________________________________________________   $     Performing a Conversational Boot         INTRODUCTIONA           A conversational boot is most commonly used in researchoD           and development environments and during software upgrades.@           Perform a conversational boot to stop the boot processD           before it completes. The boot process stops after it loadsE           SYS$SYSTEM:SYSBOOT.EXE and displays the SYSBOOT> prompt. At D           the SYSBOOT> prompt, you can enter specific OpenVMS SystemC           Generation utility (SYSGEN) commands to do the following:e  ,           o  Examine system parameter values  +           o  Change system parameter values   +           o  Specify another parameter file   =           o  Specify another system startup command procedureg  E           o  Select the default system parameter file if you modified ?              system parameters to values that render the systemV              unbootable   &           o  Specify a minimum startup  (     HOW TO PERFORM A CONVERSATIONAL BOOTB           There are several ways to perform a conversational boot.5           The following procedure is the most direct:   E           ___________________________________________________________eF           IF ...                          THEN ...                      7           the OpenVMS Alpha operating     go to step 1.a           system is running,  7           the OpenVMS Alpha operating     go to step 4.aG           system is not running,                                          *           1. Log in to the SYSTEM account.  B           2. Enter the following command and press the Return key:  #              $ @SYS$SYSTEM:SHUTDOWNo  ,     A-10 Halt, Boot, and Shutdown Procedures           I                                          Performing a Conversational Bootp      C               3. Answer the questions displayed by the system. WhentA                  the procedure asks if an automatic reboot shouldhD                  be performed, press the Return key for NO. When theA                  procedure is finished, it displays the followingn                  message:o  )                  SYSTEM SHUTDOWN COMPLETE   F               4. Halt the system by entering Ctrl/P or by pressing the                   Halt button.[1]  I               5. To begin the conversational boot, enter the BOOT commandc)                  in the following format:   +                  BOOT -FL 0,1 [device-name]n  G                  Substitute the device name of the drive from which youiI                  want to boot for device-name. For example, if the systemsF                  disk has a device name of DKA400, enter the following2                  command and press the Return key:  (                  >>> BOOT -FL 0,1 DKA400  F                  If you do not specify a device name, the system bootsG                  from the boot device assigned when you entered the SET %                  BOOTDEF_DEV command.   H               6. At the SYSBOOT> prompt, you can enter any of the SYSGENI                  commands listed in Table A-1. For more information about_I                  these SYSGEN commands, see the OpenVMS System Managementh,                  Utilities Reference Manual.  E               7. When you finish using the SYSGEN commands, enter thes?                  CONTINUE command to complete the boot process. "               ____________________G               [1]         See the section titled Halting the System forEG                           more information about how to halt your AlphaE#                           computer.s  I                                  Halt, Boot, and Shutdown Procedures A-11            $     Performing a Conversational Boot      E           Table A-1 SYSGEN Commands Used in the SYSBOOT Procedure    ,  E           Command_____________Description____________________________r  9           CONTINUE            Resumes the boot procedure.e  C           DISABLE CHECKS      Inhibits checking of parameter values =                               specified with the SET command.e  B           ENABLE CHECKS       Permits checking of parameter values=                               specified with the SET command.s  ?           HELP                Displays a summary of the SYSBOOT >                               commands on the terminal screen.  ?           SET parameter-name  Establishes the value of a system (                               parameter.  A           SET/STARTUP         Sets the name of the system startups0                               command procedure.  @           SHOW [parameter]    Displays active, current, default,=                               maximum, and minimum values for_E                               specific parameters. (Use qualifiers tooC                               display characteristics of parameters 5                               grouped by categories.)   >           USE [file-spec]     Specifies a parameter file to beB                               used as a source of values. You mustB                               enter the entire file specification,A                               including device and directory; youfE                               cannot specify a logical name.         lE           ___________________________________________________________o       FOR MORE INFORMATION?           For examples of using conversational booting, see the B           sections titled Booting with Minimum Startup and Booting           in an Emergency.                  ,     A-12 Halt, Boot, and Shutdown Procedures           I                                              Booting with Minimum Startupt    I         _________________________________________________________________   $         Booting with Minimum Startup             INTRODUCTIONB               In certain cases, you might want to boot your systemE               without performing the full sequence of startup events. G               For example, if a startup event prevents you from loggingpI               in, you might want to boot the system without executing theHI               startup so that you can log in and fix the problem. You can G               use the conversational boot to specify a minimum startup.   D               Note: Because this procedure bypasses specific startup@               operations, it does not autoconfigure the system's!               peripheral devices.   (         HOW TO BOOT WITH MINIMUM STARTUP>               Boot the system with minimum startup as follows:  H               1. Perform a conversational boot by entering the following/                  command at the console prompt:_  /                  >>> BOOT -FL 0,1 [device-name]   F               2. Enter the following command and press the Return key:  .                  SYSBOOT> SET STARTUP_P1 "MIN"  A               3. Enter the following command to continue booting:   "                  SYSBOOT> CONTINUE  G               4. After the system boots, log in and enter the followinghC                  commands to invoke SYSMAN and clear the STARTUP_P1g-                  parameter you set in step 2:   (                  $ RUN SYS$SYSTEM:SYSMAN/                  SYSMAN> PARAMETERS USE CURRENT 5                  SYSMAN> PARAMETERS SET STARTUP_P1 ""l1                  SYSMAN> PARAMETERS WRITE CURRENTh          I                                  Halt, Boot, and Shutdown Procedures A-13i t  n      ,     Booting with the XDelta Utility (XDELTA)    E     _________________________________________________________________   ,     Booting with the XDelta Utility (XDELTA)         INTRODUCTION>           The XDelta utility (XDELTA) is a debugging tool thatE           system programmers use. The procedure for booting all Alphap,           computers with XDELTA is the same.    !     BOOT COMMAND QUALIFIER VALUESi@           The following table describes the valid values you can+           specify when booting with XDELTA:a  E           ___________________________________________________________oE           Value__System_Response_____________________________________k  0           0      Normal, nonstop boot (default).  C           1      Begins a conversational boot and then displays thet                   SYSBOOT prompt.  >           2      Includes XDELTA but does not take the initial                  breakpoint.  D           3      Displays the SYSBOOT prompt and includes XDELTA but6                  does not take the initial breakpoint.  B           6      Includes XDELTA and takes the initial breakpoint.  >           7      Includes XDELTA, displays the SYSBOOT prompt,;                  and takes the initial breakpoint at systemEH                  initialization.                                        E           ___________________________________________________________        HOW TO BOOT WITH XDELTAmE           The following is an example of booting with XDELTA from the            console prompt:l             >>> BOOT -FL 0,7            ,     A-14 Halt, Boot, and Shutdown Procedures f         I                                  Booting with the XDelta Utility (XDELTA)                FOR MORE INFORMATIONF               For more information about using XDELTA, see the OpenVMS+               Delta/XDelta Debugger Manual.n                                                                                    I                                  Halt, Boot, and Shutdown Procedures A-15     d      &     Booting from a Different Directory    E     _________________________________________________________________e  &     Booting from a Different Directory         INTRODUCTIONE           By default, the OpenVMS Alpha operating system is installed @           in the system root directory named [SYS0]. However, ifA           you have created a cluster system disk, you can use thevC           SYS$MANAGER:CLUSTER_CONFIG.COM procedure to add a copy of2B           the operating system to a different root directory. (SeeB           the OpenVMS System Manager's Manual for more informationD           about using the SYS$MANAGER:CLUSTER_CONFIG.COM procedure.)    *     HOW TO BOOT FROM A DIFFERENT DIRECTORYC           To boot from a different directory (for example, [SYS3]),t,           enter the BOOT command as follows:  "           >>> BOOT -FL 3,0  DKA200                                                    ,     A-16 Halt, Boot, and Shutdown Procedures    D      I                        Booting with a PMAZB or PMAZC TURBOchannel Adapter     I         _________________________________________________________________   :         Booting with a PMAZB or PMAZC TURBOchannel Adapter             INTRODUCTIONE               PMAZB and PMAZC TURBOchannel adapters are adapters that4G               are software-compatible with the integrated SCSI ports on ,               DEC 3000 Alpha series systems.  A               The DEC 3000 Alpha series system consoles implement D               the SHOW CONFIGURATION console command, which displaysG               information about the TURBOchannel options and the built-EF               in adapters in the system. When a PMAZB or PMAZC adapterF               is installed in the TURBOchannel, the SHOW CONFIGURATIONG               command displays the "PMAZB-AA" or "PMAZC-AA" string, the >               TURBOchannel slot number, and the device status.  C               The DEC 3000 Alpha series consoles also implement the G               SHOW DEVICE command, which displays information about the H               devices in the system. Because the integrated SCSI adapterC               is built into every DEC 3000 Alpha series system, thecF               SHOW DEVICE console command can display the SCSI devicesG               connected to the integrated SCSI ports. However, the SHOWaD               DEVICE console command cannot display the SCSI devices9               connected to the PMAZB or PMAZC SCSI ports.            DISPLAYING DEVICESF               To make the console display the devices connected to theG               PMAZB or PMAZC SCSI ports, enter the following command at I               the console prompt, where x is the TURBOchannel slot number-?               in which the PMAZB or PMAZC adapter is installed:                  >>> TEST TCx CNFGO  E               This command displays the devices that are connected totF               each SCSI port of the PMAZB or PMAZC adapter. The deviceH               controller letters are either A or B, based upon the PMAZBG               or PMAZC ports to which the devices are connected. Do not E               confuse these devices with any DKAxxx or DKBxxx devicesmD               displayed by the SHOW DEVICE command, which shows SCSI8               devices on the integrated SCSI ports only.        I                                  Halt, Boot, and Shutdown Procedures A-17  e  n      6     Booting with a PMAZB or PMAZC TURBOchannel Adapter           HOW TO BOOT =           To boot from a device connected to a PMAZB or PMAZC 5           adapter, enter the boot command as follows:r             >>> BOOT "X/DKYzzz"   =           In the example, the following conventions are used:   D           -  X is the TURBOchannel slot number in which the PMAZB or'              PMAZC adapter is installedr  5           -  DK is the device code of the boot devicer  B           -  Y is either A or B, depending on the SCSI port of theA              PMAZB or PMAZC adapter that contains the boot devicee  ;           -  zzz is the SCSI unit number of the boot devicen       HOW ADAPTERS ARE IDENTIFIEDiA           The OpenVMS Alpha operating system does not distinguish ?           between the PMAZB or PMAZC adapter and the integratedSD           SCSI adapter. The operating system views them as identicalA           adapters. Because the operating system searches for I/O D           adapters in backplane slot number order, device controllerE           letters are assigned that correspond to the backplane order A           of the TURBOchannel options, followed by the integrated >           adapters. This is different from console SCSI device=           naming, which always designates SCSI devices on the B           integrated SCSI ports as either "A" or "B" port devices.       EXAMPLE C           On a DEC 3000 Model 500 Alpha system with no TURBOchannel E           options installed, the OpenVMS Alpha operating system names B           the integrated SCSI ports PKA0 and PKB0, and the devicesC           connected to the ports inherit the controller letter fromtB           the port controller letter (A or B). However, if a PMAZB@           or PMAZC adapter is installed in the TURBOchannel, theC           operating system names the PMAZB or PMAZC SCSI ports PKA0 E           and PKB0 and names the integrated SCSI ports PKC0 and PKD0. C           The devices connected to the ports inherit the controller A           letter from the port controller letter (A, B, C, or D).r        ,     A-18 Halt, Boot, and Shutdown Procedures d  t      I           Booting Over the Network with an Alternate TURBOchannel AdapterC    I         _________________________________________________________________   G         Booting Over the Network with an Alternate TURBOchannel Adapterf             INTRODUCTIONE               You can use an alternate TURBOchannel adapter to boot a1C               DEC 3000 series Alpha computer (with the TURBOchannel E               option) over the network in an InfoServer or VMScluster F               environment. Examples of alternate TURBOchannel adaptersI               are the PMAD (which connects to the Ethernet) and the DEFTAt+               (which connects to the FDDI).h             HOW TO BOOTeA               To boot from a TURBOchannel device connected to one D               of these alternate adapters, enter the boot command as               follows:                 >>> BOOT "n/ESA0"   A               The value for n is the TURBOchannel slot number forhC               the device, which you can obtain by entering the SHOWeC               CONFIGURATION command at the console prompt (>>>) and B               examining the display. In the following example, theI               TURBOchannel slot number (listed under the "TCINFO" column)f               is 0:a           >>> SHOW CONFIG_           DEC 3000 - M300_%         Digital Equipment CorporationrP      VPP PAL X5.47-80800101/OSF PAL X1.34-80800201 - Built on 18-MAR-1995 11:376                          I                                  Halt, Boot, and Shutdown Procedures A-19e           C     Booting Over the Network with an Alternate TURBOchannel Adaptero      /               TCINFO      DEVNAM        DEVSTAT 0               ------      --------      --------P                 CPU      OK KN16-AA -V3.2-S6CD-I151-sV2.0-DECchip 21064 P3.0-150                ASIC      OKn                 MEM      OK                  MEM      OK      6a                 CXT      OK      5                  NVR      OKr                 SCC      OKi                  NI      OK                 ISDN      OKs     4t                SCSI      OK  0-PMAD-AA       TC0                                                           ,     A-20 Halt, Boot, and Shutdown Procedures s  V      I                                                   Booting in an EmergencyO    I         _________________________________________________________________o           Booting in an Emergencyo             INTRODUCTIOND               If a system problem prevents your system from booting,D               you might need to perform an emergency boot operation.G               Table A-2 summarizes these emergency boot operations, andpF               the sections that follow describe each boot operation in               more detail.  J               Table A-2 Emergency Boot Procedures                           I               Operation_____________When_to_Use__________________________a  @               Booting with default  When parameter values in theE               system parameters     parameter file have been modified D                                     so that the system is unbootable  G               Booting without       If an error in the startup or login H               startup and login     procedures prevents you from logging&               procedures            in  F               Booting without the   If you have forgotten the passwordE               user authorization    and cannot log in to a privilegedHI               file                  account                              bI               ___________________________________________________________i  .         BOOTING WITH DEFAULT SYSTEM PARAMETERS@               If the current values stored in the parameter fileD               have been incorrectly modified, these incorrect valuesA               might cause the system to become unbootable. With a E               conversational boot operation, you can reset the activeeG               values for all system parameters to the default value.[1]eI               The default values allow you to boot the system temporarily -               so you can correct the problem.   "               ____________________D               [1]         In most cases, Digital recommends that youB                           use AUTOGEN to modify system parameters.B                           In certain cases, however, you can use aC                           conversational boot to modify a parametermI                           value temporarily.  To change a parameter valuenF                           permanently, you must edit MODPARAMS.DAT andH                           run AUTOGEN. For instructions, see the OpenVMS2                           System Manager's Manual.  I                                  Halt, Boot, and Shutdown Procedures A-21                 Booting in an Emergencya                 The_Procedure   D           1. Perform a conversational boot by entering the following+              command at the console prompt:   +              >>> BOOT -FL 0,1 [device-name]   A           2. At the SYSBOOT> prompt, enter the following command:   !              SYSBOOT> USE DEFAULT_  A              This command specifies that default values should be %              used for all parameters.L  =           3. Enter the following command to continue booting:                 SYSBOOT> CONTINUE  >           4. When the system finishes booting, determine which?              changed parameter caused the problem and reset theh@              parameter value. If you specified the value for theC              parameter in the AUTOGEN parameter file MODPARAMS.DAT,eA              fix the value in that file and run AUTOGEN. For moreuB              information, see the OpenVMS System Manager's Manual.  -           5. Shut down and reboot the system.              Example              SYSBOOT> USE DEFAULT           SYSBOOT> CONTINUEe           Username: SYSTEM           Password: !           $ RUN SYS$SYSTEM:SYSMANm(           SYSMAN> PARAMETERS USE CURRENT1           SYSMAN> PARAMETERS SET NPAGEDYN 2999808 *           SYSMAN> PARAMETERS WRITE CURRENT           SYSMAN> EXIT)           $ EDIT SYS$SYSTEM:MODPARAMS.DATt              .              .              .7           [Insert the following line in MODPARAMS.DAT:]             MIN_NPAGEDYN = 2999808              .              .              .0           $ @SYS$UPDATE:AUTOGEN SAVPARAMS REBOOT  ,     A-22 Halt, Boot, and Shutdown Procedures           I                                                   Booting in an Emergency_      4         BOOTING WITHOUT STARTUP AND LOGIN PROCEDURESG               If the system does not complete the startup procedures or H               does not allow you to log in, bypass the startup and loginF               procedures. The startup and login procedures provided byF               Digital should always work. However, if you introduce anI               error when modifying the startup or login procedures, it is_G               possible to accidentally lock yourself out of the system.m                 The_ProcedureC  H               1. Perform a conversational boot by entering the following/                  command at the console prompt:o  /                  >>> BOOT -FL 0,1 [device-name]   D               2. Enter the following command at the SYSBOOT> prompt:  +                  SYSBOOT> SET/STARTUP OPA0:   A               3. Enter the following command to continue booting:a  "                  SYSBOOT> CONTINUE  I               4. When the system is booted, the operator console displayso?                  the DCL command prompt ($). You are logged in.e  1               5. Enter the following DCL command:h                    $ SET NOONO  D                  This command directs the operating system to ignoreF                  any errors that might occur. If you do not enter thisI                  command and you invoke an error, the system will log you                   out.O  B               6. Correct the error condition that caused the loginE                  failure. (That is, make the necessary repairs to the1I                  startup or login procedures, or to the SYSUAF.DAT file.)   E                  Invoke a text editor to correct the startup or logineH                  file. Note that some system consoles might not supply aG                  screen-mode editor. You can also copy a corrected fileiI                  and delete the incorrect version by using the RENAME andS!                  DELETE commands.   H               7. Invoke SYSMAN and enter the following commands to reset'                  the startup procedure:   I                                  Halt, Boot, and Shutdown Procedures A-23                 Booting in an EmergencyX      $              $ RUN SYS$SYSTEM:SYSMAN+              SYSMAN> PARAMETERS USE CURRENT B              SYSMAN> PARAMETERS SET/STARTUP SYS$SYSTEM:STARTUP.COM-              SYSMAN> PARAMETERS WRITE CURRENTg              SYSMAN> EXITm              $  ?           8. Perform a normal startup by entering the followingE              command:   "              $ @SYS$SYSTEM:STARTUP             Examplea  $           SYSBOOT> SET/STARTUP OPA0:           SYSBOOT> CONTINUEg           $ SET NOON,           $ SET DEFAULT SYS$SYSROOT:[SYSEXE]!           $ RUN SYS$SYSTEM:SYSMANu(           SYSMAN> PARAMETERS USE CURRENT?           SYSMAN> PARAMETERS SET/STARTUP SYS$SYSTEM:STARTUP.COM.*           SYSMAN> PARAMETERS WRITE CURRENT           SYSMAN> EXIT           $ @SYS$SYSTEM:STARTUPo  /     BOOTING WITHOUT THE USER AUTHORIZATION FILEoB           Ordinarily, the startup and login procedures provided byB           Digital always work; however, certain user interventionsD           can cause them to fail. A very simple way to lock yourselfA           out of the system is to set passwords to login accountse@           and forget them. In such an emergency, you can use theD           alternate user authorization file rather than the standard"           user authorization file.  D           Note: You can use this method only to log in to the systemB           from the console terminal; you cannot use other terminal           lines.  ;           Setting the system parameter UAFALTERNATE defines>6           the logical name SYSUAF to refer to the fileB           SYS$SYSTEM:SYSUAFALT.DAT. If this file is found during aB           normal login, the system uses it to validate the account9           and prompts you for the user name and password.T    ,     A-24 Halt, Boot, and Shutdown Procedures e  a      I                                                   Booting in an Emergency       F               If it cannot find this file, the system assumes that theB               UAF is corrupt and accepts any user name and any twoC               passwords to log you in to the system from the system D               console. Logins are prohibited from all other terminal               lines.                                                                                I                                  Halt, Boot, and Shutdown Procedures A-25i                Booting in an Emergency:      A           When you perform this procedure, the system assigns they0           following values to your user account:  E           ___________________________________________________________uE           Field____________Value_____________________________________B  $           Name             User name  $           UIC              [001,004]             Command          DCL           interpreter              Login flags      None3  @           Priority         Value of the system parameter, DEFPRI  >           Resources        Values of the PQL system parameters  G           Privileges       All                                          E           ___________________________________________________________   E           The process name is usually the name of the device on whichN.           you logged in (for example, _OPA0:).             The_Procedures  D           1. Perform a conversational boot by entering the following+              command at the console prompt:   +              >>> BOOT -FL 0,1 [device-name]r  A           2. At the SYSBOOT> prompt, enter the following command:c  (              SYSBOOT> SET UAFALTERNATE 1  ?           3. If your system is running DECwindows software, you C              must also disable the windowing system by entering the               following command:B  )              SYSBOOT> SET WINDOW_SYSTEM 0   <           4. Enter the CONTINUE command to continue booting:                SYSBOOT> CONTINUE  @           5. When the startup procedure completes, log in on theC              console terminal by entering any user name and any twoiA              passwords in response to the Username: and Password:s              prompts.a  ,     A-26 Halt, Boot, and Shutdown Procedures           I                                                   Booting in an Emergencyp      D               6. Enter the following command to use the default UAF:  L                  $ DEFINE/SYSTEM/EXECUTIVE_MODE SYSUAF SYS$SYSTEM:SYSUAF.DAT  I               7. Use the Authorize utility to fix the problem that caused C                  you to be locked out of the system (for example, aeC                  forgotten password). Enter HELP MODIFY at the UAF>rB                  prompt for information about modifying passwords.D                  For more details, see the OpenVMS System Management,                  Utilities Reference Manual.  H               8. Enter the following commands to invoke SYSMAN and clearE                  the UAFALTERNATE system parameter you set in step 2:a  (                  $ RUN SYS$SYSTEM:SYSMAN/                  SYSMAN> PARAMETERS USE CURRENT 6                  SYSMAN> PARAMETERS SET UAFALTERNATE 0  G                  In most cases, Digital recommends that you use AUTOGENBC                  to modify system parameters. However, because thiscE                  parameter is only being changed temporarily, you can .                  use SYSMAN to change it back.  I               9. If you disabled the windowing system in step 3, reenable 6                  it by entering the following command:  7                  SYSMAN> PARAMETERS SET WINDOW_SYSTEM 1   G               10.Enter the following command to save the changed systemT"                  parameter values:  1                  SYSMAN> PARAMETERS WRITE CURRENT   1               11.Shut down and reboot the system.M                 ExampleC                  I                                  Halt, Boot, and Shutdown Procedures A-27  Y              Booting in an EmergencyI      %           SYSBOOT> SET UAFALTERNATE 1p&           SYSBOOT> SET WINDOW_SYSTEM 0           SYSBOOT> CONTINUEi           Username: <Return>           Password: <Return>           Password: <Return>E           $ DEFINE/SYSTEM/EXECUTIVE_MODE SYSUAF SYS$SYSTEM:SYSUAF.DAT "           $ SET DEFAULT SYS$SYSTEM           $ RUN AUTHORIZEh4           AUTHORIZE> MODIFY SYSTEM/PASSWORD=FGLFTUTU           AUTHORIZE> EXITt!           $ RUN SYS$SYSTEM:SYSMAN (           SYSMAN> PARAMETERS USE CURRENT0           SYSMAN> PARAMETERS SET WINDOW_SYSTEM 1/           SYSMAN> PARAMETERS SET UAFALTERNATE 0 *           SYSMAN> PARAMETERS WRITE CURRENT           SYSMAN> EXIT            $ @SYS$SYSTEM:SHUTDOWN                                                      ,     A-28 Halt, Boot, and Shutdown Procedures r  d                        I         _________________________________________________________________l  I                                       Set, Show, and Writeboot Operationsp                                                                          I                                  Halt, Boot, and Shutdown Procedures A-29e e  r      ,     Setting the System for Automatic Booting    E     _________________________________________________________________O  ,     Setting the System for Automatic Booting         INTRODUCTION;           The Alpha computers can boot automatically from aI@           designated boot device. When you installed the OpenVMSC           Alpha operating system, you designated the system disk as A           the default boot device. The section titled Setting and B           Showing Boot Devices describes how to change the default           boot device.    '     WHEN SYSTEMS CAN BOOT AUTOMATICALLY_A           Alpha computers can boot automatically from the defaultt5           boot device under the following conditions:   0           o  When you first turn on system power  =           o  When system power comes on after a power failures  D           o  After you shut down the system (if you enter Y when theE              shutdown procedure asks if an automatic reboot should be.              performed)R             o  After a bugcheck   6           o  If the system halts under program control       HOW TO SET THE SYSTEMe@           Set the system to boot automatically by performing the           following steps:  E           ___________________________________________________________bE           IF ...                          THEN ...                   0  7           the OpenVMS Alpha operating     go to step 1.t           system is running,  7           the OpenVMS Alpha operating     go to step 4. E           system is not running,                                      E           ___________________________________________________________   *           1. Log in to the SYSTEM account.  B           2. Enter the following command and press the Return key:  #              $ @SYS$SYSTEM:SHUTDOWNa  ,     A-30 Halt, Boot, and Shutdown Procedures 0  S      I                                  Setting the System for Automatic Booting       C               3. Answer the questions displayed by the system. When A                  the procedure asks if an automatic reboot shouldeD                  be performed, press the Return key for NO. When theA                  procedure is finished, it displays the following                   message:I  )                  SYSTEM SHUTDOWN COMPLETE   F               4. Halt the system by entering Ctrl/P or by pressing the                   Halt button.[1]  H               5. If you have an SMP system with multiple CPUs, enter theF                  following command at the console prompt (>>>) to stop                   the other CPUs:                    >>> INITIALIZE   G               6. Enter the following command to show whether the systemd4                  has been set to boot automatically:  %                  >>> SHOW AUTO_ACTION   :                  The system displays one of the following:                    o  Restartt                    o  Boot                    o  Halt  A               7. Enter the SET AUTO_ACTION command if you want to D                  change the automatic booting behavior. For example,@                  the following command sets the system to reboot                  automatically:o  ,                  >>> SET AUTO_ACTION RESTART  I               8. After you set this variable, Digital recommends that you H                  set the boot device and operating system flags as well,H                  using the SET BOOTDEF_DEV and SET BOOT_OSFLAGS commands5                  described in the following sections.a  "               ____________________G               [1]         See the section titled Halting the System for G                           more information about how to halt your Alpha #                           computer.s  I                                  Halt, Boot, and Shutdown Procedures A-31     o      $     Setting and Showing Boot Devices    E     _________________________________________________________________i  $     Setting and Showing Boot Devices         INTRODUCTIONB           Use the SET BOOTDEF_DEV command to tell the system whichE           drive you want to boot from (that drive becomes the defaultAC           boot device). Use the SHOW BOOTDEF_DEV command to displayi*           the current default boot device.  B           Note that when you set this variable, Digital recommendsD           that you set the operating system boot parameters as well,-           using the SET BOOT_OSFLAGS command.u       SETTING THE BOOT DEVICE @           At the console prompt (>>>), enter the SET BOOTDEF_DEV*           command in the following format:  %           SET BOOTDEF_DEV device-name   C           Substitute the device name of the system disk for device-eD           name. For example, to boot from a drive with a device nameB           of DKA400 on a DEC 3000 Alpha series computer, enter the5           following command and press the Return key:   $           >>> SET BOOTDEF_DEV DKA400  C           The next time you boot the system, you can enter the BOOT E           command without specifying a device name (because DKA400 isD4           now the default boot device). For example:             >>> BOOT  C           Note: If you have not used the SET BOOTDEF_DEV command to C           set the drive to boot from and you enter the BOOT command B           without specifying a device name, the system displays an           error message.       SHOWING THE BOOT DEVICEgE           Use the SHOW BOOTDEF_DEV command to find out what drive was >           specified in the last SET BOOT command. For example:             >>> SHOW BOOTDEF_DEV    ,     A-32 Halt, Boot, and Shutdown Procedures           I                                          Setting and Showing Boot Devices       "         CANCELLING THE BOOT DEVICEI               To cancel the drive specified in a previous SET BOOTDEF_DEV G               command, enter the following command and press the Return                key:  !               >>> SET BOOTDEF_DEV   F               Note: This command is not valid on DEC 3000 Alpha series               systems.                                                                        I                                  Halt, Boot, and Shutdown Procedures A-33  t  M           Setting Boot Parametersu    E     _________________________________________________________________U       Setting Boot ParametersC         INTRODUCTION9           By default, when you boot the operating system,Y6           the flags parameter is set to 0. If you want1           to define parameters to enable specific 7           functions during the booting process, use theM+           SET BOOT_OSFLAGS console command.M         LIST OF VALID PARAMETERSD           The following is a list of values you can specify with the#           SET BOOT_OSFLAGS command:9  E           ___________________________________________________________D           HexadecimalEE           Value________System_Response_______________________________   ?           1            Allows a conversational boot (the systemc5                        displays the SYSBOOT> prompt).C  7           2            Maps XDELTA to a running system.t  E           4            Stops the boot procedure at the initial systemt"                        breakpoint.  7           8            Performs a diagnostic bootstrap.   @           10           Stops the boot procedure at the bootstrap#                        breakpoints.t  C           20           Omits header from secondary bootstrap image.e  <           80           Prompts for the name of the secondary&                        bootstrap file.  <           100          Halts the system before the secondary!                        bootstrap.   D           2000         Marks corrected read data error pages as bad.  B           10000        Displays extensive, detailed debug messages/                        during the boot process.r  ?           20000        Displays selected user-oriented messagesSE                        during the boot process.                      tE           ___________________________________________________________a  ,     A-34 Halt, Boot, and Shutdown Procedures i  D      I                                                   Setting Boot Parameterse      1         HOW TO ENTER THE SET BOOT_OSFLAGS COMMANDe8               The following examples show how to use the'               SET BOOT_OSFLAGS command:   H               o  The following command specifies the root directory as 0I                  and the parameter as 1, which sets the system to perform I                  a conversational boot from the [SYS0] directory when your(                  enter the BOOT command:  )                  >>> SET BOOT_OSFLAGS 0,1e                                                                      I                                  Halt, Boot, and Shutdown Procedures A-35a    y           Setting Boot Parameters       ?           o  The following command specifies the root directory ?              as 1 and the parameter as 0, which sets the systemr?              (for example, the second host in a two-system DSSIo>              VMScluster configuration) to boot from the [SYS1]B              directory (instead of [SYS0]) when you enter the BOOT              command:N  %              >>> SET BOOT_OSFLAGS 1,0P  ?           o  The following example specifies the root directory A              as 0 and the parameters as 1, 2, 4, and 20000 (for aNA              total hexadecimal value of 20007). As a result, wheno@              you enter the BOOT command, the system will performA              a conversational boot from the [SYS0] directory with ?              XDELTA, stop at the initial system breakpoint, andg,              display relevant user messages.  )              >>> SET BOOT_OSFLAGS 0,20007Y       DISPLAYING PARAMETERSN>           To display the parameters you have just set, use the1           SHOW BOOT_OSFLAGS command. For example:E             >>> SHOW BOOT_OSFLAGSN            BOOT_OSFLAGS = 0,20007                                        ,     A-36 Halt, Boot, and Shutdown Procedures r         I                                               Using the Writeboot Utility     I         _________________________________________________________________   #         Using the Writeboot Utilitys             INTRODUCTIONE               The Writeboot utility (WRITEBOOT.EXE) is copied to youreF               system disk during the installation procedure. It allowsE               you to create a bootable OpenVMS Alpha system disk fromhE               one that was originally created by one of the followingi               methods:  D               o  A nonimage backup of an Alpha system disk (possibly+                  corrupting the boot block)a  I               o  A nonimage restore of an Alpha system disk from an imagei                  save set   B               The Writeboot utility also allows you to rewrite theF               boot block of an OpenVMS Alpha system disk to point to aE               new version of the OpenVMS Alpha primary bootstrap file D               (APB.EXE) that you have previously copied to the disk.6               (Note that the file must be contiguous.)           INVOKING WRITEBOOTB               To invoke the Writeboot utility, enter the following               command:  (               $ RUN SYS$SYSTEM:WRITEBOOT  1               The utility prompts you as follows:   >               Update VAX portion of boot block (default is Y):@               Update Alpha portion of boot block (default is Y):  G               Answer N (No) to the VAX prompt. If you answer Y (Yes) to:F               update the Alpha boot block, the utility prompts you for"               the Alpha boot file:  $               Enter Alpha boot file:  H               Specify device-name:[VMS$COMMON.SYSEXE]APB.EXE in responseH               to this prompt, where device-name: indicates the device on/               which the system disk is mounted.0    I                                  Halt, Boot, and Shutdown Procedures A-37  g                           I         _________________________________________________________________   I                                              Halt and Shutdown Operations                                                                           I                                  Halt, Boot, and Shutdown Procedures A-39a                Halting the System    E     _________________________________________________________________        Halting the System         INTRODUCTION:           During installation, upgrade, and related systemE           operations, you might need to halt your system. The methods.C           for halting Alpha computers slightly, as described in the            next section.E    #     HOW TO HALT YOUR ALPHA COMPUTERi>           The following table summarizes the ways you can halt#           specific Alpha computers:   E           ___________________________________________________________ E           Alpha_Computer________How_to_Halt__________________________   8           AlphaServer 1000,     Do one of the following:9           2000, 2100 series     o  Press the Halt button.t  0                                 o  Press Ctrl/P.  -           AlphaServer 8200,     Press Ctrl/P.n           8400 series   8           AlphaStation 200,     Do one of the following:@           400 series            o  Press the Halt button (if the  E                                    graphics monitor is serving as thea,                                    console).  E                                 o  Press Ctrl/P (if you are using the ?                                    alternate console and port).   8           DEC 2000, 3000        Do one of the following:@           series                o  Press the Halt button (if the  E                                    graphics monitor is serving as thes,                                    console).  E                                 o  Press Ctrl/P (if you are using thea?                                    alternate console and port).M    ,     A-40 Halt, Boot, and Shutdown Procedures m  r      I                                                        Halting the System     I               ___________________________________________________________ I               Alpha_Computer________How_to_Halt__________________________o  <               DEC 4000 series       Do one of the following:  =                                     o  Press the Halt button.a  I                                     o  Press the Break key on the console =                                        (the default setting).,  C                                     o  Press Ctrl/P, but only after D                                        using the console command SETF                                        TTA0_HALTS n to enable this keyD                                        combination, where n can be 6I                                        (enables the Break key and Ctrl/P) H                                        or 2 (enables Ctrl/P but disables6                                        the Break key).  1               DEC 7000, 10000       Press Ctrl/P.F               seriesI               ___________________________________________________________r                                                    I                                  Halt, Boot, and Shutdown Procedures A-41$ T  S           Shutting Down the System    E     _________________________________________________________________P       Shutting Down the System         INTRODUCTIONB           Before you shut down the operating system, decide if youA           want it to reboot automatically or if you want to enterN=           console-mode commands after the shutdown completes.W  ?           You can perform the following three types of shutdownO           operations:   =           o  An orderly shutdown with SYS$SYSTEM:SHUTDOWN.COMw  4           o  An emergency shutdown with OPCCRASH.EXE  6           o  An emergency shutdown with crash commands  B           If you want the system to reboot automatically after theA           shutdown, see the section titled Setting the System for            Automatic Booting.       ORDERLY SHUTDOWN  @           The SHUTDOWN.COM procedure shuts down the system while<           performing maintenance functions such as disabling?           future logins, stopping the batch and printer queues,hB           dismounting volumes, and stopping user processes. To useB           the SHUTDOWN.COM command procedure, log in to the SYSTEMD           account, enter the following command, and press the Return           key:              $ @SYS$SYSTEM:SHUTDOWN  =           For more information about the SHUTDOWN.COM command =           procedure, see the OpenVMS System Manager's Manual.   (     EMERGENCY SHUTDOWN WITH OPCCRASH.EXE<           If you cannot perform an orderly shutdown with the@           SHUTDOWN.COM procedure, run the OPCCRASH.EXE emergencyC           shutdown program. To run the OPCCRASH.EXE program, log inwA           to the SYSTEM account, enter the following command, ands           press the Return key:o  #           $ RUN SYS$SYSTEM:OPCCRASH   ,     A-42 Halt, Boot, and Shutdown Procedures c  b      I                                                  Shutting Down the System       F               For more information about the OPCCRASH program, see the.               OpenVMS System Manager's Manual.  .         EMERGENCY SHUTDOWN WITH CRASH COMMANDSD               Use crash commands only if the system is "hung" (stopsF               responding to any commands) and you cannot log in to theE               SYSTEM account to use the SHUTDOWN.COM procedure or the #               OPCCRASH.EXE program.   @               Note: The method described here works on all AlphaC               computers. However, on certain systems, you can force_C               your processor to fail (crash) by entering a specificiF               console command. See the hardware manuals that came with1               your computer for that information.M  @               To force your processor to fail, do the following:  F               1. Halt the system by entering Ctrl/P or by pressing the                   Halt button.[1]  D               2. To examine processor registers, enter the following3                  commands and press the Return key:                     >>> E -N F R0                  >>> E PS   I                  The system displays the contents of the registers. Write H                  down these values if you want to save information about)                  the state of the system.   G               3. Enter the following commands and press the Return key:   *                  >>> D PC FFFFFFFF00000000                  >>> D PS 1F00  D                  By depositing these values, you cause the system toI                  write a memory dump to the system dump file on the disk.f  F               4. Enter the following command and press the Return key:                    >>> CONTINUE   >                  This causes the system to perform a bugcheck.  H               5. After the system reboots, log in to the SYSTEM account.  "               ____________________G               [1]         See the section titled Halting the System for G                           more information about how to halt your Alpha #                           computer.t  I                                  Halt, Boot, and Shutdown Procedures A-43> S  A           Shutting Down the System      C           6. To examine the dump file, enter the following commands 5              and press the Return key after each one:l  3              $ ANALYZE/CRASH SYS$SYSTEM:SYSDUMP.DMPB              SDA> SHOW CRASH  @              For more information about the System Dump AnalyzerD              (SDA) utility, see the OpenVMS AXP System Dump Analyzer              Utility Manual.                                                                        ,     A-44 Halt, Boot, and Shutdown Procedures                             I         _________________________________________________________________D  I                                                Troubleshooting Procedures_                                                                          I                                  Halt, Boot, and Shutdown Procedures A-45v o  a           If the System Does Not Boot     E     _________________________________________________________________a       If the System Does Not Booto         INTRODUCTION@           If the system does not boot because a hardware problemA           occurs, a question mark (?)  usually precedes the error ?           message displayed on the console terminal. An exampleTA           of a hardware problem is a read error on a disk or tapeD           cartridge drive.         FOR HARDWARE PROBLEMS >           If you suspect a hardware problem, do the following:  A           1. Consult the hardware manual for your Alpha computer.,  3           2. Contact Multivendor Customer Services.D       FOR SOFTWARE PROBLEMSiD           When the operating system is loaded into memory, a messageB           similar to the following appears on the terminal screen:  <           SYSTEM   job terminated at 19-MAR-1995 15:05:03.17  A           If the system does not display this message, a software :           problem has probably occurred. Do the following:  D           1. Turn off the system. Turn it back on and try to reboot.  C           2. Perform a conversational boot using the default systemmD              parameters or try one of the emergency boot procedures.  E           3. If the system boots, run the AUTOGEN procedure. For moresE              information about the AUTOGEN procedure, see the OpenVMSp%              System Manager's Manual.o                  ,     A-46 Halt, Boot, and Shutdown Procedures o  a      I                               Detecting and Responding to System Problemst    I         _________________________________________________________________   3         Detecting and Responding to System Problems              INTRODUCTIONC               If your system exhibits unexpected behavior, note the                following:  I               o  If the system displays a bugcheck message on the consoleCD                  terminal and shuts itself down, it means the systemB                  encountered a problem that made further operationH                  impossible or dangerous. Reboot the system as explainedG                  in the section titled Booting Manually from the System_I                  Disk, or let it reboot automatically as explained in theII                  section titled Setting the System for Automatic Booting.h  F               o  If the system stops responding to your commands (thatH                  is, the system "hangs"), there is a possible failure inF                  a system software or hardware component or a possible                  power failure.w  E               o  If the system exhibits erratic behavior (it does notAC                  respond according to specifications), it indicates_D                  a possible failure in a system software or hardware                  component._  !         DETECTING SYSTEM PROBLEMS E               To determine if the failure is a system problem, do thel               following:  D               o  Be sure that you did not press the F1 key (the HoldD                  Screen key). The Hold Screen light goes on when you1                  press either F1 or enter Ctrl/S.   D               o  Enter Ctrl/T to check the status of your process. AB                  status line should appear, indicating the name ofE                  the program that is executing and other information.e@                  If the status line does not appear, the program>                  you are executing might be stalled or "hung."=                  (If you have disabled Ctrl/T by entering the A                  command SET NOCONTROL=T or have set the terminalr<                  to NOBROADCAST mode by entering the commandI                  SET TERMINAL/NOBROADCAST, this procedure does not work.)     I                                  Halt, Boot, and Shutdown Procedures A-47            /     Detecting and Responding to System Problems       C           o  Make sure the cable connecting the terminal or monitor-%              to the system is secure.        HOW TO RESPONDA           If you determine that you have a system problem, do the            following:  >           1. Force an exit from a stalled or "hung" program byB              entering Ctrl/Y. Note that when you enter Ctrl/Y, anyC              work performed by the program and not saved on disk isr              lost.  E           2. If the system is still unresponsive, halt it by entering 6              Ctrl/P or by pressing the Halt button.[1]  B           3. Note in detail the sequence of events that caused the>              problem and notify Multivendor Customer Services.                                                         ____________________C           [1]         See the section titled Halting the System fortC                       more information about how to halt your Alphae                       computer.   ,     A-48 Halt, Boot, and Shutdown Procedures    o                    I                                                                         BtI         _________________________________________________________________   I                                  Backing Up and Restoring the System Disk                                                                             I                              Backing Up and Restoring the System Disk B-1l x  c           Overview    E     _________________________________________________________________i       Overview  C           This appendix describes how to perform backup and restore C           operations on the system disk. You perform these tasks by A           entering commands from a specialized, restricted backupG>           environment that you access through the menu that isD           displayed when you boot the OpenVMS Alpha operating systemE           CD-ROM or through an alternate method that does not requireO           the CD-ROM.   D           This specialized backup environment is required because itD           allows you to create an exact copy of the system disk. YouD           cannot create an exact copy in a standard operating systemC           environment because the OpenVMS Backup utility saves onlyoA           what is on the disk at the moment the BACKUP command istB           executing, excluding portions of open files contained inE           memory or data about files not yet written back to the diskt           (cache).  A           For more information about backup operations, includinge;           procedures for backing up and restoring files and ?           directories, see the OpenVMS System Manager's Manual.   *     REASONS FOR BACKING UP THE SYSTEM DISKA           The primary reason why you should have a backup copy ofmD           the system disk is so you can fully restore your system inC           response to any hardware or software problem that affectsVD           the integrity of your original system disk or your abilityE           to access it. For example, you would need to use the backuphE           copy to restore your system under the following conditions:u  B           o  When a problem occurs during an OpenVMS Alpha upgradeD              or update, or during the installation of other softwareB              products. If you backed up the system disk before youE              attempted any of those procedures, you could restore theo9              system disk and attempt the procedure again.n  D           o  When a system file that is accidentally deleted rendersD              the system disk inoperable. If you backed up the systemC              disk after you installed or upgraded the OpenVMS AlphalB              operating system and any other software products, you+              could restore the system disk.p    0     B-2 Backing Up and Restoring the System Disk d  t      I                                                                  Overview       H               o  When the drive that holds the system disk malfunctions.F                  If you have a backup copy of the system disk, you canI                  restore it to a functioning disk and continue to use then                  system.  B               Another reason for backing up the system disk, is toC               eliminate disk fragmentation, which occurs when filess@               are stored noncontiguously on the disk. The BACKUPE               /IMAGE command creates a copy on which files are storedh               contiguously.N           SUGGESTED PROCEDURES/               Digital recommends the following:s  G               o  The preferred method for performing system disk backuplG                  and restore operations is to boot the operating system H                  CD-ROM, choose the DCL option from menu, and then enterI                  the appropriate backup commands. The detailed procedures D                  are described in the sections titled Backing Up the;                  System Disk and Restoring the System Disk._  G                  However, if you do not have access to the compact disk I                  or if you want to back up a shadowed system disk without B                  disabling the shadow set, you can use a differentE                  procedure, described in the section titled Alternatee.                  Backup and Restore Procedure.  8               o  Store the backup media in a safe place.  :               o  If you have a VMScluster environment with7                  more than one system disk, be sure the <                  volume label on each system disk and backup;                  copies of system disks are unique. Use the F                  SET VOLUME/LABEL command to change a volume label, if                  necessary.l           VMSCLUSTER CAUTIONH               If any nodes except the node used to run BACKUP are bootedF               during the backup operations described in this appendix,B               your cluster will become partitioned, where nodes inF               the existing cluster divide into two or more independentF               clusters. This condition can cause data file corruption.      I                              Backing Up and Restoring the System Disk B-3_ _  _           Overview      @           In addition, these backup environments do not restrictD           your use of DCL commands to the BACKUP command only, whichC           further increases your risk of accidentally destroying or E           corrupting data on a disk. Therefore, to avoid jeopardizing C           the integrity of your data in any way, Digital recommends D           that you shut down the entire VMScluster system before you#           back up your system disk.i                                                                            0     B-4 Backing Up and Restoring the System Disk           I                                                Backing Up the System Diske    I         _________________________________________________________________l  "         Backing Up the System Disk             GETTING STARTEDBC               Before you back up the system disk, do the following:   F               1. In a VMScluster environment, dismount the system diskC                  from all systems in the cluster that have the disk I                  mounted as a data disk (rather than as the system disk).$  =               2. Shut down all systems booted from that disk._  E               3. Boot the operating system CD-ROM locally or from thew9                  InfoServer (as described in Appendix A).u  F               4. Choose the DCL option (4) from the menu. For example:  P                 ****************************************************************  P                   You can install or upgrade the OpenVMS Alpha operating system.M                   You can also execute DCL commands and procedures to performUI                   "standalone" tasks, such as backing up the system disk.   3                 Please choose one of the following:   C                    1  Install or upgrade OpenVMS Alpha Version V6.2 P                    2)  List layered product kits that this procedure can install<                    3)  Install or upgrade layered product(s):                    4)  Execute DCL commands and procedures,                    5)  Shut down this system  ?                  Enter CHOICE or ? to repeat menu: (1/2/3/?)) 4   B               5. At the triple dollar sign prompt ($$$), enter the&                  SHOW DEVICES command.  G               6. Examine the list of devices so you can determine which E                  device is the source drive (the system disk you want G                  to back up) and which device is your target drive (thedH                  supported disk or tape device that will hold the backed                  up files).f      I                              Backing Up and Restoring the System Disk B-5e u  h           Backing Up the System Disk           MOUNTING DEVICESC           When you have determined which devices will be the sourcet>           drive and target drive, mount those devices (and anyB           other output devices you plan to use) before you perform@           any backup operations. Enter the MOUNT commands in the           following format:t  9           $$$ MOUNT/OVERRIDE=IDENTIFICATION  source-drivee(           $$$ MOUNT/FOREIGN target-drive  )           Note the following conventions:M  E           o  source-drive is the name of the drive holding the systeml              disk.  E           o  target-drive is the name of the drive that will hold theg              backup files.       ENTERING THE BACKUP COMMANDMC           When the system disk and output devices are mounted, back B           up the system disk by entering the BACKUP command in the           following format:a  =           $$$ BACKUP/IMAGE/VERIFY source-drive: target-drive:(  D           (You must also include the save set name and the /SAVE_SET:           qualifier if the target drive is a tape device.)       EXAMPLES?           In this example the system disk and a target disk areoA           mounted so the BACKUP command can create a backup disk.b7           (You can use a backup disk as a system disk.)   2           $$$ MOUNT/OVERRIDE=IDENTIFICATION DKA200"           $$$ MOUNT/FOREIGN DKA3001           $$$ BACKUP/IMAGE/VERIFY DKA200: DKA300:E  B           In this example the system disk and a target tape deviceE           are mounted so the BACKUP command can create a backup tape.s  2           $$$ MOUNT/OVERRIDE=IDENTIFICATION DKA200"           $$$ MOUNT/FOREIGN MKA300K           $$$ BACKUP/IMAGE/VERIFY DKA200: MKA300:APR_06_BACKUP.BCK/SAVE_SET     0     B-6 Backing Up and Restoring the System Disk           I                                                Backing Up the System Diske      +         CHANGING THE CLUSTER_SIZE PARAMETERyF               The BACKUP command creates a system disk that includes aG               set of volume parameters provided by Digital, including a G               CLUSTER_SIZE (disk access scheme) that is appropriate for H               your system. (The CLUSTER_SIZE refers to the way files areG               stored on the disk, not to cluster environments.) You canHE               change most volume parameters later with the SET VOLUMEt               command.  G               However, to change the CLUSTER_SIZE, you must back up theHH               system disk to a disk that has been previously initializedG               with the CLUSTER_SIZE that you want. For more informationiE               about initializing a disk and using the BACKUP command, E               see the OpenVMS System Manager's Manual and the OpenVMS G               System Management Utilities Reference Manual, and see thelF               description of the INITIALIZE and BACKUP commands in the%               OpenVMS DCL Dictionary.            WHAT TO DO NEXT H               After you complete the backup operation, do the following:  >               1. Enter the LOGOUT command to exit from the DCL4                  environment and return to the menu.  0               2. Choose the shutdown option (5).  I               3. After the shutdown completes, boot from the system disk.                                     I                              Backing Up and Restoring the System Disk B-7  f  e           Restoring the System Disk_    E     _________________________________________________________________S       Restoring the System DiskR         GETTING STARTEDeA           Before you can restore the system disk, you must do the            following:  "           1. Shut down the system.  A           2. Boot the operating system CD-ROM locally or from thea5              InfoServer (as described in Appendix A).   B           3. Choose the DCL option (4) from the menu. For example:  P                 ****************************************************************  O                  You can install or upgrade the OpenVMS Alpha operating system.eL                  You can also execute DCL commands and procedures to performH                  "standalone" tasks, such as backing up the system disk.  4                  Please choose one of the following:  C                    1  Install or upgrade OpenVMS Alpha Version V6.2sP                    2)  List layered product kits that this procedure can install<                    3)  Install or upgrade layered product(s):                    4)  Execute DCL commands and procedures,                    5)  Shut down this system  ;              Enter CHOICE or ? to repeat menu: (1/2/3/?)) 4   >           4. At the triple dollar sign prompt ($$$), enter the"              SHOW DEVICES command.  C           5. Examine the list of devices so you can determine whichlE              device is the source drive (the drive holding the backed C              up files you want to restore) and which device is youry?              target drive (the disk on which you want the files_              restored)._            0     B-8 Backing Up and Restoring the System Disk           I                                                 Restoring the System Diskh               MOUNTING DEVICESG               When you have determined which devices will be the sourceCB               drive and target drive, mount those devices (and anyF               other output devices you plan to use) before you performE               any restore operations. Enter the MOUNT commands in thed               following format:   =               $$$ MOUNT/OVERRIDE=IDENTIFICATION  source-driveo,               $$$ MOUNT/FOREIGN target-drive  -               Note the following conventions:   I               o  source-drive is the device holding the files you want tod                  restore.   D                  (Note, however, that you must use the MOUNT/FOREIGN?                  command if the source drive is a tape device.)o  1               o  target-drive is the destination.   #         ENTERING THE BACKUP COMMANDe?               Enter the BACKUP command in the following format:f  A               $$$ BACKUP/IMAGE/VERIFY source-drive: target-drive:s  H               (You must also include the save set name and the /SAVE_SET>               qualifier if the source drive is a tape device.)           EXAMPLESI               In this example a backup disk and a target disk are mounted H               so the BACKUP command can restore the system disk from the               backup disk:  6               $$$ MOUNT/OVERRIDE=IDENTIFICATION DKA300&               $$$ MOUNT/FOREIGN DKA2005               $$$ BACKUP/IMAGE/VERIFY DKA300: DKA200:l  I               In this example a backup tape and a target disk are mountediH               so the BACKUP command can restore the system disk from the               backup tape:  &               $$$ MOUNT/FOREIGN MKA300&               $$$ MOUNT/FOREIGN DKA200O               $$$ BACKUP/IMAGE/VERIFY MKA300:APR_06_BACKUP.BCK/SAVE_SET DKA200:   I                              Backing Up and Restoring the System Disk B-9c a              Restoring the System DiskC           WHAT TO DO NEXTtE           After you complete the restore operation, do the following:   :           1. Enter the LOGOUT command to exit from the DCL0              environment and return to the menu.  ,           2. Choose the shutdown option (5).  E           3. After the shutdown completes, boot from the system disk.y                                                                        1     B-10 Backing Up and Restoring the System Disk" g  r      I                                    Alternate Backup and Restore Procedure     I         _________________________________________________________________l  .         Alternate Backup and Restore Procedure             INTRODUCTIONF               This section describes an alternate method of performingE               backup and restore operations on your system disk. WithpD               this method, you install the operating system (withoutB               options) on another disk and perform your backup andH               restore operations on the system disk from there. Use this4               method under the following conditions:  I               o  If you do not have access to the operating system CD-ROMd$                  and its menu system  F               o  If you want to back up a shadowed system disk without)                  disabling the shadow set_  F               Note: It it also possible to back up your running systemD               disk by using the qualifier /IGNORE=INTERLOCK with theD               BACKUP command and ignoring warning messages. However,C               that method requires that all other use of the systemiF               be suspended, including disabling logins, stopping printD               and batch queues, and turning off networking software.F               In addition, you cannot use this method to restore filesG               to the running system disk. Because of these limitations,eI               Digital recommends that if you must use an alternate methodaF               to backup or restore the system disk, you use the method(               described in this section.  #         PREPARING AN ALTERNATE DISK 3               Prepare an alternate disk as follows:   G               1. Log in to a privileged account on your running OpenVMS                   Alpha system.  D               2. Using the SHOW DEVICE command, identify a data diskD                  on which you can install the operating system, withF                  no options. This will be your target disk during that2                  installation. Note the following:  H                  o  You will need approximately 75,000 blocks to install9                     the operating system with no options.o  :                  o  Existing data will remain on the disk.  I                             Backing Up and Restoring the System Disk B-11e a  e      *     Alternate Backup and Restore Procedure      >           3. The target disk must be mounted privately to yourD              process. (This prevents other users from accessing thisA              disk during the installation and backup procedures.) D              Therefore, if the target disk was mounted with /SYSTEM,@              /CLUSTER, /GROUP, or /SHARE, dismount that disk andD              mount it without using those qualifiers or the /FOREIGN$              qualifier. For example:  3              $ MOUNT/OVERRIDE=IDENTIFICATION DKA200   E           4. Enter the following command to install the OpenVMS Alpha C              operating system, with no options, on the target disk:   D              $ @SYS$SYSTEM:AXPVMS$PCSI_INSTALL_MIN.COM [target-disk]  D              (The procedure will prompt you for a device name if you4              do not specify it on the command line.)  E           5. As the procedure completes the installation, the display )              is similar to the following:   ?     *** DEC AXPVMS VMS V6.2: VMS Operating System, Version V6.2e  :         COPYRIGHT  (c) 21-MAR-1995 -- All rights reserved  %         Digital Equipment CorporationS  /     %PCSIUI-I-DONEASK, execution phase starting ,     The following product will be installed:     DEC AXPVMS VMS V6.2 I     %PCSI-I-VOLINFO, estimated space information for volume DISK$MINAlphaI=     -PCSI-I-VOLSPC, -1 required; 741063 available; 741064 net P    Portion Done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%-     The following product has been installed:c     DEC AXPVMS VMS V6.2i	         . 	         .m	         .fB         The installation of minimum OpenVMS Alpha is now complete.  :         Use the following command to boot minimum OpenVMS:  )             BOOT -FLAGS E,O <device-name>h  @         (Your system may require additional parameters to boot.)  1     B-12 Backing Up and Restoring the System Disk            I                                    Alternate Backup and Restore Procedurer      E                  Caution: If your system is a cluster member, DigitalcD                  recommends that you shut down the entire VMSclusterF                  system before you back up your system disk. This willI                  prevent you from creating a partitioned cluster and from E                  jeopardizing the integrity of your data in any otheru                  way.t            USING THE ALTERNATE DISK@               Use the alternate disk (on which you installed theE               operating system with no options) to perform backup and ,               restore operations as follows:  '               1. Shut down your system.e  I               2. Boot the alternate disk from the SYSE root. For example:   +                  >>> BOOT -FLAGS E,0 DKA200i  C                  The system automatically logs you in to the SYSTEM F                  account and then displays a triple dollar sign prompt                  ($$$).i  C                  Note: During the boot and login operations on thiscH                  minimum version of the operating system, you can ignoreB                  messages about licenses, which are similar to the                  following:   P             %LICENSE-I-NOLICENSE, no license is active for this software product  D               3. If your system disk is shadowed, install and load aE                  Volume Shadowing license on this data disk. You willsF                  then be able to back up the shadowed system disk fromA                  this data disk without disabling the shadow set.   E                  Note: Digital recommends that you do not install anyoD                  other licenses, including OpenVMS licenses, on thisG                  alternate system. You will be able use the system onlyi"                  from the console.              I                             Backing Up and Restoring the System Disk B-13a D  t      *     Alternate Backup and Restore Procedure      E           4. Mount the system disk and any output devices you plan to 9              use during the backup or restore operations.   C           5. Perform the necessary backup and restore operations by 6              entering the appropriate BACKUP commands.  "           6. Shut down the system.  1           7. Boot from your original system disk._                                                                        1     B-14 Backing Up and Restoring the System Disk  k  o                    I                                                                         C I         _________________________________________________________________   I                                             License Management Supplement                                                                             I                                         License Management Supplement C-1r                Overview    E     _________________________________________________________________m       Overview  A           This appendix contains information that supplements the*@           license instructions in this manual and in the OpenVMS,           License Management Utility Manual.  C           After you install the OpenVMS Alpha operating system, you A           must register OpenVMS Alpha licenses, which let you use D           the OpenVMS Alpha operating system. You must also registerA           the licenses for the OpenVMS Alpha layered products you @           have purchased, such as DECnet for OpenVMS. (Note thatB           after an upgrade, however, you do not have to reregister@           licenses for the OpenVMS Alpha operating system or for@           the layered products.) To register a license, you needA           to obtain a Product Authorization Key (PAK). A PAK is adD           printed document provided by Digital Equipment Corporation@           that contains the appropriate information to authorizeE           access to software on an Alpha computer (or in a VMScluster ?           environment). You can obtain a PAK from a MultivendoryA           Customer Services representative in the same way as youi           obtain software.  3     USING THE LICENSE UNIT REQUIREMENT TABLE (LURT) ?           Many PAKs contain a table name in the availability or >           activity fields. This name refers to a column in the?           License Unit Requirement Table (LURT), which is shownuA           in Table C-1. Column A in the LURT indicates the numbery@           of license units required for each processor listed in?           the System Marketing Model column. Column H refers tot>           layered products you may choose to register as well.B           For example, if your PAK specifies availability = A, youA           would require 50 license units to load the license on asB           DEC 3000 Alpha Model 500 series computer, or 500 licenseA           units to load the license on a DEC 7000 Alpha Model 610            computer.   E           Note that some PAKs specify MOD_UNITS in the options field.tC           The MOD_UNITS option allows the system manager to use theeB           DCL command LICENSE MODIFY/UNITS to temporarily increaseA           the size of the PAK. This permits a product to be used,g@           in certain emergency situations, on a processor largerA           than the processor size specified in the license. Check D           your license terms and conditions before modifying license  %     C-2 License Management Supplemento e  C      I                                                                  Overview       F               units. Reset the PAK size to its original size after the.               emergency situation is resolved.  I               Table C-1 License Unit Requirement Table (LURT)            n  I               System_Marketing_Model______A___________H__________________e  9               AlphaServer 1000 4/233      15         1050O  9               AlphaServer 2000 4/233 (1   400        1100A               CPU)  9               AlphaServer 2000 4/233 (2   500        1100                CPU)  9               AlphaServer 2000 4/275 (1   400        1100                CPU)  9               AlphaServer 2000 4/275 (2   500        1100                CPU)  9               AlphaServer 2100 4/233 (1   400        1100a               CPU)  9               AlphaServer 2100 4/233 (2   500        1100                CPU)  9               AlphaServer 2100 4/233 (3   600        1100                CPU)  9               AlphaServer 2100 4/233 (4   700        1100o               CPU)  9               AlphaServer 2100 5/250 (1   400        1100u               CPU)  9               AlphaServer 2100 5/250 (2   500        1100                CPU)  I               Key to License Type Codes and Values:                      h3               _____________________________________hG                A - The number of OpenVMS Alpha operating system licenseuE                    units (Unlimited or Base) required for the system. H                B through G - Omitted from table; reserved for future useG                H - The number of OpenVMS Alpha layered products licensei1                    units required for the system.   I                                                  (continued on next page)   I                                         License Management Supplement C-3  .  t           Overview      E           Table C-1 (Cont.) License Unit Requirement Table (LURT)       E           System_Marketing_Model______A___________H__________________t  5           AlphaServer 2100 5/250 (3   600        1100            CPU)  5           AlphaServer 2100 5/250 (4   700        1100            CPU)  5           AlphaServer 8200 (1 CPU)   2000        1150m  5           AlphaServer 8200 (2 CPU)   2100        1150_  5           AlphaServer 8200 (3 CPU)   2200        1150R  5           AlphaServer 8200 (4 CPU)   2300        1150o  5           AlphaServer 8200 (5 CPU)   2400        1150:  5           AlphaServer 8200 (6 CPU)   2500        1150o  5           AlphaServer 8400 (1 CPU)   2600        1150   5           AlphaServer 8400 (2 CPU)   2700        1150   5           AlphaServer 8400 (3 CPU)   2800        1150l  5           AlphaServer 8400 (4 CPU)   2900        1150*  5           AlphaServer 8400 (5 CPU)   3000        1150i  5           AlphaServer 8400 (6 CPU)   3100        1150   5           AlphaServer 8400 (7 CPU)   3200        1150e  5           AlphaServer 8400 (8 CPU)   3300        1150c  5           AlphaServer 8400 (9 CPU)   3400        1150s  5           AlphaServer 8400 (10 CPU)  3500        1150n  5           AlphaServer 8400 (11 CPU)  2600        1150   E           Key to License Type Codes and Values:                       /           _____________________________________dD             A - The number of OpenVMS Alpha operating system licenseB                 units (Unlimited or Base) required for the system.E             B through G - Omitted from table; reserved for future uselD             H - The number of OpenVMS Alpha layered products license.                 units required for the system.  E                                              (continued on next page)e  %     C-4 License Management Supplemente o  a      I                                                                  Overvieww      I               Table C-1 (Cont.) License Unit Requirement Table (LURT)    p  I               System_Marketing_Model______A___________H__________________   9               AlphaServer 8400 (12 CPU)  2600        1150N  9               AlphaStation 200 4/100      12         1050v  9               AlphaStation 200 4/133      12         1050e  9               AlphaStation 200 4/266      12         1050v  9               AlphaStation 250 4/266      12         1050e  9               AlphaStation 400 4/233      12         1050   9               DEC 2000-300/300S           12         1050E  9               DEC 2000-500/500S           12         1050a  9               DEC 3000-300                15         1050   9               DEC 3000-300L               15         1050e  9               DEC 3000-400/400S           20         1050   9               DEC 3000-600/600S           20         1050   9               DEC 3000-500/500S           50         1100   9               DEC 3000-500X               50         1100N  9               DEC 3000-800/800S           50         1100m  9               DEC 4000-610                300        1150A  9               DEC 4000-620                400        1200m  9               DEC 4000-710                300        1150   9               DEC 4000-720                400        1200   9               DEC 7000-610                500        1200   3               Key to License Type Codes and Values: 3               _____________________________________ G                A - The number of OpenVMS Alpha operating system license3E                    units (Unlimited or Base) required for the system.AH                B through G - Omitted from table; reserved for future useG                H - The number of OpenVMS Alpha layered products licensee1                    units required for the system.p  I                                                  (continued on next page)E  I                                         License Management Supplement C-5V E  K           Overview      E           Table C-1 (Cont.) License Unit Requirement Table (LURT)       E           System_Marketing_Model______A___________H__________________f  5           DEC 7000-620                600        1250   5           DEC 7000-630                700        1250e  5           DEC 7000-640                800        1250   5           DEC 10000-610               800        1250   5           DEC 10000-620               900        1300k  5           DEC 10000-630              1000        1300   5           DEC 10000-640              1100        1300y    D,        Key to License Type Codes and Values:/           _____________________________________ D             A - The number of OpenVMS Alpha operating system licenseB                 units (Unlimited or Base) required for the system.E             B through G - Omitted from table; reserved for future usehD             H - The number of OpenVMS Alpha layered products licenseI                 units required for the system.                           s                                          %     C-6 License Management Supplement            I                                   License Management Facility (LMF) Notese    I         _________________________________________________________________e  /         License Management Facility (LMF) Notes   C               The following list addresses some common concerns andwH               questions regarding the License Management Facility (LMF).D               For full explanations of these issues, see the OpenVMS0               License Management Utility Manual.  I               o  If you do not have a valid OpenVMS Alpha license that is H                  registered and activated, the system displays a warningG                  message as part of system startup and restricts systemi5                  use to the operator's console, OPA0.w  E               o  If a checksum error is displayed when you register aoH                  license, check all the fields of data that you entered,/                  including the checksum itself.t  C               o  After your PAKs are registered, they are activatedsG                  (loaded) automatically as part of each system startup.   ?               o  If an OpenVMS Alpha license is registered withpD                  insufficient license units, the system displays theF                  following message when the user (process) attempts to                  log in:  P        %LICENSE-F-EXCEEDED, licensed product has exceeded current license limits  I                  Users can always log in to the operator's console, OPA0,o                  however.   D               o  The default LICENSE database is located in the fileE                  SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB. You can move the D                  database, although Digital does not recommend doingE                  so. If you move the database, you must either definenD                  the logical name LMF$LICENSE at the system level toH                  point to the new database or use the /DATABASE=filespecA                  qualifier with all LICENSE commands. To redirectrE                  LMF to another database location on a more permanentnG                  basis, add the following line to the command procedureu,                  SYS$MANAGER:SYLOGICALS.COM:  N                  $ DEFINE/SYSTEM LMF$LICENSE device:[directory]LMF$LICENSE.LDB  B                  If you specify a device other than SYS$SYSDEVICE,@                  you must also mount the specified disk from the2                  SYLOGICALS.COM command procedure.  I                                         License Management Supplement C-7            +     License Management Facility (LMF) Notesa      ?           o  Each OpenVMS Alpha find license is restricted to anE              single node for permanent PAKs. You must assign a System C              Communications Services (SCS) name to the license when D              you register with the VMSLICENSE.COM command procedure,A              or you must enter a LICENSE MODIFY/INCLUDE=node-name14              command after you register the license.  B              Note: The SCS node name is not necessarily the DECnetB              node name. SCSNODE is a system parameter; it can be a2              maximum of six alphabetic characters.       RESTRICTIONS<           Availability Product Authorization Keys (PAKs) are>           available for the OpenVMS Alpha operating system. AnA           OpenVMS Alpha PAK is identified by the keyword ALPHA iniB           the PAK's option field. Note the following restrictions:  E           o  PAKs having the ALPHA option can be loaded and used only C              on Alpha computers. However, they can safely reside in B              a license database (LDB) shared by both VAX and Alpha              systems.e  E           o  Because the LMF for Alpha systems is capable of handling @              all types of PAKs, including those for VAX systems,E              Digital recommends that you perform your LDB tasks usingl              the Alpha LMF.   A           o  Availability PAKs for VAX systems (availability PAKs =              without the ALPHA option) will not load on AlphalA              systems. Only those availability PAKs containing thea5              ALPHA option will load on Alpha systems.f  <           o  Other PAK types such as activity (also known asB              concurrent or n-user) and personal use (identified byA              the RESERVE_UNITS option) work on both VAX and Alpha               systems.   B           o  Avoid using the following LICENSE commands from a VAX9              system on a PAK containing the ALPHA option:i                -  REGISTER                -  DELETE/STATUSB                -  DISABLE                 -  ENABLE  %     C-8 License Management Supplement            I                                   License Management Facility (LMF) Notes(                        -  ISSUED                    -  MOVE                    -  COPY                    -  LIST  A               o  Caution: By default, all Alpha availability PAKsiD                  look disabled to a VAX system. Never use the DELETEE                  /STATUS=DISABLED command from a VAX system on an LDBoI                  that contains Alpha PAKs. If you do, all Alpha PAKs willa                  be deleted.  A               o  With the exception of the DELETE/STATUS=DISABLEDaH                  command, if you inadvertently use one of the previouslyD                  listed LICENSE commands on an Alpha PAK while usingC                  a VAX system, the PAK and the database will not becI                  adversely affected. Repeat the command using LMF runningeI                  on an Alpha system, and the PAK should return to a valid.                  state.   G               o  If you do not repeat the command using LMF on an Alpha E                  system, the system that you intended to disable willtG                  remain enabled (the system is not otherwise affected).r=                  Only the Alpha LMF can disable an Alpha PAK.t  E                  However, if you attempt to use any of the previously C                  listed commands on a PAK located in an LDB that is I                  shared with a VAX system, the following serious problems                   may result:  E                  -  Because Alpha PAKs look disabled to a VAX system, A                     they are normally ignored at load time by VAX E                     systems. However, if one of the previously listed_E                     commands is entered from a VAX system and the PAK G                     information is not set to a valid state by an Alpha I                     system, there is a chance the VAX system will attempt F                     to load the Alpha PAK. Because the VAX system willI                     be unable to load the PAK, the VAX LMF will report an                      error.  G                  -  Even if a valid VAX PAK for the affected product is I                     in the LDB, it too may not load. In this case, systemt@                     users might be denied access to the product.  I                                         License Management Supplement C-9            +     License Management Facility (LMF) Notes       C              If the PAK cannot be restored to a valid state becausedC              all Alpha systems are inaccessible for any reason, use D              your VAX system to disable the Alpha PAK. This preventsC              your VAX system from attempting to load the Alpha PAK.r       FOR MORE INFORMATIONC           For additional license information, see the release notesd<           and the OpenVMS License Management Utility Manual.                                                                          &     C-10 License Management Supplement                         I                                                                         DaI         _________________________________________________________________i  I                               Preparing to Use OpenVMS Management StationS                                                                            I                           Preparing to Use OpenVMS Management Station D-1l    t           Overview    E     _________________________________________________________________o       Overview         INTRODUCTIOND           This appendix describes how to prepare your OpenVMS systemB           and your PC to run the OpenVMS Management Station serverD           and client software. The information provided includes the           following:  =           o  Preliminary procedures, including the following:l  $              -  Editing system files  B              -  Starting OpenVMS Management Station on other nodes  ?              -  Verifying that you have the proper memory, disk B                 space, media, and the required software to install=                 and run OpenVMS Management Station on your PC   B              -  Creating installation media for PC client software  6           o  Installing the client software on your PC  "           o  Defining DECnet nodes  "           o  Accessing online help  7           o  PATHWORKS installation tips and guideliness       REQUIRED FILES@           During the OpenVMS Version 6.2 installation or upgrade?           procedure, the OpenVMS Management Station software is B           automatically installed on your OpenVMS system disk whenB           you accept all the default values. If you did not acceptD           the default values and did not manually select the OpenVMSC           Management Station component, you must add those files to E           your OpenVMS system disk before you follow the instructions_A           in this appendix. Use the OpenVMS Version 6.2 operating C           system CD-ROM and the DCL command PRODUCT RECONFIGURE VMS1E           to add the OpenVMS Management Station files to your system.0        3     D-2 Preparing to Use OpenVMS Management Statione 0  4      I                                                                  Overview4               CHECKLIST G               Use the following checklist as a guide to verify that you D               perform the required tasks described in this appendix:  G               [] Be sure the optional OpenVMS Management Station client4E                  software files are installed on your OpenVMS system.r  C               [] Edit the system startup and shutdown files on your G                  OpenVMS system to start the OpenVMS Management Station                   server.  I               [] Start OpenVMS Management Station on OpenVMS nodes withinnC                  the cluster that you have configured with failover_                  mechanisms.  H               [] Be sure that your PC has at least 8 MB of random-accessF                  memory (RAM) and 6 MB of free disk space and that youD                  have two 3-1/2 inch, high-density floppy diskettes.  F               [] Be sure that your PC is running MS-DOS Version 5.0 orE                  later and Microsoft Windows Version 3.1 or Microsoft 5                  Windows for Workgroups Version 3.11.   F               [] Be sure your PC is running PATHWORKS Version 5.0A (orE                  Version 5.1) for DOS and Windows client software and.H                  that the PATHWORKS file PWSOCK.DLL is available to yourI                  PC. (If necessary, refer to the section titled PATHWORKS53                  Installation Tips and Guidelines.)   @               [] Create the PC installation media (on two floppyE                  diskettes) containing the OpenVMS Management StationS!                  client software.5  G               [] Install the OpenVMS Management Station client softwarel                  on your PC.  H               [] After installing the client software on your PC, defineH                  the DECnet node names and network addresses of primary-@                  server OpenVMS systems that you want to manage.  @               [] Access online help to get started using OpenVMS$                  Management Station.      I                           Preparing to Use OpenVMS Management Station D-30                             I         _________________________________________________________________P  I                                                    Preparing Your Systems5                                                                          I                           Preparing to Use OpenVMS Management Station D-5( C         !     Preparing Your OpenVMS Systemc    E     __________________________________________________________________  !     Preparing Your OpenVMS System          INTRODUCTION@           During the OpenVMS Version 6.2 installation or upgradeD           procedure, the OpenVMS Management Station server files areD           automatically installed on your OpenVMS system disk. AfterC           the installation or upgrade is complete, you must preparedE           your OpenVMS system to run the server software so that yournE           system can properly interact with the PC running the client            software.   :           This section includes the following information:  E           o  A list of the OpenVMS Management Station files installed $              on your OpenVMS system.  ?           o  A procedure for editing the system files to enablerA              automatic startup and shutdown of OpenVMS Management2              Station  C           o  A procedure for starting OpenVMS Management Station on (              other nodes in a VMScluster       FILES INSTALLED ON OPENVMSC           The files installed on your OpenVMS system disk followingSC           the OpenVMS Version 6.2 installation or upgrade procedure3           are as follows:5  &           o  SYS$SYSTEM:TNT$SERVER.EXE  (           o  SYS$STARTUP:TNT$STARTUP.COM  )           o  SYS$STARTUP:TNT$SHUTDOWN.COM   !           o  SYS$TEST:TNT$IVP.COM   7           o  SYS$COMMON:[SYSTEST.TNT]TNT$SERVER_IVP.EXE   *           o  SYS$HELP:TNT010.RELEASE_NOTES  :           This file is created when the server is started:  ,           o  SYS$COMMON:[SYSEXE]TNT$UADB.DAT  3     D-6 Preparing to Use OpenVMS Management Station            I                                             Preparing Your OpenVMS System       G               These client software files are installed on your OpenVMS I               system during the installation or upgrade procedure as well H               (or when you later add those files to the system using theI               DCL command PRODUCT RECONFIGURE VMS). These files allow younF               to create the PC installation media (using the procedureG               described later in the section titled Preparing Your PC).   D               Note that after you successfully transfer these clientE               software files from your OpenVMS Alpha system to floppy E               diskettes and install that software on your PC, you canuD               then remove those files from your OpenVMS Alpha systemF               to save disk space. (Use the PRODUCT RECONFIGURE command.               rather than a delete operation.)  4               o  SYS$COMMON:[TNT.CLIENT]DISKIMAG.EXE  4               o  SYS$COMMON:[TNT.CLIENT]TNTCLID1.IMG  4               o  SYS$COMMON:[TNT.CLIENT]TNTCLID2.IMG           EDITING SYSTEM FILESD               You must edit the system startup and shutdown files onF               your OpenVMS system to provide for automatic startup andH               shutdown of OpenVMS Management Station when your system is               rebooted.   4               To edit the files, follow these steps:                                    I                           Preparing to Use OpenVMS Management Station D-7  0         !     Preparing Your OpenVMS Systemd    E           ___________________________________________________________ E           Step_____Action____________________________________________n  ;           1        Add the command line that starts OpenVMS A                    Management Station to the system startup file, 1                    SYS$MANAGER:SYSTARTUP_VMS.COM.l  B                    The following example shows the network startupB                    command line followed by the OpenVMS Management0                    Station startup command line:  .                    $ @SYS$MANAGER:STARTNET.COM                         .                          ._                         ._1                    $ @SYS$STARTUP:TNT$STARTUP.COM   @                    Note: OpenVMS Management Station cannot startB                    until after the network has started. Therefore,@                    you must position this new command line afterD                    the line that invokes the network startup command                    procedure.o  ?           2        Add the following command line to the system <                    shutdown file, SYS$MANAGER:SYSHUTDWN.COM:  F                    $ @SYS$STARTUP:TNT$SHUTDOWN.COM                    E           ___________________________________________________________   6     STARTING OPENVMS MANAGEMENT STATION ON OTHER NODESD           If you plan to run OpenVMS Management Station on more thanD           one node in a VMScluster without rebooting, you must start?           the software on those nodes by entering the following *           command from the SYSTEM account:  (           $ @SYS$STARTUP:TNT$STARTUP.COM  A           If you are performing an upgrade or an installation andn?           OpenVMS Management Station is already running on youriD           cluster, add the RESTART parameter to the startup command,           as follows:-  0           $ @SYS$STARTUP:TNT$STARTUP.COM RESTART        3     D-8 Preparing to Use OpenVMS Management Station  r  r      I                                                         Preparing Your PCC    I         _________________________________________________________________I           Preparing Your PC              INTRODUCTIOND               During the OpenVMS Version 6.2 installation or upgradeD               procedure, you selected the OpenVMS Management StationC               client software files to be installed on your OpenVMStH               system disk (or you added them later using the DCL commandD               PRODUCT RECONFIGURE VMS). After you have prepared yourF               OpenVMS system to run the server software, you must next9               prepare your PC to run the client software.   >               This section includes the following information:  3               o  Preliminary tasks and requirements   E               o  A procedure for creating installation media from the E                  client software installed on the OpenVMS system disk   &         REQUIRED MEMORY AND DISK SPACEE               Your PC requires 8 MB of random-access memory (RAM) and G               6 MB of free disk space to install the OpenVMS Management &               Station client software.  E               To determine the amount of memory available on your PC,s?               enter the following command at the MS-DOS prompt:o                 C:\> mem  G               To determine the amount of available free disk space, you C               can enter the following command at the MS-DOS prompt:c                 C:\> dir  
         MEDIA E               You need two 3-1/2, inch high-density floppy diskettes, I               which have to be formatted. You will use those diskettes tom/               create the PC installation media.I            I                           Preparing to Use OpenVMS Management Station D-9l o  h           Preparing Your PCt           REQUIRED SOFTWAREhD           Table D-1 describes the software that must be installed on?           your PC before installing OpenVMS Management Station.a  G           Table D-1 Prerequisite and Optional Software                 o  E           Prerequisite_Products______Purpose_________________________b  5           MS-DOS Version 5.0 or      Operating systeme           later   9           Microsoft Windows Version  Windowing capability            3.1 or           Microsoft Windows for !           Workgroups Version 3.11r  C           PATHWORKS V5.0A for DOS    ManageWORKS user interface anda6           and Windows (or V5.1)      network transportH           client software                                               E           ___________________________________________________________n  !     PATHWORKS CLIENT REQUIREMENTSl;           Note the following PATHWORKS client requirements:   7           o  Your system must be configured for DECnet.e  B           o  If you have any version of the PATHWORKS client otherC              than Version 5.0A or Version 5.1 installed on your PC, ?              it is not supported by OpenVMS Management Station.   D              Refer to the section titled PATHWORKS Installation TipsE              and Guidelines to help you quickly install the PATHWORKS E              Version 5.0A for DOS and Windows (or Version 5.1) client               software.  C           o  OpenVMS Management Station requires that the PATHWORKS C              file PWSOCK.DLL be available to your PC. PWSOCK.DLL is-D              installed as part of the Socket Library Files option of7              the PATHWORKS Network Utilities component.   D              The error message "Cannot Find PWSOCK.DLL" is displayedE              when you run OpenVMS Management Station if PWSOCK.DLL iso*              not available to your system.      4     D-10 Preparing to Use OpenVMS Management Station h  x      I                                                         Preparing Your PCe      H                  Refer to the section titled PATHWORKS Installation TipsH                  and Guidelines for instructions on how to configure theH                  Socket Library Files option to make the PWSOCK.DLL fileG                  available (see the subsection titled Configuring Usingl                  Windows).  '         CREATING THE INSTALLATION MEDIAoI               Create the PC installation media using the following steps.,  2               1. Open an MS-DOS window on your PC.  D               2. At the MS-DOS prompt, use the NFT utility on the PCF                  to copy the files to a temporary directory on your PCH                  from the OpenVMS system on which you have installed theI                  OpenVMS Management Station software. Enter the followings                  command:e  Q C:\> NFT COPY/BLOCK node"username password"::SYS$COMMON:[TNT.CLIENT]*.* \temp-dira  B                  where node, username, and password are the accessB                  control information for an account on the OpenVMSB                  system, and temp-dir is the name of the temporary                  directory.V  F                 ________________________ Note ________________________  B                 If a DECnet node is not defined in your PC networkE                 database, refer to the section titled Defining DECnet.                 Nodes.  F                 ______________________________________________________  H               3. Insert a formatted floppy disk in the 3-1/2 inch floppyF                  disk drive (A in this example). At the MS-DOS prompt,3                  type the following MS-DOS command:   B                  C:\> \temp-dir\DISKIMAG \temp-dir\TNTCLID1.IMG a:  J                  where temp-dir is the temporary directory used in step 2.  H                  When the DISKIMAG program returns to the MS-DOS prompt,D                  remove the floppy disk and label it "Disk 1-Setup".  H               4. Insert a formatted floppy disk in the 3-1/2 inch floppyE                  disk drive. At the MS-DOS prompt, type the followingt                  command:P  I                          Preparing to Use OpenVMS Management Station D-11n e  h           Preparing Your PCn      >              C:\> \temp-dir\DISKIMAG \temp-dir\TNTCLID2.IMG a:  C              where temp-dir is the temporary directory used in stepM              2.e  D              When the DISKIMAG program returns to the MS-DOS prompt,:              remove the floppy disk and label it "Disk 2".  A           5. You can delete the files DISKIMAG.EXE, TNTCLID1.IMG, E              and TNTCLID2.IMG from temp-dir after creating the floppy               disks.   B           You can now proceed with the installation of the OpenVMS0           Management Station PC client software.                                                              4     D-12 Preparing to Use OpenVMS Management Station                             I         _________________________________________________________________   L         Installing the OpenVMS Management Station Client Software on Your PC                                                                        I                          Preparing to Use OpenVMS Management Station D-13- d  n           Overview    E     _________________________________________________________________        Overview  :           This section provides the following information:  D           o  How to install the OpenVMS Management Station client on              a PCS  ?           o  How to recover from errors during the installationo  >           o  How to define DECnet nodes after the installation  E           o  The names of the files that are created on your PC afteri              the installationP  C           o  How to access online help to get started using OpenVMS               Management Station2                                                        4     D-14 Preparing to Use OpenVMS Management Station l  n      I                                            Installing the Client Softwarel    I         _________________________________________________________________e  &         Installing the Client Software             INSTALLATION PROCEDUREF               Follow these steps to install OpenVMS Management StationI               client on your PC. (Note that this procedure takes about 10                minutes.)   I               ___________________________________________________________nI               Step________Action_________________________________________e  :               1           Start your PC as you usually do.  B               2           Insert disk 1 in your floppy disk drive.  H               3           Enter the Windows environment and click on the/                           Program Manager icon.d  H               4           In the Menu bar of the Program Manager programH                           group, click on File, and then choose Run from-                           the pull-down menu.i  =                           Result: The Run dialog box appears.   6               5           In the Run dialog box, type:  &                           a:\SETUP.EXE  H                           where a: is the name of the floppy disk drive.  =               6           Click on the OK button to start the '                           installation.   E                           Result: A dialog box containing the messagemF                           "Initializing setup, please wait..." appearsB                           and is then replaced by a window labeled(                           OpenVMS Setup.              I                          Preparing to Use OpenVMS Management Station D-15            "     Installing the Client Software    E           ___________________________________________________________ E           Step________Action_________________________________________   D           7           To proceed with the installation, click on the&                       Continue button.  E                       Note: You can stop the installation at any timea5                       by clicking on the Exit button.a  @                       As the installation progresses, the system=                       displays the names of the files as theya?                       are copied, and a copy bar indicates whatlB                       percentage of the installation is done. AlsoA                       displayed is a reminder to read the OpenVMS C                       Management Station Read Me file for important "                       information.  D           8           When you are prompted by a dialog box message,B                       remove disk 1 from the disk drive and insert*                       disk 2. Click on OK.  C                       Result: When the copy bar shows that that all_A                       the files are copied, a dialog box displays ?                       a message indicating the installation hasmF                       completed_successfully.                         E           ___________________________________________________________t       RECOVERING FROM ERRORSB           If an error occurs during installation, you will receiveC           an error message describing the problem. This informationsC           can help you determine the cause of the problem. An erroriA           can occur during the installation if one or more of the %           following conditions exist:o  7           o  The operating system version is incorrect.   <           o  The prerequisite software version is incorrect.  ;           o  Disk space and memory necessary for successfulh)              installation are inadequate.e              4     D-16 Preparing to Use OpenVMS Management Station    s      I                                                     Defining DECnet NodesS    I         _________________________________________________________________            Defining DECnet Nodesg             INTRODUCTIONF               After installing the client software on your PC, use theE               MS-DOS Network Control Program (NCP) utility on your PCaF               to define the DECnet node names and network addresses ofE               primary-server OpenVMS systems that you want to manage. I               OpenVMS Management Station connects your PC to the primary-pH               server system and then routes management operations to theF               target systems. You can define multiple primary servers.  F                 ________________________ Note ________________________  A                 Failure to access the NCP utility from the MS-DOS 9                 prompt can result in connection problems.e  D                 By accessing the NCP utility from the MS-DOS prompt,B                 you define DECnet node names and network addressesE                 in both DECnet Phase IV and DECnet Phase V databases.OC                 If you access the NCP utility from Windows, data isn2                 defined only in Phase V databases.  F                 ______________________________________________________  +         PROCEDURE FOR DEFINING DECNET NODESe8               Follow these steps to define DECnet nodes:  I               ___________________________________________________________tI               Step________Action_________________________________________   I               1           At the MS-DOS prompt, invoke the NCP utility asl"                           follows:  "                           C:\> NCP  I               2           At the NCP> prompt, type the following command:   :                           NCP> DEFINE NODE addrs NAME name  G                           where addrs is the DECnet address and name isd/                           the DECnet node name.   "                           Example:  <                           NCP> DEFINE NODE 19.208 NAME ISTAR  I                          Preparing to Use OpenVMS Management Station D-17D N  Y           Defining DECnet Nodest    E           ___________________________________________________________sE           Step________Action_________________________________________p  C           3           At the NCP prompt, type EXIT and press Return G                       to exit the operation.                            E           ___________________________________________________________n                                                                                  4     D-18 Preparing to Use OpenVMS Management Station _  _      I                                                     Defining DECnet Nodes                FILES CREATED ON THE PCtB               The following files (with their directory names) areD               created on your PC when the OpenVMS Management Station+               client software is installed:o  2               o  PATHWORKS directory (usually \PW)                    -  VMSACNT.DLLt                    -  VMSCLU.DLL                     -  VMSINFRA.DLL                    -  VMSMGMT.DLL                      -  VMSMSCRL.DLL                    -  VMSNODE.DLL                      -  VMSTIMEL.DLL                     -  VMSUAOMM.DLL                    -  ACCOUNT.HLPt                    -  DOMAIN.HLP                    -  MANAGE.HLP                    -  README.WRI  5               o  Windows directory (usually \WINDOWS)                     -  XTIDNW.DLL                    -  XTILIB.DLL  C               o  Window systems directory (usually \WINDOWS\SYSTEM)a                    -  CTL3DV2.DLL           I                          Preparing to Use OpenVMS Management Station D-19: $  T           Getting Started     E     _________________________________________________________________        Getting StartedN         INTRODUCTION@           All information about getting started, setting up, andA           using OpenVMS Management Station is contained in online >           help and the OpenVMS Management Station Overview and           Release Notes.         ACCESSING ONLINE HELPnE           Follow these steps to access the OpenVMS Management Stationp           online help:  E           ___________________________________________________________nE           Step_____Action____________________________________________u  B           1        Open the PATHWORKS Windows Applications program                    group.   @           2        Click on the OpenVMS Management Help icon forF                    instructions on how to get started.                E           ____________________________________________________________                                            4     D-20 Preparing to Use OpenVMS Management Station r  n                        I         _________________________________________________________________   I                                PATHWORKS Installation Tips and Guidelines                                                                           I                          Preparing to Use OpenVMS Management Station D-21  n              Overview    E     _________________________________________________________________n       Overview  ?           If you already have the PATHWORKS for DOS and Windows A           client software installed on your PC, you can disregard            this entire section.  A           If you are installing the PATHWORKS for DOS and WindowsoA           client software on your PC because the PATHWORKS clientEB           software is a requirement for OpenVMS Management Station;           (that is, you are not using PATHWORKS to manage ae@           local area network of PCs), you may find the following2           installation tips and guidelines useful.  =           For complete installation instructions and detailed-:           information on PATHWORKS, refer to the PATHWORKS           documentation.       REQUIRED DISK SPACE D           PATHWORKS for DOS and Windows client software requirementsC           for free disk space are different during installation andt?           after installation. Files created during installationc@           can later be deleted. Table D-2 summarizes the storage           requirements.l  F           Table D-2 Disk Space Requirements                             !                            During E           Kit______________Installation_____After_Installation_______a  0           PATHWORKS for    Up to 30 MB      7 MB           DOS and WindowsoE           client                                                     qE           ___________________________________________________________e  $     ABOUT INSTALLING AND CONFIGURINGB           You use both MS-DOS and Windows to install and configure(           the PATHWORKS Client software:  6           1. Install the client software using MS-DOS.  D           2. After installation, configure the client software using              Windows.       4     D-22 Preparing to Use OpenVMS Management Station w  o      H                                                  Installing Using MS-DOS    I         __________________________________________________________________           Installing Using MS-DOSL  >               Exit Windows before you begin this installation.  A               1. The client software installation procedure wantsnC                  to install the software to the root directory of aoI                  "substituted" hard disk. Create a substituted hard drive G                  by typing the following commands at the MS-DOS prompt. E                  Note that the example reflects the PATHWORKS Version I                  5.0A for DOS and Windows client software; Version 5.1 is                    also supported.  %                  C:\> mkdir c:\pwv50af(                  C:\> subst x: c:\pwv50a  H                  where x: is the name of an unused MS-DOS drive. (If youF                  have a single hard disk, G is usually a good choice.)  D                  C is the name of a local drive that meets the space                  requirements.  F               2. Insert the LAN Manager setup disk in your PC's floppy"                  drive. Then type:                    a:setup  F                  Note that A is the MS-DOS drive letter for the floppy                  drive.x  E               3. Choose the Install Kit option from the Setup window.   F               4. To install the software to the substituted hard driveA                  created in step 1 (G: was suggested), choose the B                  appropriate drive from the Select Drive list box.F                  (Scroll through the list box if the drive name is not&                  immediately visible.)                    Click on OK.I  G               5. When prompted, insert disk 1 into drive A and click onu                  OK.  E                  A working dialog box displays the names of the files D                  as they are copied, and a copy gauge indicates what8                  percentage of the installation is done.  E               6. Insert the LAN Manager setup disk again when you aree2                  prompted. Click on the OK button.  I                          Preparing to Use OpenVMS Management Station D-23o u  n           Installing Using MS-DOSN      B           7. From the PATHWORKS Installation utility window, clickD              on the arrow to the right of the Installing to: option.A              Select the substituted drive from the displayed liste              box.   E           8. From the Install: list box in the PATHWORKS Installation_@              Utility window, you can choose the PATHWORKS clientE              options you want to install. You need only the followingn.              options in the Install: list box.  $                 DECnet and Utilities                 ManageWORKS_!                 Network Utilitieso"                 PATHWORKS Tutorial)                 PATHWORKS Windows Network   =              Remove unneeded options from the Install list byoC              clicking on an option, and then clicking on the Remove\=              button to move the selected option to the Do Nott              Install: list box.e  >           9. Verify your selection of options and click on OK.  A           10.An Installation Starting dialog box is displayed and"E              you are asked whether you want to go back and read help.e              Choose NO.   E           11.When you are prompted, insert the necessary floppy disks %              to install the software.   D              A working dialog box displays the names of the files as              they are copied.   E           12.When the installation process is complete, you are asked C              whether you want to configure the Workstation Manager;               choose NO.e  =           13.An Installation Complete dialog box displays the               following message:   3              Exiting PATHWORKS Installation UtilityI  $              Click on the OK button.  C           14.At this point, the installation utility returns to the C              initial Setup window. Click on the Exit option to quite0              the PATHWORKS Installation utility.  4     D-24 Preparing to Use OpenVMS Management Station           I                                                 Configuring Using Windows     I         __________________________________________________________________  !         Configuring Using WindowsV  C               Use the following steps to configure PATHWORKS client                software:   E               1. Start Windows and choose Run from the File pull-down E                  menu on the Program Manager menu bar. In the Command_.                  Line box, type the following:  !                  x:\pcapp\pwsetup   F                  where x: is the substituted drive that you created in+                  step 1 (G: was suggested).n  B                  Click on the OK button. This starts the PATHWORKS'                  Configuration utility.   D               2. Click on the OK button in the Please Enter SoftwareF                  Destination box to signify that the displayed default%                  location is correct.n  D                  A PATHWORKS Configuration Warning box is displayed.D                  Click on the OK button to indicate that you want to.                  create the default directory.  D               3. When you are prompted, verify the substituted driveG                  letter you used when you installed the client software_-                  under MS-DOS by clicking OK.   F               4. Choose the Express option from the displayed Select a/                  Configuration Option list box.   E               5. In the Express: Select a Workstation Template dialog G                  box, choose the highlighted Blank template by clicking_"                  on the OK button.  C               6. In the Customize: Modify Workstation Configuration ;                  template, choose only the following items:   &                  o  PATHWORKS Services  /                  o  Network Adapter Informationn  G                  Deselect the other items. Then click on the OK button.g  F               7. You are prompted to select the following tasks (thoseH                  listed in step 4 of the MS-DOS installation procedure):  (                     DECnet and Utilities                     ManageWORKS   I                          Preparing to Use OpenVMS Management Station D-25                 Configuring Using Windows       !                 Network Utilities "                 PATHWORKS Tutorial)                 PATHWORKS Windows Network   B              Click on each option. Then click on the Add button toA              move each option to the Run on Workstation list box.l  B           8. Choose the DECnet and Utilities option. Then click on              the Detail button.   E           9. From the displayed list box, double-click on the Network ?              File Transfer option. Then click on the OK button.   C           10.A Customize: Select PATHWORKS Services for Workstation B              dialog box is displayed. Choose the Network Utilities4              option, and click on the Detail button.  D           11.From the displayed list box, double-click on the Socket?              Library Files option. Then click on the OK button.   D           12.From the displayed Customize: Select PATHWORKS Services@              for Workstation dialog box, click on the OK button.  @           13.Select the Ethernet adapter installed in your PC byB              clicking on the appropriate adapter description. Then              click on OK.   B           14.When you are prompted, enter the DECnet node name andA              DECnet network address. Do not enter the server node +              name and address. Click on OK.a  B           15.In the Enter Windows Directory dialog box, accept the<              displayed default by clicking on the OK button.  @           16.In the Customize: Save Template to Disk dialog box,?              choose a name for the startup template (any string @              of characters is permitted), along with an optional8              description. Then click on the Save button.  >           17.A displayed message asks whether you want to have>              the network started automatically via an entry in              AUTOEXEC.BAT.  A              Select YES. If you start up Windows in AUTOEXEC.BAT,_A              examine AUTOEXEC.BAT after the configuration utility B              exits to ensure that the call to STARTNET.BAT appears$              before the WIN command.  4     D-26 Preparing to Use OpenVMS Management Station r  e      I                                                 Configuring Using Windows       G               18.In the displayed Customize: PROTOCOL.INI Editor dialogTB                  box, click on the OK button to accept the default                  options.   H                  A copy gauge displays the progress of the installation.  F               19.Select the OK option to exit the displayed Customize:4                  Configuration Completed dialog box.  =               20.Select the Exit option to exit the PATHWORKS '                  Configuration utility._  G                 ______________________ Important ______________________e  F                 You must exit Windows and restart your computer beforeD                 you install the OpenVMS Management Station software.  F                 ______________________________________________________                                                      I                          Preparing to Use OpenVMS Management Station D-27e S  i           Configuring Using Windows            STARTING WINDOWSD           The first time Windows starts after this installation, you           see the message:  (           Could not load Windows Network  D           Click on the "Disable this warning" button, and then click           on the OK button.        DELETING A DIRECTORY@           Now that you have successfully installed the PATHWORKSB           Client software and have run the PATHWORKS ConfigurationA           utility, you can delete the PWV50A directory, which you <           created in step 1 when you installed using MS-DOS.                                                              4     D-28 Preparing to Use OpenVMS Management Station                             I         _________________________________________________________________I  I                                                                  Glossary       B               This glossary defines key terms in the context of an2               OpenVMS Alpha computing environment.                 boot, bootstrap   G               The process of loading system software into a processor's                main memory.                 boot server   H               An Alpha computer that is part of a local area VMScluster.I               The boot server is a combination of a MOP server and a disk F               server for the satellite system disk. See also satellite               node.                   CI only VMScluster  ?               A computer system consisting of a number of AlphaFG               computers. It uses only the computer interconnect, or CI,pG               to communicate with other Alpha computers in the cluster. 9               These computers share a single file system._                 CI  G               A type of I/O subsystem. It links computers to each other >               and to HSx devices (for example, an HSC or HSD).                 device name   H               The name used to identify a device on the system. A deviceI               name indicates the device code, controller designation, and                unit number.    I                                                                Glossary-1                               disk server   B           A computer that is part of a local area VMScluster. ThisC           computer provides an access path to CI, DSSI, and locallya@           connected disks for other computers that do not have a           direct connection.             HSx device  D           A self-contained, intelligent, mass storage subsystem (forE           example, an HSC or HSD) that lets computers in a VMScluster-"           environment share disks.             HSx drive   @           Any disk or tape drive connected to an HSx device (forD           example, an HSC or HSD). A system disk on an HSx drive canE           be shared by several computers in a VMScluster environment.              InfoServer  B           A general-purpose disk storage server that allows you toB           use the operating system CD-ROM to install the operatingE           system on remote client systems connected to the same local            area network (LAN).              local area VMScluster   B           A configuration consisting of one or more computers that>           act as a MOP server and disk server, and a number ofB           low-end computers that act as satellite nodes. The localA           area network (LAN) connects all of the computers. Theseu/           computers share a single file system.n             local drivei  C           A drive, such as an RRD42 CD-ROM drive, that is connectedtA           directly to an Alpha computer. If you have a standaloneIC           Alpha computer, it is likely that all drives connected ton&           the system are local drives.             media_  B           Any packaging agent capable of storing computer softwareB           (for example, CD-ROMs, magnetic tapes, floppy diskettes,+           disk packs, and tape cartridges).p       Glossary-2                   +               mixed interconnect VMSclustere  G               A computer system consisting of a number of computers. It F               uses CI, Ethernet, and DSSI adapters to communicate with-               other computers in the cluster.                  MOP server  E               A computer system running DECnet for OpenVMS Alpha that C               downline loads VMScluster satellites using the DECnet .               Maintenance Operations Protocol.                 satellite node  C               A computer that is part of a local area VMScluster. A E               satellite node is downline loaded from a MOP server and2G               then boots remotely from the system disk served by a disk_2               server in the local area VMScluster.                 scratch disk  C               A blank disk or a disk with files you no longer need.                  source drive  I               The drive that holds the distribution kit during an upgradeOH               or installation, or the drive from which you restore files               to a target disk.t                 standalone systema  =               A computer system with only one Alpha computer.                  system disk   F               The disk that contains or will contain the OpenVMS Alpha               operating system.                  target drive  G               The drive that holds the system disk during an upgrade ortF               installation, or the drive you designate when backing up               the system disk.                 UETP  D               User Environment Test Package. A software package thatG               tests all the standard peripheral devices on your system,cB               various commands and operating system functions, theD               system's multiuser capability, DECnet for OpenVMS, and)               the VMScluster environment.   I                                                                Glossary-3t a  n                          VMScluster environment  C           A computer system consisting of a number of Alpha and VAX E           computers. There are four types of VMScluster environments:_A           CI only, DSSI only, local area, and mixed-interconnect.D                                                                                     Glossary-4 H  K                            F      _________________________________________________________________  F                                                                  Index      ?      A                                 Alpha computers (cont'd) ;      _______________________________     booting with PMAZC A      Accounts                               TURBOchannel adapter,_0        creating after installation,         A-17C          4-4                             booting with XDELTA,  A-14lF        setting up after an               cancelling boot device,  A-337          installation,  4-6              halting,  A-40tB      Adding files                        performing conversational6        after installation, 4-13             boot, A-10C        after upgrade, 8-14               setting boot device,  A-32tA      AGEN$PARAMS.REPORT,  4-21           setting boot parameters, 0      Allocation class                       A-34  F        See also ALLOCLASS parameter      setting for automatic booting2        determining, 2-3                     , A-30C      ALLOCLASS parameter,  2-3           showing boot device,  A-32u=        supplying during VMScluster       shutting down,  A-42 D          installation,  3-36             troubleshooting procedures,0      Alpha computers                        A-47C        booting failure, A-46           ANALYZE/CRASH command,  A-44 E        booting from a different        ANALYZE/DISK_STRUCTURE utility <          directory,  A-16                error message,  5-8F        booting in an emergency,          using before an upgrade,  5-8.          A-21                          APB.EXEE        booting with minimum startup,     and Writeboot utility,  A-37 5          A-13                          AUTOGEN,  4-21 F        booting with PMAD                 running after an installation2          TURBOchannel adapter,              , 4-21B          A-20                            running after an upgrade,0        booting with PMAZB                   8-21:          TURBOchannel adapter,           running at end of>          A-17                               installation, 3-38    F                                                                Index-1    t              7                                        Booting problems >     B______________________________     fixing by booting with  D     Backing up the system disk,            default parameter values,/        1-8, 4-18, 5-7, 8-19, A-4,          A-21D5        A-7, B-2                        Bugcheck, A-47          in a shadow set,  B-11F       without booting the CD-ROM,      C______________________________  0          B-11                          Checklist?     BACKUP command,  B-3                postinstallation,  4-23x?     Boot block                          postupgrade,  8-22, D-3s9       writing,  A-37                    preupgrade,  5-11 ;     Boot command                       Cluster group numbero@       qualifiers for XDELTA,  A-14      rules for creating,  2-57     Booting                            Cluster password @       automatic,  A-30                  rules for creating,  2-57       cancelling boot device,  A-33    Cluster upgradesd?       conversational,  A-10             See Concurrent upgradest<       failure,  A-46                    See Rolling upgrades!       from a different directory,b=          A-16                           See Upgrade procedureIB       from the InfoServer,  3-7,       CLUSTER_SIZE parameter, B-79          7-4, A-5                      Command proceduresiD       in an emergency,  A-21            checking after upgrade,  8-9B          with default system           Concurrent upgrades, 6-4 to,             parameters, A-21             6-5A          without startup and login      required operating system 7             procedures, A-23               version, 6-4s:          without the User               restrictions,  6-4=             Authorization File,        CONTINUE command, A-11e;             A-24                       Crash commands, A-43 C       setting boot device,  A-32       Creating a system disk, 3-11d3       setting boot parameters,         Ctrl/T, A-47 B          A-34                          Customizing the system, 4-6  (       showing boot device,  A-32       DF       with alternate TURBOchannel      _______________________________?          adapter, A-20                 DEC 3000 Alpha computersPA       with minimum startup,  A-13       booting over the network, /       with PMAZB TURBOchannel,             A-19 >          A-17                           booting with alternate@       with PMAZC TURBOchannel,             TURBOchannel adapter,/          A-17                              A-20 :       with XDELTA,  A-14                booting with PMAZB@                                            TURBOchannel adapter,/                                            A-17        Index-2  t  P                        DEC 3000 Alpha computersI           (cont'd)                        E______________________________u  E          booting with PMAZC               Editing startup files,  4-6 B             TURBOchannel adapter,         Emergency system startup?             A-17                            with default system ?         DECnet for OpenVMS Alpha              parameters,  A-21tE          configuring after an               without startup and logini?             installation,  4-7                procedures,  A-23rA          ignoring during startup,  4-7      without the UAF, A-24 0          registering license after        Errors?             installation,  4-3              cluster hang duringlG          running with DECwindows,  4-7        preupgrade shutdown,  6-9tA         DECnet node address, 2-3            running ANALYZE/DISK_ =          providing during installation        STRUCTURE,  5-8 8             ,  3-35                       EXPECTED_VOTES:         DECnet node name, 2-3               parameter, 8-7          possible values,  3-34 I          providing during installation    F______________________________eD             ,  3-34                       Factory installed software6         Decompressing system libraries       (FIS), xvC           ,  4-9, 8-10                    Feedback on documentationeG         DECW$IGNORE_DECNET logical          sending comments to Digital ;           name,  4-7                          writers,  iiis7         Default system parameters         FIELD account H          booting with,  A-21                creating after installation,1         Digital writers                       4-4a/          sending comments to,  iii        Filesd2         Disk space                          addingG          amount needed for upgrade,            after installation, 4-13 B             5-9                                after upgrade, 8-144          amount needed to decompress        removingG             libraries,  8-10                   after installation, 4-13oB          amount needed to decompress           after upgrade, 8-14"             system libraries,  4-9I         Documentation                     H______________________________ C          sending comments to Digital      Halting the system,  A-40t2             writers,  iii                 Hardware:         Dump file                           supported, D-9:          checking size,  8-7              Hardware problem<          modifying size,  8-6               diagnosing, A-46  4                                           HSx device;                                             definition, 1-2k<                                             specifying, 3-32  I                                                                   Index-3O    v              B                                        LIBDECOMP.COM (procedure toE     I______________________________      decompress system libraries)c  6     InfoServer                           ,  4-10, 8-10A       booting,  3-7, 7-4, A-5           running after an upgrade, /       losing connection,  3-9, 7-6         8-10w0     INITIALIZE command,  A-31          Libraries>     Installation                        decompressing after an<       See also Postinstallation            installation, 4-9B          tasks, Preinstallation        LICENSE (License Management1          tasks                           utility) E       booting system disk after         example of registration,  C-2 <          transferring required save     license registration9          set, 3-32                         procedure, C-2 B       information needed for            using during installation,/          VMScluster, 2-2                   3-21nB       of layered products,  3-28,      License Management Facility4          4-15, 7-15                      (LMF),  C-7?       rebooting system,  3-40           restrictions,  C-8, C-9tE       recording,  1-4                  License Unit Requirement Table 5       registering licenses,  3-19        (LURT),  C-2e/       registering OpenVMS Alpha        Licenses   8          license, 3-40                  See also ProductB       running AUTOGEN,  3-38               Authorization Key (PAK)E       setting passwords,  3-14          registering after an upgrade,t.       specifying VMScluster                8-59          configuration, 3-34            registering after <       stages of,  3-2                      installation, 4-3:       using the POLYCENTER Software     registering during=          Installation utility, 1-8         installation, 3-19O*                                        Log>     L______________________________     for installation,  1-41     Layered products                   Logging ind<       effect of upgrade on,  5-4,       when errors in loginC          8-16                              procedures prevent, A-23_>       installing after OpenVMS          when errors in startupC          Alpha installation, 4-15          procedures prevent, A-23a@       installing during OpenVMS         when forgotten passwords8          Alpha installation, 3-28          prevent, A-244       installing during OpenVMS        Logical names;          Alpha upgrade, 7-15            UAFALTERNATE,  A-24 ?                                        Login command proceduresi>                                         booting without,  A-23D                                         when errors prevent you from;                                            logging in, A-23P       Index-4u i                 ;                                           Password (cont'd) H         M______________________________     setting during installation,  2         Minimum startup, A-13                 3-14D         Mixed-architecture cluster,       PMAZB TURBOchannel adapter@           6-6                               booting system, A-17D         Mixed-version cluster, 6-2,       PMAZC TURBOchannel adapter@           6-7                               booting system, A-17=         MODPARAMS.DAT (parameter file)    POLYCENTER SoftwaretA           ,  4-21, 8-21                      Installation utility D          modifying for cluster,  8-7        installing the operating:          modifying for single system,         system,  1-8C             8-7                             upgrading the operating :         Monitoring Performance History        system,  1-8F          installing,  4-17, 8-18          Postinstallation tasks,  4-1F                                             adding and removing files,2         N______________________________       4-13H         NETCONFIG.COM procedure             adjusting system parameters,1          running after an installation        4-6 G             ,  4-7                          backing up the system disk,i7                                               4-5, 4-18 B         O                                   configuring DECnet forA         _______________________________       OpenVMS Alpha,  4-7 G         OPCCRASH.EXE, A-42                  customizing the system, 4-6 @         OpenVMS Alpha                       decompressing system=          license                              libraries,  4-9 G             registering during              editing startup procedures, 1                installation,  3-19            4-6 H          save sets                          installing layered products,2             transferring to system            4-15D                disk,  3-11                  preparing to use OpenVMSG         OpenVMS Management Station            Management Station,  4-14fE          preparing system,  4-14, 8-15      registering licenses, 4-3,E         Output                              setting up user accounts,m1          saving from installation,            4-6 G             1-4                             testing the system with thel  C         P                                     User Environment Teste;         _______________________________       Package,  4-8 B         Page file                           tuning the system with<          checking size,  8-7                  AUTOGEN,  4-21;          modifying size,  8-6             Postupgrade taskstF         Password                            adding and removing files,2          forgotten,  3-41, A-24               8-14H          minimum length,  3-14              backing up system disk, 8-19  G                                             changing MODPARAMS.DAT, 8-7a  I                                                                   Index-5e m  e              @     Postupgrade tasks (cont'd)         Product Authorization Key.       checking system file sizes,        (PAK)<          8-7                            registering after an<       decompressing system                 installation, 4-3E          libraries, 8-10                registering after an upgrade,l.       examining command procedure          8-5=          templates, 8-9                 registering during an =       modifying size of dump file,         installation, 3-19             8-6F       modifying size of page file,     Q______________________________  5          8-6                           Queue database 6       modifying size of swap file,      creating,  4-64          8-6                           Queue manager6       preparing to use OpenVMS          starting,  4-6-          Management Station, 8-15      Quorum B       registering new licenses,         See also VMScluster quorumB          8-5                            maintaining during rolling8       running AUTOGEN,  8-21               upgrades, 6-82       running UETP,  8-13              Quorum diskB     Preinstallation tasks               choosing during VMScluster=       collecting information you           installation, 3-36n          will need, 3-3sF       preparing for a VMScluster       R______________________________-          environment, 2-2              Reboot A       software and hardware             after installation,  3-40 E          components, 1-4               Recording an installation, 1-4r5     Preupgrade tasks                   Removing fileslA       analyzing and repairing           after installation,  4-13a<          system disk, 5-8               after upgrade,  8-14D       backing up system disk,  5-7     Restoring files on the system=       preparing system disk,  5-8        disk,  1-8, A-4, A-7cE       shutting down system,  5-9       Restoring the system disk, B-8 C     Printer                             without booting the CD-ROM,k/       recording installation on,           B-11n3          1-4                           Restrictions B     Problems                            for OpenVMS Alpha upgrade,.       booting                              5-3C          fixing by booting with         License Management Facilityt:             default parameter              (LMF), C-8, C-9C             values, A-21               Rolling upgrades, 6-6 to 6-9 C       forgotten password                maintaining cluster quorum, .          fixing by booting without         6-8A             the UAF, A-24               required operating systemn7       logging in,  A-23, A-24              version, 6-6r       Index-6A                   @         Rolling upgrades (cont'd)         SYCONFIG.COM procedureI          restrictions,  6-6                 editing after an installation 4                                               ,  4-6B         S______________________________   SYLOGICALS.COM procedureI         SCSI VMScluster systems, 3-34       editing after an installation 4         SDA (System Dump Analyzer),           ,  4-6?           A-44                            SYLOGIN.COM proceduresI         Sending comments to Digital         editing after an installation 4           writers,  iii                       ,  4-6<         SET AUTO_ACTION command, A-31     SYSBOOT.EXE,  A-10:         SET BOOTDEF_DEV command, A-32       commands, A-110         SET BOOT_OSFLAGS command, A-34    SYSGENG         Setting passwords during an         commands for conversationalh9           installation,  3-14                 boot,  A-11rE         Shadow sets                       SYSTARTUP_VMS.COM proceduretI          system disk                        editing after an installationt4             upgrading,  5-5                   ,  4-6I         SHOW BOOTDEF_DEV command, A-32      editing to control DECnet forSA         SHOW CRASH command, A-44              OpenVMS Alpha,  4-7 0         Shutdown                          System<          after installation,  3-40          customizing, 4-6I          before an upgrade,  5-10,          shutting down before upgrade, 1             6-4, 6-8                          5-9p8          procedures,  A-42                SYSTEM accountD         SHUTDOWN.COM, A-42                  forgotten password, 3-41B         Site-specific command               setting password, 3-145           procedures                      System diskm8          restored during upgrade,  8-9      adding filesG         Source drive, 1-3, B-6                 after installation, 4-13EB         Startup command procedure              after upgrade, 8-14H          booting without,  A-23             analyzing and repairing, 5-8<          when errors prevent you from       backing up, 8-19?             logging in,  A-23               backing up after an A         Startup files                         installation,  4-18wI          editing after an installation      backing up before an upgrade,r1             ,  4-6                            5-7 G         Swap file                           booting after installation, 2          checking size,  8-7                  3-40F          modifying size,  8-6               booting after transferringF         SWAPFILES.COM procedure               required save set,  3-32I          executing to change system         checking amount of free space86             file sizes,  8-7                  on,  4-9:                                             creating, 3-11I                                             free space needed for upgrade 4                                               ,  5-9  I                                                                   Index-7                    8     System disk (cont'd)               Target drive, B-6@       free space needed to             Transferring save sets to;          decompress libraries,           system disk,  3-11 3          4-9                           TURBOchannel >       preparing for an OpenVMS          booting with alternate8          Alpha upgrade, 5-8                adapter, A-20C       removing files                    booting with PMAZB adapter, /          after installation,  4-13         A-17 C          after upgrade,  8-14           booting with PMAZC adapter,o/       unique volume label                  A-17 ;          requirement, B-3              TURBOchannel adapterUA       upgrading,  5-5                   booting over the network,m/     System Generation utility              A-19           (SYSGEN)tF       ALLOCLASS parameter,  2-3        U______________________________D       commands for conversational      UAF (User Authorization File)E          boot, A-11                     booting with alternate,  A-24rA     System hang,  A-47                  returning to the default,e/     System parameters                      A-26uA       booting with default,  A-21      UAFALTERNATE logical name, -       UAFALTERNATE,  A-26                A-24 E       when incorrect values prevent    UAFALTERNATE system parameter, -          the system from booting,        A-26 +          A-21                          UETPiA     System startup                      See User Environment Test        in an emergencyO2          with default system               Package.             parameters, A-21           Upgrade  D          without startup and login      See also Post-upgrade tasks,D             procedures, A-23               Preupgrade tasks, Upgrade4          without the UAF,  A-24            procedureB     SYSTEST account                     cautions and restrictions,.       creating after installation,         5-3E          4-4                            disk space requirement,  5-9, /     SYSUAFALT.DAT file,  A-24              7-13,C                                         effect on layered products,t.     T______________________________        5-4;     Tailoring files                     requirements,  5-11_<       See Adding files, Removing        shadowed disks,  5-58          files                         Upgrade procedureE     Target disk                         effect on command procedures, .       using backup copy for,  5-7          8-9E                                         effect on MODPARAMS.DAT,  8-7i       Index-8                    9         Upgrade procedure (cont'd)        VOTES parameter I          required operating system          checking for rolling upgradesh4             version,  5-3, 6-4, 6-6           ,  6-7            rolling upgradesaI             adding a new CPU,  6-2        W______________________________oB          using the POLYCENTER Software    Writeboot utility,  A-37I             Installation utility,  1-8    Writing a new boot block,  A-37l%         User Environment Test Package            when to run,  4-8, 8-13  '         V______________________________-           VMScluster          building,  4-6l!          information required forg&             OpenVMS Alpha installation             ,  2-2&          installation questions,  3-34$          label for system disk,  B-3%         VMScluster installation, 3-34)$          choosing quorum disk,  3-36!          configuring the cluster,e             3-34          SCSI systems,  3-34          suggested answers to              questions,  3-34&          supplying ALLOCLASS parameter             ,  3-36          VMScluster quorum #          maintaining during rolling              upgrades,  6-8           VMScluster upgrades              See Concurrent upgrades            See Rolling upgradese            See Upgrade procedure         Volume label          definition,  1-5u%          requirement for VMSclusters,4             B-3          Volume shadowing$          backing up the system disk,             B-11  I                                                                   Index-9t