WHOA! The HPSUSAN is stored in a PROM either on the Backplane or the the primary CPU
depending on the class of machines (Nova, K-class, Kittyhawk, yada yada). The HPCPUNAME is
stored in the same chip. BOTH can be changed by SSCONFIG, courtesy of your local HP CE.

Yes, it is a good idea to keep the HPCPUNAME up to date, yes changing it will cause some software
packages to fail, you will need new unlock codes from your 3rd party vendors if you change it and
possibly pay hefty upgrade charges if that puts your box in a new tier. I am aware of no 3rd party
package that senses the number of CPU's and decides whether to work or not based on that, they
basically limit themselves to HPSUSAN and HPCPUNAME.

Your system will sense and use an additional CPU automatically.

If adding a CPU puts your box in a different tier, you owe them money for support, if you are on it.
Otherwise, no, the HP police won't come break you door down.

Paul Courry



On Sat, 9 Dec 2000 02:03:48 -0500, Wayne R. Boyer wrote:

>Ok, here's my understanding of this subject:
>
>The HPSUSAN is derived from the physical serial number on the cabinet and
>should never change but CAN be changed via ss_config.
>
>The HPCPUNAME should change when processors are added (or subtracted) and
>is also set via ss_config.
>
>Either or both may be determined by some software and that software may
>then refuse to run.  I had a client with a 958 which had a 'null' in the
>HPCPUNAME field. Didn't show visually but was logically different from a
>blank space.  They had no end of headaches with that.
>
>I do not know if a system will sense and use or not use an
>additional/subtracted processor without a firmware change.  Worth knowing.
>Otherwise hardware changes get tied up with critical software changes.
>
>Now for the REALLY REALLY big question/issue: What legal "rules" does HP
>have (if any, and if so, written down where?) Is somebody violating a
>license agreement by plugging in additional hardware?  Anybody have any
>experience with that one?
>
>Wayne