×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On Tue, Oct 29, 2019 at 1:41 PM Rob Berendt <rob@xxxxxxxxx> wrote:
Actually, as Larry suggested, this ain't IBM's first rodeo and they handle the time change effectively. Read his reply for the details.
I am not suggesting IBM doesn't handle time changes effectively.
Indeed, if the person I was responding to in fact does schedule things
for 1:59 AM, and hasn't experienced those jobs running twice, then
that is itself a demonstration of the ability of the scheduler to
handle time changes "effectively".
However, regardless of what IBM does, there could be *ambiguity* if
you rely on the scheduler. The scheduler can ensure that something
runs exactly once, but it might not make the same choice as you want
regarding exactly *when* to run it. You can sidestep that issue
completely if you avoid scheduling anything in the 0100 to 0300
window.
Even if it's purely for psychological reasons, there is nothing
*wrong* with avoiding that window. If someone doesn't want to step on
cracks in the sidewalk, that's fine. I'm just pointing out where one
of the cracks actually *is* (because they were stepping on it,
apparently unknowingly).
John Y.
midrange.com
