× 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.



I'm trying to understand the math on your answer Alan.

And regardless of if I'm going to be working, I don't want somebody talking smack about me like I talk about pre-me programmers. Fix it like the user wants it or fix it correctly. Pick one. But document it well if doing it like the user wants.

-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Alan Shore via RPG400-L
Sent: Tuesday, August 25, 2020 9:29 AM
To: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx>
Cc: Alan Shore <ashore@xxxxxxxx>
Subject: RE: [EXTERNAL] Re: legacy date hell

You are assuming that this is not some expiration date, 15 years into the future That's one of the predicaments Im facing

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 Jeff Crosby
Sent: Tuesday, August 25, 2020 9:22 AM
To: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx>
Subject: [EXTERNAL] Re: legacy date hell

You still gonna be working in 2039? :)


On Tue, Aug 25, 2020 at 9:19 AM Jay Vaughn <jeffersonvaughn@xxxxxxxxx>
wrote:

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://urldefense.proofpoint.com/v2/url?u=https-3A__lists.midrange.co
m_mailman_listinfo_rpg400-2Dl&d=DwICAg&c=euGZstcaTDllvimEN8b7jXrwqOf-v
5A_CdpgnVfiiMM&r=LifWsbmXTz4aXbMMEwOi1aJ3sWD5nsP_QI4reJ8MbDM&m=KQ2O0jt
2LHzDedTB8AlIRRqAxwL1z4hqzDHy85QSFjI&s=nIVzTRGKdG75o414JP_q5ycTP2IB7td
T6mzEb1iO3hw&e= or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://urldefense.proofpoint.com/v2/url?u=https-3A__archive.midrange.com_rpg400-2Dl&d=DwICAg&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=LifWsbmXTz4aXbMMEwOi1aJ3sWD5nsP_QI4reJ8MbDM&m=KQ2O0jt2LHzDedTB8AlIRRqAxwL1z4hqzDHy85QSFjI&s=q9QIQJfHlAyOQxF7vC1GKGtztmzo2NnJJm-UCmGLekc&e=.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.

Help support
https://urldefense.proofpoint.com/v2/url?u=http-3A__midrange.com&d=DwI
CAg&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=LifWsbmXTz4aXbMMEw
Oi1aJ3sWD5nsP_QI4reJ8MbDM&m=KQ2O0jt2LHzDedTB8AlIRRqAxwL1z4hqzDHy85QSFj
I&s=ORcI8HDvwbkBSiRLckDB9kwTXgtriA9qzpVyE_6_2CQ&e= by shopping at
https://urldefense.proofpoint.com/v2/url?u=http-3A__amazon.com&d=DwICA
g&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=LifWsbmXTz4aXbMMEwOi
1aJ3sWD5nsP_QI4reJ8MbDM&m=KQ2O0jt2LHzDedTB8AlIRRqAxwL1z4hqzDHy85QSFjI&
s=kd_Y7LxW1OQ_QWU64l8Eukhn2E4pvrJ9GoXLMgf5csU&e= with our affiliate
link:
https://urldefense.proofpoint.com/v2/url?u=https-3A__amazon.midrange.c
om&d=DwICAg&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=LifWsbmXTz
4aXbMMEwOi1aJ3sWD5nsP_QI4reJ8MbDM&m=KQ2O0jt2LHzDedTB8AlIRRqAxwL1z4hqzD
Hy85QSFjI&s=L9Cwvo7JoCKn4GjqBaGQVWvSFe09aCKu__3ZICtpyMA&e=




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.