Some for us here!

HPSUSAN is important for a lot of 3rd Party S/W. This can be kept.
HPCPUNAME should always reflect the real CPU type.

So you need to take into consideration to go for new License Codes of 3rd
Party S/W in advance  to be installed after the H/W change (e.g. MAESTRO.
JobRescue, et al.), assuming that the HPSUSAN will remain the same, and
knowing the new HPCPUNAME in advance (SERIES 995-600 e.g.).

Best regards, Andreas Schmidt, CSC, Germany





[log in to unmask] on 11/12/98 12:52:00 AM

Please respond to [log in to unmask]

To:   [log in to unmask]
cc:    (bcc: Andreas Schmidt/HI/CSC)
Subject:  Re: Changing the 'HPCPUNAME' variable




This should be done by the CE when the CPU upgrade is done.  Normally,
he/she will run SS_CONFIG (or whatever) on a portable PC to compute the
HPSUSAN and (I think) the new model string to enter into stable storage on
the 3K.  Typically, we've been able to retain the same HPSUSAN across all
upgrades, but HPCPUNAME has always reflected the new model string.
 I hope I understood your question correctly.
Lee Gunter          [log in to unmask]
Regence BlueCross BlueShield of Oregon / Regence HMO Oregon
==========================================================
The opinions expressed, here, are mine and mine alone.



From: "Paul H. Christidis" <[log in to unmask]> on 11/11/98
      02:05 PM
Please respond to [log in to unmask]

To:   [log in to unmask]
cc:    (bcc: Lee Gunter/BCBSO/TBG)
Subject:  Changing the 'HPCPUNAME' variable



If additional processors were to be added to a multi-CPU machine is/has the
value of the 'hpcpuname' variable also changed to reflect the presence of
the additional CPU(s)?
Regards
Paul H. Christidis