Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
send() z/OS Communications Server: IP Sockets Application Programming Interface Guide and Reference SC27-3660-00 |
|
The send() call sends datagrams on the socket with descriptor s. The send() call applies to all connected sockets. If buffer space is not available to hold the socket data to be transmitted, and the socket is in blocking mode, send() blocks the caller until more buffer space becomes available. If the socket is in nonblocking mode, send() returns a -1 and sets errno to EWOULDBLOCK. See fcntl() or ioctl() to set nonblocking mode. See select() for additional information. For datagram sockets, this call sends the entire datagram, providing the datagram can fit into the TCP/IP buffers. Stream sockets act like streams of information with no boundaries separating data. For example, if an application wants to send 1000 bytes, each call to this function can send 1 byte, or 10 bytes, or the entire 1000 bytes. Therefore, applications using stream sockets should place this call in a loop and call this function until all data has been sent.
Return valuesNo indication of failure
to deliver is implicit in a send() routine. The value -1 indicates
locally detected errors. Errno identifies the specific error.
Related callsconnect(), fcntl(), getsockopt(), ioctl(), read(), readv(), recv(), recvfrom(), recvmsg(), select(), selectex(), sendmsg(), sendto(), socket(), write(), writev() |
Copyright IBM Corporation 1990, 2014
|