HP Services Software Patches - consoleeco1015

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

PRODUCT:     POLYCENTER Console Manager (PCM)

OP/SYS:      OpenVMS VAX
             OpenVMS AXP

SOURCE:      Digital Equipment Corporation

ECO INFORMATION:

     ECO Kit Name:  CONSOLEECO1015
     ECO Kits Superseded by This ECO Kit:  None
     ECO Kit Approximate Size:  21,200 blocks
     Kit Applies To:  POLYCENTER Console Manager V1.5
                      OpenVMS VAX V6.0 or later
                      OpenVMS AXP V1.5 or later
     System Reboot Necessary:  No


ECO KIT SUMMARY:

An ECO kit exists for POLYCENTER Console Manager V1.5 on OpenVMS VAX
V6.0 or higher and OpenVMS AXP V1.5 or higher.  This kit addresses the
following problems: 
 
  o  Additional system icons have been provided with this ECO.  These
     icons are installed in the default icon area.

  o  The editor UID file provided in the PCM Version 1.5 software kit 
     for OpenVMS AXP was corrupt.

  o  If you were running Eventlist interactively and restarted PCM by 
     selecting the restart option from the File menu, Eventlist would 
     not start up again in interactive mode.

  o  Eventlist would sometimes access violate or core dump when it
     received events as a result of a user's program calling the
     CMUserSendEvent API routine. 

  o  Archiving Console Manager log files would fail with the message
     that logging was disabled. 
 
  o  The Console Manager Extract utility would not always extract the
     latest console data received by the PCM daemons. 

  o  The API routine CMEventContext would incorrectly return the log
     length and time when the event text indicated that there was no
     context for the event. 

  o  The API routine CMUserSendEvent would access violate or core dump
     if some of the required parameters were supplied as NULL pointers.
  
  o  The PCM daemon would access violate or core dump if the
     configuration database contained details of: 

     +  An enabled system that used TELNET transport and had a
        listener number containing non-numeric characters.

     +  An enabled system that used LAT or TELNET transport that did not
        have any information entered for a terminal server name or
        port/listener name/number. 

  o  If the configuration database contained invalid information for an
     enabled system, the PCM daemon processes would sometimes access
     violate or core dump. 

  o  The character cell and X-windows editors had different limits for
     event count and start values. 
 
  o  There was a problem with the amount of memory used by the
     Event Notification Services (ENS).

  o  If a user's program executed CMUserSendEvent a number of times, the
     ENS daemon would access violate or core dump. 

  o  The byte limit quota restricted the number of Eventlist connections
     the ENS daemon could create.  When it reached the quota, ENS would
     exit. 
 
  o  If the connection between a system console using TELNET and a
     terminal server was lost while the PCM daemon was checking the
     connection to a remote system, the daemon would access violate.

  o  The character cell editor did not remove blank spaces from the
     front or end of usernames entered in the configuration database.
     This caused mismatches when privileges were checked.
     
  o  The monitor interface did not interpret any key values set in the
     initialization file. 
  
  o  The monitor interface would access violate or core dump if you
     repeatedly used the ONE and TWO commands with VIEW and SHOW.
   
  o  The monitor interface would access violate or core dump if you used
     the SHOW KEYS command or SHOW SYSTEMS command to create a log
     window and then connected to and disconnected from a system.
 
  o  On OpenVMS systems only, if you used the monitor interface SET
     WIDTH command to set the display from 80 to 132 columns, the width
     of the screen changed but 80 columns of data continued to be
     displayed. 

  o  On an OpenVMS system, the IVP incorrectly checked for the 
     file CONSOLE$PRIVATE_LOGICALS.TEMPLATE.

  o  If you used the C3 Interface on an OpenVMS system to create a
     window for historical events, any new log data or event data
     returned would not be shown in this window. 

  o  The PCM Daemon on OpenVMS Failed to Open a Device.

  o  On OpenVMS systems, an archive would sometimes cause both the
     archiver and the console controller daemon for the system being
     archived to "hang". 

  o  The eventlist, dialog, and monitor interfaces did not correctly
     interpret the CONSOLE$USER_DEFAULTS logical on OpenVMS systems
     and CONSOLE_USER_DEFAULTS environment variable on ULTRIX and OSF/1 
     systems.

  o  On OSF/1 systems, a memory leak would sometimes cause eventlist to
     access violate. 

  o  The monitor interface would sometimes hang on ULTRIX Systems.

  o  Section 4.5.1 of the POLYCENTER Console Manager Users' Guide
     describes how to archive multiple systems by specifying their names
     on the command line.   This description is incorrect.   Only a 
     single system or all systems can be archived using the procedures
     described in Section 4.5.


INSTALLATION NOTES:

Before the installation of this ECO, please make sure that POLYCENTER 
Console Manager is shut down.

The system does not need to be rebooted after this kit is installed.

After the installation, the following command should be used to restart 
the POLYCENTER Console Manager.

   $ @SYS$STARTUP:CONSOLE$STARTUP

Files on this server are as follows:

»consoleeco1015.README
»consoleeco1015.CHKSUM
»consoleeco1015.a-dcx_axpexe
»consoleeco1015.a-dcx_vaxexe