No, some fixes just delayed it.




From:
"Musselman, Paul" <pmusselman@xxxxxxxxxxxxxxxx>
To:
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date:
11/28/2011 02:03 PM
Subject:
RE: 2039 cutoff
Sent by:
midrange-l-bounces@xxxxxxxxxxxx



Didn't we take care of all this sort of thing in 1999??? (:

Paul E Musselman
PaulMmn@xxxxxxxxxxxxxxxxxxxx



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Monday, November 28, 2011 12:02 PM
To: midrange-l@xxxxxxxxxxxx
Subject: 2039 cutoff

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?


Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.