See, that's one way to handle it. Another, is to use the GMT (or UCT) as the starting point, and represent the local time from there. In your scenario, there is no way to know exactly how long the process took. With the other way it is simple math against UCT.
++
Dennis
++
"A lie can travel half way around the world while the truth is putting on its shoes."
-- Mark Twain




Sent from my Galaxy tablet phone. Please excuse my brevity.
For any grammatic/spelling errors, there is no excuse.
++


"Luis Rodriguez" <luisro58@xxxxxxxxx> wrote:

Dennis,

Suppose you have a process that begins at, say 01:00am and runs in less
than an hour. If you change your clock back one hour, it could happen
that
your process would end before it begins (FTL neutrinos anyone? :-) )

To avoid that, beginning (IIRC) V5R3, the systems "slows down" the
clock,
so it just does the 1-hour time adjust in, say, two hours. After that,
the
clock starts to run at the normal rate.

Hope this makes sense.

Regards,


Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries
--




On Mon, Nov 7, 2011 at 10:44 AM, Dennis <iseries@xxxxxxxxxxxx> wrote:

Hopefully that "gradual" part is incorrect, and the system - like the
rest
of the non-personal computer systems in the world - merely
"decodes/represents" the time differently rather than actually
changing any
clock. Nowadays, most systems use the applicable UCT offset to
determine
what the local time is/was.

Can anyone here confirm the internal process?
++
Dennis
++
"I'm a great believer in luck, and I find the harder I work the more
I
have of it."
-- Thomas Jefferson




Sent from my Galaxy tablet phone. Please excuse my brevity.
For any grammatic/spelling errors, there is no excuse.
++


"Jerry C. Adams" <midrange@xxxxxxxx> wrote:

An off-list reply mentioned that DST support may not have been added
until
V5R3 and enhanced in V5R4. And a search of PTF cover letters shows
nothing
older than 5.3.

The "nice" thing about having the system change the time, especially
in
the
fall, if I recall correctly, is that the adjustment is gradual, not
instantaneous like I did. A quick change could have an adverse
effect
on
things like journals. But ya do what ya gotta do, I guess.

Jerry C. Adams
IBM i Programmer/Analyst
Everything that can be invented, has been invented. -Charles Duell,
U.S.
Patent Office Director (1899)
--
A&K Wholesale
Murfreesboro, TN
615-867-5070

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Paul Nelson
Sent: Monday, November 07, 2011 8:05 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: DST PTF(s) for V5R1?

I don't recall which release introduced the link to an SNTP server,
but
you
could whip up a program to change the time for you. Stick it in the
job
scheduler to run on Sunday mornings, and have it read a 1 record
file
containing the actual dates to increase or decrease QHOUR. Plug in
the
dates
in January, and you're done for the year.



Paul Nelson
Office 512-392-2577
Cell 708-670-6978
nelsonp@xxxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jerry C. Adams
Sent: Monday, November 07, 2011 7:25 AM
To: Midrange-L
Subject: DST PTF(s) for V5R1?

I'm pretty sure that this is a futile question, but, hey, nothing
ventured.



Yesterday afternoon (Sunday, 6 November) I checked our iSeries
machine,
which is running V5R1. The time had not changed. Since no one
works
on the
system on weekends, I changed the time manually. Is there a PTF
*still*
available for 5.1 regarding Daylight Savings Time? Our office admin
and I
were trying to remember if anyone had to do anything for DST back in
the
Spring, but I'm old and she's blonde, ergo neither of us could
recall
anyone
doing a manual change.



I suspect that I'm stuck with changing the time manually from here
on
out.



Jerry C. Adams

IBM i Programmer/Analyst

The game was closer than the score indicated. -Dizzy Dean on a 1-0
ball
game

--

A&K Wholesale

Murfreesboro, TN

615-867-5070



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.