When I had dedicated VTLs, I routinely ran with an arbitrarily large maxscratch 
value and used the amount of tapes defined as the limiting factor detect 
run-away situations. You don’t have to keep them synchronized in any particular 
manner as long as MaxScratch is larger. 

On Oct 9, 2014, at 5:54 AM, Loon, EJ van (SPLXM) - KLM <Eric-van.Loon AT KLM 
DOT COM> wrote:

> Hi Steven!
> So if I understand your explanation correctly, for a storagepool used by one 
> server only, the maxscratch should always be equal to the total amount of 
> volumes in this pool? So when adding new scratches, one has to raise the 
> maxscratch with an equal amount? 
> Kind regards,
> Eric van Loon
> AF/KLM Storage Engineering
>