Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
RawIpSend z/OS Communications Server: IP Sockets Application Programming Interface Guide and Reference SC27-3660-00 |
|
This procedure shown in this example sends IP datagrams of the given protocol number. The entire packet, including the IP header, must be in the buffer. The TCP/IP address space uses the total length field of the IP header to determine where each packet ends. Subsequent packets begin at the next doubleword (eight-byte) boundary within the buffer. The packets in your buffer are transmitted unchanged with
the following exceptions:
You get the return code NOsuchCONNECTION if the client
is not handling the protocol, or if a packet in the buffer has another
protocol. The return code BADlengthARGUMENT is received when:
A ReturnCode value of NObufferSPACE indicates that the data is rejected, because TCP/IP is out of buffers. When buffer space is available, the notification RAWIPspaceAVAILABLE is sent to the client. Figure 1. RawIpSend example
Note: If your buffer contains multiple packets waiting to
be sent, some of the packets might have been sent even if ReturnCode
is not OK.
For a description of Pascal return codes, see Table 1. |
Copyright IBM Corporation 1990, 2014
|