Comments on: How to know when EOD jobs are done so I can schedule my AS/400 job?

By: yorkshireman

yorkshireman — Tue, 06 Sep 2011 07:00:14 +0000

You could use a data area

THis is a well used technique, but ensure that any failrues / restarts are taken care of. If a job fails, the data area will exist, signifying that EOD is active, and this would prevent a rerun, for instance.
A ‘dissolving’ lock could be arranged, whereby, say, the first thread creates a lock on the dtaara, and any other jobs add a lock, and believe that EOD is active only if a lock exists. If a job fails, its lock dissolves when the session ends…

- There are lots of variations – a file with records per job step, the record locked for the duration of the step.. blah blah…

By: splat

splat — Fri, 02 Sep 2011 15:02:56 +0000

You could use a data area to carry flags indicating the state of the EOD jobs, keeping your job in a delay loop until the the data area indicates the jobs are complete.

By: tomliotta

tomliotta — Thu, 01 Sep 2011 18:24:38 +0000

Jobs will send completion (*COMP) messages to their external message queues when they end. The SBMJOB MSGQ() parameter determines what message queue will get the message. A CL program can use RCVMSG MSGTYPE(*COMP) from that message queue to determine when each job ends.

Tom

By: futymed

futymed — Thu, 01 Sep 2011 09:46:53 +0000

You might also want to Consider using the JOBPTY parameter. The default priority is 5, you could make your job 6 or 9. Thus if anyone submitted a job after your job was submitted, but your job was still on the single-theaded jobq, their job would be run before your job, – Futymed

By: tomliotta

tomliotta — Fri, 15 Oct 2010 23:42:55 +0000

How do you know that all EOD jobs are complete when you look yourself?

If you can tell us what you look for manually, we can tell you how to do it with a program.

A single-threaded job queue is potentially useful, but there might be significant problems.

Tom