OpenVMS] VMS72_MOUNT96-V0100 Alpha V72 MOUNT ECO Summary

TITLE: OpenVMS] VMS72_MOUNT96-V0100 Alpha V72 MOUNT ECO Summary Modification Date: 23-JUN-99 Modification Type: New Kit NOTE: An OpenVMS saveset or PCSI installation file is stored on the Internet in a self-expanding compressed file. The name of the compressed file will be kit_name-dcx_vaxexe for OpenVMS VAX or kit_name-dcx_axpexe for OpenVMS Alpha. Once the file is copied to your system, it can be expanded by typing RUN compressed_file. The resultant file will be the OpenVMS saveset or PCSI installation file which can be used to install the ECO. Copyright (c) Compaq Computer Corporation 1999. All rights reserved. OP/SYS: OpenVMS Alpha COMPONENT: Mount MOUNTSHR VMOUNT SYSMSG MOUNT.CLD SOURCE: Compaq Computer Corporation ECO INFORMATION: ECO Kit Name: VMS72_MOUNT96-V0100 DEC-AXPVMS-VMS72_MOUNT96-V0100--4.PCSI ECO Kits Superseded by This ECO Kit: None ECO Kit Approximate Size: 1344 Blocks Kit Applies To: OpenVMS Alpha V7.2 System/Cluster Reboot Necessary: Yes Rolling Re-boot Supported: Yes Installation Rating: INSTALL_3 3 - To be installed on all systems running the listed versions of OpenVMS which are experiencing the problems described. Kit Dependencies: The following remedial kit(s) must be installed BEFORE installation of this kit: None In order to receive all the corrections listed in this kit, the following remedial kits should also be installed: None ECO KIT SUMMARY: An ECO kit exists for the MOUNT utility on OpenVMS Alpha V7.2. This kit addresses the following problems: 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. 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 systems 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 the following warning message rather than a fatal error: %MOUNT-W-INCONSIZE, inconsistent number of blocks reported, some data may not be accessible 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 Previously, a fix was included to address a problem in which 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. 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 systems unable to MOUNT multiple CDROMS have been attributed to this problem. Due to the problems that it caused, the original fix has been removed. 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: + /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. + /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 incorrect disks being added to shadow set is mistyped commands. Less data will be lost if only "scratch" disks can be added to shadow sets. This is similar to the /CONFIRM switch, 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 INSTALLATION NOTES: The images in this kit will not take effect until the system is rebooted. If there are other nodes in the VMScluster, 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 rolling re-boot may be performed. All trademarks are the property of their respective owners.

This patch can be found at any of these sites:

Files on this server are as follows:

dec-axpvms-vms72_mount96-v0100--4.README
dec-axpvms-vms72_mount96-v0100--4.CHKSUM
dec-axpvms-vms72_mount96-v0100--4.pcsi-dcx_axpexe
vms72_mount96-v0100.CVRLET_TXT