Out on the 3000-L newsgroup and mailing list, a 3000 user who's cloaked their identity as "false" asked about using HPSUSAN numbers while installing the CHARON emulator product from Stromasys. The question, and a few answers, were phrased in a tone of code that suggested there might be trouble from HP if an illicit number was used. HPSUSAN is a predefined variable on a 3000, one that's used to ensure software is not illegally replicated or moved to another system without the software vendor's consent.
People have been talking about HPSUSAN for decades by now, even as far back as the Toronto conference that produced the proceedings cover above. A 19-year-old paper from that meeting -- the last one which was not called HP World -- still has useful instructions on the utility of HPSUSAN. More on that in a moment, after we examine what HPSUSAN does today.
On the fully-featured edition of CHARON for the 3000, a current HP 3000's HPSUSAN number is required. Stromasys installs this number on a thumb drive, which is then plugged into the Intel-based server powering CHARON. There's a 36-hour grace period for using CHARON if that thumb drive malfunctions, or comes up missing, according to CHARON customer Jeff Elmer of Dairylea Cooperative.
But the HPSUSAN process and requirement is different for the freeware, A-202 model of CHARON that can be downloaded from the Stromasys website. As of this spring, users of this non-commercial/production model simply must enter any HPSUSAN number -- and affirm they have the right to use this number. Neither HP or Stromasys checks these freeware HPSUSAN numbers. That model of CHARON software isn't meant to replace any production 3000, or even a developer box.
The freeware situation and installing strategy all makes the newsgroup's answers more interesting. One consultant and 3000 manager suggested that a number from a Dell server would be just as binding as anything from a genuine Hewlett-Packard 3000 server.
Mc Rae explained to us, and to a 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."
Nearly 20 years ago, HPSUSAN was not the focal point that it's become since the start of this century. HP 3000s had these numbers swapped and pirated by companies such as Hardware House in 1998 and 1999, and the civil suit and criminal investigations led to low-jack jail time and fines. Some software and service companies even chose to adjust their MPE plans after HP's legal moves. You could be in the right in this kind of circumstance, but not have enough legal budget to prevail in a court against HP. Better to keep a profile low and unquestionably legal.
Of course, that was a different HP than the one which now is scuffling to maintain its sales, as well as watching its Business Critical Servers bleed off double-digit percentage sales dips every quarter. Whatever the legal budget to defend BCS systems like the 3000 was in 1999, these kinds of servers are not HP's focal point. They do remain HP's intellectual property, however. And so, the coded language of today's exchange, starting with the question from "false."
How would one go about getting a HPSUSAN to be able to stand up a HP-3000 VM to play with? Just playing around--not intending anything, but it would be nice to see if I can do it. BTW, my budget for this project is approximately the price of a plain Einstein Bros Bagel with cream cheese.
If you know what an HPSUSAN is, then you should know how to get one. If you only offer a bagel and cheese, you're up a gum tree without a paddle. Since you need to hide behind a 'false' name, you are onto a hiding and burning your bridges at both ends.
What Tom said is true. I would suggest that an HPSUSAN is about the same as the Service Tag on your Dell. I would try using that.
If a 3000 customer has ever owned a server, they've got an HPSUSAN number on file. (It's in your Gold Book, along with all of the other configuration data and software vendor contacts. Sorry, that's 1990s thinking. HP used to issue these notebook binders upon system purchase.)
And if you still have the right to use this number -- for example, if your HP 3000 was scrapped instead of sold -- then there's a great place to start looking for a number to input while CHARON A202 is installed on that Linux-Intel laptop.
HP has not advised its customers about the utility of HPSUSANs from mothballed 3000s. Using Mc Rae's explanation above, 3000s were based on hardware ownership. If a 3000 has been scrapped -- sold for parts or just materials -- nobody else owns that server. The ownership rights don't revert to Hewlett-Packard, do they? This might be one reason for these coded replies. Nobody knows for sure, and like Mc Rae said, "MPE hardware and software was created before the technology of virtual systems and emulators."
Twenty years after the server was created, though, HPSUSAN was a topic that led David Largent to publish an Interex '95 conference paper entitled 101 (More Or Less) Moral Things To Do With HPSusan. You can read it at the 3K Associates archive website. In part, this is how Largent explained what HPSUSAN was meant to do.
The name is actually an acronym for the words "System Unique Serially Assigned Number." So what purpose does it serve? About the same as any serial number does. Software companies have found they can use HPSUSAN as a way to tie a particular copy of their software to a given machine, thus controlling software piracy. They simply request your HPSUSAN and include that in some validation logic in their program that prohibits the running of their software if the HPSUSAN from the system does not match the value in the software.
And so, CHARON requests an HPSUSAN number for the freeware version of its 3000 model. The only thing it requires would be the basic number format, as well as the integrity of the manager installing it. HPSUSAN matters to vendors other than HP, too.
Some of these freeware CHARON installations start out as pilot projects to ensure applications will run correctly. And some of those apps use software which employ HPSUSAN checks. But MPE/iX is not among that software. That's a decision that HP chose. Perhaps it was one small way to ensure that MPE users can keep their 3000 environments alive. First the pilot install, then a proper production-grade install of CHARON. They all need HPSUSANs. Some requirements, though, are more stringent than others. That's what a non-commercial license for a virtual 3000 will buy you -- installation through integrity.