On the Submit to batch parameter, the *YES default submits a multi-thread capable batch job. When *NO is specified for the parameter, CMPFILDTA generates a batch immediate job to do the bulk of the processing. A batch immediate job is not processed through a job queue and is identified with a job type of BCI on the WRKACTJOB screen. Similarly, if CMPFILDTA is issued from a batch job whose ALWMLTTHD attribute is *NO, a batch immediate job will also be spawned.
In cases where a batch immediate job is generated, the original job waits for the batch immediate job to complete and re-issues any messages generated by CMPFILDTA. Interactive jobs are not permitted to have multiple threads, which are required for CMPFILDTA processing. Thus, you need to be aware of the following issues when a batch immediate job is generated:
-
The identity of the job will be issued in a message in the original job.
-
Since the batch immediate job cannot access the interactive job’s QTEMP library, outfiles and files to be compared may not reside in QTEMP, even when CMPFILDTA is issued from a multi-thread capable batch job.
-
Re-issued messages will not have the original “from” and “to” program information. Instead, you must view the job log of the generated job to determine this information.
-
Escape messages created prior to the final message will be converted to diagnostic messages.
-
Canceling the interactive request will not cancel the batch immediate job.