OpenVMS VMS73_DRIVER-V0300 Alpha V7.3 Drivers ECO Summary
TITLE: OpenVMS VMS73_DRIVER-V0300 Alpha V7.3 Drivers ECO Summary
NOTE: An OpenVMS saveset or PCSI installation file is stored
on the Internet in a self-expanding compressed file.
For OpenVMS savesets, the name of the compressed saveset
file will be kit_name.a-dcx_vaxexe for OpenVMS VAX or
kit_name.a-dcx_axpexe for OpenVMS Alpha. Once the OpenVMS
saveset is copied to your system, expand the compressed
saveset by typing RUN kitname.dcx_vaxexe or kitname.dcx_alpexe.
For PCSI files, once the PCSI file is copied to your system,
rename the PCSI file to kitname.pcsi-dcx_axpexe or
kitname.pcsi-dcx_vaxexe, then it can be expanded by typing
RUN kitname.pcsi-dcx_axpexe or kitname.pcsi-dcx_vaxexe. The
resultant file will be the PCSI installation file which can be
used to install the ECO.
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
SOURCE: Compaq Computer Corporation
ECO Kit Name: VMS73_DRIVER-V0300
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.
The following remedial kit(s), or later, must be installed BEFORE
installation of this, or any required kit:
In order to receive all the corrections listed in this
kit, the following remedial kits, or later, should also be
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.
o An ACCVIO occurs when using the PREFER.MAR routine with a
$ PREFER $1$DUA15: /HOST=HSC000 /FORCE
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual
PC =0000000C, PSL=0000000F
If the command is executed without the /FORCE qualifier, no
$ PREFER $1$DUA15: /HOST=HSC000
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.
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:MAIN.RBF;
-SYSTEM-F-IVDENS, invalid density
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:[RUN]GEM.EXE
Failing PC: FFFFFFFF.80088384 SMP$TIMEOUT_C+00064
Failing PS: 18000000.00000803
(Link Date/Time:22-MAR-2001 01:01:40.01)
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.
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
75-66-1171, 75-66-1238, 75-66-1199, 75-66-1219,
This kit requires a system reboot. Compaq strongly recommends that
a reboot is performed immediately after kit installation to avoid
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.
Install this kit with the POLYCENTER Software installation utility
by logging into the SYSTEM account, and typing the following at the
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.
- 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
All trademarks are the property of their respective owners.
Files on this server are as follows: