======================================================================= Hewlett-Packard OpenVMS ECO Release Notes ======================================================================= 1 KIT NAME: VMS84I_F11X-V0200 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 for Integrity Servers V8.4 2.4 New functionality or new hardware support provided: No 3 KITS SUPERSEDED BY THIS KIT: - VMS84I_F11X-V0100 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS84I_PCSI-V0400 - VMS84I_UPDATE-V0700 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 VMS84I_F11X-V0200 KIT 5.1 New functionality addressed in this kit Not Applicable 5.2 Problems addressed in this kit 5.2.1 System crash XQPERR, Error detected by file system XQP 5.2.1.1 Problem Description: Under rare circumstances, an XQPERR bugcheck with an error status of IVLOCKID (Invalid Lock Id) can occur during a dismount. Images Affected: - [SYS$LDR]F11BXQP.EXE - [SYS$LDR]F11BXQP.STB 5.2.1.2 Quix and PTR cases reporting this problem: 5.2.1.2.1 Quix Cases QXCM1000750135,QXCM1000969153 QXCM1001000418,QXCM1001154739 5.2.1.2.2 PTR(s) 75-13-2453 5.2.1.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.4 Page 3 5.2.1.4 Work-arounds: None 5.2.2 Directory files getting corrupted, if disk defragmenter tool like DFO is being used 5.2.2.1 Problem Description: There is a potential that if directory file is moved back and forth using MOVEFILE subfunction, and file creation/deletion operations were done on that directory at the same time, then directory file might get corrupted. The corruption symptoms are - a) File names not appearing in alphanumerical order while listing a directory file b) Disappearance of a file from a directory c) Deleted files appearing again while listing the directory (appearing like a stale entry) d) Duplicate filenames within the directory e) Not able to access file temporarily but able to access the file after sometime f) Content of system space getting shifted by some amount leading to system crash in other component such as logical name translation module Problem is more likely to be seen if DFO(Disk File Optimizer) is used as DFO uses MOVEFILE subfunction. Images Affected: - [SYS$LDR]F11BXQP.EXE - [SYS$LDR]F11BXQP.STB 5.2.2.2 Quix and PTR cases reporting this problem: 5.2.2.2.1 Quix Cases QXCM1001201239 5.2.2.2.2 PTR(s) None Page 4 5.2.2.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.4 5.2.2.4 Work-arounds: None 5.2.3 File system response time slower or system crash in case large numbers of directory files are renamed 5.2.3.1 Problem Description: On OpenVMS V8.4, if large numbers of directory files are renamed without them being accessed later, then this can make file system response time slower resulting in performance degradation. This scenario can eventually result in a system crash. Images Affected: - [SYS$LDR]F11BXQP.EXE - [SYS$LDR]F11BXQP.STB 5.2.3.2 Quix and PTR cases reporting this problem: 5.2.3.2.1 Quix Cases QXCM1001219891 5.2.3.2.2 PTR(s) None 5.2.3.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.4 5.2.3.4 Work-arounds: After a directory is renamed, access the directory using DCL command DIRECTORY, DUMP, etc. Page 5 5.2.4 XQPERR BUGCHECK with "Unexpected lock manager error" 5.2.4.1 Problem Description: If a file is opened for write with FIB$V_NOLOCK bit set, then in certain cases Filesystem might bugcheck if some previous accessor has unfinished truncate left to be done on that particular file. This problem has been fixed. Images Affected: - [SYS$LDR]F11BXQP.EXE - [SYS$LDR]F11BXQP.STB 5.2.4.2 Quix and PTR cases reporting this problem: 5.2.4.2.1 Quix Cases QXCM1001210589 5.2.4.2.2 PTR(s) None 5.2.4.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.4 5.2.4.4 Work-arounds: None 5.2.5 System crash with BADFID BUGCHECK due to bad FID value in the XQP FID cache 5.2.5.1 Problem Description: Under certain circumstances, XQP FID cache can end up having an entry with wrong FID value. This results in a system crash with BADFID BUGCHECK. With this fix, XQP will auto recover from this error scenario and continue normal execution without disrupting any user activity. Page 6 Images Affected: - [SYS$LDR]F11BXQP.EXE - [SYS$LDR]F11BXQP.STB 5.2.5.2 Quix and PTR cases reporting this problem: 5.2.5.2.1 Quix Cases QXCM1001222197,QXCM1000441310 QXCM1001063553,QXCM1001170012 5.2.5.2.2 PTR(s) None 5.2.5.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.4 5.2.5.4 Work-arounds: None 6 PROBLEMS ADDRESSED IN PREVIOUS KITS Problems addressed by previously released VMS84I_F11X patch kits can be found in the following files: o VMS84I_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 VMS84I_F11X /VERSION=V2.0 - [/file=destination_directory] o To extract a single release notes file use: PRODUCT EXTRACT FILE VMS84I_F11X /VERSION=V2.0 - /SELECT=release_note_name[/DESTINATION=destination_directory] The names of individual RELEASE_NOTES files in the kit can be found with: PRODUCT LIST VMS84I_F11X /VERSION=V2.0 /SELECT = *.RELEASE_NOTES Page 7 7 FILES PATCHED OR REPLACED: o [SYS$LDR]F11BXQP.EXE (new image) Image Identification Information Image name: "F11BXQP" Image file identification: "XQP V84R_RE CFI" Image build identification: "0100000083" linker identification: "Linker I02-37" Link Date/Time: 24-AUG-2012 14:23:12.47 Overall Image Checksum: 459E6D83 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 Self Extracting ZIPEXE kit. To expand this file to the installable .PCSI file, run the file with the following command: $ RUN VMS84I_F11X-V0200.ZIPEXE Page 8 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 VMS84I_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=HP/BASE=I64VMS/VER=V2.0 [/SOURCE=location of Kit] Page 9 o De-assign the logical names assigned For example, a sample command file to install the VMS84I_F11X-V0200 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS84I_F11X/PRODUCER=HP/BASE=I64VMS/VER=V2.0 $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit $! 9 COPYRIGHT AND DISCLAIMER: (C) Copyright 2012 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.