Upgrade Guide for DB2 UDB for z/OS > Upgrading a Database from the Mainframe > Executing the Upgrade on the z/OS Host (Phase 1 of 2) >

Migrating Preschm Data

The PRESCHM jobs migrate pre-7.8 Siebel data to version 7.8 data. Generally, this involves inserting or updating values in the target tables but new indexes may also be created and rebuilt. The PRESCH jobs also create temporary indexes for data migration.

There are optional data migration scripts for eChannel and Household data and for Siebel Financial Services (FINS) applications.

Some of the PRESCHM jobs run independently but others are submitted in a defined order and cannot run until previous jobs have completed successfully; you can run the stand-alone jobs in parallel with those with dependencies. To see the serial flow of the PRESCHM jobs and the PRESCHM job dependencies, look at the PDS member DSNHLQ.SIEBEL.PRESCHM.JCL(@TRIGGER).

To migrate preschm data

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

   TSO SBLUPG78

2. Select option 5: RUN UPGRADE / POST-UPGRADE MAINTENANCE.

   The Siebel Upgrade Job Submission Menu for your upgrade path appears.

   • For Siebel Business application upgrades, the panel ID is SBLRUNHP.
   • For Siebel Industry application (SIA) upgrades, the panel ID is SBLRUNFP.
3. Select option 6: PRESCHM.

   This places you in edit mode for dataset DSNHLQ.SIEBEL.INSTALL.JCL(SUBPSH).

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

   NOTE:  This job automatically submits the first PRESCHM job referenced in dataset DSNHLQ.SIEBEL.EXEC(@PRESCHM).

   • If this job runs successfully, it automatically submits the next dependent job, and so on.
   • This process continues for all PRESCHM jobs. If a job fails, the succeeding dependent job does not get submitted. The automatic job submission sequence terminates.
5. After all PRESCHM jobs are run, verify that each job ran successfully.

   RC=0, RC=4, or RC=8 indicates that the job was successful. RC=8 is associated with jobs that have an X in position 3 of the member name.

   Jobs with an ABEND (end abnormally) U99 or U099 message are jobs that failed.

   If you selected Siebel-Scheduled Mode, this job is logged (as Completed Successfully or Failed) to the target Siebel log table: TARGET_TABLEOWNER.TMP_SBLLOG_TAR.

   NOTE:  You must fix any failed jobs before proceeding with the upgrade. For information on restarting failed jobs, see Restarting Failed Jobs on the Mainframe.

6. Enter cancel on the command line or press PF3 to save changes.
7. View the job status.

   For information on how to view job status if you selected Siebel-Scheduled Mode, see Viewing the Siebel Job Log Status.