                                           H                     ____________________________________________________D                     OpenVMS VAX Version 6.2 Upgrade and Installation                     Manual    -                     Order Number: AA-PV6WC-TE                          May 1995  F                     This manual provides step-by-step instructions forF                     upgrading and installing the OpenVMS VAX operating                     system.               H                     Revision/Update Information:  This manual supersedesA                                                   the OpenVMS VAX I                                                   Version 6.1 Upgrade and F                                                   Installation Manual.  I                     Operating System and Version: OpenVMS VAX Version 6.2       1                     Digital Equipment Corporation *                     Maynard, Massachusetts                 J           ________________________________________________________________           May 1995  @           Digital Equipment Corporation makes no representationsA           that the use of its products in the manner described in B           this publication will not infringe on existing or futureB           patent rights, nor do the descriptions contained in thisB           publication imply the granting of licenses to make, use,>           or sell equipment or software in accordance with the           description.  ?           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.  D            Digital Equipment Corporation 1995. All rights reserved.  ;           The following are trademarks of Digital Equipment C           Corporation: Bookreader, CDA, CI, DEC, DECdtm, DEC PHIGS, E           DEC RALLY, DECnet, DECtp, DECwindows, DEQNA, Digital, EDCS, A           HSC, InfoServer, LAT, MicroVAX, MicroVAX II, MUXserver, >           OpenVMS, OpenVMS Volume Shadowing, PATHWORKS, Q-bus,=           Rdb/VMS, ULTRIX, VAX, VAX 4000, VAX 6000, VAX 8200, E           VAX 8250, VAX 8300, VAX 8350, VAX 8600, VAX 8650, VAX 8840, C           VAX 9000, VAX-11/730, VAX-11/750, VAX-11/780, VAX-11/785, ?           VAX C, VAXcluster, VAXELN, VAXft, VAXlink, VAXserver, ?           VAXset, VAXstation, VIDA, VMS, WPS-PLUS, XUI, and the            DIGITAL logo.   3           The following are third-party trademarks:   ;           Adobe, Adobe Illustrator, Display POSTSCRIPT, and ?           POSTSCRIPT are registered trademarks of Adobe Systems            Incorporated.   D           Microsoft and MS-DOS are registered trademarks and Windows2           is a trademark of Microsoft Corporation.  :           Motif is a registered trademark of Open Software           Foundation, Inc.  >           OSI is a registered trademark of CA Management, Inc.  :           X/Open is a trademark of X/Open Company Limited.  @           All other trademarks and registered trademarks are the/           property of their respective holders.   E                                                                ZK6423   /           This document is available on CD-ROM.   D           This document was prepared using VAX DOCUMENT Version 2.1.                                Send Us Your Comments   C               We welcome your comments on this or any other OpenVMS H               manual. If you have suggestions for improving a particularD               section or find any errors, please indicate the title,A               order number, chapter, section, and page number (if E               available). We also welcome more general comments. Your C               input is valuable in improving future releases of our                documentation.  @               You can send comments to us in the following ways:  E               o  Internet electronic mail: openvmsdoc@zko.mts.dec.com   F               o  Fax: 603-881-0120 Attn: OpenVMS Documentation, ZKO3-4                  /U08                  o  Online form  C                  Print or edit the online form SYS$HELP:OPENVMSDOC_ @                  COMMENTS.TXT. Send the completed online form byE                  electronic mail to our Internet address, or send the E                  completed hardcopy form by fax or through the postal                   service.   4                  Please send letters or the form to:  .                  Digital Equipment Corporation&                  OpenVMS Documentation0                  110 Spit Brook Road, ZKO3-4/U08'                  Nashua, NH  03062-2698                   USA                 Thank you.                  I                                                                       iii                    )     How To Order Additional Documentation   C           Use the following table to order additional documentation 9           or information. If you need help deciding which ?           documentation best meets your needs, call 800-DIGITAL            (800-344-4825).                                                                                    iv                                 C   _________________________________________________________________   C                                                            Contents       C   Preface...................................................   xvii   4   1  Overview of Installation and Upgrade Procedures  C               Overview......................................    1-1 C               Cautions, Restrictions, and Changes...........    1-2 C                   Introduction..............................    1-2 C                   Cautions..................................    1-2 C                   Restrictions..............................    1-4 C                   Changes Since OpenVMS Version 6.1.........    1-4 C               Definitions: A Few Key Terms..................    1-6 C               Locating Files on the Distribution Media......    1-8 C                   Introduction..............................    1-8 C                   On Magnetic Tape..........................    1-8 C                   On Tape Cartridges........................    1-8 C                   On Compact Disc...........................    1-9 <                   DECamds and Monitoring Performance HistoryC                   (MPH) Files...............................    1-9 C                   Software Product Descriptions (SPDs)......    1-9 C               Installation Procedure........................   1-12 C                   What Happens During an Installation.......   1-12 C                   When to Perform an Installation...........   1-12 -                   How to Use the Installation C                   Documentation.............................   1-13 C               Upgrade Procedure.............................   1-15 C                   What Happens During an Upgrade............   1-15 C                   When to Perform an Upgrade................   1-15 C                   Restrictions..............................   1-16 C                   How to Use the Upgrade Documentation......   1-16 C                   Where to Go Next..........................   1-16         C                                                                   v                    -     2  Before Installing OpenVMS VAX Software   E                 Overview......................................    2-1 E                 Cautions and Restrictions.....................    2-2 E                     Introduction..............................    2-2 E                     Cautions..................................    2-2 E                     Restrictions..............................    2-2 E                 Are You Ready to Install?.....................    2-4 E                     Introduction..............................    2-4 E                     Hardware Components.......................    2-4 E                     Software Components.......................    2-4 E                 Preparing for an Installation.................    2-6 E                     Introduction..............................    2-6 E                     Preparing for a C2 System.................    2-6 E                     Preparing for a VAXcluster Environment....    2-6 E                     Preparing Tape and Disk Drives............    2-8 3                     Information You Need During the E                     Installation..............................    2-9 E                 Preinstallation Checklist.....................   2-15 E                     Introduction..............................   2-15 E                     Did You . . ..............................   2-15 E                     Where to Go Next..........................   2-17   2     3  Installing the OpenVMS VAX Operating System  E                 Overview......................................    3-1 E                 Booting Standalone BACKUP.....................    3-2 E                     Introduction..............................    3-2 E                     Where to Find Standalone BACKUP...........    3-2 E                     Booting from Tape Cartridge...............    3-2 E                     Where to Go Next..........................    3-3 E                     Booting from an InfoServer Device.........    3-3 E                     Where to Go Next..........................    3-5 E                 Creating the System Disk......................    3-6 E                     Overview..................................    3-6 E                     Step 1: Determine Device Names............    3-6 E                     Step 2: Load Distribution Media...........    3-6 <                     Step 3: Transfer VMS062.B to Your SystemE                     Disk......................................    3-7 E                     Step 4: Boot the New System Disk..........    3-8 E                     Step 5: Specify the Volume Label..........   3-10 E                     Step 6: Specify the Source Drive..........   3-10 3                     Step 7: Select Optional OpenVMS E                     Components................................   3-11        vi                   9                         Step 8: Choose DECwindows Support I                         Options...................................   3-16 I                         Step 9: Verify Your Choices...............   3-19 I                         Step 10: Install OpenVMS Options..........   3-19 I                         Where to Go Next..........................   3-20 ;                         Step 11: Install DECwindows Support I                         Software..................................   3-20 I                     Joining a VAXcluster Environment..............   3-22 I                         Introduction..............................   3-22 I                         VAXcluster or Standalone?.................   3-22 I                         Determine the Type of VAXcluster..........   3-24 I                         CI-Only VAXcluster........................   3-24 9                         Local Area and Mixed-Interconnect I                         VAXcluster................................   3-25 A                     Setting Passwords and SCSNODE and SCSSYSTEMID I                     Parameters....................................   3-28 I                         Introduction..............................   3-28 I                         How to Enter Passwords....................   3-28 8                         Entering SCSNODE and SCSSYSTEMIDI                         Parameters................................   3-30 I                     Postinstallation Tasks Described..............   3-31 I                         Introduction..............................   3-31 I                         Sample Message............................   3-31 I                         Where to Go Next..........................   3-32 I                     Registering Licenses..........................   3-33 I                         Introduction..............................   3-33 I                         How to Register Your Licenses.............   3-33 I                         Where to Find More Information............   3-33 I                         Types of Licenses.........................   3-34 I                         How to Register OpenVMS VAX Licenses......   3-37 I                         Beginning the Licensing Procedure.........   3-39 9                         How to Register System Integrated I                         Products..................................   3-39 I                         Where to Go Next..........................   3-40 I                     Running AUTOGEN...............................   3-41 I                         Introduction..............................   3-41 I                         How AUTOGEN Works.........................   3-41                 I                                                                       vii                    #     4  After Installing OpenVMS VAX   E                 Overview......................................    4-1 E                 Verifying System Time.........................    4-2 E                     Introduction..............................    4-2 E                     How to Reset System Time..................    4-2 E                     Compensating for Time Zones...............    4-2 E                 Registering Your Licenses.....................    4-3 E                     Background................................    4-3 E                     Where to Find More Information............    4-3 E                 Backing Up Your System Disk...................    4-4 E                     Background................................    4-4 E                     Where to Find More Information............    4-4 E                 Customizing the System........................    4-5 E                     Background................................    4-5 E                     Where to Find More Information............    4-5 E                 Configuring and Starting DECnet...............    4-7 E                     Introduction..............................    4-7 E                     Configure Your System.....................    4-7 E                     Edit SYSTARTUP_VMS........................    4-7 E                 Testing the System with UETP Software.........    4-9 E                     Background................................    4-9 E                     Where to Find More Information............    4-9 E                 Decompressing System Libraries................   4-10 E                     Background................................   4-10 E                     How to Decompress Libraries...............   4-12 E                 Removing or Adding OpenVMS Files..............   4-14 E                     Background................................   4-14 E                     Where to Find More Information............   4-14 E                 Backing Up the Customized System Disk.........   4-15 E                     Background................................   4-15 E                     Where to Find More Information............   4-15 E                 Running AUTOGEN...............................   4-16 E                     Background................................   4-16 E                     When to Run AUTOGEN.......................   4-16 E                     What to Do Next...........................   4-17 E                 Postinstallation Checklist....................   4-18 E                     Introduction..............................   4-18 E                     Did You . . ..............................   4-18                  viii                   0         5  Before Upgrading OpenVMS VAX Software  I                     Overview......................................    5-1 I                     Cautions and Restrictions.....................    5-2 I                         Introduction..............................    5-2 I                         Cautions..................................    5-2 I                         Restrictions..............................    5-7 I                     Are You Ready to Upgrade?.....................    5-9 I                         Introduction..............................    5-9_I                         Hardware Components.......................    5-9 I                         Software Components.......................   5-10TI                     Examining AUTOGEN Feedback Data...............   5-11vI                         Background................................   5-11lI                         How to Check Feedback Data................   5-11 I                     Backup Tasks..................................   5-13 I                         Introduction..............................   5-13 I                         How to Back Up the System Disk............   5-13 I                         How to Back Up Console Media..............   5-13 I                     Preparing Your System Disk....................   5-15 I                         Introduction..............................   5-15MI                         Create a Nonshadowed System Disk..........   5-15_;                         Boot the Backup Copy of Your System I                         Disk......................................   5-15tA                         Copy UAF and Auditing Files to the SystempI                         Disk......................................   5-16,I                         Rename the System Dump File...............   5-16 I                         Analyze the System Disk...................   5-16 I                         Check Page and Swap Files.................   5-17,I                         Check for Free Blocks.....................   5-18tI                         Check Quotas and Limits...................   5-18 I                         Set System Parameters.....................   5-19pI                         Check AGEN$INCLUDE Files..................   5-22s9                         Add Modified System Parameters toCI                         MODPARAMS.DAT.............................   5-22nI                     Preparing the System..........................   5-23rI                         Enable Auto Restart or Manual Reboot......   5-23SI                         Shut Down and Reboot the System...........   5-23 I                         Prevent Interactive Logins................   5-23 I                         Check for DECnet for OpenVMS..............   5-24AI                         Check for Volume Shadowing................   5-24sI                         Stop Queues...............................   5-25 I                     Gathering Information for the Upgrade.........   5-26II                         Introduction..............................   5-26rI                         Information You Need......................   5-26   I                                                                        ix  r  f              E                     Where to Go Next..........................   5-30 E                 Preupgrade Checklist..........................   5-31aE                     Introduction..............................   5-31eE                     Did You . . ..............................   5-31 E                     Where to Go Next..........................   5-34   )     6  Upgrading a VAXcluster Environment6  E                 Overview......................................    6-1sE                 Concurrent and Rolling Upgrades...............    6-2 E                     Introduction..............................    6-2uE                     Concurrent Upgrades.......................    6-2hE                     Rolling Upgrades..........................    6-2nE                 Concurrent Upgrades...........................    6-3hE                     Introduction..............................    6-3 E                     How to Perform a Concurrent Upgrade.......    6-3nE                 Rolling Upgrades..............................    6-5 E                     Introduction..............................    6-5 E                     Restrictions..............................    6-5 E                     How to Perform a Rolling Upgrade..........    6-6 5                     Adding an OpenVMS VAX Version 6.2 E                     Supported CPU.............................    6-8   1     7  Upgrading the OpenVMS VAX Operating Systemr  E                 Overview......................................    7-1hE                 Preparing to Boot from [SYSF].................    7-2aE                     Introduction..............................    7-2oE                     Modifying Boot Command Procedures.........    7-2 E                 Configuring Devices...........................    7-4 E                     Introduction..............................    7-4UE                     How to Configure Devices..................    7-4 E                 Beginning the Upgrade Procedure...............    7-5 E                     Overview..................................    7-5lE                     Step 1: Load Distribution Media...........    7-5n1                     Step 2: If Upgrading from theeE                     InfoServer................................    7-52E                     Step 3: Start VMSINSTAL...................    7-6 E                     Step 4: Back Up the System Disk...........    7-7_E                     Step 5: Specify the Source Drive..........    7-8 E                     Step 6: Enter Product Name................    7-9.E                     Step 7: Mount the First Volume............    7-9eE                     Step 8: Checking for DECnet Products......   7-10.         x. .  .              I                         Step 9: Monitor Messages from VMSINSTAL...   7-10 I                         Step 10: Verify Date and Time.............   7-11 I                         Where to Go Next..........................   7-11 I                     Upgrade Phase 1...............................   7-12 I                         Overview..................................   7-12iI                         Step 1: Specify Type of Upgrade...........   7-12sI                         Step 2: Enter Passwords...................   7-12.I                         Step 3: Choose Boot Method................   7-14.I                         Step 4: File Cleanup......................   7-15.7                         Step 5: Select Optional OpenVMS.I                         Components................................   7-16g9                         Step 6: Choose DECwindows Support.I                         Options...................................   7-20iI                         Step 7: Verify Your Choices...............   7-23.I                         Step 8: Shut Down Your System.............   7-23.I                         Step 9: Reboot the System.................   7-23 I                         Step 10: Verify System Time...............   7-25oI                     Upgrade Phase 2...............................   7-26cI                         What the Procedure Does...................   7-26DI                         What You Do...............................   7-26UI                     Upgrade Phase 3...............................   7-29.I                         What the Procedure Does...................   7-29aI                     Upgrade Phase 4...............................   7-30.I                         What the Procedure Does...................   7-30 I                         What You Do...............................   7-30SI                         Where to Go Next..........................   7-31 I                     Upgrade Phase 5...............................   7-32-I                         What the Procedure Does...................   7-32 I                     Upgrade Phase 6...............................   7-33 I                         Introduction..............................   7-33 I                         Restoring System Files....................   7-33 I                         Registering Licenses......................   7-34 I                         Running AUTOGEN...........................   7-35 I                         Shutting Down the System..................   7-35nI                         Booting Voting Nodes......................   7-36cI                         Executing STARTUP.........................   7-36oI                         Logging In................................   7-37 I                         Where to Go Next..........................   7-37D              I                                                                        xi                    "     8  After Upgrading OpenVMS VAX  E                 Overview......................................    8-1 E                 Verifying System Time.........................    8-3 E                     Introduction..............................    8-3 E                     How to Reset System Time..................    8-3 E                     Compensating for Time Zones...............    8-3 E                 Restoring the Preferred Node List.............    8-4 E                     Background................................    8-4 E                     To Restore the Preferred Node List........    8-4 (                 Replacing SYSUAF.DAT andE                 VMS$AUDIT_SERVER.DAT..........................    8-5.E                     Background................................    8-5.E                     How to Replace Updated Files..............    8-5vE                 Examining AGEN$PARAMS.REPORT..................    8-6.E                     Background................................    8-6.E                     To View This Report.......................    8-6.E                 Checking the Size of System Files.............    8-7sE                     Background................................    8-7iE                     To Modify Size of System Files............    8-7YE                 Examining Your Command Procedures.............    8-8.E                     Background................................    8-8.E                     Files to Examine..........................    8-8.E                 Changing MODPARAMS.DAT........................    8-9.E                     Background................................    8-9 E                     What to Look for..........................    8-9 E                 Updating Your DECnet Phase IV Configuration...   8-10dE                     Introduction..............................   8-10.E                     Check Network Security Level..............   8-10.8                     Run the Network Configuration UpdateE                     Command Procedure.........................   8-11o9                     Run the Cluster Member Update Command E                     Procedure.................................   8-14oE                 Converting Your Network Proxy Database........   8-15oE                     Background................................   8-15 4                     How to Convert the Network ProxyE                     Database..................................   8-15 E                     Save Old Database.........................   8-16.E                 Updating Your Console Media...................   8-17.>                     VAX 8530, 8550, 8810 (8700), 8820-N (8800)E                     Computers.................................   8-17.;                     VAX 11/730, 750, 780, 785 and VAX 8200,NE                     8250, 8300, 8350, 8600, 8650 Computers....   8-20.E                     VAX 9000 Computers........................   8-21.       xii. .  .              I                     Decompressing the System Libraries............   8-22 I                         Background................................   8-22 I                         How to Decompress Libraries...............   8-23oI                     Testing the System with UETP..................   8-26 I                         Background................................   8-26 I                         Where to Find More Information............   8-26 I                     Increasing Free Space on the System Disk......   8-27eI                         Background................................   8-27 I                         Using VMSTAILOR and DECW$TAILOR...........   8-27 I                         Purging System Files......................   8-27 I                     Restoring Your System Password Dictionary.....   8-29 I                         Background................................   8-29 I                         How to Restore Your Passwords.............   8-29 I                     Customizing DECwindows Support................   8-30 I                         Customize DECwindows Support Software.....   8-30.I                         How to Customize DECwindows Support.......   8-30e;                     Preparing to Run the OpenVMS ManagementnI                     Station.......................................   8-31 I                         Background................................   8-31 I                         How to Prepare Your Systems...............   8-31 I                     Backing Up the System Disk....................   8-32 I                         Background................................   8-32iI                         For More Information......................   8-32 I                     Running AUTOGEN...............................   8-33iI                         Background................................   8-33SI                         When to Run AUTOGEN.......................   8-33TI                     Postupgrade Checklist.........................   8-35.I                         Introduction..............................   8-35.I                         Did You . . ..............................   8-35n  2         9  Customizing DECwindows Support Software  I                     Overview......................................    9-1.I                     Customizing the Server Startup................    9-2fI                         Note......................................    9-2.I                         Assumptions...............................    9-2.I                         How to Override Incorrect Assumptions.....    9-3.I                     Using DEC TCP/IP Services for OpenVMS.........   9-10.I                         Overview..................................   9-10.I                         For More Information......................   9-10 I                     Using Other Transports with DECwindows........   9-11 I                         Introduction..............................   9-11 I                         Writing a Transport Interface.............   9-11     I                                                                      xiii  e  p              6                     Installing the Transport InterfaceE                     Image.....................................   9-11 E                 Using the Example Transport...................   9-12oE                     Introduction..............................   9-12 E                     How to Use the Example Transport..........   9-12   '     10  Using VMSTAILOR and DECW$TAILOR   E                 Overview......................................   10-14E                 Using VMSTAILOR...............................   10-24E                     When to Use VMSTAILOR.....................   10-24E                     How VMSTAILOR Works.......................   10-24E                     Removing OpenVMS VAX Files................   10-44E                     Adding OpenVMS VAX Files..................   10-54E                     Sample Session............................   10-84E                 Using DECW$TAILOR.............................  10-114E                     When to Use DECW$TAILOR...................  10-114E                     How DECW$TAILOR Works.....................  10-114E                     DECwindows Files You Can Tailor...........  10-12rE                     Removing DECwindows Files.................  10-12.E                     Adding DECwindows Files...................  10-13rE                     Sample Session............................  10-15i       A  License Management Notes   E                 Overview......................................    A-1 E                 Registering Your Licenses.....................    A-2.E                     When to Register..........................    A-2.E                     How to Register...........................    A-2.8                 Using the License Unit Requirement TableE                 (LURT)........................................    A-5CE                     Introduction..............................    A-5 E                     License Unit Requirement Table............    A-5aE                 License Management Facility Notes.............   A-13 E                     Common Concerns and Questions About LMF...   A-13 E                 Volume Shadowing for OpenVMS License..........   A-16 E                     When to Register..........................   A-16 E                     Volume Shadowing Phase I and Phase II.....   A-16 E                     Types of Licenses.........................   A-16 E                 Other System Integrated Product Licenses......   A-17                xiv     n              0         B  Booting from [SYSF] During an Upgrade  I                     Booting Procedures............................    B-1 I                         Introduction..............................    B-1.I                         MicroVAX and VAXstation Computers.........    B-1UB                         VAX 8530, 8550, 8810 (8700), 8820-N (8800)I                         Computers.................................    B-2eI                         VAX 8820, 8830, and 8840 Computers........    B-2z>                         VAX-11/750, 8200, 8250, 8300, and 8350I                         Computers.................................    B-2 B                         VAX-11/730, 11/780, 11/785, 8600, and 8650I                         Computers.................................    B-4 I                         VAX 6000 Series...........................    B-7 I                         VAX 9000 Series...........................    B-8   *         C  OpenVMS VAX Save Set Subclasses  I                     Overview......................................    C-1nI                     File Subclasses...............................    C-2rI                         Save Set C Subclasses.....................    C-2SI                         Save Set D Subclasses.....................    C-3 I                         Save Set E Subclasses.....................    C-3 I                         Save Set F Subclasses.....................    C-4AI                         Save Set G Subclasses.....................    C-4s  9         D  DECwindows Display Server and Fonts Components.  I                     Overview......................................    D-1.I                     Table of Components...........................    D-2.  '         E  NEW_OVER and NEW_UNDER Filesm  I                     Overview......................................    E-1 I                     Where Files Are Installed.....................    E-2 I                         Introduction..............................    E-2 I                         NEW_OVER Files............................    E-3 I                         NEW_UNDER Files...........................    E-4 I                         Site-Specific Files.......................    E-4r              I                                                                        xvn                   2     F  Preparing to Use OpenVMS Management Station  E                 Overview......................................    F-1 E                 Introduction..................................    F-2uE                     Required Files............................    F-2hE                     Checklist.................................    F-3n  E           Preparing Your Systems..............................    F-5 E                 Overview......................................    F-5 E                 Preparing Your OpenVMS System.................    F-6 E                     Introduction..............................    F-6 E                     Files Installed on OpenVMS................    F-6 E                     Editing System Files......................    F-7 :                     Starting OpenVMS Management Station onE                     Other Nodes...............................    F-7 E                 Preparing Your PC.............................    F-9 E                     Introduction..............................    F-9rE                     Required Memory and Disk Space............    F-9pE                     Media.....................................    F-9 E                     Required Software.........................    F-9 E                     PATHWORKS Client Requirements.............   F-10fE                     Creating the Installation Media...........   F-11   :           Installing the OpenVMS Management Station ClientE           Software on Your PC.................................   F-13 E                 Overview......................................   F-13 E                 Installing the Client Software................   F-14 E                     Installation Procedure....................   F-14 E                     Recovering from Errors....................   F-15rE                 Defining DECnet Nodes.........................   F-16tE                     Introduction..............................   F-16aE                     Procedure for Defining DECnet Nodes.......   F-16pE                     Files Created on the PC...................   F-18nE                 Getting Started...............................   F-19oE                     Introduction..............................   F-19hE                     Accessing Online Help.....................   F-19   E           PATHWORKS Installation Tips and Guidelines..........   F-217E                 Overview......................................   F-21.E                 Introduction..................................   F-22.E                     Required Disk Space ......................   F-22.E                     About Installing and Configuring..........   F-22.E                 Installing Using MS-DOS ......................   F-23pE                 Configuring Using Windows.....................   F-25dE                     Starting Windows..........................   F-28o       xvi. .  .              I                         Deleting a Directory......................   F-28   &         G  Small Capacity System Disks  I                     Overview......................................    G-1.I                     Limited Space Support.........................    G-2 I                         Introduction..............................    G-2 I                         Limited Space Support Option..............    G-2 I                         Configurations Affected...................    G-3 I                         Dealing with a Small System Disk..........    G-3 I                     Tailoring Considerations......................    G-5 I                         Introduction..............................    G-5 I                         Configuration Goals.......................    G-5 ?                         Controlling the Size of Dump, Page, and I                         Swap Files................................    G-6 I                         Make a Backup Copy of Your System Disk....    G-7 I                         Analyze the System Disk...................    G-8 I                         Tailoring Options.........................    G-8 :                     Installing OpenVMS VAX Version 6.2 and<                     DECwindows Motif for OpenVMS VAX VersionI                     1.2-3.........................................   G-10.I                         Introduction..............................   G-10eI                         Install OpenVMS VAX Version 6.2...........   G-10.I                         Install DECwindows Motif .................   G-11.<                     Upgrading to OpenVMS VAX Version 6.2 andI                     DECwindows Motif for OpenVMS Version 1.2-3....   G-12 I                         Introduction..............................   G-12 I                         Upgrading to OpenVMS VAX Version 6.2......   G-12 8                     Managing Single or Small System DiskI                     Systems.......................................   G-14 I                         Introduction..............................   G-14 I                         System Dump File..........................   G-14 I                         Using PAGEFILE.SYS for the Dump File......   G-15 I                         Decompressing Libraries...................   G-15 I                         Disabling Log File Creation...............   G-16 ;                         Accessing Example and Documentation I                         Files.....................................   G-18 I                     Managing Multiple Disk Systems................   G-19 I                         Introduction..............................   G-19 I                         Alternate Page and Swap Files.............   G-19 I                         Copying Dump Files........................   G-19     I                                                                      xviis e  e              E                     Offloading System Logs and Files..........   G-20 E                     Offloading Nonessential Files.............   G-20        Glossary    	     Index.         Examples  E           10-1      Sample VMSTAILOR Session..................   10-8.  E           10-2      Sample DECW$TAILOR Session................  10-15.       Figures   4           1-1       Documentation Used to Perform anE                     Installation..............................   1-14.  4           1-2       Documentation Used to Perform anE                     Upgrade...................................   1-16.  
     Tables  .           2-1       VAXcluster Information forE                     Installations.............................    2-7a  6           3-1       Installation Questions for CI-OnlyE                     VAXcluster................................   3-24i  9           3-2       Installation Questions for Local Area 5                     and Mixed-Interconnect VAXcluster-E                     Environments..............................   3-26-  E           4-1       Sizes of Decompressed System Libraries....   4-10   E           8-1       Sizes of Decompressed System Libraries....   8-22   E           9-1       DECwindows Keymap.........................    9-4   9           A-1       The First VMS or OpenVMS Version That E                     Supports VAX Computers....................    A-3   E           A-2       License Unit Requirement Table (LURT).....    A-6   7           D-1       DECwindows Display Server and Fonts E                     Components................................    D-2   E           F-1       Prerequisite and Optional Software........   F-10   E           F-2       Disk Space Requirements...................   F-22   	     xviiio n  t                        I         _________________________________________________________________   I                                                                   Preface                  INTRODUCTIONF               This manual is your primary source for information aboutB               upgrading and installing the OpenVMS VAX Version 6.2H               operating system. Before you attempt to install or upgradeI               the operating system, be sure to read all the release notes F               and cover letters (if any) included in your distribution               kit.  "         WHO SHOULD USE THIS MANUALD               If you are responsible for installing or upgrading theI               OpenVMS operating system and for performing related backup, G               shutdown, and startup procedures, read this manual before F               you install or upgrade to Version 6.2 of the OpenVMS VAX               operating system..             HOW TO USE THIS MANUALB               If you received factory-installed software with your>               computer, read that user documentation first forG               information about starting up your system. Otherwise, use.F               this manual for step-by-step instructions for performingE               an installation or an upgrade. When the instructions insG               this manual direct you to do so, refer to the upgrade and F               installation supplement for information specific to your               VAX computer.                 H                                                                      xix                         HOW THIS MANUAL IS ORGANIZEDA           The information in this manual is organized as follows:S  >           o  Chapter 1 provides an overview of the upgrade and?              installation procedures. It describes what happensRE              during an installation or an upgrade, lists some changes.D              and restrictions you should be aware of, and refers you.              to the appropriate documentation.  B           o  Chapter 2 describes the tasks you must perform before9              installing the OpenVMS VAX operating system..  >           o  Chapter 3 describes how to install Version 6.2 ofB              the OpenVMS VAX operating system on a VAXcluster or a%              standalone VAX computer.   C           o  Chapter 4 lists the tasks you should perform after you 6              install the OpenVMS VAX operating system.  ;           o  Chapter 5 contains cautions, restrictions, and.@              requirements for upgrading your VAX computer systemE              and tells you how to prepare your system for an upgrade.n  D           o  Chapter 6 contains additional information for upgrading&              a VAXcluster environment.  >           o  Chapter 7 describes the procedure for upgrading a%              standalone VAX computer..  C           o  Chapter 8 lists the tasks you should perform after ther              upgrade..  C           o  Chapter 9 describes how to customize DECwindows device.              support software.  :           o  Chapter 10 describes how to use VMSTAILOR andD              DECW$TAILOR to add or remove optional OpenVMS software.  ?           o  Appendix A provides notes and supplemental license.C              management information to the upgrade and installation.              procedures.  =           o  Appendix B describes how to boot from the [SYSF] ?              directory on the different types of VAX computers..  ?           o  Appendix C lists the subclasses in the OpenVMS VAX.2              optional save sets C, D, E, F, and G.  @           o  Appendix D lists DECwindows display server and font              files.        xx                   F               o  Appendix E lists files installed either over or underI                  the version numbers of existing files during an upgrade.   H               o  Appendix F describes how to prepare your OpenVMS systemI                  and your PC to run the OpenVMS Management Station server %                  and client software.a  I               o  Appendix G describes methods for managing small capacity F                  system disks, including some specific recommendationsG                  for installing or upgrading to the OpenVMS VAX Version B                  6.2 operating system and the DECwindows Motif for7                  OpenVMS Version 1.2-3 layered product..  :               o  The Glossary defines commonly used terms.  D               o  The Index provides a quick way to find information.           ASSOCIATED DOCUMENTSI               The following documents contain information associated with 4               performing an upgrade or installation:  E               o  The upgrade and installation supplement for your VAX E                  computer-Provides supplemental information necessary G                  during an installation or upgrade, such as booting the 5                  system and determining device names..  E               o  OpenVMS Version 6.2 Release Notes -Describes changed.F                  and enhanced software features, software problems andC                  restrictions, and changes to the documentation forrA                  Version 6.2 of the OpenVMS VAX operating system.   F               o  OpenVMS Version 6.2 New Features Manual-Describes newH                  software features for the OpenVMS Version 6.2 operating                  system.  H               o  VMScluster Systems for OpenVMS-Describes the proceduresI                  for establishing and managing VAXcluster configurations.-  C               o  OpenVMS License Management Utility Manual-Provides-D                  information about registering and managing licenses*                  on an OpenVMS VAX system.  D               o  OpenVMS Guide to System Security-Describes securityG                  features provided by the OpenVMS VAX operating system,e3                  including criteria for C2 systems.h  G               o  OpenVMS System Manager's Manual-Provides task-orientede>                  information about managing an OpenVMS system.  I                                                                       xxiy m  t              ?           o  OpenVMS DCL Dictionary-Provides detailed reference C              information and examples for all OpenVMS DCL commands.   A           o  The hardware manuals supplied with your VAX computer @              provide detailed information about system hardware.    #     CONVENTIONS USED IN THIS MANUALtD           In this manual, every use of OpenVMS VAX means the OpenVMS           VAX operating system.   A           The following conventions are also used in this manual:-  C           Ctrl/x           A sequence such as Ctrl/x indicates that B                            you must hold down the key labeled CtrlD                            while you press another key or a pointing)                            device button.0  B           PF1 x            A sequence such as PF1 x indicates that?                            you must first press and release theAB                            key labeled PF1, then press and releaseC                            another key or a pointing device button.   @           <Return>         In examples, a key name enclosed in a@                            box indicates that you press a key onD                            the keyboard. (In text, a key name is not.                            enclosed in a box.)  <            . . .           A horizontal ellipsis in examples9                            indicates one of the followingS)                            possibilities:   @                            o  Additional optional arguments in a:                               statement have been omitted.  @                            o  The preceding item or items can be9                               repeated one or more times..  E                            o  Additional parameters, values, or other.9                               information can be entered.                xxii                     I               .                A vertical ellipsis indicates the omissionrF               .                of items from a code example or commandD               .                format; the items are omitted becauseH                                they are not important to the topic being)                                discussed..  B               ( )              In format descriptions, parenthesesE                                indicate that, if you choose more than G                                one option, you must enclose the choicesP.                                in parentheses.  H               [ ]              In format descriptions, brackets indicateE                                optional elements. You can choose one, E                                none, or all of the options. (Brackets G                                are not optional, however, in the syntax E                                of a directory name in an OpenVMS file C                                specification, or in the syntax of a G                                substring specification in an assignment *                                statement.)  F               { }              In format descriptions, braces surroundE                                a required choice of options; you must.@                                choose one of the options listed.  H               boldface text    Boldface text represents the introductionH                                of a new term or the name of an argument.  F                                Boldface text is also used to show userB                                input in Bookreader versions of the&                                manual.  ?               italic text      Italic text emphasizes importantrD                                information, indicates variables, andD                                indicates complete titles of manuals.F                                Italic text also represents informationD                                that can vary in system messages (forG                                example, Internal error number), command.G                                lines (for example, /PRODUCER=name), andi:                                command parameters in text.  F               UPPERCASE TEXT   Uppercase text indicates a command, theH                                name of a routine, the name of a file, orG                                the abbreviation for a system privilege.c  K                                                                       xxiiie i  D                C           -                A hyphen in code examples indicates that.B                            additional arguments to the request are=                            provided on the line that follows..  =           numbers          All numbers in text are assumed tol>                            be decimal, unless otherwise noted.?                            Nondecimal radixes-binary, octal, orw@                            hexadecimal-are explicitly indicated.  C           This manual often refers to products by their abbreviated C           names. For example, the VAX 8200, VAX 8250, VAX 8300, and C           VAX 8350 computers are referred to as the VAX 8200, 8250, B           8300, 8350. The MicroVAX 2000 computer is referred to as'           the MicroVAX 2000, and so on..                                                                 xxiv .  .                    I                                                                         1.I         _________________________________________________________________   I                           Overview of Installation and Upgrade Procedures   I         _________________________________________________________________            Overview  I               This chapter describes what happens during the installationeI               and upgrade procedures. It lists changes since the previousgG               version and cautions and restrictions you should be awarelC               of for OpenVMS VAX Version 6.2. It also describes theaE               contents of the distribution kit, tells you whether you H               should do an installation or an upgrade, and refers you to,               the appropriate documentation.                                                    I                       Overview of Installation and Upgrade Procedures 1-1. .  .      '     Cautions, Restrictions, and Changese    E     _________________________________________________________________l  '     Cautions, Restrictions, and Changes-         INTRODUCTIONE           This section describes cautions and restrictions you should D           be aware of and the new or changed features in the OpenVMS:           Version 6.2 installation and upgrade procedures.         CAUTIONS           DECnet_Requirements1  A           The OpenVMS VAX Version 6.2 kit includes the DECnet for.@           OpenVMS (DNA Phase IV) software. If your are currentlyA           running the DECnet/OSI for OpenVMS layered product, thef@           OpenVMS Version 6.2 kit detects this and gives you theB           option to retain those files. If you want to install theD           Phase IV code base, you have the option to do so. However,?           you will not be able to use DECnet over TCP/IP if your           choose Phase IV.  ?           If you want to run the DECnet/OSI for OpenVMS layereds?           product on your OpenVMS Version 6.2 systems, you must.@           upgrade to Version 6.1 of DECnet/OSI for OpenVMS. ThisE           version of DECnet/OSI allows you to run DECnet applications.           over TCP/IP.  =           Before you upgrade to Version 6.1 of DECnet/OSI for 3           OpenVMS, note the following requirements:s  E           ___________________________________________________________n/           If . . .                   Then . . . E           ___________________________________________________________ C           You are upgrading from     You can upgrade to Version 6.1 E           OpenVMS Version 6.1,       of DECnet/OSI prior to upgrading 9                                      your OpenVMS system..  B           You are upgrading from     You must upgrade your OpenVMS?           OpenVMS Version 6.0,       system before upgrading to.?                                      Version 6.1 of DECnet/OSI.         7     1-2 Overview of Installation and Upgrade Procedures            I                                       Cautions, Restrictions, and Changesf    I               ___________________________________________________________.3               If . . .                   Then . . .AI               ___________________________________________________________A  H               You are running DEC        You must upgrade to Version 3.2G               TCP/IP                     of the DEC TCP/IP Services for.I               Services for OpenVMS,      OpenVMS product before upgrading F                                          to Version 6.1 of DECnet/OSI.  G               You are running TCP/IP     Consult your TCP/IP vendor for E               from another vendor,       the minimum version of their I                                          product that will support DECnet 6                                          applications.I               ___________________________________________________________   B               The DECnet for OpenVMS VAX Extensions product is notI               supported for OpenVMS VAX Version 6.2. The network productscH               associated with DECnet for OpenVMS VAX Extensions (P.S.I.,B               WANDD, VOTS, OSAK, and FTAM) are no longer availableF               separately. If you need these products, you must migrateG               to Version 6.1 of DECnet/OSI for OpenVMS. For informationuH               about planning for and implementing DECnet/OSI for OpenVMSI               software, see the DECnet/OSI installation and configurationS               manuals.  5               Volume_Shadowing_Phase_I_Not_Available.   G               Volume shadowing phase I is no longer available. Phase IIFG               (host-based) shadowing is designed to fully replace phaseFH               I (controller-based) shadowing with significantly enhanced               features._  C               For more information about migrating to phase II, see +               Volume Shadowing for OpenVMS.   0               MACRO32.EXE_and_Standalone_Backup.  E               To build standalone backup onto tape, you must have theiF               image MACRO32.EXE on your system disk. Do not tailor offH               the Macro libraries before building standalone backup onto               tape.e  @               Layered_Product_Availability. For the most currentE               information about OpenVMS VAX layered products, contactU0               your Digital sales representative.      I                       Overview of Installation and Upgrade Procedures 1-3  a         '     Cautions, Restrictions, and Changesr           RESTRICTIONS;           Restrictions for OpenVMS VAX Version 6.2 include:.  ;           o  The minimum memory requirement is 4 megabytes.   6           o  The MA780 shared memory is not supported.  @           o  You cannot install or upgrade to Version 6.2 of the>              OpenVMS VAX operating system on the following VAX(              computers and system disks:  E              Computers     MicroVAX I, VAXstation I, VAXstation 8000, 5                            VAX 11/725, and VAX 11/782n  D              System_disks  RK07, RL02, RC25, RD32, RD51, RD52, RD53,#                            and RZ22l  =           o  If your system uses an RZ23L or some other small @              capacity system disk (less than 175 megabytes), the@              entire OpenVMS VAX Version 6.2 operating system andB              the complete DECwindows Motif for OpenVMS VAX layeredD              product will not fit on your disk. Appendix G describesD              some methods that will enable you to install or upgrade@              to OpenVMS VAX Version 6.2 and DECwindows Motif for9              OpenVMS VAX on a small capacity system disk.o  ;              Note that you can use the methods described inp<              Appendix G to free up disk space on any system.  B           o  The RZ23 disk cannot be used as an OpenVMS VAX system4              disk in a DECwindows Motif environment.  D           For more information, see the OpenVMS Operating System forA           VAX and Alpha, Version 6.2 Software Product Description            (SPD).  %     CHANGES SINCE OPENVMS VERSION 6.1 *           New or changed features include:  @           o  Software_Product_Descriptions_(SPDs). The followingB              Software Product Descriptions (SPDs) are now providedD              on the OpenVMS VAX distribution kit. (Hardcopies of the*              SPDs are no longer provided.)  =              -  DECnet for OpenVMS VAX and Alpha, Version 6.2X  ;              -  OpenVMS Operating System for VAX and Alpha,o                 Version 6.2   7     1-4 Overview of Installation and Upgrade Proceduresl s  e      I                                       Cautions, Restrictions, and Changest      ;                  -  RMS Journaling for OpenVMS, Version 6.2p  9                  -  OpenVMS Cluster Software, Version 6.2e  =                  -  Volume Shadowing for OpenVMS, Version 6.2l  F                  For information about the location of these SPD filesI                  on the distribution kit and how you can obtain them, seelF                  the section Locating Files on the Distribution Media.  B               o  New_Save_Set. The OpenVMS Management Station is aG                  client-server application that provides OpenVMS system H                  management capabilities through a client application onH                  a personal computer (PC) running Microsoft Windows. TheE                  OpenVMS Management Station optional files, which are H                  used to create the installation media for the PC clientB                  software, are contained in the VMS062.G save set.  6                  For more information, see Appendix F.                                                    I                       Overview of Installation and Upgrade Procedures 1-5  A  n            Definitions: A Few Key Terms    E     _________________________________________________________________e        Definitions: A Few Key Terms  D           You should be familiar with the following key terms before0           performing an installation or upgrade:  E           ___________________________________________________________e*           Term                  DefinitionE           ___________________________________________________________   @           Distribution Media    The media containing the OpenVMSC                                 VAX operating system software. ThisdE                                 software is supplied in a format thatpA                                 the computer cannot use until youaC                                 perform an installation or upgrade.u  ?           System Disk           The disk that contains (or willnB                                 contain) the OpenVMS VAX operating>                                 system in a usable format. TheA                                 installation or upgrade procedurecB                                 converts the OpenVMS VAX operatingE                                 system software to this usable format2C                                 when transferring the software fromsD                                 the distribution media to the system%                                 disk.p  B           Local Drive           A drive that is connected directly?                                 to a VAX computer. For example,L?                                 a magnetic tape drive connectedr=                                 directly to a VAX computer is E                                 referred to as a local tape drive. IfSC                                 you have a standalone VAX computer, E                                 it is likely all the drives connected @                                 to your system are local drives.  >           InfoServer            A general-purpose disk storageA                                 server that allows you to use the D                                 distribution compact disc to installE                                 the operating system on remote clientiA                                 systems connected to the same LANh5                                 (local area network).   E           Source Drive          The drive that holds the distributionN;                                 media during the upgrade ors-                                 installation.A  7     1-6 Overview of Installation and Upgrade Procedures     o      I                                              Definitions: A Few Key Termsd    I               ___________________________________________________________l.               Term                  DefinitionI               ___________________________________________________________   C               Target Drive          The drive that holds the system @                                     disk-or, for some files, theE                                     alternate disk-during the upgrade 4                                     or installation.  G               HSC Drive             A drive connected to a hierarchical D                                     storage controller (HSC) device.F                                     For example, a magnetic tape driveA                                     connected to an HSC device ishE                                     referred to as an HSC tape drive.e  @                                     The HSC is a self-contained,G                                     intelligent, mass storage subsystem D                                     that enables VAXcluster nodes toF                                     share Digital Storage Architecture0                                     (DSA)_disks.I               ___________________________________________________________   E               For definitions of other specialized terms used in this ?               manual, see the glossary at the end of this book.i                                                I                       Overview of Installation and Upgrade Procedures 1-7  f  a      ,     Locating Files on the Distribution Media    E     _________________________________________________________________   ,     Locating Files on the Distribution Media         INTRODUCTION=           The OpenVMS VAX Version 6.2 files are stored on the 8           distribution media as the following save sets:  E           ___________________________________________________________ '           Save Set Name     Description E           ___________________________________________________________   $           VMS062.A          Required  $           VMS062.B          Required  .           VMS062.C          Library (optional)  /           VMS062.D          Optional (optional)v  3           VMS062.E          Help Message (optional)   6           VMS062.F          OpenVMS manuals (optional)  B           VMS062.G          OpenVMS Management Station software PC,                             files (optional)E           ___________________________________________________________   @           See Appendix C for descriptions of the file subclasses.           contained in the optional save sets.       ON MAGNETIC TAPE@           The OpenVMS VAX Version 6.2 magnetic tape kit contains=           OpenVMS VAX software on three tapes. The first tape D           contains the required save sets VMS062.A and VMS062.B. TheC           second tape contains the save sets VMS062.C and VMS062.D.s?           The third tape contains save sets VMS062.E, VMS062.F,fB           VMS062.G and the DECwindows base support and workstation           support files.       ON TAPE CARTRIDGESD           The OpenVMS VAX Version 6.2 TK50 tape kit contains OpenVMSB           VAX software on two tape cartridges. The first cartridgeD           contains VMS062.A, VMS062.B, VMS062.C, VMS062.D, VMS062.E,?           VMS062.F and VMS062.G save sets. The second cartridgerA           contains standalone BACKUP, and DECwindows base supporto(           and workstation support files.  7     1-8 Overview of Installation and Upgrade Procedures            I                                  Locating Files on the Distribution Median               ON COMPACT DISC G               The OpenVMS VAX Version 6.2 compact disc kit contains all G               the save sets and DECwindows base and workstation support G               files on one compact disc. (For more information, see thei6               OpenVMS Version 6.2 CD-ROM User's Guide.  @               Note that you can install or upgrade the operatingD               system from a local compact disc drive as well as from#               an InfoServer device.   >         DECAMDS AND MONITORING PERFORMANCE HISTORY (MPH) FILESI               The DECamds software is now included as save sets AMDS062.A G               and AMDS062.B on the OpenVMS VAX Version 6.2 distributionhI               media. The save sets are located on the third magnetic tapetF               volume, on the second tape cartridge, and on the compactH               disc in the [AMDS062] directory. For more information, seeF               the system management chapter of the OpenVMS Version 6.2               Release Notes.  B               The Monitoring Performance History (MPH) kit is alsoI               included on the OpenVMS VAX Version 6.2 distribution media. G               The MPH kit is located on the third magnetic tape, on the_I               second tape cartridge, and on the compact disc in the [MPH] H               directory. For more information, see the system management?               chapter of the OpenVMS Version 6.2 Release Notes._  ,         SOFTWARE PRODUCT DESCRIPTIONS (SPDS)D               The following SPD files are located on the second tapeF               cartidge of the TK50 distribution kit and the third tapeD               of the magnetic tape distribution kit. These SPD filesE               have been grouped into an OpenVMS BACKUP save set named F               VMS062_SPD.BCK. File names with the .PS extention are inG               PostScript format. File names with the .TXT extention are )               in plain ASCII text format.   E               DECNET_SPD.PS         DECnet for OpenVMS VAX and Alpha,i/               DECNET_SPD.TXT        Version 6.2.  H               OVMS_62_SPD.PS        OpenVMS Operating System for VAX and6               OVMS_62_SPD.TXT       Alpha, Version 6.2  G               RMS_SPD.PS            RMS Journaling for OpenVMS, Versionh'               RMS_SPD.TXT           6.2t    I                       Overview of Installation and Upgrade Procedures 1-9O V         ,     Locating Files on the Distribution Media        E           CLUSTER_SPD.PS        OpenVMS Cluster Software, Version 6.2M           CLUSTER_SPD.TXTd  E           VOL_SHAD_SPD.PS       Volume Shadowing for OpenVMS, Versione#           VOL_SHAD_SPD.TXT      6.2n  >           To obtain all the SPD files and restore them to yourA           current default directory, enter a BACKUP command usingn           the following format:a  <           BACKUP source-drive:VMS062_SPD.BCK /SAVE_SET *.*;*  B           For source-drive, substitute the name of the device thatC           holds your distribution kit. For example, if your source-tC           drive is a local magnetic tape drive with the device name 6           MUAO, you would enter the following command:  6           $ BACKUP MUAO:VMS062_SPD.BCK/SAVE_SET  *.*;*  C           To restore all the SPD files in PostScript format to yourT1           default directory, enter the following:.  B           $ BACKUP MUAO:VMS062_SPD.BCK/SAVE_SET/SELECT=*.PS  *.*;*                                          8     1-10 Overview of Installation and Upgrade Procedures           I                                  Locating Files on the Distribution Media_      H               The following command restores the PostScript SPD file forI               the OpenVMS VAX and OpenVMS Alpha operating systems to your (               current default directory:  J         $ BACKUP MUAO:VMS062_SPD.BCK/SAVE_SET/SELECT=OVMS_62_SPD.PS  *.*;*  H               If your distribution kit is on compact disk, the SPD filesD               are located in the [DOCUMENTATION.V062] directory. ForF               information about locating and printing these SPD files,>               see the OpenVMS Version 6.2 CD-ROM User's Guide.                                                                      I                      Overview of Installation and Upgrade Procedures 1-11A                Installation Procedure    E     _________________________________________________________________        Installation Procedure    '     WHAT HAPPENS DURING AN INSTALLATION @           When you install the OpenVMS VAX operating system, the4           installation procedure does the following:  C           o  Initializes the system disk, overwriting its contents.   2           o  Creates a system directory structure.  B           o  Transfers the OpenVMS VAX files from the distributionD              media to the system disk. Some files can be transferred"              to an alternate disk.  #     WHEN TO PERFORM AN INSTALLATION <           Use the installation procedure under the following           conditions:   >           o  If your VAX computer is new (it has never had anyE              version of the operating system running on it, including )              factory-installed software).V  B           o  If your VAX computer is running a previous version of?              the operating system and you want to overwrite theh@              entire contents of the system disk (the OpenVMS VAXE              operating system, application software, and user files).r  C           o  If you are running a previous version of the operatingh@              system, but you cannot upgrade. For example, if youB              changed the names of system directories on the systemA              disk, the upgrade procedure will not work correctly.FC              You can either restore the system disk to its originalhB              directory structure, or you can reinstall the OpenVMS"              VAX operating system.  D           Caution: The installation procedure initializes the systemB           disk, overwriting its contents. For this reason, use theD           installation procedure only on new VAX computers or if you:           want to destroy the contents of the system disk.        8     1-12 Overview of Installation and Upgrade Procedures r  i      I                                                    Installation Procedure       1         HOW TO USE THE INSTALLATION DOCUMENTATION @               This manual contains step-by-step instructions forG               performing an OpenVMS VAX installation. However, you will E               need to refer to several different documents before and G               during the installation. Figure 1-1 illustrates the major H               steps in an installation and the documents you will use to                perform each step.                                                                            I                      Overview of Installation and Upgrade Procedures 1-13  e  S           Installation Procedure      B           Figure 1-1 Documentation Used to Perform an Installation                          ' 		(FIGURE NOT AVAILABLE IN .TXT FORMAT)                                                             8     1-14 Overview of Installation and Upgrade Procedures           I                                                         Upgrade Procedure     I         _________________________________________________________________            Upgrade Procedures    &         WHAT HAPPENS DURING AN UPGRADED               When you upgrade the OpenVMS VAX operating system, the3               upgrade procedure does the following:   H               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 7                  distribution media to the system disk.   A                  Note: The upgrade procedure puts the most recent A                  versions of the OpenVMS VAX files in SYS$COMMON.   I               o  Merges some of the old VMS files and the new OpenVMS VAXn+                  files and replaces others.   D                  Certain OpenVMS VAX files are placed either over orH                  under existing files (that is, they are given a versionI                  number above or below the version number of the existingeE                  file). This is done to protect any customizations torI                  the files and results in having two versions of the fileeI                  when the upgrade is completed. For more information, seeO                  Appendix E.  D               o  Cleans up files and structures used only during the                  upgrade.   F               o  Leaves your VMS license and System Integrated Product'                  (SIP) licenses intact.t  F                  You do not need to reinstall these licenses after youH                  upgrade. (See Appendix A for detailed information aboutA                  license management for OpenVMS VAX Version 6.2.)   "         WHEN TO PERFORM AN UPGRADEH               In most cases, you can use the upgrade procedure to obtainC               a higher version of the OpenVMS VAX operating system.tF               Unlike the installation procedure, the upgrade procedureF               does not initialize your system disk. This means you canE               get the latest version of the operating system and keepmA               your user files and optional software files intact.   I                      Overview of Installation and Upgrade Procedures 1-15  e  S           Upgrade Proceduref           RESTRICTIONSC           The upgrade procedure will not work correctly if you have @           changed the names of system directories on your system@           disk. Restore your system disk to a standard directory1           structure before attempting an upgrade.   (     HOW TO USE THE UPGRADE DOCUMENTATION<           This manual contains step-by-step instructions forC           performing an OpenVMS VAX upgrade. However, you will need_C           to refer to several different documents before and duringhB           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 Upgraden      ' 		(FIGURE NOT AVAILABLE IN .TXT FORMAT)_                 WHERE TO GO NEXTD           If you are installing the OpenVMS VAX operating system, go           to Chapter 2.   C           If you are upgrading the OpenVMS VAX operating system, goa           to Chapter 5.t                          8     1-16 Overview of Installation and Upgrade Procedures                         I                                                                         2kI         _________________________________________________________________V  I                                    Before Installing OpenVMS VAX SoftwareT  I         _________________________________________________________________            Overview  F               This chapter describes how to prepare for installing theB               OpenVMS VAX Version 6.2 operating system, including:  =               o  Being aware of the cautions and restrictions   0               o  Ensuring your hardware is ready  D               o  Ensuring your software distribution kit is complete  *               o  Preparing for a C2 system  7               o  Preparing for a VAXcluster environment   4               o  Preparing your tape and disk drives  H               o  Gathering the information you need to supply during the'                  installation procedurec  9               o  Completing the preinstallation checklista  G               If you are an experienced system manager, you can use thelE               checklist at the end of the chapter to complete all thea.               necessary preinstallation tasks.  F               If you are a less-experienced system manager, you shouldH               read the entire chapter and then use the checklist to make?               sure you completed all the preinstallation tasks.r            I                                Before Installing OpenVMS VAX Software 2-1e m  A           Cautions and Restrictionsl    E     _________________________________________________________________s       Cautions and Restrictions          INTRODUCTION?           Before you begin the installation procedure, note thea.           following cautions and restrictions.         CAUTIONS  ?           o  The software installation procedure overwrites thet>              contents of the system disk. Use the installationA              procedure only if your VAX computer is new or if you @              want to destroy the contents of the system disk. IfB              your system disk contains files you want to save, youE              should upgrade to the new version of OpenVMS VAX. For ani>              overview of the upgrade procedure, see Chapter 5.  =           o  Do not attempt to use VMSINSTAL with OPTION G to B              transfer OpenVMS VAX save sets to another media type;C              doing so will produce an unusable system. Instead, youtB              can use the DCL command COPY to transfer save sets to               another media type.  B              If you move the save sets from the distribution mediaE              before beginning the installation, you must move them to D              the [000000] directory on a disk that is not the system9              disk; otherwise, the installation will fail.        RESTRICTIONS  <           o  If your system contains DIGITAL Storage Systems:              Interconnect (DSSI) disks attached to a KFQSAE              controller, you will notice a change in the device names :              for DSSI disks attached to KFQSA controllers.  A              When you boot standalone BACKUP, it will display then?              devices on your system using the new device naming <              scheme. Use the new device names throughout theB              installation and after you complete the installation.        .     2-2 Before Installing OpenVMS VAX Software a         I                                                 Cautions and Restrictionso      D               o  If you want to use DECwindows software with OpenVMSC                  VAX Version 6.2, you must purchase and install theiE                  VMS DECwindows Motif Version 1.1, or higher, layered_G                  product. (Note that, for versions higher than 1.1, theiD                  name of the layered product is DECwindows Motif for                  OpenVMS.)                                                                              I                                Before Installing OpenVMS VAX Software 2-3p n  v           Are You Ready to Install?M    E     _________________________________________________________________)       Are You Ready to Install?p         INTRODUCTION?           Before you begin to install the OpenVMS VAX operating B           system, make sure you have all the required hardware and           software components.         HARDWARE COMPONENTSa2           Examine your hardware for the following:  B           o  Make sure the hardware has been installed and checkedE              for proper operation. For detailed information about theeE              hardware, see the hardware manual for your VAX computer.S  ?           o  Make sure you know how to turn on and operate yournC              system components, including the system unit, console,MD              monitor, drives, terminals, and printers. If necessary,>              read the manuals that came with these components.  D           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, theE              screen messages will be lost. You will need a transcript @              in case there is a problem during the installation.C              For more information, see the upgrade and installationi*              supplement for your computer.       SOFTWARE COMPONENTS 2           Examine your software for the following:  C           o  Make sure you have all the items listed on the bill ofpD              materials (BOM) in the OpenVMS VAX distribution kit. IfD              your kit is incomplete, notify Digital Software Supply,@              and request priority shipment of any missing items.  @           o  Before installing the OpenVMS VAX operating system,D              review Appendix A of this manual for license management?              information, the (OpenVMS Version 6.2 New Features C              Manual, the OpenVMS Version 6.2 Release Notes, and any 2              cover letters included with your kit.    .     2-4 Before Installing OpenVMS VAX Software e  S      I                                                 Are You Ready to Install?       B               o  Read the Before Installing OpenVMS section in theA                  upgrade and installation supplement for your VAXrE                  computer, which describes tasks specific to your VAXeE                  computer that you must complete before beginning the                   installation.                                                                                I                                Before Installing OpenVMS VAX Software 2-5n c  p      !     Preparing for an Installationt    E     _________________________________________________________________m  !     Preparing for an Installatione         INTRODUCTION=           Now that you have determined that your hardware andTC           software components are ready, you can make the necessarye?           preparations for installing the OpenVMS VAX operatingK           system.          PREPARING FOR A C2 SYSTEMfC           Many of the security features provided by the OpenVMS VAXaD           operating system are directed toward the criteria for a C2A           system, as defined in the Department of Defense Trusted ?           Computer System Evaluation Criteria, published by the B           U.S. Department of Defense Computer Security Center (DOD           5200.28-STD).e  D           A C2 system is the shipped system that has been configuredB           according to the guidelines in Appendix C of the OpenVMSB           Guide to System Security. Before installing OpenVMS VAX,@           become familiar with the requirements for operating an5           OpenVMS VAX system within the C2 framework.   *     PREPARING FOR A VAXCLUSTER ENVIRONMENTC           If you are installing the OpenVMS VAX operating system intC           a VAXcluster environment, the installation procedure willeD           ask you for information about your VAXcluster environment.C           Before proceeding, review VMScluster Systems for OpenVMS,O@           which provides the information you will need to answer,           questions during the installation.  9           Note: Entering incorrect information during the 9           installation can force you to repeat the entireS!           installation procedure.   A           Table 2-1 lists the VAXcluster information you need andoA           explains how to obtain that information. For a complete :           explanation, see VMScluster Systems for OpenVMS.          .     2-6 Before Installing OpenVMS VAX Software           I                                             Preparing for an InstallationD      :         Table 2-1 VAXcluster Information for InstallationsI         _________________________________________________________________E         Information You '         Need              How to Get It0I         _________________________________________________________________   F         Type of           Configuration types are distinguished by theD         configuration     interconnect device that the VAX computersD                           in the cluster use to communicate with oneH                           another- CI (Computer Interconnect), Ethernet,I                           DSSI (DIGITAL Storage Systems Interconnect), or B                           FDDI (Fiber Distributed Data Interface).  E         DECnet node name  Determined by the network or system managermH         and node address  for each VAX computer on the network. See yourG                           system or network manager for the DECnet node D                           name and node address for the VAX computerE                           on which you are installing the OpenVMS VAXiF                           operating system. See the DECnet for OpenVMSC                           Guide to Networking for more information.D  D         Allocation class  During the installation procedure you willE         value             be asked for the ALLOCLASS value of the VAX B                           computer on which you are installing theD                           OpenVMS VAX operating system. For example:  I                           Enter a value for MYNODE's ALLOCLASS parameter:t  I                           Refer to VMScluster Systems for OpenVMS for theeF                           rules on specifying allocation class values.G                           Note that, in a mixed-interconnect VAXcluster H                           environment, the allocation class value cannotE                           be zero. It has to be a value between 1 andyE                           255. This is also true for any VAX computeraB                           that is connected to a dual-pathed disk.  H                           When you enter the allocation class value, theI                           installation procedure uses it to automaticallye?                           set the value of the system parameter $                           ALLOCLASS.  I         Quorum disk       See VMScluster Systems for OpenVMS to determinetH                           whether you want a quorum disk in the cluster.  I                                                  (continued on next page)o  I                                Before Installing OpenVMS VAX Software 2-7e S         !     Preparing for an Installation       >     Table 2-1 (Cont.) VAXcluster Information for InstallationsE     _________________________________________________________________      Information Youe#     Need              How to Get It E     _________________________________________________________________   E     Location for      See VMScluster Systems for OpenVMS to determine C     page and swap     where the page and swap files will be located B     files             for the system from which you are installing@                       the OpenVMS VAX operating system software.  B     MOP servers,      To establish either a local area or a mixed-C     disk servers,     interconnect cluster, determine which systems C     tape servers      will be Maintenance Operations Protocol (MOP) D                       servers, disk servers, and tape servers. Refer8                       to VMScluster Systems for OpenVMS.  B     Cluster group     Needed to establish either a local area or a1     number and        mixed-interconnect cluster.rA     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 31E                       alphanumeric characters, including dollar signse.                       ($) and underscores (_).H     _________________________________________________________________     "     PREPARING TAPE AND DISK DRIVES?           Prepare your tape and disk drives using the followingr           steps:  C           1. Decide which drive will hold the distribution tape andeA              which drive will hold the system disk. Determine thed?              device names for each drive, and write these nameso@              on a piece of paper. You will need this informationA              throughout the installation. If you need informationw@              about devices and device names, refer to the Before?              Installing the OpenVMS Operating System section inuA              the upgrade and installation supplement for your VAXV              computer.  C              Note: Do not place the distribution media in the driveM              at this point.s  @           2. Follow this step only if the source drive or targetC              drive is attached to a hierarchical storage controllera,              (HSC). Otherwise, go to step 3.  .     2-8 Before Installing OpenVMS VAX Software i  n      I                                             Preparing for an Installation       F                  Make sure that both the CI and HSC devices are turnedD                  on and on line. Obtain the HSC name from the system9                  manager, or use the following procedure:l  =                  a. Press Ctrl/C at the HSC console terminal.   F                  b. Enter the following command at the HSC> prompt and!                     press Return:n  $                     HSC> SHOW SYSTEM  F                     The information displayed includes the name of the%                     HSC. For example:t  L              22-JUN-1995 15:00:00.00 Boot:12-JUN-1995 11:31:11.41  Up: 51:00L              Version V350           System ID: %X000000011        Name: MUTT                      .                      .                      .@              DISK allocation class = 1 TAPE allocation class = 0(              Start command file Disabled  "              SETSHO - Program Exit  C                     For more information, see the HSC User's Guide.n  F               3. Place a scratch disk in the drive for the system disk3                  (unless the system disk is fixed).a  I               4. Spin up the disk that will be the system disk but do not "                  write protect it.  4         INFORMATION YOU NEED DURING THE INSTALLATIONC               During the installation, the procedure prompts you to I               supply certain information. To save time once the procedureu@               begins, be sure you have the following informationH               available. Remember, entering incorrect information duringC               the installation could force you to repeat the entiree%               installation procedure.r            I                                Before Installing OpenVMS VAX Software 2-9r e  i      !     Preparing for an Installation     E     _________________________________________________________________c     Required"     Information        ExplanationE     _________________________________________________________________ C     Passwords          You will be prompted to type passwords of at B                        least 8 characters for the SYSTEM, SYSTEST,*                        and FIELD accounts.  E     SCSNODE and        If you are installing a standalone system, younE     SCSSYSTEMID        will be prompted to supply an SCSNODE name and D     parameters         an SCSSYSTEMID. The SCSNODE name must be a 1-B                        to 6-character unique DECnet node name. TheD                        SCSSYSTEMID system parameter is calculated as                        follows:_  9                        (DECnet area * 1024) + node numberw  E                        Note that, if you are installing the operatinge>                        system in a VAXcluster environment, theA                        installation procedure does not prompt younD                        to supply these parameters. It calculates theB                        SCSNODE and SCSSYSTEMID based on the DECnetA                        node name and node address that you supplyr0                        earlier in the procedure.  @     Optional           The installation procedure prompts you to>     components         specify whether you want to install theA                        library (VMS062.C) and optional (VMS062.D)o=                        components. Appendix C lists the filesm4                        included in these components.  E                        You can save some space on your system disk ifsB                        you choose not to install these components,>                        but be sure to review Appendix C before                         deciding.                      /     2-10 Before Installing OpenVMS VAX Software            I                                             Preparing for an Installation     I         __________________________________________________________________         Required&         Information        ExplanationI         _________________________________________________________________ G         Location for       Save set VMS062.E (8900 blocks) contains the D         Help Message       online Help Message utility, and VMS062.FH         utility and        (6200 blocks) contains three online referenceI         online manuals     manuals in ASCII format: OpenVMS Master Index, D                            OpenVMS Glossary, and Overview of OpenVMS)                            Documentation.   F                            Know the name of the disk on which you willI                            be installing these save sets. You can install D                            these save sets on your system disk or onG                            alternate disks. (However, if you copied the D                            distribution kit to some other media fromI                            which you will be performing the installation,hE                            you cannot install these save sets on thatiF                            media.) Save set VMS062.E can reside on oneD                            alternate disk, and save set VMS062.F canH                            reside on another. However, you cannot divideF                            the text files in save set VMS062.F betweenD                            disks; they must all be on the same disk.                                              I                               Before Installing OpenVMS VAX Software 2-11o o  r                
                   ?                            (THIS PAGE INTENTIONALLY LEFT BLANK)r                                                                        /     2-12 Before Installing OpenVMS VAX Softwaret           I                                             Preparing for an InstallationA    I         _________________________________________________________________o         Required&         Information        ExplanationI         _________________________________________________________________oD         DECwindows         The installation procedure prompts you toD         components         specify which of the following DECwindows:                            components you want to install:  C                            o  DECwindows base support (required forVA                               running DECwindows software), which '                               includes:   5                               -  DECwindows transport   3                               -  DECwindows keymaps_  F                            o  DECwindows workstation support (requiredD                               for VAX workstations), which includes:  >                               -  DECwindows X11 display server  1                               -  Graphics driversa  9                               -  75 dots/inch video fontsn  B                               -  100 dots/inch video fonts (optionH                                  available only if you select DECwindows5                                  workstation support),  D                            You must install the DECwindows Motif forD                            OpenVMS (previously called VMS DECwindowsD                            Motif) layered product if you want to runH                            the DECwindows software. VMS DECwindows MotifG                            Version 1.1 is the minimum supported versionrB                            for systems running OpenVMS VAX VersionC                            6.2. If you do not know which version of E                            DECwindows Motif you are currently runningYH                            on your system, you can check by entering the-                            following command:m  G                            $ ANALYZE/IMAGE SYS$LIBRARY:DECW$XLIBSHR.EXEc  I                            Note: The DECwindows Motif for OpenVMS layered D                            product does not have the DECwindows baseE                            and workstation support components. To getiC                            full DECwindows support, you must selectaF                            the DECwindows components provided with theF                            OpenVMS VAX Version 6.2 kit and install theH                            separate DECwindows Motif for OpenVMS layeredE                            product, which supports both Motif and XUI (                            environments.  I                               Before Installing OpenVMS VAX Software 2-13  -  e      !     Preparing for an Installation     E     _________________________________________________________________I     Required"     Information        ExplanationE     _________________________________________________________________t8     PAK information    The information listed on ProductA                        Authorization Keys (PAKs) for your OpenVMSeE                        VAX license and any system-integrated productslE                        you will run. The installation procedure gives C                        you the opportunity to register any licensesVD                        you have. To register your licenses, you willB                        need to enter the information listed on the,                        PAK for each license.E     _________________________________________________________________r                                                                  /     2-14 Before Installing OpenVMS VAX Softwares l         I                                                 Preinstallation Checklistf    I         _________________________________________________________________   !         Preinstallation Checklistd             INTRODUCTIONB               Before you begin the installation, use the followingH               checklist to make sure you have completed all of the tasks(               described in this chapter:             DID YOU . . .2  D               <  Read the cautions and restrictions described at the+                  beginning of this chapter?e  @               <  Make sure the hardware is installed and tested?@                  (Described in the hardware manuals for your VAX                  computer.)n  C               <  Check the contents of your kit against the bill ofP!                  materials (BOM)?   H               <  Read Appendix A of this manual, the OpenVMS Version 6.2E                  New Features Manual, the OpenVMS Version 6.2 Release E                  Notes, and any cover letters included with your kit?   G               <  Read the section Preparing for a C2 System for special G                  considerations about running the OpenVMS VAX operatingiH                  system in a C2 environment if you intend to create a C2'                  compliant environment?e  B               <  Turn on the system? (Described in the upgrade and@                  installation supplement for your VAX computer.)  I               <  Set up your system to record the installation procedure?xF                  (Described in the upgrade and installation supplement(                  for your VAX computer.)  B               <  Read the Before Installing OpenVMS section in theA                  upgrade and installation supplement for your VAXa@                  computer and perform the tasks described there?  B               <  Make sure you have the most recent version of the>                  console media if you have a VAX computer thatB                  uses console media? (Described in the upgrade and@                  installation supplement for your VAX computer.)  I                               Before Installing OpenVMS VAX Software 2-15t u  t           Preinstallation Checklist       A           <  Determine whether you want a CI-only, local area, or A              mixed-interconnect cluster if you are installing the @              OpenVMS VAX operating system on a VAX computer in aE              VAXcluster environment? (Described in VMScluster Systems               for OpenVMS.)  D              You should have the following information, depending on$              the type of VAXcluster:  C              o  CI-Only VAXcluster: Get the allocation class value,pA                 DECnet node name, and DECnet node address for then?                 computer. You also need to decide if you want anA                 quorum disk and where the page and swap files foro@                 the system from which you are installing will be                 located.  B              o  Local Area and Mixed-Interconnect VAXclusters: GetE                 the allocation class value, the DECnet node name, the B                 DECnet node address, the cluster group number, andD                 the cluster password. You also need to decide if youD                 want a quorum disk and where the page and swap filesD                 for the system from which you are installing will be                 located.  @           <  Prepare the disk and tape drives? (Described in the5              section Preparing Tape and Disk Drives.)   D           <  Make sure you have the following information (described;              in the section Information You Need During thee%              Installation) available:   B              o  Passwords containing at least 8 characters for the4                 SYSTEM, SYSTEST, and FIELD accounts?  ?              o  SCSNODE and SCSSYSTEMID if you are installing ao"                 standalone system?  E              o  A list of optional OpenVMS VAX components you want toL                 install?  D              o  A list of optional DECwindows support components you                  want to install?  @              o  Information listed on Product Authorization KeysC                 (PAKs) for your OpenVMS VAX license and any system-B1                 integrated products you will run?   /     2-16 Before Installing OpenVMS VAX Software  l  -      I                                                 Preinstallation Checklist_               WHERE TO GO NEXTI               After you have performed all the tasks in the checklist, go_5               to Chapter 3 to begin the installation._                                                                                    I                               Before Installing OpenVMS VAX Software 2-17i                         I                                                                         3rI         _________________________________________________________________   H                              Installing the OpenVMS VAX Operating System  I         _________________________________________________________________P           Overview  F               During the installation procedure, OpenVMS VAX files areC               transferred from the distribution media to the systemtC               disk or, for certain files, to an alternate disk. TheeH               time required to complete an installation varies dependingD               on your hardware configuration and on the distributionI               media you are using. In most cases, magnetic tapes and tape >               cartridges require more time than compact discs.  D               The following installation tasks are described in this               chapter:  *               o  Booting standalone BACKUP  )               o  Creating the system diskr  3               o  Joining a VAXcluster configurationt  "               o  Setting passwords  -               o  Creating the rights database   %               o  Registering licenses                   o  Running AUTOGEN  G               At certain points in the procedure you will need to referpE               to the upgrade and installation supplement for your VAXa               computer.t          I                          Installing the OpenVMS VAX Operating System  3-1I a  n           Booting Standalone BACKUPn    E     _________________________________________________________________        Booting Standalone BACKUP          INTRODUCTIONE           Standalone BACKUP is a subset of the OpenVMS Backup utility D           (BACKUP). Because you boot it into main memory, standalone>           BACKUP executes outside the control of the operatingC           system. You use standalone BACKUP to restore the requiredlD           save sets from the distribution media to your system disk.    #     WHERE TO FIND STANDALONE BACKUPoA           Each piece of media in the distribution kit has a labeleA           that indicates its contents. For example, there are twofD           tape cartridges in a TK50 kit. Standalone BACKUP is on the            second tape cartridge.       BOOTING FROM TAPE CARTRIDGE A           If your distribution media is tape cartridges, completem@           the following steps to boot standalone BACKUP. (If you?           are using an InfoServer device, go to Booting from an            InfoServer Device.)   C           1. Place the media that contains standalone BACKUP in the02              source drive or in the console drive.  E           2. Follow the instructions in the Booting Standalone BACKUP C              section of the upgrade and installation supplement for               your VAX computer.1  B           3. After you boot standalone BACKUP, the system displays              the following:a  J     %BACKUP-I-IDENT, standalone BACKUP V6.1; the date is 22-JUN-1995 15:00     $   A           Note: If you have a tape cartridge kit, remove the tape @           cartridge 2/2 from the drive after you boot standaloneB           BACKUP. Put the tape cartridge that contains the OpenVMSB           VAX operating system in the drive. The tape cartridge is1           labeled VMS062 BIN TK50 1/2 VMS BINARY.l      3     3-2 Installing the OpenVMS VAX Operating Systemc a  i      I                                                 Booting Standalone BACKUPa               WHERE TO GO NEXTH               After you have booted standalone BACKUP, go to the section'               Creating the System Disk.y  )         BOOTING FROM AN INFOSERVER DEVICElG               If you are using the InfoServer to boot standalone BACKUPt@               from a compact disc, complete the following steps:  E               1. Insert the distribution compact disc into the drive._  I               2. Follow the instructions in the Booting Standalone BACKUP_G                  section of the upgrade and installation supplement foro#                  your VAX computer.t  C               3. Enter your VAX processor boot command by using the E                  designator for the Ethernet adapter in the boot pathNG                  and, except for the VAX 9000 computer, add the /R5:100S/                  qualifier to the boot command.E                                                      I                          Installing the OpenVMS VAX Operating System  3-3C    e           Booting Standalone BACKUPS      1              For example, on a VAX 6000 computer:   %              >>> B/R5:100/X:D/B:6 ET0   D              On VAX 9000 computers, standalone BACKUP resides on theD              console hard disk. Because the boot process is slightlyB              different for each type of controller, each supported<              controller has a unique boot command procedure.A              Refer to the upgrade and installation supplement forS@              your VAX 9000 computer for instructions for booting.              standalone BACKUP on your system.  E           4. During an InfoServer boot, the procedure prompts you forTC              a file name that contains an ISL (initial system load)i@              boot program instead of a virtual memory boot (VMB)=              program. Select one of the two files as follows:m                o  ISL_SVAX_062                o  ISL_LVAX_062  A              Use the following table to determine which file nameeE              and boot path designator to use for your processor. NoteoC              that the VAX 9000 computer has the ISL file data builti9              in its VMB image that runs from the console.   E              ________________________________________________________               Processor?              Series        ISL File        Boot Path Designator E              _________________________________________________________E              VAX 3000      ISL_SVAX_062    ESA0 (LANCE), XQA0 (DELQA)_  D              VAX 4000      ISL_SVAX_062    EZA0 (SGEC), XQA0 (DELQA)  =              VAX 6000      ISL_LVAX_062    EXA0 (DEMNA), FXA0 @                                            (DEMFA), ETA0 (DEBNI)2                                            (DEBNA)  E              VAX 7000      ISL_LVAX_062    EXA0 (DEMNA), FXA0 (DEMFA)m  E              VAX 10000     ISL_LVAX_062    EXA0 (DEMNA), FXA0 (DEMFA)a  E              MicroVAX      ISL_SVAX_062    ESA0 (LANCE), XQA0 (DELQA)   7              VAXstation    ISL_SVAX_062    ESA0 (LANCE)o  7              VAXft 110,    ISL_SVAX_062    EPA0 (LANCE)               310, 410,              610, and 612tH              ___________________________________________________________3     3-4 Installing the OpenVMS VAX Operating System            I                                                 Booting Standalone BACKUPh      H                  On a VAX 6000 computer, you would respond to the prompt3                  as shown in the following example:   )                  Loading system software.   '                  Filename: ISL_LVAX_062e  G               5. The InfoServer ISL program then displays the followingh                  menu:  7                    Network Initial System Load Functione                    Version 1.1  .                      FUNCTION         FUNCTION                        ID 2                        1     -        Display Menu*                        2     -        Help4                        3     -        Choose Service4                        4     -        Select Options*                        5     -        Stop  ,                   Enter a function ID value:  G                  If you need more information, select function ID 2 for                   help.  F               6. After you boot standalone BACKUP, the system displays                  the following:   N         %BACKUP-I-IDENT, standalone BACKUP V6.1; the date is 22-JUN-1995 15:00	         $_           WHERE TO GO NEXTG               Once you have booted standalone BACKUP, go to the section '               Creating the System Disk.y                    I                          Installing the OpenVMS VAX Operating System  3-5                 Creating the System Disk    E     _________________________________________________________________s       Creating the System Disk         OVERVIEW?           This section describes the steps for transferring ther?           OpenVMS VAX files from the distribution media to your B           system disk or, for certain files, to an alternate disk.  E           To transfer the OpenVMS VAX files from the distribution kit ;           to your system disk, perform the following steps:   "     STEP 1: DETERMINE DEVICE NAMESE           If you have not already done so, determine the device namesoB           for the source drive, the target drive, and an alternateA           device if you will be using one. Write these names on acC           piece of paper. You will need this information throughout D           the installation. If either the source drive or the targetE           drive is connected to an HSC, you also need the name of the D           HSC. (To determine the value for hsc-name, see the section7           Preparing Tape and Disk Drives in Chapter 2.)E  <           If you need more information about determining the@           device names for your system, refer to the upgrade and8           installation supplement for your VAX computer.  #     STEP 2: LOAD DISTRIBUTION MEDIA A           Each piece of media in the distribution kit has a labelnD           that indicates its contents. Place the media that contains?           the OpenVMS VAX operating system in the source-drive.   D           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 tapeC           cartridge kit, make sure the first tape is in the source-t           drive.  E           If you are installing from a compact disc, it is already in            the drive.            3     3-6 Installing the OpenVMS VAX Operating System  e  S      I                                                  Creating the System Disko      5         STEP 3: TRANSFER VMS062.B TO YOUR SYSTEM DISKuH               Enter a BACKUP command in the following format to transfer8               the VMS062.B save set to your system disk:  M               $ BACKUP/IMAGE/VERIFY [hsc-name]source-drive:VMS062.B/SAVE_SET- (               _$ [hsc-name]target-drive:  F               Substitute the appropriate device names for hsc-name (ifI               appropriate), source-drive, and target-drive. Make sure youtE               put a colon (:) after each device name and that you use I               zeros rather than the letter "O" in the device names and in                VMS062.s  G               The square brackets ([])  indicate that you need the hsc-l=               name only if the device is connected to an HSC.i  F               For example, if your system has a source-drive that is aG               local TU80 magnetic tape drive with a device name of MUA0aI               and a target-drive that is an RA82 disk drive with a device_E               name of DUA1, enter the following command and press the                Return key:   @               $ BACKUP/IMAGE/VERIFY MUA0:VMS062.B/SAVE_SET DUA1:  D               If your system has a source-drive that is a local tapeE               cartridge drive with a device name of MUC6 or a target-_I               drive that is an RA81 disk drive with a device name of DUA1 G               and an HSC name of YOURS, enter the following command andu               press Return:   F               $ BACKUP/IMAGE/VERIFY MUC6:VMS062.B/SAVE_SET YOURS$DUA1:  D               The procedure transfers the VMS062.B save set from theH               distribution kit to the system disk.[1] The amount of timeE               this takes varies depending on the type of VAX computer F               and distribution media you have. During the process, the5               command displays the following message:   ?               %BACKUP-I-STARTVERIFY, starting verification pass   "               ____________________H               [1]          The BACKUP command creates a system disk thatF                           includes a set of volume parameters providedB                           by Digital, including CLUSTER_SIZE (diskD                           access scheme).  For more information, seeE                           the upgrade and installation supplement forp,                           your VAX computer.  I                          Installing the OpenVMS VAX Operating System  3-7e                Creating the System Disk      D           This message indicates that the VMS062.B save set has been@           transferred to the system disk and the files are beingD           checked for errors. If, instead, you see a message similarB           to the following, you might have the wrong volume of the/           distribution kit in the source drive:n  E           % BACKUP-F-OPENIN, error opening  MUA0:[000000]VMS062.B; ase             input -           - SYSTEM-W-NOSUCHFILE, no such file               .              .              .H           If you do want to perform another standalone BACKUP operation,B           ensure the standalone BACKUP volume is online and ready."           Enter "YES" to continue:  E           If the procedure displays the previous messages, remove the D           distribution volume from the drive and replace it with theE           correct volume as described in Step 2. Then type Yes, presse'           Return, and repeat this step.   B           When standalone BACKUP has completed checking files, the3           procedure displays the following message:u  M  %BACKUP-I-PROCDONE, Operation completed. Processing finished at 22-JUN-1995    15:00. C  If you do not want to perform another standalone BACKUP operation,a$  use the console to halt the system.  B     If you do want to perform another standalone BACKUP operation,A     ensure the standalone application volume is online and ready.n     Enter "YES" to continue:  $     STEP 4: BOOT THE NEW SYSTEM DISKD           Halt the system and boot the new system disk, as describedA           in the upgrade and installation supplement for your VAXl           computer.   >           When the boot is completed, the procedure displays aC           message and prompts you to enter the date and time. Enter D           the date and time using the 24-hour clock format and press           Return.d        3     3-8 Installing the OpenVMS VAX Operating Systemd f  u      I                                                  Creating the System Disk                      For example:  D    OpenVMS VAX Version 6.2 Major version id = 1 Minor version id = 0  <                      OpenVMS VAX V6.2 Installation Procedure  ;                                Model: VAXserver 3600 Seriese2                        System device: RA82 - _DUA8-                          Free blocks: 1170940r+                             CPU type: 10-01e  I    * Please enter the date and time (DD-MMM-YYYY HH:MM):22-JUN-1995 15:00   @    STDRV-I-STARTUP, VMS startup begun at 22-JUN-1995 15:00:00.59L    %SET-I-NEWAUDSERV, identification of new audit server process is 00000028           .            .            .n;    %%%%%%%%%%%  OPCOM  22-JUN-1995 15:00:15.46  %%%%%%%%%%%l*    Message from user JOB_CONTROL on POKIPCC    %JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT   ;    %%%%%%%%%%%  OPCOM  22-JUN-1995 15:00:15.41  %%%%%%%%%%% *    Message from user JOB_CONTROL on POKIPC%    -SYSTEM-W-NOSUCHFILE, no such file   A    LICENSE-F-EMTLDB, license database contains no license recordseD    %LICENSE-E-NOAUTH, DEC VAX-VMS use is not authorized on this nodeH    -%LICENSE-F-NOLICENSE, no license is active for this software product5    -%LICENSE-I-SYSMGR, please see your system managerh#    Startup processing continuing...a  A    %STDRV-I-STARTUP, VMS startup begun at 22-JUN-1995 15:03:00.00   C               Note: The procedure displays OPCOM messages from JOB_ H               CONTROL stating the master queue file QMAN$MASTER.DAT doesG               not exist. You can ignore these messages. You will create #               the queue file later._  E               The procedure also displays error messages stating that G               the OpenVMS VAX license is not registered. You can ignore_F               these messages. License registration occurs later in theD               procedure. For more information about registering yourI               licenses, see Appendix A and the OpenVMS License Management                Utility Manual.a  I                          Installing the OpenVMS VAX Operating System  3-9  i  a           Creating the System Disk      $     STEP 5: SPECIFY THE VOLUME LABELB           The procedure prompts you to specify the volume label ofE           the system disk. A volume label is the name the OpenVMS VAX D           operating system uses to refer to the system disk. You canB           press the Return key to accept the default volume label,E           OpenVMS062, or you can enter a volume label of your choice. E           The volume label can be 1 to 12 characters long; do not uset           spaces. For example:  G     If this system disk is to be used in a cluster with multiple system E     disks, then each system disk must have a unique volume label. AnynG     nodes having system disks with duplicate volume labels will fail toi     boot into the cluster.  K     You can indicate a volume label of 1 to 12 characters in length. If younL     want to use the default name of OpenVMS062, just press the Return key in"     response to the next question.  G     * Enter the volume label for this system disk [OpenVMS062]: SYSDSK1B  $     STEP 6: SPECIFY THE SOURCE DRIVE@           The procedure prompts you to specify which drive holdsD           the distribution kit. Enter the device name for the source           drive.  B           For example, if you are not using the InfoServer and theD           source drive is a magnetic tape drive with the device name+           MUA0, type MUA0 and press Return.   N     * Enter the name of the drive holding the OpenVMS distribution media: MUA07     * Is the OpenVMS media ready to be mounted? [N] YESe4     %MOUNT-I-MOUNTED, VMS062       mounted on _MUA0:  B           If you are not using the InfoServer, continue to Step 7:-           Select Optional OpenVMS Components.   6           If you are using an InfoServer, enter DAD1:.  M           * Enter the volume label for this system disk [OpenVMS062]: SYSDSK1 M           * Enter name of drive holding the OpenVMS distribution media: DAD1:v  ,           The procedure then prompts you to:  :           * Enter the InfoServer service name [VAXVMS062]:7           * Enter the InfoServer work group number [0]:t  =           Press the Return key as a response to both of theseo           prompts.  4     3-10 Installing the OpenVMS VAX Operating System 1         I                                                  Creating the System Diskt      F               The InfoServer work group number was determined when youH               made a selection from the menu displayed by the InfoServerB               ISL program (refer to the section Booting StandaloneF               BACKUP). If the answer to the group number is incorrect,3               the procedure displays the following:r  G               InfoServer work group number must be in the range 0-1023.Y  -               The procedure then prompts you:a  @               * Is the OpenVMS media ready to be mounted? [N]: Y=                %MOUNT-I-MOUNTED, VMS062     mounted on _DAD1:E  2         STEP 7: SELECT OPTIONAL OPENVMS COMPONENTSH               The procedure displays information about OpenVMS VAX filesF               that are optional and about the remaining amount of diskG               space. The information is similar to the following (block,)               sizes might vary slightly):   O               Select optional software you want to install. You can install onelH               or more of the following OpenVMS or DECwindows components:  L               o OpenVMS library                              -  43500 blocksL               o OpenVMS optional                             -  19100 blocksL               o OpenVMS Help Message                         -   8850 blocksL               o Text versions of three OpenVMS manuals       -   4450 blocksL               o DECwindows workstation support               -  25750 blocksL               o DECwindows base support                      -   3600 blocksL               o OpenVMS Management Station                   -   5900 blocks  <               Space remaining on system disk: 1170752 blocks  I               You must indicate which of the options you want to install.CI               If you require network support, you must select the OpenVMSs                library component.  D               Note: If you do not install the optional components atG               this time, you can install them after the installation bynF               using the VMSTAILOR or DECW$TAILOR utility. However, theG               Help Message utility and the three OpenVMS manuals can be G               tailored on to the system disk only. If you do not choose E               them at this point in the procedure and want them on an H               alternate device, you will not be able to use VMSTAILOR to!               restore them later.i  I                         Installing the OpenVMS VAX Operating System  3-110                Creating the System Disk      B           If you want to install Help Message on an alternate diskE           after the installation procedure completes, you can use the %           BACKUP command, as follows:i  A           BACKUP/VERIFY source-device:[000000]VMS062.F/SAVE_SET -_(           target-device:[directory-name]  @           For source-device, enter the device name for the driveA           on which the distribution media is mounted. For target-_C           device, enter the device name on which the alternate disk_C           is mounted, and for directory-name, enter the name of theSC           directory to which you are copying the files. (To installLD           the OpenVMS manuals, specify VMS062.E/SAVE_SET in place of           VMS062.F/SAVE_SET.)   D           Also note that, for TK50 tape cartridges, it is quicker toC           install OpenVMS VAX software during the installation thanXA           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 theS2           instructions displayed by the procedure.             OpenVMS Library Files            ---------------------_7           The procedure displays the following message:V  C           * Do you want to install the OpenVMS library files? (Y/N)   A           The file subclasses of the VMS062.C save set are listed C           in Appendix C. If you want to install the VMS062.C files, C           type Y (for YES) and press Return. If you require networkeD           support, you must select the OpenVMS library component. IfD           you do not want to install the VMS062.C files, type N (for           NO) and press Return.               OpenVMS Optional Files            ----------------------7           The procedure displays the following message:   D           * Do you want to install the OpenVMS optional files? (Y/N)  A           The file subclasses of the VMS062.D save set are listed C           in Appendix C. If you want to install the VMS062.D files, D           type Y and press Return. If you do not want to install the2           VMS062.D files, type N and press Return.  4     3-12 Installing the OpenVMS VAX Operating System o         I                                                  Creating the System Disks      .               OpenVMS Management Station Files.               --------------------------------;               The procedure displays the following message:G  C       The OpenVMS Management Station is a client-server application D       that provides OpenVMS system management capabilities through aF       client application on a personal computer (PC) running MicrosoftD       Windows. The server application runs on OpenVMS systems and isF       automatically installed as part of the OpenVMS operating system.  J       This option provides the files used to create the installation mediaL       for the PC client software.  If you want to use the OpenVMS ManagementM       Station, you must install these files on at least one OpenVMS system to J       create the installation media, which can then be used to install the#       PC client on one or more PCs.e  I       Note: To use the OpenVMS Management Station on your PC, you must bevO       running Digital's PATHWORKS V5.0A for DOS and Windows (or V5.1) software.e  N       The OpenVMS Management Station optional files consume approximately 5900O       blocks and will be placed on your system disk in SYS$COMMON:[TNT.CLIENT].t  P    * Do you want to install the optional OpenVMS Management Station files? (Y/N)  7       Space remaining on system disk:     623240 blockse  I               If you want to use the OpenVMS Management Station software,nB               you must install these files. After the installationH               procedure completes, follow the instructions in Appendix FC               to prepare your OpenVMS system and your PC to run thenD               OpenVMS Management Station server and client software.                  Help Message Files                ------------------;               The procedure displays the following message:a  K              The Help Message utility (MSGHLP) provides online explanations K              and user actions for OpenVMS messages in place of the hardcopy N              OpenVMS System Messages and Recovery Procedures Reference Manual,/              which is now separately orderable.   =              The MSGHLP database, MSGHLP$LIBRARY.MSGHLP$DATA, ;              consumes approximately 8850 blocks and will beaI              placed by default on your system disk in SYS$COMMON:[SYSHLP]lB              unless you specify an alternate device when prompted.  <          * Do you want to install the MSGHLP database? (Y/N)  I                         Installing the OpenVMS VAX Operating System  3-13e    K           Creating the System Disk      A           The Help Message utility is an online system for system E           messages documentation. You can install Help Message eitherSD           on the system disk or on an alternate disk. If you want toB           install the Help Message files, type Y and press Return.  7           The procedure displays the following message:   N       You can install this database on your system disk in SYS$COMMON:[SYSHLP]K       or on an alternate device. If you specify an alternate device, but no M       directory, MSGHLP$LIBRARY.MSGHLP$DATA is placed in [HELP_MESSAGE]. WheneK       prompted, take the default of the system disk or specify an alternate         device, using this format:  .                             device:[directory]  N  * Where do you want to install the MSGHLP database?[SYS$COMMON:[SYSHLP]] DUA1                                                          4     3-14 Installing the OpenVMS VAX Operating System s  h      I                                                  Creating the System Disk.      D               The Help Message database is installed in the area youI               specify, and the system displays information similar to the                following:  I                   Space remaining on alternate device DUA1: 124532 blocks                  OpenVMS Manualso               --------------- ;               The procedure displays the following message:6  O               You have the choice of installing the text version of one or moreB               OpenVMS manuals:  J               o OpenVMS Master Index                       -   3600 blocksJ               o OpenVMS Master Glossary                    -    650 blocksJ               o Overview of OpenVMS Documentation          -    200 blocks  L               You can install these manuals, by default, to your system diskK               in [SYSHLP.VMSDOC], or to an alternate device of your choice. I               In either case, all manuals must reside on the same device. O               If you choose an alternate device and do not specify a directory,gJ               [VMSDOC_TEXT] will be created for you.  The device structureE               for the alternate device should resemble the following:   5                                    device:[directory]o  D               Do you want any of these three OpenVMS manuals?: (Y/N)  H               Type Y to install all three manuals or to install a subset               of the manuals.t  1               The following message is displayed:r  :               Do you want all three OpenVMS manuals? (Y/N)  H               To install all three manuals, type Y. To install a subset,F               type N and the system will display each manual title and<               prompt you to type either Y or N to select it.  I               When you have completed selecting which manuals to install,W0               the following prompt is displayed:  N          * Where do you want to install the OpenVMS manual(s)? [SYSHLP.VMSDOC]  H               Press Return to accept the default, [SYSHLP.VMSDOC] on theE               system disk, or enter the alternate disk name and pressu               Return.s  I                         Installing the OpenVMS VAX Operating System  3-15a i  i           Creating the System Disk      -     STEP 8: CHOOSE DECWINDOWS SUPPORT OPTIONS D           Next, the procedure displays messages about the DECwindows:           components shipped with OpenVMS VAX Version 6.2.  ?           Important: The OpenVMS VAX operating system no longerd@           ships the VMS DECwindows product. The operating systemC           now ships only the DECwindows base support and DECwindowse@           workstation support components. To get full DECwindows@           support, you must also install the separate DECwindowsA           Motif for OpenVMS VAX (previously called VMS DECwindowsPC           Motif) layered product, which supports both Motif and XUIn           environments.b  :           Note: The DECwindows base support and DECwindowsA           workstation support components are not shipped with thetD           layered product. If you want to install these options, youB           must select them now or use the DECW$TAILOR option after/           the installation procedure completes.d  /           The procedure displays the following:i  E             You can select DECwindows support now, or you can use the G             DECW$TAILOR utility to provide or remove DECwindows supportS#             after the installation.   B             Some media, TK50s in particular, can be very slow whenD             tailoring on files. You might want to provide DECwindows<             options now and tailor off unwanted files later.  H             You can install all of the DECwindows components provided inG             this kit, which requires approximately 29350 blocks, or youM+             can select specific components.M  H             o DECwindows workstation support             -  20750 blocks8               -  75 dots per inch video fonts (included)H               - 100 dots per inch video fonts (optional) -   5000 blocksH             o DECwindows base support                    -   3600 blocks  N             If you are installing this kit on a workstation or on a VAXclusterK             that contains workstations, then you must choose the DECwindowsO'             workstation support option.l  L             If you are installing this kit on a system that does not includeL             workstations but does include Xterminals, then you might want toL             choose the DECwindows workstation support option to provide fontJ             files.  If you decide not to select the DECwindows workstationF             support option at this time, then you will have to use theI             DECW$TAILOR utility to provide font files for the Xterminals.   4     3-16 Installing the OpenVMS VAX Operating System A  o      I                                                  Creating the System Disk       J           If you plan to run DECwindows software, then you must choose the)           DECwindows base support option.   N           NOTE: This kit does NOT contain full DECwindows support. It includesL                 only the DECwindows base and workstation support components.L                 To obtain full DECwindows support, you must also install theJ                 separate DECwindows Motif for OpenVMS VAX layered product.  L           NOTE: VMS DECwindows Motif Version 1.1 is the minimum version that9                 can be used with OpenVMS VAX Version 6.2.   @      * Do you want to provide optional DECwindows support? (Y/N)                                                                  I                         Installing the OpenVMS VAX Operating System  3-17t d  .           Creating the System Disk                 Before You Decidea           -----------------rD           Before you indicate whether you want to install DECwindows3           support software, consider the following:   E     _________________________________________________________________c0     If you...                     Then choose...E     _________________________________________________________________s:     Intend to install the         DECwindows base support.     DECwindows Motif layered     producte  A     Intend to install the         DECwindows workstation support.      DECwindows Motif layered     product on a workstation     or on a VAXcluster thatt     contains workstations or     Xterminals  A     Are installing on a           DECwindows workstation support.O     workstation or on a      VAXcluster that includes     workstations or Xterminals  E     Have a workstation monitor    DECwindows workstation support withv;     capable of displaying 100     the 100 dots/inch option.v>     dots/inch (for example, a     By selecting the workstationB     VR150, VR160, or VR295)       support files, you automatically  =                                   get 75 dots/inch video fontmA                                   files, and you will be promptedeD                                   to indicate if you want to installA                                   100 dots/inch video font files.eE     _________________________________________________________________oC           If you do not want to install DECwindows support, type N,y0           press Return, and go to the next step.  E           If you want to install DECwindows support, type Y and press ?           Return. The procedure displays the following message:o  H           * Do you want to install DECwindows workstation support? (Y/N)  D           If you answer Yes to this prompt, the following DECwindows'           components will be installed:I  +           o  DECwindows workstation support   $           o  DECwindows base support  4     3-18 Installing the OpenVMS VAX Operating System           I                                                  Creating the System Disks      )               o  75 dots/inch video fontsr  G               You are also given the option to select the 100 dots/inch                video fonts.  E               If you decide not to install the DECwindows workstationsH               support, you are given the option to select the DECwindowsD               base support, which is required if you plan to run any"               DECwindows software.  E               * Do you want to install DECwindows base support? (Y/N)   #         STEP 9: VERIFY YOUR CHOICES I               The procedure displays a list of OpenVMS VAX and DECwindowsfA               support options you have selected and gives you thenB               opportunity to change your mind before proceeding by/               displaying the following message:   &               * Is this correct? (Y/N)  D               If you answer No to this prompt, you can respecify theI               OpenVMS and DECwindows support options you want to install.e  (         STEP 10: INSTALL OPENVMS OPTIONSI               If you answer Yes to the prompt in Step 9, the installation E               procedure begins restoring the OpenVMS options you havepI               selected. After the installation has completed, you can useiH               the VMSTAILOR utility to remove any optional OpenVMS filesE               that you do not need. (For more information about using )               VMSTAILOR, see Chapter 10.)   H               This step in the procedure will vary, depending on whetherH               your distribution kit is on tape cartridges, compact disc,                or magnetic tapes.  F               Tape_Cartridges_or_Compact_Disc-If your distribution kitF               is on tape cartridges or compact disc and you elected toI               install the VMS062.C, VMS062.D, VMS062.E, and VMS062.F savecB               sets, the procedure displays the following messages:  4               Restoring OpenVMS library save set ...?               %BACKUP-I-STARTVERIFY, starting verification passi  5               Restoring OpenVMS optional save set ... ?               %BACKUP-I-STARTVERIFY, starting verification pass   I                         Installing the OpenVMS VAX Operating System  3-19  l  n           Creating the System Disk      5           Restoring OpenVMS Help Message save set ... ;           %BACKUP-I-STARTVERIFY, starting verification pass   0           Restoring OpenVMS manuals save set ...;           %BACKUP-I-STARTVERIFY, starting verification passe  ?           Magnetic_tapes-If your distribution media is magneticoB           tape, you must mount tape 2 of the distribution kit. TheC           procedure then begins restoring the VMS062.C and VMS062.DaE           save sets, if you elected to install them, and displays thed           following messages:   0           Restoring OpenVMS library save set ...;           %BACKUP-I-STARTVERIFY, starting verification passe  1           Restoring OpenVMS optional save set ...t;           %BACKUP-I-STARTVERIFY, starting verification passh  @           The procedure now prompts you to mount the third tape.>           After you mount the third tape, the procedure begins?           restoring the VMS062.E and VMS062.F save sets, if you =           elected to install them, and displays the following            messages:X  5           Restoring OpenVMS Help Message save set ... ;           %BACKUP-I-STARTVERIFY, starting verification passS  0           Restoring OpenVMS manuals save set ...;           %BACKUP-I-STARTVERIFY, starting verification pass        WHERE TO GO NEXTB           If you are installing DECwindows support software, go to7           Step 11: Install DECwindows Support Software.e  C           If you are not installing DECwindows support software, gol:           to the section Joining a VAXcluster Environment.  0     STEP 11: INSTALL DECWINDOWS SUPPORT SOFTWAREC           If you are installing from magnetic tape or compact disc,oB           the distribution media containing the DECwindows support7           files is already loaded on your source drive.   @           If you are installing from tape cartridges, remove theB           tape that contains the OpenVMS VAX operating system from@           the source drive when you see a message similar to the           following:  4     3-20 Installing the OpenVMS VAX Operating System    e      I                                                  Creating the System Disk       L                  You can now remove the OpenVMS distribution kit from MUA0:.  6                  Load the DECwindows distribution kit.  ?               Put the second tape cartridge, which contains thenB               DECwindows support files, in the source drive. (NoteG               that you are not loading the DECwindows Motif for OpenVMS ,               layered product at this time.)  I               When prompted, type the device name of the source drive andt(               press Return. For example:  N      * Enter name of the drive holding the DECwindows distribution media: MUA0;      * Is the DECwindows media ready to be mounted? [N] YESa  D               The procedure installs the DECwindows options that youG               specified and displays messages similar to the following:t  8               %MOUNT-I-MOUNTED, DEC062 mounted on _MUA0:  @                   Restoring DECwindows base support save set ...?               %BACKUP-I-STARTVERIFY, starting verification passa  G                   Restoring DECwindows workstation support save set ...M?               %BACKUP-I-STARTVERIFY, starting verification pass   J                   Restoring DECwindows 75 dots per inch fonts save set ...?               %BACKUP-I-STARTVERIFY, starting verification pass   K                   Restoring DECwindows 100 dots per inch fonts save set ... ?               %BACKUP-I-STARTVERIFY, starting verification passx  >               Note: The DECwindows support files are listed inH               Appendix D. After you finish the installation, you can useF               the DECwindows tailoring utility, DECW$TAILOR, to removeH               the DECwindows files you do not need. For more informationD               about removing files with DECW$TAILOR, see Chapter 10.  G               If your distribution media is tape cartridges or magnetic C               tape, the procedure displays a message similar to thetF               following after the DECwindows options you have selected/               have been successfully installed:s  L               You can now remove the DECwindows distribution kit from MUA0:.  ;               Remove the distribution media from the drive.l  H               If your distribution media is compact disc leave it in the               drive.  I                         Installing the OpenVMS VAX Operating System  3-21c r  R      $     Joining a VAXcluster Environment    E     _________________________________________________________________M  $     Joining a VAXcluster Environment         INTRODUCTION=           The installation procedure now asks whether you arekE           installing the OpenVMS VAX operating system in a VAXclusterd?           or standalone environment. If you are installing in aH@           VAXcluster environment, the procedure asks a series ofA           questions about your configuration. Refer to VMSclustere@           Systems for OpenVMS to get the information you need to!           answer these questions.d         VAXCLUSTER OR STANDALONE?M8           The procedure displays the following messages:  .           Creating [VMS$COMMON] directory tree  M           In a cluster, you can run multiple systems sharing all files excepttD           PAGEFILE.SYS, SWAPFILE.SYS, SYSDUMP.DMP and VAXVMSSYS.PAR.  5           * Will this node be a cluster member? (Y/N)a  E     _________________________________________________________________M-     If you are installing a ...      Then ...SE     _________________________________________________________________e  6     Standalone system                Do the following:  @                                      1. Type N and press Return.  B                                      2. If you selected DECwindowsJ                                         workstation support, the procedureG                                         asks you if you want DECwindows G                                         Motif as your default windowingsE                                         system. Type Y or N and presst/                                         Return.   K                                      3. Go to the section Setting Passwords C                                         and SCSNODE and SCSSYSTEMID 3                                         Parameters.s      4     3-22 Installing the OpenVMS VAX Operating System f  s      I                                          Joining a VAXcluster Environment     I         _________________________________________________________________ 1         If you are installing a ...      Then ... I         _________________________________________________________________   :         VAXcluster system                Do the following:  D                                          1. Type Y and press Return.  K                                          2. Make sure you have a VAXcluster I                                          license PAK for each node in thed4                                          VAXcluster.  @                                          3. Go to the next step.I         _________________________________________________________________                                                                 I                         Installing the OpenVMS VAX Operating System  3-23e t  n      $     Joining a VAXcluster Environment      $     DETERMINE THE TYPE OF VAXCLUSTERE           If you answered Yes to the previous question, the proceduren)           displays the following message:   8           Now configuring system to be a cluster member.  D           The installation procedure then displays several questionsB           about the configuration of your VAXcluster. Your answersB           to these questions depend on whether you want to installB           a CI-only, local area, FDDI, DSSI, or mixed interconnect@           VAXcluster. Before answering these questions, you mustE           determine which type of VAXcluster you want to install. ForMD           a complete description of VAXcluster types, see VMScluster           Systems for OpenVMS.       CI-ONLY VAXCLUSTERC           Table 3-1 lists the questions you are asked if you want a @           CI-only VAXcluster and explains the typical responses.    ;     Table 3-1 Installation Questions for CI-Only VAXclusteraE     _________________________________________________________________ 0     Question                      How to RespondE     _________________________________________________________________u*     Will this node be a cluster   Enter Y.     member (Y/N)?w  D     What is the node's DECnet     Enter the unique DECnet node name-?     node name?                    for example, KRUP. The DECnetl>                                   node name can be from 1 to 6C                                   alphanumeric characters in length D                                   and cannot include dollar signs or.                                   underscores.  >     What is the node's DECnet     Enter the unique DECnet node;     node address?                 address-for example, 2.2.i  D     Will the Ethernet be used     Enter N. A CI-only VAXcluster doesB     for cluster communications    not use the Ethernet for cluster1     (Y/N)?                        communications.   E                                              (continued on next page)       4     3-24 Installing the OpenVMS VAX Operating System           I                                          Joining a VAXcluster Environmentn      G         Table 3-1 (Cont.) Installation Questions for CI-Only VAXclusterEI         _________________________________________________________________ 4         Question                      How to RespondI         _________________________________________________________________bH         Will be a disk server (Y/N)?  Enter Y if you want local disks toF                                       be served to the cluster. If youE                                       enter Y, the procedure will askoG                                       if the node will serve HSC disks.oF                                       Enter N to this second question.D                                       HSC disks are available to allE                                       nodes in a CI-cluster. Refer to D                                       VMScluster Systems for OpenVMSG                                       for information on served clusters,                                       disks.  D         Enter a value for KRUP's      If the system includes a dual-H         ALLOCLASS parameter:          ported disk, enter the appropriateE                                       allocation class value (it musthD                                       be a value between 1 and 255).I                                       Otherwise, enter 0. For informationm@                                       on selecting the ALLOCLASSG                                       parameter, see VMScluster Systemso2                                       for OpenVMS.  E         Does this cluster contain a   Enter Y or N, depending on yourlD         quorum disk (Y/N)?            configuration. If you enter Y,H                                       the procedure asks for the name ofG                                       the quorum disk. Enter the deviceCG                                       name of the quorum disk. Refer towH                                       VMScluster Systems for OpenVMS forE                                       information about quorum disks. I         _________________________________________________________________ 4         LOCAL AREA AND MIXED-INTERCONNECT VAXCLUSTERG               Table 3-2 lists the questions you are asked if you want agF               local area VAXcluster or a mixed-interconnect VAXcluster1               and explains the typical responses.o                  I                         Installing the OpenVMS VAX Operating System  3-25_ _  _      $     Joining a VAXcluster Environment      8     Table 3-2 Installation Questions for Local Area and 8               Mixed-Interconnect VAXcluster EnvironmentsE     _________________________________________________________________ 0     Question                      How to RespondE     _________________________________________________________________w*     Will this node be a cluster   Enter Y.     member (Y/N)?   D     What is the node's DECnet     Enter the unique DECnet node name-?     node name?                    for example, KRUP. The DECnet >                                   node name can be from 1 to 6C                                   alphanumeric characters in lengthrD                                   and cannot include dollar signs or.                                   underscores.  >     What is the node's DECnet     Enter the unique DECnet node;     node address?                 address-for example, 2.2.   C     Will the Ethernet be used     Enter Y. The Ethernet is required =     for cluster communications    for cluster (SCS internode) B     (Y/N)?                        communications in local area and?                                   mixed-interconnect VAXcluster_*                                   systems.  D     Enter this cluster's group    Enter a number in the range from 1<     number:                       to 4095 or 61440 to 65535.  A     Enter this cluster's          Enter the cluster password. The ?     password:                     password must be from 1 to 31 C                                   alphanumeric characters in length B                                   and can include dollar signs andC                                   underscores. (The password is not @                                   displayed while you enter it.)  7     Reenter this cluster's        Reenter the password.      password for verification:  C     Will be a disk server (Y/N)?  Enter Y. In local area and mixed- B                                   interconnect VAXcluster systems,B                                   the system disk is always servedE                                   to the cluster. Refer to VMScluster E                                   Systems for OpenVMS for information :                                   on served cluster disks.  E                                              (continued on next page)n  4     3-26 Installing the OpenVMS VAX Operating System P         I                                          Joining a VAXcluster Environmenta      C         Table 3-2 (Cont.) Installation Questions for Local Area andoD                           Mixed-Interconnect VAXcluster EnvironmentsI         _________________________________________________________________s4         Question                      How to RespondI         _________________________________________________________________sF         Will KRUP serve HSC disks     Enter a response appropriate for9         (Y/N)?                        your configuration.n  F         Enter a value for KRUP's      Enter the appropriate allocationG         ALLOCLASS parameter:          class value. If you have a mixed-hH                                       interconnect VAXcluster, the valueD                                       must be between 1 and 255; you5                                       cannot enter 0.s  E         Does this cluster contain a   Enter Y or N, depending on youreD         quorum disk (Y/N)?            configuration. If you enter Y,H                                       the procedure asks for the name ofG                                       the quorum disk. Enter the devicesG                                       name of the quorum disk. Refer totH                                       VMScluster Systems for OpenVMS forB                                       information on quorum disks.H        _________________________________________________________________                                              I                         Installing the OpenVMS VAX Operating System  3-27R ,  a      <     Setting Passwords and SCSNODE and SCSSYSTEMID Parameters    E     _________________________________________________________________i  <     Setting Passwords and SCSNODE and SCSSYSTEMID Parameters         INTRODUCTION=           Next, the installation procedure prompts you to set C           passwords for the SYSTEM, SYSTEST, and FIELD accounts andn<           uses this information to create a rights database.         HOW TO ENTER PASSWORDS/           When setting the passwords, remember:t  4           o  Passwords must be 8 characters or more.  D           o  Passwords are not displayed by the system while you are              entering them.   8           o  Press Return after you enter each password.  '           o  Each password is verified.T  7           Use the following procedure to set passwords:n  C           1. Supply the passwords when prompted by the installationt#              procedure, as follows:h  E     Now we will ask you for new passwords for the following accounts:   *                     SYSTEM, SYSTEST, FIELD  H     Passwords must be a minimum of 8 characters in length. All passwordsJ     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) updated9     %VMS-I-PWD_OKAY, account password for SYSTEM verified,  !     * Enter password for SYSTEST:H      * Re-enter for verification:*     %UAF-I-MDFYMSG, user record(s) updated:     %VMS-I-PWD_OKAY, account password for SYSTEST verified  F          The SYSTEST_CLIG account will be disabled. You must re-enable=          it before running UETP but do not assign a password.   4     3-28 Installing the OpenVMS VAX Operating System    y      I                  Setting Passwords and SCSNODE and SCSSYSTEMID Parametersn      #         * Enter password for FIELD: $         * Re-enter for verification:.         %UAF-I-MDFYMSG, user record(s) updated<         %VMS-I-PWD_OKAY, account password for FIELD verified  G               2. If there are no password errors, the procedure creates F                  your rights database, and you can proceed to the next                  section.t  G                  If you enter a password incorrectly or if the passwordCC                  is too easy to guess, the procedure displays errorh3                  messages similar to the following:   >    %VMS-I-PWD_INVALID, account password for SYSTEST is invalid1    %VMS-I-PWD_WEAK, password is too easy to guess   O    Because of the preceding error, you must take action to secure this account.uI    You must either disable this account, change its password, or do both.r                                                      I                         Installing the OpenVMS VAX Operating System  3-29o x  l      <     Setting Passwords and SCSNODE and SCSSYSTEMID Parameters      ?           3. When the procedure asks if you want to disable theNA              account, type N and press Return. When the procedurenA              asks if you want to enter a new password, type Y andoB              press Return. Then enter a new password. For example:  0     Do you want to disable this account (Y/N)? N7     Do you want to change the account password (Y/N)? YRK     You must now select a new primary password for the SYSTEST account. TherJ     password you select must be at least 8 characters in length and cannot+     be the same as the name of the account:t       New password:o     Verification:a*     %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, theA              installation procedure creates your rights database, A              which lets you manage user access to the system, ande,              displays the following message:  E              Creating RIGHTS database file, SYS$SYSTEM:RIGHTSLIST.DAT I              Ignore any "-SYSTEM-F-DUPIDENT, duplicate identifier" errorsa                    .                    .                    .  /     ENTERING SCSNODE AND SCSSYSTEMID PARAMETERSaB           If you are installing a standalone system, the procedure)           displays the following prompts:   %           * Please enter SCSNODE nameo  $           * Please enter SCSSYSTEMID  D           Enter the SCSNODE name and SCSSYSTEMID that you determined<           as part of the preinstallation tasks in Chapter 2.  D           If you are installing the operating system in a VAXcluster;           environment, you are not prompted to supply theserE           parameters. The procedure calculates these parameters usingsD           the DECnet node name and node address you supplied earlier           in the procedure._    4     3-30 Installing the OpenVMS VAX Operating System u  r      I                                          Postinstallation Tasks Described     I         _________________________________________________________________X  (         Postinstallation Tasks Described             INTRODUCTIONA               After the procedure creates the rights database, it E               displays messages describing postinstallation tasks you $               might want to perform.  I               Important: Note that you do not perform these tasks now butU/               after the installation completes.p           SAMPLE MESSAGED               The tasks displayed on your screen might vary from theG               following example, depending on what options you chose to /               install earlier in the procedure.V  N       After the installation finishes, you might want to do one or more of the       following tasks:  K       o DECOMPRESS THE SYSTEM LIBRARIES - To save space, many of the system E       libraries are shipped in a data-compressed format.  If you have_L       enough disk space, you can decompress the libraries for faster access.)       To data expand the libraries, type:s  $           $ SYS$UPDATE:LIBDECOMP.COM  J       If you do not decompress these libraries, you will experience slower/       response with the HELP and LINK commands.   M       o BUILD A STANDALONE BACKUP KIT - You can build a standalone backup kit N       using the procedure described in the upgrade and installation supplement%       provided for your VAX computer.r  O       o TAILOR THE SYSTEM DISK - You might want to review the files provided or H       not provided during this installation. If you find there are filesL       you want to remove from the system disk (TAILOR OFF) or files you wantD       to add (TAILOR ON), use the following utilities to perform the       desired tailoring.  C           OpenVMS tailoring:             $ RUN SYS$UPDATE:VMSTAILORm  E           DECwindows tailoring:          $ RUN SYS$UPDATE:DECW$TAILOR_  M       Note: The tailor procedure cannot be used to TAILOR ON or to TAILOR OFF_+       files located on an alternate device._  I                         Installing the OpenVMS VAX Operating System  3-31            $     Postinstallation Tasks Described      =           For more information about decompressing the systemrC           libraries, see the section Decompressing System Librariesc=           in Chapter 4. For information on using VMSTAILOR or &           DECW$TAILOR, see Chapter 10.  =           After the messages about postinstallation tasks are_@           displayed, the procedure displays a message similar to           the following:  E              Continuing with OpenVMS VAX V6.2 installation procedure.e  5              Configuring all devices on the system...n  C             You can safely ignore the following NCP error messages.   8           %NCP-W-UNRCMP, Unrecognized component , Object       WHERE TO GO NEXT;           Proceed to the next section for information abouty$           registering your licenses.                                                  4     3-32 Installing the OpenVMS VAX Operating System A  u      I                                                      Registering Licensess    I         _________________________________________________________________            Registering Licenses             INTRODUCTIONI               Before you can use the OpenVMS VAX operating system and its I               components, you must first register all licenses. If you do H               not register your licenses at this point in the procedure,H               you must register them immediately after the installation,B               before you perform the other postinstallation tasks.    %         HOW TO REGISTER YOUR LICENSES_E               You must register your licenses in the following order:s  I               1. Register the OpenVMS VAX license for the VAX computer on_G                  which you have just installed the operating system. IfeH                  you have a VAXcluster environment, you then register anH                  OpenVMS VAX license for each additional VAX computer inH                  the cluster that will boot off the system disk that youG                  just created. Each registered OpenVMS VAX license must A                  be assigned to one of the nodes for the cluster.   I               2. Register the licenses for any System Integrated ProductsD+                  (SIPs) that you purchased.o  &         WHERE TO FIND MORE INFORMATIONF               For more information about registering licenses, see the               following:  A               o  OpenVMS License Management Utility Manual, which                   provides:  G                  -  Details about all LICENSE commands, error messages, ?                     and recovery procedures for licensing tasksm  F                  -  A description of VMSLICENSE.COM, with step-by-step9                     instructions for registering licensesi  I                  -  Examples of license registration using VMSLICENSE.COM_1                     and LICENSE REGISTER commandsn  E               o  Appendix A of this manual for notes and supplemental_0                  information concerning licenses  I                         Installing the OpenVMS VAX Operating System  3-33                 Registering Licenses           TYPES OF LICENSES D           The OpenVMS VAX operating system uses one of two different?           categories of licenses, depending on the hardware and B           software configuration used and currently supported. TheE           two categories of operating system licenses for OpenVMS VAX            are:             o  VAX VMS licensing  "           o  OpenVMS VAX licensing  A           The VAX VMS licenses include the rights for the Rdb/VMS A           Run-Time Option for OpenVMS VAX. This allows you to run @           an application developed using Rdb/VMS for OpenVMS VAXA           software. However, Rdb/VMS for OpenVMS VAX has separatee>           media and documentation. In addition, if you want to?           perform Rdb development, you must purchase a separate @           license. (Refer to SPD 25.59.xx for more information.)  A           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.   E     _________________________________________________________________ %     Type of License       DescriptionfE     _________________________________________________________________r-                              VAX VMS Licenses E     _________________________________________________________________ @     Traditional License   Provides unlimited use to the users on?                           a defined system. VAX VMS traditional B                           licenses are sized to capacity according)                           to system type._                        4     3-34 Installing the OpenVMS VAX Operating System C  T      I                                                      Registering Licenses     I         _________________________________________________________________ )         Type of License       Description I         _________________________________________________________________S1                                  VAX VMS LicensesrI         _________________________________________________________________ C         Multiuser License     Provides use according to a specified_D                               number of concurrent users. This is anC                               activity-based license. The Multiuser_D                               License gives you the right to use theB                               operating system for up to the limitC                               of users specified in the license. An H                               operating system user is one who is loggedE                               into the system or one who is using therF                               operating system software by means otherB                               than login, or both. This license isF                               available only on limited system models,F                               primarily MicroVAX and VAX 4000 systems.  E                               Interactive use of VAX systems licensedeI                               with the Multiuser License can be increased @                               by the addition of the OpenVMS VAXI                               Interactive User License[1] for one or more G                               users. For more information, refer to the H                               description of the OpenVMS VAX Interactive?                               User License later in this table.   E         VAX VMS Workstation   Provides use for a single user on a VAX G         License               workstation. This license type allows one G                               direct login for the single user and then H                               one additional login for system management,                               purposes only.  ?                               Additional interactive use of VAXoD                               workstations licensed with the VAX VMSG                               Workstation License requires the additionX@                               of an OpenVMS VAX Interactive UserH                               License[1] for one or more users. For moreF                               information, refer to the description ofF                               the OpenVMS VAX Interactive User License2                               later in this table.J         _________________________________________________________________ G         [1]The OpenVMS VAX Interactive User License is not supported byVE         the VMS or OpenVMS VAX operating system releases prior to VMSe         Version 5.5.  I                         Installing the OpenVMS VAX Operating System  3-35     _           Registering Licenses    E     _________________________________________________________________ %     Type of License       Description_E     _________________________________________________________________ -                              VAX VMS Licenses E     _________________________________________________________________n@     File and Application  Provides for the noninteractive use ofC     Server License        OpenVMS VAX. OpenVMS based VAXservers are A                           sold with a File and Application Serverv"                           License.  B                           The intent of an OpenVMS based VAXserverA                           is to provide file, print, application,nB                           and compute services to clients who haveE                           remotely submitted their requests for these E                           services. This license type also allows one E                           direct login for system management purposes                            only.r  ?                           Additional interactive use of OpenVMSO?                           VAXservers licensed with the File andqA                           Application Server License requires the_E                           addition of an OpenVMS VAX Interactive User D                           License[1] for one or more users. For moreB                           information, refer to the description ofB                           the OpenVMS VAX Interactive User License.                           later in this table.  E     _________________________________________________________________ /                            OpenVMS VAX Licenses E     _________________________________________________________________ =     OpenVMS VAX O/S Base  Provides the right to unrestricted,O?     License[2]            noninteractive use of the OpenVMS VAXb?                           operating system for the execution of @                           remotely submitted requests for batch,E                           print, application, and computing services,n<                           on a designated, single processor.  @                           No direct OpenVMS VAX operating system>                           logins by users are permitted on theA                           system. One direct login is allowed foro:                           system management purposes only.E     _________________________________________________________________cC     [1]The OpenVMS VAX Interactive User License is not supported by A     the VMS or OpenVMS VAX operating system releases prior to VMS      Version 5.5.C     [2]The OpenVMS VAX O/S Base License is not supported by the VMSMA     or OpenVMS VAX operating system releases prior to VMS Versiono     5.5.  4     3-36 Installing the OpenVMS VAX Operating System t  f      I                                                      Registering Licenses,    E     _________________________________________________________________ %     Type of License       Description E     _________________________________________________________________83                                OpenVMS VAX Licenses E     _________________________________________________________________r  G                               The OpenVMS VAX O/S Base License does notrG                               include the license right for the Rdb/VMSVB                               Run-Time Option for OpenVMS VAX. TheF                               Rdb/VMS for OpenVMS VAX Run-Time License6                               is available separately.  I                               Interactive use of systems licensed with ancG                               OpenVMS VAX O/S Base License requires thepI                               addition of an OpenVMS VAX Interactive Userg?                               License[1] for one or more users.l  E         OpenVMS VAX           Provides the right to interactively usehE         Interactive User      the operating system by a specified, oruF         License[1]            unlimited, number of concurrent users onD                               a designated, single processor. A userD                               is one who is logged in to a processorC                               or one who is interactively using the F                               operating system software by means otherE                               than login, or both. An OpenVMS VAX O/S G                               Base License, or any of the four types ofeI                               VAX VMS Licenses, is a prerequisite for thesC                               OpenVMS VAX Interactive User License.sI         _________________________________________________________________EG         [1]The OpenVMS VAX Interactive User License is not supported bynE         the VMS or OpenVMS VAX operating system releases prior to VMS          Version 5.5.  ,         HOW TO REGISTER OPENVMS VAX LICENSESD               You can use the SYS$UPDATE:VMSLICENSE.COM procedure toF               register a license for any Digital product that suppliesE               a Product Authorization Key (PAK). Or, you can register I               licenses with the LICENSE REGISTER command. See the OpenVMSsI               License Management Utility Manual for detailed information.               I                         Installing the OpenVMS VAX Operating System  3-37f "  r           Registering Licenses      D           The installation procedure displays the following message:  S              If you have any Product Authorization Keys (PAKS) to register, you can               register them now.p  I           * Do you want to register any Product Authorization Keys? (Y/N)S  E     _________________________________________________________________e$     If you choose ...       Then ...E     _________________________________________________________________p-     Not to register the     Do the following:o7     licenses at this time   1. Type N and press Return.a  A                             2. Go to the section Running AUTOGEN.   E                             3. Remember that, after the installation,tE                                you must register your licenses beforemD                                performing any other postinstallation5                                tasks (see Chapter 4)._  -     To register your        Do the following: 7     licenses now            1. Type Y and press Return.D  B                             2. Be sure you have a copy of your PAKB                                for each license you will register.  B                             3. Go to the next section to begin the3                                licensing procedure.UE     _________________________________________________________________S                                4     3-38 Installing the OpenVMS VAX Operating System    l      I                                                      Registering Licensesl      )         BEGINNING THE LICENSING PROCEDUREaI               By typing Y (Yes) to register your licenses now, you invokekI               the SYS$UPDATE:VMSLICENSE.COM procedure, which displays thes                following message:  =                   OpenVMS License Management Utility Options:p  =                       1. REGISTER a Product Authorization KeyoD                       2. AMEND an existing Product Authorization KeyE                       3. CANCEL an existing Product Authorization Keye8                       4. LIST Product Authorization KeysE                       5. MODIFY an existing Product Authorization KeyeF                       6. DISABLE an existing Product Authorization KeyE                       7. DELETE an existing Product Authorization Key C                       8. COPY an existing Product Authorization KeyoC                       9. MOVE an existing Product Authorization KeyeE                      10. ENABLE an existing Product Authorization Keyi>                      11. SHOW the licenses loaded on this nodeA                      12. SHOW the unit requirements for this nodea  ,                      99. Exit this procedure  M                   Type '?' at any prompt for a description of the information O                   requested. Press Ctrl/Z at any prompt to return to this menu.   0               Enter one of the above choices [1]  I               Select the appropriate options (beginning with 1, as shown) G               until you have successfully registered all required PAKs.i  2         HOW TO REGISTER SYSTEM INTEGRATED PRODUCTSB               After you register the OpenVMS VAX license, you mustB               register the license for any of the following System<               Integrated Products (SIPs) you have purchased:                 o  VAXcluster /                  (LMF Product Name: VAXCLUSTER)i  #               o  DECnet for OpenVMS   ;                  There are two DECnet for OpenVMS licenses:e  7                  -  The end node license named DVNETENDn  ;                  -  The routing node license named DVNETRTGe  I                         Installing the OpenVMS VAX Operating System  3-39H    G           Registering Licenses      C                 All routing nodes must have a routing license. Each A                 end node can have either an end node license or anA                 routing license. If neither license is registered A                 and activated, DECnet does not start and your use @                 is limited to local DECnet only (SET HOST 0). IfD                 DECnet for OpenVMS is running when you register yourB                 license, you must stop and then restart DECnet for                 OpenVMS.  E                 You can control which VAXcluster nodes have access totE                 each license. Using the LICENSE MODIFY/INCLUDE=(node-t=                 name[,node-name,...]) command, you can assign A                 licenses to nodes and limit access as needed. For A                 example, you can assign a routing node license tor@                 only one VAXcluster node and assign the end nodeB                 licenses to the remaining VAXcluster nodes. If youD                 choose this approach, make sure you assign a licenseC                 to each end node license. Specify include lists for C                 each license of the same type. For details, see the :                 OpenVMS License Management Utility Manual.  '           o  RMS Journaling for OpenVMSe'              (LMF Product Name: RMSJNL)   >              On systems that do not have registered and loadedA              journaling licenses, users cannot write to any filesu#              marked for journaling.u  )           o  Volume Shadowing for OpenVMSF(              (LMF Product Name: VOLSHAD)  <              You must register and load a license for Volume<              Shadowing for OpenVMS on each node using volumeD              shadowing, including satellites in a VAXcluster system.       WHERE TO GO NEXTD           To complete the installation procedure, continue on to the(           next section, Running AUTOGEN.              4     3-40 Installing the OpenVMS VAX Operating System t  t      I                                                           Running AUTOGENa    I         _________________________________________________________________            Running AUTOGEN              INTRODUCTIONF               The remaining portion of the installation procedure runsA               AUTOGEN to evaluate your hardware configuration and B               estimate typical workloads. AUTOGEN then sets systemF               parameters, the sizes of page, swap, and dump files, andF               the contents of VMSIMAGES.DAT. When AUTOGEN finishes andD               the system has rebooted, the installation procedure is               complete.o             HOW AUTOGEN WORKS B               The installation procedure runs AUTOGEN, as follows:  I               1. The installation procedure displays a series of messagese*                  similar to the following:  9      Running AUTOGEN to compute new SYSTEM parameters ...n  /   %AUTOGEN-I-BEGIN, GETDATA phase is beginning.XN   %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.e        .        .        .  .   %AUTOGEN-I-BEGIN, REBOOT phase is beginning.  @                  If you need to create or modify the size of theG                  pagefile or swapfile, use the SYSMAN utility. For more F                  information, see the OpenVMS System Manager's Manual:                  Essentials.  H               2. After AUTOGEN finishes, the procedure displays a series;                  of shutdown messages that begin like this:   J           The system is shutting down to allow the system to boot with theB           generated site-specific parameters and installed images.  I           The system will automatically reboot after the shutdown and theu#           upgrade will be complete.   8           SHUTDOWN -- Perform an Orderly System Shutdown  I                         Installing the OpenVMS VAX Operating System  3-41                 Running AUTOGEN       @           3. After the system shuts down, the procedure tries to?              reboot the new system disk. If the system does not 6              reboot automatically, reboot it manually.  D              For example, suppose you have a VAX-11/780 computer andA              the system disk is on an RA60 disk drive with a unit_A              number of one. Enter the following command and pressV              Return:                >>> B DUA1_  A              For information on booting, refer to the upgrade and @              installation supplement for your VAX computer. Then#              return to this manual.i                                                              4     3-42 Installing the OpenVMS VAX Operating System           I                                                           Running AUTOGENe      E               4. After the system reboots, the procedure displays the #                  following message:n  L           OpenVMS VAX Version V6.2 Major version id = 1 Minor version id = 0  I           ***************************************************************f             OpenVMS VAX V6.2  K           You have SUCCESSFULLY installed the OpenVMS VAX operating system.   C           The system is now executing the STARTUP procedure. Please E           wait for the completion of STARTUP before logging in to the            system.tI          ****************************************************************l  G                  Note: If you did not register your OpenVMS VAX licensetF                  as described in the section Registering Licenses, theE                  procedure displays warning messages that the OpenVMSrE                  license must be registered. Be sure to register this F                  license when the installation procedure finishes. ForI                  more information, see Appendix A and the OpenVMS Licensea+                  Management Utility Manual.   G                  Finally, the procedure displays informational messages 9                  and accounting information. For example:   M    %SET-I-INTSET, login interactive limit = 64, current interactive value = 0 9    SYSTEM       job terminated at 22-JUN-1995 15:37:04.00       Accounting information:G    Buffered I/O count:       859      Peak working set size:        565SG    Direct I/O count:         478      Peak virtual size:           2570XG    Page faults:             5003      Mounted volumes:                0 G    Charged CPU time:  0 00:00:55.33   Elapsed time:       0 00:01:31.24   B                  At this point the OpenVMS VAX operating system is                  running.h  G               5. Press the Return key. The system asks you for the user F                  name and password. Log into the SYSTEM account so youI                  can perform certain postinstallation tasks. For example:n    I                         Installing the OpenVMS VAX Operating System  3-43r    e           Running AUTOGEN       -                   Welcome to OpenVMS VAX V6.2a                Username: SYSTEM               Password:                   ._                   ._                   ._5                   Welcome to OpenVMS VAX Version V6.2   D              If you forget the password, follow the instructions forB              performing an emergency startup in the OpenVMS System*              Manager's Manual: Essentials.  >           6. There are several postinstallation tasks you mustC              perform before you can use the system. These tasks arer$              described in Chapter 4.                                                          4     3-44 Installing the OpenVMS VAX Operating System O  V                    I                                                                         4 I         _________________________________________________________________   I                                              After Installing OpenVMS VAX   I         _________________________________________________________________i           Overview  H               After you have installed the OpenVMS VAX operating system,H               you need to perform several important tasks to prepare theH               system for operation. This chapter describes the followingC               postinstallation tasks in the order you perform them:n  &               o  Verifying system time  %               o  Registering licenseso  ,               o  Backing up your system disk  (               o  Customizing your system  <               o  Configuring and starting DECnet for OpenVMS  #               o  Testing the systemt  /               o  Decompressing system libraries_  (               o  Removing unwanted files  6               o  Backing up the customized system disk                  o  Running AUTOGEN  :               o  Completing the postinstallation checklist  C               If you are an experienced system manager, you can use E               the checklist at the end of the chapter to complete thei/               necessary postinstallation tasks.t  F               If you are a less-experienced system manager, you shouldH               read the entire chapter and then use the checklist to makeE               sure you have completed all the postinstallation tasks.y  I                                          After Installing OpenVMS VAX 4-1                 Verifying System Timen    E     _________________________________________________________________.       Verifying System Time_         INTRODUCTION@           During the installation, the procedure prompted you toC           enter the date and time. Now that you have installed your D           system, verify that the system time is correct by entering            the following command:             $ SHOW TIMEX  0           The system displays the date and time.       HOW TO RESET SYSTEM TIMED           If the time displayed by your system is not correct, resetA           it by entering the command SET TIME using the following_           format:_  '           SET TIME=dd-mmm-yyyy:hh:mm:ss              For example:  )           $ SET TIME=22-JUN-1995:18:35:30_       COMPENSATING FOR TIME ZONES @           If your system communicates with systems in other time@           zones, you can use the time conversion service and the=           Coordinated Universal Time (UTC) system services to >           compensate for differences in time stamps because ofE           differing time zones. For more information, see the OpenVMSM.           System Manager's Manual: Essentials.                          $     4-2 After Installing OpenVMS VAX s  a      I                                                 Registering Your Licensesc    I         _________________________________________________________________i  !         Registering Your Licenses              BACKGROUNDD               The installation procedure gave you the opportunity toD               register any software product licenses. If you did notI               register your OpenVMS VAX license at that time, you must dobI               so before you can use the OpenVMS VAX operating system. YouuF               must also register the licenses for any of the following<               System Integrated Products you have purchased:                    VAXcluster #                  DECnet for OpenVMSe'                  OpenVMS RMS Journaling -                  Volume Shadowing for OpenVMSh  &         WHERE TO FIND MORE INFORMATIONG               For step-by-step instructions about registering licenses,nC               see the OpenVMS License Management Utility Manual andMD               Appendix A of this manual, which provides supplemental               information.                                              I                                          After Installing OpenVMS VAX 4-3c e  e           Backing Up Your System Disk     E     _________________________________________________________________s       Backing Up Your System Disk          BACKGROUND?           Now that you have spent time installing the operatingrA           system, you should protect your work by making a backup E           copy of the system disk in case you have any problems whilerA           customizing it. Digital recommends that you perform the            following operations:i  C           o  Make a standalone BACKUP kit on the system disk and on               removable media  <           o  Perform a standalone BACKUP of your system disk  A           You should also back up your system disk after you haves           customized it.  "     WHERE TO FIND MORE INFORMATIONB           For complete information about these operations, see theD           upgrade and installation supplement for your VAX computer.                                              $     4-4 After Installing OpenVMS VAX _  _      I                                                    Customizing the System_    I         _________________________________________________________________i           Customizing the System             BACKGROUNDE               You can customize the system to meet the specific needsNE               of your site. In addition, if your VAX computer is partiG               of a VAXcluster environment, you must prepare the clusterr4               environment and configure the cluster.    &         WHERE TO FIND MORE INFORMATIONF               For instructions about customizing your system, refer to               the following:  ?               o  Read the chapter on booting in the upgrade and D                  installation supplement for your VAX computer. ThisH                  chapter explains the different ways to boot the system.?                  It also tells you how to shut down the system.l  E               o  If the computer is part of a VAXcluster environment,_@                  read VMScluster Systems for OpenVMS for further8                  information about setting up a cluster.  I               o  Read the OpenVMS System Manager's Manual: Essentials for G                  instructions on customizing and using your system. YousA                  will find information about the following tasks:$  <                  -  Editing the template files SYCONFIG.COM,F                     SYLOGICALS.COM, SYLOGIN.COM, and SYSTARTUP_VMS.COM  C                  -  Starting the queue manager and creating a queuezD                     database. (If you are installing on a VAXclusterI                     system with multiple system disks, see the VMSclusteroE                     Systems for OpenVMS for additional instructions.)   ,                  -  Setting up user accounts  /                  -  Adjusting system parametersa  A               o  If you plan to use either the DECnet-VAX product C                  included on the OpenVMS VAX Version 6.2 kit or the A                  DECnet/OSI for OpenVMS layered product, read theVD                  section Configuring and Starting DECnet and performE                  the steps described there. If you are installing theOH                  DECnet/OSI for OpenVMS layered product, you should alsoG                  refer to the DECnet/OSI installation and configurationu                  documentation.a  I                                          After Installing OpenVMS VAX 4-5e P  s           Customizing the System      D           o  If you installed DECwindows support software, there areE              several steps you must take to customize your DECwindows @              environment. Depending on your configuration, these!              tasks might include:M  .              -  Customizing the server startup  @              -  Using the Transmission Control Protocol/Internet;                 Protocol (TCP/IP) as a DECwindows transportt  @              -  Using transports for DECwindows other than those#                 supplied by Digitale  D              See Chapter 9 for complete instructions for customizing.              your DECwindows support software.  E           o  If you installed the optional OpenVMS Management Station B              files, see Appendix F for information about preparingE              your OpenVMS system and your PC to use this application.                                                     $     4-6 After Installing OpenVMS VAX s  E      I                                           Configuring and Starting DECnet     I         _________________________________________________________________   '         Configuring and Starting DECnets             INTRODUCTIONF               In local area and mixed-interconnect VAXcluster systems,D               DECnet software is required for both system managementF               functions and for cluster communications, such as remoteG               booting operations. All VAXcluster systems require DECnet I               software, which ensures that system managers can access all :               VAXcluster computers from a single terminal.  D               You can use the DECnet for OpenVMS (Phase IV) softwareE               included on the OpenVMS VAX Version 6.2 kit, or you can ?               install the DECnet/OSI (Phase V) layered product.   I               Both of these products require that you run a configurationtF               procedure to configure the network. If you choose to runH               DECnet for OpenVMS, you must also edit your system startupB               file as described in the section Edit SYSTARTUP_VMS.           CONFIGURE YOUR SYSTEM H               After you have registered your DECnet license, execute oneD               of the following interactive configuration procedures:  @               o  For the DECnet for OpenVMS layered product, runG                  SYS$MANAGER:NETCONFIG.COM. (See the DECnet for OpenVMSn;                  Guide to Networking for more information.)   D               o  For the DECnet/OSI for OpenVMS layered product, runC                  SYS$MANAGER:NET$CONFIGURE.COM. (See the DECnet/OSIiD                  for OpenVMS Installation and Configuration for more                  information.n           EDIT SYSTARTUP_VMSI               If you plan to run DECnet/OSI, you do not need to edit this0;               file because DECnet will start automatically.   ?               If you plan to run DECnet for OpenVMS (Phase IV),OB               after you start the queue manager, edit the commandsE               in SYS$COMMON:[SYSMGR]SYSTARTUP_VMS.COM that pertain to G               networking, so that DECnet starts automatically when your G               system is booted. Choose one of the following commands to D               start the network and remove the comment delimiter (!)                from that command:  I                                          After Installing OpenVMS VAX 4-7  O         #     Configuring and Starting DECnetr      L  $! IF F$SEARCH("SYS$SYSTEM:NETACP.EXE") .NES. "" THEN @SYS$MANAGER:STARTNETV  $! IF F$SEARCH("SYS$SYSTEM:NETACP.EXE") .NES. "" THEN SUBMIT SYS$MANAGER:STARTNET.COM  >           Both of the previous commands perform the same task.E           However, the first command executes STARTNET.COM and delaysNB           further processing until the procedure is completed; theD           second submits STARTNET.COM to a batch queue and continuesE           executing SYSTARTUP_VMS.COM. If you plan to run both DECnetfD           for OpenVMS and DECwindows Motif for OpenVMS VAX, you mustA           also edit SYS$COMMON:[SYSMGR]SYSTARTUP_VMS.COM to add aeB           comment delimiter (!)  immediately following the dollar-?           sign ($)  in the DEFINE DECW$IGNORE_DECNET command ast           follows:  +           $! DEFINE DECW$IGNORE_DECNET TRUEt  B           If you are not going to start DECnet for OpenVMS or haveB           not yet started it, this command tells DECwindows not to           wait for DECnet.                                                    $     4-8 After Installing OpenVMS VAX i  t      I                                     Testing the System with UETP Software     I         _________________________________________________________________p  -         Testing the System with UETP Software              BACKGROUNDC               UETP software is a user environment test package thataI               tests whether the OpenVMS VAX operating system is installedAG               correctly. As part of the postinstallation procedure, youh:               should run UETP to verify your installation.  C               Note that UETP needs at least 1200 free blocks on thepD               system disk and is available only if you installed theD               optional save set VMS062.D. If you did not install theC               optional save set, you can add the UETP files to your %               system using VMSTAILOR.r  &         WHERE TO FIND MORE INFORMATIONC               For information about using VMSTAILOR see Chapter 10.   I               For complete information about UETP, see the OpenVMS System H               Manager's Manual: Tuning, Monitoring, and Complex Systems.                                                I                                          After Installing OpenVMS VAX 4-9e s         "     Decompressing System Libraries    E     _________________________________________________________________r  "     Decompressing System Libraries       BACKGROUNDD           Decompressing the system libraries gives the system fasterE           access to them. You can decompress all the system librariesnD           or just some of them. Table 4-1 gives the number of blocks7           consumed by each library after decompression.l  :           Table 4-1 Sizes of Decompressed System LibrariesE           ___________________________________________________________*@           Library           Blocks      Library           BlocksE           ___________________________________________________________g>           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      102E           ___________________________________________________________r%     4-10 After Installing OpenVMS VAXr a  e      I                                            Decompressing System Librariesr            H               The additional amount of disk space required to decompressF               all the system libraries is about 13,500 blocks. To findC               out how much disk space you have, enter the following /               command and press the Return key:   )               $ SHOW DEVICE SYS$SYSDEVICEh                                                                  I                                         After Installing OpenVMS VAX 4-11  .  e      "     Decompressing System Libraries           HOW TO DECOMPRESS LIBRARIESaC           To decompress the system libraries, you run LIBDECOMP.COM D           by logging into the SYSTEM account, entering the following'           command, and pressing Return:t  %           $ @SYS$UPDATE:LIBDECOMP.COM   1           The following information is displayed:   1                 VMS Library Decompression Utility_           Options:  J         1  HELPLIB.HLB          13  DBG$UIHELP.HLB       25  PATCHHELP.HLBJ         2  STARLET.OLB          14  DBG$HELP.HLB         26  PHONEHELP.HLBD         3  VAXCCURSE.OLB        15  EXCHNGHLP.HLB        27  SDA.HLBJ         4  VAXCRTL.OLB          16  NCPHELP.HLB          28  SHWCLHELP.HLBG         5  VAXCRTLG.OLB         17  ANLRMSHLP.HLB        29  SYSGEN.HLBnE         6  DECCCURSE.OLB        18  DISKQUOTA.HLB        30  TECO.HLBtH         7  DECCRTL.OLB          19  EDFHLP.HLB           31  UAFHELP.HLBI         8  DECCRTLG.OLB         20  TPUHELP.HLB          32  EVE$HELP.HLBuL         9  ERFLIB.TLB           21  ACLEDT.HLB           33  EVE$KEYHELP.HLBI         10  STARLETSD.TLB        22  INSTALHLP.HLB        34  STARLET.MLBgE         11  MAILHELP.HLB         23  LATCP$HELP.HLB       35  LIB.MLB 0         12  EDTHELP.HLB          24  MNRHELP.HLB  3         or    A    ALL libraries to be decompressed &               E    EXIT this procedure  A       * Enter letter or number(s) of libraries to be decompressedu1         (Separate multiple entries with a comma):   <           Enter the appropriate letter or the numbers of the=           libraries you want to decompress. To decompress all C           libraries, the process takes approximately one half hour.   C           If you prefer, you can execute LIBDECOMP interactively or A           as a batch job. If you use either of these methods, youy@           can decompress up to 8 libraries each time you executeB           LIBDECOMP by listing the names of the libraries you wantC           to decompress as parameters on the command line. (You can B           decompress all the libraries by omitting the /PARAMETERS@           qualifier.) Be sure to separate the library names withD           commas and do not include the file extension. For example,C           to decompress the VAXCRTL.OLB, DISKQUOTA.HLB, and LIB.MLBn@           libraries as a batch job, enter the following command:  %     4-12 After Installing OpenVMS VAXT S         I                                            Decompressing System Libraries       C               $ SUBMIT/NOTIFY/PARAMETERS=(VAXCRTL, DISKQUOTA, LIB)-m%               _$ SYS$UPDATE:LIBDECOMPh  I               To decompress these same libraries interactively, enter the3                following command:  ;               $ @SYS$UPDATE:LIBDECOMP VAXCRTL DISKQUOTA LIBe  G               Note that, when you type the command for a batch job, you I               separate the library names with commas and enclose the listpI               within parentheses. You do not use commas or parentheses onz+               the interactive command line.                                                                   I                                         After Installing OpenVMS VAX 4-13            $     Removing or Adding OpenVMS Files    E     __________________________________________________________________  $     Removing or Adding OpenVMS Files         BACKGROUNDD           To remove unwanted OpenVMS VAX files from the system disk,C           use VMSTAILOR or DECW$TAILOR. For example, if you are notfA           running DECnet for OpenVMS, use VMSTAILOR to remove thea'           files associated with DECnet.f  E           Note: You cannot use VMSTAILOR to remove files installed ontB           an alternate device from save sets VMS062.E or VMS062.F.  "     WHERE TO FIND MORE INFORMATION<           For complete information about using VMSTAILOR andB           DECW$TAILOR to remove optional OpenVMS VAX software, see           Chapter 10.n                                                        %     4-14 After Installing OpenVMS VAXc n  b      I                                     Backing Up the Customized System Diski    I         _________________________________________________________________e  -         Backing Up the Customized System Disk              BACKGROUNDI               Now that you have spent time installing and customizing the H               operating system, protect your work by making a standalone-               backup copy of the system disk._    &         WHERE TO FIND MORE INFORMATIONF               For complete information about these operations, see theH               upgrade and installation supplement for your VAX computer.G               Once you have made a standalone backup copy of the systemhF               disk, install any software products that you want to runI               on your system. Follow the directions given in the software +               product installation manuals.r                                                        I                                         After Installing OpenVMS VAX 4-15k t  y           Running AUTOGENz    E     _________________________________________________________________a       Running AUTOGENi         BACKGROUNDB           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.   B           In many cases, AUTOGEN can improve system performance byE           using dynamic feedback information from the running system. B           As a postinstallation task, you should run AUTOGEN againE           using the feedback mechanism to make further adjustments to            system parameters.  <           When AUTOGEN runs, it uses the parameter values inB           SYS$SYSTEM:MODPARAMS.DAT. Note that hard-coded values inE           MODPARAMS.DAT affect AUTOGEN's calculations of the feedbacko?           parameters. For AUTOGEN to properly calculate minimumeB           default values, you should replace the hard-coded valuesB           in MODPARAMS.DAT with MIN_ values. If you need to modifyA           the parameter values calculated by AUTOGEN, you can usetC           AUTOGEN to change the hard-coded values in MODPARAMS.DAT.p  E           For information about using AUTOGEN, see the OpenVMS Systemt'           Manager's Manual: Essentials.        WHEN TO RUN AUTOGENtB           After installing the operating system, run AUTOGEN again(           using the following procedure:  A           1. After 24 hours of operation, run AUTOGEN in feedback (              mode and reboot the system.  B           2. Run AUTOGEN in this same way, again, two working days              later.   @              Note: For large memory systems such as the VAX 9000C              computer, AUTOGEN's initial parameter calculations are E              conservative. To obtain parameter values that match your D              system workload, you can run AUTOGEN in feedback mode aC              number of times. For more information, see the upgraden;              and installation supplement for your computer.   %     4-16 After Installing OpenVMS VAXa           I                                                           Running AUTOGENi      G               3. Digital recommends that you run AUTOGEN from SAVPARAMS @                  through TESTFILES on a weekly basis and examineH                  AGEN$PARAMS.REPORT to determine the need for additional                  changes.s           WHAT TO DO NEXT C               After you run AUTOGEN following the first 24 hours of A               system operation (step 1), use the Postinstallation E               Checklist to make sure you have completed all the tasks (               described in this chapter.                                                                      I                                         After Installing OpenVMS VAX 4-17s a  t           Postinstallation Checklist    E     _________________________________________________________________s       Postinstallation Checklist         INTRODUCTIONB           Use the following checklist to make sure you perform all/           the necessary postinstallation tasks.a         DID YOU . . .   C           <  Verify the system time? (Described in Verifying System               Time.)b  C           <  Register your licenses if you did not do so during thecE              installation procedure? (Described in Appendix A of this A              manual and in the OpenVMS License Management Utility               Manual.)d  A           <  Build a standalone BACKUP kit on the system disk andm>              on removable media? (Described in the upgrade and8              installation supplement for your computer.)  :           <  Back up the system disk as a safeguard beforeB              customizing the system? (Described in the upgrade and8              installation supplement for your computer.)  <           <  Customize the system? (Described in the section%              Customizing the System.)c  B           <  Configure and start DECnet for OpenVMS? (Described in:              the section Configuring and Starting DECnet.)  E           <  Run UETP (the User Environment Test Package) to test the C              system? (Described in OpenVMS System Manager's Manual: 6              Tuning, Monitoring, and Complex Systems.)  A           <  Decompress the system libraries using LIBDECOMP.COM? =              (Described in the Decompressing System Libraries               section.)  A           <  Remove unwanted files from the system disk using theOB              OpenVMS tailoring utility? (Described in Chapter 10.)  B           <  Back up the system disk after you have customized it?B              (Described in the upgrade and installation supplement               for your computer.)  %     4-18 After Installing OpenVMS VAXc e  n      I                                                Postinstallation Checklist       B               <  Run AUTOGEN after the system has been running forC                  at least 24 hours to collect feedback information? <                  (Described in the section Running AUTOGEN.)                                                                                    I                                         After Installing OpenVMS VAX 4-19e S  o                    I                                                                         5/I         _________________________________________________________________   I                                     Before Upgrading OpenVMS VAX Softwaref  I         _________________________________________________________________e           Overview  F               Before you begin an upgrade, you need to perform severalA               important tasks to prepare the system. This chaptereF               describes what you need to know and do to prepare for an!               upgrade, including:w  =               o  Being aware of the cautions and restrictions   E               o  Making sure your hardware is ready and your software -                  distribution kit is completel  0               o  Examining AUTOGEN feedback data  ,               o  Backing up your system disk  +               o  Preparing your system diskg  &               o  Preparing your system  D               o  Gathering the information for the upgrade procedure  4               o  Completing the preupgrade checklist  C               If you are an experienced system manager, you can use F               the checklist at the end of this chapter to complete the)               necessary preupgrade tasks.r  F               If you are a less-experienced system manager, you shouldH               read the entire chapter and then use the checklist to make?               sure you have completed all the preupgrade tasks.n        I                                 Before Upgrading OpenVMS VAX Software 5-1R S  T           Cautions and Restrictionsn    E     _________________________________________________________________t       Cautions and Restrictionsa         INTRODUCTIONB           Before you begin the upgrade, take note of the following$           cautions and restrictions.         CAUTIONS  >           o  If you have the DECset Version 11 layered product:              installed on your system, you must remove the?              @DEBUG$STARTUP.COM command from the system startupt=              procedure. The debugger shipped with OpenVMS VAXw?              Version 6.2 is a superset of the debugger that was_B              shipped with the DECset Version 11 software. RemovingC              the @DEBUG$STARTUP.COM command will cause the debuggersC              shipped with OpenVMS VAX Version 6.2 to be the defaulth              system debugger.i  @              To remove the @DEBUG$STARTUP.COM command before you?              upgrade the operating system software, perform thei              following steps:o  <              1. Log in to an account with system privileges.  9              2. Using the editor of your choice, open the A                 SYS$STARTUP:SYSTARTUP_VMS.COM file and search for &                 the following command:                    $ @DEBUG$STARTUP  C                 Delete the command and any parameters. (The commandIA                 might have an optional parameter of either VMS or                  DECSET.)  6              3. Exit from the file, saving the change.  E              If you do not remove this command before you upgrade the D              operating system software, you must remove it after theB              upgrade, and you must deassign the logicals that wereE              defined by DEBUG$STARTUP.COM by performing the following_              steps:_  B              1. Log in to the account that you used to perform the                 upgrade.  -     5-2 Before Upgrading OpenVMS VAX Software            I                                                 Cautions and Restrictionso      1                  2. Enter the following commands:   +                     $ DEASSIGN/SYSTEM DEBUGl.                     $ DEASSIGN/SYSTEM DEBUGSHR0                     $ DEASSIGN/SYSTEM DEBUGUISHR/                     $ DEASSIGN/SYSTEM DBGTBKMSGi.                     $ DEASSIGN/SYSTEM DBG$HELP0                     $ DEASSIGN/SYSTEM DBG$UIHELP3                     $ DEASSIGN/SYSTEM DEBUGAPPCLASS 1                     $ DEASSIGN/SYSTEM VMSDEBUGUILT                                                                      I                                 Before Upgrading OpenVMS VAX Software 5-3  4              Cautions and Restrictions       D              3. Using the editor of your choice, open the SYSTARTUP_B                 VMS.COM file and search for the following command:                    $ @DEBUG$STARTUP  C                 Delete the command and any parameters. (The command1A                 might have an optional parameter of either VMS or1                 DECSET.)  6              4. Exit from the file, saving the change.  A           o  The Version 6.2 upgrade procedure provides new files.A              and directories in the directory [VMS$COMMON...]. IfP?              you had any special protections and access controlHA              lists (ACLs) before the upgrade, you need to reapplyLA              them to reestablish the security environment you had E              previously established. For more information on creating1B              and maintaining a secure environment, see the OpenVMS&              Guide to System Security.  @           o  Before you perform an upgrade, remove or rename anyC              special testing or debugging files that you might haverE              in any of the SYS$SPECIFIC: or SYS$SYSROOT: directories.n@              Files in these directories are used in place of the.              files in SYS$COMMON: directories.  9              As a minimum, you should check the followingw              directories:   !              SYS$SYSROOT:[SYSEXE] "              SYS$SYSROOT:[SYS$LDR]  B              Because the upgrade procedure affects the SYS$COMMON:A              directories and does not check or alter the contents1>              of the SYS$SPECIFIC: or SYS$SYSROOT: directories,B              any testing or debugging files that you have in theseC              directories remain there unchanged until you remove oraE              rename them. If you do not remove or rename these files,tA              your system might behave in an unpredictable manner.n  D           o  The upgrade procedure does not work across the network.D              DECnet for OpenVMS is not available during the upgrade,C              so you must have the save sets available locally or on               the InfoServer.  -     5-4 Before Upgrading OpenVMS VAX Software5 X  G      I                                                 Cautions and Restrictions       G               o  If the node you are upgrading is a cluster member, the2C                  upgrade procedure checks the previously set values E                  of several system parameters at the beginning of the I                  upgrade (see the section Beginning the Upgrade Procedure G                  in Chapter 7). If any of the values are less than that D                  required to upgrade to OpenVMS VAX Version 6.2, youD                  are given the choice of continuing or canceling theD                  upgrade. If you choose to continue the upgrade, theF                  entire upgrade might not be completed and the cluster/                  might be left in a hung state.e  B               o  If you changed the names of system directories onF                  your system disk, the upgrade procedure will not workB                  correctly. Restore your system disk to a standardC                  directory structure before you attempt an upgrade.o  B               o  If you use your AUTOGEN feedback data, you shouldB                  save this information before rebooting the systemD                  with minimum startup to begin the upgrade. For moreH                  information, see the section Examining AUTOGEN Feedback                  Data.  E               o  If you elect not to install optional components, the C                  upgrade procedure removes existing files for thoseuA                  components from the system disk. You can installmA                  optional files during the upgrade or later usingo                  VMSTAILOR.D  H                  Note: Some optional files can be placed on an alternateG                  device. You cannot tailor files on or off an alternate                   device.  A               o  Do not attempt to use VMSINSTAL with OPTION G to F                  transfer OpenVMS VAX save sets to another media type;G                  doing so will produce an unusable system. Instead, yousF                  can use the DCL command COPY to transfer save sets to$                  another media type.  ?                  If you move the OpenVMS VAX save sets from thedD                  distribution media to the system disk or some otherF                  disk before beginning the upgrade, the save sets mustI                  be in the [000000] directory of the disk, or the upgradee                  will fail.   F               o  You must not move the system disk or the distributionB                  kit from one drive to another during the upgrade.  I                                 Before Upgrading OpenVMS VAX Software 5-5_ _  _           Cautions and Restrictionsi      C           o  Before you start the upgrade procedure in a VAXclusterVD              environment, you must shut down all the nodes that bootB              from the system disk you are upgrading, including the-              node you perform the upgrade on.   ?           o  The upgrade procedure deletes all the operator andRA              accounting logs. To save these files, move them to as9              user directory before you start the upgrade.F  ;           o  OpenVMS VAX Version 6.2 software creates a newL?              proxy database that is managed by the new securityw<              server process. After upgrading to Version 6.2,9              you must convert your current proxy databaseM8              (SYS$SYSTEM:NETPROXY.DAT) to the new format(              (SYS$SYSTEM:NET$PROXY.DAT).  A              At the end of an upgrade, the procedure runs AUTOGEN_C              and reboots the system. At that time (or at some later >              reboot), you might get one of the following error              messages:  K     %SYSTEM-W-PROXYCONVERT, old-format proxy database needs to be converted E     %SYSTEM-W-PROXYMISSING, old-format proxy database file is missingE  D              The first message (%SYSTEM-W-PROXYCONVERT) is displayed>              if the procedure detects an existing NETPROXY.DAT=              file without a corresponding NET$PROXY.DAT file.dB              This message indicates that you need to run the proxyE              database conversion utility to convert the database. ForlC              information about running this conversion utility, seelA              Converting Your Network Proxy Database in Chapter 8.   E              The second message (%SYSTEM-W-PROXYMISSING) is displayedXB              if the procedure detects an existing new format proxyD              database file (NET$PROXY.DAT) but not the correspondingB              old format file (NETPROXY.DAT). When you convert yourA              proxy database, do not delete the old proxy databasee@              file. DECnet Phase IV and many layered products useA              the old file. If you delete the NETPROXY.DAT file by D              mistake, you can restore it from the backup copy of theD              system disk that you make before performing an upgrade.        -     5-6 Before Upgrading OpenVMS VAX Softwaren T  N      I                                                 Cautions and Restrictions                RESTRICTIONS  C               o  Before you can upgrade to OpenVMS VAX Version 6.2, H                  your system must be running at least Version 6.0 of theI                  OpenVMS operating system. For example, you can upgrade aeH                  system disk to Version 6.2 of the OpenVMS VAX operatingF                  system from any of the following versions (or related$                  hardware releases):  +                     OpenVMS VAX Version 6.0T+                     OpenVMS VAX Version 6.1g  H               o  If you want to use DECwindows software with OpenVMS VAXE                  Version 6.2, you must install Version 1.1 or greatersH                  of the DECwindows Motif for OpenVMS VAX layered productG                  if it is not already installed on your system. You can:H                  install this layered product either before or after you%                  perform the upgrade.   9               o  If you have a shared system dump file innF                  SYS$COMMON:[SYSEXE], the shared dump file cannot haveG                  the name SYSDUMP.DMP. If you have a shared system dumptH                  file with this name, Digital recommends that you rename=                  it to SYS$COMMON:[SYSEXE]SYSDUMP_COMMON.DMP.U  C               o  You cannot upgrade a shadowed system disk. If youraE                  system disk is part of a shadow set, you must createuH                  a nonshadowed system disk before beginning the upgrade.  D                  Also, if you copy the distribution media to another<                  disk, that disk must be a nonshadowed disk.  C                  For more information, see the Volume Shadowing fora                  OpenVMS.   E               o  The upgrade procedure is designed so that you should B                  not have to reinstall most layered products afterB                  the upgrade. However, you might need to reinstallE                  certain layered products because of product-specifick)                  installation procedures.   ?                  If a layered product is available yet exhibits D                  unexpected behavior once Version 6.2 of the OpenVMSC                  VAX operating system is running, check the OpenVMStG                  Version 6.2 Release Notes for possible layered-product_E                  restrictions. For the most current information aboutR  I                                 Before Upgrading OpenVMS VAX Software 5-7                 Cautions and Restrictionss      E              OpenVMS VAX layered products, contact your Digital sales               representative.                                                                                      -     5-8 Before Upgrading OpenVMS VAX Software  A  n      I                                                 Are You Ready to Upgrade?     I         _________________________________________________________________y  !         Are You Ready to Upgrade?a             INTRODUCTIONC               Before you begin to upgrade the OpenVMS VAX operatingrF               system, make sure you have all the required hardware and"               software components.             HARDWARE COMPONENTS 6               Examine your hardware for the following:  D               o  Make sure your hardware has been checked for properE                  operation. To perform a successful upgrade, you must D                  understand the basic operations of the VAX computerA                  that you are upgrading. Refer to the upgrade andcF                  installation supplement for your VAX computer. If youC                  have a VAXcluster environment, refer to VMSclusters%                  Systems for OpenVMS.m  F               o  Set up your system to record the upgrade procedure onD                  either a hardcopy terminal or a printer attached toH                  the console terminal. If you do not do this, the screenE                  messages will be lost. You will need a transcript insE                  case there is a problem during the upgrade. For moreuI                  information, see the upgrade and installation supplement '                  for your VAX computer.n  H               o  Have scratch console media (media that does not containH                  files you want to save) available for the following VAX                  computers:e  "                     VAX 8600, 8650.                     VAX 8200, 8250, 8300, 8350                     VAX-11/730                     VAX-11/750#                     VAX-11/780, 785   D                  For example, if you have a VAX-11/780 or VAX-11/785C                  computer, you need a scratch RX01 floppy diskette.         I                                 Before Upgrading OpenVMS VAX Software 5-9_ _  _           Are You Ready to Upgrade?            SOFTWARE COMPONENTSo2           Examine your software for the following:  C           o  Make sure you have all the items listed on the bill of E              materials (BOM) in the OpenVMS distribution kit. If youroC              kit is incomplete, notify Digital Software Supply, and <              request priority shipment of any missing items.  D           o  Before upgrading the OpenVMS VAX operating system, readC              Appendix A of this manual, the OpenVMS Version 6.2 NewMD              Features Manual, the OpenVMS Version 6.2 Release Notes,:              and any cover letters included with your kit.                                                                  .     5-10 Before Upgrading OpenVMS VAX Software g         I                                           Examining AUTOGEN Feedback Datai    I         _________________________________________________________________k  '         Examining AUTOGEN Feedback Datan             BACKGROUNDF               After the upgrade is finished, AUTOGEN runs. If it findsI               valid feedback data on your system, it tries to use AUTOGENuH               feedback. Feedback data is produced by the SAVPARAMS phaseG               of AUTOGEN and is stored in SYS$SYSTEM:AGEN$FEEDBACK.DAT.u8               Valid feedback data is defined as follows:  A               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._  D               Note: If your feedback data is not valid, AUTOGEN willC               run without feedback (all previous feedback-generated C               parameters will be replaced by the AUTOGEN NOFEEDBACKo               calculations).  "         HOW TO CHECK FEEDBACK DATAI               To ensure that AUTOGEN feedback will run after the upgrade,n               do the following:   D               1. Check the validity of your current feedback data by0                  entering the following command:  8                  $ @SYS$UPDATE:AUTOGEN GETDATA TESTFILES  F                  This command is for test purposes and does not resultG                  in the modification of system parameters or changes tohE                  the page and swap files. If your current feedback isTG                  valid, AUTOGEN will use it during the upgrade, and youo1                  can proceed to the next section.o  G                  If your current feedback data is invalid, AUTOGEN will I                  issue several warnings. If you get these warnings, go toR                  Step 2.  F               2. If your current feedback is invalid, you can generateF                  new feedback data (assuming your system was up for at>                  least 24 hours). Enter the following command:  :                  $ @SYS$UPDATE:AUTOGEN SAVPARAMS TESTFILES  I                                Before Upgrading OpenVMS VAX Software 5-11m    s      #     Examining AUTOGEN Feedback Data       B              This command is for test purposes and does not resultC              in the modification of system parameters or changes tofE              the page and swap files. Again, AUTOGEN warns you if thee4              feedback data just produced is invalid.  A           3. If you follow Steps 1 or 2 and your current feedbacka?              data is valid, AUTOGEN uses your current feedback- B              generated parameters during the upgrade. Your currentB              feedback-generated parameters will not be lost during              the upgrade.                                                                       .     5-12 Before Upgrading OpenVMS VAX Software N  S      I                                                              Backup Tasks     I         _________________________________________________________________L           Backup Tasks             INTRODUCTIONG               Digital recommends that you make a standalone backup copy F               of the system disk and, if your configuration allows it,F               upgrade the backup copy. If there are problems, you will/               still have a working system disk.T    &         HOW TO BACK UP THE SYSTEM DISKB               To make a backup copy of the system disk, follow theE               instructions in the upgrade and installation supplement C               for your VAX computer. If you do not have a removable G               system disk, back up your system disk to tape and restorecG               the image backup to the system disk. This eliminates diskeE               fragmentation on the system disk and creates contiguous I               free disk blocks required for the upgrade. (The upgrade can G               fail if there are not sufficient contiguous free blocks.)e5               Store the backup tapes in a safe place.   $         HOW TO BACK UP CONSOLE MEDIAF               If you have one of the following VAX computers, you also;               must make a backup copy of the console media:.                    VAX-11/730f                  VAX-11/750a                   VAX-11/780, 7857                  VAX 8200, 8250, 8300, 8350, 8600, 8650i  A               To make a backup copy of the console media, use the D               SYS$UPDATE:CONSCOPY.COM procedure, as described in theH               upgrade and installation supplement for your VAX computer.I               Use the backup copy of the console media during the upgrade[H               procedure. The upgrade procedure updates the console media               for you.  D               If your VAX computer uses one of the following consoleI               media, you did not receive a new standalone BACKUP kit with,0               your OpenVMS VAX distribution kit:  $                  TU58 tape cartridge                  RX33 diskette                  RX50 diskette  I                                Before Upgrading OpenVMS VAX Software 5-13y m  g           Backup Tasks                    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 theA           STABACKIT.COM procedure as described in the upgrade and 8           installation supplement for your VAX computer.  B           Note: You cannot build standalone BACKUP on TU58 or RX01B           console media because the OpenVMS VAX Version 6.2 kit isD           too large. If your VAX computer uses a TU58 or RX01, buildA           a standalone BACKUP kit before upgrading and retain theiD           backup copies for use with future versions of OpenVMS VAX.                                                              .     5-14 Before Upgrading OpenVMS VAX Software           I                                                Preparing Your System Disk     I         _________________________________________________________________h  "         Preparing Your System Disk             INTRODUCTIONC               To prepare the system disk for the upgrade, log in tosF               the SYSTEM account and, depending on your configuration,:               complete some or all of the following tasks:    (         CREATE A NONSHADOWED SYSTEM DISKF               If you are using a volume-shadowed system disk, you mustE               create a nonshadowed system disk to upgrade. Follow thevH               instructions in the Volume Shadowing for OpenVMS manual to@               prepare a nonshadowed system disk for the upgrade.  0         BOOT THE BACKUP COPY OF YOUR SYSTEM DISKH               If you need to boot the backup copy of your system disk orF               if you are upgrading a VAXcluster environment, enter theA               following command (otherwise, go to the next step):i  $               $ @SYS$SYSTEM:SHUTDOWN  C               When the procedure asks if an automatic system rebootAD               should be performed, press Return for NO. If you are aI               VAXcluster member, choose the CLUSTER_SHUTDOWN option. When E               the procedure is finished, halt the system as described E               in the upgrade and installation supplement for your VAXA               computer.d  G               If applicable, remove the system disk and replace it withd               the backup copy.  F               Boot the system from the backup copy of the system disk.E               If you do not know how to boot the system, refer to theoH               upgrade and installation supplement for your VAX computer.  +               Log in to the SYSTEM account.u              I                                Before Upgrading OpenVMS VAX Software 5-15     r           Preparing Your System Disk      2     COPY UAF AND AUDITING FILES TO THE SYSTEM DISKA           The current copies of the SYSUAF.DAT and the VMS$AUDIT_ E           SERVER.DAT files must be on the system disk; otherwise, youS*           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: If you are doing a rolling upgrade, the shared/           version of SYSUAF.DAT is not updated.r  A           Move any files that you do not want changed into a user6           directory.       RENAME THE SYSTEM DUMP FILEh2           If you have a shared system dump file inC           SYS$COMMON:[SYSEXE], the shared dump file cannot have theoA           name SYSDUMP.DMP. If you have a shared system dump fileXB           with this name, Digital recommends that you rename it to0           SYS$COMMON:[SYSEXE]SYSDUMP-COMMON.DMP.       ANALYZE THE SYSTEM DISK C           To analyze the system disk for inconsistencies and errors =           in the file structure, enter the following command:   0           $ ANALYZE/DISK_STRUCTURE SYS$SYSDEVICE  C           The following message represents normal behavior; you can-           ignore it:  8           %ANALDISK-I-OPENQUOTA, error opening QUOTA.SYS  E           If you find any other errors on the system disk, repair thei3           errors by entering the following command:s  7           $ ANALYZE/DISK_STRUCTURE/REPAIR SYS$SYSDEVICEi  D           Refer to the OpenVMS System Management Utilities ReferenceC           Manual for more information on the ANALYZE/DISK_STRUCTUREr           command.  .     5-16 Before Upgrading OpenVMS VAX Software k  o      I                                                Preparing Your System DiskS      !         CHECK PAGE AND SWAP FILESrE               Digital recommends that the page file be located on theeC               system disk in SYS$SPECIFIC:[SYSEXE] for the upgrade.i  E               The swapfile (SWAPFILE.SYS) does not need to be located >               on the system disk for the upgrade, but if it isE               located on the system disk, the file must be located in $               SYS$SPECIFIC:[SYSEXE].  D               If the upgrade procedure finds the page files and swapE               files in the common directory, it will move them to the :               system-specific directory before continuing.  C               The page file be at least 4600 blocks. If the upgradeiE               procedure detects fewer than 4600 blocks, it displays arI               message that gives you the option of continuing the upgradeiE               or exiting the procedure and increasing the size of theeI               page file. If you get this message, Digital recommends that H               you exit the procedure, increase the page file to at least=               4600 blocks, and restart the upgrade procedure.s  I               To check the size of your page file and enter a new size ifn2               needed, use the following procedure:  B               1. To determine the size of the page file, enter the#                  following command:   (                  $ @SYS$UPDATE:SWAPFILES  E                  The procedure displays the size of the page file ande;                  asks you to enter a new value, as follows:a  0                  Enter new size for paging file:  E                  If the page file (PAGEFILE.SYS) size is greater thansF                  4600 blocks, press the Return key. If it is less than:                  4600 blocks, enter 4600 and press Return.  G               2. If the swap and dump files are on the system disk, theaG                  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, theE                  procedure asks if you want to create one. You do notsD                  need swap and dump files on the system disk for theF                  upgrade procedure. Enter the appropriate response for                  your system..  I                                Before Upgrading OpenVMS VAX Software 5-17                 Preparing Your System Disk      B              If you changed the size of the page file or created a@              swap file, a message is displayed that tells you toB              reboot the system. Do not reboot now. You will reboot              later.        CHECK FOR FREE BLOCKS A           Check the system disk to make sure there is enough room E           for the upgrade. To determine whether you have enough room, &           enter the following command:  %           $ SHOW DEVICE SYS$SYSDEVICEs  @           To upgrade the OpenVMS VAX required files, the minimumD           number of free blocks required is 51,550. Even if you planE           to upgrade the OpenVMS library or optional files, you might B           not need more than 51,550 free blocks because many files@           are deleted as the upgrade progresses, thus freeing up           additional space.e       CHECK QUOTAS AND LIMITS.@           Use the Authorize utility (AUTHORIZE) to make sure theC           SYSTEM account has sufficient quotas and limits. To check B           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   D              AUTHORIZE displays the SYSTEM account's quota and limit              values.  ?           2. Compare the values displayed on your screen to them/              following minimum required values:   E              ________________________________________________________ >              Quota or Limit Name                 Minimum_ValueE              ________________________________________________________ 6              Open file quota (FILLM)               100  6              Buffered I/O limit (BIOLM)             18  6              Direct I/O limit (DIOLM)               18  .     5-18 Before Upgrading OpenVMS VAX Software t  e      I                                                Preparing Your System Disk     I                  ________________________________________________________ C                  Quota or Limit Name                  Minimum Value I                  ________________________________________________________ :                  AST limit (ASTLM)                      24  :                  Enqueue quota (ENQLM)                 200  ;                  Buffered byte quota count (BYTLM)   32768+aI                  ________________________________________________________ G                  +If you are using an InfoServer device to upgrade your >                  system, increase the value of BYTLM to 33150.  H               3. If necessary, adjust the quota and limit values in yourI                  SYSTEM account so that they are equal to or greater than -                  the minimum required values.-  D                  To change the value for a quota or limit, enter theB                  MODIFY SYSTEM command using the following format:  .                  MODIFY SYSTEM/limit=new_value                    For example:X  ,                  UAF> MODIFY SYSTEM/DIOLM=18  E               4. Exit the Authorize utility by entering the followingw                  command:                     UAF> EXIT  I               5. If you adjusted the values for any of the SYSTEM accountnF                  quotas or limits, log out and log back in to have the(                  new values take effect.           SET SYSTEM PARAMETERS C               During the upgrade procedure, the system is shut downtF               and rebooted a number of times. You must boot the systemB               minimum (STARTUP_P1 set to MIN) before you begin theG               upgrade (see Preparing the System). This prevents startupiH               of certain system integrated products and layered productsA               on the system during each reboot. To set the system H               parameter STARTUP_P1 to MIN, enter the following commands:  %               $ RUN SYS$SYSTEM:SYSMAN_,               SYSMAN> PARAMETERS USE CURRENT5               SYSMAN> PARAMETERS SET STARTUP_P1 "MIN" .               SYSMAN> PARAMETERS WRITE CURRENT               SYSMAN> EXIT  I                                Before Upgrading OpenVMS VAX Software 5-19     d           Preparing Your System Disk      A           Make sure the system parameters SCSNODE and SCSSYSTEMIDE@           are defined on your system. To determine whether theseD           parameters are defined on your system, enter the following           commands:   !           $ RUN SYS$SYSTEM:SYSMAN )           SYSMAN> PARAMETERS SHOW SCSNODEr-           SYSMAN> PARAMETERS SHOW SCSSYSTEMIDe  E           If SCSNODE and SCSSYSTEMID are not set correctly, enter thekE           following commands where node is a 1- to 6-character uniquepA           DECnet node name and systemid is (DECnet area * 1024) +            node number:  (           SYSMAN> PARAMETERS USE CURRENT/           SYSMAN> PARAMETERS SET SCSNODE "node" 5           SYSMAN> PARAMETERS SET SCSSYSTEMID systemidv*           SYSMAN> PARAMETERS WRITE CURRENT              .              .              .                                                .     5-20 Before Upgrading OpenVMS VAX Software t         I                                                Preparing Your System Diskm      F               Make sure the system parameter VMS5 is set to 0. If yourE               system has a KFQSA controller, the VMS5 parameter mightuF               have been set to a nonzero value for a previous upgrade.D               The VMS5 parameter is reserved for Digital's use only.  A               To check the value of the VMS5 parameter, enter thes!               following commands:      $ RUN SYS$SYSTEM:SYSMANr    SYSMAN> PARAMETERS USE CURRENT   SYSMAN> PARAMETERS SHOW VMS5N   Parameter Name           Current   Default   Minimum   Maximum Unit  DynamicN   --------------           -------   -------   -------   ------- ----  -------@   VMS5                           1         0         0        -1  C               If the current value of VMS5 is not 0, set it to 0 byk.               entering the following commands:  ,               SYSMAN> PARAMETERS USE CURRENT+               SYSMAN> PARAMETERS SET VMS5 0a.               SYSMAN> PARAMETERS WRITE CURRENT               SYSMAN> EXIT  D               If you used the Snapshot facility to boot your currentF               system with a system snapshot image, you must change theH               BOOT_STYLE system parameter to 0 before you can perform anF               upgrade. To change the BOOT_STYLE system parameter to 0,+               enter the following commands:   %               $ RUN SYS$SYSTEM:SYSMAN ,               SYSMAN> PARAMETERS USE CURRENT1               SYSMAN> PARAMETERS SET BOOT_STYLE 0e.               SYSMAN> PARAMETERS WRITE CURRENT               SYSMAN> EXIT               $   ?               You can re-execute the Snapshot command procedure_H               (SYS$MANAGER:SNAPSHOT.COM) after the upgrade is completed,B               as described in the OpenVMS System Manager's Manual:               Essentials.d          I                                Before Upgrading OpenVMS VAX Software 5-21r r  e           Preparing Your System Disk           CHECK AGEN$INCLUDE FILES;           During an upgrade, user disks are not mounted andkC           SYLOGICALS.COM is not invoked, so AUTOGEN can access only ?           data files that are on the system disk and whose fileVB           specification includes a logical name that is shipped asE           part of the OpenVMS operating system. Therefore, if you usemC           AGEN$INCLUDE in SYS$SYSTEM:MODPARAMS.DAT to point to datarC           files that are not on the system disk, follow these steps (           before you perform an upgrade:  A           1. Copy any files that you want AUTOGEN to include to an*              directory on the system disk.  9           2. For each file that you move, change the fileC6              specification on the AGEN$INCLUDE line inB              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 availableB           during the upgrade and parameters might be set to values6           considerably different from what you intend.  3     ADD MODIFIED SYSTEM PARAMETERS TO MODPARAMS.DATsC           Any system parameter values that you modified and did notf@           enter in MODPARAMS.DAT are lost during the upgrade. ToB           retain the values of these parameters, enter their namesE           in MODPARAMS.DAT and the value that AUTOGEN needs to add too$           the default minimum value.  <           For example, if you modified GBLPAGES by 128 pages6           above the default, add the following line to#           SYS$SYSTEM:MODPARAMS.DAT:k             ADD_GBLPAGES=128  D           When AUTOGEN runs after the upgrade, it uses the values in           MODPARAMS.DAT.  D           The following section, Preparing the System, tells you how2           to get your system ready for an upgrade.        .     5-22 Before Upgrading OpenVMS VAX Software    o      I                                                      Preparing the Systemk    I         _________________________________________________________________            Preparing the System  F               To prepare the system for the upgrade, use the following               procedure:  ,         ENABLE AUTO RESTART OR MANUAL REBOOTF               If your computer uses console media, set the computer toF               restart automatically. For some VAX computers this meansB               setting one or more switches. For others, this meansI               entering certain console mode commands. To determine how to H               enable auto restart, refer to the upgrade and installation/               supplement for your VAX computer.   C               If you have a system that does not use console media,_@               set your system so you can reboot it manually. ForE               more information, refer to the upgrade and installationg/               supplement for your VAX computer.t  '         SHUT DOWN AND REBOOT THE SYSTEM D               Shut down and reboot the system to activate any systemG               parameters that you changed (STARTUP_P1, for example). Toh@               shut down the system, enter the following command:  $               $ @SYS$SYSTEM:SHUTDOWN  C               When the procedure asks if an automatic system reboot H               should be performed, type Y (for YES) and press the Return               key.  E               After the system reboots, log in to the SYSTEM account.f  "         PREVENT INTERACTIVE LOGINSG               To prevent users from logging in to the system during thel3               upgrade, enter the following command:   (               $ SET LOGINS/INTERACTIVE=0                I                                Before Upgrading OpenVMS VAX Software 5-23f e  p           Preparing the System            CHECK FOR DECNET FOR OPENVMS@           To determine whether your system is running DECnet for8           OpenVMS software, enter the following command:  !           $ SHOW LOGICAL SYS$NODEe  E           If the system displays the following message, DECnet is notlC           running on your system and you can proceed to the sectionk           Stop Queues:  B           %SHOW-S-NOTRAN, no translation for logical name SYS$NODE  A           If the system responds with a translation for SYS$NODE, 0           then DECnet is running on your system.  B           If you set STARTUP_P1 to MIN as described in the sectionA           Set System Parameters, DECnet should not be running. To B           set STARTUP_P1 to MIN, repeat all of the preceding stepsE           beginning with the section Set System Parameters. Note thatnB           you must shut down and reboot the system for any changes7           you make to system parameters to take effect.        CHECK FOR VOLUME SHADOWING;           Phase I (controller-based) shadowing is no longeraC           available. Phase II (host-based) shadowing is designed tooE           fully replace phase I shadowing with significantly enhanced            features.S  ?           If you have volume shadowing installed on your systemSA           but are unsure which phase, you can enter the followinge           commands:a  !           $ RUN SYS$SYSTEM:SYSMANS(           SYSMAN> PARAMETERS USE CURRENT+           SYSMAN> PARAMETERS SHOW SHADOWINGo  E           If the SHADOWING parameter is 1 or 3, then you have phase I D           shadowing currently loaded on your system. For information?           about migrating to phase II, see Volume Shadowing forU           OpenVMS.  B           At the beginning of an upgrade, the procedure checks theD           setting of the SHADOWING system parameter. If you have notE           migrated to phase II and the procedure detects the presenceiE           of phase I shadowing, it displays the following message andt3           asks if you want to continue the upgrade:K  .     5-24 Before Upgrading OpenVMS VAX Software e  g      I                                                      Preparing the SystemS      H            The SHADOWING system parameter (currently set to 1) specifiesJ            phase I of volume shadowing, which is no longer available as ofN            OpenVMS VAX Version 6.1.  If you continue with this upgrade, volumeM            shadowing will not be present on your system after the upgrade haslL            completed. Please consult the Volume Shadowing for OpenVMS manualI            for instructions about moving to phase II of volume shadowing.   /          * Do you want to continue the upgrade?m  G               At that point, you can exit the upgrade procedure, followoB               the instructions in Volume Shadowing for OpenVMS forF               migrating to phase II shadowing, and restart the upgradeD               procedure from the beginning. If you continue with theE               upgrade without migrating to phase II, volume shadowingeF               will not be present on your system after the upgrade has               completed.           STOP QUEUESeD               To stop all batch and print queues on the node you are5               upgrading, enter the following command:s  #               $ STOP/QUEUES/ON_NODE   F               It is not necessary to stop queues on nodes that you are               not upgrading.                                        I                                Before Upgrading OpenVMS VAX Software 5-25            )     Gathering Information for the Upgradei    E     _________________________________________________________________m  )     Gathering Information for the Upgradeu         INTRODUCTION?           At different points during the upgrade, the procedurea,           prompts you to supply information.         INFORMATION YOU NEEDB           To save time once the procedure begins, be sure you have@           the following information readily available. Remember,A           entering incorrect information during the upgrade couldY;           force you to repeat the entire upgrade procedure.   E     _________________________________________________________________v     Required"     Information        ExplanationE     _________________________________________________________________)D     Device names       You will need to specify the device names forA                        the drives that will hold the distributiona1                        media and the system disk.d  C     Passwords          You will be prompted to type passwords of atsB                        least 8 characters for the SYSTEM, SYSTEST,*                        and FIELD accounts.  C     Optional           The upgrade procedure prompts you to specify >     components         whether you want to install the library>     and OpenVMS        (VMS062.C), optional (VMS062.D) OpenVMSA     Management         components, and OpenVMS Management StationeE     Station files      software PC files (VMS062.G). Appendix C lists =                        the files included in these save sets.   E                        You can save some space on your system disk ifeB                        you choose not to install these components,>                        but be sure to review Appendix C before                         deciding.              .     5-26 Before Upgrading OpenVMS VAX Software c  h      I                                     Gathering Information for the Upgradee    I         _________________________________________________________________          Required&         Information        ExplanationI         _________________________________________________________________eE         Location for       Save set VMS062.E contains the online HelpOG         Help Message       Message utility, and VMS062.F contains threenD         utility and        online reference manuals in ASCII format:F         online manuals     OpenVMS Master Index, OpenVMS Glossary, and=                            Overview of OpenVMS Documentation.A  F                            Know the name of the disk on which you willI                            be installing these save sets. You can install D                            these save sets on your system disk or onG                            alternate disks. (However, if you copied theND                            distribution kit to some other media fromI                            which you will be performing the installation, E                            you cannot install these save sets on that H                            media.) The contents of save set VMS062.E canH                            reside on one disk, and save set VMS062.F canE                            reside on another alternate disk. However,_G                            you cannot divide the text files in save set F                            VMS062.F between disks; they must all be on)                            the same disk.   M     _________________________________________________________________________                                           I                                Before Upgrading OpenVMS VAX Software 5-27_ _  _      )     Gathering Information for the Upgradei                                7                    (THIS PAGE INTENTIONALLY LEFT BLANK)_                                                                           .     5-28 Before Upgrading OpenVMS VAX Software )         I                                     Gathering Information for the Upgrade     I         _________________________________________________________________          Required&         Information        ExplanationI         _________________________________________________________________ D         DECwindows         The installation procedure prompts you toD         components         specify which of the following DECwindows:                            components you want to install:  C                            o  DECwindows base support (required for A                               running DECwindows software), which '                               includes:w  5                               -  DECwindows transport   3                               -  DECwindows keymaps   F                            o  DECwindows workstation support (requiredD                               for VAX workstations), which includes:  >                               -  DECwindows X11 display server  1                               -  Graphics drivers   9                               -  75 dots/inch video fontsM  B                               -  100 dots/inch video fonts (optionH                                  available only if you select DECwindows5                                  workstation support)o  D                            Note that you must install the DECwindowsG                            Motif for OpenVMS VAX (previously called VMSnH                            DECwindows Motif) layered product if you wantI                            to run the DECwindows software. VMS DECwindowsgE                            Motif Version 1.1 is the minimum supportedMB                            version for systems running OpenVMS VAXH                            Version 6.2. If you do not know which versionH                            of DECwindows Motif you are currently runningH                            on your system, you can check by entering the-                            following command:D  G                            $ ANALYZE/IMAGE SYS$LIBRARY:DECW$XLIBSHR.EXEh  F                            Also note that the layered product does notC                            have the DECwindows base and workstation E                            support components. To get full DECwindowsOB                            support, you must select the DECwindowsC                            components provided with the OpenVMS VAX C                            Version 6.2 kit and install the separateEC                            DECwindows Motif for OpenVMS VAX layeredAE                            product, which supports both Motif and XUI (                            environments.  I                                Before Upgrading OpenVMS VAX Software 5-29     .      )     Gathering Information for the Upgrade     E     _________________________________________________________________      Required"     Information        ExplanationE     _________________________________________________________________r8     PAK information    The information listed on ProductE                        Authorization Keys (PAKs) for any new products E                        you will register. You do not need to registerpC                        your OpenVMS VAX license or the licenses forkD                        any System Integrated Products (SIPs) you are'                        already_running. E     _________________________________________________________________a       WHERE TO GO NEXTC           Once you have completed these steps, use the checklist in B           Preupgrade Checklist to make sure you have completed allA           the necessary tasks before continuing with the upgrade.                                                             .     5-30 Before Upgrading OpenVMS VAX Software           I                                                      Preupgrade ChecklistS    I         _________________________________________________________________T           Preupgrade Checklist             INTRODUCTIONG               Before you begin the upgrade procedure, use the followingsI               checklist to make sure you have completed all the necessary                preupgrade tasks..             DID YOU . . .y  F               <  Read the OpenVMS Version 6.2 New Features Manual, theI                  OpenVMS Version 6.2 Release Notes, and any cover lettersR)                  that came with your kit?B  D               <  Read the cautions and restrictions described at the<                  beginning of this chapter and in Chapter 1?  G               <  Make sure you have enough free blocks for the upgrade?OF                  You need at least 51,550 free blocks for the requiredF                  files to start the upgrade. (Described in the sectionI                  Preparing Your System Disk.) The entire upgrade requiresr&                  about 162,600 blocks.  F               <  Set up your system to record the upgrade procedure onH                  either a hardcopy terminal or a printer attached to theD                  console terminal? If you do not do this, the screenB                  messages will be lost. You will need a transcriptC                  in case there is a problem during the upgrade. FormH                  information on how to connect a hardcopy device to yourE                  console to record the procedure, see the upgrade andf?                  installation supplement for your VAX computer.   F               <  Check your AUTOGEN feedback information to be sure itH                  is valid before rebooting the system? (Described in the:                  section Examining AUTOGEN Feedback Data.)  >               <  Make a backup copy of the system disk and, ifD                  applicable, of the console media? (Described in theH                  upgrade and installation supplement for your computer.)  I               <  If, in previous versions, your distribution kit provideduG                  standalone BACKUP on one of the following media types,eF                  make sure you have created a standalone BACKUP kit on*                  one of these media types?                       RX33  I                                Before Upgrading OpenVMS VAX Software 5-31                 Preupgrade Checklist                       TU58                 RX50                 RX01                 RL02  5              (Described in the section Backup Tasks.)   C           <  Make sure SYSUAF.DAT is in the SYS$COMMON:[SYSEXE] anda?              VMS$AUDIT_SERVER.DAT is in the SYS$COMMON:[SYSMGR]T@              directory? (Described in the section Preparing Your              System Disk.)  C           <  Make sure SWAPFILE.SYS (if it is located on the system,C              disk) and PAGEFILE.SYS are inthe SYS$SPECIFIC:[SYSEXE]a@              directory? (Described in the section Preparing Your              System Disk.)  =           <  Make sure the page file is at least 4600 blocks?sC              (Described in the section Preparing Your System Disk.)_  5           <  If you have a shared system dump file in B              SYS$COMMON:[SYSEXE], make sure the shared file is notC              named SYSDUMP.DMP? (Described in the section Preparing               Your System Disk.)e  B           <  If your system disk is part of a shadow set, create aE              nonshadowed system disk to upgrade? (Described in Volumer$              Shadowing for OpenVMS.)  C           <  Make sure the SYSTEM account has sufficient quotas and D              limits? (Described in the section Preparing Your System              Disk.)u  @           <  Set the appropriate system parameters and make sureE              that STARTUP_P1 is set to MIN? (Described in the sectiony)              Preparing Your System Disk.)   B           <  Define the system parameters SCSNODE and SCSSYSTEMID?C              (Described in the section Preparing Your System Disk.)T  A           <  If your system has a KFQSA controller, make sure thetE              VMS5 parameter is set to 0? (Described in Preparing Yourr              System Disk.)  ;           <  Check the location of your AGEN$INCLUDE files? A              (Described in the section Check AGEN$INCLUDE Files.)k  .     5-32 Before Upgrading OpenVMS VAX Software d         I                                                      Preupgrade Checklist       G               <  Set up the system to restart automatically? (Described H                  in the upgrade and installation supplement for your VAX                  computer.)   D               <  Shut down and reboot the system from which you willH                  perform the upgrade? If you are upgrading a VAXcluster,G                  shut down all computers that boot from the system disk #                  you are upgrading?S  -               <  Set interactive logins to 0?u  I               <  Shut down DECnet for OpenVMS software? (Described in the /                  section Preparing the System.)f  @               <  Migrate to phase II volume shadowing if you areC                  currently using phase I? (Described in the section '                  Preparing the System.)N  D               <  Stop all batch and print queues on the node you are@                  upgrading? (Described in Preparing the System.)  H               <  Make sure you have the following information (describedF                  in the section Gathering Information for the Upgrade)                  available:   E                  o  The device names of the drives that will hold the ;                     system disk and the distribution media?   F                  o  Passwords of at least 8 characters for the SYSTEM,0                     SYSTEST, and FIELD accounts?  I                  o  A list of optional OpenVMS VAX components you want too                     install?  H                  o  A list of optional DECwindows components you want to                     install?  C                  o  The information listed on Product AuthorizationaE                     Keys (PAKs) for any new product licenses you will                      register?   H               <  Create a command procedure to be used when booting from(                  [SYSF]? See Appendix B.    I                                Before Upgrading OpenVMS VAX Software 5-33h y  h           Preupgrade Checklist           WHERE TO GO NEXT:           To upgrade a standalone system, go to Chapter 7.  ?           To upgrade a VAXcluster environment, go to Chapter 6.e                                                                                  .     5-34 Before Upgrading OpenVMS VAX Software i  t                    I                                                                         6lI         _________________________________________________________________u  I                                        Upgrading a VAXcluster Environment   I         _________________________________________________________________            Overview  @               This chapter describes how to upgrade a VAXclusterF               environment. Refer to VMScluster Systems for OpenVMS forC               more detailed information on VAXcluster environments.   I               If your cluster environment has both VAX and Alpha systems,lH               you should also refer to the OpenVMS Compatibility Between               VAX and Alpha.                                                    I                                    Upgrading a VAXcluster Environment 6-1  n  y      #     Concurrent and Rolling Upgrades     E     _________________________________________________________________   #     Concurrent and Rolling Upgradesa         INTRODUCTION    A           There are two types of cluster upgrades: concurrent and E           rolling. The type of upgrade you use depends on whether you E           want to maintain the availability of the cluster during the A           upgrade and whether you have more than one system disk.s       CONCURRENT UPGRADESuD           During a concurrent upgrade, you must shut down the entireB           cluster and upgrade each system disk. No one can use theD           cluster until you upgrade each system disk and reboot eachD           VAX computer. If all systems in the VAXcluster environment=           are booted from one system disk, you must perform a            concurrent upgrade.m  D           Note: For OpenVMS VAX Version 6.2 concurrent upgrades, allC           nodes in the cluster must be running at least OpenVMS VAXdB           Version 5.5-2. However, the system disk on which you areD           performing the upgrade must be running OpenVMS VAX VersionD           6.0 or 6.1. (See the Restrictions section in Chapter 5 for           more information.)  <           To perform a concurrent upgrade, go to the section           Concurrent Upgrades.       ROLLING UPGRADES@           During a rolling upgrade, you can keep some of the VAXC           computers in the cluster running while you upgrade others_@           (you must have more than one system disk). The clusterC           runs temporarily with different versions of the operating            system.   A           Note: For OpenVMS VAX Version 6.2 rolling upgrades, all C           nodes in the cluster must be running at least OpenVMS VAXmD           Version 5.5-2. However, the system disks you are upgradingB           must be running OpenVMS VAX Version 6.0 or 6.1. (See theB           Restrictions section in Chapter 5 for more information.)  A           To perform a rolling upgrade, go to the section Rollingp           Upgrades.s  *     6-2 Upgrading a VAXcluster Environment           I                                                       Concurrent Upgrades     I         _________________________________________________________________C           Concurrent Upgradesi             INTRODUCTIONC               You perform a concurrent upgrade by shutting down theYG               entire cluster, upgrading each system disk, and rebootinguI               each VAX computer in the cluster. When the cluster reboots,eG               each VAX computer will be running the upgraded version of I               the operating system. Users cannot access the cluster until H               you upgrade each system disk and reboot each VAX computer.    +         HOW TO PERFORM A CONCURRENT UPGRADE_@               To perform a concurrent upgrade, use the following               procedure:  I               1. Shut down the entire cluster by logging in to the SYSTEMiE                  account on each node locally, entering the followingMC                  command, and choosing the CLUSTER_SHUTDOWN option:t  '                  $ @SYS$SYSTEM:SHUTDOWNn  I               2. If you have only one system disk for your cluster, go tos                  Step 3.  E                  If you have more than one system disk, select one to                   upgrade.k  G               3. Perform a conversational boot of a single VAX computersE                  from the system disk you will be upgrading. For moresE                  information about the conversational boot procedure, E                  refer to the upgrade and installation supplement for #                  your VAX computer.   D                  At the SYSBOOT> prompt, use the SHOW VOTES and SHOWH                  EXPECTED_VOTES command to display the current values ofI                  the parameters. Write these values down because you will H                  need to restore them later. Set the VOTES and EXPECTED_F                  VOTES values to 1 by entering the following commands:  %                  SYSBOOT> USE CURRENTn%                  SYSBOOT> SET VOTES 1V.                  SYSBOOT> SET EXPECTED_VOTES 1"                  SYSBOOT> CONTINUE  @               4. Upgrade the system disk, using the procedure in                  Chapter 7.   I                                    Upgrading a VAXcluster Environment 6-3  n              Concurrent Upgrades       <           5. If you have only one system disk, go to Step 6.  A              If you have more than one system disk, shut down the ?              system that you just upgraded. Then repeat Steps 2 B              through 4 to upgrade each system disk in the cluster.E              When you finish upgrading all of the system disks, go tor              Step 6.  @           6. Reboot each computer in the VAXcluster environment.  =           7. Complete the postupgrade procedures described in_              Chapter 8._                                                                  *     6-4 Upgrading a VAXcluster Environment    o      I                                                          Rolling Upgrades     I         _________________________________________________________________s           Rolling Upgrades             INTRODUCTIOND               During a rolling upgrade, you upgrade each system disk@               individually, allowing old and new versions of theF               operating system to run together temporarily in the sameE               cluster. Clusters running two versions of the operating G               system are called mixed-version clusters. Because rolling I               upgrades allow mixed-version clusters, the systems that you 1               are not upgrading remain available.              RESTRICTIONSC               The following restrictions apply to rolling upgrades:d  G               o  Digital recommends that all VAX computers in a clusterlE                  run the same version of the operating system. Mixed- D                  version clusters are supported only for the purposeG                  of upgrading the entire cluster incrementally. DigitalnH                  further recommends that all VAX systems in a VAXclusterD                  run the latest version of the OpenVMS VAX operating                  system.  G               o  A rolling upgrade does not apply when all systems boot F                  from a single system disk. When all systems boot fromC                  a single system disk, perform a concurrent upgrade H                  using the procedure described in the section Concurrent                  Upgrades.  B               o  During the rolling upgrade, the queuing system isI                  disabled on the nodes being upgraded. The queuing systemhG                  on the other nodes should be unaffected by the upgradetI                  as long as a START/QUEUE/MANAGER/ON=(upgrade node . . .) G                  command is not executed. A START/QUEUE/MANAGER command G                  could attempt to move the queue manager process to the H                  node being upgraded if the /ON qualifier indicates thatG                  it is one of the preferred nodes. If the queue manager H                  attempts to run on the node being upgraded, the queuing8                  system will hang on the entire cluster.        I                                    Upgrading a VAXcluster Environment 6-5p M  A           Rolling Upgrades      @              If your startup file contains a START/QUEUE/MANAGERC              /ON=(upgrade node1, node2 . . . noden) command, do not B              boot in any nonupgrading nodes until you have removedB              that command from the startup file. Booting in a nodeD              will cause the queuing system to hang on the cluster ifF              the START/QUEUE/MANAGER/ON=(upgrade node, . . . ) commandE              is executed. When the upgrade has completed, you can adde2              the command back to the startup file.  D              If the cluster queuing system hangs during the upgrade,E              it is most likely caused by the queue manager attempting_B              to run on the upgrading node. To clear the condition,C              move the queue manager to a node you are not upgradingt/              by entering the following command:h  9              START/QUEUE/MANAGER/ON=(nonupgrading node1,-               node2 . . . noden)   $     HOW TO PERFORM A ROLLING UPGRADE:           To perform a rolling upgrade follow these steps:  A           1. Check the votes and make adjustments to maintain the A              proper quorum so the cluster can continue to operate D              throughout the upgrade. (VMScluster Systems for OpenVMS1              describes this procedure in detail.)o  -           2. Select a system disk to upgrade.u  E           3. Shut down all VAX computers booting from the system disk E              that you are upgrading, except for the computer that you E              will use to apply the upgrade. VAX computers that do notND              boot from the system disk that you are upgrading remain               available to users.  D              a. Log in to the SYSTEM account on the VAX computer you"                 are shutting down.  ,              b. Enter the following command:  *                 $ @SYS$SYSTEM:SHUTDOWN.COM  B              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.s  *     6-6 Upgrading a VAXcluster Environment           I                                                          Rolling Upgradeso      F                  This procedure lets one VAX computer continue runningF                  from the system disk (assuming computers running fromF                  different system disks supply enough votes to sustain!                  cluster quorum).r  F               4. If proper quorum is not maintained at any time duringH                  the upgrade procedure, the shutdown procedure will hangE                  the cluster. If the cluster hangs during a shutdown, H                  enter the following commands on the system console of a4                  CPU that is still a cluster member:                    $ <Ctrl/P>p                  >>> H                  >>> D/I 14 Ci                  >>> C                  IPC> Q                   IPC> <Ctrl/Z>  ?               5. Upgrade the system disk using the procedure inr                  Chapter 7.u  I                  Caution: The upgrade procedure requires exclusive accessgG                  to the drive that holds the distribution media. Do notB=                  mount the distribution media on other nodes.   F               6. During phase 1 of the upgrade, the procedure will askI                  if you are performing a rolling upgrade. If you enter Y, I                  the procedure asks you several questions to determine if H                  all system disks in the cluster (other than the one youH                  are upgrading) are running at least OpenVMS VAX Version$                  5.5-2. For example:  O                  * Are the other system disks running OpenVMS V5.5-2 or higher?   D                  All systems in the cluster must be running at leastA                  OpenVMS VAX Version 5.5-2 to perform the rolling :                  upgrade. Type Y and press the Return key.  I               7. When the upgrade has completed, reboot each VAX computer H                  that boots from the system disk you have just upgraded.  F               8. Perform the postupgrade tasks described in Chapter 8.  F               9. Repeat Steps 2 through 7 for each system disk you areH                  upgrading. Once you have performed tasks a through d in?                  Step 3, you do not need to perform them again.   I                                    Upgrading a VAXcluster Environment 6-7h w  s           Rolling Upgrades      3     ADDING AN OPENVMS VAX VERSION 6.2 SUPPORTED CPU ?           If you need to add a new CPU supported by OpenVMS VAX >           Version 6.2 to an existing Version 5.5-2 VAXcluster,?           Digital supports two options, listed in the followings           preferred order:  B           1. Upgrade the entire cluster to OpenVMS VAX Version 6.22              and bring the new CPU in as a member.  ?           2. If you need to keep some systems in the cluster at A              OpenVMS VAX Version 5.5-2, you must upgrade a systemTA              disk in the cluster to Version 6.2 using the rollinghA              upgrade procedure and then boot the new CPU into theg,              cluster using that system disk.                                                              *     6-8 Upgrading a VAXcluster Environment D  i                    I                                                                         7 I         _________________________________________________________________S  I                                Upgrading the OpenVMS VAX Operating Systemh  I         _________________________________________________________________.           Overview  H               This chapter explains the procedure for upgrading a single1               OpenVMS VAX system disk, including:,  E               o  How to prepare for booting from the [SYSF] directory   )               o  How to configure devices   )               o  How to begin the upgrade   E               o  What the procedure does and what you are asked to do 5                  during the six phases of the upgrade   D               You must complete each phase of the upgrade procedure.C               On most VAX computers the upgrade procedure continues I               automatically from phase to phase. Read the screen displaysnD               carefully and, if you need to reboot your VAX computerH               manually, refer to the upgrade and installation supplementB               for your VAX computer and Appendix B of this manual.  G               The time required to complete an upgrade varies depending D               on your hardware configuration and on the distributionI               media you are using. In most cases, magnetic tapes and tapea>               cartridges require more time than compact discs.  G               Before you begin the upgrade procedure, read the overviewlA               of the upgrade procedure described in Chapter 1 and C               complete the preupgrade tasks described in Chapter 5.nC               If you are upgrading a VAXcluster, you must also readt               Chapter 6.        I                            Upgrading the OpenVMS VAX Operating System 7-1            !     Preparing to Boot from [SYSF]     E     _________________________________________________________________[  !     Preparing to Boot from [SYSF]          INTRODUCTIONA           During the upgrade procedure, you are asked to boot theg>           system from the [SYSF] directory on the system disk.A           The [SYSF] directory is a root directory created on theXD           system disk by the upgrade procedure. It temporarily holdsB           the system files used in the upgrade until the procedureB           moves the files to their permanent location. The upgradeE           procedure then removes the [SYSF] directory from the system            disk._  >           If you do not know how to boot from [SYSF], read theC           upgrade and installation supplement for your VAX computer (           and Appendix B of this manual.  ?           Ignore any error messages after the first reboot that A           indicate an invalid dump header version. These messagesn,           are normal and are to be expected.  %     MODIFYING BOOT COMMAND PROCEDURESoC           Some VAX computers require a special command procedure to C           boot from [SYSF]. If you are performing an upgrade on onedA           of the following VAX computers you must modify the boot D           command procedures, DEFBOO and dddGEN before beginning the           upgrade procedure:  /              VAX 8530, 8550, 8700, 8810, 8820-N !              VAX 8820, 8830, 8840e  >           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 ofC           DEFBOO and dddGEN before you modify them. Name the copiess$           DEFBOO.SAV and dddGEN.SAV.  >           The upgrade and installation supplement for your VAXE           computer describes the procedures for copying and modifyingUB           DEFBOO and dddGEN. Use these procedures to modify DEFBOOA           and dddGEN so that they specify [SYSF] as the directoryc           from which to boot.n    2     7-2 Upgrading the OpenVMS VAX Operating System           I                                             Preparing to Boot from [SYSF]       H               In DEFBOO, change the DEPOSIT command that sets boot flags,               in register 5 (R5) as follows:  !               DEPOSIT R5=F0000000e  ?               In dddGEN, change the DEPOSIT command as follows:.  !               DEPOSIT R5 F0000001h  B               If you are upgrading a VAX 8200, 8250, 8300, or 8350E               computer, you must create a boot command procedure thatrA               allows you to boot from the [SYSF] directory beforeuA               beginning the upgrade. The upgrade and installation F               supplement for your VAX computer describes how to create*               this boot command procedure.                                                            I                            Upgrading the OpenVMS VAX Operating System 7-3w    f           Configuring Devices     E     _________________________________________________________________        Configuring Deviceso         INTRODUCTION@           Because you rebooted your system with minimum startup,A           the system did not automatically configure all devices.pB           However, you might need access to some of the devices to           perform the upgrade.         HOW TO CONFIGURE DEVICES?           To make sure you can access the devices that might be ?           needed for the upgrade, run SYSGEN to reconfigure the E           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 CONFIGUREa                                                2     7-4 Upgrading the OpenVMS VAX Operating System           I                                           Beginning the Upgrade Procedure     I         _________________________________________________________________p  '         Beginning the Upgrade Procedures             OVERVIEWG               This section describes how to start the upgrade procedure H               using VMSINSTAL. You can type a question mark (?) for help2               at any time while running VMSINSTAL.  G               The instructions refer to the source drive and the targetS               drive, where:u  =               o  The source drive is the drive that holds the "                  distribution kit.  D               o  The target drive is the drive that holds the system                  disk.  '         STEP 1: LOAD DISTRIBUTION MEDIA E               Put the distribution compact disc or tape in the sourcesB               drive. If your OpenVMS VAX distribution kit containsF               several tapes, put the first one in the drive. The paperE               labels on the tapes indicate the order in which you use                them.a  F               If you are not using an InfoServer device, go to Step 3:               Start VMSINSTAL.  H               If you are using an InfoServer device, proceed to the next               step.S  0         STEP 2: IF UPGRADING FROM THE INFOSERVERA               If upgrading from an InfoServer device, perform them               following steps:  E               1. Start the InfoServer Client software by entering theT#                  following command:T  2                  $ @SYS$STARTUP:ESS$STARTUP CLIENT  >                  The CLIENT parameter loads the client driver,H                  ESS$DADDRIVER.EXE, and the InfoServer transport driver,$                  ESS$LASTDRIVER.EXE.    I                            Upgrading the OpenVMS VAX Operating System 7-57           #     Beginning the Upgrade Procedurea      ?           2. As the startup procedure executes, it displays the                following messages:  :              %LASTCP-I-VERSION, LASTDRIVER X1.5 is stoppedG              %LASTCP-I-ADAINIT, Initializing adapter xxx for LASTDRIVER C              %LASTCP-I-STARTED, LASTDRIVER X1.5 started on node yyyh  E           3. After you start the InfoServer Client software, you mustoE              make the compact disc drive accessible to your system by ,              completing the following steps:  C              a. Insert the distribution compact disc in the compact 7                 disc drive connected to the InfoServer.   -              b. Enter the following commands:A  '              $ RUN SYS$SYSTEM:ESS$LADCP 1              LADCP> BIND/CONNECT/SYSTEM VAXVMS062lM              %LADCP-I-BIND, service bound to logical unit DAD$VMS062 (_DADn:)_              LADCP> EXIT  @              Make note of the device name _DADn: in the previous?              display. You will have to specify this device namei               during the upgrade.       STEP 3: START VMSINSTALt:           To start VMSINSTAL, use the following procedure:  *           1. Log in to the SYSTEM account.  )           2. Enter the following command:l  $              $ @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:o  J                   OpenVMS VAX Software Product Installation Procedure V6.1  *           It is 22-JUN-1995 at 15:00.00.00  9           Enter a question mark (?) at any time for help.e  D           VMSINSTAL checks your system's account quotas. If it findsA           account quotas that are less than it expects, VMSINSTALt6           displays a message similar to the following:  2     7-6 Upgrading the OpenVMS VAX Operating System e  t      I                                           Beginning the Upgrade Procedure       D %VMSINSTAL-W-LOWQUOTA, The following account quotas may be too low. M -VMSINSTAL-W-LOWQUOTA, If you want to modify these account quotas, type NO tonP -VMSINSTAL-W-LOWQUOTA, the next question, modify the appropriate quotas, log outC -VMSINSTAL-W-LOWQUOTA, then log back in and restart this procedure.   7          BYTLM: currently 32512; minimum expected 32768s  & * Do you want to continue anyway [NO]?  F               You should have verified that your SYSTEM account quotasD               were sufficient before beginning the upgrade. (See theB               section Check Quotas and Limits in Chapter 5 for theH               minimum required values and for instructions for modifying!               quotas and limits.)r  A               To modify the account quotas now, do the following:l  2               1. Type No and press the Return key.  >               2. Modify the account quotas you want to change.  H               3. Log out of the SYSTEM account; then log back in so that2                  the new quotas will be in effect.  #               4. Restart VMSINSTAL.l  F                 ________________________ Note ________________________  @                 If you are using an InfoServer device to performA                 the upgrade, the procedure might display an error D                 message stating that the BYTLM quota is too low. You/                 can safely ignore that message.   F                 ______________________________________________________  C               To continue the upgrade without modifying the accounta8               quotas, type Yes and press the Return key.  '         STEP 4: BACK UP THE SYSTEM DISKb;               The procedure displays the following message:n  L               * Are you satisfied with the backup of your system disk [YES]?  F               If you have made a standalone backup of the system disk,F               press Return and go to Step 5: Specify the Source Drive.  I                            Upgrading the OpenVMS VAX Operating System 7-7     S      #     Beginning the Upgrade Procedure       ?           If you have not made a standalone image backup of theA(           system disk, do the following:  E           1. Type N (for No) and press Return. VMSINSTAL ends and the 1              dollar-sign prompt ($) is displayed.   D           2. Back up the system disk as described in the upgrade and;              installation supplement for your VAX computer.r  C           3. After you have made a backup of the system disk, start )              the upgrade procedure again.b  $     STEP 5: SPECIFY THE SOURCE DRIVEA           VMSINSTAL asks for the name of the drive that holds the            distribution media:g  ;           * Where will the distribution volumes be mounted:s  D           Enter the device name of the source drive. For example, ifD           you have a VAX 6000 series computer that has a TK70 with aB           device name of MUC6, type MUC6 and press the Return key.  A           If the drive is connected to an HSC, enter the HSC name E           and the device name of the drive separated by a dollar sign D           ($).  (If you do not enter the device name in this manner,B           it will cause a failure in Phase 2.) For example, if theA           HSC name is MUTT and the device name is MUA0, enter the %           following and press Return:   E           * Where will the distribution volumes be mounted: MUTT$MUA0g  D           If you are not using an InfoServer device, proceed to Step            6: Enter Product Name.  B           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 theC           distribution compact disc as previously described in Stepe.           2: If Upgrading from the InfoServer.  E           If VMSINSTAL displays an error message, make sure the drive D           is connected and set up properly. Enter the name again. IfE           VMSINSTAL displays another error message, use the followingt.           procedure to verify the device name:  1           1. Press Ctrl/Y to exit from VMSINSTAL.   D           2. Enter the SHOW DEVICE command to make sure you have the!              correct device name.i  2     7-8 Upgrading the OpenVMS VAX Operating System i         I                                           Beginning the Upgrade Procedureh      A               3. Restart the upgrade procedure from Step 3: Startr                  VMSINSTAL.   H               If VMSINSTAL does not display an error message, proceed to)               Step 6: Enter Product Name.l  "         STEP 6: ENTER PRODUCT NAMEH               When VMSINSTAL displays the following message, type VMS062B               and press the Return key. Make sure that you use theD               number zero (not the letter "O") when you type VMS062.               For example:                  * Products: VMS062  F               When the procedure displays the following message, press               Return:   B               * Enter installation options you wish to use (none):  &         STEP 7: MOUNT THE FIRST VOLUMED               VMSINSTAL displays a message similar to the following:  @               Please mount the first volume of the set on _MUA0.  G               When the procedure displays the following message, type Y ,               (for Yes) S) and press Return:  !               * Are you ready?  Y.  G               The procedure displays messages similar to the following:g  8               %MOUNT-I-MOUNTED, VMS062 mounted on _MUA0:  7               The following products will be processed:                    OpenVMS V6.2  C               After a slight pause, the procedure displays messages '               similar to the following:   E                       Beginning installation of OpenVMS V6.2 at 15:05t  B               %VMSINSTAL-I-RESTORE, Restoring product saveset A...    I                            Upgrading the OpenVMS VAX Operating System 7-9            #     Beginning the Upgrade Proceduret      (     STEP 8: CHECKING FOR DECNET PRODUCTS@           The DECnet for OpenVMS (Phase IV) software is providedB           on the OpenVMS VAX Version 6.2 kit. If you are currently>           running the DECnet/OSI for OpenVMS (Phase V) layered?           product, the procedure detects this and gives you the D           option to retain those files. (However, you should upgradeD           to Version 6.1 of DECnet/OSI for OpenVMS.) See the sectionC           Cautions, Restrictions, and Changes in Chapter 1 for more            information.  =           After the OpenVMS VAX Version 6.2 upgrade procedure >           completes, refer to the section Updating Your DECnetC           Phase IV Configuration in Chapter 8 for information abouttD           configuring your DECnet software if you are running DECnetD           for OpenVMS. Refer to the section Configuring and Starting?           DECnet in Chapter 4 if you are running DECnet/OSI fore           OpenVMS.  +     STEP 9: MONITOR MESSAGES FROM VMSINSTAL C           The upgrade procedure displays several important messages :           that provide you with the following information:  %           -  What VMSINSTAL is doing.W  E           -  Notes, suggestions, and restrictions about various partsr              of the upgrade.  #           -  Status of the upgrade.   D           Read these messages carefully to decide whether or not youB           need to interrupt the upgrade procedure. An interruption?           is allowed before Phase 1. The procedure displays thel           following message:  +           * Do you want to continue? (Y/N):   E           To continue the upgrade, type Yes and press the Return key.m  5           To interrupt the upgrade, do the following:   &           1. Type No and press Return.  D           2. If prompted for another product, type EXIT to exit from              VMSINSTAL.   3     7-10 Upgrading the OpenVMS VAX Operating Systemt a         I                                           Beginning the Upgrade Procedureo      %         STEP 10: VERIFY DATE AND TIMEoF               The procedure displays the current date and time. If theI               date and time are correct, type Yes. If they are incorrect, H               type No. Enter the correct date and time using the 24-hour9               clock format and press Return. For example:g  N               PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) 22-JUN-1995 15:10           WHERE TO GO NEXT3               Continue with Phase 1 of the upgrade._                                                                      I                           Upgrading the OpenVMS VAX Operating System 7-11  t  f           Upgrade Phase 1     E     _________________________________________________________________d       Upgrade Phase 1t         OVERVIEWD           This section describes Phase 1 of the upgrade. During thisE           phase, you provide passwords for system accounts and selectpB           OpenVMS options, and the procedure restores the files in3           the OpenVMS required save set (VMS062.B).   E           At the end of this phase, the procedure shuts down your VAX D           computer. If your computer uses console media when bootingD           and the boot file was modified as described in the sectionA           Preparing to Boot from [SYSF], the system should reboothE           automatically. Otherwise, you must reboot manually from thec           SYSF directory.C  #     STEP 1: SPECIFY TYPE OF UPGRADEc?           At the beginning of Phase 1, the procedure displays af+           message similar to the following:o  :                   Upgrade Phase 1  22-JUN-1995 15:11:17.05  8           * Are you performing a rolling upgrade? (Y/N):  E           If you are performing a concurrent upgrade or an upgrade on8@           a standalone system, type No and press the Return key.  ?           If you are performing a rolling upgrade, type Yes and D           press Return. The procedure will ask you several questions@           to determine if all system disks in the cluster (otherB           than the one you upgrading) are running at least OpenVMSA           VAX Version 6.0. Follow the instructions in the Rollingt(           Upgrades section of Chapter 6.       STEP 2: ENTER PASSWORDSuC           To ensure system security, the upgrade procedure requireseC           you to enter passwords for the SYSTEM, SYSTEST, and FIELDf?           accounts before continuing. Passwords must contain at C           least 8 characters; they are not displayed by the system. C           Press Return after you enter each password and it will be             verified. For example:      3     7-12 Upgrading the OpenVMS VAX Operating System  r  s      I                                                           Upgrade Phase 1d      N         To help provide a more secure system, you are asked to enter passwordsL         for key system accounts. Passwords must be a minimum of 8 characters;         in length. You can enter new or existing passwords.r  3         Enter passwords for the following accounts:c  ,                       SYSTEM, SYSTEST, FIELD  $         * 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  J              The SYSTEST_CLIG account will be disabled. You must re-enableA              it before running UETP but do not assign a password.   .         %UAF-I-MDFYMSG, user record(s) updated  !         Enter password for FIELD:t"         Re-enter for verification:.         %UAF-I-MDFYMSG, user record(s) updated<         %VMS-I-PWD-OKAY, account password for FIELD verified  G               If you enter a password incorrectly or if the password iseF               too easy to guess, the procedure displays error messages'               similar to the following:o  ;   %VMS-W-PWD-INVALID, account password for FIELD is invalidN0   %VMS-I-PWD-WEAK, password is too easy to guess  N   Because of the preceding error, you must take action to secure this account.H   You must either disable this account, change its password, or do both.  I               When the procedure asks if you want to disable the account, G               type No and press the Return key. When the procedure askspE               if you want to enter a new password, type Yes and press =               Return. Then enter a new password. For example:d  -   Do you want to disable the account (Y/N)? N 5   Do you want to change the account password (Y/N)? Y G   You must now select a new primary password for the FIELD account. TheoK   password you select must be at least 8 characters in length and cannot beT&   the same as the name of the account.  I                           Upgrading the OpenVMS VAX Operating System 7-13  t  d           Upgrade Phase 1            New password:      Verification:D)     %UAF-I-MDFMSG, user record(s) updated :     %VMS-I-PWD-SET, primary password for account FIELD set  =           After you have correctly entered the passwords, the '           procedure does the following:   B           o  Checks the account quotas in the DEFAULT, SYSTEM, andB              various other accounts and modifies them if necessary  0           o  Turns off quotas on the system disk             o  Stops OPCOM  /           o  Stops the error formatter (ERRFMT)d       STEP 3: CHOOSE BOOT METHODA           If your VAX computer is not one of the following, go to            Step 4: File Cleanup.n                VAX 11/730               VAX 11/750w              VAX 11/780 '              VAX 8200, 8250, 8300, 8350               VAX 8600, 8650               VAX 9000T  A           If your VAX computer is included in the preceding list, A           the procedure can temporarily modify the DEFBOO.CMD (or B           DEFBOO.COM if you have a VAX 8600 computer) to boot fromB           the [SYSF] directory. During Phase 4 of the upgrade, theE           procedure restores the DEFBOO.CMD (or DEFBOO.COM) file that C           is set up to boot from the current system disk and systemt           root.h  C           The procedure displays a message similar to the following >           (except for VAX 11/730, 11/780, and 8600 computers):  9           * Do you want to boot from the [console media]?S  D           If you prefer to boot your system manually from the [SYSF]?           directory or if you are booting directly from a local D           system disk, type No, press the Return key, and go to Step2           4: File Cleanup to continue the upgrade.  D           Type Yes and press Return if one of the following is true:  5           o  You want to boot from the console media.e  3     7-14 Upgrading the OpenVMS VAX Operating SystemS :  $      I                                                           Upgrade Phase 1-      @               o  Your computer is a VAX 11/730, 11/780, or 8600.  '               o  You are using a CI750.   F               The procedure prompts you to insert the console media inI               the drive. Insert the backup copy of the console media into E               the drive and do not remove it from the drive until thedH               upgrade has been completed. Make sure the console media is               write enabled.           STEP 4: FILE CLEANUP/               The procedure does the following:r  D               o  Renames files found in SYS$SPECIFIC:[SYSMGR] and inC                  SYS$COMMON:[SYSMGR] by adding _OLD_SPECIFIC to the H                  file extensions. For example, [SYSMGR]LOGIN.COM becomesI                  [SYSMGR]LOGIN.COM_OLD_SPECIFIC. (The file extensions are?C                  restored during Phase 6 of the upgrade procedure.)a  D               o  Cleans up the system disk by purging all accountingE                  data files, operator logs, and the directory SYSERR.lE                  The procedure also deletes all JNL files in the root 2                  directory and its subdirectories.  I               o  Builds the directory tree [SYSF] and deletes the OpenVMStG                  VAX and DECwindows files that are not needed to reboote/                  during Phase 2 of the upgrade.U  H               As the procedure performs each of these tasks, it displaysG               messages describing what is being done. When this step isMH               completed, the procedure displays a message similar to the               following:  =               File cleanup complete - 22-JUN-1995 15:29:41.92                       I                           Upgrading the OpenVMS VAX Operating System 7-15s d  m           Upgrade Phase 1       .     STEP 5: SELECT OPTIONAL OPENVMS COMPONENTSC           The procedure displays information about optional OpenVMS ?           VAX files and the remaining amount of disk space. The D           information is similar to the following (block sizes might           vary slightly):o  G           Select optional software you want to install. You can installnH           one or more of the following OpenVMS or DECwindows components:  H           o OpenVMS library                              -  43500 blocksH           o OpenVMS optional                             -  19100 blocksH           o OpenVMS Help Message                         -   8850 blocksH           o Text versions of three OpenVMS manuals       -   4450 blocksH           o DECwindows workstation support               -  25750 blocksH           o DECwindows base support                      -   3600 blocksH           o OpenVMS Management Station                   -   5900 blocks  6           Space remaining on system disk: 80696 blocks  E           You must indicate which of the options you want to install.oE           If you require network support, you must select the OpenVMSy           library component.  E           Note: If you do not install the optional OpenVMS components A           at this time, you can install them after the upgrade by E           using the VMSTAILOR and DECW$TAILOR utilities. However, the-E           Help Message utility and the three reference manuals can be C           tailored on to the system disk only. If you do not choosetC           the Help Message files or the three manuals at this pointRD           in the procedure and want them on an alternate device, youB           will not be able to use VMSTAILOR to restore them later.B           If you want to install Help Message on an alternate diskE           after the installation procedure completes, you can use thei%           BACKUP command, as follows:o  @           BACKUP/VERIFY source-device:[000000]VMS062.E/SAVE_SET-(           target-device:[directory-name]  @           For source-device, enter the device name for the driveA           on which the distribution media is mounted. For target-i>           device, enter the device name on which the alternateC           disk is mounted, and for directory, enter the name of thenC           directory to which you are copying the files. (To installdD           the OpenVMS manuals, specify VMS062.F/SAVE_SET in place of           VMS062.E/SAVE_SET.)d  3     7-16 Upgrading the OpenVMS VAX Operating Systemr e  v      I                                                           Upgrade Phase 1p      E               Also note that, for TK50 tape cartridges, it is quicker H               to install OpenVMS VAX software during the upgrade than toF               add software after the upgrade with a tailoring utility.D               For information about using VMSTAILOR, see Chapter 10.C               To select the options you want to install, follow thee6               instructions displayed by the procedure.  #               OpenVMS_Library_Files   ;               The procedure displays the following message:n  G               * Do you want to install the OpenVMS library files? (Y/N)r  H               The file subclasses of the OpenVMS library (VMS062.C) saveF               set are listed in Appendix C. If you want to install theG               VMS062.C files, type Yes and press Return. If you requirehB               network support, you must select the OpenVMS libraryC               component. If you do not want to install the VMS062.Ct.               files, type No and press Return.  $               OpenVMS_Optional_Files  ;               The procedure displays the following message:   H               * Do you want to install the OpenVMS optional files? (Y/N)  D               The file subclasses of the OpenVMS optional (VMS062.D)G               save set are listed in Appendix C. If you want to installiF               the VMS062.D files, type Yes and press Return. If you doG               not want to install the VMS062.D files, type No and pressL               Return.                             I                           Upgrading the OpenVMS VAX Operating System 7-17  b  z           Upgrade Phase 1e      *           OpenVMS_Management_Station_Files  7           The procedure displays the following message:p  D        The OpenVMS Management Station is a client-server applicationE        that provides OpenVMS system management capabilities through a G        client application on a personal computer (PC) running MicrosoftaE        Windows. The server application runs on OpenVMS systems and isrG        automatically installed as part of the OpenVMS operating system.y  K        This option provides the files used to create the installation media M        for the PC client software.  If you want to use the OpenVMS ManagementsN        Station, you must install these files on at least one OpenVMS system toK        create the installation media, which can then be used to install the $        PC client on one or more PCs.  J        Note: To use the OpenVMS Management Station on your PC, you must beP        running Digital's PATHWORKS V5.0A for DOS and Windows (or V5.1) software.  O        The OpenVMS Management Station optional files consume approximately 5900.P        blocks and will be placed on your system disk in SYS$COMMON:[TNT.CLIENT].  O   * Do you want to install the optional OpenVMS Management Station files? (Y/N)R  8        Space remaining on system disk:     623240 blocks  E           If you want to use the OpenVMS Management Station software,yC           you must install these files. After the upgrade procedure =           completes, follow the instructions in Appendix F toiD           prepare your OpenVMS system and your PC to run the OpenVMS8           Management Station server and client software.             Help_Message_Files  7           The procedure displays the following message:r  L               The Help Message utility (MSGHLP) provides online explanationsL               and user actions for OpenVMS messages in place of the hardcopyO               OpenVMS System Messages and Recovery Procedures Reference Manual,o0               which is now separately orderable.  G               The MSGHLP database, MSGHLP$LIBRARY.MSGHLP$DATA, consumesgE               approximately 8850 blocks and will be placed by default N               on your system disk in SYS$COMMON:[SYSHLP] unless you specify an-               alternate device when prompted.a  =           * Do you want to install the MSGHLP database? (Y/N)   3     7-18 Upgrading the OpenVMS VAX Operating System  t         I                                                           Upgrade Phase 1       E               The Help Message utility is an online system for systemuI               messages documentation. You can install Help Message eitherrH               on the system disk or on an alternate disk. If you want toH               install the Help Message files, type Yes and press Return.  ;               The procedure displays the following message:   O        You can install this database on your system disk in SYS$COMMON:[SYSHLP]iL        or on an alternate device. If you specify an alternate device, but noN        directory, MSGHLP$LIBRARY.MSGHLP$DATA is placed in [HELP_MESSAGE]. WhenL        prompted, take the default of the system disk or specify an alternate         device using this format:  /                              device:[directory]   O  * Where do you want to install the MSGHLP database? [SYS$COMMON:[SYSHLP]] DUA1t  D               The Help Message database is installed in the area youG               specified, and the system displays information similar to2               the following:  <               %MOUNT-I-MOUNTED, VMS062       mounted on DUA1  J                   Space remaining on alternate device DUA1:: 124532 blocks                 OpenVMS_Manuals   ;               The procedure displays the following message:   P               You have the choice of installing the text versions of one or more(               OpenVMS reference manuals:  J               o OpenVMS Master Index                       -   3600 blocksJ               o OpenVMS Master Glossary                    -    650 blocksJ               o Overview of OpenVMS Documentation          -    200 blocks  L               You can install these manuals, by default, to your system diskJ               in [SYSHLP.VMSDOC] or to an alternate device of your choice.I               In either case, all manuals must reside on the same device.nO               If you choose an alternate device and do not specify a directory, J               [VMSDOC_TEXT] will be created for you.  The device structureD               for an alternate device should resemble the following:  5                                    device:[directory]   D               Do you want any of these three OpenVMS manuals?: (Y/N)  C               Type Yes to install all three manuals or to install a $               subset of the manuals.  I                           Upgrading the OpenVMS VAX Operating System 7-19  r  o           Upgrade Phase 1a      -           The following message is displayed:r  6           Do you want all three OpenVMS manuals? (Y/N)  >           To install all three manuals, type Yes. To install aA           subset, type No and the system will display each manualhE           title and prompt you to type either Yes or No to select it.l  E           When you have completed selecting which manuals to install,g,           the following prompt is displayed:  O           * Where do you want to install the OpenVMS manual(s)? [SYSHLP.VMSDOC]   D           Press Return to accept the default, [SYSHLP.VMSDOC] on theA           system disk, or enter the alternate disk name and presss           Return.E  -     STEP 6: CHOOSE DECWINDOWS SUPPORT OPTIONS D           Next, the procedure displays messages about the DECwindows:           components shipped with OpenVMS VAX Version 6.2.  ?           Important: The OpenVMS VAX operating system no longerd@           ships the VMS DECwindows product. The operating systemC           now ships only the DECwindows base support and DECwindows @           workstation support components. To get full DECwindows@           support, you must also install the separate DECwindowsA           Motif for OpenVMS VAX (previously called VMS DECwindows C           Motif) layered product, which supports both Motif and XUIe           environments.w  :           Note: The DECwindows base support and DECwindowsA           workstation support components are not shipped with therC           DECwindows Motif for OpenVMS layered product. If you wantVC           to install these options, you must select them now or useeA           the DECW$TAILOR option after the installation procedure            completes.  /           The procedure displays the following:t  =     You can select DECwindows support now, or you can use thec?     DECW$TAILOR utility to provide or remove DECwindows supporte     after the upgrade.  :     Some media, TK50s in particular, can be very slow when<     tailoring on files. You might want to provide DECwindows4     options now and tailor off unwanted files later.  3     7-20 Upgrading the OpenVMS VAX Operating Systemr o  I      I                                                           Upgrade Phase 1o      @     You can install all of the DECwindows components provided in?     this kit, which requires approximately 29350 blocks, or youI#     can select specific components.   @     o DECwindows workstation support             -  20750 blocks0       -  75 dots per inch video fonts (included)@       - 100 dots per inch video fonts (optional) -   5000 blocks@     o DECwindows base support                    -   3600 blocks  F     If you are installing this kit on a workstation or on a VAXclusterC     that contains workstations, then you must choose the DECwindows      workstation support option.   D     If you are installing this kit on a system that does not includeD     workstations but does include Xterminals, then you might want toD     choose the DECwindows workstation support option to provide fontB     files.  If you decide not to select the DECwindows workstationJ     support option at this time, then you will have to use the DECW$TAILOR5     utility to provide font files for the Xterminals.   D     If you plan to run DECwindows software, then you must choose the#     DECwindows base support option.i  I     NOTE: This kit does NOT contain full DECwindows support.  It includesrF           only the DECwindows base and workstation support components.F           To obtain full DECwindows support, you must also install theD           separate DECwindows Motif for OpenVMS VAX layered product.  F     NOTE: VMS DECwindows Motif Version 1.1 is the minimum version that3           can be used with OpenVMS VAX Version 6.2.   =   * Do you want to provide optional DECwindows support? (Y/N)R                 Before You DecideE               -----------------tH               Before you indicate whether you want to install DECwindows7               support software, consider the following:   I         _________________________________________________________________V7         If you . . .                  Then choose . . .uI         _________________________________________________________________ >         Intend to install the         DECwindows base support.          DECwindows Motif layered         product   I                           Upgrading the OpenVMS VAX Operating System 7-21c r  e           Upgrade Phase 1E    E     _________________________________________________________________i3     If you . . .                  Then choose . . .cE     _________________________________________________________________oA     Intend to install the         DECwindows workstation support.n     DECwindows Motif layered     product on a workstation     or on a VAXcluster thatl     contains workstations or     Xterminals  A     Are installing on a           DECwindows workstation support.o     workstation or on an     VAXcluster that includes     workstations or Xterminals  E     Have a workstation monitor    DECwindows workstation support with:;     capable of displaying 100     the 100 dots/inch option. >     dots/inch (for example, a     By selecting the workstationB     VR150, VR160, or VR295)       support files, you automatically  =                                   get 75 dots/inch video font A                                   files, and you will be prompted D                                   to indicate if you want to installA                                   100 dots/inch video font files.iE     _________________________________________________________________ E           If you do not want to install the DECwindows software, typee4           No, press Return, and go to the next step.  A           If you want to install DECwindows support, type Yes and E           press Return. The procedure displays the following message:   H           * Do you want to install DECwindows workstation support? (Y/N)  D           If you answer Yes to this prompt, the following DECwindows'           components will be installed:(  +           o  DECwindows workstation supporto  %           o  75 dots/inch video fontsr  $           o  DECwindows base support  C           You are also given the option to select the 100 dots/incha           video fonts.  A           If you decide not to install the DECwindows workstationeD           support, you are given the option to select the DECwindows<           base support, which is required if you plan to run           DECwindows software.  3     7-22 Upgrading the OpenVMS VAX Operating System            I                                                           Upgrade Phase 1m      E               * Do you want to install DECwindows base support? (Y/N)   #         STEP 7: VERIFY YOUR CHOICES I               The procedure displays a list of OpenVMS VAX and DECwindows D               support options that you have chosen and gives you theB               opportunity to change your mind before proceeding by/               displaying the following message:   &               * Is this correct? (Y/N)  F               If you answer Yes to this prompt, the procedure restoresE               the OpenVMS required save set (VMS062.B) and purges then8               page, swap, dump, and authorization files.  D               If you answer No to this prompt, you can respecify theA               OpenVMS VAX and DECwindows options that you want totG               install. The procedure restores the DECwindows componentse-               you have chosen during Phase 2.   %         STEP 8: SHUT DOWN YOUR SYSTEM I               After several minutes, the upgrade procedure indicates that H               the system will shut down to reboot the partially upgradedF               OpenVMS VAX system and displays information about how to                reboot the system.  B               On certain VAX computers, the procedure displays the                following message:  0               * Press RETURN to shutdown system:  I               Once you have read the information displayed on the screen,c1               press Return to begin the shutdown.o  !         STEP 9: REBOOT THE SYSTEMfH               If your system uses console media, it should automaticallyA               reboot from the SYSF directory when the shutdown islI               complete. If you have a MicroVAX or if your system does noteH               reboot from SYSF, halt the system and boot from the [SYSF]H               directory. For most MicroVAX and VAXstation computers, useI               the BOOT command in the following format and substitute thes6               device name of the system disk for ddcu:  !               >>> B/F0000000 ddcuo    I                           Upgrading the OpenVMS VAX Operating System 7-23     T           Upgrade Phase 1.      E           For more information on booting your computer from the SYSF D           directory, see the upgrade and installation supplement for           your VAX computer.                                                                                    3     7-24 Upgrading the OpenVMS VAX Operating Systemd c  e      I                                                           Upgrade Phase 1m      #         STEP 10: VERIFY SYSTEM TIMEeG               When the system reboots, it displays a message similar tof               the following:  N            OpenVMS VAX Version V6.2  Major version id = 1 Minor version id = 0  0          System time is: 22-JUN-1995 15:54:08.30  
             . 
             .S
             .            * Is that correct?  I               ___________________________________________________________ ,               If . . .            Then . . .I               ___________________________________________________________ D               You want to         Type a question mark (?) and press)               redisplay the       Return.                time  <               The system time     Type Yes and press Return.               displayed by               the proceduren               is correct  ;               The system time     Type No and press Return. G               displayed by        The procedure promps you to enter theo8               the procedure       correct date and time.               is incorrectI               ___________________________________________________________                             I                           Upgrading the OpenVMS VAX Operating System 7-25l    e           Upgrade Phase 2o    E     _________________________________________________________________a       Upgrade Phase 2n         WHAT THE PROCEDURE DOESl?           At the beginning of Phase 2, the procedure displays a +           message similar to the following:   =           Continuing with OpenVMS VAX V6.2 Upgrade Procedure.   B                    Upgrade Phase 2         22-JUN-1995 15:55:42.57  L           %STDRV-I-STARTUP, OpenVMS startup begun at 22-JUN-1995 15:55:43.22=           On MIN or UPGRADE system startup - CLUE is not run. 
             . 
             . 
             .e  H           %STDRV-I-STARTUP, VMS startup begun at 22-JUN-1995 15:57:00.59  D           During Phase 2, the upgrade procedure restores the rest ofB           the library (C), optional (D), Help Message (E), OpenVMSB           manuals (F), and OpenVMS Management Station software (G)B           save sets and DECwindows support files if you elected to           install them.        WHAT YOU DOm=           During Phase 2, the procedure prompts you to do thes           following:  ?           1. If your OpenVMS VAX distribution media is magneticaD              tape, the procedure asks you to replace volume 1 in theD              drive with volume 2 prior to restoring the VMS062.C andC              VMS062.D save sets. After restoring save set VMS062.D,e?              the procedure prompts you to replace volume 2 withe              volume 3.  C              Note: Do not remove the OpenVMS VAX distribution mediaa%              until prompted to do so.s  ?           2. If your distribution media is tape cartridges, thesB              procedure displays a message similar to the following=              after it restores the OpenVMS VAX files (if your A              distribution media is compact disc or magnetic tape,r.              you will not see these messages):  3     7-26 Upgrading the OpenVMS VAX Operating System     o      I                                                           Upgrade Phase 2y      O                     You can now remove the OpenVMS distribution kit from MUA0:.e  9                     Load the DECwindows distribution kit.y  F                  If you selected any of the DECwindows support optionsE                  during Phase 1, put the second tape cartridge, whicheE                  contains the DECwindows support files, in the sourcee=                  drive. The procedure displays the following:t  L    * Enter name of the drive holding the DECwindows distribution media: MUA09    * Is the DECwindows media ready to be mounted? [N] YES   3                  Type Yes and press the Return key.                                                                 I                           Upgrading the OpenVMS VAX Operating System 7-27e P  e           Upgrade Phase 2       ?           3. The procedure installs the DECwindows options thatH?              you specified and displays messages similar to the               following:   7              %MOUNT-I-MOUNTED, DEC062 mounted on _MUA0:m  ?                  Restoring DECwindows base support save set ...l>              %BACKUP-I-STARTVERIFY, starting verification pass  F                  Restoring DECwindows workstation support save set ...>              %BACKUP-I-STARTVERIFY, starting verification pass  I                  Restoring DECwindows 75 dots per inch fonts save set ...e>              %BACKUP-I-STARTVERIFY, starting verification pass  J                  Restoring DECwindows 100 dots per inch fonts save set ...>              %BACKUP-I-STARTVERIFY, starting verification pass  @           4. After restoring the DECwindows files, the procedure9              displays a message similar to the following:   J              You can now remove the DECwindows distribution kit from MUA0:  =           5. If your distribution media is tape cartridges ore;              magnetic tape, remove the media containing the -              DECwindows files from the drive.,  B              If your distribution media is compact disc, leave the'              compact disc in the drive.                                 3     7-28 Upgrading the OpenVMS VAX Operating Systemb ?  Y      I                                                           Upgrade Phase 3i    I         _________________________________________________________________m           Upgrade Phase 3              WHAT THE PROCEDURE DOESMC               At the beginning of Phase 3, the procedure displays an/               message similar to the following:   @               Continuing with OpenVMS VAX V6.2 Upgrade Procedure  L                    Upgrade Phase 3                   22-JUN-1995 16:45:18.35  G               During Phase 3, the upgrade procedure does the following:   B               1. Merges the OpenVMS VAX distributed files that areD                  commonly edited by system managers with new OpenVMS                  VAX files.r  C               2. Merges all the miscellaneous user files in the old I                  system directories into a new set of system directories, =                  temporarily called SYSF.SYSEXE, SYSF.SYSMGR, (                  SYSF.SYSLIB, and so on.  H               3. Removes the directory entries for page, swap, dump, andA                  authorization files from the old directory tree.   A               4. Deletes all the remaining accounting data files,aF                  operator logs, and all files in the SYSERR directory.  H               5. Merges the old and new versions of the following files:@                  HELP, DCLTABLES, IMAGELIB.OLB, and STARLET.OLB.  F               6. Moves all remaining files from the old directory tree8                  [VMS$COMMON] to the new directory tree.  =               7. Deletes the old directory tree [VMS$COMMON].                   I                           Upgrading the OpenVMS VAX Operating System 7-29? /              Upgrade Phase 4t    E     _________________________________________________________________t       Upgrade Phase 4n         WHAT THE PROCEDURE DOESy?           At the beginning of Phase 4, the procedure displays ah+           message similar to the following:a  =           Continuing with OpenVMS VAX V6.2 Upgrade Procedure.   A                Upgrade Phase 4            22-JUN-1995 17:14:34.12   C           During Phase 4, the upgrade procedure does the following:   ;           1. Corrects back pointers for system directories.s  #           2. Shuts down the system.H  E           3. Reboots the system, or requires that you manually rebootm              the system.       WHAT YOU DOn@           If the procedure requires that you manually reboot theE           system from the original system root (usually SYS0), do theE           following:  C           1. If you are upgrading a VAX 8530, 8550, 8810, or 8820-Na(              computer, do the following:  C              a. Restore the original copies of DEFBOO and dddGEN too6                 boot from the original root directory.  A              b. In the preupgrade procedure (Chapter 5), you madedE                 copies of the boot command procedures, DEFBOO.SAV and B                 dddGEN.SAV. To restore the original names to theseA                 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 theD              BOOT command in the following format and substitute the5              device name of the system disk for ddcu:                 >>> B ddcue  3     7-30 Upgrading the OpenVMS VAX Operating Systeme d         I                                                           Upgrade Phase 4t      E               For more information about booting your system, see the H               upgrade and installation supplement for your VAX computer.           WHERE TO GO NEXTG               When the system reboots, the procedure displays a message '               similar to the following:   K          OpenVMS VAX Version 6.2  Major version id = 1 Minor version id = 0t  D               After the system reboots, the procedure continues withI               upgrade Phase 5. Do not move the system disk to a different F               drive. The system disk must remain in the same drive for5               the procedure to continue with Phase 5.                                                                 I                           Upgrading the OpenVMS VAX Operating System 7-31     o           Upgrade Phase 5     E     _________________________________________________________________        Upgrade Phase 5n         WHAT THE PROCEDURE DOESw?           At the beginning of Phase 5, the procedure displays ar+           message similar to the following:s  =           Continuing with OpenVMS VAX V6.2 Upgrade Procedure.,  A                Upgrade Phase 5            22-JUN-1995 17:45:24.03n  C           During Phase 5, the upgrade procedure does the following:a  9           1. Deletes the temporary [SYSF] directory tree.i  D           2. Cleans up files used only during the upgrade procedure.  @           3. Converts all VAXVMSSYS.PAR parameter files found in0              system roots to Version 6.2 format.  >           4. If you have DECnet Phase IV installed, checks the?              security of DECnet for OpenVMS objects and images.o  A           5. Displays messages listing tasks that you can performe@              after the upgrade procedure is completed. Chapter 8"              explains these tasks.                                    3     7-32 Upgrading the OpenVMS VAX Operating Systemy i  c      I                                                           Upgrade Phase 6d    I         __________________________________________________________________           Upgrade Phase 6f             INTRODUCTIONC               At the beginning of Phase 6, the procedure displays a_/               message similar to the following:t  D                  Continuing with OpenVMS VAX V6.2 Upgrade Procedure.  C                       Upgrade Phase 6       22-JUN-1995 17:45:25.03   9                  Configuring all devices on the system...E  O                  %STDRV-I-STARTUP, VMS startup begun at 22-JUN-1995 17:45:25.03f           RESTORING SYSTEM FILESI               The procedure restores SYS$SPECIFIC and SYS$COMMON versions_H               of the following system files that were renamed with .COM_H               OLD_SPECIFIC and .DAT_OLD_SPECIFIC extensions during Phase               1:  "                  SYSTARTUP_VMS.COM                  SYCONFIG.COMo"                  SYPAGSWPFILES.COM                  SYSECURITY.COM                   SYSHUTDWN.COM                  SYLOGIN.COM                  LOGIN.COM                  SYLOGICALS.COMn0                  AGEN$NEW_SATELLITE_DEFAULTS.DAT+                  AGEN$NEW_NODE_DEFAULTS.DATr"                  LAT$SYSTARTUP.COM                   TFF$STARTUP.COM  G               You might not have site-specific versions of all of these F               files. The procedure will display a message listing each%               file as it is restored.   F               You might receive any of the following network messages,#               which can be ignored:e  >                  %NCP-W-UNRCMP, Unrecognized component, Object    I                           Upgrading the OpenVMS VAX Operating System 7-33f r  t           Upgrade Phase 6e      
           Or:e  $              %NCP-I-SUCCESS, Success              Object = X$X04              %NML-I-RECDELET, Database entry deleted       REGISTERING LICENSESA           The upgrade procedure also gives you the opportunity tor+           register any additional licenses.i  7           The procedure displays the following message:l  N             If you have Product Authorization Keys (PAKs) to register, you can             register them now.  G        * Do you want to register any Product Authorization Keys? (Y/N):                                                           3     7-34 Upgrading the OpenVMS VAX Operating Systemo t  o      I                                                           Upgrade Phase 6       G               You do not have to reregister your OpenVMS VAX license orwD               licenses for the following system integrated products:                    VAXclusters#                  DECnet for OpenVMSd                  RMS Journaling !                  Volume Shadowinga  F               If you want to register a new Product Authorization Key,G               type Yes and press the Return key. Otherwise, type No and                press Return.v  C               For more information on registering licenses, see thenD               description of VMSLICENSE.COM in Appendix A and in the8               OpenVMS License Management Utility Manual.           RUNNING AUTOGENiI               Next, the procedure displays the following message and runse               AUTOGEN:  E               Running AUTOGEN to compute the new SYSTEM parameters...   A               If AUTOGEN encounters any problems, it displays the                 following message:  M       %AUTOGEN-W-REPORT, Warnings were detected by AUTOGEN. Please review thenJ               information given in the file SYS$SYSTEM:AGEN$PARAMS.REPORT.  @               If AUTOGEN displays this message, be sure to checkB               AGEN$PARAMS.REPORT as one of your postupgrade tasks.=               This task is described in the section Examiningn.               AGEN$PARAMS.REPORT in Chapter 8.            SHUTTING DOWN THE SYSTEMG               After AUTOGEN finishes, the procedure displays a sequence 9               of shutdown messages that begins like this:E  N               The system is shutting down to allow the system to boot with theF               generated site-specific parameters and installed images.  M               The system will automatically reboot after the shutdown and the '               upgrade will be complete.   E                        SHUTDOWN -- Perform an Orderly System Shutdowno                  .                  .                  .  I                           Upgrading the OpenVMS VAX Operating System 7-35                 Upgrade Phase 6V      E           The system shuts down and will reboot automatically if yourwB           system is set up to do so. If the system does not rebootA           automatically, reboot it manually. For more information B           on booting your system, see the upgrade and installation+           supplement for your VAX computer.        BOOTING VOTING NODESB           If you are upgrading a standalone system, go to the next           step.s  D           If you are upgrading a VAXcluster system, the system mightD           hang when you try to reboot the upgraded system disk. ThisE           is because the total cluster value is less than the cluster E           quorum value. To remedy this situation, boot voting members D           that run from the system disk you just upgraded. (For moreA           information about quorum values and voting members, seelD           VMScluster Systems for OpenVMS.) All nodes that are booted3           at this time will run AUTOGEN and reboot.-       EXECUTING STARTUP >           After the system reboots, the procedure displays the           following message:  E           ***********************************************************.             OpenVMS VAX V6.2  G           You have SUCCESSFULLY installed the OpenVMS operating system.   C           The system is now executing the STARTUP procedure. Please E           wait for the completion of STARTUP before logging in to the            system.   E           ***********************************************************   C           Finally, the procedure displays informational messages asm6           well as accounting information. For example:  C     %STDRV-I-STARTUP, OpenVMS startup begun at 22-JUN-1995 18:27:30r        .        .        .L     %SET-I-INTSET, login interactive limit=64, current interactive value = 0  <       SYSTEM       job terminated at 22-JUN-1995 18:30:00.00  3     7-36 Upgrading the OpenVMS VAX Operating Systemt    t      I                                                           Upgrade Phase 6_                 Accounting information:L           Buffered I/O count:        133   Peak working set size:        401L           Direct I/O count:           12   Peak virtual size:           2379L           Page faults:               325   Mounted volumes:                0L           Charged CPU time 0 00:00:55.23   Elapsed time        0 00:01:31.24  H               At this point the OpenVMS VAX operating system is running.           LOGGING INE               Press the Return key. The system asks for the user name H               and password. Log in to the SYSTEM account so that you canH               perform the postupgrade procedures described in Chapter 8.  .                    Welcome to OpenVMS VAX V6.2               Username: SYSTEM               Password:a                  .                  .                  .  E               If you forget the password, follow the instructions formC               performing an emergency startup in the OpenVMS Systemt+               Manager's Manual: Essentials.            WHERE TO GO NEXTH               Go to Chapter 8 to perform the required postupgrade tasks.                                      I                           Upgrading the OpenVMS VAX Operating System 7-37V 6                       I                                                                         8cI         _________________________________________________________________e  I                                               After Upgrading OpenVMS VAX   I         _________________________________________________________________            Overview  E               After you upgrade the OpenVMS VAX operating system, youOH               need to perform several important tasks before you can useG               the system. This chapter describes the following tasks in )               the order you perform them:S  &               o  Verifying system time  2               o  Restoring the preferred node list  >               o  Replacing SYSUAF.DAT and VMS$AUDIT_SERVER.DAT  -               o  Examining AGEN$PARAMS.REPORTd  2               o  Checking the size of system files  2               o  Examining your command procedures  '               o  Changing MODPARAMS.DATs  ?               o  Updating your DECnet for OpenVMS configurationo  7               o  Converting your network proxy databaseh  ,               o  Updating your console media  /               o  Decompressing system librariesu  H               o  Testing the system with UETP, the user environment test                  package  :               o  Increasing free space on your system disk  %               o  Purging system files   D               o  Restoring your modifications to the system password                  dictionary   8               o  Customizing DECwindows support software  I               o  Preparing to run the OpenVMS Management Station software   I                                           After Upgrading OpenVMS VAX 8-1n U  m           Overview      '           o  Backing up the system diskl             o  Running AUTOGEN  1           o  Completing the postupgrade checklistR  ?           If you are an experienced system manager, you can use%B           the checklist at the end of this chapter to complete the&           necessary postupgrade tasks.  B           If you are a less-experienced system manager, you shouldD           read the entire chapter and then use the checklist to make<           sure you have completed all the postupgrade tasks.                                                                #     8-2 After Upgrading OpenVMS VAX  d  l      I                                                     Verifying System TimeE    I         _________________________________________________________________            Verifying System Time              INTRODUCTIONI               During the upgrade, the procedure displayed the system time G               and gave you the opportunity to enter the correct time if /               the displayed time was incorrect.   E               Now that you have upgraded your system, verify that the?G               system time is correct by entering the following command:r                 $ SHOW TIME_  4               The system displays the date and time.            HOW TO RESET SYSTEM TIMEH               If the time displayed by your system is not correct, resetE               it by entering the command SET TIME using the followingf               format:   +               SET TIME=dd-mmm-yyyy:hh:mm:sso                 For example:  -               $ SET TIME=22-JUN-1995:18:35:305  #         COMPENSATING FOR TIME ZONES D               If your system communicates with systems in other timeD               zones, you can use the time conversion service and theA               Coordinated Universal Time (UTC) system services tolB               compensate for differences in time stamps because ofI               differing time zones. For more information, see the OpenVMSc2               System Manager's Manual: Essentials.                      I                                           After Upgrading OpenVMS VAX 8-3r o  e      %     Restoring the Preferred Node List     E     _________________________________________________________________D  %     Restoring the Preferred Node Listf         BACKGROUND@           After the upgrade completes, the queuing system on the=           upgraded nodes is enabled, and you must restore thei4           preferred node list for the queue manager.    &     TO RESTORE THE PREFERRED NODE LIST4           Enter the following command from any node:  ;           START/QUEUE/MANAGER/ON=(node1, node2 . . . noden)   A           For node1, node2, and so forth, supply the names of the C           nodes-separated by commas-that you want to restore to them           preferred node list.                                                      #     8-4 After Upgrading OpenVMS VAX  p  d      I                             Replacing SYSUAF.DAT and VMS$AUDIT_SERVER.DAT     I         _________________________________________________________________   5         Replacing SYSUAF.DAT and VMS$AUDIT_SERVER.DATe             BACKGROUNDD               If you permanently store the SYSUAF.DAT and VMS$AUDIT_D               SERVER.DAT files on the system disk, go to the section+               Examining AGEN$PARAMS.REPORT.   G               If you do not permanently store SYSUAF.DAT and VMS$AUDIT_oC               SERVER.DAT on the system disk, you copied them to the D               system disk before you did the upgrade. During upgrade2               procedure, these files were updated.  G               Note: If you did a rolling upgrade, the shared version ofr)               SYSUAF.DAT was not updated.-  $         HOW TO REPLACE UPDATED FILESD               Copy the updated versions of SYSUAF.DAT and VMS$AUDIT_H               SERVER.DAT from the system disk to the directory where you                usually keep them.                                                I                                           After Upgrading OpenVMS VAX 8-5V o  s            Examining AGEN$PARAMS.REPORT    E     _________________________________________________________________         Examining AGEN$PARAMS.REPORT         BACKGROUND9           When AUTOGEN runs, it writes informational and, 4           if necessary, warning messages to the fileB           SYS$SYSTEM:AGEN$PARAMS.REPORT. You can view the contents8           of this report file to examine these messages.         TO VIEW THIS REPORTmA           To display AGEN$PARAMS.REPORT on your screen, enter thet5           following command and press the Return key:   .           $ TYPE SYS$SYSTEM:AGEN$PARAMS.REPORT  D           If the report includes a message similar to the following,B           you can modify the size of the PAGE, SWAP, or DUMP file:    ******************uO  %AUTOGEN-W-DSKSPC, The disk on which DISK$OpenVMS062:[SYS0.SYSEXE]PAGEFILE.SYSeH         resides would be over 95% full if it were modified to hold 20000         blocks.V  ******************s  ?           For more information about modifying the sizes of therE           PAGE, SWAP, and DUMP files, see Checking the Size of System            Files.                                #     8-6 After Upgrading OpenVMS VAXa i  h      I                                         Checking the Size of System Files     I         _________________________________________________________________   )         Checking the Size of System Files7             BACKGROUNDG               AUTOGEN sets the following files at sizes appropriate for_               your system:  $                  [SYSEXE]SYSDUMP.DMP%                  [SYSEXE]PAGEFILE.SYS %                  [SYSEXE]SWAPFILE.SYS   &         TO MODIFY SIZE OF SYSTEM FILESF               For special workloads or configurations, you can specifyG               different sizes for these files. Check the sizes of these H               files to be sure they meet your needs. Log into the SYSTEM6               account and enter the following command:  %               $ @SYS$UPDATE:SWAPFILES   D               For more information, see the OpenVMS System Manager's!               Manual: Essentials.s                                              I                                           After Upgrading OpenVMS VAX 8-7  D  e      %     Examining Your Command Procedures     E     _________________________________________________________________t  %     Examining Your Command Proceduresa         BACKGROUNDC           The upgrade procedure places a new version of WELCOME.TXTUB           on your system disk. If your system uses a site-specificB           version of this file, you must modify the new version of%           the file with your changes._         FILES TO EXAMINEC           The upgrade procedure restores your site-specific version D           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.COMs              LAT$SYSTARTUP.COM              TFF$STARTUP.COM  B           The upgrade procedure provides new templates for some ofE           these files with the .TEMPLATE extension. The new templatesvA           can include features that are not in your site-specificaE           files. Check the templates against your site-specific filesi+           and edit your files as necessary.   D           Remember, you do not need a START/QUEUE/MANAGER command inC           your startup file because the queue manager automatically -           starts up when you boot the system.M                    #     8-8 After Upgrading OpenVMS VAX. n         I                                                    Changing MODPARAMS.DATF    I         _________________________________________________________________M           Changing MODPARAMS.DAT             BACKGROUNDC               Review the file SYS$SYSTEM:MODPARAMS.DAT. The upgrade C               procedure created a new version of this file. The old G               version is named SYS$SYSTEM:MODPARAMS.DAT_OLD. Modify the 6               new file, if necessary, for your system.             WHAT TO LOOK FORD               If you are upgrading a VAXcluster, you must update theF               MODPARAMS.DAT file for each VAX computer that boots fromD               the system disk. Make sure the EXPECTED_VOTES value isH               correct. The value is the sum of all VOTES in the cluster.A               For example, if there are five VAX computers in therG               cluster, and each has one VOTE, the value is five. As you G               reboot each VAX computer, AUTOGEN runs automatically. ThedD               cluster forms when you have booted enough computers to$               attain cluster quorum.  I               For more information, refer to the OpenVMS System Manager's >               Manual: Tuning, Monitoring, and Complex Systems.                                          I                                           After Upgrading OpenVMS VAX 8-9            /     Updating Your DECnet Phase IV Configurationc    E     _________________________________________________________________t  /     Updating Your DECnet Phase IV Configuration          INTRODUCTIOND           If you are not running DECnet Phase IV software, skip thisD           section and go to the section Updating Your Console Media.  =           If you are running DECnet Phase IV software, do they           following:        CHECK NETWORK SECURITY LEVEL           Overview  B           The security of DECnet for OpenVMS objects and images on?           your system are checked during Phase 5 of the upgrade ?           procedure. If your DECnet configuration does not meet C           the default level of security, the procedure displays the D           following message recommending that you run the NETCONFIG_#           UPDATE command procedure.   K      The upgrade has detected items which should be reviewed to ensure that ;      DECnet for OpenVMS will operate properly and securely.y  L      Once the upgrade completes, you should manually review the items listedI      above.  Failure to do so could leave your node vulnerable to certain J      forms of attack.  For more information, consult the OpenVMS VAX Guide      to System Security.  J      You can execute the command procedure SYS$UPDATE:NETCONFIG_UPDATE.COMK      to update the security of your existing DECnet configuration. For moreOH      information on NETCONFIG_UPDATE.COM see the OpenVMS VAX Upgrade and      Installation Manual.   E           NETCONFIG_UPDATE.COM is a command procedure introduced withoC           VMS Version 5.2 that implements several security measuresiA           that affect default access to your system. When you runo@           NETCONFIG_UPDATE.COM, your configuration database doesB           not change, except for the changes you might make to theB           default DECNET account or to the accounts you can create           for specific objects.   D           You can use NETCONFIG_UPDATE.COM to increase your level ofB           network security only. The procedure does not prompt youC           for input if your network configuration meets the minimumy1           level established with VMS Version 5.2.o  $     8-10 After Upgrading OpenVMS VAX           I                               Updating Your DECnet Phase IV Configurationr      G               NETCONFIG_UPDATE.COM generates passwords for each accountgE               that you decide to keep in your configuration database.yI               For example, if you currently have a default DECNET account I               and decide to keep it, NETCONFIG_UPDATE.COM generates a newtI               password for it and replaces the existing password with them               new one.  >         RUN THE NETWORK CONFIGURATION UPDATE COMMAND PROCEDUREB               The following is an example of how to run NETCONFIG_               UPDATE.COM:   @               Note: Depending on your network configuration, theD               procedure might not display all of the questions shown               in this example.  -               1. Enter the following command:o  /                  $ @SYS$UPDATE:NETCONFIG_UPDATE*  >                  The procedure displays the following message:  M                       DECnet for OpenVMS node configuration upgrade procedure   J                       This procedure will allow you to create, display andN                       optionally execute the necessary commands to update yourJ                       executor and object database characteristics so thatN                       they will be compatible with V5.2 of DECnet for OpenVMS.  2                       Getting Executor Information0                       Getting Object Information  9                       Modifying Executor node 6.36 (KRUP)TK                  Do you wish a default nonprivileged DECnet account?  [NO]:M  E               2. The default DECnet account, named DECNET, allows alleD                  network objects general access to the system. It isE                  only appropriate for networks with very low securityuA                  requirements. For networks with greater security B                  requirements, Digital recommends separate defaultI                  accounts for specific network objects. After you respond E                  to this prompt, the procedure displays the following0                  message:   @                  Do you wish to disable the TASK object?  [YES]:  I                                          After Upgrading OpenVMS VAX 8-11u k         /     Updating Your DECnet Phase IV Configurationa      D           3. The TASK object, by means of the default DECnet account>              (DECNET), allows user-written command procedures-E              including those that can be used in attempted break-ins- C              to be executed on your system. You can disable default C              access to the TASK object and still allow remote user-i@              written command procedures to run on your system by@              using access control strings or proxy access. AfterC              you respond to this prompt, the procedure displays them              following message:   G              Do you want a default account for the MAIL object?  [YES]:h  B           4. MAIL is an image that provides personal mail services@              for VMS systems. To receive MAIL, you must create aB              default account for the MAIL object. An account namedD              MAIL$SERVER will be created on your system if you replyE              Yes to this query. After you respond to this prompt, the_6              procedure displays the following message:  E              Do you want a default account for the FAL object?  [NO]:   A           5. FAL (File Access Listener) is the remote file access B              facility. FAL is an image that receives and processesE              remote file access requests for files at the local node.i@              A default account for FAL allows network access, byC              any remote user, to any files marked world accessible. B              It also allows any remote user to create files in any@              directory with world WRITE access. An account namedC              FAL$SERVER will be created on your system if you reply E              Yes to this query. After you respond to this prompt, the 6              procedure displays the following message:  H              Do you want a default account for the PHONE object?  [YES]:  D           6. PHONE is an image that allows online conversations withC              users on remote OpenVMS systems. A default account for A              this object lets anyone in the network get a list ofiB              users currently logged in to the local system. A userE              can then attempt to log in using the list of user names.CB              An account named PHONE$SERVER will be created on yourE              system if you reply Yes to this query. After you respond A              to this prompt, the procedure displays the following               message:   F              Do you want a default account for the NML object?  [YES]:  $     8-12 After Upgrading OpenVMS VAX c  s      I                               Updating Your DECnet Phase IV Configuration       B               7. NML is the Network Management Listener. A defaultI                  account for this object lets remote users issue NCP TELLnG                  commands to gather and report network information fromkG                  your volatile DECnet for OpenVMS databases. An account.C                  named NML$SERVER will be created on your system if G                  you reply Yes to this query. After you respond to this F                  prompt, the procedure displays the following message:  J                  Do you want a default account for the VPM object?  [YES]:  G               8. VPM is the VMS Performance Monitor. To use the clusterhF                  monitoring features of the Monitor Utility (MONITOR),H                  you must create a default VPM account. An account namedG                  VPM$SERVER will be created on your system if you reply I                  Yes to this query. After you respond to this prompt, theo:                  procedure displays the following message:  M                  Do you want a default account for the MIRROR object?  [YES]:   B               9. MIRROR is an image that is used for most types ofF                  loopback tests, including those run during the DECnetC                  phase of the UETP. To run most loopback tests, youoE                  must create a default account for the MIRROR object.1F                  An account named MIRRO$SERVER will be created on your7                  system if you reply Yes to this query.   I               10.Next the procedure displays a series of commands and ther#                  following message:e  C                  Do you wish to execute these commands now?  [YES]:a  H               11.If you execute the commands, the procedure displays the#                  following message:s  I                          The DECnet for OpenVMS database has been updated   "               For_More_Information  G               For a description of the network configuration procedure,_E               NETCONFIG.COM, refer to the DECnet for OpenVMS Guide tonH               Networking or to the DECnet for OpenVMS Networking Manual.        I                                          After Upgrading OpenVMS VAX 8-13u s  e      /     Updating Your DECnet Phase IV Configuration       3     RUN THE CLUSTER MEMBER UPDATE COMMAND PROCEDURE <           When you run NETCONFIG_UPDATE.COM on a member of a:           VAXcluster environment, the NETCONFIG_UPDATE.COM9           procedure creates the secondary procedure named <           SYS$COMMON:[SYSMGR]UPDATE_CLUSTER_MEMBERS.COM. TheE           NETCONFIG_UPDATE.COM procedure instructs you to run UPDATE_ C           CLUSTER_MEMBERS.COM on the other VAXcluster members. This A           secondary procedure modifies the default access of eachSE           VAXcluster member exactly as you modified that of the first_           member.   @           To run UPDATE_CLUSTER_MEMBERS.COM using SYSMAN, do the           following:  !           $ RUN SYS$SYSTEM:SYSMANS5           SYSMAN> SET ENVIRONMENT/CLUSTER/USER=SYSTEMo                Remote Password:i  :                %SYSMAN-I-ENV, current command environment:3                        Clusterwide on local clusterSE                        Username SYSTEM will be used on nonlocal nodestC           SYSMAN> DO @SYS$COMMON:[SYSMGR]UPDATE_CLUSTER_MEMBERS.COMu           SYSMAN> EXIT                                            $     8-14 After Upgrading OpenVMS VAX e  h      I                                    Converting Your Network Proxy DatabaseO    I         _________________________________________________________________n  .         Converting Your Network Proxy Database             BACKGROUNDH               If you upgraded from an OpenVMS VAX Version 6.1 system, go9               to the section Updating Your Console Media.   I               If you upgraded from an OpenVMS VAX Version 6.0 system, you.?               must perform the tasks described in this section._  B               OpenVMS VAX Version 6.2 software creates a new proxyA               database that is managed by the new security server G               process. After upgrading to Version 6.2, you must convertEF               your current proxy database (SYS$SYSTEM:NETPROXY.DAT) to8               the new format (SYS$SYSTEM:NET$PROXY.DAT).  D               To perform this task, you must have the network up andG               running. If you installed the DECnet/OSI layered product,SC               the network was automatically started. If you did notsD               install the DECnet/OSI layered product and the networkE               is not up and running, you can start it by entering theC                following command:  %               $ @SYS$MANAGER:STARTNETi  1         HOW TO CONVERT THE NETWORK PROXY DATABASEd=               To accomplish the conversion, do the following:   H               1. Shut down the security server by entering the following                  command:t  +                  $ SET SERVER SECURITY/EXIT   G               2. Define logical names for the location of your existing E                  proxy database and for the location of the converted :                  proxy database by entering the following:  :                  $ DEFINE NETPROXY SYS$SYSTEM:NETPROXY.DAT<                  $ DEFINE NET$PROXY SYS$SYSTEM:NET$PROXY.DAT  F               3. Run the proxy database conversion utility by entering                  the following:P  /                  $ RUN SYS$SYSTEM:CONVERT_PROXY   I                                          After Upgrading OpenVMS VAX 8-15            *     Converting Your Network Proxy Database      D           4. Restart the security server with the following command:  (              $ SET SERVER SECURITY/START  B           If you have not installed the DECnet/OSI layered productC           but do so later, you must repeat this conversion process.        SAVE OLD DATABASEaA           Do not delete the old proxy database file NETPROXY.DAT.tE           DECnet Phase IV and many layered products use the old file. A           If you delete the NETPROXY.DAT file by mistake, you can E           restore it from the backup copy of the system disk you made_'           before performing an upgrade._                                                                $     8-16 After Upgrading OpenVMS VAX s  n      I                                               Updating Your Console Medias    I         _________________________________________________________________f  #         Updating Your Console Media_  D               If your computer does not use console media, skip thisF               section and go to the Decompressing the System Libraries               section.  D               If your computer uses console media, you must copy theG               Version 6.2 VMB.EXE onto your system's console media. TheNG               procedure for accomplishing this differs depending on theGF               VAX series computer you have. Follow the instructions in<               the section that applies to your VAX computer.  <         VAX 8530, 8550, 8810 (8700), 8820-N (8800) COMPUTERSH               If you have one of the VAX 8000 series computers listed to)               the left, do the following:l  B               1. Place a blank RX50 diskette in one of the consoleE                  diskette drives. The console refers to the upper (orAC                  left-hand) diskette drive as DZ1 while the OpenVMS G                  VAX operating system refers to it as CSA1. The console G                  refers to the lower (or right-hand) drive as DZ2 while G                  the OpenVMS VAX operating system refers to it as CSA2.   I               2. Make sure the diskette drives have been connected to the :                  OpenVMS VAX operating system, as follows:  "                  $ SHOW DEVICE CSAJ                  Device                  Device           Error     VolumeJ                   Name                   Status           Count      Label?                  CSA0:         (SYSTEM)  Online               0e?                  CSA1:         (SYSTEM)  Online               0i?                  CSA2:         (SYSTEM)  Online               0   G                  If the drives are not connected, the following messageM                  is displayed:  >                  %SYSTEM-W-NOSUCHDEV, no such device available  B                  If this message is displayed, enter the following6                  commands (you need CMKRNL privilege):  (                  $ RUN SYS$SYSTEM:SYSGEN(                  SYSGEN> CONNECT CONSOLE                  SYSGEN> EXIT   I                                          After Upgrading OpenVMS VAX 8-17c t  q           Updating Your Console Mediaa      ?           3. To initialize the diskette, enter a command in thei              following format:  ?              $ INITIALIZE/STRUCTURE=1 device-name: volume-label   E              Substitute CSA1 or CSA2 for device-name. Substitute a 1- @              to 12-character name for volume-label. For example:  6              $ INITIALIZE/STRUCTURE=1 CSA1: V61CONSOLE                                                                        $     8-18 After Upgrading OpenVMS VAX h         I                                               Updating Your Console Medias      D               4. Enter the following commands to mount the diskette,B                  create the required directories, and copy the newE                  VMB.EXE to the diskette. Substitute CSA1 or CSA2 fori                  device-name.   1                  $ MOUNT/OVERRIDE=ID device-name: :                  $ CREATE/DIRECTORY device-name:[TRANSFER]A                  $ COPY SYS$SYSTEM:VMB.EXE device-name:[TRANSFER]   H               5. Once you have copied all the files, enter the followingI                  command to dismount the diskette. (Leave the diskette inhE                  the drive.) Substitute CSA1 or CSA2 for device-name.p  (                  $ DISMOUNT device-name:  F               6. To enter console mode, press Ctrl/P. To exit from the>                  console program, enter the following command:                    >>> EXIT   F               7. Open the diskette drive door, pause for a moment, and>                  close it. The red indicator light will flash.  G               8. To copy VMB.EXE from the diskette to the console fixed.9                  disk drive, enter the following command:e  =                  $ COPY DZu:[TRANSFER]VMB.EXE   LB0:[CONSOLE]   /                  Substitute DZ1 or DZ2 for DZu.c  F                  The fixed drive in the console is known by two names,A                  DW2 and LB0. Most console files are stored using D                  the name LB0. If the system displays a message thatG                  describes a protection violation on the output device, E                  copy the files using the device name DW2 rather than                   LB0.   E               9. When you have finished copying the files, remove the )                  diskette from the drive.u  F               10.Restart the console program by entering the following-                  command and pressing Return:                     $ RUN CONTROL  I               11.Return to the operating system by entering the followinga-                  command and pressing Return:   )                  >>> SET TERMINAL PROGRAMp  I                                          After Upgrading OpenVMS VAX 8-19f r  o           Updating Your Console Media,      C     VAX 11/730, 750, 780, 785 AND VAX 8200, 8250, 8300, 8350, 8600,t     8650 COMPUTERSA           If you have one of the VAX 700 or 8000 series computersl=           listed to the left, 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  8           o  Copies the new VMB.EXE to the console media  D           o  Updates the BOOT58 file for the VAX 11/750, 8200, 8250,$              8300 and 8350 computers  C           To update the console media, use the following procedure:$  )           1. Log into the SYSTEM account.   E           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 foryB              device-name; if you are updating one of the other VAX1              computers, use CSA1 for device-name.d  $              $ RUN SYS$SYSTEM:SYSGEN$              SYSGEN> CONNECT CONSOLE              SYSGEN> EXITe5              $ EXCHANGE DIRECTORY device-name:VMB.EXEr  I              Directory of RT-11 volume TINES$CSA1:      22-JUN-1995 18:40   ,                VMB.EXE      80   22-JUN-1995  K              Total of 1 file, 80 blocks.  Free space 43 blocks, largest 23.   A              If the size of the current VMB, plus the free space,e@              does not equal at least 120 blocks, delete unneeded;              files on the console until you have 120 blocksyE              available. In the above example, the size of the currentr@              VMB.EXE (80 blocks) plus the free space (43 blocks)C              equals 123 blocks, so files do not have to be deleted.   B           3. Enter the following command and press the Return key:  -              $ @SYS$UPDATE:UPDATE_CONSOLE.COM   B           4. If you are updating the console medium for a VAX 8600E              or VAX 8650 computer, the new VMB.EXE is copied onto the1              console medium.  $     8-20 After Upgrading OpenVMS VAX           I                                               Updating Your Console MediaE      F                  If you are updating the console medium for one of theE                  other VAX computers, the procedure uses the EXCHANGEnG                  procedure to copy the contents of the existing consolebI                  medium, merge the new files onto the copy of the console H                  medium, and create a new version of the console medium.F                  When the computer is ready to create the new version,E                  it displays a message asking you to insert a scratch I                  tape cassette or diskette. Take out the original consoles-                  medium and insert a new one.            VAX 9000         COMPUTERSeG               VAX 9000 computers use a special version of VMB.EXE namedtD               VMB9AQ.EXE. The upgrade procedure automatically copiesB               a new version of this file to the console hard disk.H               However, if for some reason you need to update the consoleE               hard disk, use the UPDATE_CONSOLE.COM command procedure G               described for the VAX 11/730, 750, 780, 785 and VAX 8200,sI               8250, 8300, 8350, 8600, 8650 computers. The device name for 5               the VAX 9000 console hard disk is CSA1.o                                                  I                                          After Upgrading OpenVMS VAX 8-21e o         &     Decompressing the System Libraries    E     _________________________________________________________________   &     Decompressing the System Libraries       BACKGROUNDD           Decompressing the system libraries gives the system fasterD           access to the libraries. You can decompress all the systemD           libraries or just some of them. Table 8-1 gives the numberA           of blocks consumed by each library after decompression.   :           Table 8-1 Sizes of Decompressed System LibrariesE           ___________________________________________________________ @           Library           Blocks      Library           BlocksE           ___________________________________________________________o>           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      102E           ___________________________________________________________ $     8-22 After Upgrading OpenVMS VAX t  n      I                                        Decompressing the System Libraries             H               The additional amount of disk space required to decompressF               all system libraries is about 13,500 blocks. To find outG               how much disk space you have, enter the following command '               and press the Return key:s  )               $ SHOW DEVICE SYS$SYSDEVICEc  #         HOW TO DECOMPRESS LIBRARIES @               You execute the LIBDECOMP.COM command procedure toD               decompress the system libraries. To run LIBDECOMP, logG               into the SYSTEM account, enter the following command, andt               press Return:s  )               $ @SYS$UPDATE:LIBDECOMP.COM                                                   I                                          After Upgrading OpenVMS VAX 8-23  D  o      &     Decompressing the System Libraries      1           The following information is displayed:c  1                 VMS Library Decompression Utilitye           Options:  K          1  HELPLIB.HLB          13  DBG$UIHELP.HLB       25  PATCHHELP.HLBoK          2  STARLET.OLB          14  DBG$HELP.HLB         26  PHONEHELP.HLBaE          3  VAXCCURSE.OLB        15  EXCHNGHLP.HLB        27  SDA.HLBOK          4  VAXCRTL.OLB          16  NCPHELP.HLB          28  SHWCLHELP.HLBrH          5  VAXCRTLG.OLB         17  ANLRMSHLP.HLB        29  SYSGEN.HLBF          6  DECCCURSE.OLB        18  DISKQUOTA.HLB        30  TECO.HLBI          7  DECCRTL.OLB          19  EDFHLP.HLB           31  UAFHELP.HLB J          8  DECCRTLG.OLB         20  TPUHELP.HLB          32  EVE$HELP.HLBM          9  ERFLIB.TLB           21  ACLEDT.HLB           33  EVE$KEYHELP.HLBeJ          10  STARLETSD.TLB        22  INSTALHLP.HLB        34  STARLET.MLBF          11  MAILHELP.HLB         23  LATCP$HELP.HLB       35  LIB.MLB1          12  EDTHELP.HLB          24  MNRHELP.HLBh  4          or    A    ALL libraries to be decompressed'                E    EXIT this procedure   @      * Enter letter or number(s) of libraries to be decompressed0        (Separate multiple entries with a comma):  <           Enter the appropriate letter or the numbers of the=           libraries you want to decompress. To decompress allIC           libraries, the process takes approximately one half hour.   C           If you prefer, you can execute LIBDECOMP interactively or A           as a batch job. If you use either of these methods, youm@           can decompress up to 8 libraries each time you executeB           LIBDECOMP by listing the names of the libraries you wantC           to decompress as parameters on the command line. (You cangB           decompress all the libraries by omitting the /PARAMETERS@           qualifier.) Be sure to separate the library names withD           commas and do not include the file extension. For example,C           to decompress the VAXCRTL.OLB, DISKQUOTA.HLB, and LIB.MLBf@           libraries as a batch job, enter the following command:  ?           $ SUBMIT/NOTIFY/PARAMETERS=(VAXCRTL, DISKQUOTA, LIB)- !           _$ SYS$UPDATE:LIBDECOMP   E           To decompress these same libraries interactively, enter thei           following command:  7           $ @SYS$UPDATE:LIBDECOMP VAXCRTL DISKQUOTA LIB   $     8-24 After Upgrading OpenVMS VAX           I                                        Decompressing the System Libraries       G               Note that, when you type the command for a batch job, youoI               separate the library names with commas and enclose the list I               within parentheses. You do not use commas or parentheses onn+               the interactive command line.o                                                                                  I                                          After Upgrading OpenVMS VAX 8-25     n            Testing the System with UETP    E     _________________________________________________________________G        Testing the System with UETP         BACKGROUND@           UETP, the user environment test package, is a software>           package that tests whether the OpenVMS VAX operatingC           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 thes@           system disk and is available only if you installed the@           optional save set VMS062.D. If you did not install the?           optional save set, you can add the UETP files to yourX!           system using VMSTAILOR.   "     WHERE TO FIND MORE INFORMATION?           For information about using VMSTAILOR see Chapter 10.   E           For complete information about UETP, see the OpenVMS System D           Manager's Manual: Tuning, Monitoring, and Complex Systems.                                                $     8-26 After Upgrading OpenVMS VAX t  h      I                                  Increasing Free Space on the System Disky    I         _________________________________________________________________,  0         Increasing Free Space on the System Disk             BACKGROUNDG               This section describes how to increase the amount of freeEC               space on your system disk. You can gain free space by F               removing optional OpenVMS VAX files that you do not needE               from the system disk or by purging old versions of someo               system files.     '         USING VMSTAILOR AND DECW$TAILOR G               To remove files you do not need from the system disk, use G               VMSTAILOR. For example, if you are not running DECnet for E               OpenVMS, you do not need the network support files. For_I               complete information about using VMSTAILOR to remove files,r               see Chapter 10.i  I               If you are running DECwindows Motif, use DECW$TAILOR to addsI               or remove DECwindows base support, workstation support, andi               fonts.  B               Note: Files installed on alternate devices cannot be               tailored.r           PURGING SYSTEM FILESG               In most cases, you can purge the following OpenVMS systemeF               files to free space on your system disk. However, beforeH               you purge any of these files, read Appendix E to make sureE               you do not purge a file version you might want to keep.                             I                                          After Upgrading OpenVMS VAX 8-27e n  e      ,     Increasing Free Space on the System Disk      !           SYS$SYSTEM:SHUTDOWN.COMf            SYS$SYSTEM:STARTUP.COM#           SYS$LIBRARY:ENCRYPSHR.EXEo           SYS$LIBRARY:*RTL*.EXES           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.EXEs%           SYS$STARTUP:VMS$LAYERED.DATS  B           To purge a file, enter the PURGE command followed by the*           file specification. For example:  )           $ PURGE SYS$SYSTEM:SHUTDOWN.COM                                                       $     8-28 After Upgrading OpenVMS VAX :         I                                 Restoring Your System Password DictionaryO    I         _________________________________________________________________   1         Restoring Your System Password Dictionary              BACKGROUND@               The OpenVMS VAX operating system screens potentialG               passwords for acceptability. The DCL command SET PASSWORDu@               takes the user's proposed password, converts it toE               lowercase (if necessary), and compares it to entries inEG               a system dictionary. If the proposed password is found inVF               the dictionary, it is rejected as a valid user password,E               and the user must suggest another. Many system managersfG               modify the system password dictionary to include words ofl)               significance to their site.o  E               During the upgrade, the procedure replaces the existingmC               system password dictionary with a new one. If you hadRD               modified the dictionary and want to restore your local@               additions, you must merge the file containing your1               additions with the new system file.   %         HOW TO RESTORE YOUR PASSWORDS C               To add your site-specific passwords to the new system E               password dictionary, enable SYSPRV and merge your local H               additions by entering the following commands, where LOCAL_E               PASSWORD_DICTIONARY.DATA is the file that contains youra               additions:  ,               $ SET PROCESS/PRIVILEGE=SYSPRVB               $ CONVERT/MERGE/PAD LOCAL_PASSWORD_DICTIONARY.DATA -9               _$ SYS$LIBRARY:VMS$PASSWORD_DICTIONARY.DATAl                            I                                          After Upgrading OpenVMS VAX 8-29e i  )      "     Customizing DECwindows Support    E     _________________________________________________________________o  "     Customizing DECwindows Support    )     CUSTOMIZE DECWINDOWS SUPPORT SOFTWAREhB           If you have installed DECwindows support software, there>           are several steps that you can take to customize theB           DECwindows environment. Depending on your configuration,?           DECwindows customization tasks include the following:   +           o  Customizing the server startupg  =           o  Using the Transmission Control Protocol/Internet:8              Protocol (TCP/IP) as a DECwindows transport  =           o  Using transports for DECwindows other than thoseb               supplied by Digital  '     HOW TO CUSTOMIZE DECWINDOWS SUPPORTnC           Go to Chapter 9 for complete instructions for customizingh+           your DECwindows support software.i  E           After you complete the tasks described in Chapter 9, return D           to this chapter to continue with the remaining postupgrade           tasks.                                        $     8-30 After Upgrading OpenVMS VAX u         I                           Preparing to Run the OpenVMS Management Station     I         _________________________________________________________________   7         Preparing to Run the OpenVMS Management Stationo             BACKGROUNDC               The OpenVMS Management Station client-server software E               provides OpenVMS system management capabilities througheF               a client application on a personal computer (PC) running                Microsoft Windows.  @               When you upgraded your OpenVMS system, the OpenVMS@               Management Station server files were automaticallyG               installed on your OpenVMS system disk. However, to obtain H               complete support, you had to select the OpenVMS ManagementF               Station client software files during the OpenVMS upgradeB               procedure. Those files are required for creating theC               installation media that you use to install the client0"               software on your PC.  #         HOW TO PREPARE YOUR SYSTEMSoF               Go to Appendix F for complete instructions for preparing@               your OpenVMS system and your PC to run the OpenVMS)               Management Station software   I               Note: If you did not select the optional OpenVMS ManagementCF               Station client software files during the installation orF               upgrade, you must add these files to your OpenVMS systemH               disk before you follow the instructions in Appendix F. UseF               the OpenVMS Version 6.2 distribution media and VMSTAILORI               to add the OpenVMS Management Station files to your system.4F               (For information about using VMSTAILOR, see Chapter 10.)                            I                                          After Upgrading OpenVMS VAX 8-31M p              Backing Up the System Disk    E     _________________________________________________________________s       Backing Up the System Disk         BACKGROUNDE           Digital recommends that you protect your work by performing(#           the following operations:o  E           o  Use SYS$UPDATE:CONSCOPY.COM to back up the console media               (if applicable).o  C           o  Make a standalone BACKUP kit on removable media and onD              the system disk..  A              Note: If your console media is a TU58 tape cartridgeoD              or an RX01 diskette, use the standalone BACKUP copy youD              made before you began the upgrade. (See the section How4              to Back Up Console Media in Chapter 5.)  %           o  Back up the system disk.        FOR MORE INFORMATIONB           For complete information about these operations, see theD           upgrade and installation supplement for your VAX computer.                                          $     8-32 After Upgrading OpenVMS VAX s  t      I                                                           Running AUTOGENt    I         _________________________________________________________________e           Running AUTOGEN              BACKGROUNDE               When you upgraded the OpenVMS VAX operating system, thetD               procedure executed AUTOGEN to set the values of systemA               parameters and the sizes of the page and swap files 1               according to the system's workload.   F               In many cases, AUTOGEN can improve system performance byI               using dynamic feedback information from the running system. F               As a postinstallation task, you should run AUTOGEN againI               using the feedback mechanism to make further adjustments to                 system parameters.  G               When AUTOGEN runs after an upgrade, it uses the parameter0F               values in SYS$SYSTEM:MODPARAMS.DAT. Note that hard-codedF               values in MODPARAMS.DAT affect AUTOGEN's calculations ofH               the feedback parameters. For AUTOGEN to properly calculateI               minimum values, you should replace the hard-coded values in_G               MODPARAMS.DAT with MIN_ values. The MIN_ prefix specifieshB               the minimum value to which a parameter can be set by               AUTOGEN.  B               If you are not satisfied with the parameter settingsH               calculated by AUTOGEN, you can modify the parameter valuesI               by editing MODPARAMS.DAT as explained in the OpenVMS SystemnH               Manager's Manual: Tuning, Monitoring, and Complex Systems.           WHEN TO RUN AUTOGEN_G               After you have upgraded the operating system, run AUTOGENi2               again using the following procedure:  E               1. After 24 hours of operation, run AUTOGEN in feedback1,                  mode and reboot the system.  F               2. Run AUTOGEN in this same way, again, two working days                  later.E  C                  Note: For the VAX 9000 computer, AUTOGEN's initial.C                  parameter calculations are conservative. To obtainBF                  parameter values that match your system workload, youD                  can run AUTOGEN in feedback mode a number of times.G                  For more information, see the upgrade and installation 7                  supplement for your VAX 9000 computer.   I                                          After Upgrading OpenVMS VAX 8-33  L  P           Running AUTOGENN      C           3. Digital recommends that you run AUTOGEN from SAVPARAMS <              through TESTFILES on a weekly basis and examineD              AGEN$PARAMS.REPORT to determine the need for additional              changes.H  E           For information about using AUTOGEN, see the OpenVMS System D           Manager's Manual: Tuning, Monitoring, and Complex Systems.                                                                            $     8-34 After Upgrading OpenVMS VAX _  _      I                                                     Postupgrade Checklist     I         _________________________________________________________________            Postupgrade Checklisto             INTRODUCTIONF               Use the following checklist to make sure you perform all.               the necessary postupgrade tasks.             DID YOU . . .w  G               <  Verify the system time? (Described in Verifying SystemH                  Time.)   G               <  Restore the preferred node list for the queue manager?CG                  (Described in the section Restoring the Preferred Nodee                  List.)   H               <  Replace SYSUAF.DAT and VMS$AUDIT_SERVER.DAT? (DescribedC                  in the section Replacing SYSUAF.DAT and VMS$AUDIT_O                  SERVER.DAT.)   :               <  Examine AUTOGEN output stored in the fileH                  AGEN$PARAMS.REPORT? (Described in the section Examining%                  AGEN$PARAMS.REPORT.)l  F               <  Examine the command procedure templates supplied withC                  OpenVMS VAX Version 6.2? (Described in the section14                  Examining Your Command Procedures.)  A               <  Examine MODPARAMS.DAT? (Described in the section )                  Changing MODPARAMS.DAT.)P  D               <  Start DECnet for OpenVMS (for DECnet Phase IV usersF                  only)? (Described in the section Updating Your DECnet)                  Phase IV Configuration.)6  D               <  Convert your network proxy database if you upgradedH                  from OpenVMS VAX Version 6.0? (Described in the section9                  Converting Your Network Proxy Database.)E  E               <  Update your console media? (Described in the section$.                  Updating Your Console Media.)  E               <  Decompress the system libraries using LIBDECOMP.COM? C                  (Described in the section Decompressing the System                   Libraries.)  I                                          After Upgrading OpenVMS VAX 8-35  c  r           Postupgrade Checkliste      E           <  Run UETP (the user environment test package) to test theaC              system? (Described in OpenVMS System Manager's Manual:t6              Tuning, Monitoring, and Complex Systems.)  @           <  Remove unwanted files and check the sizes of systemC              files? (Described in the section Increasing Free Spacet!              on the System Disk.)h  @           <  Restore your local additions to the system passwordA              dictionary? (Described in the section Restoring Youry)              System Password Dictionary.)t  E           <  Customize your DECwindows environment? (Described in the 5              section Customizing DECwindows Support.)A                                                              $     8-36 After Upgrading OpenVMS VAX    l      I                                                     Postupgrade ChecklistS      I               <  Build a standalone BACKUP kit? (Described in the section -                  Backing Up the System Disk.)S  E               <  Back up the console media? (Described in the section -                  Backing Up the System Disk.)i  G               <  Back up the system disk? (Described in the upgrade andI<                  installation supplement for your computer.)  E               <  Run AUTOGEN and reboot the system after the first 24iF                  hours of operation? (Described in the section Running                  AUTOGEN.)                                                                  I                                          After Upgrading OpenVMS VAX 8-37p n  s                    I                                                                         9 I         _________________________________________________________________   I                                   Customizing DECwindows Support Softwarew  I         __________________________________________________________________           Overview  E               This chapter describes how you can customize DECwindowsrI               support software. The DECwindows components provided on theeH               OpenVMS Version 6.2 kit supply DECwindows base support andG               workstation support files only. If you have not installeduH               either of these DECwindows components on your system, skip               this chapter.n  G               Depending on your configuration, DECwindows customization2*               tasks include the following:  /               o  Customizing the server startupX  A               o  Using the Transmission Control Protocol/InternetA<                  Protocol (TCP/IP) as a DECwindows transport  B               o  Using transports with DECwindows other than those$                  supplied by Digital  G               Note: The OpenVMS VAX operating system no longer includes I               the VMS DECwindows product. To get full DECwindows support, E               you must also install the separate DECwindows Motif for H               OpenVMS VAX layered product, which supports both the Motif#               and XUI environments.n                    I                               Customizing DECwindows Support Software 9-1t a  n      "     Customizing the Server Startup    E     _________________________________________________________________n  "     Customizing the Server Startup         NOTEE           By default, the DECwindows server no longer logs successfuly;           connect/disconnect messages to the DECW$SERVER_#_ >           ERROR.LOG file. To enable these messages, define theD           symbol DECW$SERVER_CONNECT_LOG in the DECW$PRIVATE_SERVER_D           SETUP.COM file to be "T" and restart the server. Note thatB           abnormal or unsuccessful connect/disconnect messages are%           still logged by the server.          ASSUMPTIONS @           The startup command procedures automatically determine@           most of the configuration variables for the DECwindowsC           display server. However, there are items that the commandlA           procedures cannot determine, so they make the following            assumptions:  A           o  The startup procedures normally assume that you haves?              a 75 dots/inch monitor (such as a VR260 or VR290).vA              However, if you are installing on a VAXstation 4000,iC              the startup procedures assume that you have a 100 dotsi              /inch monitor.   D           o  If you have a GPX, SPX, or LCG workstation, the startup=              procedures assume that you have a color monitor.n  A           o  The startup procedures normally assume that you have C              a North American keyboard layout (you have an LK201-AA A              or an LK201-LA keyboard). If you are installing on a D              VAXstation 4000, the startup procedures assume that you'              have an LK401-AA keyboard.X  C           o  The startup procedures assume that the server will useIC              only DECnet for OpenVMS software and local transports.               /     9-2 Customizing DECwindows Support Softwarer e  R      I                                            Customizing the Server Startup       -         HOW TO OVERRIDE INCORRECT ASSUMPTIONS I               If any of these assumptions is incorrect, you must override:               them as follows:  I               1. Make a copy of the file SYS$MANAGER:DECW$PRIVATE_SERVER__F                  SETUP.TEMPLATE and rename it to a .COM file type. TheG                  comments in this file show how to customize individual E                  workstations by adding a section of DCL commands foraG                  each workstation. You can also add DCL commands to theaD                  common section of the server startup file. By doingI                  this, you ensure that the customizations you make affectdC                  all workstations that use the server startup file.i  I               2. If your screen supports 100 dots/inch, add the followingr                  line:  /                  $ DECW$SERVER_DENSITY == "100"e  G                  Add this line to the section for each workstation thathE                  has a 100 dots/inch monitor, or add it to the commontF                  section for all workstations (if all the workstations.                  have 100 dots/inch monitors).  I               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"  H               4. The section for any workstation with color graphics andH                  a monochrome screen should contain the following lines:  (                  $ DECW$COLOR == "FALSE"*                  $ DECW$BITONAL == "FALSE"  C               5. To override the default keyboard layout, determinenE                  the correct name from the model number of your LK201V&                  keyboard, as follows:  G                  a. Turn the keyboard upside down, and look for a label F                     which specifies the model number. The model number>                     should be in a format similar to LK201-xx.  F                     If the model number is listed as LK201 without anyI                     additional characters, the information you need is onOI                     another part of the label. Look for a number that hasf)                     the following format:h  "                       nn-nnnnn-xx.  I                               Customizing DECwindows Support Software 9-3w o  c      "     Customizing the Server Startup      A              b. Use the xx part of this number to choose a keymape@                 name from Table 9-1. The table is arranged based=                 on the dialect that each keyboard is designedtA                 for. Choose the keymap ending in _DP for the datalC                 processing keyboard layout, or the keymap ending in .                 _TW for the typewriter layout.       Table 9-1 DECwindows KeymaptE     _________________________________________________________________,>     Dialect         Model               DECwindows Keymap NameE     _________________________________________________________________ B     Austrian        LK201-              AUSTRIAN_GERMAN_LK201LG_DPB     /German         (AG,LG,BG,MG)       AUSTRIAN_GERMAN_LK201LG_TW  B                     LK201-(NG,PG)       AUSTRIAN_GERMAN_LK201NG_DPB                                         AUSTRIAN_GERMAN_LK201NG_TW  B                     LK401-(AG)          AUSTRIAN_GERMAN_LK401AG_TW  A     Belgian/French  LK201-              BELGIAN_FRENCH_LK201LP_DPcA                     (AP,LP,BP,MP)       BELGIAN_FRENCH_LK201LP_TWn  A     Belgian/French  LK401-(AP)          BELGIAN_FRENCH_LK401AP_DP A                                         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  B     Canadian        LK201-              CANADIAN_FRENCH_LK201LC_DPB     /French         (AC,LC,BC,MC)       CANADIAN_FRENCH_LK201LC_TW  B     Canadian        LK401-              CANADIAN_FRENCH_LK401AC_DPB     /French         (AC,LC,BC,MC)       CANADIAN_FRENCH_LK401AC_TW  E                                              (continued on next page)e  /     9-4 Customizing DECwindows Support Softwarea e  S      I                                            Customizing the Server StartupS      +         Table 9-1 (Cont.) DECwindows Keymap I         _________________________________________________________________ B         Dialect         Model               DECwindows Keymap NameO         _________________________________________________________________      u  9         Czech           LK401-(BV)          CZECH_LK401AVn  =         Danish          LK201-              DANISH_LK201LD_DPa=                         (AD,LD,BD,MD)       DANISH_LK201LD_TW   =                         LK201-(ED,RD,FD)    DANISH_LK201RD_DPg=                                             DANISH_LK201RD_TWk  =         Danish          LK401-              DANISH_LK401AD_DP_=                         (AD,LD,BD,MD)       DANISH_LK401AD_TWD  <         Dutch           LK201-              DUTCH_LK201LH_DP<                         (AH,LH,BH,MH)       DUTCH_LK201LH_TW  9                         LK201-(NH,PH)       DUTCH_LK201NH   9                         LK401-(NH,PH)       DUTCH_LK401AHe  >         Finnish         LK201-              FINNISH_LK201LF_DP>                         (AF,LF,BF,MF)       FINNISH_LK201LF_TW>                                             FINNISH_LK401AF_TW  >         Flemish         LK201-              FLEMISH_LK201LB_DP>                         (AB,LB,BB,MB)       FLEMISH_LK201LB_TW  I                                                  (continued on next page)I  I                               Customizing DECwindows Support Software 9-5     r      "     Customizing the Server Startup      '     Table 9-1 (Cont.) DECwindows Keymap E     _________________________________________________________________ >     Dialect         Model               DECwindows Keymap NameK     _________________________________________________________________      e  :     Flemish         LK401-              FLEMISH_LK401AB_DP:                     (AB,LB,BB,MB)       FLEMISH_LK401AB_TW  :     Hungarian       LK401-(BQ)          HUNGARIAN_LK401_BQ  <     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)M  <     Norwegian       LK201-              NORWEGIAN_LK201LN_DP<                     (AN,LN,BN,MN)       NORWEGIAN_LK201LN_TW  <                     LK201-(EN,RN,FN)    NORWEGIAN_LK201RN_DP  <     Norwegian       LK401-              NORWEGIAN_LK401AN_DP<                     (AN,LN,BN,MN)       NORWEGIAN_LK401AN_TW  7     Polish          LK401-(BP)          POLISH_LK401_BPa  E                                              (continued on next page)a  /     9-6 Customizing DECwindows Support Software            I                                            Customizing the Server Startupi      +         Table 9-1 (Cont.) DECwindows KeymapnI         _________________________________________________________________ B         Dialect         Model               DECwindows Keymap NameO         _________________________________________________________________      c  >         Portuguese      LK201-              PORTUGUESE_LK201LV%                         (AV,LV,BV,MV)n  >         Portuguese      LK401-              PORTUGUESE_LK401AV%                         (AV,LV,BV,MV)   <         Russian         LK401-(BT)          RUSSIAN_LK401_BT  ;         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  C         Swiss/French    LK201-              SWISS_FRENCH_LK201LK_DP C                         (AK,LK,BK,MK)       SWISS_FRENCH_LK201LK_TW.  C         Swiss/French    LK401-              SWISS_FRENCH_LK401AK_DP C                         (AK,LK,BK,MK)       SWISS_FRENCH_LK401AK_TW   I                                                  (continued on next page)_  I                               Customizing DECwindows Support Software 9-7o p  d      "     Customizing the Server Startup      '     Table 9-1 (Cont.) DECwindows Keymap E     _________________________________________________________________ >     Dialect         Model               DECwindows Keymap NameK     _________________________________________________________________         ?     Swiss/German    LK201-              SWISS_GERMAN_LK201LL_DP ?                     (AL,LL,BL,ML)       SWISS_GERMAN_LK201LL_TWe  ?     Swiss/German    LK401-              SWISS_GERMAN_LK401AL_DPn?                     (AL,LL,BL,ML)       SWISS_GERMAN_LK401AL_TWo  2     Combined US/UK  LK201-(EE,RE,PE)    UK_LK201RE2                                         US_LK201RE  2     Combined US/UK  LK401-(EE,RE,PE)    UK_LK401AA2                                         US_LK401AAE     _________________________________________________________________aA              c. After you choose a keymap name, modify the serverVA                 startup file. For example, to change the keyboardY<                 layout to a Dutch typewriter layout, add the:                 following line to the server startup file:  A                 $ DECW$DEFAULT_KEYBOARD_MAP == "DUTCH_LK201LH_TW"C  D                 Add a line similar to this for each workstation thatB                 does not have a North American keyboard layout, orE                 add it to the common section for all workstations (if C                 all the workstations use the same keyboard layout).   A           6. To add support for the Transmission Control Protocol @              /Internet Protocol (TCP/IP) transport using the DECC              TCP/IP Services for OpenVMS product, add the followingm              line:  =              $ DECW$SERVER_TRANSPORTS == "DECNET,LOCAL,TCPIP"s  C              Add this line to the section for each workstation that B              will be using TCP/IP, or add it to the common section"              for all workstations.  =              To include support for other transports, add thecA              last part of the transport image name to the list ofeE              transports. For example, suppose you want to add supporteD              for a customer-written transport that has the following              image name:  /     9-8 Customizing DECwindows Support Software            I                                            Customizing the Server Startup       -                  SYS$SHARE:DECW_TRANSPORT_FOOs  2                  You would add the following line:  ?                  $ DECW$SERVER_TRANSPORTS == "DECNET,LOCAL,FOO"   E               7. Reboot the workstations for which you customized theA                   server startup.  H               8. Customize security as described in the Using DECwindows*                  Motif for OpenVMS manual.  I               After you start the server, a per-server logical name tablenG               is created on your system but is not added to the default .               logical name table search lists.                                                            I                               Customizing DECwindows Support Software 9-9D r  d      )     Using DEC TCP/IP Services for OpenVMSo    E     _________________________________________________________________   )     Using DEC TCP/IP Services for OpenVMS          OVERVIEWD           DECwindows contains support for the TCP/IP transport. ThisE           support requires DEC TCP/IP Services for OpenVMS, a Digital C           layered product. Before you can use the DECwindows TCP/IPnC           transport interface, you must install DEC TCP/IP Services            for OpenVMS.  B           Note: Other vendors' implementation of TCP/IP transportsD           use different call interfaces. For this reason, DECwindows?           support for TCP/IP is compatible only with DEC TCP/IP_           Services for OpenVMS.   B           You can conserve memory and process slots by configuringB           DEC TCP/IP Services for OpenVMS software for the minimum;           DECwindows requirement to support the X protocol. <           DECwindows only requires that INET_ACP be running.C           DECwindows does not require that the NFS server, the FTPD <           server, or the remote terminal servers be running.       FOR MORE INFORMATIONA           For more information about TCP/IP concepts, see the DECz>           TCP/IP Services for OpenVMS System Management Guide.  B           For information on how to configure the TCP/IP software,C           see the  DEC TCP/IP Services for OpenVMS Installation andP           Configuation Guide.                               0     9-10 Customizing DECwindows Support Software    s      I                                    Using Other Transports with DECwindowsg    I         _________________________________________________________________s  .         Using Other Transports with DECwindows             INTRODUCTION@               DECwindows supports DECnet for OpenVMS, local, andG               TCP/IP transports. However, you can use other transports, H               such as new transports for layered products and transportsD               from third party vendors, with DECwindows by writing a3               DECwindows transport interface layer.n    %         WRITING A TRANSPORT INTERFACE F               For information about writing a transport interface, see2               the VMS DECwindows Transport Manual.  D               The transport interface image's filename must have theG               following format where name is the unique transport name:S  F               DECW$TRANSPORT_name (for transports supplied by Digital)C               DECW_TRANSPORT_name (for customer-written transports)e  0         INSTALLING THE TRANSPORT INTERFACE IMAGEE               Install the image as a protected image in the SYS$SHARErG               directory (as defined by an executive mode logical name). I               Digital recommends that you install the image by adding the >               following line to SYS$MANAGER:SYSTARTUP_VMS.COM:  F            $ INSTALL CREATE SYS$SHARE:DECW_TRANSPORT_name/OPEN/SHARED-)                /HEADER_RESIDENT/PROTECTED   F               You can also include this command in a startup file that"               SYSTARTUP_VMS calls.  I               To use this transport with the DECwindows server, customize D               the server startup as described in the Customizing the5               Server Startup section of this chapter.                   I                              Customizing DECwindows Support Software 9-11v                Using the Example Transportu    E     _________________________________________________________________        Using the Example Transportt         INTRODUCTIONB           DECwindows has an example transport interface based upon@           the DEC TCP/IP Services for VMS layered product. It is?           similar to the DECwindows TCP/IP transport interface, ?           except it includes its own source files and it uses at?           different port number (5000). You can run the example <           transport interface simultaneously with the TCP/IP           transport interface.    $     HOW TO USE THE EXAMPLE TRANSPORTE           If you have installed DEC TCP/IP Services for VMS software, D           you can install and use the example transport by doing the           following:  E           1. Copy the example transport to the SYS$SHARE directory as               follows:o  H     $ COPY DECW$EXAMPLES:DECW$TRANSPORT_EXAMPLE.EXE SYS$SHARE:/PROT=W:RE  E           2. Add the following line to SYS$MANAGER:SYSTARTUP_VMS.COM:C  D     $ INSTALL CREATE SYS$SHARE:DECW$TRANSPORT_EXAMPLE /OPEN /SHARED-$         / HEADER_RESIDENT /PROTECTED  A           3. Customize the private server startup as described in C              the section Customizing the Server Startup for TCP/IP, B              except use the transport name "EXAMPLE". For example,.              you could add the following line:  E              $ DECW$SERVER_TRANSPORTS == "DECNET,LOCAL,TCPIP,EXAMPLE"o  ;           4. Reboot the workstation, or restart DECwindows.m  @           5. Customize TCP/IP security as described in the Using=              DECwindows Motif for OpenVMS manual, but use the 9              transport name "EXAMPLE" instead of "TCPIP".e  E           6. Create a DECterm window on the workstation and enter theo              following command:   E              $ SET DISPLAY /CREATE /NODE=your_node /TRANSPORT=EXAMPLEc  C              Substitute the node name of your workstation for your_n              node.  0     9-12 Customizing DECwindows Support Software C  O      I                                               Using the Example Transport       I                  Remember that the same transport must be running on bothmI                  the client and server. It is not necessary, however, forwD                  the client and the server to be on the same system.  H               7. Run any DECwindows application from the DECterm window.A                  It will now use the example transport to display.F                  graphics on your workstation screen. For example, youD                  would enter the following command to run the clock:  ,                  $ RUN SYS$SYSTEM:DECW$CLOCK                                                                      I                              Customizing DECwindows Support Software 9-13     u                    I                                                                        10 I         _________________________________________________________________   I                                           Using VMSTAILOR and DECW$TAILOR   I         _________________________________________________________________h           Overview  B               This chapter describes how to add or remove optionalF               OpenVMS VAX files and DECwindows support files from yourH               system disk using VMSTAILOR and DECW$TAILOR. You will needG               your OpenVMS VAX Version 6.2 software media kit to tailornE               on files. Any site-specific customization that has been_F               done to a class will be lost when that class is tailored               off.                                                    I                                      Using VMSTAILOR and DECW$TAILOR 10-1_                Using VMSTAILOR     E     _________________________________________________________________        Using VMSTAILORA         WHEN TO USE VMSTAILOR0E           To add or remove unwanted OpenVMS VAX files from the systemBB           disk, use VMSTAILOR. For example, if you are not runningE           DECnet for OpenVMS, and you do not need the network support C           files, you can remove those files using VMSTAILOR. If you B           later decide you want to run DECnet for OpenVMS, you canA           add the necessary files at any time using VMSTAILOR andTE           your OpenVMS VAX Version 6.2 distribution media. (Note that_A           you cannot tailor files on or off an alternate device.)L         HOW VMSTAILOR WORKS,%           VMSTAILOR has three phases:_  @           1. VMSTAILOR asks if you want to tailor your system byB              adding files (tailor on) or by deleting files (tailor              off).  C           2. If you choose to tailor files on, VMSTAILOR lists eachu?              class of OpenVMS VAX files and asks if you want to E              include them on the system disk. If you choose to tailor D              files off, VMSTAILOR lists each class of files and asks=              if you want to delete them from the system disk.c  C           3. VMSTAILOR adds or deletes the files you indicated from_E              the system disk. If you are tailoring files on, you must D              load your OpenVMS VAX Version 6.2 distribution media inB              a drive available to the system. If your distributionA              media 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 ofA           OpenVMS VAX files that can be added or deleted by using A           VMSTAILOR. For a complete list of OpenVMS VAX files andcC           their functions, see the OpenVMS System Manager's Manual: 2           Tuning, Monitoring, and Complex Systems.             o  Network Support  1                 Incoming Remote File Access filesN.                 Incoming Remote Terminal files"                 Network Test files#                 Remote Task Loading,  (     10-2 Using VMSTAILOR and DECW$TAILOR           I                                                           Using VMSTAILOR       $               o  Programming Support  ,                     Debugger utility (DEBUG)=                     Image Dump utility (ANALYZE/PROCESS_DUMP)eF                     RMS Analyze and FDL Editor utilities (ANALYZE/RMS,                      ANALYZE/FDL)-                     Message utility (MESSAGE) 8                     Object and Shareable Image libraries#                     MACRO libraries_#                     MACRO assemblero8                     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 utilityC)                     Delta/XDelta debugger,I                     System Dump Analyzer utility (ANALYZE/SYSTEM, ANALYZE                      /CRASH) 6                     System Symbol Table file (SYS.STB)4                     Miscellaneous Symbol Table files  *               o  Secure User's Environment  6                     File Access Control List utilities3                     Print and Batch Queue utilitiesA6                     Input Queue Symbiont (Card Reader);                     Accounting Log Report Generator utility                      DECdtm                 o  Utilities                        Mail utility                      DUMP utility"                     RUNOFF utility!                     Phone utility (                     OpenVMS Help library8                     OpenVMS System Messages Help Library,                     Foreign Terminal Support9                     LAT-11 terminal server (via Ethernet) %                     Standalone BACKUP F                     Error Log Report Generator utility (ANALYZE/ERROR)"                     DECTPU utility  I                                      Using VMSTAILOR and DECW$TAILOR 10-3y n              Using VMSTAILOR_      *                 Terminal Fallback facility                 TECO editor !                 EDT documentation 4                 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       REMOVING OPENVMS VAX FILES?           To remove unwanted files using VMSTAILOR, perform the            following steps:  *           1. Log in to the SYSTEM account.  B           2. Enter the following command and press the Return key:  '              $ RUN SYS$UPDATE:VMSTAILOR,  >              VMSTAILOR displays a description of the VMSTAILOR8              program and displays the following message:  7              Do you want to tailor files "ON" or "OFF"?   D           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 groupedW>              according to their function. For example, all theA              files required for network support are in one class. B              A file class is made up of many smaller groups calledD              subclasses. You can eliminate an entire class of files,D              or you can eliminate one or more of its subclasses. For              example:   (     10-4 Using VMSTAILOR and DECW$TAILOR    t      I                                                           Using VMSTAILORr                 CLASS - Network support?                    Size of entire class (with subclasses): 1499_G                    Size of common files required for any subclass: 1249sI                    Do you wish to select the entire class (default = NO)?_                     .w                     .                      .L  H               4. Decide which file classes or subclasses you do not needG                  to support your system. The VMSTAILOR program displays H                  step-by-step instructions. Follow these instructions toI                  specify which classes or subclasses of files you want to                   remove.  F               5. VMSTAILOR deletes the files you selected and displaysE                  the names of those files. After it finishes, AUTOGEN_D                  runs automatically to make the adjustments that areG                  necessary after system files are deleted. AUTOGEN alsoe$                  reboots the system.  F               Caution: To cancel VMSTAILOR during the first and second@               phases, press Ctrl/C, Ctrl/Y, or Ctrl/Z. CancelingD               VMSTAILOR during the third phase can cause a partiallyE               tailored disk. For a description of each phase, see Howm               VMSTAILOR Works.            ADDING OPENVMS VAX FILESC               To add optional OpenVMS VAX files that you previouslyuB               removed, or that you chose not to install during theC               OpenVMS VAX installation procedure, do the following:P  .               1. Log in to the SYSTEM account.  I               2. Load your distribution media in a drive available to the F                  system. For example, if your distribution media is onH                  a TK50 tape cartridge, load the first tape cartridge inH                  a TK50 drive that is available to the system. Make sure/                  the drive is online and ready.o  B                  If you are adding files from a compact disc on anI                  InfoServer, first determine whether the SYSGEN parameteroC                  SCSNODE is defined on your system (see the section B                  Preparing Your System Disk in Chapter 5) or startE                  the DECnet software, and then refer to Step 2 of the F                  Beginning the Upgrade Procedure section in Chapter 7.  I                                      Using VMSTAILOR and DECW$TAILOR 10-5i l  :           Using VMSTAILOR$      B           3. Enter the following command and press the Return key:  '              $ RUN SYS$UPDATE:VMSTAILOR   >              VMSTAILOR displays a description of the VMSTAILOR8              program and displays the following message:  7              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 theA              files required for network support are in one class. B              A file class is made up of many smaller groups calledE              subclasses. You can add an entire class of files, or youe@              can add one or more of its subclasses. For example:  $              CLASS - Network supportC                        Size of entire class (with subclasses): 1499 K                        Size of common files required for any subclass: 1249 M                        Do you wish to select the entire class (default = NO)?n                 .o                 .i                 .P  @           5. Decide which file classes or subclasses you need to?              add. VMSTAILOR displays step-by-step instructions. B              Follow these instructions to specify which classes or1              subclasses of files you want to add.g  D           6. VMSTAILOR adds the files you specified and displays theA              names of the files. After the files have been added, D              AUTOGEN runs automatically to make the adjustments thatE              are necessary after system files are added. AUTOGEN also                reboots the system.  B           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 partiallyA           tailored disk. For a description of each phase, see HowP           VMSTAILOR Works.  B           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  (     10-6 Using VMSTAILOR and DECW$TAILOR _  _      I                                                           Using VMSTAILORw      @               files. This file usually has the following format:&               SYS$UPDATE:VMSUn06n.TXT.                                                                                      I                                      Using VMSTAILOR and DECW$TAILOR 10-7m i  p           Using VMSTAILORw      >           For example, suppose you do not need the OpenVMS VAXA           Version 6.2 Phone utility (PHONE) and you run VMSTAILORmB           to remove those files. Later, you decide you want to use?           Phone. Run VMSTAILOR to return the Phone files to theeB           system disk; then, apply any OpenVMS VAX update that hasE           occurred since Version 6.2 that affected the Phone utility.O       SAMPLE SESSIONA           Example 10-1 illustrates how to add all Network SupportoB           files and selected Programming Support files to a system           disk.     )     Example 10-1 Sample VMSTAILOR Session     $ RUN SYS$UPDATE:VMSTAILORi        .        .        ./   Do you want to tailor files "ON" or "OFF"? ON   
  TAILOR-ON
  ---------D   You will now be prompted with a list of the classes and subclassesN   of OpenVMS VAX files that are optional. The size of each class and subclass M   is included in the list. This will help you decide whether or not you want  ,   to add a class or subclass to your system.  N   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 ask7   for either the entire class or any of its subclasses.   1  Total size of the system disk is 2376153 blocks. 7  Total space used on the system disk is 2241252 blocks. 6  Total space left on the system disk is 134901 blocks.    CLASS - Network support7            Size of entire class (with subclasses): 1499_?            Size of common files required for any subclass: 1249 E            Do you wish to select the entire class (default = NO)? YES   E                                              (continued on next page)i      (     10-8 Using VMSTAILOR and DECW$TAILOR           I                                                           Using VMSTAILOR       5         Example 10-1 (Cont.) Sample VMSTAILOR Sessionp    CLASS - Programming Support7           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)?J           Do you wish to select any of its subclasses (default = NO)? )YES9           Select the subclasses that you wish to provide:aG             SUBCLASS - Debugger utility (DEBUG) (4690 blocks) [NO]: YESMV             SUBCLASS - Image Dump utility (ANALYZE/PROCESS_DUMP) (48 blocks) [NO]: YESW             SUBCLASS - RMS Analyze and FDL Editor utilities (ANALYZE/RMS, ANALYZE/FDL)- !             (374 blocks) [NO]:YES B             SUBCLASS - Message utility (MESSAGE) (49 blocks) [NO]:S             SUBCLASS - Object and Shareable Image libraries (4311 blocks) [NO]: YESe:             SUBCLASS - Macro libraries (2293 blocks) [NO]:9             SUBCLASS - Macro assembler (457 blocks) [NO]:DO             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 - RMSjournaling files5           Size of entire class (with subclasses): 155f-           No subclasses in this tailor class.d@           Do you wish to select the entire class (default = NO)?  #  CLASS - System programming SupportA7            Size of entire class (with subclasses): 2286b=            Size of common files required for any subclass: 93 A            Do you wish to select the entire class (default = NO)?OF            Do you wish to select any of its subclasses (default = NO)?  "  CLASS - Secure User's Environment6            Size of entire class (with subclasses): 919<            Size of common files required for any subclass: 0A            Do you wish to select the entire class (default = NO)?h  F            Do you wish to select any of its subclasses (default = NO)?              .            .            .  I                                                  (continued on next page)o    I                                      Using VMSTAILOR and DECW$TAILOR 10-9c a  t           Using VMSTAILOR       1     Example 10-1 (Cont.) Sample VMSTAILOR Session        Files have been selected7     Do you wish to add all of the options selected? YESg3     Creating temporary command file, please wait... ?     * Enter device containing OpenVMS distribution media: mua0:           .        .        .                                                                      )     10-10 Using VMSTAILOR and DECW$TAILOR  T  O      I                                                         Using DECW$TAILOR_    I         _________________________________________________________________t           Using DECW$TAILOR              WHEN TO USE DECW$TAILORnB               You can use DECW$TAILOR to add or remove some or allD               DECwindows X11 display server, base support, and fontsE               files from the system disk. For example, if you are noteE               planning to use the DECwindows PEX (PHIGS Extensions toiC               X) support, you can remove those files. Later, if you E               decide you want DECwindows programming support, you can I               add the files to the system disk using DECW$TAILOR and yourII               DECwindows distribution media. (Note that you cannot tailor_3               files on or off an alternate device.)T  I               Note: To add or remove VMS DECwindows Motif files, refer toBI               the DECwindows Motif Version 1.2-3 for OpenVMS Installation A               Guide. DECW$TAILOR will only tailor on or off those F               DECwindows display server, base support, and font files,G               with the exception of the required files, supplied on the                OpenVMS VAX kit.           HOW DECW$TAILOR WORKS +               DECW$TAILOR has three phases:e  F               o  DECW$TAILOR asks if you want to tailor your system byF                  adding files (tailor on) or by deleting files (tailor                  off).  D               o  If you choose to tailor files on, DECW$TAILOR listsG                  each class of DECwindows files and asks if you want to I                  include them on the system disk. If you choose to tailor F                  files off, DECW$TAILOR lists each class of DECwindowsC                  files and asks if you want to delete them from the                   system disk.h  D               o  DECW$TAILOR adds or deletes the files you indicatedI                  from the system disk. If you are tailoring files on, youdH                  must load your DECwindows distribution media in a driveF                  available to the system. For example, if your OpenVMSI                  VAX Version 6.2 DECwindows distribution kit is on a TK50nF                  tape cartridge, load the second tape cartridge into a<                  TK50 drive that is available to the system.    I                                     Using VMSTAILOR and DECW$TAILOR 10-11  t  n           Using DECW$TAILOR       #     DECWINDOWS FILES YOU CAN TAILORo>           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 D.  A           o  DECwindows base support files-If you plan to installeB              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 youC              intend to install the DECwindows Motif for OpenVMS VAXtE              layered product, you need the workstation support files. -              Otherwise, you do not need them.   D              Note: If you tailor device support files ON or OFF, the              system reboots.  <           o  100 dots/inch video font files-By default, someB              workstation monitors (for example, a VR150, VR160, orA              VR295) display 100 dots/inch, which gives you a moreJC              readable display when you run DECwindows applications. E              If your workstation monitor cannot display 100 dots/inch E              fonts (for example, a VR260 or VR290), you can save disk E              space by not selecting this option. For more informationZC              about the capabilities of your particular monitor, seea0              the owner's guide for your monitor.  >           o  75 dots/inch video font files-If your workstationC              monitor cannot display 75 dots/inch, you can save disk E              space by not selecting this option. For more information C              about the capabilities of your particular monitor, seer0              the owner's guide for your monitor.       REMOVING DECWINDOWS FILES A           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   )     10-12 Using VMSTAILOR and DECW$TAILOR            I                                                         Using DECW$TAILORU      G                  DECW$TAILOR displays information about the DECW$TAILOR <                  program and displays the following message:  ;                  Do you want to tailor files "ON" or "OFF"?   E               3. Type OFF to remove unwanted files, and press Return.   D                  The DECW$TAILOR program lists each group, or class,C                  of files and its size in blocks. Files are groupedaH                  according to their function. For example, all the filesI                  required for DECwindows device support are in one class. F                  A file class is made up of many small subclasses. YouC                  can eliminate an entire class of files, or you canOF                  eliminate one or more of its subclasses. For example:  6           CLASS - DECwindows workstation support filesA                     Size of entire class (with subclasses): 14301aH                     Size of common files required for any subclass: 8937J                     Do you wish to select the entire class (default = NO)?                     .                      .                      .a  I               4. Decide which file classes or subclasses you need to add.eG                  DECW$TAILOR displays step-by-step instructions. FollowAF                  these instructions to specify which of the classes or/                  subclasses you want to remove.a  H               5. DECW$TAILOR deletes the files you selected and displaysH                  the names of those files. If you deleted device supportH                  files, the system automatically shuts down and reboots.  A               Caution: To cancel DECW$TAILOR during the first and G               second phases, press Ctrl/C, Ctrl/Y, or Ctrl/Z. CancelingVF               DECW$TAILOR during the third phase can cause a partiallyI               tailored disk. For a description of each phase, see the Hows(               DECW$TAILOR Works section.           ADDING DECWINDOWS FILES G               To install DECwindows device support and font files after H               the OpenVMS VAX installation or to add optional DECwindowsH               files that you previously chose not to install or that you(               removed, do the following:  .               1. Log in to the SYSTEM account.  I                                     Using VMSTAILOR and DECW$TAILOR 10-13y e  n           Using DECW$TAILORr      @           2. Load the OpenVMS VAX Version 6.2 distribution mediaE              containing the DECwindows save sets in a drive availabledD              to your system. For example, if your distribution mediaE              is a TK50 tape cartridge, load the second tape cartridgeoD              into a TK50 drive that is available to the system. Make0              sure the drive is online and ready.  >              If you are adding files from a compact disc on anE              InfoServer, first determine whether the SYSGEN parameter ?              SCSNODE is defined on your system (see the sectioniB              Preparing Your System Disk in Chapter 5) or start theC              DECnet software, and then refer to Step 2 of Beginning 0              the Upgrade Procedure in Chapter 7.  ;           3. Enter the following command, and press Return:   )              $ RUN SYS$UPDATE:DECW$TAILORt  C              DECW$TAILOR displays information about the DECW$TAILOR 9              program, and displays the following message:   7              Do you want to tailor files "ON" or "OFF"?n  4           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 D              according to their function. For example, all the filesE              required for DECwindows device support are in one class.iB              A file class is made up of many small subclasses. YouD              can add an entire class of files, or you can add one or1              more of its subclasses. For example:   9              CLASS - DECwindows workstation support files D                        Size of entire class (with subclasses): 14301M                        Size of common files required for any subclasses: 8937 M                        Do you wish to select the entire class (default = NO)?                  .I                 .                  .o  D           5. Decide which file classes or subclasses you do not needE              to support your system. The DECW$TAILOR program displaysAD              step-by-step instructions. Follow these instructions toC              specify which of the classes or subclasses you want toE              add.s  )     10-14 Using VMSTAILOR and DECW$TAILORe S  L      I                                                         Using DECW$TAILORc      I               6. DECW$TAILOR installs the files you selected and displayslF                  the names of those files. If you added device supportH                  files, the system automatically shuts down and reboots.  A               Caution: To cancel DECW$TAILOR during the first and G               second phases, press Ctrl/C, Ctrl/Y, or Ctrl/Z. Canceling F               DECW$TAILOR during the third phase can cause a partiallyI               tailored disk. For a description of each phase, see the Howu(               DECW$TAILOR Works section.  F               After adding files to the system disk, apply any updatesC               that affect them. For example, suppose you delete theDD               Version 6.2 DECwindows 100 dots/inch video font files.D               Later on, you are able to use the 100 dots/inch fonts,F               so you run DECW$TAILOR to return the files to the systemG               disk. You must then apply any OpenVMS VAX update that hascH               occurred since Version 6.2 that affected the 100 dots/inchF               video font files. OpenVMS VAX update procedures create aF               .TXT file that contains a description of modified files.C               This file is usually named with the following format::)               SYS$UPDATE:VMSUn05n.TXT[1].e           SAMPLE SESSION?               Example 10-2 illustrates how to add the files fori2               DECwindows 100 dots/inch font files.  /         Example 10-2 Sample DECW$TAILOR Session   $         $ RUN SYS$UPDATE:DECW$TAILOR            .            .            .  6          Do you want to tailor files "ON" or "OFF"? ON  I                                                  (continued on next page)o          "               ____________________F               [1]         Examine this file to determine if the update  >                           patched the 100 dots/inch font files  I                                     Using VMSTAILOR and DECW$TAILOR 10-15                 Using DECW$TAILOR       3     Example 10-2 (Cont.) Sample DECW$TAILOR Session   
  TAILOR-ON
  ---------D   You will now be prompted with a list of the classes and subclassesO   of DECwindows files that are optional. The size of each class and subclass is P   included in the list. This will help you decide whether or not you want to add%   a class or subclass to your system.u  N   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 ask7   for either the entire class or any of its subclasses.y  2   Total size of the system disk is 2376153 blocks.8   Total space used on the system disk is 1728072 blocks.7   Total space left on the system disk is 648081 blocks.   &  CLASS - DECwindows base support files7            Size of entire class (with subclasses): 3363   .            No subclasses in this tailor class.A            Do you wish to select the entire class (default = NO)?m  -  CLASS - DECwindows workstation support files 8            Size of entire class (with subclasses): 12376?            Size of common files required for any subclass: 8916 D            Do you wish to select the entire class (default = NO)? NOF            Do you wish to select any of its subclasses (default = NO)?  *  CLASS - 75 dots per inch video font files7            Size of entire class (with subclasses): 4537e  .            No subclasses in this tailor class.A            Do you wish to select the entire class (default = NO)?e  +  CLASS - 100 dots per inch video font filesl6           Size of entire class (with subclasses): 3693-           No subclasses in this tailor class.wD           Do you wish to select the entire class (default = NO)? YES  E                                              (continued on next page)f        )     10-16 Using VMSTAILOR and DECW$TAILOR            I                                                         Using DECW$TAILOR       7         Example 10-2 (Cont.) Sample DECW$TAILOR Session             Files have been selected;         Do you wish to add all of the options selected? YESP7         Creating temporary command file, please wait...sF         * Enter device containing DECwindows distribution media: MUA0:            .            .            .                                                                        I                                     Using VMSTAILOR and DECW$TAILOR 10-17y w                       I                                                                         A I         _________________________________________________________________Y  I                                                  License Management Notes   I         _________________________________________________________________s           Overview  D               This appendix contains supplemental information to theH               license instructions given in the installation and upgradeF               procedures and in the OpenVMS License Management UtilityG               Manual. Although most of the information in this appendix5H               pertains to managing OpenVMS and System Integrated ProductA               (SIP) licenses, some of the information pertains to[0               managing layered product licenses.  =               This appendix covers the following information:e  *               o  Registering your licenses  @               o  Using the License Unit Requirement Table (LURT)  8               o  License Management Facility (LMF) notes  5               o  Volume Shadowing for OpenVMS licensef  ?               o  Other System Integrated Product (SIP) licensesl                            I                                              License Management Notes A-1- c              Registering Your Licensesf    E     _________________________________________________________________r       Registering Your Licenses   :           This section provides an overview of the license!           registration procedure.o       WHEN TO REGISTERA           After you install the OpenVMS VAX operating system, you >           must register an OpenVMS VAX license. An OpenVMS VAXB           license lets you use the operating system. You must alsoA           register the licenses for any of the following SIPs you0           have purchased:              o  VAXclusters             o  DECnet for OpenVMSd  #           o  OpenVMS RMS Journaling   )           o  Volume Shadowing for OpenVMS.  @           After you upgrade the OpenVMS VAX operating system, inD           most cases there is no need to reregister licenses for the'           operating system or for SIPs.1  A           In addition to the OpenVMS VAX operating system and the @           SIPs, many layered products-including DECwindows MotifB           for OpenVMS VAX-that run on OpenVMS VAX Version 6.2 also?           require license registration. See the OpenVMS LicenseOE           Management Utility Manual for a full explanation of license            registration.X       HOW TO REGISTER =           To register a license, you need to obtain a ProductoD           Authorization Key (PAK). A typical PAK is a piece of paperA           provided by Digital Equipment Corporation that containsoE           the appropriate information to authorize access to softwaresC           on a VAX computer or in a VAXcluster environment. You cansD           obtain a PAK from a Digital representative the same way as           you obtain software.  B           See Table A-1 for a complete list of the versions of theA           OpenVMS VAX operating system and the VAX computers thatr1           were first supported by these versions.2        A-2 License Management Notes           I                                                 Registering Your Licensess      F               Table A-1 The First VMS or OpenVMS Version That Supports%                         VAX Computers I               ___________________________________________________________ 4               VMS Version     First Computer SupportI               ___________________________________________________________d?               Version 5.0     VAX 6000 Model 2xx, VAX 8820-8840   0               Version 5.0-2A  MicroVAX 3300/3400  D               Version 5.1     VAX 6000 Model 3xx, MicroVAX 3800/3900  :               Version 5.1-B   VAXstation 3100, Model 30/40  2               Version 5.1-1   VAXstation 3520/3540  ?               Version 5.2     VAX 6000 Model 4xx, MicroVAX 3100   :               Version 5.2-1   VAXstation 3100, Model 38/48  0               Version 5.3     No CPUs introduced  I                                                  (continued on next page)                                               I                                              License Management Notes A-3d e              Registering Your Licensesm      A           Table A-1 (Cont.) The First VMS or OpenVMS Version Thatw2                             Supports VAX ComputersE           ___________________________________________________________T0           VMS Version     First Computer SupportE           ___________________________________________________________ ,           Version 5.3-1   No CPUs introduced  ,           Version 5.3-2   VAX 4000 Model 300  =           Version 5.4     VAXstation 3100 Model 76, VAX 9000,E7                           VAX 6000 Model 5xx, VAXft 310   ,           Version 5.4-1   No CPUs introduced  ,           Version 5.4-2   VAX 4000 Model 200  4           Version 5.4-3   VAXft Models 410, 610, 612  C           Version 5.5     VAXstation 4000 VLC, MicroVAX 3100 ModelsXA                           30, 40, and 80, VAX 6000 Model 600, VAX.C                           4000 Model 500, VAXstation 4000 Model 60, -                           and VAXft Model 110k  D           Version 5.5-2   VAX 4000 Model 100, VAXstation 4000 ModelsA                           90 and 100, MicroVAX 3100 Model 90, VAX A                           4000 Model 400, VAX 4000 Model 600, VAXtA                           7000 Model 600, and VAX 10000 Model 600   D           Version 5.5-    VAX 4000 Models 100A, 500A, 600A, and 700A
           2H4t  )           Version 5.5-    VAXft Model 810i
           2HF   J           ________________________________________________________________           OpenVMSp0           Version         First Computer SupportJ           ________________________________________________________________6           Version 6.0     VAX 7000 Models 650 and 660,6                           VAX 10000 Models 600 and 650  ,           Version 6.1     VAX 7000 Model 7xx  G           Version 6.2     VAX 4000 Model 106A, MicroVAX 3500 Model 95A,tJ                           MicroVAX 3100 Model 96, VAXstation 4000 Model 96J           ________________________________________________________________      A-4 License Management Notes    d      I                           Using the License Unit Requirement Table (LURT)r    I         _________________________________________________________________t  7         Using the License Unit Requirement Table (LURT)              INTRODUCTIONC               Many PAKs contain a table name in the availability or B               activity fields. This name refers to a column in the4               License Unit Requirement Table (LURT).  E               For more information on using the LURT, see the OpenVMSs0               License Management Utility Manual.  &         LICENSE UNIT REQUIREMENT TABLEE               Table A-2 has seven lettered columns (A, B, C, D, E, F,yF               and I; G and H are reserved by Digital and therefore areG               not listed). The numbers listed in these columns indicatesE               the number of license units required for each processor G               listed in the System Marketing Model column. For example, G               if your PAK specifies availability = F, you would require C               100 license units to load the license on a VAX 11/780lF               computer, or 4800 license units to load the license on a$               VAX 9000-430 computer.  I               Note that some PAKs specify MOD_UNITS in the options field.eG               The MOD_UNITS option allows the system manager to use theeF               DCL command LICENSE MODIFY/UNITS to temporarily increaseE               the size of the PAK. This permits a product to be used,sD               in certain emergency situations, on a processor largerE               than the processor size specified in the license. CheckcH               your license terms and conditions before modifying licenseF               units. Reset the PAK size to its original size after the.               emergency situation is resolved.                          I                                              License Management Notes A-5  s  i      3     Using the License Unit Requirement Table (LURT)       3     Table A-2 License Unit Requirement Table (LURT)eE     _________________________________________________________________i7                                   License Types by Codes@                           ____________________________________  A                                   OpenVMS          SIP         LP E                           _____________________   ______  ___________      System MarketingD     Model                  A    B     C     D       E       F      IE     _________________________________________________________________ E     VAX 11/730             10   NA    NA    NA     230      50     50s  E     VAX 11/750             12   NA    NA    NA     230     100    100p  E     VAX 11/780, 785        13   NA    NA    NA     230     100    100   E     VAX 6000-210, 6000-    58   NA    NA    NA     230     300    300e     310   E     VAXft 110              60   NA    NA    NA     230     100    100   E     VAXft 310, 410,        58   NA    NA    NA     230     300    300      610, 810  E     VAX 6000-220, 6000-    69   NA    NA    NA     230     600    600i     320, 6000-410   E     VAX 6000-230, 6000-    81   NA    NA    NA     400     900    900      330, 6000-510.  E     VAX 6000-240, 6000-    93   NA    NA    NA     400    1200   1200t     340, 6000-350,     6000-420, 7000-610, 
     10000-610KE     _________________________________________________________________r(     Key to License Type Codes and Values  5       A-OpenVMS Capacity or OpenVMS Unlimited or Base        B-OpenVMS Server       C-OpenVMS Concurrent usere       D-OpenVMS Workstations"       E-System integrated products       F-Layered products       G-Reserved (not listed)5%       H-OpenVMS reserved (not listed)t       I-Layered products       NA-Not applicable   E                                              (continued on next page)o        A-6 License Management Notes           I                           Using the License Unit Requirement Table (LURT)o      >         Table A-2 (Cont) License Unit Requirement Table (LURT)I         _________________________________________________________________ ;                                       License Types by Code D                               ____________________________________  E                                       OpenVMS          SIP         LPaI                               _____________________   ______  ___________e         System MarketingH         Model                  A    B     C     D       E       F      II         _________________________________________________________________a  I         VAX 6000-540, 6000-   170   NA    NA    NA     600    2400   2400          640C  I         VAX 6000-550, 6000-   195   NA    NA    NA     600    2400   2400s         650a  I         VAX 6000-560, 6000-   220   NA    NA    NA     600    2400   2400b         660   I         VAX 6000-610           81   NA    NA    NA     400    1200   1200)  I         VAX 8200, 8250         20   NA    NA    NA     230     100    100.  I         VAX 8300, 8350         25   NA    NA    NA     230     200    200p  I         VAX 8500               63   NA    NA    NA     230     400    400   I         VAX 8530               65   NA    NA    NA     230     400    400   I         VAX 8550, 8700,        72   NA    NA    NA     400     600    600T         8810  I         VAX 8600, 8650         28   NA    NA    NA     230     400    400   I         VAX 8800, 8820         93   NA    NA    NA     400    1200   1200o  I         _________________________________________________________________d,         Key to License Type Codes and Values  8          A-OpenVMS Capacity or OpenVMS Unlimited or Base          B-OpenVMS Server$"          C-OpenVMS Concurrent user          D-OpenVMS Workstations/%          E-System integrated products           F-Layered productse           G-Reserved (not listed)(          H-OpenVMS reserved (not listed)          I-Layered products           NA-Not applicable  I                                                  (continued on next page)p  I                                              License Management Notes A-7t h         3     Using the License Unit Requirement Table (LURT)n      :     Table A-2 (Cont) License Unit Requirement Table (LURT)E     _________________________________________________________________t7                                   License Types by Code @                           ____________________________________  A                                   OpenVMS          SIP         LPsE                           _____________________   ______  ___________c     System MarketingD     Model                  A    B     C     D       E       F      IE     _________________________________________________________________   E     VAX 8830, 6000-360,   119   NA    NA    NA     600    1800   1800i     6000-430, 6000-520,E     6000-620  E     VAX 7000-620,         145   NA    NA    NA     600    1800   1800 
     10000-620   E     VAX 6000-440, 6000-   143   NA    NA    NA     600    2400   2400      450, 6000-460,     6000-530  E     VAX 7000-630,         167   NA    NA    NA     600    2400   2400n     10000-630,  E     VAX 7000-640,         197   NA    NA    NA     600    2400   2400      10000-640,  E     VAX 6000-630, 9000-   143   NA    NA    NA     600    2400   24000     210, 9000-410l  E     VAX 9000-420          241   NA    NA    NA     800    4800   4800   E     VAX 9000-430          330   NA    NA    NA     800    4800   4800t  E     _________________________________________________________________b(     Key to License Type Codes and Values  5       A-OpenVMS Capacity or OpenVMS Unlimited or Bases       B-OpenVMS Server       C-OpenVMS Concurrent usert       D-OpenVMS Workstations"       E-System integrated products       F-Layered products       G-Reserved (not listed) %       H-OpenVMS reserved (not listed)r       I-Layered products       NA-Not applicables  E                                              (continued on next page)t        A-8 License Management Notes y  m      I                           Using the License Unit Requirement Table (LURT).      >         Table A-2 (Cont) License Unit Requirement Table (LURT)I         _________________________________________________________________a;                                       License Types by Code.D                               ____________________________________  E                                       OpenVMS          SIP         LPtI                               _____________________   ______  ___________d         System MarketingH         Model                  A    B     C     D       E       F      II         _________________________________________________________________S  I         VAX 9000-440          386   NA    NA    NA     800    4800   4800u  I         VAX 7000-710           93   NA    NA    NA     230     600    600   I         VAX 7000-720          193   NA    NA    NA     230     600    600   I         VAX 7000-730          293   NA    NA    NA     230     600    600   I         VAX 7000-740          393   NA    NA    NA     230     600    600o  I         VAX 7000-750          493   NA    NA    NA     230     600    600   I         VAX 7000-760          593   NA    NA    NA     230     600    600n  I         MicroVAX II            18   NA    100   NA     230      50     50   I         MicroVAX 2000,         18   NA    100   NA     230      20     20I         3100-10e, 3100-20e,          3100-30, 3100-40,          3100-80,  I         MicroVAX 3100-90,      60   NA    100   NA     230      20     20p         3100-96A  I         _________________________________________________________________ ,         Key to License Type Codes and Values  8          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  I                                                  (continued on next page)_  I                                              License Management Notes A-9n    t      3     Using the License Unit Requirement Table (LURT)       :     Table A-2 (Cont) License Unit Requirement Table (LURT)E     _________________________________________________________________ 7                                   License Types by Code5@                           ____________________________________  A                                   OpenVMS          SIP         LPtD                           _____________________   ______  __________     System MarketingD     Model                  A    B     C     D       E       F      IE     _________________________________________________________________L  E     MicroVAX 3500,         60   NA    100   NA     230     200    200      3600, 3800, 3900,w     4000-200  E     MicroVAX 3300,         60   NA    100   NA     230     100    100n     3400, 4000-100, 
     4000-106A   E     VAX 4000-300, 4000-    60   NA    100   NA     230     300    300c     400, 4000-500A,t     4000-600A, 4000-     700A, 4000-706A_  E     VAX 4000-500, 4000-    60   NA    100   NA     400     900    900o     600e  E     VAXstation II, II     NA    NA    NA    100     50      10     10      /GPX  E     VAXstation 2000,      NA    NA    NA    100     50      10     10      2000/GPXE     _________________________________________________________________n(     Key to License Type Codes and Values  5       A-OpenVMS Capacity or OpenVMS Unlimited or Baser       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)n       I-Layered products       NA-Not applicable   E                                              (continued on next page)   !     A-10 License Management Notes  t  o      I                           Using the License Unit Requirement Table (LURT)       >         Table A-2 (Cont) License Unit Requirement Table (LURT)I         _________________________________________________________________ ;                                       License Types by Code D                               ____________________________________  E                                       OpenVMS          SIP         LPiI                               _____________________   ______  ___________t         System MarketingH         Model                  A    B     C     D       E       F      II         _________________________________________________________________   I         VAXstation 3100,      NA    NA    NA    100     50      10     10b         3200, 3500, 3520,e         3540, 4000-60,         4000 VLC, 4000-90,         4000-96   I         VAXserver 2000        NA      52  NA    NA      50      10     10M  I         VAXserver 3300,        NA    100  NA    NA      50      10     10o         3400, 3500, 3600,          3900, 4000-200,t         4000-300  I         VAXserver 6000-210,   NA    1443  NA    NA     230     200    200s         6000-310  I         VAXserver 6000-220,   NA    1737  NA    NA     230     400    400          6000-320, 6000-410,          6000-420  I         VAXserver 6000-510    NA     600  NA    NA     230     400    400   I         VAXserver 6000-520    NA     890  NA    NA     230     400    400_I         _________________________________________________________________ ,         Key to License Type Codes and Values  8          A-OpenVMS Capacity or OpenVMS Unlimited or Base          B-OpenVMS Server/"          C-OpenVMS Concurrent user          D-OpenVMS Workstations %          E-System integrated productsn          F-Layered productse           G-Reserved (not listed)(          H-OpenVMS reserved (not listed)          I-Layered products3          NA-Not applicable  I                                                  (continued on next page)   I                                             License Management Notes A-11            3     Using the License Unit Requirement Table (LURT)       :     Table A-2 (Cont) License Unit Requirement Table (LURT)E     _________________________________________________________________ 6                                  License Types by Code@                           ____________________________________  @                                  OpenVMS          SIP         LPE                           _____________________   ______  ___________      System MarketingD     Model                  A    B     C     D       E       F      IE     _________________________________________________________________   E     VAXserver 9000-110,   143   143   NA    NA     600     900    900d     9000-310  E     VAXserver 9000-320    241   241   NA    NA     800    1200   1200e  E     VAXserver 9000-330    330   330   NA    NA     800    1200   1200A  E     VAXserver 9000-340    386   386   NA    NA     800    1200   12006E     _________________________________________________________________e(     Key to License Type Codes and Values  5       A-OpenVMS Capacity or OpenVMS Unlimited or Base1       B-OpenVMS Server       C-OpenVMS Concurrent usera       D-OpenVMS Workstations"       E-System integrated products       F-Layered products       G-Reserved (not listed) %       H-OpenVMS reserved (not listed)o       I-Layered products       NA Not applicablelH     ____________________________________________________________________                              !     A-12 License Management Notes_ _  _      I                                         License Management Facility Notes     I         __________________________________________________________________  )         License Management Facility Notes     /         COMMON CONCERNS AND QUESTIONS ABOUT LMF B               The following list is offered to help new users withF               some common concerns and questions regarding the License(               Management Facility (LMF).  G               o  If you do not have a valid OpenVMS VAX license that is_H                  registered and activated, the system displays a warningG                  message as part of system startup and restricts systemt5                  use to the operator's console, OPA0._  E               o  If a checksum error is displayed when you register aiH                  license, check all the fields of data that you entered,/                  including the checksum itself.i  C               o  After your PAKs are registered, they are activatednG                  (loaded) automatically as part of each system startup.   E               o  If an OpenVMS VAX availability license is registered B                  with insufficient license units for the specifiedD                  VAX computer, the system displays a warning messageF                  at system startup but allows normal system use at the$                  console level only.  A               o  If an OpenVMS VAX activity license is registeredbB                  with insufficient license units to meet your userH                  requirements, the system displays the following message<                  when the user (process) attempts to log in:  M     %LICENSE-F-EXCEEDED, licensed product has exceeded current license limitsp  D                  A user can always log in to the operator's console,                  OPA0, however.   D               o  The default LICENSE database is located in the fileE                  SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB. You can move the D                  database, although Digital does not recommend doingE                  so. If you move the database, you must either define D                  the logical name LMF$LICENSE at the system level toH                  point to the new database or use the /DATABASE=filespecA                  qualifier with all LICENSE commands. To redirect E                  LMF to another database location on a more permanent G                  basis, add the following line to the command procedure ,                  SYS$MANAGER:SYLOGICALS.COM:  I                                             License Management Notes A-13e t  b      %     License Management Facility NotesR      J              $ 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.                                                                                !     A-14 License Management NotesM e  g      I                                         License Management Facility Notes_      C               o  Each OpenVMS VAX license is restricted to a single0B                  node for permanent PAKs. You must assign a SystemG                  Communications Services (SCS) name to the license when H                  you register with the VMSLICENSE.COM command procedure,E                  or you must enter a LICENSE MODIFY/INCLUDE=node-name I                  command after you register the license. Although you can H                  successfully activate an unassigned OpenVMS VAX licenseE                  on a standalone system, you cannot activate one in a (                  VAXcluster environment.  F                  Note: The SCS node name is not necessarily the DECnetF                  node name. SCSNODE is a system parameter; it can be a4                  maximum of 6 alphabetic characters.                                                                I                                             License Management Notes A-15     -      (     Volume Shadowing for OpenVMS License    E     _________________________________________________________________o  (     Volume Shadowing for OpenVMS License         WHEN TO REGISTER=           After you install OpenVMS VAX Version 6.2, you mustoC           register your Volume Shadowing for OpenVMS license before B           you can use Volume Shadowing. If you upgraded to OpenVMS=           VAX Version 6.2, you do not need to reregister this            license.    )     VOLUME SHADOWING PHASE I AND PHASE II =           In the past, volume shadowing has offered two modes :           of operation: Phase I and Phase II. The originalB           implementation of shadowing, Phase I, was HSC controllerB           based. The newer implementation, Phase II, is host based7           and provides performance superior to Phase I.   E           With the release of OpenVMS VAX Version 6.2, Phase I Volume_?           Shadowing is no longer available. Refer to the VolumeeD           Shadowing for OpenVMS manual for instructions about moving#           from Phase I to Phase II._       TYPES OF LICENSES_>           Two types of Volume Shadowing licenses are valid for"           OpenVMS VAX Version 6.2:  D           o  Capacity license-If you are using this type of license,A              you must have one license for each node in a clusterA-              that is accessing shadowed data.   D           o  Per-disk license-If you are using this type of license,E              you must have on license for every disk contained in the0              shadow set.  B              For information about OpenVMS VAX Version 6.2 changesE              to per-disk licensing for Volume Shadowing, refer to the +              section Cautions in Chapter 1.   >           See the Volume Shadowing for OpenVMS manual for more/           information about these two licenses.       !     A-16 License Management Notes  A         I                                  Other System Integrated Product Licenses     I         __________________________________________________________________  0         Other System Integrated Product Licenses  A               After you install OpenVMS VAX Version 6.2, you must E               register licenses for any system integrated product. If I               you upgraded to OpenVMS VAX Version 6.2, you do not need to A               reregister licenses for system integrated products.                                                                             I                                             License Management Notes A-17e n  x                    I                                                                         B I         _________________________________________________________________   I                                     Booting from [SYSF] During an Upgrade_  I         _________________________________________________________________            Booting Procedures             INTRODUCTIOND               You must boot from the [SYSF] root during phases 2, 3,E               and 4 of the upgrade procedure. Different VAX computers_E               require that you use different booting procedures. This F               appendix describes how to boot the various VAX computers               from [SYSF].  D               Go to the section that describes your VAX computer andE               follow the instructions for booting from [SYSF]. If you G               need more information about booting, refer to the upgrade0@               and installation supplement for your VAX computer.  )         MICROVAX AND VAXSTATION COMPUTERS0F               The information in this section applies to the following               VAX computers:  B                  VAXstation II, VAXstation II/GPX, and MicroVAX II2                  VAXstation 2000 and MicroVAX 20009                  VAXstation 3100 and MicroVAX 3100 series )                  VAXstation 3200 and 3500A)                  VAXstation 3520 and 35400                   VAXstation 40002                  VAXft 110, 310, 410, 610, and 612@                  MicroVAX 3300, 3400, 3500, 3600, 3800, and 3900  @               To boot from [SYSF], enter the BOOT command in the8               following format and press the Return key:  (               >>> B/F0000000 device-name  G               Substitute the device name of the system disk for device-(               name.-  I                                 Booting from [SYSF] During an Upgrade B-1a s              Booting Procedures      8     VAX 8530, 8550, 8810 (8700), 8820-N (8800) COMPUTERS;           To boot from [SYSF], use the following procedure:h  =           1. Press Ctrl/P. Enter the following command at the @              console-mode prompt (>>>) and press the Return key:                >>> HALT_  D           2. Enter the BOOT command at the console-mode prompt (>>>)%              in the following format:   $              >>> B dddn /R5:F0000000  E              Substitute BCI, BDA, or UDA for ddd. Substitute the unit ?              number of the drive holding the system disk for n._  &     VAX 8820, 8830, AND 8840 COMPUTERS;           To boot from [SYSF], use the following procedure:   C           1. Enter the following command at the PS-OS-0> prompt and_              press Return:  "              PS-OS-0> HALT/CPU=ALL  B           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.0  
     VAX-11.     /750, 8200, 8250, 8300, AND 8350 COMPUTERS?           To boot from [SYSF], create a command procedure named03           SYFBOO.CMD before the upgrade is started.   <           To create SYFBOO.CMD, use the following procedure:  B           Note: This procedure assumes that you have installed andE           booted the OpenVMS VAX operating system and are logged intoe           the SYSTEM account.3  *           1. Log in to the SYSTEM account.  ?           2. Make sure that the console media is in the console               drive._  -     B-2 Booting from [SYSF] During an Upgrade_ _  _      I                                                        Booting Procedurest      F               3. To connect the console drive to the system, enter theG                  following commands and press the Return key after eache                  one:   (                  $ RUN SYS$SYSTEM:SYSGEN(                  SYSGEN> CONNECT CONSOLE                  SYSGEN> EXITd  F               4. Use the Exchange utility to copy the appropriate bootI                  command procedure from the console media to your current G                  directory on the system disk. If the system disk is on H                  an HSC drive and you have created DEFBOO.CMD, enter the4                  following command and press Return:  2                  $ EXCHANGE COPY CSA1:DEFBOO.CMD *  E                  On the VAX 11/750 computer, if the system disk is on D                  a local drive, copy the boot command procedure thatB                  matches the drive that holds the system disk. ForE                  example, suppose the system disk is on an RP06 drive H                  and has a controller designation of A and a unit numberI                  of one. Enter the following command and press the ReturnV                  key:A  2                  $ EXCHANGE COPY CSA1:DA1BOO.CMD *  A               5. Edit the boot command procedure. Change the lineAD                  that deposits a value in register 5 (R5). This lineH                  contains the comment !software boot flags. The value isE                  a hexadecimal number with eight digits. For example:0  1                  D/G R5 0    !software boot flags   G                  Change the left-most digit of the value to reflect the H                  name of the root directory from which you want to boot.E                  For example, to boot from the [SYSF] root directory,_,                  change the line as follows:  ?                  D/G/L R5 F0000000     !designated root is SYSFp  E               6. Rename the boot command procedure to SYFBOO.CMD. ForeF                  example, if the boot command procedure is DEFBOO.CMD,F                  enter the following command and press the Return key:  /                  $ RENAME DEFBOO.CMD SYFBOO.CMDc  I                                 Booting from [SYSF] During an Upgrade B-3( t  e           Booting Procedures      D           7. Use the Exchange utility to copy SYFBOO.CMD back to theA              console media. Enter the following command and pressn              Return:  7              $ EXCHANGE COPY SYFBOO.CMD CSA1:SYFBOO.CMD_  C           8. When the copy operation completes, enter the following &              command and press Return:                $ DISMOUNT CSA1  B           9. To secure the console media from unauthorized access,C              you must enter the following command and press Return:_  9              $ MOUNT/FOREIGN/SYSTEM/NOWRITE/NOASSIST CSA1   ;           To boot from [SYSF], use the following procedure:   D           1. Make sure the console media is in the console drive. OnC              the VAX 11/750 computers, make sure the keylock switch0D              is set to LOCAL. Set the BOOT DEVICE switch to position              A.   C              On the VAX 8200 computer, set the upper keylock switch <              to ENABLE and the lower keylock switch to HALT.             2. Press Ctrl/P.  D           3. On the VAX 11/750 computer, enter the following command&              and press the Return key:                >>> B/800 DDA0A  E              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  
     VAX-112     /730, 11/780, 11/785, 8600, AND 8650 COMPUTERS?           To boot from [SYSF], create a command procedure named C           SYFBOO.CMD (for VAX-11/730, 11/780, and 11/785 computers)tD           or SYFBOO.COM (for VAX 8600 and 8650 computers) before the           upgrade is started.   ?           To create SYFBOO.CMD or SYFBOO.COM, use the following            procedure:  -     B-4 Booting from [SYSF] During an Upgrade  O  V      I                                                        Booting Procedurese      F               Note: This procedure assumes that you have installed andI               booted the OpenVMS VAX operating system and are logged into1!               the SYSTEM account.e  .               1. Log in to the SYSTEM account.  C               2. Make sure that the console media is in the console_H                  drive. On the VAX 8600 computer, make sure the TERMINAL0                  CONTROL switch is set to LOCAL.  B               3. To connect the console drive, enter the followingB                  commands and press the Return key after each one:  (                  $ RUN SYS$SYSTEM:SYSGEN(                  SYSGEN> CONNECT CONSOLE                  SYSGEN> EXIT   A               4. Use the Exchange utility to copy DEFBOO.CMD (for_H                  VAX 11/730, 11/780, and 11/785 computers) or DEFBOO.COMI                  (for VAX 8600 and 8650 computers) from the console media4E                  to your current directory on the system disk. On the H                  VAX 11/780, 11/785, and 8600 computers, enter a command;                  similar to the following and press Return:_  2                  $ EXCHANGE COPY CSA1:DEFBOO.CMD *  H                  On the VAX 11/730 computer, enter the following command*                  and press the Return key:  2                  $ EXCHANGE COPY CSA2:DEFBOO.CMD *  D               5. Edit DEFBOO.CMD or DEFBOO.COM. Change the line thatH                  deposits a value in register 5 (R5). On the VAX-11/730,E                  11/780, and 11/785 computers, this line contains the_I                  comment !software boot flags. On the VAX 8600, this line G                  contains the comment !Use R5 for optional boot control F                  flags [SYSB.]. The value is a hexadecimal number with)                  eight bits. For example:_  =                  DEPOSIT R5 10000000     !software boot flags   G                  Change the left-most digit of the value to reflect theoH                  name of the root directory from which you want to boot.E                  For example, to boot from [SYSF], change the line asF                  follows:   =                  DEPOSIT R5 F0000000     !software boot flags   I                                 Booting from [SYSF] During an Upgrade B-5                 Booting Procedures      >           6. Rename DEFBOO.CMD to SYFBOO.CMD (or DEFBOO.COM to%              SYFBOO.COM), as follows:   +              $ RENAME DEFBOO.CMD SYFBOO.CMDi  ;           7. Use the Exchange utility to copy SYFBOO.CMD oro@              SYFBOO.COM to the console media. On the VAX 11/780,B              11/785, and 8600 computers enter a command similar to              the following:o  7              $ EXCHANGE COPY SYFBOO.CMD CSA1:SYFBOO.CMD   C              On the VAX 11/730 computer enter the following command &              and press the Return key:  7              $ EXCHANGE COPY SYFBOO.CMD CSA2:SYFBOO.CMDp  B           8. When you are finished, enter a command similar to the(              following and press Return:                $ DISMOUNT CSA1  B           9. To secure the console media from unauthorized access,B              you must enter a command similar to the following and              press Return:  9              $ MOUNT/FOREIGN/SYSTEM/NOWRITE/NOASSIST CSA1   B           To boot from [SYSF] during an upgrade, use the following           procedure:  D           1. Make sure the console media is in the console drive. OnD              the VAX 11/730, 11/780, and 11/785 computers, make sureA              the keylock switch is set to LOCAL. On the VAX 8600, C              make sure the TERMINAL CONTROL switch is set to LOCAL.   >           2. Press Ctrl/P. On the VAX 11/780, 11/785, and 8600B              computers, enter the HALT command at the console-mode3              prompt (>>>) and press the Return key:t                >>> HALT   D           3. Use SYFBOO.CMD to boot from [SYSF]. Enter the following&              command and press Return:                >>> B SYF  -     B-6 Booting from [SYSF] During an Upgraden m         I                                                        Booting Proceduresr               VAX 6000         SERIES?               To boot from [SYSF], use the following procedure:a  G               1. If you have a CIBCA-A adapter and are booting over the E                  CI, insert the console tape cartridge in the consoleC                  drive.I  @               2. Press Ctrl/P to put the system in console mode.  @               3. Enter the BOOT command in the following format:  N                  >>> BOOT /R5:F0000000  /XMI:a  /BI:b  [/R3:c]  [/NODE:d]  DUu                    where:-  @                  o  a is the XMI node number of the system disk.  B                  o  b is the VAXBI node number of the system disk.  E                  o  c pertains to Volume Shadowing. This qualifier is G                     not required unless you are using Volume Shadowing.uF                     For more information, see the Volume Shadowing for#                     OpenVMS manual.m  H                  o  d is the HSC node number of the node being accessed.C                     The /NODE qualifier is not necessary if you areAE                     booting from a local disk. The HSC node number isOH                     in hexadecimal. You can deposit a maximum of two HSC=                     node numbers (if two HSCs are available).   H                  o  u is the unit number of the drive holding the system                     disk.D                        I                                 Booting from [SYSF] During an Upgrade B-7                 Booting Procedures      D              For example, suppose you want to boot from [SYSF] on anC              HSC disk with a unit number of one and your system hasn)              the following configuration:_  =              o  The disk is connected to the VAXBI at node 2.e  B              o  The VAXBI you are using is connected to the XMI at                 node 3.u  B              o  The disk is available to two HSCs, node numbers 0E                 and 02.   B              Enter the following command and press the Return key:  :              >>> BOOT/R5:F0000000/XMI:3/BI:2/NODE:0E02 DU1       VAX 9000
     SERIESC           The upgrade procedure automatically updates DEFBOO.CMD toeC           boot from [SYSF]. If you want to boot a VAX 9000 computergB           manually from [SYSF] however, you must set up DEFBOO.CMD@           to boot from the system disk and perform the following           procedure:  7           1. Press Ctrl/P to obtain the console prompt.h  /           2. Enter the following BOOT commands:l                >>> I/K              >>> BOOT/NOSTART $              >>> DEPOSIT R5 F0000000              >>> CONTINUEc  D           3. If you set up DEFBOO.CMD properly, the system will bootD              from the SYSF directory on the system disk and continue(              with the upgrade procedure.  8              If the system does not boot, enter the SHOWE              CONFIGURATION console command and verify that DEFBOO.CMDlE              contains the correct information for your configuration.PB              For more information, see the OpenVMS VAX Upgrade and6              Installation Supplement: VAX 9000 Series.      -     B-8 Booting from [SYSF] During an Upgrader i  a                    I                                                                         CrI         _________________________________________________________________   I                                           OpenVMS VAX Save Set Subclasses   I         _________________________________________________________________            Overview  F               This appendix lists the file subclasses contained in the"               following save sets:  *               o  VMS062.C-Library save set  +               o  VMS062.D-Optional save set   /               o  VMS062.E-Help Message save set   2               o  VMS062.F-OpenVMS manuals save set  =               o  VMS062.G-OpenVMS Management Station save sets                                          I                                       OpenVMS VAX Save Set Subclasses C-1                 File Subclasses     E     _________________________________________________________________a       File Subclasses          SAVE SET C SUBCLASSES D           The following files are contained in the Library save set:             o  Network support  1                 Incoming Remote File Access files .                 Incoming Remote Terminal files"                 Network Test files#                 Remote Task Loading_              o  Programming Support  (                 Debugger utility (DEBUG)9                 Image Dump utility (ANALYZE/PROCESS_DUMP)sB                 RMS Analyze and FDL Editor utilities (ANALYZE/RMS,                 ANALYZE/FDL))                 Message utility (MESSAGE)e4                 Object and Shareable Image libraries                 MACRO libraries                  MACRO assembler 4                 SDL intermediary form of STARLET.MLB&                 Fortran required files&                 VAX C object libraries4                 X/Open transport interface libraries,                 OpenVMS RMS journaling files  '           o  System programming Support   :                 Files-11 ODS-1, ISO 9660, High Sierra ACPs                 Monitor utilityo%                 Delta/XDelta debuggertE                 System Dump Analyzer utility (ANALYZE/SYSTEM, ANALYZE                  /CRASH)t2                 System Symbol Table file (SYS.STB)0                 Miscellaneous symbol table files  &           o  Secure User's Environment  2                 File Access Control List utilities/                 Print and Batch Queue utilities02                 Input Queue Symbiont (Card Reader)7                 Accounting Log Report Generator utilitym                 DECdtm  '     C-2 OpenVMS VAX Save Set Subclassesm a  p      I                                                           File Subclasses                      o  Utilities                        Mail utility                      DUMP utility"                     RUNOFF utility!                     Phone utility (                     OpenVMS Help library,                     Foreign Terminal Support9                     LAT-11 terminal server (via Ethernet) %                     Standalone backupfF                     Error Log Report Generator utility (ANALYZE/ERROR)"                     DECTPU utility.                     Terminal Fallback Facility8                     National Character Set utility (NCS)=                     C language internationalization utilities                  o  TECO editor  "               o  EDT documentation  ,               o  OpenVMS workstation support  +               o  Workstation device supportM           SAVE SET D SUBCLASSESYI               The following files are contained in the Optional save set:a  $               o  Miscellaneous files                 o  System map                  o  LPA-11 support   %               o  BLISS required files-  9               o  UETP (the User Environment Test Package)                  o  Example files           SAVE SET E SUBCLASSESBH               The following files are contained in the Help Message save               set:  &               o  Help Message database  I                                       OpenVMS VAX Save Set Subclasses C-3c r  a           File Subclassesb           SAVE SET F SUBCLASSES B           The following files are contained in the OpenVMS Manuals           save set:e  !           o  OpenVMS Master Indexa  $           o  OpenVMS Master Glossary  .           o  Overview of OpenVMS Documentation       SAVE SET G SUBCLASSES E           The following files are contained in the OpenVMS Managements           Station save set:   9           o  OpenVMS Management Station software PC files                                                             '     C-4 OpenVMS VAX Save Set Subclasses                          I                                                                         DcI         _________________________________________________________________   I                            DECwindows Display Server and Fonts ComponentsE  I         _________________________________________________________________            Overview  D               This appendix provides a list of files provided by theI               DECwindows base and workstation support components includedd>               on the OpenVMS VAX Version 6.2 distribution kit.                                                            I                        DECwindows Display Server and Fonts Components D-1                 Table of Components,    E     _________________________________________________________________o       Table of Components   ?           Table D-1 contains the name of the DECwindows display >           server and fonts components, the directory where the=           component can be found, a brief description of whatu@           the component does, and one of the following component           classifications:  =           o  BASE-Indicates that the component is part of allC              installations.   ;           o  WS-Indicates that the component is part of thet!              workstation support.(  >           o  FONT-Indicates the component is part of the fonts              component.     <     Table D-1 DECwindows Display Server and Fonts ComponentsH     ____________________________________________________________________H                                                                ComponentD     File                      Purpose                          ClassH     ____________________________________________________________________7                          Files in DECW$KEYMAP DirectoryLH     ____________________________________________________________________C     DECW$KEYMAP                                                BASE   E                                              (continued on next page)f                                  6     D-2 DECwindows Display Server and Fonts Components c         I                                                       Table of Componentse      H         Table D-1 (Cont.) DECwindows Display Server and Fonts ComponentsL         ____________________________________________________________________L                                                                    ComponentH         File                      Purpose                          ClassL         ____________________________________________________________________  C                              Files in SYS$LOADABLE IMAGES DirectoryzL         ____________________________________________________________________E         GAADRIVER.EXE             VAXstation II/GPX driver         WS   E         GABDRIVER.EXE             VAXstation 2000/GPX driver       WSM  E         GBBDRIVER.EXE             VAXstation 35x0 driver           WSV  E         GCADRIVER.EXE             VAXstation II monochrome         WSo/                                   device driver   E         GCBDRIVER.EXE             VAXstation 2000 monochrome       WSy/                                   device driverr  E         GEBDRIVER.EXE             Scanproc graphics device         WS (                                   driver  E         GECDRIVER.EXE             Spxg/gt graphics device driver   WS8  E         GFBDRIVER.EXE             Low-cost graphics device         WSm(                                   driver  E         IEDRIVER.EXE              Input extension driver           WS   E         IKDRIVER.EXE              Keyboard decoder driver          WSB  E         IMDRIVER.EXE              Mouse decoder driver             WS0  E         INDRIVER.EXE              Common input function driver     WSe  G         WSDRIVER.EXE              Set display driver               BASE   I         _________________________________________________________________ :                              Files in SYS$SYSTEM DirectoryI         _________________________________________________________________[G         DECW$FONTCOMPILER.EXE     Font compiler image              FONT   G         DECW$MKFONTDIR.EXE        Font utility to generate list    FONTo4                                   of fonts and paths  E         DECW$SERVER_MAIN.EXE      Server main image                WS   G         DECW$SETSHODIS.EXE        SHOW DISPLAY command image       BASE.  I                                                  (continued on next page)   I                        DECwindows Display Server and Fonts Components D-3                 Table of Components.      C     Table D-1 (Cont.)DECwindows Display Server and Fonts Components H     ____________________________________________________________________H                                                                ComponentD     File                      Purpose                          ClassH     ____________________________________________________________________  5                          Files in DECW$FONT DirectoryAH     ____________________________________________________________________A     See VMS DECwindows Xlib   DECwindows fonts                 WSV     Programming Volume  H     ____________________________________________________________________9                          Files in DECW$EXAMPLES DirectoryEH     ____________________________________________________________________C     DECW$FONT_ALIAS_          Example alias file for Charter   FONT #     CHARTER.DAT               fontsD  C     DECW$FONT_ALIAS_          Example alias file for 100 dpi   FONTh+     CHARTER_100DPI.DAT        Charter fontss  C     DECW$FONT_ALIAS_          Brief alias name list for        FONTp+     FILENAMES.DAT             shipped fonts   C     DECW$FONT_ALIAS_          Example alias file for           FONT (     KANJI.DAT                 Kanjifonts  C     DECW$FONT_ALIAS_          Example alias file for Lucida    FONTx#     LUCIDA.DAT                fonts   C     DECW$FONT_ALIAS_LUCIDA_   Example alias file for 100 dpi   FONT!*     100DPI.DAT                Lucida fonts  H     ____________________________________________________________________7                          Files in SYS$LIBRARY Directory H     ____________________________________________________________________A     DECW$DRIVER.MLB           Driver macro library             WSt  C     DECW$FONTCOMPILER.CLD     CLD for font compile commands    FONT   A     DECW$SERVER_DDX_GA.EXE    Server color device support      WS -                               shareable imageD  A     DECW$SERVER_DDX_GB.EXE    Server color device support      WS$-                               shareable imageU  A     DECW$SERVER_DDX_GC.EXE    Server monochrome device         WSO5                               support shareable image   E                                              (continued on next page)f  6     D-4 DECwindows Display Server and Fonts Components F  .      I                                                       Table of Components       G         Table D-1 (Cont.)DECwindows Display Server and Fonts ComponentsSL         ____________________________________________________________________L                                                                    ComponentH         File                      Purpose                          ClassL         ____________________________________________________________________  ;                              Files in SYS$LIBRARY Directory/L         ____________________________________________________________________E         DECW$SERVER_DDX_GE.EXE    Server scanproc device-          WSa;                                   dependent shareable image/  E         DECW$SERVER_DDX_GF.EXE    Server low-cost graphics         WSs<                                   device-dependent shareable'                                   image   E         DECW$SERVER_DIX.EXE       Server device independent        WS )                                   support   E         DECW$SERVER_XINPUT_       Input extension for handling     WS ;         IE.EXE                    nonstandard input devicesm  G         DECW$SESSIONSHRP.EXE      Support routines for             BASE <                                   DECwindows Session Manager  E         DECW$SVEXT_ADOBE_DPS_     Display PostScript server        WS 1         EXTENSION.EXE             extension image   E         DECW$SVEXT_D2DX_          DECwindows 2D extensions         WSe         EXTENSIONS.EXE  E         DECW$SVEXT_DEC_           Input and event recording and    WSC4         XTRAP.EXE                 playback extention  E         DECW$SVEXT_MULTI_         DECwindows multi-buffering       WSe+         BUFFERING.EXE             extensiont  E         DECW$SVEXT_X3D_PEX.EXE    Phigs Extension to X (PEX) for   WS:$                                   3D  E         DECW$SVEXT_X3D_PEX_       PEX for 35x0 systems             WSI         GB.EXE  E         DECW$SVEXT_X3D_PEX_GB_    PEX micro code for 35x0          WS )         UCODE.EXE                 systemsi  E         DECW$SVEXT_X3D_PEX_       PEX for scanproc systems         WSr         GE.EXE  I                                                  (continued on next page)   I                        DECwindows Display Server and Fonts Components D-5     s           Table of Componentse      C     Table D-1 (Cont.)DECwindows Display Server and Fonts ComponentsiH     ____________________________________________________________________H                                                                ComponentD     File                      Purpose                          ClassH     ____________________________________________________________________  7                          Files in SYS$LIBRARY Directory H     ____________________________________________________________________A     DECW$SVEXT_X3D_PEX_       PEX for scanproc systems with    WSe0     STP.EXE                   geometry processor  A     DECW$SVEXT_X3D_PEX_STP_   PEX microcode for scanproc       WS 3     UCODE.EXE                 systems with geometry '                               processor   A     DECW$SVEXT_X3D_PEX_       PEX color frame buffer           WSh,     VCFB.EXE                  (software PEX)  A     DECW$SVEXT_XIE.EXE        DECwindows imaging extention     WS   A     DECW$SVEXT_               DECwindows input extension       WSt     XINPUTEXTENSION.EXE   C     DECW$TRANSPORT_           Common transport shareable       BASE #     COMMON.EXE                imager  C     DECW$TRANSPORT_           DECnet transport image           BASEy     DECNET.EXE  C     DECW$TRANSPORT_           Local transport image            BASEs
     LOCAL.EXED  C     DECW$TRANSPORT_           TCP/IP transport image           BASE 
     TCPIP.EXE:  C     DECW$XPORTCOM.H           Common transport definitions     BASE   C     DECW$XPORTCOM.MAR         Common transport definitions     BASE   C     DECW$XPORTCOM.R32         Common transport definitions     BASE   C     DECW$XPORTDEF.H           Transport definitions            BASEh  C     DECW$XPORTDEF.MAR         Transport definitions            BASEd  C     DECW$XPORTDEF.R32         Transport definitions            BASE   C     DECW$XPORTMAC.R32         Transport BLISS macros           BASEI  E                                              (continued on next page)   6     D-6 DECwindows Display Server and Fonts Components r  r      I                                                       Table of Componentse      G         Table D-1 (Cont.)DECwindows Display Server and Fonts Components L         ____________________________________________________________________L                                                                    ComponentH         File                      Purpose                          ClassL         ____________________________________________________________________  ;                              Files in SYS$LIBRARY DirectorysL         ____________________________________________________________________G         DECW$XPORTMSG.R32         Transport message symbols        BASE   E         XDPS$MASTERDPSVM.DAT      Display PostScript support       WSs&                                   file  L         ____________________________________________________________________;                              Files in SYS$MANAGER Directory L         ____________________________________________________________________G         DECW$DEVICE.COM           Device detection and             BASE_/                                   configuration   E         DECW$DEVICE_GE.COM        Scanproc device detection and    WSe/                                   configurationk  E         DECW$DEVICE_GF.COM        Low-cost graphics device         WS =                                   detection and configuratione  E         DECW$DEVICE_GG.COM        Scanproc turbo device            WSg=                                   detection and configuration   E         DECW$RGB.DAT              Definitions of the color names   WSl-                                   used by the 6                                   XStoreNamedColor and;                                   XAllocNamedColor requestsa  E         DECW$STARTSERVER.COM      Server initialization and        WS )                                   startupA  L         ____________________________________________________________________;                              Files in SYS$MESSAGE DirectorysL         ____________________________________________________________________G         DECW$TRANSPORTMSG.EXE     Transport message image          BASEs  I                                                  (continued on next page)         I                        DECwindows Display Server and Fonts Components D-7  C  H           Table of Componentso      C     Table D-1 (Cont.)DECwindows Display Server and Fonts Components H     ____________________________________________________________________H                                                                ComponentD     File                      Purpose                          ClassH     ____________________________________________________________________  6                          Files in SYS$UPDATE DirectoryH     ____________________________________________________________________C     DECW$MKFONTDIR.COM        Command file to invoke           FONT 5                               DECW$MKFONTDIR.EXE fonty%                               utility H     ____________________________________________________________________                                                                    6     D-8 DECwindows Display Server and Fonts Components                         I                                                                         E I         _________________________________________________________________t  I                                              NEW_OVER and NEW_UNDER Filesl  I         _________________________________________________________________            Overview  F               This appendix lists files installed either over or under/               existing files during an upgrade.                                                               I                                          NEW_OVER and NEW_UNDER Files E-1                 Where Files Are Installed     E     _________________________________________________________________e       Where Files Are InstalledE         INTRODUCTIONA           During an upgrade, the procedure replaces certain filestD           that exist on your system with new versions of those filesE           from the OpenVMS VAX Version 6.2 distribution kit. For some C           system files, the upgrade procedure does not replace your C           existing system files, which might contain customizationsiE           for your site. Instead, the procedure retains your existingSB           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 theA           contents of your existing files and the contents of theiB           new files provided by OpenVMS VAX Version 6.2. Enter the-           command using the following syntax:   D           DIFFERENCES/OUTPUT=filespec existing_filename new_filename  >           The /OUTPUT qualifier causes the DIFFERENCES commandA           to write the list of differences to the output file youiC           specify. This output file will have the default file type_@           .DIF. For more information about using the DIFFERENCES7           command, refer to the OpenVMS DCL Dictionary.l  C           New files that the procedure installs at a version numberrE           higher than your existing files are referred to as new_oversE           files. You must use these files at least until you complete C           the upgrade. After you have upgraded your system, you cane1           add your customizations to these files.   @           New files installed at a version number lower than theA           existing files are referred to as new_under files. ThiseB           allows you to continue to use your existing files during            and after the upgrade.  A           If you purge a new_over file, you are left with the new C           version of the file provided by the distribution kit, andsE           any customizations you might have made to the existing fileoC           will be lost. If you purge a new_under file, you are leftt8           with the file that existed before the upgrade.  $     E-2 NEW_OVER and NEW_UNDER Files    p      I                                                 Where Files Are Installeds      D               In addition to the new_over and new_under files, thereG               are certain files that are intended to contain your site- I               specific modifications. During an upgrade, the old versions E               of these files are retained if they were present before_C               the upgrade. The new version of the file is installedWD               only if no old version is present on your system. WithH               the exception of TFF$STARTUP.COM, there is a correspondingH               .TEMPLATE file for each of the site-specfic files. The newE               version of the .TEMPLATE file replaces the old version.s           NEW_OVER FILESF               During an upgrade, the following new files are installedA               over (that is, at a version number higher than) then               existing files:o  %                  [SYSEXE]SHUTDOWN.COM_$                  [SYSEXE]STARTUP.COM$                  [SYSHLP]HELPLIB.HLB#                  [SYSLIB]ADARTL.EXEC#                  [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.EXEa#                  [SYSLIB]LIBRTL.EXE $                  [SYSLIB]LIBRTL2.EXE#                  [SYSLIB]MTHRTL.EXE #                  [SYSLIB]PASRTL.EXEn#                  [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    I                                          NEW_OVER and NEW_UNDER Files E-3  -  t           Where Files Are Installed                     [SYSLIB]VMSRTL.EXE                [SYSLIB]VMTHRTL.EXE"              [SYSMGR]DBLSTRTUP.COM%              [SYSMGR]WELCOME.TEMPLATEa               [SYSMGR]WELCOME.TXT       NEW_UNDER FILES B           During an upgrade, the following new files are installed=           under (that is, at a version number lower than) the            existing files:e  ,              [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       SITE-SPECIFIC FILESlC           The following files are intended to contain site-specific 9           modifications. Note that, with the exception of B           TFF$STARTUP.COM, there is a corresponding .TEMPLATE fileC           for each of these files. The new version of the .TEMPLATE (           file replaces the old version.                [SYSEXE]SYSUAF.DATr/              [SYSMGR]AGEN$NEW_NODE_DEFAULTS.DATl4              [SYSMGR]AGEN$NEW_SATELLITE_DEFAULTS.DAT&              [SYSMGR]LAT$SYSTARTUP.COM              [SYSMGR]LOGIN.COM!              [SYSMGR]SYCONFIG.COM_#              [SYSMGR]SYLOGICALS.COM                [SYSMGR]SYLOGIN.COM&              [SYSMGR]SYPAGSWPFILES.COM#              [SYSMGR]SYSECURITY.COM "              [SYSMGR]SYSHUTDWN.COM&              [SYSMGR]SYSTARTUP_VMS.COM$              [SYSMGR]TFF$STARTUP.COM        $     E-4 NEW_OVER and NEW_UNDER Files _  _                    I                                                                         F I         __________________________________________________________________  I                               Preparing to Use OpenVMS Management StationP  I         __________________________________________________________________           Overview  H               This appendix describes how to prepare your OpenVMS systemF               and your PC to run the OpenVMS Management Station serverH               and client software. The information provided includes the               following:  A               o  Preliminary procedures, including the following:   (                  -  Editing system files  F                  -  Starting OpenVMS Management Station on other nodes  C                  -  Verifying that you have the proper memory, diskcF                     space, media, and the required software to installA                     and run OpenVMS Management Station on your PC   F                  -  Creating installation media for PC client software  :               o  Installing the client software on your PC  &               o  Defining DECnet nodes  &               o  Accessing online help  ;               o  PATHWORKS installation tips and guidelinesa                  I                           Preparing to Use OpenVMS Management Station F-1     W           Introduction    E     _________________________________________________________________        Introduction  ;           The OpenVMS Management Station is a client-server =           application that provides OpenVMS system management_A           capabilities through a client application on a personal 2           computer (PC) running Microsoft Windows.       REQUIRED FILES@           During the OpenVMS Version 6.2 installation or upgrade@           procedure, the OpenVMS Management Station server filesB           are automatically installed on your OpenVMS system disk.B           However to obtain complete support, you must also selectE           the OpenVMS Management Station client software files during_D           the OpenVMS installation or upgrade procedure. Those filesD           are required to create the installation media that you use4           to install the client software on your PC.  D           Note: If you did not select the OpenVMS Management StationD           component during the installation or upgrade, you must addC           those files to your OpenVMS system disk before you follow D           the instructions in this appendix. Use the OpenVMS VersionA           6.2 distribution media and VMSTAILOR to add the OpenVMS C           Management Station files to your system. (For information 1           about using VMSTAILOR, see Chapter 10.)                                         3     F-2 Preparing to Use OpenVMS Management Station            I                                                              Introductione               CHECKLIST G               Use the following checklist as a guide to verify that you D               perform the required tasks described in this appendix:  G               <  Be sure the optional OpenVMS Management Station clientEE                  software files are installed on your OpenVMS system.O  C               <  Edit the system startup and shutdown files on your                    OpenVMS system.  H               <  Start OpenVMS Management Station on other OpenVMS nodes                  (optional).  H               <  Be sure that your PC has at least 8 MB of random-accessF                  memory (RAM) and 6 MB of free disk space and that youE                  have two, 3-1/2 inch, high-density floppy diskettes.o  F               <  Be sure that your PC is running MS-DOS Version 5.0 orE                  later and Microsoft Windows Version 3.1 or MicrosoftB5                  Windows for Workgroups Version 3.11.e  G               <  Be sure your PC is running PATHWORKS V5.0A for DOS and I                  Windows (or V5.1) client software and that the PATHWORKSEH                  file PWSOCK.DLL is available to your PC. (If necessary,H                  refer to the section titled PATHWORKS Installation Tips!                  and Guidelines.)l  @               <  Create the PC installation media (on two floppyE                  diskettes) containing the OpenVMS Management Station_!                  client software.   G               <  Install the OpenVMS Management Station client software                   on your PC.  H               <  After installing the client software on your PC, defineH                  the DECnet node names and network addresses of primary-@                  server OpenVMS systems that you want to manage.  @               <  Access online help to get started using OpenVMS$                  Management Station.          I                           Preparing to Use OpenVMS Management Station F-3c r                           I         _________________________________________________________________s  I                                                    Preparing Your Systems     I         _________________________________________________________________w           Overview  >               This section includes the following information:  I               o  A list of the OpenVMS Management Station files installedo(                  on your OpenVMS system.  C               o  A procedure for editing the system files to enabletE                  automatic startup and shutdown of OpenVMS Management                   Station  G               o  A procedure for starting OpenVMS Management Station on/,                  other nodes in a VMScluster  I               o  Preliminary tasks and requirements for preparing your PC +                  to run the client softwareo  E               o  A procedure for creating installation media from thetE                  client software installed on the OpenVMS system diski                            I                           Preparing to Use OpenVMS Management Station F-5E X  T      !     Preparing Your OpenVMS System     E     _________________________________________________________________   !     Preparing Your OpenVMS System          INTRODUCTION@           During the OpenVMS Version 6.2 installation or upgradeD           procedure, the OpenVMS Management Station server files areD           automatically installed on your OpenVMS system disk. AfterC           the installation or upgrade is complete, you must prepare_E           your OpenVMS system to run the server software so that your E           system can properly interact with the PC running the cliente           software.          FILES INSTALLED ON OPENVMSB           The files installed automatically on your OpenVMS system@           disk following the OpenVMS Version 6.2 installation or+           upgrade procedure are as follows:_  &           o  SYS$SYSTEM:TNT$SERVER.EXE  (           o  SYS$STARTUP:TNT$STARTUP.COM  )           o  SYS$STARTUP:TNT$SHUTDOWN.COMS  !           o  SYS$TEST:TNT$IVP.COMi  7           o  SYS$COMMON:[SYSTEST.TNT]TNT$SERVER_IVP.EXEe  *           o  SYS$HELP:TNT010.RELEASE_NOTES  :           This file is created when the server is started:  ,           o  SYS$COMMON:[SYSEXE]TNT$UADB.DAT  C           These client software files are installed on your OpenVMS ?           system when you select the OpenVMS Management Station_@           component during the installation or upgrade procedure@           (or when you later add those files to the system using<           VMSTAILOR). These files allow you to create the PCA           installation media (using the procedure described later 3           in the section titled Preparing Your PC).   0           o  SYS$COMMON:[TNT.CLIENT]DISKIMAG.EXE  0           o  SYS$COMMON:[TNT.CLIENT]TNTCLID1.IMG  0           o  SYS$COMMON:[TNT.CLIENT]TNTCLID2.IMG  3     F-6 Preparing to Use OpenVMS Management Station            I                                             Preparing Your OpenVMS Systeme               EDITING SYSTEM FILESD               You must edit the system startup and shutdown files onF               your OpenVMS system to provide for automatic startup andH               shutdown of OpenVMS Management Station when your system is               rebooted.   4               To edit the files, follow these steps:H               __________________________________________________________               Step     ActionXH               __________________________________________________________?               1        Add the command line that starts OpenVMS E                        Management Station to the system startup file, 5                        SYS$MANAGER:SYSTARTUP_VMS.COM.   F                        The following example shows the network startupF                        command line followed by the OpenVMS Management4                        Station startup command line:  2                        $ @SYS$MANAGER:STARTNET.COM                             ._                             ._                             . 5                        $ @SYS$STARTUP:TNT$STARTUP.COM   D                        Note: OpenVMS Management Station cannot startF                        until after the network has started. Therefore,D                        you must position this new command line afterH                        the line that invokes the network startup command!                        procedure.   C               2        Add the following command line to the systemn@                        shutdown file, SYS$MANAGER:SYSHUTDWN.COM:  6                        $ @SYS$STARTUP:TNT$SHUTDOWN.COMH               __________________________________________________________  :         STARTING OPENVMS MANAGEMENT STATION ON OTHER NODESH               If you plan to run OpenVMS Management Station on more thanH               one node in a VMScluster without rebooting, you must startC               the software on those nodes by entering the following                command:  ,               $ @SYS$STARTUP:TNT$STARTUP.COM    I                           Preparing to Use OpenVMS Management Station F-7O           !     Preparing Your OpenVMS Systemh      A           If you are performing an upgrade or an installation and_?           OpenVMS Management Station is already running on your D           cluster, add the RESTART parameter to the startup command,           as follows:   0           $ @SYS$STARTUP:TNT$STARTUP.COM RESTART                                                                              3     F-8 Preparing to Use OpenVMS Management Stations t  p      I                                                         Preparing Your PC     I         _________________________________________________________________            Preparing Your PCi             INTRODUCTIOND               During the OpenVMS Version 6.2 installation or upgradeD               procedure, you selected the OpenVMS Management StationC               client software files to be installed on your OpenVMShI               system disk (or you added them later using VMSTAILOR. After.E               you have prepared your OpenVMS system to run the server G               software, you must next prepare your PC to run the clienth               software.s    &         REQUIRED MEMORY AND DISK SPACEE               Your PC requires 8 MB of random-access memory (RAM) andiG               6 MB of free disk space to install the OpenVMS Managementi&               Station client software.  E               To determine the amount of memory available on your PC, ?               enter the following command at the MS-DOS prompt:                  C:\> mem  G               To determine the amount of available free disk space, youeC               can enter the following command at the MS-DOS prompt:                  C:\> dir  
         MEDIAdE               You need two 3-1/2, inch high-density floppy diskettes, I               which have to be formatted. You will use those diskettes too/               create the PC installation media.t           REQUIRED SOFTWAREnH               Table F-1 describes the software that must be installed onC               your PC before installing OpenVMS Management Station.e                I                           Preparing to Use OpenVMS Management Station F-9a t  h           Preparing Your PCi      6           Table F-1 Prerequisite and Optional SoftwareE           ___________________________________________________________R,           Prerequisite Products      PurposeE           ___________________________________________________________ 5           MS-DOS Version 5.0 or      Operating system            later   9           Microsoft Windows Version  Windowing capability            3.1 or           Microsoft Windows forg!           Workgroups Version 3.11   C           PATHWORKS V5.0A for DOS    ManageWORKS user interface and 6           and Windows (or V5.1)      network transport           client softwareyE           ___________________________________________________________x  !     PATHWORKS CLIENT REQUIREMENTSa;           Note the following PATHWORKS client requirements:s  B           o  If you have any version of the PATHWORKS client other?              than V5.0A or V5.1 installed on your PC, it is not 5              supported by OpenVMS Management Station.a  D              Refer to the section titled PATHWORKS Installation TipsE              and Guidelines to help you quickly install the PATHWORKSOA              V5.0A for DOS and Windows (or V5.1) client software.H  C           o  OpenVMS Management Station requires that the PATHWORKSLC              file PWSOCK.DLL be available to your PC. PWSOCK.DLL is D              installed as part of the Socket Library Files option of7              the PATHWORKS Network Utilities component.L  D              The error message "Cannot Find PWSOCK.DLL" is displayedE              when you run OpenVMS Management Station if PWSOCK.DLL is *              not available to your system.  D              Refer to the section within PATHWORKS Installation Tips@              and Guidelines titled Configuring Using Windows for@              instructions on how to configure the Socket Library@              Files option to make the PWSOCK.DLL file available.          4     F-10 Preparing to Use OpenVMS Management Station    Y      I                                                         Preparing Your PCB      '         CREATING THE INSTALLATION MEDIA.I               Create the PC installation media using the following steps.   2               1. Open an MS-DOS window on your PC.  C               2. Copy the files to a temporary directory on your PCSD                  from the OpenVMS system on which you have installed9                  the OpenVMS Management Station software.   G               3. At the MS-DOS prompt, use the NFT utility on the PC to,B                  copy the files by entering the following command:  A        C:\> NFT COPY /BLOCK node"username password"::SYS$COMMON:- %             [TNT.CLIENT]*.* \temp-dirA  B                  where node, username, and password are the accessB                  control information for an account on the OpenVMSB                  system, and temp-dir is the name of the temporary                  directory.C  F                 ________________________ Note ________________________  B                 If a DECnet node is not defined in your PC networkB                 database, refer to the section in Chapter 4 titledE                 Procedure for Defining DECnet Nodes for instructions.d  F                 ______________________________________________________  H               4. Insert a formatted floppy disk in the 3-1/2 inch floppyF                  disk drive (A in this example). At the MS-DOS prompt,3                  type the following MS-DOS command:   B                  C:\> \temp-dir\DISKIMAG \temp-dir\TNTCLID1.IMG a:  G                  where temp-dir is the temporary directory used in step                   2.G  H                  When the DISKIMAG program returns to the MS-DOS prompt,D                  remove the floppy disk and label it "Disk 1-Setup".  H               5. Insert a formatted floppy disk in the 3-1/2 inch floppyE                  disk drive. At the MS-DOS prompt, type the following                   command:   B                  C:\> \temp-dir\DISKIMAG \temp-dir\TNTCLID2.IMG a:  G                  where temp-dir is the temporary directory used in step                   2.m  H                  When the DISKIMAG program returns to the MS-DOS prompt,>                  remove the floppy disk and label it "Disk 2".  I                          Preparing to Use OpenVMS Management Station F-11r t  O           Preparing Your PCv      A           6. You can delete the files DISKIMAG.EXE, TNTCLID1.IMG,tE              and TNTCLID2.IMG from temp-dir after creating the floppy,              disks.i  B           You can now proceed with the installation of the OpenVMS0           Management Station PC client software.                                                                              4     F-12 Preparing to Use OpenVMS Management Station    i                        I      ____________________________________________________________________r  I      Installing the OpenVMS Management Station Client Software on Your PCn    I      ____________________________________________________________________            Overview  >               This section provides the following information:  E               o  How to install the OpenVMS Management Station clientU                  on a PC  C               o  How to recover from errors during the installation_  B               o  How to define DECnet nodes after the installation  I               o  The names of the files that are created on your PC aftert!                  the installationn  G               o  How to access online help to get started using OpenVMS #                  Management Stationr                                I                          Preparing to Use OpenVMS Management Station F-13     r      "     Installing the Client Software    E     _________________________________________________________________s  "     Installing the Client Software         INSTALLATION PROCEDUREB           Follow these steps to install OpenVMS Management StationE           client on your PC. (Note that this procedure takes about 10l           minutes.)u  E           ___________________________________________________________t           Step        ActionE           ___________________________________________________________n6           1           Start your PC as you usually do.  >           2           Insert disk 1 in your floppy disk drive.  D           3           Enter the Windows environment and click on the+                       Program Manager icon.m  D           4           In the Menu bar of the Program Manager programD                       group, click on File, and then choose Run from)                       the pull-down menu.   9                       Result: The Run dialog box appears.t  2           5           In the Run dialog box, type:  "                       a:\SETUP.EXE  D                       where a: is the name of the floppy disk drive.  9           6           Click on the OK button to start thee#                       installation.i  A                       Result: A dialog box containing the messagenB                       "Initializing setup, please wait..." appears>                       and is then replaced by a window labeled$                       OpenVMS Setup.              4     F-14 Preparing to Use OpenVMS Management Station n  h      I                                            Installing the Client Softwareo    I               ___________________________________________________________B                Step        ActionI               ___________________________________________________________   H               7           To proceed with the installation, click on the*                           Continue button.  I                           Note: You can stop the installation at any time 9                           by clicking on the Exit button.0  D                           As the installation progresses, the systemA                           displays the names of the files as theyoC                           are copied, and a copy bar indicates whatdF                           percentage of the installation is done. AlsoE                           displayed is a reminder to read the OpenVMS G                           Management Station Read Me file for important &                           information.  H               8           When you are prompted by a dialog box message,F                           remove disk 1 from the disk drive and insert.                           disk 2. Click on OK.  G                           Result: When the copy bar shows that that all E                           the files are copied, a dialog box displays C                           a message indicating the installation has 1                           completed successfully.OI               ____________________________________________________________           RECOVERING FROM ERRORSF               If an error occurs during installation, you will receiveG               an error message describing the problem. This information_G               can help you determine the cause of the problem. An error E               can occur during the installation if one or more of the )               following conditions exist:i  ;               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.A              I                          Preparing to Use OpenVMS Management Station F-15  c  t           Defining DECnet Nodesy    E     _________________________________________________________________        Defining DECnet Nodes          INTRODUCTIONB           After installing the client software on your PC, use theA           MS-DOS Network Control Program (NCP) utility on your PC B           to define the DECnet node names and network addresses ofA           primary-server OpenVMS systems that you want to manage. E           OpenVMS Management Station connects your PC to the primary- D           server system and then routes management operations to theB           target systems. You can define multiple primary servers.  C              ________________________ Note ________________________a  >              Failure to access the NCP utility from the MS-DOS6              prompt can result in connection problems.  A              By accessing the NCP utility from the MS-DOS prompt,u?              you define DECnet node names and network addresseseB              in both DECnet Phase IV and DECnet Phase V databases.@              If you access the NCP utility from Windows, data is/              defined only in Phase V databases.2  C              ______________________________________________________   '     PROCEDURE FOR DEFINING DECNET NODES 4           Follow these steps to define DECnet nodes:  E           ___________________________________________________________            Step        ActionE           ___________________________________________________________   E           1           At the MS-DOS prompt, invoke the NCP utility asS                       follows:                         C:\> NCP  E           2           At the NCP> prompt, type the following command:O  6                       NCP> DEFINE NODE addrs NAME name  C                       where addrs is the DECnet address and name iso+                       the DECnet node name.I                         Example:  8                       NCP> DEFINE NODE 19.208 NAME ISTAR  4     F-16 Preparing to Use OpenVMS Management Station n  o      I                                                     Defining DECnet NodesC    I               ___________________________________________________________I                Step        ActionI               ___________________________________________________________   G               3           At the NCP prompt, type EXIT and press Return 1                           to  exit the operation.sI               ___________________________________________________________c                                                                                I                          Preparing to Use OpenVMS Management Station F-17  s  t           Defining DECnet Nodes_           FILES CREATED ON THE PC_>           The following files (with their directory names) are@           created on your PC when the OpenVMS Management Station'           client software is installed:   .           o  PATHWORKS directory (usually \PW)                -  VMSACNT.DLL                 -  VMSCLU.DLL                -  VMSINFRA.DLL                -  VMSMGMT.DLLg                -  VMSMSCRL.DLL                -  VMSNODE.DLLa                -  VMSTIMEL.DLL                -  VMSUAOMM.DLL                -  ACCOUNT.HLP:                -  DOMAIN.HLP                -  MANAGE.HLP                -  README.WRI  1           o  Windows directory (usually \WINDOWS)                 -  XTIDNW.DLL                -  XTILIB.DLL  ?           o  Window systems directory (usually \WINDOWS\SYSTEM)t                -  CTL3DV2.DLLu          4     F-18 Preparing to Use OpenVMS Management Station    y      I                                                           Getting Startedt    I         _________________________________________________________________            Getting Startedf             INTRODUCTIOND               All information about getting started, setting up, andE               using OpenVMS Management Station is contained in online B               help and the OpenVMS Management Station Overview and               Release Notes.             ACCESSING ONLINE HELP I               Follow these steps to access the OpenVMS Management Station                online help:  I               ___________________________________________________________o                Step        ActionI               ___________________________________________________________ F               1        Open the PATHWORKS Windows Applications program                        group.o  D               2        Click on the OpenVMS Management Help icon for:                        instructions on how to get started.I               ___________________________________________________________                                           I                          Preparing to Use OpenVMS Management Station F-19                              I         _________________________________________________________________o  I                                PATHWORKS Installation Tips and Guidelinesp    I         __________________________________________________________________           Overview  =               This section describes how to do the following:   F               o  Install PATHWORKS for DOS and Windows client software  C               o  Use Windows to configure PATHWORKS client softwaret                                                    I                          Preparing to Use OpenVMS Management Station F-21                 Introduction    E     _________________________________________________________________        Introduction  ?           If you already have the PATHWORKS for DOS and WindowsRA           client software installed on your PC, you can disregarde           this entire section.  A           If you are installing the PATHWORKS for DOS and Windows A           client software on your PC because the PATHWORKS clientaB           software is a requirement for OpenVMS Management Station;           (that is, you are not using PATHWORKS to manage am@           local area network of PCs), you may find the following2           installation tips and guidelines useful.  =           For complete installation instructions and detailed :           information on PATHWORKS, refer to the PATHWORKS           documentation.       REQUIRED DISK SPACErD           PATHWORKS for DOS and Windows client software requirementsC           for free disk space are different during installation andl?           after installation. Files created during installation @           can later be deleted. Table F-2 summarizes the storage           requirements.   +           Table F-2 Disk Space RequirementstE           ___________________________________________________________ !                            Duringa>           Kit              Installation     After InstallationE           ____________________________________________________________0           PATHWORKS for    Up to 30 MB      7 MB           DOS and Windowsr           clientE           ___________________________________________________________o  $     ABOUT INSTALLING AND CONFIGURINGB           You use both MS-DOS and Windows to install and configure(           the PATHWORKS Client software:  6           1. Install the client software using MS-DOS.  D           2. After installation, configure the client software using              Windows._      4     F-22 Preparing to Use OpenVMS Management Station Q  E      H                                                  Installing Using MS-DOS    I         _________________________________________________________________5           Installing Using MS-DOSt  >               Exit Windows before you begin this installation.  A               1. The client software installation procedure wantssC                  to install the software to the root directory of aKI                  "substituted" hard disk. Create a substituted hard drive G                  by typing the following commands at the MS-DOS prompt. G                  Note that the example reflects the PATHWORKS V5.0A for I                  DOS and Windows client software; V5.1 is also supported.e  %                  C:\> mkdir c:\pwv50a (                  C:\> subst x: c:\pwv50a  H                  where x: is the name of an unused MS-DOS drive. (If youF                  have a single hard disk, G is usually a good choice.)  D                  C is the name of a local drive that meets the space                  requirements.  F               2. Insert the LAN Manager setup disk in your PC's floppy"                  drive. Then type:                    a:setup  F                  Note that A is the MS-DOS drive letter for the floppy                  drive.   E               3. Choose the Install Kit option from the Setup window.r  F               4. To install the software to the substituted hard driveA                  created in step 1 (G: was suggested), choose the B                  appropriate drive from the Select Drive list box.F                  (Scroll through the list box if the drive name is not&                  immediately visible.)                    Click on OK.M  G               5. When prompted, insert disk 1 into drive A and click ont                  OK.  E                  A working dialog box displays the names of the files:D                  as they are copied, and a copy gauge indicates what8                  percentage of the installation is done.  E               6. Insert the LAN Manager setup disk again when you aren2                  prompted. Click on the OK button.  I                          Preparing to Use OpenVMS Management Station F-23  d  c           Installing Using MS-DOS_      B           7. From the PATHWORKS Installation utility window, clickD              on the arrow to the right of the Installing to: option.A              Select the substituted drive from the displayed listo              box.o  E           8. From the Install: list box in the PATHWORKS Installation_@              Utility window, you can choose the PATHWORKS clientE              options you want to install. You need only the followings.              options in the Install: list box.  $                 DECnet and Utilities                 ManageWORKS-!                 Network Utilities "                 PATHWORKS Tutorial)                 PATHWORKS Windows Network   =              Remove unneeded options from the Install list bymC              clicking on an option, and then clicking on the Removes=              button to move the selected option to the Do Notm              Install: list box.c  >           9. Verify your selection of options and click on OK.  A           10.An Installation Starting dialog box is displayed andtE              you are asked whether you want to go back and read help.m              Choose NO.r  E           11.When you are prompted, insert the necessary floppy disksI%              to install the software.o  D              A working dialog box displays the names of the files as              they are copied.i  E           12.When the installation process is complete, you are askedoC              whether you want to configure the Workstation Manager;C              choose NO.a  =           13.An Installation Complete dialog box displays the               following message:   3              Exiting PATHWORKS Installation Utility   $              Click on the OK button.  C           14.At this point, the installation utility returns to the C              initial Setup window. Click on the Exit option to quiti0              the PATHWORKS Installation utility.  4     F-24 Preparing to Use OpenVMS Management Station I  a      I                                                 Configuring Using Windows_    I         _________________________________________________________________i  !         Configuring Using Windowsi  C               Use the following steps to configure PATHWORKS clientp               software:c  E               1. Start Windows and choose Run from the File pull-downeE                  menu on the Program Manager menu bar. In the Command .                  Line box, type the following:  !                  x:\pcapp\pwsetupt  F                  where x: is the substituted drive that you created in+                  step 1 (G: was suggested).s  B                  Click on the OK button. This starts the PATHWORKS'                  Configuration utility.e  D               2. Click on the OK button in the Please Enter SoftwareF                  Destination box to signify that the displayed default%                  location is correct.t  D                  A PATHWORKS Configuration Warning box is displayed.D                  Click on the OK button to indicate that you want to.                  create the default directory.  D               3. When you are prompted, verify the substituted driveG                  letter you used when you installed the client software -                  under MS-DOS by clicking OK._  F               4. Choose the Express option from the displayed Select a/                  Configuration Option list box.d  E               5. In the Express: Select a Workstation Template dialogcG                  box, choose the highlighted Blank template by clicking "                  on the OK button.  C               6. In the Customize: Modify Workstation Configurationc;                  template, choose only the following items:   &                  o  PATHWORKS Services  /                  o  Network Adapter Informationn  G                  Deselect the other items. Then click on the OK button.   F               7. You are prompted to select the following tasks (thoseH                  listed in step 4 of the MS-DOS installation procedure):  (                     DECnet and Utilities                     ManageWORKS   I                          Preparing to Use OpenVMS Management Station F-25                 Configuring Using Windowsb      !                 Network Utilities."                 PATHWORKS Tutorial)                 PATHWORKS Windows Network   B              Click on each option. Then click on the Add button toA              move each option to the Run on Workstation list box._  B           8. Choose the DECnet and Utilities option. Then click on              the Detail button._  E           9. From the displayed list box, double-click on the Networkh?              File Transfer option. Then click on the OK button.b  C           10.A Customize: Select PATHWORKS Services for Workstation B              dialog box is displayed. Choose the Network Utilities4              option, and click on the Detail button.  D           11.From the displayed list box, double-click on the Socket?              Library Files option. Then click on the OK button.o  D           12.From the displayed Customize: Select PATHWORKS Services@              for Workstation dialog box, click on the OK button.  @           13.Select the Ethernet adapter installed in your PC byB              clicking on the appropriate adapter description. Then              click on OK.   B           14.When you are prompted, enter the DECnet node name andA              DECnet network address. Do not enter the server node +              name and address. Click on OK.   B           15.In the Enter Windows Directory dialog box, accept the<              displayed default by clicking on the OK button.  @           16.In the Customize: Save Template to Disk dialog box,?              choose a name for the startup template (any string @              of characters is permitted), along with an optional8              description. Then click on the Save button.  >           17.A displayed message asks whether you want to have>              the network started automatically via an entry in              AUTOEXEC.BAT.  A              Select YES. If you start up Windows in AUTOEXEC.BAT,uA              examine AUTOEXEC.BAT after the configuration utilitynB              exits to ensure that the call to STARTNET.BAT appears$              before the WIN command.  4     F-26 Preparing to Use OpenVMS Management Station           I                                                 Configuring Using Windows       G               18.In the displayed Customize: PROTOCOL.INI Editor dialogMB                  box, click on the OK button to accept the default                  options._  H                  A copy gauge displays the progress of the installation.  F               19.Select the OK option to exit the displayed Customize:4                  Configuration Completed dialog box.  =               20.Select the Exit option to exit the PATHWORKSn'                  Configuration utility.   G                 ______________________ Important ______________________n  F                 You must exit Windows and restart your computer beforeD                 you install the OpenVMS Management Station software.  F                 ______________________________________________________                                                      I                          Preparing to Use OpenVMS Management Station F-27p p  a           Configuring Using Windows            STARTING WINDOWSD           The first time Windows starts after this installation, you           see the message:  (           Could not load Windows Network  D           Click on the "Disable this warning" button, and then click           on the OK button.        DELETING A DIRECTORY@           Now that you have successfully installed the PATHWORKSB           Client software and have run the PATHWORKS ConfigurationA           utility, you can delete the PWV50A directory, which you_<           created in step 1 when you installed using MS-DOS.                                                              4     F-28 Preparing to Use OpenVMS Management Station    t                    I                                                                         G I         _________________________________________________________________o  I                                               Small Capacity System Disks   I         _________________________________________________________________            Overview  H               This appendix describes some methods you can use to manageC               small capacity system disks, along with some specific H               recommendations for installing or upgrading to OpenVMS VAXF               Version 6.2 and DECwindows Motif for OpenVMS VAX VersionB               1.2-3 on an RZ23L, RA80, or RM80 system disk. (TheseE               recommendations will also work for Versions 1.1 and 1.2_G               of the DECwindows Motif for OpenVMS VAX layered product.)d  A               Note that you can use the methods described in this B               appendix to free disk space on any space-constrained               system.                                             I                                           Small Capacity System Disks G-1e S  i           Limited Space Supporti    E     _________________________________________________________________n       Limited Space Support          INTRODUCTIOND           As the OpenVMS VAX operating system and associated layeredC           products continue to develop and mature, their sizes havelA           grown so that previously acceptable system disk devicesLD           might 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 systemC           might be perceived as entry level, it does, in fact, haveiB           an increased need for system disk capacity to handle the(           desired graphical environment.          LIMITED SPACE SUPPORT OPTIONA           In the past, when the OpenVMS VAX operating system grewrE           too large for a specific disk type, that disk was no longer_C           supported as a system device. The OpenVMS VAX Version 6.2 C           operating system and the DECwindows Motif for OpenVMS VAX C           Version 1.2-3 layered product cannot fit, in total, on an            RZ23L disk device.  :           However, to preserve the investment in some userA           configurations, a limited space support option has beeneE           introduced that will allow the RZ23L to continue to be usedhB           as a system disk but with some features removed. For theE           most part, these features include new online documentation,_B           programming examples, and programming support files. TheD           most important mechanisms used to provide this environmentB           are the OpenVMS VAX and DECwindows tailoring facilities,@           VMSTAILOR and DECW$TAILOR. (For more information about,           these facilities, see Chapter 10.)  C           The limited space support option means that, although the A           disk (in this case, the RZ23L) is supported as a system C           device, you must take some explicit action to not install_D           or to remove some portions of the product so the remainderA           will fit. This option gives small, resource-constrainedeA           system users a choice between investing in new hardware_  #     G-2 Small Capacity System Disks            I                                                     Limited Space SupportP      F               or continuing with existing hardware but with (possibly)#               reduced capabilities.t           CONFIGURATIONS AFFECTED F               The RZ23L disk is now too small for the full OpenVMS VAXF               Version 6.2 and DECwindows Motif for OpenVMS VAX VersionF               1.2-3 kits, regardless of user configuration. Other diskG               devices, such as the RZ24 and RD54 disks, will need to be H               closely monitored, depending on the system environment and!               user configuration.   C               The general disk space guideline for OpenVMS VAX pluslH               DECwindows Motif for OpenVMS VAX Version 1.2-3 is a systemC               disk of at least 175 megabytes (or about 360,000 disk D               blocks). For nonworkstation, single-user systems, thisE               guideline can be reduced to about 125 megabytes becauseuB               DECwindows support is not necessary. For timesharingI               systems, a larger disk is usually necessary due to the need H               for many layered products and applications. For VAXclusterD               systems, a larger system disk capacity is also usually;               required. See the VAXcluster SPD for details.f  H               For specific information about disk space requirements and>               supported system disks, see the OpenVMS VAX SPD.  D               While the absolute minimum disk space requirements canC               make base system support available, layered products, D               applications, and user files usually make it necessaryC               to manage even large capacity system disks carefully._G               Therefore, some of the following techniques and ideas can G               be useful for a broader range of users than can be listed_               by hardware type.o  (         DEALING WITH A SMALL SYSTEM DISKD               You can solve small system disk configuration problems               three ways:s  H               o  Upgrade your hardware to a larger capacity disk device.  F               o  Add additional hardware disk devices (one or more) toC                  the system and redistribute the software contents.i  B               o  Reduce the software contents on the existing disk                  device.  I                                           Small Capacity System Disks G-3                 Limited Space Support       B           Upgrading hardware might have the highest monetary cost,E           but has the benefits of a full environment and the simplesttC           and fastest upgrade mechanism. Adding additional hardware"D           (or using existing extra hardware) can require less money,>           but requires more time and effort for setting up andE           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 E           investigate the tailoring recommendations first. If time or E           simplicity are more important, you might want to purchase a            larger system disk.a                                                                #     G-4 Small Capacity System Disks  p         I                                                  Tailoring Considerations     I         _________________________________________________________________             Tailoring Considerations             INTRODUCTIONI               Most of this appendix describes the mechanisms for reducing G               the software contents on the existing disk device, mostly B               by tailoring. There are also some hints for multipleF               disk systems. There is nothing specific to recommend forG               upgrading the hardware device, except that moving up in a H               single large increment is much more effective than several               smaller ones.   F               The target device in the following sections is the RZ23LG               disk, which has 237,600 blocks (or 121 megabytes) of disk E               space. However, you can use these methods on any system.1               that is tight on system disk space.r           CONFIGURATION GOALSC@               The basic configuration goal for the limited spaceG               support option is for an environment that is not used for-G               programming. Typically, this would be a system with a fewcF               user applications or a turnkey system. It is possible toF               build a viable system with a single programming languageG               environment (notably, the C language); however, the spaceWD               used for this support and for the compiler reduces the-               amount of available user space.o  D               There are some mechanisms and techniques common to anyF               space-constrained system both for installing new systemsA               and for upgrading existing systems. One of the mostAB               important considerations is to reduce the disk spaceC               consumption of the normal, ongoing system environment C               before doing an upgrade or as soon as possible during F               or after an installation. Some methods for accomplishingH               this are discussed in the section Managing Single or SmallF               System Disk Systems and in the section Managing Multiple               Disk Systems.k  F               Note that, during an upgrade or installation, there willG               be a period of time when the windowing software is likely H               to be unavailable. This means that, on a workstation, yourH               monitor will function only as an operator console, and you>               will not be able to use screen-oriented editors.  I                                           Small Capacity System Disks G-5                 Tailoring Considerations      6     CONTROLLING THE SIZE OF DUMP, PAGE, AND SWAP FILES?           One of the primary things to control is the sizing oftB           the dump, page, and swap files in AUTOGEN. The tailoringD           facilities automatically use AUTOGEN to reboot the system,D           adjusting anything that the tailoring might have affected.?           Because AUTOGEN normally includes existing disk spaceM>           in calculating the sizes for these files, unexpectedA           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 fileC           SYS$SYSTEM:MODPARAMS.DAT will prevent this from occurring D           during an upgrade or after an installation (and, possibly,-           while installing layered products).                                                                 #     G-6 Small Capacity System Diskse t         I                                                  Tailoring Considerations       C               The following values are suggested as generous for ano               upgrade:  !                  PAGEFILE = 38000u!                  SWAPFILE = 13500o                  DUMPFILE = 0n  G               If your system has been running successfully with smallerd(               values, use those instead.  F               If your windowing system is unavailable, you will not beE               able to use a screen-oriented editor to add these lines C               to the SYS$SYSTEM:MODPARAMS.DAT file. You can use the.F               COPY command to add lines to the end of the text file as               follows:  T         $ COPY SYS$SYSTEM:MODPARAMS.DAT,SYS$INPUT: SYS$SYSTEM:MODPARAMS.DAT <Return>#         newparam1 = value1 <Return>f#         newparam2 = value2 <Return>          <Ctrl/Z>  E               Note: To be able to use the delete key more effectivelytI               when typing input to the console, set the operator terminalmF               to be a scope (assuming it is not a hardcopy device). ToI               set the console terminal to be a scope, enter the followingm               command:  *               $ SET TERM/SCOPE/PERM _OPA0:  .         MAKE A BACKUP COPY OF YOUR SYSTEM DISKG               It is important to make a backup copy of your system disknD               before any system software upgrade. When tailoring andI               system environment options must be used to fit the requiredlG               software on the device, it is even more important to make D               a backup copy before you begin and at major milestonesG               during the procedure. This gives you a fallback to a lastwH               good position in the event that a subsequent step producesH               undesired side effects (especially when tailoring softwareG               off of the disk) or fails due to unexpectedly running outt               of space.t          I                                           Small Capacity System Disks G-7                 Tailoring Considerations           ANALYZE THE SYSTEM DISKoD           The space used on the system disk might include files thatA           have been only partially deleted (usually, because theySC           were still open when an attempt was made to delete them).o=           To recover this space, enter the following command:   .           $ ANALYZE/DISK/REPAIR SYS$SYSDEVICE:  E           Continue to use the ANALYZE/DISK/REPAIR command after everyTC           reboot or before each major step to be sure that all freem@           blocks are available for the upgrade procedure to use.       TAILORING OPTIONStC           The installation and upgrade procedures (for both OpenVMS >           VAX Version 6.2 and DECwindows Motif) let you selectC           optional software to install or upgrade only by save set.tC           The tailoring facilities are capable of finer granularitysC           and can usually select files in smaller groups within thek           save sets.  =           In the case of DECW$MOTIF_TAILOR, the save sets and B           tailoring groups are the same. Additionally, DECW$MOTIF_C           TAILOR can only tailor off. To add files, you must eithero?           use the installation or upgrade procedures or use the @           OpenVMS Backup utility (BACKUP) manually to select theE           desired files. For the VMSTAILOR and DECW$TAILOR utilities,sD           the tailorable options are subsets of the installation andD           upgrade save sets and can be tailored either on or off. IfE           there is sufficient space to take an entire save set, it iseC           usually faster to select it during the procedure and theniE           tailor off the undesired pieces, rather than tailor them on            later.  C           If you are doing an upgrade and have a large area of user @           application files or a large database that is not partA           of the OpenVMS VAX operating system or DECwindows Motif.B           layered product but resides on the system disk, it mightC           be convenient to back up that data to a separate piece ofcC           media, delete it from the system disk before the upgrade, B           and then restore it after the upgrade. The blocks can beB           used in the interim, and you can save time and effort in,           the tailoring and upgrade process.      #     G-8 Small Capacity System Disks            I                                                  Tailoring Considerationso      G               You can decrease the time needed to perform the tailoringlE               and upgrade tasks by disabling highwater marking on the_B               system disk. To disable highwater marking, enter the                following command:  5               $ SET VOLUME/NOHIGHWATER SYS$SYSDEVICE:t  E               Depending on the system security you require, you mightTC               want to leave highwater marking permanently disabled.sE               Otherwise, you can restore it by entering the followingW               command:  3               $ SET VOLUME/HIGHWATER SYS$SYSDEVICE:n                                                                I                                           Small Capacity System Disks G-9  l  t      Y     Installing OpenVMS VAX Version 6.2 and DECwindows Motif for OpenVMS VAX Version 1.2-3d    E     _________________________________________________________________M  ?     Installing OpenVMS VAX Version 6.2 and DECwindows Motif for      OpenVMS VAX Version 1.2-3n         INTRODUCTION<           In general, installing OpenVMS VAX Version 6.2 andB           DECwindows Motif for OpenVMS VAX Version 1.2-3 is easier?           than doing an upgrade because there are no user files A           on the disk when you perform the installation. However, C           because the total size of the two kits is larger than the_D           capacity of the RZ23L disk, you cannot select some options2           and you might have to do some tailoring.    #     INSTALL OPENVMS VAX VERSION 6.2iD           By itself, the entire OpenVMS VAX Version 6.2 distributionE           kit fits on the RZ23L system disk. So, the easiest approachX?           might be to select both the library and optional savei@           sets, then use the VMSTAILOR and DECW$TAILOR utilitiesE           to increase the free space before installing the DECwindows             Motif layered product.  B           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,-B           and do not need the UETP facility, you can choose not toC           select the optional save set during the installation. ThepD           BLISS support in the optional save set (approximately 7000D           blocks) and the examples (over 8500 blocks) are two of the>           largest single areas that you can easily tailor off.  B           You might choose not to install the Help Message utilityC           (MSGHLP) or OpenVMS manuals because both of these optionstE           are also very large. Or, you can select them at the expensenA           of other tailorable options later (or at the expense ofiC           reduced user capacity). The Help Message utility consumes ?           8850 blocks; the OpenVMS manuals consume 4450 blocks.k  C           Once the OpenVMS VAX installation is complete, set up thenD           dump file as required. It is preferable not to have a dumpC           file at all or to use the paging file as described in the A           section System Dump File. Also, set fixed sizes for thepB           page and dump files so that AUTOGEN does not continually  $     G-10 Small Capacity System Disks e  s      I  VAX       Version 6.2 and DECwindows Motif for OpenVMS VAX Version 1.2-3e      F               resize them as you proceed with tailoring and installingI               the DECwindows Motif for OpenVMS layered product. When youreH               environment is complete, you can remove the fixed sizes toG               allow AUTOGEN to calculate appropriate sizes based on thew&               final space on the disk.  C               To fit the operating system on an RZ23L disk and have I               sufficient space to add some layered product or applicationrG               packages and have user space remaining, you can generallypF               support, at most, one programming language and no onlineD               examples or manuals. Use the VMSTAILOR and DECW$TAILOR;               utilities to remove software you do not need.a            INSTALL DECWINDOWS MOTIF@               Depending on the options and setup of your system,C               you might have sufficient space to install the entire E               DECwindows Motif for OpenVMS kit. However, it is likely H               that you again will need to remove support for all but oneH               programming language and not include the examples. BecauseE               the programming support save sets for each language areaE               large, choose only the support for languages you really D               need. In the case of the example files, you might wantF               to install them if you have the space required, and thenG               tailor them off once you have perused them or copied themi               to another area.  H               Remember to use the ANALYZE/DISK/REPAIR command to recover:               any lost space from partially deleted files.          t                            I                                          Small Capacity System Disks G-11l o  o    J     Upgrading to OpenVMS VAX Version 6.2 and DECwindows Motif for OpenVMS I                                                             Version 1.2-3   E     _________________________________________________________________   A     Upgrading to OpenVMS VAX Version 6.2 and DECwindows Motif for      OpenVMS Version 1.2-3n         INTRODUCTIONC           The following sections describe how to upgrade to OpenVMS @           VAX Version 6.2 with the DECwindows Motif Version 1.2->           3 layered product from an OpenVMS Version 6.0 or 6.1@           system running VMS DECwindows Motif Version 1.1. (NoteE           that Version 1.1 is the minimum version of DECwindows Motife7           that you can run on OpenVMS VAX Version 6.2.)u  ;           This option requires the most attention and extra E           tailoring consideration because the disk blocks used by theuD           DECwindows Motif layered product cannot be used during theB           OpenVMS VAX upgrade procedure. This means that you mightD           not be able to select even the library save set during theE           upgrade and that you would need to tailor on portions of itn-           (most notably, the DECnet support)._  C           Depending on your configuration, it might be necessary toaE           tailor off DECwindows Motif and then reinstall it followings           the upgrade.  (     UPGRADING TO OPENVMS VAX VERSION 6.2D           Before beginning the upgrade procedure, prepare the systemA           environment-notably the dump, page, and swap files (seeaB           the section Controlling the Size of Dump, Page, and Swap@           Files)-and remove as many excess files from the systemB           disk as possible. Use the tailoring facilities to removeA           files that will be replaced or obsoleted by the upgrade B           procedure. This is a good way to get the necessary spaceD           (51,550 blocks) to start the upgrade but probably will not?           contribute to the final additional capacity required.e  E           Tailor off all the OpenVMS programming files, examples, andsB           miscellaneous utilities and any DECwindows Motif support>           that is not required. Before upgrading the operatingA           system, keep, at most, one language support option, andeC           do not keep any DECwindows Motif examples unless you havetC           sufficient space to get at least the OpenVMS VAX required 8           and library save sets directly in the upgrade.    $     G-12 Small Capacity System Disks    s      G  OpenVMS VAX Version 6.2 and DECwindows Motif for OpenVMS Version 1.2-3m      C               If you have sufficient space after tailoring to allowmD               both the OpenVMS VAX required and library save sets toG               be selected, then the upgrade will include DECnet supportyI               and DECwindows Motif will start normally after the upgrade.   D               If you cannot select the library save set, the lack ofC               DECnet support will likely keep DECwindows Motif fromoC               starting on your system (at which point you will havecD               only the operator window on your workstation). You canG               then tailor on the DECnet support to get DECwindows Motif H               for OpenVMS running again. After you have DECwindows MotifG               running, tailoring on any other pieces you might not havecG               already acquired from either the library or optional saveu"               sets will be easier.  F               Digital recommends that you not take any of the optionalD               online manuals or the Help Message utility (unless youD               install them on an alternate device). You will want toI               choose the DECwindows device support if you are upgrading as               workstation.  I               Remember to use the ANALYZE/DISK/REPAIR command to clean up *               any partially deleted files.                                                   I                                          Small Capacity System Disks G-13i i         0     Managing Single or Small System Disk Systems    E     _________________________________________________________________o  0     Managing Single or Small System Disk Systems         INTRODUCTIOND           The primary goal for this type of environment is to reduceA           the system disk block usage incurred by the OpenVMS VAXm@           system during normal operation. Both dynamic usage and=           static requirements can be reduced in various ways.r@           Some system processing overhead can also be reduced or@           eliminated in this fashion, along with a corresponding'           reduction in system disk I/O.m         SYSTEM DUMP FILEA           One of the best mechanisms for reducing the total blockaA           overhead of the system is to carefully define the usage ?           of the system dump file. Normally, this is configured B           as a separate file, SYS$SYSTEM:SYSDUMP.DMP, to which the@           contents of memory are written after a detected systemC           failure. Depending on your system requirements, you might 9           be able to reduce or eliminate this disk usage.   E           One effective technique is to use part of the system pagingoB           file, SYS$SYSTEM:PAGEFILE.SYS, as a temporary dump file,B           so that the space used for dump files is not permanentlyA           reserved and gets used only in the event of a crash. To D           do this, you will need to modify some system parameters inD           SYS$SYSTEM:MODPARAMS.DAT and delete the actual SYSDUMP.DMP>           file if it exists. This method is most effective for6           systems having small or medium memory sizes.  C           Alternately, you might set the DUMPSTYLE parameter to uset@           the selective dump mechanism to reduce the size of theC           dump file. This method is typically used for large memorys@           systems that do not need to preserve the entire memoryE           contents in the event of a system failure. Instead of usingeB           selective dumps to the paging file, keep a separate, but$           smaller, SYSDUMP.DMP file.  C           If you have no need to preserve dump files or are runninguC           in a very stable environment, you might want to clear theh@           DUMPBUG parameter to avoid all dump processing and not'           write a dump file on failure.   $     G-14 Small Capacity System Disks           I                              Managing Single or Small System Disk Systems       ,         USING PAGEFILE.SYS FOR THE DUMP FILEC               To use the system paging file as a dump file, add the8C               following lines to the SYS$SYSTEM:MODPARAMS.DAT file:   :               DUMPBUG = 1  ! Enable system dumps (default)B               SAVEDUMP = 1  ! Keep dump in pagefile until analysisJ               DUMPFILE = 0  ! Disallow AUTOGEN to create or size dump file  H               Then delete the SYSDUMP.DMP file by entering the following               command:  /               $ DELETE SYS$SYSTEM:SYSDUMP.DMP;*c  H               Because the system currently has the file open, the deleteC               command will not physically remove the file until theRG               system is shutdown and rebooted. Use the AUTOGEN facility C               to reboot the system. When it has rebooted, enter theeF               following command to clean up and finish the deletion ofE               the file (and any others that were in a similar state):p  2               $ ANALYZE/DISK/REPAIR SYS$SYSDEVICE:  D               After a system failure that writes dump information toD               the pagefile, you can analyze the data by entering the                following command:  5               $ ANALYZE/CRASH SYS$SYSTEM:PAGEFILE.SYSp  G               When your analysis is complete, you can free the pages toeE               be used for paging once again by entering the followingu               command:  =               $ ANALYZE/CRASH/RELEASE SYS$SYSTEM:PAGEFILE.SYS   F               For more information about the system dump file, see the>               OpenVMS VAX System Dump Analyzer Utility Manual.           DECOMPRESSING LIBRARIESpE               The OpenVMS help libraries (as well as some programmingeH               libraries) are distributed in a compressed format. You canF               use the SYS$UPDATE:LIBDECOMP.COM procedure to decompressD               the libraries all at once or individually. For a smallI               system disk, it is almost never worth the extra disk blocks I               consumed to decompress these libraries. The cost of leavingiH               them compressed is a longer access time when you use them.  I                                          Small Capacity System Disks G-15e e  o      0     Managing Single or Small System Disk Systems      A           If you frequently use help or an individual programmingoD           library, it might be worthwhile to individually decompress?           those libraries. If you only infrequently use help or B           do not mind the slower response time of the libraries in1           compressed form, leave them compressed.g       DISABLING LOG FILE CREATION C           Depending on your environment, there might be system jobs D           that create log files of no concern to you or that contain)           more information than you need.   B           Unless you are a network manager or experiencing networkC           problems, you probably do not need to log network events.DA           By not logging network events, you can save disk space,eC           a process slot, and some memory in the running system. Tor@           disable network logging, enter the following commands:  +           $ MCR NCP PURGE KNOWN LOGGING ALL +           $ MCR NCP CLEAR KNOWN LOGGING ALLe  A           You need to enter these commands only once; they becomeuD           permanent unless you reset the DECnet logging information.                                              $     G-16 Small Capacity System Disks           I                              Managing Single or Small System Disk Systemsa      E               To reduce the logging information for other tasks (suchdF               as OPCOM, Accounting, Security Auditing, Network MonitorF               Event Listener, and system-created batch log files), youG               need to add some commands to your system-specific startupOE               command file, SYS$MANAGER:SYSTARTUP_VMS.COM (previouslyd'               called SYSTARTUP_V5.COM).g  H               The following is an example SYSTARTUP_VMS.COM command file,               for a single-user workstation:  /    $ SET NOON     ! Continue thru any problems.     $!h?    $ DEFINE/USER SYS$COMMAND _OPA0:  ! Disable some events fromyK    $ REPLY/DISABLE=(NETWORK,CLUSTER,SECURITY) !  using the operator window. J    $ SET TERM/SCOPE/PERM _OPA0:   ! If windows do not start, use as scope.    $! 9    $ SET AUDIT/ALARM -    ! Log interesting audit events. I    /ENABLE=(AUDIT,AUTHORIZATION,ACL,LOGIN=(LOCAL,DIALUP,NETWORK,REMOTE),-     LOGFAILURE=ALL,BREAKIN=ALL)    $!h@    $ IF F$SEARCH("SYS$MANAGER:ACCOUNTNG.DAT;-1") .NES. "" THEN -H       PURGE SYS$MANAGER:ACCOUNTNG.DAT/KEEP=4 ! Purge old accounting info    $!E?    $ IF F$SEARCH("SYS$MANAGER:OPERATOR.LOG;-1") .NES. "" THEN -nE       PURGE SYS$MANAGER:OPERATOR.LOG/KEEP=4 ! Purge old operator infov    $!aL    $ DEFINE/SYSTEM/EXEC SYS$SYLOGIN SYS$MANAGER:SYLOGIN ! Setup system login    $!tG    $ ENABLE AUTOSTART/QUEUES   ! Provide resources for autostart queuesE3    $ START/QUEUE SYS$BATCH    ! Start a batch queue     $! M    $ SUBMIT/NOKEEP/NOPRINT SYS$MANAGER:STARTNET ! Start net without batch loga    $!SJ    $! ...  add other system specific and layered product commands here ...    $!w	    $ EXIT   G               You might have an environment that can function with even_B               less information than that shown in the example. ForF               example, to disable the operator log file, you would useF               REPLY/NOLOG, or to disable accounting, you would use SETH               ACCOUNTING/DISABLE. For more information about using these7               commands, see the OpenVMS DCL Dictionary.     I                                          Small Capacity System Disks G-17  a         0     Managing Single or Small System Disk Systems      -     ACCESSING EXAMPLE AND DOCUMENTATION FILESo>           If you have network access to another OpenVMS system?           (especially a timesharing system), you do not need toe@           duplicate the example files distributed in the OpenVMS?           VAX or DECwindows Motif kits if they are available onhC           the remote system. Similarly, remote access to the onlinehD           documentation files will also save considerable disk space4           on any system with constrained disk space.                                                                          $     G-18 Small Capacity System Disks i  r      I                                            Managing Multiple Disk Systemsi    I         _________________________________________________________________p  &         Managing Multiple Disk Systems             INTRODUCTIONE               The following sections describe techniques for managingiH               multiple disk systems. In addition to the goal of reducingI               the space requirements on the system device, it is possible I               to simultaneously reduce some of the I/O load to the system E               disk by redirecting necessary functions to an alternateG               device.     %         ALTERNATE PAGE AND SWAP FILESrI               Setting up alternate page and swap files is one of the besthE               ways to reduce both the system disk space usage and I/OsG               overhead. If you set up only a small primary page file ontH               the system disk and install additional page and swap filesH               in the startup command file SYS$MANAGER:SYPAGSWPFILES.COM,H               you can permanently cause these files to consume the leastH               amount of space on the system device. For more informationE               about setting up alternate page and swap files, see the .               OpenVMS System Manager's Manual.           COPYING DUMP FILESD               At startup, you can enhance the use of the paging fileC               as a dump file that will automatically copy dump data A               for later analysis. This releases the disk space inpI               SYS$SYSTEM:PAGEFILE.SYS to be used for paging automaticallyhC               as well. Instead of manually invoking the System DumpeB               Analyzer (SDA) to release the pages, you can add theE               following commands to the SYS$MANAGER:SYSTARTUP_VMS.COM                file:a  5               $ ANALYZE/CRASH SYS$SYSTEM:PAGEFILE.SYS 3               COPY alternate_disk:[dir]dumpname.exte               EXIT  ?               Note: The dump file, whether it is SYSDUMP.DMP or F               PAGEFILE.SYS, must reside on the system disk. This mightF               limit the actual savings you can achieve using alternate               page files.       I                                          Small Capacity System Disks G-19a s  i      "     Managing Multiple Disk Systems      $     OFFLOADING SYSTEM LOGS AND FILES=           There are several system logs and files that can be A           redirected to another device. For other system logs anda@           files, it might be easier to reset and start a new logA           file, copy the old file or files to another device, ando*           purge them from the system disk.  :           Some files that can be redirected are the systemC           authorization file, the queue manager database, the auditr?           log file, and batch log files. Some files that can be >           reset, copied, and purged are the operator log file,B           the accounting log file, and network log files. For moreC           information about these facilities see the OpenVMS System >           Manager's Manual, the OpenVMS DCL Dictionary, or theB           utility reference manual for the utility whose files you           want to offload.  !     OFFLOADING NONESSENTIAL FILES >           Some of the online manuals included with OpenVMS VAXE           Version 6.2 can be redirected to an alternate device during_C           the installation or upgrade procedure. This can save manyiB           valuable system disk blocks while providing quick accessD           to the manuals. For a small system disk configuration withB           multiple disks, this approach is recommended if you want@           the manuals or the Help Message utility (MSGHLP) to be           available online.i                                      $     G-20 Small Capacity System Disks i  w                        I         _________________________________________________________________s  I                                                                  Glossary                      boot, bootstrapE  G               The process of loading system software into a processor's I               main memory. This guide uses the term boot to refer to thiss               process.  $               boot command procedure  G               A program, stored on the console fixed disk, that is used,C               to boot the OpenVMS operating system from a specifiediG               controller. Digital provides a boot command procedure forr:               each controller that the processor supports.                 boot name6  H               The abbreviated name of the boot command procedure you use!               to boot the system.p                 boot server   E               A VAX computer that is part of a local area VAXcluster. I               The boot server is a combination of a MOP server and a diskaF               server for the satellite system disk. See also satellite               node.o                  CI-only VAXcluster  H               A computer system consisting of a number of VAX computers.H               It uses only the computer interconnect (CI) to communicateF               with other VAX computers in the cluster. These computers)               share a single file system.s  (               computer interconnect (CI)  E               A type of I/O subsystem. It links VAX computers to eachgE               other and to HSC devices. See also Hierarchical Storagep&               Controller (HSC) device.  I                                                                Glossary-1t a  t                         DECW$TAILORn  C           A software program that lets you add or remove DECwindowst&           files from your system disk.             device named  D           The name used to identify a device on the system. A deviceE           name indicates the device code, controller designation, andS           unit number.             disk server   A           A VAX computer that is part of a local area VAXcluster. @           This computer provides an access path to CI, CSSI, andA           locally-connected disks for other computers that do notl#           have a direct connection.w  6           Hierarchical Storage Controller (HSC) device  D           A self-contained, intelligent, mass storage subsystem thatE           lets VAX computers in a VAXcluster environment share disks.i/           Examples are the HSC50 and the HSC70.              HSC driven  E           Any disk or tape drive connected to an HSC device is called,C           an HSC drive. A system disk on an HSC drive can be sharede?           by several VAX computers in a VAXcluster environment.              InfoServer  B           A general-purpose disk storage server that allows you toD           use the distribution compact disc to install the operatingC           system on remote client systems connected to the same LANn           (local area network).C             local area VAXclusterp  A           A configuration consisting of one or more VAX computerss@           that act as a MOP server and disk server, and a numberC           of low-end VAX computers that act as satellite nodes. The A           local area network (LAN) connects all of the computers.t5           These computers share a single file system.a             local drive   A           Any drive that is connected directly to a VAX computer._       Glossary-2 n                                media   G               Any packaging agent capable of storing computer software.tH               Examples: compact discs, magnetic tapes, floppy diskettes,*               disk packs, tape cartridges.                 MOP server  B               A computer system running DECnet that downline loadsB               VAXcluster satellites using the DECnet MOP protocol.                 satellite node  E               A VAX computer that is part of a local area VAXcluster. G               A satellite node is downline loaded from a MOP server andoG               then boots remotely from the system disk served by a disksH               server in the local area VAXcluster. See also boot server,&               disk server, MOP server.                 save set  F               The format in which the Backup utility stores files. TheA               OpenVMS operating system is shipped in this format.                  scratch disk  C               A blank disk or a disk with files you no longer need.a                 source drive  I               The drive that holds the distribution kit during an upgradet               or installation.                  spin up, spin down  D               To spin up means to bring a disk drive up to operatingF               speed; to spin down means to bring it to a gradual stop.                 standalone BACKUPl  E               A subset of the BACKUP utility that is booted into mainfH               memory instead of running under the control of the OpenVMSH               operating system. Standalone BACKUP is used to back up andF               restore the system disk and to install OpenVMS operating               system software.                 standalone systemh  ;               A computer system with only one VAX computer.s  I                                                                Glossary-3p o  e                         system disk   <           The disk that contains or will contain the OpenVMSC           operating system. A OpenVMS system disk is set up so thate@           most of the OpenVMS files can be shared by several VAXE           computers. In addition, each computer has its own directory C           on the system disk that contains its page, swap, and dump            files.             target drive  C           The drive that holds the system disk during an upgrade orD           installation.o             transaction logs  C           A log used by DECdtm services to record information about:A           transactions. The Log Manager Control Program (LMCP) isd+           used to create a transaction log.   .           UETP (User Environment Test Package)  C           A software package that tests all the standard peripheral @           devices on your system, various commands and operatingE           system functions, the system's multiuser capability, DECnetM6           for OpenVMS, and the VAXcluster environment.              VAXcluster environment  D           A computer system consisting of a number of VAX computers.D           There are three types of VAXcluster environments: CI-only,-           local area, and mixed interconnect.d             VMSTAILOR   A           A software program that lets you add or remove optional .           OpenVMS files from your system disk.                     Glossary-4 N  Z                            F      _________________________________________________________________  F                                                                  Index      @      A                                 AUTOGEN command procedure9      _______________________________     running (cont'd)pC      Accounting logs                        after an upgrade,  8-33cF        effect of upgrades on, 5-6           at end of an installation,3      Accounts                                  3-41 A        disabling during an                  at end of an upgrade,e3          installation,  3-30                   7-35UD        setting up after an                  before an upgrade,  5-118          installation,  4-5            Automatic restart>      AGEN$INCLUDE files                  for an upgrade,  5-23"        location for upgrades, 5-22(      AGEN$PARAMS.REPORT file,  4-17,   BF         8-34                           _______________________________B      Allocation classes                Backing up the system disk,4        See also ALLOCLASS parameter       4-15, 8-325        determining, 2-7                BACKUP commandeA      ALLOCLASS parameter,  2-7           using to create a system 5        supplying during VAXcluster          disk, 3-6 8          installation,  3-25           Backup proceduresA      ANALYZE/DISK_STRUCTURE utility      before an upgrade,  5-13r>        error message, 5-16             Boot command procedures6        using before an upgrade,          dddGEN,  7-306          5-16                            DEFBOO,  7-30.      Auditing files                    BootingB        replacing after upgrade, 8-5      from console media,  7-14A      AUTOGEN                             from [SYSF],  B-1 to B-8 D        accessing data files during       manually during an upgrade,0          an upgrade,  5-22                  7-14B      AUTOGEN command procedure           with InfoServer ISL file,/        feedback data, 5-11                  3-4 B        running                         Building standalone BACKUP,-           after an installation,          4-4s               4-16  F                                                                Index-1 f  o              =                                        Console media (cont'd)CD     C______________________________     backing up after an upgrade,  /     C2 systems,  2-6                       8-32 E     Checklist                           backing up before an upgrade, /       for the OpenVMS Management           5-13y>          Station, F-3                   booting from during an8     Checklists                             upgrade, 7-146       postinstallation,  4-18           copying,  5-13?       postupgrade,  8-35                modifying for automaticM8       preinstallation,  2-15               restart, 5-23E       preupgrade,  5-31                 modifying to boot from [SYSF]y1     CI-only VAXcluster                     , 7-14 E       information needed to install     required for an installation,T/          , 2-7                             2-15 C       installation question,  3-24      required for upgrades,  5-9e  ?     Cluster upgrades                    restoring original boot   C       See Concurrent upgrades              command procedures, 7-30yB       See Rolling upgrades              updating after an upgrade,/     Clusters                               8-17fB       See also VAXcluster               using backup copies,  5-13B          environments                  Creating a system disk, 3-6@       group numbers,  2-8               from InfoServer devices,/       passwords,  2-8                      3-10:B     CLUSTER_SIZE parameter             Customizing the system, 4-5         of system disk,  3-7F     Command procedures                 D______________________________  +       checking after an upgrade,       DateLB          8-8                            format for entering,  7-11D     Compact disc kit                   dddGEN boot command procedureC       contents of,  1-9                 restoring original version, /     Computer-specific installation         7-30 >        instructions, 3-1               DEC TCP/IP Services for0     Concurrent upgrades,  6-2            OpenVMS:       restrictions,  6-2                configuring,  9-107       setting QUORUM parameter,         function,  9-10i-          6-3                           DECnet <       upgrade procedures,  6-3 to       configuring after an<          6-4                               installation, 4-79     CONSCOPY.COM procedure,  5-13      DECnet for OpenVMSyE     Console                             configuration database,  8-10nE       connecting with SYSGEN,  8-17     ignoring during startup,  4-8aA     Console media                       preparing for an upgrade,y/       automatic update during an           5-24l          upgrade, 5-13       Index-2  C  S              F         DECnet for OpenVMS (cont'd)       DECwindows Motif for OpenVMS5          running with DECwindows Motif       (cont'd)t  B             ,  4-8                          using with OpenVMS VAX?          security measures,  8-10             Version 6.2,  2-3hH         DECnet for OpenVMS license        DECwindows support components,1          registering after an                5-29l>             installation,  4-3              base support, 3-18<          registering during an              choosing optionsF             installation,  3-39                during an installation,5          registering during an upgrade           3-16 F             ,  7-35                            during an upgrade, 7-20<         DECnet node addresses, 2-7          customizing, 9-1I          providing during an                customizing after an upgrade,w2             installation,  3-24               8-30G         DECnet node names, 2-7              customizing the server, 9-2 E          possible values,  3-24             display server files, D-2 >          providing during an                distribution mediaB             installation,  3-24                loading, 3-21, 7-27C         DECnet Phase IV, 1-2                   removing from drive,D;         DECnet/OSI, 1-2                          3-21, 7-28p;         DECnet/OSI for OpenVMS, 7-10        font files, D-2 7         Decompressing system libraries      fonts, 7-21eH          after an installation,  4-10       installing, 2-13, 3-20, 7-227          after an upgrade,  8-23            sizes, 3-16 A         DECset Version 11                   TCP/IP transport, 9-8,<          caution before upgrading,          transports, 9-10B             5-2                             using customer-written?          changing the default debugger        transports,  9-11 =             after upgrading,  5-2           video fonts, 3-19sE             before upgrading,  5-2          workstation support, 3-18aE         DECW$IGNORE_DECNET logical        Default volume label,  3-10 G           name,  4-8                      DEFBOO boot command proceduresG         DECW$MOTIF_TAILOR utility, G-8      restoring original version, 2         DECW$TAILOR utility                   7-306          using on a small system disk,    Device namesA             G-8                             determining, 2-8, 3-6 C          using to install optional          format for upgrade, 7-8 B             components,  3-11               HSC name format for an;          using to remove files from a         upgrade,  7-8 1             system disk,  4-14, 8-27,     DevicesfI             10-12, 10-13                    configuring before an upgrade 4         DECwindows Motif for OpenVMS          ,  7-4            support for,  3-16e          tailoring,  8-27   I                                                                   Index-3t y  m              1     DIGITAL Storage Systems            DSSI disks @        Interconnect (DSSI) disks        device name change,  2-21       See DSSI disks                   Dump filese;     Digital writers                     checking size,  8-7 A       sending comments to,  iii         controlling size of,  G-6 <     Directories                         modifying size,  8-6A       processed during an upgrade,      purged during an upgrade,a/          7-29                              7-23hC     Directory trees                     requirement for an upgrade, /       merged during an upgrade,            5-16 :          7-29                           shared,  5-7, 5-16       Disabling network objects,F        8-10                            E______________________________  A     Disk drives                        Editing startup files, 4-5 ?       selecting for an installation    Error formatter (ERRFMT)lB          , 2-8                          stopped during an upgrade,/     Disk space                             7-14 A       increasing on the system         Errors during installation >          disk, 8-27, G-2                license messages,  3-9=       needed for an upgrade,  5-18     Errors during upgrades E       needed to decompress              cluster hang during shutdown,o.          libraries, 8-23                   6-7=       needed to decompress system       console update,  8-19dC          libraries, 4-10                while entering device code,L.       needed to run UETP,  4-9,            7-9D          8-26                          EXPECTED_VOTES parameter, 8-9D     Distribution kit                    setting for rolling upgrade,.       compact disc,  1-9                   6-6       magnetic tapes,  1-8F       OpenVMS VAX,  3-2                F______________________________A       save sets in,  1-8               Factory installed softwarer       Standalone BACKUP,  3-3m/       tape cartridges,  1-8             See FISt1       TK50 tape cartridges in,  3-2    FAL objectcD       with multiple volumes,  3-2,      enabling or disabling,  8-124          7-26                          Feedback dataC     Distribution media,  1-6            checking before an upgrade,i/       loading,  7-5                        5-11 @       location during an upgrade,      Feedback on documentationC          5-5                            sending comments to Digitala7       multiple volumes,  7-5               writers, iii 4     Documentation                      FIELD account@       sending comments to Digital       setting passwords,  3-28            writers, iiia       Index-4e r  d              @         File Access Listener              Installation procedure5          See FAL object                      (cont'd)tE         FIS (Factory installed              booting system disk afterpH           software),  xvii                    transferring required save  7                                               set,  3-8eH         H______________________________     choosing optional DECwindows  ?         Hardware                              components,  3-18s=          supported,  F-9                    computer-specific @         Help Message save set                 instructions,  3-1F          contents,  C-3                     rebooting the system, 3-41F         Help Message utility                registering licenses, 3-33C          installing,  2-10, 3-13            registering OpenVMS VAXw<         Hierarchical Storage                  license,  3-43A           Controller                        running AUTOGEN, 3-41mI          See HSC                            selecting optional componentsn5         HSC                                   ,  3-12 C          device format for an               setting passwords, 3-28 A             installation,  3-7              specifying VAXcluster B          device format for an upgrade,        configuration,  3-22:             7-8                             stages of, 3-1B          displaying name of,  2-9           when to use, 1-12, 2-24          drives,  1-7                     Installing>          names,  3-6                        DECwindows support@          preparing for installations,         compontents,  3-20B             2-9                             layered products, 4-15E                                             optional components, 3-11aB         I                                 Installing the operating8         _______________________________      system, 3-1;         InfoServer devices, 1-6             C2 systems, 2-6tF          booting Standalone BACKUP,         cautions and restrictions,1             3-3                               2-2 H          creating the system disk           choosing optional DECwindows<             from,  3-10                       support,  7-22  B         Initial software load (ISL)         information needed forF          See ISL                              VAXcluster systems,  2-6>         Installation procedure, 1-12        preparing for, 2-6A          See also Postinstallation          recording log of, 2-4aG             tasks                           VMSINSTAL option G warning,t1          See also Preinstallation             2-2 E             tasks                         ISL (initial software load)c8          booting standalone BACKUP,         booting, 3-4               3-2o  I                                                                   Index-5O e  r              8                                        Licenses (cont'd)E     K______________________________     registering during an upgrade   1     Keyboards                              , 7-34p?       customizing,  9-3                 types of,  3-34 to 3-37a-       layout,  9-2                     Limitse=          DECwindows keymap,  9-4 to     minimum values,  5-18s>             9-8                        LMF (License Management2       model numbers,  9-3                facility)=     Keymap names                        error messages,  3-33oE       determining,  9-3                 example of registration,  A-2M<     KFQSA controller                    license registration9       upgrade requirement,  5-21           procedure, A-2 A                                         system integrated product 9     L______________________________        licenses, A-17pE     Layered products                    using during an installation,o/       availability of,  1-3                3-39iB       effect of upgrade on,  5-7        Volume Shadowing software,/       installing,  4-15                    A-16n<     LIBDECOMP.COM procedure,  8-23     Local Area VAXclusterE       running after an installation     information needed to installe0          , 4-12                            , 2-7E       running after an upgrade,         installation questions,  3-25tB          8-23                           upgrade requirements,  5-68     Libraries                          Local drives, 1-6*       decompressing after an           LogE          installation, 4-10             keeping for an upgrade,  5-31 E       decompressing after an           LURT (License Unit Requirement 5          upgrade, 8-22, 8-23             Table),  A-5V       Library save setF       contents,  C-2                   M______________________________  8       installing,  3-12, 7-17          Magnetic tape kit  6     License Management facility         contents,  1-82       See LMF                          MAIL objectD     License Unit Requirement Table      enabling or disabling,  8-122       See LURT                         Manual bootD     Licenses                            after running AUTOGEN,  7-35A                                         during an upgrade,  7-14, /       See also LMF                         7-30r  @       See also PAK                      enabling for an upgrade,/       error messages,  3-9                 5-23 :       registering after an             Memory requirements:          installation, 4-3              restrictions,  1-4       registering during anm!          installation, 3-33, 3-37c       Index-6e                   9         MicroVAX computers                Network objectsr;          booting from [SYS0],  7-30         disabling, 8-10u@          booting from [SYSF],  7-23,      Network proxy databaseF             B-1                             updating after an upgrade,2         Minimum startup                       8-15:          configuring devices after,       Network securityF             7-4                             updating after an upgrade,2          setting before an upgrade,           8-102             5-19                          NetworksG         MIRROR object                       configuring the system for, 1          enabling or disabling,  8-13         4-7c>         Mixed-interconnect VAXcluster     NEW_OVER files,  E-3?          information needed to install    NEW_UNDER files,  E-4nA             ,  2-7                        NML (Network Managementd=          installation questions,  3-25       Listener) object G          upgrade requirements,  5-6         enabling or disabling, 8-12a         Mixed-version cluster-I          upgrading to,  6-6 to 6-8        O______________________________o/         MODPARAMS.DAT (parameter file)    OPCOM F           ,  4-16                           stopped during an upgrade,2          entering parameters in,  5-22        7-14D          modifying,  8-9                  OpenVMS distribution mediaE          modifying values,  8-33            removing from drive, 3-20e?         Monochrome workstations, 9-3      OpenVMS library filesO  G         Motif                               choosing during an upgrade,C  2          See DECwindows Motif for             7-17D             OpenVMS VAX                   OpenVMS Management Station  :                                             checklist, F-3B         N______________________________     installing, 3-13, 7-18C         NETCONFIG.COM procedure             postupgrade tasks, 8-31rB          running after an installation    OpenVMS manuals save set9             ,  4-7                          contents, C-4n<         NETCONFIG_UPDATE.COM procedure      installing, 3-157          example,  8-11                     sizes, 3-15   E          running,  8-10                   OpenVMS optional components   C         Network                             See Optional components-H          See also DECnet for OpenVMS      OpenVMS RMS Journaling license@          requirements for an upgrade,       registering after an@             5-25                              installation,  4-3I          restriction on upgrades,  5-4      registering during an upgrade 5         Network Management Listener           ,  7-35 H          See NML object                   OpenVMS VAX distribution media8                                             loading, 3-6E                                             removing from drive, 7-27   I                                                                   Index-7  u  a              A     OpenVMS VAX license                PAK (Product Authorization -       registering after an               Key)l<          installation, 4-3              registering after an<     OpenVMS versions                       installation, 4-3E       computer support,  A-2            registering during an upgrade-1       required for upgrades,  5-7          , 7-345:     Operator logs                       registering during=       effect of upgrades on,  5-6          installation, 3-38e0     Optional components                PasswordsC       choosing,  2-10                   for default DECnet account,n/       installing on alternate disks        8-10eB          , 3-12                         for system accounts,  2-109       installing with DECW$TAILOR,         setting duringe@          3-11                                 installation, 3-28>       installing with VMSTAILOR,        forgotten,  3-44, 7-37=          3-11                           minimum length,  3-28 @       selecting,  3-12                  modifying during upgrade:       selecting during an                  procedure, 7-12;          installation, 3-11             requirements,  7-12:D       selecting during an upgrade,     Phase 1 of upgrade procedure,-          7-16                            7-12dD       sizes,  3-11                     Phase 2 of upgrade procedure,-     Optional save set                    7-26 D       contents,  C-3                   Phase 3 of upgrade procedure,-       installing,  3-12, 7-17            7-29uD       upgrading,  7-16                 Phase 4 of upgrade procedure,-     Output                               7-307D       saving from an upgrade,  5-31    Phase 5 of upgrade procedure,  -     P                                    7-32 D     _______________________________    Phase 6 of upgrade procedure,-     Page and swap files                  7-33 .       locating,  2-7                   Phase I>     Page files                          volume shadowing,  1-33       checking size,  5-17, 8-7        PHONE object,D       controlling size of,  G-6         enabling or disabling,  8-12B       modifying size,  5-17, 8-6       Postinstallation tasks, 4-1D       purged during an upgrade,         adjusting system parameters,.          7-23                              4-5C       recommended location,  5-17       backing up the system disk,l4       size required for an upgrade,        4-4, 4-15@          5-17                           configuring DECnet,  4-7C                                         creating standalone BACKUP,t.                                            4-4       Index-8V V                 D         Postinstallation tasks            Postupgrade tasks (cont'd)F           (cont'd)                          purging system files, 8-27E          customizing DECwindows             replacing SYSUAF.DAT, 8-5 @             support software,  9-1          replacing VMS$AUDIT_>          customizing the system,  4-5         SERVER.DAT,  8-5A          decompressing system               running AUTOGEN, 8-33aI             libraries,  4-10                running NET_CONFIG_UPDATE.COMn5          editing startup procedures,          ,  8-10 >             4-5                             running UETP, 8-26C          installing layered products,       running UPDATE_CLUSTER_ @             4-15                              MEMBERS.COM,  8-14B          registering licenses,  4-3         tuning the system with<          removing unwanted system             AUTOGEN,  8-33H             files,  4-14                    updating console media, 8-17<          running UETP,  4-9                 updating networkE          setting up user accounts,            configuration database, 2             4-5                               8-10B          tuning the system with             updating network proxy=             AUTOGEN,  4-16                    database,  8-15 E         Postupgrade tasks                   updating network security @          adding and removing files,           environment,  8-10A             8-27                            using VMSTAILOR, 8-27nE          backing up console media,        Preinstallation tasks,  2-6rG             8-32                            collecting information, 2-9 E          backing up system disk,  8-32      determining HSC name, 2-9 D          changing MODPARAMS.DAT,  8-9       preparing for VAXcluster@          checking system file sizes,          environments,  2-6F             8-7                             preparing tape drives, 2-8@          creating standalone BACKUP,      Preupgrade tasks,  5-1G             8-32                            analyzing and repairing theu@          customizing DECwindows               system disk,  5-16E             support,  8-30                  backing up console media,l2          decompressing system                 5-13G             libraries,  8-22 to 8-25        backing up the system disk,i2          examining command procedure          5-13D             templates,  8-8                 checking page file size,2          increasing space on the              5-17D             system disk,  8-27              configuring devices, 7-4G          modifying size of dump file,       creating standalone BACKUP, 2             8-6                               5-14I          modifying size of page file,       preparing DECnet for OpenVMS, 2             8-6                               5-24F          modifying size of swap file,       preparing the system disk,2             8-6                               5-15  I                                                                   Index-9e r                      Preupgrade tasks (cont'd) F       preventing interactive logins    R______________________________  0          , 5-23                        RebootingD       running AUTOGEN,  5-11            after an installation,  3-425       setting system parameters,        manual,  5-232E          5-19                          Recording an installation, 2-4 A       stopping queues,  5-25           Recording an upgrade, 5-31_E     Printer                            Removing unwanted system filesf0       recording upgrade on,  5-31        ,  4-148     Products (VMSINSTAL)               Required save setB       specifying for an upgrade,        transferring to the system4          7-9                               disk, 3-7.     PURGE command,  8-28               RestartA     Purging system files,  8-27         enabling automatic,  5-23a3                                        Restrictionse?     Q______________________________     for installations,  2-2 :     Queue database                      for upgrades,  5-76       creating after an upgrade,       Rights database:          4-5                            creating during an=     Queue manager                          installation, 3-302:       restoring preferred node         RIGHTSLIST.DAT file:          list, 8-4                      creating during an=     Queues                                 installation, 3-30aA       requirements for an upgrade,     RMS Journaling for OpenVMS_0          5-25                            license=       stopping batch/print,  5-25       registering during anU=       stopping before an upgrade,          installation, 3-39 <          5-25                          Rolling upgrades, 6-2B     Quorum                              effect on SYSUAF.DAT,  8-5B       See also VAXcluster quorum        effect on SYSUAF.DAT file,/       maintaining during rolling           5-16 C          upgrades, 6-7                  maintaining cluster quorum,u.     Quorum disk,  2-7                      6-7?       choosing during VAXcluster        restrictions,  6-2, 6-5 A          installation, 3-25             source drive requirement,t.     QUORUM parameter                       6-7C       setting for concurrent            upgrade procedures,  6-6 tow.          upgrades, 6-3                     6-7  
     Quotas        checked during an upgrade,
          7-14e       minimum values,  5-18        Index-10    o              @                                           Source drives (cont'd)F         S______________________________     requirement for VAXcluster  ;         Satellites nodes                      upgrade,  6-7 -          upgrade requirements,  5-6       SPDi@         Save sets                           See Software ProductB          installing on an alternate           Descriptions (SPDs).E             disk,  5-27                   STABACKIT.COM (procedure totG          location on magnetic tape,          create standalone BACKUP), 1             1-8                              5-14 ;          required location,  1-8, 2-2     Standalone BACKUP 8          tape cartridge containing,         booting, 3-2E             3-2                             booting from InfoServers, 1          transferring to the system           3-3SI             disk,  3-6                      booting from tape cartridges,S1         SCSNODE parameter, 5-20               3-2 I         SCSSYSTEMID parameter, 5-20         booting on VAX 9000 computers 4         Security                              ,  3-4?          updating after an upgrade,         creating a kit, 4-4-F             8-10                            creating after an upgrade,2         Selecting optional components,        8-32G           7-16                              creating before an upgrade,m2         Sending comments to Digital           5-14>           writers,  iii                     loading media, 3-2I         Server                              locating on distribution kit, 1          customizing the DECwindows,          3-2oD             9-2                             on multiple volumes, 3-2F         Shared memory                       upgrade requirements, 5-147          restrictions,  1-4               Startup filestI         Shutdowns                           editing after an installation 4          before an upgrade,  5-15             ,  4-5>         Site-specific command             STARTUP_P1 parameter@           procedures                        setting to MIN, 5-194          restored during an upgrade,      Swap files>             7-33, 8-8                       checking size, 8-7D         Snapshot facility                   controlling size of, G-6:          resetting the BOOT_STYLE           creating, 5-17?             parameter,  5-21                modifying size, 8-6 E         Software Product Descriptions       purged during an upgrade, 2           (SPDs)                              7-23F          location on the distribution       recommended location, 5-17A             kit,  1-9                     SWAPFILES.COM procedure F         Source drives, 1-6                  executing to change system>          definition,  7-5                     file sizes,  8-7  I                                                                  Index-11b d                 8     SWAPFILES.COM procedure            System disks, 1-6@        (cont'd)                         analyzing and repairing,/       to check or modify page file         5-16 9          size, 5-17                     backing up,  8-32 ;       to create swap file,  5-17        backing up after an B     SYCONFIG.COM procedure                 installation, 4-4, 4-15E       editing after an installation     backing up before an upgrade,s/          , 4-5                             5-13 D     SYLOGICALS.COM procedure            booting a backup copy,  5-15E       editing after an installation     booting after an installationa1          , 4-5                             , 3-41 B     SYLOGIN.COM procedure               booting after transferringA       editing after an installation        required save set, 3-8 E          , 4-5                          checking amount of free spacer3     [SYSF] directory                       on, 4-11 D       booting from during an            CLUSTER_SIZE parameter,  3-76          upgrade, 7-23, B-1             creating,  3-6E       booting from during upgrade,      customizing with DECW$TAILOR, =          7-2                               4-14, 10-12, 10-13 C       command to boot MicroVAX and      customizing with VMSTAILOR,r;          VAXstation computers from,        4-14, 8-27, 10-2pC          7-23                           dealing with limited space, 3     [SYSF] directory tree                  G-2, G-3 @       built by upgrade procedure,       disk space needed to run:          7-15                              UETP, 4-9, 8-26@       deletion of,  7-32                free space needed for an8     SYSGEN parameters                      upgrade, 5-18<       See System parameters             free space needed to@     SYSGEN utility                         decompress libraries,/       ALLOCLASS parameter,  2-7            4-11iA       configuring devices,  7-4         preparing for an upgrade, /       using to connect console,            5-15nD          8-17                           preparing for installations,.     SYSTARTUP_VMS.COM procedure            2-9E       editing after an installation     removing unwanted files from,f/          , 4-5                             4-14 C       editing to control DECnet for     required location during anm8          OpenVMS, 4-8                      upgrade, 7-318     SYSTEM account                      restoring,  1-16:       forgotten passwords,  3-44,       restrictions,  1-43          7-37                           RZ23L,  G-5 @       limits,  5-18                     space requirements,  G-3D       quotas,  5-18                     specifying volume label for,/       setting passwords,  3-28             3-10r       Index-12    i              A         System disks (cont'd)             Tape cartridge (cont'd)   I          volume shadowing restrictions      containing standalone BACKUP,r1             ,  5-7                            3-2 5         System files                      Tape drives I          modifying,  8-7                    preparing for an installationm4          purging,  8-27                       ,  2-8I         System Generation utility           selecting for an installation 4          See SYSGEN utility.                  ,  2-85         System hang, 7-36                 Target disktG         System libraries                    using backup copy for, 5-13o=          decompressing,  3-31, 8-22 to    Target drives,  1-7 ;             8-25                            definition, 7-5g5          sizes after decompressing,       TASK object_G             8-22                            enabling or disabling, 8-111  9         System parameters                 TCP/IP software   G          adjusting,  4-5                    See DEC TCP/IP Services for 5          generated by AUTOGEN feedback        OpenVMSi.             ,  5-11                       TimeE          requirements for an upgrade,       format for entering, 7-11OH             5-5, 5-19, 5-20               Time conversion service,  4-2,0         System password dictionary           8-34          restoring after an upgrade,      Time zonesE             8-29                            setting up your system tohG         System shutdowns                      compensate for,  4-2, 8-337          after an installation,  3-41     TK50 tape kitp<         System time, 4-2, 8-3               contents of, 1-8G         SYSTEST account                   Transferring save sets to thet=          setting passwords,  3-28            system disk, 3-6i         SYSTEST_CLIG accountI          disabling during an              U______________________________ G             installation,  3-28           UAF (user authorization file)   F         SYSUAF.DAT file                     effect of rolling upgrades  <          See UAF                              on,  5-16, 8-5  E                                             purged during an upgrade, 2         T______________________________       7-23  H         Tailored system disks               replacing after upgrade, 8-5C          See DECW$TAILOR utility            required location, 5-16 E          See VMSTAILOR utility            UETP (User Environment Test 5         Tailoring                            Package) E          on small system disks,  G-5        disk space needed to run, 7         Tape cartridge                        4-9, 8-26 B          containing save sets,  3-2         when to run, 4-9, 8-26  I                                                                  Index-13, 3                 A     UPDATE_CLUSTER_MEMBERS.COM         Upgrade procedure (cont'd)lC        procedure                        enabling automatic restart,g/       running,  8-14                       5-23 E     UPDATE_CONSOLE.COM procedure        enabling manual reboot,  5-23iC       running after an upgrade,         error entering device code, .          8-20                              7-9@     Upgrade and installation            files deleted by,  7-15,5        supplements                         7-29, 7-32 B       using,  2-4, 3-1                  files purged during,  7-23D     Upgrade preparation,  5-22          interrupting before Phase 1,/     Upgrade procedure,  1-15               7-10-C       automatic update of console       license requirements,  7-35 ;          media, 5-13                    loading OpenVMS VAX B       booting from console media,          distribution media, 7-5>          7-14                           loading VMS DECwindowsC       booting from [SYSF],  7-23           distribution media, 7-27nB       booting manually during,          manual reboot after,  7-35B          7-14                           manual reboot from [SYS0],/       building [SYSF] directory,           7-30l@          7-15                           merging directory trees,/       cautions and restrictions,           7-29t@          5-2                            modifying console media,/       choosing optional OpenVMS            5-23pB          components, 7-17               modifying console media toA       concurrent upgrades,  6-3            boot from [SYSF], 7-14 B       console media required,  5-9      modifying passwords,  7-126       conversion of VAXVMSSYS.PAR,      Phase 1,  7-126          7-32                           Phase 2,  7-266       correcting directory pointers     Phase 3,  7-296          , 7-30                         Phase 4,  7-306       deletion of [SYSF] directory      Phase 5,  7-326          tree, 7-32                     Phase 6,  7-33D       disk space needed for page        processing user files,  7-298          files, 5-17                    recording,  5-31<       disk space requirement,  5-18     recording logs,  5-9C       effect on accounting logs,        registering licenses,  7-34g;          5-6                            removing DECwindows C       effect on command procedures,        distribution media, 7-28r<          8-8                            removing OpenVMS VAXC       effect on layered products,          distribution media, 7-27lA          5-7                            required location of save'4       effect on MODPARAMS.DAT,  8-9        sets, 5-5@       effect on operator logs,  5-6     required location of the<                                            system disk, 7-31       Index-14    s              A         Upgrade procedure (cont'd)        VAXcluster environments 5          requirement for shared dump         (cont'd)r  I             files,  5-16                    DECwindows support componentsa8          requirements,  5-31                  for,  3-18G          restoring original dddGEN,         information required for and@             7-30                              installation,  2-6?          restoring original DEFBOO,         installing in, 3-22eD             7-30                               choosing quorum disk,5          restrictions,  1-16                     3-254H          rolling upgrades,  6-5                choosing VAXcluster type,5             adding a new CPU,  6-8               3-24uG          running AUTOGEN,  7-35                configuring the cluster, 5          security check,  7-32                   3-22tC          selecting optional components         suggested answers to6A             ,  7-16                              questions,  3-22 B          shared dump files,  5-7               supplying ALLOCLASSA          system files renamed by,                parameter,  3-25 C             7-15                            local area installatione>          using a printer to record            questions,  3-25>             output,  5-9                    Mixed-InterconnectE          VMS version requirement,  5-7        installation questions,a2          VMSINSTAL option G warning,          3-25C             5-5                             problem upgrading, 7-3669          when to use,  1-15, 2-2            types of, 2-7e  C         User authorization file             upgrade requirement fors  F          See UAF                              shared dump files,  5-16<         User files                        VAXcluster license@          processed during an upgrade,       registering after an@             7-29                              installation,  4-3A         UTC (Coordinated Universal          registering during aneA           Time),  4-2, 8-3                    installation,  3-39   I                                             registering during an upgradee5         V______________________________       ,  7-35m=         VAX computers                       requirement, 3-22d;          booting from [SYSF],  B-1 to     VAXcluster quorum I             B-8                             maintaining during an upgrade 5          OpenVMS VAX support for,  A-2        ,  7-36 F         VAXcluster environments             maintaining during rolling<          building,  4-5                       upgrades,  6-7E          CI-only installation             VAXcluster QUORUM parameter B             questions,  3-24                setting for concurrent<          cluster group numbers,  2-8          upgrades,  6-3             cluster passwords,  2-8  I                                                                  Index-15, -                 6     VAXcluster upgrades                VOTES parameterE       See Concurrent upgrades           checking for rolling upgradesi0       See Rolling upgrades                 , 6-6>     VAXft computers                     setting for concurrent8       booting from [SYSF],  B-1            upgrades, 6-3A     VAXstation computers                upgrade requirement,  6-3)1       booting from [SYS0],  7-30       VPM objectfD       booting from [SYSF],  7-23,       enabling or disabling,  8-13            B-1F     VAXVMSSYS.PAR parameter files      W______________________________  7       conversion,  7-32                WELCOME.TXT filea6     VMB.EXE                             updating,  8-83       copying to console media,        Workstationsi9          8-17                           customizing,  9-3r       VMS Performance Monitorr  F       See VPM object                   X______________________________1     VMS$AUDIT_SERVER.DAT file          Xterminals E       required location,  5-16          DECwindows support components 4     VMSINSTAL command procedure            for, 3-18        invoking for upgrade,  7-6       option G warning,  2-2     VMSTAILOR utility3#       using on a small system disk,,          G-8       using to install optional            components, 3-11, 7-16,
          10-5g"       using to remove files from a!          system disk, 4-14, 8-27, 
          10-4      Volume label       specifying during an          installation, 3-10g     Volume shadowing       phase I availablity,  1-3e"       requirements for an upgrade,
          5-24u     Volume Shadowing license       registering after an          installation, 4-3       registering during an           installation, 3-39s#       registering during an upgrade           , 7-35        Index-16                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              