On Friday, September 15, 2000 1:37 PM, Andrew Cartledge  wrote:

snip;

: I found that if I run the client program at two terminals at the same time,
: the second client is locked out until the first client closes.

I'm fairly certain this is due to the single threaded nature of the cobol
client server socket model.  Unless you spawn instances of child
processes and pass the socket info off, the cobol server program
will only be communicating with one process at a time.

: hang after some 61 (ipcdest, connect, recv, shutdown, send, shutdown) loops

>From what I've done before and what I understand of NetIPC and sockets,
after you call the shutdown intrinsic the VC is terminated and you no
longer have a socket to send on.

: Can/should two (in this case identical) client processes be able to post to
: the same socket at the same time?

I don't believe so.  Once a socket connection is established between two
processes, communication is only possible between those endpoints
unless you use the ipcget and ipcgive intrinsics to pass the socket (or
file handle) off to another process.

I've forgotten what the cause of the Network error was.  One tool that
I used to find out that I was created a huge amount of socket connections
and not terminating them was the showconn utility.

HTH

----------------------------------------------------------------------------
-------
David Burney                               [log in to unmask]
Summit Racing Equipment                     http://www.summitracing.com
                                    -----------
      Politicians are the same all over. They promise to build bridges
      even where there are no rivers.                          -Nikita
Khrushechev
                        -----------
      All opinions expressed herein are my own and reflect,
                  in no way, those of my employer.