I migrated our W2K3 TSM server recently from 5.2.1.3 to 5.3.2.0 and I've
had to change the MAXSCRATCH parameter on our tape storage pools from 0
to some arbitrary number like 1000 because migrations, as well as backup
storage pool commands have been failing.  Any reason why this is?  Is 0
a valid MAXSCRATCH value in 5.3.2.0?  If not, any suggestions as to what
value I should set each of the storage pools to?
 
 
Mel Dennis