Re: Activity log filtering, ignorable messages, &c.
2006-04-27 04:15:20
Hi,
ANR1440I will be followed by an ARN????E if there is something
(proces/job) cancelled.
ANE errors, changed during processing/file in use things should be
minimized by properly implementing incl/excl list. Generic incl/excl
statement in client option sets on the server. BA client specific
incl/excludes in de dsm.opt/sys of that client.
Regards,
Karel
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Allen S. Rout
Sent: woensdag 26 april 2006 19:30
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Activity log filtering, ignorable messages, &c.
>> 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
Disclaimer.txt
Description: Text document
|
|
|