RE: Valid dates allowed by the operating system

The file I'm "massaging" is the result of a boatload of queries, and I'm
left with both *ISO and *MDY formats.

Through brute force and some complex CASE tests, I'm making headway.

Paul Nelson
Cell 708-670-6978
Office 409-267-4027
nelsonp@xxxxxxxxxxxxx


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Justin Taylor
Sent: Thursday, December 21, 2017 8:47 AM
To: Midrange Systems Technical Discussion
Subject: RE: Valid dates allowed by the operating system

That's interesting. I just created a new table (just a single date column)
on 7.3, and here's what it did for me.

I inserted 2049-12-31 and 2096-12-31 into the table successfully.
DSPPFM, QRY/400 and STRSQL all work fine.
My SQuirreL JDBC client gives SQLSTATE 01534.




-----Original Message-----
From: Paul Nelson [mailto:nelsonp@xxxxxxxxxxxxx]
Sent: Thursday, December 21, 2017 7:25 AM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxx>
Subject: Valid dates allowed by the operating system

Gang,

I'm working on a data mining project for a client and have come across
something weird. For whatever reason, their programmers decided that
2096-12-31 was a good date to pick for a lease expiration date, and
proceeded to populate hundreds of thousands of records with that date.

The crazy thing is that SQL doesn't like those dates, but query doesn't
care. Even crazier is that DSPPFM can't handle them. I keep getting data
mapping errors.

What is the highest valid date allowed by the system? I seem to recall that
it was 2049-12-31 at one point.

Paul Nelson
Cell 708-670-6978
Office 409-267-4027
nelsonp@xxxxxxxxxxxxx