| I think what the code in SCHED CHECK/ALL does is to cause the scheduler
to read every job record in the database (in job # order), and "process" it,
doing any neccessary actions (this includes re-checking schedule and all
dependencies for each job, etc.) If a job is encountered during the
check that "should" run, then it will be run. The SCHED CHECK operation
involves a lot of processing and if you have a lot of jobs, it can take
a while. If, while the check is running, run is requested for a job
via the user interface, and the job hasn't been processed yet by the
"check" command, then the job will be run as soon as the scheduler gets
to that job number during processing. If the job wasn't runnable
at the moment it was processed by SCHED CHECK, and then becomes
runnable while SCHED CHECK is still processing, (for example if run was
requested via the user interface, dependencies complete, or the
scheduled time arrives) than it won't run untill SCHED CHECK completes
and normal processing resumes.
In theory there should be no need to run $ SCHED CHECK command at
all - in fact it wasn't documented in early versions of the scheduler.
(Because of the large amount of overhead and job processing delay)
Are they doing this for any particular reason ?
|