On Thursday, 02/23/2006 at 04:58 CST, "Jeff Gribbin, EDS"
<[EMAIL PROTECTED]> wrote:
> My point is that the current criterion (cpuid) is dynamically variable
> whereas the proposed criterion (SYSTEMID) is fixed. Once upon a time
this
> would have been an issue for me. Nowadays, for me, the convenience and
> simplicity of SYSTEMID would win hands-down - but it DOES imply a
tradeoff
> and, if implemented, may irritate one or two remaining eccentrics such
as
> I used to be.
I do not propose to eliminate the current capabilities of "{nodeid,
rscsid} = f(cpuid)". But, rather, to add "{nodeid, rscsid} = f(systemid)"
and a default of "{nodeid, rscsid} = {systemid, RSCS}".
And maybe, just maybe, we could have SET SYSTEMID just as we do SET CPUID,
eh? How many times have people requested to be able to change the
systemid seen in the lower right-hand corner? :-)
But the real objective is to (a) not require any configuration of SYSTEM
NETID where none is needed, and (b) eliminate one of the annoying
pain-points during migrations. It doesn't necessarily mean making the
ability to change your nodeid and rscsid to something other than the
default any easier. (But it would be nice.)
Alan Altmark
z/VM Development
IBM Endicott
