Now for those that didn't move to a 4 digit year to resolve Y2K but instead 
went to a window technique, how many of your current staff know what dates were 
used for the window so they can again fix the problem before it occurs.

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of David L. Craig
Sent: Friday, April 20, 2018 4:26 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [IBM-MAIN] IRS - 60-Year-Old IT System Failed on Tax Day Due to 
New Hardware (nextgov.com)

In 1974, we considered it, but the cost of a byte of disk storage was enough to 
push the storage of each date's century toward the '90s.  We fully expected the 
remediation would be needed but storage would be more affordable by then, which 
panned out.  What everybody got wrong was expecting the relative costs of 
hardware and software to not change, but in fact they flipped--hardware became 
dirt cheap but software became very expensive.

On Fri, Apr 20, 2018 at 7:46 PM, Gerhard Adam <gada...@charter.net> wrote:

> It was discussed, but the general feeling was that those systems would 
> have been rewritten or replaced long before it became an issue.
>
> No one expected applications to be running 30-40 years after they were 
> first implemented.
>
> Sent from my iPhone
>
> > On Apr 20, 2018, at 12:25 PM, Lester, Bob <bles...@ofiglobal.com> wrote:
> >
> >
> > I agree with both you and Gil.  But, how many programmers in the 
> > 60s,
> 70s, even 80s were thinking about Y2K?  Sure, the really good ones 
> were, but what about the other 80%?
> >
> > ....and, Y2K came off without a hitch...(FSVO - "hitch")    😊
> >
> > I love Fridays...
> >
> > BobL
> >
> > -----Original Message-----
> > From: IBM Mainframe Discussion List 
> > [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Porowski, Kenneth
> > Sent: Friday, April 20, 2018 1:20 PM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Re: IRS - 60-Year-Old IT System Failed on Tax Day Due to 
> > New
> Hardware (nextgov.com) [ EXTERNAL ]
> >
> > That was due to lack of foresight by the programmer not due to the 
> > age
> of the system.
> >
> >
> >
> > This email message and any accompanying materials may contain
> proprietary, privileged and confidential information of CIT Group Inc. 
> or its subsidiaries or affiliates (collectively, β€œCIT”), and are 
> intended solely for the recipient(s) named above.  If you are not the 
> intended recipient of this communication, any use, disclosure, 
> printing, copying or distribution, or reliance on the contents, of 
> this communication is strictly prohibited.  CIT disclaims any 
> liability for the review, retransmission, dissemination or other use 
> of, or the taking of any action in reliance upon, this communication 
> by persons other than the intended recipient(s).  If you have received 
> this communication in error, please reply to the sender advising of 
> the error in transmission, and immediately delete and destroy the 
> communication and any accompanying materials.  To the extent permitted 
> by applicable law, CIT and others may inspect, review, monitor, 
> analyze, copy, record and retain any communications sent from or received at 
> this email address.
> >
> >
> > -----Original Message-----
> > From: IBM Mainframe Discussion List 
> > [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Paul Gilmartin
> > Sent: Friday, April 20, 2018 3:13 PM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Re: [IBM-MAIN] IRS - 60-Year-Old IT System Failed on Tax 
> > Day
> Due to New Hardware (nextgov.com)
> >
> >> On Fri, 20 Apr 2018 07:14:20 -0700, Gerhard Adam wrote:
> >>
> >> Applications don't get old.  They either do what they're supposed 
> >> to do
> or they don't.   It has nothing to do with age.
> > Remember Y2K?
> >
> > -- gil
> >
> > --------------------------------------------------------------------
> > -- For IBM-MAIN subscribe / signoff / archive access instructions, 
> > send
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> >
> >
> > --------------------------------------------------------------------
> > -- For IBM-MAIN subscribe / signoff / archive access instructions, 
> > send
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> >
> > This e-mail transmission may contain information that is 
> > proprietary,
> privileged and/or confidential and is intended exclusively for the
> person(s) to whom it is addressed. Any use, copying, retention or 
> disclosure by any person other than the intended recipient or the 
> intended recipient's designees is strictly prohibited. If you are not 
> the intended recipient or their designee, please notify the sender 
> immediately by return e-mail and delete all copies. OppenheimerFunds 
> may, at its sole discretion, monitor, review, retain and/or disclose 
> the content of all email communications.
> >
> >
> > --------------------------------------------------------------------
> > -- For IBM-MAIN subscribe / signoff / archive access instructions, 
> > send email to lists...@listserv.ua.edu with the message: INFO 
> > IBM-MAIN
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send 
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to