OpenVMS VAXMSCP01_071 VAX V7.1 TMSCP/MSCP 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 
            MSCP.EXE

SOURCE:     Digital Equipment Corporation

ECO INFORMATION:

     ECO Kit Name:  VAXMSCP01_071
     ECO Kits Superseded by This ECO Kit:  None 
     ECO Kit Approximate Size:  144 Blocks
     Kit Applies To:  OpenVMS VAX V7.1 
     System/Cluster Reboot Necessary:  Yes

     Installation Rating:  3 - To be installed on all systems running
                               the listed versions of OpenVMS which
                               are experiencing the problems described.

     NOTE:  In order to receive the full fixes listed in this kit,
            the following remedial kits also need to be installed:

                 None 


ECO KIT SUMMARY:

An ECO kit exists for TMSCP and MSCP on OpenVMS VAX V7.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  An inconsistent transfer count occurs when a forced error is
     encountered on a drive.  A drive directly attached (or HSx
     served) reports a different transfer count from the same drive
     served via the MSCP server.

     Code that attempts to determine the LBN of a forced error
     block by looking at the byte count in the IOST/IOSB will
     arrive at different values on the same drive when directly
     accessed or MSCP served.


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

vaxmscp01_071.README
vaxmscp01_071.CHKSUM
vaxmscp01_071.CVRLET_TXT
vaxmscp01_071.a-dcx_vaxexe