obj_type=KC_TIMER_PAR

Application timer settings are to be modified. You must enter the data structure kc_timer_par_str in the data area.

Possible modifications

The following table shows which timers can be modified. You can modify as many of these timers as you wish in a single call.

Field name	Meaning
conrtime_min[5]	Specify here the time in minutes after which UTM is to attempt to re-establish a lost connection to a printer or a TS application. The precondition is that the connection must previously have been established automatically by UTM (kc_pterm_str.auto_connect='Y' or kc_lterm_str.plev > 0).
	At conrtime_min='0' UTM makes no attempt to re-establish a lost connection.
	Maximum value: '32767' Minimum value: '0'
pgwttime_sec[5]	The maximum time in seconds which a program unit is to wait for the arrival of messages after a blocking function call (e.g. PGWT). During this waiting period, one process remains exclusively reserved by this program unit.
	Maximum value: '32767' Minimum value: '60'
reswait_ta_sec[5]	The maximum time in seconds which a program unit is to wait for a device currently being used by another transaction.
	reswait_ta_sec='0' means that the program unit does not wait. A program unit run wishing to access a reserved device immediately receives an appropriate return code.
	Maximum value: '32767' Minimum value: '0'
reswait_pr_sec[5]	The maximum time in seconds which UTM is to wait for a device currently being used by another process. If this time is exceeded, the application terminates with a UTM error message. It should be noted that the value of reswait_pr_sec must be as long as the longest (real time) processing time for the following cases: In TS applications that are not SOCKET applications (clients with PTYPE=APPLI) the devices are locked for the duration of a processing stage, including a VORGANG exit at the beginning and/or end of the service. At the end of the service, the devices are reserved for as long as the VORGANG exit program is running.
	Minimum value: '300', Maximum value: '32767'
	If you specify a value of < 300, the call is rejected.
termwait_in_ta_sec[5]	The maximum time in seconds in a multi-step transaction (i.e. in the PEND KP program) which may elapse between an output to a dialog partner and the subsequent dialog response.
	If the time termwait_in_ta_sec is exceeded, the transaction is rolled back. The devices reserved by the transaction are released. The connection to the partner is shut down.
	Maximum value: '32767' Minimum value: '60'
logackwait_sec[5]	Only on BS2000 systems: The maximum time in seconds which UTM is to wait for a logical print confirmation from the printer or a transport confirmation for an asynchronous message to another application (created using the KDCS call FPUT). If the confirmation does not arrive after this time, e.g. due to a printer being out of paper, UTM shuts down the logical connection to the device.
	Minimum value: '10' Maximum value: '32767'
The following timers are relevant only in the context of UTM applications with distributed processing via LU 6.1 or OSI TP.
conctime1_sec[5]	The time in seconds for monitoring the setup of a session (LU6.1) or association (OSI TP). If the session or association is not established within the specified time, UTM shuts down the transport connection to the partner application.
	conctime1_sec='0' means: for LU6.1 connections: session setup is not monitored (UTM will wait indefinitely). for OSI TP connections: UTM waits up to 60 seconds for an association to be set up.
	Minimum value: '0' Maximum value: '32767'
conctime2_sec[5]	The maximum waiting time in seconds for a confirmation from the recipient when transferring an asynchronous message. Once the time conctime2_sec has expired, UTM shuts down the transport connection. The asynchronous job is not lost, but remains in the local message queue.
	conctime2_sec = '0' means that monitoring is not performed.
	Minimum value: '0' Maximum value: '32767'
ptctime_sec[5]	This timer is relevant only in the context of distributed processing via LU6.1 connections. ptctime_sec defines the maximum time in seconds which a local job-receiving service will wait in the PTC state (prepare to commit, transaction status P) for a confirmation from the job-submitting service. When the time expires, the connection to the job submitter is shut down, the transaction in the job-receiving service is rolled back and the service terminated. This may possibly result in a mismatch. If KDCSHUT WARN or GRACE has already been issued for the application and the value of ptc_time_sec is not 0, then the waiting time is chosen independently of ptc_time_sec in such a way that the transaction is rolled back before the application is terminated in order to avoid abnormal termination of the application with ENDPET if possible.
	ptctime_sec = '0' means that UTM waits indefinitely for a confirmation.
	Minimum value: '0' Maximum value: '32767'

See also "kc_timer_par_str - Timer settings" for further information.

Period of validity / transaction management: type GIR ("KC_MODIFY_OBJECT - Modify object properties and application parameters")

The modifications do not take effect on timers which are already running; they only apply to timers started after the modification.

Some of the modifications can also be performed with the administration command KDCAPPL ("KDCAPPL - Change properties and limit values for an operation").