This is what we need.  My understanding of the expiry issues is that
ultimately, after upgrading to 3.1.2.15, 16, or 20, files with too many
versions will have their situation corrected as files are next backed up.

What about the files that don't get backed up again?

Aside from that, my findings in the BACKUPS table show me that I have some
files that still have too many versions, files that have still been backed
up on a regular basis.  To top it off, some of the versions have
De-Activation dates that are dated BEFORE the object's backup date.  I can
only assume that thats an error in the database...(?).

After ADSM development fixed reclamation issues, they came out with Audit
Reclaim.....  Now that this server is running at 3.1.2.16 (supposedly
without expiry issues), I could sure use an Audit Expire.....

Paul