This sounds like APAR IC32821, which is fixed in TSM 4.2.2.0. I
have heard that it is also being retrofitted in 4.1.x, but it is not
available yet. This APAR talks about "Sequential volumes may become
inaccessible because they may be inadvertently be left in "in use" status,
preventing them from being used further. A bypass for this is to restart
the TSM application."



At 04:16 PM 5/16/2002 -0700, you wrote:

Fred Thanks , Here are the OS and TSM
information-----------------------------------------------------------------
------------------------------------------------------------------------

OS                             Aix  4.3.3.0

Storage Management Server for AIX-RS/6000 - Version 4, Release 1, Level 4.0

----------------------------------------------------------------------------
-----------------------------------------------------------------

----- Original Message -----
From: "Fred Johanson" <fred AT MIDWAY.UCHICAGO DOT EDU>
To: <ADSM-L AT VM.MARIST DOT EDU>
Sent: Thursday, May 16, 2002 12:53 PM
Subject: Re: Mount request denied


What version and what OS?  We have seen this sporadically with 4.1.4.5 on
AIX 4.3.3.  Some days the only way to get out of it is to recycle the
machine.


At 02:50 PM 5/16/2002 -0700, you wrote:
>
>Error Messages (TSM on AIX Server)
>
>05/15/02   06:41:44      ANR1401W Mount request denied for volume 400142 -
>mount  failed.
>
>05/15/02   06:41:44      ANR1401W Mount request denied for volume 400219 -
>mount  failed.
>
>
>
>05/15/02   06:52:52      ANR1404W Scratch volume mount request denied -
>mount failed.
>
>05/15/02   06:52:52      ANR0525W Transaction failed for session 4459 for
>node
>
>                           NT_COMP_S1111131 (WinNT) - storage media
> inaccessible.
>
>
>
>
>
>
>
>I have done thefollowing tasks.
>
>7         checked the volumes which got error message in the log  are in
>the library with readw status for private.
>
>7         NO changes to devclass or in TSM.
>
>7         There are enough scratch volumes are available in the library.
>
>7         We had a problem with the griper last week and IBM Support Fixed
>that and we start getting such problem after that but Hardware support
>person has not upgrade or de-grade any micro -code on 3494 system or 3590
>drives.
>
>7         At this point Library and drives are working fine
>
>7         In a later session I tried to move the data and it worked fine.
>
>7         After the failed messages, Most of the time process or schedules
>get completed successfully.
>
>7
>
>This causes restore/retrieves/reclamation/migration to fail, rather than
>queue, until a drive becomes available (nothing mounted.
>
>
>Some time the failed restarted process works fine.
>
>
>
>
>
>I also found in a later try that all drive were idel  and migration failed
>with the following error message
>
>05/16/02   12:37:36      ANR8447E No drives are currently available in
>library  ATL3494.
>
>05/16/02   12:37:36      ANR1401W Mount request denied for volume 400491 -
>mount failed.
>
>05/16/02   12:37:36      ANR0985I Process 1478 for SPACE RECLAMATION
>running in the
>
>                           BACKGROUND completed with completion state
> FAILURE
> at  12:37:36.
>
>05/16/02   12:37:36      ANR1081W Space reclamation terminated for volume
>400585 storage media inaccessible.
>
>
>
>tsm: AIX_ADSM_SERVER>q
>mo
>
>ANR8329I 3590 volume 400068 is mounted R/W in drive 3590E_RMT5
>(/dev/rmt5), status: IDLE.
>
>ANR8329I 3590 volume 400159 is mounted R/O in drive 3590E_RMT6
>(/dev/rmt6), status: IDLE.
>
>ANR8329I 3590 volume 400796 is mounted R/W in drive 3590E_RMT3
>(/dev/rmt3), status: IDLE.
>
>ANR8329I 3590 volume 400034 is mounted R/O in drive 3590E_RMT0
>(/dev/rmt0), status: IDLE.
>
>ANR8329I 3590 volume 400095 is mounted R/O in drive 3590E_RMT4
>(/dev/rmt4), status: IDLE.
>
>ANR8329I 3590 volume 400600 is mounted R/O in drive 3590E_RMT2
>(/dev/rmt2), status: IDLE.
>
>ANR8334I         6 volumes
>found.
>
>
>
>
>
>
>
>
>
>
>
>
>Any idea why this is happening.

Money is not the root of all evil - full backups are.