|
|
 |
OpenVMS VAXLAD02_071 OpenVMS VAX V7.1 LAD Drivers ECO Summary
|
TITLE: OpenVMS VAXLAD02_071 OpenVMS VAX V7.1 LAD Drivers ECO Summary
Modification Date: 06-OCT-1999
Modification Type: Updated Kit: SupersedeS VAXLAD01_071
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) Compaq Computer Corporation 1998, 1999. 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: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: VAXLAD02_071
ECO Kits Superseded by This ECO Kit: VAXLAD01_071
ECO Kit Approximate Size: 396 Blocks
Kit Applies To: OpenVMS VAX V7.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 V7.1. This kit addresses the
following problems:
Problems Addressed in VAXLAD02_071 Kit:
o In a multi-processor environment, the service solicitation
queues may be accessed by several processors. Since these
queues are not synchronized correctly, they can get corrupted.
Thus, the system crashes with an INVEXCEPTN at around
LASTDRIVER+3513 in routine LAST$TICK.
Note:
LAST should not be started on non-connected Ethernet
controllers. Otherwise, problems with the LADCP> SHOW
SERVICE command can occur.
Image(s) Affected: [SYS$LDR]ESS$LASTDRIVER.EXE
o If a tape is initialized on a TZ87 and then put on a TZ86 with
an attempt to re-initialize the tape, the TZ86 takes an
excessive amount of time to determine how to handle the tape.
Hence, it times out.
Image(s) Affected: [SYS$LDR]ESS$MADDRIVER.EXE
o System crashes can occur when an attempt is made to create a
directory or write a file to a large InfoServer partition.
Image(s) Affected: [SYS$LDR]ESS$DADDRIVER.EXE
Problems Addressed in VAXLAD01_071:
o The system crashes in LTDRIVER when SSB is deleted prematurely
while an UNLOAD is in progress.
o LASTDRIVER crashes when it receives a run message in circuit
stalled state.
o The LASTDRIVER image crashes when it receives an Advertisement
(ADV) or Solicit (SOL) message with a negative message length.
o An overrun error on magtape occurs if the record size is
greater than 65024.
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
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.
All trademarks are the property of their respective owners.
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: VAXLAD01_071
ECO Kits Superseded by This ECO Kit: None
ECO Kit Approximate Size: 406 Blocks
Saveset A - 396 Blocks
Kit Applies To: OpenVMS VAX V7.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 V7.1. This kit addresses the following problems:
PROBLEMS ADDRESSED IN VAXLAD01_071 KIT:
o The system crashes in LTDRIVER when SSB is deleted prematurely
while an UNLOAD is in progress.
o LASTDRIVER crashes when it receives a run message in circuit
stalled state.
o The LASTDRIVER image crashes when it receives an Advertisement
(ADV) or Solicit (SOL) message with a negative message length.
o An overrun error on magtape occurs if the record size is
greater then 65024.
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
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.
|
Files on this server are as follows:
|
»vaxlad02_071.README
»vaxlad02_071.CHKSUM
»vaxlad02_071.CVRLET_TXT
»vaxlad02_071.a-dcx_vaxexe
»vaxlad02_071.CVRLET_TXT
|
