We keep ActLogRetention, EventRetention and SummaryRetention at 37 days.
Reason:  we generate some monthly reports from those tables.  That gives
us a 6-7 day window to generate the reports, plus extra time to regenerate
them if something is amiss, and to allow for long weekends, vacations,
holidays, sick leave....

There  are alternatives - one good recent suggestion was to create an
admin schedule to frequently redirect/append the latest output of a 'q
actlog' (e.g. hourly, using begintime=-1 enditme=now) to an external file.
 Then you can shorten ActLogRetention substantially if you need to.

Kent Monthei
GlaxoSmithKline





"Mr. Lindsay Morris" <lmorris AT servergraph DOT com>

Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
20-Nov-2002 10:00
Please respond to lmorris AT servergraph DOT com




        To:     ADSM-L

        cc:
        Subject:        Re: Activity Log

If you're concerned about your activity log eating up too much space in
your
TSM database, don't be.  It uses relatively tiny amounts compared to the
contents table.  But there'e probably no good reason to keep more than 30
days.

---------------------------------
Mr. Lindsay Morris
Lead Architect, Servergraph
www.servergraph.com <http://www.servergraph.com>
859-253-8000 ofc
425-988-8478 fax


> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
> Nelson Kane
> Sent: Wednesday, November 20, 2002 9:44 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Activity Log
>
>
> Good Morning TSM'ers,
> Can someone tell me where the activity log maps to on the AIX side.
> I would like to expand the duration of the log, but I need to
> know how much
> is being utilized currently before I do that.
> Thanks in advance....
> -kane
>