Alan, Additional function (as opposed to replacement function) should cause ver y few problems - it would certainly get my vote.
Browsing the later discussion I think I can summarise the needs that woul d perhaps get a chance of being addressed with the likely available resources as: IDENTIFY checks SYSTEM NETID and, if it finds a match, uses it. SYSTEM NETID syntax is extended to include keying on SYSTEMID (as in response from QUERY USERID) as well as on virtual CPUID. Somebody defines what happens if there are, "duplicates" in SYSTEM NETID. (If it were me I'd just take first match found, scanning file from the top, but YMMV.) If there's no match in SYSTEM NETID, IDENTIFY uses a set of defaults. The IBM-supplied default uses, "RSCS" as the, "SPOOL Networking Userid". There is some way (probably SYSTEM NETID) of changing the, "Default default". Asterisk remains valid as a target userid. ------------------------------------------ The above would, I believe, achieve the goals of: Making IDENTIFY use RSCS in the system-as-shipped (our primary goal). Allowing current as-shipped behaviour (asterisk) to be restored in a simple manner. Making IDENTIFY use either SYSTEMID or CPUID as deciding criterion. My prime assumption is that anybody who wants to restore the default of asterisk or change the name of the RSCS userid is unlikely to be fazed by the challenges associated with updating a file on MAINT's 0190. (Why is it always the little things that generate the big discussions!) Regards Jeff
