Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
RECVFROM call z/OS Communications Server: IP CICS Sockets Guide SC27-3649-00 |
|||||||||||||||||||
The RECVFROM call receives data on a socket with descriptor S and stores it in a buffer. The RECVFROM call applies to both connected and unconnected sockets. The IPv4 or IPv6 socket address is returned in the NAME structure. If a datagram packet is too long to fit in the supplied buffers, datagram sockets discard extra bytes. For datagram protocols, the RECVFROM call returns the source address associated with each incoming datagram. For connection-oriented protocols like TCP, the GETPEERNAME call returns the address associated with the other end of the connection. On return, NBYTE contains the number of data bytes received. For stream sockets, data is processed as streams of information with no boundaries separating the data. For example, if programs A and B are connected with a stream socket and program A sends 1000 bytes, each call to this function can return any number of bytes, up to the entire 1000 bytes. The number of bytes returned are contained in RETCODE. Therefore, programs using stream sockets should place RECVFROM in a loop that repeats until all data has been received. For raw sockets, RECVFROM adds a 20-byte header. If data is not available for the socket, and the socket
is in blocking mode, RECVFROM blocks the caller until data arrives.
If data is not available and the socket is in nonblocking mode, RECVFROM
returns a -1 and sets ERRNO to 35 (EWOULDBLOCK). See FCNTL call or IOCTL call for
a description of how to set nonblocking mode.
Note: See EZACIC05 program for a subroutine that translates ASCII
input data to EBCDIC.
The following requirements apply to this call:
Figure 1 shows an example of RECVFROM call instructions. Figure 1. RECVFROM call instruction example
For equivalent PL/I and assembler language declarations, see Converting parameter descriptions. |
Copyright IBM Corporation 1990, 2014
|