Bookshelf Home | Contents | Index | PDF     

Upgrade Guide for DB2 UDB for z/OS > Upgrading a Database from the Mainframe > Preparing the Schema and JCL Files on the z/OS Host >

Unpacking the Unload and Load Control Cards and Executing the DDL

Complete the following procedure to unpack the unload and load cards and execute the DDL.

To unpack, unload/load, and execute the DDL

  1. On the Siebel Upgrade Main Menu, select option 3: SCHEMA/JCL - BUILD DDL AND JCL-PREP FOR UPGRADE.

    The SCHEMA/JCL MENU appears. The panel ID is SBLUPGP.

  2. On the Schema/JCL Menu, select option 1: PDS/SCHEMA/VERIFICATION UTILITIES.

    The Utilities Menu appears.

  3. On the Utilities Menu, select option 0: BUILD/POPULATE UNLOAD/LOAD PDS DATASETS (UNPACK02).

    This places you in edit mode for PDS dataset member: DSNHLQ.SIEBEL.INSTALL.JCL(UNPACK02).

  4. Run the job using the JCL in dataset: DSNHLQ.SIEBEL.INSTALL.JCL(UNPACK02).

    This job populates (unpacks, using IEBUPDTE) the unload and load control cards into members in their corresponding PDS dataset. The DDL files are output (using IEBGENER) to sequential files.

  5. Verify that the job ran successfully, RC=0.

    The JCLTEST return code should be FLUSH. If you do not see the FLUSH return code, you can verify the condition codes by searching for the condition code IEF206I.

  6. After submitting the job, enter cancel on the command line or press PF3 to save changes.
  7. After the batch unpack02 (option 0) job has run successfully, select option 1: CUSTOMIZE UNLOAD/LOAD FOR TABLES W/CLOB COLUMNS (CLOBCOPY).

    If the source system has no CLOB columns on any tables, one of two message types appears:

    • A message box that indicates that no CLOB tables exist.
    • UTL0033: CLOB CUSTOMIZATION NOT REQUIRED FOR upgtype UPGRADE PATH.

      If CLOBs exist on the source 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 dataset:

    DSNHLQ.SIEBEL.INSTALL.JCL(CLOBCOPY)

  8. Submit the job and verify that it ran successfully, RC=0.
  9. On the Utilities Menu, select option 2: CREATE DB2 SCHEMA (DB, TABLESPACE, TABLE, UNIQUE INDEXES, VIEW).

    This places you in edit mode for PDS dataset member: DSNHLQ.SIEBEL.INSTALL.JCL(SCHEMA01).

    NOTE:  You need to verify the DDL before running the following job.

  10. Run the job using the JCL in dataset: DSNHLQ.SIEBEL.INSTALL.JCL(SCHEMA01).
  11. Verify that the job ran successfully, RC=0.
  12. After submitting the job, enter cancel on the command line or press PF3 to save changes.

    NOTE:  Verify that the DDL creation (the job submitted in Step 9) was successful before continuing with the upgrade.

  13. Select option 3: CREATE TEMP/WORK TABLE SCHEMA (3 SETS: TMPTAB00, 01 AND 02).

    A message that describes the process for creating the Temp-Tables appears. This process involves being placed in edit mode three times on different PDS TMPTABnn members in the INSTALL.JCL library:

    • TMPTAB00
    • TMPTAB01
    • TMPTAB02

      You receive an edit-mode message each time this process occurs. After accepting the message, run a batch job.

      The messages have the following format:

      1. YOU WILL NOW BE PLACED IN EDIT MODE FOR TMPTAB00 ...PRESS ENTER TO CONTINUE.

      NOTE:  The SIEBTMP1 database in DSNHLQ.SIEBEL.TMPTAB* is a temporary database. You should be authorized to create this database. You can rename it in these members in accordance with your organization's naming standards.

  14. At the edit-mode message for TMPTAB00, press Enter.

    This places you in edit mode for PDS dataset and member DSNHLQ.SIEBEL.INSTALL.JCL(TMPTAB00).

    1. Run this job using the JCL in dataset DSNHLQ.SIEBEL.INSTALL.JCL(TMPTAB00).

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

    2. Verify that the job ran successfully, RC=0.

      The JCLTEST return code should be FLUSH. If you do not see the FLUSH return code, you can verify the condition codes by searching for the condition code IEF206I.

    3. After submitting the job, press PF3 to save changes.
  15. At the edit-mode message for TMPTAB01, do the following:
    1. Press Enter.

      This places you in edit mode for PDS dataset and member: DSNHLQ.SIEBEL.INSTALL.JCL(TMPTAB01).

    2. Run this job using the JCL in dataset DSNHLQ.SIEBEL.INSTALL.JCL(TMPTAB01).

      This job creates a log table used by the upgrade process to log Unload jobs on the source subsystem. This table is used only if you are using Siebel Logging and Scheduling.

    3. Verify that the job ran successfully, RC=0.

      The JCLTEST return code should be FLUSH. If you do not see the FLUSH return code, you can verify the condition codes by searching for the condition code IEF206I.

    4. After submitting the job, press PF3 to save changes.
  16. At the edit-mode message for TMPTAB02, do the following:
    1. Press Enter.

      This places you in edit mode for PDS dataset and member: DSNHLQ.SIEBEL.INSTALL.JCL(TMPTAB02).

    2. Run this job using the JCL in dataset DSNHLQ.SIEBEL.INSTALL.JCL(TMPTAB02).

      This job creates a log table used by the upgrade process to log selected target subsystem jobs. This table is used only if you are using Siebel Logging and Scheduling.

    3. Verify that the job ran successfully, RC=0.

      The JCLTEST return code should be FLUSH. If you do not see the FLUSH return code, you can verify the condition codes by searching for the condition code IEF206I.

    4. After submitting the job, press PF3 to save changes.
    
Upgrade Guide for DB2 UDB for z/OS