Re: [EXTERNAL] legacy date hell -- RPG400-L

Can you add a never expire field and when active bypass the date or add a
year to the date when you hit the expired date ?

On Tue, Aug 25, 2020 at 9:43 AM Duane Scott <dscott@xxxxxxxxxxx> wrote:

I'm +1 on this option, except they want 9999.

Seems like the best programming solution would be to add the century and
accept a two digit year unless entered as 4. Probably not too bad on the
user. Lesser evil?

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

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://urldefense.proofpoint.com/v2/url?u=https-3A__lists.midrange.com_mailman_listinfo_rpg400-2Dl&d=DwICAg&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=LifWsbmXTz4aXbMMEwOi1aJ3sWD5nsP_QI4reJ8MbDM&m=_7DXRvEnlACYGcAck2pkHshk-zjl-HWvvTic618vrdw&s=a0BqjHIe06q052ihvi3opqcAqtQ_zu-TIf8DVv1z2fk&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=_7DXRvEnlACYGcAck2pkHshk-zjl-HWvvTic618vrdw&s=uebKRP4z_Dmn_jTyCopI5OQPCwUowyB7T-hNUlRDFBY&e=
.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support
https://urldefense.proofpoint.com/v2/url?u=http-3A__midrange.com&d=DwICAg&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=LifWsbmXTz4aXbMMEwOi1aJ3sWD5nsP_QI4reJ8MbDM&m=_7DXRvEnlACYGcAck2pkHshk-zjl-HWvvTic618vrdw&s=Zi1su9oGRFmNtyRd2Jx_WXahxE5YrRLAloJG0kCNfNI&e=
by shopping at
https://urldefense.proofpoint.com/v2/url?u=http-3A__amazon.com&d=DwICAg&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=LifWsbmXTz4aXbMMEwOi1aJ3sWD5nsP_QI4reJ8MbDM&m=_7DXRvEnlACYGcAck2pkHshk-zjl-HWvvTic618vrdw&s=Ox5Fvh1nBV5d6VeuQeH_9vZwbaqzFm3y2KcRIjClRqA&e=
with our affiliate link:
https://urldefense.proofpoint.com/v2/url?u=https-3A__amazon.midrange.com&d=DwICAg&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=LifWsbmXTz4aXbMMEwOi1aJ3sWD5nsP_QI4reJ8MbDM&m=_7DXRvEnlACYGcAck2pkHshk-zjl-HWvvTic618vrdw&s=s0Opet423h24aloOqpXG0nnloFaKiWyvzG_ySa9IXu0&e=

--
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.com_mailman_listinfo_rpg400-2Dl&d=DwICAg&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=LifWsbmXTz4aXbMMEwOi1aJ3sWD5nsP_QI4reJ8MbDM&m=_7DXRvEnlACYGcAck2pkHshk-zjl-HWvvTic618vrdw&s=a0BqjHIe06q052ihvi3opqcAqtQ_zu-TIf8DVv1z2fk&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=_7DXRvEnlACYGcAck2pkHshk-zjl-HWvvTic618vrdw&s=uebKRP4z_Dmn_jTyCopI5OQPCwUowyB7T-hNUlRDFBY&e=
.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support
https://urldefense.proofpoint.com/v2/url?u=http-3A__midrange.com&d=DwICAg&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=LifWsbmXTz4aXbMMEwOi1aJ3sWD5nsP_QI4reJ8MbDM&m=_7DXRvEnlACYGcAck2pkHshk-zjl-HWvvTic618vrdw&s=Zi1su9oGRFmNtyRd2Jx_WXahxE5YrRLAloJG0kCNfNI&e=
by shopping at
https://urldefense.proofpoint.com/v2/url?u=http-3A__amazon.com&d=DwICAg&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=LifWsbmXTz4aXbMMEwOi1aJ3sWD5nsP_QI4reJ8MbDM&m=_7DXRvEnlACYGcAck2pkHshk-zjl-HWvvTic618vrdw&s=Ox5Fvh1nBV5d6VeuQeH_9vZwbaqzFm3y2KcRIjClRqA&e=
with our affiliate link:
https://urldefense.proofpoint.com/v2/url?u=https-3A__amazon.midrange.com&d=DwICAg&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=LifWsbmXTz4aXbMMEwOi1aJ3sWD5nsP_QI4reJ8MbDM&m=_7DXRvEnlACYGcAck2pkHshk-zjl-HWvvTic618vrdw&s=s0Opet423h24aloOqpXG0nnloFaKiWyvzG_ySa9IXu0&e=
CONFIDENTIALITY NOTICE: This electronic message transmission is intended
only for the person or entity to which it is addressed and may contain
information that is privileged, confidential or otherwise protected from
disclosure. If you have received this transmission, but are not the
intended recipient, you are hereby notified that any disclosure, copying,
distribution or use of the contents of this information is strictly
prohibited. If you have received this e-mail in error, please contact NALC
Health Benefit Plan at 703-729-4677 and delete and destroy the original
message and all copies.
--
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