Migration schemes
A migration scheme defines one or more migration paths. Each migration path refers to a pair of CICS® configurations: a source CICS configuration and a target CICS configuration. The source CICS configuration identifies where you want to migrate from; the target CICS configuration identifies where you want to migrate to.
When you issue the command to migrate a change package, you specify the migration scheme that you want to use. CICS Configuration Manager copies resource definitions according to the migration paths in the migration scheme.
For example, Figure 1 shows a change package containing two resource definitions from different CICS configurations, DEVA and DEVAB, and a migration scheme containing three migration paths.

In this example, CICS Configuration Manager copies:
- Resource definition X from DEVA to TESTA
- Resource definition Y from DEVAB to TESTA
- Resource definition Y from DEVAB to TESTB
For each migration path, you can specify a "delete at source?" option. If you specify "yes", migration effectively moves rather than copies resource definitions: after copying resource definitions to the target CICS configuration, CICS Configuration Manager deletes them from the source CICS configuration. The default value is "no" (do not delete at source). If the source CICS configuration refers to an export file, you must specify "no".
Deleting at source suits migration scenarios such as the following:
- You have a CSD file that you use only as a work file for creating and editing resource definitions, not as the DFHCSD file for any active CICS systems. After promoting (migrating) resource definitions from this work file to other target CSD files or contexts, you want the resource definitions to be deleted from the work file. The work file is a staging area: it only contains resource definitions that have not yet been promoted.
- You are implementing a CICSPlex® SM BAS alternative to using CSD files, and you want to move resource definitions from CSD files to a CICSPlex SM data repository.