SNA and TCP/IP APPC sessions

In order to allow remote regions to connect the local XCICS region to perform inter system communication (i.e. starting transactions for DTP or to request services such DPL or RFA), some server sessions must be defined in the XCICS configuration file.

Depending on the transport layer, two different directives are used.

SNA sessions

SNA sessions are defined by means of the define sessions directive.

Each session is background terminal defined in TCT, which name is composed by the one-byte prefix followed by a counter.

define session

Syntax

define sessions

size=<value>,
[luname=<value>],
[prefix=<value>,];

size

This is the number of parallel session to be activated.

luname

specifies the LU alias for the incoming connections. If not specified, XCICS assigns the name specified by the general setting default_inbound_lu, if declared, or the application name itself.

prefix

If specified, overrides the default character ("-") for terminal name generation.

TCP/IP sessions

TCP/IP sessions are activated by a TCP server and are defined by means of the add tcpserver directive.

The TCP server listens for incoming TCP/IP connections and activates a background task to serve the request

define session

Syntax

add tcpserver

name=<value>,
port=<value>
[,terminal=<value>],
isc;

name

Name of the TCP server.

port

Number of the TCP port, where the server is waiting for connections.

terminal

(Optional) Name of the virtual terminal where the task is to be started.

isc

It is mandatory.