Application parameters and maximum values for the application are to be modified. You must assign the data structure kc_max_par_str in the data area.
Possible modifications
All the modifications described below can proceed in a single call.
You can modify application maximum values, which were defined in the MAX statement during KDCDEF generation. These modifications may affect application performance (see also "Performance check").
The following table shows which maximum values can be modified and the fields of the data structure kc_max_par_str to which you must pass the new maximum values.
Field name
Meaning
bretrynr[5]
Only on BS2000 systems:
Specify in bretrynr how often UTM is to attempt to pass a message to the transport system (BCAM) if BCAM cannot immediately accept the message.
The selected value of bretrynr should not be too high because the process attempting to the pass the message to BCAM is blocked for the duration of the attempts.For asynchronous messages to a dialog partner type of the ptype='APPLI' (TS application), bretrynr is not relevant (see bretrynr in chapter "kc_max_par_str - Maximum values for the application (MAX parameters)")
Minimum value: '1'
Maximum value: '32767'cachesize_paging[3]
Specify in cachesize_paging the percentage of the cache which is to be written to the KDCFILE in the event of a bottleneck so that the cache memory can be used for other data.
UTM replaces at least 8 UTM pages out to cache in a single paging, even if the value of cachesize_paging is smaller.Minimum value: '0', i.e. 8 UTM pages are swapped out to cache
Maximum value: '100' (%)Cache size is defined in the MAX statement during KDCDEF generation and can be ascertained, for example, by using KC_GET_OBJECT for obj_type=KC_MAX_PAR (cache_size_pages).
Period of validity / transaction management: type GIR ("KC_MODIFY_OBJECT - Modify object properties and application parameters")
Field name
Meaning
conn_users[10]
By using conn_users you can prevent the application from being overloaded by too many active users. To do this, specify in conn_users the maximum number of users or clients that can currently be signed on to the UTM application.
The following situation applies in applications generated with user IDs:
If the number specified for conn_users is greater than the number of generated users, conn_users has no effect.
User IDs which have been generated with administration privileges can still sign on to the UTM application after the maximum number of concurrent user IDs has been reached.
The following situation applies in applications which are generated without user IDs:
The number of dialog partners which can concurrently be connected to the UTM application is restricted by conn_users.
If the number specified for conn_users is greater than the number of generated dialog LTERM partners, conn_users has no effect. Dialog LTERM partners are all those LTERM partners entered with usage_type= 'D', LTERM partners of the LTERM pool and the LTERM partners created internally by UTM for multiplex connections.
If the number of simultaneously active users is not to be restricted or if a restriction is to be cancelled, specify conn_users= '0'.
Minimum value: '0' (i.e. no restriction)
Maximum value: '500000'
On Unix, Linux and Windows systems, the maximum value may not exceed the value generated in the generation parameter MAX ... CONN-USERS.Period of validity / transaction management: type IR ("KC_MODIFY_OBJECT - Modify object properties and application parameters")
You can define a new destination for the results of the KDCADM administration commands which were called by KDCADM through asynchronous TACs.
Field name
Meaning
destadm[8]
Specify in destadm the new recipient for the results of KDCADM administration calls which have been processed asynchronously (asynchronous KDCADM transaction codes). This overwrites the old value of destadm.
You can specify the following for destadm:
the name of an LTERM partner
an asynchronous transaction code or
a TAC queue
If you specify blanks for destadm no recipient is defined any longer. The results of the asynchronous KDCADM transaction code then are lost.
Period of validity / transaction management: type GPD ("KC_MODIFY_OBJECT - Modify object properties and application parameters")
You can change the number of failed attempts which UTM allows before UTM triggers the silent alarm.
Field name
Meaning
signon_fail
Specify in signon_fail the number of unsuccessful sign-on attempts (security violations) from a client following in immediate succession after which a “silent alarm” (K094-UTM message) is triggered.
Minimum value: '1'
Maximum value: '100'Period of validity / transaction management: type GIR ("KC_MODIFY_OBJECT - Modify object properties and application parameters")
You can activate or deactivate the supply of data to openSM2:
Field name
Meaning
sm2='Y'
UTM is to supply data to openSM2 for the purpose of monitoring performance data.
The supply of data can only be activated if it was not excluded at a general level during KDCDEF generation (MAX statement operand SM2).sm2='N'
The supply of data to openSM2 is to be deactivated.
Period of validity / transaction management: type GIR ("KC_MODIFY_OBJECT - Modify object properties and application parameters")
 | Some of the modifications can also be performed with the administration command KDCAPPL ("KDCAPPL - Change properties and limit values for an operation"). |