Michael, this is not a bug.  With DB2/6000 V2, the naming convention
used for the backup files has changed vrom DB2/6000 V1;  with DB2/6000 V2
all backup file names are based on a sequence number and therefore are
unique for every backup to ADSM.  The backup copies in ADSM are therefore
always active and never deleted by normal ADSM file expiration processing.
DB2/6000 V2 provides a db2adult utility to delet backups and log files
that are no longer required.  The latest redbook on ADSM database backup,
SG24-4335-01, is available and describes this.
thanks,
Cyndie Behrens
IBM - ITSO San Jose
408-927-3627
cbehrens AT vnet.ibm DOT com