On Nov 29, 2005, at 1:01 PM, Dennis Melburn W IT743 wrote:

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?

MAXSCRatch=0 has always been a valid specification; but it means to
disallow the use of Scratch volumes, as specified in the Admin Guide
manual. Where volumes were not then defined to storage pools, then
certainly storage pool operations needing output media space would fail.

   Richard Sims