Updated: 24-SEP-2003 (Use your browsers' Reload button to ensure you're viewing the most recent version)
ALPLAD01_061 for OpenVMS Alpha V6.1 Drivers ECO Summary
Copyright (c) Digital Equipment Corporation 1998. All rights reserved.
OP/SYS: OpenVMS Alpha
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: ALPLAD01_061
ECO Kits Superseded by This ECO Kit: ALPLAD03_070
ECO Kit Approximate Size: 1172 Blocks
Saveset A - 1152 Blocks
Kit Applies To: OpenVMS Alpha V6.1, V6.1-1H1, V6.1-1H2
System/Cluster Reboot Necessary: Yes
Rolling Re-boot Supported: Yes
Installation Rating: 2 - To be installed on all systems running
the listed versions 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 Alpha V6.1 through V6.1-1H2. This kit addresses
the following problems:
PROBLEMS ADDRESSED IN ALPLAD01_061:
o LASTDRIVER/DADDRIVER/MADDRIVER fixes:
1. LASTDRIVER crashes when it receives a run message in the
circuit stalled state.
2. Typing a CTRL/Y could cause an IO$_PACKACK function to a
MAD device to be cancelled. The result could eventually be
that the system crashes in I/O post processing.
3. 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 The system crashes in LTDRIVER when SSB is deleted prematurely
while an UNLOAD is in progress.
o The LASTDRIVER image crashes when it receives an Advertisement
(ADV) or Solicit (SOL) message with a negative message length.
o In the past, BIND/TAPE/NOPERMANENT "tape_service" created a
MADx device UCB that could be deleted once the UCB reference
count went to zero. Problems occurred when the UCB was deleted
due to the use of the /NOPERMANENT qualifier, that is
multivolume BACKUP.
Note: A MAD device is a tape device that is attached to an
InfoServer.
PROBLEMS ADDRESSED IN ALPLAD03_070 KIT FOR OPENVMS ALPHA V6.1,
V6.1-1H1, V6.1-1H2
o Infoserver boots very slowly.
PROBLEMS ADDRESSED IN ALPLAD01_070 KIT FOR OPENVMS ALPHA V6.1,
V6.1-1H1, V6.1-1H2:
o Not waiting for "unit ready" caused system crashes in MADDRIVER
and LASTDRIVER.
o MADDRIVER has not supported reverse read. This fix allows the
user to issue READ with I/O modifier IO$M_REVERSE set.
o Adding new controller names FW & HC to internal table
DATA_RATES.
o There was no InfoServer virtual tape driver (MADDRIVER) support
for ALPHA OpenVMS V6.1. This change is to provide MADDRIVER
support for ALPHA OpenVMS V6.1:
o InfoServer tape client was enhanced to handle end of tape
and long tape operations (skip EOT) so the behavior is the
same as if the tape drive were attached locally.
o A private QIO was added so an ident string can be passed to
the LADCP program from both the tape client driver
(MADDRIVER) and the disk client driver.
o LASTDRIVER was enhanced to better handle a race condition
that occurred when multiple processes were doing a LADCP
SHOW SERVICES.
These fixes are included in V7.0 OpenVMS Alpha.
o There is a typographical error in the DCL command file used to
start the LAST transport.
PROBLEMS ADDRESSED IN ALPLAD01_062 KIT FOR OPENVMS ALPHA V6.1,
V6.1-1H1, V6.1-1H2
o After dismount and modification by PCDISK, when the virtual
disk was re-mounted the blocks held in the cache did not
reflect the modifications. Thus, data corruption occurred.
o Entering the following commands causes system to crash:
$ @sys$startup:ess$startup client
$ mc ess$lastcp
LASTCP> show active nodes
This problem is corrected in OpenVMS Alpha V6.2
o Routine READ_BFRS_DONE_WITH, of module LADDRIVER, attempts to
remove the IOP from the active queue. However, the active
queue is zero, the request has already been aborted, thus the
system crashes.
This problem is corrected in OpenVMS Alpha V6.2
o If routine LAD$REQUEST_CU, is called with the wrong function,
or if it is unable to acquire an IOP due to some resource
allocation failure, then LAD$REQUEST_CU will try to re-insert
the IOP on the FREE_IOP_Q. the system will then crash with an
INVEXCEPTN as there is an invalid IOP address.
This problem is corrected in OpenVMS Alpha V6.2
o There is an error (missing parentheses) in the DCL command file
used to start the LAST transport.
This problem is corrected in OpenVMS Alpha V6.2
o INVEXCEPTN bugcheck MADDRIVER+3c48 referencing a deallocated
IRP.
This problem is corrected in OpenVMS Alpha V6.2
o UCB$L_DEVCHAR2 characteristics bits are not defined correctly
when the template UCB is created. This causes SECURITY to
crash the system and causes LADCP> BIND SERVICE/TAPE to prefix
device name, MADx, with the node name or allocation class.
This is inconsistent with the DAD device naming convention.
o Container file corruption for PATHWORKS. None of the LAD
services can be written to without corrupting the data in the
service. After a write operation some of the errors with the
following format can be seen using CHKDSK on a disk service:
E:\EGASMC.FRS
Allocation error, size adjusted
E:\EGAUND.FRS
Has invalid allocation unit, file truncated
E:\EGASMC.FRS
Is cross linked on allocation unit 95
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: 'ALPLAD01_061' or 'ALPLAD'.
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 |
+----------------------------+----------+-----------------+--------------+
| ESS$LADCP.EXE | 052F9541 | A1.4 | 15-DEC-1997 |
| | | 13:47:20.53 |
+----------------------------+----------+-----------------+--------------+
| ESS$LASTCP.EXE | 9210F268 | A01-01 | 15-DEC-1997 |
| | | 13:47:15.61 |
+----------------------------+----------+-----------------+--------------+
| SYS$DADDRIVER.EXE | D19C4CA4 | X-3 | 15-DEC-1997 |
| | | 13:47:08.00 |
+----------------------------+----------+-----------------+--------------+
| SYS$LADDRIVER.EXE | 2E455578 | X-3 | 15-DEC-1997 |
| | | 13:46:41.28 |
+----------------------------+----------+-----------------+--------------+
| SYS$LASTDRIVER.EXE | 8A8AD516 | X-3 | 15-DEC-1997 |
| | | 13:46:52.22 |
+----------------------------+----------+-----------------+--------------+
| SYS$MADDRIVER.EXE | 63AE86AB | X-3 | 15-DEC-1997 |
| | | 13:46:59.51 |
+----------------------------+----------+-----------------+--------------+
|
