RE: iSeries CLOCK _SYNC -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: RE: iSeries CLOCK _SYNC
From: "Jeff Crosby" <jlcrosby@xxxxxxxxxxxxxxxx>
Date: Fri, 19 May 2006 15:39:18 -0400
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

> We are running V5R3 on a 520. I will look into this for a 
> possible solution. 

In V5R3 the i5 can be both an NTP server and an NTP client.  Here's what we
do:

1) Set up the i5 to sync with some external source (US Naval Observatory or
such)

2) Have every PC in the place (including the IXS) sync to the i5.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: iSeries CLOCK _SYNC , Tom Jedrzejewicz

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.