HP3000-L Archives

November 1998, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Gavin Scott <[log in to unmask]>
Reply To:
Gavin Scott <[log in to unmask]>
Date:
Thu, 12 Nov 1998 11:01:10 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (23 lines)
Andreas writes:
> HPSUSAN is important for a lot of 3rd Party S/W. This can be kept.

My understanding is that the SUSAN number is bound to the serial number
of the box.  On any upgrade that does not change the serial number of the
system (i.e. is not a "box swap" upgrade) the SUSAN number absolutely
should remain the same.  If, however, the serial number of the box is
changed, then the SUSAN number *must* change as well.

> HPCPUNAME should always reflect the real CPU type.

Agree.  This includes the number of CPUs on a multiprocessor system.

> 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.).

Many products use the SUSAN number for licensing.  Some (those with tier
pricing generally) will also use the CPUNAME value.

G.

ATOM RSS1 RSS2