*  *  PROBLEM FIXED    *  *

        1 tape drive was "online" however a control block in TSM is
"goofed up" and will not use it. From an availability stand point TSM
always thinks he has this one drive available so he never drives the
pre-empt logic...however because of the "goofed up" control block for this
drive TSM cant use the drive. The drive had a problem 4 days ago, but I
haven't had an error reported for it since. The only indication I could
get of a problem with the drive is the following after I attempted to make
the drive OFFLINE or ONLINE...

ANR8798W Drive DRIVE3 in library 3494LIB is busy; some transactions may
fail.

        Of course because TSM thinks it is busy I can not delete paths
and/or the drive ..........Sooooo tomorrow I'll bounce my tsm server to
clean up the "goofed up" control block and all should be well.

        Thanks for the help Rich!

David R. Nicholson





Richard Sims <rbs AT BU DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
04/05/2005 07:39 AM
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: ANR8447E .. Mount failed even though several drives 
in "idle" status


Mount retention is pre-empted to gain access to a drive, providing that
no process or session is engaged to use the drive and media.
See that msg in http://people.bu.edu/rbs/ADSM.QuickFacts for reasons we
have experienced. Check your Devclass MOUNTLimit as the most common
cause, plus your Activity Log for accompanying messages.

   Richard Sims

On Apr 5, 2005, at 7:23 AM, David Nicholson wrote:

> All,
>
> TSM Server 5.2.4.0  (AIX 5.3)
> 3494 library w/ (15) 3590E
>
>         Suddenly (I think) I am getting a LOT of ANR8447E messages.
> A "q
> mount" shows several drives in an "idle" state. My mount retention is
> set
> to '3'.  I thought that the mount retention would be preempted if there
> was a need to mount  a new tape. Can someone confirm or deny this for
> me?
> I am finding if I manually "dismount vol xxxxxx" the problem goes away
> for
> a bit until I get several "idle" drives again.