Reclamation is dependent on expiration and user deletions.

I have found that keeping reclamation at one number always ( 45% )  and
having Expiration triggered at one time each day causes tape reclamation
to occur shortly after expiration processing starts every day.

But a reclamation can also be triggered by a user that deletes his/her
filespaces completely.  (which requires the privilege)

So you may want to trigger reclamation by lowering the number from 100 down to
the number you like, about an hour or so after you trigger expiration.

    ... joe.f.

P.S>  some people see expiration and reclamation as real performance hits and
only trigger them on weekends but we run * VM * and I find a daily 'flushing'
works just fine and is not a performance hit since VM manages performance
between ADSM and all our users very well.

On Tue, 14 Oct 1997 08:30:12 -0400 David Wilshire said:
>Hi, fellow ADSMers!
>
>I'm trying to serialize my daily processing.  This involves expiring
>inventory, flushing my disk storage pool to tape, database backups, etc.
>
>After I expire my inventory, I check for any reclamation process that
>might have been invoked.  Finding none, I continue with my processing.
>Then, magically, a reclamation process may start!  This really screws up
>my job stream.
>
>What is it that tells ADSM to invoke reclamation?  How can I check for
>this?  How can I manually start a reclamation?
>
>Thanks in advance,
>David Wilshire, Systems Administrator
>LensCrafters, Inc.
>dwilshir AT lenscrafters DOT com
>"Knowledge Is Support"