RE: RPG Socket fails after a number of communications

This problem seems to be solved:

The problem was that I start a PC server job using RUNRMTCMD, and then
immediately try to connect a socket to it.  The PC job sometimes isn't
ready for connecting right away, so if the first connect fails, I delay 1
second, and then try again.  I was neglecting to use the close() API on the
first failed connection, because I didn't realize that whenever you
retrieve a socket ID, it gets marked as an open ID, whether you run a
successful connect() against it or not.

Thank you to everyone who made suggestions, and especially to Scott Klement
who ran some great testing scenarios to help prove out the socket
functions.