Re: Test device before socket connection

Hi Craig,

Please don't reply to an existing thread if you're posting a new message that's unrelated to the one you're replying to. That screws up the threading in many places (including the archives and many e-mail programs, including mine.)

I very nearly didn't see your message.

Furthermore, if your question is how to make a connection with a 2 second timeout in RPG... I know two different ways to accomplish that, so PLEASE don't post a message saying it's not possible. I'd be happy to discuss them with you, but it needs to be on the RPG list, not here. (or if you're doing it in C, ask on the C mailing list)

Finally, I don't understand your question. You want to check if something is connected before calling connect()? Huh? Connect() is the API that establishes that connection. Obviously, if you haven't called connect(), it's not connected!


Craig Jacobsen wrote:

I am using Scott Klement's socket programs to get weights from scales.
This has been running fine for over a year.

Ever since the network replaced its wireless controller early this week, the
wireless connection drops at times. (I'm already in touch with Lantronix)

When it drops, the connect() hangs for 3 to 5 minutes trying to make a
connection. (I would like that to be a second or 2, but there are no
timeout values). This hangs the 5250 manifest station for that time before
I can issue an error message.

Is there a way I can test the IP address to make sure the device is
connected (other than PING) before I try the socket connection?

Thanks,

Craig