| Paul,
> We are monitoring a number of systems; some messages from some systems actually relay the status of other systems that we are also monitoring.
> We capture these events and use an action routine to "retarget" them to
> the system to which the message applies. Is there any way in which we
> can exclude the initial event from the event list window? Ideally as
> well is it possible for these events to be prevented from affecting the
> icon of the first system?
>
The only thought that comes to mind is to look into using the Filter
option in the Event list 'Options' pulldown menu. I think you will have
to get the event before you can exclude it. It's a bit primative, but
it might help you to achieve your goal.
>Secondly, we get the status of all these systems by sending an
> appropriate command to one of these systems which then relays the
> status of all these systems (which we then "retarget" as above). We
> would like to send this command out whenever a user starts a C3
> window so that their display reflects the current application status.
> Is there any way of achieving this?
Can you put the 'Console C3' command into a command procedure/shell
script which in turn would generate a console (retargeted) event?
You users would then have to execute this command procedure instead of
starting up the C3 directly.
Dave
|
| > We are monitoring a number of systems; some messages from some systems
> actually relay the status of other systems that we are also monitoring.
> We capture these events and use an action routine to "retarget" them to
> the system to which the message applies. Is there any way in which we
> can exclude the initial event from the event list window? Ideally as
> well is it possible for these events to be prevented from affecting the
> icon of the first system?
You would have to create an event preprocessor that ENS would call
before putting the even through "normal" processing. It is the ENS
daemon that actually sends events onto the C3 and Monitor interface.
In the "normal" case when an event is seen from a system that event
is sent to any C3 or Monitor interfaces and inthe case of the C3 the
icon color is changed etc. When ENS hands if off to your action
routine that retargets the event then I assume that that systems icon
also changes color?
If you create an event preprocessor, you can determine via the
preprocessor if you want to pass the event back to ENS unmolested, or
if you want to change the characteristics of the event and then send it
back. In fact, if your event text contains the name of the system that
you are going to "retarget" to, you could change the system name right
there and then pass the event bak to ENS and elimate the retartgeting
the action rotuine. By changing the event and then passing it back you
achieve *exactly* what you want to do.
>Secondly, we get the status of all these systems by sending an
>appropriate command to one of these systems which then relays the
>status of all these systems (which we then "retarget" as above). We
>would like to send this command out whenever a user starts a C3
>window so that their display reflects the current application status.
>Is there any way of achieving this?
Dave's idea in -1 sounds like a good idea.
Regards,
Dan
|