**************************** ECO SUMMARY INFORMATION **************************** Release Date: 14-JUL-2004 Kit Name: DEC-AXPVMS-VMS732_LIBRTL-V0100--4.PCSI Kit Applies To: OpenVMS ALPHA V7.3-2 Approximate Kit Size: 4144 blocks Installation Rating: INSTALL_3 Superseded Kits: None. Mandatory Kit Dependencies: VMS732_UPDATE-V0200 VMS732_PCSI-V0100 Optional Kit Dependencies: None. VMS732_LIBRTL-V0100.PCSI-DCX_AXPEXE Checksum: 1938432568 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= ECO NUMBER: VMS732_LIBRTL-V0100 PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3-2 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3-2 1 KIT NAME: VMS732_LIBRTL-V0100 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_3 : To be installed by customers experiencing the problems corrected. 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 Alpha V7.3-2 2.4 New functionality or new hardware support provided: No. 3 KITS SUPERSEDED BY THIS KIT: - None. 4 KIT DEPENDENCIES: Page 2 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS732_PCSI-V0100 - VMS732_UPDATE-V0200 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 FILES PATCHED OR REPLACED: o [SYSLIB]LIBRTL.EXE (new image) Image Identification Information image name: "LIBRTL" image file identification: "X01-001" image file build identification: "XA99-0060110003" link date/time: 21-MAY-2004 14:25:12.49 linker identification: "A11-50" Overall Image Checksum: 3373659189 o [SYSLIB]LIBRTL_INSTRUMENTED.EXE (new image) Image Identification Information image name: "LIBRTL_INSTRUMENTED" image file identification: "X01-001" image file build identification: "XA99-0060110003" link date/time: 21-MAY-2004 14:25:24.17 linker identification: "A11-50" Overall Image Checksum: 2347397952 o [SYSLIB]LIBRTL.STB (new file) 6 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS732_LIBRTL-V0100 KIT Page 3 6.1 New functionality addressed in this kit None. 6.2 Problems addressed in this kit 6.2.1 Potential application hangs 6.2.1.1 Problem Description: Some LIB$ RTL routines are not thread-safe because they use event flag zero (0) when they should be using EFN$C_EFN. Using these LIB$ RTL routines can cause a potential application hang since event flag zero can be set/cleared from two or more potential threads affecting other threads. Note that this fix is required to run new versions of the SAS software. Images Affected: - - [SYSLIB]LIBRTL.EXE - [SYSLIB]LIBRTL.STB 6.2.1.2 CLDs, and QARs reporting this problem: 6.2.1.2.1 CLD(s) CFS.100354,70-16-59 6.2.1.2.2 QAR(s) None. 6.2.1.3 Problem Analysis: See problem Description 6.2.1.4 Release Version of OpenVMS that will contain this change: Next release after V7.3-2 Page 4 6.2.1.5 Work-arounds: None. 6.2.2 Overflow not detected 6.2.2.1 Problem Description: Calls to LIB$CVT_DX_DX using string descriptor class, DSC$K_CLASS_SD, with longword type, DSC$K_DTYPE_L, and non-zero scales do not detect overflow. Images Affected: - [SYSLIB]LIBRTL.EXE - [SYSLIB]LIBRTL.STB 6.2.2.2 CLDs, and QARs reporting this problem: 6.2.2.2.1 CLD(s) None. 6.2.2.2.2 QAR(s) 75-13-1049 6.2.2.3 Problem Analysis: The macro used for longword to longword scaling had no overflow detection. 6.2.2.4 Release Version of OpenVMS that will contain this change: Next release after V7.3-2 6.2.2.5 Work-arounds: None. 6.2.3 Calls to malloc64(size) fail to allocate the memory Page 5 6.2.3.1 Problem Description: After upgrading to V7.3-2, calls to the C runtime function malloc64(size), with size greater than one Gigabyte, fail to allocate the memory. Images Affected: - [SYSLIB]LIBRTL.EXE - [SYSLIB]LIBRTL.STB 6.2.3.2 CLDs, and QARs reporting this problem: 6.2.3.2.1 CLD(s) CFS.105783,70-16-75 6.2.3.2.2 QAR(s) None. 6.2.3.3 Problem Analysis: A sanity check on user specified size is not conditionalized to compile only for the 32-bit allocation malloc(size) variant. 6.2.3.4 Release Version of OpenVMS that will contain this change: Next release after V7.3-2 6.2.3.5 Work-arounds: None. 6.2.4 Remove LIB$RENAME_FILE behavior change 6.2.4.1 Problem Description: For OpenVMS V7.3-1, a change was made to LIB$RENAME_FILE to preserve case for a new filename. For example, a lib$rename of TEST.X to test.tmp creates the following files: o On V7.3 TEST.TMP is created Page 6 o On V7.3-1 and V7.3-2 test.tmp is created This change caused problems with customer code. LIB$RENAME_FILE is being reverted to pre-V7.3-1 behavior. Images Affected: - [SYSLIB]LIBRTL.EXE - [SYSLIB]LIBRTL.STB - [SYSLIB]LIBRTL_INSTRUMENTED.EXE 6.2.4.2 CLDs, and QARs reporting this problem: 6.2.4.2.1 CLD(s) CFS.107598 6.2.4.2.2 QAR(s) None. 6.2.4.3 Problem Analysis: See Problem Description 6.2.4.4 Release Version of OpenVMS that will contain this change: Next Release after V7.3-2 6.2.4.5 Work-arounds: None. 7 INSTALLATION INSTRUCTIONS 7.1 Compressed File This kit is provided as a DCX compressed kit. To expand this file to the installable PCSI file, run the file with a RUN file_name command. When the file is run you will see the following output: $ RUN VMS732_LIBRTL-V0100.PCSI-DCX_AXPEXE FTSV DCX auto-extractible compressed file for OpenVMS (AXP) FTSV V3.0 -- FTSV$DCX_AXP_AUTO_EXTRACT Copyright (c) Digital Equipment Corp. 1993 Page 7 Options: [output_file_specification] [input_file_specification] The decompressor needs to know the filename to use for the decompressed file. If you don't specify any, it will use the original name of the file before it was compressed, and create it in the current directory. If you specify a directory name, the file will be created in that directory. Decompress into (file specification): If you want the file to be expanded into a different directory, enter the directory specification. DO NOT enter a new file name. The expanded file must retain the original name. If you want to expand the file via batch, the command file must contain an answer to the Decompress into "(file specification)" question, either a or an alternate directory specification 7.2 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 VMS732_LIBRTL /SAVE_RECOVERY_DATA [/SOURCE=location of Kit] 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. 7.3 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 8 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=DEC/BASE=AXPVMS/VER=V1.0/SAVE_RECOVERY_DATA o De-assign the logical names assigned For example, a sample command file to install the VMS732_LIBRTL-V0100 kit would be: $ $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS732_LIBRTL/PRODUCER=DEC/BASE=AXPVMS- /VER=V1.0/SAVE_RECOVERY_DATA $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit 8 COPYRIGHT AND DISCLAIMER: (C) Copyright 2004 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 Page 9 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.