Updated: 24-SEP-2003 (Use your browsers' Reload button to ensure you're viewing the most recent version)
VAXDRIV12_U2055 VAX V5.5-2 DUDRIVER ECO Summary
Copyright (c) Digital Equipment Corporation 1997. All rights reserved.
OP/SYS: OpenVMS VAX
COMPONENT: DUDRIVER
TUDRIVER
SOURCE: Digital Equipment Corporation
ECO INFORMATION:
ECO Kit Name: VAXDRIV12_U2055
ECO Kits Superseded by This ECO Kit: VAXDRIV11_U2055
VAXDRIV04_070 (Supersedes the
OpenVMS VAX V5.5-2x section
of this kit *ONLY*)
VAXDRIV02_070
ECO Kit Approximate Size: 162 Blocks
Kit Applies To: OpenVMS VAX V5.5-2, V5.5-2H4, and V5.5-2HF
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_U2055 on OpenVMS VAX V5.5-2 systems
NOTE: The DUDRIVER.EXE image contained in this kit for OpenVMS
V5.5-2 is more current than the DUDRIVER.EXE images contained
in the VAXSHAD09_U2055 ECO kit.
ECO KIT SUMMARY:
An ECO kit exists for DUDRIVER/TUDRIVER on OpenVMS VAX V5.5-2, V5.5-2H4,
and V5.5-2HF. This kit addresses the following problems:
Problems addressed in the VAXDRIV12_U2055 Kit:
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.
Problems addressed in the VAXDRIV11_U2055 Kit:
o These OpenVMS VAX V5.5-2 problem corrections were included in
the multi-version VAXDRIV04_070 remedial kit. They are now
being issued as a V5.5-2 only remedial kit.
There are no new problem corrections in this remedial kit.
Problems addressed in the VAXDRIV04_070 Kit:
o A PGFIPLHI 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.
RELATED ARTICLES:
Detailed articles describing the problems listed above may exist in
the STORAGE and OPENVMS databases. To view these articles, open
the appropriate product database and perform a query using either of
the following search strings: 'VAXDRIV12_U2055,' 'VAXDRIV' or
'VAXSHAD'.
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 |
+----------------------------+----------+-----------------+--------------+
| DUDRIVER.EXE |%X3DD48634| X-19A19A1A10 | 7-JUL-1997 |
| | | 14:15:45.42 |
+----------------------------+----------+-----------------+--------------+
| TUDRIVER.EXE |%XAC0A6896| X-20A7B6 | 7-JUL-1997 |
| | | 14:15:47.25 |
+----------------------------+----------+-----------------+--------------+
|
