[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference csc32::consolemanager

Title:POLYCENTER Console Manager
Notice:Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS:
Moderator:CSC32::BUTTERWORTH
Created:Thu Aug 06 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1541
Total number of notes:6564

632.0. "PCM and OpenVMS T6.2-FT2: No more console management..." by VELI::KORKKO (Veli K�rkk�, FNO/OMS Delivery, DTN 879-5512) Wed Mar 01 1995 09:08

Last evening I upgraded to OpenVMS T6.2-FT2 (from FT1). After this my PCM no longer
works. The startup fails due to some database problem...

In fact:

$ show logi console$Actions/Full
   "CONSOLE$ACTIONS" [super] = "CONSOLE$USER_ACTIONS" (CONSOLE$LOGICAL_NAMES)
        = "CONSOLE$SYSTEM_ACTIONS"
1  "CONSOLE$USER_ACTIONS" [super] = "CONSOLE$ROOT:[ACTIONS.USER]" (CONSOLE$LOGIC
AL_NAMES)
1  "CONSOLE$SYSTEM_ACTIONS" [super] = "CONSOLE$ROOT:[ACTIONS.SYSTEM]" (CONSOLE$L
OGICAL_NAMES)
$ dir console$Actions

Directory CONSOLE$ROOT:[ACTIONS.USER]

FM_PAGER.COM;10

Total of 1 file.

Directory CONSOLE$ROOT:[ACTIONS.SYSTEM]

CONSOLE$ARCHIVE_CLEANUP.COM;1           CONSOLE$BROADCAST.EXE;3
CONSOLE$EVENTLIST.EXE;3                 CONSOLE$EVENTSINGLE.EXE;3
CONSOLE$MAIL.COM;1

Total of 5 files.

Grand total of 2 directories, 6 files.

But still with 

$ cons edit/int=Char
POLYCENTER Console Manager
Character Cell Editor Version V1.5-006
Copyright (c) 1994 Digital Equipment Corporation. All Rights Reserved

PCM Edit> verify
Action 'Archive Clean-up' command 'console$archive_cleanup' not found in CONSOLE
$ACTIONS
Action 'Broadcast' command 'console$broadcast' not found in CONSOLE$ACTIONS
Action 'FM Pager' command 'FM_PAGER' not found in CONSOLE$ACTIONS
Action 'Mail' command 'console$mail' not found in CONSOLE$ACTIONS
Action 'Multi-Line Window' command 'console$eventlist' not found in CONSOLE$ACTI
ONS
Action 'Single-Shot Window' command 'console$eventsingle' not found in CONSOLE$A
CTIONS
...
6 verification warnings

And that basically is why PCM does not start any more. Since the change was OpenVMS
ft version, this basically means that QAR should be raised against them. Before that
I would like to know however, how PCM performs this particular verify step and why it
would fail? Using $SEARCH perhaps...


veli
T.RTitleUserPersonal
Name
DateLines
632.1OPG::SIMONWed Mar 01 1995 09:516
Veli,
     yes we did the same last night as we have been asked by OpenVMS eng to 
validate against V6.2. We had the same problem, so until further notice V6.2
is not supported, but we will work on it.

Cheers Simon...
632.2OPG::PHILIPAnd through the square window...Wed Mar 01 1995 11:068
Veli,

  This would appear to be a change of behaviour in the C-RTL stat function.

  I have QAR'd this, hopefully we will have this resolved soon.

Cheers,
Phil
632.3PCM does not work on OpenVMS T6.2-FT3 either!VELI::KORKKOVeli K�rkk�, FNO/OMS Delivery, DTN 879-5512Thu Apr 13 1995 16:0818
Phil,

I have upgraded my workstation to T6.2-FT3 and still no joy. PCM does not work.
CONS EDIT/INT=CHAR and VERIFY still reveals:

PCM Edit> ver
Action 'Archive Clean-up' command 'console$archive_cleanup' not found in CONSOLE
$ACTIONS
Action 'Broadcast' command 'console$broadcast' not found in CONSOLE$ACTIONS
Action 'FM Pager' command 'FM_PAGER' not found in CONSOLE$ACTIONS
Action 'Mail' command 'console$mail' not found in CONSOLE$ACTIONS
Action 'Multi-Line Window' command 'console$eventlist' not found in CONSOLE$ACTI
ONS
Action 'Single-Shot Window' command 'console$eventsingle' not found in CONSOLE$A
CTIONS
...

So, have you had any response to your QAR?
632.4YOSSAM::PHILIPAnd through the square window...Thu Apr 13 1995 16:1415
Veli,

  You will have to wait for PCM V1.6 for a supported version to run
  on OpenVMS V6.2.

  The result of the QAR was that the stat() function was changed in
  order to comply and behave just like its equivalent on Digital UNIX and
  other "Open" platforms. It turns out that our use of it was not standard
  and we were just lucky it worked. I have reworked the 5 ines of our code
  which caused the problem, however, this will not appear until we release
  V1.6

Cheers,
Phil