× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi Jay
There is another option
NOT pretty - but its another option
This particular data field - do you have any instances of this date being in the 20th century - 1901 through 1999
If you do - then this wont work
If you don't - then determine every program that uses this particular date field - and wherever it is used - convert the year portion (YY) to be century year (CCYY) with the following pseudo code
CCYY = 2000 + YY

Like I said - not pretty - but its another option
Hope you see what I am trying to explain

Alan Shore
E-mail : ASHORE@xxxxxxxx
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
'If you're going through hell, keep going.'
Winston Churchill

-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Jay Vaughn
Sent: Tuesday, August 25, 2020 9:18 AM
To: RPG programming on the IBM i (AS/400 and iSeries) <rpg400-l@xxxxxxxxxxxxxxxxxx>
Subject: [EXTERNAL] legacy date hell

So we have an input date on the screen as 3 separate fields... mm dd yy

Biz wants the ability to put a "max" date of 12/31/9999 in so that this record never expires.

I guess they didn't review the 2 digit year on the screen first... because if you put 99 in then when it comes time to store that input into the table where the date is 8s0, then it will think it is 1999.

And if we do store the date in the table as 12/31/9999, whenever any other pgm tries to convert from *ISO to *MDY, the pgm will blow up, because 9999 is not a valid date for *MDY.

So the way I see it the options are, train the user to input 39 into the screen yy for the max date which is the least invasive approach (and will create a new y2k scenario). OR expand screen date year to yyyy and refactor any and all pgms that convert this 8s0 date from *MDY to *ISO to handle the 9999 stored year correctly.

Pretty sure they will want to go with the 39 approach as they "claim" the system will be decommissioned in a couple years (which I've heard that a million times before).

Any other suggestions I am overlooking?


tia

Jay
--
This is the RPG programming on IBM i (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.