Consider the possibility that you are not expiring well enough, which
could be causing database bloat. (Not to mention tape storage pool
bloat.) How long does your expiration process take? Does it seem to
never end? If so, you may be in an expiration bound death spiral.

If you are having trouble with expiration as it is, you are in no
position to take on an additional large client system, as was the start
of this thread. Dramatically lengthening expiration process run times
are a true sign that a TSM server is out of gas, and needs an upgrade
just for its present workload, not to mention adding more work to it.

Roger Deschner      University of Illinois at Chicago     rogerd AT uic DOT edu

On Tue, 30 Jul 2002, Todd Lundstedt wrote:

>Well, well.. I totally read my book the wrong way.  I will go recalculate.
>Thanks for pointing out this huge error on my part.  Now I have to go
>figure out where the rest of my database utilization is going, too.