I have a scenario where a job abends or fails (which turns "red" in color)
When this happens we continue with the rest of the successor jobs until the schedule completes.

Upon "New Day Process", the abended job stays in the AJF or queue.
How can I delete the job or change the status of the job so it will roll-off upon "New Day Process" without manual intervention. In other words, without manually forcing the job ok. Preferred to do this in batch.

I forgot to mention that when a job abends, several jobs are bypassed before the schedule continues to completion.

If I code do ok on the abended job, it will post and run the bypassed jobs. Perhaps adding a negative dependency in the abended job's "STEPS TAB" before the do ok? I'll try a few things. Meanwhile, any advise?

I would suggest setting up all the out conditions using the STEPS TAB. We can do OK the job on any code, however posting the conditions can be taken care of with different codes on different steps, providing you with a lot of opportunities to handle dependent job streams.

You may use compstat eq 0 in on statement just to add the out conditions. This will add conditions only upon successful completion of the job. You can use another on statement with statement * code * and do OK.
This should be sufficient to accomplish what you are looking for.

I was able to successfully test mulitple scenarios: (For example: JOB1 through JOB5 single thread)

If JOB1 fails, JOB2 and JOB3 are bypassed and JOB4 will continue to JOB5. This was accomplished from the recommended steps tab while posting the conditions with different codes on different jobs.

However, If I DO OK on the abended job (JOB1), the bypassed jobs (JOB2 and JOB3) are released. How can I prevent the successor jobs (JOB2 and JOB3) from running because of a 'DO OK' condition from a predecessor job? Can this be accomplisted? If so, How?

Do not use any out conditions in the normal out conditions tab of job1. Please use on step * compstat eq 0 do condition and then add conditions to job2 and job3. In this case un-necessary adding of condition on DO OK would be avoided.

The color scheme works like this if it is a group scheduling table. It totally depends on the maxwait which decides the stay of gray or red jobs in ajf. If your bypassed jobs have exhausted the maxwait value, then yellow color of table should not be a problem during the roll out process, provided there are no running jobs in the table.

You are absolutely correct! I left the table in a yellow status over the weekend and when I came in on Monday, it had rolled off from an "executing" or yellow status without any jobs executing.

The following have been accomplished:
- Continue with the schedule when an abend condtion is acceptable
- Bypass and skip jobs depending on the job's predecessor and condition
- Use of the Steps tab vs the out/in cond
- Force job OK or complete through Batch
- Hold successors from a "DO OK" Condition
- Roll the schedule from New Day Process

Thank you so much for all the help! This has all been done through batch and will be implemented for automation.

Who is online

Users browsing this forum: No registered users and 2 guests

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum