Recovery from a concurrent nonstandard image copy
Before you recover the DBDS or DEDB area with a concurrent nonstandard image copy data set, issue the CHANGE.DBDS command with the RECOV parameter to set 'recovery needed' status to indicate that the DBDS or DEDB area is unavailable for use.
After the DBDS or DEDB area has been restored from the image copy, run the Database Recovery utility to add the changes that occurred since the time stamp of the nonstandard image copy data set. DBRC provides and verifies JCL only for the sources of change records to be applied to the already-restored DBDS or DEDB area.
If you are using a concurrent nonstandard image copy and you use the GENJCL.RECOV command to generate the recovery JCL, do not include the USEDBDS parameter; in this case, a flag in the DBRC RECON data set indicates that the image copy data set is to not to be included in the generated JCL.
When you recover the database data set, you must indicate the runtime when the nonstandard concurrent image copy was taken. You can do this by specifying either the USERIC(time_stamp) keyword or the LASTUIC keyword of the GENJCL.RECOV command, which generates a JCL stream for the Database Recovery utility that adds the changes since the nonstandard concurrent image copy data set was created. DBRC generates and verifies JCL only for the sources of change records to be applied to the already-restored DBDS or DEDB area.
Because the Database Recovery utility does not use an image copy for processing the change records, DBRC does not allow the Database Recovery utility to process any log that contains changes outside the recovery range. The recovery range is defined by the time-stamp recovery record's RECOV TO (image copy time) and RUNTIME values.