The printing of job summaries is controlled primarily by the JOBSUMMARY task attribute. To cause job summary printing, you can assign a value of UNCONDITIONAL, and to prevent job summary printing, you can assign a value of SUPPRESSED. To cause conditional printing of job summaries, you can use either of two values: ABORTONLY or CONDITIONAL. Either of these values causes job summary printing if the job or any of its tasks terminate abnormally. The difference between the two values is that the CONDITIONAL value also causes job summary printing if the job has any printer backup files associated with it or if a compiler task encounters syntax errors.
-
If the NOSUMMARY option of the OPTION task attribute is set, then a JOBSUMMARY task attribute of DEFAULT is interpreted as CONDITIONAL.
-
If the NOSUMMARY option of the OPTION task attribute is reset, then the Print System JOBSUMMARY option controls the job summary printing. The Print System JOBSUMMARY option is set or reset through the PS DEFAULT system command. The JOBSUMMARY option can specify any of the following values: CONDITIONAL, UNCONDITIONAL, SUPPRESSED, or ABORTONLY.
If the JOBSUMMARY task attribute has a value of DEFAULT, then job summary printing is controlled by either of two types of defaults.
A job summary can be printed for any WFL job that compiled successfully, as well as a job that failed to compile. This is true even if the job never ran because no job queue would accept it or because an operator discontinued the job while it was queued.
The conversion of job logs into job summaries for printing is handled by visible independent runners with the name JOBFILE/CONVERTER. These processes are visible in the mix so that you can monitor their resource usage.
