======================================================================= Hewlett-Packard OpenVMS ECO Release Notes ======================================================================= 1 KIT NAME: VMS84I_ACRTL-V0200 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_3 : To be installed by customers experiencing the problems corrected. 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_ACRTL-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_ACRTL-V0200 KIT 5.1 New functionality addressed in this kit Not Applicable 5.2 Problems addressed in this kit 5.2.1 Applications using CRTL write() api may get into hang state when DECC$FD_LOCKING logical is defined. 5.2.1.1 Problem Description: CRTL UNIX I/O apis synchronizes using FD mutex locking mechanism when DECC$FD_LOCKING logical is defined. CRTL write() api may return failure without unlocking FD mutex lock which has already been acquired. This may result in hang for any subsequent UNIX I/O call with same FD, as it tries to acquire the same mutex lock again. Images Affected: - [SYSLIB]DECC$SHR.EXE 5.2.1.2 Quix and PTR cases reporting this problem: 5.2.1.2.1 Quix Cases QXCM1001201953 5.2.1.2.2 PTR(S) 75-126-228 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 SSH Server ACCVIOs when accessed via Bitvise Tunnelier SSH client. 5.2.2.1 Problem Description: CRTL readdir() api internally maintains the list of the files in a particular directory stream opened using opendir() api. This list gets freed when current location reaches to the end of directory stream. In certain scenarios, current location pointer may point to the address which has already been freed; this caused the ACCVIO. Images Affected: - [SYSLIB]DECC$SHR.EXE 5.2.2.2 Quix and PTR cases reporting this problem: 5.2.2.2.1 Quix Cases QXCM1001194568 5.2.2.2.2 PTR(S) 75-126-227 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 CRTL write() may fail/hang when O_SYNC or O_DSYNC flags are set and DECC$FD_LOCKING logical is enabled. Page 4 5.2.3.1 Problem Description: CRTL write() may fail if the target file has been opened with O_SYNC or O_DSYNC flags set and DECC$FD_LOCKING logical is enabled. This is because write tries to lock the FD mutex lock which has already been locked. Images Affected: - [SYSLIB]DECC$SHR.EXE 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-13-2448 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 CRTL api uname() could hang waiting for event flag zero (0) in certain scenarios. 5.2.4.1 Problem Description: CRTL api uname() calls system service sys$getsyiw to get system identification information. uname() calls the system service with event flag zero (EFN 0) but without an IOSB (I/O Status Block), thus using only the event flag for synchronization. If AST routines are also using EFN 0, the process could hang in LEF state waiting for event flag to be set, as an AST could have already set and then cleared the event flag. The api call has been modified to use EFN$C_ENF and an IOSB to avoid this possible conflict. Images Affected: Page 5 - [SYSLIB]DECC$SHR.EXE 5.2.4.2 Quix and PTR cases reporting this problem: 5.2.4.2.1 Quix Cases QXCM1001237573 5.2.4.2.2 PTR(S) 75-126-283 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 CRTL symbolic link api readlink() should fail if the input is not a symbolic link. 5.2.5.1 Problem Description: CRTL readlink() api return success even though the input file specification is not a symbolic link; ideally it should fail with EINVAL error. This problem has been fixed. Images Affected: - [SYSLIB]DECC$SHR.EXE 5.2.5.2 Quix and PTR cases reporting this problem: 5.2.5.2.1 Quix Cases None Page 6 5.2.5.2.2 PTR(S) 75-126-309 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 5.2.6 CRTL lstat() and lchown() apis may ACCVIO if the file_path argument is of VMS and UNIX style in mixed mode. 5.2.6.1 Problem Description: CRTL lstat() and lchown() apis, file_path argument can be a valid OpenVMS or UNIX style directory specification. These apis should return error for an invalid file_path input. There are some instances where lstat() and lchown() causes ACCVIO if the input file_path argument is of VMS and UNIX style in mixed mode; for example "/a:[b]". This problem has been fixed. Images Affected: - [SYSLIB]DECC$SHR.EXE 5.2.6.2 Quix and PTR cases reporting this problem: 5.2.6.2.1 Quix Cases QXCM1001235387 5.2.6.2.2 PTR(S) 75-126-282 5.2.6.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 Page 7 5.2.6.4 Work-arounds: None 6 PROBLEMS ADDRESSED IN PREVIOUS KITS Problems addressed by previously released VMS84I_ACRTL patch kits can be found in the following files: o VMS84I_ACRTL-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_ACRTL /VERSION=V2.0 - [/file=destination_directory] o To extract a single release notes file use: PRODUCT EXTRACT FILE VMS84I_ACRTL /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_ACRTL /VERSION=V2.0 /SELECT = *.RELEASE_NOTES 7 FILES PATCHED OR REPLACED: o [SYSLIB]DECC$SHR.EXE (new image) Image Identification Information Image name: "DECC$SHR" Image file identification: "V8.4-00" Image build identification: "0100000094" linker identification: "Linker I02-37" Link Date/Time: 7-DEC-2012 10:03:17.83 Overall Image Checksum: 500229EB o [SYSLIB]DECC$SHRP.EXE (new image) Image Identification Information Image name: "DECC$SHRP" Image file identification: "V8.4-00" Image build identification: "0100000094" linker identification: "Linker I02-37" Link Date/Time: 7-DEC-2012 10:03:16.74 Overall Image Checksum: CB7DB68F Page 8 o [SYSLIB]DECC$RTLDEF.TLB (updated by DECC$RTLDEF.FOR_RELEASE) 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_ACRTL-V0200.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_ACRTL[/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 9 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] o De-assign the logical names assigned For example, a sample command file to install the VMS84I_ACRTL-V0200 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS84I_ACRTL/PRODUCER=HP/BASE=I64VMS/VER=V2.0 $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! Page 10 $ 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.