Oh crap. the offset is in minutes?

I'm an idiot.

thanks everyone!

On Mon, Mar 27, 2017 at 8:52 PM, Alan Campin <alan0307d@xxxxxxxxx> wrote:

Mark is correct. QN0500EST3 is correct. 300 is 5 hours.

ONEZONE.ZONENAME = 'QN0500EST3'
ONEZONE.LOCALSYSTEMTIMEINDICATOR = '0'
ONEZONE.DAYLIGHTSAVINGTIMEINDICATOR = '1'
ONEZONE.OFFSETFROMUTC = -300
ONEZONE.STANDARDABBREVIATEDNAME = 'EST '
ONEZONE.FULLNAME = 'Eastern Standard Time
ONEZONE.DAYLIGHTSAVINGABBREVIATEDNAME = 'EDT '
ONEZONE.DAYLIGHTSAVINGFULLNAME =
'Eastern Daylight Time
ONEZONE.STANDARDTIMEMESSAGEID = 'CPX091E'
ONEZONE.DAYLIGHTSAVINGTIMEMESSAGEID = 'CPX091F'
ONEZONE.MESSAGEFILENAME = 'QCPFMSG '
ONEZONE.MESSAGEFILELIBRARY = '*LIBL '
ONEZONE.DAYLIGHTSAVINGSTARTMONTH = '03'
ONEZONE.DAYLIGHTSAVINGSTARTDAY = '7'
ONEZONE.DAYLIGHTSAVINGSTARTRELATIVEDAYOFMONTH = '2'
ONEZONE.DAYLIGHTSAVINGSTARTTIME = '020000'
ONEZONE.DAYLIGHTSAVINGENDMONTH = '11'
ONEZONE.DAYLIGHTSAVINGENDDAY = '7'
ONEZONE.DAYLIGHTSAVINGENDRELATIVEDAYOFMONTH = '1'
ONEZONE.DAYLIGHTSAVINGENDTIME = '020000'

On Mon, Mar 27, 2017 at 3:48 PM, rick baird <rick.baird@xxxxxxxxx> wrote:

Hey all,

We just upgraded to V7R1M0 and the time description API QWCRTVTZ is
giving
the wrong data for EST - see below

EVAL tzds
TZDS.ZONE = 'QN0500EST '
TZDS.SYSZONE = '1'
TZDS.SUPDST = '1'
TZDS.UTCOFFSET = -300
TZDS.STDABBR = 'EST '
TZDS.STDFULL = 'Eastern Standard Time
TZDS.DSTABBR = 'EDT '
TZDS.DSTFULL = 'Eastern Daylight Time
TZDS.STDMSGID = 'CPX091E'
TZDS.DSTMSGID = 'CPX091F'
TZDS.MSGFILE = 'QCPFMSG '
TZDS.MSGFLIB = '*LIBL '
TZDS.DSTSTRMON = 04.
TZDS.DSTSTRDOWK = 7
TZDS.DSTSTRRDMO = '1'
TZDS.DSTSTRTIME = 020000.
TZDS.DSTENDMON = 10.
TZDS.DSTENDDOWK = 7.
TZDS.DSTENDRDMO = 'L'
TZDS.DSTENDTIME = 020000.

QN0500EST is Eastern Standard Time, so I know I'm getting the proper
zone.

Offset should be -5, not -3.
The DST start month is 3, not 4.
day of week is right at 7, but day of month should be 2 (second sunday)
didn't check for the DST end dates, but I'm guessing they're wrong too.

I double checked my data structure against the V7 api finder and it's
good. I can't guarantee it worked just before our upgrade, but it's not
working now.

Any ideas? thanks in advance.
--
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.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.