Upgrade Guide for DB2 UDB for z/OS > How the Upgrade Works > Job Flow of a Production Database (Mainframe-Centric) Upgrade >

About JCL Job Generation


  • The DSNHLQ.SIEBEL.EXEC data set contains base job cards for all the upgrade jobs. The upgrade process uses these job cards as a base for all jobs of a particular type and then generates an individual job card for each job based on the information in the base card and in the @JOBPREFX member of the DSNHLQ.SIEBEL.EXEC data set.

    For example, the base job card for PRESCHM jobs is JCPRES. An individual job card is created for each PRESCHM job based on information in both of the following:

    • DSNHLQ.SIEBEL.EXEC(@JOBPREFX) - job prefix
    • DSNHLQ.SIEBEL.EXEC(JCPRES) - base job card

      Once job cards have been generated, changing the information in the @JOBPREFX member does not cause job card details to change.

  • Load and Unload job procedures are located in the DSNHLQ.SIEBEL.PROC data set.
  • Some JCL jobs, for example, some Data Migration jobs, have dependencies on other jobs. These jobs are submitted in a specific order, with subsequent jobs only being submitted when the current job has completed successfully. The @TRIGGER member in the relevant JCL data set shows the order in which the jobs are to be submitted, for example, see DSNHLQ.SIEBEL.PRESCHM.JCL(@TRIGGER) for details of the submission sequence for PRESCHM jobs.
Upgrade Guide for DB2 UDB for z/OS