****************************
ECO SUMMARY INFORMATION
****************************
Kit Name: VAXDRIV03_073.A
Kit Applies To: OpenVMS VAX V7.3
Approximate Kit Size: 645 blocks
Installation Rating: INSTALL_1
Reboot Required: Yes - rolling reboot
Superseded Kits: VAXDRIV02_073
Mandatory Kit Dependencies: None
Optional Kit Dependencies: None
VAXDRIV03_073.A-DCX_VAXEXE Checksum: 1810687363
=======================================================================
Hewlett-Packard OpenVMS ECO Cover Letter
=======================================================================
ECO NUMBER: VAXDRIV03_073
PRODUCT: OpenVMS VAX OPERATING SYSTEM V7.3
UPDATE PRODUCT: OpenVMS VAX OPERATING SYSTEM V7.3
1 KIT NAME:
VAXDRIV03_073
2 KIT DESCRIPTION:
2.1 Installation Rating:
INSTALL_1 : To be installed by all customers.
This installation rating, based upon current CLD information, is
provided to serve as a guide to which customers should apply this
remedial kit. (Reference attached Disclaimer of Warranty and
Limitation of Liability Statement)
2.2 Reboot Requirement:
Reboot Required. HP strongly recommends that a reboot is performed
immediately after kit installation to avoid system instability.
If you have other nodes in your OpenVMS cluster, they must also be
rebooted in order to make use of the new image(s). If it is not
possible or convenient to reboot the entire cluster at this time, a
rolling re-boot may be performed.
2.3 Version(s) of OpenVMS to which this kit may be applied:
OpenVMS VAX V7.3
2.4 New functionality or new hardware support provided:
No.
3 KITS SUPERSEDED BY THIS KIT:
- VAXDRIV02_073
4 KIT DEPENDENCIES:
4.1 The following remedial kit(s), or later, must be installed
BEFORE installation of this, or any required kit:
- None
Page 2
4.2 In order to receive all the corrections listed in this kit,
the following remedial kits, or later, should also be
installed:
- None
5 FILES PATCHED OR REPLACED:
o [SYS$LDR]DUDRIVER.EXE (new image)
Image Identification Information
image name: "DUDRIVER"
image file identification: "X-115"
link date/time: 11-JUL-2003 16:03:57.3
linker identification: "V11-38"
Overall Image Checksum: 680FB088
o [SYS$LDR]PEDRIVER.EXE (new image)
Image Identification Information
image name: "PEDRIVER"
image file identification: "VMS-17"
link date/time: 11-JUL-2003 16:04:09.73
linker identification: "V11-38"
Overall Image Checksum: 1F954C2B
o [SYS$LDR]PKBDRIVER.EXE (new image)
Image Identification Information
image name: "PKBDRIVER"
image file identification: "X-45"
link date/time: 11-JUL-2003 16:04:30.06
linker identification: "V11-38"
Overall Image Checksum: 9C282258
o [SYS$LDR]PKCDRIVER.EXE (new image)
Image Identification Information
image name: "PKCDRIVER"
image file identification: "X-45"
link date/time: 11-JUL-2003 16:04:27.89
linker identification: "V11-38"
Overall Image Checksum: 9D8353D3
o [SYS$LDR]PKRDRIVER.EXE (new image)
Image Identification Information
image name: "PKRDRIVER"
Page 3
image file identification: "X-45"
link date/time: 11-JUL-2003 16:04:29.07
linker identification: "V11-38"
Overall Image Checksum: 9423D0DA
o [SYS$LDR]SCACP.EXE (new image)
Image Identification Information
image name: "SCACP"
image file identification: "X-13"
link date/time: 29-MAR-2002 21:39:31.28
linker identification: "V11-38"
Overall Image Checksum: 6C0AA89A
o [SYS$LDR]TUDRIVER.EXE (new image)
Image Identification Information
image name: "TUDRIVER"
image file identification: "X-81"
link date/time: 11-JUL-2003 16:04:00.78
linker identification: "V11-38"
Overall Image Checksum: 8796784D
o [SYSEXE]PEDRIVER.STB (new image)
6 PROBLEMS ADDRESSED IN THIS KIT
6.1 New problems addressed in the VAXDRIV03_073 kit
6.1.1 SYS$SYSTEM:SCACP.EXE image not installed
6.1.1.1 Problem Description:
The SYS$SYSTEM:SCACP.EXE image is not properly installed
by the VAXDRIV02_073 ECO kit.
Images Affected:
- [SYSEXE]SCACP.EXE
6.1.1.2 CLDs, and QARs reporting this problem:
6.1.1.3 CLD(s)
70-3-7602,CFS.104390
Page 4
6.1.1.4 QAR(s)
None.
6.1.1.5 Problem Analysis:
SCACP VUI file was not provided in the kit.
6.1.1.6 Work-arounds:
None.
6.2 New problems addressed in the VAXDRIV02_073 kit
6.2.1 DGA device identified as snapshot device
6.2.1.1 Problem Description:
The output of SHOW DEV/FULL for a DGA device
identifies the device as a snapshot device. With
this fix the device is properly identified as an
HSG80 device.
Images Affected:
- [SYS$LDR]DUDRIVER.EXE
6.2.1.2 CLDs, and QARs reporting this problem:
6.2.1.3 CLD(s)
None.
6.2.1.4 QAR(s)
75-45-359
6.2.1.5 Problem Analysis:
A new entry to the MEDIA_ID to Device Type
Conversion Table was needed. Implementing this
change makes the table entry compatible with the one
which currently exists for Alpha
Page 5
6.2.1.6 Work-arounds:
None.
6.2.2 Maningless error message when mounting or
initializing a tapeunit
6.2.2.1 Problem Description:
When mounting or initializing a tapeunit with a
density that the unit can not handle, a misleading
error message is generated. For example:
$ mount/for/den=800 $1$MUA7: test
%MOUNT-F-BUGCHECK, internal consistency failure
This error does not indicate to the user issuing the
command what the problem is.
Images Affected:
- [SYS$LDR]TUDRIVER.EXE
6.2.2.2 CLDs, and QARs reporting this problem:
6.2.2.3 CLD(s)
None.
6.2.2.4 QAR(s)
75-45-1967
6.2.2.5 Problem Analysis:
This is a sort of 'catch all' error message returned
by TUDRIVER when a setmode command is rejected by
the controller receiving the command. Rather than
use SS$_IVDENS, the SS$_DRVERR error status will be
used. SS$_IVDENS should not be returned as there
may be more causes for the error.
6.2.2.6 Work-arounds:
None.
Page 6
6.2.3 I/O's to a device hang after an error condition
occurs.
6.2.3.1 Problem Description:
I/O's to a device hang after an error condition
occurs. A forced crash must be issued.
Images Affected:
- [SYS$LDR]PKBDRIVER.EXE
- [SYS$LDR]PKCDRIVER.EXE
- [SYS$LDR]PKRDRIVER.EXE
6.2.3.2 CLDs, and QARs reporting this problem:
6.2.3.3 CLD(s)
CFS.85039
6.2.3.4 QAR(s)
None.
6.2.3.5 Problem Analysis:
When an error condition occurs, the QUEUE_FROZEN bit
is set. If any SCDRPs timeout before the error
condition is resolved, those SCDRPs are given more
time to complete. When the SCDRPs are timed out,
the DSCN bit is cleared and the TMODSCN bit is set
in the SCDRP's CNX_STS. When the SCDRPs are given
more time, as a result of the QUEUE_FROZEN bit being
set, the TMODSCN bit is cleared and the DSCN bit is
set in the SCDT$L_STS.
Because the TMODSCN bit is still set for these
SCDRPs in the SCDRP's CNX_STS, the time out code
ignores these SCDRPs forever. Because the
QUEUE_FROZEN bit is set in the SCDT, no further
I/O's are queued to this connection and the system
hangs until a forced crash is issued.
6.2.3.6 Work-arounds:
None.
Page 7
6.2.4 System hang or crash after tapeunit failover
6.2.4.1 Problem Description:
The system may hang after a tapeunit fails over to a
second controller. Another symptom may be a
CPUSPINWAIT crash on an SMP system. The hang occurs
at routine DUTU$MOVE_IODB when the code attempts to
follow a chain of UCB's via the field
UCB$L_CDDB_LINK, while the field points to the UCB
itself. Normally the last field in the chain of
UCB's should be zero.
Crashdump Summary Information:
------------------------------
Bugcheck Type: CPUSPINWAIT, CPU spinwait
timer expired
Failing PC: FFFFFFFF.8007A384 SMP$TIMEOUT_C+00064
Failing PS: 28000000.00000804
Module: SYSTEM_SYNCHRONIZATION
(Link Date/Time: 28-MAY-1999 23:39:
Offset: 00000384
Stack Pointers:
KSP = FFFFFFFF.F5D33E28 ESP = FFFFFFFF.F5D35000
SSP = FFFFFFFF.F5D31000 USP = FFFFFFFF.F5D31000
Failing Instruction:
SMP$TIMEOUT_C+00064: BUGCHK
Images Affected:
- [SYS$LDR]DUDRIVER.EXE
- [SYS$LDR]TUDRIVER.EXE
6.2.4.2 CLDs, and QARs reporting this problem:
6.2.4.3 CLD(s)
CFS.71855, CFS.77429, CFS.86456, CFS.89658,
CFS.90050
6.2.4.4 QAR(s)
None.
Page 8
6.2.4.5 Problem Analysis:
UTU$LINK_UCB2CDDB can, under certain circumstances,
be called to link a UCB into the CDDB's chain when
that UCB is already in the chain. The way it is
currently handled causes the chain to be corrupted,
i.e. when finished, UCB$L_CDDB_LINK will point to
the UCB itself causing problems later on.
6.2.4.6 Work-arounds:
None.
6.2.5 System can crash, during boot, with an INVEXCEPTN
bugcheck at $RELEASEL+00011 from pkcdriver+04858.
6.2.5.1 Problem Description:
If the system parameter MULTIPROCESSING is set to 2,
the system can crash, during boot, with an
INVEXCEPTN bugcheck at $RELEASEL+00011 from
pkcdriver+04858.
Images Affected:
- [SYS$LDR]PKBDRIVER.EXE
- [SYS$LDR]PKCDRIVER.EXE
- [SYS$LDR]PKRDRIVER.EXE
6.2.5.2 CLDs, and QARs reporting this problem:
6.2.5.3 CLD(s)
CFS.94500
6.2.5.4 QAR(s)
None.
6.2.5.5 Problem Analysis:
A field was changed from scdrp to scdt without
adapting the register used as an index. Thus a bit
was set in the wrong data structure.
Page 9
6.2.5.6 Work-arounds:
None.
6.2.6 Access to certain drives can hang, SHADDETINCON
bugcheck.
6.2.6.1 Problem Description:
o Upon a connection failure, access to certain
drives can hang, with an IRP to DUDRIVER never
being returned to an application. This hang can
spread from a single process to systemwide as
other processes back up behind lock requests.
Investigation shows the process' IRP is not
found in the usual places in DUDRIVER (CDDB
active queue, restart queue, UCB pending queue
etc.). In other words it is "lost".
o If Shadowing is involved on a hung drive, the
system will crash with a SHADDETINCON bugcheck.
Investigation shows an I/O (IRP) has been
pending for MVTIMEOUT seconds (1 hour) and the
shadowing IRP is "lost", as described above.
Images Affected:
- [SYS$LDR]DUDRIVER.EXE
- [SYS$LDR]TUDRIVER.EXE
6.2.6.2 CLDs, and QARs reporting this problem:
6.2.6.3 CLD(s)
CFS.92106, CFS.95877
6.2.6.4 QAR(s)
None.
6.2.6.5 Problem Analysis:
See Problem Description.
Page 10
6.2.6.6 Work-arounds:
None.
6.2.7 System can crash with an INVEXCEPN bugcheck at
DUDRIVER+3F07
6.2.7.1 Problem Description:
The system can crash with an INVEXCEPN bugcheck at
DUDRIVER+3F07, MOVL 14(R4),R4 with R4=0.
Images Affected:
- [SYS$LDR]DUDRIVER.EXE
- [SYS$LDR]TUDRIVER.EXE
6.2.7.2 CLDs, and QARs reporting this problem:
6.2.7.3 CLD(s)
CFS.98583
6.2.7.4 QAR(s)
None.
6.2.7.5 Problem Analysis:
See problem Description.
6.2.7.6 Work-arounds:
None.
6.2.8 Possible Data Corruption
6.2.8.1 Problem Description:
Extreme stress testing with fault insertion in a
laboratory environment has indicated that there is a
very small window in the cluster disk driver,
(DUDRIVER.EXE) that could result in undetected data
corruption under very remote circumstances. In order
for this problem to occur, all of the following
criteria must be met:
Page 11
o The system must be in a cluster.
o The system must have multiple cluster
interconnects.
o The system must have multiple CPUs.
o There must be a failure on the current
connection while I/O is outstanding
o A new connection must be formed before the I/O
completes.
It is possible that this problem could occur but has
never been seen on VAX systems. The code is also
common to TUDRIVER (the cluster tape driver) but the
failover characteristics of cluster tapes make the
problem even less likely to occur there.
Images Affected:
- [SYS$LDR]DUDRIVER.EXE
- [SYS$LDR]TUDRIVER.EXE
6.2.8.2 CLDs, and QARs reporting this problem:
6.2.8.3 CLD(s)
None.
6.2.8.4 QAR(s)
75-83-892
6.2.8.5 Problem Analysis:
See problem Description.
6.2.8.6 Work-arounds:
None.
7 PROBLEMS ADDRESSED IN VAXDRIV01_073 KIT
o SCACP erroneously returns a "managed object handle
invalid" error status. This results in an inability
to issue SCACP commands on some systems. Also, on
some systems (random), SCACP returns an error status
Page 12
on every command.
Images Affected:
- [SYS$LDR]PEDRIVER.EXE
- [SYSEXE]SCACP.EXE
- [SYSEXE]PEDRIVER.STB
o The error status given to SCACP is not displayed.
Images Affected:
- [SYS$LDR]PEDRIVER.EXE
- [SYSEXE]SCACP.EXE
- [SYSEXE]PEDRIVER.STB
o SET, STOP, START, SHOW commands default to wildcard *
if no device, channel, or VC name is specified. Only
SHOW should default in such a manner. SET, STOP and
START should require explicit specification of the
names or an * if all are requested. four error
messages have been added:
o NODEVGIVEN - No devices specified (default to
wildcard only on SHOW)
o NOCHANGIVEN - No channels specified (default to
wildcard only on SHOW)
o NOVCGIVEN - No VCs specified (default to wildcard
only on SHOW)
o OBJ_HANDLE_INV - Managed object handle invalid
Images Affected:
- [SYS$LDR]PEDRIVER.EXE
- [SYSEXE]SCACP.EXE
- [SYSEXE]PEDRIVER.STB
o The /OUTPUT qualifier does not process the supplied
file name correctly. This results in an output file
being created with the wrong name, generally the
specified name with some extra characters.
Page 13
Images Affected:
- [SYSEXE]SCACP.EXE
8 INSTALLATION INSTRUCTIONS:
8.1 Installation Command
Install this kit with the VMSINSTAL utility by logging into
the SYSTEM account, and typing the following at the DCL
prompt:
@SYS$UPDATE:VMSINSTAL VAXDRIV03_073 [location of the saveset]
The saveset location may be a tape drive, CD, or a disk
directory that contains the kit saveset.
9 COPYRIGHT AND DISCLAIMER:
(C) Copyright 2003 Hewlett-Packard Development Company, L.P.
Confidential computer software. Valid license from HP and/or
its subsidiaries required for possession, use, or copying.
Consistent with FAR 12.211 and 12.212, Commercial Computer
Software, Computer Software Documentation, and Technical Data
for Commercial Items are licensed to the U.S. Government
under vendor's standard commercial license.
Neither HP nor any of its subsidiaries shall be liable for
technical or editorial errors or omissions contained herein.
The information in this document is provided "as is" without
warranty of any kind and is subject to change without notice.
The warranties for HP products are set forth in the express
limited warranty statements accompanying such products.
Nothing herein should be construed as constituting an
additional warranty.
DISCLAIMER OF WARRANTY AND LIMITATION OF LIABILITY
THIS PATCH IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND.
ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND
WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY,
FITNESS FOR PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE
HEREBY EXCLUDED TO THE EXTENT PERMITTED BY APPLICABLE LAW. IN
NO EVENT WILL COMPAQ BE LIABLE FOR ANY LOST REVENUE OR PROFIT,
OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR
PUNITIVE DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY
OF LIABILITY, WITH RESPECT TO ANY PATCH MADE AVAILABLE HERE OR
TO THE USE OF SUCH PATCH.