____________________________________________________ OpenVMS Alpha Version 7.0 Upgrade and Installation Manual Order Number: AA-QSE8A-TE December 1995 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 manual supersedes the OpenVMS Alpha Version 6.2 Upgrade and Installation Manual. Software Version: OpenVMS Alpha Version 7.0 Digital Equipment Corporation Maynard, Massachusetts ________________________________________________________________ December 1995 Digital Equipment 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 Digital or an authorized sublicensor. Digital conducts its business in a manner that conserves the environment and protects the safety and health of its employees, customers, and the community. © Digital Equipment Corporation 1995. All rights reserved. The following are trademarks of Digital Equipment Corporation: AlphaServer, AlphaStation, Bookreader, CI, DEC, DECdtm, DECnet, DECwindows, Digital, HSC, InfoServer, LAT, OpenVMS, PATHWORKS, POLYCENTER, RRD42, RZ, TURBOchannel, UETP, VAX, VAX DOCUMENT, VMS, VMScluster, XUI, and the DIGITAL logo. The following are third-party trademarks: Microsoft, MS, MS-DOS, and Windows are registered trademarks of Microsoft Corporation. Motif is a registered trademark of the Open Software Foundation, Inc. All other trademarks and registered trademarks are the property of their respective holders. ZK6458 This document is available on CD-ROM. This document was prepared using VAX DOCUMENT Version 2.1. _________________________________________________________________ Contents Preface................................................... xv 1 Getting Started Overview...................................... 1-2 Introduction.............................. 1-2 Key Terms................................. 1-2 Examining Software and Hardware Components.... 1-4 Introduction.............................. 1-4 Hardware Components....................... 1-4 Software Components....................... 1-4 Operating System CD-ROM................... 1-5 Required PALcode.......................... 1-5 Device Naming Conventions................. 1-6 Using the Operating System CD-ROM............. 1-8 Using the Menu............................ 1-8 Sample Menu Display....................... 1-9 How the Install or Upgrade Option Works... 1-10 How the Layered Products Options Work..... 1-12 How the DCL Option Works.................. 1-13 How the Shutdown Option Works............. 1-13 What to Do Next........................... 1-13 2 Preparing to Install in a VMScluster Environment Overview...................................... 2-2 Where to Find More Information............ 2-2 VMScluster Information You Will Need...... 2-3 What to Do Next........................... 2-6 iii 3 Installing the OpenVMS Alpha Operating System Overview...................................... 3-2 Introduction.............................. 3-2 Checking PALcode.......................... 3-2 Preparing to Respond to Prompts During the Installation.................................. 3-3 Introduction.............................. 3-3 Summary of Prompts........................ 3-3 Installing from CD-ROM or from a Running System........................................ 3-6 Introduction.............................. 3-6 How to Begin.............................. 3-6 Booting the Operating System CD-ROM........... 3-7 Introduction.............................. 3-7 Booting from the Local Drive.............. 3-7 Booting from the InfoServer............... 3-7 Creating the System Disk...................... 3-11 Installing from the CD-ROM................ 3-11 Installing from a Running System.......... 3-12 Choosing INITIALIZE or PRESERVE........... 3-12 Specifying the Target Disk................ 3-13 Specifying the Volume Label............... 3-14 Setting the SYSTEM Account Password....... 3-14 Becoming a Cluster Member................. 3-15 Setting System Parameters................. 3-16 Updating Time Zone Information............ 3-17 Registering Licenses.......................... 3-19 Introduction.............................. 3-19 Types of OpenVMS Alpha Licenses........... 3-19 For More Information...................... 3-21 How to Register Licenses.................. 3-21 Using the Licensing Procedure............. 3-23 Completing the Installation................... 3-24 Choosing Descriptive Help Text............ 3-24 Selecting Components...................... 3-24 List of Components........................ 3-25 Completing the Procedure.................. 3-27 What to Do Next........................... 3-28 Installing Layered Products................... 3-29 Introduction.............................. 3-29 How to Install............................ 3-29 Booting the New System Disk................... 3-33 Introduction.............................. 3-33 iv Preparing to Boot the New System Disk..... 3-33 How to Boot the New System Disk........... 3-34 Joining a VMScluster.......................... 3-35 Introduction.............................. 3-35 VMScluster Prompts........................ 3-35 What to Do Next........................... 3-37 Running AUTOGEN............................... 3-38 How AUTOGEN Works......................... 3-38 AUTOGEN Messages.......................... 3-38 Rebooting the System.......................... 3-40 Introduction.............................. 3-40 Rebooting the System Manually............. 3-40 Logging in to the SYSTEM Account.............. 3-41 Introduction.............................. 3-41 Logging in to a Character Cell Terminal... 3-41 Logging in to a Workstation............... 3-42 What to Do Next........................... 3-42 4 After Installing the OpenVMS Alpha Operating System Overview...................................... 4-2 Registering Your Licenses..................... 4-3 Introduction.............................. 4-3 For More Information...................... 4-3 Creating Accounts............................. 4-4 Introduction.............................. 4-4 For More Information...................... 4-4 Backing Up Your System Disk................... 4-5 Introduction.............................. 4-5 How to Back Up the System Disk............ 4-5 When to Back Up the System Disk........... 4-5 For More Information...................... 4-5 Customizing the System........................ 4-6 Introduction.............................. 4-6 For More Information...................... 4-6 Configuring and Starting DECnet for OpenVMS Alpha Software................................ 4-7 Testing the System with UETP.................. 4-9 Introduction.............................. 4-9 For More Information...................... 4-9 Decompressing the System Libraries............ 4-10 Introduction.............................. 4-10 Determining Disk Space.................... 4-10 v Methods of Using LIBDECOMP.COM............ 4-10 Responding to LIBDECOMP.COM Prompts....... 4-11 Using LIBDECOMP.COM Interactively......... 4-11 Using LIBDECOMP.COM in Batch.............. 4-13 Adding and Removing Files..................... 4-14 Introduction.............................. 4-14 How to Add and Remove Files............... 4-14 For More Information...................... 4-14 Preparing to Use OpenVMS Management Station... 4-15 Introduction.............................. 4-15 For More Information...................... 4-15 Removing Files............................ 4-15 Installing Layered Products................... 4-16 Procedure................................. 4-16 Alternate Procedure....................... 4-17 DECwindows Support........................ 4-17 Monitoring Performance History............ 4-18 Additional Notes.......................... 4-18 Backing Up the Customized System Disk......... 4-19 Introduction.............................. 4-19 How to Back Up the Customized System Disk...................................... 4-19 For More Information...................... 4-19 Configuring a Multihead System................ 4-20 Definition................................ 4-20 Introduction.............................. 4-20 How to Set Up the System.................. 4-20 For More Information...................... 4-21 Running AUTOGEN............................... 4-22 Introduction.............................. 4-22 When to Run AUTOGEN....................... 4-22 Modifying Parameters...................... 4-22 For More Information...................... 4-23 Postinstallation Checklist.................... 4-24 5 Before Upgrading the OpenVMS Alpha Operating System Overview...................................... 5-2 For More Information...................... 5-2 Cautions and Restrictions..................... 5-3 Introduction.............................. 5-3 Required Operating System Version......... 5-3 Update License............................ 5-3 vi Files and Directories..................... 5-3 Licenses and Layered Products............. 5-4 Preparing to Upgrade in a Volume Shadowing Environment................................... 5-5 Introduction.............................. 5-5 Creating a Nonshadowed Target Disk........ 5-5 Changing the Label........................ 5-6 Setting the Boot Device................... 5-6 What to Do Next........................... 5-6 Backing Up the System Disk.................... 5-7 Introduction.............................. 5-7 How to Back Up the System Disk............ 5-7 For More Information...................... 5-7 Preparing the System Disk..................... 5-8 Introduction.............................. 5-8 Examining the System Disk................. 5-8 Checking the Size of the System Disk...... 5-8 Verifying System Parameters............... 5-9 What to Do Next........................... 5-9 Preupgrade Checklist.......................... 5-11 6 Preparing to Upgrade in a VMScluster Environment Overview...................................... 6-2 Types of Upgrades......................... 6-2 Adding a New System to the Cluster........ 6-2 For More Information...................... 6-3 Concurrent Upgrade............................ 6-4 Introduction.............................. 6-4 How a Concurrent Upgrade Works............ 6-4 Notes and Restrictions.................... 6-4 Preparing for a Concurrent Upgrade........ 6-4 Rolling Upgrade............................... 6-6 Introduction.............................. 6-6 How a Rolling Upgrade Works............... 6-6 Notes and Restrictions.................... 6-6 Preparing for a Rolling Upgrade........... 6-7 vii 7 Upgrading the OpenVMS Alpha Operating System Overview...................................... 7-2 Introduction.............................. 7-2 Upgrading from CD-ROM or from a Running System........................................ 7-3 Introduction.............................. 7-3 How to Begin.............................. 7-3 Booting the Operating System CD-ROM........... 7-4 Introduction.............................. 7-4 Booting from the Local Drive.............. 7-4 Booting from the InfoServer............... 7-4 Performing the Upgrade........................ 7-8 Upgrading from the CD-ROM................. 7-8 Upgrading from a Running System........... 7-9 Choosing INITIALIZE or PRESERVE........... 7-9 Specifying the Target Disk................ 7-10 Specifying the Volume Label............... 7-10 Updating Time Zone Information............ 7-10 Choosing Descriptive Help Text............ 7-12 Selecting Components...................... 7-12 Completing the Upgrade.................... 7-14 What to Do Next........................... 7-17 Installing Layered Products................... 7-18 Introduction.............................. 7-18 How to Install............................ 7-18 What to Do After the Shutdown................. 7-22 Standalone Upgrade........................ 7-22 Concurrent VMScluster Upgrade............. 7-22 Rolling VMScluster Upgrade................ 7-23 8 After Upgrading the OpenVMS Alpha Operating System Overview...................................... 8-2 Re-Forming the Shadow Set..................... 8-3 Introduction.............................. 8-3 How to Add Shadow Set Members............. 8-3 Example................................... 8-4 Registering New Licenses...................... 8-5 Introduction.............................. 8-5 For More Information...................... 8-5 Examining the AUTOGEN Report File............. 8-6 Introduction.............................. 8-6 Interpreting the Report File.............. 8-6 viii Modifying the System Parameters File.......... 8-7 Introduction.............................. 8-7 System File Sizes......................... 8-7 VMScluster Parameters..................... 8-8 Examining Your Command Procedures............. 8-9 Introduction.............................. 8-9 Site-Specific Files....................... 8-9 Decompressing the System Libraries............ 8-10 Introduction.............................. 8-10 Determining Disk Space.................... 8-10 Methods of Using LIBDECOMP.COM............ 8-10 Responding to LIBDECOMP.COM Prompts....... 8-10 Using LIBDECOMP.COM Interactively......... 8-11 Using LIBDECOMP.COM in Batch.............. 8-12 Testing the System with UETP.................. 8-13 Introduction.............................. 8-13 For More Information...................... 8-13 Adding and Removing Files..................... 8-14 Introduction.............................. 8-14 How to Add and Remove Files............... 8-14 For More Information...................... 8-14 Preparing to Use OpenVMS Management Station... 8-15 Introduction.............................. 8-15 For More Information...................... 8-15 Removing Files............................ 8-15 Installing Layered Products................... 8-16 Introduction.............................. 8-16 Procedure................................. 8-16 Alternate Procedure....................... 8-17 DECwindows Support........................ 8-17 Monitoring Performance History............ 8-18 Additional Notes.......................... 8-18 Backing Up the Customized System Disk......... 8-19 Introduction.............................. 8-19 How to Back Up the Customized System Disk...................................... 8-19 For More Information...................... 8-19 Rebooting Cluster Members..................... 8-20 Introduction.............................. 8-20 For More Information...................... 8-20 Running AUTOGEN............................... 8-21 Introduction.............................. 8-21 Running After the Upgrade................. 8-21 ix Running Weekly............................ 8-21 For More Information...................... 8-21 Postupgrade Checklist......................... 8-22 A Halt, Boot, and Shutdown Procedures Overview...................................... A-2 Booting Operations.................................. A-3 Booting the Operating System CD-ROM........... A-4 Introduction.............................. A-4 Booting from the Local Drive.............. A-4 Booting from the InfoServer............... A-5 Booting Manually from the System Disk......... A-8 Introduction.............................. A-8 How to Boot Manually...................... A-8 Performing a Conversational Boot.............. A-10 Introduction.............................. A-10 How to Perform a Conversational Boot...... A-10 For More Information...................... A-12 Booting with Minimum Startup.................. A-13 Introduction.............................. A-13 How to Boot with Minimum Startup.......... A-13 Booting with the XDelta Utility (XDELTA)...... A-14 Introduction.............................. A-14 Boot Command Qualifier Values............. A-14 How to Boot with XDELTA................... A-14 For More Information...................... A-15 Booting from a Different Directory............ A-16 Introduction.............................. A-16 How to Boot from a Different Directory.... A-16 Booting with a PMAZB or PMAZC TURBOchannel Adapter....................................... A-17 Introduction.............................. A-17 Displaying Devices........................ A-17 How to Boot............................... A-18 How Adapters Are Identified............... A-18 Example................................... A-18 Booting Over the Network with an Alternate TURBOchannel Adapter.......................... A-19 Introduction.............................. A-19 How to Boot............................... A-19 Booting in an Emergency....................... A-21 Introduction.............................. A-21 x Booting with Default System Parameters.... A-21 Booting without Startup and Login Procedures................................ A-23 Booting without the User Authorization File...................................... A-24 Set, Show, and Writeboot Operations................. A-29 Setting the System for Automatic Booting...... A-30 Introduction.............................. A-30 When Systems Can Boot Automatically....... A-30 How to Set the System..................... A-30 Setting and Showing Boot Devices.............. A-32 Introduction.............................. A-32 Setting the Boot Device................... A-32 Showing the Boot Device................... A-32 Cancelling the Boot Device................ A-33 Setting Boot Parameters....................... A-34 Introduction.............................. A-34 List of Valid Parameters.................. A-34 How to Enter the SET BOOT_OSFLAGS Command................................... A-35 Displaying Parameters..................... A-36 Using the Writeboot Utility................... A-37 Introduction.............................. A-37 Invoking WRITEBOOT........................ A-37 Halt and Shutdown Operations........................ A-39 Halting the System............................ A-40 Introduction.............................. A-40 How to Halt Your Alpha Computer........... A-40 Shutting Down the System...................... A-42 Introduction.............................. A-42 Orderly Shutdown.......................... A-42 Emergency Shutdown with OPCCRASH.EXE...... A-42 Emergency Shutdown with Crash Commands.... A-43 Troubleshooting Procedures.......................... A-45 If the System Does Not Boot................... A-46 Introduction.............................. A-46 For Hardware Problems..................... A-46 For Software Problems..................... A-46 Detecting and Responding to System Problems... A-47 Introduction.............................. A-47 Detecting System Problems................. A-47 How to Respond............................ A-48 xi B Backing Up and Restoring the System Disk Overview...................................... B-2 Reasons for Backing Up the System Disk.... B-2 Suggested Procedures...................... B-3 VMScluster Caution........................ B-3 Backing Up the System Disk.................... B-5 Getting Started........................... B-5 Mounting Devices.......................... B-6 Entering the BACKUP Command............... B-6 Examples.................................. B-6 Changing the CLUSTER_SIZE Parameter....... B-7 What to Do Next........................... B-7 Restoring the System Disk..................... B-8 Getting Started........................... B-8 Mounting Devices.......................... B-9 Entering the BACKUP Command............... B-9 Examples.................................. B-9 What to Do next........................... B-10 Alternate Backup and Restore Procedure........ B-11 Introduction.............................. B-11 Preparing an Alternate Disk............... B-11 Using the Alternate Disk.................. B-13 C License Management Supplement Overview...................................... C-2 Using the License Unit Requirement Table (LURT).................................... C-2 License Management Facility (LMF) Notes....... C-7 Restrictions.............................. C-8 For More Information...................... C-10 D Preparing to Use OpenVMS Management Station Overview...................................... D-2 Introduction.............................. D-2 Required Files............................ D-2 Checklist................................. D-3 Preparing Your Systems.............................. D-5 Preparing Your OpenVMS System................. D-6 Introduction.............................. D-6 Files Installed on OpenVMS................ D-6 xii Editing System Files...................... D-7 Starting OpenVMS Management Station on Other Nodes............................... D-8 Preparing Your PC............................. D-9 Introduction.............................. D-9 Required Memory and Disk Space............ D-9 Media..................................... D-9 Required Software......................... D-10 PATHWORKS Client Requirements............. D-10 Creating the Installation Media........... D-11 Installing the OpenVMS Management Station Client Software on Your PC................................. D-13 Overview...................................... D-14 Installing the Client Software................ D-15 Installation Procedure.................... D-15 Recovering from Errors.................... D-16 Defining DECnet Nodes......................... D-17 Introduction.............................. D-17 Procedure for Defining DECnet Nodes....... D-17 Files Created on the PC................... D-18 Getting Started............................... D-19 Introduction.............................. D-19 Accessing Online Help..................... D-19 PATHWORKS Installation Tips and Guidelines.......... D-21 Overview...................................... D-22 Required Disk Space....................... D-22 About Installing and Configuring.......... D-22 Installing Using MS-DOS ...................... D-23 Configuring Using Windows..................... D-25 Starting Windows.......................... D-28 Deleting a Directory...................... D-28 Glossary Index xiii Tables 3-1 Prompts for VMScluster Configurations..... 3-35 A-1 SYSGEN Commands Used in the SYSBOOT Procedure................................. A-11 A-2 Emergency Boot Procedures................. A-21 C-1 License Unit Requirement Table (LURT)..... C-3 D-1 Prerequisite and Optional Software........ D-10 D-2 Disk Space Requirements................... D-22 xiv _________________________________________________________________ Preface INTRODUCTION This manual contains installation, upgrade, and operations information for Alpha computers that run OpenVMS Alpha operating system software. WHO SHOULD USE THIS MANUAL 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. HOW THIS MANUAL IS ORGANIZED 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 a VMScluster environment. o Chapter 3 describes how to install the operating system. xv 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. o Chapter 6 supplements Chapter 5 with additional tasks you must perform before upgrading a VMScluster 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 The Glossary defines key terms used in this manual. REQUIRED 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.0 Release Notes, which provides important supplementary information about the OpenVMS Alpha operating system. o VMScluster Systems for OpenVMS and Guidelines for VMScluster Configurations, if you plan to install your system in a VMScluster environment. xvi o OpenVMS Version 7.0 New Features Manual, which describes enhancements and new support included in the OpenVMS Version 7.0 operating system. 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 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. ADDITIONAL DOCUMENTS 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 The OpenVMS License Management Utility Manual, which contains detailed information about registering your software licenses. o A Comparison of System Management on OpenVMS AXP and OpenVMS VAX, which explains similarities and differences between managing OpenVMS Alpha and OpenVMS VAX systems. If you have been responsible for installation, upgrade, and related system management operations on OpenVMS VAX systems, review that manual before performing similar operations on your OpenVMS Alpha system. o The 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 Manager's Manual also describes in more detail how to use the POLYCENTER Software Installation utility to add or remove files, install other software, and perform related operations. o DECnet for OpenVMS Guide to Networking, which contains detailed information about using the DECnet for OpenVMS Alpha software. xvii 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. 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 OpenVMS products and services, access the Digital OpenVMS World Wide Web site. Use the following URL: http://www.openvms.digital.com READER'S COMMENTS Digital 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 881-0120, Attention: OpenVMS Documentation, ZK03-4/U08 Mail OpenVMS Documentation Group, ZKO3-4/U08 110 Spit Brook Rd. Nashua, NH 03062-2698 xviii HOW TO ORDER ADDITIONAL DOCUMENTATION Use the following table to order additional documentation or information. If you need help deciding which documentation best meets your needs, call 800-DIGITAL (800-344-4825). xix CONVENTIONS The name of the OpenVMS AXP operating system has been changed to OpenVMS Alpha. Any references to OpenVMS AXP or AXP are synonymous with OpenVMS Alpha or Alpha. In this manual, every use of DECwindows and DECwindows Motif refers to DECwindows Motif for OpenVMS software. 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.) . . . Horizontal ellipsis points 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. . Vertical ellipsis points 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, if you choose more than one option, you must enclose the choices in parentheses. xx [ ] 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.) { } In command format descriptions, braces indicate a required choice of options; you must choose one of the options listed. boldface text Boldface text represents the introduction of a new term or the name of an argument, an attribute, or a reason. Boldface text is also used to show user input in Bookreader versions of the manual. 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 device- name contains up to five alphanumeric characters). UPPERCASE TEXT Uppercase text indicates a command, the name of a routine, the name of a file, or the abbreviation for a system privilege. xxi Monospace type 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. xxii 1 _________________________________________________________________ Getting Started Getting Started 1-1 Overview _________________________________________________________________ Overview INTRODUCTION This chapter defines key terms and describes preliminary procedures you must perform before an installation or upgrade. 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. This software is supplied in a format that the computer cannot use until you perform an installation or upgrade. HSx device A self-contained, intelligent, mass storage subsystem that lets computers in a VMScluster 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). 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. 1-2 Getting Started Overview ___________________________________________________________ Term__________________Definition___________________________ 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 in a usable format. The installation or upgrade procedure converts the OpenVMS Alpha operating system to this usable format when transferring the software from the operating system CD-ROM to the system disk. Target drive The drive that holds the system disk during the upgrade or installation. Getting Started 1-3 Examining Software and Hardware Components _________________________________________________________________ Examining Software and Hardware Components INTRODUCTION Before beginning an installation or upgrade, be sure you have all the required hardware and software components, as described in the following sections. HARDWARE COMPONENTS Before you begin an installation or upgrade, do the following: o Be sure the hardware has been installed and 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. 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. 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 Multivendor Customer Services, 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-4 Getting Started Examining Software and Hardware Components 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[TM] Alpha[TM] Operating System V7.0 Software Volume Label: ALPHA070 Note: The volume label is the machine-readable name that the OpenVMS Alpha operating system and InfoServer systems use to access the CD-ROM. REQUIRED PALCODE The required and recommended minimum version of privileged architecture library code (PALcode) for the following Alpha computers is 1.15. o AlphaServer 2100 5/250 o AlphaServer 2100 5/300 o AlphaServer 8200 5/300 o AlphaServer 8400 5/300 o AlphaStation 600 5/266 o AlphaStation 600 5/333 The required and recommended minimum PALcode version for all other Alpha computers supported in Version 7.0 of the OpenVMS Alpha operating system is 5.48. If your computer console does not have a specific minimum version of the PALcode, you may not be able to boot your system during the installation or upgrade procedure. Digital recommends, therefore, that you do the following before performing an installation or upgrade: 1. At the console prompt (>>>) on your running Alpha system, enter the SHOW CONFIGURATION command (or SHOW PAL command on DEC 7000 and DEC 10000 Alpha series systems). The system display will indicate which version of PALcode your computer is running. Getting Started 1-5 Examining Software and Hardware Components 2. Refer to the most recent OpenVMS Alpha operating system cover letter or release notes, or contact your Multivendor Customer Services representative to determine whether your system is running the required or recommended minimum version of PALcode. 3. If the PALcode is below the required or recommended minimum, upgrade your console by following the directions contained in either the hardware manuals that came with your Alpha computer or supplementary release notes contained on the separate firmware CD-ROM. Note: If you boot the operating system CD-ROM without first upgrading your console to the required or recommended minimum PALcode, the system will display messages similar to the following: o If you do not have the required minimum PALcode, the system displays a fatal error message similar to the following: APB-F-PALREV, PALcode revision 5.15 is below required minimum of 5.48 UNABLE TO CONTINUE o If you do not have the recommended minimum PALcode, the system displays a warning message similar to the following: APB-W-PALREV, PALcode revision 5.25 is below recommended minimum of 5.48 Although you will still be able to boot your system, contact your Multivendor Customer Services representative about upgrading your console to the recommended minimum version of the PALcode before installing or upgrading the operating system. 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 1-6 Getting Started Examining Software and Hardware Components 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 VMScluster 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. Getting Started 1-7 Using the Operating System CD-ROM _________________________________________________________________ Using the Operating System CD-ROM 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 and installing certain layered products that are included on the operating system CD-ROM. 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, using the POLYCENTER Software Installation utility o List the layered products that can be installed from the CD-ROM using the POLYCENTER Software Installation utility o Install layered products from the CD-ROM, 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 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-8 Getting Started Using the Operating System CD-ROM SAMPLE MENU DISPLAY The following is a sample display of the menu: OpenVMS Alpha (TM) Operating System, Version 7.0 Copyright (c) 1995 Digital Equipment 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) Install or upgrade OpenVMS Alpha Version V7.0 2) List layered product kits that this procedure can install 3) Install or upgrade layered product(s) 4) Execute DCL commands and procedures 5) Shut down this system Enter CHOICE or ? to repeat menu: (1/2/3/4/5/?) Getting Started 1-9 Using the Operating System CD-ROM HOW THE INSTALL OR UPGRADE OPTION WORKS 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. * 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] 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 OpenVMS Alpha 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 1-10 Getting Started Using the Operating System CD-ROM original directory structure, you would have to reinstall the operating system. Getting Started 1-11 Using the Operating System CD-ROM Specifying_the_PRESERVE_Option When you specify the PRESERVE option, the following operations take place: ___________________________________________________________ IF ... THEN ... the OpenVMS Alpha the following operations take place: operating system o The OpenVMS Alpha operating system is not already is installed. installed on the target disk, o All other contents of the target disk are retained. the OpenVMS Alpha the OpenVMS Alpha operating system is operating system upgraded, as 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), Digital recommends that you first make a backup copy of your system disk. If there is any problem during the installation or upgrade which might affect the integrity of the disk, you will have the backup copy as a safeguard. HOW THE LAYERED PRODUCTS OPTIONS WORK After you have installed or upgraded the operating system, you can use the menu to install certain layered products as well. The layered products options allow you to first view the list of layered products that can be installed using the POLYCENTER Software Installation utility (option 2) and then to install them (option 3). 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 each layered product. Because the operating system is booted from the CD-ROM and 1-12 Getting Started Using the Operating System CD-ROM the layered products are installed on a different device (the target disk), 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). HOW THE DCL OPTION WORKS When you choose the DCL option (4) 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 menu, enter the LOGOUT command. HOW THE SHUTDOWN OPTION WORKS When you choose the shutdown option (5) 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 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: Getting Started 1-13 Using the Operating System CD-ROM ___________________________________________________________ IF ... THEN ... you want to install the go to Chapter 2. operating system in a VMScluster environment, 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 VMScluster environment, you want only to back up or go to Appendix B. restore your system disk, 1-14 Getting Started 2 _________________________________________________________________ Preparing to Install in a VMScluster Environment Preparing to Install in a VMScluster Environment 2-1 Overview _________________________________________________________________ Overview This chapter contains information you should review before performing an installation in a VMScluster environment. This will help you have have a clear understanding of VMScluster systems so you can enter correct information when you are prompted to do so. Note: Before installing the OpenVMS Alpha operating system in a VMScluster environment, note the following: o If you enter incorrect VMScluster information during the installation, you might have to repeat the entire installation procedure. Therefore, review this chapter carefully before beginning the installation. o If you configure your OpenVMS Alpha Version 7.0 system in a mixed-architecture VMScluster environment that includes VAX computers, those VAX computers must be running only Version 5.5-2, Version 6.0, Version 6.1, or Version 6.2 of the OpenVMS VAX operating system. WHERE TO FIND MORE INFORMATION Before installing the operating system in a VMScluster environment, be sure you review any relevant VMScluster information, contained in the following documents: o The cover letters and the software product descriptions included with your distribution kit o OpenVMS Version 7.0 New Features Manual o The OpenVMS Version 7.0 Release Notes o If you are installing the operating system in a DSSI VMScluster system, the DSSI VMScluster Installation and Troubleshooting Guide Be sure the following sources of information are available as well: o VMScluster Systems for OpenVMS o Guidelines for VMScluster Configurations o DECnet for OpenVMS Guide to Networking o Your network or system manager 2-2 Preparing to Install in a VMScluster Environment Overview VMSCLUSTER INFORMATION YOU WILL NEED If during the installation you answer YES to the system prompt asking whether your system will be a member of a VMScluster, 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 VMScluster 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. See the DECnet for OpenVMS Guide to Networking for additional information as well. Preparing to Install in a VMScluster Environment 2-3 Overview ___________________________________________________________ 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 Alpha143 ALLOCLASS parameter: Refer to VMScluster Systems for OpenVMS for the rules on specifying allocation class values. Note that in a mixed-interconnect VMScluster 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 VMScluster Systems for quorum disk OpenVMS to help you determine whether you want a quorum disk in the cluster. 2-4 Preparing to Install in a VMScluster Environment Overview ___________________________________________________________ Required Information___________Explanation__________________________ 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 VMScluster Systems for OpenVMS 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. 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 Operations Protocol. Preparing to Install in a VMScluster Environment 2-5 Overview WHAT TO DO NEXT After you have completed all the tasks in this chapter, go to Chapter 3 to begin the installation. 2-6 Preparing to Install in a VMScluster Environment 3 _________________________________________________________________ Installing the OpenVMS Alpha Operating System Installing the OpenVMS Alpha Operating System 3-1 Overview _________________________________________________________________ Overview INTRODUCTION This chapter describes the following tasks: o Preparing to respond to prompts during the installation o Installing from the operating system CD-ROM or from a running system 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 a VMScluster (optional) o Running AUTOGEN o Logging in to the SYSTEM account CHECKING PALCODE Before you install the operating system, be sure your computer is running the correct version of PALcode, as described in the section titled Required PALcode in Chapter 1. 3-2 Installing the OpenVMS Alpha Operating System Preparing to Respond to Prompts During the Installation _________________________________________________________________ Preparing to Respond to Prompts During the Installation INTRODUCTION 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. However, Digital recommends that you review the following summary before you begin the installation so that you have an understanding ahead of time of the types of information you will need to provide. SUMMARY OF PROMPTS 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 a VMScluster 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). Important: These settings identify your system by name and number in a DECnet or cluster environment. Be sure you can supply a node name and DECnet address before you begin the installation. Note as well that if you supply a DECnet address, the system will automatically Installing the OpenVMS Alpha Operating System 3-3 Preparing to Respond to Prompts During the Installation 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-4 Installing the OpenVMS Alpha Operating System 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. (Note that you must install the DECwindows components if you plan to install the separate DECwindows Motif for OpenVMS Alpha layered product. You must also install all of the OpenVMS Management Station server and client software files if you plan to use this product with your PC.) Installing the OpenVMS Alpha Operating System 3-5 Installing from CD-ROM or from a Running System _________________________________________________________________ Installing from CD-ROM or from a Running System INTRODUCTION The OpenVMS Alpha Version 7.0 operating system includes procedures that allow you to easily install the operating system using the POLYCENTER Software Installation utility. In console mode, you can boot the operating system CD-ROM to begin the installation procedure. On a system that is already running the OpenVMS Alpha Version 7.0 operating system, you can invoke the installation procedure by entering a command at the DCL level. HOW TO BEGIN Depending on whether you are installing the OpenVMS Alpha operating system from the operating system CD-ROM or from a running OpenVMS Alpha Version 7.0 system, begin the procedure as follows: ___________________________________________________________ If installing from ... Then... the operating go to the section titled Booting the system CD-ROM, Operating System CD-ROM a running Version go to the section titled Creating the 7.0 system, System Disk 3-6 Installing the OpenVMS Alpha Operating System Booting the Operating System CD-ROM _________________________________________________________________ Booting the Operating System CD-ROM INTRODUCTION 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. 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 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 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 -FL 0,0 -FI APB_070 lan-device-name Note the following conventions: o APB_070 is the file name of the APB program used for the initial system load (ISL) boot program. Installing the OpenVMS Alpha Operating System 3-7 Booting the Operating System CD-ROM 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. ________________________________________________________ Ethernet FDDI Alpha_Computer_____________Device________Device_________ AlphaServer 1000 series ERA0, EWA0 FRA0 AlphaServer 2000 series ERA0, EWA0 FRA0 AlphaServer 2100 series ERA0, EWA0 FRA0 AlphaServer 8200 series EXA0, EWA0 FXA0 AlphaServer 8400 series EXA0, EWA0 FXA0 AlphaStation 200 series EWA0 - AlphaStation 400 series EWA0 - AlphaStation 600 series ERA0, EWA0 - DEC 2000 series ERA0 - DEC 3000 series ESA0 "n/ESA0" DEC 4000 series EZA0 - DEC 7000 series EXA0 FXA0 DEC 10000 series EXA0 FXA0 Notes: If you are using a DEC 3000 or 4000 series system, note the following: o On DEC 3000 series systems, you can boot through the InfoServer using an alternate 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 prompt (>>>) and examining the display. For more information, see the section titled Booting 3-8 Installing the OpenVMS Alpha Operating System Booting the Operating System CD-ROM Over the Network with an Alternate TURBOchannel Adapter, in Appendix A. o On DEC 4000 series, you must specify the ISL file name in uppercase (APB_070). In addition, if your system uses console firmware prior to Version 3.2, enter the BOOT command as follows: >>> BOOT -FL 0,0 -start 0 -FI APB_070 EZA0 2. The InfoServer ISL program then displays the following menu: Network Initial System Load Function Version 1.1 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 (ALPHA070). 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: ALPHA070 Installing the OpenVMS Alpha Operating System 3-9 Booting the Operating System CD-ROM 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 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 operating INITIALIZE option, 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 operating option, system CD-ROM. 2. Enter the DCL environment by choosing option 2 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. ___________________________________________________________ 3-10 Installing the OpenVMS Alpha Operating System Creating the System Disk _________________________________________________________________ Creating the System Disk 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 Alpha (TM) Operating System, Version V7.0 $! Copyright (c) 1995 Digital Equipment 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) Install or upgrade OpenVMS Alpha Version V7.0 2) List layered product kits that this procedure can install 3) Install or upgrade layered product(s) 4) Execute DCL commands and procedures 5) Shut down this system Enter CHOICE or ? to repeat menu: (1/2/3/4/5/?) 1 After you choose the install option, go to the section titled Choosing INITIALIZE or PRESERVE to continue the procedure. Installing the OpenVMS Alpha Operating System 3-11 Creating the System Disk INSTALLING FROM A RUNNING SYSTEM If you are installing the operating system from an Alpha system that is already running Version 7.0 of the OpenVMS Alpha operating system, enter the following command from the SYSTEM account and then press the Return key: $ @SYS$SYSTEM:AXPVMS$PCSI_INSTALL After you enter the command, go to the section titled Choosing INITIALIZE or PRESERVE to continue the procedure. CHOOSING INITIALIZE OR PRESERVE After you choose the install option (if you are installing from the operating system CD-ROM) or start the AXPVMS$PCSI_ INSTALL command procedure (if you are installing from a running OpenVMS Alpha Version 7.0 system), 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) 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 install OpenVMS Alpha on an existing disk on which OpenVMS VAX or any other operating system is installed. Do you want to INITIALIZE or to PRESERVE? [PRESERVE]) 3-12 Installing the OpenVMS Alpha Operating System 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, 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) ? Device Device Error Volume Free Trans Mnt Name Status Count Label Blocks Count Cnt DKA100: Online 0 DKA200: Online 0 DKA400: Online wrtlck 0 Enter device name for target disk: (? for choices) DKA200 Installing the OpenVMS Alpha Operating System 3-13 Creating the System Disk 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 (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 (_)). 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: DKA200: is now labeled SYSDISK Do you want to keep this label? (Yes/No) [Yes] NO Enter volume label for target system disk: [AXPVMSSYS] You have chosen to install OpenVMS Alpha on a new disk. The target system disk, DKA200:, will be initialized. It will be labeled AXPVMSSYS. Any data currently on the target system disk will be lost. Is this OK? (yes/No) YES Initializing and mounting target ... 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. 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. 3-14 Installing the OpenVMS Alpha Operating System Creating the System Disk Password for SYSTEM account: Re-enter SYSTEM password for verification: If you enter 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. 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 a VMScluster? (Yes/No) [No] If you answer Yes, you will be asked a series of questions about the cluster after you boot the new system disk. Installing the OpenVMS Alpha Operating System 3-15 Creating the System Disk SETTING SYSTEM PARAMETERS Next, you must set two parameters, SCSNODE and SCSSYSTEMID, so that your system is identified by name and number in a DECnet or cluster environment. If you plan to use DECnet software, you must specify a DECnet address (which the system uses to calculate the SCSSYSTEMID value). The following is an example of the system 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 OSI (Phase V) node synonym. If you have multiple OpenVMS systems, the SCSNODE on each system must be unique. Enter SCSNODE: mynode If you plan to use DECnet, SCSSYSTEMID must be set based on the DECnet 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 1 and 1023. If you plan to use DECnet OSI (Phase V), enter the Phase IV compatible address. If you plan to use DECnet OSI (Phase V) WITHOUT Phase IV compatible addresses, enter 0.0. Enter DECnet (Phase IV) Address [1.1]: 63.180 SCSSYSTEMID will be set to 64692, calculated as follows: (DECnet_area_number * 1024) + DECnet_node_number) 3-16 Installing the OpenVMS Alpha Operating System Creating the System Disk 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. You begin by selecting the desired time zone from the main time zone menu, which is the first menu displayed. 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. A sample display follows: 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 Installing the OpenVMS Alpha Operating System 3-17 Creating the System Disk 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 describes your location: 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 repects 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): NO Enter the Time Differential Factor: -5 NEW SYSTEM TIME DIFFERENTIAL FACTOR = -5:00. Is this correct? [Y]: For more information about TDF and local time zone support, see the OpenVMS Version 7.0 New Features Manual. Also, see the section in the OpenVMS System Manager's Manual entitled "Customizing the System to Compensate for Different Time Zones". 3-18 Installing the OpenVMS Alpha Operating System Registering Licenses _________________________________________________________________ Registering Licenses INTRODUCTION 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 Digital recommends), by responding to the prompts displayed by the SYS$UPDATE:VMSLICENSE.COM procedure. o After the installation, by using the LICENSE REGISTER command or by invoking SYS$UPDATE:VMSLICENSE.COM. 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 licenses include the NO_SHARE attribute and remain with the initial host computer. _________________________________________________________________ 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. Installing the OpenVMS Alpha Operating System 3-19 Registering Licenses _________________________________________________________________ Type_of_License____________Description___________________________ 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. 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-20 Installing the OpenVMS Alpha Operating System Registering Licenses FOR MORE INFORMATION 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 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: ___________________________________________________________ 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 Digital 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. Installing the OpenVMS Alpha Operating System 3-21 Registering Licenses ___________________________________________________________ IF ... THEN ... 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 the section titled Completing the Installation. 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-22 Installing the OpenVMS Alpha Operating System Registering Licenses 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: 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. Installing the OpenVMS Alpha Operating System 3-23 Completing the Installation _________________________________________________________________ Completing the Installation 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. 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 VMS V7.0 *** DEC AXPVMS VMS V7.0: VMS Operating System, Version V7.0 COPYRIGHT (c) 29-DEC-1995 -- All rights reserved Digital Equipment Corporation After the system displays a series of additional messages, it 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: Do you want all the default values for this product [YES] Notes: 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 group and subgroup of files. o If you are not sure whether you want certain files, request help by entering a question mark (?) at the prompt for that file (or group of files). 3-24 Installing the OpenVMS Alpha Operating System Completing the Installation o After you select all the files you want, you will have an opportunity to view your selections and make changes (if necessary). o If you plan to install the separate DECwindows Motif for OpenVMS Alpha layered product, you must install the DECwindows base support and workstation support (to run windowing software on Alpha workstations or in a VMScluster that includes workstations or Xterminals) included with the OpenVMS Alpha operating system. 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 installation to change which OpenVMS Alpha operating system files you want installed on your system, you can use the POLYCENTER Software Installation utility on your running system to add or remove files. 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 ($). LIST OF COMPONENTS Following is the list of components included with the OpenVMS Alpha Version 7.0 operating system: Installing the OpenVMS Alpha Operating System 3-25 Completing the Installation Accounting Log Report Generator Utility Access Control List Utilities Print and Batch Queue Utilities DECdtm Distributed Transaction Manager DECnet Phase IV / DECnet/OSI Support DECnet Phase IV DECnet/OSI 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 RMS Journaling Recovery Utility System Programming Support Support for ISO 9660 and High Sierra CDrom Formats MONITOR Analyze Object File Utility 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 3-26 Installing the OpenVMS Alpha Operating System Completing the Installation 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 COMPLETING THE PROCEDURE When you have answered all the prompts and selected the components you want installed, the system gives you the opportunity to review your selections (and make changes if necessary), then installs the product, provides informational messages, and returns you to the menu. Following is a sample display. Note: If you are installing from a running OpenVMS Alpha Version 7.0 system, the system displays the dollar sign prompt ($) instead of the 5-option menu when the installation is complete. Do you want to view the values? [NO] %PCSIUI-I-DONEASK, execution phase starting The following product will be installed: DEC AXPVMS VMS V7.0 %PCSI-I-VOLINFO, estimated space information for volume DISK$AXPVMSSYS -PCSI-I-VOLSPC, 265572 required; 811128 available; 545556 net Portion Done: 10%...20%...30%...40%...50%...60%...70%...80%...90%...100% The following product has been installed: DEC AXPVMS VMS V7.0 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 VMScluster operation. o Run AUTOGEN to set system parameters o Reboot the system with the newly set parameters. Installing the OpenVMS Alpha Operating System 3-27 Completing the Installation You can shut down now or continue with other operations. Process SYSTEM_1 logged out at 29-DEC-1995 14:55:52.16 **************************************************************** 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.0 2) List layered product kits that this procedure can install 3) Install or upgrade layered product(s) 4) Execute DCL commands and procedures 5) Shut down this system Enter CHOICE or ? to repeat menu: (1/2/3/4/5/?) WHAT TO DO NEXT If you want to install layered products, including the DECwindows Motif for OpenVMS layered product, go to the next section. If you do not want to install layered products or perform any other operations prior to booting the new system disk, choose 5 from the menu to shut down the system. The system display is similar to the following: Enter CHOICE or "?" to repeat menu: (1/2/3/4/5/?) 5 Shutting down the system SYSTEM SHUTDOWN COMPLETE After you complete the installation and shut down the system, go to the section titled Booting the New System Disk. 3-28 Installing the OpenVMS Alpha Operating System Installing Layered Products _________________________________________________________________ Installing Layered Products INTRODUCTION 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.) HOW TO INSTALL To install layered products using the POLYCENTER Software Installation utility, choose option 2 to view the list and then option 3. For example: Please choose one of the following: 1) Install or upgrade OpenVMS Alpha Version V7.0 2) List layered product kits that this procedure can install 3) Install or upgrade layered product(s) 4) Execute DCL commands and procedures 5) Shut down this system Enter CHOICE or ? to repeat menu: (1/2/3/4/5/?) 2 The following layered product kits are available on the OpenVMS operating system CD-ROM and can be installed at this time: DEC AXPVMS AMDS V6.1 found in DKB400:[KITS.AMDS061] DEC AXPVMS DWMOTIF V1.2-3 found in DKB400:[KITS.DWMOTIF] DEC AXPVMS POSIX V2.0 found in DKB400:[KITS.POSIX] DEC AXPVMS SOFTWIN V1.0 found in DKB400:[KITS.SOFTWINDOWS] DEC AXPVMS SWXCR V2.0 found in DKB400:[KITS.SWXCR$KIT] **************************************************************** 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: Installing the OpenVMS Alpha Operating System 3-29 Installing Layered Products 1) Install or upgrade OpenVMS Alpha Version V7.0 2) List layered product kits that this procedure can install 3) Install or upgrade layered product(s) 4) Execute DCL commands and procedures 5) Shut down this system Enter CHOICE or ? to repeat menu: (1/2/3/4/5/?) 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. o If you are upgrading to 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. You must enter the device name for the target disk on which the layered product(s) will be installed. Enter device name for target disk: (? for choices) DKA200 DKA200: is labeled AXPVMSSYS. 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 AMDS V6.1 2 - DEC AXPVMS DWMOTIF V1.2-3 3 - DEC AXPVMS POSIX V2.0 4 - DEC AXPVMS SOFTWIN V1.0 5 - DEC AXPVMS SWXCR V2.0 6 - All products listed above 7 - Exit Desired Product(s): 2 The following product has been selected: DEC AXPVMS DWMOTIF V1.2-3 Do you want to continue? [YES] 3-30 Installing the OpenVMS Alpha Operating System Installing Layered Products *** DEC AXPVMS DWMOTIF V1.2-3: DECwindows Motif V1.2-3 for OpenVMS Alpha Copyright Digital Equipment Corporation 1988, 1995. All rights reserved. Digital Equipment Corporation This product uses the PAK: DW-MOTIF Do you want all the default values for this product? [YES] no DECwindows Motif runtime support files [YES] Programming Support (C Language) [YES] Fortran programming support [YES] PASCAL programming support [YES] Programming examples [YES] Translated Image Support (OSF/Motif V1.1.3) [NO] Do you want to view the values? [NO] no %PCSIUI-I-DONEASK, execution phase starting The following product will be installed: DEC AXPVMS DWMOTIF V1.2-3 %PCSI-I-VOLINFO, estimated space information for volume DISK$AXPVMSSYS -PCSI-I-VOLSPC, 96117 required; 478119 available; 382002 net Portion Done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% The following product has been installed: DEC AXPVMS DWMOTIF V1.2-3 The installation is now complete. Process AXPVMS_INST_LP logged out at 20-DEC-1995 12:14:27.54 **************************************************************** 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: Installing the OpenVMS Alpha Operating System 3-31 Installing Layered Products 1) Install or upgrade OpenVMS Alpha Version V7.0 2) List layered product kits that this procedure can install 3) Install or upgrade layered product(s) 4) Execute DCL commands and procedures 5) Shut down this system If you do not want to perform any other operations prior to booting the new system disk, enter 5 to shut down the system. The system display is similar to the following: Enter CHOICE or "?" to repeat menu: (1/2/3/4/5/?) 5 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-32 Installing the OpenVMS Alpha Operating System Booting the New System Disk _________________________________________________________________ Booting the New System Disk INTRODUCTION After you have successfully installed the operating system, boot the new system disk, as described in the following sections. 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, 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 the section titled Setting and Showing Boot Devices in Appendix A. ____________________ [1] For more information about halting your Alpha computer, see Appendix A. Installing the OpenVMS Alpha Operating System 3-33 Booting the New System Disk 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: OpenVMS Alpha (TM) Operating System, Version V7.0 $! Copyright (c) 1995 Digital Equipment Corporation. All rights reserved. Installing required known files... Configuring devices... . . . 3-34 Installing the OpenVMS Alpha Operating System Joining a VMScluster _________________________________________________________________ Joining a VMScluster INTRODUCTION If during the installation, you previously answered Yes to the question about joining a VMScluster, 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 VMScluster Systems for OpenVMS or Guidelines for VMScluster Configurations to answer these questions. VMSCLUSTER PROMPTS Following is a list of VMScluster 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_VMScluster_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. What is the node's DECnet node Enter the DECnet node address- address? for example, 2.2. (continued on next page) Installing the OpenVMS Alpha Operating System 3-35 Joining a VMScluster Table_3-1_(Cont.)_Prompts_for_VMScluster_Configurations__________ Question__________________________How_to_Respond_________________ Will the Ethernet be used for Enter N for a CI only or DSSI- cluster communications (Y/N)? only VMScluster. 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 VMScluster Systems for OpenVMS 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 VMScluster 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 many not need to supply the cluster group number and password. (continued on next page) 3-36 Installing the OpenVMS Alpha Operating System Joining a VMScluster Table_3-1_(Cont.)_Prompts_for_VMScluster_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 VMScluster Systems for OpenVMS. 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 VMScluster Systems for OpenVMS for information on quorum disks. WHAT TO DO NEXT After you respond to the VMScluster prompts, continue to the next section to run AUTOGEN. Installing the OpenVMS Alpha Operating System 3-37 Running AUTOGEN _________________________________________________________________ Running AUTOGEN HOW AUTOGEN WORKS 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, the installation procedure is complete. AUTOGEN MESSAGES 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 a VMScluster 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, DKA200:[SYS0.SYSEXE]PAGEFILE.SYS;1 extended %SYSGEN-I-EXTENDED, DKA200:[SYS0.SYSEXE]SWAPFILE.SYS;1 extended %SYSGEN-I-CREATED, SYS$SYSROOT:[SYSEXE]SYSDUMP.DMP;1 created %AUTOGEN-I-REPORT, AUTOGEN has produced some informational messages which have been stored in the file SYS$SYSTEM:AGEN$PARAMS.REPORT. You may wish to review the information in that file. 3-38 Installing the OpenVMS Alpha Operating System Running AUTOGEN %AUTOGEN-I-END, GENFILES phase has successfully completed. %AUTOGEN-I-BEGIN, SETPARAMS phase is beginning. . . . Installing the OpenVMS Alpha Operating System 3-39 Rebooting the System _________________________________________________________________ Rebooting the System INTRODUCTION 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 %SHUTDOWN-I-BOOTCHECK, performing reboot consistency check... %SHUTDOWN-I-CHECKOK, basic reboot consistency check completed . . . 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, the system displays a message similar to the following: OpenVMS Alpha (TM) Operating System, Version V7.0 Copyright (c) 1995 Digital Equipment Corporation. All rights reserved. %STDRV-I-STARTUP, VMS startup begun at 15-DEC-1995 16:24:02.27 . . . 3-40 Installing the OpenVMS Alpha Operating System Logging in to the SYSTEM Account _________________________________________________________________ Logging in to the SYSTEM Account INTRODUCTION The system next displays informational messages and accounting information indicating that your OpenVMS Alpha operating system is running. For example: %SET-I-INTSET, login interactive limit = 64, current interactive value = 0 SYSTEM job terminated at 29-DEC-1995 12:55:43.92 Accounting information: Buffered I/O count: 1733 Peak working set size: 3184 Direct I/O count: 650 Peak page file size: 19440 Page faults: 974 Mounted volumes: 0 Charged CPU time: 0 00:00:04.45 Elapsed time: 0 00:00:34.82 At this time, you can log in to the SYSTEM account (so you can perform postinstallation tasks), as described in the following sections. LOGGING IN TO 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: Welcome to OpenVMS Alpha (TM) Operating System, Version V7.0 Username: SYSTEM Password: . . . Welcome to OpenVMS Alpha (TM) Operating System, Version V7.0 (If you forget your password, follow the instructions in Appendix A to perform an emergency startup.) Installing the OpenVMS Alpha Operating System 3-41 Logging in to the SYSTEM Account LOGGING IN TO 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. 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 Installing the OpenVMS Alpha Operating System 4-1 Overview _________________________________________________________________ Overview After you have installed the OpenVMS Alpha operating system, you must perform several important tasks to prepare the system for operation. These tasks, described in this chapter in the order in which you perform them, are as follows: o Registering licenses o Creating accounts o Backing up the system disk o Customizing the system o Configuring and starting DECnet for OpenVMS Alpha 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, including DECwindows o Backing up the customized system disk o Configuring a multihead system o Running AUTOGEN o Using the postinstallation checklist 4-2 After Installing the OpenVMS Alpha Operating System Registering Your Licenses _________________________________________________________________ Registering Your Licenses INTRODUCTION 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 such as the DECnet for Open VMS Alpha software. You can invoke the OpenVMS License utility by entering the following command: $ @SYS$UPDATE:VMSLICENSE (You can also use the LICENSE REGISTER command.) FOR MORE INFORMATION For information about registering licenses, see the following: o The section titled Registering Licenses in Chapter 3 o Appendix C o The OpenVMS License Management Utility Manual After Installing the OpenVMS Alpha Operating System 4-3 Creating Accounts _________________________________________________________________ Creating Accounts INTRODUCTION During the installation, DEFAULT and SYSTEM accounts are created for you automatically. However, if plan to have Digital 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 (VMScluster system) account to run UETP. FOR MORE INFORMATION For complete information about creating accounts for Digital service representatives and UETP, see the OpenVMS System Manager's Manual: Essentials. 4-4 After Installing the OpenVMS Alpha Operating System Backing Up Your System Disk _________________________________________________________________ Backing Up Your System Disk INTRODUCTION 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. HOW TO BACK UP THE SYSTEM DISK To back up the system disk, do the following: 1. Shut down the system (described in Appendix A). 2. Boot the operating system CD-ROM (locally or from the InfoServer). 3. Use the menu system to enter the DCL environment (option 4). 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 5 from the menu. 8. Boot from the system disk. WHEN TO BACK UP 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 MORE INFORMATION 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. After Installing the OpenVMS Alpha Operating System 4-5 Customizing the System _________________________________________________________________ Customizing the System INTRODUCTION You can customize the system to meet your site-specific needs. In addition, if your Alpha computer is part of a VMScluster environment, you must prepare the cluster environment and configure the cluster. FOR MORE INFORMATION For instructions on customizing the system, review the following documentation: o If the computer is part of a VMScluster environment, refer to VMScluster Systems for OpenVMS for further information on setting up a cluster. o The release notes, release notes addendum, and A Comparison of System Management on OpenVMS AXP and OpenVMS VAX, for notes and restrictions that might be relevant to your customization plans. o The OpenVMS System Manager's Manual, for instructions on customizing and using your system. You will find information about the following tasks: o Editing the template files SYCONFIG.COM, SYLOGICALS.COM, SYLOGIN.COM, and SYSTARTUP_VMS.COM o Starting the queue manager and creating a queue database o Setting up user accounts o Adjusting system parameters o Setting up your system to run DECdtm services o The section in this chapter titled Configuring and Starting DECnet for OpenVMS Alpha Software. Note: You can customize your DECwindows environment as well, but you must first install the separate DECwindows Motif for OpenVMS Alpha layered product (see the section titled Installing Layered Products). 4-6 After Installing the OpenVMS Alpha Operating System Configuring and Starting DECnet for OpenVMS Alpha Software _________________________________________________________________ Configuring and Starting DECnet for OpenVMS Alpha Software If you plan to run DECnet for OpenVMS Alpha software, you must do the following: 1. After you have registered the license for the DECnet 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. 2. 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 for OpenVMS software starts automatically when your system is booted. Edit the file as follows: o 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 o 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 3. If you plan to run both DECnet 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: After Installing the OpenVMS Alpha Operating System 4-7 Configuring and Starting DECnet for OpenVMS Alpha Software $ DEFINE DECW$IGNORE_DECNET TRUE If you are not going to start the DECnet for OpenVMS Alpha software or have not yet started it, this command tells the DECwindows software not to wait for the DECnet for OpenVMS Alpha software. 4-8 After Installing the OpenVMS Alpha Operating System Testing the System with UETP _________________________________________________________________ Testing the System with UETP INTRODUCTION 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, Digital recommends that you run UETP to verify the installation. FOR MORE INFORMATION For complete information about using UETP, see the OpenVMS System Manager's Manual. After Installing the OpenVMS Alpha Operating System 4-9 Decompressing the System Libraries _________________________________________________________________ Decompressing the System Libraries INTRODUCTION 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. 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. 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. 4-10 After Installing the OpenVMS Alpha Operating System Decompressing the System Libraries 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 resulting display is similar to the following: VMS Library Decompression Utility Options: 1 HELPLIB.HLB 12 EDTHELP.HLB 22 EVE$KEYHELP.HLB 2 STARLET.OLB 13 NCPHELP.HLB 23 UAFHELP.HLB 3 ACLEDT.HLB 14 SDA.HLB 24 LIB.MLB 4 ANLRMSHLP.HLB 15 SHWCLHELP.HLB 25 STARLET.MLB 5 DBG$HELP.HLB 16 SYSGEN.HLB 26 STARLETSD.TLB 6 DISKQUOTA.HLB 17 ANALAUDIT$HELP 27 DECC$RTLDEF.TLB 7 EDFHLP.HLB 18 SYSMANHELP.HLB 28 VAXCCURSE.OLB 8 INSTALHLP.HLB 19 TFF$TFUHELP.HLB 29 VAXCRTL.OLB 9 LATCP$HELP.HLB 20 TPUHELP.HLB 30 VAXCRTLD.OLB 10 MAILHELP.HLB 21 EVE$HELP.HLB 31 VAXCRTLT.OLB 11 MNRHELP.HLB or 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.) 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. After Installing the OpenVMS Alpha Operating System 4-11 Decompressing the System Libraries 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-12 After Installing the OpenVMS Alpha Operating System Decompressing the System Libraries 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. After Installing the OpenVMS Alpha Operating System 4-13 Adding and Removing Files _________________________________________________________________ Adding and Removing Files INTRODUCTION If you decide after the installation to change which OpenVMS Alpha operating system files you want installed on your system, you can use the POLYCENTER Software Installation utility on your running system to add or remove files. Note that you can obtain information about individual system files by entering HELP SYSTEM_FILES at the dollar sign prompt ($). HOW TO ADD AND REMOVE FILES To add or remove operating system files, use the DCL command PRODUCT RECONFIGURE VMS. Note that if you add files, you will need the OpenVMS Alpha operating system CD-ROM. FOR MORE INFORMATION For more information about using the POLYCENTER Software Installation utility to add or remove files, see the OpenVMS System Manager's Manual. 4-14 After Installing the OpenVMS Alpha Operating System Preparing to Use OpenVMS Management Station _________________________________________________________________ Preparing to Use OpenVMS Management Station INTRODUCTION 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: 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 Creating installation media for PC client software o Installing the client software on your PC o Defining DECnet nodes FOR MORE INFORMATION For complete information about preparing your OpenVMS system and your PC to run the OpenVMS Management Station server and client software, see Appendix D. REMOVING FILES Note that after you complete the tasks described in Appendix D, which include transferring the client software files from your system to two floppy diskettes, you can then remove those files from your system to save disk space. (Use the PRODUCT RECONFIGURE command rather than a delete operation.) After Installing the OpenVMS Alpha Operating System 4-15 Installing Layered Products _________________________________________________________________ Installing Layered Products PROCEDURE 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. 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 5 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. 4-16 After Installing the OpenVMS Alpha Operating System Installing Layered Products 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] 3. To install layered products that require VMSINSTAL (indicated in the directories by saveset file names with file types of .A, .B, and so on), enter the @SYS$UPDATE:VMSINSTAL command and then specify the CD-ROM device and directory. For example: $ @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 or the Motif interface to the POLYCENTER Software Installation utility 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] DECWINDOWS SUPPORT The DECwindows components provided with the OpenVMS Alpha Version 7.0 operating system supply only DECwindows base support and workstation support files. To get full DECwindows support, you must also install the separate DECwindows Motif for OpenVMS Alpha layered product, which supports both the Motif and XUI environments. After Installing the OpenVMS Alpha Operating System 4-17 Installing Layered Products MONITORING PERFORMANCE HISTORY The OpenVMS Alpha Version 7.0 operating system CD-ROM also includes a Monitoring Performance History (MPH) kit located in the [MPH] directory. See the OpenVMS Version 7.0 Release Notes for more information about installing and using this optional software. ADDITIONAL NOTES Note the following: o For additional information about installing layered products, see the OpenVMS System Manager's Manual. o Be sure you back up the system disk after you install all your layered products. 4-18 After Installing the OpenVMS Alpha Operating System Backing Up the Customized System Disk _________________________________________________________________ Backing Up the Customized System Disk INTRODUCTION After you have customized the OpenVMS Alpha operating system to your satisfaction and installed your layered products, protect your work by making a backup copy of the system disk. HOW TO BACK UP THE CUSTOMIZED SYSTEM DISK To back up the system disk, do the following: 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 4). 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 5 from the menu. 8. Boot from the system disk. FOR MORE INFORMATION 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. After Installing the OpenVMS Alpha Operating System 4-19 Configuring a Multihead System _________________________________________________________________ Configuring a Multihead System DEFINITION 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). INTRODUCTION 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. HOW TO SET UP THE SYSTEM To set up your system for multihead support, do the following: 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 4-20 After Installing the OpenVMS Alpha Operating System Configuring a Multihead System FOR MORE INFORMATION 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. After Installing the OpenVMS Alpha Operating System 4-21 Running AUTOGEN _________________________________________________________________ Running AUTOGEN INTRODUCTION When you installed the 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 need to run the AUTOGEN.COM procedure again to properly tune the system. WHEN TO RUN 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. Digital 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. 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. 4-22 After Installing the OpenVMS Alpha Operating System Running AUTOGEN FOR MORE INFORMATION For more information about the MODPARAMS.DAT file and about using AUTOGEN in general, see the OpenVMS System Manager's Manual. After Installing the OpenVMS Alpha Operating System 4-23 Postinstallation Checklist _________________________________________________________________ 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). 4-24 After Installing the OpenVMS Alpha Operating System 5 _________________________________________________________________ Before Upgrading the OpenVMS Alpha Operating System Before Upgrading the OpenVMS Alpha Operating System 5-1 Overview _________________________________________________________________ Overview This chapter describes which tasks you should perform prior to beginning an upgrade. Tasks described in this chapter include: o Reviewing 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 FOR MORE INFORMATION In addition to reviewing the information in this chapter, you might need to refer to the following sources of information as well: o The OpenVMS Version 7.0 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 5-2 Before Upgrading the OpenVMS Alpha Operating System Cautions and Restrictions _________________________________________________________________ Cautions and Restrictions INTRODUCTION 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. REQUIRED OPERATING SYSTEM VERSION To upgrade to Version 7.0 of the OpenVMS Alpha operating system, you must be running at least Version 6.1 or 6.2. If you are upgrading in a cluster environment, also see Chapter 6 for information about required versions of the OpenVMS Alpha and OpenVMS VAX operating systems. UPDATE LICENSE To upgrade to OpenVMS Version 7.0, you must have an appropriate license. Digital'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 license prior to Version 7.0 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 Version 7.0. If you do not have an Update License, please contact your Digital account representative who will assist you in obtaining the correct Product Authorization Key (PAK) needed to access the OpenVMS operating system. FILES AND DIRECTORIES Note the following about files and directories: o 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. Before Upgrading the OpenVMS Alpha Operating System 5-3 Cautions and Restrictions o 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. o The OpenVMS Alpha Version 7.0 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 AXP Guide to System Security. LICENSES AND LAYERED PRODUCTS Note the following: o The upgrade procedure is designed so that you should not have to reinstall most layered products after the upgrade. However, you might need to reinstall certain layered products because of product-specific installation procedures. o 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-4 Before Upgrading the OpenVMS Alpha Operating System Preparing to Upgrade in a Volume Shadowing Environment _________________________________________________________________ Preparing to Upgrade in a Volume Shadowing Environment INTRODUCTION 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. 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. 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 -FL 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. Before Upgrading the OpenVMS Alpha Operating System 5-5 Preparing to Upgrade in a Volume Shadowing Environment 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 VMScluster systems, be sure that the volume label is a unique name across the cluster. 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 VMScluster 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: 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.) WHAT TO DO NEXT 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-6 Before Upgrading the OpenVMS Alpha Operating System Backing Up the System Disk _________________________________________________________________ Backing Up the System Disk INTRODUCTION Digital 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.) HOW TO BACK UP THE SYSTEM DISK To back up the system disk, do the following: 1. Shut down the system (described in Appendix A). 2. Boot the operating system CD-ROM (locally or from the InfoServer). 3. Use the menu system to enter the DCL environment (option 4.) 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 5 from the menu. 8. Boot from the system disk. FOR MORE INFORMATION 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. Before Upgrading the OpenVMS Alpha Operating System 5-7 Preparing the System Disk _________________________________________________________________ Preparing the System Disk INTRODUCTION 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 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 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 because 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. 5-8 Before Upgrading the OpenVMS Alpha Operating System Preparing the System Disk 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 alerting you to that fact 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 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 WHAT TO DO NEXT Continue the preupgrade tasks as follows, depending on whether you are upgrading in a standalone or VMScluster environment: Before Upgrading the OpenVMS Alpha Operating System 5-9 Preparing the System Disk ___________________________________________________________ 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 a do the following: VMScluster system, 1. Review the checklist at the end of this chapter. 2. Go to Chapter 6. ___________________________________________________________ 5-10 Before Upgrading the OpenVMS Alpha Operating System Preupgrade Checklist _________________________________________________________________ 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. < 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 a VMScluster system, go to Chapter 6. If you are not upgrading a VMScluster system, go to Chapter 7 to begin the upgrade procedure. Before Upgrading the OpenVMS Alpha Operating System 5-11 6 _________________________________________________________________ Preparing to Upgrade in a VMScluster Environment Preparing to Upgrade in a VMScluster Environment 6-1 Overview _________________________________________________________________ Overview This chapter describes how to prepare to upgrade in a VMScluster 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 VMScluster system. 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. ADDING A NEW SYSTEM TO THE CLUSTER If you need to add a new computer supported by OpenVMS Alpha Version 7.0 to an existing VMScluster configuration, Digital supports two options, listed in the following preferred order: 1. Upgrade the entire cluster to Version 7.0 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 the OpenVMS Alpha operating system, you must upgrade a system disk in the cluster to OpenVMS Alpha Version 7.0 using the rolling upgrade procedure and then boot the new computer into the cluster using that upgraded system disk. 6-2 Preparing to Upgrade in a VMScluster Environment Overview FOR MORE INFORMATION When you upgrade the operating system in a VMScluster environment, be sure the following sources of information are available for you to review: o The cover letters and the software product descriptions included with your distribution kit o The OpenVMS Version 7.0 Release Notes o VMScluster Systems for OpenVMS o Guidelines for VMScluster Configurations o OpenVMS Version 7.0 New Features Manual Preparing to Upgrade in a VMScluster Environment 6-3 Concurrent Upgrade _________________________________________________________________ Concurrent Upgrade INTRODUCTION This section describes the following: o How a concurrent upgrade works o Notes and restrictions o Tasks you need to perform to prepare your system for a concurrent upgrade. 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. NOTES AND RESTRICTIONS Before performing a concurrent upgrade, note the following: o For OpenVMS Alpha Version 7.0 concurrent upgrades, all nodes in the cluster must be running at least OpenVMS Alpha Version 6.1. o If all Alpha systems in the VMScluster environment are booted from one system disk, you must perform a concurrent upgrade. PREPARING FOR A CONCURRENT UPGRADE To prepare for a concurrent upgrade, use the following procedure: 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 6-4 Preparing to Upgrade in a VMScluster Environment Concurrent Upgrade 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, select the disk on which you already performed the preupgrade tasks and then go to Chapter 7 to begin the upgrade procedure. After the upgrade is complete, you will be instructed to reboot each computer in the VMScluster environment before beginning other postupgrade procedures. ____________________ [1] For more information about halting your Alpha computer, see Appendix A. Preparing to Upgrade in a VMScluster Environment 6-5 Rolling Upgrade _________________________________________________________________ Rolling Upgrade INTRODUCTION This section describes the following: o How a rolling upgrade works o Notes and restrictions o Tasks you need to perform to prepare your system for a rolling upgrade. HOW A ROLLING UPGRADE WORKS During a rolling upgrade, you upgrade each system disk individually, allowing old and new versions of the operating system to run together in the same cluster, 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). NOTES AND RESTRICTIONS Before performing a rolling upgrade, note the following: o During a rolling upgrade you must ensure that: - The upgraded system does not attempt to access any disk that is being accessed by one or more of the remaining VMScluster systems. - The remaining VMScluster 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 VMScluster systems. (The OpenVMS system booted from the operating system CD-ROM does not MSCP serve local disks.) Whenever possible, Digital recommends that you perform the upgrade on a local disk or that you perform a concurrent upgrade. 6-6 Preparing to Upgrade in a VMScluster Environment Rolling 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 VMScluster members. o Digital supports rolling upgrades on Alpha computers that belong to a mixed-architecture VMScluster containing VAX computers running Versions 7.0, 6.1, 6.0, or 5.5-2 of the OpenVMS VAX operating system. o Digital 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 queueing 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. PREPARING FOR A ROLLING UPGRADE To prepare for a rolling upgrade follow these steps: 1. Log in to any node where the 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. (VMScluster Systems for OpenVMS describes this procedure in detail.) Preparing to Upgrade in a VMScluster Environment 6-7 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: 6-8 Preparing to Upgrade in a VMScluster Environment 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. Preparing to Upgrade in a VMScluster Environment 6-9 7 _________________________________________________________________ Upgrading the OpenVMS Alpha Operating System Upgrading the OpenVMS Alpha Operating System 7-1 Overview _________________________________________________________________ Overview INTRODUCTION This chapter describes the following tasks: o Beginning the upgrade from the operating system CD-ROM or from a running system 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-2 Upgrading the OpenVMS Alpha Operating System Upgrading from CD-ROM or from a Running System _________________________________________________________________ Upgrading from CD-ROM or from a Running System INTRODUCTION The OpenVMS Alpha Version 7.0 operating system includes procedures that allow you to easily upgrade the operating system using the POLYCENTER Software Installation utility. In console mode, you can boot the operating system CD-ROM to begin the upgrade procedure. On a system that is already running the OpenVMS Alpha Version 7.0 operating system, you can invoke the upgrade procedure by entering a command at the DCL level. HOW TO BEGIN Depending on whether you are upgrading the OpenVMS Alpha operating system from the operating system CD-ROM or from a running OpenVMS Alpha Version 7.0 system, begin the procedure as follows: ___________________________________________________________ If upgrading from ... Then ... the operating go to the section titled Booting the system CD-ROM, Operating System CD-ROM a running Version go to the section titled Performing 7.0_system, the Upgrade Upgrading the OpenVMS Alpha Operating System 7-3 Booting the Operating System CD-ROM _________________________________________________________________ Booting the Operating System CD-ROM INTRODUCTION 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. BOOTING FROM THE LOCAL DRIVE 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 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 -FI APB_070 lan-device-name Note the following conventions: o APB_070 is the file name of the APB program used for the initial system load (ISL) boot program. 7-4 Upgrading the OpenVMS Alpha Operating System Booting the Operating System CD-ROM 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. ________________________________________________________ Ethernet FDDI Alpha_Computer_____________Device________Device_________ AlphaServer 1000 series ERA0, EWA0 FRA0 AlphaServer 2000 series ERA0, EWA0 FRA0 AlphaServer 2100 series ERA0, EWA0 FRA0 AlphaServer 8200 series EXA0, EWA0 FXA0 AlphaServer 8400 series EXA0, EWA0 FXA0 AlphaStation 200 series EWA0 - AlphaStation 400 series EWA0 - AlphaStation 600 series ERA0, EWA0 - DEC 2000 series ERA0 - DEC 3000 series ESA0 "n/ESA0" DEC 4000 series EZA0 - DEC 7000 series EXA0 FXA0 DEC 10000 series EXA0 FXA0 Notes: If you are using a DEC 3000 or 4000 series system, note the following: o On DEC 3000 series systems, you can boot through the InfoServer 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 the section titled Booting Over the Network with an Alternate TURBOchannel Adapter, in Appendix A. Upgrading the OpenVMS Alpha Operating System 7-5 Booting the Operating System CD-ROM o On DEC 4000 series, you must specify the ISL file name in uppercase (APB_070). In addition, if your system uses console firmware prior to Version 3.2, enter the BOOT command as follows: >>> BOOT -FL 0,0 -start 0 -FI APB_070 EZA0 2. The InfoServer ISL program then displays the following menu: Network Initial System Load Function Version 1.1 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 (ALPHA070). 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: ALPHA070 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-6 Upgrading the OpenVMS Alpha Operating System Booting the Operating System CD-ROM 1. Reboot the OpenVMS Alpha operating system CD-ROM. 2. Enter the DCL environment by choosing option 2 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. Upgrading the OpenVMS Alpha Operating System 7-7 Performing the Upgrade _________________________________________________________________ Performing the Upgrade 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 Alpha (TM) Operating System, Version 7.0 Copyright (c) 1995 Digital Equipment 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) Install or upgrade OpenVMS Alpha Version V7.0 2) List layered product kits that this procedure can install 3) Install or upgrade layered product(s) 4) Execute DCL commands and procedures 5) Shut down this system Enter CHOICE or ? to repeat menu: (1/2/3/4/5/?) 1 After you choose the upgrade option, go to the section titled Choosing INITIALIZE or PRESERVE to continue the procedure. 7-8 Upgrading the OpenVMS Alpha Operating System Performing the Upgrade UPGRADING FROM A RUNNING SYSTEM If you are performing an upgrade from an Alpha system that is already running Version 7.0 of the OpenVMS Alpha operating system, enter the following command from the SYSTEM account and then press the Return key: $ @SYS$SYSTEM:AXPVMS$PCSI_INSTALL After you enter the command, go to the section titled Choosing INITIALIZE or PRESERVE to continue the procedure. 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.0 system), 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) 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 install OpenVMS Alpha on an existing 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). Upgrading the OpenVMS Alpha Operating System 7-9 Performing the Upgrade 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) DKA200 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 (_)). After you select the volume label, the target disk is mounted and page and swap files are created. For example: DKA200: is now labeled AXPVMSSYS. Do you want to keep this label? (Yes/No) [Yes] OpenVMS Alpha will be upgraded on DKA200:. UPDATING TIME ZONE INFORMATION At this point in the upgrade, the procedure asks you for information that is used for providing local time zone support. For local time zone support to work correctly, the upgrade 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. You begin by selecting the desired time zone from the main time zone menu, which is the first menu displayed. If you do not select a time zone, the default is Greenwich Mean Time (GMT). 7-10 Upgrading the OpenVMS Alpha Operating System Performing the Upgrade 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. A sample display follows: 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 describes 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]: Upgrading the OpenVMS Alpha Operating System 7-11 Performing the Upgrade 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 repects 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): NO Enter the Time Differential Factor: -5 NEW SYSTEM TIME DIFFERENTIAL FACTOR = -5:00. Is this correct? [Y]: For more information about TDF and local time zone support, see the OpenVMS Version 7.0 New Features Manual. Also, see the section in the OpenVMS System Manager's Manual entitled "Customizing the System to Compensate for Different Time Zones". CHOOSING DESCRIPTIVE HELP TEXT The system next 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. 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: 7-12 Upgrading the OpenVMS Alpha Operating System Performing the Upgrade The following product has been selected: DEC AXPVMS VMS V7.0 [Available] *** DEC AXPVMS VMS V7.0: VMS Operating System, Version V7.0 COPYRIGHT (c) 29-DEC-1995 -- All rights reserved Digital Equipment Corporation Do you want all the default values for this product? [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 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 how you did so in 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 re-enter the values. Notes: When selecting components, note the following as well: o Whether you choose all the default values or select individual files, the system will give you the opportunity to view your selections and make changes (if necessary). Upgrading the OpenVMS Alpha Operating System 7-13 Performing the Upgrade o If you are not sure whether you want certain files, request help by entering a question mark (?) at the prompt for that file (or group of files). o If you plan to install the separate DECwindows Motif for OpenVMS Alpha layered product, you must install the DECwindows base support and workstation support (to run windowing software on Alpha workstations or in a VMScluster that includes workstations or Xterminals) included with the OpenVMS Alpha operating system. 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 files you want installed on your system, you can use the POLYCENTER Software Installation utility on your running system to add or remove files. 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 ($). COMPLETING THE UPGRADE When you have answered all the prompts and selected the components you want installed, the system gives you the opportunity to review your selections (and make changes if necessary) and then displays messages about the following: o The amount of space on the disk required for the upgrade, based on the components you have chosen. (If your disk does not have enough space to perform the upgrade, the system displays a message alerting you to that fact and allows you to terminate the upgrade.) o (Optional) Notification that DECnet/OSI networking software has been upgraded (only if an older version already exists on your system). 7-14 Upgrading the OpenVMS Alpha Operating System Performing the Upgrade o Notification that the upgrade has been completed. o Information about running AUTOGEN. o The menu. Following is a sample display. Notes: If you are upgrading from a running OpenVMS Alpha Version 7.0 system, the system displays the dollar sign prompt ($) instead of the 5-option menu when the upgrade is complete. In this example, the DECnet/OSI software (DEC AXPVMS DECNET_OSI V7.0) is upgraded after the OpenVMS Alpha operating system (DEC AXPVMS DECNET_OSI V7.0) upgrade completes. However, if you do not have existing DECnet/OSI software installed on your system, there can be no DECnet/OSI upgrade. In that case, the system does not display any DECnet/OSI product messages. Do you want to view the values? [NO] %PCSIUI-I-DONEASK, execution phase starting The following product will be installed: DEC AXPVMS VMS V7.0 %PCSI-I-VOLINFO, estimated space information for volume DISK$AXPVMSSYS -PCSI-I-VOLSPC, 40 required; 185469 available; 185429 net Portion Done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% The following product has been installed: DEC AXPVMS VMS V7.0 The following product has been selected: DEC AXPVMS DECNET_OSI V7.0 *** DEC AXPVMS DECNET_OSI V7.0: DECnet/OSI V7.0 for OpenVMS AXP Copyright © Digital Equipment Corporation 1995. All rights reserved. Digital Equipment Corporation This product requires one of two PAKs: DVNETEND or DVNETEXT. Do you want all the default values for this product? [YES] Do you want to view the values? [NO] Upgrading the OpenVMS Alpha Operating System 7-15 Performing the Upgrade Execution phase starting ... The following product will be installed: DEC AXPVMS DECNET_OSI V7.0 The following product will be removed: DEC AXPVMS DECNET_OSI V6.0 %PCSI-I-VOLINFO, estimated space information for volume DISK$AXPVMSSYS -PCSI-I-VOLSPC, 78915 required; 185429 available; 106514 net Portion done: 0%...10%...20%...30%...40%...50%...80%...90%...100% The following product has been installed: DEC AXPVMS DECNET_OSI V7.0 The following product has been removed: DEC AXPVMS DECNET_OSI V6.0 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 can shut down now or continue with other operations. Process AXPVMS_INSTALL logged out at 29-DEC-1995 13:21:07.90 **************************************************************** 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.0 2) List layered product kits that this procedure can install 3) Install or upgrade layered product(s) 4) Execute DCL commands and procedures 5) Shut down this system 7-16 Upgrading the OpenVMS Alpha Operating System Performing the Upgrade WHAT TO DO NEXT If you want to install layered products, including the DECwindows Motif for OpenVMS layered product, go to the next section. If you do not want to 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 (5) from the menu. 2. Go to the section titled What to Do After the Shutdown. Upgrading the OpenVMS Alpha Operating System 7-17 Installing Layered Products _________________________________________________________________ Installing Layered Products INTRODUCTION 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.) HOW TO INSTALL To install layered products using the POLYCENTER Software Installation utility, choose option 2 to view the list and then option 3. For example: Please choose one of the following: 1) Install or upgrade OpenVMS Alpha Version V7.0 2) List layered product kits that this procedure can install 3) Install or upgrade layered product(s) 4) Execute DCL commands and procedures 5) Shut down this system Enter CHOICE or ? to repeat menu: (1/2/3/4/5/?) 2 The following layered product kits are available on the OpenVMS operating system CD-ROM and can be installed at this time: DEC AXPVMS AMDS V6.1 found in DKB400:[KITS.AMDS061] DEC AXPVMS DWMOTIF V1.2-3 found in DKB400:[KITS.DWMOTIF] DEC AXPVMS POSIX V2.0 found in DKB400:[KITS.POSIX] DEC AXPVMS SOFTWIN V1.0 found in DKB400:[KITS.SOFTWINDOWS] DEC AXPVMS SWXCR V2.0 found in DKB400:[KITS.SWXCR$KIT] **************************************************************** 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-18 Upgrading the OpenVMS Alpha Operating System Installing Layered Products 1) Install or upgrade OpenVMS Alpha Version V7.0 2) List layered product kits that this procedure can install 3) Install or upgrade layered product(s) 4) Execute DCL commands and procedures 5) Shut down this system Enter CHOICE or ? to repeat menu: (1/2/3/4/5/?) 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. o If you are upgrading to 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. You must enter the device name for the target disk on which the layered product(s) will be installed. Enter device name for target disk: (? for choices) DKA200 DKA200: is labeled AXPVMSSYS. 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 AMDS V6.1 2 - DEC AXPVMS DWMOTIF V1.2-3 3 - DEC AXPVMS POSIX V2.0 4 - DEC AXPVMS SOFTWIN V1.0 5 - DEC AXPVMS SWXCR V2.0 6 - All products listed above 7 - Exit Desired Product(s): 2 The following product has been selected: DEC AXPVMS DWMOTIF V1.2-3 Do you want to continue? [YES] Upgrading the OpenVMS Alpha Operating System 7-19 Installing Layered Products *** DEC AXPVMS DWMOTIF V1.2-3: DECwindows Motif V1.2-3 for OpenVMS Alpha Copyright Digital Equipment Corporation 1988, 1995. All rights reserved. Digital Equipment Corporation This product uses the PAK: DW-MOTIF Do you want all the default values for this product? [YES] no DECwindows Motif runtime support files [YES] Programming Support (C Language) [YES] Fortran programming support [YES] PASCAL programming support [YES] Programming examples [YES] Translated Image Support (OSF/Motif V1.1.3) [NO] Do you want to view the values? [NO] no %PCSIUI-I-DONEASK, execution phase starting The following product will be installed: DEC AXPVMS DWMOTIF V1.2-3 %PCSI-I-VOLINFO, estimated space information for volume DISK$AXPVMSSYS -PCSI-I-VOLSPC, 96117 required; 478119 available; 382002 net Portion Done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% The following product has been installed: DEC AXPVMS DWMOTIF V1.2-3 The installation is now complete. Process AXPVMS_INST_LP logged out at 29-DEC-1995 12:14:27.54 **************************************************************** 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-20 Upgrading the OpenVMS Alpha Operating System Installing Layered Products 1) Install or upgrade OpenVMS Alpha Version V7.0 2) List layered product kits that this procedure can install 3) Install or upgrade layered product(s) 4) Execute DCL commands and procedures 5) Shut down this system If you do not want to perform any other operations prior to booting the upgraded disk, do the following: 1. Shut down the system by choosing the shutdown option (5) from the menu. 2. Go to the next section to perform specific tasks after the system shuts down. Upgrading the OpenVMS Alpha Operating System 7-21 What to Do After the Shutdown _________________________________________________________________ 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. STANDALONE UPGRADE If you are upgrading a standalone system, do the following: 1. Reboot the system. 2. Log in to the system. 3. Go to Chapter 8 to perform additional postupgrade procedures. CONCURRENT VMSCLUSTER UPGRADE If you are performing a concurrent upgrade in a VMScluster environment, do the following: ___________________________________________________________ IF_...________________THEN_..._____________________________ you have one system do the following: disk, 1. Reboot each system that uses the upgraded disk. 2. Go to Chapter 8. 7-22 Upgrading the OpenVMS Alpha Operating System 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. ___________________________________________________________ ROLLING VMSCLUSTER UPGRADE If you are performing a rolling upgrade in a VMScluster environment, do the following: 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.) Upgrading the OpenVMS Alpha Operating System 7-23 8 _________________________________________________________________ After Upgrading the OpenVMS Alpha Operating System After Upgrading the OpenVMS Alpha Operating System 8-1 Overview _________________________________________________________________ Overview 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 Re-forming 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 the system libraries o Testing the system with UETP o Adding and removing 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 Using the postupgrade checklist 8-2 After Upgrading the OpenVMS Alpha Operating System Re-Forming the Shadow Set _________________________________________________________________ Re-Forming the Shadow Set INTRODUCTION If you have upgraded a disk in a volume shadowing environment, you must now re-form the shadow set. Follow the procedure described in this section. HOW TO ADD SHADOW SET MEMBERS Re-form 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 DSA54: Mounted 0 SHADOWDISK 918150 100 1 $11$DKB100: (NODE1) Online 0 SCRATCH $11$DKB200: (NODE1) ShadowSetMember 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 re-form 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. After Upgrading the OpenVMS Alpha Operating System 8-3 Re-Forming the Shadow Set EXAMPLE The following is an example of re-forming a shadow set: $ MOUNT/CONFIRM/SYSTEM DSA54: /SHADOW=($11$DKB200:,$11$DKB100:) ALPHA070 %MOUNT-F-SHDWCOPYREQ, shadow copy required Virtual Unit - DSA54 Volume label ALPHA070 Member Volume label Owner UIC $11$DKB100: (NODE1) SCRATCH [100,100] Allow FULL shadow copy on the above member(s)? [N]: YES 8-4 After Upgrading the OpenVMS Alpha Operating System Registering New Licenses _________________________________________________________________ Registering New Licenses INTRODUCTION 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 MORE INFORMATION For information about registering licenses, see the following: o The section titled Registering Licenses in Chapter 3 o Appendix C o The OpenVMS License Management Utility Manual After Upgrading the OpenVMS Alpha Operating System 8-5 Examining the AUTOGEN Report File _________________________________________________________________ Examining the AUTOGEN Report File INTRODUCTION 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. INTERPRETING THE 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. 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-6 After Upgrading the OpenVMS Alpha Operating System Modifying the System Parameters File _________________________________________________________________ Modifying the System Parameters File INTRODUCTION 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. Modify the parameters in the new file as necessary. The following two sections are examples of instances where you need to modify parameters in MODPARAMS.DAT. SYSTEM FILE SIZES AUTOGEN sets the following files at sizes appropriate for your system: [SYSEXE]SYSDUMP.DMP [SYSEXE]PAGEFILE.SYS [SYSEXE]SWAPFILE.SYS 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 After Upgrading the OpenVMS Alpha Operating System 8-7 Modifying the System Parameters File VMSCLUSTER PARAMETERS If you are upgrading a VMScluster system, note the following: o You must update the MODPARAMS.DAT file for each Alpha computer that boots from the system disk. 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. 8-8 After Upgrading the OpenVMS Alpha Operating System Examining Your Command Procedures _________________________________________________________________ Examining Your Command Procedures INTRODUCTION This section describes how the upgrade procedure affects command procedures. SITE-SPECIFIC FILES 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 provides 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. After Upgrading the OpenVMS Alpha Operating System 8-9 Decompressing the System Libraries _________________________________________________________________ Decompressing the System Libraries INTRODUCTION 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. 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. 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. 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 8-10 After Upgrading the OpenVMS Alpha Operating System Decompressing the System Libraries The resulting display is similar to the following: VMS Library Decompression Utility Options: 1 HELPLIB.HLB 12 EDTHELP.HLB 22 EVE$KEYHELP.HLB 2 STARLET.OLB 13 NCPHELP.HLB 23 UAFHELP.HLB 3 ACLEDT.HLB 14 SDA.HLB 24 LIB.MLB 4 ANLRMSHLP.HLB 15 SHWCLHELP.HLB 25 STARLET.MLB 5 DBG$HELP.HLB 16 SYSGEN.HLB 26 STARLETSD.TLB 6 DISKQUOTA.HLB 17 ANALAUDIT$HELP 27 DECC$RTLDEF.TLB 7 EDFHLP.HLB 18 SYSMANHELP.HLB 28 VAXCCURSE.OLB 8 INSTALHLP.HLB 19 TFF$TFUHELP.HLB 29 VAXCRTL.OLB 9 LATCP$HELP.HLB 20 TPUHELP.HLB 30 VAXCRTLD.OLB 10 MAILHELP.HLB 21 EVE$HELP.HLB 31 VAXCRTLT.OLB 11 MNRHELP.HLB or 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. (Decompressing all libraries takes approximately one-half hour.) 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 After Upgrading the OpenVMS Alpha Operating System 8-11 Decompressing the System Libraries USING LIBDECOMP.COM IN BATCH You can also execute LIBDECOMP.COM in batch mode to 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-12 After Upgrading the OpenVMS Alpha Operating System Testing the System with UETP _________________________________________________________________ Testing the System with UETP INTRODUCTION Run the User Environment Test Package (UETP) to verify that the upgrade completed correctly. FOR MORE INFORMATION For instructions on running UETP, see the OpenVMS System Manager's Manual. After Upgrading the OpenVMS Alpha Operating System 8-13 Adding and Removing Files _________________________________________________________________ Adding and Removing Files INTRODUCTION If you decide after the installation to change which OpenVMS Alpha operating system files you want installed on your system, you can use the POLYCENTER Software Installation utility on your running system to add or remove files. Note that you can obtain information about individual system files by entering HELP SYSTEM_FILES at the dollar sign prompt ($). HOW TO ADD AND REMOVE FILES To add or remove operating system files, use the DCL command PRODUCT RECONFIGURE VMS. Note that you will need the OpenVMS Alpha operating system CD-ROM. FOR MORE INFORMATION For more information about using the POLYCENTER Software Installation utility to add or remove files, see the OpenVMS System Manager's Manual. 8-14 After Upgrading the OpenVMS Alpha Operating System Preparing to Use OpenVMS Management Station _________________________________________________________________ Preparing to Use OpenVMS Management Station INTRODUCTION 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 Creating installation media for PC client software o Installing the client software on your PC o Defining DECnet nodes FOR MORE INFORMATION For complete information about preparing your OpenVMS system and your PC to run the OpenVMS Management Station server and client software, see Appendix D. REMOVING FILES Note that after you complete the tasks described in Appendix D, which include transferring the client software files from your system to two floppy diskettes, you can then remove those files from your system to save disk space. (Use the PRODUCT RECONFIGURE command rather than a delete operation.) After Upgrading the OpenVMS Alpha Operating System 8-15 Installing Layered Products _________________________________________________________________ Installing Layered Products INTRODUCTION Except in certain instances, you should not have to reinstall layered products that you had on your system prior to the upgrade. However, if you need to install layered products, follow the directions in this section. PROCEDURE 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 upgrade procedure, you can do so using the following procedure. 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 5 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. 8-16 After Upgrading the OpenVMS Alpha Operating System Installing Layered Products 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] 3. To install layered products that require VMSINSTAL (indicated in the directories by saveset file names with file types of .A, .B, and so on), enter the @SYS$UPDATE:VMSINSTAL command and then specify the CD-ROM device and directory. For example: $ @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 or the Motif interface to the POLYCENTER Software Installation utility 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] DECWINDOWS SUPPORT The DECwindows components provided with the OpenVMS Alpha Version 7.0 operating system supply only DECwindows base support and workstation support files. If you do not already have the separate DECwindows Motif for OpenVMS Alpha layered product installed on your system, you must install that product to get full DECwindows support. After Upgrading the OpenVMS Alpha Operating System 8-17 Installing Layered Products MONITORING PERFORMANCE HISTORY The OpenVMS Alpha Version 7.0 operating system CD-ROM also includes a Monitoring Performance History (MPH) kit located in the [MPH] directory. See the OpenVMS AXP Version 6.1 Release Notes for more information about installing and using this optional software. ADDITIONAL NOTES Note the following: o For additional information about installing layered products, see the OpenVMS System Manager's Manual. o Be sure you back up the system disk after you install all your layered products. 8-18 After Upgrading the OpenVMS Alpha Operating System Backing Up the Customized System Disk _________________________________________________________________ Backing Up the Customized System Disk INTRODUCTION 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. HOW TO BACK UP THE CUSTOMIZED SYSTEM DISK To back up the system disk, use the following procedure. 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 4). 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 5 from the menu. 8. Boot from the system disk. FOR MORE INFORMATION 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. After Upgrading the OpenVMS Alpha Operating System 8-19 Rebooting Cluster Members _________________________________________________________________ Rebooting Cluster Members INTRODUCTION If you are performing a rolling upgrade in a VMScluster 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 For more information about booting your system, see Appendix A. 8-20 After Upgrading the OpenVMS Alpha Operating System Running AUTOGEN _________________________________________________________________ Running AUTOGEN INTRODUCTION Although AUTOGEN runs automatically at the end of the upgrade procedure, Digital recommends that you run AUTOGEN periodically after you perform an upgrade. This section describes how often you should run AUTOGEN and what it does. RUNNING AFTER THE UPGRADE After 24 hours of operation, run AUTOGEN in FEEDBACK mode and reboot the system. Run AUTOGEN in this way again two workdays later. RUNNING WEEKLY AUTOGEN sets the values of system parameters and the sizes of the page and swap files according to the system's work load. Digital 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 For more information about the MODPARAMS.DAT file and about using AUTOGEN in general, see the OpenVMS System Manager's Manual. After Upgrading the OpenVMS Alpha Operating System 8-21 Postupgrade Checklist _________________________________________________________________ Postupgrade Checklist Use the following checklist to make sure you have performed all the necessary tasks: < In a volume shadowing environment, re-form 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.0 operating system. < 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 a VMScluster environment). < Run AUTOGEN. 8-22 After Upgrading the OpenVMS Alpha Operating System A _________________________________________________________________ Halt, Boot, and Shutdown Procedures Halt, Boot, and Shutdown Procedures A-1 Overview _________________________________________________________________ Overview 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 A-2 Halt, Boot, and Shutdown Procedures _________________________________________________________________ Booting Operations Halt, Boot, and Shutdown Procedures A-3 Booting the Operating System CD-ROM _________________________________________________________________ Booting the Operating System CD-ROM INTRODUCTION 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. 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-4 Halt, Boot, and Shutdown Procedures Booting the Operating System CD-ROM 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 -FL 0,0 -FI APB_061 lan-device-name Note the following conventions: o APB_061 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. ________________________________________________________ Ethernet FDDI Alpha_Computer_____________Device________Device_________ AlphaServer 1000 series ERA0, EWA0 FRA0 AlphaServer 2000 series ERA0, EWA0 FRA0 AlphaServer 2100 series ERA0, EWA0 FRA0 AlphaServer 8200 series EXA0, EWA0 FXA0 AlphaServer 8400 series EXA0, EWA0 FXA0 AlphaStation 200 series EWA0 - AlphaStation 400 series EWA0 - AlphaStation 600 series ERA0, EWA0 - DEC 2000 series ERA0 - DEC 3000 series ESA0 "n/ESA0" DEC 4000 series EZA0 - DEC 7000 series EXA0 FXA0 DEC 10000 series EXA0 FXA0 Halt, Boot, and Shutdown Procedures A-5 Booting the Operating System CD-ROM Notes: If you are using a DEC 3000 or 4000 series system, note the following: o On DEC 3000 series systems, you can boot through the InfoServer 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 the section titled Booting Over the Network with an Alternate TURBOchannel Adapter in Appendix A. o On DEC 4000 series, you must specify the ISL file name in uppercase (APB_F70). In addition, if your system uses console firmware prior to Version 3.2, enter the BOOT command as follows: >>> BOOT -FL 0,0 -start 0 -FI APB_F70 EZA0 2. The InfoServer ISL program then displays the following menu: Network Initial System Load Function Version 1.1 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 (ALPHAF70). A-6 Halt, Boot, and Shutdown Procedures Booting the Operating System CD-ROM 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: ALPHAF70 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. Halt, Boot, and Shutdown Procedures A-7 Booting Manually from the System Disk _________________________________________________________________ Booting Manually from the System Disk INTRODUCTION This section describes how to manually boot the OpenVMS Alpha operating system from the system disk. HOW TO BOOT MANUALLY 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.[1] 5. Enter the BOOT command in the following format: BOOT device-name ____________________ [1] See the section titled Halting the System for more information about how to halt your Alpha computer. A-8 Halt, Boot, and Shutdown Procedures Booting Manually from the System Disk 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 To boot from the network, enter the following command and press the Return key: >>> BOOT ESA0 Halt, Boot, and Shutdown Procedures A-9 Performing a Conversational Boot _________________________________________________________________ Performing a Conversational Boot INTRODUCTION 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 HOW TO PERFORM A CONVERSATIONAL BOOT 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 A-10 Halt, Boot, and Shutdown Procedures Performing a Conversational Boot 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.[1] 5. To begin the conversational boot, enter the BOOT command in the following format: BOOT -FL 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 -FL 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. ____________________ [1]See the section titled Halting the System for more information about how to halt your Alpha computer. Halt, Boot, and Shutdown Procedures A-11 Performing a Conversational Boot 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. 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 MORE INFORMATION For examples of using conversational booting, see the sections titled Booting with Minimum Startup and Booting in an Emergency. A-12 Halt, Boot, and Shutdown Procedures Booting with Minimum Startup _________________________________________________________________ Booting with Minimum Startup INTRODUCTION 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. HOW TO BOOT WITH MINIMUM STARTUP Boot the system with minimum startup as follows: 1. Perform a conversational boot by entering the following command at the console prompt: >>> BOOT -FL 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 Halt, Boot, and Shutdown Procedures A-13 Booting with the XDelta Utility (XDELTA) _________________________________________________________________ Booting with the XDelta Utility (XDELTA) INTRODUCTION The XDelta utility (XDELTA) is a debugging tool that system programmers use. The procedure for booting all Alpha computers with XDELTA is the same. BOOT COMMAND QUALIFIER VALUES 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. 6 Includes XDELTA and takes the initial breakpoint. 7 Includes XDELTA, displays the SYSBOOT prompt, and takes the initial breakpoint at system initialization. HOW TO BOOT WITH XDELTA The following is an example of booting with XDELTA from the console prompt: >>> BOOT -FL 0,7 A-14 Halt, Boot, and Shutdown Procedures Booting with the XDelta Utility (XDELTA) FOR MORE INFORMATION For more information about using XDELTA, see the OpenVMS Delta/XDelta Debugger Manual. Halt, Boot, and Shutdown Procedures A-15 Booting from a Different Directory _________________________________________________________________ Booting from a Different Directory INTRODUCTION By default, the OpenVMS Alpha operating system is installed in the system root directory named [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.) HOW TO BOOT FROM A DIFFERENT DIRECTORY To boot from a different directory (for example, [SYS3]), enter the BOOT command as follows: >>> BOOT -FL 3,0 DKA200 A-16 Halt, Boot, and Shutdown Procedures Booting with a PMAZB or PMAZC TURBOchannel Adapter _________________________________________________________________ Booting with a PMAZB or PMAZC TURBOchannel Adapter INTRODUCTION 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. 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. DISPLAYING DEVICES 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. Halt, Boot, and Shutdown Procedures A-17 Booting with a PMAZB or PMAZC TURBOchannel Adapter HOW TO BOOT To boot from a device connected to a PMAZB or PMAZC adapter, enter the boot command as follows: >>> BOOT "X/DKYzzz" In the example, the following conventions are used: - X is the TURBOchannel slot number in which the PMAZB or PMAZC adapter is installed - DK is the device code of the boot device - Y is either A or B, depending on the SCSI port of the PMAZB or PMAZC adapter that contains the boot device - zzz is the SCSI unit number of the boot device HOW ADAPTERS ARE IDENTIFIED 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 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-18 Halt, Boot, and Shutdown Procedures Booting Over the Network with an Alternate TURBOchannel Adapter _________________________________________________________________ Booting Over the Network with an Alternate TURBOchannel Adapter INTRODUCTION 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 VMScluster environment. Examples of alternate TURBOchannel adapters are the PMAD (which connects to the Ethernet) and the DEFTA (which connects to the FDDI). HOW TO BOOT 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.47-80800101/OSF PAL X1.34-80800201 - Built on 18-DEC-1995 11:376 Halt, Boot, and Shutdown Procedures A-19 Booting Over the Network with an Alternate TURBOchannel Adapter 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-20 Halt, Boot, and Shutdown Procedures Booting in an Emergency _________________________________________________________________ Booting in an Emergency INTRODUCTION 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 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.[1] The default values allow you to boot the system temporarily so you can correct the problem. ____________________ [1] In most cases, Digital 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. Halt, Boot, and Shutdown Procedures A-21 Booting in an Emergency The_Procedure 1. Perform a conversational boot by entering the following command at the console prompt: >>> BOOT -FL 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. 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-22 Halt, Boot, and Shutdown Procedures Booting in an Emergency 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 Digital 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. The Procedure 1. Perform a conversational boot by entering the following command at the console prompt: >>> BOOT -FL 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. 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: Halt, Boot, and Shutdown Procedures A-23 Booting in an Emergency $ 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 BOOTING WITHOUT THE USER AUTHORIZATION FILE Ordinarily, the startup and login procedures provided by Digital 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. A-24 Halt, Boot, and Shutdown Procedures Booting in an Emergency 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. Halt, Boot, and Shutdown Procedures A-25 Booting in an Emergency 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 The process name is usually the name of the device on which you logged in (for example, _OPA0:). The_Procedure 1. Perform a conversational boot by entering the following command at the console prompt: >>> BOOT -FL 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. A-26 Halt, Boot, and Shutdown Procedures Booting in an Emergency 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, Digital 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. 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 Halt, Boot, and Shutdown Procedures A-27 Booting in an Emergency 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-28 Halt, Boot, and Shutdown Procedures _________________________________________________________________ Set, Show, and Writeboot Operations Halt, Boot, and Shutdown Procedures A-29 Setting the System for Automatic Booting _________________________________________________________________ Setting the System for Automatic Booting INTRODUCTION The 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. The section titled Setting and Showing Boot Devices describes how to change the default boot device. WHEN SYSTEMS CAN BOOT AUTOMATICALLY 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 HOW TO SET THE SYSTEM 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 A-30 Halt, Boot, and Shutdown Procedures Setting the System for Automatic Booting 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.[1] 5. If you have an SMP system with multiple CPUs, enter the following command at the console prompt (>>>) to stop the other CPUs: >>> INITIALIZE 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, Digital 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. ____________________ [1]See the section titled Halting the System for more information about how to halt your Alpha computer. Halt, Boot, and Shutdown Procedures A-31 Setting and Showing Boot Devices _________________________________________________________________ Setting and Showing Boot Devices INTRODUCTION 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, Digital recommends that you set the operating system boot parameters as well, using the SET BOOT_OSFLAGS command. SETTING THE BOOT DEVICE 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 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. SHOWING THE BOOT DEVICE Use the SHOW BOOTDEF_DEV command to find out what drive was specified in the last SET BOOT command. For example: >>> SHOW BOOTDEF_DEV A-32 Halt, Boot, and Shutdown Procedures Setting and Showing Boot Devices CANCELLING THE BOOT DEVICE 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. Halt, Boot, and Shutdown Procedures A-33 Setting Boot Parameters _________________________________________________________________ Setting Boot Parameters INTRODUCTION 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. LIST OF VALID PARAMETERS The following is a list of values you can specify with the SET BOOT_OSFLAGS command: ___________________________________________________________ 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. A-34 Halt, Boot, and Shutdown Procedures Setting Boot Parameters HOW TO ENTER THE SET BOOT_OSFLAGS COMMAND 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 Halt, Boot, and Shutdown Procedures A-35 Setting Boot Parameters 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 VMScluster configuration) to boot from the [SYS1] directory (instead of [SYS0]) when you enter the BOOT command: >>> SET BOOT_OSFLAGS 1,0 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 DISPLAYING PARAMETERS To display the parameters you have just set, use the SHOW BOOT_OSFLAGS command. For example: >>> SHOW BOOT_OSFLAGS BOOT_OSFLAGS = 0,20007 A-36 Halt, Boot, and Shutdown Procedures Using the Writeboot Utility _________________________________________________________________ Using the Writeboot Utility INTRODUCTION 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.) INVOKING WRITEBOOT 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): 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. Halt, Boot, and Shutdown Procedures A-37 _________________________________________________________________ Halt and Shutdown Operations Halt, Boot, and Shutdown Procedures A-39 Halting the System _________________________________________________________________ Halting the System INTRODUCTION 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. HOW TO HALT YOUR ALPHA COMPUTER The following table summarizes the ways you can halt specific Alpha computers: ___________________________________________________________ Alpha_Computer________How_to_Halt__________________________ AlphaServer 1000, Do one of the following: 2000, 2100 series o Press the Halt button. o Press Ctrl/P. AlphaServer 8200, Press Ctrl/P. 8400 series AlphaStation 200, Do one of the following: 400, 600 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 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). A-40 Halt, Boot, and Shutdown Procedures Halting the System ___________________________________________________________ Alpha_Computer________How_to_Halt__________________________ 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 Halt, Boot, and Shutdown Procedures A-41 Shutting Down the System _________________________________________________________________ Shutting Down the System INTRODUCTION 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 the section titled Setting the System for Automatic Booting. ORDERLY SHUTDOWN The SHUTDOWN.COM procedure shuts down the system while performing maintenance functions such as disabling future logins, stopping the batch and printer queues, 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. 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 A-42 Halt, Boot, and Shutdown Procedures Shutting Down the System For more information about the OPCCRASH program, see the OpenVMS System Manager's Manual. 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.[1] 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. ____________________ [1] See the section titled Halting the System for more information about how to halt your Alpha computer. Halt, Boot, and Shutdown Procedures A-43 Shutting Down the System 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-44 Halt, Boot, and Shutdown Procedures _________________________________________________________________ Troubleshooting Procedures Halt, Boot, and Shutdown Procedures A-45 If the System Does Not Boot _________________________________________________________________ If the System Does Not Boot INTRODUCTION 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. FOR HARDWARE PROBLEMS If you suspect a hardware problem, do the following: 1. Consult the hardware manual for your Alpha computer. 2. Contact Multivendor Customer Services. 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-DEC-1995 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-46 Halt, Boot, and Shutdown Procedures Detecting and Responding to System Problems _________________________________________________________________ Detecting and Responding to System Problems INTRODUCTION 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 the section titled Booting Manually from the System Disk, or let it reboot automatically as explained in the section titled Setting the System for Automatic Booting. 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. DETECTING SYSTEM PROBLEMS To determine if the failure is a system problem, do the following: 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.) Halt, Boot, and Shutdown Procedures A-47 Detecting and Responding to System Problems o Make sure the cable connecting the terminal or monitor to the system is secure. HOW TO RESPOND If you determine that you have a system problem, do the following: 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.[1] 3. Note in detail the sequence of events that caused the problem and notify Multivendor Customer Services. ____________________ [1] See the section titled Halting the System for more information about how to halt your Alpha computer. A-48 Halt, Boot, and Shutdown Procedures B _________________________________________________________________ Backing Up and Restoring the System Disk Backing Up and Restoring the System Disk B-1 Overview _________________________________________________________________ Overview This appendix describes how to perform backup and restore operations on the system disk. You perform these tasks by entering commands from a specialized, restricted backup environment that you access 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. 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. 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. B-2 Backing Up and Restoring the System Disk Overview 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. SUGGESTED PROCEDURES Digital 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 the sections titled Backing Up the System Disk and Restoring the System Disk. However, if you do not have access to the compact disk or if you want to back up a shadowed system disk without disabling the shadow set, you can use a different procedure, described in the section titled Alternate Backup and Restore Procedure. o Store the backup media in a safe place. o If you have a VMScluster 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. VMSCLUSTER 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. Backing Up and Restoring the System Disk B-3 Overview 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, Digital recommends that you shut down the entire VMScluster system before you back up your system disk. B-4 Backing Up and Restoring the System Disk Backing Up the System Disk _________________________________________________________________ Backing Up the System Disk GETTING STARTED Before you back up the system disk, do the following: 1. In a VMScluster 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 (4) from the menu. For example: **************************************************************** You can install or upgrade the OpenVMS Alpha operating system. 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.0 2) List layered product kits that this procedure can install 3) Install or upgrade layered product(s) 4) Execute DCL commands and procedures 5) Shut down this system Enter CHOICE or ? to repeat menu: (1/2/3/?) 4 5. 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). Backing Up and Restoring the System Disk B-5 Backing Up the System Disk 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. 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: (You must also include the save set name and the /SAVE_SET qualifier if the target drive is a tape device.) EXAMPLES In this example the system disk and a target disk 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: 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-6 Backing Up and Restoring the System Disk Backing Up the System Disk CHANGING THE CLUSTER_SIZE PARAMETER The BACKUP command creates a system disk that includes a set of volume parameters provided by Digital, 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. WHAT TO DO NEXT After you complete the backup operation, do the following: 1. Enter the LOGOUT command to exit from the DCL environment and return to the menu. 2. Choose the shutdown option (5). 3. After the shutdown completes, boot from the system disk. Backing Up and Restoring the System Disk B-7 Restoring the System Disk _________________________________________________________________ Restoring the System Disk GETTING STARTED Before you can restore the system disk, you must do the following: 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 (4) from the menu. For example: **************************************************************** You can install or upgrade the OpenVMS Alpha operating system. 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.0 2) List layered product kits that this procedure can install 3) Install or upgrade layered product(s) 4) Execute DCL commands and procedures 5) Shut down this system Enter CHOICE or ? to repeat menu: (1/2/3/?) 4 4. At the triple dollar sign prompt ($$$), enter the SHOW DEVICES command. 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-8 Backing Up and Restoring the System Disk Restoring the System Disk 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. 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.) EXAMPLES 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: 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-9 Restoring the System Disk WHAT TO DO NEXT After you complete the restore operation, do the following: 1. Enter the LOGOUT command to exit from the DCL environment and return to the menu. 2. Choose the shutdown option (5). 3. After the shutdown completes, boot from the system disk. B-10 Backing Up and Restoring the System Disk Alternate Backup and Restore Procedure _________________________________________________________________ Alternate Backup and Restore Procedure INTRODUCTION 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 it 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, Digital recommends that if you must use an alternate method to backup or restore the system disk, you use the method described in this section. PREPARING AN ALTERNATE DISK Prepare an alternate 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. Backing Up and Restoring the System Disk B-11 Alternate Backup and Restore Procedure 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 VMS V7.0: VMS Operating System, Version V7.0 COPYRIGHT © (c) 21-DEC-1995 -- All rights reserved Digital Equipment Corporation %PCSIUI-I-DONEASK, execution phase starting The following product will be installed: DEC AXPVMS VMS V7.0 %PCSI-I-VOLINFO, estimated space information for volume DISK$MINAlpha -PCSI-I-VOLSPC, -1 required; 741063 available; 741064 net Portion Done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% The following product has been installed: DEC AXPVMS VMS V7.0 . . . 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.) B-12 Backing Up and Restoring the System Disk Alternate Backup and Restore Procedure Caution: If your system is a cluster member, Digital recommends that you shut down the entire VMScluster 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. USING THE ALTERNATE DISK Use the alternate 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 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 messages about licenses, which are similar to the following: %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: Digital 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. Backing Up and Restoring the System Disk B-13 Alternate Backup and Restore Procedure 4. Mount the system disk and any output devices you plan to use during the backup or restore operations. 5. Perform the necessary backup and restore operations by entering the appropriate BACKUP commands. 6. Shut down the system. 7. Boot from your original system disk. B-14 Backing Up and Restoring the System Disk C _________________________________________________________________ License Management Supplement License Management Supplement C-1 Overview _________________________________________________________________ Overview 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 Digital Equipment Corporation that contains the appropriate information to authorize access to software on an Alpha computer (or in a VMScluster environment). You can obtain a PAK from a Multivendor Customer Services representative in the same way as you obtain software. 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. 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 C-2 License Management Supplement Overview 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 AlphaServer 1000 4/233 15 1050 AlphaServer 2000 4/233 (1 CPU) 400 1100 AlphaServer 2000 4/233 (2 CPU) 500 1100 AlphaServer 2000 4/275 (1 CPU) 400 1100 AlphaServer 2000 4/275 (2 CPU) 500 1100 AlphaServer 2100 4/233 (1 CPU) 400 1100 AlphaServer 2100 4/233 (2 CPU) 500 1100 AlphaServer 2100 4/233 (3 CPU) 600 1100 AlphaServer 2100 4/233 (4 CPU) 700 1100 AlphaServer 2100 5/250 (1 CPU) 400 1100 AlphaServer 2100 5/250 (2 CPU) 500 1100 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 Overview Table C-1 (Cont.) License Unit Requirement Table (LURT) System Marketing Model A H AlphaServer 2100 5/250 (3 CPU) 600 1100 AlphaServer 2100 5/250 (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 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-4 License Management Supplement Overview Table C-1 (Cont.) License Unit Requirement Table (LURT) System Marketing Model A H AlphaServer 8400 (12 CPU) 2600 1150 AlphaStation 200 4/100 12 1050 AlphaStation 200 4/133 12 1050 AlphaStation 200 4/266 12 1050 AlphaStation 250 4/266 12 1050 AlphaStation 400 4/233 12 1050 AlphaStation 600 4/233 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 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-5 Overview Table C-1 (Cont.) License Unit Requirement Table (LURT) System Marketing Model A H 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-6 License Management Supplement License Management Facility (LMF) Notes _________________________________________________________________ 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 Digital 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-7 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. 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, Digital 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 - DISABLE - ENABLE C-8 License Management Supplement License Management Facility (LMF) Notes - 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-9 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. FOR MORE INFORMATION For additional license information, see the release notes and the OpenVMS License Management Utility Manual. C-10 License Management Supplement D _________________________________________________________________ Preparing to Use OpenVMS Management Station Preparing to Use OpenVMS Management Station D-1 Overview _________________________________________________________________ Overview INTRODUCTION This appendix describes how to prepare your OpenVMS system and your PC to run the OpenVMS Management Station server and client software. The information provided includes the following: o Preliminary procedures, including the following: - Editing system files - Starting OpenVMS Management Station on other nodes - Verifying that you have the proper memory, disk space, media, and the required software to install and run OpenVMS Management Station on your PC - Creating installation media for PC client software o Installing the client software on your PC o Defining DECnet nodes o Accessing online help o PATHWORKS installation tips and guidelines REQUIRED FILES During the OpenVMS Version 7.0 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 Version 7.0 operating system CD-ROM and the DCL command PRODUCT RECONFIGURE VMS to add the OpenVMS Management Station files to your system. D-2 Preparing to Use OpenVMS Management Station Overview CHECKLIST Use the following checklist as a guide to verify that you perform the required tasks described in this appendix: < Be sure the optional OpenVMS Management Station client software files are installed on your OpenVMS system. < Edit the system startup and shutdown files on your OpenVMS system to start the OpenVMS Management Station server. < Start OpenVMS Management Station on OpenVMS nodes within the cluster that you have configured with failover mechanisms. < Be sure that your PC has at least 8 MB of random-access memory (RAM) and 6 MB of free disk space and that you have two 3-1/2 inch, high-density floppy diskettes. < Be sure that your PC is running MS-DOS Version 5.0 or later and Microsoft Windows Version 3.1 or Microsoft Windows for Workgroups Version 3.11. < Be sure your PC is running PATHWORKS Version 5.0A (or Version 5.1) for DOS and Windows client software and that the PATHWORKS file PWSOCK.DLL is available to your PC. (If necessary, refer to the section titled PATHWORKS Installation Tips and Guidelines.) < Create the PC installation media (on two floppy diskettes) containing the OpenVMS Management Station client software. < Install the OpenVMS Management Station client software on your PC. < After installing the client software on your PC, define the DECnet node names and network addresses of primary- server OpenVMS systems that you want to manage. < Access online help to get started using OpenVMS Management Station. Preparing to Use OpenVMS Management Station D-3 _________________________________________________________________ Preparing Your Systems Preparing to Use OpenVMS Management Station D-5 Preparing Your OpenVMS System _________________________________________________________________ Preparing Your OpenVMS System INTRODUCTION During the OpenVMS Version 7.0 installation or upgrade procedure, the OpenVMS Management Station server files are automatically installed on your OpenVMS system disk. After the installation or upgrade is complete, 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. This section includes the following information: o A list of the OpenVMS Management Station files installed on your OpenVMS system. o A procedure for editing the system files to enable automatic startup and shutdown of OpenVMS Management Station o A procedure for starting OpenVMS Management Station on other nodes in a VMScluster FILES INSTALLED ON OPENVMS The files installed on your OpenVMS system disk following the OpenVMS Version 7.0 installation or upgrade procedure are as follows: o SYS$SYSTEM:TNT$SERVER.EXE o SYS$STARTUP:TNT$STARTUP.COM o SYS$STARTUP:TNT$SHUTDOWN.COM o SYS$TEST:TNT$IVP.COM o SYS$COMMON:[SYSTEST.TNT]TNT$SERVER_IVP.EXE o SYS$HELP:TNT010.RELEASE_NOTES This file is created when the server is started: o SYS$COMMON:[SYSEXE]TNT$UADB.DAT D-6 Preparing to Use OpenVMS Management Station Preparing Your OpenVMS System These client software files are installed on your OpenVMS system during the installation or upgrade procedure as well (or when you later add those files to the system using the DCL command PRODUCT RECONFIGURE VMS). These files allow you to create the PC installation media (using the procedure described later in the section titled Preparing Your PC). Note that after you successfully transfer these client software files from your OpenVMS Alpha system to floppy diskettes and install that software on your PC, you can then remove those files from your OpenVMS Alpha system to save disk space. (Use the PRODUCT RECONFIGURE command rather than a delete operation.) o SYS$COMMON:[TNT.CLIENT]DISKIMAG.EXE o SYS$COMMON:[TNT.CLIENT]TNTCLID1.IMG o SYS$COMMON:[TNT.CLIENT]TNTCLID2.IMG EDITING SYSTEM FILES You must edit the system startup and shutdown files on your OpenVMS system to provide for automatic startup and shutdown of OpenVMS Management Station when your system is rebooted. To edit the files, follow these steps: Preparing to Use OpenVMS Management Station D-7 Preparing Your OpenVMS System ___________________________________________________________ Step_____Action____________________________________________ 1 Add the command line that starts OpenVMS Management Station to the system startup file, SYS$MANAGER:SYSTARTUP_VMS.COM. The following example shows the network startup command line followed by the OpenVMS Management Station startup command line: $ @SYS$MANAGER:STARTNET.COM . . . $ @SYS$STARTUP:TNT$STARTUP.COM Note: OpenVMS Management Station cannot start until after the network has started. Therefore, you must position this new command line after the line that invokes the network startup command procedure. 2 Add the following command line to the system shutdown file, SYS$MANAGER:SYSHUTDWN.COM: $ @SYS$STARTUP:TNT$SHUTDOWN.COM STARTING OPENVMS MANAGEMENT STATION ON OTHER NODES If you plan to run OpenVMS Management Station on more than one node in a VMScluster without rebooting, you must start the software on those nodes by entering the following command from the SYSTEM account: $ @SYS$STARTUP:TNT$STARTUP.COM If you are performing an upgrade or an installation and OpenVMS Management Station is already running on your cluster, add the RESTART parameter to the startup command, as follows: $ @SYS$STARTUP:TNT$STARTUP.COM RESTART D-8 Preparing to Use OpenVMS Management Station Preparing Your PC _________________________________________________________________ Preparing Your PC INTRODUCTION During the OpenVMS Version 7.0 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 RECONFIGURE VMS). 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 Preliminary tasks and requirements o A procedure for creating installation media from the client software installed on the OpenVMS system disk REQUIRED MEMORY AND DISK SPACE Your PC requires 8 MB of random-access memory (RAM) and 6 MB of free disk space to install the OpenVMS Management Station client software. To determine the amount of memory available on your PC, enter the following command at the MS-DOS prompt: C:\> mem To determine the amount of available free disk space, you can enter the following command at the MS-DOS prompt: C:\> dir MEDIA You need two 3-1/2, inch high-density floppy diskettes, which have to be formatted. You will use those diskettes to create the PC installation media. Preparing to Use OpenVMS Management Station D-9 Preparing Your PC REQUIRED SOFTWARE Table D-1 describes the software that must be installed on your PC before installing OpenVMS Management Station. Table D-1 Prerequisite and Optional Software Prerequisite_Products______Purpose_________________________ MS-DOS Version 5.0 or Operating system later Microsoft Windows Version Windowing capability 3.1 or Microsoft Windows for Workgroups Version 3.11 PATHWORKS V5.0A for DOS ManageWORKS user interface and and Windows (or V5.1) network transport client software PATHWORKS CLIENT REQUIREMENTS Note the following PATHWORKS client requirements: o Your system must be configured for DECnet. o If you have any version of the PATHWORKS client other than Version 5.0A or Version 5.1 installed on your PC, it is not supported by OpenVMS Management Station. Refer to the section titled PATHWORKS Installation Tips and Guidelines to help you quickly install the PATHWORKS Version 5.0A for DOS and Windows (or Version 5.1) client software. o OpenVMS Management Station requires that the PATHWORKS file PWSOCK.DLL be available to your PC. PWSOCK.DLL is installed as part of the Socket Library Files option of the PATHWORKS Network Utilities component. The error message "Cannot Find PWSOCK.DLL" is displayed when you run OpenVMS Management Station if PWSOCK.DLL is not available to your system. D-10 Preparing to Use OpenVMS Management Station Preparing Your PC Refer to the section titled PATHWORKS Installation Tips and Guidelines for instructions on how to configure the Socket Library Files option to make the PWSOCK.DLL file available (see the subsection titled Configuring Using Windows). CREATING THE INSTALLATION MEDIA Create the PC installation media using the following steps. 1. Open an MS-DOS window on your PC. 2. At the MS-DOS prompt, use the NFT utility on the PC to copy the files to a temporary directory on your PC from the OpenVMS system on which you have installed the OpenVMS Management Station software. Enter the following command at the prompt (C:\>) : NFT COPY /BLOCK node"username password"::SYS$COMMON:[TNT.CLIENT]*.* \temp-dir where node, username, and password are the access control information for an account on the OpenVMS system, and temp-dir is the name of the temporary directory. Note: If a DECnet node is not defined in your PC network database, refer to the section titled Defining DECnet Nodes. 3. Insert a formatted floppy disk in the 3-1/2 inch floppy disk drive (A in this example). At the MS-DOS prompt, type the following MS-DOS command: C:\> \temp-dir\DISKIMAG \temp-dir\TNTCLID1.IMG a: where temp-dir is the temporary directory used in step 2. When the DISKIMAG program returns to the MS-DOS prompt, remove the floppy disk and label it "Disk 1-Setup". 4. Insert a formatted floppy disk in the 3-1/2 inch floppy disk drive. At the MS-DOS prompt, type the following command: C:\> \temp-dir\DISKIMAG \temp-dir\TNTCLID2.IMG a: where temp-dir is the temporary directory used in step 2. Preparing to Use OpenVMS Management Station D-11 Preparing Your PC When the DISKIMAG program returns to the MS-DOS prompt, remove the floppy disk and label it "Disk 2." 5. You can delete the files DISKIMAG.EXE, TNTCLID1.IMG, and TNTCLID2.IMG from temp-dir after creating the floppy disks. You can now proceed with the installation of the OpenVMS Management Station PC client software. D-12 Preparing to Use OpenVMS Management Station _________________________________________________________________ Installing the OpenVMS Management Station Client Software on Your PC Preparing to Use OpenVMS Management Station D-13 Overview _________________________________________________________________ Overview This section provides the following information: o How to install the OpenVMS Management Station client on a PC o How to recover from errors during the installation o How to define DECnet nodes after the installation o The names of the files that are created on your PC after the installation o How to access online help to get started using OpenVMS Management Station D-14 Preparing to Use OpenVMS Management Station Installing the Client Software _________________________________________________________________ Installing the Client Software INSTALLATION PROCEDURE Follow these steps to install OpenVMS Management Station client on your PC. (Note that this procedure takes about 10 minutes.) ___________________________________________________________ Step________Action_________________________________________ 1 Start your PC as you usually do. 2 Insert disk 1 in your floppy disk drive. 3 Enter the Windows environment and click on the Program Manager icon. 4 In the Menu bar of the Program Manager program group, click on File, and then choose Run from the pull-down menu. Result: The Run dialog box appears. 5 In the Run dialog box, type: a:\SETUP.EXE where a: is the name of the floppy disk drive. 6 Click on the OK button to start the installation. Result: A dialog box containing the message "Initializing setup, please wait..." appears and is then replaced by a window labeled OpenVMS Setup. Preparing to Use OpenVMS Management Station D-15 Installing the Client Software ___________________________________________________________ Step________Action_________________________________________ 7 To proceed with the installation, click on the Continue button. Note: You can stop the installation at any time by clicking on the Exit button. As the installation progresses, the system displays the names of the files as they are copied, and a copy bar indicates what percentage of the installation is done. Also displayed is a reminder to read the OpenVMS Management Station Read Me file for important information. 8 When you are prompted by a dialog box message, remove disk 1 from the disk drive and insert disk 2. Click on OK. Result: When the copy bar shows that that all the files are copied, a dialog box displays a message indicating the installation has completed_successfully. 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 The prerequisite software version is incorrect. o Disk space and memory necessary for successful installation are inadequate. D-16 Preparing to Use OpenVMS Management Station Defining DECnet Nodes _________________________________________________________________ Defining DECnet Nodes INTRODUCTION After installing the client software on your PC, use the MS-DOS Network Control Program (NCP) utility on your PC to define the DECnet node names and network addresses of primary-server OpenVMS systems that you want to manage. OpenVMS Management Station connects your PC to the primary- server system and then routes management operations to the target systems. You can define multiple primary servers. Note: Failure to access the NCP utility from the MS-DOS prompt can result in connection problems. By accessing the NCP utility from the MS-DOS prompt, you define DECnet node names and network addresses in both DECnet Phase IV and DECnet Phase V databases. If you access the NCP utility from Windows, data is defined only in Phase V databases. PROCEDURE FOR DEFINING DECNET NODES Follow these steps to define DECnet nodes: ___________________________________________________________ Step________Action_________________________________________ 1 At the MS-DOS prompt, invoke the NCP utility as follows: C:\> NCP 2 At the NCP> prompt, type the following command: NCP> DEFINE NODE addrs NAME name where addrs is the DECnet address and name is the DECnet node name. Example: NCP> DEFINE NODE 19.208 NAME ISTAR 3 At the NCP prompt, type EXIT and press Return to exit the operation. Preparing to Use OpenVMS Management Station D-17 Defining DECnet Nodes FILES CREATED ON THE PC The following files (with their directory names) are created on your PC when the OpenVMS Management Station client software is installed: o PATHWORKS directory (usually \PW) - VMSACNT.DLL - VMSCLU.DLL - VMSINFRA.DLL - VMSMGMT.DLL - VMSMSCRL.DLL - VMSNODE.DLL - VMSTIMEL.DLL - VMSUAOMM.DLL - ACCOUNT.HLP - DOMAIN.HLP - MANAGE.HLP - README.WRI o Windows directory (usually \WINDOWS) - XTIDNW.DLL - XTILIB.DLL o Window systems directory (usually \WINDOWS\SYSTEM) - CTL3DV2.DLL D-18 Preparing to Use OpenVMS Management Station Getting Started _________________________________________________________________ Getting Started INTRODUCTION 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. ACCESSING ONLINE HELP Follow these steps to access the OpenVMS Management Station online help: ___________________________________________________________ Step_____Action____________________________________________ 1 Open the PATHWORKS Windows Applications program group. 2 Click on the OpenVMS Management Help icon for instructions on how to get started. Preparing to Use OpenVMS Management Station D-19 _________________________________________________________________ PATHWORKS Installation Tips and Guidelines Preparing to Use OpenVMS Management Station D-21 Overview _________________________________________________________________ Overview If you already have the PATHWORKS for DOS and Windows client software installed on your PC, you can disregard this entire section. If you are installing the PATHWORKS for DOS and Windows client software on your PC because the PATHWORKS client software is a requirement for OpenVMS Management Station (that is, you are not using PATHWORKS to manage a local area network of PCs), you may find the following installation tips and guidelines useful. For complete installation instructions and detailed information on PATHWORKS, refer to the PATHWORKS documentation. REQUIRED DISK SPACE PATHWORKS for DOS and Windows client software requirements for free disk space are different during installation and after installation. Files created during installation can later be deleted. Table D-2 summarizes the storage requirements. Table D-2 Disk Space Requirements During Kit Installation After Installation PATHWORKS for Up to 30 MB 7 MB DOS and Windows client ABOUT INSTALLING AND CONFIGURING You use both MS-DOS and Windows to install and configure the PATHWORKS Client software: 1. Install the client software using MS-DOS. 2. After installation, configure the client software using Windows. D-22 Preparing to Use OpenVMS Management Station Installing Using MS-DOS _________________________________________________________________ Installing Using MS-DOS Exit Windows before you begin this installation. 1. The client software installation procedure wants to install the software to the root directory of a "substituted" hard disk. Create a substituted hard drive by typing the following commands at the MS-DOS prompt. Note that the example reflects the PATHWORKS Version 5.0A for DOS and Windows client software; Version 5.1 is also supported. C:\> mkdir c:\pwv50a C:\> subst x: c:\pwv50a where x: is the name of an unused MS-DOS drive. (If you have a single hard disk, G is usually a good choice.) C is the name of a local drive that meets the space requirements. 2. Insert the LAN Manager setup disk in your PC's floppy drive. Then type: a:setup Note that A is the MS-DOS drive letter for the floppy drive. 3. Choose the Install Kit option from the Setup window. 4. To install the software to the substituted hard drive created in step 1 (G: was suggested), choose the appropriate drive from the Select Drive list box. (Scroll through the list box if the drive name is not immediately visible.) Click on OK. 5. When prompted, insert disk 1 into drive A and click on OK. A working dialog box displays the names of the files as they are copied, and a copy gauge indicates what percentage of the installation is done. 6. Insert the LAN Manager setup disk again when you are prompted. Click on the OK button. Preparing to Use OpenVMS Management Station D-23 Installing Using MS-DOS 7. From the PATHWORKS Installation utility window, click on the arrow to the right of the Installing to: option. Select the substituted drive from the displayed list box. 8. From the Install: list box in the PATHWORKS Installation Utility window, you can choose the PATHWORKS client options you want to install. You need only the following options in the Install: list box. DECnet and Utilities ManageWORKS Network Utilities PATHWORKS Tutorial PATHWORKS Windows Network Remove unneeded options from the Install list by clicking on an option, and then clicking on the Remove button to move the selected option to the Do Not Install: list box. 9. Verify your selection of options and click on OK. 10.An Installation Starting dialog box is displayed and you are asked whether you want to go back and read help. Choose NO. 11.When you are prompted, insert the necessary floppy disks to install the software. A working dialog box displays the names of the files as they are copied. 12.When the installation process is complete, you are asked whether you want to configure the Workstation Manager; choose NO. 13.An Installation Complete dialog box displays the following message: Exiting PATHWORKS Installation Utility Click on the OK button. 14.At this point, the installation utility returns to the initial Setup window. Click on the Exit option to quit the PATHWORKS Installation utility. D-24 Preparing to Use OpenVMS Management Station Configuring Using Windows _________________________________________________________________ Configuring Using Windows Use the following steps to configure PATHWORKS client software: 1. Start Windows and choose Run from the File pull-down menu on the Program Manager menu bar. In the Command Line box, type the following: x:\pcapp\pwsetup where x: is the substituted drive that you created in step 1 (G: was suggested). Click on the OK button. This starts the PATHWORKS Configuration utility. 2. Click on the OK button in the Please Enter Software Destination box to signify that the displayed default location is correct. A PATHWORKS Configuration Warning box is displayed. Click on the OK button to indicate that you want to create the default directory. 3. When you are prompted, verify the substituted drive letter you used when you installed the client software under MS-DOS by clicking OK. 4. Choose the Express option from the displayed Select a Configuration Option list box. 5. In the Express: Select a Workstation Template dialog box, choose the highlighted Blank template by clicking on the OK button. 6. In the Customize: Modify Workstation Configuration template, choose only the following items: o PATHWORKS Services o Network Adapter Information Deselect the other items. Then click on the OK button. 7. You are prompted to select the following tasks (those listed in step 4 of the MS-DOS installation procedure): DECnet and Utilities ManageWORKS Preparing to Use OpenVMS Management Station D-25 Configuring Using Windows Network Utilities PATHWORKS Tutorial PATHWORKS Windows Network Click on each option. Then click on the Add button to move each option to the Run on Workstation list box. 8. Choose the DECnet and Utilities option. Then click on the Detail button. 9. From the displayed list box, double-click on the Network File Transfer option. Then click on the OK button. 10.A Customize: Select PATHWORKS Services for Workstation dialog box is displayed. Choose the Network Utilities option, and click on the Detail button. 11.From the displayed list box, double-click on the Socket Library Files option. Then click on the OK button. 12.From the displayed Customize: Select PATHWORKS Services for Workstation dialog box, click on the OK button. 13.Select the Ethernet adapter installed in your PC by clicking on the appropriate adapter description. Then click on OK. 14.When you are prompted, enter the DECnet node name and DECnet network address. Do not enter the server node name and address. Click on OK. 15.In the Enter Windows Directory dialog box, accept the displayed default by clicking on the OK button. 16.In the Customize: Save Template to Disk dialog box, choose a name for the startup template (any string of characters is permitted), along with an optional description. Then click on the Save button. 17.A displayed message asks whether you want to have the network started automatically via an entry in AUTOEXEC.BAT. Select YES. If you start up Windows in AUTOEXEC.BAT, examine AUTOEXEC.BAT after the configuration utility exits to ensure that the call to STARTNET.BAT appears before the WIN command. D-26 Preparing to Use OpenVMS Management Station Configuring Using Windows 18.In the displayed Customize: PROTOCOL.INI Editor dialog box, click on the OK button to accept the default options. A copy gauge displays the progress of the installation. 19.Select the OK option to exit the displayed Customize: Configuration Completed dialog box. 20.Select the Exit option to exit the PATHWORKS Configuration utility. ______________________ Important ______________________ You must exit Windows and restart your computer before you install the OpenVMS Management Station software. ______________________________________________________ Preparing to Use OpenVMS Management Station D-27 Configuring Using Windows STARTING WINDOWS The first time Windows starts after this installation, you see the message: Could not load Windows Network Click on the "Disable this warning" button, and then click on the OK button. DELETING A DIRECTORY Now that you have successfully installed the PATHWORKS Client software and have run the PATHWORKS Configuration utility, you can delete the PWV50A directory, which you created in step 1 when you installed using MS-DOS. D-28 Preparing to Use OpenVMS Management Station _________________________________________________________________ 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. boot server An Alpha computer that is part of a local area VMScluster. 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 VMScluster 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 VMScluster. 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 a VMScluster 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 a VMScluster 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 VMScluster 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 VMScluster 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 for OpenVMS Alpha that downline loads VMScluster satellites using the DECnet Maintenance Operations Protocol. satellite node A computer that is part of a local area VMScluster. 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 VMScluster. 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. 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 for OpenVMS, and the VMScluster environment. Glossary-3 VMScluster environment A computer system consisting of a number of Alpha and VAX computers. There are four types of VMScluster environments: CI only, DSSI only, local area, and mixed-interconnect. Glossary-4 _________________________________________________________________ Index A Alpha computers (cont'd) _______________________________ booting with PMAZC Accounts TURBOchannel adapter, creating after installation, A-17 4-4 booting with XDELTA, A-14 setting up after an cancelling boot device, A-33 installation, 4-6 halting, A-40 Adding files performing conversational after installation, 4-14 boot, A-10 after upgrade, 8-14 setting boot device, A-32 AGEN$PARAMS.REPORT, 4-22 setting boot parameters, Allocation class A-34 See also ALLOCLASS parameter setting for automatic booting determining, 2-3 , A-30 ALLOCLASS parameter, 2-3 showing boot device, A-32 supplying during VMScluster shutting down, A-42 installation, 3-36 troubleshooting procedures, Alpha computers A-47 booting failure, A-46 ANALYZE/CRASH command, A-44 booting from a different ANALYZE/DISK_STRUCTURE utility directory, A-16 error message, 5-8 booting in an emergency, using before an upgrade, 5-8 A-21 APB.EXE booting with minimum startup, and Writeboot utility, A-37 A-13 AUTOGEN, 4-22 booting with PMAD running after an installation TURBOchannel adapter, , 4-22 A-20 running after an upgrade, booting with PMAZB 8-21 TURBOchannel adapter, running at end of A-17 installation, 3-38 Index-1 Booting problems B______________________________ fixing by booting with Backing up the system disk, default parameter values, 1-8, 4-19, 5-7, 8-19, A-4, A-21 A-7, B-2 Bugcheck, A-47 in a shadow set, B-11 without booting the CD-ROM, C______________________________ B-11 Checklist BACKUP command, B-3 postinstallation, 4-24 Boot block postupgrade, 8-22, D-3 writing, A-37 preupgrade, 5-11 Boot command Cluster group number qualifiers for XDELTA, A-14 rules for creating, 2-5 Booting Cluster password automatic, A-30 rules for creating, 2-5 cancelling boot device, A-33 Cluster upgrades conversational, A-10 See Concurrent upgrades; failure, A-46 Rolling upgrades; Upgrade from a different directory, procedure A-16 CLUSTER_SIZE parameter, B-7 from the InfoServer, 3-7, Command procedures 7-4, A-5 checking after upgrade, 8-9 in an emergency, A-21 Concurrent upgrades with default system required operating system parameters, A-21 version, 6-4 without startup and login restrictions, 6-4 procedures, A-23 CONTINUE command, A-11 without the User Crash commands, A-43 Authorization File, Creating a system disk, 3-11 A-24 Ctrl/T, A-47 setting boot device, A-32 Customizing the system, 4-6 setting boot parameters, A-34 D______________________________ showing boot device, A-32 DEC 3000 Alpha computers with alternate TURBOchannel booting over the network, adapter, A-20 A-19 with minimum startup, A-13 booting with alternate with PMAZB TURBOchannel, TURBOchannel adapter, A-17 A-20 with PMAZC TURBOchannel, booting with PMAZB A-17 TURBOchannel adapter, with XDELTA, A-14 A-17 Index-2 DEC 3000 Alpha computers Emergency system startup (cont'd) (cont'd) booting with PMAZC without startup and login TURBOchannel adapter, procedures, A-23 A-17 without the UAF, A-24 DECnet for OpenVMS Alpha Errors configuring after an cluster hang during installation, 4-7 preupgrade shutdown, 6-9 ignoring during startup, 4-7 running ANALYZE/DISK_ registering license after STRUCTURE, 5-8 installation, 4-3 EXPECTED_VOTES running with DECwindows, 4-7 parameter, 8-7 DECnet node address, 2-3 providing during installation F______________________________ , 3-35 Factory installed software DECnet node name, 2-3 (FIS), xiii possible values, 3-35 FIELD account providing during installation creating after installation, , 3-35 4-4 DECnet/OSI Files upgrade, 7-14 adding Decompressing system libraries after installation, 4-14 , 4-10, 8-10 after upgrade, 8-14 DECW$IGNORE_DECNET logical removing name, 4-8 after installation, 4-14 Default system parameters after upgrade, 8-14 booting with, A-21 Disk space H______________________________ amount needed for upgrade, Halting the system, A-40 5-9 Hardware amount needed to decompress supported, D-9 libraries, 8-10 Hardware problem amount needed to decompress diagnosing, A-46 system libraries, 4-10 HSx device Dump file definition, 1-2 checking size, 8-7 specifying, 3-33 modifying size, 8-6 E I______________________________ _______________________________ InfoServer Editing startup files, 4-6 booting, 3-7, 7-4, A-5 Emergency system startup losing connection, 3-10, 7-6 with default system parameters, A-21 Index-3 INITIALIZE command, A-31 Libraries Installation decompressing after an See also Postinstallation installation, 4-10 tasks, Preinstallation LICENSE (License Management tasks utility) booting system disk after example of registration, C-2 transferring required save license registration set, 3-33 procedure, C-2 information needed for using during installation, VMScluster, 2-2 3-23 of layered products, 3-29, License Management Facility 4-16, 7-18 (LMF), C-7 rebooting system, 3-40 restrictions, C-8, C-9 recording, 1-4 License Unit Requirement Table registering licenses, 3-21 (LURT), C-2 registering OpenVMS Alpha Licenses license, 3-40 See also Product running AUTOGEN, 3-38 Authorization Key (PAK) setting passwords, 3-14 registering after an upgrade, specifying VMScluster 8-5 configuration, 3-35 registering after stages of, 3-2 installation, 4-3 using the POLYCENTER Software registering during Installation utility, 1-8 installation, 3-21 Installation procedure Log time zones, 3-17 for installation, 1-4 Logging in L______________________________ when errors in login Layered products procedures prevent, A-23 effect of upgrade on, 5-4, when errors in startup 8-16 procedures prevent, A-23 installing after OpenVMS when forgotten passwords Alpha installation, 4-16 prevent, A-24 installing during OpenVMS Logical names Alpha installation, 3-29 UAFALTERNATE, A-24 installing during OpenVMS Login command procedures Alpha upgrade, 7-18 booting without, A-23 LIBDECOMP.COM (procedure to when errors prevent you from decompress system libraries) logging in, A-23 , 4-11, 8-10 running after an upgrade, 8-10 Index-4 Password (cont'd) M______________________________ setting during installation, Minimum startup, A-13 3-14 Mixed-architecture cluster, PMAZB TURBOchannel adapter 6-6 booting system, A-17 Mixed-version cluster, 6-2, PMAZC TURBOchannel adapter 6-7 booting system, A-17 MODPARAMS.DAT (parameter file) POLYCENTER Software , 4-22, 8-21 Installation utility modifying for cluster, 8-7 installing the operating modifying for single system, system, 1-8 8-7 upgrading the operating Monitoring Performance History system, 1-8 installing, 4-18, 8-18 Postinstallation tasks, 4-1 adding and removing files, N______________________________ 4-14 NETCONFIG.COM procedure adjusting system parameters, running after an installation 4-6 , 4-7 backing up the system disk, 4-5, 4-19 O configuring DECnet for _______________________________ OpenVMS Alpha, 4-7 OPCCRASH.EXE, A-42 customizing the system, 4-6 OpenVMS Alpha decompressing system license libraries, 4-10 registering during editing startup procedures, installation, 3-21 4-6 save sets installing layered products, transferring to system 4-16 disk, 3-11 preparing to use OpenVMS OpenVMS Management Station Management Station, 4-15 preparing system, 4-15, 8-15 registering licenses, 4-3 Output setting up user accounts, saving from installation, 4-6 1-4 testing the system with the P User Environment Test _______________________________ Package, 4-9 Page file tuning the system with checking size, 8-7 AUTOGEN, 4-22 modifying size, 8-6 Postupgrade tasks Password adding and removing files, forgotten, 3-41, A-24 8-14 minimum length, 3-14 backing up system disk, 8-19 changing MODPARAMS.DAT, 8-7 Index-5 Postupgrade tasks (cont'd) Product Authorization Key checking system file sizes, (PAK) 8-7 registering after an decompressing system installation, 4-3 libraries, 8-10 registering after an upgrade, examining command procedure 8-5 templates, 8-9 registering during an modifying size of dump file, installation, 3-21 8-6 modifying size of page file, Q______________________________ 8-6 Queue database modifying size of swap file, creating, 4-6 8-6 Queue manager preparing to use OpenVMS starting, 4-6 Management Station, 8-15 Quorum registering new licenses, See also VMScluster quorum 8-5 maintaining during rolling running AUTOGEN, 8-21 upgrades, 6-8 running UETP, 8-13 Quorum disk Preinstallation tasks choosing during VMScluster collecting information you installation, 3-37 will need, 3-3 preparing for a VMScluster R______________________________ environment, 2-2 Reboot software and hardware after installation, 3-40 components, 1-4 Recording an installation, 1-4 Preupgrade tasks Removing files analyzing and repairing after installation, 4-14 system disk, 5-8 after upgrade, 8-14 backing up system disk, 5-7 Restoring files on the system preparing system disk, 5-8 disk, 1-8, A-4, A-7 shutting down system, 5-9 Restoring the system disk, B-8 Printer without booting the CD-ROM, recording installation on, B-11 1-4 Restrictions Problems for OpenVMS Alpha upgrade, booting 5-3 fixing by booting with License Management Facility default parameter (LMF), C-8, C-9 values, A-21 Rolling upgrades, 6-6 to 6-9 forgotten password maintaining cluster quorum, fixing by booting without 6-8 the UAF, A-24 required operating system logging in, A-23, A-24 version, 6-6 Index-6 Rolling upgrades (cont'd) SYLOGICALS.COM procedure restrictions, 6-6 editing after an installation , 4-6 S______________________________ SYLOGIN.COM procedure SDA (System Dump Analyzer), editing after an installation A-44 , 4-6 SET AUTO_ACTION command, A-31 SYSBOOT.EXE, A-10 SET BOOTDEF_DEV command, A-32 commands, A-11 SET BOOT_OSFLAGS command, A-34 SYSGEN Setting passwords during an commands for conversational installation, 3-14 boot, A-11 Shadow sets SYSTARTUP_VMS.COM procedure system disk editing after an installation upgrading, 5-5 , 4-6 SHOW BOOTDEF_DEV command, A-32 editing to control DECnet for SHOW CRASH command, A-44 OpenVMS Alpha, 4-7 Shutdown System after installation, 3-40 customizing, 4-6 before an upgrade, 5-10, shutting down before upgrade, 6-4, 6-8 5-9 procedures, A-42 SYSTEM account SHUTDOWN.COM, A-42 forgotten password, 3-41 Site-specific command setting password, 3-14 procedures System disk restored during upgrade, 8-9 adding files Source drive, 1-3, B-6 after installation, 4-14 Startup command procedure after upgrade, 8-14 booting without, A-23 analyzing and repairing, 5-8 when errors prevent you from backing up, 8-19 logging in, A-23 backing up after an Startup files installation, 4-19 editing after an installation backing up before an upgrade, , 4-6 5-7 Swap file booting after installation, checking size, 8-7 3-40 modifying size, 8-6 booting after transferring SWAPFILES.COM procedure required save set, 3-33 executing to change system checking amount of free space file sizes, 8-7 on, 4-10 SYCONFIG.COM procedure creating, 3-11 editing after an installation free space needed for upgrade , 4-6 , 5-9 free space needed to decompress libraries, 4-10 Index-7 System disk (cont'd) Time zones (cont'd) preparing for an OpenVMS updating during an upgrade, Alpha upgrade, 5-8 7-10 removing files Transferring save sets to after installation, 4-14 system disk, 3-11 after upgrade, 8-14 TURBOchannel unique volume label booting with alternate requirement, B-3 adapter, A-20 upgrading, 5-5 booting with PMAZB adapter, System Generation utility A-17 (SYSGEN) booting with PMAZC adapter, ALLOCLASS parameter, 2-3 A-17 commands for conversational TURBOchannel adapter boot, A-11 booting over the network, System hang, A-47 A-19 System parameters booting with default, A-21 U______________________________ UAFALTERNATE, A-26 UAF (User Authorization File) when incorrect values prevent booting with alternate, A-24 the system from booting, returning to the default, A-21 A-26 System startup UAFALTERNATE logical name, in an emergency A-24 with default system UAFALTERNATE system parameter, parameters, A-21 A-26 without startup and login procedures, A-23 UETP without the UAF, A-24 See User Environment Test SYSTEST account Package creating after installation, Upgrade 4-4 See also Postupgrade tasks, SYSUAFALT.DAT file, A-24 Preupgrade tasks, Upgrade procedure T______________________________ cautions and restrictions, Tailoring files 5-3 See Adding files, Removing DECnet/OSI, 7-14 files disk space requirement, 5-9, Target disk 7-14 using backup copy for, 5-7 effect on layered products, Target drive, B-6 5-4 Time zones requirements, 5-11 updating during an shadowed disks, 5-5 installation, 3-17 Index-8 Upgrade procedure VOTES parameter effect on command procedures, checking for rolling upgrades 8-9 , 6-7 effect on MODPARAMS.DAT, 8-7 required operating system W______________________________ version, 5-3, 6-4, 6-6 Writeboot utility, A-37 rolling upgrades Writing a new boot block, A-37 adding a new CPU, 6-2 time zones, 7-10 using the POLYCENTER Software Installation utility, 1-8 User Environment Test Package when to run, 4-9, 8-13 V______________________________ VMScluster building, 4-6 information required for OpenVMS Alpha installation , 2-2 installation questions, 3-35 label for system disk, B-3 VMScluster installation, 3-35 choosing quorum disk, 3-37 configuring the cluster, 3-35 suggested answers to questions, 3-35 supplying ALLOCLASS parameter , 3-36 VMScluster quorum maintaining during rolling upgrades, 6-8 VMScluster upgrades See Concurrent upgrades; Rolling upgrades; Upgrade procedure Volume label definition, 1-5 requirement for VMSclusters, B-3 Volume shadowing backing up the system disk, B-11 Index-9