Examples

In examples where host names CHICAGO.COM and BOSTON.COM are used, it is assumed, and required, that these names have been defined to TCP/IP.

Example 1: The following is an example of a TCP/IP definition between two nodes using IP addresses. Although the HOSTNAME and PORT parameters on the NETSERV statement are not required, they are shown here to illustrate the relationship between the NETSERV statement on one node and the SOCKET statement on the other.

BOSTON:
NETSERV,NAME=JES3S1,SYSTEM=APPLES,
HOSTNAME=2.71.82.81,
PORT=495
SOCKET,NAME=SOCKET1,NETSERV=JES3S1,NODE=CHICAGO,
HOSTNAME=3.141.59.26
NJERMT,NAME=BOSTON,HOME=YES
NJERMT,NAME=CHICAGO,TYPE=TCPIP

CHICAGO:
NETSERV,NAME=JES3S2,SYSTEM=ORANGES,
HOSTNAME=3.141.59.26
SOCKET,NAME=SOCKET1,NETSERV=JES3S1,NODE=BOSTON,
HOSTNAME=2.71.82.81,
PORT=495
NJERMT,NAME=CHICAGO,HOME=YES
NJERMT,NAME=BOSTON,TYPE=TCPIP

Example 2: The following is an example of a TCP/IP definition between two nodes using a host name. Although the HOSTNAME and PORT parameters on the NETSERV statement are not required, they are shown here to illustrate the relationship between the NETSERV statement on one node and the SOCKET statement on the other.

BOSTON:
NETSERV,NAME=JES3S1,SYSTEM=APPLES,HOSTNAME=BOSTON.COM
SOCKET,NAME=SOCKET1,NETSERV=JES3S1,NODE=CHICAGO,
HOSTNAME=CHICAGO.COM
NJERMT,NAME=BOSTON,HOME=YES
NJERMT,NAME=CHICAGO,TYPE=TCPIP

CHICAGO:
NETSERV,NAME=JES3S2,SYSTEM=ORANGES,HOSTNAME=CHICAGO.COM
NJERMT,NAME=CHICAGO,HOME=YES
NJERMT,NAME=BOSTON,TYPE=TCPIP

Note:

A SOCKET statement is not required on CHICAGO unless it is required to start the communication on CHICAGO. If communication is started on BOSTON by using socket SOCKET1, TCP/IP will create an ephemeral socket on the CHICAGO side. JES3 on CHICAGO, in turn, dynamically creates a SOCKET definition with a unique name of @nnnnnnn, where nnnnnnn starts at 0000001 and is assigned to the first available number. JES3 calls this socket definitions a server socket, because when a TCP/IP connection is established, the node on which the connection is initiated is known to TCP/IP as a client and the responding node is known to TCP/IP as a server. A client socket also sometimes referred to as an outbound socket and a server socket is sometimes referred to as an inbound socket.
If BOSTON is a JES3 node and CHICAGO is a JES2 node, CHICAGO and BOSTON must define a sockets to each other. JES2 requires a socket definition for both an inbound and outbound socket; JES3 requires a socket definition only for an outbound socket.