Re: Dates greater than 2039

["Bob P. Roche" <BRoche@xxxxxxxxxxxxxxxxx>]

Does anyone know if IBM plans  on pushing the allowed 2 digit year time 
frame? I avoid these as much as I can in programming.
As we get closer to 2039, it would make sense for newer versions of the 
operating system (or compiler?) to handle dates with a different 100 year 
time range.




CRPence <CRPbottle@xxxxxxxxx> 
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
05/29/2008 04:03 PM
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>


To
rpg400-l@xxxxxxxxxxxx
cc

Subject
Re: Dates greater than 2039






   The date 15-Dec-2040 represented in *ISO is 2040-12-15 and 
represented in *YMD would be 40/12/15.  However that same *YMD value of 
40/12/15 is _actually_ understood to be the *ISO 1940-12-15, and there 
would be no error generated for using that value; except perhaps 
incorrect output.  What this suggests, is that although there is no 
support for a six digit year representing 2040 [and beyond], the six 
digit date can still be validly interpreted without error even if it is 
/incorrect/ for the wrong century.  That may be what is the issue here.?

Doug Palme wrote:
> It used to be that any date greater than 2039 would cause an
> error with a six digit date data type.....did IBM fix that?
> Because it no longer seems to be a problem......