HP Services Software Patches - alpmscp02_070

 
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 1996, 1997.  All rights reserved.

PRODUCT:    OpenVMS Alpha

COMPONENT:  MSCP.EXE

SOURCE:     Digital Equipment Corporation

ECO INFORMATION:

     ECO Kit Name:  ALPMSCP02_070
     ECO Kits Superseded by This ECO Kit:  ALPMSCP01_070 for OpenVMS 
                                           Alpha V7.0 *ONLY*
     ECO Kit Approximate Size:  270 Blocks
     Kit Applies To:  OpenVMS Alpha V7.0
     System/Cluster Reboot Necessary:  Yes


ECO KIT SUMMARY:

An ECO kit exists for MSCP.EXE on OpenVMS Alpha V7.0.  This kit 
addresses the following problems:

Problems addressed by the ALPMSCP02_070 kit:

  o  These OpenVMS Alpha V7.0 problem corrections were included in
     the multi-version ALPMSCP01_070 remedial kit.  They are now
     being issued as a V7.0 only remedial kit.

     There are no new problem corrections in this remedial kit.


Problems addressed by the ALPMSCP01_070 kit:

  o  Issuing ERASE commands with history logging enabled on MSCP
     clients for large numbers of blocks to MSCP devices served
     by an OpenVMS MSCP server causes problems on both OpenVMS VAX
     and OpenVMS Alpha.

     On an AlphaServer, an "Illegal Command" entry will be posted
     in the system error log and the command will be aborted.
     Typically, if the affected device is part of a shadow set,
     the set will enter mount verification and the I/O request will
     eventually fail with a "Fatal Controller Error".

     On a VAXserver, no immediate problem is noticed.  However, the
     possibility of a shadow set becoming corrupt exists.  The
     corruption will occur if there is a failure during the execution
     of the ERASE command and a mini-merge is performed when the set
     becomes available.

  o  A satellite node will not boot after a preferpath/forcepath
     command is issued on the server.

  o  Word instructions are used to reference a byte field.  This problem
     was discovered by engineering during testing.  In a code change,
     IRP fields were moved around, and one of these byte fields ended
     up as the last byte in the IRP. If the IRP is the last IRP in
     NON-paged pool, a word access could have caused an access crash.
     The code was changed so that they are now byte accesses.


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.

Files on this server are as follows:

»alpmscp02_070.README
»alpmscp02_070.CHKSUM
»alpmscp02_070.CVRLET_TXT
»alpmscp02_070.a-dcx_axpexe