I woke up early this morning, thanks to a call from our operators, so maybe
I'm too tired to think clearly enough to understand you.  Also, we currently
use only scratch tapes in our 3494, although we will be connecting it to
another ADSM server that's using stand-alone 3590 drives right now and I do
define volumes to the storage pools for this system.  Once I get that system
on our 3494 I will convert it from using defined tape volumes to using
scratch.

Can you explain what a tape would be used for if it's not scratch and not in
a storage pool?  I guess you could use it for a database backup or some
other command where you specified the volser.  Would I have to use mtlib to
change them to scratch if I wanted to?  Or use checkout libvol xxxxxx rem=no
followed by checkin libv ... status=scratch?

If this change comes out before I get my other server converted to scratch
tapes, then I'll be negatively affected by this.

> 5 - The only impact I see is those storage pool volumes
>     that were defined to the storage pool through the
>     DEFINE VOLUME command when they are deleted from the
>     storage pool would now remain in the private category
>     in the library inventory rather than being returned to
>     scratch.  This part I am not sure if it will have an
>     impact on customer automation scripts and is the piece
>     that I really need feedback on.  The volume will still
>     get deleted from the storage pool, it is only the
>     state of the library inventory (Scratch vs Private)
>     for this specific case that will change.
>
> Thanks - David Bohm
> ADSM server development
> (520) 799-5082 T/L 321-5082
> email - bohm AT us.ibm DOT com