RIM Needed a Mainframe

Has anybody else noticed that IT service delivery is bad and getting worse? Hardly a day has gone by when there hasn't been a big security or availability failure.

For example, Rearch in Motion (RIM), the maker of the Blackberry, certainly needs — needed — a mainframe. The company is already in trouble, rapidly losing marketshare, and now they can't even keep their messaging service running. If businesspeople cannot rely on RIM to keep their Blackberries in service, then they'll stop buying Blackberries. RIM might go out of business as a result of this disaster. How much does bankruptcy cost?

R.I.P., R.I.M.

by Timothy Sipples October 19, 2011 in Business Continuity, Current Affairs


TrackBack URL for this entry:

Listed below are links to weblogs that reference RIM Needed a Mainframe:


I think RIM needs much more than a mainframe. It's becoming clear that they need to make major high-level management changes in order to survive.

Posted by: Anthony | Oct 20, 2011 7:26:05 AM

A switch died, not a server...

Posted by: Nicolas | Oct 21, 2011 9:48:14 AM

You don't need many network switches if you don't have lots of servers to connect.

Posted by: Timothy | Oct 25, 2011 11:17:24 PM

Does any one know how to copy from Z/OS or ftp a pds load library to a laptop and
back again.

Posted by: Tony Santo | Oct 31, 2011 2:30:29 PM

The comments to this entry are closed.

The postings on this site are our own and don’t necessarily represent the positions, strategies or opinions of our employers.
© Copyright 2005 the respective authors of the Mainframe Weblog.