The Computer Aided Manufacturing User Society (CAMUS) is one of the few user associations that remain as 3000 resources. It's a modest group made up of a few dozen MANMAN sites that rely on MPE/iX. Much of the devotion is wrapped around efficiency and stability. ERP is a big migration that can take years to get right. These 3000 sites are absorbed with keeping their ships in the deep water, away from the shoals of premature change.
Change is coming, though, as if it's a lighthouse on the horizon for the 3000 skipper. The change is called 2028, or more accurately, Dec. 31, 2027. In about 10 years or so, MPE/iX will stop keeping dates as expected. Nobody could forsee a day, 45 years ago, that a 3000 would still be in production service. The HP 3000 will turn 55 in late 2027. There's a good chance emulation hardware will be functioning well on that last day of 2027. Stromasys has made the lifespan of HP's MPE hardware a non-critical element.
Some customers are looking at how to edge past that lighthouse of a date. CAMUS holds a phone-in user group meeting once a year, and this month's meeting wants to examine ways to steer around the 2028 reef. It's possible, and CAMUS might be the group to help steer this course. All it takes are production systems that could be cloned and tested with a fix.
The group has invited its members and 3000 experts to discuss the workarounds. The meeting has been penciled in as a Thursday, November 16 event. "We are looking to bring in experts to speak to the issue of what is being described as the Year 2028 Problem,” said Ed Stein, "which is where HP 3000 systems run out of valid dates beginning 1/1/2028, per the MPE operating system."
CAMUS meetings are free to attend, meaning it matches up well with the operating budgets for many 3000 shops. The server's in a mission critical position at companies which aren't devoting much spending to it. That's always been one of the 3000's charms: it delivers more than it receives. Managers can get more details on the meeting and sign up by emailing Terry Glendon Lanza or calling her at 630-212-4314.
Tactical planning for the HP 3000's future is a current practice at shops like MagicAire. The company that manufactures mobile cooling units has a Series 939 that continues to run MANMAN and carefully-crafted applications. Ed Stein there has a need to think about something more pressing than getting his apps and utilities licensed for emulator use. He's thinking strategic.
Stein chooses to think about the end of the 3000's calendar days. He's interested in getting someone to fix the date issue that will arise at midnight on Dec. 31, 2027. The foresight is the first customer readiness we've seen that examines what can be done before that day arrives.
Developers and vendors have been talking about 2028, but not yet in explicit design language. Stein is the first customer who's doing the talking.
I am more concerned right now with the Year 2027 MPE issue. Not that we plan to be on MPE in that year—but if a fix is to be had, that fix needs to be done sooner than later, given the age and availability of the required expertise to develop a fix. There may be no one around in 2026 who knows how to fix it, in the event that in the worst case we are still on an HP 3000.
My company would look at paying for a fix now as insurance.
It's 10 years and five months away, but the end of 2027 is the deadline for regular date handing to stop working. It makes the challenge a Year 2027 issue if you consider Y2K to have been a Year 1999 issue. The most intense work always happens ahead of a deadline. If you're savvy, it's many years before a deadline.
There are likely partners on the horizon for the 3000 community's efforts to leap into 2028 (a Leap Year, by the way, but that calendar event won't be of any help.) Looking out into a world of 10 years from now, virtualization and emulation will still be operating at companies. Stromasys has the most to gain from keeping MPE/iX moving forward into 2028.