Hello,

TSM: 5.1.6.4 w/DRM enabled
AIX: 4.3.3.10

I having been looking at the completion of my expiration processes for
the last 15 days and I see, for example, the following:

07/27/03   15:15:01      ANR2017I Administrator ADMIN issued command:
EXPIRE
                          INVENTORY

07/27/03   15:15:01      ANR0984I Process 709 for EXPIRE INVENTORY
started in the
                          BACKGROUND at 15:15:01.

07/27/03   15:15:01      ANR0811I Inventory client file expiration
started as
                          process 709.


07/27/03   17:42:42      ANR2369I Database backup volume and recovery
plan file
                          expiration starting under process 709.

07/27/03   17:42:42      ANR0812I Inventory file expiration process 709
completed:
                          examined 3828936 objects, deleting 420981
backup objects,
                          0 archive objects, 0 DB backup volumes, and 0
recovery
                          plan files. 0 errors were encountered.

07/27/03   17:42:42      ANR0987I Process 709 for EXPIRE INVENTORY
running in the
                          BACKGROUND processed 420981 items with a
completion state
                          of SUCCESS at 17:42:42.

The process is completing successfully, but as you can see no DB backup
volumes or recovery plans are expired.  I have an admin schedule that
has the following command in it: delete volhistory todate=today-30
type=all, which I do not think would affect the expiration of DB and
recovery plan process since it is set for 30-days.

DRM expiration is set as follows:

  DB Backup Series Expiration Days: 5 Day(s)
Recovery Plan File Expiration Days: 14 Day(s)

And, when I perform a q volh t=dbb, I get DBB's that are retained from
13-days ago.

What am I missing?  Can someone explain this?

Thanks.

Mahesh