____________________________________________________ OpenVMS VAX Version 7.1 Upgrade and Installation Manual Order Number: AA-QSBQB-TE November 1996 This manual provides step-by-step instructions for upgrading and installing the OpenVMS VAX operating system. Revision/Update Information: This is a new manual. Operating System and Version: OpenVMS VAX Version 7.1 Digital Equipment Corporation Maynard, Massachusetts ________________________________________________________________ November 1996 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 manor that conserves the environment and protects the safety and health of its employees, customers, and the community. © Digital Equipment Corporation 1996. All rights reserved. The following are trademarks of Digital Equipment Corporation: Bookreader, CDA, CI, DEC, DECdirect, DECdtm, DEC PHIGS, DECnet, DECset, DECterm, DECtp, DECwindows, DEQNA, Digital, Digital UNIX, EDCS, HSC, HSC50, HSC70, InfoServer, LAT, MANAGEWORKS, MicroVAX, MicroVAX II, MUXserver, OpenVMS, OpenVMS Volume Shadowing, PATHWORKS, Q-bus, RX01, RX33, RX50, TK, UETP, ULTRIX, VAX, VAX 4000, VAX 6000, VAX 8200, VAX 8250, VAX 8300, VAX 8350, VAX 8530, VAX 8550, VAX 8600, VAX 9000, VAX-11/730, VAX-11/750, VAX-11/780, VAX-11/785, VAX C, VAXBI, VAXcluster, VAXELN, VAXft, VAXlink, VAXserver, VAXset, VAXstation, VIDA, VMS, VR150, VR160, WPS-PLUS, XMI, XUI, and the DIGITAL logo. The following are third-party trademarks: Adobe, Adobe Illustrator, Display POSTSCRIPT, and POSTSCRIPT are registered trademarks of Adobe Systems Incorporated. Microsoft, MS, and MS-DOS are registered trademarks, and Windows 95 and Windows NT are trademarks of Microsoft Corporation. Motif, OSF, OSF/1, OSF/Motif, and Open Software Foundation are registered trademarks of the Open Software Foundation, Inc. NetView is a registered trademark of International Business Machines Corporation. OSI is a registered trademark of CA Management, Inc. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Limited. X/Open is a trademark of X/Open Company Limited. All other trademarks and registered trademarks are the property of their respective holders. ZK6487 The OpenVMS documentation set is available on CD-ROM. _________________________________________________________________ Contents Preface................................................... xv 1 Overview of Installation and Upgrade Procedures 1.1 Introduction.................................. 1-1 1.2 Important Information......................... 1-1 1.2.1 DECnet-Plus............................... 1-1 1.2.2 DECwindows Motif for OpenVMS-Minimum Version................................... 1-3 1.2.3 MACRO32.EXE and Standalone Backup......... 1-3 1.2.4 Layered Product Availability.............. 1-4 1.2.5 Restrictions.............................. 1-4 1.3 Definitions: A Few Key Terms.................. 1-5 1.4 Locating Files on the Distribution Media...... 1-6 1.4.1 On Magnetic Tape.......................... 1-7 1.4.2 On Tape Cartridges........................ 1-7 1.4.3 On Compact Disc........................... 1-7 1.4.4 DECamds and Monitoring Performance History (MPH) Files............................... 1-8 1.4.5 Software Product Descriptions (SPDs)...... 1-8 1.5 What Happens During an Installation........... 1-9 1.5.1 When to Perform an Installation........... 1-9 1.5.2 How to Use the Installation Documentation............................. 1-10 1.6 What Happens During an Upgrade................ 1-12 1.6.1 When to Perform an Upgrade................ 1-12 1.6.2 How to Use the Upgrade Documentation...... 1-13 1.7 Where to Go Next.............................. 1-13 iii 2 Before Installing OpenVMS VAX Software 2.1 Overview...................................... 2-1 2.2 Cautions and Restrictions..................... 2-1 2.2.1 Cautions.................................. 2-2 2.2.2 Restrictions.............................. 2-2 2.3 Are You Ready to Install?..................... 2-3 2.3.1 Hardware Components....................... 2-3 2.3.2 Software Components....................... 2-3 2.4 Preparing for an Installation................. 2-4 2.4.1 Preparing for a C2 System................. 2-4 2.4.2 Preparing for a VAXcluster Environment.... 2-4 2.4.3 Preparing Tape and Disk Drives............ 2-6 2.4.4 Information You Need During the Installation.............................. 2-7 2.5 Preinstallation Checklist..................... 2-12 3 Installing the OpenVMS VAX Operating System 3.1 Overview...................................... 3-1 3.2 Booting Standalone BACKUP..................... 3-1 3.2.1 Booting from Tape Cartridge............... 3-2 3.2.2 Booting from an InfoServer Device......... 3-2 3.2.3 Booting OpenVMS from the CD-ROM........... 3-4 3.3 Creating the System Disk...................... 3-5 3.3.1 Step 1: Determine Device Names............ 3-5 3.3.2 Step 2: Load Distribution Media........... 3-6 3.3.3 Step 3: Transfer VMS071.B to Your System Disk...................................... 3-6 3.3.4 Step 4: Boot the New System Disk.......... 3-8 3.3.5 Step 5: Specify the Volume Label.......... 3-10 3.3.6 Step 6: Specify the Source Drive.......... 3-10 3.3.7 Step 7: Select Optional OpenVMS Components................................ 3-11 3.3.8 OpenVMS Library Files..................... 3-12 3.3.9 OpenVMS Optional Files.................... 3-13 3.3.10 Help Message Files........................ 3-13 3.3.11 OpenVMS Management Station Files.......... 3-14 3.3.12 Step 8: Choose DECwindows Support Options................................... 3-14 3.3.13 Step 9: Select DECnet Product............. 3-18 3.3.14 Step 10: Verify Your Choices.............. 3-18 3.3.15 Step 11: Install OpenVMS Options.......... 3-18 3.3.16 Compact Disc.............................. 3-19 iv 3.3.17 Tape Cartridges and 9-Track Open Reel Magnetic Tapes............................ 3-19 3.4 Configuring a Cluster......................... 3-20 3.5 Setting Passwords ............................ 3-21 3.6 Entering SCSNODE and SCSSYSTEMID Parameters... 3-23 3.7 Postinstallation Tasks Described.............. 3-24 3.8 Registering Licenses.......................... 3-25 3.8.1 Types of Licenses......................... 3-25 3.8.2 How to Register Your Licenses............. 3-29 3.8.3 How to Register OpenVMS VAX Licenses...... 3-29 3.8.4 How to Register System Integrated Products.................................. 3-31 3.9 Time Zone and Time Differential Factor Information................................... 3-32 3.9.1 Updating Time Zone Information............ 3-32 3.10 Installing DECnet-Plus........................ 3-33 3.11 Running AUTOGEN............................... 3-34 4 After Installing OpenVMS VAX 4.1 Overview...................................... 4-1 4.2 Verifying System Time......................... 4-2 4.3 Registering Your Licenses..................... 4-3 4.3.1 Where to Find More Information............ 4-3 4.4 Backing Up Your System Disk................... 4-3 4.5 Customizing the System........................ 4-3 4.6 Configuring and Starting Networking Software...................................... 4-5 4.6.1 Configuring Your System................... 4-5 4.6.2 Editing SYSTARTUP_VMS..................... 4-5 4.7 Testing the System with UETP Software......... 4-6 4.8 Decompressing System Libraries................ 4-7 4.9 Removing or Adding OpenVMS Files.............. 4-9 4.10 Installing Layered Products................... 4-9 4.10.1 TCP/IP Services for OpenVMS............... 4-9 4.11 Backing Up the Customized System Disk......... 4-10 4.12 Running AUTOGEN............................... 4-10 4.12.1 How AUTOGEN Works......................... 4-10 4.12.2 When to Run AUTOGEN....................... 4-11 4.13 Postinstallation Checklist.................... 4-11 v 5 Before Upgrading OpenVMS VAX Software 5.1 Overview...................................... 5-1 5.2 Cautions and Restrictions..................... 5-1 5.2.1 License Requirements...................... 5-2 5.2.2 DECset Version 11 Debugger................ 5-2 5.2.3 Customized Security Environment........... 5-3 5.2.4 Operator and Accounting Logs.............. 5-4 5.2.5 Special Testing and Debugging Files....... 5-4 5.2.6 Cluster Considerations.................... 5-4 5.2.7 Save Set Location......................... 5-5 5.2.8 System Disk Cautions...................... 5-5 5.2.9 AUTOGEN Feedback Data..................... 5-6 5.2.10 OpenVMS Version Requirements.............. 5-6 5.2.11 DECwindows Motif Version Requirements..... 5-6 5.2.12 Shared System Dump Files.................. 5-6 5.2.13 Layered Products.......................... 5-6 5.3 Are You Ready to Upgrade?..................... 5-7 5.3.1 Hardware Components....................... 5-7 5.3.2 Software Components....................... 5-7 5.4 Examining AUTOGEN Feedback Data............... 5-8 5.4.1 Valid Feedback Data....................... 5-8 5.4.2 How to Test Feedback Data................. 5-8 5.5 Performing Backup Tasks....................... 5-9 5.5.1 How to Back Up the System Disk............ 5-9 5.5.2 How to Back Up Console Media.............. 5-9 5.6 Preparing Your System Disk.................... 5-10 5.6.1 Create a Nonshadowed System Disk.......... 5-11 5.6.2 Boot the Backup Copy of Your System Disk...................................... 5-11 5.6.3 Copy UAF and Auditing Files to the System Disk...................................... 5-11 5.6.4 Rename the System Dump File............... 5-12 5.6.5 Analyze the System Disk................... 5-12 5.6.6 Check Page and Swap Files................. 5-12 5.6.7 Check for Free Blocks..................... 5-13 5.6.8 Check Quotas and Limits................... 5-14 5.6.9 Set System Parameters..................... 5-15 5.6.10 Check AGEN$INCLUDE Files.................. 5-17 5.6.11 Add Modified System Parameters to MODPARAMS.DAT............................. 5-17 5.7 Preparing the System.......................... 5-18 5.7.1 Enable Auto Restart or Manual Reboot...... 5-18 5.7.2 Shut Down and Reboot the System........... 5-18 vi 5.7.3 Prevent Interactive Logins................ 5-18 5.7.4 Check for DECnet.......................... 5-18 5.7.5 Check for Volume Shadowing................ 5-19 5.7.6 Stop Queues............................... 5-20 5.8 Gathering Information for the Upgrade......... 5-20 5.9 Preupgrade Checklist.......................... 5-24 6 Upgrading a VAXcluster Environment 6.1 Overview...................................... 6-1 6.2 Concurrent and Rolling Upgrades............... 6-1 6.2.1 Concurrent Upgrades....................... 6-1 6.2.2 Rolling Upgrades.......................... 6-2 6.3 Performing a Concurrent Upgrade............... 6-2 6.3.1 Concurrent Upgrade Procedure.............. 6-2 6.4 Performing a Rolling Upgrade.................. 6-4 6.4.1 Restrictions.............................. 6-4 6.4.2 Rolling Upgrade Procedure................. 6-5 6.5 Adding an OpenVMS VAX Version 7.1 Supported CPU........................................... 6-7 7 Upgrading the OpenVMS VAX Operating System 7.1 Overview...................................... 7-1 7.2 Preparing to Boot from [SYSF]................. 7-2 7.2.1 Modifying Boot Command Procedures......... 7-2 7.2.2 VAX 8200, 8250, 8300, and 8350 Computers................................. 7-3 7.2.3 Configuring Devices....................... 7-3 7.3 Beginning the Upgrade Procedure............... 7-3 7.3.1 Step 1: Load Distribution Media........... 7-4 7.3.2 Step 2: Upgrading from the InfoServer..... 7-4 7.3.3 Step 3: Start VMSINSTAL................... 7-5 7.3.4 Step 4: Back Up the System Disk........... 7-6 7.3.5 Step 5: Specify the Source Drive.......... 7-6 7.3.6 Step 6: Enter Product Name................ 7-7 7.3.7 Step 7: Mount the First Volume............ 7-7 7.3.8 Step 8: Monitor Messages from VMSINSTAL... 7-8 7.3.9 Step 9: Verify Date and Time.............. 7-8 7.4 Upgrade Phase 1............................... 7-9 7.4.1 Step 1: Specify Type of Upgrade........... 7-9 7.4.2 Step 2: Enter Passwords................... 7-9 7.4.3 Step 3: Choose Boot Method................ 7-11 vii 7.4.4 Step 4: File Cleanup...................... 7-12 7.4.5 Step 5: Select Optional OpenVMS Components................................ 7-13 7.4.6 OpenVMS Library Files..................... 7-14 7.4.7 OpenVMS Optional Files.................... 7-14 7.4.8 Help Message Files........................ 7-14 7.4.9 OpenVMS Management Station Files.......... 7-15 7.4.10 Step 6: Choose DECwindows Support Options................................... 7-16 7.4.11 Step 7: Select Networking Software........ 7-19 7.4.12 Step 8: Verify Your Choices............... 7-19 7.4.13 Step 9: Shut Down Your System............. 7-20 7.4.14 Step 10: Reboot the System................ 7-20 7.4.15 Step 11: Verify System Time............... 7-20 7.5 Upgrade Phase 2............................... 7-21 7.5.1 What the Procedure Does................... 7-22 7.5.2 Mounting Additional Tape Cartridge and 9-Track Open Reel Magnetic Tape Volumes... 7-22 7.6 Upgrade Phase 3............................... 7-23 7.6.1 What the Procedure Does................... 7-23 7.7 Upgrade Phase 4............................... 7-23 7.7.1 What the Procedure Does................... 7-24 7.7.2 What You Do............................... 7-24 7.8 Upgrade Phase 5............................... 7-25 7.9 Upgrade Phase 6............................... 7-25 7.9.1 Restoring System Files.................... 7-25 7.9.2 Registering Licenses...................... 7-26 7.9.3 Updating Time Zone Information............ 7-27 7.9.4 Installing DECnet-Plus.................... 7-28 7.9.5 Running AUTOGEN........................... 7-29 7.9.6 Shutting Down the System.................. 7-29 7.9.7 Booting Voting Nodes...................... 7-30 7.9.8 Executing STARTUP......................... 7-30 7.9.9 Logging In................................ 7-31 8 After Upgrading OpenVMS VAX 8.1 Verifying System Time......................... 8-2 8.2 Restoring the Preferred Node List............. 8-2 8.3 Replacing SYSUAF.DAT and VMS$AUDIT_SERVER.DAT.......................... 8-3 8.4 Examining AGEN$PARAMS.REPORT.................. 8-3 8.5 Checking the Size of System Files............. 8-4 viii 8.6 Examining Your Command Procedures............. 8-4 8.7 Changing MODPARAMS.DAT........................ 8-5 8.8 Updating Your Console Media................... 8-5 8.9 VAX 8530, 8550, 8810 (8700), 8820-N (8800) Computers..................................... 8-5 8.9.1 VAX-11/730, 750, 780, 785 and VAX 8200, 8250, 8300, 8350, 8600, 8650 Computers.... 8-7 8.9.2 VAX 9000 Computers........................ 8-9 8.10 Decompressing the System Libraries............ 8-9 8.10.1 How to Decompress Libraries............... 8-10 8.11 Testing the System with UETP.................. 8-12 8.12 Increasing Free Space on the System Disk...... 8-12 8.12.1 Using VMSTAILOR and DECW$TAILOR........... 8-12 8.12.2 Purging System Files...................... 8-13 8.13 Restoring Your System Password Dictionary..... 8-13 8.14 Customizing DECwindows Support Software....... 8-14 8.15 Preparing to Run the OpenVMS Management Station....................................... 8-14 8.16 Installing Layered Products................... 8-15 8.16.1 TCP/IP Services for OpenVMS............... 8-15 8.17 Backing Up the System Disk.................... 8-16 8.18 Running AUTOGEN............................... 8-16 8.19 Postupgrade Checklist......................... 8-17 9 Customizing DECwindows Support Software 9.1 Overview...................................... 9-1 9.2 Customizing the Server Startup................ 9-1 9.2.1 Assumptions............................... 9-2 9.2.2 How to Override Incorrect Assumptions..... 9-2 9.3 Using Digital TCP/IP Services for OpenVMS..... 9-9 9.4 Using Other Transports with DECwindows........ 9-9 9.4.1 Writing a Transport Interface............. 9-10 9.4.2 Installing the Transport Interface Image..................................... 9-10 9.5 Using the Example Transport................... 9-10 ix 10 Using VMSTAILOR and DECW$TAILOR 10.1 Using VMSTAILOR............................... 10-1 10.1.1 How VMSTAILOR Works....................... 10-1 10.1.2 Removing OpenVMS VAX Files................ 10-3 10.1.3 Adding OpenVMS VAX Files.................. 10-5 10.1.4 Sample Session............................ 10-6 10.2 Using DECW$TAILOR............................. 10-9 10.2.1 How DECW$TAILOR Works..................... 10-10 10.2.2 DECwindows Files You Can Tailor........... 10-10 10.2.3 Removing DECwindows Files................. 10-11 10.2.4 Adding DECwindows Files................... 10-12 10.2.5 Sample Session............................ 10-14 A Multiversion VAX Upgrade Process A.1 Determine Your Path........................... A-1 A.2 Multiversion Upgrade Procedure................ A-2 A.2.1 Before You Begin the Upgrade.............. A-2 A.2.2 Intermediate Upgrade...................... A-3 A.2.3 Final Upgrade............................. A-4 A.3 Specific Layered Product and Firmware Information................................... A-4 A.3.1 Layered Products.......................... A-4 B License Management Notes B.1 Overview...................................... B-1 B.2 Registering Your Licenses..................... B-1 B.2.1 When to Register.......................... B-1 B.2.2 How to Register........................... B-2 B.3 Using the License Unit Requirement Table (LURT)........................................ B-4 B.4 License Management Facility Notes............. B-12 B.5 Volume Shadowing for OpenVMS License.......... B-13 B.5.1 When to Register.......................... B-14 B.5.2 Volume Shadowing Phase I and Phase II..... B-14 B.5.3 Types of Licenses......................... B-14 B.6 Other System Integrated Product Licenses...... B-14 x C Booting from [SYSF] During an Upgrade C.1 Booting Procedures............................ C-1 C.1.1 MicroVAX and VAXstation Computers......... C-1 C.1.2 VAX 8530, 8550, 8810 (8700), 8820-N (8800) Computers................................. C-2 C.1.3 VAX 8820, 8830, and 8840 Computers........ C-2 C.1.4 VAX-11/750, 8200, 8250, 8300, and 8350 Computers................................. C-2 C.1.5 VAX-11/730, 11/780, 11/785, 8600, and 8650 Computers................................. C-4 C.1.6 VAX 6000 Series........................... C-7 C.1.7 VAX 9000 Series........................... C-9 D OpenVMS VAX Save Set Subclasses D.1 Save Set C Subclasses......................... D-1 D.2 Save Set D Subclasses......................... D-3 D.3 Save Set E Subclasses......................... D-3 D.4 Save Set F Subclasses......................... D-3 E DECwindows Display Server and Fonts Components E.1 Table of Components........................... E-1 F NEW_OVER and NEW_UNDER Files F.1 Where Files Are Installed..................... F-1 F.1.1 NEW_OVER Files............................ F-2 F.1.2 NEW_UNDER Files........................... F-3 F.1.3 Site-Specific Files....................... F-3 G Preparing to Use OpenVMS Management Station G.1 Preparing Your OpenVMS System................. G-1 G.1.1 Files Installed on Your OpenVMS System.... G-2 G.1.2 Setting Up in a Mixed-Architecture Cluster Environment............................... G-3 G.1.3 Start the Server on Other Nodes........... G-4 G.1.4 Update the Printer Database............... G-5 G.1.5 Edit the System Files..................... G-5 G.1.6 Allow OpenVMS Management Station to Control the Printer Environment........... G-6 xi G.1.7 Keep Your Printer Environment Up to Date...................................... G-6 G.1.8 When Does TNT$UTILITY.COM Run?............ G-6 G.1.9 Do You Need to Run TNT$UTILITY.COM Manually?................................. G-7 G.1.10 Are There Any Requirements for Running TNT$UTILITY.COM?.......................... G-8 G.1.11 Enabling Disk Quotas...................... G-9 G.1.12 Running Third-Party TCP/IP Stacks......... G-9 G.1.13 Determining and Reporting Problems........ G-9 G.2 Preparing Your PC............................. G-10 G.2.1 Required Memory and Disk Space............ G-10 G.2.2 Required Software......................... G-10 G.2.3 TeamLinks Version 1.0 is Not Supported.... G-11 G.2.4 Creating the Installation Media........... G-12 G.2.5 Installing the OpenVMS Management Station Client Software on Your PC................ G-13 G.2.6 Installation Directory.................... G-13 G.2.7 Installation Procedure.................... G-14 G.2.8 Recovering from Errors.................... G-15 G.2.9 Files Created on the PC................... G-15 G.2.10 After Installing the Client Software on Your PC................................... G-17 G.2.11 Defining TCP/IP Nodes..................... G-17 G.2.12 DECnet Support............................ G-17 G.2.13 Procedure for Defining DECnet Nodes....... G-18 G.2.14 PATHWORKS and Workgroup Administrator Support................................... G-18 G.2.15 POLYCENTER Manager on NetView for Windows NT, Version 3.0........................... G-19 G.3 Getting Started with OpenVMS Management Station....................................... G-19 G.3.1 Accessing Online Help..................... G-19 H Small Capacity System Disks H.1 Overview...................................... H-1 H.2 Limited Space Support......................... H-1 H.2.1 Limited Space Support Option.............. H-2 H.2.2 Configurations Affected................... H-2 H.2.3 Dealing with a Small System Disk.......... H-3 H.3 Tailoring Considerations...................... H-4 H.3.1 Configuration Goals....................... H-4 xii H.3.2 Controlling the Size of Dump, Page, and Swap Files................................ H-5 H.3.3 Make a Backup Copy of Your System Disk.... H-6 H.3.4 Analyze the System Disk................... H-6 H.3.5 Tailoring Options......................... H-6 H.4 Installing OpenVMS VAX and DECwindows Motif... H-7 H.4.1 Install OpenVMS VAX Version 7.1 .......... H-7 H.4.2 Install DECwindows Motif ................. H-8 H.5 Upgrading OpenVMS VAX and DECwindows Motif ... H-10 H.5.1 Upgrading to OpenVMS VAX Version 7.1 ..... H-10 H.6 Managing Single or Small System Disk Systems....................................... H-11 H.6.1 System Dump File.......................... H-11 H.6.2 Using PAGEFILE.SYS for the Dump File...... H-12 H.6.3 Decompressing Libraries................... H-13 H.6.4 Disabling Log File Creation............... H-13 H.6.5 Accessing Example and Documentation Files..................................... H-15 H.7 Managing Multiple Disk Systems................ H-15 H.7.1 Alternate Page and Swap Files............. H-15 H.7.2 Copying Dump Files........................ H-15 H.7.3 Offloading System Logs and Files.......... H-16 H.7.4 Offloading Nonessential Files............. H-16 Glossary Index Examples 10-1 Sample VMSTAILOR Session.................. 10-6 10-2 Sample DECW$TAILOR Session................ 10-14 Figures 1-1 Documentation Used to Perform an Installation.............................. 1-11 1-2 Documentation Used to Perform an Upgrade................................... 1-13 xiii Tables 2-1 VAXcluster Information for Installations............................. 2-5 4-1 Sizes of Decompressed System Libraries.... 4-7 8-1 Sizes of Decompressed System Libraries.... 8-9 9-1 DECwindows Keymap......................... 9-4 A-1 OpenVMS VAX Upgrade Version Matrix........ A-1 B-1 First VMS or OpenVMS Version That Supports VAX Computers............................. B-2 B-2 License Unit Requirement Table (LURT)..... B-5 E-1 DECwindows Display Server and Fonts Components................................ E-1 G-1 Prerequisite and Optional Software for PCs....................................... G-11 xiv _________________________________________________________________ Preface This manual is your primary source for information about upgrading and installing the OpenVMS VAX Version 7.1 operating system. Before you attempt to install or upgrade the operating system, be sure to read all the release notes and cover letters (if any) included in your distribution kit. If you received factory-installed software with your computer, read that user documentation first for information about starting up your system. Otherwise, use this manual for step-by-step instructions for performing an installation or an upgrade. When the instructions in this manual direct you to do so, refer to the upgrade and installation supplement for information specific to your VAX computer. Intended Audience If you are responsible for installing or upgrading the OpenVMS operating system and for performing related backup, shutdown, and startup procedures, read this manual before you install or upgrade to Version 7.1 of the OpenVMS VAX operating system. Document Structure The information in this manual is organized as follows: o Chapter 1 provides an overview of the upgrade and installation procedures. It describes what happens during an installation or an upgrade, lists some changes and restrictions you should be aware of, and refers you to the appropriate documentation. xv o Chapter 2 describes the tasks you must perform before installing the OpenVMS VAX operating system. o Chapter 3 describes how to install Version 7.1 of the OpenVMS VAX operating system on a VAXcluster or a standalone VAX computer. o Chapter 4 lists the tasks you should perform after you install the OpenVMS VAX operating system. o Chapter 5 contains cautions, restrictions, and requirements for upgrading your VAX computer system and tells you how to prepare your system for an upgrade. o Chapter 6 contains additional information for upgrading a VAXcluster environment. o Chapter 7 describes the procedure for upgrading a standalone VAX computer. o Chapter 8 lists the tasks you should perform after the upgrade. o Chapter 9 describes how to customize DECwindows device support software. o Chapter 10 describes how to use VMSTAILOR and DECW$TAILOR to add or remove optional OpenVMS software. o Appendix A provides a quick method of applying multiple upgrades to a VAX system. o Appendix B provides notes and supplemental license management information to the upgrade and installation procedures. o Appendix C describes how to boot from the [SYSF] directory on the different types of VAX computers. o Appendix D lists the subclasses in the OpenVMS VAX optional save sets C, D, E, and F. o Appendix E lists DECwindows display server and font files. o Appendix F lists files installed either over or under the version numbers of existing files during an upgrade. o Appendix G describes how to prepare your OpenVMS system and your PC to run the OpenVMS Management Station server and client software. xvi o Appendix H describes methods for managing small capacity system disks, including some specific recommendations for installing or upgrading to the OpenVMS VAX Version 7.1 operating system and the DECwindows Motif for OpenVMS Version 1.2-3 layered product. o The Glossary defines commonly used terms. o The Index provides a quick way to find information. Related Documents The following documents contain information associated with performing an upgrade or installation: o The upgrade and installation supplement for your VAX computer-Provides supplemental information necessary during an installation or upgrade, such as booting the system and determining device names. o OpenVMS Version 7.1 Release Notes -Describes changed and enhanced software features, software problems and restrictions, and changes to the documentation for Version 7.1 of the OpenVMS VAX operating system. o OpenVMS Version 7.1 New Features Manual-Describes new software features for the OpenVMS Version 7.1 operating system. o OpenVMS Cluster Systems-Describes the procedures for establishing and managing VAXcluster configurations. o OpenVMS License Management Utility Manual-Provides information about registering and managing licenses on an OpenVMS VAX system. o OpenVMS Guide to System Security-Describes security features provided by the OpenVMS VAX operating system, including criteria for C2 systems. o OpenVMS System Manager's Manual-Provides task-oriented information about managing an OpenVMS system, including how to use the VMSINSTAL command procedure. o OpenVMS DCL Dictionary-Provides detailed reference information and examples for all OpenVMS DCL commands. xvii o OpenVMS System Management Utilities Reference Manual: M-Z-Provides complete information about using the POLYCENTER Software Installation utility PRODUCT command. o The hardware manuals supplied with your VAX computer provide detailed information about system hardware. For additional information about the Open Systems Software Group (OSSG) 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: OSSG Documentation, ZKO3-4/U08 Mail OSSG Documentation Group, ZKO3-4/U08 110 Spit Brook Rd. Nashua, NH 03062-2698 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). Conventions In this manual, every use of OpenVMS VAX means the OpenVMS VAX operating system. Every use of DECwindows and DECwindows Motif refers to DECwindows Motif for OpenVMS software. xviii 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. PF1 x A sequence such as PF1 x indicates that you must first press and release the key labeled PF1, then press and release 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.) . . . A horizontal ellipsis in examples indicates 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 format descriptions, parentheses indicate that, if you choose more than one option, you must enclose the choices in parentheses. xix [ ] In 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 format descriptions, braces surround a required choice of options; you must choose one of the options listed. text style This text style represents the introduction of a new term or the name of an argument, an attribute, or a reason. This style is also used to show user input in Bookreader versions of the manual. italic text Italic text emphasizes important information, indicates variables, and indicates complete titles of manuals. Italic text also represents information that can vary in system messages (for example, Internal error number), command lines (for example, /PRODUCER=name), and command parameters in text. UPPERCASE TEXT Uppercase text indicates a command, the name of a routine, the name of a file, or the abbreviation for a system privilege. - A hyphen in code examples indicates that additional arguments to the request are provided on the line that follows. numbers All numbers in text are assumed to be decimal, unless otherwise noted. Nondecimal radixes-binary, octal, or hexadecimal-are explicitly indicated. xx This manual often refers to products by their abbreviated names. For example, the VAX 8200, VAX 8250, VAX 8300, and VAX 8350 computers are referred to as the VAX 8200, 8250, 8300, 8350. The MicroVAX 2000 computer is referred to as the MicroVAX 2000, and so on. xxi 1 _________________________________________________________________ Overview of Installation and Upgrade Procedures 1.1 Introduction This chapter provides a general description of what happens during the installation and upgrade procedures, including information you should be aware of before you upgrade to or install the OpenVMS VAX Version 7.1 operating system. This chapter also describes the contents of the distribution kit, tells you whether you should do an installation or an upgrade, and refers you to the appropriate documentation. 1.2 Important Information Before you install or upgrade to OpenVMS VAX Version 7.1, you should review the information in this section. 1.2.1 DECNET-PLUS The OpenVMS VAX Version 7.1 kit includes the DECnet-Plus software. The DECnet Phase IV product is no longer part of the operating system installation and upgrade menus. During the OpenVMS VAX installation or upgrade procedure, you are given the option to install the DECnet-Plus product. Whether or not you chose to install DECnet-Plus, DECnet Phase IV will not be present on your system after you install or upgrade to OpenVMS VAX Version 7.1. A kit containing the DECnet-Plus software is provided with the OpenVMS VAX Version 7.1 kit. In future releases, customers who do not receive the operating system installation kit on CD-ROM will need to purchase the DECnet-Plus media and documentation separately. Overview of Installation and Upgrade Procedures 1-1 Overview of Installation and Upgrade Procedures 1.2 Important Information If you want to use the DECnet Phase IV product, a DECnet Phase IV kit is provided, which you can install after you have installed OpenVMS VAX Version 7.1. However, be aware that, if you install or reinstall DECnet Phase IV, you must purchase a separate support contract. ________________________ Note ________________________ If DECnet-Plus is installed on your system, you must remove that product before you install the DECnet Phase IV product. Both DECnet products cannot run at the same time. ______________________________________________________ To install DECnet Phase IV, do the following after the OpenVMS VAX installation or upgrade is complete: o If DECnet-Plus is installed on your system, use the PRODUCT REMOVE command to remove that product. (See OpenVMS System Management Utilities Reference Manual: M-Z for complete information about using the PRODUCT command.) o Mount the distribution media that contains the DECnet Phase IV kit. For example, if your OpenVMS VAX distribution media is on CD-ROM and you want to mount it on a local drive, DKA400, you would enter a command similar to the following: $ MOUNT/OVER=ID DKA400 If you are using an InfoServer device, enter the following command to see if the device DAD0 is present on your system: $ SHOW DEVICE DAD0 If DAD0 is not present, enter the following: $ @SYS$STARTUP:ESS$STARTUP CLIENT Once DAD0 is present, bind to the service and mount the CD. For example, if the service name is VAXVMS071, you would enter a command similar to the following: 1-2 Overview of Installation and Upgrade Procedures Overview of Installation and Upgrade Procedures 1.2 Important Information $ MCR ESS$LADCP BIND VAXVMS071 $ MOUNT/OVER=ID DAD$VAXVMS071 Now, invoke the POLYCENTER Software Installation utility and install DECnet Phase IV by entering a command similar to the following: $ PRODUCT INSTALL DECNET_PHASE_IV /SOURCE=DKA400:[KITS.DECNET_PHASE_IV_KIT] For DKA400, substitute the correct name for your source drive. o If your distribution media is on TK50 tapes, mount the TK50 volume that contains the DECnet Phase IV kit. For example, if the device name of your TK50 drive is MKA500, you would enter a command similar to the following: $ MOUNT/OVER=ID MKA500: Now, install the DECnet Phase IV product by entering a command similar to the following: $ PRODUCT INSTALL DECNET_PHASE_IV /SOURCE=MKA500: For MKA500:, substitute the correct name for your source drive. For more information about the DECnet-Plus product, see the OpenVMS Version 7.1 New Features Manual and the DECnet/OSI for OpenVMS Installation and Configuration. 1.2.2 DECWINDOWS MOTIF FOR OPENVMS-MINIMUM VERSION For OpenVMS VAX Version 7.1, the minimum supported version of DECwindows Motif for OpenVMS is 1.2-3. 1.2.3 MACRO32.EXE AND STANDALONE BACKUP To build standalone backup onto tape, you must have the image MACRO32.EXE on your system disk. Do not tailor off the Macro libraries before building standalone backup onto tape. Overview of Installation and Upgrade Procedures 1-3 Overview of Installation and Upgrade Procedures 1.2 Important Information 1.2.4 LAYERED PRODUCT AVAILABILITY The most current information about layered product support is available in the Software Public Rollout Reports for OpenVMS. These reports are available from the OpenVMS World Wide Web site in the "literature" section. Use the following URL: http://www.openvms.digital.com If you do not have access to the Internet, you can find the operating system support information on any of the quarterly Software Products Libraries, in the following directory: [README]SW_COMPAT_MATRIX.PS (.TXT) 1.2.5 RESTRICTIONS Restrictions for OpenVMS VAX Version 7.1 include: o The minimum memory requirement is 4 megabytes. o The MA780 shared memory is not supported. o You cannot install or upgrade to Version 7.1 of the OpenVMS VAX operating system on the following VAX computers and system disks: Computers MicroVAX I, VAXstation I, VAXstation 8000, VAX-11/725, and VAX-11/782 System_disks RK07, RL02, RC25, RD32, RD51, RD52, RD53, RZ22, and RZ23L. o If your system uses a small-capacity system disk (less than 210 megabytes), the entire OpenVMS VAX Version 7.1 operating system and the complete DECwindows Motif for OpenVMS VAX layered product will not fit on your disk. Appendix H describes some methods that will enable you to install or upgrade to OpenVMS VAX Version 7.1 and DECwindows Motif for OpenVMS VAX on a small-capacity system disk. Note that you can use the methods described in Appendix H to free up disk space on any system. For more information about these restrictions, see the OpenVMS Operating System for VAX and Alpha, Version 7.1 Software Product Description (SPD). 1-4 Overview of Installation and Upgrade Procedures Overview of Installation and Upgrade Procedures 1.3 Definitions: A Few Key Terms 1.3 Definitions: A Few Key Terms You should be familiar with the following key terms before performing an installation or upgrade: ___________________________________________________________ Term__________________Definition___________________________ Distribution Media The media containing the OpenVMS VAX operating system software. This software is supplied in a format that the computer cannot use until you perform an installation or upgrade. System Disk The disk that contains (or will contain) the OpenVMS VAX operating system in a usable format. The installation or upgrade procedure converts the OpenVMS VAX operating system software to this usable format when transferring the software from the distribution media to the system disk. Local Drive A drive that is connected directly to a VAX computer. For example, a magnetic tape drive connected directly to a VAX computer is referred to as a local tape drive. If you have a standalone VAX computer, it is likely all the drives connected to your system are local drives. InfoServer A general-purpose disk storage server that allows you to use the distribution compact disc to install the operating system on remote client systems connected to the same LAN (local area network). Source Drive The drive that holds the distribution media during the upgrade or installation. Overview of Installation and Upgrade Procedures 1-5 Overview of Installation and Upgrade Procedures 1.3 Definitions: A Few Key Terms ___________________________________________________________ Term__________________Definition___________________________ Target Drive The drive that holds the system disk-or, for some files, the alternate disk-during the upgrade or installation. HSC Drive A drive connected to a hierarchical storage controller (HSC) device. For example, a magnetic tape drive connected to an HSC device is referred to as an HSC tape drive. The HSC is a self-contained, intelligent, mass storage subsystem that enables VAXcluster nodes to share Digital Storage Architecture ______________________(DSA)_disks._________________________ For definitions of other specialized terms used in this manual, see the Glossary at the end of this book. 1.4 Locating Files on the Distribution Media The OpenVMS VAX files are stored on the distribution media as the following save sets: ___________________________________________________________ Save_Set_Name_____Description______________________________ VMS071.A Required VMS071.B Required VMS071.C Library (optional) VMS071.D Optional (optional) VMS071.E Help Message (optional) VMS071.F OpenVMS Management Station software PC files (optional) ___________________________________________________________ See Appendix D for descriptions of the file subclasses contained in the optional save sets. 1-6 Overview of Installation and Upgrade Procedures Overview of Installation and Upgrade Procedures 1.4 Locating Files on the Distribution Media The optional DECwindows support files are stored on the distribution media as the following save sets: ___________________________________________________________ Save_Set_Name_____Description______________________________ DECW071.C Base support files DECW071.D Workstation support files DECW071.E 75 dots-per-inch (dpi) font files DECW071.F 100 dpi font files ___________________________________________________________ 1.4.1 ON MAGNETIC TAPE The OpenVMS VAX Version 7.1 magnetic tape kit contains OpenVMS VAX software on four tapes. The first tape contains the required save sets VMS071.A and VMS071.B. The second tape contains the save set VMS071.C. The third tape contains save sets VMS071.D, VMS071.E, and VMS0701F. The fourth tape contains the DECwindows base support and workstation support files, and DEC AMDS files. 1.4.2 ON TAPE CARTRIDGES The OpenVMS VAX Version 7.1 TK50 tape kit contains OpenVMS VAX software on two tape cartridges. The first cartridge contains VMS071.A, VMS071.B, and VMS071.C save sets. The second cartridge contains standalone BACKUP, VMS071.D, VMS071.E, and VMS071.F save sets, DECwindows base support and workstation support files, and DEC AMDS files. 1.4.3 ON COMPACT DISC The OpenVMS VAX Version 7.1 compact disc kit contains all the save sets and DECwindows base and workstation support files on one compact disc. (For more information, see the Guide to OpenVMS Version 7.1 CD-ROMs.) Note that you can install or upgrade the operating system from a local compact disc drive as well as from an InfoServer device. Overview of Installation and Upgrade Procedures 1-7 Overview of Installation and Upgrade Procedures 1.4 Locating Files on the Distribution Media 1.4.4 DECAMDS AND MONITORING PERFORMANCE HISTORY (MPH) FILES The DECamds software is included as save sets AMDS071.A and AMDS071.B on the OpenVMS VAX distribution media. The save sets are located on the third magnetic tape volume, on the second tape cartridge, and on the compact disc in the [AMDS071] directory. The Monitoring Performance History (MPH) kit is also included on the OpenVMS VAX distribution media. The MPH kit is located on the third magnetic tape, on the second tape cartridge, and on the compact disc in the [MPH] directory. 1.4.5 SOFTWARE PRODUCT DESCRIPTIONS (SPDS) The following SPD files are located on the second tape cartridge of the TK50 distribution kit and the third tape of the magnetic tape distribution kit. These SPD files have been grouped into an OpenVMS BACKUP save set named VMS071_SPD.BCK. File names with the .PS extension are in PostScript format. File names with the .TXT extension are in plain ASCII text format. DECNET_SPD.PS DECnet-Plus for OpenVMS VAX and DECNET_SPD.TXT Alpha, Version 7.1 OVMS_71_SPD.PS OpenVMS Operating System for VAX and OVMS_71_SPD.TXT Alpha, Version 7.1 RMS_SPD.PS RMS Journaling for OpenVMS, Version RMS_SPD.TXT 7.1 CLUSTER_SPD.PS OpenVMS Cluster Software CLUSTER_SPD.TXT VOL_SHAD_SPD.PS Volume Shadowing for OpenVMS, Version VOL_SHAD_SPD.TXT 7.1 To obtain all the SPD files and restore them to your current default directory, enter a BACKUP command using the following format: BACKUP source-drive:VMS071_SPD.BCK /SAVE_SET *.*;* For source-drive, substitute the name of the device that holds your distribution kit. For example, if your source- drive is a local magnetic tape drive with the device name MUAO, you would enter the following command: 1-8 Overview of Installation and Upgrade Procedures Overview of Installation and Upgrade Procedures 1.4 Locating Files on the Distribution Media $ BACKUP MUAO:VMS071_SPD.BCK/SAVE_SET *.*;* To restore all the SPD files in PostScript format to your default directory, enter the following: $ BACKUP MUAO:VMS071_SPD.BCK/SAVE_SET/SELECT=*.PS *.*;* The following command restores the PostScript SPD file for the OpenVMS VAX and OpenVMS Alpha operating systems to your current default directory: $ BACKUP MUAO:VMS071_SPD.BCK/SAVE_SET/SELECT=OVMS_71_SPD.PS *.*;* If your distribution kit is on compact disk, the SPD files are located in the [DOCUMENTATION.V071] directory. For information about locating and printing these SPD files, see the Guide to OpenVMS Version 7.1 CD-ROMs. 1.5 What Happens During an Installation When you install the OpenVMS VAX operating system, the installation procedure does the following: o Initializes the system disk, overwriting its contents. o Creates a system directory structure. o Transfers the OpenVMS VAX files from the distribution media to the system disk. Some files can be transferred to an alternate disk. 1.5.1 WHEN TO PERFORM AN INSTALLATION Use the installation procedure under the following conditions: o If your VAX computer is new (it has never had any version of the operating system running on it, including factory-installed software). o If your VAX computer is running a previous version of the operating system and you want to overwrite the entire contents of the system disk (the OpenVMS VAX operating system, application software, and user files). o If you are running a previous version of the operating system, but you cannot upgrade. For example, if you changed the names of system directories on the system disk, the upgrade procedure will not work correctly. You can either restore the system disk to its original Overview of Installation and Upgrade Procedures 1-9 Overview of Installation and Upgrade Procedures 1.5 What Happens During an Installation directory structure, or you can reinstall the OpenVMS VAX operating system. Caution: The installation procedure initializes the system disk, overwriting its contents. For this reason, use the installation procedure only on new VAX computers or if you want to destroy the contents of the system disk. 1.5.2 HOW TO USE THE INSTALLATION DOCUMENTATION This manual contains step-by-step instructions for performing an OpenVMS VAX installation. However, you will need to refer to several different documents before and during the installation. Figure 1-1 illustrates the major steps in an installation and the documents you will use to perform each step. 1-10 Overview of Installation and Upgrade Procedures Overview of Installation and Upgrade Procedures 1.5 What Happens During an Installation Figure 1-1 Documentation Used to Perform an Installation Overview of Installation and Upgrade Procedures 1-11 Overview of Installation and Upgrade Procedures 1.6 What Happens During an Upgrade 1.6 What Happens During an Upgrade When you upgrade the OpenVMS VAX operating system, the upgrade procedure does the following: o Deletes and purges some OpenVMS VAX files on the system disk but leaves all the user files intact. o Transfers the new OpenVMS VAX files from the distribution media to the system disk. Note: The upgrade procedure puts the most recent versions of the OpenVMS VAX files in SYS$COMMON. o Merges some of the old OpenVMS files and the new OpenVMS VAX files and replaces others. Certain OpenVMS VAX files are placed either over or under existing files (that is, they are given a version number above or below the version number of the existing file). This is done to protect any customizations to the files and results in having two versions of the file when the upgrade is completed. For more information, see Appendix F. o Cleans up files and structures used only during the upgrade. o Leaves your OpenVMS license and System Integrated Product (SIP) licenses intact. You do not need to reinstall these licenses after you upgrade. (See Appendix B for detailed information about license management for OpenVMS VAX Version 7.1.) 1.6.1 WHEN TO PERFORM AN UPGRADE In most cases, you can use the upgrade procedure to obtain a higher version of the OpenVMS VAX operating system. Unlike the installation procedure, the upgrade procedure does not initialize your system disk. This means you can get the latest version of the operating system and keep your user files and optional software files intact. 1-12 Overview of Installation and Upgrade Procedures Overview of Installation and Upgrade Procedures 1.6 What Happens During an Upgrade 1.6.2 HOW TO USE THE UPGRADE DOCUMENTATION This manual contains step-by-step instructions for performing an OpenVMS VAX upgrade. However, you will need to refer to several different documents before and during an upgrade. Figure 1-2 illustrates the major steps in an upgrade and the documents you will use to perform each step. Figure 1-2 Documentation Used to Perform an Upgrade 1.7 Where to Go Next If you are installing the OpenVMS VAX operating system, go to Chapter 2. If you are upgrading the OpenVMS VAX operating system, go to Chapter 5. Overview of Installation and Upgrade Procedures 1-13 2 _________________________________________________________________ Before Installing OpenVMS VAX Software 2.1 Overview This chapter describes how to prepare for installing the OpenVMS VAX operating system, including: o Being aware of the cautions and restrictions o Ensuring your hardware is ready o Ensuring your software distribution kit is complete o Preparing for a C2 system o Preparing for a VAXcluster environment o Preparing your tape and disk drives o Gathering the information you need to supply during the installation procedure o Completing the preinstallation checklist If you are an experienced system manager, you can use the checklist at the end of the chapter to complete all the necessary preinstallation tasks. If you are a less-experienced system manager, you should read the entire chapter and then use the checklist to make sure you completed all the preinstallation tasks. 2.2 Cautions and Restrictions Before you begin the installation procedure, note the following cautions and restrictions. Before Installing OpenVMS VAX Software 2-1 Before Installing OpenVMS VAX Software 2.2 Cautions and Restrictions 2.2.1 CAUTIONS The following cautions apply for Version 7.1 of the OpenVMS VAX operating system: o The software installation procedure overwrites the contents of the system disk. Use the installation procedure only if your VAX computer is new or if you want to destroy the contents of the system disk. If your system disk contains files you want to save, you should upgrade to the new version of OpenVMS VAX. For an overview of the upgrade procedure, see Chapter 5. o Do not attempt to use VMSINSTAL with OPTION G to transfer OpenVMS VAX save sets to another media type; doing so will produce an unusable system. Instead, you can use the DCL command COPY to transfer save sets to another media type. If you move the save sets from the distribution media before beginning the installation, you must move them to the [000000] directory on a disk that is not the system disk; otherwise, the installation will fail. 2.2.2 RESTRICTIONS The following restrictions apply for Version 7.1 of the OpenVMS VAX operating system: o If your system contains DIGITAL Storage Systems Interconnect (DSSI) disks attached to a KFQSA controller, you will notice a change in the device names for DSSI disks attached to KFQSA controllers. When you boot standalone BACKUP, it will display the devices on your system using the new device naming scheme. Use the new device names throughout the installation and after you complete the installation. o If you want to use DECwindows software with OpenVMS VAX Version 7.1, you must purchase and install the DECwindows Motif for OpenVMS Version 1.2-3, or higher, layered product. For more information, see Section 1.2.1. 2-2 Before Installing OpenVMS VAX Software Before Installing OpenVMS VAX Software 2.3 Are You Ready to Install? 2.3 Are You Ready to Install? Before you begin to install the OpenVMS VAX operating system, make sure you have all the required hardware and software components. 2.3.1 HARDWARE COMPONENTS Examine your hardware for the following: o Make sure the hardware has been installed and checked for proper operation. For detailed information about the hardware, see the hardware manual for your VAX computer. o Make sure you know how to turn on and operate your system components, including the system unit, console, monitor, drives, terminals, and printers. If necessary, read the 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. 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. For more information, see the upgrade and installation supplement for your computer. 2.3.2 SOFTWARE COMPONENTS Examine your software for the following: o Make sure you have all the items listed on the bill of materials (BOM) in the OpenVMS VAX distribution kit. If your kit is incomplete, notify Digital Software Supply, and request priority shipment of any missing items. o Before installing the OpenVMS VAX operating system, review Appendix B of this manual for license management information, the OpenVMS Version 7.1 New Features Manual, the OpenVMS Version 7.1 Release Notes, and any cover letters included with your kit. o Read the Before Installing OpenVMS section in the upgrade and installation supplement for your VAX computer, which describes tasks specific to your VAX computer that you must complete before beginning the installation. Before Installing OpenVMS VAX Software 2-3 Before Installing OpenVMS VAX Software 2.4 Preparing for an Installation 2.4 Preparing for an Installation Now that you have determined that your hardware and software components are ready, you can make the necessary preparations for installing the OpenVMS VAX operating system. 2.4.1 PREPARING FOR A C2 SYSTEM Many of the security features provided by the OpenVMS VAX operating system are directed toward the criteria for a C2 system, as defined in the Department of Defense Trusted Computer System Evaluation Criteria, published by the U.S. Department of Defense Computer Security Center (DOD 5200.28-STD). A C2 system is the shipped system that has been configured according to the guidelines in Appendix C of the OpenVMS Guide to System Security. Before installing OpenVMS VAX, become familiar with the requirements for operating an OpenVMS VAX system within the C2 framework. 2.4.2 PREPARING FOR A VAXCLUSTER ENVIRONMENT If you are installing the OpenVMS VAX operating system in a VAXcluster environment, the installation procedure will ask you for information about your VAXcluster environment. Before proceeding, review OpenVMS Cluster Systems, which provides the information you will need to answer questions during the installation. Note: Entering incorrect information during the installation can force you to repeat the entire installation procedure. Table 2-1 lists the VAXcluster information you need and explains how to obtain that information. For a complete explanation, see OpenVMS Cluster Systems. 2-4 Before Installing OpenVMS VAX Software Before Installing OpenVMS VAX Software 2.4 Preparing for an Installation Table_2-1_VAXcluster_Information_for_Installations_______________ Information You Need______________How_to_Get_It__________________________________ Type of Configuration types are distinguished by the configuration interconnect device that the VAX computers in the cluster use to communicate with one another: Computer Interconnect (CI), Ethernet, DIGITAL Storage Systems Interconnect (DSSI), or FDDI (Fiber Distributed Data Interface). DECnet node name Determined by the network or system manager and node address for each VAX computer on the network. See your system or network manager for the DECnet node name and node address for the VAX computer on which you are installing the OpenVMS VAX operating system. See the DECnet/OSI for OpenVMS Installation and Configuration for more information. Allocation class During the installation procedure you will value be asked for the ALLOCLASS value of the VAX computer on which you are installing the OpenVMS VAX operating system. For example: Enter a value for MYNODE's ALLOCLASS parameter: Refer to OpenVMS Cluster Systems for the rules on specifying allocation class values. Note that, in a mixed-interconnect VAXcluster environment, the allocation class value cannot be zero. It has to be a value between 1 and 255. This is also true for any VAX computer that is connected to a dual-pathed disk. When you enter the allocation class value, the installation procedure uses it to automatically set the value of the system parameter ALLOCLASS. Quorum disk See OpenVMS Cluster Systems to determine whether you want a quorum disk in the cluster. (continued on next page) Before Installing OpenVMS VAX Software 2-5 Before Installing OpenVMS VAX Software 2.4 Preparing for an Installation Table_2-1_(Cont.)_VAXcluster_Information_for_Installations_______ Information You Need______________How_to_Get_It__________________________________ Location for See OpenVMS Cluster Systems to determine where page and swap the page and swap files will be located for files the system from which you are installing the OpenVMS VAX operating system software. MOP servers, To establish either a local area or a mixed- disk servers, interconnect cluster, determine which systems tape servers will be Maintenance Operations Protocol (MOP) servers, disk servers, and tape servers. Refer to OpenVMS Cluster Systems. Cluster group To establish either a local area or a mixed- number and interconnect cluster. cluster password Cluster_group_number: A number in the range from 1 to 4095 or from 61440 to 65535. Cluster_password: Can range from 1 to 31 alphanumeric characters, including dollar signs ($) and underscores (_). ___________________________________________________________ 2.4.3 PREPARING TAPE AND DISK DRIVES Prepare your tape and disk drives using the following steps: 1. Decide which drive will hold the distribution tape and which drive will hold the system disk. Determine the device names for each drive, and write these names on a piece of paper. You will need this information throughout the installation. If you need information about devices and device names, refer to the Before Installing the OpenVMS Operating System section in the upgrade and installation supplement for your VAX computer. Note: Do not place the distribution media in the drive at this point. 2. Follow this step only if the source drive or target drive is attached to a hierarchical storage controller (HSC). Otherwise, go to step 3. 2-6 Before Installing OpenVMS VAX Software Before Installing OpenVMS VAX Software 2.4 Preparing for an Installation Make sure that both the CI and HSC devices are turned on and on line. Obtain the HSC name from the system manager, or use the following procedure: a. Press Ctrl/C at the HSC console terminal. b. Enter the following command at the HSC> prompt and press Return: HSC> SHOW SYSTEM The information displayed includes the name of the HSC. For example: 22-NOV-1996 15:00:00.00 Boot:12-NOV-1996 11:31:11.41 Up: 51:00 Version V350 System ID: %X000000011 Name: MUTT . . . DISK allocation class = 1 TAPE allocation class = 0 Start command file Disabled SETSHO - Program Exit For more information, see the HSC User's Guide. 3. Place a scratch disk in the drive for the system disk (unless the system disk is fixed). 4. Spin up the disk that will be the system disk but do not write protect it. 2.4.4 INFORMATION YOU NEED DURING THE INSTALLATION During the installation, the procedure prompts you to supply certain information. To save time once the procedure begins, be sure you have the following information available. Remember, entering incorrect information during the installation could force you to repeat the entire installation procedure. Before Installing OpenVMS VAX Software 2-7 Before Installing OpenVMS VAX Software 2.4 Preparing for an Installation Required Information________Explanation___________________________________ Passwords You will be prompted to type passwords of at least 8 characters for the SYSTEM, SYSTEST, and FIELD accounts. SCSNODE and If you are installing a standalone system, you SCSSYSTEMID will be prompted to supply an SCSNODE name and parameters an SCSSYSTEMID. The SCSNODE name must be a 1- to 6-character unique DECnet node name. The SCSSYSTEMID system parameter is calculated as follows: (DECnet area * 1024) + node number Note that, if you are installing the operating system in a VAXcluster environment, the installation procedure does not prompt you to supply these parameters. It calculates the SCSNODE and SCSSYSTEMID based on the DECnet node name and node address that you supply earlier in the procedure. Optional The installation procedure prompts you to components specify whether you want to install the and OpenVMS library (VMS071.C), optional (VMS071.D) Management OpenVMS components, and OpenVMS Management Station files Station software PC files (VMS071.F). Appendix D lists the files included in these save sets. You can save some space on your system disk if you choose not to install these components, but be sure to review Appendix D before deciding. 2-8 Before Installing OpenVMS VAX Software Before Installing OpenVMS VAX Software 2.4 Preparing for an Installation _________________________________________________________________ Required Information________Explanation___________________________________ Location for Help Save set VMS071.E contains the online Help Message utility Message utility, which you can install on your system disk or on an alternate disk. (However, if you copied the distribution kit to some other media from which you will be performing the installation, you cannot install this save set on that media.) DECwindows The installation procedure prompts you to components specify which of the following DECwindows components you want to install: o DECwindows base support (required for running DECwindows software), which includes: - DECwindows transport - DECwindows keymaps o DECwindows workstation support (required for VAX workstations), which includes: - DECwindows X11 display server - Graphics drivers - 75 dots/inch video fonts - 100 dots/inch video fonts (option available only if you select DECwindows workstation support) You must install the DECwindows Motif for OpenVMS (previously called VMS DECwindows Motif) layered product if you want to run the DECwindows software. DECwindows Motif for OpenVMS Version 1.2-3 (or 1.2 if the VAXMOTF05_012 remedial kit is installed) is the minimum supported version for systems running OpenVMS VAX Version 7.1. If you do not know which version of DECwindows Motif you are currently running on your system, you can check by entering the following command: $ ANALYZE/IMAGE SYS$LIBRARY:DECW$XLIBSHR.EXE Note: The DECwindows Motif for OpenVMS layered product does not have the DECwindows base and workstation support components. To get full DECwindows support, you must select the DECwindows components provided with the OpenVMS VAX kit and install the separate DECwindows Motif for OpenVMS layered product, which supports both Motif and XUI environments. Before Installing OpenVMS VAX Software 2-11 Before Installing OpenVMS VAX Software 2.4 Preparing for an Installation _________________________________________________________________ Required Information________Explanation___________________________________ PAK information The information listed on Product Authorization Keys (PAKs) for your OpenVMS VAX license and any system-integrated products you will run. The installation procedure gives you the opportunity to register any licenses you have. To register your licenses, you will need to enter the information listed on the PAK for each license. _________________________________________________________________ 2.5 Preinstallation Checklist Before you begin the installation, use the following checklist to make sure you have completed all of the tasks described in this chapter: < Read the cautions and restrictions described at the beginning of this chapter. < Make sure the hardware is installed and tested. (Described in the hardware manuals for your VAX computer.) < Check the contents of your kit against the bill of materials (BOM). < Read Appendix B of this manual, the OpenVMS Version 7.1 New Features Manual, the OpenVMS Version 7.1 Release Notes, and any cover letters included with your kit. < Read Section 2.4.1 for special considerations about running the OpenVMS VAX operating system in a C2 environment if you intend to create a C2 compliant environment. < Turn on the system. (Described in the upgrade and installation supplement for your VAX computer.) < Set up your system to record the installation procedure. (Described in the upgrade and installation supplement for your VAX computer.) < Read the Before Installing OpenVMS section in the upgrade and installation supplement for your VAX computer and perform the tasks described there. 2-12 Before Installing OpenVMS VAX Software Before Installing OpenVMS VAX Software 2.5 Preinstallation Checklist < Make sure you have the most recent version of the console media if you have a VAX computer that uses console media. (Described in the upgrade and installation supplement for your VAX computer.) < Determine whether you want a CI only, local area, or mixed-interconnect cluster if you are installing the OpenVMS VAX operating system on a VAX computer in a VAXcluster environment. (Described in OpenVMS Cluster Systems.) You should have the following information, depending on the type of VAXcluster: o CI Only VAXcluster: Get the allocation class value, DECnet node name, and DECnet node address for the computer. You also need to decide if you want a quorum disk and where the page and swap files for the system from which you are installing will be located. o Local Area and Mixed-Interconnect VAXclusters: Get the allocation class value, the DECnet node name, the DECnet node address, the cluster group number, and the cluster password. You also need to decide if you want a quorum disk and where the page and swap files for the system from which you are installing will be located. < Prepare the disk and tape drives. (Described in Section 2.4.3.) < Make sure you have the following information (described in Section 2.4.4) available: o Passwords containing at least 8 characters for the SYSTEM, SYSTEST, and FIELD accounts. o SCSNODE and SCSSYSTEMID if you are installing a standalone system. o A list of optional OpenVMS VAX components you want to install. o A list of optional DECwindows support components you want to install. Before Installing OpenVMS VAX Software 2-13 Before Installing OpenVMS VAX Software 2.5 Preinstallation Checklist o Information listed on Product Authorization Keys (PAKs) for your OpenVMS VAX license and any system- integrated products you will run. After you have performed all the tasks in the checklist, go to Chapter 3 to begin the installation. 2-14 Before Installing OpenVMS VAX Software 3 _________________________________________________________________ Installing the OpenVMS VAX Operating System 3.1 Overview During the installation procedure, OpenVMS VAX files are transferred from the distribution media to the system disk or, for certain files, to an alternate disk. The time required to complete an installation varies depending on your hardware configuration and on the distribution media you are using. In most cases, magnetic tapes and tape cartridges require more time than compact discs. The following installation tasks are described in this chapter: o Booting standalone BACKUP o Creating the system disk o Configuring a cluster o Setting passwords o Creating the rights database o Registering licenses o Running AUTOGEN At certain points in the procedure you will need to refer to the upgrade and installation supplement for installation instructions that are specific to your VAX computer. 3.2 Booting Standalone BACKUP Standalone BACKUP is a subset of the OpenVMS Backup utility (BACKUP). Because you boot it into main memory, standalone BACKUP executes outside the control of the operating system. You use standalone BACKUP to restore the required save sets from the distribution media to your system disk. Installing the OpenVMS VAX Operating System 3-1 Installing the OpenVMS VAX Operating System 3.2 Booting Standalone BACKUP Standalone BACKUP is included in the OpenVMS VAX distribution kit. Each piece of media in the distribution kit has a label that indicates its contents. For example, there are two tape cartridges in a TK50 kit. Standalone BACKUP is on the second tape cartridge. 3.2.1 BOOTING FROM TAPE CARTRIDGE If your distribution media is tape cartridges, complete the following steps to boot standalone BACKUP. (If you are using an InfoServer device, go to Section 3.2.2.) 1. Place the media that contains standalone BACKUP in the source drive or in the console drive. 2. Follow the instructions in the Booting Standalone BACKUP section of the upgrade and installation supplement for your VAX computer. 3. After you boot standalone BACKUP, the system displays the following: %BACKUP-I-IDENT, standalone BACKUP V6.2; the date is 22-NOV-1996 15:00 $ Note: If you have a tape cartridge kit, remove the tape cartridge 2/2 from the drive after you boot standalone BACKUP. Put the tape cartridge that contains the OpenVMS VAX operating system in the drive. The tape cartridge is labeled VMS071 BIN TK50 1/2 VMS BINARY. After you have booted standalone BACKUP, go to Section 3.3. 3.2.2 BOOTING FROM AN INFOSERVER DEVICE If you are using the InfoServer to boot standalone BACKUP from a compact disc, complete the following steps: 1. Insert the distribution compact disc into the drive. 2. Follow the instructions in the Booting Standalone BACKUP section of the upgrade and installation supplement for your VAX computer. 3. Enter your VAX processor boot command by using the designator for the Ethernet adapter in the boot path and, except for the VAX 9000 computer, add the /R5:100 qualifier to the boot command. 3-2 Installing the OpenVMS VAX Operating System Installing the OpenVMS VAX Operating System 3.2 Booting Standalone BACKUP For example, on a VAX 6000 computer: >>> B/R5:100/X:D/B:6 ET0 On VAX 9000 computers, standalone BACKUP resides on the console hard disk. Because the boot process is slightly different for each type of controller, each supported controller has a unique boot command procedure. Refer to the upgrade and installation supplement for your VAX 9000 computer for instructions for booting standalone BACKUP on your system. 4. During an InfoServer boot, the procedure prompts you for a file name that contains an initial system load (ISL) boot program instead of a virtual memory boot (VMB) program. Select one of the two files as follows: o ISL_SVAX_071 o ISL_LVAX_071 Use the following table to determine which file name and boot path designator to use for your processor. Note that the VAX 9000 computer has the ISL file data built in its VMB image that runs from the console. ________________________________________________________ Processor Series________ISL_File________Boot_Path_Designator______ VAX 3000 ISL_SVAX_071 ESA0 (LANCE), XQA0 (DELQA) VAX 4000 ISL_SVAX_071 EZA0 (SGEC), XQA0 (DELQA) VAX 6000 ISL_LVAX_071 EXA0 (DEMNA), FXA0 (DEMFA), ETA0 (DEBNI) (DEBNA) VAX 7000 ISL_LVAX_071 EXA0 (DEMNA), FXA0 (DEMFA) VAX 10000 ISL_LVAX_071 EXA0 (DEMNA), FXA0 (DEMFA) MicroVAX ISL_SVAX_071 ESA0 (LANCE), XQA0 (DELQA) VAXstation ISL_SVAX_071 ESA0 (LANCE) VAXft 110, ISL_SVAX_071 EPA0 (LANCE) 310, 410, 610, and 612 _________________________________________________________________ Installing the OpenVMS VAX Operating System 3-3 Installing the OpenVMS VAX Operating System 3.2 Booting Standalone BACKUP On a VAX 6000 computer, you would respond to the prompt as shown in the following example: Loading system software. Filename: ISL_LVAX_071 5. 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: If you need more information, select function ID 2 for help. 6. After you boot standalone BACKUP, the system displays the following: %BACKUP-I-IDENT, standalone BACKUP V6.2; the date is 22-NOV-1996 15:00 $ After you have booted standalone BACKUP, go to Section 3.3. 3.2.3 BOOTING OPENVMS FROM THE CD-ROM If you are installing from the OpenVMS VAX operating system CD-ROM (your VAX computer supports booting from a local CD-ROM or from an InfoServer), you can use the full OpenVMS environment instead of the standalone BACKUP environment to transfer the VMS071.B save set to your target system disk. Although it may take slightly longer to boot OpenVMS than to boot standalone BACKUP, you might prefer the more robust OpenVMS environment. It provides a greater range of commands and utilities than the standalone BACKUP environment. 3-4 Installing the OpenVMS VAX Operating System Installing the OpenVMS VAX Operating System 3.2 Booting Standalone BACKUP If you want to use the full OpenVMS environment, do the following: 1. Boot the CD-ROM and specify root 1. For example, from a local drive on a VAXstation 4000 computer: >>> B/1000000 DKA400: If you are booting from an InfoServer device, enter a command that specifies root 1. For example, on a VAX 6000 computer: >>> B/R5:10000100/X:D/B:6 ET0 2. After you boot the OpenVMS CD-ROM, the system displays the following menu: 1) Execute DCL commands and procedures 2) Shut down this system Choose option 1 to execute DCL commands and procedures. Note that the system displays a triple dollar sign ($$$) DCL prompt to indicate that you are in this specialized DCL environment. 3. Go to Section 3.3.3. 3.3 Creating the System Disk You create an OpenVMS VAX Version 7.1 system disk by transferring OpenVMS VAX files from the distribution media to your system disk. (For certain files, you have the option to transfer the files to your system disk or to an alternate disk.) To transfer the OpenVMS VAX files from the distribution kit to your system disk, perform the steps described in the sections that follow. 3.3.1 STEP 1: DETERMINE DEVICE NAMES If you have not already done so, determine the device names for the source drive, the target drive, and an alternate device if you will be using one. Write these names on a piece of paper. You will need this information throughout the installation. If either the source drive or the target drive is connected to an HSC, you also need the Installing the OpenVMS VAX Operating System 3-5 Installing the OpenVMS VAX Operating System 3.3 Creating the System Disk name of the HSC. (To determine the value for hsc-name, see Section 2.4.3 in Chapter 2.) If you need more information about determining the device names for your system, refer to the upgrade and installation supplement for your VAX computer. 3.3.2 STEP 2: LOAD DISTRIBUTION MEDIA Each piece of media in the distribution kit has a label that indicates its contents. Place the media that contains the OpenVMS VAX operating system in the source-drive. If your OpenVMS VAX distribution kit consists of more than one piece of media, insert the first piece of media in the source-drive. For example, if you have a TK50 tape cartridge kit, make sure the first tape is in the source- drive. If you are installing from a compact disc, it is already in the drive. 3.3.3 STEP 3: TRANSFER VMS071.B TO YOUR SYSTEM DISK Enter a BACKUP command in the following format to transfer the VMS071.B save set to your system disk: $ BACKUP/IMAGE/VERIFY [hsc-name]source-drive:VMS071.B/SAVE_SET- _$ [hsc-name]target-drive: Substitute the appropriate device names for hsc-name (if appropriate), source-drive, and target-drive. Make sure you put a colon (:) after each device name and that you use zeros rather than the letter "O" in the device names and in VMS071. The square brackets ([]) indicate that you need the hsc- name only if the device is connected to an HSC. For example, if your system has a source-drive that is a local TU80 magnetic tape drive with a device name of MUA0 and a target-drive that is an RA82 disk drive with a device name of DUA1, enter the following command and press the Return key: $ BACKUP/IMAGE/VERIFY MUA0:VMS071.B/SAVE_SET DUA1: 3-6 Installing the OpenVMS VAX Operating System Installing the OpenVMS VAX Operating System 3.3 Creating the System Disk If your system has a source-drive that is a local tape cartridge drive with a device name of MUC6 or a target- drive that is an RA81 disk drive with a device name of DUA1 and an HSC name of YOURS, enter the following command and press Return: $ BACKUP/IMAGE/VERIFY MUC6:VMS071.B/SAVE_SET YOURS$DUA1: The procedure transfers the VMS071.B save set from the distribution kit to the system disk.[1] The amount of time this takes varies depending on the type of VAX computer and distribution media you have. During the process, the command displays the following message: %BACKUP-I-STARTVERIFY, starting verification pass This message indicates that the VMS071.B save set has been transferred to the system disk and the files are being checked for errors. If, instead, you see a message similar to the following, you might have the wrong volume of the distribution kit in the source drive: % BACKUP-F-OPENIN, error opening MUA0:[000000]VMS071.B; as input - SYSTEM-W-NOSUCHFILE, no such file . . . If you do want to perform another standalone BACKUP operation, ensure the standalone BACKUP volume is online and ready. Enter "YES" to continue: If the procedure displays the previous messages, remove the distribution volume from the drive and replace it with the correct volume as described in Step 2. Then type Yes, press Return, and repeat this step. ____________________ [1] The BACKUP command creates a system disk that includes a set of volume parameters provided by Digital, including CLUSTER_SIZE (disk access scheme). For more information, see the upgrade and installation supplement for your VAX computer. Installing the OpenVMS VAX Operating System 3-7 Installing the OpenVMS VAX Operating System 3.3 Creating the System Disk Completing the Transfer Operation Complete the transfer of the VMS071.B save set to your system disk by performing one of the following operations: o If you are using standalone BACKUP to transfer the VMS071.B save set, the procedure displays the following message, when it has completed checking files: %BACKUP-I-PROCDONE, Operation completed. Processing finished at 22-NOV-1996 15:00. If you do not want to perform another standalone BACKUP operation, use the console to halt the system. If you do want to perform another standalone BACKUP operation, ensure the standalone application volume is online and ready. Enter "YES" to continue: Enter NO and go to step 4 (Section 3.3.4) to boot the new system disk. o If you are using the specialized OpenVMS environment to transfer the VMS071.B save set, the system displays the triple dollar sign prompt ($$$) DCL prompt after the BACKUP operation completes. Enter the command LOGOUT to return to the menu. For example: $$$ LOGOUT 1) Execute DCL commands and procedures 2) Shut down this system You can then choose option 2 to shut down the system in preparation for booting the new system disk, as described in step 4 (Section 3.3.4). 3.3.4 STEP 4: BOOT THE NEW SYSTEM DISK Halt the system and boot the new system disk, as described in the upgrade and installation supplement for your VAX computer. When the boot is completed, the procedure displays a message and prompts you to enter the date and time. Enter the date and time using the 24-hour clock format and press Return. 3-8 Installing the OpenVMS VAX Operating System Installing the OpenVMS VAX Operating System 3.3 Creating the System Disk For example: OpenVMS (TM) VAX Version 7.1 Major version id = 1 Minor version id = 0 OpenVMS VAX V7.1 Installation Procedure Model: VAX 4000-300 System device: RF73 - _DUA8 Free blocks: 1170940 CPU type: 11-01 * Please enter the date and time (DD-MMM-YYYY HH:MM):22-NOV-1996 15:35 ******************************************************** %SYSTEM-W-TZGMT, your local timezone has defaulted to GMT %SYSTEM-I-SETTZ, to set your local timezone use: $ @SYSMANAGER:UCT$TIME_SETUP.COM ********************************************************* STDRV-I-STARTUP, VMS startup begun at 22-NOV-1996 15:00:00.59 %SET-I-NEWAUDSERV, identification of new audit server process is 00000028 . . . %%%%%%%%%%% OPCOM 22-NOV-1996 15:00:15.46 %%%%%%%%%%% Message from user JOB_CONTROL on POKIPC %JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT %%%%%%%%%%% OPCOM 22-NOV-1996 15:00:15.41 %%%%%%%%%%% Message from user JOB_CONTROL on POKIPC -SYSTEM-W-NOSUCHFILE, no such file LICENSE-F-EMTLDB, license database contains no license records %LICENSE-E-NOAUTH, DEC VAX-VMS use is not authorized on this node -%LICENSE-F-NOLICENSE, no license is active for this software product -%LICENSE-I-SYSMGR, please see your system manager Startup processing continuing... %STDRV-I-STARTUP, VMS startup begun at 22-NOV-1996 15:03:00.00 ________________________ Note ________________________ You can ignore the time zone message. The UTC$TIME_SETUP.COM procedure runs during the final phase of the installation procedure. ______________________________________________________ Installing the OpenVMS VAX Operating System 3-9 Installing the OpenVMS VAX Operating System 3.3 Creating the System Disk The procedure also displays OPCOM messages from JOB_CONTROL stating the master queue file QMAN$MASTER.DAT does not exist. You can ignore these messages. You will create the queue file later. You can also ignore error messages stating that the OpenVMS VAX license is not registered. License registration occurs later in the procedure. For more information about registering your licenses, see Appendix B and the OpenVMS License Management Utility Manual. 3.3.5 STEP 5: SPECIFY THE VOLUME LABEL The procedure prompts you to specify the volume label of the system disk. A volume label is the name the OpenVMS VAX operating system uses to refer to the system disk. You can press the Return key to accept the default volume label, OpenVMS071, or you can enter a volume label of your choice. The volume label can be 1 to 12 characters long; do not use spaces. For example: If this system disk is to be used in a cluster with multiple system disks, then each system disk must have a unique volume label. Any nodes having system disks with duplicate volume labels will fail to boot into the cluster. You can indicate a volume label of 1 to 12 characters in length. If you want to use the default name of OpenVMS071, press Return in response to the next question. * Enter the volume label for this system disk [OpenVMS071]: SYSDSK1 3.3.6 STEP 6: SPECIFY THE SOURCE DRIVE The procedure prompts you to specify which drive holds the distribution kit. Enter the device name for the source drive. For example, if you are not using the InfoServer and the source drive is a magnetic tape drive with the device name MUA0, type MUA0 and press Return. * Enter the name of the drive holding the OpenVMS distribution media: MUA0 * Is the OpenVMS media ready to be mounted? [N] YES %MOUNT-I-MOUNTED, VMS071 mounted on _MUA0: If you are not using the InfoServer, continue to Section 3.3.7. 3-10 Installing the OpenVMS VAX Operating System Installing the OpenVMS VAX Operating System 3.3 Creating the System Disk If you are using an InfoServer, enter DAD1:. * Enter the volume label for this system disk [OpenVMS071]: SYSDSK1 * Enter name of drive holding the OpenVMS distribution media: DAD1: The procedure then prompts you to: * Enter the InfoServer service name [VAXVMS071]: * Enter the InfoServer work group number [0]: Press the Return key as a response to both of these prompts. The InfoServer work group number was determined when you made a selection from the menu displayed by the InfoServer ISL program (refer to Section 3.2). If the answer to the group number is incorrect, the procedure displays the following: InfoServer work group number must be in the range 0-1023. The procedure then prompts you: * Is the OpenVMS media ready to be mounted? [N]: Y %MOUNT-I-MOUNTED, VMS071 mounted on _DAD1: 3.3.7 STEP 7: SELECT OPTIONAL OPENVMS COMPONENTS The procedure displays information about OpenVMS VAX files that are optional and about the remaining amount of disk space. The information is similar to the following (block sizes might vary slightly): Select optional software you want to install. You can install one or more of the following OpenVMS or DECwindows components: o OpenVMS library - 53400 blocks o OpenVMS optional - 21200 blocks o OpenVMS Help Message - blocks o OpenVMS Management Station - 21200 blocks o DECwindows base support - 3800 blocks o DECwindows workstation support - 23500 blocks - 75 dots per inch video fonts - (included) - 100 dots per inch video fonts - 6000 blocks o DECnet-Plus networking - 85000 blocks Space remaining on system disk: 1170752 blocks You must indicate which of the options you want to install. If you require network support, you must select the OpenVMS Installing the OpenVMS VAX Operating System 3-11 Installing the OpenVMS VAX Operating System 3.3 Creating the System Disk library component. Note that, if you do not install the optional components at this time, you can install them after the installation by using the VMSTAILOR or DECW$TAILOR utility. However, the Help Message utility can be tailored on to the system disk only. If you want to install Help Message on an alternate disk, you must install it now or install it after the installation procedure completes by entering the following BACKUP command: BACKUP/VERIFY source-device:[000000]VMS071.E/SAVE_SET - target-device:[directory-name] For source-device, enter the device name for the drive on which the distribution media is mounted. For target- device, enter the device name on which the alternate disk is mounted, and for directory-name, enter the name of the directory to which you are copying the files. Also note that, for TK50 tape cartridges, it is quicker to install OpenVMS VAX software during the installation than to add software after the installation with a tailoring utility. For information about using VMSTAILOR, see Chapter 10. To select the options you want to install, follow the instructions displayed by the procedure. 3.3.8 OPENVMS LIBRARY FILES The procedure displays the following message: * Do you want to install the OpenVMS library files? (Y/N) The file subclasses of the VMS071.C save set are listed in Appendix D. If you want to install the VMS071.C files, type Y (for YES) and press Return. If you require network support, you must select the OpenVMS library component. If you do not want to install the VMS071.C files, type N (for NO) and press Return. 3-12 Installing the OpenVMS VAX Operating System Installing the OpenVMS VAX Operating System 3.3 Creating the System Disk 3.3.9 OPENVMS OPTIONAL FILES The procedure displays the following message: * Do you want to install the OpenVMS optional files? (Y/N) The file subclasses of the VMS071.D save set are listed in Appendix D. If you want to install the VMS071.D files, type Y and press Return. If you do not want to install the VMS071.D files, type N and press Return. 3.3.10 HELP MESSAGE FILES The procedure displays the following message: The Help Message utility (MSGHLP) provides online explanations and user actions for OpenVMS messages in place of the hardcopy OpenVMS System Messages and Recovery Procedures Reference Manual, which is now separately orderable. The MSGHLP database, MSGHLP$LIBRARY.MSGHLP$DATA, consumes approximately 10200 blocks and will be placed by default on your system disk in SYS$COMMON:[SYSHLP] unless you specify an alternate device when prompted. Users with limited disk space can access the MSGHLP database on a read-only basis at DAD1:[HELP_MESSAGE]. * Do you want to install the MSGHLP database? (Y/N) The Help Message utility is an online system for system messages documentation. You can install Help Message either on the system disk or on an alternate disk. If you want to install the Help Message files, type Y and press Return. The procedure displays the following message: You can install this database on your system disk in SYS$COMMON:[SYSHLP] or on an alternate device. If you specify an alternate device, but no directory, MSGHLP$LIBRARY.MSGHLP$DATA is placed in [HELP_MESSAGE]. When prompted, take the default of the system disk or specify an alternate device, using this format: device:[directory] * Where do you want to install the MSGHLP database?[SYS$COMMON:[SYSHLP]] DUA1 The Help Message database is installed in the area you specify, and the system displays information similar to the following: Installing the OpenVMS VAX Operating System 3-13 Installing the OpenVMS VAX Operating System 3.3 Creating the System Disk Space remaining on alternate device DUA1: 124532 blocks 3.3.11 OPENVMS MANAGEMENT STATION FILES The procedure displays the following message: The OpenVMS Management Station is a client-server application that provides OpenVMS system management capabilities through a client application on a personal computer (PC) running Microsoft Windows. The server application runs on OpenVMS systems and is automatically installed as part of the OpenVMS operating system. This option provides the files used to create the installation media for the PC client software. If you want to use the OpenVMS Management Station, you must install these files on at least one OpenVMS system to create the installation media, which can then be used to install the PC client on one or more PCs. Note: To use the OpenVMS Management Station on your PC, you must be running Digital's PATHWORKS V5.0A for DOS and Windows (or V5.1) software. The OpenVMS Management Station optional files consume approximately 212000 blocks and will be placed on your system disk in SYS$COMMON:[TNT.CLIENT]. * Do you want to install the optional OpenVMS Management Station files? (Y/N) Space remaining on system disk: 623240 blocks If you want to use the OpenVMS Management Station software, you must install these files. After the installation procedure completes, follow the instructions in Appendix G to prepare your OpenVMS system and your PC to run the OpenVMS Management Station server and client software. 3.3.12 STEP 8: CHOOSE DECWINDOWS SUPPORT OPTIONS Next, the procedure displays messages about the DECwindows components shipped with OpenVMS VAX Version 7.1. ________________________ Note ________________________ The OpenVMS VAX operating system no longer ships the VMS DECwindows product. The operating system now ships only the DECwindows base support and DECwindows workstation support components. To get full DECwindows support, you must also install the separate DECwindows Motif for OpenVMS (previously called VMS DECwindows 3-14 Installing the OpenVMS VAX Operating System Installing the OpenVMS VAX Operating System 3.3 Creating the System Disk Motif) layered product, which supports both Motif and XUI environments. The DECwindows base support and DECwindows workstation support components are not shipped with the layered product. If you want to install these options, you must select them now or use the DECW$TAILOR option after the installation procedure completes. ______________________________________________________ Before you indicate whether you want to install DECwindows support software, consider the following: ___________________________________________________________ If you... Then choose... Intend to install the DECwindows base support. DECwindows Motif layered product Intend to install the DECwindows base support DECwindows Motif layered and DECwindows workstation product on a workstation or support. on a VAXcluster system that contains workstations Are not planning to install DECwindows base support and the DECwindows Motif layered DECwindows workstation product but are installing support. OpenVMS VAX on a workstation or on a VAXcluster that includes workstations Want to provide font files DECwindows base support for X terminals and DECwindows workstation support. Installing the OpenVMS VAX Operating System 3-15 Installing the OpenVMS VAX Operating System 3.3 Creating the System Disk ___________________________________________________________ If you... Then choose... Have a workstation monitor DECwindows base support (for example, a VR150, and DECwindows workstation VR160, or VR295) capable support with the 100 dots of displaying 100 dots/inch /inch option. or a VAXstation 4000 series By selecting the workstation computer, which uses 100 support files, you dots/inch video fonts by automatically get 75 dots default /inch video font files, and you will be prompted to indicate if you want to install 100 dots/inch video font files. ___________________________________________________________ The procedure displays the following: You can select DECwindows support now, or you can use the DECW$TAILOR utility to provide or remove DECwindows support after the installation. Some media, TK50s in particular, can be very slow when tailoring on files. You might want to provide DECwindows options now and tailor off unwanted files later. NOTE: This kit does NOT contain full DECwindows. To obtain full DECwindows support, you must also install the separate layered product, DECwindows Motif for OpenVMS VAX. Version 1.2-3 is the minimum version of DECwindows Motif for OpenVMS VAX that can be used with OpenVMS VAX Version 7.1. The DECwindows components provided in this kit require approximately 33300 blocks, broken down as follows: o DECwindows base support - 3800 blocks o DECwindows workstation support - 23500 blocks - 75 dots per inch video fonts (included) - 100 dots per inch video fonts (optional) - 6000 blocks You must select the DECwindows base support option if - you plan to run DECwindows software, or - you are installing this kit on * a workstation or * a VAXcluster that contains workstations, or - you want to provide font files for Xterminals. 3-16 Installing the OpenVMS VAX Operating System Installing the OpenVMS VAX Operating System 3.3 Creating the System Disk If you are installing this kit on a system that includes Xterminals and you do not select DECwindows base support, then you will have to use the DECW$TAILOR utility to provide font files. * Do you want the DECwindows base support? (Y/N) Space remaining: 612725 You must select the DECwindows workstation support option if - you are installing this kit on * a workstation or * a VAXcluster that contains workstations, or - you want to provide font files for Xterminals. If you are installing this kit on a system that includes Xterminals and you do not select DECwindows base support, then you will have to use the DECW$TAILOR utility to provide font files. * Do you want to provide DECwindows workstation support? (Y/N) Space remaining: 591975 DECwindows workstation support includes the 75 dots per inch video fonts. All DECwindows applications run with 75 dots per inch video fonts. By default, most systems start up with 75 dots per inch video fonts. Certain applications can take advantage of 100 dots per inch video fonts. For the VAXstation 4000 series machine, 100 dots per inch video fonts are used by default. If you decide not to install 100 dots per inch video fonts, you must edit SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM to force 75 dots per inch video fonts to be the default. Otherwise, certain applications may not space text properly. For instructions on how to configure your system with both 75 and 100 dots per inch video fonts, see the template command procedure SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE. *Do you want 100 dots per inch video fonts installed? (Y/N) Space remaining: 541975 Installing the OpenVMS VAX Operating System 3-17 Installing the OpenVMS VAX Operating System 3.3 Creating the System Disk 3.3.13 STEP 9: SELECT DECNET PRODUCT Next, the procedure displays messages describing the DECnet options. For more information, refer to Section 1.2.1. Beginning with OpenVMS V7.1 DECnet-Plus is provided with the OpenVMS operating system. Digital strongly recommends that DECnet users install DECnet-Plus. DECnet Phase IV applications are supported by DECnet-Plus. If you plan to install DECnet Phase IV do NOT select DECnet-Plus. * Do you want to install DECnet-Plus. (Y/N) Y Space remaining on system disk: 456975 blocks If you want to install DECnet Phase IV, you must do so after the OpenVMS VAX installation procedure completes. 3.3.14 STEP 10: VERIFY YOUR CHOICES The procedure displays a list of OpenVMS VAX and DECwindows support options you have selected and gives you the opportunity to change your mind before proceeding by displaying the following message: * Is this correct? (Y/N) If you answer No to this prompt, you can respecify the OpenVMS and DECwindows support options you want to install. 3.3.15 STEP 11: INSTALL OPENVMS OPTIONS If you answer Yes to the prompt in step 9, the installation procedure begins restoring the OpenVMS options you have selected. After the installation has completed, you can use the VMSTAILOR utility to remove any optional OpenVMS files that you do not need. (For more information about using VMSTAILOR, see Chapter 10.) This step in the procedure will vary, depending on whether your distribution kit is on compact disc, tape cartridges, or magnetic tapes. 3-18 Installing the OpenVMS VAX Operating System Installing the OpenVMS VAX Operating System 3.3 Creating the System Disk 3.3.16 COMPACT DISC If your distribution kit is on compact disc, leave the disc in the drive. The procedure displays messages as it restores each of the OpenVMS options you have chosen to install. 3.3.17 TAPE CARTRIDGES AND 9-TRACK OPEN REEL MAGNETIC TAPES If your distribution kit is on TK50 tape cartidges or 9- track open reel magnetic tapes, you may be asked to mount additional volumes of the kit. In such a case, your system will display a message similar to the following: Please mount volume of the OpenVMS kit on where: is the volume number and is the cartridge tape drive or open reel tape drive. After you respond to the prompt, the system displays one of the following messages: o For a TK50 tape cartidge, the message is similar to the following: * Is the volume labeled OVMS VAX V7.1 BIN TK50 2/2 ready to be mounted? o For 9-track open reel tape, the message is similar to the following: * Is the volume labeled OVMS VAX V7.1 BIN MT9 n/4 ready to be mounted? where: n/4 may be 2/4, 3/4 or 4/4. To respond to either message, do the following: 1. Unload the volume currently in the drive. 2. Examine the remaining volumes and select the one with the label that matches the label specified in the prompt. 3. Load the volume and make the drive ready. 4. Answer YES to the question. For information on which save sets are located on which tape volumes, Section 1.4.1 and Section 1.4.2. Installing the OpenVMS VAX Operating System 3-19 Installing the OpenVMS VAX Operating System 3.3 Creating the System Disk Step 12: Install DECwindows Support Software If you are installing DECwindows software, the procedure installs the DECwindows options that you specified and displays messages similar to the following: Restoring DECwindows base support save set ... %BACKUP-I-STARTVERIFY, starting verification pass Restoring DECwindows workstation support save set ... %BACKUP-I-STARTVERIFY, starting verification pass Restoring DECwindows 75 dots per inch fonts save set ... %BACKUP-I-STARTVERIFY, starting verification pass Restoring DECwindows 100 dots per inch fonts save set ... %BACKUP-I-STARTVERIFY, starting verification pass The DECwindows support files are listed in Appendix E. After you finish the installation, you can use the DECwindows tailoring utility, DECW$TAILOR, to remove the DECwindows files you do not need. For more information about removing files with DECW$TAILOR, see Chapter 10. If your distribution media is tape cartridges or magnetic tape, the procedure displays a message similar to the following after the DECwindows options you have selected have been successfully installed: You can now remove the DECwindows distribution kit from MUA0:. Remove the distribution media from the drive. If your distribution media is compact disc leave it in the drive. 3.4 Configuring a Cluster The installation procedure now displays information about cluster configuration. But, because there is no network present on the system at this point in the procedure, no cluster configuration work can actually be performed at this time. 3-20 Installing the OpenVMS VAX Operating System Installing the OpenVMS VAX Operating System 3.4 Configuring a Cluster In a cluster, you can run multiple systems sharing all files except PAGEFILE.SYS, SWAPFILE.SYS, SYSDUMP.DMP, and VAXVMSSYS.PAR. Cluster configuration cannot be done at this time because no network is present. In order to configure a cluster, you must FIRST do one or both of the following: o Install DECnet-Plus (or DECnet Phase IV), or o Execute SYS$STARTUP:LAN$STARTUP.COM by removing the comment delimiter ("!") from the line $! @ SYS$STARTUP:LAN$STARTUP.COM in SYS$MANAGER:SYSTARTUP_VMS.COM. Then configure the cluster by executing the following command: @SYS$MANAGER:CLUSTER_CONFIG.COM Once the network is running on your system, you can execute the SYS$MANAGER:CLUSTER_CONFIG.COM command procedure in configure your cluster. For more information about cluster configuration, see the OpenVMS System Manager's Manual: Essentials. 3.5 Setting Passwords Next, the installation procedure prompts you to set passwords for the SYSTEM, SYSTEST, and FIELD accounts and uses this information to create a rights database. When setting the passwords, remember: o Passwords must be 8 characters or more. o Passwords are not displayed by the system while you are entering them. o Press Return after you enter each password. o Each password is verified. Use the following procedure to set passwords: 1. Supply the passwords when prompted by the installation procedure, as follows: Installing the OpenVMS VAX Operating System 3-21 Installing the OpenVMS VAX Operating System 3.5 Setting Passwords Now we will ask you for new passwords for the following accounts: SYSTEM, SYSTEST, FIELD Passwords must be a minimum of 8 characters in length. All passwords will be checked and verified. Any passwords that can be guessed easily will not be accepted. * Enter password for SYSTEM: * Re-enter for verification: %UAF-I-MDFYMSG, user record(s) updated %VMS-I-PWD_OKAY, account password for SYSTEM verified * Enter password for SYSTEST: * Re-enter for verification: %UAF-I-MDFYMSG, user record(s) updated %VMS-I-PWD_OKAY, account password for SYSTEST verified The SYSTEST_CLIG account will be disabled. You must re-enable it before running UETP but do not assign a password. * Enter password for FIELD: * Re-enter for verification: %UAF-I-MDFYMSG, user record(s) updated %VMS-I-PWD_OKAY, account password for FIELD verified 2. If there are no password errors, the procedure creates your rights database, and you can proceed to the next section. If you enter a password incorrectly or if the password is too easy to guess, the procedure displays error messages similar to the following: %VMS-I-PWD_INVALID, account password for SYSTEST is invalid %VMS-I-PWD_WEAK, password is too easy to guess Because of the preceding error, you must take action to secure this account. You must either disable this account, change its password, or do both. 3. When the procedure asks if you want to disable the account, type N and press Return. When the procedure asks if you want to enter a new password, type Y and press Return. Then enter a new password. For example: 3-22 Installing the OpenVMS VAX Operating System Installing the OpenVMS VAX Operating System 3.5 Setting Passwords Do you want to disable this account (Y/N)? N Do you want to change the account password (Y/N)? Y You must now select a new primary password for the SYSTEST account. The password you select must be at least 8 characters in length and cannot be the same as the name of the account: New password: Verification: %UAF-I-MDFYMSG, user record(s) updated %VMS-I-PWD_SET, primary password for account SYSTEST set 4. When you have successfully set the passwords, the installation procedure creates your rights database, which lets you manage user access to the system, and displays the following message: Creating RIGHTS database file, SYS$SYSTEM:RIGHTSLIST.DAT Ignore any "-SYSTEM-F-DUPIDENT, duplicate identifier" errors . . . 3.6 Entering SCSNODE and SCSSYSTEMID Parameters If you are installing a standalone system, the procedure displays the following prompts: * Please enter SCSNODE name * Please enter SCSSYSTEMID Enter the SCSNODE name and SCSSYSTEMID that you determined as part of the preinstallation tasks in Chapter 2. If you are installing the operating system in a VAXcluster environment, you are not prompted to supply these parameters. The procedure calculates these parameters using the DECnet node name and node address you supplied earlier in the procedure. Installing the OpenVMS VAX Operating System 3-23 Installing the OpenVMS VAX Operating System 3.7 Postinstallation Tasks Described 3.7 Postinstallation Tasks Described After the procedure creates the rights database, it displays messages describing postinstallation tasks you might want to perform. Note that you do not perform these tasks now but after the installation completes. The tasks displayed on your screen might vary from the following example, depending on what options you chose to install earlier in the procedure. After the installation finishes, you might want to do one or more of the following tasks: o DECOMPRESS THE SYSTEM LIBRARIES - To save space, many of the system libraries are shipped in a data-compressed format. If you have enough disk space, you can decompress the libraries for faster access. To data expand the libraries, type: $ @SYS$UPDATE:LIBDECOMP.COM If you do not decompress these libraries, you will experience slower response with the HELP and LINK commands. o BUILD A STANDALONE BACKUP KIT - You can build a standalone backup kit using the procedure described in the upgrade and installation supplement supplied for your VAX computer. o TAILOR THE SYSTEM DISK - You might want to review the files provided or not provided during this installation. If you find there are files you want to remove from the system disk (TAILOR OFF) or files you want to add (TAILOR ON), use the following utilities to perform the desired tailoring. OpenVMS tailoring: $ RUN SYS$UPDATE:VMSTAILOR DECwindows tailoring: $ RUN SYS$UPDATE:DECW$TAILOR Note: The tailor procedure cannot be used to TAILOR ON or to TAILOR OFF files located on an alternate device. o DEFINE A LOGICAL NAME - Define the logical name MSGHLP$LIBRARY in your site-specific startup file to be: DUA1:[HELP_MESSAGE] to point to the new location of the MSGHLP database. For more information about decompressing the system libraries, see Section 4.8 in Chapter 4. For information on using VMSTAILOR or DECW$TAILOR, see Chapter 10. 3-24 Installing the OpenVMS VAX Operating System Installing the OpenVMS VAX Operating System 3.7 Postinstallation Tasks Described After the messages about postinstallation tasks are displayed, the procedure displays a message similar to the following: Continuing with OpenVMS VAX V7.1 installation procedure. Configuring all devices on the system... Proceed to the next section for information about registering your licenses. 3.8 Registering Licenses Before you can use the OpenVMS VAX operating system and its components, you must first register all licenses. If you do not register your licenses at this point in the procedure, you must register them immediately after the installation, before you perform the other postinstallation tasks. 3.8.1 TYPES OF LICENSES The OpenVMS VAX operating system uses one of two different categories of licenses, depending on the hardware and software configuration used and currently supported. The two categories of operating system licenses for OpenVMS VAX are: o VAX VMS licensing o OpenVMS VAX licensing The following table describes the types of licenses for each licensing category. Digital provides the proper license type with the purchase of the system. Not all license types are available for every system model. _________________________________________________________________ Type_of_License_______Description________________________________ ________________________VAX_VMS_Licenses_________________________ Traditional License Provides unlimited use to the users on a defined system. VAX VMS traditional licenses are sized to capacity according to system type. Installing the OpenVMS VAX Operating System 3-25 Installing the OpenVMS VAX Operating System 3.8 Registering Licenses _________________________________________________________________ Type_of_License_______Description________________________________ _________________________VAX_VMS_Licenses________________________ Multi-User License Provides use according to a specified number of concurrent users. This is an activity-based license. The Multi-user License gives you the right to use the operating system for up to the limit of users specified in the license. An operating system user is one who is logged in to the system or one who is using the operating system software by means other than login, or both. This license is available only on limited system models, primarily MicroVAX and VAX 4000 systems. Interactive use of VAX systems licensed with the Multi-user License can be increased by the addition of the OpenVMS VAX Individual User License[1] for one or more users. For more information, refer to the description of the OpenVMS VAX Individual User License later in this table. VAX VMS Workstation Provides use for a single user on a VAX License workstation. This license type allows one direct login for the single user and then one additional login for system management purposes only. Additional interactive use of VAX workstations licensed with the VAX VMS Workstation License requires the addition of an OpenVMS VAX User License[1] for one or more users. For more information, refer to the description of the OpenVMS VAX Individual User License later in this table. [1]The OpenVMS VAX Individual User License is not supported by the VMS or OpenVMS VAX operating system releases prior to VMS Version 5.5. 3-26 Installing the OpenVMS VAX Operating System Installing the OpenVMS VAX Operating System 3.8 Registering Licenses _________________________________________________________________ Type_of_License_______Description________________________________ ________________________VAX_VMS_Licenses_________________________ File and Application Provides for the noninteractive use of Server License OpenVMS VAX. OpenVMS based VAXservers are sold with a File and Application Server License. The intent of an OpenVMS based VAXserver is to provide file, print, application, and compute services to clients who have remotely submitted their requests for these services. This license type also allows one direct login for system management purposes only. Additional interactive use of OpenVMS VAXservers licensed with the File and Application Server License requires the addition of an OpenVMS VAX User License[1] for one or more users. For more information, refer to the description of the OpenVMS VAX Individual User License later in this table. ___________________________________________________________ [1]The OpenVMS VAX Individual User License is not supported by the VMS or OpenVMS VAX operating system releases prior to VMS Version 5.5. Installing the OpenVMS VAX Operating System 3-27 Installing the OpenVMS VAX Operating System 3.8 Registering Licenses _________________________________________________________________ Type_of_License_______Description________________________________ _______________________OpenVMS_VAX_Licenses______________________ OpenVMS VAX O/S Base Provides the right to unrestricted, License[2] noninteractive use of the OpenVMS VAX operating system for the execution of remotely submitted requests for batch, print, application, and computing services, on a designated, single processor. No direct OpenVMS VAX operating system logins by users are permitted on the system. One direct login is allowed for system management purposes only. Interactive use of systems licensed with an OpenVMS VAX O/S Base License requires the addition of an OpenVMS VAX Individual User License[1] for one or more users. OpenVMS VAX Provides the right to interactively use Individual User the operating system by a specified, or License[1] unlimited, number of concurrent users on a designated, single processor. A user is one who is logged in to a processor or one who is interactively using the operating system software by means other than login, or both. An OpenVMS VAX O/S Base License, or any of the four types of VAX VMS Licenses, is a prerequisite for the OpenVMS VAX Individual User License. __________________________________________________________________ [1]The OpenVMS VAX Individual User License is not supported by the VMS or OpenVMS VAX operating system releases prior to VMS Version 5.5. [2]The OpenVMS VAX O/S Base License is not supported by the VMS or OpenVMS VAX operating system releases prior to VMS Version 5.5. 3-28 Installing the OpenVMS VAX Operating System Installing the OpenVMS VAX Operating System 3.8 Registering Licenses 3.8.2 HOW TO REGISTER YOUR LICENSES You must register your licenses in the following order: 1. Register the OpenVMS VAX license for the VAX computer on which you have just installed the operating system. If you have a VAXcluster environment, you then register an OpenVMS VAX license for each additional VAX computer in the cluster that will boot off the system disk that you just created. Each registered OpenVMS VAX license must be assigned to one of the nodes for the cluster. 2. Register the licenses for any System Integrated Products (SIPs) that you purchased. For more information about registering licenses, see the following: o OpenVMS License Management Utility Manual, which provides: - Details about all LICENSE commands, error messages, and recovery procedures for licensing tasks - A description of VMSLICENSE.COM, with step-by-step instructions for registering licenses - Examples of license registration using VMSLICENSE.COM and LICENSE REGISTER commands o Appendix B of this manual for notes and supplemental information concerning licenses You can use the SYS$UPDATE:VMSLICENSE.COM procedure to register a license for any Digital product that supplies a Product Authorization Key (PAK). Or, you can register licenses with the LICENSE REGISTER command. See the OpenVMS License Management Utility Manual for detailed information. 3.8.3 HOW TO REGISTER OPENVMS VAX LICENSES The installation procedure displays the following message: If you have any Product Authorization Keys (PAKS) to register, you can register them now. * Do you want to register any Product Authorization Keys? (Y/N) Installing the OpenVMS VAX Operating System 3-29 Installing the OpenVMS VAX Operating System 3.8 Registering Licenses ___________________________________________________________ If you choose ... Then ... Not to register the Do the following: licenses at this time 1. Type N and press Return. 2. Go to Section 3.11. 3. Remember that, after the installation, you must register your licenses before performing any other postinstallation tasks (see Chapter 4). To register your Do the following: licenses now 1. Type Y and press Return. 2. Be sure you have a copy of your PAK for each license you will register. 3. Go to the next section to begin the licensing procedure. ___________________________________________________________ By typing Y (Yes) to register your licenses now, you invoke the SYS$UPDATE:VMSLICENSE.COM procedure, which displays the following message: OpenVMS 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. 3-30 Installing the OpenVMS VAX Operating System Installing the OpenVMS VAX Operating System 3.8 Registering Licenses Enter one of the above choices [1] Select the appropriate options (beginning with 1, as shown) until you have successfully registered all required PAKs. 3.8.4 HOW TO REGISTER SYSTEM INTEGRATED PRODUCTS After you register the OpenVMS VAX license, you must register the license for any of the following System Integrated Products (SIPs) you have purchased: o VAXcluster (LMF Product Name: VAXCLUSTER) o DECnet-Plus There are two DECnet-Plus licenses: - The end node license named DVNETEND - The routing node license named DVNETRTG All routing nodes must have a routing license. Each end node can have either an end node license or a routing license. If neither license is registered and activated, DECnet does not start and your use is limited to local DECnet only (SET HOST 0). If DECnet- Plus for OpenVMS is running when you register your license, you must stop and then restart it. You can control which VAXcluster nodes have access to each license. Using the LICENSE MODIFY/INCLUDE=(node- name[,node-name,...]) command, you can assign licenses to nodes and limit access as needed. For example, you can assign a routing node license to only one VAXcluster node and assign the end node licenses to the remaining VAXcluster nodes. If you choose this approach, make sure you assign a license to each end node license. Specify include lists for each license of the same type. For details, see the OpenVMS License Management Utility Manual. o RMS Journaling for OpenVMS (LMF Product Name: RMSJNL) On systems that do not have registered and loaded journaling licenses, users cannot write to any files marked for journaling. Installing the OpenVMS VAX Operating System 3-31 Installing the OpenVMS VAX Operating System 3.8 Registering Licenses o Volume Shadowing for OpenVMS (LMF Product Name: VOLSHAD) You must register and load a license for Volume Shadowing for OpenVMS on each node using volume shadowing, including satellites in a VAXcluster system. 3.9 Time Zone and Time Differential Factor Information At this point in the installation, the procedure asks you for time zone information that is used for providing local time zone support. 3.9.1 UPDATING TIME ZONE INFORMATION 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 those menus. The first menu is the main time zone menu. Select the time zone that best describes your location. If you do not select a time zone, the default is Greenwich Mean Time (GMT). Some time zone choices cause an additional menu to be displayed. This happens when the time zone you select has subcomponents. For example, if you choose the United States (US) time zone from the main menu, a second menu displays the specific time zones within the United States. You then select the menu item that best represents your local 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 for measuring time of day. You can choose from the following options: o Exit the time zone procedure without setting a TDF o Set a TDF 3-32 Installing the OpenVMS VAX Operating System Installing the OpenVMS VAX Operating System 3.9 Time Zone and Time Differential Factor Information o Display the TDF for your local time zone For more information about TDF and local time zone support, see the OpenVMS System Manager's Manual If you chose to install DECnet-Plus earlier in the installation procedure, see Section 3.10. If you chose not to install DECnet-Plus, go to Section 3.11. 3.10 Installing DECnet-Plus Earlier in the procedure, you were asked whether you wanted to install the DECnet-Plus product. If you answered Yes, the procedure will now install the DECnet-Plus product. The procedure displays a message similar to the following and prompts you for information it needs to install the DECnet-Plus product. In this example, the kit is being installed from an InfoServer device, DAD1. DECnet-Plus will now be installed. Media containing the DECnet-Plus kit must be available. If you are installing OpenVMS from an InfoServer (DAD1) or local CD-ROM, there is a DECnet-Plus kit on the CD-ROM. If you are installing from a cartridge tape (TK50) or from an open reel tape, you should have a DECnet-Plus kit on cartidge tape or open reel tape. An appropriate DECnet-Plus kit may also be available on the Consolidated Distribution CD-ROM, or you may have a separate DECnet-Plus kit. NOTE: You may choose any available media for the DECnet-Plus kit. It is NOT NECESSARY to use the same type of media that contained the OpenVMS kit. If you do not have a DECnet-Plus kit available, or if you have decided NOT to install/upgrade DECnet-Plus, you can bypass the DECnet-Plus installation by entering "EXIT" for the "name of drive holding the DECnet-Plus kit". * Enter name of drive holding the DECnet-Plus kit: DAD1: * Enter the InfoServer service name: OTHER_PRODS * Enter the InfoServer work group number [0]: Installing the OpenVMS VAX Operating System 3-33 Installing the OpenVMS VAX Operating System 3.10 Installing DECnet-Plus The following product has been selected: DEC VAXVMS DECNET_OSI V7.1 DEC VAXVMS DECNET_OSI V7.1: DECnet-Plus V7.1 for OpenVMS VAX Copyright © Digital Equipment Corporation 1996. All rights reserved. Digital Equipment Corporation This product requires one of two PAKs: DVNETEND or DVNETRTG. Do you want all the default values for this product? [YES] Do you want to view the values? [NO] Execution phase starting ... The following product will be installed: DEC VAXVMS DECNET_OSI V7.1 Portion done: 0%...10%...20%...30%...40%...80%...90%...100? The following product has been installed: DEC VAXVMS DECNET_OSI V7.1 . . . To complete the installation procedure, continue on to the next section, Section 3.11. 3.11 Running AUTOGEN The remaining portion of the installation procedure runs AUTOGEN to evaluate your hardware configuration and estimate typical workloads. AUTOGEN then sets system parameters, the sizes of page, swap, and dump files, and the contents of VMSIMAGES.DAT. When AUTOGEN finishes and the system has rebooted, the installation procedure is complete. The installation procedure runs AUTOGEN, as follows: 1. The installation procedure displays a series of messages similar to the following: 3-34 Installing the OpenVMS VAX Operating System Installing the OpenVMS VAX Operating System 3.11 Running AUTOGEN Running AUTOGEN to compute new SYSTEM parameters ... %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, REBOOT phase is beginning. If you need to create or modify the size of the pagefile or swapfile, use the SYSMAN utility. For more information, see the OpenVMS System Manager's Manual: Essentials. 2. After AUTOGEN finishes, the procedure displays a series of shutdown messages that begin like this: 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 upgrade will be complete. SHUTDOWN -- Perform an Orderly System Shutdown 3. After the system shuts down, the procedure tries to reboot the new system disk. If the system does not reboot automatically, reboot it manually. For example, suppose you have a VAX-11/780 computer and the system disk is on an RA60 disk drive with a unit number of one. Enter the following command and press Return: >>> B DUA1 For information on booting, refer to the upgrade and installation supplement for your VAX computer. Then return to this manual. 4. After the system reboots, the procedure displays the following message: Installing the OpenVMS VAX Operating System 3-35 Installing the OpenVMS VAX Operating System 3.11 Running AUTOGEN OpenVMS VAX Version V7.1 Major version id = 1 Minor version id = 0 *************************************************************** OpenVMS VAX V7.1 You have SUCCESSFULLY installed the OpenVMS VAX operating system. The system is now executing the STARTUP procedure. Please wait for the completion of STARTUP before logging in to the system. **************************************************************** Note: If you did not register your OpenVMS VAX license as described in Section 3.8, the procedure displays warning messages that the OpenVMS license must be registered. Be sure to register this license when the installation procedure finishes. For more information, see Appendix B and the OpenVMS License Management Utility Manual. Finally, the procedure displays informational messages and accounting information. For example: %SET-I-INTSET, login interactive limit = 64, current interactive value = 0 SYSTEM job terminated at 22-NOV-1996 16:54:24.71 Accounting information: Buffered I/O count: 859 Peak working set size: 565 Direct I/O count: 478 Peak virtual size: 2570 Page faults: 5003 Mounted volumes: 0 Charged CPU time: 0 00:00:19.33 Elapsed time: 0 00:00:41.24 At this point the OpenVMS VAX operating system is running. 5. Press the Return key. The system asks you for the user name and password. Log in to the SYSTEM account so you can perform certain postinstallation tasks. For example: Welcome to OpenVMS VAX V7.1 Username: SYSTEM Password: . . . Welcome to OpenVMS VAX Version V7.1 3-36 Installing the OpenVMS VAX Operating System Installing the OpenVMS VAX Operating System 3.11 Running AUTOGEN If you forget the password, follow the instructions for performing an emergency startup in the OpenVMS System Manager's Manual: Essentials. 6. There are several postinstallation tasks you must perform before you can use the system. These tasks are described in Chapter 4. Installing the OpenVMS VAX Operating System 3-37 4 _________________________________________________________________ After Installing OpenVMS VAX 4.1 Overview After you have installed the OpenVMS VAX operating system, you need to perform several important tasks to prepare the system for operation. This chapter describes the following postinstallation tasks in the order you perform them: o Verifying system time o Registering licenses o Backing up your system disk o Customizing your system o Configuring and starting networking software o Testing the system o Decompressing system libraries o Removing unwanted files o Installing layered products o Backing up the customized system disk o Running AUTOGEN o Completing the postinstallation checklist If you are an experienced system manager, you can use the checklist at the end of the chapter to complete the necessary postinstallation tasks. If you are a system manager with less OpenVMS VAX experience, you should read the entire chapter and then use the checklist to make sure you have completed all the postinstallation tasks. After Installing OpenVMS VAX 4-1 After Installing OpenVMS VAX 4.2 Verifying System Time 4.2 Verifying System Time During the installation, the procedure prompted you to enter the date and time. Now that you have installed your system, verify that the system time is correct by entering the following command: $ SHOW TIME The system displays the date and time. If the time is not correct, reset it by entering the command SET TIME using the following format: SET TIME=dd-mmm-yyyy:hh:mm:ss For example: $ SET TIME=22-NOV-1996:18:35:30 4-2 After Installing OpenVMS VAX After Installing OpenVMS VAX 4.3 Registering Your Licenses 4.3 Registering Your Licenses The installation procedure gave you the opportunity to register any software product licenses. If you did not register your OpenVMS VAX license at that time, you must do so before you can use the OpenVMS VAX operating system. You must also register the licenses for any of the following System Integrated Products you have purchased: VAXcluster DECnet-Plus OpenVMS RMS Journaling Volume Shadowing for OpenVMS 4.3.1 WHERE TO FIND MORE INFORMATION For step-by-step instructions about registering licenses, see the OpenVMS License Management Utility Manual and Appendix B of this manual, which provides supplemental information. 4.4 Backing Up Your System Disk Now that you have spent time installing the operating system, you should protect your work by making a backup copy of the system disk in case you have any problems while customizing it. Digital recommends that you perform the following operations: o Make a standalone BACKUP kit on the system disk and on removable media o Perform a standalone BACKUP of your system disk You should back up your system disk again after you have customized it. For complete information about these operations, see the upgrade and installation supplement for your VAX computer. 4.5 Customizing the System You can customize the system to meet the specific needs of your site. In addition, if your VAX computer is part of a VAXcluster environment, you must prepare the cluster environment and configure the cluster. After Installing OpenVMS VAX 4-3 After Installing OpenVMS VAX 4.5 Customizing the System For instructions about customizing your system, refer to the following: o Read the chapter on booting in the upgrade and installation supplement for your VAX computer. This chapter explains the different ways to boot the system. It also tells you how to shut down the system. o If the computer is part of a VAXcluster environment, read OpenVMS Cluster Systems for further information about setting up a cluster. o Read the OpenVMS System Manager's Manual: Essentials for instructions on customizing and using your system. You will find information about the following tasks: - Editing the template files SYCONFIG.COM, SYLOGICALS.COM, SYLOGIN.COM, and SYSTARTUP_VMS.COM - Starting the queue manager and creating a queue database. (If you are installing on a VAXcluster system with multiple system disks, see the OpenVMS Cluster Systems for additional instructions.) - Setting up user accounts - Adjusting system parameters o If you plan to use either the DECnet-Plus product included on the OpenVMS VAX Version 7.1 kit or the DECnet Phase IV layered product, read Section 4.6 and perform the steps described there. If you are installing the DECnet-Plus software, you should also refer to the DECnet-Plus installation and configuration documentation. o If you installed DECwindows support software, there are several steps you must take to customize your DECwindows environment. Depending on your configuration, these tasks might include: - Customizing the server startup - Using the Transmission Control Protocol/Internet Protocol (TCP/IP) as a DECwindows transport - Using transports for DECwindows other than those supplied by Digital 4-4 After Installing OpenVMS VAX After Installing OpenVMS VAX 4.5 Customizing the System See Chapter 9 for complete instructions for customizing your DECwindows support software. o If you installed the optional OpenVMS Management Station files, see Appendix G for information about preparing your OpenVMS system and your PC to use this application. 4.6 Configuring and Starting Networking Software In local area and mixed-interconnect VAXcluster systems, DECnet software provides both system management functions and cluster communications, such as remote booting operations. DECnet software ensures that system managers can access all VAXcluster computers from a single terminal. You can use the DECnet-Plus software included on the OpenVMS VAX Version 7.1 kit, or you can install the DECnet Phase IV layered product. Both of these products require that you run a configuration procedure to configure the network. If you choose to run the DECnet Phase IV product, you must also edit your system startup file as described in Section 4.6.2. 4.6.1 CONFIGURING YOUR SYSTEM After you have registered your DECnet license, execute one of the following interactive configuration procedures: o For the DECnet Phase IV software, run SYS$MANAGER:NETCONFIG.COM. (See the DECnet for OpenVMS Guide to Networking for more information.) o For the DECnet-Plus for OpenVMS layered product, run SYS$MANAGER:NET$CONFIGURE.COM. (See the DECnet-Plus for OpenVMS Installation and Basic Configuration for more information. 4.6.2 EDITING SYSTARTUP_VMS If you plan to run DECnet-Plus, you do not need to edit this file because DECnet will start automatically. If you plan to run DECnet Phase IV, after you start the queue manager, edit the commands in SYS$COMMON:[SYSMGR]SYSTARTUP_VMS.COM that pertain to networking, so that DECnet starts automatically when your After Installing OpenVMS VAX 4-5 After Installing OpenVMS VAX 4.6 Configuring and Starting Networking Software system is booted. Choose one of the following commands to start the network and remove the comment delimiter (!) from that command: $! IF F$SEARCH("SYS$SYSTEM:NETACP.EXE") .NES. "" THEN @SYS$MANAGER:STARTNET $! IF F$SEARCH("SYS$SYSTEM:NETACP.EXE") .NES. "" THEN SUBMIT SYS$MANAGER: - _$ STARTNET.COM Both of the previous commands perform the same task. However, the first command executes STARTNET.COM and delays further processing until the procedure is completed; the second submits STARTNET.COM to a batch queue and continues executing SYSTARTUP_VMS.COM. If you plan to run both DECnet Phase IV and DECwindows Motif for OpenVMS VAX, you must also edit SYS$COMMON:[SYSMGR]SYSTARTUP_VMS.COM to add a comment delimiter (!) immediately following the dollar- sign ($) in the DEFINE DECW$IGNORE_DECNET command as follows: $! DEFINE DECW$IGNORE_DECNET TRUE If you are not going to start DECnet Phase IV or have not yet started it, this command tells DECwindows not to wait for DECnet. 4.7 Testing the System with UETP Software UETP software is a user environment test package that tests whether the OpenVMS VAX operating system is installed correctly. As part of the postinstallation procedure, you should run UETP to verify your installation. Note that UETP needs at least 1200 free blocks on the system disk and is available only if you installed the optional save set VMS071.D. If you did not install the optional save set, you can add the UETP files to your system using VMSTAILOR. For information about using VMSTAILOR see Chapter 10. For complete information about UETP, see the OpenVMS System Manager's Manual: Tuning, Monitoring, and Complex Systems. 4-6 After Installing OpenVMS VAX After Installing OpenVMS VAX 4.8 Decompressing System Libraries 4.8 Decompressing System Libraries Decompressing the system libraries gives the system faster access to them. You can decompress all the system libraries or just some of them. Table 4-1 gives the approximate number of blocks consumed by each library after decompression. Table_4-1_Sizes_of_Decompressed_System_Libraries___________ Library___________Blocks______Library___________Blocks_____ HELPLIB.HLB 9108 EDFHLP.HLB 102 STARLET.OLB 8442 TPUHELP.HLB 1038 VAXCCURSE.OLB 102 ACLEDT.HLB 102 VAXCRTL.OLB 477 INSTALHLP.HLB 102 VAXCRTLG.OLB 102 LATCP$HELP.HLB 240 DECCCURSE.OLB 102 MNRHELP.HLB 102 DECCRTL.OLB 183 PATCHHELP.HLB 102 DECCRTLG.OLB 102 PHONEHELP.HLB 102 ERFLIB.TLB 105 SDA.HLB 111 STARLETSD.TLB 4800 SHWCLHELP.HLB 150 MAILHELP.HLB 273 SYSGEN.HLB 393 EDTHELP.HLB 231 TECO.HLB 102 DBG$UIHELP.HLB 408 UAFHELP.HLB 372 DBG$HELP.HLB 1986 EVE$HELP.HLB 1197 EXCHNGHLP.HLB 117 EVE$KEYHELP.HLB 147 NCPHELP.HLB 537 STARLET.MLB 2502 ANLRMSHLP.HLB 102 LIB.MLB 2229 DISKQUOTA.HLB 102 _____________________________________________________________ The additional amount of disk space required to decompress all the system libraries is about 13,500 blocks. To find out how much disk space you have, enter the following command and press the Return key: After Installing OpenVMS VAX 4-7 After Installing OpenVMS VAX 4.8 Decompressing System Libraries $ SHOW DEVICE SYS$SYSDEVICE To decompress the system libraries, you run LIBDECOMP.COM by logging in to the SYSTEM account, entering the following command, and pressing Return: $ @SYS$UPDATE:LIBDECOMP.COM The following information is displayed: OpenVMS Library Decompression Utility 1 HELPLIB.HLB 14 NCPHELP.HLB 27 PATCHHELP.HLB 2 STARLET.OLB 15 SDA.HLB 28 PHONEHELP.HLB 3 ACLEDT.HLB 16 SHWCLHELP.HLB 29 LIB.MLB 4 ANLRMSHLP.HLB 17 SYSGEN.HLB 30 STARLET.MLB 5 DBG$HELP.HLB 18 ANALAUDIT$HELP.HLB 31 STARLETSD.TLB 6 DBG$UIHELP.HLB 19 SYSMANHELP.HLB 32 ERFLIB.TLB 7 DISKQUOTA.HLB 20 TFF$TFUHELP.HLB 33 VAXCCURSE.OLB 8 EDFHLP.HLB 21 EXCHNGHLP.HLB 34 VAXCRTL.OLB 9 INSTALHLP.HLB 22 TPUHELP.HLB 35 VAXCRTLG.OLB 10 LATCP$HELP.HLB 23 EVE$HELP.HLB 36 IMAGELIB.OLB 11 MAILHELP.HLB 24 EVE$KEYHELP.HLB 37 DECCCURSE.OLB 12 MNRHELP.HLB 25 UAFHELP.HLB 38 DECCRTL.OLB 13 EDTHELP.HLB 26 TECO.HLB 39 DECCRTLG.OLB A ALL libraries to be decompressed E EXIT this procedure * Enter letter or number(s) of libraries to be decompressed (Separate multiple entries with a comma): 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. If you prefer, you can execute LIBDECOMP interactively or as a batch job. If you use either of these methods, you can decompress up to 8 libraries each time you execute LIBDECOMP by listing the names of the libraries you want to decompress as parameters on the command line. (You can decompress all the libraries by omitting the /PARAMETERS qualifier.) Be sure to separate the library names with commas and do not include the file extension. For example, to decompress the VAXCRTL.OLB, DISKQUOTA.HLB, and LIB.MLB libraries as a batch job, enter the following command: 4-8 After Installing OpenVMS VAX After Installing OpenVMS VAX 4.8 Decompressing System Libraries $ SUBMIT/NOTIFY/PARAMETERS=(VAXCRTL, DISKQUOTA, LIB)- _$ SYS$UPDATE:LIBDECOMP To decompress these same libraries interactively, enter the following command: $ @SYS$UPDATE:LIBDECOMP VAXCRTL DISKQUOTA LIB Note that, when you type the command for a batch job, you separate the library names with commas and enclose the list within parentheses. You do not use commas or parentheses on the interactive command line. 4.9 Removing or Adding OpenVMS Files To remove unwanted OpenVMS VAX files from the system disk, use VMSTAILOR or DECW$TAILOR. For example, if you are not running DECnet software, use VMSTAILOR to remove the files associated with DECnet. ________________________ Note ________________________ You cannot use VMSTAILOR to remove files installed on an alternate device from save set VMS071.E. ______________________________________________________ For complete information about using VMSTAILOR and DECW$TAILOR to remove optional OpenVMS VAX software, see Chapter 10. 4.10 Installing Layered Products Back up your system disk and then use either the VMSINSTAL command procedure or the POLYCENTER Software Installation utility to install layered products on your system. For additional information about installing layered products, see the OpenVMS System Manager's Manual. 4.10.1 TCP/IP SERVICES FOR OPENVMS If you installed the Digital TCP/IP Services for OpenVMS software during the installation or if you choose to install it now as a layered product, note that you must also install the mandatory security update kit included with this release. After Installing OpenVMS VAX 4-9 After Installing OpenVMS VAX 4.10 Installing Layered Products The Digital TCP/IP Kit and the mandatory Security Update Kit are available in the following directory on the OpenVMS VAX CD-ROM: [TCPIP_VAX_041] If you choose to install the Digital TCP/IP Services for OpenVMS software, you must install both kits. 4.11 Backing Up the Customized System Disk Now that you have spent time installing and customizing the operating system, protect your work by making a standalone backup copy of the system disk. For complete information about these operations, see the upgrade and installation supplement for your VAX computer. 4.12 Running AUTOGEN When you installed the OpenVMS VAX operating system, the procedure executed AUTOGEN to set the values of system parameters and the sizes of the page and swap files according to the system's workload. In many cases, AUTOGEN can improve system performance by using dynamic feedback information from the running system. As a postinstallation task, you should run AUTOGEN again using the feedback mechanism to make further adjustments to system parameters. 4.12.1 HOW AUTOGEN WORKS When AUTOGEN runs, it uses the parameter values in SYS$SYSTEM:MODPARAMS.DAT. Note that hardcoded values in MODPARAMS.DAT affect AUTOGEN's calculations of the feedback parameters. For AUTOGEN to properly calculate minimum default values, you should replace the hardcoded values in MODPARAMS.DAT with MIN_ values. If you need to modify the parameter values calculated by AUTOGEN, you can use AUTOGEN to change the hardcoded values in MODPARAMS.DAT. For information about using AUTOGEN, see the OpenVMS System Manager's Manual: Essentials. 4-10 After Installing OpenVMS VAX After Installing OpenVMS VAX 4.12 Running AUTOGEN 4.12.2 WHEN TO RUN AUTOGEN After installing the operating system, run AUTOGEN again using the following procedure: 1. After 24 hours of operation, run AUTOGEN in feedback mode and reboot the system. 2. Run AUTOGEN in this same way, again, two working days later. Note: For large memory systems such as the VAX 9000 computer, AUTOGEN's initial parameter calculations are conservative. To obtain parameter values that match your system workload, you can run AUTOGEN in feedback mode a number of times. For more information, see the upgrade and installation supplement for your computer. 3. 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. After you run AUTOGEN following the first 24 hours of system operation (step 1), review the checklist in Section 4.13 to confirm that you have completed all the tasks described in this chapter. 4.13 Postinstallation Checklist Use the following checklist to make sure you perform all the necessary postinstallation tasks. < Verify the system time. (Described in Section 4.2.) < Register your licenses if you did not do so during the installation procedure. (Described in Appendix B of this manual and in the OpenVMS License Management Utility Manual.) < Build a standalone BACKUP kit on the system disk and on removable media. (Described in the upgrade and installation supplement for your computer.) < Back up the system disk as a safeguard before customizing the system. (Described in the upgrade and installation supplement for your computer.) < Customize the system. (Described in Section 4.5.) After Installing OpenVMS VAX 4-11 After Installing OpenVMS VAX 4.13 Postinstallation Checklist < Configure and start your networking software. (Described in Section 4.6.) < Run UETP (the User Environment Test Package) to test the system. (Described in OpenVMS System Manager's Manual: Tuning, Monitoring, and Complex Systems.) < Decompress the system libraries using LIBDECOMP.COM. (Described in Section 4.8.) < Remove unwanted files from the system disk using the OpenVMS tailoring utility. (Described in Chapter 10.) < Install layered products. < Back up the system disk after you have customized it. (Described in the upgrade and installation supplement for your computer.) < Run AUTOGEN after the system has been running for at least 24 hours to collect feedback information. (Described in Section 4.12.) 4-12 After Installing OpenVMS VAX 5 _________________________________________________________________ Before Upgrading OpenVMS VAX Software 5.1 Overview Before you begin an upgrade, you need to perform several important tasks to prepare the system. This chapter describes what you need to know and do to prepare for an upgrade, including: o Being aware of the cautions and restrictions o Making sure your hardware is ready and your software distribution kit is complete o Examining AUTOGEN feedback data o Backing up your system disk o Preparing your system disk o Preparing your system o Gathering the information for the upgrade procedure o Completing the preupgrade checklist If you are an experienced system manager, you can use the checklist at the end of this chapter to complete the necessary preupgrade tasks. If you are system manager with limited OpenVMS VAX experience, you should read the entire chapter and then use the checklist to make sure you have completed all the preupgrade tasks. 5.2 Cautions and Restrictions This section provides important information that you need to be aware of before you upgrade your system. If you attempt to upgrade your system without following these cautions and restrictions, the upgrade could fail or your upgraded system might not perform as expected. Before Upgrading OpenVMS VAX Software 5-1 Before Upgrading OpenVMS VAX Software 5.2 Cautions and Restrictions 5.2.1 LICENSE REQUIREMENTS To upgrade to OpenVMS Version 7.1, 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.1 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.1. 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. 5.2.2 DECSET VERSION 11 DEBUGGER If you have the DECset Version 11 layered product installed on your system, you must remove the @DEBUG$STARTUP.COM command from the system startup procedure. The debugger shipped with OpenVMS VAX Version 7.1 is a superset of the debugger that was shipped with the DECset Version 11 software. Removing the @DEBUG$STARTUP.COM command will cause the debugger shipped with OpenVMS VAX Version 7.1 to be the default system debugger. To remove the @DEBUG$STARTUP.COM command before you upgrade the operating system software, perform the following steps: 1. Log in to an account with system privileges. 2. Using the editor of your choice, open the SYS$STARTUP:SYSTARTUP_VMS.COM file and search for the following command: $ @DEBUG$STARTUP Delete the command and any parameters. (The command might have an optional parameter of either VMS or DECSET.) 3. Exit from the file, saving the change. 5-2 Before Upgrading OpenVMS VAX Software Before Upgrading OpenVMS VAX Software 5.2 Cautions and Restrictions If you do not remove this command before you upgrade the operating system software, you must remove it after the upgrade, and you must deassign the logicals that were defined by DEBUG$STARTUP.COM by performing the following steps: 1. Log in to the account that you used to perform the upgrade. 2. Enter the following commands: $ DEASSIGN/SYSTEM DEBUG $ DEASSIGN/SYSTEM DEBUGSHR $ DEASSIGN/SYSTEM DEBUGUISHR $ DEASSIGN/SYSTEM DBGTBKMSG $ DEASSIGN/SYSTEM DBG$HELP $ DEASSIGN/SYSTEM DBG$UIHELP $ DEASSIGN/SYSTEM DEBUGAPPCLASS $ DEASSIGN/SYSTEM VMSDEBUGUIL 3. Using the editor of your choice, open the SYSTARTUP_ VMS.COM file and search for the following command: $ @DEBUG$STARTUP Delete the command and any parameters. (The command might have an optional parameter of either VMS or DECSET.) 4. Exit from the file, saving the change. 5.2.3 CUSTOMIZED SECURITY ENVIRONMENT The Version 7.1 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 established. For more information on creating and maintaining a secure environment, see the OpenVMS Guide to System Security. Before Upgrading OpenVMS VAX Software 5-3 Before Upgrading OpenVMS VAX Software 5.2 Cautions and Restrictions 5.2.4 OPERATOR AND ACCOUNTING LOGS The upgrade procedure deletes all the operator and accounting logs. To save these files, move them to a user directory before you start the upgrade. 5.2.5 SPECIAL TESTING AND DEBUGGING FILES Before you perform an upgrade, remove or rename any special testing or debugging files that you might have in any of the SYS$SPECIFIC: or SYS$SYSROOT: directories. Files in these directories are used in place of the files in SYS$COMMON: directories. As a minimum, you should check the following directories: SYS$SYSROOT:[SYSEXE] SYS$SYSROOT:[SYS$LDR] Because the upgrade procedure affects the SYS$COMMON: directories and does not check or alter the contents of the SYS$SPECIFIC: or SYS$SYSROOT: directories, any testing or debugging files that you have in these directories remain there unchanged until you remove or rename them. If you do not remove or rename these files, your system might behave in an unpredictable manner. 5.2.6 CLUSTER CONSIDERATIONS The following cautions apply when you are upgrading a cluster system: o The upgrade procedure does not work across the network. The network is not available during the upgrade, so you must have the save sets available locally or on the InfoServer. o If the node you are upgrading is a cluster member, the upgrade procedure checks the previously set values of several system parameters at the beginning of the upgrade (see Section 7.3.) If any of the values are less than that required to upgrade to OpenVMS VAX Version 7.1, you are given the choice of continuing or canceling the upgrade. If you choose to continue the upgrade, the entire upgrade might not be completed and the cluster might be left in a hung state. 5-4 Before Upgrading OpenVMS VAX Software Before Upgrading OpenVMS VAX Software 5.2 Cautions and Restrictions o Before you start the upgrade procedure in a VAXcluster environment, you must shut down all the nodes that boot from the system disk you are upgrading, including the node you perform the upgrade on. 5.2.7 SAVE SET LOCATION If you move the OpenVMS VAX save sets from the distribution media to the system disk or some other disk before beginning the upgrade, the save sets must be in the [000000] directory of the disk, or the upgrade will fail. Do not attempt to use VMSINSTAL with OPTION G to transfer OpenVMS VAX save sets to another media type; doing so will produce an unusable system. Instead, you can use the DCL command COPY to transfer save sets to another media type. 5.2.8 SYSTEM DISK CAUTIONS The following cautions apply to the system disk: o If you changed the names of system directories 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 You must not move the system disk or the distribution kit from one drive to another during the upgrade. o You cannot upgrade a shadowed system disk. If your system disk is part of a shadow set, you must create a nonshadowed system disk before beginning the upgrade. Also, if you copy the distribution media to another disk, that disk must be a nonshadowed disk. For more information, see the manual Volume Shadowing for OpenVMS. o If you elect not to install optional components, the upgrade procedure removes existing files for those components from the system disk. You can install optional files during the upgrade or later using VMSTAILOR. Note that, while some optional files can be placed on an alternate device, you cannot tailor files on or off an alternate device. Before Upgrading OpenVMS VAX Software 5-5 Before Upgrading OpenVMS VAX Software 5.2 Cautions and Restrictions 5.2.9 AUTOGEN FEEDBACK DATA If you use your AUTOGEN feedback data, you should save this information before rebooting the system with minimum startup to begin the upgrade. For more information, see Section 5.4. 5.2.10 OPENVMS VERSION REQUIREMENTS Before you can upgrade to OpenVMS VAX Version 7.1, your system must be running at least Version 6.1 of the OpenVMS operating system. For example, you can upgrade a system disk to Version 7.1 of the OpenVMS VAX operating system from any of the following versions (or related hardware releases): OpenVMS VAX Version 6.1 OpenVMS VAX Version 6.2 OpenVMS VAX Version 7.0 5.2.11 DECWINDOWS MOTIF VERSION REQUIREMENTS If you want to use DECwindows software with OpenVMS VAX Version 7.1, you must be running Version 1.2-3 or higher of the DECwindows Motif for OpenVMS layered product. For more information, see Section 1.2.1. 5.2.12 SHARED SYSTEM DUMP FILES If you have a shared system dump file in SYS$COMMON:[SYSEXE], the shared dump file cannot have the name SYSDUMP.DMP. If you have a shared system dump file with this name, Digital recommends that you rename it to SYS$COMMON:[SYSEXE]SYSDUMP_COMMON.DMP. 5.2.13 LAYERED PRODUCTS The upgrade procedure is designed so that you should not have to reinstall most layered products after the upgrade. However, you might need to reinstall certain layered products because of product-specific installation procedures. If a layered product is available yet exhibits unexpected behavior once Version 7.1 of the OpenVMS VAX operating system is running, check the OpenVMS Version 7.1 Release Notes for possible layered-product restrictions. 5-6 Before Upgrading OpenVMS VAX Software Before Upgrading OpenVMS VAX Software 5.3 Are You Ready to Upgrade? 5.3 Are You Ready to Upgrade? Before you begin to upgrade the OpenVMS VAX operating system, be sure you have all the required hardware and software components. 5.3.1 HARDWARE COMPONENTS Examine your hardware for the following: o Make sure your hardware has been checked for proper operation. To perform a successful upgrade, you must understand the basic operations of the VAX computer that you are upgrading. Refer to the upgrade and installation supplement for your VAX computer. If you have a VAXcluster environment, refer to OpenVMS Cluster Systems. o 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 more information, see the upgrade and installation supplement for your VAX computer. o Have scratch console media (media that does not contain files you want to save) available for the following VAX computers: VAX 8600, 8650 VAX 8200, 8250, 8300, 8350 VAX-11/730 VAX-11/750 VAX-11/780, 785 For example, if you have a VAX-11/780 or VAX-11/785 computer, you need a scratch RX01 floppy diskette. 5.3.2 SOFTWARE COMPONENTS Examine your software for the following: o Make sure you have all the items listed on the bill of materials (BOM) in the OpenVMS distribution kit. If your kit is incomplete, notify Digital Software Supply, and request priority shipment of any missing items. Before Upgrading OpenVMS VAX Software 5-7 Before Upgrading OpenVMS VAX Software 5.3 Are You Ready to Upgrade? o Before upgrading the OpenVMS VAX operating system, read Appendix B of this manual, the OpenVMS Version 7.1 New Features Manual, the OpenVMS Version 7.1 Release Notes, and any cover letters included with your kit. 5.4 Examining AUTOGEN Feedback Data After the upgrade is finished, AUTOGEN runs. If it finds valid feedback data on your system, it tries to use AUTOGEN feedback. 5.4.1 VALID FEEDBACK DATA Feedback data is produced by the SAVPARAMS phase of AUTOGEN and is stored in SYS$SYSTEM:AGEN$FEEDBACK.DAT. Valid feedback data is defined as follows: o The system was up for at least 24 hours when the feedback data was gathered. o The feedback data is not over 30 days old. If your feedback data is not valid, AUTOGEN will run without feedback (all previous feedback-generated parameters will be replaced by the AUTOGEN NOFEEDBACK calculations). 5.4.2 HOW TO TEST FEEDBACK DATA To ensure that AUTOGEN feedback will run after the upgrade, do the following: 1. Check the validity of your current feedback data by entering the following command: $ @SYS$UPDATE:AUTOGEN GETDATA TESTFILES This command is for test purposes and does not result in the modification of system parameters or changes to the page and swap files. If your current feedback is valid, AUTOGEN will use it during the upgrade, and you can proceed to the next section. If your current feedback data is invalid, AUTOGEN will issue several warnings. If you get these warnings, go to step 2. 5-8 Before Upgrading OpenVMS VAX Software Before Upgrading OpenVMS VAX Software 5.4 Examining AUTOGEN Feedback Data 2. If your current feedback is invalid, you can generate new feedback data (assuming your system was up for at least 24 hours). Enter the following command: $ @SYS$UPDATE:AUTOGEN SAVPARAMS TESTFILES This command is for test purposes and does not result in the modification of system parameters or changes to the page and swap files. Again, AUTOGEN warns you if the feedback data just produced is invalid. 3. If you follow steps 1 or 2 and your current feedback data is valid, AUTOGEN uses your current feedback- generated parameters during the upgrade. Your current feedback-generated parameters will not be lost during the upgrade. 5.5 Performing Backup Tasks Digital recommends that you make a standalone 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. 5.5.1 HOW TO BACK UP THE SYSTEM DISK To make a backup copy of the system disk, follow the instructions in the upgrade and installation supplement for your VAX computer. If you do not have a removable system disk, back up your system disk to tape and restore the image backup to the system disk. This eliminates disk fragmentation on the system disk and creates contiguous free disk blocks required for the upgrade. (The upgrade can fail if there are not sufficient contiguous free blocks.) Store the backup tapes in a safe place. 5.5.2 HOW TO BACK UP CONSOLE MEDIA If you have one of the following VAX computers, you also must make a backup copy of the console media: VAX-11/730 VAX-11/750 VAX-11/780, 785 VAX 8200, 8250, 8300, 8350, 8600, 8650 Before Upgrading OpenVMS VAX Software 5-9 Before Upgrading OpenVMS VAX Software 5.5 Performing Backup Tasks To make a backup copy of the console media, use the SYS$UPDATE:CONSCOPY.COM procedure, as described in the upgrade and installation supplement for your VAX computer. Use the backup copy of the console media during the upgrade procedure. The upgrade procedure updates the console media for you. If your VAX computer uses one of the following console media, you did not receive a new standalone BACKUP kit with your OpenVMS VAX distribution kit: TU58 tape cartridge RX33 diskette RX50 diskette RX01 diskette RL02 disk cartridge Before beginning the upgrade, make sure you have a standalone BACKUP kit on one of these media. If you do not have one, create a standalone BACKUP kit using the STABACKIT.COM procedure as described in the upgrade and installation supplement for your VAX computer. ________________________ Note ________________________ You cannot build standalone BACKUP on TU58 or RX01 console media because the OpenVMS VAX Version 7.1 kit is too large. If your VAX computer uses a TU58 or RX01, build a standalone BACKUP kit before upgrading and retain the backup copies for use with future versions of OpenVMS VAX. ______________________________________________________ 5.6 Preparing Your System Disk To prepare the system disk for the upgrade, log in to the SYSTEM account and, depending on your configuration, complete some or all of the tasks described in the sections that follow. 5-10 Before Upgrading OpenVMS VAX Software Before Upgrading OpenVMS VAX Software 5.6 Preparing Your System Disk 5.6.1 CREATE A NONSHADOWED SYSTEM DISK If you are using a volume-shadowed system disk, you must create a nonshadowed system disk to upgrade. Follow the instructions in the Volume Shadowing for OpenVMS manual to prepare a nonshadowed system disk for the upgrade. 5.6.2 BOOT THE BACKUP COPY OF YOUR SYSTEM DISK If you need to boot the backup copy of your system disk or if you are upgrading a VAXcluster environment, enter the following command (otherwise, go to the next step): $ @SYS$SYSTEM:SHUTDOWN When the procedure asks if an automatic system reboot should be performed, press Return for NO. If you are a VAXcluster member, choose the CLUSTER_SHUTDOWN option. When the procedure is finished, halt the system as described in the upgrade and installation supplement for your VAX computer. If applicable, remove the system disk and replace it with the backup copy. Boot the system from the backup copy of the system disk. If you do not know how to boot the system, refer to the upgrade and installation supplement for your VAX computer. Log in to the SYSTEM account. 5.6.3 COPY UAF AND AUDITING FILES TO THE SYSTEM DISK The current copies of the SYSUAF.DAT and the VMS$AUDIT_ SERVER.DAT files must be on the system disk; otherwise, you cannot proceed with the upgrade. If you have moved your copy of SYSUAF.DAT to another location, copy it to the SYS$COMMON:[SYSEXE] directory for the duration of the upgrade. If you have moved your copy of VMS$AUDIT_SERVER.DAT to another location, copy it to the SYS$COMMON:[SYSMGR] directory. Note that, if you are doing a rolling upgrade, the shared version of SYSUAF.DAT is not updated. Move any files that you do not want changed into a user directory. Before Upgrading OpenVMS VAX Software 5-11 Before Upgrading OpenVMS VAX Software 5.6 Preparing Your System Disk 5.6.4 RENAME THE SYSTEM DUMP FILE If you have a shared system dump file in SYS$COMMON:[SYSEXE], the shared dump file cannot have the name SYSDUMP.DMP. If you have a shared system dump file with this name, Digital recommends that you rename it to SYS$COMMON:[SYSEXE]SYSDUMP-COMMON.DMP. 5.6.5 ANALYZE THE SYSTEM DISK To analyze the system disk for inconsistencies and errors in the file structure, enter the following command: $ ANALYZE/DISK_STRUCTURE SYS$SYSDEVICE The following message represents normal behavior; you can ignore it: %ANALDISK-I-OPENQUOTA, error opening QUOTA.SYS If you find any other errors on the system disk, repair the errors by entering the following command: $ ANALYZE/DISK_STRUCTURE/REPAIR SYS$SYSDEVICE Refer to the OpenVMS System Management Utilities Reference Manual for more information on the ANALYZE/DISK_STRUCTURE command. 5.6.6 CHECK PAGE AND SWAP FILES Digital recommends that the page file be located on the system disk in SYS$SPECIFIC:[SYSEXE] for the upgrade. The swapfile (SWAPFILE.SYS) does not need to be located on the system disk for the upgrade, but if it is located on the system disk, the file must be located in SYS$SPECIFIC:[SYSEXE]. If the upgrade procedure finds the page files and swap files in the common directory, it will move them to the system-specific directory before continuing. The page file must be at least 4600 blocks. If the upgrade procedure detects fewer than 4600 blocks, it displays a message that gives you the option of continuing the upgrade or exiting the procedure and increasing the size of the page file. If you get this message, Digital recommends that you exit the procedure, increase the page file to at least 4600 blocks, and restart the upgrade procedure. 5-12 Before Upgrading OpenVMS VAX Software Before Upgrading OpenVMS VAX Software 5.6 Preparing Your System Disk To check the size of your page file and enter a new size if needed, use the following procedure: 1. To determine the size of the page file, enter the following command: $ @SYS$UPDATE:SWAPFILES The procedure displays the size of the page file and asks you to enter a new value, as follows: Enter new size for paging file: If the page file (PAGEFILE.SYS) size is greater than 4600 blocks, press the Return key. If it is less than 4600 blocks, enter 4600 and press Return. 2. If the swap and dump files are on the system disk, the procedure displays the sizes of each file. To keep the current values, press Return after each prompt. If the swap file is not on the system disk, the procedure asks if you want to create one. You do not need swap and dump files on the system disk for the upgrade procedure. Enter the appropriate response for your system. If you changed the size of the page file or created a swap file, a message is displayed that tells you to reboot the system. Do not reboot now. You will reboot later. 5.6.7 CHECK FOR FREE BLOCKS Check the system disk to make sure there is enough room for the upgrade. To determine whether you have enough room, enter the following command: $ SHOW DEVICE SYS$SYSDEVICE To upgrade the OpenVMS VAX required files, the minimum number of free blocks required is 48,950. Even if you plan to upgrade the OpenVMS library or optional files, you might not need more than 48,950 free blocks because many files are deleted as the upgrade progresses, thus freeing up additional space. Before Upgrading OpenVMS VAX Software 5-13 Before Upgrading OpenVMS VAX Software 5.6 Preparing Your System Disk 5.6.8 CHECK QUOTAS AND LIMITS Use the Authorize utility (AUTHORIZE) to make sure the SYSTEM account has sufficient quotas and limits. To check and, if necessary, modify quota and limit values, do the following: 1. Enter the following commands: $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> SHOW SYSTEM AUTHORIZE displays the SYSTEM account's quota and limit values. 2. Compare the values displayed on your screen to the following minimum required values: ________________________________________________________ Quota_or_Limit_Name_________________Minimum_Value_______ Open file quota (FILLM) 300 Buffered I/O limit (BIOLM) 18 Direct I/O limit (DIOLM) 18 AST limit (ASTLM) 24 Enqueue quota (ENQLM) 200 Buffered byte quota count (BYTLM) 32768+ +If you are using an InfoServer device to upgrade your system, increase the value of BYTLM to 33150 3. If necessary, adjust the quota and limit values in your SYSTEM account so that they are equal to or greater than the minimum required values. To change the value for a quota or limit, enter the MODIFY SYSTEM command using the following format: MODIFY SYSTEM/limit=new_value For example: UAF> MODIFY SYSTEM/DIOLM=18 5-14 Before Upgrading OpenVMS VAX Software Before Upgrading OpenVMS VAX Software 5.6 Preparing Your System Disk 4. Exit the Authorize utility by entering the following command: UAF> EXIT 5. If you adjusted the values for any of the SYSTEM account quotas or limits, log out and log back in to have the new values take effect. 5.6.9 SET SYSTEM PARAMETERS During the upgrade procedure, the system is shut down and rebooted a number of times. You must boot the system minimum (STARTUP_P1 set to MIN) before you begin the upgrade (see Section 5.7). This prevents startup of certain system integrated products and layered products on the system during each reboot. To set the system parameter STARTUP_P1 to MIN, enter the following commands: $ RUN SYS$SYSTEM:SYSMAN SYSMAN> PARAMETERS USE CURRENT SYSMAN> PARAMETERS SET STARTUP_P1 "MIN" SYSMAN> PARAMETERS WRITE CURRENT SYSMAN> EXIT Make sure the system parameters SCSNODE and SCSSYSTEMID are defined on your system. To determine whether these parameters are defined on your system, enter the following commands: $ RUN SYS$SYSTEM:SYSMAN SYSMAN> PARAMETERS SHOW SCSNODE SYSMAN> PARAMETERS SHOW SCSSYSTEMID If SCSNODE and SCSSYSTEMID are not set correctly, enter the following commands where node is a 1- to 6-character unique DECnet node name and systemid is (DECnet area * 1024) + node number: SYSMAN> PARAMETERS USE CURRENT SYSMAN> PARAMETERS SET SCSNODE "node" SYSMAN> PARAMETERS SET SCSSYSTEMID systemid SYSMAN> PARAMETERS WRITE CURRENT . . . Make sure the system parameter VMS5 is set to 0. If your Before Upgrading OpenVMS VAX Software 5-15 Before Upgrading OpenVMS VAX Software 5.6 Preparing Your System Disk system has a KFQSA controller, the VMS5 parameter might have been set to a nonzero value for a previous upgrade. The VMS5 parameter is reserved for Digital's use only. To check the value of the VMS5 parameter, enter the following commands: $ RUN SYS$SYSTEM:SYSMAN SYSMAN> PARAMETERS USE CURRENT SYSMAN> PARAMETERS SHOW VMS5 Parameter Name Current Default Minimum Maximum Unit Dynamic -------------- ------- ------- ------- ------- ---- ------- VMS5 1 0 0 -1 If the current value of VMS5 is not 0, set it to 0 by entering the following commands: SYSMAN> PARAMETERS USE CURRENT SYSMAN> PARAMETERS SET VMS5 0 SYSMAN> PARAMETERS WRITE CURRENT SYSMAN> EXIT If you used the Snapshot facility to boot your current system with a system snapshot image, you must change the BOOT_STYLE system parameter to 0 before you can perform an upgrade. To change the BOOT_STYLE system parameter to 0, enter the following commands: $ RUN SYS$SYSTEM:SYSMAN SYSMAN> PARAMETERS USE CURRENT SYSMAN> PARAMETERS SET BOOT_STYLE 0 SYSMAN> PARAMETERS WRITE CURRENT SYSMAN> EXIT $ You can reexecute the Snapshot command procedure (SYS$MANAGER:SNAPSHOT.COM) after the upgrade is completed, as described in the OpenVMS System Manager's Manual: Essentials. 5-16 Before Upgrading OpenVMS VAX Software Before Upgrading OpenVMS VAX Software 5.6 Preparing Your System Disk 5.6.10 CHECK AGEN$INCLUDE FILES During an upgrade, user disks are not mounted and SYLOGICALS.COM is not invoked, so AUTOGEN can access only data files that are on the system disk and whose file specification includes a logical name that is shipped as part of the OpenVMS operating system. Therefore, if you use AGEN$INCLUDE in SYS$SYSTEM:MODPARAMS.DAT to point to data files that are not on the system disk, follow these steps before you perform an upgrade: 1. Copy any files that you want AUTOGEN to include to a directory on the system disk. 2. For each file that you move, change the file specification on the AGEN$INCLUDE line in SYS$SYSTEM:MODPARAMS.DAT to point to the new location of the file on the system disk. If you do not move referenced data files to the system disk, AUTOGEN uses whatever information is available during the upgrade and parameters might be set to values considerably different from what you intend. 5.6.11 ADD MODIFIED SYSTEM PARAMETERS TO MODPARAMS.DAT Any system parameter values that you modified and did not enter in MODPARAMS.DAT are lost during the upgrade. To retain the values of these parameters, enter their names in MODPARAMS.DAT and the value that AUTOGEN needs to add to the default minimum value. For example, if you modified GBLPAGES by 128 pages above the default, add the following line to SYS$SYSTEM:MODPARAMS.DAT: ADD_GBLPAGES=128 When AUTOGEN runs after the upgrade, it uses the values in MODPARAMS.DAT. Section 5.7 tells you how to get your system ready for an upgrade. Before Upgrading OpenVMS VAX Software 5-17 Before Upgrading OpenVMS VAX Software 5.7 Preparing the System 5.7 Preparing the System To prepare the system for the upgrade, use the procedure described in the following rdsections. 5.7.1 ENABLE AUTO RESTART OR MANUAL REBOOT If your computer uses console media, set the computer to restart automatically. For some VAX computers this means setting one or more switches. For others, this means entering certain console mode commands. To determine how to enable auto restart, refer to the upgrade and installation supplement for your VAX computer. If you have a system that does not use console media, set your system so you can reboot it manually. For more information, refer to the upgrade and installation supplement for your VAX computer. 5.7.2 SHUT DOWN AND REBOOT THE SYSTEM Shut down and reboot the system to activate any system parameters that you changed (STARTUP_P1, for example). To shut down the system, enter the following command: $ @SYS$SYSTEM:SHUTDOWN When the procedure asks if an automatic system reboot should be performed, type Y (for YES) and press the Return key. After the system reboots, log in to the SYSTEM account. 5.7.3 PREVENT INTERACTIVE LOGINS To prevent users from logging in to the system during the upgrade, enter the following command: $ SET LOGINS/INTERACTIVE=0 5.7.4 CHECK FOR DECNET To determine whether your system is running DECnet for OpenVMS software, enter the following command: $ SHOW LOGICAL SYS$NODE 5-18 Before Upgrading OpenVMS VAX Software Before Upgrading OpenVMS VAX Software 5.7 Preparing the System If the system displays the following message, DECnet is not running on your system and you can proceed to Section 5.7.6: %SHOW-S-NOTRAN, no translation for logical name SYS$NODE If the system responds with a translation for SYS$NODE, then DECnet is running on your system. If you set STARTUP_P1 to MIN as described in Section 5.6.9, DECnet should not be running. To set STARTUP_P1 to MIN, repeat all of the preceding steps beginning with Section 5.6.9. Note that you must shut down and reboot the system for any changes you make to system parameters to take effect. 5.7.5 CHECK FOR VOLUME SHADOWING Phase I (controller-based) shadowing is no longer available. Phase II (host-based) shadowing is designed to fully replace phase I shadowing with significantly enhanced features. If you have volume shadowing installed on your system but are unsure which phase, you can enter the following commands: $ RUN SYS$SYSTEM:SYSMAN SYSMAN> PARAMETERS USE CURRENT SYSMAN> PARAMETERS SHOW SHADOWING If the SHADOWING parameter is 1 or 3, then you have phase I shadowing currently loaded on your system. For information about migrating to phase II, see Volume Shadowing for OpenVMS. At the beginning of an upgrade, the procedure checks the setting of the SHADOWING system parameter. If you have not migrated to phase II and the procedure detects the presence of phase I shadowing, it displays the following message and asks if you want to continue the upgrade: The SHADOWING system parameter (currently set to 1) specifies phase I of volume shadowing, which is no longer available as of OpenVMS VAX Version 6.1. If you continue with this upgrade, volume shadowing will not be present on your system after the upgrade has completed. Please consult the Volume Shadowing for OpenVMS manual for instructions about moving to phase II of volume shadowing. Before Upgrading OpenVMS VAX Software 5-19 Before Upgrading OpenVMS VAX Software 5.7 Preparing the System * Do you want to continue the upgrade? At that point, you can exit the upgrade procedure, follow the instructions in Volume Shadowing for OpenVMS for migrating to phase II shadowing, and restart the upgrade procedure from the beginning. If you continue with the upgrade without migrating to phase II, volume shadowing will not be present on your system after the upgrade has completed. 5.7.6 STOP QUEUES To stop all batch and print queues on the node you are upgrading, enter the following command: $ STOP/QUEUES/ON_NODE It is not necessary to stop queues on nodes that you are not upgrading. 5.8 Gathering Information for the Upgrade At different points during the upgrade, the procedure prompts you to supply information. To save time once the procedure begins, be sure you have the following information readily available. Remember, entering incorrect information during the upgrade could force you to repeat the entire upgrade procedure. _________________________________________________________________ Required Information________Explanation___________________________________ Device names You will need to specify the device names for the drives that will hold the distribution media and the system disk. Passwords You will be prompted to type passwords of at least 8 characters for the SYSTEM, SYSTEST, and FIELD accounts. 5-20 Before Upgrading OpenVMS VAX Software Before Upgrading OpenVMS VAX Software 5.8 Gathering Information for the Upgrade _________________________________________________________________ Required Information________Explanation___________________________________ Optional The upgrade procedure prompts you to specify components whether you want to install the library and OpenVMS (VMS071.C), optional (VMS071.D) OpenVMS Management components, and OpenVMS Management Station Station files software PC files (VMS071.F). Appendix D lists the files included in these save sets. You can save some space on your system disk if you choose not to install these components, but be sure to review Appendix D before deciding. Location for Help Save set VMS071.E contains the online Help Message utility Message utility, which you can install on your system disk or on an alternate disk. (However, if you copied the distribution kit to some other media from which you will be performing the installation, you cannot install this save set on that media.) DECwindows The installation procedure prompts you to components specify which of the following DECwindows components you want to install: o DECwindows base support (required for running DECwindows software), which includes: - DECwindows transport - DECwindows keymaps o DECwindows workstation support (required for VAX workstations), which includes: - DECwindows X11 display server - Graphics drivers - 75 dots/inch video fonts - 100 dots/inch video fonts (option available only if you select DECwindows workstation support) Note that you must install the DECwindows Motif for OpenVMS (previously called VMS DECwindows Motif) layered product if you want to run the DECwindows software. DECwindows Motif for OpenVMS Version 1.2-3 (or 1.2 if the VAXMOTF05_012 remedial kit is installed) is the minimum supported version for systems running OpenVMS VAX Version 7.1. If you do not know which version of DECwindows Motif you are currently running on your system, you can check by entering the following command: $ ANALYZE/IMAGE SYS$LIBRARY:DECW$XLIBSHR.EXE Also note that the layered product does not have the DECwindows base and workstation support components. To get full DECwindows support, you must select the DECwindows components provided with the OpenVMS VAX Version 7.1 kit and install the separate DECwindows Motif for OpenVMS VAX layered product, which supports both Motif and XUI environments. Before Upgrading OpenVMS VAX Software 5-23 Before Upgrading OpenVMS VAX Software 5.8 Gathering Information for the Upgrade _________________________________________________________________ Required Information________Explanation___________________________________ PAK information The information listed on Product Authorization Keys (PAKs) for any new products you will register. You do not need to register your OpenVMS VAX license or the licenses for any System Integrated Products (SIPs) you are already_running. _________________________________________________________________ 5.9 Preupgrade Checklist Before you begin the upgrade procedure, use the following checklist to make sure you have completed all the necessary preupgrade tasks. < Read the OpenVMS Version 7.1 New Features Manual, the OpenVMS Version 7.1 Release Notes, and any cover letters that came with your kit. < Read the cautions and restrictions described at the beginning of this chapter and in Chapter 1. < Make sure you have enough free blocks for the upgrade. You need at least 48,950 free blocks for the required files to start the upgrade. (Described in Section 5.6.) The entire upgrade requires about 163,000 blocks. < 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 connect a hardcopy device to your console to record the procedure, see the upgrade and installation supplement for your VAX computer. < Check your AUTOGEN feedback information to be sure it is valid before rebooting the system. (Described in Section 5.4.) < Make a backup copy of the system disk and, if applicable, of the console media. (Described in the upgrade and installation supplement for your computer.) 5-24 Before Upgrading OpenVMS VAX Software Before Upgrading OpenVMS VAX Software 5.9 Preupgrade Checklist < If, in previous versions, your distribution kit provided standalone BACKUP on one of the following media types, make sure you have created a standalone BACKUP kit on one of the following media types: RX33 TU58 RX50 RX01 RL02 (Described in Section 5.5.) < Make sure SYSUAF.DAT is in the SYS$COMMON:[SYSEXE] and VMS$AUDIT_SERVER.DAT is in the SYS$COMMON:[SYSMGR] directory. (Described in Section 5.6.) < Make sure SWAPFILE.SYS (if it is located on the system disk) and PAGEFILE.SYS are in the SYS$SPECIFIC:[SYSEXE] directory. (Described in Section 5.6.) < Make sure the page file is at least 4600 blocks. (Described in Section 5.6.) < If you have a shared system dump file in SYS$COMMON:[SYSEXE], make sure the shared file is not named SYSDUMP.DMP. (Described in Section 5.6.) < If your system disk is part of a shadow set, create a nonshadowed system disk to upgrade. (Described in Volume Shadowing for OpenVMS.) < Make sure the SYSTEM account has sufficient quotas and limits. (Described in Section 5.6.) < Set the appropriate system parameters and make sure that STARTUP_P1 is set to MIN. (Described in Section 5.6.) < Define the system parameters SCSNODE and SCSSYSTEMID. (Described in Section 5.6.) < If your system has a KFQSA controller, make sure the VMS5 parameter is set to 0. (Described in Section 5.6.) < Check the location of your AGEN$INCLUDE files. (Described in Section 5.6.10.) < Set up the system to restart automatically. (Described in the upgrade and installation supplement for your VAX computer.) Before Upgrading OpenVMS VAX Software 5-25 Before Upgrading OpenVMS VAX Software 5.9 Preupgrade Checklist < Shut down and reboot the system from which you will perform the upgrade. If you are upgrading a VAXcluster, shut down all computers that boot from the system disk you are upgrading. < Set interactive logins to 0. < Shut down DECnet for OpenVMS software. (Described in Section 5.7.) < Migrate to phase II volume shadowing if you are currently using phase I. (Described in Section 5.7.) < Stop all batch and print queues on the node you are upgrading. (Described in Section 5.7.) < Make sure you have the following information (described in Section 5.8) available: o The device names of the drives that will hold the system disk and the distribution media. o Passwords of at least 8 characters for the SYSTEM, SYSTEST, and FIELD accounts. o A list of optional OpenVMS VAX components you want to install. o A list of optional DECwindows components you want to install. o The information listed on Product Authorization Keys (PAKs) for any new product licenses you will register. < Create a command procedure to be used when booting from [SYSF]. See Appendix C. To upgrade a standalone system, go to Chapter 7. To upgrade a VAXcluster environment, go to Chapter 6. 5-26 Before Upgrading OpenVMS VAX Software 6 _________________________________________________________________ Upgrading a VAXcluster Environment 6.1 Overview This chapter describes how to upgrade a VAXcluster environment. Refer to OpenVMS Cluster Systems for more detailed information on VAXcluster environments. If your cluster environment has both VAX and Alpha systems, you should also refer to the Migrating an Environment from OpenVMS VAX to OpenVMS Alpha. 6.2 Concurrent and Rolling 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. 6.2.1 CONCURRENT UPGRADES 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 VAX computer. If all systems in the VAXcluster environment are booted from one system disk, you must perform a concurrent upgrade. ________________________ Note ________________________ For OpenVMS VAX Version 7.1 concurrent upgrades, all nodes in the cluster must be running at least OpenVMS VAX Version 6.1. (See Section 5.2.10 for more information.) ______________________________________________________ To perform a concurrent upgrade, go to Section 6.3. Upgrading a VAXcluster Environment 6-1 Upgrading a VAXcluster Environment 6.2 Concurrent and Rolling Upgrades 6.2.2 ROLLING UPGRADES During a rolling upgrade, you can keep some of the VAX computers in the cluster running while you upgrade others (you must have more than one system disk). The cluster runs temporarily with different versions of the operating system. ________________________ Note ________________________ For OpenVMS VAX Version 7.1 rolling upgrades, all nodes in the cluster must be running at least OpenVMS VAX Version 6.1. (See Section 5.2.10 for more information.) ______________________________________________________ To perform a rolling upgrade, go to Section 6.4. 6.3 Performing a Concurrent Upgrade You perform a concurrent upgrade by shutting down the entire cluster, upgrading each system disk, and rebooting each VAX computer in the cluster. When the cluster reboots, each VAX computer will be running the upgraded version of the operating system. Users cannot access the cluster until you upgrade each system disk and reboot each VAX computer. 6.3.1 CONCURRENT UPGRADE PROCEDURE To perform a concurrent upgrade, use the following procedure: 1. Shut down the entire cluster by logging in to the SYSTEM account on each node locally, entering the following command, and choosing the CLUSTER_SHUTDOWN option: $ @SYS$SYSTEM:SHUTDOWN 2. If you have only one system disk for your cluster, go to step 3. If you have more than one system disk, select one to upgrade. 6-2 Upgrading a VAXcluster Environment Upgrading a VAXcluster Environment 6.3 Performing a Concurrent Upgrade _______________________ Caution _______________________ You cannot use the system disk that you usually use as the quorum disk to hold the save sets from the distribution kit. ______________________________________________________ 3. Perform a conversational boot of a single VAX computer from the system disk you will be upgrading. For more information about the conversational boot procedure, refer to the upgrade and installation supplement for your VAX computer. At the SYSBOOT> prompt, use the SHOW VOTES and SHOW EXPECTED_VOTES command to display the current values of the parameters. Write these values down because you will need to restore them later. Set the VOTES and EXPECTED_ VOTES values to 1 by entering the following commands: SYSBOOT> USE CURRENT SYSBOOT> SET VOTES 1 SYSBOOT> SET EXPECTED_VOTES 1 SYSBOOT> CONTINUE 4. Upgrade the system disk, using the procedure in Chapter 7. 5. If you have only one system disk, go to step 6. If you have more than one system disk, shut down the system that you just upgraded. Then repeat steps 2 through 4 to upgrade each system disk in the cluster. When you finish upgrading all of the system disks, go to step 6. 6. Reboot each computer in the VAXcluster environment. 7. Complete the postupgrade procedures described in Chapter 8. Upgrading a VAXcluster Environment 6-3 Upgrading a VAXcluster Environment 6.4 Performing a Rolling Upgrade 6.4 Performing a Rolling Upgrade During a rolling upgrade, you upgrade each system disk individually, allowing old and new versions of the operating system to run together temporarily in the same cluster. Clusters running two versions of the operating system are called mixed-version clusters. Because rolling upgrades allow mixed-version clusters, the systems that you are not upgrading remain available. 6.4.1 RESTRICTIONS The following restrictions apply to rolling upgrades: o Digital recommends that all VAX computers in a cluster run the same version of the operating system. Mixed- version clusters are supported only for the purpose of upgrading the entire cluster incrementally. Digital further recommends that all VAX systems in a VAXcluster run the latest version of the OpenVMS VAX operating system. o A rolling upgrade does not apply when all systems boot from a single system disk. When all systems boot from a single system disk, perform a concurrent upgrade using the procedure described in Section 6.3. o During the rolling upgrade, the queuing system is disabled on the nodes being upgraded. The queuing system on the other nodes should be unaffected by the upgrade as long as a START/QUEUE/MANAGER/ON=(upgrade node . . .) command is not executed. A START/QUEUE/MANAGER command could attempt to move the queue manager process to the node being upgraded if the /ON qualifier indicates that it is one of the preferred nodes. If the queue manager attempts to run on the node being upgraded, the queuing system will hang on the entire cluster. If your startup file contains a START/QUEUE/MANAGER /ON=(upgrade node1, node2 . . . noden) command, do not boot in any nonupgrading nodes until you have removed that command from the startup file. Booting in a node will cause the queuing system to hang on the cluster if the START/QUEUE/MANAGER/ON=(upgrade node, . . . ) command is executed. When the upgrade has completed, you can add the command back to the startup file. 6-4 Upgrading a VAXcluster Environment Upgrading a VAXcluster Environment 6.4 Performing a Rolling Upgrade If the cluster queuing system hangs during the upgrade, it is most likely caused by the queue manager attempting to run on the upgrading node. To clear the condition, move the queue manager to a node you are not upgrading by entering the following command: START/QUEUE/MANAGER/ON=(nonupgrading node1,- node2 . . . noden) 6.4.2 ROLLING UPGRADE PROCEDURE To perform a rolling upgrade follow these steps: 1. Check the votes and make adjustments to maintain the proper quorum so the cluster can continue to operate throughout the upgrade. (OpenVMS Cluster Systems describes this procedure in detail.) 2. Select a system disk to upgrade. 3. Shut down all VAX computers booting from the system disk that you are upgrading, except for the computer that you will use to apply the upgrade. VAX computers that do not boot from the system disk that you are upgrading remain available to users. a. Log in to the SYSTEM account on the VAX computer you are shutting down. b. Enter the following command: $ @SYS$SYSTEM:SHUTDOWN.COM c. On one of the VAX computers that is still running, enter the following command: $ SET CLUSTER/EXPECTED_VOTES d. Repeat steps a through c for each VAX computer requiring a shutdown. This procedure lets one VAX computer continue running from the system disk (assuming computers running from different system disks supply enough votes to sustain cluster quorum). 4. 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, Upgrading a VAXcluster Environment 6-5 Upgrading a VAXcluster Environment 6.4 Performing a Rolling Upgrade enter the following commands on the system console of a CPU that is still a cluster member: $ >>> H >>> D/I 14 C >>> C IPC> Q IPC> 5. Upgrade the system disk using the procedure in Chapter 7. _______________________ Caution _______________________ The upgrade procedure requires exclusive access to the drive that holds the distribution media. Do not mount the distribution media on other nodes. ______________________________________________________ 6. During phase 1 of the upgrade, the procedure will ask if you are performing a rolling upgrade. If you enter Y, the procedure asks you several questions to determine if all system disks in the cluster (other than the one you are upgrading) are running at least OpenVMS VAX Version 6.1. For example: * Are the other system disks running OpenVMS V6.1 or higher? All systems in the cluster must be running at least OpenVMS VAX Version 6.1 to perform the rolling upgrade. Type Y and press the Return key. 7. When the upgrade has completed, reboot each VAX computer that boots from the system disk you have just upgraded. 8. Perform the postupgrade tasks described in Chapter 8. 9. Repeat steps 2 through 7 for each system disk you are upgrading. Once you have performed tasks a through d in step 3, you do not need to perform them again. 6-6 Upgrading a VAXcluster Environment Upgrading a VAXcluster Environment 6.5 Adding an OpenVMS VAX Version 7.1 Supported CPU 6.5 Adding an OpenVMS VAX Version 7.1 Supported CPU If you need to add a new CPU supported by OpenVMS VAX Version 7.1 to an existing Version 6.1 VAXcluster, Digital supports two options, listed in the following preferred order: 1. Upgrade the entire cluster to OpenVMS VAX Version 7.1 and bring the new CPU in as a member. 2. If you need to keep some systems in the cluster at OpenVMS VAX Version 6.1, you must upgrade a system disk in the cluster to Version 7.1 using the rolling upgrade procedure and then boot the new CPU into the cluster using that system disk. Upgrading a VAXcluster Environment 6-7 7 _________________________________________________________________ Upgrading the OpenVMS VAX Operating System 7.1 Overview This chapter explains the procedure for upgrading a single OpenVMS VAX system disk, including: o How to prepare for booting from the [SYSF] directory o How to configure devices o How to begin the upgrade o What the procedure does and what you are asked to do during the six phases of the upgrade You must complete each phase of the upgrade procedure. On most VAX computers the upgrade procedure continues automatically from phase to phase. Read the screen displays carefully and, if you need to reboot your VAX computer manually, refer to the upgrade and installation supplement for your VAX computer and Appendix C of this manual. The time required to complete an upgrade varies depending on your hardware configuration and on the distribution media you are using. In most cases, magnetic tapes and tape cartridges require more time than compact discs. Before you begin the upgrade procedure, read the overview of the upgrade procedure described in Chapter 1 and complete the preupgrade tasks described in Chapter 5. If you are upgrading a VAXcluster, you must also read Chapter 6. Upgrading the OpenVMS VAX Operating System 7-1 Upgrading the OpenVMS VAX Operating System 7.2 Preparing to Boot from [SYSF] 7.2 Preparing to Boot from [SYSF] During the upgrade procedure, you are asked to boot the system from the [SYSF] directory on the system disk. The [SYSF] directory is a root directory created on the system disk by the upgrade procedure. It temporarily holds the system files used in the upgrade until the procedure moves the files to their permanent location. The upgrade procedure then removes the [SYSF] directory from the system disk. If you do not know how to boot from [SYSF], read the upgrade and installation supplement for your VAX computer and Appendix C of this manual. Ignore any error messages after the first reboot that indicate an invalid dump header version. These messages are normal and are to be expected. 7.2.1 MODIFYING BOOT COMMAND PROCEDURES Some VAX computers require a special command procedure to boot from [SYSF]. If you are performing an upgrade on one of the following VAX computers you must modify the boot command procedures, DEFBOO and dddGEN before beginning the upgrade procedure: VAX 8530, 8550, 8700, 8810, 8820-N VAX 8820, 8830, 8840 To modify the boot command procedures, exit from the OpenVMS VAX operating system (but do not shut it down) and enter the appropriate console mode. Make copies of DEFBOO and dddGEN before you modify them. Name the copies DEFBOO.SAV and dddGEN.SAV. The upgrade and installation supplement for your VAX computer describes the procedures for copying and modifying DEFBOO and dddGEN. Use these procedures to modify DEFBOO and dddGEN so that they specify [SYSF] as the directory from which to boot. In DEFBOO, change the DEPOSIT command that sets boot flags in register 5 (R5) as follows: DEPOSIT R5=F0000000 7-2 Upgrading the OpenVMS VAX Operating System Upgrading the OpenVMS VAX Operating System 7.2 Preparing to Boot from [SYSF] In dddGEN, change the DEPOSIT command as follows: DEPOSIT R5 F0000001 7.2.2 VAX 8200, 8250, 8300, AND 8350 COMPUTERS If you are upgrading a VAX 8200, 8250, 8300, or 8350 computer, you must create a boot command procedure that allows you to boot from the [SYSF] directory before beginning the upgrade. The upgrade and installation supplement for your VAX computer describes how to create this boot command procedure. 7.2.3 CONFIGURING DEVICES Because you rebooted your system with minimum startup, the system did not automatically configure all devices. However, you might need access to some of the devices to perform the upgrade. To make sure you can access the devices that might be needed for the upgrade, run SYSGEN to reconfigure the devices on the system and run STARTUP CONFIGURE by entering the following commands: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> AUTOCONFIGURE ALL SYSGEN> EXIT $ @SYS$SYSTEM:STARTUP CONFIGURE 7.3 Beginning the Upgrade Procedure This section describes how to start the upgrade procedure using VMSINSTAL. You can type a question mark (?) for help at any time while running VMSINSTAL. The instructions refer to the source drive and the target drive, where: o The source drive is the drive that holds the distribution kit. o The target drive is the drive that holds the system disk. Upgrading the OpenVMS VAX Operating System 7-3 Upgrading the OpenVMS VAX Operating System 7.3 Beginning the Upgrade Procedure 7.3.1 STEP 1: LOAD DISTRIBUTION MEDIA Put the distribution compact disc or tape in the source drive. If your OpenVMS VAX distribution kit contains several tapes, put the first one in the drive. The paper labels on the tapes indicate the order in which you use them. If you are not using an InfoServer device, go to Section 7.3.3. If you are using an InfoServer device, proceed to the next step. 7.3.2 STEP 2: UPGRADING FROM THE INFOSERVER If upgrading from an InfoServer device, perform the following steps: 1. Start the InfoServer Client software by entering the following command: $ @SYS$STARTUP:ESS$STARTUP CLIENT The CLIENT parameter loads the client driver, ESS$DADDRIVER.EXE, and the InfoServer transport driver, ESS$LASTDRIVER.EXE. 2. As the startup procedure executes, it displays the following messages: %LASTCP-I-VERSION, LASTDRIVER X1.5 is stopped %LASTCP-I-ADAINIT, Initializing adapter xxx for LASTDRIVER %LASTCP-I-STARTED, LASTDRIVER X1.5 started on node yyy 3. After you start the InfoServer Client software, you must make the compact disc drive accessible to your system by completing the following steps: a. Insert the distribution compact disc in the compact disc drive connected to the InfoServer. b. Enter the following commands: $ RUN SYS$SYSTEM:ESS$LADCP LADCP> BIND/CONNECT/SYSTEM VAXVMS071 %LADCP-I-BIND, service bound to logical unit DAD$VMS071 (_DADn:) LADCP> EXIT 7-4 Upgrading the OpenVMS VAX Operating System Upgrading the OpenVMS VAX Operating System 7.3 Beginning the Upgrade Procedure Make note of the device name _DADn: in the previous display. You will have to specify this device name during the upgrade. 7.3.3 STEP 3: START VMSINSTAL To start VMSINSTAL, use the following procedure: 1. Log in to the SYSTEM account. 2. Enter the following command: $ @SYS$UPDATE:VMSINSTAL VMSINSTAL displays a message similar to the following, depending on which version of the operating system is currently running on your system: OpenVMS VAX Software Product Installation Procedure V7.0 It is 22-NOV-1996 at 15:00.00.00 Enter a question mark (?) at any time for help. VMSINSTAL checks your system's account quotas. If it finds account quotas that are less than it expects, VMSINSTAL displays a message similar to the following: %VMSINSTAL-W-LOWQUOTA, The following account quotas may be too low. -VMSINSTAL-W-LOWQUOTA, If you want to modify these account quotas, type NO to -VMSINSTAL-W-LOWQUOTA, the next question, modify the appropriate quotas, log out -VMSINSTAL-W-LOWQUOTA, then log back in and restart this procedure. BYTLM: currently 32512; minimum expected 32768 * Do you want to continue anyway [NO]? You should have verified that your SYSTEM account quotas were sufficient before beginning the upgrade. (See Section 5.6.8 for the minimum required values and for instructions for modifying quotas and limits.) To modify the account quotas now, do the following: 1. Type No and press the Return key. 2. Modify the account quotas you want to change. 3. Log out of the SYSTEM account; then log back in so that the new quotas will be in effect. Upgrading the OpenVMS VAX Operating System 7-5 Upgrading the OpenVMS VAX Operating System 7.3 Beginning the Upgrade Procedure 4. Restart VMSINSTAL. To continue the upgrade without modifying the account quotas, type Yes and press the Return key. 7.3.4 STEP 4: BACK UP THE SYSTEM DISK The procedure displays the following message: * Are you satisfied with the backup of your system disk [YES]? If you have made a standalone backup of the system disk, press Return and go to Section 7.3.5. If you have not made a standalone image backup of the system disk, do the following: 1. Type N (for No) and press Return. VMSINSTAL ends and the dollar-sign prompt ($) is displayed. 2. Back up the system disk as described in the upgrade and installation supplement for your VAX computer. 3. After you have made a backup of the system disk, start the upgrade procedure again. 7.3.5 STEP 5: SPECIFY THE SOURCE DRIVE VMSINSTAL asks for the name of the drive that holds the distribution media: * Where will the distribution volumes be mounted: Enter the device name of the source drive. For example, if you have a VAX 6000 series computer that has a TK70 with a device name of MUC6, type MUC6 and press the Return key. If the drive is connected to an HSC, enter the HSC name and the device name of the drive separated by a dollar sign ($). (If you do not enter the device name in this manner, it will cause a failure in Phase 2.) For example, if the HSC name is MUTT and the device name is MUA0, enter the following and press Return: * Where will the distribution volumes be mounted: MUTT$MUA0 If you are not using an InfoServer device, proceed to Section 7.3.6. 7-6 Upgrading the OpenVMS VAX Operating System Upgrading the OpenVMS VAX Operating System 7.3 Beginning the Upgrade Procedure If you are upgrading from a compact disc drive connected to an InfoServer, the device name is DADn. The n part of the device name was displayed when you bound to the distribution compact disc as previously described in Section 7.3.2. If VMSINSTAL displays an error message, make sure the drive is connected and set up properly. Enter the name again. If VMSINSTAL displays another error message, use the following procedure to verify the device name: 1. Press Ctrl/Y to exit from VMSINSTAL. 2. Enter the SHOW DEVICE command to make sure you have the correct device name. 3. Restart the upgrade procedure from Section 7.3.3. If VMSINSTAL does not display an error message, proceed to Section 7.3.6. 7.3.6 STEP 6: ENTER PRODUCT NAME When VMSINSTAL displays the following message, type VMS071 and press the Return key. Make sure that you use the number zero (not the letter "O") when you type VMS071. For example: * Products: VMS071 When the procedure displays the following message, press Return: * Enter installation options you wish to use (none): 7.3.7 STEP 7: MOUNT THE FIRST VOLUME VMSINSTAL displays a message similar to the following: Please mount the first volume of the set on _MUA0. When the procedure displays the following message, type Y (for Yes) S) and press Return: * Are you ready? Y Upgrading the OpenVMS VAX Operating System 7-7 Upgrading the OpenVMS VAX Operating System 7.3 Beginning the Upgrade Procedure The procedure displays messages similar to the following: %MOUNT-I-MOUNTED, VMS071 mounted on _MUA0: The following products will be processed: OpenVMS V7.1 After a slight pause, the procedure displays a message similar to the following: Beginning installation of OpenVMS V7.1 at 15:05 %VMSINSTAL-I-RESTORE, Restoring product saveset A... 7.3.8 STEP 8: MONITOR MESSAGES FROM VMSINSTAL The upgrade procedure displays several important messages that provide you with the following information: - What VMSINSTAL is doing. - Notes, suggestions, and restrictions about various parts of the upgrade. - Status of the upgrade. Read these messages carefully to decide whether or not you need to interrupt the upgrade procedure. An interruption is allowed before Phase 1. The procedure displays the following message: * Do you want to continue? (Y/N): To continue the upgrade, type Yes and press the Return key. To interrupt the upgrade, do the following: 1. Type No and press Return. 2. If prompted for another product, type EXIT to exit from VMSINSTAL. 7.3.9 STEP 9: VERIFY DATE AND TIME The procedure displays the current date and time. If the date and time are correct, type Yes. If they are incorrect, type No. Enter the correct date and time using the 24-hour clock format and press Return. For example: PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) 22-NOV-1996 15:10 7-8 Upgrading the OpenVMS VAX Operating System Upgrading the OpenVMS VAX Operating System 7.4 Upgrade Phase 1 7.4 Upgrade Phase 1 This section describes Phase 1 of the upgrade. During this phase, you provide passwords for system accounts and select OpenVMS options, and the procedure restores the files in the OpenVMS required save set (VMS071.B). At the end of this phase, the procedure shuts down your VAX computer. If your computer uses console media when booting and the boot file was modified as described in Section 7.2, the system should reboot automatically. Otherwise, you must reboot manually from the SYSF directory. 7.4.1 STEP 1: SPECIFY TYPE OF UPGRADE At the beginning of Phase 1, the procedure displays a message similar to the following: Upgrade Phase 1 22-NOV-1996 15:11:17.05 * Are you performing a rolling upgrade? (Y/N): If you are performing a concurrent upgrade or an upgrade on a standalone system, type No and press the Return key. If you are performing a rolling upgrade, type Yes and press Return. The procedure will ask you several questions to determine if all system disks in the cluster (other than the one you are upgrading) are running at least OpenVMS VAX Version 6.0. Follow the instructions in Section 6.4. 7.4.2 STEP 2: ENTER PASSWORDS To ensure system security, the upgrade procedure requires you to enter passwords for the SYSTEM, SYSTEST, and FIELD accounts before continuing. Passwords must contain at least 8 characters; they are not displayed by the system. Press Return after you enter each password and it will be verified. For example: To help provide a more secure system, you are asked to enter passwords for key system accounts. Passwords must be a minimum of 8 characters in length. You can enter new or existing passwords. Enter passwords for the following accounts: SYSTEM, SYSTEST, FIELD Upgrading the OpenVMS VAX Operating System 7-9 Upgrading the OpenVMS VAX Operating System 7.4 Upgrade Phase 1 * Enter password for SYSTEM: * Re-enter for verification: %UAF-I-MDFYMSG, user record(s) updated %VMS-I-PWD_OKAY, account password for SYSTEM verified * Enter Password for SYSTEST * Re-enter for verification: %UAF-I-MDFYMSG, user record(s) updated %VMS-I-PWD_OKAY, account password for SYSTEST verified The SYSTEST_CLIG account will be disabled. You must re-enable it before running UETP but do not assign a password. %UAF-I-MDFYMSG, user record(s) updated Enter password for FIELD: Re-enter for verification: %UAF-I-MDFYMSG, user record(s) updated %VMS-I-PWD-OKAY, account password for FIELD verified If you enter a password incorrectly or if the password is too easy to guess, the procedure displays error messages similar to the following: %VMS-W-PWD-INVALID, account password for FIELD is invalid %VMS-I-PWD-WEAK, password is too easy to guess Because of the preceding error, you must take action to secure this account. You must either disable this account, change its password, or do both. When the procedure asks if you want to disable the account, type No and press the Return key. When the procedure asks if you want to enter a new password, type Yes and press Return. Then enter a new password. For example: Do you want to disable the account (Y/N)? N Do you want to change the account password (Y/N)? Y You must now select a new primary password for the FIELD account. The password you select must be at least 8 characters in length and cannot be the same as the name of the account. New password: Verification: %UAF-I-MDFMSG, user record(s) updated %VMS-I-PWD-SET, primary password for account FIELD set 7-10 Upgrading the OpenVMS VAX Operating System Upgrading the OpenVMS VAX Operating System 7.4 Upgrade Phase 1 After you have correctly entered the passwords, the procedure does the following: o Checks the account quotas in the DEFAULT, SYSTEM, and various other accounts and modifies them if necessary o Turns off quotas on the system disk o Stops OPCOM o Stops the error formatter (ERRFMT) 7.4.3 STEP 3: CHOOSE BOOT METHOD If your VAX computer is not one of the following, go to Section 7.4.4. VAX-11/730 VAX-11/750 VAX-11/780 VAX 8200, 8250, 8300, 8350 VAX 8600, 8650 VAX 9000 If your VAX computer is included in the preceding list, the procedure can temporarily modify the DEFBOO.CMD (or DEFBOO.COM if you have a VAX 8600 computer) to boot from the [SYSF] directory. During Phase 4 of the upgrade, the procedure restores the DEFBOO.CMD (or DEFBOO.COM) file that is set up to boot from the current system disk and system root. The procedure displays a message similar to the following (except for VAX-11/730, 11/780, and 8600 computers): * Do you want to boot from the [console media]? If you prefer to boot your system manually from the [SYSF] directory or if you are booting directly from a local system disk, type No, press the Return key, and go to Section 7.4.4 to continue the upgrade. Type Yes and press Return if one of the following is true: o You want to boot from the console media. o Your computer is a VAX-11/730, 11/780, or 8600. Upgrading the OpenVMS VAX Operating System 7-11 Upgrading the OpenVMS VAX Operating System 7.4 Upgrade Phase 1 o You are using a CI750. The procedure prompts you to insert the console media in the drive. Insert the backup copy of the console media into the drive and do not remove it from the drive until the upgrade has been completed. Make sure the console media is write enabled. 7.4.4 STEP 4: FILE CLEANUP The procedure does the following: o Checks for the location of the SYS$TIMEZONE.DAT file, which must now must be in the SYS$COMMON:[SYSEXE] directory. If the procedure finds this file in some other directory, it deletes it from that directory. Later, during the final phase of the upgrade, the procedure prompts you for the information it needs to create a SYS$TIMEZONE.DAT file in the SYS$COMMON:[SYSEXE] directory. o Renames files found in SYS$SPECIFIC:[SYSMGR] and in SYS$COMMON:[SYSMGR] by adding _OLD_SPECIFIC to the file extensions. For example, [SYSMGR]LOGIN.COM becomes [SYSMGR]LOGIN.COM_OLD_SPECIFIC. (The file extensions are restored during Phase 6 of the upgrade procedure.) o Cleans up the system disk by purging all accounting data files, operator logs, and the directory SYSERR. The procedure also deletes all JNL files in the root directory and its subdirectories. o Builds the directory tree [SYSF] and deletes the OpenVMS VAX and DECwindows files that are not needed to reboot during Phase 2 of the upgrade. As the procedure performs each of these tasks, it displays messages describing what is being done. When this step is completed, the procedure displays a message similar to the following: File cleanup complete - 22-NOV-1996 15:29:41.92 7-12 Upgrading the OpenVMS VAX Operating System Upgrading the OpenVMS VAX Operating System 7.4 Upgrade Phase 1 7.4.5 STEP 5: SELECT OPTIONAL OPENVMS COMPONENTS The procedure displays information about optional OpenVMS VAX files and the remaining amount of disk space. The information is similar to the following (block sizes might vary slightly): Select optional software you want to install. You can install one or more of the following OpenVMS or DECwindows components: o OpenVMS library - 53400 blocks o OpenVMS optional - 21200 blocks o OpenVMS Help Message - 10200 blocks o OpenVMS Management Station - 21200 blocks o DECwindows base support - 3800 blocks o DECwindows workstation support - 23500 blocks - 75 dots per inch video fonts - (included) - 100 dots per inch video fonts - 6000 blocks o DECnet-Plus networking - 85000 blocks Space remaining on system disk: 682440 blocks You must indicate which of the options you want to install. If you require network support, you must select the OpenVMS library component. Note that, if you do not install the optional OpenVMS components at this time, you can install them after the upgrade by using the VMSTAILOR and DECW$TAILOR utilities. However, the Help Message utility and the three reference manuals can be tailored on to the system disk only. If you do not choose the Help Message files or the three manuals at this point in the procedure and want them on an alternate device, you will not be able to use VMSTAILOR to restore them later. If you want to install Help Message on an alternate disk after the installation procedure completes, you can use the BACKUP command, as follows: BACKUP/VERIFY source-device:[000000]VMS071.E/SAVE_SET- target-device:[directory-name] For source-device, enter the device name for the drive on which the distribution media is mounted. For target- device, enter the device name on which the alternate disk is mounted, and for directory, enter the name of the directory to which you are copying the files. Upgrading the OpenVMS VAX Operating System 7-13 Upgrading the OpenVMS VAX Operating System 7.4 Upgrade Phase 1 Also note that, for TK50 tape cartridges, it is quicker to install OpenVMS VAX software during the upgrade than to add software after the upgrade with a tailoring utility. For information about using VMSTAILOR, see Chapter 10. To select the options you want to install, follow the instructions displayed by the procedure. 7.4.6 OPENVMS LIBRARY FILES The procedure displays the following message: * Do you want to install the OpenVMS library files? (Y/N) The file subclasses of the OpenVMS library (VMS071.C) save set are listed in Appendix D. If you want to install the VMS071.C files, type Yes and press Return. If you require network support, you must select the OpenVMS library component. If you do not want to install the VMS071.C files, type No and press Return. 7.4.7 OPENVMS OPTIONAL FILES The procedure displays the following message: * Do you want to install the OpenVMS optional files? (Y/N) The file subclasses of the OpenVMS optional (VMS071.D) save set are listed in Appendix D. If you want to install the VMS071.D files, type Yes and press Return. If you do not want to install the VMS071.D files, type No and press Return. 7.4.8 HELP MESSAGE FILES The procedure displays the following message: The Help Message utility (MSGHLP) provides online explanations and user actions for OpenVMS messages in place of the hardcopy OpenVMS System Messages and Recovery Procedures Reference Manual, which is now separately orderable. The MSGHLP database, MSGHLP$LIBRARY.MSGHLP$DATA, consumes approximately 10200 blocks and will be placed by default on your system disk in SYS$COMMON:[SYSHLP] unless you specify an alternate device when prompted. 7-14 Upgrading the OpenVMS VAX Operating System Upgrading the OpenVMS VAX Operating System 7.4 Upgrade Phase 1 Users with limited disk space can access the MSGHLP database on a read-only basis at DAD1:[HELP_MESSAGE]. * Do you want to install the MSGHLP database? (Y/N) The Help Message utility is an online system for system messages documentation. You can install Help Message either on the system disk or on an alternate disk. If you want to install the Help Message files, type Yes and press Return. The procedure displays the following message: You can install this database on your system disk in SYS$COMMON:[SYSHLP] or on an alternate device. If you specify an alternate device, but no directory, MSGHLP$LIBRARY.MSGHLP$DATA is placed in [HELP_MESSAGE]. When prompted, take the default of the system disk or specify an alternate device using this format: device:[directory] * Where do you want to install the MSGHLP database? [SYS$COMMON:[SYSHLP]] DUA1 The Help Message database is installed in the area you specified, and the system displays information similar to the following: %MOUNT-I-MOUNTED, VMS071 mounted on DUA1 Space remaining on alternate device DUA1:: 124532 blocks 7.4.9 OPENVMS MANAGEMENT STATION FILES The procedure displays the following message: The OpenVMS Management Station is a client-server application that provides OpenVMS system management capabilities through a client application on a personal computer (PC) running Microsoft Windows. The server application runs on OpenVMS systems and is automatically installed as part of the OpenVMS operating system. This option provides the files used to create the installation media for the PC client software. If you want to use the OpenVMS Management Station, you must install these files on at least one OpenVMS system to create the installation media, which can then be used to install the PC client on one or more PCs. Note: To use the OpenVMS Management Station on your PC, you must be running Digital's PATHWORKS V5.0A for DOS and Windows (or V5.1) software. Upgrading the OpenVMS VAX Operating System 7-15 Upgrading the OpenVMS VAX Operating System 7.4 Upgrade Phase 1 The OpenVMS Management Station optional files consume approximately 212000 blocks and will be placed on your system disk in SYS$COMMON:[TNT.CLIENT]. * Do you want to install the optional OpenVMS Management Station files? (Y/N) Space remaining on system disk: 623240 blocks If you want to use the OpenVMS Management Station software, you must install these files. After the upgrade procedure completes, follow the instructions in Appendix G to prepare your OpenVMS system and your PC to run the OpenVMS Management Station server and client software. 7.4.10 STEP 6: CHOOSE DECWINDOWS SUPPORT OPTIONS Next, the procedure displays messages about the DECwindows components shipped with OpenVMS VAX Version 7.1. The OpenVMS VAX operating system no longer ships the OpenVMS DECwindows product. The operating system now ships only the DECwindows base support and DECwindows workstation support components. To get full DECwindows support, you must also install the separate DECwindows Motif for OpenVMS VAX (previously called VMS DECwindows Motif) layered product, which supports both Motif and XUI environments. Note that the DECwindows base support and DECwindows workstation support components are not shipped with the DECwindows Motif for OpenVMS layered product. If you want to install these options, you must select them now or use the DECW$TAILOR option after the installation procedure completes. Before you indicate whether you want to install DECwindows support software, consider the following: ___________________________________________________________ If you... Then_choose... Intend to install the DECwindows base support. DECwindows Motif layered product 7-16 Upgrading the OpenVMS VAX Operating System Upgrading the OpenVMS VAX Operating System 7.4 Upgrade Phase 1 ___________________________________________________________ If you... Then choose... Intend to install the DECwindows base support and DECwindows Motif layered DECwindows workstation product on a workstation or support. on a VAXcluster system that contains workstations Are not planning to install DECwindows base support and the DECwindows Motif layered DECwindows workstation product but are installing support. OpenVMS VAX on a workstation or on a VAXcluster that includes workstations Want to provide font files DECwindows base support and for X terminals DECwindows workstation support. Have a workstation monitor DECwindows base support and (for example, a VR150, DECwindows workstation VR160, or VR295) capable support with the 100 dots of displaying 100 dots/inch /inch option. or a VAXstation 4000 series By selecting the workstation computer, which uses 100 support files, you dots/inch video fonts by automatically get 75 dots default /inch video font files, and you will be prompted to indicate if you want to install 100 dots/inch video font_files. _______________________________________________________ The procedure displays the following: You can select DECwindows support now, or you can use the DECW$TAILOR utility to provide or remove DECwindows support after upgrade. Some media, TK50s in particular, can be very slow when tailoring on files. You might want to provide DECwindows options now and tailor off unwanted files later. NOTE: This kit does NOT contain full DECwindows. To obtain full DECwindows support, you must also install the separate layered product, DECwindows Motif for OpenVMS VAX. Version 1.2-3 is the minimum version of DECwindows Motif for OpenVMS VAX that can be used with OpenVMS VAX Version 7.1. Upgrading the OpenVMS VAX Operating System 7-17 Upgrading the OpenVMS VAX Operating System 7.4 Upgrade Phase 1 The DECwindows components provided in this kit require approximately 29350 blocks, broken down as follows: o DECwindows base support - 3800 blocks o DECwindows workstation support - 23500 blocks - 75 dots per inch video fonts (included) - 100 dots per inch video fonts (optional) - 6000 blocks You must select the DECwindows base support option if - you plan to run DECwindows software, or - you are installing this kit on * a workstation or * a VAXcluster that contains workstations, or - you want to provide font files for Xterminals. If you are installing this kit on a system that includes Xterminals and you do not select DECwindows base support, then you will have to use the DECW$TAILOR utility to provide font files. * Do you want the DECwindows base support? (Y/N) Space remaining: 619640 You must select the DECwindows workstation support option if - you are installing this kit on * a workstation or * a VAXcluster that contains workstations, or - you want to provide font files for Xterminals. If you are installing this kit on a system that includes Xterminals and you do not select DECwindows base support, then you will have to use the DECW$TAILOR utility to provide font files. * Do you want to provide DECwindows workstation support? (Y/N) Space remaining: 598890 DECwindows workstation support includes the 75 dots per inch video fonts. All DECwindows applications run with 75 dots per inch video fonts. By default, most systems start up with 75 dots per inch video fonts. Certain applications can take advantage of 100 dots per inch video fonts. For the VAXstation 4000 series machine, 100 dots per inch video fonts are used by default. If you decide not to install 100 dots per inch video fonts, you must edit SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM to force 75 dots per inch video fonts to be the default. Otherwise, certain applications may not space text properly. 7-18 Upgrading the OpenVMS VAX Operating System Upgrading the OpenVMS VAX Operating System 7.4 Upgrade Phase 1 For instructions on how to configure your system with both 75 and 100 dots per inch video fonts, see the template command procedure SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE. *Do you want 100 dots per inch video fonts installed? (Y/N) Space remaining: 593890 7.4.11 STEP 7: SELECT NETWORKING SOFTWARE Next, the procedure displays messages describing the DECnet options. For more information, refer to Section 1.2.1. Beginning with OpenVMS V7.1 DECnet-Plus is provided with the OpenVMS operating system. Digital strongly recommends that DECnet users install DECnet-Plus. DECnet Phase IV applications are supported by DECnet-Plus. If you plan to install DECnet Phase IV do NOT select DECnet-Plus. * Do you want to install DECnet-Plus. (Y/N) Y Space remaining on system disk: 508890 blocks 7.4.12 STEP 8: VERIFY YOUR CHOICES The procedure displays a list of OpenVMS VAX and DECwindows support options that you have chosen and gives you the opportunity to change your mind before proceeding by displaying the following message: * Is this correct? (Y/N) If you answer Yes to this prompt, the procedure restores the OpenVMS required save set (VMS071.B) and purges the page, swap, dump, and authorization files. If you answer No to this prompt, you can respecify the OpenVMS VAX and DECwindows options that you want to install. The procedure restores the DECwindows components you have chosen during Phase 2. Upgrading the OpenVMS VAX Operating System 7-19 Upgrading the OpenVMS VAX Operating System 7.4 Upgrade Phase 1 7.4.13 STEP 9: SHUT DOWN YOUR SYSTEM After several minutes, the upgrade procedure indicates that the system will shut down to reboot the partially upgraded OpenVMS VAX system and displays information about how to reboot the system. On certain VAX computers, the procedure displays the following message: * Press RETURN to shutdown system: Once you have read the information displayed on the screen, press Return to begin the shutdown. 7.4.14 STEP 10: REBOOT THE SYSTEM If your system uses console media, it should automatically reboot from the SYSF directory when the shutdown is complete. If you have a MicroVAX or if your system does not reboot from SYSF, halt the system and boot from the [SYSF] directory. For most MicroVAX and VAXstation computers, use the BOOT command in the following format and substitute the device name of the system disk for ddcu: >>> B/F0000000 ddcu If the system fails to boot, you can boot into SYSBOOT by entering the following: >>> B/F0000001 ddcu For more information on booting your computer from the SYSF directory, see the upgrade and installation supplement for your VAX computer. 7.4.15 STEP 11: VERIFY SYSTEM TIME When the system reboots, it displays a message similar to the following: OpenVMS VAX Version V7.1 Major version id = 1 Minor version id = 0 System time is: 22-NOV-1996 15:54:08.30 . . . 7-20 Upgrading the OpenVMS VAX Operating System Upgrading the OpenVMS VAX Operating System 7.4 Upgrade Phase 1 * Is that correct? (Y/N/?) ___________________________________________________________ If ... Then ... You want to redisplay the Type a question mark (?) and time press Return. The system time displayed by Type Yes and press Return. the procedure is correct The system time displayed by Type No and press Return. the procedure is incorrect The procedure prompts you to enter the correct date and time. ___________________________________________________________ 7.5 Upgrade Phase 2 At the beginning of Phase 2, the procedure displays a message similar to the following: Continuing with OpenVMS VAX V7.1 Upgrade Procedure. Upgrade Phase 2 22-NOV-1996 15:55:42.57 ********************************************************* %SYSTEM-W-TZGMT, your local timezone has defaulted to GMT %SYSTEM-I-SETTZ, to set your local timezone use: $ @SYS$MANAGER:UTC$TIME_SETUP.COM ********************************************************* On MIN or UPGRADE system startup - CLUE is not run. . . . 22-NOV-1996 15:57:00.59 You can ignore the time zone message. The UTC$TIME_ SETUP.COM procedure runs during the final phase of the upgrade procedure. Upgrading the OpenVMS VAX Operating System 7-21 Upgrading the OpenVMS VAX Operating System 7.5 Upgrade Phase 2 7.5.1 WHAT THE PROCEDURE DOES During Phase 2, the upgrade procedure restores the rest of the library (C), optional (D), Help Message (E), and OpenVMS Management Station software (F) save sets and DECwindows support files if you elected to install them. 7.5.2 MOUNTING ADDITIONAL TAPE CARTRIDGE AND 9-TRACK OPEN REEL MAGNETIC TAPE VOLUMES If your distribution kit is on TK50 tape cartidges or 9- track open reel magnetic tapes, you may be asked to mount additional volumes of the kit. In such a case, your system will display a message similar to the following: Please mount volume of the OpenVMS kit on where: is the volume number and is the cartridge tape drive or open reel tape drive. After you respond to the prompt, the system displays one of the following messages: o For a TK50 tape cartidge, the message is similar to the following: * Is the volume labeled OVMS VAX V7.1 BIN TK50 2/2 ready to be mounted? o For 9-track open reel tape, the message is similar to the following: * Is the volume labeled OVMS VAX V7.1 BIN MT9 n/4 ready to be mounted? where: n/4 may be 2/4, 3/4 or 4/4. To respond to either message, do the following: 1. Unload the volume currently in the drive. 2. Examine the remaining volumes and select the one with the label that matches the label specified in the prompt. 3. Load the volume and make the drive ready. 4. Answer YES to the question. For information on which save sets are located on which tape volumes, Section 1.4.1 and Section 1.4.2. 7-22 Upgrading the OpenVMS VAX Operating System Upgrading the OpenVMS VAX Operating System 7.6 Upgrade Phase 3 7.6 Upgrade Phase 3 At the beginning of Phase 3, the procedure displays a message similar to the following: Continuing with OpenVMS VAX V7.1 Upgrade Procedure Upgrade Phase 3 22-NOV-1996 16:45:18.35 7.6.1 WHAT THE PROCEDURE DOES During Phase 3, the upgrade procedure does the following: 1. Merges the OpenVMS VAX distributed files that are commonly edited by system managers with new OpenVMS VAX files. 2. Merges all the miscellaneous user files in the old system directories into a new set of system directories, temporarily called SYSF.SYSEXE, SYSF.SYSMGR, SYSF.SYSLIB, and so on. 3. Removes the directory entries for page, swap, dump, and authorization files from the old directory tree. 4. Deletes all the remaining accounting data files, operator logs, and all files in the SYSERR directory. 5. Merges the old and new versions of the following files: HELP, DCLTABLES, IMAGELIB.OLB, and STARLET.OLB. 6. Moves all remaining files from the old directory tree [VMS$COMMON] to the new directory tree. 7. Deletes the old directory tree [VMS$COMMON]. 7.7 Upgrade Phase 4 At the beginning of Phase 4, the procedure displays a message similar to the following: Continuing with OpenVMS VAX V7.1 Upgrade Procedure. Upgrade Phase 4 22-NOV-1996 17:14:34.12 Upgrading the OpenVMS VAX Operating System 7-23 Upgrading the OpenVMS VAX Operating System 7.7 Upgrade Phase 4 7.7.1 WHAT THE PROCEDURE DOES During Phase 4, the upgrade procedure does the following: 1. Corrects back pointers for system directories. 2. Shuts down the system. 3. Reboots the system, or requires that you manually reboot the system. 7.7.2 WHAT YOU DO If the procedure requires that you manually reboot the system from the original system root (usually SYS0), do the following: 1. If you are upgrading a VAX 8530, 8550, 8810, or 8820-N computer, do the following: a. Restore the original copies of DEFBOO and dddGEN to boot from the original root directory. b. In the preupgrade procedure (Chapter 5), you made copies of the boot command procedures, DEFBOO.SAV and dddGEN.SAV. To restore the original names to these files, enter the following commands and press the Return key after each one: >>> EXIT $ COPY DEFBOO.SAV DEFBOO.COM $ COPY dddGEN.SAV dddGEN.COM 2. For most MicroVAX and VAXstation computers, use the BOOT command in the following format and substitute the device name of the system disk for ddcu: >>> B ddcu If the system fails to boot, you can boot into SYSBOOT by entering the following: >>> B/1 ddcu For more information about booting your system, see the upgrade and installation supplement for your VAX computer. When the system reboots, the procedure displays a message similar to the following: OpenVMS VAX Version 7.1 Major version id = 1 Minor version id = 0 7-24 Upgrading the OpenVMS VAX Operating System Upgrading the OpenVMS VAX Operating System 7.7 Upgrade Phase 4 After the system reboots, the procedure continues with upgrade Phase 5. Do not move the system disk to a different drive. The system disk must remain in the same drive for the procedure to continue with Phase 5. 7.8 Upgrade Phase 5 At the beginning of Phase 5, the procedure displays a message similar to the following: Continuing with OpenVMS VAX V7.1 Upgrade Procedure. Upgrade Phase 5 22-NOV-1996 17:45:24.03 During Phase 5, the upgrade procedure does the following: 1. Deletes the temporary [SYSF] directory tree. 2. Cleans up files used only during the upgrade procedure. 3. Converts all VAXVMSSYS.PAR parameter files found in system roots to Version 7.1 format. 4. Displays messages listing tasks that you can perform after the upgrade procedure is completed. These tasks are described in Chapter 8. 7.9 Upgrade Phase 6 At the beginning of Phase 6, the procedure displays a message similar to the following: Continuing with OpenVMS VAX V7.1 Upgrade Procedure. Upgrade Phase 6 22-NOV-1996 17:45:25.03 Configuring all devices on the system... 7.9.1 RESTORING SYSTEM FILES The procedure restores SYS$SPECIFIC and SYS$COMMON versions of the following system files that were renamed with .COM_ OLD_SPECIFIC and .DAT_OLD_SPECIFIC extensions during Phase 1: SYSTARTUP_VMS.COM SYCONFIG.COM SYPAGSWPFILES.COM SYSECURITY.COM Upgrading the OpenVMS VAX Operating System 7-25 Upgrading the OpenVMS VAX Operating System 7.9 Upgrade Phase 6 SYSHUTDWN.COM SYLOGIN.COM LOGIN.COM SYLOGICALS.COM AGEN$NEW_SATELLITE_DEFAULTS.DAT AGEN$NEW_NODE_DEFAULTS.DAT LAT$SYSTARTUP.COM TFF$STARTUP.COM You might not have site-specific versions of all of these files. The procedure will display a message listing each file as it is restored. You might receive any of the following network messages, which can be ignored: %NCP-W-UNRCMP, Unrecognized component, Object Or: %NCP-I-SUCCESS, Success Object = X$X0 %NML-I-RECDELET, Database entry deleted 7.9.2 REGISTERING LICENSES The upgrade procedure also gives you the opportunity to register any additional licenses. The procedure 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? (Y/N): You do not have to reregister your OpenVMS VAX license or licenses for the following system integrated products: VAXclusters DECnet-Plus RMS Journaling Volume Shadowing If you want to register a new Product Authorization Key, type Yes and press the Return key. Otherwise, type No and press Return. 7-26 Upgrading the OpenVMS VAX Operating System Upgrading the OpenVMS VAX Operating System 7.9 Upgrade Phase 6 For more information on registering licenses, see the description of VMSLICENSE.COM in Appendix B and in the OpenVMS License Management Utility Manual. 7.9.3 UPDATING TIME ZONE INFORMATION At this point in the upgrade, the procedure checks for the presence of time zone and time differential factor (TDF) files on your system. If it does not find one or the other of these files, the procedure prompts you for information to be 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 those menus. The first menu is the main time zone menu. Select the time zone that best describes your location. If you do not select a time zone, the default is Greenwich Mean Time (GMT). Some time zone choices cause an additional menu to be displayed. This happens when the time zone you select has subcomponents. For example, if you choose the United States (US) time zone from the main menu, a second menu displays the specific time zones within the United States. You then select the menu item that best represents your local 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 for measuring time of day. You can choose from the following options: o Exit the time zone procedure without setting a TDF o Set a TDF o Display the TDF for your local time zone For more information about TDF and local time zone support, see the OpenVMS System Manager's Manual. Upgrading the OpenVMS VAX Operating System 7-27 Upgrading the OpenVMS VAX Operating System 7.9 Upgrade Phase 6 7.9.4 INSTALLING DECNET-PLUS Earlier in the procedure, you were asked whether you wanted to install the DECnet-Plus product. If you answered Yes, the procedure now installs it. Note that, if DECnet-Plus (formerly DECnet/OSI) is already installed on your system and if the installed version is the same as or higher than the version supplied with OpenVMS VAX Version 7.1, then DECnet-Plus is not reinstalled, and the procedure displays the following message: DECnet--Plus is already installed. If DECnet-Plus is not already installed on your system, the procedure displays a message similar to the following and prompts you for information it needs to install the DECnet- Plus product. In this example, the kit is being installed from an InfoServer device, DAD1. DECnet-Plus will now be installed. Media containing the DECnet-Plus kit must be available. If you are installing OpenVMS from an InfoServer (DAD1) or local CD-ROM, there is a DECnet-Plus kit on the CD-ROM. If you are installing from a cartridge tape (TK50) or from an open reel tape, you should have a DECnet-Plus kit on cartidge tape or open reel tape. An appropriate DECnet-Plus kit may also be available on the Consolidated Distribution CD-ROM, or you may have a separate DECnet-Plus kit. NOTE: You may choose any available media for the DECnet-Plus kit. It is NOT NECESSARY to use the same type of media that contained the OpenVMS kit. * Enter name of drive holding the DECnet-Plus kit: DAD1: * Enter the InfoServer service name: OTHER_PRODS * Enter the InfoServer work group number [0]: The following product has been selected: DEC VAXVMS DECNET_PLUS V7.1 *** DEC VAXVMS DECNET_PLUS V7.1: DECnet-Plus V7.1 N3_H for OpenVMS VAX Copyright (c) Digital Equipment Corporation 1996. All rights reserved. 7-28 Upgrading the OpenVMS VAX Operating System Upgrading the OpenVMS VAX Operating System 7.9 Upgrade Phase 6 Digital Equipment Corporation This product requires one of two PAKs: DVNETEND or DVNETRTG. Do you want all the default values for this product? [YES] Do you want to view the values? [NO] Execution phase starting ... The following product will be installed: DEC VAXVMS DECNET_PLUS V7.1 Portion done: 0%...10%...20%...30%...40%...80%...90%...100? The following product has been installed: DEC VAXVMS DECNET_PLUS V7.1 7.9.5 RUNNING AUTOGEN Next, the procedure displays the following message and runs AUTOGEN: Running AUTOGEN to compute the new SYSTEM parameters... If AUTOGEN encounters any problems, it displays the following message: %AUTOGEN-W-REPORT, Warnings were detected by AUTOGEN. Please review the information given in the file SYS$SYSTEM:AGEN$PARAMS.REPORT. If AUTOGEN displays this message, be sure to check AGEN$PARAMS.REPORT as one of your postupgrade tasks. This task is described in Section 8.4. 7.9.6 SHUTTING DOWN THE SYSTEM After AUTOGEN finishes, the procedure displays a sequence of shutdown messages that begins like this: 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 upgrade will be complete. SHUTDOWN -- Perform an Orderly System Shutdown . . . The system shuts down and will reboot automatically if your system is set up to do so. If the system does not reboot Upgrading the OpenVMS VAX Operating System 7-29 Upgrading the OpenVMS VAX Operating System 7.9 Upgrade Phase 6 automatically, reboot it manually. For more information on booting your system, see the upgrade and installation supplement for your VAX computer. 7.9.7 BOOTING VOTING NODES If you are upgrading a standalone system, go to the next step. If you are upgrading a VAXcluster system, the system might hang when you try to reboot the upgraded system disk. This is because the total cluster value is less than the cluster quorum value. To remedy this situation, boot voting members that run from the system disk you just upgraded. (For more information about quorum values and voting members, see OpenVMS Cluster Systems.) All nodes that are booted at this time will run AUTOGEN and reboot. 7.9.8 EXECUTING STARTUP After the system reboots, the procedure displays the following message: *********************************************************** OpenVMS VAX V7.1 You have SUCCESSFULLY installed the OpenVMS operating system. The system is now executing the STARTUP procedure. Please wait for the completion of STARTUP before logging in to the system. *********************************************************** Finally, the procedure displays informational messages as well as accounting information. For example: %STDRV-I-STARTUP, OpenVMS startup begun at 22-NOV-1996 18:27:30 . . . %SET-I-INTSET, login interactive limit=64, current interactive value = 0 SYSTEM job terminated at 22-NOV-1996 18:30:00.00 7-30 Upgrading the OpenVMS VAX Operating System Upgrading the OpenVMS VAX Operating System 7.9 Upgrade Phase 6 Accounting information: Buffered I/O count: 133 Peak working set size: 401 Direct I/O count: 12 Peak virtual size: 2379 Page faults: 325 Mounted volumes: 0 Charged CPU time 0 00:00:55.23 Elapsed time 0 00:01:31.24 At this point the OpenVMS VAX operating system is running. 7.9.9 LOGGING IN Press the Return key. The system asks for the user name and password. Log in to the SYSTEM account so that you can perform the postupgrade procedures described in Chapter 8. Welcome to OpenVMS VAX V7.1 Username: SYSTEM Password: . . . If you forget the password, follow the instructions for performing an emergency startup in the OpenVMS System Manager's Manual: Essentials. Proceed to Chapter 8 to perform the required postupgrade tasks. Upgrading the OpenVMS VAX Operating System 7-31 8 _________________________________________________________________ After Upgrading OpenVMS VAX After you upgrade the OpenVMS VAX operating system, you need to perform several important tasks before you can use the system. This chapter describes the following tasks in the order you perform them: o Verifying system time o Restoring the preferred node list o Replacing SYSUAF.DAT and VMS$AUDIT_SERVER.DAT o Examining AGEN$PARAMS.REPORT o Checking the size of system files o Examining your command procedures o Changing MODPARAMS.DAT o Updating your console media o Decompressing system libraries o Testing the system with UETP, the user environment test package o Increasing free space on your system disk o Purging system files o Restoring your modifications to the system password dictionary o Customizing DECwindows support software o Preparing to run the OpenVMS Management Station software o Installing layered products o Backing up the system disk o Running AUTOGEN After Upgrading OpenVMS VAX 8-1 After Upgrading OpenVMS VAX o Completing the postupgrade checklist If you are an experienced system manager, you can use the checklist at the end of this chapter to complete the necessary postupgrade tasks. If you are a less-experienced system manager, you should read the entire chapter and then use the checklist to make sure you have completed all the postupgrade tasks. 8.1 Verifying System Time During the upgrade, the procedure displayed the system time and gave you the opportunity to enter the correct time if the displayed time was incorrect. Now that you have upgraded your system, verify that the system time is correct by entering the following command: $ SHOW TIME The system displays the date and time. If the time displayed by your system is not correct, reset it by entering the command SET TIME using the following format: SET TIME=dd-mmm-yyyy:hh:mm:ss For example: $ SET TIME=22-NOV-1996:18:35:30 8.2 Restoring the Preferred Node List After the upgrade completes, the queuing system on the upgraded nodes is enabled, and you must restore the preferred node list for the queue manager. To restore the preferred node list, enter the following command from any node: START/QUEUE/MANAGER/ON=(node1, node2 . . . noden) For node1, node2, and so forth, supply the names of the nodes-separated by commas-that you want to restore to the preferred node list. 8-2 After Upgrading OpenVMS VAX After Upgrading OpenVMS VAX 8.3 Replacing SYSUAF.DAT and VMS$AUDIT_SERVER.DAT 8.3 Replacing SYSUAF.DAT and VMS$AUDIT_SERVER.DAT If you permanently store the SYSUAF.DAT and VMS$AUDIT_ SERVER.DAT files on the system disk, go to Section 8.4. If you do not permanently store SYSUAF.DAT and VMS$AUDIT_ SERVER.DAT on the system disk, you copied them to the system disk before you did the upgrade. During upgrade procedure, these files were updated. ________________________ Note ________________________ If you did a rolling upgrade, the shared version of SYSUAF.DAT was not updated. ______________________________________________________ To replace the updated files, copy the updated versions of SYSUAF.DAT and VMS$AUDIT_SERVER.DAT from the system disk to the directory where you usually keep them. 8.4 Examining AGEN$PARAMS.REPORT When AUTOGEN runs, it writes informational and, if necessary, warning messages to the file SYS$SYSTEM:AGEN$PARAMS.REPORT. You can view the contents of this report file to examine these messages. To display AGEN$PARAMS.REPORT on your screen, enter the following command and press the Return key: $ TYPE SYS$SYSTEM:AGEN$PARAMS.REPORT If the report includes a message similar to the following, you can modify the size of the PAGE, SWAP, or DUMP file: ****************** %AUTOGEN-W-DSKSPC, The disk on which DISK$OpenVMS071:[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 Section 8.5. After Upgrading OpenVMS VAX 8-3 After Upgrading OpenVMS VAX 8.5 Checking the Size of System Files 8.5 Checking the Size of System Files AUTOGEN sets the following files at sizes appropriate for your system: [SYSEXE]SYSDUMP.DMP [SYSEXE]PAGEFILE.SYS [SYSEXE]SWAPFILE.SYS For special workloads or configurations, you can specify different sizes for these files. Check the sizes of these files to be sure they meet your needs. Log in to the SYSTEM account and enter the following command: $ @SYS$UPDATE:SWAPFILES For more information, see the OpenVMS System Manager's Manual: Essentials. 8.6 Examining Your Command Procedures The upgrade procedure places a new version of WELCOME.TXT on your system disk. If your system uses a site-specific version of this file, you must modify the new version of the file with your changes. The upgrade procedure restores your site-specific version of the following files with *.COM_OLD_SPECIFIC extensions: SYSTARTUP_VMS.COM SYCONFIG.COM SYPAGSWPFILES.COM SYSECURITY.COM SYSHUTDWN.COM SYLOGIN.COM LOGIN.COM SYLOGICALS.COM LAT$SYSTARTUP.COM TFF$STARTUP.COM The upgrade procedure provides new templates for some of these files with the .TEMPLATE extension. The new templates can include features that are not in your site-specific files. Check the templates against your site-specific files and edit your files as necessary. 8-4 After Upgrading OpenVMS VAX After Upgrading OpenVMS VAX 8.6 Examining Your Command Procedures Remember, you do not need a START/QUEUE/MANAGER command in your startup file because the queue manager automatically starts up when you boot the system. 8.7 Changing MODPARAMS.DAT 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 new file, if necessary, for your system. If you are upgrading a VAXcluster, you must update the MODPARAMS.DAT file for each VAX computer that boots from the system disk. Make sure the EXPECTED_VOTES value is correct. The value is the sum of all VOTES in the cluster. For example, if there are five VAX computers in the cluster, and each has one VOTE, the value is five. As you reboot each VAX computer, AUTOGEN runs automatically. The cluster forms when you have booted enough computers to attain cluster quorum. For more information, refer to the OpenVMS System Manager's Manual: Tuning, Monitoring, and Complex Systems. 8.8 Updating Your Console Media If your computer does not use console media, skip this section and go to Section 8.10. If your computer uses console media, you must copy the Version 7.1 VMB.EXE onto your system's console media. The procedure for accomplishing this differs depending on the VAX series computer you have. Follow the instructions in the section that applies to your VAX computer. 8.9 VAX 8530, 8550, 8810 (8700), 8820-N (8800) Computers If you upgraded a VAX 8530, 8550, 8810 (8700), or 8820-N (8800) computer, do the following: 1. Place a blank RX50 diskette in one of the console diskette drives. The console refers to the upper (or left-hand) diskette drive as DZ1 while the OpenVMS VAX operating system refers to it as CSA1. The console refers to the lower (or right-hand) drive as DZ2 while the OpenVMS VAX operating system refers to it as CSA2. After Upgrading OpenVMS VAX 8-5 After Upgrading OpenVMS VAX 8.9 VAX 8530, 8550, 8810 (8700), 8820-N (8800) Computers 2. Make sure the diskette drives have been connected to the OpenVMS VAX operating system, as follows: $ SHOW DEVICE CSA Device Device Error Volume Name Status Count Label CSA0: (SYSTEM) Online 0 CSA1: (SYSTEM) Online 0 CSA2: (SYSTEM) Online 0 If the drives are not connected, the following message is displayed: %SYSTEM-W-NOSUCHDEV, no such device available If this message is displayed, enter the following commands (you need CMKRNL privilege): $ RUN SYS$SYSTEM:SYSGEN SYSGEN> CONNECT CONSOLE SYSGEN> EXIT 3. To initialize the diskette, enter a command in the following format: $ INITIALIZE/STRUCTURE=1 device-name: volume-label Substitute CSA1 or CSA2 for device-name. Substitute a 1- to 12-character name for volume-label. For example: $ INITIALIZE/STRUCTURE=1 CSA1: V61CONSOLE 4. Enter the following commands to mount the diskette, create the required directories, and copy the new VMB.EXE to the diskette. Substitute CSA1 or CSA2 for device-name. $ MOUNT/OVERRIDE=ID device-name: $ CREATE/DIRECTORY device-name:[TRANSFER] $ COPY SYS$SYSTEM:VMB.EXE device-name:[TRANSFER] 5. Once you have copied all the files, enter the following command to dismount the diskette. (Leave the diskette in the drive.) Substitute CSA1 or CSA2 for device-name. $ DISMOUNT device-name: 8-6 After Upgrading OpenVMS VAX After Upgrading OpenVMS VAX 8.9 VAX 8530, 8550, 8810 (8700), 8820-N (8800) Computers 6. To enter console mode, press Ctrl/P. To exit from the console program, enter the following command: >>> EXIT 7. Open the diskette drive door, pause for a moment, and close it. The red indicator light will flash. 8. To copy VMB.EXE from the diskette to the console fixed disk drive, enter the following command: $ COPY DZu:[TRANSFER]VMB.EXE LB0:[CONSOLE] Substitute DZ1 or DZ2 for DZu. The fixed drive in the console is known by two names, DW2 and LB0. Most console files are stored using the name LB0. If the system displays a message that describes a protection violation on the output device, copy the files using the device name DW2 rather than LB0. 9. When you have finished copying the files, remove the diskette from the drive. 10.Restart the console program by entering the following command and pressing Return: $ RUN CONTROL 11.Return to the operating system by entering the following command and pressing Return: >>> SET TERMINAL PROGRAM 8.9.1 VAX-11/730, 750, 780, 785 AND VAX 8200, 8250, 8300, 8350, 8600, 8650 COMPUTERS If you upgraded a VAX-11/730, 750, 780, 785 and VAX 8200, 8250, 8300, 8350, 8600, or 8650 computer, follow the instructions in this section. The procedure does the following: o Checks to see if you have enough space for the new VMB.EXE o Copies the new VMB.EXE to the console media o Updates the BOOT58 file for the VAX-11/750, 8200, 8250, 8300 and 8350 computers After Upgrading OpenVMS VAX 8-7 After Upgrading OpenVMS VAX 8.9 VAX 8530, 8550, 8810 (8700), 8820-N (8800) Computers To update the console media, use the following procedure: 1. Log in to the SYSTEM account. 2. Enter the following commands to check if there is enough space for the new VMB.EXE. You need 120 blocks. If you are updating a VAX-11/730 system, use CSA2 for device-name; if you are updating one of the other VAX computers, use CSA1 for device-name. $ RUN SYS$SYSTEM:SYSGEN SYSGEN> CONNECT CONSOLE SYSGEN> EXIT $ EXCHANGE DIRECTORY device-name:VMB.EXE Directory of RT-11 volume TINES$CSA1: 22-NOV-1996 18:40 VMB.EXE 80 22-NOV-1996 Total of 1 file, 80 blocks. Free space 43 blocks, largest 23. If the size of the current VMB, plus the free space, does not equal at least 120 blocks, delete unneeded files on the console until you have 120 blocks available. In the above example, the size of the current VMB.EXE (80 blocks) plus the free space (43 blocks) equals 123 blocks, so files do not have to be deleted. 3. Enter the following command and press the Return key: $ @SYS$UPDATE:UPDATE_CONSOLE.COM 4. If you are updating the console medium for a VAX 8600 or VAX 8650 computer, the new VMB.EXE is copied onto the console medium. If you are updating the console medium for one of the other VAX computers, the procedure uses the EXCHANGE procedure to copy the contents of the existing console medium, merge the new files onto the copy of the console medium, and create a new version of the console medium. When the computer is ready to create the new version, it displays a message asking you to insert a scratch tape cassette or diskette. Take out the original console medium and insert a new one. 8-8 After Upgrading OpenVMS VAX After Upgrading OpenVMS VAX 8.9 VAX 8530, 8550, 8810 (8700), 8820-N (8800) Computers 8.9.2 VAX 9000 COMPUTERS VAX 9000 computers use a special version of VMB.EXE named VMB9AQ.EXE. The upgrade procedure automatically copies a new version of this file to the console hard disk. However, if for some reason you need to update the console hard disk, use the UPDATE_CONSOLE.COM command procedure described for the VAX-11/730, 750, 780, 785 and VAX 8200, 8250, 8300, 8350, 8600, 8650 computers. The device name for the VAX 9000 console hard disk is CSA1. 8.10 Decompressing the System Libraries Decompressing the system libraries gives the system faster access to the libraries. You can decompress all the system libraries or just some of them. Table 8-1 gives the approximate number of blocks consumed by each library after decompression. Table_8-1_Sizes_of_Decompressed_System_Libraries___________ Library___________Blocks______Library___________Blocks_____ HELPLIB.HLB 9108 EDFHLP.HLB 102 STARLET.OLB 8442 TPUHELP.HLB 1038 VAXCCURSE.OLB 102 ACLEDT.HLB 102 VAXCRTL.OLB 477 INSTALHLP.HLB 102 VAXCRTLG.OLB 102 LATCP$HELP.HLB 240 DECCCURSE.OLB 102 MNRHELP.HLB 102 DECCRTL.OLB 183 PATCHHELP.HLB 102 DECCRTLG.OLB 102 PHONEHELP.HLB 102 ERFLIB.TLB 105 SDA.HLB 111 STARLETSD.TLB 4800 SHWCLHELP.HLB 150 MAILHELP.HLB 273 SYSGEN.HLB 393 EDTHELP.HLB 231 TECO.HLB 102 (continued on next page) After Upgrading OpenVMS VAX 8-9 After Upgrading OpenVMS VAX 8.10 Decompressing the System Libraries Table_8-1_(Cont.)_Sizes_of_Decompressed_System_Libraries___ Library___________Blocks______Library___________Blocks_____ DBG$UIHELP.HLB 408 UAFHELP.HLB 372 DBG$HELP.HLB 1986 EVE$HELP.HLB 1197 EXCHNGHLP.HLB 117 EVE$KEYHELP.HLB 147 NCPHELP.HLB 537 STARLET.MLB 2502 ANLRMSHLP.HLB 102 LIB.MLB 2229 DISKQUOTA.HLB 102 ---------------------------------------------------------- The additional amount of disk space required to decompress all system libraries is about 13,500 blocks. To find out how much disk space you have, enter the following command and press the Return key: $ SHOW DEVICE SYS$SYSDEVICE 8.10.1 HOW TO DECOMPRESS LIBRARIES You execute the LIBDECOMP.COM command procedure to decompress the system libraries. To run LIBDECOMP, log in to the SYSTEM account, enter the following command, and press Return: $ @SYS$UPDATE:LIBDECOMP.COM The following information is displayed: OpenVMS Library Decompression Utility 8-10 After Upgrading OpenVMS VAX After Upgrading OpenVMS VAX 8.10 Decompressing the System Libraries 1 HELPLIB.HLB 14 NCPHELP.HLB 27 PATCHHELP.HLB 2 STARLET.OLB 15 SDA.HLB 28 PHONEHELP.HLB 3 ACLEDT.HLB 16 SHWCLHELP.HLB 29 LIB.MLB 4 ANLRMSHLP.HLB 17 SYSGEN.HLB 30 STARLET.MLB 5 DBG$HELP.HLB 18 ANALAUDIT$HELP.HLB 31 STARLETSD.TLB 6 DBG$UIHELP.HLB 19 SYSMANHELP.HLB 32 ERFLIB.TLB 7 DISKQUOTA.HLB 20 TFF$TFUHELP.HLB 33 VAXCCURSE.OLB 8 EDFHLP.HLB 21 EXCHNGHLP.HLB 34 VAXCRTL.OLB 9 INSTALHLP.HLB 22 TPUHELP.HLB 35 VAXCRTLG.OLB 10 LATCP$HELP.HLB 23 EVE$HELP.HLB 36 IMAGELIB.OLB 11 MAILHELP.HLB 24 EVE$KEYHELP.HLB 37 DECCCURSE.OLB 12 MNRHELP.HLB 25 UAFHELP.HLB 38 DECCRTL.OLB 13 EDTHELP.HLB 26 TECO.HLB 39 DECCRTLG.OLB A ALL libraries to be decompressed E EXIT this procedure * Enter letter or number(s) of libraries to be decompressed (Separate multiple entries with a comma): 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. If you prefer, you can execute LIBDECOMP interactively or as a batch job. If you use either of these methods, you can decompress up to 8 libraries each time you execute LIBDECOMP by listing the names of the libraries you want to decompress as parameters on the command line. (You can decompress all the libraries by omitting the /PARAMETERS qualifier.) Be sure to separate the library names with commas and do not include the file extension. For example, to decompress the VAXCRTL.OLB, DISKQUOTA.HLB, and LIB.MLB libraries as a batch job, enter the following command: $ SUBMIT/NOTIFY/PARAMETERS=(VAXCRTL, DISKQUOTA, LIB)- _$ SYS$UPDATE:LIBDECOMP To decompress these same libraries interactively, enter the following command: $ @SYS$UPDATE:LIBDECOMP VAXCRTL DISKQUOTA LIB Note that, when you type the command for a batch job, you separate the library names with commas and enclose the list within parentheses. You do not use commas or parentheses on the interactive command line. After Upgrading OpenVMS VAX 8-11 After Upgrading OpenVMS VAX 8.11 Testing the System with UETP 8.11 Testing the System with UETP UETP, the user environment test package, is a software package that tests whether the OpenVMS VAX operating system is installed correctly. As part of the postupgrade procedure, you should run UETP to verify your upgrade. Note that UETP needs at least 1200 free blocks on the system disk and is available only if you installed the optional save set VMS071.D. If you did not install the optional save set, you can add the UETP files to your system using VMSTAILOR. For information about using VMSTAILOR, see Chapter 10. For complete information about UETP, see the OpenVMS System Manager's Manual: Tuning, Monitoring, and Complex Systems. 8.12 Increasing Free Space on the System Disk This section describes how to increase the amount of free space on your system disk. You can gain free space by removing optional OpenVMS VAX files that you do not need from the system disk or by purging old versions of some system files. 8.12.1 USING VMSTAILOR AND DECW$TAILOR To remove files you do not need from the system disk, use VMSTAILOR. For example, if you are not running DECnet for OpenVMS, you do not need the network support files. For complete information about using VMSTAILOR to remove files, see Chapter 10. If you are running DECwindows Motif, use DECW$TAILOR to add or remove DECwindows base support, workstation support, and fonts. ________________________ Note ________________________ Files installed on alternate devices cannot be tailored. ______________________________________________________ 8-12 After Upgrading OpenVMS VAX After Upgrading OpenVMS VAX 8.12 Increasing Free Space on the System Disk 8.12.2 PURGING SYSTEM FILES In most cases, you can purge the following OpenVMS system files to free space on your system disk. However, before you purge any of these files, read Appendix F to make sure you do not purge a file version you might want to keep. SYS$SYSTEM:SHUTDOWN.COM SYS$SYSTEM:STARTUP.COM SYS$LIBRARY:ENCRYPSHR.EXE SYS$LIBRARY:*RTL*.EXE SYS$LIBRARY:*SHR.EXE SYS$MANAGER:EDTINI.EDT SYS$MANAGER:DBLSTRTUP.COM SYS$MANAGER:*.TEMPLATE SYS$EXAMPLES:XADRIVER.MAR SYS$LIBRARY:CDDSHR.EXE SYS$LIBRARY:EPC$FACILITY.TLB SYS$MESSAGE:EPC$MSG.EXE SYS$STARTUP:VMS$LAYERED.DAT To purge a file, enter the PURGE command followed by the file specification. For example: $ PURGE SYS$SYSTEM:SHUTDOWN.COM 8.13 Restoring Your System Password Dictionary The OpenVMS VAX operating system screens potential passwords for acceptability. The DCL command SET PASSWORD takes the user's proposed password, converts it to lowercase (if necessary), and compares it to entries in a system dictionary. If the proposed password is found in the dictionary, it is rejected as a valid user password, and the user must suggest another. Many system managers modify the system password dictionary to include words of significance to their site. During the upgrade, the procedure replaces the existing system password dictionary with a new one. If you had modified the dictionary and want to restore your local additions, you must merge the file containing your additions with the new system file. After Upgrading OpenVMS VAX 8-13 After Upgrading OpenVMS VAX 8.13 Restoring Your System Password Dictionary To add your site-specific passwords to the new system password dictionary, enable SYSPRV and merge your local additions by entering the following commands, where LOCAL_ PASSWORD_DICTIONARY.DATA is the file that contains your additions: $ SET PROCESS/PRIVILEGE=SYSPRV $ CONVERT/MERGE/PAD LOCAL_PASSWORD_DICTIONARY.DATA - _$ SYS$LIBRARY:VMS$PASSWORD_DICTIONARY.DATA 8.14 Customizing DECwindows Support Software If you have installed DECwindows support software, there are several steps that you can take to customize the DECwindows environment. Depending on your configuration, DECwindows customization tasks include the following: o Customizing the server startup o Using the Transmission Control Protocol/Internet Protocol (TCP/IP) as a DECwindows transport o Using transports for DECwindows other than those supplied by Digital Go to Chapter 9 for complete instructions for customizing your DECwindows support software. After you complete the tasks described in Chapter 9, return to this chapter to continue with the remaining postupgrade tasks. 8.15 Preparing to Run the OpenVMS Management Station The OpenVMS Management Station client-server software provides OpenVMS system management capabilities through a client application on a personal computer (PC) running Microsoft Windows. When you upgraded your OpenVMS system, the OpenVMS Management Station server files were automatically installed on your OpenVMS system disk. However, to obtain complete support, you had to select the OpenVMS Management Station client software files during the OpenVMS upgrade procedure. Those files are required for creating the installation media that you use to install the client software on your PC. 8-14 After Upgrading OpenVMS VAX After Upgrading OpenVMS VAX 8.15 Preparing to Run the OpenVMS Management Station Appendix G provides complete instructions for preparing your OpenVMS system and your PC to run the OpenVMS Management Station software. ________________________ Note ________________________ If you did not select the optional OpenVMS Management Station client software files during the installation or upgrade, you must add these files to your OpenVMS system disk before you follow the instructions in Appendix G. Use the OpenVMS Version 7.1 distribution media and VMSTAILOR to add the OpenVMS Management Station files to your system. (For information about using VMSTAILOR, see Chapter 10.) ______________________________________________________ 8.16 Installing Layered Products Back up your system disk and then use either the VMSINSTAL command procedure or the POLYCENTER Software Installation utility to install layered products on your system. For additional information about installing layered products, see the OpenVMS System Manager's Manual. 8.16.1 TCP/IP SERVICES FOR OPENVMS If you installed the Digital TCP/IP Services for OpenVMS software during the installation or if you choose to install it now as a layered product, note that you must also install the mandatory security update kit included with this release. The Digital TCP/IP Kit and the mandatory Security Update Kit are available in the following directory on the OpenVMS VAX CD-ROM: [TCPIP_VAX_041] If you choose to install the Digital TCP/IP Services for OpenVMS software, you must install both kits. After Upgrading OpenVMS VAX 8-15 After Upgrading OpenVMS VAX 8.17 Backing Up the System Disk 8.17 Backing Up the System Disk Digital recommends that you protect your work by performing the following operations: o Use SYS$UPDATE:CONSCOPY.COM to back up the console media (if applicable). o Make a standalone BACKUP kit on removable media and on the system disk. If your console media is a TU58 tape cartridge or an RX01 diskette, use the standalone BACKUP copy you made before you began the upgrade. (See Section 5.5.2.) o Back up the system disk. For complete information about these operations, see the upgrade and installation supplement for your VAX computer. 8.18 Running AUTOGEN When you upgraded the OpenVMS VAX operating system, the procedure executed AUTOGEN to set the values of system parameters and the sizes of the page and swap files according to the system's workload. In many cases, AUTOGEN can improve system performance by using dynamic feedback information from the running system. As a postinstallation task, you should run AUTOGEN again using the feedback mechanism to make further adjustments to system parameters. When AUTOGEN runs after an upgrade, it uses the parameter values in SYS$SYSTEM:MODPARAMS.DAT. Note that hardcoded values in MODPARAMS.DAT affect AUTOGEN's calculations of the feedback parameters. For AUTOGEN to properly calculate minimum values, you should replace the hardcoded values in MODPARAMS.DAT with MIN_ values. The MIN_ prefix specifies the minimum value to which a parameter can be set by AUTOGEN. If you are not satisfied with the parameter settings calculated by AUTOGEN, you can modify the parameter values by editing MODPARAMS.DAT as explained in the OpenVMS System Manager's Manual: Tuning, Monitoring, and Complex Systems. 8-16 After Upgrading OpenVMS VAX After Upgrading OpenVMS VAX 8.18 Running AUTOGEN After you have upgraded the operating system, run AUTOGEN again using the following procedure: 1. After 24 hours of operation, run AUTOGEN in feedback mode and reboot the system. 2. Run AUTOGEN in this same way, again, two working days later. ________________________ Note ________________________ For the VAX 9000 computer, AUTOGEN's initial parameter calculations are conservative. To obtain parameter values that match your system workload, you can run AUTOGEN in feedback mode a number of times. For more information, see the upgrade and installation supplement for your VAX 9000 computer. ______________________________________________________ 3. 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. For information about using AUTOGEN, see the OpenVMS System Manager's Manual: Tuning, Monitoring, and Complex Systems. 8.19 Postupgrade Checklist Use the following checklist to make sure you perform all the necessary postupgrade tasks. < Verify the system time. (Described in Section 8.1.) < Restore the preferred node list for the queue manager. (Described in Section 8.2.) < Replace SYSUAF.DAT and VMS$AUDIT_SERVER.DAT. (Described in Section 8.3.) < Examine AUTOGEN output stored in the file AGEN$PARAMS.REPORT. (Described in Section 8.4.) < Examine the command procedure templates supplied with OpenVMS VAX Version 7.1. (Described in Section 8.6.) < Examine MODPARAMS.DAT? (Described in Section 8.7.) < Update your console media. (Described in Section 8.8.) After Upgrading OpenVMS VAX 8-17 After Upgrading OpenVMS VAX 8.19 Postupgrade Checklist < Decompress the system libraries using LIBDECOMP.COM. (Described in Section 8.10.) < Run UETP (the user environment test package) to test the system. (Described in OpenVMS System Manager's Manual: Tuning, Monitoring, and Complex Systems.) < Remove unwanted files and check the sizes of system files. (Described in Section 8.12.) < Restore your local additions to the system password dictionary. (Described in Section 8.13.) < Customize your DECwindows environment. (Described in Section 8.14.) < Build a standalone BACKUP kit. (Described in Section 8.17.) < Back up the console media. (Described in Section 8.17.) < Install layered products. < Back up the system disk. (Described in the upgrade and installation supplement for your computer.) < Run AUTOGEN and reboot the system after the first 24 hours of operation. (Described in Section 8.18.) 8-18 After Upgrading OpenVMS VAX 9 _________________________________________________________________ Customizing DECwindows Support Software 9.1 Overview This chapter describes how you can customize DECwindows support software. The DECwindows components provided on the OpenVMS VAX kit supply DECwindows base support and workstation support files only. If you have not installed either of these DECwindows components on your system, skip this chapter. Depending on your configuration, DECwindows customization tasks include the following: o Customizing the server startup o Using the Transmission Control Protocol/Internet Protocol (TCP/IP) as a DECwindows transport o Using transports with DECwindows other than those supplied by Digital Note that the OpenVMS VAX operating system no longer includes the VMS DECwindows product. To get full DECwindows support, you must also install the separate DECwindows Motif for OpenVMS VAX layered product, which supports both the Motif and XUI environments. 9.2 Customizing the Server Startup By default, the DECwindows server no longer logs successful connect/disconnect messages to the DECW$SERVER_#_ ERROR.LOG file. To enable these messages, define the symbol DECW$SERVER_CONNECT_LOG in the DECW$PRIVATE_SERVER_ SETUP.COM file to be "T" and restart the server. Note that abnormal or unsuccessful connect/disconnect messages are still logged by the server. Customizing DECwindows Support Software 9-1 Customizing DECwindows Support Software 9.2 Customizing the Server Startup 9.2.1 ASSUMPTIONS The startup command procedures automatically determine most of the configuration variables for the DECwindows display server. However, there are items that the command procedures cannot determine, so they make the following assumptions: o The startup procedures normally assume that you have a 75 dots/inch monitor (such as a VR260 or VR290). However, if you are installing on a VAXstation 4000, the startup procedures assume that you have a 100 dots /inch monitor. o If you have a GPX, SPX, or LCG workstation, the startup procedures assume that you have a color monitor. o The startup procedures normally assume that you have a North American keyboard layout (you have an LK201-AA or an LK201-LA keyboard). If you are installing on a VAXstation 4000, the startup procedures assume that you have an LK401-AA keyboard. o The startup procedures assume that the server will use only DECnet software and local transports. 9.2.2 HOW TO OVERRIDE INCORRECT ASSUMPTIONS If any of these assumptions is incorrect, you must override them as follows: 1. Make a copy of the file SYS$MANAGER:DECW$PRIVATE_SERVER_ SETUP.TEMPLATE and rename it to a .COM file type. The comments in this file show how to customize individual workstations by adding a section of DCL commands for each workstation. You can also add DCL commands to the common section of the server startup file. By doing this, you ensure that the customizations you make affect all workstations that use the server startup file. 2. If your screen supports 100 dots/inch, add the following line: $ DECW$SERVER_DENSITY == "100" Add this line to the section for each workstation that has a 100 dots/inch monitor, or add it to the common section for all workstations (if all the workstations have 100 dots/inch monitors). 9-2 Customizing DECwindows Support Software Customizing DECwindows Support Software 9.2 Customizing the Server Startup 3. If you have upgraded to a VAXstation 4000 but still have a 75 dots/inch monitor, add the following line: $ DECW$SERVER_DENSITY == "75" 4. The section for any workstation with color graphics and a monochrome screen should contain the following lines: $ DECW$COLOR == "FALSE" $ DECW$BITONAL == "FALSE" 5. To override the default keyboard layout, determine the correct name from the model number of your LK201 keyboard, as follows: a. Turn the keyboard upside down, and look for a label that specifies the model number. The model number should be in a format similar to LK201-xx. If the model number is listed as LK201 without any additional characters, the information you need is on another part of the label. Look for a number that has the following format: nn-nnnnn-xx. b. Use the xx part of this number to choose a keymap name from Table 9-1. The table is arranged based on the dialect that each keyboard is designed for. Choose the keymap ending in _DP for the data processing keyboard layout, or the keymap ending in _TW for the typewriter layout. Customizing DECwindows Support Software 9-3 Customizing DECwindows Support Software 9.2 Customizing the Server Startup Table_9-1_DECwindows_Keymap______________________________________ Dialect_________Model_______________DECwindows_Keymap_Name_______ Austrian LK201- AUSTRIAN_GERMAN_LK201LG_DP /German (AG,LG,BG,MG) AUSTRIAN_GERMAN_LK201LG_TW LK201-(NG,PG) AUSTRIAN_GERMAN_LK201NG_DP AUSTRIAN_GERMAN_LK201NG_TW LK401-(AG) AUSTRIAN_GERMAN_LK401AG_TW Belgian/French LK201- BELGIAN_FRENCH_LK201LP_DP (AP,LP,BP,MP) BELGIAN_FRENCH_LK201LP_TW Belgian/French LK401-(AP) BELGIAN_FRENCH_LK401AP_DP BELGIAN_FRENCH_LK401AP_TW British LK201- BRITISH_LK201LE_DP (AE,LE,BE,ME) BRITISH_LK201LE_TW British LK401-(AA,PA) BRITISH_LK401AA_DP BRITISH_LK401AA_TW Canadian LK201- CANADIAN_FRENCH_LK201LC_DP /French (AC,LC,BC,MC) CANADIAN_FRENCH_LK201LC_TW Canadian LK401- CANADIAN_FRENCH_LK401AC_DP /French (AC,LC,BC,MC) CANADIAN_FRENCH_LK401AC_TW Czech LK401-(BV) CZECH_LK401AV Danish LK201- DANISH_LK201LD_DP (AD,LD,BD,MD) DANISH_LK201LD_TW (continued on next page) 9-4 Customizing DECwindows Support Software Customizing DECwindows Support Software 9.2 Customizing the Server Startup Table_9-1_(Cont.)_DECwindows_Keymap______________________________ Dialect_________Model_______________DECwindows_Keymap_Name_______ LK201-(ED,RD,FD) DANISH_LK201RD_DP DANISH_LK201RD_TW Danish LK401- DANISH_LK401AD_DP (AD,LD,BD,MD) DANISH_LK401AD_TW Dutch LK201- DUTCH_LK201LH_DP (AH,LH,BH,MH) DUTCH_LK201LH_TW LK201-(NH,PH) DUTCH_LK201NH LK401-(NH,PH) DUTCH_LK401AH Finnish LK201- FINNISH_LK201LF_DP (AF,LF,BF,MF) FINNISH_LK201LF_TW LK201-(NX,PX) FINNISH_LK201NX_DP FINNISH_LK201NX_TW Finnish LK401- FINNISH_LK401AF_DP (AF,LF,BF,MF) FINNISH_LK401AF_TW Flemish LK201- FLEMISH_LK201LB_DP (AB,LB,BB,MB) FLEMISH_LK201LB_TW Flemish LK401- FLEMISH_LK401AB_DP (AB,LB,BB,MB) FLEMISH_LK401AB_TW Hungarian LK401-(BQ) HUNGARIAN_LK401_BQ (continued on next page) Customizing DECwindows Support Software 9-5 Customizing DECwindows Support Software 9.2 Customizing the Server Startup Table_9-1_(Cont.)_DECwindows_Keymap______________________________ Dialect_________Model_______________DECwindows_Keymap_Name_______ Icelandic LK201- ICELANDIC_LK201LU_DP (AU,LU,BU,MU) ICELANDIC_LK201LU_TW Italian LK201- ITALIAN_LK201LI_DP (AI,LI,BI,MI) ITALIAN_LK201LI_TW Italian LK401- ITALIAN_LK401AI_DP (AI,LI,BI,MI) ITALIAN_LK401AI_TW North American LK201- NORTH_AMERICAN_LK201LA (AA,LA,BA,MA) North American LK401- NORTH_AMERICAN_LK401AA (AA,LA,BA,MA) Norwegian LK201- NORWEGIAN_LK201LN_DP (AN,LN,BN,MN) NORWEGIAN_LK201LN_TW LK201-(EN,RN,FN) NORWEGIAN_LK201RN_DP NORWEGIAN_LK201RN_TW Norwegian LK401- NORWEGIAN_LK401AN_DP (AN,LN,BN,MN) NORWEGIAN_LK401AN_TW Polish LK401-(BP) POLISH_LK401_BP Portuguese LK201- PORTUGUESE_LK201LV (AV,LV,BV,MV) Portuguese LK401- PORTUGUESE_LK401AV (AV,LV,BV,MV) Russian LK401-(BT) RUSSIAN_LK401_BT (continued on next page) 9-6 Customizing DECwindows Support Software Customizing DECwindows Support Software 9.2 Customizing the Server Startup Table_9-1_(Cont.)_DECwindows_Keymap______________________________ Dialect_________Model_______________DECwindows_Keymap_Name_______ Slovakian LK401-(CZ) SLOVAK_LK401_CZ Spanish LK201- SPANISH_LK201LS_DP (AS,LS,BS,MS) SPANISH_LK201LS_TW Spanish LK401- SPANISH_LK401AS_DP (AS,LS,BS,MS) SPANISH_LK401AS_TW Swedish LK201- SWEDISH_LK201LM_DP (AM,LM,BM,MM) SWEDISH_LK201LM_TW LK201-(NM,PM) SWEDISH_LK201NM_DP SWEDISH_LK201NM_TW Swedish LK401- SWEDISH_LK401AM_DP (AM,LM,BM,MM) SWEDISH_LK401AM_TW Swiss/French LK201- SWISS_FRENCH_LK201LK_DP (AK,LK,BK,MK) SWISS_FRENCH_LK201LK_TW Swiss/French LK401- SWISS_FRENCH_LK401AK_DP (AK,LK,BK,MK) SWISS_FRENCH_LK401AK_TW Swiss/German LK201- SWISS_GERMAN_LK201LL_DP (AL,LL,BL,ML) SWISS_GERMAN_LK201LL_TW Swiss/German LK401- SWISS_GERMAN_LK401AL_DP (AL,LL,BL,ML) (continued on next page) Customizing DECwindows Support Software 9-7 Customizing DECwindows Support Software 9.2 Customizing the Server Startup Table_9-1_(Cont.)_DECwindows_Keymap______________________________ Dialect_________Model_______________DECwindows_Keymap_Name_______ SWISS_GERMAN_LK401AL_TW Combined US/UK LK201-(EE,RE,PE) UK_LK201RE US_LK201RE Combined US/UK LK401-(EE,RE,PE) UK_LK401AA US LK401AA -------------------------------------------------------------- c. After you choose a keymap name, modify the server startup file. For example, to change the keyboard layout to a Dutch typewriter layout, add the following line to the server startup file: $ DECW$DEFAULT_KEYBOARD_MAP == "DUTCH_LK201LH_TW" Add a line similar to this for each workstation that does not have a North American keyboard layout, or add it to the common section for all workstations (if all the workstations use the same keyboard layout). 6. To add support for the Transmission Control Protocol /Internet Protocol (TCP/IP) transport using the DEC TCP/IP Services for OpenVMS product, add the following line: $ DECW$SERVER_TRANSPORTS == "DECNET,LOCAL,TCPIP" Add this line to the section for each workstation that will be using TCP/IP, or add it to the common section for all workstations. To include support for other transports, add the last part of the transport image name to the list of transports. For example, suppose you want to add support for a customer-written transport that has the following image name: SYS$SHARE:DECW_TRANSPORT_FOO You would add the following line: $ DECW$SERVER_TRANSPORTS == "DECNET,LOCAL,FOO" 9-8 Customizing DECwindows Support Software Customizing DECwindows Support Software 9.2 Customizing the Server Startup 7. Reboot the workstations for which you customized the server startup. 8. Customize security as described in the Using DECwindows Motif for OpenVMS manual. After you start the server, a per-server logical name table is created on your system but is not added to the default logical name table search lists. 9.3 Using Digital TCP/IP Services for OpenVMS DECwindows contains support for the TCP/IP transport. This support requires Digital TCP/IP Services for OpenVMS, a Digital layered product. Before you can use the DECwindows TCP/IP transport interface, you must install Digital TCP/IP Services for OpenVMS. ________________________ Note ________________________ Other vendors' implementation of TCP/IP transports use different call interfaces. For this reason, DECwindows support for TCP/IP is compatible only with Digital TCP/IP Services for OpenVMS. ______________________________________________________ You can conserve memory and process slots by configuring Digital TCP/IP Services for OpenVMS software for the minimum DECwindows requirement to support the X protocol. DECwindows only requires that INET_ACP be running. DECwindows does not require that the NFS server, the FTPD server, or the remote terminal servers be running. For more information about TCP/IP concepts, see the Digital TCP/IP Services for OpenVMS: Management manual. For information on how to configure the TCP/IP software, see the Digital TCP/IP Services for OpenVMS: Installation and Basic Configuation manual. 9.4 Using Other Transports with DECwindows DECwindows supports DECnet-Plus, local, and TCP/IP transports. However, you can use other transports, such as new transports for layered products and transports from third-party vendors, with DECwindows by writing a DECwindows transport interface layer. Customizing DECwindows Support Software 9-9 Customizing DECwindows Support Software 9.4 Using Other Transports with DECwindows 9.4.1 WRITING A TRANSPORT INTERFACE For information about writing a transport interface, see the VMS DECwindows Transport Manual. The transport interface image's filename must have the following format where name is the unique transport name: DECW$TRANSPORT_name (for transports supplied by Digital) DECW_TRANSPORT_name (for customer-written transports) 9.4.2 INSTALLING THE TRANSPORT INTERFACE IMAGE Install the image as a protected image in the SYS$SHARE directory (as defined by an executive mode logical name). Digital recommends that you install the image by adding the following line to SYS$MANAGER:SYSTARTUP_VMS.COM: $ INSTALL CREATE SYS$SHARE:DECW_TRANSPORT_name/OPEN/SHARED- /HEADER_RESIDENT/PROTECTED You can also include this command in a startup file that SYSTARTUP_VMS calls. To use this transport with the DECwindows server, customize the server startup as described in Section 9.2. 9.5 Using the Example Transport DECwindows has an example transport interface based upon the Digital TCP/IP Services for OpenVMS layered product. It is similar to the DECwindows TCP/IP transport interface, except it includes its own source files and it uses a different port number (5000). You can run the example transport interface simultaneously with the TCP/IP transport interface. If you have installed Digital TCP/IP Services for OpenVMS software, you can install and use the example transport by doing the following: 1. Copy the example transport to the SYS$SHARE directory as follows: $ COPY DECW$EXAMPLES:DECW$TRANSPORT_EXAMPLE.EXE SYS$SHARE:/PROT=W:RE 2. Add the following line to SYS$MANAGER:SYSTARTUP_VMS.COM: $ INSTALL CREATE SYS$SHARE:DECW$TRANSPORT_EXAMPLE /OPEN /SHARED- /HEADER_RESIDENT /PROTECTED 9-10 Customizing DECwindows Support Software Customizing DECwindows Support Software 9.5 Using the Example Transport 3. Customize the private server startup as described in Section 9.2 for TCP/IP, except use the transport name "EXAMPLE". For example, you could add the following line: $ DECW$SERVER_TRANSPORTS == "DECNET,LOCAL,TCPIP,EXAMPLE" 4. Reboot the workstation, or restart DECwindows. 5. Customize TCP/IP security as described in the Using DECwindows Motif for OpenVMS manual, but use the transport name "EXAMPLE" instead of "TCPIP". 6. Create a DECterm window on the workstation and enter the following command: $ SET DISPLAY /CREATE /NODE=your_node /TRANSPORT=EXAMPLE Substitute the node name of your workstation for your_ node. Remember that the same transport must be running on both the client and server. It is not necessary, however, for the client and the server to be on the same system. 7. Run any DECwindows application from the DECterm window. It will now use the example transport to display graphics on your workstation screen. For example, you would enter the following command to run the clock: $ RUN SYS$SYSTEM:DECW$CLOCK Customizing DECwindows Support Software 9-11 10 _________________________________________________________________ Using VMSTAILOR and DECW$TAILOR This chapter describes how to add or remove optional OpenVMS VAX files and DECwindows support files from your system disk using VMSTAILOR and DECW$TAILOR. You will need your OpenVMS VAX software media kit to tailor on files. Any site-specific customization that has been done to a class will be lost when that class is tailored off. 10.1 Using VMSTAILOR To add or remove unwanted OpenVMS VAX files from the system disk, use VMSTAILOR. For example, if you are not running DECnet for OpenVMS, and you do not need the network support files, you can remove those files using VMSTAILOR. If you later decide you want to run DECnet for OpenVMS, you can add the necessary files at any time using VMSTAILOR and your OpenVMS VAX distribution media. (Note that you cannot tailor files on or off an alternate device.) 10.1.1 HOW VMSTAILOR WORKS VMSTAILOR has three phases: 1. VMSTAILOR asks if you want to tailor your system by adding files (tailor on) or by deleting files (tailor off). 2. If you choose to tailor files on, VMSTAILOR lists each class of OpenVMS VAX files and asks if you want to include them on the system disk. If you choose to tailor files off, VMSTAILOR lists each class of files and asks if you want to delete them from the system disk. 3. VMSTAILOR adds or deletes the files you indicated from the system disk. If you are tailoring files on, you must load your OpenVMS VAX distribution media in a drive available to the system. If your distribution media Using VMSTAILOR and DECW$TAILOR 10-1 Using VMSTAILOR and DECW$TAILOR 10.1 Using VMSTAILOR consists of more than one piece, put the first piece of the media into the drive. The following is a list of classes and subclasses of OpenVMS VAX files that can be added or deleted by using VMSTAILOR. For a complete list of OpenVMS VAX files and their functions, see the OpenVMS System Manager's Manual: Tuning, Monitoring, and Complex Systems. o Network Support Incoming Remote File Access files Incoming Remote Terminal files Network Test files Remote Task Loading o Programming Support Debugger utility (DEBUG) Image Dump utility (ANALYZE/PROCESS_DUMP) RMS Analyze and FDL Editor utilities (ANALYZE/RMS, ANALYZE/FDL) Message utility (MESSAGE) Object and Shareable Image libraries MACRO libraries MACRO assembler SDL intermediary form of STARLET.MLB Fortran required files VAX C object libraries o OpenVMS RMS Journaling Files o System Programming Support Files-11 ODS-1,ISO 9660, High Sierra ACPs Monitor utility Delta/XDelta debugger System Dump Analyzer utility (ANALYZE/SYSTEM, ANALYZE /CRASH) System Symbol Table file (SYS.STB) Miscellaneous Symbol Table files o Secure User's Environment File Access Control List utilities Print and Batch Queue utilities Input Queue Symbiont (Card Reader) Accounting Log Report Generator utility 10-2 Using VMSTAILOR and DECW$TAILOR Using VMSTAILOR and DECW$TAILOR 10.1 Using VMSTAILOR DECdtm o Utilities Mail utility DUMP utility RUNOFF utility Phone utility OpenVMS Help library OpenVMS System Messages Help Library Foreign Terminal Support LAT-11 terminal server (via Ethernet) Standalone BACKUP Error Log Report Generator utility (ANALYZE/ERROR) DECTPU utility Terminal Fallback facility TECO editor EDT documentation National Character Set utility (NCS) o VMS Workstation Support (VWS) Workstation device support o BLISS require files o Miscellaneous Files System map LPA-11 support o User Environment Test Package o Example Files 10.1.2 REMOVING OPENVMS VAX FILES To remove unwanted files using VMSTAILOR, perform the following steps: 1. Log in to the SYSTEM account. 2. Enter the following command and press the Return key: $ RUN SYS$UPDATE:VMSTAILOR VMSTAILOR displays a description of the VMSTAILOR program and displays the following message: Do you want to tailor files "ON" or "OFF"? Using VMSTAILOR and DECW$TAILOR 10-3 Using VMSTAILOR and DECW$TAILOR 10.1 Using VMSTAILOR 3. Enter OFF to remove unwanted files and press the Return key. The VMSTAILOR program lists each group, or class, of files and its size in blocks. Files are grouped according to their function. For example, all the files required for network support are in one class. A file class is made up of many smaller groups called subclasses. You can eliminate an entire class of files, or you can eliminate one or more of its subclasses. For example: CLASS - Network support Size of entire class (with subclasses): 1499 Size of common files required for any subclass: 1249 Do you wish to select the entire class (default = NO)? . . . 4. Decide which file classes or subclasses you do not need to support your system. The VMSTAILOR program displays step-by-step instructions. Follow these instructions to specify which classes or subclasses of files you want to remove. 5. VMSTAILOR deletes the files you selected and displays the names of those files. After it finishes, AUTOGEN runs automatically to make the adjustments that are necessary after system files are deleted. AUTOGEN also reboots the system. _______________________ Caution _______________________ To cancel VMSTAILOR during the first and second phases, press Ctrl/C, Ctrl/Y, or Ctrl/Z. Canceling VMSTAILOR during the third phase can cause a partially tailored disk. For a description of each phase, see Section 10.1.1. ______________________________________________________ 10-4 Using VMSTAILOR and DECW$TAILOR Using VMSTAILOR and DECW$TAILOR 10.1 Using VMSTAILOR 10.1.3 ADDING OPENVMS VAX FILES To add optional OpenVMS VAX files that you previously removed, or that you chose not to install during the OpenVMS VAX installation procedure, do the following: 1. Log in to the SYSTEM account. 2. Load your distribution media in a drive available to the system. For example, if your distribution media is on a TK50 tape cartridge, load the first tape cartridge in a TK50 drive that is available to the system. Make sure the drive is on line and ready. If you are adding files from a compact disc on an InfoServer, first determine whether the SYSGEN parameter SCSNODE is defined on your system (see Section 5.6) or start the DECnet software, and then refer to step 2 of Section 7.3. 3. Enter the following command and press the Return key: $ RUN SYS$UPDATE:VMSTAILOR VMSTAILOR displays a description of the VMSTAILOR program and displays the following message: Do you want to tailor files "ON" or "OFF"? 4. Enter ON to add files and press the Return key. The VMSTAILOR program lists each group, or class, of files and its size in blocks. Files are grouped according to their function. For example, all the files required for network support are in one class. A file class is made up of many smaller groups called subclasses. You can add an entire class of files, or you can add one or more of its subclasses. For example: CLASS - Network support Size of entire class (with subclasses): 1499 Size of common files required for any subclass: 1249 Do you wish to select the entire class (default = NO)? . . . Using VMSTAILOR and DECW$TAILOR 10-5 Using VMSTAILOR and DECW$TAILOR 10.1 Using VMSTAILOR 5. Decide which file classes or subclasses you need to add. VMSTAILOR displays step-by-step instructions. Follow these instructions to specify which classes or subclasses of files you want to add. 6. VMSTAILOR adds the files you specified and displays the names of the files. After the files have been added, AUTOGEN runs automatically to make the adjustments that are necessary after system files are added. AUTOGEN also reboots the system. _______________________ Caution _______________________ To cancel VMSTAILOR during the first and second phases, press Ctrl/C, Ctrl/Y, or Ctrl/Z. Canceling VMSTAILOR during the third phase can cause a partially tailored disk. For a description of each phase, see Section 10.1.1. ______________________________________________________ After adding files to the system disk, apply any updates that affect them. OpenVMS VAX update procedures create a .TXT file that contains a description of patched files. This file usually has the following format: SYS$UPDATE:VMSUn06n.TXT. For example, suppose you do not need the OpenVMS Phone utility (PHONE) and you run VMSTAILOR to remove those files. Later, you decide you want to use Phone. Run VMSTAILOR to return the Phone files to the system disk; then, apply any OpenVMS VAX update that has occurred since Version 7.1 that affected the Phone utility. 10.1.4 SAMPLE SESSION Example 10-1 shows how to add all Network Support files and selected Programming Support files to a system disk. Example 10-1 Sample VMSTAILOR Session (continued on next page) 10-6 Using VMSTAILOR and DECW$TAILOR Using VMSTAILOR and DECW$TAILOR 10.1 Using VMSTAILOR Example 10-1 (Cont.) Sample VMSTAILOR Session $ RUN SYS$UPDATE:VMSTAILOR . . . Do you want to tailor files "ON" or "OFF"? ON TAILOR-ON --------- You will now be prompted with a list of the classes and subclasses of OpenVMS VAX files that are optional. The size of each class and subclass is included in the list. This will help you decide whether or not you want to add a class or subclass to your system. Under some classes, there is a set of common files that is required in order for any subclasses to work. These files are added when you ask for either the entire class or any of its subclasses. Total size of the system disk is 2376153 blocks. Total space used on the system disk is 2241252 blocks. Total space left on the system disk is 134901 blocks. CLASS - Network support Size of entire class (with subclasses): 1499 Size of common files required for any subclass: 1249 Do you wish to select the entire class (default = NO)? YES (continued on next page) Using VMSTAILOR and DECW$TAILOR 10-7 Using VMSTAILOR and DECW$TAILOR 10.1 Using VMSTAILOR Example 10-1 (Cont.) Sample VMSTAILOR Session CLASS - Programming Support Size of entire class (with subclasses): 14706 Size of common files required for any subclass: 0 Do you wish to select the entire class (default = NO)? Do you wish to select any of its subclasses (default = NO)? )YES Select the subclasses that you wish to provide: SUBCLASS - Debugger utility (DEBUG) (4690 blocks) [NO]: YES SUBCLASS - Image Dump utility (ANALYZE/PROCESS_DUMP) (48 blocks) [NO]: YES SUBCLASS - RMS Analyze and FDL Editor utilities (ANALYZE/RMS, ANALYZE/FDL)- (374 blocks) [NO]:YES SUBCLASS - Message utility (MESSAGE) (49 blocks) [NO]: SUBCLASS - Object and Shareable Image libraries (4311 blocks) [NO]: YES SUBCLASS - Macro libraries (2293 blocks) [NO]: SUBCLASS - Macro assembler (457 blocks) [NO]: SUBCLASS - SDL intermediary form of STARLET.MLB (1957 blocks) [NO]: SUBCLASS - FORTRAN require files (51 blocks) [NO]: SUBCLASS - VAX-C object libraries (471 blocks) [NO]: CLASS - RMS journaling files Size of entire class (with subclasses): 155 No subclasses in this tailor class. Do you wish to select the entire class (default = NO)? CLASS - System programming Support Size of entire class (with subclasses): 2286 Size of common files required for any subclass: 93 Do you wish to select the entire class (default = NO)? Do you wish to select any of its subclasses (default = NO)? (continued on next page) 10-8 Using VMSTAILOR and DECW$TAILOR Using VMSTAILOR and DECW$TAILOR 10.1 Using VMSTAILOR Example 10-1 (Cont.) Sample VMSTAILOR Session CLASS - Secure User's Environment Size of entire class (with subclasses): 919 Size of common files required for any subclass: 0 Do you wish to select the entire class (default = NO)? Do you wish to select any of its subclasses (default = NO)? . . . Files have been selected Do you wish to add all of the options selected? YES Creating temporary command file, please wait... * Enter device containing OpenVMS distribution media: mua0: . . . 10.2 Using DECW$TAILOR You can use DECW$TAILOR to add or remove some or all DECwindows X11 display server, base support, and fonts files from the system disk. For example, if you are not planning to use the DECwindows PEX (PHIGS Extensions to X) support, you can remove those files. Later, if you decide you want DECwindows programming support, you can add the files to the system disk using DECW$TAILOR and your DECwindows distribution media. You cannot tailor files on or off an alternate device. ________________________ Note ________________________ To add or remove VMS DECwindows Motif files, refer to the DECwindows Motif Version 1.2-3 for OpenVMS Installation Guide. DECW$TAILOR will only tailor on or off those DECwindows display server, base support, and font files, with the exception of the required files, supplied on the OpenVMS VAX kit. ______________________________________________________ Using VMSTAILOR and DECW$TAILOR 10-9 Using VMSTAILOR and DECW$TAILOR 10.2 Using DECW$TAILOR 10.2.1 HOW DECW$TAILOR WORKS DECW$TAILOR has three phases: o DECW$TAILOR asks if you want to tailor your system by adding files (tailor on) or by deleting files (tailor off). o If you choose to tailor files on, DECW$TAILOR lists each class of DECwindows files and asks if you want to include them on the system disk. If you choose to tailor files off, DECW$TAILOR lists each class of DECwindows files and asks if you want to delete them from the system disk. o DECW$TAILOR adds or deletes the files you indicated from the system disk. If you are tailoring files on, you must load your DECwindows distribution media in a drive that is available to the system. For example, if your OpenVMS VAX distribution kit is on a TK50 tape cartridge, load the second tape cartridge, which contains the DECwindows support files, into a TK50 drive that is available to the system. 10.2.2 DECWINDOWS FILES YOU CAN TAILOR The following is a list of classes and subclasses of DECwindows files that you can add or delete using DECW$TAILOR. For a list of DECwindows files and their functions, see Appendix E. o DECwindows base support files-If you plan to install the separate DECwindows Motif for OpenVMS VAX layered product, you must add the base support files. o DECwindows workstation support files-If you are installing DECwindows support on a workstation or in a cluster that includes workstations or if you intend to install the DECwindows Motif for OpenVMS VAX layered product, you need the workstation support files. Otherwise, you do not need them. ________________________ Note ________________________ If you tailor device support files ON or OFF, the system reboots. ______________________________________________________ 10-10 Using VMSTAILOR and DECW$TAILOR Using VMSTAILOR and DECW$TAILOR 10.2 Using DECW$TAILOR o 100 dots/inch video font files-By default, some workstation monitors (for example, a VR150, VR160, or VR295) display 100 dots/inch, which gives you a more readable display when you run DECwindows applications. If your workstation monitor cannot display 100 dots/inch fonts (for example, a VR260 or VR290), you can save disk space by not selecting this option. For more information about the capabilities of your particular monitor, see the owner's guide for your monitor. o 75 dots/inch video font files-If your workstation monitor cannot display 75 dots/inch, you can save disk space by not selecting this option. For more information about the capabilities of your particular monitor, see the owner's guide for your monitor. 10.2.3 REMOVING DECWINDOWS FILES To remove DECwindows files from the system disk, do the following: 1. Log in to the SYSTEM account. 2. Type the following command, and press Return: $ RUN SYS$UPDATE:DECW$TAILOR DECW$TAILOR displays information about the DECW$TAILOR program and displays the following message: Do you want to tailor files "ON" or "OFF"? 3. Type OFF to remove unwanted files, and press Return. The DECW$TAILOR program lists each group, or class, of files and its size in blocks. Files are grouped according to their function. For example, all the files required for DECwindows device support are in one class. A file class is made up of many small subclasses. You can eliminate an entire class of files, or you can eliminate one or more of its subclasses. For example: Using VMSTAILOR and DECW$TAILOR 10-11 Using VMSTAILOR and DECW$TAILOR 10.2 Using DECW$TAILOR CLASS - DECwindows workstation support files Size of entire class (with subclasses): 14301 Size of common files required for any subclass: 8937 Do you wish to select the entire class (default = NO)? . . . 4. Decide which file classes or subclasses you need to add. DECW$TAILOR displays step-by-step instructions. Follow these instructions to specify which of the classes or subclasses you want to remove. 5. DECW$TAILOR deletes the files you selected and displays the names of those files. If you deleted device support files, the system automatically shuts down and reboots. _______________________ Caution _______________________ To cancel DECW$TAILOR during the first and second phases, press Ctrl/C, Ctrl/Y, or Ctrl/Z. Canceling DECW$TAILOR during the third phase can cause a partially tailored disk. For a description of each phase, see Section 10.2.1. ______________________________________________________ 10.2.4 ADDING DECWINDOWS FILES To install DECwindows device support and font files after the OpenVMS VAX installation or to add optional DECwindows files that you previously chose not to install or that you removed, do the following: 1. Log in to the SYSTEM account. 2. Load the OpenVMS VAX distribution media containing the DECwindows save sets in a drive available to your system. For example, if your distribution media is a TK50 tape cartridge, load the second tape cartridge into a TK50 drive that is available to the system. Make sure the drive is on line and ready. 10-12 Using VMSTAILOR and DECW$TAILOR Using VMSTAILOR and DECW$TAILOR 10.2 Using DECW$TAILOR If you are adding files from a compact disc on an InfoServer, first determine whether the SYSGEN parameter SCSNODE is defined on your system (see Section 5.6) or start the DECnet software, and then refer to step 2 of Section 7.3 in Chapter 7. 3. Enter the following command, and press Return: $ RUN SYS$UPDATE:DECW$TAILOR DECW$TAILOR displays information about the DECW$TAILOR program, and displays the following message: Do you want to tailor files "ON" or "OFF"? 4. Type ON to add files, and press Return. The DECW$TAILOR program lists each group, or class, of files and its size in blocks. Files are grouped according to their function. For example, all the files required for DECwindows device support are in one class. A file class is made up of many small subclasses. You can add an entire class of files, or you can add one or more of its subclasses. For example: CLASS - DECwindows workstation support files Size of entire class (with subclasses): 14301 Size of common files required for any subclasses: 8937 Do you wish to select the entire class (default = NO)? . . . 5. Decide which file classes or subclasses you do not need to support your system. The DECW$TAILOR program displays step-by-step instructions. Follow these instructions to specify which of the classes or subclasses you want to add. 6. DECW$TAILOR installs the files you selected and displays the names of those files. If you added device support files, the system automatically shuts down and reboots. _______________________ Caution _______________________ To cancel DECW$TAILOR during the first and second phases, press Ctrl/C, Ctrl/Y, or Ctrl/Z. Canceling DECW$TAILOR during the third phase can cause a Using VMSTAILOR and DECW$TAILOR 10-13 Using VMSTAILOR and DECW$TAILOR 10.2 Using DECW$TAILOR partially tailored disk. For a description of each phase, see Section 10.2.1. ______________________________________________________ After adding files to the system disk, apply any updates that affect them. For example, suppose you delete the Version 7.1 DECwindows 100 dots/inch video font files. Later on, you are able to use the 100 dots/inch fonts, so you run DECW$TAILOR to return the files to the system disk. You must then apply any OpenVMS VAX update that has occurred since Version 7.1 that affected the 100 dots/inch video font files. OpenVMS VAX update procedures create a .TXT file that contains a description of modified files. This file is usually named with the following format: SYS$UPDATE:VMSUn05n.TXT[1]. 10.2.5 SAMPLE SESSION Example 10-2 illustrates how to add the files for DECwindows 100 dots/inch font files. Example 10-2 Sample DECW$TAILOR Session $ RUN SYS$UPDATE:DECW$TAILOR . . . Do you want to tailor files "ON" or "OFF"? ON TAILOR-ON --------- You will now be prompted with a list of the classes and subclasses of DECwindows files that are optional. The size of each class and subclass is included in the list. This will help you decide whether or not you want to add a class or subclass to your system. Under some classes, there is a set of common files that is required in order for any subclasses to work. These files are added when you ask for either the entire class or any of its subclasses. (continued on next page) ____________________ [1] Examine this file to determine if the update patched the 100 dots/inch font files 10-14 Using VMSTAILOR and DECW$TAILOR Using VMSTAILOR and DECW$TAILOR 10.2 Using DECW$TAILOR Example 10-2 (Cont.) Sample DECW$TAILOR Session Total size of the system disk is 2376153 blocks. Total space used on the system disk is 1728072 blocks. Total space left on the system disk is 648081 blocks. CLASS - DECwindows base support files Size of entire class (with subclasses): 3363 No subclasses in this tailor class. Do you wish to select the entire class (default = NO)? CLASS - DECwindows workstation support files Size of entire class (with subclasses): 12376 Size of common files required for any subclass: 8916 Do you wish to select the entire class (default = NO)? NO Do you wish to select any of its subclasses (default = NO)? CLASS - 75 dots per inch video font files Size of entire class (with subclasses): 4537 No subclasses in this tailor class. Do you wish to select the entire class (default = NO)? CLASS - 100 dots per inch video font files Size of entire class (with subclasses): 3693 No subclasses in this tailor class. Do you wish to select the entire class (default = NO)? YES Files have been selected Do you wish to add all of the options selected? YES Creating temporary command file, please wait... * Enter device containing DECwindows distribution media: MUA0: . . . Using VMSTAILOR and DECW$TAILOR 10-15 A _________________________________________________________________ Multiversion VAX Upgrade Process This appendix provides you with an express method and easy to follow set of directions to apply multiple OpenVMS VAX version upgrades to your current system. ________________________ Note ________________________ By following these directions, the time that you spend on upgrading your VAX computer from Version 5.5-2 to Version 7.1 can be significantly reduced. ______________________________________________________ A.1 Determine Your Path Your first step is to determine which upgrade path you need to perform Table A-1 lists the recommended upgrade paths to reach OpenVMS VAX Version 7.1. Table_A-1_OpenVMS_VAX_Upgrade_Version_Matrix_______________ Intermediate Current_Version__Version(s)_______Final_Version____________ 5.5-2 6.1 7.1 6.0 6.1 or 6.2 7.1 6.1 [1] 7.1 6.2 [1] 7.1 7.0 [1] 7.1 [1]No intermediate version_needed. ___________________________________________________________ Multiversion VAX Upgrade Process A-1 Multiversion VAX Upgrade Process A.2 Multiversion Upgrade Procedure A.2 Multiversion Upgrade Procedure This procedure refers to an intermediate upgrade and final upgrade. An intermediate upgrade is defined as a version of the operating system that you need to install to reach your final version. . The final upgrade is the version of the operating system that you want to be running on your system at the end of this process. ______________________ Important ______________________ You should not plan to stay at the intermediate version. If you do need to upgrade to and run the intermediate version, please use the normal upgrade procedure located in the specific version installation manual. ______________________________________________________ A.2.1 BEFORE YOU BEGIN THE UPGRADE Before you begin the multiversion upgrade, you need to perform the following steps: 1. Locate the OpenVMS VAX software kits for the versions that you need. 2. Review the layered products on your system to determine the minimum supported version of each layered product to be installed on your final operating system version. o Determine which layered products you want to run on your system. See the web page at the following URL: http://www.service.digital.com/openvms o For information about specific layered products, see Section A.3. A-2 Multiversion VAX Upgrade Process Multiversion VAX Upgrade Process A.2 Multiversion Upgrade Procedure A.2.2 INTERMEDIATE UPGRADE Follow these steps to perform an intermediate upgrade of your OpenVMS VAX operating system. 1. Review your mixed-cluster version environment. Digital recommends that you upgrade all of your systems to the same version prior to performing a multiversion upgrade. 2. Review the firmware running on your system. For information about specific layered products, see Section A.3. 3. Review the version-specific documentation. Digital recommends that you read the New Features, Release Notes, Installation Guide manuals and Software Product Description available in your software kit. 4. Review the preupgrade checklist located in the Installation Guide. 5. Perform the upgrade. ______________________ Important ______________________ For the intermediate upgrade, install only the base operating system. Do not install any options. By installing only the base operating system, the time that you spend on upgrading your VAX computer during this intermediate upgrade can be reduced by 40 percent. ______________________________________________________ 6. Perform the postupgrade checklist located in the Installation Guide. 7. If you are performing multiple intermediate upgrades, repeat steps 3-7 as necessary. 8. You have completed the intermediate phase of the multiversion upgrade procedure. Proceed to Section A.2.3 to apply the final upgrade phase of this procedure . Multiversion VAX Upgrade Process A-3 Multiversion VAX Upgrade Process A.2 Multiversion Upgrade Procedure A.2.3 FINAL UPGRADE Follow these steps to perform the final upgrade of your OpenVMS VAX operating system. 1. Review the version-specific documentation. Digital recommends that you read the New Features, Release Notes, Installation Guide manuals and Software Product Description available in your software kit. 2. Perform the preupgrade checklist located in the Installation Guide. 3. Perform the complete upgrade and select the optional files that you need for your final version. 4. Perform the postupgrade checklist located in the Installation Guide. 5. Upgrade the layered products on your system based on your review of layered products in Section A.2.1. See the web page at the following URL: http://www.service.digital.com/openvms A.3 Specific Layered Product and Firmware Information This section provides specific information about the following layered products and firmware: o BASEstar o Debugger A.3.1 LAYERED PRODUCTS This section contains information about layered products. BASEstar Classic Domain A BASEstar Classic domain that consists of BASEstar Classic for OpenVMS VAX Versions 3.2 and 3.3 is fully supported on OpenVMS Version 7.1, as long as you have obtained the kits through normal support channels. However, on Alpha systems you need to be running BASEstar Classic Version 3.4. This means that any BASEstar Classic domain consisting of both VAX and Alpha systems can only have the VAX systems upgraded to OpenVMS Version 7.1 at this time. A-4 Multiversion VAX Upgrade Process Multiversion VAX Upgrade Process A.3 Specific Layered Product and Firmware Information Debugger Graphical User Interface (GUI) In order to run the Debugger Graphical User Interface (GUI) on OpenVMS Version 7.1, you must be running the DECwindows Motif for OpenVMS layered product. See Section 1.2.2 for information about DECwindows Motif. Multiversion VAX Upgrade Process A-5 B _________________________________________________________________ License Management Notes B.1 Overview This appendix contains supplemental information to the license instructions given in the installation and upgrade procedures and in the OpenVMS License Management Utility Manual. Although most of the information in this appendix pertains to managing OpenVMS and System Integrated Product (SIP) licenses, some of the information pertains to managing layered product licenses. This appendix covers the following information: o Registering your licenses o Using the License Unit Requirement Table (LURT) o License Management Facility (LMF) notes o Volume Shadowing for OpenVMS license o Other System Integrated Product (SIP) licenses B.2 Registering Your Licenses This section provides an overview of the license registration procedure. B.2.1 WHEN TO REGISTER After you install the OpenVMS VAX operating system, you must register an OpenVMS VAX license. An OpenVMS VAX license lets you use the operating system. You must also register the licenses for any of the following SIPs you have purchased: o VAXclusters o DECnet-Plus o OpenVMS RMS Journaling License Management Notes B-1 License Management Notes B.2 Registering Your Licenses o Volume Shadowing for OpenVMS After you upgrade the OpenVMS VAX operating system, in most cases there is no need to reregister licenses for the operating system or for SIPs. In addition to the OpenVMS VAX operating system and the SIPs, many layered products-including DECwindows Motif for OpenVMS VAX-that run on OpenVMS VAX Version 7.1 also require license registration. See the OpenVMS License Management Utility Manual for a full explanation of license registration. B.2.2 HOW TO REGISTER To register a license, you need to obtain a Product Authorization Key (PAK). A typical PAK is a piece of paper provided by Digital Equipment Corporation that contains the appropriate information to authorize access to software on a VAX computer or in a VAXcluster environment. You can obtain a PAK from a Digital representative the same way as you obtain software. See Table B-1 for a complete list of the versions of the OpenVMS VAX operating system and the VAX computers that were first supported by these versions. Table B-1 First VMS or OpenVMS Version That Supports VAX __________Computers________________________________________ VMS_Version_____First_Computer_Support_____________________ Version 5.0 VAX 6000 Model 2xx, VAX 8820-8840 Version 5.0-2A MicroVAX 3300/3400 Version 5.1 VAX 6000 Model 3xx, MicroVAX 3800/3900 Version 5.1-B VAXstation 3100, Model 30/40 Version 5.1-1 VAXstation 3520/3540 Version 5.2 VAX 6000 Model 4xx, MicroVAX 3100 (continued on next page) B-2 License Management Notes License Management Notes B.2 Registering Your Licenses Table B-1 (Cont.) First VMS or OpenVMS Version That __________________Supports_VAX_Computers___________________ VMS_Version_____First_Computer_Support_____________________ Version 5.2-1 VAXstation 3100, Model 38/48 Version 5.3 No CPUs introduced Version 5.3-1 No CPUs introduced Version 5.3-2 VAX 4000 Model 300 Version 5.4 VAXstation 3100 Model 76, VAX 9000, VAX 6000 Model 5xx, VAXft 310 Version 5.4-1 No CPUs introduced Version 5.4-2 VAX 4000 Model 200 Version 5.4-3 VAXft Models 410, 610, 612 Version 5.5 VAXstation 4000 VLC, MicroVAX 3100 Models 30, 40, and 80, VAX 6000 Model 600, VAX 4000 Model 500, VAXstation 4000 Model 60, and VAXft Model 110 Version 5.5-2 VAX 4000 Model 100, VAXstation 4000 Models 90 and 100, MicroVAX 3100 Model 90, VAX 4000 Model 400, VAX 4000 Model 600, VAX 7000 Model 600, and VAX 10000 Model 600 Version 5.5- VAX 4000 Models 100A, 500A, 600A, and 700A 2H4 Version 5.5- VAXft Model 810 2HF (continued on next page) License Management Notes B-3 License Management Notes B.2 Registering Your Licenses Table B-1 (Cont.) First VMS or OpenVMS Version That ___________________________________________________________ OpenVMS Version_________First_Computer_Support_____________________ Version 6.0 VAX 7000 Models 650 and 660, VAX 10000 Models 600 and 650 Version 6.1 VAX 7000 Model 7xx Version 6.2 VAX 4000 Model 106A, MicroVAX 3500 Model 95A, MicroVAX 3100 Model 96, VAXstation 4000 Model 96 ___________________________________________________________ B.3 Using the License Unit Requirement Table (LURT) Many PAKs contain a table name in the availability or activity fields. This name refers to a column in the License Unit Requirement Table (LURT). (For more information about using the LURT, see the OpenVMS License Management Utility Manual.) Table B-2 has seven lettered columns (A, B, C, D, E, F, and I; G and H are reserved by Digital and therefore are not listed). The numbers listed in these columns indicate the number of license units required for each processor listed in the System Marketing Model column. For example, if your PAK specifies availability = F, you would require 100 license units to load the license on a VAX-11/780 computer, or 4800 license units to load the license on a VAX 9000-430 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 units. Reset the PAK size to its original size after the emergency situation is resolved. B-4 License Management Notes License Management Notes B.3 Using the License Unit Requirement Table (LURT) Table_B-2_License_Unit_Requirement_Table_(LURT)__________________ ________License_Types_by_Code________ ________OpenVMS________ SIP__ ____LP_____ System Marketing Model__________________A_____B____C_____D_______E______F______I__ VAX-11/730 10 NA NA NA 230 50 50 VAX 11/750 12 NA NA NA 230 100 100 VAX 11/780, 785 13 NA NA NA 230 100 100 VAX 6000-210, 6000- 58 NA NA NA 230 300 300 310 VAXft 110 60 NA NA NA 230 100 100 VAXft 310, 410, 58 NA NA NA 230 300 300 610, 810 VAX 6000-220, 6000- 69 NA NA NA 230 600 600 320, 6000-410 VAX 6000-230, 6000- 81 NA NA NA 400 900 900 330, 6000-510 ----------------------------------------------------------------- Key to License Type Codes and Values: A-OpenVMS Capacity or OpenVMS Unlimited or Base B-OpenVMS Server C-OpenVMS Concurrent user D-OpenVMS Workstations E-System integrated products F-Layered products G-Reserved (not listed) H-OpenVMS reserved (not listed) I-Layered products NA-Not applicable (continued on next page) License Management Notes B-5 License Management Notes B.3 Using the License Unit Requirement Table (LURT) Table_B-2_(Cont.)_License_Unit_Requirement_Table_(LURT)__________ ________License_Types_by_Code________ ________OpenVMS________ SIP__ _____LP____ System Marketing Model__________________A_____B____C_____D_______E______F______I__ VAX 6000-240, 6000- 93 NA NA NA 400 1200 1200 340, 6000-350, 6000-420, 7000-610, 10000-610 VAX 6000-540, 6000- 170 NA NA NA 600 2400 2400 640 VAX 6000-550, 6000- 195 NA NA NA 600 2400 2400 650 VAX 6000-560, 6000- 220 NA NA NA 600 2400 2400 660 VAX 6000-610 81 NA NA NA 400 1200 1200 VAX 8200, 8250 20 NA NA NA 230 100 100 VAX 8300, 8350 25 NA NA NA 230 200 200 VAX 8500 63 NA NA NA 230 400 400 VAX 8530 65 NA NA NA 230 400 400 _________________________________________________________________ Key to License Type Codes and Values: A-OpenVMS Capacity or OpenVMS Unlimited or Base B-OpenVMS Server C-OpenVMS Concurrent user D-OpenVMS Workstations E-System integrated products F-Layered products G-Reserved (not listed) H-OpenVMS reserved (not listed) I-Layered products NA-Not applicable (continued on next page) B-6 License Management Notes License Management Notes B.3 Using the License Unit Requirement Table (LURT) Table_B-2_(Cont.)_License_Unit_Requirement_Table_(LURT)__________ ________License_Types_by_Code________ ________OpenVMS________ SIP__ ____LP_____ System Marketing Model__________________A_____B____C_____D_______E______F______I__ VAX 8550, 8700, 72 NA NA NA 400 600 600 8810 VAX 8600, 8650 28 NA NA NA 230 400 400 VAX 8800, 8820 93 NA NA NA 400 1200 1200 VAX 8830, 6000-360, 119 NA NA NA 600 1800 1800 6000-430, 6000-520, 6000-620 VAX 7000-620, 145 NA NA NA 600 1800 1800 10000-620 VAX 6000-440, 6000- 143 NA NA NA 600 2400 2400 450, 6000-460, 6000-530 VAX 7000-630, 167 NA NA NA 600 2400 2400 10000-630, VAX 7000-640, 197 NA NA NA 600 2400 2400 10000-640, __________________________________________________________________ Key to License Type Codes and Values: A-OpenVMS Capacity or OpenVMS Unlimited or Base B-OpenVMS Server C-OpenVMS Concurrent user D-OpenVMS Workstations E-System integrated products F-Layered products G-Reserved (not listed) H-OpenVMS reserved (not listed) I-Layered products NA-Not applicable (continued on next page) License Management Notes B-7 License Management Notes B.3 Using the License Unit Requirement Table (LURT) Table_B-2_(Cont.)_License_Unit_Requirement_Table_(LURT)__________ ________License_Types_by_Code________ ________OpenVMS________ SIP__ _____LP____ System Marketing Model__________________A_____B____C_____D_______E______F______I__ VAX 6000-630, 143 NA NA NA 600 2400 2400 9000-210, 9000-410 VAX 9000-420 241 NA NA NA 800 4800 4800 VAX 9000-430 330 NA NA NA 800 4800 4800 VAX 9000-440 386 NA NA NA 800 4800 4800 VAX 7000-710, 810 93 NA NA NA 230 600 600 VAX 7000-720, 820 193 NA NA NA 230 600 600 VAX 7000-730, 830 293 NA NA NA 230 600 600 VAX 7000-740, 840 393 NA NA NA 230 600 600 VAX 7000-750, 850 493 NA NA NA 230 600 600 VAX 7000-760, 860 593 NA NA NA 230 600 600 MicroVAX II 18 NA 100 NA 230 50 50 _________________________________________________________________ Key to License Type Codes and Values: A-OpenVMS Capacity or OpenVMS Unlimited or Base B-OpenVMS Server C-OpenVMS Concurrent user D-OpenVMS Workstations E-System integrated products F-Layered products G-Reserved (not listed) H-OpenVMS reserved (not listed) I-Layered products NA-Not applicable (continued on next page) B-8 License Management Notes License Management Notes B.3 Using the License Unit Requirement Table (LURT) Table_B-2_(Cont.)_License_Unit_Requirement_Table_(LURT)__________ ________License_Types_by_Code________ ________OpenVMS________ SIP__ ____LP_____ System Marketing Model__________________A_____B____C_____D_______E______F______I__ MicroVAX 2000, 18 NA 100 NA 230 20 20 3100-10e, 3100-20e, 3100-30, 3100-40, 3100-80 MicroVAX 3100-90, 60 NA 100 NA 230 20 20 3100-96, 3100-96A MicroVAX 3500, 60 NA 100 NA 230 200 200 3600, 3800, 3900, 4000-200 MicroVAX 3300, 60 NA 100 NA 230 100 100 3400, 4000-100, 4000-106A VAX 4000-100, 4000- 60 NA 100 NA 230 100 100 106 ___________________________________________________________ Key to License Type Codes and Values: A-OpenVMS Capacity or OpenVMS Unlimited or Base B-OpenVMS Server C-OpenVMS Concurrent user D-OpenVMS Workstations E-System integrated products F-Layered products G-Reserved (not listed) H-OpenVMS reserved (not listed) I-Layered products NA-Not applicable (continued on next page) License Management Notes B-9 License Management Notes B.3 Using the License Unit Requirement Table (LURT) Table_B-2_(Cont.)_License_Unit_Requirement_Table_(LURT)__________ ________License_Types_by_Code________ ________OpenVMS________ SIP__ _____LP____ System Marketing Model__________________A_____B____C_____D_______E______F______I__ VAX 4000-300, 4000- 60 NA 100 NA 230 300 300 400, 4000-500A, 4000- 600A, 4000-700A, 4000- 706A VAX 4000-500, 4000- 60 NA 100 NA 400 900 900 600 VAXstation II, II NA NA NA 100 50 10 10 /GPX VAXstation 2000, NA NA NA 100 50 10 10 2000/GPX VAXstation 3100, NA NA NA 100 50 10 10 3200, 3500, 3520, 3540, 4000-60, 4000 VLC, 4000-90, 4000-96 _________________________________________________________________ Key to License Type Codes and Values: A-OpenVMS Capacity or OpenVMS Unlimited or Base B-OpenVMS Server C-OpenVMS Concurrent user D-OpenVMS Workstations E-System integrated products F-Layered products G-Reserved (not listed) H-OpenVMS reserved (not listed) I-Layered products NA-Not applicable (continued on next page) B-10 License Management Notes License Management Notes B.3 Using the License Unit Requirement Table (LURT) Table_B-2_(Cont.)_License_Unit_Requirement_Table_(LURT)__________ ________License_Types_by_Code________ ________OpenVMS________ SIP__ ____LP_____ System Marketing Model__________________A_____B____C_____D_______E______F______I__ VAXserver 2000 NA 52 NA NA 50 10 10 VAXserver 3300, NA 100 NA NA 50 10 10 3400, 3500, 3600, 3900, 4000-200, 4000-300 VAXserver 6000-210, NA 1443 NA NA 230 200 200 6000-310 VAXserver 6000-220, NA 1737 NA NA 230 400 400 6000-320, 6000-410, 6000-420 VAXserver 6000-510 NA 600 NA NA 230 400 400 VAXserver 6000-520 NA 890 NA NA 230 400 400 VAXserver 9000-110, 143 143 NA NA 600 900 900 9000-310 VAXserver 9000-320 241 241 NA NA 800 1200 1200 VAXserver 9000-330 330 330 NA NA 800 1200 1200 VAXserver 9000-340 386 386 NA NA 800 1200 1200 __________________________________________________________________ Key to License Type Codes and Values: A-OpenVMS Capacity or OpenVMS Unlimited or Base B-OpenVMS Server C-OpenVMS Concurrent user D-OpenVMS Workstations E-System integrated products F-Layered products G-Reserved (not listed) H-OpenVMS reserved (not listed) I-Layered products NA-Not applicable License Management Notes B-11 B.4 License Management Facility Notes The following list is offered to help new users with some common concerns and questions regarding the License Management Facility (LMF). o If you do not have a valid OpenVMS VAX 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 VAX availability license is registered with insufficient license units for the specified VAX computer, the system displays a warning message at system startup but allows normal system use at the console level only. B-12 License Management Notes License Management Notes B.4 License Management Facility Notes o If an OpenVMS VAX activity license is registered with insufficient license units to meet your user requirements, the system displays the following message when the user (process) attempts to log in: %LICENSE-F-EXCEEDED, licensed product has exceeded current license limits A user 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. o Each VAX VMS and OpenVMS VAX Base 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. Although you can successfully activate an unassigned OpenVMS VAX license on a standalone system, you cannot activate one in a VAXcluster environment. Note that the SCS node name is not necessarily the DECnet node name. SCSNODE is a system parameter; it can be a maximum of 6 alphabetic characters. B.5 Volume Shadowing for OpenVMS License The following paragraphs describe Volume Shadowing for OpenVMS licenses. License Management Notes B-13 License Management Notes B.5 Volume Shadowing for OpenVMS License B.5.1 WHEN TO REGISTER After you install OpenVMS VAX Version 7.1, you must register your Volume Shadowing for OpenVMS license before you can use Volume Shadowing. If you upgraded to OpenVMS VAX Version 7.1, you do not need to reregister this license. B.5.2 VOLUME SHADOWING PHASE I AND PHASE II In the past, volume shadowing has offered two modes of operation: phase I and phase II. The original implementation of shadowing, phase I, was HSC controller based. The newer implementation, phase II, is host based and provides performance superior to phase I. With the release of OpenVMS VAX Version 6.2, phase I Volume Shadowing is no longer available. Refer to the Volume Shadowing for OpenVMS manual for instructions about moving from phase I to phase II. B.5.3 TYPES OF LICENSES Two types of Volume Shadowing licenses are valid for OpenVMS VAX Version 7.1: o Capacity license-If you are using this type of license, you must have one license for each node in a cluster that is accessing shadowed data. o Per-disk license-If you are using this type of license, you must have one license for every disk contained in the shadow set. For information about OpenVMS VAX Version 7.1 changes to per-disk licensing for Volume Shadowing, refer to Section 1.2.1. See the Volume Shadowing for OpenVMS manual for more information about these two licenses. B.6 Other System Integrated Product Licenses After you install OpenVMS VAX Version 7.1, you must register licenses for any system integrated product. If you upgraded to OpenVMS VAX Version 7.1, you do not need to reregister licenses for system integrated products. B-14 License Management Notes C _________________________________________________________________ Booting from [SYSF] During an Upgrade C.1 Booting Procedures You must boot from the [SYSF] root during phases 2, 3, and 4 of the upgrade procedure. Different VAX computers require that you use different booting procedures. This appendix describes how to boot the various VAX computers from [SYSF]. Go to the section that describes your VAX computer and follow the instructions for booting from [SYSF]. If you need more information about booting, refer to the upgrade and installation supplement for your VAX computer. C.1.1 MICROVAX AND VAXSTATION COMPUTERS The information in this section applies to the following VAX computers: VAXstation II, VAXstation II/GPX, and MicroVAX II VAXstation 2000 and MicroVAX 2000 VAXstation 3100 and MicroVAX 3100 series VAXstation 3200 and 3500 VAXstation 3520 and 3540 VAXstation 4000 VAXft 110, 310, 410, 610, and 612 MicroVAX 3300, 3400, 3500, 3600, 3800, and 3900 To boot from [SYSF], enter the BOOT command in the following format and press the Return key: >>> B/F0000000 device-name Substitute the device name of the system disk for device- name. Booting from [SYSF] During an Upgrade C-1 Booting from [SYSF] During an Upgrade C.1 Booting Procedures C.1.2 VAX 8530, 8550, 8810 (8700), 8820-N (8800) COMPUTERS To boot from [SYSF], use the following procedure: 1. Press Ctrl/P. Enter the following command at the console-mode prompt (>>>) and press the Return key: >>> HALT 2. Enter the BOOT command at the console-mode prompt (>>>) in the following format: >>> B dddn /R5:F0000000 Substitute BCI, BDA, or UDA for ddd. Substitute the unit number of the drive holding the system disk for n. C.1.3 VAX 8820, 8830, AND 8840 COMPUTERS To boot from [SYSF], use the following procedure: 1. Enter the following command at the PS-OS-0> prompt and press Return: PS-OS-0> HALT/CPU=ALL 2. Enter the BOOT command at the PS-CIO-0> prompt in the following format: PS-CIO-0> B dddn /R5=F0000000 Substitute BCI or BDA for ddd. Substitute the unit number of the drive holding the system disk for n. C.1.4 VAX-11/750, 8200, 8250, 8300, AND 8350 COMPUTERS To boot from [SYSF], create a command procedure named SYFBOO.CMD before the upgrade is started. To create SYFBOO.CMD, use the following procedure: ________________________ Note ________________________ This procedure assumes that you have installed and booted the OpenVMS VAX operating system and are logged in to the SYSTEM account. ______________________________________________________ 1. Log in to the SYSTEM account. 2. Make sure that the console media is in the console drive. C-2 Booting from [SYSF] During an Upgrade Booting from [SYSF] During an Upgrade C.1 Booting Procedures 3. To connect the console drive to the system, enter the following commands and press the Return key after each one: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> CONNECT CONSOLE SYSGEN> EXIT 4. Use the Exchange utility to copy the appropriate boot command procedure from the console media to your current directory on the system disk. If the system disk is on an HSC drive and you have created DEFBOO.CMD, enter the following command and press Return: $ EXCHANGE COPY CSA1:DEFBOO.CMD * On the VAX-11/750 computer, if the system disk is on a local drive, copy the boot command procedure that matches the drive that holds the system disk. For example, suppose the system disk is on an RP06 drive and has a controller designation of A and a unit number of one. Enter the following command and press the Return key: $ EXCHANGE COPY CSA1:DA1BOO.CMD * 5. Edit the boot command procedure. Change the line that deposits a value in register 5 (R5). This line contains the comment !software boot flags. The value is a hexadecimal number with eight digits. For example: D/G R5 0 !software boot flags Change the left-most digit of the value to reflect the name of the root directory from which you want to boot. For example, to boot from the [SYSF] root directory, change the line as follows: D/G/L R5 F0000000 !designated root is SYSF 6. Rename the boot command procedure to SYFBOO.CMD. For example, if the boot command procedure is DEFBOO.CMD, enter the following command and press the Return key: $ RENAME DEFBOO.CMD SYFBOO.CMD Booting from [SYSF] During an Upgrade C-3 Booting from [SYSF] During an Upgrade C.1 Booting Procedures 7. Use the Exchange utility to copy SYFBOO.CMD back to the console media. Enter the following command and press Return: $ EXCHANGE COPY SYFBOO.CMD CSA1:SYFBOO.CMD 8. When the copy operation completes, enter the following command and press Return: $ DISMOUNT CSA1 9. To secure the console media from unauthorized access, you must enter the following command and press Return: $ MOUNT/FOREIGN/SYSTEM/NOWRITE/NOASSIST CSA1 To boot from [SYSF], use the following procedure: 1. Make sure the console media is in the console drive. On the VAX-11/750 computers, make sure the keylock switch is set to LOCAL. Set the BOOT DEVICE switch to position A. On the VAX 8200 computer, set the upper keylock switch to ENABLE and the lower keylock switch to HALT. 2. Press Ctrl/P. 3. On the VAX-11/750 computer, enter the following command and press the Return key: >>> B/800 DDA0 On the VAX 8200 computer, enter the following command at the console-mode prompt (>>>) and press Return: >>> B/R5:800 CSA1 4. At the BOOT58> prompt, enter the following command: BOOT58> @SYFBOO.CMD C.1.5 VAX-11/730, 11/780, 11/785, 8600, AND 8650 COMPUTERS To boot from [SYSF], create a command procedure named SYFBOO.CMD (for VAX-11/730, 11/780, and 11/785 computers) or SYFBOO.COM (for VAX 8600 and 8650 computers) before the upgrade is started. C-4 Booting from [SYSF] During an Upgrade Booting from [SYSF] During an Upgrade C.1 Booting Procedures To create SYFBOO.CMD or SYFBOO.COM, use the following procedure: ________________________ Note ________________________ This procedure assumes that you have installed and booted the OpenVMS VAX operating system and are logged in to the SYSTEM account. ______________________________________________________ 1. Log in to the SYSTEM account. 2. Make sure that the console media is in the console drive. On the VAX 8600 computer, make sure the TERMINAL CONTROL switch is set to LOCAL. 3. To connect the console drive, enter the following commands and press the Return key after each one: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> CONNECT CONSOLE SYSGEN> EXIT 4. Use the Exchange utility to copy DEFBOO.CMD (for VAX-11/730, 11/780, and 11/785 computers) or DEFBOO.COM (for VAX 8600 and 8650 computers) from the console media to your current directory on the system disk. On the VAX-11/780, 11/785, and 8600 computers, enter a command similar to the following and press Return: $ EXCHANGE COPY CSA1:DEFBOO.CMD * On the VAX-11/730 computer, enter the following command and press the Return key: $ EXCHANGE COPY CSA2:DEFBOO.CMD * 5. Edit DEFBOO.CMD or DEFBOO.COM. Change the line that deposits a value in register 5 (R5). On the VAX-11/730, 11/780, and 11/785 computers, this line contains the comment !software boot flags. On the VAX 8600, this line contains the comment !Use R5 for optional boot control flags [SYSB.]. The value is a hexadecimal number with eight bits. For example: DEPOSIT R5 10000000 !software boot flags Booting from [SYSF] During an Upgrade C-5 Booting from [SYSF] During an Upgrade C.1 Booting Procedures Change the left-most digit of the value to reflect the name of the root directory from which you want to boot. For example, to boot from [SYSF], change the line as follows: DEPOSIT R5 F0000000 !software boot flags 6. Rename DEFBOO.CMD to SYFBOO.CMD (or DEFBOO.COM to SYFBOO.COM), as follows: $ RENAME DEFBOO.CMD SYFBOO.CMD 7. Use the Exchange utility to copy SYFBOO.CMD or SYFBOO.COM to the console media. On the VAX-11/780, 11/785, and 8600 computers, enter a command similar to the following: $ EXCHANGE COPY SYFBOO.CMD CSA1:SYFBOO.CMD On the VAX-11/730 computer, enter the following command and press the Return key: $ EXCHANGE COPY SYFBOO.CMD CSA2:SYFBOO.CMD 8. When you are finished, enter a command similar to the following and press Return: $ DISMOUNT CSA1 9. To secure the console media from unauthorized access, you must enter a command similar to the following and press Return: $ MOUNT/FOREIGN/SYSTEM/NOWRITE/NOASSIST CSA1 To boot from [SYSF] during an upgrade, use the following procedure: 1. Make sure the console media is in the console drive. On the VAX-11/730, 11/780, and 11/785 computers, make sure the keylock switch is set to LOCAL. On the VAX 8600, make sure the TERMINAL CONTROL switch is set to LOCAL. 2. Press Ctrl/P. On the VAX-11/780, 11/785, and 8600 computers, enter the HALT command at the console-mode prompt (>>>) and press the Return key: >>> HALT C-6 Booting from [SYSF] During an Upgrade Booting from [SYSF] During an Upgrade C.1 Booting Procedures 3. Use SYFBOO.CMD to boot from [SYSF]. Enter the following command and press Return: >>> B SYF C.1.6 VAX 6000 SERIES To boot from [SYSF], use the following procedure: 1. If you have a CIBCA-A adapter and are booting over the CI, insert the console tape cartridge in the console drive. 2. Press Ctrl/P to put the system in console mode. 3. Enter the BOOT command in the following format: >>> BOOT /R5:F0000000 /XMI:a /BI:b [/R3:c] [/NODE:d] DUu where: o a is the XMI node number of the system disk. o b is the VAXBI node number of the system disk. o c pertains to volume shadowing. This qualifier is not required unless you are using volume shadowing. For more information, see the Volume Shadowing for OpenVMS manual. o d is the HSC node number of the node being accessed. The /NODE qualifier is not necessary if you are booting from a local disk. The HSC node number is in hexadecimal. You can deposit a maximum of two HSC node numbers (if two HSCs are available). o u is the unit number of the drive holding the system disk. For example, suppose you want to boot from [SYSF] on an HSC disk with a unit number of one and your system has the following configuration: o The disk is connected to the VAXBI at node 2. o The VAXBI you are using is connected to the XMI at node 3. o The disk is available to two HSCs, node numbers 0E and 02. Booting from [SYSF] During an Upgrade C-7 Booting from [SYSF] During an Upgrade C.1 Booting Procedures Enter the following command and press the Return key: >>> BOOT/R5:F0000000/XMI:3/BI:2/NODE:0E02 DU1 C-8 Booting from [SYSF] During an Upgrade Booting from [SYSF] During an Upgrade C.1 Booting Procedures C.1.7 VAX 9000 SERIES The upgrade procedure automatically updates DEFBOO.CMD to boot from [SYSF]. If you want to boot a VAX 9000 computer manually from [SYSF] however, you must set up DEFBOO.CMD to boot from the system disk and perform the following procedure: 1. Press Ctrl/P to obtain the console prompt. 2. Enter the following BOOT commands: >>> I/K >>> BOOT/NOSTART >>> DEPOSIT R5 F0000000 >>> CONTINUE 3. If you set up DEFBOO.CMD properly, the system will boot from the SYSF directory on the system disk and continue with the upgrade procedure. If the system does not boot, enter the SHOW CONFIGURATION console command and verify that DEFBOO.CMD contains the correct information for your configuration. For more information, see the OpenVMS VAX Upgrade and Installation Supplement: VAX 9000 Series. Booting from [SYSF] During an Upgrade C-9 D _________________________________________________________________ OpenVMS VAX Save Set Subclasses This appendix lists the file subclasses contained in the following save sets: o VMS070.C-Library save set o VMS070.D-Optional save set o VMS070.E-Help Message save set o VMS070.F-OpenVMS Management Station save set D.1 Save Set C Subclasses The following files are contained in the Library save set: o Network support Incoming Remote File Access files Incoming Remote Terminal files Network Test files Remote Task Loading o Programming Support Debugger utility (DEBUG) Image Dump utility (ANALYZE/PROCESS_DUMP) RMS Analyze and FDL Editor utilities (ANALYZE/RMS, ANALYZE/FDL) Message utility (MESSAGE) Object and Shareable Image libraries MACRO libraries MACRO assembler SDL intermediary form of STARLET.MLB Fortran required files VAX C object libraries X/Open transport interface libraries OpenVMS RMS journaling files OpenVMS VAX Save Set Subclasses D-1 OpenVMS VAX Save Set Subclasses D.1 Save Set C Subclasses o System programming Support Files-11 ODS-1, ISO 9660, High Sierra ACPs Monitor utility Delta/XDelta debugger System Dump Analyzer utility (ANALYZE/SYSTEM, ANALYZE /CRASH) System Symbol Table file (SYS.STB) Miscellaneous symbol table files o Secure User's Environment File Access Control List utilities Print and Batch Queue utilities Input Queue Symbiont (Card Reader) Accounting Log Report Generator utility DECdtm o Utilities Mail utility DUMP utility RUNOFF utility Phone utility OpenVMS Help library Foreign Terminal Support LAT-11 terminal server (via Ethernet) Standalone backup Error Log Report Generator utility (ANALYZE/ERROR) DECTPU Terminal Fallback Facility National Character Set utility (NCS) C language internationalization utilities o TECO editor o EDT documentation o OpenVMS workstation support o Workstation device support D-2 OpenVMS VAX Save Set Subclasses OpenVMS VAX Save Set Subclasses D.2 Save Set D Subclasses D.2 Save Set D Subclasses The following files are contained in the Optional save set: o Miscellaneous files o System map o LPA-11 support o BLISS required files o UETP (the User Environment Test Package) o Example files D.3 Save Set E Subclasses The following files are contained in the Help Message save set: o Help Message database D.4 Save Set F Subclasses The following files are contained in the OpenVMS Management Station save set: o OpenVMS Management Station software PC files OpenVMS VAX Save Set Subclasses D-3 E _________________________________________________________________ DECwindows Display Server and Fonts Components This appendix provides a list of files provided by the DECwindows base and workstation support components included on the OpenVMS VAX distribution kit. E.1 Table of Components Table E-1 contains the name of the DECwindows display server and fonts components, the directory where the component can be found, a brief description of what the component does, and one of the following component classifications: o BASE-Indicates that the component is part of all installations. o WS-Indicates that the component is part of the workstation support. o FONT-Indicates the component is part of the fonts component. Table_E-1_DECwindows_Display_Server_and_Fonts_Components_________ Component File______________________Purpose__________________________Class_ __________________________Files_in_DECW$KEYMAP_Directory_________ DECW$KEYMAP BASE (continued on next page) DECwindows Display Server and Fonts Components E-1 DECwindows Display Server and Fonts Components E.1 Table of Components Table_E-1_(Cont.)_DECwindows_Display_Server_and_Fonts_Components_ Component _________________________________________________________________ __________________________Files_in_SYS$LOADABLE_IMAGES_Directory_ GAADRIVER.EXE VAXstation II/GPX driver WS GABDRIVER.EXE VAXstation 2000/GPX driver WS GBBDRIVER.EXE VAXstation 35x0 driver WS GCADRIVER.EXE VAXstation II monochrome WS device driver GCBDRIVER.EXE VAXstation 2000 monochrome WS device driver GEBDRIVER.EXE Scanproc graphics device WS driver GECDRIVER.EXE Spxg/gt graphics device driver WS GFBDRIVER.EXE Low-cost graphics device WS driver IEDRIVER.EXE Input extension driver WS IKDRIVER.EXE Keyboard decoder driver WS IMDRIVER.EXE Mouse decoder driver WS INDRIVER.EXE Common input function driver WS WSDRIVER.EXE Set display driver BASE _________________________________________________________________ __________________________Files_in_SYS$SYSTEM_Directory__________ DECW$FONTCOMPILER.EXE Font compiler image FONT DECW$MKFONTDIR.EXE Font utility to generate list FONT of fonts and paths DECW$SERVER_MAIN.EXE Server main image WS DECW$SETSHODIS.EXE SHOW DISPLAY command image BASE (continued on next page) E-2 DECwindows Display Server and Fonts Components DECwindows Display Server and Fonts Components E.1 Table of Components Table_E-1_(Cont.)_DECwindows_Display_Server_and_Fonts_Components_ Component File______________________Purpose__________________________Class_ __________________________Files_in_DECW$FONT_Directory___________ See VMS DECwindows Xlib DECwindows fonts WS Programming Volume _________________________________________________________________ __________________________Files_in_DECW$EXAMPLES_Directory_______ DECW$FONT_ALIAS_ Example alias file for Charter FONT CHARTER.DAT fonts DECW$FONT_ALIAS_ Example alias file for 100 dpi FONT CHARTER_100DPI.DAT Charter fonts DECW$FONT_ALIAS_ Brief alias name list for FONT FILENAMES.DAT shipped fonts DECW$FONT_ALIAS_ Example alias file for FONT KANJI.DAT Kanjifonts DECW$FONT_ALIAS_ Example alias file for Lucida FONT LUCIDA.DAT fonts DECW$FONT_ALIAS_LUCIDA_ Example alias file for 100 dpi FONT 100DPI.DAT Lucida fonts _________________________________________________________________ __________________________Files_in_SYS$LIBRARY_Directory_________ DECW$DRIVER.MLB Driver macro library WS DECW$FONTCOMPILER.CLD CLD for font compile commands FONT DECW$SERVER_DDX_GA.EXE Server color device support WS shareable image DECW$SERVER_DDX_GB.EXE Server color device support WS shareable image DECW$SERVER_DDX_GC.EXE Server monochrome device WS support shareable image (continued on next page) DECwindows Display Server and Fonts Components E-3 DECwindows Display Server and Fonts Components E.1 Table of Components Table_E-1_(Cont.)_DECwindows_Display_Server_and_Fonts_Components_ Component File______________________Purpose__________________________Class_ __________________________Files_in_SYS$LIBRARY_Directory_________ DECW$SERVER_DDX_GE.EXE Server scanproc device- WS dependent shareable image DECW$SERVER_DDX_GF.EXE Server low-cost graphics WS device-dependent shareable image DECW$SERVER_DIX.EXE Server device independent WS support DECW$SERVER_XINPUT_ Input extension for handling WS IE.EXE nonstandard input devices DECW$SESSIONSHRP.EXE Support routines for BASE DECwindows Session Manager DECW$SVEXT_ADOBE_DPS_ Display PostScript server WS EXTENSION.EXE extension image DECW$SVEXT_D2DX_ DECwindows 2D extensions WS EXTENSIONS.EXE DECW$SVEXT_DEC_ Input and event recording and WS XTRAP.EXE playback extension DECW$SVEXT_MULTI_ DECwindows multi-buffering WS BUFFERING.EXE extension DECW$SVEXT_X3D_PEX.EXE Phigs Extension to X (PEX) for WS 3D DECW$SVEXT_X3D_PEX_ PEX for 35x0 systems WS GB.EXE DECW$SVEXT_X3D_PEX_GB_ PEX microcode for 35x0 systems WS UCODE.EXE DECW$SVEXT_X3D_PEX_ PEX for scanproc systems WS GE.EXE (continued on next page) E-4 DECwindows Display Server and Fonts Components DECwindows Display Server and Fonts Components E.1 Table of Components Table_E-1_(Cont.)_DECwindows_Display_Server_and_Fonts_Components_ Component File______________________Purpose__________________________Class_ __________________________Files_in_SYS$LIBRARY_Directory_________ DECW$SVEXT_X3D_PEX_ PEX for scanproc systems with WS STP.EXE geometry processor DECW$SVEXT_X3D_PEX_STP_ PEX microcode for scanproc WS UCODE.EXE systems with geometry processor DECW$SVEXT_X3D_PEX_ PEX color frame buffer WS VCFB.EXE (software PEX) DECW$SVEXT_XIE.EXE DECwindows imaging extension WS DECW$SVEXT_ DECwindows input extension WS XINPUTEXTENSION.EXE DECW$TRANSPORT_ Common transport shareable BASE COMMON.EXE image DECW$TRANSPORT_ DECnet transport image BASE DECNET.EXE DECW$TRANSPORT_ Local transport image BASE LOCAL.EXE DECW$TRANSPORT_ TCP/IP transport image BASE TCPIP.EXE DECW$XPORTCOM.H Common transport definitions BASE DECW$XPORTCOM.MAR Common transport definitions BASE DECW$XPORTCOM.R32 Common transport definitions BASE DECW$XPORTDEF.H Transport definitions BASE DECW$XPORTDEF.MAR Transport definitions BASE DECW$XPORTDEF.R32 Transport definitions BASE DECW$XPORTMAC.R32 Transport BLISS macros BASE (continued on next page) DECwindows Display Server and Fonts Components E-5 DECwindows Display Server and Fonts Components E.1 Table of Components Table_E-1_(Cont.)_DECwindows_Display_Server_and_Fonts_Components_ Component File______________________Purpose__________________________Class_ __________________________Files_in_SYS$LIBRARY_Directory_________ DECW$XPORTMSG.R32 Transport message symbols BASE XDPS$MASTERDPSVM.DAT Display PostScript support WS file _________________________________________________________________ __________________________Files_in_SYS$MANAGER_Directory_________ DECW$DEVICE.COM Device detection and BASE configuration DECW$DEVICE_GE.COM Scanproc device detection and WS configuration DECW$DEVICE_GF.COM Low-cost graphics device WS detection and configuration DECW$DEVICE_GG.COM Scanproc turbo device WS detection and configuration DECW$RGB.DAT Definitions of the color names WS used by the XStoreNamedColor and XAllocNamedColor requests DECW$STARTSERVER.COM Server initialization and WS startup _________________________________________________________________ __________________________Files_in_SYS$MESSAGE_Directory_________ DECW$TRANSPORTMSG.EXE Transport message image BASE (continued on next page) E-6 DECwindows Display Server and Fonts Components DECwindows Display Server and Fonts Components E.1 Table of Components Table_E-1_(Cont.)_DECwindows_Display_Server_and_Fonts_Components_ Component _________________________________________________________________ __________________________Files_in_SYS$UPDATE_Directory__________ DECW$MKFONTDIR.COM Command file to invoke FONT DECW$MKFONTDIR.EXE font utility _________________________________________________________________ DECwindows Display Server and Fonts Components E-7 F _________________________________________________________________ NEW_OVER and NEW_UNDER Files This appendix lists files installed either over or under existing files during an upgrade. F.1 Where Files Are Installed During an upgrade, the procedure replaces certain files that exist on your system with new versions of those files from the OpenVMS VAX distribution kit. For some system files, the upgrade procedure does not replace your existing system files, which might contain customizations for your site. Instead, the procedure retains your existing file and installs the new file from the kit at a version number higher or at a version number lower than your existing file. You can use the DCL command DIFFERENCES to compare the contents of your existing files and the contents of the new files provided by OpenVMS VAX Version 7.1. Enter the command using the following syntax: DIFFERENCES/OUTPUT=filespec existing_filename new_filename The /OUTPUT qualifier causes the DIFFERENCES command to write the list of differences to the output file you specify. This output file will have the default file type .DIF. For more information about using the DIFFERENCES command, refer to the OpenVMS DCL Dictionary. New files that the procedure installs at a version number higher than your existing files are referred to as new_over files. You must use these files at least until you complete the upgrade. After you have upgraded your system, you can add your customizations to these files. NEW_OVER and NEW_UNDER Files F-1 NEW_OVER and NEW_UNDER Files F.1 Where Files Are Installed New files installed at a version number lower than the existing files are referred to as new_under files. This allows you to continue to use your existing files during and after the upgrade. If you purge a new_over file, you are left with the new version of the file provided by the distribution kit, and any customizations you might have made to the existing file will be lost. If you purge a new_under file, you are left with the file that existed before the upgrade. In addition to the new_over and new_under files, there are certain files that are intended to contain your site- specific modifications. During an upgrade, the old versions of these files are retained if they were present before the upgrade. The new version of the file is installed only if no old version is present on your system. With the exception of TFF$STARTUP.COM, there is a corresponding .TEMPLATE file for each of the site-specfic files. The new version of the .TEMPLATE file replaces the old version. F.1.1 NEW_OVER FILES During an upgrade, the following new files are installed over (that is, at a version number higher than) the existing files: [SYSEXE]SHUTDOWN.COM [SYSEXE]STARTUP.COM [SYSHLP]HELPLIB.HLB [SYSLIB]ADARTL.EXE [SYSLIB]BASRTL.EXE [SYSLIB]BASRTL2.EXE [SYSLIB]BLAS1RTL.EXE [SYSLIB]COBRTL.EXE [SYSLIB]DBLRTL.EXE [SYSLIB]DCLTABLES.EXE [SYSLIB]ENCRYPSHR.EXE [SYSLIB]FORRTL.EXE [SYSLIB]FORRTL2.EXE [SYSLIB]IMAGELIB.OLB [SYSLIB]LBRSHR.EXE [SYSLIB]LIBRTL.EXE [SYSLIB]LIBRTL2.EXE [SYSLIB]MTHRTL.EXE F-2 NEW_OVER and NEW_UNDER Files NEW_OVER and NEW_UNDER Files F.1 Where Files Are Installed [SYSLIB]PASRTL.EXE [SYSLIB]PLIRTL.EXE [SYSLIB]PPLRTL.EXE [SYSLIB]RPGRTL.EXE [SYSLIB]SCNRTL.EXE [SYSLIB]STARLET.OLB [SYSLIB]UVMTHRTL.EXE [SYSLIB]VAXCRTL.EXE [SYSLIB]VAXCRTLG.EXE [SYSLIB]VBLAS1RTL.EXE [SYSLIB]VMSRTL.EXE [SYSLIB]VMTHRTL.EXE [SYSMGR]DBLSTRTUP.COM [SYSMGR]WELCOME.TEMPLATE [SYSMGR]WELCOME.TXT F.1.2 NEW_UNDER FILES During an upgrade, the following new files are installed under (that is, at a version number lower than) the existing files: [SYS$LDR]VMS$SYSTEM_IMAGES.DATA [SYS$STARTUP]ESS$LAST_STARTUP.DAT [SYS$STARTUP]VMS$LAYERED.DAT [SYSEXE]VMS$IMAGE_VERSION.DAT [SYSLIB]CDDSHR.EXE [SYSLIB]EPC$FACILITY.TLB [SYSLIB]EPC$SHR.EXE [SYSLIB]UISSHR.EXE [SYSMSG]EPC$MSG.EXE F.1.3 SITE-SPECIFIC FILES The following files are intended to contain site-specific modifications. Note that, with the exception of TFF$STARTUP.COM, there is a corresponding .TEMPLATE file for each of these files. The new version of the .TEMPLATE file replaces the old version. [SYSEXE]SYSUAF.DAT [SYSMGR]AGEN$NEW_NODE_DEFAULTS.DAT [SYSMGR]AGEN$NEW_SATELLITE_DEFAULTS.DAT [SYSMGR]LAT$SYSTARTUP.COM [SYSMGR]LOGIN.COM NEW_OVER and NEW_UNDER Files F-3 NEW_OVER and NEW_UNDER Files F.1 Where Files Are Installed [SYSMGR]SYCONFIG.COM [SYSMGR]SYLOGICALS.COM [SYSMGR]SYLOGIN.COM [SYSMGR]SYPAGSWPFILES.COM [SYSMGR]SYSECURITY.COM [SYSMGR]SYSHUTDWN.COM [SYSMGR]SYSTARTUP_VMS.COM [SYSMGR]TFF$STARTUP.COM F-4 NEW_OVER and NEW_UNDER Files G _________________________________________________________________ Preparing to Use OpenVMS Management Station This appendix describes how to prepare your OpenVMS system and your PC to run the OpenVMS Management Station server and client software. The OpenVMS Management Station is a client-server application that provides OpenVMS system management capabilities through a client application on a personal computer (PC) running Microsoft Windows. During the OpenVMS VAX installation or upgrade procedure, the OpenVMS Management Station server files are automatically installed on your OpenVMS system disk. However to obtain complete support, you must also select the OpenVMS Management Station client software files during the OpenVMS installation or upgrade procedure. Those files are required to create the installation media that you use to install the client software on your PC. If you did not select the OpenVMS Management Station component during the installation or upgrade, you must add those files to your OpenVMS system disk before you follow the instructions in this appendix. Use the OpenVMS VAX distribution media and VMSTAILOR to add the OpenVMS Management Station files to your system. (For information about using VMSTAILOR, see Chapter 10.) G.1 Preparing Your OpenVMS System You must prepare your OpenVMS system to run the server software so that your system can properly interact with the PC running the client software. The procedures include the following: o Set up within a mixed-architecture cluster environment (if applicable). o Start the server on other nodes. Preparing to Use OpenVMS Management Station G-1 Preparing to Use OpenVMS Management Station G.1 Preparing Your OpenVMS System o Update the printer database. o Edit the system files. o Allow OpenVMS Management Station to control the printer environment. o Keep your printer environment up to date. o Check if running third-party TCP/IP stacks. o Recover from a failure. o Determine and report problems. G.1.1 FILES INSTALLED ON YOUR OPENVMS SYSTEM The following files are created on your OpenVMS system when the OpenVMS Management Station server is installed: o SYS$SYSTEM:TNT$SERVER.EXE o SYS$STARTUP:TNT$STARTUP.COM o SYS$STARTUP:TNT$SHUTDOWN.COM o SYS$STARTUP:TNT$UTILITY.COM o SYS$TEST:TNT$IVP.COM o SYS$COMMON:[SYSTEST.TNT]TNT$SERVER_IVP.EXE o SYS$HELP:TNTV20.RELEASE_NOTES These optional files are created when you install PC installation media files: o SYS$COMMON:[TNT.CLIENT]DISKIMAG.EXE o SYS$COMMON:[TNT.CLIENT]TNTCLID1.IMG o SYS$COMMON:[TNT.CLIENT]TNTCLID2.IMG o SYS$COMMON:[TNT.CLIENT]TNTCLID3.IMG o SYS$COMMON:[TNT.CLIENT]TNTCLID4.IMG o SYS$COMMON:[TNT.CLIENT]TNTCLID5.IMG o SYS$COMMON:[TNT.CLIENT]TNTCLID6.IMG These files are created when the server is started: o SYS$COMMON:[SYSEXE]TNT$UADB.DAT o SYS$COMMON:[SYSEXE]TNT$ACS.DAT G-2 Preparing to Use OpenVMS Management Station Preparing to Use OpenVMS Management Station G.1 Preparing Your OpenVMS System o SYS$COMMON:[SYSEXE]TNT$JOURNAL.TNT$TRANSACTION_JOURNAL G.1.2 SETTING UP IN A MIXED-ARCHITECTURE CLUSTER ENVIRONMENT The OpenVMS Management Station server creates three main configuration files: o TNT$UADB.DAT o TNT$ACS.DAT o TNT$JOURNAL.TNT$TRANSACTION_JOURNAL In a common-environment cluster with one common system disk, you use a common copy of each of these files located in the SYS$COMMON:[SYSEXE] directory on the common system disk, or on a disk that is mounted by all cluster nodes. No further action is required. However, to prepare a common user environment for an OpenVMS Cluster system that includes more than one common VAX system disk or more than one common Alpha system disk, you must coordinate the files on those disks. Rules: The following rules apply: o Disks holding common resources must be mounted early in the system startup procedure, such as in the SYLOGICALS.COM procedure. o You must ensure that the disks are mounted with each cluster reboot. Follow these steps to coordinate files: 1. Decide where to locate the files. In a cluster with multiple system disks, system management is much easier if the common system files are located on a single disk that is not a system disk. 2. Copy TNT$UADB.DAT, TNT$ACS.DAT, and TNT$JOURNAL.TNT$TRANSACTION_JOURNAL to a location other than the system disk. 3. Edit the file SYS$COMMON:[SYSMGR]SYLOGICALS.COM on each system disk and define logical names that specify the location of the cluster common files. Preparing to Use OpenVMS Management Station G-3 Preparing to Use OpenVMS Management Station G.1 Preparing Your OpenVMS System Example: If the files will be located on $1$DJA16, define logical names as follows: $ DEFINE/SYSTEM/EXEC TNT$ACS - _$ $1$DJA16:[VMS$COMMON.SYSEXE]TNT$ACS.DAT $ DEFINE/SYSTEM/EXEC TNT$UADB - _$ $1$DJA16:[VMS$COMMON.SYSEXE]TNT$UADB.DAT $ DEFINE/SYSTEM/EXEC TNT$JOURNAL - _$ $1$DJA16:[VMS$COMMON.SYSEXE]TNT$JOURNAL.TNT$TRANSACTION_JOURNAL 4. To ensure that the system disks are mounted correctly with each reboot, follow these steps: 1. Copy the SYS$EXAMPLES:CLU_MOUNT_DISK.COM file to the [VMS$COMMON.SYSMGR] directory, and edit it for your configuration. 2. Edit SYLOGICALS.COM and include commands to mount, with the appropriate volume label, the system disk containing the shared files. Example: If the system disk is $1$DJA16, include the following command: $ @SYS$SYSDEVICE:[VMS$COMMON.SYSMGR]CLU_MOUNT_DISK.COM - _$ $1$DJA16: volume-label G.1.3 START THE SERVER ON OTHER NODES If you plan to run OpenVMS Management Station on more than one node in an OpenVMS Cluster without a reboot, you need to start the software on those nodes. Enter the following command: $ @SYS$STARTUP:TNT$STARTUP.COM If you are performing an upgrade or a reinstallation and OpenVMS Management Station is already running on the node, add the RESTART parameter to the startup command, as follows: $ @SYS$STARTUP:TNT$STARTUP.COM RESTART G-4 Preparing to Use OpenVMS Management Station Preparing to Use OpenVMS Management Station G.1 Preparing Your OpenVMS System G.1.4 UPDATE THE PRINTER DATABASE When you installed OpenVMS Management Station, the installation started the OpenVMS Management Station server on the installation node and created an initial version of the printer database file TNT$ACS.DAT. However, this initial version of the database might not contain complete device and queue information for your OpenVMS Cluster system. To complete the database, first start the OpenVMS Management Station server on each node in your cluster. The instances of the server communicate with each other to determine device and queue information, and the server must be running on each node for this communication to take place. Once you have started the server on each node, run the following procedure to update the printer database: $ @SYS$STARTUP:TNT$UTILITY UPDATE PRINTERS G.1.5 EDIT THE SYSTEM FILES To start the OpenVMS Management Station server from your system startup files, insert the following line into your system startup procedures (usually SYS$MANAGER:SYSTARTUP_ VMS.COM) after both the Queue Manager and network are started, but before ENABLE AUTOSTART/QUEUES. $ @SYS$STARTUP:TNT$STARTUP BOOT (The best place for this is immediately prior to the ENABLE AUTOSTART/QUEUES command.) ________________________ Note ________________________ Remove any other invocations of TNT$STARTUP you might have added in previous releases of the OpenVMS Management Station. OpenVMS Management Station cannot start until the network has started. If you start your network using a batch process, OpenVMS Management Station might start before the batch process completes and the network is started. ______________________________________________________ Preparing to Use OpenVMS Management Station G-5 Preparing to Use OpenVMS Management Station G.1 Preparing Your OpenVMS System Add the following command line to the system shutdown file, SYS$MANAGER:SYSHUTDWN.COM: $ @SYS$STARTUP:TNT$SHUTDOWN.COM G.1.6 ALLOW OPENVMS MANAGEMENT STATION TO CONTROL THE PRINTER ENVIRONMENT Placing the server startup before ENABLE AUTOSTART/QUEUES in the system startup procedure allows the server to start any queues not already started by your existing DCL command procedures. It is not necessary to remove your existing queue startup DCL procedures immediately. The OpenVMS Management Station server will recognize that you started a queue with your command procedures and will assume that you want it that way. As you become familiar with the server's management ability, you can remove or comment out the DCL commands and procedures that perform these tasks and allow OpenVMS Management Station to control your printer environment. G.1.7 KEEP YOUR PRINTER ENVIRONMENT UP TO DATE The OpenVMS Management Station server installation creates a file named SYS$STARTUP:TNT$UTILITY.COM. This command procedure scans the OpenVMS system and updates the database of known printers, queues, and related devices. TNT$UTILITY.COM runs at regular intervals to keep the database files synchronized with the actual system. G.1.8 WHEN DOES TNT$UTILITY.COM RUN? The TNT$UTILITY.COM procedure runs: o As part of the OpenVMS Management Station installation. o When you specifically invoke it. o At periodic intervals as a background thread. Two logical names control how often it runs: G-6 Preparing to Use OpenVMS Management Station Preparing to Use OpenVMS Management Station G.1 Preparing Your OpenVMS System ________________________________________________________ Logical_Name__________Description_______________________ TNT$PRINTER_RECON_ How often TNT$UTILITY.COM should INTERVAL run, in minutes, from when the server was last started on this node. If you do not define this logical, the default value is 1440 minutes (24 hours). TNT$PRINTER_RECON_ The minimum number of minutes that INTERVAL_MIN must elapse before TNT$UTILITY.COM should run again, starting from when the database was last updated. If you do not define this logical, the default value is 60 minutes (1 hour). _________________________________________________________________ You can think of these logicals as meaning "run TNT$UTILITY.COM this often (TNT$PRINTER_RECON_INTERVAL), but make sure this much time has elapsed since the database was last updated (TNT$PRINTER_RECON_INTERVAL_MIN)." Because you can run TNT$UTILITY.COM yourself, and because the OpenVMS Management Station server also updates the database, the TNT$PRINTER_RECON_INTERVAL_MIN logical prevents the database from being updated more frequently than is actually needed. If you want to change the defaults for one of these logicals, define the logical on all nodes on which the OpenVMS Management Station server is running. G.1.9 DO YOU NEED TO RUN TNT$UTILITY.COM MANUALLY? If you use OpenVMS Management Station to make all of the changes to your printer configuration, the configuration files are immediately modified to reflect the changes and you probably do not need to specifically run TNT$UTILITY.COM. TNT$UTILITY.COM runs at periodic intervals as a background thread to make sure that the database is kept up to date. Preparing to Use OpenVMS Management Station G-7 Preparing to Use OpenVMS Management Station G.1 Preparing Your OpenVMS System However, if you or someone else uses DCL to make a change - for example, if you use the DELETE /QUEUE command to delete a queue - the configuration files will not be synchronized. In this case, the OpenVMS Management Station client will advise you to run TNT$UTILITY.COM to resynchronize the database. Run the following procedure on one node in the cluster to make the database match your system: $ @SYS$STARTUP:TNT$UTILITY.COM UPDATE PRINTERS For example, if you or someone else used DCL to delete a queue, you need to delete that queue from the database. TNT$UTILITY.COM assumes that your system is set up and running the way that you want it to, so you should fix any problems before you run TNT$UTILITY.COM. G.1.10 ARE THERE ANY REQUIREMENTS FOR RUNNING TNT$UTILITY.COM? You need the SYSNAM privilege to run TNT$UTILITY.COM. TNT$UTILITY.COM connects to the OpenVMS Management Station server on the current OpenVMS system to determine device and queue information. Therefore, the OpenVMS Management Station server must be running on the node where you run TNT$UTILITY.COM. The OpenVMS Management Station server then connects to the other OpenVMS Management Station servers in the OpenVMS Cluster to determine device and queue information. It is generally a good idea to keep the OpenVMS Management Station server running on the other nodes in an OpenVMS Cluster to keep the database up to the minute. However, if the OpenVMS Management Server is not able to connect to the OpenVMS Management Station server on a given node, it uses the known information about that OpenVMS node from the database. That is, in the absence of a valid connection to that OpenVMS node, the information in the database is assumed to be correct. G-8 Preparing to Use OpenVMS Management Station Preparing to Use OpenVMS Management Station G.1 Preparing Your OpenVMS System G.1.11 ENABLING DISK QUOTAS Before installing OpenVMS Management Station, you might have disabled disk quotas on the SYSTEM disk. If so, you should reenable the quotas and then rebuild to update quota information by entering the following commands: $ RUN SYS$SYSTEM:DISKQUOTA DISKQUOTA> ENABLE DISKQUOTA> REBUILD DISKQUOTA> EXIT G.1.12 RUNNING THIRD-PARTY TCP/IP STACKS Digital TCP/IP Services for OpenVMS Version 3.2 or higher is the only supported TCP/IP stack. Additional stacks have not been tested. However, TCP/IP stacks that are 100% compliant with the QIO interface for TCP/IP Services for OpenVMS should also work. (Contact your TCP/IP vendor for additional information and support issues.) For the best chance of success, check the following: o Make sure that the QIO service (for example, UCXQIO) is enabled. o For TCPware, also make sure that TCPware's UCX$IPC_SHR.EXE is an installed image. G.1.13 DETERMINING AND REPORTING PROBLEMS If you encounter a problem while using OpenVMS Management Station, please report it to Digital. Depending on the nature of the problem and the type of support you have, you can take one of the following actions: o If your software contract or warranty agreement entitles you to telephone support, call Digital. o If the problem is related to OpenVMS Management Station documentation, use the Internet address printed in front of this book to send us your comments. Preparing to Use OpenVMS Management Station G-9 Preparing to Use OpenVMS Management Station G.2 Preparing Your PC G.2 Preparing Your PC During the OpenVMS Version 7.1 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 Required memory and disk space o Required software o TeamLinks support o Creating the installation media o Installing the client software o Getting started using OpenVMS Management Station G.2.1 REQUIRED MEMORY AND DISK SPACE Your PC requires 8 MB of random-access memory (RAM) and 11.5 MB of free disk space to install the OpenVMS Management Station client software. G.2.2 REQUIRED SOFTWARE Table G-1 describes the software that must be installed on your PC before installing OpenVMS Management Station. G-10 Preparing to Use OpenVMS Management Station Preparing to Use OpenVMS Management Station G.2 Preparing Your PC Table_G-1_Prerequisite_and_Optional_Software_for_PCs_______ Prerequisite_Products______Purpose_________________________ Microsoft Windows NT Operating system Version 3.51 or Microsoft Windows 95 or Microsoft Windows Version 3.1 or Microsoft Windows for Workgroups Version 3.11 ___________________________________________________________ Optional_Products__________Purpose_________________________ PATHWORKS Version 5.1 for Integrate with PATHWORKS, DOS and Windows client DECnet support software ManageWORKS Workgroup ManageWORKS integration Administrator, Version 2.2 Your TCP/IP stack IP connections _________________________________________________________________ PATHWORKS for Windows 95 and any version of Windows NT prior to Version 3.51 are not officially supported. G.2.3 TEAMLINKS VERSION 1.0 IS NOT SUPPORTED If Version 1.0 of TeamLinks is installed on your PC, the OpenVMS Management Station PC installation program will ask whether to update the XTI library component of TeamLinks. If you answer No, the OpenVMS Management Station installation terminates. However, if you allow OpenVMS Management Station to update the XTI library, Version 1.0 of TeamLinks will no longer work. The version of the XTI library included with Version 1.0 of TeamLinks does not allow TCP/IP connections from your PC and is not supported in this version of OpenVMS Management Station. If you want to utilize both TCP/IP connections Preparing to Use OpenVMS Management Station G-11 Preparing to Use OpenVMS Management Station G.2 Preparing Your PC and TeamLinks, you must upgrade to a higher version of TeamLinks. G.2.4 CREATING THE INSTALLATION MEDIA Create the PC installation media using the following procedure. Note: You need six formatted 3-1/2-inch, high-density floppy disks. 1. For PCs running TCP/IP, at the MS-DOS prompt use the FTP utility on the PC to copy the files by entering commands similar to the following: C:\> cd temp-dir C:\temp> ftp ftp> open node Connected to node Username: username Password: password User logged in. ftp> cd sys$common:[tnt.client] ftp> type bin ftp> mget *.* 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. 2. For PCs running DECnet, at the MS-DOS prompt use the NFT utility on the PC to copy the files by entering the following command: 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. The node name must be defined in the PC's network database. G-12 Preparing to Use OpenVMS Management Station Preparing to Use OpenVMS Management Station G.2 Preparing Your PC 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. Repeat this process for TNTCLID2.IMG through TNTCLID6.IMG 5. You can delete the files DISKIMAG.EXE and TNTCLID1.IMG through TNTCLID6.IMG from temp-dir after creating the floppy disks. G.2.5 INSTALLING THE OPENVMS MANAGEMENT STATION CLIENT SOFTWARE ON YOUR PC 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 G.2.6 INSTALLATION DIRECTORY The installation procedure allows you to select the installation directory, and suggests \VMSTNT as the default. Do not install OpenVMS Management Station into the PATHWORKS or ManageWORKS Workgroup Administrator directories. If you do want to configure PATHWORKS or ManageWORKS Workgroup Administrator to load OpenVMS Management Station, see Section G.2.14. Preparing to Use OpenVMS Management Station G-13 Preparing to Use OpenVMS Management Station G.2 Preparing Your PC G.2.7 INSTALLATION PROCEDURE Follow these steps to install OpenVMS Management Station client: 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. You are then prompted to continue. 7. To proceed with the installation, click on the Next button. Note: You can stop the installation at any time by clicking on the Cancel button. As the installation progresses, the system displays a status bar indicating 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. Repeat this process for the remaining disks. G-14 Preparing to Use OpenVMS Management Station Preparing to Use OpenVMS Management Station G.2 Preparing Your PC G.2.8 RECOVERING FROM ERRORS If an error occurs during installation, you will receive an error message describing the problem. This information can help you determine the cause of the problem. An error can occur during the installation if one or more of the following conditions exist: o The operating system version is incorrect. o The prerequisite software version is incorrect. o Disk space and memory necessary for successful installation are inadequate. G.2.9 FILES CREATED ON THE PC The following files (with their directory names) are created on your PC after the OpenVMS Management Station client software is installed: o OpenVMS Management Station directory (usually \VMSTNT) - VMSACNT.DLL - VMSACNT.HLP - VMSCLU.DLL - VMSCUSCT.DLL - VMSINFRA.DLL - VMSMGMT.DLL - VMSMGMT.HLP - VMSMSCRL.DLL - VMSNODE.DLL - VMSPRINT.HLP - VMSSCOPE.HLP - VMSTAB.DLL - VMSTIMEL.DLL - VMSUAOMM.DLL - CLASS.IDX - CLASS.POD Preparing to Use OpenVMS Management Station G-15 Preparing to Use OpenVMS Management Station G.2 Preparing Your PC - CONTAIN.DLL - CONTAIN.IDX - CONTAIN.POD - DISPATCH.DLL - MWBROWSE.DLL - MW_OEM.DLL - MW_OEM2.DLL - MW_OEM3.DLL - OMMLIB.DLL - OBJECT.POD - OBJECT.IDX - POD.DLL - PRMAKTPL.EXE - PWMGMT.EXE - PWMGMT.HLP - PWMGMT.INI - PWSHELL.DLL - SVN.DLL - SVNVIEW.DLL - XMEM.DLL o Windows directory (usually \WINDOWS) - XTIDNW.DLL - XTILIB.DLL - XTIWINS.DLL - VMSTNT.INI o Windows systems directory (usually \WINDOWS\SYSTEM) - CTL3DV2.DLL - COMPOBJ.DLL - MFC250.DLL G-16 Preparing to Use OpenVMS Management Station Preparing to Use OpenVMS Management Station G.2 Preparing Your PC - MFCO250.DLL - MFCOLEUI.DLL - OLE2.DLL - OLE2DISP.DLL - OLE2NLS.DLL - STORAGE.DLL G.2.10 AFTER INSTALLING THE CLIENT SOFTWARE ON YOUR PC OpenVMS Management Station allows you to use both the TCP/IP and DECnet transports to establish connections. You can have a mix of DECnet and TCP/IP connections, all DECnet connections, or all TCP/IP connections. OpenVMS Management Station does not have any DECnet dependencies and can run in a TCP/IP-only environment. Note that Windows NT and Windows 95 support TCP/IP connections only. You do need to make sure that your PC can connect to the primary-server systems, as described in the following sections. OpenVMS Management Station connects your PC to the primary-server system and then routes management operations to the target systems. G.2.11 DEFINING TCP/IP NODES If you select the TCP/IP transport, your host's file or name server must be able to resolve the IP name or address of all primary-server systems. If you can successfully ping the primary-server systems from your PC, then this condition is met. G.2.12 DECNET SUPPORT If you want to use DECnet connections, PATHWORKS Version 5.1 for DOS and Windows must be installed somewhere on the PC and listed in the PC's path statement. Define the DECnet node names and network addresses of primary-server OpenVMS systems that you want to manage. Preparing to Use OpenVMS Management Station G-17 Preparing to Use OpenVMS Management Station G.2 Preparing Your PC G.2.13 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. _________________________________________________________________ G.2.14 PATHWORKS AND WORKGROUP ADMINISTRATOR SUPPORT You no longer need the PATHWORKS client software to run OpenVMS Management Station. OpenVMS Management Station installs into its own directory and includes all of the ManageWORKS components it needs to run. If you happen to have PATHWORKS or ManageWORKS Workgroup Administrator installed, both will continue to function independently of OpenVMS Management Station. You can configure PATHWORKS Version 5.1 for DOS and Windows or the ManageWORKS Workgroup Administrator Version 2.2 to load the OpenVMS Management Station software if you want to. To do this, run the ManageWORKS Setup application and use the Browse feature to select the file ARGUS.MMI in the VMSTNT directory. Refer to the ManageWORKS online help for step-by-step instructions. G-18 Preparing to Use OpenVMS Management Station Preparing to Use OpenVMS Management Station G.2 Preparing Your PC G.2.15 POLYCENTER MANAGER ON NETVIEW FOR WINDOWS NT, VERSION 3.0 You can launch OpenVMS Management Station from POLYCENTER Manager on NetView for Windows NT, Version 3.0. To do this, copy the file VMSTNT.REG from the temporary directory (or disk 1 if you requested client media) to the following directory: \usr\ov\registration\c\ Note that NetView can be installed only on an NTFS partition. G.3 Getting Started with OpenVMS Management Station All information about getting started, setting up, and using OpenVMS Management Station is contained in online help and the OpenVMS Management Station Overview and Release Notes. G.3.1 ACCESSING ONLINE HELP Follow these steps to access the OpenVMS Management Station online help: 1. Open the OpenVMS Management Station program group. 2. Click on the OpenVMS Management Help icon for instructions on how to get started. Preparing to Use OpenVMS Management Station G-19 H _________________________________________________________________ Small Capacity System Disks H.1 Overview This appendix describes some methods you can use to manage small capacity system disks, along with some specific recommendations for installing or upgrading to OpenVMS VAX Version 7.1 and DECwindows Motif for OpenVMS VAX Version 1.2-3 on an RZ24, RA80, or RM80 system disk. (These recommendations will also work for Versions 1.1 and 1.2 of the DECwindows Motif for OpenVMS VAX layered product.) Note that you can use the methods described in this appendix to free disk space on any space-constrained system. H.2 Limited Space Support As the OpenVMS VAX operating system and associated layered products continue to develop and mature, their sizes have grown so that previously acceptable system disk devices might now have insufficient capacity for the desired computing environment. Support for added features, conformance to standards, addition of online documentation, and especially, support for a graphical user environment (specifically, DECwindows Motif) have contributed to this growth. Although a single-user workstation system might be perceived as entry level, it does, in fact, have an increased need for system disk capacity to handle the desired graphical environment. Small Capacity System Disks H-1 Small Capacity System Disks H.2 Limited Space Support H.2.1 LIMITED SPACE SUPPORT OPTION In the past, when the OpenVMS VAX operating system grew too large for a specific disk type, that disk was no longer supported as a system device. The OpenVMS VAX Version 7.1 operating system and the DECwindows Motif for OpenVMS VAX Version 1.2-3 layered product cannot fit, in total, on an RZ24 disk device. However, to preserve the investment in some user configurations, a limited space support option has been introduced that will allow the RZ24 to continue to be used as a system disk but with some features removed. For the most part, these features include new online documentation, programming examples, and programming support files. The most important mechanisms used to provide this environment are the OpenVMS VAX and DECwindows tailoring facilities, VMSTAILOR and DECW$TAILOR. (For more information about these facilities, see Chapter 10.) The limited space support option means that, although the disk (in this case, the RZ24) is supported as a system device, you must take some explicit action to not install or to remove some portions of the product so the remainder will fit. This option gives small, resource-constrained system users a choice between investing in new hardware or continuing with existing hardware but with (possibly) reduced capabilities. H.2.2 CONFIGURATIONS AFFECTED The RZ24 disk is now too small for the full OpenVMS VAX Version 7.1 and DECwindows Motif for OpenVMS VAX Version 1.2-3 kits, regardless of user configuration. Other disk devices, such as the RZ24 and RD54 disks, will need to be closely monitored, depending on the system environment and user configuration. The general disk space guideline for OpenVMS VAX plus DECwindows Motif for OpenVMS VAX Version 1.2-3 is a system disk of at least 213 megabytes (or about 377,000 disk blocks). For nonworkstation, single-user systems, this guideline can be reduced to about 125 megabytes because DECwindows support is not necessary. For timesharing systems, a larger disk is usually necessary due to the need for many layered products and applications. For VAXcluster H-2 Small Capacity System Disks Small Capacity System Disks H.2 Limited Space Support systems, a larger system disk capacity is also usually required. See the VAXcluster SPD for details. For specific information about disk space requirements and supported system disks, see the OpenVMS VAX SPD. While the absolute minimum disk space requirements can make base system support available, layered products, applications, and user files usually make it necessary to manage even large capacity system disks carefully. Therefore, some of the following techniques and ideas can be useful for a broader range of users than can be listed by hardware type. H.2.3 DEALING WITH A SMALL SYSTEM DISK You can solve small system disk configuration problems three ways: o Upgrade your hardware to a larger capacity disk device. o Add additional hardware disk devices (one or more) to the system and redistribute the software contents. o Reduce the software contents on the existing disk device. Upgrading hardware might have the highest monetary cost, but has the benefits of a full environment and the simplest and fastest upgrade mechanism. Adding additional hardware (or using existing extra hardware) can require less money, but requires more time and effort for setting up and maintaining the environment. Reducing the software contents requires the lowest capital expense but, by necessity, removes some features, documentation, or capabilities. If your major constraint is fiscal, you might want to investigate the tailoring recommendations first. If time or simplicity are more important, you might want to purchase a larger system disk. Small Capacity System Disks H-3 Small Capacity System Disks H.3 Tailoring Considerations H.3 Tailoring Considerations Most of this appendix describes the mechanisms for reducing the software contents on the existing disk device, mostly by tailoring. There are also some hints for multiple disk systems. There is nothing specific to recommend for upgrading the hardware device, except that moving up in a single large increment is much more effective than several smaller ones. The target device in the following sections is the RZ24 disk, which has 209 megabytes of disk space. However, you can use these methods on any system that is tight on system disk space. H.3.1 CONFIGURATION GOALS The basic configuration goal for the limited space support option is for an environment that is not used for programming. Typically, this would be a system with a few user applications or a turnkey system. It is possible to build a viable system with a single programming language environment (notably, the C language); however, the space used for this support and for the compiler reduces the amount of available user space. There are some mechanisms and techniques common to any space-constrained system both for installing new systems and for upgrading existing systems. One of the most important considerations is to reduce the disk space consumption of the normal, ongoing system environment before doing an upgrade or as soon as possible during or after an installation. Some methods for accomplishing this are discussed in Section H.6 and in Section H.7. Note that, during an upgrade or installation, there will be a period of time when the windowing software is likely to be unavailable. This means that, on a workstation, your monitor will function only as an operator console, and you will not be able to use screen-oriented editors. H-4 Small Capacity System Disks Small Capacity System Disks H.3 Tailoring Considerations H.3.2 CONTROLLING THE SIZE OF DUMP, PAGE, AND SWAP FILES One of the primary things to control is the sizing of the dump, page, and swap files in AUTOGEN. The tailoring facilities automatically use AUTOGEN to reboot the system, adjusting anything that the tailoring might have affected. Because AUTOGEN normally includes existing disk space in calculating the sizes for these files, unexpected results can occur when tailoring removes some files and AUTOGEN increases the size of others. Fixing the size of these files by adding appropriate lines to the file SYS$SYSTEM:MODPARAMS.DAT will prevent this from occurring during an upgrade or after an installation (and, possibly, while installing layered products). The following values are suggested as generous for an upgrade: PAGEFILE = 38000 SWAPFILE = 13500 DUMPFILE = 0 If your system has been running successfully with smaller values, use those instead. If your windowing system is unavailable, you will not be able to use a screen-oriented editor to add these lines to the SYS$SYSTEM:MODPARAMS.DAT file. You can use the COPY command to add lines to the end of the text file as follows: $ COPY SYS$SYSTEM:MODPARAMS.DAT,SYS$INPUT: SYS$SYSTEM:MODPARAMS.DAT newparam1 = value1 newparam2 = value2 ________________________ Note ________________________ To be able to use the delete key more effectively when typing input to the console, set the operator terminal to be a scope (assuming it is not a hardcopy device). To set the console terminal to be a scope, enter the following command: $ SET TERM/SCOPE/PERM _OPA0: ______________________________________________________ Small Capacity System Disks H-5 Small Capacity System Disks H.3 Tailoring Considerations H.3.3 MAKE A BACKUP COPY OF YOUR SYSTEM DISK It is important to make a backup copy of your system disk before any system software upgrade. When tailoring and system environment options must be used to fit the required software on the device, it is even more important to make a backup copy before you begin and at major milestones during the procedure. This gives you a fallback to a last good position in the event that a subsequent step produces undesired side effects (especially when tailoring software off of the disk) or fails due to unexpectedly running out of space. H.3.4 ANALYZE THE SYSTEM DISK The space used on the system disk might include files that have been only partially deleted (usually, because they were still open when an attempt was made to delete them). To recover this space, enter the following command: $ ANALYZE/DISK/REPAIR SYS$SYSDEVICE: Continue to use the ANALYZE/DISK/REPAIR command after every reboot or before each major step to be sure that all free blocks are available for the upgrade procedure to use. H.3.5 TAILORING OPTIONS The installation and upgrade procedures (for both OpenVMS VAX Version 7.1 and DECwindows Motif) let you select optional software to install or upgrade only by save set. The tailoring facilities are capable of finer granularity and can usually select files in smaller groups within the save sets. In the case of DECW$MOTIF_TAILOR, the save sets and tailoring groups are the same. Additionally, DECW$MOTIF_ TAILOR can only tailor off. To add files, you must either use the installation or upgrade procedures or use the OpenVMS Backup utility (BACKUP) manually to select the desired files. For the VMSTAILOR and DECW$TAILOR utilities, the tailorable options are subsets of the installation and upgrade save sets and can be tailored either on or off. If there is sufficient space to take an entire save set, it is usually faster to select it during the procedure and then tailor off the undesired pieces, rather than tailor them on later. H-6 Small Capacity System Disks Small Capacity System Disks H.3 Tailoring Considerations If you are doing an upgrade and have a large area of user application files or a large database that is not part of the OpenVMS VAX operating system or DECwindows Motif layered product but resides on the system disk, it might be convenient to back up that data to a separate piece of media, delete it from the system disk before the upgrade, and then restore it after the upgrade. The blocks can be used in the interim, and you can save time and effort in the tailoring and upgrade process. You can decrease the time needed to perform the tailoring and upgrade tasks by disabling highwater marking on the system disk. To disable highwater marking, enter the following command: $ SET VOLUME/NOHIGHWATER SYS$SYSDEVICE: Depending on the system security you require, you might want to leave highwater marking permanently disabled. Otherwise, you can restore it by entering the following command: $ SET VOLUME/HIGHWATER SYS$SYSDEVICE: H.4 Installing OpenVMS VAX and DECwindows Motif In general, installing OpenVMS VAX Version 7.1 and DECwindows Motif for OpenVMS VAX Version 1.2-3 is easier than doing an upgrade because there are no user files on the disk when you perform the installation. However, because the total size of the two kits is larger than the capacity of the RZ24 disk, you cannot select some options and you might have to do some tailoring. H.4.1 INSTALL OPENVMS VAX VERSION 7.1 By itself, the entire OpenVMS VAX Version 7.1 distribution kit fits on the RZ24 system disk. So, the easiest approach might be to select both the library and optional save sets, then use the VMSTAILOR and DECW$TAILOR utilities to increase the free space before installing the DECwindows Motif layered product. Small Capacity System Disks H-7 Small Capacity System Disks H.4 Installing OpenVMS VAX and DECwindows Motif If you plan to run DECnet for OpenVMS, be sure to select the library save set. If you do not perform system programming or BLISS programming, do not have an LPA11 device, do not need any of the OpenVMS example files, and do not need the UETP facility, you can choose not to select the optional save set during the installation. The BLISS support in the optional save set (approximately 7000 blocks) and the examples (over 8500 blocks) are two of the largest single areas that you can easily tailor off. You might choose not to install the Help Message utility (MSGHLP) because this option is also very large (8900 blocks). Or, you can select it at the expense of other tailorable options later (or at the expense of reduced user capacity). Once the OpenVMS VAX installation is complete, set up the dump file as required. It is preferable not to have a dump file at all or to use the paging file as described in Section H.6.1. Also, set fixed sizes for the page and dump files so that AUTOGEN does not continually resize them as you proceed with tailoring and installing the DECwindows Motif for OpenVMS layered product. When your environment is complete, you can remove the fixed sizes to allow AUTOGEN to calculate appropriate sizes based on the final space on the disk. To fit the operating system on an RZ24 disk and have sufficient space to add some layered product or application packages and have user space remaining, you can generally support, at most, one programming language and no online examples or manuals. Use the VMSTAILOR and DECW$TAILOR utilities to remove software you do not need. H.4.2 INSTALL DECWINDOWS MOTIF Depending on the options and setup of your system, you might have sufficient space to install the entire DECwindows Motif for OpenVMS kit. However, it is likely that you again will need to remove support for all but one programming language and not include the examples. Because the programming support save sets for each language are large, choose only the support for languages you really need. In the case of the example files, you might want to install them if you have the space required, and then H-8 Small Capacity System Disks Small Capacity System Disks H.4 Installing OpenVMS VAX and DECwindows Motif tailor them off once you have perused them or copied them to another area. Remember to use the ANALYZE/DISK/REPAIR command to recover any lost space from partially deleted files. Small Capacity System Disks H-9 Small Capacity System Disks H.5 Upgrading OpenVMS VAX and DECwindows Motif H.5 Upgrading OpenVMS VAX and DECwindows Motif The following sections describe how to upgrade to OpenVMS VAX Version 7.1 with the DECwindows Motif Version 1.2- 3 layered product from an OpenVMS Version 6.1 or 6.2 system running VMS DECwindows Motif Version 1.1. (Note that Version 1.1 is the minimum version of DECwindows Motif that you can run on OpenVMS VAX Version 7.1.) This option requires the most attention and extra tailoring consideration because the disk blocks used by the DECwindows Motif layered product cannot be used during the OpenVMS VAX upgrade procedure. This means that you might not be able to select even the library save set during the upgrade and that you would need to tailor on portions of it (most notably, the DECnet support). Depending on your configuration, it might be necessary to tailor off DECwindows Motif and then reinstall it following the upgrade. H.5.1 UPGRADING TO OPENVMS VAX VERSION 7.1 Before beginning the upgrade procedure, prepare the system environment-notably the dump, page, and swap files (see Section H.3.2)-and remove as many excess files from the system disk as possible. Use the tailoring facilities to remove files that will be replaced or obsoleted by the upgrade procedure. This is a good way to get the necessary space (48,950 blocks) to start the upgrade but probably will not contribute to the final additional capacity required. Tailor off all the OpenVMS programming files, examples, and miscellaneous utilities and any DECwindows Motif support that is not required. Before upgrading the operating system, keep, at most, one language support option, and do not keep any DECwindows Motif examples unless you have sufficient space to get at least the OpenVMS VAX required and library save sets directly in the upgrade. If you have sufficient space after tailoring to allow both the OpenVMS VAX required and library save sets to be selected, then the upgrade will include DECnet support and DECwindows Motif will start normally after the upgrade. H-10 Small Capacity System Disks Small Capacity System Disks H.5 Upgrading OpenVMS VAX and DECwindows Motif If you cannot select the library save set, the lack of DECnet support will likely keep DECwindows Motif from starting on your system (at which point you will have only the operator window on your workstation). You can then tailor on the DECnet support to get DECwindows Motif for OpenVMS running again. After you have DECwindows Motif running, tailoring on any other pieces you might not have already acquired from either the library or optional save sets will be easier. Digital recommends that you not take the optional Help Message utility (unless you install it on an alternate device). You will want to choose the DECwindows device support if you are upgrading a workstation. Remember to use the ANALYZE/DISK/REPAIR command to clean up any partially deleted files. H.6 Managing Single or Small System Disk Systems The primary goal for this type of environment is to reduce the system disk block usage incurred by the OpenVMS VAX system during normal operation. Both dynamic usage and static requirements can be reduced in various ways. Some system processing overhead can also be reduced or eliminated in this fashion, along with a corresponding reduction in system disk I/O. H.6.1 SYSTEM DUMP FILE One of the best mechanisms for reducing the total block overhead of the system is to carefully define the usage of the system dump file. Normally, this is configured as a separate file, SYS$SYSTEM:SYSDUMP.DMP, to which the contents of memory are written after a detected system failure. Depending on your system requirements, you might be able to reduce or eliminate this disk usage. One effective technique is to use part of the system paging file, SYS$SYSTEM:PAGEFILE.SYS, as a temporary dump file, so that the space used for dump files is not permanently reserved and gets used only in the event of a crash. To do this, you will need to modify some system parameters in SYS$SYSTEM:MODPARAMS.DAT and delete the actual SYSDUMP.DMP file if it exists. This method is most effective for systems having small or medium memory sizes. Small Capacity System Disks H-11 Small Capacity System Disks H.6 Managing Single or Small System Disk Systems Alternately, you might set the DUMPSTYLE parameter to use the selective dump mechanism to reduce the size of the dump file. This method is typically used for large memory systems that do not need to preserve the entire memory contents in the event of a system failure. Instead of using selective dumps to the paging file, keep a separate, but smaller, SYSDUMP.DMP file. If you have no need to preserve dump files or are running in a very stable environment, you might want to clear the DUMPBUG parameter to avoid all dump processing and not write a dump file on failure. H.6.2 USING PAGEFILE.SYS FOR THE DUMP FILE To use the system paging file as a dump file, add the following lines to the SYS$SYSTEM:MODPARAMS.DAT file: DUMPBUG = 1 ! Enable system dumps (default) SAVEDUMP = 1 ! Keep dump in pagefile until analysis DUMPFILE = 0 ! Disallow AUTOGEN to create or size dump file Then delete the SYSDUMP.DMP file by entering the following command: $ DELETE SYS$SYSTEM:SYSDUMP.DMP;* Because the system currently has the file open, the delete command will not physically remove the file until the system is shut down and rebooted. Use the AUTOGEN facility to reboot the system. When it has rebooted, enter the following command to clean up and finish the deletion of the file (and any others that were in a similar state): $ ANALYZE/DISK/REPAIR SYS$SYSDEVICE: After a system failure that writes dump information to the pagefile, you can analyze the data by entering the following command: $ ANALYZE/CRASH SYS$SYSTEM:PAGEFILE.SYS When your analysis is complete, you can free the pages to be used for paging once again by entering the following command: $ ANALYZE/CRASH/RELEASE SYS$SYSTEM:PAGEFILE.SYS H-12 Small Capacity System Disks Small Capacity System Disks H.6 Managing Single or Small System Disk Systems For more information about the system dump file, see the OpenVMS VAX System Dump Analyzer Utility Manual. H.6.3 DECOMPRESSING LIBRARIES The OpenVMS help libraries (as well as some programming libraries) are distributed in a compressed format. You can use the SYS$UPDATE:LIBDECOMP.COM procedure to decompress the libraries all at once or individually. For a small system disk, it is almost never worth the extra disk blocks consumed to decompress these libraries. The cost of leaving them compressed is a longer access time when you use them. If you frequently use help or an individual programming library, it might be worthwhile to individually decompress those libraries. If you only infrequently use help or do not mind the slower response time of the libraries in compressed form, leave them compressed. H.6.4 DISABLING LOG FILE CREATION Depending on your environment, there might be system jobs that create log files of no concern to you or that contain more information than you need. Unless you are a network manager or experiencing network problems, you probably do not need to log network events. By not logging network events, you can save disk space, a process slot, and some memory in the running system. To disable network logging, enter the following commands: $ MCR NCP PURGE KNOWN LOGGING ALL $ MCR NCP CLEAR KNOWN LOGGING ALL You need to enter these commands only once; they become permanent unless you reset the DECnet logging information. To reduce the logging information for other tasks (such as OPCOM, Accounting, Security Auditing, Network Monitor Event Listener, and system-created batch log files), you need to add some commands to your system-specific startup command file, SYS$MANAGER:SYSTARTUP_VMS.COM (previously called SYSTARTUP_V5.COM). Small Capacity System Disks H-13 Small Capacity System Disks H.6 Managing Single or Small System Disk Systems The following is an example SYSTARTUP_VMS.COM command file for a single-user workstation: $ SET NOON ! Continue thru any problems. $! $ DEFINE/USER SYS$COMMAND _OPA0: ! Disable some events from $ REPLY/DISABLE=(NETWORK,CLUSTER,SECURITY) ! using the operator window. $ SET TERM/SCOPE/PERM _OPA0: ! If windows do not start, use as scope. $! $ SET AUDIT/ALARM - ! Log interesting audit events. /ENABLE=(AUDIT,AUTHORIZATION,ACL,LOGIN=(LOCAL,DIALUP,NETWORK,REMOTE),- LOGFAILURE=ALL,BREAKIN=ALL) $! $ IF F$SEARCH("SYS$MANAGER:ACCOUNTNG.DAT;-1") .NES. "" THEN - PURGE SYS$MANAGER:ACCOUNTNG.DAT/KEEP=4 ! Purge old accounting info $! $ IF F$SEARCH("SYS$MANAGER:OPERATOR.LOG;-1") .NES. "" THEN - PURGE SYS$MANAGER:OPERATOR.LOG/KEEP=4 ! Purge old operator info $! $ DEFINE/SYSTEM/EXEC SYS$SYLOGIN SYS$MANAGER:SYLOGIN ! Set up system login $! $ ENABLE AUTOSTART/QUEUES ! Provide resources for autostart queues $ START/QUEUE SYS$BATCH ! Start a batch queue $! $ SUBMIT/NOKEEP/NOPRINT SYS$MANAGER:STARTNET ! Start net without batch log $! $! ... add other system specific and layered product commands here ... $! $ EXIT You might have an environment that can function with even less information than that shown in the example. For example, to disable the operator log file, you would use REPLY/NOLOG, or to disable accounting, you would use SET ACCOUNTING/DISABLE. For more information about using these commands, see the OpenVMS DCL Dictionary. H-14 Small Capacity System Disks Small Capacity System Disks H.6 Managing Single or Small System Disk Systems H.6.5 ACCESSING EXAMPLE AND DOCUMENTATION FILES If you have network access to another OpenVMS system (especially a timesharing system), you do not need to duplicate the example files distributed in the OpenVMS VAX or DECwindows Motif kits if they are available on the remote system. Similarly, remote access to the on line documentation files will also save considerable disk space on any system with constrained disk space. H.7 Managing Multiple Disk Systems The following sections describe techniques for managing multiple disk systems. In addition to the goal of reducing the space requirements on the system device, it is possible to simultaneously reduce some of the I/O load to the system disk by redirecting necessary functions to an alternate device. H.7.1 ALTERNATE PAGE AND SWAP FILES Setting up alternate page and swap files is one of the best ways to reduce both the system disk space usage and I/O overhead. If you set up only a small primary page file on the system disk and install additional page and swap files in the startup command file SYS$MANAGER:SYPAGSWPFILES.COM, you can permanently cause these files to consume the least amount of space on the system device. For more information about setting up alternate page and swap files, see the OpenVMS System Manager's Manual. H.7.2 COPYING DUMP FILES At startup, you can enhance the use of the paging file as a dump file that will automatically copy dump data for later analysis. This releases the disk space in SYS$SYSTEM:PAGEFILE.SYS to be used for paging automatically as well. Instead of manually invoking the System Dump Analyzer (SDA) to release the pages, you can add the following commands to the SYS$MANAGER:SYSTARTUP_VMS.COM file: Small Capacity System Disks H-15 Small Capacity System Disks H.7 Managing Multiple Disk Systems $ ANALYZE/CRASH SYS$SYSTEM:PAGEFILE.SYS COPY alternate_disk:[dir]dumpname.ext EXIT ________________________ Note ________________________ The dump file, whether it is SYSDUMP.DMP or PAGEFILE.SYS, must reside on the system disk. This might limit the actual savings you can achieve using alternate page files. ______________________________________________________ H.7.3 OFFLOADING SYSTEM LOGS AND FILES There are several system logs and files that can be redirected to another device. For other system logs and files, it might be easier to reset and start a new log file, copy the old file or files to another device, and purge them from the system disk. Some files that can be redirected are the system authorization file, the queue manager database, the audit log file, and batch log files. Some files that can be reset, copied, and purged are the operator log file, the accounting log file, and network log files. For more information about these facilities see the OpenVMS System Manager's Manual, the OpenVMS DCL Dictionary, or the utility reference manual for the utility whose files you want to offload. H.7.4 OFFLOADING NONESSENTIAL FILES Some of the files included with OpenVMS VAX Version 7.1 can be redirected to an alternate device during the installation or upgrade procedure. This can save many valuable system disk blocks while providing quick access to these files. For a small system disk configuration with multiple disks, this approach is recommended if you want the the Help Message utility (MSGHLP) to be available on line. H-16 Small Capacity System Disks _________________________________________________________________ Glossary boot, bootstrap The process of loading system software into a processor's main memory. This guide uses the term boot to refer to this process. boot command procedure A program, stored on the console fixed disk, that is used to boot the OpenVMS operating system from a specified controller. Digital provides a boot command procedure for each controller that the processor supports. boot name The abbreviated name of the boot command procedure you use to boot the system. boot server A VAX computer that is part of a local area VAXcluster. 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 VAXcluster A computer system consisting of a number of VAX computers. It uses only the computer interconnect (CI) to communicate with other VAX computers in the cluster. These computers share a single file system. computer interconnect (CI) A type of I/O subsystem. It links VAX computers to each other and to HSC devices. See also Hierarchical Storage Controller (HSC) device. Glossary-1 DECW$TAILOR A software program that lets you add or remove DECwindows files from your system disk. device name The name used to identify a device on the system. A device name indicates the device code, controller designation, and unit number. disk server A VAX computer that is part of a local area VAXcluster. This computer provides an access path to CI, CSSI, and locally-connected disks for other computers that do not have a direct connection. Hierarchical Storage Controller (HSC) device A self-contained, intelligent, mass storage subsystem that lets VAX computers in a VAXcluster environment share disks. Examples are the HSC50 and the HSC70. HSC drive Any disk or tape drive connected to an HSC device is called an HSC drive. A system disk on an HSC drive can be shared by several VAX computers in a VAXcluster environment. InfoServer A general-purpose disk storage server that allows you to use the distribution compact disc to install the operating system on remote client systems connected to the same LAN (local area network). local area VAXcluster A configuration consisting of one or more VAX computers that act as a MOP server and disk server, and a number of low-end VAX 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 Any drive that is connected directly to a VAX computer. Glossary-2 media Any packaging agent capable of storing computer software. Examples: compact discs, magnetic tapes, floppy diskettes, disk packs, tape cartridges. MOP server A computer system running DECnet that downline loads VAXcluster satellites using the DECnet MOP protocol. satellite node A VAX computer that is part of a local area VAXcluster. 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 VAXcluster. See also boot server, disk server, MOP server. save set The format in which the Backup utility stores files. The OpenVMS operating system is shipped in this format. 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. spin up, spin down To spin up means to bring a disk drive up to operating speed; to spin down means to bring it to a gradual stop. standalone BACKUP A subset of the BACKUP utility that is booted into main memory instead of running under the control of the OpenVMS operating system. Standalone BACKUP is used to back up and restore the system disk and to install OpenVMS operating system software. standalone system A computer system with only one VAX computer. Glossary-3 system disk The disk that contains or will contain the OpenVMS operating system. An OpenVMS system disk is set up so that most of the OpenVMS files can be shared by several VAX computers. In addition, each computer has its own directory on the system disk that contains its page, swap, and dump files. target drive The drive that holds the system disk during an upgrade or installation. transaction log A log used by DECdtm services to record information about transactions. The Log Manager Control Program (LMCP) is used to create a transaction log. 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 VAXcluster environment. VAXcluster environment A computer system consisting of a number of VAX computers. There are three types of VAXcluster environments: CI only, local area, and mixed interconnect. VMSTAILOR A software program that lets you add or remove optional OpenVMS files from your system disk. Glossary-4 _________________________________________________________________ Index A AUTOGEN command procedure _______________________________ running (cont'd) Accounting logs at end of an upgrade, effect of upgrades on, 5-4 7-29 Accounts before an upgrade, 5-8 disabling during an Automatic restart installation, 3-22 for an upgrade, 5-18 setting up after an installation, 4-4 B______________________________ AGEN$INCLUDE files Backing up the system disk, location for upgrades, 5-17 AGEN$PARAMS.REPORT file, 4-11, 4-10, 8-16 8-17 BACKUP command Allocation classes using to create a system determining, 2-5 disk, 3-5 ALLOCLASS parameter, 2-5 Backup procedures ANALYZE/DISK_STRUCTURE utility before an upgrade, 5-9 error message, 5-12 Boot command procedures using before an upgrade, dddGEN, 7-24 5-12 DEFBOO, 7-24 Auditing files Booting replacing after upgrade, 8-3 from console media, 7-11 AUTOGEN from [SYSF], C-1 to C-9 accessing data files during manually during an upgrade, an upgrade, 5-17 7-11 AUTOGEN command procedure with InfoServer ISL file, feedback data, 5-8 3-3 running Building standalone BACKUP, after an installation, 4-3 4-10 after an upgrade, 8-16 at end of an installation, 3-34 Index-1 Console media C______________________________ automatic update during an C2 systems, 2-4 upgrade, 5-10 Checklists backing up after an upgrade, postinstallation, 4-11 8-16 postupgrade, 8-17 backing up before an upgrade, preinstallation, 2-12 5-9 preupgrade, 5-24 booting from during an CI only VAXcluster upgrade, 7-11 information needed to install copying, 5-10 , 2-5 modifying for automatic Cluster upgrades restart, 5-18 See Concurrent upgrades modifying to boot from [SYSF] See Rolling upgrades , 7-11 Clusters required for an installation, See also VAXcluster 2-13 environments required for upgrades, 5-7 group numbers, 2-6 restoring original boot passwords, 2-6 command procedures, 7-24 CLUSTER_SIZE parameter updating after an upgrade, of system disk, 3-7 8-5 Command procedures using backup copies, 5-10 checking after an upgrade, Creating a system disk, 3-5 8-4 from InfoServer devices, Common files 3-10 coordinating for multiple Customizing the system, 4-3 boot servers, G-3 D coordinating for multiple _______________________________ system disks, G-3 Date Compact disc kit format for entering, 7-8 contents of, 1-7 dddGEN boot command procedure Computer-specific installation restoring original version, instructions, 3-1 7-24 Concurrent upgrades, 6-1 DECnet restrictions, 6-1 configuring after an setting QUORUM parameter, installation, 4-5 6-3 DECnet for OpenVMS upgrade procedures, 6-2 to preparing for an upgrade, 6-3 5-18 CONSCOPY.COM procedure, 5-10 DECnet node addresses, 2-5 Console DECnet node names, 2-5 connecting with SYSGEN, 8-6 DECnet Phase IV, 1-1 ignoring during startup, 4-6 installing on system, 1-2 Index-2 DECnet Phase IV (cont'd) DECwindows Motif for OpenVMS running with DECwindows Motif (cont'd) , 4-6 using with OpenVMS VAX DECnet-Plus, 1-1 Version 7.1, 2-2 choosing to install, 3-18, DECwindows support components, 7-19 5-23 installing during an base support, 3-15, 7-16 installation, 3-33 choosing options installing during an upgrade, during an installation, 7-28 3-14 removing from system, 1-2 during an upgrade, 7-16 DECnet-Plus license customizing, 9-1 registering after an customizing after an upgrade, installation, 4-3 8-14 registering during an customizing the server, 9-1 installation, 3-31 display server files, E-1 registering during an upgrade distribution media , 7-26 removing from drive, 3-20 Decompressing system libraries font files, E-1 after an installation, 4-7 installing, 2-11, 3-20 after an upgrade, 8-10 sizes, 3-16, 7-17 DECset Version 11 TCP/IP transport, 9-8 caution before upgrading, transports, 9-9 5-2 using customer-written changing the default debugger transports, 9-9 after upgrading, 5-3 workstation support, 3-15, before upgrading, 5-2 7-16 DECW$IGNORE_DECNET logical Default volume label, 3-10 name, 4-6 DEFBOO boot command procedure DECW$MOTIF_TAILOR utility, H-6 restoring original version, DECW$TAILOR utility 7-24 using on a small system disk, Device names H-6 determining, 2-6, 3-5 using to install optional format for upgrade, 7-6 components, 3-12 HSC name format for an using to remove files from a upgrade, 7-6 system disk, 4-9, 8-12, Devices 10-11, 10-12 configuring before an upgrade DECwindows Motif for OpenVMS , 7-3 minimum version requirement, DIGITAL Storage Systems 1-3 Interconnect (DSSI) disks support for, 3-15 See DSSI disks tailoring, 8-12 Index-3 Digital TCP/IP Services for Dump files (cont'd) OpenVMS purged during an upgrade, configuring, 9-9 7-19 function, 9-9 requirement for an upgrade, installing mandatory update, 5-12 4-9, 8-15 shared, 5-6, 5-12 Directories processed during an upgrade, E 7-23 _______________________________ Directory trees Editing startup files, 4-3 merged during an upgrade, Error formatter (ERRFMT) 7-23 stopped during an upgrade, Disk drives 7-11 selecting for an installation Errors during installation , 2-6 license messages, 3-9 Disk space Errors during upgrades increasing on the system cluster hang during shutdown, disk, 8-12, H-2 6-6 needed for an upgrade, 5-13 console update, 8-7 needed to decompress while entering device code, libraries, 8-10 7-7 needed to decompress system EXPECTED_VOTES parameter, 8-5 libraries, 4-7 setting for rolling upgrade, needed to run UETP, 4-6, 6-5 8-12 F Distribution kit _______________________________ compact disc, 1-7 Factory installed software magnetic tapes, 1-7 See FIS OpenVMS VAX, 3-2 Feedback data save sets in, 1-6 checking before an upgrade, Standalone BACKUP, 3-2 5-8 tape cartridges, 1-7 FIELD account TK50 tape cartridges in, 3-2 setting passwords, 3-21 with multiple volumes, 3-2 FIS (Factory installed Distribution media, 1-5 software), xiii loading, 7-4 location during an upgrade, H 5-5 _______________________________ multiple volumes, 7-4 Hardware DSSI disks supported, G-10 device name change, 2-2 Help Message save set Dump files contents, D-3 checking size, 8-4 Help Message utility controlling size of, H-5 installing, 2-8, 3-13 modifying size, 8-3 Index-4 Hierarchical Storage Installation procedure Controller (HSC) (cont'd) See HSC selecting optional components HSC , 3-12 device format for an setting passwords, 3-21 installation, 3-6 stages of, 3-1 device format for an upgrade, time zones, 3-32 7-6 when to use, 1-9, 2-2 displaying name of, 2-7 Installing drives, 1-6 DECwindows software, 3-20 names, 3-6 optional components, 3-11 preparing for installations, Installing the operating 2-7 system, 3-1 C2 systems, 2-4 I______________________________ cautions and restrictions, InfoServer devices, 1-5 2-1 booting Standalone BACKUP, information needed for 3-2 VAXcluster systems, 2-4 creating the system disk preparing for, 2-4 from, 3-10 recording log of, 2-3 Initial software load (ISL) VMSINSTAL option G warning, 2-2 See ISL ISL (initial software load) Installation booting, 3-3 of layered products, 4-9, 8-15 K______________________________ Installation procedure, 1-9 Keyboards See also Postinstallation customizing, 9-3 tasks layout, 9-2 See also Preinstallation DECwindows keymap, 9-4 to tasks 9-8 booting standalone BACKUP, model numbers, 9-3 3-2 Keymap names booting system disk after determining, 9-3 transferring required save KFQSA controller set, 3-8 upgrade requirement, 5-16 computer-specific instructions, 3-1 L______________________________ rebooting the system, 3-35 Layered products registering licenses, 3-25 availability of, 1-4 registering OpenVMS VAX effect of upgrade on, 5-6 license, 3-36 installing after OpenVMS VAX running AUTOGEN, 3-34 installation, 4-9 Index-5 Layered products (cont'd) LMF (License Management installing after upgrade, facility) (cont'd) 8-15 using during an installation, LIBDECOMP.COM procedure, 8-10 3-30 running after an installation Volume Shadowing software, , 4-8 B-14 running after an upgrade, Local Area VAXcluster 8-10 information needed to install Libraries , 2-5 decompressing after an upgrade requirements, 5-5 installation, 4-7 Local drives, 1-5 decompressing after an LURT (License Unit Requirement upgrade, 8-9, 8-10 Table), B-4 Library save set contents, D-1 M______________________________ installing, 3-12, 7-14 Magnetic tape kit License Management facility contents, 1-7 See LMF Manual boot License Unit Requirement Table after running AUTOGEN, 7-29 See LURT during an upgrade, 7-11, Licenses 7-24 See also LMF enabling for an upgrade, See also PAK 5-18 error messages, 3-9 Memory requirements registering after an restrictions, 1-4 installation, 4-3 MicroVAX computers registering during an booting from [SYS0], 7-24 installation, 3-25, 3-29 booting from [SYSF], 7-20, registering during an upgrade C-1 , 7-26 Minimum startup required for upgrades, 5-2 configuring devices after, types of, 3-25 to 3-28 7-3 Limits setting before an upgrade, minimum values, 5-14 5-15 LMF (License Management Mixed-interconnect VAXcluster facility) information needed to install error messages, 3-29 , 2-5 example of registration, B-2 upgrade requirements, 5-5 license registration Mixed-version cluster procedure, B-1 upgrading to, 6-5 to 6-7 system integrated product MODPARAMS.DAT (parameter file) licenses, B-14 , 4-10 entering parameters in, 5-17 modifying, 8-5 Index-6 MODPARAMS.DAT (parameter file) OpenVMS versions (cont'd) computer support, B-2 modifying values, 8-16 required for upgrades, 5-6 Monochrome workstations, 9-3 Operator logs Multiversion upgrade, A-2 effect of upgrades on, 5-4 Optional components N choosing, 2-8 _______________________________ installing on alternate disks NETCONFIG.COM procedure , 3-12 running after an installation installing with DECW$TAILOR, , 4-5 3-12 Network installing with VMSTAILOR, See also DECnet for OpenVMS 3-12 requirements for an upgrade, selecting, 3-12 5-20 selecting during an restriction on upgrades, 5-4 installation, 3-11 Networks selecting during an upgrade, configuring the system for, 7-13 4-5 sizes, 3-11 NEW_OVER files, F-2 Optional save set NEW_UNDER files, F-3 contents, D-3 installing, 3-13, 7-14 O______________________________ upgrading, 7-13 OPCOM stopped during an upgrade, P______________________________ 7-11 Page and swap files OpenVMS library files locating, 2-5 choosing during an upgrade, Page files 7-14 checking size, 5-13, 8-4 OpenVMS Management Station controlling size of, H-5 installing, 3-14, 7-15 modifying size, 5-13, 8-3 postupgrade tasks, 8-14 purged during an upgrade, OpenVMS optional components 7-19 See Optional components recommended location, 5-12 OpenVMS RMS Journaling license size required for an upgrade, registering after an 5-12 installation, 4-3 PAK (Product Authorization registering during an upgrade Key) , 7-26 registering after an OpenVMS VAX distribution media installation, 4-3 loading, 3-6 registering during an upgrade OpenVMS VAX license , 7-26 registering after an registering during installation, 4-3 installation, 3-29 Index-7 Passwords Postinstallation tasks for system accounts, 2-7 (cont'd) setting during tuning the system with installation, 3-21 AUTOGEN, 4-10 forgotten, 3-37, 7-31 Postupgrade tasks minimum length, 3-21 adding and removing files, modifying during upgrade 8-12 procedure, 7-9 backing up console media, requirements, 7-9 8-16 Phase 1 of upgrade procedure, backing up system disk, 8-16 7-9 changing MODPARAMS.DAT, 8-5 Phase 2 of upgrade procedure, checking system file sizes, 7-21 8-4 Phase 3 of upgrade procedure, creating standalone BACKUP, 7-23 8-16 Phase 4 of upgrade procedure, customizing DECwindows 7-23 support, 8-14 Phase 5 of upgrade procedure, decompressing system 7-25 libraries, 8-9 to 8-11 Phase 6 of upgrade procedure, examining command procedure 7-25 templates, 8-4 Postinstallation tasks, 4-1 increasing space on the adjusting system parameters, system disk, 8-12 4-4 installing layered products, backing up the system disk, 8-15 4-3, 4-10 modifying size of dump file, configuring DECnet, 4-5 8-3 creating standalone BACKUP, modifying size of page file, 4-3 8-3 customizing DECwindows modifying size of swap file, support software, 9-1 8-3 customizing the system, 4-3 purging system files, 8-13 decompressing system replacing SYSUAF.DAT, 8-3 libraries, 4-7 replacing VMS$AUDIT_ editing startup procedures, SERVER.DAT, 8-3 4-4 running AUTOGEN, 8-16 installing layered products, running UETP, 8-12 4-9 tuning the system with registering licenses, 4-3 AUTOGEN, 8-16 removing unwanted system updating console media, 8-5 files, 4-9 using VMSTAILOR, 8-12 running UETP, 4-6 Preinstallation tasks, 2-4 setting up user accounts, collecting information, 2-7 4-4 determining HSC name, 2-7 Index-8 Preinstallation tasks (cont'd) Queues (cont'd) preparing for VAXcluster stopping before an upgrade, environments, 2-4 5-20 preparing tape drives, 2-6 Quorum Preupgrade tasks, 5-1 maintaining during rolling analyzing and repairing the upgrades, 6-5 system disk, 5-12 Quorum disk, 2-5 backing up console media, QUORUM parameter 5-9 setting for concurrent backing up the system disk, upgrades, 6-3 5-9 Quotas checking page file size, checked during an upgrade, 5-12 7-11 configuring devices, 7-3 minimum values, 5-14 creating standalone BACKUP, 5-10 R______________________________ preparing DECnet for OpenVMS, Rebooting 5-18 after an installation, 3-35 preparing the system disk, manual, 5-18 5-10 Recording an installation, 2-3 preventing interactive logins Removing unwanted system files , 5-18 , 4-9 running AUTOGEN, 5-8 Required save set setting system parameters, transferring to the system 5-15 disk, 3-6 stopping queues, 5-20 Restart Products (VMSINSTAL) enabling automatic, 5-18 specifying for an upgrade, Restrictions 7-7 for installations, 2-2 PURGE command, 8-13 Rights database Purging system files, 8-13 creating during an installation, 3-23 Q______________________________ RIGHTSLIST.DAT file Queue database creating during an creating after an upgrade, installation, 3-23 4-4 RMS Journaling for OpenVMS Queue manager license restoring preferred node registering during an list, 8-2 installation, 3-31 Queues Rolling upgrades, 6-2 requirements for an upgrade, effect on SYSUAF.DAT, 8-3 5-20 effect on SYSUAF.DAT file, stopping batch/print, 5-20 5-11 Index-9 Rolling upgrades (cont'd) Source drives, 1-5 maintaining cluster quorum, definition, 7-3 6-5 requirement for VAXcluster restrictions, 6-2, 6-4 upgrade, 6-6 source drive requirement, SPDs (Software Product 6-6 Descriptions) upgrade procedures, 6-5 to location on the distribution 6-6 kit, 1-8 STABACKIT.COM (procedure to S______________________________ create standalone BACKUP), Satellites nodes 5-10 upgrade requirements, 5-5 Standalone BACKUP Save sets booting, 3-1 installing on an alternate booting from InfoServers, disk, 5-21 3-2 location on magnetic tape, booting from tape cartridges, 1-7 3-2 required location, 1-6, 2-2 booting on VAX 9000 computers tape cartridge containing, , 3-3 3-2 creating a kit, 4-3 transferring to the system creating after an upgrade, disk, 3-5 8-16 SCSNODE parameter, 5-15 creating before an upgrade, SCSSYSTEMID parameter, 5-15 5-10 Selecting optional components, loading media, 3-2 7-13 locating on distribution kit, Server 3-2 customizing the DECwindows, on multiple volumes, 3-2 9-1 upgrade requirements, 5-10 Shared memory using alternative backup restrictions, 1-4 procedure, 3-4 Shutdowns Startup files before an upgrade, 5-11 editing after an installation Site-specific command , 4-3 procedures STARTUP_P1 parameter restored during an upgrade, setting to MIN, 5-15 7-25, 8-4 Swap files Snapshot facility checking size, 8-4 resetting the BOOT_STYLE controlling size of, H-5 parameter, 5-16 creating, 5-13 modifying size, 8-3 Software Product Descriptions purged during an upgrade, (SPDs) 7-19 See SPDs recommended location, 5-12 Index-10 SWAPFILES.COM procedure SYSTEM account (cont'd) executing to change system quotas, 5-14 file sizes, 8-4 setting passwords, 3-21 to check or modify page file System disks, 1-5 size, 5-13 analyzing and repairing, to create swap file, 5-13 5-12 SYCONFIG.COM procedure backing up, 8-16 editing after an installation backing up after an , 4-4 installation, 4-3, 4-10 SYLOGICALS.COM procedure backing up before an upgrade, editing after an installation 5-9 , 4-4 booting a backup copy, 5-11 SYLOGIN.COM procedure booting after an installation editing after an installation , 3-35 , 4-4 booting after transferring SYS$TIMEZONE.DAT file, 7-12 required save set, 3-8 [SYSF] directory checking amount of free space booting from during an on, 4-7 upgrade, 7-20, C-1 CLUSTER_SIZE parameter, 3-7 booting from during upgrade, creating, 3-5 7-2 customizing with DECW$TAILOR, command to boot MicroVAX and 4-9, 10-11, 10-12 VAXstation computers from, customizing with VMSTAILOR, 7-20 4-9, 8-12, 10-1 [SYSF] directory tree dealing with limited space, built by upgrade procedure, H-1, H-3 7-12 disk space needed to run deletion of, 7-25 UETP, 4-6, 8-12 SYSGEN parameters free space needed for an See System parameters upgrade, 5-13 SYSGEN utility free space needed to ALLOCLASS parameter, 2-5 decompress libraries, configuring devices, 7-3 4-7 using to connect console, preparing for an upgrade, 8-6 5-10 SYSTARTUP_VMS.COM procedure preparing for installations, editing after an installation 2-7 , 4-4 removing unwanted files from, editing to control DECnet 4-9 Phase IV, 4-6 required location during an SYSTEM account upgrade, 7-25 forgotten passwords, 3-37, restrictions, 1-4 7-31 RZ24, H-4 limits, 5-14 space requirements, H-2 Index-11 System disks (cont'd) Tape cartridge (cont'd) specifying volume label for, containing standalone BACKUP, 3-10 3-2 System files Tape drives modifying, 8-4 preparing for an installation purging, 8-13 , 2-6 System Generation utility selecting for an installation See SYSGEN utility. , 2-6 System hang, 7-30 Target disk System libraries using backup copy for, 5-9 decompressing, 3-24, 8-9 to Target drives, 1-6 8-11 definition, 7-3 sizes after decompressing, TCP/IP software 8-9 See Digital TCP/IP Services System parameters for OpenVMS adjusting, 4-4 Time generated by AUTOGEN feedback format for entering, 7-8 , 5-8 Time zones requirements for an upgrade, updating during an 5-4, 5-15 installation, 3-32 System password dictionary updating during an upgrade, restoring after an upgrade, 7-27 8-13 TK50 tape kit System shutdowns contents of, 1-7 after an installation, 3-35 Transferring save sets to the System time, 4-2, 8-2 system disk, 3-5 SYSTEST account setting passwords, 3-21 U______________________________ SYSTEST_CLIG account UAF (user authorization file) disabling during an effect of rolling upgrades installation, 3-21 on, 5-11, 8-3 SYSUAF.DAT file purged during an upgrade, See UAF 7-19 replacing after upgrade, 8-3 T______________________________ required location, 5-11 Tailored system disks UETP (User Environment Test See DECW$TAILOR utility Package) See VMSTAILOR utility disk space needed to run, Tailoring 4-6, 8-12 on small system disks, H-4 when to run, 4-6, 8-12 Tape cartridge UPDATE_CONSOLE.COM procedure containing save sets, 3-2 running after an upgrade, 8-8 Index-12 Upgrade and installation Upgrade procedure (cont'd) supplements files purged during, 7-19 using, 2-3, 3-1 interrupting before Phase 1, Upgrade preparation, 5-17 7-8 Upgrade procedure, 1-12 license requirements, 7-26 automatic update of console loading OpenVMS VAX media, 5-10 distribution media, 7-4 booting from console media, manual reboot after, 7-29 7-11 manual reboot from [SYS0], booting from [SYSF], 7-20 7-24 booting manually during, merging directory trees, 7-11 7-23 building [SYSF] directory, modifying console media, 7-12 5-18 cautions and restrictions, modifying console media to 5-1 boot from [SYSF], 7-11 choosing optional OpenVMS modifying passwords, 7-9 components, 7-14 OpenVMS version requirement, concurrent upgrades, 6-2 5-6 console media required, 5-7 Phase 1, 7-9 conversion of VAXVMSSYS.PAR, Phase 2, 7-21 7-25 Phase 3, 7-23 correcting directory pointers Phase 4, 7-23 , 7-24 Phase 5, 7-25 deletion of [SYSF] directory Phase 6, 7-25 tree, 7-25 processing user files, 7-23 disk space needed for page recording logs, 5-7 files, 5-12 registering licenses, 7-26 disk space requirement, 5-13 required location of save effect on accounting logs, sets, 5-5 5-4 required location of the effect on command procedures, system disk, 7-25 8-4 requirement for shared dump effect on layered products, files, 5-12 5-6 requirements, 5-24 effect on MODPARAMS.DAT, 8-5 restoring original dddGEN, effect on operator logs, 5-4 7-24 enabling automatic restart, restoring original DEFBOO, 5-18 7-24 enabling manual reboot, 5-18 rolling upgrades, 6-4 error entering device code, adding a new CPU, 6-7 7-7 running AUTOGEN, 7-29 files deleted by, 7-12, selecting optional components 7-23, 7-25 , 7-13 Index-13 Upgrade procedure (cont'd) VAXcluster quorum (cont'd) shared dump files, 5-6 maintaining during rolling system files renamed by, upgrades, 6-5 7-12 VAXcluster QUORUM parameter time zones, 7-27 setting for concurrent using a printer to record upgrades, 6-3 output, 5-7 VAXcluster upgrades VMSINSTAL option G warning, See Concurrent upgrades 5-5 See Rolling upgrades when to use, 1-12, 2-2 VAXft computers User authorization file booting from [SYSF], C-1 See UAF VAXstation computers User files booting from [SYS0], 7-24 processed during an upgrade, booting from [SYSF], 7-20, 7-23 C-1 VAXVMSSYS.PAR parameter files V______________________________ conversion, 7-25 VAX computers VMB.EXE booting from [SYSF], C-1 to copying to console media, C-9 8-5 OpenVMS VAX support for, B-2 VMS$AUDIT_SERVER.DAT file VAXcluster environments required location, 5-11 building, 4-3 VMSINSTAL command procedure cluster group numbers, 2-6 invoking for upgrade, 7-5 cluster passwords, 2-6 option G warning, 2-2 DECwindows support components VMSTAILOR utility for, 3-15, 7-16 using on a small system disk, information required for an H-6 installation, 2-4 using to install optional problem upgrading, 7-30 components, 3-12, 7-13, types of, 2-5 10-5 upgrade requirement for using to remove files from a shared dump files, 5-12 system disk, 4-9, 8-12, VAXcluster license 10-3 registering after an Volume label installation, 4-3 specifying during an registering during an installation, 3-10 installation, 3-31 Volume shadowing registering during an upgrade requirements for an upgrade, , 7-26 5-19 VAXcluster quorum Volume Shadowing license maintaining during an upgrade registering after an , 7-30 installation, 4-3 Index-14 Volume Shadowing license (cont'd) W______________________________ registering during an WELCOME.TXT file installation, 3-31 updating, 8-4 registering during an upgrade Workstations , 7-26 customizing, 9-3 VOTES parameter checking for rolling upgrades X______________________________ , 6-5 X terminals setting for concurrent DECwindows support components upgrades, 6-3 for, 3-15, 7-16 upgrade requirement, 6-3 Index-15