Migrating data structure changes to other subsystems

Use the following procedure to migrate data structure changes from a control subsystem to receiving subsystems. This procedure consists of establishing a baseline of the changed application and performing a change migration process.

  1. Establish a catalog baseline of the changed application.
    1. Create a baseline profile and use the scope rules to control the objects that are included in the baseline. For more information, see Creating-a-catalog-baseline-profile.
    2. Create a baseline from the baseline profile that you created in Step 1.a. See Creating-a-structure-only-catalog-baseline.
  2. Compare two versions of a catalog baseline.
    1. Create an outbound migrate profile that specifies your receiving subsystems (locations). For more information, see Creating-an-outbound-migrate-profile.
    2. Compare a baseline to a baseline, using the outbound migrate profile that you created in Step 2.a. For more information, see Comparing-a-baseline-to-a-baseline.
  3. Import the CDL from the comparison in Step 2 to an alter-type work ID.
    1. Create an alter-type work ID. For more information, see Creating-an-alter-type-work-ID
    2. Import the CDL to the work ID that you created in Step 3.a. For more information, see Importing-a-CDL-DDL-or-DML-file-to-Change-Manager.
  4. Analyze the alter-type work ID and generate a worklist. For more information, see Analyzing-an-alter-type-work-ID-and-generating-a-worklist-in-Change-Manager.
  5. Execute the worklist. For more information, see Executing-an-alter-type-worklist.

Related topic

Accomplishing-your-maintenance-goals



 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*