We are wrestling with a couple issue that maybe some one could shed some
light on....

1) We are seeing insufficient space in target copy storage pool message
but when you look at the non-collocated copy pool vols there are many
tapes with 0.1% with a filling status, so there should be sufficient
space. Right?  


2) We are also trying to maximize the usage of our onsite co-located
Tape Stgpools, there seems to be a fine line in setting Maxscratch too
high or too low.  When we set Maxscratch on the high side then TSM will
eat up tapes with 0.01% utilization  (Tape for each node - even if
there's still tapes allocated to that node that have plenty of free
space)  When we set Maxscratch too low then we get the insufficient
space errors on that stgpool.  

Is the Stgpool percent utilized an accurate gauge to go by, or does it
consider the available space on pending scratch also.  What do you do to
avoid eating too many tapes on a co-located tape pool, but not run out
of space?

This manual monitoring is a drag (even if we get daily reports on what
the Maxscratch is set to, how many vols actually allocated.)


Regards,

Charles