Re: SNTP client - was RE: How to move forward

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>]

Rob, I don't know about the 11 minute thing. But the TCP9117 messages are 
perfectly in sync.

I am surprised that the TCP9119 at 11:35:08 AM indicates the clock was set 
- you had to have a wide range to allow setting, and this can mess you up. 
it looks like you need to look at QUTCOFFSET - 5 hours difference sounds 
like an offset from Greenwich. The next TCP9119, at 11:37:09 AM, shows it 
did not set the clock.

Regards

Vern

At 07:35 AM 8/22/2003 -0500, you wrote:
> That's what I am trying to get working.  The iSeries Navigator part of
> this.  It even logs the stuff into a file
> /QIBM/UserData/OS400/TCPIP/NTP/QTOT20030821
> where the file changes by date.
> TCP9136 SNTP Client started.
> TCP9116 08/21/03 11:35:08 AM NTP server UTC time is 08/21/03 16:29:05.083.
>
> TCP9117 08/21/03 11:35:08 AM Software clock UTC time is 08/21/03
> 16:38:12.739.
> TCP9119 08/21/03 11:35:08 AM Software clock set = 1 (0 = not set, 1 = set)
>
> TCP9116 08/21/03 11:37:09 AM NTP server UTC time is 08/21/03 16:40:13.924.
>
> TCP9117 08/21/03 11:37:09 AM Software clock UTC time is 08/21/03
> 16:40:13.971.
> TCP9120 08/21/03 11:37:09 AM Software clock adjusted = 0  (0 = not
> adjusted, 1 = adjusted)
> However, I don't understand how the "NTP server UTC time" can vary by over
> 11 minutes in just two minutes time.
>
> V5R2 of iSeries Navigator
> V5R2 of OS/400
> cume=TL03161
> WRKPTFGRP
> PTF Group             Level
> SF99519                  62
> SF99502                   8
> SF99271                   8
> SF99190                  10
> SF99169                  10
> SF99149                   3
> SF99148                   3
> SF99098                   9
> SF99085                   5
> SF99039                   2
>
>
> Rob Berendt
> --
> "They that can give up essential liberty to obtain a little temporary
> safety deserve neither liberty nor safety."
> Benjamin Franklin
>
>
>
>
>
> Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 08/21/2003 06:15 PM
> Please respond to Midrange Systems Technical Discussion
>
>         To:     Midrange Systems Technical Discussion
> <midrange-l@xxxxxxxxxxxx>
>         cc:
>         Fax to:
>         Subject:        SNTP client - was RE: How to move forward
>
>
> BTW, there's an SNTP client (lumped in with TCP/IP "servers" in OpsNav,
> unfortunately) since V5R1, I think. It adjusts software clock - I have
> written a thing that sets the system values based on this - it can run
> every morning. The hardware clock is not the same as the software clock,
> but I think this can link them.
>
> The Consult Line is cool - nice price, too - until you need support, I
> suppose. $495 for the enterprise.
>
> Vern
>
> At 04:49 PM 8/21/2003 -0500, you wrote:
> >IBM doesn't even support SNTP.  We did step by step instructions on it
> and
> >it royally messed up our system time.  Called IBM and the first thing
> they
> >tried to peddle was a Consult line contract.  Stopped me dead right after
> >the word SNTP.
> >
> >Rob Berendt
>
>
> _______________________________________________
> 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.