I heartily agree with Richard's note about using the ACCOUNTING (not the
activity) log.

We tried several things with Servergraph, and found that:
   -- activity log messages are sometimes erroneous
   -- summary table data is sometimes unreliable
   -- frequent queries against these tables can impact the TSM server's
performance.

Servergraph uses the accounting log extensively for these reasons.  Rock
solid data there,
because it's written by the TSM server, not by the client software.

-----------------------------
Mr. Lindsay Morris
Lead Architect
www.servergraph.com
512-482-6137 ext 105

> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
> Ted Byrne
> Sent: Tuesday, May 04, 2004 9:16 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: TSM DB growing, but number of files remains the same ...
>
>
> Arnaud,
>
>
> >I believe what I have to do now is to build some solid queries to explore
> >our activity
> >log...
>
> Unless I'm mistaken, I believe that you may have misread Richard's
> advice.  (Correct me if I'm wrong, Richard.) His recommendation:
>
> >I stress accounting log reporting because it is the very best,
> detailed handle
> >on what your clients are throwing at the server
>
> Accounting log records are comma-delimited records written to a flat file
> called dsmaccnt.log, assuming that you have accounting turned on.  If you
> don't, I would recommend that you turn it on now...
>
> The accounting log records give a very detailed,
> session-by-session picture
> of the activity between the server and clients. It will be easier to parse
> and process than what you can get out of the activity log.
>
> Ted
>