**************************** ECO SUMMARY INFORMATION **************************** Release Date: 21-DEC-2006 Kit Name: DEC-AXPVMS-VMS732_MOUNT96-V0200--4.PCSI$COMPRESSED Kit Applies To: OpenVMS ALPHA V7.3-2 Approximate Kit Size: 1849 blocks Installation Rating: INSTALL_3 Reboot Required: Yes - rolling reboot Superseded Kits: VMS732_MOUNT96-V0100 Mandatory Kit Dependencies: VMS732_UPDATE-V0900 or later VMS732_PCSI-V0300 or later Optional Kit Dependencies: None Checksums: VMS732_MOUNT96-V0200.ZIPEXE Checksum: 29184710 DEC-AXPVMS-VMS732_MOUNT96-V0200--4.PCSI$COMPRESSED Checksum: 3421474308 VMS732_MOUNT96-V0200.ZIPEXE MD5 Checksum: A6177AC502DC978BC1065A5549F8E9C5 DEC-AXPVMS-VMS732_MOUNT96-V0200--4.PCSI$COMPRESSED MD5 Checksum: C851E16A1E6B5E1A6799088A96AFA376 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= 1 KIT NAME: VMS732_MOUNT96-V0200 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_3 : To be installed by customers experiencing the problems corrected. 2.2 Reboot Requirement: Reboot Required. HP strongly recommends that a reboot is performed immediately after kit installation to avoid system instability. 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 rolling re-boot may be performed. 2.3 Version(s) of OpenVMS to which this kit may be applied: OpenVMS ALPHA V7.3-2 2.4 New functionality or new hardware support provided: No 3 KITS SUPERSEDED BY THIS KIT: - VMS732_MOUNT96-V0100 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS732_PCSI-V0300 - VMS732_UPDATE-V0900 Page 2 4.2 In order to receive all the corrections listed in this kit, the following remedial kits, or later, should also be installed: - None 5 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS732_MOUNT96-V0200 KIT 5.1 New functionality addressed in this kit Not Applicable 5.2 Problems addressed in this kit 5.2.1 Caching Turned Off on SECURITY.SYS File 5.2.1.1 Problem Description: If the SECURITY.SYS file on a disk was created by MOUNT96 (an old disk now being mounted on the current version) or if a BACKUP/IMAGE restore was performed, XFC may turn caching on for the file. This can result in stale data. Images Affected: - [SYSLIB]MOUNTSHR.EXE 5.2.1.2 CLDs, and QARs reporting this problem: 5.2.1.2.1 CLD(s) None. 5.2.1.2.2 QAR(s) None. 5.2.1.3 Problem Analysis: MOUNT will now check the caching characteristics of SECURITY.SYS and if caching is enabled, MOUNT will disable it. Page 3 5.2.1.4 Release Version of OpenVMS that will contain this change: OpenVMS Alpha V8.2 5.2.1.5 Work-arounds: None. 5.2.2 INIT/ERASE Command Hangs 5.2.2.1 Problem Description: If an INIT/ERASE command is executed on a disk that is MSCP served and the host system is shutdown or removed, the local INIT will appear to hang with no error message. Images Affected: - [SYSLIB]INIT$SHR.EXE - [SYSLIB]MOUNTSHR.EXE - [SYSMSG]SYSMSG.EXE 5.2.2.2 CLDs, and QARs reporting this problem: 5.2.2.2.1 CLD(s) None. 5.2.2.2.2 QAR(s) 75-107-76 5.2.2.3 Problem Analysis: The ERASE code ignored error returned in the IOSB of the $QIO where normally this type of error is returned via the $QIO status. 5.2.2.4 Release Version of OpenVMS that will contain this change: OpenVMS Alpha V8.2 Page 4 5.2.2.5 Work-arounds: None. 5.2.3 INIT/LIMIT and SET VOL/LIMIT Commands Set Value Incorrectly 5.2.3.1 Problem Description: INIT/LIMIT and SET VOL/LIMIT commands fail to set the value correctly. Images Affected: - [SYSLIB]MOUNTSHR.EXE 5.2.3.2 CLDs, and QARs reporting this problem: 5.2.3.2.1 CLD(s) QXCM1000300505,WFM1209318085-121 5.2.3.2.2 QAR(s) None. 5.2.3.3 Problem Analysis: When a disk is initialized with a large cluster size the calculation of bitmap size times cluster size can overflow the 32 bit field of vcb$l_expsize. 5.2.3.4 Release Version of OpenVMS that will contain this change: OpenVMS Alpha V8.3 5.2.3.5 Work-arounds: None. 5.2.4 Disk Can not be mounted After Initialization. Page 5 5.2.4.1 Problem Description: After initializing a large volume, the disk may not be able to be mounted. Images Affected: - [SYSEXE]VMOUNT.EXE - [SYSLIB]MOUNTSHR.EXE - [SYSEXE]SET.EXE - [SYSEXE]SYSINIT.EXE - [SYSEXE]DISKQUOTA.EXE 5.2.4.2 CLDs, and QARs reporting this problem: 5.2.4.2.1 CLD(s) QXCM1000340264,WFM3214952692-321 5.2.4.2.2 QAR(s) 75-13-1649 5.2.4.3 Problem Analysis: For large values of cluster size and volume size, dividends of the form (cluster size + volume size) will yield incorrect results if the dividend overflows to bit 32. 5.2.4.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.4.5 Work-arounds: None. 6 PROBLEMS ADDRESSED IN PREVIOUS KITS Problems addressed by previously released VMS732_MOUNT96 ECO kits can be found in the following files: Page 6 o VMS732_MOUNT96-V100.RELEASE_NOTES Before kit installation, these files can be extracted from the kit via the following commands: o To extract all release notes files at once use: PRODUCT EXTRACT RELEASE_NOTES VMS732_MOUNT96/VERSION= - /DESTINATION= destination_directory o To extract a single release notes file use: PRODUCT EXTRACT FILE VMS732_MOUNT96/VERSION= V2.0 - /SELECT=[SYSUPD]release_note_name/DESTINATION=destination_directory 7 FILES PATCHED OR REPLACED: o [SYSEXE]DISKQUOTA.EXE (new image) Image Identification Information image name: "DISKQUOTA" image file identification: "X-6" image file build identification: "XBCV-0060110000" link date/time: 10-OCT-2006 08:48:33.17 linker identification: "A11-50" Overall Image Checksum: 1253803048 o [SYSLIB]INIT$SHR.EXE (new image) Image Identification Information image name: "INIT$SHR" image file identification: "X-6" image file build identification: "XBC9-0060111004" link date/time: 21-AUG-2006 10:13:38.92 linker identification: "A11-50" Overall Image Checksum: 3062637251 o [SYSLIB]MOUNTSHR.EXE (new image) Image Identification Information image name: "MOUNTSHR" image file identification: "X-6" image file build identification: "XBC9-SSB-0000" link date/time: 26-JUL-2006 09:45:45.35 linker identification: "A11-50" Overall Image Checksum: 3502971229 o [SYSEXE]SET.EXE (new image) Image Identification Information Page 7 image name: "SET" image file identification: "X01-13" image file build identification: "XBCV-0060111015" link date/time: 19-SEP-2006 13:03:41.10 linker identification: "A11-50" Overall Image Checksum: 3398505837 o [SYSEXE]SYSINIT.EXE (new image) Image Identification Information image name: "SYSINIT" image file identification: "X-100A1A1" image file build identification: "XBCV-0060111005" link date/time: 10-OCT-2006 08:48:39.14 linker identification: "A11-50" Overall Image Checksum: 3057784084 o [SYSMSG]SYSMSG.EXE (new image) Image Identification Information image name: "SYSMSG" image file identification: "X-9" image file build identification: "XA99-0060111007" link date/time: 14-JUN-2006 13:19:00.77 linker identification: "A11-50" Overall Image Checksum: 1315705248 o [SYSEXE]VMOUNT.EXE (new image) Image Identification Information image name: "VMOUNT" image file identification: "X-10" image file build identification: "XBC9-SSB-0000" link date/time: 26-JUL-2006 09:47:43.31 linker identification: "A11-50" Overall Image Checksum: 4218542227 8 INSTALLATION INSTRUCTIONS 8.1 Test/Debug Image Loss In the course of debugging problems reported to OpenVMS Engineering, customers may be given debug or point-fix images to install. Typically, these images do not have the same image generation flags contained in images released via the OpenVMS remedial patch process. Because of this, any debug or point-fix image that is in the SYS$COMMON area, will be replaced by any image of the same name installed by this kit. If this occurs, you will lose any functionality that is provided by the replaced image. If you wish to retain these debug or point-fix images, you can take the following steps: Page 8 o Prior to installing this kit, move the test/debug image(s) to be saved to the SYS$SPECIFIC area. o During kit installation, you will be asked if you wish to delete the image(s) in SYS$SPECIFIC. You should answer NO for each image that you want to keep. o After installation completes, but before rebooting the system (if required), move the image(s) from SYS$SPECIFIC back to SYS$COMMON. 8.2 Compressed File This kit is provided as a Self Extracting ZIPEXE kit. To expand this file to the installable .PCSI file, run the file with the following command: $ RUN VMS732_MOUNT96-V0200.ZIPEXE 8.3 Installation Command Install this kit with the POLYCENTER Software installation utility by logging into the SYSTEM account, and typing the following at the DCL prompt: PRODUCT INSTALL VMS732_MOUNT96[/SOURCE=location of Kit] Note that this kit will install with the /SAVE_RECOVERY_DATA option turned on. Using this qualifier will allow easy removal of the kit from the system in the event of problems. If you wish to disable this option you must use the /NOSAVE_RECOVERY_DATA qualifier on the PRODUCT INSTALL command. The /SAVE_RECOVERY_DATA qualifier is optional but highly recommended. Using this qualifier will allow easy removal of the kit from the system in the event of problems. The kit location may be a tape drive, CD, or a disk directory that contains the kit. The /SOURCE qualifier is not needed if the PRODUCT INSTALL command is executed from the same directory as the kit location. Additional help on installing PCSI kits can be found by typing HELP PRODUCT INSTALL at the system prompt. 8.4 Scripting of Answers to Installation Questions During installation, this kit will ask and require user response to several questions. If you wish to automate the installation of this kit and avoid having to provide responses to these questions, you must create a DCL command procedure that includes the following logical name definitions and commands: Page 9 o To avoid the BACKUP question, define the following: $ DEFINE/SYS NO_ASK$BACKUP TRUE o To avoid the REBOOT question, define the following: $ DEFINE/SYS NO_ASK$REBOOT TRUE o To save replaced files as *.*_OLD define the following logical name as YES. If you do not wish to save replaced files, define the logical name as NO. Note that if you use the /SAVE_RECOVERY_DATA qualifier (recommended) on the PRODUCT INSTALL command all replaced files will be saved as part of that operation. There is no need to also save files as *.*_OLD: $ DEFINE/JOB ARCHIVE_OLD NO o Add the following qualifiers to the PRODUCT INSTALL command and add that command to the DCL procedure. /PROD=DEC/BASE=AXPVMS/VER=V2.0 [/SOURCE=location of Kit] o De-assign the logical names assigned For example, a sample command file to install the VMS732_MOUNT96-V0200 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS732_MOUNT96/PRODUCER=DEC/BASE=AXPVMS/VER=V2.0" $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit $! 9 COPYRIGHT AND DISCLAIMER: (C) Copyright 2006 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP and/or its subsidiaries required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Page 10 Neither HP nor any of its subsidiaries shall be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for HP products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty. 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 HP 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.