I have several systems that have test oracle databases I need to archive
with great regularity. Because of the network interface, these systems
cannot drive my tape units at anywhere near efficient speed. As a
result, I run them into a disk pool and let this migrate to tape as it
fills.

How do I prevent these systems from going direct to tape if the disk
pool is full? These are test environments, and low priority - and the
original system is about 22 GB running through a 3.4 GB ADSM pool, so it
will fill from time to time. I *cannot* afford to have a tape unit tied
up for the length of time these systems will take to move an object to
tape.

My current 'technique' is to cancel the session when it goes to tape,
and let the retry process do recovery - but this is too labor-intensive.

Suggestions?

TIA

Tom Kauffman
NIBCO, Inc

kauffmant AT nibco DOT com