Integrating with BMC AMI Recover

You can also use these input change accumulation files in a recovery job with the following options:

• INDEP OUTSPACE

• LOGONLY or LOGAPPLY ONLY

You can create change accumulation files in normal recovery jobs including those where you specify INDEP OUTSPACE for a recovery to the current point.

When you run a BMC AMI Recover job that specifies the OBIDXLAT, INCOPY, or DROPRECOVERY option, you cannot create change accumulation files from the job.

When a table space is dropped, the SYSCOPY and SYSLGRNX entries no longer exist. If you run MODIFY ACCUM after a table space is dropped, the corresponding change accumulation files are deleted. When you subsequently run BMC AMI Recover, the deleted change accumulation files are not available for recovery.

The following figure shows how you can use change accumulation files with BMC AMI Recover to recover a dropped table space. In this example, change accumulation files were created before the table space was dropped. The table space must be created again using the same name. Because you have not run MODIFY ACCUM since the new table space was created, the change accumulation files for the dropped table space still exist in the repository and you can use BMC AMI Recover to perform the drop recovery operation.

For more information, see  Using R+/CHANGE ACCUM with BMC AMI Recover .