Updated: 24-SEP-2003 (Use your browsers' Reload button to ensure you're viewing the most recent version)
VAXLIBR03_062 VAX V6.2 LIBRTL ECO Summary
Copyright (c) Digital Equipment Corporation 1998. All rights reserved.
OP/SYS: OpenVMS VAX
COMPONENTS: LIBRTL.EXE
LIBRTL2.EXE
LIBRTL_INSTRUMENTED.EXE
SOURCE: Digital Equipment Corporation
ECO INFORMATION:
ECO Kit Name: VAXLIBR03_062
ECO Kits Superseded by This ECO Kit: VAXLIBR06_070 ( For OpenVMS
VAX V6.2 only)
VAXLIBR05_070
VAXLIBR02_070
VAXLIBR01_070
VAXLIBR02_062
VAXLIBR01_062
ECO Kit Approximate Size: 1129 Blocks
Saveset A - 1116 Blocks
Kit Applies To: OpenVMS VAX V6.2
System/Cluster Reboot Necessary: Yes
Rolling Reboot Supported: Yes
Installation Rating: 3: To be installed by customers experiencing
the problems corrected
KIT DEPENDENCIES:
The following remedial kit(s) must be installed BEFORE
installation of this, or any required kit:
VAXY2K02_062
In order to receive all the corrections listed in this kit,
the following remedial kits should also be installed:
None.
ECO KIT SUMMARY:
An ECO kit exists for the LIBRTL routines on OpenVMS VAX V6.2.
This kit addresses the following problems:
Problems addressed in VAXLIBR03_062:
o The wrong length was returned in the resultant-length field
from LIB$GET_FOREIGN in the case that the input string was
truncated. LIB$GET_FOREIGN was returning the original length
of the string instead of the truncated length.
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.
RELATED ARTICLES:
Detailed articles describing the problems listed above may exist in the
OPENVMS database. To view these articles, open the appropriate product
database and perform a query using either of the following search
strings: 'VAXLIBR03_062' or 'VAXLIBR'.
ECO KIT ORDERING INSTRUCTIONS:
If after an evaluation you wish to obtain this kit, request it
electronically using the appropriate Advanced Electronic Services
(AES) Service Tool. If you are not familiar with how to request
kits electronically, open the DIA, WIS or DSNLINK database and
review the article entitled:
[AES] How To Electronically Request ECO Kits Using Service Tools
INSTALLATION NOTES:
The images in this kit will not take effect until the system is
rebooted.
If you have other nodes in your VMS 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.
==========================================================================
| Table of Kit Image Information |
+----------------------------+----------+-----------------+--------------+
| | Overall | Image File | Image Link |
| Image Name | Checksum | Identification | Date/Time |
+----------------------------+----------+-----------------+--------------+
| LIBRTL.EXE |%X863158F6| V06-001 | 11-JUN-1998 |
| | | 09:01:40.28 |
+----------------------------+----------+-----------------+--------------+
| LIBRTL2.EXE |%X7AFED5AB| V05-000 | 11-JUN-1998 |
| | | 09:01:46.90 |
+----------------------------+----------+-----------------+--------------+
| LIBRTL_INSTRUMENTED.EXE |%X8B62D7FC| V06-001 | 11-JUN-1998 |
| | | 09:05:49.74 |
+----------------------------+----------+-----------------+--------------+
|
