Upgrade Guide for DB2 UDB for z/OS and OS/390 > Upgrading a Database from the Mainframe >

Preparing Siebel-Scheduled JCL

Upgrades: All upgrades.

Environments: Development (mainframe-centric) environment and Production environment.

This topic is part of an upgrade process. See How to Perform the Upgrade.

Perform the following procedure to prepare the 7.7 index DDL, build index rebuild jobs, and build drop statements for old schema indexes.

NOTE:  The following procedure applies only if you are using the Siebel-Scheduled Mode for executing jobs.

To prepare Siebel-scheduled JCL

1. If you are not on the Siebel Upgrade Main Menu, enter the following command:

   TSO SBLUPG77

2. Select option 3: SCHEMA/JCL - BUILD DDL AND JCL-PREP FOR UPGRADE.

   The Schema/JCL Menu appears. The panel ID is SBLUPGP.

3. Select option 2: SIEBEL SCHEDULED - JCL-PREP TO BUILD/EXECUTE/MANAGE JOBS VIA SIEBEL.
4. Select option 4: GENERATE INDEX REBUILDS. The Index Menu appears. The panel ID is SBLIDXP.
5. The example text uses the TSO foreground mode (either batch or foreground mode can be used).

   NOTE:  It is recommended that you perform the procedure in batch mode.

   Run option 2: GEN PRIMARY INDEX REBUILDS in batch mode by entering 2 in the option field, then tabbing to the RUN OPTION 1-OR-2 IN BATCH? N (Y/N) screen. Replace the N with a Y.

6. Select option 2: GEN PRIMARY INDEX REBUILDS.

   A series of messages are displayed beginning with the following:

   ==> SPLIT AND BUILD "SCINDX" INDEX DDL FILES:

   DROP INDEXES : DSN=DSNHLQ.SIEBEL.SCINDX.GPDRPIX.DDL

   EIM : DSN=DSNHLQ.SIEBEL.SCINDX.EIM.DDL

   PRE-GEN_PRIMARY : DSN=DSNHLQ.SIEBEL.SCINDX.GPPRE.DDL

   POST-GEN_PRIMARY: DSN=DSNHLQ.SIEBEL.SCINDX.GPPST.DDL

   Messages continued:

   ==> JCL TO RUN DROP/CREATE INDEX "DDL" WRITTEN TO:

   DROP INDEXES : DSN=DSNHLQ.SIEBEL.INSTALL.JCL(@GPDRPIX)

   CREATE INDEXES : DSN=DSNHLQ.SIEBEL.INSTALL.JCL(@EIMIX)

   DSN=DSNHLQ.SIEBEL.INSTALL.JCL(@GPPREIX)

   The Split and Build runs next.

   The following message appears:

   NOTE: FOLLOWING THE MESSAGES BELOW IN APPROX 15 SECONDS, AN "ENTER" PROMPT WILL APPEAR REQUIRING YOUR ENTRY...

   These additional messages appear:

   DROP STATEMENTS WILL BE BUILT FOR OPTIONAL USE:

   BUILDING - DROP DATABASE STATEMENTS

   BUILDING - DROP TABLESPACE STATEMENTS

   BUILDING - DROP TABLE STATEMENTS

   BUILDING - DROP INDEX (UNIQUE ONLY) STATEMENTS

   BUILDING - DROP INDEX (NON-UNIQUE ONLY) STATEMENTS

   BUILDING - DROP INDEX (OBSOLETE ONLY) STATEMENTS

7. At the following prompt, enter the maximum number of indexes for a single job.

   ENTER THE MAXIMUM NUMBER OF INDEXES TO BE INCLUDED IN A SINGLE REBUILD JOB. (PRESS ENTER TO ACCEPT DEFAULT OF 3, MAXIMUM IS 10)

   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—reducing resource requirements but building fewer indexes in parallel.

   The JCL generation for the Gen Primary Index Rebuilds runs approximately 40 minutes. The following messages appear as the generation runs:

   *** => GENERATING INDEX REBUILD JOBS FOR INDEXES TO BE REBUILT "***BEFORE***" GEN_PRIMARY DATA MIGRATION IS RUN

   "NEW-SCHEMA" - SIEBEL 7.7 BUILDING "PRE"-GEN_PRIMARY INDEX REBUILDS (GPPREIX)

   DSN=DSNHLQ.SIEBEL.SCINDX.GPPRE.JCL

   DSN=DSNHLQ.SIEBEL.SCINDX.GPPRE.SQL

   The number of generated index rebuilds appears.

   The following message appears:

   NUMBER OF INDEX REBUILD JOBS BUILT = 2226

   PROCESSING COMPLETE...

   NOTE:  Index count varies according to your upgrade path and the number of indexes included in each job.

8. Press Enter when three asterisks (***) appear.

   The Index Menu reappears. The panel ID is SBLIDXP.