LSES - define a session name for distributed processing based on LU6.1

The LSES control statement required only for communication based on the LU6.1 protocol.

For more information about generating LU6.1 connection see "Distributed processing via the LU6.1 protocol".

It allows you to define a common session name for the connection established between two applications for distributed processing. This name is then used to resume an interruptedcommunication process. LSES also enables you to allocate the session to an LPAP partner. For this purpose, each LPAP statement must be assigned at least one LSES statement. In the case of parallel sessions, several different session names must be defined for the LPAP partner lpapname.

An LPAP partner must be always be assigned the same number of sessions (LSES statement) and transport connections (CON statement).

Exception: More LSES statements than CON statements can be assigned to an LPAP partner for a UTM cluster application.

If a session is defined for the local application with LSES AAA, RSES=BBB, this sessionmust be defined with LSES BBB, RSES=AAA in the generation of the partner application.

To ensure that the USER and session name need not be unique in two connected applications, the common session name consists of two parts:
sessionname = local_sessionname + remote_sessionname

LSES	local_sessionname     ,LPAP=lpapname [ ,RSES=remote_sessionname ] addtional operand on Unix, Linux and Windows systems [ ,NODE_NAME=nodename ]

local_sessionname	Name of the session in the local application. The specified name must be unique and must not be assigned to any other object in name class 2. See also "Uniqueness of names and addresses".
LPAP=	lpapname Name of the LPAP partner assigned to the partner application. local_sessionname is used for communicating with the partner application assigned to the LPAP partner lpapname in the local application.
NODE-NAME=	node_name This parameter is only relevant for UTM cluster applications on Unix, Linux and Windows systems. To ensure that openUTM is able to select the "right" session when establishing a session with a partner application, you must assign the LU6.1 sessions to the node applications via the NODE-NAME operand. The following dependencies apply: The name specified in NODE-NAME must be defined in a CLUSTER-NODE statement using the identically named NODE-NAME operand. The host name for the node (HOSTNAME) specified in this CLUSTER-NODE statement must be referenced in a CON statement in the partner application (PRONAM). The LPAP name specified in this CON statement must, in the partner application, be specified in an LSES statement that matches the LSES statement generated here. I.e. the local session name in the partner application corresponds to the RSES name that is specified here and vice versa. See also "Generation notes" and "Procedure when generating LU6.1 connections". Default value: eight spaces, i.e. not a node application. In the case of standalone applications, NODE-NAME may not contain any values other than spaces.
RSES=	remote_sessionname Remote half session name Default: remote_sessionname=local_sessionname is set, if RSES is not named.