ECO NUMBER: VAXCLUSIO01_062 PRODUCT: OpenVMS VAX OPERATING SYSTEM 6.2 UPDATE PRODUCT: OpenVMS VAX OPERATING SYSTEM 6.2 COVER LETTER 1 KIT NAME: VAXCLUSIO01_062 2 KITS SUPERSEDED BY THIS KIT: None 3 KIT DESCRIPTION: 3.1 Version(s) of OpenVMS to which this kit may be applied: OpenVMS VAX V6.2 3.2 In order to receive the full fixes listed in this kit the following remedial kits also need to be installed: None 3.3 Files patched or replaced: o [SYS$LDR]DEBUG_SHDRIVER.EXE (new image) o [SYSLIB]DISMNTSHR.EXE (new image) o [SYSEXE]DISMOUNT.EXE (new image) o [SYS$LDR]DUDRIVER.EXE (new image) o [SYS$LDR]ERRORLOG.EXE (new image) o [SYS$LDR]EXEC_INIT.EXE (new image) o [SYSEXE]F11BXQP.EXE (new image) o [SYS$LDR]IMAGE_MANAGEMENT.EXE (new image) o [SYSLIB]INIT$SHR.EXE (new image) o [SYS$LDR]IO_ROUTINES.EXE (new image) o [SYS$LDR]LOCKING.EXE (new image) o [SYSLIB]MOUNTSHR.EXE (new image) o [SYSEXE]MSCP.EXE (new image) -- COVER LETTER -- Page 2 4 March 1997 o [SYSLIB]NISCS_LOAD.EXE (new image) o [SYS$LDR]PAGE_MANAGEMENT.EXE (new image) o [SYSEXE]SDA.EXE (new image) o [SYSEXE]SHADOW_SERVER.EXE (new image) o [SYSEXE]SHADOW_SERVER_DEBUG.EXE (new image) o [SYS$LDR]SHDRIVER.EXE (new image) o [SYSEXE]SHOW.EXE (new image) o [SYSLIB]SMI$OBJSHR.EXE (new image) o [SYSEXE]SMISERVER.EXE (new image) o [SYSEXE]SYSBOOT.EXE (new image) o [SYSEXE]SYSGEN.EXE (new image) o [SYSEXE]SYSINIT.EXE (new image) o [SYSEXE]SYSMAN.EXE (new image) o [SYSMSG]SYSMSG.EXE (new image) o [SYSEXE]TMSCP.EXE (new image) o [SYS$LDR]TUDRIVER.EXE (new image) o [SYSEXE]VMOUNT.EXE (new image) o [SYSUPD]VMS$REMEDIAL_ID.EXE (new image) 4 PROBLEMS NOT ADDRESSED IN VAXCLUSIO01_062 KIT o The following three MOUNT problems were discovered at a late stage in the release of this kit. OpenVMS Engineering is working on solutions to these problems which will be available in a future MOUNT ECO kit. If a user, either manually or by a command procedure, performs one of the following errors, MOUNT may incorrectly add members to existing shadow sets. - A MOUNT/SHAD with an incorrect volume label will succeed in adding the member to the shadow set, for example: $ MOUNT/SYSTEM DSA1/SHAD=$4$DUA1 TST1 $! The shadow set DSA1 is now available with DUA1 as $! the only member -- COVER LETTER -- Page 3 4 March 1997 $ MOUNT/SYSTEM DSA1/SHAD=$4$DUA5 TST5 $! The device $4$DUA5 is wrongly added as a full copy $! target. - Similarly, a MOUNT/SHAD with an incorrect volume label of a shadow set that is mounted elsewhere in the cluster will succeed in adding the member to the shadow set on the other nodes, but the MOUNT will fail on the local node, for example: NODE_1> $ MOUNT/SYSTEM DSA1/SHAD=$4$DUA1 TST1 NODE_1> $ ! The shadow set DSA1 is now available on NODE_1 NODE_2> $ MOUNT/SYSTEM DSA1/SHAD=$4$DUA5 TST5 NODE_2> $! The MOUNT correctly fails on NODE_2 with $! INCVOLLABEL error NODE_1> $! However, the member $4$DUA5 is wrongly added NODE_1> $! to the set DSA1 as a full copy target. - MOUNT will incorrectly allow a non-shareable MOUNT/SHADOW of a disk that is already mounted on another node as "shareable" to succeed. As a result, corruption of the disk(s) will take place, for example: NODE_1> $ MOUNT/SYSTEM DSA1/SHAD=$4$DUA1 TST1 NODE_1> $ ! The shadow set DSA1 is now available on NODE_1 NODE_2> $ MOUNT /NOSHARE DSA5/SHAD=$4$DUA1 TST1 NODE_2> $! The shadow set DSA5 is (wrongly) now available $! on NODE_2 NODE_1> $! The shadow set DSA1 is also available on NODE_1 Corruption of the disk will occur when write operations are performed by either node. 5 PROBLEMS ADDRESSED IN VAXCLUSIO01_062 A SHADDETINCON BUGCHECK will occur in SHD_THREADS trying to terminate a thread that is still a Significant Event. o The Volume Shadowing driver delivered in V7.1 and the V6.2 Cluster Compatibility kits (xxxCOMPAT_062) did not contain the full solution for the 'Bad Block Repair' (BBR) problem. As a result, when it might be warranted, a disk would not be expelled from the shadow-set. o An incompatibility has developed between StorageWorks Host Based RAID Software, and the enhanced volume shadowing provided in both OpenVMS 7.1 and in the Cluster Compatibility Kits -- COVER LETTER -- Page 4 4 March 1997 (xxxCOMPAT_62). Because of this incompatibility, RAID software can no longer detect that a shadow set state change has occurred. o Write protecting a shadow set member which is being added to an existing shadowset causes virtual unit to hang. o System crashes with INVEXCEPTN Bugchecks in SHSB$SEND_MESSAGE because the UCB address in R5 is zero. Or it may also crash in IOC_STD$CVT_DEVNAM in IO_ROUTINES when we try to get a DDB out of a UCB that is bad. The problem is caused when the IRP$L_ARB field in not correctly set up with the clone error index. In routine SH$VP_DEV_DRVERR we use this byte as an index to fetch the UCB of the erring device. The value is FF so we fetch an incorrect longword. The bad value occurs when we enter volume processing to initiate mount verification after a device error occurs. o Shadowsets can hang in mountverify for hours after encountering a controller failure (DRAB_INT) on an HSJ50 followed by many 'forced error flagged in last sector read' error messages on multiple shadowset member disks. o The VAXCLUSIO01_062 remedial kit includes the fucntionality shipped with the VAXCOMPAT_062 Cluster Compatibilty Kit. The OpenVMS Cluster Compatibility Kit provides many OpenVMS Version 7.1 enhancements for Version 6.2 systems. This kit is required for Version 6.2 systems if they are included in a cluster with Version 7.1 systems (same system architecture or a mix of VAX and Alpha systems). Optionally, users can install it on other OpenVMS Version 6.2 systems to derive the same benefits. Cluster Compatibility Kit Features: o OpenVMS Version 7.1 Volume Shadowing enhancements The volume shadowing enhancements include significant quality improvements and an increase in supported shadow set members from 400 to 500. Note that the Version 7.1 volume shadowing system disk minimerge feature is not included in the Cluster Compatibility Kit nor is the Dump file off the system disk for OpenVMS Alpha. (Dump file off the system disk has been available for OpenVMS VAX systems since Version 6.2.) _______________________ Note _______________________________ If you use volume shadowing , be sure to read the volume shadowing release notes. ____________________________________________________________ o OpenVMS Version 7.1 Mount enhancements The Mount utility has been completely rewritten, resulting in a faster, more robust utility. -- COVER LETTER -- Page 5 4 March 1997 o Correction to an OpenVMS Version 6.2 lock manager problem The lock manager changes correct a problem in OpenVMS Version 6.2 that could corrupt some internal states in lock information used by fork lock routines, notably the I/O cache subsystem . This problem was corrected in OpenVMS Version 7.0, and also in the limited hardware releases for OpenVMS Alpha Version 6.2-1H2 and Version 6.2-1H3. o Limited support for new port allocation classes for SCSI devices Port allocation classes are a new naming option for SCSI devices on systems running OpenVMS Alpha Version 7.1. If you have installed the Cluster Compatibility Kit (on a VAX or Alpha system ), you can access SCSI disks on an OpenVMS Alpha Version 7.1 system that use port allocation classes in their names, but you cannot name SCSI disks on a Version 6.2 system with port allocationclasses. o Snapshot Facility Disabled Installing the Cluster Compatibility Kit on a Version 6.2 system disables the Snapshot facility , which has been removed from OpenVMS VAX Version 7.1. o System Dump Analyzer Utility (SDA) A special version of the OpenVMS Version 6.2 System Dump Analyzer (SDA) utility is included in the Cluster Compatibility Kit. It recognizes the new volume shadowing data structures. When you install the Cluster Compatibility Kit, the existing OpenVMS Version 6.2 SDA is renamed SDA_OLD . EXE and the Cluster Compatibility Kit version is named SDA.EXE. Use SDA_OLD.EXE to analyze crash dumps from an OpenVMS Version 6.2 system that has not installed the Cluster Compatibility Kit. Use SDA.EXE to analyze crash dumps from an OpenVMS Version 6.2 systemthat has installed the Cluster Compatibility Kit. 6 KIT INSTALLATION RATING: The following kit installation rating, based upon current CLD information, is provided to serve as a guide as to which customers should apply this remedial kit. (Reference attached Disclaimer of Warranty and Limitation of Liability Statement) INSTALLATION RATING: -- COVER LETTER -- Page 6 4 March 1997 INSTALL_2 : To be installed by all customers using the following feature(s): - Customers running the ALPCOMPAT_062 - Customers running OpenVMS V6.2 that want to take advantage of the included enhancements; SHADOW and MOUNT. 7 INSTALLATION INSTRUCTIONS: **** NOTE **** Before installing the VAXCLUSIO01_062 remedial kit you should review the documentation for the following four remedial kits. If you wish to install these kits they must be installed before installing the VAXCLUSIO01_062 kit. VAXCLIU02_070 VAXMANA03_070 VAXSYS05_070 VAXDOSD06_062 The VAXCLUSIO01_062 kit contains all the fixes included in the following list of remedial kits. Once the ALPCLUSIO01_062 kit is installed, you no longer need to install these remedial kits on V6.2* OpenVMS Alpha systems. .literal VAXDISM01_062 VAXDRIV04_070 VAXF11X03_070 VAXSYS01_062 VAXINIT01_070 VAXSYS06_070 VAXMSCP01_070 VAXSHAD05_062 VAXSYS04_070 Install this kit with the VMSINSTAL utility by logging into the SYSTEM account, and typing the following at the DCL prompt: @SYS$UPDATE:VMSINSTAL VAXCLUSIO01_062 [location of the saveset] The saveset location may be a tape drive, or a disk directory that contains the kit saveset. System should be rebooted after successful installation of the kit. If you have other nodes in your VMScluster, they should also be rebooted in order to make use of the new image(s). Copyright (c) Digital Equipment Corporation, 1997 All Rights Reserved. Unpublished rights reserved under the copyright laws of the United States. The software contained on this media is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or dissemination of the software and media is authorized only pursuant to a valid written license from Digital Equipment Corporation. -- COVER LETTER -- Page 7 4 March 1997 DISCLAIMER OF WARRANTY AND LIMITATION OF LIABILITY THIS PATCH IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND. ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY EXCLUDED TO THE EXTENT PERMITTED BY APPLICABLE LAW. IN NO EVENT WILL DIGITAL BE LIABLE FOR ANY LOST REVENUE OR PROFIT, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, WITH RESPECT TO ANY PATCH MADE AVAILABLE HERE OR TO THE USE OF SUCH PATCH.