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



OK, I've just dug through a zillion more archived posts on the UTC offset
and then braved a search the rest of the Internet.  I think I've got it now.
I must admit though, I still don't understand what Greenwich Mean Time has
to do with Br*tn*y Sp**rs.

Here in Nashville (CST) I should be setting the UTC offset to -5:00 with
Daylight Savings Time when I change QHOUR ahead one hour and changing the
UTC offset back to -6:00 back when I "Fall back".  GMT is a time standard
not affected by the various country and region daylight savings times and
exceptions.  Did I get it right?

Also, Is an IPL or restart of any services necessary?

-Jim

-----Original Message-----
From: Scott Mildenberger [mailto:scottmildenberger@xxxxxxxxx]
Sent: Tuesday, April 08, 2003 8:42 AM
To: Midrange Systems Technical Discussion
Subject: Re: Netserver, time zones, offsets?


Did you also change the QUTCOFFSET when you changed
the time?

Scott Mildenberger

--- Jim Damato <jdamato@xxxxxxxxxxxxxxxxx> wrote:
> I'm pretty sure this is a daily savings time issue. 
> Since we've changed the
> time this past weekend we've been experiencing
> discrepancies in the time
> stamps on files shared via Netserver.  For example,
> a process was run on the
> AS/400 to create a bunch of files at 4:30 PM today. 
> If I look at the
> attributes of those files from WRKLNK on the server
> I see the correct time
> of 4:30 PM in the data and attribute change
> date/time fields.  If I browse
> the folder via netserver from any client or NT
> server using NT Explorer the
> files all show a stamp of 5:30 PM.
> 
> I checked the archives and found a similar post, but
> the problem was with a
> difference in time offsets between their server and
> the client's Outlook
> config.  In our network the UTC offset value is set
> to -6:00 on the AS/400,
> the clients, and the primary domain controller.
> 
> Any ideas on the cause and cure?  Much thanks in
> advance...
> 



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.