|
|
|
|
|
Before you can copy data sets from the master IOA environment to the slave IOA environments or share data sets between the master and slave IOA environments, the Multisystem Upgrade process analyzes the data sets on the IOA environment (including SMP/E-managed and non-SMP/E-managed data sets) and detects those data sets that have changed during upgrade or maintenance. Data sets that have not changed (such as the INCONTROL product repositories and data bases) require no further action. Data sets that are detected as changed are divided into the following categories:
Table 26 Categories of data sets for Multisystem Upgrade
Number |
Category |
Further information |
|---|---|---|
1 |
Remain as is |
Data sets that do not contain hard-coded, installation-specific customization (such as environment prefixes), and can safely be copied to the slave IOA environment or shared between slave environments. The Multisystem Upgrade process strives to include as many data sets as possible in this group. For a list of data sets that you are required to keep free of installation-specific customization, see Limitations and requirements. |
2 |
Adjusted by the Propagation job |
For members that need to be copied from SMP/E-managed to non-SMP/E-managed libraries and contain installation-specific customizations, the Multisystem Upgrade process provides a special Propagation job. The Propagation job adjusts environment-specific parameters in copied members within target non-SMP/E-managed libraries. You must run the Propagation job on each slave IOA environment. |
3 |
Handled manually |
Certain changed data sets are not handled by the Propagation job and their contents cannot be copied between IOA environments. You must handle these data sets manually. Updated members in such data sets are identified by the Multisystem Upgrade process. |
Parent Topic |