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 >

Preparing the Nonadditive Schema SQL and JCL Templates and Executing the DDL

Perform the following procedure to prepare the nonadditive schema files.

To prepare nonadditive schema SQL and JCL templates

1. Go to the Siebel Upgrade Main Menu by entering the following command and pressing Enter:

   TSO SBLUPG81

   The panel ID is SBLUPG8P.

2. On the Siebel Upgrade Main Menu, select option 1: FILE GENERATION and press Enter. The Staging Database File Generation Menu is displayed. The panel ID is SBLSFGP.
3. On the Staging Database File Generation Menu, select option 5: Process Non-Additive Components, and press Enter:
   • If you are performing a development environment upgrade, the Staging Database Non-Additive Schema Menu is displayed. The panel ID is SBLSADNP.
   • If you are performing a production environment upgrade, you are first prompted to confirm that you have applied and completed all planned additive changes. Enter Y and press Enter and the Staging Database Non-Additive Schema Menu is displayed.
4. On the Staging Database Non-Additive Schema Menu, select option 0: Apply JCL/Schema Template Parms, and press Enter.

   Messages are displayed indicating that changes are being applied to the Unload and Load data sets.

5. On the Staging Database Non-Additive Schema Menu, select option 1: Populate JCL/Schema PDS Datasets, and press Enter.
6. Submit the JCL in data set DSNHLQ.SIEBEL.INSTALL.JCL(UNPACK02).

   This job unpacks the JCL and schema files into members in their corresponding PDS data set.

7. Verify that the job ran successfully.

   Review the output in SDSF or another job output facility. Verify that the return code is 0 and that the JCLTEST return code is FLUSH. If you do not see the FLUSH return code, you can verify the condition codes by searching for the condition code IEF206I.

8. On the Staging Database Non-Additive Schema Menu, select option 2: Customize CLOB Unload/Load cards, and press Enter.

   If the target database does not have CLOB columns on any tables, one of two message types appears:

   • A message box that indicates that this step is not required.
   • UTL0033: CLOB CUSTOMIZATION NOT REQUIRED FOR upgtype UPGRADE PATH.

     If CLOBs exist on the target system, a series of messages appear. Read them carefully. This option will run in foreground and then place you in edit mode in the following data set:

   DSNHLQ.SIEBEL.INSTALL.JCL(CLOBCOPY)

9. Submit the job and review the output in SDSF or another job output facility. Verify that the return code is 0 or 4 and that the JCLTEST return code is FLUSH. If you do not see the FLUSH return code, you can verify the condition codes by searching for the condition code IEF206I.
10. On the Staging Database Non-Additive Schema Menu, select option 3: Add Jobcards & Siebel Logging to Unloads/Loads and Data Migration Jobs, and press Enter.

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

    You can choose to modify the Unload/Load and data migration jobs in either TSO foreground mode or batch mode. It is recommended that you perform the procedure in batch mode.

    In foreground mode, messages are displayed on the screen as the JCL-Prep progresses. This mode will lock up your session until the option is complete. Each option can take an extended period of time (more than thirty minutes), depending on the user's dispatching priority.

    NOTE:  It is recommended that you perform the procedure in batch mode. Before doing so, make sure you modify the ISPF batch procedure, dsnhlq.siebel.proc(ispbat), to your installation standards. If you perform the procedure in foreground mode, make sure your logon region size is at least 7092.

11. Enter Y to confirm that the ISPF batch proc is correctly configured, and press Enter.
12. Press Enter again and you are placed in edit mode in the following data set:

    DSNHLQ.SIEBEL.INSTALL.JCL(SBLJCL23)

13. Submit the job and review the output in SDSF or another job output facility. Verify that the return code is 0 or 4 and that the JCLTEST return code is FLUSH. If you do not see the FLUSH return code, you can verify the condition codes by searching for the condition code IEF206I.

    NOTE:  If you chose to perform the upgrade using Siebel-Scheduled mode, the data migration JCL includes a jobstep that automatically submits dependent jobs in the data migration flow until all jobs are completed for that data migration job type.