____________________________________________________ OpenVMS Alpha Version 7.2 Upgrade and Installation Manual Order Number: AA-QSE8C-TE January 1999 This document contains step-by-step instructions for installing and upgrading the OpenVMS Alpha operating system on Alpha computers. It also includes information about booting, shutdown, backup, and licensing procedures. Revision/Update Information: This is a new manual. Software Version: OpenVMS Alpha Version 7.2 Compaq Computer Corporation Houston, Texas ________________________________________________________________ January 1999 Compaq Computer Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Compaq Computer Corporation or an authorized sublicensor. Compaq Computer Corporation conducts its business in a manner that conserves the environment and protects the safety and health of its employees, customers, and the community. © Compaq Computer Corporation 1999. All rights reserved. The following are trademarks of Compaq Computer Corporation: AlphaServer, AlphaStation, Bookreader, CI, DEC, DECdirect, DECdtm, DECevent, DECnet, DECterm, DECwindows, DIGITAL, HSC, InfoServer, LAT, ManageWORKS, MSCP, OpenVMS, OpenVMS Cluster, PATHWORKS, POLYCENTER, RRD42, RZ, TeamLinks, TURBOchannel, UETP, VAX, VMS, XUI, and the Compaq logo. The following are third-party trademarks: 3Com is a registered trademark of the 3Com Corporation. Adaptec is a trademark of Adaptec, Inc. InstallShield is a registered trademark of Stirling Technologies, Inc. Intel is a registered trademark of Intel Corporation. Microsoft, MS, MS-DOS, and Windows 95 are registered trademarks, and Windows NT is a trademark of Microsoft Corporation. Motif is a registered trademark of the Open Software Foundation, Inc. NetView is a registered trademark of International Business Machines Corporation. All other trademarks and registered trademarks are the property of their respective holders. ZK6522 The OpenVMS documentation set is available on CD-ROM. This document was prepared using VAX DOCUMENT Version 2.1. _________________________________________________________________ Contents Preface................................................... ix 1 Getting Started 1.1 Key Terms..................................... 1-1 1.2 Examining Software and Hardware Components.... 1-2 1.2.1 Hardware Components....................... 1-2 1.2.2 Software Components....................... 1-3 1.2.3 Operating System CD-ROM................... 1-3 1.2.4 Firmware Revision Checking................ 1-4 1.2.5 Device Naming Conventions................. 1-5 1.3 Using the Operating System CD-ROM............. 1-5 1.3.1 Using the Menu............................ 1-6 1.3.2 Sample Menu Display....................... 1-6 1.3.3 How the Install or Upgrade Option Works... 1-7 1.3.3.1 Specifying the INITIALIZE Option........ 1-8 1.3.3.2 Specifying the PRESERVE Option.......... 1-8 1.3.4 How the Layered Products Options Work..... 1-10 1.3.5 How the DCL Option Works.................. 1-11 1.3.6 How the Shutdown Option Works............. 1-11 1.4 What to Do Next............................... 1-11 2 Preparing to Install in an OpenVMS Cluster Environment 2.1 Mixed-Version Support......................... 2-1 2.2 OpenVMS Cluster Information You Will Need..... 2-3 2.3 What to Do Next............................... 2-5 iii 3 Installing the OpenVMS Alpha Operating System 3.1 Preparing to Respond to Prompts During the Installation.................................. 3-1 3.2 Booting the Operating System CD-ROM........... 3-3 3.2.1 Booting from the Local Drive.............. 3-3 3.2.2 Booting from the InfoServer............... 3-4 3.3 Creating the System Disk...................... 3-8 3.3.1 Installing from the CD-ROM................ 3-8 3.3.2 Choosing INITIALIZE or PRESERVE........... 3-9 3.3.3 Specifying the Target Disk................ 3-10 3.3.4 Specifying the Volume Label............... 3-10 3.3.5 Setting the SYSTEM Account Password....... 3-11 3.3.6 Becoming a Cluster Member................. 3-12 3.3.7 Becoming an OpenVMS Galaxy Instance....... 3-12 3.3.8 MEMORY CHANNEL Information................ 3-13 3.3.9 Installing Windowing and Networking Products.................................. 3-16 3.3.10 Setting System Parameters................. 3-18 3.3.11 Updating Time Zone Information............ 3-19 3.4 Registering Licenses.......................... 3-21 3.4.1 Types of OpenVMS Alpha Licenses........... 3-21 3.4.2 How to Register Licenses.................. 3-23 3.4.3 Using the Licensing Procedure............. 3-24 3.5 Completing the Installation................... 3-25 3.5.1 Choosing Descriptive Help Text............ 3-25 3.5.2 Selecting Components...................... 3-26 3.5.3 List of Components........................ 3-27 3.5.4 Completing the Procedure.................. 3-28 3.6 Installing Layered Products................... 3-30 3.7 Booting the New System Disk................... 3-34 3.7.1 Preparing to Boot the New System Disk..... 3-35 3.7.2 How to Boot the New System Disk........... 3-35 3.8 Joining an OpenVMS Cluster.................... 3-36 3.8.1 OpenVMS Cluster Prompts................... 3-36 3.9 Running AUTOGEN............................... 3-38 3.10 Rebooting the System.......................... 3-40 3.10.1 Rebooting the System Manually............. 3-40 3.11 Logging in to the SYSTEM Account By Means of a Character Cell Terminal....................... 3-42 3.12 Logging in to the SYSTEM Account By Means of a Workstation................................... 3-42 3.13 What to Do Next............................... 3-42 iv 4 After Installing the OpenVMS Alpha Operating System 4.1 Registering Your Licenses..................... 4-2 4.2 Creating Accounts............................. 4-2 4.3 Backing Up Your System Disk................... 4-2 4.4 Customizing the System........................ 4-3 4.5 Configuring and Starting Networking Software...................................... 4-4 4.5.1 DECnet-Plus for OpenVMS Alpha............. 4-4 4.5.2 DECnet Phase IV for OpenVMS Alpha......... 4-4 4.5.3 DIGITAL TCP/IP Services for OpenVMS....... 4-6 4.6 Testing the System with UETP.................. 4-6 4.7 Decompressing the System Libraries............ 4-6 4.7.1 Determining Disk Space.................... 4-6 4.7.2 Methods of Using LIBDECOMP.COM............ 4-7 4.7.3 Responding to LIBDECOMP.COM Prompts....... 4-7 4.7.4 Using LIBDECOMP.COM Interactively......... 4-8 4.7.5 Using LIBDECOMP.COM in Batch.............. 4-8 4.8 Adding and Removing Operating System Files.... 4-9 4.9 Preparing to Use OpenVMS Management Station... 4-11 4.10 Installing Layered Products................... 4-12 4.10.1 Alternate Procedure....................... 4-13 4.10.2 DECevent.................................. 4-14 4.10.3 Monitoring Performance History............ 4-14 4.11 Installing DIGITAL OpenVMS Debugger Clients on a PC.......................................... 4-14 4.12 Backing Up the Customized System Disk......... 4-16 4.13 Configuring a Multihead System................ 4-17 4.14 Running AUTOGEN............................... 4-17 4.14.1 Modifying Parameters...................... 4-18 4.15 Postinstallation Checklist.................... 4-19 5 Before Upgrading the OpenVMS Alpha Operating System 5.1 Notes, Cautions, and Restrictions............. 5-2 5.1.1 Spiralog File System Not Supported........ 5-2 5.1.2 Required Operating System Version......... 5-2 5.1.3 Upgrade Paths............................. 5-2 5.1.4 Update License............................ 5-2 5.1.5 Files and Directories..................... 5-3 5.1.6 Licenses and Layered Products............. 5-3 5.2 Preparing to Upgrade in a Volume Shadowing Environment................................... 5-3 5.2.1 Creating a Nonshadowed Target Disk........ 5-4 v 5.2.2 Changing the Label........................ 5-4 5.2.3 Setting the Boot Device................... 5-5 5.3 Backing Up the System Disk.................... 5-5 5.4 Preparing the System Disk..................... 5-6 5.4.1 Examining the System Disk................. 5-6 5.4.2 Checking the Size of the System Disk...... 5-7 5.4.3 Verifying System Parameters............... 5-7 5.5 What to Do Next............................... 5-8 5.6 Preupgrade Checklist.......................... 5-8 6 Preparing to Upgrade in an OpenVMS Cluster Environment 6.1 Mixed-Version Support......................... 6-1 6.2 Adding a New System to the Cluster............ 6-3 6.3 Types of Upgrades............................. 6-3 6.4 Concurrent Upgrade............................ 6-3 6.4.1 How a Concurrent Upgrade Works............ 6-3 6.4.2 Preparing Your System for a Concurrent Upgrade................................... 6-4 6.5 Rolling Upgrade............................... 6-4 6.5.1 How a Rolling Upgrade Works............... 6-5 6.5.2 Notes and Restrictions.................... 6-5 6.5.3 Preparing Your System for a Rolling Upgrade................................... 6-6 7 Upgrading the OpenVMS Alpha Operating System 7.1 Booting the Operating System CD-ROM........... 7-1 7.1.1 Booting from the Local Drive.............. 7-1 7.1.2 Booting from the InfoServer............... 7-2 7.2 Performing the Upgrade........................ 7-5 7.2.1 Upgrading from the CD-ROM................. 7-5 7.2.2 Choosing INITIALIZE or PRESERVE........... 7-6 7.2.3 Specifying the Target Disk................ 7-7 7.2.4 Specifying the Volume Label............... 7-8 7.2.5 Checking Related Software................. 7-8 7.2.5.1 Spiralog................................ 7-8 7.2.5.2 AMDS.................................... 7-9 7.2.5.3 PATHWORKS............................... 7-9 7.2.6 Checking OpenVMS Cluster Membership....... 7-10 7.2.7 Becoming an OpenVMS Galaxy Instance....... 7-10 7.2.8 Memory Channel Information................ 7-11 vi 7.2.9 Upgrading Windowing and Networking Products.................................. 7-14 7.2.10 Updating Time Zone Information............ 7-16 7.2.11 Choosing Descriptive Help Text............ 7-18 7.2.12 Configuration Options..................... 7-18 7.2.13 Selecting Components...................... 7-19 7.2.14 Completing the Upgrade.................... 7-21 7.2.15 What to Do Next........................... 7-23 7.3 Installing Layered Products................... 7-23 7.4 What to Do After the Shutdown................. 7-27 7.4.1 Standalone Upgrade........................ 7-27 7.4.2 Concurrent OpenVMS Cluster Upgrade........ 7-27 7.4.3 Rolling OpenVMS Cluster Upgrade........... 7-28 8 After Upgrading the OpenVMS Alpha Operating System 8.1 Reforming the Shadow Set...................... 8-2 8.2 Registering New Licenses...................... 8-3 8.3 Examining the AUTOGEN Report File............. 8-3 8.4 Modifying the System Parameters File.......... 8-4 8.4.1 System File Sizes......................... 8-4 8.4.2 OpenVMS Cluster Parameters................ 8-5 8.5 Examining Your Command Procedures............. 8-6 8.6 Testing the System with UETP.................. 8-6 8.7 Decompressing System Libraries................ 8-6 8.7.1 Determining Disk Space.................... 8-7 8.7.2 Methods of Using LIBDECOMP.COM............ 8-7 8.7.3 Responding to LIBDECOMP.COM Prompts....... 8-7 8.7.4 Using LIBDECOMP.COM Interactively......... 8-8 8.7.5 Using LIBDECOMP.COM in Batch.............. 8-9 8.8 Adding and Removing Operating System Files.... 8-9 8.9 Preparing to Use OpenVMS Management Station... 8-12 8.10 Installing Layered Products................... 8-13 8.10.1 Alternate Procedure....................... 8-14 8.10.2 DECevent.................................. 8-15 8.10.3 Monitoring Performance History............ 8-15 8.11 Installing DIGITAL OpenVMS Debugger Clients on a PC.......................................... 8-15 8.12 Backing Up the Customized System Disk......... 8-17 8.13 Rebooting Cluster Members..................... 8-17 8.14 Running AUTOGEN............................... 8-18 8.15 Postupgrade Checklist......................... 8-18 vii A Halt, Boot, and Shutdown Procedures A.1 Booting Operations............................ A-2 A.1.1 Booting the Operating System CD-ROM....... A-2 A.1.1.1 Booting from the Local Drive............ A-2 A.1.1.2 Booting from the InfoServer............. A-3 A.1.2 Booting Manually from the System Disk..... A-6 A.1.3 Performing a Conversational Boot.......... A-7 A.1.4 Booting with Minimum Startup.............. A-9 A.1.5 Booting with the XDelta Utility (XDELTA).................................. A-10 A.1.6 Booting from a Different Directory........ A-11 A.1.7 Booting with a PMAZB or PMAZC TURBOchannel Adapter................................... A-11 A.1.8 Booting Over the Network with an Alternate TURBOchannel Adapter...................... A-13 A.1.9 Booting in an Emergency................... A-14 A.1.9.1 Booting with Default System Parameters.............................. A-15 A.1.9.2 Booting Without Startup and Login Procedures.............................. A-16 A.1.9.3 Booting Without the User Authorization File.................................... A-18 A.2 Set, Show, and Writeboot Operations........... A-20 A.2.1 Setting the System for Automatic Booting................................... A-20 A.2.2 Setting and Showing Boot Devices.......... A-22 A.2.3 Setting Boot Parameters................... A-23 A.2.4 Using the Writeboot Utility............... A-25 A.3 Halt and Shutdown Operations.................. A-26 A.3.1 Halting the System........................ A-26 A.3.2 Shutting Down the System.................. A-27 A.3.2.1 Orderly Shutdown........................ A-28 A.3.2.2 Emergency Shutdown with OPCCRASH.EXE.... A-28 A.3.2.3 Emergency Shutdown with Crash Commands................................ A-28 A.4 Troubleshooting Procedures.................... A-29 A.4.1 If the System Does Not Boot............... A-29 A.4.1.1 For Hardware Problems................... A-30 A.4.1.2 For Software Problems................... A-30 A.4.2 Detecting and Responding to System Problems.................................. A-30 viii B Backing Up and Restoring the System Disk B.1 Reasons for Backing Up the System Disk........ B-1 B.2 Suggested Procedures.......................... B-2 B.3 OpenVMS Cluster Caution....................... B-3 B.4 Backing Up the System Disk.................... B-3 B.4.1 Getting Started........................... B-3 B.4.2 Mounting Devices.......................... B-4 B.4.3 Entering the BACKUP Command............... B-4 B.4.4 Changing the CLUSTER_SIZE Parameter....... B-5 B.4.5 What to Do Next........................... B-5 B.5 Restoring the System Disk..................... B-6 B.5.1 Getting Started........................... B-6 B.5.2 Mounting Devices.......................... B-7 B.5.3 Entering the BACKUP Command............... B-7 B.5.4 What to Do Next........................... B-8 B.6 Alternate Backup and Restore Procedure........ B-8 B.6.1 Preparing an Alternate System Disk........ B-9 B.6.2 Using the Alternate System Disk........... B-10 C License Management Supplement C.1 Using the License Unit Requirement Table (LURT)........................................ C-1 C.2 License Management Facility (LMF) Notes....... C-5 C.2.1 Restrictions.............................. C-6 D Preparing to Use OpenVMS Management Station D.1 Preparing Your OpenVMS System................. D-1 D.1.1 Setting Up in a Mixed-Architecture Cluster Environment............................... D-2 D.1.2 Start the Server on Other Nodes........... D-4 D.1.3 Error Log Information..................... D-4 D.1.4 Update the Printer and Storage Database... D-4 D.1.5 Edit the System Files..................... D-5 D.1.6 Allow OpenVMS Management Station to Control the Printer and Storage Environment............................... D-7 ix D.1.7 Keep Your Printer Environment Up to Date...................................... D-7 D.1.7.1 When is the Database Updated?........... D-8 D.1.7.2 Do You Need to Run TNT$UTILITY.COM Manually?............................... D-9 D.1.7.3 Are There Any Requirements for Running TNT$UTILITY.COM?........................ D-9 D.1.8 Keeping Your Storage Environment Up to Date...................................... D-10 D.1.9 Enabling Disk Quotas...................... D-10 D.1.10 Caching Storage Configuration Data........ D-10 D.1.11 Running Third-Party TCP/IP Stacks......... D-11 D.1.12 Determining and Reporting Problems........ D-11 D.1.13 Removing the OpenVMS Management Station Server.................................... D-12 D.2 Preparing Your PC............................. D-12 D.2.1 Required Memory and Disk Space............ D-12 D.2.2 Distribution Files........................ D-13 D.2.3 Required Software......................... D-13 D.2.4 Time Required for Installation............ D-13 D.2.5 Copy the Client File to the PC............ D-13 D.2.6 Installation Directory.................... D-13 D.2.7 Installation Procedure.................... D-14 D.2.8 Recovering from Errors.................... D-14 D.3 After Installing the Client Software on Your PC............................................ D-14 D.3.1 Defining TCP/IP Nodes..................... D-15 D.4 Uninstalling Version 2.1 of the OpenVMS Management Station Client..................... D-15 D.5 Uninstalling OpenVMS Management Station....... D-15 D.6 Getting Started with OpenVMS Management Station....................................... D-16 E Removing the OpenVMS Alpha Operating System x Glossary Index Tables 2-1 OpenVMS Cluster Warranted and Migration Support for VAX and Alpha................. 2-2 3-1 Prompts for OpenVMS Cluster Configurations............................ 3-36 6-1 OpenVMS Cluster Warranted and Migration Support for VAX and Alpha................. 6-2 A-1 SYSGEN Commands Used in the SYSBOOT Procedure................................. A-8 A-2 Emergency Boot Procedures................. A-14 C-1 License Unit Requirement Table (LURT)..... C-2 xi _________________________________________________________________ Preface Intended Audience This manual is intended for anyone responsible for installing or upgrading the OpenVMS Alpha operating system and for the startup, shutdown, and backup operations required on Alpha computers running this software. When to Use This Manual If you received factory-installed software (FIS) with your Alpha computer, refer to that user documentation to start up your system for the first time. Use this manual if you need to install or upgrade the OpenVMS Alpha operating system software yourself or if you need to perform certain startup, shutdown, or backup operations. Document Structure This manual is organized as follows: o Chapter 1 defines key terms and provides information about hardware and software components. Review this chapter before performing any installation or upgrade. o Chapter 2 provides preliminary information about installing the operating system in an OpenVMS Cluster environment. o Chapter 3 describes how to install the operating system. o Chapter 4 describes the tasks you must perform after installing the operating system. o Chapter 5 describes how to prepare your system for an upgrade. ix o Chapter 6 supplements Chapter 5 with additional tasks you must perform before upgrading an OpenVMS Cluster system. o Chapter 7 describes how to upgrade the operating system. o Chapter 8 describes the tasks you must perform after upgrading the operating system. o Appendix A contains instructions for halting the system, booting the operating system CD-ROM and the system disk, 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. o Appendix C contains supplementary information about registering licenses. o Appendix D describes how to prepare your OpenVMS system and your PC to run the OpenVMS Management Station server and client software. o Appendix E explains how to remove the OpenVMS Alpha operating system from your disk. o The Glossary defines key terms used in this manual. Related Documents Before installing, upgrading, or using the OpenVMS Alpha operating system on your Alpha computer, be sure you have access to the following documents: o All cover letters included with your kit. o The OpenVMS Version 7.2 Release Notes, which provides important supplementary information about the OpenVMS Alpha operating system. o OpenVMS Version 7.2 New Features Manual, which describes enhancements and new support included in the OpenVMS Version 7.2 operating system. o OpenVMS Cluster Systems and Guidelines for OpenVMS Cluster Configurations, if you plan to install your system in an OpenVMS Cluster environment. x o The most recent version of the DECwindows Motif for OpenVMS Installation Guide and Managing DECwindows Motif for OpenVMS Systems (if you plan to install and customize DECwindows Motif for OpenVMS Alpha software). o The following networking software documents (if you plan to install and configure DECnet-Plus, DECnet Phase IV, or DIGITAL TCP/IP Services for OpenVMS software): - DECnet-Plus for OpenVMS Installation and Basic Configuration - DECnet for OpenVMS Guide to Networking - DIGITAL TCP/IP Services for OpenVMS Installation and Configuration Documentation for the networking products listed above are included on the OpenVMS Online Documentation CD-ROM. Hardcopy documentation must be purchased separately. o The hardware manuals that are supplied with your Alpha computer. These manuals provide detailed information about your system hardware, including the operation of the system unit, the drives, and the monitor. During the course of installing, upgrading, or using the OpenVMS Alpha operating system on your Alpha computer, you might need to refer to the following documents as well: o OpenVMS License Management Utility Manual, which contains detailed information about registering your software licenses. o OpenVMS System Manager's Manual and the OpenVMS System Management Utilities Reference Manual, which contain information about system management operations and utilities that you might need to use when you install, upgrade, customize, and maintain your OpenVMS Alpha system. The OpenVMS System Management Utilities Reference Manual: M-Z provides complete information about using the POLYCENTER Software Installation utility PRODUCT command to add or remove files, install other software, and related operations. o Volume Shadowing for OpenVMS, which you might need if you are installing or upgrading the OpenVMS Alpha operating system on a shadowed system disk. xi o OpenVMS Management Station Overview and Release Notes, which provides information about getting started, setting up, and using OpenVMS Management Station. For additional information on the Open Systems Software Group (OSSG) products and services, access the following OpenVMS World Wide Web address: http://www.openvms.digital.com Reader's Comments Compaq Computer Corporation welcomes your comments on this manual. Print or edit the online form SYS$HELP:OPENVMSDOC_ COMMENTS.TXT and send us your comments by: Internet openvmsdoc@zko.mts.dec.com Fax 603 884-0120, Attention: OSSG Documentation, ZKO3-4/U08 Mail Compaq Computer Corporation OSSG Documentation Group, ZKO3-4/U08 110 Spit Brook Rd. Nashua, NH 03062-2698 How To Order Additional Documentation Use the following World Wide Web address to order additional documentation: http://www.openvms.digital.com:81/ If you need help deciding which documentation best meets your needs, call 800-DIGITAL (800-344-4825). Conventions VMScluster systems are now referred to as OpenVMS Cluster systems. Unless otherwise specified, references to OpenVMS Clusters or clusters in this document are synonymous with VMSclusters. In this manual, every use of DECwindows and DECwindows Motif refers to DECwindows Motif for OpenVMS software. xii The following conventions are also used in this manual: Ctrl/x A sequence such as Ctrl/x indicates that you must hold down the key labeled Ctrl while you press another key or a pointing device button. In examples, a key name enclosed in a box indicates that you press a key on the keyboard. (In text, a key name is not enclosed in a box.) In the HTML version of this document, this convention appears as brackets, rather than a box. . . . A horizontal ellipsis in examples indicate one of the following possibilities: o Additional optional arguments in a statement have been omitted. o The preceding item or items can be repeated one or more times. o Additional parameters, values, or other information can be entered. . A vertical ellipsis indicate the omission . of items from a code example or command . format; the items are omitted because they are not important to the topic being discussed. ( ) In command format descriptions, parentheses indicate that you must enclose the options in parentheses if you choose more than one. [ ] In command format descriptions, brackets indicate optional elements. You can choose one, none, or all of the options. (Brackets are not optional, however, in the syntax of a directory name in an OpenVMS file specification or in the syntax of a substring specification in an assignment statement.) xiii { } In command format descriptions, braces indicate required elements; you must choose one of the options listed. bold text This text style represents the introduction of a new term or the name of an argument, an attribute, or a reason. italic text Italic text indicates important information, complete titles of manuals, or variables. Variables include information that varies in system output (Internal error number), in command lines (/PRODUCER=name), and in command parameters in text (where dd represents the predefined code for the device type). UPPERCASE TEXT Uppercase text indicates a command, the name of a routine, the name of a file, or the abbreviation for a system privilege. Monospace text Monospace type indicates code examples and interactive screen displays. In the C programming language, monospace type in text identifies the following elements: keywords, the names of independently compiled external functions and files, syntax summaries, and references to variables or identifiers introduced in an example. - A hyphen at the end of a command format description, command line, or code line indicates that the command or statement continues on the following line. numbers All numbers in text are assumed to be decimal unless otherwise noted. Nondecimal radixes - binary, octal, or hexadecimal - are explicitly indicated. xiv 1 _________________________________________________________________ Getting Started This chapter defines key terms and describes preliminary procedures you must perform before an installation or upgrade. 1.1 Key Terms The following are a few key terms you need to know before you install or upgrade the system: ___________________________________________________________ Term__________________Definition___________________________ Operating system The CD-ROM containing the OpenVMS CD-ROM Alpha operating system. HSx device A self-contained, intelligent, mass storage subsystem that lets computers in an OpenVMS Cluster environment share disks. The disk on which you install or upgrade the operating system can be connected to one of these systems (for example, an HSC or HSD). InfoServer A general-purpose disk storage server that allows you to use the operating system CD-ROM to install the operating system on remote client systems connected to the same local area network (LAN). Getting Started 1-1 Getting Started 1.1 Key Terms ___________________________________________________________ Term__________________Definition___________________________ Local drive A drive, such as an RRD42 CD-ROM drive, that is connected directly to an Alpha computer. If you have a standalone Alpha computer, it is likely that all drives connected to the system are local drives. Source drive The drive that holds the operating system CD-ROM during the upgrade or installation. System disk The disk that contains (or will contain) the OpenVMS Alpha operating system. The installation or upgrade procedure transfers the OpenVMS Alpha operating system from the operating system CD-ROM on the source drive to the system disk. Target drive The drive that holds the system disk ______________________during_the_upgrade_or_installation.__ 1.2 Examining Software and Hardware Components Before beginning an installation or upgrade, be sure you have all the required hardware and software components, as described in the following sections. 1.2.1 Hardware Components Before you begin an installation or upgrade, do the following: o Be sure the hardware has been installed and checked for proper operation. For detailed information, see the hardware manuals you received with your Alpha computer. o Be sure you know how to turn on and operate the components of your system, including the system unit, console, monitor, drives, terminals, and printers. If necessary, read the hardware manuals that came with these components. 1-2 Getting Started Getting Started 1.2 Examining Software and Hardware Components o Set up your system to record the installation procedure on either a hardcopy terminal or a printer attached to the console terminal. (See your hardware manuals for more details about connecting those components to your system.) If you do not do this, the screen messages will be lost. You will need a transcript in case there is a problem during the installation. 1.2.2 Software Components Before you begin an installation or upgrade, do the following: o Be sure you have all the items listed on the bill of materials in the distribution kit. If your distribution kit is incomplete, notify your Compaq support representative and request priority shipment of any missing items. o Before installing the OpenVMS Alpha operating system software, review all cover letters and release notes. 1.2.3 Operating System CD-ROM Included in your kit is the OpenVMS Alpha operating system CD-ROM, which you use to install or upgrade the operating system, or to perform operations such as backing up the system disk. The CD-ROM is labeled similar to the following: CD-ROM Label: OpenVMS Alpha V7.2 Operating System Volume Label: ALPHA072 ________________________ Note ________________________ The volume label is the machine-readable name that the OpenVMS Alpha operating system and InfoServer systems use to access the CD-ROM. ______________________________________________________ Getting Started 1-3 Getting Started 1.2 Examining Software and Hardware Components 1.2.4 Firmware Revision Checking OpenVMS Alpha Version 7.2 provides enhanced firmware checking for systems during a boot operation. When you boot the OpenVMS Alpha operating system CD-ROM, the system automatically checks the version of console firmware, which includes PALcode, that is running on your computer. The system also provides more explicit information about how to upgrade the firmware. Previously, only the PALcode version was checked and the informational messages were less specific. If you do not have the required version of console firmware, the system displays a message similar to the following: %SYSBOOT-F-FIRMREV, Firmware rev. nnn is below the absolute minimum of nnn. Please update your firmware to the recommended revision nnn, which can be found on the firmware CD labeled: Alpha AXP Systems Firmware Update nnn. If you do not have the recommended version of console firmware, the system displays a message similar to the following: %SYSBOOT-W-FIRMREV, Firmware rev. nnn is below the recommended minimum of nnn. Please update your firmware to the recommended revision, which can be found on the firmware CD labeled: Alpha AXP Systems Firmware Update nnn. The latest console firmware CD-ROM is included with your kit. ________________________ Note ________________________ Once you install this version of the OpenVMS Alpha operating system, the firmware check (similar to the previous PALcode check) will occur each time you reboot the system. ______________________________________________________ 1-4 Getting Started Getting Started 1.2 Examining Software and Hardware Components 1.2.5 Device Naming Conventions When you perform specific operations, you are asked to specify device names for the source drive and target drive. When specifying those device names, note the following naming conventions: o When the source drive is a local CD-ROM drive, the device name is similar to the following: DKA400 o When the source drive is a CD-ROM drive connected to the InfoServer, the device name is always the following: DAD1 o When the target drive is a local disk, the device name is similar to the following: DKA0: Note the following conventions: - DK is the device code of the boot device. - A is the boot device controller designation. - 0 is the unit number of the boot device. o On Alpha systems configured in certain OpenVMS Cluster or HSx environments, the device naming convention is similar to the following: DUA20.14.0.2.0 The values you specify identify components such as the boot device, controller, unit number of the boot device, HSx controller node number, and channel numbers. Because these values vary depending on your specific hardware configuration, refer to the owner, operator, and technical service manuals that came with your computer for detailed information. 1.3 Using the Operating System CD-ROM The following sections describe how you use the operating system CD-ROM to install, upgrade, and modify your system disk. Getting Started 1-5 Getting Started 1.3 Using the Operating System CD-ROM 1.3.1 Using the Menu The OpenVMS Alpha operating system CD-ROM includes a menu system that allows you to easily upgrade or install the operating system and to perform related operations such as backing up the system disk, installing layered products, and removing or reconfiguring products. This command procedure starts automatically when you boot the OpenVMS Alpha operating system CD-ROM, displaying a menu from which you choose options to perform the following tasks: o Install or upgrade the operating system from the CD-ROM. o Display a list of products that can be installed from the CD-ROM. o Install or upgrade layered products from the CD-ROM. o Show which products are installed on your system. o Reconfigure layered products installed on your system. o Remove products. o Enter a DCL environment from which you can perform preinstallation or maintenance tasks such as mounting or showing devices and backing up or restoring files on the system disk. o Shut down the system. Review the following sections to understand how the menu works. You will then be prepared to choose appropriate menu options when you are asked to do so before, during, and after an installation or upgrade. 1.3.2 Sample Menu Display The following is a sample display of the menu: OpenVMS (TM) Alpha Operating System, Version V7.2 Copyright (c) 1998 Compaq Computer Corporation. All rights reserved. Installing required known files... Configuring devices... *************************************************************** 1-6 Getting Started Getting Started 1.3 Using the Operating System CD-ROM You can install or upgrade the OpenVMS Alpha operating system or you can install or upgrade layered products that are included on the OpenVMS Alpha operating system CD-ROM. You can also execute DCL commands and procedures to perform "standalone" tasks, such as backing up the system disk. Please choose one of the following: 1) Install or upgrade OpenVMS Alpha Version V7.2 2) Display products and patches that this procedure can install 3) Install or upgrade layered products and patches 4) Show installed products 5) Reconfigure installed products 6) Remove installed products 7) Execute DCL commands and procedures 8) Shut down this system Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?) 1.3.3 How the Install or Upgrade Option Works The OpenVMS Installation and Upgrade implement a POLYCENTER Software Installation (PCSI) utility concept called a platform. The OpenVMS Alpha platform contains the OpenVMS Alpha operating system, plus options for certain other products, including DECwindows, DECnet, and DIGITAL TCP/IP services. Including these products in the OpenVMS platform allows you to install or upgrade these products along with the OpenVMS Alpha operating system. Once you select which of these optional products you want to install, information is retained in the database maintained by the PCSI utility. This information allows future OpenVMS upgrades to select the correct default choices for these optional products. When you choose the install or upgrade option (1) from the menu, the system asks whether you want to preserve or initialize the system disk. The display is similar to the following: There are two choices for Installation/Upgrade: INITIALIZE - Removes all software and data files that were previously on the target disk and installs OpenVMS Alpha. PRESERVE -- Installs or upgrades OpenVMS Alpha on the target disk and retains all other contents of the target disk. Getting Started 1-7 Getting Started 1.3 Using the Operating System CD-ROM * Note: You cannot use PRESERVE to install OpenVMS Alpha on a disk on which OpenVMS VAX or any other operating system is installed. Do you want to INITIALIZE or to PRESERVE? [PRESERVE] 1.3.3.1 Specifying the INITIALIZE Option When you specify the INITIALIZE option, the following operations take place: o All software and data files that were previously on the target disk are removed. o The operating system is installed. Specify the INITIALIZE option and perform a full installation under the following conditions: o If your Alpha computer is new (it has never had any version of the operating system running on it, including factory-installed software). o If your Alpha computer is running a version of the OpenVMS Alpha operating system and you want to overwrite the entire contents of the system disk (the operating system, application software, and user files). o If you want to create a new system disk but keep the old one (if you want to alternate between the two). 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, the upgrade procedure will not work correctly. Therefore, unless you chose to restore the system disk to its original directory structure, you would have to reinstall the operating system. 1.3.3.2 Specifying the PRESERVE Option When you specify the PRESERVE option, the following operations take place: 1-8 Getting Started Getting Started 1.3 Using the Operating System CD-ROM ___________________________________________________________ IF_...________________THEN_..._____________________________ the OpenVMS Alpha the following operations take place: operating system o The operating system is installed. is not already installed on the o All other contents of the target target disk, disk are retained. the OpenVMS Alpha the operating system is upgraded, as operating system follows: is installed on the o Old operating system files and new target disk, files are merged or replaced. o All other contents of the target disk are retained. ___________________________________________________________ ________________________ Note ________________________ If you intend to choose the PRESERVE option (because there are certain files on the disk that you want to retain), Compaq recommends that you first make a backup copy of your system disk. If there is any problem during the installation or upgrade that might affect the integrity of the disk, you will have the backup copy as a safeguard. ______________________________________________________ If you choose the PRESERVE option and choose a target disk that already contains the OpenVMS Alpha Version 7.2 software, you are provided with the option to either reconfigure or reinstall the OpenVMS Alpha operating system. Reconfigure the operating system if you want to change the options you chose to include when the operating system was installed. Reinstall the operating system if you think that your system files may have become corrupted. The following message may be displayed: Version V7.2 of the OpenVMS operating system is already installed on the target disk. You may choose one of the following actions: o Reconfigure the OpenVMS platform. This action will allow you to change your selections of which of the windowing and network products you included with your OpenVMS operating system installation. Getting Started 1-9 Getting Started 1.3 Using the Operating System CD-ROM o Reconfigure the OpenVMS operating system. This action will allow you to change your choices about which options you included for the OpenVMS operating system. o Reinstall the OpenVMS operating system. This action will cause ALL operating system files to be replaced. You can also change your choices about which options you included for the OpenVMS operating system. Reinstall will take longer than Reconfigure. Reinstall may be appropriate if you suspect that files in the operating system, or in the windowing and network products have become corrupted. If you want to reinstall any of the windowing and network products, choose "Install or upgrade layered products and patches" (option 3) from the main menu. If you want to change your choices about which options you included for any of the windowing and network products, choose "Reconfigure installed products" (option 5) from the main menu. 1.3.4 How the Layered Products Options Work After you have installed or upgraded the operating system, you can use the menu to show, install, reconfigure (change previously selected options for a layered product), or remove products as well. ________________________ Note ________________________ When you boot the OpenVMS operating system CD-ROM and select the option to install layered products, that installation procedure does not run the Installation Verification Procedure (IVP) for layered products. Because the operating system is booted from the CD-ROM and the layered products are installed on a different device (the target drive), the IVPs cannot execute correctly. However, you can run the IVP for each layered product after you boot the target system (see the layered product installation documents for information on running the IVP). ______________________________________________________ 1-10 Getting Started Getting Started 1.3 Using the Operating System CD-ROM 1.3.5 How the DCL Option Works When you choose the DCL option (7) from the menu, you can use a subset of DCL commands (such as SHOW DEVICE, MOUNT, and BACKUP) to perform specific preinstallation and maintenance operations. Note, however, that this is a restricted DCL environment in that certain DCL commands and utilities will not function as expected because you are booting from read-only or write-locked media and because the full system startup is not performed. A triple dollar sign system prompt ($$$) indicates that you are in this restricted DCL environment, as shown in the following example: $$$ SHOW DEVICE To exit from the DCL environment and return to the main menu, enter the LOGOUT command. 1.3.6 How the Shutdown Option Works When you choose the shutdown option (8) from the menu, your system shuts down and you are returned to the console prompt (>>>). The system displays a message similar to the following: Shutting down the system SYSTEM SHUTDOWN COMPLETE 1.4 What to Do Next Now that you have reviewed key terms, examined hardware and software requirements, and learned how to use the menu system included on the OpenVMS Alpha operating system CD- ROM, you can do the following: ___________________________________________________________ IF_..._______________________________THEN_...______________ you want to install the operating go to Chapter 2. system in an OpenVMS Cluster environment, Getting Started 1-11 Getting Started 1.4 What to Do Next ___________________________________________________________ IF_..._______________________________THEN_...______________ you want to install the operating go to Chapter 3. system in a nonclustered environment, you want to upgrade the operating go to Chapter 5. system in a standalone, Volume Shadowing, or OpenVMS Cluster environment, you want only to back up or go to Appendix B. restore_your_system_disk,__________________________________ 1-12 Getting Started 2 _________________________________________________________________ Preparing to Install in an OpenVMS Cluster Environment This chapter contains information that you should review before performing an installation in an OpenVMS Cluster environment. Before installing the operating system in an OpenVMS Cluster environment, be sure you review any relevant OpenVMS Cluster information, contained in the following documents: o The cover letters and the software product descriptions included with your distribution kit o OpenVMS Version 7.2 New Features Manual o OpenVMS Version 7.2 Release Notes o If you are installing the operating system in a DSSI OpenVMS Cluster system, the DSSI OpenVMS Cluster Installation and Troubleshooting Guide Be sure the following sources of information are available as well: o OpenVMS Cluster Systems manual o Guidelines for OpenVMS Cluster Configurations manual o Your network or system manager 2.1 Mixed-Version Support OpenVMS Alpha Version 7.2 and OpenVMS VAX Version 7.2 provide two levels of support for mixed-version and mixed- architecture OpenVMS Cluster systems. These two support types are warranted and migration. Preparing to Install in an OpenVMS Cluster Environment 2-1 Preparing to Install in an OpenVMS Cluster Environment 2.1 Mixed-Version Support Warranted support means that Compaq has fully qualified the two versions coexisting in an OpenVMS Cluster and will answer all problems identified by customers using these configurations. Migration support is a superset of the Rolling Upgrade support provided in earlier releases of OpenVMS and is available for mixes that are not warranted. Migration support means that Compaq has qualified the versions for use together in configurations that are migrating in a staged fashion to a newer version of OpenVMS VAX or to OpenVMS Alpha. Problem reports submitted against these configurations will be answered by Compaq. However, in exceptional cases Compaq may request that you move to a warranted configuration as part of answering the problem. Migration support will help you move to warranted OpenVMS Cluster version mixes with minimal impact on your cluster environment. Table 2-1 shows the level of support provided for all possible version pairings. Table 2-1 OpenVMS Cluster Warranted and Migration Support __________for_VAX_and_Alpha________________________________ ____________V6.2-xxx____V7.1-xxx____V7.2___________________ V6.2 WARRANTED Migration Migration V7.1 Migration WARRANTED Migration V7.2________Migration___Migration___WARRANTED______________ ________________________ Note ________________________ Compaq does not support the use of Version 7.1 or higher with Version 6.1 (or earlier versions) in an OpenVMS Cluster environment. ______________________________________________________ 2-2 Preparing to Install in an OpenVMS Cluster Environment Preparing to Install in an OpenVMS Cluster Environment 2.2 OpenVMS Cluster Information You Will Need 2.2 OpenVMS Cluster Information You Will Need If during the installation you answer YES to the system prompt asking whether your system will be a member of an OpenVMS Cluster, you will need to provide the following information after you boot the system disk: ___________________________________________________________ Required Information___________Explanation__________________________ Type of Configuration types (CI, DSSI, SCSI, configuration local area, or mixed-interconnect) are distinguished by the interconnect device that the VAX and Alpha computers in the OpenVMS Cluster use to communicate with one another. DECnet node name See the network or system manager to and node address obtain the DECnet node name and node address for the computer on which you are installing the OpenVMS Alpha operating system. If you install DECnet-Plus (Phase V) software and do not plan to use DECnet for OpenVMS (Phase IV) addresses, then you do not need to provide this information. Preparing to Install in an OpenVMS Cluster Environment 2-3 Preparing to Install in an OpenVMS Cluster Environment 2.2 OpenVMS Cluster Information You Will Need ___________________________________________________________ Required Information___________Explanation__________________________ Allocation class During the installation procedure, value you will be asked for the allocation class value (ALLOCLASS) of the Alpha computer on which you are installing the OpenVMS Alpha operating system. For example: Enter a value for this_node ALLOCLASS parameter: Refer to OpenVMS Cluster Systems for the rules on specifying allocation class values. Note that in a mixed-interconnect OpenVMS Cluster environment, the allocation class value cannot be zero if the nodes serve DSSI or CI disks. It must be a value from 1 to 255. This is also true for any Alpha computer that is connected to a dual-pathed disk. After you enter the allocation class value, the installation procedure uses it to automatically set the value of the ALLOCLASS system parameter. Whether you want a Refer to OpenVMS Cluster Systems to quorum disk help you determine whether you want a quorum disk in the cluster. Location of the On a nonclustered system, the page page and swap files and swap files are on one or more local disks but on a clustered system, the files are on one or more local or clustered disks. See OpenVMS Cluster Systems to help you determine where the page and swap files will be located for the system on which you are installing the OpenVMS Alpha operating system software. 2-4 Preparing to Install in an OpenVMS Cluster Environment Preparing to Install in an OpenVMS Cluster Environment 2.2 OpenVMS Cluster Information You Will Need ___________________________________________________________ Required Information___________Explanation__________________________ Systems that will If you are going to set up either a be MOP[1] servers, local area or a mixed-interconnect disk servers, and cluster, you will need to make these tape servers determinations. Cluster group If you are going to set up a local number and cluster area cluster or a mixed-interconnect password cluster that is LAN-based, use the following rules to determine the cluster group number and password: o Cluster group number - A number in the range from 1 to 4095 or 61440 to 65535 o Cluster password - Must be from 1 to 31 alphanumeric characters in length and can include dollar signs ($) and underscores (_) [1]Servers_that_use_the_DECnet_maintenance_operation_______ protocol.__________________________________________________ 2.3 What to Do Next After you have completed all the tasks in this chapter, go to Chapter 3 to begin the installation. Preparing to Install in an OpenVMS Cluster Environment 2-5 3 _________________________________________________________________ Installing the OpenVMS Alpha Operating System This chapter describes the following installation tasks: o Preparing to respond to prompts during the installation o Installing from the operating system CD-ROM o Creating the system disk o Registering licenses o Selecting operating system components o Installing layered products o Booting the new system disk o Rebooting the system o Joining an OpenVMS Cluster (optional) o Running AUTOGEN o Logging in to the SYSTEM account ________________________ Note ________________________ Before you install the operating system, the correct version of console firmware should be running on your computer, as described in Section 1.2.4. ______________________________________________________ 3.1 Preparing to Respond to Prompts During the Installation At different points during the installation, you must respond to prompts asking you to supply specific information. This manual and the Help text available during the installation procedure tell you how to obtain most of this information and how to make decisions when responding to specific prompts. Installing the OpenVMS Alpha Operating System 3-1 Installing the OpenVMS Alpha Operating System 3.1 Preparing to Respond to Prompts During the Installation However, Compaq recommends that you review the following summary before you begin the installation so that you have an understanding beforehand of the types of information you will need to provide. During the installation, the system will prompt you for the following information: o The names of the source drive, target drive, and local area network device (if you are booting from an InfoServer system). o Whether you want to select the INITIALIZE or PRESERVE option (as described in Chapter 1). o A volume label for the target disk (if you choose not to use the default volume label). o A password for the SYSTEM account. You will be prompted to enter a password of at least 8 characters (but not exceeding 31 characters). o Whether you want to join an OpenVMS Cluster system and, if so, what kind (as described in Chapter 2). o DECnet node name and address (or values for the system parameters, SCSNODE and SCSSYSTEMID). ________________________ Note ________________________ If you install the DECnet-Plus for OpenVMS Alpha software but want to use addresses compatible with DECnet Phase IV for OpenVMS Alpha software, you still need to provide this information. These settings identify your system by name and number in a DECnet or cluster environment. Note as well that if you supply a DECnet address, the system will automatically calculate the SCSSYSTEMID value. If necessary, see the network or system manager to obtain this information. ______________________________________________________ o Information listed on Product Authorization Keys (PAKs) for your OpenVMS licenses. To register your licenses, you will need to enter the information listed on the PAK for each license. 3-2 Installing the OpenVMS Alpha Operating System Installing the OpenVMS Alpha Operating System 3.1 Preparing to Respond to Prompts During the Installation o Operating system components that you want to install (including DECwindows and OpenVMS Management Station files). You can install all components by default, or you can select each component individually. You can install DECwindows Motif, DIGITAL TCP/IP Services for OpenVMS, and either DECnet-Plus or DECnet Phase IV with the OpenVMS Alpha operating system. If you install DECwindows Motif, you must include the Support for DECwindows components. If you install either implementation of DECnet, you must include the Support for DECnet components. You must also include these components if you later plan to install these products separately. If you need to create a kit to install the PC component of the OpenVMS Management Station software, then you must include the OpenVMS Management Station Software-PC files component. See Section 3.5.3 for a complete list of components included with the OpenVMS Alpha operating system. 3.2 Booting the Operating System CD-ROM The OpenVMS Alpha Version 7.2 operating system includes procedures that allow you to easily install the operating system using the POLYCENTER Software Installation utility. To get started, boot the OpenVMS Alpha operating system CD-ROM either from your local CD-ROM drive or from a CD- ROM drive connected to the InfoServer, as described in the following sections. 3.2.1 Booting from the Local Drive To boot the operating system CD-ROM from the local CD-ROM drive, follow these steps: 1. Insert the operating system CD-ROM into the local CD-ROM drive. 2. At the console prompt (>>>), enter the SHOW DEVICE 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 Installing the OpenVMS Alpha Operating System 3-3 Installing the OpenVMS Alpha Operating System 3.2 Booting the Operating System CD-ROM Substitute the device name of the CD-ROM drive (as listed in the SHOW DEVICE display) for source-drive. For example, if the SHOW DEVICE display lists the device name of your CD-ROM drive as DKA400, enter the following command and press the Return key: >>> BOOT -FLAGS 0,0 DKA400 3.2.2 Booting from the InfoServer To boot the operating system CD-ROM using the InfoServer, follow these steps: 1. At the console prompt, enter the following command: >>> BOOT -FLAGS 0,0 -FILE APB_072 lan-device-name Note the following conventions: o APB_072 is the file name of the APB program used for the initial system load (ISL) boot program. o lan-device-name is the name of the local area network (LAN) device identified with your computer. For information about the LAN devices your system supports, refer to the following table. For additional information, see the hardware manuals that you received with your Alpha computer and the OpenVMS Software Product Description. 3-4 Installing the OpenVMS Alpha Operating System Installing the OpenVMS Alpha Operating System 3.2 Booting the Operating System CD-ROM ________________________________________________________ Ethernet FDDI Alpha_Computer_____________Device________Device_________ ALPHAbook 1 EOA0 - AlphaServer 400 series EWA0 FWA0 AlphaServer 1000 series ERA0, EWA0 FRA0 AlphaServer 1000A series EWA0 FWA0 AlphaServer 1200 series EWA0 FWA0 AlphaServer 2000 series ERA0, EWA0 FRA0 AlphaServer 2100, 2100A ERA0, EWA0 FRA0 series AlphaServer 4100 series EWA0 FWA0 AlphaServer 8200 series EXA0, EWA0 FXA0 AlphaServer 8400 series EXA0, EWA0 FXA0 AlphaStation 200 series EWA0 FWA0 AlphaStation 400 series EWA0 FWA0 AlphaStation 500 series EWA0 FWA0 AlphaStation 600 series ERA0, EWA0 FWA0 DEC 2000 series ERA0 - DEC 3000 series ESA0 "n/ESA0" DEC 4000 series EZA0 - DEC 7000 series EXA0 FXA0 DEC 10000 series EXA0 FXA0 Digital Personal EWA0 FWA0 Workstation (DPWS) series__________________________________________________ ________________________ Note ________________________ 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 TURBOchannel device, such as a PMAD (Ethernet) or DEFTA (FDDI), by specifying the device name as "n /ESA0". The value for n is the TURBOchannel slot number, which you can obtain by entering the SHOW CONFIGURATION command at the console Installing the OpenVMS Alpha Operating System 3-5 Installing the OpenVMS Alpha Operating System 3.2 Booting the Operating System CD-ROM prompt (>>>) and examining the display. For more information, see Section A.1.8, in Appendix A. o On DEC 4000 series systems, you must specify the ISL file name in uppercase (APB_072). ______________________________________________________ 2. The InfoServer ISL program then displays the following menu: Network Initial System Load Function Version 1.2 FUNCTION FUNCTION ID 1 - Display Menu 2 - Help 3 - Choose Service 4 - Select Options 5 - Stop Enter a function ID value: 3. Respond to the prompts as follows, pressing the Return key after each entry: a. Enter 3 for the function ID. b. Enter 2 for the option ID. c. Enter the service name (ALPHA072). A sample display follows: Enter a function ID value: 3 OPTION OPTION ID 1 - Find Services 2 - Enter known Service Name Enter an Option ID value: 2 Enter a Known Service Name: ALPHA072 ________________________ Note ________________________ If you boot the OpenVMS Alpha operating system CD-ROM from an InfoServer but lose your connection during the installation procedure (the system is unresponsive and 3-6 Installing the OpenVMS Alpha Operating System Installing the OpenVMS Alpha Operating System 3.2 Booting the Operating System CD-ROM pressing Ctrl/Y does not return you to the menu), do the following: ______________________________________________________ IF_...________________THEN_...________________________ you previously do the following: chose the 1. Reboot the OpenVMS Alpha INITIALIZE option, operating system CD-ROM. 2. Choose the install option from the menu and perform the installation again, as described in this chapter. you previously do the following: chose the PRESERVE 1. Reboot the OpenVMS Alpha option, operating system CD-ROM. 2. Enter the DCL environment by choosing option 7 from the menu. 3. Mount the device containing your backup copy of the target disk and the device that is your target disk. 4. Restore the backup copy of your target disk by entering the appropriate BACKUP commands. (See Appendix B for complete information using MOUNT and BACKUP commands to restore a system disk.) 5. Log out from the DCL environment. 6. Choose the install option from the menu and perform the installation again, as described in this chapter. ______________________________________________________ ______________________________________________________ Installing the OpenVMS Alpha Operating System 3-7 Installing the OpenVMS Alpha Operating System 3.3 Creating the System Disk 3.3 Creating the System Disk The following sections describe how to create the system disk from the operating system CD-ROM. 3.3.1 Installing from the CD-ROM After you boot the operating system CD-ROM, choose the install option (1) from the menu displayed on the screen. For example: OpenVMS (TM) Alpha Operating System, Version V7.2 Copyright (c) 1998 Compaq Computer Corporation. All rights reserved. Installing required known files... Configuring devices... **************************************************************** You can install or upgrade the OpenVMS Alpha operating system or you can install or upgrade layered products that are included on the OpenVMS Alpha operating system CD-ROM. You can also execute DCL commands and procedures to perform "standalone" tasks, such as backing up the system disk. Please choose one of the following: 1) Upgrade, install or reconfigure OpenVMS Alpha Version V7.2 2) Display products and patches that this procedure can install 3) Install or upgrade layered products and patches 4) Show installed products 5) Reconfigure installed products 6) Remove installed products 7) Execute DCL commands and procedures 8) Shut down this system Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?) 1 The OpenVMS Alpha operating system CD-ROM may contain patch kits. If it does, information similar to the following is displayed: 3-8 Installing the OpenVMS Alpha Operating System Installing the OpenVMS Alpha Operating System 3.3 Creating the System Disk The following PATCH kits are present on the OpenVMS Alpha distribution media. ----------------------------------- ----------- ---------- PRODUCT KIT TYPE KIT FORMAT ----------------------------------- ----------- ---------- DEC AXPVMS UCXECO_42_1 V1.0 Patch Sequential ----------------------------------- ----------- ---------- 1 item found Please consult the OpenVMS Alpha Upgrade and Installation Manual, the Release Notes, and the Cover Letter to determine if any or all of these patches may be required for your system. If you have not already done so, check to determine if you need to install any patches. 3.3.2 Choosing INITIALIZE or PRESERVE After you choose the install option, the system displays the following information and prompts: *********************************************************** The installation procedure will ask a series of questions. () - encloses acceptable answers [] - encloses default answers Type your response and press the key. Type: ? - to repeat an explanation ^ - to change prior input (not always possible) Ctrl/Y - to exit the installation procedure There are two choices for Installation/Upgrade: INITIALIZE - Removes all software and data files that were previously on the target disk and installs OpenVMS Alpha. PRESERVE -- Installs or upgrades OpenVMS Alpha on the target disk and retains all other contents of the target disk. * NOTE: You cannot use preserve to install OpenVMS Alpha on a disk on which OpenVMS VAX or any other operating system is installed. Do you want to INITIALIZE or to PRESERVE? [PRESERVE] Installing the OpenVMS Alpha Operating System 3-9 Installing the OpenVMS Alpha Operating System 3.3 Creating the System Disk Respond to the INITIALIZE or PRESERVE prompt as follows: ___________________________________________________________ IF_...________________THEN_..._____________________________ your system disk is do the following: new, 1. Enter INITIALIZE. 2. Press the Return key. you want to remove do the following: all files from an 1. Enter INITIALIZE. existing system disk, 2. Press the Return key. you want to retain press the Return key to accept the certain files on an default (PRESERVE). existing_disk,_____________________________________________ 3.3.3 Specifying the Target Disk The procedure next asks you for the name of the target disk. If you enter a question mark (?), the system displays a list of devices on your system. Select the appropriate disk and respond to the prompt. For example: You must enter the device name for the target disk on which OpenVMS Alpha will be installed. Enter device name for target disk: (? for choices) DKB400 If you select a device that is not available or that cannot be used for some other reason, the system displays information indicating why the device cannot be used. For example, if you enter MKA500, a tape device, a message similar to the following is displayed: MKA500 is not a disk device 3.3.4 Specifying the Volume Label The system then prompts you for the volume label and asks if the information is correct. You can keep the label already assigned to the disk, accept the default label assigned by the system (ALPHASYS), or specify a different volume label (with a limit of 12 characters that can be letters A-Z, numbers 0-9, dollar signs ($), hyphens (-), or underscores (_)). 3-10 Installing the OpenVMS Alpha Operating System Installing the OpenVMS Alpha Operating System 3.3 Creating the System Disk ________________________ Note ________________________ Compaq strongly recommends that the volume labels for all disks on your system or OpenVMS Cluster have unique labels. If a disk that has the same label as the system disk is mounted, various OpenVMS components will not function as intended. ______________________________________________________ After you select the volume label and choose to continue by answering Yes to the next prompt, the target disk is initialized and mounted, and page and swap files are created. For example: DKB400: is now labeled ALPHASYS. The existing label causes problems for OpenVMS. You must enter a new label. Enter volume label for target system disk: [ALPHASYS] alphainsv You have chosen to install OpenVMS Alpha on a new disk. The target system disk, DKB400:, will be initialized. It will be labeled ALPHAINSV. Any data currently on the target system disk will be lost. Is this OK? (yes/No) y Initializing and mounting target.... Creating page and swap files.... 3.3.5 Setting the SYSTEM Account Password Before you respond to the system prompt asking you to enter a password for the SYSTEM account, note the following: 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 valid password. o Reenter the password for verification. Installing the OpenVMS Alpha Operating System 3-11 Installing the OpenVMS Alpha Operating System 3.3 Creating the System Disk The following is a sample display: You must enter a password for the SYSTEM account. The password must be a minimum of 8 characters in length, and may not exceed 31 characters. It will be checked and verified. The system will not accept passwords that can be guessed easily. The password will not be displayed as you enter it. Password for SYSTEM account: Reenter SYSTEM password for verification: If you reenter the password incorrectly or if the system determines that the password is too easy for another user to guess, the system displays an error message and gives you the opportunity to specify a valid password. 3.3.6 Becoming a Cluster Member The procedure now asks if your system will be part of a cluster. The display is similar to the following: Will this system be a member of an OpenVMS Cluster? (Yes/No) Yes Answering Yes to this question causes SYS$MANGER:CLUSTER_ CONFIG.COM to run automatically when your newly installed system is first booted. The CLUSTER_CONFIG procedure will ask a series of questions about the cluster. If you answer No to the cluster question, the system can still be a member of an OpenVMS Cluster. However, in this case you will have to explicitly configure the cluster when your newly installed system is first booted. You can do this by executing a command similar to the following: $ @SYS$MANGER:CLUSTER_CONFIG 3.3.7 Becoming an OpenVMS Galaxy Instance The procedure next asks if your system will be an instance in an OpenVMS Galaxy. The display is similar to the following: Will this system be an instance in an OpenVMS Galaxy? (Yes/No) Yes If you answer Yes to this question, and you also answered Yes to the OpenVMS Cluster question, information about required remedial kits is displayed. 3-12 Installing the OpenVMS Alpha Operating System Installing the OpenVMS Alpha Operating System 3.3 Creating the System Disk For compatibility with OpenVMS Galaxy, any systems in the OpenVMS Cluster that are running versions of OpenVMS prior to Version 7.1-2 must have a remedial kit installed. The following display indicates the correct remedial kits for various OpenVMS Alpha and VAX systems. For compatibility with OpenVMS Galaxy, any systems in the OpenVMS Cluster that are running versions of OpenVMS prior to Version 7.1-2 must have a remedial kit installed. The appropriate kit from the following list must be installed on all system disks used by these systems. (Later versions of these remedial kits may be used if available.) Alpha V7.1 and V7.1-1xx ALPSYSB02_071 Alpha V6.2 and V6.2-1xx ALPSYSB02_062 VAX V7.1 VAXSYSB01_071 VAX V6.2 VAXSYSB01_062 3.3.8 MEMORY CHANNEL Information This section contains information specific to becoming a cluster member in a MEMORY CHANNEL environment. The MEMORY CHANNEL remedial kit (ALPMC01_071 and later) changed the data structures used with MEMORY CHANNEL. This change is not backwardly compatible and requires special considerations for MEMORY CHANNEL when upgrading OpenVMS from a version earlier than Version 7.1-2 to Version 7.1-2 (or later), under the following conditions: o Your upgraded system disk will be part of an OpenVMS Cluster, and o One or more of the systems in the OpenVMS Cluster has a MEMORY CHANNEL adapter, and o Either: - Your OpenVMS Cluster uses multiple system disks, or - You will be performing a rolling upgrade If your target system is already at OpenVMS Version 7.2 or later, you have already resolved this configuration issue. In this case, or if you indicated that the target system will not be a member of an OpenVMS Cluster, the procedure jumps to Section 3.3.9. Otherwise, it proceeds as follows: Installing the OpenVMS Alpha Operating System 3-13 Installing the OpenVMS Alpha Operating System 3.3 Creating the System Disk An OpenVMS Cluster may use more than one system disk, either on a continuing basis, or only during a rolling upgrade. Will the OpenVMS Cluster use more than one system disk? (Yes/No) Yes If you answer Yes to this question, the procedure provides information about MEMORY CHANNEL adapters, as follows: A MEMORY CHANNEL adapter is a device that allows systems in an OpenVMS Cluster to be connected (usually through a MEMORY CHANNEL hub) to provide high speed communications among nodes in the OpenVMS Cluster. If the procedure can detect that a MEMORY CHANNEL adapter (MCA) is present, it displays the following message: This system has a MEMORY CHANNEL adapter. Otherwise, it displays a question similar to the following: Is a MEMORY CHANNEL adapter installed on this system or on any other system in the OpenVMS Cluster? (Yes/No) Yes If you answer yes to this question, or your system has a MEMORY CHANNEL adapter, the following information is displayed: You will be using multiple system disks and MEMORY CHANNEL adapters. This requires special consideration in order to avoid data corruption. Either the ALPMC01_071 TIMA kit must be installed on all system disks, or you must not use the MEMORY CHANNEL until after all system disks in the OpenVMS Cluster have been upgraded to the new OpenVMS release and all systems have re-booted from the upgraded system disks. You can prevent using MEMORY CHANNEL in one of two ways: o Power off the MEMORY CHANNEL hub, if one is used, or o Disconnect the MEMORY CHANNEL cable, if using a virtual hub. You must NOT POWER UP OR RECONNECT until after all system disks in the OpenVMS Cluster have been upgraded to the new OpenVMS release and all systems have re-booted from the upgraded system disks. You can search [VMS$COMMON.SYSUPD]VMSINSTAL.HISTORY for ALPMC on any system disk to determine if the TIMA kit is installed on that disk. Answer the next question with a "?" if you wish to search VMSINSTAL.HISTORY for the ALPMC01_071 TIMA kit. 3-14 Installing the OpenVMS Alpha Operating System Installing the OpenVMS Alpha Operating System 3.3 Creating the System Disk Do you have the ALPMC01_071 TIMA kit installed on all systems disks that are part of the OpenVMS Cluster and that are prior to OpenVMS V7.2? (Yes/No) No If you answer with a question mark (?), the OpenVMS SEARCH command is used to look in VMSINSTAL.HISTORY for the ALPMC01_071 remedial kit. If the kit is found, the line in VMSINSTAL.HISTORY that contains it is displayed. If it is not found, the message "No strings matched" is displayed. In either case, the question is repeated. Answer Yes if the ALPMC01_071 remedial kit is installed as required on all system disks. Otherwise, answer No. If you answer No, the procedure continues as follows: Have you powered off the MEMORY CHANNEL hub? (Or disconnected the MEMORY CHANNEL cable?) (Yes/No) No Answer Yes if you have powered off the MEMORY CHANNEL hub or disconnected the MEMORY CHANNEL cable. Otherwise, answer No. If you answer No, the procedure continues as follows: Before proceeding with the OpenVMS upgrade, you must either o Install the ALPMC01_071 TIMA kit on all system disks that are part of the OpenVMS Cluster, or o Take action to prevent using MEMORY CHANNEL. Termination is strongly recommended. Do you want to terminate? (Yes/No) [YES] ________________________ Note ________________________ If termination is recommended, do not attempt to continue. Follow the instructions provided in this section and with the ALPMC01_071 remedial kit. If you continue, MEMORY CHANNEL will not work correctly and you will encounter problems, including possible data corruption. ______________________________________________________ The installation will not recommend terminating if o The system will not be a member of an OpenVMS Cluster, or Installing the OpenVMS Alpha Operating System 3-15 Installing the OpenVMS Alpha Operating System 3.3 Creating the System Disk o The OpenVMS Cluster does not use more than one system disk, or o There is no MEMORY CHANNEL adapter in the OpenVMS Cluster, or o The ALPMC01_071 remedial kit is installed on all system disks in the OpenVMS Cluster, or o You have powered down the MEMORY CHANNEL hub or disconnected the MEMORY CHANNEL cables 3.3.9 Installing Windowing and Networking Products The procedure next asks if you want to install the following Compaq windowing and networking software: o DECwindows Motif for OpenVMS Alpha o DECnet-Plus for OpenVMS Alpha or DECnet Phase IV for OpenVMS Alpha o DIGITAL TCP/IP Services for OpenVMS This software is included with the OpenVMS Alpha operating system. You can change the default values for these products later in the installation procedure. ________________________ Note ________________________ The OpenVMS Alpha Version 7.2 installation menu offers the choice to install either DECnet-Plus or DECnet Phase IV networking software. However, you cannot have DECnet-Plus and DECnet Phase IV concurrently installed on your system. Install either DECnet-Plus or DECnet Phase IV. Once you have DECnet-Plus and TCP/IP installed on your system, you can run DECnet applications over your TCP/IP network. Please see the DECnet-Plus for OpenVMS Management Guide for more information on DECnet over TCP/IP. ______________________________________________________ 3-16 Installing the OpenVMS Alpha Operating System Installing the OpenVMS Alpha Operating System 3.3 Creating the System Disk The display is similar to the following: You can install the following products along with the OpenVMS operating system: o DECwindows Motif for OpenVMS Alpha o DECnet-Plus for OpenVMS Alpha o DECnet Phase IV for OpenVMS Alpha o DIGITAL TCP/IP Services for OpenVMS If you want to change your selections, you can do so later in the installation by answering "NO" to the following question: "Do you want the defaults for all product options?" Do you want to install DECwindows Motif for OpenVMS Alpha V1.2-5? (Yes/No) [YES] y Beginning with OpenVMS V7.1, the DECnet-Plus kit is provided with the OpenVMS operating system kit. Compaq recommends that DECnet users install DECnet-Plus. DECnet Phase IV applications are supported by DECnet-Plus. DECnet Phase IV is also provided as an option. Support for DECnet Phase IV is available through a Prior Version Support Contract available through Compaq's MCS Services. If you install DECnet-Plus and TCP/IP you can run DECnet applications over a TCP/IP network. Please see the OpenVMS Management Guide for information on running DECnet over TCP/IP. Do you want to install DECnet-Plus for OpenVMS Alpha V7.2? (Yes/No) [YES] y Do you want to install Digital TCP/IP Services for OpenVMS V5.0-9? (Yes/No) [YES] n Note that if you answer No to the prompt to install DECnet- Plus, you will be prompted to install DECnet Phase IV. Installing the OpenVMS Alpha Operating System 3-17 Installing the OpenVMS Alpha Operating System 3.3 Creating the System Disk 3.3.10 Setting System Parameters The procedure now asks you to set values for the parameters SCSNODE and SCSSYSTEMID. SCSNODE is a name that can be from 1 to 6 letters or numbers; it must include at least one letter. If this system is part of an OpenVMS Cluster, then SCSNODE must be unique within the cluster. If you are using DECnet Phase IV or DECnet-Plus with DECnet Phase IV addresses, then SCSNODE must be the same as your DECnet node name. SCSSYSTEMID must also be unique within an OpenVMS Cluster. In addition, if you are using DECnet Phase IV or DECnet- Plus with DECnet Phase IV addresses, then SCSSYSTEMID depends on the DECnet Phase IV address that your system is using. The following is an example of the display and valid responses: For your system to operate properly, you must set two parameters: SCSNODE and SCSSYSTEMID. SCSNODE can be from 1 to 6 letters or numbers. It must contain at least one letter. If you plan to use DECnet, SCSNODE must be the DECnet Phase IV node name, or the DECnet-Plus (Phase V) node synonym. If you have multiple OpenVMS systems, the SCSNODE on each system must be unique. Enter SCSNODE: alpcsi If you plan to use DECnet, SCSSYSTEMID must be set based on the DECnet Phase IV address. DECnet Phase IV addresses are in the format DECnet_area_number.DECnet_node_number DECnet_area_number is a number between 1 and 63. DECnet_node_number is a number between 1 and 1023. If you plan to use DECnet WITHOUT Phase IV compatible addresses, enter 0.0. Enter DECnet (Phase IV) Address [1.1]: 63.180 SCSSYSTEMID will be set to 64692. 3-18 Installing the OpenVMS Alpha Operating System Installing the OpenVMS Alpha Operating System 3.3 Creating the System Disk This was calculated as follows: (DECnet_area_number * 1024) + DECnet_node_number If you are not using DECnet, or if you enter 0.0 as the DECnet Phase IV address, you are prompted to enter a SCSSSYSTEMID in the range of 1 to 65535. If this is a standalone system, the default 65534 is acceptable. However, if this system is part of an OpenVMS Cluster, you must enter a unique SCSSYSTEMID. The following is a sample display: Please choose a SCSSYSTEMID between 1 and 65535. If you have multiple OpenVMS systems, the SCSSYSTEMID on each system must be unique. Enter SCSYSTEMID [65535]: 12345 3.3.11 Updating Time Zone Information At this point in the installation, the procedure asks you for information that is used for providing local time zone support. For local time zone support to work correctly, the installation procedure must set the time zone that accurately describes the location you want to be considered as your default time zone. Usually, this is the time zone in which your system is running. In addition, your system must be correctly configured to use a valid OpenVMS time differential factor (TDF). The procedure displays a series of time zone menus and prompts you to make selections from each. Begin by selecting the desired time zone from the main time zone menu. If you do not select a time zone, the default is Greenwich Mean Time (GMT). If you choose a time zone that has subcomponents, the system displays an additional menu. For example, if you choose the United States (US) time zone from the main menu, a second menu displays the specific time zones within the United States. You then select the menu item that best represents the desired time zone. The procedure then prompts you for the TDF. The TDF is the difference between your system time and Coordinated Universal Time (UTC), which is an international standard (similar to Greenwich Mean Time) for measuring time of day. The procedure supplies a default for TDF, which is generally the correct response. Installing the OpenVMS Alpha Operating System 3-19 Installing the OpenVMS Alpha Operating System 3.3 Creating the System Disk The following is a sample display: Configuring the Local Time Zone TIME ZONE SPECIFICATION -- Main Time Zone Menu 1) Australia 11) GMT 21) Mexico 31) Turkey 2) Brazil 12) Greenwich 22) NZ 32) UCT 3) CET 13) Hongkong 23) NZ-CHAT 33) US 4) Canada 14) Iceland 24) Navajo 34) UTC 5) Chile 15) Iran 25) PRC 35) Universal 6) Cuba 16) Israel 26) Poland 36) W-SU 7) EET 17) Jamaica 27) ROC 37) WET 8) Egypt 18) Japan 28) ROK 38) Zulu 9) Factory 19) Libya 29) Singapore 10) GB-Eire 20) MET 30) SystemV 0) None of the above Select the number above that best represents the desired time zone: 33 You selected US as your time zone. Is this correct? (Yes/No) [YES]: US Time Zone Menu 1) Alaska 4) Central 7) Hawaii 10) Mountain 2) Aleutian 5) East-Indiana 8) Indiana-Starke 11) Pacific 3) Arizona 6) Eastern 9) Michigan 12) Samoa 0) None of the above Select the number above that best represents the desired time zone: 6 You selected US/Eastern as your time zone. Is this correct? (Yes/No) [YES]: Default Time Differential Factor for standard time is -5:00. Default Time Differential Factor for daylight saving time is -4:00. The Time Differential Factor (TDF) is the difference between your system time and Coordinated Universal Time (UTC). UTC is similar in most respects to Greenwich Mean Time (GMT). The TDF is expressed as hours and minutes, and should be entered in the hh:mm format. TDFs for the Americas will be negative (-3:00, -4:00, etc.); TDFs for Europe, Africa, Asia and Australia will be positive (1:00, 2:00, etc.). Is Daylight Savings time in effect? (Yes/No): y 3-20 Installing the OpenVMS Alpha Operating System Installing the OpenVMS Alpha Operating System 3.3 Creating the System Disk Enter the Time Differential Factor [-4:00]: NEW SYSTEM TIME DIFFERENTIAL FACTOR = -4:00. Is this correct? [Y]: For more information about TDF and local time zone support, see the OpenVMS System Manager's Manual. 3.4 Registering Licenses Before you can use the OpenVMS Alpha operating system and its components, you must register all licenses in one of two ways: o During the installation (which Compaq recommends), by responding to the prompts displayed by the SYS$UPDATE:VMSLICENSE.COM procedure. This procedure is executed if you answer Yes (the default) to the following question: Do you want to register any Product Authorization Keys? o After the installation, by using the LICENSE REGISTER command or by invoking SYS$UPDATE:VMSLICENSE.COM. In addition to reviewing the license information provided in this chapter, you can also refer to the following: o Appendix C, which contains notes and supplemental information about licenses and licensing procedures o The OpenVMS License Management Utility Manual, which contains complete, detailed information about the licensing procedure 3.4.1 Types of OpenVMS Alpha Licenses The operating system uses one or more of the following types of licenses, depending on your hardware and software configuration. ________________________ Note ________________________ All OpenVMS Alpha Base and SMP licenses include the NO_SHARE attribute and remain with the initial host computer. ______________________________________________________ Installing the OpenVMS Alpha Operating System 3-21 Installing the OpenVMS Alpha Operating System 3.4 Registering Licenses _________________________________________________________________ Type_of_License____________Description___________________________ Operating System Base Grants the right to noninteractive License use of the remote batch, print, application, and computing services of the operating system on a single processor and authorizes one direct login (for system management purposes only). This license is a prerequisite for OpenVMS Alpha Interactive User Licenses. Interactive User Grant the right to interactive Licenses use of the OpenVMS Alpha operating system, provided you have previously installed the appropriate OpenVMS Alpha Operating System Base License on your Alpha computer. These licenses, which are concurrent, are available in any quantity desired or as an unlimited user license. You can add interactive users to the computer at any time by specifying the same node name on the additional Interactive User License PAK and by following the license combination procedure described in the OpenVMS License Management Utility Manual. 3-22 Installing the OpenVMS Alpha Operating System Installing the OpenVMS Alpha Operating System 3.4 Registering Licenses _________________________________________________________________ Type_of_License____________Description___________________________ Symmetric Upgrades the Operating System Base Multiprocessing License and all Interactive User (SMP) Extension to the licenses (including Unlimited) to Operating System Base the matching multiprocessing level of License your DEC 4000 or DEC 7000 series Alpha computer. Because the Symmetric Multiprocessing (SMP) Extension grants all the rights the existing Base and User licenses provided at the uniprocessing level, you do not need to reinstall those licenses when you upgrade to a multiprocessing system. Each time you upgrade your system to a new multiprocessing level (for example, from a DEC 7000 Model 620 Alpha system to a DEC 7000 Model 630 Alpha system), you add an SMP Extension to your ___________________________existing_licenses.____________________ 3.4.2 How to Register Licenses After you install the OpenVMS Alpha operating system, the system displays the following message: If you have Product Authorization Keys (PAKs) to register, you can register them now. Do you want to register any Product Authorization Keys? (Yes/No) [Yes] Respond to the prompt as follows: Installing the OpenVMS Alpha Operating System 3-23 Installing the OpenVMS Alpha Operating System 3.4 Registering Licenses ___________________________________________________________ IF_...________________THEN_..._____________________________ you choose to do the following: register your 1. Be sure you review Appendix C licenses at this and have the OpenVMS License time (which Compaq Management Utility Manual recommends), available. 2. Be sure you have a copy of the Product Authorization Key (PAK) for each license that you will register. 3. Type Y and press the Return key. 4. Register your licenses, as described in the next section. you choose not do the following: 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 Section 3.5. 3. After completing the installation, register your licenses using the LICENSE REGISTER command or by invoking SYS$UPDATE:VMSLICENSE.COM before performing any other postinstallation tasks. ___________________________________________________________ 3.4.3 Using the Licensing Procedure Entering Y (Yes) to register your licenses during the installation invokes the SYS$UPDATE:VMSLICENSE.COM procedure, which displays the following message: VMS License Management Utility Options: 3-24 Installing the OpenVMS Alpha Operating System Installing the OpenVMS Alpha Operating System 3.4 Registering Licenses 1. REGISTER a Product Authorization Key 2. AMEND an existing Product Authorization Key 3. CANCEL an existing Product Authorization Key 4. LIST Product Authorization Keys 5. MODIFY an existing Product Authorization Key 6. DISABLE an existing Product Authorization Key 7. DELETE an existing Product Authorization Key 8. COPY an existing Product Authorization Key 9. MOVE an existing Product Authorization Key 10. ENABLE an existing Product Authorization Key 11. SHOW the licenses loaded on this node 12. SHOW the unit requirements for this node 99. Exit this procedure Type '?' at any prompt for a description of the information requested. Press Ctrl/Z at any prompt to return to this menu. Enter one of the above choices [1] 1. Select the appropriate options (beginning with 1, as indicated in the display) until you have successfully registered all required PAKs. 2. After you register all your licenses, exit from the License Management procedure by entering option 99. 3.5 Completing the Installation The following sections describe the remaining steps that you need to perform to complete the installation. 3.5.1 Choosing Descriptive Help Text Next, the system prompts you as follows: The installation can provide brief or detailed descriptions. 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 additional explanatory text with each prompt. Installing the OpenVMS Alpha Operating System 3-25 Installing the OpenVMS Alpha Operating System 3.5 Completing the Installation 3.5.2 Selecting Components The system next displays the following message, indicating that the procedure is ready to install the operating system: The following product has been selected: DEC AXPVMS OPENVMS V7.2 Platform (product suite) Configuration phase starting ... You will be asked to choose options, if any, for each selected product and for any products that may be installed to satisfy software dependency requirements. DEC AXPVMS OPENVMS V7.2: OpenVMS and related products Platform COPYRIGHT (c) 12-SEP-1998 -- All rights reserved Compaq Computer Corporation After the system displays a series of additional messages, the procedure prompts you to choose the default values for all the options and suboptions for each component included in the operating system. The display is similar to the following: Do you want the defaults for all options? [YES] When selecting components, note the following: o If you want all the default values, press the Return key. If you want to select components individually, answer NO. The system will then prompt you for each option and suboption. o If you are not sure whether you want certain options, request help by entering a question mark (?) at the prompt for that option. o After you select all the options you want, you will have an opportunity to view your selections and make changes (if necessary). o OpenVMS Management Station software is automatically installed on your OpenVMS system disk when you accept all the default values. If you do not accept the default values, you must select the OpenVMS Management Station component (server and client files) if you plan to use that product. After the installation is complete, you 3-26 Installing the OpenVMS Alpha Operating System Installing the OpenVMS Alpha Operating System 3.5 Completing the Installation can then prepare your OpenVMS Alpha system and your PC to run OpenVMS Management Station by following the procedures described in Appendix D. o If you decide after the installation to change which OpenVMS Alpha operating system options you want installed on your system, you must reconfigure the installation as described in Section 1.3.3.2. o After you boot the new system disk and log in, you can obtain information about individual system files by entering HELP SYSTEM_FILES at the dollar sign prompt ($). 3.5.3 List of Components The following components are included with the OpenVMS Alpha Version 7.2 operating system: Accounting Log Report Generator Utility Access Control List Utilities Print and Batch Queue Utilities DECdtm Distributed Transaction Manager Support for DECnet-Plus or DECnet for OpenVMS DECnet Incoming Remote File Access DECnet Incoming Remote Terminal DECnet Network Test DECnet Remote Task Loading Programming Support Debugger Utility Image Dump Utility RMS Analyze and FDL Editor Utilities Message Utility System Shareable Image and Object Module Libraries Macro libraries Macro-32 Migration Compiler TLB intermediary form of STARLET Fortran Require Files C Object Libraries C Header Files VMS text libraries of Ada declarations RMS Journaling Recovery Utility System Programming Support Support for ISO 9660 and High Sierra CD-ROM Formats MONITOR Analyze Object File Utility Installing the OpenVMS Alpha Operating System 3-27 Installing the OpenVMS Alpha Operating System 3.5 Completing the Installation Delta Debugger System Dump Analyzer Utility Miscellaneous Symbol Table Files OpenVMS Management Station Software -- PC files Utilities OpenVMS Mail Utility Dump Utility DIGITAL Standard Runoff (DSR) Text Formatter Phone Utility Help Library Foreign Terminal Support LAT-11 Terminal Server (via Ethernet) Error Log Generator Utility Terminal Fallback Facility TECO Interactive Text Editor National Character Set Utility (NCS) DIAGNOSE Utility XPG4 Internationalization Utilities Bliss Require Files Example Files Message Facility Files (HELP/MESSAGE) Translated Image Support UETP Files Support for DECwindows DECwindows workstation files Video fonts 100 dots per inch video fonts Delete any obsolete OpenVMS files 3.5.4 Completing the Procedure When you have answered all the prompts and selected the components you want installed, the system allows you to review your selections (and make changes if necessary), then installs the product, provides informational messages, and returns you to the menu. The following is a sample display: ________________________ Note ________________________ If you perform two installations at the same time to systems connected by MEMORY CHANNEL, you may a message similar to the following every 5 seconds: 3-28 Installing the OpenVMS Alpha Operating System Installing the OpenVMS Alpha Operating System 3.5 Completing the Installation %PMA0 CPU00: 30-OCT-1998 14:58:40 Remote System Conflicts with Known System - REMOTE NODE %PMA0 CPU00: 30-OCT-1998 14:58:45 Remote System Conflicts with Known System - REMOTE NODE Disregard the message. The installation or upgrade will proceed normally and the messages will not be present when the system reboots with its actual node name. ______________________________________________________ Do you want to review the options? [NO] Execution phase starting ... The following products will be installed: DEC AXPVMS DECNET_OSI V7.2 Layered Product DEC AXPVMS DWMOTIF V1.2-5 Layered Product DEC AXPVMS OPENVMS V7.2 Platform (product suite) DEC AXPVMS VMS V7.2 Operating System Portion done: 0%...10%...20%...30%...40%...50%...60%...70% ...80%...90%...100% The following products have been installed: DEC AXPVMS DECNET_OSI V7.2 Layered Product DEC AXPVMS DWMOTIF V1.2-5 Layered Product DEC AXPVMS OPENVMS V7.2 Platform (product suite) DEC AXPVMS VMS V7.2 Operating System The installation is now complete. When the newly installed system is first booted, a special startup procedure will be run. This procedure will: o Configure the system for standalone or OpenVMS Cluster operation. o Run AUTOGEN to set system parameters. o Reboot the system with the newly set parameters. You may shut down now or continue with other operations. Process AXPVMS_INSTALL logged out at 12-SEP-1998 14:45:49.54 Press Return to continue... **************************************************************** Installing the OpenVMS Alpha Operating System 3-29 Installing the OpenVMS Alpha Operating System 3.5 Completing the Installation You can install or upgrade the OpenVMS Alpha operating system or you can install or upgrade layered products that are included on the OpenVMS Alpha operating system CD-ROM. You can also execute DCL commands and procedures to perform "standalone" tasks, such as backing up the system disk. Please choose one of the following: 1) Install or upgrade OpenVMS Alpha Version V7.2 2) Display products and patches that this procedure can install 3) Install or upgrade layered products and patches 4) Show installed products 5) Reconfigure installed products 6) Remove installed products 7) Execute DCL commands and procedures 8) Shut down this system Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?) If you want to install layered products, go to Section 3.6. If you do not want to install layered products or perform any other operations prior to booting the new system disk, choose option 8 from the menu to shut down the system. The system display is similar to the following: Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?) 8 Shutting down the system SYSTEM SHUTDOWN COMPLETE After you complete the installation and shut down the system, go to Section 3.7. 3.6 Installing Layered Products You can use the menu system included on the operating system CD-ROM to install certain layered products with the POLYCENTER Software Installation utility. You can view a list of the layered products that can be installed in this way by choosing option 2 from the menu. (To install layered products that are not listed, see Chapter 4 and the installation documentation for each layered product.) 3-30 Installing the OpenVMS Alpha Operating System Installing the OpenVMS Alpha Operating System 3.6 Installing Layered Products You may see the following product name while installing layered products: DEC AXPVMS UCX V4.2-PLACEHOLDER Do not attempt to install this kit. This is a "dummy" that is needed for technical reasons to facilitate upgrading from the prior UCX implementation of DIGITAL TCP/IP Services to the new implementation. If you do attempt to install this kit, the following message will be displayed: The UCX implementation of TCP/IP Services is obsolete and is not supported on OpenVMS V7.2 and higher versions. Starting with OpenVMS V7.2, the UCX implementation of TCP/IP services is replaced by the new TCPIP product. This is a placeholder kit to satisfy OpenVMS upgrade requirements so that UCX can be automatically upgraded to TCPIP. You cannot use this kit to install UCX. The installation will then terminate. You can install (or upgrade to) the new implementation of DIGITAL TCP/IP services, version 5.0, as part of the OpenVMS upgrade. If you wish to install version 5.0 separately, choose the product: DEC AXPVMS TCPIP V5.0-9 To install layered products using the POLYCENTER Software Installation utility, choose option 2 to view the list and then option 3 to perform the installation. For example: Please choose one of the following: 1) Upgrade, install or reconfigure OpenVMS Alpha Version V7.2 2) Display products and patches that this procedure can install 3) Install or upgrade layered products and patches 4) Show installed products 5) Reconfigure installed products 6) Remove installed products 7) Execute DCL commands and procedures 8) Shut down this system Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?) 2 Installing the OpenVMS Alpha Operating System 3-31 Installing the OpenVMS Alpha Operating System 3.6 Installing Layered Products The following versions of the OpenVMS operating system, the DECwindows graphical user interface and network products. are available on the OpenVMS Distribution compact disk. They can be installed by selecting choice 1: DEC AXPVMS VMS version V7.2 DEC AXPVMS DWMOTIF version V1.2-5 DEC AXPVMS DECNET_OSI version V7.2 DEC AXPVMS DECNET_PHASE_IV version V7.2 DEC AXPVMS TCPIP version V5.0-9 The following Layered Product kits are available on the OpenVMS Distribution Compact Disk. They can be installed by selecting choice 3. If already installed, they can be reconfigured by selecting choice 5, or removed by selecting choice 6. ----------------------------------- ----------- ---------- PRODUCT KIT TYPE KIT FORMAT ----------------------------------- ----------- ---------- DEC AXPVMS DECNET_OSI V7.2 Full LP Sequential DEC AXPVMS DECNET_PHASE_IV V7.2 Full LP Sequential DEC AXPVMS DWMOTIF V1.2-5 Full LP Sequential DEC AXPVMS TCPIP V5.0-9 Full LP Sequential DEC AXPVMS UCX V4.2-99PLACEHOLDER Full LP Sequential ----------------------------------- ----------- ---------- 5 items found Press Return to continue... **************************************************************** You can install or upgrade the OpenVMS Alpha operating system or you can install or upgrade layered products that are included on the OpenVMS Alpha operating system CD-ROM. You can also execute DCL commands and procedures to perform "standalone" tasks, such as backing up the system disk. Please choose one of the following: 3-32 Installing the OpenVMS Alpha Operating System Installing the OpenVMS Alpha Operating System 3.6 Installing Layered Products 1) Upgrade, install or reconfigure OpenVMS Alpha Version V7.2 2) Display products and patches that this procedure can install 3) Install or upgrade layered products and patches 4) Show installed products 5) Reconfigure installed products 6) Remove installed products 7) Execute DCL commands and procedures 8) Shut down this system Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?) 3 *********************************************************** If you choose to install or upgrade DECwindows Motif, please note the following: o If you did not select the OpenVMS DECwindows base support and workstation files options, DECwindows Motif will not run. You must add these options to use DECwindows Motif. o If you are upgrading DECwindows Motif from version V1.1 and want to save the OSF/Motif Release 1.1.3 programming files, DO NOT upgrade now. Instead, see the DECwindows Motif installation manual and follow the instructions for running PCSI_INSTALLATION.COM. If you choose to install or upgrade DECnet-Plus or DECnet Phase IV, please note the following: o If you did not select the OpenVMS DECNET option, neither version of DECnet will run. You must add this option to use DECnet. Press Return to continue... *********************************************************** The installation procedure will ask a series of questions. () - encloses acceptable answers [] - encloses default answers Type your response and press the Return key. Type: ? - to repeat an explanation ^ - to change prior input (not always possible) Ctrl-Y - to exit the installation procedure You must enter the device name for the target disk on which the layered product(s) installation will be performed. Enter device name for target disk: [DKB400:] (? for choices) Installing the OpenVMS Alpha Operating System 3-33 Installing the OpenVMS Alpha Operating System 3.6 Installing Layered Products DKB400: is labeled V72_TCPIPV50. The install operation can provide brief or detailed descriptions. In either case, you can request the detailed descriptions by typing "?". Do you always want detailed descriptions? (Yes/No) [No] 1 - DEC AXPVMS DECNET_OSI V7.2 Layered Product 2 - DEC AXPVMS DECNET_PHASE_IV V7.2 Layered Product 3 - DEC AXPVMS DWMOTIF V1.2-5 Layered Product 4 - DEC AXPVMS TCPIP V5.0-9 Layered Product 5 - DEC AXPVMS UCX V4.2-99PLACEHOLDER Layered Product 6 - All products listed above 7 - Exit Choose one or more items from the menu separated by commas: Note that the UCX V4.2-99PLACEHOLDER kit is not a valid UCX (TCP/IP) kit. It is present only to support upgrading UCX to the new TCPIP implementation of DIGITAL TCP/IP Services. Any attempt to install this PLACEHOLDER kit will terminate with an error. If you do not want to perform any other operations after you install the layered products, enter option 8 to shut down the system. The system display is similar to the following: Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?) 8 Shutting down the system SYSTEM SHUTDOWN COMPLETE After you complete the installation and shut down the system, go to the next section to boot the new system disk. 3.7 Booting the New System Disk After you have successfully installed the operating system, boot the new system disk, as described in the following sections. 3-34 Installing the OpenVMS Alpha Operating System Installing the OpenVMS Alpha Operating System 3.7 Booting the New System Disk 3.7.1 Preparing to Boot the New System Disk Before you boot the new system disk, you must do the following: 1. Halt the system by entering Ctrl/P or by pressing the Halt button. [1] 2. At the console prompt (>>>), enter the SET BOOTDEF_DEV command in the following format: SET BOOTDEF_DEV target-drive 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 the following command and press the Return key: >>> SET BOOTDEF_DEV DKA400 If the system disk is connected to a hierarchical storage device (HSx), the format for specifying that drive is different. For example, on a DEC 7000 series system connected to an HSC device, the command is similar to the following: >>> SET BOOTDEF_DEV DUA20.14.0.2.0 For more information about setting and showing the default boot device, see Section A.2.2 in Appendix A. 3.7.2 How to Boot the New System Disk To boot the system disk, enter the following command and press the Return key: >>> BOOT -FLAGS 0,0 When the system finishes booting, it displays informational messages that begin as follows: ____________________ [1] For more information about halting your Alpha computer, see Appendix A. Installing the OpenVMS Alpha Operating System 3-35 Installing the OpenVMS Alpha Operating System 3.7 Booting the New System Disk OpenVMS (TM) Alpha Operating System, Version V7.2 %DECnet-I-LOADED, network base image loaded, version = 05.0D.00 $! Copyright (c) 1998 Compaq Computer Corporation. All rights reserved. Installing required known files... Configuring devices... . . . 3.8 Joining an OpenVMS Cluster If during the installation, you previously answered Yes to the question about joining an OpenVMS Cluster, the system now asks a series of questions about your configuration (CI, DSSI, SCSI, local area, or mixed-interconnect). You might need to refer to OpenVMS Cluster Systems or Guidelines for OpenVMS Cluster Configurations to answer these questions. 3.8.1 OpenVMS Cluster Prompts Table 3-1 lists the OpenVMS Cluster prompts and suggested responses. Note that, depending on your responses and particular cluster configuration, some prompts will not be displayed. Table_3-1_Prompts_for_OpenVMS_Cluster_Configurations_____________ Question__________________________How_to_Respond_________________ Will this node be a cluster Enter Y. member (Y/N)? What is the node's DECnet node Enter the DECnet node name (for name? example, MYNODE). The DECnet node name may be from one to six alphanumeric characters in length and cannot include dollar signs or underscores. (continued on next page) 3-36 Installing the OpenVMS Alpha Operating System Installing the OpenVMS Alpha Operating System 3.8 Joining an OpenVMS Cluster Table_3-1_(Cont.)_Prompts_for_OpenVMS_Cluster_Configurations_____ Question__________________________How_to_Respond_________________ What is the node's DECnet node Enter the DECnet node address - address? for example, 2.2. Will the Ethernet be used for Enter N for a CI only or cluster communications (Y/N)? DSSI-only OpenVMS Cluster. Otherwise, answer Y. [1] Enter this cluster's group Enter a number in the range number: from 1 to 4095 or 61440 to 65535. Enter this cluster's password: Enter the cluster password. The password must be from 1 to 31 alphanumeric characters in length and may include dollar signs and underscores.[2] Reenter this cluster's password Reenter the password. for verification: Will MYNODE be a disk server Enter Y if you want local (Y/N)? disks to be served to the cluster (mandatory for local area and mixed-interconnect configurations). Refer to OpenVMS Cluster Systems for information on served cluster disks. Will MYNODE serve RFxx disks Enter a response appropriate (Y)? for your DSSI configuration, if such disks are available to your system. [1]The_Ethernet_may_not_be_required_for_communication_within_a___ local area OpenVMS Cluster system configured with FDDI devices. Within certain DSSI or CI mixed-interconnect configurations, neither the Ethernet nor FDDI may be required for communication. If your configuration fits either scenario, you can answer No (N) to this prompt. [2]If neither the Ethernet nor FDDI is being used for communication in your cluster configuration, you may not need to supply the cluster group number and password. (continued on next page) Installing the OpenVMS Alpha Operating System 3-37 Installing the OpenVMS Alpha Operating System 3.8 Joining an OpenVMS Cluster Table_3-1_(Cont.)_Prompts_for_OpenVMS_Cluster_Configurations_____ Question__________________________How_to_Respond_________________ Enter a value for MYNODE's In a CI only system (connected ALLOCLASS parameter: to a dual-ported disk), a DSSI-only system, or a local area or mixed-interconnect configuration where nodes serve DSSI or CI disks, enter the appropriate allocation class value (1 to 255). Otherwise, enter 0. For information about selecting the ALLOCLASS parameter, see OpenVMS Cluster Systems. Does this cluster contain a For CI only, SCSI, local quorum disk (Y/N)? area, and mixed-interconnect configurations, enter Y or N, depending on your configuration. For most DSSI systems, enter Y. However, if you are adding a two-system DSSI configuration to an existing cluster (in which case you might not need a quorum disk), you can answer N. If you enter Y, the system asks for the name of the quorum disk. Enter the device name of the quorum disk. Refer to OpenVMS Cluster Systems for information on __________________________________quorum_disks.__________________ 3.9 Running AUTOGEN The system next runs AUTOGEN to evaluate your hardware configuration and estimate typical work loads. AUTOGEN then sets system parameters, the sizes of page, swap, and dump files, and the contents of VMSIMAGES.DAT. When AUTOGEN finishes and you reboot your system, the installation procedure is complete. 3-38 Installing the OpenVMS Alpha Operating System Installing the OpenVMS Alpha Operating System 3.9 Running AUTOGEN The installation procedure displays messages similar to the following: AUTOGEN will now be run to compute the new SYSGEN parameters. The system will then shut down and reboot, and the installation or upgrade will be complete. After rebooting you can continue with such system management tasks as: Decompressing the System Libraries Configuring DECnet Using SYS$MANAGER:CLUSTER_CONFIG.COM to create an OpenVMS Cluster Creating FIELD, SYSTEST, and SYSTEST_CLIG accounts if needed %AUTOGEN-I-BEGIN, GETDATA phase is beginning. %AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:PARAMS.DAT has been created. You may wish to purge this file. %AUTOGEN-I-END, GETDATA phase has successfully completed. %AUTOGEN-I-BEGIN, GENPARAMS phase is beginning. %AUTOGEN-I-NEWFILE, A new version of SYS$MANAGER:VMSIMAGES.DAT has been created. You may wish to purge this file. %AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:SETPARAMS.DAT has been created. You may wish to purge this file. %AUTOGEN-I-END, GENPARAMS phase has successfully completed. %AUTOGEN-I-BEGIN, GENFILES phase is beginning. %SYSGEN-I-EXTENDED, SYS$SYSROOT:[SYSEXE]PAGEFILE.SYS;1 extended %SYSGEN-I-EXTENDED, SYS$SYSROOT:[SYSEXE]SWAPFILE.SYS;1 extended %SYSGEN-I-CREATED, SYS$SYSROOT:[SYSEXE]SYSDUMP.DMP;1 created %AUTOGEN-I-REPORT, AUTOGEN has produced some informational messages that have been stored in the file SYS$SYSTEM:AGEN$PARAMS. REPORT. You may wish to review the information in that file. %AUTOGEN-I-END, GENFILES phase has successfully completed. %AUTOGEN-I-BEGIN, SETPARAMS phase is beginning. . . . Installing the OpenVMS Alpha Operating System 3-39 Installing the OpenVMS Alpha Operating System 3.10 Rebooting the System 3.10 Rebooting the System After AUTOGEN finishes, the system shuts down, displaying messages similar to the following: The system is shutting down to allow the system to boot with the generated site-specific parameters and installed images. The system will automatically reboot after the shutdown and the installation will be complete. SHUTDOWN -- Perform an Orderly System Shutdown on node ALPCSI %SHUTDOWN-I-BOOTCHECK, performing reboot consistency check... %SHUTDOWN-I-CHECKOK, basic reboot consistency check completed . . . 3.10.1 Rebooting the System Manually If the system does not reboot automatically, reboot the system manually. For example, if the system disk is on an RZ25 disk drive with a unit number of 1, enter the following command and press the Return key: >>> BOOT DKA1 After the system reboots, a message similar to the following is displayed: OpenVMS (TM) Alpha Operating System, Version V7.2 Copyright (c) 1998 Compaq Computer Corporation. All rights reserved. %STDRV-I-STARTUP, OpenVMS startup begun at 12-SEP-1998 14:50:18.35 . . . The system next displays informational messages and accounting information indicating that your OpenVMS Alpha operating system is running. For example: 3-40 Installing the OpenVMS Alpha Operating System Installing the OpenVMS Alpha Operating System 3.10 Rebooting the System %SET-I-INTSET, login interactive limit = 64, current interactive value = 0 SYSTEM job terminated at 12-SEP-1998 14:51:23.47 Accounting information: Buffered I/O count: 2177 Peak working set size: 6848 Direct I/O count: 1358 Peak page file size: 179552 Page faults: 1805 Mounted volumes: 0 Charged CPU time: 0 00:00:13.37 Elapsed time: 0 00:01:06.20 At this time, you can log in to the SYSTEM account (so you can perform postinstallation tasks), as described in the following sections. Installing the OpenVMS Alpha Operating System 3-41 Installing the OpenVMS Alpha Operating System 3.11 Logging in to the SYSTEM Account By Means of a Character Cell Terminal 3.11 Logging in to the SYSTEM Account By Means of a Character Cell Terminal Log in to a character cell terminal by entering the user name SYSTEM followed by the password. The display is similar to the following: OpenVMS (TM) Alpha Operating System, Version V7.2 Username: SYSTEM Password: . . . OpenVMS (TM) Alpha Operating System, Version V7.2 (If you forget your password, follow the instructions in Appendix A to perform an emergency startup.) 3.12 Logging in to the SYSTEM Account By Means of a Workstation If you installed the DECwindows Motif for OpenVMS Alpha software on your workstation, do the following after the login window displays on your screen: 1. Enter the user name SYSTEM followed by the password. 2. Click on the OK button. 3.13 What to Do Next After you have successfully installed the OpenVMS Alpha operating system and logged in to the SYSTEM account, you must perform certain postinstallation tasks before you can use the system. For complete information, go to Chapter 4. 3-42 Installing the OpenVMS Alpha Operating System 4 _________________________________________________________________ After Installing the OpenVMS Alpha Operating System After you have installed the OpenVMS Alpha operating system, you must perform several important tasks to prepare the system for operation. This chapter describes the following postinstallation tasks in the order in which you perform them: o Registering licenses o Creating accounts o Backing up the system disk o Customizing the system o Configuring and starting networking software o Testing the system with UETP o Decompressing the system libraries o Adding and removing files o Preparing your OpenVMS Alpha system and your PC to run OpenVMS Management Station o Installing layered products o Installing DIGITAL OpenVMS Debugger clients on a PC o Backing up the customized system disk o Configuring a multihead system o Running AUTOGEN o Using the postinstallation checklist After Installing the OpenVMS Alpha Operating System 4-1 After Installing the OpenVMS Alpha Operating System 4.1 Registering Your Licenses 4.1 Registering Your Licenses The installation procedure gave you the opportunity to register any software product licenses. If you did not register your OpenVMS Alpha licenses at that time, you must do so before you can use the OpenVMS Alpha operating system. You must also register the licenses for OpenVMS Alpha layered products. You can invoke the OpenVMS License utility by entering the following command: $ @SYS$UPDATE:VMSLICENSE (You can also use the LICENSE REGISTER command.) For information about registering licenses, see the following: o Section 3.4 o Appendix C o The OpenVMS License Management Utility Manual 4.2 Creating Accounts During the installation, DEFAULT and SYSTEM accounts are created for you automatically. However, if you plan to have Compaq service representatives test your system or if you plan to run testing software such as UETP, you must create accounts for each representative and a SYSTEST (standalone system) or SYSTEST_CLIG (OpenVMS Cluster system) account to run UETP. For complete information about creating accounts for Compaq service representatives and UETP, see the OpenVMS System Manager's Manual: Essentials. 4.3 Backing Up Your System Disk After you install the operating system, protect your work by making a backup copy of the system disk in case you have any problems while customizing it. To back up the system disk: 1. Shut down the system (described in Appendix A). 4-2 After Installing the OpenVMS Alpha Operating System After Installing the OpenVMS Alpha Operating System 4.3 Backing Up Your System Disk 2. Boot the operating system CD-ROM (locally or from the InfoServer). 3. Use the menu system to enter the DCL environment (option 7). 4. Mount the system disk and the target device on which you will make the backup copy. 5. Enter backup commands to back up the system disk to supported media. 6. Log out from the DCL environment. 7. Shut down the system by selecting option 8 from the menu. 8. Boot from the system disk. In addition to backing up the system disk now before you customize it, you should back up your system disk again after you successfully complete your customization tasks and install layered products. For complete information about backup operations, including a description of an alternate method that does not require booting from the operating system CD-ROM and that allows you to back up a shadowed disk without disabling the shadow set, see Appendix B. 4.4 Customizing the System You can customize the system to meet your site-specific needs. In addition, if your Alpha computer is part of an OpenVMS Cluster environment, you must prepare the cluster environment and configure the cluster. For instructions on customizing the system, review the following documentation: o If the computer is part of an OpenVMS Cluster environment, refer to OpenVMS Cluster Systems for further information about setting up a cluster. o The release notes, for notes and restrictions that might be relevant to your customization plans. After Installing the OpenVMS Alpha Operating System 4-3 After Installing the OpenVMS Alpha Operating System 4.4 Customizing the System o The OpenVMS System Manager's Manual, for instructions on customizing and using your system. You will find information about the following tasks: - Editing the template files SYCONFIG.COM, SYLOGICALS.COM, SYLOGIN.COM, and SYSTARTUP_VMS.COM - Starting the queue manager and creating a queue database - Setting up user accounts - Adjusting system parameters - Setting up your system to run DECdtm services o Section 4.5. ________________________ Note ________________________ If you have installed the DECwindows Motif for OpenVMS Alpha layered product (see Section 4.10), you can customize your DECwindows environment. ______________________________________________________ 4.5 Configuring and Starting Networking Software The following sections describe how to configure and start your networking software. 4.5.1 DECnet-Plus for OpenVMS Alpha If you installed DECnet-Plus for OpenVMS Alpha software, refer to the DECnet-Plus for OpenVMS Release Notes and DECnet-Plus for OpenVMS Installation and Basic Configuration for postinstallation instructions. 4.5.2 DECnet Phase IV for OpenVMS Alpha ________________________ Note ________________________ Support for DECnet Phase IV is only available under Compaq's Prior Version Support Program. Contact your local Compaq support representative for additional information. ______________________________________________________ 4-4 After Installing the OpenVMS Alpha Operating System After Installing the OpenVMS Alpha Operating System 4.5 Configuring and Starting Networking Software If you plan to run DECnet Phase IV for OpenVMS Alpha software, note the following: o After you have registered the license for the DECnet Phase IV for OpenVMS Alpha software, execute the interactive command procedure SYS$MANAGER:NETCONFIG.COM to automatically configure your system for networking. See the DECnet for OpenVMS Guide to Networking for instructions on using NETCONFIG.COM. o After you start the queue manager (see the OpenVMS System Manager's Manual), edit the commands in SYS$COMMON:[SYSMGR]SYSTARTUP_VMS.COM that pertain to networking so that the DECnet Phase IV for OpenVMS Alpha software starts automatically when your system is booted. Edit the file as follows: - If you have batch queues set up on your system, choose the following command by removing the comment delimiter (!) from the command line. Enabling this command allows the system to start up more quickly and decreases the amount of time you must wait to log in. !$ SUBMIT SYS$MANAGER:STARTNET.COM - If you do not have batch queues set up on your system, remove the comment delimiter (!) from the following lines: $! DECNET_VERSION = F$INTEGER(F$EXTRACT(2,2,F$GETSYI("DECNET_VERSION"))) $! IF DECNET_VERSION .GE. 5 $! THEN $! START/NETWORK "DECNET/OSI" $! ELSE $! START/NETWORK DECNET $! ENDIF o If you plan to run both DECnet Phase IV for OpenVMS Alpha and DECwindows software, you must also edit SYS$COMMON:[SYSMGR]SYSTARTUP_VMS.COM to add a comment delimiter (!) immediately following the dollar sign ($) in the following command: $ DEFINE DECW$IGNORE_DECNET TRUE After Installing the OpenVMS Alpha Operating System 4-5 After Installing the OpenVMS Alpha Operating System 4.5 Configuring and Starting Networking Software If you are not going to start the DECnet Phase IV for OpenVMS Alpha software or have not yet started it, this command tells the DECwindows software not to wait for the DECnet Phase IV for OpenVMS Alpha software. 4.5.3 DIGITAL TCP/IP Services for OpenVMS If you installed DIGITAL TCP/IP for OpenVMS software, refer to the DIGITAL TCP/IP Services for OpenVMS Installation and Configuration manual for information about how to configure this software using the TCPIP$CONFIG.COM procedure. 4.6 Testing the System with UETP The User Environment Test Package (UETP) is a software package designed to test whether the OpenVMS Alpha operating system is installed correctly. As part of the postinstallation procedure, Compaq recommends that you run UETP to verify the installation. For complete information about using UETP, see the OpenVMS System Manager's Manual. 4.7 Decompressing the System Libraries Decompressing the system libraries gives the system faster access to them. The decompressed libraries require several thousand additional blocks of disk space for all libraries to be decompressed. You use the LIBDECOMP.COM procedure to decompress the libraries. 4.7.1 Determining Disk Space To find out how much disk space you have, enter the following command and press the Return key: $ SHOW DEVICE SYS$SYSDEVICE If you have approximately 30,000 free blocks on the disk, you can decompress the libraries. Note that you can choose to decompress only the libraries that are used frequently. 4-6 After Installing the OpenVMS Alpha Operating System After Installing the OpenVMS Alpha Operating System 4.7 Decompressing the System Libraries 4.7.2 Methods of Using LIBDECOMP.COM You can use the LIBDECOMP.COM procedure to decompress libraries in three ways: o Entering a command and responding to prompts from the procedure o Entering an interactive command o Entering a batch command The following sections describe each method. ________________________ Note ________________________ Before you use the LIBDECOMP.COM procedure, be sure you are logged in to the SYSTEM account. ______________________________________________________ 4.7.3 Responding to LIBDECOMP.COM Prompts If you want to decompress libraries by responding to prompts from the LIBDECOMP.COM procedure, do the following: 1. Enter the following command and then press the Return key: $ @SYS$UPDATE:LIBDECOMP.COM The following information is displayed: OpenVMS Library Decompression Utility 1 HELPLIB.HLB 14 NCPHELP.HLB 27 PHONEHELP.HLB 2 STARLET.OLB 15 SDA.HLB 28 LIB.MLB 3 ACLEDT.HLB 16 SHWCLHELP.HLB 29 STARLET.MLB 4 ANLRMSHLP.HLB 17 SYSGEN.HLB 30 STARLETSD.TLB 5 DBG$HELP.HLB 18 ANALAUDIT$HELP.HLB 31 SYS$STARLET_C.TLB 6 DBG$UIHELP.HLB 19 SYSMANHELP.HLB 32 ERFLIB.TLB 7 DISKQUOTA.HLB 20 TFF$TFUHELP.HLB 33 SYS$LIB_C.TLB 8 EDFHLP.HLB 21 EXCHNGHLP.HLB 34 VAXCCURSE.OLB 9 INSTALHLP.HLB 22 TPUHELP.HLB 35 VAXCRTL.OLB 10 LATCP$HELP.HLB 23 EVE$HELP.HLB 36 VAXCRTLD.OLB 11 MAILHELP.HLB 24 EVE$KEYHELP.HLB 37 VAXCRTLT.OLB 12 MNRHELP.HLB 25 UAFHELP.HLB 38 IMAGELIB.OLB 13 EDTHELP.HLB 26 TECO.HLB 39 VMS$VOLATILE_PRIVATE_INTERFACES.OLB After Installing the OpenVMS Alpha Operating System 4-7 After Installing the OpenVMS Alpha Operating System 4.7 Decompressing the System Libraries A ALL libraries to be decompressed E EXIT this procedure * Enter letter or number(s) of libraries to be decompressed (Separate multiple entries with a comma): 2. Enter the appropriate letter or the numbers of the libraries you want to decompress. To decompress all libraries, the process takes approximately one-half hour. 4.7.4 Using LIBDECOMP.COM Interactively You can execute LIBDECOMP.COM interactively to decompress up to eight libraries at a time by listing the names of the libraries you want to decompress as parameters on the command line. Be sure to separate the library names with commas and do not include the file extensions. For example, to decompress VAXCRTL.OLB, DISKQUOTA.HLB, and LIB.MLB interactively, enter the following command: $ @SYS$UPDATE:LIBDECOMP VAXCRTL, DISKQUOTA, LIB 4.7.5 Using LIBDECOMP.COM in Batch You can also execute LIBDECOMP.COM in batch mode to decompress up to eight libraries at a time by listing the names of the libraries you want to decompress as parameters on a command line that includes the SUBMIT command. Be sure to separate the library names with commas and do not include the file extensions. For example, to decompress VAXCRTL.OLB, DISKQUOTA.HLB, and LIB.MLB as a batch job, enter the following command: $ SUBMIT/NOTIFY/PARAMETERS=(VAXCRTL, DISKQUOTA, LIB)- _$ SYS$UPDATE:LIBDECOMP ________________________ Note ________________________ When you enter the command for a batch job, be sure you enclose the list of library names within parentheses. ______________________________________________________ 4-8 After Installing the OpenVMS Alpha Operating System After Installing the OpenVMS Alpha Operating System 4.8 Adding and Removing Operating System Files 4.8 Adding and Removing Operating System Files If you decide after the installation to change which OpenVMS Alpha operating system files you want installed on your system, you can use the menu system contained on the OpenVMS Alpha operating system CD-ROM to add or remove files. ________________________ Note ________________________ You can obtain information about individual system files by entering HELP SYSTEM_FILES at the dollar sign prompt ($). ______________________________________________________ To add or remove operating system files: 1. Mount and boot the OpenVMS Alpha operating system CD- ROM. 2. Choose option 1 from the menu. 3. Choose the PRESERVE option. 4. Enter the name of the device that contains the system disk and answer the questions. 5. After you answer the question "Do you want detailed descriptions?," information regarding reconfiguring or reinstalling is displayed. Read the instructions, then choose the desired entry from the menu of options. The following is a sample display: Please choose one of the following: 1) Install or upgrade OpenVMS Alpha Version V7.2 2) Display products and patches that this procedure can install 3) Install or upgrade layered products and patches 4) Show installed products 5) Reconfigure installed products 6) Remove installed products 7) Execute DCL commands and procedures 8) Shut down this system Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?) 1 *********************************************************** After Installing the OpenVMS Alpha Operating System 4-9 After Installing the OpenVMS Alpha Operating System 4.8 Adding and Removing Operating System Files . . . Do you want to INITIALIZE or to PRESERVE? [PRESERVE] . . . Version V7.2 of the OpenVMS operating system is already installed on the target disk. You may choose one of the following actions: o Reconfigure the OpenVMS platform. This action will allow you to change your selections of which of the windowing and network products you included with your OpenVMS operating system installation. o Reconfigure the OpenVMS operating system. This action will allow you to change your choices about which options you included for the OpenVMS operating system. o Reinstall the OpenVMS operating system. This action will cause ALL operating system files to be replaced. You can also change your choices about which options you included for the OpenVMS operating system. Reinstall will take longer than Reconfigure. Reinstall may be appropriate if you suspect that files in the operating system, or in the windowing and network products have become corrupted. If you want to reinstall any of the windowing and network products, choose "Install or upgrade layered products and patches" (option 3) from the main menu. If you want to change your choices about which options you included for any of the windowing and network products, choose "Reconfigure installed products" (option 5) from the main menu. Please choose one of the following: 1) Reconfigure the OpenVMS platform. 2) Reconfigure the OpenVMS operating system. 3) Reinstall the OpenVMS operating system. 4) Return to the Main Menu (abort the upgrade/installation). 4-10 After Installing the OpenVMS Alpha Operating System After Installing the OpenVMS Alpha Operating System 4.8 Adding and Removing Operating System Files Enter choice or ? for help: (1/2/3/4/?) 2 The following product has been selected: DEC AXPVMS VMS V7.2 Operating System Configuration phase starting ... You will be asked to choose options, if any, for each selected product and for any products that may be installed to satisfy software dependency requirements. DEC AXPVMS VMS V7.2: OpenVMS Operating System COPYRIGHT (c) 12-SEP-1998 -- All rights reserved Compaq Computer Corporation Do you want the defaults for all options? [YES] Answer No to this question, and select the options you want as described in Section 3.5.2. A list of components is provided in Section 3.5.3. After you respond to the prompts, the display continues and the installation procedure completes as described in Section 3.5.4. The following is a continuation of the sample display: Do you want to review the options? [NO] Execution phase starting ... The following product will be reconfigured: DEC AXPVMS VMS V7.2 Portion done: 0%...10%...20%...30%...40%...50%...60%...80%... 90%...100% The following product has been reconfigured: DEC AXPVMS VMS V7.2 . . . For detailed instructions on how to remove the OpenVMS Alpha operating system from your disk, see Appendix E. 4.9 Preparing to Use OpenVMS Management Station If you installed the OpenVMS Management Station software on your system (either by accepting all default values or by selecting the component manually during the installation 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: After Installing the OpenVMS Alpha Operating System 4-11 After Installing the OpenVMS Alpha Operating System 4.9 Preparing to Use OpenVMS Management Station o Editing system files o Starting OpenVMS Management Station on other nodes o Verifying that you have the proper memory, disk space, media, and the required software to install and run OpenVMS Management Station on your PC o Installing the client software on your PC o Defining DECnet nodes For complete information about preparing your OpenVMS system and your PC to run the OpenVMS Management Station server and client software, see Appendix D. ________________________ Note ________________________ After you complete the tasks described in Appendix D, you can then remove those files from your system to save disk space. Do not use the DELETE command to remove the files. Instead, reconfigure the OpenVMS Alpha operating system as described in Section 4.8. ______________________________________________________ 4.10 Installing Layered Products 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 you did not install those layered products previously during the installation procedure, you can do so using the following procedure. To install layered products that require VMSINSTAL, see Section 4.10.1. ________________________ 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 layered products on a target system that has a different version of the operating system, use the alternate procedure described in the next section. ______________________________________________________ 1. Shut down the system (described in Appendix A). 4-12 After Installing the OpenVMS Alpha Operating System After Installing the OpenVMS Alpha Operating System 4.10 Installing Layered Products 2. Boot the operating system CD-ROM (locally or from the InfoServer). 3. Choose option 2 from the menu to view which layered products can be installed using the POLYCENTER Software Installation utility. 4. Choose option 3 from the menu to install the layered products. 5. Shut down the system by selecting option 8 from the menu. 6. Boot from the system disk. If the layered product that you want to install is not listed in the display, see the documentation you received with that layered product for installation information. For additional information about installing layered products, see the OpenVMS System Manager's Manual. Be sure you back up the system disk after you install all your layered products. 4.10.1 Alternate Procedure Following is another method for installing layered products from the OpenVMS Alpha operating system CD-ROM: 1. From your running OpenVMS system (the target system disk), mount the OpenVMS Alpha operating system CD-ROM. 2. Locate the directories and files containing the available layered products by entering the following command (where, in the example, DKA400: is the device name of the CD-ROM): $ DIRECTORY /NOHEAD/NOTRAIL DKA400:[*.KIT] You can use the PRODUCT FIND command to locate kits that are installed using the POLYCENTER Software Installation utility. For example: $ PRODUCT FIND * /SOURCE=DKA400:[*.KIT] 3. To install layered products that require VMSINSTAL (indicated in the directories by save-set file names with file types of .A, .B, and so on), enter the @SYS$UPDATE:VMSINSTAL command and then specify the CD-ROM device and directory. For example: After Installing the OpenVMS Alpha Operating System 4-13 After Installing the OpenVMS Alpha Operating System 4.10 Installing Layered Products $ @SYS$UPDATE:VMSINSTAL * Where will the distribution volumes be mounted: DKB400:[UCX032.KIT] 4. To install layered products that require the POLYCENTER Software Installation utility (indicated in the directories by file names with file types of .PCSI or .PCSI$DESCRIPTION), use the PRODUCT INSTALL command to specify the CD-ROM device name and directory. Following is an example of the PRODUCT INSTALL command: $ PRODUCT INSTALL POSIX /SOURCE=DKB400:[POSIX020.KIT] 4.10.2 DECevent When you install OpenVMS Alpha Version 7.2, the DIAGNOSE command is disabled. To enable the DIAGNOSE command, you must install the DECevent kit provided on the OpenVMS Alpha Version 7.2 CD-ROM following the installation of OpenVMS Alpha Version 7.2. The DECevent kit is located in the directory [DECEVENT_0252.KIT] on the CD-ROM. If the DECevent kit provided on the OpenVMS Alpha CD-ROM is not installed after the operating system, users attempting to use the DIAGNOSE command will receive the following system message: $ DIAGNOSE [params] %DIA-E-NOINSTAL, DIAGNOSE has not been installed on this system 4.10.3 Monitoring Performance History The OpenVMS Alpha Version 7.2 operating system CD-ROM also includes a Monitoring Performance History (MPH) kit located in the [MPH] directory. See the OpenVMS Version 7.2 Release Notes for more information about installing and using this optional software. 4.11 Installing DIGITAL OpenVMS Debugger Clients on a PC The DIGITAL OpenVMS Debugger Version 7.2 includes a client/server interface. The debug server runs on the OpenVMS operating system; there are debug clients that run on OpenVMS, Microsoft Windows 95, and Microsoft Windows NT. There is no separate installation procedure for the components that run on the OpenVMS operating system. They are installed when you install the operating system. 4-14 After Installing the OpenVMS Alpha Operating System After Installing the OpenVMS Alpha Operating System 4.11 Installing DIGITAL OpenVMS Debugger Clients on a PC This section describes the procedure for installing debug clients on a PC. The following table shows which client kit to use for each PC configuration: ___________________________________________________________ Operating CPU__System__________Client_Kit____________________________ IntelMicrosoft [DEBUG_CLIENTS010.KIT]DEBUGX86010.EXE Windows 95 IntelMicrosoft [DEBUG_CLIENTS010.KIT]DEBUGX86010.EXE Windows NT AlphaMicrosoft [DEBUG_ _____Windows_NT______CLIENTS010.KIT]DEBUGALPHA010.EXE______ The client kits are self-extracting .EXE files. To make these clients available to PC users, copy these files from the distribution media to a suitable PATHWORKS share, FTP server, or other device available to the PC. Once the appropriate executable file has been transferred to the PC, you can run the file to install the debug client on the PC. The InstallShield installation procedure guides you through the installation. By default, the debug client is installed in the \Programs\OpenVMS Debugger directory. You can also click on the Browse button to select an alternate directory. You can choose one of the following installation options: ___________________________________________________________ Install Option______Details________________________________________ Typical Debug Client and the OpenVMS Debugger Manual in HTML format Compact Debug Client only Custom Choice of Debug Client and/or the OpenVMS ____________Debugger_Manual_in_HTML_format_________________ The Typical installation option creates an OpenVMS Debugger program folder that contains shortcuts to the following items: After Installing the OpenVMS Alpha Operating System 4-15 After Installing the OpenVMS Alpha Operating System 4.11 Installing DIGITAL OpenVMS Debugger Clients on a PC o Debug client o Debug client Help file o The OpenVMS Debugger Manual in HTML format o A Readme file o An Uninstall procedure For information about using the OpenVMS Debugger, see the OpenVMS Debugger Manual. 4.12 Backing Up the Customized System Disk After you have customized the OpenVMS Alpha operating system to your satisfaction and installed your layered products, protect your work by making a standalone backup copy of the system disk. For complete information about backup operations, including a description of an alternate method that does not require booting from the operating system CD-ROM, see Appendix B. To back up the system disk: 1. Shut down the system (described in Appendix A). 2. Boot the operating system CD-ROM (locally or from the InfoServer). 3. Use the menu system to enter the DCL environment (option 7). 4. Mount the system disk and the target device on which you will make the backup copy. 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 8 from the menu. 8. Boot from the system disk. 4-16 After Installing the OpenVMS Alpha Operating System After Installing the OpenVMS Alpha Operating System 4.13 Configuring a Multihead System 4.13 Configuring a Multihead System A multihead configuration consists of a single workstation (such as a DEC 3000 Alpha Model 500 system) that supports multiple graphics options. A graphics option consists of a graphics controller and a graphics display interface (monitor). Your system can be automatically configured for multihead use if you rename the private server setup file from a template file type to a command procedure file type. The DECwindows Motif for OpenVMS Alpha server loads this command procedure on startup or restart. This file always configures the console as the primary head, or screen 0. The firmware always selects the lowest device found in the system (that is, the device with the lowest TURBOchannel slot address) as the console device. To set up your system for multihead support: 1. After installing the DECwindows Motif for OpenVMS Alpha software on your system, log in to your system. 2. Rename the private server setup file by entering the following command: $ RENAME SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE _To: SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM 3. Restart the DECwindows server by entering the following command: $ @SYS$STARTUP:DECW$STARTUP RESTART See the most recent version of the DECwindows Motif for OpenVMS Installation Guide and Managing DECwindows Motif for OpenVMS Systems for more information about customizing your DECwindows environment using the SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM file. 4.14 Running AUTOGEN When you installed the OpenVMS Alpha operating system, the system executed the AUTOGEN.COM procedure to set the values of system parameters and the sizes of the page, swap, and dump files according to the system configuration. As a postinstallation procedure, you should run the AUTOGEN.COM procedure again to properly tune the system. After Installing the OpenVMS Alpha Operating System 4-17 After Installing the OpenVMS Alpha Operating System 4.14 Running AUTOGEN Run AUTOGEN as follows: 1. After 24 hours of operation, run AUTOGEN in feedback mode and reboot the system. 2. Run AUTOGEN again in feedback mode two workdays later, and then reboot the system. 3. Compaq recommends that you run AUTOGEN from SAVPARAMS through TESTFILES on a weekly basis thereafter, and examine AGEN$PARAMS.REPORT to determine the need for additional changes. 4.14.1 Modifying Parameters Based on your examination of AGEN$PARAMS.REPORT, you might need to modify parameter values in MODPARAMS.DAT. If so, note the following: o Hardcoded values in MODPARAMS.DAT should not hinder AUTOGEN's ability to calculate feedback parameters. AUTOGEN generally does not reduce the value of parameters that allocate resources; it considers current parameter values to be minimum values, which means that you do not have to add MIN_* symbols to MODPARAMS.DAT. o AUTOGEN does increase parameter values according to its calculations unless you have specified explicit or maximum values (by adding MAX_* symbols) in MODPARAMS.DAT. For more information about the MODPARAMS.DAT file and about using AUTOGEN in general, see the OpenVMS System Manager's Manual. 4-18 After Installing the OpenVMS Alpha Operating System After Installing the OpenVMS Alpha Operating System 4.15 Postinstallation Checklist 4.15 Postinstallation Checklist Use the following checklist to make sure you perform all the necessary postinstallation tasks: < Register your licenses if you did not do so during the installation procedure. < Create accounts. < Back up the system disk as a safeguard before customizing the system. < Customize the system. < Configure and start the DECnet for OpenVMS Alpha software. < Run the User Environment Test Package (UETP) to test the system. < Decompress the system libraries using LIBDECOMP.COM. < Add and remove files. < Prepare your OpenVMS Alpha system and your PC to run OpenVMS Management Station by following the procedures described in Appendix D. < Install layered products. < Back up the system disk after you have customized it and installed layered products. < Configure your multihead system (if applicable). < After the system has been running for at least 24 hours, run AUTOGEN to collect feedback information and modify the MODPARAMS.DAT file (if necessary). After Installing the OpenVMS Alpha Operating System 4-19 5 _________________________________________________________________ Before Upgrading the OpenVMS Alpha Operating System This chapter describes which tasks you should perform prior to beginning an upgrade. Tasks described in this chapter include: o Reviewing notes, cautions, and restrictions o Preparing to upgrade in a volume shadowing environment o Backing up the current system disk o Preparing the system disk for the upgrade o Shutting down the system o Using the preupgrade checklist In addition to reviewing the information in this chapter, you might need to refer to the following sources of information as well: o OpenVMS Version 7.2 Release Notes o OpenVMS System Manager's Manual, for information about using AUTOGEN, modifying the system parameters file (MODPARAMS.DAT), and related operations o OpenVMS System Management Utilities Reference Manual, for information about using system management utilities such as SYSMAN and ANALYZE/DISK_STRUCTURE o OpenVMS Guide to System Security, for information about reestablishing your security environment after the upgrade Before Upgrading the OpenVMS Alpha Operating System 5-1 Before Upgrading the OpenVMS Alpha Operating System 5.1 Notes, Cautions, and Restrictions 5.1 Notes, Cautions, and Restrictions This section provides important information that can affect the success of your upgrade. Review the cautions, restrictions, and notes carefully before you begin the upgrade. 5.1.1 Spiralog File System Not Supported The Spiralog file system will not work with OpenVMS Alpha Version 7.2. If Spiralog is installed on your system, you must uninstall it before upgrading to OpenVMS Alpha Version 7.2. 5.1.2 Required Operating System Version To upgrade to Version 7.2 of the OpenVMS Alpha operating system, you must be running at least Version 6.1, 6.2-xxx, 7.0, or 7.1-xxx. If you are upgrading in a cluster environment, also see Chapter 6 for information about the required version of the OpenVMS Alpha operating system. 5.1.3 Upgrade Paths Upgrades are supported from Version 6.1, 6.2-xxx, 7.0, and 7.1-xxx of the OpenVMS Alpha operating system. Rolling upgrades are supported from Version 6.2-xxx and 7.1-xxx of the OpenVMS Alpha operating system (see Chapter 6 for more information). 5.1.4 Update License To upgrade to OpenVMS Alpha Version 7.2, you must have an appropriate license. Compaq's software licenses grant the right to use the current version of a product or any previous version of the product at the time of purchase. If you have an OpenVMS Alpha license prior to Version 7.2 and are not covered by a Software Product Services agreement, which includes the right to use new versions (RTNV), you must purchase an Update License before upgrading to OpenVMS Alpha Version 7.2. If you do not have an Update License, please contact your Compaq support representative who will assist you in obtaining the correct Product Authorization Key (PAK) needed to access the OpenVMS operating system. 5-2 Before Upgrading the OpenVMS Alpha Operating System Before Upgrading the OpenVMS Alpha Operating System 5.1 Notes, Cautions, and Restrictions 5.1.5 Files and Directories If you choose not to install optional OpenVMS Alpha software during the upgrade, the upgrade procedure removes existing files for those components from the system disk. If you have changed directory structure on your system disk, the upgrade procedure will not work correctly. Restore your system disk to a standard directory structure before you attempt an upgrade. The OpenVMS Alpha Version 7.2 upgrade procedure provides new files and directories in the directory [VMS$COMMON...]. If you had any special protections and access control lists (ACLs) before the upgrade, you need to reapply them to reestablish the security environment you had previously set up. For more information about creating and maintaining a secure environment, see the OpenVMS Guide to System Security. 5.1.6 Licenses and Layered Products The upgrade procedure is designed so that you should not have to reinstall most layered products after the upgrade. However, you might need to reinstall certain layered products because of product-specific installation procedures. The upgrade procedure leaves your OpenVMS Alpha license and layered product licenses intact. You do not need to reinstall these licenses after you upgrade. 5.2 Preparing to Upgrade in a Volume Shadowing Environment Because you cannot upgrade the operating system on a shadowed system disk (the upgrade will fail), you need to disable shadowing on that disk and perform other operations before you can upgrade the operating system. There are several methods for creating a nonshadowed target disk. This chapter describes how to change one of your existing shadowed system disks in a multimember shadow set to a nonshadowed disk that you can use as your target disk for the upgrade. Before Upgrading the OpenVMS Alpha Operating System 5-3 Before Upgrading the OpenVMS Alpha Operating System 5.2 Preparing to Upgrade in a Volume Shadowing Environment If you have a larger configuration with disks that you can physically access, you may want to use a copy of the system disk as your target disk. Volume Shadowing for OpenVMS describes two methods you can use to create this copy (using volume shadowing commands or BACKUP commands) and how to disable volume shadowing. 5.2.1 Creating a Nonshadowed Target Disk Change one of your existing shadowed system disks to a nonshadowed disk as follows: 1. Shut down all systems booted from the shadowed system disk. 2. Perform a conversational boot (see Appendix A if necessary) on the system disk you have chosen for your target disk. For example: >>> BOOT -FLAGS 0,1 DKA100 3. At the SYSBOOT> prompt, enter the following command to disable volume shadowing on the disk: SYSBOOT> SET SHADOW_SYS_DISK 0 4. Enter the CONTINUE command to resume the boot procedure. For example: SYSBOOT> CONTINUE 5. After the boot completes, log in to the system. After you have created a nonshadowed system disk that you can use for the upgrade, perform the additional preupgrade procedures described in the balance of this chapter. 5.2.2 Changing the Label If you want to change the label on the upgrade disk, use the DCL command SET VOLUME/LABEL=volume-label device- spec[:] to perform this optional task. (The SET VOLUME /LABEL command requires write access [W] to the index file on the volume. If you are not the volume owner, you must have either a system UIC or the SYSPRV privilege.) For OpenVMS Cluster systems, be sure that the volume label is a unique name across the cluster. 5-4 Before Upgrading the OpenVMS Alpha Operating System Before Upgrading the OpenVMS Alpha Operating System 5.2 Preparing to Upgrade in a Volume Shadowing Environment If you change the volume label, you must also register that change in the POLYCENTER Software Installation utility database. To do this, use the following command: $ PRODUCT REGISTER VOLUME old-volume-label device-name Note that you must supply the old volume label. The new volume label is found by using the device name. ________________________ Note ________________________ If you need to change the volume label of a disk that is mounted across the cluster, be sure you change the label on all nodes in the OpenVMS Cluster system. The following example shows how you can use the SYSMAN utility to define the environment as a cluster and propagate the volume label change to all nodes in that cluster: SYSMAN> SET ENVIRONMENT/CLUSTER SYSMAN> DO SET VOLUME/LABEL=new-label disk-device-name: ______________________________________________________ 5.2.3 Setting the Boot Device Be sure your system is set to boot from the upgrade disk by default. Use the SHOW BOOTDEF_DEV and SET BOOTDEF_DEV console commands to accomplish this task. (See Appendix A for more information.) 5.3 Backing Up the System Disk Compaq strongly recommends that you make a backup copy of the system disk and, if your configuration allows it, upgrade the backup copy. (If there are problems, you will still have a working system disk.) To back up the system disk: 1. Shut down the system (described in Appendix A). 2. Boot the operating system CD-ROM (locally or from the InfoServer). 3. Use the menu system to enter the DCL environment (option 7). Before Upgrading the OpenVMS Alpha Operating System 5-5 Before Upgrading the OpenVMS Alpha Operating System 5.3 Backing Up the System Disk 4. Mount the system disk and the target device on which you will make the backup copy. 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 8 from the menu. 8. Boot from the system disk. For complete information about backup operations, including a description of an alternate method that does not require booting from the operating system CD-ROM, see Appendix B. 5.4 Preparing the System Disk The following sections describe how to prepare the system disk for the upgrade. The operations include the following: o Examining the system disk o Checking the size of the system disk o Verifying system parameters 5.4.1 Examining the System Disk Examine and repair (if necessary) the system disk using the ANALYZE/DISK_STRUCTURE command. (See the OpenVMS System Management Utilities Reference Manual for more information about this command.) Use the following procedure: 1. Analyze the system disk for inconsistencies and errors in the file structure by entering the following command: $ ANALYZE/DISK_STRUCTURE SYS$SYSDEVICE Ignore the following message: %ANALDISK-I-OPENQUOTA, error opening QUOTA.SYS 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 5-6 Before Upgrading the OpenVMS Alpha Operating System Before Upgrading the OpenVMS Alpha Operating System 5.4 Preparing the System Disk 5.4.2 Checking the Size of the System Disk It is difficult to determine in advance how many blocks of disk space you will need for the upgrade. It depends on how many files you have on the target disk already and on how many components you select during the 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. o After you select the components you want installed on the system for the upgrade, the upgrade procedure calculates whether you have enough disk space, displaying the number of available blocks and the number required for the upgrade. If the procedure determines that your disk does not have enough space to perform the upgrade, it displays a message to alert you and allows you to terminate the upgrade so you can create more disk space and try the upgrade again. To see how much space you have on the system disk, enter the following command: $ SHOW DEVICE SYS$SYSDEVICE 5.4.3 Verifying System Parameters Verify (and modify if necessary) system parameters, described as follows. (If necessary, see the OpenVMS System Manager's Manual for more information about modifying system parameters.) Any system parameters that you modified and did not enter in SYS$SYSTEM:MODPARAMS.DAT are lost during the upgrade. To retain these parameters, enter their names in SYS$SYSTEM:MODPARAMS.DAT and the value that AUTOGEN needs to add to the default minimum value. (When AUTOGEN runs after the upgrade, it uses the values in 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 Before Upgrading the OpenVMS Alpha Operating System 5-7 Before Upgrading the OpenVMS Alpha Operating System 5.5 What to Do Next 5.5 What to Do Next Continue the preupgrade tasks as follows, depending on whether you are upgrading in a standalone or OpenVMS Cluster environment: ___________________________________________________________ IF_...________________THEN_..._____________________________ you are upgrading a do the following: standalone system, 1. Log in to the SYSTEM account. 2. Enter the following command and then press the Return key: $ @SYS$SYSTEM:SHUTDOWN 3. When the procedure asks if an automatic system reboot should be performed, enter N (No) and press the Return key. 4. Go to the checklist at the end of this chapter to verify that you have performed the necessary tasks; then go to Chapter 7 to begin the upgrade procedure. you are upgrading do the following: an OpenVMS Cluster 1. Review the checklist at the end of system, this chapter. 2. Go to Chapter 6. ___________________________________________________________ 5.6 Preupgrade Checklist Use the following checklist to make sure you have performed all the tasks before beginning the upgrade: < Review all cover letters and the release notes. < Review all cautions and notes. < If your system disk is part of a shadow set, create a nonshadowed system disk to upgrade. 5-8 Before Upgrading the OpenVMS Alpha Operating System Before Upgrading the OpenVMS Alpha Operating System 5.6 Preupgrade Checklist < Set up your system to record the upgrade procedure on either a hardcopy terminal or a printer attached to the console terminal. If you do not do this, the screen messages will be lost. You will need a transcript in case there is a problem during the upgrade. For information on how to record the procedure, see the hardware manuals that came with your Alpha computer. < Make a backup copy of the system disk. < Examine and repair (if necessary) the system disk using the ANALYZE/DISK_STRUCTURE command. < Check the size of the system disk. < Verify system parameters. < Shut down the system (if you are upgrading in a standalone environment). < If you are upgrading an OpenVMS Cluster system, go to Chapter 6. If you are not upgrading an OpenVMS Cluster system, go to Chapter 7 to begin the upgrade procedure. Before Upgrading the OpenVMS Alpha Operating System 5-9 6 _________________________________________________________________ Preparing to Upgrade in an OpenVMS Cluster Environment This chapter describes how to prepare to upgrade in an OpenVMS Cluster environment, depending on the type of upgrade you perform and whether you need to add any new computers to the cluster. ________________________ Note ________________________ Be sure you have performed the preupgrade tasks described in Chapter 5 before you upgrade your OpenVMS Cluster system. ______________________________________________________ When you upgrade the operating system in an OpenVMS Cluster environment, be sure the following information is available to review: o The cover letters and the software product descriptions included with your distribution kit o OpenVMS Version 7.2 Release Notes o OpenVMS Cluster Systems o Guidelines for OpenVMS Cluster Configurations o OpenVMS Version 7.2 New Features Manual 6.1 Mixed-Version Support OpenVMS Alpha Version 7.2 and OpenVMS VAX Version 7.2 provide two levels of support for mixed-version and mixed- architecture OpenVMS Cluster systems. These two support types are warranted and migration. Preparing to Upgrade in an OpenVMS Cluster Environment 6-1 Preparing to Upgrade in an OpenVMS Cluster Environment 6.1 Mixed-Version Support Warranted support means that Compaq has fully qualified the two versions coexisting in an OpenVMS Cluster and will answer all problems identified by customers using these configurations. Migration support is a superset of the Rolling Upgrade support provided in earlier releases of OpenVMS and is available for mixes that are not warranted. Migration support means that Compaq has qualified the versions for use together in configurations that are migrating in a staged fashion to a newer version of OpenVMS VAX or to OpenVMS Alpha. Problem reports submitted against these configurations will be answered by Compaq. However, in exceptional cases Compaq may request that you move to a warranted configuration as part of answering the problem. Migration support will help you move to warranted OpenVMS Cluster version mixes with minimal impact on your cluster environment. Table 6-1 shows the level of support provided for all possible version pairings. Table 6-1 OpenVMS Cluster Warranted and Migration Support __________for_VAX_and_Alpha________________________________ ____________V6.2-xxx____V7.1-xxx____V7.2___________________ V6.2 WARRANTED Migration Migration V7.1 Migration WARRANTED Migration V7.2________Migration___Migration___WARRANTED______________ ________________________ Note ________________________ Compaq does not support the use of Version 7.1 or higher with Version 6.1 (or earlier versions) in an OpenVMS Cluster environment. ______________________________________________________ 6-2 Preparing to Upgrade in an OpenVMS Cluster Environment Preparing to Upgrade in an OpenVMS Cluster Environment 6.2 Adding a New System to the Cluster 6.2 Adding a New System to the Cluster If you need to add a new computer supported by OpenVMS Alpha Version 7.2 to an existing OpenVMS Cluster configuration, Compaq supports two options, listed in the following preferred order: 1. Upgrade the entire cluster to Version 7.2 of the OpenVMS Alpha operating system and add the new computer as a member. 2. If you need to keep some systems in the cluster running the current version of OpenVMS Alpha, you must upgrade a system disk in the cluster to OpenVMS Alpha Version 7.2 using the rolling upgrade procedure. Then boot the new computer into the cluster using that upgraded system disk. 6.3 Types of Upgrades There are two types of cluster upgrades: concurrent and rolling. The type of upgrade you use depends on whether you want to maintain the availability of the cluster during the upgrade and whether you have more than one system disk. Review this chapter and then perform the preliminary tasks for the upgrade procedure (concurrent or rolling) that best suits your configuration. 6.4 Concurrent Upgrade This section describes the following: o How a concurrent upgrade works o Preparing your system for a concurrent upgrade 6.4.1 How a Concurrent Upgrade Works During a concurrent upgrade, you must shut down the entire cluster and upgrade each system disk. No one can use the cluster until you upgrade each system disk and reboot each Alpha computer. When the cluster reboots, each Alpha computer will be running the upgraded version of the OpenVMS Alpha operating system. If all Alpha systems in the OpenVMS Cluster environment are booted from one system disk, you must perform a concurrent upgrade. Preparing to Upgrade in an OpenVMS Cluster Environment 6-3 Preparing to Upgrade in an OpenVMS Cluster Environment 6.4 Concurrent Upgrade 6.4.2 Preparing Your System for a Concurrent Upgrade To prepare for a concurrent upgrade: 1. Log in locally to the SYSTEM account. 2. Shut down all systems by entering the following command on each system (satellites first, then the boot nodes): $ @SYS$SYSTEM:SHUTDOWN 3. When the procedure asks if an automatic system reboot should be performed, enter N (No) and press the Return key. 4. Choose the CLUSTER_SHUTDOWN option. 5. When the shutdown procedure is finished on all nodes, halt each system by entering Ctrl/P or by pressing the Halt button.[1] 6. If you have only one system disk for your cluster, go to Chapter 7 to begin the upgrade procedure. If you have more than one system disk, make sure that you have performed the preupgrade tasks on each system disk that you will be upgrading. Then go to Chapter 7 and perform an upgrade on each system disk. You do not have to reboot the operating system CD-ROM for each upgrade. You only need to choose option 1 from the menu for each upgrade. After the upgrade is complete, you will be instructed to reboot each computer in the OpenVMS Cluster environment before beginning other postupgrade procedures. 6.5 Rolling Upgrade This section describes the following: o How a rolling upgrade works o Notes and restrictions o Preparing your system for a rolling upgrade ____________________ [1] For more information about halting your Alpha computer, see Appendix A. 6-4 Preparing to Upgrade in an OpenVMS Cluster Environment Preparing to Upgrade in an OpenVMS Cluster Environment 6.5 Rolling Upgrade 6.5.1 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, creating a mixed-version cluster. Because rolling upgrades allow mixed-version clusters, the systems that you are not upgrading remain available. During a rolling upgrade, you keep some of the computers in the cluster running while you upgrade others (you must have more than one system disk). 6.5.2 Notes and Restrictions The following restrictions apply to rolling upgrades. See the OpenVMS Version 7.2 Release Notes for additional compatibility issues and restrictions. o Rolling upgrades are supported from Version 6.2-xxx and 7.1-xxx of the OpenVMS Alpha operating system. Rolling upgrades in mixed-architecture OpenVMS Cluster environments are supported with VAX computers running Versions 7.1 or 6.2 of the OpenVMS VAX operating system (see Table 6-1). o The upgraded system does not attempt to access any disk that is being accessed by one or more of the remaining OpenVMS Cluster systems. o The remaining OpenVMS Cluster systems do not attempt to access the target disk of the system being upgraded. If the target disk being upgraded is locally attached to the system performing the upgrade, then it is not accessible to the remaining OpenVMS Cluster systems. (The OpenVMS system booted from the operating system CD- ROM does not MSCP serve local disks.) Whenever possible, Compaq recommends that you perform the upgrade on a local disk or that you perform a concurrent upgrade. During the upgrade, be sure that the target disk you select, as well as any disk you access from the DCL menu option, is either a local disk or one that is not being accessed by any of the remaining OpenVMS Cluster members. Preparing to Upgrade in an OpenVMS Cluster Environment 6-5 Preparing to Upgrade in an OpenVMS Cluster Environment 6.5 Rolling Upgrade ________________________ Note ________________________ Any attempt to access the target disk from the remaining OpenVMS Cluster members will corrupt the target disk in most cases. Even if the target disk is mounted only by a remaining cluster member, and no file access is done, the target disk will probably be corrupted. If a disk is corrupted in this way, the only supported recovery is to restore the backup copy of the corrupted disk. ______________________________________________________ o Compaq recommends that all Alpha computers in a cluster run the same (and preferably the latest) version of the OpenVMS Alpha operating system. o You cannot perform a rolling upgrade if all systems boot from a single system disk. Perform a concurrent upgrade instead. o The upgrade procedure affects the queuing system as follows: - The queuing system is not active on the system you are upgrading; do not attempt to execute a START /QUEUE/ MANAGER command. - You cannot create a queue database on the operating system CD-ROM (because it is not writable). - The queue manager process on other nodes in the cluster can continue to run during the upgrade if the queue database is not on the disk being upgraded. 6.5.3 Preparing Your System for a Rolling Upgrade To prepare for a rolling upgrade: 1. Log in to any node where the target disk is mounted as a data disk, rather than as the system disk. (That disk must be the one on which you already performed the preupgrade tasks described in Chapter 5.) 2. Check the votes and make adjustments to maintain the proper quorum so the cluster can continue to operate throughout the upgrade. (OpenVMS Cluster Systems describes this procedure in detail.) 6-6 Preparing to Upgrade in an OpenVMS Cluster Environment Preparing to Upgrade in an OpenVMS Cluster Environment 6.5 Rolling Upgrade 3. Use the DCL command DISMOUNT/CLUSTER to dismount the data disk. (You can also perform this operation using the SYSMAN utility.) Note that you can ignore messages from nodes where the 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: $ MCR SYSMAN SYSMAN> SET ENVIRONMENT/CLUSTER SYSMAN> DO SHOW DEVICE disk-name Examine the display to be sure the disk is not mounted on any nodes as a data disk. Noting the value listed in the Trans Count field can help you make that determination: A value of less than 50 indicates that the disk is mounted as a data disk rather than as the system disk; a much larger value (for example, 300) 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; otherwise, exit from the SYSMAN utility. 6. Shut down all nodes that boot from the system disk you are upgrading, including the node from which you will perform the upgrade. Enter the following command on each node: $ @SYS$SYSTEM:SHUTDOWN 7. When the procedure asks if an automatic system reboot should be performed, enter N (No) and press the Return key. 8. Choose the REMOVE_NODE option. 9. If proper quorum is not maintained at any time during the upgrade procedure, the shutdown procedure will hang the cluster. If the cluster hangs during a shutdown, enter the following commands on the system console of a system that is still a cluster member: Preparing to Upgrade in an OpenVMS Cluster Environment 6-7 Preparing to Upgrade in an OpenVMS Cluster Environment 6.5 Rolling Upgrade $ >>> D SIRR C >>> C IPC> Q IPC> 10.After the shutdown procedure is finished on all nodes, go to Chapter 7 to begin the upgrade procedure. 6-8 Preparing to Upgrade in an OpenVMS Cluster Environment 7 _________________________________________________________________ Upgrading the OpenVMS Alpha Operating System This chapter describes the following tasks: o Beginning the upgrade from the operating system CD-ROM o Specifying the target disk o Specifying the volume label o Updating time zone information o Choosing descriptive help text o Completing the upgrade o Performing postupgrade tasks (including booting the upgraded system) o Installing layered products 7.1 Booting the Operating System CD-ROM The OpenVMS Alpha Version 7.2 operating system includes procedures that allow you to easily upgrade the operating system using the POLYCENTER Software Installation utility. To get started, boot the OpenVMS Alpha operating system CD-ROM either from your local CD-ROM drive or from a CD- ROM drive connected to the InfoServer, as described in the following sections. 7.1.1 Booting from the Local Drive To boot the operating system CD-ROM from the local drive, follow these steps: 1. Insert the operating system CD-ROM into the local CD-ROM drive. 2. At the console prompt (>>>), enter the SHOW DEVICE command so you can identify the name of the CD-ROM drive (for example, DKA400:) Upgrading the OpenVMS Alpha Operating System 7-1 Upgrading the OpenVMS Alpha Operating System 7.1 Booting the Operating System CD-ROM 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 listed in the SHOW DEVICE display) for source-drive. For example, if the SHOW DEVICE display lists the device name of your CD-ROM drive as DKA400, enter the following command and press the Return key: >>> BOOT -FLAGS 0,0 DKA400 7.1.2 Booting from the InfoServer To boot the operating system CD-ROM using the InfoServer, follow these steps: 1. At the console prompt, enter the following command: >>> BOOT -FLAGS 0,0 -FILE APB_072 lan-device-name Note the following conventions: o APB_072 is the file name of the APB program used for the initial system load (ISL) boot program. o lan-device-name is the name of the local area network (LAN) device Ethernet identified with your computer. For information about the LAN devices your system supports, refer to the following table. For additional information, see the hardware manuals that you received with your Alpha computer and the OpenVMS Software Product Description. 7-2 Upgrading the OpenVMS Alpha Operating System Upgrading the OpenVMS Alpha Operating System 7.1 Booting the Operating System CD-ROM ________________________________________________________ Ethernet FDDI Alpha_Computer_____________Device________Device_________ ALPHAbook 1 EOA0 - AlphaServer 400 series EWA0 FWA0 AlphaServer 1000 series ERA0, EWA0 FRA0 AlphaServer 1000A series EWA0 FWA0 AlphaServer 1200 series EWA0 FWA0 AlphaServer 2000 series ERA0, EWA0 FRA0 AlphaServer 2100, 2100A ERA0, EWA0 FRA0 series AlphaServer 4100 series EWA0 FWA0 AlphaServer 8200 series EXA0, EWA0 FXA0 AlphaServer 8400 series EXA0, EWA0 FXA0 AlphaStation 200 series EWA0 FWA0 AlphaStation 400 series EWA0 FWA0 AlphaStation 500 series EWA0 FWA0 AlphaStation 600 series ERA0, EWA0 FWA0 DEC 2000 series ERA0 - DEC 3000 series ESA0 "n/ESA0" DEC 4000 series EZA0 - DEC 7000 series EXA0 FXA0 DEC 10000 series EXA0 FXA0 DIGITAL Personal EWA0 FWA0 Workstation (DPWS) series__________________________________________________ ________________________ Note ________________________ 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 with an Ethernet PMAD device or FDDI DEFTA device by specifying the device name as "n/ESA0". The value for n is the TURBOchannel slot number, which you can obtain by entering the SHOW CONFIGURATION command at the console prompt (>>>) and examining the display. For more information, see Section A.1.8. Upgrading the OpenVMS Alpha Operating System 7-3 Upgrading the OpenVMS Alpha Operating System 7.1 Booting the Operating System CD-ROM o On DEC 4000 series, you must specify the ISL file name in uppercase (APB_072). ______________________________________________________ 2. The InfoServer ISL program then displays the following menu: Network Initial System Load Function Version 1.2 FUNCTION FUNCTION ID 1 - Display Menu 2 - Help 3 - Choose Service 4 - Select Options 5 - Stop Enter a function ID value: 3. Respond to the prompts as follows, pressing the Return key after each entry: a. Enter 3 for the function ID. b. Enter 2 for the option ID. c. Enter the service name (ALPHA072). A sample display follows: Enter a function ID value: 3 OPTION OPTION ID 1 - Find Services 2 - Enter known Service Name Enter an Option ID value: 2 Enter a Known Service Name: ALPHA072 ________________________ Note ________________________ If you boot the OpenVMS Alpha operating system CD-ROM from an InfoServer system but lose your connection during the upgrade procedure (the system is unresponsive and pressing Ctrl/Y does not return you to the menu), do the following: 7-4 Upgrading the OpenVMS Alpha Operating System Upgrading the OpenVMS Alpha Operating System 7.1 Booting the Operating System CD-ROM 1. Reboot the OpenVMS Alpha operating system CD-ROM. 2. Enter the DCL environment by choosing option 7 from the menu. 3. Mount the device containing your backup copy of the target disk and the device that is your target disk. 4. Restore the backup copy of your target disk by entering the appropriate BACKUP commands. (See Appendix B for complete information about using MOUNT and BACKUP commands to restore a system disk.) 5. Log out from the DCL environment. 6. Perform the upgrade again by choosing the upgrade option (1) from the menu and following the procedures described in this chapter. ______________________________________________________ 7.2 Performing the Upgrade The following sections describe how to upgrade from the operating system CD-ROM. 7.2.1 Upgrading from the CD-ROM After you boot the operating system CD-ROM, choose the upgrade option (1) from the menu displayed on the screen. The display is similar to the following: OpenVMS (TM) Alpha Operating System, Version V7.2 Copyright (c) 1998 Compaq Computer Corporation. All rights reserved. Installing required known files... Configuring devices... **************************************************************** You can install or upgrade the OpenVMS Alpha operating system or you can install or upgrade layered products that are included on the OpenVMS Alpha operating system CD-ROM. Upgrading the OpenVMS Alpha Operating System 7-5 Upgrading the OpenVMS Alpha Operating System 7.2 Performing the Upgrade You can also execute DCL commands and procedures to perform "standalone" tasks, such as backing up the system disk. Please choose one of the following: 1) Upgrade, install or reconfigure OpenVMS Alpha Version V7.2 2) Display products and patches that this procedure can install 3) Install or upgrade layered products and patches 4) Show installed products 5) Reconfigure installed products 6) Remove installed products 7) Execute DCL commands and procedures 8) Shut down this system Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?) 1 The OpenVMS Alpha operating system CD-ROM may contain patch kits. If it does, information similar to the following will be displayed: The following PATCH kits are present on the OpenVMS Alpha distribution media. ----------------------------------- ----------- ---------- PRODUCT KIT TYPE KIT FORMAT ----------------------------------- ----------- ---------- DEC AXPVMS UCXECO_42_1 V1.0 Patch Sequential ----------------------------------- ----------- ---------- 1 item found Please consult the OpenVMS Alpha Upgrade and Installation Manual, the Release Notes, and the Cover Letter to determine if any or all of these patches may be required for your system. 7.2.2 Choosing INITIALIZE or PRESERVE After you choose the upgrade option (if you are upgrading from the operating system CD-ROM) or start the AXPVMS$PCSI_ INSTALL command procedure (if you are upgrading from a running OpenVMS Alpha Version 7.2 system), the system displays the following information and prompts: 7-6 Upgrading the OpenVMS Alpha Operating System Upgrading the OpenVMS Alpha Operating System 7.2 Performing the Upgrade *********************************************************** The installation procedure will ask a series of questions. () - encloses acceptable answers [] - encloses default answers Type your response and press the key. Type: ? - to repeat an explanation ^ - to change prior input (not always possible) Ctrl/Y - to exit the installation procedure There are two choices for Installation/Upgrade: INITIALIZE - removes all software and data files that were previously on the target disk and installs OpenVMS Alpha. PRESERVE -- installs or upgrades OpenVMS Alpha on the target disk and retains all other contents of the target disk. * NOTE: You cannot use PRESERVE to install OpenVMS Alpha on a disk on which OpenVMS VAX or any other operating system is installed. Do you want to INITIALIZE or to PRESERVE? [PRESERVE]) For an upgrade, press the Return key to accept the default (PRESERVE). 7.2.3 Specifying the Target Disk Next, the procedure asks you for the name of the target disk. If you enter a question mark (?), the system displays a list of devices on your system. Select the appropriate disk and respond to the prompt. For example: You must enter the device name for the target disk on which OpenVMS Alpha will be installed. Enter device name for target disk: (? for choices) dkb400 If you select a device that is not available or that cannot be used for some other reason, the system displays information indicating why the device cannot be used. For example, if you enter MKA500, a tape device, a message similar to the following is displayed: MKA500 is not a disk device Upgrading the OpenVMS Alpha Operating System 7-7 Upgrading the OpenVMS Alpha Operating System 7.2 Performing the Upgrade 7.2.4 Specifying the Volume Label The system then prompts you for the volume label and asks if the information is correct. You can accept the default label assigned by the system (AXPVMSSYS) or specify a different volume label (with a limit of 12 characters that can be letters A-Z, numbers 0-9, dollar signs ($), hyphens (-), or underscores (_)). ________________________ Note ________________________ Compaq strongly recommends that the volume labels for all disks on your system or OpenVMS Cluster have unique labels. If a disk that has the same label as the system disk is mounted, various OpenVMS components will not function as intended. ______________________________________________________ After you select the volume label, the target disk is mounted and page and swap files are created. For example: DKB400: is now labeled ALPHAUPGIV. Do you want to keep this label? (Yes/No) [Yes] OpenVMS Alpha will be upgraded on DKB400:. 7.2.5 Checking Related Software At this point the upgrade performs checks of some related software products. 7.2.5.1 Spiralog If your system contains a version of Spiralog lower than Version 1.2, the following message is displayed: The target system contains a version of SPIRALOG that is not compatible with this version of the operating system. SPIRALOG must be removed before upgrading OpenVMS Alpha. Termination is strongly recommended. Do you want to terminate? (Yes/No) [YES] Note that Spiralog will not work with OpenVMS Alpha Version 7.2. If you have any version of Spiralog installed on your system, uninstall it before upgrading to OpenVMS Alpha Version 7.2. 7-8 Upgrading the OpenVMS Alpha Operating System Upgrading the OpenVMS Alpha Operating System 7.2 Performing the Upgrade 7.2.5.2 AMDS Beginning with OpenVMS version 7.2 and AMDS version 7.2, certain parts of AMDS that were previously supplied with the layered product kit are now incorporated into OpenVMS. Because of this, prior versions of AMDS must be removed. If the upgrade procedure detects a prior version of AMDS, it will display the following message and automatically remove the prior version of AMDS. Note that you must reinstall AMDS if you wish to continue using it. The target system contains a version of DEC AMDS that is not compatible with this version of the operating system. If you continue AMDS will be removed. A current version of AMDS can be installed after the upgrade completes. 7.2.5.3 PATHWORKS If PATHWORKS is installed on the system, OpenVMS Version 7.2 requires PATHWORKS Version V6.0B or later. The installation determines the PATHWORKS version and displays one of the following messages if an earlier version of PATHWORKS is present. If PATHWORKS Version 5 or earlier is present: PATHWORKS V5 is installed on the target system. This version of PATHWORKS will not work on OpenVMS V7.2. You must upgrade to PATHWORKS V6.0B or later, or disable PATHWORKS on the target system, before upgrading OpenVMS. Please refer to the release notes for additional information. Do you want to continue? (Yes/No) [NO] If PATHWORKS Version 6.0 or 6.0A is present: PATHWORKS V6.0-000 is installed on the target system. This version of PATHWORKS is not supported on OpenVMS V7.2. PATHWORKS V6.0B and later are supported on OpenVMS V7.2. You may wish to upgrade to PATHWORKS V6.0B or later before upgrading OpenVMS. Please refer to the release notes for additional information. Do you want to continue? (Yes/No) [NO] Upgrading the OpenVMS Alpha Operating System 7-9 Upgrading the OpenVMS Alpha Operating System 7.2 Performing the Upgrade In both cases the default is to terminate the upgrade. You must explicitly enter Yes and press the Return key to continue. 7.2.6 Checking OpenVMS Cluster Membership The procedure now asks if your system will be part of a cluster. The display is similar to the following: Will this system be a member of an OpenVMS Cluster? (Yes/No) Yes Unlike an installation, answering Yes to this question will not cause SYS$MANGER:CLUSTER_CONFIG.COM to be run. However, correct cluster membership information is required by the upgrade procedure. 7.2.7 Becoming an OpenVMS Galaxy Instance The procedure next asks if your system will be an instance in an OpenVMS Galaxy. The display is similar to the following: Will this system be an instance in an OpenVMS Galaxy? (Yes/No) Yes If you answer Yes to this question, and you also answered Yes to the OpenVMS Cluster question, then information about required remedial kits is displayed. For compatibility with OpenVMS Galaxy, any systems in the OpenVMS Cluster that are running versions of OpenVMS prior to Version 7.1-2 must have a remedial kit installed. The following display indicates the correct remedial kits for various OpenVMS Alpha and VAX systems: For compatibility with OpenVMS Galaxy, any systems in the OpenVMS Cluster that are running versions of OpenVMS prior to V7.1-2 must have a remedial kit installed. The appropriate kit from the following list must be installed on all system disks used by these systems. (Later versions of these remedial kits may be used if available.) Alpha V7.1 and V7.1-1xx ALPSYSB02_071 Alpha V6.2 and V6.2-1xx ALPSYSB02_062 VAX V7.1 VAXSYSB01_071 VAX V6.2 VAXSYSB01_062 7-10 Upgrading the OpenVMS Alpha Operating System Upgrading the OpenVMS Alpha Operating System 7.2 Performing the Upgrade 7.2.8 Memory Channel Information This section contains information specific to becoming a cluster member in a MEMORY CHANNEL environment. The MEMORY CHANNEL remedial kit (ALPMC01_071 and later) changed the data structures used with MEMORY CHANNEL. This change is not backwardly compatible and requires special considerations for MEMORY CHANNEL when upgrading OpenVMS from a version earlier than Version 7.1-2 to Version 7.1-2 (or later), under the following conditions: o Your system disk will be part of an OpenVMS Cluster, and o One or more of the systems in the OpenVMS Cluster has a MEMORY CHANNEL adapter, and o Either: - Your OpenVMS Cluster uses multiple system disks, or - You will be performing a rolling upgrade If your target system is already at OpenVMS Version 7.2 or higher, you have already seen this information. In this case, or if you indicated that the target system will not be a member of an OpenVMS Cluster, the procedure jumps to Section 7.2.9. Otherwise, it proceeds as follows: An OpenVMS Cluster may use more than one system disk, either on a continuing basis, or only during a rolling upgrade. Will the OpenVMS Cluster use more than one system disk? (Yes/No) Yes If you answer Yes to this question, the procedure provides information about MEMORY CHANNEL adapters, as follows: A MEMORY CHANNEL adapter is a device that allows systems in an OpenVMS Cluster to be connected (usually through a MEMORY CHANNEL hub) to provide high speed communications among nodes in the OpenVMS Cluster. If the procedure can detect that a MEMORY CHANNEL adapter (MCA) is present, it displays the following message: This system has a Memory Channel adapter. Otherwise, it displays a question similar to the following: Is a MEMORY CHANNEL adapter installed on this system or on any other system in the OpenVMS Cluster? (Yes/No) yes Upgrading the OpenVMS Alpha Operating System 7-11 Upgrading the OpenVMS Alpha Operating System 7.2 Performing the Upgrade If you answer Yes to this question, or your system has a MEMORY CHANNEL adapter, the following information is displayed. You will be using multiple system disks and MEMORY CHANNEL adapters. This requires special consideration in order to avoid data corruption. Either the ALPMC01_071 TIMA kit must be installed on all system disks, or you must not use the MEMORY CHANNEL until after all system disks in the OpenVMS Cluster have been upgraded to the new OpenVMS release and all systems have rebooted from the upgraded system disks. You can prevent using MEMORY CHANNEL in one of two ways: o Power off the MEMORY CHANNEL hub, if one is used, or o Disconnect the MEMORY CHANNEL cable, if using a virtual hub. You must NOT POWER UP OR RECONNECT until after all system disks in the OpenVMS Cluster have been upgraded to the new OpenVMS release and all systems have rebooted from the upgraded system disks. You can search [VMS$COMMON.SYSUPD]VMSINSTAL.HISTORY for ALPMC on any system disk to determine if the TIMA kit is installed on that disk. Answer the next question with a "?" if you wish to search VMSINSTAL.HISTORY for the ALPMC01_071 TIMA kit. Do you have the ALPMC01_071 TIMA kit installed on all systems disks that are part of the OpenVMS Cluster and that are prior to OpenVMS V7.2? (Yes/No) No If you answer with a question mark (?), the OpenVMS SEARCH command is used to look in VMSINSTAL.HISTORY for the ALPMC01_071 remedial kit. If the kit is found, the line in VMSINSTAL.HISTORY that contains it is displayed. If it is not found, the message "No strings matched" is displayed. In either case, the question is repeated. Answer Yes if the ALPMC01_071 remedial kit is installed as required on all system disks. Otherwise answer No. If you answer No, the procedure continues as follows: Have you powered off the MEMORY CHANNEL hub? (Or disconnected the MEMORY CHANNEL cable?) (Yes/No) No 7-12 Upgrading the OpenVMS Alpha Operating System Upgrading the OpenVMS Alpha Operating System 7.2 Performing the Upgrade Answer Yes if you have powered off the MEMORY CHANNEL hub or disconnected the MEMORY CHANNEL cable. Otherwise, answer No. If you answer No, the procedure continues as follows: Before proceeding with the OpenVMS upgrade, you must either o Install the ALPMC01_071 remedial kit on all system disks that are part of OpenVMS Cluster, or o Take action to prevent using MEMORY CHANNEL. Termination is strongly recommended. Do you want to terminate? (Yes/No) [YES] ________________________ Note ________________________ If termination is recommended, do not attempt to continue. Follow the instructions provided in this section and with the ALPMC01_071 remedial kit. If you continue, your MEMORY CHANNEL will not work correctly and you will encounter problems, including possible data corruption. ______________________________________________________ The upgrade will not recommend terminating if o The system will not be a member of an OpenVMS Cluster, or o The OpenVMS Cluster does not use more than one system disk, or o There is no MEMORY CHANNEL adapter in the OpenVMS Cluster, or o The ALPMC01_071 remedial kit is installed on all systems disks in the OpenVMS Cluster, or o You have powered down the MEMORY CHANNEL hub or disconnected the MEMORY CHANNEL cables Upgrading the OpenVMS Alpha Operating System 7-13 Upgrading the OpenVMS Alpha Operating System 7.2 Performing the Upgrade 7.2.9 Upgrading Windowing and Networking Products The procedure next selects the following Compaq software that is installed on your system: o DECwindows Motif for OpenVMS Alpha o DECnet-Plus for OpenVMS Alpha or DECnet Phase IV for OpenVMS Alpha o DIGITAL TCP/IP Services for OpenVMS ________________________ Note ________________________ If you do not have DECnet for OpenVMS Alpha software installed on your system, you can install that software during the upgrade. Note, however, that you cannot have DECnet-Plus and DECnet Phase IV concurrently installed on your system. Once you have DECnet-Plus and TCP/IP installed on your system, you can run DECnet applications over your TCP/IP network. Please see the DECnet-Plus for OpenVMS Management Guide for more information on DECnet over TCP/IP. Beginning with OpenVMS V7.2, a new implementation of DIGITAL TCP/IP Services is available. This new implementation replaces the UCX product. Older, UCX versions of DIGITAL TCP/IP Services can be upgraded to this new implementation. Note, however, that you CANNOT have both the new TCPIP implementation and the older UCX implementation concurrently installed on your system. ______________________________________________________ If you are upgrading DECnet, the procedure removes the existing version of DECnet during the upgrade. For example, if DECnet Phase IV is installed on your system, and you upgrade to DECnet-Plus, DECnet Phase IV will be removed during the upgrade procedure. The display is similar to the following: 7-14 Upgrading the OpenVMS Alpha Operating System Upgrading the OpenVMS Alpha Operating System 7.2 Performing the Upgrade If necessary, the following products will be upgraded along with the OpenVMS operating system: o DECwindows Motif for OpenVMS Alpha o DECnet-Plus for OpenVMS Alpha o DECnet Phase IV for OpenVMS Alpha o Digital TCP/IP Services for OpenVMS If you want to add or delete these products, you can do so later in the upgrade by answering "NO" to the following question: "Do you want the defaults for all product options?" Beginning with OpenVMS V7.1, DECnet-Plus is provided with the OpenVMS operating system. Compaq recommends that DECnet users install DECnet-Plus. DECnet Phase IV applications are supported by DECnet-Plus. DECnet Phase IV is also provided as an option. Support for DECnet Phase IV is available through a Prior Version Support Contract available through Compaq MCS Services. Once you have DECnet-Plus and TCP/IP installed on your system, you can run DECnet applications over your TCP/IP network. Please see the DECnet-Plus for OpenVMS Management Guide for more information on DECnet over TCP/IP. Do you want to install DECnet-Plus for OpenVMS Alpha V7.2? (Yes/No) [YES] n DECnet Phase IV for OpenVMS Alpha is installed on your system. It will be upgraded. Beginning with OpenVMS V7.2, a new implementation of Digital TCP/IP Services is available. This new implementation replaces the UCX product. Older, UCX version of Digital TCP/IP Services can be upgraded to this new implementation. DIGITAL TCP/IP Services for OpenVMS is not installed on your system. It will not be installed. Some of the windowing and networking products may have versions installed that are below the current versions, but that are still supported on OpenVMS Version 7.2. In this case you will see messages similar to the following: Upgrading the OpenVMS Alpha Operating System 7-15 Upgrading the OpenVMS Alpha Operating System 7.2 Performing the Upgrade A supported version of DECwindows Motif is already installed. You can keep the installed version or upgrade to V1.2-5. Do you want to upgrade to V1.2-5? (Yes/No) [YES] You can choose to keep the currently-installed version, or to upgrade to the latest version supplied with OpenVMS Version 7.2. 7.2.10 Updating Time Zone Information For local time zone support to work correctly, the time zone that accurately describes the location you want to be considered as your default time zone must be set. In addition, your system must be correctly configured to use a valid OpenVMS time differential factor (TDF). If both of these are already set, the procedure continues with Section 7.2.11. If either of these are not set, you are required to set them at this point. The procedure displays a series of time zone menus and prompts you to make selections from each. You begin by selecting the desired time zone from the main time zone menu. If you do not select a time zone, the default is Greenwich Mean Time (GMT). Some time zone choices cause an additional menu to be displayed. This happens when the time zone you select has subcomponents. For example, if you choose the United States (US) time zone from the main menu, a second menu displays the specific time zones within the United States. You then select the menu item that best represents the desired time zone. The procedure then prompts you for the TDF. The TDF is the difference between your system time and Coordinated Universal Time (UTC), which is an international standard (similar to Greenwich Mean Time) for measuring time of day. The procedure supplies a default for TDF. A sample display follows: 7-16 Upgrading the OpenVMS Alpha Operating System Upgrading the OpenVMS Alpha Operating System 7.2 Performing the Upgrade Configuring the Local Time Zone TIME ZONE SPECIFICATION -- Main Time Zone Menu 1) Australia 11) GMT 21) Mexico 31) Turkey 2) Brazil 12) Greenwich 22) NZ 32) UCT 3) CET 13) Hongkong 23) NZ-CHAT 33) US 4) Canada 14) Iceland 24) Navajo 34) UTC 5) Chile 15) Iran 25) PRC 35) Universal 6) Cuba 16) Israel 26) Poland 36) W-SU 7) EET 17) Jamaica 27) ROC 37) WET 8) Egypt 18) Japan 28) ROK 38) Zulu 9) Factory 19) Libya 29) Singapore 10) GB-Eire 20) MET 30) SystemV 0) None of the above Select the number above that best represents the desired time zone: 33 You selected US as your time zone. Is this correct? (Yes/No) [YES]: US Time Zone Menu 1) Alaska 4) Central 7) Hawaii 10) Mountain 2) Aleutian 5) East-Indiana 8) Indiana-Starke 11) Pacific 3) Arizona 6) Eastern 9) Michigan 12) Samoa 0) None of the above Select the number above that best represents the desired time zone: 6 You selected US/Eastern as your time zone. Is this correct? (Yes/No) [YES]: Default Time Differential Factor for standard time is -5:00. Default Time Differential Factor for daylight saving time is -4:00. The Time Differential Factor (TDF) is the difference between your system time and Coordinated Universal Time (UTC). UTC is similar in most respects to Greenwich Mean Time (GMT). The TDF is expressed as hours and minutes, and should be entered in the hh:mm format. TDFs for the Americas will be negative (-3:00, -4:00, etc.); TDFs for Europe, Africa, Asia, and Australia will be positive (1:00, 2:00, etc.). Is daylight savings time in effect? (Yes/No): y Enter the Time Differential Factor [-4:00]: Upgrading the OpenVMS Alpha Operating System 7-17 Upgrading the OpenVMS Alpha Operating System 7.2 Performing the Upgrade NEW SYSTEM TIME DIFFERENTIAL FACTOR = -4:00. Is this correct? [Y]: For more information about TDF and local time zone support, see the OpenVMS System Manager's Manual. 7.2.11 Choosing Descriptive Help Text The system next prompts you as follows: The installation operation can provide brief or detailed descriptions. 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 additional explanatory text with each prompt. 7.2.12 Configuration Options If you are using the OpenVMS Alpha Version 7.2 CD-ROM and have selected a target disk that already has Version 7.2 installed, you are presented with several configuration options. A sample display follows: Version V7.2 of the OpenVMS operating system is already installed on the target disk. You may choose one of the following actions: o Reconfigure the OpenVMS platform. This action will allow you to change your selections of which of the windowing and network products you included with your OpenVMS operating system installation. o Reconfigure the OpenVMS operating system. This action will allow you to change your choices about which options you included for the OpenVMS operating system. o Reinstall the OpenVMS operating system. This action will cause ALL operating system files to be replaced. You can also change your choices about which options you included for the OpenVMS operating system. Reinstall will take longer than Reconfigure. Reinstall may be appropriate if you suspect that files in the operating system, or in the windowing and network products have become corrupted. If you want to reinstall any of the windowing and network products, choose "Install or upgrade layered products and patches" (option 3) from the main menu. 7-18 Upgrading the OpenVMS Alpha Operating System Upgrading the OpenVMS Alpha Operating System 7.2 Performing the Upgrade If you want to change your choices about which options you included for any of the windowing and network products, choose "Reconfigure installed products" (option 5) from the main menu. Please choose one of the following: 1) Reconfigure the OpenVMS platform. 2) Reconfigure the OpenVMS operating system. 3) Reinstall the OpenVMS operating system. 4) Return to the Main Menu (abort the upgrade/installation). Enter choice or ? for help: (1/2/3/4/?) 7.2.13 Selecting Components As you begin the upgrade procedure, the system asks if you want all the default values, meaning all the files and subgroups of files for each component included in the operating system. The display is similar to the following: The following product has been selected: DEC AXPVMS OPENVMS V7.2 Platform (product suite) Configuration phase starting ... You will be asked to choose options, if any, for each selected product and for any products that may be installed to satisfy software dependency requirements. DEC AXPVMS OPENVMS V7.2: OpenVMS and related products platform COPYRIGHT (c) 12-SEP-1998 -- All rights reserved Compaq Computer Corporation Do you want the defaults for all options? [YES] DEC AXPVMS DECNET_PHASE_IV V7.2: DECNET_PHASE_IV Support addendum to DECnet Phase IV service contract required Do you want to continue? [YES] During an upgrade, the POLYCENTER Software Installation utility defines "default values" as the values that you selected when you last installed or upgraded the OpenVMS Alpha operating system on your system. Therefore, before you respond to the prompt, note the following: o If you answer YES (by pressing the Return key) to accept the default values, you will receive the same components that you selected when you last installed or upgraded Upgrading the OpenVMS Alpha Operating System 7-19 Upgrading the OpenVMS Alpha Operating System 7.2 Performing the Upgrade the system (instead of all the components currently available) plus any new components that were not in the previous version of the OpenVMS Alpha operating system. o If you want to include or exclude any components differently from the last installation or upgrade, you must answer NO and then respond to the prompts for each option, even those that you are not changing. o If you want to review the current defaults first, you can answer NO. Then answer YES when the system asks if you want to view the values. If you review the defaults and are satisfied, answer YES to the prompt asking if you are satisfied with the values. However, if you want to make changes, answer NO to that question and then answer YES when the system asks if you want to reenter the values. When selecting components, note the following as well: o Whether you choose all the default values or select individual files, the system will allow you to view your selections and make changes (if necessary). o If you are not sure whether you want certain components, request help by entering a question mark (?) at the prompt for that component (or group of components). o OpenVMS Management Station software is automatically installed on your OpenVMS system disk when you accept all the default values. If you do not accept the default values, you must select the OpenVMS Management Station component (server and client files) if you plan to use that product. After the installation is complete, you can then prepare your OpenVMS Alpha system and your PC to run OpenVMS Management Station by following the procedures described in Appendix D. o If you decide after the upgrade to change which OpenVMS Alpha operating system components you want installed on your system, you must reconfigure the installation as described in Section 1.3.3.2. 7-20 Upgrading the OpenVMS Alpha Operating System Upgrading the OpenVMS Alpha Operating System 7.2 Performing the Upgrade o After you boot the upgraded system disk and log in, you can obtain information about individual system files by entering HELP SYSTEM_FILES at the dollar sign prompt ($). For a complete list of components included with the OpenVMS Alpha Version 7.2 operating system, see Section 3.5.3. 7.2.14 Completing the Upgrade When you have answered all the prompts and selected the components you want installed, the system allows you to review your selections (and make changes if necessary) and then displays messages about the following: o Notification that DECwindows Motif for OpenVMS Alpha, DECnet-Plus for OpenVMS Alpha, DECnet Phase IV for OpenVMS Alpha, or DIGITAL TCP/IP Services for OpenVMS software has been upgraded (or installed) on your system. o Notification that the upgrade has been completed. o Information about running AUTOGEN. o The menu. The following is a sample display. ________________________ Note ________________________ If you perform two installations at the same time to systems connected via MEMORY CHANNEL, you may see a message similar to the following every 5 seconds: %PMA0 CPU00: 30-OCT-1998 14:58:40 Remote System Conflicts with Known System - REMOTE NODE %PMA0 CPU00: 30-OCT-1998 14:58:45 Remote System Conflicts with Known System - REMOTE NODE Disregard the message. The installation or upgrade will proceed normally and the messages will not be present when the system reboots with its real node name. ______________________________________________________ Upgrading the OpenVMS Alpha Operating System 7-21 Upgrading the OpenVMS Alpha Operating System 7.2 Performing the Upgrade Do you want to review the options? [NO] Execution phase starting ... The following products will be installed: DEC AXPS DECNET_PHASE_IV V7.2 Layered Product DEC AXPVMS OPENVMS V7.2 Platform (product suite) DEC AXPVMS VMS V7.2 Operating System The following products will be removed: DEC AXPVMS DECNET_PHASE_IV G7.1 Layered Product DEC AXPVMS OPENVMS G7.1 Platform (product suite) DEC AXPVMS VMS G7.1 Operating System Portion Done: 0%...10%...20%...30%...40%...50%...60%...70%... 80%...90%...100% The following products have been installed: DEC AXPS DECNET_PHASE_IV V7.2 Layered Product DEC AXPVMS OPENVMS V7.2 Platform (product suite) DEC AXPVMS VMS V7.2 Operating System The following products have been removed: DEC AXPVMS DECNET_PHASE_IV V7.1 Layered Product DEC AXPVMS OPENVMS V7.1 Platform (product suite) DEC AXPVMS VMS V7.1 Operating System The upgrade is now complete. When the newly upgraded system is first booted, a special startup procedure will be run. This procedure will: o Run AUTOGEN to set system parameters. o Reboot the system with the newly set parameters. You may shut down now or continue with other operations. Process AXPVMS_INSTALL logged out at 12-SEP-1998 15:34:22.47 Press Return to continue... **************************************************************** You can install or upgrade the OpenVMS Alpha operating system or you can install or upgrade layered products that are included on the OpenVMS Alpha operating system CD-ROM. You can also execute DCL commands and procedures to perform "standalone" tasks, such as backing up the system disk. Please choose one of the following: 7-22 Upgrading the OpenVMS Alpha Operating System Upgrading the OpenVMS Alpha Operating System 7.2 Performing the Upgrade 1) Upgrade, install or reconfigure OpenVMS Alpha Version V7.2 2) Display products and patches that this procedure can install 3) Install or upgrade layered products and patches 4) Show installed products 5) Reconfigure installed products 6) Remove installed products 7) Execute DCL commands and procedures 8) Shut down this system 7.2.15 What to Do Next If you want to install layered products, go to the next section. If you do not want to install layered products or perform any other operations prior to booting the upgraded disk, do the following: 1. Shut down the system by choosing the shutdown option (8) from the menu. 2. Go to Section 7.4. 7.3 Installing Layered Products You can use the menu system included on the operating system CD-ROM to install certain layered products with the POLYCENTER Software Installation utility. You can view a list of the layered products that can be installed in this way by choosing option 2 from the menu. (To install layered products that are not listed, see Chapter 4 and the installation documentation for each layered product.) You may see the following product name while installing layered products: DEC AXPVMS UCX V4.2-PLACEHOLDER Do not attempt to install this kit. This is a "dummy" that is needed for technical reasons to facilitate upgrading from the prior UCX implementation of DIGITAL TCP/IP Services to the new implementation. If you do attempt to install this kit, the following message will be displayed: Upgrading the OpenVMS Alpha Operating System 7-23 Upgrading the OpenVMS Alpha Operating System 7.3 Installing Layered Products The UCX implementation of TCP/IP Services is obsolete and is not supported on OpenVMS V7.2 and higher versions. Starting with OpenVMS V7.2, the UCX implementation of TCP/IP services is replaced by the new TCPIP product. This is a placeholder kit to satisfy OpenVMS upgrade requirements so that UCX can be automatically upgraded to TCPIP. You cannot use this kit to install UCX. The installation will then terminate. You can install (or upgrade to) the new implementation of DIGITAL TCP/IP services, version 5.0, as part of the OpenVMS upgrade. If you wish to install version 5.0 separately, choose the product: DEC AXPVMS TCPIP V5.0-9 To install layered products using the POLYCENTER Software Installation utility, choose option 2 to view the list and then option 3 to perform the installation. For example: Please choose one of the following: 1) Upgrade, install or reconfigure OpenVMS Alpha Version V7.2 2) Display products and patches that this procedure can install 3) Install or upgrade layered products and patches 4) Show installed products 5) Reconfigure installed products 6) Remove installed products 7) Execute DCL commands and procedures 8) Shut down this system Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?) 2 The following versions of the OpenVMS operating system, the DECwindows graphical user interface and network products. are available on the OpenVMS Distribution compact disk. They can be installed by selecting choice 1: DEC AXPVMS VMS version V7.2 DEC AXPVMS DWMOTIF version V1.2-5 DEC AXPVMS DECNET_OSI version V7.2 DEC AXPVMS DECNET_PHASE_IV version V7.2 DEC AXPVMS TCPIP version V5.0-9 7-24 Upgrading the OpenVMS Alpha Operating System Upgrading the OpenVMS Alpha Operating System 7.3 Installing Layered Products The following Layered Product kits are available on the OpenVMS Distribution Compact Disk. They can be installed by selecting choice 3. If already installed, they can be reconfigured by selecting choice 5, or removed by selecting choice 6. ----------------------------------- ----------- ---------- PRODUCT KIT TYPE KIT FORMAT ----------------------------------- ----------- ---------- DEC AXPVMS DECNET_OSI V7.2 Full LP Sequential DEC AXPVMS DECNET_PHASE_IV V7.2 Full LP Sequential DEC AXPVMS DWMOTIF V1.2-5 Full LP Sequential DEC AXPVMS TCPIP V5.0-9 Full LP Sequential DEC AXPVMS UCX V4.2-99PLACEHOLDER Full LP Sequential ----------------------------------- ----------- ---------- 5 items found Press Return to continue... **************************************************************** You can install or upgrade the OpenVMS Alpha operating system or you can install or upgrade layered products that are included on the OpenVMS Alpha operating system CD-ROM. You can also execute DCL commands and procedures to perform "standalone" tasks, such as backing up the system disk. Please choose one of the following: 1) Install or upgrade OpenVMS Alpha Version V7.2 2) Display products and patches that this procedure can install 3) Install or upgrade layered products and patches 4) Show installed products 5) Reconfigure installed products 6) Remove installed products 7) Execute DCL commands and procedures 8) Shut down this system Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?) 3 *********************************************************** If you choose to install or upgrade to DECwindows Motif, please note the following: o If you did not select the OpenVMS DECwindows base support and workstation files options, DECwindows Motif will not run. You must add these options to use DECwindows Motif. Upgrading the OpenVMS Alpha Operating System 7-25 Upgrading the OpenVMS Alpha Operating System 7.3 Installing Layered Products o If you are upgrading DECwindows Motif from Version 1.1 and want to save the OSF/Motif Release 1.1.3 programming files, DO NOT upgrade now. Instead, see the DECwindows Motif Installation Manual and follow the instructions for running PCSI_INSTALLATION.COM. If you choose to install or upgrade DECnet-Plus or DECnet Phase IV, please note the following: o If you did not select the OpenVMS DECNET option, neither version of DECnet will run. You must add this option to use DECnet. You must enter the device name for the target disk on which the layered product(s) install will be performed. Enter device name for target disk: (? for choices) DKB400 DKB400: is labeled ALPHAUPGIV. The installation can provide brief or detailed descriptions. In either case, you can request the detailed descriptions by typing "?". Do you always want detailed descriptions? (Yes/No) [No] 1 - DEC AXPVMS DECNET_OSI V7.2 Layered Product 2 - DEC AXPVMS DECNET_PHASE_IV V7.2 Layered Product 3 - DEC AXPVMS DWMOTIF V1.2-5 Layered Product 4 - DEC AXPVMS TCPIP V5.0-9 Layered Product 5 - DEC AXPVMS UCX V4.2-99PLACEHOLDER Layered Product 6 - All products listed above 7 - Exit Choose one or more items from the menu separated by commas: If you do not want to perform any other operations after you install the layered products, do the following: 1. Shut down the system by choosing the shutdown option (8) from the menu. 2. Go to the next section to perform specific tasks after the system shuts down. 7-26 Upgrading the OpenVMS Alpha Operating System Upgrading the OpenVMS Alpha Operating System 7.4 What to Do After the Shutdown 7.4 What to Do After the Shutdown After the system shuts down, you need to perform certain tasks, depending on the configuration of your system and the type of upgrade you are performing. Refer to the appropriate section. ________________________ Note ________________________ When you boot your system following the shutdown (regardless of the type of upgrade and configuration), note that your system will automatically run AUTOGEN and boot again. ______________________________________________________ 7.4.1 Standalone Upgrade If you are upgrading a standalone system: 1. Reboot the system. 2. Log in to the system. 3. Go to Chapter 8 to perform additional postupgrade procedures. 7.4.2 Concurrent OpenVMS Cluster Upgrade If you are performing a concurrent upgrade in an OpenVMS Cluster environment: ___________________________________________________________ IF_...________________THEN_..._____________________________ you have one system do the following: disk, 1. Reboot each system that uses the upgraded disk. 2. Go to Chapter 8. Upgrading the OpenVMS Alpha Operating System 7-27 Upgrading the OpenVMS Alpha Operating System 7.4 What to Do After the Shutdown ___________________________________________________________ IF_...________________THEN_..._____________________________ you have multiple do the following: system disks, 1. Repeat the upgrade process for each system disk in the cluster, beginning with the preupgrade tasks described in Chapter 5. 2. Reboot each system in the cluster. 3. Log in to an upgraded system. 4. Go to Chapter 8 to perform additional postupgrade procedures. ___________________________________________________________ 7.4.3 Rolling OpenVMS Cluster Upgrade If you are performing a rolling upgrade in an OpenVMS Cluster environment: 1. Log in to the upgraded system. 2. Go to Chapter 8 to perform additional postupgrade procedures. (You will reboot the other systems that boot from the upgraded disk after you complete those tasks.) 7-28 Upgrading the OpenVMS Alpha Operating System 8 _________________________________________________________________ After Upgrading the OpenVMS Alpha Operating System After you upgrade the OpenVMS Alpha operating system, you need to perform several important tasks before you can use the system. These tasks, described in the order in which you perform them, are as follows: o Reforming the shadow set (if applicable) o Registering new licenses o Examining the AUTOGEN report file o Modifying the system parameters file (MODPARAMS.DAT) o Examining your command procedures o Decompressing system libraries o Testing the system with UETP, the user environment test package o Adding and removing operating system files o Preparing your OpenVMS Alpha system and your PC to run OpenVMS Management Station o Installing layered products o Backing up the customized system disk o Rebooting cluster members (if applicable) o Running AUTOGEN o Completing the postupgrade checklist After Upgrading the OpenVMS Alpha Operating System 8-1 After Upgrading the OpenVMS Alpha Operating System 8.1 Reforming the Shadow Set 8.1 Reforming the Shadow Set If you have upgraded a disk in a volume shadowing environment, you must now reform the shadow set as follows: 1. Enter the SHOW DEVICE D command to display a list of disks available on your system. For example: $ SHOW DEVICE D Device Device Error Volume Free Trans Mnt Name Status Count Label Blocks Count Cnt $11$DKB100: (NODE1) Online 0 $11$DKB200: (NODE1) Mounted 0 ALPHA070 918150 1 31 2. Enter a command in the following format: $ MOUNT/CONFIRM/SYSTEM DSAn: /SHADOW=(upgraded-disk:,new-member:) volume-label Note the following conventions: o DSAn: is the virtual unit name of the shadow set. o upgraded-disk: is the name of the shadowed system disk you just upgraded. o new-member: is the name of the disk you want to add as a member of the shadow set. o volume-label is the volume label of the shadowed system disk you just upgraded. ________________________ Note ________________________ When you reform the shadow set, the contents of the new member are replaced by the contents of the disk you upgraded. Specifying the /CONFIRM qualifier reminds you of this fact, confirming that you are specifying the correct name of a disk that either is blank or contains files you no longer need. ______________________________________________________ 8-2 After Upgrading the OpenVMS Alpha Operating System After Upgrading the OpenVMS Alpha Operating System 8.1 Reforming the Shadow Set Example $ MOUNT/CONFIRM/SYSTEM DSA54: /SHADOW=($11$DKB200:,$11$DKB100:) ALPHA072 %MOUNT-F-SHDWCOPYREQ, shadow copy required Virtual Unit - DSA54 Volume label ALPHA072 Member Volume label Owner UIC $11$DKB100: (NODE1) SCRATCH [100,100] Allow FULL shadow copy on the above member(s)? [N]: YES 8.2 Registering New Licenses If you need to register new OpenVMS Alpha or layered product licenses, you can do so by entering the following command: $ @SYS$UPDATE:VMSLICENSE You can also use the LICENSE REGISTER command. For information about registering licenses, see the following: o Section 3.4 in Chapter 3 o Appendix C o The OpenVMS License Management Utility Manual 8.3 Examining the AUTOGEN Report File When AUTOGEN runs, it writes informational and, if necessary, warning messages to the file SYS$SYSTEM:AGEN$PARAMS.REPORT. You should examine the contents of this report file. To view AGEN$PARAMS.REPORT on your screen, enter the following command and press the Return key: $ TYPE SYS$SYSTEM:AGEN$PARAMS.REPORT (You can also print this file or examine it using the EDIT /READ_ONLY command.) For more information on AGEN$PARAMS.REPORT, see the OpenVMS System Manager's Manual. After Upgrading the OpenVMS Alpha Operating System 8-3 After Upgrading the OpenVMS Alpha Operating System 8.3 Examining the AUTOGEN Report File If the report includes a message similar to the following, you might need to modify the size of the page, swap, or dump file: %AUTOGEN-W-DSKSPC, The disk on which DKA0:[SYS0.SYSEXE]PAGEFILE.SYS resides would be over 95% full if it were modified to hold 20000 blocks. For more information about modifying the sizes of the page, swap, and dump files, see the next section. 8.4 Modifying the System Parameters File Review the file SYS$SYSTEM:MODPARAMS.DAT. The upgrade procedure created a new version of this file. The old version is named SYS$SYSTEM:MODPARAMS.DAT_OLD. The new MODPARAMS.DAT file contains all the parameters in the old file, plus various parameters that the upgrade procedure added to ensure that all necessary system parameters are properly propagated from the prior version of OpenVMS. The upgrade procedure also adds comment lines to explain the source of the parameters in each section of the new MODPARAMS.DAT file. Note that the old MODPARAMS.DAT is included in the new MODPARAMS.DAT each time an upgrade is performed. Because of this, if MODPARAMS.DAT is not reviewed and "cleaned up" after each upgrade, it will eventually contain many levels of duplicated parameters. For this reason, you should review MODPARAMS.DAT after each upgrade. This allows you to eliminate the duplication. You can also take this opportunity to modify any parameters, if necessary. The following two sections are examples of instances where you need to modify parameters in MODPARAMS.DAT. 8.4.1 System File Sizes AUTOGEN sets the following files at sizes appropriate for your system: [SYSEXE]SYSDUMP.DMP [SYSEXE]PAGEFILE.SYS [SYSEXE]SWAPFILE.SYS 8-4 After Upgrading the OpenVMS Alpha Operating System After Upgrading the OpenVMS Alpha Operating System 8.4 Modifying the System Parameters File If you have special workloads or configurations, you can specify different sizes for these files by performing the following steps: 1. Log in to the SYSTEM account. 2. Enter the following command: $ @SYS$UPDATE:AUTOGEN SAVPARAMS TESTFILES 3. If the file sizes displayed need to be adjusted, add symbols to the MODPARAMS.DAT file (described in detail in the OpenVMS System Manager's Manual: Tuning, Monitoring, and Complex Systems) and repeat step 2 until you are satisfied with the file sizes. 4. When you are satisfied with the file sizes, enter the following command to ensure that the modified system files are installed when the system is rebooted: $ @SYS$UPDATE:AUTOGEN GENPARAMS REBOOT 8.4.2 OpenVMS Cluster Parameters If you are upgrading an OpenVMS Cluster system, note the following: o The upgrade procedure creates a new MODPARAMS.DAT for system root on your system disk. Normally, there is one root for each Alpha computer that boots from the system disk. You must review each of these MODPARAMS.DAT files. The MODPARAMS.DAT file for the system on which you are running is located in SYS$SYSTEM:MODPARAMS.DAT. The MODPARAMS.DAT files for other roots on the same system disk can be found in SYS$SYSDEVICE:[SYSx.SYSEXE]MODPARAMS.DAT, where x represents the root number; for example, SYS0, SYS1, SYS2, and so forth. (Valid root numbers may include hexadecimal digits-SYSA, SYSB, and so forth.) o Be sure the EXPECTED_VOTES value is correct. That value is the sum of all VOTES in the cluster. For example, if 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 runs automatically. The cluster forms when you have booted enough computers to attain cluster quorum. After Upgrading the OpenVMS Alpha Operating System 8-5 After Upgrading the OpenVMS Alpha Operating System 8.5 Examining Your Command Procedures 8.5 Examining Your Command Procedures The upgrade procedure retains the site-specific versions of the following files located in the [VMS$COMMON] directory: [SYSMGR]LAT$SYSTARTUP.COM [SYSMGR]LOGIN.COM [SYSMGR]SYCONFIG.COM [SYSMGR]SYLOGICALS.COM [SYSMGR]SYLOGIN.COM [SYSMGR]SYPAGSWPFILES.COM [SYSMGR]SYSECURITY.COM [SYSMGR]SYSHUTDWN.COM [SYSMGR]SYSTARTUP_VMS.COM [SYSMGR]TFF$SYSTARTUP.COM [SYSMGR]WELCOME.TXT [SYS$STARTUP]ESS$LAST_STARTUP.DAT The upgrade procedure may provide new templates for some of these files with the .TEMPLATE extension. The new templates might include features that are not in your site-specific files. Check the templates against your site-specific files and edit your files as necessary. 8.6 Testing the System with UETP The User Environment Test Package (UETP) is a software package designed to test whether the OpenVMS Alpha operating system is installed correctly. As part of the postupgrade procedure, Compaq recommends that you run UETP to verify the upgrade. For complete information about using UETP, see the OpenVMS System Manager's Manual. 8.7 Decompressing System Libraries Decompressing the system libraries gives the system faster access to them. The decompressed libraries require several thousand additional blocks of disk space for all libraries to be decompressed. You use the LIBDECOMP.COM procedure to decompress the libraries. 8-6 After Upgrading the OpenVMS Alpha Operating System After Upgrading the OpenVMS Alpha Operating System 8.7 Decompressing System Libraries 8.7.1 Determining Disk Space To find out how much disk space you have, enter the following command and press the Return key: $ SHOW DEVICE SYS$SYSDEVICE If you have approximately 30,000 free blocks on the disk, you can decompress the libraries. Note that you can choose to decompress only the libraries that are used frequently. 8.7.2 Methods of Using LIBDECOMP.COM You can use the LIBDECOMP.COM procedure to decompress libraries in three ways: o Entering a command and responding to prompts from the procedure o Entering an interactive command o Entering a batch command The following three sections describe each method. ________________________ Note ________________________ Before you use the LIBDECOMP.COM procedure, be sure you are logged in to the SYSTEM account. ______________________________________________________ 8.7.3 Responding to LIBDECOMP.COM Prompts If you want to decompress libraries by responding to prompts from the LIBDECOMP.COM procedure, do the following: 1. Enter the following command and then press the Return key: $ @SYS$UPDATE:LIBDECOMP.COM The following information is displayed: OpenVMS Library Decompression Utility After Upgrading the OpenVMS Alpha Operating System 8-7 After Upgrading the OpenVMS Alpha Operating System 8.7 Decompressing System Libraries 1 HELPLIB.HLB 14 NCPHELP.HLB 27 PHONEHELP.HLB 2 STARLET.OLB 15 SDA.HLB 28 LIB.MLB 3 ACLEDT.HLB 16 SHWCLHELP.HLB 29 STARLET.MLB 4 ANLRMSHLP.HLB 17 SYSGEN.HLB 30 STARLETSD.TLB 5 DBG$HELP.HLB 18 ANALAUDIT$HELP.HLB 31 SYS$STARLET_C.TLB 6 DBG$UIHELP.HLB 19 SYSMANHELP.HLB 32 ERFLIB.TLB 7 DISKQUOTA.HLB 20 TFF$TFUHELP.HLB 33 SYS$LIB_C.TLB 8 EDFHLP.HLB 21 EXCHNGHLP.HLB 34 VAXCCURSE.OLB 9 INSTALHLP.HLB 22 TPUHELP.HLB 35 VAXCRTL.OLB 10 LATCP$HELP.HLB 23 EVE$HELP.HLB 36 VAXCRTLD.OLB 11 MAILHELP.HLB 24 EVE$KEYHELP.HLB 37 VAXCRTLT.OLB 12 MNRHELP.HLB 25 UAFHELP.HLB 38 IMAGELIB.OLB 13 EDTHELP.HLB 26 TECO.HLB 39 VMS$VOLATILE_PRIVATE_INTERFACES.OLB A ALL libraries to be decompressed E EXIT this procedure * Enter letter or number(s) of libraries to be decompressed (Separate multiple entries with a comma): 2. Enter the appropriate letter or the numbers of the libraries you want to decompress. To decompress all libraries, the process takes approximately one-half hour. 8.7.4 Using LIBDECOMP.COM Interactively You can execute LIBDECOMP.COM interactively to decompress up to eight libraries at a time by listing the names of the libraries you want to decompress as parameters on the command line. Be sure to separate the library names with commas and do not include the file extensions. For example, to decompress VAXCRTL.OLB, DISKQUOTA.HLB, and LIB.MLB interactively, enter the following command: $ @SYS$UPDATE:LIBDECOMP VAXCRTL, DISKQUOTA, LIB 8-8 After Upgrading the OpenVMS Alpha Operating System After Upgrading the OpenVMS Alpha Operating System 8.7 Decompressing System Libraries 8.7.5 Using LIBDECOMP.COM in Batch You can also execute LIBDECOMP.COM in batch mode to decompress up to eight libraries at a time by listing the names of the libraries you want to decompress as parameters on a command line that includes the SUBMIT command. Be sure to separate the library names with commas and do not include the file extension. For example, to decompress VAXCRTL.OLB, DISKQUOTA.HLB, and LIB.MLB as a batch job, enter the following command: $ SUBMIT/NOTIFY/PARAMETERS=(VAXCRTL, DISKQUOTA, LIB)- _$ SYS$UPDATE:LIBDECOMP ________________________ Note ________________________ When you type the command for a batch job, be sure you enclose the list of library names within parentheses. ______________________________________________________ 8.8 Adding and Removing Operating System Files If you decide after the upgrade to change which OpenVMS Alpha operating system files you want installed on your system, you can use the menu system contained on the OpenVMS Alpha operating system CD-ROM to add or remove files. Note that you can obtain information about individual system files by entering HELP SYSTEM_FILES at the dollar sign prompt ($). The procedure is as follows: 1. Mount and boot the OpenVMS Alpha operating system CD- ROM. 2. Choose option 1 from the menu. 3. Choose the PRESERVE option. 4. Enter the name of the device that contains the system disk and answer the questions. After Upgrading the OpenVMS Alpha Operating System 8-9 After Upgrading the OpenVMS Alpha Operating System 8.8 Adding and Removing Operating System Files 5. After you answer the question "Do you want detailed descriptions?," information regarding reconfiguring or reinstalling is displayed. Read the instructions, then choose the desired entry from the menu of reconfigure /reinstall options. The following is a sample reconfigure operation: Please choose one of the following: 1) Install or upgrade OpenVMS Alpha Version V7.2 2) Display products and patches that this procedure can install 3) Install or upgrade layered products and patches 4) Show installed products 5) Reconfigure installed products 6) Remove installed products 7) Execute DCL commands and procedures 8) Shut down this system Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?) 1 *********************************************************** . . . Do you want to INITIALIZE or to PRESERVE? [PRESERVE] . . . Version V7.2 of the OpenVMS operating system is already installed on the target disk. You may choose one of the following actions: o Reconfigure the OpenVMS platform. This action will allow you to change your selections of which of the windowing and network products you included with your OpenVMS operating system installation. o Reconfigure the OpenVMS operating system. This action will allow you to change your choices about which options you included for the OpenVMS operating system. o Reinstall the OpenVMS operating system. This action will cause ALL operating system files to be replaced. You can also change your choices about which options you included for the OpenVMS operating system. 8-10 After Upgrading the OpenVMS Alpha Operating System After Upgrading the OpenVMS Alpha Operating System 8.8 Adding and Removing Operating System Files Reinstall will take longer than Reconfigure. Reinstall may be appropriate if you suspect that files in the operating system, or in the windowing and network products have become corrupted. If you want to reinstall any of the windowing and network products, choose "Install or upgrade layered products and patches" (option 3) from the main menu. If you want to change your choices about which options you included for any of the windowing and network products, choose "Reconfigure installed products" (option 5) from the main menu. Please choose one of the following: 1) Reconfigure the OpenVMS platform. 2) Reconfigure the OpenVMS operating system. 3) Reinstall the OpenVMS operating system. 4) Return to the Main Menu (abort the upgrade/installation). Enter choice or ? for help: (1/2/3/4/?) 2 The following product has been selected: DEC AXPVMS VMS V7.2 Operating System Configuration phase starting ... You will be asked to choose options, if any, for each selected product and for any products that may be installed to satisfy software dependency requirements. DEC AXPVMS VMS V7.2: OpenVMS Operating System COPYRIGHT (c) 12-SEP-1998 -- All rights reserved Compaq Computer Corporation Do you want the defaults for all options? [YES] Answer NO to this question, and select the options you want as described in Section 3.5.2. A list of components is provided in Section 3.5.3. After you respond to the prompts, the display continues and the installation procedure completes as described in Section 3.5.4. The following is a continuation of the sample display: After Upgrading the OpenVMS Alpha Operating System 8-11 After Upgrading the OpenVMS Alpha Operating System 8.8 Adding and Removing Operating System Files Do you want to review the options? [NO] Execution phase starting ... The following product will be reconfigured: DEC AXPVMS VMS V7.2 Portion done: 0%...10%...20%...30%...40%...50%...60%...80%... 90%...100% The following product has been reconfigured: DEC AXPVMS VMS V7.2 . . . For detailed instructions on how to remove the OpenVMS Alpha operating system from your disk, see Appendix E. 8.9 Preparing to Use OpenVMS Management Station If you installed the OpenVMS Management Station software on your system (either by accepting all default values or by selecting the component manually during the upgrade 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 files o Starting OpenVMS Management Station on other nodes o Verifying that you have the proper memory, disk space, media, and the required software to install and run OpenVMS Management Station on your PC o Installing the client software on your PC For complete information about preparing your OpenVMS system and your PC to run the OpenVMS Management Station server and client software, see Appendix D. ________________________ Note ________________________ After you complete the tasks described in Appendix D, you can then remove those files from your system to save disk space. Do not use the DELETE command to remove the files. Instead, reconfigure the OpenVMS Alpha operating system as described in Section 4.8. ______________________________________________________ 8-12 After Upgrading the OpenVMS Alpha Operating System After Upgrading the OpenVMS Alpha Operating System 8.10 Installing Layered Products 8.10 Installing Layered Products 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 layered products, 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 you did not install those layered products previously during the installation procedure, you can do so using the following procedure. To install layered products that require VMSINSTAL, see Section 8.10.1. ________________________ 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 layered products on a target system that has a different version of the operating system, use the alternate procedure described in the next section. ______________________________________________________ 1. Shut down the system (described in Appendix A). 2. Boot the operating system CD-ROM (locally or from the InfoServer). 3. Choose option 2 from the menu to view which layered products can be installed using the POLYCENTER Software Installation utility. 4. Choose option 3 from the menu to install the layered products. 5. Shut down the system by selecting option 8 from the menu. 6. Boot from the system disk. If the layered product that you want to install is not listed in the display, see the documentation you received with that layered product for installation information. For additional information about installing layered products, see the OpenVMS System Manager's Manual. After Upgrading the OpenVMS Alpha Operating System 8-13 After Upgrading the OpenVMS Alpha Operating System 8.10 Installing Layered Products Be sure you back up the system disk after you install all your layered products. 8.10.1 Alternate Procedure The following is another method for installing layered products from the OpenVMS Alpha operating system CD-ROM: 1. From your running OpenVMS system (the target system disk), mount the OpenVMS Alpha operating system CD-ROM. 2. Locate the directories and files containing the available layered products by entering the following command (where, in the example, DKA400: is the device name of the CD-ROM): $ DIRECTORY /NOHEAD/NOTRAIL DKA400:[*.KIT] You can use the PRODUCT FIND command to locate kits that are installed using the POLYCENTER Software Installation utility. For example: $ PRODUCT FIND * /SOURCE=DKA400:[*.KIT] 3. To install layered products that require VMSINSTAL (indicated in the directories by save-set file names with file types of .A, .B, and so on), enter the @SYS$UPDATE:VMSINSTAL command and then specify the CD-ROM device and directory. For example: $ @SYS$UPDATE:VMSINSTAL * Where will the distribution volumes be mounted: DKB400:[LP.KIT] 4. To install layered products that require the POLYCENTER Software Installation utility (indicated in the directories by file names with file types of .PCSI or .PCSI$DESCRIPTION), use the PRODUCT INSTALL command to specify the CD-ROM device name and directory. The following is an example of the PRODUCT INSTALL command: $ PRODUCT INSTALL name /SOURCE=DKB400:[name.KIT] 8-14 After Upgrading the OpenVMS Alpha Operating System After Upgrading the OpenVMS Alpha Operating System 8.10 Installing Layered Products 8.10.2 DECevent When you install OpenVMS Alpha Version 7.2, the DIAGNOSE command is disabled. To enable the DIAGNOSE command, you must install the DECevent kit provided on the OpenVMS Alpha Version 7.2 CD-ROM following the upgrade to OpenVMS Alpha Version 7.2. The DECevent kit is located in the directory [DECEVENT_0252.KIT] on the CD-ROM. If the DECevent kit provided on the OpenVMS Alpha CD-ROM is not installed after the operating system, users attempting to use the DIAGNOSE command will receive the following system message: $ DIAGNOSE [params] %DIA-E-NOINSTAL, DIAGNOSE has not been installed on this system 8.10.3 Monitoring Performance History The OpenVMS Alpha Version 7.2 operating system CD-ROM also includes a Monitoring Performance History (MPH) kit located in the [MPH] directory. See the OpenVMS Version 7.2 Release Notes for more information about installing and using this optional software. 8.11 Installing DIGITAL OpenVMS Debugger Clients on a PC The DIGITAL OpenVMS Debugger Version 7.2 includes a client/server interface. The debug server runs on the OpenVMS operating system; there are debug clients that run on OpenVMS, Microsoft Windows 95, and Microsoft Windows NT. There is no separate installation procedure for the components that run on the OpenVMS operating system. They are installed when you install the operating system. This section describes the procedure for installing debug clients on a PC. The following table shows which client kit to use for each PC configuration: ___________________________________________________________ Operating CPU__System__________Client_Kit____________________________ IntelMicrosoft [DEBUG_CLIENTS010.KIT]DEBUGX86010.EXE Windows 95 After Upgrading the OpenVMS Alpha Operating System 8-15 After Upgrading the OpenVMS Alpha Operating System 8.11 Installing DIGITAL OpenVMS Debugger Clients on a PC ___________________________________________________________ Operating CPU__System__________Client_Kit____________________________ IntelMicrosoft [DEBUG_CLIENTS010.KIT]DEBUGX86010.EXE Windows NT AlphaMicrosoft [DEBUG_ _____Windows_NT______CLIENTS010.KIT]DEBUGALPHA010.EXE______ The client kits are self-extracting .EXE files. To make these clients available to PC users, copy these files from the distribution media to a suitable PATHWORKS share, FTP server, or other device available to the PC. Once the appropriate executable file has been transferred to the PC, you can run the file to install the debug client on the PC. The InstallShield installation procedure guides you through the installation. By default, the debug client is installed in the \Programs\OpenVMS Debugger directory. You can also click on the Browse button to select an alternate directory. You can choose one of the following installation options: ___________________________________________________________ Install Option______Details________________________________________ Typical Debug Client and the OpenVMS Debugger Manual in HTML format Compact Debug Client only Custom Choice of Debug Client and/or the OpenVMS ____________Debugger_Manual_in_HTML_format_________________ The Typical installation option creates an OpenVMS Debugger program folder that contains shortcuts to the following items: o Debug client o Debug client Help file o The OpenVMS Debugger Manual in HTML format o A Readme file o An Uninstall procedure 8-16 After Upgrading the OpenVMS Alpha Operating System After Upgrading the OpenVMS Alpha Operating System 8.11 Installing DIGITAL OpenVMS Debugger Clients on a PC For information about using the OpenVMS Debugger, see the OpenVMS Debugger Manual. 8.12 Backing Up the Customized System Disk After you have upgraded and customized the OpenVMS Alpha operating system to your satisfaction and installed layered products, protect your work by making a backup copy of the system disk. To back up the system disk: 1. Shut down the system (described in Appendix A). 2. Boot the operating system CD-ROM (locally or from the InfoServer). 3. Use the menu system to enter the DCL environment (option 7). 4. Mount the system disk and the target device on which you will make the backup copy. 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 8 from the menu. 8. Boot from the system disk. For complete information about backup operations, including a description of an alternate method that does not require booting from the operating system CD-ROM and that allows you to back up a shadowed disk without disabling the shadow set, see Appendix B. 8.13 Rebooting Cluster Members If you are performing a rolling upgrade in an OpenVMS Cluster environment and have completed all the postupgrade tasks required for your upgraded system disk, reboot each system that boots from that system disk. For more information about booting your system, see Appendix A. After Upgrading the OpenVMS Alpha Operating System 8-17 After Upgrading the OpenVMS Alpha Operating System 8.14 Running AUTOGEN 8.14 Running AUTOGEN Although AUTOGEN runs automatically at the end of the upgrade procedure, Compaq recommends that you run AUTOGEN periodically after you perform an upgrade. After 24 hours of operation, run AUTOGEN in FEEDBACK mode and reboot the system. Run AUTOGEN in this way again two workdays later. AUTOGEN sets the values of system parameters and the sizes of the page and swap files according to the system's work load. Compaq recommends that you run AUTOGEN from SAVPARAMS through TESTFILES on a weekly basis and examine AGEN$PARAMS.REPORT to determine the need for additional changes. Hardcoded values in MODPARAMS.DAT should not hinder AUTOGEN's ability to calculate feedback parameters. AUTOGEN generally does not reduce the value of parameters that allocate resources; it considers current parameter values to be minimum values, which means you do not have to add MIN_* symbols to MODPARAMS.DAT. AUTOGEN does increase parameter values according to its calculations unless you have specified explicit or maximum values (by adding MAX_* symbols) in MODPARAMS.DAT. For more information about the MODPARAMS.DAT file and about using AUTOGEN in general, see the OpenVMS System Manager's Manual. 8.15 Postupgrade Checklist Use the following checklist to make sure you have performed all the necessary tasks: < In a volume shadowing environment, reform the shadow set. < Register new licenses. < Examine AUTOGEN output stored in the file AGEN$PARAMS.REPORT. < Examine MODPARAMS.DAT. < Examine the command procedure templates supplied with the OpenVMS Alpha Version 7.2 operating system. 8-18 After Upgrading the OpenVMS Alpha Operating System After Upgrading the OpenVMS Alpha Operating System 8.15 Postupgrade Checklist < Decompress the system libraries using LIBDECOMP.COM. < Run the User Environment Test Package (UETP) to test the system (described in the OpenVMS System Manager's Manual). < Add and remove files. < Prepare your OpenVMS Alpha system and your PC to run OpenVMS Management Station by following the procedures described in Appendix D. < Install layered products, including DECwindows (if necessary). < Back up the customized system disk. < Reboot each system that boots from the upgraded system disk (for a rolling upgrade in an OpenVMS Cluster environment). < Run AUTOGEN. After Upgrading the OpenVMS Alpha Operating System 8-19 A _________________________________________________________________ Halt, Boot, and Shutdown Procedures This appendix contains the following information: o Booting operations, including the following: - Booting the operating system CD-ROM, locally and from an InfoServer system - Booting manually from the system disk - Performing a conversational boot - Booting with minimum startup - Booting with the XDelta utility (XDELTA) - Booting from a different directory - Booting with a PMAZB or PMAZC TURBOchannel adapter - Booting over the network with an alternate TURBOchannel adapter - Booting in an emergency o Set, Show, and Writeboot operations, including the following: - Setting the system for automatic booting - Setting and showing boot devices - Setting boot parameters - Using the Writeboot utility o Halt and shutdown operations o Troubleshooting procedures Halt, Boot, and Shutdown Procedures A-1 Halt, Boot, and Shutdown Procedures A.1 Booting Operations A.1 Booting Operations The following sections describe different methods of booting your system. A.1.1 Booting the Operating System CD-ROM If you need to boot the OpenVMS Alpha operating system CD- ROM, either to perform an installation or upgrade or to perform related operations such as mounting or backing up the system disk, follow the steps in the following sections, depending on whether you are booting locally or from the InfoServer. A.1.1.1 Booting from the Local Drive Boot from the local drive as follows: 1. Insert the operating system CD-ROM into the local CD-ROM drive. 2. At the console prompt (>>>), enter the SHOW DEVICE 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 listed in the SHOW DEVICE display) for source-drive. For example, if the SHOW DEVICE display lists the device name of your CD-ROM drive as DKA400, enter the following command and press the Return key: >>> BOOT -FLAGS 0,0 DKA400 After you boot, the system displays a menu from which you can choose options to perform the following tasks: o Install or upgrade the operating system using the POLYCENTER Software Installation utility. o Enter a DCL environment from which you can perform preinstallation or maintenance tasks such as mounting or showing devices and backing up or restoring files on the system disk. o Shut down the system. A-2 Halt, Boot, and Shutdown Procedures Halt, Boot, and Shutdown Procedures A.1 Booting Operations A.1.1.2 Booting from the InfoServer To boot the operating system CD-ROM using the InfoServer, do the following: 1. At the console prompt, enter the following command: >>> B -FLAGS 0,0 -FILE APB_072 lan-device-name Note the following conventions: o APB_072 is the file name of the APB program used for the initial system load (ISL) boot program. o lan-device-name is the name of the local area network (LAN) device identified with your computer. For information about the LAN devices your system supports, refer to the following table. For additional information, see the hardware manuals that you received with your Alpha computer and the OpenVMS Software Product Description. Halt, Boot, and Shutdown Procedures A-3 Halt, Boot, and Shutdown Procedures A.1 Booting Operations ________________________________________________________ Ethernet FDDI Alpha_Computer_____________Device________Device_________ ALPHAbook 1 EOA0 - AlphaServer 400 series EWA0 FWA0 AlphaServer 1000 series ERA0, EWA0 FRA0 AlphaServer 1000A series EWA0 FWA0 AlphaServer 1200 series EWA0 FWA0 AlphaServer 2000 series ERA0, EWA0 FRA0 AlphaServer 2100, 2100A ERA0, EWA0 FRA0 series AlphaServer 4100 series EWA0 FWA0 AlphaServer 8200 series EXA0, EWA0 FXA0 AlphaServer 8400 series EXA0, EWA0 FXA0 AlphaStation 200 series EWA0 FWA0 AlphaStation 400 series EWA0 FWA0 AlphaStation 500 series EWA0 FWA0 AlphaStation 600 series ERA0, EWA0 FWA0 DEC 2000 series ERA0 - DEC 3000 series ESA0 "n/ESA0" DEC 4000 series EZA0 - DEC 7000 series EXA0 FXA0 DEC 10000 series EXA0 FXA0 Digital Personal EWA0 FWA0 Workstation (DPWS) series__________________________________________________ ________________________ Note ________________________ 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 with an Ethernet PMAD device or FDDI DEFTA device by specifying the device name as "n/ESA0". The value for n is the TURBOchannel slot number, which you can obtain by entering the SHOW CONFIGURATION command at the console prompt (>>>) and examining the display. For more information, see Section A.1.8 in Appendix A. A-4 Halt, Boot, and Shutdown Procedures Halt, Boot, and Shutdown Procedures A.1 Booting Operations o On DEC 4000 series, you must specify the ISL file name in uppercase (APB_072). ______________________________________________________ 2. The InfoServer ISL program then displays the following menu: Network Initial System Load Function Version 1.2 FUNCTION FUNCTION ID 1 - Display Menu 2 - Help 3 - Choose Service 4 - Select Options 5 - Stop Enter a function ID value: 3. Respond to the prompts as follows, pressing the Return key after each entry: a. Enter 3 for the function ID. b. Enter 2 for the option ID. c. Enter the service name (ALPHA072). A sample display follows: Enter a function ID value: 3 OPTION OPTION ID 1 - Find Services 2 - Enter known Service Name Enter an Option ID value: 2 Enter a Known Service Name: ALPHA072 After you boot, the system displays a menu from which you can choose options to perform the following tasks: o Install or upgrade the operating system using the POLYCENTER Software Installation utility. Halt, Boot, and Shutdown Procedures A-5 Halt, Boot, and Shutdown Procedures A.1 Booting Operations o Enter a DCL environment from which you can perform preinstallation or maintenance tasks such as mounting or showing devices and backing up or restoring files on the system disk. o Shut down the system. A.1.2 Booting Manually from the System Disk Boot the system disk manually as follows: ___________________________________________________________ IF_...__________________________THEN_...___________________ the OpenVMS Alpha operating go to step 1. system is running, the OpenVMS Alpha operating go to step 4. system_is_not_running,_____________________________________ 1. Log in to the SYSTEM account. 2. Enter the following command and press the Return key: $ @SYS$SYSTEM:SHUTDOWN 3. Answer the questions displayed by the system. When the procedure asks if an automatic reboot should be performed, press the Return key for NO. When the procedure is finished, it displays the following message: SYSTEM SHUTDOWN COMPLETE 4. Halt the system by entering Ctrl/P or by pressing the Halt button. (See Section A.3.1 for more information about how to halt your Alpha computer.) 5. Enter the BOOT command in the following format: BOOT device-name Substitute the device name of the system disk for device-name. For example, to boot from a drive with a device name of DKA400, enter the following command and press the Return key: >>> BOOT DKA400 A-6 Halt, Boot, and Shutdown Procedures Halt, Boot, and Shutdown Procedures A.1 Booting Operations To boot from the network, enter the following command and press the Return key: >>> BOOT ESA0 A.1.3 Performing a Conversational Boot A conversational boot is most commonly used in research and development environments and during software upgrades. Perform a conversational boot to stop the boot process before it completes. The boot process stops after it loads SYS$SYSTEM:SYSBOOT.EXE and displays the SYSBOOT> prompt. At the SYSBOOT> prompt, you can enter specific OpenVMS System Generation utility (SYSGEN) commands to do the following: o Examine system parameter values o Change system parameter values o Specify another parameter file o Specify another system startup command procedure o Select the default system parameter file if you modified system parameters to values that render the system unbootable o Specify a minimum startup There are several ways to perform a conversational boot. The following procedure is the most direct: ___________________________________________________________ IF_...__________________________THEN_...___________________ the OpenVMS Alpha operating go to step 1. system is running, the OpenVMS Alpha operating go to step 4. system_is_not_running,_____________________________________ 1. Log in to the SYSTEM account. 2. Enter the following command and press the Return key: $ @SYS$SYSTEM:SHUTDOWN Halt, Boot, and Shutdown Procedures A-7 Halt, Boot, and Shutdown Procedures A.1 Booting Operations 3. Answer the questions displayed by the system. When the procedure asks if an automatic reboot should be performed, press the Return key for NO. When the procedure is finished, it displays the following message: SYSTEM SHUTDOWN COMPLETE 4. Halt the system by entering Ctrl/P or by pressing the Halt button. (See Section A.3.1 for more information about how to halt your Alpha computer.) 5. To begin the conversational boot, enter the BOOT command in the following format: BOOT -FLAGS 0,1 [device-name] Substitute the device name of the drive from which you want to boot for device-name. For example, if the system disk has a device name of DKA400, enter the following command and press the Return key: >>> BOOT -FLAGS 0,1 DKA400 If you do not specify a device name, the system boots from the boot device assigned when you entered the SET BOOTDEF_DEV command. 6. At the SYSBOOT> prompt, you can enter any of the SYSGEN commands listed in Table A-1. For more information about these SYSGEN commands, see the OpenVMS System Management Utilities Reference Manual. 7. When you finish using the SYSGEN commands, enter the CONTINUE command to complete the boot process. Table_A-1_SYSGEN_Commands_Used_in_the_SYSBOOT_Procedure____ Command_____________Description____________________________ CONTINUE Resumes the boot procedure. DISABLE CHECKS Inhibits checking of parameter values specified with the SET command. (continued on next page) A-8 Halt, Boot, and Shutdown Procedures Halt, Boot, and Shutdown Procedures A.1 Booting Operations Table A-1 (Cont.) SYSGEN Commands Used in the SYSBOOT __________________Procedure________________________________ Command_____________Description____________________________ ENABLE CHECKS Permits checking of parameter values specified with the SET command. HELP Displays a summary of the SYSBOOT commands on the terminal screen. SET parameter-name Establishes the value of a system parameter. SET/STARTUP Sets the name of the system startup command procedure. SHOW [parameter] Displays active, current, default, maximum, and minimum values for specific parameters. (Use qualifiers to display characteristics of parameters grouped by categories.) USE [file-spec] Specifies a parameter file to be used as a source of values. You must enter the entire file specification, including device and directory; you ____________________cannot_specify_a_logical_name._________ For examples of using conversational booting, see Section A.1.4 and Section A.1.9. A.1.4 Booting with Minimum Startup In certain cases, you might want to boot your system without performing the full sequence of startup events. For example, if a startup event prevents you from logging in, you might want to boot the system without executing the startup so that you can log in and fix the problem. You can use the conversational boot to specify a minimum startup. ________________________ Note ________________________ Because this procedure bypasses specific startup operations, it does not autoconfigure the system's peripheral devices. ______________________________________________________ Halt, Boot, and Shutdown Procedures A-9 Halt, Boot, and Shutdown Procedures A.1 Booting Operations Boot the system with minimum startup as follows: 1. Perform a conversational boot by entering the following command at the console prompt: >>> BOOT -FLAGS 0,1 [device-name] 2. Enter the following command and press the Return key: SYSBOOT> SET STARTUP_P1 "MIN" 3. Enter the following command to continue booting: SYSBOOT> CONTINUE 4. After the system boots, log in and enter the following commands to invoke SYSMAN and clear the STARTUP_P1 parameter you set in step 2: $ RUN SYS$SYSTEM:SYSMAN SYSMAN> PARAMETERS USE CURRENT SYSMAN> PARAMETERS SET STARTUP_P1 "" SYSMAN> PARAMETERS WRITE CURRENT A.1.5 Booting with the XDelta Utility (XDELTA) The XDelta utility (XDELTA) is a debugging tool that system programmers use. The procedure for booting all Alpha computers with XDELTA is the same. The following table describes the valid values you can specify when booting with XDELTA: ___________________________________________________________ Value__System_Response_____________________________________ 0 Normal, nonstop boot (default). 1 Begins a conversational boot and then displays the SYSBOOT prompt. 2 Includes XDELTA but does not take the initial breakpoint. 3 Displays the SYSBOOT prompt and includes XDELTA but does not take the initial breakpoint. A-10 Halt, Boot, and Shutdown Procedures Halt, Boot, and Shutdown Procedures A.1 Booting Operations ___________________________________________________________ Value__System_Response_____________________________________ 6 Includes XDELTA and takes the initial breakpoint. 7 Includes XDELTA, displays the SYSBOOT prompt, and takes the initial breakpoint at system _______initialization._____________________________________ The following is an example of booting with XDELTA from the console prompt: >>> BOOT -FLAGS 0,7 For more information about using XDELTA, see the OpenVMS Delta/XDelta Debugger Manual. A.1.6 Booting from a Different Directory By default, the OpenVMS Alpha operating system is installed in the system root directory [SYS0]. However, if you have created a cluster system disk, you can use the SYS$MANAGER:CLUSTER_CONFIG.COM procedure to add a copy of the operating system to a different root directory. (See the OpenVMS System Manager's Manual for more information about using the SYS$MANAGER:CLUSTER_CONFIG.COM procedure.) To boot from a different directory (for example, [SYS3]), enter the BOOT command as follows: >>> BOOT -FLAGS 3,0 DKA200 A.1.7 Booting with a PMAZB or PMAZC TURBOchannel Adapter PMAZB and PMAZC TURBOchannel adapters are adapters that are software-compatible with the integrated SCSI ports on DEC 3000 Alpha series systems. The DEC 3000 Alpha series system consoles implement the SHOW CONFIGURATION console command, which displays information about the TURBOchannel options and the built- in adapters in the system. When a PMAZB or PMAZC adapter is installed in the TURBOchannel, the SHOW CONFIGURATION command displays the "PMAZB-AA" or "PMAZC-AA" string, the TURBOchannel slot number, and the device status. Halt, Boot, and Shutdown Procedures A-11 Halt, Boot, and Shutdown Procedures A.1 Booting Operations The DEC 3000 Alpha series consoles also implement the SHOW DEVICE command, which displays information about the devices in the system. Because the integrated SCSI adapter is built into every DEC 3000 Alpha series system, the SHOW DEVICE console command can display the SCSI devices connected to the integrated SCSI ports. However, the SHOW DEVICE console command cannot display the SCSI devices connected to the PMAZB or PMAZC SCSI ports. To make the console display the devices connected to the PMAZB or PMAZC SCSI ports, enter the following command at the console prompt, where x is the TURBOchannel slot number in which the PMAZB or PMAZC adapter is installed: >>> TEST TCx CNFG This command displays the devices that are connected to each SCSI port of the PMAZB or PMAZC adapter. The device controller letters are either A or B, based upon the PMAZB or PMAZC ports to which the devices are connected. Do not confuse these devices with any DKAxxx or DKBxxx devices displayed by the SHOW DEVICE command, which shows SCSI devices on the integrated SCSI ports only. To boot from a device connected to a PMAZB or PMAZC adapter, enter the boot command as follows: >>> BOOT "X/DKYzzz" The following conventions are used: o X is the TURBOchannel slot number in which the PMAZB or PMAZC adapter is installed. o DK is the device code of the boot device. o Y is either A or B, depending on the SCSI port of the PMAZB or PMAZC adapter that contains the boot device. o zzz is the SCSI unit number of the boot device. The OpenVMS Alpha operating system does not distinguish between the PMAZB or PMAZC adapter and the integrated SCSI adapter. The operating system views them as identical adapters. Because the operating system searches for I/O adapters in backplane slot number order, device controller letters are assigned that correspond to the backplane order of the TURBOchannel options, followed by the integrated adapters. This is different from console SCSI device A-12 Halt, Boot, and Shutdown Procedures Halt, Boot, and Shutdown Procedures A.1 Booting Operations naming, which always designates SCSI devices on the integrated SCSI ports as either "A" or "B" port devices. Example On a DEC 3000 Model 500 Alpha system with no TURBOchannel options installed, the OpenVMS Alpha operating system names the integrated SCSI ports PKA0 and PKB0, and the devices connected to the ports inherit the controller letter from the port controller letter (A or B). However, if a PMAZB or PMAZC adapter is installed in the TURBOchannel, the operating system names the PMAZB or PMAZC SCSI ports PKA0 and PKB0 and names the integrated SCSI ports PKC0 and PKD0. The devices connected to the ports inherit the controller letter from the port controller letter (A, B, C, or D). A.1.8 Booting Over the Network with an Alternate TURBOchannel Adapter You can use an alternate TURBOchannel adapter to boot a DEC 3000 series Alpha computer (with the TURBOchannel option) over the network in an InfoServer or OpenVMS Cluster environment. Examples of alternate TURBOchannel adapters are the PMAD (which connects to the Ethernet) and the DEFTA (which connects to the FDDI). To boot from a TURBOchannel device connected to one of these alternate adapters, enter the boot command as follows: >>> BOOT "n/ESA0" The value for n is the TURBOchannel slot number for the device, which you can obtain by entering the SHOW CONFIGURATION command at the console prompt (>>>) and examining the display. In the following example, the TURBOchannel slot number (listed under the "TCINFO" column) is 0: >>> SHOW CONFIG DEC 3000 - M300 Digital Equipment Corporation VPP PAL X5.56-80800101/OSF PAL X1.34-80800201 - Built on 18-DEC-1996 11:376 Halt, Boot, and Shutdown Procedures A-13 Halt, Boot, and Shutdown Procedures A.1 Booting Operations TCINFO DEVNAM DEVSTAT ------ -------- -------- CPU OK KN16-AA -V3.2-S6CD-I151-sV2.0-DECchip 21064 P3.0-150 ASIC OK MEM OK MEM OK 6 CXT OK 5 NVR OK SCC OK NI OK ISDN OK 4 SCSI OK 0-PMAD-AA TC0 A.1.9 Booting in an Emergency If a system problem prevents your system from booting, you might need to perform an emergency boot operation. Table A-2 summarizes these emergency boot operations, and the sections that follow describe each boot operation in more detail. Table_A-2_Emergency_Boot_Procedures________________________ Operation_____________When_to_Use__________________________ Booting with default When parameter values in the system parameters parameter file have been modified so that the system is unbootable Booting without If an error in the startup or login startup and login procedures prevents you from logging procedures in Booting without the If you have forgotten the password user authorization and cannot log in to a privileged file__________________account______________________________ A-14 Halt, Boot, and Shutdown Procedures Halt, Boot, and Shutdown Procedures A.1 Booting Operations A.1.9.1 Booting with Default System Parameters If the current values stored in the parameter file have been incorrectly modified, these incorrect values might cause the system to become unbootable. With a conversational boot operation, you can reset the active values for all system parameters to the default value. (In most cases, Compaq recommends that you use AUTOGEN to modify system parameters. In certain cases, however, you can use a conversational boot to modify a parameter value temporarily. To change a parameter value permanently, you must edit MODPARAMS.DAT and run AUTOGEN. For instructions, see the OpenVMS System Manager's Manual.) The default values allow you to boot the system temporarily so you can correct the problem. How to Perform This Task 1. Perform a conversational boot by entering the following command at the console prompt: >>> BOOT -FLAGS 0,1 [device-name] 2. At the SYSBOOT> prompt, enter the following command: SYSBOOT> USE DEFAULT This command specifies that default values should be used for all parameters. 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 the parameter value. If you specified the value for the parameter in the AUTOGEN parameter file MODPARAMS.DAT, fix the value in that file and run AUTOGEN. For more information, see the OpenVMS System Manager's Manual. 5. Shut down and reboot the system. Halt, Boot, and Shutdown Procedures A-15 Halt, Boot, and Shutdown Procedures A.1 Booting Operations Example SYSBOOT> USE DEFAULT SYSBOOT> CONTINUE Username: SYSTEM Password: $ RUN SYS$SYSTEM:SYSMAN SYSMAN> PARAMETERS USE CURRENT SYSMAN> PARAMETERS SET NPAGEDYN 2999808 SYSMAN> PARAMETERS WRITE CURRENT SYSMAN> EXIT $ EDIT SYS$SYSTEM:MODPARAMS.DAT . . . [Insert the following line in MODPARAMS.DAT:] MIN_NPAGEDYN = 2999808 . . . $ @SYS$UPDATE:AUTOGEN SAVPARAMS REBOOT A.1.9.2 Booting Without Startup and Login Procedures If the system does not complete the startup procedures or does not allow you to log in, bypass the startup and login procedures. The startup and login procedures provided by Compaq should always work. However, if you introduce an error when modifying the startup or login procedures, it is possible to accidentally lock yourself out of the system. How to Perform This Task 1. Perform a conversational boot by entering the following command at the console prompt: >>> BOOT -FLAGS 0,1 [device-name] 2. Enter the following command at the SYSBOOT> prompt: SYSBOOT> SET/STARTUP OPA0: 3. Enter the following command to continue booting: SYSBOOT> CONTINUE 4. When the system is booted, the operator console displays the DCL command prompt ($). You are logged in. A-16 Halt, Boot, and Shutdown Procedures Halt, Boot, and Shutdown Procedures A.1 Booting Operations 5. Enter the following DCL command: $ SET NOON This command directs the operating system to ignore any errors that might occur. If you do not enter this command and you invoke an error, the system will log you out. 6. Correct the error condition that caused the login failure. (That is, make the necessary repairs to the startup or login procedures, or to the SYSUAF.DAT file.) Invoke a text editor to correct the startup or login file. Note that some system consoles might not supply a screen-mode editor. You can also copy a corrected file and delete the incorrect version by using the RENAME and DELETE commands. 7. Invoke SYSMAN and enter the following commands to reset the startup procedure: $ RUN SYS$SYSTEM:SYSMAN SYSMAN> PARAMETERS USE CURRENT SYSMAN> PARAMETERS SET/STARTUP SYS$SYSTEM:STARTUP.COM SYSMAN> PARAMETERS WRITE CURRENT SYSMAN> EXIT $ 8. Perform a normal startup by entering the following command: $ @SYS$SYSTEM:STARTUP Example SYSBOOT> SET/STARTUP OPA0: SYSBOOT> CONTINUE $ SET NOON $ SET DEFAULT SYS$SYSROOT:[SYSEXE] $ RUN SYS$SYSTEM:SYSMAN SYSMAN> PARAMETERS USE CURRENT SYSMAN> PARAMETERS SET/STARTUP SYS$SYSTEM:STARTUP.COM SYSMAN> PARAMETERS WRITE CURRENT SYSMAN> EXIT $ @SYS$SYSTEM:STARTUP Halt, Boot, and Shutdown Procedures A-17 Halt, Boot, and Shutdown Procedures A.1 Booting Operations A.1.9.3 Booting Without the User Authorization File Ordinarily, the startup and login procedures provided by Compaq always work; however, certain user interventions can cause them to fail. A very simple way to lock yourself out of the system is to set passwords to login accounts and forget them. In such an emergency, you can use the alternate user authorization file rather than the standard user authorization file. ________________________ Note ________________________ You can use this method only to log in to the system from the console terminal; you cannot use other terminal lines. ______________________________________________________ Setting the system parameter UAFALTERNATE defines the logical name SYSUAF to refer to the file SYS$SYSTEM:SYSUAFALT.DAT. If this file is found during a normal login, the system uses it to validate the account and prompts you for the user name and password. If it cannot find this file, the system assumes that the UAF is corrupt and accepts any user name and any two passwords to log you in to the system from the system console. Logins are prohibited from all other terminal lines. When you perform this procedure, the system assigns the following values to your user account: ___________________________________________________________ Field____________Value_____________________________________ Name User name UIC [001,004] Command DCL interpreter Login flags None Priority Value of the system parameter, DEFPRI Resources Values of the PQL system parameters Privileges_______All_______________________________________ A-18 Halt, Boot, and Shutdown Procedures Halt, Boot, and Shutdown Procedures A.1 Booting Operations The process name is usually the name of the device on which you logged in (for example, _OPA0:). How to Perform This Task 1. Perform a conversational boot by entering the following command at the console prompt: >>> BOOT -FLAGS 0,1 [device-name] 2. At the SYSBOOT> prompt, enter the following command: SYSBOOT> SET UAFALTERNATE 1 3. If your system is running DECwindows software, you must also disable the windowing system by entering the following command: SYSBOOT> SET WINDOW_SYSTEM 0 4. Enter the CONTINUE command to continue booting: SYSBOOT> CONTINUE 5. When the startup procedure completes, log in on the console terminal by entering any user name and any two passwords in response to the Username: and Password: prompts. 6. Enter the following command to use the default UAF: $ DEFINE/SYSTEM/EXECUTIVE_MODE SYSUAF SYS$SYSTEM:SYSUAF.DAT 7. Use the Authorize utility to fix the problem that caused you to be locked out of the system (for example, a forgotten password). Enter HELP MODIFY at the UAF> prompt for information about modifying passwords. For more details, see the OpenVMS System Management Utilities Reference Manual. 8. Enter the following commands to invoke SYSMAN and clear the UAFALTERNATE system parameter you set in step 2: $ RUN SYS$SYSTEM:SYSMAN SYSMAN> PARAMETERS USE CURRENT SYSMAN> PARAMETERS SET UAFALTERNATE 0 In most cases, Compaq recommends that you use AUTOGEN to modify system parameters. However, because this parameter is only being changed temporarily, you can use SYSMAN to change it back. Halt, Boot, and Shutdown Procedures A-19 Halt, Boot, and Shutdown Procedures A.1 Booting Operations 9. If you disabled the windowing system in step 3, reenable it by entering the following command: SYSMAN> PARAMETERS SET WINDOW_SYSTEM 1 10.Enter the following command to save the changed system parameter values: SYSMAN> PARAMETERS WRITE CURRENT 11.Shut down and reboot the system. Example SYSBOOT> SET UAFALTERNATE 1 SYSBOOT> SET WINDOW_SYSTEM 0 SYSBOOT> CONTINUE Username: Password: Password: $ DEFINE/SYSTEM/EXECUTIVE_MODE SYSUAF SYS$SYSTEM:SYSUAF.DAT $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE AUTHORIZE> MODIFY SYSTEM/PASSWORD=FGLFTUTU AUTHORIZE> EXIT $ RUN SYS$SYSTEM:SYSMAN SYSMAN> PARAMETERS USE CURRENT SYSMAN> PARAMETERS SET WINDOW_SYSTEM 1 SYSMAN> PARAMETERS SET UAFALTERNATE 0 SYSMAN> PARAMETERS WRITE CURRENT SYSMAN> EXIT $ @SYS$SYSTEM:SHUTDOWN A.2 Set, Show, and Writeboot Operations The following sections describe how to perform SET, SHOW, and Writeboot operations. A.2.1 Setting the System for Automatic Booting Alpha computers can boot automatically from a designated boot device. When you installed the OpenVMS Alpha operating system, you designated the system disk as the default boot device. Section A.2.2 describes how to change the default boot device. A-20 Halt, Boot, and Shutdown Procedures Halt, Boot, and Shutdown Procedures A.2 Set, Show, and Writeboot Operations Alpha computers can boot automatically from the default boot device under the following conditions: o When you first turn on system power o When system power comes on after a power failure o After you shut down the system (if you enter Y when the shutdown procedure asks if an automatic reboot should be performed) o After a bugcheck o If the system halts under program control Set the system to boot automatically by performing the following steps: ___________________________________________________________ IF_...__________________________THEN_...___________________ the OpenVMS Alpha operating go to step 1. system is running, the OpenVMS Alpha operating go to step 4. system_is_not_running,_____________________________________ 1. Log in to the SYSTEM account. 2. Enter the following command and press the Return key: $ @SYS$SYSTEM:SHUTDOWN 3. Answer the questions displayed by the system. When the procedure asks if an automatic reboot should be performed, press the Return key for NO. When the procedure is finished, it displays the following message: SYSTEM SHUTDOWN COMPLETE 4. Halt the system by entering Ctrl/P or by pressing the Halt button. (See Section A.3.1 for more information about how to halt your Alpha computer.) 5. If you have an SMP system with multiple CPUs, enter the following command at the console prompt (>>>) to stop the other CPUs: >>> INITIALIZE Halt, Boot, and Shutdown Procedures A-21 Halt, Boot, and Shutdown Procedures A.2 Set, Show, and Writeboot Operations 6. Enter the following command to show whether the system has been set to boot automatically: >>> SHOW AUTO_ACTION The system displays one of the following: o Restart o Boot o Halt 7. Enter the SET AUTO_ACTION command if you want to change the automatic booting behavior. For example, the following command sets the system to reboot automatically: >>> SET AUTO_ACTION RESTART 8. After you set this variable, Compaq recommends that you set the boot device and operating system flags as well, using the SET BOOTDEF_DEV and SET BOOT_OSFLAGS commands described in the following sections. A.2.2 Setting and Showing Boot Devices Use the SET BOOTDEF_DEV command to tell the system which drive you want to boot from (that drive becomes the default boot device). Use the SHOW BOOTDEF_DEV command to display the current default boot device. Note that when you set this variable, Compaq recommends that you set the operating system boot parameters as well, using the SET BOOT_OSFLAGS command. At the console prompt (>>>), enter the SET BOOTDEF_DEV command in the following format: SET BOOTDEF_DEV device-name Substitute the device name of the system disk for device- name. For example, to boot from a drive with a device name of DKA400 on a DEC 3000 Alpha series computer, enter the following command and press the Return key: >>> SET BOOTDEF_DEV DKA400 A-22 Halt, Boot, and Shutdown Procedures Halt, Boot, and Shutdown Procedures A.2 Set, Show, and Writeboot Operations The next time you boot the system, you can enter the BOOT command without specifying a device name (because DKA400 is now the default boot device). For example: >>> BOOT ________________________ Note ________________________ If you have not used the SET BOOTDEF_DEV command to set the drive to boot from and you enter the BOOT command without specifying a device name, the system displays an error message. ______________________________________________________ Use the SHOW BOOTDEF_DEV command to find out what drive was specified in the last SET BOOT command. For example: >>> SHOW BOOTDEF_DEV To cancel the drive specified in a previous SET BOOTDEF_DEV command, enter the following command and press the Return key: >>> SET BOOTDEF_DEV ________________________ Note ________________________ This command is not valid on DEC 3000 Alpha series systems. ______________________________________________________ A.2.3 Setting Boot Parameters By default, when you boot the operating system, the flags parameter is set to 0. If you want to define parameters to enable specific functions during the booting process, use the SET BOOT_OSFLAGS console command. The following is a list of values you can specify with the SET BOOT_OSFLAGS command: Halt, Boot, and Shutdown Procedures A-23 Halt, Boot, and Shutdown Procedures A.2 Set, Show, and Writeboot Operations ___________________________________________________________ Hexadecimal Value________System_Response_______________________________ 1 Allows a conversational boot (the system displays the SYSBOOT> prompt). 2 Maps XDELTA to a running system. 4 Stops the boot procedure at the initial system breakpoint. 8 Performs a diagnostic bootstrap. 10 Stops the boot procedure at the bootstrap breakpoints. 20 Omits header from secondary bootstrap image. 80 Prompts for the name of the secondary bootstrap file. 100 Halts the system before the secondary bootstrap. 2000 Marks corrected read data error pages as bad. 10000 Displays extensive, detailed debug messages during the boot process. 20000 Displays selected user-oriented messages _____________during_the_boot_process.______________________ The following examples show how to use the SET BOOT_OSFLAGS command: o The following command specifies the root directory as 0 and the parameter as 1, which sets the system to perform a conversational boot from the [SYS0] directory when you enter the BOOT command: >>> SET BOOT_OSFLAGS 0,1 o The following command specifies the root directory as 1 and the parameter as 0, which sets the system (for example, the second host in a two-system DSSI OpenVMS Cluster configuration) to boot from the [SYS1] directory (instead of [SYS0]) when you enter the BOOT command: >>> SET BOOT_OSFLAGS 1,0 A-24 Halt, Boot, and Shutdown Procedures Halt, Boot, and Shutdown Procedures A.2 Set, Show, and Writeboot Operations o The following example specifies the root directory as 0 and the parameters as 1, 2, 4, and 20000 (for a total hexadecimal value of 20007). As a result, when you enter the BOOT command, the system will perform a conversational boot from the [SYS0] directory with XDELTA, stop at the initial system breakpoint, and display relevant user messages. >>> SET BOOT_OSFLAGS 0,20007 To display the parameters you have just set, use the SHOW BOOT_OSFLAGS command. For example: >>> SHOW BOOT_OSFLAGS BOOT_OSFLAGS = 0,20007 A.2.4 Using the Writeboot Utility The Writeboot utility (WRITEBOOT.EXE) is copied to your system disk during the installation procedure. It allows you to create a bootable OpenVMS Alpha system disk from one that was originally created by one of the following methods: o A nonimage backup of an Alpha system disk (possibly corrupting the boot block) o A nonimage restore of an Alpha system disk from an image save set The Writeboot utility also allows you to rewrite the boot block of an OpenVMS Alpha system disk to point to a new version of the OpenVMS Alpha primary bootstrap file (APB.EXE) that you have previously copied to the disk. (Note that the file must be contiguous.) To invoke the Writeboot utility, enter the following command: $ RUN SYS$SYSTEM:WRITEBOOT The utility prompts you as follows: Update VAX portion of boot block (default is Y): Update Alpha portion of boot block (default is Y): Halt, Boot, and Shutdown Procedures A-25 Halt, Boot, and Shutdown Procedures A.2 Set, Show, and Writeboot Operations Answer N (No) to the VAX prompt. If you answer Y (Yes) to update the Alpha boot block, the utility prompts you for the Alpha boot file: Enter Alpha boot file: Specify device-name:[VMS$COMMON.SYSEXE]APB.EXE in response to this prompt, where device-name: indicates the device on which the system disk is mounted. A.3 Halt and Shutdown Operations The following sections describe halt and shutdown operations for Alpha computers. A.3.1 Halting the System During installation, upgrade, and related system operations, you might need to halt your system. The methods for halting Alpha computers differ slightly with certain models, as described in the next section. The following table summarizes the ways you can halt specific Alpha computers: ___________________________________________________________ Alpha_Computer________How_to_Halt__________________________ AlphaServer 300, Do one of the following: 800, 1000, 1200, o Press the Halt button. 2000, 2100 series o Press Ctrl/P. AlphaServer 8200, Press Ctrl/P. 8400 series AlphaStation 200, Do one of the following: 400, 500, 600 o Press the Halt button (if the series graphics monitor is serving as the console). o Press Ctrl/P (if you are using the alternate console and port). A-26 Halt, Boot, and Shutdown Procedures Halt, Boot, and Shutdown Procedures A.3 Halt and Shutdown Operations ___________________________________________________________ Alpha_Computer________How_to_Halt__________________________ DEC 2000, 3000 Do one of the following: series o Press the Halt button (if the graphics monitor is serving as the console). o Press Ctrl/P (if you are using the alternate console and port). DEC 4000 series Do one of the following: o Press the Halt button. o Press the Break key on the console (the default setting). o Press Ctrl/P, but only after using the console command SET TTA0_HALTS n to enable this key combination, where n can be 6 (enables the Break key and Ctrl/P) or 2 (enables Ctrl/P but disables the Break key). DEC 7000, 10000 Press Ctrl/P. series_____________________________________________________ A.3.2 Shutting Down the System Before you shut down the operating system, decide if you want it to reboot automatically or if you want to enter console-mode commands after the shutdown completes. You can perform the following three types of shutdown operations: o An orderly shutdown with SYS$SYSTEM:SHUTDOWN.COM o An emergency shutdown with OPCCRASH.EXE o An emergency shutdown with crash commands If you want the system to reboot automatically after the shutdown, see Section A.2.1. Halt, Boot, and Shutdown Procedures A-27 Halt, Boot, and Shutdown Procedures A.3 Halt and Shutdown Operations A.3.2.1 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, dismounting volumes, and stopping user processes. To use the SHUTDOWN.COM command procedure, log in to the SYSTEM 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. A.3.2.2 Emergency Shutdown with OPCCRASH.EXE If you cannot perform an orderly shutdown with the SHUTDOWN.COM procedure, run the OPCCRASH.EXE emergency shutdown program. To run the OPCCRASH.EXE program, log in to the SYSTEM account, enter the following command, and press the Return key: $ RUN SYS$SYSTEM:OPCCRASH For more information about the OPCCRASH program, see the OpenVMS System Manager's Manual. A.3.2.3 Emergency Shutdown with Crash Commands Use crash commands only if the system is "hung" (stops responding to any commands) and you cannot log in to the SYSTEM account to use the SHUTDOWN.COM procedure or the OPCCRASH.EXE program. ________________________ Note ________________________ The method described here works on all Alpha computers. However, on certain systems, you can force your processor to fail (crash) by entering a specific console command. See the hardware manuals that came with your computer for that information. ______________________________________________________ To force your processor to fail, do the following: 1. Halt the system by entering Ctrl/P or by pressing the Halt button. (See Section A.3.1 for more information about how to halt your Alpha computer.) A-28 Halt, Boot, and Shutdown Procedures Halt, Boot, and Shutdown Procedures A.3 Halt and Shutdown Operations 2. To examine processor registers, enter the following commands and press the Return key: >>> E -N F R0 >>> E PS The system displays the contents of the registers. Write down these values if you want to save information about the state of the system. 3. Enter the following commands and press the Return key: >>> D PC FFFFFFFF00000000 >>> D PS 1F00 By depositing these values, you cause the system to write a memory dump to the system dump file on the disk. 4. Enter the following command and press the Return key: >>> CONTINUE This causes the system to perform a bugcheck. 5. After the system reboots, log in to the SYSTEM account. 6. To examine the dump file, enter the following commands and press the Return key after each one: $ ANALYZE/CRASH SYS$SYSTEM:SYSDUMP.DMP SDA> SHOW CRASH For more information about the System Dump Analyzer (SDA) utility, see the OpenVMS Alpha System Dump Analyzer Utility Manual. A.4 Troubleshooting Procedures The following sections describe procedures that you can follow if you encounter problems with your system. A.4.1 If the System Does Not Boot If the system does not boot because a hardware problem occurs, a question mark (?) usually precedes the error message displayed on the console terminal. An example of a hardware problem is a read error on a disk or tape cartridge drive. Halt, Boot, and Shutdown Procedures A-29 Halt, Boot, and Shutdown Procedures A.4 Troubleshooting Procedures A.4.1.1 For Hardware Problems If you suspect a hardware problem, do the following: 1. Consult the hardware manual for your Alpha computer. 2. Contact a Compaq support representative. A.4.1.2 For Software Problems When the operating system is loaded into memory, a message similar to the following appears on the terminal screen: SYSTEM job terminated at 19-SEP-1997 15:05:03.17 If the system does not display this message, a software problem has probably occurred. Do the following: 1. Turn off the system. Turn it back on and try to reboot. 2. Perform a conversational boot using the default system parameters or try one of the emergency boot procedures. 3. If the system boots, run the AUTOGEN procedure. For more information about the AUTOGEN procedure, see the OpenVMS System Manager's Manual. A.4.2 Detecting and Responding to System Problems If your system exhibits unexpected behavior, note the following: o If the system displays a bugcheck message on the console terminal and shuts itself down, it means the system encountered a problem that made further operation impossible or dangerous. Reboot the system as explained in Section A.1.2, or let it reboot automatically as explained in Section A.2.1. o If the system stops responding to your commands (that is, the system "hangs"), there is a possible failure in a system software or hardware component or a possible power failure. o If the system exhibits erratic behavior (it does not respond according to specifications), it indicates a possible failure in a system software or hardware component. A-30 Halt, Boot, and Shutdown Procedures Halt, Boot, and Shutdown Procedures A.4 Troubleshooting Procedures To determine if the failure is a system problem: o Be sure that you did not press the F1 key (the Hold Screen key). The Hold Screen light goes on when you press either F1 or enter Ctrl/S. o Enter Ctrl/T to check the status of your process. A status line should appear, indicating the name of the program that is executing and other information. 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 command SET NOCONTROL=T or have set the terminal to NOBROADCAST mode by entering the command SET TERMINAL/NOBROADCAST, this procedure does not work.) o Make sure the cable connecting the terminal or monitor to the system is secure. If you determine that you have a system problem: 1. Force an exit from a stalled or "hung" program by entering Ctrl/Y. Note that when you enter Ctrl/Y, any work performed by the program and not saved on disk is lost. 2. If the system is still unresponsive, halt it by entering Ctrl/P or by pressing the Halt button. (See Section A.3.1 for more information about how to halt your Alpha computer.) 3. Note in detail the sequence of events that caused the problem and notify a Compaq support representative. Halt, Boot, and Shutdown Procedures A-31 B _________________________________________________________________ Backing Up and Restoring the System Disk This appendix describes how to perform backup and restore operations on the system disk. You perform these tasks by entering commands from a specialized backup environment. You access this environment through the menu that is displayed when you boot the OpenVMS Alpha operating system CD-ROM or through an alternate method that does not require the CD-ROM. This specialized backup environment is required because it allows you to create an exact copy of the system disk. You cannot create an exact copy in a standard operating system environment because the OpenVMS Backup utility saves only what is on the disk at the moment the BACKUP command is executing, excluding portions of open files contained in memory or data about files not yet written back to the disk (cache). For more information about backup operations, including procedures for backing up and restoring files and directories, see the OpenVMS System Manager's Manual. B.1 Reasons for Backing Up the System Disk The primary reason why you should have a backup copy of the system disk is so you can fully restore your system in response to any hardware or software problem that affects the integrity of your original system disk or your ability to access it. For example, you would need to use the backup copy to restore your system under the following conditions: o When a problem occurs during an OpenVMS Alpha upgrade or update, or during the installation of other software products. If you backed up the system disk before you attempted any of those procedures, you could restore the system disk and attempt the procedure again. Backing Up and Restoring the System Disk B-1 Backing Up and Restoring the System Disk B.1 Reasons for Backing Up the System Disk o When a system file that is accidentally deleted renders the system disk inoperable. If you backed up the system disk after you installed or upgraded the OpenVMS Alpha operating system and any other software products, you could restore the system disk. o When the drive that holds the system disk malfunctions. If you have a backup copy of the system disk, you can restore it to a functioning disk and continue to use the system. Another reason for backing up the system disk is to eliminate disk fragmentation, which occurs when files are stored noncontiguously on the disk. The BACKUP /IMAGE command creates a copy on which files are stored contiguously. B.2 Suggested Procedures Compaq recommends the following: o The preferred method for performing system disk backup and restore operations is to boot the operating system CD-ROM, choose the DCL option from menu, and then enter the appropriate backup commands. The detailed procedures are described in Section B.4 and Section B.5. However, if you do not have access to the compact disc or if you want to back up a shadowed system disk without disabling the shadow set, you can use a different procedure, described in Section B.6. o Store the backup media in a safe place. o If you have an OpenVMS Cluster environment with more than one system disk, be sure the volume label on each system disk and backup copies of system disks are unique. Use the SET VOLUME/LABEL command to change a volume label, if necessary. B-2 Backing Up and Restoring the System Disk Backing Up and Restoring the System Disk B.3 OpenVMS Cluster Caution B.3 OpenVMS Cluster Caution If any nodes except the node used to run BACKUP are booted during the backup operations described in this appendix, your cluster will become partitioned, where nodes in the existing cluster divide into two or more independent clusters. This condition can cause data file corruption. In addition, these backup environments do not restrict your use of DCL commands to the BACKUP command only, which further increases your risk of accidentally destroying or corrupting data on a disk. Therefore, to avoid jeopardizing the integrity of your data in any way, Compaq recommends that you shut down the entire OpenVMS Cluster system before you back up your system disk. B.4 Backing Up the System Disk The following sections describe how to back up the system disk. B.4.1 Getting Started Before you back up the system disk, do the following: 1. In an OpenVMS Cluster environment, dismount the system disk from all systems in the cluster that have the disk mounted as a data disk (rather than as the system disk). 2. Shut down all systems booted from that disk. 3. Boot the operating system CD-ROM locally or from the InfoServer (as described in Appendix A). 4. Choose the DCL option (7) from the menu. For example: **************************************************************** You can install or upgrade the OpenVMS Alpha operating system or you can install or upgrade layered products that are included on the OpenVMS Alpha operating system CD-ROM. You can also execute DCL commands and procedures to perform "standalone" tasks, such as backing up the system disk. Please choose one of the following: Backing Up and Restoring the System Disk B-3 Backing Up and Restoring the System Disk B.4 Backing Up the System Disk 1) Install or upgrade OpenVMS Alpha Version V7.2 2) Display products and patches that this procedure can install 3) Install or upgrade layered products and patches 4) Show installed products 5) Reconfigure installed products 6) Remove installed products 7) Execute DCL commands and procedures 8) Shut down this system Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?) 7 5. At the triple dollar sign prompt ($$$), enter the SHOW DEVICES command. 6. Examine the list of devices so you can determine which device is the source drive (the system disk you want to back up) and which device is your target drive (the supported disk or tape device that will hold the backed up files). B.4.2 Mounting Devices When you have determined which devices will be the source drive and target drive, mount those devices (and any other output devices you plan to use) before you perform any backup operations. Enter the MOUNT commands in the following format: $$$ MOUNT/OVERRIDE=IDENTIFICATION source-drive $$$ MOUNT/FOREIGN target-drive Note the following conventions: o source-drive is the name of the drive holding the system disk. o target-drive is the name of the drive that will hold the backup files. B.4.3 Entering the BACKUP Command When the system disk and output devices are mounted, back up the system disk by entering the BACKUP command in the following format: $$$ BACKUP/IMAGE/VERIFY source-drive: target-drive: B-4 Backing Up and Restoring the System Disk Backing Up and Restoring the System Disk B.4 Backing Up the System Disk (You must also include the save-set name and the /SAVE_SET qualifier if the target drive is a tape device.) Example 1 In this example the system disk and a target disk are mounted so the BACKUP command can create a backup disk. (You can use a backup disk as a system disk.) $$$ MOUNT/OVERRIDE=IDENTIFICATION DKA200 $$$ MOUNT/FOREIGN DKA300 $$$ BACKUP/IMAGE/VERIFY DKA200: DKA300: Example 2 In this example the system disk and a target tape device are mounted so the BACKUP command can create a backup tape. $$$ MOUNT/OVERRIDE=IDENTIFICATION DKA200 $$$ MOUNT/FOREIGN MKA300 $$$ BACKUP/IMAGE/VERIFY DKA200: MKA300:APR_06_BACKUP.BCK/SAVE_SET B.4.4 Changing the CLUSTER_SIZE Parameter The BACKUP command creates a system disk that includes a set of volume parameters provided by Compaq, including a CLUSTER_SIZE (disk access scheme) that is appropriate for your system. (The CLUSTER_SIZE refers to the way files are stored on the disk, not to cluster environments.) You can change most volume parameters later with the SET VOLUME command. However, to change the CLUSTER_SIZE, you must back up the system disk to a disk that has been previously initialized with the CLUSTER_SIZE that you want. For more information about initializing a disk and using the BACKUP command, see the OpenVMS System Manager's Manual and the OpenVMS System Management Utilities Reference Manual, and see the description of the INITIALIZE and BACKUP commands in the OpenVMS DCL Dictionary. B.4.5 What to Do Next After you complete the backup operation: 1. Enter the LOGOUT command to exit from the DCL environment and return to the menu. 2. Choose the shutdown option (8). Backing Up and Restoring the System Disk B-5 Backing Up and Restoring the System Disk B.4 Backing Up the System Disk 3. After the shutdown completes, boot from the system disk. B.5 Restoring the System Disk The following sections describe how to restore the system disk. B.5.1 Getting Started Before you can restore the system disk: 1. Shut down the system. 2. Boot the operating system CD-ROM locally or from the InfoServer (as described in Appendix A). 3. Choose the DCL option (7) from the menu. For example: **************************************************************** You can install or upgrade the OpenVMS Alpha operating system or you can install or upgrade layered products that are included on the OpenVMS Alpha operating system CD-ROM. You can also execute DCL commands and procedures to perform "standalone" tasks, such as backing up the system disk. Please choose one of the following: 1) Install or upgrade OpenVMS Alpha Version V7.2 2) Display products and patches that this procedure can install 3) Install or upgrade layered products and patches 4) Show installed products 5) Reconfigure installed products 6) Remove installed products 7) Execute DCL commands and procedures 8) Shut down this system Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?) 7 4. At the triple dollar sign prompt ($$$), enter the SHOW DEVICES command. 5. Examine the list of devices so you can determine which device is the source drive (the drive holding the backed up files you want to restore) and which device is your target drive (the disk on which you want the files restored). B-6 Backing Up and Restoring the System Disk Backing Up and Restoring the System Disk B.5 Restoring the System Disk B.5.2 Mounting Devices When you have determined which devices will be the source drive and target drive, mount those devices (and any other output devices you plan to use) before you perform any restore operations. Enter the MOUNT commands in the following format: $$$ MOUNT/OVERRIDE=IDENTIFICATION source-drive $$$ MOUNT/FOREIGN target-drive Note the following conventions: o source-drive is the device holding the files you want to restore. (Note, however, that you must use the MOUNT/FOREIGN command if the source drive is a tape device.) o target-drive is the destination. B.5.3 Entering the BACKUP Command Enter the BACKUP command in the following format: $$$ BACKUP/IMAGE/VERIFY source-drive: target-drive: (You must also include the save set name and the /SAVE_SET qualifier if the source drive is a tape device.) Example 1 In this example a backup disk and a target disk are mounted so the BACKUP command can restore the system disk from the backup disk: $$$ MOUNT/OVERRIDE=IDENTIFICATION DKA300 $$$ MOUNT/FOREIGN DKA200 $$$ BACKUP/IMAGE/VERIFY DKA300: DKA200: Example 2 In this example a backup tape and a target disk are mounted so the BACKUP command can restore the system disk from the backup tape: $$$ MOUNT/FOREIGN MKA300 $$$ MOUNT/FOREIGN DKA200 $$$ BACKUP/IMAGE/VERIFY MKA300:APR_06_BACKUP.BCK/SAVE_SET DKA200: Backing Up and Restoring the System Disk B-7 Backing Up and Restoring the System Disk B.5 Restoring the System Disk B.5.4 What to Do Next After you complete the restore operation: 1. Enter the LOGOUT command to exit from the DCL environment and return to the menu. 2. Choose the shutdown option (8). 3. After the shutdown completes, boot from the system disk. B.6 Alternate Backup and Restore Procedure This section describes an alternate method of performing backup and restore operations on your system disk. With this method, you install the operating system (without options) on another disk and perform your backup and restore operations on the system disk from there. Use this method under the following conditions: o If you do not have access to the operating system CD-ROM and its menu system o If you want to back up a shadowed system disk without disabling the shadow set ________________________ Note ________________________ It is also possible to back up your running system disk by using the qualifier /IGNORE=INTERLOCK with the BACKUP command and ignoring warning messages. However, that method requires that all other use of the system be suspended, including disabling logins, stopping print and batch queues, and turning off networking software. In addition, you cannot use this method to restore files to the running system disk. Because of these limitations, Compaq recommends that if you must use an alternate method to back up or restore the system disk, you use the method described in this section. ______________________________________________________ B-8 Backing Up and Restoring the System Disk Backing Up and Restoring the System Disk B.6 Alternate Backup and Restore Procedure B.6.1 Preparing an Alternate System Disk Prepare an alternate system disk as follows: 1. Log in to a privileged account on your running OpenVMS Alpha system. 2. Using the SHOW DEVICE command, identify a data disk on which you can install the operating system, with no options. This will be your target disk during that installation. Note the following: o You will need approximately 75,000 blocks to install the operating system with no options. o Existing data will remain on the disk. 3. The target disk must be mounted privately to your process. (This prevents other users from accessing this disk during the installation and backup procedures.) Therefore, if the target disk was mounted with /SYSTEM, /CLUSTER, /GROUP, or /SHARE, dismount that disk and mount it without using those qualifiers or the /FOREIGN qualifier. For example: $ MOUNT/OVERRIDE=IDENTIFICATION DKA200 4. Enter the following command to install the OpenVMS Alpha operating system, with no options, on the target disk: $ @SYS$SYSTEM:AXPVMS$PCSI_INSTALL_MIN.COM [target-disk] (The procedure will prompt you for a device name if you do not specify it on the command line.) 5. As the procedure completes the installation, the display is similar to the following: DEC AXPVMS OPENVMS V7.2: OpenVMS and related products platform COPYRIGHT (c) 12-SEP-1998 -- All rights reserved Compaq Computer Corporation Execution phase starting ... The following product will be installed: DEC AXPVMS VMS V7.2 Portion Done: 0%...10%...20%...30%...40%...50%...60%... 70%...80%...90%...100% Backing Up and Restoring the System Disk B-9 Backing Up and Restoring the System Disk B.6 Alternate Backup and Restore Procedure The following product has been installed: DEC AXPVMS VMS V7.2 . . . The installation of minimum OpenVMS Alpha is now complete. Use the following command to boot minimum OpenVMS: BOOT -FLAGS E,O (Your system may require additional parameters to boot.) _______________________ Caution _______________________ If your system is a cluster member, Compaq recommends that you shut down the entire OpenVMS Cluster system before you back up your system disk. This will prevent you from creating a partitioned cluster and from jeopardizing the integrity of your data in any other way. ______________________________________________________ B.6.2 Using the Alternate System Disk Use the alternate system disk (on which you installed the operating system with no options) to perform backup and restore operations as follows: 1. Shut down your system. 2. Boot the alternate system disk from the SYSE root. For example: >>> BOOT -FLAGS E,0 DKA200 The system automatically logs you in to the SYSTEM account and then displays a triple dollar sign prompt ($$$). ________________________ Note ________________________ During the boot and login operations on this minimum version of the operating system, you can ignore license messages that are similar to the following: ______________________________________________________ B-10 Backing Up and Restoring the System Disk Backing Up and Restoring the System Disk B.6 Alternate Backup and Restore Procedure %LICENSE-I-NOLICENSE, no license is active for this software product 3. If your system disk is shadowed, install and load a Volume Shadowing license on this data disk. You will then be able to back up the shadowed system disk from this data disk without disabling the shadow set. ________________________ Note ________________________ Compaq recommends that you do not install any other licenses, including OpenVMS licenses, on this alternate system. You will be able to use the system only from the console. ______________________________________________________ 4. Mount the system disk and any output devices you plan to use during the backup or restore operations. See Section B.5.2 for more information. 5. Perform the necessary backup and restore operations by entering the appropriate BACKUP commands. See Section B.5.3 for more information. 6. Shut down the system. 7. Boot from your original system disk. Backing Up and Restoring the System Disk B-11 C _________________________________________________________________ License Management Supplement This appendix contains information that supplements the license instructions in this manual and in the OpenVMS License Management Utility Manual. After you install the OpenVMS Alpha operating system, you must register OpenVMS Alpha licenses, which let you use the OpenVMS Alpha operating system. You must also register the licenses for the OpenVMS Alpha layered products you have purchased, such as DECnet for OpenVMS. (Note that 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 need to obtain a Product Authorization Key (PAK). A PAK is a printed document provided by Compaq that contains the appropriate information to authorize access to software on an Alpha computer (or in an OpenVMS Cluster environment). You can obtain a PAK from a Compaq support representative in the same way as you obtain software. C.1 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 shown in Table C-1. Column A in the LURT indicates the number of license units required for each processor listed in the System Marketing Model column. Column H refers to layered products you may choose to register as well. For example, if your PAK specifies availability = A, you would require 50 license units to load the license on a DEC 3000 Alpha Model 500 series computer, or 500 license units to load the license on a DEC 7000 Alpha Model 610 computer. License Management Supplement C-1 License Management Supplement C.1 Using the License Unit Requirement Table (LURT) Note that some PAKs specify MOD_UNITS in the options field. The MOD_UNITS option allows the system manager to use the DCL command LICENSE MODIFY/UNITS to temporarily increase the size of the PAK. This permits a product to be used, in certain emergency situations, on a processor larger than the processor size specified in the license. Check your license terms and conditions before modifying license units. Reset the PAK size to its original size after the emergency situation is resolved. Table_C-1_License_Unit_Requirement_Table_(LURT)____________ System_Marketing_Model______A___________H__________________ ALPHAbook 1 12 1050 AlphaServer 400 12 1050 AlphaServer 800, 1000, 15 1050 1000A AlphaServer 1200 (1 CPU) 25 1050 AlphaServer 1200 (2 CPU) 75 1050 AlphaServer 2000, 2000A 400 1100 (1 CPU) AlphaServer 2000, 2000A 500 1100 (2 CPU) AlphaServer 2100, 2100A 400 1100 (1 CPU) AlphaServer 2100, 2100A 500 1100 (2 CPU) AlphaServer 2100, 2100A 600 1100 (3 CPU) AlphaServer 2100, 2100A 700 1100 (4 CPU) Key_to_License_Type_Codes_and_Values:______________________ A-The number of OpenVMS Alpha operating system license units (Unlimited or Base) required for the system. B through G-Omitted from table; reserved for future use. H- The number of OpenVMS Alpha layered products license units required for the system. (continued on next page) C-2 License Management Supplement License Management Supplement C.1 Using the License Unit Requirement Table (LURT) Table_C-1_(Cont.)_License_Unit_Requirement_Table_(LURT)____ System_Marketing_Model______A___________H__________________ AlphaServer 4100 (1 CPU) 400 1100 AlphaServer 4100 (2 CPU) 500 1100 AlphaServer 4100 (3 CPU) 600 1100 AlphaServer 4100 (4 CPU) 700 1100 AlphaServer 8200 (1 CPU) 2000 1150 AlphaServer 8200 (2 CPU) 2100 1150 AlphaServer 8200 (3 CPU) 2200 1150 AlphaServer 8200 (4 CPU) 2300 1150 AlphaServer 8200 (5 CPU) 2400 1150 AlphaServer 8200 (6 CPU) 2500 1150 AlphaServer 8400 (1 CPU) 2600 1150 AlphaServer 8400 (2 CPU) 2700 1150 AlphaServer 8400 (3 CPU) 2800 1150 AlphaServer 8400 (4 CPU) 2900 1150 AlphaServer 8400 (5 CPU) 3000 1150 AlphaServer 8400 (6 CPU) 3100 1150 AlphaServer 8400 (7 CPU) 3200 1150 AlphaServer 8400 (8 CPU) 3300 1150 AlphaServer 8400 (9 CPU) 3400 1150 AlphaServer 8400 (10 CPU) 3500 1150 AlphaServer 8400 (11 CPU) 2600 1150 AlphaServer 8400 (12 CPU) 2600 1150 AlphaStation 205, 250, 12 1050 255, 500 AlphaStation 400 12 1050 Key_to_License_Type_Codes_and_Values:______________________ A-The number of OpenVMS Alpha operating system license units (Unlimited or Base) required for the system. B through G-Omitted from table; reserved for future use. H- The number of OpenVMS Alpha layered products license units required for the system. (continued on next page) License Management Supplement C-3 License Management Supplement C.1 Using the License Unit Requirement Table (LURT) Table_C-1_(Cont.)_License_Unit_Requirement_Table_(LURT)____ System_Marketing_Model______A___________H__________________ AlphaStation 600 12 1050 DEC 2000-300/300S 12 1050 DEC 2000-500/500S 12 1050 DEC 3000-300 15 1050 DEC 3000-300L 15 1050 DEC 3000-400/400S 20 1050 DEC 3000-600/600S 20 1050 DEC 3000-500/500S 50 1100 DEC 3000-500X 50 1100 DEC 3000-800/800S 50 1100 DEC 4000-610 300 1150 DEC 4000-620 400 1200 DEC 4000-710 300 1150 DEC 4000-720 400 1200 DEC 7000-610 500 1200 DEC 7000-620 600 1250 DEC 7000-630 700 1250 DEC 7000-640 800 1250 DEC 10000-610 800 1250 DEC 10000-620 900 1300 DEC 10000-630 1000 1300 DEC 10000-640 1100 1300 Key_to_License_Type_Codes_and_Values:______________________ A-The number of OpenVMS Alpha operating system license units (Unlimited or Base) required for the system. B through G-Omitted from table; reserved for future use. H- The number of OpenVMS Alpha layered products license __units_required_for_the_system.___________________________ C-4 License Management Supplement License Management Supplement C.2 License Management Facility (LMF) Notes C.2 License Management Facility (LMF) Notes The following list addresses some common concerns and questions regarding the License Management Facility (LMF). For full explanations of these issues, see the OpenVMS License Management Utility Manual. o If you do not have a valid OpenVMS Alpha license that is registered and activated, the system displays a warning message as part of system startup and restricts system use to the operator's console, OPA0. o If a checksum error is displayed when you register a license, check all the fields of data that you entered, including the checksum itself. o After your PAKs are registered, they are activated (loaded) automatically as part of each system startup. o If an OpenVMS Alpha license is registered with insufficient license units, the system displays the following message when the user (process) attempts to log in: %LICENSE-F-EXCEEDED, licensed product has exceeded current license limits Users can always log in to the operator's console, OPA0, however. o The default LICENSE database is located in the file SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB. You can move the database, although Compaq does not recommend doing so. If you move the database, you must either define the logical name LMF$LICENSE at the system level to point to the new database or use the /DATABASE=filespec qualifier with all LICENSE commands. To redirect LMF to another database location on a more permanent basis, add the following line to the command procedure SYS$MANAGER:SYLOGICALS.COM: $ DEFINE/SYSTEM LMF$LICENSE device:[directory]LMF$LICENSE.LDB If you specify a device other than SYS$SYSDEVICE, you must also mount the specified disk from the SYLOGICALS.COM command procedure. License Management Supplement C-5 License Management Supplement C.2 License Management Facility (LMF) Notes o Each OpenVMS Alpha find license is restricted to a single node for permanent PAKs. You must assign a System Communications Services (SCS) name to the license when you register with the VMSLICENSE.COM command procedure, or you must enter a LICENSE MODIFY/INCLUDE=node-name command after you register the license. ________________________ Note ________________________ The SCS node name is not necessarily the DECnet node name. SCSNODE is a system parameter; it can be a maximum of six alphabetic characters. ______________________________________________________ C.2.1 Restrictions Availability Product Authorization Keys (PAKs) are available for the OpenVMS Alpha operating system. An OpenVMS Alpha PAK is identified by the keyword ALPHA in the PAK's option field. Note the following restrictions: o PAKs having the ALPHA option can be loaded and used only on Alpha computers. However, they can safely reside in a license database (LDB) shared by both VAX and Alpha systems. o Because the LMF for Alpha systems is capable of handling all types of PAKs, including those for VAX systems, Compaq recommends that you perform your LDB tasks using the Alpha LMF. o Availability PAKs for VAX systems (availability PAKs without the ALPHA option) will not load on Alpha systems. Only those availability PAKs containing the ALPHA option will load on Alpha systems. o Other PAK types such as activity (also known as concurrent or n-user) and personal use (identified by the RESERVE_UNITS option) work on both VAX and Alpha systems. o Avoid using the following LICENSE commands from a VAX system on a PAK containing the ALPHA option: - REGISTER - DELETE/STATUS C-6 License Management Supplement License Management Supplement C.2 License Management Facility (LMF) Notes - DISABLE - ENABLE - ISSUE - MOVE - COPY - LIST o Caution: By default, all Alpha availability PAKs look disabled to a VAX system. Never use the DELETE /STATUS=DISABLED command from a VAX system on an LDB that contains Alpha PAKs. If you do, all Alpha PAKs will be deleted. o With the exception of the DELETE/STATUS=DISABLED command, if you inadvertently use one of the previously listed LICENSE commands on an Alpha PAK while using a VAX system, the PAK and the database will not be adversely affected. Repeat the command using LMF running on an Alpha system, and the PAK should return to a valid state. o If you do not repeat the command using LMF on an Alpha system, the system that you intended to disable will remain enabled (the system is not otherwise affected). Only the Alpha LMF can disable an Alpha PAK. However, if you attempt to use any of the previously listed commands on a PAK located in an LDB that is shared with a VAX system, the following serious problems may result: - Because Alpha PAKs look disabled to a VAX system, they are normally ignored at load time by VAX systems. However, if one of the previously listed commands is entered from a VAX system and the PAK information is not set to a valid state by an Alpha system, there is a chance the VAX system will attempt to load the Alpha PAK. Because the VAX system will be unable to load the PAK, the VAX LMF will report an error. - Even if a valid VAX PAK for the affected product is in the LDB, it too may not load. In this case, system users might be denied access to the product. License Management Supplement C-7 License Management Supplement C.2 License Management Facility (LMF) Notes If the PAK cannot be restored to a valid state because all Alpha systems are inaccessible for any reason, use your VAX system to disable the Alpha PAK. This prevents your VAX system from attempting to load the Alpha PAK. C-8 License Management Supplement D _________________________________________________________________ Preparing to Use OpenVMS Management Station During the OpenVMS installation or upgrade procedure, the OpenVMS Management Station software is automatically installed on your OpenVMS system disk when you accept all the default values. If you did not accept the default values and did not manually select the OpenVMS Management Station component, you must add those files to your OpenVMS system disk before you follow the instructions in this appendix. Use the OpenVMS operating system CD-ROM and the DCL command PRODUCT INSTALL TNT to add the OpenVMS Management Station files to your system. (See the OpenVMS System Management Utilities Reference Manual: M-Z for complete information about using the PRODUCT command.) After you have ensured that OpenVMS Management Station software is installed on your system, follow the procedures described in this appendix. D.1 Preparing Your OpenVMS System You must prepare your OpenVMS system to run the server software so that your system can properly interact with the PC running the client software. The procedures include the following: o Set up within a mixed-architecture cluster environment (if applicable). o Start the server on other nodes. o Update the printer and storage database. o Edit the system files. o Allow OpenVMS Management Station to control the printer and storage environment. Preparing to Use OpenVMS Management Station D-1 Preparing to Use OpenVMS Management Station D.1 Preparing Your OpenVMS System o Keep your printer environment up to date. o Check if running third-party TCP/IP stacks. o Recover from a failure. o Determine and report problems. D.1.1 Setting Up in a Mixed-Architecture Cluster Environment The OpenVMS Management Station server creates several configuration files: o TNT$UADB.DAT o TNT$ACS.DAT o TNT$JOURNAL.TNT$TRANSACTION_JOURNAL o TNT$MONITOR.DAT o TNT$MONITOR.TNT$MONITOR_JOURNAL o TNT$EMERGENCY_MOUNT.COM In a common-environment cluster with one common system disk, you use a common copy of each of these files located in the SYS$COMMON:[SYSEXE] directory on the common system disk, or on a disk that is mounted by all cluster nodes. No further action is required. However, to prepare a common user environment for an OpenVMS Cluster system that includes more than one common VAX system disk or more than one common Alpha system disk, you must coordinate the files on those disks. The following rules apply: o Disks holding common resources must be mounted early in the system startup procedure, such as in the SYLOGICALS.COM procedure. o You must ensure that the disks are mounted with each cluster reboot. Follow these steps to coordinate files: 1. Decide where to locate the files. In a cluster with multiple system disks, system management is much easier if the common system files are located on a single disk that is not a system disk. D-2 Preparing to Use OpenVMS Management Station Preparing to Use OpenVMS Management Station D.1 Preparing Your OpenVMS System 2. Copy TNT$UADB.DAT, TNT$ACS.DAT, TNT$MONITOR.DAT, TNT$MONITOR.TNT$MONITOR_JOURNAL, TNT$EMERGENCY_ MOUNT.COM, and TNT$JOURNAL.TNT$TRANSACTION_JOURNAL to a location other than the system disk. 3. Edit the file SYS$COMMON:[SYSMGR]SYLOGICALS.COM on each system disk and define logical names that specify the location of the cluster common files. Example If the files will be located on $1$DJA16, define logical names as follows: $ DEFINE/SYSTEM/EXEC TNT$ACS - _$ $1$DJA16:[VMS$COMMON.SYSEXE]TNT$ACS.DAT TNT$EMERGENCY_MOUNT.COM will be created in SYS$SYSTEM or in the directory pointed to by the TNT$ACS logical, if the logical exists. $ DEFINE/SYSTEM/EXEC TNT$UADB - _$ $1$DJA16:[VMS$COMMON.SYSEXE]TNT$UADB.DAT $ DEFINE/SYSTEM/EXEC TNT$JOURNAL - _$ $1$DJA16:[VMS$COMMON.SYSEXE] TNT$JOURNAL.TNT$TRANSACTION_JOURNAL $ DEFINE/SYSTEM/EXEC TNT$MONITOR - _$ $1$DJA16:[VMS$COMMON.SYSEXE]TNT$MONITOR.DAT $ DEFINE/SYSTEM/EXEC TNT$MONITORJOURNAL - _$ $1$DJA16:[VMS$COMMON.SYSEXE]TNT$MONITOR.TNT$MONITOR_JOURNAL 4. To ensure that the system disks are mounted correctly with each reboot, follow these steps: 1. Copy the SYS$EXAMPLES:CLU_MOUNT_DISK.COM file to the [VMS$COMMON.SYSMGR] directory, and edit it for your configuration. 2. Edit SYLOGICALS.COM and include commands to mount, with the appropriate volume label, the system disk containing the shared files. Preparing to Use OpenVMS Management Station D-3 Preparing to Use OpenVMS Management Station D.1 Preparing Your OpenVMS System Example If the system disk is $1$DJA16, include the following command: $ @SYS$SYSDEVICE:[VMS$COMMON.SYSMGR]CLU_MOUNT_DISK.COM - _$ $1$DJA16: volume-label D.1.2 Start the Server on Other Nodes If you plan to run OpenVMS Management Station on more than one node in an OpenVMS Cluster without a reboot, you need to start the software on those nodes. Use SYSMAN to start the server as follows: $ @SYS$STARTUP:TNT$STARTUP.COM or, you can log into each node that shares the SYS$COMMON: directory and enter the following command: $ @SYS$STARTUP:TNT$STARTUP.COM If you are performing an upgrade or a reinstallation and OpenVMS Management Station is already running on the node, add the RESTART parameter to the startup command, as follows: $ @SYS$STARTUP:TNT$STARTUP.COM RESTART D.1.3 Error Log Information OpenVMS Management Station writes error log information to the file TNT$SERVER_ERROR.LOG. This error log is created in the SYS$SPECIFIC:[SYSEXE] directory. If you start the OpenVMS Management Station server on multiple nodes in a cluster, which is recommended, there will be multiple server error logs. D.1.4 Update the Printer and Storage Database When you installed OpenVMS Management Station, the installation started the OpenVMS Management Station server on the installation node. If this installation was an upgrade, the server converts the existing OpenVMS Management Station database to the V3.0 format. If this was a new installation, the server creates an initial version of the database file TNT$ACS.DAT and invokes the update functions automatically. D-4 Preparing to Use OpenVMS Management Station Preparing to Use OpenVMS Management Station D.1 Preparing Your OpenVMS System To complete the database, start the OpenVMS Management Station server on each node in your cluster. The instances of the server communicate with each other to determine device, queue, and volume information, and the server must be running on each node for this communication to take place. D.1.5 Edit the System Files To start the OpenVMS Management Station server from your system startup files, insert one of the following commands into your system startup procedures (probably SYS$MANAGER:SYSTARTUP_VMS.COM) after both the Queue Manager and network are started, but immediately prior to the ENABLE AUTOSTART/QUEUES. ________________________ Note ________________________ Remove any other invocations of TNT$STARTUP you might have added in previous releases of the OpenVMS Management Station. OpenVMS Management Station cannot start until the network has started. If you start your network using a batch process, OpenVMS Management Station might start before the batch process completes and the network is started. ______________________________________________________ _________________________________________________________________ ParameterParameter Command______1________2________Description_______________________ @TNT$STARTUP blank N.A. Starts the server. Does not start printer queues or mount volumes. @TNT$STARTUP RESTART N.A. Shuts down a running server, then starts the server. Does not start printer queues or mount volumes. Preparing to Use OpenVMS Management Station D-5 Preparing to Use OpenVMS Management Station D.1 Preparing Your OpenVMS System _________________________________________________________________ ParameterParameter Command______1________2________Description_______________________ @TNT$STARTUP BOOT blank Starts the server. Starts any printer queues that are not yet started and are managed by OpenVMS Management Station. Does not mount volumes managed by OpenVMS Management Station. @TNT$STARTUP BOOT ALL Starts the server. Starts any printer queues that are not yet started and are managed by OpenVMS Management Station. Mounts any volumes that are not yet mounted and are managed by OpenVMS Management Station. @TNT$STARTUP BOOT PRINTERS Starts the server. Starts any printer queues that are not yet started and are managed by OpenVMS Management Station. Does not mount volumes managed by OpenVMS Management Station. @TNT$STARTUP BOOT STORAGE Starts the server. Mounts any volumes that are not yet mounted and are managed by OpenVMS Management Station. Does not start _______________________________any_printer_queues._______________ Note that the effect of TNT$STARTUP BOOT, with no second parameter, has not changed from earlier releases. This command starts any printer queues that are not yet started and are managed by OpenVMS Management Station, but does not mount any volumes. Add the following command line to the system shutdown file, SYS$MANAGER:SYSHUTDWN.COM: $ @SYS$STARTUP:TNT$SHUTDOWN.COM D-6 Preparing to Use OpenVMS Management Station Preparing to Use OpenVMS Management Station D.1 Preparing Your OpenVMS System D.1.6 Allow OpenVMS Management Station to Control the Printer and Storage Environment It is not necessary to remove your existing queue startup and volume mount DCL procedures immediately. The OpenVMS Management Station server will recognize that you started a queue or mounted a volume with your command procedures and will assume that you want it that way. As you become familiar with the server's management ability, you can remove or comment out the DCL commands and procedures that perform these tasks and allow OpenVMS Management Station to control your printer and storage environment. In addition, the OpenVMS Management Station server periodically (every 24 hours) generates a DCL command procedure that includes the commands to mount all of the volumes managed by OpenVMS Management Station. If you are familiar with DCL, you can look at this command procedure to see what actions OpenVMS Management Station performs for you. And, in the event of an unforeseen system problem or a corrupt server database (SYS$SYSTEM:TNT$ACS.DAT), you could use this command procedure to mount the volumes. The name of the generated file is TNT$EMERGENCY_MOUNT.COM. TNT$EMERGENCY_MOUNT.COM is created in SYS$SYSTEM or in the directory pointed to by the TNT$ACS logical, if that logical name exists. The OpenVMS Management Station server limits TNT$EMERGENCY_ MOUNT.COM to seven versions. D.1.7 Keep Your Printer Environment Up to Date The OpenVMS Management Station server installation creates a file named SYS$STARTUP:TNT$UTILITY.COM. This command procedure scans the OpenVMS system and updates the database of known printers, queues, and related devices. Preparing to Use OpenVMS Management Station D-7 Preparing to Use OpenVMS Management Station D.1 Preparing Your OpenVMS System D.1.7.1 When is the Database Updated? The database is updated: o As part of the OpenVMS Management Station installation. o When you specifically invoke TNT$UTILITY.COM. o At periodic intervals as a server background thread. Two logical names control how often this server thread runs: ________________________________________________________ Logical_Name__________Description_______________________ TNT$PRINTER_RECON_ How often the thread should run, INTERVAL in minutes, from when the server was last started on this node. If you do not define this logical, the default value is 1440 minutes (24 hours). TNT$PRINTER_RECON_ The minimum number of minutes INTERVAL_MIN that must elapse before the thread should run again, starting from when the database was last updated. If you do not define this logical, the default value is 60 ______________________minutes_(1_hour)._________________ You can think of these logicals as meaning "run the thread this often (TNT$PRINTER_RECON_INTERVAL), but make sure this much time has elapsed since the database was last updated (TNT$PRINTER_RECON_INTERVAL_MIN)." Because you can run TNT$UTILITY.COM yourself, and because the OpenVMS Management Station server also updates the database, the TNT$PRINTER_RECON_INTERVAL_MIN logical prevents the database from being updated more frequently than is actually needed. If you want to change the defaults for one of these logicals, define the logical on all nodes on which the OpenVMS Management Station server is running. D-8 Preparing to Use OpenVMS Management Station Preparing to Use OpenVMS Management Station D.1 Preparing Your OpenVMS System D.1.7.2 Do You Need to Run TNT$UTILITY.COM Manually? If you use OpenVMS Management Station to make all of the changes to your printer configuration, the configuration files are immediately modified to reflect the changes and you probably do not need to specifically run TNT$UTILITY.COM. However, if you or someone else uses DCL to make a change - for example, if you use the DELETE /QUEUE command to delete a queue - the configuration files will not be synchronized. In this case, the OpenVMS Management Station client will advise you to run TNT$UTILITY.COM to resynchronize the database. Run the following procedure on one node in the cluster to make the database match your system: $ @SYS$STARTUP:TNT$UTILITY.COM UPDATE PRINTERS For example, if you or someone else used DCL to delete a queue, you need to delete that queue from the database. TNT$UTILITY.COM assumes that your system is set up and running the way that you want it to, so you should fix any problems before you run TNT$UTILITY.COM. D.1.7.3 Are There Any Requirements for Running TNT$UTILITY.COM? You need the SYSNAM privilege to run TNT$UTILITY.COM. TNT$UTILITY.COM connects to the OpenVMS Management Station server on the current OpenVMS system to determine device and queue information. Therefore, the OpenVMS Management Station server must be running on the node where you run TNT$UTILITY.COM. The OpenVMS Management Station server then connects to the other OpenVMS Management Station servers in the OpenVMS Cluster to determine device and queue information. It is generally a good idea to keep the OpenVMS Management Station server running on the other nodes in an OpenVMS Cluster to keep the database up to the minute. However, if the OpenVMS Management Server is not able to connect to the OpenVMS Management Station server on a given node, it uses the known information about that OpenVMS node from the database. That is, in the absence of a valid connection to that OpenVMS node, the information in the database is assumed to be correct. Preparing to Use OpenVMS Management Station D-9 Preparing to Use OpenVMS Management Station D.1 Preparing Your OpenVMS System D.1.8 Keeping Your Storage Environment Up to Date The TNT$UTILITY.COM utility accepts parameters (UPDATE STORAGE) to update the storage database. However, the storage database is updated dynamically every time you use the OpenVMS Management Station client to perform a storage management operation. Therefore, you do not need to run TNT$UTILITY.COM to update the storage database. D.1.9 Enabling Disk Quotas Before installing OpenVMS Management Station, you might have disabled disk quotas on the SYSTEM disk. If so, you should reenable the quotas and then rebuild to update quota information by entering the following commands: $ RUN SYS$SYSTEM:DISKQUOTA DISKQUOTA> ENABLE DISKQUOTA> REBUILD DISKQUOTA> EXIT D.1.10 Caching Storage Configuration Data OpenVMS Management Station uses two logical names to determine how often to refresh cached (in-memory) storage configuration data. o TNT$PURGE_CYCLE_LATENCY-Determines how often to wait (in seconds) after purging stale device reports before purging again. This value affects how frequently the cluster-wide data (maintained by a "master server" is updated in memory. min = 180 default = 1800 (30 minutes) max = 18000 (5 hours) o TNT$LOCAL_SURVEY_LATENCY-Determines the delay (in seconds) from one node-specific device survey to the next. This value is independent of cluster-wide surveys requested by the "master server" when performing a purge. min = 6 default = 60 (1 minute) max = 600 (10 minutes) D-10 Preparing to Use OpenVMS Management Station Preparing to Use OpenVMS Management Station D.1 Preparing Your OpenVMS System For both logical names, smaller values result in the OpenVMS Management Station server consuming more CPU cycles in periodic purges or surveys. If you do not accept the defaults, you might find that larger OpenVMS Cluster systems behave better with values on the high end of the allowed range. If you do not define these logicals, the OpenVMS Management Station server uses the default values. If you do define these logical names, the values are used only if they are within the minimum to maximum range. D.1.11 Running Third-Party TCP/IP Stacks DIGITAL TCP/IP Services for OpenVMS Version 3.2 or higher is the only supported TCP/IP stack. Additional stacks have not been tested. However, TCP/IP stacks that are 100% compliant with the QIO interface for DIGITAL TCP/IP Services for OpenVMS should also work. (Contact your TCP/IP vendor for additional information and support issues.) For the best chance of success, check the following: o Make sure that the QIO service (for example, UCXQIO) is enabled. o For TCPware, also make sure that TCPware's UCX$IPC_SHR.EXE is an installed image. o Also for TCPware, make sure you are running a version of TCPware that correctly implements a DECC-compatible socket interface, such as Version 5.3-3. D.1.12 Determining and Reporting Problems If you encounter a problem while using OpenVMS Management Station, please report it to Compaq. Depending on the nature of the problem and the type of support you have, you can take one of the following actions: o If your software contract or warranty agreement entitles you to telephone support, call Compaq. o If the problem is related to OpenVMS Management Station documentation, use the Internet address printed in front of this book to send us your comments. Preparing to Use OpenVMS Management Station D-11 Preparing to Use OpenVMS Management Station D.1 Preparing Your OpenVMS System D.1.13 Removing the OpenVMS Management Station Server If you use the POLYCENTER Software Installation utility to remove OpenVMS Management Station from the OpenVMS system, the following files are not removed: o TNT$ACS.DAT o TNT$JOURNAL.TNT$TRANSACTION_JOURNAL o TNT$SERVER_ERROR.LOG o TNT$UADB.DAT o TNT$EMERGENCY_MOUNT.COM Do not delete these files unless you have already removed OpenVMS Management Station. D.2 Preparing Your PC During the OpenVMS installation or upgrade procedure, you selected the OpenVMS Management Station client software files to be installed on your OpenVMS system disk (or you added them later using the DCL command PRODUCT INSTALL TNT). After you have prepared your OpenVMS system to run the server software, you must next prepare your PC to run the client software. This section includes the following information: o Required memory and disk space o Required software o Installing the client software o Getting started using OpenVMS Management Station D.2.1 Required Memory and Disk Space Your PC requires 13 MB of free disk space to install the OpenVMS Management Station client software. D-12 Preparing to Use OpenVMS Management Station Preparing to Use OpenVMS Management Station D.2 Preparing Your PC D.2.2 Distribution Files There are two versions of the OpenVMS Management Station client kit: TNT030_I.EXE for Intel systems (Windows 95 and Windows NT), and TNT030_A.EXE for Alpha Windows NT systems. Both of these files are located in the SYS$COMMON:[TNT.CLIENT] directory. The Intel kit will not install under FX!32 running on Alpha processors; use the Alpha native kit in this case. D.2.3 Required Software Microsoft Windows NT Versions 4.0 (Service Pack 3 or higher) or Windows 95 or higher (Intel only) must be installed on each PC on which you want to install the OpenVMS Management Station client. The version of MMC included in this baselevel requires files provided by Microsoft Internet Explorer. Version 3.02 or later of Internet Explorer must be present on the system. D.2.4 Time Required for Installation The time required to install the OpenVMS Management Station client software is approximately 5 minutes. D.2.5 Copy the Client File to the PC The client files TNT030_I.EXE (Intel) and TNT030_A.EXE (Alpha) are located in the SYS$COMMON:[TNT.CLIENT] directory. Copy either client file to a temporary directory the PC using any of the following procedures: o Create a file share to the OpenVMS system and copy the file. o Use FTP on the PC to copy the file from the OpenVMS system. D.2.6 Installation Directory The installation procedure allows you to select the installation directory, and suggests \Program Files\OpenVMS Mgmt Station\ as the default. Preparing to Use OpenVMS Management Station D-13 Preparing to Use OpenVMS Management Station D.2 Preparing Your PC D.2.7 Installation Procedure Run TNT030_I.EXE (Intel) or TNT030_A.EXE (Alpha) from a temporary directory. These are self-extracting executable files that automate the OpenVMS Management Station installation. D.2.8 Recovering from Errors If an error occurs during installation, you will receive an error message describing the problem. This information can help you determine the cause of the problem. An error can occur during the installation if one or more of the following conditions exist: o The operating system version is incorrect. o Disk space and memory necessary for successful installation are inadequate. D.3 After Installing the Client Software on Your PC When you create an OpenVMS Cluster or OpenVMS Node object in an OpenVMS Management Domain, you select the transport you want to use for all connections to that system. You can choose DECnet Phase IV or TCP/IP. OpenVMS Management Station uses this transport for all communications between the PC and this system, or between any other OpenVMS system that is running the OpenVMS Management Station server and this system. ________________________ Note ________________________ The OpenVMS Management Station client supports only TCP/IP connections for primary servers. That is, the connection between the PC and the OpenVMS system uses only TCP/IP. Therefore, at least one OpenVMS system must be running TCP/IP. ______________________________________________________ You do need to make sure that your PC can connect to the primary-server systems, as described in the following sections. OpenVMS Management Station connects your PC to the primary-server system and then routes management operations to the target systems. D-14 Preparing to Use OpenVMS Management Station Preparing to Use OpenVMS Management Station D.3 After Installing the Client Software on Your PC D.3.1 Defining TCP/IP Nodes Your hosts file or name server must be able to resolve the IP name or address of all primary-server systems. If you can successfully ping the primary-server systems from your PC, then this condition is met. D.4 Uninstalling Version 2.1 of the OpenVMS Management Station Client Version 3.0 of the OpenVMS Management Station client is not dependent on Version 2.1 and does not share any files with this prior version. After installing the Version 3.0 client, you can uninstall the Version 2.1 client software. D.5 Uninstalling OpenVMS Management Station If you need to uninstall the OpenVMS Management Station client software, make sure you first exit OpenVMS Management Station. The uninstallation fails if OpenVMS Management Station is currently running. If you run the OpenVMS Management Station Help, the following files might be created: o VMSMGMT.FTS o VMSMGMT.GID o VMSPRINT.FTS o VMSPRINT.GID o VMSSCOPE.FTS o VMSSCOPE.GID o VMSSTORE.FTS o VMSSTORE.GID o VMSACNT.FTS o VMSACNT.GID The OpenVMS Management Station Uninstall program does not delete these files. To complete the uninstall: 1. Delete these files 2. Delete the OpenVMS Management Station directory Preparing to Use OpenVMS Management Station D-15 Preparing to Use OpenVMS Management Station D.5 Uninstalling OpenVMS Management Station Note that the OpenVMS Management Station Uninstall program does not uninstall the Microsoft Management Console (MMC) support files. D.6 Getting Started with OpenVMS Management Station All information about getting started, setting up, and using OpenVMS Management Station is contained in online help and the OpenVMS Management Station Overview and Release Notes. D-16 Preparing to Use OpenVMS Management Station E _________________________________________________________________ Removing the OpenVMS Alpha Operating System You can remove the OpenVMS Alpha operating system from your disk in the following ways: o If the disk contains a small number of user files, copy those user files elsewhere and then reinitialize the disk. o If the disk contains many user files, use the PRODUCT REMOVE command to remove an obsolete or extra copy of the OpenVMS Alpha operating system without removing any of the user files. Note that you must also delete or archive certain operating system files that the PRODUCT REMOVE command cannot delete. Follow these steps to remove OpenVMS Alpha operating system files: 1. If your system disk has multiple system-specific roots, boot the system and execute SYS$MANAGER:CLUSTER_ CONFIG.COM to remove all roots except the one from which you are booted. 2. Shut down and boot from the distribution CD-ROM or from a system disk other than the one from which OpenVMS Alpha is being removed. Then do one of the following: o If OpenVMS Alpha is not running from the distribution CD-ROM, log in to a privileged account. o If OpenVMS Alpha is running from the distribution CD-ROM, choose the option to execute DCL commands. 3. Enter the following DCL commands: $ DEFINE/NOLOG PCSI$SYSDEVICE target-disk $ DEFINE/NOLOG PCSI$SPECIFIC target-disk:[SYSx.] $ DEFINE/NOLOG PCSI$DESTINATION target-disk:[VMS$COMMON] $ PRODUCT REMOVE VMS /REMOTE Removing the OpenVMS Alpha Operating System E-1 Removing the OpenVMS Alpha Operating System where: o target-disk is the device name of the disk from which OpenVMS Alpha is being removed. o SYSx is the root number that you did not remove in step 1. 4. If the disk also contains layered products that were installed using the POLYCENTER Software Installation utility, Compaq recommends that you remove them as well. Remove any layered products before using the PRODUCT REMOVE VMS command. Use the following command to remove all the products at once. Select the layered products you want to remove from the menu. $ PRODUCT REMOVE * /REMOTE Use the following commands to remove individual products: $ PRODUCT SHOW PRODUCT/REMOTE $ PRODUCT REMOVE product-name /REMOTE 5. Because the PRODUCT REMOVE command does not delete certain files, review the target disk to determine if you want to delete, move, or archive the operating system files that still remain on the disk. Following are lists of the files that the PRODUCT REMOVE command does not delete: o In target-disk:[SYS*.SYSEXE], where * is 0 or the hexadecimal number of any additional OpenVMS Cluster roots on the target disk: ALPHAVMSSYS.PAR MODPARAMS.DAT PAGEFILE.SYS SWAPFILE.SYS o In target-disk:[VMS$COMMON.SYSEXE]: LMF$LICENSE.LDB PCSI$FILE_SYSTEM.PCSI$DATABASE PCSI$PROCESSOR.PCSI$DATABASE PCSI$ROOT.PCSI$DATABASE RIGHTSLIST.DAT E-2 Removing the OpenVMS Alpha Operating System Removing the OpenVMS Alpha Operating System SYSUAF.DAT As you examine the preceding lists of files, you may want to archive, rather than delete, the following files: ALPHAVMSSYS.PAR MODPARAMS.DAT LMF$LICENSE.LDB RIGHTSLIST.DAT SYSUAF.DAT Also, if you previously removed layered products, there may be additional files created by the layered products that you may want to delete, move, or archive. 6. Review the target disk for the directory structures [VMS$COMMON...] and [SYSx...] that remain after you remove the OpenVMS Alpha operating system. You may want to delete these directories. Note that the directories [SYSx]SYSCOMMON.DIR (in all [SYSx]) are aliases for the file [000000]VMS$COMMON.DIR. DO NOT DELETE THESE SYSCOMMON.DIR files. Instead, use SET FILE /REMOVE as follows: $SET FILE /REMOVE [SYS*]SYSCOMMON.DIR After you have executed this command and deleted, moved or archived all the files in [VMS$COMMON...] you can delete [000000]VMS$COMMON.DIR. You can then proceed to delete, move or archive the files in each [SYSx] directory. Removing the OpenVMS Alpha Operating System E-3 _________________________________________________________________ Glossary This glossary defines key terms in the context of an OpenVMS Alpha computing environment. boot, bootstrap The process of loading system software into a processor's main memory. This guide uses the term boot to refer to this process. boot server An Alpha computer that is part of a local area OpenVMS Cluster. The boot server is a combination of a MOP server and a disk server for the satellite system disk. See also satellite node. CI only OpenVMS Cluster A computer system consisting of a number of Alpha computers. It uses only the computer interconnect, or CI, to communicate with other Alpha computers in the cluster. These computers share a single file system. CI A type of I/O subsystem. It links computers to each other and to HSx devices (for example, an HSC or HSD). device name The name used to identify a device on the system. A device name indicates the device code, controller designation, and unit number. Glossary-1 disk server A computer that is part of a local area OpenVMS Cluster. This computer provides an access path to CI, DSSI, and locally connected disks for other computers that do not have a direct connection. HSx device A self-contained, intelligent, mass storage subsystem (for example, an HSC or HSD) that lets computers in an OpenVMS Cluster environment share disks. HSx drive Any disk or tape drive connected to an HSx device (for example, an HSC or HSD). A system disk on an HSx drive can be shared by several computers in an OpenVMS Cluster environment. InfoServer A general-purpose disk storage server that allows you to use the operating system CD-ROM to install the operating system on remote client systems connected to the same local area network (LAN). local area OpenVMS Cluster A configuration consisting of one or more computers that act as a MOP server and disk server, and a number of low-end computers that act as satellite nodes. The local area network (LAN) connects all of the computers. These computers share a single file system. local drive A drive, such as an RRD42 CD-ROM drive, that is connected directly to an Alpha computer. If you have a standalone Alpha computer, it is likely that all drives connected to the system are local drives. media Any packaging agent capable of storing computer software (for example, CD-ROMs, magnetic tapes, floppy diskettes, disk packs, and tape cartridges). Glossary-2 mixed interconnect OpenVMS Cluster A computer system consisting of a number of computers. It uses CI, Ethernet, and DSSI adapters to communicate with other computers in the cluster. MOP server A computer system running DECnet software that downline loads OpenVMS Cluster satellites using the DECnet maintenance operations protocol. OpenVMS Cluster environment A computer system consisting of a number of Alpha and VAX computers. There are four types of OpenVMS Cluster environments: CI only, DSSI only, local area, and mixed- interconnect. satellite node A computer that is part of a local area OpenVMS Cluster. A satellite node is downline loaded from a MOP server and then boots remotely from the system disk served by a disk server in the local area OpenVMS Cluster. See also boot server, disk server, MOP server. scratch disk A blank disk or a disk with files you no longer need. source drive The drive that holds the distribution kit during an upgrade or installation, or the drive from which you restore files to a target disk. standalone system A computer system with only one Alpha computer. system disk The disk that contains or will contain the OpenVMS Alpha operating system. target drive The drive that holds the system disk during an upgrade or installation, or the drive you designate when backing up the system disk. Glossary-3 UETP (User Environment Test Package) A software package that tests all the standard peripheral devices on your system, various commands and operating system functions, the system's multiuser capability, DECnet software, and the OpenVMS Cluster environment. Glossary-4 _________________________________________________________________ Index A Alpha computers (cont'd) _______________________________ booting with PMAZC Accounts TURBOchannel adapter, creating after installation, A-11 4-2 booting with XDELTA, A-10 setting up after an canceling boot device, A-23 installation, 4-4 halting, A-26 Adding files performing conversational after installation, 4-9 boot, A-7 after upgrade, 8-9 setting boot device, A-22 AGEN$PARAMS.REPORT, 4-18 setting boot parameters, Allocation class A-23 See also ALLOCLASS parameter setting for automatic booting determining, 2-3 , A-20 ALLOCLASS parameter, 2-3 showing boot device, A-23 supplying during OpenVMS shutting down, A-27 Cluster installation, 3-37 troubleshooting procedures, Alpha computers A-30 booting failure, A-29 ANALYZE/CRASH command, A-29 booting from a different ANALYZE/DISK_STRUCTURE utility directory, A-11 error message, 5-6 booting in an emergency, using before an upgrade, 5-6 A-14 APB.EXE booting with minimum startup, and Writeboot utility, A-25 A-9 Architectures booting with PMAD Alpha and VAX, 2-1, 6-1 TURBOchannel adapter, AUTOGEN, 4-18 A-14 running after an installation booting with PMAZB , 4-17 TURBOchannel adapter, running after an upgrade, A-11 8-18 running at end of installation, 3-38 Index-1 Booting problems B______________________________ fixing by booting with Backing up the system disk, default parameter values, 1-6, 4-16, 5-5, 8-17, A-2, A-15 A-6, B-1 Bugcheck, A-30 in a shadow set, B-8 without booting the CD-ROM, C______________________________ B-8 Checklist BACKUP command, B-2 postinstallation, 4-19 Boot block postupgrade, 8-18 writing, A-25 preupgrade, 5-8 Boot command Cluster group number qualifiers for XDELTA, A-10 rules for creating, 2-5 Booting Cluster password automatic, A-20 rules for creating, 2-5 canceling boot device, A-23 Cluster upgrades conversational, A-7 See Concurrent upgrades; failure, A-29 Rolling upgrades; Upgrade from a different directory, procedure A-11 CLUSTER_SIZE parameter, B-5 from the InfoServer, 3-4, Command procedures 7-2, A-3 checking after upgrade, 8-6 in an emergency, A-14 Common files with default system coordinating for multiple parameters, A-15 boot servers, D-2 without startup and login coordinating for multiple procedures, A-16 system disks, D-2 without the User CONTINUE command, A-8 Authorization File, Crash commands, A-28 A-18 Creating a system disk, 3-8 setting boot device, A-22 Ctrl/T, A-31 setting boot parameters, Customizing the system, 4-3 A-23 showing boot device, A-23 D______________________________ with alternate TURBOchannel DEC 3000 Alpha computers adapter, A-14 booting over the network, with minimum startup, A-9 A-13 with PMAZB TURBOchannel, booting with alternate A-11 TURBOchannel adapter, with PMAZC TURBOchannel, A-11 A-14 with XDELTA, A-10 booting with PMAZB TURBOchannel adapter, A-11 Index-2 DEC 3000 Alpha computers Disk space (cont'd) (cont'd) amount needed to decompress booting with PMAZC libraries, 8-6 TURBOchannel adapter, amount needed to decompress A-11 system libraries, 4-6 DECevent Dump file installing, 4-14, 8-15 checking size, 8-4 DECnet node address, 2-3 modifying size, 8-4 providing during installation , 3-36 E______________________________ DECnet node name, 2-3 Editing startup files, 4-3 possible values, 3-36 Emergency system startup providing during installation with default system , 3-36 parameters, A-15 DECnet Phase IV for OpenVMS without startup and login Alpha procedures, A-16 configuring after an without the UAF, A-18 installation, 4-4 Errors ignoring during startup, 4-5 cluster hang during registering license after preupgrade shutdown, 6-8 installation, 4-2 running ANALYZE/DISK_ running with DECwindows, 4-5 STRUCTURE, 5-6 upgrade, 7-21 EXPECTED_VOTES DECnet-Plus for OpenVMS Alpha parameter, 8-4 configuring after an installation, 4-4 F______________________________ removing, 4-4 Factory installed software upgrade, 7-21 Decompressing system libraries (FIS), ix , 4-6, 8-6 FIELD account DECW$IGNORE_DECNET logical creating after installation, name, 4-5 4-2 Default system parameters Files booting with, A-15 adding DIGITAL OpenVMS Debugger after installation, 4-9 installing clients on a PC, after upgrade, 8-9 4-14, 8-15 removing DIGITAL TCP/IP Services for after installation, 4-9 OpenVMS after upgrade, 8-9 configuring after an installation, 4-6 Disk space amount needed for upgrade, 5-7 Index-3 H______________________________ L______________________________ Halting the system, A-26 Layered products Hardware effect of upgrade on, 5-3, supported, D-12 8-13 Hardware problem installing after OpenVMS diagnosing, A-29 Alpha installation, 4-12 HSx device installing during OpenVMS definition, 1-1 Alpha installation, 3-30 specifying, 3-35 installing during OpenVMS Alpha upgrade, 7-23 I______________________________ LIBDECOMP.COM (procedure to InfoServer decompress system libraries) booting, 3-4, 7-2, A-3 , 4-7, 8-7 losing connection, 3-6, 7-4 running after an upgrade, INITIALIZE command, A-21 8-6 Installation Libraries See also Postinstallation decompressing after an tasks, Preinstallation installation, 4-6 tasks LICENSE (License Management booting system disk after utility) transferring required save example of registration, C-1 set, 3-35 license registration information needed for procedure, C-1 OpenVMS Cluster, 2-1 using during installation, of DIGITAL OpenVMS Debugger 3-24 clients, 4-14, 8-15 License Management Facility of layered products, 3-30, (LMF), C-5 4-12, 7-23 restrictions, C-6, C-7 rebooting system, 3-40 Licenses recording, 1-2 See also Product registering licenses, 3-23 Authorization Key (PAK) running AUTOGEN, 3-38 registering after an upgrade, setting passwords, 3-11 8-3 specifying OpenVMS Cluster registering after configuration, 3-36 installation, 4-2 stages of, 3-1 registering during using the POLYCENTER Software installation, 3-23 Installation utility, 1-6 License Unit Requirement Table Installation procedure (LURT), C-1 time zones, 3-19 Log for installation, 1-2 Index-4 Logging in OpenVMS Alpha (cont'd) when errors in login removing operating system procedures prevent, A-16 files, E-1 when errors in startup save sets procedures prevent, A-16 transferring to system when forgotten passwords disk, 3-8 prevent, A-18 OpenVMS Cluster Logical names building, 4-3 UAFALTERNATE, A-18 information required for Login command procedures OpenVMS Alpha installation booting without, A-16 , 2-1 when errors prevent you from label for system disk, B-2 logging in, A-16 OpenVMS Cluster installation, 3-36 M______________________________ choosing quorum disk, 3-38 Migration support, 2-1, 6-1 configuring the cluster, Minimum startup, A-10 3-36 Mixed-architecture OpenVMS prompts during, 3-36 Cluster systems, 2-1, 6-1, suggested answers to 6-5 questions, 3-36 Mixed-version cluster, 6-3 supplying ALLOCLASS parameter Mixed-version OpenVMS Cluster , 3-37 systems, 2-1, 6-1, 6-2, 6-6 OpenVMS Cluster quorum MODPARAMS.DAT (parameter file) maintaining during rolling , 4-18, 8-18 upgrades, 6-7 modifying for cluster, 8-4 OpenVMS Cluster upgrades modifying for single system, See Concurrent upgrades; 8-4 Rolling upgrades; Upgrade Monitoring Performance History procedure installing, 4-14, 8-15 OpenVMS Management Station preparing system, 4-11, 8-12 N______________________________ Output NETCONFIG.COM procedure saving from installation, running after an installation 1-2 , 4-5 P______________________________ O______________________________ Page file OPCCRASH.EXE, A-28 checking size, 8-4 OpenVMS Alpha modifying size, 8-4 license Password registering during forgotten, 3-42, A-18 installation, 3-23 minimum length, 3-11 setting during installation, 3-11 Index-5 PMAZB TURBOchannel adapter Postupgrade tasks (cont'd) booting system, A-11 checking system file sizes, PMAZC TURBOchannel adapter 8-4 booting system, A-11 decompressing system POLYCENTER Software libraries, 8-6 Installation utility examining command procedure installing the operating templates, 8-6 system, 1-6 modifying size of dump file, upgrading the operating 8-4 system, 1-6 modifying size of page file, Postinstallation tasks, 4-1 8-4 adding and removing files, modifying size of swap file, 4-9 8-4 adjusting system parameters, preparing to use OpenVMS 4-4 Management Station, 8-12 backing up the system disk, registering new licenses, 4-3, 4-16 8-3 configuring networking running AUTOGEN, 8-18 software, 4-4 running UETP, 8-6 customizing the system, 4-3 Preinstallation tasks decompressing system collecting information you libraries, 4-6 will need, 3-1 editing startup procedures, preparing for an OpenVMS 4-4 Cluster environment, 2-1 installing DIGITAL OpenVMS software and hardware Debugger clients, 4-14, components, 1-2 8-15 Preupgrade tasks installing layered products, analyzing and repairing 4-12 system disk, 5-6 preparing to use OpenVMS backing up system disk, 5-5 Management Station, 4-11 preparing system disk, 5-6 registering licenses, 4-2 shutting down system, 5-8 setting up user accounts, Printer 4-4 recording installation on, testing the system with the 1-2 User Environment Test Problems Package, 4-6 booting tuning the system with fixing by booting with AUTOGEN, 4-17 default parameter Postupgrade tasks values, A-15 adding and removing files, forgotten password 8-9 fixing by booting without backing up system disk, 8-17 the UAF, A-18 changing MODPARAMS.DAT, 8-4 logging in, A-16, A-18 Index-6 Product Authorization Key Restrictions (cont'd) (PAK) License Management Facility registering after an (LMF), C-6, C-7 installation, 4-2 Rolling upgrades, 6-4 to 6-8 registering after an upgrade, maintaining cluster quorum, 8-3 6-7 registering during an required operating system installation, 3-23 version, 6-5 PRODUCT REMOVE command restrictions, 6-5 files not removed with, E-2 removing operating system S______________________________ files, E-1 SDA (System Dump Analyzer), Q A-29 _______________________________ SET AUTO_ACTION command, A-22 Queue database SET BOOTDEF_DEV command, A-22 creating, 4-4 SET BOOT_OSFLAGS command, A-23 Queue manager Setting passwords during an starting, 4-4 installation, 3-11 Quorum Shadow sets See also OpenVMS Cluster system disk quorum upgrading, 5-3 maintaining during rolling SHOW BOOTDEF_DEV command, upgrades, 6-7 A-22, A-23 Quorum disk SHOW CRASH command, A-29 choosing during OpenVMS Shutdown Cluster installation, after installation, 3-40 3-38 before an upgrade, 5-8, 6-4, 6-7 R______________________________ procedures, A-27 Reboot SHUTDOWN.COM, A-27, A-28 after installation, 3-40 Site-specific command Recording an installation, 1-2 procedures Removing files restored during upgrade, 8-6 after installation, 4-9 Source drive, 1-2, B-4 after upgrade, 8-9 Spiralog Restoring files on the system restrictions, 5-2 disk, 1-6, A-2, A-6 Startup command procedure Restoring the system disk, B-6 booting without, A-16 without booting the CD-ROM, when errors prevent you from B-8 logging in, A-16 Restrictions Startup files for OpenVMS Alpha upgrade, editing after an installation 5-2 , 4-3 Index-7 Swap file System disk (cont'd) checking size, 8-4 booting after transferring modifying size, 8-4 required save set, 3-35 SWAPFILES.COM procedure checking amount of free space executing to change system on, 4-6 file sizes, 8-5 creating, 3-8 SYCONFIG.COM procedure free space needed for upgrade editing after an installation , 5-7 , 4-4 free space needed to SYLOGICALS.COM procedure decompress libraries, editing after an installation 4-6 , 4-4 preparing for an OpenVMS SYLOGIN.COM procedure Alpha upgrade, 5-6 editing after an installation removing files , 4-4 after installation, 4-9 SYSBOOT.EXE, A-7 after upgrade, 8-9 commands, A-8 unique volume label SYSGEN requirement, B-2 commands for conversational upgrading, 5-3 boot, A-8 System Dump Analyzer SYSTARTUP_VMS.COM procedure See SDA editing after an installation System Generation utility , 4-4 (SYSGEN) editing to control DECnet ALLOCLASS parameter, 2-3 Phase IV for OpenVMS Alpha commands for conversational , 4-5 boot, A-8 System System hang, A-30 customizing, 4-3 System parameters shutting down before upgrade, booting with default, A-15 5-8 UAFALTERNATE, A-19 SYSTEM account when incorrect values prevent forgotten password, 3-42 the system from booting, setting password, 3-11 A-15 System disk System startup adding files in an emergency after installation, 4-9 with default system after upgrade, 8-9 analyzing and repairing, 5-6 parameters, A-15 backing up, 8-17 without startup and login backing up after an procedures, A-16 installation, 4-16 without the UAF, A-18 backing up before an upgrade, SYSTEST account 5-5 creating after installation, booting after installation, 4-2 3-40 Index-8 SYSUAFALT.DAT file, A-18 Upgrade (cont'd) DECnet-Plus for OpenVMS Alpha T______________________________ , 7-21 Tailoring files disk space requirement, 5-7 See Adding files, Removing effect on layered products, files 5-3 Target disk requirements, 5-8 using backup copy for, 5-5 shadowed disks, 5-3 Target drive, B-4 Upgrade procedure Time zones effect on command procedures, updating during an 8-6 installation, 3-19 effect on MODPARAMS.DAT, 8-4 updating during an upgrade, required operating system 7-16 version, 5-2, 6-5 Transferring save sets to rolling upgrades system disk, 3-8 adding a new CPU, 6-3 TURBOchannel time zones, 7-16 booting with alternate using the POLYCENTER Software adapter, A-14 Installation utility, 1-6 booting with PMAZB adapter, User Authorization File A-11 See UAF booting with PMAZC adapter, User Environment Test Package A-11 See UETP U______________________________ V______________________________ UAF (User Authorization File) Volume label booting with alternate, A-18 definition, 1-3 returning to the default, requirement for OpenVMS A-19 Clusters, B-2 UAFALTERNATE logical name, Volume shadowing A-18 backing up the system disk, UAFALTERNATE system parameter, B-8 A-19 VOTES parameter UETP (User Environment Test checking for rolling upgrades Package), 4-6, 8-6 , 6-6 Upgrade See also Postupgrade tasks; W______________________________ Preupgrade tasks; Upgrade Warranted support, 2-1, 6-1 procedure Writeboot utility, A-25 cautions and restrictions, Writing a new boot block, A-25 5-2 DECnet Phase IV for OpenVMS Alpha, 7-21 Index-9