OpenVMS ALPLAD04_070 for OpenVMS Alpha V7.0 Drivers 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 1998. All rights reserved.
Modification Date: 19-MAY-1998
Modification Type: Updated ECO - supersedes ALPLAD03_070
OP/SYS: OpenVMS Alpha
COMPONENT: 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: ALPLAD04_070
ECO Kits Superseded by This ECO Kit: ALPLAD03_070
ALPLAD02_070
ALPLAD01_070
ALPLAD02_062
ALPLAD01_062
ECO Kit Approximate Size: 1182 Blocks
Saveset A - 1170 Blocks
Kit Applies To: OpenVMS Alpha V7.0
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 Alpha V7.0. This kit addresses the following
problems:
PROBLEMS ADDRESSED IN ALPLAD04_070:
o LADRIVER Fixes:
1. LASTDRIVER crashes when it receives a run message in the
circuit stalled state.
2. 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.
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
o Infoserver boots very slowly.
PROBLEMS ADDRESSED IN ALPLAD01_070 KIT
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.
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 patch can be found at any of these sites:
Colorado Site
Georgia Site
Files on this server are as follows:
alplad04_070.README
alplad04_070.CHKSUM
alplad04_070.CVRLET_TXT
alplad04_070.a-dcx_axpexe
|
