OpenVMS VAXLAD02_062 OpenVMS VAX V6.2 LAD Drivers ECO Summary
TITLE: OpenVMS VAXLAD02_062 OpenVMS VAX V6.2 LAD Drivers ECO Summary
Modification Date: 06-OCT-1999
Modification Type: Updated Kit: Supersedes VAXLAD01_062
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 (ESS$DRIVER.EXE)
LADDRIVER (ESS$LADDRIVER.EXE)
LASTDRIVER (ESS$LASTDRIVER.EXE)
MADDRIVER (ESS$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_062
ECO Kits Superseded by This ECO Kit: VAXLAD01_062
ECO Kit Approximate Size: 396 Blocks
Kit Applies To: OpenVMS VAX V6.2
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 ESS$DADDRIVER, ESS$LADDRIVER, ESS$LASTDRIVER,
and ESS$MADDRIVER on OpenVMS VAX V6.2. This kit addresses the
following problems:
Problems Addressed in VAXLAD02_062:
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 that LAST should
not be started on non-connected Ethernet controllers.
Otherwise, problems with the LADCP> SHOW SERVICE command
can occur.
This problem is corrected in OpenVMS VAX V7.2
Image(s) Affected: [SYS$LDR]SYS$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.
This problem is corrected in OpenVMS VAX V7.2
Image(s) Affected: [SYS$LDR]SYS$MADDRIVER.EXE
Problems Addressed in VAXLAD01_062:
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 LASTDRIVER crashes when it receives a run message in circuit
stalled.
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 cancelled.
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 than
the seed unit number. This problem can happen for both
DADDRIVER and MADDRIVER.
o When booting from a CD, the InfoServer client can't be started.
o InfoServer Client STOP/START bugs were fixed.
EAGLE QAR 168, EAGLE QAR 168, EAGLE QAR 63
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 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.
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_062
ECO Kits Superseded by This ECO Kit: None
ECO Kit Approximate Size: 409 Blocks
Saveset A - 396 Blocks
Kit Applies To: OpenVMS VAX V6.2
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.2. This kit addresses the following problems:
PROBLEMS ADDRESSED IN VAXLAD01_062 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 LASTDRIVER crashes when it receives a run message in circuit
stalled.
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 When booting from a CD, the InfoServer client can't be started.
o InfoServer Client STOP/START bugs were fixed.
EAGLE QAR 168, EAGLE QAR 168, EAGLE QAR 63
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 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.
This patch can be found at any of these sites:
Colorado Site
Georgia Site
Files on this server are as follows:
vaxlad02_062.README
vaxlad02_062.CHKSUM
vaxlad02_062.CVRLET_TXT
vaxlad02_062.a-dcx_vaxexe
vaxlad02_062.CVRLET_TXT
|
