Re: 2039 cutoff

[Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>]

Back when IBM introduced the 2040 workaround (in the 90's, in 
preparation for Y2K) they warned that this was a temporary workaround. 
They said that we should update our code to use 4-digit years, lest we 
have the same problem in 2040 that we were having (at that time) with Y2K.

I haven't heard any further talk about sliding the window, but I assume 
IBM's original statement stands:  That it was a temporary workaround, 
not intended to continue indefinitely.


On 11/28/2011 11:02 AM, rob@xxxxxxxxx wrote:
> If one tries to convert 2040-01-31 to MMDDYY it aborts.  Documented here
> at
> http://publib.boulder.ibm.com/infocenter/iseries/v7r1m0/topic/db2/rbafzch2date.htm
> and elsewhere.
>
> Is there any talk about sliding that window?
>
> Since we've already hit a hiccup are some people considering dropping
> using built in techniques to convert from 8 to 6 digit date fields and use
> custom code?