« Free software worth the time to track it down | Main | Replacing apps: a migration option, or not? »

March 23, 2016

Putting a CPUNAME on HPSUSAN's profile

The MPE is a most unique creature of the computer ecosystem. This is software that does not have its own license, specifically. According to HP, the ownership of any MPE/iX version is determined by ownership of an Hewlett-Packard 3000 server, one built to boot up MPE/iX. When a copy of MPE is moved onto a Charon virtualized server, it must come from one that's been assigned to one of HP's 3000s. 

SusanWe reached out for clarity about this when a major manufacturer was looking into replacing HP's 3000 iron with Charon licenses on Intel systems. After the MPE/iX software is turned off on any replaced 3000 hardware, does its hardware-based license then expire? The operating system license, according to HP's MPE Technical Consultant Cathlene Mc Rae, is related to the HPSUSAN of the original HP hardware.

So wait a minute. Are these HPSUSAN numbers of 3000s considered de-licensed, even if they're going to be used on the Charon emulator? Mc Rae explained.

The HPSUSAN number is different from the MPE/iX license, although there is a relation between the two. The ability to use MPE/iX on the emulator is a result of completing a Software License Transfer. The original MPE/iX license on the HP e3000 would then no longer exist. 

In the hardware world of HP 3000s, HPSUSAN takes the original serial and model numbers on the system. It remains the same, as long as the customer owns the system. This combination was used to ID the hardware and enable diagnostics for the correct system.

However, that transferred license for the MPE/iX installation on the Charon emulator -- available via a $432 Software License Transfer Fee -- won't be getting a new HPSUSAN number during the process. HPSUSAN gets re-used, and so it leads us to see what HPSUSAN stands for, and how the HPCPUNAME is a key in emulator installations.

The U in HPSUSAN stands for Unique, as in System Unique Serially Assigned Number. Mc Rae said that HPSUSAN is one of a kind for HP-built 3000 systems. But SUSAN doesn't designate an MPE/iX license, even though MPE is licensed via hardware ownership. 

Mc Rae explained to us, and to any Charon prospective user, "MPE hardware and software was created before the technology of  virtual systems and emulators, in the 1970s. Licenses were based on hardware ownership."

This sounds familiar. HP once compared the licensing of MPE/iX to license plates issued for a car. They could not be separated, these numbers and the car that was the HP 3000 iron. (Let's just put aside the common practice of those metal-plate days, when they'd give you a new number after your plate was older than 8 years in Texas.)

In 1999, HP was busy suing Hardware House and a few other resellers over the resellers' separation of HPSUSANs from HP's 3000 hardware cars. The House was taking other PA-RISC servers and pressing valid HPSUSAN numbers onto the non-3000 iron. People went to jail. Lo-jacks were ordered for ankles.

Thanks to the passage of 17 years' time, an HPSUSAN number can now move to a USB thumb drive plugged into a Charon Intel- or AMD-based server. Those license plates can travel to a newer model of car. The emulator's HPCPUNAME, however, can only be designated as an A-Class or N-Class system, according to HP's knowledge. That'll likely be a reason to contact all software vendors whose products operate on the replaced HP 3000 iron.

You see, vendors use a combo of HPSUSAN and HPCPUNAME to control licensing. Products such as Infor's MANMAN or PowerHouse not only want to read HPSUSAN -- which you can move to Charon  -- but also HPCPUNAME. If you're moving off a Series 979, for example, "979-100" isn't an emulated system under Charon. No 979-100 for HPCPUNAME. You've got to get license permission from your software vendors to enable an A-Class or N-Class HPCPUNAME.

The HPCPUNAME on the Charon system may not be set to 979, Mc Rae said. "Based on the Charon HPA/3000 family, it is assumed that the HPCPUNAME will be set to an A-Class or N-Class CPUNAME," she said. "For example: HPCPUNAME = SERIES e3000/A500-200-50. As far as I know, Charon can only emulate A- and N-Class systems." That's true: a Series 9xx model isn't on the HPA/3000 product list.

The silver lining in this cloud is that you're only doing this contacting and CPUNAME-changing once. Moving to an A-Class or faster CPU from a 9x9 system is the last time you'll be changing from an unsupported CPUNAME to something included in the Charon product line. 

In short, independent software vendors are going to have to be contacted, if they've licensed their products with the HPCPUNAME-HPSUSAN combo on a Series 9xx. Contacting your software vendors about a system upgrade is a fair business practice. But it's more than the right thing to do. Series 9xx users headed to the emulator look like they need that refresh to boot up their indie software.

08:05 PM in Homesteading, News Outta HP | Permalink

Bookmark and Share

Use our search engine to find 20 years
of HP 3000 news and articles



The comments to this entry are closed.