You may be missing a PTF that went in years back when the month changed for when EDT goes in effect.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rick baird
Sent: Monday, March 27, 2017 6:49 PM
To: Midrange Systems Technical Discussion
Subject: QWCRTVTZ givng wrong data for time zone.
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
midrange.com
