Usage of LU6.1-LPAP bundles for communication with an UTM cluster application on Unix, Linux and Windows systems

Note the following when generating LU6.1 communication between a standalone partner application and a UTM cluster application:

• A partner application must generate one LPAP with a specific number of sessions and connections for each node of the UTM cluster application with which it wants to communicate.

• To address the UTM cluster application, an LU6.1-LPAP bundle whose slave LPAPs are assigned to the cluster node should be generated in the partner application (see "MASTER-LU61-LPAP - Define the master LPAP of an LU6.1-LPAP bundle" ).

• In the UTM cluster application, more sessions (LSES) than connections (CON) must be generated for the LPAP that represents the partner application: One session per cluster node must be generated for each connection.

  Each cluster node requires only exactly the number of connections assigned to each LPAP in the partner application for the corresponding LPAP. However, because all cluster nodes have identical generations, the sessions for all the LPAPs of the partner application must be generated in every cluster node.

• During generation, the LU6.1 sessions must be explicitly assigned to the node applications. To do this, define the reference name of the node application in the NODE-NAME parameter of the CLUSTER-NODE statement and specify this name in the NODE-NAME parameter of the LSES statement. As a result, the "right" session is selected when a session is established with a partner application.

Example:

The example below shows a generation in which the standalone application SA on the host HOSTSA is linked to the UTM cluster application CA on the cluster nodes NODECAX, NODECAY and NODECAZ. 4 connections between the standalone application and each of the node applications are generated. A MASTER-LU61-LPAP is generated for the LPAPs that represent the node applications in the standalone application. This represents the UTM cluster application.

Standalone application SA on HOSTSA	UTM cluster application CA on NODECAX/Y/Z
	CLUSTER-NODE NODE-NAME=NODECAX - , HOSTNAME=NODECAX, - , FILEBASE=BASE1 CLUSTER-NODE NODE-NAME=NODECAY - , HOSTNAME=NODECAY, - , FILEBASE=BASE2 CLUSTER-NODE NODE-NAME=NODECAZ - , HOSTNAME=NODECAZ, - , FILEBASE=BASE3
BCAMAPPL SA11 BCAMAPPL SA12 MASTER-LU61-LPAP MLPAPCA  LPAP LPAPCAX,SESCHA=SESCHCA- , BUNDLE=MLPAPCA LPAP LPAPCAY,SESCHA=SESCHCA- , BUNDLE=MLPAPCA LPAP LPAPCAZ,SESCHA=SESCHCA- , BUNDLE=MLPAPCA  SESCHA SESCHCA, CONTWIN=NO, PLU=YES	BCAMAPPL CA11 BCAMAPPL CA12 LPAP LPAPSA, SESCHA=SESCHSA SESCHA SESCHSA, CONTWIN=YES, PLU=NO
CON CA11, PRONAM=NODECAX – , BCAMAPPL=SA11, LPAP=LPAPCAX  CON CA12, PRONAM=NODECAX – , BCAMAPPL=SA11, LPAP=LPAPCAX CON CA11, PRONAM=NODECAX –  , BCAMAPPL=SA12, LPAP=LPAPCAX CON CA12, PRONAM=NODECAX – , BCAMAPPL=SA12, LPAP=LPAPCAX	CON SA11, PRONAM=HOSTSA – , BCAMAPPL=CA11, LPAP=LPAPSA CON SA11, PRONAM=HOSTSA – , BCAMAPPL=CA12, LPAP=LPAPSA CON SA12, PRONAM=HOSTSA – , BCAMAPPL=CA11, LPAP=LPAPSA CON SA12, PRONAM=HOSTSA – , BCAMAPPL=CA12, LPAP=LPAPSA
CON CA11, PRONAM=NODECAY – , BCAMAPPL=SA11, LPAP=LPAPCAY CON CA12, PRONAM=NODECAY –  , BCAMAPPL=SA11, LPAP=LPAPCAY CON CA11, PRONAM=NODECAY – , BCAMAPPL=SA12, LPAP=LPAPCAY  CON CA12, PRONAM=NODECAY – , BCAMAPPL=SA12, LPAP=LPAPCAY
CON CA11, PRONAM=NODECAZ –  , BCAMAPPL=SA11, LPAP=LPAPCAZ CON CA12, PRONAM=NODECAZ – , BCAMAPPL=SA11, LPAP=LPAPCAZ  CON CA11, PRONAM=NODECAZ – , BCAMAPPL=SA12, LPAP=LPAPCAZ CON CA12, PRONAM=NODECAZ –  , BCAMAPPL=SA12, LPAP=LPAPCAZ
LSES SAA2CAX, RSES= CA12SA1- , LPAP=LPAPCAX LSES SAB2CAX, RSES= CA12SA2- , LPAP=LPAPCAX LSES SAC2CAX, RSES= CA12SA3- , LPAP=LPAPCAX LSES SAD2CAX, RSES= CA12SA4- , LPAP=LPAPCAX	LSES CA12SA1, RSES= SAA2CAX- , LPAP=LPAPSA - , NODE-NAME=NODECAX LSES CA12SA2, RSES= SAB2CAX- , LPAP=LPAPSA - , NODE-NAME=NODECAX LSES CA12SA3, RSES= SAC2CAX- , LPAP=LPAPSA  , NODE-NAME=NODECAX LSES CA12SA4, RSES= SAD2CAX- , LPAP=LPAPSA - , NODE-NAME=NODECAX
LSES SAA2CAY, RSES= CA22SA1- , LPAP=LPAPCAY LSES SAB2CAY, RSES= CA22SA2- , LPAP=LPAPCAY LSES SAC2CAY, RSES= CA22SA3- , LPAP=LPAPCAY LSES SAD2CAY, RSES= CA22SA4- , LPAP=LPAPCAY	LSES CA22SA1, RSES= SAA2CAY- , LPAP=LPAPS - , NODE-NAME=NODECAY LSES CA22SA2, RSES= SAB2CAY- , LPAP=LPAPSA - , NODE-NAME=NODECAY LSES CA22SA3, RSES= SAC2CAY- , LPAP=LPAPSA - , NODE-NAME=NODECAY LSES CA22SA4, RSES= SAD2CAY- , LPAP=LPAPSA - , NODE-NAME=NODECAY
LSES SAA2CAZ, RSES= CA32SA1- , LPAP=LPAPCAZ LSES SAB2CAZ, RSES= CA32SA2- , LPAP=LPAPCAZ LSES SAC2CAZ, RSES= CA32SA3- , LPAP=LPAPCAZ LSES SAD2CAZ, RSES= CA32SA4- , LPAP=LPAPCAZ	LSES CA32SA1, RSES= SAA2CAZ- , LPAP=LPAPSA - , NODE-NAME=NODECAZ LSES CA32SA2, RSES= SAB2CAZ- , LPAP=LPAPSA - , NODE-NAME=NODECAZ LSES CA32SA3, RSES= SAC2CAZ- , LPAP=LPAPSA - , NODE-NAME=NODECAZ LSES CA32SA4, RSES= SAD2CAZ- , LPAP=LPAPSA - , NODE-NAME=NODECAZ