Programmer Utilities › Introduction › Overview › Compile Preprocessor › General Considerations for the Compile Preprocessor › Preprocessor Job Entries

Preprocessor Job Entries

Whether the preprocessor is invoked for a particular job is controlled by the job’s routing data. Which preprocessor options are run depends on the job’s switch settings. Both of these are described below.

Routing Data Required to Invoke the Pre-processor

Once the utility is installed in a subsystem, the preprocessor runs on all compilation requests (that is, CRTRPGPGM, CRTCLPGM, CRTPF etc.) submitted to the subsystem with the routing data YCRTOVR. Routing data can either be specified on the SBMJOB, TFRJOB or RRTJOB commands, or more conveniently on the job description. For example:

To submit a job that invokes the preprocessor:

SBMJOB RTGDTA(YCRTOVR) RQSDTA(‘CRTRPGPGM DEMO’)

To transfer a job and invoke the preprocessor:

TFRJOB RTGDTA(YCRTOVR) RQSDTA(‘CRTRPGPGM DEMO’)

To reroute a job:

RRTJOB RTGDTA(YCRTOVR) RQSDTA(‘CRTRPGPGM DEMO’)

To change a job description so that all compilations using the job description invoke the preprocessor:

CHGJOBD JOBD(QBATCH) RTGDTA(YCRTOVR)

The routing data on a job description only has to be changed once. When submitting jobs with the SBMJOB command change the routing data parameter to *JOBD. This will ensure that the routing data defined in the job description is used by the SBMJOB command and the preprocessor will be invoked. This is particularly convenient if compilations are submitted using the i OS Programmer’s Menu.