Wouldn't it be nice if there were more categories. How about severity levels
1 thru 99 associated with the criticality of the error. Then we could turn
event logging on for the levels we want to see. Like query failures would be
a 5 and tapes going unavailable would be 80, so log everything above 70.
Thank You,
Stefan Dusedau
infoWorks
A Viacom technology service
(212)258-6739
stefan.dusedau AT viacom DOT com <mailto:stefan.dusedau AT viacom DOT com>
-----Original Message-----
From: Purdon, James [mailto:james_purdon AT MERCK DOT COM]
Sent: Wednesday, March 24, 1999 4:18 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: excess activity log msgs - v3
You've got it. Back under ADSM server version 2 I decided
to be a good
dobee and print out a daily error report. Now, thanks to
the inane "No
items match query" messages, this report excedes all
reasonable size and has
become pretty useless.
When I do a "query volume access=readonly" and get nothing
back, I'm happy -
so don't make me sad by logging it as an error. The same
goes for all my
queries against volumes or the library - I'm looking to see
whether
something is there or not. Just because it isn't there
doesn't mean its an
error.
Some good-hearted folks have suggested using a variety of
filtering
mechanisms to just see the messages that I want. Seems like
a lot of work
(and who knows what other tripe will get stuffed into the
activity log with
each new release of ADSM) just to make things the way they
used to be and
it misses the point. I want my errors to be errors - broken
tape drives,
bad tapes, running out of space, that sort of thing. A
query that doesn't
return any items just isn't an error.
Jim
> ----------
> From: Dwight Cook[SMTP:decook AT AMOCO DOT COM]
> Reply To: ADSM: Dist Stor Manager
> Sent: Wednesday, March 24, 1999 3:54 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: excess activity log msgs - v3
>
> Ya know... one of the largest quantity of errors that
shows up in my
> daily report of ANR????[E,S,D] messages are the ones
for "no items
> selected for query" (or what ever the wording is...)
> So if my report generator gets no E,S,orD messages on
any given day,
> the next day there will be at least one where the
previous day's
> query
> DIDN'T FIND ANY and that might be the only ERROR from
the previous 30
> hours AAARRRRGGGGHHHHH ! ! ! ! ! ! !
>
> Dwight
>
>
> ______________________________ Reply Separator
> _________________________________
>
> Subject: Re: excess activity log msgs - v3
> Author: PrathW1 (PrathW1 AT CENTRAL.SSD.JHUAPL DOT EDU) at
unix,mime
> Date: 3/24/99 2:36 PM
>
>
> The problem I have with all the extra messages coming to
the server in V3,
> is that one "q actlog" command generates 5 or 6
meaningless messages in
> the
> activity log. It doesn't add any information, and it
makes the task of
> finding the meaningful messages in the log much more
difficult.
>
> On the other hand, I do indeed understand and approve of
having an audit
> trail of administrator activity.
>
> What I would like to see, is the ability to EXCLUDE
administrator audit
> messages from a Q ACTLOG.
>
> Perhaps make Q AUDITTRAIL a separate command from Q
ACTLOG.
>
> Or for a more general solution, allow the user to create a
list of message
> numbers that are excluded when a Q ACTLOG is processed.
>
> What do you all think?
>
>
>
> > -----Original Message-----
> > From: Hilton Tina [SMTP:HiltonT AT TCE DOT COM]
> > Sent: Friday, March 19, 1999 8:40 AM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Re: excess activity log msgs - v3
> >
> > You can't disable server messages from the actlog,
though -- like the
> > messages saying someone entered 'q ac' or 'q pr'.
> >
> > > -----Original Message-----
> > > From: Dwight Cook [SMTP:decook AT AMOCO DOT COM]
> > > Sent: Thursday, March 18, 1999 11:01 PM
> > > To: ADSM-L AT VM.MARIST DOT EDU
> > > Subject: Re: excess activity log msgs - v3
> > >
> > > To issue this command, you must have system privilege.
> > >
> > > Syntax
> > >
> > > .-,-------------.
.-,--------------.
> > > V | V
|
> > >
>>-DISAble--EVents------+-ALL------+--+-----+-eventname-+--+---->
> > > +-CONSOLE--+
+-ALL-------+
> > > +-ACTLOG---+
+-INFO------+
> > > +-FILE-----+
+-WARNING---+
> > > +-SNMP-----+
+-ERROR-----+
> > > +-TIVOLI---+
'-SEVERE----'
> > > '-USEREXIT-'
> > >
> > >
>-----+-------------------------------+------------------------><
> > > | .-,-----------. |
> > > | V | |
> > > '-NODEname--=-----nodename---+--'
> > >
> > >
> > >
> > >
> > > ______________________________ Reply Separator
> > > _________________________________
> > > Subject: excess activity log msgs - v3
> > > Author: schirico at
unix,mime/DD.RFC-822=schirico AT WATERW DOT COM
> > > Date: 3/18/99 5:03 PM
> > >
> > >
> > > We upgraded to v3 recently, and now are excessive
message in the
> > activity
> > > log (i.e. everything
> > > that anyone does, query's etc.
> > >
> > > Does anyone know how to keep some of these messages
from going to the
> > log?
>
|
