You need to look at the SYSLOG around this time to see what the operating
system messages were. As far as ADSM is concerned, there were available
drives because he wasn't using them, but other jobs in the system could have
used the available drives and the operator was givin an allocation error and
cancelled the request. Another problem I have seen is that the library
inventory maintained by OAM (part of OS390) has the volume as a scratch
tape. The system will not allow you to request a volser for what he thinks
is a scratch tape. You may have to alter the volumes status in the library
using ISMF. If you don't have access, you may have to speak with the tape
librarian or system programmers about getting this resolved. You should also
check the tape management system to make sure that this volser is an ADSM
tape.

Bill Boyer
DSS, Inc.


> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
> Forrester, Benjamin S.
> Sent: Wednesday, November 17, 1999 11:22 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Storage media inaccessible in a 3494 library
>
>
> I am trying to move data from some suspect volumes in our library, but the
> move datas consistently fail. The accounting log gives me the following
> errors:
>
> 11/17/99   09:55:11  ANR8447E No drives are currently available in library
>                       LIB3494A.
> 11/17/99   09:55:11  ANR1401W Mount request denied for volume
> A00088 - mount
>                       failed.
> 11/17/99   09:56:25  ANR1144W Move data process terminated for
> volume A00088
> -
>                       storage media inaccessible.
> 11/17/99   09:56:25  ANR0985I Process 126 for MOVE DATA running in the
>                       BACKGROUND completed with completion state
> FAILURE at
>                       09:56:25.
> The problem is that there are available 3590E drives available
> when I issue
> the command, and issuing the move data command on a different volume works
> perfectly. Has anyone seen this before or have any ideas as to what is
> wrong? Is the data or the cart so corrupt that it cannot be mounted? Any
> comments or suggestions would be very helpful. We are at ADSM
> level 3.1.2.40
> and have the latest microcode for the 3590E drives. The following
> information is the detailed information on the volume I was
> trying to move.
>
> Thanks,
>
> Ben Forrester
> System Administrator
> University of Missouri - Columbia
>
>                    Volume Name: A00088
>              Storage Pool Name: BACKUPCART
>              Device Class Name: 3590
>        Estimated Capacity (MB): 10,240.0
>                       Pct Util: 15.6
>                  Volume Status: Filling
>                         Access: Read/Write
>         Pct. Reclaimable Space: 29.9
>                Scratch Volume?: Yes
>                In Error State?: No
>       Number of Writable Sides: 1
>        Number of Times Mounted: 13
>              Write Pass Number: 1
>      Approx. Date Last Written: 10/07/99   05:18:23
>         Approx. Date Last Read: 10/08/99   10:03:43
>            Date Became Pending:
>         Number of Write Errors: 0
>          Number of Read Errors: 0
>                Volume Location:
> Last Update by (administrator): DILLB
>          Last Update Date/Time: 11/16/99   23:49:28
>