Is there something other than 'del volhist' that trims the volhist file?  The 
oldest entries in my volhist are 30 days but if I search actlog I don't find 
any sign that a 'del volhist' command was run.

>>> mark.stapleton AT BERBEE DOT COM 04/13/05 9:31 AM >>>
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On 
Behalf Of David E Ehresman
>If one uses DRM to expire data base backups, should one still routinely
>do a "del volhist type=all today="? Why or why not?

From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On 
Behalf Of Talafous, John
>Using the "del volhist" command in conjunction with DRM may potentially
>cause deletion of DB backup tapes that are vaulted. Hence, TSM DRM will
>not process the volume via vault retrieve. 
>
>If you do both, be sure your "DRM DB Backup Series Expiration Days"
>value in DRM is less than the TODate value of the "del 
>volhist" command.
>
>For example, DRM DB Backup Series Expiration Days = 7
>"Del volhist todate=today-30"

Well, there *are* reasons to run DEL VOLHISTORY periodically, in order
to keep really old volume history entries from piling up in the TSM
database. I normally have customers run something like this:

        del volh type=dbb todate=today-180
        del volh type=dbs todate=today-180
        del volh type=stgdelete todate=today-180
        del volh type=stgnew todate=today-180
        del volh type=stgreuse todate=today-180
        del volh type=rpffile todate=today-10

(The number of days for the "type=rpfile" matches the number of days set
by DRMDBBACKUPEXPIRE and DRMRPFEXPIREDAYS.) 

The reason I don't normally recommend "type=all" is that doing so will
remove all references to export tapes and backupsets.

--
Mark Stapleton (stapleton AT berbee DOT com)
IBM Certified Advanced Deployment Professional
Tivoli Storage Management Solutions 2005
Office 262.521.5627