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

Restarting Failed Jobs on the Mainframe

Upgrades: All upgrades.

Environments: Development (mainframe-centric) environment and Production environment.

This topic is part of an upgrade process. See How to Perform the Upgrade.

This topic describes how to restart jobs that fail when you are performing a mainframe-centric upgrade.

To restart a failed job on the mainframe

1. Identify the job that failed under the SDSF exit (job status).

   If you are using Siebel-scheduling, you can find the name of the job that failed using option 6: JOB LOG - DISPLAY JOB STATUS (SIEBEL SCHEDULED MODE) on the SBLUPG78 panel. See Viewing the Siebel Job Log Status for further information.

2. Determine the reason the job failed. You can determine the reason for the job failure by selecting the job on the SDSF output queue panel using the s action character.
3. Correct the problem.

   If a job fails because of an SQL error, fix the problem in the appropriate SQL PDS member. For example, for PRESCHM jobs, you can locate the relevant SQL PDS member in the DSNHLQ.SIEBEL.PRESCHM.SQL data set. You can also find information about which member corresponds to a failed job using option 6: JOB LOG - DISPLAY JOB STATUS (SIEBEL SCHEDULED MODE) on the SBLUPG78 panel.

   NOTE:  Contact Siebel Technical Support if you need help in performing these tasks or if you require confirmation that the tasks that you are about to run are correct.

4. Once the problem has been identified and corrected, restart the job. You can do this by selecting the job that failed on the SDSF output queue using the SJ action character. This will automatically call up the next scheduled job allowing the upgrade process, for example PRESCHM, to continue.