MVSFORUMS.com

[vmbigot]

We are using the standard DB2 COPY utility to create image copies, both full and incremental, of all of our databases. We would like to be able to selectively delete image copies out of the SYSIBM.SYSCOPY table and their associated datasets. The problem with the standard DB2 MODIFY utility is that you have only two options, delete ALL image copies that are more than AGE(nnn) old or ALL image copies that are older than DATE(yyyymmdd). We need to keep monthly full image copies for at least three years, but in order to do that we need to keep ALL image copies for three years, and that is a lot of disk space and tapes!

Is there a utility that is available that manages image copies in such a way that you can select those image copies you would like to keep and delete the rest?

Thanks,

vmbigot
_________________
Inside every older man is a young boy asking this question. What the heck happened?!?

[kolusu]

vmbigot,

Run LISTDEF/REPORT utilities and parse the output and create the MODIFY control cards on the fly for the ones you want to delete/keep

Kolusu

[CraigG]

Modify does not delete the image copies, it only deletes the entries from the syscopy table.

[vmbigot]

Kolusu,

I've found that I can still use the catalogued image copy datasets as input to a LOAD, even though the dataset is no longer in the SYSCOPY table. Therefore, I am comfortable with setting up a scheduled MODIFY RECOVERY job to delete old entries in the SYSCOPY table.

The only reason we need to keep three years of backups is so that our programmers can bring back archived data for auditing purposes. Now that I know that a LOAD will process old data without an entry in the SYSCOPY table I can reassure our auditors that old data will not be lost.

Thanks again for your assistance.

vmbigot
_________________
Inside every older man is a young boy asking this question. What the heck happened?!?

[videlord]

DSN1COPY is more easier.
You don't need UNLOAD/LOAD.