Re: legacy date hell

[Brad Stone <bvstone@xxxxxxxxx>]

People thought y2k was bad.  When I saw what was going on with a lot of
shops, I said that y2k will be nothing compared to 2039.  :)  I should be
retiring about that time..... :)


Bradley V. Stone
www.bvstools.com
GreenTools for G Suite/Google Apps <https://www.bvstools.com/g4g.html>:
Easy to use interfaces for GMail, Google Drive, Calendar, Contacts and
Cloud Print! <\body> <\html>

On Tue, Aug 25, 2020 at 8:22 AM Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx>
wrote:

> 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://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
>
>
> --
>
>
> Jeff Crosby
> VP Information Systems
> UniPro FoodService/Dilgard
> P.O. Box 13369
> Ft. Wayne, IN 46868-3369
> 260-422-7531
> direct.dilgardfoods.com
>
> The opinions expressed are my own and not necessarily the opinion of my
> company.  Unless I say so.
> --
> 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