Mountretention only looks at idle tapes.
A process/session requesting a tape should normally take over a tape resource
if it's idle, regardless.

This is a possible issue of the 8 legged variety.

Cheers, Suad
--
On Wed, Dec 05, 2001 at 11:22:11AM -0500, William Boyer wrote:
On Wed, Dec 05, 2001 at 11:22:11AM -0500, William Boyer wrote:
> Check the MOUNTRETENTION in the device class.
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
> Suad Musovich
> Sent: Wednesday, December 05, 2001 4:12 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: TSM 4.2.1.7 Upgrade-
>
>
> Upgraded to 4.2.1.7 (AIX) from 4.2.0.1 this morning and it went well. All of
> the
> old problems seemed to go away, but...
>
> I just had a wierd thing happen.
>
> We have 6 drives in our library and 5 drives in use (1 move data and 3
> backuppool
> migrations).
>
> Then the move data and one of the migrations gets cancelled by a "higher
> priority operation" requesting the tape drives. The thing was, there was no
> process
> or session wanting a tape drive, or the tapes.
>
> >From the 2 remaining migrations, 1 was operating normally and the other was
> "waiting
> for a mount point".
>
> A "q mount" showed there was 5 idle mounts. I had to manually dismount a
> tape to
> get it to recognise the free drive. The process has then requested and
> mounted a
> subsequent tape.
>
> Has anyone seen this one ?
>
> Cheers, Suad
> --
>
> On Mon, Dec 03, 2001 at 02:24:24PM -0500, David.Bean AT US.PM DOT COM wrote:
> > If upgrading on AIX:
> >
> > The migration as per documentation does not work and produces errors
> during
> > install:
> >
> > Tivoli.tsm.server.rte.config [388]: 27002 IOT/Abort trap(coredump)
> > Tivoli.tsm.server.webadmin.config[44]:17383 IOT/Abort trap(coredump)
> >
> > Tivoli recommended solution: remove backlevel lpps and re-install 4.2.x
> > level.
> > Hence it really is a 4.x install,  not a migration.
> >
> > License bug:  When registering licenses, they don't show up as registered
> > with a q license command
> > in TSM 4.2.0.  Recommendation is to upgrade to 4.2.1 (if client
> compatiblity
> > allows) and then
> > apply APAR.
> > -----Original Message-----
> > From: Dan Lee [mailto:Dan.Lee AT MUTUALOFOMAHA DOT COM]
> > Sent: Monday, December 03, 2001 1:48 PM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: TSM 4.2.1.7 Upgrade-
> >
> >
> > Looking for anyone who has upgradeed to 4.2.1.X or greater.
> >
> > We are upgrading this weekend and we would like any information that might
> > make the process go smooth
> >
> > Thanks
> >
> > Dan Lee
> > Associate Systems Programmer
> > Mutual of Omaha
> > I/S Midrange Services
> > 402-351-8377