SEARCH CONTACT US SUPPORT SERVICES PRODUCTS STORE
United States    
COMPAQ STORE | PRODUCTS | SERVICES | SUPPORT | CONTACT US | SEARCH
gears
compaq support options
support home
software & drivers
ask Compaq
reference library
support forum
frequently asked questions
support tools
warranty information
service centers
contact support
product resources
parts for your system
give us feedback
associated links
.
} what's new
.
} contract access
.
} browse patch tree
.
} search patches
.
} join mailing list
.
} feedback
.
patches by topic
.
} DOS
.
} OpenVMS
.
} Security
.
} Tru64 Unix
.
} Ultrix 32
.
} Windows
.
} Windows NT
.
connection tools
.
} nameserver lookup
.
} traceroute
.
} ping
PLY_CM CONSOLEECO2016 POLYCENTER Console Manager OpenVMS ECO Summary

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 1995, 1996. All rights reserved. PRODUCT: POLYCENTER Console Manager (PCM) OP/SYS: OpenVMS VAX OpenVMS Alpha SOURCE: Digital Equipment Corporation ECO INFORMATION: ECO Kit Name: CONSOLEECO2016 ECO Kits Superseded by This ECO Kit: CONSOLEECO1016 ECO Kit Approximate Size: Saveset A - 8532 Blocks Saveset B - 10116 Blocks Saveset C - 10134 Blocks Saveset D - 17316 Blocks Saveset E - 17316 Blocks Cover Letter - 10 Blocks Total of 6 files - 63424 Blocks Kit Applies To: POLYCENTER Console Manager V1.6 OpenVMS VAX V6.1, V6.2 OpenVMS Alpha V6.1, V6.2 System/Cluster Reboot Necessary: No ECO KIT SUMMARY: An ECO kit exists for POLYCENTER Console Manager V1.6 for OpenVMS VAX and OpenVMS Alpha. This kit addresses the following problems: Problems addressed in the CONSOLEECO2016 Kit: o Transmission break on the console. Transmission break on some types of systems was followed by an Access Violation (ACCVIO). o DIALOG command. + RATE command did not work. + Console DIALOG command did not work for an unprivileged user. + Console MONITOR DIALOG command failed to determine the dialog file location. o Controller processes crashes with ACCVIO. Parent and Child Controller processes often crashed with ACCVIO in different situations on OpenVMS. o Console MONITOR crashes and hangs. + Console MONITOR crashed with ACCVIO in the cases of the system log file being absence or corrupt. + Console MONITOR crashed with ACCVIO when using the FIND command. + Console MONITOR crashed in some cases with ACCVIO after issuing the CONNECT command or using the C3 'Connect to Console' interface. + Console MONITOR would hang on OpenVMS V6.2 if no Monitor commands were issued for 5 seconds. + Console MONITOR (also Console WATCH) sometimes gave old information between the lines of currently logged information. + Console MONITOR UNLOCK command caused ACCVIO in some situations. o Console CONNECT crashes. + Console CONNECT crashed with ACCVIO after issuing the CTRL/G immediately followed by any key strike. + Console CONNECT crashed with ACCVIO after PCM Shutdown, restart and attempt to issue the next CONNECT command from the MONITOR interface. o Console RECONFIGURE hangs. Console RECONFIGURE would hang after abnormal ARCHIVE completing with the message "Archive in progress, Reconfigure not performed". o Console WATCH crashes. + Console WATCH would crash with ACCVIO for an unprivileged user with only group access. + Console WATCH couldn't use Configuration Database group names and DCL logical names (for systems and groups of systems). o C3 problems. + C3 log window did not display event context for events that include special characters. + An unprivileged user could edit the C3 interface. + User that was not defined in Configuration DB couldn't leave the C3 interface. + C3 main window had very slow screen refresh rate. o Broadcast action. This action did not work. o Console EXTRACT exit. EXTRACT exit prompt was wrong in some situations. o Archive hangs. Console archive would hang during monitoring or watching. o ENS problems. + API routine CMRetreiveEventText() caused memory leak. + API routine CMGetEventContext() in some situations counted context lines incorrectly. + In some cases action routines failed to connect back to ENS. Problems addressed in the CONSOLEECO1016 Kit: o CMEventContextLine() Routine The API routine CMEventContextLine in Versions of PCM up to and including V1.5 used an event line number starting at 0. In V1.6 this has changed such that the line number now starts at line 1. This is an incompatible change, and requires that any action routine using this function call be re-compiled after suitable changes are made to the application. o CMUserGetEvent() Call Customer written action routines which used the CMUserGetEvent() call would fail in the PCM Version 1.6. o Lock Icon The lock icon was added or removed when connect and disconnect events were either cleared or acknowledged. o Archiving If a file open failed during archiving, the file would remain locked. o Startup of Eventlist Interface When Eventlist started up, it incorrectly indicated that it was detached. o Eventsingle and Timeout If a timeout value of more than 30 seconds was specified, Eventsingle would crash. o CONSOLE$DAEMON.EXE on OpenVMS Certain situations in archiving would cause the controller daemons to hang. o Eventlist and X Screen Saver When an event is received by PCM, and the screen saver is activated, the screen would remain blank. PCM now unblanks the screen when new events are received. o Privilege Checking on Groups The privilege checking on groups incorrectly allowed access to the groups when there were no users in the configuration database. o Invalid Icon Size Any X-Window displays which do not return a valid icon size list, when queried by the X-Window based interfaces, will now cause the smallest available icon to be used (16 x 16 pixels). o Starting Monitor During Archive The Monitor interface would crash when it was started whilst an archive operation was in progress. o DIALOG SPEED Command The DIALOG SPEED command would enter an infinite loop when SPEED was set to values greater than 1000. Please refer to the Release Notes included in the ECO kit for more details. INSTALLATION NOTES: You must be logged into the SYSTEM account to install this ECO. Before you install the kit, make sure that POLYCENTER Console Manager is shut down. The ECO kit is installed with the VMSINSTAL command procedure: $ @SYS$UPDATE:VMSINSTAL After the installation, use the following command to restart the product, rather than the startup option from the C3 interface: $ @SYS$STARTUP:CONSOLE$STARTUP This command reinstalls the PCM images for you. A system reboot is not necessary.



This patch can be found at any of these sites:

Colorado Site
Georgia Site



Files on this server are as follows:

consoleeco2016.README
consoleeco2016.CHKSUM
consoleeco2016.CVRLET_TXT
consoleeco2016.a-dcx_axpexe
consoleeco2016.a-dcx_vaxexe
consoleeco2016.b-dcx_axpexe
consoleeco2016.b-dcx_vaxexe
consoleeco2016.c-dcx_axpexe
consoleeco2016.c-dcx_vaxexe
consoleeco2016.d-dcx_axpexe
consoleeco2016.d-dcx_vaxexe
consoleeco2016.e-dcx_axpexe
consoleeco2016.e-dcx_vaxexe

privacy and legal statement