Take care in using "remove=untileefull", you will have to reply to each tape
that it put in you I/O slot.

-----Original Message-----
From: PAC Brion Arnaud [mailto:Arnaud.Brion AT PANALPINA DOT COM]
Sent: Friday, August 16, 2002 8:55 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: LTO Bulk Reader filled....


Hi David,

You should get a rid of this problem by adding "remove=untileefull" in
your "move drm" statement !
Hope it helped !
Cheers.

Arnaud

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| Arnaud Brion, Panalpina Management Ltd., IT Group     |
| Viaduktstrasse 42, P.O. Box, 4002 Basel - Switzerland |
| Phone: +41 61 226 19 78 / Fax: +41 61 226 17 01       |
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=



-----Original Message-----
From: David Stabler [mailto:dstabler AT MORRISONHOMES DOT COM]
Sent: Friday, 16 August, 2002 14:59
To: ADSM-L AT VM.MARIST DOT EDU
Subject: LTO Bulk Reader filled....


I was using DRM to manage a copypool, and sent my "Vault" tapes to the
bulk reader.  I wasn't paying attention at the time, but I sent more
than 10 tapes.  The extra tapes were dutifully marked at the Vault, and
TSM lost track of them, but they were still in the LTO!  A key, and a
few minutes of scanning, found them, but it wasn't what I expected....

Is there any way in TSM to monitor, easily, how many tapes are to be
ejected, compare that to what, if any, tapes are already in the bulk
reader, and send only what can fit?  Or, error out for trying to do too
much?

I have written a rather nasty shell script that does a few selects,
picks a tape list, cuts off the top 10 tapes, and only sends those (one
at a time, rather than with any wildcards), but I'm wondering if I'm
using a sledge hammer on this finishing nail....

AIX 4.3.3, TSM 4.2.1.8

-drs-