I too see the same thing with ADSM 3.1.2.20. I have created a devclass of
reclaim-cache. When I begin reclamation a  migration task kicks off almost
immediately. However, it will wait and wait and wait for the disk file to
fill. In addition, it would like to mount the output volume while it waits!
Therefore, I set the devclass mountlimit to 1 to prohibit this. Problem is,
I can only run 1 reclamation process with this devclass!!  I haven't had an
opportunity to research this much. A Query Process just a few seconds ago
shows:

1,063 Migration            Volume ADSM.RECLAIM.CACHE.BTNC (storage pool
                               RECLAIM-CACHE-BTNC), Moved Files: 0, Moved

                               Bytes: 0, Unreadable Files: 0, Unreadable
Bytes:
                               0. Current Physical File (bytes): 55,369

                               Waiting for mount points in device classes

                               RECLAIM-CACHE and CARTRIDGE (3654 seconds).

   1,071 Space Reclamation    Volume R37594 (storage pool BACKTAPE_NO_COL),

                               Moved Files: 0, Moved Bytes: 0, Unreadable

                               Files: 0, Unreadable Bytes: 0. Current
Physical
                               File (bytes): 1,547,573

                               Waiting for mount of input volume R37594 (11

                               seconds).

                               Current output volume:
ADSM.RECLAIM.CACHE.BTNC.

Volume ADSM.RECLAIM.CACHE.BTNC belongs to devclass RECLAIM-CACHE. I have
reduced the mountlimit to 1 to keep the migration task from mounting an
output tape and waiting. It just hogs one more tape drive!

I would be interested in hearing what support tells you.


John G. Talafous                         Sr. Tech. Prog/Anal
The Timken Company                 Phone: (330)-471-3390
P.O. Box 6927                           Fax  : (330)-471-4034
1835 Dueber Ave. S.W.
Canton, Ohio USA  44706-0927
talafous AT timken DOT com                  http://www.timken.com/