Not multiple stacks, multiple sockets on one port, one stack. The application is a driver of test systems that opens thousands of sockets, one for each endpoint that it emulates. Since it is one IUCV connection, my MAXCONN is not in danger of being exceeded.
Regards, Richard Schuh > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:[EMAIL PROTECTED] On Behalf Of Rob van der Heij > Sent: Sunday, October 05, 2008 1:55 AM > To: [email protected] > Subject: Re: MAXCONN > > On Sat, Oct 4, 2008 at 6:18 PM, Ivica Brodaric > <[EMAIL PROTECTED]> wrote: > > > For applications, check IPGATE if you have it. It does only one > > socket('INITIALIZE') in the top level routine, but creates > new sockets > > for each userid/APPC resource pair. According to previous post, it > > should use only one IUCV link to the stack. > > It depends on the application. The fact that you can is no > guarantee the application will. > > 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. > > PS IPGATE does have one IUCV connection to CP for each > resource that it provides. > > -Rob >
