*******************************************************************************
* *
* This is an update to an existing patch... *
* *
* Online links can be found at *
* http://ftp.support.compaq.com/patches/public/vms/axp/v7.2-1/dec-axpvms-vms721_librtl-v0300--4.README
*******************************************************************************

TITLE: OpenVMS VMS721_LIBRTL-V0300 Alpha V7.2-1 LIBRTL ECO Summary

New Kit Date : 28-JUN-2001
Modification Date: Not Applicable
Modification Type: Updated Kit Supersedes VMS721_LIBRTL-V0200
 
NOTE: An OpenVMS saveset or PCSI installation file is stored
       on the Internet in a self-expanding compressed file.
 
       For OpenVMS savesets, the name of the compressed saveset
       file will be kit_name.a-dcx_vaxexe for OpenVMS VAX or
       kit_name.a-dcx_axpexe for OpenVMS Alpha. Once the OpenVMS
       saveset is copied to your system, expand the compressed
       saveset by typing RUN kitname.dcx_vaxexe or kitname.dcx_alpexe.
 
       For PCSI files, once the PCSI file is copied to your system,
       rename the PCSI file to kitname-dcx_axpexe.pcsi, then it can
       be expanded by typing RUN kitname-dcx_axpexe.pcsi. The resultant
       file will be the PCSI installation file which can be used to install
       the ECO.
 

Copyright (c) Compaq Computer Corporation 2001. All rights reserved.

OP/SYS: OpenVMS Alpha

COMPONENT: LIBRTL

SOURCE: Compaq Computer Corporation

ECO INFORMATION:

     ECO Kit Name: VMS721_LIBRTL-V0300
                    DEC-AXPVMS-VMS721_LIBRTL-V0300--4.PCSI
     ECO Kits Superseded by This ECO Kit: VMS721_LIBRTL-V0200
     ECO Kit Approximate Size: 4544 Blocks
     Kit Applies To: OpenVMS Alpha V7.2-1
     System/Cluster Reboot Necessary: Yes
     Rolling Re-boot Supported: Yes
     Installation Rating: INSTALL_3
                            3 - To be installed on all systems running
                                the listed versions of OpenVMS which
                                are experiencing the problems described.
 
     Kit Dependencies:

       The following remedial kit(s) must be installed BEFORE
       installation of this kit:

         VMS721_UPDATE-V0200
         VMS721_PCSI-V0100

       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 LIBRTL on OpenVMS Alpha V7.2-1.
This kit addresses the following problems:

PROBLEMS ADDRESSED IN VMS721_LIBRTL-V0300 KIT

  o The V7.2 and V7.2-1 stack walking and stack frame accessing
      routines, e.g., lib$calling_standard routines, sometimes fail.
      That is, they complain (sometimes ACCVIO) about illegal (do
      not conform to the calling standard) stack frames and cannot
      access frames previous to the illegal frame. Because of this,
      it is possible, especially in AST, thread, or interrupt rich
      applications, to encounter such illegal stacks, which will
      cause the application to fail.

          Images Affected: [SYSLIB]LIBRTL.EXE
                            [SYSLIB]LIBRTL_INSTRUMENTED.EXE

  o A routine that declares lib$sig_to_ret as an exception handler
      returns an unexpected status return, a C signal, SS$_BREAK,
      SS$_IMGDMP or SS$_DEBUG.

          Images Affected: [SYSLIB]LIBRTL.EXE

PROBLEMS ADDRESSED IN VMS721_LIBRTL-V0200 KIT

  o Each Time NET$ACP writes DECNET$CDI_CACHE.DAT, it allocates a
      channel to SYS$SYSDEVICE and never frees it.

      The NET$ACP process performs checkpoints on its cache file by
      writing to a temporary file and then, utilizing a DECC rename
      routine, it renames the temporary file back to
      DECNET$CDI_CACHE.DAT. The DECC rename routine invokes the
      runtime library routine LIB$RENAME_FILE.

      Processes that utilize the LIB$RENAME_FILE library routine,
      such as NET$ACP, may lose a process channel and memory each
      time the library routine is called. This failure occurs when
      the files to be renamed are pointed to by a searchlist
      logical. The pgflquota of net$acp decreases continuously
      until it reaches zero.

          Images Affected: [SYSLIB]LIBRTL.EXE.
                            [SYSLIB]LIBRTL_INSTRUMENTED.EXE.

  o A PASCAL program that calls the LIB$FID_TO_NAME routine, with
      an empty varying string as the output file specification,
      receives an LIB$_INVARG return status.

          Images Affected: [SYSLIB]LIBRTL.EXE.

  o The lib$mult_delta_time routine returns a %LIB-F-IVTIME
      'invalid time' error message when a negative multiplier is
      supplied to the routine.

          Images Affected: [SYSLIB]LIBRTL.EXE

  o After installing the VMS721_LIBRTL-V0100 TIMA kit,
      LIB$FIND_IMAGE_SYMBOL fails with -RMS-F-DEV, error in device
      name or inappropriate device type. Programs using
      LIB$FIND_IMAGE_SYMBOL in images that are on disks, which are
      served by MSCP (mass storage control program) but have an
      allocation class, fail with this error message. For example:

      Assume node X is a satellite of the cluster and that $4$DUA300
      is a disk served by node MASTER from an HSX called HSX. Using
      $GETDVI with item code DVI$_DEVNAM, the return values are:

          Node X is _MASTER$DUA300:
          MASTER is _HSX$DUA300:

          Images Affected: [SYSLIB]LIBRTL.EXE

  o LIB$GET_LOGICAL does not return a logical translation
      resultant length when it is set to "0." LIB$GET_LOGICAL will
      only return a "resultant-length" if the length passed in is
      greater than the length of the logical name equivalent
      returned by this service.

          Images Affected: [SYSLIB]LIBRTL.EXE

Problems Addressed in VMS721_LIBRTL-V0100:

  o A memory leak occurs when using LIB$FIND_FILE/LIB$FIND_FILE_END
      with long file names (flags=LIB$M_FIL_LONG_NAMES).

          Images Affected: [SYSLIB]LIBRTL.EXE
                            [SYSLIB]LIBRTL_INSTRUMENTED.EXE

  o A synchonization failure occurs for multithread programs using
      the DEC C RTL routine malloc and free with "long" pointers (P2
      space heap routines). These DEC C RTL routines in turn use
      the LIBRTL Routines LIB$VM_MALLOC_64 and LIB$VM_FREE_64.
      Symptoms could be varied, including "%LIB-F-MEMALRFRE, memory
      already free" errors.

      For an application to see this problem it would have to have
      the following characteristics:

          1. Call the DEC C RTL routines malloc and free

          2. Be multithreaded

          3. Be compiled with the /POINTER_SIZE=LONG and
             /REENTRANCY=MULTITHREAD switches

          4. Be linked /THREADS_ENABLE=(MULTIPLE_KERNEL_THREADS,UPCALLS)

          5. Run on a multiprocessor system with kernel threads
             enabled.

      Note that programs using the "normal" P0 heap routines are not
      affected by this problem.

          Images Affected: [SYSLIB]LIBRTL.EXE
                            [SYSLIB]LIBRTL_INSTRUMENTED.EXE

  o The LIB$CREATE_DIR RTL routine is documented to accept 64 bit
      parameters. However, passing a 64 bit descriptor to the
      routine fails with a LIB$_INVSTRDES error or passing a 64 bit
      address may result in an SS$_ACCVIO error.

          Images Affected: [SYSLIB]LIBRTL.EXE
                            [SYSLIB]LIBRTL_INSTRUMENTED.EXE

  o A program can fail with the following error:

         %LIB-W-ILLRECTYP, illegal record type (nnn)
         %TRACE-W-TRACEBACK, symbolic stack dump follows

      followed by:

         %SYSTEM-F-ACCVIO, access violation, reason mask=00,
         virtual address=0000000000000008, PC=nnnnnnnnnnnnnnnn,
         PS=0000001B

      if the program:

          1. Is created that is directly linked with a shareable image

          2. Calls LIB$FIND_IMAGE_SYMBOL to find an entry point in the
              same shareable image

          3. The program is executed and the user creates a new version
              of the shareable image while the program is executing

          Images Affected: [SYSLIB]LIBRTL.EXE
                            [SYSLIB]LIBRTL_INSTRUMENTED.EXE

  o LIB$FIND_IMAGE_SYMBOL fails to locate symbols for images whose
      record attributes have been altered.

      This has been seen with DCOM as follows:

        $ mcr DCOM$COMREGEDT

        %SYSTEM-F-ACCVIO, access violation, reason mask=00,
        virtual address=0000000000000008, PC=0000000000B43348,
        PS=0000001B

        Improperly handled condition, image exit forced.
        Signal arguments: Number = 0000000000000005
                            Name = 000000000000000C
                                     0000000000000000
                                     0000000000000008
                                     0000000000B43348
                                     000000000000001B

          Images Affected: [SYSLIB]LIBRTL.EXE
                            [SYSLIB]LIBRTL_INSTRUMENTED.EXE

  o LIB$FIND_IMAGE_SYMBOL fails for images on disks whose device
      names are more than 13 characters - which generally means a 3
      digit unit number.

          Images Affected: [SYSLIB]LIBRTL.EXE
                            [SYSLIB]LIBRTL_INSTRUMENTED.EXE

  o In the case of a $ PRINT [X]FOO.PRF,;-1 command, LIB$FIND_FILE
      may fail to find the second file (;-1). This problem may be
      seen with certain DCL commands, such as PRINT, and with user
      application calls to LIB$FIND FILE when LIB$M_FIL_LONG_NAMES
      and the "multiple" flags are set (bits 1 and 2 of the flags
      argument).

          Images Affected: [SYSLIB]LIBRTL.EXE
                            [SYSLIB]LIBRTL_INSTRUMENTED.EXE

  o A failure to unwind properly occurs when a large amount of
      stack space is being used. This could result in an improperly
      handled condition error, or a bad stack notification, or other
      error.

          Images Affected: [SYSLIB]LIBRTL.EXE
                            [SYSLIB]LIBRTL_INSTRUMENTED.EXE

INSTALLATION NOTES:

This kit requires a system reboot. Compaq 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.

INSTALLATION INSTRUCTIONS:

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 VMS721_LIBRTL /SOURCE=[location of Kit]

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

Additional help on installing PCSI kits can be found by typing
HELP PRODUCT INSTALL at the system prompt

All trademarks are the property of their respective owners.

---

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]