All good points.  There is one minor correction I will offer, however.  The
stable storage that contains the model string and HPSUSAN is on the
backplane on most machines.  Only a backplane replacement would create the
problems you describe.  A problem that occurs more frequently is an upgrade
where you add additional processors, but the HPCPUNAME string does not
change to reflect it.  In that case you have to tell your software vendors,
"I need a license for a four-processor 9xx, but give me an activation code
for a two-processor one."

In the current environment, a replacement backplane can be submitted to HP
to have the stable storage updated as needed in a replacement situation.
Perhaps that service will still be available after the HP 3000 EOL, since
the capability will still be needed for the 9000's.  Depending on the
criticality of your applications, it might be advisable to have a
preconfigured backplane on hand in case of emergencies.  Third-party repair
organizations obviously deal with this contingency on a somewhat regular
basis.  Perhaps someone from one of those companies can tell us what, if
anything, they know about future plans.

-----Original Message-----
From: Wayne R. Boyer [mailto:[log in to unmask]]
Sent: Tuesday, April 16, 2002 10:48 AM
To: [log in to unmask]
Subject: Re: Software ID and Model string


In a message dated 4/16/02 10:19:34 AM Pacific Daylight Time,
[log in to unmask]
writes:


> Besides, the HP9000 has the same hardware. Releasing SSCONFIG might allow
> people to change the strings on HP9000's as well.
>
>

Paul: If I understand you correctly, you are supposing that SSCONFIG could
be
used by non-HP-3000 users (ie: HP-9000) to change around HP-9000
configuration settings.  That could be a giant problem for HP.  So how is HP
going to solve this? Does HP care about their customers or not?  Any HP-3000
system that was a CPU failure after end of support for that model is faced
with one of these four choices:

a) Replacing the CPU board with a used board from another similar HP-3000 -
if so then the HPSUSAN should at least be changed in order to allow some
software to run.

b) Replacing the CPU board with a used board from a similar HP-9000 - if so
then many firmware settings must be established in order for the system to
even boot up.

c) Utilizing a used replacement CPU board and dealing with whatever it has
stored in it's firmware AS-IS. Ie: change your third-party software, etc. to
accomodate it.

d) Scrapping the unusable hardware.

If everyone who intends to keep their HP-3000 running for at least a little
while after the end of support would look at the above choices... which one
do you want to do if you have a CPU board failure????  Remember: choices "a"
and "b" require SSCONFIG whch is unavailable!

Wayne Boyer
Cal-Logic

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *