Migration strategy
In the course of maintaining applications across several Db2 sites, you must implement a migration strategy. Every migration strategy establishes a control point.
A strong sender migration strategy, for example, might use the development subsystem as the control point for defining data structure definitions. Change control over the application originates at the development subsystem. When the application needs to be established at another subsystem, migration of the application’s structures, data, or both takes place using a migrate worklist. When an application needs to be maintained at another subsystem, CDL is used to migrate the application’s data structures.
When the control point of a migration process is at the receiving subsystem, then the migration strategy is referred to as a strong receiver. The subsystem that receives the migrate worklist applies rules that enforce local requirements for the application’s structure definitions. This strategy is sometimes preferred when Db2 software is purchased from a third-party vendor or when application data structures are implemented over a wide network of Db2 systems.
This section contains the following topic:
Related topic