> To cross the partition border from VM LPAR to z/OS LPAR you can use hipersockets, which you are doing, or > OSA devices (they can be shared), or real CTCAs - different types of chpids can be configured as CTCAs - and > you can get a bunch of CTCAs from one channel. If you are running into hipersocket limitations consider sharing your > FDR traffic with your other traffic. > NICDEFs and SPECIAL statements refer to using guest lans - a completely virtual network - the lan is virtual and so are the adapters. Setup via CP commands and/or directory statements. TCPIP is TCPIP is TCPIP - doesn't know or care that the > network is virtual - Every effort should be made to connect virtual machines within one LPAR via guest lans. It's not > virtual IP addressing - that's another topic.
One way to think of it might look this way: (inside the VM LPAR) lots of guests attached to guest LAN --> Linux "bridge router" system --> real hipersocket ---> z/OS (in the z/OS LPAR) VM guest LANs don't have the 127 device limitation. The "bridge router" system consumes only 1 set of addresses on the real hipersocket, and 1 set on each guest lan it's attached to (there can be as many as you can define interfaces for). Repeat a similar configuration for the other physical hipersocket. It's MUCH simpler to manage (no IOCP stuff for adding/deleting guests) it this way since you have VM -- use it! (btw, can you edit down the included message somewhat? It makes your questions hard to find...) -- db ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
