OpenVMS VAXLIBR06_070 VAX V5.5 - V7.0 LIBRTL ECO Summary

NOTE: An OpenVMS saveset or PCSI installation file is stored on the Internet in a self-expanding compressed file. The name of the compressed file will be kit_name-dcx_vaxexe for OpenVMS VAX or kit_name-dcx_axpexe for OpenVMS Alpha. Once the file is copied to your system, it can be expanded by typing RUN compressed_file. The resultant file will be the OpenVMS saveset or PCSI installation file which can be used to install the ECO. Copyright (c) Digital Equipment Corporation 1996, 1997. All rights reserved. INSTALLATION NOTES: If your system is running OpenVMS VAX V5.5-2* *AND* you installed VAXLIBR05_070 on that system, in order to avoid possible system crashes, you *MUST* install this kit, VAXLIBR06_070, on your system. If your system is running OpenVMS VAX V5.5, V5.5-1, V6.0, V6.1, V6.2 or V7.0 and VAXLIBR05_070 has been installed on your system, you *DO NOT* need to install this kit, VAXLIBR06_070. If your system is running OpenVMS VAX V5.5, V5.5-1, V5.5-2*, V6.0, V6.1, V6,2, or V7.0 and VAXLIBR05_070 has not been installed on your system, you *MUST* install this kit, VAXLIBR06_070, on your system. OP/SYS: OpenVMS VAX COMPONENTS: For OpenVMS VAX V5.5, V5.5-1, V5.5-2, V5.5-2H4, V5.5-2HF, V5.5-2HW, and V6.0: LIBRTL.EXE LIBRTL2.EXE MESSAGE_ROUTINES.EXE STARLET.OLB - Updated with LIB$DATE_ARITHMETIC and LIB$DATE_CVT For OpenVMS VAX V6.1, V6.2, and V7.0: LIBRTL.EXE LIBRTL2.EXE LIBRTL_INSTRUMENTED.EXE MESSAGE_ROUTINES.EXE STARLET.OLB - Updated with LIB$DATE_ARITHMETIC and LIB$DATE_CVT For OpenVMS VAX V5.5 through V7.0: LIBRTL$ECO_DROP.COM (If desired, this command file may be used to remove the ECO and restore the original files and libraries. If this file is used to remove the kit from the system, the system needs to be rebooted after the successful removal of the kit.) SOURCE: Digital Equipment Corporation ECO INFORMATION: ECO Kit Name: VAXLIBR06_070 ECO Kits Superseded by This ECO Kit: VAXLIBR05_070 VAXLIBR02_070 VAXLIBR01_070 VAXLIBR02_062 VAXLIBR01_062 ECO Kit Approximate Size: 4770 Blocks Saveset A - 126 Blocks Saveset B - 378 Blocks Saveset C - 396 Blocks Saveset D - 414 Blocks Saveset E - 1134 Blocks Saveset F - 1152 Blocks Saveset G - 1170 Blocks Kit Applies To: OpenVMS VAX V5.5, V5.5-1, V5.5-2, V5.5-2H4, V5.5-2HF, V5.5-2HW, V6.0, V6.1, V6.2, V7.0 System/Cluster Reboot Necessary: Yes Installation Rating: 1 - To be installed on all systems running the listed version(s) of OpenVMS. NOTE: In order to receive the full fixes listed in this kit, the following remedial kits also need to be installed: None ECO KIT SUMMARY: An ECO kit exists for the LIBRTL routines on OpenVMS VAX V5.5 through V7.0. Problems addressed in the VAXLIBR06_070 kit for OpenVMS VAX V5.5-2, V5.5-2H4, V5.5-2HW, and V5.5-2HF *ONLY*: o The VAXLIBR05_070 remedial kit contains a fix that causes a Kernel Stack Not Valid Bugcheck which resulted in a system reboot. This appears to happen under two circumstances: + The system has at least one secondary pagefile installed and AUTOGEN is run with preserve feedback (i.e., AGEN$FEEDBACK.EXE is run). + The POLYCENTER DECps product is installed and run on the system, specifically the Data Collection portion DECps-DC. If either of the above are run after the VAXLIBR05_070 kit has been installed on V5.5-2*, the system will crash. NOTE: This is only a problem for customers running V5.5-2*. If you are running a version other than V5.5-2* and have installed the VAXLIBR05_070 remedial kit, you do not need to install the VAXLIBR06_070 kit. o Possible memory leak when calling lib$get_vm. o The message length field in the message sent to the queue manager can get corrupted when the buffer size exceeds 64K and the user process can obtain 64K of P1 space. o Sometimes, during a heavy system load, a process may lose the response to a queuing request and the command will hang indefinitely. o In order to correct a problem where the batch/print queue manager can lose a connection to one of its client nodes (after a failover), the $SNDJBC system service has added the new status return code QMAN$_RETRYLINK. This informs the queue manager to attempt to re-establish its link to this client node. The new status is returned when the client node detects that the queue manager is attempting to link, but context for a previous link still exists. However, in order to correct the lost connection problem, you must be running a version of the queue manager which recognizes the new QMAN$_RETRYLINK status code. Queue manager versions beginning with OpenVMS VAX V6.0 contain the update which recognizes the new status code. The update is also available in the remedial kit VAXQMAN03_070. If you are experiencing the lost connection problem (a very low probability event), and have installed the VAXLIBR06_070 kit, you may see OPCOM messages similar to the following (on the operator console or in the operator log file): %%%%%%%%%%% OPCOM 6-AUG-1992 15:06:00.26 %%%%%%%%%%% Message from user QUEUE_MANAGE on SUMNODE %QMAN-E-COMMERROR, unexpected error #5 in communicating with node CSID 0008000B %%%%%%%%%%% OPCOM 6-AUG-1992 15:06:00.28 %%%%%%%%%%% Message from user QUEUE_MANAGE on SUMNODE -QMAN-W-NOMSG, Message number 04FE8678 o Allow lower case months to be entered to the $BINTIM system service. Problems addressed in the VAXLIBR05_070 kit for OpenVMS VAX V5.5, V5.5-1, V5.5-2, V5.5-2H4, V5.5-2HF, V5.5-2HW, V6.0, V6.1, V6.2 and V7.0: o The OpenVMS operating system has a documented delta-time restriction that may cause an error in some applications and OpenVMS components beginning on or around 19-MAY-1997. This ECO corrects this potential problem by removing the delta-time limit. Applications and OpenVMS components most likely to experience errors are those that pass delta-time arguments with values exceeding 9999 days on system-supplied date routines. The most likely date that these errors will occur is 19-MAY-1997:00:00, which is 10,000 days after the common UNIX time origin of 1-JAN-1970. This problem is fixed in OpenVMS VAX V7.1. Problems addressed in the VAXLIBR02_070 kit for OpenVMS VAX V6.1, V6.2, and V7.0: o Heaps that are removed from the heap pending list are only merged with the most recently returned heap. This can lead to heap fragmentation (LIB$VM_REALLOC fragmentation). Problems addressed in the VAXLIBR01_070 kit for OpenVMS VAX V6.1, V6.2, and V7.0: o LIB$FID_TO_NAME has been modified to ensure that the use of very deep directory trees do not result in the call stack being corrupted. o The 10,000 day limit in LIB$CVT_TO_INTERNAL_TIME causes problems for DECthreads since it is using this routine to convert UNIX times to VAX time. It will fail to work on 19-May-1997. Problems addressed in the VAXLIBR02_062 kit for OpenVMS V6.1 and V6.2: o When setting host into a DECnet PhaseV system, the logical name SYS$REM_NODE is incorrectly set. When the code was originally written there was no support for node synonyms. The value for SYS$REM_NODE is currently coming from a NET$K_TAG_COMPRESSEDNAME request but needs to be set from a NET$K_TAG_NODESYNONYM request. Problems addressed in the VAXLIBR01_062 kit for OpenVMS V6.2: o Due to an integer overflow, LIB$CVT_DX_DX returns a status of 00158334 (LIB$_INTOVF) when converting '-2147483648' to quadword. INSTALLATION NOTES: In order for the corrections in this kit to take effect, the system must be rebooted. If the system is a member of a VMScluster, the entire cluster should be rebooted. NOTE: If you are not running version 5.5-2* and have already installed the VAXLIBR05_070 remedial kit, you do NOT need to install VAXLIBR06_070.

This patch can be found at any of these sites:

Files on this server are as follows:

vaxlibr06_070.README
vaxlibr06_070.CHKSUM
vaxlibr06_070.CVRLET_TXT
vaxlibr06_070.a-dcx_vaxexe
vaxlibr06_070.b-dcx_vaxexe
vaxlibr06_070.c-dcx_vaxexe
vaxlibr06_070.d-dcx_vaxexe
vaxlibr06_070.e-dcx_vaxexe
vaxlibr06_070.f-dcx_vaxexe
vaxlibr06_070.g-dcx_vaxexe