OpenVMS VAXMTAA03_062 OpenVMS VAX V6.2 MTAAACP ECO Summary
TITLE: OpenVMS VAXMTAA03_062 OpenVMS VAX V6.2 MTAAACP ECO Summary
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 1999. All rights reserved.
Modification Date: 18-MAR-1999
Modification Type: Article Updated as VAXMOUN03_062 is Now Available
Modification Date: 02-DEC-1998
Modification Type: Updated Article to list the dependent ECO
VAXMOUN03_062 as unavailable until a later date.
Modification Date: 20-NOV-1998
Modification Type: New ECO Kit
OP/SYS: OpenVMS VAX
COMPONENT: MTAAACP MTAAACP.EXE
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: VAXMTAA03_062
ECO Kits Superseded by This ECO Kit: VAXMTAA02_062
VAXMTAA01_062
VAXMTAA02_061
ECO Kit Approximate Size: 162 Blocks
Kit Applies To: OpenVMS VAX V6.2
System/Cluster Reboot Necessary: No
Installation Rating: INSTALL_3
3 - To be installed on all systems running
the listed versions of OpenVMS which
are experiencing the problems described.
KIT DEPENDENCIES:
The following remedial kit(s) must be installed BEFORE
installation of this, or any required kit:
VAXY2K02_062
In order to receive all the corrections listed in this kit,
the following remedial kits should also be installed:
VAXSYSA02_062
VAXBACK03_062
VAXMOUN03_062
VAXDISM02_062
VAXINIT01_062
ECO KIT SUMMARY:
An ECO kit exists for MTAAACP on OpenVMS VAX 6.2. This kit addresses
the following problems:
Problems addressed in the VAXMTAA03_062 kit:
o A possible system crash occurs during Host Based RAID Unbinds
with MME code enabled. A mailbox read synchronization problem
causes the crash.
This problem only occurs when a host-based RAID UNBIND command
is done while an MME-based application is running.
This problem can occur in several different code areas of the
operating system. In order to eliminate all known instances of
this problem, the following remedial kits (or their
supersedants) will also need to be installed:
VAXSYSA02_062
VAXBACK03_062
VAXMOUN03_062
VAXINIT01_062
VAXDISM02_062
o A process using MME could potentially "miss" the VOL1 label on
a tape. Also, a process could "hang" trying to send a message
to the MME process.
Problems addressed in the VAXMTAA02_062 kit:
o This kit is a re-issue of the VAXMTAA01_062 kit with the
OpenVMS VAX V6.2 portion only. The V6.1 section of the
VAXMTAA01_062 kit will be superseded by a future Shadowing kit.
Problems addressed in the VAXMTAA01_062 kit for OpenVMS VAX V6.1, V6.2
o The system crashes with a NOBVPVCB bugcheck. The crash occurs
on the kernel stack with MTAAACP.EXE as the current image.
o The system crashes with an XQPERR while dismounting a MAD drive.
Problems addressed in the VAXMTAA01_062 kit for OpenVMS VAX V6.1
o If a tape is initialized with a non-blank accessibility field
and then mounted using /OVERRIDE=(ACCESSIBILITY), the tape
mounts but cannot be read or written to. The command format to
initialize the tape would be similar to:
INIT/LABEL=VOLUME_ACCESSIBILITY="+" tape: LABEL
In addition, the following OPCOM messages are generated and the
tape volume is automatically unloaded after an attempt to WRITE
or READ the tape volume:
%%%%%%%%%%% OPCOM 12-DEC-1994 12:57:23.53 %%%%%%%%%%% Message
from user USERXX on NODEXX non-blank accessibility field in
volume labels on SYS$DEVICE:
%%%%%%%%%%% OPCOM 12-DEC-1994 12:57:23.54 %%%%%%%%%%%
o If a user tried to kill the MTAAACP process or process that
emitted the QIO, MTAAACP would go into RWAST state and hang.
Problems addressed in the VAXMTAA01_061 kit for OpenVMS VAX V6.1:
o If the wrong volume is inserted as the next volume, MTAAACP
cancels the request and then hangs.
INSTALLATION NOTES:
The system does not need to be rebooted after this kit is installed.
However, if you have other nodes in your OpenVMS VAXcluster, they
should be rebooted or you should install this kit on each system in
order to make use of the new image(s).
This patch can be found at any of these sites:
Colorado Site
Georgia Site
Files on this server are as follows:
vaxmtaa03_062.README
vaxmtaa03_062.CHKSUM
vaxmtaa03_062.CVRLET_TXT
vaxmtaa03_062.a-dcx_vaxexe
|
