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

AS/400 jobs
AS400 - job scheduling
HI My business requirement is that i need to schedule my job,when all the EOD jobs are completed. how can i know that eod jobhs are completed are not? can anyone help me out in writing the cl program for this requirement. Thanks

Software/Hardware used:

Answer Wiki

Thanks. We'll let you know when a new response is added.

if possible, place all of your end of day jobs in a single-threaded Job Queue and submit your job last.

this way, ALL of the jobs in the single-threaded jobq will complete before your job can become active.


Discuss This Question: 5  Replies

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • TomLiotta
    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
    125,585 pointsBadges:
  • Futymed
    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
    10 pointsBadges:
  • TomLiotta
    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
    125,585 pointsBadges:
  • Splat
    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.
    12,915 pointsBadges:
  • Yorkshireman
    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...
    6,085 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: