For people and institutions which owned or managed bonds, Y2K occurred 1/1/1970. Right after that Warrington had a nifty package which I supported for a while for a bank in Houston which had all 4 digit yrs.
On the other hand the bank's DDA internally written code stored the yr as 1/2 byte so that the day after 12/31/1975 was 1/1/1960. And yes they went right down to the wire replacing it. And since it was Asm -> Cobol, the head of tech support got a promotion to VP for asking the question "In worst case scenario, are 2 155's running MVT enough to do posting overnight?" The answer, verified by running an experiment, was NO. It was prophetic that the third 155 had yellow skins. No planning done before its time. IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> wrote on 03/16/2013 04:48:57 PM: > From: "g...@gabegold.com" <g...@gabegold.com> > To: IBM-MAIN@LISTSERV.UA.EDU, > Date: 03/16/2013 04:49 PM > Subject: Re: Query for Destination z article -- mainframes back to the future > Sent by: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> > > My first year-end retirement account statement -- for 1971! -- > listed my projected retirement date as the incredibly distant, > unimaginable, science-fiction-like date of February 1, 2012. So back > then at least TIAA-CREF understood time windows spanning entire > careers and beyond. > > Quoting: > > I was somewhat surprised that it took so long for Y2K to rise to the > top, with 30-year mortgages and such forward-looking things being > far from uncommon. But I guess those systems all got fixed one at a > time as their windows passed 2000, without enough awareness that > anyone said "Hey, we need to fix this globally, now that storage > (both memory and DASD) is cheap!" ----------------------------------------- The information contained in this communication (including any attachments hereto) is confidential and is intended solely for the personal and confidential use of the individual or entity to whom it is addressed. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this communication in error and that any review, dissemination, copying, or unauthorized use of this information, or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. Thank you ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
