kc_lpap_str - Properties of LU6.1 partner applications

The data structure kc_lpap_str is defined for the object type KC_LPAP. In the case of KC_GET_OBJECT, UTM returns the properties of an LPAP partner in kc_lpap_str.

An LPAP partner is a logical connection point for an LU6.1 partner application. LPAP partners are defined during the static generation with KDCDEF and are assigned to the LU6.1 partner applications. You can make the assignment to a real partner application at generation or dynamically when creating a new CON object.

mod1	Data structure kc_lpap_str
-	char lp_name[8];
-	char kset[8];
-	char lnetname[8];
-	char netprio; (only on BS2000 systems)
-	char permit;
-	char qlev[5];
-	char rnetname[8];
x(GPD)	char state;
x(GPD)	char auto_connect;
-	char contwin;
-	char dpn[8];
x(GPD)	char idletime_sec[5];
-	char map; (only on Unix, Linux and Windows systems)
-	char paccnt[2];
-	char plu;
x(A)	char connect_mode;
x(IR)	char quiet_connect;
x(IR)	char bcam_trace;
-	char out_queue[5];
-	char nbr_dputs[10];
-	char master[8];
-	char bundle;
-	char out_queue_ex[10];
x(GPD)	char dead_letter_q;

¹ The contents of the field can be modified using KC_MODIFY_OBJECT; see "obj_type=KC_LPAP"

The fields in the data structure have the following meanings:

lp_name	Contains the name of the LPAP partners, i.e. the logical name of the partner application. Through this name the local application initiates communication with the partner application. lp_name only has meaning in the local application.
kset	Contains the name of the key set that is assigned to the partner application. The key set specifies the access privileges of the partner application within the local application, meaning that the partner application may only use the transaction codes that are either secured by a lock code for which the key set contains the appropriate key or access code or that are not secured by a lock code.
lnetname	lnetname is only relevant for heterogeneous links. lnetname contains the name of the local UTM application under which the local application is known in the partner application.
netprio	(only on BS2000 Systems) Contains the transport priority used in the transport connection assigned to this LPAP partner.
	'M'	"Medium" transport priority
	'L'	"Low" transport priority
permit	Specifies the privileges that the partner application has within the local application.
	'A'	(ADMIN) The partner application has administration privileges, it may execute all administration functions in the local application.
	'N'	(NONE) The partner application does not have any administration privileges. Only on BS2000 systems: If the local application is a UTM application on a BS2000 system, then the partner application is also not allowed to execute any UTM SAT administration functions.
	'B'	(BOTH, only on BS2000 systems) The partner application may execute administration functions as well as UTM SAT administration functions in the local application.
	'S'	(SAT, only on BS2000 systems) The partner application has UTM SAT administration privileges. It may execute preselection functions in the local application, i.e. it can enable or disable the SAT logging for certain events.
qlev	(queue level) qlev specifies the maximum number of asynchronous messages that may be in the local message queue for the partner application. If this control value is exceeded, then any additional asynchronous jobs sent to the partner application will be rejected (i.e. '40Z' will be returned for any APRO-AM calls thereafter).
rnetname	rnetname is only relevant for heterogeneous links. rnetname contains the VTAM name of the partner CICS application or IMS application.
state	Contains the status of the LPAP partner:
	'Y'	The LPAP partner is not disabled. A connection to the partner application can be established or there already is an established connection.
	'N'	The LPAP partner is disabled. No connections to the partner application can be established.
auto_connect	Specifies if the connection to the partner application is automatically established when the local application is started:
	'N'	The connection is not automatically established; it must be established by the administrator.
	'Y'	When the local application is started, UTM will automatically establish the connection to the partner application as long as the partner application is available at that time.
	If automatic connecting is defined in both applications (local application and partner application), then the connection between the two is automatically established as soon as both applications are available.
contwin	(contention winner) Specifies if the partner application is the contention winner in the session connecting the local application and the partner application. The contention winner administers the session and controls how resources are allocated for jobs in the session. In any case, jobs from the local application as well as from the partner application may be started. In case of a conflict, such as when the local and the partner application want to start a job at the same time, the job from the contention winner will be started in the session.
	'Y'	The partner application is the contention winner.
	'N'	The local application is the contention winner.
dpn	(destination process name) dpn is only meaningful for connections to IBM systems. dpn contains the name of the instance that processes asynchronous messages.
idletime_sec	Contains the maximum time in seconds that a session to the partner application may be in the idle state before UTM closes the connection to the partner application. The idle state means that the session is not handling any jobs. idletime_sec = '0' means that the idle state will not be monitored. Minimum value: '60' Maximum value: '32767'
map	(only on Unix, Linux and Windows Systems) Specifies whether UTM performs a code conversion (ASCII <-> EBCDIC) for user messages without any formatting flags which are exchanged between the partner applications.
	'U'	(USER) UTM does not convert user messages, i.e. the data in the message is transmitted unchanged to the partner application.
	'1', '2', '3', '4' (SYS1 | SYS2 | SYS3 | SYS4)
		UTM converts the user messages according to the code tables provided for the code conversion, i.e.: Prior to sending, the code is converted from ASCII to EBCDIC. After receival, the code is converted from EBCDIC to ASCII. openUTM assumes that the messages contain only printable characters.
	For more information on code conversion, please refer to the openUTM manual „Programming Applications with KDCS”; keyword „code conversion".
paccnt	(pacing Count) Contains the number of parts of a long message that the local application may receive without having to acknowledge. A pacing value in paccnt that is too large can lead to bottlenecks in the network. If paccnt = '0', there is no limit to the number of parts of a message that can be received before acknowledging.
plu	(primary logical unit) Specifies if the partner application is responsible for establishing the session, i.e. if the partner application is the ’primary logical unit’ (PLU).
	'Y'	The partner application is the ’primary logical unit’.
	'N'	The local application is the ’primary logical unit’.
connect_mode	Specifies the status of the connection to the partner application.
	'Y'	The partner application is currently connected to the application.
	'N'	The partner application is not currently connected to the application.
	'W'	UTM is currently attempting to establish a connection to the partner application (WAIT).
quiet_connect	Specifies if the QUIET property is set for the connection to the LPAP partner. QUIET means that UTM closes the connection to the partner application as soon as the sessions generated for the partner application do not contain any more jobs. No more new dialog jobs are accepted for the partner application.
	'Y'	The QUIET property is set.
	'N'	The QUIET property is not set.
bcam_trace	Specifies whether the BCAM trace is explicitly enabled or disabled for the LPAP partner of the partner application. The trace function that monitors connectionspecific activity within a UTM application (for example, the BCAM trace function on BS2000 systems) is called the BCAM trace. The BCAM trace can be enabled for all connections of the application (i.e. for all LPAP and LTERM partners) or explicitly for certain LTERM or LPAP partners.
	'Y'	The BCAM trace was explicitly enabled for this LPAP partner. If the BCAM trace was enabled for all connections of the UTM application, then 'N' will be returned in bcam_trace. You can determine if the BCAM trace is enabled for all connections by, for example, calling KC_GET_OBJECT with the KC_DIAG_AND_ACCOUNT_PAR parameter type. Then bcam_trace='Y' will be returned in kc_diag_and_account_par_str.
	'N'	The BCAM trace was not explicitly enabled for this LPAP partner.
	You can enable or disable the BCAM trace during the application run.
out_queue	The number of messages currently being stored temporarily in the local message queue of the partner application and which must still be sent to the partner application. If the number of messages is greater than 99999, then the number is not displayed in full. You should therefore use the field out_queue_ex since larger numbers can be entered in full here.
nbr_dputs	The number of pending time-driven jobs for this LPAP whose starting time has not yet been reached.
master	If the LPAP partner is a slave in an LU6.1 LPAP bundle then the master LPAP partner of the bundle is returned in master.
bundle	Specifies whether the LPAP partner belongs to an LPAP bundle.
	'N'	The LPAP partner does not belong to an LPAP bundle.
	'M'	The LPAP partner is the master of an LPAP bundle.
	'S'	The LPAP partner is a slave in an LPAP bundle.
out_queue_ex	see out_queue
dead_letter_q	specifies whether an asynchronous message to an LPAP partner is saved in the dead letter queue if it could not be sent because of a permanent error.
	'Y'	Asynchronous messages to this LPAP partner which could not be sent because of a permanent error are saved in the dead letter queue, as long as (in case of message complexes) no negative confirmation job was defined.
	'N'	Asynchronous messages to this LPAP partner which could not be sent because of a permanent error are not saved in the dead letter queue but deleted.