|
On Wed, 29 Oct 2003, James Rich wrote:
Notice "on some architectures". Most likely is that the timezone structure is not filled out on the iSeries platform. If so, this is not a bug.
Do you know for a fact that this is the reason, or is it just a guess? When I look in the iSeries Information Center, I see this:
It says NOTHING about the time zone not being filled in, despite that this is an iSeries-specific manual. In fact, there's an example at the end of this page which shows output like this:
Example Output: gettimeofday() successful. time = 866208142.290944, minuteswest = 360, dsttime = 1
Why would IBM put an example in their own iSeries manual that shows the timezone being returned if they don't support it?
Something isn't right here. Either their documentation is really really misleading, or something else is wrong, here..
No, it's not. The time returned by gettimeofday() is the seconds from Jan 1 1970, UTC, NOT the local time. This is documented in the Infocenter as well, but I also tested it with a quick program...
Here's my test program, I deliberately coded this so that it would work on V4R2 or later (since that's when the API was introduced). On my system, it returns the UTC time and 0 for the minutes west.
As an Amazon Associate we earn from qualifying purchases.
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.