ECO NUMBER: VMS72_MOUNT96-V0100 PRODUCT: OpenVMS VMS ALPHA OPERATING SYSTEM V7.2 UPDATE PRODUCT: OpenVMS VMS ALPHA OPERATING SYSTEM V7.2 COVER LETTER 1 KIT NAME: VMS72_MOUNT96-V0100 2 KITS SUPERSEDED BY THIS KIT: None. 3 KIT DEPENDENCIES: 3.1 The following remedial kit(s) must be installed BEFORE installation of this, or any required kit: None. 3.2 In order to receive all the corrections listed in this kit, the following remedial kits should also be installed: None. 4 KIT DESCRIPTION: 4.1 Version(s) of OpenVMS to which this kit may be applied: OpenVMS Alpha V7.2 4.2 Files patched or replaced: o [SYSLIB]MOUNTSHR.EXE (new image) o [SYSEXE]VMOUNT.EXE (new image) o [SYSMSG]SYSMSG.EXE (new image) o [SYSUPD]MOUNT.CLD (update to DCLTABLES) 5 PROBLEMS ADDRESSED IN VMS72_MOUNT96-V0100 KIT o OpenVMS V7.2 provided a new check to determine if the disk that is being MOUNTed was initialized to a size that is larger than the number of blocks that are now available. -- COVER LETTER -- Page 2 9 June 1999 This size discrepancy occurs when a disk is moved from one controller type to another (for example, from a local SCSI connection to an HSJ) without the disk being initialized on the new controller. As a result, some data may be inaccessible through the new controller. If this condition was detected, then a fatal MOUNT-F-FILESTRUCT error was reported and the MOUNT was aborted. It has been determined that a number of customers are running with disks which are in this condition. While there may be data that is inaccessible on the disk, the usefulness of the disk should be left to the discretion of the system manager. Therefore, this change makes this condition issue a warning message: %MOUNT-W-INCONSIZE, inconsistent number of blocks reported, some data may not be accessible rather than a fatal error. It is recommended that the BACKUP utility be used to move data from a disk on one controller type to a disk on another controller type, especially if those controllers report a different number of blocks available for the same disk type. Once the data has been moved, the physical disk can be moved and initialized on the new controller. Images Affected: - [SYSLIB]MOUNTSHR.EXE - [SYSEXE]VMOUNT.EXE - [SYSMSG]SYSMSG.EXE o An ILLQUAL error is being reported in OpenVMS Alpha V7.2 when MOUNT/MEDIA_FORMAT=COMPACTION is specified without a /FOREIGN or /INIT=ALL qualifier. Images Affected: - [SYSLIB]MOUNTSHR.EXE - [SYSEXE]VMOUNT.EXE o A change was made last fall to fix a problem where SWL disks do not come out of mount verification properly. The fix insured that the VCB$T_VOLOCKNAM matches the SCB$_VOLOCKNAME of the volume, even for privately mounted disks. However, if a member of a shadow set is removed from the set for BACKUPs, then both the still-mounted shadow set and the privately mounted former member will have the same VCB$T_VOLOCKNAMs. -- COVER LETTER -- Page 3 9 June 1999 This causes a variety of symptoms, including access conflicts during BACKUPs of the former member and in at least one case, an XQPERR, Error detected by file system XQP bugcheck at F11BXQP_PRO+0BE48. In addition, reports of customers unable to MOUNT multiple CDROMs have been attributed to this problem. The original fix has been removed to fix these problems. As a result, the original problem may still occur. If a disk is write-locked, it will not successfully complete mount verification. The device will be marked as "wrong volume". Compaq OpenVMS Engineering continues to research solutions to this problem. Images Affected: - [SYSLIB]MOUNTSHR.EXE - [SYSEXE]VMOUNT.EXE o /MEDIA_FORMAT and /DENSITY qualifiers are not always handled properly, resulting in tapes being written in different modes than intended. Images Affected: - [SYSLIB]MOUNTSHR.EXE - [SYSEXE]VMOUNT.EXE o The following switches and options have been added to the MOUNT command: o /POLICY=REQUIRE_MEMBERS This forces all specified members to be available for MOUNT to occur. This switch is used in disaster-tolerant configurations where another site may have a more recent disk that is not available. In effect, this will force more human decision making. o /POLICY=VERIFY_LABELS All copy targets must have the label 'SCRATCH_DISK' or they will not be added to the set. The volume must be ODS2 and have a valid file structure. This change starts forcing users to use alternate volume labels. One of the biggest causes of "I just added the wrong disk to a shadow set" complaints is mis-typed commands. If the customers are given a way to be sure that they only add "scratch" disks to shadow sets, then perhaps customers will be less likely -- COVER LETTER -- Page 4 9 June 1999 to lose data. This is similar to the /CONFIRM, except that it can be used in command procedures as well, without immediate operator intervention. It is also similar to the /NOCOPY command, except it allows copies to occur, as long as the label is 'scratch'. Images Affected: - [SYSLIB]MOUNTSHR.EXE - [SYSEXE]VMOUNT.EXE - [SYSMSG]SYSMSG.EXE - [SYSLIB]DCLTABLES.EXE 6 KIT INSTALLATION RATING: The following kit installation rating, based upon current CLD information, is provided to serve as a guide to which customers should apply this remedial kit. (Reference attached Disclaimer of Warranty and Limitation of Liability Statement) INSTALLATION RATING: INSTALL_3 : To be installed by customers experiencing the problems corrected. 7 INSTALLATION INSTRUCTIONS: Install this kit with the PCSI utility by logging into the SYSTEM account, and typing the following at the DCL prompt: PRODUCT INSTALL VMS72_MOUNT96 /SOURCE=[location of Kit] The kit location may be a tape drive, CD, or a disk directory that contains the kit. Additional help on installing PCSI kits can be found by typing HELP PRODUCT INSTALL at the system prompt The images in this kit will not take effect until the system is rebooted. If you have other nodes in your OpenVMS cluster, they must also be rebooted in order to make use of the new image(s). If it is not possible or convenient to reboot the entire cluster at this time, a -- COVER LETTER -- Page 5 9 June 1999 rolling re-boot may be performed. Copyright (c) Compaq Computer Corporation, 1999 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 Compaq Computer Corporation. Possession, use, or dissemination of the software and media is authorized only pursuant to a valid written license from Compaq Computer 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 COMPAQ 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.