RE: Getting "hard halts" on years > 2039

When I said "all dates" should use date data types, I of course meant displays as well. Thank you for clarifying for me.

Brian May
Solutions Architect
Profound Logic Software
http://www.profoundlogic.com
937-439-7925 Phone
877-224-7768 Toll Free



The IBM i Modernization Experts
www.profoundlogic.com
             


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Wednesday, April 22, 2015 1:43 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Getting "hard halts" on years > 2039

On 22-Apr-2015 12:56 -0500, Brian May wrote:

I agree it is the 1940 to 2039 window. Honestly, the "correct" way to
fix it will be to migrate all dates into true date data types.
This is not a small "fix". This will most likely be a major overhaul,
but in the end, you will know it is done correctly.

To be sure, even if all dates were stored with the DATE data-type, the _same issue_ with date values falling outside the window can occur.
If the presentation-format for a DATE data-type value allows for only a two-digit year, then the same failure should transpire to prevent mis-inference of would be an otherwise _ambiguous_ value. A complete fix might require that no date ever be represented with a two-digit year, or that when such a presentation were desirable, a window appropriate to the date information being presented would need to be used instead of the 1940-2039 window.

--
Regards, Chuck

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