OpenVMS VAXDRIV06_061 VAX V6.1 DUDRIVER/TUDRIVER 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, 1998.  All rights reserved. 

OP/SYS:     DIGITAL OpenVMS VAX

COMPONENT:  DUDRIVER
            TUDRIVER

SOURCE:     Digital Equipment Corporation

ECO INFORMATION:

     ECO Kit Name:  VAXDRIV06_061
     ECO Kits Superseded by This ECO Kit:  VAXDRIV04_061
                                           VAXDRIV04_070 (Supersedes the
                                             OpenVMS VAX V6.1 section
                                             of this kit *ONLY*)
                                           VAXDRIV02_070
                                           VAXDRIV01_070
     ECO Kit Approximate Size:  162 Blocks
     Kit Applies To:  OpenVMS VAX V6.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:

                 VAXSHAD09_061
               OpenVMS VAX V6.1       VAXDRIV06_061


ECO KIT SUMMARY:

An ECO kit exists for DUDRIVER/TUDRIVER on OpenVMS VAX V6.1.  This kit 
addresses the following problems:

Problems addressed in the VAXDRIV06_061 Kit:

  o  Attempting to perform a directory of a mounted tape causes  the
     process  to  hang  and "INVALID COMMAND" MSCP END MSG* errorlog
     entries to be generated.

  o  Unexpected end messages are logged on client nodes for GUS and
     AVAILABLE commands.

  o  DUDRIVER does not FLUSH the pending queue of SHADOWING, HBR and
     served IOs when connection failure routines are entered.  This
     causes a system/cluster hang.

  o  A DCL copy command to a HSD05/10 based tape drive causes a
     process hang


Problems addressed in the VAXDRIV04_061 Kit:

  o  These OpenVMS VAX V6.1 problem corrections were included in
     the multi-version VAXDRIV04_070 remedial kit.  They are now
     being issued as a V6.1 only remedial kit.

     There are no new problem corrections in this remedial kit.


Problems addressed in the VAXDRIV04_070 Kit:  

  o  A PGFLIPLHI system crash may occur when the controller is rebooted.

  o  A problem exists with HSJ/HSD30, 40 and 50 controllers where,
     after an event that initiates Mount Verification, a packet 
     acknowledgment will fail to complete.  The controller will 
     report that it is making progress on the command, but will 
     never finish.  This causes all IO to the affected devices to 
     hang.  


Problems addressed in the VAXDRIV02_070 Kit: 

  o  A node may hang due to no quorum after losing its connection 
     to the quorum disk.

  o  DUDRIVER does not log IRP information.


Problems addressed in the VAXDRIV01_070 kit:

  o  Static load balancing does not work as it designed to.                   
                                                                              
  o  System crashes occur in DUDRIVER, usually at FUNCTION_EXIT:.             
     However, the crashes may also occur in other places.                     
                                                                              
  o  The errorlog does not contain any information on the actual              
     outstanding command that has timed out from a Get Command                
     Status (GCS) query issued from DUDRIVER to the MSCP Server.              
                                                                              
  o  Host Based Shadowset Virtual Units hang in MountVerification.            
     All IO to the device is stalled.                                         
  


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


This patch can be found at any of these sites:


Colorado Site


Georgia Site




Files on this server are as follows:

vaxdriv06_061.README
vaxdriv06_061.CHKSUM
vaxdriv06_061.CVRLET_TXT
vaxdriv06_061.a-dcx_vaxexe