gtpc1m2d | Transmission Control Protocol/Internet Protocol |
Sockets that use TCP/IP native stack support are not limited to a single ECB, subsystem, or I-stream. For example, an ECB running in subsystem ABC on I-stream 2 creates a socket. The file descriptor of this socket is then saved in a user table and the ECB exits. Next, an ECB running in subsystem XYZ on I-stream 4 retrieves the file descriptor of the socket from the user table and issues a socket API call. This is allowed.
Multiple ECBs can issue socket API calls for the same socket at the same time. For example, one ECB can issue a read API call for a socket at the same time that another ECB issues a send API call for this socket. You can even have multiple ECBs issue send API calls for the socket at the same time. The TCP/IP native stack support code handles the necessary serialization. You can issue any combination of socket API calls for a given socket with the following restrictions: