IMPORTANT NOTICE

Updated: 24-SEP-2003 (Use your browsers' Reload button to ensure you're viewing the most recent version)

To obtain this kit please call the Customer Support Centre or use the FTP site Search for this ECO kit and dependencies Search the Compaq FTP web site this kit (exact match) Search the Compaq FTP web site this or related ECOs

Copyright (c) Digital Equipment Corporation 1997.  All rights reserved.

OP/SYS:     OpenVMS VAX

COMPONENT:  PADRIVER.EXE
            PEDRIVER.EXE

SOURCE:     Digital Equipment Corporation

ECO INFORMATION:

     ECO Kit Name:  VAXDRIV03_062
     ECO Kits Superseded by This ECO Kit:  VAXLAVC01_062
     ECO Kit Approximate Size:  252 Blocks
     Kit Applies To:  OpenVMS VAX V6.2
     System/Cluster Reboot Necessary:  Yes

     Installation Rating:   3 - To be installed on all systems running
                                the listed versions of OpenVMS which
                                are experiencing the problems described.

     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 PADRIVER and PEDRIVER on OpenVMS VAX V6.2.
This kit addresses the following problems:

Problems Addressed in the VAXDRIV03_062 Kit:

  o  Adapters such as the KFESA restart and log "Invalid Buffer
     Name" errors.  INVALID BUFFER NAME errors are a known issue
     that occur as a result of an incompatibility (or "race
     condition" as mentioned in the original case text) in certain
     hardware where there is a different perception of when a DSSI
     packet has been "received" as good.  If a reset occurs during
     this time (before BUS FREE), the initiator will resend the
     packet to the target that has already accepted the packet as
     "good".  If the resent packet is the last in a buffered data
     transfer, the re-transmit attempt may not occur until after the
     target has invalidated its buffer descriptor resulting in the
     error.

     This appears to happen in systems at times of heavy I/O
     activity.

  o  Any message which is received with an SCS$W_STATUS field of 0
     will cause OpenVMS to crash.  The  crash  will be an "INVEXCEPTN,
     Exception while above ASTDEL" in SYS$SCS.  This situation will not
     occur very often.  It is basically caused by non-compliance to SCS
     specifications or by errors in firmware.


Problems Addressed in the VAXLAVC01_062 ECO Kit:

  o  Nodes in an LAVC (Local Area VAX Cluster) may CLUEXIT bugcheck
     in mixed ENET/FDDI environments where duplicate hello messages are
     being produced (i.e., out-of-rev bridge firmware).


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: 'VAXDRIV03_062' or 'VAXDRIV'.


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:

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.
  
  ==========================================================================
  |                     Table of Kit Image Information                     |
  +----------------------------+----------+-----------------+--------------+
  |                            | Overall  | Image File      | Image Link   |
  | Image Name                 | Checksum | Identification  | Date/Time    |
  +----------------------------+----------+-----------------+--------------+
  | PADRIVER.EXE               |%X22FFCFE8| X-29            |  5-MAY-1997  |
  |                                       |                 | 15:39:16.83  |
  +----------------------------+----------+-----------------+--------------+
  | PEDRIVER.EXE               |%X42AFB8A0| VMS-5           |  5-MAY-1997  |
  |                                       |                 | 15:39:35.69  |
  +----------------------------+----------+-----------------+--------------+