Skip to main content
Question

Zeke Data Differs

  • Oct 15, 2026 3:12 PM UTC
  • 1 reply
  • 22 views

Robert Carr

We are running Zeke 7.1 / Zebb 4.0

How do others handle jobs that get a ‘Zeke Data Differs’ that cause the job status in Scheduleview to display ‘FAIL JCL ERROR’.  

We are trying to get a handle on reducing these to lower our ticket count as a result of this error.

Thanks….

1 reply

Paul Wade
Forum|alt.badge.img
  • Rocketeer
  • Oct 22, 2026 8:20 AM UTC

Hi Robert, hopefully my response will prompt others to contribute as well.

The "Zeke Data Differs" condition typically indicates that the JCL or job attributes that Zeke expects do not match what is being presented at submission time. In ScheduleView/Zebb, this is often surfaced as "FAIL JCL ERROR", even though the underlying issue is usually a scheduling definition mismatch rather than a true JCL syntax error. 

You may be able to reduce the number of these incidents by focusing on the root causes rather than simply clearing the failures:

  • Tighten change control around production JCL libraries and Zeke job definitions so they remain synchronized.
  • Identify jobs that frequently generate "Data Differs" and determine whether JCL is being modified outside the normal scheduler maintenance process.
  • Review any symbolic variables, overrides, or automated JCL-generation processes that may be causing the submitted JCL to differ from the stored Zeke definition.
  • Where appropriate, update the Zeke definition after approved JCL changes so the scheduler's baseline matches production.

The key question is whether these failures represent legitimate configuration drift that should be investigated, or expected differences caused by local operational practices. Reducing ticket volume might come down to identifying and eliminating the recurring sources of JCL drift rather than suppressing the error itself.

It might be worth providing an example on a support ticket of a job receiving "Zeke Data Differs", including the differences being reported, so we can help determine whether there is a configuration adjustment or operational practice that could reduce the frequency of these failures.