One of our customers run a cron job every four hours that dumps the 
activity log to disk using SQL statement "select date(date_time) date, 
time(date_time) time, msgno, process, session, message from actlog where 
date(current_timestamp)=date(date_time) and 
cast((current_timestamp-date_time) hours as integer)<4". Results are 
analysed in batch and archived (with delete) automatically to TSM on a 
daily basis. 

Works much faster than "q actlog". And makes it easy to minimize space 
used by the actlog in TSM - by now, only 7 days are kept online and the 
customer thinks about reducing it again...

regards
Ullrich

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
- - - - - - - - 
Ullrich Mänz
System-Integration

FRITZ & MACZIOL Software und Computervertrieb GmbH
Ludwig Str. 180D, 63067 Offenbach, Germany

Mobil:
+49 170 7678434
Fax:
+49 69 38013500 10
Web:
http://www.fum.de

Amtsgericht Ulm, Handelsregister-Nummer: HRB 1936
Geschäftsführer: Heribert Fritz, Oliver Schallhorn, Frank Haines
Inhaber: Imtech N.V., Gouda, Niederlande
Referenzen finden Sie auf unserer Website, Rubrik 'News'.



Von:    James Choate <jchoate AT CHOOSES1 DOT COM>
An:     ADSM-L AT VM.MARIST DOT EDU
Datum:  18.11.2011 17:07
Betreff:        Re: [ADSM-L] TSM 5.5 actlog size..
Gesendet von:   "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>



Upgrade to 6.2.3.  Much faster :)

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Ajay Patel
Sent: Thursday, November 17, 2011 1:35 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] TSM 5.5 actlog size..

Hi,

On one of  my tsm server Activity Log Size: 3,742 M  so it is very
difficult to get information from actlog - response time for 24 hour is
too high and if we query for more then 24 hr then not sure on output...

Could you please suggest  the solution without touching retention period
?.. TSM server version - 5.5 .4.3 on AIX


Regards,
Ajay Patel