obj_type=KC_CURR_PAR

The counters for application-specific statistical values are to be reset. For this you must assign the data structure kc_curr_par_str to the data area.

Furthermore, you can enable or disable data compression, see section "Enabling/Disabling data compression".

Possible modifications

All the counters listed below can be set in one call. In order to reset the counters you must pass the value '0' to UTM in the relevant field, unless there is a note to the contrary. You can reset the following counters or statistical values:

Field name	Specification
term_input_msgs='0'	Number of messages which the application received from clients or partner applications since the last reset. The counter is reset to 0.
term_output_msgs='0'	Number of messages which the application sent to clients, printers or partner applications since the last reset. The counter is reset to 0.
max_dial_ta_per_100sec='0'	Maximum number of dialog transactions carried out within the space of 100 seconds. The counter is reset to 0 ("kc_curr_par_str - Current values of the application parameters").
max_asyn_ta_per_100sec='0'	Maximum number of asynchronous transactions carried out within the space of 100 seconds. The counter is reset to to 0 ("kc_curr_par_str - Current values of the application parameters").
max_dial_step_per_100sec='0'	Maximum number of dialog steps carried out within the space of 100 seconds. The counter is reset to to 0 ("kc_curr_par_str - Current values of the application parameters").
max_pool_size='0'	Maximum utilization of the page pool in percent since the last reset. The counter is reset to 0. If this value is reset then the value of avg_pool_size is also implicitly reset to 0.
avg_pool_size='0'	Average utilization of the page pool in percent since the last reset of the counter. The counter is reset to 0. If this value is reset then the value of max_pool_size is also implicitly set to 0.
cache_hit_rate='0'	Hit rate for pages in the cache memory since the counter was last reset (in percent). The counter is reset to 0. If this value is reset then the values cache_wait_buffer, nr_cache_rqs and nr_cache_searches are also impicitly reset to 0.
cache_wait_buffer='0'	Percentage of buffer requests in the cache, that led to a wait time. The counter is reset to 0. If this value is reset then the values cache_hit_rate , nr_cache_rqs and nr_cache_searches are also impicitly reset to 0.
abterm_services='0'	Number of abnormally terminated services since the last reset. The counter is reset to 0.
deadlocks='0'	Number of known and resolved deadlocks of UTM resources since the last reset. The counter is reset to 0.
periodic_writes='0'	Number of periodic writes since the last reset (periodic write = backup of all relevant administration data in the UTM application). The counter is reset to 0.
pages_pwrite='0'	Number of UTM pages saved on average in a periodic write. The counter is reset to 0.
logfile_writes='0'	Number of requests to write log records to the user log file ((USLOG). The counter is reset to 0.
maximum_jr='0'	In distributed processing only: Maximum number of remote job receiver services addressed in the local application at the same time in relation to the generated value MAXJR (see kc_utmd_par_str in chapter "kc_utmd_par_str - Parameters for distributed processing"). This is a percent value. The counter is reset to the value of curr_jr ("kc_curr_par_str - Current values of the application parameters").
max_load='0'	max_load specifies as a percentage the maximum load of the UTM application registered since the start of the application or the last reset. The value is reset to the value in curr_load (see "kc_curr_par_str - Current values of the application parameters").
max_wait_resources='0'	max_wait_resources specifies the maximum conflict rate for user data locks over the application run. The value is specified as an amount per thousand. The counter is reset to 0. If this value is reset then the values max_wait_system_resources, nr_res_rqs_for_max and nr_sys_res_rqs_for_max are also impicitly reset to 0.
max_wait_system_resources='0'	max_wait_system_resources specifies the maximum conflict rate for system resource locks (system locks) across the application run. The value is specified as an amount per thousand. The counter is reset to 0. If this value is reset then the values max_wait_resources, nr_res_rqs_for_max and nr_sys_res_rqs_for_max are also implicitly reset to 0.
nr_cache_rqs='0'	Number of buffer requests taken into account to calculate the value cache_wait_buffer. The counter is reset to 0. If this value is reset then the values cache_hit_rate, cache_wait_buffer and nr_cache_searches are also implicitly reset to 0.
nr_cache_searches='0'	Number of search operations for UTM pages in the cache taken into account to calculate the value cache_hit_rate. The counter is reset to 0. If this value is reset then the values cache_hit_rate, cache_wait_buffer and nr_cache_rqs are also implicitly reset to 0.
nr_res_rqs_for_max='0'	Number of requests for transaction resources in the 100 second period during which the maximum conflict rate max_wait_resources was reached. The counter is reset to 0. If this value is reset then the values max_wait_resources, max_wait_system_resources and nr_sys_res_rqs_for_max are also implicitly reset to 0.
nr_sys_res_rqs_for_max='0'	Number of requests for system resources in the 100 second period during which the maximum conflict rate max_wait_system_resources was reached. The counter is reset to 0. If this value is reset then the values max_wait_resources, max_wait_system_resources and nr_res_rqs_for_max are also implicitly reset to 0.
avg_saved_pgs_by_compr='0'	Average value for the UTM pages saved per data compression. The counter is reset to 0.

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

If you wish to reset the statistical values listed above yourself, you should set MAX STATISTICS-MSG =NONE in KDCDEF generation. This stops UTM resetting the counters to 0 at hourly intervals and creating the statistics message K081.

Enabling/Disabling data compression

Field name	Specification
data_compression='Y'	Data compression is enabled. For this purpose data compression must be permitted by means of UTM generation, see openUTM manual “Generating Applications”, MAX DATA-COMPRESSION=
data_compression='N'	Data compression is disabled.

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