Implementing Siebel Business Applications on DB2 for z/OS > Migrating a Siebel Database to Unicode Format > Process of Performing the Database Unicode Migration >

Building the Unicode Migration Jobs

Once you have built your Unicode schema, you must build the appropriate DB2 Cross Loader, index rebuild, and Runstats jobs that are required to migrate your source database to your Unicode database. This topic describes how to build the data migration jobs.

This task is a step in the Process of Performing the Database Unicode Migration.

To build the Unicode migration jobs

1. On the Siebel Unicode Migration Option Menu, select option 2. Pre-Migration, and press Enter.
2. On the Unicode Pre-Migration Menu, select option 3. Build Jobs, and press Enter. The Unicode Pre-Migration Build Job Menu is displayed. The panel ID is SBLBLDJP.
3. Select option 1. Build Cross Loader Jobs, and press Enter.
4. Submit the JCL in the data set DSNHLQ.SIEBEL.UNI.INSTALL.JCLLIB(SBLJCL23) to generate the data migration jobs.
5. After submitting the job, enter cancel on the command line or press PF3 to save changes.
6. Verify that the job ran successfully (RC is 0), and that a data set, DSNHLQ.SIEBEL.DDLIMP.UNLOAD.CNTL, was created.

   This data set contains the Cross Loader cards and jobs that copy the data from the source to the target database.

7. On the Unicode Pre-Migration Build Job Menu, select option 2. Build Index Rebuild Jobs, and press Enter.

   A message appears, asking you to confirm that the DSNHLQ.SIEBEL.PROC(ISPBAT) (ISPF batch procedure) is installed.

8. Enter Y to confirm that the ISPF batch proc is installed, and press Enter.
9. When the following message appears, specify the number of indexes to be included in each rebuild job, and press Enter:

   NUMBER OF INDEXES PER REBUILD JOB.

   The maximum number of indexes that can be included in a job is 10.

   Consider your objective before choosing a maximum number of indexes for each job. Increasing this number results in fewer jobs but requires more memory and sort work. Reducing this number results in more jobs, which reduces resource requirements but causes fewer indexes to be built in parallel.

10. Submit the JCL in the data set, DSNHLQ.SIEBEL.UNI.INSTALL.JCLLIB(SBLJCL24).

    NOTE:  This job builds the Index Rebuild jobs for unique, non-unique, and obsolete indexes and can take an extended period of time to complete (up to an hour or more).

11. Verify that the job ran successfully (RC is 0) and that the following data sets were created:
    • DSNHLQ.SIEBEL.UNI.RBLDOIX.JCL
    • DSNHLQ.SIEBEL.UNI.RBLDOIX.SQL
    • DSNHLQ.SIEBEL.UNI.RBLDSIX.JCL
    • DSNHLQ.SIEBEL.UNI.RBLDSIX.SQL
12. On the Unicode Pre-Migration Build Job Menu, select option 3. Build Runstat Jobs, and press Enter.

    The Upgrade RUNSTATS panel is displayed (the panel ID is SBLRSP).

13. Read the information relating to the RUNSTATS jobs on the Upgrade Runstats panel, then press Enter.
14. Submit the JCL in the data set DSNHLQ.SIEBEL.UNI.INSTALL.JCLLIB(SBLRS) to start the RUNSTATS job generation process. When the process is completed, the Runstat jobs are placed in the DSNHLQ.SIEBEL.UNI.RUNST data set.
15. Press PF3 twice to return to the Unicode Pre-Migration Menu.

    NOTE:  Before proceeding to Step 16 to load the log table, ensure that all of the Build jobs have finished running and that they completed successfully (RC is 0).

16. Select option 4. Load Target Schema to load the Siebel logging table with the Unicode migration jobs to be executed against the target schema. Press Enter.
17. Submit the job using the JCL in data set DSNHLQ.SIEBEL.UNI.INSTALL.JCL(LOADLOG2).
18. Verify that the job ran successfully, and that additional log entries for Cross Loader, index rebuild, and runstats jobs have been loaded to the log table (TMP_SBLLOG_UNI).

    The process of building the Unicode migration jobs is completed.