On Thu, 23 Feb 2006 22:44:39 +0100, Rob van der Heij <[EMAIL PROTECTED]> wrote:
>My understanding is that z/OS will make assumptions about topology of >the network based on the CHPID. So if z/OS finds two NICs with the >same CHPID, it will assume they connect to the same OSA. >Now if you were to connect the z/OS guest to both dedicated OSA and >Guest LAN, you would need to make sure they are on different virtual >CHPID, and since you cannot tweak the one of the dedicated OSA, you >pick the CHPID of the virtual NIC different from any real OSA in the >machine, just in case... And apparently there's also options for >confusion in z/OS when the virtual NIC is on the same CHPID as another >device. So this is an upper boundary for the number of different Guest >LANs each z/OS can connect to. Which still begs the question: Why does z/OS (and apparently only z/OS) need to know what the CHPID is ahead of time when other TCPIP stacks (ie z/VM & LINUX) happily work with whatever CHPID gets dynamically assig ned? And is there any hope/plan for a remedy from either platform (z/OS or z/VM)? Brian Nielsen
