On Nov 20, 2006, at 9:11 AM, Smith, I (Ian) wrote:

I've seen may situations where DRMDBBACKUPEXPIREDAYS does not
correctly
expire the tapes. I found a library with 120+ Dbbackup tapes in the
volhist but not in the drm cycle. Once the above expiredays parameter
has expired the tapes are no longer effectively managed by DRM, so as
long as the command deletes tapes longer than the setting- it should
clean things up- as long as they can be kept track of.

Hence the reason why a manual command may be implemented.

If you're certain that the DRMDBBackupexpiredays is in effect, and
that the age of the last volume of the series has exceeded the
expiration value, and that all volumes in the series are in Vault
state, and not part of the most recent dbbackup series (which
includes Full and Incrementals), then I would recommend reporting it
to TSM Support as an apparent defect.  This will help all customers.

   Richard Sims