======================================================================= Hewlett-Packard OpenVMS ECO Release Notes ======================================================================= 1 KIT NAME: VMS84I_RMS-V0300 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 IA64 V8.4 2.4 New functionality or new hardware support provided: No 3 KITS SUPERSEDED BY THIS KIT: - VMS84I_RMS-V0200 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-V0300 - VMS84I_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 VMS84I_RMS-V0300 KIT 5.1 New functionality addressed in this kit Not Applicable 5.2 Problems addressed in this kit 5.2.1 CONV$CONVERT() API fails with SYSTEM-F-ACCVIO in Alpha or CONV-F-OPENIN in IA64. 5.2.1.1 Problem Description: When convert API's such as CONV$PASS_FILES(), CONV$PASS_OPTIONS() and CONV$CONVERT() are used in a user program to convert files, the CONV$CONVERT() API throws the following error based on the underlying hardware: a) SYSTEM-F-ACCVIO on Alpha when number of files passed to the routines is greater than 18. b) CONV-F-OPENIN on IA64 when number of files passed to the routines is greater than 21. With this patch, the CONV$CONVERT() API will now generate an "INP_FILES - too many input files error message to user in both architectures. Images Affected: - [SYSLIB]CONVSHR.EXE 5.2.1.2 Quix and PTR cases reporting this problem: 5.2.1.2.1 Quix Cases QXCM1001148977 Page 3 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 DCL command COPY throws an improper error message when called with long file specification containing Unicode characters. 5.2.2.1 Problem Description: RMS $PARSE service erroneously returns normal successful completion status in case the complete file specification is longer than 512 characters and if any directory name in the complete file specification consists of Unicode characters. The COPY utility internally uses RMS $PARSE and hence, when called with such a file specification, displays an incorrect error message viz "%COPY-W-DIRNOTCRE" to the user instead of the proper error message "%RMS-F-DIR, error in directory name". 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-128-41 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 Unable to create a directory file of the format ^.DIR.DIR when another directory of the format .DIR already exists 5.2.3.1 Problem Description: Suppose there is a directory .DIR in a user directory, and if we try to create another directory ^.DIR.DIR in the same user directory, then the creation fails with the message %CREATE-I-EXISTS. This problem is applicable only to an ODS-5 disk. E.g. $! Following operations should be on an ODS 5 disk $ set proc/parse_style=extended/case=blind $ create/dir [.foo]/log %CREATE-I-CREATED, $10$DKA0:[test.foo] created $! Now lets try to create another directory $ create/dir [.foo^.dir]/log %CREATE-I-EXISTS, [.foo^.dir] already exists 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 QXCM1001130537 5.2.3.2.2 PTR(s) None. Page 5 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 A non-directory file with UNICODE characters having an extension of .DIR, fails when a recursive directory lookup is performed 5.2.4.1 Problem Description: A non-directory file with UNICODE characters having an extension of .DIR, fails when a recursive directory lookup is performed For example - $ CREATE TESTDIR:[FOO]^U1234.DIR $ DIRECTORY TESTDIR:[FOO] Directory TESTDIR:[FOO] ^U1234.DIR;1 Total of 1 file. $ DIRECTORY TESTDIR:[FOO...] Directory TESTDIR:[FOO] %DIRECT-E-OPENIN, error opening TESTDIR:[FOO.^U1234]*.*;* as input -RMS-E-ACC, ACP file access failed -SYSTEM-F-FILNOTACC, file not accessed on channel ^U1234.DIR;1 Images Affected: - [SYS$LDR]RMS.EXE - [SYS$LDR]RMS.STB 5.2.4.2 Quix and PTR cases reporting this problem: Page 6 5.2.4.2.1 Quix Cases QXCM1001130537. 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 Process hang while using RMS Global buffers. 5.2.5.1 Problem Description: If RMS global buffers are being used on a file and if a process using that file runs out of ENQLM quota, then the CR lock reference count value of the bucket being read might become negative. This might cause other processes performing record operations on that file to hang. This problem has been fixed. Images Affected: - [SYS$LDR]RMS.EXE - [SYS$LDR]RMS.STB 5.2.5.2 Quix and PTR cases reporting this problem: 5.2.5.2.1 Quix Cases QXCM1001162749,QXCM1001095873 5.2.5.2.2 PTR(s) None. Page 7 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 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=V3.0 - [/file=destination_directory] o To extract a single release notes file use: PRODUCT EXTRACT FILE VMS84I_RMS /VERSION=V3.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=V3.0 /SELECT = *.RELEASE_NOTES 7 FILES PATCHED OR REPLACED: o [SYSEXE]CONVERT.EXE (new image) Image Identification Information Image name: "CONVERT" Image file identification: "X-12" Image build identification: "0100000005" linker identification: "Linker I02-37" Link Date/Time: 2-FEB-2012 11:31:35.15 Overall Image Checksum: 29501629 Page 8 o [SYSLIB]CONVSHR.EXE (new image) Image Identification Information Image name: "CONVSHR" Image file identification: "X1-012" Image build identification: "0100000005" linker identification: "Linker I02-37" Link Date/Time: 2-FEB-2012 11:30:46.01 Overall Image Checksum: 6B40D389 o [SYSEXE]RECLAIM.EXE (new image) Image Identification Information Image name: "RECLAIM" Image file identification: "X-6" Image build identification: "0100000005" linker identification: "Linker I02-37" Link Date/Time: 2-FEB-2012 11:31:36.50 Overall Image Checksum: 19AFE135 o [SYS$LDR]RMS.EXE (new image) Image Identification Information Image name: "RMS" Image file identification: "X-5" Image build identification: "0100000005" linker identification: "Linker I02-37" Link Date/Time: 2-FEB-2012 11:31:45.22 Overall Image Checksum: 91BF24F4 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. Page 9 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-V0300.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: o To avoid the BACKUP question, define the following: $ DEFINE/SYS NO_ASK$BACKUP TRUE Page 10 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=V3.0 [/SOURCE=location of Kit] o De-assign the logical names assigned For example, a sample command file to install the VMS84I_RMS-V0300 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=V3.0 $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit $! 8.5 Special Installation Instructions: If this kit is being installed in a clustered environment with a shared system disk, in order for all members of the cluster that share the system disk to make use of the new image, you must execute the following command on each node that is sharing the system disk (except for the node on which the installation was performed ; the installation has already done the INSTALL REPLACE on that node). : INSTALL REPLACE SYS$SHARE:CONVSHR.EXE INSTALL REPLACE SYS$SYSTEM:CONVERT.EXE INSTALL REPLACE SYS$SYSTEM:RECLAIM.EXE Once installed, users will need to logout and login back in order to use the new image. Page 11 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.