Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Providing address information for the SOCKET transport system (Unix, Linux and Windows systems)

In connections to a TS application with PTYPE=SOCKET, communication is performed via the socket interface using native TCP/IP as the transport protocol. For these socket applications the address information will be provided for the transport system via the UTM generation.
The address information is stored in the PRONAM and LISTENER-PORT operands as well as in T-PROT and TSEL-FORMAT. In addition, the BCAMAPPL operand is also important. Note the following points in this context:

  • For PRONAM you must specify the TCP/IP host name, see "Specifying computer names in KDCDEF generation". openUTM determines the IP address from it.

  • You must enter a port number for LISTENER-PORT. The port number absolutely must match the port number used by the communication partner. Specification of a LISTENER-PORT is mandatory.

  • You must specify SOCKET for T-PROT.

  • It is recommended to set a value in the TSEL-FORMAT operand.

  • In BCAMAPPL you must specify an application name for which T-PROT=SOCKET was generated.

    Unix, Linux and Windows systems

    Please note the maximum number of connections that can be established at a time via one transport system end point. For details see BCAMAPPL statement in section "BCAMAPPL - define additional application names".

PTYPE=SOCKET connection

In the following example, port number 10010 is used in the local application and port number 12100 is used in the remote application LU61PART. The remote application is running on the computer named CENTRAL5.

BCAMAPPL BSPSOC -
,LISTENER-PORT=10100 -
,T-PROT=SOCKET -
,T-SEL-FORMAT=T -
,...

PTERM SOCPART -
,PTYPE=SOCKET -
,BCAMAPPL=BSPSOC -
,PRONAM=CENTRAL5 -
,LISTENER-PORT=12100 -
,T-PROT=SOCKET -
,TSEL-FORMAT=T -
,...