Adjusting the Jobs 

It is possible to adjust the job skeletons that are used in the DBA planning calendar for Upload to suit your individual requirements. This allows you to use brand new features of DB2 utilities that are useful for your shop.

To adjust a job skeleton for the DBA planning calendar, proceed as follows:

       1.      Call transaction DB2J (JCL Management Entry).

       2.      Choose list all jobs to display all jobs.

       3.      Select a job whose skeleton you would like to modify. The names of the jobs are self-explanatory, for example the skeleton of the RUNSTATS job for an individual table (or tablespace) is called RUNSTATS_TABLE.

The job must first be selected in the list and then chosen by selecting the button Select job.

       4.      Choose Change to go to an editor in which you can make changes to the skeleton.

If the job name does NOT start with UTILS:, the job is suited for upload of a JCL job. There, any meaningful addition that will generate a syntactically correct JCL Job is allowed. However, keep the rough structure of the job, as the internal parsing routines will otherwise not be able to deal with the skeleton.

If the Job name starts with UTILS: the utility template will be used for stored procedure execution. Since this is no JCL, only the utility name with valid utility options can be inserted there. Do not insert any JCL cards please.

The following is an example of a section of the RUNSTATS_TABLE skeleton:

RUNSTATS TABLSPACE $DB.$TS

   TABLE($TB)

   SAMPLE($SAMP)

   COLUMN(ALL)

   INDEX($IX)
   SHRVLEVEL(CHANGE)

To use the history option, you can change the skeleton here as follows:

RUNSTATS TABLSPACE $DB.$TS

   TABLE($TB)

   SAMPLE($SAMP)

   COLUMN(ALL)

   INDEX($IX)
   HISTORY ALL

   SHRVLEVEL(CHANGE)

       5.      Save the changes. They will come into effect the next time the relevant job is run.

Please be aware that the stored procedure templates will only come into existence after the first job submission (not upload) in Planning Calendar (Transaction DB13). If you wish to protect your changes to stored procedure templates against interference with SAP Support Packages, you can do so in transaction DB2J, button Profile Parameters.