> Is the data in an error state ?
> For  example, if a scratch tape is mounted and the volser can't be verified
> (read) the tape will be marked private to prevent further access.  This
> sounds like it could be your problem... try to read the label on the tape...
>
> "checkout libvol LIB VOLSER checklabel=yes"
> and see what you get...

...and in addition to all the other info, you can look at your
volumehistory file, to see if the volumes was ever in a storage pool.  On
unix, you could cat the volhist file, piping it to grep for that volume,
seeing all of that volumes' usage:

cat  /usr/lpp/adsmserv/bin/volumehistory | grep -i a00000
1999/11/23 06:24:35  STGNEW         0      0      0 3590COPY     A00000
2000/01/06 07:47:13  STGDELETE      0      0      0 3590COPY     A00000
2000/02/13 08:11:57  STGNEW         0      0      0 3590COPY     A00000
2000/03/27 15:32:53  STGDELETE      0      0      0 3590COPY     A00000
2000/03/28 04:36:24  STGNEW         0      0      0 3590PRIMARY  A00000

In this case, A00000 has been used several times in the stgpool 3590COPY,
but us now part of stgpool 3590PRIMARY.

As an aside, I have never trimmed any data from my volhistory files...

Steve Roder, University at Buffalo
VM Systems Programmer
UNIX Systems Administrator (Solaris and AIX)
ADSM Administrator
(tkssteve AT buffalo DOT edu | (716)645-3564 | 
http://ubvm.cc.buffalo.edu/~tkssteve)