You can 'exercise' the archive data all you want, but the original request
was using backupsets, and these you don't 'exercise' with reclamation or
even move data commands. Like that guy on the Info-mercials says ... "Set it
and forget it!".

With archiveing vs. backupsets, you can always move the archive data to
another storage pool with more up-to-date equipement. A backupset is here to
stay. No way to move it, and not even a way to re-build it. That 'snapshot'
of the node/filespace is gone the next time a backup runs against it.

Maybe sending the backupset to a FILE device class, then turning around and
ARCHIVING those file back into TSM. Now it's an ARCHIVE object you can play
around with.

Just rambling....it's been a long week today!
Bill Boyer
DSS, Inc.