| » contact hp |
search: |  | more options |
| Supportall of hp US

|  | HP Services Software Patches |

» | software & drivers
» | ask Compaq
» | reference library
» | forums & communities
» | support tools
» | warranty information
» | contact support
» | parts
» | give us feedback
patches by topic
» | DOS
» | OpenVMS
» | Security
» | Tru64 Unix
» | Ultrix 32
» | Windows
» | Windows NT
associated links
» | what's new
» | contract access
» | browse patch tree
» | search patch tree
» | join mailing list
connection tools
» | nameserver lookup
» | traceroute
» | ping
HP Services Software Patches - vaxmont01_061
    Copyright (c) Digital Equipment Corporation 1995.  All rights reserved.

    OP/SYS:     OpenVMS VAX

    COMPONENT:  MONITOR Utility

    SOURCE:     Digital Equipment Corporation

    ECO INFORMATION:

         ECO Kit Name:  VAXMONT01_061
         ECO Kits Superseded by This ECO Kit:  VAXMONT03_U2055 (CSCPAT_1033)
         ECO Kit Approximate Size:  Saveset A -   72 Blocks
                                    Saveset B -  504 Blocks
                                    Saveset C -  522 Blocks
                                    Saveset D -  522 Blocks
                                 Cover Letter -   15 Blocks

                             Total of 5 files - 1635 Blocks

         Kit Applies To:  OpenVMS VAX V5.5-2, V5.5-2H4, V6.0, V6.1
         System/Cluster Reboot Necessary:  Yes

    ECO KIT SUMMARY:

    An ECO kit exists for the MONITOR Utility on OpenVMS VAX V5.5-2 through
    V6.1.  This kit addresses the following problems:

    Problems Addressed in VAXMONT01_061 for OpenVMS VAX V5.5-2, V5.5-2H4,
    V6.0, and V6.1:

      o  When the 'MONITOR DISK' command is issued on a system with DFS
         devices mounted, only the first three characters of the DFS
         disk name are displayed correctly.  The last character is
         often displayed as a non-printable character or as an escape
         sequence.  This may cause terminal lock-ups, resetting of
         terminal characteristics or other unexpected terminal side effects.

      o  The 'MONITOR DISK' command may appear to hang when monitoring
         a system with more than 800 disks.  An error occurs, but the
         error status is not displayed.  The hang may also occur when a
         MONITOR CLUSTER command is issued.

      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 the complete fix for this problem, one of
         the following kits 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 most current
                  Volume Shadowing kit

      o  Use of the 'MONITOR PROCESS' command in a local environment will
         fail if the SYSGEN parameter MAXPROCESSCNT is set to 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 for OpenVMS VAX V5.5-2 and V5.5-2H4:

      o  In a mixed version OpenVMScluster, the following MONITOR
         command will crash the target V6.0 node if it is issued
         from a V5.5-2 node:

              $MONITOR STATES,POOL,DECNET,LOCK /NODE=V6.0_node

    Problems Addressed in VAXMONT03_U2055 for OpenVMS VAX V5.5-2:

      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 for OpenVMS VAX V5.5-2:

      o  An error occurs when using the following MONITOR command:

              $ MONITOR [CLASS] /NODE={nodelist}

         The error indicates that the connection to a remote node
         has been lost and the collection activity terminates for
         that node.

      o  The MONITOR process class will not function if the SYSGEN
         parameter MAXPROCESSCNT is larger than 1040.  The following
         errors will be returned:

              %MONITOR-E-COLLERR, error during data collection
              -SYSTEM-F-BADPARAM, bad parameter value

    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 must be rebooted.
Files on this server are as follows:
    »vaxmont01_061.README
    »vaxmont01_061.CHKSUM
    »vaxmont01_061.CVRLET_TXT
    »vaxmont01_061.a-dcx_vaxexe
    »vaxmont01_061.b-dcx_vaxexe
    »vaxmont01_061.c-dcx_vaxexe
    »vaxmont01_061.d-dcx_vaxexe

privacy statement | using this site means you accept its terms |
© 1994-2002 Hewlett-Packard Company