======================================================================= Hewlett-Packard OpenVMS ECO Release Notes ======================================================================= 1 KIT NAME: VMS84I_ACRTL-V0300 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-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-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_ACRTL-V0300 KIT 5.1 New functionality addressed in this kit Not Applicable 5.2 Problems addressed in this kit 5.2.1 Fortran single carriage-control format file when read using CIFS, displays the first line as blank when logical DECC$TERM_REC_CRLF is defined. 5.2.1.1 Problem Description: The feature switch DECC$TERM_REC_CRLF is modified for the Fortran single carriage-control format (FTN) file having record attribute single-space carriage control; to avoid prefix the first record with CRLF. Because of this prefix, FTN file when read using CIFS starts printing from second line leaving the first line as blank. This problem has been fixed. Images Affected: - [SYSLIB]DECC$SHR.EXE 5.2.1.2 Quix and PTR cases reporting this problem: 5.2.1.2.1 Quix Cases QXCM1001240796 5.2.1.2.2 PTR(S) None. Page 3 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 Applications using NAMESER_COMPAT.H may get "Undefined or invalid BYTE_ORDER" error for IA64 platforms. 5.2.2.1 Problem Description: Generally BYTE_ORDER should be defined in NAMESER_COMPAT.H header file; however conditionalization statement in NAMESER_COMPAT.H to define BYTE_ORDER for IA64 platforms is missing. Hence applications may get "Undefined or invalid BYTE_ORDER" error. This problem has been fixed. Images Affected: - [SYSLIB]DECC$RTLDEF.TLB 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) 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 CRTL access() API may fail when input file_spec is directory specification while the DECC$ACL_ACCESS_CHECK logical is defined. 5.2.3.1 Problem Description: CRTL access() API returns failure when the first parameter is of directory specification with DECC$ACL_ACCESS_CHECK logical being defined. This problem has been fixed. 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) None. 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 lstat() API fails with an error for self-referential symbolic link files. 5.2.4.1 Problem Description: CRTL lstat() API should return about the symbolic link itself if the input file specification is a symbolic link file. This API fails with "no such file or directory" error. This problem has been fixed. 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 None. 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 CRTL setenv() API may fail for default environment variables. 5.2.5.1 Problem Description: CRTL setenv() API may fail, if we try to store a value longer than the previous one in default environment variables HOME, TERM, PATH or USER. 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) None. 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 vfork() and execve() may fail to execute a DCL command procedure. 5.2.6.1 Problem Description: CRTL vfork() and execve() may fail to execute a DCL command procedure, if the total length of all given parameters exceeds 262 characters. 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 None. 5.2.6.2.2 PTR(S) None. 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. 5.2.7 Shared Memory API shmat() fails with EINVAL if the input address provided is not allocated by the process. 5.2.7.1 Problem Description: CRTL Shared Memory shmat() API doesn't allow to attach to the un-allocated address; so even though the input address is got from the previous call to shmat() there may be possibility that the same Virtual Address might have already been used by the process; so shmat() fails with EINVAL error. To attach shared memory segment to an un-allocated address, applications has to define DECC$ALLOW_SPECIFIC_SHMADDR logical. This problem has been fixed. Images Affected: - [SYSLIB]DECC$SHR.EXE - [SYSLIB]DECC$SHRP.EXE 5.2.7.2 Quix and PTR cases reporting this problem: 5.2.7.2.1 Quix Cases None. 5.2.7.2.2 PTR(S) None. 5.2.7.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.2.7.4 Work-arounds: None. Page 8 5.2.8 CRTL rmdir() API may change directory protection in some failure cases. 5.2.8.1 Problem Description: CRTL rmdir() API changes file protection and left it unchanged on failure, for non-empty directories. This problem has been fixed. Images Affected: - [SYSLIB]DECC$SHR.EXE 5.2.8.2 Quix and PTR cases reporting this problem: 5.2.8.2.1 Quix Cases None. 5.2.8.2.2 PTR(S) None. 5.2.8.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.2.8.4 Work-arounds: None. 5.2.9 For Fortran Carriage Control Format file with Variable length Records and for Print Carriage Control Format file with VFC, need some changes for CIFS to display in appropriate format. 5.2.9.1 Problem Description: Fortran Carriage Control Format file when DECC$TERM_REC_CRLF is defined: when first character in record is "space" the earlier displayed format is changed to and when first character in record is "1" the earlier displayed format is changed to . Print Carriage Control Format file when DECC$TERM_REC_CRLF is defined: when Prefix is 0x8D and Postfix is 0x01 the earlier displayed Page 9 format is changed to . This problem has been fixed. Images Affected: - [SYSLIB]DECC$SHR.EXE 5.2.9.2 Quix and PTR cases reporting this problem: 5.2.9.2.1 Quix Cases QXCM1001264203, QXCM1001278644 5.2.9.2.2 PTR(S) None. 5.2.9.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.2.9.4 Work-arounds: None. 5.2.10 For relative pathnames, DECC$TO_VMS and GLOB output is broken when dealing with wildcards. Path is wrongly displayed. 5.2.10.1 Problem Description: For relative pathnames DECC$TO_VMS and GLOB output is broken when dealing with wildcards. The problem is that, for DECC$TO_VMS output no matter how many directory levels down the resulting file is, it only returns the immediately adjacent directory and for GLOB output directory path is wrongly displayed. This problem has been fixed. Images Affected: - [SYSLIB]DECC$SHR.EXE Page 10 5.2.10.2 Quix and PTR cases reporting this problem: 5.2.10.2.1 Quix Cases None. 5.2.10.2.2 PTR(S) None. 5.2.10.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.2.10.4 Work-arounds: None. 5.2.11 Lstat information for a soft link pointing to a directory returns wrong information. 5.2.11.1 Problem Description: Lstat information for a soft link pointing to a directory is retrieved as directory and not as softlink when DECC$EFS_CHARSET logical is set to 1. This problem has been fixed. Images Affected: - [SYSLIB]DECC$SHR.EXE 5.2.11.2 Quix and PTR cases reporting this problem: 5.2.11.2.1 Quix Cases None. 5.2.11.2.2 PTR(S) None. Page 11 5.2.11.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.2.11.4 Work-arounds: None. 5.2.12 CRTL fread() API may return wrong result in certain scenarios. 5.2.12.1 Problem Description: CRTL fread() API may return wrong result when used to read just one byte from the input stream, where this one byte has been pushed by a previous ungetc() call. This problem has been fixed. Images Affected: - [SYSLIB]DECC$SHR.EXE 5.2.12.2 Quix and PTR cases reporting this problem: 5.2.12.2.1 Quix Cases None. 5.2.12.2.2 PTR(S) None. 5.2.12.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.2.12.4 Work-arounds: None. Page 12 5.2.13 Modification to CRTL APIs to use EFN$C_ENF event flag instead of event flag "0" with wait form of system services. 5.2.13.1 Problem Description: OpenVMS CRTL APIs use wait form of system services to perform the required operations, with EFN parameter as zero. We have modified such APIs to use EFN$C_ENF along with IOSB status block, adhering to wait form of system service guidelines specified in "HP OpenVMS Programming Concepts Manual" under "Using EFN$C_ENF Local Event Flag" section. Primarily this eliminates any possible event flag contention and makes the CRTL processing efficient. Images Affected: - [SYSLIB]DECC$SHR.EXE - [SYSLIB]DECC$SHRP.EXE 5.2.13.2 Quix and PTR cases reporting this problem: 5.2.13.2.1 Quix Cases None. 5.2.13.2.2 PTR(S) None. 5.2.13.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.2.13.4 Work-arounds: None. 5.2.14 C and C++ programs using "isnormal()" macro fails to compile in IEEE mode. Page 13 5.2.14.1 Problem Description: Compilation of C and C++ programs using "isnormal()" macro fails with '%CC-E-NOSEMI, Missing ";"' and '%CXX-E-EXPSEMICOLON, expected a ";"' error respectively. This problem has been fixed. Images Affected: - [SYSLIB]DECC$RTLDEF.TLB 5.2.14.2 Quix and PTR cases reporting this problem: 5.2.14.2.1 Quix Cases None. 5.2.14.2.2 PTR(S) None. 5.2.14.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.2.14.4 Work-arounds: None. 5.2.15 CRTL APIs ferror(), clearerr() and feof() accvios for closed file streams. 5.2.15.1 Problem Description: CRTL APIs ferror(), clearerr() and feof() accepts file pointer as arguments. These APIs may crash with ACCVIO when called with closed file stream (NULL) as argument. This problem has been fixed. Images Affected: - [SYSLIB]DECC$RTLDEF.TLB Page 14 5.2.15.2 Quix and PTR cases reporting this problem: 5.2.15.2.1 Quix Cases None. 5.2.15.2.2 PTR(S) None. 5.2.15.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.2.15.4 Work-arounds: None. 5.2.16 UN.H header file to support Unix Domain Sockets feature with TCP/IP 5.7 ECO2 release. 5.2.16.1 Problem Description: TCP/IP 5.7 ECO2 supports Unix Domain Sockets feature. TCP/IP header file UN.H has been included into DECC$RTLDEF.TLB header library to support this feature. This problem has been fixed. Images Affected: - [SYSLIB]DECC$RTLDEF.TLB 5.2.16.2 Quix and PTR cases reporting this problem: 5.2.16.2.1 Quix Cases None. 5.2.16.2.2 PTR(S) None. Page 15 5.2.16.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.2.16.4 Work-arounds: None. 5.2.17 Shared Memory API shmget() with key as IPC_PRIVATE may fail in certain scenarios. 5.2.17.1 Problem Description: Call to shmget() with key as IPC_PRIVATE is failing if the flag argument is not accompanied by IPC_CREAT. This problem has been fixed. Images Affected: - [SYSLIB]DECC$SHR.EXE - [SYSLIB]DECC$SHRP.EXE 5.2.17.2 Quix and PTR cases reporting this problem: 5.2.17.2.1 Quix Cases None. 5.2.17.2.2 PTR(S) None. 5.2.17.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.2.17.4 Work-arounds: None Page 16 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 o VMS84I_ACRTL-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_ACRTL /VERSION=V3.0 - [/file=destination_directory] o To extract a single release notes file use: PRODUCT EXTRACT FILE VMS84I_ACRTL /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_ACRTL /VERSION=V3.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: "0100000127" linker identification: "Linker I02-37" Link Date/Time: 10-FEB-2014 13:26:38.13 Overall Image Checksum: 1B6520B5 o [SYSLIB]DECC$SHRP.EXE (new image) Image Identification Information Image name: "DECC$SHRP" Image file identification: "V8.4-00" Image build identification: "0100000127" linker identification: "Linker I02-37" Link Date/Time: 10-FEB-2014 13:26:33.24 Overall Image Checksum: F898B815 Page 17 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-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_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 18 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=V3.0 [/SOURCE=location of Kit] o De-assign the logical names assigned For example, a sample command file to install the VMS84I_ACRTL-V0300 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=V3.0 $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! Page 19 $ 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. 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.