OpenVMS VAXDRIV03_071 VAX V7.1 PADRIVER/PEDRIVER 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 1997.  All rights reserved.

OP/SYS:     OpenVMS VAX 

COMPONENT:  PADRIVER.EXE
            PEDRIVER.EXE

SOURCE:     Digital Equipment Corporation

ECO INFORMATION:

     ECO Kit Name:  VAXDRIV03_071 
     ECO Kits Superseded by This ECO Kit:  VAXDRIV02_071 
     ECO Kit Approximate Size:  252 Blocks
     Kit Applies To:  OpenVMS VAX V7.1 
     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 V7.1. 
This kit addresses the following problems: 

Problems Addressed in the VAXDRIV03_071 Kit:

  o  The ALPDRIV02_071 ECO documented that a bugcheck was fixed.   
     However, that fix did not get populated into the ALPDRIV02_071 
     kit.  This kit, ALPDRIV03_071, fixes that problem and does 
     contain the fix for the bugcheck.  See the section below entitled
     "Problems Addressed in the VAXDRIV02_071 Kit:" for a complete 
     explanation of the bugcheck problem and fix.

Problems Addressed in the VAXDRIV02_071 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.

     Any message which is received with an SCS$W_STATUS field of 0
     will cause OpenVMS to crash.  This situation will not occur
     very often, it is basically caused by non-compliance to SCS
     specifications - or by errors in firmware.

     Routine SCS$MAP_SCSSTS is used to translate the returned SCS
     status code into a standard SS type VMS status code.  The VMS
     status code is used in subsequent SCS code paths.  The crash
     was caused by routine CONNECT_FAIL correctly deallocating the
     CDT for the connection in error, however when resuming the
     original CONNECT thread from the fork process in the deallocated 
     CDT, a returned status of SS$_NORMAL caused the fork process to 
     assume it still had a CDT rather than treat as an error.

  o  An INVEXCEPTN bugcheck can occur in SCS due to erroneous packets
     received from third party hardware.  This specifically occurs 
     with MTI's Disk Server STINGRAY SERVER 3.


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. 

Colorado Site
Georgia Site

vaxdriv03_071.README
vaxdriv03_071.CHKSUM
vaxdriv03_071.CVRLET_TXT
vaxdriv03_071.a-dcx_vaxexe