If you're going to change the default of IDENTIFY, I'd rather it default to the CP node name (System_Identifier_Default from SYSTEM CONFIG) if it doesn't find a match in SYSTEM NETID. Allowing wildcards for CPUID in SYSTEM NETID would also be handy.
Dennis O'Brien "Of all tyrannies, a tyranny exercised for the good of its victims may be the most oppressive. It may be better to live under robber barons than omnipotent moral busybodies. The robber baron's cruelty may sometimes sleep, his cupidity may at some point be satiated; but those who torment us for our own good will torment us without end, for they do so with the approval of their own conscience." -- C.S. Lewis -----Original Message----- From: VM/ESA and z/VM Discussions [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes Sent: Wednesday, February 22, 2006 04:39 To: [email protected] Subject: Re: SYSTEM NETID and CPUIDs > > Doesn't everyone have at least the LPR/LPD functions of > RSCS? If so, > > then setting the default SYSTEM NETID to have a RSCSid of > RSCS should > > be correct (and cause PPS and friends to work out of the box). > > Sorry, I shouldn't have used the word "have". Everyone has RSCS now > and can use it for LPR and LPD for free. I should have said "use". In either case, doesn't it make sense to have IDENTIFY return a default RSCSid of RSCS (if there is no SYSTEM NETID entry specifying otherwise) instead of *, since everyone *does* have RSCS these days, and (unless you know what you're doing and have deliberately changed the id) it's always installed as userid RSCS? It does no harm, and strikes me as something that is in the category of picking sensible defaults (and in at least one case, a default that avoids a problem and makes it easier to exploit useful function). -- db
