|  | Marc,
  We deliberately didnt put this on either of the
  event list windows (the action or the C3) as the
  event context is available either by a single click
  on the event line in the C3, or selecting "Show Context"
  in the action routine. The rational behind this was that
  the information field should adequately describe the
  event in order to enable the user to understand the
  type of problem, then if further detail is required
  it can be requested. The further detail is potentially
  a time consuming operation, as the context of the event
  has to be retrieved by either the C3 or the eventlist
  action from the log files, and in the case of a long
  event may not have actually been flushed from the daemons
  internal buffers before the user requests it.
  Imaging 200 systems which each have an event, the C3
  (or event list action) would have to open each consoles
  log file and get the context of the event in order to put
  the line you require in the list box! (Its worse than this
  each console actually has 3 files)
  We will consider your comments for a future version, and
  see if we can do something to satisfy your need.
Cheers,
Phil
 | 
|  | Sorry ... I didn't read the doc carrefully enough
and didn't knew that by clicking on the event line in C3,
it was available.
This is ok for me and understand your remarks about
performance problems with 200 nodes.
Please consider .0 as obsolete and accept my apologizes.
Thanks,
Marc.
 |