Not at all -- unless it's a totally new system you're talking about.  Adding or
replacing CPU's in an existing MPE/iX system should not result in a new HPSUSAN
value.  Certain repair or upgrade scenarios may exist which would require the
HPSUSAN to change, but I've never encountered one.  Think of the thrill of
having to contact all your software vendors (who use HPSUSAN copy protection) in
the middle of the night to get new activation codes.    :-)
----
Lee Gunter                    The Regence Group
Supervisor, TRG HP/MPE Systems     503.375.4498
----
Opinions expressed are solely mine.





From: Mark Landin <[log in to unmask]> on 12/14/99 07:49 AM

Please respond to Mark Landin <[log in to unmask]>


To:   [log in to unmask]
cc:    (bcc: Lee Gunter/BCBSO/TBG)
Subject:  Re: [HP3000-L] NEW CPU replacement causing problems




On Tue, 14 Dec 1999 02:34:23 -0500, Kevin O'Sullivan
<[log in to unmask]> wrote:

>Hi all,
>
>I'll make the assumption that Omnidex complained that the SUSAN number had
>changed.
>
>I have heard that under extreme circumstances, the SUSAN number can be
>changed by the CE, which if you have a
>LOT of targeted software installed, could be very handy indeed.
>

Actually I think changing the SUSAN and related information after a
CPU replacement is supposed to be the rule, not the exception. Right?