Admit it, you were a true believer in the 90’s that the mainframe would be gone by 2000. And now you’re a true believer that the cloud will kill it. And there isn’t one fact that supports you. None. It’s still growing by leaps and bounds. Doing more work every year.
Sent from Yahoo Mail for iPhone On Sunday, December 12, 2021, 10:04 AM, Tom Brennan <[email protected]> wrote: Of course. What what I thinking SMH. You are always right. On 12/12/2021 6:52 AM, Bill Johnson wrote: > Yeah, I read the whole article and nowhere does it contradict my claims. > Perhaps you interpret incorrectly! > > > Sent from Yahoo Mail for iPhone > > > On Saturday, December 11, 2021, 11:11 PM, Tom Brennan > <[email protected]> wrote: > > I just made a fake account and now I can read it. > I wonder if Bill read it all the way to the bottom, because there are > some points in the article that don't really help his case. > > On 12/11/2021 6:04 PM, Clark Morris wrote: >> On Sat, 11 Dec 2021 20:40:08 +0000, Bill Johnson >> <[email protected]> wrote: >> >>> https://www.americanbanker.com/news/why-some-banks-still-lean-on-mainframes >>> >> I can't read beyond the first 2 paragraphs on either Firefox or Edge. >> >> Clark Morris >>> >>> >>> Sent from Yahoo Mail for iPhone >>> >>> >>> On Saturday, December 11, 2021, 3:10 PM, Tom Brennan >>> <[email protected]> wrote: >>> >>> And that's where we disagree. Banks will do whatever is most economical >>> that still meets their needs. If x86-cloud doesn't meet those >>> requirements today, they stay on the mainframe. Tomorrow... only the >>> shadow knows. >>> >>> People say OS/2 was far better in design, operation, and security than >>> Windows, but it's gone now. Sometimes the "best" system is simply what >>> everybody else is using. Got to go now because I just put in a betamax. >>> >>> On 12/11/2021 10:51 AM, Bill Johnson wrote: >>>> Do you put your DR placement right across the street from your data >>>> center? Consolidation is bad. Exposure for everyone in the same place is a >>>> disaster waiting to happen. Like last week. It's why truly important >>>> functions like banks don't do clouds. >>>> >>>> >>>> Sent from Yahoo Mail for iPhone >>>> >>>> >>>> On Saturday, December 11, 2021, 1:46 PM, Tom Brennan >>>> <[email protected]> wrote: >>>> >>>> Of course... military has the money (the $500 hammer?) to have >>>> redundancy on their redundancy. Business installations normally can't >>>> justify those costs. >>>> >>>> However, I think if we looked close we both might be surprised at all >>>> the various baskets AWS has behind the scenes. But like any basket >>>> collection, there are always single points of failure. >>>> >>>> On 12/11/2021 6:06 AM, Bill Johnson wrote: >>>>> You've just described what the mainframe does for an organization. But, I >>>>> don't want every organization to have its eggs in one basket any more >>>>> than I want every nuclear weapon in one silo. >>>>> >>>>> >>>>> Sent from Yahoo Mail for iPhone >>>>> >>>>> >>>>> On Saturday, December 11, 2021, 2:01 AM, Tom Brennan >>>>> <[email protected]> wrote: >>>>> >>>>> I don't agree (surprise!) I've always advocated putting all your eggs in >>>>> one basket, and then taking really good care of that basket with >>>>> backups, DR, procedures, dual this, dual that, etc. >>>>> >>>>> On 12/10/2021 5:55 PM, Bill Johnson wrote: >>>>>> This paragraph concerns me. >>>>>> One of the founding principles of the early Internet design was >>>>>> decentralization - by design, a single fault would not be able to take >>>>>> out everything. In a way, today's reliance on large cloud providers >>>>>> removes the benefits of decentralization; we rely on the scalability, >>>>>> cost effectiveness, and flexibility of today's SaaS and Cloud offerings >>>>>> yet we are potentially putting all of our eggs into one basket. This >>>>>> same statement applies to CDNs, as seen with the recent Akamai outage >>>>>> from this past summer. >>>>>> This was one of the drawbacks we experienced when our GM subsidiary (and >>>>>> all GM subsidiaries eventually) combined into EDS data centers. >>>>>> Charlotte was where ours was located. If the mainframe went down in >>>>>> Charlotte, multiple GM subsidiaries were screwed. Costing GM tens of >>>>>> millions in highly paid union labor twiddling their thumbs. >>>>>> If an ETSY business owner selling crocheted scarves has a 4 hour outage, >>>>>> it's probably not that bad. If an auto plant, bank or brokerage, health >>>>>> care provider, insurance company, or airline is down for 4 hours, it >>>>>> could be disastrous. >>>>>> Clouds aren't all they're cracked up to be. >>>>>> >>>>>> >>>>>> Sent from Yahoo Mail for iPhone >>>>>> >>>>>> >>>>>> On Friday, December 10, 2021, 8:00 PM, Mark Regan <[email protected]> >>>>>> wrote: >>>>>> >>>>>> Since this topic is still somewhat active, I thought I'd forward this >>>>>> link. >>>>>> >>>>>> https://www.thousandeyes.com/blog/aws-outage-analysis-dec-7-2021 >>>>>> >>>>>> Regards, >>>>>> >>>>>> Mark Regan, K8MTR, EN80tg >>>>>> CTO1 USNR-Retired (1969-1979 active; 1979-1991, reserves; including two >>>>>> years with the Ohio Air National Guard) >>>>>> Nationwide Insurance, Retired, 1986-2017 (z/OS Network Software >>>>>> Consultant) >>>>>> Email: [email protected] >>>>>> LinkedIn: https://www.linkedin.com/in/mark-t-regan >>>>>> >>>>>> ---------------------------------------------------------------------- >>>>>> For IBM-MAIN subscribe / signoff / archive access instructions, >>>>>> send email to [email protected] with the message: INFO IBM-MAIN >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> ---------------------------------------------------------------------- >>>>>> For IBM-MAIN subscribe / signoff / archive access instructions, >>>>>> send email to [email protected] with the message: INFO IBM-MAIN >>>>>> . >>>>>> >>>>> >>>>> ---------------------------------------------------------------------- >>>>> For IBM-MAIN subscribe / signoff / archive access instructions, >>>>> send email to [email protected] with the message: INFO IBM-MAIN >>>>> >>>>> >>>>> >>>>> >>>>> ---------------------------------------------------------------------- >>>>> For IBM-MAIN subscribe / signoff / archive access instructions, >>>>> send email to [email protected] with the message: INFO IBM-MAIN >>>>> . >>>>> >>>> >>>> ---------------------------------------------------------------------- >>>> For IBM-MAIN subscribe / signoff / archive access instructions, >>>> send email to [email protected] with the message: INFO IBM-MAIN >>>> >>>> >>>> >>>> >>>> ---------------------------------------------------------------------- >>>> For IBM-MAIN subscribe / signoff / archive access instructions, >>>> send email to [email protected] with the message: INFO IBM-MAIN >>>> . >>>> >>> >>> ---------------------------------------------------------------------- >>> For IBM-MAIN subscribe / signoff / archive access instructions, >>> send email to [email protected] with the message: INFO IBM-MAIN >>> >>> >>> >>> >>> ---------------------------------------------------------------------- >>> For IBM-MAIN subscribe / signoff / archive access instructions, >>> send email to [email protected] with the message: INFO IBM-MAIN >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to [email protected] with the message: INFO IBM-MAIN >> . >> > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > . > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
