======================================================================= Hewlett-Packard OpenVMS ECO Release Notes ======================================================================= 1 KIT NAME: VMS84I_RMS-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 for Integrity Servers V8.4 2.4 New functionality or new hardware support provided: No 3 KITS SUPERSEDED BY THIS KIT: - VMS84I_RMS-V0300 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-V0800 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_RMS-V0400 KIT 5.1 New functionality addressed in this kit Not Applicable 5.2 Problems addressed in this kit 5.2.1 When a process writes a record into a file that has RU Journaling enabled and the process itself gets deleted before the record is committed into the file, another process is temporarily able to read that record 5.2.1.1 Problem Description: Consider a scenario where a writer process writes records into a file that has RU journaling enabled and a reader process has opened the same file and reads records from it periodically by setting the RAB$V_RRL (read regardless) flag in the RAB structure. In such a scenario if the writer process is deleted after it has written a record but before committing that transaction by using the DCL command STOP/ID, the reader process will be able to read the same record and gets "%RMS-S-NORMAL, normal successful completion" as return status instead of getting "%RMS-E-RNF, record not found" or "%RMS-S-OK_RRL, record locked against read but read anyway". Now if the file is explicitly recovered (e.g. by using DCL TYPE command), the reader process will cease to see the record. This problem has been fixed. Images Affected: - [SYS$LDR]RMS.EXE - [SYS$LDR]RMS.STB Page 3 5.2.1.2 Quix and PTR cases reporting this problem: 5.2.1.2.1 Quix Cases QXCM1001188022 5.2.1.2.2 PTR(S) None 5.2.1.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.2.1.4 Work-arounds: None 5.2.2 DIR/FILE/NOSYM displaying improper file id for symlink pointing to a file with only extension 5.2.2.1 Problem Description: While accessing symlink pointing to a file having only extension in it's name ( that is, no name component in it's file-name), instead of accessing the file, the parent directory of the file is accessed. This problem has been fixed. Images Affected: - [SYS$LDR]RMS.EXE - [SYS$LDR]RMS.STB 5.2.2.2 Quix and PTR cases reporting this problem: 5.2.2.2.1 Quix Cases None 5.2.2.2.2 PTR(S) 75-120-1618 Page 4 5.2.2.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.2.2.4 Work-arounds: None 5.2.3 Under certain scenarios, wildcard operations involving symbolic links can select the same file multiple times 5.2.3.1 Problem Description: Issuing a DIR command with wildcard specification that involves symbolic links can result in displaying the same file multiple times.This problem occurs when files with same name but in different directories gets selected by the wildcard specification provided in the DIR command. This problem has been fixed. Images Affected: - [SYS$LDR]RMS.EXE - [SYS$LDR]RMS.STB 5.2.3.2 Quix and PTR cases reporting this problem: 5.2.3.2.1 Quix Cases None 5.2.3.2.2 PTR(S) 75-130-18 5.2.3.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.2.3.4 Work-arounds: None Page 5 5.2.4 RMS Recovery Server process hang 5.2.4.1 Problem Description: If there are many processes that have open files with RU journaling enabled, and if any such processes crashes then this may cause the Recovery server process (RMSREC_pid or RMSREC_SERVER) to hang in HIB state. In a cluster environment this problem can also occur when any NODE exits the cluster. This problem has been fixed. Images Affected: - [SYSEXE]RECOVER.EXE - [SYSEXE]RMSREC$SERVER.EXE 5.2.4.2 Quix and PTR cases reporting this problem: 5.2.4.2.1 Quix Cases QXCM1001135962 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 Integrity after V8.4 5.2.4.4 Work-arounds: None 6 PROBLEMS ADDRESSED IN PREVIOUS KITS Problems addressed by previously released VMS84I_RMS patch kits can be found in the following files: o VMS84I_RMS-V0100.RELEASE_NOTES o VMS84I_RMS-V0200.RELEASE_NOTES o VMS84I_RMS-V0300.RELEASE_NOTES Before kit installation, these files can be extracted from the kit Page 6 via the following commands: o To extract all release notes files at once use: PRODUCT EXTRACT RELEASE_NOTES VMS84I_RMS /VERSION=V4.0 - [/file=destination_directory] o To extract a single release notes file use: PRODUCT EXTRACT FILE VMS84I_RMS /VERSION=V4.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_RMS /VERSION=V4.0 /SELECT = *.RELEASE_NOTES 7 FILES PATCHED OR REPLACED: o [SYSEXE]RECOVER.EXE (new image) Image Identification Information Image name: "RECOVER" Image file identification: "X01-03" Image build identification: "0100000096" linker identification: "Linker I02-37" Link Date/Time: 7-JAN-2013 11:46:50.50 Overall Image Checksum: 2EF02AAC o [SYS$LDR]RMS.EXE (new image) Image Identification Information Image name: "RMS" Image file identification: "X-5" Image build identification: "0100000086" linker identification: "Linker I02-37" Link Date/Time: 1-OCT-2012 12:39:52.07 Overall Image Checksum: 3E81F530 o [SYSEXE]RMSREC$SERVER.EXE (new image) Image Identification Information Image name: "RMSREC$SERVER" Image file identification: "X-14" Image build identification: "0100000096" linker identification: "Linker I02-37" Link Date/Time: 7-JAN-2013 11:46:53.10 Overall Image Checksum: 50A4A493 Page 7 o [SYS$LDR]RMS.STB (new file) 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_RMS-V0400.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 VMS84I_RMS[/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. Page 8 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=V4.0 [/SOURCE=location of Kit] o De-assign the logical names assigned For example, a sample command file to install the VMS84I_RMS-V0400 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS84I_RMS/PRODUCER=HP/BASE=I64VMS/VER=V4.0 $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! Page 9 $ exit $! 9 COPYRIGHT AND DISCLAIMER: (C) Copyright 2013 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.