|
We've always journalled where I've worked, so we never wanted to have journal receivers suddenly 'jump back' in time sequence. (Could cause problems in a DR scenario, etc). Plus, when we've had *really* long running batch jobs, it could cause some confusion when the time changes in the midst of the job. For instance, I was going to write a system once that watched when batch jobs ran versus when they normally ran, and notified the operators if a job was late. If the time changed automatically, a system of this type would believe jobs were late when they really weren't. So from a data processing point of view, its always been easier for me to pick when to change the time (both times of the year), rather than have the OS change it for me. Scott "Dare" <oludare@ix.netcom. To: <midrange-l@midrange.com> com> cc: (bcc: Scott Lindstrom/PDC/Pactiv) Sent by: Subject: Re: Daylight savings time midrange-l-admin@mi drange.com 09/16/02 01:43 PM Please respond to midrange-l Hey Scott, R u saying it is not PRATICAL to have this done at the system level by the OS? Dare
As an Amazon Associate we earn from qualifying purchases.
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.