Installation manual

ManualsBrandsVax ManualsHousehold AppliancesVS-190 SERIES

OpenVMSVAXVersion7.3

UpgradeandInstallationManual

Order Number: AA–QSBQD–TE

September 2001

This manual provides step-by-step instructions for upgrading and

installing the Compaq OpenVMS VAX operating system.

This version of OpenVMS VAX Version 7.3 Upgrade and Installation

Manual has been updated and the online version is the most current

version of the manual.

Revision/Update Information: This is a new manual.

Software Version: OpenVMS VAX Version 7.3

Compaq Computer Corporation

Houston, Texas

Summary of content (208 pages)

PAGE 1
OpenVMS VAX Version 7.3 Upgrade and Installation Manual Order Number: AA–QSBQD–TE September 2001 This manual provides step-by-step instructions for upgrading and installing the Compaq OpenVMS VAX operating system. This version of OpenVMS VAX Version 7.3 Upgrade and Installation Manual has been updated and the online version is the most current version of the manual. Revision/Update Information: This is a new manual. Software Version: OpenVMS VAX Version 7.
PAGE 2
© 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. Adobe and Acrobat are trademarks of Adobe Systems Incorporated. Microsoft, Visual C++, Windows, and Windows NT are trademarks of Microsoft Corporation. Intel is a trademark of Intel Corporation. Motif is a trademark of The Open Group.
PAGE 3
Contents Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii 1 Getting Started 1.1 1.1.1 1.1.2 1.1.3 1.1.4 1.1.5 1.1.6 1.2 1.3 1.3.1 1.3.2 1.3.3 1.3.4 1.4 1.4.1 1.4.2 1.5 1.5.1 1.5.2 1.6 Important Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Compaq TCP/IP Services for OpenVMS . . . . . . . . . . . . . . . . . DECnet Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 4
3 Installing the OpenVMS VAX Operating System 3.1 Booting Standalone BACKUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.1 Booting from Tape Cartridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.2 Booting from the InfoServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.3 Booting from the CD–ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2 Creating the System Disk . . . . . . . . . . . . . . . . . . . . . . .
PAGE 5
4.5.2 4.6 4.7 4.7.1 4.7.2 4.7.3 4.7.4 4.8 4.9 4.10 4.11 4.12 4.13 Editing SYSTARTUP_VMS . . . . . . . . . . . . Testing the System with UETP . . . . . . . . . . . . Decompressing the System Libraries . . . . . . . . Methods of Using LIBDECOMP.COM . . . . Responding to LIBDECOMP.COM Prompts Using LIBDECOMP.COM Interactively . . . Using LIBDECOMP.COM in Batch . . . . . . Adding and Removing Operating System Files Installing Layered Products . . . . . . . . . . . . . . .
PAGE 6
5.6.3 5.6.4 5.6.5 5.6.6 5.7 5.8 Prevent Interactive Logins . . . . . . . Check for DECnet for OpenVMS . . Check for Volume Shadowing . . . . . Stop Queues . . . . . . . . . . . . . . . . . . Gathering Information for the Upgrade Preupgrade Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 7
.3.12 7.3.13 7.4 7.4.1 7.5 7.6 7.6.1 7.7 7.8 7.8.1 7.8.2 7.8.3 7.8.4 7.8.5 7.8.6 7.8.7 7.8.8 7.8.9 7.9 Manual System Reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying System Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrade Phase 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mounting Additional Magnetic Tape and Tape Cartridge Volumes Upgrade Phase 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 8
9 Customizing DECwindows Support Software 9.1 9.1.1 9.1.2 9.2 9.3 9.3.1 9.3.2 9.4 Customizing the Server Startup . . . . . . . . . . . . Assumptions . . . . . . . . . . . . . . . . . . . . . . . . How to Override Incorrect Assumptions . . Using Compaq TCP/IP Services for OpenVMS . Using Other Transports with DECwindows . . . Writing a Transport Interface . . . . . . . . . . Installing the Transport Interface Image . . Using the Example Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 9
C Booting from [SYSF] During an Upgrade C.1 C.1.1 C.1.2 C.1.3 C.1.4 C.1.5 C.1.6 C.1.7 Booting Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MicroVAX and VAXstation Computers . . . . . . . . . . . . . . VAX 8530, 8550, 8810 (8700), 8820-N (8800) Computers VAX 8820, 8830, and 8840 Computers . . . . . . . . . . . . . . VAX 8200, 8250, 8300, and 8350 Computers . . . . . . . . . VAX 8600 and 8650 Computers . . . . . . . . . . . . . . . . . . . VAX 6000 Series . . . . . . . . . . . . .
PAGE 10
G.2.5 G.2.6 G.2.7 G.2.8 G.3 G.4 G.5 G.6 G.7 Copy the Client File to the PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recovering from Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . After Installing the Client Software on Your PC . . . . . . . . . . . . . . . . . Defining TCP/IP Nodes . .
PAGE 11
Figures 1–1 1–2 Documentation Used to Perform an Installation . . . . . . . . . . . . . . . . . Documentation Used to Perform an Upgrade . . . . . . . . . . . . . . . . . . . . 1–7 1–9 Frequently Abbreviated Product Names . . . . . . . . . . OpenVMS Cluster Information for Installations . . . . Sizes of Decompressed System Libraries . . . . . . . . . . OpenVMS Cluster Warranted and Migration Support Sizes of Decompressed System Libraries . . . . . . . . . . DECwindows Keymap . . . . . . . . . . . . . . .
PAGE 12
PAGE 13
Preface Intended Audience This manual is intended for anyone responsible for installing or upgrading the Compaq OpenVMS VAX operating system and for the startup, shutdown, and backup operations required on VAX computers running this software. When to Use This Manual If you received factory-installed software (FIS) with your VAX computer, refer to that user documentation to start up your system for the first time.
PAGE 14
• Chapter 10, Using VMSTAILOR and DECW$TAILOR, describes how to use VMSTAILOR and DECW$TAILOR to add or remove optional OpenVMS software. • Appendix A, Multiversion VAX Upgrade Process, provides a quick method of applying multiple upgrades to a VAX system. • Appendix B, License Management Supplement, contains supplementary information about registering licenses.
PAGE 15
Documentation for the Compaq networking products listed above are included on the OpenVMS Online Documentation CD–ROM. Hardcopy documentation must be purchased separately. • The OpenVMS License Management Utility Manual provides information about registering and managing licenses on an OpenVMS VAX system. • The OpenVMS Guide to System Security describes security features provided by the OpenVMS VAX operating system, including criteria for C2 systems.
PAGE 16
Conventions In this manual, Compaq software products are often referred to by their abbreviated names. Some of these are shown (for reference) in Table 1.
PAGE 17
{} In command format descriptions, braces indicate required elements; you must choose one of the options listed. bold text This text style represents the introduction of a new term or the name of an argument, an attribute, or a reason. In the HTML version of this Conventions table, this convention appears as italic text. italic text Italic text indicates important information, complete titles of manuals, or variables.
PAGE 18
PAGE 19
1 Getting Started This chapter provides a general description of what happens during the installation and upgrade procedures, including information you should know before you install or upgrade to the Compaq OpenVMS VAX Version 7.3 operating system. This chapter also describes the contents of the distribution kit, tells you whether you should do an installation or an upgrade, and refers you to the appropriate documentation. 1.1 Important Information Before you install or upgrade to OpenVMS VAX Version 7.
PAGE 20
Getting Started 1.1 Important Information 1.1.4 MACRO32.EXE and Standalone BACKUP To build standalone BACKUP onto tape, you must have the image MACRO32.EXE on your system disk. Do not tailor off (remove) the Macro libraries before building standalone BACKUP onto tape. 1.1.5 Layered Product Availability The most current information about layered product support is available online. Use the following URL: http://www.compaq.
PAGE 21
Getting Started 1.2 Key Terms Term Definition Source drive The drive that holds the distribution media during the upgrade or installation. Target drive The drive that holds the system disk—or, for some files, the alternate disk—during the upgrade or installation. HSx device A self-contained, intelligent, mass storage subsystem that lets computers in an OpenVMS Cluster environment share disks.
PAGE 22
Getting Started 1.3 Locating Files on the Distribution Media The CD–ROM is labeled similar to the following: CD–ROM Label: OpenVMS VAX Version 7.3 Volume Label: VAXVMS073 Note The volume label is the machine-readable name that the OpenVMS VAX operating system and InfoServer systems use to access the CD–ROM. 1.3.2 On Magnetic Tape or Tape Cartridges The OpenVMS VAX Version 7.3 kit is available on two, 6250 BPI, open reel magnetic tapes or on two TK50 CompacTape cartridges.
PAGE 23
Getting Started 1.3 Locating Files on the Distribution Media VOL_SHAD_SPD.PS VOL_SHAD_SPD.TXT Volume Shadowing for OpenVMS GALAXY_SPD.PS GALAXY_SPD.TXT OpenVMS Galaxy To obtain all the SPD files and restore them to your current default directory, enter a BACKUP command using the following format: BACKUP source-drive:VMS073_SPD.BCK /SAVE_SET *.*;* For source-drive, substitute the name of the device that holds your distribution kit.
PAGE 24
Getting Started 1.4 What Happens During an Installation 1.4.2 How to Use the Installation Documentation This manual contains step-by-step instructions for performing an OpenVMS VAX installation. However, you will need to refer to several different documents before and during the installation. Figure 1–1 illustrates the major steps in an installation and the documents you will use to perform each step.
PAGE 25
Getting Started 1.
PAGE 26
Getting Started 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: • Deletes and purges some OpenVMS VAX files on the system disk but leaves all the user files intact. • Transfers the new OpenVMS VAX files from the distribution media to the system disk. Note The upgrade procedure puts the most recent versions of the OpenVMS VAX files in the system common directories (SYS$COMMON).
PAGE 27
Getting Started 1.
PAGE 28
PAGE 29
2 Preparing to Install the OpenVMS VAX Operating System This chapter describes how to prepare for installing the OpenVMS VAX operating system, including: • Being aware of the cautions and restrictions • Ensuring your hardware is ready • Ensuring your software distribution kit is complete • Preparing for an OpenVMS Cluster environment • Preparing your tape and disk drives • Gathering the information you need to supply during the installation procedure • Completing the preinstallation checklist
PAGE 30
Preparing to Install the OpenVMS VAX Operating System 2.1 Cautions and Restrictions 2.1.2 Restrictions The following restrictions apply for Version 7.3 of the OpenVMS VAX operating system: • If your system contains DIGITAL Storage Systems Interconnect (DSSI) disks attached to a KFQSA controller, you will notice a change in the device names for DSSI disks attached to KFQSA controllers. When you boot standalone BACKUP, it displays the devices on your system using the new device naming scheme.
PAGE 31
Preparing to Install the OpenVMS VAX Operating System 2.3 Preparing for an Installation 2.3 Preparing for an Installation Now that you have determined that your hardware and software components are ready, you can make the necessary preparations for installing the OpenVMS VAX operating system. 2.3.
PAGE 32
Preparing to Install the OpenVMS VAX Operating System 2.3 Preparing for an Installation Table 2–1 (Cont.) OpenVMS Cluster Information for Installations Information You Need How to Get It MOP servers, disk servers, tape servers To establish either a local area or a mixed-interconnect cluster, determine which systems will be Maintenance Operations Protocol (MOP) servers, disk servers, and tape servers. Refer to OpenVMS Cluster Systems.
PAGE 33
Preparing to Install the OpenVMS VAX Operating System 2.3 Preparing for an Installation 2.3.3 Information You Need During the Installation During the installation, the procedure prompts you to supply certain information. To save time once the procedure begins, be sure you have the following information available. Remember, entering incorrect information during the installation could force you to repeat the entire installation procedure.
PAGE 34
Preparing to Install the OpenVMS VAX Operating System 2.
PAGE 35
Preparing to Install the OpenVMS VAX Operating System 2.4 Preinstallation Checklist Make sure you have the most recent version of the console media if you have a VAX computer that uses console media. (Described in the upgrade and installation supplement for your VAX computer) Determine whether you want a CI only, local area, or mixed-interconnect cluster if you are installing the OpenVMS VAX operating system on a VAX computer in a cluster environment.
PAGE 36
PAGE 37
3 Installing the OpenVMS VAX Operating System During the installation procedure, OpenVMS VAX files are transferred from the distribution media to the system disk or, for certain files, to an alternate disk. The time required to complete an installation varies depending on your hardware configuration and on the distribution media you are using. In most cases, magnetic tapes and tape cartridges require more time than compact discs.
PAGE 38
Installing the OpenVMS VAX Operating System 3.1 Booting Standalone BACKUP 2. Follow the instructions in the Booting Standalone BACKUP section of the upgrade and installation supplement for your VAX computer. 3. After you boot standalone BACKUP, the system displays the following message: %BACKUP-I-IDENT, standalone BACKUP V7.3; the date is 13-NOV-2000 10:00 $ Note If you have a tape cartridge kit, remove the tape cartridge 2/2 from the drive after you boot standalone BACKUP.
PAGE 39
Installing the OpenVMS VAX Operating System 3.
PAGE 40
Installing the OpenVMS VAX Operating System 3.1 Booting Standalone BACKUP 3.1.3 Booting from the CD–ROM If you are installing from the OpenVMS VAX operating system CD–ROM (your VAX computer supports booting from a local CD–ROM or from an InfoServer), you can use the full OpenVMS environment instead of the standalone BACKUP environment to transfer the VMS073.B save set to your target system disk.
PAGE 41
Installing the OpenVMS VAX Operating System 3.2 Creating the System Disk 3.2.1 Determining Device Names If you have not already done so, determine the device names for the source drive, the target drive, and an alternate device if you will be using one. Write these names on a piece of paper. You will need this information throughout the installation. If either the source drive or the target drive is connected to an HSC, you also need the name of the HSC. (To determine the value for hsc-name, see Section 2.
PAGE 42
Installing the OpenVMS VAX Operating System 3.2 Creating the System Disk If your system has a source-drive that is a local tape cartridge drive with a device name of MUC6 or a target-drive that is an RA81 disk drive with a device name of DUA1 and an HSC name of YOURS, enter the following command and press Return: $ BACKUP/IMAGE/VERIFY MUC6:VMS073.B/SAVE_SET YOURS$DUA1: The procedure transfers the VMS073.B save set from the distribution kit to the system disk.
PAGE 43
Installing the OpenVMS VAX Operating System 3.2 Creating the System Disk You can then choose option 2 to shut down the system in preparation for booting the new system disk, as described in Section 3.2.4. 3.2.4 Booting the New System Disk Halt the system and boot the new system disk, as described in the upgrade and installation supplement for your VAX computer. When the boot is completed, the procedure displays a message and prompts you to enter the date and time.
PAGE 44
Installing the OpenVMS VAX Operating System 3.2 Creating the System Disk %SET-I-INTSET, login interactive limit = 1, current interactive value = 0 %SET-I-INTSET, login interactive limit = 0, current interactive value = 0 Note You can ignore the time zone message. The UTC$TIME_SETUP.COM procedure runs during the final phase of the installation procedure. The procedure also displays OPCOM messages from JOB_CONTROL stating the master queue file QMAN$MASTER.DAT does not exist. You can ignore these messages.
PAGE 45
Installing the OpenVMS VAX Operating System 3.2 Creating the System Disk 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. The procedure then prompts you as follows: * Is the OpenVMS media ready to be mounted? [N]: Y %MOUNT-I-MOUNTED, VMS073 mounted on _DAD1: 3.2.
PAGE 46
Installing the OpenVMS VAX Operating System 3.2 Creating the System Disk 3.2.7.1 OpenVMS Library Files The procedure displays the following message: * Do you want to install the OpenVMS library files? (Y/N) The file subclasses of the VMS073.C save set are listed in Appendix D. If you want to install the VMS073.C files, type Y (for Yes) and press Return. If you require network support, you must select the OpenVMS library component. If you do not want to install the VMS073.
PAGE 47
Installing the OpenVMS VAX Operating System 3.2 Creating the System Disk 3.2.7.4 OpenVMS Management Station Files The procedure displays the following message: The OpenVMS Management Station is a client-server application that provides OpenVMS system management capabilities through a client application on a personal computer (PC) running Microsoft Windows. The server application runs on OpenVMS systems and is automatically installed as part of the OpenVMS operating system.
PAGE 48
Installing the OpenVMS VAX Operating System 3.2 Creating the System Disk If you... Then choose...
PAGE 49
Installing the OpenVMS VAX Operating System 3.2 Creating the System Disk All DECwindows applications run with 75 dots per inch video fonts. By default, most systems start up with 75 dots per inch video fonts. Certain applications can take advantage of 100 dots per inch video fonts. For the VAXstation 4000 series machine, 100 dots per inch video fonts are used by default. If you decide not to install 100 dots per inch video fonts, you must edit SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.
PAGE 50
Installing the OpenVMS VAX Operating System 3.2 Creating the System Disk 3.2.11 Installing OpenVMS Options If you answer Yes to the prompt in Section 3.2.10, the installation procedure begins restoring the OpenVMS options you have selected. After the installation has completed, you can use the VMSTAILOR utility to remove any optional OpenVMS files that you do not need. (For more information about using VMSTAILOR, see Chapter 10.
PAGE 51
Installing the OpenVMS VAX Operating System 3.2 Creating the System Disk The DECwindows support files are listed in Appendix E. After you finish the installation, you can use the DECwindows tailoring utility, DECW$TAILOR, to remove the DECwindows files you do not need. For more information about removing files with DECW$TAILOR, see Chapter 10. 3.
PAGE 52
Installing the OpenVMS VAX Operating System 3.4 Configuring a Cluster $! @ SYS$STARTUP:LAN$STARTUP.COM in SYS$MANAGER:SYSTARTUP_VMS.COM. Then configure the cluster by executing the following command: @SYS$MANAGER:CLUSTER_CONFIG See the OpenVMS System Manager’s Manual: Essentials for more information. Once the network is running on your system, you can execute the SYS$MANAGER:CLUSTER_CONFIG.COM command procedure to configure your cluster.
PAGE 53
Installing the OpenVMS VAX Operating System 3.6 Setting Passwords If you reenter a password incorrectly or if the system determines that the password is too easy for another user to guess, the system displays an error message similar to the following: %VMS-I-PWD_INVALID, account password for SYSTEST is invalid %VMS-I-PWD_WEAK, password is too easy to guess Because of the preceding error, you must take action to secure this account. You must either disable this account, change its password, or do both.
PAGE 54
Installing the OpenVMS VAX Operating System 3.8 Postinstallation Tasks Described After the installation finishes, you might want to do one or more of the following tasks: o DECOMPRESS THE SYSTEM LIBRARIES - To save space, many of the system libraries are shipped in a data-compressed format. If you have enough disk space, you can decompress the libraries for faster access. To data expand the libraries, type: $ @SYS$UPDATE:LIBDECOMP.
PAGE 55
Installing the OpenVMS VAX Operating System 3.9 Registering Licenses – • Examples of license registration using VMSLICENSE.COM and LICENSE REGISTER commands 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 supplies a Product Authorization Key (PAK). Or, you can register licenses with the LICENSE REGISTER command.
PAGE 56
Installing the OpenVMS VAX Operating System 3.9 Registering Licenses Type of License Description VAX VMS Licenses File and Application Server License Provides for the noninteractive use of OpenVMS VAX. OpenVMS based VAXservers are sold with a File and Application Server License. The intent of an OpenVMS based VAXserver is to provide file, print, application, and compute services to clients who have remotely submitted their requests for these services.
PAGE 57
Installing the OpenVMS VAX Operating System 3.9 Registering Licenses If you choose ... Then ... Not to register the licenses at this time Do the following: To register your licenses now 1. Type N and press Return. 2. Go to Section 3.12. 3. Remember that, after the installation, you must register your licenses before performing any other postinstallation tasks (see Chapter 4). Do the following: 1. Type Y and press Return. 2.
PAGE 58
Installing the OpenVMS VAX Operating System 3.9 Registering Licenses • Volume Shadowing for OpenVMS (LMF Product Name: VOLSHAD) You must register and load a license for Volume Shadowing for OpenVMS on each node using volume shadowing, including satellites in an OpenVMS Cluster system. 3.9.5 How to Register DECnet Products You must also register the license for any of the DECnet products you have purchased.
PAGE 59
Installing the OpenVMS VAX Operating System 3.
PAGE 60
Installing the OpenVMS VAX Operating System 3.11 Installing Compaq DECnet-Plus for OpenVMS VAX Software 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. DECnet-Plus will now be installed. Media containing the DECnet-Plus kit must be available.
PAGE 61
Installing the OpenVMS VAX Operating System 3.12 Running AUTOGEN 3.12 Running AUTOGEN The remaining portion of the installation procedure runs AUTOGEN to evaluate your hardware configuration and estimate typical work loads. AUTOGEN then sets system parameters, the sizes of page, swap, and dump files, and the contents of VMSIMAGES.DAT. When AUTOGEN finishes and you reboot your system, the installation procedure is complete.
PAGE 62
Installing the OpenVMS VAX Operating System 3.12 Running AUTOGEN installation procedure finishes. For more information, see Appendix B and refer to the OpenVMS License Management Utility Manual. The system next displays informational messages and accounting information indicating that your OpenVMS VAX operating system is running. For example: %SET-I-INTSET, login interactive limit = 64, current interactive value = 0 SYSTEM job terminated at 13-NOV-2000 13:58:16.
PAGE 63
4 After Installing the OpenVMS VAX Operating System After you have installed the OpenVMS VAX operating system, you need to perform several important tasks to prepare the system for operation.
PAGE 64
After Installing the OpenVMS VAX Operating System 4.2 Registering Your Licenses 4.2 Registering Your Licenses The installation procedure gave you the opportunity to register any software product licenses. If you did not register your OpenVMS VAX license at that time, you must do so before you can use the OpenVMS VAX operating system.
PAGE 65
After Installing the OpenVMS VAX Operating System 4.4 Customizing the System – Starting the queue manager and creating a queue database. (If you are installing on an OpenVMS Cluster system with multiple system disks, refer to the OpenVMS Cluster Systems for additional instructions.) – Setting up user accounts – Adjusting system parameters • 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.
PAGE 66
After Installing the OpenVMS VAX Operating System 4.5 Configuring and Starting Networking Software 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 start automatically. If you plan to run DECnet Phase IV for OpenVMS VAX, after you start the queue manager, edit the commands in SYS$COMMON:[SYSMGR]SYSTARTUP_ VMS.COM that pertain to networking, so that DECnet starts automatically when you boot the system.
PAGE 67
After Installing the OpenVMS VAX Operating System 4.7 Decompressing the System Libraries Table 4–1 gives the approximate number of blocks consumed by each library after decompression. Table 4–1 Sizes of Decompressed System Libraries Library ACLEDT.HLB Blocks 102 Library Blocks ANALAUDIT$HELP.HLB ANLRMSHLP.HLB 16 DBG$UIHELP.HLB 438 DECCCURSE.OLB 15 DECCRTL.OLB 315 DECCRTLG.OLB 77 12 EDFHLP.HLB 37 229 ERFLIB.TLB 104 EVE$KEYHELP.HLB 145 DISKQUOTA.HLB EDTHELP.HLB EVE$HELP.HLB EXCHNGHLP.
PAGE 68
After Installing the OpenVMS VAX Operating System 4.7 Decompressing the System Libraries 4.7.2 Responding to LIBDECOMP.COM Prompts If you want to decompress libraries by responding to prompts from the LIBDECOMP.COM procedure, do the following: 1. Enter the following command and then press Return: $ @SYS$UPDATE:LIBDECOMP.COM The following information is displayed: OpenVMS Library Decompression Utility 1 2 3 4 5 6 7 8 9 10 11 12 13 14 HELPLIB.HLB STARLET.OLB ACLEDT.HLB ANLRMSHLP.HLB DBG$HELP.HLB DBG$UIHELP.
PAGE 69
After Installing the OpenVMS VAX Operating System 4.7 Decompressing the System Libraries of library names within parentheses. 4.8 Adding and Removing Operating System Files To remove OpenVMS VAX operating system files from the system disk, use VMSTAILOR or DECW$TAILOR. For example, if you are not running DECnet software, use VMSTAILOR to remove the files associated with DECnet. Note You cannot use VMSTAILOR to remove files installed on an alternate device from save set VMS073.E.
PAGE 70
After Installing the OpenVMS VAX Operating System 4.11 Running AUTOGEN 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 installation supplement for your computer. 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.
PAGE 71
After Installing the OpenVMS VAX Operating System 4.13 Postinstallation Checklist 4.13 Postinstallation Checklist Use the following checklist to make sure you perform all the necessary postinstallation tasks. Verify the system time. (Described in Section 4.1) Register your licenses if you did not do so during the installation procedure. (Described in Appendix B of this manual and in the OpenVMS License Management Utility Manual) Build a standalone BACKUP kit on the system disk and on removable media.
PAGE 72
PAGE 73
5 Before Upgrading the OpenVMS VAX Operating System This chapter describes which tasks you should perform prior to beginning an upgrade.
PAGE 74
Before Upgrading the OpenVMS VAX Operating System 5.1 Cautions and Restrictions 5.1.2 DECset Version 11 Debugger If you have the DECset Version 11 layered product installed on your system, you must remove the @DEBUG$STARTUP.COM command from the system startup procedure. The debugger shipped with OpenVMS VAX Version 7.3 is a superset of the debugger that was shipped with the DECset Version 11 software. Removing the @DEBUG$STARTUP.COM command will cause the debugger shipped with OpenVMS VAX Version 7.
PAGE 75
Before Upgrading the OpenVMS VAX Operating System 5.1 Cautions and Restrictions 5.1.4 Operator and Accounting Logs The upgrade procedure deletes all the operator and accounting logs. To save these files, move them to a user directory before you start the upgrade. 5.1.5 Special Testing and Debugging Files Before you perform an upgrade, remove or rename any special testing or debugging files that you might have in any of the SYS$SPECIFIC: or SYS$SYSROOT: directories.
PAGE 76
Before Upgrading the OpenVMS VAX Operating System 5.1 Cautions and Restrictions 5.1.8 System Disk Cautions The following cautions apply to the system disk: • If you changed the names of system directories on your system disk, the upgrade procedure will not work correctly. Restore your system disk to a standard directory structure before you attempt an upgrade. • You must not move the system disk or the distribution kit from one drive to another during the upgrade.
PAGE 77
Before Upgrading the OpenVMS VAX Operating System 5.1 Cautions and Restrictions 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 the name SYSDUMP.DMP. If you have a shared system dump file with this name, Compaq recommends that you rename it to SYS$COMMON:[SYSEXE]SYSDUMP_COMMON.DMP. 5.1.13 Layered Products The upgrade procedure is designed so that you should not have to reinstall most layered products after the upgrade.
PAGE 78
Before Upgrading the OpenVMS VAX Operating System 5.3 Examining AUTOGEN Feedback Data 5.3 Examining AUTOGEN Feedback Data After the upgrade is finished, AUTOGEN runs. If it finds valid feedback data on your system, it tries to use AUTOGEN feedback. 5.3.1 Valid Feedback Data Feedback data is produced by the SAVPARAMS phase of AUTOGEN and is stored in SYS$SYSTEM:AGEN$FEEDBACK.DAT. Valid feedback data is defined as follows: • The system was up for at least 24 hours when the feedback data was gathered.
PAGE 79
Before Upgrading the OpenVMS VAX Operating System 5.4 Backing Up the System Disk 5.4.1 How to Back Up the System Disk To make a backup copy of the system disk, follow the instructions in the upgrade and installation supplement for your VAX computer. If you do not have a removable system disk, back up your system disk to tape and restore the image backup to the system disk. This eliminates disk fragmentation on the system disk and creates contiguous free disk blocks required for the upgrade.
PAGE 80
Before Upgrading the OpenVMS VAX Operating System 5.5 Preparing the System Disk 5.5.2 Boot the Backup Copy of Your System Disk If you need to boot the backup copy of your system disk or if you are upgrading an OpenVMS Cluster systems environment, enter the following command (otherwise, go to the next step): $ @SYS$SYSTEM:SHUTDOWN When the procedure asks if an automatic system reboot should be performed, press Return for NO. If you are a cluster member, choose the REMOVE_NODE option.
PAGE 81
Before Upgrading the OpenVMS VAX Operating System 5.5 Preparing the System Disk 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 located on the system disk for the upgrade, but if it is located on the system disk, the file must be located in SYS$SPECIFIC:[SYSEXE].
PAGE 82
Before Upgrading the OpenVMS VAX Operating System 5.5 Preparing the System Disk 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.
PAGE 83
Before Upgrading the OpenVMS VAX Operating System 5.5 Preparing the System Disk Make sure the system parameters SCSNODE and SCSSYSTEMID are defined on your system.
PAGE 84
Before Upgrading the OpenVMS VAX Operating System 5.5 Preparing the System Disk 5.5.11 Add Modified System Parameters to MODPARAMS.DAT Any system parameter values that you modified and did not enter in MODPARAMS.DAT are lost during the upgrade. To retain the values of these parameters, enter their names in MODPARAMS.DAT and the value that AUTOGEN needs to add to the default minimum value. For example, if you modified GBLPAGES by 128 pages above the default, add the following line to SYS$SYSTEM:MODPARAMS.
PAGE 85
Before Upgrading the OpenVMS VAX Operating System 5.6 Preparing the System 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 If the system responds with a translation for SYS$NODE, then DECnet is running on your system. If you set STARTUP_P1 to MIN as described in Section 5.5.9, DECnet should not be running.
PAGE 86
Before Upgrading the OpenVMS VAX Operating System 5.7 Gathering Information for the Upgrade 5.7 Gathering Information for the Upgrade At different points during the upgrade, the procedure prompts you to supply information. To save time once the procedure begins, be sure you have the following information readily available. Remember, entering incorrect information during the upgrade could force you to repeat the entire upgrade procedure.
PAGE 87
Before Upgrading the OpenVMS VAX Operating System 5.7 Gathering Information for the Upgrade Required Information Explanation PAK information The information listed on Product Authorization Keys (PAKs) for any new products you will register. You do not need to register your OpenVMS VAX license or the licenses for any System Integrated Products (SIPs) you are already running. 5.
PAGE 88
Before Upgrading the OpenVMS VAX Operating System 5.8 Preupgrade Checklist If your system disk is part of a shadow set, create a nonshadowed system disk to upgrade. (Described in Volume Shadowing for OpenVMS) Make sure the SYSTEM account has sufficient quotas and limits. (Described in Section 5.5) Set the appropriate system parameters and make sure that STARTUP_P1 is set to MIN. (Described in Section 5.5) Define the system parameters SCSNODE and SCSSYSTEMID. (Described in Section 5.
PAGE 89
6 Preparing to Upgrade in an OpenVMS Cluster Environment This chapter describes how to upgrade an OpenVMS Cluster environment. Refer to OpenVMS Cluster Systems for more detailed information about OpenVMS Cluster environments. 6.1 Mixed-Version Support OpenVMS Alpha Version 7.3 and OpenVMS VAX Version 7.3 provide two levels of support for mixed-version and mixed-architecture OpenVMS Cluster systems. These two support types are warranted and migration.
PAGE 90
Preparing to Upgrade in an OpenVMS Cluster Environment 6.2 Adding a New System to the Cluster 6.2 Adding a New System to the Cluster If you need to add a new computer supported by OpenVMS VAX Version 7.3 to an existing OpenVMS Cluster configuration, Compaq supports two options, listed in the following preferred order: 1. Upgrade the entire cluster to OpenVMS VAX Version 7.3 and add the new computer as a member. 2.
PAGE 91
Preparing to Upgrade in an OpenVMS Cluster Environment 6.4 Concurrent Upgrade 6.4 Concurrent Upgrade This section describes the following: • How a concurrent upgrade works • Tasks you need to perform to prepare your system for a concurrent upgrade 6.4.1 How a Concurrent Upgrade Works During a concurrent upgrade, you must shut down the entire cluster and upgrade each system disk and reboot each VAX computer in the cluster.
PAGE 92
Preparing to Upgrade in an OpenVMS Cluster Environment 6.5 Rolling Upgrade 6.5 Rolling Upgrade This section describes the following: • How a rolling upgrade works • Notes and restrictions • Tasks you need to perform to prepare your system for a rolling upgrade 6.5.1 How a Rolling Upgrade Works During a rolling upgrade, you upgrade each system disk individually, allowing old and new versions of the operating system to run together in the same cluster, creating a mixed-version cluster.
PAGE 93
Preparing to Upgrade in an OpenVMS Cluster Environment 6.5 Rolling Upgrade 6.5.3 Preparing for a Rolling Upgrade To prepare for a rolling upgrade, follow these steps: 1. Check the votes and make adjustments to maintain the proper quorum so the cluster can continue to operate throughout the upgrade. (OpenVMS Cluster Systems describes this procedure in detail.) 2. Select a system disk to upgrade. 3.
PAGE 94
Preparing to Upgrade in an OpenVMS Cluster Environment 6.5 Rolling Upgrade 7. When the upgrade has completed, reboot each VAX computer that boots from the system disk you have just upgraded. 8. Perform the postupgrade tasks described in Chapter 8. 9. Repeat steps 2 to 7 for each system disk you are upgrading. Once you have performed tasks a to d in step 3, you do not need to perform them again.
PAGE 95
7 Upgrading the OpenVMS VAX Operating System This chapter explains the procedure for upgrading a single OpenVMS VAX system disk, including: • How to prepare for booting from the [SYSF] directory • How to configure devices • How to begin the upgrade • What the procedure does and what you are asked to do during the six phases of the upgrade You must complete each phase of the upgrade procedure. On most VAX computers, the upgrade procedure continues automatically from phase to phase.
PAGE 96
Upgrading the OpenVMS VAX Operating System 7.1 Preparing to Boot from [SYSF] 7.1.1 Modifying Boot Command Procedures Some VAX computers require a special command procedure to boot from [SYSF].
PAGE 97
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 source drive. If your OpenVMS VAX distribution kit contains several tapes, put the first one in the drive. The paper labels on the tapes indicate the order in which you use them. If you are not using an InfoServer device, go to Section 7.2.3. If you are using an InfoServer device, proceed to the next section. 7.2.
PAGE 98
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 displays a message similar to the following: %VMSINSTAL-W-LOWQUOTA, -VMSINSTAL-W-LOWQUOTA, -VMSINSTAL-W-LOWQUOTA, -VMSINSTAL-W-LOWQUOTA, The following account quotas may be too low.
PAGE 99
Upgrading the OpenVMS VAX Operating System 7.2 Performing the Upgrade 7.2.5 Specifying the Source Drive VMSINSTAL asks for the name of the drive that holds the distribution media: * Where will the distribution volumes be mounted: Enter the device name of the source drive. For example, if you have a VAX 6000 series computer that has a TK70 with a device name of MUC6, type MUC6 and press Return.
PAGE 100
Upgrading the OpenVMS VAX Operating System 7.2 Performing the Upgrade After a slight pause, the procedure displays a message similar to the following: Beginning installation of VMS V7.3 at 10:08 %VMSINSTAL-I-RESTORE, Restoring product saveset A ... 7.2.8 Monitoring Messages from VMSINSTAL The upgrade procedure displays several important messages that provide you with the following information: What VMSINSTAL is doing. Notes, suggestions, and restrictions about various parts of the upgrade.
PAGE 101
Upgrading the OpenVMS VAX Operating System 7.3 Upgrade Phase 1 7.3.2 SYSTEST and FIELD Account Creation If your system does not have SYSTEST or FIELD accounts, 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.
PAGE 102
Upgrading the OpenVMS VAX Operating System 7.3 Upgrade Phase 1 Do you want to disable the account (Y/N)? N Do you want to change the account password (Y/N)? Y You must now select a new primary password for the SYSTEST account. The password you select must be at least 8 characters in length and cannot be the same as the name of the account.
PAGE 103
Upgrading the OpenVMS VAX Operating System 7.3 Upgrade Phase 1 • Renames files found in SYS$SPECIFIC:[SYSMGR] and in SYS$COMMON:[SYSMGR] by adding _OLD_SPECIFIC to the file extensions. For example, [SYSMGR]LOGIN.COM becomes [SYSMGR]LOGIN.COM_OLD_ SPECIFIC. (The file extensions are restored during Phase 6 of the upgrade procedure.) • Cleans up the system disk by purging all accounting data files, operator logs, and the directory SYSERR.
PAGE 104
Upgrading the OpenVMS VAX Operating System 7.3 Upgrade Phase 1 Also note that, for TK50 tape cartridges, it is quicker to install OpenVMS VAX software during the upgrade than to add software after the upgrade with a tailoring utility. For information about using VMSTAILOR, see Chapter 10. To select the options you want to install, follow the instructions displayed by the procedure. 7.3.6.
PAGE 105
Upgrading the OpenVMS VAX Operating System 7.3 Upgrade Phase 1 7.3.6.4 OpenVMS Management Station Files The procedure displays the following message: The OpenVMS Management Station is a client-server application that provides OpenVMS system management capabilities through a client application on a personal computer (PC) running Microsoft Windows. The server application runs on OpenVMS systems and is automatically installed as part of the OpenVMS operating system.
PAGE 106
Upgrading the OpenVMS VAX Operating System 7.3 Upgrade Phase 1 If you... Then choose... Want to provide font files for X terminals DECwindows base support and DECwindows workstation support Have a workstation monitor (for example, a VR150, VR160, or VR295) capable of displaying 100 dots/inch or a VAXstation 4000 series computer, which uses 100 dots/inch video fonts by default DECwindows base support and DECwindows workstation support with the 100 dots/inch option.
PAGE 107
Upgrading the OpenVMS VAX Operating System 7.3 Upgrade Phase 1 For the VAXstation 4000 series machine, 100 dots per inch video fonts are used by default. If you decide not to install 100 dots per inch video fonts, you must edit SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM to force 75 dots per inch video fonts to be the default. Otherwise, certain applications may not space text properly.
PAGE 108
Upgrading the OpenVMS VAX Operating System 7.3 Upgrade Phase 1 7.3.
PAGE 109
Upgrading the OpenVMS VAX Operating System 7.3 Upgrade Phase 1 Once the shutdown is complete, stop the system using the HALT button on the computer control panel, or the BREAK key on the console terminal if your system has no HALT button. Reboot the system with the following command, replacing "ddcu" with the name of the disk drive that contains the system disk. B/F0000000 ddcu The upgrade is set up to continue once the system reboots. If, for some reason, the kernel V7.
PAGE 110
Upgrading the OpenVMS VAX Operating System 7.4 Upgrade Phase 2 ********************************************************* On MIN or UPGRADE system startup - CLUE is not run. . . . 13-NOV-2000 10:53:26.27 You can ignore the time zone message. The UTC$TIME_SETUP.COM procedure runs during the final phase of the upgrade procedure.
PAGE 111
Upgrading the OpenVMS VAX Operating System 7.5 Upgrade Phase 3 3. Removes the directory entries for page, swap, dump, and authorization files from the old directory tree. 4. Deletes all the remaining accounting data files, operator logs, and all files in the SYSERR directory. 5. Merges the old and new versions of the following files: HELP, DCLTABLES, IMAGELIB.OLB, and STARLET.OLB. 6. Moves all remaining files from the old directory tree [VMS$COMMON] to the new directory tree. 7.
PAGE 112
Upgrading the OpenVMS VAX Operating System 7.6 Upgrade Phase 4 For more information on booting your system, refer to the upgrade and installation supplement for your VAX computer. When the system reboots, the procedure displays a message similar to the following: OpenVMS (TM) VAX Version V7.3 Major version id = 1 Minor version id = 0 After the system reboots, the procedure continues with upgrade Phase 5. Do not move the system disk to a different drive.
PAGE 113
Upgrading the OpenVMS VAX Operating System 7.8 Upgrade Phase 6 SYLOGICALS.COM AGEN$NEW_SATELLITE_DEFAULTS.DAT AGEN$NEW_NODE_DEFAULTS.DAT ICC$SYSTARTUP.COM LAT$SYSTARTUP.COM TFF$STARTUP.COM You might not have site-specific versions of all of these files. The procedure displays a message listing each file as it is restored.
PAGE 114
Upgrading the OpenVMS VAX Operating System 7.8 Upgrade Phase 6 7.8.3 Installing Compaq DECnet-Plus for OpenVMS VAX Earlier in the procedure, you were asked whether you wanted to install the Compaq DECnet-Plus for OpenVMS VAX product. If you answered Yes, the procedure now installs it. 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 with OpenVMS VAX Version 7.
PAGE 115
Upgrading the OpenVMS VAX Operating System 7.8 Upgrade Phase 6 Execution phase starting ... The following product will be installed to destination: DEC VAXVMS DECNET_OSI V7.3 DISK$VAXV72INS:[VMS$COMMON.] Portion done: 0%...10%...20%...30%...40%...80%...90%...100% The following product has been installed: DEC VAXVMS DECNET_OSI V7.3 Layered Product 7.8.4 Running AUTOGEN Next, the procedure displays the following message and runs AUTOGEN: Running AUTOGEN to compute the new SYSTEM parameters ...
PAGE 116
Upgrading the OpenVMS VAX Operating System 7.8 Upgrade Phase 6 Finally, the procedure displays informational messages as well as accounting information indicating that your OpenVMS VAX operating system is running. For example: %STDRV-I-STARTUP, OpenVMS startup begun at 13-NOV-2000 13:36:40.32 . . . %SET-I-INTSET, login interactive limit=64, current interactive value = 0 SYSTEM job terminated at 13-NOV-2000 13:39:28.
PAGE 117
8 After Upgrading the OpenVMS VAX Operating System After you upgrade the OpenVMS VAX operating system, you need to perform several important tasks before you can use the system. These tasks, described in the order in which you perform them, are as follows: • Verifying system time • Restoring the preferred node list • Replacing SYSUAF.DAT and VMS$AUDIT_SERVER.DAT • Examining AGEN$PARAMS.REPORT • Checking the size of system files • Examining your command procedures • Changing MODPARAMS.
PAGE 118
After Upgrading the OpenVMS VAX Operating System 8.1 Verifying System Time 8.1 Verifying System Time During the upgrade, the procedure displayed the system time and gave you the opportunity to enter the correct time if the displayed time was incorrect. Now that you have upgraded your system, verify that the system time is correct by entering the following command: $ SHOW TIME The system displays the date and time.
PAGE 119
After Upgrading the OpenVMS VAX Operating System 8.4 Examining AGEN$PARAMS.REPORT If the report includes a message similar to the following, you can modify the size of the page, swap, or dump file: (****************** %AUTOGEN-W-DSKSPC, The disk on which DISK$OpenVMS072:[SYS0.SYSEXE]PAGEFILE.SYS resides would be over 95% full if it were modified to hold 20000 blocks. ******************) For more information about modifying the sizes of the page, swap, or dump files, see Section 8.5. 8.
PAGE 120
After Upgrading the OpenVMS VAX Operating System 8.7 Changing MODPARAMS.DAT 8.7 Changing MODPARAMS.DAT Review the file SYS$SYSTEM:MODPARAMS.DAT. The upgrade procedure created a new version of this file. The old version is named SYS$SYSTEM:MODPARAMS.DAT_OLD. Modify the new file, if necessary, for your system. If you are upgrading an OpenVMS Cluster system, you must update the MODPARAMS.DAT file for each VAX computer that boots from the system disk.
PAGE 121
After Upgrading the OpenVMS VAX Operating System 8.9 VAX 8530, 8550, 8810 (8700), 8820-N (8800) Computers Substitute CSA1 or CSA2 for device-name. Substitute a 1- to 12-character name for volume-label. For example: $ INITIALIZE/STRUCTURE=1 CSA1: V61CONSOLE 4. Enter the following commands to mount the diskette, create the required directories, and copy the new VMB.EXE to the diskette. Substitute CSA1 or CSA2 for device-name.
PAGE 122
After Upgrading the OpenVMS VAX Operating System 8.9 VAX 8530, 8550, 8810 (8700), 8820-N (8800) Computers 2. Enter the following commands to check if there is enough space for the new VMB.EXE. You need 120 blocks. If you are updating a VAX computer, use CSA1 for device-name. $ RUN SYS$SYSTEM:SYSGEN SYSGEN> CONNECT CONSOLE SYSGEN> EXIT $ EXCHANGE DIRECTORY device-name:VMB.EXE Directory of RT-11 volume TINES$CSA1: VMB.EXE 80 13-NOV-2000 18:40 13-NOV-2000 Total of 1 file, 80 blocks.
PAGE 123
After Upgrading the OpenVMS VAX Operating System 8.10 Decompressing the System Libraries Table 8–1 Sizes of Decompressed System Libraries Library Blocks ACLEDT.HLB 102 Library Blocks ANALAUDIT$HELP.HLB ANLRMSHLP.HLB 16 DBG$UIHELP.HLB 438 DECCCURSE.OLB 15 DECCRTL.OLB 315 DECCRTLG.OLB 77 12 EDFHLP.HLB 37 229 ERFLIB.TLB 104 EVE$KEYHELP.HLB 145 DISKQUOTA.HLB EDTHELP.HLB EVE$HELP.HLB 1197 EXCHNGHLP.HLB 118 IMAGELIB.OLB 1122 DBG$HELP.HLB 18 HELPLIB.HLB INSTALHLP.
PAGE 124
After Upgrading the OpenVMS VAX Operating System 8.10 Decompressing the System Libraries Enter the appropriate letter or the numbers of the libraries you want to decompress. To decompress all libraries, the process takes approximately one half hour. If you prefer, you can execute LIBDECOMP interactively or as a batch job.
PAGE 125
After Upgrading the OpenVMS VAX Operating System 8.12 Increasing Free Space on the System Disk If quotas are not in use on the system disk, ignore the "No such file" message for QUOTA.SYS. Most inconsistencies (including "marked for delete") can be repaired by entering the following command: $ ANALYZE /DISK_STRUCTURE /REPAIR SYS$SYSDEVICE: 8.12.2 Using VMSTAILOR and DECW$TAILOR To remove files you do not need from the system disk, use VMSTAILOR.
PAGE 126
After Upgrading the OpenVMS VAX Operating System 8.13 Restoring Your System Password Dictionary To add your site-specific passwords to the new system password dictionary, enable SYSPRV and merge your local additions by entering the following commands, where LOCAL_PASSWORD_DICTIONARY.DATA is the file that contains your additions: $ SET PROCESS/PRIVILEGE=SYSPRV $ CONVERT/MERGE/PAD LOCAL_PASSWORD_DICTIONARY.DATA _$ SYS$LIBRARY:VMS$PASSWORD_DICTIONARY.DATA 8.
PAGE 127
After Upgrading the OpenVMS VAX Operating System 8.16 Installing Layered Products 8.16 Installing Layered Products Back up your system disk and then use either the VMSINSTAL command procedure or the POLYCENTER Software Installation utility to install layered products on your system. If the system contained Compaq TCP/IP Services for OpenVMS previous to the upgrade, you must reinstall it now. For additional information about installing layered products, see the OpenVMS System Manager’s Manual. 8.
PAGE 128
After Upgrading the OpenVMS VAX Operating System 8.18 Running AUTOGEN 2. Run AUTOGEN in this same way, again, two working days later. Note For the VAX 9000 computer, AUTOGEN’s initial parameter calculations are conservative. To obtain parameter values that match your system workload, you can run AUTOGEN in feedback mode a number of times. For more information, refer to the upgrade and installation supplement for your VAX 9000 computer. 3.
PAGE 129
After Upgrading the OpenVMS VAX Operating System 8.19 Postupgrade Checklist 8.19 Postupgrade Checklist Use the following checklist to make sure you perform all the necessary postupgrade tasks. Verify the system time (described in Section 8.1) Restore the preferred node list for the queue manager (described in Section 8.2) Replace SYSUAF.DAT and VMS$AUDIT_SERVER.DAT (described in Section 8.3) Examine AUTOGEN output stored in the file AGEN$PARAMS.REPORT (described in Section 8.
PAGE 130
PAGE 131
9 Customizing DECwindows Support Software This chapter describes how you can customize DECwindows support software. The DECwindows components provided on the OpenVMS VAX kit supply DECwindows base support and workstation support files only. If you have not installed either of these DECwindows components on your system, skip this chapter.
PAGE 132
Customizing DECwindows Support Software 9.1 Customizing the Server Startup 9.1.2 How to Override Incorrect Assumptions If any of these assumptions is incorrect, you must override them as follows: 1. Make a copy of the file SYS$MANAGER:DECW$PRIVATE_SERVER_ SETUP.TEMPLATE and rename it to a .COM file type. The comments in this file show how to customize individual workstations by adding a section of DCL commands for each workstation.
PAGE 133
Customizing DECwindows Support Software 9.
PAGE 134
Customizing DECwindows Support Software 9.1 Customizing the Server Startup Table 9–1 (Cont.
PAGE 135
Customizing DECwindows Support Software 9.1 Customizing the Server Startup Table 9–1 (Cont.) DECwindows Keymap Dialect Model DECwindows Keymap Name Combined US/UK LK201-(EE,RE,PE) UK_LK201RE US_LK201RE Combined US/UK LK401-(EE,RE,PE) UK_LK401AA US_LK401AA c. After you choose a keymap name, modify the server startup file.
PAGE 136
Customizing DECwindows Support Software 9.2 Using Compaq TCP/IP Services for OpenVMS You can conserve memory and process slots by configuring Compaq TCP/IP Services for OpenVMS software for the minimum DECwindows requirement to support the X protocol. DECwindows only requires that INET_ACP be running. DECwindows does not require that the NFS server, the FTPD server, or the remote terminal servers be running.
PAGE 137
Customizing DECwindows Support Software 9.4 Using the Example Transport 2. Add the following line to SYS$MANAGER:SYSTARTUP_VMS.COM: $ INSTALL CREATE SYS$SHARE:DECW$TRANSPORT_EXAMPLE /OPEN /SHARED/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: $ DECW$SERVER_TRANSPORTS == "DECNET,LOCAL,TCPIP,EXAMPLE" 4. Reboot the workstation, or restart DECwindows. 5.
PAGE 138
PAGE 139
10 Using VMSTAILOR and DECW$TAILOR This chapter describes how to add (tailor on) or remove (tailor off) optional OpenVMS VAX files and DECwindows support files from your system disk using VMSTAILOR and DECW$TAILOR. You will need your OpenVMS VAX software media kit to tailor on files. Any site-specific customization that has been done to a class will be lost when that class is tailored off. 10.1 Using VMSTAILOR To add or remove unwanted OpenVMS VAX files from the system disk, use VMSTAILOR.
PAGE 140
Using VMSTAILOR and DECW$TAILOR 10.1 Using VMSTAILOR Message utility (MESSAGE) Object and Shareable Image libraries MACRO libraries MACRO assembler SDL intermediary form of STARLET.MLB Fortran required files VAX C object libraries • OpenVMS RMS Journaling Files • System Programming Support Files-11 ODS-1,ISO 9660, High Sierra ACPs Monitor utility Delta/XDelta debugger System Dump Analyzer utility (ANALYZE/SYSTEM, ANALYZE/CRASH) System Symbol Table file (SYS.
PAGE 141
Using VMSTAILOR and DECW$TAILOR 10.1 Using VMSTAILOR 10.1.2 Removing OpenVMS VAX Files To remove unwanted files using VMSTAILOR, perform the following steps: 1. Log in to the SYSTEM account. 2. Enter the following command and press Return: $ RUN SYS$UPDATE:VMSTAILOR VMSTAILOR displays a description of the VMSTAILOR program and the following message: Do you want to tailor files "ON" or "OFF"? 3. Enter OFF to remove unwanted files and press Return.
PAGE 142
Using VMSTAILOR and DECW$TAILOR 10.1 Using VMSTAILOR If you are adding files from a compact disc on an InfoServer, first determine whether the SYSGEN parameter SCSNODE is defined on your system (see Section 5.5) or start the DECnet software, and then refer to step 2 of Section 7.2. 3. Enter the following command and press Return: $ RUN SYS$UPDATE:VMSTAILOR VMSTAILOR displays a description of the VMSTAILOR program and the following message: Do you want to tailor files "ON" or "OFF"? 4.
PAGE 143
Using VMSTAILOR and DECW$TAILOR 10.1 Using VMSTAILOR 10.1.4 Sample Session Example 10–1 shows how to add all Network Support files and selected Programming Support files to a system disk. Example 10–1 Sample VMSTAILOR Session $ RUN SYS$UPDATE:VMSTAILOR . . . Do you want to tailor files "ON" or "OFF"? ON TAILOR-ON --------You will now be prompted with a list of the classes and subclasses of OpenVMS Vax files that are optional. The size of each class and subclass is included in the list.
PAGE 144
Using VMSTAILOR and DECW$TAILOR 10.1 Using VMSTAILOR Example 10–1 (Cont.) Sample VMSTAILOR Session CLASS - Secure User’s Environment Size of entire class (with subclasses): 919 Size of common files required for any subclass: 0 Do you wish to select the entire class (default = NO)? Do you wish to select any of its subclasses (default = NO)? . . . Files have been selected Do you wish to add all of the options selected? YES Creating temporary command file, please wait...
PAGE 145
Using VMSTAILOR and DECW$TAILOR 10.2 Using DECW$TAILOR 10.2.2 DECwindows Files You Can Tailor The following is a list of classes and subclasses of DECwindows files that you can add or delete using DECW$TAILOR. For a list of DECwindows files and their functions, see Appendix E. • DECwindows base support files — If you plan to install the separate DECwindows Motif for OpenVMS VAX layered product, you must add the base support files.
PAGE 146
Using VMSTAILOR and DECW$TAILOR 10.2 Using DECW$TAILOR 4. Decide which file classes or subclasses you need to add. DECW$TAILOR displays step-by-step instructions. Follow these instructions to specify which of the classes or subclasses you want to remove. 5. DECW$TAILOR deletes the files you selected and displays the names of those files. If you deleted device support files, the system automatically shuts down and reboots.
PAGE 147
Using VMSTAILOR and DECW$TAILOR 10.2 Using DECW$TAILOR 5. Decide which file classes or subclasses you do not need to support your system. The DECW$TAILOR program displays step-by-step instructions. Follow these instructions to specify which of the classes or subclasses you want to add. 6. DECW$TAILOR installs the files you selected and displays the names of those files. If you added device support files, the system automatically shuts down and reboots.
PAGE 148
Using VMSTAILOR and DECW$TAILOR 10.2 Using DECW$TAILOR Example 10–2 (Cont.) Sample DECW$TAILOR Session No subclasses in this tailor class.
PAGE 149
A Multiversion VAX Upgrade Process This appendix provides you with a quick method and an easy to follow set of directions to apply multiple OpenVMS VAX version upgrades to your current system. Note By following these directions, the time that you spend upgrading your VAX computer from Version 5.5-2 to Version 7.3 can be significantly reduced. A.1 Determine Your Path Your first step is to determine which upgrade path you need to perform.
PAGE 150
Multiversion VAX Upgrade Process A.2 Multiversion Upgrade Procedure A.2.1 Before You Begin the Upgrade Before you begin the multiversion upgrade, you need to perform the following steps: 1. Locate the OpenVMS VAX software kits for the versions that you need. 2. Review the layered products on your system to determine the minimum supported version of each layered product to be installed on your final operating system version. • Determine which layered products you want to run on your system.
PAGE 151
Multiversion VAX Upgrade Process A.2 Multiversion Upgrade Procedure A.2.3 Final Upgrade Follow these steps to perform the final upgrade of your OpenVMS VAX operating system. 1. Review the version-specific documentation. Compaq recommends that you read the New Features, Release Notes, Installation Guide, and Software Product Description available in your software kit. 2. Perform the preupgrade checklist located in the Installation Guide. 3.
PAGE 152
PAGE 153
B License Management Supplement This appendix contains supplemental information to the license instructions given in the installation and upgrade procedures and in the OpenVMS License Management Utility Manual. Although most of the information in this appendix pertains to managing OpenVMS and System Integrated Product (SIP) licenses, some of the information pertains to managing layered product licenses.
PAGE 154
License Management Supplement B.1 Registering Your Licenses B.1.2 How to Register To register a license, you need to obtain a Product Authorization Key (PAK). A typical PAK is a piece of paper provided by Compaq Computer Corporation that contains the appropriate information to authorize access to software on a VAX computer or in an OpenVMS Cluster environment. You can obtain a PAK from a Compaq representative the same way that you obtain software. B.
PAGE 155
License Management Supplement B.2 Using the License Unit Requirement Table (LURT) Table B–1 (Cont.
PAGE 156
License Management Supplement B.2 Using the License Unit Requirement Table (LURT) Table B–1 (Cont.
PAGE 157
License Management Supplement B.3 License Management Facility (LMF) Notes • If a checksum error is displayed when you register a license, check all the fields of data that you entered, including the checksum itself. • After your PAKs are registered, they are activated (loaded) automatically as part of each system startup.
PAGE 158
License Management Supplement B.4 Volume Shadowing for OpenVMS License B.4.2 Volume Shadowing Software Phase I and Phase II In the past, volume shadowing has offered two modes of operation: phase I and phase II. The original implementation of volume shadowing, phase I, was HSC controller-based. The newer implementation, phase II, is host-based and provides performance superior to phase I. With the release of OpenVMS VAX Version 6.2, phase I volume shadowing is no longer available.
PAGE 159
C Booting from [SYSF] During an Upgrade C.1 Booting Procedures You must boot from the [SYSF] root during phases 2, 3, and 4 of the upgrade procedure. Different VAX computers require that you use different booting procedures. This appendix describes how to boot the various VAX computers from [SYSF]. Go to the section that describes your VAX computer and follow the instructions for booting from [SYSF].
PAGE 160
Booting from [SYSF] During an Upgrade C.1 Booting Procedures C.1.3 VAX 8820, 8830, and 8840 Computers To boot from [SYSF], use the following procedure: 1. Enter the following command at the PS-OS-0> prompt and press Return: PS-OS-0> HALT/CPU=ALL 2. Enter the BOOT command at the PS-CIO-0> prompt in the following format: PS-CIO-0> B dddn /R5=F0000000 Substitute BCI or BDA for ddd. Substitute the unit number of the drive holding the system disk for n. C.1.
PAGE 161
Booting from [SYSF] During an Upgrade C.1 Booting Procedures 7. Use the Exchange utility to copy SYFBOO.CMD back to the console media. Enter the following command and press Return: $ EXCHANGE COPY SYFBOO.CMD CSA1:SYFBOO.CMD 8. When the copy operation completes, enter the following command and press Return: $ DISMOUNT CSA1 9.
PAGE 162
Booting from [SYSF] During an Upgrade C.1 Booting Procedures 5. Edit DEFBOO.COM. Change the line that deposits a value in register 5 (R5). This line contains the comment !Use R5 for optional boot control flags [SYSB.]. The value is a hexadecimal number with eight bits. For example: DEPOSIT R5 10000000 !software boot flags Change the left-most digit of the value to reflect the name of the root directory from which you want to boot.
PAGE 163
Booting from [SYSF] During an Upgrade C.1 Booting Procedures • d is the HSC node number of the node being accessed. The /NODE qualifier is not necessary if you are booting from a local disk. The HSC node number is in hexadecimal. You can deposit a maximum of two HSC node numbers (if two HSCs are available). • u is the unit number of the drive holding the system disk.
PAGE 164
PAGE 165
D OpenVMS VAX Save Set Subclasses This appendix lists the file subclasses contained in the following save sets: • VMS073.C — Library save set • VMS073.D — Optional save set • VMS073.E — Help Message save set • VMS073.F — OpenVMS Management Station save set D.
PAGE 166
OpenVMS VAX Save Set Subclasses D.
PAGE 167
E DECwindows Display Server and Fonts Components This appendix provides a list of files provided by the DECwindows base and workstation support components included on the OpenVMS VAX distribution kit. E.
PAGE 168
DECwindows Display Server and Fonts Components E.1 Table of Components Table E–1 DECwindows Display Server and Fonts Components File Purpose Component Class Files in DECW$KEYMAP Directory DECW$KEYMAP BASE Files in SYS$LOADABLE_IMAGES Directory GAADRIVER.EXE VAXstation II/GPX driver WS GABDRIVER.EXE VAXstation 2000/GPX driver WS GBBDRIVER.EXE VAXstation 35x0 driver WS GCADRIVER.EXE VAXstation II monochrome device driver WS GCBDRIVER.
PAGE 169
DECwindows Display Server and Fonts Components E.1 Table of Components Table E–1 (Cont.) DECwindows Display Server and Fonts Components File Purpose Component Class Files in SYS$LIBRARY Directory DECW$DRIVER.MLB Driver macro library WS DECW$FONTCOMPILER.CLD CLD for font compile commands FONT DECW$SERVER_DDX_GA.EXE Server color device support shareable image WS DECW$SERVER_DDX_GB.EXE Server color device support shareable image WS DECW$SERVER_DDX_GC.
PAGE 170
DECwindows Display Server and Fonts Components E.1 Table of Components Table E–1 (Cont.) DECwindows Display Server and Fonts Components File Purpose Component Class Files in SYS$LIBRARY Directory DECW$XPORTDEF.MAR Transport definitions BASE DECW$XPORTDEF.R32 Transport definitions BASE DECW$XPORTMAC.R32 Transport BLISS macros BASE DECW$XPORTMSG.R32 Transport message symbols BASE XDPS$MASTERDPSVM.DAT Display PostScript support file WS Files in SYS$MANAGER Directory DECW$DEVICE.
PAGE 171
F NEW_OVER and NEW_UNDER Files This appendix lists files installed either over or under existing files during an upgrade. F.1 Where Files Are Installed During an upgrade, the procedure replaces certain files that exist on your system with new versions of those files from the OpenVMS VAX distribution kit. For some system files, the upgrade procedure does not replace your existing system files, which might contain customizations for your site.
PAGE 172
NEW_OVER and NEW_UNDER Files F.1 Where Files Are Installed F.1.1 NEW_OVER Files During an upgrade, the following new files are installed over (that is, at a version number higher than) the existing files: [SYSEXE]SHUTDOWN.COM [SYSEXE]STARTUP.COM [SYSHLP]HELPLIB.HLB [SYSLIB]ADARTL.EXE [SYSLIB]BASRTL.EXE [SYSLIB]BASRTL2.EXE [SYSLIB]BLAS1RTL.EXE [SYSLIB]COBRTL.EXE [SYSLIB]DBLRTL.EXE [SYSLIB]DCLTABLES.EXE [SYSLIB]ENCRYPSHR.EXE [SYSLIB]FORRTL.EXE [SYSLIB]FORRTL2.EXE [SYSLIB]IMAGELIB.OLB [SYSLIB]LBRSHR.
PAGE 173
NEW_OVER and NEW_UNDER Files F.1 Where Files Are Installed [SYSLIB]XDPS$DPSCLIENTSHR.EXE [SYSLIB]XDPS$DPSLIBSHR.EXE [SYSLIB]XNL$SHR.EXE [SYSMGR]AMDS$DRIVER_ACCESS.TEMPLATE [SYSMGR]AMDS$LOGICALS.TEMPLATE F.1.3 Site-Specific Files The following files are intended to contain site-specific modifications. Note that, with the exception of TFF$STARTUP.COM, there is a corresponding .TEMPLATE file for each of these files. The new version of the .TEMPLATE file replaces the old version. [SYS$STARTUP]ICC$SYSTARTUP.
PAGE 174
PAGE 175
G Preparing to Use OpenVMS Management Station During the OpenVMS installation or upgrade procedure, the OpenVMS Management Station server software is automatically installed on your OpenVMS system disk. If you accepted the default options the PC client files will be located in SYS$COMMON:[TNT.CLIENT]. If these files are deleted from your system you can either tailor (see Chapter 10) them back on, or download them from the following location: http://www.openvms.compaq.com/openvms/products/argus/index.
PAGE 176
Preparing to Use OpenVMS Management Station G.1 Preparing Your OpenVMS System G.1.1 Setting Up in a Mixed-Architecture Cluster Environment The OpenVMS Management Station server creates several configuration files: • TNT$UADB.DAT • TNT$ACS.DAT • TNT$JOURNAL.TNT$TRANSACTION_JOURNAL • TNT$MONITOR.DAT • TNT$MONITOR.TNT$MONITOR_JOURNAL • TNT$EMERGENCY_MOUNT.
PAGE 177
Preparing to Use OpenVMS Management Station G.1 Preparing Your OpenVMS System 4. To ensure that the system disks are mounted correctly with each reboot, follow these steps: 1. Copy the SYS$EXAMPLES:CLU_MOUNT_DISK.COM file to the [VMS$COMMON.SYSMGR] directory, and edit it for your configuration. 2. Edit SYLOGICALS.COM and include commands to mount, with the appropriate volume label, the system disk containing the shared files.
PAGE 178
Preparing to Use OpenVMS Management Station G.1 Preparing Your OpenVMS System G.1.5 Edit the System Files To start the OpenVMS Management Station server from your system startup files, insert one of the following commands into your system startup procedures (probably SYS$MANAGER:SYSTARTUP_VMS.COM) after both the Queue Manager and network are started, but immediately prior to the ENABLE AUTOSTART/QUEUES.
PAGE 179
Preparing to Use OpenVMS Management Station G.1 Preparing Your OpenVMS System As you become familiar with the server’s management ability, you can remove or comment out the DCL commands and procedures that perform these tasks and allow OpenVMS Management Station to control your printer and storage environment.
PAGE 180
Preparing to Use OpenVMS Management Station G.1 Preparing Your OpenVMS System G.1.7.2 Do You Need to Run TNT$UTILITY.COM Manually? If you use OpenVMS Management Station to make all of the changes to your printer configuration, the configuration files are immediately modified to reflect the changes and you probably do not need to specifically run TNT$UTILITY.COM.
PAGE 181
Preparing to Use OpenVMS Management Station G.1 Preparing Your OpenVMS System G.1.10 Caching Storage Configuration Data OpenVMS Management Station uses two logical names to determine how often to refresh cached (in-memory) storage configuration data. • TNT$PURGE_CYCLE_LATENCY—Determines how often to wait (in seconds) after purging stale device reports before purging again. This value affects how frequently the cluster-wide data (maintained by a ‘‘master server’’ is updated in memory.
PAGE 182
Preparing to Use OpenVMS Management Station G.1 Preparing Your OpenVMS System • If the problem is related to OpenVMS Management Station documentation, use the Internet address printed in front of this book to send us your comments. 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: • TNT$ACS.DAT • TNT$JOURNAL.
PAGE 183
Preparing to Use OpenVMS Management Station G.2 Preparing Your PC G.2.3 Required Software Microsoft Windows NT Versions 4.0 (Service Pack 3 or higher) or Windows 95 or higher (Intel only) must be installed on each PC on which you want to install the OpenVMS Management Station client. The version of MMC included in this baselevel requires files provided by Microsoft Internet Explorer. Version 3.02 or later of Internet Explorer must be present on the system. G.2.
PAGE 184
Preparing to Use OpenVMS Management Station G.3 After Installing the Client Software on Your PC PC and the OpenVMS system uses only TCP/IP. Therefore, at least one OpenVMS system must be running TCP/IP. You do need to make sure that your PC can connect to the primary-server systems, as described in the following sections. OpenVMS Management Station connects your PC to the primary-server system and then routes management operations to the target systems. G.
PAGE 185
Preparing to Use OpenVMS Management Station G.7 Getting Started with OpenVMS Management Station G.7 Getting Started with OpenVMS Management Station All information about getting started, setting up, and using OpenVMS Management Station is contained in online help and the OpenVMS Management Station Overview and Release Notes.
PAGE 186
PAGE 187
H Small Capacity System Disks This appendix describes some methods you can use to manage small capacity system disks. Some specific recommendations are also included for installing or upgrading to OpenVMS VAX Version 7.3 and DECwindows Motif for OpenVMS VAX Version 1.2-6 on an RZ24 or RA80 system disk. (These recommendations also apply to earlier versions of the DECwindows Motif for OpenVMS VAX layered product.
PAGE 188
Small Capacity System Disks H.1 Limited Space Support H.1.2 Configurations Affected The RZ24 disk is now too small for the full OpenVMS VAX Version 7.3 and DECwindows Motif for OpenVMS VAX kits, regardless of the user’s configuration. Slightly larger disk devices need to be closely monitored, depending on the system environment and user configuration. The general disk space guideline for OpenVMS VAX plus DECwindows Motif for OpenVMS VAX Version 1.
PAGE 189
Small Capacity System Disks H.2 Tailoring Considerations H.2.1 Configuration Goals The basic configuration goal for the limited space support option is for an environment that is not used for programming. Typically, this is a system with a few user applications or a turnkey system. It is possible to build a viable system with a single programming language environment (notably, the C language); however, the space used for this support and for the compiler reduces the amount of available user space.
PAGE 190
Small Capacity System Disks H.2 Tailoring Considerations H.2.3 Make a Backup Copy of Your System Disk It is important to make a backup copy of your system disk before any system software upgrade. When tailoring and system environment options must be used to fit the required software on the device, it is even more important to make a backup copy before you begin and at major milestones during the procedure.
PAGE 191
Small Capacity System Disks H.3 Installing OpenVMS VAX and DECwindows Motif for OpenVMS VAX H.3 Installing OpenVMS VAX and DECwindows Motif for OpenVMS VAX In general, installing OpenVMS VAX Version 7.3 and the latest version of DECwindows Motif for OpenVMS VAX is easier than doing an upgrade because there are no user files on the disk when you perform the installation.
PAGE 192
Small Capacity System Disks H.3 Installing OpenVMS VAX and DECwindows Motif for OpenVMS VAX Remember to use the ANALYZE/DISK/REPAIR command to recover any lost space from partially deleted files. H.4 Upgrading OpenVMS VAX and DECwindows Motif for OpenVMS VAX The following sections describe how to upgrade to OpenVMS VAX Version 7.3 and DECwindows Motif for OpenVMS VAX Version 1.2-6 from an OpenVMS VAX Version 6.1 or 6.2 (or higher) system running an older version of DECwindows Motif for OpenVMS VAX.
PAGE 193
Small Capacity System Disks H.5 Managing Single or Small System Disk Systems H.5 Managing Single or Small System Disk Systems The primary goal for this type of environment is to reduce the system disk block usage incurred by the OpenVMS VAX system during normal operation. Both dynamic usage and static requirements can be reduced in various ways. Some system processing overhead can also be reduced or eliminated in this manner, along with a corresponding reduction in system disk I/O. H.5.
PAGE 194
Small Capacity System Disks H.5 Managing Single or Small System Disk Systems When your analysis is complete, you can free the pages to be used for paging once again by entering the following command: $ ANALYZE/CRASH/RELEASE SYS$SYSTEM:PAGEFILE.SYS For more information about the system dump file, refer to 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.
PAGE 195
Small Capacity System Disks H.5 Managing Single or Small System Disk Systems $ SET NOON ! Continue thru any problems. $! $ DEFINE/USER SYS$COMMAND _OPA0: ! Disable some events from $ REPLY/DISABLE=(NETWORK,CLUSTER,SECURITY) ! using the operator window. $ SET TERM/SCOPE/PERM _OPA0: ! If windows do not start, use as scope. $! $ SET AUDIT/ALARM ! Log interesting audit events.
PAGE 196
Small Capacity System Disks H.6 Managing Multiple Disk Systems 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 data for later analysis. This releases the disk space in SYS$SYSTEM:PAGEFILE.SYS to be used for paging automatically as well. Instead of manually invoking the System Dump Analyzer (SDA) to release the pages, you can add the following commands to the SYS$MANAGER:SYSTARTUP_VMS.
PAGE 197
Glossary This glossary defines key terms in the context of an OpenVMS VAX computing environment. boot, bootstrap The process of loading system software into a processor’s main memory. This guide uses the term boot to refer to this process. boot command procedure A program, stored on the console fixed disk, that is used to boot the OpenVMS operating system from a specified controller. Compaq provides a boot command procedure for each controller that the processor supports.
PAGE 198
Hierarchical Storage Controller (HSC) device A self-contained, intelligent, mass storage subsystem that lets computers in a cluster environment share disks. Examples are the HSC50 and the HSC70. HSC drive Any disk or tape drive connected to an HSC device is called an HSC drive. A system disk on an HSC drive can be shared by several computers in an OpenVMS Cluster environment.
PAGE 199
spin up, spin down To spin up means to bring a disk drive up to operating speed; to spin down means to bring it gradually to a stop. standalone BACKUP A subset of the BACKUP utility that is booted into main memory instead of running under the control of the OpenVMS operating system. Standalone BACKUP is used to back up and restore the system disk and to install OpenVMS operating system software. standalone system A computer system consisting of just one computer.
PAGE 200
PAGE 201
Index Building standalone BACKUP, 4–2 A Accounting logs effect of upgrades on, 5–3 Accounts disabling during an installation, 3–17 setting up after an installation, 4–3 AGEN$INCLUDE files location for upgrades, 5–11 AGEN$PARAMS.
PAGE 202
Console media (cont’d) restoring original boot command procedures, 7–17 updating after an upgrade, 8–4 using backup copies, 5–7 Creating a system disk, 3–4 from InfoServer devices, 3–8 Customizing the system, 4–2 D Date format for entering, 7–6 dddGEN boot command procedure restoring original version, 7–17 DECnet configuring after an installation, 4–3 DECnet for OpenVMS preparing for an upgrade, 5–12 DECnet node addresses, 2–3 DECnet node names, 2–3 DECnet Phase IV for OpenVMS VAX, 1–1 choosing to install,
PAGE 203
E Error formatter (ERRFMT) stopped during an upgrade, 7–8 Errors during installation license messages, 3–7 Errors during upgrades cluster hang during shutdown, 6–5 console update, 8–5 while entering device code, 7–5 EXPECTED_VOTES parameter, 8–4 setting for rolling upgrade, 6–5 F Factory installed software See FIS Feedback data checking before an upgrade, 5–6 FIELD account setting passwords, 3–16 FIS (Factory installed software), xiii H Hardware supported, G–8 Help Message utility installing, 2–5, 3–10 sa
PAGE 204
License Management facility See LMF License Unit Requirement Table See LURT Licenses See also LMF; PAK error messages, 3–7 registering after an installation, 4–2 registering during an installation, 3–18, 3–19 required for upgrades, 5–1 types of, 3–19 to 3–20 Limits minimum values, 5–10 LMF (License Management facility) error messages, 3–18 example of registration, B–2 license registration procedure, B–1 system integrated product licenses, B–6 using during an installation, 3–21 Volume Shadowing software, B–5
PAGE 205
Optional components (cont’d) selecting during an upgrade, 7–9 sizes, 3–9 Optional save set contents, D–2 installing, 3–10, 7–10 upgrading, 7–9 P Page files checking size, 5–9, 8–3 controlling size of, H–3 locating, 2–3 modifying size, 5–9, 8–3 purged during an upgrade, 7–14 recommended location, 5–9 size required for an upgrade, 5–9 PAK (Product Authorization Key) registering after an installation, 4–2 registering during installation, 3–20 Passwords for system accounts, 2–5 setting during installation, 3–1
PAGE 206
Rebooting (cont’d) manually, 3–25 Removing unwanted system files, 4–7 Required save set transferring to the system disk, 3–5 Restart enabling automatic, 5–12 Restrictions for installations, 2–2 Restrictions for Version 7.3, 1–2 Rights database creating during an installation, 3–17 RIGHTSLIST.DAT file creating during an installation, 3–17 RMS Journaling for OpenVMS license registration during an installation, 3–21 Rolling upgrades, 6–2 effect on SYSUAF.
PAGE 207
System disks (cont’d) creating, 3–4 customizing with DECW$TAILOR, 4–7, 10–7, 10–8 customizing with VMSTAILOR, 4–7, 8–9, 10–1 dealing with limited space, H–1, H–2 disk space needed to run UETP, 4–4, 8–8 free space needed for an upgrade, 5–9 preparing for an upgrade, 5–7 preparing for installations, 2–4 removing unwanted files from, 4–7 required location during an upgrade, 7–18 RZ24, H–2 space requirements, H–2 specifying volume label for, 3–8 System files modifying, 8–3 purging, 8–9 System Generation utility
PAGE 208
Upgrade procedure (cont’d) modifying console media, 5–12 modifying console media to boot from [SYSF], 7–8 modifying passwords, 7–7 OpenVMS version requirement, 5–4 Phase 1, 7–6 Phase 2, 7–15 Phase 3, 7–16 Phase 4, 7–17 Phase 5, 7–18 Phase 6, 7–18 preparation for, 5–11 processing user files, 7–16 recording logs, 5–5 required location of save sets, 5–3 required location of the system disk, 7–18 requirement for shared dump files, 5–8 requirements, 5–15 restoring original dddGEN, 7–17 restoring original DEFBOO,