Using RESET with concurrent copy (OY65555)

The RESET keyword specifies that DFSMSdss resets the data-set-changed indicator for data sets after the dump is complete. By default, the RESET keyword is ignored when the CONCURRENT keyword is also specified with the DUMP command.

Setting the byte at offset X'18' in ADRPATCH to a nonzero value causes DFSMSdss to perform RESET processing when both the RESET and CONCURRENT keywords are specified with the DUMP command. In this case, the data-set-changed indicator is reset after concurrent copy initialization is complete and before the data set is written to the output.

To dynamically enable RESET processing with concurrent copy, use the SET PATCH command. To enable RESET processing with concurrent copy permanently, modify the sample JCL (see Sample JCL) as follows:

//SYSIN    DD *
   NAME ADRDSSU ADRPATCH
   VER   18      00
   REP   18      FF

After the data-set-changed indicator has been reset, if the concurrent copy dump is unsuccessful for any reason, the data-set-changed indicator for the data set remains reset even though you might not have a usable dump of the data. For this reason, you must carefully evaluate the risks of using this patch to enable RESET processing with concurrent copy. Rather than using this patch to accomplish incremental backup in DFSMSdss with concurrent copy, use DFSMShsm instead.

In the event that the data-set-changed indicators have been reset and the dump subsequently fails, your recovery action can be either of the following:

Turn the data-set-changed indicators back on by using AMASPZAP.
Dump the data again. Because the data-set-changed indicators are still off, you must not specify "BY(DSCHA,EQ,YES)" in the dump command.