On Sunday, 10/29/2006 at 10:18 CST, Dennis Schaffer <[EMAIL PROTECTED]> wrote:
> In my production environment, this z/VM system shares its OSA adapters with > three other z/OS systems. One of these z/OS systems was recently > reconfigured as the PRIROUTER TCPIP stack because of (1 the need to > establish a hipersockets connection between this and another z/OS system Sorry. What does establishing a HiperSocket connection between the two z/OS systems have to do with PRIROUTER on the OSA? Rather than using the "other" z/OS to route data, it should share the "other" OSA instead, using the HiperSocket only for z/OS-to-z/OS communications. > and (2 the importance of its workload to our organization causing it to be > the first mainframe system normally IPLd in our shop. I really wouldn't depend on IPL sequence to protect you. Only one LPAR should have the PRIROUTER designation, and only because it is acting as a router. At this point I feel I should stop giving advice as I haven't seen a drawing of your intended network. Sometimes I think we're talking about non-routing guests attached to a VSWITCH, and other times I think we're talking about a Guest LAN connected to a virtual router. Alan Altmark z/VM Development IBM Endicott
