You shouldn't need to configure anything other than the retention policy for these savesets. Once they have passed their retention date (and there is no dependant savesets) then the savesets will be deleted automatically from the AFTD. If this is not happening fast enough and you want to force it to be deleted in your test environment, you can run the commands nsrmm -d -S [ssid] - to delete the saveset from the medai-db and nsrim -X to have all expired or deleted savesets physically deleted from the AFTD.
Hi Michael I agree with bobby that Once the savesets have passed their retention date (and there is no dependant savesets) then the savesets will be deleted automatically from the AFTD and the space reclaimed.
Additionally if this is not happening you may also use : nsrstage -v -C -V The advantage with -C option is that you dont have to stage the data to another pool. A brief description for -C syntax is as follows:
-C = Instructs nsrstage to perform a volume cleaning operation. Scans a volume for save sets with no entries in the media data base and recovers their space. Space for recyclable and aborted save sets are also recovered from the volume with the save set entries removed from the media data base. You can perform this operation on adv_file and file type volumes.
coganb
736 Posts
606
0
Posted July 23rd, 2010 02:00
Hi,
You shouldn't need to configure anything other than the retention policy for these savesets. Once they have passed their retention date (and there is no dependant savesets) then the savesets will be deleted automatically from the AFTD. If this is not happening fast enough and you want to force it to be deleted in your test environment, you can run the commands nsrmm -d -S [ssid] - to delete the saveset from the medai-db and nsrim -X to have all expired or deleted savesets physically deleted from the AFTD.
-Bobby