On Fri, Oct 24, 2014 at 7:13 AM, <rob@xxxxxxxxx> wrote:
There is no need to write a program to go out and check NIST time.
RTM:
http://www-01.ibm.com/support/knowledgecenter/api/content/ssw_ibm_i_72/rzakt/rzaktkickoff.htm
I can't say I combed through it in detail, but from what I can gather
so far, it wouldn't suit my purpose.
1. It requires system configuration. Which for me is a bigger hurdle
than writing code.
2. It seems to me the feature is mainly about keeping the i
synchronized to some standard time. (Or serving *as* the standard
time for other machines.) I'm not interested in synchronization at
all.
3. What I *want* is to see the gradual time adjustment in action. So
I would want to get NIST time every so often, say every 5 seconds (or
more frequently, if the system and the connection can handle it), and
store that in a file. When I come in on Monday, I should see where it
is that the system clock began to deviate from NIST, and where it
reconverged. I should get to see what the documentation means by
"gradual".
For example, I could envision a scheme for the "fall back" change
where starting at 1:00 a.m., each system clock second is really 1.01s,
with gradually lengthening seconds until the height of the time
stretching, where each system clock second is really 3.0s, after which
the seconds gradually get quicker again for a "soft landing" at 2:00
a.m.; or maybe it doesn't "curve" at all, and starting at 1:00 a.m.,
each clock second is exactly 2s, until 2:00 a.m. Chuck's post
suggests the latter, just with different constant factors.
Maybe somewhere in the docs you linked to, there's a way to set up
automatic time requests and logging. If not, then I would have to
write a program anyway.
John Y.
midrange.com
