Jump to page titleUNITED STATES
hp.com home products and services support and drivers solutions how to buy
» contact hp

more options
hp.com home
End of Jump to page title
HP Services Software Patches
Jump to content

» software & drivers
» ask Compaq
» reference library
» forums & communities
» support tools
» warranty information
» contact support
» parts
» give us feedback

patches by topic
» 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

Find Support Information and Customer Communities for Presario.
Content starts here
HP Services Software Patches - dcrosf151
Copyright (c) Digital Equipment Corporation 1994. All rights reserved.

PRODUCT:     POLYCENTER Console Manager (PCM)


SOURCE:      Digital Equipment Corporation


     ECO Kit Name:                     DCROSF151
     ECO Kits Superseded by This Kit:  None
     ECO Kit Approximate Size:         6820 blocks (tar file)
     Kit Applies To:                   POLYCENTER Console Manager V1.5
                                       DEC OSF/1 V1.3 or later
     System Reboot Necessary:          No


An ECO kit exists for POLYCENTER Console Manager V1.5 on DEC OSF/1 V1.3 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
  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.
Files on this server are as follows:
privacy statement using this site means you accept its terms