HP Services Software Patches - vaxmont01_060

Copyright (c) Digital Equipment Corporation 1996.  All rights reserved.

OP/SYS:     OpenVMS VAX

COMPONENT:  MONITOR Utility

SOURCE:     Digital Equipment Corporation

ECO INFORMATION:

     ECO Kit Name:  VAXMONT01_060
     ECO Kits Superseded by This ECO Kit:  VAXMONT01_061
                                           VAXMONT03_U2055
     ECO Kit Approximate Size:  572  Blocks
     Kit Applies To:   OpenVMS VAX V6.0
     System/Cluster Reboot Necessary:  Yes


ECO KIT SUMMARY:

An ECO kit exists for MONITOR Utility on OpenVMS VAX V6.0.  This kit 
addresses the following problems: 

Problems addressed in the VAXMONT01_060 kit:

  o  This kit is a re-issue of the VAXMONT01_061 kit with the
     OpenVMS V6.0 portion only.  The V5.5-2 and V6.1 sections of the
     VAXMONT01_061 kit will be superseded by future Shadowing kits.
         
Problems addressed in VAXMONT01_061 kit for OpenVMS VAX V5.5-2,
V5.5-2H4, V6.0, and V6.1

  o  Specifying the DISK Class to Monitor can result in unexpected
     side effects to the display.  When MONITOR DISK command is issued 
     on a system with DFS devices mounted, only the first three  
     characters of the DFS name are displayed correctly.  Instead of 
     the fourth character, the low byte of the unitm number is output.   
     It is often displayed as an non-printable character or as an escape 
     sequence (in which case, may cause terminal lock-ups, resetting 
     characteristics, etc).
     
     The following command illustrates this problem when executed on
     a system with DFS disks mounted:

     $MONITOR DISK

                       DISK I/O STATISTICS
                       on node NODENAME
                       7-APR-1994 16:25:17

     I/O Operation Rate


     DSA2241:         FOLKLORE            6.27    6.27    6.27    6.27
     DSA2249:         AUDIT               0.00    0.00    0.00    0.00
     DSA2263:         VMS19NOVC3L         0.00    0.00    0.00    0.00
     DSA2264:         LAV19NOVC3L         0.00    0.00    0.00    0.00
     DSA2265:         MDF19NOVC3L        15.84    15.84   15.84   15.84
     DSA2266:         VMS28APRB3E         0.00    0.00    0.00    0.00
     DSA2267:         LAV28APRB3E         0.00    0.00    0.00    0.00
     DSA2268:         MDF28APRB3E         0.00    0.00    0.00    0.00
     DSA2269:         VMS18JANC3L         0.00    0.00    0.00    0.00
     DSA2270:         MDF18JANC3L         0.00    0.00    0.00    0.00
     DSA2271:         LAV18JANC3L         0.00    0.00    0.00    0.00
     DSA2280:         VMS12OCTM3C         0.00    0.00    0.00    0.00
     $254$DFSé1001()  DEC:..._STAR        0.00    0.00    0.00    0.00
     $254$DFSH8008()  V501_RESD           0.00    0.00    0.00    0.00
     $254$DFSI8009()  V51_RESD            0.00    0.00    0.00    0.00
             

    o  The MONITOR DISK command hangs when monitoring a system with
       more than 800 disks.  MONITOR contains an arbitrary upper limit
       of 800 on the number of disks it can monitor.   When a system
       contains more than 800, MONITOR generates an error status, but
       the status is not properly signaled, and the display appears to
       hang.   This can also be seen with a MONITOR CLUSTER command
       (which collects DISK data implicitly).

    o  Due to an inadequate synchronization mechanism, the MONITOR
       DISK command can go into an infinite loop on multi-processor
       machines.

       In order to receive this complete fix the following kit will
       also need to be installed:

    o  For OpenVMS VAX V5.5-2:  VAXSYS12_U2055

    o  For OpenVMS VAX V6.0 and V6.1:  The latest available
       shadowing kit.          

    o  MONITOR PROCESS in a local environment will fail if the SYSGEN
       parameter MAXPROCESSCNT is set to more allow more than 1040
       processes.  When Virtual Balance Slots were added in OpenVMS
       V6.0, this number dropped to 978.
       
Problems addressed in VAXMONT01_061 kit for OpenVMS VAX V5.5-2,
V5.5-2H4

    o  In a mixed version OpenVMS cluster, the following MONITOR
       command will crash the target V6.0 node if issued from a V5.5-2
       node:
         
       MONITOR STATES,POOL,DECNET,LOCK /NODE=V6.0_node       

Problems addressed in VAXMONT03_U2055 KIT

    o  The image to correct the MAXPROCESSCNT problem should have been
       included in the VAXMON02_U2055 kit.  It was not.

Problems addressed in VAXMON02_U2055 KIT

    o  An error would occur when using the following MONITOR command;
       $MONITOR [CLASS] /NODE={nodelist} The error would indicate that
       the connection to one of the remote nodes had been lost and the
       collection activity would terminate for that node.

    o  The Monitor Process class will not function if the SYSGEN
       parameter MAXPROCESSCNT is larger than 1040.


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 VAXcluster, 
the entire cluster should be rebooted. 

Files on this server are as follows:

»vaxmont01_060.README
»vaxmont01_060.CHKSUM
»vaxmont01_060.CVRLET_TXT
»vaxmont01_060.a-dcx_vaxexe