obj_type=KC_TPOOL

This operation relates to an LTERM pool for the UTM application.

In the identification area you must pass the name of the LTERM pool (LTERM prefix). For this the field kc_name8 of the union kc_id_area is available.

In the data area you must pass the data structure kc_tpool_str with the new values of the properties.

Possible modification

• You can increase or decrease the number of clients which may be connected concurrently via this LTERM pool, i.e. you specify how many LTERM partners of the LTERM pool are to be released or disabled. One client can connect to the application via each enabled LTERM partner in the LTERM pool. The number of LTERM partners included in the LTERM pool, i.e. the maximum number of LTERM partners which can be permitted for this LTERM pool, is defined during KDCDEF generation. Specify the following in the data structure kc_tpool_str:

  Field name	Meaning
  state='N' state_number=...	Of the total number of LTERM partners in this LTERM pool (see kc_tpool_str.max_number in chapter "kc_tpool_str - LTERM pools for the application"), the number specified in state_number is to be disabled. The number of permitted LTERM partners for this LTERM pool is consequently: max_number - state_number.
  	If the entire LTERM pool is to be disabled, you must specify the value of max_number in state_number.
  	If you want to release all the LTERM partners in the LTERM pool, specify state_number= '0'.
  	Minimum value for state_number: '0' Maximum value for state_number: the maximum number returned in kc_tpool_str.max_number
  state='Y' state_number=...	Of the total number of LTERM partners, only the number specified in state_number is to be permitted.
  	If all the LTERM partners in the LTERM pools are to be permitted, you must specify the generated maximum value (kc_tpool_str.max_number in chapter "kc_tpool_str - LTERM pools for the application") in state_number.
  	You can disable the entire LTERM pool if you specify state_number='0'.
  	Minimum value for state_number: '0' Maximum value for state_number: the maximum number returned in kc_tpool_str.max_number

  The fields state and state_number must always be specified together.

  If the number in state_number exceeds the generated maximum number of LTERM partners, UTM automatically resets the value of state_number to this maximum number.

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

  Disabling LTERM partners in the LTERM pool has the following effect:

  • A connection setup request from a client via this LTERM pool is rejected by UTM as soon as the permitted number of clients is reached which are connected to the application via this LTERM pool (all permitted LTERM partners are occupied).

  • If, at the time at which the call is processed by UTM, the number of live connections to this LTERM pool exceeds the number of permitted LTERM partners for the LTERM pool, all existing connections are initially maintained.

    The lock only comes into effect for new connection setup requests.

    If terminal users sign off with KDCOFF BUT, they can sign on again with KDCSIGN, even if at that time more clients than permitted are connected to the application through the LTERM pool. This is possible because the connection remains in this case.

    KDCPOOL ("KDCPOOL - Administer LTERM pools")

• You can change the maximum period for which UTM waits for an entry from the client after the end of a transaction or after sign-on. If the time is exceeded, the connection to the client is cleared down. Specify the following in the kc_tpool_str data structure:

  Field name	Meaning
  idletime[5]	In idletime you specify the maximum time in seconds that openUTM waits for an entry from the client outside a transaction (i.e. after the end of a transaction or after sign-on). When idletime=0 is specified, openUTM waits for an unlimited period.
  	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 GP ("KC_MODIFY_OBJECT - Modify object properties and application parameters")

  The modification of the timer takes effect at the next end of transaction, but not before the end of the program unit run (PEND) in which the call is processed.