In the case of a link by means of the LU6.1 protocol, for communication between the local UTM application and a remote application you must define one or more transport connections and sessions by means of which the communication relationships are set up.
For the entry of a transport connection, call KC_CREATE_OBJECT for the object type KC_CON. To define a session, call KC_CREATE_OBJECT for the object type KC_LSES.
The prerequisite is that LPAP partners must be known and session properties defined in each application.
A number of CON and LSES objects must be created for each LPAP; the number of CON and LSES objects determines the number of parallel connections that are possible with a partner application via an LPAP.
In cluster applications (Unix, Linux and Windows systems), it is necessary to generate, for each CON object, as many LSES objects as there are node applications in order to enable the partner application to communicate with all the node applications.
A CON object and an LSES object are created for each parallel connection via an LPAP and assigned to the LPAP. Every CON object and every LSES object in each of the applications involved must be created appropriately so that the following applies:
A CON name in the local application is the same as a BCAMAPPL name in the remote application and vice versa.
An LSES name in the local application is the same as an RSES name in the remote application and vice versa.
CAUTION!
It is not permissible for an LPAP name to create a number of CON objects that lead to different applications or are assigned to different LPAPs in the partner application via their corresponding CON objects.
Such configurations are not recognized by UTM and lead to errors when connections and sessions are set up and when sessions are restarted.