Space reclamation is based upon a threshold. Just because the threshold is reduced doesn't mean active sessions are cancelled. If you want to cancel the session issue a cancel process command against the process ID.
-- Joshua S. Bassi IBM Certified - AIX 4/5L, SAN, Shark eServer Systems Expert -pSeries HACMP Tivoli Certified Consultant - ADSM/TSM Cell (415) 215-0326 [EMAIL PROTECTED] -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of Halvorsen Geirr Gulbrand Sent: Thursday, August 01, 2002 2:15 AM To: [EMAIL PROTECTED] Subject: Space reclamation of copypool 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
