When a user submits a batch job, the job gathers information from
several system objects before it is placed on a job queue.
- A user submits a job.
- The job searches for job attributes. If the job attributes are not found
on the Submit Job (SBMJOB) command, the job looks in the
job description (specified on the SBMJOB command), the
current user's user profile, and the currently active job (the job issuing
the SBMJOB command).
Note: Similar to interactive job initiation,
you can specify in the job description to use the user profile. The user profile
can specify to use a system value to find certain job attributes.
- Once the job has all of its attributes, it resides on the job queue.
- When the subsystem is ready to handle a job, it looks for jobs in the
job queues (those that the subsystem has allocated).
- Then, like interactive job processing, the subsystem checks the job description
for the routing data.
- The subsystem uses the routing data to find a routing entry. The routing
entry provides information about which pool the job will use, which routing
program will be used, and from which class the job will get its run-time attributes.
- After this information is obtained, the routing program is run. If you
use QCMD, QCMD will carry out the SBMJOB command.
It runs the command specified on the CMD or RQSDTA parameter.