OpenVMS VMS731_CLUSTER-V0100 Alpha V7.3-1 CLUSTER ECO Summary
TITLE: OpenVMS VMS731_CLUSTER-V0100 Alpha V7.3-1 CLUSTER 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: 02-MAY-2003
Modification Date: Not Applicable
Modification Type: NEW KIT
Copyright (c) Hewlett-Packard Company 2002,2003. All rights reserved.
OP/SYS: OpenVMS Alpha
SOURCE: Hewlett-Packard Company
ECO Kit Name: VMS731_CLUSTER-V0100
ECO Kits Superseded by This ECO Kit: None
ECO Kit Approximate Size: 352 Blocks
Kit Applies To: OpenVMS Alpha V7.3-1
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 installed:
ECO KIT SUMMARY:
An ECO kit exists for CLUSTER on OpenVMS Alpha V7.3-1. This kit addresses the
PROBLEMS ADDRESSED IN VMS731_CLUSTER-V0100 KIT
o Since V7.2, a MSCP_SERVE_ALL value of 4 has not worked
correctly. It is supposed to serve only the system disk, but
it does not serve any disks. All other values of
MSCP_SERVE_ALL work correctly.
This change insures that you can MSCP serve *just* the system
disk, as is documented with MSCP_SERVE_ALL = 4.
o When updating from OpenVMS V7.3R to V7.3-1R it is possible for
the LANACP process to get an ACCVIO followed by a PROCGONE
bugcheck as the LANACP process attempts to terminate and run
down. This will cause the upgrade procedure to terminate
prematurely during the reboot.
o If an SCS data-transfer SCS$MAP request encounters an SCS
port-specific mapping resource exhaustion ("stall"), the
system will crash upon attempt to resume the SCS map
data-transfer setup operation, when such resources become
available and the stalled operation restarts.
While many VMS SCS port drivers use port-specific SCS mapping
resources (S/G-maps, CRCTX$, etc.), only SYS$PADRIVER for the
SHAC-DSSI-chip/KFESA has an unusually small quantity of SCS
mapping resources (128 CI buffer descriptors, to be exact).
It is therefore most likely to encounter this failure.
This kit requires a system reboot. HP 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 VMS731_CLUSTER /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
VMS731_CLUSTER kit would be:
$ DEFINE/SYS NO_ASK$BACKUP TRUE
$ DEFINE/SYS NO_ASK$REBOOT TRUE
$ PROD INSTALL VMS731_CLUSTER/PROD=DEC/BASE=AXPVMS/VER=V1.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: