| > My customer has Excusrions running in order to get the Multiline
> Window, then in the evening when they call it a day they shutdown
> Excusrions with PCM still running (apparently this is possible, but I
> don't know Excursions that well to know its clean down procedure) and
> all appears to be o.k,
Excursion runs on the PC and provides an X-windows server for X clients
(such as Multi-Line Window) to send a display to. The point here is
that there is no association between PCM and Excursion so the act of
shutting down Excursion has no effect on PCM's ability to run. The
only side effect will be that ENS can't send the Multi-Line Window to
the PCM because the X-server on the PC has been shutdown.
>but then when they create another Multiline
>Window after starting Excursions they don't get any responce on the
>PC and they have checked the Console Status Failed Actions field which
>clocks up about 8000 failures and the only way of resolving the problem
>is to restart PCM.
How is the customer doing this ->"but then when they create another Multiline"
Are they issuing a CONSOLE EVENTLIST command while logged into the PCM
engine or are they letting ENS create it via a filter or both. The fact
that you have 8000 failed actions indicates that there is at least one
filter setup to send the Multi-Line Window to the PC. What you can do
is DEFINE/SYSTEM CONSOLE$DEBUG "ENS,ACTIONS", restart PCM and then do
some tests to reproduce the problem. You will find some logfiles in
CONSOLE$TMP that should give us an idea of what error status is
occurring when PCM attempts to send the Multi-Line Window. I would not
leave these logicals on overnight as you could comsume a lot of space
with those logfiles.
Regards,
dan
|