____________________________________________________ OpenVMS AXP Version 1.5-1H1 Release Notes and Update Procedures Order Number: AV-Q1CRA-TE October 1993 This document contains release notes for the OpenVMS AXP Version 1.5-1H1 operating system and procedures for applying the update. Revision/Update Information: This is a new document. Operating System and Version: OpenVMS AXP Version 1.5-1H1 Digital Equipment Corporation Maynard, Massachusetts ________________________________________________________________ October 1993 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 1993. All Rights Reserved. The following are trademarks of Digital Equipment Corporation: Alpha AXP, AXP, Bookreader, CI, DECnet, DECwindows, Digital, InfoServer, LN01, MSCP, OpenVMS, Q-bus, TURBOchannel, UETP, VAX, VAX DOCUMENT, VMS, VMScluster, and the DIGITAL logo. The following is a third-party trademark: Windows NT is a trademark of Microsoft Corporation. ZK6360 This document was prepared using VAX DOCUMENT, Version 2.1. _________________________________________________________________ Contents Preface................................................... v 1 OpenVMS AXP Version 1.5-1H1 Release Notes 1.1 DEC 2000 Model 300 Notes and Restrictions..... 1-1 1.1.1 No Datacheck Support for Floppy Drive..... 1-1 1.1.2 Using the EISA Configuration Utility (ECU)..................................... 1-1 1.1.3 Running AUTOGEN........................... 1-2 1.1.4 SCSI Port Error Count..................... 1-2 1.1.5 Switching Console Output.................. 1-3 1.1.6 Keyboard Support on DEC 2000 Model 300 Systems................................... 1-3 1.1.6.1 Keyboard Mappings....................... 1-3 1.1.6.2 Using the CAPS LOCK Key................. 1-5 1.1.6.3 Keyboard Restrictions................... 1-6 1.1.7 Graphics Support on DEC 2000 Model 300 Systems................................... 1-6 1.2 Displaying Model Numbers for DEC 3000 Model 600 and 800 Systems........................... 1-8 1.3 LMF Installation Problem and Workaround....... 1-8 1.4 Guidelines for Installing or Updating the OpenVMS AXP Operating System.................. 1-9 1.4.1 When to Update............................ 1-9 1.4.2 How to Update............................. 1-10 1.4.3 When to Install........................... 1-10 1.4.4 How to Install............................ 1-10 iii 2 VMScluster Release Notes 2.1 OpenVMS AXP V1.5 and OpenVMS VAX V6.0 Interoperability.............................. 2-1 2.1.1 Compatibility Between VAX and AXP systems................................... 2-1 2.1.2 Rolling Upgrades in Dual-Architecture Clusters.................................. 2-2 2.1.3 SYSMAN Restriction........................ 2-2 2.1.4 Where to Find Interoperability Information............................... 2-2 2.2 FDDI Support.................................. 2-5 2.2.1 Supported Adapters........................ 2-5 2.2.2 Enabling FDDI............................. 2-6 2.2.3 Satellite Booting......................... 2-6 2.2.4 UETP Not Supported for FDDI Devices....... 2-7 2.2.5 Using the DEMFA Adapter on AXP Systems.... 2-7 2.3 DSSI Configurations........................... 2-7 2.3.1 Support for Specific Configurations....... 2-7 2.3.2 Using the KFQSA Adapter................... 2-7 2.4 VMScluster Support for DEC 2000 Model 300 Systems....................................... 2-8 2.5 Support for Larger Configurations............. 2-8 2.5.1 Support for Up to 50 DEC 3000 and DEC 2000 Alpha AXP Systems......................... 2-8 2.5.2 Configuration Rules....................... 2-9 3 Updating to OpenVMS AXP Version 1.5-1H1 3.1 Preparing Your System......................... 3-1 3.2 Matching Update Procedures to System Configurations................................ 3-3 3.2.1 Updating VMScluster Environments.......... 3-4 3.2.2 Updating a Local Area VMScluster System with One Boot Server and Two System Disks..................................... 3-4 3.3 Applying the OpenVMS AXP Version 1.5-1H1 Update........................................ 3-5 3.4 Tasks to Perform After the Update............. 3-8 iv Tables 1-1 Keyboard Mappings for DEC 2000 Model 300 Keyboards................................. 1-3 v _________________________________________________________________ Preface The OpenVMS AXP Version 1.5-1H1 operating system is available as an update that you can apply to your OpenVMS AXP Version 1.5 system and as a complete kit requiring a full installation. Intended Audience This document is intended for anyone responsible for maintaining the OpenVMS AXP operating system. Document Structure This document is organized as follows: o Chapter 1 includes release notes relevant to this kit. o Chapter 2 includes release notes about VMScluster support. o Chapter 3 describes how to prepare your system for an update, how to use the update procedure, and how to perform postupdate tasks. v Associated Documents If you are updating your OpenVMS AXP Version 1.5 system to Version 1.5-1H1 or if you are performing a full installation, you might need to refer to one or more of the following documents: o The OpenVMS AXP Version 1.5 Upgrade and Installation Manual (required for full installation) o The OpenVMS AXP Version 1.5 Release Notes o The OpenVMS AXP Version 1.5 Release Notes Addendum Conventions The following conventions are used in this manual: ( ) In format descriptions, parentheses indicate that, if you choose more than one option, you must enclose the choices in parentheses. [ ] In format descriptions, brackets indicate optional elements. You can choose one, none, or all of the options. (Brackets are not optional, however, in the syntax of a directory name in an OpenVMS file specification, or in the syntax of a substring specification in an assignment statement.) italic text Italic text emphasizes important information, indicates variables, and indicates complete titles of manuals. Italic text also represents information that can vary in system messages (for example, Internal error number), command lines (for example, /PRODUCER=name), and command parameters in text. vi 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 Bookreader versions of the manual. UPPERCASE TEXT Uppercase text indicates a command, the name of a routine, the name of a file, or the abbreviation for a system privilege. - A hyphen in code examples indicates that additional arguments to the request are provided on the line that follows. numbers All numbers in text are assumed to be decimal, unless otherwise noted. Nondecimal radixes-binary, octal, or hexadecimal-are explicitly indicated. vii 1 _________________________________________________________________ OpenVMS AXP Version 1.5-1H1 Release Notes This chapter contains OpenVMS AXP Version 1.5-1H1 release notes you should review before installing or updating your system. 1.1 DEC 2000 Model 300 Notes and Restrictions This section contains notes and restrictions specific to DEC 2000 Model 300 systems. 1.1.1 No Datacheck Support for Floppy Drive Version 1.5-1H1 of the OpenVMS AXP operating system does not include support for datacheck operations for the floppy diskette drive (DVDRIVER) on DEC 2000 Model 300 computers. 1.1.2 Using the EISA Configuration Utility (ECU) When deciding whether to use the EISA Configuration Utility (ECU) on DEC 2000 Model 300 systems, note the following: o You cannot run the ECU from an alternate console. o If you want to configure an EISA device other than the base configuration, you must use the ECU. o If you have been using the ECU on a Windows NT[TM] system, you must continue to do so. However, because the OpenVMS ECU configuration files are different (most significantly in the configuration of multiple Adaptec[TM] SCSI adapters) from those used by the Windows NT system, you should rerun the ECU specifically provided for OpenVMS or OSF systems. ____________________ [TM] Windows NT is a trademark of Microsoft Corporation. [TM] Trademark of Adaptec, Inc. 1-1 OpenVMS AXP Version 1.5-1H1 Release Notes 1.1 DEC 2000 Model 300 Notes and Restrictions To rerun the ECU, do the following: 1. Because you must run the ECU from the Windows NT console, enter the following command: SET OS NT 2. After power cycling the system, use the arrow key to select the SETUP menu. Using this menu, you can select and run the ECU from a floppy diskette. 3. For complete information about using the ECU, refer to the ECU online help and the manual entitled DECpc AXP 150 and DEC 2000 Model 300 Customer Technical Information. 1.1.3 Running AUTOGEN Digital strongly recommends that you run AUTOGEN to make sure all system parameter values are calculated correctly. (Be sure the system has been running for at least 24 hours with a typical workload before running AUTOGEN.) 1.1.4 SCSI Port Error Count When the OpenVMS AXP operating system is booted on a DEC 2000 Model 300 system, SCSI ports labeled PKn0 (as listed in the SHOW DEVICE or SHOW ERROR display) will show an error count of 1 but will not have the error listed in the log file. This is not an actual error, but rather the result of the SCSI bus reset issued in the boot path. 1-2 OpenVMS AXP Version 1.5-1H1 Release Notes 1.1 DEC 2000 Model 300 Notes and Restrictions 1.1.5 Switching Console Output You can switch your console output to the alternate console or to the graphics terminal by using the SET CONSOLE command and specifying either VGA (graphics terminal) or serial (alternate console). For example: >>> SET CONSOLE VGA 1.1.6 Keyboard Support on DEC 2000 Model 300 Systems The DEC 2000 Model 300 keyboard comes in both 101- and 102-key versions. This keyboard looks similar to the LK443 (101-key) and LK444 (102-key) keyboards supplied with other Digital computers. This section describes modifications that make it easier for you to use the PC keyboard in an OpenVMS environment. 1.1.6.1 Keyboard Mappings The keyboard uses an industry-standard PC layout, rather than an LK201 or LK401 keyboard layout. However, to be compatible with Digital software, the default keyboard mapping on DEC 2000 Model 300 systems does not always generate the value that is engraved on the key, but instead generates the value that would be applicable to an LK201 or LK401 keyboard. This allows most OpenVMS applications to work using the default keyboard without requiring you to use shift keys for commonly used keys. See Table 1-1 for the list of keys and their default bindings. Table_1-1_Keyboard_Mappings_for_DEC_2000_Model_300_Keyboards_____ Key Engraving____Value______Shift________Right_Ctrl_____Shift/Right Ctrl Function_Keys_______________________________________________________ Print XK_Help XK_Sys_Req Screen Scroll Lock XK_Menu XK_Menu(DO) XK_Scroll_Lock XK_Scroll_Lock (DO) (continued on next page) 1-3 OpenVMS AXP Version 1.5-1H1 Release Notes 1.1 DEC 2000 Model 300 Notes and Restrictions Table 1-1 (Cont.) Keyboard Mappings for DEC 2000 Model 300 __________________Keyboards______________________________________ Key Engraving________Value_______Shift__________Right_Ctrl______Shift/Right Ctrl Control_Keys_______________________________________________________________ Right Ctrl XK_Mode_Switch XK_Mode_Switch XK_Mode_Switch XK_Mode_Switch __________________________________________________________________________ Editing_Keys______________________________________________________________ Insert XK_Find XK_Find XK_Insert XK_Insert Delete XK_Select XK_Select XK_Delete XK_BackSpace Home XK_Insert XK_Insert XK_Home XK_Home End XK_Prior XK_Prior XK_End XK_End (Prev) (Prev) Page Up DRemove DRemove XK_Prior XK_Prior (Remove) (Remove) (continued on next page) 1-4 OpenVMS AXP Version 1.5-1H1 Release Notes 1.1 DEC 2000 Model 300 Notes and Restrictions Table 1-1 (Cont.) Keyboard Mappings for DEC 2000 Model 300 __________________Keyboards______________________________________ Key Engraving____Value___________Shift__________Right_Ctrl_____Shift/Right Ctrl Keypad_Keys______________________________________________________________ Num Lock XK_KP_F1 XK_Num_Lock XK_Num_Lock XK_Num_Lock (PF1) / (Divide) XK_KP_F2 XK_KP_F2 XK_KP_Divide XK_KP_Divide (PF2) (PF2) * (Multiply) XK_KP_F3 XK_KP_F3 XK_KP_Multiply XK_KP_Multiply (PF3) (PF3) - (Subtract) XK_KP_F4 XK_KP_F4 XK_KP_Subtract XK_KP_Subtract (PF4) (PF4) . (Decimal) XK_KP_Decimal XK_KP_Decimal XK_KP_Delete XK_KP_Decimal + (Add) XK_KP_Separator XK_KP_Subtract XK_KP_Add XK_KP_Separator Keypad 0 XK_KP_0 XK_KP_0 XK_KP_Insert XK_KP_0 Keypad 1 XK_KP_1 XK_KP_1 XK_KP_End XK_KP_1 Keypad 2 XK_KP_2 XK_KP_2 XK_KP_Down XK_KP_2 Keypad 3 XK_KP_3 XK_KP_3 XK_KP_Next XK_KP_3 Keypad 4 XK_KP_4 XK_KP_4 XK_KP_Left XK_KP_4 Keypad 6 XK_KP_6 XK_KP_6 XK_KP_Right XK_KP_6 Keypad 7 XK_KP_7 XK_KP_7 XK_KP_Home XK_KP_7 Keypad 8 XK_KP_8 XK_KP_8 XK_KP_Up XK_KP_8 Keypad 9 XK_KP_9 XK_KP_9 XK_KP_Prior XK_KP_9 1.1.6.2 Using the CAPS LOCK Key By using the CAPS LOCK key as a shift key and then pressing function keys F1 through F10 and the Keypad Plus Key, you can generate function keys F11 through F20 and the Keypad Minus key. When any of these keys are pressed, and the CAPS LOCK key is pressed, the CAPS LOCK is assumed to be a temporary shift key and the LOCK state is returned to its previous state, and the translated function key is generated. This provides compatibility with the VT510 1-5 OpenVMS AXP Version 1.5-1H1 Release Notes 1.1 DEC 2000 Model 300 Notes and Restrictions terminal and allows the generation of keys F17 to F20 by pressing CAPS LOCK and then keys F7 to F10. 1.1.6.3 Keyboard Restrictions Note the following keyboard restrictions: o This release does not support Num Lock as a locking modifier for the keypad, as it does on a PC. Num Lock support will be provided in a future release of the OpenVMS AXP operating system. o The Num Lock light corresponds to the COMPOSE light. o You can activate the COMPOSE function by using the LK201 mechanism of pressing the ALT and SPACE keys. o This release does not set the default keyboard type and language and will instead use a LK401 keymap file. To obtain the correct keyboard mapping, you must select the Keyboard entry from the Options pulldown menu in the Session Manager window. The keymap files are denoted by LK444 (102-key keyboards) and LK443 (101-key US keyboard). 1.1.7 Graphics Support on DEC 2000 Model 300 Systems The following notes and restrictions apply to DEC 2000 Model 300 systems with graphics. o The system parameter VIRTUALPAGECNT must be set to a minimum of 400,000 pagelets. The server requires over 160MB of virtual address space to map the frame buffer and registers into the DEC 2000 Model 300 sparse address space. o The DEC 2000 Model 300 computer supports only a single QVision video card. o Graphics will not work if you boot the system using the alternate console. Only the console for graphics (with keyboard and mouse input) is supported. o When you boot the system from the graphics console, the serial lines do not work, nor can you use Ctrl/P to halt the system. o If the window system is active, halting the system and then entering the console command, CONTINUE, is not supported. 1-6 OpenVMS AXP Version 1.5-1H1 Release Notes 1.1 DEC 2000 Model 300 Notes and Restrictions o Note the following about the console window: - The console window is full screen (VGA mode) and when active, the server operation is suspended until the console window is removed. - Because the server is stalled by the console, a logical is available that will allow you to remove the console window automatically after a specified number of seconds. This feature is not enabled by default. To enable the feature, define the server logical (in DECW$PRIVATE_ SERVER_SETUP.COM) as follows: DEFINE/SYS DECW$SERVER_AUTO_CONSOLE_REMOVE n where: n is the number of seconds you want the console window to be visible before it is removed. - The console window is 24 lines by 80 columns. The 25th line contains one of two possible displays. When the window system is active, the following message is displayed: OpenVMS AXP Operator Console - Ctrl+F2 to Resume the Window System When the window system is not active, the following message is displayed: OpenVMS AXP Operator Console You can customize or internationalize the messages by defining the server logicals (in DECW$PRIVATE_SERVER_ SETUP.COM) as follows: DEFINE/SYS DECW$SERVER_ACTIVE_STATUS_LINE "text-for-active-window-system-message" DEFINE/SYS DECW$SERVER_NOT_ACTIVE_STATUS_LINE "text-for-inactive-window-system-message" - The server implements a fast 0-width line drawing algorithm that uses the QVision drawing engine at full speed. Due to a hardware problem, lines may not be correct for the last pixel of lines using CapNotLast. You can choose accurate semantics but the drawing performance will be 10 times slower (0- width lines do not need to be accurate). To draw end pixels correctly for 0-width lines, define the 1-7 OpenVMS AXP Version 1.5-1H1 Release Notes 1.1 DEC 2000 Model 300 Notes and Restrictions server logical (in DECW$PRIVATE_SERVER_SETUP.COM) as follows: DEFINE/SYS DECW$SERVER_USE_SLOW_VGA TRUE 1.2 Displaying Model Numbers for DEC 3000 Model 600 and 800 Systems When you enter the SHOW CLUSTER command, the HW_TYPE field displays "ALPH" instead of specific model numbers for the DEC 3000 Model 600 and 800 systems. For example: $ SHOW CLUSTER/CONTINUE View of Cluster from system ID 62345 node: DEC3T6 27-JUL-1993 16:49:20 SYSTEMS NODE SYS_ID HW_VERS HW_TYPE SOFTWARE DEC3T6 62345 042700000000000000000004 ALPH VMS V1.5 DEC3T8 20073 042800000000000000000004 ALPH VMS V1.5 DEC3T4 64568 040B00000000000000000004 DEC 3000 Model 400 VMS V1.5 DEC3T5 65525 040900000000000000000004 DEC 3000 Model 500 VMS V1.5 VAX4T6 64894 00EC00000000000012000003 VAXstation 4000-60 VMS V6.0 To display the model number for a DEC 3000 Model 600 or 800 system, log in to that system and then enter the following command: $ Write SYS$OUTPUT F$GETSYI ("HW_NAME") 1.3 LMF Installation Problem and Workaround If your terminal has a device type of UNKNOWN, FT1-FT8, or LN01K, a LICENSE LIST command will list all the PAKs in your license database (LDB), except for the last PAK. As a workaround, enter the following command: $ SET TERMINAL/DEVICE_TYPE=terminal-type This command modifies your terminal type. For a list of terminal types, do one of the following: o Enter the following command: $HELP SET TERMINAL/DEVICE_TYPE 1-8 OpenVMS AXP Version 1.5-1H1 Release Notes 1.3 LMF Installation Problem and Workaround o Enter the LICENSE LIST/OUTPUT=file command and then TYPE the file for a complete listing. 1.4 Guidelines for Installing or Updating the OpenVMS AXP Operating System The following sections provide information about the distribution media and guidelines for updating to or installing the OpenVMS AXP Version 1.5-1H1 operating system. ________________________ Note ________________________ You cannot upgrade to Version 1.5-1H1 of the operating system. You must perform either an update or an installation, as outlined in the following sections. ______________________________________________________ 1.4.1 When to Update You can update directly to Version 1.5-1H1 of the OpenVMS AXP operating system only if your AXP computer is running Version 1.5 of the OpenVMS AXP operating system. (You cannot update from Version 1.0 or field test versions of Version 1.5 of the OpenVMS AXP operating system.) If you are adding a new AXP computer to an existing cluster, you can update directly to Version 1.5-1H1 of the OpenVMS AXP operating system if you perform the update on the OpenVMS AXP Version 1.5 boot node in the cluster. ________________________ Note ________________________ When deciding whether to update your system, note the following: o The update procedure does not initialize the system disk; that is, it leaves layered products and user files intact. o You can apply the update on a system running only OpenVMS AXP Version 1.5. If your system is running Version 1.0 of the OpenVMS AXP operating system, you must upgrade to OpenVMS AXP Version 1.5 before applying this update (if you do not want to perform a full installation, 1-9 OpenVMS AXP Version 1.5-1H1 Release Notes 1.4 Guidelines for Installing or Updating the OpenVMS AXP Operating System which would overwrite existing files on your system disk). See the OpenVMS AXP Version 1.5 Upgrade and Installation Manual and the OpenVMS AXP Release Notes Addendum for information about the upgrade procedure. ______________________________________________________ 1.4.2 How to Update To update your system to Version 1.5-1H1 of the OpenVMS AXP operating system, follow the procedures described in Chapter 3. 1.4.3 When to Install You must perform a full installation (rather than an update) if your system meets one of the following conditions: o Your AXP computer is new. (However, if you are adding a new system to an existing cluster, you do not need to perform an installation if you update the OpenVMS AXP Version 1.5 boot node in that cluster.) o Your AXP computer has never had any version of the OpenVMS AXP operating system running on it. o Your AXP computer is running the OpenVMS AXP operating system and you want to destroy the contents of the system disk (both AXP and user files). 1.4.4 How to Install To install the OpenVMS AXP Version 1.5-1H1 operating system, do the following: 1. Review the OpenVMS AXP Version 1.5 Release Notes, the OpenVMS AXP Release Notes Addendum, and accompanying cover letters for information relevant to your specific AXP computer and to installation procedures in general. 2. Begin the installation using the OpenVMS AXP Version 1.5 Upgrade and Installation Manual, but note the following: o When you boot from the InfoServer, enter APB_1H1015 when the installation procedure prompts you for the 1-10 OpenVMS AXP Version 1.5-1H1 Release Notes Guidelines for Installing or Updating the OpenVMS AXP Operating System file name that contains the initial system load (ISL) boot program. o When you create the new system disk, specify AVMS1H1015.B as the save-set name when you enter the backup command that transfers the save set from your source drive to your target drive. 1-11 2 _________________________________________________________________ VMScluster Release Notes The following notes contain information that supplements the OpenVMS VAX Version 6.0 Release Notes and the OpenVMS AXP Version 1.5 Release Notes. This chapter is divided into four main topics: o OpenVMS AXP V1.5 and OpenVMS VAX V6.0 interoperability o FDDI support o DSSI configurations o DEC 3000 and DEC 2000 support and configuration In a dual-architecture VMScluster system, you can use the latter three items on AXP systems running OpenVMS AXP Version 1.5 and VAX systems running either OpenVMS VAX Version 5.5-2 or Version 6.0. 2.1 OpenVMS AXP V1.5 and OpenVMS VAX V6.0 Interoperability This section includes information about the following: o Compatibility between VAX and AXP systems o Performing rolling upgrades on VAX systems in dual- architecture clusters o A SYSMAN restriction o Where to find interoperability information 2.1.1 Compatibility Between VAX and AXP systems Nodes running OpenVMS AXP V1.5 now can be clustered with nodes running either OpenVMS VAX Version 6.0 or Version V5.5-2 (not Version A5.5-2). However, Digital does not recommend clustering OpenVMS AXP V1.5 with both VAX versions at the same time. 2-1 VMScluster Release Notes 2.1 OpenVMS AXP V1.5 and OpenVMS VAX V6.0 Interoperability 2.1.2 Rolling Upgrades in Dual-Architecture Clusters During rolling upgrades from OpenVMS VAX Version V5.5-2 to Version 6.0, you might need to temporarily run both VAX versions simultaneously with OpenVMS AXP Version 1.5. Although Digital does not recommend running more than two versions of OpenVMS VAX in a dual-architecture cluster for an extended period of time, it can be done for the limited duration of the upgrade procedure. The upgrade procedure allows a VMScluster system running on multiple system disks to continue to provide service while the system software is being upgraded. Note: There are no known problems with running the three operating system versions in the same VMScluster system. However, extensive testing has not been done to qualify this type of configuration. Digital strongly discourages running three operating system versions in a VMScluster system, especially one that is doing production work. 2.1.3 SYSMAN Restriction Do not enter System Management (SYSMAN) utility commands that are specific to AXP processors against VAX processors. This can cause the OpenVMS VAX Version 6.0 SYSMAN server (SMISERVER) to return an access violation (ACCVIO) error. Refer to A Comparison of System Management on OpenVMS AXP and OpenVMS VAX for a discussion of SYSMAN command usage. 2.1.4 Where to Find Interoperability Information Virtually all OpenVMS VAX system management utilities, command formats, and tasks are identical in the OpenVMS AXP environment. However, some exceptions exist for dual- architecture VMScluster systems that system managers must consider for proper setup and management of these VMScluster systems. For clustering, OpenVMS AXP Version 1.5 is functionally equivalent to OpenVMS VAX Version 5.5-2. The following functional and architectural differences apply to a dual- architecture VMScluster running OpenVMS AXP Version 1.5 and OpenVMS VAX Version 6.0, 2-2 VMScluster Release Notes 2.1 OpenVMS AXP V1.5 and OpenVMS VAX V6.0 Interoperability o Apply the same functional differences that are documented for OpenVMS VAX Version 6.0 and OpenVMS VAX Version 5.5-2. o Apply the same architectural differences that are documented for OpenVMS AXP Version 1.5 and OpenVMS VAX Version 5.5-2. Functional and architectural differences and considerations are discussed in the following OpenVMS documentation manuals: ___________________________________________________________ Document_Title_____Description_____________________________ OpenVMS VAX Chapter 2 describes features, changes, Version 6.0 and restrictions specific to VMScluster Release Notes systems running OpenVMS VAX Version 6.0, including: o Security changes o Support for multiple LAN adapters o Batch and print queuing changes o Volume Shadowing for OpenVMS changes o Virtual I/O cache OpenVMS AXP Chapter 4 describes system management Version 1.5 features, changes, and restrictions Release Notes specific to systems running OpenVMS AXP Version 1.5, including: o AUTOGEN o Backup utility o DECnet support for cluster alias o Monitor utility o Mount utility o Security auditing o System Management utility 2-3 VMScluster Release Notes 2.1 OpenVMS AXP V1.5 and OpenVMS VAX V6.0 Interoperability ___________________________________________________________ Document_Title_____Description_____________________________ OpenVMS VAX Describes the new features of the Version 6.0 New OpenVMS VAX Version 6.0 operating Features Manual system. Refer to Chapter 4 for the following cluster-specific topics: o CLUSTER_CONFIG.COM options for tape servers o MSCP dynamic load balancing o Virtual balance slots o Virtual I/O cache to improve virtual read performance o Multiple queue managers o Security changes impacting system management o SYSMAN startup logging and shutdown VMScluster Describes VMScluster system management Systems for tasks, including: OpenVMS o Interoperability information between OpenVMS AXP Version 1.5 and OpenVMS VAX Version 5.5-2 in Chapter 1 o Single security domains on VMScluster systems in Chapter 3 o Management of multiple queue managers on OpenVMS VAX Version 6.0 computers in Chapter 6 OpenVMS Compares and contrasts features on Compatibility computers running OpenVMS VAX Version Between VAX and 6.0 and OpenVMS AXP Version 1.5. The AXP manual focuses on the features provided to end users, system managers, and programmers. 2-4 VMScluster Release Notes 2.1 OpenVMS AXP V1.5 and OpenVMS VAX V6.0 Interoperability ___________________________________________________________ Document_Title_____Description_____________________________ A Comparison of Compares how specific system management System Management tasks differ or remain the same on OpenVMS AXP between OpenVMS AXP Version 1.5 and and OpenVMS VAX the following VAX releases: o VAX VMS Version 5.5 o OpenVMS VAX Version 6.0 ___________________________________________________________ 2.2 FDDI Support When OpenVMS AXP Version 1.5 initially shipped, VMScluster systems supported the CI (computer interconnect), DSSI (Digital Storage Systems Interconnect) and Ethernet interconnects. Now, the Fiber Distributed Data Interface (FDDI) is supported as a VMScluster interconnect for systems running OpenVMS AXP Version 1.5. Alpha AXP FDDI adapters are supported on the full range of DEC 3000, DEC 4000, DEC 7000 and DEC 10000 systems. In a dual-architecture VMScluster system, you can use the FDDI interconnect for SCS node-to-node communications between AXP systems running OpenVMS AXP Version 1.5 and VAX systems running either OpenVMS VAX Version 5.5-2 or Version 6.0. 2.2.1 Supported Adapters The following FDDI adapters are supported: o DEMFA (XMI to FDDI) o DEFTA (TURBOchannel to FDDI) o DEFAA (Futurebus to FDDI) The DEFZA adapter is not supported. 2-5 VMScluster Release Notes 2.2 FDDI Support 2.2.2 Enabling FDDI On systems running OpenVMS AXP Version 1.5, set the PE3 system parameter to a value of 1 to enable clustering over the supported FDDI adapters. If PE3 is set to 0 on a system that has FDDI adapters installed, a warning message similar to the following is displayed during startup: %VMScluster-W-NOSUPPORT, FXA is NOT SUPPORTED by the cluster software You can ignore the message. Note: Setting the PE3 system parameter to enable FDDI VMScluster configurations is specific to OpenVMS AXP Version 1.5 only. Beginning with the next release of OpenVMS AXP, this support will change as follows: o FDDI will be enabled by default. o The PE3 system parameter will be reserved for Digital use only and will no longer be used to enable FDDI. 2.2.3 Satellite Booting Booting satellite nodes over the FDDI is not supported on VMScluster systems running OpenVMS AXP Version 1.5. When using satellite nodes with FDDI adapters, the embedded Ethernet adapter is used for initial downline load of OpenVMS. FDDI VMScluster traffic is enabled during the boot process. When installing the OpenVMS AXP operating system or when running the CLUSTER_CONFIG.COM command procedure, you are asked if the Ethernet will be used for cluster communication. Respond Y to this question if you intend to use Ethernet to boot a VMScluster system and then use FDDI for general cluster traffic. For example: Will the Ethernet be used for cluster communications (Y/N)? Y Satellite booting over the FDDI will be supported in a future release of OpenVMS. 2-6 VMScluster Release Notes 2.2 FDDI Support 2.2.4 UETP Not Supported for FDDI Devices UETP is not supported for FDDI devices on VMScluster systems running OpenVMS AXP Version 1.5. If you attempt to run the UETP software on an AXP system, warning messages are displayed. You can ignore these messages. UETP will support FDDI devices in a future release. 2.2.5 Using the DEMFA Adapter on AXP Systems On systems running OpenVMS AXP Version 1.5, the DEMFA device's FXDRIVER requires a fix to ensure that the DEMFA self-test completes prior to the DEMFA network address being set. Contact your Digital support person to acquire and apply this fix before you enable the DEMFA adapter. 2.3 DSSI Configurations 2.3.1 Support for Specific Configurations OpenVMS AXP V1.5 now supports: o Quad-host DSSI configurations with DEC 4000 systems DEC 4000 systems can be configured only as end nodes on a DSSI bus, therefore, quad-host configurations must include at least two VAX systems. o KFQSA Q-bus to DSSI configurations VAX processors that use the KFQSA adapter can be placed on the same DSSI bus as DEC 4000 processors. 2.3.2 Using the KFQSA Adapter Note the following when using the KFQSA adapter: o The performance of the KFQSA is slow relative to newer generation DSSI adapters. Take this into consideration when you configure KFQSA adapters in VMScluster systems using high performance VAX and AXP computers. o VMScluster System Communications Services (SCS) traffic is not supported over the KFQSA adapter. Only disk and tape data traffic is supported on the KFQSA adapter. Thus, AXP and VAX processors can share data on the DSSI in a VMScluster system, but System Communications Services (SCS) node-to-node communication between 2-7 VMScluster Release Notes 2.3 DSSI Configurations VAX systems configured with KFQSA adapters and other cluster members is possible only over some other type of interconnect, such as Ethernet or FDDI. 2.4 VMScluster Support for DEC 2000 Model 300 Systems VMScluster systems running OpenVMS AXP Version 1.5 now support DEC 2000 Model 300 systems. The DEC 2000 Model 300 systems must be running OpenVMS AXP Version 1.5-1H1. Note: Functionally, OpenVMS AXP Version 1.5-1H1 and Version 1.5 are the same in regard to VMScluster system features and capabilities. 2.5 Support for Larger Configurations This section includes information about the following: o Support for large configurations of DEC 2000 and DEC 3000 Alpha AXP Systems o Configuration rules 2.5.1 Support for Up to 50 DEC 3000 and DEC 2000 Alpha AXP Systems When OpenVMS AXP Version 1.5 initially shipped, VMScluster configurations supported a maximum of twelve DEC 3000 systems. Now, VMScluster systems running OpenVMS AXP Version 1.5 support a combined total of up to 50 DEC 3000 and DEC 2000 AXP systems. The following configuration rules apply: o The DEC 2000 Model 300 systems must be running OpenVMS AXP Version 1.5-1H1. o For DEC 2000 Model 300 systems, communication is supported over Ethernet interconnects only. o For DEC 3000 systems, communication is supported over Ethernet and FDDI interconnects. Note: In VMScluster configurations that include both VAX and AXP computers, the total number of systems supported remains at 96 nodes. 2-8 VMScluster Release Notes 2.5 Support for Larger Configurations 2.5.2 Configuration Rules The following rules apply to AXP systems in a VMScluster configuration: o A maximum of three DEC 7000 and DEC 10000 systems. o A maximum of two DEC 4000 systems. o A maximum of 50 DEC 3000 and DEC 2000 Model 300 systems. o A maximum of two CI adapters can be configured on a DEC 7000 or DEC 10000 system. o A maximum of two LAN adapters can be configured on an Alpha AXP system. o DEC 4000, DEC 7000, and DEC 10000 systems require a system disk that is accessed via a local controller or through a local CI or DSSI connection. These systems cannot be configured to boot as VMScluster satellite nodes. 2-9 3 _________________________________________________________________ Updating to OpenVMS AXP Version 1.5-1H1 This chapter describes how to prepare your system for an update, how to use the update procedure, and how to perform postupdate tasks. ________________________ Note ________________________ Before you update your system, be sure you have reviewed the update and installation guidelines in Section 1.4. ______________________________________________________ 3.1 Preparing Your System Before you install the kit, perform the following tasks: 1. Make sure that your system is running OpenVMS AXP Version 1.5. 2. Using OpenVMS AXP Version 1.5 standalone BACKUP, make an image backup copy of the system disk. _______________________ Caution _______________________ A system failure at a critical point in the update procedure might corrupt the contents of the system disk. Therefore, it is important that you back up the system disk at this time so that you always have a working copy. For more information about backing up your system disk, see the OpenVMS AXP Version 1.5 Upgrade and Installation Manual. ______________________________________________________ 3-1 Updating to OpenVMS AXP Version 1.5-1H1 3.1 Preparing Your System 3. Prepare the system disk. Make sure that you have at least 4000 blocks of free space on the system disk for the update. 4. If the system is part of a VMScluster configuration, shut down any nodes that boot from the system disk on which you are installing the kit. 5. To make sure that the SYSTEM account has sufficient quotas and limits, use the OpenVMS Authorize Utility as follows: a. Enter the following commands: $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> SHOW SYSTEM b. Compare the limits and quotas of the SYSTEM account to the following minimum required values: _____________________________________________________ Quota_Name______________________Minimum_Values_______ Open file quota (FILLM) 100 Buffered I/O limit (BIOLM) 18 Direct I/O limit (DIOLM) 18 AST limit (ASTLM) 24 Enqueue quota (ENQLM) 200 Buffered byte quota count 32768 (BYTLM)______________________________________________ c. If necessary, adjust the limits and quotas until they are equal to or greater than the required values. You can change each value by entering a command in the following format: UAF> MODIFY SYSTEM/limit=new_value For example: UAF> MODIFY SYSTEM/DIOLM=18 d. Exit the OpenVMS Authorize utility by entering the following command: UAF> EXIT 3-2 Updating to OpenVMS AXP Version 1.5-1H1 3.1 Preparing Your System e. If you adjust any of the parameter or quota values of the SYSTEM account, log out and log in again so that the new values take effect. 6. Be sure that you are the only user logged in to the SYSTEM account by completing the following steps: a. Enter the following command to notify current users that they must log out: $ REPLY/ALL/BELL/SHUTDOWN "Log out for Version 1.5-1H1 update." b. Enter the following command to prevent nonprivileged users from logging in: $ SET LOGINS/INTERACTIVE=0 7. If you want to shut down the DECnet software on your system, enter the following commands and then go to Section 3.2: $ RUN SYS$SYSTEM:NCP NCP> SET EXECUTOR STATE OFF NCP> EXIT 3.2 Matching Update Procedures to System Configurations Different system configurations require slightly different update procedures. The following list indicates the possible system configurations and the section to which you should refer: o VMScluster environment: Section 3.2.1 o Dual-architecture VMSclusters: Section 3.2.1. In dual- architecture VMSclusters, only reapply the update to system disks for OpenVMS AXP systems running Version V1.5. o Local area VMSclusters with one boot server and two system disks: Section 3.2.2 o Standalone system: Section 3.3 3-3 Updating to OpenVMS AXP Version 1.5-1H1 3.2 Matching Update Procedures to System Configurations 3.2.1 Updating VMScluster Environments Use the following procedure to update all VMScluster environments. After completing this procedure, all the systems in your VMScluster environment will be running Version 1.5-1H1 of the OpenVMS AXP operating system. 1. Make sure that you have prepared your system for the update as described in Section 3.1. 2. Log in to the SYSTEM account on a node that uses the system disk you are updating. 3. Shut down all other nodes in the cluster that boot from the system disk. 4. Apply the update according to the instructions in Section 3.3. 5. If your VMScluster environment uses several system disks, repeat steps 1 through 4 in this section for each system disk in the VMScluster environment. When the update is complete, perform the postinstallation instructions in Section 3.4. 3.2.2 Updating a Local Area VMScluster System with One Boot Server and Two System Disks To update a local area VMScluster system with one boot server and two system disks, perform the following steps: 1. Make sure that you have prepared your system for the update as described in Section 3.1. 2. Log in to the SYSTEM account on the boot server. 3. Shut down all other nodes in the cluster that boot from the first system disk. 4. Apply the update to the first system disk, according to the instructions in Section 3.3. 5. To update the second disk, perform the following steps: a. Log in to the SYSTEM account on a satellite node that boots from the second system disk. b. Shut down all other nodes in the cluster that boot from the second system disk. 3-4 Updating to OpenVMS AXP Version 1.5-1H1 3.2 Matching Update Procedures to System Configurations c. Apply the update to the second system disk, according to the instructions in Section 3.3. When the update is complete, perform the postinstallation instructions in Section 3.4. 3.3 Applying the OpenVMS AXP Version 1.5-1H1 Update To update the OpenVMS AXP Version 1.5 operating system, complete the following steps: 1. Place the OpenVMS AXP distribution compact disc in the drive. 2. Start the VMSINSTAL command procedure by entering a command similar to the following command: $ @SYS$UPDATE:VMSINSTAL AVMSU1H1015 DKA0: OPTIONS N Note that DKA0 is the device name of the source drive that holds the OpenVMS AXP distribution compact disc. The OPTIONS N portion of the command indicates that you want to display the release notes option menu. If you are updating from the InfoServer, the command is similar to the following: $ @SYS$UPDATE:VMSINSTAL AVMSU1H1015 DAD1: OPTIONS N 3. As the update procedure begins, VMSINSTAL displays messages similar to the following: OpenVMS ALPHA Software Product Installation Procedure V1.5 It is 8-SEP-1993 at 11:26 Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? If you backed up the system disk, press the Return key and go to step 4. If you have not yet backed up the system disk, do the following: a. Enter NO and press the Return key. VMSINSTAL returns to DCL level to permit you to perform the backup. b. Back up the system disk. c. When the backup is complete, restart the update procedure at step 1 in this section. 3-5 Updating to OpenVMS AXP Version 1.5-1H1 3.3 Applying the OpenVMS AXP Version 1.5-1H1 Update 4. The procedure displays the following message: The following products will be processed: AVMSU1H1 V1.5 Beginning installation of AVMSU1H1 V1.5 at 11:26 %VMSINSTAL-I-RESTORE, Restoring product save set A ... 5. With OPTIONS N selected, the procedure then displays the following message: Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: Select option 2 to print the release notes. The system displays the following message: * Do you want to continue the installation? [NO] If you want to continue with the update, enter YES and press the Return key. If you want to abort the update procedure, enter NO and press the Return key. In either case, if you select option 1, 2, or 3, the release notes will be displayed or printed according to your choice. 6. The procedure displays the following messages: %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. To complete the installation of this product, you should reboot the system. If it is not convenient to reboot at this time, then enter NO to the following question. The installation of this kit will continue and the files moved to their appropriate locations without forcing the system to reboot upon completion of the installation. The system can than be rebooted at some more convenient time to actually have this update take effect. Entering YES will cause the system to automatically reboot upon the installation of this kit. * Will you allow a system shutdown after this product is installed [YES]? 3-6 Updating to OpenVMS AXP Version 1.5-1H1 3.3 Applying the OpenVMS AXP Version 1.5-1H1 Update 7. After you respond to the question, the procedure continues with a display similar to the following: Now applying AVMSU1H1015 ... 0) APB (new image) 1) AXP_VMS$SYSVERSION (new image) 2) DEBUG_APB (new image) 3) DECW$DEVICE (new file) 4) DECW$DEVICE_CONFIG_GQ (new file) 5) DECW$SERVER_DDX_GQ (new image) 6) ERF (new image) 7) EXEC_INIT (new file) 8) EXEC_INIT (new image) 9) IODEF (new file) 10) IOGEN$EISA_CONFIG (new image) 11) IOGEN$SHARE (new image) 12) IOGEN$VTI_COMBO_CONFIG (new image) 13) IO_ROUTINES (new file) 14) IO_ROUTINES (new image) 15) LIB (new file) 16) MOM (new image) 17) NCP (new image) 18) NETACP (new image) 19) NETCONFIG (new file) 20) NMLSHR (new image) 21) STARLET (new file) 22) SYS$CPU_ROUTINES_0402 (new image) 23) SYS$CPU_ROUTINES_0602 (new image) 24) SYS$CPU_ROUTINES_0702 (new image) 25) SYS$DKDRIVER (new image) 26) SYS$DVDRIVER (new image) 27) SYS$ERDRIVER (new image) 28) SYS$FRDRIVER (new image) 29) SYS$GKDRIVER (new image) 30) SYS$GQADRIVER (new image) 31) SYS$GXADRIVER (new image) 32) SYS$ICBM_06 (new image) 33) SYS$IKBDRIVER (new image) 34) SYS$IMBDRIVER (new image) 35) SYS$INBDRIVER (new image) 36) SYS$LRDRIVER (new image) 37) SYS$MKDRIVER (new image) 38) SYS$OPDRIVER (new image) 3-7 Updating to OpenVMS AXP Version 1.5-1H1 3.3 Applying the OpenVMS AXP Version 1.5-1H1 Update 39) SYS$PEDRIVER (new file) 40) SYS$PEDRIVER (new image) 41) SYS$PKCDRIVER (new image) 42) SYS$PKJDRIVER (new image) 43) SYS$PKTDRIVER (new image) 44) SYS$PKZDRIVER (new image) 45) SYS$YSDRIVER (new image) %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... 8. When VMSINSTAL completes the update, it displays messages similar to the following: Installation of AVMSU1H1 V1.5 completed at 11:30 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]AVMSU1H1015.VMI_DATA 9. Enter EXIT at the next prompt to end the VMSINSTAL operation. For example: Enter the products to be processed from the next distribution volume set. * Products: EXIT VMSINSTAL procedure done at 11:31 10.If you specified so in your earlier response, the procedure then shuts down the system automatically. If you did not specify automatic shutdown, shut down the system manually. 11.Reboot the system with the updated system disk. If you have a VMScluster environment, reboot the nodes that use the newly updated system disk. 3.4 Tasks to Perform After the Update After you apply an update to your system, Digital recommends that you perform the following tasks: o After the update is complete, set the correct date and time, as follows: - Use the following command to set the time in a nonclustered node: $ SET TIME = 13-SEP-1993:11:22:00 3-8 Updating to OpenVMS AXP Version 1.5-1H1 3.4 Tasks to Perform After the Update - Use the following commands to set the time in a VMScluster: $ RUN SYS$SYSTEM:SYSMAN SYSMAN> SET ENVIRONMENT/CLUSTER SYSMAN> SET PROFILE/PRIVILEGE=(LOG_IO,SYSLCK) SYSMAN> CONFIGURATION SET TIME 13-SEP-1993:11:22:00 SYSMAN> EXIT Refer to your system management manuals for more information about how the operating system maintains the date and time and how to adjust those settings (for example, to allow for daylight-saving time). o If you want a listing of the images replaced by this update, you can print the following file: $ PRINT SYS$UPDATE:VMS$SPECIAL_AVMSU1H1015.DAT o Display the free block count on the system disk by entering the following command: $ SHOW DEVICE SYS$SYSDEVICE: o The VMSINSTAL procedure copies the release notes to the file SYS$HELP:AVMSU1H1015.RELEASE_NOTES. You can print this file on a line printer or display it at a terminal. 3-9