WinSock Path Configuration

Getting there

In InfoConnect Manager 32, click Configure and select Paths. Click Add. From the Path Template drop-down, select WinSock and click Configure.

Winsock Path Configuration

Application Type

Select the Application Type from the radio buttons given:

Server - means the connection is initiated by the host

Client - means the connection is initiated by the workstation

Protocol

Select the Protocol from the radio buttons given:

TCP - Transmission Control Protocol. TCP is much more common than UDP. TELNET, TP0 and TELCON connections all use TCP.
UDP - User Datagram Protocol. SNMP agents use UDP.

Server IP Address

Enter the TCP/IP address or domain name of the host computer in the Server IP Address field. The host can be a DCP, HLC, ASeries host, UNIX host, etc. This field is usually only specified when ApplicationType=Client. For Server connections, this field can be left blank.

Server Port Number

The port number identifies the communication protocol. Some standard port numbers are:

23 - TELNET connections use TCP port 23
102 - TP0 connections use TCP port 102
161 - SNMP agents listen on UDP port 161
162 - SNMP agents send traps on UDP port 162
256 - TELCON connections to OS1100 or OS/3 via a DCP use TCP port 256

Client Port Number

This field is normally left blank (or zero). In this case, the software selects an available port. A nonzero value will force the assignment of a specific port for those instances that require such control.

Advanced Options

Keepalive packets

InfoConnect can request the underlying Winsock software to use keep-alive packets on TCP connections. Keepalive causes more network activity, but enables better identification of network failures. Winsock implementations are not required to support this feature.
Debugging

InfoConnect can request the Winsock software to record debugging information. Details of how to view this information varies with the specific TCP vendor. Winsock implementations are not required to support this feature. This debugging switch is specifically for the underlying Winsock software and is not related to the InfoConnect Tracing facility.
Receive incoming Out-of-Band data as normal

Out-of-band signaling is a method whereby the sending application can mark data as urgent and have the receiving application process it separately from the normal data. This option alters the standard behavior and requests the TCP/Winsock software to merge out-of-band data into the standard data stream being received by the application.