Step 3. Run the migration batch jobs

As part of the process of migrating Db2 object definitions, object data, views, and statistics, you need to run the migration jobs that were generated by Db2 Admin Tool.

To run the migration batch jobs:

1. Review the following source system jobs and submit them in the listed sequence:
   1. SST1RE - Performs reverse engineering.
   2. SST2ULn - Unloads data; n is an integer. If you are migrating many table spaces, multiple unload jobs might be created.
   3. SST3CH - Changes unload control data sets.
2. Run the batch jobs as follows:
   • If you combined the job steps, these jobs are located in the group xxxxS1. Run the first group with the name xxxxS1 on the source system.
   • If you specified the current system node name to be the name of the target system node, the source and target systems are the same. In this case, run all of the generated jobs on the same system and skip Step 4. Optional: Transfer the jobs, work statement list, and data to the target system.
   • If you requested that a work statement list (WSL) be generated and are running in local mode (that is, not connected to a remote subsystem), run the xxxSn job in sequence to extract the DDL, unload the data, change the LOAD control statements, and write the work statement list.
   • If you are running in DRDA mode (that is, connected to a remote system), run the xxxSn job first to unload the data on the remote (source) system. After the xxxSn jobs are complete and the data sets contain the unloaded data and the LOAD control statements are transferred from the remote system to the local system, run the xxxLn job to extract the DDL, change the LOAD control statements, and write the work statement list.

     Usually, only one xxxSn job exists to unload the data. However, if many table spaces require unloading, multiple xxxSn jobs are generated. The final xxxSn job on the remote system specifies the data set names that need to be transferred to the local system for creating the WSL. n in the xxxLn job is one greater than the n in the last xxxSn job.

   Tip: If one or more SQL statements fail when you run a migrate job, you can use the Batch Restart program (ADBTEP2) to restart or resume the job at an intermediate point.