|
|
|
|
|
Often customers require more than one IOA environment. The additional IOA environments can be used for testing and debugging purposes, as well as for additional production systems.
Instead of repeating the installation process, you can simply create copies of your base (source) IOA environment, using a cloning process.
IOA provides a toolkit that can be used for efficiently cloning the existing IOA environment on the same MVS system (local cloning) or to another MVS system (remote cloning). Both SMP/E managed and non-SMP/E managed cloned environments can be created with the toolkit.
The cloning process consists of the following major steps:
In this step, the user defines the type of cloning process (local or remote) and the characteristics of the cloned environment (such as the cloned environment ID and description, whether the cloned environment is SMP/E managed, whether the user data will be cloned, and whether the allocation attributes of the cloned environment will be defined).
In this step, the user specifies various parameters of the target cloned environment. These parameters are then validated by ICE. In addition, jobs and definitions are built in preparation for the later cloning steps.
In this step, the Cloning Package is built. The package contains all the data sets of the source base IOA environment that will be copied to the target cloned environment.
In this step, all data sets from the Cloning Package are restored on the target LPAR with new names for the target cloned IOA environment. The Renaming tool is then executed on the target LPAR, adjusting internals of the target cloned IOA environment according to the new data sets names and parameters. Afterwards, post-cloning steps are performed by the user to achieve a working cloned IOA environment.
For more information, see