2039 cutoff -- MIDRANGE-L

Subject: 2039 cutoff
From: rob@xxxxxxxxx
Date: Mon, 28 Nov 2011 12:02:19 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

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.

Follow-Ups:

RE: 2039 cutoff , Musselman, Paul
Re: 2039 cutoff , Scott Klement

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.