I had the same problem and offsitereclaimlimit=20 (or whatever you want
to limit it to) worked for me.
In my particular situation my server is 5.4.1.0 (I know, very old!)
running on AIX 5.3 (5300-09-01-0847). I have a few (less than 5-10)
tapes at a 99% reclaimable level in my offsite COPYPOOL01
I had a similar situation with this error. I contacted IBM support on
this and they told me that this message can sometimes be encountered if
you are using client compression and going to a disk pool. I don't
remember the exact details, but the idea is that TSM estimates how much
of the disk
I just did this on a TSM server at 5.4.1.0 level.
It seems to work fine, but I found a couple of operational limitations.
I normally have a TAPEPOOL01 and a COPYPOOL01 storage pools that I use
for tape copies. DISKPOOL is set to go to TAPEPOOL01.
I was going to just change the TAPEPOOL01
I had a similar problem after I migrated from TSM server ver 5.2 to 5.4. The
pre and post script programs contained the - as part of their name, which
worked in 5.2 but broke in 5.4. I'm not sure about the _ character, but you
may want to rename the pre and post files to eliminate special
I have a short server command script that changes the reclamation
setting and then immediately resets it back, in order to start a
reclamation process for any tapes that are over the threshold.
When I run the two commands manually, there is enough time between them
to allow a reclamation
