Selection of source and target volumes

Consider the following requirements as you plan the cloning environment:

Scope of source volumes to be copied
Desired target volume data sets
Source and target volume condition
Target volume online status
Data set and sphere integrity
Discrete volumes versus SMS storage group specification
Migrated data sets
Requirements for source and target volume pairing

Scope of source volumes to be copied
The source volumes to be copied must include all of the data sets that are required by the applications that access the renamed data sets on the target volumes.
Desired target volume data sets
Copies of data sets that are used by an application must be included in the list of cloned volumes and must match a rename mask.
Source and target volume condition
While you plan to clone an IMS subsystem, you must consider the condition of the source and target volumes.
Target volume online status
When you are planning to clone an IMS subsystem, you must consider the condition of the status and location of the target volumes.
Data set and sphere integrity
By default, IMS Cloning Tool detects and fails the rename process if one of these data set integrity rules is violated.
Discrete volumes versus SMS storage group specification
If you use FlashCopy or SnapShot, you can indicate the source and target volumes by specifying SMS storage groups instead of discrete volumes.
Migrated data sets
Ensure that the data sets to be copied, including available generations of a renamed GDG, cannot be migrated before the volume copies are created.
Requirements for source and target volume pairing
When you are planning for the use of the source volumes, ensure that each source volume is paired with a target volume.

Parent topic: Planning to clone an IMS subsystem