RE: Word of advice: Dont' close a socket you didn't create.

[Jim Langston <jlangston@xxxxxxxxxxx>]

David,

I'm interested in this problem so that it doesn't happen to me.

How is it that you are closing socket 0 if you don't have a handle to it?

Normally, in C anyway, I would say something like socket = blah blah...
then later
close (socket)
so I don't see how it could close socket 0, unless it is a problem either
specific to your code or RPG or RPG's implementation of sockets?

Regards,

Jim Langston

-----Original Message-----
From: David Gibbs [mailto:dgibbs@mks.com]

Folks:

<SNIP>

Because our remote server will disconnect if there is no activity for a
certain period of time, we have code that allows for reconnect... but before
we try to connect (even the first time) we close the currently open socket.
When we didn't open the socket, we close socket 0.  Socket 0, unfortunately,
didn't belong to us.  It belonged to the remote command job.

Solution was to init our programs socket variable to -1 so we can detect if
we've opened it or not.