Hi guys and girls,

I have seen this question being asked several times in this list but no
answer was satisfying to solve the actual problem. So let me ask again:
We have a TSM ver 3.7 server running on AIX. There are volumes that contain
old backup sets from May 2000. The retention time for the volumes ranges
from anything between 28 days to nolimit.
1. They can not be seen via "q backupset", so one might think they have
expired (at least those with less than nolimit expiration). Thus, the
backup sets can definitely not be deleted via "delete backupset".
2. Doing a "q volhist" still shows them, though, so I am not able to check
the old volumes in as scratch or update their status after they have been
checked in private.
3. Editing the volhist file(s) does not produce any useful results, because
the volhist files are created by a "backup volhist", so the actual
information about the stale volumes is still hidden in the database.
4. Mind me, this is version 3.7, so there is no parameter like "delete
volhist ... type=backupset ...". Does this mean to delete these stubborn
backup sets, we will have to upgrade to ver 4.x??? Or is there any other
way to stay with 3.7 and tweak the database (like AIX offers the
odmdelete/odmadd commands to alter the ODM database)???


Regards Lars