Operations which refer to data in storage pools, i.e. move data, migration,
reclamation, backups (which go directly to tape) and restores (from tape), as 
well
as database backups (and exports/imports, I suppose) all allocate tape drives
through a device class via mount points, which are limited by the mount limit of
the devclass.  Operations which are only concerned with the label, i.e. label 
libv,
checkin libv, checkout libv, and move drm wherest=mountable (effectively runs a
checkout) all grab a free tape drive of the right devtype, bypassing the mount
point mechanism. It would appear that the server locks out the allocation of new
mountpoints in devclasses of the same devtype as required for the checkin/out.

Cheers...
Bruce

> Date:    Tue, 9 Jun 1998 09:18:17 +0200
> From:    Eric van Loon <evanloon AT KLM DOT NL>
> Subject: No restore possible during MOVE DRMEDIA
>
> Hi ADSM-ers!
> This morning I tried to do a restore. All the Win95 GUI was giving me was
> 'preparing...'. Nothing was happening.
> I checked the activity log and saw that the MOVE DRMEDIA was running and
> waiting for a tape to be removed (by our operator, who wasn't there yet)
> from the I/O slot.
> When I canceled the MOVE DRMEDIA process my restore was started immediately!
> Question: why isn't my restore started? The MOVE DRMEDIA command uses just
> one drive to verify the tape label, so one drive is available for my
> restore. Also, the MOVE DRMEDIA process is waiting for a reply with the tape
> in the I/O slot, so in fact both drives are available!
> Thank you very much for any reply in advance!
> Kindest regards,
> Eric van Loon
>