When we first upgraded from V2 to V3 we started having the same problem as
well as the problem of tapes being changed to 'unavailable' status.  Now
that we are at V3.1.1.5 we no longer have this problem.  One or two others
yes; but, not that one any more.

   Sandye J. Jackson
     sandye.jackson AT latimes DOT com
         Information Technology
     213/237-2132, fax 213/237-4500
  Are we having fun yet?

> -----Original Message-----
> From: Prather, Wanda [SMTP:PrathW1 AT CENTRAL.SSD.JHUAPL DOT EDU]
> Sent: Wednesday, February 03, 1999 1:34 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Orphan tapes in PRIVATE status
>
> ADSM V2.1.5.13 on AIX 4.2, STK9710 tape library
>
> I have just found a bunch of tapes in my library that are not defined in
> STGPOOLS or VOLHISTORY, but are marked PRIVATE instead of SCRATCH.
>
> We do not DEFINE any volumes to the STGPOOLS manually, all free tapes in
> the
> library should be in SCRATCH status.
> Library is dedicated to this one ADSM server.
>
> Many of these tapes I cannot find at all in the activity log (they could
> have been in this state a LONG time).
> But some of them I can see had mount failures:
>
> ANR9999D Mount error  xxxxxxx
> ANR1404W Scratch volume mount request denied - mount failed
>
> The mount failures occurred at different times for different tapes, and
> were
> all due to some explainable temporary problem with a drive or the tape
> robot.
>
> It looks as though when a mount fails for SCRATCH, ADSM is marking that
> tape
> as PRIVATE, even though there is no message to that effect.
> Can anybody confirm that is what really happens?
>
> Thanks.
> ***************************************************************
> Wanda Prather
> The Johns Hopkins Applied Physics Lab
> 443-778-8769
> wanda_prather AT jhuapl DOT edu
>
> "Intelligence has much less practical application than you'd think" -
> Scott Adams/Dilbert
> ***************************************************************