Kit Name: ALPMOUN04_071 Kits superseded by this kit: ALPMOUN03_071 Kit Description: Version(s) of OpenVMS to which this kit may be applied: OpenVMS Alpha V7.1, V7.1-1H1 In order to receive the full fixes listed in this kit the following remedial kits also need to be installed: None. Files patched or replaced: o [SYSLIB]MOUNTSHR.EXE (new image) o [SYSEXE]VMOUNT.EXE (new image) Problems addressed in ALPMOUN04_071 kit o If the target disk of a shadow copy has been inited, such that the SCB is in a different location than that of the master node (i.e. INIT/INDEX=END), and the shadow copy has not yet started, then validation during a second MOUNT of this disk would fail with an ISAMBR error. However, this error was really a WRONGVU error, but an ISAMBR error was displayed instead. Problems addressed in ALPMOUN03_071 kit o A device could be mounted /NOSHARE on one system and as the member of a shadow system disk on another system. This could result in Disk Corruption. No "Alloc. lock ID" is setup on the booting system. o A MOUNT of a former shadow set member will fail on all nodes in a cluster, except the first mounting node, with a "%MOUNT-F-DIFVOLMNT" failure. Page 2 o A MOUNT of multiple tape devices with one command will cause inconsistent "write lock" attributes. For example: $ mount/write mkb400,mkb500 MKB400,TZ000 %MOUNT-I-MOUNTED, MKB400 mounted on _N24005$MKB400: %MOUNT-I-MOUNTED, TZ000 mounted on _N24005$MKB500: $ sho dev mkb Device Device Error Volume Free Trans Mnt Name Status Count Label Blocks Count Cnt MKB400: Mounted alloc 0 MKB400 0 1 1 MKB500: Mounted alloc 0 TZ000 0 1 1 wrtlck MKB500 should not be "wrtlck". o MOUNT messages obtained through OPCOM with MOUNT/ASSIST are often less helpful than the error code returned when /NOASSIST is specified. For example: $ MOUNT/ASSIST /OVER=ID mua0: %MOUNT-I-OPRQST, device _SCSI3$MUA0: contains the wrong volume %MOUNT-I-OPRQST, Please mount device _SCSI3$MUA0: MOUNT/NOASSIST /OVER=ID mua0: %MOUNT-F-NOTLABELMT, tape is not labeled The "NOTLABELMT" is a more accurate message than "wrong volume". o MOUNT/FOREIGN/CLUSTER DUnxx will mount the disk locally, but fails to mount the device on other nodes in the cluster. The error message is: %MOUNT-W-RMTMNTFAIL, _$4$DUA216: failed to mount on node BEAR -MOUNT-F-CONFQUAL, conflicting qualifiers o Failure of a tape MOUNT would cause MOUNT to retry the MOUNT for 2 minutes before reporting the error to the user and OPCOM. This time is wasted under many circumstances as the drive status will not change without operator intervention. o If the /SYSTEM qualifier was not used when adding a member to an existing shadow set, that was mounted with /SYSTEM, the add appeared to be successful. It was not. The resulting behavior ranges from member copies that never happen ("0% copies") to system crashes. o Since the MOUNT96 rewrite some customers have had an issue with the extended period of time MOUNT attempts retries. When one or more members of a shadowset are offline/unavailable for mounting, a mount of that shadowset is observed to take approximately 2 minutes to complete. This leads to unacceptably long delays in system and application startup completion. Page 3 o Attempting to MOUNT/SYSTEM two ISO-9660 volumes, whose volume labels are not unique in the first 12 characters, results in an "another volume of the same label already mounted" error. Problems addressed in ALPMOUN02_071 kit o Wrong image was placed in the ALPMOUN01_071 kit. This kit fixes that problem. Problems addressed in ALPMOUN01_071 kit o If a DCL 'MOUNT DSAxxx/SHAD' is performed by a process that does not have BYPASS or READALL privileges, the MOUNT will fail if the DSAxxx did not previously exist. If the command is immediately repeated by the same process, it will be successful. 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: 1 : To be installed by all customers. Installation Instructions: Install this kit with the VMSINSTAL utility by logging into the SYSTEM account, and typing the following at the DCL prompt: @SYS$UPDATE:VMSINSTAL ALPMOUN04_071 [location of the saveset] The saveset location may be a tape drive, or a disk directory that contains the kit saveset. No reboot is necessary after successful installation of the kit. Copyright (c) Digital Equipment Corporation, 1998 All Rights Reserved. Unpublished rights reserved under the copyright laws of the United States. Page 4 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. 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.