ADSM-L

Re: Activity log filtering, ignorable messages, &c.

2006-04-26 13:31:45
Subject: Re: Activity log filtering, ignorable messages, &c.
From: "Allen S. Rout" <asr AT UFL DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 26 Apr 2006 13:30:14 -0400
>> On Wed, 26 Apr 2006 19:02:33 +0200, "Bos, Karel" <Karel.Bos AT atosorigin 
>> DOT com> said:

> Why not filter out any ANR????I messages (ignore) and focus on the
> ANR????W warnings to filter down. I would almost always report the E and
> D messages.


Well, I hadn't been thinking of these messages as a-prioiri classes.
I began this as a list of individual messages I'd decided weren't all
that interesting w.r.t.  the maintenance of the server; I didn't want
to ignore anything that I hadn't specifically considered, at least
momentarily.  So that's a good thought.


But as I consider it, there are plenty of -E messages which need to
get filtered, or at least shunted to the client admin.

04/25/06   03:23:49     ANE4037E (Session: 309358, Node: POWERPC.CNS.UFL.EDU)  
File '\\opers_sups\c$\Program Files\Tivoli\TSM\baclient\dsmsched.log' changed 
during processing.  File skipped.(SESSION: 30935)

though that's an ANE, not an ANR.

I haven't yet found a counterexample for the other side (i.e. a -I
message I think I want to see) ... Oh, here are a few:

04/25/06   12:35:55     ANR1440I All drives in use.  Process 5558 being 
preempted by higher priority operation. (SESSION: 660392)

04/25/06   15:50:31     ANR4553I Incremental database backup triggered; started 
as process 2639. (PROCESS: 2639)



- Allen S. Rout