×
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.
Roger wrote:
I'm a bit surprised at all these DST issues. Wasn't the OS changed some
time ago to do a clock slowdown or speedup to compensate and not do a flat
jump to new time?
On Tue, Mar 13, 2018 at 1:02 PM, Rob Berendt <rob@xxxxxxxxx> wrote:
The OS, and IBM's job scheduler, were. Not so sure about ROBOT's
scheduler.
I think the thrust of Roger's question is: Why does any scheduling
program (or pretty much any program, period) NOT rely on the system
time?
It's a very reasonable question. I do have a couple of ideas why that might be.
(1) If you don't trust the operating system to handle DST the way
you'd want it handled, then you have to take matters into your own
hands.
(2) If your program has access to the Internet, you might want to rely
on an official time server.
But I do think it's kind of surprising that a program designed solely
for IBM i could get tripped up by DST.
John Y.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
