SCOUG-Programming Mailing List Archives

<< Previous Message << >> Next Message >>

Date:	Wed, 6 Jun 2001 23:06:36 PDT
From:	Peter Skye <pskye@peterskye.com >
Reply-To:	scoug-programming@scoug.com
To:	scoug-programming@scoug.com
Subject:	SCOUG-Programming: SockListen() usage ?

Content Type: text/plain

I'm using Rexx sockets. I don't understand the result of calling
SockListen().

I was told that a call to SockListen() "blocks", which to me means that
it doesn't return until there's a client trying to connect.

But when I call SockListen() I get an immediate return value of 0,
meaning no error, even though no client is trying to connect to the
socket. The online help doesn't explain the return value from
SockListen().

Here is my code, after opening and binding with SockSocket() and
SockBind():

say "ClientSocket="ClientSocket
rc = SockListen( ClientSocket, 65535 )
say ...

(I know 65535 is ridiculously high. I also tried with 1 and got the
same results shown below.)

and here is what I have after the call:

ClientSocket=660
rc=0
SockSock_Errno()=0
errno=0
h_errno=1541

My understanding is that I first SockSocket() and SockBind(), then
SockListen() until a client connects, after which I SockAccept(). What
is the proper method of using SockListen()?

- Peter

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-programming".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================

Return to [ 06 | June | 2001 ]

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.