>We've recently seen a jump in our DB % Utilization after we had been at
>a constant level for months.  We have added new nodes and removed older
>nodes that they replace.  Our server is not new either; it has been in
>production since July 1999.  What I was wondering is if there is a good
>way of cleaning up this DB or possibly just figuring out what it is that
>is creating this recent jump in size?

An often asked question.  The most succinct way to see what is newly added
to your TSM storage pools is via the TSM accounting records.  Summarized,
they tell you exactly where the activity is, in terms of number of objects
and size.  (Ideally, you should be running such reports on a regular basis,
to be aware of surges.)  A further technique is to do Query Content with a
negative count on recently updated tape volumes.  See also "Database
consumption factors" in http://people.bu.edu/rbs/ADSM.QuickFacts .

You "clean up" the db only by eliminating unnecessary objects, via
expiration and obsolete filespace removal.

   Richard Sims