Comments on: synchronize jobs

By: splat

splat — Fri, 27 Nov 2009 16:14:18 +0000

Last time I needed to do something similar, I used a combination of the single-threaded job queue method and the data area control flag method. This allowed me to make sure the prior job had completed normally before the next job could run (I had a section at the top of the CL to re-submit the job fifteen minutes later if the data area showed the prior job hadn’t completed).

By: jwebb901

jwebb901 — Wed, 15 Feb 2006 10:14:52 +0000

To break your job into 4 pieces and then submit them individualy, is self defeating………now you have all the additional overhead of the job process x 4. One job will process faster than 4, unless of course you have a multi-processor box.

By: rolandt

rolandt — Wed, 15 Feb 2006 09:19:56 +0000

If you create a jobq that only allows one job to run at a time, then submit your jobs to that queue. The system will run the jobs in the sequence submitted, but only one at a time.

By: saratusthra

saratusthra — Wed, 08 Feb 2006 09:03:56 +0000

Not sure exactly what you want to synchronize but to avoid object locks, including DTAARAs and files, the best approach is streaming the jobs into a single-job JOBQ, which is done in the SBMJOB command. After some analysis, the jobs can be arranged sequentially in logical order before being submitted.
This way, a job will finish using objects that may be affected by the next on the queue but there will never be a conflict.
The other way is calling the jobs in the desired order within a CL.

Hope this helps.
Good luck!