If you know that a suspect file is being moved (reclaim, not backup
stgpool), use this command with the volser of the source tape:

query content VOLSER count=1 f=d

That will show you the node, file name, size, and a few other details on
the first file on the volume, which is the one being moved.

For with copied data (backup stgpool), use the target volser, and this
command JUST after the file finishes:

query content VOLSER count=-10 f=d

That will list off the last 10 files on the volume.  The file in question
may have already gotten out of the list of 10, so you can go higher, but
that's getting to be a lot of output.  And you can tell the size of the
file being moved from the "query process" output.

Nick Cassimatis

----- Forwarded by Nicholas Cassimatis/Raleigh/IBM. on 10/10/2008 01:38 PM
-----

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 10/10/2008
08:58:18 AM:

> [image removed]
>
> Re: Find clients which are sending large files.
>
> Richard Sims
>
> to:
>
> ADSM-L
>
> 10/10/2008 09:06 AM
>
> Sent by:
>
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> Please respond to "ADSM: Dist Stor Manager".
>
> Eric -
>
> File size (actually, Aggregate size) is in the Contents table - which
> is the worst of all TSM database tables to have to trawl.  If you
> must, do so with as fully qualified search as possible, to minimize
> sequential traversals.  An alternative would be to inspect tapes
> recently used by the suspect client, using the Query CONtent command,
> which is optimized for fast info retrieval.  From the TSM accounting
> records, you may be able to discern such clients by the number of
> backup objects being comparatively few relative to the amount of
> backup data.
>
>     Richard Sims