Updated: 24-SEP-2003 (Use your browsers' Reload button to ensure you're viewing the most recent version)
VAXLAD02_061 OpenVMS VAX V6.1 LAD Drivers ECO Summary
Copyright (c) Digital Equipment Corporation 1998. All rights reserved.
OP/SYS: OpenVMS VAX
COMPONENTs: DADDRIVER (SYS$DADDRIVER.EXE)
LADDRIVER (SYS$LADDRIVER.EXE)
LASTDRIVER (SYS$LASTDRIVER.EXE)
MADDRIVER (SYS$MADDRIVER.EXE)
ESS$LASTCP.EXE
ESS$LADCP.EXE
ESS$LAST_STARTUP.COM
ESS$STARTUP.COM
SOURCE: Digital Equipment Corporation
ECO INFORMATION:
ECO Kit Name: VAXLAD02_061
ECO Kits Superseded by This ECO Kit: VAXLAD01_061 (Not Released for Use)
ECO Kit Approximate Size: 411 Blocks
Saveset A - 396 Blocks
Kit Applies To: OpenVMS VAX V6.1
System/Cluster Reboot Necessary: Yes
Rolling Re-boot Supported: Yes
Installation Rating: 2 - To be installed on all systems running
the listed version of OpenVMS and
using the following feature:
InfoServer
Kit Dependencies:
The following remedial kit(s) must be installed BEFORE
installation of this kit:
None
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 SYS$DADDRIVER, SYS$LADDRIVER, SYS$LASTDRIVER, and
SYS$MADDRIVER on OpenVMS VAX V6.1. This kit addresses the following problems:
PROBLEMS ADDRESSED IN VAXLAD02_061 KIT:
o UCB$L_DEVCHAR2 characteristics bits are not defined correctly
when the template UCB is created. This problem causes SECURITY
to crash the system and causes LADCP> BIND SERVICE/TAPE to
prefix device name, MADx, with a node name or allocation class.
This result is inconsistent with the DAD device naming
convention.
o The occasional packet transmitted by EWDRIVER had a source
address and protocol type of zeros, which are discarded by the
receiver. The booting system then retransmitted the packet 3
seconds later. However, since it is handling only 10 packets
per second, the system booted very slowly.
o If LADDRIVER parses connection (or solicitation) messages that
have the sign bit set in the service class (an invalid value),
the OpenVMS system will crash with an INVEXCEPTN bugcheck.
o The system crashes in LTDRIVER when SSB is deleted prematurely
while an UNLOAD is in progress.
o LASTDRIVER/DADDRIVER/MADDRIVER fixes:
1. Typing a CTRL/Y at a certain instance could cause an
IO$_PACKACK function to a MAD device to be canceled. The
result could eventually be that the system crashes in I/O
post processing.
2. LADCP BIND/UNIT=x will cause a duplicate UCB unit number to
be generated if the unit number specified is greater then
the seed unit number. This problem can happen for both
DADDRIVER and MADDRIVER.
o LASTDRIVER crashes when it receives a run message in circuit
stalled.
PROBLEMS ADDRESSED IN THE VAXLAD01_061 KIT:
o Routine READ_BFRS_DONE_WITH, of module LADDRIVER, attempts to
remove the IOP from the active queue. If the active queue is
zero, then the request has already been aborted and the system
crashes.
In a different system crash scenario, if routine LAD$REQUEST_CU
is called with the wrong function, or an IOP cannot be acquired
due to some resource allocation failure, the attempt is made to
re-insert the IOP on the FREE_IOP_Q. The system crashes with
INVEXCEPTN because the IOP address is invalid.
o The SWEEP_CACHE routine was being called from
LAD$END_SESSION_CU routine with the wrong register pointing at
the server descriptor block. This prevented the cache blocks
associated with the session to be terminated, but not
invalidated correctly. Therefore, these blocks remained in the
cache.
Subsequently, the virtual disk could be dismounted, and
modified by PCDISK. When the virtual disk was remounted again,
the blocks held in cache did not reflect the modifications, and
data corruption occurred.
o Container file corruption for PATHWORKS
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: 'VAXLAD02_061' or 'VAXLAD'.
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:
The images in this kit will not take effect until the system is
rebooted. If there are other nodes in the VMScluster, they must
also be rebooted in order to make use of the new images.
If it is not possible or convenient to reboot the entire cluster at
this time, a rolling re-boot may be performed.
==========================================================================
| Table of Kit Image Information |
+----------------------------+----------+-----------------+--------------+
| | Overall | Image File | Image Link |
| Image Name | Checksum | Identification | Date/Time |
+----------------------------+----------+-----------------+--------------+
| DADDRIVER.EXE |%X694780FF| X-12A1 | 5-JAN-1998 |
| | | 20:15:37.98 |
+----------------------------+----------+-----------------+--------------+
| LADCP.EXE |%XC45FDAFB| V13.0 | 5-JAN-1998 |
| | | 20:15:04.15 |
+----------------------------+----------+-----------------+--------------+
| LADDRIVER.EXE |%X0590E03A| X-11A3 | 5-JAN-1998 |
| | | 20:14:56.21 |
+----------------------------+----------+-----------------+--------------+
| LASTCP.EXE |%XCA4F9149| X-4A1 | 5-JAN-1998 |
| | | 20:15:23.07 |
+----------------------------+----------+-----------------+--------------+
| LASTDRIVER.EXE |%XF77591A0| X-20A3 | 5-JAN-1998 |
| | | 20:15:14.54 |
+----------------------------+----------+-----------------+--------------+
| MADDRIVER.EXE |%X2A82540B| X-5A4 | 5-JAN-1998 |
| | | 20:15:44.15 |
+----------------------------+----------+-----------------+--------------+
|
