On Friday, 12/07/2007 at 03:10 EST, "Huegel, Thomas" <[EMAIL PROTECTED]> wrote: > I haven't really thought this thru, but how about something like this in the > VSWITCH start-up or config file an unrestrict parm that could be generic, ie > UNRESTRICT VSE* ZOS* then just machines with those prefixes would be > unrestricted ???
"Restricted" and "Unrestricted" are attributes of the VSWITCH, not the user. If the VSWITCH is unrestricted, then there is no access list and all users can couple to it. If the VSWITCH is restricted, then there is an access list and only those users in the access list can couple to it. Based on what I've read here and input I've received in other venues, I've concluded that, for non-ESM environments, the access list is the set of all users who have a NICDEF (not SPECIAL!) statement in their directory entry that references a particular VSWITCH or Guest LAN, *plus* the users identified on SET VSWITCH GRANT. No additional authorization is required, but they will not show up in QUERY VSWITCH AUTH (since no GRANT issued), nor can the authorization be revoked by command. Uncoupling from the VSWITCH doesn't hurt. If you COUPLE again, it will work (a la LINK). All of the above applies equally to a restricted Guest LAN. Alan Altmark z/VM Development IBM Endicott
