My server is AIX at PTF 12.
When this situation happened to me, I did just what you said.
I changed the properties for that volume back to read/write, and ADSM
started writing to it again.
Don't know why yours didn't.

> ----------
> From:         Booher, Joelle M[SMTP:jmbooher AT amp DOT com]
> Sent:         Tuesday, August 26, 1997 10:36 AM
> To:   ADSM-L AT vm.marist DOT edu
> Subject:      Tape in FILLING status
>
> Just a simple question...
>
> Somehow my DLT tape got switched to write protected.  When ADSM tried
> to
> write to the tape, it detected read/only, set the access to read/only
> in
> the database, asked for a scratch tape and kept on going.
>
> I manually set the access back to read/write, thinking that ADSM would
> go back and use that tape, but it has since asked for yet another
> scratch tape which leads me to believe that this volume is going to
> sit
> forever with a small amount of data on it.  Also, I assume it will
> never
> reclaim since the status never went to full.  When I query the volume,
> it's only 32% full, and the status is still FILLING.
>
> I know that I can do a move data - that's OK in this case, but these
> are
> 15Gb tapes.  What if this had happened when it was 70% full?  The move
> data would take forever!  Does anyone know of another alternative?  Am
> I
> missing something?
>
> Thanks,
> Joelle Booher
> Amp Incorporated
> (717)810-2816
> jmbooher AT amp DOT com
>