Progressive migration
Updating, in Pacbase, instances that have already been migrated is not advised. However, in some cases, you must keep on working in Pacbase. You will then have to migrate your modifications.
Before you begin
You must comply with the following use conditions:
- You are strongly advised against working simultaneously on the same instances in Pacbase and Rational® Programming Patterns because these updates create conflicts.
- You must not modify, in Rational Programming Patterns, the Dialogs of the Screens that are involved in the progressive migration. These Dialogs are always extracted by the progressive migration and their local modifications can generate conflicts.
- In a multi-session migration, to migrate the updates on a Pacbase session that has already been migrated, you must target the corresponding Rational Team Concert™ stream, which was created by the duplication of the migration stream.
- The use of the progressive migration must be as time-limited as possible to avoid complex update conflicts. During this time, if several streams (development stream and production stream for example) are each updated from a specific Pacbase session, you can manually carry over the updates to the streams but you must not promote these streams.