I have two jobs where JOB2 is dependent on JOB1 with a hard EOE dependency in the ZEKE Scheduler.
However, JOB2 was allowed to execute before JOB1 in the same batch cycle.
The log notes JOB1 was dispatched at the proper time, but the JCL did not execute until over an hour later (after JOB2).
In analyzing everything, I noted that while ZEKE has both JOBs listed as CLASS=1, the JCL for JOB1 has CLASS=2.
Could this be why the JCL for JOB1 did not execute until after JOB2?
Would the difference in CLASS allow ZEKE to think the job had completed when it had not?
ZEKE Expert Question: ZEKE allowed jobs to run out of sync
-
- Posts: 1
- Joined: Fri May 03, 2019 2:12 am
- Skillset: Gen and COBOL predominantly
- Referer: Internet
-
- Similar Topics
- Replies
- Views
- Last post
-
- 0
- 1184
-
by stel
View the latest post
Wed Sep 21, 2022 1:06 pm
-
- 0
- 988
-
by biswajit
View the latest post
Mon Mar 03, 2025 8:54 pm
-
- 2
- 2253
-
by Pedro
View the latest post
Tue Feb 27, 2024 4:44 am