z/OS V1R6.0 DFSMS Access Method Services for Catalogs

REPROThe merge operation can be restarted if an error occurs, because the targetcatalog does not have to be empty. A LISTCAT and DIAGNOSE should berun before the MERGE is restarted. If the MERGE ended while processinga generation data group, it might be necessary to delete that generationdata group from the target catalog because of duplicate data set names inthe source and target catalogs.Candidate volumes are preserved. MERGECAT retains candidate volumeinformation when moving an entry from one catalog to another.For some duplicate key errors, the merge does not end, and the processingof the next entry continues. However, some alias associations might not bemerged because of the duplicate key error.MERGECAT performs a series of DELETE NOSCRATCH and DEFINERECATALOG requests to move entries from one catalog to another. Forinformation concerning security authorization levels, see Appendix A,“Security Authorization Levels,” on page 351.During MERGECAT, if the target catalog name is found in the VVDS, thecluster entry for the VVDS is not recreated in the target catalog. You mustuse DEFINE CLUSTER RECATALOG to create the VVDS cluster entry inthe target catalog.See z/OS DFSMS: Managing Catalogs for additional information on theintegrity of RACF discrete profiles after using MERGECAT.Abbreviation: MRGCNOMERGECATspecifies that the source catalog is to be completely copied into an emptytarget catalog.MERGECAT can also be specified for tape volume catalogs or VOLCATS.For more information on REPRO MERGECAT of VOLCATS, refer to“Access Method Services Tape Library Support” on page 7.The empty target catalog implies that the copy operation cannot berestarted if an error occurs. Before the copy operation can be restarted, thetarget catalog must be redefined and all volumes that contain objects mustbe restored.After a REPRO of one catalog to another, the VVRs are changed to point tothe target catalog, and all subsequent processing must be done under thetarget catalog.Attention: Performing REPRO on a catalog while data sets are open inthe source catalog might result in a loss of information if any of those datasets extend, or other catalog updates are made. The changes might not becopied to the target catalog, resulting in a mismatch between theinformation contained in the VVDS and the new target BCS. This mightcause the data sets to be inaccessible or receive errors.Abbreviation: NOMRGCREPLACE|NOREPLACEspecifies whether a record in the source cluster (INFILE or INDATASET) is toreplace a record in the target cluster (OUTFILE or OUTDATASET) when thesource cluster is copied into the target cluster.Chapter 30. REPRO 311