Besides making rec=100, you have to cancel the
process.
Here is an example using a shell script:

   dsmadmc -id=your _id -pa=your_pa q pr | grep -i
"space reclamation" > $tmpdir/process9
   if test -s $tmpdir/process
   then exec 5<$tmpdir/process
        read -r -u5 line
        proc=${line%%Space*}
        comma=`echo $proc | grep "," | wc -l`
        if [ $comma -eq 0 ] ; then
           process=$proc
        else
           process=${proc%%,*}${proc##*,}
        fi
        print $(date) "Cancelling TSM process $process
on $server ..." >> $maste
rdir/master.log
        dsmadmc -id=your _id -pa=your_pa cancel pr
$process>>$tmpdir/end_space_reclaim.log
   else print $(date) "No space reclamation processes
found on $server." >> $mas
terdir/master.log
        continue
   fi



--- Halvorsen Geirr Gulbrand <gehal AT WMDATA DOT COM> wrote:
> Hello everyone,
> I have the following problem with Space Reclamation
> of my copypool.
> To start reclamation I have a script running UPDATE
> STG COPYPOOL RECLAIM=50
> Three hours later, I run another script to stop
> reclamation - UPDATE STG
> COPYPOOL RECLAIM=100
> but reclamation never stops. This affects all of my
> daily operations
> (migration, backup stgp..) because the
> reclamation process uses both drives.
> Question is, why does space reclamation not stop
> after updating?
> Is there a way of canceling the process (by TSM
> script)?
>
> Best regards
> Geirr G. Halvorsen


=====
<P>Thanks,</P>
<P>Manuel J Sanchez</P>
<P>Senior UNIX SA</P>
<P>Assurant Group</P>
<P>(305) 252-7035 x32153</P>

__________________________________________________
Do You Yahoo!?
Yahoo! Health - Feel better, live better
http://health.yahoo.com