Updated: 24-SEP-2003 (Use your browsers' Reload button to ensure you're viewing the most recent version)
VMS73_DRIVER-V0300 Alpha V7.3 Drivers ECO Summary
*OpenVMS] VMS73_DRIVER-V0300 Alpha V7.3 Drivers ECO Summary
New Kit Date: 18-OCT-2002
Modification Date: Not Applicable
Modification Type: NEW KIT
Copyright (c) Compaq Computer Corporation 2002. All rights reserved.
OP/SYS: OpenVMS Alpha
COMPONENT: Drivers
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: VMS73_DRIVER-V0300
DEC-AXPVMS-VMS73_DRIVER-V0300--4.PCSI
ECO Kits Superseded by This ECO Kit: VMS73_DRIVER-V0200
ECO Kit Approximate Size: 1872 Blocks
Kit Applies To: OpenVMS Alpha V7.3
System/Cluster Reboot Necessary: Yes
Rolling Re-boot Supported: Yes
Installation Rating: INSTALL_1
1 - To be installed by all customers.
Kit Dependencies:
The following remedial kit(s), or later, must be installed BEFORE
installation of this, or any required kit:
None
In order to receive all the corrections listed in this
kit, the following remedial kits, or later, should also be
installed:
VMS73_UPDATE-V0100
ECO KIT SUMMARY:
An ECO kit exists for drivers on OpenVMS Alpha V7.3. This kit
addresses the following problems:
PROBLEMS ADDRESSED IN VMS73_DRIVER-V0300 KIT
o When performing multi-volume Backup (and various other Backup
operations involving label processing) with generic SCSI
tapes, compaction status gets turned off.
Images Affected:[SYS$LDR]SYS$TUDRIVER.EXE
o An ACCVIO occurs when using the PREFER.MAR routine with a
/FORCE qualifier.
For example:
$ PREFER $1$DUA15: /HOST=HSC000 /FORCE
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual
address=0000000C,
PC =0000000C, PSL=0000000F
If the command is executed without the /FORCE qualifier, no
ACCVIO occurs:
$ PREFER $1$DUA15: /HOST=HSC000
Images Affected:[SYS$LDR]SYS$DUDRIVER.EXE
o Fix a couple of minor problems with the display of trace data.
(1) Channels specified in the SHOW/SET TRACE command are not saved
in the correct spot in the management command. The structure
used to copy them was CHACT$ when it should have been TRACEACT$.
(2) The output filename (for /OUT=file) was not initialized correctly,
in_file_name was being cleared instead of out_file_name.
Images Affected:[SYSEXE]SCACP.EXE
o A problem could occur when a multi volume backup was unable to
span multiple tapes. The following error message was seen:
%RMU-E-POSITERR, error positioning $3$MKA603:[000000]MAIN.RBF;
-SYSTEM-F-IVDENS, invalid density
Images Affected:[SYS$LDR]SYS$TUDRIVER.EXE
o The system may hang after a tapeunit did a failover to a
second controller. Another symptom may be a CPUSPINWAIT crash
on a SMP system. The hang occurs at routine DUTU$MOVE_IODB
when we attempt 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
Current Process: BATCH_1006249
Current Image: DSA1010:<GEMBASE56.>[RUN]GEM.EXE
Failing PC: FFFFFFFF.80088384 SMP$TIMEOUT_C+00064
Failing PS: 18000000.00000803
Module: SYSTEM_SYNCHRONIZATION_MIN
(Link Date/Time:22-MAR-2001 01:01:40.01)
Offset: 00000384
Images Affected:[SYS$LDR]SYS$TUDRIVER.EXE
[SYS$LDR]SYS$DUDRIVER.EXE
CFS.90879,CFS.90881
o SHOW CLUSTER and SDA SHOW CONNECTIONS can correctly report up
to 8 SMCI ports. The reason for this is that, PBDRIVER uses a
multiport scheme to handle its connections. In other words,
UCB unit numbers are coupled with the galaxy instance number,
making unit numbers greater than the standard ZERO as in
traditional SCS port drivers. SCS reports the port name in
the PB field PB$T_LPORT_NAME (format PBx0) which is only 4
bytes in length. In all cases, the unit number is set to
zero. This is incorrect for SMCI ports.
Images Affected:[SYS$LDR]SYS$PBDRIVER.EXE
o In routine DU$INSERT_RESTARTQ, certain CDRPS (MVIRP,
shadowing) were being posted with DEVOFFLINE instead of being
queued to the restart queue. Many of these CDRPs had mapping
registers active, and posting them unmapped them while still
active. This caused a variety of symptoms, such as
IOMACHINECHECKS, unrecognized SCA messages and INCONSTATE
errors.
Images Affected:[SYS$LDR]SYS$DUDRIVER.EXE
[SYS$LDR]SYS$TUDRIVER.EXE
75-66-1171, 75-66-1238, 75-66-1199, 75-66-1219,
75-66-1093
PROBLEMS ADDRESSED IN VMS73_DRIVER-V0200 KIT:
o When the CD-ROM is booted on an ES40, the following error
message is returned after the initial boot messages:
%SYSBOOT-I-GCTMINOR, GCT used with minor revision mismatch
expected 00000005.00000001 - seen: 00000005.00000002
%SYSBOOT-F-LDFAIL,unable to load SYS$BASE_IMAGE.EXE,status=00000054
halted CPU = 0
halt code = 5
HALT instruction executed
PC = 1d5e8
boot failure
Images Affected: [SYS$LDR]SYS$DQDRIVER.EXE
o When mounting an ATAPI device an ATA init_device_param command
attempts to set the disk geometry. This command is illegal
for ATAPI devices but it takes 15 seconds before the drive
reports the error.
Images Affected: [SYS$LDR]SYS$DQDRIVER.EXE
RELATED ARTICLES:
Detailed articles describing the problems listed above may exist in
the OPENVMS database(s). To view these articles, open the appropriate
product database and perform a query using either of the following
search strings: 'VMS73_DRIVER-V0300' or 'VMS73_DRIVER'.
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:
This kit requires a system reboot. Compaq 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.
INSTALLATION INSTRUCTIONS:
Install this kit with the POLYCENTER Software installation utility
by logging into the SYSTEM account, and typing the following at the
DCL prompt:
PRODUCT INSTALL VMS73_DRIVER /SOURCE=[location of Kit]
The kit location may be a tape drive, CD, or a disk directory that
contains the kit.
Additional help on installing PCSI kits can be found by typing
HELP PRODUCT INSTALL at the system prompt
Special Installation Instructions:
o Scripting of Answers to Installation Questions
During installation, this kit will ask and require user
response to several questions. If you wish to automate the
installation of this kit and avoid having to provide responses
to these questions, you must create a DCL command procedure
that includes the following definitions and commands:
- $ DEFINE/SYS NO_ASK$BACKUP TRUE
- $ DEFINE/SYS NO_ASK$REBOOT TRUE
- Add the following qualifiers to the PRODUCT INSTALL
command and add that command to the DCL procedure.
/PROD=DEC/BASE=AXPVMS/VER=V3.0
- De-assign the logicals assigned
For example, a sample command file to install the
VMS73_DRIVER-V0300 kit would be:
$
$ DEFINE/SYS NO_ASK$BACKUP TRUE
$ DEFINE/SYS NO_ASK$REBOOT TRUE
$!
$ PROD INSTALL VMS73_DRIVE/PROD=DEC/BASE=AXPVMS/VER=V3.0
$!
$ DEASSIGN/SYS NO_ASK$BACKUP
$ DEASSIGN/SYS NO_ASK$REBOOT
$!
$ exit
All trademarks are the property of their respective owners.
==========================================================================
| Table of Kit Image Information |
+----------------------------+----------+-----------------+--------------+
| | Overall | Image File | Image Link |
| Image Name | Checksum | Identification | Date/Time |
+----------------------------+----------+-----------------+--------------+
| SCACP.EXE | BD9813D5 | X-13 | 12-FEB-2002 |
| | | 09:21:00.17 |
+----------------------------+----------+-----------------+--------------+
| SYS$DQDRIVER.EXE | 7190F974 | X-26A1 | 28-JUN-2002 |
| | | 08:48:01.94 |
+----------------------------+----------+-----------------+--------------+
| SYS$DUDRIVER.EXE | 5D251DE3 | X-3 | 28-JUN-2002 |
| | | 08:39:15.58 |
+----------------------------+----------+-----------------+--------------+
| SYS$PBDRIVER.EXE | 915AB58D | X-28 | 28-JUN-2002 |
| | | 08:39:18.77 |
+----------------------------+----------+-----------------+--------------+
| SYS$PEDRIVER.EXE | E8BA4041 | X-3 | 28-JUN-2002 |
| | | 08:41:18.19 |
+----------------------------+----------+-----------------+--------------+
| SYS$PEDRIVER_MON.EXE | 07525502 | X-3 | 28-JUN-2002 |
| | | 08:41:48.43 |
+----------------------------+----------+-----------------+--------------+
| SYS$TUDRIVER.EXE | 7585805E | X-3 | 28-JUN-2002 |
| | | 08:46:05.09 |
+----------------------------+----------+-----------------+--------------+
|
