The data structure kc_timer_par_str is defined for the parameter type KC_TIMER_PAR. In the case of KC_GET_OBJECT, UTM returns the current settings for all timers of the UTM application in kc_timer_par_str.
The timers are set during the generation of the application and can be changed to adapt to the current situation during the application run using the operation code KC_MODIFY_OBJECT or with the help of the administration command KDCAPPL.
A change made to a timer only takes effect when the timer is reset for the first time after the change was made. The change does not affect timers already running. The changes are only in effect during the current application run.
mod1 | Data structure kc_timer_par_str |
x(GIR) |
|
x(GIR) |
|
x(GIR) |
|
x(GIR) |
|
x(GIR) |
|
- |
|
x(GIR) |
|
x(GIR) |
|
x(GIR) |
|
x(GIR) |
|
- |
|
- |
|
1 The contents of the field can be modified with KC_MODIFY_OBJECT; see "obj_type=KC_TIMER_PAR"
The fields in the data structure have the following meanings:
conrtime_min
(connection request time)
The time in minutes after which UTM is to attempt to re-establish a connection to a partner application, a client or a printer if the connection has been lost. conrtime is used for connections to:
printers to which UTM automatically establishes a connection at the start of the application (auto_connect='Y' in kc_pterm_str, "kc_pterm_str - Clients and printers") if this connection has not previously been shut down by administration functions.
printers to which UTM establishes a connection as soon as the number of print jobs for this printer exceeds the generated control value (LTERM partner with plev > 0). UTM will only attempt to re-establish the connection if the number of print jobs that are still pending after the connection loss is greater than or equal to the control value.
If conrtime_min!=0, UTM will also attempt to establish the connection to the printer even if administration functions have previously been used to shut it down explicitly.TS applications (ptype='APPLI' or 'SOCKET' in kc_pterm_str) to which UTM automatically establishes a connection at the start of the application (auto_connect='Y' in kc_pterm_str, "kc_pterm_str - Clients and printers") if this connection has not previously been shut down by administration functions.
OSI TP or LU6.1 partner applications to which UTM automatically establishes a connection when an application is started, if this connection has not previously been shut down by administration functions, or by UTM because a timer expired (idletime).
message routers (MUX) on BS2000 systems to which UTM automatically establishes a connection at the start of the application if it has not previously been shut down by administration functions.
If it is not possible to establish a connection to partners configured for automatic connection setup (at the start of an application or pursuant to a connection request issued using administration functions), or if such a connection is lost, then UTM will attempt to re-establish the connection, depending on the reason the connection was lost, in intervals of conrtime_min.
If conrtime_min='0', then UTM will not attempt to re-establish a logical connection.
Maximum value: '32767'
Minimum value: '0'
pgwttime_sec
The maximum amount of time in seconds that a program unit may wait for messages after a blocking function call. Blocking function calls are calls in which control is only returned to the program unit after the answer has been received (for example the KDCS call PGWT).
A process of the UTM application remains exclusively reserved for this program unit during this wait time.
Maximum value: '32767'
Minimum value: '60'
reswait_ta_sec
The maximum amount of time in seconds that a program unit may wait for a resource locked by another transaction: for example global secondary storage areas, user-specific long-term storage areas, terminal-specific long-term storage areas.
If the resource is not available after this time, then the application program will receive the appropriate return code KCRCCC.
The wait time specified in reswait_ta_sec is not significant if the lock is held by a multi-step transaction that is waiting for an input message (after a PEND KP or PGWT KP). In this case, all program units accessing the locked resource will immediately (without waiting for the time specified in reswait_ta_sec) receive the return code KCRCCC.
reswait_ta_sec='0' means that the program unit will not wait. A program unit run that attempts to access a locked resource will immediately receive the appropriate return code.
Maximum value: '32767'
Minimum value: '0'
reswait_pr_sec
The maximum amount of time in seconds that may be waited for a resource locked by another process. If this time is exceeded, then the application is terminated with an error message (see KC_MODIFY_OBJECT, obj_type=KC_TIMER_PAR as of "obj_type=KC_TIMER_PAR").
Maximum value: '32767'
Minimum value: '300'
term wait_in_ta_sec
The maximum amount of time in seconds that may pass between an output to a dialog partner and the reception of the dialog answer for multi-step transactions (i.e. in the PEND KP program). If the time termwait_in_ta_sec is exceeded, then the transaction is rolled back. The resources reserved by the transaction are released. The connection to the partner is closed.
Maximum value: '32767'
Minimum value: '60'
termwait_end_ta_sec
Does not contain a valid value. The time in seconds that UTM will wait for an input from the dialog partner after a transaction terminates or after signing on (KDCSIGN). This value is defined on a partner-specific basis as of openUTP V5.0. You will receive further information on this timer when you call KC_GET_OBJECT with obj_type KC_PTERM or KC_TPOOL (field idletime in "kc_pterm_str - Clients and printers" and "kc_tpool_str - LTERM pools for the application").
logackwait_sec (only on BS2000 systems)
The maximum amount of time in seconds that UTM is to wait for a logical print confirmation from the printer or for a transport confirmation for an asynchronous message sent to another application (created with the KDCS call FPUT).
If the confirmation is not received after this time, for example because the printer is out of paper, then UTM closes the logical connection to the device.
Minimum value: '10'
Maximum value: '32767'
The following timers are only used for UTM applications with distributed processing via LU6.1 or OSI TP.
conctime1_sec
(connection control time)
The time in seconds that the establishing of a connection to a session (LU6.1) or association (OSI TP) is to be monitored. If the session or association is not established within the specified time, then UTM closes the transport connection to the partner application. This prevents a transport connection from being disabled due to an unsuccessful attempt to establish a connection to a session or association. This can occur when a message needed to establish the connection becomes lost.
conctime1_sec='0' means that session setup is not monitored in the case of LU6.1 connections (UTM waits indefinitely). In the case of OSI TP connections, UTM waits for up to 60 seconds for an association to be set up.
Minimum value: '0'
Maximum value: '32767'
conctime2_sec
The maximum wait time in seconds that will be waited for the confirmation from the receiver when sending an asynchronous message. After the time in conctime2_sec runs out, UTM closes the transport connection. The asynchronous job is not lost, and it remains in the local message queue. Monitoring this time prevents a connection from not being used because a confirmation was lost and also prevents UTM from not being informed by the transport system of the loss of a connection.
conctime2_sec = '0' means that the connection will not be monitored.
Minimum value: 0
Maximum value: 32767
ptctime_sec
This parameter is only significant for distributed processing via LU6.1 connections. ptctime_sec specifies the maximum time in seconds that a job-receiving service in the PTC (prepare to commit, transaction status P) state will wait for confirmation from the job-submitting service. After this time is up, the connection to the jobsubmitter is closed, the transaction in the job-receiving service is rolled back and the service is terminated. This can eventually lead to 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 with ENDPET if possible.
ptctime_sec = '0' means that there is no limit to the time that will be waited for confirmation.
Minimum value: 0
Maximum value: 32767
qtime1
Indicates the maximum time in seconds that a dialog service may wait for the receipt of messages for USER, TAC or temporary queues.
qtime2
Indicates the maximum time in seconds that an asynchronous service may wait for the receipt of messages for USER, TAC or temporary queues.