4.11.3 Submit the Process to Batch
When the option to submit a process to batch has been used a screen similar to that following is always the last displayed before the job is submitted:
|
EXAMPLE Print Ledger Account History
Process : EXAMPLE - Print Ledger Account History
Submit this job . . . . . . . . . . . . . . . . . . YES YES, NO
Using Job name . . . . . . . . . . . . . . . . . . EXAMPLE Job description . . . . . . . . . . . . . . . *LIBL/QBATCH Job queue . . . . . . . . . . . . . . . . . . *JOBD Output queue . . . . . . . . . . . . . . . . *LIBL/QPRINT
Select functions to be executed :
Sel Function Usable Description _ XXXXXXX XXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX _ XXXXXXX XXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX _ XXXXXXX XXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Fnn=Help Fnn=Exit Fnn=Cancel Fnn=Messages
|
This screen requests that the submit request be confirmed and allows the job name, job description, job queue and output queue to be changed from their default values.
In addition the individual functions that make up the process are displayed. All functions that are to be executed in batch should be chosen. Each function chosen results in the submission of one batch job. Thus if six functions are chosen, six batch jobs will be submitted.
There is no harm in submitting a function to batch that attempts to "talk" to a workstation. In such cases the function will abort during initialization and messages on the job log will indicate the cause of the problem.
Generally processes and/or functions designed to run in batch have a different form to those designed to run interactively (i.e. from a workstation).
Input Options
The following input options apply when specifying details of a process that is to be submitted to batch:
Submit This Process to Batch?
Refer to Submit This Job? in .
Job Name
Refer to Job Name.
Job Description
Refer to Job Description.
Job Queue
Refer to Job Queue.
Output Queue
Refer to Output Queue.
Sel/Function/Usable/Description
This list displays details of all functions that are associated with the process and are directly accessible from the process main menu (refer to the 4.18 Function Control Table for more details of excluding functions from the process main menu).
The function name and description are displayed along with an indication of whether the function is currently usable (i.e. compiled and ready to be executed). Normally a non-usable function would only be submitted if the compile job has been previously submitted but had not completed execution yet.
Where more functions exist than can be displayed, use the roll keys to scroll backwards and forwards through the list of all functions.
A function is selected for batch execution by entering any non-blank character beside it in the column headed "Sel". Each function selected for submission to batch results in one batch job being submitted. Thus if 6 functions are chosen 6 batch jobs will be submitted.
The function chosen becomes the "initial" function that is executed in the batch job that is submitted. Whether or not it is the only function that is executed depends upon how the function is written (e.g.: uses TRANSFER or CALL commands) and of course on the function control table entries associated with the function.