IBM Wall of text:
Q: Why is the time on my files in my ifs folder different from what time it
actually is?
A: All times stored in the IFS are in Universal Time Coordinated (UTC). For
the purposes of this discussion, UTC is the same thing as Greenwich Mean
Time (GMT), though technically GMT stopped being the international standard
in 1972 and was replaced by UTC.
On your iSeries there's a system value called QUTCOFFSET which means "UTC
Offset". It tells how many hours and minutes the clock on your iSeries
differs from UTC.
For example, if you live in New York your clock is set to 5 hours before
UTC. If it's 15:00 in New York, it's 20:00 in Greenwich England where the
prime meridian is. In that case, your QUTCOFFSET system value should be set
to '-0500' if your iSeries is configured properly (though, I'm guessing that
it isn't!)
When you create a file in the IFS at 15:00, the iSeries adds that QUTCOFFSET
system value to the time, and stores the result in the IFS. In this example,
the IFS would read 20:00. When you view a directory listing later, the
system reads the 20:00 and subtracts the 5 hours to give you 15:00 again.
The problem that you've described occurs when the time zone isn't the same
on two different computers. Suppose you never set the QUTCOFFSET system
value on your iSeries? If your iSeries clock is set to 15:00, and QUTCOFFSET
is set to the default value of 0, what happens? When you create the file,
15:00 is written to the IFS -- that's because the iSeries thinks it's 15:00
and thinks that it's located in the UTC time zone. So it writes 15:00. When
you view that time from the same iSeries, it once again shows 15:00, since
adding 0 doesn't change anything.
Now you view the same file from Windows. Windows has it's time zone set to
-0500 because you're in New York your time zone is set correctly. When you
read the IFS, the Windows PC retrieves the 15:00 UTC from the IFS and
subtracts 5 from it. It thinks the file was created at 10:00!
The fix is to set your time zone properly on the iSeries. On V5R2 and
earlier, you do that by setting the QUTCOFFSET system value directly. On
V5R3 and later, you set the QTIMZON system value instead (QUTCOFFSET will be
updated automatically).
Once the QUTCOFFSET or QTIMZON has been adjusted to the proper value you
will more than likely need to change QTIME to be the "current" time
Leonard
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Luis Rodriguez
Sent: Friday, April 09, 2010 11:32 AM
To: Midrange Systems Technical Discussion
Subject: Re: Strange Time on IFS
Jon,
I wonder if it could be a time difference between the PC and the iSeries?
Check QTIME and the UTC offset (QUTCOFFSET? system value in your iSeries.
HTH,
Luis Rodriguez
IBM Certified Systems Expert - eServer i5 iSeries
On Fri, Apr 9, 2010 at 10:52 AM, Jon S <rvrratjon@xxxxxxxxxxx> wrote:
I have a customer running V5R2 and when a file is created on the IFS via
cpytoimpf, if you look at the properties through windows explorer, the
time
modified is exactly 1 hour ahead of the create time and it's causing some
problems with some scripts. Has anyone seen this before? I have looked
through PTF's to no avail.
Thanks in advance.
Jon
_________________________________________________________________
Hotmail is redefining busy with tools for the New Busy. Get more from your
inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:W
L:en-US:WM_HMP:042010_2
--
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.
midrange.com
