| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2.1 | IFT1 is available | OPG::PHILIP | And through the square window... | Thu Aug 06 1992 19:00 | 36 |
| 2.2 | IFT2 is available | OPG::SIMON | | Fri Sep 04 1992 17:04 | 35 |
| 2.3 | IFT3 kit available. | OPG::SIMON | | Wed Oct 07 1992 17:21 | 34 |
| 2.4 | EFT1 kit. | OPG::SIMON | | Wed Nov 04 1992 11:55 | 7 |
| 2.5 | EFT2 kit available. | OPG::SIMON | | Mon Dec 07 1992 15:37 | 12 |
| 2.6 | New EFT2 kit | OPG::PHILIP | And through the square window... | Wed Dec 09 1992 16:55 | 14 |
| 2.7 | Pre SSB kit available. | OPG::SIMON | | Wed Jan 27 1993 10:09 | 11 |
| 2.8 | SSB Kit available. | OPG::SIMON | | Thu Feb 11 1993 16:18 | 11 |
| 2.9 | V1.1 IFT | OPG::PHILIP | And through the square window... | Thu Nov 11 1993 16:50 | 139 |
| 2.10 | V1.1 IFT2 | OPG::PHILIP | And through the square window... | Fri Nov 19 1993 16:13 | 127 |
| 2.11 | | OPG::PHILIP | And through the square window... | Fri Nov 19 1993 16:45 | 11 |
| 2.12 | Come and get it... | OPG::PHILIP | And through the square window... | Mon Nov 22 1993 09:58 | 5 |
| 2.13 | | OPG::PHILIP | And through the square window... | Fri Nov 26 1993 18:07 | 9 |
| 2.14 | | OPG::PHILIP | And through the square window... | Wed Jan 12 1994 16:38 | 79 |
| 2.15 | They're back!!! | OPG::PHILIP | And through the square window... | Fri Jan 14 1994 14:40 | 10 |
| 2.16 | EFT2 | OPG::PHILIP | And through the square window... | Mon Feb 07 1994 16:53 | 346 |
| 2.17 | EFT3 | OPG::PHILIP | And through the square window... | Wed Mar 09 1994 14:11 | 258 |
| 2.18 | EFT4 | OPG::PHILIP | And through the square window... | Thu Mar 31 1994 15:59 | 258 |
| 2.19 | SSB submission kit | OPG::SIMON | | Fri Apr 22 1994 11:55 | 58 |
| 2.20 | V1.0 RELEASE KIT | OPG::SIMON | | Wed Apr 27 1994 12:32 | 52 |
| 2.21 | V1.5 Available | OPG::PHILIP | And through the square window... | Wed Jun 01 1994 13:35 | 129 |
|
OK, we finally did it, we actually submitted the software and
are allowed to ship it.
The POLYCENTER Console Manager V1.5 kits are available in:
OPG::CM$KITS:
The documentation is in:
OPG::CM$DOCS:
Below you will find the cover letter which will go out with the
kits, please note, the cover letter talks about V1.5 on
OpenVMS VAX only, however, you will find the V1.5 kits for ALL
platforms in the distribution area....
Enjoy,
Phil
DIGITAL
Order Number: AV-PREPC-TE
June 1994
POLYCENTER Console Manager Version 1.1
POLYCENTER Console Manager Version 1.5
READ BEFORE YOU INSTALL
Thank you for buying POLYCENTER[TM] Console Manager. Please read this
letter carefully before you begin the PCM installation as it contains
important information.
Explanation of Version Numbering Scheme
The OpenVMS[TM] VAX[TM] version of PCM is at Version 1.5 while
version numbers on the other platforms (OpenVMS AXP[TM],
RISC ULTRIX[TM] and DEC OSF/1) are at Version 1.1. This is
because the OpenVMS VAX version replaces VAXcluster[TM]
Console System (VCS) Version 1.4, and must have a version number
that is higher than 1.4.
Printed documentation refers to PCM Version 1.1 when describing all
platforms. Version 1.1 and Version 1.5 are functionally the same, and
so the Version 1.1 POLYCENTER Console Manager Installation Guide and
POLYCENTER Console Manager Users' Guide documentation is applicable
for both versions.
Important Information for VAXcluster Console (VCS) Customers
If you are a VCS Version 1.4 customer upgrading to PCM for the first
time, there are some additional postinstallation tasks you
must complete. The instructions are described in detail in the
POLYCENTER Console Manager Installation Guide. You are advised
to start your installation preparation by reading the Preface
to this guide.
Upgrading from VCS Version 1.4 to PCM for OpenVMS VAX Version 1.5
POLYCENTER Console Manager is Digital's new OpenVMS console
consolidation product, which will replace VCS Version 1.4. If
you have an update service for VCS Version 1.4, one concurrent
VCS license entitles you to one concurrent PCM Version 1.5 license.
If you are not under service for VCS, you can purchase an upgrade
license for PCM Version 1.5 on a one-to-one ratio. PCM will
recognize the VCS Product Authorization Key (PAK).
Another license type is available with PCM, an unlimited license.
This is a cost-effective license for customers using PCM to
connect to more than 100 devices. Contact your Digital
representative for assistance with trading up to an unlimited
use license, or for moving any license to a different platform.
All PCM Numbers to Match with Next CONDIST
To avoid confusion over version numbers, Digital will increase
the version number on each of the other platforms to 1.5 with
the next release of each platform's CONDIST. By late August,
PCM Version 1.5 will be the shipping version on all platforms.
Please note that the printed documentation will still refer to
Version 1.1, although it will be applicable to both versions.
Upgrading from PCM Version 1.0 On RISC ULTRIX
The only supported upgrade path from PCM Version 1.0 is on the RISC
ULTRIX platform. If you are upgrading from PCM Version 1.0 to either
PCM Version 1.1 or Version 1.5 there are some additional
preinstallation tasks you must complete. The instructions
are described in detail in the POLYCENTER Console Manager
Installation Guide. You are advised to start your installation
preparation by reading the Preface to this guide.
There are no additional preinstallation tasks to complete if you are
upgrading from PCM Version 1.1 to Version 1.5.
The Release Notes
The POLYCENTER Console Manager release notes are available only
online. OpenVMS installations will automatically put a copy of
the release notes in the SYS$HELP directory. For RISC ULTRIX
and OSF/1 systems, ensure that you choose the release notes
subset for installation when you run the installation procedure.
This is explained in detail in the POLYCENTER Console Manager
Installation Guide.
� Digital Equipment Corporation 1994. All rights reserved.
____________________
[TM] AXP, OpenVMS, POLYCENTER, ULTRIX, VAX, VAXcluster and the
DIGITAL logo are trademarks of Digital Equipment Corporation
2
|
| 2.22 | V1.5 ECO1 Available | OPG::PHILIP | And through the square window... | Wed Sep 14 1994 18:03 | 440 |
|
OK, We have finally put together the first ECO kit for V1.5
The files are all in:
OPG::CM$KIT:
The files you need are:
CONSOLEECO1015.A - OpenVMS (VAX and AXP)
DCROSF151.TAR - OSF/1
DCR151.TAR - ULTRIX
The release notes are included below for your perusal.
Enjoy,
Cheers,
Phil
POLYCENTER_Console_Manager____________________
ECO 1 Release Notes
These release notes provide information about the
the POLYCENTER Console Manager Engineering Change
Order (ECO) 1 software kit.
Revision/Update Information: This document
supplements the
release note
information provided
with POLYCENTER
Console Manager
Version 1.5.
Operating System: RISC ULTRIX Version
4.3a
OSF/1 AXP Version 1.3
OpenVMS AXP Version
1.5
OpenVMS VAX Version
6.0
Associated Software: OSF/Motif Version
1.1.3
Product and Version: POLYCENTER Console
Manager Version 1.5
ECO 1
Digital Equipment Corporation
Maynard, Massachusetts
__________________________________________________________
September 1994
The information in this document is subject to change
without notice and should not be construed as a commitment
by Digital Equipment Corporation. Digital Equipment
Corporation assumes no responsibility for any errors that
may appear in this document.
Possession, use, or copying of the software described in
this documentation is authorized only pursuant to a valid
written license from Digital or an authorized sublicensor.
While Digital believes the information included in this
publication is correct as of the date of publication, it
is subject to change without notice.
Digital Equipment Corporation makes no representations
that the use of its products in the manner described
in this document will not infringe existing or future
patent rights, nor do the descriptions contained in this
publication imply the granting of licenses to make, use
or sell equipment or software in accordance with the
description.
) Digital Equipment Corporation 1994.
All Rights Reserved.
The following are trademarks of Digital Equipment
Corporation: AXP, DECconnect, DECnet, DECserver,
DECstation, DECsystem, Decterm, OpenVMS, POLYCENTER,
ULTRIX, VAX, VMS and the DIGITAL logo
Motif, OSF, OSF/1 and OSF/Motif are registered trademarks
of the Open Software Foundation, Inc.
This document was prepared using VAX DOCUMENT, Version
2.1.
1
________________________________________________________________
POLYCENTER Console Manager ECO 1 Software
1.1 Introduction
These release notes describe the differences between
POLYCENTER[TM] Console Manager (PCM) Version 1.5 and the
software provided in the Engineering Change Order (ECO) 1
kit.
Read this information before installing the ECO 1 software
kit.
For more information about PCM, refer to the documentation
provided with the PCM Version 1.5 software:
o POLYCENTER Console Manager Installation Guide
o POLYCENTER Console Manager Users' Guide
o PCM Release Notes (online)
The information in this chapter refers to all platforms
unless otherwise stated.
1.2 System Icons
There are some additional system icons provided by the ECO
1 software. These icons are installed in the default icon
area.
1.3 Software Problems Fixed
This section describes problems found with the POLYCENTER
Console Manager Version 1.5 software and fixed by the ECO
1 software.
POLYCENTER Console Manager ECO 1 Software 1-1
POLYCENTER Console Manager ECO 1 Software
1.3 Software Problems Fixed
1.3.1 Editor UID File for OpenVMS AXP Systems
The editor UID file provided in the PCM Version 1.5
software kit for OpenVMS[TM] AXP[TM] was corrupt.
The editor UID file provided in the ECO 1 kit replaces the
corrupt file.
1.3.2 Restarting PCM and Using Eventlist Interactively
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.
1.3.3 Eventlist and CMUserSendEvent
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.
1.3.4 Archiving Log Files
Archiving Console Manager log files would fail with the
message that logging was disabled.
1.3.5 Console Data Missing in Log Files
The Console Manager Extract utility would not always
extract the latest console data received by the PCM
daemons. The Extract utility reads console data from log
files and, at the time of the extract, the data may not
have been written to the log files.
1.3.6 Log Length and Time Returned By CMEventContext
Routine
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.
1.3.7 CMUserSendEvent Routine
The API routine CMUserSendEvent would access violate or
core dump if some of the required parameters were supplied
as NULL pointers.
1-2 POLYCENTER Console Manager ECO 1 Software
POLYCENTER Console Manager ECO 1 Software
1.3 Software Problems Fixed
1.3.8 Information in the Configuration Database
The PCM daemon would access violate or core dump if the
configuration database contained details of:
o An enabled system that used TELNET transport and had a
listener number containing non-numeric characters.
o 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.
The configuration editor has been modified to check for
these conditions and provide warnings if they occur.
1.3.9 Invalid Configuration Information
If the configuration database contained invalid informa-
tion for an enabled system, the PCM daemon processes would
sometimes access violate or core dump.
The configuration editor has now been modified so that
a system is disabled if the editor detects invalid
information for it at verification.
1.3.10 Event Count and Start Limits
The character cell and X-windows editors had different
limits for event count and start values.
The limits are now the same for both editors.
1.3.11 ENS and Memory
There was a problem with the amount of memory used by the
Event Notification Services (ENS).
1.3.12 ENS Daemon and the CMUserSendEvent API Routine
If a user's program executed CMUserSendEvent a number of
times, the ENS daemon would access violate or core dump.
1.3.13 ENS Daemon and Byte Limit Quota
The byte limit quota restricted the number of Eventlist
connections the ENS daemon could create. When it reached
the quota, ENS would exit.
POLYCENTER Console Manager ECO 1 Software 1-3
POLYCENTER Console Manager ECO 1 Software
1.3 Software Problems Fixed
1.3.14 PCM Daemon and Remote System Check
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.
1.3.15 Entering Information in the Configuration Database
Using the Character Cell Editor
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.
1.3.16 Monitor Interface and the Initialization File
The monitor interface did not interpret any key values set
in the initialization file.
1.3.17 Monitor Interface Group Names
If you used a group name to start the monitor interface,
or if you specified a group name with the CONNECT command,
the group was incorrectly broken down into its subset of
defined systems.
1.3.18 Monitor Interface ONE and TWO Commands
The monitor interface would access violate or core dump if
you repeatedly used the ONE and TWO commands with VIEW and
SHOW.
1.3.19 Monitor Interface SHOW Command
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.
1.3.20 Monitor Interface SET WIDTH Command on OpenVMS
Systems
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. This problem occurred on OpenVMS systems only.
1-4 POLYCENTER Console Manager ECO 1 Software
POLYCENTER Console Manager ECO 1 Software
1.3 Software Problems Fixed
1.3.21 IVP on OpenVMS Systems
On an OpenVMS system, the IVP incorrectly checked for the
file CONSOLE$PRIVATE_LOGICALS.TEMPLATE.
This problem has now been fixed and the IVP checks for the
file CONSOLE$PRIVATE_SETUP.TEMPLATE.
1.3.22 C3 Interface on OpenVMS Systems
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.
1.3.23 PCM Daemon on OpenVMS Failed to Open a Device
If, on an OpenVMS system that used Direct transport,
console data had been received by the remote system before
the console manager had started, OpenVMS opened a channel
through the loginout process. This meant that the PCM
daemon failed when it tried to open the device.
The PCM daemon now sets the attribute NO TYPEAHEAD on
all Direct connections until the console is successfully
opened. When the console is opened, it sets the attribute
TYPEAHEAD on the connections.
Setting NO TYPEAHEAD on all Direct connections prevents
the OpenVMS job controller detecting the carriage return
sequence on the line and therefore no loginout process is
started.
1.3.24 Archiver Caused Daemon to Hang on OpenVMS Systems
On OpenVMS systems, an archive would sometimes cause both
the archiver and the console controller daemon for the
system being archived to "hang".
1.3.25 USER_DEFAULTS Logical on OpenVMS, ULTRIX, and OSF
/1 Systems
The eventlist, dialog, and monitor interfaces did not
correctly interpret the:
CONSOLE$USER_DEFAULTS logical on OpenVMS systems
CONSOLE_USER_DEFAULTS environment variable on ULTRIX
and OSF/1 systems
POLYCENTER Console Manager ECO 1 Software 1-5
POLYCENTER Console Manager ECO 1 Software
1.3 Software Problems Fixed
On OpenVMS systems, this problem has now been fixed and
the logical is used when you save data from the eventlist,
dialog, or monitor interface.
On ULTRIX and OSF/1 systems, the environment variables
do not support nested directories like the OpenVMS search
lists.
1.3.26 Eventlist Access Violation on OSF/1 Systems
On OSF/1 systems, a memory leak would sometimes cause
eventlist to access violate.
1.3.27 Monitor Interface Hangs on ULTRIX Systems
On ULTRIX systems, the monitor interface would sometimes
hang if the console was disconnected. It would continue to
accept characters from the keyboard but not process them.
1.4 Documentation Errors
1.4.1 Archive Command
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.
This restriction will be removed for a future release of
the software.
1-6 POLYCENTER Console Manager ECO 1 Software
|
| 2.23 | V1.5 MUP1 Available | OPG::PHILIP | And through the square window... | Mon Dec 19 1994 12:59 | 799 |
|
Well, Here it is, the long awaited MUP kit.
The files are all in OPG::CM$KIT:
The files you need are:
CONSOLEMUPA015.A, .B and .C - OpenVMS VAX and Alpha
PCM_V15A_ULTRIX.TAR - ULTRIX
PCM_V15A_OSF.TAR - OSF/1
The release notes are included here for your perusal. However the
following two fixes were made too late to be included in the
release notes...
1) A memory leak in the C3 which manifested itself when the C3 was
running and the rest of the product shut down is now fixed, over the
period of several hours this leak would cause the C3 to run out of
VM and so accvio.
2) The Character Cell editor would incorectly change the entity name
when doing a modify, so, if the database had system "FRED" and you
did a modify system "fred" the database entry would get changed
(incorrectly) to the name specified in the modify, in the instance,
it would go from all upper to all lower case.
---------------------------- WARNING ---------------------------
WE HAVE HAD A LOT OF PROBLEMS RELATED TO PEOPLE ATTEMPTING TO USE
DATABASES WHICH HAVE VERIFICATION ERRORS!!!
THIS MUP ALTERS THE WAY IN WHICH THE DAEMONS WORK. IF THERE ARE
***ANY*** DATABASE VERIFICATION ERRORS WHICH DO NO AUTOMATICALLY
DISABLE A SYSTEM, **** THE DAEMONS WILL REFUSE TO START UP ****
---------------------------- WARNING ---------------------------
Enjoy,
Cheers,
Phil
POLYCENTER_Console_Manager____________________
Mandatory Update Release Notes
These release notes provide information about
the the POLYCENTER Console Manager Version 1.5A
mandatory update software kit.
Revision/Update Information: This document
supplements the
release note
information provided
with POLYCENTER
Console Manager
Version 1.5A.
Operating System: RISC ULTRIX Version
4.3a
OSF/1 AXP Version 1.3
OpenVMS AXP Version
1.5
OpenVMS VAX Version
6.0
Associated Software: OSF/Motif Version
1.1.3
Product and Version: POLYCENTER Console
Manager Version 1.5A
MUP A
Digital Equipment Corporation
Maynard, Massachusetts
__________________________________________________________
December 1994
The information in this document is subject to change
without notice and should not be construed as a commitment
by Digital Equipment Corporation. Digital Equipment
Corporation assumes no responsibility for any errors that
may appear in this document.
Possession, use, or copying of the software described in
this documentation is authorized only pursuant to a valid
written license from Digital or an authorized sublicensor.
While Digital believes the information included in this
publication is correct as of the date of publication, it
is subject to change without notice.
Digital Equipment Corporation makes no representations
that the use of its products in the manner described
in this document will not infringe existing or future
patent rights, nor do the descriptions contained in this
publication imply the granting of licenses to make, use
or sell equipment or software in accordance with the
description.
� Digital Equipment Corporation 1994.
All Rights Reserved.
The following are trademarks of Digital Equipment
Corporation: AXP, DECconnect, DECnet, DECserver,
DECstation, DECsystem, Decterm, OpenVMS, POLYCENTER,
ULTRIX, VAX, VMS and the DIGITAL logo
Motif, OSF, OSF/1 and OSF/Motif are registered trademarks
of the Open Software Foundation, Inc.
This document was prepared using VAX DOCUMENT, Version
2.1.
1
________________________________________________________________
POLYCENTER Console Manager Version 1.5A Software
1.1 Introduction
These release notes describe the differences between
POLYCENTER[TM] Console Manager (PCM) Version 1.5 and
the software provided in the PCM Version 1.5A kit (see
Section 1.3).
The patches that were made for the Engineering Change
Order 1 (ECO 1) software kit are also included (see
Section 1.4).
Read this information before installing the PCM V1.5A
software kit.
For more information about PCM, refer to the documentation
provided with the PCM Version 1.5 software:
o POLYCENTER Console Manager Installation Guide
o POLYCENTER Console Manager Users' Guide
o PCM Release Notes (online)
The information in this chapter refers to all platforms
unless otherwise stated.
1.2 System Icons
The additional system icons which were provided by the ECO
1 software are included. These icons are installed in the
default icon area.
POLYCENTER Console Manager Version 1.5A Software 1-1
POLYCENTER Console Manager Version 1.5A Software
1.3 Software Problems Fixed by PCM Version 1.5A
1.3 Software Problems Fixed by PCM Version 1.5A
1.3.1 ENS and Debugging Enabled
Event Notification Services (ENS) would cause an access
violation when all the following conditions were met:
o DEBUG was enabled,
o An event occurred for an action defined as "One for All
Events and Userdata", and
o No userdata was defined in the dispatch record.
ENS no longer causes an access violation.
1.3.2 ENS and Event Preprocessing
ENS would hang in RWMBX when using event preprocessing.
ENS no longer hangs when using event preprocessing.
1.3.3 Buffers Not Flushed at PCM Shutdown
Daemon did not flush internal buffers at PCM shutdown.
Daemon now flushes internal buffers at PCM shutdown.
1.3.4 Informing the User of Extract's Progress
Extract did not indicate to the user that it was working.
Extract now displays a series of "." characters to
indicate that it is working when extracting to a file;
one character is written for every few thousand lines of
extracted data.
1.3.5 Timestamping the First Line of Data Logged
The daemon failed to write a timestamp for the first line
of data logged, which caused the daemon to loop if an
event occurred on the first line of data.
This is now fixed.
1.3.6 Actions with No Listener
ENS caused an access violation on OpenVMS, or a core dump
on ULTRIX and OSF/1 systems, if SYS$CREPRC failed for an
action which did not have a listener set up.
This is now fixed.
1-2 POLYCENTER Console Manager Version 1.5A Software
POLYCENTER Console Manager Version 1.5A Software
1.3 Software Problems Fixed by PCM Version 1.5A
1.3.7 Monitor Interface Behavior
The monitor interface did not behave like VCS when
connecting. Now any events for a system are cleared from
the event line when the user connects to that system.
This is now fixed.
1.3.8 Log Files on OpenVMS
On OpenVMS each child console controller now writes its
own log file in CONSOLE$TMP:.
1.3.9 Status of Disabled Systems
The status program now shows the status of systems that
are disabled instead of saying status is "Unknown (205)".
1.3.10 OpenVMS CONSOLE STATUS/SYSTEM=xxx Behavior
On OpenVMS, the command CONSOLE STATUS/SYSTEM=xxx did not
display any information.
This is now fixed.
1.3.11 Incorrect Data Logging
On OpenVMS, Console devices expecting to use 7 bits or
parity cause console manager to log data incorrectly.
Workaround
A workaround for this situation has been implemented for
PCM V1.5A, and involves the use of the following logical
names.
__________________________________________________________
Logical_Name__________Use_________________________________
CONSOLE$NOEIGHTBIT defined to any value will cause ALL
direct lines to be set up for 7 bits
per character.
CONSOLE$PARITY defined as either ODD or EVEN will
cause ALL direct lines to have the
______________________defined_parity_value._______________
POLYCENTER Console Manager Version 1.5A Software 1-3
POLYCENTER Console Manager Version 1.5A Software
1.3 Software Problems Fixed by PCM Version 1.5A
1.3.12 Flushing of Internal Buffers
The daemon did not flush its internal buffers until one of
the following occurred:
o The internal buffers were full,
o A user connected to the system, or
o An event occurred.
Since timestamps are only assigned to console data lines
as they are written to disk, the effect of this was
that consoles with small amounts of output, and which
never generated events, could have timestamps that were
incorrect by many hours. This did not affect the immediate
notification when events were generated.
The daemon now flushes its buffers every 30 seconds, which
means that the timestamp for a line will now be accurate
to within 30 seconds.
1.3.13 ASTs on OpenVMS Inadvertently Turned On
On OpenVMS, ASTs turned off by PCM's internal queue
management routines could inadvertently be turned back
on causing memory corruption on busy systems.
This is now fixed.
1.3.14 Quotas of Child Console Controllers
On OpenVMS, changes have been made to the default quotas
assigned to each child console controller as it starts up.
As a result, errors due to exceeded quotas are now less
likely to occur.
1.3.15 Scans Using the Characters [ and ]
When complex regular expressions using the match in range
metacharacters ([ and ]) failed, subsequent scans using
this same expression on a single line of console data
would produce unreliable results.
This is now fixed.
1-4 POLYCENTER Console Manager Version 1.5A Software
POLYCENTER Console Manager Version 1.5A Software
1.3 Software Problems Fixed by PCM Version 1.5A
1.3.16 Protection of CONSOLE$APP_DEFAULTS: Directory on
OpenVMS
On OpenVMS, the protection of the CONSOLE$APP_DEFAULTS:
directory was incorrectly set during the base product
installation; it should have a protection of World: Read,
Write.
This is now fixed.
1.3.17 Incorrect Processing of the Monitor Interface
Initialization File
The monitor interface incorrectly processed its ini-
tialization file when the user defaults logical name
/environment variable was defined.
1.3.18 SEND Command and Embedded Quotation Marks
The dialog interface now accepts embedded quotation marks
when using the SEND command.
1.3.19 SET WIDTH Command and the Monitor Interface
The monitor interface did not process the SET WIDTH 132
command correctly. The display was set to the correct
width, but the monitor interface still used to output text
at the old width.
1.3.20 Uppercase and Lowercase Characters in Status
Display
The status display now allows the use of either uppercase
or lowercase for all of its display modes.
1.3.21 Event Missing from the PCM Configuration Database
The extract interface would cause an access violation
on OpenVMS, or core dump on ULTRIX and OSF/1 systems,
when the log files contained an event which was no longer
defined in the PCM configuration database. Extract now
outputs a message detailing the name of the event that is
missing from the PCM configuration database.
POLYCENTER Console Manager Version 1.5A Software 1-5
POLYCENTER Console Manager Version 1.5A Software
1.3 Software Problems Fixed by PCM Version 1.5A
1.3.22 Archiver Caused File Access Conflicts
Archiving the Console Manager-specific log files can cause
file access conflicts. There is no fix for this release of
PCM.
Workaround
The workaround for this problem is to ensure that PCM is
shut down before issuing the command:
$ CONSOLE ARCHIVE CONSOLEMANAGER
1.3.23 Events Failed to Display in C3 History Log Window
Events which do not have up to 10 lines of log data before
them in the log files would not display on the C3 history
log window.
1.3.24 Events Could Not be Retrieved on OSF/1 Systems
On OSF/1 systems, Console Manager events could not be
retrieved by either extract or the C3 event history.
1.3.25 Displaying the Information Field
In the C3 interface, the show system dialog box did not
display the information field for the system.
1.3.26 User Preferences Not Saved
The C3 interface did not save the user's preferences for
the monitor interface control keys.
1.3.27 MODIFY FILTER Command
The MODIFY FILTER command in the character cell editor
has been changed so that current values for a filter
attribute will be maintained if a user only presses return
in response to a query to change it. Also, a user may now
change an attribute as follows:
o From filtering specific values to filtering all values.
o From filtering all values to filtering specific values.
1-6 POLYCENTER Console Manager Version 1.5A Software
POLYCENTER Console Manager Version 1.5A Software
1.3 Software Problems Fixed by PCM Version 1.5A
1.3.28 System Names with Different Case
In the C3 interface, the event history did not treat
identical system names with different case the same (for
example, FRED was different to fred). In some situations
this would result in a message which indicated the system
was not in the configuration database. This has now been
fixed.
1.3.29 Example Broadcast Action Routine Source File
On OpenVMS, the example broadcast action routine source
was missing from the kit. This mandatory update now
provides the file.
1.3.30 Eventlist and TCP/IP
When TCP/IP was set as the transport for displaying the C3
interface with the DECwindows display, and the node was
set to be the host address rather than the name, then the
eventlist would not start.
The address is now correctly processed by the eventlist.
1.3.31 Control Keys and the C3 Interface
The C3 interface would not allow the control keys to be
set on an individual system basis.
This is now fixed, and each system can now be assigned its
own unique control key values.
POLYCENTER Console Manager Version 1.5A Software 1-7
POLYCENTER Console Manager Version 1.5A Software
1.4 Software Problems Fixed by ECO 1
1.4 Software Problems Fixed by ECO 1
This section describes problems found with the POLYCENTER
Console Manager Version 1.5 software and fixed by the ECO
1 software.
1.4.1 Editor UID File for OpenVMS AXP Systems
The editor UID file provided in the PCM Version 1.5
software kit for OpenVMS AXP was corrupt.
The editor UID file provided in the ECO 1 kit replaces the
corrupt file.
1.4.2 Restarting PCM and Using Eventlist Interactively
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.
1.4.3 Eventlist and CMUserSendEvent
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.
1.4.4 Archiving Log Files
Archiving Console Manager log files would fail with the
message that logging was disabled.
1.4.5 Console Data Missing in Log Files
The Console Manager Extract utility would not always
extract the latest console data received by the PCM
daemons. The Extract utility reads console data from log
files and, at the time of the extract, the data may not
have been written to the log files.
1.4.6 Log Length and Time Returned By CMEventContext
Routine
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.
1-8 POLYCENTER Console Manager Version 1.5A Software
POLYCENTER Console Manager Version 1.5A Software
1.4 Software Problems Fixed by ECO 1
1.4.7 CMUserSendEvent Routine
The API routine CMUserSendEvent would access violate or
core dump if some of the required parameters were supplied
as NULL pointers.
1.4.8 Information in the Configuration Database
The PCM daemon would access violate or core dump if the
configuration database contained details of:
o An enabled system that used TELNET transport and had a
listener number containing non-numeric characters.
o 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.
The configuration editor has been modified to check for
these conditions and provide warnings if they occur.
1.4.9 Invalid Configuration Information
If the configuration database contained invalid informa-
tion for an enabled system, the PCM daemon processes would
sometimes access violate or core dump.
The configuration editor has now been modified so that
a system is disabled if the editor detects invalid
information for it at verification.
1.4.10 Event Count and Start Limits
The character cell and X-windows editors had different
limits for event count and start values.
The limits are now the same for both editors.
1.4.11 ENS and Memory
There was a problem with the amount of memory used by the
Event Notification Services (ENS).
1.4.12 ENS Daemon and the CMUserSendEvent API Routine
If a user's program executed CMUserSendEvent a number of
times, the ENS daemon would access violate or core dump.
POLYCENTER Console Manager Version 1.5A Software 1-9
POLYCENTER Console Manager Version 1.5A Software
1.4 Software Problems Fixed by ECO 1
1.4.13 ENS Daemon and Byte Limit Quota
The byte limit quota restricted the number of Eventlist
connections the ENS daemon could create. When it reached
the quota, ENS would exit.
1.4.14 PCM Daemon and Remote System Check
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.
1.4.15 Entering Information in the Configuration Database
Using the Character Cell Editor
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.
1.4.16 Monitor Interface and the Initialization File
The monitor interface did not interpret any key values set
in the initialization file.
1.4.17 Monitor Interface Group Names
If you used a group name to start the monitor interface,
or if you specified a group name with the CONNECT command,
the group was incorrectly broken down into its subset of
defined systems.
1.4.18 Monitor Interface ONE and TWO Commands
The monitor interface would access violate or core dump if
you repeatedly used the ONE and TWO commands with VIEW and
SHOW.
1.4.19 Monitor Interface SHOW Command
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.
1-10 POLYCENTER Console Manager Version 1.5A Software
POLYCENTER Console Manager Version 1.5A Software
1.4 Software Problems Fixed by ECO 1
1.4.20 Monitor Interface SET WIDTH Command on OpenVMS
Systems
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. This problem occurred on OpenVMS systems only.
1.4.21 IVP on OpenVMS Systems
On an OpenVMS system, the IVP incorrectly checked for the
file CONSOLE$PRIVATE_LOGICALS.TEMPLATE.
This problem has now been fixed and the IVP checks for the
file CONSOLE$PRIVATE_SETUP.TEMPLATE.
1.4.22 C3 Interface on OpenVMS Systems
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.
1.4.23 PCM Daemon on OpenVMS Failed to Open a Device
If, on an OpenVMS system that used Direct transport,
console data had been received by the remote system before
the console manager had started, OpenVMS opened a channel
through the loginout process. This meant that the PCM
daemon failed when it tried to open the device.
The PCM daemon now sets the attribute NO TYPEAHEAD on
all Direct connections until the console is successfully
opened. When the console is opened, it sets the attribute
TYPEAHEAD on the connections.
Setting NO TYPEAHEAD on all Direct connections prevents
the OpenVMS job controller detecting the carriage return
sequence on the line and therefore no loginout process is
started.
1.4.24 Archiver Caused Daemon to Hang on OpenVMS Systems
On OpenVMS systems, an archive would sometimes cause both
the archiver and the console controller daemon for the
system being archived to hang.
POLYCENTER Console Manager Version 1.5A Software 1-11
POLYCENTER Console Manager Version 1.5A Software
1.4 Software Problems Fixed by ECO 1
1.4.25 USER_DEFAULTS Logical on OpenVMS, ULTRIX, and OSF
/1 Systems
The eventlist, dialog, and monitor interfaces did not
correctly interpret the:
o CONSOLE$USER_DEFAULTS logical name on OpenVMS systems
o CONSOLE_USER_DEFAULTS environment variable on ULTRIX
and OSF/1 systems
On OpenVMS systems, this problem has now been fixed and
the logical name is used when you save data from the
eventlist, dialog, or monitor interface.
On ULTRIX and OSF/1 systems, the environment variables
do not support nested directories like the OpenVMS search
lists.
1.4.26 Eventlist Access Violation on OSF/1 Systems
On OSF/1 systems, a memory leak would sometimes cause
eventlist to access violate.
1.4.27 Monitor Interface Hangs on ULTRIX Systems
On ULTRIX systems, the monitor interface would sometimes
hang if the console was disconnected. It would continue to
accept characters from the keyboard but not process them.
1.5 Documentation Errors
1.5.1 Archive Command
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.
This restriction will be removed for a future release of
the software.
1-12 POLYCENTER Console Manager Version 1.5A Software
|
| 2.24 | MUP on HOLD | OPG::SIMON | | Tue Jan 03 1995 12:10 | 9 |
| Urgent,
to anyone whao has installed the MUP. there is a bug in the kit which
causes problems when sub scans are used with scan profiles.
For this reason I have removed access to the kits on opg.
I shalll updater this ASAP.
Cheers Simon...
|
| 2.25 | MUP available again. | OPG::SIMON | | Wed Jan 04 1995 13:05 | 13 |
| Ladies and Gents,
the MUP is now available again. It is being shipped to SSB
for checking and being loaded into the corporate Software Library today.
The kits are located as stated in .22 with the addition of an Anon ftp source.
elbrig.reo.dec.com. (16.36.32.86)
~ftp/ConsoleManager
Sorry for any problems this caused.
Cheers Simon....
|
| 2.26 | | YOSSAM::PHILIP | And through the square window... | Fri Apr 28 1995 17:06 | 250 |
|
Well, Here it is, the long awaited V1.6 FT kit.
Please exercise this kit as much as you can, if you have customers
that have been having problems such as the RWMBX one, by all means give
them this kit, but PLEASE, PLEASE stress that this is Field Test
software and so should be treated as such.
We are planning to release weekly updates to this kit, if in 4 weeks
time, the number of bugs is at a level we feel comfortable with, we
will be submitting to SSB.
If you (or your customers) have or create generic icons for systems,
groups or background bitmaps and you would like them in the kit, please
copy them to OPG:: and mail me on OPG::PHILIP I will then ensure that
they will be put in the next build of the kit.
The files for the kit and documentation are all in OPG::CM$FTKIT:
The files you need for installation are:
CONSOLE016.A, .B, .C and .D - OpenVMS VAX and Alpha
The documentation files are:
CONSOLE_V16.DECW$BOOK - Users guide in bookreader
format
CONSOLE_UG_V16.PS - Users guide in postscript
format
CONSOLE_IG_V16.PS - Installation guide in
postscript format
We will announce the OSF/1 kit when we have ironed out the last of the
bugs.
The WILL BE NO ULTRIX kit, V1.5 + MUP was the last ULTRIX release you
will see.
If you (or your customer) are using the OSCint software, or have
action routines that you have written using the API, then these action
routines MUST be re-compiled and linked as both the header file and the
mailbox message formats have changed. Any action routine not re-compiled
and re-linked will be unable to connect to ENS.
The preliminary release notes are included here for your perusal.
---------------------------- WARNING ---------------------------
WE HAVE HAD A LOT OF PROBLEMS RELATED TO PEOPLE ATTEMPTING TO USE
DATABASES WHICH HAVE VERIFICATION ERRORS!!!
THIS RELEASE ALTERS THE WAY IN WHICH THE DAEMONS WORK. IF THERE ARE
***ANY*** DATABASE VERIFICATION ERRORS WHICH DO NO AUTOMATICALLY
DISABLE A SYSTEM, **** THE DAEMONS WILL REFUSE TO START UP ****
When this happens you will get an OPCOM message telling you the
database is invalid.
---------------------------- WARNING ---------------------------
Enjoy,
Cheers,
Phil
POLYCENTER_Console_Manager____________________
Preliminary Release Notes
These release notes provide information about
the the POLYCENTER Console Manager Version 1.6
software kit.
1 New Features
1.1 New Hierarchical C3
The C3 is now hierarchical based upon the groups defined in
your database. Each group will be represented by one icon
that you may "zoom" into to see the groups member systems.
CFS.21341
1.2 Log file verifier
There is now a verification utility which will detect any
discrepancies in the log and archive files for a system.
For this release the /REPAIR functionality HAS NOT BEEN
tested.
1.3 /DELETE on Archive
After an archive, the resultant archived data may be
automatically deleted by specifying the /DELETE qualifier
on the archive command line
1.4 Dialog exit status
Dialog now set the value of $STATUS upon exit, the valid
values are listed towards the end of the file CONSOLE.H
located in SYS$LIBRARY: as well as the User guide.
1.5 /PRIORITY on extract
Extract can now filter the event output based upon
priority, this qualifier is only valid with the /EVENT
qualifier and takes the form /PRIORITY=(MINIMUM=xxx,
MAXIMUM=yyy) where xxx and yyy are one of the valid PCM
priority levels in the range CRITICAL, MAJOR, MINOR,
WARNING, CLEAR or INDETERMINATE.
1.6 Permanent controller processes
The "child" controller processes are now permanent once
they have been started even if they have no systems to
manage as a result of a reconfigure. Each child is assigned
an index, the systems in the database are assigned to each
index as can be seen via the CONSOLE STATUS command.
1.7 Parent daemon notifies exit reason.
The parent daemon will now output an OPCOM message (syslog
on OSF/1) giving the reason for its exit, such as no
licence etc.
1.8 New API routines
Several extra API routines have now been documented, see
the user guide for more details.
2 Fixes
1.1 This release incorporates all the fixes made in the V1.5
ECO and MUP release.
1.2 OSF/1 V3.2 requires patch
A patch is required for OSF/1 V3.2 LAT in order to prevent
kernel system panics when PCM is started up.
See Note 624.17 in the CONSOLEMANAGER Notes conference.
1.3 Processes in RWMBX
Under load on OpenVMS, the PCM processes would enter a
state of RWMBX and never return, the communication
mechanism used between the processes has been completely
rewritten to prevent this situation occuring. Note: The
processes may still enter a RWMBX state, however this state
should now only be temporary.
CFS.27088
CFS.24392
CFS.24376
1.4 Reconfigure
The reconfigure function is now more reliable.
1.5 Shutdown
The shutdown function is now more reliable.
CFS.25959
1.6 Watch
Watch did not show output for large numbers of selected
systems.
When used via a batch process, watch access violated.
CFS.23957
CFS.23793
CFS.24104
1.7 Dialog filenames
Dialog filenames when specified on the command line with
the /FILE qualifier would be truncated at 16 characters.
CFS.23969
CFS.23863
1.8 Extract
Extract access violates for a variety of reasons.
CFS.24009
CFS.26504
CFS.26345
Console Manager events could not be extracted
CFS.25862
1.9 Archive
Archive enters a compute bound loop
CFS.25988
1.10 Use of HOME as a system name
HOME was not correctly used as a hostname, it was being
translated by the DEC C Run-time library as part of PCM's
attempt to determine if the system specified on the command
line was a logical name or symbol. The translation check is
now not performed if the system name is one of the
following items :
HOME, USER, TERM, SHELL, MAIL, EXINIT and PATH
CFS.25855
1.11 Monitor interface
When using previous screen and next screen in the monitor
interface, lines at the top or bottom of the screen were
missed.
CFS.23864
Monitor would hang if the user typed at the keyboard before
the prompt was displayed.
CFS.24862
1.12 Memory leak exhausts VM
A memory leak in the daemon would cause the daemon to
access violate after running out of virtual memory. The
Monitor interface CYCLE command aggravated this condition
causing it to occur sooner rather than later.
CFS.24528
1.13 Eventlist using LAT for X transport
The use of LAT as the transport for the Eventlist would not
work.
CFS.24284
CFS.23794
|
| 2.27 | FT update | YOSSAM::PHILIP | And through the square window... | Fri May 05 1995 19:10 | 15 |
| Folks,
A new T1.6 kit is available in the OPG::CM$FTKIT: directory.
There is also now an OSF/1 kit in the above directory, it is named :-
DCROSF160.TAR
I havnt yet updated the bookreader of .PS files in the directory, I will
do that on Tuesday (Monday is a holiday here in the UK).
There are lots and lots of minor fixes in this kit, so we havnt bothered
to put any new release notes together.
Enjoy.
|
| 2.28 | | YOSSAM::PHILIP | And through the square window... | Thu May 11 1995 15:40 | 7 |
| Folks,
There are a new set of user and install guides (Postscript and
Bookreader) in the kit directory.
Cheers,
Phil
|
| 2.29 | T1.6-003 | YOSSAM::PHILIP | And through the square window... | Tue May 16 1995 16:00 | 61 |
| Folks,
The T1.6-003 kit is now available in OPG::CM$FTKIT:
This kit now has an extra saveset (subset on Digital Unix) full of
background bitmaps for the C3, installation of these bitmaps is
optional at install time.
So, for OpenVMS you now have...
CONSOLE016.A
CONSOLE016.B
CONSOLE016.C - this is new, background bitmaps
CONSOLE016.D - this was the old saveset C (VAX images)
CONSOLE016.E - this was the old saveset D (Alpha images)
The Digital Unix kit is in tar form and is...
DCROSF160_FT3.TAR
or for those with ftp access, the kit is available via
anonymous ftp at...
elbrig.reo.dec.com
Just cd to the subdirectory Console_Manager
Numerous bugs have been fixed in this kit although the release notes
have not been updated. However, some of the fixes/new features in this
kit are...
o Use of Pseudo-terminals no longer causes the daemons to hang in LEF
state on OpenVMS
o /dev/null doesnt get its protection changed by PCM on Digital Unix.
o The editors now remove a system from all the groups it was a member
of when the system is deleted.
o The editor implements a "Edit C3" privilege, this will be implemented
in the C3 itself for the next kit (-005)
o Various fixes in the monitor interface
o The database verification routines will now spot that TTA3 and TTA3:
are in fact the same device.
o The eventlist when executed from the C3 will attempt to reconnect to
ENS every 10 seconds if it loses the connection, also when run as part
of the C3, the quit, exit and restart buttons are greyed out.
o Various fixes to the C3 interface.
o Each console process (parent, child and ens) produce their own log
files in the PCM temporary directory.
If you have had a particular problem that isnt listed here it doesnt mean
that it hasnt been fixed, please try the kit and report the problem
(remind us if you have already reported it).
Cheers,
Phil
|
| 2.30 | T1.6-007 | PBUNIX::pgb | And through the square window... | Wed May 24 1995 20:49 | 18 |
|
OK folks,
The OpenVMS PCM T1.6-007 kit is now available in:
OPG::CM$FTKIT:
A Digital UNIX kit will be made available tomorrow.
The release notes have not been updated for this release, however,
there are LOTS of bugfixes in the daemon code, with luck, all those
LEF problems will have gone away.
Enjoy,
Phil
|
| 2.31 | | PBUNIX::pgb | And through the square window... | Tue May 30 1995 14:09 | 34 |
|
Its getting closer...
The OpenVMS and Digital UNIX PCM T1.6-009 kits are now
available in:
OPG::CM$FTKIT:
Or, alternatively via anonymous ftp from:
elbrig.reo.dec.com in the ConsoleManager subdirectory
Changes for this release are lots of bug fixes in the console line
management code, along with the following new features/fixes...
o The editors now allow only one person write access to the database
at the same time, all other editors are started with read-only access.
o When removing an entity from the database, all other entities that
reference the removed item are updated e.g. if you remove system X
then it will be removed from all groups, filters and users that
reference it.
o When performing an archive, any other interfaces which may
be attached to the system being archived (e.g. WATCH) will be
notified and they will suspend their output.
o The C3 now has the ability to remotely login to the managed
system, we think this feature needs more work so we would especially
like feedback on this please.
Enjoy,
Phil
|
| 2.32 | T1.6-031 | OPG::PHILIP | And through the square window... | Mon Jun 12 1995 17:55 | 25 |
| Folks,
The PRE-SSB kit is now available, this one is T1.6-031
So, we need your bug reports NOW if they are to be fixed before we release.
Anyway, the kit is in the usual place, so I wont go through all that agaian.
Stuff you may be interested in for this release...
1) The C3 now allows you to put your systems network name in for the remote login
commands
2) The Startup has been COMPLETELY reworked, the ENS daemon is now started by
the main controller process and not seperately in the startup. Consequently,
if ENS dies you will get an OPCOM message (syslog on Digital UNIX) telling
you it has died. For those of you who like to play with unsupported features,
you can define the system wide logical CONSOLE$RESTART_ENS to be TRUE so that
if ENS dies, the daemon will restart it automatically for you.
3) All other known problems are fixed (Except your eventlist one Geert which we
are still trying to understand).
Enjoy,
Phil
|
| 2.33 | V1.6-100 | OPG::PHILIP | And through the square window... | Wed Jun 21 1995 12:52 | 40 |
| Folks,
We submitted the Digital UNIX PCM V1.6 kit to CSERL on Monday.
We submitted the OpenVMS (VAX and Alpha) PCM V1.6 kit today.
The Kit for PCM V1.6 is now available in either of the following
locations...
OPG::CM$KIT:
Anonymous FTP via elbrig.reo.dec.com in the Console_Manager directory
The files are called...
CONSOLE016.A thru .E (OpenVMS VAX and Alpha)
PCM_V16_OSF.TAR (Digital UNIX)
The images in these kits all announce themselves as Version V1.6-100 If you
have installed ANY release prior to this version, we highly recommend that you
upgrade NOW!!
Those of you who have let your customers have FT 1.6 kits should upgrade your
customers also, this kit is IDENTICAL in every way to what they will receive
on the next issue of consolidated distribution (JULY ownards) for each platform.
Any bugs in this software must now be reported via the official IPMT mechanism,
we will not investigate/fix bugs reported to us in any other way. We would
appreciate it if your customers DID NOT report bugs against this version until
they receive their official distribution via CONDIST or whatever they normally
have. This will help the CSC's for whom it will not have officially been released
until that time.
I would like to take this opportunity to thanks all those people who helped us
fix those nasty little bugs (Geert and Gerrit plus the few External FT sites).
A special thanks to Dan Butterworth in the Colorado CSC who put up with my stupid
questions and fixed many of the bugs for us while we were asleep in bed.
Enjoy,
Phil
|
| 2.34 | V1.6 ECO1 | OPG::PHILIP | And through the square window... | Mon Jul 17 1995 16:13 | 31 |
| Everyone...
The FT kit ECO1 for PCM V1.6-100 is now available for testing.
This kit will be submitted to DEC Std.204 on Friday so please
give it as much testing as possible.
This ECO will be the last remedial bugfix support that Simon
and I will be giving PCM, after this is submitted to DEC Std.204
support will be handled by our colleagues in Israel.
The kits can be had in the OPG::CM$FTKIT: directory. The release
notes in the kit are mostly there, they just need some last minute
items added when our documentation person is available
Enjoy.
Phil
Fixes not yet in the release notes...
1) The DIALOG SPEED command would enter an infinite loop with
SPEED set to values greater than 1000.
2) The API routine CMEventContextLine in Versions of PCM up to but
not including V1.6 used an event line number starting at 0, V1.6
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.
|
| 2.35 | V1.6 ECO1 | OPG::PHILIP | And through the square window... | Fri Jul 21 1995 14:57 | 22 |
| Folks,
The final kit for the ECO1 is now available.
The kit can be obtained from OPG::CM$KIT:
This is the last of the support work we in the UK will be doing
on PCM. All our equipment is being dismantled and shipped to our
colleagues in Israel. This notes conference will also be moving
soon along with the kit distribution location. We will advise
where this is moving to in the near future.
If you have ANY problems with PCM that you need resolving, then
please submit an IPMT case, this will be to your benefit as the
problem can be officially tracked and managed.
We also ask that you have a little patience as the guys in Israel
come up to speed, I am sure they will be making their presence
known in this conference in the near future.
Cheers,
Phil
|
| 2.36 | The Kits and Documentation have moved | OPG::PHILIP | And through the square window... | Wed Jul 26 1995 19:35 | 14 |
| Folks,
The kit and documentation locations have changed.
For All kits the location is now:
PCMSVR::CM$KIT:
For All documentation the location is now:
PCMSVR::CM$DOCS:
Cheers,
Phil
|
| 2.37 | ECO's and Docs are back online - scan profiles to follow | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Fri Jun 14 1996 12:46 | 21 |
| Folks,
I'm pleased to announce that the eco's and docs are back online:
Kits: CSC32::PCM$KITS:
Docs: CSC32::PCM$DOCS:
I would also like to point out that only the ECO's are kept in the kits
directory as V1.6 has been kept on CONDIST for a long time. Also, the
documentation, which is universal to all platforms, can be had off the
OpenVMS Condist. As of the June 96 CD it's on disk 5 and the directory
tree is
[CONSOLE016.DOCUMENTATION
and the kits are
[CONSOLE016.KITS]
Regards,
Dan
|