Upgrade Guide for DB2 UDB for z/OS > Database and UI Upgrade Planning > Planning Your Upgrade >

Executions of 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 upgrade jobs and automatically submits dependent jobs by their predecessors. If you plan to use a third-party job scheduler, you will find it useful to first generate the upgrade scripts using Siebel scheduling to gain an understanding of job dependencies.

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 Database Upgrade Log Files.

NOTE:  Siebel logging is not available if you use a third-party job scheduler.