Not really an answer, set max file size of primary pool to 1GB and force
it to a next large file pool.  Check what files ends up in the large
file pool. 

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Richard Sims
Sent: Tuesday, April 21, 2009 10:43 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Object size query

You can produce an allied report by scanning your dsmaccnt.log to
report on large adds (Archive or Backup operations) over a long period
of time, by dividing quantity of data sent to the TSM server by the
number of objects, allowing you to identify nodes and users (but not
filespaces) involved in biggies.  This alone may be sufficient for
your needs; or you might use it to perform a more limited Select on
formidable tables.

    Richard Sims