Recovery after image copy
The Database Image Copy utility (DFSUDMP0) and the Database Image Copy 2 utility (DFSUDMT0) copy data sets for HISAM, HIDAM, HDAM, PHDAM, PHIDAM databases, and areas for DEDBs.
When you perform a subsequent recovery, what you need as input to the recovery depends on whether the copies are concurrent or not:
- For non-concurrent copies, you need only the image copy and those logs created after the database is restored to the online system.
- For concurrent copies, you need the image copy and logs created before and after the database is restored to the online system. DBRC helps you decide which logs you need.
Recommendation: When you run the Database
Image Copy utility (DFSUDMP0) for databases and areas (without specifying
the
CIC on the EXEC statement for
the utility), no other subsystem should update the databases. You
can prevent updates to full function databases by issuing the /DBDUMP
DB or UPDATE DB STOP(ACCESS) command.
You can prevent updates to DEDB areas by issuing either the /STOP
AREA or UPDATE AREA STOP(SCHD) command.The Online Database Image Copy utility (DFSUICP0) runs as a BMP program. You can use it for HISAM, HIDAM, and HDAM databases only. If IMS updates these databases while the utility is running, IMS requires all logs for any subsequent recovery, including the log in use when you started the utility. IMS requires the logs because the image copy is not an image of the database at any one time.