onoverlap
Defines the action that the scheduler must take on a
job stream instance that is about to start but the previous instance
has not yet completed. The options are to:
- Start the job stream instance anyway
- Wait for the previous instance to complete.
- Cancel running the new instance altogether
Syntax
onoverlap parallel|enqueue|donotstart
Arguments
- parallel
- The next instance is started regardless, and the two instances run concurrently. This is the
default behavior for the job stream if you do not use the
onoverlapkeyword. - enqueue
- The next instance is not started until the previous instance has completed its run.
- donotstart
- The next instance is not started at all. At planning time, a new dependency is added to the previous instance. The new instance will start when the dependency is released, provided that the dependency is released within four minutes of the previous instance start time. If this timeout is exceeded, the new instance does not start.
In the following example, an instance of job stream JS_0415 is run every 10 minutes. In case an
instance has not completed when the next one is to start, the next instance waits for its
completion.
SCHEDULE MDM005#JS_0415
ON RUNCYCLE ACCTRC 06/16/2018
( SCHEDTIME 1445 DEADLINE 1530 EVERY 0010 EVERYENDTIME 1515 )
ONOVERLAP ENQUEUE
:
MDM005#JS_0415
END