MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » June 2005

Re: Time Sync v5r3



fixed

I once wrote something that got me close. I used the gettimeofday() API. It is valid in CL, as it expects pointers for the parameters. At any rate, it returns the current time in a so-called timeval structure - you can look up that in QSYSINC/H(TIME) member, IIRC - do a PDM search on QSYSINC/H if I'm wrong. It contains separate 2-byte integers for the various time components. String'm together and set QTIME. You will need to use %BIN in there somewhere.

HTH
Vern

At 11:59 AM 5/31/2005, you wrote:


I have been setting up the new time sync (NTP) on my systems and partitions as each gets upgraded to v5r3. Now I hit my oldest box a small 170. This hardware will not work with the v5r3 time feature. It seems I can set the software clock BUT not the hardware clock. I found an IBM Technote (#86256E0F00681558) entitled "Synchronization of the IBM iSeries Hardware Clock (QTIME) with the Software Clock That Exists on the Same System". This uses Management Central to setup and run. I have had no luck getting the time correct and would rather not use iSeries Access to run this.

Does anyone have a better method setting the hardware clock from the
software clock?


--- Doug Hart


-- 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.






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact