Re: Question on Closing a Socket

On Tue, 30 May 2006 18:50:30 -0500 (CDT)
 Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx> wrote:

You aren't forgetting to call WSAStartup(), are you?
 Make sure you're 
calling WSAStartup() and WSACleanup() properly.  I know
there was an issue 
where if another thread called WSACleanup() more times
than WSAStartup, it 
would cause all sockets in all threads to be closed.
 But, I thought that 
was only an issue in multiple threads of the same
process, not when 
calling across two different processes.  (But, maybe I'm
wrong about 
that.)

My app is RPG (GETURI).  The other app is VARPG.
 Apparently the idea is GETURI is closing a socket that is
in use by the VARPG client.

That's where the descriptor=0 thing came into question.
 But it only happens when GETURI times out on the connect.

VARPG calls an RPG program that calls GETURI.  GETURI times
out on the connect.  GETURI closes the socket it created.
 the VARPG client gets killed.

I thought it was weird to.  :)  I just wanted to make sure
that I wasn't missing some hidden text in IBMs docs about
closing a socket that was created but didn't connect to
anything.

Brad