**************************** ECO SUMMARY INFORMATION **************************** Release Date: 20-MAR-2006 Kit Name: DEC-AXPVMS-VMS732_F11X-V0500--4.PCSI Kit Applies To: OpenVMS ALPHA V7.3-2 Approximate Kit Size: 1888 blocks Installation Rating: INSTALL_1 Reboot Required: Yes - rolling reboot Superseded Kits: VMS732_F11X-V0500 Mandatory Kit Dependencies: VMS732_UPDATE-V0600 VMS732_PCSI-V0200 Optional Kit Dependencies: None VMS732_F11X-V0500.PCSI-DCX_AXPEXE Checksum: 3508535451 DEC-AXPVMS-VMS732_F11X-V0500--4.PCSI Checksum: 3353647637 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= 1 KIT NAME: VMS732_F11X-V0500 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_1 : To be installed by all customers. This 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) 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_F11X-V0500 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-V0200 - VMS732_UPDATE-V0600 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_F11X-V0500 KIT 5.1 New functionality addressed in this kit Not Applicable 5.2 Problems addressed in this kit 5.2.1 SET VOLUME/SIZE command Fails With -SYSTEM-F-BADPARAM 5.2.1.1 Problem Description: A SET VOLUME/SIZE command can fail with a -SYSTEM-F-BADPARAM error. For example: $ SET VOLUME/SIZE $1$DGA1009 %SET-E-NOTSET, error modifying _$1$DGA1009: -SYSTEM-F-BADPARAM, bad parameter value Images Affected: - [SYS$LDR]F11BXQP.EXE - [SYS$LDR]F11BXQP.STB 5.2.1.2 CLDs, and QARs reporting this problem: 5.2.1.2.1 CLD(s) QXCM1000291506, WFM3212323542-321 5.2.1.2.2 QAR(s) None. Page 3 5.2.1.3 Problem Analysis: The volume expansion size is set by the size of the BITMAP.SYS file minus 1, multiplied by the cluster factor, multiplied by 4096. However, MOUNT and the XQP do not share the same limit size value of the volume. If, due to cluster rounding, BITMAP.SYS can map more than %x7FFFE000 blocks, then the expansion size check in EXPAND_VOLUME fails. 5.2.1.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.2 5.2.1.5 Work-arounds: None. 5.2.2 Alignment Faults 5.2.2.1 Problem Description: Utilities that use the ATR$C_ASCDATES (such as SET FILE/EXPIRATION) can cause alignment faults, negatively impacting performance. Images Affected: - [SYS$LDR]F11BXQP.EXE - [SYS$LDR]F11BXQP.STB 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-13-1549 5.2.2.3 Problem Analysis: See problem description. Page 4 5.2.2.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.2 5.2.2.5 Work-arounds: None. 5.2.3 System Crash With "XQPERR, Error Detected By File System XQP" Bugcheck 5.2.3.1 Problem Description: The system can crash with an XQPERR bugcheck: Crashdump Summary Information: ------------------------------ Bugcheck Type: XQPERR, Error detected by file system XQP Current Process: DIR Current Image: DSA3000:[SYS15.SYSCOMMON.] [SYSEXE]DIRECTORY.EXE Failing PC: FFFFFFFF.802265B8 UPDATE_INDX_C+000C8 Failing PS: 18000000.00000000 Module: F11BXQP (Link Date/Time: 1-OCT-2004 19:58:56.24) Offset: 000245B8 Images Affected: - [SYS$LDR]F11BXQP.EXE - [SYS$LDR]F11BXQP.STB 5.2.3.2 CLDs, and QARs reporting this problem: 5.2.3.2.1 CLD(s) QXCM1000298117, WFM3212671160-321 5.2.3.2.2 QAR(s) None. Page 5 5.2.3.3 Problem Analysis: The crash occurs when the directory index cache buffer was initialized for one size of a directory, but the directory now reflects a different size. This is due to some underlying issue such as a disk error or a third party tool causing the wrong information to be retrieved from the volume resulting in a mis-match in the directory. 5.2.3.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.2 5.2.3.5 Work-arounds: None. 5.2.4 System Crash With "WCBFCBMNG, WCB/FCB correspondence" Bugcheck 5.2.4.1 Problem Description: After defragmenting a disk, the system can crash with a WCBFCBMNG bugcheck. In this case, the crash occurred when BACKUP was run against the disk. Crashdump Summary Information: ------------------------------ Bugcheck Type: WCBFCBMNG, WCB/FCB correspondence broken Current Image: DSA17:[SYS0.SYSCOMMON.] [SYSEXE]BACKUP.EXE Failing PC: FFFFFFFF.8020D3F4 REMAP_FILE_C+002D8 Failing PS: 18000000.00000000 Module: F11BXQP (Link Date/Time: 3-AUG-2005 15:19:52.19) Offset: 000093F4 Stack Pointers: KSP = 00000000.7A8D5118 ESP = 00000000.7FF8C000 SSP = 00000000.7FF9CD00 USP = 00000000.7A733168 Images Affected: - [SYS$LDR]F11BXQP.EXE - [SYS$LDR]F11BXQP.STB Page 6 5.2.4.2 CLDs, and QARs reporting this problem: 5.2.4.2.1 CLD(s) QXCM1000307822, WFM3213221705-324 5.2.4.2.2 QAR(s) None. 5.2.4.3 Problem Analysis: When a disk defragmenter consolidates map pointers, the header may be improperly modified (by the defragger, not the file system) such that two map pointers are adjacent (count + LBN = LBN of next pointer). In a counting error, the code to remap the WCB in memory to a single pointer counts the blocks twice. The WCBFCBMNG bugcheck occurs when the file system verifies the size versus the count fields. 5.2.4.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.2 5.2.4.5 Work-arounds: None. 5.2.5 Invalid Device Incorrectly Marked As Valid 5.2.5.1 Problem Description: If a device goes into mount verification, it is possible that the device will be incorrectly marked as valid after mount verification has timed out. Since this happens outside of mount verification, there is some possibility that the volume checks could have failed and the volume should not be used. For example, if a volume is marked as mvtimeout on most systems in a cluster, but is still valid on one system, there exists a window such that the volumes marked as mvtimeout could show as mounted. Images Affected: - [SYS$LDR]F11BXQP.EXE - [SYS$LDR]F11BXQP.STB Page 7 - [SYSEXE]VERIFY.EXE 5.2.5.2 CLDs, and QARs reporting this problem: 5.2.5.2.1 CLD(s) None. 5.2.5.2.2 QAR(s) 75-109-941 5.2.5.3 Problem Analysis: See Problem Description. 5.2.5.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.2 5.2.5.5 Work-arounds: None. 5.2.6 "XQPERR, Error detected by file system XQP" bugcheck. 5.2.6.1 Problem Description: The system can crash with an "XQPERR, Error detected by file system XQP" bugcheck. Images Affected: - [SYS$LDR]F11BXQP.EXE - [SYS$LDR]F11BXQP.STB 5.2.6.2 CLDs, and QARs reporting this problem: Page 8 5.2.6.2.1 CLD(s) None. 5.2.6.2.2 QAR(s) 75-109-1123 5.2.6.3 Problem Analysis: The code that checks for the volume size change obtains the volume allocation lock. If the volume data has changed such that it effectively destroys the volume, instead of this error being signaled, it is ignored. This causes an XQPERR bugcheck 'downstream' when it is detected that the allocation lock is not held. This failure would likely be seen with a RAMDISK device when the hosting system is rebooted and the actual data is invalidated. 5.2.6.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.2 5.2.6.5 Work-arounds: None. 5.2.7 Logical Volume Size Larger Than Total Blocks 5.2.7.1 Problem Description: A SHOW DEVICE command can show a logical volume size that is greater than the volume total blocks: Total blocks 17773524 Sectors per track 168 Total cylinders 5290 Tracks per cylinder 20 Logical Volume Size 17842176 Expansion Size Limit 2148507648 Images Affected: - [SYSEXE]VERIFY.EXE Page 9 5.2.7.2 CLDs, and QARs reporting this problem: 5.2.7.2.1 CLD(s) 70-3-8322 5.2.7.2.2 QAR(s) None. 5.2.7.3 Problem Analysis: When the VERIFY utility checks the volume characteristics, it could detect that the information in the SCB does not match what $GETDVI is stating. This could result in a "%VERIFY-W-CHKSCB, invalid storage control block, RVN 1" error message. During the processing of this condition, the SCB volume size could be set too large. SHOW DEVICE would then show the logical volume size to be greater than the volume total blocks. 5.2.7.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.2 5.2.7.5 Work-arounds: None. 5.2.8 Device and/or System Hang During ANALYZE/DISK/REPAIR 5.2.8.1 Problem Description: If a batch job is submitted to do a ANALYZE/DISK/REPAIR and the log file is on the same device as the target of the repair, it is possible to hang the device (and possibly the system) when there is an attempt to extend the log file. With this change, the error message: %ANALDISK-F-SAMEDEVICE, you cannot write output to the disk you are repairing will be displayed before the volume can be locked. Images Affected: Page 10 - [SYSEXE]VERIFY.EXE 5.2.8.2 CLDs, and QARs reporting this problem: 5.2.8.2.1 CLD(s) None. 5.2.8.2.2 QAR(s) None. 5.2.8.3 Problem Analysis: See problem description 5.2.8.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.2 5.2.8.5 Work-arounds: None. 5.2.9 VERIFY may report ANALDISK-W-BACKLINK 5.2.9.1 Problem Description: With hard links enabled, VERIFY may report ANALDISK-W-BACKLINK, as shown in the following example: 1. CREATE a file REAL.FILE (14,1,0) in TEST.DIR (13,1,0) and then create two alias entries (SET FILE /ENTER) for REAL.FILE. - the link count for (14,1,0) = 3 - the back link for (14,1,0) is (13,1,0) - VERIFY runs clean 2. DELETE the primary file (REAL.FILE). - the link count for (14,1,0) = 2 - the back link for (14,1,0) changes to (16777215,0,0) Page 11 - VERIFY runs clean 3. Remove (SET FILE /REMOVE) the first linked file. - the link count for (14,1,0) = 1 - the back link for (14,1,0) changes to (0,0,0) - VERIFY reports %ANALDISK-W-BACKLINK and the file is entered into [SYSLOST]: %ANALDISK-W-BACKLINK, directory (13,1,0) TEST.DIR;1 incorrect back link for entry REAL.FILE;1 Since (14,1,0) is still entered in a directory, you would not expect the BACKLINK warning and the file being entered into [SYSLOST]. With this change, VERIFY will not issue the BACKLINK warning for a file with back link (0,0,0) and a non-zero link count. The new behavior is: 1. CREATE a file REAL.FILE (14,1,0) in TEST.DIR (13,1,0) and then create two alias entries (SET FILE /ENTER) for REAL.FILE. - the link count for (14,1,0) = 3 - the back link for (14,1,0) is (13,1,0) - VERIFY runs clean 2. DELETE the primary file (REAL.FILE). - the link count for (14,1,0) = 2 - the back link for (14,1,0) changes to (16777215,0,0) - VERIFY runs clean 3. Remove (SET FILE /REMOVE) the first linked file. - the link count for (14,1,0) = 1 - the back link for (14,1,0) changes to (0,0,0) - VERIFY runs clean Page 12 4. Remove (SET FILE /REMOVE) the second linked file. - the link count for (14,1,0) = 0 - the back link for (14,1,0) is still (0,0,0) - VERIFY reports %ANALDISK-W-BACKLINK and the file is entered into [SYSLOST]: %ANALDISK-W-LOSTHEADER, file (14,1,0) REAL.FILE;1 not found in a directory Images Affected: - [SYSEXE]VERIFY.EXE 5.2.9.2 CLDs, and QARs reporting this problem: 5.2.9.2.1 CLD(s) None. 5.2.9.2.2 QAR(s) 75-13-1581 5.2.9.3 Problem Analysis: See problem description. 5.2.9.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.2 5.2.9.5 Work-arounds: None. 6 PROBLEMS ADDRESSED IN PREVIOUS KITS Problems addressed by previously released VMS732_F11X ECO kits can be found in the following files: o VMS732_F11X-V0400.RELEASE_NOTES Page 13 o VMS732_F11X-V0300.RELEASE_NOTES o VMS732_F11X-V0200.RELEASE_NOTES o VMS732_F11X-V0100.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_F11X/VERSION=V5.0- /DESTINATION= destination_directory o To extract a single release notes file use: PRODUCT EXTRACT FILE VMS732_F11X/VERSION=V5.0 - /SELECT=[SYSUPD]release_note_name/DESTINATION=destination_directory 7 FILES PATCHED OR REPLACED: o [SYS$LDR]F11BXQP.EXE (new image) Image Identification Information image name: "F11BXQP" image file identification: "XQP V73-2R A99" image file build identification: "XA99-0060110034" link date/time: 30-JAN-2006 13:25:07.41 linker identification: "A11-50" Overall Image Checksum: 4181514658 o [SYSEXE]VERIFY.EXE (new image) Image Identification Information image name: "VERIFY" image file identification: "X-23" image file build identification: "XA99-0060110012" link date/time: 22-DEC-2005 07:09:43.45 linker identification: "A11-50" Overall Image Checksum: 1081451474 o [SYS$LDR]F11BXQP.STB (new file) Page 14 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: 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 DCX compressed kit. To expand this file to the installable .PCSI file, run the file with a RUN file_name command. When the file is run you will see the following output: $ RUN VMS732_F11X-V0500.PCSI-DCX_AXPEXE FTSV DCX auto-extractible compressed file for OpenVMS (AXP) FTSV V3.0 -- FTSV$DCX_AXP_AUTO_EXTRACT Copyright (c) Digital Equipment Corp. 1993 Options: [output_file_specification] [input_file_specification] The decompressor needs to know the filename to use for the decompressed file. If you don't specify any, it will use the original name of the file before it was compressed, and create it in the current directory. If you specify a directory name, the file will be created in that directory. Decompress into (file specification): If you want the file to be expanded into a different directory, enter the directory specification. DO NOT enter a new file name. The expanded file must retain the original name. If you want to expand the file via batch, the command file must contain an answer to the"Decompress into (file specification)" question, either a or an alternate directory specification Page 15 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_F11X[/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: 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=V5.0 [/SOURCE=location of Kit] Page 16 o De-assign the logical names assigned For example, a sample command file to install the VMS732_F11X-V0500 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS732_F11X/PRODUCER=DEC/BASE=AXPVMS/VER=V5.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. 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.