ADSM-L

Tape Drive contention

1998-12-17 11:35:48
Subject: Tape Drive contention
From: Carol Trible <trible AT VNET.IBM DOT COM>
Date: Thu, 17 Dec 1998 08:35:48 PST
> What would happen in the event of a situation like the following:
> 1.An OS/390 system has 2 3590 drives
> 2.An ADSM server on the system has a device class for 3590 drives with
> a
>   MOUNTLIMIT of 2
> 3.Batch jobs unrelated to ADSM start using both 3590 drives
> 4.ADSM starts a process that requires a 3590 drive

ADSM will attempt to get the number of drives it is allowed in the devclass
using dynamic allocation.  in this case, since there is a mount limit of 2, and
none have been requested, ADSM will try to allocate a drive. The allocations
will retry for awhile, then an ANR5373 message will be issued, and the operator
will have a chance to reply, R (retry), C (cancel) or W (wait). If you are not
a the latest service level, there may be some differences in the response,
because there have been some fixes in this area.

In this case, if ADSM already was using 2 drives, then it would wait for a
mount point (wait till it was finished with one of the drives).

Carol Trible
ADSM Development
<Prev in Thread] Current Thread [Next in Thread>