Siebel Database Upgrade Guide for DB2 for z/OS > Planning a Siebel Database Upgrade >

About Executing Jobs Using Siebel-Scheduled Mode or Vendor-Scheduled Mode

Before you perform a production upgrade, determine whether you will execute the jobs using Siebel-provided job scheduling or a third-party vendor scheduler. Choose your scheduling mode carefully, because once you begin an upgrade process under a selected mode, you cannot change your scheduling mode or reverse this decision.

In Siebel Scheduled Mode, the Siebel job scheduler uses job submission EXECs to run the following upgrade jobs:

• Pret
• Pret_FINS
• Household
• Household_FINS
• Preschm
• Preschm-FINS
• Upglss

The Siebel job scheduler automatically submits dependent jobs by their predecessors.

Using Siebel Scheduled Mode, if a job ends abnormally or returns an invalid return code, the upgrade process is halted. You can check the job status by querying the Siebel job log. For further information, see Reviewing the Siebel Upgrade Log Files.

If you use a third-party job scheduler, jobs are not submitted automatically. In this case, you will find it useful to first generate the upgrade scripts using Siebel scheduling to gain an understanding of job dependencies.

NOTE:  Logging is provided for both Siebel-scheduled and vendor-scheduled jobs using a DB2 table. Each job contains a step that checks whether or not all the other steps in the job completed successfully. An SQL UPDATE statement is then executed against the log table specifying the job status.