| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1329.1 | | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Thu Jun 20 1996 15:12 | 19 |
| >Hello,
>
> I would like to know how to save the contain of a multi-line window
> both on a screen and in a file in order to go back even if more
>than
> 1000 lines have been sent. We want also to make statistics
> (when the systems were up and down...)
All events are logged before any action routine gets them including
Multi-Line Window. In order to see them you can do:
$ CONSOLE EXTRACT/EVENT system-name
You also have /SINCE and /BEFORE qualifiers.
On Digital Unix the basic command is console -x.
Regards,
Dan
|
| 1329.2 | | SNOFS1::ELLISS | Are you all sitting too comfybold square on your botty? - Then w | Thu Jun 20 1996 19:36 | 10 |
| To correct Dan a little (I knew I'd be able to do it one day!), all
Console Manager events are logged before any action takes place. If you
are using events from external sources, such as PSW, then these will
not get logged if events are being directly pushed into ENS.
To get around this, OSCint has a history action which can be used to
log all events.
Shaun
|
| 1329.3 | write an action routine | DARGLE::COUGHLAN | | Fri Jun 21 1996 03:23 | 12 |
| Just to add my pennys worth.
The console extract event only applies to an individual system and is not
an option when managing several systems to view historical events which
are no longer in the multi-line window. You will have to write an action
routine which writes all events into a logfile. When an event occurs, have
it write to the logfile and run the multi-line window also. You can renew
the logfile at the appropriate intervals.
Regards
Dave.
|
| 1329.4 | | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Fri Jun 21 1996 14:46 | 34 |
| Re -2
> To correct Dan a little....
But I said in my reply
>All events are logged before action routine gets them including
> Multi-Line Window. In order to see them you can do:
So nyah-nyah-nyah-nyah-nyaahhhhh ;-}
Re -1.
>extract is not an option
I have to disagree. I see nothing bad about doing a console extract to
a file and then parsing it up. Your idea about writing an action
routine to log events to a file is a good one it's just kind of
redundant to have yet another event log file. Granted, I see this from
an engineers point of view.
Re all,
While we are at it, I gather from all of this there is a need for
some sort of reporting function. I would like to ask all of the PCM
user community for suggestions on what you'd consider the optimal
reporting function. We just might be able to squeeze this into the
development cycle. The first pass would be command-line only with the
ability to at least run it from the C3 . In other words, we wouldn't
have time to write a really nice Motif based report generator.
Regards,
Dan
|
| 1329.5 | Thanks | JOBURG::LUCOTTE | | Sat Jun 22 1996 11:39 | 9 |
| Thank you all.
At the beginning I was sure that this fuction was included somewhere
in PCM. But it seems not.
My customer wants to produce complete reports with the down-time for
each computer,list of performance problems sent by Performance advisor,
lists of errors by psw etc... to analyse and improve months by months
the global availabilty of the whole systems.
Regards, didier
|