News Outta HP

Moving the 3000 Into HP’s Gray Areas

Reprinted from December 2002


Dave Wilde is leading HP through fresh territory in its final year of selling HP 3000s. The business manager for HP’s 3000 operations is overseeing the details of establishing a homesteading practice for customers who choose not to migrate. It’s work that serves as a counterpoint for HP’s assurances that all the pieces are in place for customers who must move their applications onto other HP systems.

After this year’s HP World, customers left Wilde and HP with a host of questions about what else HP can do to assist 3000 owners in staying on the platform. Emotion hadn’t cooled, as HP reported to some publications, but a practical dialogue began between the vendor and its customers about how homesteaders will manage in a world without HP’s resources.

One persistent question began to surface, too: why HP wants to remain a force in a computer community where it will cease sales in 11 months, and end support in four years. It was just one of several queries we wanted to follow up on after the conference, during the months when HP is planning its next set of homesteading announcements. We spoke with Wilde in the weeks after HP World by phone, where he explained HP’s objectives in the 3000 homesteading market and what he’s willing to consider.

Why does HP want to force its customers to use HP hardware while running new MPE licenses on Intel-based systems? Why can’t HP let go of MPE?
The decisions are guided by a couple of factors. One factor is that we clearly want to retain a relationship with customers, to keep them as satisfied HP customers. Clearly as we move forward, we want to structure things in ways that are good for our customers, and continuing to play a part in our customers’ long-term satisfaction is important.

I recognize some of the concerns that people might have — on one hand, walking away from the platform, coupled with this may feel a little bit odd to people. But there’s a fundamental philosophy at play here. It’s important to HP that we continue to play a role in understanding the customers’ needs and in addressing those.

As an example, this licensing question that came up about the emulators: we feel strongly that going forward we’re going to have a market-leading offering in the server space. We would like customers who want to move forward with MPE to do that with HP hardware.

We said HP hardware. In the shorter run that could be HP PA-RISC hardware. It’s not only Intel-based solutions.

What’s going to make the HP solution a better deal for the customers, as well as better for HP’s sake?
We’re going to have a market-leading offering. Where customers are staying with HP-based solutions, it’s in the interest of the customers to have access to market-leading hardware.


Does HP still want these customers?
Yes. For customers who have a need to run things beyond HP’s end of support date, we’re trying to address things so they’re retained as HP customers. The things we announced which HP would try to enable after HP’s end of support date are really targeted at those customers who have more stable environments and smaller environments, and it’s more practical for them to run things beyond HP’s end of support date. It’s not our belief that’s going to be beneficial to or attractive to customers with large organizations, large applications and dynamic environments.


I understand HP’s beliefs haven’t changed. But is it true that you recognize some portion of your customer base won’t be moving away from the system?
Some of our customers have told us that they need more time to plan their transitions, and others have told us they do not intend to transition. They want HP to work on solutions, and work on solutions with our partners, to make that sort of environment more available to them.


Are you willing to recognize there’s a subset of your customer base that can’t afford to do this transition?
Yes. Their drivers are that it’s may not financially the right move for them, either because they can’t afford that transition or they’re deciding it’s not worth it for them to make the investment [in a transition]. We’re trying to have a set of solutions for them to help them address that, without going so far as to say we think that’s the right answer for the majority of the customers. We recognize there’s a significant segment, and we’re trying to be responsive to that.


Nobody has heard from a large enough segment of the customers to have a number that's representative, right?
Yes. I’ve heard different numbers, and I’d rather not get into guessing what the size of that segment is. I’d believe that it’s far from the majority, but it’s a very significant segment.


How soon can HP have a proposed MPE license fee in place, so the companies which are considering building a hardware emulator can gauge their market?
One of the things we said at HP World was that I prefer not to trickle information out one-off. It has a tendency to confuse the message and also tends to be inefficient in terms of getting substantive announcements to our customers. We were able to announce a solid bundling of new information, as well as consolidating that with existing information, and I like that model much better.

The model that seemed to resonate with the folks at HP World was roughly quarterly announcements, while providing updates when available. That would indicate around the end of this calendar year.

I will state, and I think this is important, that with this licensing HP is not looking towards structuring the MPE license to make the emulator financially unattractive to customers. We don’t want to state anything about particulars until we’ve thought the costs through and what some of the customer needs are.

Gavin Scott of Allegro said he thought it would be a lot more attractive to any company offering a hardware emulator if they could ship off a demonstration version of the emulator with enough MPE for a test. This involves someone shipping off MPE other than HP. Is that prospect possible?
I’m very open to different alternatives and approaches within the boundaries we announced at HP World.

The objective is to help make this solution work, right?
Yes. Another objective is to make sure that expectations are clear, so we don’t oversell and overset expectations for customers.


Are you willing to get into a position where HP’s just collecting royalties for MPE?
I’m open to lots of alternatives. There are many issues from a customer and partner perspective: legal issues and constraints in the future that we want to make sure don’t result in an untenable position for anybody. That’s one of the reasons we want to be, not vague, but non-specific at this point. We’re in a gray area we haven’t been in before.


What’s HP’s position on third parties taking over portions of the delivery chain beyond the end of sales date next Oct. 31?
We’re working on partners with different elements of the value chain. That’s something we’re definitely doing in the transition space. Another area is remarketed systems, and we have a very strong relationship with Client Systems’ subsidiary Phoenix Systems. We’re definitely interested in working with them. We’re open to documenting what we’re doing so customers' and partners’ interests are also protected, along with HP’s interest.


Documenting what?
Suppose the emulator runs on HP solutions. We want to make sure partners aren’t left in a bad position in case HP makes future decisions that are inconsistent with that announcement. We’re very open to different arrangements, subject to representing reasonable business needs from HP’s perspective.

The point is that I’m very open to needs not just from HP’s perspective, but also from a customer and partner perspective. We’ll be working with the OpenMPE group and with partners and customers who are expressing concerns.

What’s the thinking behind maintaining the current pricing model for current A-Class performance?
Doing things like releasing all the horsepower that’s available in one chassis has a ripple effect that’s not acceptable for the pricing model. But we’ve heard that customers who have bought into an A-Class chassis may have some needs for more upgradability. One of the questions we asked was if there was a price associated with an additional upgrade within an A-Class chassis, would they be interested? That’s a price consistent with our overall pricing model. There seemed to be some interest in that which we’ll continue to look into.


Is this a way for a customer to avoid having to find an N-Class system to upgrade to after HP’s sales of N-Class systems stop?
Yes. If there’s enough interest and demand, and we can structure it in a way that it fits in well with our established pricing model, it’s something I’d be open to trying to structure.


Why so much attraction to a pricing model that was conceived before HP decided to leave the 3000 market?
It just isn’t practical for us to restructure the pricing model. We feel we structured it in a way that there’s appropriate value in the system for what we’re delivering. It’s a reference to purchases that have already been made.


You recently made a healthy reduction in that cost to customers with the new pricing. Why not continue in that with the A-Class?
Within limits we’ve obviously tried to offer strong value while recognizing the customers’ expenses they’ll be incurring through these transitions.


Is simplifying HP’s support through such an upgrade — which would give the 6.5 customers something to upgrade to in December 2004 — a factor in creating an A-Class upgrade?
There might be some impact there. But there are enough customers in different segments that some customers incrementally going to upgrade probably doesn’t fundamentally change the support picture from HP’s perspective. What’s more meaningful to me is if it gives customers more degrees of freedom.


How long do you think CSY will continue to operate as a virtual entity with HP after 2003?
CSY is the value chain that delivers 3000s to our customers. In that respect, it exists though 2006. How it’s managed internally is a subject that nobody can predict. From a customer perspective, for me the goal is that customers would see a 3000 business orientation through HP’s end of support date.


What’s the contact for that virtual CSY beyond end of sales? It’s looking like the reseller channel will be folding its tents next year.
From a channel perspective, what’s the contact point? We’re working closely with Client Systems in the Americas to identify different ways they can support customers. We’ll be continuing to work with all our partners. We’ll need to stay tuned as things move forward.

From an HP perspective, I’m the business manager, and I’m the go-to guy. We’d like to make sure the virtual CSY value chain is also represented cleanly and consistently to our customers. Exactly how that’s implemented over time may change. It works best where our customers would be able to work with HP in a centralized fashion.

Having said that, I continue to feel like I have an important role in adding value.

What about you? How long do you want to be the 3000 go-to guy?
I basically want to do this as long as two things are true. One is that I feel like I’m continuing to add value, and that HP wants me to continue doing that. Whether that’s months or years, nobody can predict. There’s no timeline for the end of that right now.

I didn’t expect a few years ago to be in the business, let alone in this particular role. Things have worked out in a way that I’m pleased to be in this role, and feeling like I have an opportunity to add value. It’s hard to tell these days what the future holds. Things are changing very quickly, both inside and outside the company.


Now, HP's Unix transitions to legacy

Wall of books
Hewlett-Packard Enterprise has issued dates to terminate support for two releases of its HP-UX Unix environment. Next year will mark the end of HPE’s support for HP-UX 11.11 and 11.12. The final, terminal version of HP-UX, 11.31, is already in the MPS category. This Mature Product Support repairs crucial bugs. HPE adds that this support level is “without sustaining engineering.”

MPS is a milestone that the MPE/iX operating system visited in 2007. In this state, the operating system is frozen for features. The legacy managers in the HP 3000 market found a silver lining in frozen status. Fewer elements of the MPE/iX environment were likely to break, since changes did not find their way into the base software. Already a reliable OS, taking MPE/iX into Mature support makes it even more stable.

HP-UX is another matter for a legacy manager. Unix, touted as the replacement for HP 3000 datacenters, holds a riveting reputation. Security flaws are a major element in an OS that powers IT so frequently. The more Unix running in the world, the less secure it becomes.

The year 2022 ends HP’s active support for HP-UX, but the shift away from the vendor’s teams isn’t stopping legacy use. This legacy milestone usually arrives while independent support companies take on the vendor accounts relying on the OS. Change is inevitable, but changes to legacy IT are fewer. Losing vendor support may not even mean different experts will take on the work. At VMS Software Inc., some support team members shifted from HPE jobs to work at VSI.

Indies to the rescue

In the HP 3000 marketplace, Beechglen Development took up HP 3000 support, among other companies. Just about the time HP announced in 2011 it was migrating its best HP-UX features to Linux, MPE/iX support from HP ended. Beechglen remains a support resource for legacy IT in both HP 3000 and HP 9000 communities. The company uses Nickel, a program to assess the state of software on an HP-UX server.

This Network Information Collector, Keeper, and Elaborator is “a shell collection script from Hewlett Packard,” Beechglen explains. It’s been maintained and modified through the decades by Beechglen. A NICKEL script runs on HP-UX systems 10.20, 11.0, 11.11, 11.23, and 11.31.

Nickels run as a review and reference for general system health. “The script also provides aid after system events for troubleshooting,” Beechglen adds, “and getting a system back up and running in as little time as necessary.”

Beechglen, Allegro Consultants, and other companies keep supporting legacy environments after the vendor leaves the market. These companies tout expertise from a “team who eats, breathes, and sleeps HP-UX and MPE for 33-plus years, in the most demanding environments anywhere in the world.”

HP’s Unix is entering the era where MPE/iX visited 14 years earlier. Like MPE/iX did, HP-UX has gained an extra year of vendor support. System vendors will continue to collect support dollars until the latest possible date. There’s plenty of value in legacy IT, all through the years after the vendor stops selling it.


A Day That Will Always Be Marked in Red

Calendar-pages

Back in 2005, November was still a month bleeding in the red ink of memory. You can use shorthand and say "November 2001." Or you can say the day that HP's 3000 music died. The date of November 14, 2001 still marks the start of the post-HP era for MPE/iX as well as the 3000 hardware HP sold. It took another two years to stop selling the PA-RISC servers the company had just revamped with new models months before the exit-the-market announcement. PCI-based N-Class and A-Class, the market hardly knew ye before you were branded as legacy technology.

For a few years, I stopped telling this story on the anniversary, but in 2005 I cut a podcast about the history of this enterprise misstep. HP lost its faith in 2001 but the customers hadn't lost theirs and the system did not lose its life. Not after November 14 and even not today. Not a single server has been manufactured since late 2003, and even that lack of new iron hasn't killed MPE/iX. The Stromasys emulator Charon will keep the OS running in production even beyond the January 2028 date MPE/iX is supposed to stop keeping accurate dates. 

Red Letter Days were so coined because they appeared on church calendars in red. They marked the dates set aside for saints. In 1549 the first Book of Common Prayer included a calendar with holy days marked in red ink; for example, Annunciation (Lady Day), 25th March. These were high holy days and holidays. The HP 3000 came into HP's product line during a November in 1972. November is a Happening read the banners in the HP Data Systems Division. No day of that month was specified, but you might imagine it was November 14, 1972. That was a Tuesday, while the 2001 date fell on a Wednesday. A total of 1,508 weeks of HP faith.

Something important happened in that other November of 29 years later. Hewlett-Packard sent its customers into independent mode. Those who remained faithful have had a day to mark each year, logging the number of years they've created their own future. It's 20 and counting as of this year.


HP knew nothing of November during October

Sgt. Schultz

He saw nothing, nothing

From October, 2001

Just weeks before HP started to brief its vendor partners about the 3000 futures cut-off, customers asked about it. In a public forum of a webinar, the 3000's vendor relations manager, its product planning manager, as well as its customer spokesman said they knew nothing about the 3000 leaving HP's fold.

The questions surfaced in an October, 2001 broadcast. On November 14, the company released public statements. I was briefed on Nov. 9, and vendors leaked their notifications during the first week of November.

If nobody on that October Webinar knew about ending the 3000 business line, HP was certainly keeping its decision held as closely as a riverboat gambler's hand. Or perhaps a certain German sergeant on TV was the template for the answers.

After a few minutes of questions about support for disk mirroring, boot drives greater than 4Gb and other chestnuts often asked, HP began to address a number of questions about the impact of the merger on the 3000 product line. Customers asked about a published report in Network World magazine, wondering if the system was likely to survive the merger.

“I sure wish I knew the answer to that,” said Kriss Rant, CSY’s manager in charge of developer relations and a division veteran. “I don’t know any more than you do.”

“Whenever there’s a large merger like this, the press has a field day,” host Stachnik added, “speculating on exactly what it’s going to mean. I can tell you that nobody in the 3000 business has received any marching orders from Compaq or upper HP management that OpenVMS, MPE or any other operating system is supposed to survive or not. There’s been no decisions made on that. Don’t give too much credence to it.”

Platform Planning Manager Dave Snow noted that HP did a “total roll of our product line in February, and we’re delivering multiple processor support. I certainly think you can expect there will be support of MPE for many years to come.”

Other questions on the merger got a broad brush answer from Stachnik. “The correct answer at this point is, ‘We really don’t know,’ ” he said. “There are lots of open questions about whether that merger is even going to happen. The SEC needs to look at it, and there’s been all sorts of speculation in the press.

"How it’s going to impact the 3000 — we simply don’t know at this point. We’ve gotten no marching orders one way or the other, and I’m not anticipating we’re getting them anytime in the near future.”


HP advises transition plan from 3000

Pointing outbound for jet
From November, 2001

Recommendation includes five-year support guarantee, two more years of new sales

Hewlett-Packard proposed a new chapter for its oldest business computer on November 14, one that advises customers to transition away from the HP e3000 over the next five years. The announcement from 3000 division general manager Winston Prather and marketing director Christine Martino included news of a confirmed date for end of HP support and a halt of new sales in a little less than two years’ time.

HP said it will stop selling new systems on Oct. 31, 2003, ending its distribution of more than three decades of the most reliable business computer in the HP lineup. The company’s contract with North American distributor Client Systems - a company doing business exclusively in the HP 3000 line - has been extended for two more years. The computers will clearly be in service for quite awhile after that date, however, as HP is promising full customer support for the systems through the end of 2006.

“This really is about concluding that it’s time to advise customers of the long-term trend,” said Prather. “It has nothing to do with cost savings or downsizing. This is an advisory type of announcement.”

HP briefed the NewsWire several days in advance of the worldwide announcement to the general press. The announcement included news that HP will provide free unlimited HP-UX licenses for all customers who own the new A-Class and N-Class servers, and transform those systems into equivalent HP 9000 computers. And in the meantime, HP intends to continue selling the system, and upgrading it with projects that have already been announced. It will present papers and communicate with customers at Interex conferences during 2002, and continue its Webcast series with a January broadcast on transition.

“From a CSY perspective and a support perspective, it’s business as usual for the next two years,” Martino said. “It’s time for customers start their planning to move to a platform that will serve their businesses better in the future. HP recommends that customers begin transitioning off the HP 3000 to alternate HP platforms.” HP will be releasing an overview White Paper in the first of a series, “HP e3000 Migration Considerations,” from its Web site. More detailed white papers on transitions to HP-UX will be released in the future.

There’s even a silver lining in the announcement for some HP 3000 customers. The end of support date for MPE/iX 6.0 has been extended by six months to October, 2002, making it easier for companies using the HP 3000 9x7 systems to remain on the platform. HP stops support of that hardware in April, but software support for the systems has been extended as part of the transition. Series 939 and 959 system support has been extended to December of 2003.

The company is also notifying all of its customers on current support contracts by letter. Prather said the division started to brief its top-tier customers on November 9. “They were not surprised, and they really appreciated HP being able to tell them what we see as the future role of the platform,” he said. “At the same time they really love the platform, so there was some sadness in transitioning from the platform.” Prather said these top-tier customers “already have a multi-OS strategy, so they’ve been evolving their applications over time. It is a stake in the ground, but the CIOs I talked to were appreciative of hearing what the future holds.”

No layoffs or downsizing in the CSY division is being planned, nor are any additional technical development operations going to be shifted away from the California 3000 labs. The product has often been pointed to as a profitable part of the HP lineup, but CSY officials said profits didn’t enter into the decision to stop selling the systems two years from now.

The end of the CSY division seemed even fuzzier, despite its announcement of a date for the end of support. “When we get to the point where HP doesn’t need a CSY organization to support the 3000 customers, then we wouldn’t have a division,” Prather said. “We will staff the division to make sure we have whatever resources we need to meet our commitments, and we are committed through December, 2006. We will ensure from both a CSY perspective as well as our support organization and field support we have the staff we need.”

HP will also be helping continue the transition after the end of the support period. “After that, [CSY] employees will transfer to other businesses to continue the transition as well,” Prather said. HP hopes to capture HP 3000 business in its NetServer and HP-UX platforms, but recognizes that competitors will be targeting the customer base. “We will need to earn their business,” Prather said.

HP’s plans on database migration were less specific at the announcement. Prather mentioned HP Eloquence, a revision of the HP IMAGE database that’s been running on HP 9000 servers for more than a year, as an option for companies migrating their home-grown systems. Other customers should look to their application providers, Prather said, for advice and support on how to transition away from the platform. Martino and Prather said a “decline in the ecosystem” surrounding the 3000 prompted the move - and denied that the impending HP-Compaq merger had any effect on the decision to write HP’s last chapter in the 3000 community. CSY made the decision sometime after the last HP World conference, according to Prather. The general manager, who has spent his entire career managing technical and business advances for the platform, said he was saddened by his decision.

“I’m sad, because I’ve been involved in this forever,” he said. “But I feel confident we’re doing the right thing for customers. I can stand up in front of any customer and explain why we’re doing this,” Prather said. “It’s a recognition in general that we’re not going to be able to reverse the trends.” Martino said sales have been declining for the product, although the month of October, HP’s close of its fiscal year, was a record one in North America. She added that the division’s staff has been “going through stages of grief” over the decision. But despite CSY’s melancholy approach to the news, the division remains well in place trying to sell new 3000s to the community over the next 24 months. The immediate future holds no changes for companies relying on the system, HP said.

“We picked these dates that we’ll guarantee availability for customers, and we don’t have any plans to review those dates. We knew that the next question customers would ask is, ‘How long will this be a safe environment?’ That’s why we gave them these dates.” As proof of the safety, HP plans to continue with all of its announced enhancements for the system except moving it to the IA-64 platform. The ongoing PA-8700 project, which is delivering a chip that is expected improve performance another 30 percent over current top ends, will be delivered as promised. HP will also release new A-Class systems during the next two years, offering a performance bump for those low-end servers as well.

HP will also be releasing MPE/iX 7.5 next year, although the future releases of the operating system will be limited to Express updates beyond that, according to Prather. Native Fiber Channel will still be released, along with support for the new Ultrium tape systems and va7400 disk arrays. Possibilities of selling the business to another company and helping to create an Open Source movement to extend MPE’s life still may hold some potential for Prather. “We have a very diverse set of customers,” he said, “and in briefing our top-tier accounts, this doesn’t come up. I don’t believe doing any of that [Open Source] will change any of our recommendations for customers. I feel strongly that the ecosystem is starting to erode, and that right thing to do is move to another platform, hopefully an HP platform.”

But “having said all that, we will try to understand how we can help the evolution of MPE. If it is valuable to customers, we want to understand how we can help them.” Selling the source code for the operating system, as HP once did for the earlier generation of MPE, is also a possibility, “but I want to understand to who, and for what purpose.”

In the meantime, HP expects that a lively market is about to emerge around migration consulting and tools for the platform. “I have a feeling the third-party community will spring to life quickly to develop tools to help with the migration. I think a number of the partners in the ecosystem will look at this as an opportunity. This could bring the ecosystem to life for the transition period.”


The HP 3000's Earliest History

By Bob Green

With HP announcing its latest sunset for the HP 3000 in 2007, I thought some of you might be feeling nostalgic for some history. The original 16-bit HP 3000 (later called “the Classic”) was released in 1972 and re-engineered into a 32-bit RISC processor in the 1980s.

Background (1964-1969)

The HP 2000 Time-Shared Basic System (1968) was HP’s first big success in computers. The 2000 line was based on the 2116 computer, basically a DEC PDP-8 stretched from 12 to 16 bits. HP inherited the design of the 2216 computer when it acquired Data Systems, Inc. in 1964 from Union Carbide. The 2000 supported 16 to 32 time-sharing users, writing or running BASIC programs.

This product was incredibly successful, especially in schools. The original 2000A system was created by two guys working in a corner: Mike Green, who went on to found Tandem much later, and Steve Porter, who also went on to found his own computer company. Heavy sales of the 2000 brought the computer division of HP its first positive cash flow, and with it the urge to “make a contribution.” The engineers and programmers in Cupertino said to themselves, “If we can produce a time-sharing system this good using a junky computer like the 2116, think what we could accomplish if we designed our own computer.”

Abortive First Try (1969-1970)

The project to design a new computer, code-named “Omega,” brought new people into the Cupertino Lab, people who had experience with bigger operating systems on Burroughs and on IBM computers. The Omega team came up with a 32-bit mainframe: It was stack-oriented, had 32-bit instructions, data and I/O paths, eight index registers, up to 4 megabytes of main memory, up to four CPUs sharing the same memory and bus, both code segmentation and data segmentation, and a high-level systems programming language instead of Assembler; it was capable of multiprogramming from the start, and had support for many programming languages (not just BASIC as on the 2000).

The Omega was designed to compete with big CPUs. But Omega looked too risky to management. HP would have had to borrow long-term funds to finance the lease of machines to compete directly with IBM. So it was cancelled. Some of the Omega architects left HP, but most stayed. “Several people who remained took to wearing black-velvet armbands, in mourning for the cancelled project,” according to Dave Packard in his 1995 book, The HP Way.

The 16-Bit Alpha (1970-71)

Most of the Omega team were re-assigned to the Alpha project. This was an existing R&D project to produce a new 16-bit computer design. The Omega engineers and programmers were encouraged to continue with their objectives, but to limit themselves to a 16-bit machine. Alpha was Omega squeezed into 16 bits: 128 KB of main memory (max), one index register, and Huffman coding to support the many address modes desired (P+- for constants, DB+ for global variables, Q- for parameters, Q+ for local variables, and S- for expression evaluation).

Same People, Smaller Hardware, Bigger Software

The original design objectives for the Omega Operating System were limited to multiprogrammed batch. The Omega designers put off time-sharing to a later release that would be supported by a front-end communications processor. The cancellation of Omega gave the software designers another year to think of features that should be included in the Alpha Operating System.

As a result, the software specifications for this much smaller machine were now much more ambitious that those for the bigger Omega. They proposed batch, time-sharing and real-time processing, all at the same time, all at first release, and all without a front-end processor.

The instruction set of the Alpha was designed by the systems programmers who were going to write the compilers and operating system for the machine. The prevailing “computer science” philosophy of the day was that if the machine architecture was close to the structure of the systems programming languages, it would be easier to produce efficient, reliable software for the machine and you wouldn’t need to use Assembler (that is, a high-level language would be just as efficient and the code would be much easier to maintain).

The Alpha was a radical machine and it generated infectious enthusiasm. It had virtual memory, recursion, SPL instead of Assembler, friendly MPE with consistent batch and online capabilities instead of OS-360 with its obscure command syntax, variable-length segments instead of inflexible pages, and stacks instead of registers. The Alpha was announced as the HP 3000 with a fancy cabinet of pizza-oven doors, available in four colors. Prospective users were assured that it would support 64 users in 128 KB of memory.

Harsh Realities (1972-73): 200 Pounds of Armor on a 90-Pound Knight

I worked at Cupertino at the time and was assigned to coordinate the production of the ERS (External Reference Specifications) for the new software. I was as excited as everyone else. The first inkling I had that the HP 3000 was in trouble came in an MPE design meeting to review the system tables needed in main memory. Each of the ten project members described his part of MPE and his tables: code segment table, data segment table, file control blocks, etc. Some tables were memory-resident and some were swappable. When the total memory-resident requirements were calculated, they totaled more than the 128 KB maximum size of the machine.

MPE wouldn’t fit, so everyone squeezed: The programmers squeezed in 18-hour days, seven days a week trying to get MPE to work. Managers were telling their bosses that there was no problem, they just hadn’t had a chance to “optimize” MPE yet. When they did, the managers maintained, it would all turn out as originally promised. So marketing went on selling the machines to the many existing happy users of the HP 2000. As the scheduled date for the first shipment approached, the Cupertino factory was festooned with banners proclaiming “November Is a Happening.”

The first HP 3000 was shipped November 1, 1972 to Lawrence Livermore Hall of Science in Berkeley, California. But it was incomplete: It had no spooling, no real-time, etc. It supported only two users, and it crashed every 10 to 20 minutes. Customers who had been promised 64 terminals and who were used to the traditional HP reliability became increasingly frustrated and angry.

Eventually the differences between the HP 3000 reality and the HP 3000 fantasy became so large and well-known that there was even a news item in Computerworld  about it — the first bad press ever for HP. Bill and Dave were not amused. The product was withdrawn from the market for a short time.

Struggling to Restore Lost Credibility (1973-74)

Hewlett-Packard had no experience with bad publicity from low-quality products. Paul Ely was brought in from the successful Microwave Division to straighten out the computer group. The first priority was to help out the existing HP 3000 users, the ones who had trusted HP and placed early orders. Many of them received free 2000 systems to tide them over until the 3000 was improved. The second priority was to focus the programmers’ energy on fixing the reliability of MPE.

Once the HP managers realized the magnitude of the 3000 disaster, the division was in for lean times. Budgets and staffs that had swollen to handle vast projected sales were cut to the bone. Training, where I worked, was cut from 70 people to fewer than 20 in one day. HP adopted a firm “no futures” policy in answering customer questions (a policy that lasted for years after the HP 3000 trauma, but was forgotten by the time of the Spectrum-RISC project). The new division manager was strictly no nonsense. Many people had gotten in the habit of taking their coffee breaks in the final-assembly area, and kibitzing with the teams testing the new 3000s. Ely banned coffee cups from the factory floor and instituted rigorous management controls over the prima donnas of the computer group.

By continuing to work long weeks, the programmers managed to reduce MPE crashes from 48 a day to two, and to increase users from two to eight. Marketing finally took a look at what the 3000 could actually do, and found a market for it as a replacement for the IBM 1130. They sold the 3000 as a machine with more software capability than an IBM 1130 that could be available to a number of users at once instead of just one. Eventually the 3000 became a stable, useful product. To my mind, this happened when someone discovered the “24-day time bomb” bug. If you kept your HP 3000 running continuously for 24 days (2^31 milliseconds) without a shutdown or a crash, the internal clock register would overflow and the system would suddenly be set back by 25 days!

The Comeback: Fulfilling the Promise (1975-76)

The original 3000 had a minimum usable memory size of 96 KB and a maximum of 128 KB — not much of an expansion. The Series II went beyond that 16-bit limitation by adding “bank” registers for each of the key pointers (that is, code segment, data segment, and so on). Thus the Series II could support up to 512 KB, a much more reasonable configuration for the software power of MPE.

The choice of SPL as the HP 3000 machine language instead of Assembler truly began to pay off now in an avalanche of excellent software: The IMAGE database (again, two guys working in a corner: Jon Bale and Fred White) was soon joined by compilers for COBOL and RPG, a screen handler, and other tools to support transaction processing.

Concurrent, consistent batch and time-sharing was now a reality and the goal of concurrent real-time was finally dropped as unrealistic. The HP 3000 hardware now matched the software written for it. Business users discovered that the 3000 was great for online transaction processing; they dragged Hewlett-Packard firmly into the commercial information processing world.

At last, with the Series 64 in 1982, the 3000 reached the original target of 64 users on a single machine.

P.S. For another interesting history of the HP 3000, read HP’s Early Computers, Part Three: The Strongest Castle: The Rise, Fall and Rise of the HP 3000 by Chris Edlar


The Spectrum Project, Part I

By Bob Green

Commemorating the Oct 31, 2003 “wake” for the HP 3000, Robelle are devoting our NewsWire column to some history. Our story of the original 16-bit HP 3000 (1972-1976) is told on our Web site.

After initial development, the HP 3000 grew and prospered. From 1974 to 1984, HP continued to produce more powerful 3000 hardware running more capable software. Each new model was compatible with the previous version and a joy to install.

But the pressure was on to switch to a 32-bit architecture, as other manufacturers were doing. So HP announced a radical change: a new 32-bit hardware for the 3000. The project was code-named Spectrum. As a 3000 consumer and 3000 vendor, Robelle was excited and concerned about the prospect of a new hardware architecture. Certainly it would be wonderful to have more powerful processors, but what about the disruption to our steady incremental, risk-less progress?

The first notice we took of the Spectrum appeared in our December 1984 customer newsletter, with continuing news to follow for the next four years (my retrospective comments are included as “In Retrospect”).

December 12, 1984

The first Spectrum machine will be an upgrade for the Series 68. Other size models will follow soon after, since HP is working on different Spectrum CPUs in three divisions at once (in the past, all 3000 CPUs came out of one division). This first Spectrum can be expected in the first half of 1986.

In Retrospect: Please make a note of that 1986 promised delivery date, and remember that HP faced serious competition from DEC and others. Customers who loved the 3000, but had outgrown the power of the system, were demanding more capable models.

Spectrum is based on the RISC concept, modified by HP Labs. RISC stands for Reduced Instruction Set Computing. Such a computer has no micro code, only a small number of key instructions implemented in very fast logic. The original Berkeley RISC machine had only 16 instructions. Spectrum has more than 16, but not many more. HP selected the instructions for the fast base set by studying typical application mixes on the existing HP machines. Other functions will be done via subroutines or co-processors (e.g., a floating-point processor, an array processor, or a database processor).

In Retrospect: The actual number of instructions in the Spectrum turned out to be about 130, not 16, but they were all simple enough to run in a single clock cycle. HP was the first computer company to go with the RISC philosophy and the only major one to risk the firm by converting all their computer models, both technical and commercial, to a single RISC design.

June 11, 1985

HP’s new Spectrum machine will have both Native-Mode software and 3000 software. The first Spectrum machine to be released will have 3-10 times more computing power than a 68, about 8-10 MIPS in Native Mode. Programs copied straight across will run about twice as fast as on a 68, and those that can be recompiled in Native Mode should run 6-8 times faster. Much of MPE, including the disk portion of the file system, has been recoded in Native Mode. Since most programs spend most of their time within MPE, even programs running in emulation mode should show good performance (unless they are compute-bound).

In Retrospect: The expectations were building in our minds: these machines would be much faster than our current models!

Spectrum will use much of the new operating system software that had been written for Vision, which saves a great deal of development time. Spectrum will use 32-bit data paths and will have a 64-bit address space. Forty Spectrum machines have been built and delivered for internal programming, but product announcement is not likely before 1986.

In Retrospect: Vision was an alternative 32-bit computer project at HP, using traditional technology, which was cancelled to make way for the RISC design from HP Labs. Invoking Vision re-assured us that this project is possible, that progress is being made. It was now six months after the first announcement of the project.

August 16, 1985

According to an HP Roundtable reported in the MARUG newsletter, “Most of what is printed about Spectrum is not to be trusted. Spectrum will be introduced at the end of 1985 and delivered in Spring 1986. There are 40-50 prototypes running in the lab and the project team consists of 700-800 engineers. HP will co-introduce a commercial version and a technical version with the commercial version fine-tuned to handle many interactive users, transaction processing, IMAGE access, and the technical version will be structured for computational programs, engineering applications, and factory automation. HP will eventually offer a choice of MPE and Unix. Most software will be available on Spectrum at introduction time and over time all software will be available.”

In Retrospect: HP tried to dispel rumors, but still predicted 1986 for delivery. HP would produce two Spectrum lines: the Unix line for technical users and the MPE line for commercial users, using the exact same hardware.

“The following describes what will be required to convert – Least: restore files and IMAGE databases as they are and run. Next: recompile programs in native mode. Next: change over to new IMAGE database system. Next: change source code to take advantage of RISC.” Robelle Prediction: Spring 1986 for a Spectrum that will reliably run existing MPE applications is not an attainable release date.

In Retrospect: The new relational HPIMAGE database mentioned here was cancelled much later in the project, after a brief encounter with end-users. I don’t remember much about HPIMAGE, except that a lot of work went into it and it didn’t succeed as hoped. TurboIMAGE ended up as the database of choice on the Spectrum. Without any inside information, but based just on past experience and common sense, Robelle tried to inject some caution about the 1986 release date. During the original traumatic HP 3000 project, Dave Packard “sent a memo to the HP 3000 team,” according to Chris Edler. “It was only two lines long and said, essentially, that they would never again announce a product that did not then currently meet specifications.” The division listened for over 10 years, but eventually, people forget….

September 20, 1985

From a Spring 1985 UK conference: Most existing peripherals will be supported and it will be possible to use networking software to link existing model HP 3000s to Spectrum, with the exception of Series II/III and 30/33. These would need a Series 37 or other current range machine to act as a gateway to Spectrum.

From an HP press release: “100 prototype models were already being used internally for system development as of April 1985.”
HPE, the new operating system for the commercial Spectrum is a superset of MPE. It will have two modes of operation: Execute mode (HP 3000) and Native Mode. The switch between the two will be made on a procedure call, but there will be some programming work needed to translate parameters when switching.

In Retrospect: Execute mode was eventually called Compatibility Mode and switching between modes turned out to be major CPU bottleneck in the new system, albeit one that would be removed over time.

The Spectrum is rumored at this time to provide 32 general-purpose registers to the user program and a virtual data space of 2 billion bytes.

December 30, 1985

From Gerry Wade of HP: The name of the Spectrum machine, when it comes out, will not be Spectrum. Another company already has that name. Spectrum will use the IEEE standard for floating-point arithmetic and will also support the HP 3000 floating point. Each data file will have a flag attached to it that tells which type of floating-point data it contains (the formats are not the same).

In Retrospect: The file flag idea never happened, although the TurboIMAGE database did introduce a new data type to distinguish IEEE floating point. Information on implementation details is starting to flow, which helps us believe that the project is on schedule and likely to deliver the more powerful servers we desire.

June 16, 1986

In reporting on Joel Birnbaum’s Spectrum presentation, the HP Chronicle had these observations: “Comparisons with Amdahl and DEC mainframes in slides showed areas where the Spectrum computers topped the larger machines’ benchmarks. ‘Even with un-tuned operating systems software, it’s significantly superior to the VAX 8600,’ Birnbaum said.”

In Retrospect: Joel was the HP Labs leader who was the sparkplug of the RISC project, building on research that he had done previously at IBM. In retrospect, we can see that Joel was talking about the performance and delivery of the UNIX Spectrum, not the MPE version, but customers took this as a promise of vast performance improvements in the very near future. It was now past Spring 1986 and the promised new 3000 machines were nowhere in sight. In fact, HP has not yet announced the new models and pricing. This was the first slippage in the project, barely noticed at the time.

July 20, 1986

Many people have been asking, “What is Robelle doing about Spectrum?” HP has invited us to join its Fast Start program for third parties and we have agreed. This program gives us pre-release access to Spectrum information and actual systems. We have visited Cupertino and run our software on the new machines. We are confident that all of our products will operate properly at the time that Spectrum is officially released.”

In Retrospect: Since Suprtool and Qedit were essential to the large 3000 customers that HP was targeting, HP asked Robelle to start porting and testing our products on the new systems. But to do that, we had to sign a Non-Disclosure Agreement, the most draconian one we had ever seen. We used careful wording in our announcement above. From this date on, until years later, we could not tell our customers anything useful about the new machines. HP was especially sensitive about their reliability and performance.

When we arrived in Cupertino to do our first testing, we found the prototype Spectrum systems crashing every few minutes and running slower than our tiny system 37. We were appalled. Nothing in HP’s public statements had prepared us for the state of the project. I had personally gone through a similar situation with the original 3000 in 1972-74, and I wondered if upper management at HP knew how terrible things were. I thought about talking to them, but our NDA also prohibited us from talking to anyone at HP.

The Unix versions of Spectrum, on the other hand, seemed to be humming along nicely, showing that it was not a hardware problem.


The Spectrum Project, Part II

By Bob Green

Last month I presented the first half of our history of the PA-RISC 3000 development, using excerpts from our old customer newsletters, supplemented with new comments (My comments are shown below prefaced by “In Retrospect”). By 1986 we reached the point where Robelle was allowed to experiment with a prototype MPE system at the migration center and were aghast at how slow and unreliable it was. And since the Unix versions of Spectrum seemed to be humming along nicely, the problem seemed to be software, not hardware.

September 11, 1987 Newsletter:

First Spectrum Shipments: Rumor has it that HP shipped the first four 930 machines on Friday, August 21st, with more to follow every week thereafter. As of press time, we have been unable to find out whether ordinary mortals are allowed to touch these machines (as opposed to those who have signed non-disclosure agreements).

In Retrospect: Due to the NDA, over a year passed with no Spectrum news in our newsletter. The project was now 18 months past the original promised delivery date, but was still far from completion. Many people wrote articles, about the Spectrum, mostly based on marketing hype from HP, but no one broke the embargo on real information. We were all terrified. The MPE group had dug themselves into a very deep hole, and no one wanted to be the one who caught the eventual backlash.

October 19, 1987 Newsletter: The Spectrum Song

Orly Larson and his database singers performed again at the Interex show, including their hit, “The Spectrum Song:”

If it takes forever, we will wait for you
For a thousand summers, we will wait for you
‘Til you’re truly ready, ‘til we’re using you
‘Til we see you here, out in our shops!

From the HP Management Roundtable: Schedule for Shipping Spectrums — “We are shipping equally around the world. Our first shipments went to both North America and Europe. We are acknowledging availability for 930s and 950s through December at this time … We expect by the end of November to be able to have acknowledged the entire backlog.”

In Retrospect: HP continued to spin the “shipments” of Spectrums, without mentioning that these were not finished products. The models were 930 and 950 and the operating system was called MPE/XL, changed in later years to MPE/iX when POSIX was integrated into MPE. By this time, HP was worried about their stock price also and did not want any negative news in the financial press, no matter how accurate. As shown by the next Q&A at the roundtable…

Early 930/950 “Shipments”

Question: “Are the 930s and 950s being shipped or not? In public you tell me they are shipped. In private, however, I hear from both users and HP that these machines are still covered by non-disclosure agreements and that access to these machines is very restricted, even when in customer sites. What is the story?”

Answer: “MPE/XL architecture is very, very new. There’s a million new lines [of code] that go into MPE/XL, and a lot of software sub-systems as well. And so we are being extremely cautious in how we proceed at this point. We’re going through what we call a slow ramp-up through the remainder of this year and going into large shipments in 1988. The reason for that is that we want to fully test out the system capability in a large number of customer environments and we want to make sure that the information on what’s going on in there and the people involved are protected from outside folks who either benevolently or not benevolently would like to find out what’s going on.

I’m sure we’re going to run into some problems along the way that haven’t been encountered in our earlier phases of testing. We haven’t really hit these machines with full production pressure yet. We know from experience that when you do that, you uncover things that you could never uncover in testing, even though extremely rigorous. [Rumor has it that the customers receiving Spectrums now are not allowed to put them into production until 1988.]”

In Retrospect: Early Spectrum customers called us to ask which version of Suprtool and Qedit they needed for their new systems, and whether there were any problems that they should be aware of. But legally, we could not even admit that we knew of the existence of the new servers. So we came up with the following wording: “If you had a new 3000, and we are not admitting that we know anything about a new 3000, you should be using Suprtool version 3.0 and Qedit version 3.6. On this hypothetical system, it might not be a good idea to hit Control-Y while copying a file from any other HP 3000. We can’t tell you what will happen, but you won’t like it.”

February 12, 1988 Newsletter

Spectrum Finally Leaves the Nest: Hewlett-Packard has officially released the 930 and 950 Spectrum computers, finally abandoning the protection of non-disclosure agreements. We have heard from several sources that the 930 and 950 attained Manufacturing Release during the month of January. This means that people who received “Control Shipment” Spectrums can now put them into production and let outsiders use them. You no longer need to sign any restrictive agreements to get a 930/950. It also means that we users can now compare notes on what the MPE/XL systems are good for.

Interestingly, we didn’t hear about the Manufacturing Release (MR) of the Spectrum from Hewlett-Packard itself. As far as we can determine, HP kept this event very quiet — no press conferences or splashes of publicity. Even some HP people in Cupertino were not aware that MR had occurred. Just because the 930 and 950 are released does not automatically guarantee that you can get one. Given the huge backlog of orders that HP has, it will make “controlled shipments” for a while, picking sites whose expectations match the state of the machines.

In Retrospect: Users had been following Spectrum for almost four years and you could see that we were eager for the release of the product. The MPE lab had grown to hundreds of engineers and technicians and hundreds of Spectrum servers. The amount of money being plowed into the project was awesome. Anyone with any kind of skills was being hired as a consultant, in an attempt to get the situation under control and begin shipping revenue-generating servers. But we were premature in our February proclamation of Manufacturing Release, an HP corporate milestone that requires signed confirmation that the product passes the performance tests set for it in the design specifications.

March 31, 1988 Newsletter

Spectrum Is Released but Not Released: In our last news memo, we reported that MPE/XL users were now removed from non-disclosure restrictions and allowed to put their Spectrum machines into production. In the last month, that news has been confirmed by many sources.

We also concluded, and reported, that MPE/XL had obtained MR (Manufacturing Release). That is untrue. MPE/XL has apparently obtained SR (System Release), but not MR. “System Release” seems to be a new category of release, created just for MPE/XL. We have heard from some new 950 customers who did not need to sign a non-disclosure agreement. However, one customer reported that before HP would allow him to order, he had to sign a document stating that he had no specific performance expectations. On the other hand, we heard from a school that recently went live with 35 student sessions and had great response times (“the machine is coasting along at 10 percent PCU utilization”).

In Retrospect: In order to stem the rising tide of bad expectations, HP released the MPE systems even though they could not pass the testing department. And the performance was still poor in many cases, less than the non-RISC 3000s being replaced, although excellent in a few other cases.

Non-disclosure restrictions are not lifted for everyone. Sites that are beta-testing subsystems which were not released with the initial MPE/XL system are still restricted. Also, third-party FastStart companies such as ourselves are still restricted from passing on any performance or reliability information that we obtain from HP. We face no restrictions regarding performance information received from our customers, so please call with your experiences.

Non-disclosure continues – HP is picking their initial customers carefully and coaching them to only pass on the good news about their new systems. We are still frustrated to not be able to pass on our ideas about how users can improve the performance of the Spectrum.

October 12, 1988 Newsletter

Gary Porto at Childcraft reports that with MPE/XL 1.1 the problem of a serial task in a batch job hogging the system is not so bad as it was with 1.0. This problem can occur with SUPRTOOL, QUERY, or any long serial task. The batch job still hogs the system, but at least people can get a minimum of work done. With 1.0, they couldn’t even get a colon! Gary reports that he has 65 on-line users on his 64-megabyte Series 950 and that the performance is pretty good — as good as his Series 70.

In Retrospect: On the 4 year anniversary of the project, HP released version 1.1 of MPE/XL, which made the systems much more useful, but still not up to the original promised performance of 1984. However, the promise of the “Precision Architecture” (HPPA) was there, as certain tasks were amazingly fast.

By this time, HP salesmen were getting irritated with us for not giving our customers any kind of endorsement for the switch to the 930/950. But our NDA was not cancelled until Manufacturing Release. Finally, the sales force convinced HP Cupertino to send us a signed release from our NDA. I don’t know when MR eventually happened.

From the UK’s HP World magazine: Early MPE/XL Migration Results. London Business School is not a typical installation. Much of their software is written using double precision floating point Fortran which benefits considerably from the Precision Architecture. MIS Director Gordon Miller says “Our straight line performance is up considerably — one program runs 40 times faster — but the performance gains are very application dependent and cannot be accurately forecast beforehand.”

Keith Howard of Collier-Jackson in Tampa, Florida participated in the Spectrum beta testing and upgraded from a Series 58 to a Series 950 — quite a leap. One application was found to be 6% slower due to constant switching between compatibility and native modes, but in most circumstances the machine was five to ten times faster than the Series 52 and one batch job ran 53 times faster!

Glaxo Export has temporarily deferred delivery on its second and third 950 systems due to implementation problems on the initial machine.

HP promises performance improvement for Precision Architecture over the next five years of 40-50 percent per year. Some of this will be achieved by further tuning of MPE/XL — version 1.1 is said to be at least 20 percent faster overall.

In Retrospect: As with the original 3000 project, the birth of the Spectrum was traumatic, expensive and embarrassing. But it paid off. HP was able to roll out better servers for the 3000 line on a regular basis for the next 10 years.

Despite the numerous expansions and revisions to the HP 3000 hardware and software, upgrades have been painless. Even the conversion to the PA-RISC design was backward-compatible and reasonably painless (if you ignore the slipped schedules). Often the user just rolled the new system in on a Sunday, plugged it into the power, reloaded the files, and resumed production. The original 1974 MPE Pocket Reference Card is still useful; everything on it works under MPE/iX version 7.5, except the Cold Load instructions. I have programs that I wrote in 1972, for which the source code was lost years ago, and they still run in Compatibility Mode.

When asked for an eulogy for the 3000, my reply was, “A great IT platform: reliable, affordable, flexible, easy to operate, and easy to program. And every release compatible with the previous for over 30 years. Perhaps some future OS team will adopt these same goals.”


Carly's exit sparked new hopes for 3000

Newswire Classic

March 2005

After board demands CEO’s resignation, 3000 sites ponder new future

The CEO who hawked change as HP’s new mission — and so sparked the 3000’s exit from the company’s lineup — has left HP in a resignation that made some customers hope for a change in HP to alter the 3000’s fate.

But HP’s board of directors, after demanding Carly Fiorina’s resignation on Feb. 9, have shown no signs of changing the company’s commodity and consumer-driven strategy, one which hurried the 3000’s HP exit.

Interim CEO Bob Wayman told stock analysts the next CEO will need to march to the tune Fiorina composed during the five-plus years she headed the company.

The company won’t change because its board hasn’t changed much. Venture capitalist Thomas Perkins came on board in early February, but the list of directors includes a group of officers who have approved Fiorina’s plans to grow HP. The board said it removed its CEO and chairman because she did not execute HP’s strategy well enough. The company’s earnings growth has disappointed analysts in recent quarters.

Wayman said during an analyst briefing that the board is looking for a CEO to work with the current strategy: Offering a broad portfolio of products while operating a printer business integrated with the rest of HP.

“While they won’t preclude any open discussion on a new CEO’s view of what the future strategy should be,” Wayman said, “we are looking for a CEO who also embraces that strategy, in all probability.”

Fiorina, who earned $44 million in signing bonuses to join HP in 1999, left the company with a $21.1 million payout. Her contract also provides $50,000 in job counseling services, a point of irony that didn’t escape HP 3000 customers who have seen careers ended or altered after the 3000’s cancellation.

“She was the executioner,” said John Dunlop of 3000links.com “She chopped and pruned product lines and employees. Unfortunately for the HP 3000 community, the HP 3000 was one of the early casualties. Thus she became the name synonymous with the death of the HP 3000.”

Another customer said Fiorina represented a strategy of judging a customer by what they’ve bought lately. The 3000 customer has been expected to buy what HP produces after it said it won’t offer the HP 3000.

“Carly was viewed by many to be of the mindset that our value as customers was limited to our wanting to buy what HP had to sell,” said Russ Smith of credit union Cal State 9. “It was not that our value was inherent as customers, period — and that HP should produce what we need.”

The majority of customers were realistic about how much change would filter down to the HP 3000 issues that remain at the company. “HP now has bigger problems such that this issue won’t even be on the radar,” said John Wolff, the CIO at LAACO, Ltd and vice-chair of OpenMPE. “Not only did they break the HP 3000 product line, but Carly broke the whole company — 60 years to build it, six years to wreck it.”

Fiorina was the first CEO ousted from HP in such a public manner: Stories of the forced resignation aired on all major US TV networks; HP called a press conference to explain on the day it removed Fiorina. She was not the first to leave involuntarily, though. Another HP CEO, John Young, “was politely retired when Dave Packard came back out of retirement to put the company back onto the right path in October, 1992,” Wolff said. “Young was paid $1 million for ‘unused vacation time.’”

An enterprise change?

Some 3000 customers said they were hopeful a better enterprise server strategy would emerge under a new CEO. The majority of customers responding to a spot poll by the NewsWire reported they were migrating away from the server, a position that has them considering HP’s server alternatives. For many, the damage has already been done.

“We lost all faith in HP’s strategy some time ago,” said Don Baird, president of EnCore Systems. “We do not rely on anything HP except our 3000s, which we are replacing with non-HP solutions.”

HP’s change of heart is having an impact on a choice of vendor for migration sources. At the Anchorage, Alaska light and power utility, systems analyst Wayne Johnson is moving to Windows — but HP’s moves with the 3000 make the utility wary.

“Part of my company’s fear has been the HP 3000 is going away, so let’s steer clear of any other HP product,” he said. “Could the change mean that the HP 3000 will be resurrected and not meet its demise in 2006? Our Windows platform is not HP.”

Some drew a direct link to Fiorina’s strategy and the slide of HP’s enterprise business. “HP lost its personality under Carly. Their niche was solid, reliable computing platforms, not PCs and not iPods,” said John Lee of reseller Vaske Computer Solutions. “Hopefully, the new CEO will re-focus the company on its core strengths, one of which used to be enterprise computing.”

Even those moving to HP’s Unix systems want to believe more change in management is on the way. “I really hope the shakeup continues down the line,” said a long-term HP 3000 manager who wanted his name withheld. At his firm, HP 9000s are replacing HP 3000s. “Maybe we can get back to a point were the customer and our needs come first, and the profits and sales will follow,” he said. “Since the Compaq-HP merger, the quality of our service programs and sales support have dropped.”

The CEO’s departure won’t change much for Pivital Solutions, a company that signed on for the last year of HP’s authorized 3000 sales and now offers third-party support for the server and MPE. “The only hope I still loosely hold is that they will sell off the enterprise systems group before they run it into the ground,” said president Steve Suraci.

Operator seeks operations whiz

HP’s executives say the company now needs a CEO with better operational skills. Its top sales officer Mike Winkler, quoted in a published report from the recent Goldman Sachs Technology Investment Forum, said HP’s fortunes would rise with a CEO like Lou Gerstner, the IBM leader who came in to turn around that company in 1992. In that same year, HP’s founders Bill Hewlett and Dave Packard asked LaserJet czar Dick Hackborn to take the CEO reins from John Young. Hackborn wouldn’t leave his home in Boise, Idaho to take the job and retired a year later.

But Hackborn, an operator behind the scenes in most of HP’s business choices since his retirement, played the lead role in bringing Fiorina to HP after the company felt it missed out on the Internet boom during CEO Lew Platt’s watch. Another report, published in the wake of the Fiorina ouster by BusinessWeek editor Peter Burrows, says Hackborn acted as the catalyst to spark the board’s removal of Fiorina.

Now Hackborn and the rest of the HP board will try to find an operational, COO style of CEO. HP will change CEOs because of Fiorina’s inability to execute, not over her direction. “She had a strategic vision and put in place a plan that has given HP the capabilities to compete and win,” HP’s press release assured investors.

The strategy which Hackborn has pulled HP into — commodity sales like printers, with less direct customer contact — relies on resellers and outside distributors to stay in touch with all but the largest customers. Typical HP 3000 shops, working for small and medium-sized businesses, say they have not felt much contact with any HP operation except its support group.

“Working for a small company, I don’t feel that I or my company has ever been part of an ‘enterprise systems strategy,’” said John Bawden of health insurance provider QualChoice, an HP 3000 shop. “Generally we are ignored unless we have the energy and the need to go to HP for something.”

Continue reading "Carly's exit sparked new hopes for 3000" »


HP Enterprise reclaims 3000 manual library

HPE Documentation interface for support

HP 3000 and MPE/iX manuals might be found anywhere these days. It's a common request to hear from a 3000 pro, "Where can I find that manual?

HP is back in this business with a new interface. These webpages at HPE's website are a high-value address to locate documentation and make it available to a new 3000 administrator. Or a migration team trying to understand how something like TurboStore/iX works.

There's no guarantee of how long HP Enterprise will keep this library open. Get it while you can.


Damages and desires got stamped from HP's decision

EFORMz flyer

Paper, printed with barcodes or mailed, still plays a role.

Nineteen years ago, Hewlett-Packard rocked the 3000 world with a fateful announcement. "No more new 3000s," the creator of the system said. "December of 2006 marks the end of HP's MPE road. Your ecosystem has been shrinking for some time." And so on.

How bad was that decision, really, in the long view from 2020? It killed companies, cratered careers, made vendors vanish. The world's landfills and scrapyards gathered tons of aging 3000 iron, over the next decade and beyond. What good came of it might be measured in how companies and experts rebuilt their prospects and skill levels.

Not many injured parties fell immediately from a mortal wound. Like COVID, though, the news attacked those whose careers or business models were already vulnerable. I was tempted, in the years that followed, to compare the HP choice as another kind of 9/11. I didn't go there, and I won't try to equate that business decision with a pandemic that's killed close to 1.5 million people worldwide.

The pain of a loss, though, isn't so easily defined. For some people and companies, November 14 was the wildfire that cleared out the old forest floor to make way for new trees. Minisoft was roaring along with its terminal emulator and middleware business. Its founder Doug Greenup summed up the firestorm and the aftermath eloquently.

"At first our business was not really affected," he says. "In fact, our sales actually trended up slightly with upgrades. We were faced with a critical decision to either let our company fade slowly away with the declining MPE business, or reinvent ourselves. I remember that 90 percent of our total business at the time was MPE."

"We decided to take Minisoft in a radical new direction going back to our old word processing days. We originally produced a product called Miniword which competed with HPWord and TDP on the HP 3000. Based on our long lost past, we created a document management suite written in Java that was operating system agnostic. We then marketed this software suite into several new non-HP worlds: QAD, RedPrairie, Manhattan, STW, and Microsoft Dynamics."

"It was very difficult to reinvent, and it took several difficult years," Greenup wrote to us on the 10-year anniversary of the announcement. "HP's decision almost killed our company. But we survived and are stronger as a result."

A few weeks ago, Minisoft dropped a marketing flyer, full color and tri-folded, into my mailbox at the curb. The flyer updated me on eFORMz, its solution for printed forms. It emerged in the years after 2001. Minisoft says, "The world's great brands run on eFORMZ" with a list: Petco, Tiffany, Office Depot, Adidas, Victoria's Secret, Mrs. Fields. The lineup reminded me of the Who's Who list that Ecometry boasted during the year of that 2001 HP announcement. Known brands, the Ecometry sites, all using the HP 3000.

eFORMz doesn't require a 3000. If a company has one, the software integrates effortlessly. The non-HP worlds began to open up as opportunities for Minisoft after Nov. 14. The fact that a printed flyer could promote software in 2020 is a tip of the cap to the continuing power of paper. When the HP news of 2001 arrived at the NewsWire, we were as deeply invested in paper as a little business could be.

Like Minisoft, paper lined my path away from the loss. Books, to be specific, paper that's more durable than periodicals.

I think of books as the HP 3000 of communication. Steady, knowing, rich with data that becomes knowledge and then wisdom. I had to write my way out of the trouble. The Web, as we called it in 2001, became the bridge.

It's been 19 years since HP canceled its future for the 3000 and changed ours. Our lives stopped building on the success of periodical editing and publishing. We still did our 3000 storytelling, of course, and I keep doing it. But every Friday now, for six of them in a row, I write a little newsletter about writing and editing, instead of coding or managing an enterprise system. In the work of becoming a book editor, and the author of a novel and a memoir, I’m not a reporter any longer, not about the book work. I’m an author, as well as an editor and evaluator of other authors.

And Abby? Whoa — a yoga teacher who's produced three DVDs and is now in her 15th year of leading classes. Now people can attend her classes over Zoom. Students come from around the country, where they once had to show up at our address, or live in Austin for private sessions. People who don't think they might do yoga can practice Heavyweight Yoga. Thirteen retreats, too. A Fitness Magazine Fit 50 member, alongside notables like TV anchor Robin Roberts. Obesity Action Coalition's Bias Buster of the Year.

Could I see the way to this day if HP hadn’t ever stopped its 3000 business? Would our tribe instead be like the OpenVMS people who still have vendors and customers, but the latter isn’t spending much anymore, and so the former doesn't have money for ads? That all began in 2013 for VMS, when HP announced the end of its unlimited service to the Digital community. My new cattle drive toward books would’ve started 12 years later than it did. I’d have been 56, just beginning my journey. In that future, we might've had more in our retirement account. Or, we might have looted it for experiences, as we did through the years. What trip, Abby always asks, would you have not gone on?

I can think of a few, but they all promised to be delightful in the cozy run-up to each experience. Were there some lemon meringue pie slices we could have left in the San Antonio Tip Top diner’s cold case? To be sure, there were. How could we know which ones we didn’t need as comfort food for the soul, though?

There are, of course, other ways to measure how things worked out because HP lost its faith. We bet on a business that we didn’t think would last so long. You would've had to ask us on a really honest day in 1996, say, to hear me say this venture had about five good years in it. The unfettered, blue-sky time amounted to six years or so. The next 19 after 2001 have had some seasons better than others. You won't mistake technical publishing for the creative compensations of books and yoga. The satisfactions, though, are a different element to measure.

Many an MPE expert made this kind of transformation. John Burke became a mathematics professor. Some just branched out further, like Birket Foster and his Storm rural internet service company. He's still serving 3000 sites with data migration, too. Fresche Solutions waded into the IBM i Series market and held on to its 3000 work that'd begun while the company was called Speedware.

It’s an alternative history game, this one. However, it’s also a commemoration report. What did we do for Christmas in 2001, versus Christmas of 2000? I always mark what we are spending with the high water mark of the holidays. That was a time that always included the Dec. 31 birthday of my boy, the rock star who was proof I could create something warm and attractive and funny and smart. Amid my obvious failures, Nick is my durable success. And my marriage to a partner both special and true.

We got the Nov. 14 news a few days ahead of the vast majority of our customers. Some of the bigger vendors knew about it days or weeks ahead of us. I've written about hearing about the 3000's end of HP days while holding a payphone receiver with a cord on it. Fitting, considering how classic the 3000 was then and remains today. Wherever Nick and I were headed in Switzerland that night, we kept our appointment. A train station with a payphone on the platform led me to this New Tomorrow. We're all headed there by now because of COVID. Survival is going to be the outcome for so many of us, just as it was after 2001. 


HP pays $1.45 million to settle female pay charges

Hundred dollar bills
Served from a deep cup of irony comes the report that HP, both Enterprise and PC-printer arms, will be paying $1.45 million in a penalty for illegal treatment of its female employees.

The US Department of Labor levied the fine, which will cover back pay for 391 California women who suffered "systematic pay discrimination" while employed at HP.

The irony bubbles up because HP's two longest-serving CEOs this decade were Carly Fiorina and Meg Whitman. The fine includes interest, to be paid to the affected female workers.

Under the settlement, in addition to the settlement payment, the two arms of HP agreed to analyze compensation and take steps to ensure their employment practices follow US law. That accounting will include record-keeping and internal auditing, all to ensure HP's compensation practices are legal.

A Labor Department news release says HP has cooperated. But the arm that sells servers that replaced HP 3000s, Enterprise, says it disagrees with the allegations.

HPE has "settled in the interest of putting this matter behind us.” This enterprise HP, whose HQ address is now San Jose rather than Palo Alto, says it is “committed to unconditional inclusion, including pay equity regardless of gender, race, or sexual orientation.”

The other HP, headquartered in Palo Alto, says "the charges in this case are without merit. We felt it was in the best interests of all involved to resolve this matter as quickly as possible through a voluntary settlement agreement. HP does not tolerate discrimination of any kind.”

The Hewlett-Packard that developed the HP 3000 might not have hired as many women as the newer HP arms. However, the classic HP never was investigated by the US government about hiring misdeeds.

The Labor Department alleges that through routine checks for compliance with employment laws, it found “disparities in compensation between male and female employees working in similar positions.” HP offices in San Diego and Boise, Idaho — the latter where HP board kingpin Dick Hackborn headquartered himself throughout the 2000s — as well as HPE offices in Houston and Fort Collins were the sites where illegal compensation was discovered.


November is a month for 3000 owners and nonstop regrets

NonStop News

NewsWire Classic

We've marked the end of HP's passions for the 3000 many ways and many times over the last 19 years. The month of November is upon us again, and once again filled with changes. From 10 years ago, the story of the 3000's could-have-been fate, reflected in NonStop and its then-current division leader, rubbed some salt into an old wound.

November is a month filled with memory for many a 3000 owner and user. Some of the sting of watching HP stop its futures for the 3000 is sparked by the enthusiasm offered by HP's NonStop general manager, Winston Prather. NonStop enjoyed its first exclusive conference this fall, while Prather is finishing up his fourth year as GM of the server's Enterprise Division.

Prather held the very last post of General Manager for the 3000, a job where he said it was his decision alone to announce the "end of life" (as HP loves to call it) of the server still running more than a few  major firms. You can pretty much see the retread from his 3000 talks in his message in the NonStop bimonthly magazine, The Connection, from his intro for this Fall's issue (pictured above; click for details).

With all the changes we've made... we've stayed true to the what NonStop has always done best: delivering the scalability, availability and integrity you rely on to run your business. It's a NonStop, not a Tandem. The difference is real, the fundamentals remain.

Fundamentals remain on duty at many HP 3000 shops which Prather predicted would be long ago migrated. But the struggle continues to eliminate an IT asset as quickly as he eliminated 3000 futures. One customer wrote us -- and didn't want their name used, for fear of risking a severance package -- about a second attempt to replace a custom-built application. "The packages that we’ve been sold, complete with rosy allegations of full asset management functionality, simply don’t have it," he said.

Some kinds of applications are custom-written all over the world, the manager added, and "whole concepts of our line of business are obviously brand new to the programmers."

This manager retired a few weeks after the organization's “conversion staff was only now asking for descriptions of the old database. They’re obviously not converting anything; they’re just going to archive the data and hope they can refer to it later."

In the meantime, the company's management dropped all support for the HP 3000s, even though one lost a disk drive and failed to boot from it. Other than a daily full backup, there's not even a shadow of support for the systems. Without a tool like Adager to rely upon, "the database will overfill (work order lines keep on coming!) in about four weeks." Of such high-level organization's decisions -- running a 3000 until it careens into a ditch -- are a system manager's nightmares conjured.

"I’ll return to the fray seeking work," said this 3000 pro. "But what I’ll do is in the air -- obviously not much 3000 development going on, but I may be just the ticket for maintenance projects, or I can probably be valuable in a conversion. I know I’m employable and there are a few 3000 community residents who know I’m reasonably smart; I’ll be okay."

HP's hubris hovered on the dream that any 3000 app could be moved or replaced. NonStop made it to the other side of the 2002 merger with Compaq, and the 3000 didn't. Along the road, the scalability, availability and integrity relied upon by some businesses fell into in the hands of the migration and conversion companies assigned to muck out the mess.

Perhaps the product name of the NonStop line will keep its customers from looking backward at the last business decision which HP put in Prather's hands alone. That's his story of your November history, even to this day. The buck stops at his GM's desk, right up to when he decides to dismantle the furniture that might still have a future.


Upstart startup leads off with 3000 news

Good every day
Do you remember the day your first 3000 logon banner rolled across a terminal or a PC? That heady feel of stepping into something new with a promise of permanent promotions? You knew about MPE, a little, or just slid into an office chair and began to plug away at COBOL apps that tapped IMAGE data for the first time.

Starting the NewsWire, 25 years ago today, was not like that. My partner Abby and I arrived at the first issue with 22 years of publishing experience. Between us, we'd managed and launched operations for 18 news publications in the tech industry. Abby was already a publisher at four different magazines.

What was different about the NewsWire startup was its ownership. Just us, along with 10,000 or so owners of HP 3000s. Our audience owned our future. A few told us we were making something that would turn out to make us nothing. A subscription was "Not even worth $10 a year," said one 3000 veteran who'd written features at the HP Chronicle, my previous 3000 outpost. He came on to write for the NewsWire in our October 1995 issue, Volume 1 Number 1, as we say in publications.

That first technical feature, written by someone who doubted we'd sell subscriptions, was "PatchManager/iX: Maintenance Simplified." It toured the new software from HP for patching MPE/iX 5.5. That release was only forthcoming, as they call books that are promised but not yet released. In particular, one staging tool in PatchManager would improve patching. "Welcome to the 21st Century," the feature read. "MPE will go one better than most Unix systems with the StageMan/iX."

The software resolved a crying need. "Backing out a patch in today's MPE/iX environment can rival the agony of abdominal surgery—without the benefit of amnesia," Guy Smith wrote.

HP had been working on PatchManager/iX for more than a year by October of 1995. In publishing the NewsWire 25 years ago, we were picking up the trail of a business server getting a restart from its vendor. PatchManager was "created strictly to address customer issues with the patching process, not as a cost-saving measure," HP said.

Early technology

Like our readers, we were more cautious about new technology from the commodity sector. One report said "HP 3000 managers press Win95 into service—slowly" while the 3000-ready app Netmail/3000 was releasing DeskLink. The module of Netmail connected HP Deskmanager mail nodes to the outside world. "Until DeskLink came along, HP had been recommending the HP Deskmanager sites set up a Unix system to give their Desk users Internet access." The fall of 1995 was so different that email systems were thriving that didn't use the Internet—we always capitalized the word Internet that year.

We counted on those subscribers for our first revenues, but it was the advertisers and vendors who showed up first. At one point over the last 25 years, we had more than a thousand paid readers. That point arrived years after ads from sponsors—we borrowed the term from TV advertising—carried the NewsWire's fortunes. A publisher, my partner Abby stared down the daunting first months with just a few advertisers. WRQ, the biggest software company serving the 3000 other than HP itself, shook our hands on the Toronto Interex 95 floor for a full-page spread. Those pages 12 and 13, plus HP's ad on the inside front cover and Adager's ad on the back cover, were among our bedrock supporters. Full pages from MB Foster and the Support Group were also part of the starting lineup of our startup. All are serving the 3000 today. Well, not HP.

Creating the graphics files for printing was also Abby's job, tied so closely to the artwork for the ads. I came in during her first issue work to find our Macintosh LC struggling through refreshing pages. We ordered a Power Macintosh 8500 that day, but the chugger of the LC was going to have to get us through our first printing. 1995 was not a great year for Apple. In a few more months, Bill Gates would advise Apple to sell itself to Microsoft.

HP assured our readers they wanted open systems computing. The 3000 was putting on the clothing of an open system, an ill-defined term that usually meant Unix. Open was certainly not the truth about any system vendor's Unix, operating systems usually handcrafted from the standard Berkley Unix to exploit vendor hardware. Unix was open in the sense that software vendors always supported it in general. On the ground, vendor to vendor, the OS had as much support in apps as MPE/iX. If your app was having a problem, you called a vendor support line and logged your problem.

Taking our shot

If MPE/iX enjoyed the popularity of Unix in 1995, we might not have taken our shot with the NewsWire. The 3000 world was a forgotten backwater of IT. Our modest venture of two publishing pros in two back bedrooms, tapping experience and a deep list of contacts and experts, never would have had much chance against the likes of publishing giants like IDC, CMP, Ziff Davis, or even Datamation. I'd written freelance for Datamation two years before our NewsWire upstart startup. In the year before we launched the NewsWire we'd both worked on contract for Interex, writing and managing subscription campaigns. One of the hardest talks we faced in that fall was telling Interex executive director Chuck Piercey we were going to sail our own ship into the rest of 1995.

Always the former sports editor at heart, I wrote an editorial for that issue that compared the 3000 to baseball legend Cal Ripken. That year, Ripken broke the record for consecutive games played without a day off. Choosing to use the 3000 represented that same pursuit of reliability. 

"All around MPE environments, other systems go down, fail, and struggle to stay online. The HP 3000 takes the field every day. If computers were baseball players, the HP 3000 would be the Cal Ripken of the league. Cal recently broke Lou Gehrigs' Major League record for most consecutive games played." The numbers matched up. Ripken had played in 99 percent of the innings across the 2,131 games in a row. "Cal is steady, productive, and not flashy—but respected by those who watch baseball closely. Those are the traits of the HP 3000."

We started up in October, a time that leads up to the World Series. In the summer of 1994, I'd toured ballparks with my 11-year-old Little Leaguer for a road trip. The journey and its fatherhood roots would become Stealing Home, after 25 years of conception, revision and writing, then publishing. Baseball felt like a natural fit for the NewsWire and our 3000 focus. Willie Mays was a baseball legend and a star. He knew it was an every day, all the time job. "It isn't hard to be good from time to time in sports. What's tough is being good every day," he said. That was the 3000 and its community and its major league of vendors: good every day.

Not without fears

We had our panic and fears during those earliest days. 3000 owners might have experienced some on the day they learned HP wasn't going to continue selling the servers. They could do little to change that. We had to ride out the fallow times in the first year, those months when some vendors wanted to wait to see who'd support the upstart news outlet.

When we traveled to our first Interex show with a full issue, in Anaheim's HP World of 1996, HP was waiting with a warning. Frankly, the state of the 3000 market was not going to earn an HP recommendation of the 3000 to the large corporations. Glenn Osaka had been in charge of the 3000 group and then moved up to managing the business server group. Hearing that HP's heart wasn't in its 3000 work sent a bolt of panic into us. Two people with ad contracts to serve and plenty of ink, paper, and postage to buy—we didn't want to hear how little the upper HP brass thought of the 3000. It was a legacy business, after all. Show some respect.

Little of that first hard summer of 1996 matched the wonder of dreaming up the NewsWire in the spring of the previous year. In March of 1995, we talked about a newsletter that would do the work of a magazine, produced on a tight budget. We'd worked for a publisher together whose purse strings were always drawn tight. We didn't need four-color printing. We'd learned to do good with two colors: black, and a fire engine red. We had to educate many a vendor on how to create artwork that required only two colors.

Then we printed the first issue and got the newsletters delivered two weeks late, produced on too-heavy paper that busted our postage budget. A new printer took us to press the very next month. Abby had to hunt down a graphics company to replace the in-house work the old printer performed.

Y2K and the rising tide of tomorrows

Like many people in our community, the approach of the Year 2000 lifted our ship. Advertising swelled as software companies added products and customers. The legacy applications and systems were going to need more attention to get them through the narrow part of the calendar, that Dec. 31 when the first two digits of the year were going to turn over for the first time in computing history.

The 3000 business seemed to be soaring by the end of 1999, a period when we posted some of our highest page counts. Interex conferences carried extra ad dollars and gave us chances to sign on new subscribers. The web site was popular enough to carry a paywall tied to subscriptions. For the first three full years, an HP 3000 hosted our web pages. Our webmaster Chris Bartram created a random passcode generator on a 3000 which assigned login passwords for subscribers. After more than three full years, another website, 3kworld.com, paid to license our content. We walked away from further subscription growth to get our stories into a wider world. 

More than two years later, HP's managers looked at the prospects for selling these servers in a post-2000 world. Maybe legacy computing became more vulnerable after the classic apps cleared the Y2K hurdle. We'd only been publishing for about six years when the fateful November 2001 news arrived. I developed the Homesteading label for the thousands of customers who'd be going nowhere soon. I was in Europe vacationing with my son when the call from Abby arrived. In a burst of hubris and desperate hope, I rewrote a front page of the Flash Paper that handed the shutdown news from HP to a readership stunned at the prospects of fewer tomorrows.

For some of our readers, HP's intentions of almost 19 years ago mattered little. Their companies were always going to follow their own counsel and were devoted to a full return on their 3000 investment. Many more had careers derailed or sidetracked, saw fortunes dwindle, made plans for different tomorrows.

The NewsWire was never built to become a massive operation with offices, staff, and benefits. Things were lean enough in the Nineties that no one here carried health insurance. Organizing for a small footprint—though not so small that healthcare didn't ever arrive here—gave us a plan for survival long term. Here at the end of 25 years of publishing, 20 of those years have unfurled in the shadow of HP's certain departure from 3000 life.

Those earliest months when we could believe in HP's 3000 faith were still tinged with wry, sometimes dark comedy. Citizen Kane is a favorite film here, and we'd often quote one of its lines at each other when times got tough. Kane is replying to his trust manager when he's asked why he'd want to buy the New York Examiner. "I think it would be fun to run a newspaper," Kane said.

It's been fun. We look forward to more, bolstered by support from companies with a long-term view of 3000 usefulness, like Pivital Solutions. We have enjoyed support from readers and owners and veterans of the 3000 world, too. Here's to a fresh quarter-century, however it looks. The Tampa Bay Rays are looking like a good prospect to get into the World Series, winning on a pittance of a payroll. Little things that are built smart can surprise you with their ability to be good every day.

 


Where HP sells legacy OS's, and why it did

Spacex-rocket
Apple soared through a $500 per share mark yesterday. The market confidence comes from assessing the outlook for Apple's business model. The computers and devices Apple sells are powered by proprietary chips, either today, for phones and tablets, or next year for the rest of the company's line.

The operating systems for these devices are also Apple's specialized OS's. Software created for iOS or for MacOS will not operate on other devices. Soon, the Apple-branded chips will demand rewrites of applications.

Does this sound familiar? It should for customers who recall the state of HP's Year 2000 business plans. Proprietary operating systems all around for MPE, VMS, HP's Unix, and NonStop. HP-only chips powering all of those servers. Software rewrites needed as newer HP-proprietary chips entered to replace PA-RISC.

In a tale of two companies, HP's valuation at $70 a share in 2000 could be compared to Apple's $3.68 per share. Then there was a 3:1 split for Apple, and now there's a 4:1 split coming next week.

Making its own hardware and OS has been a good business play for Apple. HP turned away from this model to embrace commodity computing. Today only NonStop and HP-UX operating systems are sold by HP.

OpenVMS has been licensed by VMS Software Inc. MPE/iX licensing ended in 2010. Hewlett-Packard has a split over those two decades, indeed; the company is now halved into Enterprise and Inc. The size of its wide-ranging mission was too inefficient to maintain as a single entity. Commodity couldn't carry HP into a higher orbit.

Legacy strategy has often been powered by vendor-specific technology. Many factors apply to this year's soaring valuations. Apple became the first company ever valued at $2 trillion this month.

There's still value in legacy enterprise. The HP-UX and NonStop environments can be purchased from HP Enterprise today. Tru64, the Unix built by Compaq before HP bought the firm, is sold through indie outlets like Island Computing.

The last two decades seem to have proven there's no harm in engineering proprietary hardware and software environments. The crucial element is innovation and market reach. The invention within OpenVMS and MPE/iX keeps working for corporations that invested in legacy designs. Apple is releasing its 16th version of MacOS this year. Version number 14 of iOS rolled out this summer.

HP was able to create about 14 major releases of MPE/iX over the 20 years it sold the OS. It just hasn't been able to sustain growth using its own designs. That's a mission its legacy customers have accomplished.

Photo by SpaceX on Unsplash


25 Years: Ready to paint the 3000's future

Paintbrushes
In this week of 2006, HP was readying its first updates on how to manage the forced 2006 migration date for MPE/iX. The president of the only remaining international user group, Chris Koppe at Encompass, had picked the key sessions from the upcoming HP Technology Forum.

The 2006 Forum would be HP's first trade technical show for its enterprise customers to make its appearance as scheduled. The previous year's Tech Forum was bounced out of New Orleans when Katrina blasted in. August is a dicey time to schedule anything in the Gulf. This week we hear that the Gulf will host two hurricanes at once next week.

In '06, customers could come to an HP conference in Houston to hear

HP e3000 Transition and Migration Customer Panel
Successful Migrations: Making Them Happen
HP e3000 Business Update
OpenMPE: A Current Status
HP e3000 Peripheral and High Availability Environment

HP would cover a lot of ground in the 75 minutes that Dave Wilde would speak along with Jennie Hou, who became the 3000's final Business Manager. They'd cover

A high-level summary of developments in the HP e3000 business during the past year, recent news, and a review of what customers and partners can expect from HP during the next couple of years.

How HP was helping customers and partners transition to other HP platforms

How HP is supporting companies’ business-critical environments as they transition

There would be some frank discussion for the 3000 customer who was not well-along on a migration path, or even considering that road:

Address the concerns of companies that may continue to depend on the HP e3000 to meet some business needs beyond HP’s end-of-support date.

2006's show marked the last time the HP 3000 got so much airtime at a conference.

Image by Rudy and Peter Skitterians from Pixabay


On This Day: Sailing toward new reunions

DougMechamBoat-05Aug
Interex founding director Doug Meacham

Fifteen years ago today, the 3000 community was on a quest. Where a conference was supposed to take place, San Francisco, there was nothing but unpaid bills for exhibit halls and meeting rooms. No HP World 2005 would start up, gathering the MPE/iX community for the annual North American meeting as it had for 30 years. 

A luncheon was arranged, though, to serve community members who had nonrefundable tickets to the canceled conference. The Interex user group didn't host it, of course. The group was belly-up dead. The effort emerged from the minds of Alan Yeo and Mike Marxmeier, software vendors who faced the prospect of time in the Bay Area and a hunger to meet 3000 folk.

I wrote about how reunions are a part of family life. The 3000 still has a family, even while many of its members are retired. The gatherings are all virtual now in our lives. Such a thing was nearly impossible 15 years ago. My mom is just as departed as Interex by today, gone but well remembered. We love things that leave us, which is a good reason to grasp onto one another until the departures.

NewsWire Editorial

Even though we work with machines to compute, we crave the spark of personal contact. I felt that contact this month in the heat of Las Vegas with my brothers and sister. We met in Mom’s hometown to move her. She went down Jones Boulevard just one mile, a significant journey when your next birthday, like Mom’s, will be Number 80.

Our days were filled with strapping tape, corrugated cardboard, and sweat in the desert heat. But the nights and the early mornings carried our laughter and the looks that passed between three adult children remembering the bumpy roads of our youth together. It was a summer reunion, a rich consolation for me in this first season without an HP World after 20 years of meeting old HP friends at Interex shows across North America.

I sat in the airport with my brother Bob and told him the story of the Interex demise, then rattled off the array of cities that have been my summertime stops. Most often, we met in San Francisco. And yes, even Las Vegas once. The Interex show never visited Texas during my summertimes in the market, just like my brother John never has visited me here. That’s why we Seybolds needed a reunion, to fill our cups with the memory of the looks on family faces.

Face time, we call it in business, something to savor and prepare for. The longer we all have stayed in the 3000 community, the better each summer’s reunion became. We could tell stories, gaze into eyes under brows growing gray, recall and dismiss. I would come back from the summer trip full of flint to strike for stories, leads I could track and then transform into news you could use.

So in a summer where I now feel adrift without an HP World reunion, I also give thanks — for the fortune that turned Mom’s apartment complex into condos, forcing a move that rounded up the Seybold kids for the first time in five years. We kids are well connected, here in the early bit of the new century. I don’t mean that we’re movers and shakers, but that we use e-mail, websites, cell phones, and blogs to keep up with our family news. All those links pale compared to that contact, the feel of the firm grip of a handshake or grasp of a heartfelt hug.

We Seybolds have another reunion on our horizon, and there will be one more on the HP 3000 community’s calendar, too. I’m not talking about the meeting next month when HP will host its first Technical Forum, the New Orleans show that contributed to the Interex demise. That won’t have the feel of mom’s 80th birthday this December. We’ll plan and anticipate that event with as much ardor as 3000 veterans, the folks who helped Interex grow for more than a decade.

Instead of New Orleans-bound meetings, the news broke early this month that the 3000 family will have a luncheon as its 2005 reunion. Mike Marxmeier and Alan Yeo made the best of non-refundable tickets to San Francisco and hosted a lunch gathering. A few days later the OpenMPE user group — just about the only one left, now — held a meeting at an HP facility. We’re all wondering how large that OpenMPE family might grow up to be, now that Interex has passed away.

The meeting at the HP campus reminded me of the gentle tug between vendor mother-ship and user tender-craft. Before Interex began to called itself by that name, the group was the HP 3000 Users Group, operated with an eye toward collaboration with the vendor rather than combat. Maybe it’s time to remember, during this month of the Interex flame-out, how that relationship operates when it serves both vendor and user.

My friend Duane Percox at QSS explained it well. The HP 3000 members of Interex — those who founded the group — got more radical and active through the 1990s as their HP options grew slim. The scuffles were fun for a while, but also something a vendor won’t brook endlessly. When HP got the nerve to squash Interex with a competing show, the market's more nimble marketers didn’t hesitate.

Percox said that give-and-take between vendor and users lets both sides save face. Marketing wants a great spin on customer experiences, while the customers want the truth. You must claim to be independent from your very first day — if you want the truth to be your main mission.

“You can’t begrudge marketing for wanting the best spin on things,” he said, “just like you can’t begrudge the users for wanting the truth.” The long-term formula to mix these elements has always been collaboration, something Interex’s founder Doug Mecham recalls in his Q&A interview.

At that 3000 luncheon we got a few hours of face-time with one another — so the 3000 customers and partners might feel like I did right after my family reunion in Las Vegas. All of us went home in the afterglow from a handful of days of hard work, marinated in laughter and yes, some sadness over days past. Toss in that OpenMPE meet, and mid-August felt a bit like the typical Interex week. In Vegas and in the Bay Area, I was getting to know a town better and a hotel or two — like the way we Seybold kids learned the short cuts around the sprawl of Las Vegas Boulevard, or finding the back steps up to the room at the Tropicana.

Because I’ve had my stand-in reunion as well as my family gathering, I’ll miss the Interex show a little less this month. I could count on the family of brilliant, funny, and fulsome people like the 3000’s founders and fans to engineer a replacement reunion.

Face time can give you a chance to hear significant answers. In our last hour together in Vegas, Mom read us questions off a newsletter from her new apartment — good ones like “What event in history would you like to have experienced?” or “If you wrote your autobiography, what would its title be?”

We kids shared many lessons learned in spite of ourselves, something I wish for any group of people who consider themselves family. I hope for other reunions in my future among 3000 folk. You’re a group that can teach lessons about collaborating.


25 Years: Surviving beyond HP's wishes

Pontiac survivor plate
As the 3000 NewsWire closes in on its first 25 years, our 25 Years series tells stories from selected days in history for the 3000
.

In 2002, an emulator to enable an open MPE was fresh on the 3000's table. A group of the same name, OpenMPE, took its first mission as taking hold of the 3000's OS futures. HP's Dave Wilde met with Jon Diercks shortly after HP's "we're quitting" news surfaced. Diercks launched the idea of a group to promote an open-source MPE/iX. With Linux soaring, open source would lift all ships.

Even the ones that were drifting along at the end of three decades of success.

The emulator question rose when the community appraised its options to keep its legacy choices alive. Millions of lines of proprietary HP code couldn't stand a chance of becoming open-sourced. Quickly, OpenMPE's mission became saving the HP hardware that could run MPE. In 2002, HP drew a firm line that no emulator could ever mimic the PA-RISC chips unless the hosting hardware wore an HP badge.

During the summer that led to the first Interex conference where HP had to face angry customers, the HP-only mandate stuck in the community's craw. Patrick Santucci, working with systems at Cornerstone Brands, shared his frustration on Sept. 27. "HP still seems to be saying, 'Die, MPE, Die!' Why not let the company writing the emulator decide what hardware they will support it on? After all, they're the ones doing the work."

From that conference during that week in Los Angeles, I reported, "HP gave customers the first ledges of opportunity to continue their climb with their HP 3000s, announcing it will allow a 3000 hardware emulator project to continue as well as creating new MPE licenses."

Nothing changed about HP’s beliefs about the proper future for HP 3000 owners, however. HP’s leader of its 3000 operations, Dave Wilde, still believes that every customer must begin planning for a transition of some sort. But the company’s HP World announcements represented its first realization that staying on the computer platform is the best course for some companies.

HP won’t let a [licensed] version of MPE be used with a hardware emulator before the 2003 end of sales date, although that kind of timing of releasing an emulator would be a remote possibility anyway, according to Allegro’s Scott. Another company, SRI, has said it considers creating such an emulator to be a less lengthy project. SRI sells an emulator for the Digital VAX hardware.

Almost 18 years later, that SRI emulator is Stromasys' Charon, which boasts an HP 3000 PA-RISC version. Charon began serving 3000 owners about a decade after that HP move to permit emulators. From the very first months, HP's PCs did not power the 3000 emulator.

Image by rjlutz from Pixabay


Logon advice launches new 3000 admin crop

Row of Lettuce
By George Stachnik

There's a new crop of people taking over management of these machines. Many of the people who have managed and championed HP 3000s in the past have moved on. Today's HP 3000 system manager is now more likely to be young and have little HP 3000-specific experience, knowledge, or training. New HP 3000 system managers have been successful managing environments that include Unix, and Windows. Now they've been given responsibility for an HP 3000, a machine about which they know little or nothing.

If you fit in this category, take heart; I think I have some understanding of what you're going through. When I encountered my first HP 3000 in 1983, all of my experience had been with IBM machines. I was glad to hear that the HP 3000 is comparatively simple and elegant to use (at least compared to a mainframe), but I was still expecting a long learning curve.

For many customers, information about the HP 3000 — especially beginners' information — can be hard to come by.

Logging on

In Lewis Carroll'sThrough the Looking Glass, Alice is encouraged to "Begin at the beginning." This always seemed like good advice to me, and that's what I'll do now. Let's begin by exploring how one logs on to an HP 3000. We'll also see how to explore your system, and find the programs, files, and information that are available to you. We may even learn a few other things along the way.

You're likely to have a PC or workstation sitting on your desktop. In that case, you need two things: a physical connection between your desktop and the HP 3000, and a piece of software that lets your desktop computer act as if it were an HP terminal--a terminal emulator.

The desktop-to-3000 connection can use the same RS-232 protocol used by terminals. But a network connection using standard IEEE 802.3 or Ethernet is preferable. All you need to know is that the HP 3000 supports industry-standard telnet services, and you can use them to log on to an HP 3000 from your desktop computer.

If you're using a Windows PC on your desktop, a number of HP terminal emulators are available. Among the best are WRQ's Reflection series from Attachmate, and Secure92 from Minisoft. PC-based terminal emulators support industry-standard telnet services to connect to hosts like the HP 3000. Reflection and MS92 also support the NS/VT proprietary protocols.

Regardless of what kind of terminal or terminal emulator you've connected to the HP 3000, pressing the RETURN key (on a PC, it's usually labeled the ENTER key) will cause the HP 3000 to transmit the string "MPE/iX:" back to you. This is a prompt from the HP 3000 inviting you to log on. It's analogous to Unix's "login" prompt.

Incidentally, if something other than "MPE/iX" appears on your screen, don't panic. The system prompt is configurable and your system manager may have changed it. Regardless of the prompt that appears, the command you'll use to log on is always the same. It's called the "Hello" command. (Didn't I tell you that the 3000 is a friendly little machine?)

The HELLO command you enter will typically include two parameters separated by a period. These two words identify you to the system. The first one is your user name, and the second one is your account name. When you log on, at a minimum you must specify a user name and an account name. If there are passwords associated with your user and account (and there should be!), you will be prompted for them.

Continue reading "Logon advice launches new 3000 admin crop" »


This blog turns 15, logs a half-million views

Screen Shot 2020-06-16 at 2.16.21 PM
Earlier today, this blog served up pageview number 500,000. That's a half-million times that some business computer expert needed to learn about, repair, or plan for using MPE/iX or the HP 3000. Content at this web address still serves a community.

The straight-up math tells us that the total amounts to 33,333 page views a year on average. These days, the pageviews are closer to 16,000 per year. None of those pageviews are included among those off the website at the original 3000newswire.com. It's the repository for the 1996-2005 Newswire, the Online Extra newsletters, plus a record of 122 monthly FlashPaper supplements. That site goes back 24 years.

A half-million blog page views, all since the year before HP's original support shutdown, shows remarkable devotion. Not even necessarily to the NewsWire; that half-million illustrates how long a server can remain vital and useful. We've been telling the 3000's stories for more than 18 years since HP started to quit on it. We reported for six years while the product was still a part of HP's futures.

Although the news from that 2005 monthly roundup might seem like history, it reinforces the choices 3000 managers face today. Solutions not tied to a single vendor continue to face a steep decline. Going independent of a system vendor is the default move.

The 2005 news reports showed an HP trying to find relevance in a changing IT landscape. June was the summertime after CEO Carly Fiorina left HP. She departed after throwing the vendor's weight behind high growth, low-margin computing. PCs, laptops, and printers were ascendant in the HP of 2005. HP was finding new enterprise business elusive, unless the new systems ran Windows. Unix served some 3000 sites that migrated from MPE/iX. Many more of the departed had migrated to Windows. Some were taking a chance on Linux.

The 2005 customers were moving away quickly from the OS at the heart of their companies. By mid-year, only 43 months had ticked away since HP's exit announcement. There were not a lot of customers already exited by the month the blog opened for business. We surveyed customers to discover that a close to half were replacing a 3000 with Windows 2003 Server.

That was not HP's plan at all, figuring enterprise features of HP-UX were going to snare the ex-3000 sites.

This blog gave us the avenue to report survey updates immediately. One of the first five blog articles that kicked off the page view deluge updated our migration target survey with fresher results.

Customers expressed reluctance to put mission-critical computing onto Windows. But Windows’ familiarity won it many converts. This made HP's exclusive tech advantages less popular. “We are moving to a Windows 2003 Server environment," said programmer supervisor E. Martin Gilliam of the Wise County, Va. data processing department, "because it is the easiest to manage compared to Unix or Linux.” 

Hewlett-Packard was casting about for a plan to keep growing. In 2005 HP announced it would separate its printer units from PC segments. HP's 1990s management assumed everything was supposed to thrive on the business model that drove its laser printer success. A smaller direct sales channel, with less room for different and superior engineering, was the result of chasing commodity computing sales. HP was reorganizing, back toward a business plan that acknowledged not all products can use the same strategy.

Printers and PCs got their own leadership. At the time I looked into the future and saw that the HP 3000 customers were forced to leave might see another spinoff. A separate enterprise computing business. "An HP with non-Windows servers running HP-UX and OpenVMS could be just around the corner."

Nine years later, HP decided to break up the brand. Enterprise servers split off from the low-margin products. It didn't make HP more relevant to business IT. By 2014 even OpenVMS was flagging — and it remains the product line with the biggest number of customers not using Windows or Linux.

Our first month of blog reports included more tactical advisories. Some remain useful today. Keven Miller, who still supports 3000s and gathers MPE resources for the community, updated his 3000 firmware without the aid of HP's support engineers. It's the unusual site which doesn't need outside support help. After all, Miller's 3K Ranger firm serves 3000 customers. But the how-to about changing Processor Dependent Code is still on this blog's site, ready to serve its goodness through another page view. You will need patches, where the independent support firms can make them available.

We said at the time that "Miller's experience represents the level of admin skill a 3000 owner is going to have to call upon once HP's support leaves the field. If you're uncomfortable with this kind of admin, but need to keep your 3000s in service, there's a good lineup of 3000 service providers who can help you, all in the third-party market." There is still a healthy group of service companies working 15 years later.

Onward to the next half-million page views. It ought to happen around 2051, if we can keep up the current pace. I'll only be 94, while the 3000 will be 77. I hope to age as well as MPE.


SSD devices head for certain failures

Western Digital SanDisk
A solid-state storage device is not usually a component of HP 3000 configurations. However, with the onset of virtualizing MPE servers, those drives that do not move, but still store? They are heading for absolute failures. HP is warning customers.

The problem is surfacing in HP storage units. It's not limited to HP-brand gear, though. SanDisk devices cause these failures. One fix lies in HP Enterprise firmware updates.

HP Enterprise disk drives face a failure date of October 2020, unless administrators apply a crucial firmware patch. Notices from HP Enterprise warn the owners of some disks about failures not earlier than October. Other Solid State Drive (SSD) disks are already in danger of dying.

Some SanDisk SSD drives have already rolled past a failure date of last fall, for those that have operated constantly since late 2015. The failure of the drives is being called a data death bug.

For some, HPD7 firmware is a critical fix. HPE says that Western Digital told the vendor about failures in certain Serial Attached Storage (SAS) models inside HPE server and storage products. Some SAS SSD drives can use external connections to HPE's VMS Itanium servers.

The drives can be inside HPE's ProLiant, Synergy, and Apollo 4200 servers. Some of these units could serve as hardware hosts for virtualized 3000 systems. The SSD problem also exists in HP's Synergy Storage Modules, D3000 Storage Enclosure, and StoreEasy 1000 Storage. If the disks have a firmware version prior to HPD7, they will fail at 40,000 hours of operation (i.e., 4 years, 206 days, 16 hours). Another, even larger group of HP devices will fail at 3 years, 270 days 8 hours after power-on, a total of 32,768 hours.

The numbers mean that the failures might have started as early as September of last year. The first affected drives shipped in late 2015. HP estimates the earliest date of failure based on when it first shipped the drives. Another batch of HP drives shipped in 2017. They are also at risk. These are the drives looking at an October 2020 failure date without a firmware update.

Beyond HP gear

The devices are Western Digital's SanDisk units, according to a report on the website The Register. Dell has a similar support warning for its enterprise customers. Dell lists the SanDisk model numbers:

LT0200MO
LT0400MO
LT0800MO
LT1600MO
LT0200WM
LT0400WM
LT0800WM
LT0800RO
LT1600RO

RAID failures will occur if there is no fault tolerance, such as RAID 0. Drives will fail even in a fault tolerance RAID mode "if more SSDs fail than are supported by the fault tolerance of the RAID mode on the logical drive. Example: RAID 5 logical drive with two failed SSDs."

Adding to the complexity of the SSD failures, firmware to fix the issue has two different numbers. HPD7 repairs the 40,000-hour drives. HPD8 repairs a bigger list of devices. Leaving the HPD7 firmware inside drives among the larger list of disks — which have a death date that may arrive very soon this year — will ensure the failures.

Full details from HP's bulletins for the 40,000-hour and for the 32,768-hour drives are at the HPE website. There are also instructions on how to use HP's Smart Storage Administrator to discover uptime, plus a script for VMware, Unix, and Linux. These scripts "perform an SSD drive firmware check for the 32,768 power-on-hours failure issue on certain HPE SAS SSD drives."

A list of 20 HPE disk units falls under the 32,768-hour deadline. Four other HPE devices are in the separate 40,000-hour support bulletin.


Wayback: 3000s showed a Spectrum of hope

BeyondRisc
Thirty-six years ago this month, HP put a reboot of its business future into orbit. The project called Spectrum was the entry of PA-RISC (originally called "HP High Precision Architecture") when publicly announced in the HP Journal in 1985. HP brought the future into the light by killing its Vision project at the 1984 Interex user conference.

Stan Sieler, one of the founders of Allegro, was working at HP in the years before the HP announcement of what the company called High Performance Precision Architecture RISC. "A year or so later, when it was simply called PA-RISC (or HP PA-RISC), I asked Joel Birnbaum what happened to the "High" and I was ignored. Along with Bill Worley, these were the fathers of RISC inside HP. Birnbaum had been recruited from IBM's RISC project."

Digital was famous for raining on HP's Reduced Instruction Set Computing, as well as Unix, during the time PA-RISC rose up. Ken Olsen, DEC's founder, pulled the plug in 1989 on Prism, Digital's RISC computer design. HP struggled to get its business servers onto PA-RISC, managing to put its Unix onto the new architecture first. Digital tried to make inroads by touting its 32-bit VAX processors versus the 16-bit HP 3000 classic servers. "Digital has it now," the ads in the trade weeklies proclaimed.

Sieler says that several other companies were incensed at HP having a product called Spectrum, including Chevrolet. "I remember hearing reports of some legal actions against HP, which were reportedly dropped after HP promised to never use that term externally. That is apparently why we titled our book about PA-RISC Beyond RISC instead of Beyond Spectrum. We were told HP wouldn't buy any copies if we had "Spectrum" on the cover. But we did sneak it in: the spectrum is the photo."

RISC was designed to consolidate the development of peripheral interfaces for all all three of its computer lines: HP 3000, HP 9000s, and its real-time systems the HP 1000s. About late 1986, the real time version of HP-UX on PA-RISC —  demonstrated at the 1986 Madrid Interex conference on an HP 9000/840 — was quietly dropped. "We used to have an HP publication about real time support for HP-UX, but I think it went to the Living Computer Museum in Seattle when we gave them our manuals about two years ago," Sieler said.


Chicken, egg: First the 3000's OS, then chips

Rooster
Editor's Note: A technical paper from the DEC world asserted that VMS was the first operating system designed before the chipset that it ran upon. MPE's earliest designs were just as innovative. We asked Stan Sieler for some history.

By Stan Sieler

I'd assume that the 16-bit Classic instruction set architecture and the original MPE were designed at about the same time — probably with the architecture being mostly ready/running (real or simulated/emulated) before the software was ready. Once MPE was up and running, some years later there were arguably one to three architectures designed for it (exclusively or not).    

FOCUS

A group of about 12 of us (labs, chip people, me for the OS lab) designed a 32-bit architecture for the next generation HP 3000.        

The architecture was an evolution of an earlier FOCUS used by Ft. Collins for some HP 9000s (after the 68000 models, before the PA-RISC models), and it (the earlier) was either used by the Amigo (HP 300) and/or was inspired by the Classic 3000 architecture. The project got dropped in favor of the VISION architecture.

VISION        

This was the object-oriented architecture (with 64-bit virtual addressing) that was going to be the next-gen HP 3000, running what was going to be called HPE. We had HP 3000/4x computers with rewritten firmware emulating it, and there were a couple of hand-made real CPU boards beginning to run when I left HP in September 1983 to start Allegro. 

At that time, I had a crude command interpreter running on it under my process management code (I was in charge of process management). VISION was very very interesting.  If I had access rights to an object (say, a record from an IMAGE database with an employee name, a date-of-hire, and other information), I could send another process a "descriptor" (virtual address) that would give them access to precisely the subset I wished (e.g., read access to date-of-hire field of the record). But, that concept is gone now.  No one can do that :(        

VISION was dropped in favor of PA-RISC about a month or so after I left. I commented to Joel Birnbaum that it was dropped because I'd left HP. His reply was, "If I knew that, I'd have gotten rid of you sooner."    

About 1982-1983 I began to hear about an architecture that HP Labs was working on that would allow you to run MPE, RTE, and maybe even HP-UX simultaneously.  It was code-named "Rainbow." I think Rainbow turned out to be PA-RISC.

PA-RISC

In the 1980s, RISC (Reduced Instruction Set Computer) was all the rage. People thought it meant quicker execution due to less complex instructions. I am still dubious. I think they underestimated the types of computations and instruction/memory interactions needed — and, indeed, you can see people throwing more and more and more cache towards RISC in an effort to address the speed imbalance between the CPU and memory.

HPE, essentially an extended version of MPE, was designed to run on PA-RISC. To the extent that the virtual memory (and IO) was quite different, that part of the OS was designed for the architecture.

Most of HPE, later MPE XL, then MPE/iX, doesn't care what the architecture is, any more than  Linux/Unix/Windows cares what the architecture is. I seem to recall that a few aspects of the memory protection mechanism (including the Protection ID registers) may have been influenced by HPE's needs.  

Of course, at the same time, HP-UX was being ported from 68000 / FOCUS to PA-RISC, so there may have been interactions there, as well. Note, however, that HP-UX never fully utilized the PA-RISC architecture — particularly the memory addressability, where HPE / MPE XL / MPE/iX had it beaten by far. I don't think HPE, HP-UX, or Netware (which was on PA-RISC briefly, circa 1993) used all the capabilities, including the ability to, in controlled circumstances, let user code directly access some IO instructions.

Itanium (IPF)  

I think I heard that a basic MPE/iX kernel of sorts had been successfully ported to Itanium before the HP 3000 was killed. Obviously, HP-UX was also ported to IPF.   The primary influence MPE/iX and HP-UX probably had was the Itanium ability to run in either little-endian mode (Intel X86 style for Windows) or big-endian (Class, and PA-RISC style, for MPE/iX and HP-UX).

Other operating systems running on Itanium — which have been released in some cases, not released in others — include Windows, Netware, Solaris, OpenVMS, and Tru64 Unix. This list of systems tends to imply that the architecture was not specifically oriented towards one particular operating system.

In short, I think most operating systems exist (perhaps in an earlier form) prior to the chip architecture, but that most architectures are mostly independent of the operating system design/features. The memory addressability mechanism almost always affects major aspects of the internals of the operating system (as it would with VISION).

Photo by Ashes Sitoula on Unsplash


When the HP Way Led the 3000 Astray

Winding road forest

Editor's Note: Being a legacy system expert has its frustrating days. If experts of today ever wonder why they got into the lifespan of Hewlett Packard and MPE, they can look back to the start and the promise of the 3000. Bill Foster was a part of the HP team that created the system, before he went on to found Status Computing. the story below shows the an HP which had to remake MPE.

All the Foster you want, in an HP history worthy of being a book, is at his website.

By Bill Foster

If there ever was a company that always seemed to do the right thing, it was HP back in the 70’s. We had a term called The HP Way. There was no written definition — it was something you felt. When something good happened it was part of The HP Way. When you had the inclination to do something bad — cut corners on a project, treat a customer badly, turn in an inflated expense account, fire a really bad employee — these things didn’t happen. They were not The HP Way. It’s like we walked around with little halos over our heads.

Of course, if this was the only place you worked, you assumed all companies were like HP. You had to leave Hewlett Packard to become a part of the real world. So, we shipped HP 3000 serial #1 to the Lawrence Hall of Science in nearby Berkeley. A couple of weeks later they shipped it back. That 3000 could support at most two or three users on a good day -- nowhere near 16 or 32 or whatever they promised.  And MPE was crashing three or four times a day.

A few months and a couple of machines later HP punted and withdrew the 3000 from the marketplace. They gave free 2116 computers to the customers in hopes of appeasement — The HP Way. Bill and Dave were fuming -- this had been by far the most expensive project in the company’s history, and Hewlett Packard was being inundated with bad press — something that had never happened in the entire history of the company.

In fairly quick succession Paul Ely came down to save things and a few months later my boss Steve Vallender left. I don’t think Steve was fired — HP never fired anyone back then, they just promoted them into oblivion. But Steve was somewhat un-promotable — he lacked a college degree and HP was pretty snobbish about that.

Dick Hackborn asked me if I wanted Steve's old job. Are you kidding? Sure! Hurt me! I was looking to move up the ladder — this was a fantastic break. My guess was they chose me over my hardware counterpart because management finally figured it was better to put a software guy in charge of computer projects. No matter -- here I was, not even 30 years old, running all the hardware and software development for HP's computer business.

My first and most important job was to come up with a plan for the hockey pucks.  A year earlier, Dick Hackborn had hired a couple of smooth-talking marketing bozos out of IBM. Hackborn created a group called Product Marketing within his Engineering group to compete with the real Marketing group at the other end of the building.

This was very out of character for HP — to hire senior people from the outside. One of their first actions was to give mementos of a project to the engineers who had developed it — something tangible to remember their efforts. Apparently this was done all the time at IBM. The IBM marketing bozos came up with the idea of a brass paperweight about the size of a hockey puck, but about half the thickness. Stamped on each one were three overlapping circles signifying batch, realtime, and timesharing — things that the 3000 was supposed to do.  And each individual’s name was engraved on the back.

These were supposed to be handed out months earlier, but with all the problems, Vallender had hidden them away in a file cabinet. My first command move was to sneak in one weekend, lug them out to my car, and take them home to my garage.  The last thing I wanted was for anyone to get wind of them. The next step was to try to get some kind of usefulness out of the 3000 machine, and that meant fixing MPE.

Image by David Mark from Pixabay


Seeking forgiveness as a support plan

So sorry chalkboard
ERP software becomes wired in deeply at corporations. Now that MANMAN has seen the end date coming for its manufacturer support, customers who rely on the ERP suite are looking for a 2020 plan to keep using it.

One aspect is a ruling about whether a product or a vendor is dead, but the intentions for its product lives on. It's an aspect of law called droit moral in France. Droit moral is not recognized in the US. Intentions are preserved in droit moral.

Some HP 3000 owners considered HP a dead entity after 2008, when no more patches were being built. HP's intellectual rights to MPE and the HP 3000 remain in effect. But there are those moral rights, too. This computer would not have become the keystone at places like aircraft makers and airline ticket agencies without customers' contributions, work that started many years ago. In fact, HP once recognized this kind of help in the market with the e3000 Contributor of the Year Award.

Contributors earn rights when measured in terms of ethics. Droit moral preserves ethics.

Source code rights might belong to customers once a product goes into permanent hibernation at the manufacturer. In 2008, I wrote that I believed that in order to honor droit moral for the 3000 community, HP's increasingly restrictive statements of licensing needed to stop. The vendor's support group needed to move on to other profitable HP markets. The vendor needed to leave owners and customers to continue using their computer, without any extra licensing payments to HP.

Droit moral lived in the hearts of some of the 3000 advocates within HP. While I visited HP's 3000 group one afternoon, the former business manager Dave Wilde and I walked across the wooded HP campus to lunch. That entire campus site is now the location of Apple Park, Apple's worldwide HQ, so things have changed a lot. At the time, through, Wilde said the 3000 group wanted to give the system "the ending that it deserves." It sounded warm and genuine.

Infor, the owners of MANMAN, are not as warm and genuine, even though they have enough sense about branding to sponsor the NBA Brooklyn Nets with an Infor logo on Nets uniforms. At the moment there's no coordinated effort from the remaining MANMAN customers to establish whether MANMAN truly belongs to customers after the exit of its creator. The customers are unsure who might even respond to such ownership questions.

Continue reading "Seeking forgiveness as a support plan" »


Does orphaned source code belong to you?

Orphan with bike
Not many application vendors still have shingles hung out for business in the MPE market. It's also been awhile since any vendors made an exit from the MPE marketplace. Now that Infor, makers of MANMAN, will depart this coming June, its ERP customers are talking about what source code is rightfully theirs.

During a conference call, about a dozen customers and another dozen independent support vendors kicked around the idea. Every customer on the call had signed a MANMAN license agreement, way back in the 1980s or 1990s. It was generally accepted that you never own a piece of software unless your organization wrote it.

To put it more plainly, the use of a vendor's product is always governed by an agreement. Everybody agrees on the rules for ownership and use.

Then conditions change.

The vendor folds up a product line, or goes out of business altogether. It happened with MPE/iX, to note one instance of the former fate. 3000 users can scarcely take a few steps before they stumble on a software vendor who's closed down all business. That's what happens over time after a vendor has built the bulk of its business around a server that's no longer sold or supported by the manufacturer.

The new condition gets managers asking about why any license should apply to an orphaned product. Permission to own the code that's only been licensed — that's a matter for the courts, or at least lawyers represening both sides.

The hard place the managers encounter is the language that keeps software in a vendor's IP locker. In cases like these, IP not only means Intellectual Property. It means, "in perpetuity." If anyone has a digital copy of their contract, searching for that phrase will certainly bring up a hit.

Eleven years ago, the 3000 community talked this through while Hewlett-Packard considered the new licensing of MPE/iX source code. Customers wanted their intention of owning a 3000 — to run a business in perpetuity — to match the intentions of HP's product licensing. We invoked French law to give voice to our wishes for that outcome.

There is an aspect of French law which does not exist in US law. It's called "droit moral," meant to protect the moral rights of ownership of a work of art. Even more than HP's support group, the 3000 community considered MPE/iX to be a work of art.

One story about using droit moral in the movie business:

Droit moral is an intellectual right of an artist to protect his work. When an artist dies, the droit moral goes to his heirs, unless he appoints someone else. For example, a John Huston movie was colorized in the US, and the movie was shown this way in the States, despite the opposition of the Huston heirs who were trying to honor their father's artistic wishes. But in France, where the Huston heirs argued their father didn't want his film to be in color, the colorized film can't be shown because of droit moral.

The argument, one which might be tested in court, is that the intention of investing hundreds of thousands of dollars in a product is to use it in perpetuity. Ownership of source hasn't been much tested in US law. The places where cases have appeared before a judge are courtrooms where things went better for the customers than the manufacturers.

Image by Isa KARAKUS from Pixabay


Wayback: HP FAQ captured its OS visions

Canary close up
It's only available through the Internet Wayback Machine, but a record of HP's intent for its enterprise operating systems still exists. For reference we traveled to LegacyOS, a website devoted to the legacies of Sun and HP's enterprise products. The promised land, as HP imagined it 17 years ago, was getting its operating systems to the Itanium Processor Family.

HP's decision to keep MPE/iX away from IPF servers was the canary in the coal mine for the company's business intentions for HP 3000s. Such a canary roosted in mines while work proceeded. If the quality of the air turned poisonous, the canary died and the miners evacuated.

At the time there were only two models of Itanium processors in working servers from HP, so calling it a family was marketing optimism. Nevertheless, moving to the nascent IPF, as well as a new OS in HP-UX, was HP's vision of end-of-life. The life ending turned out to be at HP's MPE/iX labs eight years later, rather than any useful lifespan for MPE/iX.

There is a current-day lesson in any review of the HP 3000 plans of 2002. HP noted at the time the vendor created a Business Critical Systems group. That group, HP's cheerful-but-inaccurate 3000 plans, and HP itself in its classic makeup don't exist anymore. Users can count on their community, rather than the vendor, to see the conditions for any end of life canary.

Q: What is HP’s strategy moving forward with HP e3000 servers?

A: Our commitment to HP e3000 and MPE/iX operating system is to continue delivering on the roadmap we have already communicated, delivering the planned performance and functionality, with future MPE/iX releases in the 2002-2003 timeframe. Moving forward, we are focused on moving HP e3000 customers to IPF-based HP servers that deliver more benefits to the customer, using aggressive and innovative migration programs.

Q: Does HP plan to port MPE/iX to IPF-based platforms?

A: No. MPE/iX will not be ported to Itanium-based servers. The communicated HP e3000 roadmap includes PA-RISC based servers that deliver the performance and functionality customers need in the 2002-2003 timeframe. After that, HP e3000 customers benefit more by moving to HP Unix Servers using Itanium technologies and best-in-class migration programs, and taking advantage of the industry leading performance, functionality, and lasting value that Itanium and HP-UX will deliver.

Q: Should HP e3000 customers who need to stay longer on the platform than 2004 be concerned?

A: Absolutely not. HP will support the servers at least until the end of 2006. During this time, HP is committed not only to provide full support for the servers, but also to make available the aggressive and innovative migration programs, to help customers successfully move into Itanium-based HP-UX servers on their own pace.

To recap, the end of 2006 became the end of 2010, in part because HP's aggressive and innovative migration programs were undermatched to the needs of the customer. The Itanium technologies became an also-ran, lapped by Intel's modernization of x86 processors. Intel announced its departure from Itanium futures in 2015. Now commodity hardware rules the roost in today's mines.

Photo by David Clode on Unsplash


HP still keeps MPE data behind a paywall

Payphone
Photo by John-Paul Henry on Unsplash

It can be surprising to see how much value remains in an operating system that's not been altered in almost a decade. Hewlett Packard Enterprise has 3000 documentation on its website that is still behind a paywall of sorts. Users access this info by validating their HP Passport credentials — the ones that indentify the user as being current on a support contract.

The HPE website has plenty of advice and instruction available without a validation. If you ask, for example, "Can the HP 3000 and GSP LAN configuration be on different subnets?" HPE reports

There are two server platforms (A-CLASS [A400/A500] and N-CLASS [N4000]) that can run MPE, which uses the GSP (Guardian Service Processor) console for offline hardware operations like startup and shutdown of the system, access hardware console or system logs, etc.

It is possible for management purposes to place the GSP operation on a different subnet from the MPE server LAN, thus isolating or protecting either environment from one another. One reason for that can be to prevent normal users from telneting or in other ways accessing the GSP console or the other way around.

Or, another morsel that's useful in the era of declining hardware know-how: A-Class IO path memory configuration guidelines. Useful for the manager who's trying to set up memory cards in one of those $5,000 replacement 3000s.

However, if you'd like to read the most current documents, a support contract stands in the way. An updated NMMAINT listing is behind the paywall. HPE created the document in August of 2019. There's no available support to be purchased from HP for MPE/iX.

The documents that survive can be extensively redacted. A HP3000 License Transfer Process document references a web address no longer in service. The address licensing.hp.com no longer answers to requests.

Some information on MPE/iX at HPE's website is among the 4,386 documents at the site. Having the confidence that it will remain in that place is the next step in learning to rely on HPE resources. Independent MPE/iX resources have been more reliable, although the web pages for MM Support went dark this year.


Xerox HP fight copies 3000's exit saga

Copier user
Xerox has been trying to buy the part of HP left over after the vendor's split up in 2015. The latest $33.5 billion offer, rebuffed by the HP Inc. board, is going to get pushed out to the HP Inc. shareholders. "It's a better deal that you're getting now" is the message to the thousands of HPQ stock managers. Voting shares for or against a merger has a spot in the 3000's legacy.

This is also the outcome that helped cement HP's exit from the 3000 world. In 2002, HP's acquisition of Compaq got pushed out to a proxy battle. Xerox says HP is defying logic by refusing to be acquired. That's the kind of resistance HP loyalists — the HP blue, they were called — tried to muster around Bill Hewlett's son, who was an HP board member.

Without that successful buyout, HP would've had no Digital VMS customer base to court and invest in to feed a business-focused Itanium operating system. HP-UX was a lock for Integrity, to be sure. The 3000 and MPE/iX were there, ready, but just too small for HP's designs on being Number 1 in all of computing. The Compaq PCs were going to make that a reality.

However, about three years after HP rammed through the Compaq merger through a proxy battle, the spark of that deal Carly Fiorina was forced to resign as HP CEO and chairman. PC growth had not contributed to significant HP market dominance. At the same time, the health of its enterprise business began to slip ever so slightly.

Another CEO pumped up HP's sales, even while its ability to sell OpenVMS and HP-UX faltered. Enterprise computing with HP-built operating systems was in decline. HP became an all-Windows enterprise supplier when full business server sales were measured.

The juicy fruit that HP's board dangled in front of uncommitted shareholders was Compaq's roaring PC business. A combined company would be No. 1 in market share almost immediately. That was promised, anyway. The fortunes of OpenVMS seemed secure, heading into the portfolio of a technology giant that had enterprise legacy to match Digital's.

By 2016, OpenVMS was in the chute toward ex-product status at HP. The coup de gras took place this year when VMS support customers were told the future was in the hands of VMS Software, Inc. OpenVMS users, as well as the MPE customers who were the casualty in that 2002 merger, can look at Xerox and watch the conflict knowing it won't change their fates.

Those were set in motion by the last proxy battle. The juicy fruit that HP's board dangled in front of uncommitted shareholders was Compaq's roaring PC business. The fortunes of OpenVMS seemed secure, heading into the portfolio of a technology giant that had enterprise legacy to match Digital's.

MPE customers were sent down the path where Tru64, another Digital creation, sits today. Formal support ended for them. However, MPE/iX was more than a new edition of Unix. It built a community around vendors. There was no other choice once that proxy war was lost.

Mergers are a good way to see where the soul of a company resides — if there's an open fight. Of course, there wouldn't be a shadow of the old HP to fight over — printer-PC HP Inc. — if the Compaq acquisition had failed. HP might be in the position of seeing itself absorbed and erased. A new afterlife seems unlikely for a company founded on something as common as Windows and printers.


Welcome to Year 19 of the Afterlife

Cheated Death on printer
You remember where you were, perhaps, on the day you learned Hewlett-Packard was done with MPE/iX. You might have been in a meeting, or checked your email before heading home. You might have been installing something a 3000 needed to keep serving your company, or even ready to order a new server to replace the old 9x8 box. Some unlucky vendors were holding orders for new systems.

People did all of that and more on the day HP revealed its 3000 era was on its way to a finish. By 2003 the community was calling the new era The Afterlife. The lifespan of building new HP 3000 hardware was ended when a box rolled off the line at the Roseville plant in early November that year.

Afterlife shirt

And so, on November 14 of 2001, the afterlife of Hewlett-Packard's lifetime started with dismay, anger, and then resignation. The five stages of death proceeded through discussions in a lively 3000 newsgroup. Taking a cue from the horrors of 9/11 in that season, programmers and vendors howled about the relatively unimportant death in their lives.

Doug Greenup was leading Minisoft in that November week. The CEO of a software company whose products were on thousands of systems, he became aware of the HP pullout with just one day's notice.

Alvina Nishimoto from HP called me. She was in charge of third parties with HP at the time. She asked me to sign a non-disclosure which she'd just faxed me. She said she had important news. I signed it and faxed it right back. She called to tell me HP was announcing they were discontinuing the HP e3000, and that HP-UX was their future direction.

HP might have been worried the story was going to get into the world without its influence. The news had been roiling through the 3000 community for more than a week before I learned about it. I'd been away on a vacation in Europe when I got the call from my partner Abby. HP wanted to brief me. Wirt Atmar, the founder of AICS and a 3000 stalwart, threw off the lid 10 days earlier about the pullout by posting to a developers' mailing list.

I spoke to two of our oldest, most trusted customers yesterday, one a ten-year customer and the other 15 years, about this upcoming announcement. Their first reactions were that it simply sucked their breath away. When I told them about HP's proposed plans of migrating their applications to HP-UX — which as an option has all of the practicality to them of trying to establish a penguin colony in Death Valley — their second reaction was "the hell with HP. If we move, it will be to anything but HP." I think that that's going to be the general reaction.

HP learned a great deal about ending a product line with the lessons that began 18 years ago. Earlier this year the company made a graceful transfer of responsibility for OpenVMS, sending the software as well as support opportunities to an independent firm, VMS Software Inc. HP won't sell any more OpenVMS licenses, although it continues to build Itanium servers that will run the apps created for that OS.

This was a vision that the HP 3000 community took to heart during the first of the 18 years that followed. A similar group of OS experts, organized and led by Adager, wanted HP to transfer the future of MPE/iX to new, independent stewards. HP didn't know how to do this in 2001 or in 2002. The offer took another form in the OpenMPE advocate organization, but eight more years had to slip past before HP's source code made its way into independent software labs.

A new history began 18 years ago today, a chronicle of a group of customers who kept their own counsel about walking away from a corporate computing asset. The next two years or so will show HP Enterprise customers what might have been possible had MPE/iX found a third party home. VSI is predicting that it will have production-grade OpenVMS ready for a late 2021 release on Intel hardware.

This is more than a shift away from the HP Enterprise resources. VSI is carrying OpenVMS to a new chipset, a commodity home. In 2001, Atmar told HP's business manager for 3000 operations, Winston Prather, such a move was what the 3000 customers deserved.

Opening MPE up and migrating it to an Intel platform offers at least some real hope for a continued and bright future for MPE. More than that, it keeps a promise that most customers believe HP has made to them, and that is very much the nub of the moral and ethical question that faces you now, Winston.

Migrating MPE to Intel hardware would have permitted MPE to run on inexpensive but high-quality servers. Earlier this month, VSI announced a timeline for such a thing to happen with OpenVMS. A different HP paved the way to that decision—a vendor perhaps chastened by the past—than the corporation that launched the 3000's afterlife.

In the beginning, the launch of this server took place during this month. The slogan at the HP 3000 lab in 1972 was "November is a Happening." Nothing can change what happened nearly 30 years later. But the VSI transfer shows the decisions over what to do with a loyal enterprise customer base have changed in the years since 2001's happenings.


HP's tech lures Xerox offer to buy

HP printer tech
Photo by Dario Seretin on Unsplash

Plenty of writers and customers get confused about the HP of 2019. Back in 2014, the corporation split into two units, operations that align on devices and datacenters. Hewlett-Packard Enterprise now sells datacenter products and services. It's the arm that created HP 3000s in the 1970s. HP Inc., the part of the company that makes printing, imaging, and PC products, received an offer this week to be purchased by Xerox.

HP Inc. acquired 55 patents from Samsung for business printing not long ago. Now the corporation is being courted by a suitor whose printing legacy is wired deep into the DNA of Hewlett-Packard's spinoff. Patents for LaserJet tech, the engineering that in 1984 took HP into the realm of resellers farther removed from HP than any 3000 VAR, are part of what Xerox is bidding for.

The offer, which HP Inc. confirmed it has received, would sign up Xerox for more than $20 billion in debt, financed by Citigroup. The appetites of the HP which created the 3000 and then cut down the vendor's future in the MPE/iX market helped to spark that 2014 split. HP was striving for an overall Number One status as a technology supplier in the years just before it announced its takedown of its 3000 business.

Management at the vendor aligned on growing sectors of business. While the 3000 had enjoyed a nice revenue increase for several years leading up to Y2K, HP saw the unit as one whose growth had a limited future. "If it's not growing, it's going," one 3000 vendor said he'd heard in reports about HP's future.

This was in the era when PCs were soaring on the HP balance sheets and printer products were being sold in groceries. The corporation had just acquired Compaq and Compaq's Digital group, so while there was a future for OpenVMS and its growth, cutting back on enterprise products became essential in HP's strategy.

Xerox developed the first viable graphical interface technology in its Star systems. The Palo Alto Research Center's tour for a young Steve Jobs at Apple led to the mouse interface becoming an essential part of the Macintosh release. 

In a move that proves there's always value in technology that outlasts its creators, there's now a deal in the market to return some of HP business technology to a corporation that's been a part of business computing history since the 1980s. It can be hard to tell what's going to survive in computing and where it will land. HP Inc. recently announced it will be cutting 9,000 more jobs. Betting on good management is at least as important as betting on good technology. As 3000 owners know, technology like MPE/iX is able to outlive the interests of its creators.


Wayback Wed: Leaving a Wake on an exit

Chris Gauthier  Jackie at Wake
Simpkins  Nizzardini  Johnson Wake redux
Above, a 2019 commemorative lunch today at Tide Mill Café in Hampton, VA with Terry Simpkins, Al Nizzardini and Tracy Johnson, all 3000 experts and veterans of MPE. 3000s are in use at their company, TE Connectivity. At top, a 2003 World Wide Wake picture with Chris Gauthier and his co-worker Jackie Mitchell, both supporting 3000 customers as contractors to Terix.

Today we're marking the 16th anniversary of the World Wide Wake. The event was a marker of the end of HP’s 3000 manufacturing on Oct. 31, 2003. Alan Yeo, who passed away recently, organized the Wake and posted photos contributed from attendees onto what we were still calling the World Wide Web. A Web gallery for 3000 people was groundbreaking at the time.

Yeo said back in 2004, a few months after the event that drew more than 400 devotees to meetings in 15 countries, “We have created a simple single Web page that by country just lists the venues and who attended, and also has a link to any pictures for that venue," Yeo said. “The information will be condensed into a single Web page, linked to a directory of about 75 images. We have had several offers to host the information, so rather than try and pick a single host, we thought that allowing any interested attendee to host it would be best.”

Thanks to good Web hunting from Keven Miller, the Wayback Machine link to the original Web page tells the tale of who attended, and where, along with some of the photos.

Our own archive of the photos, sans captions, is here on the blog.

The photos from that day look like party pictures, even though nobody in them was celebrating anything except Halloween. The memories were on the minds of everyone in the frame, though. The future without any more new 3000s didn't seem to scare anyone on that day, at least not for the cameras. It was a coincidence that the building of new computers, as well as the licenses for the MPE/iX that made the boxes genuine 3000s, stopped on the spooky holiday. HP's fiscal year ends every year on October 31.

The Wake gatherings were all across the globe. New Zealand was the furthest away from the Epicenter of Grief, as the 3000 faithful had dubbed Lori's Little Shack in Roseville, the town where HP's 3000 factory was ending its birth of the servers. 

Loree's Epicenter Grief

Continue reading "Wayback Wed: Leaving a Wake on an exit" »


Who's to blame when the lights go out?

Power-lines-towers
Photo by Peddi Sai hrithik on Unsplash

Yesterday the lights didn't come on in Northern California. Everywhere, it seems, because the Pacific Gas & Electric corporation didn't want to be sued for windstorm damages to its power lines. They cut the juice to prevent lawsuits. Tesla owners got a dashboard warning.

The surprise about the outage was as complete as the shock over Interex dowsing its lights overnight in 2005. Except the cynics could see the PG&E blackout coming.

Solar panel-owning residents of California and electric car owners were most surprised. I went to a 3000 tech mailing list to look for people worried about topping up their Teslas, because some people who picked 3000s are pioneers, so Teslas are well represented among MPE veterans. Like the usual chaff on a mailing list, there were turds of political opinion floating there about who's to blame for California's darkness.

So I wasn't surprised to see more attacks on the state of California. "A third world country" is the shorthand smear, although you can say lots of the US isn't a first world country any longer. In the exchange on the mailing list, it was apparently too much trouble to keep a state’s government separate from talk about Pacific Gas & Electric’s corporate moves. Once PG&E goes bankrupt, then the private corporation’s demise will be blamed on California voters, using that logic. It’s easier than keeping commerce and government separate, I suppose. 

Blaming the tough regulations about state rate hikes for the disaster that is PG&E business is having it both ways: Government is crucial, and government is ridiculous. On and on it goes, until we are supposed to trust a government that lets PG&E do whatever it wants, so long as profits stay high. 
 
Because every corporation with ample profits has always taken care of its customers in every need. 
 
Some people on that mailing list sure have a short memory about such nonsense. We are all survivors of a meltdown of a business model where corporate profits were ensured — because revenue growth was the only thing that mattered — while legacy technology got scrapped. Millions of dollars of investments, the fate of hundreds of vendors, and thousands of careers were lost.
 
The mailing list name still has the numerals 3000 in it. You’d think people would remember what brought us into each others' lives, along with the lesson we learned the hard way together. Oversight is important. The problem which hit the Hewlett-Packard 3000 customers was a lack of oversight from top-level management and the board of directors. It's sometimes hard to know what to do while things are changing (the computer business) and ambitions are high (make HP bigger than anybody, so it will win every deal).
 
A good rule to follow, though, is like a physician. First, do no harm. The 3000 community got treated by HP like a limb that had gone gangrenous. Old history that'll never be changed, yes. Also, a lesson for managers on how to treat older bodies like an operating system and software that's not new but is still performing well.  
 
Complaining about oversight, when you'd rather have none at all, is what got HP into the state it's in today. Two corporations, neither growing, both unable to honor the promises of forever-computing that drove companies to buy its products. HP's cut itself loose from the future of OpenVMS, and the thousands of companies that rely on that legacy OS need to trust VMS Software Inc., new owners of the OS's future.
 
It's a better deal than the one HP gave its 3000 customers. Private money would've taken over MPE futures in 2002. HP wouldn't sell or license it, but again, that's just history. Now that the lights aren't going on for the 3000 at HP anymore — so many of HP's 3000 web pages are dead or buried alive — it evokes the powerless situation in California.

Continue reading "Who's to blame when the lights go out?" »


Relative performance online as 3000 history

Snapshot of partial HP relative performance
As the HP hardware to run MPE/iX ages, it's on the recycling and scrapping block for companies that still have an HP 3000 box on-premise. Now hardware is so cheap you can throw 3000 gear away.

The slow, old, and heavy boxes go first, of course. I remember taking a trip with Stan Sieler in the Bay Area where he took me to a scrap facility. There, shrink wrapped on the outside of a pallette, were HP 2645 terminals, right alongside Compaq boxes.

Relative performance charts can be our friend as we triage our older HP gear. There's an adequate one available online at bitsavers.org as part of a breezy page covering the history of the 3000. 

We've got The One Chart to Rule Them All you can download to use while you have HP's gear on the chopping block. There's a section for A-Class comparisons, and another compares HP's boxes in the N-Class line to older system performance.

Such numbers are relative in more ways than just the comparison between servers. HP actually massaged the numbers themselves back in the late 1990s. Our story in 1998 reported that 

HP is “restating” the performance rankings for much of its hardware, starting with this month’s rollout of the Series 989 systems. The new rating is an HP 3000 Performance Unit, not based on Series 918 performance. And the new numbers are between 29 and 52 percent higher for all systems except HP’s largest ones, the Series 996 and 997 units.

As I observed, while looking askance at the new figures, "HP wants you to think of HP 3000s as faster than ever, but its new rating measurements don’t really make existing systems any faster. They just sport higher numbers than they did last month."

There was some technical logic to the HP adjustment. The 3000 hardware from HP had just acquired some newer and faster cousins.

Dave Snow, product manager for the 3000, said "the measuring techniques for our midrange and high-end platforms were producing results that were not consistent with each other. You had a 918 performance for the midrange and a different relative performance for the high end, but the two relative performance numbers weren’t the same.”

The discrepancy was a big deal, he added, “but it was a big deal we could sort of live with, so long as the 9x9 and 99x performances were dramatically different from each other,” Snow said. “As we added performance to the 9x9 platform, it is approaching the 99x. That’s caused us to have this quandary. In some sense we’ve had two different sets of 918 numbers. We had to bite the bullet and reconcile the numbers."


Two very tough days for 3000 customers

Punch-to-jaw
July 18-19 isn't a date that lives in infamy like November 14. The latter is the date HP announced it was leaving the 3000 customers to find their own futures. The former is a pair of days in 2005 when a 31-year-old user group died, followed by HP's announcement of a layoff of 10 percent of its workforce.

That's a one-two that rocked 3000 shops still trying to concoct a transition plan toward their next computer platform. First, the storied resource of 3000 know-how switches off the lights without warning, freezing up things like a Contributed Software Library. Then 15,000 HP staff including some one-of-a-kind experts in MPE, got their termination orders.

By this July week of 2005 HP had done good work for the 3000 customer, in the form of promises, intentions, and plans, much of it by people in what was called Virtual CSY.  The layoffs didn't help any of those intentions, or reinforce the business decisions that could still make a difference to a 3000 customer.

HP's layoffs happened so long ago the vendor made the announcement before the stock market opened. That would be a post-trading news item today.

Interex, on the other hand, made an announcement that sounded like it was written standing over a terminal before someone cut out the power to the office.

Dear members:

It is with great sadness, that after 31 years, we have found it financially necessary to close the doors at Interex. Unfortunately our publications, newsletters, services, and conference (HPWorld 2005) will be terminated immediately. We are grateful to the 100,000 members and volunteers of Interex for their contributions, advocacy, and support. We dearly wish that we could have continued supporting your needs but it was unavoidable.

Interex

Your community reacted with resignation and invention. There was no panic or an accelerated drumbeat of exiting the 3000. In fact, just a few months later HP announced it was extending its exit date— and adjustment in plans triggered by the fact that customers had no intention of being done with MPE/iX by 2006.

In San Francisco, where many an airline ticket was already booked with no chance of a refund, the 3000 team decided to hold a last supper for user group conferences.

Continue reading "Two very tough days for 3000 customers" »


Wayback: Security boosts as enhancements

Booster-seat
They weren't called enhancements at the time, but 13 years ago this month some security patches to MPE represented internal improvements that no company except HP could deliver to 3000s. Not at that time, anyway. This was the era when the 3000 community knew it needed lab-level work, but its independent support providers had no access to source code.

Just bringing FTP capability up to speed was a little evidence the vendor would continue to work on MPE/iX. For the next few years, at least; HP had halted OpenMPE's dreams to staff up a source code lab by delaying end of support until 2008. The vendor announced a couple more years of its support to 3000 customers.

In doing that, though, HP made an assignment for itself with the support extension, the first of two given to the 3000 before the MPE lab went dark in 2010. That assignment was just like the one facing today's remaining HP 3000 customers: figure out how to extend the lifespan of MPE expertise in a company.

FTP subsequently worked better in 2006 than it had in the years leading up to it. It's not an arbitrary subject. FTP was the focus of a wide-ranging online chat in May. Did you know, for example, that FTP has a timeout command on MPE/iX?

The connection time-out value indicates how long to wait for a message from the remote FTP server before giving up. The allowable range is 0 to 3000. A value from 1 to 3000 indicates a time-out value in seconds. A value of 0 means no time-out (i.e., wait forever). If num-secs is not specified, the current time-out value will be displayed. Otherwise, this command sets the connection time-out to num-secs seconds.

When an FTP job gets stuck, using timeout can help.

MPE/iX engineers and systems managers were working more often in 2006 than they do today. When anybody who uses MPE/iX finds a 3000 expert still available, they need to get in line for available work time. It remains one good reason to have a support resource on contract. A company relying on a 3000 shouldn't be thinking a mailing list or a Slack channel represents a genuine support asset. Even if that FTP tip did arrive via the 3000-L.

The resource of good answers for crucial questions gets ever more rare. The 3000-L mailing list has rarely been so quiet. There are information points out there, but gathering them and starting a discussion is more challenging than ever. File Transfer Protocol is pretty antique technology for data exchange. It turns out to be one of the most current standards the 3000 supports.

Continue reading "Wayback: Security boosts as enhancements" »


Compromises throw doubts about clouds

Thunder-cloud-3554670_1920

Cloud services show some promise for companies which are dropping their on-premise IT hardware to get costs down and put maintenance in the hands of service companies.

As the HP hardware ages, its reliability becomes a weak point. There’s a risk to using clouds, though, one that the 3000 community knows well and holds dear.

Outside services can be vulnerable to security attack. When the attack takes place outside a datacenter, the responsibility falls to the manager who selects the service.

A hacking campaign known as Cloud Hopper has been the subject of a US indictment, one that accused Chinese nationals of identity theft and fraud. Prosecutors described an operation that victimized multiple Western companies. A Reuters report at the time identified two: IBM and Hewlett Packard Enterprise.

Cloud Hopper ensnared at least six more major technology firms, touching five of the world’s 10 biggest tech service providers. Reuters also found compromises through Fujitsu, Tata Consultancy Services, NTT Data, Dimension Data, and Computer Sciences Corporation.

Another compromise pathway was DXC Technology. HPE spun-off its services arm in a merger with Computer Sciences Corporation in 2017 to create DXC. HP's Enterprise group represents one-fourth of all the known compromised Cloud Hopper attack points.

Assurances that a cloud is secure come with references, but the degree of safety remains largely in the eyes of the beholder. There’s not much in the way of audits and certifications from independent reviewers. MPE cloud computing is still on the horizon. Reports about unsafe clouds are helping to keep it that way.


Being there now, right where we expect him

Birket-Chamber
Where Are They Now
?

Fifteen years ago, Birket Foster had an opening line for a history of the 3000 world. "It was a marketplace of names." Birket's is one of a group of well-known first-only names, along with Alfredo and Vladimir and Eugene. Earlier this spring he commemorated 42 years in the market. Every one has included a week of business serving HP's business server community.

In a few days he'll be doing what he's done, and in the same places, as he's done for years. There's a webinar that covers the promises and practices of application modernization and synchronization. Systems that look and behave like they're old are made new again. You can register for the June 12 event, to be held at 2 PM Eastern.

Right at the heart of the MB Foster business, though, pulses UDACentral. "We have completed its shakedown cruise at the Government of Canada in a BCIP program, and of course are moving another group of databases for customers that contract MBFoster to do the work using UDACentral."

Moving and managing data has always been at the center of MB Foster's competency. "We have been adding databases to the mix: Aurora (for AWS) and MongoDB are now part of what we are serving. We even did a paid Proof of Concept for UDASynch taking MongoDB back to Oracle."

The company's core team has been steady, but what's ahead is pushing UDACentral's wide array of improvements "to change them from a project to a product. That process will need additional sales talent and trainers, as well as more support and programming talent, so my hobby is expanding again." That's a hobby of assembling resources for new ideas.

In the meantime there is family life for Birket, the pleasures of two daughters and a son already old enough to be expanding and embracing lives in medicine and business, as well as building families of their own. Fishing the Ottawa River's massive muskies remains a passion, one he's pursuing this summer with HP 3000 tech guru Mark Ranft. Birket often has a hook in the water.


Third parties take over HP's OS support

Aircraft-instrument panel
The above headline doesn't describe a new situation for MPE/iX. HP gave up on its 3000 support, including MPE/iX, at the end of 2010. Even allowing for a few shadow years of 3000 contract completion — the time when some support contracts were running out their course, and HP ran out the clock — it's been a long time since the 3000's creator supported a 3000 system.

That's a situation that's about to kick in for the hundreds of thousands of VMS systems out there. HP's official OpenVMS support ends in December of 2020. A third party company, VMS Systems Inc., has earned a license to support VMS using its internals knowledge and experts. The company, VSI, will also become, by July, the only outlet for an OpenVMS customer to buy OpenVMS.

The 3000 customers already know how well third party support can succeed. VMS customers in the US government are going to learn how well it works for them. The Federal business in VMS was big.

This third party stewardship and development was the spot the 3000 community could never reach. The OpenMPE movement began as a way to get a third party group the access required to advance MPE/iX with features and new patches. That ground along for more than three years until HP announced it was extending its 3000 "End of Life" in 2005. The air quotes are needed before the only life that was ending was HP's life serving 3000 owners.

So any takeover of MPE/iX internals for extension and future customers' needs was out. So it then fell to the community to ask for enough access to do deep repairs and issue patches. Ultimately that license was created, sort of. Not the kind of access that VSI got for VMS. Just enough, for the seven special companies with an MPE/iX source license, to repair things for existing support clients.

It amounted to a CD with the millions of lines of internal MPE/iX code. The documentation was limited to what was inside the source file, according to some who saw the CD. One report said it was a $10,000 license.

That MPE/iX source goes above workarounds. Lots of the potential from extra source access has not been tapped after all of these years. But good customer-specific fixes have been built.

This is so much less than what the VMS community — which was in the final analysis what helped end HP's 3000 life — is getting now and in the years to come. Lots of years, because like the 3000, the VMS systems have Stromasys virtualization.

Because the VMS community was so much larger than the MPE community during 2001, and VMS had extensive government installations including Department of Defense sites, VMS won out. VMS got the engineering to support Integrity-Itanium servers. In the long run, we can all see how that mattered. Intel announced the final Itanium build this year. Some wags call the architecture the Itanic.

Many, many VMS sites remain. Everyone estimates, but it's easily a group bigger than the 3000 community ever was. Third party support is all that the OS will have in about a year and a half. That support resource, from independents like Pivital Solutions, been good enough for the 3000 for more than eight years since HP's support reached its end of life.


Itanium, we hardly knew ye, aside from HP

Titanic
Earlier this month, the computer community learned how late in life Itanium was living. The chip architecture was going to rule the world when HP and Intel first announced it in 1994 as a project called Tahoe. Intel ruled the world with x86 architecture then in the lion's share of PCs. Literally, as in the true definition of lion's share: all of it. 

It's taken 25 years, but Intel has called Time's Up for its design it co-created with HP. Intel told its customers that the final order date for Itanium 9700 series processors is January 20 of next year. The final Itanium processor shipments end on July 21, 2021.

Itanium was essential to the HP decision to stop manufacturing HP 3000s. Itanium was going to be the future of all enterprise computing, the company figured right after Y2K. There was not enough money in the R&D budget at HP to fund the redesign of MPE/iX for a new processor. VMS, sure, HP would do that for a market that was four times the size of MPE/iX.

By now HP has split in two and Itanium is nowhere but in the HP Enterprise servers, the ones running VMS and NonStop. HPE says it will support its Itanium-based Integrity servers until 2025. A superior article in the the EE Journal includes this summary.

Itanium’s developers sought a path to much faster processing. Unfortunately, the theory behind Itanium’s development was just plain wrong. While VLIW architectures do appear to work well for specialty processors running well-behaved code, particularly DSPs, they’re just not appropriate for general-purpose applications thrown willy-nilly at server processors.

And so, we remember the fallen.

It's taken awhile to understand the inertia that occupies the energy of the computer industry. HP seems to have a side of itself that learned such lessons more slowly than most enterprises. HP was late to Windows (who needed GUIs?) and got well behind the pack on the Internet (Sun crowed over HP's sluggish pace by the late 1990s.) After creating its own RISC chip in PA-RISC, HP figured that another chip developed along with the creator of the x86 was a slam dunk. 

There was a time for dictating the way forward in computing with a new architecture for chips. That time passed well before Y2K. HP hung on for more than a decade in full denial, even as it revved up the ProLiant enterprise servers using x86.

It's not easy to see a clean future in the years beyond 2025 for the companies which are invested in Integrity systems. But no one could see how the PA-RISC servers of the 3000 were going to be anything but a write-off for their users, either. The strength of the operating environment, as well as a long history of efficient computing, gave the 3000 a longer lease on life. Now's the time to see if the HP-UX and NonStop environments are going to make the jump to x86. We're also watching how well they leap and what the HP of the 2020's will say. 

Continue reading "Itanium, we hardly knew ye, aside from HP" »


Driving a Discontinued Model with Joy

Volt
When a chariot has stopped rolling off the line, it might well be the time to buy one. That's what happened to me, unexpectedly, this weekend. I felt a kinship with HP 3000 owners of the previous decade as I weighed my purchase of a new car.

Like the HP 3000, my 2019 Chevy Volt was the ultimate model of a superior design and build. The Volt was Chevy's foundational electric vehicle when the vehicle made its debut in 2011. Back in that year it was costly (true of the 3000, even through most of the 1990s) unproven (MPE/XL 1.0 was called a career move, and not a safe one) and unfamiliar — plugging in a car inside your garage might have been as unique as shopping for applications knowing every one would work with your built-in IMAGE database.

The Volt grew up, improved (like the final generation of 3000 hardware, A-Class and N) and gained a following I've only seen in the best of designs. People love this car. There's a Facebook group for Volt owners, many of whom crow and swagger as they point out things like the intelligence of the car's computer systems or the way that an owner can train a Volt to extend its electric-only range. The latter is a matter of how often the car is charged plus a combination of a paddle on the steering wheel, a gear range, and the right driving mode. H is better sometimes.

Yes, it's as complex as any intrinsic set tuned for a bundled database. The Volt's efficiency rivals the best aspects of a 3000 at the start of the millennium. GM, much like HP, decided the future of the car would not include manufacturing it. Just as I was poised to purchase, after healthy research, I learned its sales had been ended. 

The Facebook group mourned, and one owner said the car would be a collector's item someday. That's when I thought of my 3000 bretheren and signed up for six years of Volt car payments. I had the full faith of two governments behind me, however. Both the US and Texas wanted to reward me for buying something so efficient. That's how this story diverges from the HP decision about the 3000. It was the resellers, as a private group, that made those last 3000s such a great deal.

I remember when the HP cancelation was announced, Pivital Solutions was still in its first 24 months of reselling the 3000. The company remained in the business of shipping new hardware as long as HP would build new systems. Ever since that day in 2003, Pivital has supported the hardware and backstopped the software. Pivital is one of the Source Code Seven, those companies which have licenses to carry MPE/iX into the future.

Pivital and a few others in the community sealed the deal on 3000 ownership in the post-manufacturing era of the computer. No matter how long you decided to own a 3000, you could get a support contract on hardware and software. GM is promising the same to me, for the next 10 years. After that, I'm in the wilds of great fandom and aftermarket service. Your community showed great confidence in that kind of era from 2004 onward.

Continue reading "Driving a Discontinued Model with Joy" »


Long-time MPE licensees leave dates in dust

Date book
I went to a birthday celebration for Terry Floyd yesterday as part of a Super Bowl party. You may begrudge them the kudos, but congrats to the Pats, who once again executed like the MPE applications still running this week in businesses around the world. Not flashy, like MPE, but every day brings no surprises. That's a very good thing for enterprise computing, and always has been.

Floyd's turned 70 -- he’s the guy who started The Support Group here in Austin to serve MANMAN 3000 customers. One of those customers was in town to celebrate. Ed Stein spent years managing MANMAN at MagicAire, a Carrier subsidiary.

That corporation is still using MPE, even after Ed has gone. He’s moved into the interesting fields of independent support and consulting on MPE. He mentioned he's available to the community's 3000 owners looking for MPE talent. Along the way he's developed his experience on the prospects for keeping dates nine years from now in MPE.

It was Stein's intentions for prepare for the 2027 date keeping changes that led several companies to spin up services and strategies for date-keeping in 2028 and beyond. What was mumbled about in private became more public offerings and strategies. During a conference call among MANMAN managers late in 2017, Floyd and others talked about how much work it will be to keep dates straight in an era HP never planned for.

Stein says that in his travels though the community he’s still running into many a 3000 user who’s got no idea their OS will stop making accurate dates in less than nine years. He also made reference to Beechglen and its 2028 patch service. Like everyone else who's using HP's MPE source code licenses, Beechglen cannot sell a product to patch MPE/iX. HP was never going to sell permission to create patched versions of MPE/iX.

Seven companies paid HP $10,000 each to become the source code licensees about nine years ago. At the time, the 3000's operating environment felt like a long shot to feel its age and forget its date-keeping skills. The server was 18 years away from a date that no working MPE server would ever see, right?

Don't look now, but 2027 is gaining on the community. Floyd was one of several developers who identified the scope of the work to make an app like MANMAN ready for the year 2028.

Some customers will get readiness for 2028 by becoming 3000 support customers. Any support company using the MPE source must package the repairs and improvements they develop as support offerings. There are a half-dozen more companies with source capabilities for MPE/iX. Getting a relationship in place with them will be on some to-do lists for 2019. Even the companies without a clue about date keeping will eventually catch on to where the correct tomorrows are going to come from: solutions off the support bench.


Source code for MPE/iX: Security, by now

Blanket-Ad
Ten years ago this week the 3000 community was in a state of anticipation about MPE/iX. HP had an offer it was preparing that would give select vendors the right to use the operating system code. The vendors would have a reference-use-only license agreement for MPE/iX. No one knew whether the source would have any value, said Adager CEO Rene Woc.

Adager, the company whose 3000 products are so omnipresent they held a spot on the Hewlett-Packard corporate price list, believed there was potential for independent support and development vendors. What was far less certain was how far HP would let source go to solve problems for the 3000 community.

"Source code is important whenever these kinds of [vendors] have support from HP, which most of them do," he said in that month of 2008. But HP engineers can look at source, just as third parties will do, "and the answers won't come instantaneously. In the meantime, you have to get your business back on track, and I think that's what the customer is eventually interested in. It will be nice to have that additional [source code] resource — especially in the sense that it will not be lost to the community."

There was a chance that HP's source licensing terms would be too restrictive, "to the point where you say that you are better off not knowing, because then we're free to use all the methods we've worked with while we didn't have source." After getting a license to source, Woc added, "you might have to prove that you got your knowledge through a difference source than HP's source code. We will see."

That sort of proof has never been required. Not in a public display, at least. Source code, held by vendors such as Pivital Solutions and others, has been a useful component in workarounds and fixes. HP never gave the community the right to modify MPE/iX. This turned out to be a good thing, as it kept the 3000s stable and made support a manageable business for application vendors.

There was also the wisdom that the resource of HP's code would have to prove itself. At least it held a chance for rescue and repair.

The source code "is probably a security blanket," Woc said in 2008. "In that respect, it's good that it will be available, that they're starting to offer some things. We'll have to see what kind of conditions HP will offer in their license agreements." 

Having source access though a license did not automatically make license holders better providers of products and services, he added. "You cannot assume, even with good source code readers, that the solutions will pop up," he said. "A lot of the problems we see these days are due to interactions between products. So the benefit for the customer would be based more on the troubleshooting skills that an organization can provide."

"The basic resources [of source] won't make things better by themselves," Woc said. "It's a matter of troubleshooting." 


HP 3000 dream tracks close to virtualization

Railroad switches
An HP 9000 HP-UX virtualization product is in development. In that kind of design, a single Intel server with enough computing power (concurrent threads) could host both HP 3000 and HP 9000 virtualizations. HP had the same objective almost 20 years ago for its largest enterprise platforms.

Early in 1999 HP's Harry Sterling spoke at an all-day user meeting in the UK hosted by Riva Systems. Sterling, who'd retire before the end of that year, said a multi-OS server was within HP's vision for the 3000 and 9000 customers.

Sterling’s mentioned the possibility of running MPE, NT and Unix concurrently on the HP 3000 "sometime in the future." There was even the possibility of a “hot-swap” version of MPE alongside the production system. John Dunlop reported for us at the time.

The passing mention indicated that separate processors in one box would be able to run different operating systems. Sterling did suggest that a hot-swap version of MPE might be a valid use, so that there would be some redundancy with the live operating system.

This seemed to lead to the subject of more uptime. From these comments, it’s possible that HP is looking at allowing online changes to a hot-swap system and then just switching it over to achieve the so-called “magic weekend.” This is a system upgrade that occurs seamlessly and transparently to both the users and management.

That would be a dream not realized. Hot-swap didn't make it any further into the customer base than architect discussions. Sterling noted that in 1997 customers expressed concern about the future of the 3000. To counter that feeling and give the customers more confidence, he outlined in 1999 a five-year roadmap for the 3000.

Marketing was on board as well in that year that led to Y2K. It would take another 13 years before a multiple OS host for MPE/iX would emerge.

Continue reading "HP 3000 dream tracks close to virtualization" »


HP show offers something to Discover

HP Discover Madrid
Early this morning the new-ish HP, Hewlett Packard Enterprise, was connecting with its customers in an old-school way. The HPE Discover conference has been unreeling since Monday and today was the final day of three in Madrid. These kinds of events were once so remote it took a week or more to learn what was said. Now there's a live-streamed component the vendor mounts on browsers and over phones anywhere.

Whether there's anything worth a live stream depends on the C-level of the viewer. How to Tame Your Hybrid Cloud and The Future and Ethics of AI might be best absorbed by a CTO or some other CxO. On-the-ground solutions don't show up much in HP's livestreams. The most practical lessons usually came during sessions of the 1980s and '90s held in rooms where indie software vendors delivered chalk talks. Down on the expo floor the instruction was even more focused. A manager could get advisories on their specific situations.

That's part of what Stromasys is doing at Madrid this week. An application demo isn't a novel experience most of the time. Making commonplace hardware behave like proprietary systems can still be a revelation. Over in Hall 9 this morning, managers at Discover will see demos of a Charon solution that's got more than 7,000 installed sites, according to Stomasys.

More of those 7,000 sites are MPE/iX emulations than ever. The demos will operate on both on-premise servers as well as from the cloud. Stromasys likes to remind the world that its Charon emulates VAX, Alpha, and SPARC systems as well as the HP 3000. The vendor does this reminding in person at conferences in places like Madrid, like the Middle East, and it demonstrates its virtualization at VM World in the US, too.

Conferences like HPE Discover were once run by user organizations and funded by booth sales. It was a personal business in those days before the Web gave us everything everywhere. Today the personalization arrives at vendor booths with demonstrations for those who've traveled to ask questions. Having an expert on hand to answer them shows a committment to keeping new solutions on display.


It's always a red letter day today

You can use shorthand and say "November 2001." Or you can say the day that HP's 3000 music died. November 14 still marks the start of the post-HP era for MPE/iX as well as the 3000 hardware HP sold. It took another two years to stop selling the PA-RISC servers the company had just revamped with new models months before the exit-the-market announcement. PCI-based N-Class and A-Class, the market hardly knew ye before you were branded as legacy technology.

For a few years I stopped telling this story on the anniversary, but 12 years ago I cut a podcast about the history of this enterprise misstep. (Listen by clicking the graphic above) HP lost its faith in 2001 but the customers hadn't lost theirs and the system did not lose its life. Not after November 14 and even not today. Not a single server has been manufactured since late 2003, and even that lack of new iron hasn't killed MPE/iX. The Stromasys emulator Charon will keep the OS running in production even beyond the January 2028 date MPE/iX is supposed to stop keeping accurate dates. 

Red Letter Days were so coined because they appeared on church calendars in red. They marked the dates set aside for saints. In 1549 the first Book of Common Prayer included a calendar with holy days marked in red ink; for example, Annunciation (Lady Day), 25th March. These were high holy days and holidays. The HP 3000 came into HP's product line on a November in 1972. November is a Happening read the banners in the HP Data Systems Division. No day of that month was specified, but you might imagine it was November 14, 1972. That was a Tuesday, while the 2001 date fell on a Wednesday. A total of 1,508 weeks of HP interest.

Something important happened in that other November of 29 years later. Hewlett-Packard sent its customers into independent mode. Those who remained faithful have had a day to mark each year, logging the number of years they've created their own future. It's 17 and counting as of today.


Wayback: A month to download 3000 Jazz

Jazz-announcement
Ten years ago this month HP was advising its customers to get free software while it was still online. HP said that its Jazz web server was going dark because its 3000 labs would end operations on Dec. 31. Maintained by HP's lab staff, Jazz was being unplugged after 12 years. The software played an essential role in getting the 3000 into the Internet age. Eventually HP learned to market the server as the e3000.

Bootstrapping development fundamentals such as the GNU Tools, the open source gcc compiler, and utilities ported by independent developer Mark Klein had a home on Jazz for a decade. More than 80 other programs were hosted on the server, some with HP support and others ported and created by HP but unsupported by the vendor.

The software is still online 10 years later. Fresche Solutions, which began as Speedware, continues to host Jazz programs and papers at hpmigrations.com/HPe3000_resources. HP was clear in 2008 that customers had better grab what they needed before Jazz went unplugged. HP wasn't going to move the downloadable programs onto the IT Resource Center servers to doc.hp.com.

"Anything that people will need they should download before Dec. 31, 2008," said business manager Jennie Hou. "That's our recommendation."

The list of programs online is long and worth a visit for a 3000 manager looking for help to keep MPE/iX well connected to their datacenter. HP created more than a dozen open source programs which it even supported as of 2008. The list is significant.

• Apache
• BIND
• Many command files
• dnscheck
• Porting Scanner
• Porting Wrappers
• Samba
• The System Inventory Utility
• Syslog
• WebWise

Continue reading "Wayback: A month to download 3000 Jazz" »


Another If-Only Salvation, this time Linux

John Young Lulu
This man launched Red Hat out of a sewing closet, a firm that just sold for $34 billion. HP had a shot at buying Red Hat, too.

IBM announced it's buying Red Hat, paying an all-cash price of $34 billion to help make Big Blue relevant in cloud computing. While investors hated on the deal in the markets, others like Robert Cringley said it makes sense for Big Blue to own Red Hat. It's a color wheel that's spinning around IBM's enterprises. The ones that are the oldest might be those that stand to gain the most. It's the word "most" that reminds us how HP might have salvaged the future of MPE, if only with a deal to bring open source to enterprise customers.

One of my favorite readers, Tim O'Neill, sent along a message about RedHat + IBM. He said that this acquisition could have been done long ago—so long, in fact, that Hewlett-Packard could have executed it before the company stopped believing in MPE/iX. That would have been in the late 1990s, happening to a company that was deeply invested in two technologies just about played out today: Itanium and HP-UX. HP had faith enough in Itanium to stake its enterprise future for its biggest customers on the chips.

As for HP-UX, the OS that HP set out to devour 3000 opportunities, it remains to this day an environment that runs only on HP's architecture. HP used to snicker at Linux and open source options in those late 1990s. One presentation that sticks in my memory has an HP manager presenting a slide of a cartoon drawing of an open source support expert. He's a guy in a goatee slouching in a bean bag chair, mouthing "Dude" in a cartoon balloon.

HP meant to tell the audience that getting Linux support from HP was much more professional. Another message the cartoon sent was that Linux really was something dominated by open source nerds. Just about 20 years later the Revenge of the Nerds moment has arrived with a $34 billion payday. For some reference on that number, recall that HP gave up about $25 billion to purchase Compaq, a company with factories as well as labs.

HP used to have a slogan in the 1980s for advertising its PCs: What If? The IBM acquisition triggers the what-if thinking about Linux as in, "What if HP might have purchased the leading distro for Linux and used it to improve its proprietary environments' futures?" Would it have helped in any way to have a true open source platform, rather than just environments that were called "open systems?" The difference between an open source and an open system matters the most to developers and vendors, not to system makers. If Red Hat Linux might have helped MPE/iX look more open, at a source level, who knows how the 3000's prospects might have changed.

The melding and overlay of operating environments as different as Linux and MPE/iX had been tried before at HP, more than eight years before the company made its way away from the enterprise computing HP Way. In 1993 the project was HP MOST, one where I did some writing for Hewlett-Packard about a world where everybody could live together. Cats and dogs, Unix and MPE XL, all working together.

Continue reading "Another If-Only Salvation, this time Linux" »


Wed Wayback: India rises, California rests

HP-3000-lab-Bangalore-1995

As we rolled out the NewsWire 23 years ago this month we tracked a new element in the HP engineering lineup. Resources  Sterlingwere being added from India. By the time a couple of Octobers rolled past in 1997 we published our first Q&A interview with Harry Sterling. He'd just assumed the leadership of the 3000 division at HP, bringing an R&D lab leader into the general manager's post for the first time. Sterling was the best GM the 3000 ever had because his habits flowed from customer contact. The labs developed a routine with customer councils and visits as a major part.

SartainThat Indian element was integrating in earnest by 1997. MPE/iX development was a serious part of HP's work in Bangalore, India. It was becoming common to see India engineers giving technical talks at user group meetings. IMAGE lab manager Jim Sartain, who worked for Sterling, was essential in adding Indian engineering to keep the 3000's lab headcount abreast of customer needs.

Bangalore is more than twelve hours ahead of the time zone in California, the state where the 3000 labs were working in 1997. We asked Sterling about how he was integrating the Indian workers with his Cupertino CSY labs.

So the actual head count in CSY's California labs doesn't matter?

No. Our solution teams are made of engineers in Bangalore and in Cupertino. It's a virtual team. It's not like Bangalore does this set of solutions and we do that set of solutions. We don't carve it up that way because we have mirror images of the different projects.

Why is the Bangalore connection working as well as it is?

We've created an environment where our engineers have been able to establish personal relationships with the engineers at Bangalore. For example, they've often been there. One time or another over the last 18 months most of the engineers from Bangalore, at least certainly all of the leads, have been to Cupertino for some period of time. We have pictures of their whole organization in our hallways so we know who they are. We know what they look like. We know, in many cases, we know about their families and it's like another HP employee just happens to be on the other side of the world.

They're real people to us, a part of the team. And that's what's made it work for us. We don't just treat them like we've subcontracted some of our work to a team in India. There are some HP organizations that treat them that way, but we've had a much greater success. They are so proud to be a part of CSY. They have a big sign that says CSY Bangalore.

Continue reading "Wed Wayback: India rises, California rests" »


Wayback: HP's prop-up in a meltdown week

TradersTen years ago this week the HP shareholder community got a slender boost amid a storm of financial crisis around the world. While the US economy was in a meltdown, Hewlett-Packard -- still a single company -- made a fresh promise to buy back its stock for $8 billion. Companies of HP's size were being labelled Too Big to Fail. The snarl of the banking collapse would be a turning point for a Presidential election. A Wall Street Journal article on the buybacks called HP's move a display of strength. HP wanted to ensure its market capitalization wouldn't take a pounding.

HP was electing to pump a smaller buyback into its shares compared to a competitor's effort. Microsoft was announcing a $40 billion buyback in the same week. At the time, the two companies were trading at about the same share price. Hewlett-Packard was working through its final season with a 3000 lab, tying a bow on the final PowerPatch of the MPE era. One customer recently called that last 2008 release "MPE/iX 7.5.5."

The company was looking to get into a new operating system business in September of 2008, though. HP would be developing a server of its own built upon a core OS of Linux. HP closed down its Nashua, New Hampshire facility just a few months earlier. The offices where VMS was being revived were going dark. At least HP was still selling hardware and growing. We took note of the contrast between selling goods and shuffling financial paper.

Not all of the US economy is in tatters, despite what trouble is being trumpeted today. HP and Microsoft and Nike still run operations which supply product that the world still demands, product which can't be easily swapped in some shadowy back-door schemes like debt paper or mortgage hedges.

A decade later, much has changed and yet not enough to help HP's enterprise OS customers. VMS development has been sold off to a third party firm, OpenVMS Inc. That move into Linux has created a low-cost business server line for HP which doesn't even mention an OS. Meanwhile, Microsoft's stock is trading above $120 a share and HP's split-up parts sell for between $15 and $27 a share, covering the HP Enterprise and PC siblings.

Last week Microsoft announced an impressive AI acquisition, Lobe. For its part, HP Enterprise announced it was refinancing its debt "to fund the repayment of the $1.05 billion outstanding principal amount of its 2.85% notes due 2018, the repayment of the $250 million outstanding principal amount of its floating rate notes due 2018, and for general corporate purposes." A decade ago financial headwinds were in every corporate face. By this year the markets have sorted out the followers from the leaders. HP stepped away from OS software and has created a firm where sales of its Enterprise unit has gone flat. 

Stock buybacks offer a mixed bag of results. Sometimes the company doing the buyback simply doesn't have the strength and bright enough future to hope to reap some benefit—for the company. Shareholders love them, though. The customers are a secondary concern at times.

The $8 billion probably seemed like a good idea at the time, considering it was in the Leo Apotheker era and its misguided acquistions. (A deal for 3Par comes to mind, where a storage service vendor recently noted that it was Dell that drove up the 3Par acquistion price by pretending to bid for it.) The trouble with stock buybacks is just about nobody can stop them. Shareholders are always happy to have shares rise, either on the news of the buyback or the upswing over the next quarter.