RE: executing jobs in sequence

Building on this, if you need to re-run a job, the jobs in the job queue
are prioritized.  So the re-run can be submitted to the same queue but
at a higher priority to move it ahead of the others, ensuring all jobs
run in the desired order.

The single-threaded job queue that Lukas mentions is a great thing.  We
use them here for handling things that can only be done one at a time
and for handling long-running batch jobs that would bog down if too many
ran concurrently.


A second option which would be more complex to develop but potentially
nicer to use (depends on your job stream) would be to have a single CL
program drive all of the batch work (either inline or via SBMJOBs) and
have that CL program monitor for errors and enable whatever corrective
measures you require.