Some of the members of the 3000 community had no reason to believe HP would pull out of the 3000 business. In this week that marks the 10th anniversary of that exit, community members are sharing their stories of where they were when they heard -- how much they felt they could believe -- and what's become of their careers since then.
Brian Edminster: I was subcontracting at a company that specializes in supporting medical information systems (primarily Amisys, but others as well). This was a new contract at the time, and came after a multi-year gig doing a Y2K conversion on a large legacy Retail Management system.
I almost didn’t believe the news — there were too many other big changes happening in the world — and HP management had recently redoubled their support of the platform, so I just couldn’t believe it at first. I guess I was still expecting the New HP to act like the Old HP.
My consulting practice has been stable, with slow but steady growth. I’d say that my career has taken directions that I’d not have been able to anticipate, just a few years before. I’d not have gotten into open source software on the platform if the ecosystem of commercial software hadn’t started drying up. I wouldn’t have been able to justify going to the last Greater Houston RUG meeting to present a paper, and I wouldn’t have started building a website to act as a central repository for free and open source software for the 3000 (www.MPE-OpenSource.org).
Robert Holtz: I was working away on the COBOL and FORTRAN programs that were the heart of the Computer-Aided Dispatch and Mobile Data Terminal programming that ran on the three HP N-Class 3000's our Phoenix Police Department had upgraded to -- just earlier that year.
Christian Lheureux: I was sitting at my desk at Appic, sorting through HP3000-L newsgroup postings. I learned that the HP 3000 was going to be terminated from an HP internal source that I could absolutely not quote due to an ongoing NDA. In fact, I had been informally tipped much, much earlier that this was going to happen, but I simply could not believe it !
If you were there 10 years ago, you probably remember that some emotions ran quite wild, and that certainly includes mine. After a while (weeks, months), I remember having a big sigh and realizing that, in the aftermath of the Compaq takeover, HP would not keep 2 proprietary platforms and that, between a 71,000-unit installed base (HP 3000) and a 700,000-plus-unit installed base (VMS), the choice was quite obvious. To this day, VMS still exists. They even recently introduced a new release.
The company I worked for that the time still exists as a software publisher. We went bankrupt in late 2005 and the company was finally liquidated 1 year later. I probably sold the last four new HP 3000s in France, on Oct. 31st, 2003. I did my last significant MPE assignments in 2004. After that, my HP3000/MPE activity rapidly became marginal. When our company went bankrupt, I was immediately made redundant. Therefore I have absolutely no idea of what happened to the systems I had in the datacenter -- well computer room. They probably ended up in a garbage dump, much like an unneeded refrigerator that burns too much energy.
I later did some HP-UX work, then became a sales exec, then went back to pre-sales, which I still do today. I've been part and parcel of the HP ecosystem for all my adult life, HP user as a student, then HP employee, then HP consultant, then HP partner. My HP-UX skill level never rivaled my MPE knowledge, not even close, not even by a long shot. And, perhaps more important, the fun I had doing HP-UX stuff never came close to the fun I had doing MPE things like debug/dumpreading, executable code troubleshooting, performance measurement, developing tools that I needed for other assignments, writing stuff, "educating" customers, etc.
There used to be two documents that I wrote on the OpenMPE website while I served on the board. One was the DAT compatibility matrix, and the second one was the HP(e)3000 line-up, sorted by software tier, complete with performance indicators. I have absolutely no idea whether those documents still exist and if they are available anywhere. My best guess would be that,10 years after, no one cares.
That's history being made. Things come and go.
John K., AOL: I was sitting at my desk in AOL's Reston Technical Center in Reston, VA, when I heard the news. I was the manager of the Access Wardialer Lab, which filled a little over 1,100 sq. ft. of raised floor with racks containing hundreds of test and measurement PCs connected to three DS-3 lines providing telephone lines.
We had one HP 3000, and it collected, stored, and analyzed access wardialer data from hundreds of PCs which called every AOL dialup number multiple times every night to test the dialup network and hammer the AOL Windows client. The HP 3000 produced a number of reports, charts and emails every day, with virtually all of AOL's senior executives and management on the distribution lists of those emails. It also hosted a web site for retrieval of reports, processed wardialer data, Windows "debugview" logs, and other analytics. I'm told that the HP 3000 was turned off and stored for somewhere between 12 and 18 months, and then converted to an HP 9000 (AOL had many, many, many HP 9000s).
AOL's dialup usage took a nose dive in 2004, and in late 2004, my group was disbanded (layoff). Since then, AOL has split off from Time Warner. The AOL Reston Technical Center where I worked no longer exists. I was invited to, and attended AOL's 25th Anniversary Celebration in Dulles, Virginia, on May 24th, 2010, and it was great seeing so many of my former co-workers, most of whom have moved on to other jobs in the various tech industries. While a manager at AOL, I also coded in SPLASH, SPL, BASIC, and BUSINESS BASIC, and I created both terminal-based and web-based applications.
Today I'm the Software Engineering Manager for an Internet Services Provider which also provides hosting, co-lo, and VoIP telephone services. I still code, but now I code primarily in PHP and SQL, and the company's Enterprise Information System (EIS) is of my design. I also wrote all of EIS's core code.