On Fri, 24 Feb 2006 15:25:40 -0500, Alan Altmark <[EMAIL PROTECTED] > wrote:
>On Friday, 02/24/2006 at 10:52 CST, Brian Nielsen ><[EMAIL PROTECTED]> wrote: >> 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 >assigned? >> And is there any hope/plan for a remedy from either platform (z/OS or >> z/VM)? > >z/OS looks at the chpids to find out if it is sharing an OSA and to >confirm parallel connections for Hipersockets. The shared OSA >configuration is important to dynamic VIPA and IP takeover. I can't >remember for sure, but he may check the chpid numbers and compare define d >subnets. A useful thing, really. But it doesn't require specification of >a chpid number since chpid numbers can be extracted from the SCHIB. All good stuff to be done. >We continue to discuss this with z/OS, but Real z/OS Customers should ma ke >their requirements known to z/OS. I'll see if our Real z/OS Systems Programmers are willing to pursue this from the z/OS side. As a Real z/VM Customer, I think z/VM should be required to handle the virtualization of the CHPID number a guest sees, which the CHPID paramete r on NICDEF is not currently adequately doing. One of z/VM's benefits is the isolation of a guest from the real hardware. In this case, it's not being done. Brian Nielsen
