The LPAP control statement allows you to define a logical access point for the partner application in the local application. An LPAP statement is only required if communication with the partner application is to be carried out using the LU6.1 protocol. This logical access point is known as an LPAP partner. For each LPAP partner, you must define a logical name, possibly administration authorization for the partner application, maximum values for the message queue of the LPAP partner, and logical properties for communication with the partner application based on the LU6.1 protocol.
 | For information about generating LU6.1 connections see "Distributed processing via the LU6.1 protocol". |
The CON statement is used to assign a real partner application to the LPAP partner (see the CON statement in the section "CON - define a connection for distributed processing based on LU6.1"
|
additional operand on BS2000 systems |
1only permitted on BS2000 systems
lpapname | LPAP partner name, i.e. the logical name of the partner application, which is used by the program units of the local application to address the partner application. lpapname applies only in the local application, and can be up to eight characters in length. The specified name must be unique and must not be assigned to any other object in name class 1. See also section "Uniqueness of names and addresses". Together with the LTERM names and the OSI-LPAP names, the LPAP names form a common name class. |
BUNDLE= | master_lpap_name Name of the master LPAP. If this operand is specified, the LPAP becomes a slave LPAP of an LU6.1-LPAP bundle. You define the master_lpap_name with a MASTER-LU61-LPAP statement. Messages sent to the master LPAP of an LPAP bundle with an APRO call are distributed to the slave LPAPs of this LPAP bundle by openUTM. This allows the application to distribute the messages to be sent across several partner applications of the same type without the need to program this explicitly. |
DEAD-LETTER-Q= | specifies whether asynchronous messages to this LPAP partner that could not be sent due to a permanent error are to be saved in the dead letter queue. Monitoring of the number of messages in the dead letter queue is enabled and disabled with the MAX ...,DEAD-LETTER-Q-ALARM statement. |
YES | Asynchronous messages to this LPAP partner that could not be sent due to a permanent error are saved in the dead letter queue provided (in the case of message complexes) no negative confirmation job has been defined. |
NO | No asynchronous messages to this LPAP partner are saved in the dead letter queue. Default: NO Main jobs for message complexes (MCOM) with negative confirmation jobs are never saved in the dead letter queue as the negative confirmation jobs are activated in case of errors. If the number of messages in the dead letter queue is limited with QLEV, messages may be lost in the event of errors. If the number is not limited, the openUTM page pool generated must be sufficiently large. If there is a threat of a page pool bottleneck, the dead letter queue can be locked during application run with STATUS=OFF. |
KSET= | keysetname Name of the key set assigned to the partner application in the local application. The key set is defined using the KSET statement. The partner application can only start those services or address those remote services generated in the local application which are not locked, i.e. for which no lock code has been defined, and whose key codes are defined in the key set keysetname. The local application can thus be secured against unauthorized access by the partner application. Default: No key set, |
LNETNAME= | local_netname This is required only for heterogeneous links. local_netname identifies the VTAM name defined for the UTM application in the CICS or IMS partner application. Default: Blanks |
NETPRIO= | This operand is only supported on BS2000 systems. Transport priority to be used on the transport connection assigned to this LPAP partner. Default: MEDIUM |
PERMIT= | Authorization level of the partner application |
ADMIN | The partner application can execute administration functions in the local application. |
SATADM | The partner application can execute preselection functions in the local |
(ADMIN,SATADM) | The partner application can execute administration and preselection functions in the local application. Default: |
QLEV= | queue_level_number Maximum number of asynchronous messages that can be accommodated in the message queue of the LPAP partner. If this threshold value is exceeded, further APRO-AM calls to this LPAP partner are rejected with UTM message 40Z. Default: 32767 |
RNETNAME= | remote_netname This parameter is required only for heterogeneous links. remote_netname identifies the VTAM name of the CICS or IMS partner application. Default: Blanks |
SESCHA= | sescha_name The session characteristics that apply for communication between the local application and the partner application are defined under sescha_name in the SESCHA statement (see "SESCHA - define session characteristics for distributed processing based on LU6.1"). By specifying sescha_name here, you can assign this set of session characteristics to the LPAP partner. This is a mandatory operand. |
STATUS= | Specifies whether the LPAP partner is locked. The status can be changed during operation using the administration command KDCLPAP. |
ON | The LPAP partner is not locked. Connections can be established between the partner application and the local application or connections already exist. Default: ON |
OFF | The LPAP partner is locked. No connections can be established between the partner application and the local application. |