I've searched through www.adsm.org but did not find an example of how
to preform automation of DB2 archive logs and the DB2 history file when
backing up to TSM.

The db2adutl delete command provides the ability to keep N number of
versions or delete backups older than a timestamp.  Once that command is
done you must then run a db2adutl query,  find the oldest backup and see
what the oldest log file is that it needs.  Then using that value you can
delete all the logs up to that oldest log that the oldes backup needs.
whew.

After deleting a backup using db2adutl query, the information in the
db2adutl history file is now out of sync.  It still references the backup
that no longer exists on TSM storage.  You can prune the history file by
date, but this also deletes all entries in the history file, not just the
TSM backups.

So given all these factors, has anyone come up with a slick way to automate
all these processes?

Are you using some type of scripting or leaving it up to the DB2 database
administrators to manage?

James Thompson
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com