These operations relate to an LPAP partner, i.e. to the logical properties of an LU6.1 partner application or to the connection to this partner application.
You must specify the name of the LPAP partner in the identification area (field kc_name8 of the union kc_id_area). This is the name that was defined during KDCDEF generation in the LPAP statement for the partner application. In the data area you must pass the data structure kc_lpap_str with the new values of the properties.
Possible modifications
Disable an LPAP partner or release a disabled LPAP partner.
It is no longer possible to establish a connection to the partner application through a disabled LPAP partner.
Specify the following in the data structure kc_lpap_str.
Field name
Meaning
state='N'
The LPAP partner is to be disabled. There must be no connection to the partner application in existence at the time the partner is disabled. You must shut down existing connections before disabling the partner with connect_mode='N' or quiet_connect='Y'.
It is not possible to shut down the connection and disable the LPAP partner in a single call as shutting down the connection may take a relatively long time.state='Y'
The LPAP partner is to be released, i.e. any existing lock is to be cancelled.
Period of validity/ transaction management: type GPD ("KC_MODIFY_OBJECT - Modify object properties and application parameters")
Activate or deactivate automatic connection setup.
Automatic connection setup means that, whenever the application starts, UTM attempts to establish a connection to the partner application.
If automatic connection is defined in both applications (the local application and the partner application), the connection between the two of them is established automatically as soon as they are both available.
Specify the following in the data structure kc_lpap_str:
Field name
Meaning
auto_connect='Y'
As of the next application start, UTM is to attempt to establish the connection to the partner application automatically whenever it starts.
auto_connect='N'
As of the next application start, the connection to the partner application is no longer to be established automatically.
Period of validity/ transaction management: type GPD ("KC_MODIFY_OBJECT - Modify object properties and application parameters")
Change the period of time for which UTM monitors the idle state of a session to the partner application; i.e. if the session is not occupied by a job, UTM waits for this period of time before shutting down the connection.
Specify the following in the data structure kc_lpap_str:
Field name
Meaning
idletime_sec[5]
Specify in idletime_sec the time in seconds for which UTM is to monitor the idle state of a session with the partner application. idletime_sec = '0' means that the idle state is not monitored.
Maximum value: '32767'
Minimum value: '60',
In the case of values that are smaller than 60 but not equal to 0 then the value 60 is used.Period of validity/ transaction management: type GPD ("KC_MODIFY_OBJECT - Modify object properties and application parameters")
The timer modification only takes effect when the session next reaches the idle state, but not before the end of the program unit run (PEND) in which the call is processed.
Set up or shut down the connection to the partner application.
The connection can be shut down in two ways:
The connection can be shut down immediately, i.e. UTM shuts down the connection irrespective of whether or not jobs are currently being processed via the connection (connect_mode).
You can set the connection to QUIET (quiet_connect). QUIET means that UTM shuts down the connection to the partner application as soon as the sessions generated for the LPAP partner are no longer occupied by jobs (dialog or asynchronous jobs).
However, no new dialog jobs are accepted for the LPAP partner. New asynchronous jobs are accepted, but no longer sent; they remain in the output queue.
Field name
Meaning
connect_mode='Y'
UTM is to establish the connection to the partner application.
If the LPAP partner is disabled, it must be released in a separate transaction before the connection is established (state='Y').
connect_mode='N'
The connection to the partner application is to be shut down immediately.
If the connection is shut down with connect_mode = 'N', it is possible that services or conversations may be aborted abnormally. It is better to shut down the connection with quiet_connect = 'Y'.Period of validity / transaction management: type A ("KC_MODIFY_OBJECT - Modify object properties and application parameters")
Field name
Meaning
quiet_connect='Y'
The property QUIET is set for the connection to the partner application.
The property QUIET can be reversed with connect_mode='Y'.
Period of validity / transaction management: type IR ("KC_MODIFY_OBJECT - Modify object properties and application parameters")
The fields connect_mode and quiet_connect cannot be set simultaneously within a call. Moreover, connect_mode='Y' cannot be set simultaneously with state ='N'. If a KC_MODIFY call with connect_mode='N' is transmitted for a connection which has been set to QUIET, the connection is then shut down immediately.
connect_mode='N' “overwrites” quiet_connect='Y'.
Activate or deactivate the BCAM trace for the connection to the partner application.
The precondition for LPAP-specific activation is that the BCAM trace is not generally activated, i.e. the trace is either completely deactivated or is only explicitly activated for selected LTERM/LPAP partners or USERs.
The precondition for LPAP-specific deactivation is that the BCAM trace can be deactivated for a specific LPAP partner only if the BCAM trace is not generally activated.
You will find information about the general activation and deactivation of the BCAM trace in the description of the data structure kc_diag_and_account_par_str starting from chapter "kc_diag_and_account_par_str - Diagnostic and accounting parameters".
Field name
Meaning
bcam_trace='Y'
The BCAM trace is specifically activated for this LPAP partner. Events are logged on all transport connection to the partner application assigned to this LPAP partner.
When the trace function is activated, each application process creates its own trace file.bcam_trace='N'
The BCAM trace is explicitly deactivated for this LPAP partner.
The trace files are closed only when the trace function is deactivated generally (object type KC_DIAG_AND_ACCOUNT_PAR; "obj_type=KC_DIAG_AND_ACCOUNT_PAR").Period of validity / transaction management: type IR ("KC_MODIFY_OBJECT - Modify object properties and application parameters")
Enables/disables the saving of asynchronous messages in the dead letter queue for this LPAP partner. This can prevent the loss of messages for this LPAP partner in case of permanent errors.
Specify the following in the data structure kc_lpap_str:
Field name
Meaning
dead_letter_q='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.
dead_letter_q='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.
Period of validity / transaction management: type GPD ("KC_MODIFY_OBJECT - Modify object properties and application parameters")
If the LPAP is the master LPAP of a LPAP bundle then you can only modify the state field.
| KDCLPAP ("KDCLPAP - Administer connections to (OSI-)LPAP partners") / KDCDIAG ("KDCDIAG - Switch diagnostic aids on and off") for the BCAM trace |
