Hi

I think you can also check on the Movebatchsize and Movesizethresh options
(q opt). I also heard of tuning the TAPEIOBufs according to the type of
drive you have, but I haven't used it before.

Regards,

Desigan Moodley
Arivia.kom
South Africa
? DesiganM AT Datavia.co DOT za


 -----Original Message-----
From:   Richard Sims [mailto:rbs AT BU DOT EDU]
Sent:   28 February 2001 02:59
Subject:        Re: Longlasting tape-reclamation run

>   my TSM-server 3.7.2 on AIX 4.3.3 runs a tape-reclamation  now for
>nearly 4 days.  Why does it last so long ?
...
>02/28/01   09:26:04      ANR1142I Moving data for collocation cluster 3608
>                         of 4248 on volume 000059.

Peter - What stands out in the above message is the very large number
        for total clusters (4248).  I typically see a number like 23
when I perform reclamations.  This is probably at the root of it.

I have yet to see a good definition, though, as to what a "cluster" is in
the TSM server context: the only manual that mentions it is the Messages
manual, and that explains it only as "data objects".  I'm wondering if
you have ended up with a large number of tiny files on the tape due to
a small TSM transaction size in client-server sessions (TXNBytelimit,
TXNGroupmax).  If your database size is modest, you can probably do a
Select on the Contents table and check the reported FILE_SIZE to check
what Aggregate size you are getting.  Regardless, no tape reclamation
should take 4 days.  You may want to check with Tivoli Support as to
what is going on.  If you do, and get some insights from them, please
share with the List.

  Richard Sims, BU