Previous Topic: Step 1: Determine the Types of Components to MigrateNext Topic: Step 3: Identify the Individual Components

Migrating from Test to Production › Implementing Migration Procedures › Step 2: Determine the Sequence of Migration

Step 2: Determine the Sequence of Migration

Can Migrate Load Module at Any Time

If you choose to migrate only load modules, the sequence in which you migrate them does not matter.

Sequence Matters for Source Code Migration

If you migrate any source code, the sequence is very important because there are dependencies among the components.

In some migrations, certain components will already be in place; in others, you will need to migrate all components. The list below shows the sequence required if all components were to be migrated.

Non-SQL database definitions

  1. Elementary data items
  2. Group level data items
  3. Database records
  4. Schemas
  5. Subschemas

SQL database definitions

  1. Schemas
  2. Tables
  3. CALC keys
  4. Indexes
  5. Constraints

Physical database definitions

  1. Segments
  2. Areas
  3. Files
  4. DMCL modules
  5. Database name tables

Application components definitions

  1. Edit and code tables
  2. Work records for elementary data items,group level data, maps, and dialogs
  3. CA ADS process modules
  4. Modules called by CA ADS processes or other programs
  5. Maps
  6. CA ADS application structures
  7. CA ADS dialogs
  8. RCMs (for SQL DML applications only)
  9. Access modules (for SQL DML applications only)

Components that can be migrated in any sequence

  1. Load modules
  2. Source code for batch and online programs
  3. CA Culprit source code
  4. JCL