Sorry, I was misremembering what IDENTIFY returned when it didn't find a match in SYSTEM NETID.
Dennis "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 Alan Altmark Sent: Wednesday, February 22, 2006 12:36 To: [email protected] Subject: Re: SYSTEM NETID and CPUIDs On Wednesday, 02/22/2006 at 12:11 PST, "O'Brien, Dennis L" <Dennis.L.O'[EMAIL PROTECTED]> wrote: > 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. I already posed the design point that it would default to AT <system_id> VIA RSCS. IDENTIFY already defaults to AT <system_id> VIA *. Is it sufficient to just change the default to VIA RSCS and still require the use of SYSTEM NETID if you want something else? Do I really *need* SET commands to change these puppies? Alan Altmark z/VM Development IBM Endicott
