                             D                 ____________________________________________________                 OpenVMS VAX                  Version 7.3 /                 Upgrade and Installation Manual     )                 Order Number: AA-QSBQD-TE                      April 2001  B                 This manual provides step-by-step instructions for?                 upgrading and installing the Compaq OpenVMS VAX !                 operating system.               C                 Revision/Update Information:  This is a new manual.   E                 Software Version:             OpenVMS VAX Version 7.3                         +                 Compaq Computer Corporation                  Houston, Texas                 F       ________________________________________________________________  (        2001 Compaq Computer Corporation  >       Compaq, VAX, VMS, and the Compaq logo Registered in U.S."       Patent and Trademark Office.  <       OpenVMS and Tru64 are trademarks of Compaq Information=       Technologies Group, L.P. in the United States and other        countries.  7       Adobe and Acrobat are trademarks of Adobe Systems        Incorporated.   8       Microsoft, Visual C++, Windows, and Windows NT are*       trademarks of Microsoft Corporation.  0       Intel is a trademark of Intel Corporation.  -       Motif is a trademark of The Open Group.   @       Java and all Java-based marks are trademarks or registered*       trademarks of Sun Microsystems, Inc.  9       All other product names mentioned herein may be the /       trademarks of their respective companies.   ?       Confidential computer software. Valid license from Compaq ?       required for possession, use, or copying. Consistent with :       FAR 12.211 and 12.212, Commercial Computer Software,=       Computer Software Documentation, and Technical Data for @       Commercial Items are licensed to the U.S. Government under+       vendor's standard commercial license.   ;       Compaq shall not be liable for technical or editorial ;       errors or omissions contained herein. The information ;       in this document is provided "as is" without warranty >       of any kind and is subject to change without notice. TheA       warranties for Compaq products are set forth in the express =       limited warranty statements accompanying such products. ;       Nothing herein should be construed as constituting an        additional warranty.  B                                                             ZK6630  >       The Compaq OpenVMS documentation set is available on CD-
       ROM.                                 > ______________________________________________________________  ?                                                        Contents       ?   Preface................................................... xv      Getting Started   ?     1.1   Important Information.........................    1-1 ?     1.1.1     Compaq TCP/IP Services for OpenVMS........    1-1 ?     1.1.2     DECnet Software...........................    1-1 8     1.1.3     DECwindows Motif for OpenVMS VAX - Minimum?               Version...................................    1-2 ?     1.1.4     MACRO32.EXE and Standalone BACKUP.........    1-2 ?     1.1.5     Layered Product Availability..............    1-2 ?     1.1.6     Restrictions..............................    1-2 ?     1.2   Key Terms.....................................    1-3 ?     1.3   Locating Files on the Distribution Media......    1-4 ?     1.3.1     On CD-ROM.................................    1-5 ?     1.3.2     On Magnetic Tape or Tape Cartridges.......    1-6 ?     1.3.3     DECamds Files.............................    1-6 ?     1.3.4     Software Product Descriptions (SPDs)......    1-6 ?     1.4   What Happens During an Installation...........    1-7 ?     1.4.1     When to Perform an Installation...........    1-8 )     1.4.2     How to Use the Installation ?               Documentation.............................    1-8 ?     1.5   What Happens During an Upgrade................   1-10 ?     1.5.1     When to Perform an Upgrade................   1-11 ?     1.5.2     How to Use the Upgrade Documentation......   1-11 ?     1.6   What to Do Next...............................   1-11                 ?                                                             iii                    8 2  Preparing to Install the OpenVMS VAX Operating System  B       2.1   Cautions and Restrictions.....................     2-1B       2.1.1     Cautions..................................     2-1B       2.1.2     Restrictions..............................     2-2B       2.2   Examining Software and Hardware Components....     2-2B       2.2.1     Hardware Components.......................     2-3B       2.2.2     Software Components.......................     2-3B       2.3   Preparing for an Installation.................     2-4B       2.3.1     Preparing for a VAXcluster Environment....     2-4B       2.3.2     Preparing Tape and Disk Drives............     2-6/       2.3.3     Information You Need During the B                 Installation..............................     2-7B       2.4   Preinstallation Checklist.....................    2-12  . 3  Installing the OpenVMS VAX Operating System  B       3.1   Booting Standalone BACKUP.....................     3-1B       3.1.1     Booting from Tape Cartridge...............     3-2B       3.1.2     Booting from the InfoServer...............     3-2B       3.1.3     Booting from the CD-ROM...................     3-5B       3.2   Creating the System Disk......................     3-6B       3.2.1     Determining Device Names..................     3-6B       3.2.2     Loading Distribution Media................     3-74       3.2.3     Transferring VMS073.B to Your SystemB                 Disk......................................     3-7B       3.2.4     Booting the New System Disk...............     3-9B       3.2.5     Specifying the Volume Label...............    3-11B       3.2.6     Specifying the Source Drive...............    3-12B       3.2.7     Selecting Optional OpenVMS Components.....    3-13B       3.2.7.1     OpenVMS Library Files...................    3-14B       3.2.7.2     OpenVMS Optional Files..................    3-14B       3.2.7.3     Help Message Files......................    3-14B       3.2.7.4     OpenVMS Management Station Files........    3-15B       3.2.8     Choosing DECwindows Support Options.......    3-16B       3.2.9     Installing Networking Products............    3-19B       3.2.10    Verifying Your Choices....................    3-20B       3.2.11    Installing OpenVMS Options................    3-20B       3.2.11.1    Compact Disc............................    3-20B       3.2.11.2    Magnetic Tape and Tape Cartridge........    3-20B       3.2.12    Installing DECwindows Support Software....    3-216       3.3   Installing DECnet Phase IV for OpenVMS VAXB             Software......................................    3-22B       3.4   Configuring a Cluster.........................    3-23   iv                   E           3.5   Selecting the Default Windowing System........   3-23 E           3.6   Setting Passwords ............................   3-24 E           3.7   Entering SCSNODE and SCSSYSTEMID Parameters...   3-25 E           3.8   Postinstallation Tasks Described..............   3-26 E           3.9   Registering Licenses..........................   3-27 E           3.9.1     Types of OpenVMS VAX Licenses.............   3-28 E           3.9.2     How to Register OpenVMS VAX Licenses......   3-32 E           3.9.3     Using the Licensing Procedure.............   3-32 5           3.9.4     How to Register System Integrated E                     Products..................................   3-33 E           3.9.5     How to Register DECnet Products...........   3-34 E           3.10  Updating Time Zone Information................   3-34 =           3.11  Installing Compaq DECnet-Plus for OpenVMS VAX E                 Software......................................   3-36 E           3.12  Running AUTOGEN...............................   3-38 E           3.12.1    Automatic Reboot after AUTOGEN............   3-39_E           3.12.2    Manual Reboot after AUTOGEN...............   3-39 >           3.13  Logging in to the SYSTEM Account by Means of aE                 Character Cell Terminal.......................   3-40 >           3.14  Logging in to the SYSTEM Account by Means of aE                 Workstation...................................   3-41 E           3.15  What to Do Next...............................   3-41i  8     4  After Installing the OpenVMS VAX Operating System  E           4.1   Verifying System Time.........................    4-2 E           4.2   Registering Your Licenses.....................    4-3 E           4.3   Backing Up Your System Disk...................    4-3_E           4.4   Customizing the System........................    4-4r3           4.5   Configuring and Starting NetworkinggE                 Software......................................    4-5ME           4.5.1     Configuring Your System...................    4-6oE           4.5.2     Editing SYSTARTUP_VMS.....................    4-6bE           4.6   Testing the System with UETP..................    4-7 E           4.7   Decompressing the System Libraries............    4-7rE           4.7.1     Determining Disk Space....................    4-7pE           4.7.2     Methods of Using LIBDECOMP.COM............    4-8aE           4.7.3     Responding to LIBDECOMP.COM Prompts.......    4-9sE           4.7.4     Using LIBDECOMP.COM Interactively.........    4-9eE           4.7.5     Using LIBDECOMP.COM in Batch..............   4-10 E           4.8   Adding and Removing Operating System Files....   4-10eE           4.9   Installing Layered Products...................   4-112E           4.10  Backing Up the Customized System Disk.........   4-11o    E                                                                     vo e  S              B       4.11  Running AUTOGEN...............................    4-11B       4.12  Modifying Parameters..........................    4-12B       4.13  Postinstallation Checklist....................    4-13  4 5  Before Upgrading the OpenVMS VAX Operating System  B       5.1   Cautions and Restrictions.....................     5-1B       5.1.1     License Requirements......................     5-2B       5.1.2     DECset Version 11 Debugger................     5-2B       5.1.3     Customized Security Environment...........     5-3B       5.1.4     Operator and Accounting Logs..............     5-3B       5.1.5     Special Testing and Debugging Files.......     5-4B       5.1.6     Cluster Considerations....................     5-4B       5.1.7     Save Set Location.........................     5-5B       5.1.8     System Disk Cautions......................     5-5B       5.1.9     AUTOGEN Feedback Data.....................     5-6B       5.1.10    OpenVMS VAX Version Requirements..........     5-68       5.1.11    DECwindows Motif for OpenVMS VAX VersionB                 Requirements..............................     5-6B       5.1.12    Shared System Dump Files..................     5-6B       5.1.13    Layered Products..........................     5-7B       5.2   Preparing to Upgrade..........................     5-7B       5.2.1     Hardware Components.......................     5-7B       5.2.2     Software Components.......................     5-8B       5.3   Examining AUTOGEN Feedback Data...............     5-8B       5.3.1     Valid Feedback Data.......................     5-8B       5.3.2     How to Test Feedback Data.................     5-8B       5.4   Backing Up the System Disk....................     5-9B       5.4.1     How to Back Up the System Disk............     5-9B       5.4.2     How to Back Up Console Media..............    5-10B       5.5   Preparing the System Disk.....................    5-11B       5.5.1     Create a Nonshadowed System Disk..........    5-113       5.5.2     Boot the Backup Copy of Your System.B                 Disk......................................    5-119       5.5.3     Copy UAF and Auditing Files to the SystemeB                 Disk......................................    5-11B       5.5.4     Rename the System Dump File...............    5-12B       5.5.5     Analyze the System Disk...................    5-12B       5.5.6     Check Page and Swap Files.................    5-12B       5.5.7     Check for Free Blocks.....................    5-13B       5.5.8     Check Quotas and Limits...................    5-14B       5.5.9     Set System Parameters.....................    5-15B       5.5.10    Check AGEN$INCLUDE Files..................    5-17     vi e  d              5           5.5.11    Add Modified System Parameters to.E                     MODPARAMS.DAT.............................   5-17.E           5.6   Preparing the System..........................   5-18.E           5.6.1     Enable Auto Restart or Manual Reboot......   5-18rE           5.6.2     Shut Down and Reboot the System...........   5-18.E           5.6.3     Prevent Interactive Logins................   5-18 E           5.6.4     Check for DECnet for OpenVMS..............   5-18 E           5.6.5     Check for Volume Shadowing................   5-19nE           5.6.6     Stop Queues...............................   5-20CE           5.7   Gathering Information for the Upgrade.........   5-20tE           5.8   Preupgrade Checklist..........................   5-24e  7     6  Preparing to Upgrade in a VAXcluster EnvironmentC  E           6.1   Mixed-Version Support.........................    6-1.E           6.2   Types of Upgrades.............................    6-3.E           6.2.1     Concurrent Upgrades.......................    6-3.E           6.2.2     Rolling Upgrades..........................    6-4mE           6.3   Concurrent Upgrade............................    6-4 E           6.3.1     How a Concurrent Upgrade Works............    6-4 E           6.3.2     Preparing for a Concurrent Upgrade........    6-4.E           6.4   Rolling Upgrade...............................    6-6 E           6.4.1     How a Rolling Upgrade Works...............    6-6 E           6.4.2     Notes and Restrictions....................    6-6nE           6.4.3     Preparing for a Rolling Upgrade...........    6-7s;           6.5   Adding an OpenVMS VAX Version 7.3 SupportedpE                 CPU...........................................    6-9g  1     7  Upgrading the OpenVMS VAX Operating System.  E           7.1   Preparing to Boot from [SYSF].................    7-2 E           7.1.1     Modifying Boot Command Procedures.........    7-2t2           7.1.2     VAX 8200, 8250, 8300, and 8350E                     Computers.................................    7-3.E           7.1.3     Configuring Devices.......................    7-32E           7.2   Performing the Upgrade........................    7-3tE           7.2.1     Loading Distribution Media................    7-4.E           7.2.2     Upgrading from the InfoServer.............    7-4.E           7.2.3     Starting VMSINSTAL........................    7-5.E           7.2.4     Backing Up the System Disk................    7-6.E           7.2.5     Specifying the Source Drive...............    7-7.E           7.2.6     Entering the Product Name.................    7-8.E           7.2.7     Mounting the First Volume.................    7-8.    E                                                                   vii     e              B       7.2.8     Monitoring Messages from VMSINSTAL........     7-9B       7.2.9     Verifying the Date and Time...............     7-9B       7.3   Upgrade Phase 1...............................     7-9B       7.3.1     Specifying the Type of Upgrade............    7-10B       7.3.2     SYSTEST and FIELD Account Creation........    7-10B       7.3.3     Entering Passwords........................    7-10B       7.3.4     Choosing the Boot Method..................    7-12B       7.3.5     File Cleanup..............................    7-13B       7.3.6     Selecting Optional OpenVMS Components.....    7-14B       7.3.6.1     OpenVMS Library Files...................    7-15B       7.3.6.2     OpenVMS Optional Files..................    7-15B       7.3.6.3     Help Message Files......................    7-15B       7.3.6.4     OpenVMS Management Station Files........    7-16B       7.3.7     Choosing DECwindows Support Options.......    7-17B       7.3.8     Upgrading Networking Products.............    7-20B       7.3.9     Verifying Your Choices....................    7-21B       7.3.10    Shutting Down Your System.................    7-22B       7.3.11    Automatic System Reboot...................    7-23B       7.3.12    Manual System Reboot......................    7-23B       7.3.13    Verifying System Time.....................    7-24B       7.4   Upgrade Phase 2...............................    7-24:       7.4.1     Mounting Additional Magnetic Tape and TapeB                 Cartridge Volumes.........................    7-25B       7.5   Upgrade Phase 3...............................    7-25B       7.6   Upgrade Phase 4...............................    7-26B       7.6.1     How to Proceed............................    7-27B       7.7   Upgrade Phase 5...............................    7-28B       7.8   Upgrade Phase 6...............................    7-28B       7.8.1     Restoring System Files....................    7-28B       7.8.2     Updating Time Zone Information............    7-299       7.8.3     Installing Compaq DECnet-Plus for OpenVMSDB                 VAX.......................................    7-30B       7.8.4     Running AUTOGEN...........................    7-32B       7.8.5     Shutting Down the System..................    7-32B       7.8.6     Booting Voting Nodes......................    7-33B       7.8.7     Executing STARTUP.........................    7-339       7.8.8     Logging in to the SYSTEM Account by Means B                 of a Character Cell Terminal..............    7-349       7.8.9     Logging in to the SYSTEM Account by Means.B                 of a Workstation..........................    7-34B       7.9   What to Do Next...............................    7-34         viii .  .              7     8  After Upgrading the OpenVMS VAX Operating System   E           8.1   Verifying System Time.........................    8-2.E           8.2   Restoring the Preferred Node List.............    8-2 (           8.3   Replacing SYSUAF.DAT andE                 VMS$AUDIT_SERVER.DAT..........................    8-3 E           8.4   Examining AGEN$PARAMS.REPORT..................    8-35E           8.5   Checking the Size of System Files.............    8-4 E           8.6   Examining Your Command Procedures.............    8-4 E           8.7   Changing MODPARAMS.DAT........................    8-5.E           8.8   Updating Your Console Media...................    8-5 :           8.9   VAX 8530, 8550, 8810 (8700), 8820-N (8800)E                 Computers.....................................    8-5.;           8.9.1     VAX-11/730, 750, 780, 785 and VAX 8200, E                     8250, 8300, 8350, 8600, 8650 Computers....    8-7 E           8.9.2     VAX 9000 Computers........................    8-9eE           8.10  Decompressing the System Libraries............    8-9oE           8.10.1    How to Decompress Libraries...............   8-10mE           8.11  Testing the System with UETP..................   8-11eE           8.12  Increasing Free Space on the System Disk......   8-12a7           8.12.1    Running the ANALYZE /DISK_STRUCTUREdE                     Utility...................................   8-12eE           8.12.2    Using VMSTAILOR and DECW$TAILOR...........   8-12 E           8.12.3    Purging System Files......................   8-13sE           8.13  Restoring Your System Password Dictionary.....   8-13dE           8.14  Customizing DECwindows Support Software.......   8-14.7           8.15  Preparing to Use the OpenVMS ManagementdE                 Station.......................................   8-14 E           8.16  Installing Layered Products...................   8-15.E           8.17  Backing Up the System Disk....................   8-15 E           8.18  Running AUTOGEN...............................   8-16 E           8.19  Postupgrade Checklist.........................   8-17.  .     9  Customizing DECwindows Support Software  E           9.1   Customizing the Server Startup................    9-12E           9.1.1     Assumptions...............................    9-2 E           9.1.2     How to Override Incorrect Assumptions.....    9-2 E           9.2   Using Compaq TCP/IP Services for OpenVMS......    9-8.E           9.3   Using Other Transports with DECwindows........    9-9dE           9.3.1     Writing a Transport Interface.............    9-9 6           9.3.2     Installing the Transport InterfaceE                     Image.....................................    9-9.E           9.4   Using the Example Transport...................   9-10t  E                                                                    ix. .  5              # 10  Using VMSTAILOR and DECW$TAILORs  B       10.1  Using VMSTAILOR...............................    10-1B       10.1.1    How VMSTAILOR Works.......................    10-1B       10.1.2    Removing OpenVMS VAX Files................    10-3B       10.1.3    Adding OpenVMS VAX Files..................    10-5B       10.1.4    Sample Session............................    10-6B       10.2  Using DECW$TAILOR.............................    10-9B       10.2.1    How DECW$TAILOR Works.....................   10-10B       10.2.2    DECwindows Files You Can Tailor...........   10-10B       10.2.3    Removing DECwindows Files.................   10-11B       10.2.4    Adding DECwindows Files...................   10-12B       10.2.5    Sample Session............................   10-14  # A  Multiversion VAX Upgrade Process.  B       A.1   Determine Your Path...........................     A-1B       A.2   Multiversion Upgrade Procedure................     A-2B       A.2.1     Before You Begin the Upgrade..............     A-2B       A.2.2     Intermediate Upgrade......................     A-3B       A.2.3     Final Upgrade.............................     A-41       A.3   Specific Layered Product and Firmware B             Information...................................     A-4B       A.3.1     Layered Products..........................     A-4    B  License Management Supplement  B       B.1   Registering Your Licenses.....................     B-1B       B.1.1     When to Register..........................     B-1B       B.1.2     How to Register...........................     B-24       B.2   Using the License Unit Requirement TableB             (LURT)........................................     B-4B       B.3   License Management Facility (LMF) Notes.......    B-11B       B.4   Volume Shadowing for OpenVMS License..........    B-12B       B.4.1     When to Register..........................    B-125       B.4.2     Volume Shadowing Software Phase I and B                 Phase II..................................    B-12B       B.4.3     Types of Licenses.........................    B-13B       B.5   Other System Integrated Product Licenses......    B-13             xe u                 ,     C  Booting from [SYSF] During an Upgrade  E           C.1   Booting Procedures............................    C-1eE           C.1.1     MicroVAX and VAXstation Computers.........    C-1 >           C.1.2     VAX 8530, 8550, 8810 (8700), 8820-N (8800)E                     Computers.................................    C-2 E           C.1.3     VAX 8820, 8830, and 8840 Computers........    C-2 :           C.1.4     VAX-11/750, 8200, 8250, 8300, and 8350E                     Computers.................................    C-2 >           C.1.5     VAX-11/730, 11/780, 11/785, 8600, and 8650E                     Computers.................................    C-4 E           C.1.6     VAX 6000 Series...........................    C-6 E           C.1.7     VAX 9000 Series...........................    C-8.  &     D  OpenVMS VAX Save Set Subclasses  E           D.1   Save Set C Subclasses.........................    D-1.E           D.2   Save Set D Subclasses.........................    D-3 E           D.3   Save Set E Subclasses.........................    D-35E           D.4   Save Set F Subclasses.........................    D-3   5     E  DECwindows Display Server and Fonts Components   E           E.1   Table of Components...........................    E-10  #     F  NEW_OVER and NEW_UNDER Filess  E           F.1   Where Files Are Installed.....................    F-1.E           F.1.1     NEW_OVER Files............................    F-2.E           F.1.2     NEW_UNDER Files...........................    F-3.E           F.1.3     Site-Specific Files.......................    F-4.  2     G  Preparing to Use OpenVMS Management Station  E           G.1   Preparing Your OpenVMS System.................    G-1p>           G.1.1     Setting Up in a Mixed-Architecture ClusterE                     Environment...............................    G-2.E           G.1.2     Start the Server on Other Nodes...........    G-4 E           G.1.3     Error Log Information.....................    G-4-E           G.1.4     Update the Printer and Storage Database...    G-4 E           G.1.5     Edit the System Files.....................    G-5 4           G.1.6     Allow OpenVMS Management Station6                     to Control the Printer and StorageE                     Environment...............................    G-7   E                                                                    xi-                   6       G.1.7     Keeping Your Printer Environment Up toB                 Date......................................     G-7B       G.1.7.1     When is the Database Updated?...........     G-84       G.1.7.2     Do You Need to Run TNT$UTILITY.COMB                   Manually?...............................     G-98       G.1.7.3     Are There Any Requirements for RunningB                   TNT$UTILITY.COM?........................     G-96       G.1.8     Keeping Your Storage Environment Up toB                 Date......................................    G-10B       G.1.9     Enabling Disk Quotas......................    G-10B       G.1.10    Caching Storage Configuration Data........    G-10B       G.1.11    Running Third-Party TCP/IP Stacks.........    G-11B       G.1.12    Determining and Reporting Problems........    G-117       G.1.13    Removing the OpenVMS Management StationDB                 Server....................................    G-12B       G.2   Preparing Your PC.............................    G-12B       G.2.1     Required Memory and Disk Space............    G-12B       G.2.2     Distribution Files........................    G-13B       G.2.3     Required Software.........................    G-13B       G.2.4     Time Required for Installation............    G-13B       G.2.5     Copy the Client File to the PC............    G-13B       G.2.6     Installation Directory....................    G-13B       G.2.7     Installation Procedure....................    G-14B       G.2.8     Recovering from Errors....................    G-148       G.3   After Installing the Client Software on YourB             PC............................................    G-14B       G.4   Defining TCP/IP Nodes.........................    G-153       G.5   Uninstalling Version 2.1 of the OpenVMS.B             Management Station Client.....................    G-15B       G.6   Uninstalling OpenVMS Management Station.......    G-153       G.7   Getting Started with OpenVMS Management.B             Station.......................................    G-16   H  Small Capacity System Disks  B       H.1   Limited Space Support.........................     H-1B       H.1.1     Limited Space Support Option..............     H-1B       H.1.2     Configurations Affected...................     H-2B       H.1.3     Dealing with a Small System Disk..........     H-3B       H.2   Tailoring Considerations......................     H-3B       H.2.1     Configuration Goals.......................     H-47       H.2.2     Controlling the Size of Dump, Page, and.B                 Swap Files................................     H-4     xii. .  .              E           H.2.3     Make a Backup Copy of Your System Disk....    H-5 E           H.2.4     Analyze the System Disk...................    H-6tE           H.2.5     Tailoring Options.........................    H-6 ;           H.3   Installing OpenVMS VAX and DECwindows Motif E                 for OpenVMS VAX...............................    H-7 E           H.3.1     Installing OpenVMS VAX Version 7.3........    H-7 ;           H.3.2     Installing DECwindows Motif for OpenVMS E                     VAX ......................................    H-8 >           H.4   Upgrading OpenVMS VAX and DECwindows Motif forE                 OpenVMS VAX ..................................    H-9 E           H.4.1     Upgrading to OpenVMS VAX Version 7.3......    H-9 4           H.5   Managing Single or Small System DiskE                 Systems.......................................   H-10 E           H.5.1     System Dump File..........................   H-10 E           H.5.2     Using PAGEFILE.SYS for the Dump File......   H-11 E           H.5.3     Decompressing Libraries...................   H-121E           H.5.4     Disabling Log File Creation...............   H-12 7           H.5.5     Accessing Example and Documentation E                     Files.....................................   H-140E           H.6   Managing Multiple Disk Systems................   H-142E           H.6.1     Alternate Page and Swap Files.............   H-14 E           H.6.2     Copying Dump Files........................   H-14iE           H.6.3     Offloading System Logs and Files..........   H-15SE           H.6.4     Offloading Nonessential Files.............   H-15d       Glossary    	     Indexm         Examples  E           10-1      Sample VMSTAILOR Session..................   10-6e  E           10-2      Sample DECW$TAILOR Session................  10-14.                  E                                                                  xiii     .               Figures.  0       1-1       Documentation Used to Perform anB                 Installation..............................     1-9  0       1-2       Documentation Used to Perform anB                 Upgrade...................................    1-11   Tables  B       1         Frequently Abbreviated Product Names......   xviii  *       2-1       VAXcluster Information forB                 Installations.............................     2-4  B       4-1       Sizes of Decompressed System Libraries....     4-7  7       6-1       VAX and Alpha OpenVMS Cluster Warranted.B                 and Migration Support.....................     6-2  B       8-1       Sizes of Decompressed System Libraries....     8-9  B       9-1       DECwindows Keymap.........................     9-4  B       A-1       OpenVMS VAX Upgrade Version Matrix........     A-1  :       B-1       First VMS or OpenVMS Version That SupportsB                 VAX Computers.............................     B-2  B       B-2       License Unit Requirement Table (LURT).....     B-5  3       E-1       DECwindows Display Server and FontsoB                 Components................................     E-1                         xiv.    -                        E     _________________________________________________________________   E                                                               Preface.           Intended Audience.  <           This manual is intended for anyone responsible forB           installing or upgrading the Compaq OpenVMS VAX operatingE           system and for the startup, shutdown, and backup operations.:           required on VAX computers running this software.       When to Use This Manual   D           If you received factory-installed software (FIS) with yourA           VAX computer, refer to that user documentation to start.?           up your system for the first time. Use this manual if B           you need to install or upgrade the OpenVMS VAX operating<           system software yourself or if you need to performC           certain startup, shutdown, or backup operations. When theaC           instructions in this manual direct you to do so, refer to A           the upgrade and installation supplement for informationC(           specific to your VAX computer.       Document Structure  .           This manual is organized as follows:  D           o  Chapter 1, Getting Started, provides an overview of theC              upgrade and installation procedures. It describes whatVE              happens during an installation or an upgrade, lists someNA              changes and restrictions you should be aware of, andi9              refers you to the appropriate documentation.P  <           o  Chapter 2, Preparing to Install the OpenVMS VAXC              Operating System, describes the tasks you must perform 4              before installing the operating system.    C                                                                  xv  .                 @       o  Chapter 3, Installing the OpenVMS VAX Operating System,;          describes how to install the operating system on a.1          VAXcluster or a standalone VAX computer.   >       o  Chapter 4, After Installing the OpenVMS VAX Operating;          System, describes the tasks you must perform afteri)          installing the operating system.t  >       o  Chapter 5, Before Upgrading the OpenVMS VAX Operating<          System, describes how to prepare your system for an          upgrade.   8       o  Chapter 6, Preparing to Upgrade in a VAXcluster9          Environment, contains additional information for.,          upgrading a VAXcluster environment.  ?       o  Chapter 7, Upgrading the OpenVMS VAX Operating System, <          describes how to upgrade a standalone VAX computer.  =       o  Chapter 8, After Upgrading the OpenVMS VAX Operating.;          System, describes the tasks you must perform after (          upgrading the operating system.  <       o  Chapter 9, Customizing DECwindows Support Software,=          describes how to customize DECwindows device support           software.  ?       o  Chapter 10, Using VMSTAILOR and DECW$TAILOR, describes >          how to use VMSTAILOR and DECW$TAILOR to add or remove#          optional OpenVMS software.k  ?       o  Appendix A, Multiversion VAX Upgrade Process, providese>          a quick method of applying multiple upgrades to a VAX          system.  <       o  Appendix B, License Management Supplement, contains>          supplementary information about registering licenses.  ;       o  Appendix C, Booting from [SYSF] During an Upgrade, ?          describes how to boot from the [SYSF] directory on the.*          different types of VAX computers.  ?       o  Appendix D, OpenVMS VAX Save Set Subclasses, lists the ?          subclasses in the OpenVMS VAX optional save sets C, D,           E, and F.  8       o  Appendix E, DECwindows Display Server and Fonts=          Components, lists DECwindows display server and font.          files..   xvi4                   B           o  Appendix F, NEW_OVER and NEW_UNDER Files, lists filesB              installed either over or under the version numbers of.              existing files during an upgrade.  E           o  Appendix G, Preparing to Use OpenVMS Management Station,nE              describes how to prepare your OpenVMS system and your PCiD              to run the OpenVMS Management Station server and client              software.  ?           o  Appendix H, Small Capacity System Disks, describes >              methods for managing small capacity system disks,C              including some specific recommendations for installing.B              or upgrading to the OpenVMS VAX Version 7.3 operatingD              system and the DECwindows Motif for OpenVMS VAX Version#              1.2-3 layered product..  @           o  The Glossary defines key terms used in this manual.       Related Documentso  E           The following documents contain information associated with.0           performing an upgrade or installation:  6           o  All cover letters included with your kit.  A           o  The upgrade and installation supplement for your VAX B              provides supplemental information necessary during anD              installation or upgrade, such as booting the system and&              determining device names.  E           o  The OpenVMS Version 7.3 Release Notes provides importantO<              supplementary information about the OpenVMS VAX              operating system.  ?           o  OpenVMS Version 7.3 New Features and Documentation.E              Overview describes new software features for the OpenVMSn.              VAX Version 7.3 operating system.  A           o  OpenVMS Cluster Systems describes the procedures fornA              establishing and managing VAXcluster configurations..  C           o  The following Compaq networking software documents (ifXE              you plan to install and configure Compaq DECnet-Plus forsD              OpenVMS VAX, DECnet Phase IV for OpenVMS VAX, or Compaq*              TCP/IP Services for OpenVMS):  >              -  DECnet-Plus for OpenVMS Installation and Basic                 Configuration.  G                                                                    xvii. H  1              2          -  DECnet for OpenVMS Guide to Networking  ?          -  Compaq TCP/IP Services for OpenVMS Installation and              Configuration.  @          Documentation for the Compaq networking products listed?          above are included on the OpenVMS Online Documentation 9          CD-ROM. Hardcopy documentation must be purchased           separately.  ?       o  The OpenVMS License Management Utility Manual providesa?          information about registering and managing licenses on           an OpenVMS VAX system..  @       o  The OpenVMS Guide to System Security describes security?          features provided by the OpenVMS VAX operating system, +          including criteria for C2 systems.L  ;       o  The OpenVMS System Manager's Manual provides task- ?          oriented information about managing an OpenVMS system, >          including how to use the VMSINSTAL command procedure.  ?       o  The OpenVMS DCL Dictionary provides detailed reference.?          information and examples for all OpenVMS DCL commands.n  :       o  The OpenVMS System Management Utilities Reference>          Manual: M-Z provides complete information about using=          the POLYCENTER Software Installation utility PRODUCTn          command.   =       o  The hardware manuals supplied with your VAX computer <          provide detailed information about system hardware.  >       For additional information about Compaq OpenVMS products>       and services, access the Compaq website at the following       location:   #       http://www.openvms.compaq.com    Reader's Comments   ?       Compaq welcomes your comments on this manual. Please send 4       comments to either of the following addresses:  '       Internet    openvmsdoc@compaq.comr   xviii  p  s                1           Mail        Compaq Computer Corporation2:                       OSSG Documentation Group, ZKO3-4/U08(                       110 Spit Brook Rd.+                       Nashua, NH 03062-2698p                                                                                D                                                                  xix _  _              % How To Order Additional Documentation   7       Use the following World Wide Web address to orderd       additional documentation:n  #       http://www.openvms.compaq.comf  >       If you need help deciding which documentation best meets$       your needs, call 800-282-6672.   Conventions   A       In this manual, Compaq software products are often referredhA       to by their abbreviated names. Some of these are shown (forc       reference) in Table 1.  A       Table_1__Frequently_Abbreviated_Product_Names______________n  A       Abbreviated_Name______Full_Name____________________________i  :       Cluster,              Compaq VMScluster Software for#       VMS cluster,          OpenVMSs       OpenVMS clustery  ?       DECwindows,           Compaq DECwindows Motif for OpenVMSo       Decwindows Motif  >       DECnet-Plus           Compaq DECnet-Plus for OpenVMS VAX  ;       OpenVMS               Compaq OpenVMS operating systemt  :       VAX cluster           Compaq VAXcluster Software forA       ______________________OpenVMS______________________________   <       This manual often refers to hardware products by their=       abbreviated names. For example, the VAX 8200, VAX 8250,s=       VAX 8300, and VAX 8350 computers are referred to as thed?       VAX 8200, 8250, 8300, 8350. The MicroVAX 2000 computer isb2       referred to as the MicroVAX 2000, and so on.  =       The following conventions are also used in this manual:I  ?       Ctrl/x           A sequence such as Ctrl/x indicates thate>                        you must hold down the key labeled Ctrl@                        while you press another key or a pointing%                        device button.    xx                     B           PF1 x            A sequence such as PF1 x indicates thatC                            you must first press and release the keynA                            labeled PF1 and then press and releaseSC                            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.)  E                            In the HTML version of this document, this A                            convention appears as brackets, ratherd&                            than a box.  <            . . .           A horizontal ellipsis in examples9                            indicates one of the followingn)                            possibilities:u  @                            o  Additional optional arguments in a:                               statement have been omitted.  @                            o  The preceding item or items can be9                               repeated one or more times.D  E                            o  Additional parameters, values, or othera9                               information can be entered.   E           .                A vertical ellipsis indicates the omissioniB           .                of items from a code example or command@           .                format; the items are omitted becauseD                            they are not important to the topic being%                            discussed.n  :           ( )              In command format descriptions,E                            parentheses indicate that you must enclose C                            the options in parentheses if you chooses)                            more than one.s  C           [ ]              In command format descriptions, bracketsa>                            indicate optional elements. You canC                            choose one, none, or all of the options. B                            (Brackets are not optional, however, in?                            the syntax of a directory name in an ?                            OpenVMS file specification or in thepA                            syntax of a substring specification in 4                            an assignment statement.)  E                                                                   xxit                     =       { }              In command format descriptions, bracesi;                        indicate required elements; you must 8                        choose one of the options listed.  5       bold text        This text style represents theV=                        introduction of a new term or the namenA                        of an argument, an attribute, or a reason.u  >                        In the HTML version of this Conventions?                        table, this convention appears as italice                        text.  6       italic text      Italic text indicates important6                        information, complete titles of?                        manuals, or variables. Variables includey?                        information that varies in system outputy:                        (Internal error number), in command=                        lines (/PRODUCER=name), and in command >                        parameters in text (where dd represents@                        the predefined code for the device type).  >       UPPERCASE TEXT   Uppercase text indicates a command, the@                        name of a routine, the name of a file, or?                        the abbreviation for a system privilege.i  A       Monospace text   Monospace type indicates code examples andr3                        interactive screen displays.n  ?                        In the C programming language, monospaceg<                        type in text identifies the following7                        elements: keywords, the names of @                        independently compiled external functions7                        and files, syntax summaries, and =                        references to variables or identifiers 0                        introduced in an example.  >       -                A hyphen at the end of a command format>                        description, command line, or code line>                        indicates that the command or statement7                        continues on the following line.m  <       numbers          All numbers in text are assumed to beA                        decimal unless otherwise noted. Nondecimalt@                        radixes - binary, octal, or hexadecimal -0                        are explicitly indicated.   xxii f  a                    E                                                                     1 E     _________________________________________________________________a  E                                                       Getting Startedc    E           This chapter provides a general description of what happensoC           during the installation and upgrade procedures, including C           information you should know before you install or upgraderA           to the Compaq OpenVMS VAX Version 7.3 operating system.c  9           This chapter also describes the contents of them>           distribution kit, tells you whether you should do an;           installation or an upgrade, and refers you to thet$           appropriate documentation.       1.1 Important Information   C           Before you install or upgrade to OpenVMS VAX Version 7.3,V1           review the information in this section.   ,     1.1.1 Compaq TCP/IP Services for OpenVMS  E           Compaq TCP/IP Services for OpenVMS Version 5.1 is availableC>           with either OpenVMS Alpha or OpenVMS VAX Version 7.3           operating system.e  =           If you are using previous versions of Compaq TCP/IPaC           Services for OpenVMS, Compaq strongly recommends that youeA           upgrade to TCP/IP Version 5.1. Refer to the OpenVMS and :           TCP/IP release notes for additional information.       1.1.2 DECnet SoftwareS  ;           From the OpenVMS VAX Version 7.3 operating systempE           installation menu, you can choose either the Compaq DECnet- A           Plus for OpenVMS VAX or DECnet Phase IV for OpenVMS VAX E           networking software. Both DECnet products cannot run at the_E           same time on your system. You must choose to install one or            the other.    E                                                   Getting Started 1-1w o  v       Getting Started  1.1 Important Informationh    =       If you install or reinstall DECnet Phase IV for OpenVMS 9       VAX, support is only available under Compaq's Priord@       Version Support Program. Contact your local Compaq support0       representative for additional information.  ;       Documentation for DECnet Phase IV for OpenVMS VAX and_;       Compaq DECnet-Plus for OpenVMS VAX is included on the_A       OpenVMS Online Documentation CD-ROM. Hardcopy documentatione?       for these products must be purchased separately. For moreMA       information about Compaq DECnet-Plus for OpenVMS VAX, refero>       to the DECnet-Plus for OpenVMS Release Notes and DECnet-<       Plus for OpenVMS Installation and Basic Configuration.  9 1.1.3  DECwindows Motif for OpenVMS VAX - Minimum Version   @       For OpenVMS VAX Version 7.3, the minimum supported version3       of DECwindows Motif for OpenVMS VAX is 1.2-3.m  ( 1.1.4  MACRO32.EXE and Standalone BACKUP  =       To build standalone BACKUP onto tape, you must have the0>       image MACRO32.EXE on your system disk. Do not tailor off=       (remove) the Macro libraries before building standaloner       BACKUP onto tape.s  # 1.1.5  Layered Product Availability   @       The most current information about layered product support1       is available online. Use the following URL:t  2            http://www.compaq.com/software/products  =       If you do not have access to the Internet, you can findy<       the operating system support information on any of the=       quarterly Software Products Libraries, in the followingu       file:n  .            [README]SW_COMPAT_MATRIX.PS  (.TXT)   1.1.6  Restrictions   7       Restrictions for OpenVMS VAX Version 7.3 include:r  ?       o  The minimum memory requirement for OpenVMS VAX Versioni8          7.3 is 4 megabytes. Additional components, such:          as DECnet for OpenVMS, Compaq TCP/IP Services for>          OpenVMS, or VAXcluster, require more memory to ensure"          satisfactory performance.  2       o  The MA780 shared memory is not supported.   1-2  Getting Started           E                                                       Getting StartedoE                                             1.1 Important Information     E           o  You cannot install or upgrade to the OpenVMS VAX Version D              7.3 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/782   D              System disks  RK07, RL02, RC25, RD32, RD51, RD52, RD53,0                            RZ22, RZ23, and RZ23L  C           o  If your system uses a small-capacity system disk (less D              than 210 megabytes), the entire OpenVMS VAX Version 7.3C              operating system and the complete DECwindows Motif for C              OpenVMS VAX layered product will not fit on your disk. B              Appendix H describes some methods that may enable youA              to install or upgrade to OpenVMS VAX Version 7.3 and A              DECwindows Motif for OpenVMS VAX on a small-capacitym              system disk.   ;              Note that you can use the methods described inl<              Appendix H to free up disk space on any system.  A           For more information about these restrictions, refer to E           the OpenVMS operating system for VAX and Alpha, Version 7.3 -           Software Product Description (SPD).c       1.2 Key Terms   E           You need to know the following key terms before you install             or upgrade the system:  E           ___________________________________________________________aE           Term__________________Definition___________________________   D           Distribution media    The media containing the OpenVMS VAX:                                 operating system software.  ?           System disk           The disk that contains (or will B                                 contain) the OpenVMS VAX operatingC                                 system. The installation or upgradem?                                 procedure transfers the OpenVMS C                                 operating system from the operating D                                 system CD-ROM on the source drive to0                                 the system disk.  E                                                   Getting Started 1-3             Getting Startedt
 1.2 Key Termsi  A       ___________________________________________________________ A       Term__________________Definition___________________________e  >       Local drive           A drive that is connected directly;                             to a VAX computer. For example,i;                             a magnetic tape drive connectede9                             directly to a VAX computer iseA                             referred to as a local tape drive. Ife?                             you have a standalone VAX computer,eA                             it is likely all the drives connected <                             to your system are local drives.  :       InfoServer            A general-purpose disk storage=                             server that allows you to use then@                             distribution compact disc to installA                             the operating system on remote clienta=                             systems connected to the same LANt1                             (local area network).o  A       Source drive          The drive that holds the distributione7                             media during the upgrade ors)                             installation.r  ;       Target drive          The drive that holds the systemo8                             disk-or, for some files, the=                             alternate disk-during the upgraden,                             or installation.  ?       HSx device            A self-contained, intelligent, mass A                             storage subsystem that lets computersn=                             in a VAXcluster environment sharel@                             disks. The disk on which you install?                             or upgrade the operating system cane@                             be connected to one of these systemsA       ______________________(for_example,_an_HSC_or_HSD).________   =       For definitions of other specialized terms used in thisa7       manual, see the Glossary at the end of this book.   - 1.3  Locating Files on the Distribution Mediai  @       The OpenVMS VAX files are stored on the distribution media!       as the following save sets:n       1-4  Getting Started           E                                                       Getting StartedAE                          1.3 Locating Files on the Distribution Mediae  E           ___________________________________________________________ E           Save-Set_Name_____Description______________________________h  -           VMS073.A          Used for upgrades.  $           VMS073.B          Required  .           VMS073.C          Library (optional)  /           VMS073.D          Optional (optional)c  3           VMS073.E          Help Message (optional)   B           VMS073.F          OpenVMS Management Station software PCE           __________________files_(optional)_________________________   @           See Appendix D for descriptions of the file subclasses.           contained in the optional save sets.  A           The optional DECwindows support files are stored on theP8           distribution media as the following save sets:  E           ___________________________________________________________SE           Save-Set_Name_____Description______________________________   .           DECW073.C         Base support files  5           DECW073.D         Workstation support filesP  3           DECW073.E         75 dots/inch font files.  E           DECW073.F_________100_dots/inch_font_files_________________t       1.3.1 On CD-ROMi  B           The OpenVMS VAX Version 7.3 CD-ROM contains all the saveC           sets and DECwindows base and workstation support files onrD           one compact disc. You can install or upgrade the operating@           system from a local compact disc drive as well as fromC           an InfoServer device. (For more information, refer to the 0           Guide to OpenVMS Version 7.3 CD-ROMs.)  9           The CD-ROM is labeled similar to the following:I  7           CD-ROM Label:         OpenVMS VAX Version 7.3S  )           Volume Label:         VAXVMS073e  B             ________________________ Note ________________________  B             The volume label is the machine-readable name that the?             OpenVMS VAX operating system and InfoServer systemss%             use to access the CD-ROM.   B             ______________________________________________________  E                                                   Getting Started 1-5     s       Getting Startedp, 1.3 Locating Files on the Distribution Media    * 1.3.2  On Magnetic Tape or Tape Cartridges  ?       The OpenVMS VAX Version 7.3 kit is available on two, 6250o=       BPI, open reel magnetic tapes or on two TK50 CompacTapeD=       cartridges. (Earlier versions of OpenVMS VAX shipped onl       four magnetic tapes.)P  8       The first tape or cartridge contains the VMS073.A,:       VMS073.B, and VMS073.C save sets. The second tape or?       cartridge contains standalone BACKUP (TK50 tape cartridge @       only), the VMS073.D, VMS073.E, and VMS073.F save sets, and=       the DECW073.C, DECV073.D, DECW073.E, and DECW073.F savey       sets.i  ?          ________________________ Note ________________________e  8          Standalone BACKUP is not available on open reel;          magnetic tape. If you are installing from magnetict>          tape and want to use standalone BACKUP, you must boot.          standalone BACKUP from another media.  ?          ______________________________________________________    1.3.3  DECamds Files  9       The DECamds software is included on the OpenVMS VAX,;       distribution media. The DECamds kit is located on thea<       second magnetic tape or TK50 CompacTape cartridge, and%       on the Layered Products CD-ROM.   + 1.3.4  Software Product Descriptions (SPDs)   @       If your distribution kit is on compact disc, the SPD files<       are located in the [DOCUMENTATION.V073] directory. For>       information about locating and printing these SPD files,8       refer to the Guide to OpenVMS Version 7.3 CD-ROMs.  <       The following SPD files are located on the second TK50>       CompacTape cartridge and the second magnetic tape. TheseA       SPD files have been grouped into an OpenVMS BACKUP save set,A       named VMS073_SPD.BCK. File names with the .PS extension areL>       in PostScript format. File names with the .TXT extension'       are in ASCII (plain text) format.)  =       DECNET_SPD.PS    DECnet-Plus for OpenVMS VAX and Alpha,e"       DECNET_SPD.TXT   Version 7.3   1-6  Getting Started V  l      E                                                       Getting Started E                          1.3 Locating Files on the Distribution Media       ?           OVMS_73_SPD.PS   OpenVMS Operating System for VAX and -           OVMS_73_SPD.TXT  Alpha, Version 7.3i  5           RMS_SPD.PS       RMS Journaling for OpenVMSs           RMS_SPD.TXT   3           CLUSTER_SPD.PS   OpenVMS Cluster Software            CLUSTER_SPD.TXTa  7           VOL_SHAD_SPD.PS  Volume Shadowing for OpenVMSp           VOL_SHAD_X           SPD.TXT   )           GALAXY_SPD.PS    OpenVMS Galaxy(           GALAXY_SPD.TXT  >           To obtain all the SPD files and restore them to yourA           current default directory, enter a BACKUP command using_           the following format:_  <           BACKUP source-drive:VMS073_SPD.BCK /SAVE_SET *.*;*  B           For source-drive, substitute the name of the device thatC           holds your distribution kit. For example, if your source- C           drive is a local magnetic tape drive with the device namet6           MUAO, you would enter the following command:  5           $ BACKUP MUAO:VMS073_SPD.BCK/SAVE_SET *.*;*   C           To restore all the SPD files in PostScript format to your 1           default directory, enter the following:   A           $ BACKUP MUAO:VMS073_SPD.BCK/SAVE_SET/SELECT=*.PS *.*;*   D           The following command restores the PostScript SPD file forE           the OpenVMS VAX and OpenVMS Alpha operating systems to your $           current default directory:  K           $ BACKUP MUAO:VMS073_SPD.BCK/SAVE_SET/SELECT=OVMS_73_SPD.PS *.*;*_  +     1.4 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.  E                                                   Getting Started 1-7             Getting Startedt' 1.4 What Happens During an Installation     >       o  Transfers the OpenVMS VAX files from the distribution"          media to the system disk.  & 1.4.1  When to Perform an Installation  8       Use the installation procedure under the following       conditions:o  :       o  If your VAX computer is new (it has never had anyA          version of the operating system running on it, includings%          factory-installed software).p  >       o  If your VAX computer is running a previous version of;          the operating system and you want to overwrite thel<          entire contents of the system disk (the OpenVMS VAXA          operating system, application software, and user files).i  ?       o  If you are running a previous version of the operating <          system, but you cannot upgrade. For example, if you>          changed the names of system directories on the system=          disk, the upgrade procedure will not work correctly. ?          You can either restore the system disk to its original >          directory structure, or you can reinstall the OpenVMS          VAX operating system.  @          _______________________ Caution _______________________  :          The installation procedure initializes the system=          disk, overwriting its contents. For this reason, useg=          the installation procedure only on new VAX computersf=          or if you want to destroy the contents of the systemC          disk.  ?          ______________________________________________________a  0 1.4.2  How to Use the Installation Documentation  8       This manual contains step-by-step instructions for?       performing an OpenVMS VAX installation. However, you will =       need to refer to several different documents before and ?       during the installation. Figure 1-1 illustrates the major @       steps in an installation and the documents you will use to       perform each step.     1-8  Getting Started _  _      E                                                       Getting StartedoE                               1.4 What Happens During an Installationr    B           Figure 1-1 Documentation Used to Perform an Installation                                                                                        E                                                   Getting Started 1-9             Getting Startedi" 1.5 What Happens During an Upgrade    # 1.5  What Happens During an Upgrade_  <       When you upgrade the OpenVMS VAX operating system, the+       upgrade procedure does the following:o  @       o  Deletes and purges some OpenVMS VAX files on the system3          disk but leaves all the user files intact.   5       o  Transfers the new OpenVMS VAX files from the_/          distribution media to the system disk.a  ?          ________________________ Note ________________________   ?          The upgrade procedure puts the most recent versions of ?          the OpenVMS VAX files in the system common directoriesd=          (SYS$COMMON). The upgrade procedure does not replacec=          or delete any versions of these files in the system- :          specific directories (SYS$SPECIFIC). If there are>          previous versions of OpenVMS VAX files in the system-;          specific directories, the upgrade procedure or thee0          upgraded system may not work correctly.  ?          ______________________________________________________r  A       o  Merges some of the old OpenVMS files and the new OpenVMS7'          VAX files and replaces others.a  <          Certain OpenVMS VAX files are placed either over or@          under existing files (that is, they are given a versionA          number above or below the version number of the existing_=          file). This protects any customizations to the filesb<          and results in having two versions of the file when<          the upgrade is completed. For more information, see          Appendix F.  <       o  Cleans up files and structures used only during the          upgrade.   :       o  Leaves your OpenVMS license and System Integrated'          Product (SIP) licenses intact.u  >          You do not need to reinstall these licenses after you?          upgrade. (Refer to Appendix B for detailed information ?          about license management for OpenVMS VAX Version 7.3.)    1-10  Getting Startedi    O      E                                                       Getting StartedoE                                    1.5 What Happens During an Upgradee    $     1.5.1 When to Perform an Upgrade  D           In most cases, you can use the upgrade procedure to obtain?           a higher version of the OpenVMS VAX operating system.CB           Unlike the installation procedure, the upgrade procedureB           does not initialize your system disk. This means you canA           get the latest version of the operating system and keepe=           your user files and optional software files intact.t  .     1.5.2 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 duringiB           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 Upgradei                       1.6 What to Do Nextf  E           If you want to install the OpenVMS VAX operating system, go            to Chapter 2.g  C           If you are upgrading the OpenVMS VAX operating system, gos           to Chapter 5.                     E                                                  Getting Started 1-11s n  a                    E                                                                     2 E     _________________________________________________________________n  E                 Preparing to Install the OpenVMS VAX Operating SystemI    B           This chapter describes how to prepare for installing the2           OpenVMS VAX operating system, including:  9           o  Being aware of the cautions and restrictions   ,           o  Ensuring your hardware is ready  @           o  Ensuring your software distribution kit is complete  3           o  Preparing for a VAXcluster environmentg  0           o  Preparing your tape and disk drives  D           o  Gathering the information you need to supply during the#              installation procedure   5           o  Completing the preinstallation checklistL  C           If you are an experienced system manager, you can use theMA           checklist at the end of the chapter to complete all theD*           necessary preinstallation 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 completed all the preinstallation tasks.r  !     2.1 Cautions and Restrictions   ?           Before you begin the installation procedure, note the .           following cautions and restrictions.       2.1.1 Cautions  E           The following cautions apply for Version 7.3 of the OpenVMS            VAX operating system:o  ?           o  The software installation procedure overwrites the >              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, you  E             Preparing to Install the OpenVMS VAX Operating System 2-1y           5 Preparing to Install the OpenVMS VAX Operating System: 2.1 Cautions and RestrictionsO    A          should upgrade to the new version of OpenVMS VAX. For an :          overview of the upgrade procedure, see Chapter 5.  9       o  Do not attempt to use VMSINSTAL with OPTION G to >          transfer OpenVMS VAX save sets to another media type;;          doing so produces an unusable system. Instead, you >          can use the DCL command COPY to transfer save sets to          another media type.  >          If you move the save sets from the distribution mediaA          before beginning the installation, you must move them toa@          the [000000] directory on a disk that is not the system5          disk; otherwise, the installation will fail.g   2.1.2  Restrictions   =       The following restrictions apply for Version 7.3 of the #       OpenVMS VAX operating system:n  8       o  If your system contains DIGITAL Storage Systems6          Interconnect (DSSI) disks attached to a KFQSAA          controller, you will notice a change in the device namest6          for DSSI disks attached to KFQSA controllers.  A          When you boot standalone BACKUP, it displays the devicese?          on your system using the new device naming scheme. Useh=          the new device names throughout the installation andp-          after you complete the installation.m  <       o  If you want to use DECwindows software with OpenVMS;          VAX Version 7.3, you must purchase and install theh;          DECwindows Motif for OpenVMS VAX Version 1.2-3, or ;          higher, layered product. For more information, seee          Section 1.1.2._  / 2.2  Examining Software and Hardware Components   >       Before beginning an installation or upgrade, be sure you@       have all the required hardware and software components, as*       described in the following sections.          : 2-2  Preparing to Install the OpenVMS VAX Operating System           E                 Preparing to Install the OpenVMS VAX Operating System E                        2.2 Examining Software and Hardware Components          2.2.1 Hardware Componentsf  =           Before you begin an installation or upgrade, do thel           following:  D           o  Be sure the hardware has been installed and checked forE              proper operation. For detailed information, refer to theaB              hardware manuals you received with your VAX computer.  <           o  Be sure you know how to turn on and operate theB              components of your system, including the system unit,B              console, monitor, drives, terminals, and printers. If@              necessary, read the hardware manuals that came with              these components.  D           o  Set up your system to record the installation procedureC              on either a hardcopy terminal or a printer attached to B              the console terminal. (Refer to your hardware manualsB              for more details about connecting those components toE              your system.) If you do not do this, the screen messagesaC              will be lost. You need a transcript in case there is av-              problem during the installation.s       2.2.2 Software Componentso  =           Before you begin an installation or upgrade, do the            following:  A           o  Be sure you have all the items listed on the bill ofeD              materials in the distribution kit. If your distribution:              kit is incomplete, notify your Compaq support@              representative and request priority shipment of any              missing items.m  ?           o  Before installing the OpenVMS VAX operating system B              software, review all cover letters and release notes.  >           o  Read the Before Installing OpenVMS section in the=              installation and upgrade supplement for your VAX_A              computer, which describes tasks specific to your VAX A              computer that you must complete before beginning ther              installation.      E             Preparing to Install the OpenVMS VAX Operating System 2-3  e  t      5 Preparing to Install the OpenVMS VAX Operating Systeml! 2.3 Preparing for an Installationn    " 2.3  Preparing for an Installation  9       Now that you have determined that your hardware ando?       software components are ready, you can make the necessaryr;       preparations for installing the OpenVMS VAX operatingn
       system.s  - 2.3.1  Preparing for a VAXcluster Environment   A       If you are installing the OpenVMS VAX operating system in a A       VAXcluster environment, the installation procedure displayseA       information about cluster configuration. But, because thered>       is no network present on the system at this point in the>       procedure, no cluster configuration work can actually be?       performed at this time. Before proceeding, review OpenVMSeA       Cluster Systems, which provides the information you need to /       answer questions during the installation.   ?          ________________________ Note ________________________e  ?          Entering incorrect information during the installationt8          can force you to repeat the entire installation          procedure.e  ?          ______________________________________________________n  =       Table 2-1 lists the VAXcluster information you need ande=       explains how to obtain that information. For a completet4       explanation, refer to OpenVMS Cluster Systems.  A Table_2-1__VAXcluster_Information_for_Installations______________    Information YoupA Need______________How_to_Get_It__________________________________e  > Type of           Configuration types are distinguished by the< configuration     interconnect device that the VAX computers<                   in the cluster use to communicate with one@                   another: Computer Interconnect (CI), Ethernet,A                   DIGITAL Storage Systems Interconnect (DSSI), ory:                   FDDI (Fiber Distributed Data Interface).  B                                           (continued on next page)    : 2-4  Preparing to Install the OpenVMS VAX Operating System           E                 Preparing to Install the OpenVMS VAX Operating SystemaE                                     2.3 Preparing for an Installation     E     Table_2-1_(Cont.)_VAXcluster_Information_for_Installations________       Information You E     Need______________How_to_Get_It__________________________________   A     DECnet node name  Determined by the network or system manager D     and node address  for each VAX computer on the network. See yourC                       system or network manager for the DECnet noder@                       name and node address for the VAX computerA                       on which you are installing the OpenVMS VAXiD                       operating system. Refer to the DECnet-Plus forC                       OpenVMS Installation and Configuration manual +                       for more information.   E     Allocation class  During the installation procedure you are askedeA     value             for the ALLOCLASS value of the VAX computereA                       on which you are installing the OpenVMS VAXs4                       operating system. For example:  E                       Enter a value for MYNODE's ALLOCLASS parameter:h  >                       Refer to OpenVMS Cluster Systems for theB                       rules on specifying allocation class values.C                       Note that, in a mixed-interconnect VAXcluster D                       environment, the allocation class value cannotA                       be zero. It has to be a value between 1 and A                       255. This is also true for any VAX computerl6                       connected to a dual-pathed disk.  @                       When you enter the allocation class value,?                       the installation procedure uses it to setsA                       the value of the ALLOCLASS system parameterd$                       automatically.  C     Quorum disk       Refer to OpenVMS Cluster Systems to determine D                       whether you want a quorum disk in the cluster.  C     Location for      Refer to OpenVMS Cluster Systems to determineeC     page and swap     where the page and swap files will be locatedeB     files             for the system from which you are installing@                       the OpenVMS VAX operating system software.  E                                              (continued on next page)d    E             Preparing to Install the OpenVMS VAX Operating System 2-5     o      5 Preparing to Install the OpenVMS VAX Operating Systemh! 2.3 Preparing for an Installationr    A Table_2-1_(Cont.)__VAXcluster_Information_for_Installations______0   Information YoudA Need______________How_to_Get_It__________________________________i  > MOP servers,      To establish either a local area or a mixed-? disk servers,     interconnect cluster, determine which systemsn? tape servers      will be Maintenance Operations Protocol (MOP)s@                   servers, disk servers, and tape servers. Refer-                   to OpenVMS Cluster Systems.e  > Cluster group     To establish either a local area or a mixed-' number and        interconnect cluster: A cluster password  o  Cluster group number - A number in the range   :                      from 1 to 4095 or from 61440 to 65535  >                   o  Cluster password - Can range from 1 to 31>                      alphanumeric characters, including dollar3                      signs ($)  and underscores (_)r  A _________________________________________________________________s  % 2.3.2  Preparing Tape and Disk Drivesp  ;       Prepare your tape and disk drives using the following        steps:  <       1. Decide which drive will hold the distribution media=          and which drive will hold the system disk. Determinee<          the device names for each drive. You will need this=          information throughout the installation. If you needpA          information about devices and device names, refer to the ?          Before Installing the OpenVMS Operating System section @          in the upgrade and installation supplement for your VAX          computer.  ?          ________________________ Note ________________________   <          Do not place the distribution media in the drive at          this point.  ?          ______________________________________________________f  <       2. Follow this step only if the source drive or target=          drive is attached to an HSx device. Otherwise, go toa          step 3.  : 2-6  Preparing to Install the OpenVMS VAX Operating System           E                 Preparing to Install the OpenVMS VAX Operating SystemnE                                     2.3 Preparing for an Installationc    B              Make sure that both the CI and HSx devices are turnedD              on and are on line. Obtain the HSx name from the system5              manager, or use the following procedure:o  9              a. Press Ctrl/C at the HSx console terminal.o  B              b. Enter the following command at the HSx> prompt and                 press Return:   !                  HSx> SHOW SYSTEM   B                 The information displayed includes the name of the!                 HSx. For example:o  P                  11-SEP-2000 15:00:00.00 Boot:11-SEP-2000 11:31:11.41  Up: 51:00P                  Version V350           System ID: %X000000011        Name: MUTT                        .                        .                        .D                  DISK allocation class = 1 TAPE allocation class = 0,                  Start command file Disabled  &                  SETSHO - Program Exit  D                 For more information, refer to the HSx User's Guide.  B           3. Place a scratch disk in the drive for the system disk/              (unless the system disk is fixed).   E           4. Spin up the disk that will be the system disk but do not               write protect it.  6     2.3.3 Information You Need During the Installation  ?           During the installation, the procedure prompts you to E           supply certain information. To save time once the procedure <           begins, be sure you have the following informationD           available. Remember, entering incorrect information during?           the installation could force you to repeat the entirer!           installation procedure.t  E     _________________________________________________________________n     RequiredE     Information________Explanation___________________________________i  C     Passwords          You will be prompted to type passwords of atmB                        least 8 characters for the SYSTEM, SYSTEST,*                        and FIELD accounts.  E             Preparing to Install the OpenVMS VAX Operating System 2-7  t         5 Preparing to Install the OpenVMS VAX Operating Systemc! 2.3 Preparing for an Installationt  A _________________________________________________________________w RequiredA Information________Explanation___________________________________   < SCSNODE and        You will be prompted to supply an SCSNODE@ SCSSYSTEMID        name and an SCSSYSTEMID system parameter. TheA parameters         SCSNODE name must be a 1- to 6-character name;n?                    the SCSSYSTEMID system parameter is a number_1                    in the range of 1025 to 65535.-  ;                    If you will be using DECnet Phase IV fors@                    OpenVMS VAX or Compaq DECnet-Plus for OpenVMS?                    VAX with Phase IV compatible addresses, theno<                    SCSNODE must be the DECnet node name, andA                    SCSSYSTEMID must be calculated from the DECnet &                    address as follows:  <                    (DECnet-area * 1024) + DECnet-node-number  < Optional           The installation procedure prompts you to: components         specify whether you want to install the: and OpenVMS        library (VMS073.C), optional (VMS073.D)= Management         OpenVMS components, and OpenVMS Managemente8 Station files      Station software PC files (VMS073.F).?                    Appendix D lists the files included in these                     save sets.n  A                    You can save some space on your system disk ifV>                    you choose not to install these components,:                    but be sure to review Appendix D before                    deciding.  = Location for Help  Save set VMS073.E contains the online Help_A Message utility    Message utility, which you can install on your A                    system disk or on an alternate disk. (However,d=                    if you copied the distribution kit to some @                    other media from which you will be performingA                    the installation, you cannot install this save &                    set on that media.)              : 2-8  Preparing to Install the OpenVMS VAX Operating System e  l      E                 Preparing to Install the OpenVMS VAX Operating System E                                     2.3 Preparing for an Installationu  E     _________________________________________________________________      RequiredE     Information________Explanation___________________________________a                                                                                      E             Preparing to Install the OpenVMS VAX Operating System 2-9            5 Preparing to Install the OpenVMS VAX Operating System ! 2.3 Preparing for an Installationo  A _________________________________________________________________e RequiredA Information________Explanation___________________________________   < DECwindows         The installation procedure prompts you to< components         specify which of the following DECwindows2                    components you want to install:  ;                    o  DECwindows base support (required fort9                       running DECwindows software), whichn                       includes:e  -                       -  DECwindows transportA  +                       -  DECwindows keymapso  >                    o  DECwindows workstation support (required<                       for VAX workstations), which includes:  6                       -  DECwindows X11 display server  )                       -  Graphics driversa  1                       -  75 dots/inch video fonts   :                       -  100 dots/inch video fonts (option@                          available only if you select DECwindows-                          workstation support)   <                    You must install the DECwindows Motif for@                    OpenVMS VAX (previously called VMS DECwindows<                    Motif) layered product if you want to run<                    the DECwindows software. DECwindows Motif?                    for OpenVMS VAX Version 1.2-3 (or 1.2 if thed>                    VAXMOTF05_012 remedial kit is installed) is<                    the minimum supported version for systems=                    running OpenVMS VAX Version 7.3. If you dotA                    not know which version of DECwindows Motif youP@                    are currently running on your system, you can;                    check by entering the following command:   ?                    $ ANALYZE/IMAGE SYS$LIBRARY:DECW$XLIBSHR.EXE   A                    Note that the DECwindows Motif for OpenVMS VAXe?                    layered product does not have the DECwindows >                    base and workstation support components. To?                    get full DECwindows support, you must selectc>                    the DECwindows components provided with the;                    OpenVMS VAX kit and install the separate_;                    DECwindows Motif for OpenVMS VAX layeredp=                    product, which supports both Motif and XUI                      environments.  ; 2-10  Preparing to Install the OpenVMS VAX Operating Systemh i  w      E                 Preparing to Install the OpenVMS VAX Operating SystemeE                                     2.3 Preparing for an Installation   E     _________________________________________________________________t     RequiredE     Information________Explanation___________________________________   8     PAK information    The information listed on ProductA                        Authorization Keys (PAKs) for your OpenVMS_E                        VAX license and any system integrated productsvE                        you will run. The installation procedure gives_C                        you the opportunity to register any licenseseD                        you have. To register your licenses, you willB                        need to enter the information listed on theE     ___________________PAK_for_each_license._________________________a                                                                    E            Preparing to Install the OpenVMS VAX Operating System 2-11a o  t      5 Preparing to Install the OpenVMS VAX Operating Systeml 2.4 Preinstallation Checklisth     2.4  Preinstallation Checklist  :       Before you begin the installation, use the following@       checklist to make sure you have completed all of the tasks        described in this chapter:  <       <  Read the cautions and restrictions described at the#          beginning of this chapter.o  8       <  Make sure the hardware is installed and tested.8          (Described in the hardware manuals for your VAX          computer)  ;       <  Check the contents of your kit against the bill oft          materials (BOM).a  @       <  Read Appendix B of this manual, the OpenVMS Version 7.3=          New Features and Documentation Overview, the OpenVMST9          Version 7.3 Release Notes, and any cover lettersl           included with your kit.  :       <  Turn on the system. (Described in the upgrade and7          installation supplement for your VAX computer)t  A       <  Set up your system to record the installation procedure.s>          (Described in the upgrade and installation supplement          for your VAX computer)   :       <  Read the Before Installing OpenVMS section in the9          upgrade and installation supplement for your VAXo8          computer and perform the tasks described there.  :       <  Make sure you have the most recent version of the6          console media if you have a VAX computer that:          uses console media. (Described in the upgrade and7          installation supplement for your VAX computer)e  =       <  Determine whether you want a CI only, local area, or_=          mixed-interconnect cluster if you are installing ther<          OpenVMS VAX operating system on a VAX computer in a>          VAXcluster environment. (Described in OpenVMS Cluster          Systems)m  @          You should have the following information, depending on           the type of VAXcluster:  ?          o  CI Only VAXcluster: Get the allocation class value,a=             DECnet node name, and DECnet node address for theS;             computer. You also need to decide if you want a   ; 2-12  Preparing to Install the OpenVMS VAX Operating System_    u      E                 Preparing to Install the OpenVMS VAX Operating SystemCE                                         2.4 Preinstallation Checklist     A                 quorum disk and where the page and swap files for @                 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              Section 2.3.2)t  D           <  Make sure you have the following information (described)              in Section 2.3.3) available:y  B              o  Passwords containing at least 8 characters for the3                 SYSTEM, SYSTEST, and FIELD accountsn  ?              o  SCSNODE and SCSSYSTEMID if you are installing a !                 standalone system                                             E            Preparing to Install the OpenVMS VAX Operating System 2-13y c  s      5 Preparing to Install the OpenVMS VAX Operating System  2.4 Preinstallation Checkliste    A          o  A list of optional OpenVMS VAX components you want toc             installl  @          o  A list of optional DECwindows support components you             want to install   <          o  Information listed on Product Authorization Keys>             (PAKs) for your OpenVMS VAX license and any system,             integrated products you will run  A       After you have performed all the tasks in the checklist, go -       to Chapter 3 to begin the installation.                                                                   ; 2-14  Preparing to Install the OpenVMS VAX Operating SystemX e  i                    E                                                                     3_E     _________________________________________________________________e  D                          Installing the OpenVMS VAX Operating System    B           During the installation procedure, OpenVMS VAX files are?           transferred from the distribution media to the systemS?           disk or, for certain files, to an alternate disk. TheeD           time required to complete an installation varies depending@           on your hardware configuration and on the distributionE           media you are using. In most cases, magnetic tapes and tape_:           cartridges require more time than compact discs.  B           This chapter describes the following installation tasks:  &           o  Booting standalone BACKUP  %           o  Creating the system diskw  "           o  Configuring a cluster             o  Setting passwords  )           o  Creating the rights database   !           o  Registering licenses              o  Running AUTOGEN  C           At certain points in the procedure you will need to referoE           to the upgrade and installation supplement for installationt>           instructions that are specific to your VAX computer.  !     3.1 Booting Standalone BACKUP   E           Standalone BACKUP is a subset of the OpenVMS Backup utilityoD           (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 requiredYD           save sets from the distribution media to your system disk.  <           To boot a standalone BACKUP environment, enter the           following:             >>> B DKA400  E                      Installing the OpenVMS VAX Operating System  3-1O V  V      + Installing the OpenVMS VAX Operating System  3.1 Booting Standalone BACKUPi    6       Standalone BACKUP is included in the OpenVMS VAX?       distribution kit. Each piece of media in the distribution3?       kit has a label that indicates its contents. For example,d8       there are two CompacTape cartridges in a TK50 kit.8       Standalone BACKUP is on the second tape cartridge.  " 3.1.1  Booting from Tape Cartridge  @       If your distribution media is contained on TK50 CompacTapeA       cartridges, complete the following steps to boot standalone ;       BACKUP. (If you are using an InfoServer device, go to        Section 3.1.2.)   ?       1. Place the media that contains standalone BACKUP in thew@          source drive or in the console drive and boot from that          drive.i  A       2. Follow the instructions in the Booting Standalone BACKUPr?          section of the upgrade and installation supplement forp          your VAX computer.   >       3. After you boot standalone BACKUP, the system displays          the following message:t  O          %BACKUP-I-IDENT, standalone BACKUP V7.3; the date is 13-NOV-2000 10:00l
          $  ?          ________________________ Note ________________________p  :          If you have a tape cartridge kit, remove the tape?          cartridge 2/2 from the drive after you boot standalonet9          BACKUP. Put the tape cartridge that contains the <          OpenVMS VAX operating system in the drive. The tape=          cartridge is labeled VMS073 BIN TK50 1/2 VMS BINARY._  ?          ______________________________________________________u  4       After you have booted standalone BACKUP, go to       Section 3.2.  " 3.1.2  Booting from the InfoServer  ?       If you are using the InfoServer to boot standalone BACKUPT8       from a compact disc, complete the following steps:  @       1. Insert the distribution compact disc into the drive and          boot from that drive.  0 3-2  Installing the OpenVMS VAX Operating System           D                          Installing the OpenVMS VAX Operating SystemE                                         3.1 Booting Standalone BACKUPX    E           2. Follow the instructions in the Booting Standalone BACKUPnC              section of the upgrade and installation supplement fori              your VAX computer.y  ?           3. Enter your VAX processor boot command by using the:A              designator for the Ethernet adapter in the boot path C              and, except for the VAX 9000 computer, add the /R5:100 +              qualifier to the boot command.   8              For example, on a VAX 6000 computer, enter:  %              >>> B/R5:100/X:D/B:6 ET0g  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 supportedB              controller has a unique boot command procedure. ReferD              to the upgrade and installation supplement for your VAXB              9000 computer for instructions for booting standalone#              BACKUP on your system.o  E           4. During an InfoServer boot, the procedure prompts you for C              a file name that contains an initial system load (ISL)n@              boot program instead of a virtual memory boot (VMB)=              program. Select one of the two files as follows:c                o  ISL_SVAX_073                o  ISL_LVAX_073  A              Use the following table to determine which file name E              and boot path designator to use for your processor. NoteaC              that the VAX 9000 computer has the ISL file data builth9              in its VMB image that runs from the console.r  E              ________________________________________________________g              ProcessorE              Series________ISL_File________Boot_Path_Designator______   E              VAX 3000      ISL_SVAX_073    ESA0 (LANCE), XQA0 (DELQA)   D              VAX 4000      ISL_SVAX_073    EZA0 (SGEC), XQA0 (DELQA)  =              VAX 6000      ISL_LVAX_073    EXA0 (DEMNA), FXA0d@                                            (DEMFA), ETA0 (DEBNI)2                                            (DEBNA)  E              VAX 7000      ISL_LVAX_073    EXA0 (DEMNA), FXA0 (DEMFA)   E              VAX 10000     ISL_LVAX_073    EXA0 (DEMNA), FXA0 (DEMFA)   E                      Installing the OpenVMS VAX Operating System  3-3     u      + Installing the OpenVMS VAX Operating System  3.1 Booting Standalone BACKUPh  A          ________________________________________________________           ProcessorA          Series________ISL_File________Boot_Path_Designator______n  A          MicroVAX      ISL_SVAX_073    ESA0 (LANCE), XQA0 (DELQA)   3          VAXstation    ISL_SVAX_073    ESA0 (LANCE)   3          VAXft 110,    ISL_SVAX_073    EPA0 (LANCE)           310, 410,A          610,_and_612____________________________________________   ?          On a VAX 6000 computer, respond to the prompt as showno"          in the following example:  !          Loading system software.             Filename: ISL_LVAX_073   ?       5. The InfoServer ISL program then displays the following           menu:  /            Network Initial System Load Function             Version 1.2  &              FUNCTION         FUNCTION                IDa*                1     -        Display Menu"                2     -        Help,                3     -        Choose Service,                4     -        Select Options"                5     -        Stop  &           Enter a function ID value: 3  ;          Enter 3, as shown in the previous display, for thel<          function ID value. The following menu is displayed:  $              OPTION           OPTION                ID +                1     -        Find Servicesp6                2     -        Enter known Service Name  %           Enter an Option ID value: 2o  :          Enter 2 for the Option ID value. The following is          displayed:   %           Enter a Known Service Name:   ?          Enter the ISL file name for your processor series from           the previous table.  0 3-4  Installing the OpenVMS VAX Operating System           D                          Installing the OpenVMS VAX Operating SystemE                                         3.1 Booting Standalone BACKUP     C              If you need more information, select function ID 2 for_              help.  B           6. After you boot standalone BACKUP, the system displays              the following:i  P           %BACKUP-I-IDENT, standalone BACKUP V7.3; the date is 11-NOV-2000 10:00           $   8           After you have booted standalone BACKUP, go to           Section 3.2.  !     3.1.3 Booting from the CD-ROMt  E           If you are installing from the OpenVMS VAX operating systemiA           CD-ROM (your VAX computer supports booting from a localcE           CD-ROM or from an InfoServer), you can use the full OpenVMStE           environment instead of the standalone BACKUP environment tosD           transfer the VMS073.B save set to your target system disk.  >           Although it may take slightly longer to boot OpenVMS>           than to boot standalone backup, you might prefer the@           more robust OpenVMS environment. It provides a greaterD           range of commands and utilities than the standalone BACKUP           environment.  A           If you want to use the full OpenVMS environment, followo           these steps:  D           1. Boot the CD-ROM and specify root 1. For example, from a>              local drive on a VAXstation 4000 computer, enter:  &              >>> B/R5:10000000 DKA400:  B              If you are booting from an InfoServer device, enter aA              command that specifies root 1. For example, on a VAX "              6000 computer, enter:  *              >>> B/R5:10000100/X:D/B:6 ET0  C           2. After you boot the OpenVMS CD-ROM, the system displays                the following menu:  9                   1)  Execute DCL commands and proceduresI+                   2)  Shut down this system-  D              Choose option 1 to execute DCL commands and procedures.  @              The system displays a triple dollar sign ($$$)  DCLD              prompt to indicate that you are in this specialized DCL              environment.   E                      Installing the OpenVMS VAX Operating System  3-5p a  c      + Installing the OpenVMS VAX Operating Systems 3.1 Booting Standalone BACKUP     <          You can ignore the following SYSINIT errors if they          appear:  M       %SYSINIT-E, %SYSINIT, error opening system dump file, status = 00000910dP       %SYSINIT, primary PAGEFILE.SYS not found; system initialization continuing:       %SYSINIT, no dump file - error log buffers not savedA       %SYSINIT-E, error mounting system device, status = 007282ECn  ?          ___________________ Important Note ___________________o  =          During the installation, do not change the displayedr<          system time, even if it is incorrect. Attempting to=          change this value results in a write lock error thati          requires a CD reboot.  ?          ______________________________________________________a  A       3. Go to Section 3.2.3 to transfer the VMS073.B save set to_          your system disk.   3.2  Creating the System Diskt  :       You create an OpenVMS VAX Version 7.3 system disk by:       transferring OpenVMS VAX files from the distribution=       media to your system disk. (For certain files, you havee@       the option to transfer the files to your system disk or to       an alternate disk.)I  =       To transfer the OpenVMS VAX files from the distribution_A       kit to your system disk, perform the steps described in the        sections that follow.o   3.2.1  Determining Device Namesf  ;       If you have not already done so, determine the device :       names for the source drive, the target drive, and an<       alternate device if you will be using one. Write these?       names on a piece of paper. You will need this informationp@       throughout the installation. If either the source drive or@       the target drive is connected to an HSC, you also need the@       name of the HSC. (To determine the value for hsc-name, see"       Section 2.3.2 in Chapter 2.)  8       If you need more information about determining the<       device names for your system, refer to the upgrade and4       installation supplement for your VAX computer.  0 3-6  Installing the OpenVMS VAX Operating System t  i      D                          Installing the OpenVMS VAX Operating SystemE                                          3.2 Creating the System Disk     $     3.2.2 Loading Distribution Media  A           Each piece of media in the distribution kit has a label0D           that indicates its contents. Place the media that contains?           the OpenVMS VAX operating system in the source-drive.e  D           If your OpenVMS VAX distribution kit consists of more thanC           one piece of media, place the first piece of media in therB           source-drive. For example, if you have a TK50 CompacTapeC           cartridge kit, make sure the first tape is in the source-y           drive.  D           If you are installing from a compact disc, disc one of two"           is already in the drive.  3     3.2.3 Transferring VMS073.B to Your System Diska  D           Enter a BACKUP command in the following format to transfer4           the VMS073.B save set to your system disk:  I           $ BACKUP/IMAGE/VERIFY [hsc-name]source-drive:VMS073.B/SAVE_SET-t$           _$ [hsc-name]target-drive:  B             ___________________ Important Note ___________________  <             If you are using the full OpenVMS environment as=             described in Section 3.1.3, you will see a triplerB             dollar sign ($$$) instead of a single dollar sign ($).@             In this environment, you must first mount the targetA             drive with the /FOREIGN qualifier before performing aI             BACKUP:L  +             $$$ MOUNT/FOREIGN target-drive:   9             The BACKUP command must contain the directoryV>             specification [0,0] after the source drive to find             the saveset:  P           $$$ BACKUP/IMAGE/VERIFY [hsc-name]source-drive:[0,0]VMS073.B/SAVE_SET-%           _$$$[hsc-name]target-drive:E  B             ______________________________________________________  B           Substitute the appropriate device names for hsc-name (ifE           appropriate), source-drive, and target-drive. Make sure youSB           put a colon (:)  after each device name and that you useE           zeros rather than the letter "O" in the device names and ine           VMS073.e  E                      Installing the OpenVMS VAX Operating System  3-7     L      + Installing the OpenVMS VAX Operating System  3.2 Creating the System Disk    ?       The square brackets ([])  indicate that you need the hsc- 5       name only if the device is connected to an HSC._  >       For example, if your system has a source-drive that is a?       local TU80 magnetic tape drive with a device name of MUA0mA       and a target-drive that is an RA82 disk drive with a deviceLA       name of DUA1, enter the following command and press Return:   8       $ BACKUP/IMAGE/VERIFY MUA0:VMS073.B/SAVE_SET DUA1:  <       If your system has a source-drive that is a local tape=       cartridge drive with a device name of MUC6 or a target--A       drive that is an RA81 disk drive with a device name of DUA1 ?       and an HSC name of YOURS, enter the following command and        press Return:   >       $ BACKUP/IMAGE/VERIFY MUC6:VMS073.B/SAVE_SET YOURS$DUA1:  <       The procedure transfers the VMS073.B save set from the@       distribution kit to the system disk.[1] The amount of time=       this takes varies depending on the type of VAX computer >       and distribution media you have. During the process, the-       command displays the following message:   7       %BACKUP-I-STARTVERIFY, starting verification passt  @       This message indicates that the VMS073.B save set has been<       transferred to the system disk and the files are being@       checked for errors. If, instead, you see a message similar>       to the following, you might have the wrong volume of the+       distribution kit in the source drive:M  G       % BACKUP-F-OPENIN, error opening  MUA0:[000000]VMS073.B; as input )       - SYSTEM-W-NOSUCHFILE, no such file 
          .
          .
          .D       If you do want to perform another standalone BACKUP operation,?       ensure the standalone BACKUP volume is on line and ready.        Enter "YES" to continue:         ____________________9       [1]   The BACKUP command creates a system disk thate;             includes a set of volume parameters provided by >             Compaq, including the CLUSTER_SIZE parameter (disk?             access scheme).  For more information, refer to ther<             upgrade and installation supplement for your VAX               computer.y  0 3-8  Installing the OpenVMS VAX Operating System t         D                          Installing the OpenVMS VAX Operating SystemE                                          3.2 Creating the System Diski    A           If the procedure displays the previous messages, remove D           the distribution volume from the drive and replace it withE           the correct volume as described in Section 3.2.2. Then typea2           Yes, press Return, and repeat this step.  +           Completing the Transfer Operation,  @           Complete the transfer of the VMS073.B save set to yourD           system disk by performing one of the following operations:  ?           o  If you are using standalone BACKUP to transfer theAD              VMS073.B save set, the procedure displays the following:              message when it has completed checking files:  I              BACKUP-I-PROCDONE, Operation completed. Processing finished 0#              at 13-NOV-2000  10:00.rO              If you do not want to perform another standalone BACKUP operation,n0              use the console to halt the system.  K              If you do want to perform another standalone BACKUP operation,oK              ensure the standalone application volume is on line and ready.e%              Enter "YES" to continue:D  =              Go to Section 3.2.4 to boot the new system disk.z  D           o  If you are using the specialized OpenVMS environment toD              transfer the VMS073.B save set, the system displays theA              triple dollar sign ($$$) DCL prompt after the BACKUP D              operation completes. Enter the command LOGOUT to return&              to the menu. For example:                $$$ LOGOUT   8                  1)  Execute DCL commands and procedures*                  2)  Shut down this system  A              You can then choose option 2 to shut down the systemN?              in preparation for booting the new system disk, as (              described in Section 3.2.4.  %     3.2.4 Booting the New System Diskt  D           Halt the system and boot the new system disk, as describedA           in the upgrade and installation supplement for your VAX            computer.a  >           When the boot is completed, the procedure displays aC           message and prompts you to enter the date and time. EntertD           the date and time using the 24-hour clock format and press           Return.t  E                      Installing the OpenVMS VAX Operating System  3-9     n      + Installing the OpenVMS VAX Operating System  3.2 Creating the System Disk           For example:  M       OpenVMS (TM) VAX Version V7.3 Major version id = 1 Minor version id = 0n  5               OpenVMS VAX V7.3 Installation Procedurei  ;                              Model: VAXstation 3100-M76/SPXo3                      System device: RZ26 - _DKB100:o+                        Free blocks: 1984383 )                           CPU type: 11-04r  L       * Please enter the date and time (DD-MMM-YYYY HH:MM) 13-NOV-2000 10:35  ?       *********************************************************a?       %SYSTEM-W-TZGMT, your local timezone has defaulted to GMTh6       %SYSTEM-I-SETTZ, to set your local timezone use:+            $ @SYSMANAGER:UTC$TIME_SETUP.COMS  ?       *********************************************************e9       On MIN or UPGRADE system startup - CLUE is not run. >       %%%%%%%%%%%  OPCOM 13-NOV-2000 10:35:08.98   %%%%%%%%%%%7       Operator _OPA0: has been enabled, username SYSTEM >       %%%%%%%%%%%  OPCOM 13-NOV-2000 10:35:09.00   %%%%%%%%%%%)       Operator status for operator _OPA0:iL  CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,P  LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,  OPER11, OPER12i=       %%%%%%%%%%%  OPCOM 13-NOV-2000 10:35:09.62  %%%%%%%%%%%o5       Logfile has been initialized by operator _OPA0:t3       Logfile is SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1M>       %%%%%%%%%%%  OPCOM 13-NOV-2000 10:35:09.64   %%%%%%%%%%%E       Operator status for operator SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1cL  CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,P  LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,       OPER11, OPER127       %SYSTEM-I-BOOTUPGRADE, security auditing disabledn>       %%%%%%%%%%%  OPCOM  13-NOV-2000 10:35:11.60  %%%%%%%%%%%#       Message from user JOB_CONTROLVF       %JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT>       %%%%%%%%%%%  OPCOM  13-NOV-2000 10:35:11.60  %%%%%%%%%%%#       Message from user JOB_CONTROLK        -RMS-E-FNF, file not foundE       %LICENSE-F-EMTLDB, license database contains no license records 8       %SYSTEM-I-BOOTUPGRADE, security server not started>       %%%%%%%%%%%  OPCOM 13-NOV-2000 10:35:16:75   %%%%%%%%%%%  1 3-10  Installing the OpenVMS VAX Operating Systems a  i      D                          Installing the OpenVMS VAX Operating SystemE                                          3.2 Creating the System Disk     "           Message from user SYSTEMK           %LICENSE-E-NOAUTH, DEC VAX-VMS use is not authorized on this nodegN           -LICENSE-F-NOLICENSE, no license is active for this software product;           -LICENSE-I=SYSMGR, please see your system manager   K           %LICENSE-E-NOAUTH, DEC VAX-VMS use is not authorized on this nodeeO           -%LICENSE-F-NOLICENSE, no license is active for this software product_<           -%LICENSE-I-SYSMGR, please see your system manager*           Startup processing continuing...  P        %SET-I-INTSET, login interactive limit = 1, current interactive value = 0P        %SET-I-INTSET, login interactive limit = 0, current interactive value = 0  B             ________________________ Note ________________________  5             You can ignore the time zone message. TheM>             UTC$TIME_SETUP.COM procedure runs during the final0             phase of the installation procedure.  @             The procedure also displays OPCOM messages from JOB_A             CONTROL stating the master queue file QMAN$MASTER.DAT >             does not exist. You can ignore these messages. You-             will create the queue file later.e  ;             You can also ignore error messages stating thatr>             the OpenVMS VAX license is not registered. License@             registration occurs later in the procedure. For more<             information about registering your licenses, seeB             Appendix B and refer to the OpenVMS License Management             Utility Manual.h  B             ______________________________________________________  %     3.2.5 Specifying the Volume Labeln  B           The procedure prompts you to specify the volume label ofA           the system disk. A volume label is the name the OpenVMS3@           VAX operating system uses to refer to the system disk.B           You can press Return to accept the default volume label,E           OVMSVAXSYS, or you can enter a volume label of your choice.cE           The volume label can be 1 to 12 characters long; do not useU           spaces. For example:      E                     Installing the OpenVMS VAX Operating System  3-11e           + Installing the OpenVMS VAX Operating Systemb 3.2 Creating the System Disk    M           If this system disk is to be used in a cluster with multiple systemeL           disks, then each system disk must have a unique volume label.  AnyM           nodes having system disks with duplicate volume labels will fail toM            boot into the cluster.  P         You can indicate a volume label of 1 to 12 characters in length.  If youL         want to use the default name of OVMSVAXSYS, press RETURN in response         to the next question.i  A       * Enter the volume label for this system disk [OVMSVAXSYS]:e  " 3.2.6  Specifying the Source Drive  <       The procedure prompts you to specify which drive holds@       the distribution kit. Enter the device name for the source       drive.  >       For example, if you are not using the InfoServer and the@       source drive is a magnetic tape drive with the device name'       MUA0, type MUA0 and press Return.m  H       * Enter name of drive holding the OpenVMS distribution media: MUA09       * Is the OpenVMS media ready to be mounted? [N] yest0       %MOUNT-I-MOUNTED, VMS073 mounted on _MUA0:  6       If you are not using the InfoServer, continue to       Section 3.2.7.  2       If you are using an InfoServer, enter DAD1:.  I       * Enter the volume label for this system disk [OpenVMS073]: SYSDSK1rI       * Enter name of drive holding the OpenVMS distribution media: DAD1:   0       The procedure then prompts you as follows:  6       * Enter the InfoServer service name [VAXVMS073]:3       * Enter the InfoServer work group number [0]:s  :       Press Return as a response to both of these prompts.  >       The InfoServer work group number was determined when you@       made a selection from the menu displayed by the InfoServer?       ISL program (see Section 3.1). If the answer to the group @       number is incorrect, the procedure displays the following:  ?       InfoServer work group number must be in the range 0-1023.o  0       The procedure then prompts you as follows:  8       * Is the OpenVMS media ready to be mounted? [N]: Y1        %MOUNT-I-MOUNTED, VMS073 mounted on _DAD1:   1 3-12  Installing the OpenVMS VAX Operating Systeme           D                          Installing the OpenVMS VAX Operating SystemE                                          3.2 Creating the System Diskt    /     3.2.7 Selecting Optional OpenVMS Componentse  D           The procedure displays information about OpenVMS VAX filesB           that are optional and about the remaining amount of diskC           space. The information is similar to the following (block %           sizes might vary slightly):d  P                Select optional software you want to install. You can install oneI                or more of the following OpenVMS or DECwindows components:   M                o OpenVMS library                              -  52200 blocks M                o OpenVMS optional                             -  19000 blockseM                o OpenVMS Help Message                         -  10400 blockseM                o OpenVMS Management Station                   -  20000 blocksdM                o DECwindows base support                      -   4400 blocks M                o DECwindows workstation support               -  23800 blocksdL                      -  75 dots per inch video fonts          -   (included)M                      - 100 dots per inch video fonts          -   6200 blockseM                o DECnet-Plus networking                       -  80000 blocksVM                o DECnet Phase IV networking                   -    800 blocksn  8           Space remaining on system disk: 1170752 blocks  E           You must indicate which of the options you want to install.iE           If you require network support, you must select the OpenVMS            library component.  B           Note that, if you do not install the optional componentsC           at this time, you can install them after the installation*E           by using the VMSTAILOR or DECW$TAILOR utility. However, thetD           Help Message utility can be tailored on to the system disk           only.N  =           If you want to install Help Message on an alternate*?           disk, you must install it now or install it after thepD           installation procedure completes by entering the following           BACKUP command:t  A           BACKUP/VERIFY source-device:[000000]VMS073.E/SAVE_SET -M(           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 diskEC           is mounted, and for directory-name, enter the name of the%7           directory to which you are copying the files.P  E                     Installing the OpenVMS VAX Operating System  3-13%    C      + Installing the OpenVMS VAX Operating Systemr 3.2 Creating the System Disk    ;       Also note that, for TK50 CompacTape cartridges, it isD8       quicker to install OpenVMS VAX software during the>       installation than to add software after the installation;       with a tailoring utility. For information about usingt        VMSTAILOR, see Chapter 10.  ;       To select the options you want to install, follow theg.       instructions displayed by the procedure.   3.2.7.1  OpenVMS Library Files  3       The procedure displays the following message:0  ?       * Do you want to install the OpenVMS library files? (Y/N)   =       The file subclasses of the VMS073.C save set are listedb?       in Appendix D. If you want to install the VMS073.C files,c?       type Y (for Yes) and press Return. If you require network:@       support, you must select the OpenVMS library component. If@       you do not want to install the VMS073.C files, type N (for       No) and press Return.    3.2.7.2  OpenVMS Optional Files   3       The procedure displays the following message:g  @       * Do you want to install the OpenVMS optional files? (Y/N)  =       The file subclasses of the VMS073.D save set are listedl?       in Appendix D. If you want to install the VMS073.D files,S@       type Y and press Return. If you do not want to install the.       VMS073.D files, type N and press Return.   3.2.7.3  Help Message FilesI  3       The procedure displays the following message:   H           The Help Message utility (MSGHLP) provides online explanationsH           and user actions for OpenVMS messages in place of the hardcopyK           OpenVMS System Messages and Recovery Procedures Reference Manual,v,           which is now separately orderable.  ?           The MSGHLP database file, MSGHLP$LIBRARY.MSGHLP$DATA, 9           consumes approximately 10400 blocks and will be F           placed by default on your system disk in SYS$COMMON:[SYSHLP]?           unless you specify an alternate device when prompted.r  9       * Do you want to install the MSGHLP database? (Y/N)   1 3-14  Installing the OpenVMS VAX Operating System     o      D                          Installing the OpenVMS VAX Operating SystemE                                          3.2 Creating the System Disks    A           The Help Message utility is an online system for systemcE           messages documentation. You can install Help Message either D           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:_  P         You can install this database on your system disk in SYS$COMMON:[SYSHLP]M         or on an alternate device. If you specify an alternate device, but nomO         directory, MSGHLP$LIBRARY.MSGHLP$DATA is placed in [HELP_MESSAGE]. WheneM         prompted, take the default of the system disk or specify an alternatef"         device, using this format:  ;                                          device:[directory]   P    * Where do you want to install the MSGHLP database?[SYS$COMMON:[SYSHLP]] DUA1  @           The Help Message database is installed in the area youE           specify, and the system displays information similar to theg           following:  E               Space remaining on alternate device DUA1: 124532 blocksu  ,     3.2.7.4 OpenVMS Management Station Files  7           The procedure displays the following message:   J              The OpenVMS Management Station is a client-server applicationK              that provides OpenVMS system management capabilities through afM              client application on a personal computer (PC) running Microsoft K              Windows. The server application runs on OpenVMS systems and is M              automatically installed as part of the OpenVMS operating system.n  K              This option provides the files used to create the installationlN              media for the PC client software.  If you want to use the OpenVMSL              Management Station, you must install these optional files on atM              least one OpenVMS system to create the installation media, which J              can then be used to install the PC client on one or more PCs.  I              The OpenVMS Management Station client can run on Windows 3.1tK              (including Windows for Workgroups), Windows NT, or Windows 95.i  P        The OpenVMS Management Station optional files consume approximately 20000P        blocks and will be placed on your system disk in SYS$COMMON:[TNT.CLIENT].  P    * Do you want to install the optional OpenVMS Management Station files? (Y/N)  E                     Installing the OpenVMS VAX Operating System  3-15  e  h      + Installing the OpenVMS VAX Operating Systeme 3.2 Creating the System Disk    A       If you want to use the OpenVMS Management Station software,.:       you must install these files. After the installation@       procedure completes, follow the instructions in Appendix G;       to prepare your OpenVMS system and your PC to run the <       OpenVMS Management Station server and client software.  * 3.2.8  Choosing DECwindows Support Options  @       Next, the procedure displays messages about the DECwindows6       components shipped with OpenVMS VAX Version 7.3.  ?          ________________________ Note ________________________n  9          The OpenVMS VAX operating system no longer shipse9          the VMS DECwindows product. The operating systemn7          now ships only the DECwindows base support and :          DECwindows workstation support components. To get;          full DECwindows support, you must also install thei>          separate DECwindows Motif for OpenVMS VAX (previously<          called VMS DECwindows Motif) layered product, which2          supports both Motif and XUI environments.  ?          The DECwindows base support and DECwindows workstation <          support components are not shipped with the layered;          product. If you want to install these options, youo;          must select them now or use the DECW$TAILOR option 4          after the installation procedure completes.  ?          ______________________________________________________   @       Before you indicate whether you want to install DECwindows/       support software, consider the following:   A       ___________________________________________________________oA       If_you..._____________________Then_choose..._______________w  <       Intend to install the         DECwindows base support."       DECwindows Motif for OpenVMS       VAX layered producte  ;       Intend to install the         DECwindows base support >       DECwindows Motif for OpenVMS  and DECwindows workstation,       VAX layered product on        support.       a workstation or on ak       VAXcluster system that       contains workstationse  1 3-16  Installing the OpenVMS VAX Operating Systemo u  i      D                          Installing the OpenVMS VAX Operating SystemE                                          3.2 Creating the System Diskn  E           ___________________________________________________________sE           If_you..._____________________Then_choose..._______________   C           Are not planning to install   DECwindows base support and >           the DECwindows Motif for      DECwindows workstation0           OpenVMS VAX layered product   support.$           but are installing OpenVMS$           VAX on a workstation or on$           a VAXcluster that includes           workstations  ?           Want to provide font files    DECwindows base support B           for X terminals               and DECwindows workstation0                                         support.  ?           Have a workstation monitor    DECwindows base support B           (for example, a VR150,        and DECwindows workstation<           VR160, or VR295) capable      support with the 1009           of displaying 100 dots/inch   dots/inch option.eD           or a VAXstation 4000 series   By selecting the workstation:           computer, which uses 100      support files, you<           dots/inch video fonts by      automatically get 75C           default                       dots/inch video font files,   @                                         and you will be promptedB                                         to indicate if you want toC                                         install 100 dots/inch video E           ______________________________font_files.__________________p  /           The procedure displays the following:u  M You can select DECwindows support now, or you can use the DECW$TAILOR utility ? to provide or remove DECwindows support after the installation.   J Some media, TK50s in particular, can be very slow when tailoring on files.L You might want to select DECwindows now and tailor off unwanted files later.0 NOTE: This kit does NOT contain full DECwindows.= To obtain full DECwindows, you must also install the separatee2 layered product, DECwindows Motif for OpenVMS VAX.H Version 1.2-3 is the minimum version of DECwindows Motif for OpenVMS VAX' that can be used with OpenVMS VAX V7.3.e  D The DECwindows components provided in this kit require approximately% 34400 blocks, broken down as follows:a  O                    o DECwindows base support                    -   4400 blocks O                    o DECwindows workstation support             -  23800 blockspO                      -  75 dots per inch video fonts                 (included)pO                      - 100 dots per inch video fonts (optional) -   6200 blocksf  E                     Installing the OpenVMS VAX Operating System  3-17s l         + Installing the OpenVMS VAX Operating SystemS 3.2 Creating the System Disk    @            You must select the DECwindows base support option if8                - you plan to run DECwindows software, or/                - you are installing this kit onB%                    * a workstation ora@                    * a VAXcluster that contains workstations, or?                - you want to provide font files for Xterminals.u  K         If you are installing this kit on a system that includes XterminalstP         and you do NOT select DECwindows base support, then you will have to use6         the DECW$TAILOR utility to provide font files.  8       * Do you want the DECwindows base support? (Y/N) y  *            Space remaining: 1908594 blocks  G            You must select the DECwindows workstation support option if /                - you are installing this kit ona%                    * a workstation ork@                    * a VAXcluster that contains workstations, or?                - you want to provide font files for Xterminals.d  K         If you are installing this kit on a system that includes XterminalsnP         and you do NOT select DECwindows base support, then you will have to use6         the DECW$TAILOR utility to provide font files.  F       * Do you want to install DECwindows workstation support? (Y/N) y  +            Space remaining:  1884794 blocksr  P        DECwindows workstation support includes the 75 dots per inch video fonts.  I        All DECwindows applications run with 75 dots per inch video fonts.hK        By default, most systems start up with 75 dots per inch video fonts.tP        Certain applications can take advantage of 100 dots per inch video fonts.  P            For the VAXstation 4000 series machine, 100 dots per inch video fontsO            are used by default.  If you decide not to install 100 dots per inchlO            video fonts, you must edit SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COMeO            to force 75 dots per inch video fonts to be the default.  Otherwise,v<            certain applications may not space text properly.  K       For instructions on how to configure your system with both 75 and 100 J       dots per inch video fonts, see the installation guide or look at theP       template command procedure SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE.  C       *Do you want 100 dots per inch video fonts installed? (Y/N) nl  1 3-18  Installing the OpenVMS VAX Operating Systemy w         D                          Installing the OpenVMS VAX Operating SystemE                                          3.2 Creating the System Diskh    (     3.2.9 Installing Networking Products  E           Next, the procedure displays messages describing the DECnet E           options. The OpenVMS VAX Version 7.3 installation procedure E           allows you to install either Compaq DECnet-Plus for OpenVMS E           VAX or DECnet Phase IV for OpenVMS VAX networking software.eA           However, you cannot have both DECnet products installedYD           concurrently on your system. Install either Compaq DECnet-B           Plus for OpenVMS VAX or DECnet Phase IV for OpenVMS VAX.  P            Beginning with OpenVMS V7.1, the DECnet-Plus kit is provided with the9            OpenVMS operating system kit.  Compaq strongly M            recommends that DECnet users install DECnet-Plus.  DECnet Phase IVs5            applications are supported by DECnet-Plus.r  P               DECnet Phase IV is also provided as an option.  Support for DECnetL               Phase IV is available through a Prior Version Support Contract4               available through Compaq MCS Services.  F               If you install DECnet-Plus and TCP/IP you can run DECnetI               applications over a TCP/IP network.  Please see the OpenVMS_M               Management Guide for information on running DECnet over TCP/IP.a  P               If you plan to install DECnet Phase IV, do NOT select DECnet-Plus.  7           * Do you want to install DECnet-Plus. (Y/N) nn  ;           * Do you want to install DECnet Phase IV? (Y/N) y   =               Space remaining on system disk:  1883994 blocks   B             ________________________ Note ________________________  A             If you select Compaq DECnet-Plus for OpenVMS VAX, you @             will not be prompted for DECnet Phase IV for OpenVMS             VAX.  B             ______________________________________________________  E           Once you have Compaq DECnet-Plus for OpenVMS VAX and TCP/IP C           installed on your system, you can run DECnet applicationsa@           over your TCP/IP network. Refer to the DECnet-Plus forD           OpenVMS Management Guide for more information about DECnet           over TCP/IP.  E                     Installing the OpenVMS VAX Operating System  3-19     _      + Installing the OpenVMS VAX Operating System_ 3.2 Creating the System Disk     3.2.10  Verifying Your Choices  A       The procedure displays a list of OpenVMS VAX and DECwindows.9       support options you have selected and gives you thed:       opportunity to change your mind before proceeding by'       displaying the following message:V         * Is this correct? (Y/N)  8       If you answer No to this prompt, you can respecify<       the OpenVMS and DECwindows support options you want to       install.  " 3.2.11  Installing OpenVMS Options  ;       If you answer Yes to the prompt in Section 3.2.9, thehA       installation procedure begins restoring the OpenVMS options >       you have selected. After the installation has completed,>       you can use the VMSTAILOR utility to remove any optional?       OpenVMS files that you do not need. (For more information -       about using VMSTAILOR, see Chapter 10.)u  =       This step in the procedure varies, depending on whetherr@       your distribution kit is on compact disc, tape cartridges,       or magnetic tapes.   3.2.11.1  Compact Disc  <       If your distribution kit is on compact disc, leave the>       disc in the drive. The procedure displays messages as it=       restores each of the OpenVMS options you have chosen to        install.  * 3.2.11.2  Magnetic Tape and Tape Cartridge  A       If your distribution kit is contained on open reel magnetic >       tapes or TK50 CompacTape cartridges, you may be asked to>       mount the second volume of the kit. If you need to mount;       the second volume, your system will display a message        similar to the following:o  :       Please mount volume 2 of the OpenVMS kit on <device>  <       where: <device> is the magnetic tape or tape cartridge       drive.  1 3-20  Installing the OpenVMS VAX Operating System            D                          Installing the OpenVMS VAX Operating SystemE                                          3.2 Creating the System Diski    <           The system displays one of the following messages:  B           o  For a 9-track open reel magnetic tape, the message is&              similar to the following:  P           * Is the volume labeled OVMS VAX V7.3 BIN MT9 2/2 ready to be mounted?  D           o  For a TK50 CompacTape cartridge, the message is similar              to the following:  P          * Is the volume labeled OVMS VAX V7.3 BIN TK50 2/2 ready to be mounted?  9           To respond to either message, do the following:i  6           1. Unload the volume currently in the drive.  B           2. Examine the remaining volumes and select the one with>              the label that matches the label specified in the              prompt.  6           3. Load the volume and make the drive ready.  (           4. Answer YES to the question.  A           For information on which save sets are located on whichn/           tape volumes, refer to Section 1.3.2.d  1     3.2.12 Installing DECwindows Support Software   B           If you are installing DECwindows software, the procedure@           installs the DECwindows options that you specified and5           displays messages similar to the following:d  <               Restoring DECwindows base support save set ...;           %BACKUP-I-STARTVERIFY, starting verification passs  C               Restoring DECwindows workstation support save set ...i;           %BACKUP-I-STARTVERIFY, starting verification passd  F               Restoring DECwindows 75 dots per inch fonts save set ...;           %BACKUP-I-STARTVERIFY, starting verification pass   @           The DECwindows support files are listed in Appendix E.<           After you finish the installation, you can use theB           DECwindows tailoring utility, DECW$TAILOR, to remove the@           DECwindows files you do not need. For more information@           about removing files with DECW$TAILOR, see Chapter 10.  E                     Installing the OpenVMS VAX Operating System  3-21y w         + Installing the OpenVMS VAX Operating SystemS7 3.3 Installing DECnet Phase IV for OpenVMS VAX Softwaree    8 3.3  Installing DECnet Phase IV for OpenVMS VAX Software  =       If you chose to install DECnet Phase IV for OpenVMS VAXs;       earlier in the installation procedure, it will now beo       installed.  >       The procedure displays messages similar to the following@       and prompts you for information it needs to install DECnet       Phase IV for OpenVMS VAX:T  (            Installing DECnet Phase IV...2       %MOUNT-I-MOUNTED, VMS073 mounted on _MKB500:  .       The following product has been selected:E            DEC VAXVMS DECNET_PHASE_IV V7.3            Layered Productg  &       Configuration phase starting ...  O  You will be asked to choose options, if any, for each selected product and forwP  any products that may be installed to satisfy software dependency requirements.  6       DEC VAXVMS DECNET_PHASE_IV V7.3: DECNET_PHASE_IV  ;            COPYRIGHT (c)  4-JAN-2000 -- All rights reservedi  &            Compaq Computer Corporation  =       * This product does not have any configuration options.a  H            Support addendum to DECnet Phase IV service contract required  )            Do you want to continue? [YES]E  "       Execution phase starting ...  .       The following product will be installed:B            DEC VAXVMS DECNET_PHASE_IV V7.3         Layered Product  A       Portion done: 0%...10%...20%...30%...40%...80%...90%...100?y  /       The following product has been installed:eB            DEC VAXVMS DECNET_PHASE_IV V7.3         Layered Product  9       If your distribution media is magnetic tape or tapeT=       cartridges, the procedure displays a message similar todA       the following after the options you have selected have beenw       successfully installed:   ;       You can now remove the distribution kit from MKB500:.   3       Remove the distribution media from the drive.h  1 3-22  Installing the OpenVMS VAX Operating System     e      D                          Installing the OpenVMS VAX Operating SystemE               3.3 Installing DECnet Phase IV for OpenVMS VAX Softwares    E           If your distribution media is compact disc, leave it in theC           drive.       3.4 Configuring a Cluster   C           The installation procedure now displays information about A           cluster configuration. But, because there is no network B           present on the system at this point in the procedure, noA           cluster configuration work can actually be performed ati           this time.  M           In a cluster, you can run multiple systems sharing all files exceptCE           PAGEFILE.SYS, SWAPFILE.SYS, SYSDUMP.DMP, and VAXVMSSYS.PAR.n  N           Cluster configuration cannot be done at this time because no networkL           is present. In order to configure a cluster, you must FIRST do one#           or both of the following:   <               o Install DECnet-Plus (or DECnet Phase IV), orC               o Execute SYS$STARTUP:LAN$STARTUP.COM by removing the 5                 comment delimiter ("!") from the lineh  6                       $! @ SYS$STARTUP:LAN$STARTUP.COM  1                 in SYS$MANAGER:SYSTARTUP_VMS.COM.y  H           Then configure the cluster by executing the following command:  5                       @SYS$MANAGER:CLUSTER_CONFIG.COM   P        See the OpenVMS System Manager's Manual: Essentials for more information.  E           Once the network is running on your system, you can execute_A           the SYS$MANAGER:CLUSTER_CONFIG.COM command procedure toDD           configure your cluster. For more information about cluster>           configuration, refer to the OpenVMS System Manager's'           Manual, Volume 1: Essentials._  .     3.5 Selecting the Default Windowing System  @           The procedure now lets you specify a default windowingD           system. If you want to select DECwindows Motif for OpenVMS@           VAX as the default windowing system, answer yes to the           following question:E  O           * Do you want DECwindows Motif as the default windowing system? (Y/N)a  E                     Installing the OpenVMS VAX Operating System  3-23s _  .      + Installing the OpenVMS VAX Operating Systemo 3.6 Setting Passwords      3.6  Setting Passwords  9       Next, the installation procedure prompts you to sets?       passwords for the SYSTEM, SYSTEST, and FIELD accounts and 8       uses this information to create a rights database.  5       When setting the passwords, note the following:s  ?       o  Passwords must be at least eight characters in length;w+          they do not appear on the display.t  3       o  Press Return after you enter the password.y  ;       o  After you enter the password, the procedure checksl;          to make sure it meets the requirements for a valid           password.  /       o  Reenter the password for verification.   (       The following is a sample display:  L            Now we will ask you for new passwords for the following accounts:  ,                       SYSTEM, SYSTEST, FIELD  N           Passwords must be a minimum of 8 characters in length. All passwordsP           will be checked and verified. Any passwords that can be guessed easily           will not be accepted.i  "       * Enter password for SYSTEM:"       * Re-enter for verification:,       %UAF-I-MDFYMSG, user record(s) updated;       %VMS-I-PWD_OKAY, account password for SYSTEM verifiedl  #       * Enter password for SYSTEST:C"       * Re-enter for verification:,       %UAF-I-MDFYMSG, user record(s) updated<       %VMS-I-PWD_OKAY, account password for SYSTEST verified  H            The SYSTEST_CLIG account will be disabled. You must re-enable@            it before running UETP but do not assign a password.)  !       * Enter password for FIELD:t"       * Re-enter for verification:,       %UAF-I-MDFYMSG, user record(s) updated:       %VMS-I-PWD_OKAY, account password for FIELD verified  A       If there are no password errors, the procedure creates your ?       rights database, and you can proceed to the next section.   1 3-24  Installing the OpenVMS VAX Operating System            D                          Installing the OpenVMS VAX Operating SystemD                                                3.6 Setting Passwords    @           If you reenter a password incorrectly or if the systemC           determines that the password is too easy for another usereD           to guess, the system displays an error messages similar to           the following:  E           %VMS-I-PWD_INVALID, account password for SYSTEST is invalids8           %VMS-I-PWD_WEAK, password is too easy to guess  P     Because of the preceding error, you must take action to secure this account.J     You must either disable this account, change its password, or do both.  E           When the procedure asks if you want to disable the account,dA           type N and press Return. When the procedure asks if you E           want to enter a new password, type Y and press Return. Then ,           enter a new password. For example:  6           Do you want to disable this account (Y/N)? N=           Do you want to change the account password (Y/N)? YuP          You must now select a new primary password for the SYSTEST account. TheO          password you select must be at least 8 characters in length and cannotb0          be the same as the name of the account:             New password:i           Verification: 0           %UAF-I-MDFYMSG, user record(s) updatedB           %VMS-I-PWD_SET, primary password for account SYSTEST set  ;           When you have successfully set the passwords, theeD           installation procedure creates your rights database, whichE           lets you manage user access to the system, and displays the            following message:  B           Creating RIGHTS database file, SYS$SYSTEM:RIGHTSLIST.DATF           Ignore any "-SYSTEM-F-DUPIDENT, duplicate identifier" errors2           %UAF-I-RDBCREMSG, rights database create           .I           .t           .   3     3.7 Entering SCSNODE and SCSSYSTEMID Parameterss  7           The procedure displays the following prompts:i  &           * Please enter SCSNODE name:  %           * Please enter SCSSYSTEMID:a  E                     Installing the OpenVMS VAX Operating System  3-25n l  E      + Installing the OpenVMS VAX Operating Systeme/ 3.7 Entering SCSNODE and SCSSYSTEMID Parametersn    @       Enter the SCSNODE name and SCSSYSTEMID that you determined8       as part of the preinstallation tasks in Chapter 2.  % 3.8  Postinstallation Tasks DescribedV  9       After the procedure creates the rights database, itT=       displays messages describing postinstallation tasks your       might want to perform.  ?          ________________________ Note ________________________   ?          You do not perform these tasks now. Perform them afterh$          the installation completes.  ?          ______________________________________________________s  <       The tasks displayed on your screen might vary from the?       following example, depending on what options you chose to0'       install earlier in the procedure.m  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 systemoG         libraries are shipped in a data-compressed format.  If you have N         enough disk space, you can decompress the libraries for faster access.+         To data expand the libraries, type:   %           $ @SYS$UPDATE:LIBDECOMP.COM9  E         If you do not decompress these libraries, you will experience 6         slower response to the HELP and LINK commands.  M       o BUILD A STANDALONE BACKUP KIT - You can build a standalone BACKUP kit K         using the procedure described in the "Backup Procedures" chapter ofpO         the upgrade and installation supplement provided for your VAX computer.a  O       o TAILOR THE SYSTEM DISK - You might want to review the files provided oreJ         not provided during this installation. If you find there are filesN         you want to remove from the system disk (TAILOR OFF) or files you wantF         to add (TAILOR ON), use the following utilities to perform the         desired tailoring.  C           OpenVMS tailoring:             $ RUN SYS$UPDATE:VMSTAILOR   E           DECwindows tailoring:          $ RUN SYS$UPDATE:DECW$TAILORw  O         Note: The tailor procedure cannot be used to TAILOR ON or to TAILOR OFFs1               files located on an alternate disk.i  1 3-26  Installing the OpenVMS VAX Operating Systemg t         D                          Installing the OpenVMS VAX Operating SystemE                                  3.8 Postinstallation Tasks Described     =           For more information about decompressing the system B           libraries, see Section 4.7 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 V7.3 Installation Procedure.   5              Configuring all devices on the system...A  ;           Proceed to the next section for information aboutP$           registering your licenses.       3.9 Registering Licenses  E           Before you can use the OpenVMS VAX operating system and its E           components, you must register all licenses in the following C           order. If you do not register your licenses at this point D           in the procedure, you must register them immediately after?           the installation, before you perform postinstallationa           tasks.  E           1. Register the OpenVMS VAX license for the VAX computer on C              which you have just installed the operating system. IfdD              you have a VAXcluster environment, you then register anD              OpenVMS VAX license for each additional VAX computer inD              the cluster that will boot off the system disk that youC              just created. Each registered OpenVMS VAX license mustw=              be assigned to one of the nodes for the cluster.   E           2. Register the licenses for any System Integrated Products '              (SIPs) that you purchased.S  C           For more information about registering licenses, refer tot           the following:  =           o  OpenVMS License Management Utility Manual, whicha              provides:  C              -  Details about all LICENSE commands, error messages,s;                 and recovery procedures for licensing tasksr  B              -  A description of VMSLICENSE.COM, with step-by-step5                 instructions for registering licenses   E              -  Examples of license registration using VMSLICENSE.COMo-                 and LICENSE REGISTER commandst  E                     Installing the OpenVMS VAX Operating System  3-27p w         + Installing the OpenVMS VAX Operating Systeml 3.9 Registering Licenses    =       o  Appendix B of this manual for notes and supplemental (          information concerning licenses  <       You can use the SYS$UPDATE:VMSLICENSE.COM procedure to=       register a license for any Compaq product that suppliesn=       a Product Authorization Key (PAK). Or, you can registerc>       licenses with the LICENSE REGISTER command. Refer to the<       OpenVMS License Management Utility Manual for detailed       information.  $ 3.9.1  Types of OpenVMS VAX Licenses  @       The OpenVMS VAX operating system uses one of two different;       categories of licenses, depending on the hardware and >       software configuration used and currently supported. TheA       two categories of operating system licenses for OpenVMS VAXb
       are:         o  VAX VMS licensing         o  OpenVMS VAX licensing  =       The following table describes the types of licenses for:A       each licensing category. Compaq provides the proper licenseAA       type with the purchase of the system. Not all license typess+       are available for every system model.   A _________________________________________________________________ A Type_of_License_______Description________________________________   A _________________________VAX_VMS_Licenses________________________   < Traditional License   Provides unlimited use to the users on;                       a defined system. VAX VMS traditionaly>                       licenses are sized to capacity according%                       to system type.t                  1 3-28  Installing the OpenVMS VAX Operating System            D                          Installing the OpenVMS VAX Operating SystemE                                              3.9 Registering Licensese  E     _________________________________________________________________tE     Type_of_License_______Description________________________________   E     ________________________VAX_VMS_Licenses_________________________y  ?     Multi-User License    Provides use according to a specifieda@                           number of concurrent users. This is an@                           activity-based license. The Multi-User@                           License gives you the right to use the>                           operating system for up to the limit?                           of users specified in the license. An D                           operating system user is one who is loggedB                           in to the system or one who is using theB                           operating system software by means other>                           than login, or both. This license isB                           available only on limited system models,B                           primarily MicroVAX and VAX 4000 systems.  A                           Interactive use of VAX systems licensedd<                           with the Multi-User License can beB                           increased by the addition of the OpenVMS@                           VAX Individual User License[1] for one>                           or more users. For more information,A                           refer to the description of the OpenVMSrC                           VAX Individual User License later in this                             table.  A     VAX VMS Workstation   Provides use for a single user on a VAX C     License               workstation. This license type allows onenC                           direct login for the single user and thenSD                           one additional login for system management(                           purposes only.  ;                           Additional interactive use of VAX @                           workstations licensed with the VAX VMSC                           Workstation License requires the additionk?                           of an OpenVMS VAX User License[1] for_B                           one or more users. For more information,A                           refer to the description of the OpenVMSoC                           VAX Individual User License later in this_                            table.  E     [1]The_OpenVMS_VAX_Individual_User_License_is_not_supported_by___oA     the VMS or OpenVMS VAX operating system releases prior to VMSe     Version 5.5.  E                     Installing the OpenVMS VAX Operating System  3-29  l  n      + Installing the OpenVMS VAX Operating System  3.9 Registering Licenses  A _________________________________________________________________.A Type_of_License_______Description________________________________i  A _________________________VAX_VMS_Licenses________________________e  < File and Application  Provides for the noninteractive use of? Server License        OpenVMS VAX. OpenVMS based VAXservers arel=                       sold with a File and Application Server                        License.  >                       The intent of an OpenVMS based VAXserver=                       is to provide file, print, application, >                       and compute services to clients who haveA                       remotely submitted their requests for these A                       services. This license type also allows one A                       direct login for system management purposess                       only.a  ;                       Additional interactive use of OpenVMSp;                       VAXservers licensed with the File anda9                       Application Server License requires 9                       the addition of an OpenVMS VAX UserO@                       License[1] for one or more users. For more>                       information, refer to the description of=                       the OpenVMS VAX Individual User License *                       later in this table.  A _________________________________________________________________ A _______________________OpenVMS_VAX_Licenses______________________f  A [1]The_OpenVMS_VAX_Individual_User_License_is_not_supported_by___c= the VMS or OpenVMS VAX operating system releases prior to VMSA Version 5.5.                        1 3-30  Installing the OpenVMS VAX Operating Systemo a         D                          Installing the OpenVMS VAX Operating SystemE                                              3.9 Registering Licensesn  E     _________________________________________________________________tE     Type_of_License_______Description________________________________   E     ______________________OpenVMS_VAX_Licenses_______________________   =     OpenVMS VAX O/S Base  Provides the right to unrestricted,t?     License[2]            noninteractive use of the OpenVMS VAXo?                           operating system for the execution oft@                           remotely submitted requests for batch,E                           print, application, and computing services,s<                           on a designated, single processor.  @                           No direct OpenVMS VAX operating system>                           logins by users are permitted on theA                           system. One direct login is allowed forV:                           system management purposes only.  E                           Interactive use of systems licensed with an C                           OpenVMS VAX O/S Base License requires the D                           addition of an OpenVMS VAX Individual User;                           License[1] for one or more users.   A     OpenVMS VAX           Provides the right to interactively useaA     Individual User       the operating system by a specified, or B     License[1]            unlimited, number of concurrent users on@                           a designated, single processor. A user@                           is one who is logged in to a processor?                           or one who is interactively using the.B                           operating system software by means otherA                           than login, or both. An OpenVMS VAX O/SgC                           Base License, or any of the four types of E                           VAX VMS Licenses, is a prerequisite for thew>                           OpenVMS VAX Individual User License.  E     [1]The_OpenVMS_VAX_Individual_User_License_is_not_supported_by___sA     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 Version.E     5.5._____________________________________________________________d          E                     Installing the OpenVMS VAX Operating System  3-31  n  m      + Installing the OpenVMS VAX Operating System  3.9 Registering Licenses    + 3.9.2  How to Register OpenVMS VAX Licenseso  =       After you install the OpenVMS VAX operating system, thec,       system displays the following message:  O          If you have any Product Authorization Keys (PAKS) to register, you can           register them now.   E       * Do you want to register any Product Authorization Keys? (Y/N)   '       Respond to the prompt as follows:g  A       ___________________________________________________________uA       If_you_choose_..._______Then_...___________________________o  /       Not to register the     Do the following:_9       licenses at this time   1. Type N and press Return._  4                               2. Go to Section 3.12.  9                               3. Remember that, after the @                                  installation, you must register@                                  your licenses before performingA                                  any other postinstallation tasks 1                                  (see Chapter 4).-  /       To register your        Do the following: 9       licenses now            1. Type Y and press Return.   @                               2. Be sure you have a copy of your>                                  PAK for each license you will*                                  register.  @                               3. Go to the next section to begin9                                  the licensing procedure._A       ___________________________________________________________p  $ 3.9.3  Using the Licensing Procedure  ;       Entering Y (Yes) to register your licenses during thec8       installation invokes the SYS$UPDATE:VMSLICENSE.COM6       procedure, which displays the following message:      1 3-32  Installing the OpenVMS VAX Operating System            D                          Installing the OpenVMS VAX Operating SystemE                                              3.9 Registering Licenses     9               OpenVMS License Management Utility Options:   9                   1. REGISTER a Product Authorization Key @                   2. AMEND an existing Product Authorization KeyA                   3. CANCEL an existing Product Authorization Key 4                   4. LIST Product Authorization KeysA                   5. MODIFY an existing Product Authorization Key B                   6. DISABLE an existing Product Authorization KeyA                   7. DELETE an existing Product Authorization Key ?                   8. COPY an existing Product Authorization Key ?                   9. MOVE an existing Product Authorization Key A                  10. ENABLE an existing Product Authorization Key :                  11. SHOW the licenses loaded on this node=                  12. SHOW the unit requirements for this node   (                  99. Exit this procedure  I               Type '?' at any prompt for a description of the information K               requested. Press Ctrl/Z at any prompt to return to this menu.   ,           Enter one of the above choices [1]  A           1. Select the appropriate options (beginning with 1, as B              indicated in the display) until you have successfully*              registered all required PAKs.  @           2. After you register all your licenses, exit from the@              License Management procedure by entering option 99.  4     3.9.4 How to Register System Integrated Products  >           After you register the OpenVMS VAX license, you must>           register the license for any of the following System8           Integrated Products (SIPs) you have purchased:             o  VAXcluster_+              (LMF Product Name: VAXCLUSTER)   '           o  RMS Journaling for OpenVMSs'              (LMF Product Name: RMSJNL)   >              On systems that do not have registered and loadedA              journaling licenses, users cannot write to any filesi#              marked for journaling._  )           o  Volume Shadowing for OpenVMS_(              (LMF Product Name: VOLSHAD)  E                     Installing the OpenVMS VAX Operating System  3-33_ _  _      + Installing the OpenVMS VAX Operating Systemf 3.9 Registering Licenses    8          You must register and load a license for Volume8          Shadowing for OpenVMS on each node using volume@          shadowing, including satellites in a VAXcluster system.  & 3.9.5  How to Register DECnet Products  >       You must also register the license for any of the DECnet@       products you have purchased. There are two DECnet licenses?       that apply to both Compaq DECnet-Plus for OpenVMS VAX and &       DECnet Phase IV for OpenVMS VAX:  ,       o  The end node license named DVNETEND  0       o  The routing node license named DVNETRTG  @          All routing nodes must have a routing license. Each end>          node can have either an end node license or a routingA          license. If neither license is registered and activated,n?          DECnet does not start and your use is limited to localX;          DECnet only (SET HOST 0). If DECnet for OpenVMS iss>          running when you register your license, you must stop          and then restart it.   >          You can control which VAXcluster nodes have access to>          each license. Using the LICENSE MODIFY/INCLUDE=(node-?          name[,node-name,...]) command, you can assign licensesc>          to nodes and limit access as needed. For example, youA          can assign a routing node license to only one VAXclusterg?          node and assign the end node licenses to the remaining A          VAXcluster nodes. If you choose this approach, make sure ?          you assign a license to each end node license. Specifyy=          include lists for each license of the same type. ForiA          details, refer to the OpenVMS License Management Utility_          Manual.  $ 3.10  Updating Time Zone Information  ?       At this point in the installation, the procedure asks youM@       for information that is used for providing local time zone=       support. For local time zone support to work correctly, <       the installation procedure must set the time zone thatA       accurately describes the location you want to be considered ?       as your default time zone. Usually, this is the time zone ?       in which your system is running. In addition, your system >       must be correctly configured to use a valid OpenVMS time        differential factor (TDF).  1 3-34  Installing the OpenVMS VAX Operating Systems           D                          Installing the OpenVMS VAX Operating SystemE                                   3.10 Updating Time Zone Information     @           The procedure displays a series of time zone menus and<           prompts you to make selections from each. Begin byA           selecting the desired time zone from the main time zonev@           menu. If you do not select a time zone, the default is$           Greenwich Mean Time (GMT).  ?           If you choose a time zone that has subcomponents, thehA           system displays an additional menu. For example, if younE           choose the United States (US) time zone from the main menu,iC           a second menu displays the specific time zones within theo@           United States. You then select the menu item that best+           represents the desired time zone.   @           The procedure then prompts you for the TDF. The TDF isA           the difference between your system time and Coordinated B           Universal Time (UTC), which is an international standard@           (similar to Greenwich Mean Time) for measuring time ofA           day. The procedure supplies a default for TDF, which ise)           generally the correct response._  4           You can choose from the following options:  ?           o  Exit the time zone procedure without setting a TDFV             o  Set a TDF  5           o  Display the TDF for your local time zonee  ,           The following is a sample display:  O           %UTC-I-UPDTIME, updating Time Zone information in SYS$COMMON:[SYSEXE]   -               Configuring the Local Time Zone3  <               TIME ZONE SPECIFICATION -- Main Time Zone Menu  I     1) Australia       11) GMT             21) Mexico          31) Turkey F     2) Brazil          12) Greenwich       22) NZ              32) UCTE     3) CET             13) Hong Kong       23) NZ-CHAT         33) USuF     4) Canada          14) Iceland         24) Navajo          34) UTCL     5) Chile           15) Iran            25) PRC             35) UniversalG     6) Cuba            16) Israel          26) Poland          36) W-SU_F     7) EET             17) Jamaica         27) ROC             37) WETG     8) Egypt           18) Japan           28) ROK             38) Zulu 8     9) Factory         19) Libya           29) Singapore7     10) GB-Eire         20) MET             30) SystemVG  $                 0) None of the above  E                     Installing the OpenVMS VAX Operating System  3-35  s  l      + Installing the OpenVMS VAX Operating System # 3.10 Updating Time Zone Informationg    C       Select the number above that best describes your location: 33   (       You selected US as your time zone.&       Is this correct? (Yes/No) [YES]:             US Time Zone Menun  J    1) Alaska           4) Central          7) Hawaii          10) MountainI    2) Aleutian         5) East-Indiana     8) Indiana-Starke  11) PacificeG    3) Arizona          6) Eastern          9) Michigan        12) Samoa   !              0) None of the aboven  B       Select the number above that best describes your location: 6  0       You selected US/Eastern as your time zone.&       Is this correct? (Yes/No) [YES]:  F           Default Time Differential Factor for standard time is -5:00.M           Default Time Differential Factor for daylight saving time is -4:00.   K           The Time Differential Factor (TDF) is the difference between yourOK           system time and Coordinated Universal Time (UTC).  UTC is similarn7           in most repects to Greenwich Mean Time (GMT).   J           The TDF is expressed as hours and minutes, and should be enteredF           in the hh:mm format.  TDFs for the Americas will be negativeK           (-3:00, -4:00, etc.); TDFs for Europe, Africa, Asia and Australiao.           will be positive (1:00, 2:00, etc.).  7       Is Daylight Savings time in effect? (Yes/No): yes   1       Enter the Time Differential Factor [-4:00]:F  6           NEW SYSTEM TIME DIFFERENTIAL FACTOR = -4:00.         Is this correct? [Y]:t  A       For more information about TDF and local time zone support,u3       refer to the OpenVMS System Manager's Manual.n  < 3.11  Installing Compaq DECnet-Plus for OpenVMS VAX Software  <       If you chose to install Compaq DECnet-Plus for OpenVMS;       VAX, the procedure will now install it. The procedure <       displays messages similar to the following and prompts@       you for information it needs to install Compaq DECnet-Plus       for OpenVMS VAX.  1 3-36  Installing the OpenVMS VAX Operating System  o  t      D                          Installing the OpenVMS VAX Operating SystemE           3.11 Installing Compaq DECnet-Plus for OpenVMS VAX SoftwareS    ,           DECnet-Plus will now be installed.  E               Media containing the DECnet-Plus kit must be available.   E               If you are installing OpenVMS from an InfoServer (DAD1)eH               or local CD-ROM, there is a DECnet-Plus kit on the CD-ROM.  C               If you are installing from a cartridge tape (TK50) oreG               from an open reel tape, you should have a DECnet-Plus kitu2               on cartridge tape or open reel tape.  E               An appropriate DECnet-Plus kit may also be available on E               the Consolidated Distribution CD-ROM, or you may have a '               separate DECnet-Plus kit.M  >               NOTE: You may choose any available media for theC               DECnet-Plus kit.  It is NOT NECESSARY to use the same A               type of media that is contained in the OpenVMS kit.   G               If you do not have a DECnet-Plus kit available, or if youMF               have decided NOT to install/upgrade DECnet-Plus, you canD               bypass the DECnet-Plus installation by entering "EXIT"B               for the "name of drive holding the DECnet-Plus kit".  C           * Enter name of drive holding the DECnet-Plus kit: dkb200 1           * Is DKB200: ready to be mounted? [N] yn  2           The following product has been selected:F               DEC VAXVMS DECNET_OSI V7.3               Layered Product  *           Configuration phase starting ...  O  You will be asked to choose options, if any, for each selected product and for P  any products that may be installed to satisfy software dependency requirements.  G            DEC VAXVMS DECNET_OSI V7.3: DECnet-Plus V7.3 for OpenVMS VAXR  P               Copyright  Compaq Computer Corporation 2000. All rights reserved.  )               Compaq Computer Corporationu  J               This product requires one of two PAKs: DVNETEND or DVNETRTG.  9           Do you want the defaults for all options? [YES]   5           Do you want to review the options? [NO] yesi  E                     Installing the OpenVMS VAX Operating System  3-37  a  t      + Installing the OpenVMS VAX Operating SystemV; 3.11 Installing Compaq DECnet-Plus for OpenVMS VAX Softwaret    B       DEC VAXVMS DECNET_OSI V7.3: DECnet-Plus V7.3 for OpenVMS VAX)           DEC VAXVMS VMS V7.3 [Installed]e2           VAX P.S.I. or P.S.I. Access software: NO*           VAX Wide Area Device Drivers: NO$           DECdns Server software: NO$           DECdts Server software: NO  1       Are you satisfied with these options? [YES]i  "       Execution phase starting ...  .       The following product will be installed:B           DEC VAXVMS DECNET_OSI V7.3               Layered Product  A       Portion done: 0%...10%...20%...30%...40%...80%...90%...100%   /       The following product has been installed:nB           DEC VAXVMS DECNET_OSI V7.3               Layered Product  =       To complete the installation procedure, continue to thee!       next section, Section 3.12.e   3.12  Running AUTOGENy  >       The remaining portion of the installation procedure runs9       AUTOGEN to evaluate your hardware configuration andi;       estimate typical work loads. AUTOGEN then sets system >       parameters, the sizes of page, swap, and dump files, and>       the contents of VMSIMAGES.DAT. When AUTOGEN finishes and;       you reboot your system, the installation procedure isl       complete.V  A       The installation procedure displays messages similar to then       following:  A          Running AUTOGEN to compute the new SYSTEM parameters ...e  1     %AUTOGEN-I-BEGIN, GETDATA phase is beginning.aP     %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.o            .            .            .  0     %AUTOGEN-I-BEGIN, REBOOT phase is beginning.  1 3-38  Installing the OpenVMS VAX Operating System     y      D                          Installing the OpenVMS VAX Operating SystemE                                                  3.12 Running AUTOGENm    B           If you need to create or modify the size of the pagefileD           or swapfile, use the SYSMAN utility. For more information,A           refer to the OpenVMS System Manager's Manual, Volume 1:t           Essentials.   )     3.12.1 Automatic Reboot after AUTOGEN   C           After AUTOGEN finishes, the system shuts down, displayingo,           messages similar to the following:  J           The system is shutting down to allow the system to boot with theB           generated site-specific parameters and installed images.  I           The system will automatically reboot after the shutdown and theh#           upgrade will be complete.   =                SHUTDOWN -- Perform an Orderly System Shutdownf  &     3.12.2 Manual Reboot after AUTOGEN  A           If the system does not reboot automatically, reboot theT           system manually.  @           For example, if you have a VAX-11/780 computer and theD           system disk is on an RA60 disk drive with a unit number of:           1, enter the following command and press Return:             >>> B DUA1  <           After the system reboots, a message similar to the!           following is displayed:   K           *****************************************************************N           OpenVMS VAX V7.3  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.1  K           *****************************************************************b  B           For more information about booting, refer to the upgradeA           and installation supplement for your VAX computer, then             return to this manual.  E                     Installing the OpenVMS VAX Operating System  3-39a g  s      + Installing the OpenVMS VAX Operating System  3.12 Running AUTOGEN    ?          ________________________ Note ________________________s  <          If you did not register your OpenVMS VAX license as9          described in Section 3.9, the procedure displaysa:          warning messages that the OpenVMS license must be>          registered. Be sure to register this license when the?          installation procedure finishes. For more information,o8          see Appendix B and refer to the OpenVMS License#          Management Utility Manual.o  ?          ______________________________________________________   9       The system next displays informational messages andi=       accounting information indicating that your OpenVMS VAXe/       operating system is running. For example:g  P       %SET-I-INTSET, login interactive limit = 64, current interactive value = 0=         SYSTEM       job terminated at 13-NOV-2000 13:58:16.1i        Accounting information:K        Buffered I/O count:       859      Peak working set size:        565eK        Direct I/O count:         478      Peak virtual size:           2570fK        Page faults:             5003      Mounted volumes:                0)K        Charged CPU time:  0 00:00:19.33   Elapsed time:       0 00:00:41.24:  @       At this time, you can log in to the SYSTEM account (so you>       can perform postinstallation tasks), as described in the       following sections.   > 3.13  Logging in to the SYSTEM Account by Means of a Character       Cell Terminali  >       Log in to a character cell terminal by entering the user:       name SYSTEM followed by the password. The display is       similar to the following:e  &            Welcome to OpenVMS VAX V7.3         Username: SYSTEM       Password:e            .            .            ..            Welcome to OpenVMS VAX Version V7.3  >       (If you forget your password, follow the instructions in?       the OpenVMS System Manager's Manual, Volume 1: EssentialsV'       to perform an emergency startup.)   1 3-40  Installing the OpenVMS VAX Operating Systemr n  y      D                          Installing the OpenVMS VAX Operating SystemE       3.14 Logging in to the SYSTEM Account by Means of a Workstationi    C     3.14 Logging in to the SYSTEM Account by Means of a Workstationy  ?           If you installed the DECwindows Motif for OpenVMS VAX B           software on your workstation, do the following after the/           login window displays on your screen:p  A           1. Enter the user name SYSTEM followed by the password.   $           2. Click on the OK button.       3.15 What to Do Next  ?           After you have successfully installed the OpenVMS VAXbC           operating system and logged in to the SYSTEM account, youyD           must perform certain postinstallation tasks before you canD           use the system. For complete information, go to Chapter 4.                                                          E                     Installing the OpenVMS VAX Operating System  3-41  f  u                    E                                                                     4tE     _________________________________________________________________i  E                     After Installing the OpenVMS VAX Operating Systemi    D           After you have installed the OpenVMS VAX operating system,D           you need to perform several important tasks to prepare theD           system for operation. This chapter describes the following?           postinstallation tasks in the order you perform them:   "           o  Verifying system time  !           o  Registering licensest  (           o  Backing up your system disk  $           o  Customizing your system  9           o  Configuring and starting networking softwareD             o  Testing the systeml  +           o  Decompressing system librariesi  $           o  Removing unwanted files  (           o  Installing layered products  2           o  Backing up the customized system disk             o  Running AUTOGEN  6           o  Completing the postinstallation checklist  ?           If you are an experienced system manager, you can use[A           the checklist at the end of the chapter to complete theg+           necessary postinstallation tasks.O  ;           If you are a system manager with less OpenVMS VAXsA           experience, you should read the entire chapter and thenEC           use the checklist to make sure you have completed all thel!           postinstallation tasks..  E                 After Installing the OpenVMS VAX Operating System 4-1  E  s      1 After Installing the OpenVMS VAX Operating SystemO 4.1 Verifying System Time      4.1  Verifying System Time  <       During the installation, the procedure prompted you to?       enter the date and time. Now that you have installed your @       system, verify that the system time is correct by entering       the following command:         $ SHOW TIMEd  ?       The system displays the date and time. If the time is not >       correct, reset it by entering the command SET TIME using       the following format:   #       SET TIME=dd-mmm-yyyy:hh:mm:ss2         For example:  %       $ SET TIME=27-MAY-2000:18:35:30l                                                      6 4-2  After Installing the OpenVMS VAX Operating System d  A      E                     After Installing the OpenVMS VAX Operating System E                                         4.2 Registering Your Licensesa    !     4.2 Registering Your Licensesn  @           The installation procedure gave you the opportunity to@           register any software product licenses. If you did notE           register your OpenVMS VAX license at that time, you must do E           so before you can use the OpenVMS VAX operating system. YouED           must register the licenses for any of the following System1           Integrated Products you have purchased:I                VAXclusterc/              OpenVMS RMS Journaling for OpenVMS )              Volume Shadowing for OpenVMST  <           You must also register the licenses for any of the7           following DECnet products you have purchased:l  /              Compaq DECnet-Plus for OpenVMS VAX ,              DECnet Phase IV for OpenVMS VAX  C           For step-by-step instructions about registering licenses,hD           refer to the OpenVMS License Management Utility Manual and$           Appendix B in this manual.  #     4.3 Backing Up Your System Diskt  C           After you install the operating system, protect your work E           by making a backup copy of the system disk in case you have ,           any problems during customization.  :           Compaq recommends that you perform the following           operations:   C           o  Make a standalone BACKUP kit on the system disk and on               removable media.e  =           o  Perform a standalone BACKUP of your system disk.e  B           In addition to backing up the system disk now before youA           customize it, you should back up your system disk againeC           after you successfully complete your customization tasks.l  A           For complete information about backup operations, refereA           to the upgrade and installation supplement for your VAX 2           computer and the system manager's guide.  E                 After Installing the OpenVMS VAX Operating System 4-3  e  g      1 After Installing the OpenVMS VAX Operating System  4.4 Customizing the System     4.4  Customizing the System*  =       You can customize the system to meet your site-specificC;       needs. In addition, if your VAX computer is part of a :       VAXcluster environment, you must prepare the cluster,       environment and configure the cluster.  :       For instructions on customizing the system, read the       following documentation:  ?       o  The chapter on booting in the upgrade and installationi@          supplement for your VAX computer. This chapter explainsA          the different ways to boot the system. It also tells youm%          how to shut down the system.g  A       o  If the computer is part of a VAXcluster environment, thee?          OpenVMS Cluster Systems Manual for further information $          about setting up a cluster.  A       o  The release notes, for notes and restrictions that mightA1          be relevant to your customization plans.e  7       o  The OpenVMS System Manager's Manual, Volume 1:e=          Essentials for instructions on customizing and usingtA          your system. It contains information about the following           tasks:o  4          -  Editing the template files SYCONFIG.COM,>             SYLOGICALS.COM, SYLOGIN.COM, and SYSTARTUP_VMS.COM  ;          -  Starting the queue manager and creating a queuem<             database. (If you are installing on a VAXcluster;             system with multiple system disks, refer to the A             OpenVMS Cluster Systems for additional instructions.)r  $          -  Setting up user accounts  '          -  Adjusting system parameterse  =       o  If you plan to use either the Compaq DECnet-Plus for ?          OpenVMS VAX product or the DECnet Phase IV for OpenVMS <          VAX product included on the OpenVMS VAX Version 7.3>          kit, read Section 4.5 and perform the steps described@          there. If you are installing the Compaq DECnet-Plus for?          OpenVMS VAX software, also refer to the Compaq DECnet- <          Plus for OpenVMS VAX installation and configuration          documentation.t  6 4-4  After Installing the OpenVMS VAX Operating System 3  o      E                     After Installing the OpenVMS VAX Operating System E                                            4.4 Customizing the System     D           o  If you installed DECwindows support software, there areE              several steps you must take to customize your DECwindowse@              environment. Depending on your configuration, these!              tasks might include:A  .              -  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 Compaq  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 G for information about preparingE              your OpenVMS system and your PC to use this application.   4     4.5 Configuring and Starting Networking Software  D           You can use either TCP/IP or DECnet as a single networking@           backbone, or your environment may concurrently includeB           both protocols. Compaq TCP/IP Services for OpenVMS is anB           industry-standard implementation of TCP/IP protocols andE           services that provide interoperability and resource sharing C           between OpenVMS, UNIX, Windows NT, and other systems that            support TCP/IP.   =           TCP/IP is the primary network strategy for OpenVMS.e>           However, you can also use the Compaq DECnet-Plus forA           OpenVMS VAX or DECnet Phase IV for OpenVMS VAX software_>           included on the OpenVMS VAX Version 7.3 kit. (CompaqA           DECnet-Plus for OpenVMS VAX is required for DECnet overeC           TCP/IP.) These networking products require that you run asB           configuration procedure to configure the network. If youD           choose to run the DECnet Phase IV for OpenVMS VAX product,E           you must also edit your system startup file as described inm           Section 4.5.2.          E                 After Installing the OpenVMS VAX Operating System 4-5o s  e      1 After Installing the OpenVMS VAX Operating System 0 4.5 Configuring and Starting Networking Software     4.5.1  Configuring Your System  @       After you have registered your DECnet license, execute one<       of the following interactive configuration procedures:  >       o  For the DECnet Phase IV for OpenVMS VAX software, run<          SYS$MANAGER:NETCONFIG.COM. (Refer to the DECnet for;          OpenVMS Guide to Networking for more information.)t  ;       o  For the Compaq DECnet-Plus for OpenVMS VAX layered ;          product, run SYS$MANAGER:NET$CONFIGURE.COM. (Refera>          to the DECnet-Plus for OpenVMS Installation and Basic4          Configuration manual for more information.)   4.5.2  Editing SYSTARTUP_VMS  @       If you plan to run Compaq DECnet-Plus for OpenVMS VAX, you=       do not need to edit this file because DECnet will startl       automatically.  9       If you plan to run DECnet Phase IV for OpenVMS VAX,V:       after you start the queue manager, edit the commands=       in SYS$COMMON:[SYSMGR]SYSTARTUP_VMS.COM that pertain top>       networking, so that DECnet starts automatically when you>       boot the system. Choose one of the following commands to<       start the network and remove the comment delimiter (!)       from that command:  I $! IF F$SEARCH("SYS$SYSTEM:NETACP.EXE").NES."" THEN @SYS$MANAGER:STARTNETrO $! IF F$SEARCH("SYS$SYSTEM:NETACP.EXE").NES."" THEN SUBMIT SYS$MANAGER:STARTNET   :       Both of the previous commands perform the same task.A       However, the first command executes STARTNET.COM and delays >       further processing until the procedure is completed; the@       second submits STARTNET.COM to a batch queue and continuesA       executing SYSTARTUP_VMS.COM. If you plan to run both DECnet ?       Phase IV for OpenVMS VAX and DECwindows Motif for OpenVMSo;       VAX, you must also edit SYS$COMMON:[SYSMGR]SYSTARTUP_ 9       VMS.COM to add a comment delimiter (!)  immediately ?       following the dollar-sign ($)  in the DEFINE DECW$IGNORE_e        DECNET command as follows:  '       $! DEFINE DECW$IGNORE_DECNET TRUEA  ?       If you are not going to start DECnet Phase IV for OpenVMSa8       VAX or have not yet started it, this command tells(       DECwindows not to wait for DECnet.  6 4-6  After Installing the OpenVMS VAX Operating System           E                     After Installing the OpenVMS VAX Operating SystemcE                                      4.6 Testing the System with UETPh    $     4.6 Testing the System with UETP  @           The User Environment Test Package (UETP) is a software:           package designed to test whether the OpenVMS VAXA           operating system is installed correctly. As part of theaD           postinstallation procedure, Compaq recommends that you run*           UETP to verify the installation.  ?           Note that UETP needs at least 1200 free blocks on the @           system disk and is available only if you installed the@           optional save set VMS073.D. If you did not install the?           optional save set, you can add the UETP files to yourM!           system using VMSTAILOR.s  @           For information about using VMSTAILOR, see Chapter 10.  A           For complete information about using UETP, refer to thet*           OpenVMS System Manager's Manual.  *     4.7 Decompressing the System Libraries  D           Decompressing the system libraries gives the system fasterE           access to them. You can decompress all the system librariescC           or just some of them. You use the LIBDECOMP.COM procedurep&           to decompress the libraries.        4.7.1 Determining Disk Space  =           To find out how much disk space you have, enter the -           following command and press Return:S  %           $ SHOW DEVICE SYS$SYSDEVICEh  D           The additional amount of disk space required to decompress:           all the system libraries is about 13,500 blocks.  C           Table 4-1 gives the approximate number of blocks consumedo.           by each library after decompression.  E           Table_4-1_Sizes_of_Decompressed_System_Libraries___________t  E           Library___________Blocks______Library___________Blocks_____o  >           HELPLIB.HLB       9108        EDFHLP.HLB         102  >           STARLET.OLB       8442        TPUHELP.HLB       1038  E                                              (continued on next page)y  E                 After Installing the OpenVMS VAX Operating System 4-7h           1 After Installing the OpenVMS VAX Operating Systemo& 4.7 Decompressing the System Libraries    A       Table_4-1_(Cont.)__Sizes_of_Decompressed_System_Libraries__   A       Library___________Blocks______Library___________Blocks_____e  :       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  A       DISKQUOTA.HLB______102_____________________________________f  % 4.7.2  Methods of Using LIBDECOMP.COM   ;       You can use the LIBDECOMP.COM procedure to decompress        libraries in three ways:  >       o  Entering a command and responding to prompts from the          procedure  (       o  Entering an interactive command  !       o  Entering a batch command   2       The following sections describe each method.  ?          ________________________ Note ________________________   <          Before you use the LIBDECOMP.COM procedure, be sure1          you are logged in to the SYSTEM account.r  ?          ______________________________________________________   6 4-8  After Installing the OpenVMS VAX Operating System r  m      E                     After Installing the OpenVMS VAX Operating SystemiE                                4.7 Decompressing the System Librariese    -     4.7.3 Responding to LIBDECOMP.COM Prompts   >           If you want to decompress libraries by responding toE           prompts from the LIBDECOMP.COM procedure, do the following:o  ?           1. Enter the following command and then press Return:f  (              $ @SYS$UPDATE:LIBDECOMP.COM  4              The following information is displayed:  C                               OpenVMS Library Decompression Utility   L           1  HELPLIB.HLB          14  NCPHELP.HLB          27  PHONEHELP.HLBF           2  STARLET.OLB          15  SDA.HLB              28  LIB.MLBJ           3  ACLEDT.HLB           16  SHWCLHELP.HLB        29  STARLET.MLBL           4  ANLRMSHLP.HLB        17  SYSGEN.HLB           30  STARLETSD.TLBP           5  DBG$HELP.HLB         18  ANALAUDIT$HELP.HLB   31  SYS$STARLET_C.TLBI           6  DBG$UIHELP.HLB       19  SYSMANHELP.HLB       32  ERFLIB.TLB L           7  DISKQUOTA.HLB        20  TFF$TFUHELP.HLB      33  SYS$LIB_C.TLBL           8  EDFHLP.HLB           21  EXCHNGHLP.HLB        34  VAXCCURSE.OLBJ           9  INSTALHLP.HLB        22  TPUHELP.HLB          35  VAXCRTL.OLBK          10  LATCP$HELP.HLB       23  EVE$HELP.HLB         36  VAXCRTLD.OLBnK          11  MAILHELP.HLB         24  EVE$KEYHELP.HLB      37  VAXCRTLT.OLBsK          12  MNRHELP.HLB          25  UAFHELP.HLB          38  IMAGELIB.OLB .          13  EDTHELP.HLB          26  TECO.HLB  5               39  VMS$VOLATILE_PRIVATE_INTERFACES.OLBa  :                        A  ALL libraries to be decompressed-                        E  EXIT this procedureV  H              * Enter letter or number(s) of libraries to be decompressed8                (Separate multiple entries with a comma):  ?           2. Enter the appropriate letter or the numbers of ther@              libraries you want to decompress. To decompress all@              libraries, the process takes approximately one-half              hour.  +     4.7.4 Using LIBDECOMP.COM InteractivelyF  C           You can execute LIBDECOMP.COM interactively to decompressfA           up to eight libraries at a time by listing the names ofpC           the libraries you want to decompress as parameters on theO@           command line. (You can decompress all the libraries by.           omitting the /PARAMETERS qualifier.)  E                 After Installing the OpenVMS VAX Operating System 4-9n m         1 After Installing the OpenVMS VAX Operating Systemi& 4.7 Decompressing the System Libraries    9       Be sure you do not include the file extensions. ForV<       example, to decompress the VAXCRTL.OLB, DISKQUOTA.HLB,>       and LIB.MLB libraries interactively, enter the following       command:  3       $ @SYS$UPDATE:LIBDECOMP VAXCRTL DISKQUOTA LIB   # 4.7.5  Using LIBDECOMP.COM in Batch   9       You can also execute LIBDECOMP.COM in batch mode to ?       decompress up to eight libraries at a time by listing theIA       names of the libraries you want to decompress as parametersE9       on a command line that includes the SUBMIT command.M  >       Be sure to separate the library names with commas and doA       not include the file extensions. For example, to decompressR=       VAXCRTL.OLB, DISKQUOTA.HLB, and LIB.MLB as a batch job,u"       enter the following command:  ;       $ SUBMIT/NOTIFY/PARAMETERS=(VAXCRTL, DISKQUOTA, LIB)-t       _$ SYS$UPDATE:LIBDECOMPl  ?          ________________________ Note ________________________w  7          When you enter the command for a batch job, beM:          sure you enclose the list of library names within          parentheses.   ?          ______________________________________________________   / 4.8  Adding and Removing Operating System FilesE  ;       To remove OpenVMS VAX operating system files from theE=       system disk, use VMSTAILOR or DECW$TAILOR. For example,t>       if you are not running DECnet software, use VMSTAILOR to.       remove the files associated with DECnet.  ?          ________________________ Note ________________________e  >          You cannot use VMSTAILOR to remove files installed on4          an alternate device from save set VMS073.E.  ?          ______________________________________________________   8       For complete information about using VMSTAILOR and>       DECW$TAILOR to remove optional OpenVMS VAX software, see       Chapter 10.   7 4-10  After Installing the OpenVMS VAX Operating Systemd h  y      E                     After Installing the OpenVMS VAX Operating SystemPE                                       4.9 Installing Layered Productsa    #     4.9 Installing Layered Products   D           Back up your system disk and then use either the VMSINSTALC           command procedure or the POLYCENTER Software Installationm=           utility to install layered products on your system.T  =           For additional information about installing layeredtA           products, refer to the OpenVMS System Manager's Manual.a  .     4.10 Backing Up the Customized System Disk  D           After you have customized the OpenVMS VAX operating systemC           to your satisfaction and installed your layered products,cE           protect your work by making a standalone backup copy of the            system disk.  A           For complete information about backup operations, refernA           to the upgrade and installation supplement for your VAX 3           computer and the system manager's manual.        4.11 Running AUTOGEN  B           When you installed the OpenVMS VAX operating system, theE           system executed the AUTOGEN.COM procedure to set the values A           of system parameters and the sizes of the page and swap 3           files according to the system's workload.i  B           In many cases, AUTOGEN can improve system performance byE           using dynamic feedback information from the running system.ID           As a postinstallation task, you should run the AUTOGEN.COM6           procedure again to properly tune the system.  !           Run AUTOGEN as follows:o  A           1. After 24 hours of operation, run AUTOGEN in feedbackS(              mode and reboot the system.  C           2. Run AUTOGEN again in feedback mode two workdays later,h#              and reboot the system.-  B             ________________________ Note ________________________  9             For large memory systems such as the VAX 9000 >             computer, AUTOGEN's initial parameter calculations=             are conservative. To obtain parameter values thatC>             match your system workload, you can run AUTOGEN in,             feedback mode a number of times.  B             ______________________________________________________  E                After Installing the OpenVMS VAX Operating System 4-11B           1 After Installing the OpenVMS VAX Operating System  4.11 Running AUTOGEN    ?          ________________________ Note ________________________   6          For large memory systems such as the VAX 9000;          computer, AUTOGEN's initial parameter calculationsL:          are conservative. To obtain parameter values that;          match your system workload, you can run AUTOGEN inH?          feedback mode a number of times. For more information, =          refer to the upgrade and installation supplement for           your computer.T  ?          ______________________________________________________o  >       3. Compaq recommends that you run AUTOGEN from SAVPARAMS<          through TESTFILES on a weekly basis thereafter, and=          examine AGEN$PARAMS.REPORT to determine the need for           additional changes.  ;       After you run AUTOGEN following the first 24 hours ofm8       system operation (step 1), review the checklist in=       Section 4.13 to confirm that you have completed all the_&       tasks described in this chapter.   4.12  Modifying Parameters  8       When AUTOGEN runs, it uses the parameter values in<       SYS$SYSTEM:MODPARAMS.DAT. Based on your examination of<       AGEN$PARAMS.REPORT, you might need to modify parameter@       values in MODPARAMS.DAT. If so, note that hardcoded values<       in MODPARAMS.DAT affect AUTOGEN's ability to calculate<       feedback parameters. For AUTOGEN to properly calculate>       minimum default values, you should replace the hardcoded;       values in MODPARAMS.DAT with MIN_ values. If you neede;       to modify the parameter values calculated by AUTOGEN,c;       you can use AUTOGEN to change the hardcoded values inL       MODPARAMS.DAT.  ;       For more information about the MODPARAMS.DAT file and A       about using AUTOGEN in general, refer to the OpenVMS System        Manager's Manual.4            7 4-12  After Installing the OpenVMS VAX Operating System     5      E                     After Installing the OpenVMS VAX Operating SystemCE                                       4.13 Postinstallation Checklist     #     4.13 Postinstallation Checklist   B           Use the following checklist to make sure you perform all/           the necessary postinstallation tasks.Y  ?           <  Verify the system time. (Described in Section 4.1)   C           <  Register your licenses if you did not do so during the E              installation procedure. (Described in Appendix B of thisHA              manual and in the OpenVMS License Management Utility               Manual)  A           <  Build a standalone BACKUP kit on the system disk and >              on removable media. (Described in the upgrade and7              installation supplement for your computer)I  :           <  Back up the system disk as a safeguard beforeB              customizing the system. (Described in the upgrade and7              installation supplement for your computer)   =           <  Customize the system. (Described in Section 4.4)   E           <  Configure and start your networking software. (Describedl              in Section 4.5)  E           <  Run the User Environment Test Package (UETP) to test the C              system. (Described in OpenVMS System Manager's Manual, ?              Volume 2: Tuning, Monitoring, and Complex Systems)   A           <  Decompress the system libraries using LIBDECOMP.COM. '              (Described in Section 4.7)l  A           <  Remove unwanted files from the system disk using thegA              OpenVMS tailoring utility. (Described in Chapter 10)a  &           <  Install layered products.  B           <  Back up the system disk after you have customized it.B              (Described in the upgrade and installation supplement              for your computer)   >           <  Run AUTOGEN after the system has been running for?              at least 24 hours to collect feedback information.u(              (Described in Section 4.11)  E                After Installing the OpenVMS VAX Operating System 4-13r    e                    E                                                                     5KE     _________________________________________________________________o  E                     Before Upgrading the OpenVMS VAX Operating Systemb    E           This chapter describes which tasks you should perform priordB           to beginning an upgrade. Tasks described in this chapter           include:  0           o  Reviewing cautions and restrictions  A           o  Making sure your hardware is ready and your softwarec)              distribution kit is complete   ,           o  Examining AUTOGEN feedback data  (           o  Backing up your system disk  '           o  Preparing your system disk   "           o  Preparing your system  @           o  Gathering the information for the upgrade procedure  0           o  Completing the preupgrade checklist  ?           If you are an experienced system manager, you can userB           the checklist at the end of this chapter to complete the%           necessary preupgrade tasks.O  <           If you are system manager with limited OpenVMS VAXA           experience, you should read the entire chapter and thenIC           use the checklist to make sure you have completed all the            preupgrade tasks.e  !     5.1 Cautions and Restrictions   E           This section provides important information that can affectYE           the success of your upgrade. If you attempt to upgrade yournC           system without following these cautions and restrictions,_B           the upgrade could fail or your upgraded system might not           perform as expected.  E                 Before Upgrading the OpenVMS VAX Operating System 5-10    -      1 Before Upgrading the OpenVMS VAX Operating Systemh 5.1 Cautions and Restrictions      5.1.1  License RequirementsO  =       To upgrade to OpenVMS VAX Version 7.3, you must have anl;       appropriate license. Compaq's software licenses grantt>       the right to use the current version of a product or any>       previous version of the product at the time of purchase.A       If you have an OpenVMS license prior to Version 7.3 and areyA       not covered by a Software Product Services agreement, whichn=       includes the right to use new versions (RTNV), you musta@       purchase an Update License before upgrading to OpenVMS VAX       Version 7.3.  ?       If you do not have an Update License, contact your Compaqu;       account representative to assist you in obtaining the >       correct Product Authorization Key (PAK) needed to access#       the OpenVMS operating system.o  ! 5.1.2  DECset Version 11 Debuggerp  A       If you have the DECset Version 11 layered product installedt<       on your system, you must remove the @DEBUG$STARTUP.COM=       command from the system startup procedure. The debuggerl;       shipped with OpenVMS VAX Version 7.3 is a superset ofe>       the debugger that was shipped with the DECset Version 11<       software. Removing the @DEBUG$STARTUP.COM command will@       cause the debugger shipped with OpenVMS VAX Version 7.3 to%       be the default system debugger.f  A       To remove the @DEBUG$STARTUP.COM command before you upgradenA       the operating system software, perform the following steps:t  5       1. Log in to an account with system privileges.e  2       2. Using the editor of your choice, open the>          SYS$STARTUP:SYSTARTUP_VMS.COM file and search for the          following command:o            $ @DEBUG$STARTUP.  <          Delete the command and any parameters. (The command:          might have an optional parameter of either VMS or          DECSET.)_  /       3. Exit from the file, saving the change.y  6 5-2  Before Upgrading the OpenVMS VAX Operating System '  n      E                     Before Upgrading the OpenVMS VAX Operating SystemeE                                         5.1 Cautions and RestrictionsO    B           If you do not remove this command before you upgrade theA           operating system software, you must remove it after the ?           upgrade, and you must deassign the logicals that were B           defined by DEBUG$STARTUP.COM by performing the following           steps:  ?           1. Log in to the account that you used to perform the               upgrade.   *           2. Enter the following commands:  $              $ DEASSIGN/SYSTEM DEBUG'              $ DEASSIGN/SYSTEM DEBUGSHRn)              $ DEASSIGN/SYSTEM DEBUGUISHR (              $ DEASSIGN/SYSTEM DBGTBKMSG'              $ DEASSIGN/SYSTEM DBG$HELP )              $ DEASSIGN/SYSTEM DBG$UIHELPh,              $ DEASSIGN/SYSTEM DEBUGAPPCLASS*              $ DEASSIGN/SYSTEM VMSDEBUGUIL  A           3. Using the editor of your choice, open the SYSTARTUP_o?              VMS.COM file and search for the following command:F                $ @DEBUG$STARTUP,  @              Delete the command and any parameters. (The command>              might have an optional parameter of either VMS or              DECSET.)u  3           4. Exit from the file, saving the change.c  )     5.1.3 Customized Security Environmenty  D           The OpenVMS VAX Version 7.3 upgrade procedure provides newD           files and directories in the directory [VMS$COMMON...]. IfB           you had any special protections and access control lists@           (ACLs) before the upgrade, you need to reapply them toB           reestablish the security environment you had previously.?           For more information about creating and maintaining a B           secure environment, refer to the OpenVMS Guide to System           Security.s  &     5.1.4 Operator and Accounting Logs  <           The upgrade procedure deletes all the operator andC           accounting logs. To save these files, move them to a users1           directory before you start the upgrade.   E                 Before Upgrading the OpenVMS VAX Operating System 5-3            1 Before Upgrading the OpenVMS VAX Operating SystemS 5.1 Cautions and Restrictions4    * 5.1.5  Special Testing and Debugging Files  A       Before you perform an upgrade, remove or rename any speciall;       testing or debugging files that you might have in any =       of the SYS$SPECIFIC: or SYS$SYSROOT: directories. FilesP<       in these directories are used in place of the files in       SYS$COMMON: directories.  ?       As a minimum, you should check the following directories:          SYS$SYSROOT:[SYSEXE]       SYS$SYSROOT:[SYS$LDR]   ;       Because the upgrade procedure affects the SYS$COMMON: A       directories and does not check or alter the contents of thet?       SYS$SPECIFIC: or SYS$SYSROOT: directories, any testing ort?       debugging files that you have in these directories remainA@       there unchanged until you remove or rename them. If you do@       not remove or rename these files, your system might behave!       in an unpredictable manner.    5.1.6  Cluster Considerationsa  ;       The following cautions apply when you are upgrading a        cluster system:   @       o  The upgrade procedure does not work across the network.<          The network is not available during the upgrade, so@          you must have the save sets available locally or on the          InfoServer.  ?       o  If the node you are upgrading is a cluster member, theo;          upgrade procedure checks the previously set values =          of several system parameters at the beginning of theaA          upgrade (see Section 7.2.) If any of the values are lesss=          than that required to upgrade to OpenVMS VAX VersionlA          7.3, you are given the choice of continuing or cancelingh@          the upgrade. If you choose to continue the upgrade, the>          entire upgrade might not be completed and the cluster'          might be left in a hung state.t  ?       o  Before you start the upgrade procedure in a VAXcluster @          environment, you must shut down all the nodes that boot>          from the system disk you are upgrading, including the)          node you perform the upgrade on.n  6 5-4  Before Upgrading the OpenVMS VAX Operating System    t      E                     Before Upgrading the OpenVMS VAX Operating System E                                         5.1 Cautions and Restrictions          5.1.7 Save Set Location_  E           If you move the OpenVMS VAX save sets from the distributiong<           media to the system disk or some other disk before=           beginning the upgrade, the save sets must be in the C           [000000] directory of the disk, or the upgrade will fail.   C           Do not attempt to use VMSINSTAL with OPTION G to transfer ?           OpenVMS VAX save sets to another media type; doing so C           produces an unusable system. Instead, you can use the DCLNC           command COPY to transfer save sets to another media type.        5.1.8 System Disk Cautions  :           The following cautions apply to the system disk:  >           o  If you changed the names of system directories onB              your system disk, the upgrade procedure will not work>              correctly. Restore your system disk to a standard?              directory structure before you attempt an upgrade.t  B           o  You must not move the system disk or the distribution>              kit from one drive to another during the upgrade.  ?           o  You cannot upgrade a shadowed system disk. If yourlA              system disk is part of a shadow set, you must createcD              a nonshadowed system disk before beginning the upgrade.  @              Also, if you copy the distribution media to another8              disk, that disk must be a nonshadowed disk.  =              For more information, refer to the manual Volumeo#              Shadowing for OpenVMS.   A           o  If you elect not to install optional components, theS?              upgrade procedure removes existing files for thosee=              components from the system disk. You can install =              optional files during the upgrade or later using               VMSTAILOR.e  E              Note that, while some optional files can be placed on an C              alternate device, you cannot tailor files on or off ano              alternate device.    E                 Before Upgrading the OpenVMS VAX Operating System 5-5. n  r      1 Before Upgrading the OpenVMS VAX Operating Systeme 5.1 Cautions and Restrictionse     5.1.9  AUTOGEN Feedback Data  <       If you use your AUTOGEN feedback data, you should save?       this information before rebooting the system with minimump=       startup to begin the upgrade. For more information, seee       Section 5.3.  ( 5.1.10  OpenVMS VAX Version Requirements  =       Before you can upgrade to OpenVMS VAX Version 7.3, yourt@       system must be running at least Version 6.1 of the OpenVMSA       VAX operating system. For example, you can upgrade a systemm=       disk to Version 7.3 of the OpenVMS VAX operating systeme=       from any of the following versions (or related hardwaree       releases):             OpenVMS VAX Version 6.1           OpenVMS VAX Version 6.2           OpenVMS VAX Version 7.0           OpenVMS VAX Version 7.1           OpenVMS VAX Version 7.2  ?          ________________________ Note ________________________e  ;          These minimum requirements do not apply to rollingb?          upgrades. There are special considerations for rollingt>          upgrades. See Section 6.1 for additional information.  ?          ______________________________________________________e  = 5.1.11  DECwindows Motif for OpenVMS VAX Version Requirements   =       If you want to use DECwindows software with OpenVMS VAX A       Version 7.3, you must be running Version 1.2-3 or higher ofm;       the DECwindows Motif for OpenVMS VAX layered product.C  .       For more information, see Section 1.1.2.    5.1.12  Shared System Dump Files  .       If you have a shared system dump file in?       SYS$COMMON:[SYSEXE], the shared dump file cannot have thee=       name SYSDUMP.DMP. If you have a shared system dump filer=       with this name, Compaq recommends that you rename it toe,       SYS$COMMON:[SYSEXE]SYSDUMP_COMMON.DMP.  6 5-6  Before Upgrading the OpenVMS VAX Operating System d  u      E                     Before Upgrading the OpenVMS VAX Operating SystemME                                         5.1 Cautions and Restrictionso         5.1.13 Layered Productsf  >           The upgrade procedure is designed so that you should?           not have to reinstall most layered products after the ?           upgrade. However, you might need to reinstall certainGC           layered products because of product-specific installationS           procedures.   C           If a layered product is available yet exhibits unexpectedM@           behavior once Version 7.3 of the OpenVMS VAX operatingB           system is running, check the OpenVMS Version 7.3 Release:           Notes for possible layered-product restrictions.       5.2 Preparing to Upgrade  ?           Before you begin to upgrade the OpenVMS VAX operatinga@           system, be sure you have all the required hardware and           software components.       5.2.1 Hardware Componentsn  2           Examine your hardware for the following:  @           o  Make sure your hardware has been checked for properA              operation. To perform a successful upgrade, you mustO@              understand the basic operations of the VAX computer=              that you are upgrading. Refer to the upgrade andoB              installation supplement for your VAX computer. If youD              have a VAXcluster environment, refer to OpenVMS Cluster              Systems.   ?           o  Set up your system to record the upgrade procedure @              on either a hardcopy terminal or a printer attached@              to the console terminal. If you do not do this, theC              screen messages will be lost. You need a transcript ineA              case there is a problem during the upgrade. For morea?              information, refer to the upgrade and installationU.              supplement for your VAX computer.  D           o  Have scratch console media (media that does not containD              files you want to save) available for the following VAX              computers:g                   VAX 8600, 8650*                 VAX 8200, 8250, 8300, 8350                 VAX-11/730                 VAX-11/750                 VAX-11/780, 785   E                 Before Upgrading the OpenVMS VAX Operating System 5-7f o  g      1 Before Upgrading the OpenVMS VAX Operating SystemY 5.2 Preparing to Upgrade    <          For example, if you have a VAX-11/780 or VAX-11/7854          computer, you need a scratch RX01 diskette.   5.2.2  Software Components  .       Examine your software for the following:  ?       o  Make sure you have all the items listed on the bill of A          materials (BOM) in the OpenVMS distribution kit. If youro>          kit is incomplete, notify Compaq Software Supply, and8          request priority shipment of any missing items.  @       o  Before upgrading the OpenVMS VAX operating system, read?          Appendix B of this manual, the OpenVMS Version 7.3 NewkA          Features and Documentation Overview, the OpenVMS Versiont?          7.3 Release Notes, and any cover letters included withc          your kit.  $ 5.3  Examining AUTOGEN Feedback Data  >       After the upgrade is finished, AUTOGEN runs. If it findsA       valid feedback data on your system, it tries to use AUTOGENm       feedback.e   5.3.1  Valid Feedback Data  A       Feedback data is produced by the SAVPARAMS phase of AUTOGENa:       and is stored in SYS$SYSTEM:AGEN$FEEDBACK.DAT. Valid*       feedback data is defined as follows:  9       o  The system was up for at least 24 hours when theu$          feedback data was gathered.  3       o  The feedback data is not over 30 days old.m  :       If your feedback data is not valid, AUTOGEN will run7       without feedback (all previous feedback-generatedt;       parameters will be replaced by the AUTOGEN NOFEEDBACKh       calculations).    5.3.2  How to Test Feedback Data  A       To ensure that AUTOGEN feedback will run after the upgrade,        do the following:   <       1. Check the validity of your current feedback data by(          entering the following command:  0          $ @SYS$UPDATE:AUTOGEN GETDATA TESTFILES  6 5-8  Before Upgrading the OpenVMS VAX Operating System n         E                     Before Upgrading the OpenVMS VAX Operating SystemoE                                   5.3 Examining AUTOGEN Feedback Datas    E              This command is for test purposes and does not result in D              the modification of system parameters or changes to theD              page and swap files. If your current feedback is valid,D              AUTOGEN uses it during the upgrade, and you can proceed!              to the next section.n  E              If your current feedback data is invalid, AUTOGEN issues D              several warnings. If you get these warnings, go to step              2.n  B           2. If your current feedback is invalid, you can generateB              new feedback data (assuming your system was up for at:              least 24 hours). Enter the following command:  6              $ @SYS$UPDATE:AUTOGEN SAVPARAMS TESTFILES  B              This command is for test purposes and does not resultC              in the modification of system parameters or changes tooE              the page and swap files. Again, AUTOGEN warns you if the 4              feedback data just produced is invalid.  A           3. If you follow steps 1 or 2 and your current feedback ?              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.4 Backing Up the System Disk  B           Compaq recommends that you make a standalone BACKUP copyB           of the system disk and, if your configuration allows it,B           upgrade the backup copy. If there are problems, you will+           still have a working system disk.   (     5.4.1 How to Back Up the System Disk  >           To make a backup copy of the system disk, follow theA           instructions in the upgrade and installation supplement ?           for your VAX computer. If you do not have a removablerC           system disk, back up your system disk to tape and restoreoC           the image backup to the system disk. This eliminates diskuA           fragmentation on the system disk and creates contiguousaE           free disk blocks required for the upgrade. (The upgrade cantC           fail if there are not sufficient contiguous free blocks.) 1           Store the backup tapes in a safe place.u  E                 Before Upgrading the OpenVMS VAX Operating System 5-9i a  e      1 Before Upgrading the OpenVMS VAX Operating Systemm 5.4 Backing Up the System Disk    # 5.4.2  How to Back Up Console Mediae  >       If you have one of the following VAX computers, you must3       also make a backup copy of the console media:             VAX-11/730n          VAX-11/750S          VAX-11/780, 785/          VAX 8200, 8250, 8300, 8350, 8600, 8650r  9       To make a backup copy of the console media, use the_<       SYS$UPDATE:CONSCOPY.COM procedure, as described in the@       upgrade and installation supplement for your VAX computer.A       Use the backup copy of the console media during the upgradee@       procedure. The upgrade procedure automatically updates the       console media for you.  <       If your VAX computer uses one of the following consoleA       media, you did not receive a new standalone BACKUP kit withe(       your OpenVMS VAX distribution kit:            TU58 tape cartridge          RX33 diskette          RX50 diskette          RX01 diskette          RL02 disk cartridge  8       Before beginning the upgrade, make sure you have a<       standalone BACKUP kit on one of these media. If you do<       not have one, create a standalone BACKUP kit using the=       STABACKIT.COM procedure as described in the upgrade andi4       installation supplement for your VAX computer.  ?          ________________________ Note ________________________d  ;          You cannot build standalone BACKUP on TU58 or RX01 :          console media because the OpenVMS VAX Version 7.3>          kit is too large. If your VAX computer uses a TU58 or=          RX01, build a standalone BACKUP kit before upgradingd9          and retain the backup copies for use with futurea!          versions of OpenVMS VAX.t  ?          ______________________________________________________l    7 5-10  Before Upgrading the OpenVMS VAX Operating Systemc c  s      E                     Before Upgrading the OpenVMS VAX Operating SystemaE                                         5.5 Preparing the System Diske    !     5.5 Preparing the System Diskm  ?           To prepare the system disk for the upgrade, log in to B           the SYSTEM account and, depending on your configuration,E           complete some or all of the tasks described in the sectionsn           that follow.  *     5.5.1 Create a Nonshadowed System Disk  B           If you are using a volume-shadowed system disk, you mustA           create a nonshadowed system disk to upgrade. Follow thekD           instructions in the Volume Shadowing for OpenVMS manual to<           prepare a nonshadowed system disk for the upgrade.  2     5.5.2 Boot the Backup Copy of Your System Disk  D           If you need to boot the backup copy of your system disk orB           if you are upgrading a VAXcluster environment, enter the=           following command (otherwise, go to the next step):               $ @SYS$SYSTEM:SHUTDOWN  ?           When the procedure asks if an automatic system reboot @           should be performed, press Return for NO. If you are aD           VAXcluster member, choose the REMOVE_NODE option. When theD           procedure is finished, halt the system as described in theD           upgrade and installation supplement for your VAX computer.  C           If applicable, remove the system disk and replace it with            the backup copy.  B           Boot the system from the backup copy of the system disk.A           If you do not know how to boot the system, refer to the D           upgrade and installation supplement for your VAX computer.  '           Log in to the SYSTEM account.   8     5.5.3 Copy UAF and Auditing Files to the System Disk  A           The current copies of the SYSUAF.DAT and the VMS$AUDIT_eE           SERVER.DAT files must be on the system disk; otherwise, youa*           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.  E                Before Upgrading the OpenVMS VAX Operating System 5-11  q  t      1 Before Upgrading the OpenVMS VAX Operating Systemr 5.5 Preparing the System Diskr    ?       Note that, if you are doing a rolling upgrade, the sharede+       version of SYSUAF.DAT is not updated.t  =       Move any files that you do not want changed into a user        directory.  " 5.5.4  Rename the System Dump File  .       If you have a shared system dump file in?       SYS$COMMON:[SYSEXE], the shared dump file cannot have thea=       name SYSDUMP.DMP. If you have a shared system dump file =       with this name, Compaq recommends that you rename it tot,       SYS$COMMON:[SYSEXE]SYSDUMP-COMMON.DMP.   5.5.5  Analyze the System Disk  ?       To analyze the system disk for inconsistencies and errorsl9       in the file structure, enter the following command:e  ,       $ ANALYZE/DISK_STRUCTURE SYS$SYSDEVICE  ?       The following message represents normal behavior; you canu       ignore it:  4       %ANALDISK-I-OPENQUOTA, error opening QUOTA.SYS  A       If you find any other errors on the system disk, repair thet/       errors by entering the following command:.  3       $ ANALYZE/DISK_STRUCTURE/REPAIR SYS$SYSDEVICEA  @       Refer to the OpenVMS System Management Utilities Reference?       Manual for more information on the ANALYZE/DISK_STRUCTUREy       command.    5.5.6  Check Page and Swap Files  <       Compaq recommends that the page file be located on the;       system disk in SYS$SPECIFIC:[SYSEXE] for the upgrade.   >       The swap file (SWAPFILE.SYS) does not need to be located6       on the system disk for the upgrade, but if it is=       located on the system disk, the file must be located ina       SYS$SPECIFIC:[SYSEXE].  <       If the upgrade procedure finds the page files and swapA       files in the common directory, it moves them to the system-,+       specific directory before continuing.r  7 5-12  Before Upgrading the OpenVMS VAX Operating Systemn           E                     Before Upgrading the OpenVMS VAX Operating System E                                         5.5 Preparing the System Disk     D           The page file must be at least 4600 blocks. If the upgradeA           procedure detects fewer than 4600 blocks, it displays atE           message that gives you the option of continuing the upgrade A           or exiting the procedure and increasing the size of the D           page file. If you get this message, Compaq recommends thatD           you exit the procedure, increase the page file to at least9           4600 blocks, and restart the upgrade procedure.   E           To check the size of your page file and enter a new size ifw.           needed, use the following procedure:  >           1. To determine the size of the page file, enter the              following command:g  $              $ @SYS$UPDATE:SWAPFILES  A              The procedure displays the size of the page file andt7              asks you to enter a new value, as follows:   ,              Enter new size for paging file:  A              If the page file (PAGEFILE.SYS) size is greater thano?              4600 blocks, press Return. If it is less than 4600b1              blocks, enter 4600 and press Return.e  C           2. If the swap and dump files are on the system disk, thekC              procedure displays the sizes of each file. To keep thes<              current values, press Return after each prompt.  <              If the swap file is not on the system disk, theA              procedure asks if you want to create one. You do noth@              need swap and dump files on the system disk for theB              upgrade procedure. Enter the appropriate response for              your system.   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.        5.5.7 Check for Free Blocksg  A           Check the system disk to make sure there is enough room E           for the upgrade. To determine whether you have enough room,f&           enter the following command:  %           $ SHOW DEVICE SYS$SYSDEVICEd  E                Before Upgrading the OpenVMS VAX Operating System 5-137           1 Before Upgrading the OpenVMS VAX Operating Systemm 5.5 Preparing the System Diske    <       To upgrade the OpenVMS VAX required files, the minimum@       number of free blocks required is 48,950. Even if you planA       to upgrade the OpenVMS library or optional files, you might >       not need more than 48,950 free blocks because many files<       are deleted as the upgrade progresses, thus freeing up       additional space.t   5.5.8  Check Quotas and Limits  <       Use the Authorize utility (AUTHORIZE) to make sure the?       SYSTEM account has sufficient quotas and limits. To check >       and, if necessary, modify quota and limit values, do the       following:  &       1. Enter the following commands:  !          $ SET DEFAULT SYS$SYSTEM           $ RUN AUTHORIZE          UAF> SHOW SYSTEM   @          AUTHORIZE displays the SYSTEM account's quota and limit          values.  ;       2. Compare the values displayed on your screen to thei+          following minimum required values:   A          ________________________________________________________ A          Quota_or_Limit_Name_________________Minimum_Value_______o  2          Open file quota (FILLM)               300  2          Buffered I/O limit (BIOLM)             18  2          Direct I/O limit (DIOLM)               18  2          AST limit (ASTLM)                      24  2          Enqueue quota (ENQLM)                 200  3          Buffered byte quota count (BYTLM)   32768+_A          +If_you_are_using_an_InfoServer_device_to_upgrade_your__s  A          system,_increase_the_value_of_BYTLM_to_33150____________V  @       3. If necessary, adjust the quota and limit values in yourA          SYSTEM account so that they are equal to or greater than %          the minimum required values.r  <          To change the value for a quota or limit, enter the:          MODIFY SYSTEM command using the following format:  &          MODIFY SYSTEM/limit=new_value  7 5-14  Before Upgrading the OpenVMS VAX Operating Systems    k      E                     Before Upgrading the OpenVMS VAX Operating System E                                         5.5 Preparing the System Disk                   For example:o  (              UAF> MODIFY SYSTEM/DIOLM=18  A           4. Exit the Authorize utility by entering the followingc              command:                 UAF> EXIT  E           5. If you adjusted the values for any of the SYSTEM accountuB              quotas or limits, log out and log back in to have the$              new values take effect.       5.5.9 Set System ParametersO  ?           During the upgrade procedure, the system is shut downoB           and rebooted a number of times. You must boot the system>           minimum (STARTUP_P1 set to MIN) before you begin theA           upgrade (see Section 5.6). This prevents the startup ofeD           certain system integrated products and layered products onD           the system during each reboot. To set the system parameter:           STARTUP_P1 to MIN, enter the following commands:  !           $ RUN SYS$SYSTEM:SYSMANy(           SYSMAN> PARAMETERS USE CURRENT1           SYSMAN> PARAMETERS SET STARTUP_P1 "MIN"r*           SYSMAN> PARAMETERS WRITE CURRENT           SYSMAN> EXIT                                  E                Before Upgrading the OpenVMS VAX Operating System 5-15h u  n      1 Before Upgrading the OpenVMS VAX Operating System  5.5 Preparing the System Disk     =       Make sure the system parameters SCSNODE and SCSSYSTEMIDr<       are defined on your system. To determine whether these@       parameters are defined on your system, enter the following       commands:          $ RUN SYS$SYSTEM:SYSMAN.%       SYSMAN> PARAMETERS SHOW SCSNODEp)       SYSMAN> PARAMETERS SHOW SCSSYSTEMIDt  A       If SCSNODE and SCSSYSTEMID are not set correctly, enter the.A       following commands where node is a 1- to 6-character uniquem=       DECnet node name and systemid is (DECnet area * 1024) +g       node number:  $       SYSMAN> PARAMETERS USE CURRENT+       SYSMAN> PARAMETERS SET SCSNODE "node"a1       SYSMAN> PARAMETERS SET SCSSYSTEMID systemid &       SYSMAN> PARAMETERS WRITE CURRENT
          .
          .
          .  >       Make sure the system parameter VMS5 is set to 0. If your=       system has a KFQSA controller, the VMS5 parameter mighta>       have been set to a nonzero value for a previous upgrade.<       The VMS5 parameter is reserved for use by Compaq only.  9       To check the value of the VMS5 parameter, enter theS       following commands:A         $ RUN SYS$SYSTEM:SYSMANo$       SYSMAN> PARAMETERS USE CURRENT"       SYSMAN> PARAMETERS SHOW VMS5L Parameter Name           Current   Default   Minimum   Maximum Unit  DynamicL --------------           -------   -------   -------   ------- ----  -------> VMS5                           1         0         0        -1  ;       If the current value of VMS5 is not 0, set it to 0 bym&       entering the following commands:  $       SYSMAN> PARAMETERS USE CURRENT#       SYSMAN> PARAMETERS SET VMS5 0D&       SYSMAN> PARAMETERS WRITE CURRENT       SYSMAN> EXIT  7 5-16  Before Upgrading the OpenVMS VAX Operating SystemA E  S      E                     Before Upgrading the OpenVMS VAX Operating SystempE                                         5.5 Preparing the System Diskn    #     5.5.10 Check AGEN$INCLUDE Files   ;           During an upgrade, user disks are not mounted anddC           SYLOGICALS.COM is not invoked, so AUTOGEN can access onlye?           data files that are on the system disk and whose fileCB           specification includes a logical name that is shipped asE           part of the OpenVMS operating system. Therefore, if you useyC           AGEN$INCLUDE in SYS$SYSTEM:MODPARAMS.DAT to point to dataUC           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 filer6              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.  :     5.5.11 Add Modified System Parameters to MODPARAMS.DAT  C           Any system parameter values that you modified and did noth@           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 tov$           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:n             ADD_GBLPAGES=128  D           When AUTOGEN runs after the upgrade, it uses the values in           MODPARAMS.DAT.  C           Section 5.6 tells you how to get your system ready for ans           upgrade.    E                Before Upgrading the OpenVMS VAX Operating System 5-17  n  o      1 Before Upgrading the OpenVMS VAX Operating Systemu 5.6 Preparing the System     5.6  Preparing the Systema  >       To prepare the system for the upgrade, use the procedure*       described in the following sections.  + 5.6.1  Enable Auto Restart or Manual Rebooto  >       If your computer uses console media, set the computer to>       restart automatically. For some VAX computers this means:       setting one or more switches. For others, this meansA       entering certain console mode commands. To determine how toc@       enable auto restart, refer to the upgrade and installation'       supplement for your VAX computer.a  ;       If you have a system that does not use console media, 8       set your system so you can reboot it manually. For=       more information, refer to the upgrade and installation '       supplement for your VAX computer.i  & 5.6.2  Shut Down and Reboot the System  <       Shut down and reboot the system to activate any system?       parameters that you changed (STARTUP_P1, for example). Tol8       shut down the system, enter the following command:         $ @SYS$SYSTEM:SHUTDOWN  ;       When the procedure asks if an automatic system reboot =       should be performed, type Y (for YES) and press Return.a  =       After the system reboots, log in to the SYSTEM account.   ! 5.6.3  Prevent Interactive Logins   ?       To prevent users from logging in to the system during the +       upgrade, enter the following command:           $ SET LOGINS/INTERACTIVE=0  # 5.6.4  Check for DECnet for OpenVMS   <       To determine whether your system is running DECnet for4       OpenVMS software, enter the following command:         $ SHOW LOGICAL SYS$NODEd  :       If the system displays the following message, DECnet:       is not running on your system and you can proceed to       Section 5.6.6:  >       %SHOW-S-NOTRAN, no translation for logical name SYS$NODE  7 5-18  Before Upgrading the OpenVMS VAX Operating System_           E                     Before Upgrading the OpenVMS VAX Operating SystemiE                                              5.6 Preparing the System     A           If the system responds with a translation for SYS$NODE, 0           then DECnet is running on your system.  E           If you set STARTUP_P1 to MIN as described in Section 5.5.9,i<           DECnet should not be running. To set STARTUP_P1 to?           MIN, repeat all of the preceding steps beginning with @           Section 5.5.9. Note that you must shut down and rebootE           the system for any changes you make to system parameters ton           take effect.  $     5.6.5 Check for Volume Shadowing  B           Phase I (controller-based) volume shadowing is no longer>           available. Phase II (host-based) volume shadowing is>           designed to fully replace phase I with significantly           enhanced features.  A           If you have volume shadowing software installed on your >           system but are unsure which phase, you can enter the           following commands:F  !           $ RUN SYS$SYSTEM:SYSMAN (           SYSMAN> PARAMETERS USE CURRENT+           SYSMAN> PARAMETERS SHOW SHADOWING   E           If the SHADOWING parameter is 1 or 3, then you have phase ItD           volume shadowing software currently loaded on your system.?           For information about migrating to phase II, refer to.'           Volume Shadowing for OpenVMS.i  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 presenceiC           of phase I, it displays the following message and asks ifg+           you want to continue the upgrade:   J              The SHADOWING system parameter (currently set to 1) specifiesL              phase I of volume shadowing, which is no longer available as ofP              OpenVMS VAX Version 6.1.  If you continue with this upgrade, volumeO              shadowing will not be present on your system after the upgrade hasXN              completed. Please consult the Volume Shadowing for OpenVMS manualK              for instructions about moving to phase II of volume shadowing.O  0           * Do you want to continue the upgrade?  E                Before Upgrading the OpenVMS VAX Operating System 5-19r e  e      1 Before Upgrading the OpenVMS VAX Operating Systeme 5.6 Preparing the System    ?       At that point, you can exit the upgrade procedure, followM:       the instructions in Volume Shadowing for OpenVMS for=       migrating to phase II volume shadowing, and restart theT;       upgrade procedure from the beginning. If you continuen@       with the upgrade without migrating to phase II, the volumeA       shadowing software will not be present on your system after         the upgrade has completed.   5.6.6  Stop Queues  <       To stop all batch and print queues on the node you are-       upgrading, enter the following command:R         $ STOP/QUEUES/ON_NODE   >       It is not necessary to stop queues on nodes that you are       not upgrading.  * 5.7  Gathering Information for the Upgrade  ;       At different points during the upgrade, the procedurer:       prompts you to supply information. To save time once:       the procedure begins, be sure you have the followingA       information readily available. Remember, entering incorrectA>       information during the upgrade could force you to repeat#       the entire upgrade procedure.   A _________________________________________________________________  RequiredA Information________Explanation___________________________________   @ Device names       You will need to specify the device names for=                    the drives that will hold the distributionf-                    media and the system disk.U  ? Passwords          You will be prompted to type passwords of atA>                    least 8 characters for the SYSTEM, SYSTEST,&                    and FIELD accounts.              7 5-20  Before Upgrading the OpenVMS VAX Operating Systemi S  e      E                     Before Upgrading the OpenVMS VAX Operating System E                             5.7 Gathering Information for the Upgradeu  E     _________________________________________________________________s     RequiredE     Information________Explanation___________________________________e  C     Optional           The upgrade procedure prompts you to specify >     components         whether you want to install the library>     and OpenVMS        (VMS073.C), optional (VMS073.D) OpenVMSA     Management         components, and OpenVMS Management StationfE     Station files      software PC files (VMS073.F). Appendix D lists =                        the files included in these save sets.   E                        You can save some space on your system disk if B                        you choose not to install these components,>                        but be sure to review Appendix D before                         deciding.  A     Location for Help  Save set VMS073.E contains the online HelpnE     Message utility    Message utility, which you can install on youroE                        system disk or on an alternate disk. (However, A                        if you copied the distribution kit to sometD                        other media from which you will be performingE                        the installation, you cannot install this save *                        set on that media.)                                              E                Before Upgrading the OpenVMS VAX Operating System 5-21d e  l      1 Before Upgrading the OpenVMS VAX Operating Systemi) 5.7 Gathering Information for the Upgradeo  A _________________________________________________________________e RequiredA Information________Explanation___________________________________P                                                                                      7 5-22  Before Upgrading the OpenVMS VAX Operating Systemo o  t      E                     Before Upgrading the OpenVMS VAX Operating SystemrE                             5.7 Gathering Information for the Upgradea  E     _________________________________________________________________      RequiredE     Information________Explanation___________________________________u  @     DECwindows         The installation procedure prompts you to@     components         specify which of the following DECwindows6                        components you want to install:  ?                        o  DECwindows base support (required forh=                           running DECwindows software), which #                           includes:   1                           -  DECwindows transporta  /                           -  DECwindows keymaps   B                        o  DECwindows workstation support (required@                           for VAX workstations), which includes:  :                           -  DECwindows X11 display server  -                           -  Graphics driversR  5                           -  75 dots/inch video fonts   >                           -  100 dots/inch video fonts (optionD                              available only if you select DECwindows1                              workstation support)   @                        Note that you must install the DECwindowsC                        Motif for OpenVMS VAX (previously called VMS D                        DECwindows Motif) layered product if you wantA                        to run the DECwindows software. DECwindowstE                        Motif for OpenVMS VAX Version 1.2-3 (or 1.2 if C                        the VAXMOTF05_012 remedial kit is installed) C                        is the minimum supported version for systemsn@                        running OpenVMS VAXVersion 7.3. If you doA                        not know which version of DECwindows MotifEC                        for OpenVMS VAX you are currently running on A                        your system, you can check by entering thel)                        following command:e  C                        $ ANALYZE/IMAGE SYS$LIBRARY:DECW$XLIBSHR.EXEe  B                        Also note that the layered product does not?                        have the DECwindows base and workstationtA                        support components. To get full DECwindowsn>                        support, you must select the DECwindows;                        components provided with the OpenVMStB                        VAXVersion 7.3 kit and install the separate?                        DECwindows Motif for OpenVMS VAX layered.A                        product, which supports both Motif and XUIrE                Before Upgradingethe.OpenVMS VAX Operating System 5-23     .      1 Before Upgrading the OpenVMS VAX Operating Systemr) 5.7 Gathering Information for the Upgrade   A _________________________________________________________________  RequiredA Information________Explanation___________________________________f  4 PAK information    The information listed on ProductA                    Authorization Keys (PAKs) for any new products,A                    you will register. You do not need to registerU?                    your OpenVMS VAX license or the licenses for @                    any System Integrated Products (SIPs) you areA ___________________already_running.______________________________e     5.8  Preupgrade Checklisto  ?       Before you begin the upgrade procedure, use the followingpA       checklist to make sure you have completed all the necessary        preupgrade tasks.   6       <  Read the OpenVMS Version 7.3 New Features and@          Documentation Overview, the OpenVMS Version 7.3 Release>          Notes, and any cover letters that came with your kit.  <       <  Read the cautions and restrictions described at the4          beginning of this chapter and in Chapter 1.  ?       <  Make sure you have enough free blocks for the upgrade. >          You need at least 48,950 free blocks for the required?          files to start the upgrade (described in Section 5.5).n:          The entire upgrade requires about 163,000 blocks.  >       <  Set up your system to record the upgrade procedure on<          either a hardcopy terminal or a printer attached to@          the console terminal. If you do not do this, the screen=          messages will be lost. You need a transcript in cased?          there is a problem during the upgrade. For informationy<          on how to connect a hardcopy device to your console:          to record the procedure, refer to the upgrade and7          installation supplement for your VAX computer.   >       <  Check your AUTOGEN feedback information to be sure it<          is valid before rebooting the system. (Described in          Section 5.3)b  6       <  Make a backup copy of the system disk and, if<          applicable, of the console media. (Described in the?          upgrade and installation supplement for your computer)o  7 5-24  Before Upgrading the OpenVMS VAX Operating Systemn r         E                     Before Upgrading the OpenVMS VAX Operating System E                                              5.8 Preupgrade Checklists    E           <  If, in previous versions, your distribution kit providedfC              standalone BACKUP on one of the following media types,rB              make sure you have created a standalone BACKUP kit on.              one of the following media types:                   RX33                 TU58                 RX50                 RX01                 RL02  '              (Described in Section 5.4)   ?           <  Make sure SYSUAF.DAT is in the SYS$COMMON:[SYSEXE]_C              and VMS$AUDIT_SERVER.DAT is in the SYS$COMMON:[SYSMGR]n2              directory. (Described in Section 5.5)  C           <  Make sure SWAPFILE.SYS (if it is located on the system D              disk) and PAGEFILE.SYS are in the SYS$SPECIFIC:[SYSEXE]2              directory. (Described in Section 5.5)  =           <  Make sure the page file is at least 4600 blocks.8'              (Described in Section 5.5)   5           <  If you have a shared system dump file ineB              SYS$COMMON:[SYSEXE], make sure the shared file is not:              named SYSDUMP.DMP. (Described in Section 5.5)  B           <  If your system disk is part of a shadow set, create aE              nonshadowed system disk to upgrade. (Described in Volume_#              Shadowing for OpenVMS)t  C           <  Make sure the SYSTEM account has sufficient quotas andn/              limits. (Described in Section 5.5)   E           <  Set the appropriate system parameters and make sure that A              STARTUP_P1 is set to MIN. (Described in Section 5.5)   B           <  Define the system parameters SCSNODE and SCSSYSTEMID.'              (Described in Section 5.5)3  A           <  If your system has a KFQSA controller, make sure thetC              VMS5 parameter is set to 0. (Described in Section 5.5)   ;           <  Check the location of your AGEN$INCLUDE files.i*              (Described in Section 5.5.10)  C           <  Set up the system to restart automatically. (DescribedcD              in the upgrade and installation supplement for your VAX              computer)  E                Before Upgrading the OpenVMS VAX Operating System 5-25     s      1 Before Upgrading the OpenVMS VAX Operating System  5.8 Preupgrade Checklist    <       <  Shut down and reboot the system from which you will@          perform the upgrade. If you are upgrading a VAXcluster,?          shut down all computers that boot from the system diskt          you are upgrading.   %       <  Set interactive logins to 0.   =       <  Shut down DECnet for OpenVMS software. (Described ine          Section 5.6)a  8       <  Migrate to phase II volume shadowing if you are<          currently using phase I. (Described in Section 5.6)  <       <  Stop all batch and print queues on the node you are.          upgrading. (Described in Section 5.6)  @       <  Make sure you have the following information (described#          in Section 5.7) available:g  =          o  The device names of the drives that will hold the 2             system disk and the distribution media  >          o  Passwords of at least 8 characters for the SYSTEM,'             SYSTEST, and FIELD accounts_  A          o  A list of optional OpenVMS VAX components you want too             install_  @          o  A list of optional DECwindows components you want to             installr  ;          o  The information listed on Product Authorizationw=             Keys (PAKs) for any new product licenses you willn             register  @       <  Create a command procedure to be used when booting from           [SYSF]. See Appendix C.  6       To upgrade a standalone system, go to Chapter 7.  ;       To upgrade a VAXcluster environment, go to Chapter 6.         7 5-26  Before Upgrading the OpenVMS VAX Operating System  w  o                    E                                                                     6cE     _________________________________________________________________   E                      Preparing to Upgrade in a VAXcluster Environment     <           This chapter describes how to upgrade a VAXcluster@           environment. Refer to OpenVMS Cluster Systems for more:           detailed information on VAXcluster environments.       6.1 Mixed-Version Support   ?           OpenVMS Alpha Version 7.3 and OpenVMS VAX Version 7.3 D           provide two levels of support for mixed-version and mixed-A           architecture OpenVMS Cluster systems. These two support ,           types are warranted and migration.  A           Warranted support means that Compaq has fully qualifiednD           the two versions coexisting in an OpenVMS Cluster and willA           answer all problems identified by customers using these            configurations.   @           Migration support is a superset of the Rolling Upgrade@           support provided in earlier releases of OpenVMS and is?           available for mixes that are not warranted. Migration B           support means that Compaq has qualified the versions forE           use together in configurations that are migrating in phasesA@           to a newer version of OpenVMS VAX or to OpenVMS Alpha.E           Problem reports submitted against these configurations willvE           be answered by Compaq. However, in exceptional cases CompaqcC           may request that you move to a warranted configuration aso(           part of answering the problem.  C           Migration support will help you move to warranted OpenVMS C           Cluster version mixes with minimal impact on your clusterDD           environment. Table 6-1 shows the level of support provided,           for all possible version pairings.          E                  Preparing to Upgrade in a VAXcluster Environment 6-1e e  g      0 Preparing to Upgrade in a VAXcluster Environment 6.1 Mixed-Version Support     <       Table 6-1  VAX and Alpha OpenVMS Cluster Warranted andA       ___________Migration_Support________________________________  A       ______V6.2-xxx____V7.0-xxx____V7.1-xxx____V7.2-xxx____V7.3_t  E       V6.2  WARRANTED   Migration   Migration   Migration   Migration   E       V7.0  Migration   WARRANTED   Migration   Migration   Migration   E       V7.1  Migration   Migration   WARRANTED   Migration   Migration   E       V7.2  Migration   Migration   Migration   WARRANTED   Migrationy  E       V7.3__Migration___Migration___Migration___Migration___WARRANTED                                                               5 6-2  Preparing to Upgrade in a VAXcluster Environmentl h  e      E                      Preparing to Upgrade in a VAXcluster EnvironmenteE                                             6.1 Mixed-Version Support3    B             ________________________ Note ________________________  ?             Compaq does not support the use of Version 7.3 with ;             Version 6.1 (or earlier versions) in an OpenVMS B             Cluster environment. In many cases, mixing Version 7.3@             with versions prior to Version 6.2 will successfully:             operate, but Compaq cannot commit to resolving:             problems experienced with such configurations.  B             ______________________________________________________  E           If your cluster environment has both VAX and Alpha systems,tD           also refer to Migrating an Environment from OpenVMS VAX to           OpenVMS Alpha[1].n       6.2 Types of Upgradesr  A           There are two types of cluster upgrades: concurrent andtA           rolling. The type of upgrade you use depends on whethereE           you want to maintain the availability of the cluster duringAE           the upgrade and whether you have more than one system disk.sD           Review this chapter and then perform the preliminary tasksE           for the upgrade procedure (concurrent or rolling) that bestk#           suits your configuration.        6.2.1 Concurrent Upgrades   D           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 an           concurrent upgrade.a  B             ________________________ Note ________________________  <             For OpenVMS VAX Version 7.3 concurrent upgrades,=             all nodes in the cluster must be running at least A             OpenVMS VAX Version 6.1. (See Section 5.1.10 for more              information.)   B             ______________________________________________________  =           To perform a concurrent upgrade, go to Section 6.3.A             ____________________E           [1]   This manual has been archived but is available on the   -                 OpenVMS Documentation CD-ROM.   E                  Preparing to Upgrade in a VAXcluster Environment 6-3            0 Preparing to Upgrade in a VAXcluster Environment 6.2 Types of Upgradese     6.2.2  Rolling Upgrades   <       During a rolling upgrade, you can keep some of the VAX?       computers in the cluster running while you upgrade others]<       (you must have more than one system disk). The cluster?       runs temporarily with different versions of the operatingi
       system.   ?          ________________________ Note ________________________d  6          For OpenVMS VAX Version 7.3 rolling upgrades,:          all nodes in the cluster must be running at least>          OpenVMS VAX Version 6.1. (See Section 5.1.10 for more          information.)  ?          ______________________________________________________S  6       To perform a rolling upgrade, go to Section 6.4.   6.3  Concurrent Upgradem  +       This section describes the following:   '       o  How a concurrent upgrade works   ?       o  Tasks you need to perform to prepare your system for a           concurrent upgrade.  % 6.3.1  How a Concurrent Upgrade Works   @       During a concurrent upgrade, you must shut down the entire>       cluster and upgrade each system disk and reboot each VAX=       computer in the cluster. When the cluster reboots, each >       VAX computer will be running the upgraded version of the#       OpenVMS VAX operating system.h  ) 6.3.2  Preparing for a Concurrent Upgrade   <       To prepare for a concurrent upgrade, use the following       procedure:  A       1. Shut down the entire cluster by logging in to the SYSTEM =          account on each node locally, entering the following ;          command, and choosing the CLUSTER_SHUTDOWN option:s            $ @SYS$SYSTEM:SHUTDOWN   A       2. If you have only one system disk for your cluster, go too          step 3.  5 6-4  Preparing to Upgrade in a VAXcluster Environmenta t  h      E                      Preparing to Upgrade in a VAXcluster EnvironmentbE                                                6.3 Concurrent Upgradeo    A              If you have more than one system disk, select one toM              upgrade.o  C             _______________________ Caution _______________________   ?             You cannot use the system disk that you usually use =             as the quorum disk to hold the save sets from thea             distribution kit.s  B             ______________________________________________________  C           3. Perform a conversational boot of a single VAX computer A              from the system disk you will be upgrading. For moreuA              information about the conversational boot procedure,dA              refer to the upgrade and installation supplement ford              your VAX computer.   @              At the SYSBOOT> prompt, use the SHOW VOTES and SHOWD              EXPECTED_VOTES command to display the current values ofE              the parameters. Write these values down because you willoD              need to restore them later. Set the VOTES and EXPECTED_B              VOTES values to 1 by entering the following commands:  !              SYSBOOT> USE CURRENT !              SYSBOOT> SET VOTES 1_*              SYSBOOT> SET EXPECTED_VOTES 1              SYSBOOT> CONTINUE  <           4. Upgrade the system disk, using the procedure in              Chapter 7.w  <           5. If you have only one system disk, go to step 6.  A              If you have more than one system disk, shut down thet?              system that you just upgraded. Then repeat steps 2pB              through 4 to upgrade each system disk in the cluster.E              When you finish upgrading all of the system disks, go tot              step 6.  @           6. Reboot each computer in the VAXcluster environment.  =           7. Complete the postupgrade procedures described in               Chapter 8.     E                  Preparing to Upgrade in a VAXcluster Environment 6-5l o  m      0 Preparing to Upgrade in a VAXcluster Environment 6.4 Rolling Upgrade      6.4  Rolling Upgrade  +       This section describes the following:r  $       o  How a rolling upgrade works         o  Notes and restrictionsi  ?       o  Tasks you need to perform to prepare your system for at          rolling upgrade  " 6.4.1  How a Rolling Upgrade Works  <       During a rolling upgrade, you upgrade each system disk8       individually, allowing old and new versions of the;       operating system to run together in the same cluster,v@       creating a mixed-version cluster. Because rolling upgrades@       allow mixed-version clusters, the systems that you are not!       upgrading remain available.r   6.4.2  Notes and Restrictionsr  ;       The following restrictions apply to rolling upgrades:   >       o  Compaq recommends that all VAX computers in a cluster=          run the same version of the operating system. Mixed-d<          version clusters are supported only for the purpose>          of upgrading the entire cluster incrementally. Compaq@          further recommends that all VAX systems in a VAXcluster<          run the latest version of the OpenVMS VAX operating          system.  ?       o  A rolling upgrade does not apply when all systems boot_@          from a single system disk. When all systems boot from a?          single system disk, perform a concurrent upgrade usingo0          the procedure described in Section 6.3.  :       o  During the rolling upgrade, the queuing system isA          disabled on the nodes being upgraded. The queuing system ?          on the other nodes should be unaffected by the upgradeo5          as long as a START/QUEUE/MANAGER/ON=(upgradei/          node . . .) command is not executed. A >          START/QUEUE/MANAGER command could attempt to move the@          queue manager process to the node being upgraded if the@          /ON qualifier indicates that it is one of the preferred@          nodes. If the queue manager attempts to run on the node<          being upgraded, the queuing system will hang on the          entire cluster.  5 6-6  Preparing to Upgrade in a VAXcluster Environment            E                      Preparing to Upgrade in a VAXcluster EnvironmentsE                                                   6.4 Rolling Upgradew    ,              If your startup file contains aF              START/QUEUE/MANAGER/ON=(upgrade node1, node2 . . . noden)A              command, do not boot in any nonupgrading nodes until_A              you have removed that command from the startup file.V@              Booting in a node causes the queuing system to hangB              on the cluster if the START/QUEUE/MANAGER/ON=(upgradeD              node, . . . ) command is executed. When the upgrade hasC              completed, you can add the command back to the startupp              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 upgradingk/              by entering the following command:.  :              START/QUEUE/MANAGER/ON=(nonupgrading node1, -              node2 . . . noden)   )     6.4.3 Preparing for a Rolling Upgradek  ?           To prepare for a rolling upgrade, follow these steps:e  A           1. Check the votes and make adjustments to maintain the A              proper quorum so the cluster can continue to operatey=              throughout the upgrade. (OpenVMS Cluster Systems 1              describes this procedure in detail.)_  -           2. Select a system disk to upgrade.o  E           3. Shut down all VAX computers booting from the system diskaE              that you are upgrading, except for the computer that youmE              will use to apply the upgrade. VAX computers that do not_D              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_VOTESu  E              d. Repeat steps a to c for each VAX computer requiring ai                 shutdown.]  E                  Preparing to Upgrade in a VAXcluster Environment 6-7s m  a      0 Preparing to Upgrade in a VAXcluster Environment 6.4 Rolling Upgrade_    >          This procedure lets one VAX computer continue running>          from the system disk (assuming computers running from>          different system disks supply enough votes to sustain          cluster quorum).1  >       4. If proper quorum is not maintained at any time during@          the upgrade procedure, the shutdown procedure will hang=          the cluster. If the cluster hangs during a shutdown, @          enter the following commands on the system console of a,          CPU that is still a cluster member:            $ <Ctrl/P>o          >>> H          >>> D/I 14 Cp          >>> C          IPC> Q           IPC> <Ctrl/Z>  7       5. Upgrade the system disk using the procedure in           Chapter 7.r  @          _______________________ Caution _______________________  ?          The upgrade procedure requires exclusive access to then>          drive that holds the distribution media. Do not mount/          the distribution media on other nodes.d  ?          ______________________________________________________   A       6. During phase 1 of the upgrade, the procedure asks if youi>          are performing a rolling upgrade. If you enter Y, theA          procedure asks you several questions to determine if allW@          system disks in the cluster (other than the one you areA          upgrading) are running at least OpenVMS VAX Version 6.2..          For example:p  E          * Are the other system disks running OpenVMS V6.2 or higher?e  <          All systems in the cluster must be running at least@          OpenVMS VAX Version 6.2 to perform the rolling upgrade.!          Type Y and press Return.s  A       7. When the upgrade has completed, reboot each VAX computer_@          that boots from the system disk you have just upgraded.  >       8. Perform the postupgrade tasks described in Chapter 8.  5 6-8  Preparing to Upgrade in a VAXcluster Environment     i      E                      Preparing to Upgrade in a VAXcluster Environment_E                                                   6.4 Rolling Upgradec    =           9. Repeat steps 2 to 7 for each system disk you areFD              upgrading. Once you have performed tasks a to d in step6              3, you do not need to perform them again.  7     6.5 Adding an OpenVMS VAX Version 7.3 Supported CPU   ?           If you need to add a new CPU supported by OpenVMS VAX C           Version 7.3 to an existing Version 6.2 VAXcluster, Compaq A           supports two options, listed in the following preferred            order:  B           1. Upgrade the entire cluster to OpenVMS VAX Version 7.32              and bring the new CPU in as a member.  ?           2. If you need to keep some systems in the cluster at_D              OpenVMS VAX Version 6.2, you must upgrade a system diskD              in the cluster to Version 7.3 using the rolling upgradeA              procedure and then boot the new CPU into the clustert$              using that system disk.                                                    E                  Preparing to Upgrade in a VAXcluster Environment 6-9                          E                                                                     7aE     _________________________________________________________________   E                            Upgrading the OpenVMS VAX Operating Systemm    D           This chapter explains the procedure for upgrading a single-           OpenVMS VAX system disk, including:V  A           o  How to prepare for booting from the [SYSF] directoryA  %           o  How to configure devices   %           o  How to begin the upgrades  A           o  What the procedure does and what you are asked to dor1              during the six phases of the upgradeT  @           You must complete each phase of the upgrade procedure.@           On most VAX computers, the upgrade procedure continuesE           automatically from phase to phase. Read the screen displaysl@           carefully and, if you need to reboot your VAX computerD           manually, refer to the upgrade and installation supplement>           for your VAX computer and Appendix C of this manual.  C           The time required to complete an upgrade varies depending.@           on your hardware configuration and on the distributionE           media you are using. In most cases, magnetic tapes and tapep:           cartridges require more time than compact discs.  C           Before you begin the upgrade procedure, read the overviewr=           of the upgrade procedure described in Chapter 1 andt?           complete the preupgrade tasks described in Chapter 5. ?           If you are upgrading a VAXcluster, you must also reado           Chapter 6.              E                        Upgrading the OpenVMS VAX Operating System 7-1o    g      * Upgrading the OpenVMS VAX Operating System! 7.1 Preparing to Boot from [SYSF]c    " 7.1  Preparing to Boot from [SYSF]  =       During the upgrade procedure, you are asked to boot the :       system from the [SYSF] directory on the system disk.=       The [SYSF] directory is a root directory created on theo@       system disk by the upgrade procedure. It temporarily holds>       the system files used in the upgrade until the procedure>       moves the files to their permanent location. The upgradeA       procedure then removes the [SYSF] directory from the systemu       disk.e  :       If you do not know how to boot from [SYSF], read the?       upgrade and installation supplement for your VAX computer $       and Appendix C of this manual.  ;       Ignore any error messages after the first reboot thatP=       indicate an invalid dump header version. These messages (       are normal and are to be expected.  ( 7.1.1  Modifying Boot Command Procedures  ?       Some VAX computers require a special command procedure to ?       boot from [SYSF]. If you are performing an upgrade on oneM>       of the following VAX computers, you must modify the boot@       command procedures, DEFBOO and dddGEN before beginning the       upgrade procedure:  +          VAX 8530, 8550, 8700, 8810, 8820-Ni          VAX 8820, 8830, 8840t  :       To modify the boot command procedures, exit from the<       OpenVMS VAX operating system (but do not shut it down)<       and enter the appropriate console mode. Make copies of?       DEFBOO and dddGEN before you modify them. Name the copies         DEFBOO.SAV and dddGEN.SAV.  :       The upgrade and installation supplement for your VAXA       computer describes the procedures for copying and modifyinga>       DEFBOO and dddGEN. Use these procedures to modify DEFBOO=       and dddGEN so that they specify [SYSF] as the directoryi       from which to boot.   @       In DEFBOO, change the DEPOSIT command that sets boot flags$       in register 5 (R5) as follows:         DEPOSIT R5=F0000000r  / 7-2  Upgrading the OpenVMS VAX Operating System  l  t      E                            Upgrading the OpenVMS VAX Operating System E                                     7.1 Preparing to Boot from [SYSF]y    ;           In dddGEN, change the DEPOSIT command as follows:              DEPOSIT R5 F0000001d  2     7.1.2 VAX 8200, 8250, 8300, and 8350 Computers  >           If you are upgrading a VAX 8200, 8250, 8300, or 8350A           computer, you must create a boot command procedure thato=           allows you to boot from the [SYSF] directory beforeg=           beginning the upgrade. The upgrade and installationsB           supplement for your VAX computer describes how to create&           this boot command procedure.       7.1.3 Configuring Devicesy  @           Because you rebooted your system with minimum startup,A           the system did not automatically configure all devices. B           However, you might need access to some of the devices to           perform the upgrade.  ?           To make sure you can access the devices that might be ?           needed for the upgrade, run SYSGEN to reconfigure the E           devices on the system and run STARTUP CONFIGURE by entering !           the following commands:m  !           $ RUN SYS$SYSTEM:SYSGEN #           SYSGEN> AUTOCONFIGURE ALLp           SYSGEN> EXIT)           $ @SYS$SYSTEM:STARTUP CONFIGUREr       7.2 Performing the Upgrade  C           This section describes how to start the upgrade procedureuE           using VMSINSTAL. You can type a question mark (?)  for help .           at any time while running VMSINSTAL.  C           The instructions refer to the source drive and the target            drive, where:e  9           o  The source drive is the drive that holds thei              distribution kit.  @           o  The target drive is the drive that holds the system              disk.  E                        Upgrading the OpenVMS VAX Operating System 7-3I    r      * Upgrading the OpenVMS VAX Operating System 7.2 Performing the Upgrade    ! 7.2.1  Loading Distribution Media_  ?       Place the distribution compact disc or tape in the sourceu:       drive. If your OpenVMS VAX distribution kit contains>       several tapes, put the first one in the drive. The paper=       labels on the tapes indicate the order in which you use_       them._  6       If you are not using an InfoServer device, go to       Section 7.2.3.  @       If you are using an InfoServer device, proceed to the next       section.  $ 7.2.2  Upgrading from the InfoServer  9       If upgrading from an InfoServer device, perform theh       following steps:  =       1. Start the InfoServer Client software by entering the           following command:   *          $ @SYS$STARTUP:ESS$STARTUP CLIENT  6          The CLIENT parameter loads the client driver,@          ESS$DADDRIVER.EXE, and the InfoServer transport driver,          ESS$LASTDRIVER.EXE.  ;       2. As the startup procedure executes, it displays the           following messages:  6          %LASTCP-I-VERSION, LASTDRIVER X1.5 is stoppedC          %LASTCP-I-ADAINIT, Initializing adapter xxx for LASTDRIVER ?          %LASTCP-I-STARTED, LASTDRIVER X1.5 started on node yyyn  A       3. After you start the InfoServer Client software, you mustlA          make the compact disc drive accessible to your system by (          completing the following steps:  ?          a. Insert the distribution compact disc in the compacta3             disc drive connected to the InfoServer.   )          b. Enter the following commands:   &             $ RUN SYS$SYSTEM:ESS$LADCP0             LADCP> BIND/CONNECT/SYSTEM VAXVMS073L             %LADCP-I-BIND, service bound to logical unit DAD$VMS073 (_DADn:)             LADCP> EXIT,  / 7-4  Upgrading the OpenVMS VAX Operating System     l      E                            Upgrading the OpenVMS VAX Operating System E                                            7.2 Performing the Upgradem    @              Make note of the device name _DADn: in the previous?              display. You will have to specify this device names               during the upgrade.       7.2.3 Starting VMSINSTAL  :           To start VMSINSTAL, use the following procedure:  *           1. Log in to the SYSTEM account.  )           2. Enter the following command:   $              $ @SYS$UPDATE:VMSINSTAL  @           VMSINSTAL displays a message similar to the following,?           depending on which version of the operating system is +           currently running on your system:_  J                   OpenVMS VAX Software Product Installation Procedure V7.3  %           It is 13-NOV-2000 at 10:08.   9           Enter a question mark (?) at any time for help.                                             E                        Upgrading the OpenVMS VAX Operating System 7-5i t  A      * Upgrading the OpenVMS VAX Operating System 7.2 Performing the Upgrade    @       VMSINSTAL checks your system's account quotas. If it finds=       account quotas that are less than it expects, VMSINSTAL 2       displays a message similar to the following:  C %VMSINSTAL-W-LOWQUOTA, The following account quotas may be too low.iM -VMSINSTAL-W-LOWQUOTA, If you want to modify these account quotas, type NO to P -VMSINSTAL-W-LOWQUOTA, the next question, modify the appropriate quotas, log outC -VMSINSTAL-W-LOWQUOTA, then log back in and restart this procedure.r  =                BYTLM: currently 32512; minimum expected 32768e  ,       * Do you want to continue anyway [NO]?  >       You should have verified that your SYSTEM account quotas8       were sufficient before beginning the upgrade. (See;       Section 5.5.8 for the minimum required values and for 4       instructions for modifying quotas and limits.)  9       To modify the account quotas now, do the following:o  "       1. Type No and press Return.  6       2. Modify the account quotas you want to change.  @       3. Log out of the SYSTEM account; then log back in so that*          the new quotas will be in effect.         4. Restart VMSINSTAL.e  ;       To continue the upgrade without modifying the account (       quotas, type Yes and press Return.  ! 7.2.4  Backing Up the System Diska  3       The procedure displays the following message:o  D       * Are you satisfied with the backup of your system disk [YES]?  >       If you have made a standalone BACKUP of the system disk,+       press Return and go to Section 7.2.5.e  ;       If you have not made a standalone image backup of thes$       system disk, do the following:  A       1. Type N (for No) and press Return. VMSINSTAL ends and the -          dollar-sign prompt ($) is displayed.   @       2. Back up the system disk as described in the upgrade and7          installation supplement for your VAX computer.s  / 7-6  Upgrading the OpenVMS VAX Operating Systemx o  h      E                            Upgrading the OpenVMS VAX Operating System E                                            7.2 Performing the Upgrade     C           3. After you have made a backup of the system disk, starts)              the upgrade procedure again.i  B             ________________________ Note ________________________  >             If the upgrade procedure fails and you do not have<             a current backup of the system disk that you are<             upgrading, you may not be able to recover to the5             previous version of the operating system.8  B             ______________________________________________________  %     7.2.5 Specifying the Source Driveu  A           VMSINSTAL asks for the name of the drive that holds the            distribution media:d  ;           * 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 a:           device name of MUC6, type MUC6 and press Return.  A           If the drive is connected to an HSC, enter the HSC nametE           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 theO%           following and press Return:   E           * Where will the distribution volumes be mounted: MUTT$MUA0   ?           If you are not using an InfoServer device, proceed toE           Section 7.2.6.  B           If you are upgrading from a compact disc drive connected?           to an InfoServer, the device name is DADn. The n parto@           of the device name was displayed when you bound to the>           distribution compact disc as previously described in           Section 7.2.2.  E           If VMSINSTAL displays an error message, make sure the drivewD           is connected and set up properly. Enter the name again. IfE           VMSINSTAL displays another error message, use the followingu.           procedure to verify the device name:  1           1. Press Ctrl/Y to exit from VMSINSTAL.u  E                        Upgrading the OpenVMS VAX Operating System 7-7d           * Upgrading the OpenVMS VAX Operating System 7.2 Performing the Upgrade    @       2. Enter the SHOW DEVICE command to make sure you have the          correct device name.O  :       3. Restart the upgrade procedure from Section 7.2.3.  @       If VMSINSTAL does not display an error message, proceed to       Section 7.2.6.    7.2.6  Entering the Product Name  @       When VMSINSTAL displays the following message, type VMS073>       and press Return. Make sure that you use the number zero=       (not the letter "O") when you type VMS073. For example:   P       Enter the products to be processed from the first distribution volume set.       * Products: VMS073  >       When the procedure displays the following message, press
       Return:   :       * Enter installation options you wish to use (none):    7.2.7  Mounting the First Volume  <       VMSINSTAL displays a message similar to the following:  :       Please mount the first volume of the set on DKB200:.  ?       When the procedure displays the following message, type Y !       (for Yes) and press Return:i         * Are you ready? Y  ?       The procedure displays messages similar to the following:e  <       %MOUNT-I-MOUNTED, VAXVMS073 mounted on _VXPCSI$DKB200:  /       The following products will be processed:            VMS V7.3  <       After a slight pause, the procedure displays a message       similar to the following:o  9               Beginning installation of VMS V7.3 at 10:08r  ;       %VMSINSTAL-I-RESTORE, Restoring product saveset A ...g  / 7-8  Upgrading the OpenVMS VAX Operating SystemI S  e      E                            Upgrading the OpenVMS VAX Operating SystemeE                                            7.2 Performing the Upgrade     ,     7.2.8 Monitoring Messages from VMSINSTAL  C           The upgrade procedure displays several important messagesE:           that provide you with the following information:  %           -  What VMSINSTAL is doing.c  E           -  Notes, suggestions, and restrictions about various parts               of the upgrade.  #           -  Status of the upgrade.A  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 thep           following message:  +           * Do you want to continue? (Y/N):n  =           To continue the upgrade, type Yes and press Return.h  5           To interrupt the upgrade, do the following:e  &           1. Type No and press Return.  D           2. If prompted for another product, type EXIT to exit from              VMSINSTAL.M  %     7.2.9 Verifying the Date and Timeb  B           The procedure displays the current date and time. If theE           date and time are correct, type Yes. If they are incorrect, D           type No. Enter the correct date and time using the 24-hour5           clock format and press Return. For example:   J           PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) 13-NOV-2000 10:19       7.3 Upgrade Phase 1   D           This section describes Phase 1 of the upgrade. During thisE           phase, you provide passwords for system accounts and selecthB           OpenVMS options, and the procedure restores the files in3           the OpenVMS required save set (VMS073.B).   E           At the end of this phase, the procedure shuts down your VAXeD           computer. If your computer uses console media when bootingE           and the boot file was modified as described in Section 7.1, E           the system should reboot automatically. Otherwise, you must72           reboot manually from the SYSF directory.  E                        Upgrading the OpenVMS VAX Operating System 7-9            * Upgrading the OpenVMS VAX Operating System 7.3 Upgrade Phase 1a    % 7.3.1  Specifying the Type of Upgradeh  ;       At the beginning of Phase 1, the procedure displays a '       message similar to the following:u  2           Upgrade Phase 1  13-NOV-2000 10:19:30.85  4       * Are you performing a rolling upgrade? (Y/N):  A       If you are performing a concurrent upgrade or an upgrade ona4       a standalone system, type No and press Return.  ;       If you are performing a rolling upgrade, type Yes andN<       press Return. The procedure asks you several questionsA       to determine if all system disks in the cluster (other thanhA       the one you are upgrading) are running at least OpenVMS VAXp:       Version 6.2. Follow the instructions in Section 6.4.  ) 7.3.2  SYSTEST and FIELD Account CreationS  =       If your system does not have SYSTEST or FIELD accounts,u>       you will be given the opportunity to create them at this@       time. These accounts are not required for normal operation?       of OpenVMS. The User Environment Test Program (UETP) uses <       SYSTEST to perform its functions. If this account does@       not exist you will have to create it in order to run UETP.>       FIELD is traditionally used for field service access. If<       this account does not exist, you may have to create it>       later or provide an alternate account for field service.  (       SYSTEST account does not exist ...2       * Do you want to create this account? (Y/N):  &       FIELD account does not exist ...2       * Do you want to create this account? (Y/N):   7.3.3  Entering Passwordsa  ?       To ensure system security, the upgrade procedure requiresc?       you to enter passwords for the SYSTEM, SYSTEST, and FIELDk;       accounts before continuing. Passwords must contain atT?       least 8 characters; they are not displayed by the system. ?       Press Return after you enter each password and it will bes>       verified. You will not be prompted for SYSTEST and FIELD<       passwords if those accounts do not exist. For example:  0 7-10  Upgrading the OpenVMS VAX Operating System           E                            Upgrading the OpenVMS VAX Operating System E                                                   7.3 Upgrade Phase 1u    P           To help provide a more secure system, you are asked to enter passwordsN           for key system accounts. Passwords must be a minimum of 8 characters=           in length. You can enter new or existing passwords.   5           Enter passwords for the following accounts:e  -                        SYSTEM, SYSTEST, FIELDe  &           * Enter password for SYSTEM:%           * Reenter for verification: 0           %UAF-I-MDFYMSG, user record(s) updated?           %VMS-I-PWD_OKAY, account password for SYSTEM verifiedI  '           * Enter password for SYSTEST:o&           * Re-enter for verification:0           %UAF-I-MDFYMSG, user record(s) updated@           %VMS-I-PWD_OKAY, account password for SYSTEST verified  L                The SYSTEST_CLIG account will be disabled.  You must reenableC                it before running UETP but do not assign a password..  %           * Enter password for FIELD:o%           * Reenter for verification: 0           %UAF-I-MDFYMSG, user record(s) updated>           %VMS-I-PWD_OKAY, account password for FIELD verified  C           If you enter a password incorrectly or if the password isaB           too easy to guess, the procedure displays error messages#           similar to the following:   E           %VMS-W-PWD-INVALID, account password for SYSTEST is invalidt8           %VMS-I-PWD-WEAK, password is too easy to guess  L Because of the preceding error, you must take action to secure this account.F You must either disable this account, change its password, or do both.  E           When the procedure asks if you want to disable the account,lB           type No and press Return. When the procedure asks if youB           want to enter a new password, type Yes and press Return.1           Then enter a new password. For example:v  5           Do you want to disable the account (Y/N)? N =           Do you want to change the account password (Y/N)? YaN        You must now select a new primary password for the SYSTEST account. TheP        password you select must be at least 8 characters in length and cannot be.           the same as the name of the account.  E                       Upgrading the OpenVMS VAX Operating System 7-11e           * Upgrading the OpenVMS VAX Operating System 7.3 Upgrade Phase 1            New password:        Verification:u+       %UAF-I-MDFMSG, user record(s) updated >       %VMS-I-PWD-SET, primary password for account SYSTEST set  9       After you have correctly entered the passwords, the #       procedure does the following:   >       o  Checks the account quotas in the DEFAULT, SYSTEM, and>          various other accounts and modifies them if necessary  ,       o  Turns off quotas on the system disk         o  Stops OPCOM  +       o  Stops the error formatter (ERRFMT)s   7.3.4  Choosing the Boot Methode  =       If your VAX computer is not one of the following, go to        Section 7.3.5.            VAX-11/730o          VAX-11/750n          VAX-11/780 #          VAX 8200, 8250, 8300, 8350m          VAX 8600, 8650           VAX 9000t  =       If your VAX computer is included in the preceding list,e=       the procedure can temporarily modify the DEFBOO.CMD (orr>       DEFBOO.COM if you have a VAX 8600 computer) to boot from>       the [SYSF] directory. During Phase 4 of the upgrade, theA       procedure restores the DEFBOO.CMD (or DEFBOO.COM) file that ?       is set up to boot from the current system disk and system        root.   ?       The procedure displays a message similar to the following :       (except for VAX-11/730, 11/780, and 8600 computers):  5       * Do you want to boot from the [console media]?   @       If you prefer to boot your system manually from the [SYSF];       directory or if you are booting directly from a localeA       system disk, type No, press Return, and go to Section 7.3.5o       to continue the upgrade.  @       Type Yes and press Return if one of the following is true:  1       o  You want to boot from the console media.h  0 7-12  Upgrading the OpenVMS VAX Operating System           E                            Upgrading the OpenVMS VAX Operating SystemiE                                                   7.3 Upgrade Phase 1S    <           o  Your computer is a VAX-11/730, 11/780, or 8600.  #           o  You are using a CI750.   B           The procedure prompts you to insert the console media inE           the drive. Insert the backup copy of the console media intonA           the drive and do not remove it from the drive until the D           upgrade has been completed. Make sure the console media is           write enabled.       7.3.5 File Cleanup  +           The procedure does the following:   B           o  Checks for the location of the SYS$TIMEZONE.DAT file,D              which must now be in the SYS$COMMON:[SYSEXE] directory.;              If the procedure finds this file in some other A              directory, it deletes it from that directory. Later, A              during the final phase of the upgrade, the procedurer?              prompts you for the information it needs to create ?              a SYS$TIMEZONE.DAT file in the SYS$COMMON:[SYSEXE]:              directory.s  @           o  Renames files found in SYS$SPECIFIC:[SYSMGR] and in?              SYS$COMMON:[SYSMGR] by adding _OLD_SPECIFIC to thenD              file extensions. For example, [SYSMGR]LOGIN.COM becomesE              [SYSMGR]LOGIN.COM_OLD_SPECIFIC. (The file extensions are ?              restored during Phase 6 of the upgrade procedure.)A  @           o  Cleans up the system disk by purging all accountingA              data files, operator logs, and the directory SYSERR.iA              The procedure also deletes all JNL files in the roots.              directory and its subdirectories.  E           o  Builds the directory tree [SYSF] and deletes the OpenVMSaC              VAX and DECwindows files that are not needed to rebooty+              during Phase 2 of the upgrade.y  D           As the procedure performs each of these tasks, it displaysC           messages describing what is being done. When this step is D           completed, the procedure displays a message similar to the           following:  9           File cleanup complete - 13-NOV-2000 10:34:16.34   E                       Upgrading the OpenVMS VAX Operating System 7-13     y      * Upgrading the OpenVMS VAX Operating System 7.3 Upgrade Phase 1     , 7.3.6  Selecting Optional OpenVMS Components  ?       The procedure displays information about optional OpenVMSh;       VAX files and the remaining amount of disk space. The @       information is similar to the following (block sizes might       vary slightly):u  G       Select optional software you want to install. You can install ones@       or more of the following OpenVMS or DECwindows components:  D       o OpenVMS library                              -  52200 blocksD       o OpenVMS optional                             -  19000 blocksD       o OpenVMS Help Message                         -  10400 blocksD       o OpenVMS Management Station                   -  20000 blocksD       o DECwindows base support                      -   4400 blocksD       o DECwindows workstation support               -  23800 blocksC             -  75 dots per inch video fonts          -   (included).D             - 100 dots per inch video fonts          -   6200 blocksD       o DECnet-Plus networking                       -  80000 blocksD       o DECnet Phase IV networking                   -    800 blocks  4       Space remaining on system disk: 1674710 blocks  A       You must indicate which of the options you want to install. A       If you require network support, you must select the OpenVMSh       library component.  :       Note that if you do not install the optional OpenVMS=       components at this time, you can install them after theS?       upgrade by using the VMSTAILOR and DECW$TAILOR utilities.o:       However, the Help Message utility can be tailored on;       (added) to the system disk only. If you do not choosee<       to install the Help Message files at this point in the>       procedure and want them on an alternate device, you will@       not be able to use VMSTAILOR to restore them later. If you=       want to install Help Message files on an alternate diskhA       after the installation procedure completes, you can use ther!       BACKUP command, as follows:o  <       BACKUP/VERIFY source-device:[000000]VMS073.E/SAVE_SET-$       target-device:[directory-name]  <       For source-device, enter the device name for the drive=       on which the distribution media is mounted. For target-D:       device, enter the device name on which the alternate?       disk is mounted, and for directory, enter the name of theo3       directory to which you are copying the files.   0 7-14  Upgrading the OpenVMS VAX Operating System    i      E                            Upgrading the OpenVMS VAX Operating SystemeE                                                   7.3 Upgrade Phase 1o    A           Also note that, for TK50 tape cartridges, it is quicker D           to install OpenVMS VAX software during the upgrade than toB           add software after the upgrade with a tailoring utility.@           For information about using VMSTAILOR, see Chapter 10.?           To select the options you want to install, follow the 2           instructions displayed by the procedure.  !     7.3.6.1 OpenVMS Library Filesr  7           The procedure displays the following message:s  C           * Do you want to install the OpenVMS library files? (Y/N)i  D           The file subclasses of the OpenVMS library (VMS073.C) saveB           set are listed in Appendix D. If you want to install theC           VMS073.C files, type Yes and press Return. If you require >           network support, you must select the OpenVMS library?           component. If you do not want to install the VMS073.Cs*           files, type No and press Return.  "     7.3.6.2 OpenVMS Optional Files  7           The procedure displays the following message:a  D           * Do you want to install the OpenVMS optional files? (Y/N)  @           The file subclasses of the OpenVMS optional (VMS073.D)C           save set are listed in Appendix D. If you want to install.B           the VMS073.D files, type Yes and press Return. If you doC           not want to install the VMS073.D files, type No and press            Return.        7.3.6.3 Help Message Files  7           The procedure displays the following message:   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,r0               which is now separately orderable.  G               The MSGHLP database, MSGHLP$LIBRARY.MSGHLP$DATA, consumes F               approximately 10400 blocks and will be placed by defaultN               on your system disk in SYS$COMMON:[SYSHLP] unless you specify an-               alternate device when prompted.   =           * Do you want to install the MSGHLP database? (Y/N)0  E                       Upgrading the OpenVMS VAX Operating System 7-15A o  t      * Upgrading the OpenVMS VAX Operating System 7.3 Upgrade Phase 1r    =       The Help Message utility is an online system for system8A       messages documentation. You can install Help Message eithere@       on the system disk or on an alternate disk. If you want to@       install the Help Message files, type Yes and press Return.  3       The procedure displays the following message:c  H You can install this database on your system disk in SYS$COMMON:[SYSHLP]E or on an alternate device. If you specify an alternate device, but notG directory, MSGHLP$LIBRARY.MSGHLP$DATA is placed in [HELP_MESSAGE]. WhenfE prompted, take the default of the system disk or specify an alternateo device using this format:p  3                                  device:[directory]c  O       * Where do you want to install the MSGHLP database? [SYS$COMMON:[SYSHLP]]t  9           Space remaining on system disk:  1593110 blocks   <       The Help Message database is installed in the area you       specified.  ) 7.3.6.4  OpenVMS Management Station FilesS  3       The procedure displays the following message:   F          The OpenVMS Management Station is a client-server applicationG          that provides OpenVMS system management capabilities through arI          client application on a personal computer (PC) running MicrosoftsG          Windows. The server application runs on OpenVMS systems and isoI          automatically installed as part of the OpenVMS operating system.t  G          This option provides the files used to create the installationiJ          media for the PC client software.  If you want to use the OpenVMSH          Management Station, you must install these optional files on atI          least one OpenVMS system to create the installation media, whichdF          can then be used to install the PC client on one or more PCs.  E          The OpenVMS Management Station client can run on Windows 3.1eG          (including Windows for Workgroups), Windows NT, or Windows 95.   I The OpenVMS Management Station optional files consume approximately 20000EI blocks and will be placed on your system disk in SYS$COMMON:[TNT.CLIENT].P  M * Do you want to install the optional OpenVMS Management Station files? (Y/N)t  7          Space remaining on system disk: 1573110 blocksL  0 7-16  Upgrading the OpenVMS VAX Operating System E  I      E                            Upgrading the OpenVMS VAX Operating SystemrE                                                   7.3 Upgrade Phase 1l    E           If you want to use the OpenVMS Management Station software,EC           you must install these files. After the upgrade procedureo=           completes, follow the instructions in Appendix G to D           prepare your OpenVMS system and your PC to run the OpenVMS8           Management Station server and client software.  -     7.3.7 Choosing DECwindows Support Options   D           Next, the procedure displays messages about the DECwindows:           components shipped with OpenVMS VAX Version 7.3.  >           The OpenVMS VAX operating system no longer ships the>           OpenVMS DECwindows product. The operating system now?           ships only the DECwindows base support and DECwindowsn@           workstation support components. To get full DECwindows@           support, you must also install the separate DECwindowsA           Motif for OpenVMS VAX (previously called VMS DECwindowsaC           Motif) layered product, which supports both Motif and XUIn           environments.   >           Note that the DECwindows base support and DECwindowsA           workstation support components are not shipped with thewB           DECwindows Motif for OpenVMS VAX layered product. If youD           want to install these options, you must select them now orE           use the DECW$TAILOR option after the installation procedure            completes.  D           Before you indicate whether you want to install DECwindows3           support software, consider the following:   E           ___________________________________________________________ E           If_you..._____________________Then_choose..._______________   @           Intend to install the         DECwindows base support.&           DECwindows Motif for OpenVMS           VAX layered product   C           Intend to install the         DECwindows base support and >           DECwindows Motif for OpenVMS  DECwindows workstation0           VAX layered product on        support.           a workstation or on a             VAXcluster system that           contains workstations     E                       Upgrading the OpenVMS VAX Operating System 7-17i r  o      * Upgrading the OpenVMS VAX Operating System 7.3 Upgrade Phase 1   A       ___________________________________________________________ A       If_you..._____________________Then_choose..._______________o  ?       Are not planning to install   DECwindows base support ando:       the DECwindows Motif for      DECwindows workstation,       OpenVMS VAX layered product   support.        but are installing OpenVMS        VAX on a workstation or on        a VAXcluster that includes       workstations  ?       Want to provide font files    DECwindows base support andd:       for X terminals               DECwindows workstation,                                     support.  ?       Have a workstation monitor    DECwindows base support and :       (for example, a VR150,        DECwindows workstation8       VR160, or VR295) capable      support with the 1005       of displaying 100 dots/inch   dots/inch option.e@       or a VAXstation 4000 series   By selecting the workstation6       computer, which uses 100      support files, you8       dots/inch video fonts by      automatically get 75?       default                       dots/inch video font files,   <                                     and you will be prompted>                                     to indicate if you want to?                                     install 100 dots/inch videotA       ______________________________font_files.__________________u                                    0 7-18  Upgrading the OpenVMS VAX Operating System           E                            Upgrading the OpenVMS VAX Operating SystemhE                                                   7.3 Upgrade Phase 1l    /           The procedure displays the following:   E You can select DECwindows now, or you can use the DECW$TAILOR utility 6 to provide or remove DECwindows support after upgrade.  J Some media, TK50s in particular, can be very slow when tailoring on files.L You might want to select DECwindows now and tailor off unwanted files later.  0 NOTE: This kit does NOT contain full DECwindows.= To obtain full DECwindows, you must also install the separateV2 layered product, DECwindows Motif for OpenVMS VAX.H Version 1.2-3 is the minimum version of DECwindows Motif for OpenVMS VAX' that can be used with OpenVMS VAX V7.3.   D The DECwindows components provided in this kit require approximately% 34400 blocks, broken down as follows:i  O                    o DECwindows base support                    -   4400 blocks O                    o DECwindows workstation support             -  23800 blocksMO                      -  75 dots per inch video fonts                 (included) O                      - 100 dots per inch video fonts (optional) -   6200 blockss  D                You must select the DECwindows base support option if<                    - you plan to run DECwindows software, or3                    - you are installing this kit onO)                        * a workstation or D                        * a VAXcluster that contains workstations, orC                    - you want to provide font files for Xterminals.   C If you are installing this kit on a system that includes Xterminals H and you do NOT select DECwindows base support, then you will have to use. the DECW$TAILOR utility to provide font files.  <           * Do you want the DECwindows base support? (Y/N) y  .                Space remaining: 1568710 blocks  K                You must select the DECwindows workstation support option ift3                    - you are installing this kit on )                        * a workstation or D                        * a VAXcluster that contains workstations, orC                    - you want to provide font files for Xterminals.   C If you are installing this kit on a system that includes XterminalstH and you do NOT select DECwindows workstation support, then you will have5 to use the DECW$TAILOR utility to provide font files.   J           * Do you want to provide DECwindows workstation support? (Y/N) y  E                       Upgrading the OpenVMS VAX Operating System 7-19R .  H      * Upgrading the OpenVMS VAX Operating System 7.3 Upgrade Phase 1o    +            Space remaining:  1544910 blockse  I DECwindows workstation support includes the 75 dots per inch video fonts.   B All DECwindows applications run with 75 dots per inch video fonts.D By default, most systems start up with 75 dots per inch video fonts.I Certain applications can take advantage of 100 dots per inch video fonts.   P            For the VAXstation 4000 series machine, 100 dots per inch video fontsO            are used by default.  If you decide not to install 100 dots per inchnO            video fonts, you must edit SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COMeO            to force 75 dots per inch video fonts to be the default.  Otherwise,r<            certain applications may not space text properly.  E For instructions on how to configure your system with both 75 and 100MD dots per inch video fonts, see the installation guide or look at theJ template command procedure SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE.  C       *Do you want 100 dots per inch video fonts installed? (Y/N) yl  )          Space remaining:  1538710 blockso  $ 7.3.8  Upgrading Networking Products  A       Next, the procedure displays messages describing the DECnett<       options. For more information, refer to Section 1.1.2.  K           Beginning with OpenVMS V7.1, the DECnet-Plus kit is provided withWL           the OpenVMS operating system kit.  Compaq strongly recommends thatM           DECnet users install DECnet-Plus.  DECnet Phase IV applications areS#           supported by DECnet-Plus.n  L           DECnet Phase IV is also provided as an option.  Support for DECnetH           Phase IV is available through a Prior Version Support Contract0           available through Compaq MCS Services.  B           If you install DECnet-Plus and TCP/IP you can run DECnetE           applications over a TCP/IP network.  Please see the OpenVMS I           Management Guide for information on running DECnet over TCP/IP.   L           If you plan to install DECnet Phase IV, do NOT select DECnet-Plus.  3       * Do you want to install DECnet-Plus. (Y/N) y   ?       If you are upgrading from OpenVMS VAX Version 7.2 and are <       changing DECnet products, the procedure prompts you to@       remove the version of DECnet installed on your system. YouA       must remove this DECnet product because both Compaq DECnet-i>       Plus for OpenVMS VAX and DECnet Phase IV for OpenVMS VAX6       products cannot run concurrently on your system.  0 7-20  Upgrading the OpenVMS VAX Operating System    p      E                            Upgrading the OpenVMS VAX Operating SystempE                                                   7.3 Upgrade Phase 1o    E           The following message shows an upgrade from DECnet Phase IVl@           for OpenVMS VAX to Compaq DECnet-Plus for OpenVMS VAX:  7           * Do you want to install DECnet-Plus? (Y/N) y   9               DECnet Phase IV is intalled on your system. M               Before installing DECnet-Plus, you must remove DECnet Phase IV.E  9           *Do you want to remove DECnet Phase IV? (Y/N) y   2           The following product has been selected:F               DEC VAXVMS DECNET_PHASE_IV V7.3          Layered Product  N        Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...100%  1           The following product has been removed:sF               DEC VAXVMS DECNET_PHASE_IV V7.2          Layered Product  =               Space remaining on system disk:  1458710 blocksh        7.3.9 Verifying Your Choices  E           The procedure displays a list of OpenVMS VAX and DECwindowsE@           support options that you have chosen and gives you the>           opportunity to change your mind before proceeding by+           displaying the following message:w  5               The following options will be provided:   !                   OpenVMS libraryr"                   OpenVMS optional&                   OpenVMS Help MessageA                   OpenVMS Management Station Software -- PC filesm)                   DECwindows base support 6                   DECwindows workstation support with:5                       -  75 dots per inch video fonts 5                       - 100 dots per inch video fonts_                   DECnet-Plusl  =               Space remaining on system disk:  1458710 blocksn  $           * Is this correct? (Y/N) y  B           If you answer Yes to this prompt, the procedure restoresA           the OpenVMS required save set (VMS073.B) and purges thet4           page, swap, dump, and authorization files.  E                       Upgrading the OpenVMS VAX Operating System 7-21            * Upgrading the OpenVMS VAX Operating System 7.3 Upgrade Phase 1     <       If you answer No to this prompt, you can respecify the9       OpenVMS VAX and DECwindows options that you want ton?       install. The procedure restores the DECwindows components 2       you have chosen during Phase 2. For example:  B           During Phase 2 you will be required to provide input if:  /               o Your OpenVMS kit is multivolume -               o You chose an alternate device ,               o You chose DECwindows options  L           Now copying over the OpenVMS and DECwindows V7.3 REQUIRED save set7       %BACKUP-I-STARTVERIFY, starting verification passt  B           Purging pagefile, swapfile, dump file, and authorization$           files back to one version.  H           Entering old page, swap, dump, errlog, and authorization files            in new directory tree.  M           Setting the startup command file for the next phase of the upgrade.S  >           Renaming SYS$SYSDEVICE:[SYS0.SYSEXE]MODPARAMS.DAT to?                    SYS$SYSDEVICE:[SYS0.SYSEXE]MODPARAMS.DAT_OLDsB           Renaming SYS$SYSDEVICE:[SYS0.SYSEXE]MODPARAMS.DAT_NEW to;                    SYS$SYSDEVICE:[SYS0.SYSEXE]MODPARAMS.DATrB           Renaming SYS$SYSDEVICE:[SYS0.SYSEXE]VAXVMSSYS.PAR_NEW to;                    SYS$SYSDEVICE:[SYS0.SYSEXE]VAXVMSSYS.PARw  ! 7.3.10  Shutting Down Your Systema  A       After several minutes, the upgrade procedure indicates thatu@       the system will shut down to reboot the partially upgraded>       OpenVMS VAX system and displays information about how to       reboot the system:  =           System shutting down to boot the new kernel system. K           (Please ignore any error messages during the SHUTDOWN procedure.)l  I           The distribution kit must remain on DKB200: and the system disktM           must remain on VXPCSI$DKB100: in order to proceed to the next phaseo           of the upgrade.8  B           The sysgen parameters are set to boot any system. Do not?           change them during the reboot or the upgrade may failv           to execute properly!  0 7-22  Upgrading the OpenVMS VAX Operating System    e      E                            Upgrading the OpenVMS VAX Operating System E                                                   7.3 Upgrade Phase 1     K               Once the shutdown is complete, stop the system using the HALT K               button on the computer control panel, or the BREAK key on therL               console terminal if your system has no HALT button. Reboot theJ               system with the following command, replacing "ddcu" with theC               name of the disk drive that contains the system disk.u  !                   B/F0000000 ddcu/  H               The upgrade is set up to continue once the system reboots.  N               If, for some reason, the kernel V7.3 system should fail to boot,4               you can boot into SYSBOOT by entering:  !                   B/F0000001 ddcu   -           * Press RETURN to shut down system:   E           Once you have read the information displayed on the screen, -           press Return to begin the shutdown.a  "     7.3.11 Automatic System Reboot  D           If your system uses console media, it should automatically=           reboot from the SYSF directory when the shutdown isuE           complete. If you have a MicroVAX or if your system does not D           reboot from SYSF, halt the system and boot from the [SYSF]D           directory. For most MicroVAX and VAXstation computers, useE           the BOOT command in the following format and substitute thei2           device name of the system disk for ddcu:             >>> B/F0000000 ddcu        7.3.12 Manual System Reboott  C           If the system fails to boot, you can boot into SYSBOOT by.!           entering the following:a             >>> B/F0000001 ddcuf  E           For more information on booting your computer from the SYSF E           directory, refer to the upgrade and installation supplement             for your VAX computer.      E                       Upgrading the OpenVMS VAX Operating System 7-23            * Upgrading the OpenVMS VAX Operating System 7.3 Upgrade Phase 1      7.3.13  Verifying System Time   ?       When the system reboots, it displays a message similar tou       the following:  O         OpenVMS (TM) VAX Version V7.3 Major version id = 1 Minor version id = 0p  1           System time is: 13-NOV-2000 10:46:26.34R  K           Enter Yes to the next question to leave the system time unchanged ?                  (the system clock continues to run unaffected)U  +           Enter No to set a new system time   '           Enter ? to redisplay the timeD  #          * Is this correct? (Y/N/?)t  +       Enter your response and press Return.n   7.4  Upgrade Phase 2  ;       At the beginning of Phase 2, the procedure displays ar'       message similar to the following:e  9       Continuing with OpenVMS VAX V7.3 Upgrade Procedure.   8          Upgrade Phase 2         13-NOV-2000 10:46:31.86  ?       *********************************************************u?       %SYSTEM-W-TZGMT, your local timezone has defaulted to GMT 6       %SYSTEM-I-SETTZ, to set your local timezone use:  ,            $ @SYS$MANAGER:UTC$TIME_SETUP.COM  ?       *********************************************************e9       On MIN or UPGRADE system startup - CLUE is not run.a              .              .              .  #             13-NOV-2000 10:53:26.27o  9       You can ignore the time zone message. The UTC$TIME_ <       SETUP.COM procedure runs during the final phase of the       upgrade procedure.  =       During Phase 2, the upgrade procedure restores the restr=       of the library (C), optional (D), Help Message (E), anda;       OpenVMS Management Station software (F) save sets andc>       DECwindows support files if you elected to install them.  0 7-24  Upgrading the OpenVMS VAX Operating System u  o      E                            Upgrading the OpenVMS VAX Operating SystemmE                                                   7.4 Upgrade Phase 2e    >     7.4.1 Mounting Additional Magnetic Tape and Tape Cartridge           Volumes   E           If your distribution kit is contained on open reel magneticlA           tapes or TK50 CompacTape cartidges, you may be asked to B           mount the second volume of the kit. If you need to mount?           the second volume, your system will display a message #           similar to the following:m  >           Please mount volume 2 of the OpenVMS kit on <device>  @           where: <device> is the magnetic tape or tape cartridge           drive.  E           After you respond to the prompt, the system displays one of !           the following messages:.  B           o  For a 9-track open reel magnetic tape, the message is&              similar to the following:  P           * Is the volume labeled OVMS VAX V7.3 BIN MT9 2/2 ready to be mounted?  D           o  For a TK50 CompacTape cartridge, the message is similar              to the following:  P          * Is the volume labeled OVMS VAX V7.3 BIN TK50 2/2 ready to be mounted?  9           To respond to either message, do the following:m  6           1. Unload the volume currently in the drive.  D           2. Select the volume with the label that matches the label%              specified in the prompt.   6           3. Load the volume and make the drive ready.  (           4. Answer YES to the question.  A           For information on which save sets are located on whichb/           tape volumes, refer to Section 1.3.2.a       7.5 Upgrade Phase 3   ?           At the beginning of Phase 3, the procedure displays a +           message similar to the following:   =           Continuing with OpenVMS VAX V7.3 Upgrade Procedure.i  H                Upgrade Phase 3                   13-NOV-2000 11:05:47.14  E                       Upgrading the OpenVMS VAX Operating System 7-25n    u      * Upgrading the OpenVMS VAX Operating System 7.5 Upgrade Phase 3n    ?       During Phase 3, the upgrade procedure does the following:   :       1. Merges the OpenVMS VAX distributed files that are<          commonly edited by system managers with new OpenVMS          VAX files.o  ;       2. Merges all the miscellaneous user files in the oldtA          system directories into a new set of system directories,E5          temporarily called SYSF.SYSEXE, SYSF.SYSMGR,e           SYSF.SYSLIB, and so on.  @       3. Removes the directory entries for page, swap, dump, and9          authorization files from the old directory tree.h  9       4. Deletes all the remaining accounting data files,s>          operator logs, and all files in the SYSERR directory.  @       5. Merges the old and new versions of the following files:8          HELP, DCLTABLES, IMAGELIB.OLB, and STARLET.OLB.  >       6. Moves all remaining files from the old directory tree0          [VMS$COMMON] to the new directory tree.  5       7. Deletes the old directory tree [VMS$COMMON]..   7.6  Upgrade Phase 4  ;       At the beginning of Phase 4, the procedure displays a '       message similar to the following:X  9       Continuing with OpenVMS VAX V7.3 Upgrade Procedure.S  =            Upgrade Phase 4            13-NOV-2000 11:21:40.65S  ?       During Phase 4, the upgrade procedure does the following:S  7       1. Corrects back pointers for system directories.S         2. Shuts down the system.   A       3. Reboots the system, or requires that you manually rebooti          the system.      0 7-26  Upgrading the OpenVMS VAX Operating System t  t      E                            Upgrading the OpenVMS VAX Operating System E                                                   7.6 Upgrade Phase 4t         7.6.1 How to Proceed  @           If the procedure requires that you manually reboot theE           system from the original system root (usually SYS0), do theh           following:  C           1. If you are upgrading a VAX 8530, 8550, 8810, or 8820-NS(              computer, do the following:  C              a. Restore the original copies of DEFBOO and dddGEN tor6                 boot from the original root directory.  A              b. In the preupgrade procedure (Chapter 5), you madeeE                 copies of the boot command procedures, DEFBOO.SAV and B                 dddGEN.SAV. To restore the original names to theseD                 files, enter the following commands and press Return                 after each one:s                    >>> 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:i                >>> B ddcu   C              If the system fails to boot, you can boot into SYSBOOTd'              by entering the following:e                >>> B/1 ddcuo  C           For more information on booting your system, refer to the D           upgrade and installation supplement for your VAX computer.  C           When the system reboots, the procedure displays a message #           similar to the following:s  P          OpenVMS (TM) VAX Version V7.3 Major version id = 1 Minor version id = 0  @           After the system reboots, the procedure continues withE           upgrade Phase 5. Do not move the system disk to a differentwB           drive. The system disk must remain in the same drive for1           the procedure to continue with Phase 5.F  E                       Upgrading the OpenVMS VAX Operating System 7-27  r  X      * Upgrading the OpenVMS VAX Operating System 7.7 Upgrade Phase 5w     7.7  Upgrade Phase 5  ;       At the beginning of Phase 5, the procedure displays a '       message similar to the following:M  9       Continuing with OpenVMS VAX V7.3 Upgrade Procedure.,  =            Upgrade Phase 5            13-NOV-2000 11:36:36.95a  ?       During Phase 5, the upgrade procedure does the following:n  5       1. Deletes the temporary [SYSF] directory tree.t  @       2. Cleans up files used only during the upgrade procedure.  ?       3. Registers the OpenVMS VAX V7.3 operating system in then;          POLYCENTER Software Installation product database.p  ?       4. Installs DECnet Phase IV for OpenVMS VAX V7.3. Earliery>          in the procedure you were asked whether you wanted to@          install the DECnet Phase IV for OpenVMS VAX product. If9          you answered YES, the procedure now installs it.p  <       5. Converts all VAXVMSSYS.PAR parameter files found in,          system roots to Version 7.3 format.  =       6. Displays messages listing tasks that you can performi>          after the upgrade procedure is completed. These tasks$          are described in Chapter 8.   7.8  Upgrade Phase 6  ;       At the beginning of Phase 6, the procedure displays a '       message similar to the following:   <          Continuing with OpenVMS VAX V7.3 Upgrade Procedure.  ;               Upgrade Phase 6       13-NOV-2000 11:38:46.83   2          Configuring all devices on the system ...   7.8.1  Restoring System Files:  A       The procedure restores SYS$SPECIFIC and SYS$COMMON versions*@       of the following system files that were renamed with .COM_@       OLD_SPECIFIC and .DAT_OLD_SPECIFIC extensions during Phase       1:            SYSTARTUP_VMS.COM          SYCONFIG.COM*          SYPAGSWPFILES.COM  0 7-28  Upgrading the OpenVMS VAX Operating System a  p      E                            Upgrading the OpenVMS VAX Operating System E                                                   7.8 Upgrade Phase 6s                  SYSECURITY.COM.              SYSHUTDWN.COM              SYLOGIN.COM              LOGIN.COM              SYLOGICALS.COMr,              AGEN$NEW_SATELLITE_DEFAULTS.DAT'              AGEN$NEW_NODE_DEFAULTS.DAT(              LAT$SYSTARTUP.COM              TFF$STARTUP.COM  C           You might not have site-specific versions of all of these.C           files. The procedure displays a message listing each file            as it is restored.  B           You might receive any of the following network messages,           which can be ignored:h  :              %NCP-W-UNRCMP, Unrecognized component, Object  
           Or:   $              %NCP-I-SUCCESS, Success              Object = X$X04              %NML-I-RECDELET, Database entry deleted  (     7.8.2 Updating Time Zone Information  D           At this point in the upgrade, the procedure checks for theB           presence of time zone and time differential factor (TDF)D           files on your system. If it does not find one or the otherC           of these files, the procedure prompts you for informationo;           to be used for providing local time zone support.p  D           For local time zone support to work correctly, the upgradeD           procedure must set the time zone that accurately describesE           the location you want to be considered as your default timeeC           zone. Usually, this is the time zone in which your system @           is running. In addition, your system must be correctlyD           configured to use a valid OpenVMS time differential factor           (TDF).  @           The procedure displays a series of time zone menus andD           prompts you to make selections from those menus. The firstD           menu is the main time zone menu. Select the time zone thatC           best describes your location. If you do not select a timea9           zone, the default is Greenwich Mean Time (GMT).e  E                       Upgrading the OpenVMS VAX Operating System 7-29e c  d      * Upgrading the OpenVMS VAX Operating System 7.8 Upgrade Phase 6     ;       Some time zone choices cause an additional menu to beo?       displayed. This happens when the time zone you select has A       subcomponents. For example, if you choose the United States ?       (US) time zone from the main menu, a second menu displays5@       the specific time zones within the United States. You then?       select the menu item that best represents your local time        zone.p  <       The procedure then prompts you for the TDF. The TDF is=       the difference between your system time and Coordinatedu>       Universal Time (UTC), which is an international standard8       for measuring time of day. You can choose from the       following options:  ;       o  Exit the time zone procedure without setting a TDFo         o  Set a TDF  1       o  Display the TDF for your local time zoneR  A       For more information about TDF and local time zone support,y3       refer to the OpenVMS System Manager's Manual.a  4 7.8.3  Installing Compaq DECnet-Plus for OpenVMS VAX  A       Earlier in the procedure, you were asked whether you wanteds@       to install the Compaq DECnet-Plus for OpenVMS VAX product.9       If you answered Yes, the procedure now installs it.D  @       Note that if Compaq DECnet-Plus for OpenVMS VAX is already;       installed on your system and if the installed version =       is the same as or higher than the version supplied withy:       OpenVMS VAX Version 7.3, then Compaq DECnet-Plus for@       OpenVMS VAX is not reinstalled, and the procedure displays       the following message:  +           DECnet-Plus is already installed.o  :       If Compaq DECnet-Plus for OpenVMS VAX is not already@       installed on your system, the procedure displays a message>       similar to the following and prompts you for information@       it needs to install the Compaq DECnet-Plus for OpenVMS VAX       product:    0 7-30  Upgrading the OpenVMS VAX Operating System           E                            Upgrading the OpenVMS VAX Operating System E                                                   7.8 Upgrade Phase 6     0               DECnet-Plus will now be installed.  E               Media containing the DECnet-Plus kit must be available.   E               If you are installing OpenVMS from an InfoServer (DAD1)oH               or local CD-ROM, there is a DECnet-Plus kit on the CD-ROM.  C               If you are installing from a cartridge tape (TK50) ordG               from an open reel tape, you should have a DECnet-Plus kit 2               on cartridge tape or open reel tape.  E               An appropriate DECnet-Plus kit may also be available onrE               the Consolidated Distribution CD-ROM, or you may have aD'               separate DECnet-Plus kit.V  >               NOTE: You may choose any available media for theC               DECnet-Plus kit.  It is NOT NECESSARY to use the samea;               type of media that contained the OpenVMS kit.P  C           * Enter name of drive holding the DECnet-Plus kit: dkb200 1           * Is DKB200: ready to be mounted? [N] yo  2           The following product has been selected:G               DEC VAXVMS DECNET_OSI V7.3                Layered Productd  *           Configuration phase starting ...  O  You will be asked to choose options, if any, for each selected product and forbP  any products that may be installed to satisfy software dependency requirements.  F           DEC VAXVMS DECNET_OSI V7.3: DECnet-Plus V7.3 for OpenVMS VAX  P             Copyright (c) Compaq Computer Corporation 1999. All rights reserved.  )               Compaq Computer Corporationi  J               This product requires one of two PAKs: DVNETEND or DVNETRTG.  =               Do you want the defaults for all options? [YES]s  7               Do you want to review the options? [NO] yD  F               VAXVMS DECNET_OSI V7.3: DECnet-Plus V7.3 for OpenVMS VAX-               DEC VAXVMS VMS V7.3 [Installed] 6               VAX P.S.I. or P.S.I. Access software: NO.               VAX Wide Area Device Drivers: NO(               DECdns Server software: NO(               DECdts Server software: NO  5           Are you satisfied with these options? [YES]g  &           Execution phase starting ...  E                       Upgrading the OpenVMS VAX Operating System 7-31A 7  U      * Upgrading the OpenVMS VAX Operating System 7.8 Upgrade Phase 6     .       The following product will be installed:@           DEC VAXVMS DECNET_OSI V7.3             Layered Product  A       Portion done: 0%...10%...20%...30%...40%...80%...90%...100%   /       The following product has been installed:S@           DEC VAXVMS DECNET_OSI V7.3             Layered Product   7.8.4  Running AUTOGEN  A       Next, the procedure displays the following message and runse       AUTOGEN:  >       Running AUTOGEN to compute the new SYSTEM parameters ...  9       If AUTOGEN encounters any problems, it displays they       following message:  M       %AUTOGEN-W-REPORT, Warnings were detected by AUTOGEN. Please review thenJ               information given in the file SYS$SYSTEM:AGEN$PARAMS.REPORT.  8       If AUTOGEN displays this message, be sure to check?       AGEN$PARAMS.REPORT as one of your postupgrade tasks. Thisb'       task is described in Section 8.4.    7.8.5  Shutting Down the System,  ?       After AUTOGEN finishes, the procedure displays a sequence 1       of shutdown messages that begins like this:d  F       The system is shutting down to allow the system to boot with the>       generated site-specific parameters and installed images.  E       The system will automatically reboot after the shutdown and then       upgrade will be complete.t  =                SHUTDOWN -- Perform an Orderly System Shutdown_)                            on node VXPCSIu
          .
          .
          .  A       The system shuts down and will reboot automatically if your >       system is set up to do so. If the system does not reboot=       automatically, reboot it manually. For more informationS9       about booting your system, refer to the upgrade and.4       installation supplement for your VAX computer.  0 7-32  Upgrading the OpenVMS VAX Operating System           E                            Upgrading the OpenVMS VAX Operating SystemTE                                                   7.8 Upgrade Phase 6L         7.8.6 Booting Voting Nodes  B           If you are upgrading a standalone system, go to the next           step.   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 moreC           information about quorum values and voting members, refermC           to OpenVMS Cluster Systems.) All nodes that are booted atc0           this time will run AUTOGEN and reboot.       7.8.7 Executing STARTUPr  >           After the system reboots, the procedure displays the           following message:  E           ***********************************************************f             OpenVMS VAX V7.3  K           You have SUCCESSFULLY installed the OpenVMS VAX Operating System.e  C           The system is now executing the STARTUP procedure. Please E           wait for the completion of STARTUP before logging in to the            system.a  E           ***********************************************************n  C           Finally, the procedure displays informational messages as E           well as accounting information indicating that your OpenVMSh7           VAX operating system is running. For example:   L           %STDRV-I-STARTUP, OpenVMS startup begun at 13-NOV-2000 13:36:40.32              .              .              .P         %SET-I-INTSET, login interactive limit=64, current interactive value = 0  A            SYSTEM       job terminated at 13-NOV-2000 13:39:28.31   !           Accounting information:pM            Buffered I/O count:       1845   Peak working set size:        970 M            Direct I/O count:          677   Peak virtual size:           5165 M            Page faults:              8906   Mounted volumes:                0 M            Charged CPU time 0 00:00:53.34   Elapsed time        0 00:02:58.77o  E                       Upgrading the OpenVMS VAX Operating System 7-33o    h      * Upgrading the OpenVMS VAX Operating System 7.8 Upgrade Phase 6p    <       At this time, you can log in to the SYSTEM account (so=       you can perform postupgrade tasks), as described in thee       following sections.r  ? 7.8.8  Logging in to the SYSTEM Account by Means of a Charactern        Cell Terminal  >       Log in to a character cell terminal by entering the user:       name SYSTEM followed by the password. The display is       similar to the following:   &            Welcome to OpenVMS VAX V7.3         Username: SYSTEM       Password:F            .            .            ..            Welcome to OpenVMS VAX Version V7.3  >       (If you forget your password, follow the instructions in?       the OpenVMS System Manager's Manual, Volume 1: Essentialsi'       to perform an emergency startup.)   A 7.8.9  Logging in to the SYSTEM Account by Means of a Workstationt  ;       If you installed the DECwindows Motif for OpenVMS VAXa>       software on your workstation, do the following after the+       login window displays on your screen:   =       1. Enter the user name SYSTEM followed by the password.q          2. Click on the OK button.   7.9  What to Do Next  :       After you have successfully upgraded the OpenVMS VAX?       operating system and logged in to the SYSTEM account, youP?       must perform certain postupgrade tasks before you can usem<       the system. For complete information, go to Chapter 8.          0 7-34  Upgrading the OpenVMS VAX Operating System                         E                                                                     8rE     _________________________________________________________________e  E                      After Upgrading the OpenVMS VAX Operating System     A           After you upgrade the OpenVMS VAX operating system, youtD           need to perform several important tasks before you can useB           the system. These tasks, described in the order in which+           you perform them, are as follows:O  "           o  Verifying system time  .           o  Restoring the preferred node list  :           o  Replacing SYSUAF.DAT and VMS$AUDIT_SERVER.DAT  )           o  Examining AGEN$PARAMS.REPORT   .           o  Checking the size of system files  .           o  Examining your command procedures  #           o  Changing MODPARAMS.DAT   (           o  Updating your console media  +           o  Decompressing system librariest  D           o  Testing the system with UETP, the user environment test              package  6           o  Increasing free space on your system disk  !           o  Purging system filese  @           o  Restoring your modifications to the system password              dictionary   4           o  Customizing DECwindows support software  E           o  Preparing to run the OpenVMS Management Station softwareS  (           o  Installing layered products  '           o  Backing up the system disk              o  Running AUTOGEN  E                  After Upgrading the OpenVMS VAX Operating System 8-1b n  l      0 After Upgrading the OpenVMS VAX Operating System      -       o  Completing the postupgrade checklistr  ;       If you are an experienced system manager, you can user>       the checklist at the end of this chapter to complete the"       necessary postupgrade tasks.  >       If you are a less-experienced system manager, you should@       read the entire chapter and then use the checklist to make8       sure you have completed all the postupgrade tasks.   8.1  Verifying System Time  A       During the upgrade, the procedure displayed the system time.?       and gave you the opportunity to enter the correct time ife'       the displayed time was incorrect.D  =       Now that you have upgraded your system, verify that the ?       system time is correct by entering the following command:t         $ SHOW TIME   ,       The system displays the date and time.  @       If the time displayed by your system is not correct, reset=       it by entering the command SET TIME using the followingp
       format:   #       SET TIME=dd-mmm-yyyy:hh:mm:ss          For example:  %       $ SET TIME=12-JUN-2000:10:19:25y  & 8.2  Restoring the Preferred Node List  <       After the upgrade completes, the queuing system on the9       upgraded nodes is enabled, and you must restore theS0       preferred node list for the queue manager.  =       To restore the preferred node list, enter the followings       command from any node:  7       START/QUEUE/MANAGER/ON=(node1, node2 . . . noden)e  =       For node1, node2, and so forth, supply the names of theh?       nodes - separated by commas - that you want to restore to        the preferred node list.  5 8-2  After Upgrading the OpenVMS VAX Operating System  $  T      E                      After Upgrading the OpenVMS VAX Operating SystemcE                     8.3 Replacing SYSUAF.DAT and VMS$AUDIT_SERVER.DAT     5     8.3 Replacing SYSUAF.DAT and VMS$AUDIT_SERVER.DAT   @           If you permanently store the SYSUAF.DAT and VMS$AUDIT_A           SERVER.DAT files on the system disk, go to Section 8.4.d  C           If you do not permanently store SYSUAF.DAT and VMS$AUDIT_t?           SERVER.DAT on the system disk, you copied them to the.D           system disk before you did the upgrade. During the upgrade.           procedure, these files were updated.  B             ________________________ Note ________________________  ?             If you did a rolling upgrade, the shared version of '             SYSUAF.DAT was not updated.b  B             ______________________________________________________  D           To replace the updated files, copy the updated versions ofE           SYSUAF.DAT and VMS$AUDIT_SERVER.DAT from the system disk to.4           the directory where you usually keep them.  $     8.4 Examining AGEN$PARAMS.REPORT  9           When AUTOGEN runs, it writes informational and,i4           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.  A           To display AGEN$PARAMS.REPORT on your screen, enter they-           following command and press Return:m  .           $ 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:   (******************eN %AUTOGEN-W-DSKSPC, The disk on which DISK$OpenVMS072:[SYS0.SYSEXE]PAGEFILE.SYS@ resides would be over 95% full if it were modified to hold 20000 blocks.  ******************)S  E           For more information about modifying the sizes of the page,G/           swap, or dump files, see Section 8.5.   E                  After Upgrading the OpenVMS VAX Operating System 8-3  l  n      0 After Upgrading the OpenVMS VAX Operating System% 8.5 Checking the Size of System Files     & 8.5  Checking the Size of System Files  ?       AUTOGEN sets the following files at sizes appropriate for        your system:            [SYSEXE]SYSDUMP.DMP          [SYSEXE]PAGEFILE.SYSc          [SYSEXE]SWAPFILE.SYSg  >       For special workloads or configurations, you can specify?       different sizes for these files. Check the sizes of thesetA       files to be sure they meet your needs. Log in to the SYSTEM .       account and enter the following command:         $ @SYS$UPDATE:SWAPFILESt  A       For more information, refer to the OpenVMS System Manager'st#       Manual, Volume 1: Essentials.2  & 8.6  Examining Your Command Procedures  ?       The upgrade procedure places a new version of WELCOME.TXTi>       on your system disk. If your system uses a site-specific>       version of this file, you must modify the new version of!       the file with your changes.   ?       The upgrade procedure restores your site-specific version @       of the following files with *.COM_OLD_SPECIFIC extensions:            SYSTARTUP_VMS.COM          SYCONFIG.COM           SYPAGSWPFILES.COM          SYSECURITY.COM:          SYSHUTDWN.COM          SYLOGIN.COM          LOGIN.COM          SYLOGICALS.COMA          LAT$SYSTARTUP.COM          TFF$STARTUP.COM  >       The upgrade procedure provides new templates for some ofA       these files with the .TEMPLATE extension. The new templatese=       can include features that are not in your site-specific A       files. Check the templates against your site-specific files '       and edit your files as necessary.   5 8-4  After Upgrading the OpenVMS VAX Operating System     a      E                      After Upgrading the OpenVMS VAX Operating SystemoE                                 8.6 Examining Your Command ProceduresT    D           Remember, you do not need a START/QUEUE/MANAGER command inC           your startup file because the queue manager automaticallys-           starts up when you boot the system.n       8.7 Changing MODPARAMS.DAT  ?           Review the file SYS$SYSTEM:MODPARAMS.DAT. The upgrade ?           procedure created a new version of this file. The old C           version is named SYS$SYSTEM:MODPARAMS.DAT_OLD. Modify thet2           new file, if necessary, for your system.  @           If you are upgrading a VAXcluster, you must update theB           MODPARAMS.DAT file for each VAX computer that boots from@           the system disk. Make sure the value for the EXPECTED_A           VOTES parameter is correct. The value is the sum of all B           VOTES in the cluster. For example, if there are five VAXD           computers in the cluster, and each has one VOTE, the value@           is five. As you reboot each VAX computer, AUTOGEN runs?           automatically. The cluster forms when you have booted 4           enough computers to attain cluster quorum.  E           For more information, refer to the OpenVMS System Manager's D           Manual, Volume 2: Tuning, Monitoring, and Complex Systems.  #     8.8 Updating Your Console MediaM  @           If your computer does not use console media, skip this)           section and go to Section 8.10.h  @           If your computer uses console media, you must copy theC           Version 7.3 VMB.EXE onto your system's console media. TheeD           procedure differs depending on the VAX series computer youC           have. Follow the instructions in the section that appliesA           to your VAX computer.   <     8.9 VAX 8530, 8550, 8810 (8700), 8820-N (8800) Computers  B           If you upgraded a VAX 8530, 8550, 8810 (8700), or 8820-N,           (8800) computer, do the following:  ?           1. Insert a blank RX50 diskette in one of the consolesA              diskette drives. The console refers to the upper (or ?              left-hand) diskette drive as DZ1 while the OpenVMS C              VAX operating system refers to it as CSA1. The console C              refers to the lower (or right-hand) drive as DZ2 whileoC              the OpenVMS VAX operating system refers to it as CSA2.h  E                  After Upgrading the OpenVMS VAX Operating System 8-5  d  s      0 After Upgrading the OpenVMS VAX Operating System8 8.9 VAX 8530, 8550, 8810 (8700), 8820-N (8800) Computers    ;       2. Make sure the diskette drives are connected to then2          OpenVMS VAX operating system, as follows:            $ SHOW DEVICE CSAB          Device                  Device           Error     VolumeB           Name                   Status           Count      Label7          CSA0:         (SYSTEM)  Online               0l7          CSA1:         (SYSTEM)  Online               0e7          CSA2:         (SYSTEM)  Online               0   ?          If the drives are not connected, the following messageg          is displayed:  6          %SYSTEM-W-NOSUCHDEV, no such device available  :          If this message is displayed, enter the following.          commands (you need CMKRNL privilege):             $ RUN SYS$SYSTEM:SYSGEN           SYSGEN> CONNECT CONSOLE          SYSGEN> EXITt  A       3. To initialize the disk, enter a command in the followingh          format:  ;          $ INITIALIZE/STRUCTURE=1 device-name: volume-labelm  A          Substitute CSA1 or CSA2 for device-name. Substitute a 1-n<          to 12-character name for volume-label. For example:  2          $ INITIALIZE/STRUCTURE=1 CSA1: V61CONSOLE  <       4. Enter the following commands to mount the diskette,:          create the required directories, and copy the new=          VMB.EXE to the diskette. Substitute CSA1 or CSA2 for           device-name.s  )          $ MOUNT/OVERRIDE=ID device-name:t2          $ CREATE/DIRECTORY device-name:[TRANSFER]9          $ COPY SYS$SYSTEM:VMB.EXE device-name:[TRANSFER]e  @       5. Once you have copied all the files, enter the followingA          command to dismount the diskette. (Leave the diskette inw=          the drive.) Substitute CSA1 or CSA2 for device-name.r             $ DISMOUNT device-name:  5 8-6  After Upgrading the OpenVMS VAX Operating Systemi t  O      E                      After Upgrading the OpenVMS VAX Operating SystemdE              8.9 VAX 8530, 8550, 8810 (8700), 8820-N (8800) ComputersS    E           6. To enter console mode, press Ctrl/P. To exit the consoleI2              program, enter the following command:                >>> EXIT   B           7. Open the diskette drive door, pause for a moment, and:              close it. The red indicator light will flash.  C           8. To copy VMB.EXE from the diskette to the console fixed 5              disk drive, enter the following command:   9              $ COPY DZu:[TRANSFER]VMB.EXE   LB0:[CONSOLE]   +              Substitute DZ1 or DZ2 for DZu.   B              The fixed drive in the console is known by two names,=              DW2 and LB0. Most console files are stored using @              the name LB0. If the system displays a message thatC              describes a protection violation on the output device,kA              copy the files using the device name DW2 rather than.              LB0.R  A           9. When you have finished copying the files, remove thed%              diskette from the drive.s  B          10. Restart the console program by entering the following)              command and pressing Return:l                $ RUN CONTROL  E          11. Return to the operating system by entering the following )              command and pressing Return:   %              >>> SET TERMINAL PROGRAM.  C     8.9.1 VAX-11/730, 750, 780, 785 and VAX 8200, 8250, 8300, 8350,l           8600, 8650 Computers  C           If you upgraded a VAX-11/730, 750, 780, 785 and VAX 8200,T>           8250, 8300, 8350, 8600, or 8650 computer, follow the'           instructions in this section.l  +           The procedure does the following:*  ?           o  Checks to see if you have enough space for the newg              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 computersA  E                  After Upgrading the OpenVMS VAX Operating System 8-7k           0 After Upgrading the OpenVMS VAX Operating System8 8.9 VAX 8530, 8550, 8810 (8700), 8820-N (8800) Computers    ?       To update the console media, use the following procedure:[  &       1. Log in to the SYSTEM account.  A       2. Enter the following commands to check if there is enougho;          space for the new VMB.EXE. You need 120 blocks. Ifu;          you are updating a VAX-11/730 system, use CSA2 for >          device-name; if you are updating one of the other VAX-          computers, use CSA1 for device-name.O             $ RUN SYS$SYSTEM:SYSGEN           SYSGEN> CONNECT CONSOLE          SYSGEN> EXIT 1          $ EXCHANGE DIRECTORY device-name:VMB.EXEn  E          Directory of RT-11 volume TINES$CSA1:      13-NOV-2000 18:40s  (            VMB.EXE      80   13-NOV-2000  G          Total of 1 file, 80 blocks.  Free space 43 blocks, largest 23.   =          If the size of the current VMB, plus the free space, <          does not equal at least 120 blocks, delete unneeded7          files on the console until you have 120 blocks A          available. In the above example, the size of the currentU<          VMB.EXE (80 blocks) plus the free space (43 blocks)?          equals 123 blocks, so files do not have to be deleted.C  6       3. Enter the following command and press Return:  )          $ @SYS$UPDATE:UPDATE_CONSOLE.COMA  @       4. If you are updating the console media for a VAX 8600 or>          VAX 8650 computer, the new VMB.EXE is copied onto the          console media.   =          If you are updating the console media for one of theg=          other VAX computers, the procedure uses the EXCHANGE ?          procedure to copy the contents of the existing console @          media, merge the new files onto the copy of the console>          media, and create a new version of the console media.>          When the computer is ready to create the new version,=          it displays a message asking you to insert a scratchmA          tape cassette or diskette. Take out the original consoleY$          media and insert a new one.  5 8-8  After Upgrading the OpenVMS VAX Operating Systemh l         E                      After Upgrading the OpenVMS VAX Operating System E              8.9 VAX 8530, 8550, 8810 (8700), 8820-N (8800) Computersa         8.9.2 VAX 9000 Computers  C           VAX 9000 computers use a special version of VMB.EXE namedm@           VMB9AQ.EXE. The upgrade procedure automatically copies>           a new version of this file to the console hard disk.D           However, if for some reason you need to update the consoleA           hard disk, use the UPDATE_CONSOLE.COM command procedurevC           described for the VAX-11/730, 750, 780, 785 and VAX 8200,sE           8250, 8300, 8350, 8600, and 8650 computers. The device name 5           for the VAX 9000 console hard disk is CSA1.   +     8.10 Decompressing the System LibrariesS  =           Decompressing the system libraries gives the systemg@           faster access to the libraries. You can decompress allD           the system libraries or just some of them. Table 8-1 givesC           the approximate number of blocks consumed by each libraryu           after decompression.  E           Table_8-1_Sizes_of_Decompressed_System_Libraries___________e  E           Library___________Blocks______Library___________Blocks_____   >           HELPLIB.HLB       9108        EDFHLP.HLB         102  >           STARLET.OLB       8442        TPUHELP.HLB       1038  >           VAXCCURSE.OLB      102        ACLEDT.HLB         102  >           VAXCRTL.OLB        477        INSTALHLP.HLB      102  >           VAXCRTLG.OLB       102        LATCP$HELP.HLB     240  >           DECCCURSE.OLB      102        MNRHELP.HLB        102  >           DECCRTL.OLB        183        PATCHHELP.HLB      102  >           DECCRTLG.OLB       102        PHONEHELP.HLB      102  >           ERFLIB.TLB         105        SDA.HLB            111  >           STARLETSD.TLB     4800        SHWCLHELP.HLB      150  >           MAILHELP.HLB       273        SYSGEN.HLB         393  >           EDTHELP.HLB        231        TECO.HLB           102  >           DBG$UIHELP.HLB     408        UAFHELP.HLB        372  >           DBG$HELP.HLB      1986        EVE$HELP.HLB      1197  >           EXCHNGHLP.HLB      117        EVE$KEYHELP.HLB    147  E                                              (continued on next page)   E                  After Upgrading the OpenVMS VAX Operating System 8-9  a         0 After Upgrading the OpenVMS VAX Operating System' 8.10 Decompressing the System LibrariesA    A       Table_8-1_(Cont.)__Sizes_of_Decompressed_System_Libraries__Y  A       Library___________Blocks______Library___________Blocks_____e  :       NCPHELP.HLB        537        STARLET.MLB       2502  :       ANLRMSHLP.HLB      102        LIB.MLB           2229  A       DISKQUOTA.HLB______102_____________________________________y  @       The additional amount of disk space required to decompress>       all system libraries is about 13,500 blocks. To find out?       how much disk space you have, enter the following command        and press Return:I  !       $ SHOW DEVICE SYS$SYSDEVICEl  # 8.10.1  How to Decompress Librarieso  8       You execute the LIBDECOMP.COM command procedure to<       decompress the system libraries. To run LIBDECOMP, log@       in to the SYSTEM account, enter the following command, and       press Return:e  !       $ @SYS$UPDATE:LIBDECOMP.COMr  -       The following information is displayed:E  <                        OpenVMS Library Decompression Utility  L           1  HELPLIB.HLB          14  NCPHELP.HLB          27  PHONEHELP.HLBF           2  STARLET.OLB          15  SDA.HLB              28  LIB.MLBJ           3  ACLEDT.HLB           16  SHWCLHELP.HLB        29  STARLET.MLBL           4  ANLRMSHLP.HLB        17  SYSGEN.HLB           30  STARLETSD.TLBP           5  DBG$HELP.HLB         18  ANALAUDIT$HELP.HLB   31  SYS$STARLET_C.TLBI           6  DBG$UIHELP.HLB       19  SYSMANHELP.HLB       32  ERFLIB.TLB L           7  DISKQUOTA.HLB        20  TFF$TFUHELP.HLB      33  SYS$LIB_C.TLBL           8  EDFHLP.HLB           21  EXCHNGHLP.HLB        34  VAXCCURSE.OLBJ           9  INSTALHLP.HLB        22  TPUHELP.HLB          35  VAXCRTL.OLBK          10  LATCP$HELP.HLB       23  EVE$HELP.HLB         36  VAXCRTLD.OLB K          11  MAILHELP.HLB         24  EVE$KEYHELP.HLB      37  VAXCRTLT.OLB K          12  MNRHELP.HLB          25  UAFHELP.HLB          38  IMAGELIB.OLBE.          13  EDTHELP.HLB          26  TECO.HLB  5               39  VMS$VOLATILE_PRIVATE_INTERFACES.OLB   3                 A  ALL libraries to be decompressed &                 E  EXIT this procedure  6 8-10  After Upgrading the OpenVMS VAX Operating System n         E                      After Upgrading the OpenVMS VAX Operating System E                               8.10 Decompressing the System Libraries     E           * Enter letter or number(s) of libraries to be decompressedc5             (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 orLA           as a batch job. If you use either of these methods, youl@           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.MLB @           libraries as a batch job, enter the following command:  ?           $ SUBMIT/NOTIFY/PARAMETERS=(VAXCRTL, DISKQUOTA, LIB)-e!           _$ SYS$UPDATE:LIBDECOMP   E           To decompress these same libraries interactively, enter thet           following command:  7           $ @SYS$UPDATE:LIBDECOMP VAXCRTL DISKQUOTA LIBt  C           Note that, when you type the command for a batch job, you E           separate the library names with commas and enclose the list E           within parentheses. You do not use commas or parentheses onm'           the interactive command line.   %     8.11 Testing the System with UETP0  @           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 postupgradeR@           procedure, you should run UETP to verify your upgrade.  ?           Note that UETP needs at least 1200 free blocks on the @           system disk and is available only if you installed the@           optional save set VMS072.D. If you did not install the?           optional save set, you can add the UETP files to your =           system using VMSTAILOR. For information about using $           VMSTAILOR, see Chapter 10.  C           For complete information about UETP, refer to the OpenVMSoD           System Manager's Manual, Volume 2: Tuning, Monitoring, and           Complex Systems.  E                 After Upgrading the OpenVMS VAX Operating System 8-11s           0 After Upgrading the OpenVMS VAX Operating System- 8.12 Increasing Free Space on the System DiskE    . 8.12  Increasing Free Space on the System Disk  ?       This section describes how to increase the amount of freeh;       space on your system disk. You can gain free space by >       removing optional OpenVMS VAX files that you do not need=       from the system disk or by purging old versions of some        system files.   3 8.12.1  Running the ANALYZE /DISK_STRUCTURE Utilityd  >       Certain disk structure inconsistencies may be introduced<       during the OpenVMS VAX upgrade operation. To check for9       these inconsistencies, enter the following command:   .       $ ANALYZE /DISK_STRUCTURE SYS$SYSDEVICE:  ;       This command produces output in the following format:a  )                   Error opening QUOTA.SYSn                   No such file2                   File (2849,7,1) DCLTABLES.EXE;31+                           marked for deleteO+                   File (4270,3,1) SYS.EXE;28+                           marked for delete <                   File (5485,9,1) SYS$NETWORK_SERVICES.EXE;1+                           marked for delete   =       If quotas are not in use on the system disk, ignore the @       "No such file" message for QUOTA.SYS. Most inconsistenciesA       (including "marked for delete") can be repaired by entering        the following command:  6       $ ANALYZE /DISK_STRUCTURE /REPAIR SYS$SYSDEVICE:  ' 8.12.2  Using VMSTAILOR and DECW$TAILORs  ?       To remove files you do not need from the system disk, usen?       VMSTAILOR. For example, if you are not running DECnet for =       OpenVMS, you do not need the network support files. ForeA       complete information about using VMSTAILOR to remove files,s       see Chapter 10.   A       If you are running DECwindows Motif, use DECW$TAILOR to addeA       or remove DECwindows base support, workstation support, andu       fonts.  6 8-12  After Upgrading the OpenVMS VAX Operating System _  e      E                      After Upgrading the OpenVMS VAX Operating System_E                         8.12 Increasing Free Space on the System Disk     B             ________________________ Note ________________________  :             Files installed on alternate devices cannot be             tailored.   B             ______________________________________________________       8.12.3 Purging System Files   C           In most cases, you can purge the following OpenVMS system2B           files to free space on your system disk. However, beforeD           you purge any of these files, read Appendix F to make sureA           you do not purge a file version you might want to keep.   !           SYS$SYSTEM:SHUTDOWN.COMT            SYS$SYSTEM:STARTUP.COM#           SYS$LIBRARY:ENCRYPSHR.EXEP           SYS$LIBRARY:*RTL*.EXE            SYS$LIBRARY:*SHR.EXE            SYS$MANAGER:EDTINI.EDT#           SYS$MANAGER:DBLSTRTUP.COMB            SYS$MANAGER:*.TEMPLATE#           SYS$EXAMPLES:XADRIVER.MAR9            SYS$LIBRARY:CDDSHR.EXE&           SYS$LIBRARY:EPC$FACILITY.TLB!           SYS$MESSAGE:EPC$MSG.EXE %           SYS$STARTUP:VMS$LAYERED.DATo  B           To purge a file, enter the PURGE command followed by the*           file specification. For example:  )           $ PURGE SYS$SYSTEM:SHUTDOWN.COMm  2     8.13 Restoring Your System Password Dictionary  <           The OpenVMS VAX operating system screens potentialC           passwords for acceptability. The DCL command SET PASSWORD <           takes the user's proposed password, converts it toA           lowercase (if necessary), and compares it to entries in C           a system dictionary. If the proposed password is found in B           the dictionary, it is rejected as a valid user password,A           and the user must suggest another. Many system managersuC           modify the system password dictionary to include words of %           significance to their site.D  E                 After Upgrading the OpenVMS VAX Operating System 8-13I C  .      0 After Upgrading the OpenVMS VAX Operating System. 8.13 Restoring Your System Password Dictionary    =       During the upgrade, the procedure replaces the existingn;       system password dictionary with a new one. If you hadn<       modified the dictionary and want to restore your local8       additions, you must merge the file containing your)       additions with the new system file.E  ;       To add your site-specific passwords to the new system =       password dictionary, enable SYSPRV and merge your localL@       additions by entering the following commands, where LOCAL_=       PASSWORD_DICTIONARY.DATA is the file that contains your.       additions:  $       $ SET PROCESS/PRIVILEGE=SYSPRV:       $ CONVERT/MERGE/PAD LOCAL_PASSWORD_DICTIONARY.DATA -1       _$ SYS$LIBRARY:VMS$PASSWORD_DICTIONARY.DATA   - 8.14  Customizing DECwindows Support Software   >       If you have installed DECwindows support software, there:       are several steps that you can take to customize the>       DECwindows environment. Depending on your configuration,;       DECwindows customization tasks include the following:   '       o  Customizing the server startupL  9       o  Using the Transmission Control Protocol/Internet 4          Protocol (TCP/IP) as a DECwindows transport  9       o  Using transports for DECwindows other than thoseT          supplied by Compaq   ?       Go to Chapter 9 for complete instructions for customizings'       your DECwindows support software.p  A       After you complete the tasks described in Chapter 9, returnU@       to this chapter to continue with the remaining postupgrade       tasks.  5 8.15  Preparing to Use the OpenVMS Management Station   ;       The OpenVMS Management Station client/server software =       provides OpenVMS system management capabilities through >       a client application on a personal computer (PC) running       Microsoft Windows.  6 8-14  After Upgrading the OpenVMS VAX Operating System p  i      E                      After Upgrading the OpenVMS VAX Operating SystemiE                  8.15 Preparing to Use the OpenVMS Management Stationm    <           When you upgraded your OpenVMS system, the OpenVMS<           Management Station server files were automaticallyC           installed on your OpenVMS system disk. However, to obtainaD           complete support, you had to select the OpenVMS ManagementB           Station client software files during the OpenVMS upgrade>           procedure. Those files are required for creating the?           installation media that you use to install the clientS           software on your PC.  A           Appendix G provides complete instructions for preparing <           your OpenVMS system and your PC to run the OpenVMS&           Management Station software.  B             ________________________ Note ________________________  A             If you did not select the optional OpenVMS Management A             Station client software files during the installationr@             or upgrade, you must add these files to your OpenVMS=             system disk before you follow the instructions inn@             Appendix G. Use the OpenVMS Version 7.3 distribution=             media and VMSTAILOR to add the OpenVMS Management @             Station files to your system. (For information about-             using VMSTAILOR, see Chapter 10.)a  B             ______________________________________________________  $     8.16 Installing Layered Products  D           Back up your system disk and then use either the VMSINSTALC           command procedure or the POLYCENTER Software Installationl@           utility to install layered products on your system. IfA           the system contained Compaq TCP/IP Services for OpenVMSe=           previous to the upgrade, you must reinstall it now.o  =           For additional information about installing layered <           products, see the OpenVMS System Manager's Manual.  #     8.17 Backing Up the System DiskV  D           Compaq recommends that you protect your work by performing#           the following operations:A  E           o  Use SYS$UPDATE:CONSCOPY.COM to back up the console mediap              (if applicable).   C           o  Make a standalone BACKUP kit on removable media and onS              the system disk.n  E                 After Upgrading the OpenVMS VAX Operating System 8-15m s  Y      0 After Upgrading the OpenVMS VAX Operating System 8.17 Backing Up the System Diskd    =          If your console media is a TU58 tape cartridge or an ?          RX01 diskette, use the standalone BACKUP copy you made ;          before you began the upgrade. (See Section 5.4.2.)b  !       o  Back up the system disk.S  <       For complete information about these operations, refer=       to the upgrade and installation supplement for your VAXT       computer.:   8.18  Running AUTOGENo  =       When you upgraded the OpenVMS VAX operating system, the <       procedure executed AUTOGEN to set the values of system9       parameters and the sizes of the page and swap files )       according to the system's workload.   >       In many cases, AUTOGEN can improve system performance byA       using dynamic feedback information from the running system.E>       As a postinstallation task, you should run AUTOGEN againA       using the feedback mechanism to make further adjustments tof       system parameters.  ?       When AUTOGEN runs after an upgrade, it uses the parametere=       values in SYS$SYSTEM:MODPARAMS.DAT. Note that hardcoded >       values in MODPARAMS.DAT affect AUTOGEN's calculations of@       the feedback parameters. For AUTOGEN to properly calculate@       minimum values, you should replace the hardcoded values in?       MODPARAMS.DAT with MIN_ values. The MIN_ prefix specifiesn:       the minimum value to which a parameter can be set by       AUTOGEN.  :       If you are not satisfied with the parameter settings@       calculated by AUTOGEN, you can modify the parameter valuesA       by editing MODPARAMS.DAT as explained in the OpenVMS System A       Manager's Manual, Volume 2: Tuning, Monitoring, and Complex        Systems.  ?       After you have upgraded the operating system, run AUTOGEN *       again using the following procedure:  =       1. After 24 hours of operation, run AUTOGEN in feedback $          mode and reboot the system.    6 8-16  After Upgrading the OpenVMS VAX Operating System a  r      E                      After Upgrading the OpenVMS VAX Operating System E                                                  8.18 Running AUTOGENr    B           2. Run AUTOGEN in this same way, again, two working days              later.   B             ________________________ Note ________________________  B             For the VAX 9000 computer, AUTOGEN's initial parameter>             calculations are conservative. To obtain parameter?             values that match your system workload, you can run$@             AUTOGEN in feedback mode a number of times. For more>             information, refer to the upgrade and installation2             supplement for your VAX 9000 computer.  B             ______________________________________________________  B           3. Compaq 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.G  C           For information about using AUTOGEN, refer to the OpenVMSiD           System Manager's Manual, Volume 2: Tuning, Monitoring, and           Complex Systems.       8.19 Postupgrade Checklist  B           Use the following checklist to make sure you perform all*           the necessary postupgrade tasks.  >           <  Verify the system time (described in Section 8.1)  B           <  Restore the preferred node list for the queue manager'              (described in Section 8.2)n  C           <  Replace SYSUAF.DAT and VMS$AUDIT_SERVER.DAT (describedy              in Section 8.3)  6           <  Examine AUTOGEN output stored in the file:              AGEN$PARAMS.REPORT (described in Section 8.4)  B           <  Examine the command procedure templates supplied with?              OpenVMS VAX Version 7.3 (described in Section 8.6)   =           <  Examine MODPARAMS.DAT (described in Section 8.7)   A           <  Update your console media (described in Section 8.8)i  @           <  Decompress the system libraries using LIBDECOMP.COM(              (described in Section 8.10)  E                 After Upgrading the OpenVMS VAX Operating System 8-17i    s      0 After Upgrading the OpenVMS VAX Operating System 8.19 Postupgrade Checklist    A       <  Run UETP (the user environment test package) to test the >          system (described in OpenVMS System Manager's Manual,;          Volume 2: Tuning, Monitoring, and Complex Systems)   <       <  Remove unwanted files and check the sizes of system*          files (described in Section 8.12)  <       <  Restore your local additions to the system password/          dictionary (described in Section 8.13)e  <       <  Customize your DECwindows environment (described in          Section 8.14)  4       <  Build a standalone BACKUP kit (described in          Section 8.17)  >       <  Back up the console media (described in Section 8.17)  =       <  Install layered products (described in Section 8.16)   >       <  Back up the system disk (described in the upgrade and3          installation supplement for your computer)s  =       <  Run AUTOGEN and reboot the system after the first 24i7          hours of operation (described in Section 8.18)a                                        6 8-18  After Upgrading the OpenVMS VAX Operating System o  n                    E                                                                     9nE     _________________________________________________________________s  E                               Customizing DECwindows Support Software     A           This chapter describes how you can customize DECwindowsiA           support software. The DECwindows components provided on @           the OpenVMS VAX kit supply DECwindows base support andC           workstation support files only. If you have not installedeD           either of these DECwindows components on your system, skip           this chapter.   C           Depending on your configuration, DECwindows customization &           tasks include the following:  +           o  Customizing the server startup   =           o  Using the Transmission Control Protocol/Internett8              Protocol (TCP/IP) as a DECwindows transport  >           o  Using transports with DECwindows other than those              supplied by Compaqa  >           Note that the OpenVMS VAX operating system no longerE           includes the VMS DECwindows product. To get full DECwindowsV@           support, you must also install the separate DECwindowsD           Motif for OpenVMS VAX layered product, which supports both)           the Motif and XUI environments.t  &     9.1 Customizing the Server Startup  E           By default, the DECwindows server no longer logs successful ;           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.       E                           Customizing DECwindows Support Software 9-1s l         ' Customizing DECwindows Support Softwaree" 9.1 Customizing the Server Startup     9.1.1  Assumptions  <       The startup command procedures automatically determine<       most of the configuration variables for the DECwindows?       display server. However, there are items that the command =       procedures cannot determine, so they make the following        assumptions:  =       o  The startup procedures normally assume that you haveh;          a 75 dots/inch monitor (such as a VR260 or VR290). A          However, if you are installing on a VAXstation 4000, theo@          startup procedures assume that you have a 100 dots/inch          monitor.:  @       o  If you have a GPX, SPX, or LCG workstation, the startup9          procedures assume that you have a color monitor.v  =       o  The startup procedures normally assume that you have ?          a North American keyboard layout (you have an LK201-AAY=          or an LK201-LA keyboard). If you are installing on aB@          VAXstation 4000, the startup procedures assume that you#          have an LK401-AA keyboard.   ?       o  The startup procedures assume that the server will useb3          only DECnet software and local transports.   , 9.1.2  How to Override Incorrect Assumptions  A       If any of these assumptions is incorrect, you must overridea       them as follows:  A       1. Make a copy of the file SYS$MANAGER:DECW$PRIVATE_SERVER_ >          SETUP.TEMPLATE and rename it to a .COM file type. The?          comments in this file show how to customize individual =          workstations by adding a section of DCL commands foro?          each workstation. You can also add DCL commands to thec<          common section of the server startup file. By doingA          this, you ensure that the customizations you make affect ;          all workstations that use the server startup file.m  A       2. If your screen supports 100 dots/inch, add the following           line:  '          $ DECW$SERVER_DENSITY == "100"e  ?          Add this line to the section for each workstation that =          has a 100 dots/inch monitor, or add it to the commonf>          section for all workstations (if all the workstations&          have 100 dots/inch monitors).  , 9-2  Customizing DECwindows Support Software i  M      E                               Customizing DECwindows Support SoftwarerE                                    9.1 Customizing the Server Startupw    E           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"  D           4. The section for any workstation with color graphics andD              a monochrome screen should contain the following lines:  $              $ DECW$COLOR == "FALSE"&              $ DECW$BITONAL == "FALSE"  ?           5. To override the default keyboard layout, determinefA              the correct name from the model number of your LK201 "              keyboard, as follows:  C              a. Turn the keyboard upside down, and look for a label A                 that specifies the model number. The model numbers:                 should be in a format similar to LK201-xx.  B                 If the model number is listed as LK201 without anyE                 additional characters, the information you need is on E                 another part of the label. Look for a number that hasa%                 the following format:o                     nn-nnnnn-xx.  A              b. Use the xx part of this number to choose a keymapr@                 name from Table 9-1. The table is arranged based=                 on the dialect that each keyboard is designed_A                 for. Choose the keymap ending in _DP for the data C                 processing keyboard layout, or the keymap ending ine.                 _TW for the typewriter layout.                          E                           Customizing DECwindows Support Software 9-3  u  s      ' Customizing DECwindows Support Softwarey" 9.1 Customizing the Server Startup    A Table_9-1__DECwindows_Keymap_____________________________________e  A Dialect_________Model_______________DECwindows_Keymap_Name_______p  > Austrian/German LK201-              AUSTRIAN_GERMAN_LK201LG_DP                 (AG,LG,BG,MG)s  >                                     AUSTRIAN_GERMAN_LK201LG_TW  >                 LK201-(NG,PG)       AUSTRIAN_GERMAN_LK201NG_DP  >                                     AUSTRIAN_GERMAN_LK201NG_TW  >                 LK401-(AG)          AUSTRIAN_GERMAN_LK401AG_TW  = Belgian/French  LK201-              BELGIAN_FRENCH_LK201LP_DPd                 (AP,LP,BP,MP)   =                                     BELGIAN_FRENCH_LK201LP_TW   = Belgian/French  LK401-(AP)          BELGIAN_FRENCH_LK401AP_DP   =                                     BELGIAN_FRENCH_LK401AP_TW   6 British         LK201-              BRITISH_LK201LE_DP                 (AE,LE,BE,ME)r  6                                     BRITISH_LK201LE_TW  6 British         LK401-(AA,PA)       BRITISH_LK401AA_DP  6                                     BRITISH_LK401AA_TW  > Canadian/French LK201-              CANADIAN_FRENCH_LK201LC_DP                 (AC,LC,BC,MC)U  >                                     CANADIAN_FRENCH_LK201LC_TW  > Canadian/French LK401-              CANADIAN_FRENCH_LK401AC_DP                 (AC,LC,BC,MC)m  >                                     CANADIAN_FRENCH_LK401AC_TW  1 Czech           LK401-(BV)          CZECH_LK401AV1  5 Danish          LK201-              DANISH_LK201LD_DP                  (AD,LD,BD,MD)d  5                                     DANISH_LK201LD_TWw  5                 LK201-(ED,RD,FD)    DANISH_LK201RD_DP   5                                     DANISH_LK201RD_TW   5 Danish          LK401-              DANISH_LK401AD_DPa                 (AD,LD,BD,MD)   5                                     DANISH_LK401AD_TW.  B                                           (continued on next page)  , 9-4  Customizing DECwindows Support Software r         E                               Customizing DECwindows Support SoftwareuE                                    9.1 Customizing the Server Startup     E     Table_9-1_(Cont.)_DECwindows_Keymap______________________________n  E     Dialect_________Model_______________DECwindows_Keymap_Name_______   8     Dutch           LK201-              DUTCH_LK201LH_DP!                     (AH,LH,BH,MH)   8                                         DUTCH_LK201LH_TW  5                     LK201-(NH,PH)       DUTCH_LK201NHn  5                     LK401-(NH,PH)       DUTCH_LK401AHE  :     Finnish         LK201-              FINNISH_LK201LF_DP!                     (AF,LF,BF,MF)d  :                                         FINNISH_LK201LF_TW  :                     LK201-(NX,PX)       FINNISH_LK201NX_DP  :                                         FINNISH_LK201NX_TW  :     Finnish         LK401-              FINNISH_LK401AF_DP!                     (AF,LF,BF,MF)   :                                         FINNISH_LK401AF_TW  :     Flemish         LK201-              FLEMISH_LK201LB_DP!                     (AB,LB,BB,MB)a  :                                         FLEMISH_LK201LB_TW  :     Flemish         LK401-              FLEMISH_LK401AB_DP!                     (AB,LB,BB,MB)t  :                                         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)L  :                                         ITALIAN_LK401AI_TW  >     North American  LK201-              NORTH_AMERICAN_LK201LA!                     (AA,LA,BA,MA)s  E                                              (continued on next page)   E                           Customizing DECwindows Support Software 9-5n E  n      ' Customizing DECwindows Support Softwarev" 9.1 Customizing the Server Startup    A Table_9-1_(Cont.)__DECwindows_Keymap_____________________________o  A Dialect_________Model_______________DECwindows_Keymap_Name_______e  : North American  LK401-              NORTH_AMERICAN_LK401AA                 (AA,LA,BA,MA)m  8 Norwegian       LK201-              NORWEGIAN_LK201LN_DP                 (AN,LN,BN,MN)h  8                                     NORWEGIAN_LK201LN_TW  8                 LK201-(EN,RN,FN)    NORWEGIAN_LK201RN_DP  8                                     NORWEGIAN_LK201RN_TW  8 Norwegian       LK401-              NORWEGIAN_LK401AN_DP                 (AN,LN,BN,MN)   8                                     NORWEGIAN_LK401AN_TW  3 Polish          LK401-(BP)          POLISH_LK401_BPu  6 Portuguese      LK201-              PORTUGUESE_LK201LV                 (AV,LV,BV,MV)n  6 Portuguese      LK401-              PORTUGUESE_LK401AV                 (AV,LV,BV,MV)t  4 Russian         LK401-(BT)          RUSSIAN_LK401_BT  3 Slovakian       LK401-(CZ)          SLOVAK_LK401_CZp  6 Spanish         LK201-              SPANISH_LK201LS_DP                 (AS,LS,BS,MS)n  6                                     SPANISH_LK201LS_TW  6 Spanish         LK401-              SPANISH_LK401AS_DP                 (AS,LS,BS,MS)w  6                                     SPANISH_LK401AS_TW  6 Swedish         LK201-              SWEDISH_LK201LM_DP                 (AM,LM,BM,MM)c  6                                     SWEDISH_LK201LM_TW  6                 LK201-(NM,PM)       SWEDISH_LK201NM_DP  6                                     SWEDISH_LK201NM_TW  6 Swedish         LK401-              SWEDISH_LK401AM_DP                 (AM,LM,BM,MM)y  6                                     SWEDISH_LK401AM_TW  B                                           (continued on next page)  , 9-6  Customizing DECwindows Support Software n         E                               Customizing DECwindows Support SoftwareiE                                    9.1 Customizing the Server Startupt    E     Table_9-1_(Cont.)_DECwindows_Keymap______________________________i  E     Dialect_________Model_______________DECwindows_Keymap_Name_______-  ?     Swiss/French    LK201-              SWISS_FRENCH_LK201LK_DP !                     (AK,LK,BK,MK)w  ?                                         SWISS_FRENCH_LK201LK_TWs  ?     Swiss/French    LK401-              SWISS_FRENCH_LK401AK_DP !                     (AK,LK,BK,MK)   ?                                         SWISS_FRENCH_LK401AK_TW   ?     Swiss/German    LK201-              SWISS_GERMAN_LK201LL_DPn!                     (AL,LL,BL,ML)p  ?                                         SWISS_GERMAN_LK201LL_TWw  ?     Swiss/German    LK401-              SWISS_GERMAN_LK401AL_DPD!                     (AL,LL,BL,ML)   ?                                         SWISS_GERMAN_LK401AL_TW   2     Combined US/UK  LK201-(EE,RE,PE)    UK_LK201RE  2                                         US_LK201RE  2     Combined US/UK  LK401-(EE,RE,PE)    UK_LK401AA  E     ____________________________________US_LK401AA___________________   A              c. After you choose a keymap name, modify the server A                 startup file. For example, to change the keyboard <                 layout to a Dutch typewriter layout, add the:                 following line to the server startup file:  A                 $ DECW$DEFAULT_KEYBOARD_MAP == "DUTCH_LK201LH_TW"   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).   8           6. To add support for the Transmission Control@              Protocol/Internet Protocol (TCP/IP) transport usingD              the Compaq TCP/IP Services for OpenVMS product, add the              following line:  =              $ DECW$SERVER_TRANSPORTS == "DECNET,LOCAL,TCPIP"   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.  E                           Customizing DECwindows Support Software 9-7, s         ' Customizing DECwindows Support SoftwareR" 9.1 Customizing the Server Startup    9          To include support for other transports, add the =          last part of the transport image name to the list of A          transports. For example, suppose you want to add support @          for a customer-written transport that has the following          image name:  %          SYS$SHARE:DECW_TRANSPORT_FOON  *          You would add the following line:  7          $ DECW$SERVER_TRANSPORTS == "DECNET,LOCAL,FOO"   =       7. Reboot the workstations for which you customized the-          server startup.  @       8. Customize security as described in the Using DECwindows"          Motif for OpenVMS manual.  A       After you start the server, a per-server logical name table ?       is created on your system but is not added to the default &       logical name table search lists.  - 9.2  Using Compaq TCP/IP Services for OpenVMS   @       DECwindows contains support for the TCP/IP transport. This<       support requires Compaq TCP/IP Services for OpenVMS, a?       Compaq layered product. Before you can use the DECwindowsE@       TCP/IP transport interface, you must install Compaq TCP/IP       Services for OpenVMS.   ?          ________________________ Note ________________________   ?          Other vendors' implementation of TCP/IP transports use ?          different call interfaces. For this reason, DECwindows :          support for TCP/IP is compatible only with Compaq%          TCP/IP Services for OpenVMS.   ?          ______________________________________________________I  >       You can conserve memory and process slots by configuring9       Compaq TCP/IP Services for OpenVMS software for theo?       minimum DECwindows requirement to support the X protocol.E8       DECwindows only requires that INET_ACP be running.?       DECwindows does not require that the NFS server, the FTPD.8       server, or the remote terminal servers be running.  , 9-8  Customizing DECwindows Support Software a  a      E                               Customizing DECwindows Support Software E                          9.2 Using Compaq TCP/IP Services for OpenVMS     >           For more information about TCP/IP concepts, refer to?           the Compaq TCP/IP Services for OpenVMS documentation. ;           For information about how to configure the TCP/IP C           software, refer to the Compaq TCP/IP Services for OpenVMS 0           Installation and Configuration manual.  >           Documentation for Compaq TCP/IP Services for OpenVMSA           is included on the OpenVMS Online Documentation CD-ROM. >           Hardcopy documentation must be purchased separately.  .     9.3 Using Other Transports with DECwindows  <           DECwindows supports DECnet-Plus, local, and TCP/IPA           transports. However, you can use other transports, such ?           as new transports for layered products and transportsK@           from third-party vendors, with DECwindows by writing a/           DECwindows transport interface layer.   '     9.3.1 Writing a Transport InterfaceK  D           For information about writing a transport interface, refer1           to the VMS DECwindows Transport Manual.A  A           The transport interface image's file name must have the0C           following format where name is the unique transport name:   A           DECW$TRANSPORT_name (for transports supplied by Compaq) ?           DECW_TRANSPORT_name (for customer-written transports)   2     9.3.2 Installing the Transport Interface Image  A           Install the image as a protected image in the SYS$SHARE C           directory (as defined by an executive mode logical name). D           Compaq recommends that you install the image by adding the:           following line to SYS$MANAGER:SYSTARTUP_VMS.COM:  E           $ INSTALL CREATE SYS$SHARE:DECW_TRANSPORT_name/OPEN/SHARED- $           /HEADER_RESIDENT/PROTECTED  B           You can also include this command in a startup file that           SYSTARTUP_VMS calls.  E           To use this transport with the DECwindows server, customizet9           the server startup as described in Section 9.1.   E                           Customizing DECwindows Support Software 9-9A K  L      ' Customizing DECwindows Support Software  9.4 Using the Example TransportG      9.4  Using the Example Transport  <       DECwindows has an example transport interface based on@       the Compaq TCP/IP Services for OpenVMS layered product. It>       is similar to the DECwindows TCP/IP transport interface,;       except it includes its own source files and it uses ai;       different port number (5000). You can run the examplee8       transport interface simultaneously with the TCP/IP       transport interface.  >       If you have installed Compaq TCP/IP Services for OpenVMS@       software, you can install and use the example transport by       doing the following:  A       1. Copy the example transport to the SYS$SHARE directory as           follows:P  M          $ COPY DECW$EXAMPLES:DECW$TRANSPORT_EXAMPLE.EXE SYS$SHARE:/PROT=W:REK  A       2. Add the following line to SYS$MANAGER:SYSTARTUP_VMS.COM:   I          $ INSTALL CREATE SYS$SHARE:DECW$TRANSPORT_EXAMPLE /OPEN /SHARED-K$          /HEADER_RESIDENT /PROTECTED  =       3. Customize the private server startup as described in >          Section 9.1 for TCP/IP, except use the transport name<          "EXAMPLE". For example, you might add the following          line:  A          $ DECW$SERVER_TRANSPORTS == "DECNET,LOCAL,TCPIP,EXAMPLE"D  7       4. Reboot the workstation, or restart DECwindows.   <       5. Customize TCP/IP security as described in the Using9          DECwindows Motif for OpenVMS manual, but use theC5          transport name "EXAMPLE" instead of "TCPIP".   A       6. Create a DECterm window on the workstation and enter the           following command:   A          $ SET DISPLAY /CREATE /NODE=your_node /TRANSPORT=EXAMPLEE  ?          Substitute the node name of your workstation for your__          node.  A          Remember that the same transport must be running on both A          the client and server. It is not necessary, however, forK<          the client and the server to be on the same system.  - 9-10  Customizing DECwindows Support Software  W  _      E                               Customizing DECwindows Support Software E                                       9.4 Using the Example Transport0    D           7. Run any DECwindows application from the DECterm window.B              It now uses the example transport to display graphics?              on your workstation screen. For example, enter theL0              following command to run the clock:  (              $ RUN SYS$SYSTEM:DECW$CLOCK                                                                              E                          Customizing DECwindows Support Software 9-110 E  E                    E                                                                    10 E     _________________________________________________________________   E                                       Using VMSTAILOR and DECW$TAILOR     A           This chapter describes how to add (tailor on) or remove @           (tailor off) optional OpenVMS VAX files and DECwindowsA           support files from your system disk using VMSTAILOR anddD           DECW$TAILOR. You will need your OpenVMS VAX software mediaA           kit to tailor on files. Any site-specific customizationdD           that has been done to a class will be lost when that class           is tailored off.       10.1 Using VMSTAILOR  E           To add or remove unwanted OpenVMS VAX files from the systemoB           disk, use VMSTAILOR. For example, if you are not runningE           DECnet for OpenVMS, and you do not need the network supportiC           files, you can remove those files using VMSTAILOR. If youPB           later decide you want to run DECnet for OpenVMS, you canA           add the necessary files at any time using VMSTAILOR andnD           your OpenVMS VAX distribution media. (Note that you cannot6           tailor files on or off an alternate device.)       10.1.1 How VMSTAILOR Works  %           VMSTAILOR has three phases:r  @           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 eache?              class of OpenVMS VAX files and asks if you want to E              include them on the system disk. If you choose to tailorfD              files off, VMSTAILOR lists each class of files and asks=              if you want to delete them from the system disk.e  C           3. VMSTAILOR adds or deletes the files you indicated fromr@              the system disk. If you are tailoring files on, youE              must load your OpenVMS VAX distribution media in a drive @              available to the system. If your distribution media  E                                  Using VMSTAILOR and DECW$TAILOR 10-1     n       Using VMSTAILOR and DECW$TAILORr 10.1 Using VMSTAILOR    @          consists of more than one piece, put the first piece of"          the media into the drive.  :       The following is a list of classes and subclasses of=       OpenVMS VAX files that can be added or deleted by usingS=       VMSTAILOR. For a complete list of OpenVMS VAX files and_<       their functions, refer to the OpenVMS System Manager's@       Manual, Volume 2: Tuning, Monitoring, and Complex Systems.         o  Network Support  -             Incoming Remote File Access files *             Incoming Remote Terminal files             Network Test files             Remote Task Loading          o  Programming Support  $             Debugger utility (DEBUG)5             Image Dump utility (ANALYZE/PROCESS_DUMP)i>             RMS Analyze and FDL Editor utilities (ANALYZE/RMS,             ANALYZE/FDL)%             Message utility (MESSAGE)o0             Object and Shareable Image libraries             MACRO libraries              MACRO assembler 0             SDL intermediary form of STARLET.MLB"             Fortran required files"             VAX C object libraries  %       o  OpenVMS RMS Journaling FilesU  #       o  System Programming Support   5             Files-11 ODS-1,ISO 9660, High Sierra ACPss             Monitor utilityp!             Delta/XDelta debuggerm9             System Dump Analyzer utility (ANALYZE/SYSTEM,e             ANALYZE/CRASH).             System Symbol Table file (SYS.STB),             Miscellaneous Symbol Table files  "       o  Secure User's Environment  .             File Access Control List utilities+             Print and Batch Queue utilitieso.             Input Queue Symbiont (Card Reader)3             Accounting Log Report Generator utilityn  % 10-2  Using VMSTAILOR and DECW$TAILORn s  p      E                                       Using VMSTAILOR and DECW$TAILORuE                                                  10.1 Using VMSTAILORd                     DECdtm             o  Utilities                   Mail utility                 DUMP utility                 RUNOFF utility                 Phone utilityK$                 OpenVMS Help library4                 OpenVMS System Messages Help Library(                 Foreign Terminal Support5                 LAT-11 terminal server (via Ethernet) !                 Standalone BACKUPeB                 Error Log Report Generator utility (ANALYZE/ERROR)                 DECTPU utility*                 Terminal Fallback facility                 TECO editor !                 EDT documentationo4                 National Character Set utility (NCS)  *           o  VMS Workstation Support (VWS)  *                 Workstation device support              o  BLISS require files              o  Miscellaneous Files                   System map                 LPA-11 support  *           o  User Environment Test Package             o  Example Files  %     10.1.2 Removing OpenVMS VAX FilesT  ?           To remove unwanted files using VMSTAILOR, perform the            following steps:  *           1. Log in to the SYSTEM account.  :           2. Enter the following command and press Return:  '              $ RUN SYS$UPDATE:VMSTAILOR   >              VMSTAILOR displays a description of the VMSTAILOR/              program and the following message:w  7              Do you want to tailor files "ON" or "OFF"?E  A           3. Enter OFF to remove unwanted files and press Return.c  E                                  Using VMSTAILOR and DECW$TAILOR 10-3             Using VMSTAILOR and DECW$TAILORr 10.1 Using VMSTAILOR    :          The VMSTAILOR program lists each group, or class,;          of files and its size in blocks. Files are grouped :          according to their function. For example, all the=          files required for network support are in one class.I>          A file class is made up of many smaller groups called@          subclasses. You can eliminate an entire class of files,@          or you can eliminate one or more of its subclasses. For          example:              CLASS - Network support?                    Size of entire class (with subclasses): 1499gG                    Size of common files required for any subclass: 1249$I                    Do you wish to select the entire class (default = NO)?O
             . 
             .e
             .   @       4. Decide which file classes or subclasses you do not need?          to support your system. The VMSTAILOR program displaysa@          step-by-step instructions. Follow these instructions toA          specify which classes or subclasses of files you want tot          remove.  >       5. VMSTAILOR deletes the files you selected and displays=          the names of those files. After it finishes, AUTOGEN <          runs automatically to make the adjustments that are?          necessary after system files are deleted. AUTOGEN alsoh          reboots the system.  @          _______________________ Caution _______________________  8          To cancel VMSTAILOR during the first and second;          phases, press Ctrl/C, Ctrl/Y, or Ctrl/Z. Cancelingm?          VMSTAILOR during the third phase can cause a partiallyv          tailored disk.h  =          For a description of each phase, see Section 10.1.1.e  ?          ______________________________________________________             % 10-4  Using VMSTAILOR and DECW$TAILORw o  S      E                                       Using VMSTAILOR and DECW$TAILOR E                                                  10.1 Using VMSTAILORC    #     10.1.3 Adding OpenVMS VAX Filese  ?           To add optional OpenVMS VAX files that you previouslya>           removed, or that you chose not to install during the?           OpenVMS VAX installation procedure, do the following:K  *           1. Log in to the SYSTEM account.  E           2. Load your distribution media in a drive available to theCB              system. For example, if your distribution media is onD              a TK50 tape cartridge, load the first tape cartridge inD              a TK50 drive that is available to the system. Make sure,              the drive is on line and ready.  >              If you are adding files from a compact disc on anE              InfoServer, first determine whether the SYSGEN parameterAC              SCSNODE is defined on your system (see Section 5.5) or C              start the DECnet software, and then refer to step 2 ofM              Section 7.2.   :           3. Enter the following command and press Return:  '              $ RUN SYS$UPDATE:VMSTAILORl  >              VMSTAILOR displays a description of the VMSTAILOR/              program and the following message:n  7              Do you want to tailor files "ON" or "OFF"?   4           4. Enter ON to add files and press Return.  >              The VMSTAILOR program lists each group, or class,?              of files and its size in blocks. Files are groupedP>              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 you0@              can add one or more of its subclasses. For example:  $              CLASS - Network supportC                        Size of entire class (with subclasses): 1499rK                        Size of common files required for any subclass: 1249tM                        Do you wish to select the entire class (default = NO)?e                 .a                 .                  .e  E                                  Using VMSTAILOR and DECW$TAILOR 10-5  t  a       Using VMSTAILOR and DECW$TAILOR  10.1 Using VMSTAILOR    <       5. Decide which file classes or subclasses you need to;          add. VMSTAILOR displays step-by-step instructions.i>          Follow these instructions to specify which classes or-          subclasses of files you want to add.   @       6. VMSTAILOR adds the files you specified and displays the=          names of the files. After the files have been added,R@          AUTOGEN runs automatically to make the adjustments thatA          are necessary after system files are added. AUTOGEN alsoi          reboots the system.  @          _______________________ Caution _______________________  8          To cancel VMSTAILOR during the first and second;          phases, press Ctrl/C, Ctrl/Y, or Ctrl/Z. Cancelingn?          VMSTAILOR during the third phase can cause a partiallyy          tailored disk.u  =          For a description of each phase, see Section 10.1.1.   ?          ______________________________________________________   >       After adding files to the system disk, apply any updates<       that affect them. OpenVMS VAX update procedures create8       a .TXT file that contains a description of patched8       files. This file usually has the following format:       SYS$UPDATE:VMSUn06n.TXT.  :       For example, assume that you do not need the OpenVMS;       Phone utility (PHONE) and you run VMSTAILOR to removee?       those files. Later, you decide you want to use Phone. Run =       VMSTAILOR to return the Phone files to the system disk; @       then, apply any OpenVMS VAX update that has occurred since2       Version 7.3 that affected the Phone utility.   10.1.4  Sample Session  A       Example 10-1 shows how to add all Network Support files and :       selected Programming Support files to a system disk.  & Example 10-1  Sample VMSTAILOR Session  B                                           (continued on next page)    % 10-6  Using VMSTAILOR and DECW$TAILORl e         E                                       Using VMSTAILOR and DECW$TAILORAE                                                  10.1 Using VMSTAILORe    1     Example 10-1 (Cont.) Sample VMSTAILOR Session        $ RUN SYS$UPDATE:VMSTAILOR        .        .        .2      Do you want to tailor files "ON" or "OFF"? ON  
     TAILOR-ON 
     --------- J      You will now be prompted with a list of the classes and subclasses ofM      OpenVMS Vax files that are optional. The size of each class and subclass J      is included in the list. This will help you decide whether or not you4      want to add a class or subclass to your system.  P     Under some classes, there is a set of common files that is required in orderC      for any subclasses to work. These files are added when you askr:      for either the entire class or any of its subclasses.  4     Total size of the system disk is 2376153 blocks.:     Total space used on the system disk is 2241252 blocks.9     Total space left on the system disk is 134901 blocks.o       CLASS - Network supportt:               Size of entire class (with subclasses): 1499B               Size of common files required for any subclass: 1249H               Do you wish to select the entire class (default = NO)? YES  E                                              (continued on next page)-                                E                                  Using VMSTAILOR and DECW$TAILOR 10-7m n  p       Using VMSTAILOR and DECW$TAILOR  10.1 Using VMSTAILOR    . Example 10-1 (Cont.)  Sample VMSTAILOR Session   CLASS - Programming SupportS7           Size of entire class (with subclasses): 14706a;           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:t@      SUBCLASS - Debugger utility (DEBUG) (4690 blocks) [NO]: YESO      SUBCLASS - Image Dump utility (ANALYZE/PROCESS_DUMP) (48 blocks) [NO]: YES P      SUBCLASS - RMS Analyze and FDL Editor utilities (ANALYZE/RMS, ANALYZE/FDL)-      (374 blocks) [NO]:YES;      SUBCLASS - Message utility (MESSAGE) (49 blocks) [NO]: L      SUBCLASS - Object and Shareable Image libraries (4311 blocks) [NO]: YES3      SUBCLASS - Macro libraries (2293 blocks) [NO]:l2      SUBCLASS - Macro assembler (457 blocks) [NO]:H      SUBCLASS - SDL intermediary form of STARLET.MLB (1957 blocks) [NO]:7      SUBCLASS - FORTRAN require files (51 blocks) [NO]: 9      SUBCLASS - VAX-C object libraries (471 blocks) [NO]:    CLASS - RMS journaling files5           Size of entire class (with subclasses): 155c-           No subclasses in this tailor class. @           Do you wish to select the entire class (default = NO)?  " CLASS - System programming Support6           Size of entire class (with subclasses): 2286<           Size of common files required for any subclass: 93@           Do you wish to select the entire class (default = NO)?E           Do you wish to select any of its subclasses (default = NO)?c  B                                           (continued on next page)                          % 10-8  Using VMSTAILOR and DECW$TAILOR  s  i      E                                       Using VMSTAILOR and DECW$TAILORuE                                                  10.1 Using VMSTAILORT    1     Example 10-1 (Cont.) Sample VMSTAILOR Session_  %     CLASS - Secure User's Environment_9               Size of entire class (with subclasses): 919 ?               Size of common files required for any subclass: 0cD               Do you wish to select the entire class (default = NO)?  I               Do you wish to select any of its subclasses (default = NO)?           .        .        .       Files have been selected7     Do you wish to add all of the options selected? YESn3     Creating temporary command file, please wait... ?     * Enter device containing OpenVMS distribution media: mua0:           .        .        .       10.2 Using DECW$TAILOR  >           You can use DECW$TAILOR to add or remove some or all@           DECwindows X11 display server, base support, and fontsA           files from the system disk. For example, if you are notnA           planning to use the DECwindows PEX (PHIGS Extensions to ?           X) support, you can remove those files. Later, if youaA           decide you want DECwindows programming support, you canuE           add the files to the system disk using DECW$TAILOR and yourpC           DECwindows distribution media. You cannot tailor files ons%           or off an alternate device.i  B             ________________________ Note ________________________  =             To add or remove DECwindows Motif for OpenVMS VAXr>             files, refer to the DECwindows Motif Version 1.2-3A             for OpenVMS Installation Guide. DECW$TAILOR will onlyeB             tailor on or off those DECwindows display server, base>             support, and font files, with the exception of the<             required files, supplied on the OpenVMS VAX kit.  B             ______________________________________________________  E                                  Using VMSTAILOR and DECW$TAILOR 10-9"            Using VMSTAILOR and DECW$TAILORe 10.2 Using DECW$TAILOR     10.2.1  How DECW$TAILOR Works   #       DECW$TAILOR has three phases:   >       o  DECW$TAILOR asks if you want to tailor your system by>          adding files (tailor on) or by deleting files (tailor          off).  <       o  If you choose to tailor files on, DECW$TAILOR lists?          each class of DECwindows files and asks if you want tonA          include them on the system disk. If you choose to tailor >          files off, DECW$TAILOR lists each class of DECwindows;          files and asks if you want to delete them from thet          system disk.   A       o  DECW$TAILOR adds or deletes the files you indicated from1A          the system disk. If you are tailoring files on, you must @          load your DECwindows distribution media in a drive thatA          is available to the system. For example, if your OpenVMSD?          VAX distribution kit is on a TK50 tape cartridge, load A          the second tape cartridge, which contains the DECwindowsc>          support files, into a TK50 drive that is available to          the system.  ' 10.2.2  DECwindows Files You Can Tailorh  :       The following is a list of classes and subclasses of7       DECwindows files that you can add or delete usingi;       DECW$TAILOR. For a list of DECwindows files and their         functions, see Appendix E.  ?       o  DECwindows base support files - If you plan to instally>          the separate DECwindows Motif for OpenVMS VAX layered6          product, you must add the base support files.  :       o  DECwindows workstation support files - If you are:          installing DECwindows support on a workstation or:          in a cluster that includes workstations or if you?          intend to install the DECwindows Motif for OpenVMS VAX A          layered product, you need the workstation support files._)          Otherwise, you do not need them._  ?          ________________________ Note ________________________y  :          If you tailor device support files ON or OFF, the          system reboots.  ?          ______________________________________________________u  & 10-10  Using VMSTAILOR and DECW$TAILOR A  V      E                                       Using VMSTAILOR and DECW$TAILOR E                                                10.2 Using DECW$TAILOR     >           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 morehC              readable display when you run DECwindows applications.mE              If your workstation monitor cannot display 100 dots/inchdE              fonts (for example, a VR260 or VR290), you can save diskSE              space by not selecting this option. For more informationoE              about the capabilities of your particular monitor, refer 3              to 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 diskeE              space by not selecting this option. For more information E              about the capabilities of your particular monitor, refer 3              to the owner's guide for your monitor.s  $     10.2.3 Removing DECwindows Files  A           To remove DECwindows files from the system disk, do thel           following:  *           1. Log in to the SYSTEM account.  :           2. Type the following command, and press Return:  )              $ RUN SYS$UPDATE:DECW$TAILORt  C              DECW$TAILOR displays information about the DECW$TAILORw8              program and displays the following message:  7              Do you want to tailor files "ON" or "OFF"?e  A           3. Type OFF to remove unwanted files, and press Return.y  @              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. B              A file class is made up of many small subclasses. You?              can eliminate an entire class of files, or you can B              eliminate one or more of its subclasses. For example:        E                                 Using VMSTAILOR and DECW$TAILOR 10-11i V  A       Using VMSTAILOR and DECW$TAILORV 10.2 Using DECW$TAILOR    5          CLASS - DECwindows workstation support filesi@                    Size of entire class (with subclasses): 14301G                    Size of common files required for any subclass: 8937aI                    Do you wish to select the entire class (default = NO)?=
             . 
             .e
             .t  A       4. Decide which file classes or subclasses you need to add.0?          DECW$TAILOR displays step-by-step instructions. FollowR>          these instructions to specify which of the classes or'          subclasses you want to remove.A  @       5. DECW$TAILOR deletes the files you selected and displays@          the names of those files. If you deleted device support@          files, the system automatically shuts down and reboots.  @          _______________________ Caution _______________________  :          To cancel DECW$TAILOR during the first and second;          phases, press Ctrl/C, Ctrl/Y, or Ctrl/Z. Canceling 7          DECW$TAILOR during the third phase can cause ab!          partially tailored disk.   =          For a description of each phase, see Section 10.2.1.l  ?          ______________________________________________________    10.2.4  Adding DECwindows Filese  ?       To install DECwindows device support and font files after @       the OpenVMS VAX installation or to add optional DECwindows@       files that you previously chose not to install or that you        removed, do the following:  &       1. Log in to the SYSTEM account.  ;       2. Load the OpenVMS VAX distribution media containing >          the DECwindows save sets in a drive available to your=          system. For example, if your distribution media is a A          TK50 tape cartridge, load the second tape cartridge intoO@          a TK50 drive that is available to the system. Make sure(          the drive is on line and ready.    & 10-12  Using VMSTAILOR and DECW$TAILOR e         E                                       Using VMSTAILOR and DECW$TAILOR E                                                10.2 Using DECW$TAILOR     >              If you are adding files from a compact disc on anE              InfoServer, first determine whether the SYSGEN parameter C              SCSNODE is defined on your system (see Section 5.5) oryC              start the DECnet software, and then refer to step 2 ofa&              Section 7.2 in Chapter 7.  ;           3. Enter the following command, and press Return:   )              $ RUN SYS$UPDATE:DECW$TAILORD  C              DECW$TAILOR displays information about the DECW$TAILORr9              program, and displays the following message:,  7              Do you want to tailor files "ON" or "OFF"?l  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 groupedsD              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 filesMD                        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)?                  .u                 .M                 .   D           5. Decide which file classes or subclasses you do not needE              to support your system. The DECW$TAILOR program displays D              step-by-step instructions. Follow these instructions toC              specify which of the classes or subclasses you want to               add.L  E           6. DECW$TAILOR installs the files you selected and displaysoB              the names of those files. If you added device supportD              files, the system automatically shuts down and reboots.  C             _______________________ Caution _______________________e  =             To cancel DECW$TAILOR during the first and secondT>             phases, press Ctrl/C, Ctrl/Y, or Ctrl/Z. Canceling:             DECW$TAILOR during the third phase can cause a  E                                 Using VMSTAILOR and DECW$TAILOR 10-13     e       Using VMSTAILOR and DECW$TAILORs 10.2 Using DECW$TAILOR    ;          partially tailored disk. For a description of each #          phase, see Section 10.2.1.p  ?          ______________________________________________________p  >       After adding files to the system disk, apply any updates;       that affect them. For example, suppose you delete thev<       Version 7.3 DECwindows 100 dots/inch video font files.<       Later on, you are able to use the 100 dots/inch fonts,>       so you run DECW$TAILOR to return the files to the system?       disk. You must then apply any OpenVMS VAX update that has @       occurred since Version 7.3 that affected the 100 dots/inch>       video font files. OpenVMS VAX update procedures create a>       .TXT file that contains a description of modified files.;       This file is usually named with the following format:i!       SYS$UPDATE:VMSUn05n.TXT[1].f   10.2.5  Sample Session  7       Example 10-2 illustrates how to add the files forl*       DECwindows 100 dots/inch font files.  ( Example 10-2  Sample DECW$TAILOR Session   $ RUN SYS$UPDATE:DECW$TAILOR    .    .    .  .  Do you want to tailor files "ON" or "OFF"? ON  	 TAILOR-ON 	 --------- C  You will now be prompted with a list of the classes and subclasses_N  of DECwindows files that are optional. The size of each class and subclass isO  included in the list. This will help you decide whether or not you want to add $  a class or subclass to your system.  M  Under some classes, there is a set of common files that is required in orderT?  for any subclasses to work. These files are added when you ask 6  for either the entire class or any of its subclasses.  B                                           (continued on next page)         ____________________@       [1]   Examine this file to determine if the update patched  )             the 100 dots/inch font files.d  & 10-14  Using VMSTAILOR and DECW$TAILOR s  i      E                                       Using VMSTAILOR and DECW$TAILORVE                                                10.2 Using DECW$TAILOR     3     Example 10-2 (Cont.) Sample DECW$TAILOR Sessione  4     Total size of the system disk is 2376153 blocks.:     Total space used on the system disk is 1728072 blocks.9     Total space left on the system disk is 648081 blocks.   )     CLASS - DECwindows base support files :               Size of entire class (with subclasses): 3363  1               No subclasses in this tailor class.eD               Do you wish to select the entire class (default = NO)?  0     CLASS - DECwindows workstation support files;               Size of entire class (with subclasses): 12376fB               Size of common files required for any subclass: 8916G               Do you wish to select the entire class (default = NO)? NOaI               Do you wish to select any of its subclasses (default = NO)?   -     CLASS - 75 dots per inch video font filesW:               Size of entire class (with subclasses): 4537  1               No subclasses in this tailor class.ND               Do you wish to select the entire class (default = NO)?  .     CLASS - 100 dots per inch video font files:               Size of entire class (with subclasses): 36931               No subclasses in this tailor class.aH               Do you wish to select the entire class (default = NO)? YES       Files have been selected7     Do you wish to add all of the options selected? YESp3     Creating temporary command file, please wait...iB     * Enter device containing DECwindows distribution media: MUA0:        .        .        .                  E                                 Using VMSTAILOR and DECW$TAILOR 10-151                         E                                                                     ACE     _________________________________________________________________l  E                                      Multiversion VAX Upgrade Processu    D           This appendix provides you with a quick method and an easyC           to follow set of directions to apply multiple OpenVMS VAX 2           version upgrades to your current system.  B             ________________________ Note ________________________  B             By following these directions, the time that you spend=             upgrading your VAX computer from Version 5.5-2 to 5             Version 7.3 can be significantly reduced.i  B             ______________________________________________________       A.1 Determine Your Patha  E           Your first step is to determine which upgrade path you needCC           to perform. Table A-1 lists the recommended upgrade pathsn+           to reach OpenVMS VAX Version 7.3.s  E           Table_A-1_OpenVMS_VAX_Upgrade_Version_Matrix_______________h  '                            IntermediatetE           Current_Version__Version(s)_______Final_Version____________   /           5.5-2            6.1, followed    7.3_'                            by 6.2, 7.0,g)                            7.1, or 7.2[1]i  /           6.0              6.2              7.3h  /           6.1              6.2              7.3n  E           [1]You_must_perform_two_intermediate_upgrades:_First,______   C           upgrade to Version 6.1. Then, perform a second upgrade to.C           either Version 6.2, 7.0, 7.1, or 7.2, prior to your final            upgrade to 7.3.t  E                                              (continued on next page)t  E                                  Multiversion VAX Upgrade Process A-1c r  e        Multiversion VAX Upgrade Process A.1 Determine Your Pathk    A       Table_A-1_(Cont.)__OpenVMS_VAX_Upgrade_Version_Matrix______A  #                        Intermediate A       Current_Version__Version(s)_______Final_Version____________   +       6.2              [2]              7.31  +       7.0              [2]              7.3   +       7.1              [2]              7.3   +       7.2              [2]              7.3eA       [2]No_intermediate_version_needed._________________________(  A       ___________________________________________________________n  # A.2  Multiversion Upgrade Procedurei  @       This procedure refers to an intermediate upgrade and finalA       upgrade. An intermediate upgrade is defined as a version of A       the operating system that you need to install to reach your        final version.  >       The final upgrade is the version of the operating system>       that you want to be running on your system at the end of       this process..  @          ______________________ Important ______________________  8          You should not plan to stay at the intermediate7          version. If you need to upgrade to and run them?          intermediate version, use the normal upgrade procedureu=          located in the installation manual for that specifico          version.s  ?          ______________________________________________________   # A.2.1  Before You Begin the Upgradeb  <       Before you begin the multiversion upgrade, you need to"       perform the following steps:  >       1. Locate the OpenVMS VAX software kits for the versions          that you need.o  @       2. Review the layered products on your system to determineA          the minimum supported version of each layered product to =          be installed on your final operating system version.D  ?          o  Determine which layered products you want to run on ?             your system. See the web page at the following URL:   % A-2  Multiversion VAX Upgrade Processt e  s      E                                      Multiversion VAX Upgrade ProcesstE                                    A.2 Multiversion Upgrade Procedure     7                  http://www.support.compaq.com/openvms/i  D              o  For information about specific layered products, see                 Section A.3.       A.2.2 Intermediate Upgrade  B           Follow these steps to perform an intermediate upgrade of,           your OpenVMS VAX operating system.  B           1. Review your mixed-cluster version environment. CompaqC              recommends that you upgrade all of your systems to the E              same version prior to performing a multiversion upgrade.T  <           2. Review the firmware running on your system. For=              information about specific layered products, seee              Section A.3.   >           3. Review the version-specific documentation. Compaq?              recommends that you read the New Features, Release <              Notes, Installation Guide, and Software Product8              Description available in your software kit.  ;           4. Review the preupgrade checklist located in the                Installation Guide.  !           5. Perform the upgrade.i  C             ______________________ Important ______________________d  ?             For the intermediate upgrade, install only the baset<             operating system. Do not install any options. By?             installing only the base operating system, the time B             that you spend upgrading your VAX computer during this>             intermediate upgrade can be reduced by 40 percent.  B             ______________________________________________________  =           6. Perform the postupgrade checklist located in the$               Installation Guide.  B           7. If you are performing multiple intermediate upgrades,+              repeat steps 3-7 as necessary.s  =           8. You have completed the intermediate phase of thepE              multiversion upgrade procedure. Proceed to Section A.2.3T@              to apply the final upgrade phase of this procedure.  E                                  Multiversion VAX Upgrade Process A-3m    e        Multiversion VAX Upgrade Process" A.2 Multiversion Upgrade Procedure     A.2.3  Final Upgrade  =       Follow these steps to perform the final upgrade of your #       OpenVMS VAX operating system.d  :       1. Review the version-specific documentation. Compaq;          recommends that you read the New Features, Release 8          Notes, Installation Guide, and Software Product4          Description available in your software kit.  8       2. Perform the preupgrade checklist located in the          Installation Guide.  =       3. Perform the complete upgrade and select the optionall4          files that you need for your final version.  9       4. Perform the postupgrade checklist located in thed          Installation Guide.  =       5. Upgrade the layered products on your system based on >          your review of layered products in Section A.2.1. See+          the web page at the following URL:   /          http://www.support.compaq.com/openvms/   6 A.3  Specific Layered Product and Firmware Information  :       This section provides specific information about the.       following layered products and firmware:         o  BASEstaro         o  Debuggere   A.3.1  Layered Products   ?       This section contains information about layered products.N         BASEstar Classic Domains  A       A BASEstar Classic domain that consists of BASEstar Classice=       for OpenVMS VAX Versions 3.2 and 3.3 is fully supportedi>       on OpenVMS Version 7.3, as long as you obtained the kits&       through normal support channels.  ?       However, on Alpha systems you need to be running BASEstarr?       Classic Version 3.4. This means that any BASEstar Classics>       domain consisting of both VAX and Alpha systems can only=       have the VAX systems upgraded to OpenVMS Version 7.3 ata       this time.  % A-4  Multiversion VAX Upgrade Processw    a      E                                      Multiversion VAX Upgrade ProcesseE                 A.3 Specific Layered Product and Firmware Informationi    1           Debugger Graphical User Interface (GUI)   ?           To run the Debugger Graphical User Interface (GUI) on0A           OpenVMS Version 7.3, you must be running the DECwindows B           Motif for OpenVMS layered product. See Section 1.1.3 for-           information about DECwindows Motif.                                                                               E                                  Multiversion VAX Upgrade Process A-5  o  l                    E                                                                     BrE     __________________________________________________________________  E                                         License Management Supplementu    @           This appendix contains supplemental information to theD           license instructions given in the installation and upgradeB           procedures and in the OpenVMS License Management UtilityC           Manual. Although most of the information in this appendixcD           pertains to managing OpenVMS and System Integrated Product=           (SIP) licenses, some of the information pertains ton,           managing layered product licenses.  9           This appendix covers the following information:   &           o  Registering your licenses  <           o  Using the License Unit Requirement Table (LURT)  4           o  License Management Facility (LMF) notes  1           o  Volume Shadowing for OpenVMS license   ;           o  Other System Integrated Product (SIP) licenses   !     B.1 Registering Your Licenses   :           This section provides an overview of the license!           registration procedure.        B.1.1 When to Register  A           After you install the OpenVMS VAX operating system, you1>           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 yous           have purchased:v             o  VAXclusters  /           o  Compaq DECnet-Plus for OpenVMS VAX.  ,           o  DECnet Phase IV for OpenVMS VAX  #           o  OpenVMS RMS Journaling   E                                     License Management Supplement B-1             License Management Supplement  B.1 Registering Your Licenses     %       o  Volume Shadowing for OpenVMS   <       After you upgrade the OpenVMS VAX operating system, inA       most cases, there is no need to reregister licenses for the #       operating system or for SIPs._  =       In addition to the OpenVMS VAX operating system and ther<       SIPs, many layered products-including DECwindows Motif>       for OpenVMS VAX-that run on OpenVMS VAX Version 7.3 also@       require license registration. Refer to the OpenVMS LicenseA       Management Utility Manual for a full explanation of licenset       registration.r   B.1.2  How to Register  9       To register a license, you need to obtain a Products@       Authorization Key (PAK). A typical PAK is a piece of paper?       provided by Compaq Computer Corporation that contains them=       appropriate information to authorize access to softwarem?       on a VAX computer or in a VAXcluster environment. You canu?       obtain a PAK from a Compaq representative the same way as        you obtain software.  >       See Table B-1 for a complete list of the versions of the=       OpenVMS VAX operating system and the VAX computers thatm-       were first supported by these versions.   ?       Table B-1  First VMS or OpenVMS Version That Supports VAXtA       ___________Computers_______________________________________   A       VMS_Version_____First_Computer_Support_____________________p  7       Version 5.0     VAX 6000 Model 2xx, VAX 8820-8840t  (       Version 5.0-2A  MicroVAX 3300/3400  <       Version 5.1     VAX 6000 Model 3xx, MicroVAX 3800/3900  2       Version 5.1-B   VAXstation 3100, Model 30/40  *       Version 5.1-1   VAXstation 3520/3540  7       Version 5.2     VAX 6000 Model 4xx, MicroVAX 3100   2       Version 5.2-1   VAXstation 3100, Model 38/48  B                                           (continued on next page)  " B-2  License Management Supplement o  v      E                                         License Management Supplement E                                         B.1 Registering Your Licenses     =           Table B-1 (Cont.) First VMS or OpenVMS Version That E           __________________Supports_VAX_Computers___________________d  E           VMS_Version_____First_Computer_Support_____________________g  ,           Version 5.3     No CPUs introduced  ,           Version 5.3-1   No CPUs introduced  ,           Version 5.3-2   VAX 4000 Model 300  A           Version 5.4     VAXstation 3100 Model 76, VAX 9000, VAXe3                           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 ModelsiA                           30, 40, and 80, VAX 6000 Model 600, VAXtC                           4000 Model 500, VAXstation 4000 Model 60,r-                           and VAXft Model 110_  D           Version 5.5-2   VAX 4000 Model 100, VAXstation 4000 ModelsA                           90 and 100, MicroVAX 3100 Model 90, VAXmA                           4000 Model 400, VAX 4000 Model 600, VAXaA                           7000 Model 600, and VAX 10000 Model 600g  D           Version 5.5-    VAX 4000 Models 100A, 500A, 600A, and 700A
           2H4e  )           Version 5.5-    VAXft Model 810_
           2HF_  E           ___________________________________________________________i           OpenVMS E           Version_________First_Computer_Support_____________________e  6           Version 6.0     VAX 7000 Models 650 and 660,6                           VAX 10000 Models 600 and 650  ,           Version 6.1     VAX 7000 Model 7xx  B           Version 6.2     VAX 4000 Model 106A, MicroVAX 3500 ModelA                           95A, MicroVAX 3100 Model 96, VAXstation E           ________________4000_Model_96______________________________V  E                                     License Management Supplement B-3U a          License Management Supplement 3 B.2 Using the License Unit Requirement Table (LURT)n    4 B.2  Using the License Unit Requirement Table (LURT)  8       Many PAKs contain a table name in the availability9       or activity fields. This name refers to a column ino:       the License Unit Requirement Table (LURT). (For more<       information about using the LURT, refer to the OpenVMS)       License Management Utility Manual.)   =       Table B-2 has seven lettered columns (A, B, C, D, E, F, =       and I; G and H are reserved by Compaq and therefore areo?       not listed). The numbers listed in these columns indicateo=       the number of license units required for each processorm?       listed in the System Marketing Model column. For example,.?       if your PAK specifies availability = F, you would require ;       100 license units to load the license on a VAX-11/780e>       computer, or 4800 license units to load the license on a       VAX 9000-430 computer.  A       Note that some PAKs specify MOD_UNITS in the options field.s?       The MOD_UNITS option allows the system manager to use theh>       DCL command LICENSE MODIFY/UNITS to temporarily increase=       the size of the PAK. This permits a product to be used,h<       in certain emergency situations, on a processor larger=       than the processor size specified in the license. Check3@       your license terms and conditions before modifying license>       units. Reset the PAK size to its original size after the&       emergency situation is resolved.                                    " B-4  License Management Supplement           E                                         License Management SupplementnE                   B.2 Using the License Unit Requirement Table (LURT)     E     Table_B-2_License_Unit_Requirement_Table_(LURT)__________________r  ?                           ________License_Types_by_Code________n  E                           ________OpenVMS________  SIP__  ____LP_____        System MarketingE     Model__________________A_____B____C_____D_______E______F______I__u  E     VAX-11/730             10   NA    NA    NA     230      50     50d  E     VAX 11/750             12   NA    NA    NA     230     100    100   E     VAX 11/780, 785        13   NA    NA    NA     230     100    100   E     VAX 6000-210, 6000-    58   NA    NA    NA     230     300    300-     310l  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    600n     320,     6000-410  E     VAX 6000-230, 6000-    81   NA    NA    NA     400     900    900u     330,     6000-510  E     VAX 6000-240, 6000-    93   NA    NA    NA     400    1200   1200a     340, 6000-350,     6000-420, 7000-610,s
     10000-610a  E     Key_to_License_Type_Codes_and_Values_____________________________   4      A-OpenVMS Capacity or OpenVMS Unlimited or Base      B-OpenVMS Servert      C-OpenVMS Concurrent user      D-OpenVMS Workstations !      E-System integrated productsi      F-Layered products       G-Reserved (not listed)$      H-OpenVMS reserved (not listed)      I-Layered products       NA-Not applicable  E                                              (continued on next page)M  E                                     License Management Supplement B-5             License Management Supplement 3 B.2 Using the License Unit Requirement Table (LURT)e    A Table_B-2_(Cont.)__License_Unit_Requirement_Table_(LURT)_________   ;                       ________License_Types_by_Code________1  A                       ________OpenVMS________  SIP__  _____LP____    System MarketingA Model__________________A_____B____C_____D_______E______F______I__l  A VAX 6000-540, 6000-   170   NA    NA    NA     600    2400   2400v 640   A VAX 6000-550, 6000-   195   NA    NA    NA     600    2400   2400  650   A VAX 6000-560, 6000-   220   NA    NA    NA     600    2400   2400S 660J  A VAX 6000-610           81   NA    NA    NA     400    1200   1200S  A VAX 8200, 8250         20   NA    NA    NA     230     100    100i  A VAX 8300, 8350         25   NA    NA    NA     230     200    200   A VAX 8500               63   NA    NA    NA     230     400    400o  A VAX 8530               65   NA    NA    NA     230     400    400r  A VAX 8550, 8700,        72   NA    NA    NA     400     600    600e 8810  A VAX 8600, 8650         28   NA    NA    NA     230     400    400o  A VAX 8800, 8820         93   NA    NA    NA     400    1200   1200l  A VAX 8830, 6000-360,   119   NA    NA    NA     600    1800   1800  6000-430, 6000-520,i 6000-620  A Key_to_License_Type_Codes_and_Values_____________________________w  1   A-OpenVMS Capacity or OpenVMS Unlimited or Base    B-OpenVMS Server   C-OpenVMS Concurrent userK   D-OpenVMS Workstations   E-System integrated products   F-Layered products   G-Reserved (not listed) !   H-OpenVMS reserved (not listed)i   I-Layered products   NA-Not applicableu  B                                           (continued on next page)  " B-6  License Management Supplement           E                                         License Management SupplementiE                   B.2 Using the License Unit Requirement Table (LURT)a    E     Table_B-2_(Cont.)_License_Unit_Requirement_Table_(LURT)__________t  ?                           ________License_Types_by_Code________e  E                           ________OpenVMS________  SIP__  ____LP______       System MarketingE     Model__________________A_____B____C_____D_______E______F______I__4  E     VAX 7000-620,         145   NA    NA    NA     600    1800   1800A
     10000-620x  E     VAX 6000-440, 6000-   143   NA    NA    NA     600    2400   24000     450,     6000-460, 6000-530  E     VAX 7000-630,         167   NA    NA    NA     600    2400   2400      10000-630,  E     VAX 7000-640,         197   NA    NA    NA     600    2400   2400      10000-640,  E     VAX 6000-630,         143   NA    NA    NA     600    2400   2400      9000-210, 9000-410  E     VAX 9000-420          241   NA    NA    NA     800    4800   4800   E     VAX 9000-430          330   NA    NA    NA     800    4800   4800   E     VAX 9000-440          386   NA    NA    NA     800    4800   4800V  E     VAX 7000-710, 810      93   NA    NA    NA     230     600    600t  E     VAX 7000-720, 820     193   NA    NA    NA     230     600    600r  E     VAX 7000-730, 830     293   NA    NA    NA     230     600    600o  E     VAX 7000-740, 840     393   NA    NA    NA     230     600    600   E     Key_to_License_Type_Codes_and_Values_____________________________   4      A-OpenVMS Capacity or OpenVMS Unlimited or Base      B-OpenVMS Server       C-OpenVMS Concurrent user      D-OpenVMS Workstationss!      E-System integrated products       F-Layered productsL      G-Reserved (not listed)$      H-OpenVMS reserved (not listed)      I-Layered products       NA-Not applicable  E                                              (continued on next page)n  E                                     License Management Supplement B-7a n  0       License Management Supplement03 B.2 Using the License Unit Requirement Table (LURT)     A Table_B-2_(Cont.)__License_Unit_Requirement_Table_(LURT)_________   ;                       ________License_Types_by_Code________e  A                       ________OpenVMS________  SIP__  _____LP____H   System MarketingA Model__________________A_____B____C_____D_______E______F______I___  A VAX 7000-750, 850     493   NA    NA    NA     230     600    600   A VAX 7000-760, 860     593   NA    NA    NA     230     600    600_  A MicroVAX II            18   NA    100   NA     230      50     50   A MicroVAX 2000,         18   NA    100   NA     230      20     20. 3100-10e, 3100-20e,7 3100-30, 3100-40,s 3100-80   A MicroVAX 3100-90,      60   NA    100   NA     230      20     20  3100-96, 3100-96AM  A MicroVAX 3500,         60   NA    100   NA     230     200    200_ 3600, 3800, 3900,_ 4000-200  A MicroVAX 3300,         60   NA    100   NA     230     100    100a 3400, 4000-100,s	 4000-106At  A VAX 4000-100, 4000-    60   NA    100   NA     230     100    100  106   A Key_to_License_Type_Codes_and_Values_____________________________o  1   A-OpenVMS Capacity or OpenVMS Unlimited or Basev   B-OpenVMS Server   C-OpenVMS Concurrent user    D-OpenVMS Workstations   E-System integrated products   F-Layered products   G-Reserved (not listed)e!   H-OpenVMS reserved (not listed)U   I-Layered products   NA-Not applicablee  B                                           (continued on next page)  " B-8  License Management Supplement o  i      E                                         License Management SupplementeE                   B.2 Using the License Unit Requirement Table (LURT)e    E     Table_B-2_(Cont.)_License_Unit_Requirement_Table_(LURT)__________=  ?                           ________License_Types_by_Code________   E                           ________OpenVMS________  SIP__  ____LP_____s       System MarketingE     Model__________________A_____B____C_____D_______E______F______I__o  E     VAX 4000-300, 4000-    60   NA    100   NA     230     300    300h     400,     4000-500A, 4000-	     600A,t     4000-700A, 4000-     706A  E     VAX 4000-500, 4000-    60   NA    100   NA     400     900    900e     600s  E     VAXstation II,        NA    NA    NA    100     50      10     10 
     II/GPX  E     VAXstation 2000,      NA    NA    NA    100     50      10     10n     2000/GPX  E     VAXstation 3100,      NA    NA    NA    100     50      10     10u     3200, 3500, 3520,      3540, 4000-60,     4000 VLC, 4000-90,     4000-96u  E     VAXserver 2000        NA      52  NA    NA      50      10     10a  E     Key_to_License_Type_Codes_and_Values_____________________________e  4      A-OpenVMS Capacity or OpenVMS Unlimited or Base      B-OpenVMS Server_      C-OpenVMS Concurrent user      D-OpenVMS Workstationsy!      E-System integrated products       F-Layered productsn      G-Reserved (not listed)$      H-OpenVMS reserved (not listed)      I-Layered products_      NA-Not applicable  E                                              (continued on next page)   E                                     License Management Supplement B-91    0       License Management Supplement 3 B.2 Using the License Unit Requirement Table (LURT)0    A Table_B-2_(Cont.)__License_Unit_Requirement_Table_(LURT)_________   ;                       ________License_Types_by_Code________   A                       ________OpenVMS________  SIP__  _____LP____3   System MarketingA Model__________________A_____B____C_____D_______E______F______I__6  A VAXserver 3300,       NA     100  NA    NA      50      10     10  3400, 3500, 3600,4 3900, 4000-200,u 4000-300  A VAXserver 6000-210,   NA    1443  NA    NA     230     200    2004 6000-310  A VAXserver 6000-220,   NA    1737  NA    NA     230     400    400a 6000-320, 6000-410,e 6000-420  A VAXserver 6000-510    NA     600  NA    NA     230     400    400   A VAXserver 6000-520    NA     890  NA    NA     230     400    400C  A VAXserver 9000-110,   143    143  NA    NA     600     900    900d 9000-310  A VAXserver 9000-320    241    241  NA    NA     800    1200   1200V  A VAXserver 9000-330    330    330  NA    NA     800    1200   1200c  A VAXserver 9000-340    386    386  NA    NA     800    1200   1200xA Key_to_License_Type_Codes_and_Values_____________________________S  1   A-OpenVMS Capacity or OpenVMS Unlimited or Basel   B-OpenVMS Server   C-OpenVMS Concurrent userb   D-OpenVMS Workstations   E-System integrated products   F-Layered products   G-Reserved (not listed) !   H-OpenVMS reserved (not listed)_   I-Layered productsA __NA-Not_applicable______________________________________________i  # B-10  License Management Supplement_ _  _      E                                         License Management Supplement E                           B.3 License Management Facility (LMF) Notes6    /     B.3 License Management Facility (LMF) Notes   >           The following list is offered to help new users withB           some common concerns and questions regarding the License$           Management Facility (LMF).  C           o  If you do not have a valid OpenVMS VAX license that is D              registered and activated, the system displays a warningC              message as part of system startup and restricts system 1              use to the operator's console, OPA0.A  A           o  If a checksum error is displayed when you register aAD              license, check all the fields of data that you entered,+              including the checksum itself.8  ?           o  After your PAKs are registered, they are activated4C              (loaded) automatically as part of each system startup._  A           o  If an OpenVMS VAX availability license is registered >              with insufficient license units for the specified@              VAX computer, the system displays a warning messageB              at system startup but allows normal system use at the               console level only.  =           o  If an OpenVMS VAX activity license is registeredi>              with insufficient license units to meet your userD              requirements, the system displays the following message8              when the user (process) attempts to log in:  V              %LICENSE-F-EXCEEDED, licensed product has exceeded current license limits  @              A user can always log in to the operator's console,              OPA0, however.   @           o  The default LICENSE database is located in the fileA              SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB. You can move the_?              database, although Compaq does not recommend doing A              so. If you move the database, you must either define4@              the logical name LMF$LICENSE at the system level toD              point to the new database or use the /DATABASE=filespec=              qualifier with all LICENSE commands. To redirect A              LMF to another database location on a more permanent C              basis, add the following line to the command procedure0(              SYS$MANAGER:SYLOGICALS.COM:  J              $ DEFINE/SYSTEM LMF$LICENSE device:[directory]LMF$LICENSE.LDB  E                                    License Management Supplement B-11     A       License Management Supplement + B.3 License Management Facility (LMF) Notes     :          If you specify a device other than SYS$SYSDEVICE,8          you must also mount the specified disk from the*          SYLOGICALS.COM command procedure.  @       o  Each VAX VMS and OpenVMS VAX Base license is restricted=          to a single node for permanent PAKs. You must assign_;          a System Communications Services (SCS) name to theS:          license when you register with the VMSLICENSE.COM7          command procedure, or you must enter a LICENSEe<          MODIFY/INCLUDE=node-name command after you register?          the license. Although you can successfully activate any?          unassigned OpenVMS VAX license on a standalone system, =          you cannot activate one in a VAXcluster environment.   ?          ________________________ Note ________________________   =          The SCS node name is not necessarily the DECnet nodeq9          name. SCSNODE is a system parameter; it can be a_,          maximum of 6 alphabetic characters.  ?          ______________________________________________________   ) B.4  Volume Shadowing for OpenVMS License_  <       The following paragraphs describe Volume Shadowing for       OpenVMS licenses._   B.4.1  When to Register   9       After you install OpenVMS VAX Version 7.3, you must7?       register your Volume Shadowing for OpenVMS license beforeV@       you can use the volume shadowing software. If you upgraded?       to OpenVMS VAX Version 7.3, you do not need to reregister        this license.   5 B.4.2  Volume Shadowing Software Phase I and Phase II   9       In the past, volume shadowing has offered two modes 6       of operation: phase I and phase II. The original:       implementation of volume shadowing, phase I, was HSC>       controller-based. The newer implementation, phase II, is>       host-based and provides performance superior to phase I.  A       With the release of OpenVMS VAX Version 6.2, phase I volumes;       shadowing is no longer available. Refer to the Volumen@       Shadowing for OpenVMS manual for instructions about moving       from phase I to phase II.   # B-12  License Management Supplemente    d      E                                         License Management SupplementeE                              B.4 Volume Shadowing for OpenVMS License          B.4.3 Types of Licenses   >           Two types of volume shadowing licenses are valid for"           OpenVMS VAX Version 7.3:  =           o  Capacity license - If you are using this type oftB              license, you must have one license for each node in a5              cluster that is accessing shadowed data.   =           o  Per-disk license - If you are using this type of >              license, you must have one license for every disk)              contained in the shadow set.A  B              For information about OpenVMS VAX Version 7.3 changes<              to per-disk licensing for volume shadowing, see              Section 1.1.2.   C           Refer to the Volume Shadowing for OpenVMS manual for more /           information about these two licenses.   0     B.5 Other System Integrated Product Licenses  =           After you install OpenVMS VAX Version 7.3, you must A           register licenses for any system integrated product. If3E           you upgraded to OpenVMS VAX Version 7.3, you do not need to =           reregister licenses for system integrated products.u                                      E                                    License Management Supplement B-13n a  s                    E                                                                     C E     _________________________________________________________________s  E                                 Booting from [SYSF] During an Upgrade          C.1 Booting Procedures  @           You must boot from the [SYSF] root during phases 2, 3,A           and 4 of the upgrade procedure. Different VAX computerstA           require that you use different booting procedures. This B           appendix describes how to boot the various VAX computers           from [SYSF].  @           Go to the section that describes your VAX computer andA           follow the instructions for booting from [SYSF]. If you_C           need more information about booting, refer to the upgradep<           and installation supplement for your VAX computer.  +     C.1.1 MicroVAX and VAXstation Computers_  B           The information in this section applies to the following           VAX computers:  >              VAXstation II, VAXstation II/GPX, and MicroVAX II.              VAXstation 2000 and MicroVAX 20005              VAXstation 3100 and MicroVAX 3100 series %              VAXstation 3200 and 35000%              VAXstation 3520 and 35406              VAXstation 4000.              VAXft 110, 310, 410, 610, and 612<              MicroVAX 3300, 3400, 3500, 3600, 3800, and 3900  <           To boot from [SYSF], enter the BOOT command in the,           following format and press Return:  $           >>> B/F0000000 device-name  C           Substitute the device name of the system disk for device-6           name.0    E                             Booting from [SYSF] During an Upgrade C-1_ _  S      % Booting from [SYSF] During an Upgrade  C.1 Booting Procedures    ; C.1.2  VAX 8530, 8550, 8810 (8700), 8820-N (8800) Computers-  7       To boot from [SYSF], use the following procedure:v  9       1. Press Ctrl/P. Enter the following command at thee4          console-mode prompt (>>>) and press Return:            >>> HALT_  @       2. Enter the BOOT command at the console-mode prompt (>>>)!          in the following format:e             >>> B dddn /R5:F0000000  A          Substitute BCI, BDA, or UDA for ddd. Substitute the unit ;          number of the drive holding the system disk for n.h  ) C.1.3  VAX 8820, 8830, and 8840 Computers   7       To boot from [SYSF], use the following procedure:g  ?       1. Enter the following command at the PS-OS-0> prompt andI          press Return:            PS-OS-0> HALT/CPU=ALL  >       2. Enter the BOOT command at the PS-CIO-0> prompt in the          following format:  &          PS-CIO-0> B dddn /R5=F0000000  ;          Substitute BCI or BDA for ddd. Substitute the unit ;          number of the drive holding the system disk for n.   7 C.1.4  VAX-11/750, 8200, 8250, 8300, and 8350 Computersn  ;       To boot from [SYSF], create a command procedure named /       SYFBOO.CMD before the upgrade is started.i  8       To create SYFBOO.CMD, use the following procedure:  ?          ________________________ Note ________________________e  ;          This procedure assumes that you have installed ands?          booted the OpenVMS VAX operating system and are loggeds"          in to the SYSTEM account.  ?          ______________________________________________________n  &       1. Log in to the SYSTEM account.  ;       2. Make sure that the console media is in the consoleu          drive.u  * C-2  Booting from [SYSF] During an Upgrade ,  e      E                                 Booting from [SYSF] During an UpgradeaE                                                C.1 Booting Procedurest    B           3. To connect the console drive to the system, enter the@              following commands and press Return after each one:  $              $ RUN SYS$SYSTEM:SYSGEN$              SYSGEN> CONNECT CONSOLE              SYSGEN> EXITE  B           4. Use the Exchange utility to copy the appropriate bootE              command procedure from the console media to your currentmC              directory on the system disk. If the system disk is onsD              an HSC drive and you have created DEFBOO.CMD, enter the0              following command and press Return:  .              $ EXCHANGE COPY CSA1:DEFBOO.CMD *  A              On the VAX-11/750 computer, if the system disk is ond@              a local drive, copy the boot command procedure that>              matches the drive that holds the system disk. ForA              example, suppose the system disk is on an RP06 drive D              and has a controller designation of A and a unit numberB              of one. Enter the following command and press Return:  .              $ EXCHANGE COPY CSA1:DA1BOO.CMD *  =           5. Edit the boot command procedure. Change the linet@              that deposits a value in register 5 (R5). This lineD              contains the comment !software boot flags. The value isA              a hexadecimal number with eight digits. For example:n  -              D/G R5 0    !software boot flagsc  C              Change the left-most digit of the value to reflect theuD              name of the root directory from which you want to boot.A              For example, to boot from the [SYSF] root directory,c(              change the line as follows:  ;              D/G/L R5 F0000000     !designated root is SYSFn  A           6. Rename the boot command procedure to SYFBOO.CMD. For_B              example, if the boot command procedure is DEFBOO.CMD,:              enter the following command and press Return:  +              $ RENAME DEFBOO.CMD SYFBOO.CMD   D           7. Use the Exchange utility to copy SYFBOO.CMD back to theA              console media. Enter the following command and pressp              Return:  7              $ EXCHANGE COPY SYFBOO.CMD CSA1:SYFBOO.CMD   E                             Booting from [SYSF] During an Upgrade C-3t    n      % Booting from [SYSF] During an Upgrader C.1 Booting Procedures    ?       8. When the copy operation completes, enter the followingf"          command and press Return:            $ DISMOUNT CSA1  >       9. To secure the console media from unauthorized access,?          you must enter the following command and press Return:m  5          $ MOUNT/FOREIGN/SYSTEM/NOWRITE/NOASSIST CSA1h  7       To boot from [SYSF], use the following procedure:o  @       1. Make sure the console media is in the console drive. On?          the VAX-11/750 computers, make sure the keylock switchr@          is set to LOCAL. Set the BOOT DEVICE switch to position          A.,  ?          On the VAX 8200 computer, set the upper keylock switcht8          to ENABLE and the lower keylock switch to HALT.         2. Press Ctrl/P.  @       3. On the VAX-11/750 computer, enter the following command          and press Return:            >>> B/800 DDA0i  A          On the VAX 8200 computer, enter the following command at 8          the console-mode prompt (>>>) and press Return:            >>> B/R5:800 CSA1  <       4. At the BOOT58> prompt, enter the following command:            BOOT58> @SYFBOO.CMD  ; C.1.5  VAX-11/730, 11/780, 11/785, 8600, and 8650 Computersl  ;       To boot from [SYSF], create a command procedure named ?       SYFBOO.CMD (for VAX-11/730, 11/780, and 11/785 computers)d@       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:  ?          ________________________ Note ________________________-  ;          This procedure assumes that you have installed and1?          booted the OpenVMS VAX operating system and are loggedu"          in to the SYSTEM account.  ?          ______________________________________________________c  * C-4  Booting from [SYSF] During an Upgrade           E                                 Booting from [SYSF] During an Upgrade E                                                C.1 Booting Procedures       *           1. Log in to the SYSTEM account.  ?           2. Make sure that the console media is in the console D              drive. On the VAX 8600 computer, make sure the TERMINAL,              CONTROL switch is set to LOCAL.  >           3. To connect the console drive, enter the following6              commands and press Return after each one:  $              $ RUN SYS$SYSTEM:SYSGEN$              SYSGEN> CONNECT CONSOLE              SYSGEN> EXITr  =           4. Use the Exchange utility to copy DEFBOO.CMD (for2D              VAX-11/730, 11/780, and 11/785 computers) or DEFBOO.COME              (for VAX 8600 and 8650 computers) from the console media A              to your current directory on the system disk. On the D              VAX-11/780, 11/785, and 8600 computers, enter a command7              similar to the following and press Return:o  .              $ EXCHANGE COPY CSA1:DEFBOO.CMD *  D              On the VAX-11/730 computer, enter the following command              and press Return:  .              $ EXCHANGE COPY CSA2:DEFBOO.CMD *  @           5. Edit DEFBOO.CMD or DEFBOO.COM. Change the line thatD              deposits a value in register 5 (R5). On the VAX-11/730,A              11/780, and 11/785 computers, this line contains thecE              comment !software boot flags. On the VAX 8600, this line C              contains the comment !Use R5 for optional boot control3B              flags [SYSB.]. The value is a hexadecimal number with%              eight bits. For example:3  9              DEPOSIT R5 10000000     !software boot flagsm  C              Change the left-most digit of the value to reflect thepD              name of the root directory from which you want to boot.A              For example, to boot from [SYSF], change the line asa              follows:   9              DEPOSIT R5 F0000000     !software boot flags   >           6. Rename DEFBOO.CMD to SYFBOO.CMD (or DEFBOO.COM to%              SYFBOO.COM), as follows:   +              $ RENAME DEFBOO.CMD SYFBOO.CMDo  E                             Booting from [SYSF] During an Upgrade C-5t t  f      % Booting from [SYSF] During an Upgraded C.1 Booting Procedures    7       7. Use the Exchange utility to copy SYFBOO.CMD orm<          SYFBOO.COM to the console media. On the VAX-11/780,?          11/785, and 8600 computers, enter a command similar tot          the following:d  3          $ EXCHANGE COPY SYFBOO.CMD CSA1:SYFBOO.CMDh  @          On the VAX-11/730 computer, enter the following command"          and press the Return key:  3          $ EXCHANGE COPY SYFBOO.CMD CSA2:SYFBOO.CMDf  >       8. When you are finished, enter a command similar to the$          following and press Return:            $ DISMOUNT CSA1  >       9. To secure the console media from unauthorized access,>          you must enter a command similar to the following and          press Return:  5          $ MOUNT/FOREIGN/SYSTEM/NOWRITE/NOASSIST CSA1e  >       To boot from [SYSF] during an upgrade, use the following       procedure:  @       1. Make sure the console media is in the console drive. On@          the VAX-11/730, 11/780, and 11/785 computers, make sure=          the keylock switch is set to LOCAL. On the VAX 8600,_?          make sure the TERMINAL CONTROL switch is set to LOCAL.r  :       2. Press Ctrl/P. On the VAX-11/780, 11/785, and 8600>          computers, enter the HALT command at the console-mode'          prompt (>>>) and press Return:_            >>> HALT_  @       3. Use SYFBOO.CMD to boot from [SYSF]. Enter the following"          command and press Return:            >>> B SYF   C.1.6  VAX 6000 Series  7       To boot from [SYSF], use the following procedure:   ?       1. If you have a CIBCA-A adapter and are booting over the =          CI, insert the console tape cartridge in the consolee          drive.   8       2. Press Ctrl/P to put the system in console mode.  * C-6  Booting from [SYSF] During an Upgrade t  e      E                                 Booting from [SYSF] During an UpgradeTE                                                C.1 Booting Procedurest    <           3. Enter the BOOT command in the following format:  J              >>> BOOT /R5:F0000000  /XMI:a  /BI:b  [/R3:c]  [/NODE:d]  DUu                where:s  <              o  a is the XMI node number of the system disk.  >              o  b is the VAXBI node number of the system disk.  E              o  c pertains to volume shadowing. This qualifier is notAC                 required unless you are using volume shadowing. ForiC                 more information, refer to the Volume Shadowing fori                 OpenVMS manual.r  D              o  d is the HSC node number of the node being accessed.?                 The /NODE qualifier is not necessary if you arerA                 booting from a local disk. The HSC node number is:D                 in hexadecimal. You can deposit a maximum of two HSC9                 node numbers (if two HSCs are available).   D              o  u is the unit number of the drive holding the system                 disk.r  D              For example, suppose you want to boot from [SYSF] on anC              HSC disk with a unit number of one and your system hasg)              the following configuration:i  =              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.c  B              o  The disk is available to two HSCs, node numbers 0E                 and 02.t  :              Enter the following command and press Return:  :              >>> BOOT/R5:F0000000/XMI:3/BI:2/NODE:0E02 DU1            E                             Booting from [SYSF] During an Upgrade C-7R r         % Booting from [SYSF] During an Upgrade  C.1 Booting Procedures     C.1.7  VAX 9000 Series  ?       The upgrade procedure automatically updates DEFBOO.CMD ton?       boot from [SYSF]. If you want to boot a VAX 9000 computerA>       manually from [SYSF] however, you must set up DEFBOO.CMD<       to boot from the system disk and perform the following       procedure:  3       1. Press Ctrl/P to obtain the console prompt.   +       2. Enter the following BOOT commands:             >>> I/K          >>> BOOT/NOSTART            >>> DEPOSIT R5 F0000000          >>> CONTINUEo  <       3. If you set up DEFBOO.CMD properly, the system boots@          from the SYSF directory on the system disk, and you can-          continue with the upgrade procedure.r  4          If the system does not boot, enter the SHOWA          CONFIGURATION console command and verify that DEFBOO.CMDVA          contains the correct information for your configuration. ?          For more information, refer to the OpenVMS VAX Upgrade 6          and Installation Supplement: VAX 9000 Series.                                      * C-8  Booting from [SYSF] During an Upgrade C  /                    E                                                                     DRE     _________________________________________________________________,  E                                       OpenVMS VAX Save Set Subclassesa    B           This appendix lists the file subclasses contained in the           following save sets:  (           o  VMS073.C - Library save set  )           o  VMS073.D - Optional save set5  -           o  VMS073.E - Help Message save set   ;           o  VMS073.F - OpenVMS Management Station save set1       D.1 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 Loadingy              o  Programming support  (                 Debugger utility (DEBUG)9                 Image Dump utility (ANALYZE/PROCESS_DUMP)_B                 RMS Analyze and FDL Editor utilities (ANALYZE/RMS,                 ANALYZE/FDL))                 Message utility (MESSAGE) 4                 Object and Shareable Image libraries                 MACRO libraries                  MACRO assembler 4                 SDL intermediary form of STARLET.MLB&                 Fortran required files&                 VAX C object libraries6                 VMS text libraries of Ada declarations  )           o  OpenVMS RMS journaling files   E                                   OpenVMS VAX Save Set Subclasses D-1m d  n       OpenVMS VAX Save Set Subclasses  D.1 Save Set C SubclassesG    #       o  System programming support   6             Files-11 ODS-1, ISO 9660, High Sierra ACPs             Monitor utility(             Delta debugger9             System Dump Analyzer utility (ANALYZE/SYSTEM,              ANALYZE/CRASH).             System Symbol Table file (SYS.STB),             Miscellaneous symbol table files  "       o  Secure user's environment  .             File Access Control List utilities+             Print and Batch Queue utilities .             Input Queue Symbiont (Card Reader)3             Accounting Log Report Generator utilitye             DECdtm         o  Utilities               Mail utility             Dump utility             Runoff utility             Phone utilityn              OpenVMS Help library$             Foreign Terminal Support1             LAT-11 terminal server (via Ethernet)p             Standalone backup >             Error Log Report Generator utility (ANALYZE/ERROR)             DECTPU&             Terminal Fallback Facility             TECO Editor              EDT documentations0             National Character Set utility (NCS)8             C language internationionalization utilities  $       o  OpenVMS workstation support  &             Workstation device support            $ D-2  OpenVMS VAX Save Set Subclasses r  w      E                                       OpenVMS VAX Save Set Subclasses E                                             D.2 Save Set D Subclasses0         D.2 Save Set D Subclasses   E           The following files are contained in the Optional save set:F              o  Miscellaneous files                   System map                 LPA-11 support  !           o  BLISS required filesr  5           o  UETP (the User Environment Test Package)r             o  Example files       D.3 Save Set E Subclassesl  D           The following files are contained in the Help Message save           set:  "           o  Help Message database       D.4 Save Set F Subclasses   E           The following files are contained in the OpenVMS ManagementM           Station save set:7  9           o  OpenVMS Management Station software PC filest                                  E                                   OpenVMS VAX Save Set Subclasses D-3  e                       E                                                                     E E     _________________________________________________________________   E                        DECwindows Display Server and Fonts Componentst    @           This appendix provides a list of files provided by theE           DECwindows base and workstation support components includedd.           on the OpenVMS VAX distribution kit.       E.1 Table of Components   ?           Table E-1 contains the name of the DECwindows display >           server and fonts components, the directory where the=           component can be found, a brief description of what @           the component does, and one of the following component           classifications:  ?           o  BASE - Indicates that the component is part of all B              installations. BASE Component Class files are located!              in savesets B and C.a  =           o  WS - Indicates that the component is part of thei>              workstation support. WS Component Class files are"              located in saveset D.  @           o  FONT - Indicates the component is part of the fontsA              component. FONT Component Class files are located in/=              savesets E (75 DPI fonts) and C (100 DPI fonts).]  E     Table_E-1_DECwindows_Display_Server_and_Fonts_Components_________   H                                                                ComponentE     File______________________Purpose__________________________Class_t  E     __________________________Files_in_DECW$KEYMAP_Directory_________   C     DECW$KEYMAP                                                BASEs  E                                              (continued on next page)I    E                    DECwindows Display Server and Fonts Components E-1a i         . DECwindows Display Server and Fonts Components E.1 Table of Componentsa    A Table_E-1_(Cont.)__DECwindows_Display_Server_and_Fonts_Componentsd  D                                                            ComponentA File______________________Purpose__________________________Class_N  A __________________________Files_in_SYS$LOADABLE_IMAGES_Directory_r  = GAADRIVER.EXE             VAXstation II/GPX driver         WSd  = GABDRIVER.EXE             VAXstation 2000/GPX driver       WSe  = GBBDRIVER.EXE             VAXstation 35x0 driver           WSe  = GCADRIVER.EXE             VAXstation II monochrome         WSk'                           device drivero  = GCBDRIVER.EXE             VAXstation 2000 monochrome       WSi'                           device driver   = GEBDRIVER.EXE             Scanproc graphics device         WSk                            driver  = GECDRIVER.EXE             Spxg/gt graphics device driver   WSh  = GFBDRIVER.EXE             Low-cost graphics device         WS                             driver  = IEDRIVER.EXE              Input extension driver           WSg  = IKDRIVER.EXE              Keyboard decoder driver          WSM  = IMDRIVER.EXE              Mouse decoder driver             WSo  = INDRIVER.EXE              Common input function driver     WSr  ? WSDRIVER.EXE              Set display driver               BASEX  A _________________________________________________________________BA __________________________Files_in_SYS$SYSTEM_Directory__________c  ? DECW$FONTCOMPILER.EXE     Font compiler image              FONTO  ? DECW$MKFONTDIR.EXE        Font utility to generate list    FONT ,                           of fonts and paths  = DECW$SERVER_MAIN.EXE      Server main image                WSo  ? DECW$SETSHODIS.EXE        SHOW DISPLAY command image       BASE>  A _________________________________________________________________ A __________________________Files_in_DECW$FONT_Directory___________r  = See VMS DECwindows Xlib   DECwindows fonts                 WSe Programming Volume  B                                           (continued on next page)  3 E-2  DECwindows Display Server and Fonts Components            E                        DECwindows Display Server and Fonts Components E                                               E.1 Table of Componentso    E     Table_E-1_(Cont.)_DECwindows_Display_Server_and_Fonts_Components_B  H                                                                ComponentE     File______________________Purpose__________________________Class__  E     __________________________Files_in_DECW$EXAMPLES_Directory_______   C     DECW$FONT_ALIAS_          Example alias file for Charter   FONT #     CHARTER.DAT               fontsl  C     DECW$FONT_ALIAS_          Example alias file for 100 dpi   FONTV+     CHARTER_100DPI.DAT        Charter fontsS  C     DECW$FONT_ALIAS_          Brief alias name list for        FONT +     FILENAMES.DAT             shipped fontse  C     DECW$FONT_ALIAS_          Example alias file for           FONTh(     KANJI.DAT                 Kanjifonts  C     DECW$FONT_ALIAS_          Example alias file for Lucida    FONTi#     LUCIDA.DAT                fonts   C     DECW$FONT_ALIAS_LUCIDA_   Example alias file for 100 dpi   FONTl*     100DPI.DAT                Lucida fonts  E     _________________________________________________________________UE     __________________________Files_in_SYS$LIBRARY_Directory_________   A     DECW$DRIVER.MLB           Driver macro library             WS   C     DECW$FONTCOMPILER.CLD     CLD for font compile commands    FONT   A     DECW$SERVER_DDX_GA.EXE    Server color device support      WSi-                               shareable image   A     DECW$SERVER_DDX_GB.EXE    Server color device support      WSt-                               shareable imaget  A     DECW$SERVER_DDX_GC.EXE    Server monochrome device         WS 5                               support shareable image   A     DECW$SERVER_DDX_GE.EXE    Server scanproc device-          WS 7                               dependent shareable imageb  A     DECW$SERVER_DDX_GF.EXE    Server low-cost graphics         WSe8                               device-dependent shareable#                               imager  A     DECW$SERVER_DIX.EXE       Server device independent        WS %                               supportS  E                                              (continued on next page)   E                    DECwindows Display Server and Fonts Components E-3i u  i      . DECwindows Display Server and Fonts Components E.1 Table of Componentsb    A Table_E-1_(Cont.)__DECwindows_Display_Server_and_Fonts_Componentse  D                                                            ComponentA File______________________Purpose__________________________Class_h  A __________________________Files_in_SYS$LIBRARY_Directory_________e  = DECW$SERVER_XINPUT_       Input extension for handling     WSp3 IE.EXE                    nonstandard input deviceso  ? DECW$SESSIONSHRP.EXE      Support routines for             BASE 4                           DECwindows Session Manager  = DECW$SVEXT_ADOBE_DPS_     Display PostScript server        WSa) EXTENSION.EXE             extension imagea  = DECW$SVEXT_D2DX_          DECwindows 2D extensions         WSi EXTENSIONS.EXE  = DECW$SVEXT_DEC_           Input and event recording and    WSX, XTRAP.EXE                 playback extension  = DECW$SVEXT_MULTI_         DECwindows multibuffering        WS # BUFFERING.EXE             extension   = DECW$SVEXT_X3D_PEX.EXE    Phigs Extension to X (PEX) for   WS                            3D  = DECW$SVEXT_X3D_PEX_       PEX for 35x0 systems             WSl GB.EXE  = DECW$SVEXT_X3D_PEX_GB_    PEX microcode for 35x0 systems   WSt	 UCODE.EXE   = DECW$SVEXT_X3D_PEX_       PEX for scanproc systems         WSm GE.EXE  = DECW$SVEXT_X3D_PEX_       PEX for scanproc systems with    WSb, STP.EXE                   geometry processor  = DECW$SVEXT_X3D_PEX_STP_   PEX microcode for scanproc       WS / UCODE.EXE                 systems with geometryl#                           processore  = DECW$SVEXT_X3D_PEX_       PEX color frame buffer           WSe( VCFB.EXE                  (software PEX)  = DECW$SVEXT_XIE.EXE        DECwindows imaging extension     WS   = DECW$SVEXT_               DECwindows input extension       WS  XINPUTEXTENSION.EXE   B                                           (continued on next page)  3 E-4  DECwindows Display Server and Fonts Components_ _  _      E                        DECwindows Display Server and Fonts ComponentssE                                               E.1 Table of Componentsi    E     Table_E-1_(Cont.)_DECwindows_Display_Server_and_Fonts_Components_c  H                                                                ComponentE     File______________________Purpose__________________________Class_i  E     __________________________Files_in_SYS$LIBRARY_Directory_________   C     DECW$TRANSPORT_           Common transport shareable       BASE #     COMMON.EXE                imagel  C     DECW$TRANSPORT_           DECnet transport image           BASEi     DECNET.EXE  C     DECW$TRANSPORT_           Local transport image            BASEa
     LOCAL.EXEc  C     DECW$TRANSPORT_           TCP/IP transport image           BASE 
     TCPIP.EXEe  C     DECW$XPORTCOM.H           Common transport definitions     BASEs  C     DECW$XPORTCOM.MAR         Common transport definitions     BASEn  C     DECW$XPORTCOM.R32         Common transport definitions     BASET  C     DECW$XPORTDEF.H           Transport definitions            BASE   C     DECW$XPORTDEF.MAR         Transport definitions            BASEe  C     DECW$XPORTDEF.R32         Transport definitions            BASE   C     DECW$XPORTMAC.R32         Transport BLISS macros           BASEp  C     DECW$XPORTMSG.R32         Transport message symbols        BASEi  A     XDPS$MASTERDPSVM.DAT      Display PostScript support       WS "                               file  E                                              (continued on next page)a            E                    DECwindows Display Server and Fonts Components E-5i           . DECwindows Display Server and Fonts Components E.1 Table of Components     A Table_E-1_(Cont.)__DECwindows_Display_Server_and_Fonts_Components   D                                                            ComponentA _________________________________________________________________   A __________________________Files_in_SYS$MANAGER_Directory_________   ? DECW$DEVICE.COM           Device detection and             BASEA'                           configurationP  = DECW$DEVICE_GE.COM        Scanproc device detection and    WSr'                           configuration   = DECW$DEVICE_GF.COM        Low-cost graphics device         WS 5                           detection and configurationi  = DECW$DEVICE_GG.COM        Scanproc turbo device            WSi5                           detection and configurationi  = DECW$RGB.DAT              Definitions of the color names   WS %                           used by thev.                           XStoreNamedColor and3                           XAllocNamedColor requests   = DECW$STARTSERVER.COM      Server initialization and        WS !                           startup   A _________________________________________________________________sA __________________________Files_in_SYS$MESSAGE_Directory_________n  ? DECW$TRANSPORTMSG.EXE     Transport message image          BASEp  A __________________________________________________________________A __________________________Files_in_SYS$UPDATE_Directory__________S  ? DECW$MKFONTDIR.COM        Command file to invoke           FONTm1                           DECW$MKFONTDIR.EXE fontEA __________________________utility________________________________               3 E-6  DECwindows Display Server and Fonts Componentsm                         E                                                                     F_E     __________________________________________________________________  E                                          NEW_OVER and NEW_UNDER Filesn    B           This appendix lists files installed either over or under+           existing files during an upgrade.n  !     F.1 Where Files Are Installedw  A           During an upgrade, the procedure replaces certain files D           that exist on your system with new versions of those files@           from the OpenVMS VAX distribution kit. For some systemE           files, the upgrade procedure does not replace your existing C           system files, which might contain customizations for yourtA           site. Instead, the procedure retains your existing fileaD           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 the B           new files provided by OpenVMS VAX Version 7.3. 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 you C           specify. This output file has the default file type .DIF. C           For more information about using the DIFFERENCES command, .           refer to the OpenVMS DCL Dictionary.  C           New files that the procedure installs at a version numberiE           higher than your existing files are referred to as new_over E           files. You must use these files at least until you completeLC           the upgrade. After you have upgraded your system, you can 1           add your customizations to these files.       E                                      NEW_OVER and NEW_UNDER Files F-1r v          NEW_OVER and NEW_UNDER Files F.1 Where Files Are Installed     <       New files installed at a version number lower than the=       existing files are referred to as new_under files. This >       allows you to continue to use your existing files during       and after the upgrade.  =       If you purge a new_over file, you are left with the newr?       version of the file provided by the distribution kit, andi@       any customizations you made to the existing file are lost.?       If you purge a new_under file, you are left with the file &       that existed before the upgrade.  <       In addition to the new_over and new_under files, there?       are certain files that are intended to contain your site-sA       specific modifications. During an upgrade, the old versions =       of these files are retained if they were present beforeC;       the upgrade. The new version of the file is installed <       only if no old version is present on your system. With@       the exception of TFF$STARTUP.COM, there is a corresponding@       .TEMPLATE file for each of the site-specfic files. The new=       version of the .TEMPLATE file replaces the old version.p   F.1.1  NEW_OVER Files   >       During an upgrade, the following new files are installed9       over (that is, at a version number higher than) theE       existing files:r            [SYSEXE]SHUTDOWN.COMp          [SYSEXE]STARTUP.COM          [SYSHLP]HELPLIB.HLB          [SYSLIB]ADARTL.EXET          [SYSLIB]BASRTL.EXE           [SYSLIB]BASRTL2.EXE          [SYSLIB]BLAS1RTL.EXE           [SYSLIB]COBRTL.EXEn          [SYSLIB]DBLRTL.EXE           [SYSLIB]DCLTABLES.EXE          [SYSLIB]ENCRYPSHR.EXE          [SYSLIB]FORRTL.EXE           [SYSLIB]FORRTL2.EXE          [SYSLIB]IMAGELIB.OLBE          [SYSLIB]LBRSHR.EXEE          [SYSLIB]LIBRTL.EXE           [SYSLIB]LIBRTL2.EXE          [SYSLIB]MTHRTL.EXEe          [SYSLIB]PASRTL.EXE   ! F-2  NEW_OVER and NEW_UNDER Filesd o  5      E                                          NEW_OVER and NEW_UNDER FilessE                                         F.1 Where Files Are Installeds                  [SYSLIB]PLIRTL.EXE               [SYSLIB]PPLRTL.EXEW              [SYSLIB]RPGRTL.EXEd              [SYSLIB]SCNRTL.EXEX               [SYSLIB]STARLET.OLB!              [SYSLIB]UVMTHRTL.EXEr               [SYSLIB]VAXCRTL.EXE!              [SYSLIB]VAXCRTLG.EXE "              [SYSLIB]VBLAS1RTL.EXE              [SYSLIB]VMSRTL.EXE                [SYSLIB]VMTHRTL.EXE"              [SYSMGR]DBLSTRTUP.COM%              [SYSMGR]WELCOME.TEMPLATE        F.1.2 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:d  ,              [SYS$LDR]VMS$SYSTEM_IMAGES.DATA.              [SYS$STARTUP]ESS$LAST_STARTUP.DAT)              [SYS$STARTUP]VMS$LAYERED.DAT_*              [SYSEXE]VMS$IMAGE_VERSION.DAT#              [SYSLIB]CDA$ACCESS.EXE               [SYSLIB]CDDSHR.EXEC'              [SYSLIB]DECW$DWTLIBSHR.EXEu)              [SYSLIB]DECW$PRINTWGTSHR.EXE %              [SYSLIB]DECW$XLIBSHR.EXES%              [SYSLIB]EPC$FACILITY.TLBW               [SYSLIB]EPC$SHR.EXE              [SYSLIB]UISSHR.EXEO               [SYSMSG]EPC$MSG.EXE,              [SYSLIB]XDPS$DPSBINDINGSSHR.EXE*              [SYSLIB]XDPS$DPSCLIENTSHR.EXE'              [SYSLIB]XDPS$DPSLIBSHR.EXEr               [SYSLIB]XNL$SHR.EXE0              [SYSMGR]AMDS$DRIVER_ACCESS.TEMPLATE+              [SYSMGR]AMDS$LOGICALS.TEMPLATE             E                                      NEW_OVER and NEW_UNDER Files F-3X T  .       NEW_OVER and NEW_UNDER Files F.1 Where Files Are InstalledT     F.1.3  Site-Specific Files  ?       The following files are intended to contain site-specifice5       modifications. Note that, with the exception of >       TFF$STARTUP.COM, there is a corresponding .TEMPLATE file?       for each of these files. The new version of the .TEMPLATEO$       file replaces the old version.  '          [SYS$STARTUP]ICC$SYSTARTUP.COM           [SYSEXE]SYSUAF.DATb+          [SYSMGR]AGEN$NEW_NODE_DEFAULTS.DAT 0          [SYSMGR]AGEN$NEW_SATELLITE_DEFAULTS.DAT"          [SYSMGR]LAT$SYSTARTUP.COM          [SYSMGR]LOGIN.COM          [SYSMGR]SYCONFIG.COMa          [SYSMGR]SYLOGICALS.COM           [SYSMGR]SYLOGIN.COM"          [SYSMGR]SYPAGSWPFILES.COM          [SYSMGR]SYSECURITY.COM           [SYSMGR]SYSHUTDWN.COM"          [SYSMGR]SYSTARTUP_VMS.COM           [SYSMGR]TFF$STARTUP.COM                                              ! F-4  NEW_OVER and NEW_UNDER Filese    _                    E                                                                     G_E     _________________________________________________________________e  E                           Preparing to Use OpenVMS Management Stationt    C           During the OpenVMS installation or upgrade procedure, the E           OpenVMS Management Station server software is automatically-0           installed on your OpenVMS system disk.  A           If you accepted the default options the PC client filesc>           will be located in SYS$COMMON:[TNT.CLIENT]. If theseB           files are deleted from your system you can either tailorB           (see Chapter 10) them back on, or download them from the           following location:a  P         http://www.openvms.compaq.com/openvms/products/argus/index.html#ordering  :           If the TNT$* server files have been deleted from9           SYS$SYSTEM, you can recover the server files by_4           reinstalling the OpenVMS operating system.  @           After you have ensured that OpenVMS Management StationE           software is installed on your system, follow the procedures_%           described in this appendix._  %     G.1 Preparing Your OpenVMS SystemS  @           You must prepare your OpenVMS system to run the serverE           software so that your system can properly interact with theRD           PC running the client software. The procedures include the           following:  C           o  Set up within a mixed-architecture cluster environment               (if applicable).   -           o  Start the server on other nodes._  5           o  Update the printer and storage database._  #           o  Edit the system files.   D           o  Allow OpenVMS Management Station to control the printer%              and storage environment.   6           o  Keep your printer environment up to date.  E                       Preparing to Use OpenVMS Management Station G-1o u  r      + Preparing to Use OpenVMS Management Stationr! G.1 Preparing Your OpenVMS Systemf    4       o  Check if running third-party TCP/IP stacks.          o  Recover from a failure.  '       o  Determine and report problems.t  = G.1.1  Setting Up in a Mixed-Architecture Cluster Environmentf  ;       The OpenVMS Management Station server creates severalx       configuration files:         o  TNT$UADB.DATm         o  TNT$ACS.DAT  ,       o  TNT$JOURNAL.TNT$TRANSACTION_JOURNAL         o  TNT$MONITOR.DAT  (       o  TNT$MONITOR.TNT$MONITOR_JOURNAL          o  TNT$EMERGENCY_MOUNT.COM  <       In a common-environment cluster with one common system@       disk, you use a common copy of each of these files located?       in the SYS$COMMON:[SYSEXE] directory on the common system A       disk, or on a disk that is mounted by all cluster nodes. No !       further action is required.t  :       However, to prepare a common user environment for an?       OpenVMS Cluster system that includes more than one common @       VAX system disk or more than one common Alpha system disk,3       you must coordinate the files on those disks.           The following rules apply:  =       o  Disks holding common resources must be mounted earlyi8          in the system startup procedure, such as in the"          SYLOGICALS.COM procedure.  =       o  You must ensure that the disks are mounted with each           cluster reboot.  -       Follow these steps to coordinate files:c  <       1. Decide where to locate the files. In a cluster with@          multiple system disks, system management is much easier@          if the common system files are located on a single disk#          that is not a system disk.e  0 G-2  Preparing to Use OpenVMS Management Station a  e      E                           Preparing to Use OpenVMS Management Station E                                     G.1 Preparing Your OpenVMS Systemi    =           2. Copy TNT$UADB.DAT, TNT$ACS.DAT, TNT$MONITOR.DAT,b<              TNT$MONITOR.TNT$MONITOR_JOURNAL, TNT$EMERGENCY_B              MOUNT.COM, and TNT$JOURNAL.TNT$TRANSACTION_JOURNAL to3              a location other than the system disk.f  D           3. Edit the file SYS$COMMON:[SYSMGR]SYLOGICALS.COM on eachB              system disk and define logical names that specify the2              location of the cluster common files.                Example  E              If the files will be located on $1$DJA16, define logical               names as follows:  +              $ DEFINE/SYSTEM/EXEC TNT$ACS -n7              _$ $1$DJA16:[VMS$COMMON.SYSEXE]TNT$ACS.DATT  E              TNT$EMERGENCY_MOUNT.COM will be created in SYS$SYSTEM orfC              in the directory pointed to by the TNT$ACS logical, if                the logical exists.  ,              $ DEFINE/SYSTEM/EXEC TNT$UADB -8              _$ $1$DJA16:[VMS$COMMON.SYSEXE]TNT$UADB.DAT  /              $ DEFINE/SYSTEM/EXEC TNT$JOURNAL -iO              _$ $1$DJA16:[VMS$COMMON.SYSEXE]TNT$JOURNAL.TNT$TRANSACTION_JOURNAL   /              $ DEFINE/SYSTEM/EXEC TNT$MONITOR -T;              _$ $1$DJA16:[VMS$COMMON.SYSEXE]TNT$MONITOR.DAT   6              $ DEFINE/SYSTEM/EXEC TNT$MONITORJOURNAL -K              _$ $1$DJA16:[VMS$COMMON.SYSEXE]TNT$MONITOR.TNT$MONITOR_JOURNALY  B           4. To ensure that the system disks are mounted correctly2              with each reboot, follow these steps:  D              1. Copy the SYS$EXAMPLES:CLU_MOUNT_DISK.COM file to theC                 [VMS$COMMON.SYSMGR] directory, and edit it for your                  configuration.  B              2. Edit SYLOGICALS.COM and include commands to mount,B                 with the appropriate volume label, the system disk,                 containing the shared files.    E                       Preparing to Use OpenVMS Management Station G-3T X         + Preparing to Use OpenVMS Management StationL! G.1 Preparing Your OpenVMS SystemB                 Example   A             If the system disk is $1$DJA16, include the following              command:  B          $  @SYS$SYSDEVICE:[VMS$COMMON.SYSMGR]CLU_MOUNT_DISK.COM -"          _$ $1$DJA16: volume-label  & G.1.2  Start the Server on Other Nodes  @       If you plan to run OpenVMS Management Station on more than?       one node in an OpenVMS Cluster without a reboot, you needr+       to start the software on those nodes.i  0       Use SYSMAN to start the server as follows:  $       $ @SYS$STARTUP:TNT$STARTUP.COM  @       Or, you can log into each node that shares the SYS$COMMON:0       directory and enter the following command:  $       $ @SYS$STARTUP:TNT$STARTUP.COM  >       If you are performing an upgrade or a reinstallation and:       OpenVMS Management Station is already running on the=       node, add the RESTART parameter to the startup command,        as follows:S  ,       $ @SYS$STARTUP:TNT$STARTUP.COM RESTART   G.1.3  Error Log Information  @       OpenVMS Management Station writes error log information to>       the file TNT$SERVER_ERROR.LOG. This error log is created>       in the SYS$SPECIFIC:[SYSEXE] directory. If you start the<       OpenVMS Management Station server on multiple nodes in=       a cluster, which is recommended, there will be multipleE       server error logs.  . G.1.4  Update the Printer and Storage Database  8       When you installed OpenVMS Management Station, the9       installation started the OpenVMS Management Station ;       server on the installation node. If this installation >       was an upgrade, the server converts the existing OpenVMSA       Management Station database to the V3.0 format. If this wasi?       a new installation, the server creates an initial versionU=       of the database file TNT$ACS.DAT and invokes the update_       functions automatically.  0 G-4  Preparing to Use OpenVMS Management Station L  S      E                           Preparing to Use OpenVMS Management Station E                                     G.1 Preparing Your OpenVMS SystemY    @           To complete the database, start the OpenVMS ManagementD           Station server on each node in your cluster. The instances@           of the server communicate with each other to determineD           device, queue, and volume information, and the server must@           be running on each node for this communication to take           place.       G.1.5 Edit the System Files_  =           To start the OpenVMS Management Station server frome@           your system startup files, insert one of the following@           commands into your system startup procedures (probablyE           SYS$MANAGER:SYSTARTUP_VMS.COM) after both the Queue Managern?           and network are started, but immediately prior to the "           ENABLE AUTOSTART/QUEUES.  B             ________________________ Note ________________________  ;             Remove any other invocations of TNT$STARTUP youC@             might have added in previous releases of the OpenVMS             Management Station./  =             OpenVMS Management Station cannot start until thegB             network has started. If you start your network using aA             batch process, OpenVMS Management Station might starteA             before the batch process completes and the network ise             started.  B             ______________________________________________________  E     _________________________________________________________________r#                  ParameterParameter E     Command______1________2________Description_______________________o  D     @TNT$STARTUP blank    N.A.     Starts the server. Does not startC                                    printer queues or mount volumes.o  D     @TNT$STARTUP RESTART  N.A.     Shuts down a running server, thenD                                    starts the server. Does not startC                                    printer queues or mount volumes.a          E                       Preparing to Use OpenVMS Management Station G-5n m         + Preparing to Use OpenVMS Management Stationo! G.1 Preparing Your OpenVMS SystemK  A _________________________________________________________________p              ParameterParametertA Command______1________2________Description_______________________o  < @TNT$STARTUP BOOT     blank    Starts the server. Starts any>                                printer queues that are not yetA                                started and are managed by OpenVMSU;                                Management Station. Does notp?                                mount volumes managed by OpenVMSt2                                Management Station.  < @TNT$STARTUP BOOT     ALL      Starts the server. Starts any:                                printer queues that are not=                                yet started and are managed bynA                                OpenVMS Management Station. Mountsm;                                any volumes that are not yetOA                                mounted and are managed by OpenVMSk2                                Management Station.  < @TNT$STARTUP BOOT     PRINTERS Starts the server. Starts any>                                printer queues that are not yetA                                started and are managed by OpenVMSc;                                Management Station. Does not ?                                mount volumes managed by OpenVMSD2                                Management Station.  < @TNT$STARTUP BOOT     STORAGE  Starts the server. Mounts any?                                volumes that are not yet mountedh9                                and are managed by OpenVMS A                                Management Station. Does not starthA _______________________________any_printer_queues._______________m  >       Note that the effect of TNT$STARTUP BOOT, with no second<       parameter, has not changed from earlier releases. This@       command starts any printer queues that are not yet startedA       and are managed by OpenVMS Management Station, but does notS       mount any volumes.  A       Add the following command line to the system shutdown file,         SYS$MANAGER:SYSHUTDWN.COM:  %       $ @SYS$STARTUP:TNT$SHUTDOWN.COM         0 G-6  Preparing to Use OpenVMS Management Station    M      E                           Preparing to Use OpenVMS Management Station E                                     G.1 Preparing Your OpenVMS SystemS    E     G.1.6 Allow OpenVMS Management Station to Control the Printer anda           Storage Environment   C           It is not necessary to remove your existing queue startup B           and volume mount DCL procedures immediately. The OpenVMSE           Management Station server will recognize that you started a$D           queue or mounted a volume with your command procedures and0           will assume that you want it that way.  =           As you become familiar with the server's managementhA           ability, you can remove or comment out the DCL commands C           and procedures that perform these tasks and allow OpenVMSO@           Management Station to control your printer and storage           environment.  <           In addition, the OpenVMS Management Station server?           periodically (every 24 hours) generates a DCL command B           procedure that includes the commands to mount all of theC           volumes managed by OpenVMS Management Station. If you are[C           familiar with DCL, you can look at this command procedure E           to see what actions OpenVMS Management Station performs foraE           you. And, in the event of an unforeseen system problem or a:E           corrupt server database (SYS$SYSTEM:TNT$ACS.DAT), you coulde:           use this command procedure to mount the volumes.  D           The name of the generated file is TNT$EMERGENCY_MOUNT.COM.@           TNT$EMERGENCY_MOUNT.COM is created in SYS$SYSTEM or inB           the directory pointed to by the TNT$ACS logical, if that           logical name exists.  E           The OpenVMS Management Station server limits TNT$EMERGENCY_ &           MOUNT.COM to seven versions.  5     G.1.7 Keeping Your Printer Environment Up to Datee  D           The OpenVMS Management Station server installation creates@           a file named SYS$STARTUP:TNT$UTILITY.COM. This commandE           procedure scans the OpenVMS system and updates the databased9           of known printers, queues, and related devices.n            E                       Preparing to Use OpenVMS Management Station G-7  s  t      + Preparing to Use OpenVMS Management Stationt! G.1 Preparing Your OpenVMS System     & G.1.7.1  When is the Database Updated?         The database is updated:  @       o  As part of the OpenVMS Management Station installation.  6       o  When you specifically invoke TNT$UTILITY.COM.  A       o  At periodic intervals as a server background thread. Two A          logical names control how often this server thread runs:E  A          ________________________________________________________ A          Logical_Name__________Description_______________________i  ?          TNT$PRINTER_RECON_    How often the thread should run, ?          INTERVAL              in minutes, from when the serverd@                                was last started on this node. If>                                you do not define this logical,@                                the default value is 1440 minutes*                                (24 hours).  <          TNT$PRINTER_RECON_    The minimum number of minutes:          INTERVAL_MIN          that must elapse before the@                                thread should run again, starting>                                from when the database was lastA                                updated. If you do not define thiso?                                logical, the default value is 60aA          ______________________minutes_(1_hour)._________________k  @       You can think of these logicals as meaning "run the threadA       this often (TNT$PRINTER_RECON_INTERVAL), but make sure this ?       much time has elapsed since the database was last updated (       (TNT$PRINTER_RECON_INTERVAL_MIN)."  ?       Because you can run TNT$UTILITY.COM yourself, and becausen<       the OpenVMS Management Station server also updates the:       database, the TNT$PRINTER_RECON_INTERVAL_MIN logical>       prevents the database from being updated more frequently       than is actually needed.  9       If you want to change the defaults for one of theset<       logicals, define the logical on all nodes on which the3       OpenVMS Management Station server is running.e    0 G-8  Preparing to Use OpenVMS Management Station n  f      E                           Preparing to Use OpenVMS Management StationbE                                     G.1 Preparing Your OpenVMS Systeme    8     G.1.7.2 Do You Need to Run TNT$UTILITY.COM Manually?  B           If you use OpenVMS Management Station to make all of theB           changes to your printer configuration, the configuration?           files are immediately modified to reflect the changesd:           and you probably do not need to specifically run           TNT$UTILITY.COM.  E           However, if you or someone else uses DCL to make a change -aE           for example, if you use the DELETE /QUEUE command to delete,E           a queue - the configuration files will not be synchronized.pB           In this case, the OpenVMS Management Station client will@           advise you to run TNT$UTILITY.COM to resynchronize the           database._  C           Run the following procedure on one node in the cluster tot.           make the database match your system:  8           $ @SYS$STARTUP:TNT$UTILITY.COM UPDATE PRINTERS  B           For example, if you or someone else used DCL to delete aA           queue, you need to delete that queue from the database.P@           TNT$UTILITY.COM assumes that your system is set up andD           running the way that you want it to, so you should fix any2           problems before you run TNT$UTILITY.COM.  C     G.1.7.3 Are There Any Requirements for Running TNT$UTILITY.COM?n  ?           You need the SYSNAM privilege to run TNT$UTILITY.COM.t  D           TNT$UTILITY.COM connects to the OpenVMS Management StationB           server on the current OpenVMS system to determine deviceB           and queue information. Therefore, the OpenVMS ManagementB           Station server must be running on the node where you run           TNT$UTILITY.COM.  D           The OpenVMS Management Station server then connects to theA           other OpenVMS Management Station servers in the OpenVMSM?           Cluster to determine device and queue information. IttA           is generally a good idea to keep the OpenVMS ManagementmA           Station server running on the other nodes in an OpenVMSt8           Cluster to keep the database up to the minute.  B           However, if the OpenVMS Management Server is not able toE           connect to the OpenVMS Management Station server on a givenm@           node, it uses the known information about that OpenVMSD           node from the database. That is, in the absence of a validA           connection to that OpenVMS node, the information in the ,           database is assumed to be correct.  E                       Preparing to Use OpenVMS Management Station G-9            + Preparing to Use OpenVMS Management Station ! G.1 Preparing Your OpenVMS Systemn    2 G.1.8  Keeping Your Storage Environment Up to Date  <       The TNT$UTILITY.COM utility accepts parameters (UPDATE;       STORAGE) to update the storage database. However, theh<       storage database is updated dynamically every time you<       use the OpenVMS Management Station client to perform aA       storage management operation. Therefore, you do not need tot9       run TNT$UTILITY.COM to update the storage database.p   G.1.9  Enabling Disk Quotas   =       Before installing OpenVMS Management Station, you might >       have disabled disk quotas on the SYSTEM disk. If so, youA       should reenable the quotas and then rebuild to update quota 5       information by entering the following commands:e          $ RUN SYS$SYSTEM:DISKQUOTA       DISKQUOTA> ENABLEo       DISKQUOTA> REBUILD       DISKQUOTA> EXITY  * G.1.10  Caching Storage Configuration Data  :       OpenVMS Management Station uses two logical names to?       determine how often to refresh cached (in-memory) storagen       configuration data.   =       o  TNT$PURGE_CYCLE_LATENCY-Determines how often to waitO?          (in seconds) after purging stale device reports before =          purging again. This value affects how frequently the >          cluster-wide data (maintained by a "master server" is          updated in memory.D            min = 180'          default =  1800   (30 minutes)a$          max = 18000       (5 hours)  :       o  TNT$LOCAL_SURVEY_LATENCY-Determines the delay (in=          seconds) from one node-specific device survey to thea@          next. This value is independent of cluster-wide surveys;          requested by the "master server" when performing ac          purge.             min = 6"          default =  60  (1 minute)$          max = 600      (10 minutes)  1 G-10  Preparing to Use OpenVMS Management Stationn           E                           Preparing to Use OpenVMS Management StationcE                                     G.1 Preparing Your OpenVMS Systemt    >           For both logical names, smaller values result in theE           OpenVMS Management Station server consuming more CPU cyclesC(           in periodic purges or surveys.  @           If you do not accept the defaults, you might find thatE           larger OpenVMS Cluster systems behave better with values ono,           the high end of the allowed range.  E           If you do not define these logicals, the OpenVMS ManagementoB           Station server uses the default values. If you do defineC           these logical names, the values are used only if they are .           within the minimum to maximum range.  ,     G.1.11 Running Third-Party TCP/IP Stacks  E           Compaq TCP/IP Services for OpenVMS Version 3.2 or higher isiE           the only supported TCP/IP stack. Additional stacks have not.B           been tested. However, TCP/IP stacks that are 100 percentE           compliant with the QIO interface for Compaq TCP/IP ServicesmC           for OpenVMS should also work. (Contact your TCP/IP vendorn9           for additional information and support issues.)f  >           For the best chance of success, check the following:  D           o  Make sure that the QIO service (for example, UCXQIO) is              enabled.e  7           o  For TCPware, also make sure that TCPware'ss3              UCX$IPC_SHR.EXE is an installed image.   B           o  Also for TCPware, make sure you are running a versionC              of TCPware that correctly implements a DECC-compatibleN5              socket interface, such as Version 5.3-3.e  -     G.1.12 Determining and Reporting Problemsm  C           If you encounter a problem while using OpenVMS Management_?           Station, please report it to Compaq. Depending on themA           nature of the problem and the type of support you have,T4           you can take one of the following actions:  E           o  If your software contract or warranty agreement entitles 3              you to telephone support, call Compaq.   D           o  If the problem is related to OpenVMS Management StationE              documentation, use the Internet address printed in front 3              of this book to send us your comments.C  E                      Preparing to Use OpenVMS Management Station G-11  t  a      + Preparing to Use OpenVMS Management Stationa! G.1 Preparing Your OpenVMS System     6 G.1.13  Removing the OpenVMS Management Station Server  @       If you use the POLYCENTER Software Installation utility to@       remove OpenVMS Management Station from the OpenVMS system,*       the following files are not removed:         o  TNT$ACS.DAT  ,       o  TNT$JOURNAL.TNT$TRANSACTION_JOURNAL         o  TNT$SERVER_ERROR.LOGn         o  TNT$UADB.DATV          o  TNT$EMERGENCY_MOUNT.COM  ?       Do not delete these files unless you have already removedP!       OpenVMS Management Station.    G.2  Preparing Your PC  ?       During the OpenVMS installation or upgrade procedure, youa=       selected the OpenVMS Management Station client softwareE?       files to be installed on your OpenVMS system disk (or youu<       added them later using the DCL command PRODUCT INSTALL>       TNT). After you have prepared your OpenVMS system to run?       the server software, you must next prepare your PC to runM       the client software.  6       This section includes the following information:  '       o  Required memory and disk space          o  Required software  '       o  Installing the client software   9       o  Getting started using OpenVMS Management Station.  % G.2.1  Required Memory and Disk Spacen  >       Your PC requires 13 MB of free disk space to install the1       OpenVMS Management Station client software.g    1 G-12  Preparing to Use OpenVMS Management Stationt    i      E                           Preparing to Use OpenVMS Management StationfE                                                 G.2 Preparing Your PCs         G.2.2 Distribution Files  B           There are two versions of the OpenVMS Management Station=           client kit: TNT030_I.EXE for Intel systems (Windowsb@           95 and Windows NT), and TNT030_A.EXE for Alpha Windows<           NT systems. Both of these files are located in the,           SYS$COMMON:[TNT.CLIENT] directory.  E           The Intel kit will not install under FX!32 running on Alpha <           processors; use the Alpha native kit in this case.       G.2.3 Required SoftwareT  >           Microsoft Windows NT Versions 4.0 (Service Pack 3 or>           higher) or Windows 95 or higher (Intel only) must be?           installed on each PC on which you want to install they,           OpenVMS Management Station client.  @           The version of MMC included in this baselevel requires@           files provided by Microsoft Internet Explorer. VersionC           3.02 or later of Internet Explorer must be present on thev           system.I  (     G.2.4 Time Required for Installation  E           The time required to install the OpenVMS Management Stationp5           client software is approximately 5 minutes.n  (     G.2.5 Copy the Client File to the PC  @           The client files TNT030_I.EXE (Intel) and TNT030_A.EXE<           (Alpha) are located in the SYS$COMMON:[TNT.CLIENT]E           directory. Copy either client file to a temporary directorye7           the PC using any of the following procedures:d  C           o  Create a file share to the OpenVMS system and copy theo              file.  @           o  Use FTP on the PC to copy the file from the OpenVMS              system.        G.2.6 Installation Directory  =           The installation procedure allows you to select thetE           installation directory, and suggests \Program Files\OpenVMSt'           Mgmt Station\ as the default.t  E                      Preparing to Use OpenVMS Management Station G-13a a         + Preparing to Use OpenVMS Management Stationc G.2 Preparing Your PCd     G.2.7  Installation Procedure   =       Run TNT030_I.EXE (Intel) or TNT030_A.EXE (Alpha) from ap?       temporary directory. These are self-extracting executabler8       files that automate the OpenVMS Management Station       installation.    G.2.8  Recovering from Errorso  >       If an error occurs during installation, you will receive?       an error message describing the problem. This informationw?       can help you determine the cause of the problem. An errori=       can occur during the installation if one or more of theo!       following conditions exist:a  2       o  The operating system version is incorrect  7       o  Disk space and memory necessary for successfuln$          installation are inadequate  4 G.3  After Installing the Client Software on Your PC  ?       When you create an OpenVMS Cluster or OpenVMS Node objecte?       in an OpenVMS Management Domain, you select the transporttA       you want to use for all connections to that system. You canD7       choose DECnet Phase IV for OpenVMS VAX or TCP/IP.I  <       OpenVMS Management Station uses this transport for all?       communications between the PC and this system, or betweene:       any other OpenVMS system that is running the OpenVMS0       Management Station server and this system.  ?          ________________________ Note ________________________n  <          The OpenVMS Management Station client supports only=          TCP/IP connections for primary servers. That is, thec>          connection between the PC and the OpenVMS system uses<          only TCP/IP. Therefore, at least one OpenVMS system           must be running TCP/IP.  ?          ______________________________________________________m  >       You do need to make sure that your PC can connect to the;       primary-server systems, as described in the following ;       sections. OpenVMS Management Station connects your PCr=       to the primary-server system and then routes management '       operations to the target systems.m  1 G-14  Preparing to Use OpenVMS Management StationO V  M      E                           Preparing to Use OpenVMS Management StationOE                                             G.4 Defining TCP/IP Nodesp         G.4 Defining TCP/IP Nodes   D           Your hosts file or name server must be able to resolve theB           IP name or address of all primary-server systems. If youD           can successfully ping the primary-server systems from your)           PC, then this condition is met.a  B     G.5 Uninstalling Version 2.1 of the OpenVMS Management Station         Client  A           Version 3.0 of the OpenVMS Management Station client istC           not dependent on Version 2.1 and does not share any filesuC           with this prior version. After installing the Version 3.0sD           client, you can uninstall the Version 2.1 client software.  /     G.6 Uninstalling OpenVMS Management Station   A           If you need to uninstall the OpenVMS Management Station ;           client software, make sure you first exit OpenVMShA           Management Station. The uninstallation fails if OpenVMS02           Management Station is currently running.  =           If you run the OpenVMS Management Station Help, theo+           following files might be created:o             o  VMSMGMT.FTS             o  VMSMGMT.GID             o  VMSPRINT.FTSc             o  VMSPRINT.GID              o  VMSSCOPE.FTSh             o  VMSSCOPE.GIDC             o  VMSSTORE.FTSd             o  VMSSTORE.GIDe             o  VMSACNT.FTS             o  VMSACNT.GID  C           The OpenVMS Management Station Uninstall program does notu8           delete these files. To complete the uninstall:             1. Delete these filesi  <           2. Delete the OpenVMS Management Station directory  E                      Preparing to Use OpenVMS Management Station G-15t a  o      + Preparing to Use OpenVMS Management Stationt+ G.6 Uninstalling OpenVMS Management Station     @       Note that the OpenVMS Management Station Uninstall program?       does not uninstall the Microsoft Management Console (MMC)        support files.  4 G.7  Getting Started with OpenVMS Management Station  <       All information about getting started, setting up, and=       using OpenVMS Management Station is contained in onlined:       help and the OpenVMS Management Station Overview and       Release Notes.                                                                      1 G-16  Preparing to Use OpenVMS Management Stationp n  o                    E                                                                     HtE     _________________________________________________________________   E                                           Small Capacity System Disks     D           This appendix describes some methods you can use to manageD           small capacity system disks. Some specific recommendationsB           are also included for installing or upgrading to OpenVMS>           VAX Version 7.3 and DECwindows Motif for OpenVMS VAXE           Version 1.2-3 on an RZ24, RA80, or RM80 system disk. (These C           recommendations also apply to Versions 1.1 and 1.2 of thee<           DECwindows Motif for OpenVMS VAX layered product.)  =           Note that you can use the methods described in thisy>           appendix to free disk space on any space-constrained           system.        H.1 Limited Space Support   D           As the OpenVMS VAX operating system and associated layeredC           products continue to develop and mature, their sizes haven@           grown. Previously acceptable system disk devices mightB           now have insufficient capacity for the desired computing>           environment. Support for added features, conformance=           to standards, addition of online documentation, and >           especially, support for a graphical user environment?           (specifically, DECwindows Motif for OpenVMS VAX) havep<           contributed to this growth. Although a single-user?           workstation system might be perceived as entry level, B           it does, in fact, have an increased need for system disk?           capacity to handle the desired graphical environment.e  &     H.1.1 Limited Space Support Option  A           In the past, when the OpenVMS VAX operating system grew E           too large for a specific disk type, that disk was no longerTC           supported as a system device. The OpenVMS VAX Version 7.3NC           operating system and the DECwindows Motif for OpenVMS VAXuC           Version 1.2-3 layered product cannot fit, in total, on ani           RZ24 disk device..  E                                       Small Capacity System Disks H-1r e  c       Small Capacity System Diskss H.1 Limited Space Supportm    6       However, to preserve the investment in some user=       configurations, a limited space support option has been ?       introduced that allows the RZ24 to continue to be used as @       a system disk but with some features removed. For the most<       part, these features include new online documentation,>       programming examples, and programming support files. The@       most important mechanisms used to provide this environment>       are the OpenVMS VAX and DECwindows tailoring facilities,<       VMSTAILOR and DECW$TAILOR. (For more information about(       these facilities, see Chapter 10.)  ?       The limited space support option means that, although theC<       disk (in this case, the RZ24) is supported as a systemA       device, you must take some explicit action to remove or notd>       to install some portions of the product so the remainder9       fits. This option gives small, resource-constrainedo=       system users a choice between investing in new hardware.>       or continuing with existing hardware but with (possibly)       reduced capabilities.l   H.1.2  Configurations Affected  =       The RZ24 disk is now too small for the full OpenVMS VAXa>       Version 7.3 and DECwindows Motif for OpenVMS VAX Version?       1.2-3 kits, regardless of the user's configuration. OtherO?       disk devices, such as the RZ24 and RD54 disks, need to bes@       closely monitored, depending on the system environment and       user configuration.   ;       The general disk space guideline for OpenVMS VAX plus @       DECwindows Motif for OpenVMS VAX Version 1.2-3 is a system;       disk of at least 213 megabytes (or about 377,000 disko<       blocks). For nonworkstation, single-user systems, this=       guideline can be reduced to about 125 megabytes becausee:       DECwindows support is not necessary. For timesharingA       systems, a larger disk is usually necessary due to the needl@       for many layered products and applications. For VAXcluster<       systems, a larger system disk capacity is also usually8       required. Refer to the VAXcluster SPD for details.  @       For specific information about disk space requirements and;       supported system disks, refer to the OpenVMS VAX SPD.p        H-2  Small Capacity System Disks n  r      E                                           Small Capacity System Disks E                                             H.1 Limited Space Supporta    @           While the absolute minimum disk space requirements can?           make base system support available, layered products,y@           applications, and user files usually make it necessary?           to manage even large capacity system disks carefully._C           Therefore, some of the following techniques and ideas cansC           be useful for a broader range of users than can be listeds           by hardware type.e  *     H.1.3 Dealing with a Small System Disk  C           You can solve small system disk configuration problems in            three ways:   D           o  Upgrade your hardware to a larger capacity disk device.  B           o  Add additional hardware disk devices (one or more) to?              the system and redistribute the software contents.   >           o  Reduce the software contents on the existing disk              device.  B           Upgrading hardware might have the highest monetary cost,E           but has the benefits of a full environment and the simplest C           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 contentsl@           requires the lowest capital expense but, by necessity,@           removes some features, documentation, or capabilities.  ?           If your major constraint is fiscal, you might want toaE           investigate the tailoring recommendations first. If time orSE           simplicity are more important, you might want to purchase aa           larger system disk.         H.2 Tailoring Considerations  E           Most of this appendix describes the mechanisms for reducingeC           the software contents on the existing disk device, mostly >           by tailoring. There are also some hints for multipleB           disk systems. There is nothing specific to recommend forC           upgrading the hardware device, except that moving up in apD           single large increment is much more effective than several           smaller ones.M  E                                       Small Capacity System Disks H-3o            Small Capacity System Disks  H.2 Tailoring Considerations    =       The target device in the following sections is the RZ24.?       disk, which has 209 megabytes of disk space. However, you A       can use these methods on any system that is tight on system        disk space.    H.2.1  Configuration Goals  8       The basic configuration goal for the limited space;       support option is for an environment that is not usedh=       for programming. Typically, this is a system with a fewn>       user applications or a turnkey system. It is possible to>       build a viable system with a single programming language?       environment (notably, the C language); however, the space <       used for this support and for the compiler reduces the%       amount of available user space.o  <       There are some mechanisms and techniques common to any>       space-constrained system both for installing new systems9       and for upgrading existing systems. One of the mostp:       important considerations is to reduce the disk space;       consumption of the normal, ongoing system environments>       before doing an upgrade or as soon as possible during or@       after an installation. Some methods for accomplishing this6       are discussed in Section H.5 and in Section H.6.  >       Note that, during an upgrade or installation, there is a=       period of time when the windowing software is likely to =       be unavailable. This means that, on a workstation, your <       monitor functions only as an operator console, and you)       cannot use screen-oriented editors.i  9 H.2.2  Controlling the Size of Dump, Page, and Swap Filese  ;       One of the primary things to control is the sizing of >       the dump, page, and swap files in AUTOGEN. The tailoring@       facilities automatically use AUTOGEN to reboot the system,@       adjusting anything that the tailoring might have affected.;       Because AUTOGEN normally includes existing disk space :       in calculating the sizes for these files, unexpected=       results can occur when tailoring removes some files and ;       AUTOGEN increases the size of others. Fixing the sizes<       of these files by adding appropriate lines to the file?       SYS$SYSTEM:MODPARAMS.DAT will prevent this from occurring @       during an upgrade or after an installation (and, possibly,)       while installing layered products).r    H-4  Small Capacity System Disks o  n      E                                           Small Capacity System DisksoE                                          H.2 Tailoring Considerationsi    ?           The following values are suggested as generous for anp           upgrade:                PAGEFILE = 38000h              SWAPFILE = 13500               DUMPFILE = 0t  C           If your system has been running successfully with smallerr$           values, use those instead.  =           If your windowing system is unavailable, you cannot.@           use a screen-oriented editor to add these lines to theE           SYS$SYSTEM:MODPARAMS.DAT file. You can use the COPY commandd>           to add lines to the end of the text file as follows:  P     $ COPY SYS$SYSTEM:MODPARAMS.DAT,SYS$INPUT: SYS$SYSTEM:MODPARAMS.DAT <Return>%           newparam1 = value1 <Return>e%           newparam2 = value2 <Return>      <Ctrl/Z>  B             ________________________ Note ________________________  B             To be able to use the delete key more effectively whenB             typing input to the console, set the operator terminalA             to be a scope (assuming it is not a hardcopy device).c@             To set the console terminal to be a scope, enter the             following command:  (             $ SET TERM/SCOPE/PERM _OPA0:  B             ______________________________________________________  0     H.2.3 Make a Backup Copy of Your System Disk  C           It is important to make a backup copy of your system diskh@           before any system software upgrade. When tailoring andE           system environment options must be used to fit the requiredoC           software on the device, it is even more important to makec@           a backup copy before you begin and at major milestonesC           during the procedure. This gives you a fallback to a lastoD           good position in the event that a subsequent step producesD           undesired side effects (especially when tailoring softwareD           off of the disk) or fails because you unexpectedly ran out           of disk space.  E                                       Small Capacity System Disks H-5i i  l       Small Capacity System Disks  H.2 Tailoring Considerations     H.2.4  Analyze the System Disk  @       The space used on the system disk might include files that=       have been only partially deleted (usually, because they ?       were still open when an attempt was made to delete them). 9       To recover this space, enter the following command:a  *       $ ANALYZE/DISK/REPAIR SYS$SYSDEVICE:  A       Continue to use the ANALYZE/DISK/REPAIR command after everyt?       reboot or before each major step to be sure that all freea<       blocks are available for the upgrade procedure to use.   H.2.5  Tailoring Options  ?       The installation and upgrade procedures (for both OpenVMS ?       VAX Version 7.3 and DECwindows Motif for OpenVMS VAX) leti=       you select optional software to install or upgrade onlye@       by save set. The tailoring facilities are capable of finer@       granularity and can usually select files in smaller groups       within the save sets.t  9       In the case of DECW$MOTIF_TAILOR, the save sets andi>       tailoring groups are the same. Additionally, DECW$MOTIF_?       TAILOR can only tailor off. To add files, you must eithert;       use the installation or upgrade procedures or use the <       OpenVMS Backup utility (BACKUP) manually to select theA       desired files. For the VMSTAILOR and DECW$TAILOR utilities, @       the tailorable options are subsets of the installation and@       upgrade save sets and can be tailored either on or off. IfA       there is sufficient space to take an entire save set, it isv?       usually faster to select it during the procedure and thensA       tailor off the undesired pieces, rather than tailor them on        later.  @       If you performing an upgrade and have a large area of user<       application files or a large database that is not part=       of the OpenVMS VAX operating system or DECwindows Motif ?       for OpenVMS VAX layered product but resides on the systemp<       disk, it might be convenient to back up that data to a=       separate piece of media, delete it from the system diski@       before the upgrade, and then restore it after the upgrade.=       The blocks can be used in the interim, and you can save =       time and effort in the tailoring and upgrade processes.     H-6  Small Capacity System Disks r  e      E                                           Small Capacity System DisksnE                                          H.2 Tailoring Considerationsl    C           You can decrease the time needed to perform the tailoringdC           and upgrade tasks by disabling the high-water mark on thet@           system disk. To disable the high-water mark, enter the           following command:  1           $ SET VOLUME/NOHIGHWATER SYS$SYSDEVICE:f  A           Depending on the system security you require, you mighttA           want to leave the high-water mark permanently disabled.iA           Otherwise, you can restore it by entering the following            command:  /           $ SET VOLUME/HIGHWATER SYS$SYSDEVICE:   C     H.3 Installing OpenVMS VAX and DECwindows Motif for OpenVMS VAX   <           In general, installing OpenVMS VAX Version 7.3 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 C           capacity of the RZ24 disk, you cannot select some optionsa2           and you might have to do some tailoring.  ,     H.3.1 Installing OpenVMS VAX Version 7.3  D           By itself, the entire OpenVMS VAX Version 7.3 distributionD           kit fits on the RZ24 system disk. So, the easiest approach?           might be to select both the library and optional save @           sets, then use the VMSTAILOR and DECW$TAILOR utilitiesE           to increase the free space before installing the DECwindowsv0           Motif for OpenVMS VAX 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. The D           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.      E                                       Small Capacity System Disks H-7  n          Small Capacity System Disksi? H.3 Installing OpenVMS VAX and DECwindows Motif for OpenVMS VAXs    >       You might choose not to install the Help Message utility;       (MSGHLP) because this option is also very large (8900e<       blocks). Or, you can select it at the expense of otherA       tailorable options later (or at the expense of reduced usern       capacity).  ;       Once the OpenVMS VAX installation is complete, set up =       the dump file as required. It is preferable not to have ?       a dump file at all or to use the paging file as described >       in Section H.5.1. Also, set fixed sizes for the page and<       dump files so that AUTOGEN does not continually resize;       them as you proceed with tailoring and installing the.A       DECwindows Motif for OpenVMS VAX layered product. When your @       environment is complete, you can remove the fixed sizes to?       allow AUTOGEN to calculate appropriate sizes based on theE       final space on the disk.  :       To fit the operating system on an RZ24 disk and haveA       sufficient space to add some layered product or applicationf?       packages and have user space remaining, you can generally(>       support, at most, one programming language and no online<       examples or manuals. Use the VMSTAILOR and DECW$TAILOR3       utilities to remove software you do not need.o  2 H.3.2  Installing DECwindows Motif for OpenVMS VAX  8       Depending on the options and setup of your system,;       you might have sufficient space to install the entire A       DECwindows Motif for OpenVMS VAX kit. However, it is likelyD@       that you again will need to remove support for all but one@       programming language and not include the examples. Because=       the programming support save sets for each language are =       large, choose only the support for languages you really <       need. In the case of the example files, you might want>       to install them if you have the space required, and then?       tailor them off once you have perused them or copied them:       to another area.  @       Remember to use the ANALYZE/DISK/REPAIR command to recover2       any lost space from partially deleted files.            H-8  Small Capacity System Disks           E                                           Small Capacity System DisksiD       H.4 Upgrading OpenVMS VAX and DECwindows Motif for OpenVMS VAX    B     H.4 Upgrading OpenVMS VAX and DECwindows Motif for OpenVMS VAX  C           The following sections describe how to upgrade to OpenVMSnC           VAX Version 7.3 with the DECwindows Motif for OpenVMS VAX_?           Version 1.2-3 layered product from an OpenVMS VAX 6.1a@           or 6.2 system running DECwindows Motif for OpenVMS VAXD           Version 1.1. (Note that Version 1.1 is the minimum versionA           of DECwindows Motif for OpenVMS VAX that you can run ont#           OpenVMS VAX Version 7.3.)o  ;           This option requires the most attention and extraoE           tailoring consideration because the disk blocks used by thesD           DECwindows Motif for OpenVMS VAX layered product cannot beC           used during the OpenVMS VAX upgrade procedure. This meanssD           that you might not be able to select even the library saveD           set during the upgrade and that you will need to tailor on<           portions of it (most notably, the DECnet support).  @           Depending on your configuration, it might be necessaryA           to tailor off DECwindows Motif for OpenVMS VAX and thene-           reinstall it following the upgrade.t  .     H.4.1 Upgrading to OpenVMS VAX Version 7.3  D           Before beginning the upgrade procedure, prepare the systemC           environment - notably the dump, page, and swap files (see,C           Section H.2.2) - and remove as many excess files from theDB           system disk as possible. Use the tailoring facilities to@           remove files that will be replaced or obsoleted by theD           upgrade procedure. This is a good way to get the necessaryA           space (48,950 blocks) to start the upgrade but probablyp>           does not contribute to the final additional capacity           required.V  A           Tailor off all the OpenVMS programming files, examples,lB           and miscellaneous utilities and any DECwindows Motif forD           OpenVMS VAX support that is not required. Before upgradingC           the operating system, keep, at most, one language support B           option, and do not keep any DECwindows Motif for OpenVMS>           VAX examples unless you have sufficient space to getA           at least the OpenVMS VAX required and library save setso"           directly in the upgrade.      E                                       Small Capacity System Disks H-9a D  $       Small Capacity System Disksr> H.4 Upgrading OpenVMS VAX and DECwindows Motif for OpenVMS VAX    ;       If you have sufficient space after tailoring to allows<       both the OpenVMS VAX required and library save sets to?       be selected, then the upgrade will include DECnet supporta>       and DECwindows Motif for OpenVMS VAX will start normally       after the upgrade.  9       If you cannot select the library save set, the lackl9       of DECnet support will likely keep DECwindows Motiff<       for OpenVMS VAX from starting on your system (at which:       point you will have only the operator window on your=       workstation). You can then tailor on the DECnet support <       to get DECwindows Motif for OpenVMS VAX running again.>       After you have DECwindows Motif for OpenVMS VAX running,>       tailoring on any other pieces you might not have alreadyA       acquired from either the library or optional save sets will        be easier.  ;       Compaq recommends that you not take the optional Help <       Message utility (unless you install it on an alternate?       device). You want to choose the DECwindows device support )       if you are upgrading a workstation.   A       Remember to use the ANALYZE/DISK/REPAIR command to clean upa"       any partially deleted files.  1 H.5  Managing Single or Small System Disk Systemso  @       The primary goal for this type of environment is to reduce=       the system disk block usage incurred by the OpenVMS VAXo<       system during normal operation. Both dynamic usage and9       static requirements can be reduced in various ways.e<       Some system processing overhead can also be reduced or;       eliminated in this manner, along with a correspondingS#       reduction in system disk I/O.    H.5.1  System Dump Filel  =       One of the best mechanisms for reducing the total blockt=       overhead of the system is to carefully define the usageg;       of the system dump file. Normally, this is configurede>       as a separate file, SYS$SYSTEM:SYSDUMP.DMP, to which the<       contents of memory are written after a detected system?       failure. Depending on your system requirements, you might 5       be able to reduce or eliminate this disk usage.   ! H-10  Small Capacity System Disksn 3         E                                           Small Capacity System Disks E                      H.5 Managing Single or Small System Disk Systems     E           One effective technique is to use part of the system pagingnB           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. Toe?           do this, you need to modify some system parameters in D           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 usea@           the selective dump mechanism to reduce the size of theC           dump file. This method is typically used for large memoryx@           systems that do not need to preserve the entire memoryE           contents in the event of a system failure. Instead of using B           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 runninghC           in a very stable environment, you might want to clear thet@           DUMPBUG parameter to avoid all dump processing and not'           write a dump file on failure.a  .     H.5.2 Using PAGEFILE.SYS for the Dump File  ?           To use the system paging file as a dump file, add theo?           following lines to the SYS$SYSTEM:MODPARAMS.DAT file:e  6           DUMPBUG = 1  ! Enable system dumps (default)>           SAVEDUMP = 1  ! Keep dump in pagefile until analysisF           DUMPFILE = 0  ! Disallow AUTOGEN to create or size dump file  D           Then delete the SYSDUMP.DMP file by entering the following           command:  +           $ DELETE SYS$SYSTEM:SYSDUMP.DMP;*h  D           Because the system currently has the file open, the delete?           command does not physically remove the file until thehD           system is shut down and rebooted. Use the AUTOGEN facility?           to reboot the system. When it has rebooted, enter theyB           following command to clean up and finish the deletion ofA           the file (and any others that were in a similar state):   .           $ ANALYZE/DISK/REPAIR SYS$SYSDEVICE:  E                                      Small Capacity System Disks H-11u            Small Capacity System Diskso0 H.5 Managing Single or Small System Disk Systems    <       After a system failure that writes dump information to=       the page file, you can analyze the data by entering theV       following command:  -       $ ANALYZE/CRASH SYS$SYSTEM:PAGEFILE.SYSe  ?       When your analysis is complete, you can free the pages toe=       be used for paging once again by entering the following        command:  5       $ ANALYZE/CRASH/RELEASE SYS$SYSTEM:PAGEFILE.SYSs  ?       For more information about the system dump file, refer toh:       the OpenVMS VAX System Dump Analyzer Utility Manual.   H.5.3  Decompressing Libraries  =       The OpenVMS help libraries (as well as some programming.@       libraries) are distributed in a compressed format. You can>       use the SYS$UPDATE:LIBDECOMP.COM procedure to decompress<       the libraries all at once or individually. For a smallA       system disk, it is almost never worth the extra disk blocks.A       consumed to decompress these libraries. The cost of leaving @       them compressed is a longer access time when you use them.  =       If you frequently use help or an individual programmingn@       library, it might be worthwhile to individually decompress;       those libraries. If you only infrequently use help orn>       do not mind the slower response time of the libraries in-       compressed form, leave them compressed.a  " H.5.4  Disabling Log File Creation  ?       Depending on your environment, there might be system jobs @       that create log files of no concern to you or that contain%       more information than you need.   >       Unless you are a network manager or experiencing network?       problems, you probably do not need to log network events.o=       By not logging network events, you can save disk space,T?       a process slot, and some memory in the running system. Toh<       disable network logging, enter the following commands:  '       $ MCR NCP PURGE KNOWN LOGGING ALLo'       $ MCR NCP CLEAR KNOWN LOGGING ALL   =       You need to enter these commands only once; they becomey@       permanent unless you reset the DECnet logging information.  ! H-12  Small Capacity System Diskst u  a      E                                           Small Capacity System DisksgE                      H.5 Managing Single or Small System Disk Systems     A           To reduce the logging information for other tasks (such)B           as OPCOM, Accounting, Security Auditing, Network MonitorB           Event Listener, and system-created batch log files), youC           need to add some commands to your system-specific startuprA           command file, SYS$MANAGER:SYSTARTUP_VMS.COM (previously #           called SYSTARTUP_V5.COM).a  D           The following is an example SYSTARTUP_VMS.COM command file(           for a single-user workstation:  , $ SET NOON     ! Continue thru any problems. $!< $ DEFINE/USER SYS$COMMAND _OPA0:  ! Disable some events fromH $ REPLY/DISABLE=(NETWORK,CLUSTER,SECURITY) !  using the operator window.G $ SET TERM/SCOPE/PERM _OPA0:   ! If windows do not start, use as scope.  $!6 $ SET AUDIT/ALARM -    ! Log interesting audit events.F /ENABLE=(AUDIT,AUTHORIZATION,ACL,LOGIN=(LOCAL,DIALUP,NETWORK,REMOTE),- LOGFAILURE=ALL,BREAKIN=ALL)r $!= $ IF F$SEARCH("SYS$MANAGER:ACCOUNTNG.DAT;-1") .NES. "" THEN - B PURGE SYS$MANAGER:ACCOUNTNG.DAT/KEEP=4 ! Purge old accounting info $!< $ IF F$SEARCH("SYS$MANAGER:OPERATOR.LOG;-1") .NES. "" THEN -? PURGE SYS$MANAGER:OPERATOR.LOG/KEEP=4 ! Purge old operator infoy $!J $ DEFINE/SYSTEM/EXEC SYS$SYLOGIN SYS$MANAGER:SYLOGIN ! Set up system login $!D $ ENABLE AUTOSTART/QUEUES   ! Provide resources for autostart queues0 $ START/QUEUE SYS$BATCH    ! Start a batch queue $!J $ SUBMIT/NOKEEP/NOPRINT SYS$MANAGER:STARTNET ! Start net without batch log $!G $! ...  add other system specific and layered product commands here ...l $! $ EXIT>           You might have an environment that can function withC           even less information than that shown in the example. For E           example, to disable the operator log file, use REPLY/NOLOG, C           or to disable accounting, use SET ACCOUNTING/DISABLE. ForeC           more information about using these commands, refer to the !           OpenVMS DCL Dictionary.a    E                                      Small Capacity System Disks H-13l            Small Capacity System Diskse0 H.5 Managing Single or Small System Disk Systems    0 H.5.5  Accessing Example and Documentation Files  :       If you have network access to another OpenVMS system;       (especially a timesharing system), you do not need tob<       duplicate the example files distributed in the OpenVMS>       VAX or DECwindows Motif for OpenVMS VAX kits if they areA       available on the remote system. Similarly, remote access tooA       the online documentation files also saves considerable diskh6       space on any system with constrained disk space.  # H.6  Managing Multiple Disk Systemsi  =       The following sections describe techniques for managings@       multiple disk systems. In addition to the goal of reducingA       the space requirements on the system device, it is possibleOA       to simultaneously reduce some of the I/O load to the systemf=       disk by redirecting necessary functions to an alternateo
       device.n  $ H.6.1  Alternate Page and Swap Files  A       Setting up alternate page and swap files is one of the bestT=       ways to reduce both the system disk space usage and I/Ot?       overhead. If you set up only a small primary page file one@       the system disk and install additional page and swap files@       in the startup command file SYS$MANAGER:SYPAGSWPFILES.COM,@       you can permanently cause these files to consume the least@       amount of space on the system device. For more information>       about setting up alternate page and swap files, refer to*       the OpenVMS System Manager's Manual.   H.6.2  Copying Dump Files   <       At startup, you can enhance the use of the paging file<       as a dump file that automatically copies the dump data9       for later analysis. This releases the disk space in A       SYS$SYSTEM:PAGEFILE.SYS to be used for paging automaticallyS;       as well. Instead of manually invoking the System Dumpe:       Analyzer (SDA) to release the pages, you can add the=       following commands to the SYS$MANAGER:SYSTARTUP_VMS.COMy       file:t        ! H-14  Small Capacity System Disksh e  t      E                                           Small Capacity System DisksdE                                    H.6 Managing Multiple Disk Systemsd    1           $ ANALYZE/CRASH SYS$SYSTEM:PAGEFILE.SYSh/           COPY alternate_disk:[dir]dumpname.ext            EXIT  B             ________________________ Note ________________________  7             The dump file, whether it is SYSDUMP.DMP orv>             PAGEFILE.SYS, must reside on the system disk. This@             might limit the actual savings you can achieve using!             alternate page files.   B             ______________________________________________________  *     H.6.3 Offloading System Logs and Files  =           There are several system logs and files that can beiA           redirected to another device. For other system logs and @           files, it might be easier to reset and start a new logA           file, copy the old file or files to another device, andA*           purge them from the system disk.  :           Some files that can be redirected are the systemC           authorization file, the queue manager database, the audit ?           log file, and batch log files. Some files that can bee>           reset, copied, and purged are the operator log file,B           the accounting log file, and network log files. For moreA           information about these facilities refer to the OpenVMSeE           System Manager's Manual, the OpenVMS DCL Dictionary, or the B           utility reference manual for the utility whose files you           want to offload.  '     H.6.4 Offloading Nonessential Files   A           Some of the files included with OpenVMS VAX Version 7.3 =           can be redirected to an alternate device during thee?           installation or upgrade procedure. This can save many B           valuable system disk blocks while providing quick accessD           to these files. For a small system disk configuration withB           multiple disks, this approach is recommended if you wantB           the the Help Message utility (MSGHLP) to be available on           line.         E                                      Small Capacity System Disks H-15o o  i                        E     _________________________________________________________________i  E                                                              Glossaryl      >           This glossary defines key terms in the context of an,           OpenVMS VAX computing environment.             boot, bootstrapp  C           The process of loading system software into a processor's.E           main memory. This guide uses the term boot to refer to thisk           process.              boot command procedure  C           A program, stored on the console fixed disk, that is usedn?           to boot the OpenVMS operating system from a specifiedaB           controller. Compaq provides a boot command procedure for6           each controller that the processor supports.             boot name   D           The abbreviated name of the boot command procedure you use           to boot the system.d             boot serverg  A           A VAX computer that is part of a local area VAXcluster. E           The boot server is a combination of a MOP server and a diskcB           server for the satellite system disk. See also satellite           node.g             CI only VAXcluster  D           A computer system consisting of a number of VAX computers.D           It uses only the computer interconnect (CI) to communicateB           with other VAX computers in the cluster. These computers%           share a single file system.d  E                                                            Glossary-1W O  N                      computer interconnect (CI)  =       A type of I/O subsystem. It links VAX computers to eachC=       other and to HSC devices. See also Hierarchical Storage        Controller (HSC) device.         DECW$TAILOR   ?       A software program that lets you add or remove DECwindowsi"       files from your system disk.         device namec  @       The name used to identify a device on the system. A deviceA       name indicates the device code, controller designation, andi       unit number.         disk servers  =       A VAX computer that is part of a local area VAXcluster.i<       This computer provides an access path to CI, CSSI, and=       locally connected disks for other computers that do not        have a direct connection.Y  2       Hierarchical Storage Controller (HSC) device  @       A self-contained, intelligent, mass storage subsystem thatA       lets VAX computers in a VAXcluster environment share disks.E+       Examples are the HSC50 and the HSC70.n         HSC driveo  A       Any disk or tape drive connected to an HSC device is calleds?       an HSC drive. A system disk on an HSC drive can be shared.;       by several VAX computers in a VAXcluster environment.K         InfoServer  >       A general-purpose disk storage server that allows you to@       use the distribution compact disc to install the operatingA       system on remote client systems connected to the same localO       area network (LAN).G         local area VAXcluster=  =       A configuration consisting of one or more VAX computersN<       that act as a MOP server and disk server, and a number?       of low-end VAX computers that act as satellite nodes. TheU=       local area network (LAN) connects all of the computers.R1       These computers share a single file system.l  
 Glossary-2 d  t                         local drivec  A           Any drive that is connected directly to a VAX computer.m             mediao  B           Any packaging agent capable of storing computer softwareD           (For example, compact discs, magnetic tapes, floppy disks,+           disk packs, and tape cartridges.)              MOP server  A           A computer system running DECnet software that downlinerB           loads VAXcluster satellites using the DECnet maintenance           operations protocol.             satellite node  A           A VAX computer that is part of a local area VAXcluster.sC           A satellite node is downline loaded from a MOP server andsC           then boots remotely from the system disk served by a disk D           server in the local area VAXcluster. See also boot server,"           disk server, MOP server.             save set  B           The format in which the Backup utility stores files. The=           OpenVMS operating system is shipped in this format.n             scratch disk  ?           A blank disk or a disk with files you no longer need.a             source drive  E           The drive that holds the distribution kit during an upgradee           or installation.             spin up, spin down  @           To spin up means to bring a disk drive up to operatingB           speed; to spin down means to bring it to a gradual stop.             standalone BACKUP   A           A subset of the BACKUP utility that is booted into maineD           memory instead of running under the control of the OpenVMSD           operating system. Standalone BACKUP is used to back up andB           restore the system disk and to install OpenVMS operating           system software.  E                                                            Glossary-3l                          standalone systemE  3       A computer system with only one VAX computer.h         system diskt  8       The disk that contains or will contain the OpenVMS@       operating system. An OpenVMS system disk is set up so that<       most of the OpenVMS files can be shared by several VAXA       computers. In addition, each computer has its own directorys?       on the system disk that contains its page, swap, and dumpi       files.         target drive  ?       The drive that holds the system disk during an upgrade or.       installation.g         transaction log   ?       A log used by DECdtm services to record information aboutz=       transactions. The Log Manager Control Program (LMCP) is '       used to create a transaction log..  *       UETP (User Environment Test Package)  ?       A software package that tests all the standard peripheral <       devices on your system, various commands and operatingA       system functions, the system's multiuser capability, DECnetZ2       for OpenVMS, and the VAXcluster environment.         VAXcluster environment  @       A computer system consisting of a number of VAX computers.@       There are three types of VAXcluster environments: CI only,)       local area, and mixed interconnect.r         VMSTAILOR   =       A software program that lets you add or remove optionalh*       OpenVMS files from your system disk.        
 Glossary-4 _  _                            B  _________________________________________________________________  B                                                              Index      =  A                                  AUTOGEN command procedure 5  _______________________________     running (cont'd) B  Accounting logs                        at end of an installation,/    effect of upgrades on,  5-3             3-38 =  Accounts                               at end of an upgrade, /    disabling during an                     7-32 ?       installation, 3-25                before an upgrade,  5-8h5    setting up after an              Automatic restart :       installation, 4-4              for an upgrade,  5-18  AGEN$INCLUDE files %    location for upgrades,  5-17     B C  AGEN$PARAMS.REPORT file,  4-12,    _______________________________t?     8-17                            Backing up the system disk,a0  Allocation classes                   4-11, 8-152    determining,  2-5                BACKUP command=  ALLOCLASS parameter,  2-5           using to create a system 1  ANALYZE/DISK_STRUCTURE utility         disk, 3-6e5    error message,  5-12             Backup proceduresr<    using before an upgrade,          before an upgrade,  5-9;       5-12                          Boot command proceduresf2  Architectures                       dddGEN,  7-272    Alpha and VAX,  6-1               DEFBOO,  7-27+  Auditing files                     Bootingu>    replacing after upgrade,  8-3     from console media,  7-12=  AUTOGEN                             from [SYSF],  C-1 to C-8H@    accessing data files during       manually during an upgrade,,       an upgrade, 5-17                  7-12>    rebooting,  3-39                  with InfoServer ISL file,+  AUTOGEN command procedure              3-3 ?    feedback data,  5-8              Building standalone BACKUP,n)    running                            4-3        after an installation,
          4-11a       after an upgrade,  8-16   B                                                            Index-1    c              =                                    Compaq TCP/IP Services fore, C______________________________      OpenVMS5 CD-ROM kit                          configuring,  9-8 2   contents of,  1-5                 function,  9-8; Checklists                         Concurrent upgrades, 6-3s6   postinstallation,  4-13           restrictions,  6-3A   postupgrade,  8-17                setting VOTES parameter,  6-5 ?   preinstallation,  2-12            upgrade procedures,  6-4 tor*   preupgrade,  5-24                    6-5? CI only VAXcluster                 CONSCOPY.COM procedure, 5-10d*   information needed to install    Console?       2-4                          connecting with SYSGEN,  8-6l0 Cluster upgrades                   Console media>   See Concurrent upgrades;          automatic update during an5      Rolling upgrades                  upgrade,  5-10h@ Clusters                            backing up after an upgrade,+                                        8-15 A   See also VAXcluster               backing up before an upgrade, +      environments                      5-10 :   group numbers,  2-6               booting from during an5   passwords,  2-6                      upgrade,  7-12a2 CLUSTER_SIZE parameter              copying,  5-10;   of system disk,  3-8              modifying for automatic 5 Command procedures                     restart,  5-18 A   checking after an upgrade,        modifying to boot from [SYSF] -      8-4                                 7-12dA Common files                        required for an installation, +   coordinating for multiple            2-12s?      boot servers, G-2              required for upgrades,  5-7a;   coordinating for multiple         restoring original boot @      system disks, G-2                 command procedures,  7-27> Compaq DECnet-Plus for OpenVMS      updating after an upgrade,*    VAX,  1-1                           8-5>   choosing to install,  3-19,       using backup copies,  5-10>      7-20                          Creating a system disk, 3-6<   installing during an              from InfoServer devices,+      installation, 3-36                3-12i>   installing during an upgrade,    Customizing the system, 4-4	      7-30u Compaq DECnet-Plus for OpenVMS    VAX license   registering after an      installation, 4-3   registering during an       installation, 3-34n   Index-2s o  s              @                                       DECW$IGNORE_DECNET logical2     D______________________________      name, 4-6E     Date                              DECW$MOTIF_TAILOR utility,  H-6o9       format for entering, 7-9        DECW$TAILOR utilitynE     dddGEN boot command procedure       using on a small system disk, -       restoring original version,         H-6lA         7-27                            using to install optionalt;     DECnet                                components,  3-13vD       configuring after an              using to remove files from aC         installation,  4-5                system disk,  4-10, 8-12,o6     DECnet for OpenVMS                    10-11, 10-12B       preparing for an upgrade,       DECwindows Motif for OpenVMS7         5-18                            tailoring, 8-12pB     DECnet node addresses, 2-4        DECwindows Motif for OpenVMS,     DECnet node names, 2-4               VAXD     DECnet Phase IV for OpenVMS         minimum version requirement,-       VAX,  1-1                           1-2a9       choosing to install, 3-19,        support for, 3-16a>         7-20                            using with OpenVMS VAX;       ignoring during startup, 4-6        Version 7.3,  2-2aD       running with DECwindows Motif   DECwindows support components,,           4-6                           5-23@     DECnet Phase IV for OpenVMS         base support, 3-16, 7-178       VAX license                       choosing optionsB       registering after an                 during an installation,1         installation,  4-3                   3-16 B       registering during an                during an upgrade, 7-178         installation,  3-34             customizing, 9-1E     DECnet Phase IV for OpenVMS         customizing after an upgrade, .       VAX software                        8-14C       installing during an              customizing the server, 9-1tA         installation,  3-22             display server files, E-1i:     Decompressing system libraries      distribution mediaD       after an installation, 4-7           removing from drive, 3-227       after an upgrade, 8-10            font files, E-1g>     DECset Version 11                   installing, 2-10, 3-219       caution before upgrading,         sizes, 3-17, 7-19 =         5-2                             TCP/IP transport, 9-7 7       changing the default debugger     transports, 9-8k>          after upgrading, 5-3           using customer-written:          before upgrading, 5-2            transports,  9-9B                                         workstation support, 3-16,.                                           7-17    E                                                               Index-3e                   : Default volume label,  3-11        Distribution media, 1-31 DEFBOO boot command procedure       loading,  7-4o?   restoring original version,       location during an upgrade,o*      7-27                              5-5: Device names                        multiple volumes,  7-4-   determining,  2-6, 3-6           DSSI disks <   format for upgrade,  7-7          device name change,  2-2-   HSC name format for an           Dump filesa7      upgrade, 7-7                   checking size,  8-4 = Devices                             controlling size of,  H-4t8   configuring before an upgrade     modifying size,  8-3<       7-3                          purged during an upgrade,+ DIGITAL Storage Systems                7-21s?    Interconnect (DSSI) disks        requirement for an upgrade,e+   See DSSI disks                       5-12p6 Directories                         shared,  5-6, 5-12  $   processed during an upgrade,     EB      7-26                          _______________________________= Directory trees                    Editing startup files, 4-4 ;   merged during an upgrade,        Error formatter (ERRFMT) >      7-26                           stopped during an upgrade,+ Disk drives                            7-12(=   selecting for an installation    Errors during installationi;        2-6                          license messages,  3-10 9 Disk space                         Errors during upgradesaA   amount needed to decompress       cluster hang during shutdown,l*      system libraries, 4-7             6-88   increasing on the system          console update,  8-7?      disk, 8-12, H-2                while entering device code,8*   needed for an upgrade,  5-13         7-8@   needed to decompress             EXPECTED_VOTES parameter, 8-5@      libraries, 8-10                setting for rolling upgrade,*   needed to decompress system          6-7        libraries, 4-7 B   needed to run UETP,  4-7,        F______________________________  =      8-11                          Factory installed softwareS+ Distribution kit                    See FISr0   CD-ROM,  1-5                     Feedback data?   magnetic tapes,  1-6              checking before an upgrade, *   OpenVMS VAX,  3-2                    5-80   save sets in,  1-4               FIELD account<   Standalone BACKUP,  3-2           setting passwords,  3-24   TK50 tape cartridges in,  3-2    with multiple volumes,  3-2a   Index-4e 8                 <     FIS (Factory installed            Installation procedure1       software),  xiii                   (cont'd)   B                                         booting standalone BACKUP,-     H______________________________       3-2t  A     Hardware                            booting system disk after D       supported, G-12                     transferring required save3     Help Message save set                 set,  3-9n9       contents, D-3                     computer-specific1<     Help Message utility                  instructions,  3-1B       installing, 2-8, 3-14             rebooting the system, 3-39  B     Hierarchical Storage                registering licenses, 3-27?       Controller (HSC)                  registering OpenVMS VAXo8       See HSC                             license,  3-39=     HSC (Hierarchical Storage           running AUTOGEN, 3-38lC       Controller)                       selecting default windowing 7       device format for an                system,  3-23oE         installation,  3-8              selecting optional components 0       device format for an upgrade,         3-14?         7-7                             setting passwords, 3-24t?       names, 3-6                        tasks performed by, 3-1h8     HSx                                 time zones, 3-34=       displaying name of, 2-7           when to use, 1-8, 2-1r0       preparing for installations,    InstallingA         2-7                             DECwindows software, 3-21aA     HSx device                          optional components, 3-13o>       definition, 1-4                 Installing the operating4                                          system, 3-1B     I                                   cautions and restrictions,-     _______________________________       2-1p>     InfoServer devices, 1-4             information needed forB       booting Standalone BACKUP,          VAXcluster systems,  2-4:         3-2                             preparing for, 2-4=       creating the system disk          recording log of, 2-3 C         from,  3-12                     VMSINSTAL option G warning,n  -     Initial software load (ISL)           2-2   A       See ISL                         ISL (initial software load) 4     Installation                        booting, 3-3        of layered products, 4-11,E         8-15                          K______________________________e/     Installation procedure, 1-7       Keyboards1  8       See also Postinstallation         customizing, 9-33         tasks; Preinstallation          layout, 9-2 D         tasks                              DECwindows keymap, 9-4 to0                                              9-7  E                                                               Index-5o i  t              ) Keyboards (cont'd)                 LimitsS9   model numbers,  9-3               minimum values,  5-14,: Keymap names                       LMF (License Management.   determining,  9-3                  facility)9 KFQSA controller                    error messages,  3-27_A   upgrade requirement,  5-16        example of registration,  B-2 8                                     license registration6 L______________________________        procedure,  B-1= Layered products                    system integrated product 6   availability of,  1-2                licenses,  B-13A   effect of upgrade on,  5-7        using during an installation,n+   installing after OpenVMS VAX         3-32 >      installation, 4-11             Volume Shadowing software,+   installing after upgrade,            B-12 8      8-15                          Local Area VAXclusterA LIBDECOMP.COM (procedure to         information needed to install ,    decompress system libraries)          2-4>       4-9                           upgrade requirements,  5-44 LIBDECOMP.COM procedure,  8-10     Local drives, 1-4&   running after an upgrade,        Log:      8-10                           for installation,  2-3A Libraries                          LURT (License Unit Requirement 1   decompressing after an             Table),  B-4a  $      installation, 4-7             MB   decompressing after an           _______________________________4      upgrade, 8-9                  Magnetic tape kit2 Library save set                    contents,  1-6.   contents,  D-1                   Manual boot@   installing,  3-14, 7-15           after running AUTOGEN,  7-32= License Management facility         during an upgrade,  7-12, +   See LMF                              7-27 < License Unit Requirement Table      enabling for an upgrade,+   See LURT                             5-18a6 Licenses                           Memory requirements6                                     restrictions,  1-25   See also LMF; PAK                MicroVAX computers >   error messages,  3-10             booting from [SYS0],  7-27?   registering after an              booting from [SYSF],  7-23, *      installation, 4-3                 C-19   registering during an            Migration support, 6-1i2      installation, 3-27, 3-28      Minimum startup>   required for upgrades,  5-2       configuring devices after,*   types of,  3-28 to 3-31              7-3   Index-6-                   @     Minimum startup (cont'd)          OpenVMS Management Station>       setting before an upgrade,        installing, 3-15, 7-16?         5-15                            postupgrade tasks, 8-14   A     Mixed-architecture OpenVMS        OpenVMS optional components   ?       Cluster systems,  6-1             See Optional componentstD     Mixed-interconnect VAXcluster     OpenVMS RMS Journaling license<       information needed to install     registering after an<            2-4                            installation,  4-3D       upgrade requirements, 5-4       OpenVMS VAX distribution media4     Mixed-version cluster               loading, 3-79       upgrading to, 6-7 to 6-9        OpenVMS VAX license <     Mixed-version OpenVMS Cluster       registering after an<       systems,  6-1                       installation,  4-36     MODPARAMS.DAT (parameter file)    OpenVMS versions=          4-12                           computer support, B-2 B       entering parameters in, 5-17      required for upgrades, 5-63       modifying, 8-5                  Operator logs B       modifying values, 8-16            effect of upgrades on, 5-39     Monochrome workstations, 9-3      Optional componentsm5     Multiversion upgrade, A-2           choosing, 2-8 E                                         installing on alternate disks 0     N______________________________         3-13D     NETCONFIG.COM procedure             installing with DECW$TAILOR,.       running after an installation       3-13B            4-6                          installing with VMSTAILOR,.     Network                               3-137       See also DECnet for OpenVMS       selecting, 3-14 ;       requirements for an upgrade,      selecting during an1=         5-20                              installation,  3-13oD       restriction on upgrades, 5-4      selecting during an upgrade,.     Networks                              7-143       configuring the system for,       sizes, 3-13a7         4-6                           Optional save set 5     NEW_OVER files, F-2                 contents, D-3a>     NEW_UNDER files, F-3                installing, 3-14, 7-157                                         upgrading, 7-14 ,     O                                 OutputA     _______________________________     saving from installation,o-     OPCOM                                 2-3         stopped during an upgrade,         7-12     OpenVMS library files_!       choosing during an upgrade,8         7-15  E                                                               Index-7     e              @                                    Phase 6 of upgrade procedure,) P______________________________      7-28 > Page and swap files                Postinstallation tasks, 4-1@   locating,  2-5                    adjusting system parameters,* Page files                             4-4?   checking size,  5-13, 8-4         backing up the system disk, 0   controlling size of,  H-4            4-3, 4-11<   modifying size,  5-13, 8-3        configuring DECnet,  4-5?   purged during an upgrade,         creating standalone BACKUP,n*      7-21                              4-3:   recommended location,  5-12       customizing DECwindows=   size required for an upgrade,        support software,  9-1 @      5-12                           customizing the system,  4-48 PAK (Product Authorization          decompressing system6    Key)                                libraries,  4-7?   registering after an              editing startup procedures, *      installation, 4-3                 4-4@   registering during                installing layered products,+      installation, 3-32                4-11t> Passwords                           registering licenses,  4-3<   for system accounts,  2-7         removing unwanted system3      setting during                    files,  4-10 6         installation, 3-24          running UETP,  4-7=   forgotten,  3-40, 7-34            setting up user accounts, *   minimum length,  3-24                4-4:   modifying during upgrade          tuning the system with5      procedure, 7-10                   AUTOGEN,  4-11 4   requirements,  7-10              Postupgrade tasks>   restoring dictionary after an     adding and removing files,+      upgrade, 8-14                     8-12h=   screening for acceptibility,      backing up console media,t+      8-13                              8-15 A Phase 1 of upgrade procedure,       backing up system disk,  8-15 @    7-9                              changing MODPARAMS.DAT,  8-5? Phase 2 of upgrade procedure,       checking system file sizes, *    7-24                                8-4? Phase 3 of upgrade procedure,       creating standalone BACKUP,_+    7-25                                8-15 : Phase 4 of upgrade procedure,       customizing DECwindows5    7-26                                support,  8-14 8 Phase 5 of upgrade procedure,       decompressing system>    7-28                                libraries,  8-9 to 8-11?                                     examining command procedure 6                                        templates,  8-4   Index-8                    ?     Postupgrade tasks (cont'd)        Preupgrade tasks (cont'd)   B       increasing space on the           preparing the system disk,.         system disk,  8-12                5-11E       installing layered products,      preventing interactive loginsP1         8-15                                 5-18a<       modifying size of dump file,      running AUTOGEN, 5-8B         8-3                             setting system parameters,.       modifying size of page file,        5-15=         8-3                             stopping queues, 5-20 -       modifying size of swap file,    Printer B         8-3                             recording installation on,-       purging system files, 8-13          2-3i:       replacing SYSUAF.DAT, 8-3       Products (VMSINSTAL)B       replacing VMS$AUDIT_              specifying for an upgrade,-         SERVER.DAT,  8-3                  7-8g:       running AUTOGEN, 8-16           PURGE command,  8-13A       running UETP, 8-11              Purging system files,  8-13B       tuning the system withE         AUTOGEN,  8-16                Q______________________________ 4       updating console media, 8-5     Queue databaseB       using VMSTAILOR, 8-12             creating after an upgrade,-     Preinstallation tasks, 2-4            4-4 3       collecting information, 2-7     Queue managera@       determining HSx name, 2-7         restoring preferred node4       preparing for VAXcluster            list,  8-2,         environments,  2-4            QueuesD       preparing tape drives, 2-6        requirements for an upgrade,.       software and hardware               5-20B         components,  2-2                stopping batch/print, 5-20C     Preupgrade tasks, 5-1               stopping before an upgrade, .       analyzing and repairing the         5-20,         system disk,  5-12            QuorumB       backing up console media,         maintaining during rolling8         5-10                              upgrades,  6-87       backing up the system disk,     Quorum disk,  2-5r,         5-9                           QuotasB       checking page file size,          checked during an upgrade,.         5-12                              7-12<       configuring devices, 7-3          minimum values, 5-14!       creating standalone BACKUP,          5-10#       preparing DECnet for OpenVMS,i         5-18  E                                                               Index-9                    5                                    Save sets (cont'd)t@ R______________________________     required location,  1-4, 2-2  > Rebooting                           tape cartridge containing,*   after an installation,  3-39         3-2>   after AUTOGEN,  3-39              transferring to the system1   manual,  5-18                        disk,  3-6o:   manually,  3-39                  SCSNODE parameter, 5-16> Recording an installation,  2-3    SCSSYSTEMID parameter, 5-16A Removing unwanted system files     Selecting optional components, )       4-10                           7-14 ) Required save set                  Servert?   transferring to the system        customizing the DECwindows,5*      disk, 3-7                         9-10 Restart                            Shared memory6   enabling automatic,  5-18         restrictions,  1-2, Restrictions                       Shutdowns<   for installations,  2-2           before an upgrade,  5-118 Rights database                    Site-specific command/   creating during an                 procedures ?      installation, 3-25             restored during an upgrade, 0 RIGHTSLIST.DAT file                    7-28, 8-4@   creating during an               Software Product Descriptions+      installation, 3-25              (SPDs)M, RMS Journaling for OpenVMS          See SPDs5    license                         Source drives, 1-4 4   registering during an             definition,  7-3>      installation, 3-33             requirement for VAXcluster4 Rolling upgrades,  6-4                 upgrade,  6-89   effect on SYSUAF.DAT,  5-11,     SPDs (Software Productr2      8-3                             Descriptions)@   maintaining cluster quorum,       location on the distribution0      6-8                               kit,  1-6>   restrictions,  6-4, 6-6          STABACKIT.COM (procedure to?   source drive requirement,          create standalone BACKUP),_)      6-8                             5-10 4   upgrade procedures,  6-7 to      Standalone BACKUP1      6-9                            booting,  3-1   = S                                   booting from InfoServers, * _______________________________        3-2A Save sets                           booting from tape cartridges,f*   installing on an alternate           3-2A      disk, 5-21                     booting on VAX 9000 computers ,   location on magnetic tape,             3-38      1-6                            creating a kit,  4-3   Index-10 o  g              ?     Standalone BACKUP (cont'd)        [SYSF] directory (cont'd)   D       creating after an upgrade,        command to boot MicroVAX andD         8-15                              VAXstation computers from,.       creating before an upgrade,         7-23;         5-10                          [SYSF] directory tree_C       locating on distribution kit,     built by upgrade procedure, .         3-2                               7-139       upgrade requirements, 5-10        deletion of, 7-28i7       using alternative backup        SYSGEN parameters =         procedure,  3-5                 See System parametersn4     Startup files                     SYSGEN utility@       editing after an installation     ALLOCLASS parameter, 2-5@            4-4                          configuring devices, 7-3A     STARTUP_P1 parameter                using to connect console,t-       setting to MIN, 5-15                8-6 A     Swap files                        SYSTARTUP_VMS.COM procedureeE       checking size, 8-4                editing after an installation /       controlling size of, H-4              4-4 A       creating, 5-13                    editing to control DECnet C       modifying size, 8-3                 Phase IV for OpenVMS VAX,1-       purged during an upgrade,           4-6 4         7-21                          SYSTEM accountB       recommended location, 5-12        forgotten passwords, 3-40,.     SWAPFILES.COM procedure               7-344       executing to change system        limits, 5-144         file sizes,  8-4                quotas, 5-14?       to check or modify page file      setting passwords, 3-24i8         size,  5-13                   System disks,  1-3@       to create swap file, 5-13         analyzing and repairing,.     SYCONFIG.COM procedure                5-128       editing after an installation     backing up, 8-15;            4-4                          backing up after an B     SYLOGICALS.COM procedure              installation,  4-3, 4-11E       editing after an installation     backing up before an upgrade, -            4-4                            5-9 C     SYLOGIN.COM procedure               booting a backup copy, 5-11AE       editing after an installation     booting after an installation 1            4-4                               3-39nB     SYS$TIMEZONE.DAT file, 7-13         booting after transferringA     [SYSF] directory                      required save set,  3-9 C       booting from during an            CLUSTER_SIZE parameter, 3-8k5         upgrade,  7-2, 7-23, C-1        creating, 3-6   E                                         customizing with DECW$TAILOR, <                                           4-10, 10-11, 10-12  E                                                              Index-11P    7              3 System disks (cont'd)              System shutdownsu@   customizing with VMSTAILOR,       after an installation,  3-398      4-10, 8-12, 10-1              System time, 4-2, 8-22   dealing with limited space,      SYSTEST account<      H-1, H-3                       setting passwords,  3-247   disk space needed to run         SYSTEST_CLIG account 7      UETP, 4-7, 8-11                disabling during an :   free space needed for an             installation,  3-24  2      upgrade, 5-13                 SYSUAF.DAT file  +   preparing for an upgrade,         See UAFt  	      5-112B   preparing for installations,     T______________________________  8      2-7                           Tailored system disks<   removing unwanted files from,     See DECW$TAILOR utility;8      4-10                              VMSTAILOR utility,   required location during an      Tailoring?      upgrade, 7-27                  on small system disks,  H-3 1   restrictions,  1-3               Tape cartridge >   RZ24,  H-3                        containing save sets,  3-2A   space requirements,  H-2          containing standalone BACKUP, *   specifying volume label for,         3-2.      3-11                          Tape drivesA System files                        preparing for an installation3-   modifying,  8-4                         2-68A   purging,  8-13                    selecting for an installation   - System Generation utility                 2-6t  .   See SYSGEN utility               Target disk? System hang,  7-33                  using backup copy for,  5-9a5 System libraries                   Target drives, 1-4 4   decompressing,  3-26, 8-9 to      definition,  7-3.      8-11                          TCP/IP, 4-52   sizes after decompressing,       TCP/IP software>      8-9                            See Compaq TCP/IP Services2 System parameters                      for OpenVMS'   adjusting,  4-4                  Time =   generated by AUTOGEN feedback     format for entering,  7-9 -        5-8                         Time zones 6   requirements for an upgrade,      updating during an:      5-4, 5-15, 5-16                   installation,  3-34? System password dictionary          updating during an upgrade,-+   restoring after an upgrade,          7-29r	      8-14a   Index-12 e  d              @     Transferring save sets to the     Upgrade procedure (cont'd)D       system disk,  3-6                 deletion of [SYSF] directory  5                                           tree,  7-28 B     U______________________________     disk space needed for page  6     UAF (user authorization file)         files,  5-12D       effect of rolling upgrades        disk space requirement, 5-13B         on,  5-11, 8-3                  effect on accounting logs,-       purged during an upgrade,           5-3 E         7-21                            effect on command procedures, -       replacing after an upgrade,         8-4_C         8-3                             effect on layered products,n-       required location, 5-11             5-7aD     UETP (User Environment Test         effect on MODPARAMS.DAT, 8-5D       Package)                          effect on operator logs, 5-3C       disk space needed to run,         enabling automatic restart,E.         4-7, 8-11                         5-18D       when to run, 4-7, 8-11            enabling manual reboot, 5-18C     UPDATE_CONSOLE.COM procedure        error entering device name,7-       running after an upgrade,           7-8t?         8-8                             files deleted by, 7-13,54     Upgrade and installation              7-26, 7-28A       supplements                       files purged during, 7-211D       using, 2-3, 3-1                   interrupting before Phase 1,-     Upgrade preparation, 5-17             7-9e;     Upgrade procedure, 1-10             loading OpenVMS VAXpB       automatic update of console         distribution media,  7-4A         media,  5-10                    manual reboot after, 7-32HB       booting from console media,       manual reboot from [SYS0],.         7-12                              7-27@       booting from [SYSF], 7-23         merging directory trees,.       booting manually during,            7-26@         7-12                            modifying console media,.       building [SYSF] directory,          5-18B         7-13                            modifying console media toA       cautions and restrictions,          boot from [SYSF],  7-12rA         5-1                             modifying passwords, 7-10aD       choosing optional OpenVMS         OpenVMS version requirement,-         components,  7-15                 5-6t4       concurrent upgrades, 6-4          Phase 1, 7-95       console media required, 5-7       Phase 2, 7-24o5       conversion of VAXVMSSYS.PAR,      Phase 3, 7-25 5         7-28                            Phase 4, 7-26 5       correcting directory pointers     Phase 5, 7-28 5            7-26                         Phase 6, 7-28e  E                                                              Index-13                    : Upgrade procedure (cont'd)         VAXcluster environments2   processing user files,  7-26      building,  4-4?   recording logs,  5-7              cluster group numbers,  2-63;   required location of save         cluster passwords,  2-6 A      sets, 5-5                      DECwindows support components 7   required location of the             for,  3-16, 7-17p?      system disk, 7-27              information required for an 9   requirement for shared dump          installation,  2-4i<      files, 5-12                    problem upgrading,  7-332   requirements,  5-24               types of,  2-4;   restoring original dddGEN,        upgrade requirement for ?      7-27                              shared dump files,  5-12s5   restoring original DEFBOO,       VAXcluster licensev8      7-27                           registering after an9   rolling upgrades,  6-6               installation,  4-3 9      adding a new CPU,  6-9         registering during ani:   running AUTOGEN,  7-32               installation,  3-334   selecting optional components    VAXcluster quorumA        7-14                         maintaining during an upgrade .   shared dump files,  5-6                 7-33>   system files renamed by,          maintaining during rolling5      7-13                              upgrades,  6-8i  6   time zones,  7-29                VAXcluster upgrades<   using a printer to record         See Concurrent upgrades;7      output, 5-7                       Rolling upgradess2   VMSINSTAL option G warning,      VAXft computers=      5-5                            booting from [SYSF],  C-1M7   when to use,  1-11, 2-1          VAXstation computerse> User authorization file             booting from [SYS0],  7-27?   See UAF                           booting from [SYSF],  7-23, * User Environment Test Package          C-1@   See UETP                         VAXVMSSYS.PAR parameter files5 User files                          conversion,  7-281*   processed during an upgrade,     VMB.EXE=      7-26                           copying to console media, *                                        8-5< V                                  VMS$AUDIT_SERVER.DAT file< _______________________________     required location,  5-11> VAX computers                      VMSINSTAL command procedure>   booting from [SYSF],  C-1 to      invoking for upgrade,  7-5:      C-8                            option G warning,  2-24   OpenVMS VAX support for,  B-2    VMSTAILOR utilityA                                     using on a small system disk, *                                        H-6   Index-14 ,  1              5     VMSTAILOR utility (cont'd)        VOTES parameter B       using to install optional         checking votes for rolling8         components,  3-13, 7-14,          upgrades,  6-7>         10-5                            setting for concurrent8       using to remove files from a        upgrades,  6-5@         system disk,  4-10, 8-12,       upgrade requirement, 6-5  '         10-3                          W E     Volume label                      _______________________________S=       definition, 1-5                 Warranted support,  6-1i6       specifying during an            WELCOME.TXT file5         installation,  3-11             updating, 8-4 2     Volume shadowing                  Workstations8       requirements for an upgrade,      customizing, 9-3           5-19E     Volume Shadowing license          X______________________________ 1       registering after an            X terminals E         installation,  4-3              DECwindows support componentsn:       registering during an               for,  3-16, 7-17         installation,  3-33_                                                E                                                              Index-15 