Hi *SM-ers!
Please help me with this and take the time to read this request!!!!

We're having serious performance problems with our TSM database. Part of the
discussion with IBM is how expiration should perform.
A technical document on the TSM website stated that one should be able to
expire 3.8 million objects per hour. As soon as I referred to this document
("How to determine when disk tuning is needed") IBM removed it from their
site!!!!
Expiration runs at a speed of 140.000 objects per hour in my shop an I know
for sure that some of you are running at 3.8 million or more and I like to
prove this to IBM.

I'm begging for your help with this. I would like to ask you to issue the
following SQL statements on your TSM server(s) and send the output directly
to me: Eric-van.Loon AT klm DOT com:

select activity, cast ((end_time) as date) as "Date" ,(examined/cast
((end_time-start_time) seconds as decimal(18,13)) *3600) "Objects Examined
Up/Hr" from summary where activity='EXPIRATION' and days (end_time)
-days(start_time)=0

select pct_utilized, avail_space_mb from db

The first statement calculates your expiration performance (objects/hour)
and the second one lists your database size and utilization.
Thank you VERY much for sending me your statistics in advance, I REALLY
appreciate it!!!
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines


**********************************************************************
For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), 
its subsidiaries and/or its employees shall not be liable for the incorrect or 
incomplete transmission of this e-mail or any attachments, nor responsible for 
any delay in receipt.
**********************************************************************