Siebel Database Upgrade Guide for DB2 for z/OS > Creating the Siebel Staging Database > Preparing the z/OS Upgrade Environment and Creating the Staging Database >

Verifying JCL Upgrade Jobs

After running each JCL upgrade job, you must verify that the job ran successfully by reviewing the output in SDSF or another job output facility. All jobs must complete successfully before you proceed to the next step.

Once you have run the job Receive XMIT Datasets as described in Preparing the Upgrade Environment and Building the Staging Database, all jobs contain one of the following JCL INCLUDE members to check job step return codes. If condition codes are not met, then the job ends abnormally, with a return code of User 99, and the job must be rerun.

Acceptable return codes for each step of each job is controlled by the following three JCL test condition checks:

• JCLTEST requires that the return code is less than or equal to 4
• JCLTEST0 requires that the return code is 0
• JCLTEST8 requires that the return code is less than or equal to 8

For example, if a job that includes the JCLTEST member generates a return code that is less than or equal to 4, the JCLTEST step is not processed and the JCLTEST return code is FLUSH. If the same job generates a return code that is greater than 4, the JCLTEST step is processed and the job ends abnormally.

Verify that the return code for each job is 0, 4, or 8 (depending on the job) and 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.

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