Conference csc32::consolemanager

  I am trying to help a customer troubleshoot an ENS problem on an Ultrix system.
I know VCS and PCM on VMS reasonably well but I have very little Utlrix knowledge
and don't have PCM installed on an Ultrix system here. I believe the customer 
is running V1.1. What is the easiest way to verify this on an Ultrix system ?

Invoke the editor console -E ( The version is in the Header)

POLYCENTER Console Manager
Character Cell Editor Version V1.5-000
Copyright (c) 1994 Digital Equipment Corporation. All Rights Reserved
 


The problem they have is that ENS actions are not begin invoked as specified by 
the filters. The events are highlighted in the eventlist window so the events are
being detected. The customer has tried using a user defined action routine and a
supplied action routine (mail) without success. I have looked at the filter and
action routines from the character cell interface but they look O.K. I see in 
notes 170 that the environment variable CONSOLE_DEBUG can be defined to ENS. 
What information will that give ? Will there be any ENS log files created that 
can be checked ?


Hmm. This is slightly mopre tricky on ULTRIX than on VMS. The DEBUG on ULTRIX
was originally for debugging the software, and in this case we ran the daemon
and the ens daemon as interactive processes. It was then just a matter of doing
setenv CONSOLE_DEBUG ENS in the session which would be used to run ens.

If the customer is not happy to do this the best bet is to put a line in the
console_startup shell procedure which will do the assignment

In this case the output will go to /var/kits/console/tmp/console_ensd.log.


WARNINGS!!!!

  can easily use up a LOT of disk space doing this.

  The file will be deleted at the next PCM startup.

  I'm a C-Shell user the startup script is sh so beware. 

Cheers Simon...

Hope that helps

Simon,
     Thanks for the reply. They don't get any version number from console -e 
command but they use commands CM rather than CONSOLE so it must be an earlier
version than V1.5. In this verion would the environment variable be CM_DEBUG.
The customer can now get his action to DECmcc to work using a shell script that
runs his program but the ENS process dies afterwards to he has to restart PCM.
Do you know what might cause this ?

Thanks,

Geoff.

>Thanks for the reply. They don't get any version number from console -e 
command 

I said console -E!!!! The char cell editor Unix case sensitivity claims another
victim


>They use commands CM rather than CONSOLE so it must be an earlierversion than
>V1.5. 

No cm was kept for backward compatibility for this version only. It will NOT be
available in the next release. This is ULTRIX only!!!


>In this verion would the environment variable be CM_DEBUG.
>The customer can now get his action to DECmcc to work using a shell script that
>runs his program but the ENS process dies afterwards to he has to restart PCM.
>Do you know what might cause this ?


Send us:

1) export of config database
2) copy of shell script custome has written
3) Anything else which may be of use!!


Cheers Simon....
T

The '-e' was just a typo on my part using '-E' only gives him a copyright message
but no version number.

He is sending in an export of the configuration database and the action routine
used. He also claims the same happens if he uses a supplied action routine.

Thanks,

Geoff.

Geoff,
  If he gets no version number, he is running an OLD version of the 
  software and should really upgrade to V1.5 before going any further with
  this problem. 

Cheers,
Phil