Restarting from the beginning

This specifies that if the utility ID does not exist, treat it as new. If the utility ID does exist, clean up for the previous run, and then restart the job from the beginning.

For table spaces image copies, when you use NEW/RESET to restart a job that failed in the COPY phase and the original job used the FULL YES and RESETMOD YES options, BMC AMI Copy puts a T entry in the ICTYPE column of SYSIBM.SYSCOPY to prohibit the making of an incremental copy until a full copy is successfully made.

Dynamic allocation of image copies

If you use dynamic allocation for your output data set, no modification to the job stream is required.

Allocation of image copies in the JCL

The advantage of NEW/RESET is that only the data set names must be modified for the restart. If GDGs are used, no modification of the JCL is necessary. Do not use this method under a restart package that modifies the data set names or dispositions on restart.

If you allocate the copy data sets in the JCL, you must also do the following things:

• Use DISP=(NEW,CATLG,CATLG) or DISP=(NEW,KEEP,KEEP).
• Use unique data set names for each execution. GDGs or symbolic variables (Using-GDGs-and-symbolic-variables-in-data-set-names) are helpful for accomplishing this.
• Code BLKSIZE=0 for disk data sets so that unopened data sets can be migrated successfully (if desired).

Allocating the copy data sets in the JCL usually causes extra processing during a restart if multiple spaces are copied in the job step because any copies made during the original job step will be made again. This method leaves empty, unused data sets if disk copies are made for any COPY commands not executed by the failing run.