Understanding the Clone function

You use keywords to identify the source repository, which contains the records that you want to copy, and the target repository, which will contain the copied records. You also use keywords to select the records that you want to copy:

• For elemental group, connecting group, object, profile, and utility records, you can provide a generic name (by using masking characters) or a specific name. You can also specify whether to replace an existing record in the target repository.

  When you use the Clone function to clone elemental group, connecting group, and object records, the function copies these records without modification from the source repository to the target repository. To ensure that the data in the cloned repository accurately reflects the new environment, you should verify and update the data in the IMS and Sharegroup environment records and run the Rebuild function. The Rebuild function detects changes and updates the group and object definitions as necessary to reflect the new environment. This function also produces a report that summarizes detected differences.

  Warning

  Note

  Although the Rebuild function will change object data set names and volume serial numbers to reflect their current state, these changes do not indicate changes to the organization or composition of the group and are not identified in the report.

• For RMGR environment, IMS environment, and sharegroup environment records, you can specify a new RMGR name, IMS ID, or sharegroup name for the new record in the target repository. If you specify a new name, you must specify the name of a record in the source repository to use as a model for the contents. This action simplifies the setup of multiple similar environments.

  For an RMGR environment, IMS environment, or sharegroup environment record to be cloned, the new record cannot exist in the target repository, and the model record must exist in the source repository.