Congratulations to us all. This is the 15th anniversary of the "we're killing off the 3000" announcement from HP. The end-game hasn't played out like HP expected. In 2001 the company's management didn't see three CEO resignations coming over those 15 years, or the company being forced to split itself to stay relevant to enterprise IT. Those two events are related. Yes, the 3000 got its pink-slip notice at the HP of 2001. So did the overstuffed, unwieldy Hewlett-Packard. The company that lurched toward every business while stepping back from others. It took 14 years almost to the day, but HP is half the size it was: HP Enterprise is the severed sibling from 2001's family.
Inside the 3000's division during that year, no one was talking about emulating the 3000 PA-RISC hardware that the company would stop building in 2003. That's now a reality, a new development since the 10-year anniversary of this sobering date. Hewlett-Packard was going to lead four customers out of every five away from MPE/iX, delivering them to the Unix alternative of HP-UX. Windows was going to get new customers out of the upheaval, too. No one figured three of every four departing companies would choose a non-HP environment.
Here on this date in 2016, the idea of an environment as a crucial strategy is feeling outdated. IT directors always cared about applications. Now they're told they don't have to worry about environments. The cloud computing providers will do that for them. Except when they cannot provide the cloud. Behold (above) the map of Internet outage from last month on an ugly day.
The Support Group's Terry Floyd offered a Plan B strategy to the manufacturing customers of CAMUS last week. More than 30 companies using HP 3000s and MANMAN are in the CAMUS user group. Floyd's company is delivering a fresh alternative to help MANMAN sites move on from the 3000. But he also supports homesteading sites. With a foot in both worlds, he recommends staying safe by having a Plan B, even while you employ cloud computing for your future.
If any of you are thinking about cloud apps, you should think about a hybrid app. You'd have some stuff in-house on your own boxes, and some stuff out there on the cloud. For instance, we're doing EDI [for a client]. It's pretty much local. We'll be able to receive and send stuff even if the Internet went away for a day. It would kill us not to be able to do EDI. Even hours of Internet downtime would kill us in some situations.
Think about what you might consider really critical to your company—and think about putting some of that stuff in-house. Having shipping on a local server, for example a SQL Server, we'd be able to ship whether the Internet's up or down.
"Sometimes the Internet goes away for different people for different reasons," he said, and it's so very true. DDoS attacks are becoming a too-regular event for the world's Internet. When Twitter, Netfix, Amazon, Tumblr, Reddit and Pinterest can be taken offline at once, as they were on that map of Oct. 22, everyone needs to manage the risk. A Plan B once meant staying on the HP 3000 in spite of HP's community exit. Today it means keeping some computing local, no matter what your enivronment.