ARC1212I
DUPLICATE MIGRATED COPY ALREADY EXISTS ON ANOTHER MIGRATION VOLUME

Explanation

During a FREEVOL operation, migration of a data set was ended, because it was a duplicated migration copy. Another copy exists on a volume indicated by the MCDVSN field in the MCD record.

System action

The migration copy will not be migrated to another volume. FREEVOL processing will continue.

Programmer response

The data set will remain on the source volume. You will probably want to do something with the duplicate data set on the ML1 volume as there will not be a DFSMShsm record associated with it.

Using the FIXCDS command and information provided in message ARC0734I, you can locate additional information about the data set which is causing the problem. If the migration copy name appears in message ARC0734I, read the MCA record first to find the user data set name. Then, use the user data set name to read the MCD record. If you do not have the migration copy name, then use the MCD record first.

Once you have the exact information describing the data set and its locations, you can determine what should be done. For example, you may choose to either delete or recall the data set.

Source

DFSMShsm