On Sunday, 10/05/2008 at 04:55 EDT, Rob van der Heij <[EMAIL PROTECTED]> wrote:
> From what I see, IPGATE can only talk to one single stack, so it makes > sense to use a single connection. I have never used RXSOCKET, but from > what I see it does not support multiple stacks either, so it is > practical to have only one IUCV connection. But if you write a server > with CMS Pipelines to listen to multiple sockets (on different stacks > if you want) then there will be one IUCV to the TCP/IP virtual machine > for each socket. Multiple TCP/IP client (IUCV) connections to the stack is useful when you are acting as a proxy on behalf of your own clients. E.g. a sniffer virtual machine. Then, you SEVER your connection to the stack if a client severs his or her connection to you. Other than that, I don't think there's any value in one IUCV connection per socket. It's a convenient programming model, but it's a waste of resources. > PS IPGATE does have one IUCV connection to CP for each resource that > it provides. The connection is an APPC/VM connection to the APPC *resource manager*, not a connection to CP, as would be the case for a "starsys" system service. Alan Altmark z/VM Development IBM Endicott
