Updated: 24-SEP-2003 (Use your browsers' Reload button to ensure you're viewing the most recent version)
VAXMSCP02_061 VAX V6.1 TMSCP ECO Summary
Copyright (c) Digital Equipment Corporation 1997. All rights reserved.
OP/SYS: OpenVMS VAX
COMPONENT: TMSCP.EXE
SOURCE: Digital Equipment Corporation
ECO INFORMATION:
ECO Kit Name: VAXMSCP02_061
ECO Kits Superseded by This ECO Kit: None
ECO Kit Approximate Size: 90 Blocks
Kit Applies To: OpenVMS VAX V6.1
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 that MSCP serve tapes and disks.
NOTE: In order to receive the full fixes listed in this kit,
the following remedial kits also need to be installed:
VAXSHAD09_061
ECO KIT SUMMARY:
An ECO kit exists for TMSCP on OpenVMS VAX V6.1. This kit addresses
the following problems:
o TMSCP does not restore R2 properly before using the register
as an MSCP message. This misuse manifests either in a
corrupted TMSCP$ERR_TBL which causes devices to be inaccessible,
or the system will crash. The outcome depends on the value in
R2.
o The client process hangs when it attempts to mount a tape device
that is online to another host. Mount issues a packack for the
device. The client then issues an ONLINE command. During
TMSCP/ONLINE processing, if the server finds an HQB address in
the UQB$L_ONLINE_HQB field, it returns SUCCESS status with an
ALONL subcode even though the HQB is not for the requesting host.
When the client processes the successful ONLINE end message, it
issues a GUS. The server returns a unit-available for this
command which causes the client TUDRIVER to reissue an ONLINE
which starts the process all over again. It stays in this
loop forever.
o An INVEXCEPTN system crash may occur when TMSCP does not get a
message buffer during configuration when a connection to
MSCP$TAPE is broken.
o Unexpected end messages are logged on client nodes for GUS and
AVAILABLE commands. A Cache Data Lost error is detected in the
tape subsystem due to a hardware-related problem. A GUS end
message is returned to the client with an end message status of
08 (data error). This status is set up in the SEND_END routine
in TMSCP. Since this is not a valid status for a GUS, the client
TUDRIVER rejects the invalid status, logs an error and then calls
TU$RE_SYNCH which breaks the connection.
RELATED ARTICLES:
Detailed articles describing the problems listed above may exist in
the OPENVMS database. To view these articles, open the appropriate
product database and perform a query using either of the following
search strings: 'VAXMSCP02_061' or 'VAXMSCP'.
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:
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.
==========================================================================
| Table of Kit Image Information |
+----------------------------+----------+-----------------+--------------+
| | Overall | Image File | Image Link |
| Image Name | Checksum | Identification | Date/Time |
+----------------------------+----------+-----------------+--------------+
| TMSCP.EXE |%X7E85832F| X-22A8 | 6-MAY-1997 |
| | | 01:17:36.50 |
+----------------------------+----------+-----------------+--------------+
|
