The Comm. Bridge TCP/IP implementation makes use of stream sockets. A stream socket provides a full-duplex, sequenced, reliable transmission mechanism, over which a DPC cooperative flow byte stream can flow. The socket provides the TCP communications endpoint, used by the Comm. Bridge, to gain access to the IP network.
A Comm. Bridge is connected to the IP network and listens for inbound connections using its well-known port number. This well-known port number is configured within the Comm. Bridge. The Comm. Bridge port listening subsystem will handle concurrent connections originating from either IPv4 or IPv6 clients.
When a client successfully connects to a Comm. Bridge the client is added to the client list found on the Comm. Bridge main GUI window. This scrollable list displays an entry for each connected client. Each client entry displays the client's host name or IP address. The IP address can be either an IPv4 or IPv6 address depending on the protocol used for a successful connection. Each entry also includes a time/date stamp of the last flow activity to or from the client as well as a running byte count totals. Selecting a client from the client list will result in appropriate connection configuration details being displayed in the Selected Client Details area just below the list. A client is removed from the list when it becomes disconnected from the Comm. Bridge.
By default, a domain name service (DNS) host name lookup is performed to obtain the name of the client workstation. Optionally, if desired for performance reasons, the DNS host name lookup can be skipped and a client IP address displayed instead. This behavior can be modified using the Comm. Bridge IEFNET TCP/IP user exit. For more information about this user exit, see "Comm. Bridge User Exits."
The following procedure can be used to configure the Comm. Bridge well known client port number.
|
Copyright © 2013 CA.
All rights reserved.
|
|