I have watched this thread, and there is simply one thing most of us are missing. This is a MF forum. For years, we have been subjected to "oh using the (insert new technology) is so much better than these old obsolete mainframes." And we have universally warned not to drink the Kool-Aid.

So excuse us a bit of satisfaction when the one of these "master of the universe" technologies has a problem that renders it mortal, like these old, obsolete mainframes.

Proving once again the certainty of Murphy's Law (or one of the corollaries): "What can go wrong, will go wrong, and at the most inopportune time."

Doug Fuerst

------ Original Message ------
From: "kekronbekron" <000002dee3fcae33-dmarc-requ...@listserv.ua.edu>
To: IBM-MAIN@listserv.ua.edu
Sent: 08-Dec-21 8:32:48
Subject: Re: AWS is down.

True, I haven't worked in healthcare.
I do apologize for being a bit dramatic in refuting the initial statement.
I just don't get the 'this way or no way' perspective, however understandable 
it is.

IBM's own quantum efforts may make MF irrelevant.
Tech will keep evolving, yes MF is excellent at what it does.
But why hold on to the favourite box and see nothing else.
Even if MF is around for 500 years, is it really going to stay as excellent as 
it has been?
I'm only seeing "hey! I can do it too" sort of implementations of "new" sw on Z.
On the hardware side, I can't wait for DS9K etc.
What would be excellent is if zOS v3 started afresh and cut out all the baggage 
of backward compatibility... for those who can afford to do that and therefore 
take the gains therein.

- KB
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Wednesday, December 8th, 2021 at 6:01 PM, Bill Johnson 
<00000047540adefe-dmarc-requ...@listserv.ua.edu> wrote:

 I see someone who has never worked in health care where the mainframe 
processes each drug prescribed and checks for drug interactions in a 
microsecond. Yes, people die if the mainframe isn’t available. It’s also why 
there are plenty of pharmacies open 24 hours and why hospitals have pharmacies.

 Sent from Yahoo Mail for iPhone

 On Wednesday, December 8, 2021, 1:33 AM, kekronbekron 
000002dee3fcae33-dmarc-requ...@listserv.ua.edu wrote:

 Critical infra in some places, sure, not everyone is denying that.

 At the moment of urgent need, do people really buy something and wait for MF 
to finish processing, for them to be then allowed to continue breathing?

 What happened to the interim stages (logstics etc).

 It sounds as though failure to buy/order something immediately is going to 
lead to their death... is what's being said.

 Sounds pretty privileged to me.

 It also sounds like it's assumed that mainframes will last 500 years, no?

 Did the world not exist before 1960s?

 Did people automatically die before 1960s because they didn't have MF?

 Are people and organizations not allowed to be wrong (to their own detriment), 
etc.

 Are we sure that 100% of all information out there is truth, apart from this 
announcement that AWS wants to replace MF?

 We can all like MF, but don't need to act like it's the sole saviour of 
humanity.

 Again that means that all technology that evolved since then is a complete 
waste of time and people's efforts.

 Sounds pretty delusional to me... just to convey that MFs are good servers.

 -   KB

     ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

     On Wednesday, December 8th, 2021 at 10:00 AM, Bill Johnson 
00000047540adefe-dmarc-requ...@listserv.ua.edu wrote:

 > AWS had a larger & longer outage today, than all the outages on the 
mainframes I’ve worked on in the last 30 years. Much worse. Yet, some here think AWS 
is going to replace the mainframe for critical applications like banking, health care, 
big retail, and insurance. Plus, the mainframe has had plenty of negative posts here 
in the decades I’ve been involved. Nobody dies when Netflix isn’t available. (One of 
the hits from today) people can and do die if the drugs they need aren’t available 
because the computer system is down.
 >
 > Sent from Yahoo Mail for iPhone
 >
 > On Tuesday, December 7, 2021, 11:01 PM, kekronbekron 
000002dee3fcae33-dmarc-requ...@listserv.ua.edu wrote:
 >
 > Not at anybody in particular:
 >
 > Do we have to make snide remarks because someone else had an outage?
 >
 > Don't we remember the times when things on the mainframe itself went south?
 >
 > Has every site's MF env. been 100% available through all these decades?
 >
 > Is it wrong to fail sometimes?
 >
 > Is this the attitude with which you'd like to retire, holding onto precious 
remarks and burning the path behind you as you leave?
 >
 > What does that say about one's mentality and outlook in life?
 >
 > -  KB
 >
 > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
 >
 > On Wednesday, December 8th, 2021 at 3:54 AM, Ronald Wells 
000002ebc63ff5ef-dmarc-requ...@listserv.ua.edu wrote:
 >
 > > Pretty pic/web pages make the $$ did you not get the memo
 > >
 > > -----Original Message-----
 > >
 > > From: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU On Behalf Of 
John McKown
 > >
 > > Sent: Tuesday, December 7, 2021 2:57 PM
 > >
 > > To: IBM-MAIN@LISTSERV.UA.EDU
 > >
 > > Subject: Re: AWS is down.
 > >
 > > ** EXTERNAL EMAIL - USE CAUTION **
 > >
 > > Oh, but they advertise that they can replace mainframe. Well, maybe the 
processing. But not the on site reliability. Of course, for WFH, the internet is the 
week point. And, most likely, also the home equipment. I just had to reboot my 
Windows PC at home because it decided to stop talking to my internet router.
 > >
 > > On Tue, Dec 7, 2021, 12:49 Bill Johnson < 
00000047540adefe-dmarc-requ...@listserv.ua.edu> wrote:
 > >
 > > > Amazon Web Services is down. I can’t get to my pictures. Glad we don’t
 > > >
 > > > have our mainframe running there.
 > > >
 > > > 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
 > >
 > > Email Disclaimer
 > >
 > > This E-mail contains confidential information belonging to the sender, 
which may be legally privileged information. This information is intended only for 
the use of the individual or entity addressed above. If you are not the intended 
recipient, or an employee or agent responsible for delivering it to the intended 
recipient, you are hereby notified that any disclosure, copying, distribution, or the 
taking of any action in reliance on the contents of the E-mail or attached files is 
strictly prohibited.
 > >
 > > 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


 
-----------------------------------------------------------------------------------------------------------------------------------------

 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