thanks Kent,  at least I've verified that I'm not going crazy and
imagining this stuff.  IF/WHEN you upgrade to 3.7.x let me know if it
changes behaviour on you.

Better yet let IBM know!  :-)  ... joe.f.

Joseph A Faracchio,  Systems Programmer, UC Berkeley


On Mon, 5 Feb 2001, Kent J. Monthei wrote:

> We also use ADSM 3.1.2.20 (for Solaris) with IBM 3494 Libraries and have
> observed behavior consistent with that described by Joseph in the original 
> email
> - an idle mount will be immediately dismounted if/when there is another mount
> pending and no other drive is available.  However, we also recently dropped 
> the
> mount retention from the default 60 minutes down to just 5 minutes.
>
> Under what scenarios (or rationale) does it make sense to force tapes to 
> remain
> mounted more than 5 minutes after a client backup session has completed?
>
> -Kent M., GSK
>
>
>
>
>
>
> joelf AT cac.washington DOT edu on 05-Feb-2001 19:57
>
>
>
> Please respond to ADSM-L AT vm.marist DOT edu
>
> To:   ADSM-L
> cc:    (bcc: Kent J Monthei/CIS/PHRD/SB_PLC)
> Subject:  Re: tape mount retention behaviour
>
>
>
>
> I thought it always worked this way.  At one time I was going to put in a
> request to have two mount retention times.  One for when there are no
> pending request for a drive and the other for when there are pending
> request.
>
> On Mon, 5 Feb 2001, Joe Faracchio wrote:
>
> > I recently upgraded from 3.1.2.20 to 3.7.2.0
> > and notice a very annoying behaviour.
> >
> > The system keeps an idle tape mounted for the full retention period
> > specified despite the pending mounts that are waiting.
> >
> > when / where will this be fixed???
> >
> > thanks ... joe.f.
> >
> > Joseph A Faracchio,  Systems Programmer, UC Berkeley
> >
>