____________________________________________________ VMS Version 5.5 Upgrade and Installation Manual Order Number: AA-NG61D-TE November 1991 This document contains step-by-step instructions for upgrading and installing Version 5.5 of the VMS operating system and VMS DECwindows software. Revision/Update Information: This manual supersedes the VMS Version 5.4 Upgrade and Installation Manual. Software Version: VMS Version 5.5 Digital Equipment Corporation Maynard, Massachusetts ________________________________________________________________ November 1991 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. © Digital Equipment Corporation 1991. All Rights Reserved. The postpaid Reader's Comments forms at the end of this document request your critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: ACMS, CDA, DBMS, DEC, DECdtm, DECnet, DECUS, DECwindows, DECwrite, DEQNA, DIGITAL, GIGI, HSC, LiveLink, LN03, MASSBUS, Micro/VAX, PrintServer, Q-bus, Rdb/VMS, ReGIS, ULTRIX, UNIBUS, VAX, VAXcluster, VAX RMS, VAX RALLY, VAX SQL, VAXserver, VAXstation, VMS, XUI, and the DIGITAL logo. The following are third-party trademarks: PostScript and Display PostScript are registered trademarks of Adobe Systems Incorporated. ZK5844 This document was prepared using VAX DOCUMENT, Version 2.0. _________________________________________________________________ Contents Preface................................................... ix Part I Installation and Upgrade Introduction 1 Installation and Upgrade Procedures 1.1 What Happens During an Installation.............. 1-1 1.2 What Happens During an Upgrade................... 1-3 Part II Installation Procedures 2 Before Installing VMS 2.1 Preinstallation Checklist........................ 2-1 2.2 The Distribution Media and the System Disk....... 2-3 2.3 Local Drives..................................... 2-3 2.4 HSC Drives....................................... 2-3 2.5 Preparing for a VMS Installation................. 2-4 2.5.1 Preparing for a VAXcluster Environment ........ 2-4 2.5.2 Preparing Tape and Disk Drives ................ 2-6 2.6 Information You Need During the Installation..... 2-7 3 Installing the VMS Operating System and DECwindows Software 3.1 Cautions and Restrictions........................ 3-2 3.2 Booting Standalone BACKUP........................ 3-3 3.3 Creating the System Disk......................... 3-5 3.4 Installing VMS DECwindows Software............... 3-15 3.5 Joining a VAXcluster............................. 3-17 3.6 Setting Passwords................................ 3-21 3.7 Applying the Mandatory Update.................... 3-23 iii 3.8 Registering Licenses............................. 3-24 3.9 Running AUTOGEN.................................. 3-29 4 After Installing VMS 4.1 Postinstallation Checklist....................... 4-1 4.2 Registering Your Licenses........................ 4-2 4.3 Setting Files NOMOVE for Additional System Disks............................................ 4-3 4.4 Backing Up Your System Disk...................... 4-3 4.5 Customizing the System........................... 4-3 4.6 Configuring and Starting DECnet-VAX.............. 4-4 4.7 Using or Disabling DECdtm Services............... 4-5 4.7.1 Using DECdtm Services ......................... 4-5 4.7.2 Disabling DECdtm Services ..................... 4-6 4.8 Testing the System............................... 4-6 4.9 Decompressing the System Libraries............... 4-6 4.10 Setting Up the System Messages Help Library...... 4-7 4.11 Removing Unwanted Files.......................... 4-9 4.12 Customizing DECwindows........................... 4-9 4.13 Starting the Queue Manager....................... 4-9 4.13.1 Standalone Queue Manager Upgrade .............. 4-10 4.14 Backing Up the Customized System Disk............ 4-11 4.15 Running AUTOGEN.................................. 4-11 Part III Upgrade Procedures 5 Overview of the Upgrade Procedure 5.1 What Happens During an Upgrade................... 5-3 5.2 Cautions and Restrictions........................ 5-3 5.3 Items You Need for the Upgrade................... 5-6 6 Before You Do an Upgrade 6.1 Preupgrade Checklist............................. 6-1 6.2 Understanding Version 5.5 of the VMS Operating System........................................... 6-3 6.3 Checking AUTOGEN Feedback Data................... 6-4 6.4 Backup Tasks..................................... 6-5 6.5 Preparing the System Disk........................ 6-6 6.6 Preparing the System............................. 6-11 6.7 Information You Need During the Upgrade.......... 6-12 iv 7 Upgrading a VAXcluster Environment 7.1 Performing a Concurrent Upgrade.................. 7-2 7.2 Restriction on a Rolling Upgrade From VMS Version 5.4-3 to VMS Version 5.5......................... 7-3 7.3 Performing a Rolling Upgrade..................... 7-4 7.3.1 Adding a VMS Version 5.5-Supported CPU ........ 7-7 8 Upgrading The VMS Operating System 8.1 Preparing to Boot from [SYSF].................... 8-2 8.2 Configuring Devices.............................. 8-3 8.3 Beginning the Upgrade Procedure.................. 8-3 8.4 Upgrade Phase 1.................................. 8-8 8.5 Upgrade Phase 2.................................. 8-19 8.6 Upgrade Phase 3.................................. 8-21 8.7 Upgrade Phase 4.................................. 8-22 8.8 Upgrade Phase 5.................................. 8-23 8.9 Upgrade Phase 6.................................. 8-23 9 After You Do an Upgrade 9.1 Postupgrade Checklist............................ 9-1 9.2 Replacing SYSUAF.DAT............................. 9-2 9.3 Setting Files NOMOVE for Additional System Disks............................................ 9-2 9.4 Examining AGEN$PARAMS.REPORT..................... 9-3 9.5 Checking the Size of System Files................ 9-3 9.6 Examining Your Command Procedures................ 9-4 9.7 Using or Disabling DECdtm Services............... 9-4 9.7.1 Using DECdtm Services ......................... 9-5 9.7.2 Disabling DECdtm Services .................... 9-5 9.8 Changing MODPARAMS.DAT........................... 9-6 9.9 Updating Your DECnet-VAX Configuration........... 9-6 9.9.1 Running NETCONFIG_UPDATE.COM .................. 9-6 9.9.2 Running UPDATE_CLUSTER_MEMBERS.COM ............ 9-10 9.10 Updating Your Console Media...................... 9-11 9.10.1 VAX 8530, 8550, 8810 (8700), 8820-N (8800) Computers...................................... 9-11 9.10.2 VAX 11/730, 750, 780, 785 and VAX 8200, 8250, 8300, 8350, 8600, 8650 Computers............... 9-13 9.10.3 VAX 9000 Computers ............................ 9-14 9.11 Decompressing the System Libraries............... 9-14 9.12 Setting Up the System Messages Help Library...... 9-15 v 9.13 Testing the System with UETP..................... 9-16 9.14 Increasing Free Space on the System Disk......... 9-17 9.14.1 Using VMSTAILOR, DECW$TAILOR, and DECW$MOTIF_TAILOR.............................. 9-17 9.14.2 Purging System Files .......................... 9-17 9.15 Checking Workstation Software.................... 9-18 9.16 Starting the Queue Manager....................... 9-18 9.16.1 Standalone Queue Manager Upgrade .............. 9-19 9.16.2 VAXcluster Queue Manager Upgrades ............. 9-20 9.17 Backing Up the System Disk....................... 9-22 9.18 Running AUTOGEN.................................. 9-22 Part IV Upgrade and Installation Final Tasks 10 Running UETP 10.1 Summary of UETP Operating Instructions........... 10-1 10.2 Logging In....................................... 10-4 10.2.1 SYSTEST Directories ........................... 10-5 10.3 Setting Up for UETP.............................. 10-5 10.3.1 The System Disk ............................... 10-6 10.3.2 Additional Disks .............................. 10-6 10.3.3 Magnetic Tape Drives .......................... 10-8 10.3.4 Tape Cartridge Drives ......................... 10-8 10.3.4.1 TLZ04 Tape Drives........................... 10-9 10.3.5 Compact Disc Drives ........................... 10-9 10.3.6 Optical Disk Drives ........................... 10-9 10.3.7 Terminals and Line Printers ................... 10-10 10.3.8 Ethernet Adapters ............................. 10-10 10.3.9 DR11-W Data Interface ......................... 10-10 10.3.10 DRV11-WA Data Interface ....................... 10-11 10.3.11 DR750 or DR780 (DR32 Interface) ............... 10-12 10.3.12 MA780 Multiport Memory ........................ 10-12 10.3.13 Second LPA11-K Device ......................... 10-13 10.3.14 Devices Not Tested ............................ 10-13 10.3.15 VAXcluster Testing ............................ 10-13 10.3.16 Testing A Small-Disk System ................... 10-15 10.3.17 DECnet-VAX Phase .............................. 10-15 10.4 Preparing Vector Processors and the VVIEF........ 10-16 10.5 Starting UETP.................................... 10-17 10.5.1 Running a Subset of Phases .................... 10-17 10.5.2 Single Run Versus Multiple Passes ............. 10-18 10.5.3 Defining User Load for Load Test .............. 10-18 vi 10.5.4 Report Formats ................................ 10-19 10.5.5 Termination of UETP ........................... 10-20 10.5.5.1 Using Ctrl/Y................................ 10-20 10.5.5.2 Using Ctrl/C................................ 10-21 10.6 Troubleshooting.................................. 10-22 10.6.1 Relationship of UETP to Error Logging and Diagnostics.................................... 10-22 10.6.2 Interpreting UETP Output ...................... 10-22 10.6.2.1 Defining a Remote Node for UETP Ethernet Testing..................................... 10-25 10.6.3 Log Files ..................................... 10-26 10.6.4 Possible UETP Errors .......................... 10-27 10.6.4.1 Wrong Quotas, Privileges, or Account........ 10-28 10.6.4.2 UETINIT01 Failure........................... 10-31 10.6.4.3 Device Allocated or in Use by Another Application................................. 10-33 10.6.4.4 Insufficient Disk Space..................... 10-33 10.6.4.5 Incorrect Setup of a VAXcluster............. 10-35 10.6.4.6 Problems During the Load Test............... 10-36 10.6.4.7 DECnet-VAX Error............................ 10-38 10.6.4.8 Errors Logged but Not Displayed............. 10-39 10.6.4.9 No PCB or Swap Slots........................ 10-39 10.6.4.10 Hangs....................................... 10-40 10.6.4.11 Lack of Default Access for the FAL Object... 10-41 10.6.4.12 Bugchecks and Machine Checks................ 10-41 10.7 UETP Tests and Phases............................ 10-42 10.7.1 Initialization Phase .......................... 10-42 10.7.2 Device Test Phase ............................. 10-43 10.7.2.1 How the Device Phase Works.................. 10-43 10.7.2.2 Running a Single Device Test................ 10-44 10.7.3 System Load Test Phase ........................ 10-48 10.7.4 DECnet-VAX Test Phase ......................... 10-49 10.7.4.1 Environment................................. 10-50 10.7.4.2 How the DECnet-VAX Phase Works.............. 10-50 10.7.5 Cluster-Integration Test Phase ................ 10-53 vii 11 Customizing VMS DECwindows Software 11.1 Controlling Startup of VMS DECwindows Software... 11-1 11.1.1 After an Upgrade .............................. 11-2 11.1.2 VMS DECwindows Logical Names Created At Startup........................................ 11-2 11.2 Customizing the Server Startup................... 11-3 11.3 Using TCP/IP with DECwindows..................... 11-10 11.4 Using Non-Digital Transports with DECwindows..... 11-10 11.5 Using the Example Transport...................... 11-11 11.6 Defining Print Formats........................... 11-12 11.7 Compiling Ada Source Files....................... 11-13 12 Using VMSTAILOR and DECW$TAILOR 12.1 Using VMSTAILOR.................................. 12-1 12.1.1 Removing VMS Files ............................ 12-3 12.1.2 Adding VMS Files .............................. 12-5 12.2 Using DECW$TAILOR................................ 12-9 12.2.1 Removing DECwindows Files ..................... 12-10 12.2.2 Adding DECwindows Files ....................... 12-11 A License Management Notes A.1 Registering Your Licenses........................ A-1 A.2 Using the License Unit Requirement Table (LURT).. A-3 A.3 License Management Facility Notes................ A-7 A.4 VMS Volume Shadowing License..................... A-9 A.5 Other System Integrated Product Licenses......... A-10 B Booting from [SYSF] During an Upgrade B.1 Micro/VAX and VAXstation Computers............... B-1 B.2 VAX 8530, 8550, 8810 (8700), 8820-N (8800) Computers........................................ B-1 B.3 VAX 8820, 8830, and 8840 Computers............... B-2 B.4 VAX-11/750, 8200, 8250, 8300, and 8350 Computers........................................ B-2 B.5 VAX-11/730, 11/780, 11/785, 8600, and 8650 Computers........................................ B-4 B.6 VAX 6000 Series.................................. B-6 B.7 VAX 9000 Series.................................. B-7 viii C VMS Library and Optional Save Set Files D DECwindows Software Components E Layered Products Availability Table Glossary Index Examples 12-1 Sample VMSTAILOR Session ...................... 12-6 12-2 Sample DECW$TAILOR Session .................... 12-13 Figures 1-1 Documentation Used to Perform a VMS Installation................................... 1-3 1-2 Documentation Used to Perform a VMS Upgrade ... 1-5 Tables 3-1 Installation Questions for CI-Only VAXclusters.................................... 3-18 3-2 Installation Questions for Local Area and Mixed-Interconnect VAXclusters................. 3-19 4-1 Software that Uses or Supports DECdtm Services....................................... 4-5 9-1 Software That Uses or Supports DECdtm Services....................................... 9-5 10-1 Device Tests .................................. 10-47 11-1 DECW$LOGICAL_NAMES ............................ 11-3 11-2 DECwindows Keymap ............................. 11-5 11-3 Print Dialog Box Logical Names ................ 11-12 A-1 The First VMS Version That Supports VAX Computers.................................. A-2 A-2 License Unit Requirement Table (LURT) ......... A-4 ix D-1 DECwindows Software Components ................ D-1 E-1 VMS Layered Products Currently Available for VMS Version V5.5............................... E-1 x _________________________________________________________________ Preface This manual is your primary source of information for upgrading or installing the VMS operating system. It contains step-by-step instructions for upgrading and installing Version 5.5 of the VMS operating system and VMS DECwindows. ______________________ IMPORTANT ______________________ If you received factory-installed software (VMS FIS) with your computer, refer to that user documentation first for information about starting up your system. If you subsequently need to upgrade or install the VMS operating system, use the supplied VMS documentation as follows: 1. Read all the release notes and release-specific cover letters (if any) included with your distribution kit. 2. If you are performing an upgrade or installation, follow the step-by-step upgrade or installation instructions in this guide. 3. When the instructions in this guide direct you to do so, refer to the installation and operations supplement for information specific to your VAX computer. 4. Store the hardcopy of this guide and the installation and operations supplement for your VAX processor in the binder that contains the VMS Release Notes. ______________________________________________________ ix Intended Audience This manual is intended for anyone responsible for installing or upgrading the VMS operating system. Read this manual before you install or upgrade to Version 5.5 of the VMS operating system. Document Structure This manual is divided into four parts. Part I Part I provides an overview of the upgrade and installation procedures. o Chapter 1 describes what happens during an installation or an upgrade and refers you to the appropriate documentation. Part II Part II provides step-by-step instructions for installing the VMS operating system and VMS DECwindows. o Chapter 2 describes the tasks you must perform before installing the VMS operating system. o Chapter 3 describes how to install Version 5.5 of the VMS operating system and VMS DECwindows on a VAXcluster or a standalone VAX computer. o Chapter 4 lists the tasks you should perform after you install the VMS operating system. Part III Part III provides step-by-step instructions for upgrading the VMS operating system. o Chapter 5 contains cautions, restrictions, and requirements for upgrading your VAX computer system. o Chapter 6 tells you how to prepare your system for an upgrade. o Chapter 7 contains additional information for upgrading a VAXcluster environment. o Chapter 8 describes the procedure for upgrading a standalone VAX computer. x o Chapter 9 lists the tasks you should perform after the upgrade. Part IV Part IV contains information on additional tasks you might perform after upgrading or installing the VMS operating system. o Chapter 10 describes the VMS User Environment Test Package (UETP) and how to use it to test the system. o Chapter 11 describes how to customize VMS DECwindows software. o Chapter 12 contains information on how to add or remove optional VMS and VMS DECwindows software by using VMSTAILOR and DECW$TAILOR. This manual also contains five appendixes, a glossary, and an index. o Appendix A provides notes and supplemental license management information to the upgrade and installation procedures. o Appendix B describes how to boot from SYSF on the different types of VAX computers. o Appendix C lists the files in the VMS library and optional save sets. o Appendix D lists VMS DECwindows files. o Appendix E outlines layered product support for Version 5.5 of the VMS operating system. o The Glossary defines terms. o The index provides a quick way to find information you need. Associated Documents The following documents might be useful: o The VMS upgrade and installation supplement for your VAX computer-Provides supplemental information that you will need during an installation or upgrade, such as booting the system and determining device names. xi o VMS Version 5.5 Release Notes-Provides notes on the various aspects of the VMS operating system. o VMS Version 5.5 New Features Manual-Describes new software features of VMS Version 5.5. o VMS VAXcluster Manual-Describes the procedures for setting up and managing VAXcluster configurations. o VMS License Management Utility Manual-Provides information about registering and managing licenses on a VMS system. o The hardware manuals supplied with your VAX computer provide detailed information about system hardware. Conventions The following conventions are used in this manual: Ctrl/x A sequence such as Ctrl/x indicates that you must hold down the key labeled Ctrl while you press another key or a pointing device button. In examples, a key name is shown enclosed in a box to indicate that you press a key on the keyboard. (In text, a key name is not enclosed in a box.) . . . In examples, a horizontal ellipsis indicates one of the following possibilities: o Additional optional arguments in a statement have been omitted. o The preceding item or items can be repeated one or more times. o Additional parameters, values, or other information can be entered. xii A vertical ellipsis indicates the . omission of items from a code . example or command format; the . items are omitted because they are not important to the topic being discussed. [] In format descriptions, brackets indicate that whatever is enclosed within the brackets is optional; you can select none, one, or all of the choices. (Brackets are not, however, optional in the syntax of a directory name in a file specification or in the syntax of a substring specification in an assignment statement.) red ink Red ink indicates information that you must enter from the keyboard or a screen object that you must choose or click on. For online versions of the book, user input is shown in bold. boldface text Boldface text represents the introduction of a new term or the name of an argument, an attribute, or a reason. Boldface text is also used to show user input in online versions of the book. UPPERCASE TEXT Uppercase letters indicate that you must enter a command (for example, enter OPEN/READ), or they indicate the name of a routine, the name of a file, the name of a file protection code, or the abbreviation for a system privilege. xiii - Hyphens in coding examples indicate that additional arguments to the request are provided on the line that follows. numbers Unless otherwise noted, all numbers in the text are assumed to be decimal. Nondecimal radixes-binary, octal, or hexadecimal-are explicitly indicated. This manual often refers to products by their abbreviated names. For example, the VAX 8200, VAX 8250, VAX 8300, and VAX 8350 computers are referred to collectively as the VAX 8200, 8250, 8300, 8350. The Micro/VAX 2000 computer is referred to as the Micro/VAX 2000, and so on. xiv Part I _________________________________________________________________ Installation and Upgrade Introduction Part I contains Chapter 1, which is an overview of the VMS installation and upgrade procedures. 1 _________________________________________________________________ Installation and Upgrade Procedures This chapter describes what happens during the installation and upgrade procedures. It also tells whether you should do an installation or an upgrade and refers you to the appropriate documentation. _______________________ Caution _______________________ You cannot install or upgrade to Version 5.5 of the VMS operating system on the following VAX computers and system disks: o Micro/VAX I, VAXstation I, VAXstation 8000, and VAX 11/725 computers o RK07, RL02, RC25, RD32, RD51, RD52, and RD53 system disks o You cannot install VMS DECwindows on an RZ23 system disk. ______________________________________________________ 1.1 What Happens During an Installation When you install the VMS operating system, the installation procedure does the following: o Initializes the system disk, overwriting its contents o Creates a system directory structure o Transfers the VMS files from the distribution media to the system disk 1-1 Installation and Upgrade Procedures 1.1 What Happens During an Installation Use the installation procedure under the following conditions: o If your VAX computer is new (it has never had any version of the operating system running on it, including factory installed software). o If your VAX computer is running a version of the VMS operating system and you want to overwrite the entire contents of the system disk (the VMS operating system, application software, and user files). o If you are running the VMS operating system, but cannot upgrade. For example, if you changed the names of system directories on the system disk, the upgrade procedure will not work correctly. You can either restore the system disk to its original directory structure, or you can reinstall the VMS operating system. _______________________ Caution _______________________ The installation procedure initializes the system disk, overwriting its contents. For this reason, use the installation procedure only on new VAX computers or if you want to destroy the contents of the system disk. ______________________________________________________ This manual contains step-by-step instructions for performing a VMS installation. However, you will need to refer to several different manuals 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. If you are installing the VMS operating system, go to Chapter 2. 1-2 Installation and Upgrade Procedures 1.2 What Happens During an Upgrade Figure 1-1 Documentation Used to Perform a VMS Installation 1.2 What Happens During an Upgrade 1-3 Installation and Upgrade Procedures 1.2 What Happens During an Upgrade When you upgrade the VMS operating system, the upgrade procedure does the following: o Deletes and purges some VMS files on the system disk but leaves all the user files intact o Transfers the new VMS files from the distribution media to the system disk o Merges some of the old VMS files and the new VMS files and replaces others o Cleans up files and structures used only during the upgrade In most cases, you can use the upgrade procedure to obtain a higher version of the VMS operating system. The upgrade procedure does not initialize the system disk. ________________________ Note ________________________ The upgrade procedure will not work correctly if you have changed the names of system directories on your system disk. Restore your VMS system disk to a standard directory structure before attempting an upgrade. ______________________________________________________ This manual contains step-by-step instructions for performing a VMS upgrade. However, you will need to refer to several different manuals before and during an upgrade. Figure 1-2 illustrates the major steps in an upgrade and the documents you will use to perform each step. If you are upgrading the VMS operating system, go to Chapter 5. 1-4 Installation and Upgrade Procedures 1.2 What Happens During an Upgrade Figure 1-2 Documentation Used to Perform a VMS Upgrade 1-5 Part II _________________________________________________________________ Installation Procedures Part II contains Chapter 2, Chapter 3, and Chapter 4, which describe how to install Version 5.5 of the VMS operating system and VMS DECwindows software on a VAXcluster or a single VAX computer. 2 _________________________________________________________________ Before Installing VMS This chapter describes how to prepare for a VMS installation. It also provides information you must know before installing the VMS operating system. This information includes the following: o Definition of the terms distribution media and system disk o Description of local and HSC (hierarchical storage controller) drives 2.1 Preinstallation Checklist Experienced system managers can use the following checklist to make sure they have completed all the necessary tasks before beginning the installation. System managers with less experience are advised to read this chapter beginning with Section 2.2 and to use the following checklist after completing the tasks in this chapter. < Make sure the hardware is installed and tested (described in the hardware manuals for your VAX computer). < Check the contents of your kit against the bill of materials. < Read Appendix A of this manual, the VMS Version 5.5 New Features Manual, and the VMS Version 5.5 Release Notes and any cover letters included with your kit. < Turn on the system (described in the VMS upgrade and installation supplement for your VAX computer). < Set up your system to record the installation procedure (described in the VMS upgrade and installation supplement for your VAX computer). 2-1 Before Installing VMS 2.1 Preinstallation Checklist < Read the "Before Installing VMS" section in the VMS upgrade and installation supplement for your VAX computer and perform the tasks described there. < If you have a VAX computer that uses console media, make sure you have the most recent version of the console media. < If you are installing the VMS operating system on a VAX computer in a VAXcluster environment, determine whether you want a CI-only, local area, or mixed-interconnect cluster (described in the VMS VAXcluster Manual). Obtain the following information, depending on the type of VAXcluster: o CI-Only VAXcluster: Get the allocation class value, DECnet node name, and DECnet node address for the computer. You also need to decide if you want a quorum disk and where the page and swap files for the system from which you are installing will be located. o Local Area and Mixed-Interconnect VAXclusters: Get the allocation class value, the DECnet node name, the DECnet node address, the cluster group number, and the cluster password. You also need to decide if you want a quorum disk and where the page and swap files for the system from which you are installing will be located. < Prepare the disk and tape drives (described in Section 2.5.2). < Make sure you have the following information (described in Section 2.6) readily available: o Passwords of at least 8 characters for the SYSTEM, SYSTEST, and FIELD accounts. o A list of optional VMS components you wish to install. o A list of optional DECwindows components you wish to install. o Information listed on Product Authorization Keys (PAKs) for your VMS license and any system-integrated products you will run. 2-2 Before Installing VMS 2.1 Preinstallation Checklist Once you have performed all the tasks in the checklist, go to Chapter 3 to begin the VMS installation. 2.2 The Distribution Media and the System Disk When you install the VMS operating system, you work primarily with the distribution media and the system disk. The distribution media is the compact disc or set of tapes that the VMS operating system is supplied on. The VMS operating system is supplied on the distribution media in a format that the processor cannot readily use. The installation procedure transfers the VMS operating system from the distribution media to your system disk and puts it in a format that the system can use. A system disk is the disk that contains (or will contain) the VMS operating system in a usable format. 2.3 Local Drives A drive that is connected directly to a VAX computer is referred to as a local drive. For example, a magnetic tape drive connected directly to a VAX computer is referred to as a local tape drive. If you have a standalone VAX computer, it is likely all the drives connected to the system are local drives. 2.4 HSC Drives A drive that is connected to an hierarchical storage controller (HSC) device is referred to as an HSC drive. For example, a magnetic tape drive connected to an HSC device is referred to as an HSC tape drive. If you have a VAXcluster environment, you can have local drives, HSC drives, or both, depending on the type of VAXcluster configuration. Check with the system manager if you are not sure what types of drives you are using for the installation. 2-3 Before Installing VMS 2.5 Preparing for a VMS Installation 2.5 Preparing for a VMS Installation To prepare for a VMS installation, you must perform the following tasks: 1. Make sure the hardware has been installed and checked for proper operation. For detailed information on the hardware, see the hardware manual for your VAX computer. 2. Make sure you have all the items listed on the bill of materials in the VMS distribution kit. If your kit is incomplete, notify Digital Software Supply, and request priority shipment of any missing items. 3. Before installing the VMS operating system, read Appendix A of this manual, the VMS Version 5.5 New Features Manual, and VMS Version 5.5 Release Notes and any cover letters included with your kit. 4. If necessary, read the section "Turning on the System" in the VMS upgrade and installation supplement for your VAX computer and turn on power to your computer. 5. Set up your system to record the installation procedure on either a hardcopy terminal or a printer attached to the console terminal. If you do not do this, the screen messages will be lost. You will need a transcript in case there is a problem during the installation. For more information, see the VMS upgrade and installation supplement for your computer. 6. Read the "Before Installing VMS" section in the VMS upgrade and installation supplement for your VAX computer. This section describes tasks specific to your VAX computer that you must complete before beginning the installation. 2.5.1 Preparing for a VAXcluster Environment If you are installing the VMS operating system in a VAXcluster environment, the installation procedure will ask you for information about your VAXcluster environment. Before proceeding, you must read the VMS VAXcluster Manual. If you have a clear understanding of VAXclusters before you do an installation, you are less likely to enter incorrect information during the installation. Entering incorrect information during the installation might force you to repeat the entire installation procedure. 2-4 Before Installing VMS 2.5 Preparing for a VMS Installation Following is a list of steps to obtain the VAXcluster information you need. For a complete explanation, see the VMS VAXcluster Manual. o Determine what type of configuration you want: CI-only, local area, or mixed-interconnect. These configuration types are distinguished by the interconnect device that the VAX computers in the cluster use to communicate with one another (CI, Ethernet, or both). o Determine the DECnet node name and node address for the VAX computer on which you are installing the VMS operating system. The network or system manager determines the DECnet node name and node address for each VAX computer on the network. See your system or network manager for this information, or see the Guide to DECnet-VAX Networking for more information on the DECnet node name and node address. o Determine the appropriate allocation class value for the VAX computer on which you are installing the VMS operating system. During the installation procedure you will be asked for the ALLOCLASS value of the VAX computer on which you are installing the VMS operating system. For example: Enter a value for ALICE's ALLOCLASS parameter: Refer to the VMS VAXcluster Manual for the rules on specifying allocation class values. Note that in a mixed-interconnect VAXcluster environment, the allocation class value cannot be zero. It has to be a value between 1 and 255. This is also true for any VAX computer that is connected to a dual-pathed disk. When you enter the allocation class value, the installation procedure uses it to automatically set the value of the SYSGEN parameter ALLOCLASS. o Determine whether you want a quorum disk in the cluster. o Determine where the page and swap files will be located for the system from which you are installing the VMS operating system software. o If you are going to set up either a local area or a mixed-interconnect cluster, determine which systems will be MOP servers, disk servers, and tape servers. 2-5 Before Installing VMS 2.5 Preparing for a VMS Installation o If you are going to set up either a local area or a mixed-interconnect cluster, determine the cluster group number and the cluster password. Use the following rules to determine the cluster group number and password: - Cluster group number-A number in the range from 1 to 4095 or 61440 to 65535. - Cluster password-Must be from 1 to 31 alphanumeric characters in length and can include dollar signs ($) and underscores (_). 2.5.2 Preparing Tape and Disk Drives Prepare your tape and disk drives as follows: 1. Decide which drive will hold the distribution tape and which drive will hold the system disk, and determine the device names for each drive. Write these names on a piece of paper. You will need this information throughout the installation. The "Before Installing the VMS Operating System" section in the VMS upgrade and installation supplement for your computer provides information on devices and device names. Do not place the distribution media in the drive at this point. 2. Follow this step only if the source-drive or target- drive is attached to an HSC. Otherwise, go to step 3. (Refer to the Glossary in this manual for descriptions of these and other terms.) Make sure that both the CI and HSC devices are turned on, and are on line. Obtain the HSC name from the system manager, or use the following procedure: a. Press Ctrl/C at the HSC console terminal. b. Enter the following command at the HSC> prompt and press RETURN: HSC> SHOW SYSTEM The information displayed includes the name of the HSC. For example: 2-6 Before Installing VMS 2.5 Preparing for a VMS Installation 19-OCT-1991 15:00:00.00 Boot:19-Oct-1991 11:31:11.41 Up: 51:00 Version V350 System ID: %X000000011 Name: KRUP . . . DISK allocation class = 1 TAPE allocation class = 0 Start command file Disabled SETSHO - Program Exit For more information, see the HSC User's Guide. 3. Place a scratch disk in the drive for the system disk (unless the system disk is fixed). 4. Spin up the disk that will be the system disk but do not write-protect it. 2.6 Information You Need During the Installation At different points during the installation, you will be prompted to supply information. Make sure you have this information readily available. The information you need includes the following: o Passwords for the SYSTEM, SYSTEST, and FIELD accounts. You will be prompted to type passwords of at least 8 characters for each of these accounts. o A list of optional VMS components you wish to install. You can save some space on your system disk if you choose not to install the library (VMS055.C) and optional (VMS055.D) VMS components. The installation procedure prompts you to specify whether you want to install each of these components. Appendix C lists the files included in these components. o A list of DECwindows components you want to install. If you want to save space on your system disk, you can choose not to install certain DECwindows components. Note that VMS DECwindows Motif software, which supersedes VMS DECwindows software, does not provide device support. If you plan to install VMS DECwindows software on a workstation or on a VAXcluster that includes workstations, Digital requires that you choose the device support files, even if you will install the VMS DECwindows Motif layered product. Otherwise, you are 2-7 Before Installing VMS 2.6 Information You Need During the Installation not required to install any VMS DECwindows components. The installation procedure prompts you to specify which of the following DECwindows components you want to install: device support, applications, programming support, and example files. Appendix D lists the files included in each of these components. o Information listed on Product Authorization Keys (PAKs) for your VMS license and any system-integrated products you will run. The installation procedure gives you the opportunity to register any licenses you have. To register your licenses, you will need to enter the information listed on the PAK for each license. Once you have completed these steps, use the checklist in Section 2.1 to make sure you have completed all the necessary tasks. Then go to Chapter 3 to begin the installation. 2-8 3 _________________________________________________________________ Installing the VMS Operating System and DECwindows Software Read the cautions and restrictions in Section 3.1, then follow the instructions in this chapter to install Version 5.5 of the VMS operating system and VMS DECwindows software. At certain points you will need to refer to the VMS upgrade and installation supplement for your VAX computer. _______________________ Caution _______________________ The software installation procedure overwrites the contents of the system disk. Use the installation procedure only if your VAX computer is new or if you want to destroy the contents of the system disk. If your system disk contains files that you want to save, you should upgrade to the new version of VMS. For an overview of the upgrade procedure, see Chapter 5. ______________________________________________________ During the installation procedure, the VMS files are transferred from the distribution kit to the system disk. You also have the option of installing VMS DECwindows software. The following tasks are described in this chapter: o Booting standalone BACKUP (Section 3.2) o Creating the system disk (Section 3.3) o Installing VMS DECwindows software (optional) (Section 3.4) o Joining a VAXcluster (optional) (Section 3.5) o Setting passwords (Section 3.6) o Applying the mandatory update (Section 3.7) o Registering licenses (Section 3.8) 3-1 Installing the VMS Operating System and DECwindows Software o Running AUTOGEN (Section 3.9) The instructions refer to the source-drive and the target- drive where: o The source-drive is the drive that holds the distribution kit. o The target-drive is the drive that holds the system disk. 3.1 Cautions and Restrictions Before you begin the VMS installation procedure, you must be aware of the following cautions and restrictions: o You cannot install Version 5.5 of the VMS operating system on the following VAX computers and system disks: - Micro/VAX I, VAXstation I, VAXstation 8000, and VAX 11/725 computers - RK07, RL02, RC25, RD32, RD51, RD52, and RD53 system disks - You cannot install VMS DECwindows on an RZ23 system disk. _______________________ Caution _______________________ Do not attempt to use VMSINSTAL with OPTION G to transfer VMS and VMS DECwindows save sets to another media type. If you perform an installation using such a kit, you will produce an unusable system. ______________________________________________________ o If you must move the VMS save sets from the distribution media to a disk that is not the system disk before beginning the installation, they must be in the [000000] directory on the disk, or the installation will fail. o If your system contains Digital Small Storage Interconnect (DSSI) disks attached to a KFQSA controller, you will notice a change in the device names for DSSI disks attached to KFQSA controllers. 3-2 Installing the VMS Operating System and DECwindows Software 3.1 Cautions and Restrictions When you boot standalone BACKUP, it will display the devices on your system using the new device naming scheme. Use the new device names throughout the installation and after you complete the installation. For complete information on the naming scheme for DSSI disks attached to KFQSA controllers, see the VMS Version 5.5 Release Notes. 3.2 Booting Standalone BACKUP Complete the following steps to boot standalone BACKUP: 1. Each piece of media in the distribution kit has a label that indicates its contents. Place the media that contains standalone BACKUP in the source-drive or the console drive. If your kit contains standalone BACKUP on more than one piece of media, put the first piece in the source-drive or the console drive. For example, there are two tape cartridges in a TK50 kit. Standalone BACKUP is on the same tape cartridge as VMS DECwindows. This tape cartridge is labeled VMS V5.5 BIN TK50 2/2 DECWINDOWS & S/A BKUP. To begin the installation, put this tape cartridge in the appropriate drive. 2. Follow the instructions in "Booting Standalone BACKUP" in the VMS upgrade and installation supplement for your VAX computer. If you are not using an InfoServer, boot standalone backup and go to step 3 of this procedure. If you are using the InfoServer to boot standalone BACKUP from a compact disc, enter your VAX processor boot command by using the designator for the Ethernet adapter in the boot path and, except for the VAX 9000 computer, add the /R5:100 qualifier to the boot command. For example, on a VAX 6000 computer: >>> B/R5:100/X:D/B:6 ET0 Booting on the VAX 9000 computer is different from the other computers. For example, if you are booting off the DEMNA, first edit MNACDBOO.CMD and add a line that deposits the correct value to R1. Then enter BOOT MNACD at the prompt: >>> BOOT MNACD 3-3 Installing the VMS Operating System and DECwindows Software 3.2 Booting Standalone BACKUP During an InfoServer boot, the procedure prompts you for a file name that contains an ISL (initial system load) boot program instead of a VMB program. Select one of the two files as follows: o ISL_SVAX_055 o ISL_LVAX_055 Use the following table to determine which file name and boot path designator to use for your processor. Note that the VAX 9000 computer has the ISL file data built in its VMB image that is run from the console. ________________________________________________________ Processor_____ISL_File________Boot_Path_Designator______ VAX 6000s ISL_LVAX_055 EX0 (DEMNA), FX0 (DEMFA), ET0 (DEBNI) (DEBNA) VAX 9000s EX0 (DEMNA), FX0 (DEMFA) VAX 4000s ISL_SVAX_055 EZ0 (SGEC), XQ0 (DELQA) VAX 3000s ISL_SVAX_055 ES0 (LANCE), XQ0 (DELQA) Micro/VAXs ISL_SVAX_055 ES0 (LANCE), XQ0 (DELQA) VAXstations ISL_SVAX_055 ES0 (LANCE) VAXft 110, ISL_SVAX_055 EP0 (LANCE) 310, 410, 610,_and_612____________________________________________ For example, on a VAX 6000 computer: Loading system software. Filename: ISL_LVAX_055 The InfoServer ISL program then displays the following menu: Network Initial System Load Function Version 1.1 3-4 Installing the VMS Operating System and DECwindows Software 3.2 Booting Standalone BACKUP FUNCTION FUNCTION ID 1 - Display Menu 2 - Help 3 - Choose Service 4 - Select Options 5 - Stop Enter a function ID value: For further information select 2 for help. After you boot standalone BACKUP (from a local drive or from InfoServer), continue to step 3 of this procedure. 3. After you boot standalone BACKUP you will see the following display: %BACKUP-I-IDENT, standalone BACKUP V5.5; the date is 19-JUL-1991 15:00 $ ________________________ Note ________________________ If you have a tape cartridge kit, remove the tape cartridge 2/2 from the drive after you boot standalone BACKUP. Put the tape cartridge that contains the VMS operating system in the drive. The VMS tape cartridge is labeled VMS V5.5 BIN TK50 1/2 VMS BINARY. ______________________________________________________ 4. Follow the instructions in Section 3.3 to create the system disk. 3.3 Creating the System Disk This section describes the steps for transferring the VMS files from the distribution kit to your system disk. The VMS files are stored on the distribution kit as three save sets: VMS055.B, VMS055.C, and VMS055.D, which were called the required, library, and optional save sets. ________________________ Note ________________________ The VMS Version 5.5 magnetic tape kit contains VMS and VMS DECwindows software on three tapes. The first tape contains the VMS055.B save set. The second tape 3-5 Installing the VMS Operating System and DECwindows Software 3.3 Creating the System Disk contains the VMS055.C and VMS055.D save sets. The third tape contains the VMS DECwindows software. The VMS Version 5.5 TK50 tape kit contains VMS and VMS DECwindows software on two tape cartridges. The first cartridge contains the VMS VMS055.B, VMS055.C and VMS055.D save sets. The second cartridge contains standalone BACKUP and VMS DECwindows software. ______________________________________________________ 1. If you have not already done so, determine the device names for the source-drive and the target-drive. 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 are connected to an HSC, you also need the name of the HSC. (To determine the value for hsc-name, see Section 2.5.2.) If you need more information about determining the device names for your system, refer to the VMS upgrade and installation supplement for your VAX computer. 2. Each piece of media in the distribution kit has a label that indicates its contents. Place the media that contains the VMS operating system in the source- drive. If your VMS distribution kit consists of more than one piece of media, insert the first piece of media in the source-drive. For example, if you have a TK50 tape cartridge kit, make sure the tape labeled VMS V5.5 BIN TK50 1/2 VMS BINARY is in the source-drive. 3. Enter a BACKUP command in the following format to transfer the VMS055.B save set to your system disk, $ BACKUP/IMAGE/VERIFY [hsc-name]source-drive:VMS055.B/SAVE_SET [hsc-name]target-drive: Substitute the appropriate device names for hsc-name (if appropriate), source-drive and target-drive. Make sure you put a colon (:) after each device name and that you use zeros rather than the letter "O" in the device names and in VMS055. The square brackets ([]) indicate that you need the hsc-name only if the device is connected to an HSC. 3-6 Installing the VMS Operating System and DECwindows Software 3.3 Creating the System Disk For example, if your system has the following configuration: o A source-drive that is a local TU80 magnetic tape drive with a device name of MUA0 and o A target-drive that is an RA60 disk drive with a device name of DJA1 enter the following command and press the Return key: $ BACKUP/IMAGE/VERIFY MUA0:VMS055.B/SAVE_SET DJA1: If your system has the following configuration: o A source-drive that is a local tape cartridge drive with a device name of MUC6 or o 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:VMS055.B/SAVE_SET YOURS$DUA1: 4. The procedure transfers the VMS055.B save set from the distribution kit to the system disk.[1] The amount of time this takes varies depending upon the type of VAX computer and distribution media you have. During the process the command displays the following message: %BACKUP-I-STARTVERIFY, starting verification pass This message indicates that the VMS055.B save set has been transferred to the system disk and the files are being checked for errors. If, instead, you see a message similiar to the following, you might have the wrong volume of the distribution kit in the source drive: ____________________ [1] The BACKUP command creates a system disk that includes a set of volume parameters provided by Digital, including CLUSTER_SIZE (disk access scheme). For more information, see the VMS upgrade and installation supplement for your VAX computer. 3-7 Installing the VMS Operating System and DECwindows Software 3.3 Creating the System Disk % BACKUP-F-OPENIN, error opening MUA0:[000000]VMS055.B; as input - SYSTEM-W-NOSUCHFILE, no such file . . . If you do want to perform another standalone BACKUP operation, ensure the standalone BACKUP volume is online and ready. Enter "YES" to continue: If the procedure displays the previous messages, remove the distribution volume from the drive and replace it with the correct volume as described in step 2. Then type YES, press Return, and go back to step 3. When standalone BACKUP is done checking the files, the procedure displays the following message: %BACKUP-I-PROCDONE, Operation completed. Processing finished at 19-JUL-1991 15:00 If you do not want to perform another standalone BACKUP operation, use the console to halt the system. If you do want to perform another standalone BACKUP operation, ensure the standalone application volume is online and ready. Enter "YES" to continue: 5. Halt the system and boot the new system disk, as described in the VMS upgrade and installation supplement for your VAX computer. After you boot the new system disk, return to this manual for the next step in the VMS Version 5.5 installation procedure. 6. When the boot is completed, the procedure displays a message and prompts you to enter the date and time. Enter the date and time using the 24-hour clock format and press Return. For example: VAX/VMS Version BI55-xxx Major version id = 1 Minor version id = 0 VAX/VMS V5.5 Installation Procedure Model: VAX 6000-410 System device: RA60 - DJA3 Free blocks: 359916 CPU type: 11-02 * Please enter the date and time (DD-MMM-YYYY HH:MM): 19-JUL-1991 15:00 3-8 Installing the VMS Operating System and DECwindows Software 3.3 Creating the System Disk STDRV-I-STARTUP, VMS startup begun at 19-JUL-1991 15:00:00.59 %SET-I-NEWAUDSERV, identification of new audit server process is 00000027 %LICENSE-F-EMTLDB, license database contains no license records %LICENSE-E-NOAUTH, DEC VAX-VMS use is not authorized on this node -%LICENSE-F-NOLICENSE, no license is active for this software product -%LICENSE-I-SYSMGR, please see your system manager Startup processing continuing... %%%%%%%%%%% OPCOM 19-JUL-1991 15:00:00.00 %%%%%%%%%%% . . . ________________________ Note ________________________ The procedure displays error messages stating that the VMS license is not registered. At this point, you can ignore these messages. You will be given the opportunity to register licenses later in the procedure. For more information about registering your licenses, see Appendix A and the VMS License Management Utility Manual. ______________________________________________________ You can also ignore the following messages: %SYSGEN-W-OPENIN, error opening SYS$SYSROOT:[SYSEXE]VEDRIVER.EXE; as input %SYSGEN-E-FNF, file not found 7. The procedure prompts you to specify the volume label of the system disk. A volume label is the name the VMS operating system uses to refer to the system disk. You can press Return to accept the default volume label, VAXVMSRL055, or you can enter a volume label of your choice. The volume label can be 1 to 12 characters long; do not use spaces. For example: If this system disk is to be used in a cluster with multiple system disks, then each system disk must have a unique volume label. Any nodes having system disks with duplicate volume labels will fail to boot into the cluster. You may indicate a volume label of 1 to 12-characters in length. If you wish to use the default name of VAXVMSRL055 just press Return in response to the next question. * Enter the volume label for this system disk [VAXVMSV055]: SYSDSK1 3-9 Installing the VMS Operating System and DECwindows Software 3.3 Creating the System Disk 8. The procedure prompts you to specify which drive holds the distribution kit. Enter the device name of the source-drive. For example, if you are not using the InfoServer and the source-drive is a tape cartridge drive with a device name of MUA0, type "MUA0" and press Return. * Enter the name of the drive holding the VMS distribution media: MUA0 * Is the VMS media ready to be mounted? [N] YES %MOUNT-I-MOUNTED, VMS055 mounted on _MUA0: If you are not using the InfoServer, continue to the next step. If you are using an InfoServer, enter DAD1n:. * Enter the volume label for this system disk [VAXVMSRL055]: SYSDSK1 * Enter name of drive holding the VMS distribution media: DAD1: The procedure then asks you: * Enter the InfoServer service name [VMS055]: * Enter the InfoServer work group number [0]: Press Return as a response to both of these prompts. The InfoServer group number was determined when the InfoServe ISL program was run and you made a selection from the displayed menu (see Section 3.2). If the answer to the group number is incorrect, the procedure displays: InfoServer work group number must be in the range 0-1023. The procedure then prompts: * Is the VMS media ready to be mounted? [N]: Y %MOUNT-I-MOUNTED, VMS055 mounted on _DAD1: 9. The procedure displays information about VMS and DECwindows files that are optional and the remaining amount of disk space. The information is similiar to the following: Select Optional software you wish to have installed. You can choose to Install one or more of the following VMS and/or DECwindows components: 3-10 Installing the VMS Operating System and DECwindows Software 3.3 Creating the System Disk o VMS library - 32000 blocks o VMS optional - 16500 blocks o DECwindows device support - 21400 blocks o DECwindows applications - 12000 blocks o DECwindows programming support - 26500 blocks o DECwindows example files - 3500 blocks Space remaining: 359715 blocks You must indicate which of the options you want to install. If you require network support, you must select the VMS library component. ________________________ NOTE ________________________ If you do not install the optional VMS and DECwindows components at this time, you can install them after the installation by using the VMSTAILOR and DECW$TAILOR utilities. Please note that, for TK50 tape cartridges, it is quicker to install VMS and DECwindows software during the installation than to add software after the installation with a tailoring utility. For information on using VMSTAILOR and DECW$TAILOR, see Chapter 12. ______________________________________________________ To select the options you want to install, follow the instructions displayed by the procedure. For example: * Do you want to install the VMS library files? (Y/N) 10.The contents of the VMS055.C save set are listed in Appendix C. If you want to install the VMS055.C files, type Y (for YES) and press Return. If you do not want to install the VMS055.C files, type N (for NO) and press Return. The procedure displays the following message: * Do you want to install the VMS optional files? (Y/N) 11.The contents of the VMS055.D save set are listed in Appendix C. If you want to install the VMS055.D files, type Y and press Return. If you do not want to install the VMS055.D files, type N and press Return. 3-11 Installing the VMS Operating System and DECwindows Software 3.3 Creating the System Disk The procedure displays some messages about DECwindows software. You can provide DECwindows support now, or you can use the DECW$TAILOR utility to provide or remove DECwindows support after the upgrade. NOTE: Some media, TK50s in particular, can be very slow when tailoring on files. You might want to provide DECwindows options now and tailor off unwanted files later. * Do you want to provide optional DECwindows support? (Y/N) 12.You must indicate if you wish to install DECwindows software. If VMS DECwindows Motif is going to be installed, you should choose to install only the DECwindows device support. (Step b. tells you how to choose selected VMS DECwindows options.) ________________________ Note ________________________ If you are installing this kit on a workstation or on a VAXcluster that includes workstations, Digital requires that you choose the device support files, even if you will install the VMS DECwindows Motif layered product. VMS DECwindows Motif software supersedes the VMS DECwindows software supplied with VMS Version 5.5, but it does not provide device support. The VMS DECwindows Motif Installation Guide describes the VMS DECwindows Motif installation procedure. ______________________________________________________ Appendix D lists the DECwindows software components. If you do not want to install VMS DECwindows software, type N, press Return, and go to step 13. Note that VMS DECwindows software is useful, even on a nonworkstation VAX computer, because you can run VMS DECwindows applications on a nonworkstation VAX computer and display them on a workstation. 3-12 Installing the VMS Operating System and DECwindows Software 3.3 Creating the System Disk If you want to install VMS DECwindows software, follow steps a and b: a. Type Y and press Return. The procedure displays the following message: You can install either the complete DECwindows kit or selected portions of it. A complete installation requires 56000 blocks. If you want to perform a partial installation, you can choose to install one or more of the following DECwindows components: o DECwindows device support - 13500 blocks o DECwindows applications - 12000 blocks o DECwindows programming support - 27000 blocks o DECwindows example files - 3500 blocks * Do you want to install complete DECwindows support? (Y/N) b. To install the complete DECwindows kit, type Y and press Return. The procedure displays the amount of remaining disk space and the VMS DECwindows options that will be provided. To install selected portions of the VMS DECwindows kit, type N and press Return. The procedure displays information about the amount of space you need on the system disk for each option. As you choose your options, the procedure calculates the amount of space that would be left on the system disk. Before you select the VMS DECwindows options that you want to install, consider the following: o Device support files-If you are installing VMS DECwindows on a workstation or on a VAXcluster that includes workstations, Digital requires that you choose the device support files, even if you will install the VMS DECwindows Motif layered product. Otherwise, you do not need them. In selecting the device support files, you automatically get applications files and 75 dots /inch video font files, and you will be prompted to indicate if you want to install 100 dots/inch video font files. 3-13 Installing the VMS Operating System and DECwindows Software 3.3 Creating the System Disk o Applications files-VMS DECwindows provides a variety of applications including the following: Bookreader, Calculator, Calendar, Cardfiler, CDA Document Viewer, Clock, EVE Text Editor, FileView, Mail, Notepad Text Editor, Paint Graphics Editor, DECterm, the Session Manager, and the Window Manager. If you are installing VMS DECwindows on a VAXstation, you need these files. They are also useful on a nonworkstation VAX computer. o Video 100 dots/inch font files-If you have a workstation monitor capable of displaying 100 dots/inch (for example, a VR150, VR160, or VR295), selecting 100 dots/inch fonts will give you a more readable display when you run VMS DECwindows applications. If your workstation monitor cannot display 100 dots/inch fonts (for example, a VR260 or VR290), you can save disk space by not selecting this option. For more information on the capabilities of your particular monitor, see the owner's guide for your monitor. If you select the device support option you will be prompted to specify if you also want to select the 100 dots/inch files. o Programming support files-The VMS DECwindows programming support files are needed only to develop applications and are not required to run VMS DECwindows applications. Support files are supplied for the following VAX programming languages: Ada, BASIC, BLISS, C, FORTRAN, MACRO, Pascal, and PL/1. In addition, support files are supplied for programming in the C language. The files use conventions and standards developed at the Massachusetts Institute of Technology. o DECwindows example files-The VMS DECwindows example files provide examples of files used to develop various DECwindows applications. 13.The procedure gives you the opportunity to change your mind before proceeding by displaying the following message: * Is this correct? (Y/N) 3-14 Installing the VMS Operating System and DECwindows Software 3.3 Creating the System Disk If you are installing from magnetic tape, you will need to put tape 2/3 in the drive now. If you answer YES to this prompt, the installation procedure begins restoring the VMS055.C save set (if you elected to install it). If you answer NO to this prompt, you can respecify the VMS and DECwindows options that you want to install. 14.If you elected to install the VMS055.C and VMS055.D save sets, the procedure displays the following messages: Restoring VMS library save set ... %BACKUP-I-STARTVERIFY, starting verification pass Restoring VMS optional save set ... %BACKUP-I-STARTVERIFY, starting verification pass You can use the VMSTAILOR utility to remove the optional VMS files that you do not need after you finish the installation. For more information on removing files with VMSTAILOR see Chapter 12. 15.If you are installing VMS DECwindows software, go to Section 3.4. If you are not installing VMS DECwindows software, go to Section 3.5. 3.4 Installing VMS DECwindows Software If you are installing VMS DECwindows software, complete the following steps: 1. If you are not installing from a compact disc (you can also install from a local compact disc, not only from an InfoServer), remove the tape that contains the VMS operating system from the source-drive when you see a message similar to the following: You may now remove the distribution kit from MUA0:. Load the DECwindows distribution kit. 2. Put the tape that contains the VMS DECwindows software in the source-drive. If you are installing from magnetic tape, this tape is labeled 3/3. If you are installing from a TK50 cartridge, the cartridge is labeled 2/2. 3-15 Installing the VMS Operating System and DECwindows Software 3.4 Installing VMS DECwindows Software 3. Type the device name of the source-drive and press Return. For example: * Enter name of the drive holding the DECwindows distribution media: MUA0 * Is the DECwindows media ready to be mounted? [N] YES Note that if you are using an InfoServer, enter DAD1: as the name of the source drive. 4. The procedure installs the VMS DECwindows options that you specified and displays messages similar to the following: %MOUNT-I-MOUNTED, DECW55 mounted on _MUA0: Restoring DECwindows applications save set ... %BACKUP-I-STARTVERIFY, starting verification pass Restoring DECwindows device support save set ... %BACKUP-I-STARTVERIFY, starting verification pass Restoring DECwindows 75DPI fonts save set ... %BACKUP-I-STARTVERIFY, starting verification pass Restoring DECwindows 100DPI fonts save set ... %BACKUP-I-STARTVERIFY, starting verification pass Restoring DECwindows programming support save set ... %BACKUP-I-STARTVERIFY, starting verification pass Restoring DECwindows examples save set ... %BACKUP-I-STARTVERIFY, starting verification pass The VMS DECwindows files are listed in Appendix D. You can use the DECwindows tailoring utility, DECW$TAILOR, to remove the VMS DECwindows files you do not need after you finish the installation. For more information on removing files with DECW$TAILOR, see Chapter 12. 5. If you installed VMS DECwindows options, the procedure displays a message similar to the following: You may now remove the DECwindows distribution kit from MUA0: Remove the distribution media from the drive. 3-16 Installing the VMS Operating System and DECwindows Software 3.5 Joining a VAXcluster 3.5 Joining a VAXcluster The installation procedure now asks you whether you are installing the VMS operating system in a VAXcluster environment. If you are installing a VAXcluster, the procedure asks a series of questions about your configuration. You might need to refer to the VMS VAXcluster Manual to answer these questions. 1. The procedure displays the following messages: Creating [VMS$COMMON] directory tree In a cluster, you can run multiple systems sharing all files except PAGEFILE.SYS, SWAPFILE.SYS, SYSDUMP.DMP and VAXVMSSYS.PAR. * Will this node be a cluster member? (Y/N) If you are installing a standalone system, type N and press Return. If you are installing a VAXcluster, type Y and press Return. If you answer YES to the VAXcluster question, you must have a VAXcluster license. 2. If you are installing the VMS operating system in a VAXcluster environment, go to step 3. If you are installing the VMS operating system on a standalone system, go to step 5. 3. The procedure displays the following message: Now configuring system to be a cluster member. 4. The installation procedure displays several questions about the configuration of your VAXcluster. Your answers to these questions depend on whether you want to install a CI-only, local area, or mixed interconnect VAXcluster. Before answering these questions, you must determine which type of cluster you want to install. For a complete description of VAXcluster types, see the VMS VAXcluster Manual. Table 3-1 lists the questions you are asked if you want a CI-only VAXcluster. Table 3-2 lists the questions you are asked if you want a local area VAXcluster or a mixed-interconnect VAXcluster. Typical responses are explained in the tables. Refer to the appropriate table to enter the information for your VAXcluster 3-17 Installing the VMS Operating System and DECwindows Software 3.5 Joining a VAXcluster configuration. When you have answered all the questions, go to Section 3.6. Table_3-1_Installation_Questions_for_CI-Only_VAXclusters_________ Question______________________How_to_Respond_____________________ Will this node be a cluster Enter Y. member (Y/N)? What is the node's DECnet Enter the DECnet node name-for node name? example, KRUP. The DECnet node name may be from 1 to 6 alphanumeric characters in length and cannot include dollar signs or underscores. What is the node's DECnet Enter the DECnet node address-for node address? example, 2.2. Will the Ethernet be used Enter N. A CI-only VAXcluster does for cluster communications not use the Ethernet for cluster (Y/N)? communications. Will KRUP be a disk server Enter Y if you want local disks to (Y/N)? be served to the cluster. If you enter Y, the procedure will ask if the node will serve HSC disks. Enter N to this second question. HSC disks are available to all nodes in a CI-cluster. Refer to the VMS VAXcluster Manual for information on served cluster disks. Enter a value for KRUP's If the system is connected to ALLOCLASS parameter: a dual-ported disk, enter the appropriate allocation class value (it must be a value between 1 and 255). Otherwise, enter 0. For information on selecting the ALLOCLASS parameter, see the VMS VAXcluster Manual. (continued on next page) 3-18 Installing the VMS Operating System and DECwindows Software 3.5 Joining a VAXcluster Table_3-1_(Cont.)_Installation_Questions_for_CI-Only_VAXclusters_ Question______________________How_to_Respond_____________________ Does this cluster contain a Enter Y or N, depending on your quorum disk (Y/N)? configuration. If you enter Y, the procedure asks for the name of the quorum disk. Enter the device name of the quorum disk. Refer to the VMS VAXcluster Manual for ______________________________information_on_quorum_disks._______ Table 3-2 Installation Questions for Local Area and Mixed- __________Interconnect_VAXclusters_______________________________ Question______________________How_to_Respond_____________________ Will this node be a cluster Enter Y. member (Y/N)? What is the node's DECnet Enter the DECnet node name-for node name? example, KRUP. The DECnet node name may be from 1 to 6 alphanumeric characters in length and may not include dollar signs or underscores. What is the node's DECnet Enter the DECnet node address-for node address? example, 2.2. Will the Ethernet be used Enter Y. The Ethernet is required for cluster communications for cluster (SCS internode) (Y/N)? communications in local area and mixed-interconnect VAXclusters. Enter this cluster's group Enter a number in the range from 1 number: to 4095 or 61440 to 65535. Enter this cluster's Enter the cluster password. The password: password must be from 1 to 31 alphanumeric characters in length and may include dollar signs and underscores. (continued on next page) 3-19 Installing the VMS Operating System and DECwindows Software 3.5 Joining a VAXcluster Table 3-2 (Cont.) Installation Questions for Local Area and __________________Mixed-Interconnect_VAXclusters_________________ Question______________________How_to_Respond_____________________ Reenter this cluster's Reenter the password. password for verification: Will KRUP be a disk server Enter Y. In local area and mixed- (Y/N)? interconnect VAXclusters, the system disk is always served to the cluster. Refer to the VMS VAXcluster Manual for information on served cluster disks. Will KRUP serve HSC disks Enter a response appropriate for (Y)? your configuration. Enter a value for KRUP's Enter the appropriate allocation ALLOCLASS parameter: class value. If you have a mixed- interconnect VAXcluster, the value must be between 1 and 255; you cannot enter 0. Does this cluster contain a Enter Y or N, depending on your quorum disk (Y/N)? configuration. If you enter Y, the procedure asks for the name of the quorum disk. Enter the device name of the quorum disk. Refer to the VMS VAXcluster Manual for ______________________________information_on_quorum_disks._______ 5. If you installed VMS DECwindows and indicated that the node is not part of a VAXcluster, the procedure displays the following message: * Do you want DECwindows as the default windowing system? (Y/N) Depending on your preference, type Y or N and press Return. If you type Y, the procedure sets the SYSGEN parameter WINDOW_SYSTEM to one for DECwindows. If you type N, the procedure sets the SYSGEN parameter WINDOW_ SYSTEM to zero. For information on the WINDOW_SYSTEM parameter, see the VMS System Generation Utility Manual. 3-20 Installing the VMS Operating System and DECwindows Software 3.6 Setting Passwords 3.6 Setting Passwords Next, the installation procedure prompts you to set passwords for certain accounts and uses this information to create a rights database. 1. The procedure asks you for passwords for the SYSTEM, SYSTEST, and FIELD accounts. Passwords must be at least 8 characters in length; they do not appear on the display. Press Return after you enter each one. After you enter the passwords, the procedure checks each one to make sure it meets the requirements for a good password. For example: Now we will ask you for new passwords for the following accounts: SYSTEM, SYSTEST, FIELD Passwords must be a minimum of 8 characters in length. All passwords will be checked and verified. Any passwords that can be guessed easily will not be accepted. * Enter password for SYSTEM: * Re-enter for verification: %UAF-I-MDFYMSG, user record(s) updated %VMS-I-PWD_OKAY, account password for SYSTEM verified * Enter password for SYSTEST: * Re-enter for verification: %UAF-I-MDFYMSG, user record(s) updated %VMS-I-PWD_OKAY, account password for SYSTEST verified The SYSTEST_CLIG account will be disabled. You must re-enable it before running UETP but do not assign a password. * Enter password for FIELD: * Re-enter for verification: %UAF-I-MDFYMSG, user record(s) updated %VMS-I-PWD_OKAY, account password for FIELD verified If you do not get password errors, go to step 2. If you enter a password incorrectly or if the password is too easy to guess, the procedure displays error messages similar to the following: %VMS-I-PWD_INVALID, account password for SYSTEST is invalid %VMS-I-PWD_WEAK, password is too easy to guess Because of the preceding error, you must take action to secure this account. You must either disable this account, change its password, or do both. 3-21 Installing the VMS Operating System and DECwindows Software 3.6 Setting Passwords When the procedure asks if you want to disable the account, type N and press Return. When the procedure asks if you want to enter a new password, type Y and press Return. Then enter a new password. For example: Do you want to disable this account (Y/N)? N Do you want to change the account password (Y/N)? Y You must now select a new primary password for the SYSTEST account. The password you select must be at least 8 characters in length and may not be the same as the name of the account: New password: Verification: %UAF-I-MDFYMSG, user record(s) updated %VMS-I-PWD_SET, primary password for account SYSTEST set 2. After you have entered the passwords, the procedure creates your RIGHTS database and displays the following message: Creating RIGHTS database file, SYS$SYSTEM:RIGHTSLIST.DAT Ignore any "-SYSTEM-F-DUPIDENT, duplicate identifier" errors . . . 3. After the procedure creates the RIGHTS database, it displays the following messages: After the installation finishes, you may want to do one or more of the following tasks: o DECOMPRESS THE SYSTEM LIBRARIES - For space considerations, many of the system libraries are shipped in a data-compressed format. If you have enough disk space, you may decompress them for faster access. To data expand the libraries, type: $ @SYS$UPDATE:LIBDECOMP.COM If you choose not to decompress these libraries you will experience slower response with the HELP and LINK commands. o BUILD A STANDALONE BACKUP KIT - You can build a standalone backup kit using the procedure described in your VMS upgrade and installation supplement for your VAX computer. 3-22 Installing the VMS Operating System and DECwindows Software 3.6 Setting Passwords o TAILOR THE SYSTEM DISK - You may want to review the files provided or not provided during this installation. IF you find there are files you want to remove from the system disk (TAILOR OFF) or files you want to add (TAILOR ON), then use the following utilities to perform the desired tailoring. VMS tailoring: $ RUN SYS$UPDATE:VMSTAILOR DECwindows tailoring: $ RUN SYS$UPDATE:DECW$TAILOR For information on using VMSTAILOR or DECW$TAILOR, see Chapter 12. 3.7 Applying the Mandatory Update After the messages about postinstallation tasks are displayed, the procedure displays the following message: Continuing with VAX/VMS V5.5 installation procedure. Configuring all devices on the system... You must now install the Mandatory Update, which can be found on a separate distribution volume. . . . Follow these steps to apply the mandatory update: 1. The procedure asks you for the device name of the drive that contains the mandatory update. Type the device name of the drive where you will put the disk or tape that contains the mandatory update. For example, if the mandatory update is on a TK50 drive named MUA0, enter the following and press the Return key: *Where will the distribution volumes be mounted: MUA0 The procedure displays the following message: Please mount the first volume of the set on MUA0:. *Are you ready? 2. Place the tape labeled VMS V5.5 MANDATORY UPDATE in the appropriate drive. If you are installing from a compact disc, the mandatory update is stored on the same compact disc as the rest of the VMS software. When you are ready 3-23 Installing the VMS Operating System and DECwindows Software 3.7 Applying the Mandatory Update to continue, type Y and press Return. The procedure displays the following series of messages: %MOUNT-I-MOUNTED, VMSMUP mounted on _CSA1: The following products will be processed: VMSMUP V5.5 Beginning installation of VMSMUP V5.5 at 15:00 %VMSINSTAL-I-RESTORE, Restoring product save set A ... . . . 3. If there is more than one piece of media containing the mandatory update, you will be asked to switch them at some point during the procedure. Read and follow instructions in the screen displays. When the procedure is finished, it displays a message similar to the following: Installation of VMSMUP V5.5 completed at 15:00 VMSINSTAL procedure done at 15:02 You may receive any of the following network (NCP) messages which can be ignored: %NCP-W-UNRCMP, Unrecognized component, Object Or: %NCP-I-SUCCESS, Success Object = X$X0 %NML-I-RECDELET, Database entry deleted 3.8 Registering Licenses After installing the VMS operating system and mandatory update, register your licenses in the following order: 1. Register the VMS license for the VAX computer on which you have just installed the VMS operating system. If you have a VAXcluster environment, you then register a VMS license for each additional VAX computer in the cluster. Each registered VMS license must be assigned to one of the nodes for the cluster. 3-24 Installing the VMS Operating System and DECwindows Software 3.8 Registering Licenses 2. Register the licenses for any SIPs that you purchased. If you do not register your licenses at this point, you must register them immediately after the installation, before performing the other post-installation tasks. The installation procedure displays the following message: If you have any Product Authorization Keys (PAKS) to register, you may register them now. * Do you want to register any Product Authorization Keys? (Y/N) 1. If you want to register a license, type Y and press Return. You must have a copy of your Product Authorization Key (PAK) for each license you will register. If you do not want to register the licenses at this time, type N, press Return, and go to Section 3.9. 2. The procedure displays the following message: VMS License Management Utility Options: 1. REGISTER a Product Authorization Key 2. AMEND an existing Product Authorization Key 3. CANCEL an existing Product Authorization Key 4. LIST Product Authorization Keys 5. MODIFY an existing Product Authorization Key 6. DISABLE an existing Product Authorization Key 7. DELETE an existing Product Authorization Key 8. COPY an existing Product Authorization Key 9. MOVE an existing Product Authorization Key 10. ENABLE an existing Product Authorization Key 11. SHOW the licenses loaded on this node 12. SHOW the unit requirements for this node 99. Exit this procedure Type '?' at any prompt for a description of the information requested. Enter one of the above choices [1] 3. Refer to the description of VMSLICENSE.COM in the VMS License Management Utility Manual for step-by-step instructions to register licenses. 3-25 Installing the VMS Operating System and DECwindows Software 3.8 Registering Licenses You can use the SYS$UPDATE:VMSLICENSE.COM procedure to register a license for any Digital product that supplies a PAK. You can also register licenses with the LICENSE REGISTER command. See the VMS License Management Utility Manual for examples of license registration using VMSLICENSE.COM and LICENSE REGISTER commands. The VMS License Management Utility Manual, which is a part of the VMS Version 5.5 Base Documentation Set, provides details about all LICENSE commands, error messages, and recovery procedures for licensing tasks. The VMS license permits you to use the VMS operating system. You must register this license. Appendix A contains notes and supplemental information concerning licenses. The VMS operating system uses one of the following types of license depending on the hardware and software configuration used and currently supported: o VMS Availability License Provides unlimited access to the users on a VAX computer or VAXcluster environment and is sometimes referred to as a capacity license or clusterwide license. VMS availability licenses are sized according to License Unit Requirement Table (LURT) entries for each VAX computer. Section A.2 contains the LURT for VMS Version 5.5. o VMS Activity License Provides use according to a specified number of concurrent users. This is an multiuser-based license. Every product has the option to define an activity as related to the License Management Facility. VMS defines activities, sometimes referred to as VMS users, as follows: - Each remote terminal connection is considered an activity. This is true even if you set host to your local node (SET HOST 0). - Each connection from a terminal server is considered an activity. 3-26 Installing the VMS Operating System and DECwindows Software 3.8 Registering Licenses - A multiple-window session on a workstation is considered one activity, regardless of the number of windows (unless you set host to your local node (SET HOST 0)). - A batch job is not considered an activity. - A remote network connection (other than a remote terminal connection) is not considered an activity. VMS determines the number of activities through the LOGINOUT image as part of initiating a new interactive process. o VMS Workstation License Provides use for a single user on a VAX workstation. Workstation licenses actually use the same licensing formulas as the VMS activity license. o VMS File and Application Server License Provides for the remotely submitted batch, print, application and computing services. The license authorizes one direct log-on to the VAXserver, for system management purposes only. Interactive use of the VAXserver is not permitted. o Reserved User License Defines the names of system users who can access the product. The License Management Facility checks reservation lists associated with the licenses to determine which users are allowed access. After you register the VMS license, you must register the license for any of the following system integrated products you have purchased: o VAXclusters o DECnet-VAX There are two DECnet-VAX licenses: - The end node license named DVNETEND - The routing node license named DVNETRTG 3-27 Installing the VMS Operating System and DECwindows Software 3.8 Registering Licenses All routing nodes must have a routing license. Each end node can have either an end node license or a routing license. If neither license is registered and activated, DECnet does not start and your use is limited to local DECnet only (SET HOST 0). If DECnet-VAX is running when you register your license, you must stop and then restart DECnet-VAX. You can control which VAXcluster nodes have access to each license. Using the LICENSE MODIFY /INCLUDE=(node-name[,node-name,...]) command, you can assign licenses to nodes and limit access as needed. For example, you can assign a routing node license to only one VAXcluster node and assign the end node licenses to the remaining VAXcluster nodes. If you choose this approach, make sure you assign each end node license to the same list of nodes. That is, specify identical include lists for each license of the same type. For details, see the VMS License Management Utility Manual. o RMS Journaling On systems that do not have registered and activated journaling licenses, users cannot write to any files marked for journaling. o Volume Shadowing 4. When you exit the License Management procedure, the following message is displayed: Setting the NOMOVE attribute on critical system files. This will take a few minutes... After completion of this installation, you should set the NOMOVE attribute on the critical system files of all alternate system disks by executing the command: $ @SYS$SYSTEM:SETFILENOMOVE This message informs you that the installation procedure is disabling move-file operations on critical system files for this system disk. 3-28 Installing the VMS Operating System and DECwindows Software 3.8 Registering Licenses For any additional system disks you might have, you must perform this task manually. After the installation is complete, you may run the following command procedure for each additional system disk. $ @SYS$SYSTEM:SETFILENOMOVE altsysdsk: where altsysdsk is the device name of the alternate system disk. Setting files NOMOVE on the system disk is a new safety procedure that is intended for use with defragmentation tools. The installation procedure sets files to the NOMOVE state for this system disk only. For any additional system disks you might have, you must perform this task manually after the installation procedure has been completed. In a VAXcluster environment, if a file is being moved as it is being used by a system that is booting or crashing, it can corrupt the system disk. During an installation, all local files that are in use during booting and crashing are set NOMOVE to prevent these problems. 3.9 Running AUTOGEN The remaining portion of the installation procedure runs AUTOGEN to evaluate your hardware configuration and estimate typical workloads. AUTOGEN then sets system parameters, the sizes of page, swap, and dump files, and the contents of VMSIMAGES.DAT. When AUTOGEN finishes and you reboot, the installation procedure is complete. 1. The installation procedure displays the following series of messages: Running AUTOGEN to compute new SYSGEN parameters. An attempt may be made to resize the pagefile or swapfile. If there is insufficient room on the disk, the recommended size is displayed with a message that the file should be created or extended manually by the system manager later on. Running AUTOGEN - Please wait. . . . If you need to create or modify the size of the 3-29 Installing the VMS Operating System and DECwindows Software 3.9 Running AUTOGEN pagefile or swapfile, use the SYSGEN utility. For more information, see the Guide to Setting Up a VMS System. 2. After AUTOGEN finishes, the procedure displays a series of shutdown messages that begins like this: The system is shutting down to allow the system to boot with the generated site-specific parameters and installed images. The system will automatically reboot after the shutdown and the upgrade will be complete. SHUTDOWN -- Perform an Orderly System Shutdown 3. After the system shuts down, the procedure tries to reboot the new system disk. If the system does not reboot automatically, reboot it manually. For example, suppose you have a VAX-11/780 computer and the system disk is on an RA60 disk drive with a unit number of one. Enter the following command and press Return: >>> B DU1 For information on booting, refer to the VMS upgrade and installation supplement for your VAX computer. Then return to this manual. 4. After the system reboots, the procedure displays the following message: VAX/VMS Version V5.5 Major version id = 1 Minor version id = 0 *************************************************************** VAX/VMS V5.5 You have SUCCESSFULLY installed the VMS operating system. The system is now executing the STARTUP procedure. Please wait for the completion of STARTUP before logging in to the system. **************************************************************** The VAX/VMS system is now executing the system startup procedure. %%%%%%%%%%% OPCOM 19-JUL-1991 15:00.00.00 %%%%%%%%%%% . . . 3-30 Installing the VMS Operating System and DECwindows Software 3.9 Running AUTOGEN ________________________ Note ________________________ If you did not register your VMS license as described in Section 3.8, the procedure displays warning messages that the VMS license must be registered. Be sure to register this license when the installation procedure finishes. For more information, see Appendix A and the VMS License Management Utility Manual. ______________________________________________________ Finally, the procedure displays informational messages and accounting information. For example: The VAX/VMS system is now executing the system startup commands. %SET-I-INTSET, login interactive limit = 64, current interactive value = 0 19-JUL-1991 15:00:00.00 SYSTEM job terminated at 19-JUL-1991 15:00:00.00 Accounting information: Buffered I/O count: 859 Peak working set size: 565 Direct I/O count: 478 Peak virtual size: 2570 Page faults: 5003 Mounted volumes: 0 Charged CPU time: 0 00:00:55.33 Elapsed time: 0 00:01:31.24 At this point the VMS operating system is running. 5. Press the Return key. The system asks you for the user name and password. Log into the SYSTEM account so that you can perform certain post-installation tasks. For example: Welcome to VAX/VMS V5.5 Username: SYSTEM Password: . . . Welcome to VAX/VMS Version V5.5 If you forget the password, follow the instructions for performing an emergency startup in the Guide to Setting Up a VMS System. 6. There are several things you must do before you can use the system. For complete information, see Chapter 4. 3-31 4 _________________________________________________________________ After Installing VMS After you have installed the VMS operating system, you need to perform several important tasks to prepare the system for operation. This chapter describes these tasks in the order in which you perform them. 4.1 Postinstallation Checklist If you are an experienced system manager, use the following checklist to make sure you perform the necessary tasks. Less experienced system managers are advised to follow the step-by-step instructions beginning in Section 4.2, and to use the following checklist when they have completed the postinstallation tasks. < Register your licenses, if you did not do so during the installation procedure (described in Appendix A of this manual and the VMS License Management Utility Manual). < Set files NOMOVE for additional system disks. < Build a standalone BACKUP kit on the system disk and on removable media (described in the VMS upgrade and installation supplement for your computer). < Back up the system disk as a safeguard before customizing the system (described in the VMS upgrade and installation supplement for your computer). < Customize the system (described in Section 4.5). < Configure and start DECnet-VAX (described in Section 4.6). < Create a transaction log file or disable DECdtm software, depending on whether or not you want to use DECdtm services (described in Section 4.7). < Run the VMS User Environment Test Package (UETP) to test the system (described in Chapter 10) . 4-1 After Installing VMS 4.1 Postinstallation Checklist < Decompress the system libraries using LIBDECOMP.COM (described in Section 4.9). < Set up the system messages help library (described in Section 4.10). < Remove unwanted files from the system disk using the VMS and DECwindows tailoring utilities (described in Chapter 12). < Customize VMS DECwindows (described in Chapter 11). < Back up the system disk after you have customized it (described in the VMS upgrade and installation supplement for your computer). < Start the new batch/print queuing system (described in Section 4.13). < After the system has been running for at least 24 hours, run AUTOGEN to collect feedback information (described in Section 4.15). 4.2 Registering Your Licenses The installation procedure gave you the opportunity to register any software product licenses. If you did not register your VMS license at that time, you must do so before you can use the VMS operating system. You must also register the licenses for any of the following system integrated products you have purchased: VAXclusters DECnet-VAX RMS Journaling Volume Shadowing For step-by-step instructions on registering licenses, see the VMS License Management Utility Manual and Appendix A of this manual, which provides supplemental information. 4-2 After Installing VMS 4.3 Setting Files NOMOVE for Additional System Disks 4.3 Setting Files NOMOVE for Additional System Disks The installation procedure sets critical system files to the NOMOVE state only for the disk on which you perform the installation. If any of these files are moved at any time, data corruption could occur during a system boot or a crash; setting these files to the NOMOVE state prevents corruption of the system disks. For any additional system disks you might have, you must perform this task manually. For each additional system disk, run the following command procedure: $ @SYS$SYSTEM:SETFILENOMOVE altsysdsk: where altsysdsk is the device name of the additional system disk. 4.4 Backing Up Your System Disk Now that you have spent time installing the operating system, you should protect your work by making a backup copy of the system disk in case you have any problems while customizing it. Digital recommends that you perform the following operations: o Make a standalone BACKUP kit on the system disk and on removable media o Perform a standalone backup of your system disk You should also back up your system disk after you have customized it. For complete information on these operations, see the VMS upgrade and installation supplement for your VAX computer. 4.5 Customizing the System You can customize the system to meet your site-specific 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 (in the order given): 1. Read the chapter on booting in the VMS upgrade and installation supplement for your VAX computer. This 4-3 After Installing VMS 4.5 Customizing the System chapter explains the different ways to boot the system. It also tells you how to shut down the system. 2. If the computer is part of a VAXcluster environment, read the VMS VAXcluster Manual for further information on setting up a cluster. 3. Read the Guide to Setting Up a VMS System for instructions on customizing and using your system. You will find information on the following tasks: a. Editing the template files SYCONFIG.COM, SYLOGICALS.COM, SYLOGIN.COM, and SYSTARTUP_V5.COM b. Setting up user accounts c. Adjusting system parameters 4. Read Section 4.6 in this chapter and perform the steps to configure and start DECnet-VAX. 5. Read Section 4.7 in this chapter and perform the steps appropriate for your configuration. 4.6 Configuring and Starting DECnet-VAX If you plan to run DECnet-VAX, you must do the following: 1. Once you have registered the license for DECnet- VAX, execute the interactive command procedure SYS$MANAGER:NETCONFIG.COM to automatically configure your system for networking. See the Guide to DECnet-VAX Networking for instructions on using NETCONFIG.COM. 2. After you start the queue manager (see Section 4.13), edit the commands in SYS$COMMON:[SYSMGR]SYSTARTUP_ V5.COM that pertain to networking, so that DECnet starts automatically when your system is booted. Choose one of the following commands to start the network and remove the comment delimiter (!) from that command: $! IF F$SEARCH("SYS$SYSTEM:NETACP.EXE") .NES. "" THEN @SYS$MANAGER:STARTNET $! IF F$SEARCH("SYS$SYSTEM:NETACP.EXE") .NES. "" THEN SUBMIT SYS$MANAGER:STARTNET.COM 4-4 After Installing VMS 4.6 Configuring and Starting DECnet-VAX Both of the previous commands perform the same task. However, the first command executes STARTNET.COM and delays further processing until the procedure is completed; the second submits STARTNET.COM to a batch queue and continues executing SYSTARTUP_V5.COM. 3. If you plan to run both DECnet-VAX and VMS DECwindows, you must also edit SYS$COMMON:[SYSMGR]SYSTARTUP_V5.COM to add a comment delimiter (!) immediately following the dollar-sign ($) in the following command: $ DEFINE DECW$IGNORE_DECNET TRUE If you are not going to start DECnet-VAX or have not yet started it, this command tells DECwindows not to wait for DECnet-VAX. 4.7 Using or Disabling DECdtm Services The following sections describe how to use and disable DECdtm services. 4.7.1 Using DECdtm Services If you use, or plan to use, any of the VMS software listed in Table 4-1, you must create a transaction log. This log is used by DECdtm services to record information about transactions. Table_4-1_Software_that_Uses_or_Supports_DECdtm_Services___ Type_of_Software__Name_of_Product__Version_of_Product______ Resource manager DBMS 4.2 and later Rdb/VMS 4.0 and later RMS Journaling VMS Version 5.4 and later TP monitor ACMS 3.2 and later DECintact 2.0 and later Programming VAX RALLY 3.2 and later language __________________VAX_SQL__________4.0_and_later___________ To create a transaction log, you use the Log Manager Control Program (LMCP) Utility. Refer to the LMCP section 4-5 After Installing VMS 4.7 Using or Disabling DECdtm Services in the VMS Version 5.5 New Features Manual for information on how to use the LMCP Utility to create a transaction log. 4.7.2 Disabling DECdtm Services By default, DECdtm services are enabled when you boot VMS. The DECdtm services process, TP_SERVER, then checks for the existence of a transaction log on the system and continues checking every 15 seconds until it finds one. If you do not use, and do not plan to use, any of the software listed in Table 4-1, you can disable DECdtm services. This stops the creation of the TP_SERVER process during a system boot. To disable DECdtm services, define the system-wide logical name SYS$DECDTM_INHIBIT in the SYS$MANAGER:SYLOGICALS.COM command procedure. You can define SYS$DECDTM_INHIBIT to be any string. For example: $ DEFINE/SYSTEM/EXEC SYS$DECDTM_INHIBIT yes Note that this does not immediately disable DECdtm services; instead they are disabled the next time you reboot the system. For information on the SYLOGICALS.COM command procedure, see the Guide to Setting Up a VMS System. 4.8 Testing the System Run the User Environment Test Package (UETP) to verify the installation. For complete information, see Chapter 10. Note that UETP needs at least 1200 free blocks on the system disk. 4.9 Decompressing the System Libraries Decompressing the system libraries gives the system faster access to them. The decompressed libraries require approximately 8500 additional blocks of disk space. To find out how much disk space you have, enter the following command and press the Return key: $ SHOW DEVICE SYS$SYSDEVICE 4-6 After Installing VMS 4.9 Decompressing the System Libraries If you have at least 8500 free blocks on the disk, you can decompress the libraries. The decompression process takes approximately a half hour. Log into the SYSTEM account, enter the following command, and press Return: $ @SYS$UPDATE:LIBDECOMP.COM This command can be submitted for batch processing. 4.10 Setting Up the System Messages Help Library For VMS Version 5.5, you can install and access an optional online Help version of the VMS System Messages and Recovery Procedures Reference Manual. Because this is a large file, it is not included as part of the default root library, SYS$HELP:HELPLIB.HLB. Instead, it is provided as a separate file, named SYS$HELP:SYSMSGHELP.HLB. You can view the system messages by accessing the file in one of three ways: o Use the /LIBRARY qualifier with the HELP command. For example: $ HELP/LIBRARY=SYS$HELP:SYSMSGHELP.HLB ERRORS ACCVIO o Or, define a logical name that instructs the Help Facility to search the new help library when it does not find the specified topic in the VMS root help library. For example: $ DEFINE HLP$LIBRARY DISK$2:[QUAIL]SYSMSGHELP $ HELP ERRORS DISMAL In this example, the DEFINE statement creates a logical name for the help library that the Help Facility will search after it has searched the root library, SYS$HELP:HELPLIB.HLB. (The DEFINE command would normally be placed in SYLOGICALS.COM (see Section 4.5).) In this example, the help library is located in DISK$2:[QUAIL], to where it had previously been copied from SYS$HELP; you should specify the appropriate device and directory for your system. First, the Help facility searches the root library for ERRORS. If it does not find ERRORS,[1] it searches ____________________ [1] Previous versions of HELPLIB.HLB provided information about system messages format under the name ERROR. This information is now named FORMAT_OF_ERROR. 4-7 After Installing VMS 4.10 Setting Up the System Messages Help Library the library defined by HLP$LIBRARY, until it finds ERRORS and displays the appropriate information. For information on defining logical names and search patterns for the Help facility, see the HELP command in the VMS DCL Dictionary. o Or, using the VMS Librarian Utility, you can extract the ERRORS module from SYSMSGHELP.HLB and insert it into the default root help library HELPLIB.HLB. This allows direct access without using extra HELP qualifiers or logical names. For more information, see the VMS Librarian Utility Manual. The system messages help library is in compressed format. Decompressing the library gives you faster access to it but requires an additional 1600 blocks of disk space. To decompress the library, enter a command similiar to the following: $ LIBRARY/DATA=EXPAND/OUTPUT=device:[directory]SYSMSGHELP.HLB - _$ device:[directory]SYSMSGHELP.HLB In this example, device is the name of the device where the file is located, and directory is the name of the directory. ________________________ Note ________________________ The help library for system messages is not decompressed when you execute the LIBDECOMP.COM procedure described in Section 4.9. ______________________________________________________ The system messages help library can be deleted without affecting other help libraries. You can also add or delete this library using the VMS tailoring utility (VMSTAILOR). The system messages help library does not need to be stored on the system disk. 4-8 After Installing VMS 4.11 Removing Unwanted Files 4.11 Removing Unwanted Files To remove unwanted VMS files from the system disk, use VMSTAILOR. For example, if you are not running DECnet-VAX, use VMSTAILOR to remove the files associated with DECnet- VAX. For complete information on using VMSTAILOR to remove optional VMS software see Chapter 12. To remove unwanted DECwindows files from the system disk, use DECW$TAILOR. For example, if you do not plan to use the DECwindows programming support, you can remove those files. For complete information on removing DECwindows files with DECW$TAILOR see Chapter 12. 4.12 Customizing DECwindows After you register the VMS license and reboot the system, DECwindows starts automatically (if you installed it). If you have installed VMS DECwindows software, there are several steps that you must take to customize the VMS DECwindows environment. Chapter 11 describes these steps. After you finish customizing VMS DECwindows software, return to this chapter. 4.13 Starting the Queue Manager VMS Version 5.5 contains a new batch and print queuing system. To start the queue manager and create a queue database, enter: $ START/QUEUE/MANAGER/NEW_VERSION Once you execute the START/QUEUE/MANAGER command the first time, it is stored in the queue database, and is automatically executed each time the system is rebooted. For more information on the START/QUEUE/MANAGER command, see DCL HELP or the chapter on batch and print operations in the Guide to Maintaining a VMS System. 4-9 After Installing VMS 4.13 Starting the Queue Manager 4.13.1 Standalone Queue Manager Upgrade Before attempting a queue manager upgrade, you should make sure that IPC is running and that SYSGEN parameters SCSNODE and SCSSYSTEMID are defined correctly. To determine whether IPC is running, enter the SHOW SYSTEM command. If IPC is running, a process named IPCACP is shown in the resulting display. If IPC is not running, it is probably because SCSNODE was not equal to the DECnet node name or SCSSYSTEMID was not defined correctly, as described in step 14 of Section 6.5. To check and, if necessary, modify SCSNODE and SCSSYSTEMID, run SYSGEN as described in step 14 of Section 6.5. Then edit SYS$SYSTEM:MODPARAMS.DAT and add the following lines if SCSNODE and SYSSTEMID are not properly defined: SCSNODE="decnet_node_name" SCSSYSTEMID=systemid After correctly defining SCSNODE and SCSSYSTEMID, shut down the system and reboot to start IPC. To start the new queuing system after a standalone upgrade, perform the following steps: 1. You must upgrade the old V5.4 queuing system to the new queuing system. Execute the following queue-upgrade command procedure from the SYSTEM account: $ @SYS$UPDATE:VMS$UPGRADE_A55_V55 This procedure will prompt you for the location of your old queue file (JBCSYSQUE.DAT), and for the location of the new master file QMAN$MASTER.DAT, and will then convert your old queue file of V5.4 into the new file of V5.5. (Note that your old V5.4 queue file is still saved at this point.) 2. To invoke and start the new system, enter: $ START/QUEUE/MANAGER Once you execute the START/QUEUE/MANAGER command the first time, it is stored in the queue database and is automatically executed each time the system is rebooted. Edit your site-specific startup procedure SYSTARTUP_ V5.COM and remove the START/QUEUE/MANAGER command. 4-10 After Installing VMS 4.13 Starting the Queue Manager For more information on the START/QUEUE/MANAGER command, see DCL HELP or the chapter on batch and print operations in the Guide to Maintaining a VMS System. 4.14 Backing Up the Customized System Disk Now that you have spent time installing and customizing the operating system, protect your work by making a backup copy of the system disk. For complete information on these operations, see the VMS upgrade and installation supplement for your VAX computer. Once you have made a standalone backup image copy of the system disk, install any software products that you have purchased. Follow the directions given in the software product installation manuals. 4.15 Running AUTOGEN After 24 hours of operation, run AUTOGEN in feedback mode and reboot the system. Run AUTOGEN in this way again two workdays later. ________________________ Note ________________________ For the VAX 9000 computer, AUTOGEN's initial parameter calculations are conservative. To obtain parameter values that match your system workload, you may need to run AUTOGEN in feedback mode a number of times. For more information, see the VAX 9000 notes in the system manager chapter of the VMS Version 5.5 Release Notes. ______________________________________________________ AUTOGEN sets the values of system parameters and the sizes of the page and swap files according to the system's workload. Digital recommends that you run AUTOGEN from SAVPARAMS through TESTFILES on a weekly basis and examine AGEN$PARAMS.REPORT to determine the need for additional changes. Hard coded values in MODPARAMS.DAT affect AUTOGEN's calculations of the feedback parameters. For AUTOGEN to properly calculate values, you should replace the hard coded values in MODPARAMS.DAT with MIN_ values. 4-11 After Installing VMS 4.15 Running AUTOGEN For information on using AUTOGEN, see the Guide to Setting Up a VMS System. After you run AUTOGEN, use the checklist in Section 4.1 to make sure you have completed all the tasks described in this chapter. 4-12 Part III _________________________________________________________________ Upgrade Procedures Part III contains Chapter 5, Chapter 6, Chapter 7, Chapter 8, and Chapter 9, which describe how to upgrade to Version 5.5 of the VMS operating system. 5 _________________________________________________________________ Overview of the Upgrade Procedure Use the upgrade procedure when you want to obtain a higher version of the VMS operating system. The upgrade procedure does not initialize the system disk (as does the installation procedure). This means you can obtain the latest version of the operating system while keeping your user files and optional software intact. The Version 5.5 upgrade procedure gives you the opportunity to install VMS DECwindows software on the system disk. DECwindows Motif V1.0 supersedes VMS DECwindows. If you already have VMS DECwindows Motif on your system disk, do not choose to install VMS DECwindows during the VMS Version 5.5 upgrade procedure. Note that if you are installing VMS DECwindows Motif on a workstation or in a VAXcluster that includes workstations, you must choose VMS DECwindows device support files. Refer to Section 6.7 and Section 8.4. ________________________ Note ________________________ The Version 5.5 upgrade procedure provides new files and directories in the directory [VMS$COMMON...]. If you had any special protections and ACLs before the upgrade, you need to reapply them to reestablish the security environment you previously had set up. For more information on creating and maintaining a secure environment, see the Guide to VMS System Security. ______________________________________________________ The Version 5.5 upgrade procedure leaves your VMS license and System Integrated Product licenses intact. You will not need to reinstall these licenses after you upgrade. (See Appendix A for detailed information on license management for VMS Version 5.5.) 5-1 Overview of the Upgrade Procedure Before you can upgrade to VMS Version 5.5, your standalone system must be running at least Version 5.0 of the VMS operating system (rolling upgrade excluded). For example, you can upgrade a single system disk to Version 5.5 of the VMS operating system from any of the following versions (or related hardware releases): VMS Version 5.0 VMS Version 5.0-1 VMS Version 5.0-2 VMS Version 5.0-2A VMS Version 5.1 VMS Version 5.1-B VMS Version 5.1-1 VMS Version 5.2 VMS Version 5.2-1 VMS Version 5.3 VMS Version 5.3-1 VMS Version 5.3-2 VMS Version 5.4 VMS Version 5.4-0A VMS Version 5.4-1 VMS Version 5.4-1A VMS Version 5.4-2 VMS Version 5.4-3 ________________________ Note ________________________ If your system is running a pre-V5.0 VMS version, such as Version 4.7, you must upgrade to Version 5.0 of the VMS operating system before upgrading to VMS Version 5.5. For a Version 5.5 rolling upgrade, all systems in the VAXcluster environment must be running at least Version 5.4 of the VMS operating system. ______________________________________________________ To perform a successful upgrade, you must understand the basic operations of the VAX computer that you are upgrading. Refer to the VMS upgrade and installation supplement for your VAX computer. If you have a VAXcluster environment, refer to the VMS VAXcluster Manual. This chapter describes what happens during the upgrade procedure. It also tells you what you need and lists some restrictions. 5-2 Overview of the Upgrade Procedure 5.1 What Happens During an Upgrade 5.1 What Happens During an Upgrade When you upgrade the VMS operating system, the upgrade procedure does the following: 1. Deletes and purges some VMS files but leaves all the user files intact 2. Transfers the VMS and VMS DECwindows files from the distribution media to the system disk (VMS DECwindows Motif files are not overwritten) ________________________ Note ________________________ The upgrade puts the most recent versions of the VMS files in SYS$COMMON. ______________________________________________________ 3. Merges some of the old VMS files and the new VMS files and replaces others 4. Cleans up files and structures used only during the upgrade 5.2 Cautions and Restrictions Be aware of the following cautions and restrictions before you begin the upgrade: o The upgrade procedure does not work across the network. o If the node you are upgrading is a cluster member, the upgrade procedure checks the previously set values of several SYSGEN parameters at the beginning of the upgrade (see Section 8.3). If any of the values are less than that required to upgrade to VMS Version 5.5, you are given the choice of continuing or canceling the upgrade. If you choose to continue the upgrade, the entire upgrade may not be completed and the cluster may be left in a hung state. o If you have 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. 5-3 Overview of the Upgrade Procedure 5.2 Cautions and Restrictions o If you use your AUTOGEN feedback data, you should save this information before rebooting the system with minimum startup to begin the upgrade. For more information, see Section 6.3. o If you elect not to install optional VMS or VMS DECwindows software, the upgrade procedure removes existing files for those components from the system disk. You can install optional VMS or VMS DECwindows software during the upgrade or later using VMSTAILOR and DECW$TAILOR. _______________________ Caution _______________________ Do not attempt to use VMSINSTAL with OPTIONS G to transfer VMS and VMS DECwindows save sets to another media type. If you upgrade using a kit made in this manner, you will produce an unusable system. ______________________________________________________ o If you must move the VMS save sets from the distribution media to a disk before beginning the upgrade, the save sets must be in the [000000] directory of the disk, or the upgrade will fail. o If you have a shared system dump file in SYS$COMMON:[SYSEXE], the dump file cannot have the name SYSDUMP.DMP. If you have a shared system dump file with this name, Digital recommends that you rename it to SYS$COMMON:[SYSEXE]SYSDUMP-COMMON.DMP. For more information, see the System Management section of the VMS Version 5.5 Release Notes. o You must not move the system disk or the VMS distribution kit from one drive to another during the upgrade. o You cannot upgrade a shadowed system disk. If your system disk is part of a shadow set, you must create a nonshadowed system disk before beginning the upgrade. For more information, see the VMS Volume Shadowing Manual. 5-4 Overview of the Upgrade Procedure 5.2 Cautions and Restrictions o Before you start the upgrade procedure in a VAXcluster environment, you must shut down all the nodes that boot from the system disk you are upgrading, including the node you perform the upgrade on. o 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. o VMS Version 5.5 contains a new batch and print queuing system. It is a single clusterwide queuing system that is started with the START/QUEUE/MANAGER command. The STOP/QUEUE/MANAGER/CLUSTER command stops the clusterwide queue manager. The old queuefile JBCSYSQUE.DAT is no longer used. There are now three queue database files: - QMAN$MASTER.DAT, which is the master file - SYS$QUEUE_MANAGER.QMAN$QUEUES, which is the queue file - SYS$QUEUE_MANAGER.QMAN$JOURNAL, which is the journal file The location of these last two files can be specified in the START/QUEUE/MANAGER command. For more information, see the START/QUEUE/MANAGER command in DCL help. The master file can only be moved by defining a logical name QMAN$MASTER in a logical name definition file SYLOGICALS.COM. For more information, see the chapter on batch and print operations in the Guide to Maintaining a VMS System. A cluster has just one queuing system (one set of database files) and there is no limit to the number of queues that can be defined. All nodes in the cluster must be running VMS Version 5.5 and a SYS$UPDATE:VMS$UPGRADE_A55_V55.COM procedure must be invoked from each system disk in the cluster to upgrade the queue system. For mixed-version cluster queuing options and procedures, see Section 9.16. 5-5 Overview of the Upgrade Procedure 5.2 Cautions and Restrictions o You should record the upgrade procedure on either a hardcopy terminal or a printer attached to the console terminal. If you do not do this, the screen messages will be lost. You will need a transcript in case there is a problem during the upgrade. For information on how to record the procedure, see the VMS upgrade and installation supplement for your VAX computer. o The upgrade procedure is designed so that you should not have to reinstall most layered products after the upgrade. However, you might need to reinstall certain layered products because of product-specific installation procedures. For example, you must reinstall layered products that either create directories synonymous with system directories or use VMS-defined data structures. If a layered product is available (refer to Appendix E), yet exhibits unexpected behavior once Version 5.5 of the VMS operating system is running, check the VMS Version 5.5 Release Notes for layered-product restrictions. If problems persist, contact your Digital Services representative. o Note the restriction on performing a rolling upgrade, as described in Section 7.2, before you initiate a rolling upgrade. 5.3 Items You Need for the Upgrade You need the following items to upgrade the VMS operating system to Version 5.5: o VMS Version 5.5 software distribution kit o Scratch console media (media that does not contain files you want to save) for the following VAX computers: VAX 8600, 8650 VAX 8200, 8250, 8300, 8350 VAX-11/730 VAX-11/750 VAX-11/780, 785 For example, if you have a VAX-11/780 or VAX-11/785 computer, you need a scratch RX01 floppy diskette. 5-6 Overview of the Upgrade Procedure 5.3 Items You Need for the Upgrade To prepare for an upgrade, follow the instructions in Chapter 6. 5-7 6 _________________________________________________________________ Before You Do an Upgrade Before you do an upgrade, you need to perform several important tasks to prepare the system. This chapter provides step-by-step instructions to perform each of these tasks. 6.1 Preupgrade Checklist If you are an experienced system manager and are already familiar with these tasks, use the following checklist to make sure you have performed all the tasks before beginning the upgrade. System Managers with less experience are advised to follow the step-by-step instructions beginning at Section 6.2 and to use the following checklist after they have completed all the instructions in this chapter. < Read the VMS Version 5.5 New Features Manual and the VMS Version 5.5 Release Notes. < Read the cautions and restrictions described in Section 5.2. < Set up your system to record the upgrade procedure on either a hardcopy terminal or a printer attached to the console terminal. If you do not do this, the screen messages will be lost. You will need a transcript in case there is a problem during the upgrade. For information on how to record the procedure, see the VMS upgrade and installation supplement for your VAX computer. < Check your AUTOGEN feedback information to be sure it is valid before rebooting the system (described in Section 6.3). < 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). 6-1 Before You Do an Upgrade 6.1 Preupgrade Checklist < If, in previous versions, your distribution kit provided standalone BACKUP on one of the following media types, make sure you have created a standalone BACKUP kit on one of these media types (described in Section 6.4): RX33 TU58 RX50 RX01 RL02 < Make sure SYSUAF.DAT is in the SYS$SYSTEM directory (described in Section 6.5). < Make sure PAGEFILE.SYS and SWAPFILE.SYS (if they are located on the system disk) are in the SYS$SPECIFIC:[SYSEXE] directory (described in Section 6.5). < Make sure the page file is at least 4600 blocks (described in Section 6.5). < If you have a shared system dump file in SYS$COMMON:[SYSEXE], make sure the file is not named SYSDUMP.DMP (described in Section 6.5). < Make sure the system disk has at least 38,500 free blocks (described in Section 6.5). < If your system disk is part of a shadow set, create a nonshadowed system disk to upgrade (described in the VMS Volume Shadowing Manual). < Set STARTUP_P1 to MIN (described in Section 6.5). < If upgrading from the InfoServer, you must define the System Generation Utility (SYSGEN) parameter SCSNODE. < If your system has a KFQSA controller, make sure the VMS5 parameter is set to 0 (described in Section 6.5). < Set up the system to restart automatically (described in the VMS upgrade and installation supplement for your VAX computer). < Shut down and reboot the system from which you will perform the upgrade. If you are upgrading a VAXcluster, shut down all computers that boot from the system disk you are upgrading. 6-2 Before You Do an Upgrade 6.1 Preupgrade Checklist < Set interactive logins to 0. < Shut down DECnet-VAX (described in Section 6.6). < Before attempting a queue manager upgrade, you should determine that IPC is running and that SCSNODE and SCSSYSTEMID in MODPARAMS.DAT are correct. < Stop the queue manager (described in Section 6.6). (Booting MIN does not prevent the queue manager from running.) < Make sure you have the following information (described in Section 6.7) readily available: o The device names of the drives that will hold the system disk and the distribution media. o Passwords of at least 8 characters for the SYSTEM, SYSTEST, and FIELD accounts. o A list of optional VMS components you wish to install. (If VMS DECwindows Motif is already installed, see Section 6.7.) o A list of optional DECwindows components you wish to install. o The information listed on Product Authorization Keys (PAKs) for any new product licenses you will register. < Create a command procedure to be used when booting from [SYSF]. See Section B.4 and Section B.5. To upgrade a standalone system, go to Chapter 8. To upgrade a VAXcluster environment, go to Chapter 7. 6.2 Understanding Version 5.5 of the VMS Operating System Before you begin the upgrade, read the VMS Version 5.5 New Features Manual and the VMS Version 5.5 Release Notes. These manuals describe the changes made to the VMS operating system in Version 5.5. 6-3 Before You Do an Upgrade 6.3 Checking AUTOGEN Feedback Data 6.3 Checking 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. Feedback data is produced by the SAVPARAMS phase of AUTOGEN and is stored in SYS$SYSTEM:AGEN$FEEDBACK.DAT. Valid feedback data is defined as follows: o The system was up for at least 24 hours when the feedback data was gathered o The feedback data is not over 30 days old ________________________ Note ________________________ If your feedback data is not valid, AUTOGEN will run without feedback (all previous feedback-generated parameters will be replaced by the AUTOGEN NOFEEDBACK calculations). ______________________________________________________ To ensure that AUTOGEN feedback will run after the upgrade, do the following: 1. Check the validity of your current feedback data by entering the following command: $ @SYS$UPDATE:AUTOGEN GETDATA TESTFILES This command is for test purposes and does not result in the modification of SYSGEN parameters or changes to the page and swap files. If your current feedback is valid, AUTOGEN will use it during the upgrade. AUTOGEN will issue several warnings if your current feedback data is invalid. If your current feedback data is invalid, go to step 2. 2. If your current feedback is invalid, you can generate new feedback data (assuming your system was up for at least 24 hours). Enter the following command: $ @SYS$UPDATE:AUTOGEN SAVPARAMS TESTFILES This command is for test purposes and does not result in the modification of SYSGEN parameters or changes to the page and swap files. Again, AUTOGEN warns you if the feedback data just produced is invalid. 6-4 Before You Do an Upgrade 6.3 Checking AUTOGEN Feedback Data 3. If you follow steps 1 or 2 and your current feedback data is valid, AUTOGEN uses your current feedback generated parameters during the upgrade. Your current feedback generated parameters will not be lost during the upgrade. 6.4 Backup Tasks Digital recommends that you make a backup copy of the system disk and, if your configuration allows it, upgrade the backup copy. If there are problems, you will still have a working system disk. To make a backup copy of the system disk, follow the instructions in the VMS upgrade and installation supplement for your VAX computer. If you do not have a removeable system disk, back up your system disk to tape and restore the backup copy to the system disk. This eliminates disk fragmentation on the system disk and creates contiguous free disk blocks required for the upgrade. Store the backup tapes in a safe place. If you have a VAXcluster environment with more than one system disk, make sure the volume label on each system disk and backup copies of system disks are unique. Use the SET VOLUME/LABEL command to change a volume label, if necessary. If you have one of the following VAX computers, you also must make a backup copy of the console media: VAX-11/730 VAX-11/750 VAX-11/780, 785 VAX 8200, 8250, 8300, 8350 VAX 8600, 8650 The upgrade procedure updates the console media for you. Use the backup copy of the console media during the upgrade procedure. If there are problems, you will still have a working copy of the console media. To make a backup copy of the console media, use the CONSCOPY.COM procedure, as described in the VMS upgrade and installation supplement for your VAX computer. 6-5 Before You Do an Upgrade 6.4 Backup Tasks _______________________ Caution _______________________ If your VAX computer uses one of the following console media, you did not receive a new standalone BACKUP kit with your VMS distribution kit: TU58 tape cartridge RX33 diskette RX50 diskette RX01 diskette RL02 disk cartridge Before beginning the upgrade, make sure you have a standalone BACKUP kit one one of these media. If you do not have one, create a standalone BACKUP kit using the STABACKIT.COM procedure as, described in the VMS upgrade and installation supplement for your VAX computer. ______________________________________________________ 6.5 Preparing the System Disk Prepare the system disk for the upgrade using the following procedure: 1. Log in to the SYSTEM account. 2. If you are using a volume-shadowed system disk, you must create a nonshadowed system disk to upgrade. Follow the instructions in the VMS Volume Shadowing Manual to prepare a shadowed system disk for the upgrade. 3. If you need to boot the backup copy of your system disk, or if you are upgrading a VAXcluster environment, enter the following command (otherwise, go to step 7): $ @SYS$SYSTEM:SHUTDOWN When the procedure asks if an automatic system reboot should be performed, press Return for NO. If you are a VAXcluster member, choose the CLUSTER_SHUTDOWN option. When the procedure is finished, halt the system as described in the VMS upgrade and installation supplement for your VAX computer. 4. If applicable, remove the system disk and replace it with the backup copy. 6-6 Before You Do an Upgrade 6.5 Preparing the System Disk 5. Boot the system from the backup copy of the system disk. If you do not know how to boot the system, refer to the VMS upgrade and installation supplement for your VAX computer. 6. Log in to the SYSTEM account. 7. The current copy of SYSUAF.DAT must be on the system disk in the SYS$SYSTEM directory. Otherwise, you cannot proceed with the upgrade. If you have moved your copy of SYSUAF.DAT to another location, copy it to SYS$SYSTEM for the duration of the upgrade. ________________________ Note ________________________ If you are doing a rolling upgrade, the shared version of SYSUAF.DAT is not updated. ______________________________________________________ Move any files that you do not want changed into a user directory. 8. If you have a shared system dump file in SYS$COMMON:[SYSEXE], the dump file cannot have the name SYSDUMP.DMP. If you have a shared system dump file with this name, Digital recommends that you rename it to SYS$COMMON:[SYSEXE]SYSDUMP-COMMON.DMP. For more information, see the VMS Version 5.5 Release Notes. 9. To analyze the system disk for inconsistencies and errors in the file structure, enter the following command: $ ANALYZE/DISK_STRUCTURE SYS$SYSDEVICE Ignore the following message: %ANALDISK-I-OPENQUOTA, error opening QUOTA.SYS If you find any other errors on the system disk, repair the errors by entering the following command: $ ANALYZE/DISK_STRUCTURE/REPAIR SYS$SYSDEVICE Refer to the VMS Analyze/Disk_Structure Utility Manual for more information on the ANALYZE/DISK_STRUCTURE command. 6-7 Before You Do an Upgrade 6.5 Preparing the System Disk 10.Make sure the page file (PAGEFILE.SYS) and, if appropriate, the swap file (SWAPFILE.SYS) are in SYS$SPECIFIC:[SYSEXE]. The upgrade requires that the page file be located on the system disk in SYS$SPECIFIC:[SYSEXE]. The swapfile (SWAPFILE.SYS) does not need to be located on the system disk for the upgrade, but if it is located on the system disk, the file must be located in SYS$SPECIFIC:[SYSEXE]. If the upgrade procedure finds these files in the common directory, it will move them to the system specific directory before continuing. 11.Check the page file to make sure it is at least 4600 blocks. Use the following procedure: a. To find out the size of the page file, enter the following command: $ @SYS$UPDATE:SWAPFILES The procedure displays the size of the page file and asks you to enter a new value, as follows: Enter new size for paging file: If the page file (PAGEFILE.SYS) size is greater than 4600 blocks, press the Return key. If it is less than 4600 blocks, enter 4600 and press Return. b. If the swap and dump files are on the system disk, the procedure displays the sizes of each file. To keep the current values, press Return after each prompt. If the swap file is not on the system disk, the procedure asks if you want to create one. You do not need swap and dump files on the system disk for the upgrade procedure. Enter the appropriate response for your system. If you changed the size of the page file or created a swap file, a message is displayed that tells you to reboot the system. Do not reboot now. You will reboot later. 6-8 Before You Do an Upgrade 6.5 Preparing the System Disk 12.Check the system disk to make sure there is enough room for the upgrade. To determine whether you have enough room, enter the following command: $ SHOW DEVICE SYS$SYSDEVICE To upgrade the VMS required files, the maximum number of free blocks required is 38,500. If you plan to upgrade the VMS library or optional files, or VMS DECwindows, you will not require more free blocks, because many files are deleted as the upgrade progresses-thus freeing up additional space. 13.During the upgrade procedure you will shut down and reboot the system a number of times. To avoid startup of certain system integrated products and layered products on the system during each reboot, set the SYSGEN parameter STARTUP_P1 to MIN. Enter the following commands: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> USE CURRENT SYSGEN> SET STARTUP_P1 "MIN" SYSGEN> WRITE CURRENT SYSGEN> EXIT 14.Make sure the SYSGEN parameters SCSNODE and SCSSYSTEMID are defined on your system. To determine whether SCSNODE is defined on your system, enter the following commands: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> SHOW SCSNODE SYSGEN> SHOW SCSSYSTEMID If you are planning to use the New Queue Manager, these two parameters need to be set correctly in VMS Version 5.5. Also, verify that these parameters are set in SYS$SYSTEM:MODPARAMS.DAT. If SCSNODE and SCSSYSTEMID are set correctly, proceed to step 15. To set SCSNODE and SCSSYSTEMID, enter the following commands where node is a 1- to 6 character unique DECnet node name and systemid is (DECnet area * 1024) + node number: 6-9 Before You Do an Upgrade 6.5 Preparing the System Disk SYSGEN> SET SCSNODE node SYSGEN> SET SCSSYSTEMID systemid SYSGEN> WRITE CURRENT . . . 15.Make sure the SYSGEN parameter VMS5 is set to 0. If your system has a KFQSA controller, the VMS5 parameter may have been set to a nonzero value for a previous upgrade. The VMS5 parameter is reserved for Digital use only. To check the value of the VMS5 parameter, enter the following commands: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> USE CURRENT SYSGEN> SHOW VMS5 Parameter Name Current Default Minimum Maximum Unit Dynamic -------------- ------- ------- ------- ------- ---- ------- VMS5 1 0 0 -1 If the current value of VMS5 is not 0, set it to 0 by entering the following commands: SYSGEN> SET VMS5 0 SYSGEN> WRITE CURRENT SYSGEN> EXIT 16.Any SYSGEN parameters that you modified and did not enter in MODPARAMS.DAT are lost during the upgrade. To retain these parameters, enter their names in MODPARAMS.DAT and the value that AUTOGEN needs to add to the default minimum value. For example, if you modified GBLPAGES by 128 pages above the default, add the following line to SYS$SYSTEM:MODPARAMS.DAT: ADD_GBLPAGES=128 When AUTOGEN runs after the upgrade, it uses the values in MODPARAMS.DAT. 17.To prepare the system for the upgrade, go to Section 6.6. 6-10 Before You Do an Upgrade 6.6 Preparing the System 6.6 Preparing the System To prepare the system for the upgrade, use the following procedure: 1. If your computer uses console media, set the computer to restart automatically. For some VAX computers this means setting one or more switches. For others, this means entering certain console mode commands. To determine how to enable auto restart, refer to the VMS upgrade and installation supplement for your VAX computer. If you have a system that does not use console media, set your system so you can reboot it manually. For more information, refer to the VMS upgrade and installation supplement for your VAX computer. 2. Shut down and reboot the system to activate any SYSGEN parameters that you changed (STARTUP_P1, for example). To shut down the system, enter the following command: $ @SYS$SYSTEM:SHUTDOWN When the procedure asks if an automatic system reboot should be performed, type Y (for YES) and press the Return key. 3. After the system reboots, log in to the SYSTEM account. 4. To prevent users from logging in to the system during the upgrade, enter the following command: $ SET LOGINS/INTERACTIVE=0 5. To determine whether your system is running DECnet-VAX software, enter the following command: $ SHOW NETWORK If the system displays the following message, go to step 6: %SHOW-I-NONET, network unavailable If the system displays information on the status of the DECnet-VAX network, enter the following commands to shut down the network: $ RUN SYS$SYSTEM:NCP NCP> SET EXECUTOR STATE OFF NCP> EXIT 6-11 Before You Do an Upgrade 6.6 Preparing the System 6. To stop all batch and print queues, enter the following command: $ STOP/QUEUE/MANAGER 6.7 Information You Need During the Upgrade At different points during the upgrade, you will be prompted to supply information. Make sure you have this information readily available. The information you will need includes the following: o Device names of the drives that will hold the system disk and the distribution media. o Passwords of at least 8 characters for the SYSTEM, SYSTEST, and FIELD accounts. You will be prompted to enter passwords of at least 8 characters for each of these accounts. o A list of optional VMS components you wish to install. If you want to save space on your system disk, you can choose not to install the library and optional VMS components. The upgrade procedure prompts you to specify whether you want to install each of these components. Appendix C lists the files included in these components. o A list of DECwindows components you want to install. If you want to save space on your system disk, you can choose not to install certain DECwindows components. Note that VMS DECwindows Motif software, which supersedes VMS DECwindows software, does not provide device support. If you are installing VMS DECwindows software on a workstation or on a VAXcluster that includes workstations, Digital requires that you choose the device support files, even if you will install the VMS DECwindows Motif layered product. Otherwise, you are not required to install any VMS DECwindows components. The upgrade procedure prompts you to specify which of the following DECwindows components you want to install: device support, applications, programming support, and example files. Appendix D lists the files included in each of these components. If VMS DECwindows Motif is installed, refer to Section 8.4. 6-12 Before You Do an Upgrade 6.7 Information You Need During the Upgrade o The information listed on Product Authorization Keys (PAKs) for any new product licenses you will register. You do not need to reregister your VMS license, or the licenses for any system-integrated products you are already running. If you wish to register new licenses, however, the upgrade procedure gives you the opportunity to do so. You can also register them after the upgrade is completed by using VMSLICENSE.COM or the LICENSE REGISTER command. To register a license, you need to enter the information listed on the accompanying PAK. Once you have completed these steps, use the checklist in Section 6.1 to make sure you have completed all the necessary tasks before continuing with the upgrade. 6-13 7 _________________________________________________________________ Upgrading a VAXcluster Environment This chapter describes how to upgrade a VAXcluster environment. Refer to the VMS VAXcluster Manual for more detailed information on VAXcluster environments. There are two types of cluster upgrades: concurrent and rolling. The type of upgrade you use depends on whether you want to maintain the availability of the cluster during the upgrade and whether you have more than one system disk: o Concurrent upgrade-During a concurrent upgrade, you must shut down the entire cluster and upgrade each system disk. No one can use the cluster until you upgrade each system disk and reboot each VAX computer. If all systems in the VAXcluster environment are booted from one system disk, you must perform a concurrent upgrade. To perform a concurrent upgrade, see Section 7.1. o Rolling upgrade-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 VMS operating system. Note the restriction on performing a rolling upgrade, as described in Section 7.2, before you initiate a rolling upgrade. To perform a rolling upgrade, see Section 7.3. 7-1 Upgrading a VAXcluster Environment 7.1 Performing a Concurrent Upgrade 7.1 Performing a Concurrent Upgrade You perform a concurrent upgrade by shutting down the entire cluster, upgrading each system disk or disks, and rebooting each VAX computer in the cluster. When the cluster reboots, each VAX computer will be running the upgraded version of the VMS operating system. Users cannot access the cluster until you upgrade each system disk and reboot each VAX computer. To perform a concurrent upgrade, use the following procedure: 1. Shut down the entire cluster by logging in to the SYSTEM account on each node locally, entering the following command, and choosing the CLUSTER_SHUTDOWN option: $ @SYS$SYSTEM:SHUTDOWN 2. If you have only one system disk for your cluster, go to step 3. If you have more than one system disk, select one to upgrade. 3. Perform a conversational boot of a single VAX computer from the system disk you will be upgrading. For more information about the conversational boot procedure, refer to the VMS upgrade and installation supplement for your VAX computer. At the SYSBOOT> prompt, use the SHOW VOTES and SHOW EXPECTED_VOTES command to display the current values of the parameters. Write these values down because you will need to restore them later. Set the VOTES and EXPECTED_ VOTES values to 1, by entering the following commands: SYSBOOT> USE CURRENT SYSBOOT> SET VOTES 1 SYSBOOT> SET EXPECTED_VOTES 1 SYSBOOT> CONTINUE 4. Upgrade the system disk, using the procedure in Chapter 8. 5. If you have only one system disk, go to step 6. 7-2 Upgrading a VAXcluster Environment 7.1 Performing a Concurrent Upgrade If you have more than one system disk, shut down the system that you just upgraded. Then repeat steps 2 through 4 to upgrade each system disk in the cluster. When you finish upgrading all of the system disks, go to step 6. 6. Reboot each computer in the VAXcluster environment. 7. Complete the postupgrade procedures described in Chapter 9. 7.2 Restriction on a Rolling Upgrade From VMS Version 5.4-3 to VMS Version 5.5 This restriction applies when performing a rolling upgrade from VMS Version 5.4-3 to VMS Version 5.5 in configurations that contain at least two computers with CIXCDs that boot from different system disks. You must install a patch to all system disks in your cluster that support systems with the CIXCD adapter before beginning the rolling upgrade. This restriction does not apply if you will perform a rolling upgrade from an earlier version of the VMS operating system. Use the following procedure to apply a patch to each VMS Version 5.4-3 system disk that supports systems with the CIXCD adapter before beginning the rolling upgrade. If you do not apply this patch, systems with CIXCDs will crash after you upgrade the first system disk. 1. Log in to the SYSTEM account on the VMS Version 5.4-3 system. 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 6.5) or start the DECnet software, and then refer to step 2 of Section 8.3. 2. Load the piece of media that contains the VMS Version 5.5 mandatory update in the appropriate drive. If you are installing the patch from a compact disc, the mandatory update is on the VMS Version 5.5 compact disc. If you are installing the patch from a magnetic tape, the magnetic tape is labeled VMS V5.5 BIN 16MT9 MUP. If 7-3 Upgrading a VAXcluster Environment 7.2 Restriction on a Rolling Upgrade From VMS Version 5.4-3 to VMS Version 5.5 you are installing the patch from a TK50 tape cartridge, the TK50 is labeled VMS V5.5 BIN TK50 MUP. 3. Enter the following command to copy the save set containing the patch to the SYS$UPDATE directory on the system disk: $ BACKUP/SELECT=PADRIVER01U3054.A - _$ ddcu:VMSMUP055.B/SAVE SYS$COMMON:SYSUPD]* where ddcu: is the name of the device on which you loaded the mandatory update media. 4. Enter the following command to apply the patch: $ @SYS$UPDATE:VMSINSTAL PADRIVER01U3054 5. Enter the following commands to check that the patch installed correctly: $ ANALYZE/IMAGE/OUT=NORDP.FIND SYS$COMMON:[SYS$LDR]PADRIVER.EXE $ SEARCH/NORDP.FIND NORDP If the patch applied correctly, the string NORDP will be in the file NORDP.FIND. If this string is not in NORDP.FIND, reapply the patch. 6. Follow steps 1 through 5 to apply the patch to each VMS Version 5.4-3 system disk that supports systems with CIXCDs. 7. Shut down all nodes in the cluster that boot from system disks to which you applied the patch. 8. Reboot all nodes in the cluster that boot from system disks to which you applied the patch. 9. Proceed with the VMS Version 5.5 rolling upgrade. 7.3 Performing a Rolling Upgrade During a rolling upgrade, you upgrade each system disk individually, allowing old and new versions of the VMS operating system to run together temporarily in the same cluster. Clusters running two versions of the VMS operating system are called mixed-version clusters. Because rolling upgrades allow mixed-version clusters, the systems that you are not upgrading remain available. 7-4 Upgrading a VAXcluster Environment 7.3 Performing a Rolling Upgrade _______________________ CAUTION _______________________ To perform a Version 5.5 rolling upgrade, the other nodes in the cluster must be running at least Version 5.4 of the VMS operating system. ______________________________________________________ Digital recommends that all VAX computers in a cluster run the same version of the VMS operating system. Mixed-version clusters are supported only for the purpose of upgrading the entire cluster incrementally. A rolling upgrade does not apply when all systems boot from a single system disk. When all systems boot from a single system disk, perform a concurrent upgrade using the procedure described in Section 7.1. During a rolling upgrade from Version 5.4 to Version 5.5, the V5.4 batch and print queuing system is maintained. Once the VAXcluster system is fully upgraded to Version 5.5, the new V5.5 batch and print queuing system becomes available. After the new V5.5 batch and print queuing system is operational, booting V5.4 CPUs into the VAXcluster system is permitted only if the V5.4 CPUs do not participate in any batch and print operations, such as the PRINT, SUBMIT, and START/QUEUE/MANAGER commands. Coexistence of the A5.5 and V5.4 batch and print facilities is supported. However, coexistence of the V5.4 and V5.5 batch and print facilities is supported only if queuing is done on the V5.5 nodes and not on the V5.4 nodes. Digital recommends that all VAX systems in a VAXcluster run the latest version of VMS. To perform a rolling upgrade: 1. Check the votes and make adjustments to maintain the proper quorum so that the cluster can continue to operate throughout the upgrade. (The VMS VAXcluster Manual describes this procedure in detail.) 2. Select a system disk to upgrade. 3. 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: 7-5 Upgrading a VAXcluster Environment 7.3 Performing a Rolling Upgrade $ >>> H >>> D/I 14 C >>> C IPC> Q IPC> 4. Shut down all VAX computers booting from the system disk that you are upgrading, except for the computer that you will use to apply the upgrade. ________________________ Note ________________________ VAX computers that do not boot from the system disk that you are upgrading remain available to users. ______________________________________________________ a. Log in to the SYSTEM account on the VAX computer you are shutting down. b. Enter the following command: $ @SYS$SYSTEM:SHUTDOWN.COM c. On one of the the VAX computers that is still running, enter the following command: $SET CLUSTER/EXPECTED_VOTES d. Repeat steps a through c for each VAX computer requiring a shutdown. This procedure lets one VAX computer continue running from the system disk (assuming computers running from different system disks supply enough votes to sustain cluster quorum). 5. Upgrade the system disk using the procedure in Chapter 8. _______________________ CAUTION _______________________ The upgrade procedure requires exclusive access to the drive that holds the distribution media. Do not mount the distribution disk on other nodes. ______________________________________________________ 7-6 Upgrading a VAXcluster Environment 7.3 Performing a Rolling Upgrade 6. During phase 1 of the upgrade, the procedure will ask if you are performing a rolling upgrade. If you enter Y, the procedure asks you several questions to determine if all system disks in the cluster (other than the one you are upgrading) are running at least VMS Version 5.4. For example: * Are the other system disks running VMS V5.4 or higher? All systems in the cluster must be running at least VMS Version 5.4 to perform the rolling upgrade. Type Y and press the Return key. 7. When the upgrade is completed, reboot each VAX computer that boots from the system disk you have just upgraded. 8. Repeat steps 2 through 7 for each system disk you are upgrading. Once you have performed steps a through d in step 4, you do not need to perform them again. 9. Perform the postupgrade tasks described in Chapter 9. 7.3.1 Adding a VMS Version 5.5-Supported CPU If you need to add a new CPU that is supported by VMS Version 5.5 to an existing V5.4 VAXcluster, Digital supports three options, which are listed in the following preferred order: 1. Upgrade the entire cluster to VMS Version 5.5 and bring the new CPU in as a member. 2. If you need to keep some systems in the cluster at VMS Version 5.4, you must upgrade a system disk in the cluster to A5.5 and then boot the new CPU into the cluster using that system disk. A straight installation does not allow you to stop at A5.5; you must upgrade a system disk to obtain an A5.5 system disk for this new node. With A5.5, you are running the V5.4 queuing system on all nodes. 3. If you do not want to run at A5.5, perform the following steps: a. Install VMS Version 5.5 on the new CPU outside the cluster. b. Disable all batch queues and print activity on the V5.4 systems in the cluster. 7-7 Upgrading a VAXcluster Environment 7.3 Performing a Rolling Upgrade c. Bring the V5.5 node into the cluster. d. Enable batch and print activities on the V5.5 nodes only. 7-8 8 _________________________________________________________________ Upgrading The VMS Operating System This chapter explains the upgrade procedure for a single VMS system disk. Before you begin the upgrade procedure, read the overview of the upgrade procedure described in Chapter 5 and complete the preupgrade tasks described in Chapter 6. If you are upgrading a VAXcluster, you must also read Chapter 7. _______________________ CAUTION _______________________ You cannot upgrade to Version 5.5 of the VMS operating system on the following VAX computers and system disks: o Micro/VAX I, VAXstation I, VAXstation 8000, and VAX 11/725 computers o RK07, RL02, RC25, RD32, RD51, RD52, and RD53 system disks o You cannot install VMS DECwindows on an RZ23 system disk. ______________________________________________________ The upgrade procedure is divided into six phases. You must complete each phase of the upgrade procedure. On most VAX computers the upgrade procedure continues automatically from phase to phase. Read the screen displays carefully and, if you need to reboot your VAX computer manually, refer to the VMS upgrade and installation supplement for your VAX computer and Appendix B of this manual. 8-1 Upgrading The VMS Operating System 8.1 Preparing to Boot from [SYSF] 8.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 (or temporary workspace) on the system disk where the upgrade procedure temporarily holds the system files used in the upgrade prior to moving these files to their permanent location. If you do not know how to boot from [SYSF], read the VMS upgrade and installation supplement for your VAX computer and Appendix B of this manual. Ignore any error messages after the first reboot that indicate an invalid dump header version. Some VAX computers require a special command procedure to boot from [SYSF]. If you are performing an upgrade on one of the following VAX computers you must modify the boot command procedures, DEFBOO and dddGEN before beginning the upgrade procedure: VAX 8530, 8550, 8700, 8810, 8820-N VAX 8820, 8830, 8840 To modify the boot command procedures, exit from the VMS 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 VMS upgrade and installation supplement for your VAX computer describes the procedures for copying and modifying DEFBOO and dddGEN. Use these procedures to modify DEFBOO and dddGEN so that they specify [SYSF] as the directory from which to boot. In DEFBOO, change the DEPOSIT command, as follows: DEPOSIT R5=F0000000 In dddGEN, change the DEPOSIT command that sets boot flags in register 5 (R5), as follows: DEPOSIT R5 F0000001 8-2 Upgrading The VMS Operating System 8.1 Preparing to Boot from [SYSF] If you are upgrading a VAX 8200, 8250, 8300, or 8350 computer, you must create a boot command procedure that allows you to boot from the [SYSF] directory before beginning the upgrade. The VMS upgrade and installation supplement for your VAX computer describes how to create this boot command procedure. 8.2 Configuring Devices Because you rebooted your system with minimum startup, the system did not automatically configure all devices. However, you might need access to some of the devices to perform the upgrade. Run SYSGEN to reconfigure the devices on the system and run STARTUP CONFIGURE by entering the following commands: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> AUTOCONFIGURE ALL SYSGEN> EXIT $ @SYS$SYSTEM:STARTUP CONFIGURE 8.3 Beginning the Upgrade Procedure This section describes how to start the upgrade procedure using VMSINSTAL. You can type a question mark (?) for help at any time while running VMSINSTAL. The instructions refer to the source-drive and the target- drive where: o The source-drive is the drive that holds the distribution kit. o The target-drive is the drive that holds the system disk. 1. Put the distribution compact disc or tape in the source- drive. If your VMS distribution kit contains several compact discs or tapes, put the first one in the drive. The paper labels on the compact discs or tapes indicate the order in which you use them. If you are not using the InfoServer, go to step 3. 8-3 Upgrading The VMS Operating System 8.3 Beginning the Upgrade Procedure 2. If upgrading from the InfoServer, perform the following steps: a. Start the InfoServer Client software by entering the following command: $ @SYS$STARTUP:ESS$STARTUP CLIENT The CLIENT parameter loads the client driver, ESS$DADDRIVER.EXE, and the InfoServer transport driver, ESS$LASTDRIVER.EXE. b. To start the InfoServer Client software each time the system boots, add the following line to SYS$MANAGER:SYSTARTUP_V5.COM: $ @SYS$STARTUP:ESS$STARTUP CLIENT c. As the startup procedure executes, it displays the following messages: %LASTCP-I-VERSION, LASTDRIVER X1.5 is stopped %LASTCP-I-ADAINIT, Initializing adapter xxx for LASTDRIVER %LASTCP-I-STARTED, LASTDRIVER X1.5 started on node yyy d. After you start the InfoServer Client software, you must make the CD drive accessible to your system by completing the following steps: 1. Insert the distribution CD in the CD drive connected to the InfoServer. 2. Enter the following commands: $ RUN SYS$SYSTEM:ESS$LADCP LADCP> BIND VMS055 %LADCP-I-BIND, service bound to logical unit DAD$VMS055 (_DADn:) LADCP> EXIT Make note of the device name _DADn: in the previous display. You will have to specify this device name during the upgrade. 3. To start VMSINSTAL, use the following procedure: a. Log in to the SYSTEM account. b. Enter the following command: $ @SYS$UPDATE:VMSINSTAL 8-4 Upgrading The VMS Operating System 8.3 Beginning the Upgrade Procedure 4. If the node is not a cluster member, go to step 5. If the node is a cluster member, the procedure determines the values set by the following System Generation (SYSGEN) parameters: o NPAGEDYN - size of the nonpaged pool o LRPCOUNT - number of preallocated large request packets o SRPCOUNT - number of preallocated small request packets o IRPCOUNT - number of preallocated intermediate request packets If any of these parameters are less than that required to upgrade to VMS Version 5.5, the procedure displays part or all of the following message: Your SYSGEN parameter(s), NPAGEDYN, LRPCOUNT, SRPCOUNT, IRPCOUNT may be too low to successfully complete the installation of VAX/VMS V5.5. NPAGEDYN should be at least n. LRPCOUNT should be at least 44. SRPCOUNT should be at least 600. IRPCOUNT should be at least 300. Do you want to continue with the installation of VAX/VMS V5.5? [NO] If you type Y, the upgrade continues. However, the upgrade may not complete successfully. If you type N or press Return, the installation terminates. You must then increase the values for the parameters indicated in the message and restart the installation. 5. VMSINSTAL displays messages similar to the following: VAX/VMS Software Product Installation Procedure V5.4 It is 19-JUL-1991 at 15:00.00.00 Enter a question mark (?) at any time for help. 6. The procedure displays the following message: * Are you satisfied with the backup of your system disk [YES]? If you have made a backup of the system disk, press Return and go to step 7. 8-5 Upgrading The VMS Operating System 8.3 Beginning the Upgrade Procedure If you have not made a backup of the system disk, do the following: a. Type N (for NO) and press Return. VMSINSTAL ends and the dollar-sign prompt ($) is displayed. b. Back up the system disk as described in the VMS upgrade and installation supplement for your VAX computer. c. After you have made a backup of the system disk, start the upgrade procedure again from the beginning of Section 8.3. 7. 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, enter the following command and press the Return key: * Where will the distribution volumes be mounted: MUC6 If the drive is connected to an HSC, enter the HSC name and the device name of the drive separated by a dollar sign ($). For example, if the HSC name is MUTT and the device name is MUA0, enter the following and press Return: * Where will the distribution volumes be mounted: MUTT$MUA0 If you are upgrading from a CD drive connected to an InfoServer, the device name is DADn. The n part of the device name was displayed when you bound to the distribution CD, as described in step 2. If VMSINSTAL displays an error message, make sure the drive is connected and set up properly. Enter the name again. If VMSINSTAL displays another error message, verify the device name using the following procedure: a. Press Ctrl/Y. b. Enter the SHOW DEVICE command to make sure you have the correct device name. c. Start the upgrade procedure again from the beginning of Section 8.3. 8-6 Upgrading The VMS Operating System 8.3 Beginning the Upgrade Procedure If you are not using the InfoServer, continue to the next step. 8. When VMSINSTAL displays the following message, type VMS055 and press the Return key. Make sure that you use the number zero (not the letter "O") when you type VMS055. For example: * Products: VMS055 9. When the procedure displays the following message, press Return: * Enter installation options you wish to use (none): 10.VMSINSTAL displays a message similar to the following: Please mount the first volume of the set on _MUA0. When the procedure displays the following message, type Y (for YES) and press Return: * Are you ready? Y The procedure displays messages similar to the following: %MOUNT-I-MOUNTED, VMS055 mounted on _MUA0: The following products will be processed: VMS V5.5 After a slight pause, the procedure displays messages similar to the following: Beginning installation of VMS V5.5 at 15:05 %VMSINSTAL-I-RESTORE, Restoring product saveset A... VAX/VMS V5.5 Upgrade Procedure Model: VAX 6000-410 System device: RA82 - KROK$DUA1: System root: [SYS0] Free blocks: 752667 CPU type: 11-02 The upgrade procedures display several messages that provide you with the following information: - What VMSINSTAL is doing. 8-7 Upgrading The VMS Operating System 8.3 Beginning the Upgrade Procedure - Notes, suggestions, and restrictions about various parts of the upgrade. - Status of the upgrade. Read these messages carefully to decide whether or not you need to interrupt the upgrade procedure. 11.An interruption is allowed before Phase 1. The procedure displays the following message: * Do you want to continue? (Y/N): To continue the upgrade, type Y and press the Return key. To interrupt the upgrade, do the following: a. Type N and press Return. b. If prompted for another product, press Ctrl/Z to exit from VMSINSTAL. 12.The procedure displays the current date and time. If the date and time are correct, type Y. If they are incorrect, type N. Enter the correct date and time using the 24-hour clock format and press Return. For example: PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) 19-JUL-1991 15:10 13.Continue with Phase 1 of the upgrade. 8.4 Upgrade Phase 1 This section describes Phase 1 of the upgrade. During this phase you provide passwords for system accounts and select VMS and VMS DECwindows options, and the procedure restores the files in the VMS required save set. At the end of this phase, the procedure shuts down your VAX computer. If your computer uses console media when booting, the system should reboot automatically. Otherwise, you must reboot manually from the SYSF directory. At the beginning of Phase 1, the procedure displays a message similar to the following: 8-8 Upgrading The VMS Operating System 8.4 Upgrade Phase 1 Upgrade Phase 1 19-JUL-1991 15:11:17.05 * Are you performing a rolling upgrade? (Y/N): 1. If you are performing a concurrent upgrade or an upgrade on a standalone system, type N and press the Return key. If you are performing a rolling upgrade, type Y and press Return. Follow the instructions in Section 7.3. 2. To ensure system security, the upgrade procedure requires you to enter passwords for the SYSTEM, SYSTEST, and FIELD accounts before continuing. Passwords must be at least 8 characters in length; they do not appear on the display. Press Return after you enter each one. After you enter the passwords, the procedure checks each one to make sure it meets the requirements for a good password. For example: To help provide a more secure system, you are asked to enter passwords for key system accounts. Passwords must be a minimum of 8 characters in length. You may enter new or existing passwords. Enter passwords for the following accounts: SYSTEM, SYSTEST, FIELD * Enter password for SYSTEM: * Re-enter for verification: %UAF-I-MDFYMSG, user record(s) updated %VMS-I-PWD_OKAY, account password for SYSTEM verified * Enter Password for SYSTEST * Re-enter for verification: %UAF-I-MDFYMSG, user record(s) updated %VMS-I-PWD_OKAY, account password for SYSTEST verified The SYSTEST_CLIG account will be disabled. You must re-enable it before running UETP but do not assign a password. %UAF-I-MDFYMSG, user record(s) updated Enter new password for account FIELD: Re-enter for verification: %UAF-I-MDFYMSG, user record(s) updated %VMS-I-PWD_OKAY, account password for FIELD verified If you do not get password errors, go to step 3. 8-9 Upgrading The VMS Operating System 8.4 Upgrade Phase 1 If you enter a password incorrectly or if the password is too easy to guess, the procedure displays error messages similar to the following: %VMS-W-PWD_INVALID, account password for FIELD is invalid -VMS-I-PWD_WEAK, password is too easy to guess Because of the preceding error, you must take action to secure this account. You must either disable this account, change its password, or do both. When the procedure asks if you want to disable the account, type N and press the Return key. When the procedure asks if you want to enter a new password, type Y and press Return. Then enter a new password. For example: Do you want to disable the account (Y/N)? N Do you want to change the account password (Y/N)? Y You must now select a new primary password for the FIELD account. The password you select must be at least 8 characters in length and may not be the same as the name of the account. New password: Verification: %UAF-I-MDFMSG, user record(s) updated %VMS-I-PWD-SET, primary password for account FIELD set 3. The procedure does the following: o Checks the value of the FILLM quota 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) 4. If your VAX computer is not one of the following, go to step 6: VAX 11/730 VAX 11/750 VAX 11/780 VAX 8200, 8250, 8300, 8350 VAX 8600, 8650 VAX 9000 8-10 Upgrading The VMS Operating System 8.4 Upgrade Phase 1 If your VAX computer is included in the preceding list, the procedure can temporarily modify the DEFBOO.CMD (or DEFBOO.COM if you have a VAX 8600 computer) to boot from the [SYSF] directory. During Phase 4 of the upgrade, the procedure restores the DEFBOO.CMD (or DEFBOO.COM) file that is set up to boot from the current system disk and system root. The procedure displays a message similar to the following: * Do you want to boot from the [console media]? If you prefer to boot your system manually from [SYSF], type N, press the Return key, and go to step 5. If you are booting directly from a local system disk, type N and press Return. If you are using a CI750, type Y and press Return. If you typed Y, the procedure will ask you to insert the console media in the drive. Use the backup copy of the console media. Insert the backup copy in the drive and do not remove it from the drive until the upgrade has been completed. Make sure the console media is write-enabled. 5. The procedure displays the following message: * Do you want to continue? (Y/N) To interrupt the upgrade, type N and press Return. To continue the upgrade, type Y and press Return. 6. The procedure does the following: o Cleans up the system disk by purging all accounting data files, operator logs, and the directory SYSERR. The procedure also deletes all JNL files in the root directory and its subdirectories. o Builds the directory tree [SYSF] and deletes the VMS and VMS DECwindows files that are not needed to reboot during Phase 1 of the upgrade. As the procedure performs each of these tasks, it displays messages describing what is being done. When this step is completed, the procedure displays a message similiar to the following: 8-11 Upgrading The VMS Operating System 8.4 Upgrade Phase 1 File cleanup complete - 16-JUL-1991 15:29:41.92 7. In the interest of optimizing disk space as well as providing your specific support requirements, the procedure displays information about VMS and VMS DECwindows files that you may choose to keep on your system. The information displayed is similiar to the following: Select optional software you wish to have installed. You can choose to install one or more of the following VMS and/or DECwindows components: o VMS library - 32000 blocks o VMS optional - 16500 blocks o DECwindows device support - 21400 blocks o DECwindows applications - 12000 blocks o DECwindows programming support - 26500 blocks o DECwindows example files - 3500 blocks Space remaining: 251165 blocks You must indicate which options you want to install. If you have VMS DECwindows Motif installed, the procedure offers just three software options, as shown in the following display. This is because VMS DECwindows Motif supersedes the VMS DECwindows supplied with the VMS Version 5.5 kit. Select optional software you wish to have installed. You can choose to install one or more of the following VMS and/or DECwindows components: o VMS library - 32000 blocks o VMS optional - 16500 blocks o DECwindows device support - 21400 blocks Space remaining: 293165 blocks ________________________ Note ________________________ If you elect not to install one or more of the optional VMS or DECwindows components at this time, you can install the files after the upgrade using the VMSTAILOR, DECW$TAILOR, and DECW$MOTIF_TAILOR utilities. Please note that for TK50 tape cartridges, it is quicker to install VMS and DECwindows software during the upgrade than to tailor on optional components after the upgrade. For information about using VMSTAILOR or DECW$TAILOR, see Chapter 12. For 8-12 Upgrading The VMS Operating System 8.4 Upgrade Phase 1 information about using DECW$MOTIF_TAILOR, see the VMS DECwindows Motif Installation Guide. ______________________________________________________ To select the options you want to install, follow the instructions displayed on the screen. For example: * Do you want to install the VMS library files? (Y/N) 8. The contents of the VMS library save set are listed in Appendix C. If you want to install the VMS library files, type Y and press the Return key. If you do not want to install the VMS library files, type N and press Return. The procedure displays the following message: * Do you want to install the VMS optional files? (Y/N) 9. The contents of the VMS optional save set are listed in Appendix C. If you want to install the VMS optional files, type Y and press Return. If you do not want to install the VMS optional files, type N and press Return. The procedure displays the following message: You can provide DECwindows support now, or you can use the DECW$TAILOR utility to provide or remove DECwindows support after the upgrade. NOTE: Some media, TK50s in particular, can be very slow when tailoring on files. You might want to provide DECwindows options now and tailor off unwanted files later. * Do you want to provide optional DECwindows support? (Y/N) 10.You must indicate if you wish to install DECwindows software. If you do not want to install VMS DECwindows software, type N and go to step 11. Note that VMS DECwindows software is useful even on a nonworkstation VAX computer, because you can run VMS DECwindows applications on a nonworkstation VAX computer and display them on a workstation. 8-13 Upgrading The VMS Operating System 8.4 Upgrade Phase 1 If you do not have VMS DECwindows Motif installed, the procedure displays the following message: You can install either the complete DECwindows kit or selected portions of it. A complete installation requires 56000 blocks. If you want to perform a partial installation, you can choose to install one or more of the following DECwindows components: o DECwindows device support - 21400 blocks o DECwindows applications - 12000 blocks o DECwindows programming support - 26500 blocks o DECwindows example files - 3500 blocks * Do you want to install complete DECwindows support? (Y/N) ________________________ Note ________________________ If the procedure detected that you have DECwindows Motif installed (rather than the message shown above), the procedure displays a message that begins: This procedure has detected that you are running VMS DECwindows Motif. A complete installation requires 13500 blocks. If you want to perform a . . . If you received this message, go to step b for the Motif options. ______________________________________________________ If you want to install all components of the VMS DECwindows software, type Y, press the Return key, and proceed to step a. If you are unsure, see step a for more description of the component options. a. To install all of the VMS DECwindows kit, type Y and press Return in response to the complete DECwindows support question. The procedure displays the amount of remaining disk space and the DECwindows options that will be provided. To install selected portions of the VMS DECwindows kit, type N and press Return. The procedure displays information about the amount of space you need on the system disk for each option. As you choose your options, the procedure calculates the amount of space that would be left on the system disk. 8-14 Upgrading The VMS Operating System 8.4 Upgrade Phase 1 Consider the following before you select the VMS DECwindows options that you want to install: o Device support files-If you are installing VMS DECwindows on a workstation or on a VAXcluster that includes workstations, Digital requires that you choose the device support files, even if you will install VMS DECwindows Motif layered product. Otherwise, you do not need them. In selecting the device support files, you automatically get applications and 75 dots/inch video font files, and you will be prompted to indicate if you want to install 100 dots/inch video font files. o Applications files-VMS DECwindows provides a variety of applications including the following: Bookreader, Calculator, Calendar, Cardfiler, CDA Document Viewer, Clock, EVE Text Editor, FileView, Mail, Notepad Text Editor, Paint Graphics Editor, DECterm, the Session Manager, and the Icon Box. If you are installing VMS DECwindows on a VAXstation, you need these files. They are also useful on a nonworkstation VAX computer. o Video 100 dots/inch font files-If you have a workstation monitor capable of displaying 100 dots/inch (for example, a VR150, VR160, or VR295), selecting 100 dots/inch fonts will give you a more readable display when you run VMS DECwindows applications. If your workstation monitor cannot display 100 dots/inch fonts (for example, a VR260 or VR290), you can save disk space by not selecting this option. For more information on the capabilities of your particular monitor, see the owner's guide for your monitor. You will only be prompted to indicate if you want 100 dots/inch files if you select the device support option. o Programming support files-The VMS DECwindows programming support files are needed only to develop applications and are not required to run VMS DECwindows applications. Support files are supplied for the following VAX programming languages: Ada, BASIC, BLISS, C, FORTRAN, MACRO, Pascal, and PL/1. In addition, support files 8-15 Upgrading The VMS Operating System 8.4 Upgrade Phase 1 are supplied for programming in the C language using conventions and standards developed at the Massachusetts Institute of Technology. o Example files-The VMS DECwindows example files provide examples of files used to develop various DECwindows applications. After selecting the DECwindows software options, proceed to step 11. b. If the procedure detected a Motif environment on your system, the following message is displayed: This procedure has detected that you are running VMS DECwindows Motif. A complete installation requires 13500 blocks. If you want to perform a complete installation, you can choose to install the following DECwindows component: o DECwindows device support - 13500 blocks If you are installing this kit on a workstation or on a VAXcluster that includes workstations, Digital recommends that you choose the device support files (13500 blocks). * Do you want to install DECwindows device support? (Y/N) If your VAXcluster includes workstations requiring Motif, type Y and press the Return key. The procedure displays information about the amount of space you need on the system disk for the DECwindows options. As you choose options, the procedure calculates the amount of space that would be left on the system disk. If you select YES for the device support option, the procedure displays: You elected to install VMS DECwindows device support, you automatically get the following installed: 75 dots per inch (dpi) video fonts All DECwindows applications run with 75 dpi fonts. By default, most systems start up with 75 dpi fonts. You have the option of installing 100 dpi fonts, which certain applications can take advantage of. 8-16 Upgrading The VMS Operating System 8.4 Upgrade Phase 1 For the VAXstation 4000 series machines, 100 dpi fonts are used by default. If you decide not to install 100 dpi fonts, you must edit SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM to force 75 dpi fonts to be the default. Otherwise, certain applications may not space text properly. For instructions on how to configure your system with both 75 and 100 dpi fonts, see the installation guide or look at the template command procedure SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE. * Do you want 100 dpi video fonts installed? (Y/N) The following options will be provided: VMS Library VMS optional DECwindows device support with: o 75 dots per inch video fonts o 100 dots per inch video fonts For the Motif envirionment you can consider the following as you select the DECwindows device support options: o Device support files-If you have already installed VMS DECwindows Motif on a workstation or in a VAXcluster that includes workstations, Digital requires that you choose the device support files. Otherwise, you do not need them. In selecting the device support files, you automatically get the 75 dots/inch video font files. Answer Yes to the 100 dots/inch prompt if you want to install 100 dots/inch video font files. o Video 100 dots/inch font files-If you have a workstation monitor capable of displaying 100 dots/inch (for example, a VR150, VR160, or VR295), selecting 100 dots/inch fonts will give you a more readable display when you run VMS DECwindows Motif applications. If your workstation monitor cannot display 100 dots/inch fonts (for example, a VR260 or VR290), you can save disk space by not selecting this option. For more information on the capabilities of your particular monitor, see the owner's guide for your monitor. Note that if you selected the device support option, you will be prompted to indicate if you want 100 dots/inch files (as shown above). 8-17 Upgrading The VMS Operating System 8.4 Upgrade Phase 1 11.For either the VMS DECwindows or DECwindows Motif options, the procedure gives you the opportunity to change your mind before proceeding by displaying the following message: * Is this correct? (Y/N) If you answer YES to this prompt, the installation procedure begins copying and restoring the VMS required save set. If you answer NO to this prompt, you can respecify the VMS and DECwindows options that you want to install. For the Motif environment, the procedure displays the following messages: Deleting DECwindow files out of SYSF not needed for the installation of VMS V5.5 - 17-JUL-1991 14:23:56.82 ... 25 files deleted from SYSF Moving DECwindows files to SYSF needed for the installation of VMS V5.5 - 17-JUL-1991 14:24:31.02 ... 25 files moved to SYSF The VMS DECwindows files are listed in Appendix D. Use DECW$TAILOR to remove the VMS DECwindows files you do not need. For complete information on using DECW$TAILOR to remove VMS DECwindows files see Chapter 12. The procedure will restore the VMS DECwindows options you have chosen during Phase 2. 12.The procedure restores the VMS required save set and purges the page, swap, dump, and authorization files. 13.After several minutes, the upgrade procedure indicates that the system will shut down to reboot the partially upgraded VMS Version 5.5 system and displays information about how to reboot the system. On certain VAX computers, the procedure displays the following message: * Press RETURN to shutdown system: Once you have read the information displayed on the screen, press Return to begin the shutdown. 8-18 Upgrading The VMS Operating System 8.4 Upgrade Phase 1 14.If your system uses console media, it should automatically reboot from the SYSF directory when the shutdown is complete. If you have a Micro/VAX or if your system does not reboot from SYSF, halt the system and boot from the [SYSF] directory. For most Micro/VAX and VAXstation computers, use the BOOT command in the following format and substitute the device name of the system disk for ddcu: >>> B/F0000000 ddcu For more information on booting your computer from the SYSF directory, see the VMS upgrade and installation supplement for your VAX computer. When the system reboots, it displays the VMS banner similar to the following: VAX/VMS Version BC55-xxx Major version id = 1 Minor version id = 0 After the system reboots, the procedure continues with upgrade Phase 2. 8.5 Upgrade Phase 2 This section describes Phase 2 of the upgrade. During Phase 2, the procedure installs the VMS library and optional save sets (if you elected to install them), and VMS DECwindows software (if you elected to install it). You will be required to provide input during Phase 2 if your VMS kit is on more than one volume, or if you chose to install DECwindows options. At the beginning of Phase 2, the procedure displays a message similar to the following: Continuing with VAX/VMS V5.5 Upgrade Procedure. Upgrade Phase 2 19-JUL-1991 15:55:42.57 If you are installing from magtape, you will have to insert tape 2/3 at this point. During Phase 2, the upgrade procedure does the following: 1. Phase 2 restores the rest of the optional VMS files. If your VMS distribution kit contains more than one piece of media, the procedure asks you to replace the volume in the drive with the next one in the kit. 8-19 Upgrading The VMS Operating System 8.5 Upgrade Phase 2 If VMS DECwindows Motif is installed on your system, you may ignore the following error messages: %DCL-E-OPENIN, error opening SYS$SYSROOT:[SYSMGR]DECW$STARTUP.COM; as input -RMS-E-FNF, file not found %SYSTEM-W-NOSUCHFILE, no such file \sys$share:decw$dwtshr.exe\ %SYSTEM-W-NOSUCHFILE, no such file \sys$share:decw$xmlibshr.exe\ %SYSTEM-W-NOSUCHFILE, no such file \sys$share:decw$dxmlibshr.exe\ %SYSTEM-W-NOSUCHFILE, no such file \sys$share:decw$xtshr.exe\ %SYSTEM-W-NOSUCHFILE, no such file \sys$share:xie$shrlib.exe\ %SYSTEM-W-NOSUCHFILE, no such file \sys$share:lwk$dxmshr.exe\ %SYSTEM-W-NOSUCHFILE, no such file \sys$share:decw$ailshr.exe\ %SYSTEM-W-NOSUCHFILE, no such file \sys$share:cda$accessmsg.exe\ 2. After restoring the VMS files, the procedure displays a message similiar to the following: You may now remove the VMS distribution kit from MUA0:. If you are not using an InfoServer, remove the VMS distribution media from the drive. 3. If you are not installing VMS DECwindows software, go to Section 8.6. If you are installing VMS DECwindows software, the procedure displays the following message: Load the DECwindows distribution kit. * Enter name of drive holding the DECwindows distribution media: Insert the VMS DECwindows distribution media. Then enter the device name of the drive. The procedure displays the following message: * Is the DECwindows media ready to be mounted? [N] 8-20 Upgrading The VMS Operating System 8.5 Upgrade Phase 2 Type Y and press the Return key. 4. After restoring the VMS DECwindows files, the procedure displays a message similiar to the following: You may now remove the DECwindows distribution kit from MUA0: 5. Remove the VMS DECwindows distribution media from the drive. 8.6 Upgrade Phase 3 At the beginning of Phase 3, the procedure displays a message similar to the following: Continuing with VAX/VMS V5.5, Upgrade Procedure Upgrade Phase 3 19-JUL-1991 16:45:18.35 During Phase 3, the upgrade procedure does the following: o Merges the VMS-distributed files that are commonly edited by system managers with new VMS files. o Merges all the miscellaneous user files in the old system directories into a new set of system directories, temporarily called SYSF.SYSEXE, SYSF.SYSMGR, SYSF.SYSLIB, and so on. o Removes the directory entries for page, swap, dump, and authorization files from the old directory tree. o Deletes all the remaining accounting data files, operator logs, and all files in the SYSERR directory. o Merges the old and new versions of the following files: HELP, DCLTABLES, IMAGELIB.OLB, and STARLET.OLB. o Moves all remaining files from the old directory tree [VMS$COMMON] to the new directory tree. o Deletes the old directory tree [VMS$COMMON]. During Phase 3, the system may display LIBRAR-E-DUPGLOBAL errors and FILENOTFOUND messages, which you can ignore. 8-21 Upgrading The VMS Operating System 8.7 Upgrade Phase 4 8.7 Upgrade Phase 4 At the beginning of Phase 4, the procedure displays a message similar to the following: Continuing with VAX/VMS V5.5 Upgrade Procedure. Upgrade Phase 4 19-JUL-1991 17:14:34.12 During Phase 4, the upgrade procedure does the following: 1. Corrects back pointers for system directories. 2. Shuts down the system. 3. May require you to manually reboot the system from the original system root (usually SYS0). If you are upgrading a VAX 8530, 8550, 8810, or 8820-N computer, do the following: a. Restore the original copies of DEFBOO and dddGEN to boot from the original root directory. b. In the preupgrade procedure (Chapter 6), you made copies of the boot command procedures, DEFBOO.SAV and dddGEN.SAV. To restore the original names to these files, enter the following commands and press the Return key after each one: >>> EXIT $ COPY DEFBOO.SAV DEFBOO.COM $ COPY dddGEN.SAV dddGEN.COM For more information on booting the system, see the VMS upgrade and installation supplement for your VAX computer. For most Micro/VAX and VAXstation computers, use the BOOT command in the following format and substitute the device name of the system disk for ddcu: >>> B ddcu 4. When the system boots, the procedure displays a message similar to the following: VAX/VMS Version BC55-xxx 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. The system disk must remain in the same drive for the procedure to continue with Phase 5. 8-22 Upgrading The VMS Operating System 8.8 Upgrade Phase 5 8.8 Upgrade Phase 5 At the beginning of Phase 5, the procedure displays a message similar to the following: Continuing with VAX/VMS V5.5 Upgrade Procedure. Upgrade Phase 5 19-JUL-1991 17:45:24.03 During Phase 5, the upgrade procedure does the following: o Deletes the temporary [SYSF] directory tree. o Cleans up files used only during the upgrade procedure. o Converts all VAXVMSSYS.PAR parameter files found in system roots to Version 5.5 format. o Checks the security of DECnet-VAX objects and images. o Displays messages listing tasks that you might want to perform after the upgrade procedure is completed. Chapter 9 explains these tasks. 8.9 Upgrade Phase 6 At the beginning of Phase 6, the procedure displays a message similar to the following: Continuing with VAX/VMS V5.5 Upgrade Procedure. Upgrade Phase 6 19-JUL-1991 17:45:25.03 Configuring all devices on the system... %STDRV-I-STARTUP, VMS startup begun at 19-JUL-1991 17:45:25.03 Phase 6 applies the mandatory update, which is provided on a separate tape. If you are upgrading from a compact disc, the mandatory update is stored on the same compact disc as the rest of the software. Use the following procedure to apply the mandatory update: 1. The procedure asks for the name of the drive that holds the disc or tape: * Where will the distribution volumes be mounted: Enter the device name of the drive. For example, if the mandatory update is on drive MUA0, enter the following: * Where will the distribution volumes be mounted: MUA0 8-23 Upgrading The VMS Operating System 8.9 Upgrade Phase 6 The procedure asks you to mount the disc or tape. Make sure the tape is write-protected and place it in the drive. (Compact discs are read-only media; there is no need to write-protect them.) * Please mount the first volume of the set on ddcu:. 2. The procedure asks if you are ready. Type Y and press the Return key. For example: * Are you ready? Y 3. The procedure displays the following series of messages: %MOUNT-I-MOUNTED, VMSMUP mounted on _DJA1: The following products will be processed: VMSMUP V5.5 Beginning installation of VMSMUP V5.5 at 15:00 %VMSINSTAL-I-RESTORE, Restoring product saveset A... * Do you want to purge files replaced by this installation [YES]? %VMSMUP-I-MORE_QUESTIONS, this procedure will ask additional questions after the update is done. %VMSMUP-I-APPLY_UPDATES, now applying the V5.5 updates... %VMSINSTAL-I-RESTORE, Restoring product save set B ... . . . %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... You should answer "YES" to the following question if all of the items below are TRUE. o You wish to run the "new " JOB_CONTROL and queing system. o All nodes in your cluster are at 5.5 minimum version. o The system SCSNODE matches your DECNET nodename. o The SCSSYSTEMID matches your DECNET address. If you have (or plan to have) older versions of VMS (Pre 5.5) run in your cluster, then you must stay at A5.5 by answering the question with "NO". 8-24 Upgrading The VMS Operating System 8.9 Upgrade Phase 6 If you decide not to upgrade to the new JOB_CONTROL at this time, or if your system is not properly configured to do so, you may invoke the following command procedure at a later time : @SYS$UPDATE:VMS$UPGRADE_A55_V55.COM * Do you wish to upgrade to the new JOB_CONTROL at this time [NO]? 4. If you press Return or type NO in response to this question, the message in step 6 is displayed. If you type YES in response to this question, the following message is displayed: If you have queues set up on the system that you are UPGRADing and would like to have those queues copied over to the new V5.5 system, then you should answer "YES" to the following question. If you answer YES, the new JOB_CONTROL process and QUEUE_MANAGER process will be started and your queueing environment will be copied to the V5.5 system. If you wish to simply finish the UPGRADE by starting the new JOB_CONTROL process, then you should answer the following question with a "NO". You may ABORT this procedure now, if you enter ABORT. You must answer with YES, NO, or ABORT. * Do you wish to convert queues now ? (YES,NO,ABORT) 5. If you type YES or ABORT in response to this question, the message in step 6 is displayed. If you type NO in response to this question, the following message is displayed: %UPGRADE-I-NEWJOBCTL, the new JOB_CONTROL process will be started PATCH Version 5-05 20-June-1991 %PATCH-I-NOLCL, image does not contain local symbols %PATCH-I-NOGBL, some or all global symbols not accessible old: 800044B8: 'V5.5' new: 800044B8: 'V5.5' %PATCH-I-WRTFIL, updating image file SYS$COMMON:[SYS$LDR]SYS.EXE;6 6. If there is more than one disk or tape containing the mandatory update, you will be asked to switch them at some point during the procedure. Read the screen displays. When the procedure finishes, it displays a message similar to the following: 8-25 Upgrading The VMS Operating System 8.9 Upgrade Phase 6 Installation of VMSMUP V5.5 completed at 15:00 VMSINSTAL procedure done at 15:02 During phase 6, the procedure restores your site-specific versions of the following system files with *.COM_OLD_ VMS$UPG extensions: [SYSMGR]DECW$SYLOGIN.COM [SYSMGR]LOGIN.COM [SYSMGR]LTLOAD.COM [SYSMGR]RTTLOAD.COM [SYSMGR]STARTNET.COM [SYSMGR]SYLOGIN.COM [SYSMGR]SYSTARTUP_V5.COM [SYSMGR]SYCONFIG.COM [SYSMGR]SYSECURITY.COM [SYSMGR]SYSHUTDWN.COM [SYSMGR]SYPAGSWPFILES.COM [SYSMGR]SYLOGICALS.COM [SYSMGR]TFF$STARTUP.COM [SYSMGR]LAT$SYSTARTUP.COM [SYS$STARTUP]ESS$LAST_STARTUP.DAT You might not have site-specific versions of all of these files. The procedure will display a message listing each file as it is restored. The procedure will only rename the files back to the common area. If there was a SY*.COM file in SYS$SPECIFIC, it is renamed to SYS$COMMON. ________________________ Note ________________________ If you use VWS, the VWS layered product must be reinstalled after the upgrade. ______________________________________________________ You may receive any of the following network (NCP) messages which can be ignored: %NCP-W-UNRCMP, Unrecognized component, Object Or: %NCP-I-SUCCESS, Success Object = X$X0 %NML-I-RECDELET, Database entry deleted 8-26 Upgrading The VMS Operating System 8.9 Upgrade Phase 6 During Phase 6, the upgrade procedure also gives you the opportunity to register any additional licenses and runs AUTOGEN. 1. The procedure displays the following message: If you have Product Authorization Keys (PAKs) to register, you may register them now. * Do you want to register any Product Authorization Keys? (Y/N): You do not have to reregister your VMS license or licenses for the following system integrated products: VAXclusters DECnet-VAX RMS Journaling Volume Shadowing If you want to register a new Product Authorization Key, type Y and press the Return key. Otherwise, type N and press Return. For more information on registering licenses, see the description of VMSLICENSE.COM in Appendix A. 2. When you exit the License Management procedure, the following message is displayed: Setting the NOMOVE attribute on critical system files. This will take a few minutes... After completion of this installation, you should set the NOMOVE attribute on the critical system files of all alternate system disks by executing the command: $ @SYS$SYSTEM:SETFILENOMOVE This message informs you that the upgrade procedure is disabling move-file operations on critical system files for this system disk. For any additional VMS Version 5.5 system disks you might have, you must perform this task manually. After the upgrade is complete, you may run the following command procedure for each additional system disk. $ @SYS$SYSTEM:SETFILENOMOVE altsysdsk: where altsysdsk is the device name of the additional system disk. 8-27 Upgrading The VMS Operating System 8.9 Upgrade Phase 6 Setting files NOMOVE on the system disk is a new safety procedure that is intended for use with defragmentation tools. The upgrade procedure sets files to the NOMOVE state for this system disk only. For any additional system disks you might have, you must perform this task manually after the upgrade procedure has been completed. In a VAXcluster environment, if a file is being moved as it is being used by a system that is booting or crashing, it can corrupt the system disk. During an upgrade, all local files that are in use during booting and crashing are set NOMOVE to prevent these problems. 3. Next, the procedure displays the following message and runs AUTOGEN: Running AUTOGEN to compute the new SYSGEN parameters... If AUTOGEN encounters any problems, it displays the following message: %AUTOGEN-W-REPORT, Warnings were detected by AUTOGEN. Please review the information given in the file SYS$SYSTEM:AGEN$PARAMS.REPORT. If AUTOGEN displays this message, be sure to check AGEN$PARAMS.REPORT as one of your postupgrade tasks. This task is described in Section 9.4. 4. After AUTOGEN finishes, the procedure displays a sequence of shutdown messages that begins like this: The system is shutting down to allow the system to boot with the generated site-specific parameters and installed images. The system will automatically reboot after the shutdown and the upgrade will be complete. SHUTDOWN -- Perform an Orderly System Shutdown . . . 5. 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 information on booting your system, see the VMS upgrade and installation supplement for your VAX computer. 6. If you are upgrading a standalone system, skip this step. 8-28 Upgrading The VMS Operating System 8.9 Upgrade Phase 6 If you are upgrading a VAXcluster system, the system might hang when you try to reboot the upgraded system disk. This is because the total cluster value is less than the cluster quorum value. To remedy this situation, boot voting nodes that run from the system disk you just upgraded. (All nodes that are booted at this time will have AUTOGEN run and will then reboot.) 7. After the system reboots, the procedure displays the following message: *********************************************************** VAX/VMS A5.5 You have SUCCESSFULLY installed the VMS operating system. The system is now executing the STARTUP procedure. Please wait for the completion of STARTUP before logging in to the system. *********************************************************** Finally, the procedure displays informational messages as well as accounting information. For example: %STDRV-I-STARTUP, VMS startup begun at 18:xx:xx %SET-I-INTSET, login interactive limit=64, current interactive value = 0 19-JUL-1991 18:30:00.00 SYSTEM job terminated at 19-JUL-1991 18:30:00.00 Accounting information: Buffered I/O count: 133 Peak working set size: 401 Direct I/O count: 12 Peak virtual size: 2379 Page faults: 325 Mounted volumes: 0 Charged CPU time 0 00:00:55.23 Elapsed time 0 00:01:31.24 At this point the VMS operating system is running. 8. Press the Return key. The system asks for the user name and password. Log in to the SYSTEM account so that you can perform the postupgrade procedures described in Chapter 9. 8-29 Upgrading The VMS Operating System 8.9 Upgrade Phase 6 Welcome to VAX/VMS V5.5 USERNAME: SYSTEM PASSWORD: . . . Welcome to VAX/VMS V5.5 If you forget the password, follow the instructions for performing an emergency startup in the Guide to Setting Up a VMS System. 9. Go to Chapter 9 to perform the required postupgrade tasks. 8-30 9 _________________________________________________________________ After You Do an Upgrade After you upgrade the VMS operating system, you need to perform several important tasks before you can use the system. This chapter tells you what the tasks are and the order in which you perform them. 9.1 Postupgrade Checklist Experienced system managers can use the following checklist to make sure they have performed all the necessary tasks. System Managers with less experience are advised to go to Section 9.2 for complete step-by-step instructions, and to use this checklist after they have completed the instructions in this chapter. < Replace SYSUAF.DAT (described in Section 9.2). < Examine AUTOGEN output stored in the file AGEN$PARAMS.REPORT (described in Section 9.4). < Examine the command procedure templates supplied with VMS Version 5.5 (described in Section 9.6). < Create a transaction log file, or disable the DECdtm software (described in Section 9.7), depending on whether or not you want to use DECdtm services. < Examine MODPARAMS.DAT (described in Section 9.8). < Start DECnet-VAX (described in Section 9.9). < Update your console media (described in Section 9.10). < Decompress the system libraries using LIBDECOMP.COM (described in Section 9.11). < Set up the system messages help library and decompress the library, if desired (described in Section 9.12). < Run the User Environment Test Package (UETP) to test the system (described in Chapter 10). 9-1 After You Do an Upgrade 9.1 Postupgrade Checklist < Remove unwanted files and check the sizes of system files (described in Section 9.14). < Customize VMS DECwindows software (described in Chapter 11). < Start the new batch and print queuing system (described in Section 9.16). < Build a standalone BACKUP kit (described in Section 9.17). < Back up the console media (described in Section 9.17). < Back up the system disk (described in the VMS upgrade and installation supplement for your computer). < Run AUTOGEN (described in Section 9.18). Information on licensing is provided in Section 3.8 and Appendix A. 9.2 Replacing SYSUAF.DAT If you permanently store SYSUAF.DAT on the system disk, skip this section and go to Section 9.4. If you do not permanently store SYSUAF.DAT on the system disk, you copied it to the system disk before you did the upgrade. The upgrade procedure updates SYSUAF.DAT. Copy this updated version of SYSUAF.DAT from the system disk to the directory where you usually keep it. ________________________ Note ________________________ If you did a rolling upgrade, the shared version of SYSUAF.DAT was not updated. ______________________________________________________ 9.3 Setting Files NOMOVE for Additional System Disks The upgrade procedure sets critical system files to the NOMOVE state only for the disk on which you perform the upgrade. If any of these files is moved at any time, data corruption could occur during a system boot or a crash; setting these files to the NOMOVE state prevents corruption of the system disks. For any additional system disks you might have, you must perform this task manually. For 9-2 After You Do an Upgrade 9.3 Setting Files NOMOVE for Additional System Disks each additional system disk, run the following command procedure: $ @SYS$SYSTEM:SETFILENOMOVE altsysdsk: where altsysdsk is the device name of the additional system disk. 9.4 Examining AGEN$PARAMS.REPORT When AUTOGEN runs, it writes informational and, if necessary, warning messages to the file SYS$SYSTEM:AGEN$PARAMS.REPORT. You should examine the contents of this report file. To view AGEN$PARAMS.REPORT on your screen, enter the following command and press the Return key: $ TYPE SYS$SYSTEM:AGEN$PARAMS.REPORT For more information on AGEN$PARAMS.REPORT, see the VMS Version 5.5 New Features Manual. If the report includes a message similar to the following, you might need to modify the size of the PAGE, SWAP, or DUMP file: ****************** %AUTOGEN-W-DSKSPC, The disk on which DISK$VAXVMSRL5:[SYS0.SYSEXE]PAGEFILE.SYS resides would be over 95% full if it were modified to hold 20000 blocks. ****************** For more information on modifying the sizes of the PAGE, SWAP, and DUMP files, see Section 9.5. 9.5 Checking the Size of System Files AUTOGEN sets the following files at sizes appropriate for your system: [SYSEXE]SYSDUMP.DMP [SYSEXE]PAGEFILE.SYS [SYSEXE]SWAPFILE.SYS For special workloads or configurations, you may want to specify different sizes for these files. Check the sizes of these files to be sure they meet your needs. To modify the size of these files, log into the SYSTEM account and enter the following command: 9-3 After You Do an Upgrade 9.5 Checking the Size of System Files $ @SYS$UPDATE:SWAPFILES For more information, see the Guide to Setting Up a VMS System. 9.6 Examining Your Command Procedures The upgrade procedure places a new version of WELCOME.TXT on your system disk. If your system uses a site-specific version of this file, you must modify the new version of the file with your changes. The upgrade procedure restores your site-specific version of the following files with *.COM_OLD_VMS$UPG extensions: [SYSMGR]DECW$SYLOGIN.COM [SYSMGR]LOGIN.COM [SYSMGR]LTLOAD.COM [SYSMGR]RTTLOAD.COM [SYSMGR]STARTNET.COM [SYSMGR]SYLOGIN.COM [SYSMGR]SYSTARTUP_V5.COM [SYSMGR]SYCONFIG.COM [SYSMGR]SYSECURITY.COM [SYSMGR]SYSHUTDWN.COM [SYSMGR]SYPAGSWPFILES.COM [SYSMGR]SYLOGICALS.COM [SYSMGR]TFF$STARTUP.COM [SYSMGR]LAT$SYSTARTUP.COM [SYS$STARTUP]ESS$LAST_STARTUP.DAT The upgrade procedure provides new templates for some of these files with the .TEMPLATE extension. The new templates might include features that are not in your site-specific files. Check the templates against your site-specific files and edit your files as necessary. 9.7 Using or Disabling DECdtm Services The following sections describe how to use and disable DECdtm services. 9-4 After You Do an Upgrade 9.7 Using or Disabling DECdtm Services 9.7.1 Using DECdtm Services If you use, or plan to use, any of the VMS software listed in Table 9-1, you must create a transaction log. This log is used by DECdtm services to record information about transactions. Table_9-1_Software_That_Uses_or_Supports_DECdtm_Services___ Type_of_Software__Name_of_Product__Version_of_Product______ Resource manager DBMS 4.2 and later Rdb/VMS 4.0 and later RMS Journaling VMS Version 5.4 and later TP monitor ACMS 3.2 and later DECintact 2.0 and later Programming VAX Rally 3.2 and later language __________________VAX_SQL__________4.0_and_later___________ To create a transaction log, you use the Log Manager Control Program (LMCP) Utility. Refer to the LMCP section in the VMS Version 5.5 New Features Manual for information on how to use the LMCP Utility to create a transaction log. 9.7.2 Disabling DECdtm Services By default, DECdtm services are enabled when you boot VMS. The DECdtm services process, TP_SERVER, then checks for the existence of a transaction log on the system, and continues checking every 15 seconds until it finds one. If you do not use, or do not plan to use, any of the software listed in Table 9-1, you can disable DECdtm services. This stops the creation of the TP_SERVER process during a system boot. To disable DECdtm services define the system-wide logical name SYS$DECDTM_INHIBIT in the SYS$MANAGER:SYLOGICALS.COM command procedure. You can define SYS$DECDTM_INHIBIT to be any string. For example: $ DEFINE/SYSTEM/EXEC SYS$DECDTM_INHIBIT yes 9-5 After You Do an Upgrade 9.7 Using or Disabling DECdtm Services Note that this does not immediately disable DECdtm services; instead they are disabled next time you reboot the system. For information on the SYLOGICALS.COM command procedure, see the Guide to Setting Up a VMS System. 9.8 Changing MODPARAMS.DAT Review the file SYS$SYSTEM:MODPARAMS.DAT. The upgrade procedure created a new version of this file. The old version is named SYS$SYSTEM:MODPARAMS.DAT_OLD. Modify the new file, if necessary, for your system. If you are upgrading a VAXcluster, you must update the MODPARAMS.DAT file for each VAX computer that boots from the system disk. Make sure the EXPECTED_VOTES value is correct. The value is the sum of all VOTES in the cluster. For example, if there are five VAX computers in the cluster, and each has one VOTE, the value is five. As you reboot each VAX computer, AUTOGEN runs automatically. The cluster forms when you have booted enough computers to attain cluster quorum. 9.9 Updating Your DECnet-VAX Configuration If you are not running DECnet-VAX, skip this section and go to Section 9.10. If you are running DECnet-VAX, follow the instructions in Section 9.9.1 and Section 9.9.2. 9.9.1 Running NETCONFIG_UPDATE.COM As of VMS Version 5.2, DECnet-VAX provides a more secure network environment by default. During Phase 5, the upgrade procedure checks the security of DECnet-VAX objects and images on your system. If your DECnet-VAX configuration does not meet the default level of security, the procedure displays the following message recommending that you run the NETCONFIG_UPDATE command procedure. 9-6 After You Do an Upgrade 9.9 Updating Your DECnet-VAX Configuration The upgrade has detected items which should be reviewed to ensure that DECnet-VAX will operate properly and securely. Once the upgrade completes, you should manually review the items listed above. Failure to do so could leave your node vulnerable to certain forms of attack. For futher information, consult the "VMS Guide to System Security," Chapter 7. You can execute the command procedure SYS$UPDATE:NETCONFIG_UPDATE.COM to update the security of your existing DECnet configuration. For more information on NETCONFIG_UPDATE.COM see the VMS Upgrade and Installation Manual. NETCONFIG_UPDATE.COM is a command procedure introduced with VMS Version 5.2 that implements several security measures that affect default access to your system. When you run NETCONFIG_UPDATE.COM, your configuration database does not change, except for the changes you may make to the default DECNET account or the accounts you may create for specific objects. You can only use NETCONFIG_UPDATE.COM to increase your level of network security. The procedure will not prompt you for input if your network configuration meets the minimum level established with VMS Version 5.2. NETCONFIG_UPDATE.COM generates passwords for each account that you decide to keep in your configuration database. For example, if you currently have a default DECNET account and decide to keep it, NETCONFIG_UPDATE.COM generates a new password for it and replaces the existing password with the new one. The following steps show an example of running NETCONFIG_ UPDATE.COM: ________________________ Note ________________________ Depending on your network configuration, the procedure might not display all of the questions shown in this example. ______________________________________________________ 1. Enter the following command: $ @SYS$UPDATE:NETCONFIG_UPDATE 9-7 After You Do an Upgrade 9.9 Updating Your DECnet-VAX Configuration The procedure displays the following message: DECnet--VAX node configuration upgrade procedure This procedure will allow you to create, display and optionally execute the necessary commands to update your executor and object database characteristics so that they will be compatible with V5.2 of DECnet--VAX. Getting Executor Information Getting Object Information Modifying Executor node 6.36 (KRUP) Do you wish a default nonprivileged DECnet account? [NO]: 2. The default DECnet account, named DECNET, allows all network objects general access to the system. It is only appropriate for networks with very low security requirements. For networks with greater security requirements, Digital recommends separate default accounts for specific network objects. After you respond to this prompt, the procedure displays the following message: Do you wish to disable the TASK object? [YES]: 3. The TASK object, by means of the default DECnet account (DECNET), allows user-written command procedures- including those which might be used in attempted break- ins-to be executed on your system. You can disable default access to the TASK object and still allow remote user-written command procedures to run on your system by using access control strings or proxy access. After you respond to this prompt, the procedure displays the following message: Do you want a default account for the MAIL object? [YES]: 4. MAIL is an image that provides personal mail services for VMS systems. To receive MAIL, you must create a default account for the MAIL object. An account named MAIL$SERVER will be created on your system if you reply YES to this query. After you respond to this prompt, the procedure displays the following message: Do you want a default account for the FAL object? [NO]: 9-8 After You Do an Upgrade 9.9 Updating Your DECnet-VAX Configuration 5. FAL (File Access Listener) is the remote file access facility. FAL is an image that receives and processes remote file access requests for files at the local node. A default account for FAL allows network access, by any remote user, to any files marked world-accessible. It also allows any remote user to create files in any directory with world WRITE access. An account named FAL$SERVER will be created on your system if you reply YES to this query. After you respond to this prompt, the procedure displays the following message: Do you want a default account for the PHONE object? [YES]: 6. PHONE is an image that allows online conversations with users on remote VMS systems. A default account for this object lets anyone in the network get a list of users currently logged in to the local system. A user can then attempt to log in using the list of user names. An account named PHONE$SERVER will be created on your system if you reply YES to this query. After you respond to this prompt, the procedure displays the following message: Do you want a default account for the NML object? [YES]: 7. NML is the Network Management Listener. A default account for this object lets remote users issue NCP TELL commands to gather and report network information from your volatile DECnet-VAX databases. An account named NML$SERVER will be created on your system if you reply YES to this query. After you respond to this prompt, the procedure displays the following message: Do you want a default account for the VPM object? [YES]: 8. VPM is the VMS Performance Monitor. To use the cluster monitoring features of the Monitor Utility (MONITOR), you must create a default VPM account. An account named VPM$SERVER will be created on your system if you reply YES to this query. After you respond to this prompt, the procedure displays the following message: Do you want a default account for the MIRROR object? [YES]: 9-9 After You Do an Upgrade 9.9 Updating Your DECnet-VAX Configuration 9. MIRROR is an image that is used for most types of loopback tests, including those run during the DECnet phase of the User Environment Test Program (UETP). To run most loopback tests, you must create a default account for the MIRROR object. An account named MIRRO$SERVER will be created on your system if you reply YES to this query. 10.Next the procedure displays a series of commands and the following message: Do you wish to execute these commands now? [YES]: 11.If you execute the commands, the procedure displays the following message: The DECnet--VAX database has been updated For a description of the network configuration procedure, NETCONFIG.COM, refer to the Guide to DECnet-VAX Networking or to the VMS Networking Manual. 9.9.2 Running UPDATE_CLUSTER_MEMBERS.COM When you run NETCONFIG_UPDATE.COM on a member of a VAXcluster environment, the NETCONFIG_UPDATE.COM procedure creates the secondary procedure named SYS$COMMON:[SYSMGR]UPDATE_CLUSTER_MEMBERS.COM. NETCONFIG_ UPDATE.COM instructs you to run UPDATE_CLUSTER_MEMBERS.COM on the other VAXcluster members. This secondary procedure modifies the default access of each VAXcluster member exactly as you modified that of the first member. To run UPDATE_CLUSTER_MEMBERS.COM using SYSMAN, do the following: $ RUN SYS$SYSTEM:SYSMAN SYSMAN> SET ENVIRONMENT/CLUSTER/USER=SYSTEM Remote Password: %SYSMAN-I-ENV, current command environment: Clusterwide on local cluster Username SYSTEM will be used on nonlocal nodes SYSMAN> DO @SYS$COMMON:[SYSMGR]UPDATE_CLUSTER_MEMBERS.COM SYSMAN> EXIT 9-10 After You Do an Upgrade 9.10 Updating Your Console Media 9.10 Updating Your Console Media If your computer does not use console media, skip this section and go to Section 9.11. If your computer uses console media, you must copy the Version 5.5 VMB.EXE onto your system's console media. Section 9.10.1 describes the procedure to use if you have a VAX 8530, 8550, 8810 (8700), or 8820-N (8800) computer. Section 9.10.2 describes the procedure to use if you have one of the following VAX computers: VAX-11/730 VAX-11/750 VAX-11/780, 785 VAX 8200, 8250, 8300, 8350 VAX 8600, 8650 Section 9.10.3 contains special information for the VAX 9000 computer. 9.10.1 VAX 8530, 8550, 8810 (8700), 8820-N (8800) Computers If you have a a VAX 8530, 8550, 8810 (8700), or 8820-N (8800), follow the directions in this section. 1. Place a blank RX50 diskette in one of the console diskette drives. The console refers to the upper (or left-hand) diskette drive as DZ1 while the VMS operating system refers to it as CSA1. The console refers to the lower (or right-hand) drive as DZ2 while the VMS operating system refers to it as CSA2. 2. Make sure the diskette drives have been connected to the VMS operating system, as follows: $ SHOW DEVICE CSA Device Device Error Volume Name Status Count Label CSA0: (SYSTEM) Online 0 CSA1: (SYSTEM) Online 0 CSA2: (SYSTEM) Online 0 If the drives are not connected, the following message is displayed: %SYSTEM-W-NOSUCHDEV, no such device available 9-11 After You Do an Upgrade 9.10 Updating Your Console Media If this message is displayed, enter the following commands (you need CMKRNL privilege): $ RUN SYS$SYSTEM:SYSGEN SYSGEN> CONNECT CONSOLE SYSGEN> EXIT 3. To initialize the diskette, enter a command in the following format: $ INITIALIZE/STRUCTURE=1 device-name: volume-label Substitute CSA1 or CSA2 for device-name. Substitute a 1- to 12-character name for volume-label. For example: $ INITIALIZE/STRUCTURE=1 CSA1: V55CONSOLE 4. Enter the following commands to mount the diskette, create the required directories, and copy the new VMB.EXE to the diskette. Substitute CSA1 or CSA2 for device-name. $ MOUNT/OVERRIDE=ID device-name: $ CREATE/DIRECTORY device-name:[TRANSFER] $ COPY SYS$SYSTEM:VMB.EXE device-name:[TRANSFER] 5. Once you have copied all the files, enter the following command to dismount the diskette. (Leave the diskette in the drive.) Substitute CSA1 or CSA2 for device-name. $ DISMOUNT device-name: 6. To enter console mode, press Ctrl/P. To exit from the console program, enter the following command: >>> EXIT 7. Open the diskette drive door, pause for a moment, and close it. The red indicator light will flash. 8. To copy VMB.EXE from the diskette to the console fixed disk drive, enter the following command: $ COPY DZu:[TRANSFER]VMB.EXE LB0:[CONSOLE] Substitute DZ1 or DZ2 for DZu. The fixed drive in the console is known by two names, DW2 and LB0. Most console files are stored using the name LB0. If the system displays a message that describes a protection violation on the output device, copy the files using the device name DW2. 9-12 After You Do an Upgrade 9.10 Updating Your Console Media 9. When you have finished copying the files, remove the diskette from the drive. 10.Restart the console program by entering the following command and pressing Return: $ RUN CONTROL 11.Return to the VMS operating system by entering the following command and pressing Return: >>> SET TERMINAL PROGRAM 9.10.2 VAX 11/730, 750, 780, 785 and VAX 8200, 8250, 8300, 8350, 8600, 8650 Computers If you have one of the following VAX computers, follow the directions in this section: VAX-11/730 VAX-11/750 VAX-11/780, 785 VAX 8200, 8250, 8300, 8350 VAX 8600, 8650 This procedure does the following: o Checks to see if you have enough space for the new VMB.EXE o Copies the new VMB.EXE to the console media o Updates the BOOT58 file for the VAX 11/750, 8200, 8250, 8300 and 8350 computers To update the console media, use the following procedure: 1. Log into the SYSTEM account. 2. Enter the following commands to check if there is enough space for the new VMB.EXE. You need 120 free blocks. If you are updating a VAX-11/730 system, use CSA2 for device-name; if you are updating one of the other VAX computers, use CSA1 for device-name. $ RUN SYS$SYSTEM:SYSGEN SYSGEN> CONNECT CONSOLE SYSGEN> EXIT $ EXCHANGE DIRECTORY device-name:VMB.EXE Directory of RT-11 volume TINES$CSA1: 19-OCT-1991 14:04 9-13 After You Do an Upgrade 9.10 Updating Your Console Media VMB.EXE 80 19-Oct-1991 Total of 1 file, 80 blocks. Free space 43 blocks, largest 23. If the size of the current VMB, plus the free space, does not equal at least 120 blocks, delete unneeded files on the console until you have 120 blocks available. In the above example, the size of the current VMB.EXE (80 blocks) plus the free space (43 blocks) equals 123 blocks, so files do not have to be deleted. 3. Enter the following command and press the Return key: $ @SYS$UPDATE:UPDATE_CONSOLE.COM 4. If you are updating the console medium for a VAX 8600 or VAX 8650 computer, the new VMB.EXE is copied onto the console medium. If you are updating the console medium for one of the other VAX computers, the procedure uses the EXCHANGE procedure to copy the contents of the existing console medium, merge the new files onto the copy of the console medium, and create a new version of the console medium. When the computer is ready to create the new version, it displays a message asking you to insert a scratch tape cassette or diskette. Take out the original console medium and insert a new one. 9.10.3 VAX 9000 Computers VAX 9000 computers use a special version of VMB.EXE named VMB9AQ.EXE. The upgrade procedure automatically copies a new version of this file to the console hard disk. However, if for some reason you need to update the console hard disk, use the UPDATE_CONSOLE.COM command procedure described in Section 9.10.2. The device name for the VAX 9000 console hard disk is CSA1. 9.11 Decompressing the System Libraries Decompressing the system libraries gives the system faster access to the libraries. The decompressed libraries require approximately 8500 additional blocks of disk space. To find out how much disk space you have, enter the following command and press the Return key: $ SHOW DEVICE SYS$SYSDEVICE 9-14 After You Do an Upgrade 9.11 Decompressing the System Libraries If you have enough room on the disk, you can decompress the libraries. The decompression process takes approximately 30 minutes. Log into the SYSTEM account, enter the following command, and press Return: $ @SYS$UPDATE:LIBDECOMP This command can be submitted for batch processing. 9.12 Setting Up the System Messages Help Library For VMS Version 5.5, you can install and access an optional online Help version of the VMS System Messages and Recovery Procedures Reference Manual. Because this is a large file, it is not included as part of the default root library, SYS$HELP:HELPLIB.HLB. Instead, it is provided as a separate file named SYS$HELP:SYSMSGHELP.HLB. You can view the contents of this file by accessing it in one of three ways: o Use the /LIBRARY qualifier with the HELP command. For example: $ HELP/LIBRARY=SYS$HELP:SYSMSGHELP.HLB ERRORS ACCVIO o Or, define a logical name that instructs the Help facility to search the new help library when it does not find the specified topic in the VMS root help library. For example: $ DEFINE HLP$LIBRARY DISK$2:[QUAIL]SYSMSGHELP $ HELP ERRORS DISMAL In this example, the DEFINE statement creates a logical name for the help library that the Help facility will search after it has searched the root library, SYS$HELP:HELPLIB.HLB. (The DEFINE command would normally be placed in SYLOGICALS.COM.) In this example, the help library is located in DISK$2:[QUAIL], where it had previously been copied from SYS$HELP; you should specify the appropriate device and directory for your system. First, the Help facility searches the root library for ERRORS. If it does not find ERRORS,[1] it searches the ____________________ [1] Previous versions of HELPLIB.HLB provided information about system messages format under the name ERROR. This information is now named FORMAT_OF_ERROR. 9-15 After You Do an Upgrade 9.12 Setting Up the System Messages Help Library library defined by HLP$LIBRARY until it finds ERRORS and displays the appropriate information. For information on defining logical names and search patterns for the Help facility, see the HELP command in the VMS DCL Dictionary. o Or, using the VMS Librarian Utility, you can extract the ERRORS module from SYSMSGHELP.HLB and insert it into the default root help library HELPLIB.HLB. This allows direct access without using extra HELP qualifiers or logical names. For more information, see the VMS Librarian Utility Manual. The system messages help library is in compressed format. Decompressing the library gives you faster access to it but requires an additional 1600 blocks of disk space. To decompress the library, enter a command similiar to the following: $ LIBRARY/DATA=EXPAND/OUTPUT=device:[directory]SYSMSGHELP.HLB - _$ device:[directory]SYSMSGHELP.HLB In this example, device is the name of the device on which the file is located, and directory is the name of the directory. ________________________ Note ________________________ The system messages help library is not decompressed when you execute the LIBDECOMP.COM procedure described in Section 9.11. ______________________________________________________ The system messages help library can be deleted without affecting other help libraries. You can also add or delete this library by using the VMS tailoring utility (VMSTAILOR). The system messages help library does not need to be stored on the system disk. 9.13 Testing the System with UETP Run the User Environment Test Package (UETP) to verify that the upgrade completed correctly. For instructions on running UETP, see Chapter 10. 9-16 After You Do an Upgrade 9.14 Increasing Free Space on the System Disk 9.14 Increasing Free Space on the System Disk This section describes how to increase the amount of free space on your system disk. You can gain free space by removing optional VMS or VMS DECwindows files that you do not need from the system disk or by purging old versions of some system files. 9.14.1 Using VMSTAILOR, DECW$TAILOR, and DECW$MOTIF_TAILOR To remove VMS files that you do not need from the system disk, use VMSTAILOR. For example, if you are not running DECnet-VAX, you do not need the network support files. For complete information on using VMSTAILOR to remove VMS software see Chapter 12. To remove unneeded DECwindows files from the system disk, use DECW$TAILOR. For example, if you do not plan to use the DECwindows programming support, you can remove those files. For complete information on using DECW$TAILOR to remove DECwindows files see Chapter 12. If you are running DECwindows Motif, use DECW$TAILOR to add or remove device support and fonts. To remove unwanted Motif files from the system disk, use DECW$MOTIF_TAILOR. Refer to the VMS DECwindows Motif Installation Guide. 9.14.2 Purging System Files You might want to purge the following VMS files to increase disk space: SYS$SYSTEM:SHUTDOWN.COM SYS$SYSTEM:STARTUP.COM SYS$LIBRARY:ENCRYPSHR.EXE SYS$LIBRARY:*RTL*.EXE SYS$LIBRARY:*SHR.EXE SYS$MANAGER:EDTINI.EDT SYS$MANAGER:DBLSTRTUP.COM SYS$MANAGER:*.TEMPLATE SYS$EXAMPLES:XADRIVER.MAR SYS$LIBRARY:CDDSHR.EXE SYS$LIBRARY:EPC$FACILITY.TLB SYS$LIBRARY:EPC$MSG.EXE SYS$STARTUP:VMS$LAYERED.DAT 9-17 After You Do an Upgrade 9.14 Increasing Free Space on the System Disk To purge a file, enter the PURGE command followed by the file specification. For example: $ PURGE SYS$SYSTEM:SHUTDOWN.COM 9.15 Checking Workstation Software If you have installed VMS DECwindows software, there are several steps that you must take to customize the VMS DECwindows environment. Chapter 11 describes these steps. After you finish customizing VMS DECwindows software, return to this chapter. For workstations that need VWS, you must reinstall the VWS software after upgrading to VMS Version 5.5. 9.16 Starting the Queue Manager VMS Version 5.5 contains a new batch and print queuing system controlled by a single process called the queue manager. For more information on the new batch and print queuing system, see the VMS Version 5.5 New Features Manual and the Guide to Maintaining a VMS System. There are three queue database files (master, queue, and journal files) associated with the V5.5 queue manager that must be placed on a disk available to every node that is eligible to run a queue manager. The master file is on a system disk which must be mounted before the job controller is started. The queue and journal files can be on the same disk or any other disk. Note that should the master file QMAN$MASTER.DAT need to be moved from the original system disk location, the logical name QMAN$MASTER must be redefined to reflect the new system disk location. See Section 5.2 for queue manager restrictions and more information. Note that at this point in the VMS V5.5 upgrade process, the upgrade is complete except for the queue software. Your system is presently at VMS Version A5.5. If you choose a complete queue upgrade in the procedures that follow, your system upgrade will be complete at Version 5.5. 9-18 After You Do an Upgrade 9.16 Starting the Queue Manager 9.16.1 Standalone Queue Manager Upgrade Before attempting a queue manager upgrade, you should determine that IPC is running and that SYSGEN parameters SCSNODE and SCSSYSTEMID are defined correctly. To determine whether IPC is running, enter the SHOW SYSTEM command. If IPC is running, a process named IPCACP is shown in the resulting display. If IPC is not running, it is probably because SCSNODE was not equal to the DECnet node name or SCSSYSTEMID was not defined correctly, as described in step 14 of Section 6.5. To check and, if necessary, modify SCSNODE and SCSSYSTEMID, run SYSGEN as described in step 14 of Section 6.5. Then edit SYS$SYSTEM:MODPARAMS.DAT and add the following lines if SCSNODE and SYSSTEMID are not properly defined: SCSNODE="decnet_node_name" SCSSYSTEMID=systemid After correctly defining SCSNODE and SCSSYSTEMID, shut down the system and reboot to start IPC. To start the new queuing system after a standalone upgrade, perform the following steps: 1. You must upgrade the old V5.4 queuing system to the new queuing system. Execute the following queue-upgrade command procedure from the SYSTEM account: $ @SYS$UPDATE:VMS$UPGRADE_A55_V55 This procedure will prompt you for the location of your old queue file (JBCSYSQUE.DAT), and for the location of the new master file QMAN$MASTER.DAT, and will then convert your old queue file of V5.4 into the new file of V5.5. (Note that your old V5.4 queue file is still saved at this point.) 2. To invoke and start the new system, enter: $ START/QUEUE/MANAGER Once you execute the START/QUEUE/MANAGER command the first time, it is stored in the queue database and is automatically executed each time the system is rebooted. Edit your site-specific startup procedure SYSTARTUP_ V5.COM and remove the START/QUEUE/MANAGER command. 9-19 After You Do an Upgrade 9.16 Starting the Queue Manager For more information on the START/QUEUE/MANAGER command, see DCL HELP or the chapter on batch and print operations in the Guide to Maintaining a VMS System. Your system is now upgraded to V5.5. Proceed to the next postupgrade checklist item. 9.16.2 VAXcluster Queue Manager Upgrades Upgrading the queuing system in a VAXcluster requires more consideration than on a standalone system. If you want to run with mixed versions in your cluster, you must consider which queuing system meets your requirements. To continue to operate with a cluster-wide queuing system, postpone this final upgrade step until all nodes are upgraded to A5.5. The A5.5 version of VMS contains a V5.4 compatible version of the queuing system. The V5.5 version of VMS contains a new queuing system that is not compatible with the V5.4 queuing system. The change from one queuing system to another must be accomplished in one step. Before attempting a queue manager upgrade, you should determine that IPC is running and that SYSGEN parameters SCSNODE and SCSSYSTEMID are defined correctly. To determine whether IPC is running, enter the SHOW SYSTEM command. If IPC is running, a process named IPCACP is shown in the resulting display. If IPC is not running, it is probably because SCSNODE was not equal to the DECnet node name or SCSSYSTEMID was not defined correctly, as described in step 14 of Section 6.5. To check and, if necessary, modify SCSNODE and SCSSYSTEMID, run SYSGEN as described in step 14 of Section 6.5. Then edit SYS$SYSTEM:MODPARAMS.DAT and add the following lines if SCSNODE and SYSSTEMID are not properly defined: SCSNODE="decnet_node_name" SCSSYSTEMID=systemid After correctly defining SCSNODE and SCSSYSTEMID, shut down the system and reboot to start IPC. If your VAXcluster has more one system disk, perform the following steps to cause the conversion process to build the queuing database on a disk available cluster-wide: 1. Use SYSMAN to define the QMAN$MASTER logical name on all VAXcluster nodes: 9-20 After You Do an Upgrade 9.16 Starting the Queue Manager $ RUN SYS$SYSTEM:SYSMAN SYSMAN> SET ENVIRONMENT/CLUSTER SYSMAN> DO DEFINE/SYSTEM/EXECUTIVE QMAN$MASTER device:[directory_name] SYSMAN> EXIT 2. Edit the file SYS$COMMON:[SYSMGR]:SYLOGICALS.COM on each system disk to add the following line: $ DEFINE/SYSTEM/EXECUTIVE QMAN$MASTER device:[directory_name] Note that the device:[directory_name] specification in steps 1 and 2 must be identical and specify a disk that is available cluster-wide. Perform the following steps to upgrade each system disk: 1. To upgrade each system disk in the cluster to V5.5, execute the following queue-upgrade command procedure from the SYSTEM account: $ @SYS$UPDATE:VMS$UPGRADE_A55_V55 This procedure will prompt you for the location of your old queue file (JBCSYSQUE.DAT), and for the location of the new master file (QMAN$MASTER.DAT), and will then convert your old queue file (V5.4) into the new V5.5 queue file. Note that your old V5.4 queue file is still saved at this point; you can still run the old queue system, and your system is completely upgraded to VMS Version V5.5. All nodes on your VAXCLUSTER are now running the new queuing system. However, VAXcluster systems running from other system disks still have a version number of A5.5. 2. To change the version number from A5.5 to V5.5, repeat step 1 for the other VAXcluster system disks. 3. Once all system disks in the cluster have been upgraded to V5.5 and their queuing system converted to the new V5.5 queue system with the VMS$UPGRADE_A55_V55.COM procedure, start the new queue manager. To start the new queue manager with all systems running V5.5, enter: $ START/QUEUE/MANAGER device:[directory_name] 9-21 After You Do an Upgrade 9.16 Starting the Queue Manager You only enter this command once from any V5.5 system. This command is now stored in the queue database and will automatically be executed each time the system reboots. Edit your startup procedure SYS$MANAGER:SYSTARTUP_V5.COM and remove the START/QUEUE /MANAGER command. Your cluster system disks are now fully upgraded to V5.5. (Note that you may run with V5.4 systems in your cluster if you refrain from starting the queue manager on those systems. No queuing commands will execute on a V5.4 system.) For more information on the START/QUEUE/MANAGER command, see DCL HELP or the chapter on batch and print operations in the Guide to Maintaining a VMS System. 9.17 Backing Up the System Disk Digital recommends that you protect your work by performing the following operations: o Make a standalone BACKUP kit on removable media and on the system disk o Back up the console media (if applicable) o Back up the system disk For complete information on these operations, see the VMS upgrade and installation supplement for your VAX computer. 9.18 Running AUTOGEN After 24 hours of operation, run AUTOGEN in FEEDBACK mode and reboot the system. Run AUTOGEN in this way again 2 workdays later. AUTOGEN sets the values of system parameters and the sizes of the page and swap files according to the system's workload. Digital recommends that you run AUTOGEN from SAVPARAMS through TESTFILES on a weekly basis and examine AGEN$PARAMS.REPORT to determine the need for additional changes. Hardcoded values in MODPARAMS.DAT affect AUTOGEN's calculations of the feedback parameters. For AUTOGEN FEEDBACK to properly calculate values, you should replace the hardcoded values in MODPARAMS.DAT with MIN_ values. 9-22 After You Do an Upgrade 9.18 Running AUTOGEN For information on using AUTOGEN, see the Guide to Setting Up a VMS System. 9-23 Part IV _________________________________________________________________ Upgrade and Installation Final Tasks Part IV contains Chapter 10, Chapter 11, and Chapter 12, which describe additional tasks you might perform after installing or upgrading the VMS operating system. 10 _________________________________________________________________ Running UETP The User Environment Test Package (UETP) is a VMS software package designed to test whether the VMS operating system is installed correctly. UETP puts the system through a series of tests that simulate a typical user environment, by making demands on the system that are similar to demands that might occur in everyday use. UETP is not a diagnostic program; it does not attempt to test every feature exhaustively. When UETP runs to completion without encountering nonrecoverable errors, the system being tested is ready for use. UETP exercises devices and functions that are common to all VMS systems, with the exception of optional features such as high-level language compilers. The system components tested include the following: o Most standard peripheral devices o The system's multiuser capability o DECnet-VAX software o Clusterwide file access and locks 10.1 Summary of UETP Operating Instructions This section summarizes the procedure for running all phases of UETP with default values. If you are familiar with the test package, refer to this section. If you need further information, refer to Section 10.2. 1. Log in to the SYSTEST account as follows: Username: SYSTEST Password: 10-1 Running UETP 10.1 Summary of UETP Operating Instructions _______________________ Caution _______________________ Because the SYSTEST and SYSTEST_CLIG accounts have privileges, unauthorized use of these accounts might compromise the security of your system. ______________________________________________________ 2. Make sure no user programs are running and no user volumes are mounted. _______________________ Caution _______________________ By design, UETP assumes and requests the exclusive use of system resources. If you ignore this restriction, UETP may interfere with applications that depend on these resources. ______________________________________________________ 3. After you log in, check all devices to be sure that the following conditions exist: o All devices you want to test are powered up and are on line to the system. o Scratch disks are mounted and initialized. o Disks contain a directory named [SYSTEST] with OWNER_ UIC=[1,7]. (You can create this directory with the DCL command CREATE/DIRECTORY.) o Scratch magnetic tape reels are physically mounted on each drive you want tested and are initialized with the label UETP (using the DCL command INITIALIZE). Make sure magnetic tape reels contain at least 600 feet of tape. o Scratch tape cartridges have been inserted in each drive you want to test and are initialized with the label UETP. o Line printers and hardcopy terminals have plenty of paper. o Terminal characteristics and baud rate are set correctly (see the user's guide for your terminal). Note that some communications devices need to be set up by Digital Services (see Section 10.3). 10-2 Running UETP 10.1 Summary of UETP Operating Instructions If you encounter any problems in preparing to run UETP, read Section 10.3 before proceeding. 4. To start UETP, enter the following command and press RETURN: $ @UETP UETP responds with the following question: Run "ALL" UETP phases or a "SUBSET" [ALL]? Press RETURN to choose the default response enclosed in brackets. UETP responds with three more questions in the following sequence: How many passes of UETP do you wish to run [1]? How many simulated user loads do you want [n]? Do you want Long or Short report format [Long]? Press RETURN after each prompt. After you answer the last question, UETP initiates its entire sequence of tests, which run to completion without further input. The final message should look like the following: ***************************************************** * * END OF UETP PASS 1 AT 19-OCT-1991 16:30:09.38 * * ***************************************************** 5. After UETP runs, check the log files for errors. If testing completes successfully, the VMS operating system is in proper working order. ________________________ Note ________________________ After a run of UETP, you should run the Error Log Utility to check for hardware problems that can occur during a run of UETP. For information on running the Error Log Utility, refer to the VMS Error Log Utility Manual. ______________________________________________________ If UETP does not complete successfully, refer to Section 10.6. 10-3 Running UETP 10.1 Summary of UETP Operating Instructions If you want to run UETP without using the default responses, refer to Section 10.5 through Section 10.5.4, which explain the options. 10.2 Logging In This section contains detailed instructions on running UETP. For a brief summary of these steps, see Section 10.1. Obtain the SYSTEST password from your system manager. Log into the SYSTEST account from the console terminal as follows: Username: SYSTEST Password: ________________________ Note ________________________ Because SYSTEST has privileges, unauthorized use of this account might compromise the security of your system. ______________________________________________________ UETP will fail if you do not run the test from the SYSTEST account. Also, if you try to run UETP from a terminal other than the console terminal, the device test phase displays an error message stating that the terminal you are using is unavailable for testing. You can ignore this message. After you log into the SYSTEST account, enter the command SHOW USERS to make sure no user programs are running and no user volumes are mounted. UETP requires exclusive use of system resources. If you ignore this restriction, UETP may interfere with applications that depend on these resources. ________________________ Note ________________________ The information contained in Section 10.6.4.1 is intended to help you identify and solve problems, including wrong quotas, privileges, or accounts, that could occur when you are running UETP. You should refer to this section before you run UETP. ______________________________________________________ 10-4 Running UETP 10.2 Logging In 10.2.1 SYSTEST Directories If you logged in successfully, you should be in the root directory [SYSTEST] on the system disk. UETP uses directories named [SYSTEST] to hold all the files used by UETP command procedure (UETP.COM) and temporary files used by UETP during testing. The DCL command SHOW LOGICAL displays the translation of the logical name SYS$TEST on a typical system: $ SHOW LOGICAL SYS$TEST "SYS$TEST" = "SYS$SYSROOT:[SYSTEST]" (LNM$SYSTEM_TABLE) To use UETP to test a particular disk, such as a scratch disk, create either a [SYSTEST] directory or a [SYS0.SYSTEST] directory on that disk. Section 10.3.2 discusses setting up scratch disks for testing. 10.3 Setting Up for UETP After you log in, set up the devices on the system for UETP testing. ________________________ Note ________________________ Your system may not have all the devices described in this section. ______________________________________________________ Check all devices to be sure that the following conditions exist: o All devices you want to test are turned on and are on line. o Scratch disks are initialized and mounted. o Disks contain a directory named [SYSTEST] with OWNER_ UIC=[1,7]. Use the CREATE/DIRECTORY command if the [SYSTEST] directory does not exist on the disk. o Scratch magnetic tape reels are physically mounted on each drive you want tested and are initialized with the label UETP (using the DCL command INITIALIZE). Make sure magnetic tape reels contain at least 600 feet of tape. 10-5 Running UETP 10.3 Setting Up for UETP o Scratch tape cartridges have been inserted in each drive you want to test and are mounted and initialized with the label UETP. o Line printers and hardcopy terminals have plenty of paper. o Terminal characteristics and baud rate are set correctly (see the user's guide for your terminal). Note that some communications devices discussed in this section need to be set up by Digital Services. 10.3.1 The System Disk Before running UETP, be sure that the system disk has at least 1200 blocks available. Note that systems running more than 20 load test processes may require a minimum of 2000 available blocks. If you run multiple passes of UETP, log files will accumulate in the default directory and further reduce the amount of disk space available for subsequent passes. If disk quotas are enabled on the system disk, you should disable them before you run UETP. 10.3.2 Additional Disks The disk test uses most of the available free space on each testable disk in the following manner: o On each testable disk, the device test phase tries to create two files. The size of these files depends on how much free space is available on the disk. Usually the test creates each file with 5% of the free space on the disk. However, if the disk is nearly full, the test creates files that are 5 blocks. If the test cannot create 5 block files, it fails. Only the initial file creation can cause the device test to fail because of lack of disk space. o The test randomly reads and writes blocks of data to the files. After every multiple of 20 writes for each file, the test tries to extend the file. The size of this extension is either 5% of the free disk space, or 5 blocks if the file was created with 5 blocks. This process of extension continues until the combined space of the files reaches 75% of the free disk space. 10-6 Running UETP 10.3 Setting Up for UETP By creating and extending fragmented files in this way, UETP exercises the disk. This allows the test to check for exceeded quotas or a full disk, and to adjust for the amount of available disk space. To prepare each disk drive in the system for UETP testing, use the following procedure: 1. Place a scratch disk in the drive and spin up the drive. If a scratch disk is not available, use any disk with a substantial amount of free space; UETP does not overwrite existing files on any volume. If your scratch disk contains files that you want to keep, do not initialize the disk; go to step 3. 2. If the disk does not contain files you want to save, initialize it. For example: $ INITIALIZE DUA1: TEST1 This command initializes DUA1, and assigns the volume label TEST1 to the disk. All volumes must have unique labels. 3. Mount the disk. For example: $ MOUNT/SYSTEM DUA1: TEST1 This command mounts the volume labeled TEST1 on DUA1. The /SYSTEM qualifier indicates that you are making the volume available to all users on the system. 4. UETP uses the [SYSTEST] directory when testing the disk. If the volume does not contain the directory [SYSTEST], you must create it. For example: $ CREATE/DIRECTORY/OWNER_UIC=[1,7] DUA1:[SYSTEST] This command creates a [SYSTEST] directory on DUA1 and assigns a user identification code (UIC) of [1,7]. The directory must have a UIC of [1,7] to run UETP. If the disk you have mounted contains a root directory structure, you can create the [SYSTEST] directory in the [SYS0.] tree. 10-7 Running UETP 10.3 Setting Up for UETP 10.3.3 Magnetic Tape Drives Set up magnetic tape drives that you want to test by doing the following: 1. Place a scratch magnetic tape with at least 600 feet of magnetic tape in the tape drive. Make sure that the write-enable ring is in place. 2. Position the magnetic tape at the beginning-of-tape (BOT) and put the drive on line. 3. Initialize each scratch magnetic tape with the label UETP. For example, if you have physically mounted a scratch magnetic tape on MTA1, enter the following command and press RETURN: $ INITIALIZE MTA1: UETP Magnetic tapes must be labeled UETP to be tested. As a safety feature, UETP does not test tapes that have been mounted with the MOUNT command. If you encounter a problem initializing the magnetic tape, or if the test has a problem accessing the magnetic tape, refer to the description of the INITIALIZE command in the VMS DCL Dictionary. 10.3.4 Tape Cartridge Drives Set up tape cartridge drives that you want to test by doing the following: 1. Insert a scratch tape cartridge in the tape cartridge drive. 2. Initialize the tape cartridge. For example: $ INITIALIZE MUA0: UETP Tape cartridges must be labeled UETP to be tested. As a safety feature, UETP does not test tape cartridges that have been mounted with the MOUNT command. If you encounter a problem initializing the tape cartridge, or if the test has a problem accessing the tape cartridge, refer to the description of the DCL INITIALIZE command in the VMS DCL Dictionary. 10-8 Running UETP 10.3 Setting Up for UETP 10.3.4.1 TLZ04 Tape Drives During the initialization phase, UETP sets a time limit of 6 minutes for a TLZ04 unit to complete the UETTAPE00 test. If the device does not complete the UETTAPE00 test within the alloted time, UETP displays a message similar to the following: -UETP-E-TEXT, UETTAPE00.EXE testing controller MKA was stopped ($DELPRC) at 16:23:23.07 because the time out period (UETP$INIT_TIMEOUT) expired or because it seemed hung or because UETINIT01 was aborted. To increase the timeout value, type a command similiar to the following before running UETP: $ DEFINE/GROUP UETP$INIT_TIMEOUT "0000 00:08:00.00" This example defines the initialization timeout value to 8 minutes. 10.3.5 Compact Disc Drives To run UETP on an RRD40 or RRD50 compact disc drive, you must first load the test disc that you received with your compact disc drive unit. 10.3.6 Optical Disk Drives To run UETP on an RV60 drive, set up the RV64 optical disk- storage system, by doing the following: 1. Use the Jukebox Control Software (JCS) to load an optical disk in each of the RV60 drives. JCS is a layered product on the VMS operating system that comes with the RV64 and is responsible for controlling the robot arm that loads and unloads the disks. 2. Initialize the optical disks with the label UETP, but do not mount them. UETP tests all the RV60s present in the RV64 simultaneously. Unlike the tape tests, UETP does not re- initialize the optical disks at the end of the test. 10-9 Running UETP 10.3 Setting Up for UETP 10.3.7 Terminals and Line Printers Terminals and line printers must be turned on to be tested by UETP. They must also be on line. Check that line printers and hardcopy terminals have enough paper. The amount of paper required depends on the number of UETP passes that you plan to execute. Each pass requires two pages for each line printer and hardcopy terminal. Check that all terminals are set to the correct baud rate and are assigned appropriate characteristics (see the user's guide for your terminal). Spooled devices and devices allocated to queues fail the initialization phase of UETP and are not tested. 10.3.8 Ethernet Adapters Make sure that no other processes are sharing the Ethenet adaptor device when you run UETP. ________________________ Note ________________________ UETP will not test your Ethernet adapter if DECnet-VAX or another application has the device allocated. ______________________________________________________ Because either DECnet-VAX or the LAT terminal server might also try to use the Ethernet adapter (a shareable device), you must shut down DECnet-VAX and the LAT terminal server before you run the device test phase, if you want to test the Ethernet adapter. 10.3.9 DR11-W Data Interface The DR11-W data interface uses an internal logical loopback mode that tests all functionality except that of module connectors, cables, and transceivers. _______________________ Caution _______________________ Only Digital Services personnel should set up the DR11-W for UETP testing. ______________________________________________________ 10-10 Running UETP 10.3 Setting Up for UETP Because random external patterns are generated during this operation, the user device or other processor might need to be isolated from the DR11-W being tested until the testing is completed. To test the DR11-W properly, the E105 switchpack must be set as follows: Switch 1 Switch 2 Switch 3 Switch 4 Switch 5 Off On Off Off On When UETP testing is completed, restore the DR11-W to the proper operating configuration. 10.3.10 DRV11-WA Data Interface The DRV-WA data interface is a general-purpose, 16-bit, parallel, direct-memory-access (DMA) data interface. _______________________ Caution _______________________ Only Digital Services personnel should set up the DRV11-WA for UETP testing. ______________________________________________________ To prepare the DRV11-WA driver on a Micro/VAX computer for UETP testing, be sure the following conditions exist: o The jumpers on the DRV11-WA board are set to W2, W3, and W6. o A loop-back cable is connected to the DRV11-WA board. o The DRV11-WA board is in a slot from 8 to 12. If the DRV11-WA is in a slot other than 8 to 12, you might get timeout errors. When UETP testing is completed, restore the DRV11-WA to the proper operating configuration. 10-11 Running UETP 10.3 Setting Up for UETP 10.3.11 DR750 or DR780 (DR32 Interface) The DR32 is an interface adapter that connects the internal memory bus of a VAX processor to a user-accessible bus called the DR32 device interconnect (DDI). _______________________ Caution _______________________ Only Digital Services personnel should set up the DR750 or DR780 for UETP testing. ______________________________________________________ To prepare the DR750 or the DR780 for UETP testing, use the following procedure: 1. Copy the DR780 microcode file, XF780.ULD, from the diagnostic medium to SYS$SYSTEM. Use the procedure described in the documentation provided with the DR780 Microcode Kit. 2. Turn off the power to the DR780. 3. Make the following DR780 backplane jumper changes: o Remove the jumper from W7 and W8. o Add a jumper from E04M1 to E04R1. o Add a jumper from E04M2 to E04R2. 4. Disconnect the DDI cable from the DR780. This cable is either a BC06V-nn cable, which can be disconnected, or a BC06R-nn cable, which requires that you remove its paddle card from the backplane of the DR780. 5. Restore power to the DR780. When UETP testing is completed, restore the DR750 or the DR780 to the proper operating configuration. 10.3.12 MA780 Multiport Memory Make sure that the MA780 is set up according to the guidelines for shared memory in the Guide to Maintaining a VMS System. If you run the MA780 device test individually, the logical name CTRLNAME must be defined as MPM, regardless of the memory name. As an alternative, you can enter "MPM" in response to the controller designation prompt. 10-12 Running UETP 10.3 Setting Up for UETP 10.3.13 Second LPA11-K Device If you have two LPA11-Ks, be sure that each is given a systemwide logical name in the SYS$MANAGER:LPA11STRT.COM file. The logical name for the first LPA11-K should be LPA11$0, and the logical name for the second LPA11-K should be LPA11$1. 10.3.14 Devices Not Tested UETP does not test the following devices; their status has no effect on UETP execution: o Devices that require operator interaction (such as card readers) o Software devices (such as the null device and local memory mailboxes) UETP does not have specific tests for UDA, HSC, or CI devices; they are tested implicitly by the disk, magnetic tape, and DECnet-VAX tests. UETP also does not test the console terminal or console drives. If you boot the system, log in, and start UETP, you have shown that these devices can be used. 10.3.15 VAXcluster Testing Before you run UETP in a VAXcluster environment, you should check the SYSTEST_CLIG account. The SYSTEST_CLIG account parallels SYSTEST except that it is dedicated to running the cluster-integration test. The requirements for the SYSTEST_CLIG account are as follows: 1. The account should be present in the user authorization file, exactly as distributed by Digital on each system in your VAXcluster. ________________________ Note ________________________ The SYSTEST_CLIG account might have been disabled as part of the VMS upgrade procedure. If it was disabled, you should reenable the SYSTEST_CLIG account and give it a null password before you run UETP. ______________________________________________________ 10-13 Running UETP 10.3 Setting Up for UETP To reenable the SYSTEST_CLIG account, enter the following commands: $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> MODIFY /FLAGS=NODISUSER /NOPASSWORD SYSTEST_CLIG UAF> EXIT ________________________ Note ________________________ Digital recommends that you disable the SYSTEST_CLIG account after testing has completed. ______________________________________________________ To disable the SYSTEST_CLIG account, enter the following commands: $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> MODIFY /FLAGS=DISUSER SYSTEST_CLIG UAF> EXIT 2. The privileges and quotas of the SYSTEST_CLIG account should match those of the SYSTEST account. UETP requires little additional preparation for the cluster-integration test phase beyond the requirements for other UETP test phases. The additional requirements for cluster integration testing are as follows: 1. Your system must be a member of a VAXcluster. If it is not, UETP displays a message and does not attempt to run the test. 2. Your system must use the same deadlock detection interval as the other systems in the VAXcluster. (The deadlock detection interval is set by the SYSGEN parameter DEADLOCK_WAIT. It is normally not changed from the default value, which is 10 seconds.) 3. The files UETCLIG00.COM and UETCLIG00.EXE, located in SYS$TEST, are necessary for each system included in the test. 10-14 Running UETP 10.3 Setting Up for UETP 4. DECnet-VAX must be set up between the VAXcluster nodes; UETP uses DECnet-VAX to create a process on those nodes. All checks that the test makes depend on its ability to create the SYSTEST_CLIG processes and to communicate with them using DECnet-VAX. 5. There must be a [SYSTEST] or [SYS0.SYSTEST] directory on some disk available to the VAXcluster for each node (both VMS and HSC) in the cluster. The test uses the same directory as the UETP disk test to create a file on each cluster node and to see if some other VMS node in the cluster can share access to that file. There must be one such directory per node; the test continues with the next cluster node once it has finished with a file. 10.3.16 Testing A Small-Disk System After you install the VMS operating system on a small system disk (for example, an RD53), you may not have the 1200 blocks of free disk space required to run UETP successfully. If you do not have 1200 free blocks on your system disk, use VMSTAILOR or DECW$TAILOR to remove some files from the system disk before you run UETP. For instructions on using VMSTAILOR and DECW$TAILOR see Chapter 12. 10.3.17 DECnet-VAX Phase The DECnet-VAX phase of UETP uses more system resources than other tests. You can, however, minimize disruptions to other users by running the test on the "least busy" node. By default, the file UETDNET00.COM specifies the node from which the DECnet-VAX test will be run. To run the DECnet- VAX test on a different node, enter the following command before you invoke UETP: $ DEFINE/GROUP UETP$NODE_ADDRESS node_address This command equates the group logical name UETP$NODE_ ADDRESS to the node address of the node in your area on which you want to run the DECnet-VAX phase of UETP. 10-15 Running UETP 10.3 Setting Up for UETP For example: $ DEFINE/GROUP UETP$NODE_ADDRESS 9.999 ________________________ Note ________________________ When you use the logical name UETP$NODE_ADDRESS, UETP tests only the first active circuit found by NCP. Otherwise, UETP tests all active testable circuits. ______________________________________________________ When you run UETP, a router node attempts to establish a connection between your node and the node defined by UETP$NODE_ADDRESS. Occasionally, the connection between your node and the router node might be busy or non- existent. When this happens, the system displays the following error messages: %NCP-F-CONNEC, Unable to connect to listener -SYSTEM-F-REMRSRC, resources at the remote node were insufficient %NCP-F-CONNEC, Unable to connect to listener -SYSTEM-F-NOSUCHNODE, remote node is unknown 10.4 Preparing Vector Processors and the VVIEF No preparation is required to test vector processors. UETP automatically loads all installed and enabled vector processors during the load phase, and automatically tests all installed and enabled vector processors during the device test phase. However, UETP cannot load the VAX Vector Instruction Emulation Facility (VVIEF) during the load phase, and will not automatically test VVIEF. To test VVIEF, you must do the following before running UETP: 1. Edit the file UETCONT00.DAT to add the following line: Y Y UETVECTOR.EXE "DEVICE_TEST" 2. Make sure VVIEF was activated when the system was booted. To determine if the VVIEF was activated, enter the following DCL commands: $ X = F$GETSYI("VECTOR_EMULATOR") $ SHOW SYMBOL X 10-16 Running UETP 10.4 Preparing Vector Processors and the VVIEF If the system displays a value of 1, VVIEF is loaded; if the system displays a value of 0, VVIEF is not loaded. The VVIEF test can be executed as an individual test using the RUN command, as described in Section 10.7.2.2. 10.5 Starting UETP When you have logged in and prepared the system and devices, you are ready to begin the test. To start UETP, enter the following command and press RETURN: $ @UETP UETP displays the following prompt: Run "ALL" UETP phases or a "SUBSET" [ALL]? Throughout the startup dialog, brackets indicate the default value, which you can choose by pressing RETURN. When running UETP for the first time, it is a good idea to choose the default value (ALL) and run all the phases. If you choose ALL, UETP displays three more questions, which are described in Section 10.5.2 through Section 10.5.4. If you want to run all the test phases, skip the next section. 10.5.1 Running a Subset of Phases You can run a single phase by entering SUBSET or S in response to the following prompt: Run "ALL" UETP phases or a "SUBSET" [ALL]? If you enter S or SUBSET, UETP prompts you for the phase you want to run as follows: You can choose one or more of the following phases: DEVICE, LOAD, DECNET, CLUSTER Phases(s): There is no default; enter one or more phase names from the list. Separate two or more phases with spaces or commas. If your choice includes the LOAD phase, UETP displays the three prompts described in the next sections. To run the LOAD phase, refer to Section 10.5.3. 10-17 Running UETP 10.5 Starting UETP If you exclude the LOAD phase, UETP responds with only two prompts: How many passes of UETP do you wish to run [1]? Do you want Long or Short report format [Long]? Section 10.5.2 and Section 10.5.4 discuss these questions. After you answer both questions, the phase you have selected runs to completion. 10.5.2 Single Run Versus Multiple Passes If you specified the default ALL or a subset of phases at the last prompt, UETP displays the following message: How many passes of UETP do you wish to run [1]? You can repeat the test run as many times as you want. If you enter 1 in response to the prompt (or press RETURN for the default), UETP stops after completing a single run. If you specify a number greater than 1, UETP restarts itself until it completes the number of passes (runs) specified. You can run UETP once to check that the system is working, or many times to evaluate the system's response to continuous use. For example, a service technician who is interested only in verifying that a newly installed system works might run UETP once or twice. A manufacturing technician might let the system run for several hours as part of the system integration and test. When you specify multiple UETP runs, you might want to request a short console log (see Section 10.5.4). Make certain that all line printers and hardcopy terminals have enough paper, because each run requires two pages. 10.5.3 Defining User Load for Load Test After you specify the number of passes, UETP prompts you as follows: How many simulated user loads do you want [n]? ________________________ Note ________________________ UETP displays this prompt only if you choose to run the LOAD phase, either implicitly (by running 10-18 Running UETP 10.5 Starting UETP all phases) or explicitly (by running a subset and specifying the LOAD phase). ______________________________________________________ The load test simulates a situation in which a number of users (detached processes) are competing for system resources. In response to this prompt, enter the number of users you want to simulate for this test. The number in brackets is the default value that UETP computed for your system. The default value depends on the amount of memory and the paging and swapping space that your system has. Although the given default value is the best choice, you can increase or decrease the user load by entering your own response to the prompt. However, be aware that an increase might cause the test to fail because of insufficient resources. If you want to see UETP display the user load equation as it runs, see Section 10.6.2. 10.5.4 Report Formats The following prompt allows you to choose one of two console report formats: Do you want Long or Short report format [Long]? If you choose the long report format (the default), UETP sends all error messages as well as information on the beginning and end of all phases and tests to the console terminal. UETP records all its output in the UETP.LOG file, regardless of your response to this question. In many cases, it may not be convenient to have UETP write the bulk of its output to the terminal. For example, if you run UETP from a hardcopy terminal, the output printing can slow the progress of the tests. This delay may not be a problem if you have requested only one run; however, you may prefer to use the short format if you intend to run multiple passes of UETP from a hardcopy terminal. If you request the short format, UETP displays status information at the console, such as error messages and notifications of the beginning and end of each phase. This information enables you to determine whether UETP is proceeding normally. If the short console log indicates 10-19 Running UETP 10.5 Starting UETP a problem, you can look at the file UETP.LOG for further information. UETP.LOG contains all the output generated by the various phases, as well as the status information displayed at the console. After you choose the report format, UETP initiates its sequence of tests and runs to completion. If UETP does not complete successfully, refer to Section 10.6 for troubleshooting information. 10.5.5 Termination of UETP At the end of a UETP pass, the master command procedure UETP.COM displays the time at which the pass ended. In addition, UETP.COM determines whether UETP needs to be restarted. (You can request multiple passes when you start up the test package; see Section 10.5.2.) At the end of an entire UETP run, UETP.COM deletes temporary files and does other cleanup activities. Pressing Ctrl/Y or Ctrl/C lets you terminate a UETP run before it completes normally. Normal completion of a UETP run, however, includes the deletion of miscellaneous files that have been created by UETP for the purpose of testing. The use of Ctrl/Y or Ctrl/C might interrupt or prevent these cleanup procedures. The effect of these control characters depends on what part of UETP you are executing. For an explanation of the organization of UETP and its components, refer to Section 10.7. 10.5.5.1 Using Ctrl/Y Press Ctrl/Y to abort a UETP run. Note, however, that cleanup of files and network processes in the [SYSTEST] directory may not be complete. If you are running an individual test image, pressing Ctrl/Y interrupts the current UETP test and temporarily returns control to the command interpreter. While the test is interrupted, you can enter a subset of DCL commands that are executed within the command interpreter and do not cause the current image to exit. The VMS DCL Concepts Manual contains a table of commands that you can use within the command interpreter. In addition, you can enter any of the following commands: 10-20 Running UETP 10.5 Starting UETP o The CONTINUE command continues the test from the point of interruption (except during execution of the cluster test). o The STOP command terminates the test; the test aborts and control returns to the command interpreter. ________________________ Note ________________________ Using the STOP command may prevent cleanup procedures from executing normally. You should use the EXIT command if you want the image to do cleanup procedures before terminating. ______________________________________________________ o The EXIT command executes cleanup procedures and terminates the test (except during execution of the cluster test); control returns to the command interpreter. If you enter any DCL command other than CONTINUE, STOP and EXIT, the test does cleanup procedures and terminates, and the DCL command executes. 10.5.5.2 Using Ctrl/C Press Ctrl/C to interrupt a UETP run. You cannot continue the same test phase after you press Ctrl/C. UETP automatically goes to the next phase in the master command procedure. Some UETP phases react to Ctrl/C by cleaning up all activity and terminating immediately. Such tests display the following message: %UETP-I-ABORTC, 'testname' to abort this test, type ^C The phases that do not display the previous message terminate all processes they have started. These processes might not have a chance to complete normal cleanup procedures. If you are running an individual test image, however, you can use Ctrl/C to terminate the execution of the image and complete cleanup procedures. Note that Ctrl/C does not complete cleanup procedures for the cluster test. 10-21 Running UETP 10.6 Troubleshooting 10.6 Troubleshooting This section explains the role of UETP in interpreting operational errors in a VMS operating system. Section 10.6.4 discusses common errors that can appear in a UETP run and describes how to correct them. 10.6.1 Relationship of UETP to Error Logging and Diagnostics When UETP encounters an error, it reacts like a user program. It either returns an error message and continues, or it reports a fatal error and terminates the image or phase. In either case, UETP assumes the hardware is operating properly and it does not attempt to diagnose the error. If the cause of an error is not readily apparent, use the following methods to diagnose the error: o VMS Error Log Utility-Run the Error Log Utility to obtain a detailed report of hardware and system errors. Error log reports provide information about the state of the hardware device and I/O request at the time of each error. For information about running the Error Log Utility, refer to the VMS Error Log Utility Manual. o Diagnostic facilities-Use the diagnostic facilities to test exhaustively a device or medium to isolate the source of the error. 10.6.2 Interpreting UETP Output You can monitor the progress of UETP tests at the terminal from which they were started. This terminal always displays status information, such as messages that announce the beginning and end of each phase and messages that signal an error. The tests send other types of output to various log files, depending on how you started the tests (see Section 10.6.3). The log files contain output generated by the test procedures. Even if UETP completes successfully, with no errors displayed at the terminal, it is good practice to check these log files for errors. Furthermore, when errors are displayed at the terminal, check the log files for more information about their origin and nature. 10-22 Running UETP 10.6 Troubleshooting Each test returns a final completion status to the test controller image, UETPHAS00, using a termination mailbox. This completion status is an unsigned longword integer denoting a condition value. As a troubleshooting aid, UETPHAS00 displays the test's final completion status using the $FAO and $GETMSG system services. Sometimes, however, the $FA0 service needs additional information which cannot be provided using the termination mailbox. When this happens, UETP displays an error message similar to the following: UETP-E-ABORT, !AS aborted at !%D When UETP displays these types of error messages, check the log files for more information. You can also run the individual test to attempt to diagnose the problem. The error messages that appear at the terminal and within the log files have two basic sources: o UETP tests o System components that are tested To interpret the messages, you might need to refer either to the VMS System Messages and Recovery Procedures Reference Manual or to the manual that describes the individual system component. Several parts of UETP, such as some device tests, UETINIT00.EXE, UETCLIG00.EXE, and UETDNET00.COM, let you obtain additional information concerning the progress of the test run or the problems it encounters. Because this information is usually insignificant, it is not displayed on the screen. To view the information, enter the following command to define the logical name MODE and run the program: $ DEFINE MODE DUMP The following example shows the output for UETINIT00.EXE on a VAX 11/750 system: 10-23 Running UETP 10.6 Troubleshooting $ RUN UETINIT00 Welcome to VAX/VMS UETP Version V5.5 %UETP-I-ABORTC, UETINIT00 to abort this test, type ^C You are running on an 11/750 CPU with 8704 pages of memory. The system was booted from _DRA0:[SYS0.]. Run "ALL" UETP phases or a "SUBSET" [ALL]? How many passes of UETP do you wish to run [1]? The default number of loads is the minimum result of 1) CPU_SCALE * ((MEM_FREE + MEM_MODIFY) / (WS_SIZE * PER_WS_INUSE)) 0.80 * (( 8704 + 323) / ( 350 * 0.20)) = 103 2) Free process slots = 56 3) Free page file pages / Typical use of page file pages per process 18040 / 1000 = 18 How many simulated user loads do you want [18]? Do you want Long or Short report format [Long]? UETP starting at 19-OCT-1991 09:08:26.71 with parameters: DEVICE LOAD DECNET CLUSTER phases, 1 pass, 18 loads, long report. $ This program does not initiate any phase; it displays the equation used by UETP to determine user load and the specific factors that are employed in the current run. You should respond to the questions by pressing RETURN. After you respond to the first prompt, the program displays the expressions that determine the default number of simultaneous processes. The following definitions apply: o CPU_SCALE refers to the relative processing power of the CPU in relation to a VAX-11/780 computer. For example, a VAX-11/785 computer has a CPU_SCALE of 1.5 because it has 1.5 times the processing power of a VAX-11/780 (1.0) computer. o MEM_FREE represents memory in pages available to users. 10-24 Running UETP 10.6 Troubleshooting o MEM_MODIFY represents memory pages on the modified page list. o WS_SIZE represents working set size. o PER_WS_INUSE represents typical percentage of the working set in active use for each process. UETINIT00 also displays the specific values represented by the expressions. In this example, UETP selects 18 as the default for simulated user loads, because 18 is the minimum result of the three expressions. You should deassign the logical name MODE before running UETP, unless you prefer to see the previous breakdown every time you run UETP. 10.6.2.1 Defining a Remote Node for UETP Ethernet Testing Occasionally during the UETUNAS00 test, it is difficult to determine whether the problem reports concern the device under test or the remote device. The easiest way to ensure proper error reporting is to define a "good turnaround." A "good turnaround" is a remote node that you know turns around Ethernet packets correctly and is up and waiting in the ready state. You can make the UETUNAS00 test use a known "good turnaround" by performing the following actions. In the commands that follow, assume that the "good" device is on node BETA, and that node BETA is already defined in the network database. 1. Find the address of the "good" Ethernet node by using the Network Control Program (NCP). In order to use NCP, the following conditions must apply: o DECnet-VAX must be up and running on the system. o The account you are using must have TMPMBX and NETMBX privileges. Enter the following commands and press RETURN: $ RUN SYS$SYSTEM:NCP NCP> TELL HOYDEN SHOW EXECUTOR STATUS 10-25 Running UETP 10.6 Troubleshooting If node HOYDEN has not been defined in your network database, NCP displays an error message. In this event, specify another "good" node and retry the command. Otherwise, see your system or network manager. NCP displays information similar to the following: Node Volatile Status as of 19-OCT-1991 16:13:02 Executor node = 19.617 (HOYDEN) State = on Physical address = AA-00-04-00-69-4E Active links = 6 Delay = 1 2. Use the displayed hardware address (in this case, AA00040046D3) to define the logical name TESTNIADR to point to the "good turnaround." Note that you do not specify the hyphens (-). First, log in to the SYSTEST account. Then enter the following command: $ DEFINE/SYSTEM TESTNIADR AA00040046D3 3. Run UETP. 4. When UETP has completed, deassign the logical name TESTNIADR by entering the following command: $ DEASSIGN/SYSTEM TESTNIADR 10.6.3 Log Files UETP stores all information generated by all UETP tests and phases from its current run in one or more UETP.LOG files, and it stores the information from the previous run in one or more OLDUETP.LOG files. If a run of UETP involves multiple passes, there will be one UETP.LOG or one OLDUETP.LOG file for each pass. At the beginning of a run, UETP deletes all OLDUETP.LOG files, and renames any UETP.LOG files to OLDUETP.LOG. Then UETP creates a new UETP.LOG file and stores the information from the current pass in it. Subsequent passes of UETP create higher versions of UETP.LOG. Thus, at the end of a run of UETP that involves multiple passes, there is one UETP.LOG file for each pass. In producing the files 10-26 Running UETP 10.6 Troubleshooting UETP.LOG and OLDUETP.LOG, UETP provides the output from the two most recent runs. If the run involves multiple passes, UETP.LOG contains information from all the passes. However, only information from the latest run is stored in this file. Information from the previous run is stored in a file named OLDUETP.LOG. Using these two files, UETP provides the output from its tests and phases from the two most recent runs. The cluster test creates a NETSERVER.LOG file in SYS$TEST for each pass on each system included in the run. If the test is unable to report errors (for example, if the connection to another node is lost), the NETSERVER.LOG file on that node contains the result of the test run on that node. UETP does not purge or delete NETSERVER.LOG files; therefore, you must delete them occasionally to recover disk space. If a UETP run does not complete normally, SYS$TEST might contain other log files. Ordinarily these log files are concatenated and placed within UETP.LOG. You can use any log files that appear on the system disk for error checking, but you must delete these log files before you run any new tests. You may delete these log files yourself or rerun the entire UETP, which checks for old UETP.LOG files and deletes them. 10.6.4 Possible UETP Errors This section is intended to help you identify and solve problems you might encounter running UETP. You should refer to this section if you need help understanding a system failure and isolating its cause. This section is not intended as a repair manual and is not expected to diagnose any flaws in your system. It should, however, help you to interpret and act upon the information in the error messages. If you are unable to correct an error after following the steps in this section, you should contact your Digital Services representative. Any information you can supply about the measures you have taken to isolate the problem will help your Digital Services representative diagnose the problem. 10-27 Running UETP 10.6 Troubleshooting The following are the most common failures encountered while running UETP: o Wrong quotas, privileges, or account o UETINIT01 failure o Ethernet device allocated or in use by another application o Insufficient disk space o Incorrect VAXcluster setup o Problems during the load test o DECnet-VAX error o Lack of default access for the FAL object o Errors logged but not displayed o No PCB or swap slots o Hangs o Bug checks and machine checks The following sections describe these errors and offer the best course of action for dealing with each one. 10.6.4.1 Wrong Quotas, Privileges, or Account If your assigned quotas or privileges do not match standard quotas and privileges for the SYSTEST account, UETP displays the following error message: ********************** * UETINIT00 * * Error count = 1 * ********************** -UETP-W-TEXT, The following: OPER privilege, BIOLM quota, ENQLM quota, FILLM quota, are nonstandard for the SYSTEST account and may result in UETP errors. 10-28 Running UETP 10.6 Troubleshooting This message informs you that the OPER privilege and the BIOLM, ENQLM, and FILLM quotas either are not assigned correctly or are not assigned at all. ________________________ Note ________________________ UETP displays a similar message if you run the cluster integration test phase, and the privileges and quotas for the SYSTEST_CLIG account are incorrect. The SYSTEST and SYSTEST_CLIG accounts require the same privileges and quotas. Take the action described in this section for both accounts. ______________________________________________________ Solution To correct the problem, use the following procedure: 1. Display all privileges and quotas in effect for the SYSTEST account using the AUTHORIZE utility as follows: $ RUN SYS$SYSTEM:AUTHORIZE UAF> SHOW SYSTEST Username: SYSTEST Owner: SYSTEST-UETP Account: SYSTEST UIC: [1,7] ([SYSTEST]) CLI: DCL Tables: DCLTABLES Default: SYS$SYSROOT:[SYSTEST] LGICMD: LOGIN Login Flags: Primary days: Mon Tue Wed Thu Fri Sat Sun Secondary days: No access restrictions Expiration: (none) Pwdminimum: 8 Login Fails: 0 Pwdlifetime: 14 00:00 Pwdchange: 19-OCT-1991 10:12 Last Login: (none) (interactive), (none) (non-interactive) Maxjobs: 0 Fillm: 100 Bytlm: 32768 Maxacctjobs: 0 Shrfillm: 0 Pbytlm: 0 Maxdetach: 0 BIOlm: 300 JTquota: 1024 Prclm: 8 DIOlm: 300 WSdef: 256 Prio: 4 ASTlm: 100 WSquo: 512 Queprio: 0 TQElm: 100 WSextent: 2048 CPU: (none) Enqlm: 300 Pgflquo: 45000 Authorized Privileges: CMKRNL CMEXEC SYSNAM GRPNAM DETACH DIAGNOSE LOG_IO GROUP PRMCEB PRMMBX SETPRV TMPMBX NETMBX VOLPRO PHY_IO SYSPRV 10-29 Running UETP 10.6 Troubleshooting Default Privileges: CMKRNL CMEXEC SYSNAM GRPNAM DETACH DIAGNOSE LOG_IO GROUP PRMCEB PRMMBX SETPRV TMPMBX NETMBX VOLPRO PHY_IO SYSPRV UAF> SHOW SYSTEST_CLIG . . . UAF> EXIT 2. Check that the default privileges and quotas assigned to the account match the following: Privileges CMKRNL CMEXEC NETMBX DIAGNOSE DETACH PRMCEB PRMMBX PHY_IO GRPNAM TMPMBX VOLPRO LOG_IO SYSNAM SYSPRV SETPRV GROUP Quotas BIOLM: 18 PRCLM: 8 DIOLM: 55 ASTLM: 100 FILLM: 100 BYTLM: 32768 TQELM: 20 CPU: no limit ENQLM: 300 PGFLQUOTA: 20480 WSDEFAULT: 256 WSQUOTA: 512 WSEXTENT: 2048 3. If any privileges or quotas are incorrect, run the Authorize Utility (AUTHORIZE) to add them (AUTHORIZE is explained in the VMS Authorize Utility Manual). If you are logged in to the wrong account, the following error message asks you to log in to the SYSTEST account: 10-30 Running UETP 10.6 Troubleshooting $ @UETP ********************** * UETINIT00 * * Error count = 1 * ********************** -UETP-E-ABORT, UETINIT00 aborted at 19-OCT-1991 14:24:10.13 -UETP-E-TEXT, You are logged in to the wrong account. Please log in to the SYSTEST account. $ You must run UETP from the SYSTEST account. 10.6.4.2 UETINIT01 Failure UETINIT01 failures are related to peripheral devices; this type of error message might indicate any of the following: o Device failure o Device not supported or not mounted o Device allocated to another user o Device write-locked o Lost vacuum on a magnetic tape drive o Drive off line In some cases, the course of action you should take is specified explicitly in the error message. For example, you might receive a message from the Operator Communication Facility (OPCOM) process informing you of a problem and recommending a corrective measure: %OPCOM, 19-OCT-1991 14:10:52.96, request 1, from user SYSTEST Please mount volume UETP in device _MTA0: %MOUNT-I-OPRQST, Please mount volume UETP in device _MTA0: Other error messages might relate information in which the solution is specified implicitly: 10-31 Running UETP 10.6 Troubleshooting %UETP-S-BEGIN, UETDISK00 beginning at 19-OCT-1991 13:34:46.03 ********************** * DISK_DRA * * Error count = 1 * ********************** -UETP-E-TEXT, RMS file error in file DRA0:DRA00.TST -RMS-E-DNR, device not ready or not mounted %UETP-S-ENDED, UETDISK00 ended at 19-OCT-1991 13:34:46.80 This message tells you that a disk drive is either not ready or not mounted. From this information, you know where to look for the cause of the failure-at the disk drive. If you cannot see the cause of the problem immediately, check the setup instructions in Section 10.3. In other cases, the cause of a failure might not be obvious from the information in the message. The problem might be related to hardware rather than software. For example, the Ethernet adapter test may produce one of the following messages if UETP does not have exclusive access to the Ethernet adapter: o Intermodule cable unplugged o Self-test failure code 0000000 To run the self-test diagnostic on the Ethernet adapter successfully, UETP needs exclusive access to the adapter. As explained in Section 10.3.8, you must shut down DECnet- VAX and the LAT terminal server before running the UETP device test phase if you want to test the Ethernet adapter. Solution To determine where or when the failure occurs in the execution of UETP, use the following procedure: o Run the device test individually (see Section 10.5.1). By doing this, you can determine if the failure can be recreated. Also, you are isolating the cause of the problem by reproducing it using the least amount of software possible. For example, if the failure occurs only when you run the entire device phase, and not when you run the affected device test individually, you can conclude the problem is related to device-interaction. Conversely, if you can recreate the error by running the 10-32 Running UETP 10.6 Troubleshooting single device test, then you have proved that the error is not related to device interaction. o Run the device test with different media. If your run of the single device test succeeded in reproducing the error, the magnetic tape or disk media could be defective. Running the same test with new media determines whether this is the problem. o Call Digital Services. If you have tried all the previous steps without solving the problem, you should contact your Digital Services representative. 10.6.4.3 Device Allocated or in Use by Another Application If DECnet-VAX software or the LAT software is running during the DEVICE phase, the UETUNAS00 test displays the following message: -UETP-W-TEXT, Device is in use by DECnet or another application Other UETP communication device tests display the following message: SYSTEM-W-DEVALLOC, device already allocated to another user Solution If you want to run the device test on the Ethernet Adapter, shut down DECnet-VAX and LAT software before beginning the test. 10.6.4.4 Insufficient Disk Space When you run continuous passes of UETP, log files accumulate on the disk from which UETP was run. These files reduce the amount of free disk space available for each successive pass. If the amount of disk space available becomes too small for the current load, the following error message appears: 10-33 Running UETP 10.6 Troubleshooting %UETP-S-BEGIN, UETDISK00 beginning at 19-OCT-1991 08:12:24.34 %UETP-I-ABORTC, DISK_DJA to abort this test, type ^C ********************** * DISK_DJA * * Error count = 1 * ********************** -UETP-F-TEXT, RMS file error in file DJA0:DJA00.TST -RMS-F-FUL, device full (insufficient space for allocation) ********************** * DISK_DJA * * Error count = 2 * ********************** -UETP-F-TEXT, RMS file error in file DJA0:DJA01.TST -RMS-F-FUL, device full (insufficient space for allocation) %UETP-E-DESTP, DISK_DJA stopped testing DJA unit 0 at 08:12:36.91 %UETP-S-ENDED, UETDISK00 ended at 19-OCT-1991 08:12:37.98 Solution Make more space available on the disk. You can do this by using one or more of the following techniques: o Delete unnecessary files to create more space. o Purge files, if multiple versions exist. o Mount a volume with sufficient space. o Check for disk quotas that may be enabled on the disk. If disk quotas are enabled, either disable or increase them (see the VMS SYSMAN Utility Manual for a description of the Disk Quota Utility). o Run VMSTAILOR if you have a small-disk system. See Chapter 4 for more information. See Section 10.2.1 and Section 10.3.2 for a further discussion of disk space. 10-34 Running UETP 10.6 Troubleshooting 10.6.4.5 Incorrect Setup of a VAXcluster Most problems that can occur during the cluster-integration test are related to improper setup of the VAXcluster or of UETP on the VAXcluster. These problems are most likely to occur at the following stages of the VAXcluster test: o Near the beginning, when processes on VMS nodes are started o Toward the end, when cluster file access is checked The cluster test phase shows that various VMS nodes in your cluster can simultaneously access files on selected nodes in the cluster. First, UETP tries to create a file on a disk drive that is accessible to the other selected nodes in the cluster. The following are the requirements for creating a file in the cluster test phase: o There must be a [SYSTEST] directory on the disk in either the master file directory (MFD) or in the root directory [SYS0.]. o The [SYSTEST] directory must be protected so that the SYSTEST account can create a file in it. If UETP is unable to find a suitable device on a certain node, the test displays a warning message and proceeds to the next cluster node. Nodes on which the operator's terminal (OPA0) is set to the "No broadcast" terminal characteristic will generate the following error message during the cluster test: ********************** * UETCLIG00master * * Error count = 1 * ********************** -UETP-E-TEXT, 0 operator consoles timed out on the cluster test warning and 1 operator console rejected it. -UETP-E-TEXT, Status returned was, "%SYSTEM-F-DEVOFFLINE, device is not in configuration or not available" Disregard this message if OPA0 is set to "No broadcast." 10-35 Running UETP 10.6 Troubleshooting Solution Whenever you suspect a problem, you should try to examine the SYS$TEST:NETSERVER.LOG file that was created when the SYSTEST_CLIG process was created. This file may contain additional error information that could not be transmitted to the node running the test. If it was not possible to create the SYSTEST_CLIG process on some node, the system accounting file for that node may contain a final process status in a process termination record. The following problems can occur during a cluster test: o Logging in at other nodes-This problem is due to incorrect setup for the cluster test at the remote VMS node. For example, if you specified a password for the SYSTEST_CLIG account or if you disabled the SYSTEST_CLIG account, the test displays the following message: %SYSTEM-F-INVLOGIN, login information invalid at remote node Refer to Section 10.3.15 and Section 10.6.2.1 for information on preparing for VAXcluster testing. o Communicating with other nodes-A message indicates a DECnet-VAX problem. Check the NETSERVER.LOG file on the affected node to determine the cause. o Taking out locks or detecting deadlocks-The most likely cause of this problem is that you are not logged in to the SYSTEST account. Another possibility is that your cluster is not configured properly. o Creating files on VAXcluster nodes-This problem is due to incorrect setup for the cluster test; refer to Section 10.3.15 for information on preparing for VAXcluster testing. 10.6.4.6 Problems During the Load Test A variety of errors can occur during the load test because the command procedures that are started during the tests run several utilities and do many functions. Tracking a problem can be difficult because UETP deletes the log files that are generated during the load test (see Section 10.7.3). 10-36 Running UETP 10.6 Troubleshooting Solution If a problem occurs during the load test and the cause is not obvious, you can modify UETP.COM to preserve the log files as follows: 1. Add the /NODELETE qualifier to the following line: $ TCNTRL UETLOAD00.DAT/PARALLEL_COUNT='LOADS/REPORT_TYPE='REPORT 2. Delete or comment out the following line: $ DELETE UETLO*.LOG;* Rerun the load test with these changes to try to recreate the problem. If you recreate the problem, look at the contents of the appropriate log file. You can determine which log file to read by understanding the scheme by which the load test names its processes and log files. (The log file names are derived from the process names.) The load test creates processes that are named in the following format: UETLOADnn_nnnn For example: %UETP-I-BEGIN, UETLOAD00 beginning at 19-OCT-1991 15:45:08.97 %UETP-I-BEGIN, UETLOAD02_0000 beginning at 19-OCT-1991 15:45:09.42 %UETP-I-BEGIN, UETLOAD03_0001 beginning at 19-OCT-1991 15:45:09.63 %UETP-I-BEGIN, UETLOAD04_0002 beginning at 19-OCT-1991 15:45:10.76 %UETP-I-BEGIN, UETLOAD05_0003 beginning at 19-OCT-1991 15:45:11.28 %UETP-I-BEGIN, UETLOAD06_0004 beginning at 19-OCT-1991 15:45:12.56 %UETP-I-BEGIN, UETLOAD07_0005 beginning at 19-OCT-1991 15:45:13.81 %UETP-I-BEGIN, UETLOAD08_0006 beginning at 19-OCT-1991 15:45:14.94 %UETP-I-BEGIN, UETLOAD09_0007 beginning at 19-OCT-1991 15:45:16.99 %UETP-I-BEGIN, UETLOAD10_0008 beginning at 19-OCT-1991 15:45:19.32 %UETP-I-BEGIN, UETLOAD11_0009 beginning at 19-OCT-1991 15:45:19.94 %UETP-I-BEGIN, UETLOAD02_0010 beginning at 19-OCT-1991 15:45:20.20 %UETP-I-BEGIN, UETLOAD03_0011 beginning at 19-OCT-1991 15:45:21.94 %UETP-I-BEGIN, UETLOAD04_0012 beginning at 19-OCT-1991 15:45:22.99 Note that if more than 10 processes are created, the numbering sequence for the UETLOADnn portion of the process name starts over at UETLOAD02; however, the 4 digits of the _nnnn portion continue to increase. 10-37 Running UETP 10.6 Troubleshooting Each load test process creates two log files. The first log file is created by the test controller; the second log file is created by the process itself. The log file that you need to look at for error information on any given load test process is the one that was created by the test controller (the first log file). The load test log file derives its file name from the process name, appending the last four digits of the process name (from the _nnnn portion) to UETLO. The test-controller log file and the process log file for each process use the same file name; however, the process log file has the higher version number of the two. For example, the log files created by the process UETLOAD05_0003 would be named as follows: UETLO0003.LOG;1 (test-controller log file) UETLO0003.LOG;2 (process log file) Make sure that you look at the log file with the lower version number; that file contains the load test commands and error information. After you have isolated the problem, restore UETP.COM to its original state and delete the log files from the load test (UETL0*.LOG;*); failure to delete these files might result in disk space problems. 10.6.4.7 DECnet-VAX Error A DECnet-VAX error message might indicate that the network is unavailable. Solution o If DECnet-VAX software is included in your system, register the product authorization key (PAK). For instructions, see the Appendix A. o If DECnet-VAX software is not included in your system, ignore the message; it is normal and does not affect the UETP run. 10-38 Running UETP 10.6 Troubleshooting If you encounter other DECnet-VAX-related errors, you should do the following: o Run DECnet-VAX software as a single phase (see Section 10.5.1) to determine whether the error can be recreated. o Refer to the VMS System Messages and Recovery Procedures Reference Manual. 10.6.4.8 Errors Logged but Not Displayed If no errors are displayed at the console terminal or reported in the UETP.LOG file, you should run the Error Log Utility to see if any errors were logged in the ERRLOG.SYS file. See the VMS Error Log Utility Manual for information about running the Error Log Utility. 10.6.4.9 No PCB or Swap Slots The following error message indicates that no process control block (PCB) or swap slots are available: %UETP-I-BEGIN, UETLOAD00 beginning at 19-OCT-1991 07:47:16.50 %UETP-I-BEGIN, UETLOAD02_0000 beginning at 19-OCT-1991 07:47:16.76 %UETP-I-BEGIN, UETLOAD03_0001 beginning at 19-OCT-1991 07:47:16.92 %UETP-I-BEGIN, UETLOAD04_0002 beginning at 19-OCT-1991 07:47:17.13 %UETP-I-BEGIN, UETLOAD05_0003 beginning at 19-OCT-1991 07:47:17.35 %UETP-I-BEGIN, UETLOAD06_0004 beginning at 19-OCT-1991 07:47:17.61 %UETP-W-TEXT, The process -UETLOAD07_0005- was unable to be created, the error message is -SYSTEM-F-NOSLOT, no pcb or swap slot available %UETP-W-TEXT, The process -UETLOAD08_0006- was unable to be created, the error message is -SYSTEM-F-NOSLOT, no pcb or swap slot available %UETP-W-TEXT, The process -UETLOAD09_0007- was unable to be created, the error message is -SYSTEM-F-NOSLOT, no pcb or swap slot available %UETP-W-TEXT, The process -UETLOAD10_0008- was unable to be created, the error message is -SYSTEM-F-NOSLOT, no pcb or swap slot available %UETP-W-TEXT, The process -UETLOAD11_0009- was unable to be created, the error message is -SYSTEM-F-NOSLOT, no pcb or swap slot available %UETP-W-ABORT, UETLOAD00 aborted at 19-OCT-1991 07:47:54.10 -UETP-W-TEXT, Aborted via a user Ctrl/C. *************************************************** 10-39 Running UETP 10.6 Troubleshooting * * END OF UETP PASS 1 AT 19-OCT-1991 07:48:03.17 * * *************************************************** Solution To solve this problem, use the following procedure: 1. Rerun individually the phase that caused the error message (the LOAD phase in the previous example) to see if the error can be reproduced. 2. Increase the size of the page file, using either the command procedure SYS$UPDATE:SWAPFILES.COM or the System Generation Utility (see the VMS System Generation Utility Manual). 3. Increase the SYSGEN parameter MAXPROCESSCNT, if necessary, and reboot the system. 4. Increase both the page file size and the MAXPROCESSCNT, if necessary. 10.6.4.10 Hangs If there is no keyboard response or system disk activity, the system may be hung. Solution A system hang can be difficult to trace; you should save the dump file for reference. To learn why the system hung, run the System Dump Analyzer as described in the VMS System Dump Analyzer Utility Manual. Reasons for a system hang include the following: o Insufficient pool space-Increase the value of the SYSGEN parameter NPAGEVIR and reboot the system. o Insufficient page file space-Increase the page file space using the System Generation Utility as described in the VMS System Generation Utility Manual. o I/O device failure causing driver-permanent loop-Call Digital Services. 10-40 Running UETP 10.6 Troubleshooting 10.6.4.11 Lack of Default Access for the FAL Object With VMS Version 5.2, the network configuration procedure NETCONFIG.COM no longer provides access for the FAL network object by default. UETP, however, still assumes the existence of default access for the FAL object (this assumption will be removed in a future release of VMS). When you install DECnet using the defaults presented by the procedure NETCONFIG.COM, the UETP DECnet phase may produce error messages that were not seen in earlier versions. If default FAL access is disabled at the remote node selected by UETP for DECnet testing (the adjacent node on each active circuit, or a node defined by the group logical name UETP$NODE_ADDRESS), messages similar to the following will appear: %UETP-W-TEXT, The process -SVA019841_0001- returned a final status of: %COPY-E-OPENOUT, error opening !AS as output These messages are followed by: %COPY-E-OPENOUT, error opening 9999""::SVA019841.D1; as output -RMS-E-CRE, ACP file create failed -SYSTEM-F-INVLOGIN, login information invalid at remote node %COPY-W-NOTCOPIED, SYS$COMMON:[SYSTEST]UETP.COM;2 not copied %UETP-E-TEXT, Remote file test data error These messages can be ignored. 10.6.4.12 Bugchecks and Machine Checks When the system aborts its run, a bugcheck message appears at the console. Solution Call Digital Services. Often a hardware problem causes bugchecks and machine checks; there is no easy way to solve bugchecks or machine checks. It is important, however, that you save the SYS$SYSTEM:SYSDUMP.DMP and ERRLOG.SYS files so that they are available for examination. It is also important to know whether the failure can be recreated; you can verify this by running UETP again. 10-41 Running UETP 10.7 UETP Tests and Phases 10.7 UETP Tests and Phases This section explains in detail the organization of UETP and the individual components within the test package. You run UETP by starting a master command procedure containing commands to start each test phase. The procedure begins by prompting you for information needed by the various test phases. (See Section 10.5 for a detailed description of starting UETP.) The master command procedure, UETP.COM, contains commands that initiate each test phase. UETP.COM also contains commands that do such tasks as defining logical names and manipulating files generated by the tests. The UETP.COM procedure also issues commands to start the test controlling program, UETPHAS00.EXE, which, in turn, controls each test phase. The test controller starts up multiple detached processes. It also reports their completion status and other information the processes report to it. The following sections describe the various UETP test phases. 10.7.1 Initialization Phase The following occurs during the initialization phase: o The image UETINIT00.EXE prompts you for information (see Section 10.5). Your information defines variables that affect the execution of UETP tests. o The image UETINIT01.EXE gathers information on all the controllers in the system and on their associated devices. This image writes the information into a file called UETINIDEV.DAT. o Using the information in UETSUPDEV.DAT, UETINIT01.EXE verifies which devices in the configuration are operable by running the appropriate device test. Each device test completes a simple read/write operation to each device. If a device fails this test, the device's entry in UETINIDEV.DAT specifies that the device cannot be tested. As a result, subsequent UETP tests ignore that device. 10-42 Running UETP 10.7 UETP Tests and Phases o For each testable controller, UETINIT01.EXE writes a line into a file called UETCONT00.DAT. The line associates a test file with the controller it tests. A summary of UETINIDEV.DAT always exists in UETP.LOG, and UETINIT01.EXE sends that summary to the console if you have requested the long report format. 10.7.2 Device Test Phase The device test phase includes separate tests for each type of device, such as disk, magnetic tape, line printer, and terminal. This section explains the device test phase and presents instructions for testing a single device. If you want to run the entire device test phase individually, refer to Section 10.5.1. 10.7.2.1 How the Device Phase Works The UETP device test phase starts an executable image, the phase controller UETPHAS00, which creates a detached process for every device controller to be tested. For example, if a system includes three terminal controllers, one line printer controller, and two disk controllers, the image creates six detached processes. In parallel, the detached processes execute images that test the various types of devices. The initialization phase of UETP creates a file called UETINIDEV.DAT and a file called UETCONT00.DAT. UETINIDEV.DAT contains data on the VMS-supported controllers in the system and their associated devices; UETCONT00.DAT associates a device test image with each testable controller. UETPHAS00 uses the information in UETCONT00.DAT to find a device controller name to pass to each detached process that it creates. UETPHAS00 passes the controller name by writing it to a mailbox that is SYS$INPUT to individual tests. Each detached process uses that data to determine which controller to test. The test image then searches UETINIDEV.DAT for the device controller and for all testable units on that controller. The phase controller terminates when all devices on all controllers have completed testing. 10-43 Running UETP 10.7 UETP Tests and Phases Because UETCONT00.DAT is deleted automatically at the end of a UETP run, you cannot run the device phase unless you start UETP.COM; you can run only individual test images. UETINIDEV.DAT exists in SYS$TEST unless you delete it. 10.7.2.2 Running a Single Device Test You must be logged in to the SYSTEST account to run the individual tests as described in this section. Also, a copy of UETINIDEV.DAT must exist. If a copy of the file is not present from a previous run (a run of the entire UETP or a run of the device test phase creates UETINIDEV.DAT), you can create it. Note that when you run a single test, no log file is created; the test sends all its output to your terminal. If you do not want to test all the device types, you can test a specific controller by choosing a test image name from Table 10-1 and executing it as in the following example: $ RUN UETTTYS00 Controller designation?: TTB UETP prompts you for the controller designation and the device code. Unless you are testing your own terminal, you must explicitly designate a controller name. If you are running the terminal test, you can press RETURN to test your terminal only. If you plan to repeat the run several times, you might find it more convenient to define the logical name CTRLNAME as follows: $ DEFINE CTRLNAME TTB $ RUN UETTTYS00 When you define the controller name in this way, the logical name CTRLNAME remains assigned after the test completes. To deassign this logical name, use the DCL command DEASSIGN as follows: $ DEASSIGN CTRLNAME 10-44 Running UETP 10.7 UETP Tests and Phases Format of UETINIDEV.DAT The UETINIDEV.DAT file is an ASCII sequential file that you can type or edit if necessary. The contents of this file are shown in the following command sequence: $ TYPE UETINIDEV.DAT DDB x ddd UCB y uuuuu nnnnnnnnn.nnn END OF UETINIDEV.DAT The symbols in this example are defined as follows: ___________________________________________________________ Symbol_________Value_______________________________________ x T, if there are any testable units for this controller; N, if this controller is not to be tested y T, if this unit is testable; N, if this unit is not testable ddd Device controller name, for example DUA uuuuu Device unit number, for example 25 nnnnnnnnn.nnn UETP device test name for the unit, for _______________example,_UETDISK00.EXE______________________ UETINIDEV.DAT contains a DDB (device data block) line for each controller connected or visible to your system. After the DDB line there is a UCB (unit control block) line for each unit connected to that controller. In addition, if your system uses MA780 memory in a loosely coupled CPU configuration, UETINIDEV.DAT includes one UCB line for each MA780 memory. A device test can test a particular device only if both the DDB line and the UCB line indicate that the device is testable. Running a Test in Loop Mode If you want to put extra stress on a device, you can run the device test in loop mode, which causes the test to run indefinitely. For example: 10-45 Running UETP 10.7 UETP Tests and Phases $ DEFINE MODE LOOP $ RUN UETDISK00 Controller designation?: DRA %UETP-I-TEXT, End of pass 1 with 980 iterations at 19-OCT-1991 16:18:51:03 ^C You must use Ctrl/C to terminate the test run. If you use Ctrl/Y, UETP does not complete cleanup procedures. Functions of Individual Device Tests For each disk in the system, the disk test allocates two files into which it randomly writes blocks of data. The test then checks the data, reports any errors to SYS$OUTPUT, and deletes the disk files. When you run the disk test phase in a cluster environment, the test accesses all disks that are mounted by the system being tested, and users of the disk being tested might encounter an insufficient disk space problem. You should warn users on remote nodes (who share disks with users on the local system) that UETP may be testing a disk they are using. The magnetic tape test exercises all the magnetic tape drives in the system. The test creates a large file on each mounted magnetic tape, into which it writes multiple sequential records of varying sizes. After writing the records, the test rewinds the magnetic tape, validates the written records, and reinitializes the magnetic tape. The terminal and line printer test generates several pages or screens of output, in which each page or screen contains a header line and a test pattern of ASCII characters. A header line contains the test name, the device name, the date, and the time. For the laboratory peripheral accelerator (LPA11-K), the test image determines the configuration on the LPA11-K's I/O bus. The image loads all types of microcode to the LPA11-K and reads or writes data for each device on the LPA11-K I/O bus. 10-46 Running UETP 10.7 UETP Tests and Phases The communications device tests fill the transmit message buffer with random data; then, using loopback mode, the tests transmit and receive the message several times. To check that the looped-back data is correct, an AST routine is associated with a $QIO read to compare the received message against the transmitted message. The procedure is repeated using messages of different lengths. The interface device tests put the devices they are testing in maintenance mode, write random data, and then verify the data. The MA780 device test creates and modifies mailboxes, common event flags, and global sections in shared memory; then it verifies that modifications can be made. You can run MA780 tests in parallel from separate systems so that the tests interact with each other through common MA780 memories. The Ethernet adapter test does self-test diagnostics on the device. It also does read and write tasks with test data that uses various adapter modes (such as internal loopback and external loopback). The vector processor device test performs simple vector- scalar and vector-vector arithmetic operations and compares the results with expected values. The test also uses vector-related system service extensions and forces the system to generate arithmetic and memory management exceptions. Table 10-1 lists the device test images and the devices to be tested. Table_10-1_Device_Tests____________________________________ Test_Image_Name__Devices_Tested____________________________ UETDISK00.EXE Disks UETTAPE00.EXE Magnetic tape drives and tape cartridge drives UETTTYS00.EXE Terminals and line printers (continued on next page) 10-47 Running UETP 10.7 UETP Tests and Phases Table_10-1_(Cont.)_Device_Tests____________________________ Test_Image_Name__Devices_Tested____________________________ UETLPAK00.EXE LPA11-K UETCOMS00.EXE DMC11, DMR11 UETDMPF00.EXE DMF32, DMP11 UETDR1W00.EXE DR11-W UETDR7800.EXE DR780, DR750 UETMA7800.EXE MA780 UETCDRO00.EXE RRD40, RRD50 UETUNAS00.EXE Ethernet Adapters UETVECTOR.EXE____Vector_Processor,_VVIEF___________________ 10.7.3 System Load Test Phase The purpose of the system load test is to simulate a number of terminal users who are demanding system resources simultaneously. The system load tests, directed by the file UETLOAD00.DAT, create a number of detached processes that execute various command procedures. Each process simulates a user logged in at a terminal; the commands within each procedure are the same types of commands that a user enters from a terminal. The load test creates the detached processes in quick succession, and the processes generally execute their command procedures simultaneously. The effect on the system is analogous to an equal number of users concurrently issuing commands from terminals. In this way, the load test creates an environment that is similar to normal system use. The load test uses the logical name LOADS to determine the number of detached processes to create. When you initiate the UETP command procedure, it prompts for the number of users to be simulated (see Section 10.5.3) and consequently the number of detached processes to be created. Your response, which depends on the amount of memory and the swapping and paging space in your system, defines the group logical name LOADS. 10-48 Running UETP 10.7 UETP Tests and Phases The UETP master command procedure deassigns all group logical names assigned by its tests as part of the termination phase. The group logical name LOADS remains assigned only if the UETP package does not complete normally. The command procedures executed by the load test can generate a large amount of output, depending on the number of detached processes created. For each detached process (or user), the test creates a version of an output file called UETLOnnnn.LOG ("nnnn" represents a string of numeric characters). The console displays only status information as the load test progresses. Whether the load test runs as part of the entire UETP or as an individual phase, UETP combines the UETLOnnnn.LOG files, writes the output to the file UETP.LOG, and deletes the individual output files. You can run the system load test as a single phase by selecting LOAD from the choices offered in the startup dialog (see Section 10.5.1). 10.7.4 DECnet-VAX Test Phase If DECnet-VAX software is included in your VMS system, a run of the entire UETP automatically tests DECnet-VAX hardware and software. Because communications devices are allocated to DECnet-VAX and the DECnet-VAX devices cannot be tested by the UETP device test, UETP will not test the Ethernet adapter if DECnet-VAX or another application has allocated the device. The DECnet-VAX node and circuit counters are zeroed at the beginning of the DECnet-VAX test to allow for failure monitoring during the run. As with other UETP phases, you can run the DECnet-VAX phase individually by following the procedure described in Section 10.5.1. 10-49 Running UETP 10.7 UETP Tests and Phases 10.7.4.1 Environment The DECnet-VAX test will work successfully on VMS systems connected to all DECnet-VAX supported node types, including routing and nonrouting nodes and several different types of operating systems (such as RSTS, RSX, TOPS, and RT). There must be some sort of default access on remote systems to copy files between systems. The DECnet-VAX phase tests the following: o The node UETP is running on. o All circuits in sequence, unless you have defined the logical name UETP$NODE_ADDRESS to be the remote node that you want to run the test on. If you have defined a remote node, the DECnet-VAX phase tests only one circuit. o All adjacent or first-hop nodes and all circuits in parallel. There is no limit on the number of communication lines supported by the tests. A test on one adjacent node should last no more than two minutes at normal communications transfer rates. ________________________ Note ________________________ UETP assumes your system has default access for the FAL object, even though the network configuration command procedure NETCONFIG.COM does not provide access for the FAL object by default. When you install DECnet software with the defaults presented by NETCONFIG.COM, the UETP DECnet phase might produce error messages. You can ignore these error messages. See Section 10.6.4.11 for more information. ______________________________________________________ 10.7.4.2 How the DECnet-VAX Phase Works UETP (under the control of UETPHAS00.EXE) reads the file UETDNET00.DAT and completes the following steps during the DECnet-VAX phase: 1. Executes a set of Network Control Program (NCP) LOOP EXECUTOR commands to test the node on which UETP is running. 10-50 Running UETP 10.7 UETP Tests and Phases 2. Uses NCP to execute the command SHOW ACTIVE CIRCUITS. The results are placed in UETININET.TMP, from which UETP creates the data file UETININET.DAT. The UETININET.TMP file contains the following information for any circuit in the ON state but not in transition: o Circuit name o Node address o Node name (if one exists) The UETININET.TMP file is used throughout the DECnet-VAX phase to determine which devices to test. 3. Uses the UETININET.TMP file to create an NCP command procedure for each testable circuit. Each command procedure contains a set of NCP commands to zero the circuit and node counters and to test the circuit and adjacent node by copying files back and forth. ________________________ Note ________________________ If you do not want the counters zeroed, do not test the DECnet-VAX software. ______________________________________________________ 4. Executes the command procedures from step 3 in parallel to simulate a heavy user load. The simulated user load is the lesser of the following values: o The number of testable circuits, multiplied by two o The maximum number of user-(detached) processes that can be created on the system before it runs out of resources (determined by UETINIT00) 5. Executes a program, UETNETS00.EXE, that uses the UETININET.DAT file to check the circuit and node counters for each testable circuit. If a counter indicates possible degradation (by being nonzero), its name and value are reported to the console. All counters are reported in the log file, but only the counters that indicate degradation are reported to the console. Following is an example of UETNETS00 output: 10-51 Running UETP 10.7 UETP Tests and Phases %UETP-S-BEGIN, UETNETS00 beginning at 19-OCT-1991 13:45:33.18 %UETP-W-TEXT, Circuit DMC-0 to (NODENAME1) OK. %UETP-I-TEXT, Node (NODENAME2) over DMC-1 response timeouts = 1. %UETP-I-TEXT, Circuit DMC-1 to (NODENAME2) local buffer errors = 34. %UETP-I-TEXT, Node (NODENAME3) over DMP-0 response timeouts = 3. %UETP-S-ENDED, UETNETS00 ended at 19-OCT-1991 13:45:36.34 Because degradation is not necessarily an error, the test's success is determined by you, not by the system. The following counters indicate possible degradation: For Circuits o Arriving congestion loss o Corruption loss o Transit congestion loss o Line down o Initialization failure o Data errors inbound o Data errors outbound o Remote reply timeouts o Local reply timeouts o Remote buffer errors o Local buffer errors o Selection timeouts o Remote process errors o Local process errors o Locally initiated resets o Network initiated resets For Nodes o Response timeouts o Received connect resource errors o Aged packet loss o Node unreachable packet loss o Node out of range packet loss 10-52 Running UETP 10.7 UETP Tests and Phases o Oversized packet loss o Packet format error o Partial routing update loss o Verification reject 10.7.5 Cluster-Integration Test Phase The cluster-integration test phase consists of a single program and a command file that depend heavily on DECnet- VAX software. This phase uses DECnet-VAX software to create SYSTEST_CLIG processes on each VMS node in the cluster and to communicate with each node. SYSTEST_CLIG is an account that is parallel to SYSTEST, but limited so that it can only be used as part of the cluster-integration test. The following restrictions on the SYSTEST_CLIG account are necessary for a correct run of the cluster test phase: o The account must be enabled and the password must be null. For more information, see Section 10.3.15. o The UIC must be the same as that of the SYSTEST account. o The account must have the same privileges and quotas as the SYSTEST account. For more information, see Section 10.6.4.1. o The account can allow login only through DECnet-VAX software. o The account must be locked into running UETCLIG00.COM when it logs in. These items are necessary to ensure the security and privacy of your system. If the test cannot create a SYSTEST_CLIG process on some VMS node, it gives the reason for the failure and ignores that node for the lock tests and for sharing access during the file test. Also, the test does not copy log files from any node on which it cannot create the SYSTEST_CLIG process. If there is a problem communicating with a SYSTEST_CLIG process after the process has been created, the test excludes it from further lock and file sharing tests. At the end of the cluster-integration test, an attempt is made to report any errors seen by that node. 10-53 Running UETP 10.7 UETP Tests and Phases UETCLIG00.EXE has two threads of execution: the primary and the secondary. The first, or primary thread, checks the cluster configuration (VMS nodes, HSC nodes, and the attached disks that are available to the node running the test). For selected VMS nodes, the primary thread attempts to start up a SYSTEST_CLIG process through DECnet- VAX software. If the primary thread was able to start a SYSTEST_CLIG process on a node, the node runs the command file UETCLIG00.COM, which starts up UETCLIG00.EXE and runs the secondary execution thread. The process running the primary thread checks to see that it can communicate with the processes running the secondary threads. It then instructs them to take out locks so that a deadlock situation is created. The primary thread tries to create a file on some disk on selected VMS and HSC nodes in the cluster. The primary thread writes a block, reads it back, and verifies it. The primary thread selects one VMS node at random and asks that node to read the block and verify it. The primary thread then extends the file by writing another block and has the secondary thread read and verify the second block. The file is deleted. The secondary processes exit. They copy to the primary process the contents of their SYS$ERROR files, so that the UETP log file and console report show all problems in a central place. DECnet-VAX software automatically creates a NETSERVER.LOG in SYS$TEST as the test is run, so that if necessary, you can read that file later from the node in question. During the test run, the primary process uses the system service SYS$BRKTHRU to announce the beginning and ending of the test to each VMS node's console terminal. You can define the group logical name MODE to the equivalence string DUMP to trace most events as they occur. Note that the logical name definitions apply only to the node on which they were defined. You must define MODE on each node in the VAXcluster on which you want to trace events. 10-54 11 _________________________________________________________________ Customizing VMS DECwindows Software This chapter describes the tasks that you must perform to customize VMS DECwindows software. If you have not installed VMS DECwindows software on your system, skip this chapter. Depending on your configuration, VMS DECwindows customization tasks include the following: o Controlling the startup of VMS DECwindows software as described in Section 11.1. o Customizing the server startup as described in Section 11.2. o Using VMS/ULTRIX Connection software as a DECwindows transport. o Using non-Digital transports with DECwindows. o Defining print formats as described in Section 11.6. o Compiling the optional Ada software as described in Section 11.7. ________________________ Note ________________________ This chapter covers only the XUI-based DECwindows shipped with VMS, not VMS DECwindows Motif V1.0. ______________________________________________________ 11.1 Controlling Startup of VMS DECwindows Software If you upgraded your system to VMS Version 5.5, go to Section 11.1.1. 11-1 Customizing VMS DECwindows Software 11.1 Controlling Startup of VMS DECwindows Software 11.1.1 After an Upgrade VMS DECwindows software starts automatically after SYSTARTUP_V5.COM runs, however you may need to do the following: 1. If you upgraded from V5.1, V5.1-1, or V5.1-B, you need to edit SYS$SYSROOT:[SYSMGR]:SYSTARTUP_V5.COM and delete the following line: $ @SYS$MANAGER:DECW$STARTUP 2. If you placed the DECW$STARTUP command in a file other than SYSTARTUP_V5.COM, you can either delete the command from the file it is in or add the following command to SYSTARTUP_V5.COM: $ DEFINE DECW$IGNORE_DECWINDOWS TRUE ! Delay DECwindows startup You should only add the above command to SYSTARTUP_ V5.COM if your site-specific startup is going to execute DECW$STARTUP at a later time. You should execute DECW$STARTUP on all VAX computers using any function of DECwindows software, including those computers performing only as DECwindows servers. You do not need to execute DECW$STARTUP if you have removed all classes of DECwindows software using DECW$TAILOR. 3. If you plan to use the DECwindows C example programs, make sure that VAX C is installed using the option to extract VAX C definition (.h) files. All of the DECwindows C example programs assume that the definition files were extracted; if you have already installed VAX C and you did not extract the definition files, the DECwindows C example programs do not work. For more information, see the VMS Version 5.5 Release Notes. 11.1.2 VMS DECwindows Logical Names Created At Startup After you start VMS DECwindows, a system-wide logical name table is created and is added to the default logical name table search lists. Table 11-1 lists the logical names contained in this table. 11-2 Customizing VMS DECwindows Software 11.1 Controlling Startup of VMS DECwindows Software Table_11-1_DECW$LOGICAL_NAMES______________________________ Logical_Name__________Definition___________________________ CDA$LIBRARY DDIF document style guide DECW$BOOK Online documentation DECW$EXAMPLES DECwindows example files directory DECW$INCLUDE DECwindows MIT-compatible C language include files DECW$KEYMAP DECwindows keyboard map definitions directory used by the Session Manager DECW$SYSTEM_DEFAULTS The system-wide directory where DECwindows applications will look for resource files DECW$USER_DEFAULTS The user directory where DECwindows applications will look for resource files DECW$WINMGREXE Window manager executable file used by the Session Manager DECW$XLIBERRDB Pointer to the Xlib error resource database UIL$INCLUDE Directory containing toolkit UIL files VUE$LIBRARY Directory containing FileView command files and the FileView default system profile XDPS$INCLUDE Directory containing Display Postscript programming include header files XDPS$EXAMPLES Directory containing Display ______________________Postscript_example_application_files_ 11.2 Customizing the Server Startup If you are not planning on starting the VMS DECwindows server, go to Section 11.6. ________________________ Note ________________________ By default, the DECWindows server no longer logs successful connect/disconnect messages to the 11-3 Customizing VMS DECwindows Software 11.2 Customizing the Server Startup DECW$SERVER_#_ERROR.LOG file. To enable these messages, define the symbol DECW$SERVER_CONNECT_ LOG in the DECW$PRIVATE_SERVER_SETUP.COM file to be "T" and restart the server. Note that abnormal or unsuccessful connect/disconnect messages can be logged by the server. ______________________________________________________ The startup command procedures automatically determine most of the configuration variables for the VMS DECwindows server. However, there are four items which the command procedures cannot determine: o The startup procedures assume that you have a 75 dots /inch monitor (such as a VR260 or VR290). o If you have a VAXstation 2000/GPX, a VAXstation 3xxx /GPX, or a VAXstation II/GPX, the startup procedures assume that you have a color monitor. o The startup procedures assume that you have a North American keyboard layout (you have an LK201-AA or -LA keyboard). o The startup procedures assume that the server will use only DECnet-VAX software and local transports. If any of these assumptions is incorrect, you must override them as follows: 1. Make a copy of the file SYS$MANAGER:DECW$PRIVATE_SERVER_ SETUP.TEMPLATE and rename it to a .COM file type. The comments in this file show how to customize individual workstations by adding a section of DCL commands for each workstation. You can also add DCL commands to the common section of the server startup file. By doing this, you ensure that the customizations you make affect all workstations that use the server startup file. 2. If your screen supports 100 dots/inch, add the following line: $ DECW$SERVER_DENSITY == 100 Add this line to the section for each workstation that has a 100 dots/inch monitor, or add it to the common section for all workstations (if all the workstations have 100 dots/inch monitors). 11-4 Customizing VMS DECwindows Software 11.2 Customizing the Server Startup 3. The section for any monochrome /GPX workstation should contain the following line: $ DECW$COLOR == "FALSE" 4. To override the default keyboard layout, determine the correct name from the model number of your LK201 keyboard, as follows: a. Turn the keyboard upside down, and look for a label which specifies the model number. The model number should be in a format similar to LK201-xx. The model number may also be listed as simply LK201. In this case, the information you need is in another part of the label where there will be a number that has the following format: nn-nnnnn-xx. b. Use the xx part of this number to choose a keymap name from Table 11-2. The table is arranged based on the dialect that each keyboard is designed for. Choose the keymap ending in _DP for the data processing keyboard layout, or the keymap ending in _TW for the typewriter layout. Table_11-2_DECwindows_Keymap_____________________________________ Dialect________Model_______________DECwindows_Keymap_Name________ Austrian LK201- AUSTRIAN_GERMAN_LK201LG_DP /German (AG,LG,BG,MG) AUSTRIAN_GERMAN_LK201LG_TW LK201-(NG,PG) AUSTRIAN_GERMAN_LK201NG_DP AUSTRIAN_GERMAN_LK201NG_TW LK401-(AG) AUSTRIAN_GERMAN_LK401AG_TW Belgian LK201- BELGIAN_FRENCH_LK201LP_DP /French (AP,LP,BP,MP) BELGIAN_FRENCH_LK201LP_TW Belgian LK401-(AP) BELGIAN_FRENCH_LK401AP_DP /French (continued on next page) 11-5 Customizing VMS DECwindows Software 11.2 Customizing the Server Startup Table_11-2_(Cont.)_DECwindows_Keymap_____________________________ Dialect________Model_______________DECwindows_Keymap_Name________ BELGIAN_FRENCH_LK401AP_TW British LK201- BRITISH_LK201LE_DP (AE,LE,BE,ME) BRITISH_LK201LE_TW British LK401-(AA,PA) BRITISH_LK401AA_DP BRITISH_LK401AA_TW Canadian LK201- CANADIAN_FRENCH_LK201LC_DP /French (AC,LC,BC,MC) CANADIAN_FRENCH_LK201LC_TW Canadian LK401- CANADIAN_FRENCH_LK401AC_DP /French (AC,LC,BC,MC) CANADIAN_FRENCH_LK401AC_TW Danish LK201- DANISH_LK201LD_DP (AD,LD,BD,MD) DANISH_LK201LD_TW LK201-(ED,RD,FD) DANISH_LK201RD_DP DANISH_LK201RD_TW Danish LK401- DANISH_LK401AD_DP (AD,LD,BD,MD) DANISH_LK401AD_TW Dutch LK201- DUTCH_LK201LH_DP (AH,LH,BH,MH) DUTCH_LK201LH_TW LK201-(NH,PH) DUTCH_LK201NH LK401-(NH,PH) DUTCH_LK401AH Finnish LK201- FINNISH_LK201LF_DP (AF,LF,BF,MF) FINNISH_LK201LF_TW LK201-(NX,PX) FINNISH_LK201NX_DP FINNISH_LK201NX_TW (continued on next page) 11-6 Customizing VMS DECwindows Software 11.2 Customizing the Server Startup Table_11-2_(Cont.)_DECwindows_Keymap_____________________________ Dialect________Model_______________DECwindows_Keymap_Name________ Finnish LK401- FINNISH_LK401AF_DP (AF,LF,BF,MF) FINNISH_LK401AF_TW Flemish LK201- FLEMISH_LK201LB_DP (AB,LB,BB,MB) FLEMISH_LK201LB_TW Flemish LK401- FLEMISH_LK401AB_DP (AB,LB,BB,MB) FLEMISH_LK401AB_TW Icelandic LK201- ICELANDIC_LK201LU_DP (AU,LU,BU,MU) ICELANDIC_LK201LU_TW Italian LK201- ITALIAN_LK201LI_DP (AI,LI,BI,MI) ITALIAN_LK201LI_TW Italian LK401- ITALIAN_LK401AI_DP (AI,LI,BI,MI) ITALIAN_LK401AI_TW North LK201- NORTH_AMERICAN_LK201LA American (AA,LA,BA,MA) North LK401- NORTH_AMERICAN_LK401AA American (AA,LA,BA,MA) Norwegian LK201- NORWEGIAN_LK201LN_DP (AN,LN,BN,MN) NORWEGIAN_LK201LN_TW LK201-(EN,RN,FN) NORWEGIAN_LK201RN_DP NORWEGIAN_LK201RN_TW Norwegian LK401- NORWEGIAN_LK401AN_DP (AN,LN,BN,MN) NORWEGIAN_LK401AN_TW (continued on next page) 11-7 Customizing VMS DECwindows Software 11.2 Customizing the Server Startup Table_11-2_(Cont.)_DECwindows_Keymap_____________________________ Dialect________Model_______________DECwindows_Keymap_Name________ Portuguese LK201- PORTUGUESE_LK201LV (AV,LV,BV,MV) Portuguese LK401- PORTUGUESE_LK401AV (AV,LV,BV,MV) Spanish LK201- SPANISH_LK201LS_DP (AS,LS,BS,MS) SPANISH_LK201LS_TW Spanish LK401- SPANISH_LK401AS_DP (AS,LS,BS,MS) SPANISH_LK401AS_TW Swedish LK201- SWEDISH_LK201LM_DP (AM,LM,BM,MM) SWEDISH_LK201LM_TW LK201-(NM,PM) SWEDISH_LK201NM_DP SWEDISH_LK201NM_TW Swedish LK401- SWEDISH_LK401AM_DP (AM,LM,BM,MM) SWEDISH_LK401AM_TW Swiss/French LK201- SWISS_FRENCH_LK201LK_DP (AK,LK,BK,MK) SWISS_FRENCH_LK201LK_TW Swiss/French LK401- SWISS_FRENCH_LK401AK_DP (AK,LK,BK,MK) SWISS_FRENCH_LK401AK_TW Swiss/German LK201- SWISS_GERMAN_LK201LL_DP (AL,LL,BL,ML) SWISS_GERMAN_LK201LL_TW Swiss/German LK401- SWISS_GERMAN_LK401AL_DP (AL,LL,BL,ML) SWISS_GERMAN_LK401AL_TW (continued on next page) 11-8 Customizing VMS DECwindows Software 11.2 Customizing the Server Startup Table_11-2_(Cont.)_DECwindows_Keymap_____________________________ Dialect________Model_______________DECwindows_Keymap_Name________ Combined US LK201-(EE,RE,PE) UK_LK201RE /UK US_LK201RE Combined US LK401-(EE,RE,PE) UK_LK401AA /UK ___________________________________US_LK401AA____________________ c. After you choose a keymap name, modify the server startup file. For example, to change the keyboard layout to a Dutch typewriter layout, add the following line to the server startup file: $ DECW$DEFAULT_KEYBOARD_MAP == "DUTCH_LK201LH_TW" Add a line similar to this for each workstation that does not have a North American keyboard layout, or add it to the common section for all workstations (if all the workstations use the same keyboard layout). 5. To add support for the Transmission Control Protocol /Internet Protocol (TCP/IP) transport using the VMS /ULTRIX Connection product (UCX), add the following line: $ DECW$SERVER_TRANSPORTS == "DECNET,LOCAL,TCPIP" Add this line to the section for each workstation that will be using TCP/IP, or add it to the common section for all workstations. To include support for other transports, add the last part of the transport image name to the list of transports. For example, suppose you want to add support for a customer-written transport that has the following image name: SYS$SHARE:DECW_TRANSPORT_FOO You would add the following line: $ DECW$SERVER_TRANSPORTS == "DECNET,LOCAL,FOO" 6. Reboot the workstations for which you customized the server startup. 11-9 Customizing VMS DECwindows Software 11.2 Customizing the Server Startup 7. Customize security as described in the VMS DECwindows User's Guide. 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. 11.3 Using TCP/IP with DECwindows DECwindows contains support for the TCP/IP transport. This support depends on the VMS/ULTRIX Connection software (UCX), which is a Digital layered product. Before you can use DECwindows TCP/IP transport interface, you must install UCX. For more information about TCP/IP concepts, see the VMS/ULTRIX Connection System Manager's Guide. ________________________ Note ________________________ Other vendors' implementation of TCP/IP transports use different call interfaces. For this reason, DECwindows support for TCP/IP is compatible only with UCX. ______________________________________________________ You can conserve memory and process slots by configuring UCX software for the minimum DECwindows requirement to support the X protocol. DECwindows only requires that INET_ ACP be running. DECwindows does not require that the NFS server, the FTPD server, or the remote terminal servers be running. For information on how to configure the UCX software, see the VMS/ULTRIX Connection Installation Guide. 11.4 Using Non-Digital Transports with DECwindows DECwindows supports DECnet-VAX, local, and TCP/IP transports. However, you can use other transports with DECwindows by writing a DECwindows transport interface layer. Digital will likely supply new transports for various layered products, and third-party vendors can also supply new transports, such as other TCP/IP transports. For information on writing a transport interface, see the VMS DECwindows Transport Manual. The transport interface image's filename must have the following format where name is the unique transport name: 11-10 Customizing VMS DECwindows Software 11.4 Using Non-Digital Transports with DECwindows DECW$TRANSPORT_name (for transports supplied by Digital) DECW_TRANSPORT_name (for customer-written transports) Install the image as a protected image in the SYS$SHARE directory (as defined by an executive mode logical name). Digital recommends that you install the image by adding the following line to SYS$MANAGER:SYSTARTUP_V5.COM: $ INSTALL CREATE SYS$SHARE:DECW_TRANSPORT_name/OPEN/SHARED/HEADER_RESIDENT/PROTECTED You can also include this command in a startup file that SYSTARTUP_V5 calls. To use this transport with the DECwindows server, customize the server startup as described in Section 11.2. 11.5 Using the Example Transport DECwindows has an example transport interface based upon the UCX software. It is similar to the DECwindows TCP/IP transport interface, except it includes its own source files and it uses a different port number (5000). You can run the example transport interface simultaneously with the TCP/IP transport interface. If you have installed UCX software, you can install and use the example transport by doing the following: 1. Copy the example transport to the SYS$SHARE directory as follows: $ COPY DECW$EXAMPLES:DECW$TRANSPORT_EXAMPLE.EXE SYS$SHARE:/PROT=W:RE 2. Add the following line to SYS$MANAGER:SYSTARTUP_V5.COM: $ INSTALL CREATE SYS$SHARE:DECW$TRANSPORT_EXAMPLE /OPEN /SHARED/ HEADER_RESIDENT /PROTECTED 3. Customize the private server startup as described in Section 11.2 for TCP/IP, except use the transport name "EXAMPLE". For example, you could add the following line: $ DECW$SERVER_TRANSPORTS == "DECNET,LOCAL,TCPIP,EXAMPLE" 4. Reboot the workstation. 5. Customize security as described in the VMS DECwindows User's Guide for TCP/IP, but use the transport name "EXAMPLE" instead of "TCPIP". 11-11 Customizing VMS DECwindows Software 11.5 Using the Example Transport 6. Create a DECterm window on the workstation and enter the following command: $ SET DISPLAY /CREATE /NODE=your_node /TRANSPORT=EXAMPLE Substitute the node name of your workstation for your_ node. 7. Run any DECwindows application from the DECterm window. It will now use the example transport to display graphics on your workstation screen. For example, you would enter the following command to run the clock: $ RUN SYS$SYSTEM:DECW$CLOCK 11.6 Defining Print Formats If you do not want to define print formats on your system, go to Section 11.7. The print dialog box is used in many applications for the queuing of files or screens to a printer. (See the VMS DECwindows User's Guide for more information about the print dialog box.) By default, all printing devices on the system are displayed in the "Printers" listbox. However, you can take advantage of a feature where print queues can be associated with print formats through the definition of logical names. The logical name is defined to be a comma-separated or space- separated list of print queues with the first queue being the default choice. For example, if DECW$PRINTER_FORMAT_ANSI2 is defined to be "MY_PRINTER, CLUSTER_LN03, ANOTHER_LN03", when you select "ANSI2" from the print format listbox, only MY_PRINTER, CLUSTER_LN03, and ANOTHER_LN03 will be shown in the printer listbox, with MY_PRINTER being the default choice. Table 11-3 lists the logical names and the print formats associated with each. Table_11-3_Print_Dialog_Box_Logical_Names__________________ Logical_name_________________Print_format__________________ DECW$PRINTER_FORMAT_PS PostScript (continued on next page) 11-12 Customizing VMS DECwindows Software 11.6 Defining Print Formats Table_11-3_(Cont.)_Print_Dialog_Box_Logical_Names__________ Logical_name_________________Print_format__________________ DECW$PRINTER_FORMAT_TEXT Text DECW$PRINTER_FORMAT_LINE Line Printer DECW$PRINTER_FORMAT_TERM Terminal DECW$PRINTER_FORMAT_ANSI2 ANSI2 DECW$PRINTER_FORMAT_ANSI ANSI DECW$PRINTER_FORMAT_REGIS ReGIS DECW$PRINTER_FORMAT_TEK Tektronix DECW$PRINTER_FORMAT_DDIF_____DDIF__________________________ The logical names can be defined by system managers in the appropriate logical name tables and can be overridden by users. If you have defined any of the logical names in Table 11-3, they will serve as the list of printer queue names to be presented when the corresponding print format is selected. This method is much faster than making the print dialog box derive the names of all the queues on the system, most of which are inappropriate for the print format under consideration, as the following example shows: $ DEFINE DECW$PRINTER_FORMAT_TEXT "CLUSTER_LN03,CLUSTER_PRINT, - _$ ANSI_ARTWRK,ANSI_PROTON" $ DEFINE DECW$PRINTER_FORMAT_LINE "CLUSTER_PRINT" $ DEFINE DECW$PRINTER_FORMAT_ANSI2 "CLUSTER_LN03,ANSI_ARTWRK,ANSI_PROTON" $ DEFINE DECW$PRINTER_FORMAT_ANSI "CLUSTER_LN03,ANSI_ARTWRK,ANSI_PROTON" $ DEFINE DECW$PRINTER_FORMAT_REGIS "SYS$NULL" 11.7 Compiling Ada Source Files If you have not installed Ada programming software on your system, skip this section. VMS DECwindows provides programming interface definitions for the Ada language. When you select Ada support at the time of the VMS DECwindows kit installation, five Ada package source files are placed in the SYS$LIBRARY: directory of your system. These files are: o CDA$CDA_.ADA-Package CDA-Compound Document Architecture 11-13 Customizing VMS DECwindows Software 11.7 Compiling Ada Source Files o DDIF$DDIF_.ADA-Package DDIF-Digital Document Interchange Format o DTIF$DTIF_.ADA-Package DTIF-Digital Table Interchange Format o DECW$DWT_.ADA-Package DWT-DECwindows Toolkit o DECW$X_.ADA-Package X-Xlib If VMS DECwindows Motif is installed, the Motif-Ada package, DECW$MOTIF_.ADA is also included. These package source files can be individually compiled into your Ada program libraries or compiled into the systemwide Ada predefined library. To make the packages available systemwide, the command procedure SYS$UPDATE:DECW$COMPILE_ADA_UNITS.COM is provided. This command procedure compiles all the packages into the predefined Ada library, and, if the VAX Source Code Analyzer (SCA) product is present, loads SCA analysis data for the packages into the SCA library for the predefined library. The command procedure should be run as a batch job and should have available a minimum of 2000 pages in the working set; however, 3000 pages is preferable. A page file quota of at least 30000 pages is suggested. Once the units are compiled into the predefined Ada library, you must execute the following Ada program library manager command to make the units visible: $ ACS ENTER UNIT ADA$PREDEFINED CDA,DDIF,DTIF,DWT,X You need to do this only once. This step is also performed automatically for all Ada program libraries created after the VMS DECwindows units are compiled into the predefined library. Future installations of VMS DECwindows might replace the Ada packages. If so, the new packages must be compiled as shown. If you want to keep the old package units in your library, you must then execute the following command to make your library current: $ ACS REENTER * 11-14 Customizing VMS DECwindows Software 11.7 Compiling Ada Source Files Future installations of VAX Ada might replace the Ada predefined library and remove the VMS DECwindows units. If this occurs, execute the DECW$COMPILE_ADA_UNITS.COM command procedure again. 11-15 12 _________________________________________________________________ Using VMSTAILOR and DECW$TAILOR Read this chapter if you want to add or remove optional VMS software or VMS DECwindows software from your system disk. To add or remove optional VMS files, use VMSTAILOR. To add or remove DECwindows software, use DECW$TAILOR. You will need your VMS Version 5.5 software media kit to tailor on VMS and DECwindows. Any site-specific customization that has been done to a class will be lost when that class is tailored off. 12.1 Using VMSTAILOR To add or remove unwanted VMS files from the system disk, use VMSTAILOR. For example, if you are not running DECnet- VAX, and you do not need the network support files, you can remove those files using VMSTAILOR. If you later decide you want to run DECnet-VAX, you can add the necessary files at any time using VMSTAILOR and your VMS Version 5.5 distribution media. VMSTAILOR has three phases: 1. VMSTAILOR asks if you want to tailor your system by adding files (tailor on) or by deleting files (tailor off). 2. If you choose to tailor files on, VMSTAILOR lists each class of VMS files and asks if you want to include them on the system disk. If you choose to tailor files off, VMSTAILOR lists each class of files and asks if you want to delete them from the system disk. 3. VMSTAILOR adds or deletes the files you indicated from the system disk. If you are tailoring files on, you must load your VMS Version 5.5 distribution media in a drive available to the system. If your distribution media consists of more than one piece, put the first piece of the media into the drive. 12-1 Using VMSTAILOR and DECW$TAILOR 12.1 Using VMSTAILOR The following is a list of classes and subclasses of VMS files that can be added or deleted by using VMSTAILOR. For a complete list of VMS files and their functions, see the Guide to Setting Up a VMS System. o Network Support Incoming Remote File Access files Incoming Remote Terminal files Network Test files Remote Task Loading o Programming Support Debugger utility (DEBUG) Image Dump utility (ANALYZE/PROCESS_DUMP) RMS Analyze and FDL Editor utilities (ANALYZE/RMS, ANALYZE/FDL) Message utility (MESSAGE) Object and Shareable Image libraries Macro libraries Macro assembler SDL intermediary form of STARLET.MLB FORTRAN require files VAX-C object libraries o RMS Journaling Files o System Programming Support Files-11 ODS1 ACP Monitor utility Analyze Object File utility (ANALYZE/IMAGE, ANALYZE /OBJECT) Delta debugger System Dump Analyzer utility (ANALYZE/SYSTEM, ANALYZE /CRASH) System Symbol Table file (SYS.STB) Miscellaneous Symbol Table files o Secure User's Environment File Access Control List utilities Print and Batch Queue utilities Input Queue Symbiont (Card Reader) Accounting Log Report Generator utility DECdtm 12-2 Using VMSTAILOR and DECW$TAILOR 12.1 Using VMSTAILOR o Utilities MAIL utility DUMP utility RUNOFF utility PHONE utility VMS HELP library VMS System Messages Help Library Foreign Terminal Support LAT-11 terminal server (via Ethernet) Standalone BACKUP Error Log Report Generator utility (ANALYZE/ERROR) VAXTPU utility Terminal Fallback Facility TECO editor EDT documentation National Character Set utility (NCS) o VMS Workstation Support Workstation device support o BLISS Require Files o Miscellaneous Files System map LPA-11 support o User Environment Test Package o Example Files 12.1.1 Removing VMS Files To remove unwanted files using VMSTAILOR, perform the following steps: 1. Log in to the SYSTEM account. 2. Enter the following command and press the Return key: $ RUN SYS$UPDATE:VMSTAILOR VMSTAILOR displays a description of the VMSTAILOR program and displays the following message: Do you want to tailor files "ON" or "OFF"? 3. Enter OFF to remove unwanted files and press the Return key. 12-3 Using VMSTAILOR and DECW$TAILOR 12.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. A file class is made up of many smaller groups called subclasses. You can eliminate an entire class of files, or you can eliminate one or more of its subclasses. For example: CLASS - Network support Size of entire class (with subclasses): 1499 Size of common files required for any subclass: 1249 Do you wish to select the entire class (default = NO)? . . . 4. Decide which file classes or subclasses you do not need to support your system. The VMSTAILOR program displays step-by-step instructions. Follow these instructions to specify which classes or subclasses of files you want to remove. 5. VMSTAILOR deletes the files you selected and displays the names of those files. After it finishes, AUTOGEN runs automatically to make the adjustments that are necessary after system files are deleted. AUTOGEN also reboots the system. _______________________ Caution _______________________ To cancel VMSTAILOR during the first and second phases, press Ctrl/C, Ctrl/Y, or Ctrl/Z. Canceling VMSTAILOR during the third phase may cause a partially tailored disk. For a description of each phase, see Section 12.1. ______________________________________________________ 12-4 Using VMSTAILOR and DECW$TAILOR 12.1 Using VMSTAILOR 12.1.2 Adding VMS Files To add optional VMS files that you previously removed, or that you chose not to install during the VMS installation procedure, do the following: 1. Log in to the SYSTEM account. 2. Load your distribution media in a drive available to the system. For example, if your distribution media is on a TK50 tape cartridge, load the tape cartridge labeled VMS V5.5 BIN TK50 1/2 VMS BINARY in a TK50 drive available to the system. Make sure the drive is online and ready. If you are adding files from a compact disc on an InfoServer, first determine whether the SYSGEN parameter SCSNODE is defined on your system (see Section 6.5) or start the DECnet software, and then refer to step 2 of Section 8.3. 3. Enter the following command and press the Return key: $ RUN SYS$UPDATE:VMSTAILOR VMSTAILOR displays a description of the VMSTAILOR program and displays the following message: Do you want to tailor files "ON" or "OFF"? 4. Enter ON to add files and press the Return key. The VMSTAILOR program lists each group, or class, of files and its size in blocks. Files are grouped according to their function. For example, all the files required for network support are in one class. A file class is made up of many smaller groups called subclasses. You can add an entire class of files, or you can add one or more of its subclasses. For example: CLASS - Network support Size of entire class (with subclasses): 1499 Size of common files required for any subclass: 1249 Do you wish to select the entire class (default = NO)? . . . 12-5 Using VMSTAILOR and DECW$TAILOR 12.1 Using VMSTAILOR 5. Decide which file classes or subclasses you need to add. VMSTAILOR displays step-by-step instructions. Follow these instructions to specify which classes or subclasses of files you want to add. 6. VMSTAILOR adds the files you specified and displays the names of the files. After the files have been added, AUTOGEN runs automatically to make the adjustments that are necessary after system files are deleted. AUTOGEN also reboots the system. _______________________ Caution _______________________ To cancel VMSTAILOR during the first and second phases, press Ctrl/C, Ctrl/Y, or Ctrl/Z. Canceling VMSTAILOR during the third phase may cause a partially tailored disk. For a description of each phase, see Section 12.1. ______________________________________________________ After adding files to the system disk, apply any updates that affect them. For example, suppose you do not need the VMS Version 5.5 PHONE Utility and you run VMSTAILOR to remove those files. Later, if you decide you want to use PHONE, run VMSTAILOR to return the PHONE files to the system disk. Then apply any VMS update that has occurred since Version 5.5 that affected the PHONE utility. VMS update procedures create a .TXT file that contains a description of patched files. This file usually has the following format: SYS$UPDATE:VMSUn05n.TXT[1]. Example 12-1 illustrates how to add all Network Support files, and selected Programming Support files to a system disk. Example 12-1 Sample VMSTAILOR Session (continued on next page) ____________________ [1] Examine this file to determine if the update patched the PHONE utility 12-6 Using VMSTAILOR and DECW$TAILOR 12.1 Using VMSTAILOR Example 12-1 (Cont.) Sample VMSTAILOR Session $ RUN SYS$UPDATE:VMSTAILOR . . . Do you want to tailor files "ON" or "OFF"? ON TAILOR-ON --------- You will now be prompted with a list of the classes and subclasses of VMS files that are optional. The size of each class and subclass is included in the list. This will help you decide whether or not you want to add a class or subclass to your system. Under some classes, there is a set of common files that is required in order for any subclasses to work. These files are added when you ask for either the entire class or any of its subclasses. Total size of the system disk is 2376153 blocks. Total space used on the system disk is 2241252 blocks. Total space left on the system disk is 134901 blocks. CLASS - Network support Size of entire class (with subclasses): 1499 Size of common files required for any subclass: 1249 Do you wish to select the entire class (default = NO)? YES (continued on next page) 12-7 Using VMSTAILOR and DECW$TAILOR 12.1 Using VMSTAILOR Example 12-1 (Cont.) Sample VMSTAILOR Session CLASS - Programming Support Size of entire class (with subclasses): 14706 Size of common files required for any subclass: 0 Do you wish to select the entire class (default = NO)? Do you wish to select any of its subclasses (default = NO)? )YES Select the subclasses that you wish to provide: SUBCLASS - Debugger utility (DEBUG) (4690 blocks) [NO]: YES SUBCLASS - Image Dump utility (ANALYZE/PROCESS_DUMP) (48 block s) [NO]: YES SUBCLASS - RMS Analyze and FDL Editor utilities (ANALYZE/RMS, ANALYZE/FDL)(374 blocks) [NO]:YES SUBCLASS - Message utility (MESSAGE) (49 blocks) [NO]: SUBCLASS - Object and Shareable Image libraries (4311 blocks) [NO]: YES SUBCLASS - Macro libraries (2293 blocks) [NO]: SUBCLASS - Macro assembler (457 blocks) [NO]: SUBCLASS - SDL intermediary form of STARLET.MLB (1957 blocks) [NO]: SUBCLASS - FORTRAN require files (51 blocks) [NO]: SUBCLASS - VAX-C object libraries (471 blocks) [NO]: CLASS - RMS journaling files Size of entire class (with subclasses): 155 No subclasses in this tailor class. Do you wish to select the entire class (default = NO)? CLASS - System programming Support Size of entire class (with subclasses): 2286 Size of common files required for any subclass: 93 Do you wish to select the entire class (default = NO)? Do you wish to select any of its subclasses (default = NO)? ) 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)? . . . (continued on next page) 12-8 Using VMSTAILOR and DECW$TAILOR 12.1 Using VMSTAILOR Example 12-1 (Cont.) Sample VMSTAILOR Session Files have been selected Do you wish to add all of the options selected? YES Creating temporary command file, please wait... * Enter device containing VMS distribution media: mua0: . . . 12.2 Using DECW$TAILOR Use DECW$TAILOR to add or remove some or all DECwindows files from the system disk. For example, if you are not planning on using the DECwindows programming support, you can remove those files. Later, if you decide you want DECwindows programming support, you can add the files to the system disk using DECW$TAILOR and your VMS DECwindows distribution media. If you have installed VMS DECwindows Motif, refer to the VMS DECwindows Motif Installation Guide. DECW$TAILOR will only tailor on or off those DECwindows files, with the exception of the required files, supplied in the VMS kit. DECW$TAILOR has three phases: 1. DECW$TAILOR asks if you want to tailor your system by adding files (tailor on) or by deleting files (tailor off). 2. If you choose to tailor files on, DECW$TAILOR lists each class of DECwindows files and asks if you want to include them on the system disk. If you choose to tailor files off, DECW$TAILOR lists each class of DECwindows files and asks if you want to delete them from the system disk. 3. DECW$TAILOR adds or deletes the files you indicated from the system disk. If you are tailoring files on, you must load your VMS DECwindows distribution media in a drive available to the system. For example, if your VMS DECwindows distribution kit is on a TK50 tape cartridge, load the tape cartridge labeled "VMS V5.5 BIN TK50 2/2 12-9 Using VMSTAILOR and DECW$TAILOR 12.2 Using DECW$TAILOR S/A BKUP - DECWINDOWS" into a TK50 drive available to the system. The following is a list of classes and subclasses of VMS DECwindows files that you can add or delete using DECW$TAILOR. For a list of DECwindows files and their functions, see the current version of the VMS Upgrade and Installation Manual. o DECwindows Applications Files o DECwindows Device Support Files[1] PEX for PHIGS support files o 75 dots/inch Video Font Files o 100 dots/inch Video Font Files o DECwindows Programming Support Files Ada files BASIC files BLISS files VAXC (MIT binding) files VAXC (VAX binding) files FORTRAN files Macro files Pascal files PL/1 files o Example Files 12.2.1 Removing DECwindows Files To remove DECwindows files from the system disk, do the following: 1. Log in to the SYSTEM account. 2. Type the following command, and press RETURN: $ RUN SYS$UPDATE:DECW$TAILOR DECW$TAILOR displays information about the DECW$TAILOR program and displays the following message: Do you want to tailor files "ON" or "OFF"? ____________________ [1] If you tailor device support files ON or OFF, the system reboots. 12-10 Using VMSTAILOR and DECW$TAILOR 12.2 Using DECW$TAILOR 3. Type OFF to remove unwanted files, and press RETURN. The DECW$TAILOR program lists each group, or class, of files and its size in blocks. Files are grouped according to their function. For example, all the files required for VMS DECwindows device support are in one class. A file class is made up of many small subclasses. You can eliminate an entire class of files, or you can eliminate one or more of its subclasses. For example: CLASS - DECwindows device support files Size of entire class (with subclasses): 7868 Size of common files required for any subclass: 5847 Do you wish to select the entire class (default = NO)? . . . 4. Decide which file classes or subclasses you do not need to support your system. DECW$TAILOR displays step-by- step instructions. Follow these instructions to specify which of the classes or subclasses you want to remove. 5. DECW$TAILOR deletes the files you selected and displays the names of those files. If you deleted device support files, the system automatically shuts down and reboots. _______________________ Caution _______________________ To cancel DECW$TAILOR during the first and second phases, press Ctrl/C, Ctrl/Y, or Ctrl/Z. Canceling DECW$TAILOR during the third phase may cause a partially tailored disk. For a description of each phase, see Section 12.2. ______________________________________________________ 12.2.2 Adding DECwindows Files To install DECwindows after the VMS installation, or 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. 12-11 Using VMSTAILOR and DECW$TAILOR 12.2 Using DECW$TAILOR 2. Load the distribution media containing the VMS DECwindows save sets in a drive available to your system. For example, if your distribution media is a TK50 tape cartridge, load the tape cartridge labeled VMS V5.5 BIN TK50 2/2 DECwindows & S/A BKUP in a TK50 drive available to the system. Make sure the drive is online and ready. If you are adding files from a compact disc on an InfoServer, first determine whether the SYSGEN parameter SCSNODE is defined on your system (see Section 6.5) or start the DECnet software, and then refer to step 2 of Section 8.3. 3. Enter the following command, and press RETURN: $ RUN SYS$UPDATE:DECW$TAILOR DECW$TAILOR displays information about the DECW$TAILOR program, and displays the following message: Do you want to tailor files "ON" or "OFF"? 4. Type ON to add files, and press RETURN. The DECW$TAILOR program lists each group, or class, of files and its size in blocks. Files are grouped according to their function. For example, all the files required for VMS DECwindows device support are in one class. A file class is made up of many small subclasses. You can add an entire class of files, or you can add one or more of its subclasses. For example: CLASS - DECwindows device support files Size of entire class (with subclasses): 7868 Size of common files required for any subclasses: 5847 Do you wish to select the entire class (default = NO)? . . . 5. Decide which file classes or subclasses you do not need to support your system. The DECW$TAILOR program displays step-by-step instructions. Follow these instructions to specify which of the classes or subclasses you want to add. 12-12 Using VMSTAILOR and DECW$TAILOR 12.2 Using DECW$TAILOR 6. DECW$TAILOR installs the files you selected and displays the names of those files. If you added device support files, the system automatically shuts down and reboots. _______________________ Caution _______________________ To cancel DECW$TAILOR during the first and second phases, press Ctrl/C, Ctrl/Y, or Ctrl/Z. Canceling DECW$TAILOR during the third phase may cause a partially tailored disk. For a description of each phase, see Section 12.2. ______________________________________________________ After adding files to the system disk, apply any updates that affect them. For example, suppose you delete the Version 5.5 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 VMS update that has occurred since Version 5.5 that affected the 100 dots/inch video font files. VMS update procedures create a .TXT file that contains a description of modified files. This file is usually named with the following format: SYS$UPDATE:VMSUn05n.TXT[1]. Example 12-2 illustrates how to add the files for DECwindows applications, and the DECwindows programming support files for Ada and BLISS to a system disk. Example 12-2 Sample DECW$TAILOR Session $ RUN SYS$UPDATE:DECW$TAILOR . . . Do you want to tailor files "ON" or "OFF"? ON (continued on next page) ____________________ [1] Examine this file to determine if the update patched the 100 dots/inch font files 12-13 Using VMSTAILOR and DECW$TAILOR 12.2 Using DECW$TAILOR Example 12-2 (Cont.) Sample DECW$TAILOR Session TAILOR-ON --------- You will now be prompted with a list of the classes and subclasses of DECwindows files that are optional. The size of each class and subclass is included in the list. This will help you decide whether or not you want to add a class or subclass to your system. Under some classes, there is a set of common files that is required in order for any subclasses to work. These files are added when you ask for either the entire class or any of its subclasses. Total size of the system disk is 2376153 blocks. Total space used on the system disk is 1728072 blocks. Total space left on the system disk is 648081 blocks. CLASS - DECwindows applications files Size of entire class (with subclasses): 11545 No subclasses in this tailor class. Do you wish to select the entire class (default = NO)? YES CLASS - DECwindows device support files Size of entire class (with subclasses): 7868 Size of common files required for any subclass: 5847 Do you wish to select the entire class (default = NO)? NO Do you wish to select any of its subclasses (default = NO)? CLASS - 75 dots per inch video font files Size of entire class (with subclasses): 2249 No subclasses in this tailor class. Do you wish to select the entire class (default = NO)? CLASS - 100 dots per inch video font files Size of entire class (with subclasses): 2788 No subclasses in this tailor class. Do you wish to select the entire class (default = NO)? (continued on next page) 12-14 Using VMSTAILOR and DECW$TAILOR 12.2 Using DECW$TAILOR Example 12-2 (Cont.) Sample DECW$TAILOR Session CLASS - DECwindows programming support files Size of entire class (with subclasses): 26206 Size of common files required for any subclass: 924 Do you wish to select the entire class (default = NO)? Do you wish to select any of its subclasses (default = NO)? YES Select the subclasses that you wish to use: SUBCLASS - Ada files (3365 blocks) [NO]: YES SUBCLASS - BASIC files (2694 blocks) [NO]: SUBCLASS - BLISS files (2083 blocks) [NO]: YES SUBCLASS - VAX C (MIT binding) files (1302 blocks) [NO]: SUBCLASS - VAX C (VAX binding) files (2945 blocks) [NO]: SUBCLASS - FORTRAN files (2034 blocks) [NO]: SUBCLASS - Macro files (3641 blocks) [NO]: SUBCLASS - Pascal files (4662 blocks) [NO]: SUBCLASS - PL/1 files (2556 blocks) [NO]: Files have been selected Do you wish to add all of the options selected? YES Creating temporary command file, please wait... * Enter device containing DECwindows distribution media: MUA0: . . . 12-15 A _________________________________________________________________ License Management Notes This appendix contains supplemental information to the license instructions of the installation/upgrade procedures and VMS License Management Utility Manual. Although most of the information in this appendix pertains to managing VMS and System Integrated Product (SIP) licenses, some of the information pertains to managing layered product licenses. A.1 Registering Your Licenses This section provides an overview of the license registration procedure. After you install the VMS operating system, you must register a VMS license. A VMS license lets you use the VMS operating system. You must also register the licenses for any of the following SIPs you have purchased: o VAXclusters o DECnet-VAX o VAX RMS Journaling o VMS Volume Shadowing After you upgrade the VMS operating system, there is no need to reregister licenses for the VMS operating system or for System Integrated Products. In addition to the VMS operating system and the SIPs, many layered products that run on VMS Version 5.5 also require license registration. See the VMS License Management Utility Manual for a full explanation of license registration. A-1 License Management Notes A.1 Registering Your Licenses To register a license, you need to obtain a Product Authorization Key (PAK). A typical PAK is a piece of paper provided by Digital Equipment Corporation that contains the appropriate information to authorize access to software on a VAX computer or in a VAXcluster environment. You can obtain a PAK from a Digital representative in much the same way as you obtain software. See Table A-1 for a complete list of the versions of the VMS operating system and the VAX computers that were first supported by these versions. Table_A-1_The_First_VMS_Version_That_Supports_VAX_Computers VMS_Version__First_Computer_Support________________________ Version 5.0 VAX 6000 Model 2xx, VAX 8820-8840 Version Micro/VAX 3300/3400 5.0-2A Version 5.1 VAX 6000 Model 3xx, Micro/VAX 3800/3900 Version VAXstation 3100, Model 30/40 5.1-B Version VAXstation 3520/3540 5.1-1 Version 5.2 VAX 6000 Model 4xx, Micro/VAX 3100 Version VAXstation 3100, Model 38/48 5.2-1 Version 5.3 No CPUs introduced (continued on next page) A-2 License Management Notes A.1 Registering Your Licenses Table A-1 (Cont.) The First VMS Version That Supports __________________VAX_Computers____________________________ VMS_Version__First_Computer_Support________________________ Version No CPUs introduced 5.3-1 Version VAX 4000 5.3-2 Version 5.4 VAXstation 3100 Model 76, VAX 9000, VAX 6000 Model 5xx, VAXft 310 Version No CPUs introduced 5.4-1 Version VAX 4000 Model 200 5.4-2 Version VAXft Models 410, 610, 612 5.4-3 Version 5.5 VAXstation 4000 VLC, Micro/VAX 3100 Models 30, 40, and 80, VAX 6000 Model 600, VAX 4000 Model 500, VAXstation 4000 Model 60, and VAXft Model _____________110___________________________________________ A.2 Using the License Unit Requirement Table (LURT) Many PAKs contain a table name in the availability or activity fields. This name refers to a column in the License Unit Requirement Table (LURT), which is shown in Table A-2. The six lettered columns (A through F) in the LURT indicate the number of license units required for each processor listed in the System Marketing Model column. For example, if your PAK specifies availability = F, you would require 100 license units to load the license on a VAX 11 /780 computer, or 4,800 license units to load the license on a VAX 9000-430 computer. Note that some PAKs specify MOD_UNITS in the options field. The MOD_UNITS option allows the system manager to use the DCL command LICENSE MODIFY/UNITS to temporarily increase the size of the PAK. This permits a product to be used, in certain emergency situations, on a processor larger than the processor size specified in the license. Check your license terms and conditions before modifying license A-3 License Management Notes A.2 Using the License Unit Requirement Table (LURT) units. Reset the PAK size to its original size after the emergency situation is resolved. For more information on using the LURT, see the VMS License Management Utility Manual. Table_A-2_License_Unit_Requirement_Table_(LURT)____________ ________License_Types_by_Code________ __________VMS__________ SIP__ LP___ System Marketing Model_________________A_____B_____C_____D______E______F____ VAX 11/730 10 NA NA NA 230 50 VAX 11/750 12 NA NA NA 230 100 VAX 11/780, 785 13 NA NA NA 230 100 VAX 6000-210, 6000- 58 NA NA NA 230 300 310 VAXft 110, 310, 410, 58 NA NA NA 230 300 610 VAX 6000-220, 6000- 69 NA NA NA 230 600 320, 6000-410 VAX 6000-230, 6000- 81 NA NA NA 400 900 330, 6000-510 VAX 6000-240, 6000- 93 NA NA NA 400 1200 340, 6000-350, 6000-420 VAX 6000-540, 6000- 170 NA NA NA 600 2400 640 Key_to_License_Type_Codes_and_Values_______________________ A-VMS capacity B-VMS server C-VMS concurrent user D-VMS workstations E-System integrated products F-Layered products NA-Not applicable (continued on next page) A-4 License Management Notes A.2 Using the License Unit Requirement Table (LURT) Table_A-2_(Cont.)_License_Unit_Requirement_Table_(LURT)____ ________License_Types_by_Code________ __________VMS__________ SIP__ LP___ System Marketing Model_________________A_____B_____C_____D______E______F____ VAX 6000-550, 6000- 195 NA NA NA 600 2400 650 VAX 6000-560, 6000- 220 NA NA NA 600 2400 660 VAX 6000-610 81 NA NA NA 400 1200 VAX 8200, 8250 20 NA NA NA 230 100 VAX 8300, 8350 25 NA NA NA 230 200 VAX 8530 65 NA NA NA 230 400 VAX 8550, 8700, 8810 72 NA NA NA 400 600 VAX 8600, 8650 28 NA NA NA 230 400 VAX 8800, 8820 93 NA NA NA 400 1200 VAX 8830, 6000-360, 119 NA NA NA 600 1800 6000-430, 6000-520, 6000-620 VAX 6000-440, 6000- 143 NA NA NA 600 2400 450, 6000-460, 6000-530 VAX 6000-630, 9000- 143 NA NA NA 600 2400 210, 9000-410 VAX 9000-220, 9000- 241 NA NA NA 800 4800 420 Key_to_License_Type_Codes_and_Values_______________________ A-VMS capacity B-VMS server C-VMS concurrent user D-VMS workstations E-System integrated products F-Layered products NA-Not applicable (continued on next page) A-5 License Management Notes A.2 Using the License Unit Requirement Table (LURT) Table_A-2_(Cont.)_License_Unit_Requirement_Table_(LURT)____ ________License_Types_by_Code________ __________VMS__________ SIP__ LP___ System Marketing Model_________________A_____B_____C_____D______E______F____ VAX 9000-430 330 NA NA NA 800 4800 VAX 9000-440 386 NA NA NA 800 4800 Micro/VAX II 18 NA 100 NA 230 50 Micro/VAX 2000, 3100 18 NA 100 NA 230 20 Micro/VAX 3500, 60 NA 100 NA 230 200 3600, 3800, 3900 Micro/VAX 3300, 3400 60 NA 100 NA 230 100 VAX 4000-300 60 NA 100 NA 230 300 VAX 4000-500 60 NA 100 NA 400 900 VAXstation II, II NA NA NA 100 50 10 /GPX VAXstation 2000, NA NA NA 100 50 10 2000/GPX VAXstation 3100, NA NA NA 100 50 10 3200, 3500, 3520, 3540, 4000-60, 4000 VLC VAXserver 2000 NA 52 NA NA 50 10 Key_to_License_Type_Codes_and_Values_______________________ A-VMS capacity B-VMS server C-VMS concurrent user D-VMS workstations E-System integrated products F-Layered products NA-Not applicable (continued on next page) A-6 License Management Notes A.2 Using the License Unit Requirement Table (LURT) Table_A-2_(Cont.)_License_Unit_Requirement_Table_(LURT)____ ________License_Types_by_Code________ __________VMS__________ SIP__ LP___ System Marketing Model_________________A_____B_____C_____D______E______F____ VAXserver 3300, NA 100 NA NA 50 10 3400, 3500, 3600, 3900, 4000-200, 4000-300 VAXserver 6000-210, NA 1443 NA NA 230 200 6000-310 VAXserver 6000-220, NA 1737 NA NA 230 400 6000-320, 6000-410, 6000-420 VAXserver 6000-510 NA 600 NA NA 230 400 VAXserver 6000-520 NA 890 NA NA 230 400 VAXserver 9000-110, 143 143 NA NA 400 900 9000-310 VAXserver 9000-320 241 241 NA NA 400 1200 VAXserver 9000-330 330 330 NA NA 400 1200 VAXserver 9000-340 386 386 NA NA 400 1200 Key_to_License_Type_Codes_and_Values_______________________ A-VMS capacity B-VMS server C-VMS concurrent user D-VMS workstations E-System integrated products F-Layered products NA-Not applicable ___________________________________________________________ A.3 License Management Facility Notes The following list is offered to help new users with some common concerns and questions regarding the License Management Facility (LMF). For full explanations of these issues, see the VMS License Management Utility Manual. A-7 License Management Notes A.3 License Management Facility Notes o If you do not have a valid VMS license that is registered and activated, the system displays a warning message as part of system startup and restricts system use to the operator's console, OPA0. o If a checksum error is displayed when you register a license, check all the fields of data that you entered, including the checksum itself. o After your PAKs are registered, they are activated (loaded) automatically as part of each system startup. o If a VMS availability license is registered with insufficient license units for the specified VAX computer, the system displays a warning message at system startup but allows normal system use. o If a VMS activity license is registered with insufficient license units, the system displays the following message when the user (process) attempts to log in: %LICENSE-F-EXCEEDED, licensed product has exceeded current license limits Users can always log in to the operator's console, OPA0, however. o The default LICENSE database is located in the file SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB. You can move the database, although Digital does not recommend doing so. If you move the database, you must either define the logical name LMF$LICENSE at the system level to point to the new database or use the /DATABASE=filespec qualifier with all LICENSE commands. To redirect LMF to another database location on a more permanent basis, add the following line to the command procedure SYS$MANAGER:SYLOGICALS.COM: $ DEFINE/SYSTEM LMF$LICENSE device:[directory]LMF$LICENSE.LDB If you specify a device other than SYS$SYSDEVICE, you must also mount the specified disk from the SYLOGICALS.COM command procedure. o Each VMS license is restricted to a single node for permanent PAKs. You must assign a System Communications Services (SCS) name to the license when you register with the VMSLICENSE.COM command procedure, or you must enter a LICENSE MODIFY/INCLUDE=node-name command A-8 License Management Notes A.3 License Management Facility Notes after you register the license. Although you can successfully activate an unassigned VMS license on a standalone system, you cannot activate one in a VAXcluster environment. ________________________ Note ________________________ The SCS node name is not necessarily the DECnet node name. SCSNODE is a System Generation Utility (SYSGEN) parameter; it can be a maximum of six alphabetic characters. ______________________________________________________ A.4 VMS Volume Shadowing License After you install VMS Version 5.5, you must register your VMS Volume Shadowing license before you can use VMS Volume Shadowing. If you upgraded to VMS Version 5.5, you do not need to reregister this license. Please note that, with the introduction of VMS Version 5.4, the name of the VAX Volume Shadowing product changed to VMS Volume Shadowing. The HSC controller-based functionality provided by VAX Volume Shadowing is now referred to as VMS Volume Shadowing Phase I. The host-based functionality introduced with VMS Version 5.4 is referred to as VMS Volume Shadowing Phase II. The same VMS Volume Shadowing license applies for both Phase I and Phase II. In order to access Phase I shadow sets, which reside on HSC controllers, a license is required for every VAX computer that needs to access a shadow set and is directly connected to the same CI as the HSC controllers. If the license is not installed, a MOUNT/SHADOW command generates the following error message: %MOUNT-F-SHADOWFAIL, failed to create (or add to) the shadow set -LICENSE-F-NOLICENSE, no license is active for this software product Nodes that use a VMS MSCP Server to access Phase I shadow sets do not require a license. Every node that needs to access a Phase II shadow set must have a license installed, regardless of the access path to the members of the shadow set. A-9 License Management Notes A.5 Other System Integrated Product Licenses A.5 Other System Integrated Product Licenses After you install VMS Version 5.5, you must register licenses for any system integrated product. If you upgraded to VMS Version 5.5, you do not need to reregister licenses for system integrated products. A-10 B _________________________________________________________________ Booting from [SYSF] During an Upgrade This appendix describes how to boot the various VAX computers from [SYSF]. You must boot from the [SYSF] root during phases 2, 3, and 4 of the upgrade procedure. If you need more information on booting, refer to the upgrade and installation supplement for your VAX computer. B.1 Micro/VAX and VAXstation Computers The information in this section applies to the following VAX computers: VAXstation II, VAXstation II/GPX, and Micro/VAX II VAXstation 2000 and Micro/VAX 2000 VAXstation 3100 and Micro/VAX 3100 series VAXstation 3200 and 3500 VAXstation 3520 and 3540 VAXstation 4000 VAXft 110, 310, 410, 610, and 612 Micro/VAX 3300, 3400, 3500, 3600, 3800, and 3900 To boot from [SYSF], enter the BOOT command in the following format and press the Return key: >>> B/F0000000 device-name Substitute the device name of the system disk for device- name. B.2 VAX 8530, 8550, 8810 (8700), 8820-N (8800) Computers To boot from [SYSF], use the following procedure: 1. Press Ctrl/P. Enter the following command at the console-mode prompt (>>>) and press the Return key: >>> HALT B-1 Booting from [SYSF] During an Upgrade B.2 VAX 8530, 8550, 8810 (8700), 8820-N (8800) Computers 2. Enter the BOOT command at the console-mode prompt (>>>) in the following format: >>> B dddn /R5:F0000000 Substitute BCI, BDA, or UDA for ddd. Substitute the unit number of the drive holding the system disk for n. B.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. B.4 VAX-11/750, 8200, 8250, 8300, and 8350 Computers To boot from [SYSF], create a command procedure named SYFBOO.CMD before the upgrade is started. To create SYFBOO.CMD, use the following procedure: ________________________ Note ________________________ This procedure assumes that you have installed and booted the VMS operating system and are logged into the SYSTEM account. ______________________________________________________ 1. Log in to the SYSTEM account. 2. Make sure that the console media is in the console drive. 3. To connect the console drive to the system, enter the following commands and press the Return key after each one: B-2 Booting from [SYSF] During an Upgrade B.4 VAX-11/750, 8200, 8250, 8300, and 8350 Computers $ RUN SYS$SYSTEM:SYSGEN SYSGEN> CONNECT CONSOLE SYSGEN> EXIT 4. Use the Exchange Utility to copy the appropriate boot command procedure from the console media to your current directory on the system disk. If the system disk is on an HSC drive and you have created DEFBOO.CMD, enter the following command and press Return: $ EXCHANGE COPY CSA1:DEFBOO.CMD * On the VAX 11/750 computer, if the system disk is on a local drive, copy the boot command procedure that matches the drive that holds the system disk. For example, suppose the system disk is on an RP06 drive and has a controller designation of A and a unit number of one. Enter the following command and press the Return key: $ EXCHANGE COPY CSA1:DA1BOO.CMD * 5. Edit the boot command procedure. Change the line that deposits a value in register 5 (R5). This line contains the comment !software boot flags. The value is a hexadecimal number with eight digits. For example: D/G R5 0 !software boot flags Change the left-most digit of the value to reflect the name of the root directory from which you want to boot. For example, to boot from the [SYSF] root directory, change the line as follows: D/G/L R5 F0000000 !designated root is SYSF 6. Rename the boot command procedure to SYFBOO.CMD. For example, if the boot command procedure is DEFBOO.CMD, enter the following command and press the Return key: $ RENAME DEFBOO.CMD SYFBOO.CMD 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 B-3 Booting from [SYSF] During an Upgrade B.4 VAX-11/750, 8200, 8250, 8300, and 8350 Computers 8. When you are finished, enter the following command and press Return: $ DISMOUNT CSA1 9. To secure the console media from unauthorized access, you must enter the following command and press Return: $ MOUNT/FOREIGN/SYSTEM/NOWRITE/NOASSIST CSA1 To boot from [SYSF], use the following procedure: 1. Make sure the console media is in the console drive. On the VAX 11/750 computers, make sure the keylock switch is set to LOCAL. Set the BOOT DEVICE switch to position A. On the VAX 8200 computer, set the upper keylock switch to ENABLE and the lower keylock switch to HALT. 2. Press Ctrl/P. 3. On the VAX 11/750 computer, enter the following command and press the Return key: >>> B/800 DDA0 On the VAX 8200 computer, enter the following command at the console-mode prompt (>>>) and press Return: >>> B/R5:800 CSA1 4. At the BOOT58> prompt, enter the following command: BOOT58> @SYFBOO.CMD B.5 VAX-11/730, 11/780, 11/785, 8600, and 8650 Computers To boot from [SYSF], create a command procedure named SYFBOO.CMD (for VAX-11/730, 11/780, and 11/785 computers) or SYFBOO.COM (for VAX 8600 and 8650 computers) before the upgrade is started. To create SYFBOO.CMD or SYFBOO.COM, use the following procedure: ________________________ Note ________________________ This procedure assumes that you have installed and booted the VMS operating system and are logged into the SYSTEM account. ______________________________________________________ B-4 Booting from [SYSF] During an Upgrade B.5 VAX-11/730, 11/780, 11/785, 8600, and 8650 Computers 1. Log in to the SYSTEM account. 2. Make sure that the console media is in the console drive. On the VAX 8600 computer, make sure the TERMINAL CONTROL switch is set to LOCAL. 3. To connect the console drive, enter the following commands and press the Return key after each one: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> CONNECT CONSOLE SYSGEN> EXIT 4. Use the Exchange Utility to copy DEFBOO.CMD (for VAX-11 /730, 11/780, and 11/785 computers) or DEFBOO.COM (for VAX-8600 and 8650 computers) from the console media to your current directory on the system disk. On the VAX-11/780, 11/785, and 8600 computers, enter a command similar to the following and press Return: $ EXCHANGE COPY CSA1:DEFBOO.CMD * On the VAX 11/730 computer, enter the following command and press the Return key: $ EXCHANGE COPY CSA2:DEFBOO.CMD * 5. Edit DEFBOO.CMD or DEFBOO.COM. Change the line that deposits a value in register 5 (R5). On the VAX-11/730, 11/780, and 11/785 computers, this line contains the comment !software boot flags. On the VAX 8600, this line contains the comment !Use R5 for optional boot control flags [SYSB.]. The value is a hexadecimal number with eight bits. For example: DEPOSIT R5 10000000 !software boot flags Change the left-most digit of the value to reflect the name of the root directory from which you want to boot. For example, to boot from [SYSF], change the line as follows: DEPOSIT R5 F0000000 !software boot flags 6. Rename DEFBOO.CMD to SYFBOO.CMD (or DEFBOO.COM to SYFBOO.COM), as follows: $ RENAME DEFBOO.CMD SYFBOO.CMD B-5 Booting from [SYSF] During an Upgrade B.5 VAX-11/730, 11/780, 11/785, 8600, and 8650 Computers 7. Use the Exchange Utility to copy SYFBOO.CMD or SYFBOO.COM to the console media. On the VAX-11/780, 11/785, and 8600 computers enter a command similar to the following: $ EXCHANGE COPY SYFBOO.CMD CSA1:SYFBOO.CMD On the VAX 11/730 computer enter the following command and press the Return key: $ EXCHANGE COPY SYFBOO.CMD CSA2:SYFBOO.CMD 8. When you are finished, enter a command similar to the following and press Return: $ DISMOUNT CSA1 9. To secure the console media from unauthorized access, you must enter a command similar to the following and press Return: $ MOUNT/FOREIGN/SYSTEM/NOWRITE/NOASSIST CSA1 To boot from [SYSF] during an upgrade, use the following procedure: 1. Make sure the console media is in the console drive. On the VAX-11/730, 11/780, and 11/785 computers, make sure the keylock switch is set to LOCAL. On the VAX 8600, make sure the TERMINAL CONTROL switch is set to LOCAL. 2. Press Ctrl/P. On the VAX-11/780, 11/785 and 8600 computers, enter the HALT command at the console-mode prompt (>>>) and press the Return key: >>> HALT 3. Use SYFBOO.CMD to boot from [SYSF]. Enter the following command and press Return: >>> B SYF B.6 VAX 6000 Series To boot from [SYSF], use the following procedure: 1. If you have a CIBCA-A adapter and are booting over the CI, insert the console tape cartridge in the console drive. 2. Press Ctrl/P to put the system in console mode. B-6 Booting from [SYSF] During an Upgrade B.6 VAX 6000 Series 3. Enter the BOOT command in the following format: >>> BOOT /R5:F0000000 /XMI:a /BI:b [/R3:c] [/NODE:d] DUu where: o a is the XMI node number of the system disk. o b is the VAXBI node number of the system disk. o c pertains to Volume Shadowing. This qualifier is not required unless you are using Volume Shadowing. For more information, see the VAX Volume Shadowing Manual. o d is the HSC node number of the node being accessed. The /NODE qualifier is not necessary if you are booting from a local disk. The HSC node number is in hexadecimal. You can deposit a maximum of two HSC node numbers (if two HSCs are available). o u is the unit number of the drive holding the system disk. For example, suppose you want to boot from [SYSF] on an HSC disk with a unit number of one and your system has the following configuration: o The disk is connected to the VAXBI at node 2. o The VAXBI you are using is connected to the XMI at node 3. o The disk is available to two HSCs, node numbers 0E and 02. Enter the following command and press the Return key: >>> BOOT/R5:F0000000/XMI:3/BI:2/NODE:0E02 DU1 B.7 VAX 9000 Series The upgrade procedure automatically updates DEFBOO.CMD to boot from [SYSF]. If you want to boot a VAX 9000 computer manually from [SYSF] however, you must set up DEFBOO.CMD to boot from the system disk and perform the following procedure: 1. Press Ctrl/P to obtain the console prompt. B-7 Booting from [SYSF] During an Upgrade B.7 VAX 9000 Series 2. Enter the following BOOT commands: >>> I/K >>> BOOT/NOSTART >>> DEPOSIT R5 F0000000 >>> CONTINUE 3. If you set up DEFBOO.CMD properly, the system will boot from the SYSF directory on the system disk and continue with the upgrade procedure. If the system does not boot, enter the SHOW CONFIGURATION console command and verify that DEFBOO.CMD contains the correct information for your configuration. For more information, see the VMS Upgrade and Installation Supplement: VAX 9000 Series. B-8 C _________________________________________________________________ VMS Library and Optional Save Set Files This appendix lists the VMS library and optional, that is, VMS055.C and VMS055.D, save set files. VMS Library Save Set Files Accounting Log Report Generator Utility Analyze Object File Utility (ANALYZE/OBJECT) Debugger Utility (DEBUG) Delta debugger DUMP EDT documentation Error Log Report Generator Utility (ANALYZE/ERROR) File Access Control List Utilities Files-11 ODS1 ACP Foreign terminal support FORTRAN require files Image Dump Utility (ANALYZE/IMAGE) Incoming Remote File Access files Incoming Remote Terminal files Input Queue Symbiont (Card Reader) LAT-11 terminal server (via Ethernet) MACRO Assembler MACRO Libraries MAIL Message Utility (MESSAGE) Monitor Utility National Character Set Utility (NCS) Network support Network Test files Object and Shareable Image libraries PHONE Print and Batch Queue Utilities Programming support Remote Task Loading C-1 VMS Library and Optional Save Set Files RMS Analyze and FDL Editor Utilities (ANALYZE/RMS, ANALYZE/FDL) RMS Journaling files RUNOFF SDL intermediary form of STARLET.MLB Secure User's Environment Standalone BACKUP System Dump Analyzer Utility (ANALYZE/SYSTEM, ANALYZE/CRASH) System programming support System Symbol Table file (SYS.STB) TECO editor Terminal Fallback Facility VAX-C object libraries VAXTPU VMS HELP library VMS workstation support VMS workstation device support VMS Optional Save Set Files BLISS require files Example files Files for VMS development only Files used for kitting LPA-11 support Miscellaneous files Miscellaneous Symbol Table files System map User Environment Test Package (UETP) C-2 D _________________________________________________________________ DECwindows Software Components Table D-1 contains the name of each VMS DECwindows software component, the directory where the component can be found, a brief description of what the component does, and one of the following three component classifications: o ALL-Indicates that the component is part of all installations. o PROG-Indicates the component is part of the programming environment. o WS-Indicates that the component is part of the workstation device support. o XMPL-Indicates that the component is part of the programming examples. Table_D-1_DECwindows_Software_Components_________________________ Component File__________________Purpose______________________________Class_ ______________________Files_in_CDA$LIBRARY_Directory_____________ DEFSTYLE.DDIF DDIF document style guide PROG (continued on next page) D-1 DECwindows Software Components Table_D-1_(Cont.)_DECwindows_Software_Components_________________ Component _________________________________________________________________ ______________________Files_in_DECW$EXAMPLES_Directory___________ DEMO_BUILD.COM Procedure to compile demo sources XMPL ALLOBJS.H Demo source XMPL BITMAP.C Demo source XMPL BITMAP.EXE Demo source XMPL BTRAP.C Broadcast message trapper program XMPL file BTRAP.EXE Broadcast message trapper image XMPL file BTRAP.UID Broadcast message trapper support XMPL file BTRAP.UIL Broadcast message trapper support XMPL file CLOCK.DDIF Paint example ALL DECBURGER.ADA UIL DRM Demo source XMPL DECBURGER.C UIL DRM Demo souce XMPL DECBURGER.COM UIL DRM Demo file XMPL DECBURGER.EXE UIL DRM Demo image XMPL DECBURGER.FOR UIL DRM Demo file XMPL DECBURGER.UID UIL DRM Demo file XMPL DECBURGER.UIL UIL DRM Demo file XMPL DECBURGER_DEFS.FOR UIL DRM Demo file XMPL DECW$TRANSPORT_ Demo image XMPL EXAMPLE.EXE DIALOG.C Demo source XMPL DWTVMSPUSHTEST.B32 XUI toolkit demo XMPL DWTVMSPUSHTEST.EXE Demo image XMPL HELLOWORLD.ADA XUI toolkit demo source XMPL HELLOWORLD.C XUI toolkit demo XMPL (continued on next page) D-2 DECwindows Software Components Table_D-1_(Cont.)_DECwindows_Software_Components_________________ Component File__________________Purpose______________________________Class_ ______________________Files_in_DECW$EXAMPLES_Directory___________ HELLOWORLD.EXE XUI toolkit demo image XMPL HELLOWORLD.FOR XUI toolkit demo XMPL HELLOWORLD.UID XUI toolkit demo file XMPL HELLOWORLD.UIL XUI toolkit demo file XMPL ICO.C Demo source XMPL ICO.EXE Demo image XMPL ICOPAS.PAS Demo source XMPL OBJCUBE.H Demo source XMPL OBJICO.H Demo source XMPL OBJTETRA.H Demo source XMPL PLAID.C Demo source XMPL PLAID.EXE Demo image XMPL POLYINFO.H Demo source XMPL STRINGS.MAR Low-level DECwindows utility XMPL routine TESTVHIST.C Histogram widget exerciser program XMPL file TESTVHIST.EXE Histogram widget exerciser image XMPL file TESTVHIST.UIL Histogram widget exerciser support XMPL file TESTVHIST.UID VList widget exerciser support file XMPL TESTVLIST.C VList widget exerciser program file XMPL TESTVLIST.EXE VList widget exerciser image file XMPL TESTVLIST.UID VList widget exerciser support file XMPL TESTVLIST.UIL VList widget exerciser support file XMPL TLIST.C TList widget source file XMPL TLIST.H TList widget support file XMPL (continued on next page) D-3 DECwindows Software Components Table_D-1_(Cont.)_DECwindows_Software_Components_________________ Component File__________________Purpose______________________________Class_ ______________________Files_in_DECW$EXAMPLES_Directory___________ TLIST.NOTE TList widget support file XMPL TLIST.UIL TList widget support file XMPL VFRAME.C VFrame widget source file XMPL VFRAME.H VFrame widget support file XMPL VFRAME.UIL VFrame widget support file XMPL VDRAGEXAMPLE.C VDrag exerciser source file XMPL VDRAGEXAMPLE.EXE VDrag exerciser image file XMPL VDRAG.C VDrag exerciser source file XMPL VDRAG.NOTE VDrag exerciser support file XMPL VHEADER.C VHeader widget source file XMPL VHEADER.H VHeader widget support file XMPL VHEADER.UIL VHeader widget support file XMPL VHIST.C VHist widget source file XMPL VHIST.H VHist widget support file XMPL VHIST.NOTE VHist widget support file XMPL VHIST.UIL VHist widget support file XMPL VLIST.C VList widget source file XMPL VLIST.H VList widget support file XMPL VLIST.NOTE VList widget support file XMPL VLIST.UIL VList widget support file XMPL XLIBINTRO.ADA Demo source XMPL XLIBINTRO.C Demo source XMPL XLIBINTRO.EXE Demo image XMPL (continued on next page) D-4 DECwindows Software Components Table_D-1_(Cont.)_DECwindows_Software_Components_________________ Component File__________________Purpose______________________________Class_ ______________________Files_in_DECW$EXAMPLES_Directory___________ XLIBINTRO.FOR Demo source XMPL XPORTEXAMPLEDEF.R32 Demo source XMPL XPORT_EXAMPLE.B32 Demo source XMPL XPORT_EXAMPLE_ Demo source XMPL QUEUE.MAR XPORT_EXAMPLE_ Demo source XMPL XFER.MAR _________________________________________________________________ ______________________Files_in_DECW$FONT_Directory_______________ See VMS DECwindows DECwindows fonts WS Xlib Programming Volume _________________________________________________________________ ______________________Files_in_DECW$INCLUDE_Directory____________ COMPOBJ.H Xlib and XUI toolkit programming PROG include files COMPOBJP.H Xlib and XUI toolkit programming PROG include files COMPOSITE.H Xlib and XUI toolkit programming PROG include files COMPOSITEP.H Xlib and XUI toolkit programming PROG include files CONSTRAINT.H Xlib and XUI toolkit programming PROG include files CONSTRAINP.H Xlib and XUI toolkit programming PROG include files CONVERT.H Xlib and XUI toolkit programming PROG include files (continued on next page) D-5 DECwindows Software Components Table_D-1_(Cont.)_DECwindows_Software_Components_________________ Component File__________________Purpose______________________________Class_ ______________________Files_in_DECW$INCLUDE_Directory____________ CORE.H Xlib and XUI toolkit programming PROG include files COREP.H Xlib and XUI toolkit programming PROG include files CSTEXTP.H Xlib and XUI toolkit programming PROG include files CURSORFONT.H Xlib and XUI toolkit programming PROG include files DECW$DWTDEF.UIL UIL language include file PROG DECWDWTAPPLPROG.H Xlib and XUI toolkit programming PROG include files DECWDWTAPPLPROG.UIL XUI toolkit support PROG DECWDWTWIDGETPROG.H Xlib and XUI toolkit programming PROG include files DECWMHINTS.H Xlib and XUI toolkit programming PROG include files DRMDECLS.H Xlib and XUI toolkit programming PROG include file DRMPUBLIC.H Xlib and XUI toolkit programming PROG include file DVR$CC_DEF.H CDA Viewer support file ALL DVR$DECW_DEF.H CDA Viewer support file ALL DVR$MSG.H CDA Viewer support file ALL DWTAPPL.H Xlib and XUI toolkit programming PROG include files DWTAPPL.UIL Xlib and XUI toolkit programming PROG include files DWTWIDGET.H Xlib and XUI toolkit programming PROG include files (continued on next page) D-6 DECwindows Software Components Table_D-1_(Cont.)_DECwindows_Software_Components_________________ Component File__________________Purpose______________________________Class_ ______________________Files_in_DECW$INCLUDE_Directory____________ EVENT.H Xlib and XUI toolkit programming PROG include files INTRINSIC.H Xlib and XUI toolkit programming PROG include files INTRINSICP.H Xlib and XUI toolkit programming PROG include files KEYSYM.H Xlib and XUI toolkit programming PROG include files KEYSYMDEF.H Xlib and XUI toolkit programming PROG include files OBJECT.H Xlib and XUI toolkit programming PROG include files OBJECTP.H Xlib and XUI toolkit programming PROG include files RECTOBJ.H Xlib and XUI toolkit programming PROG include files RECTOBJP.H Xlib and XUI toolkit programming PROG include files SELECTION.H Xlib and XUI toolkit programming PROG include files SHELL.H Xlib and XUI toolkit programming PROG include files SHELLP.H Xlib and XUI toolkit programming PROG include files STRINGDEFS.H Xlib and XUI toolkit programming PROG include files TRANSLATE.H Xlib and XUI toolkit programming PROG include files VENDOR.H Xlib and XUI toolkit programming PROG include files (continued on next page) D-7 DECwindows Software Components Table_D-1_(Cont.)_DECwindows_Software_Components_________________ Component File__________________Purpose______________________________Class_ ______________________Files_in_DECW$INCLUDE_Directory____________ VENDORP.H Xlib and XUI toolkit programming PROG include files WINDOWOBJ.H Xlib and XUI toolkit programming PROG include files WINDOWOBJP.H Xlib and XUI toolkit programming PROG include files X.H Xlib and XUI toolkit programming PROG include files XATOM.H Xlib and XUI toolkit programming PROG include files XLIB.H Xlib and XUI toolkit programming PROG include files XMD.H Xlib and XUI toolkit programming PROG include files XOS.H Xlib and XUI toolkit programming PROG include files XPROTO.H Xlib and XUI toolkit programming PROG include files XPROTOSTR.H Xlib and XUI toolkit programming PROG include files XRESOURCE.H Xlib and XUI toolkit programming PROG include files XUTIL.H Xlib and XUI toolkit programming PROG include files (continued on next page) D-8 DECwindows Software Components Table_D-1_(Cont.)_DECwindows_Software_Components_________________ Component _________________________________________________________________ ______________________Files_in_DECW$SYSTEM_DEFAULTS_Directory____ DDIF$VIEW.UID CDA Viewer support file ALL DDIF$VIEWWGT.UID CDA Viewer support file ALL DECW$BOOKREADER.DAT Bookreader support file ALL DECW$BOOKREADER.UID Bookreader support file ALL DECW$CALC.DAT Calculator support file ALL DECW$CALC.UID Calculator support file ALL DECW$CALENDAR.DAT Calendar support file ALL DECW$CALENDAR.UID Calendar support file ALL DECW$CARDFILER.DAT Cardfiler support file ALL DECW$CARDFILER.UID Cardfiler support file ALL DECW$CLOCK.DAT Clock support file ALL DECW$CLOCK.UID Clock support file ALL DECW$LOGIN.DAT Login support file ALL DECW$LOGIN.UID Login support file ALL DECW$MAIL.DAT DECwindows VMSmail support file ALL DECW$MAIL_MAIN.UID DECwindows VMSmail support file ALL DECW$MAIL_MISC.UID DECwindows VMSmail support file ALL DECW$MAIL_READ.UID DECwindows VMSmail support file ALL DECW$MAIL_SEND.UID DECwindows VMSmail support file ALL DECW$NOTEPAD.DAT NOTEPAD support file ALL DECW$NOTEPAD.UID NOTEPAD support file ALL DECW$PAINT.DAT DECwindows Paint support file ALL DECW$PAINT.UID DECwindows Paint support file ALL DECW$PRINTWGT.UID Print support file ALL DECW$PRINTWGT_UI.UID Print support file ALL DECW$PUZZLE.DAT Puzzle support file ALL DECW$PUZZLE.UID Puzzle support file ALL (continued on next page) D-9 DECwindows Software Components Table_D-1_(Cont.)_DECwindows_Software_Components_________________ Component File__________________Purpose______________________________Class_ ______________________Files_in_DECW$SYSTEM_DEFAULTS_Directory____ DECW$SESSION.DAT Session manager support file ALL DECW$SESSION.UID Session manager support file ALL DECW$SM_BW.DAT Session manager support file ALL DECW$SM_COLOR.DAT Session manager support file ALL DECW$SM_GENERAL.DAT Session manager support file ALL DECW$SM_GRAY.DAT Session manager support file ALL DECW$TERMINAL.DAT Terminal support file ALL DECW$TERMINAL.UID Terminal support file ALL DECW$WINMGR.DAT Window manager support file ALL DECW$WINMGR.UID Window manager support file ALL VUE$MASTER.UID FileView defaults file ALL XNL_88591.UID XNLS ISOLATIN1 character set PROG XNL_88598.UID XNLS ISOLATIN8 character set PROG XNL_DE_CH.UID XNLS Swiss German culture file PROG XNL_DE_DE.UID XNLS German culture file PROG XNL_EN_AU.UID XNLS Australian culture file PROG XNL_EN_GB.UID XNLS British English culture file PROG XNL_EN_NZ.UID XNLS New Zealand culture file PROG XNL_EN_PG.UID XNLS Papua New Guinea culture file PROG XNL_EN_US.UID XNLS American English culture file PROG XNL_ES_ES.UID XNLS Spanish culture file PROG XNL_FI_FI.UID XNLS Finnish culture file PROG XNL_FJ_FJ.UID XNLS Fiji culture file PROG XNL_FR_BE.UID XNLS Belgian French culture file PROG XNL_FR_CA.UID XNLS Canadian French culture file PROG XNL_FR_CH.UID XNLS Swiss French culture file PROG XNL_FR_FR.UID XNLS French culture file PROG (continued on next page) D-10 DECwindows Software Components Table_D-1_(Cont.)_DECwindows_Software_Components_________________ Component File__________________Purpose______________________________Class_ ______________________Files_in_DECW$SYSTEM_DEFAULTS_Directory____ XNL_IT_CH.UID XNLS Swiss Italian culture file PROG XNL_IT_IT.UID XNLS Italian culture file PROG XNL_IW_IL.UID XNLS Hebrew culture file PROG XNL_NL_BE.UID XNLS Flemish culture file PROG XNL_NL_NL.UID XNLS Dutch culture file PROG XNL_NO_NO.UID XNLS Norwegian culture file PROG XNL_SV_SE.UID XNLS Swedish culture file PROG _________________________________________________________________ ______________________Files_in_SYS$LIBRARY_Directory_____________ CDA$ACCESS.EXE The DDIF toolkit and DDIF converter PROG toolkit Run-time-library shareable image CDA$CDA_.ADA CDA Ada binding PROG CDA$DEF.*+ DDIF converter language binding PROG CDA$DTIF_TO_DDIF.EXE CDA DTIF to DDIF converter image ALL CDA$MSG.*+ DDIF message symbols PROG CDA$WRITE_ CDA image ALL ANALYSIS.EXE DDIF$DDIF_.ADA DDIF Ada binding PROG DDIF$DEF.*+ DDIF language binding PROG DDIF$READ_TEXT.EXE Text front end shareable image ALL DDIF$VIEWSHR.EXE DDIF viewer shareable image ALL DDIF$WRITE_PS.EXE Text image ALL DDIF$WRITE_TEXT.EXE Text back end shareable image ALL DECW$AILSHR.EXE Image support shareable image ALL +BASIC,_BLISS,_FORTRAN,_C,_Macro,_Pascal,_and_PLI_languages______ are supported. Asterisk (*) represents the appropriate file extension for each language. (continued on next page) D-11 DECwindows Software Components Table_D-1_(Cont.)_DECwindows_Software_Components_________________ Component File__________________Purpose______________________________Class_ ______________________Files_in_SYS$LIBRARY_Directory_____________ DECW$CALENDAR_ Calendar support file ALL PROLOG.PS DECW$CURSOR.H Cursor include files PROG DECW$DRIVER.MLB Driver macro library PROG DECW$DWT_.ADA Toolkit Ada binding PROG DECW$DWTDEF.*+ Widget include files PROG DECW$DWTENTRY.* DECW$DWTLIBSHR.EXE XUI toolkit shareable image PROG DECW$DWTMSG.* Toolkit message file PROG DECW$DWTSTRUCT.* Widget include files PROG DECW$DWTWIDGETSTRUCT.*Widget include files PROG DECW$DWTWIDGETDEF.*+ Widget include files PROG DECW$LOGINOUT.EXE DECwindows extension to VMS ALL loginout image DECW$MAILSHR.EXE DECwindows VMSmail shareable image ALL DECW$PRINTWGT.UID Print support file ALL DECW$PRINTWGTSHR.EXE DECwindows print widget shareable ALL image DECW$SERVER_DDX_ Server color device support WS GA.EXE shareable image DECW$SERVER_DDX_ Server color device support WS GB.EXE shareable image DECW$SERVER_DDX_ Server monochrome device support WS GC.EXE shareable image DECW$SERVER_DDX_ Server scanproc device-dependent WS GE.EXE shareable image +BASIC,_BLISS,_FORTRAN,_C,_Macro,_Pascal,_and_PLI_languages______ are supported. Asterisk (*) represents the appropriate file extension for each language. (continued on next page) D-12 DECwindows Software Components Table_D-1_(Cont.)_DECwindows_Software_Components_________________ Component File__________________Purpose______________________________Class_ ______________________Files_in_SYS$LIBRARY_Directory_____________ DECW$SERVER_DDX_ Server low-cost graphics device- WS GF.EXE dependent sharable image DECW$SERVER_DIX.EXE Server device independent support WS DECW$SERVER_ PHIGS X Server Extension WS EXTENSION_PEX.EXE DECW$SVEXT_ADOBE_ Display Postscript server extension WS DPS_EXTENSION.EXE image DECW$TERMINALSHR.EXE Terminal shareable image ALL DECW$TRANSPORT_ Common transport shareable image ALL COMMON.EXE DECW$TRANSPORT_ DECnet transport image ALL DECNET.EXE DECW$TRANSPORT_ LAT transport image ALL LAT.EXE DECW$TRANSPORT_ Local transport image ALL LOCAL.EXE DECW$TRANSPORT_ TCP/IP transport image ALL TCPIP.EXE DECW$UIL.ENV LSE template for UIL compilier PROG DECW$X_.ADA Xlib Ada binding PROG DECW$XLIBDEF.*+ Language Xlib binding PROG DECW$XLIBMSG.*+ Language message symbols PROG DECW$XLIBSHR.EXE Xlib shareable image PROG DECW$XPORTCOM.H Common transport definitions PROG DECW$XPORTCOM.MAR Common transport definitions PROG DECW$XPORTCOM.R32 Common transport definitions PROG DECW$XPORTDEF.H Transport definitions PROG +BASIC,_BLISS,_FORTRAN,_C,_Macro,_Pascal,_and_PLI_languages______ are supported. Asterisk (*) represents the appropriate file extension for each language. (continued on next page) D-13 DECwindows Software Components Table_D-1_(Cont.)_DECwindows_Software_Components_________________ Component File__________________Purpose______________________________Class_ ______________________Files_in_SYS$LIBRARY_Directory_____________ DECW$XPORTDEF.MAR Transport definitions PROG DECW$XPORTDEF.R32 Transport definitions PROG DECW$XPORTMAC.R32 Transport BLISS macros PROG DECW$XPORTMSG.R32 Transport message symbols PROG PHIGS$GB_UCODE.EXE PHIGS image WS XDPS$DPSBINDINGSSHR.EXDisplay Postscript VAX Bindings ALL image XDPS$DPSCLIENTSHR.EXE Display Postscript client library ALL image XDPS$DPSLIBSHR.EXE Display Postscript xlib extension ALL image XDPS$DPSOPS.*++ Display Postscript include file PROG XDPS$DPSXCLIENT.*++ Display Postscript include file PROG XDPS$MASTERDPSVM.DAT Display Postscript support file ALL XDPS$PSOPS.*++ Display Postscript include file PROG XNL$SHR.EXE XNLS shareable image ALL XDPS$XDPS.*++ Display Postscript include file PROG XDPS$XDPSLIB.*++ Display Postscript include file PROG XNL$DEF.*++ XNLS include files PROG XNL$MSG.*++ XNLS message symbols PROG _________________________________________________________________ ______________________Files_in_SYS$MANAGER_Directory_____________ DECW$CHECK_ Check AUTOGEN parameters ALL PARAMS.COM DECW$DEVICE.COM Device detection and configuration ALL ++BASIC,_BLISS,_FORTRAN,_C,_and_Macro_languages_are_supported.___ Asterisk (*) represents the appropriate file extension for each language. (continued on next page) D-14 DECwindows Software Components Table_D-1_(Cont.)_DECwindows_Software_Components_________________ Component File__________________Purpose______________________________Class_ ______________________Files_in_SYS$MANAGER_Directory_____________ DECW$DEVICE_GE.COM Scanproc device detection and WS configuration DECW$DEVICE_GF.COM Low-cost graphics device detection WS and configuration DECW$LOGICALS.COM Logical name table initialization ALL and start DECW$PRIVATE_SERVER_ Server customization template WS SETUP.TEMPLATE DECW$RGB.COM Definitions of the color names WS used by the XStoreNamedColor and XAllocNamedColor requests DECW$STARTAPPS.COM User environment ALL DECW$STARTLIBS.COM Programming environment startup PROG DECW$STARTSERVER.COM Server initialization and startup WS DECW$STARTSM.COM Starts the session manager ALL DECW$STARTUP.COM Starts the DECwindows environment ALL DECW$SYLOGIN.TEMPLATE System login file template ALL _________________________________________________________________ ______________________Files_in_SYS$MESSAGE_Directory_____________ DDIF$VIEWMSG.EXE Viewer message file ALL DECW$DWTERRDB.DAT Toolkit error support file PROG DECW$DWTMSG.EXE Toolkit message file PROG DECW$TERMINALMSG.EXE DECterm message file ALL DECW$TRANSPORTMSG.EXE Transport message image ALL DECW$XLIBERRDB.DAT Xlib resource database PROG DECW$XLIBMSG.EXE Xlib message image PROG (continued on next page) D-15 DECwindows Software Components Table_D-1_(Cont.)_DECwindows_Software_Components_________________ Component File__________________Purpose______________________________Class_ ______________________Files_in_SYS$SYSTEM_Directory______________ CDA$CONVERT.EXE DDIF converter image ALL DDIF$VIEW.EXE DDIF viewer ALL DECW$BOOKREADER.EXE Bookreader image ALL DECW$CALC.EXE Calculator image ALL DECW$CALENDAR.EXE Calendar image ALL DECW$CARDFILER.EXE Cardfiler image ALL DECW$CLOCK.EXE Clock image ALL DECW$FONTCOMPILER.EXE Font compiler image ALL DECW$MAIL.EXE DECwindows VMSmail image ALL DECW$NOTEPAD.EXE Notepad image ALL DECW$PAINT.EXE Paint image ALL DECW$PUZZLE.EXE Puzzle image ALL DECW$SERVER_MAIN.EXE Server main image WS DECW$SESSION.EXE Manages the session and contains ALL the control panel DECW$SETSHODIS.EXE SET/SHOW DISPLAY command image PROG DECW$STARTLOGIN.EXE Starts the DECwindows LOGINOUT.EXE ALL image DECW$TERMINAL.EXE Terminal emulator controller ALL DECW$TERMINAL_ DECterm image ALL CREATE.EXE DECW$UILCOMPILER.EXE UIL compiler PROG DECW$WINMGR.EXE DECwindows window manager ALL VUE$MASTER.EXE FileView image ALL XDPS$PSWRAP.EXE Display Postscript PSWRAP utility PROG image (continued on next page) D-16 DECwindows Software Components Table_D-1_(Cont.)_DECwindows_Software_Components_________________ Component File__________________Purpose______________________________Class_ ______________________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 WS driver GCBDRIVER.EXE VAXstation 2000 monochrome device WS driver GEBDRIVER.EXE scanproc graphics device driver WS GFBDRIVER.EXE Low-cost graphics device driver WS IKDRIVER.EXE Keyboard decoder driver WS IMDRIVER.EXE Mouse decoder driver WS INDRIVER.EXE Common input function driver WS PYDRIVER.EXE Pseudo terminal driver ALL TWDRIVER.EXE Pseudo terminal driver ALL WSDRIVER.EXE Set display driver ALL (continued on next page) D-17 DECwindows Software Components Table_D-1_(Cont.)_DECwindows_Software_Components_________________ Component File__________________Purpose______________________________Class_ ______________________Files_in_DECW$BOOK_Directory_______________ BOOKREADER.DECW$BOOK Online user's guide for the ALL Bookreader LIBRARY.DECW$BOOKSHELFBookreader bookshelf ALL _________________________________________________________________ ______________________Files_in_DECW$KEYMAP_Directory_____________ *.DECW$KEYMAP DECwindows Keymap files WS _________________________________________________________________ ______________________Files_in_SYS$HELP_Directory________________ DDIF$VIEW.HLB View help file ALL DECW$BOOKREADER.HLB Bookreader help file ALL DECW$CALC.HLB Calculator help file ALL DECW$CALENDAR.HLB Calendar help file ALL DECW$CARDFILER.HLB Cardfiler help file ALL DECW$CLOCK.HLB Clock help file ALL DECW$HELPHELP.HLB HELP help file PROG DECW$MAIL.HLB Mail help file ALL DECW$NOTEPAD.HLB Notepad help file ALL DECW$PAINT.HLB Paint help file ALL DECW$PRINTWGT.HLB Print help file ALL DECW$PUZZLE.HLB Puzzle help file ALL DECW$SESSION.HLB Session Manager help file ALL DECW$TERMINAL.HLB Terminal Emulator help file ALL DECW$VUE.HLB FileView help file ALL _________________________________________________________________ ______________________Files_in_SYS$UPDATE_Directory______________ DECW$COMPILE_ADA_ Ada build file PROG UNITS.COM DECW$KITBLD.DAT Installation support file ALL (continued on next page) D-18 DECwindows Software Components Table_D-1_(Cont.)_DECwindows_Software_Components_________________ Component File__________________Purpose______________________________Class_ ______________________Files_in_SYS$UPDATE_Directory______________ DECW$KITBLD.IDX Installation support file ALL DECW$TAILOR.EXE Tailoring program ALL DECW$TAILOR_ Tailoring support file ALL ON.TEMPLATE (continued on next page) D-19 DECwindows Software Components Table D-1 (Cont.) DECwindows Software Components ______________________Files_in_VUE$LIBRARY_Directory_____________ VUE$*.COM FileView verb command files ALL VUE$SYSTEM_ FileView default system profile ALL PROFILE.VUE$DAT _________________________________________________________________ ______________________Files_in_XDPS$EXAMPLES_Directory___________ ACTIONPRCS.H Display Postscript PSDRAW example XMPL application file ACTIONS.C Display Postscript PSDRAW example XMPL application file ACTIONS.H Display Postscript PSDRAW example XMPL application file BIGICON.BIT Display Postscript PSDRAW example XMPL application file BUILD_PSDRAW.COM Display Postscript PSDRAW example XMPL application file BUTTON.C Display Postscript PSDRAW example XMPL application file BUTTON.H Display Postscript PSDRAW example XMPL application file BUTTONP.H Display Postscript PSDRAW example XMPL application file COLOR.C Display Postscript PSDRAW example XMPL application file COLOR.H Display Postscript PSDRAW example XMPL application file COORDS.C Display Postscript PSDRAW example XMPL application file COORDS.H Display Postscript PSDRAW example XMPL application file COORDSP.H Display Postscript PSDRAW example XMPL application file DRAWING.C Display Postscript PSDRAW example XMPL application file (continued on next page) D-20 DECwindows Software Components Table_D-1_(Cont.)_DECwindows_Software_Components_________________ Component File__________________Purpose______________________________Class_ ______________________Files_in_XDPS$EXAMPLES_Directory___________ DRAWING.H Display Postscript PSDRAW example XMPL application file DRAWINGP.H Display Postscript PSDRAW example XMPL application file KNOBS.C Display Postscript PSDRAW example XMPL application file KNOBS.H Display Postscript PSDRAW example XMPL application file KNOBSP.H Display Postscript PSDRAW example XMPL application file MENUS.C Display Postscript PSDRAW example XMPL application file MENUS.H Display Postscript PSDRAW example XMPL application file MODE.C Display Postscript PSDRAW example XMPL application file MODE.H Display Postscript PSDRAW example XMPL application file MODEP.H Display Postscript PSDRAW example XMPL application file M_PI.H Display Postscript PSDRAW example XMPL application file OPS.C Display Postscript PSDRAW example XMPL application file PANE.C Display Postscript PSDRAW example XMPL application file PANE.H Display Postscript PSDRAW example XMPL application file PANEP.H Display Postscript PSDRAW example XMPL application file (continued on next page) D-21 DECwindows Software Components Table_D-1_(Cont.)_DECwindows_Software_Components_________________ Component File__________________Purpose______________________________Class_ ______________________Files_in_XDPS$EXAMPLES_Directory___________ PIXMGR.C Display Postscript PSDRAW example XMPL application file PIXMGR.H Display Postscript PSDRAW example XMPL application file POPUP.C Display Postscript PSDRAW example XMPL application file POPUP.H Display Postscript PSDRAW example XMPL application file PROP.C Display Postscript PSDRAW example XMPL application file PROP.H Display Postscript PSDRAW example XMPL application file PROPP.H Display Postscript PSDRAW example XMPL application file PSDRAW.C Display Postscript PSDRAW example XMPL application file PSDRAW.COM Display Postscript PSDRAW example XMPL application file PSDRAW.DAT Display Postscript PSDRAW example XMPL application file PSDRAW.H Display Postscript PSDRAW example XMPL application file PSDRAWCOMPLIB.DAT Display Postscript PSDRAW example XMPL application file PSDRAWKINDS.DAT Display Postscript PSDRAW example XMPL application file PSWINDOW.C Display Postscript PSDRAW example XMPL application file PSWINDOW.H Display Postscript PSDRAW example XMPL application file (continued on next page) D-22 DECwindows Software Components Table_D-1_(Cont.)_DECwindows_Software_Components_________________ Component File__________________Purpose______________________________Class_ ______________________Files_in_XDPS$EXAMPLES_Directory___________ PSWINDOWP.H Display Postscript PSDRAW example XMPL application file PSWINDW.C Display Postscript PSDRAW example XMPL application file PSWINDW.PSW Display Postscript PSDRAW example XMPL application file RECT.C Display Postscript PSDRAW example XMPL application file RECT.H Display Postscript PSDRAW example XMPL application file RECTP.H Display Postscript PSDRAW example XMPL application file ROUND.C Display Postscript PSDRAW example XMPL application file SCRN.C Display Postscript PSDRAW example XMPL application file SCRN.H Display Postscript PSDRAW example XMPL application file SCRNP.H Display Postscript PSDRAW example XMPL application file SCROLLW.C Display Postscript PSDRAW example XMPL application file SCROLLW.H Display Postscript PSDRAW example XMPL application file SCROLLWP.H Display Postscript PSDRAW example XMPL application file SMALLICON.BIT Display Postscript PSDRAW example XMPL application file STRING.H Display Postscript PSDRAW example XMPL application file (continued on next page) D-23 DECwindows Software Components Table_D-1_(Cont.)_DECwindows_Software_Components_________________ Component File__________________Purpose______________________________Class_ ______________________Files_in_XDPS$EXAMPLES_Directory___________ STRINGS.MAR Display Postscript PSDRAW example XMPL application file UTIL.C Display Postscript PSDRAW example XMPL application file UTIL.H Display Postscript PSDRAW example XMPL application file VALUE.C Display Postscript PSDRAW example XMPL application file VALUE.H Display Postscript PSDRAW example XMPL application file VALUEP.H Display Postscript PSDRAW example XMPL application file WIDGET.C Display Postscript PSDRAW example XMPL application file WIDGET.H Display Postscript PSDRAW example XMPL application file WIDGETINFO.C Display Postscript PSDRAW example XMPL application file WIDGETINFO.H Display Postscript PSDRAW example XMPL application file WRAPS.C Display Postscript PSDRAW example XMPL application file WRAPS.PSW Display Postscript PSDRAW example XMPL application file XMAPRGBTOPIXEL.C Display Postscript PSDRAW example XMPL application file PSDRAW.EXE Display Postscript PSDRAW example XMPL application file PSDRAW_README.PS Display Postscript PSDRAW example XMPL application file (continued on next page) D-24 DECwindows Software Components Table_D-1_(Cont.)_DECwindows_Software_Components_________________ Component File__________________Purpose______________________________Class_ ______________________Files_in_XDPS$INCLUDE_Directory____________ DPSCLIENT.H Display Postscript support file PROG DPSCUSTOMOPS.H Display Postscript support file PROG DPSEXCEPT.H Display Postscript support file PROG DPSFRIENDS.H Display Postscript support file PROG DPSOPS.H Display Postscript support file PROG DPSXCLIENT.H Display Postscript support file PROG PSCUSTOMOPS.H Display Postscript support file PROG PSOPS.H Display Postscript support file PROG XDPS.H Display Postscript support file PROG XDPSLIB.H_____________Display_Postscript_support_file______PROG__ D-25 E _________________________________________________________________ Layered Products Availability Table Given the design of the VMS Version 5.5 upgrade procedure, you should not have to reinstall most layered products after the upgrade. If a product is available (refer to Table E-1), yet it exhibits unexpected behavior when Version 5.5 is running, check the Upgrade Notes section in Chapter 2 of the VMS Version 5.5 Release Notes for layered product restrictions. If problems persist, contact your Digital Services representative. Table E-1 lists the versions of layered products that were supported for VMS Version 5.5 on October 29, 1991. As this list is subject to change, Digital recommends that you refer to the System Support Addendum and Release Notes for the latest information on each layered product. If problems persist, contact your Digital Services representative. Table E-1 VMS Layered Products Currently Available for VMS __________Version_V5.5___________________________________________ Most Recent Product_Name___________________________________Version___________ 3270 Terminal Option Software 1.1 AAF01/VMS Subroutine Library 2.0 ADF01/VMS Subroutine Library 4.0 ALL-IN-1 2.4[1] ALL-IN-1 Electronic Authorization and Routing 2.1 System for VMS ALL-IN-1 Mail 1.1 [1]See_VMS_Version_5.5_Release_Notes_for_additional_information._ (continued on next page) E-1 Layered Products Availability Table Table E-1 (Cont.) VMS Layered Products Currently Available for __________________VMS_Version_V5.5_______________________________ Most Recent Product_Name___________________________________Version___________ ALL-IN-1 PC Server for VMS 1.0 ALL-IN-1 Services for DECwindows 1.0 ALL-IN-1 Starter 2.4 BASEstar for VMS 3.0 CDA Converter Library for VMS 1.1 DEC ACA Services for VMS 2.0 DEC COMMserver for VMS 1.0 DEC Computer Integrated Telephony Application 3.0 Interface for VMS DEC Computer Integrated Telephony Server for 3.0 VMS DEC Extended Basic Mode (XBM) CO3 Access for 4.0 VMS DEC Extended Basic Mode (XBM) CO3 Gateway for 4.0 VMS DEC GKS for VMS 4.2 DEC GKS-3D for VMS 1.1 DEC High Availability Management Software for 1.2 VMS DEC IEZ11 Class Driver for VMS 2.0 DEC Image Utility Library for VMS 1.0 DEC LMF PAK Generator for VMS 1.0 DEC ODA Compound Document Architecture (CDA) 1.0 Gateway for VMS DEC PHIGS for VMS 2.2A DEC PrintServer Supporting Host Software for 4.0 VMS DEC RdbAccess for Oracle on VMS 1.0 DEC RdbAccess for VAX RMS on VMS 1.0 (continued on next page) E-2 Layered Products Availability Table Table E-1 (Cont.) VMS Layered Products Currently Available for __________________VMS_Version_V5.5_______________________________ Most Recent Product_Name___________________________________Version___________ DEC RdbExpert for VMS 1.0 DEC Realtime Test Integrator for VMS 2.1 DEC Remote Operation Services (ROS) for VMS 1.0 DEC Remote Operation Services Development Kit 4.0 for VMS DEC Security Reporting Facility for VMS 1.1A DEC SecurityGate for VMS 1.0 DEC SoftPC for VMS 3.0 DEC TM32 Software for VMS 1.0 DEC TRELLIS Object System for VMS 1.0 DEC VUIT (Visual User Interface Tool) for VMS 2.0 Systems DEC WANrouter 100/500 1.0 DEC X25 Gateway 100/500 1.0 DEC/EDI 1.0 DECdecision 1.5 DECdesign 1.1 DECdx/VMS 1.2 DECelms (DEC Extended Lan Management 1.1 Software) DECfonts Typeface Collection for VMS and 1.1 ULTRIX DECforms 1.3 DECimage Application Services for VMS 3.0 DECimage Character Recognition Services for 1.0 VMS DECimage Scan Software for VMS 2.1 DECimage Storage Manager for VMS 1.0 DECinspect 2.1A (continued on next page) E-3 Layered Products Availability Table Table E-1 (Cont.) VMS Layered Products Currently Available for __________________VMS_Version_V5.5_______________________________ Most Recent Product_Name___________________________________Version___________ DECintact 2.0 DECmcc Basic Management System 1.1 DECmcc DECnet IV Diagnosis Functional Module 1.1 for VMS DECmcc Developers Toolkit 1.1 DECmcc Director 1.1 DECmcc Enterprise Management Station 2.1 DECmcc Extended LAN Manager AM 1.0 DECmcc Site Management Station 2.1 DECmcc TCP/IP SNMP Access Module for VMS 1.0 DECmcc WANdesigner 1.0 DECmessageQ for VMS 1.0 DECndu (Network Device Upgrade) Utility for 1.0 VMS DECnet-VAX Extensions 5.4 DECnet Router Server 1.2 DECnet/SNA Data Transfer Facility 3.0 DECnet/SNA Gateway 1.5 DECnet/SNA Gateway for Channel Transport 2.1 DECnet/SNA Gateway for Synchronous Transport 2.1 DECnet/SNA VMS 3270 Data Stream Programming 1.4 Interface DECnet/SNA VMS 3270 Terminal Emulator 1.5 DECnet/SNA VMS APPC/LU6.2 Programming 2.2 Interface DECnet/SNA VMS Application Programming 2.3 Interface DECnet/SNA VMS DISOSS Document Exchange 1.4 Facility (continued on next page) E-4 Layered Products Availability Table Table E-1 (Cont.) VMS Layered Products Currently Available for __________________VMS_Version_V5.5_______________________________ Most Recent Product_Name___________________________________Version___________ DECnet/SNA VMS Distributed Host Command 1.2 Facility DECnet/SNA VMS Gateway Management 2.1 DECnet/SNA VMS Printer Emulator 1.2 DECnet/SNA VMS Remote Job Entry 1.4 DEComni/VMS 1.1 DECpage 3.1 DECperformance Solution Accounting Chargeback 1.0 for VMS DECperformance Solution Capacity Planner for 1.0 VMS DECperformance Solution Data Collector for 1.0 VMS DECperformance Solution Performance Advisor 1.0 for VMS DECplan for VMS 1.0 DECplan Time Manager for VMS 1.0 DECpresent for VMS 1.0 DECprint Printing Services for VMS 4.1 DECprint Utility for Postscript to Sixel 1.0 Printing for VMS DECram for VMS 1.0 DECrouter 200 1.1 DECrouter 2000 1.2 DECrouter 250 1.1 DECscheduler for VMS 1.1A DECserver 100 for VMS and MicroVMS 2.0 DECserver 200 for VMS 3.1 DECserver 250 for VMS 2.0 (continued on next page) E-5 Layered Products Availability Table Table E-1 (Cont.) VMS Layered Products Currently Available for __________________VMS_Version_V5.5_______________________________ Most Recent Product_Name___________________________________Version___________ DECserver 300 for VMS 2.0 DECserver 500 for VMS 2.1 DECtalk Mail Access 1.1 DECtp DESKtop for ACMS 1.0 DECtrace for VMS 1.1 DECview 3D for VMS 2.1 DECvoice Software 2.0A DECwindows 4125 Emulator for VMS 1.0A DECwindows DECnet/SNA 3270 Terminal Emulator 1.0 for VMS DECwindows Developers Kit for VMS on OSF 1.1[1] /Motif DECwrite for VMS 1.1 DECxpress 100 VMS Client Software 3.0 Digital Cartridge Server Component for VMS 1.1 Digital Extended Math Library for VMS 1.0A DRB32 VMS Drivers 3.0 EDCS II 2.1 Ethernet Terminal Server for VMS and MicroVMS 3.0 External Document Exchange with IBM DISOSS 2.1 Fortran IV/VAX to RSX 2.8 IEX-VMS-Driver 4.2B Internet Portal 1.1 KMV1A MICROVAX Driver 2.5 KMV1A MICROVAX Driver and Development Tools 2.2 KMV1A MICROVAX Driver and X.25 Link Level 2.1A Software LAN Traffic Monitor for VMS 1.2 [1]See_VMS_Version_5.5_Release_Notes_for_additional_information._ (continued on next page) E-6 Layered Products Availability Table Table E-1 (Cont.) VMS Layered Products Currently Available for __________________VMS_Version_V5.5_______________________________ Most Recent Product_Name___________________________________Version___________ LCG01 Software 1.5 MICROVAX MIRA Switch Control 2.2 MICROVAX VSV21 Support Software 3.0 MICROVAX/DRQ3B Device Driver 1.3A MUXserver 100 Remote Terminal Server 2.3 MUXserver 300 Remote Terminal Server for VMS 1.2 NMCC/DECnet Monitor 2.3 NMCC/VAX ETHERnim 2.3 PATHWORKS for MACintosh 1.0A PATHWORKS for VMS 4.1 PBXserver 2.1 PDP-11 C for VMS 1.1 PDP-11 Datatrieve/VAX 3.3A PDP-11 FORTRAN-77/VAX to RSX 5.4 PDP-11 Symbolic Debugger/VAX to RSX 2.2 Powerframe for VMS 1.2 Remote System Manager 2.3 Session Support Utility 1.3 Terminal Server Manager 1.4 ULTRIX/SQL Remote Access to Rdb/VMS 1.0 VAX 2780/3780 Protocol Emulator 1.7 VAX 3271 Protocol Emulator 2.5 VAX ACMS 3.2 VAX Ada 2.2 VAX ADE 2.5 VAX APL 4.0[1] VAX BASIC 3.5 [1]See_VMS_Version_5.5_Release_Notes_for_additional_information._ (continued on next page) E-7 Layered Products Availability Table Table E-1 (Cont.) VMS Layered Products Currently Available for __________________VMS_Version_V5.5_______________________________ Most Recent Product_Name___________________________________Version___________ VAX BLISS-32 Implementation Language 4.6 VAX C 3.2 VAX CDD/Plus 4.3 VAX COBOL 4.4A VAX COBOL Generator 1.3 VAX Computer Integrated Telephony Message 1.0 Desk VAX CoProcessor/RSX 1.2 VAX Data Distributor 2.2 VAX Datatrieve 5.1 VAX DBMS 4.2A VAX DEC/CMS 3.4 VAX DEC/MAP 3.0A VAX DEC/MMS 2.6 VAX DEC/Shell 2.2 VAX DEC/Test Manager 3.2 VAX DECalc 4.0 VAX DECalc-Plus 4.0 VAX DECalc/DECgraph Package 4.0 VAX DECgraph 1.6 VAX Decision Expert for VMS 1.0B VAX DECrad 4.0 VAX DECScan VMS and ELN BITBUS Drivers 2.0 VAX DECscan VMS Software Toolkit 2.1 VAX DECslide 1.4 VAX DECspell/Verifier Corrector 1.1 VAX DIBOL 4.1A VAX Disk Striping Driver for VMS 2.0 (continued on next page) E-8 Layered Products Availability Table Table E-1 (Cont.) VMS Layered Products Currently Available for __________________VMS_Version_V5.5_______________________________ Most Recent Product_Name___________________________________Version___________ VAX Distributed File Service 1.2 VAX Distributed Name Service 1.1A VAX Distributed Queuing Service 1.2 VAX Document 2.0 VAX DSM 6.0A VAX DT07 3.0 VAX Encryption 1.2 VAX FMS 2.4 VAX FORTRAN 5.7 VAX FORTRAN High Performance Option 1.3 VAX FTAM 1.1 VAX Grammar Checker 1.0 VAX Image/3L Supporting Software for VMS 1.1 VAX ISDN 1.1 VAX ISDN Access 1.1 VAX ISDN Primary Access D Channel Interface 1.0 for VMS VAX Jukebox Control Software 1.0 VAX KCT32 2.1 VAX Key Distribution Center 1.2 VAX KMS11-BD/BE HDLC/BSC Framing Software 2.1 VAX KMS11-BD/BE X.25 Link Level Software 2.1 VAX Language Sensitive Editor/Source Code 3.1 Analyzer VAX LISP/VMS 3.1 VAX LN03 Image Support Software 1.0 VAX MAILGATE for MCI Mail 2.0 VAX Media Manager 1.0 (continued on next page) E-9 Layered Products Availability Table Table E-1 (Cont.) VMS Layered Products Currently Available for __________________VMS_Version_V5.5_______________________________ Most Recent Product_Name___________________________________Version___________ VAX Message Router 3.2 VAX Message Router X.400 Gateway 2.1B VAX Message Router/P Gateway 1.1B VAX Message Router/S Gateway 1.1B VAX Notes 2.2 VAX OPS5 3.0A VAX OSI Applications Kernel 1.1 VAX Packetnet System Interface 4.3 VAX Packetnet System Interface Access 4.3 VAX Pascal 4.2 VAX PCL 2.0 VAX Performance Advisor[2] VAX Performance and Coverage Analyzer 3.0 VAX PL/I 3.4 VAX PrintServer Client Software 3.0 VAX Public Access Communications 1.3A VAX Rally 2.3 VAX Rdb/VMS 4.0A VAX Real-time Accelerator Software 2.0A VAX ReGIS to Sixels Converter 1.0 VAX Remote Environmental Monitoring Software 1.3 VAX Scan 1.2 VAX Software Performance Monitor 3.4 VAX Software Project Manager 1.2 VAX Storage Library System 2.1 VAX TDMS 1.9A [2]VAX_Performance_Advisor_has_been_replaced_by_the______________ DECperformance Solution family of products. (continued on next page) E-10 Layered Products Availability Table Table E-1 (Cont.) VMS Layered Products Currently Available for __________________VMS_Version_V5.5_______________________________ Most Recent Product_Name___________________________________Version___________ VAX Teamdata 1.4 VAX TU70/72 Device Driver 1.2[1] VAX Vertical Forms Printing for VMS 1.0 VAX VTX 4.1 VAX Wide Area Network Device Drivers 1.1B VAX XWAY 1.2 VAX-11 RSX 2.5 VAXcamera for VMS 1.0 VAXcluster Console System 1.3 VAXELN Ada 2.2 VAXELN KAV Toolkit Extensions for VMS 1.0 VAXELN Toolkit 4.2 VAXft System Services 1.2 VAXlink for IMS and VSAM Client 1.1 VAXset Package 10.0 VIDA for DB2 1.0A VMS DECwindows Motif 1.0 VMS Workstation Software 4.3 VMS/SNA 2.1 VMS/ULTRIX Connection 1.3A WPS-PLUS/VMS 4.0 X25Portal 2000 1.0 X25Router 2000 1.1 [1]See_VMS_Version_5.5_Release_Notes_for_additional_information._ _________________________________________________________________ E-11 _________________________________________________________________ Glossary boot, bootstrap The process of loading system software into a processor's main memory. This guide uses the term boot to refer to this process. boot command procedure A program, stored on the console fixed disk, that is used to boot the VMS operating system from a specified controller. Digital provides a boot command procedure for each controller that the processor supports. boot name The abbreviated name of the boot command procedure you use to boot the system. boot server A VAX computer that is part of a local area VAXcluster. The boot server is a combination of a MOP server and a disk server for the satellite system disk. See also satellite node. CI-only VAXcluster A computer system consisting of a number of VAX computers. It uses only the computer interconnect (CI) to communicate with other VAX computers in the cluster. These computers share a single file system. computer interconnect (CI) A type of I/O subsystem. It links VAX computers to each other and to HSC devices. See also Hierarchical Storage Controller (HSC) device. Glossary-1 DECW$TAILOR A software program that lets you add or remove DECwindows files from your system disk. device name The name used to identify a device on the system. A device name indicates the device code, controller designation, and unit number. disk server A VAX computer that is part of a local area VAXcluster. This computer provides an access path to CI, CSSI, and locally-connected disks for other computers that do not have a direct connection. Hierarchical Storage Controller (HSC) device A self-contained, intelligent, mass storage subsystem that lets VAX computers in a VAXcluster environment share disks. Examples are the HSC50 and the HSC70. HSC drive Any disk or tape drive connected to an HSC device is called an HSC drive. A system disk on an HSC drive can be shared by several VAX computers in a VAXcluster environment. local area VAXcluster A configuration consisting of one or more VAX computers that act as a MOP server and disk server, and a number of low-end VAX computers that act as satellite nodes. The local area network (LAN) connects all of the computers. These computers share a single file system. local drive Any drive that is connected directly to a VAX computer. media Any packaging agent capable of storing computer software. Examples: compact discs, magnetic tapes, floppy diskettes, disk packs, tape cartridges. Glossary-2 mixed-interconnect VAXcluster A computer system consisting of a number of VAX computers. It uses both the computer interconnect (CI) and Ethernet to communicate with other VAX computers in the cluster. These computers share a single file system. MOP server A computer system running DECnet that downline loads VAXcluster satellites using the DECnet MOP protocol. satellite node A VAX computer that is part of a local area VAXcluster. A satellite node is downline loaded from a MOP server and then boots remotely from the system disk served by a disk server in the local area VAXcluster. See also boot server, disk server, MOP server. save set The format in which the Backup Utility stores files. The VMS operating system is shipped in this format. scratch disk A blank disk or a disk with files you no longer need. source drive The drive that holds the distribution kit during an upgrade or installation. spin up, spin down To spin up means to bring a disk drive up to operating speed; to spin down means to bring it to a gradual stop. standalone BACKUP A subset of the BACKUP Utility that is booted into main memory instead of running under the control of the VMS operating system. Standalone BACKUP is used to back up and restore the system disk and to install VMS operating system software. standalone system A computer system with only one VAX computer. Glossary-3 system disk The disk that contains or will contain the VMS operating system. A VMS system disk is set up so that most of the VMS files can be shared by several VAX computers. In addition, each computer has its own directory on the system disk that contains its page, swap, and dump files. target drive The drive that holds the system disk during an upgrade or installation. 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. VMS User Environment Test Package (UETP) A software package that tests all the standard peripheral devices on your system, various commands and operating system functions, the system's multiuser capability, DECnet-VAX, and the VAXcluster environment. VMSTAILOR A software program that lets you add or remove optional VMS files from your system disk. Glossary-4 _________________________________________________________________ Index A AUTOGEN, 4-11 _______________________________ feedback data, 6-4 Account running after an installation disabling during installation , 4-11 , 3-22 running after an upgrade, setting up after an 9-22 installation, 4-4 running at end of Accounting logs installation, 3-29 effect of upgrade on, 5-4 running at end of upgrade, Ada 8-28 compiling source files, 11-13 running before an upgrade, programming interfaces, 11-13 6-4 AGEN$PARAMS.REPORT, 4-11 AUTOGEN.PAR Allocation class creation of, 8-23 See also ALLOCLASS parameter Automatic restart determining, 2-5 for upgrade, 6-11 ALLOCLASS parameter, 2-5 supplying during VAXcluster B______________________________ installation, 3-18 Backing up the system disk, ANALYZE/DISK_STRUCTURE utility 4-11, 9-22 error message, 6-7 BACKUP command using before an upgrade, 6-7 using to create a system Applications files for VMS disk, 3-5 DECwindows, 8-15 Backup procedures Applying the mandatory update, before an upgrade, 6-5 8-23 Batch and print queuing system See Queuing system Index-1 Batch queues Command procedures See Queues checking after upgrade, 9-4 Boot command procedures Compact disc drive See DEFBOO; dddGEN supported by UETP, 10-9 Booting Computer-specific installation from [SYSF], B-1 to B-8 instructions, 3-1 manually during upgrade Concurrent upgrade procedure, 8-11 description, 7-1 with InfoServer ISL file, 3-3 preupgrade procedure, 7-2 Bugcheck message procedure, 7-2 to 7-3 during UETP, 10-41 setting QUORUM parameter, 7-2 Building standalone BACKUP, summary, 7-2 4-3 CONSCOPY.COM procedure, 6-5 Console connecting with SYSGEN, 9-12 C______________________________ Console media Checklist automatic update during postinstallation, 4-1 upgrade, 6-5 postupgrade, 9-1 backing up after an upgrade, preinstallation, 2-1 9-22 preupgrade, 6-1 backing up before an upgrade, Choosing a windowing system, 6-5 3-20 booting from during an CI-only VAXcluster upgrade, 8-10 information needed to install copying, 6-5 , 2-5 modifying for automatic installation questions, 3-18 restart, 6-11 Cluster modifying to boot from [SYSF] See VAXcluster , 8-10 Cluster group number required for an installation, rules for creating, 2-6 2-2 Cluster password required for an upgrade, 5-6 rules for creating, 2-6 restoring original boot Cluster upgrade command procedures, 8-22 See Concurrent upgrade updating after an upgrade, See Rolling upgrade 9-11 CLUSTER_SIZE parameter using backup copy, 6-5 of system disk, 3-7 Index-2 Console report during UETP, DECnet-VAX (cont'd) 10-19 running with VMS DECwindows, Creating a system disk, 3-5 4-5 from InfoServer, 3-9 security measures, 9-6 Creating a transaction log UETP test of, 10-50 file, 4-5, 9-5 UETP test phase, 10-49 CTRLNAME logical name, 10-12, DECnet-VAX license 10-44 registering after Customizing the system, 4-3 installation, 4-2 registering during an upgrade D______________________________ , 8-27 Date registering during format for entering, 8-8 installation, 3-27 dddGEN Decompressing system libraries restoring original version, , 4-6, 9-14 8-22 Decompressing the system DECdtm services, 4-5, 9-4 messages help library, 4-8, disabling, 4-6, 9-5 9-16 DECnet DECW$BOOK logical name, 11-3 UETP defaults for DECW$IGNORE_DECNET logical installation, 10-41 name, 4-5 DECnet node address, 2-5 DECW$IGNORE_DECWINDOWS logical providing during installation name, 11-2 , 3-18 DECW$MOTIF_TAILOR DECnet node name, 2-5 using to remove files from a possible values, 3-18 system disk, 9-17 providing during installation DECW$TAILOR , 3-18 using to remove files from DECnet-VAX a system disk, 4-9, 9-17, configuration database, 9-6 12-10, 12-11 configuring after an DECwindows installation, 4-4 See VMS DECwindows error message during UETP, DEFBOO 10-38 restoring original version, ignoring during startup, 4-5 8-22 preparing for UETP, 10-15 Device preparing for upgrade, 6-11 format for upgrade, 8-6 requirement for upgrade, 6-11 Index-3 Device (cont'd) Disk space (cont'd) HSC name format for upgrade, amount needed to decompress 8-6 system libraries, 4-6 Device names amount needed to run UETP, determining, 2-6, 3-6 4-6 Devices increasing the amount on the configuring before upgrade, system disk, 9-17 8-3 Distribution kit Device support files for VMS magnetic tapes in, 3-5 DECwindows, 8-15 save sets in, 3-5 Device support files for VMS Standalone BACKUP, 3-3 DECwindows Motif, 8-17 TK50 tape cartridges in, 3-3 Device test (in UETP) VMS, 3-5 running individually, 10-44 VMS DECwindows, 3-3 Diagnostics with multiple volumes, 3-3, relationship to UETP, 10-22 8-19 Digital Small Storage Distribution media, 2-3 Interconnect (DSSI) disks location during upgrade, 5-4 device name change, 3-2 Dump file Directories checking size, 9-3 user, processed during modifying size, 9-3 upgrade, 8-21 purged during upgrade, 8-18 Directory trees requirement for upgrade, 6-7 merged by upgrade procedure, shared, 5-4, 6-7 8-21 Disabling network objects, 9-6 E______________________________ Disabling the TP_SERVER Editing startup files, 4-3 process, 4-6, 9-5 Enabling automatic restart, Disk 6-11 See System disk, User disk Enabling manual reboot, 6-11 Disk space Error during installation amount needed for upgrade, LICENSE, 3-8 6-9 Error during UETP, 10-27 amount needed to decompress diagnosing, 10-22 help library, 4-8, 9-16 sources of, 10-23 amount needed to decompress Error during upgrade libraries, 9-14 cluster hang during shutdown, 7-6 Index-4 Error during upgrade (cont'd) during console update, 9-12 H______________________________ LIBRAR facility, 8-21 Hang while entering device code, See System hang 8-6 Help Error formatter (ERRFMT) setting up and decompressing, stopped during upgrade, 8-10 4-7, 9-15 Error Log Utility Hierarchical Storage relationship to UETP, 10-3, Controller 10-22, 10-39 See HSC (Hierarchical Storage Error running ANALYZE/DISK_ STRUCTURE, 6-7 Controller) Ethernet HLP$LIBRARY logical name, 4-7, defining a remote node for 9-15 UETP, 10-25 HSC (Hierarchical Storage preparing for UETP, 10-10 Controller) Example files for VMS device format for an DECwindows, 8-16 installation, 3-6 EXPECTED_VOTES device format for upgrade, parameter, 9-6 8-6 setting for rolling upgrade, displaying name, 2-6 7-6 drive, 2-3 if drive is connected to, 3-6 F______________________________ name, 3-6 Factory installed software, ix I FAL (File Access Listener) _______________________________ object InfoServer enabling or disabling, 9-8 booting Standalone BACKUP, Feedback data 3-3 checking before an upgrade, creating system disk, 3-9 6-4 Initial software load (ISL) FIELD account booting, 3-3 setting password, 3-21 Installation FILLM quota See Postinstallation tasks, checked during upgrade Preinstallation tasks, procedure, 8-10 Installation procedure FIS, ix booting standalone BACKUP, 3-3 Index-5 Installation (cont'd) Installing VMS on a VAXcluster booting system disk after , 3-17 transferring required save Interrupt set, 3-8 upgrade before Phase 1, 8-8 cautions and restrictions, IRPCOUNT parameter 3-2 requirement for upgrade, 8-5 choosing optional VMS K DECwindows components, _______________________________ 3-13 Keyboard layout, 11-4 computer-specific customizing, 11-5 instructions, 3-1 list of, 11-5 information needed for Keyboard model number, 11-5 VAXcluster, 2-4 Keymap name of layered products, 4-11 determining, 11-5 preparing for, 2-4 KFQSA controller rebooting system, 3-30 upgrade requirement, 6-10 recording, 2-4 registering licenses, 3-24 L______________________________ registering VMS license, 3-30 Layered products specifying VAXcluster effect of upgrade on, 5-6 configuration, 3-17 installing after VMS warning about VMSINSTAL installation, 4-11 option G, 3-2 supported versions, E-1 Installation instructions, 3-1 LIBDECOMP.COM (procedure to Installation procedure, 1-1 decompress system libraries) choosing optional VMS , 4-7 components, 3-11 running after an upgrade, running AUTOGEN, 3-29 9-14 setting passwords, 3-21 Librarian Utility stages of, 3-1 See VMS Librarian Utility when to use, 1-2 Libraries Installing optional components decompressing after an , 3-10 installation, 4-6 Installing the VMS operating Library save set system, 3-1 contents, C-1 Installing VMS DECwindows, installing, 3-11 3-12 instructions, 3-15 Index-6 LICENSE (License Management LOADS logical name, 10-48 Utility) Load test activity definition, 3-26 defining user load for UETP, error messages, 3-26 10-18 example of registration, A-2 description, 10-48 license registration error during UETP, 10-36 procedure, A-1 running individually, 10-17 License Management Facility Local Area VAXcluster See LMF information needed to install License Management Utility , 2-5 See LICENSE installation questions, 3-19 using during installation, upgrade requirement, 5-5 3-25 Local drive, 2-3 Licenses Log See also Product keeping of installation, 2-4 keeping of upgrade, 6-1 Authorization Key (PAK) Log file generated by UETP error messages, 3-8 See also UETP.LOG file registering after during the load test, 10-37 installation, 4-2 NETSERVER.LOG, 10-36 registering during an upgrade OLDUETP.LOG, 10-27 , 8-27 Logical names registering during VMS for VMS DECwindows, 11-2 installation, 3-24 Logical name used by UETP License Unit Requirement Table CTRLNAME, 10-44 (LURT), A-3 LOADS, 10-48 Line printer SYS$INPUT, 10-43 preparing for UETP, 10-2, SYS$OUTPUT, 10-46 10-6, 10-10 Long report format UETP output, 10-46 See Console report during UETP test image, 10-47 UETP UETP test of, 10-43 LRPCOUNT parameter LMF (License Management requirement for upgrade, 8-5 Facility) system integrated product licenses, A-10 VMS Volume Shadowing software , A-9 Index-7 Mixed-interconnect VAXcluster M______________________________ (cont'd) Magnetic tape upgrade requirement, 5-5 preparing for UETP, 10-2, Mixed-version cluster 10-5, 10-8 upgrading to, 7-5 to 7-8 test of, 10-43, 10-46 MODE, 10-54 UETP test image, 10-47 MODE logical name, 10-23 Magnetic tape kit MODPARAMS.DAT (parameter file) description of contents, 3-5 , 4-11 MAIL object entering parameters in, 6-10 enabling or disabling, 9-8 modifying for cluster, 9-6 Mandatory update modifying for single system, applying during installation, 4-10, 9-6, 9-19, 9-20 3-23 Monochrome workstation, 11-5 applying during upgrade, 8-23 Motif Manual boot See VMS DECwindows Motif after running AUTOGEN, 8-28 during upgrade procedure, N 8-11, 8-22 _______________________________ enabling for upgrade, 6-11 NETCONFIG.COM procedure Master command procedure running after an installation See UETP.COM , 4-4 Messages NETCONFIG_UPDATE.COM procedure online help for, 4-7, 9-15 example, 9-7 Micro/VAX computers running, 9-6 booting from [SYS0], 8-22 Network booting from [SYSF], 8-18, See also DECnet-VAX B-1 requirement for upgrade, 6-11 Minimum startup restriction on upgrade, 5-3 configuring devices after, Network objects 8-3 disabling, 9-6 setting before upgrade, 6-9 Network security MIRROR object updating after an upgrade, enabling or disabling, 9-9 9-6 Mixed-interconnect VAXcluster NML (Network Management information needed to install Listener) object , 2-5 enabling or disabling, 9-9 installation questions, 3-19 NOMOVE attribute during install, 3-28 Index-8 NOMOVE attribute (cont'd) during upgrade, 8-27 P______________________________ NOMOVE files Page file additional system disks, 4-3, checking size, 6-8, 9-3 9-2 modifying size, 6-8, 9-3 during installation, 3-29 purged during upgrade, 8-18 during upgrade, 8-28 required location, 6-7 NPAGEDYN parameter size required for upgrade, requirement for upgrade, 8-5 6-8 PAK O______________________________ See Product Authorization Key OLDUETP.LOG file, 10-26 (PAK) Online help Password for system messages, 4-7, forgotten, 3-31, 8-30 9-15 generating for default DECnet OPCOM account, 9-6 stopped during upgrade, 8-10 minimum length, 3-21 Operator logs modifying during upgrade effect of upgrade on, 5-4 procedure, 8-9 Optional components requirements, 8-9 selecting during installation setting during installation, procedure, 3-10 3-21 selecting during upgrade Phase 1 of upgrade procedure, procedure, 8-12 8-8 Optional save set Phase 2 of upgrade procedure, contents, C-2 8-19 installing, 3-11 Phase 3 of upgrade procedure, upgrading, 8-12 8-21 Output Phase 4 of upgrade procedure, saving from installation, 2-4 8-22 saving from upgrade, 6-1 Phase 5 of upgrade procedure, Output during UETP 8-23 terminal and line printer, Phase 6 of upgrade procedure, 10-46 8-23 Phase controller for UETP See UETPHAS00.EXE Index-9 PHONE object Postupgrade tasks (cont'd) enabling or disabling, 9-9 checking system file sizes, Postinstallation tasks, 4-1 9-3 adjusting system parameters, creating standalone BACKUP, 4-4 9-22 backing up the system disk, customizing VMS DECwindows, 4-3, 4-11 9-18, 11-2 configuring DECnet-VAX, 4-4 decompressing system creating standalone BACKUP, libraries, 9-14 4-3 examining command procedure customizing the system, 4-3 templates, 9-4 customizing VMS DECwindows, increasing space on the 11-1 system disk, 9-17 decompressing system modifying size of dump file, libraries, 4-6 9-3 editing startup procedures, modifying size of page file, 4-4 9-3 installing layered products, modifying size of swap file, 4-11 9-3 registering licenses, 4-2 purging system files, 9-17 removing unwanted system replacing SYSUAF.DAT, 9-2 files, 4-9 running AUTOGEN, 9-22 setting up the system running NET_CONFIG_UPDATE.COM messages help library, , 9-6 4-7 running UETP, 9-16 setting up user accounts, 4-4 running UPDATE_CLUSTER_ testing the system with UETP, MEMBERS.COM, 9-10 4-6 setting up the system tuning the system with messages help library, AUTOGEN, 4-11 9-15 Postupgrade tasks updating console media, 9-11 adding and removing files, updating network 9-17 configuration database, backing up console media, 9-6 9-22 updating network security backing up system disk, 9-22 environment, 9-6 changing MODPARAMS.DAT, 9-6 using VMSTAILOR and DECW$TAILOR, 9-17 Index-10 Preinstallation tasks, 2-4 Product Authorization Key collecting information you (PAK), 3-25 will need, 2-7 registering after an determining HSC name, 2-6 installation, 4-2 preparing for a VAXcluster registering during an environment, 2-4 installation, 3-24 preparing tape drives, 2-6 registering during Preupgrade tasks installation, 3-25 analyzing and repairing registering during upgrade, system disk, 6-7 8-27 backing up console media, 6-5 Products (VMSINSTAL) backing up system disk, 6-5 specification for upgrade, checking page file size, 6-8 8-7 configuring devices, 8-3 Programming Support for VMS creating standalone BACKUP, DECwindows, 8-15 6-6 PURGE command, 9-18 preparing DECnet-VAX, 6-11 Purging system files, 9-17 preparing system disk, 6-6 preventing interactive logins Q______________________________ , 6-11 Queue manager running AUTOGEN, 6-4 after installation, 4-9 setting system parameters, cluster upgrade, 9-20 6-9 restrictions, 5-5 stopping queues, 6-12 standalone upgrade, 4-10, Print Dialog Box 9-19 logical names, 11-12 starting, 9-18 Printer upgrades, 9-18 recording installation on, Queues 2-4 batch/print, 5-5, 9-18 recording upgrade on, 6-1 in rolling upgrade, 7-5 Print formats starting, 4-9 defining for VMS DECwindows, stopping, 6-12 11-12 requirement for upgrade, 6-11 Print queue stopping before upgrade, 6-12 See also Queues Queuing system associating with a print in mixed version VAXclusters, format, 11-12 7-5 Privilege required for UETP, 10-30 Index-11 Quorum RMS Journaling See also VAXcluster quorum registering during an upgrade maintaining during rolling , 8-27 upgrade, 7-6 RMS Journaling license Quorum disk registering after choosing during VAXcluster installation, 4-2 installation, 3-18 registering during QUORUM parameter installation, 3-27 setting for concurrent Rolling upgrade upgrade, 7-2 batch/print functionality, Quotas 7-5 checked during upgrade description, 7-1 procedure, 8-10 effect on SYSUAF.DAT, 6-7, required to run UETP, 10-30 9-2 maintaining cluster quorum, R______________________________ 7-6 Reboot procedure, 7-5 after installation, 3-30 required patch, 7-3 manual, 6-11 restriction, 7-3 Recording an installation, 2-4 source drive requirement, 7-6 Recording an upgrade, 6-1 VMS version requirement, 5-2 Removing unwanted system files VMS version restrictions, 7-4 , 4-9 RV60 optical disk drive Required save set supported by UETP, 10-9 transferring to system disk, S 3-6 _______________________________ Restart Satellites nodes enabling automatic, 6-11 upgrade requirement, 5-5 Restrictions SCSNODE parameter, 4-10, 6-9, for rolling upgrade, 7-3 9-19, 9-20 for VMS installation, 3-2 SCSSYSTEMID parameter, 4-10, for VMS upgrade, 5-3 6-9, 9-19, 9-20 Rights database Security creating during installation, updating after an upgrade, 3-22 9-6 RIGHTSLIST.DAT Selecting a disk or tape drive creating during installation, , 2-6 3-22 Index-12 Selecting optional components, Standalone BACKUP (cont'd) 8-12 on multiple volumes, 3-3 Server tape cartridge containing, customizing the VMS 3-3 DECwindows, 11-3 upgrade requirement, 6-6 Setting passwords during an Standalone BACKUP media installation, 3-21 loading, 3-3 Shadowed system disk Startup files upgrade restriction, 5-4 editing after an installation Short report format , 4-3 See Console report during STARTUP_P1 parameter UETP requirement for upgrade, 6-9 Shutdown Swap file after installation, 3-30 checking size, 9-3 before an upgrade, 6-6 creating, 6-8 Site-specific command modifying size, 9-3 procedures purged during upgrade, 8-18 restored during upgrade, required loction, 6-7 8-26, 9-4 SWAPFILES.COM procedure Source drive executing to change system requirement for VAXcluster file sizes, 9-3 upgrade, 7-6 to check or modify page file Source-drive, 3-2 size, 6-8 definition, 8-3 to create swap file, 6-8 SRPCOUNT parameter SYCONFIG.COM procedure requirement for upgrade, 8-5 editing after an installation STABACKIT.COM (procedure to , 4-4 create standalone BACKUP), SYLOGICALS.COM procedure 6-6 before an upgrade, 5-5 Standalone BACKUP editing after an installation booting to begin an , 4-4 installation, 3-3 SYLOGIN.COM procedure creating after an upgrade, editing after an installation 9-22 , 4-4 creating a kit, 4-3 SYS$INPUT logical name, 10-43 creating before an upgrade, SYS$OUTPUT logical name, 10-46 6-6 SYS$TEST logical name, 10-5, InfoServer containing, 3-3 10-14, 10-26 Index-13 [SYSF] directory System disk (cont'd) booting from during upgrade, backing up, 9-22 8-2, 8-18, B-1 backing up after an command to boot Micro/VAX and installation, 4-11 VAXstation computers from, backing up before an upgrade, 8-18 6-5 [SYSF] directory tree booting after installation, built by upgrade procedure, 3-30 8-11 booting after transferring deletion of, 8-23 required save set, 3-8 SYSGEN checking amount of free space configuring devices, 8-3 on, 4-6 parameter reqirements for CLUSTER_SIZE parameter, 3-7 queue manager upgrade, creating, 3-5 4-10, 9-19, 9-20 devices no longer supported, parameter reqirements for 3-2, 8-1 upgrade, 6-9 disk space needed to run parameter requirements for UETP, 4-6, 10-6 upgrade, 5-3, 6-9, 8-5 free space needed for upgrade using to connect console, , 6-9 9-12 free space needed to SYSTARTUP_V5.COM procedure decompress libraries, editing after an installation 4-6 , 4-4 preparing for a VMS editing to control DECnet-VAX installation, 2-7 , 4-5 preparing for a VMS upgrade, System 6-6 customizing, 4-3 removing unwanted files from, logging into for UETP, 10-1, 4-9 10-4 required location during resource requirements for upgrade, 8-22 UETP, 10-2, 10-4 restrictions, 1-1 SYSTEM account specifying volume label for, forgotten password, 3-31, 3-9 8-30 test error during UETP, setting password, 3-21 10-32, 10-33 System disk, 2-3 UETP test image, 10-47 analyzing and repairing, 6-7 UETP test of, 10-46 Index-14 System disk (cont'd) SYSTEST directory (cont'd) unique volume label function during UETP, 10-5 requirement, 6-5 SYSTEST_CLIG account using DECW$TAILOR to disabling during installation customize, 4-9, 9-17, , 3-21 12-10, 12-11 reenabling for UETP, 10-13 using VMSTAILOR to customize, requirements for UETP, 10-13, 4-9, 9-17, 12-1 10-53 volume shadowing restriction, SYSUAF.DAT (User Authorization 5-4 File) System files effect of rolling upgrade on, purging, 9-17 6-7, 9-2 System Generation Utility replacing after upgrade, 9-2 (SYSGEN) required location, 6-7 ALLOCLASS parameter, 2-5 SCSNODE parameter, 4-10, 6-9, T______________________________ 9-19, 9-20 Tailored system disk SCSSYSTEMID parameter, 4-10, See DECW$MOTIF_TAILOR 6-9, 9-19, 9-20 See DECW$TAILOR System hang, 8-29, 10-28, See VMSTAILOR 10-40 Tape cartridge System messages containing standalone BACKUP, accessing with online help, 3-3 4-7, 9-15 containing VMS DECwindows System parameters save sets, 3-3 generated by AUTOGEN feedback containing VMS save sets, 3-5 , 6-4 Tape cartridge drive requirement for upgrade, 6-9 preparing for UETP, 10-8 SYSTEST account Tape drive logging into for UETP, 10-1, preparing for installation, 10-4 2-6 privileges required for UETP, Target disk 10-30 using backup copy for, 6-5 quotas required to run UETP, Target-drive, 3-2 10-30 definition, 8-3 setting password, 3-21 TASK object SYSTEST directory enabling or disabling, 9-8 creating for UETP, 10-7 Index-15 TCP/IP software UETP use with DECwindows, 11-10 See User Environment Test Terminal Package preparing for UETP, 10-2, UETP$NODE_ADDRESS logical 10-6, 10-10, 10-18 name, 10-15 simulating users for UETP, UETP (User Environment Test 10-48 Package) test of, 10-43 DECnet installation defaults, UETP output, 10-46 10-41 UETP test image, 10-47 RRD40 and RRD50 compact disc UETP test of, 10-46 drive, 10-9 Time RV60 optical disk drive, 10-9 format for entering, 8-8 TLZ04 tape drive, 10-9 TLZ04 tape drive UETP.COM file, 10-42 supported by UETP, 10-9 termination of, 10-20 TP_SERVER process UETP.LOG file, 10-19, 10-26, disabling, 4-6, 9-5 10-39, 10-49 Transaction log file UETPHAS00.EXE program, 10-42, creating, 4-5, 9-5 10-43 Transferring VMS save sets to UETUNAS00.EXE UETP test image, system disk, 3-5 10-25 Troubleshooting UETP, 10-27 UIC See User Identification Code U______________________________ Unsupported system disks, 3-2, UETCONT00.DAT file, 10-43 8-1 creation of, 10-43 Unsupported VAX computers, UETINIDEV.DAT file, 10-42, 3-2, 8-1 10-45 UPDATE_CLUSTER_MEMBERS.COM creation of, 10-43 procedure format, 10-45 running, 9-10 UETININET.DAT, 10-51 UPDATE_CONSOLE.COM procedure UETININET.DAT file, 10-51 running after an upgrade, UETINIT00.EXE image, 10-42 9-14 UETINIT01.EXE image, 10-28, Upgrade 10-42 See also Postupgrade tasks, UETLOAD00.DAT, 10-48 Preupgrade tasks, Upgrade UETNETS00.EXE, 10-51 procedure Index-16 Upgrade (cont'd) Upgrade (cont'd) automatic update of console shared dump file, 5-4 media, 6-5 using VMSINSTAL options G, cautions and restrictions, 5-4 5-3 VMS version requirement, 5-2 concurrent upgrade, 7-2 Upgrade procedure, 1-3 console media required, 5-6 applying mandatory update, disk space needed for page 8-23 file, 6-8 booting from console media, disk space requirement, 6-9 8-10 effect on accounting logs, booting from [SYSF], 8-18 5-4 booting manually during, 8-11 effect on layered products, building [SYSF] directory, 5-6 8-11 effect on operator logs, 5-4 conversion of VAXVMSSYS.PAR, enabling automatic restart, 8-23 6-11 correcting directory pointers enabling manual reboot, 6-11 , 8-22 error entering device code, deletion of [SYSF] directory 8-6 tree, 8-23 files purged during, 8-18 effect on command procedures, interrupting before Phase 1, 9-4 8-8 effect on MODPARAMS.DAT, 9-6 license requirements, 8-27 files deleted by, 8-11, 8-21, maintaining a secure 8-23 enviroment, 5-1 loading VMS DECwindows modifying console media, 6-11 distribution media, 8-20 procedure, 8-3 to 8-30 loading VMS distribution recording, 6-1 media, 8-3 required location of VMS save manual reboot after, 8-28 sets, 5-4 manual reboot from [SYS0], requirement for shared dump 8-22 file, 6-7 merging directory trees, 8-21 requirements, 6-1 modifying console media to rolling upgrade, 7-4 boot from [SYSF], 8-10 adding a new CPU, 7-7 modifying passwords, 8-9 required patch, 7-3 Phase 1, 8-8 restriction, 7-3 Phase 2, 8-19 Index-17 Upgrade procedure (cont'd) User Environment Test Package Phase 3, 8-21 (UETP) Phase 4, 8-22 aborting execution of, 10-20 Phase 5, 8-23 description of, 10-1 Phase 6, 8-23 disk space needed to run, 4-6 processing user files, 8-21 displaying tests as they run, registering licenses, 8-27 10-23 removing VMS DECwindows initialization phase, 10-42 distribution media, 8-21 interpreting output of, 10-22 removing VMS distribution master command procedure, media, 8-20 10-42 required location of system normal completion of, 10-20 disk, 8-22 organization of, 10-42 restoring original dddGEN, required privileges, 10-30 8-22 required quotas, 10-30 restoring original DEFBOO, requirements for small disk 8-22 systems, 10-15 restrictions, 1-4 running all phases of, 10-3 running AUTOGEN, 8-28 running individual phase of, security check, 8-23 10-17 selecting optional components running multiple passes of, , 8-12 10-18, 10-26 selecting VMS DECwindows, starting, 10-17 8-13 typical failures reported by, User Authorization File (UAF) 10-28 effect of rolling upgrade on, when to run, 4-6, 9-16 6-7, 9-2 User Environment Test purged during upgrade, 8-18 Package(UETP) replacing after upgrade, 9-2 testing the VAX Vector required location, 6-7 Instruction, 10-16 User disk testing vector processors, preparing for UETP, 10-2, 10-16 10-7 User files space requirements for UETP, processed during upgrade, 10-6 8-21 test error during UETP, 10-32 User Identification Code (UIC) UETP test image, 10-47 for UETP, 10-7 UETP test of, 10-46 User load Index-18 User load (cont'd) VAXcluster installation defined for UETP DECnet-VAX (cont'd) test, 10-51 supplying ALLOCLASS parameter defining for the UETP load , 3-18 test, 10-18 VAXcluster license equation used to determine registering after for UETP load test, 10-24 installation, 4-2 registering during V______________________________ installation, 3-27 VAX C registering during upgrade, example programs, 11-2 8-27 extracting definition files, requirement, 3-17 11-2 VAXcluster quorum VAXcluster maintaining during rolling See also Cluster group upgrade, 7-6 number, Cluster password maintaining during upgrade, building, 4-3 8-29 information required for VMS VAXcluster QUORUM parameter installation, 2-4 setting for concurrent label for system disk, 6-5 upgrade, 7-2 preparing for UETP, 10-14 VAXcluster upgrade problem upgrading, 8-29 See Concurrent upgrade test failure during UETP, See Rolling upgrade 10-35 VAX computers types, 2-5 booting from [SYSF], B-1 to upgrade requirement for B-8 shared dump file, 6-7 no longer supported, 3-2, 8-1 VAXcluster installation, 3-17 VAX computers, VMS support choosing quorum disk, 3-18 for, A-2 choosing VAXcluster cluster VAXft computers type, 3-17 booting from [SYSF], B-1 CI-only VAXcluster, 3-18 VAXstation computers configuring the cluster, 3-17 booting from [SYS0], 8-22 local area VAXcluster, 3-19 booting from [SYSF], 8-18, Mixed Interconnect VAXcluster B-1 , 3-19 suggested answers to questions, 3-17 Index-19 VAX Vector Instruction VMS DECwindows (cont'd) Emulation Facility (VVIEF), installing selected portions, 10-16 8-14 VAXVMSRL055 installing the complete kit, default volume label, 3-9 8-14 VAXVMSSYS.PAR parameter files logical names, 11-2 conversion, 8-23 optional components, 8-12 Video font files for VMS programming support, 8-15 DECwindows, 8-15, 8-17 selecting during upgrade VMB.EXE procedure, 8-13 copying to console media, starting, 4-9 9-11 transports, 11-10 VMS upgrading, 8-13 optional components, 8-12 using customer-written VMS DECwindows transports, 11-10 applications, 8-15 video fonts, 8-15, 8-17 automatic startup, 11-2 VMS DECwindows distribution C example programs, 11-2 media choosing options during an loading, 3-15, 8-20 installation, 3-13, 8-14 removing from drive, 3-5, compiling Ada software, 11-13 3-16, 8-21 components, 3-14 VMS DECwindows Motif controlling startup, 11-1 See also VMS DECwindows Motif customizing, 4-9, 9-18, 11-1 Installation Guide customizing after an components, 8-16 installation, 4-9 device support, 8-17 customizing after an upgrade, installing, 8-14, 8-16 9-18 tailoring, 9-17 customizing the server, 11-3 VMS DECwindows options defining print formats, 11-12 applications, 3-14 device support, 8-15 device support, 3-13 example files, 8-16 examples, 3-14 files, D-1 programming support, 3-14 if you choose not to upgrade, video fonts, 3-14 8-13 VMS DECwindows save sets installing, 3-12, 3-14, 8-14 location on magnetic tape, installing during the upgrade 3-5 procedure, 8-13 Index-20 VMS DECwindows save sets VMSTAILOR (cont'd) using to install optional tape cartridge containing, components, 3-11, 12-5 3-3 using to remove files from VMS distribution media a system disk, 4-9, 9-17, loading, 3-6, 8-3 12-3 multiple volumes, 8-3 VMS/ULTRIX Connection software removing from drive, 3-15, (UCX) 8-20 function, 11-10 VMSINSTAL VMS Upgrade invoke for upgrade, 8-4 See Upgrade option G, 3-2 VMS upgrade and installation VMS Librarian Utility supplements using to set up online help, using, 2-4, 3-1 4-8, 9-16 VMS version required, for VMS library files upgrade, 5-2 selecting during upgrade, VMS versions 8-13 computer support, A-2 VMS library save set Volume label contents, C-1 requirement for VAXclusters, VMS license 6-5 registering after specifying, 3-9 installation, 4-2 Volume Shadowing registering during VMS registering during an upgrade installation, 3-27 , 8-27 VMS optional files upgrade restriction, 5-4 selecting during upgrade, Volume Shadowing license 8-13 registering after VMS optional save set installation, 4-2 contents, C-2 registering during VMS save sets installation, 3-27 location on magnetic tape, VOTES parameter 3-5 checking for rolling upgrade, required location, 3-2, 3-5 7-5 tape cartridge containing, setting for concurrent 3-5 upgrade, 7-2 transferring to system disk, upgrade requirement, 7-2 3-5 Index-21 VPM (VMS Performance Monitor) updating, 9-4 object Windowing system enabling or disabling, 9-9 choosing, 3-20 WINDOW_SYSTEM SYSGEN parameter W______________________________ , 3-20 WELCOME.TXT Workstation customizing, 11-5 Index-22