Re: Socket Recv Question

[Rory Hewitt <rory.hewitt@xxxxxxxxx>]

Michael,

Check out Scott's article on using socket timeouts:
http://systeminetwork.com/article/timeouts-sockets-0

regards,

Rory

On Wed, Mar 2, 2011 at 1:54 PM, Koester, Michael <mkoester@xxxxxxxxxxxxx>wrote:

> Don't know if this is related, but I also am having trouble with recv().
> Since I don't know when I've received everything that will be sent (from
> telephone switch equipment), if I don't find the expected string in the
> buffer, I save what I've received so far and call recv() again.  This
> seems to work to get additional data when I'm trying to check results
> too soon, but I suspect when there's nothing more to be sent (how would
> I know?), and I call recv() again, control does not return to my RPG
> program.
> Has recv() timed out?  I have to crash the job, which leaves a
> connection to the switch open and messes to clean up.
> I haven't done anything fancy with recv().  The line that locks up is:
>
> rc = recv(sock: %addr(recbuf):3000:0);
>
> I send the request to the switch with "send(sock: %addr(request):
> reqlen:0)", and then execute a dou loop to interpret the response from
> the switch:
>        Dou done;
>          [wait a bit]
>          Recbuf = *blanks;
>          rc = recv(sock: %addr(recbuf):3000:0);
>          [translate recbuf to EBCDIC and scan for expected prompt
> string]
>          [If found, leave do loop - else, repeat loop up to a
> reasonable number of times]
>        Enddo;
>
> Debug confirms that it hangs on recv().  Works well so long as the
> expected prompt is returned, but I can't process the "not found"
> condition if I don't know that there isn't more to receive...
>
> Suggestions welcome!
>  Michael