RE: How can a program find out whether a system is on Daylight Saving Time?

Seriously,

Does anyone know whether a job's UTCOFFSET attribute changes when the system value gets changed? If this job level attribute is like the rest of OS400, then that value is retrieved when the job initializes, and would not be set correctly on jobs that were started before the time change...

I wish I knew if the time() function uses system values, or job attributes...

It's also a remote possibility that your application might be trying to manually format a UTC 0 timestamp. If so, it's possible that you retrieved the utc offset at job init, then stored it reuse within the job...

RTVJOBA TIMOFFSET(&UTCOFFSET)

Just food for thought...
-Eric DeLong

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of DeLong, Eric
Sent: Monday, March 12, 2012 1:58 PM
To: Midrange Systems Technical Discussion
Subject: RE: How can a program find out whether a system is on Daylight Saving Time?

Lol, restart your NEPS!

-Eric DeLong

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Gary Thompson
Sent: Monday, March 12, 2012 1:23 PM
To: Midrange Systems Technical Discussion
Subject: RE: How can a program find out whether a system is on Daylight Saving Time?

So, >maybe< your server is daylight saving time and,
the web service is not dst?
Or, >maybe< your web service interface does not correctly
identify your time zone?

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James Lampert
Sent: Monday, March 12, 2012 12:14 PM
To: Midrange Systems Technical Discussion
Subject: How can a program find out whether a system is on Daylight Saving Time?

The subject line says it all. My Google Calendar Interface has started blowing up, and I've determined that it's happening because the C time() function (which is used in generation of the digital signature for the web service request) is now returning a time number that is one hour in the future. And the Google Calendar web services are rejecting it.

If I run the request out of OAuth Playground, the time number is 3600 seconds earlier than what I get on the 400, and if, in the debugger, I manually subtract 3600 seconds from the time number, it works just fine, which makes the above diagnosis look pretty conclusive.

--
JHHL