OpenVMS ALPCLUSIO01_062 Alpha V6.2 VMScluster/MOUNT/Shadow ECO Summary
TITLE: OpenVMS ALPCLUSIO01_062 Alpha V6.2 VMScluster/MOUNT/Shadow ECO Summary
Modification Date: 02-AUG-1999
Modification Type: DOCUMENTATION: Technical Modification:
Added note regarding cosmetic error.
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 1997, 1999. All rights reserved.
REBOOT WARNING: When this kit is installed, the system *MUST* be
rebooted before any other ECO kit is installed. If
the reboot is not performed, the system will lose
functionality.
WARNING: Any customer with MTI StingRay 2 controllers should check
with MTI to see if their current version of firmware will
support CLUSIO or OpenVMS V7.1. This is *NOT* a problem
with OpenVMS V7.1.
WORKAROUND FOR COSMETIC ERROR INTRODUCED BY THIS KIT:
PROBLEM STATEMENT:
This kit fails to replace image LBRSHR.EXE in
SYS$COMMON:[SYSLIB]IMAGELIB.OLB.
PROBLEM SYMPTOM:
If you try to link against a routine in the LBRSHR image, the
following informational message can occur:
%LINK-I-DATMISMCH, creation date of d2-mmm-yyyy hh:mm in
shareable image
SYS$COMMON:[SYSLIB]LBRSHR.EXE;2 differs from date of
d1-mmm-yyyy hh:mm in Shareable image library
SYS$COMMON:[SYSLIB]IMAGELIB.OLB;2
The date d2-mmm-yyyy reflects the LBRSHR image left by the Y2K
ECO kit, while the d1-mmm-yyyy date reflects the date when
LBRSHR was last replaced in the library.
SOLUTION:
Execute the following DCL command to avoid getting the informational
message:
$ LIBRARY/REPLACE SYS$COMMON:[SYSLIB]IMAGELIB.OLB -
_$ SYS$COMMON:[SYSLIB]LBRSHR.EXE
CAUTIONS: To all OpenVMS Volume Shadowing Customers
1. The Volume Shadowing software which was shipped in
OpenVMS Alpha and VAX V7.1 requires additional
non-paged pool to improve synchronization. It uses
approximately 800 bytes of additional non-paged pool
per concurrent IO to the virtual unit. Customers
should take this into account when they are tuning
their systems, and be aware that Volume Shadowing is
now more sensitive to resource problems with the
possibility that systems may crash if non-paged pool
is exhausted.
2. Please note that this version of the software was also
back-ported to OpenVMS V6.2, and is available on the
V7.1 media in the V6.2 Compatibility (COMPAT) save sets.
OpenVMS Engineering recommends that V6.2 customers
install the TIMA versions of these Compatibility kits,
ALPCLUSIO01_062 and VAXCLUSIO01_062 and tune their
systems appropriately for non-paged pool expansion.
CAUTIONS: To all RAID Software Users:
RAID Software for OpenVMS, V2.3 (Host-based Raid) and earlier versions
do not work correctly with the following:
o OpenVMS V7.1
o OpenVMS V6.2 Cluster Compatibility kit on V7.1 media
SOLUTION:
In order to use RAID Software on either OpenVMS V7.1 or the V6.2
Compatibility Kit, the following kits must be installed:
OpenVMS V7.1 OpenVMS V6.2 Cluster
Compatibility Kit
----------------------------- -----------------------------
o RAID Software V2.4 or higher o RAID Software V2.4 or higher
o ECO kit SHAD01_V71 or higher o ECO kit CLUSIO01_062 or higher
WRITEBOOT NOTE:
There have been several reports that after installing this kit on
just one node of a cluster and rebooting, disks can no longer
be mounted from that node.
The workaround is to install this kit on all nodes in the cluster OR
remove the kit, run WRITEBOOT, and reboot.
REGRESSION NOTE: OpenVMS Engineering has discovered that if this ECO
kit is installed on a system on which the ALPDRIV04_070
ECO has been installed, the following fix that was
contained in the ALPDRIV04_070 ECO kit will be lost:
o A problem exists with HSJ/HSD30, 40 and 50
controllers where, after an event that initiates
Mountverfication, a packet acknowledgment will fail
to complete. The controller will report that it is
making progress on the command, but will never
finish. This causes all IO to the affected devices
to hang.
OpenVMS Engineering has released the ALPDRIV11_062
kit which fixes this problem.
********** URGENT NOTE REGARDING SYSMSG.EXE CONFLICT **********
* *
* Due to a conflict between the SYSMSG.EXE files in the *
* ALPCLUSIO01_062 ECO Kit and the COBOLRTL024 Kit that has *
* been released by way of the Consolidated Distribution, *
* installation of the ALPCLUSIO01_062 ECO kit may fail with *
* the following error: *
* *
* 47) SYSMSG (new Image) *
* *
* This kit will NOT be installed. A regression in *
* the level of layered product functionality *
* in [sysmsg]sysmsg.exe would occur as a result *
* of applying an additional level of bugfixes. *
* *
* Existing bugfix/LP level for 1L/0B *
* The kit bugfix/LP level for NE/00 *
* *
* Please contact your Compaq ... for a new kit *
* *
* %VMSINSTAL-E-INSFAIL, The installation of ALPCLUSIO01_ V6.2 *
* has failed. *
* *
* The following explains how this conflict can be avoided so *
* that the ALPCLUSIO01_062 ECO Kit can be successfully *
* installed. *
* *
* If ALPCLUSIO01_062 is installed first, perform the following *
* steps: *
* *
* o Rename SYS$COMMON:[SYSMSG]SYSMSG.EXE to *
* SYS$COMMON:[SYSMSG]SYSMSG.EXE_HOLD *
* *
* o Install COBOLRTL024 *
* *
* o Rename SYS$COMMON:[SYSMSG]SYSMSG.EXE_HOLD *
* to SYS$COMMON:[SYSMSG]SYSMSG.EXE *
* *
* If COBOLRTL024 is installed first, an image conflict will *
* exist. In order to avoid the ALPCLUSIO01_062 installation *
* failure, the following solution can be used: *
* *
* o Rename SYS$COMMON:[SYSMSG]SYSMSG.EXE to *
* SYS$COMMON:[SYSMSG]SYSMSG.EXE_HOLD *
* *
* o Install ALPCLUSIO01_062 *
* *
* o *DO NOT* rename the SYSMSG.EXE_HOLD image back *
* to SYSMSG.EXE. The image in the ALPCLUSIO01_062 *
* kit is the most recent image and should be left *
* available to the system. *
* *
* This conflict will be addressed in a future release of COBOL.*
* *
*****************************************************************
PRODUCT: OpenVMS Alpha
COMPONENT: VMScluster
MOUNT
Volume Shadowing
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: ALPCLUSIO01_062
ECO Kits Superseded by This ECO Kit: See Note Below
ECO Kit Approximate Size: 17,082 Blocks
Kit Applies To: OpenVMS Alpha V6.2, V6.2-1H1, V6.2-1H2, V6.2-1H3
System/Cluster Reboot Necessary: Yes
Installation Rating: 2 - To be installed on all systems running
the listed version(s) of OpenVMS and
using the following feature(s):
+ Systems running the ALPCOMPAT_062
Compatibility Kit
+ Systems running OpenVMS V6.2 where
the included enhancements to SHADOW
and MOUNT are wanted
NOTES: In order to receive the full fixes listed in this kit,
the following remedial kits also need to be installed:
None
The ALPCLUSIO01_062 kit contains all the fixes included
in the following list of remedial kits. Once the
ALPCLUSIO01_062 kit is installed there will no longer
be a need to install the remedial kits on this list to
OpenVMS Apha V6.2* systems.
ALPBOOT05_062
ALPDISM01_062
ALPF11X03_070
ALPINIT01_070
ALPSYS06_062
ALPSYS03_062
ALPSYS02_062
ALPMOUN01_062
ALPMSCP01_070
ALPSHAD05_062
ALPDRIV04_070 (Please see Regression Note above.)
ALPSYS08_070
ECO KIT SUMMARY:
An ECO kit exists for several components on OpenVMS Alpha V6.2 through
V6.2-1H3.
Existing Problems Not Addressed in the ALPCLUSIO01_062 Kit:
o The following three MOUNT problems were discovered at a late
stage in the release of this kit. OpenVMS Engineering is
working on solutions to these problems which will be available
in a future MOUNT ECO kit.
If a user, either manually or by a command procedure, executes
one of the following errors, MOUNT may incorrectly add members
to existing shadow sets.
- A MOUNT/SHAD with an incorrect volume label will succeed
in adding the member to the shadow set, for example:
$ MOUNT/SYSTEM DSA1/SHAD=$4$DUA1 TST1
$! The shadow set DSA1 is now available with DUA1 as
$! the only member
$ MOUNT/SYSTEM DSA1/SHAD=$4$DUA5 TST5
$! The device $4$DUA5 is wrongly added as a full copy
$! target.
- Similarly, a MOUNT/SHAD with an incorrect volume label of
a shadow set that is MOUNTed elsewhere in the VMScluster
will succeed in adding the member to the set on the other
nodes in the VMScluster, but the MOUNT will fail on the
local node, for example:
NODE_1> $ MOUNT/SYSTEM DSA1/SHAD=$4$DUA1 TST1
NODE_1> $ ! The shadow set DSA1 is now available on NODE_1
NODE_2> $ MOUNT/SYSTEM DSA1/SHAD=$4$DUA5 TST5
NODE_2> $ ! The MOUNT correctly fails on NODE_2 with an
$ ! INCVOLLABEL error
NODE_1> $ ! However, the member $4$DUA5 is incorrectly added
NODE_1> $ ! to the set DSA1 as a full copy target.
- MOUNT will incorrectly allow a non-shareable MOUNT/SHADOW of a
disk that is already mounted on another node as "shareable" to
succeed. As a result, corruption of the disk(s) will occur,
for example:
NODE_1> $ MOUNT/SYSTEM DSA1/SHAD=$4$DUA1 TST1
NODE_1> $ ! The shadowset DSA1 is now available on NODE_1
NODE_2> $ MOUNT /NOSHARE DSA5/SHAD=$4$DUA1 TST1
NODE_2> $ ! The shadowset DSA5 is now incorrectly available
$ ! on NODE_2
NODE_1> $ ! The shadowset DSA1 is also available on NODE_1
Corruption of the disk will occur when write operations are
performed by either node.
Problems Addressed in the ALPCLUSIO01_062 ECO Kit:
o A SHADDETINCON BUGCHECK may occur in SHD_THREADS when an
attempt is made to terminate a thread that is still a
Significant Event.
o The Volume Shadowing driver delivered in OpenVMS V7.1 and
the V6.2 Cluster Compatibility kit (ALPCOMPAT_062) does not
contain the full solution for the 'Bad Block Repair' (BBR)
problem. As a result, a disk may not be expelled from a
shadow set when necessary.
o An incompatibility exists between the StorageWorks Host
Based RAID Software and the enhanced volume shadowing
provided in both OpenVMS 7.1 and in the Cluster Compatibility
Kit (ALPCOMPAT_62). Because of this incompatibility, RAID
software can no longer detect that a shadow set state change
has occurred.
o Write protecting a shadow set member which is being added to
an existing shadowset causes the virtual unit to hang.
o A system may crash with an INVEXCEPTN bugcheck in SHSB$SEND_MESSAGE
because the UCB address in R5 is zero. It may also crash in
IOC_STD$CVT_DEVNAM in IO_ROUTINES when an attempt is made to get
a DDB out of a UCB that is corrupt.
The problem occurs when the IRP$L_ARB field is not correctly set
up with the clone error index. In the SH$VP_DEV_DRVERR routine,
this byte is used as an index to fetch the longword UCB of the
erring device which is set to FF and is incorrect.
The bad value occurs when volume processing begins to initiate
mount verification after a device error occurs.
o A shadowset may hang in mountverify for an extended period of
time after it encounters a DRAB_INT controller failure on an
HSJ50 which is followed by many 'forced error flagged in last
sector read' error messages on multiple shadowset member disks.
o Cluster Compatibility Kit Functionality
+ The ALPCLUSIO01_062 remedial kit includes the functionality
shipped with the ALPCOMPAT_062 Cluster Compatibilty Kit. The
OpenVMS Cluster Compatibility Kit provides many OpenVMS
Version 7.1 enhancements for Version 6.2 systems. This kit
is required for Version 6.2 systems if they are included in
a VMScluster with Version 7.1 systems (same system architecture
or a mix of VAX and Alpha systems). Optionally, users can
install it on other OpenVMS Version 6.2 systems to derive the
same benefits.
Cluster Compatibility Kit Features:
- OpenVMS Version 7.1 Volume Shadowing enhancements
The volume shadowing enhancements include significant
quality improvements and an increase in supported shadow
set members from 400 to 500. Note that the Version 7.1
volume shadowing system disk minimerge feature is not
included in the Cluster Compatibility Kit nor is the
Dump file off the system disk for OpenVMS Alpha. (The
Dump file off the system disk has been available for
OpenVMS VAX systems since Version 6.2.)
_______________________ Note _______________________________
If you use volume shadowing, be sure to read the volume
shadowing release notes.
____________________________________________________________
- OpenVMS Version 7.1 Mount Enhancements
The Mount utility has been completely rewritten, resulting
in a faster, more robust utility.
- Correction to an OpenVMS Version 6.2 Lock Manager problem
The Lock Manager changes correct a problem in OpenVMS
Version 6.2 that could corrupt some internal states in
lock information used by fork lock routines, notably the
I/O cache subsystem. This problem was corrected in OpenVMS
Version 7.0, and also in the limited hardware releases for
OpenVMS Alpha Version 6.2-1H2 and Version 6.2-1H3.
- Limited support for new port allocation classes for SCSI
Devices
Port allocation classes are a new naming option for SCSI
devices on systems running OpenVMS Alpha Version 7.1. If
you have installed the Cluster Compatibility Kit (on a VAX
or Alpha system ), you can access SCSI disks on an OpenVMS
Alpha Version 7.1 system that use port allocation classes
in their names, but you cannot name SCSI disks on a Version
6.2 system with port allocation classes.
- Snapshot Facility Disabled
Installing the Cluster Compatibility Kit on a Version 6.2
system disables the Snapshot facility, which has been
removed from OpenVMS VAX Version 7.1.
- System Dump Analyzer Utility (SDA)
A special version of the OpenVMS Version 6.2 System Dump
Analyzer (SDA) utility is included in the Cluster
Compatibility Kit. It recognizes the new volume shadowing
data structures.
When you install the Cluster Compatibility Kit, the
existing OpenVMS Version 6.2 SDA is renamed SDA_OLD.EXE
and the Cluster Compatibility Kit version is named
SDA.EXE. Use SDA_OLD.EXE to analyze crash dumps from
OpenVMS Version 6.2 systems on which the Cluster
Compatibility Kit has not been installed. Use SDA.EXE
to analyze crash dumps from OpenVMS Version 6.2 systems
on which the Cluster Compatibility Kit has been installed.
INSTALLATION NOTES:
In order for the corrections in this kit to take effect, the system must
be rebooted. If the system is a member of a VMScluster, the entire
cluster should be rebooted.
This patch can be found at any of these sites:
Colorado Site
Georgia Site
Files on this server are as follows:
alpclusio01_062.README
alpclusio01_062.CHKSUM
alpclusio01_062.CVRLET_TXT
alpclusio01_062.a-dcx_axpexe
alpclusio01_062.CVRLET_TXT
|
