======================================================================= Hewlett-Packard OpenVMS ECO Release Notes ======================================================================= 1 KIT NAME: VMS84I_RMS-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 for Integrity Servers V8.4 2.4 New functionality or new hardware support provided: No 3 KITS SUPERSEDED BY THIS KIT: - VMS84I_RMS-V0400 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-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 VMS84I_RMS-V0500 KIT 5.1 New functionality addressed in this kit Not Applicable 5.2 Problems addressed in this kit 5.2.1 Alignment faults in RMS. 5.2.1.1 Problem Description: Under certain circumstances alignment faults are generated in RMS while doing an RMS $PARSE operation. Alignment faults are seen at the PC value , RMS+01DCEE0. This problem has been fixed. Images Affected: - [SYS$LDR]RMS.EXE - [SYS$LDR]RMS.STB 5.2.1.2 Quix and PTR cases reporting this problem: 5.2.1.2.1 Quix Cases QXCM1001264814 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 Page 3 5.2.1.4 Work-arounds: None 5.2.2 Disable RMS directory path cache for an NFS disk. 5.2.2.1 Problem Description: In an NFS served disk, if a directory is deleted from the server node or from any other NFS client node, then directory operations from the client node which has accessed that directory previously may fail. This problem is fixed by disabling RMS directory path cache in the NFS client node. To disable RMS directory path cache for an NFS disk the second bit of SYSGEN parameter RMSD1 value should be set. For example, if the current value of SYSGEN paramter RMSD1 is 0, then RMSD1 should be set to 2. If the value is 1, then RMSD1 should be set to 3. 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 QXCM1001278472, QXCM1001256670 5.2.2.2.2 PTR(S) None 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 Page 4 5.2.3 Process gets deleted while writing records to a file. 5.2.3.1 Problem Description: Under certain scenarios process gets deleted while appending or writing records to a file of size greater than 1 TB. An operator message "%RMS-F-BUG, fatal RMS condition (FFFFFFEF), process deleted" is displayed on the console. Images Affected: - [SYS$LDR]RMS.EXE 5.2.3.2 Quix and PTR cases reporting this problem: 5.2.3.2.1 Quix Cases QXCM1001319462 5.2.3.2.2 PTR(S) 75-126-373 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 5.2.4 Alignment faults in FAL on V8.4 Itanium system. 5.2.4.1 Problem Description: The FAL image generates alignment faults for certain operations on V8.4 Itanium system such as $ DIRECTORY FOO"user password"::FOO:[*...]*.*;*/OUT=NL: Images Affected: - [SYSEXE]FAL.EXE Page 5 5.2.4.2 Quix and PTR cases reporting this problem: 5.2.4.2.1 Quix Cases QXCM1001310615 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 5.2.5 CONVERT command fails with %CONVERT-F-INP_FILES error. 5.2.5.1 Problem Description: When CONVERT command is used with /FDL qualifier where many secondary keys are specified in the FDL file, it throws %CONVERT-F-INP_FILES error under certain scenarios. For example: $ convert/nosort/fdl=FOO.FDL INPUT.DAT OUTPUT.DAT %CONVERT-F-INP_FILES, too many input files There are 40 secondary keys specified in FOO.FDL. This problem is fixed. Images Affected: - [SYSLIB]CONVSHR.EXE 5.2.5.2 Quix and PTR cases reporting this problem: Page 6 5.2.5.2.1 Quix Cases QXCM1001324989 5.2.5.2.2 PTR(S) 75-126-375 5.2.5.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.2.5.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 o VMS84I_RMS-V0400.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_RMS /VERSION=V5.0 - [/file=destination_directory] o To extract a single release notes file use: PRODUCT EXTRACT FILE VMS84I_RMS /VERSION=V5.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=V5.0 /SELECT = *.RELEASE_NOTES Page 7 7 FILES PATCHED OR REPLACED: o [SYSLIB]CONVSHR.EXE (new image) Image Identification Information Image name: "CONVSHR" Image file identification: "X1-012" Image build identification: "0100000125" linker identification: "Linker I02-37" Link Date/Time: 15-JAN-2014 12:34:24.82 Overall Image Checksum: 72C55201 o [SYSEXE]FAL.EXE (new image) Image Identification Information Image name: "FAL" Image file identification: "X-10" Image build identification: "0100000119" linker identification: "Linker I02-37" Link Date/Time: 25-OCT-2013 18:28:10.62 Overall Image Checksum: 883D24AB o [SYS$LDR]RMS.EXE (new image) Image Identification Information Image name: "RMS" Image file identification: "X-5" Image build identification: "0100000124" linker identification: "Linker I02-37" Link Date/Time: 10-DEC-2013 14:20:30.32 Overall Image Checksum: A2AA88D4 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: 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 VMS84I_RMS-V0500.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. 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=HP/BASE=I64VMS/VER=V5.0 [/SOURCE=location of Kit] o De-assign the logical names assigned For example, a sample command file to install the VMS84I_RMS-V0500 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=V5.0 $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit $! 9 COPYRIGHT AND DISCLAIMER: (C) Copyright 2014 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.