**************************** ECO SUMMARY INFORMATION **************************** Release Date: 26-AUG-2004 Kit Name: DEC-AXPVMS-VMS731_F11X-V0400--4.PCSI Kit Applies To: OpenVMS ALPHA V7.3-1 Approximate Kit Size: 1232 blocks Installation Rating: INSTALL_1 Superseded Kits: VMS731_F11X-V0300 Mandatory Kit Dependencies: VMS731_UPDATE-V0400 VMS731_PCSI-V0200 Optional Kit Dependencies: None. VMS731_F11X-V0400.PCSI-DCX_AXPEXE Checksum: 2208065546 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= ECO NUMBER: VMS731_F11X-V0400 PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3-1 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3-1 1 KIT NAME: VMS731_F11X-V0400 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-1 2.4 New functionality or new hardware support provided: No. 3 KITS SUPERSEDED BY THIS KIT: - VMS731_F11X-V0300 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS731_PCSI-V0200 - VMS731_UPDATE-V0400 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 FILES PATCHED OR REPLACED: o [SYS$LDR]F11BXQP.EXE (new image) Image Identification Information image name: "F11BXQP" image file identification: "XQP V73-1R A2Q" image file build identification: "XA2Q-0060030019" link date/time: 15-JUL-2004 16:51:48.35 linker identification: "A11-50" Overall Image Checksum: 1729248997 o [SYS$LDR]F11BXQP.STB (new file) 6 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS731_F11X-V0400 KIT 6.1 New functionality addressed in this kit None. 6.2 Problems addressed in this kit 6.2.1 System crash with an XQPERR bugcheck 6.2.1.1 Problem Description: A bound volume set can crash with an XQPERR bugcheck. Crashdump Summary Information ---------------------------- Bugcheck Type: XQPERR, Error detected by file system XQP VMS Version: V7.3-1 Current Process: WSSTST9MAINT Current Image: $1$DUA200:[SYS0.SYSCOMMON.] [SYSEXE]SHOW.EXE Failing PC: FFFFFFFF.80234708 SEARCH_FCB_C+00EE8 Failing PS: 00000000.00000000 Module: F11BXQP (Link Date/Time: 17-MAR-2004 12:16:07.28) Offset: 00014708 Page 3 Stack Pointers: KSP = 00000000.75FC0B80 ESP = 00000000.7FFA6000 SSP = 00000000.7FFAC100 USP = 00000000.75DE7160 Images Affected: - [SYS$LDR]F11BXQP.EXE - [SYS$LDR]F11BXQP.STB 6.2.1.2 CLDs, and QARs reporting this problem: 6.2.1.2.1 CLD(s) 70-3-7981,CFS.107294 6.2.1.2.2 QAR(s) None. 6.2.1.3 Problem Analysis: When a file is being examined by an FID_TO_SPEC operation, there is a need to release the FCB while backing up the chain. This requires that the FCB be left with an incremented reference count. Upon restoring the reference count, FID_TO_SPEC may not cause the deletion of the FCB, leaving it unreferenced and effectively stale. 6.2.1.4 Release Version of OpenVMS that will contain this change: Next release after V7.3-2 6.2.1.5 Work-arounds: None. 6.2.2 VERIFY command returns ANALDISK-W-CHKALTHOME errors Page 4 6.2.2.1 Problem Description: A VERIFY command returns errors similar to the following on a volume mounted with a reduced XQP buffer cache (%MOUNT-I-REDCACHE): Analyze/Disk_Structure for _$2$MDA0: started on ... %ANALDISK-W-READHEADER, file (16777215,65535,255) file header read error %ANALDISK-W-CHKALTHOME, invalid alternate home block, VBN 3, RVN 1 %ANALDISK-W-CHKALTHOME, invalid alternate home block, VBN 4, RVN 1 %ANALDISK-W-CHKALTHOME, invalid alternate home block, VBN 5, RVN 1 %ANALDISK-W-CHKALTHOME, invalid alternate home block, VBN 6, RVN 1 %ANALDISK-W-CHKALTHOME, invalid alternate home block, VBN 7, RVN 1 %ANALDISK-W-CHKALTHOME, invalid alternate home block, VBN 8, RVN 1 %ANALDISK-W-CHKALTHOME, invalid alternate home block, VBN 9, RVN 1 %ANALDISK-I-OPENQUOTA, error opening QUOTA.SYS -SYSTEM-W-NOSUCHFILE, no such file %ANALDISK-W-READHEADER, file (24129,43690,1) file header read error -SYSTEM-W-ENDOFFILE, end of file %ANALDISK-W-READHEADER, file (24130,43690,1) file header read error -SYSTEM-W-ENDOFFILE, end of file Images Affected: - [SYS$LDR]F11BXQP.EXE - [SYS$LDR]F11BXQP.STB 6.2.2.2 CLDs, and QARs reporting this problem: 6.2.2.2.1 CLD(s) 70-3-8000,CFS.107422 Page 5 6.2.2.2.2 QAR(s) None. 6.2.2.3 Problem Analysis: The first READHEADER message is in reference to INDEXF.SYS. The buffer returned by the XQP was not a file header but something that looked more like a storage bitmap block. The CHKALTHOME messages are caused by bogus map pointer information obtained from this bogus file header. 6.2.2.4 Release Version of OpenVMS that will contain this change: Next release after V7.3-2 6.2.2.5 Work-arounds: None. 6.2.3 Case blind matches less than the exact name are not returned. 6.2.3.1 Problem Description: A case blind lookup using IO$_ACCESS with FIB$V_SEARCH initially (with FIB$L_WCC = 0) returns an exact match (if one exists). Subsequent lookups (after WCC is established) correctly return any case blind matches that are greater than the exact name. However, any case blind matches which are less than the exact name are, erroneously, not returned. For example, given the names: MIXED.CASE MIXEd.CASE MIXed.CASE MIxed.CASE Mixed.CASE mixed.CASE A test program which passes MIxed.CASE as the filename returns: Located the file MIxed.CASE;1 Located the file Mixed.CASE;1 Located the file mixed.CASE;1 Note that MIXED.CASE, MIXEd.CASE, and MIXed.CASE are not returned. These names precede the exact name match. With this change, all case blind matches will be returned. Page 6 Images Affected: - [SYS$LDR]F11BXQP.EXE - [SYS$LDR]F11BXQP.STB 6.2.3.2 CLDs, and QARs reporting this problem: 6.2.3.2.1 CLD(s) None. 6.2.3.2.2 QAR(s) 75-83-1407 6.2.3.3 Problem Analysis: FND_SEARCH_MODE was not set for FIB$L_WCC = 0. 6.2.3.4 Release Version of OpenVMS that will contain this change: Next release after V7.3-2 6.2.3.5 Work-arounds: None. 7 PROBLEMS ADDRESSED IN PREVIOUS KITS Problem addressed in previously released VMS731_F11X kits can be found in the following files: o [SYSHLP]VMS731_F11X-V0300.RELEASE_NOTES o [SYSHLP]VMS731_F11X-V0200.RELEASE_NOTES o [SYSHLP]VMS731_F11X-V0100.RELEASE_NOTES 8 INSTALLATION INSTRUCTIONS Page 7 8.1 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 VMS731_F11X-V0400.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 8.2 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 VMS731_F11X /SAVE_RECOVERY_DATA [/SOURCE=location of Kit] 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. Page 8 8.3 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=V4.0/SAVE_RECOVERY_DATA o De-assign the logical names assigned For example, a sample command file to install the VMS731_F11X-V0400 kit would be: $ $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS731_F11X/PRODUCER=DEC/BASE=AXPVMS- /VER=V4.0/SAVE_RECOVERY_DATA $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit Page 9 9 COPYRIGHT AND DISCLAIMER: (C) Copyright 2004 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.