Siebel Database Upgrade Guide for DB2 for z/OS > Generating the Siebel Upgrade Files > Preparing and Executing the Nonadditive Schema and JCL Files on the z/OS Host >

Creating the Data Migration Indexes

Perform the following procedure to create temporary tables and indexes for the data migration scripts and to rebuild indexes.

To create data migration indexes

1. On the Staging Database Non-Additive Schema Menu, select option 5: Build Data Migration Index Statements, and press Enter.

   Messages are displayed on screen indicating that data migration CEATE INDEX and DROP INDEX statements are being generated. The messages you receive depends on your upgrade path.

2. On the Staging Database Non-Additive Schema Menu, select option 6: Create Data Migration Temp Table/Indexes, and press Enter.

   This job creates COMMON temp tables and indexes used by upgrade data migration SQL scripts.

3. Submit the JCL in one of the following data sets:
   • For Siebel Industry Application (SIA) upgrades, use DSNHLQ.SIEBEL.INSTALL.JCL(DMXSIA7)
   • For Siebel Business Applications upgrades, use DSNHLQ.SIEBEL.INSTALL.JCL(DMXHOR).
4. Verify that the job ran successfully with a return code of 0, 4, or 8. For information, see Verifying JCL Upgrade Jobs
5. After submitting the job, enter cancel on the command line or press PF3 to save changes.
6. On the Staging Database Non-Additive Schema Menu, select option 7: Generate Index Rebuilds, and press Enter.

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

   Make sure that the ISPF batch procedure dsnhlq.siebel.proc(ispbat) is modified to your installation standards.

7. Enter Y to confirm that the ISPF batch procedure is correctly configured, then press Enter.
8. 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. It is recommended that you specify 3.

   CAUTION:  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.

9. Press Enter, and you are placed in Edit mode in the DSNHLQ.SIEBEL.INSTALL(SBLJCL24) data set.
10. Submit the job and verify that the job ran successfully with a return code of 0 or 4. For information, see Verifying JCL Upgrade Jobs.
11. Press PF3 twice to return to the Staging Database File Generation Menu.