Modification of data structures using change rules
You can use change rules to modify the attributes of the data structures. Change rules compare the object type, attribute, and current value of the attribute, along with any name qualifiers, with those in the migration. If a match is found, the new value specified for the attribute is used for the object on the destination subsystem.
The following types of change rules exist:
Change-type | Change-type is used to change the value of a data structure’s attribute. For example, you can change the buffer pool of a table space from BP1 to BP3. You can also change the names of objects to enforce the naming conventions of the receiving location. |
|---|---|
Include-type | Include-type is used to include volumes in a storage group, table space, or index. This type of change rule enables you to tailor a set of data structures for the DASD requirements of the receiving location. |
Exclude-type | Exclude-type is used to exclude volumes from a storage group, table space, or index. |
(Migration only) Force-type | Force-type is used to force storage group defined table spaces and indexes to be created by using VCAT catalog names on the receiving subsystem instead of storage group names. You can only use this rule with storage-group defined table spaces or indexes and you must specify the VCAT attribute. |
(Import and comparison only) Suppress-type | Suppress-type is used in an inbound migrate profile to filter out the changes specified in a Change Definition Language (CDL) file when you use the Import component to import the CDL. You can also filter out specific changes from appearing in a CDL file by using suppress-type change rules in an outbound migrate profile with the Compare component. |
You can specify change rules for either migrate-type work IDs or outbound migrate profiles.
This section contains the following topics:
Related topic