For TS applications, HTTP clients, UPIC clients and OpenCPIC clients, address information is required to establish a connection. This information is stored in the UTM generation. For socket applications, there is no difference between BS2000 systems and Unix, Linux or Windows systems. For other clients, the characteristics of the transport system take effect. This information is therefore divided into separate paragraphs.
The address information for OpenCPIC clients is specified in the same way as for OSI TP partners in generell, see chapter "Generation of distributed processing based on OSI TP". The information supplied must match the configuration of the OpenCPIC client.
Providing the address information for HTTP clients and TS applications of type SOCKET
When communicating with HTTP clients or TS applications via TCP/IP the socket interface is used directly.
The address information required for communication is provided in the UTM generation.
KDCDEF generation
The address information is stored in the operands LISTENER-PORT=, T-PROT= and PRONAM= of the BCAMAPPL and TPOOL/PTERM statements.
BCAMAPPL statement
You must always specify a BCAMAPPL statement for socket applications. The following applies:
In LISTENER-PORT= you must always enter a port number under which the UTM application waits for the requests of the socket application. The port number must correspond to the settings of the communication partner.
In T-PROT= you must enter SOCKET.
Unix, Linux and Windows systems:
LISTENER-ID= assigns the connection an optional listener ID. You can use the listener ID to distribute the management of network connections to different network processes. The values for the LISTENER-ID of non-socket connections and socket connections may be assigned independently of each other.
PTERM statement
If you generate a socket partner individually, you will need to specify the following operands and parameters:
If the socket application is to establish the connection, the PTERM name must have the format PRTnnnnn, where nnnnn is the port number from which the socket application establishes the connection. The name may be supplemented by leading zeros.
In BCAMAPPL= enter the application name as defined in the BCAMAPPL statement.
In PRONAM= you must specify the TCP/IP host name.
For Unix, Linux and Windows systems, please consider also section "Specifying computer names in KDCDEF generation".
In the LISTENER-PORT= operand, you must specify the port number at which the socket partner is waiting for connection establishment requests.
TPOOL statement
If you want to connect a socket partner using a LTERM pool, then:
In PRONAM= you must specify the TCP/IP host name or the mapped name of a SUBNET statement.
If you specify the mapped name of a SUBNET statement for PRONAM, clients from any computers from this subnet can sign on, provided they correspond to the type specified in PTYPE=.
If you enter PRONAM=*ANY, then clients from any computer can sign on assuming they are of the same type as specified in PTYPE= .
For Unix, Linux and Windows systems, please consider also section "Specifying computer names in KDCDEF generation".
In BCAMAPPL= enter the application name as defined in the BCAMAPPL statement.
Example
The following example uses the port number 10100. The socket application is linked via the LTERM pool and runs on the computer PCSOCK01.
BCAMAPPL BSPSOCK -
,LISTENER-PORT=10100 -
,T-PROT=SOCKET -
,...
TPOOL ...
,PTYPE=SOCKET -
,BCAMAPPL=BSPSOCK -
,PRONAM=PCSOCK01 -
,...