Restart of COPY

You can restart the COPY utility.

Recommendation: Use restart current when possible, because it:
  • Is valid for full image copies and incremental copies
  • Is valid for a single job step with several COPY control statements
  • Is valid for a list of objects
  • Requires a minimum of re-processing
  • Keeps the Db2 catalog and the integrated catalog facility catalog synchronized

If you do not use the TERM UTILITY command, you can restart a COPY job. COPY jobs with the CONCURRENT option restart from the beginning, and other COPY jobs restart from the last commit point. You cannot use RESTART(PHASE) for any COPY job. If you are restarting a COPY job with uncataloged output data sets, you must specify the appropriate volumes for the job in the JCL or on the TEMPLATE utility statement. Doing so could impact your ability to use implicit restart.

If the recommended procedure is not followed an ABEND 413-1C may occur during restart of the COPY.

Restarting with a new data set

If you define a new output data set for a current restart, complete the following actions before restarting the COPY job:

  1. Copy the failed COPY output to the new data set.
  2. Delete the old data set.
  3. Rename the new data set to use the old data set name.

Restarting COPY after an out-of-space condition

You can also restart COPY from the last commit point after receiving an out-of-space condition.