Item 1: add the ability to track the first initial scheduled time for a
job and an option to allow a job to run only for MaxRunInitSchedTime
before being canceled
Origin: Thomas Lohman - thomasl@...
Date: 12 March 2013
Status: patch attached
What: Hi, it may be that it is possible to do this another way but
currently if you have a requirement that you want to start a job at time
X, reschedule it on error every Y minutes but also make sure that after
Z hours, the job is canceled no matter what, it doesn't look like there
is a way to ensure that this happens. The MaxRunSchedTime option uses
the time of the last re-scheduling as it's baseline so if you are using
Reschedule On Error then MaxRunSchedTime doesn't accomplish what we
wanted to do. Because of this, I made the following patch to the 5.2.13
source code (see attached unified diff file).
Why: We have a set of jobs that we want to definitely end at a known
time - Z hours after they've been initially scheduled - no matter what
state the job is in.
Notes: If there is another way to accomplish what we need to do then
that would be great.
thanks very much,