Joined: 06 Jun 2008 Posts: 8339 Location: Dubuque, Iowa, USA
How can we tell which job scheduler you are using? If you are referring to JES3 by mentioning the JTS parameter, then you need to know the JTS parameter is NOT used for scheduling.
Furthermore, neither JES2 nor JES3 really have any way to schedule jobs. You can use dependent job control (DJC) in JES3 to "schedule" jobs (and with the latest release of z/OS, JES2 has a similar capability), although DJC is a VERY limited job scheduler -- it cannot schedule by time, and when jobs don't behave by having JCL errors or abends, the requirement is to flush the entire network and resubmit it to the system. This is why companies buy job schedulers such as CA-7, JOBTRAC, TWS, and so forth.
Joined: 03 Oct 2009 Posts: 1786 Location: Bloomington, IL
Robert Sample wrote:
when jobs don't behave by having JCL errors or abends, the requirement is to flush the entire network and resubmit it to the system.
It's possible to control this behavior with the ABNORMAL and NORMAL parameters of the JES3 NET statement. At my last client, we had a tool that generated quite elaborate DJC networks. If a job abended (which for a variety of reasons they often did), the network was suspended but not flushed; the solution was to resubmit the corrected job with the same NET statement as the abended one; when it completed successfully, the network resumed from where it had been suspended.
That said, I agree that a scheduler is preferable to DJC.