T.R | Title | User | Personal Name | Date | Lines |
---|
1296.1 | | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Tue May 14 1996 15:42 | 6 |
| Steve,
Your not doing anything wrong. Install ECO 2 and you should be all
set.
Regs,
Dan
|
1296.2 | Its working. But.... | CHEFS::HATT | Wait a minute you're not Miss Jackson......! | Fri May 17 1996 09:49 | 19 |
| Dan,
Thanks - ECO 2 installed and edit function now ok.
However...
I now have a problem with the events screen (probably there before ECO
put on). What I do is create a detached process to run the C3 screen
and this creates the Events screen. When I do this from the PCM_USER
a/c (with the settings in base note), I get the windows but events in
the Events window are just displayed as the search string. eg I see
%DECFM-I*^ instead of %DECFM-I-TEST, This is a test message If I then
double click on the event (to see the context) the events window
disappears. If I look in the log created from the detached process
there is a stack dump.
Is this a known problem? I can post the stack dump etc if you need
to see it.
Thanks,
Steve
|
1296.3 | | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Mon May 20 1996 16:50 | 19 |
| > I now have a problem with the events screen (probably there before
>ECO put on). What I do is create a detached process to run the C3
>screen and this creates the Events screen. When I do this from the
>PCM_USER a/c (with the settings in base note), I get the windows but events
>in the Events window are just displayed as the search string. eg I see
> %DECFM-I*^ instead of %DECFM-I-TEST, This is a test message If I
>then double click on the event (to see the context) the events window
> disappears. If I look in the log created from the detached process
> there is a stack dump. Is this a known problem? I can post the stack
>dump etc if you need to see it.
I'm assuming you mean the Evenlist application (aka Multi-Line Window)
when you say "Events screen". The problem you are seeing is not a bug.
Your unable to read the console logfiles and this is probably due to a
file or directory-protection problem. The username the process is
running under has to have read access to the logfiles.
Regs,
Dan
|