Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

LU6.1-LPAP bundles

LU6.1=LPAP bundles allow messages to be distributed automatically across several LPAP partners. If a UTM application has to exchange a very large number of messages with a partner application then load distribution may be improved by starting multiple instances of the partner application and distributing the messages across the individual instances. In an LU6.1-LPAP bundle, openUTM is responsible for distributing the messages to the partner application instances. To achieve this, the program units in the APRO call must address the MASTER-LU61-LPAP.

One application scenario for distributing messages in this way is communication between a UTM application and a UTM cluster application. This allows messages to the UTM cluster application to be distributed across the individual node applications. You will find detailed information on this in section "LU6.1-LPAP bundles of a standalone application with a UTM cluster application".

An LU6.1-LPAP bundle consists of a master LPAP and multiple slave LPAPs. The slave LPAPs are assigned to the master LPAP on generation. In normal circumstances, the individual slave LPAPs address different partner applications.

Figure 6: Example of an LU6.1-LPAP bundle

Generating an LU6.1-LPAP bundle

MASTER-LU61-LPAP statement in section "MASTER-LU61-LPAP - Define the master LPAP of an LU6.1-LPAP bundle"
Specifies the name and properties of the master LPAP in an LU6.1-LPAP bundle.

  • master-lpap-name

    Name of the master LPAP.

  • STATUS=

    Specifies whether messages can be sent to this LPAP bundle.

LPAP statement in section "LPAP - define an LPAP partner for distributed processing based on LU6.1"
The following properties must be specified to generate a slave LPAP:

  • lpap-name

    Name of the slave LPAP.

  • BUNDLE=master-lpap-name

    Name of the master LPAP. The master LPAP specified here must be defined in a MASTER-LU61-LPAP statement. If you specify BUNDLE, this LPAP becomes a slave LPAP of the specified master LPAP.

    MASTER-LU61-LPAP master , ...
    LPAP slave-lpap , BUNDLE= master , ...

CONs of LPAPs belonging to an LU6.1-LPAP bundle

  • No physical connections (CONs) can be assigned to a master LPAP. This means that it cannot be specified as the LPAP in a CON statement. The master LPAP always uses the connections assigned to the slave LPAPs.

Distribution of messages

For details, refer to the section "Distributing messages" in chapter "LU6.1-LPAP bundles".

Display in the KB header

For details, refer to the section "Information displayed in the KB header" in chapter "LU6.1-LPAP bundles".