OpenVMS VAXMSCP02_061 VAX V6.1 TMSCP 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) 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: 

Problems Addressed in the VAXMSCP02_061 Kit:

  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.


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. 

Colorado Site
Georgia Site

vaxmscp02_061.README
vaxmscp02_061.CHKSUM
vaxmscp02_061.CVRLET_TXT
vaxmscp02_061.a-dcx_vaxexe