Bookshelf Home | Contents | Index | PDF     

Upgrade Guide for DB2 UDB for z/OS > Upgrading a Database from the Mainframe > Preparing the z/OS Host Environment >

Preparing for Table Creation (PRET) on the Source Database

The PRET (pre-table) jobs are run against the source tables prior to the beginning of the upgrade. There are two types of PRET jobs: jobs that you submit manually and jobs that run automatically. The manual PRET jobs perform the following tasks (this list varies according to your upgrade path):

  • Determine whether there are clobs in the schema
  • Query catalog tables for clustering index information
  • Deletes all rows from the S_DOCK_TXN_LOG and S_ESCL_REQ tables.

The automatic jobs drop some indexes, rename table(s) and add columns to tables. If you are using Siebel Scheduling, the automatic jobs use the unique job name prefixes you specify in Adding Jobcards to All PRET Jobs.

A small number of source tables are altered by the PRET step—new columns are added— but user data in the source database remains untouched. You might, however, want to run back-up (unload) jobs on the source tables that will be altered by the PRET jobs.

Complete the following procedures to prepare the source database to generate unload, load, and schema files:

Accessing the PRET Upgrade Processes Menu

Complete the following procedure to access the PRET menu from where you can choose options that will modify the source database.

Navigate to the PRET menu

  1. On the Siebel Upgrade Main Menu, select option 2: PRET UPGRADE PROCESSES.

    The PRET Upgrade Processes menu appears. The panel ID is SBLPRETP.

  2. Enter the appropriate number for the PRET job you want to perform and press Enter.

    To return to the PRET Upgrade Processes menu, press PF3.

Adding Jobcards to All PRET Jobs

Perform the following procedure to add job cards to all PRET jobs and to choose your preferred job scheduling method (Siebel scheduled or vendor scheduled). Changing the job name prefixes to a unique value makes it easier to identify your jobs in the queue.

Ensure that your job card follows your organization's standards.

To add jobcards to all jobs

  1. On the PRET Upgrade Process menu, select option 1: ADD JOBCARDS TO PRET JOB TYPES.
  2. When you are prompted to enter the type of scheduling for the PRET processes, enter 1: Siebel Scheduled or 2: Vendor Scheduled. For information about choosing a scheduler, see Executions of Jobs Using Siebel-Scheduled Mode or Vendor-Scheduled Mode.

    CAUTION:  Choose your scheduling mode carefully. Once you select a a scheduling mode for PRET, you cannot change it.

This option builds job cards for the PRET and pretfins job types. The pretfins jobcards are only built if you are upgrading a Siebel Industry application. If you executed Household scripts on the midtier and transferred those files to the z/OS host, household jobcards are also built (no messages are displayed).

During the Schema/JCL (JCL-Prep) phase you will again be prompted to select Siebel- or Vendor-scheduled Mode. You can select a different scheduling mode than what you selected during the PRET process.

Generating and Dropping Interface Tables

Perform the following procedure to generate and drop interface tables from the source database.

NOTE:  Perform this procedure only during the production environment upgrade. For information on generating and dropping interface tables during a development environment upgrade, see Preparing EIM Tables for Upgrade.

To generate and drop interface tables

  1. On the Siebel Upgrade Main Menu, enter 2 to generate and drop interface tables from the source system.

    This places you in edit mode on JCL member PRETIDRP for dataset DSNHLQ.SIEBEL.INSTALL.JCL.

  2. Enter sub on the command line and press Enter to submit the job using the JCL in dataset DSNHLQ.SIEBEL.INSTALL.JCL(PRETIDRP).
  3. After submitting the job, review the output in SDSF or another job output facility to verify that the job ran successfully.
    1. Verify that all steps in this job contain an acceptable return code:
      • RC=0 or RC=4 indicates the job was successful
      • RC=98 indicates that this job has already been run, so there is nothing to drop. RC=98 may be acceptable, but you should verify that all EIM interface tables do not exist under the source tableowner.
    2. Verify 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.
  4. After submitting the job, enter cancel on the command line or press PF3 to save changes.

Running Table Edit Maintenance Jobs

Perform the following procedure to run the table edit maintenance jobs called PRETEDIT.

To run PRETEDIT jobs

  1. On the Siebel Upgrade Main Menu, select option 3: PRETEDIT JOBS. This places you in edit mode for the PDS dataset DSNHLQ.SIEBEL.PRETEDIT.JCL.

    NOTE:  Jobs from this step can run in parallel.

  2. Submit each PDS member job using the JCL in dataset DSNHLQ.SIEBEL.PRETEDIT.JCL.
  3. After all jobs are submitted, review the output in SDSF or another job output facility to verify that the job ran successfully.
    • All steps must contain an acceptable return code: RC=0 or RC=4.
    • 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, enter cancel on the command line or press PF3 to save changes.

Running Table Creation Maintenance Jobs

Perform the following procedure to run the table creation maintenance jobs called PRET.

To run the table creation maintenance jobs

  1. On the Siebel PRET menu, select option 4: PRET - PRET JOBS.

    This places you in edit mode for the PDS dataset DSNHLQ.SIEBEL.INSTALL.JCL(SUBPRET).

    NOTE:  If you are upgrading a Siebel Financial Services (FINS-SIA) application, you must first complete option 4: PRET - PRET JOBS. Once you have completed this option, you need to select option 5: PRETFINS - PRETFINS JOBS. This option places you in edit mode for the PDS dataset DSNHLQ.SIEBEL.INSTALL.JCL(SUBPRETF).

    This job submits the first PRET job. If the first job is successful, it submits the dependent jobs. This process continues until all PRET jobs are run.

    CAUTION:  Each job must run serially due to dependencies. If a single job fails, the process stops until the failed job is corrected and run successfully.

  2. After all jobs have run, review the output in SDSF or another job output facility to verify that the job ran successfully.

    All steps must contain an acceptable return code: RC=0 or RC=8.

    The JCLTEST or JCLTEST8 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, enter cancel on the command line or press PF3 to save changes.

NOTE:  After successfully completing this task, continue with the upgrade on the midtier.

    
Upgrade Guide for DB2 UDB for z/OS