Re: Time off by 6 seconds

Why do it weekly?
I usually set it to every hour - the NTP process is very lightweight, The
chgsntpa (attributes) defaults a no change if off by xx milliseconds, and
it keeps an activity log to see when changed and how much.
It helps when communicating to other systems (and they run ntp as well) to
be able to coordinate when transactions occurred.

Change SNTP Attributes (CHGNTPA)



Type choices, press Enter.



Remote system . . . . . . . . . 'TIME.GOOGLE.COM'



+ for more values



Client autostart . . . . . . . . *YES *SAME, *NO, *YES

Client poll interval . . . . . . 60 1-1440 minutes, *SAME

Client minimum adjustment . . . 20 0-300000 milliseconds...

Client maximum adjustment . . . 20 1-120 minutes, *SAME

Client adjustment threshold . . *MAXADJ 1-7200 seconds, *SAME,
*MAXADJ
Client activity log . . . . . . *CHANGE *SAME, *NONE, *CHANGE,
*POLL
Server autostart . . . . . . . . *NO *SAME, *NO, *YES

Server activity log . . . . . . *NONE *SAME, *NONE, *ALL,
*ERROR
Synchronization required . . . . *NO *SAME, *NO, *YES





Jim Franz

On Mon, Sep 25, 2023 at 3:17 PM Gerald Magnuson <gmagqcy.midrange@xxxxxxxxx>
wrote:

6 seconds per week sounds about what we were having on the various power
systems I have had.
I would almost predict that as computing continues to modernize, the
concept of "keeping time" will get even more difficult for computers.
a dozen or more years ago we went to NTP, and I haven't really worried
about it since.

On Mon, Sep 25, 2023 at 12:25 PM (WalzCraft) Jerry Forss <
JForss@xxxxxxxxxxxxx> wrote:

I have a little stored procedure that is called from the network side
every Sunday to sync the time.

Every week the IBMi is behind by 6 seconds.
Any idea why there would be such a drift?

I know there are other ways to set the correct time but just wondering

why

it loses so much.



Subject to Change Notice:

WalzCraft reserves the right to improve designs, and to change
specifications without notice.

Confidentiality Notice:

This message and any attachments may contain confidential and privileged
information that is protected by law. The information contained herein is
transmitted for the sole use of the intended recipient(s) and should

"only"

pertain to "WalzCraft" company matters. If you are not the intended
recipient or designated agent of the recipient of such information, you

are

hereby notified that any use, dissemination, copying or retention of this
email or the information contained herein is strictly prohibited and may
subject you to penalties under federal and/or state law. If you received
this email in error, please notify the sender immediately and permanently
delete this email. Thank You

WalzCraft PO Box 1748 La Crosse, WI, 54602-1748
www.walzcraft.com<http://www.walzcraft.com> Phone: 1-800-237-1326
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

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

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.