ECO NUMBER:     VAXLIBR03_062
             PRODUCT:        OpenVMS VAX OPERATING SYSTEM 6.2
             UPDATE PRODUCT: OpenVMS VAX OPERATING SYSTEM 6.2




                                COVER LETTER


1  KIT NAME:

     VAXLIBR03_062


2  KITS SUPERSEDED BY THIS KIT:

     VAXLIBR06_070 for OpenVMS V6.2 only


3  KIT DEPENDENCIES:

     3.1  The  following  remedial  kit(s)  must  be  installed   BEFORE
          installation of this, or any required kit:

     None.


     3.2  In order to receive all the corrections listed  in  this  kit,
          the following remedial kits should also be installed:

     None.


4  KIT DESCRIPTION:

     4.1  Version(s) of OpenVMS to which this kit may be applied:

     OpenVMS VAX V6.2


     4.2  Files patched or replaced:


      o  [SYSLIB]LIBRTL.EXE (new image)

      o  [SYSLIB]LIBRTL2.EXE (new image)

      o  [SYSLIB]LIBRTL_INSTRUMENTED.EXE (new image)



5  PROBLEMS ADDRESSED IN VAXLIBR03_062 KIT


      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.


-- COVER LETTER --                                              Page 2
                                                          24 June 1998


6  PROBLEMS ADDRESSED IN VAXLIBR05_070 KIT FOR OPENVMS V6.2 ONLY


      o  The  OpenVMS  operating  system  has  a  documented  delta-time
         restriction that may cause a serious error in some applications
         and OpenVMS components  beginning  on  or  around  19-MAY-1997.
         DIGITAL  has  corrected this potential problem and has provided
         ECOs (Engineering Change Orders)  that  remove  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.


         6.0.1  Fixed in:  V7.1


7  PROBLEMS ADDRESSED IN VAXLIBR02_070 KIT FOR OPENVMS V6.2 ONLY


      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.



8  PROBLEMS ADDRESSED IN VAXLIBR01_070 KIT FOR OPENVMS V6.2 ONLY


      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.



9  PROBLEMS ADDRESSED IN VAXLIBR02_062 KIT FOR OPENVMS V6.2 ONLY


      o  When the code was originally written there was no  support  for
         node synonyms.  Now that the support is there, people are using
         it The code doesn't get the right value from the network call.


-- COVER LETTER --                                              Page 3
                                                          24 June 1998


10  PROBLEMS ADDRESSED IN VAXLIBR01_062 KIT


      o  LIB$CVT_DX_DX returns a status of 00158334  (LIB$_INTOVF)  when
         converting '-2147483648' to quadword.



11  KIT INSTALLATION RATING:

     The following kit  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)

     INSTALLATION RATING:

       INSTALL_3 : To  be  installed  by  customers  experiencing  the  problems
           corrected.



12  INSTALLATION INSTRUCTIONS:

     Install this kit with the VMSINSTAL utility  by  logging  into  the
     SYSTEM account, and typing the following at the DCL prompt:

         @SYS$UPDATE:VMSINSTAL VAXLIBR03_062 [location of the saveset]

     The saveset location may be a tape drive, or a disk directory  that
     contains the kit saveset.

     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.


     Copyright  (c)  Digital  Equipment  Corporation,  1998  All  Rights
     Reserved.   Unpublished rights reserved under the copyright laws of
     the United States.

     The software contained on this media is proprietary to and embodies
     the  confidential  technology  of  Digital  Equipment  Corporation.
     Possession, use, or dissemination of  the  software  and  media  is
     authorized  only  pursuant  to a valid written license from Digital
     Equipment Corporation.

     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

-- COVER LETTER --                                              Page 4
                                                          24 June 1998


     PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY EXCLUDED TO THE
     EXTENT PERMITTED BY APPLICABLE LAW.  IN NO EVENT  WILL  DIGITAL  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.