The one thing that you and others do is make assumptions that I think companies run or should only run on the mainframe. Heck, even 40 years ago we had workloads at GM that ran better on other platforms. The Engineering group ran on DEC VAX machines. Often called IBM killer back then. Every shop I’ve been has run multiple platforms. I’m not anti public cloud. I’ve seen numerous claims that the mainframe is dying, none of which came to fruition. And the public cloud won’t replace it either.
Sent from Yahoo Mail for iPhone On Friday, June 17, 2022, 2:16 PM, David Crayford <dcrayf...@gmail.com> wrote: On 18/06/2022 2:02 am, Bill Johnson wrote: > Don’t really care. I’ll be retired soon. The first time it gets hacked, and > it will, Jamie will be facing lawsuits that will make the Capital One payout > look like pocket change. JP Morgan Chase already run significant workloads on multi-cloud (AWS, Azure and GCP). All banks do. It's where they do fraud detection, analytics and providing caching layers for online transactions. > Oh, and I’ve got dozens of stories about planned “upgrades” that went awry >over the years. All platforms suffer outages, Bill. We've flogged this to death already. https://lmgtfy.app/?q=mainframe+outagehttps://lmgtfy.app/?q=mainframe+outagehttps://lmgtfy.app/?q=mainframe+outagehttps://lmgtfy.app/?q=mainframe+outagehttps://lmgtfy.app/?q=mainframe+outagehttps://lmgtfy.app/?q=mainframe+outage > I’d bet JPM still runs on a mainframe 10, 20 or more years from now. I certainly hope so as they're one of our customers! It won't stop them trying to get off though. I heard that ING has moved off. It's always depressing when a financial services giant leaves the platform. > > > Sent from Yahoo Mail for iPhone > > > On Friday, June 17, 2022, 1:47 PM, David Crayford<dcrayf...@gmail.com> wrote: > > You may want to change banks > > >https://www.paymentsjournal.com/go-big-or-go-home-jpm-will-spend-up-to-12b-to-get-to-the-cloud/amp/ > >> On 18 Jun 2022, at 01:43, Bill >> Johnson<00000047540adefe-dmarc-requ...@listserv.ua.edu> wrote: >> >> What’s the difference between JPM’s mainframe and Capital One’s AWS? Other >> than one is fast, reliable, and secure and the other is not. Both can be >> located anywhere in the world and accessed from anywhere via all kinds of >> devices. Explain the difference. What makes one a cloud and not the other? >> >> >> Sent from Yahoo Mail for iPhone >> >> >> On Friday, June 17, 2022, 1:36 PM, zMan<zedgarhoo...@gmail.com> wrote: >> >> OK...that was the commonality. Either that or you were suggesting that >> "banking transactions" implies cloud. >> >> I saw no "cloud" in anything you listed other than that one bank was >> running their stuff in AWS. Viewed through that lens, the question doesn't >> even make sense: "Is this thing that IS in the cloud different from this >> other thing that's not in the cloud?" Well, yes. >> >>> On Fri, Jun 17, 2022 at 1:30 PM Bill Johnson < >>> 00000047540adefe-dmarc-requ...@listserv.ua.edu> wrote: >>> >>> I never said APP = Cloud. I can get my banking transactions anywhere in >>> the world from JPM wherever their mainframe is located. The exact same >>> thing I can do with Capital One via AWS. The APPS are just the front end >>> query mechanism. >>> >>> >>> Sent from Yahoo Mail for iPhone >>> >>> >>> On Friday, June 17, 2022, 1:22 PM, zMan<zedgarhoo...@gmail.com> wrote: >>> >>> Correct. App <> cloud. >>> >>> On Fri, Jun 17, 2022 at 1:04 PM Bill Johnson < >>> 00000047540adefe-dmarc-requ...@listserv.ua.edu> wrote: >>> >>>> So if I get my banking transactions by Capital One APP via AWS, that’s >>>> cloud, but if I get those same banking transactions via JP Morgan APP >>> which >>>> acquires the records via CICS transaction from DB2 that’s not cloud? >>>> >>>> >>>> Sent from Yahoo Mail for iPhone >>>> >>>> >>>>> On Friday, June 17, 2022, 12:56 PM, zMan<zedgarhoo...@gmail.com> wrote: >>>> I'm highly suspicious of cloud in general, don't get me wrong. But IBM >>>> can't just call CICS "cloud" and expect it to mean anything. Calling a >>> tail >>>> a leg doesn't make it one: when the rest of the industry says "cloud" >>> these >>>> days, they don't just mean outsourcing, and definitely don't mean CICS. >>> And >>>> CICS isn't a synonym for outsourcing in any case. >>>> >>>> Actually, if you think of cloud services in terms of HTTPS transactions, >>>> CICS isn't that far off in some ways--but it still isn't the same thing, >>>> more an older, pre-Internet version of something similar. Yes, CICS can >>>> serve web pages; that doesn't make CICS = cloud! >>>> >>>> "Mainframe modernization" is a pretty bogus term, nicely loaded: "Hmm, if >>>> mainframe modernization exists, mainframes must be >>>> old-fashioned/obsolete/behind". Wrong, as we know. "Mainframe emulation" >>> is >>>> closer, only that tends to make us think zPDT, Hercules, et al.; "z/OS >>>> emulation" seems more accurate to me, but isn't the term that folks use, >>> so >>>> it doesn't help at this point. It's a mess. >>>> >>>> But none of this discussion, interesting as it is, relates to the fact >>> that >>>> IBM claims to have a cloud presence BUT has chosen to host their offering >>>> in AWS. Those two items are pretty hard to reconcile. >>>> >>>> ---------------------------------------------------------------------- >>>> For IBM-MAIN subscribe / signoff / archive access instructions, >>>> send email tolists...@listserv.ua.edu with the message: INFO IBM-MAIN >>>> >>>> >>>> >>>> >>>> ---------------------------------------------------------------------- >>>> For IBM-MAIN subscribe / signoff / archive access instructions, >>>> send email tolists...@listserv.ua.edu with the message: INFO IBM-MAIN >>>> >>> >>> -- >>> zMan -- "I've got a mainframe and I'm not afraid to use it" >>> >>> ---------------------------------------------------------------------- >>> For IBM-MAIN subscribe / signoff / archive access instructions, >>> send email tolists...@listserv.ua.edu with the message: INFO IBM-MAIN >>> >>> >>> >>> >>> ---------------------------------------------------------------------- >>> For IBM-MAIN subscribe / signoff / archive access instructions, >>> send email tolists...@listserv.ua.edu with the message: INFO IBM-MAIN >>> >> >> -- >> zMan -- "I've got a mainframe and I'm not afraid to use it" >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email tolists...@listserv.ua.edu with the message: INFO IBM-MAIN >> >> >> >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email tolists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email tolists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email tolists...@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
