TCP/IP Listeners

Client applications can communicate with a remote XCICS region using sockets, either via direct socket API calls and EZASOKET APIs.

Users may write their own socket listener, or take advantage of the listeners supplyed by XCICS/TS: They emulate the behaviour of the IBM EZASOKET Listener provided by IBM and may be used to activate and communicate with a transaction from a remote application.

In order to enable activate the predefined socket listeners, a TCP service definition must be added to the XCICS/TS configuration file (see TCP/IP services). XCICS/TS will provide to automatically start up the defined TCP service(s). Each TCP service instance will be listening on the pre-defined port for incoming requestes, in order to forward them to the transaction server, where requests will be serviced.

The work mode of a TCP listener is specified in its configuration in the XCICS configuration file. The Direct Link mode is the default.

i.e.

add tcpipservice name=DEFAULT, port=8888, terminal=TCPD, direct, use_engines;
add tcpipservice name=IBMEZ,   port=8099, terminal=TCPC, classic;

For further information on how to use the predefined socket listeners please refer to the TCP/IP Sockets Programming Guide.