One time when we wanted to find out what a change to RETONLY would
accomplish, I restored
a TSM db to a test server, changed the policy, ran expiration, then checked
the occupancy.  I don't
know if this was right, but it provided some numbers to play with.

Rick


"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 08/15/2008
10:14:03 AM:

> We are going to start billing folks for TSM resources usage/occupancy.
>
> One issue that came up was how to identify those node objects/files that
> are marked as DELETED and thus remain in inventory due to the RETONLY
> duration of the management class.  If we are to start billing for
> occupancy, we would need to be able to identify how much is being held
> because of RETONLY, especially since some managementclasses have this
> coded for 5-years (we have been arguing to lower this value, with much
> resistance, so we want to show them how much it is costing).
>
> Is there a way/query to do this?


-----------------------------------------
The information contained in this message is intended only for the
personal and confidential use of the recipient(s) named above. If
the reader of this message is not the intended recipient or an
agent responsible for delivering it to the intended recipient, you
are hereby notified that you have received this document in error
and that any review, dissemination, distribution, or copying of
this message is strictly prohibited. If you have received this
communication in error, please notify us immediately, and delete
the original message.