"a variety of alternative communications tools"
Does this include dusting off the long forgotten IBM typewriters? and not the electronic ones either. I hope it's the 1940's versions where you had to bash each letter with a hammer
IBM's email migration misadventure has been worse than the IT titan has let on, current and former staff have told us. Big Blue yesterday acknowledged "some IBM employees are experiencing email service delays," and that the company is using "a variety of alternative communications tools to ensure minimal disruption to our …
Selectrics rock! I have one that works and one I'm trying to fix. They are *completely* mechanical.
But why stop there? Teletypes! They were used for business for years, until these fancy computers came along. Also completely mechanical (except for the selector magnet driver card). They run over regular telephone lines...
...Yep. IBM's hosed.
Indeed. And I can imagine a phone conversation something like this...
PHB: Hi Bob, how you doing? It's Ian, your old manager at IBM.
Bob: Ah yes, the one who laid me off.
PHB: Erm, yes, err sorry about that. The thing is, we're having a small issue with a migration, and our new hires are having a few, erm, knowledge issues, and we were wondering if you'd like to come back as a contractor for a few weeks to help out. Would you be interested? Please say yes...
Bob: Sure, I can do that for you. My rate will be £5,000.
PHB: £5,000 a day? That's a bit steep Bob!
Bob: No, that's per hour, you snivelling little fuckwit. And I want it written into my contract that I get to call you that as often as I like...
Indeed. I wonder if they have tried to contact their (older and laid off) ex-workers in the hope of getting them to come and fix this issue.
Serves them right for getting rid of more expensive, older, experienced workforce in favour of unskilled, cheaper greenhorns.
Because anybody can just google on how to fix a Bloated Goats issue, right?
A clear case of penny-wise, pound foolish.
When we migrated away from on-prem Exchange to O365, the two systems was briefly running in parallel while we verified that all user data have migrated successfully, and only then did we pull the plug on the on-prem Exchange.
All of this happening at the same time as IBM starts using SalesForce solutions for its field personal. I am not surprised that this is hitting the fan and combined with the CSP program that they are running now, you will see a huge downturn in revenue for IBM as a whole. Clients are pissed and looking for other alternatives that are reliable, other than IBM
I was *very* glad to see the back of PROFS, despite Notes being only half useable at the start. But in those days, there were competent people highly motivated to make stuff work. Nowadays, the "management" believes that you can buy competence wherever it's cheapest by the square metre, and manage it by KPIs. They deserve the result, but it's bad luck on the employees and customers (if they have any of the latter).
Yes, but in 1994 when I had a very early laptop, I had to convert my email inbox on PROFS into a single flat file and download it to my laptop (with EBCDIC to ASCII translation of course) to my laptop. I could then read my email and write replies as I travelled, then upload the replies back to PROFS when I got home to send them off ...... it could be done but it was hardly a pleasant process!
Profs was good, but then they went to that wretched Notes running under an even more wretched OS/2. Notes worked better under Windows 3.1 for Workgroups. I'll never understand why Notes wasn't ditched long ago; it seems to have infested IBM like a virus which is hard to destroy.
Before PROFS or NOSS as HO liked to call it, some of us end-users used TSO for messaging and script document creating. We also had the benefit of being able to browse the PL/1 source code for our applications and advise ADM of code changes needed to fix bugs. Happy days then when everyone pulled together with respect to everyone; those are now distant happy memories.
18 months but keep in mind how slow IBM internal processes are. What IBM does in 18 months, others would do in 3-4. The added months are just for the added layers of bureaucracy and beancounter approval.
So the question would be, are 3-4 months really enough to plan for such a migration?
Agreed 100%. However, business analysts get too hung up on quarterly results. If a few sales shift by a few days did your company's performance really change by much? Probably not.
I used to work at a publicly traded manufacturing facility. Their management was focused on month-end numbers. Make your monthly target or catch hell. Result was that at the end of every month, there would be a mad scramble of overtime. After the beginning of the month, there'd be a few days where people would be sent home for lack of work.
Always seemed to me that saving the overtime and expedite fees would be a good idea. We didn't lose any sales, they'd just occur in a different month.
Oh, it's worse than just "end of quarter". They scheduled it for the last possible date before HCL shuts off the cloud servers that IBM previously relied on.
So they left themselves with no margin to fail back to the old system, reassess, and take a second run at it, if everything went pear-shaped.
And of course everything went pear-shaped.
As the article points out, IBMers have Slack access, so for internal communications, having e-mail servers a bit flakey is probably not that big of a deal. Probably would not hurt IBM if more of its people shifted some away from doing so much e-mail, kind of a forced learning experience. For a lot of the development areas, a Slack outage would probably have more impact. But sales & service, not-so-good to have these sorts of e-mail problems.
E-mail (and Chat, including Group Chat like Slack/Microsoft Teams/Sametime/etc.) always seems problematical. I do not think I have run into an e-mail system that did everything I wanted. IBM sold off Notes/Domino to HCL, sounds like parts of these problems have to do with updating to current there. But the alternatives are also somewhat problematical, Microsoft Exchange/Outlook has its own set of difficulties (proprietary aspects, deficiencies on the scheduling/calendar sides, lack of decent migration support, etc.), Google Mail the same (continues to improve and has some nice search stuff, but the surrounding apps are a bit weak), and so forth. I am actually a bit surprised that after all these years that there are not better options, e-mail and chat wise, particularly cross-platform. Google and to a lesser degree Apple, when external/private are factored in, probably have the biggest market share, and the advantage of working with a lot of different clients and so forth, but it all seems a tower of babel.
I am actually a bit surprised that after all these years that there are not better options, e-mail and chat wise, particularly cross-platform.
There is a better option for an e-mail client (Thunderbird), the problem is more with the mail server part of it.
Writing a native mail client is complex - cross-platform even more so - and open source plus web mail killed the market for commercial clients.
Thunderbird was an attempt - but it was ill-designed to comply with outdated mail setups nobody uses, and it requires a far more complex UI than a web browser - something Mozilla can't deliver, especially with the latest changes made to FIrefox.
Only Outlook really keeps on because MS need it to sell Exchange. And it's some time its IMAP features have been reduced.
Many IBMers will tell you that Slack really does not work well for an organization the size of IBM. It's great for ephemeral chats with small groups or individuals, but if you ever want to find a conversation again more than a couple of days later? Hopeless.
TBH I like Slack, but it's not remotely a substitute for enterprise email and/or document management.
Slack is crap, and especially as IBM has implemented it. Everyone there hates it except the IBMers who have never worked anywhere else and don't know any better...because they have never used anything but Notes/Sametime.
I've seen perhaps six or seven email migrations at different work places, and they have all gone remarkably smoothly for end-users. Never been without email, even for an hour, and never had messages lost. That's included Notes to Exchange, merging local systems into the corporate system after take-overs & reorganisations, moving from on-site to off-site, and moving hosting from one continent to another. Ironically one migration handled by an IBM team without any visible trouble at all . Of course it is a difficult task and probably all sorts of trouble went on in the back-ground, but it is a task that most IT teams are totally on top of and get right - credit to them.
I've administered both Notes and Exchange, and I would rather set my own dick on fire than manage Notes again, and that's not even factoring in the abortion of a client. I can't help but believe that Notes "lovers" have some form of Stockholm syndrome. Notes is a better application platform, I will grant that much, and it is certainly easier to deal with than SharePoint, but on the email/calendaring front it blows goats.
Good luck, IBM! My years of refusing to even look at IBM technology are certainly seeming wise!
This fiasco is what happens when you have manglement not management. Many have migrated emails from one system to another without any issues on numerous occasions. Often this is done when there is a merger or purchase. But with the generally ineptitude at Itsy Bitsy Morons I am not really surprised at something like this.
Notes server is actually a very sophisticated (for its time back in the late 90s) application server and database. Yes, it also does email. But there are Notes applications and databases that require the fat client and people need the applications to do their jobs. I used to write Notes applications back in the late 90s and it was amazing what it could do at that time. Sure, email could be migrated to some other solution and probably will be in the near future. Actually, surprised that email hasn't been migrated since other internal IBM products like Sametime for chat was abandoned for a non-IBM solution (Slack).
VM/CMS "msg" command! (or vmsg for that matter)...
or, if you want to tell the responsible fuckwits they are fuckwits without your sender id then "msgnoh"! (msg with no header)
or, if you wanted to use one of the rexx utilities people wrote that would use msgnoh to translate the characters into 10+ line character high equivalents even better (bigmsg and other variants) to call them a very big fuckwit in very big letters!
p.s. is there an EBCDIC to morse code utility?
Notes was an abomination 20 years ago. In the late 1990s, a company I worked for was taken over and the new owners inflicted Bloated Goats on us. We reverted to hand written sticky notes, because we could write a message on a note, walk downstairs, stick it on the recipient’s monitor and return to our desks in less time than it took to type up the message in Scrotes and send it. What on earth is IBM doing still using it?
Words cannot explain how much I loathe Lotus Notes… this goes close (Hitler switches to Lotus Notes):
I know of several big accounts who set up their own email solution using O365 because the clients said Notes/Verse does not have enough security. That should have been enough to kill Notes/Verse ages ago. Part of me thinks this is intentional to have justification to get out of the contract with HCL. I’ve seen clients do this before to GTS contracts.
None of the extremely highly paid execs have ever had an idea to actually fix anything. Just like Governments, they just observe events, and call it policy.
Hardware business going badly? Fix the bad management? Noooo... declare it unfixable and sell it off.
Now we are Software and Services! But they can't do that so....
Now we are The Cloud! Only they can't do that either.
Anybody that hires IBM for anything must have been bribed.
IBM is the last (and only) significant tech company still using the steaming pile of offal known as Domino/Notes.
The move is underway, IBM's entire CIO/Executive organization have already been moved to Outlook/Exchange (refusing to eat the dog food) over the last two years, and were not impacted.
Biting the hand that feeds IT © 1998–2021