The data structure kc_curr_par_str is defined for the parameter type KC_CURR_PAR. In the case of KC_GET_OBJECT, UTM returns the current values of the parameter settings, data pertaining to the application run and statistical information on the load of the application in kc_curr_par_str (see also KDCINF, "type=STATISTICS" in chapter "Output from KDCINF (examples)").
You can reset some of the counters used by UTM to generate statistical information with the aid of KC_MODIFY_OBJECT if you need to (see also max_statistics_msg in chapter "kc_max_par_str - Maximum values for the application (MAX parameters)").
If MAX STATISTICS-MSG=NONE the counters in a UTM-S application are only reset the first time the application is started and in UTM-F applications they are reset each time the application is started.
If MAX STATISTICS-MSG=FULL-HOUR then the counters are reset every full hour. As a result, the values displayed in the initial period following a full hour may be too low.
mod 1 | Data structure kc_curr_par_str |
- |
|
- |
|
- |
|
- |
|
- |
|
- |
|
- |
|
- |
|
- |
|
- |
|
- |
|
- |
|
- |
|
- |
|
- |
|
x(GIR) |
|
x(GIR) |
|
- |
|
- |
|
- |
|
- |
|
- |
|
- |
|
- |
|
- |
|
- |
|
- |
|
- |
|
- |
|
x(GIR) |
|
x(GIR) |
|
x(GIR) |
|
x(GIR) |
|
- |
|
x(GIR) |
|
x(GIR) |
|
x(GIR) |
|
- |
|
- |
|
- |
|
x(GIR) |
|
- |
|
x(GIR) |
|
x(GIR) |
|
x(GIR) |
|
x(GIR) |
|
- |
|
x(GIR) |
|
- |
|
- |
|
x(GIR) |
|
- |
|
x(GIR) |
|
x(GIR) |
|
- |
|
x(GIR) |
|
- |
|
x(GIR) |
|
x(GIR) |
|
x(GIR) |
|
- |
|
x(GIR) |
|
- |
|
x(GIR) |
|
- |
|
x(GID) |
|
x(GIR) |
|
- |
|
- |
|
- |
|
- |
|
- |
|
- |
|
1 | The field contents can be modified with KC_MODIFY_OBJECT; see "obj_type=KC_CURR_PAR" |
2 | Internal UTM field; the contents of the field are irrelevant and will not be described in the following. |
The fields in the data structure have the following meanings:
appliname
Name of the UTM application set in the KDCDEF generation in MAX APPLINAME.
appliname is the name of the application that must be specified when establishing a connection from the terminal.
utm_version
The openUTM version used including the update information, for example V07.0A00.
applimode
Specifies if the UTM application is a UTM-S or UTM-F application.
'S' | The application is generated as a UTM-S application (secure). |
'F' | The application is generated as a UTM-F application (fast). |
start_date_year, start_date_month, start_date_day
UTM-S application: date of the last cold start of the application
UTM-F application: date of the last start of the application
start_time_hour, start_time_min, start_time_sec
UTM-S application: time of the last cold start of the application
UTM-F application: time of the last start of the application
curr_date_year, curr_date_month, curr_date_day
The current date.
curr_time_hour, curr_time_min, curr_time_sec
The current time.
term_input_msgs
Total number of messages that the application has received from clients or partner applications since the last time the term_input_msgs counter was reset.
UTM automatically resets the counter to 0 each time the application is started and on each full hour, if MAX STATISTICS-MSG=FULL-HOUR (default value) was set during KDCDEF generation.
You can set term_input_msgs to 0.
term_output_msgs
Total number of messages that the application sent to clients, printers or partner applications since the last time the term_output_msgs counter was reset.
UTM automatically resets the counter to 0 each time the application is started and on each full hour, if MAX STATISTICS-MSG=FULL-HOUR (default value) was set during KDCDEF generation.
You can set term_output_msgs to 0.
curr_max_asyntasks
Current setting for the maximum number of processes that may be used for asynchronous processing. curr_max_asyntasks is dynamically adjusted by UTM if the total number of processes of the application or the maximum number of processes for asynchronous processing (kc_tasks_par_str.mod_max_asyntasks in chapter "kc_tasks_par_str - Number of processes") is changed by the administration.
curr_max_tasks_in_pgwt
Current setting for the maximum number of processes that may simultaneously process jobs from TAC classes whose transaction codes are allowed to use blocking calls such as, for example, the KDCS call PGWT (Program Wait). curr_max_tasks_in_pgwt is dynamically adjusted by UTM if the total number of processes of the application or the number of processes
kc_tasks_par.mod_max_tasks_in_pgwt (see chapter "kc_tasks_par_str - Number of processes") is changed.
curr_tasks
Contains the number of processes of the application currently running.
curr_asyntasks
Contains the number of processes currently processing asynchronous jobs.
curr_tasks_in_pgwt
Contains the number of processes currently processing jobs whose transaction codes are allowed to use blocking function calls (for example PGWT).
tasks_waiting_in_pgwt
The current number of processes in the wait state due to blocking function calls (for example the KDCS call PGWT).
connected_users
The number of users currently connected to the application.
open_dial_services
The number of dialog services currently open.
In a UTM cluster application, an open dialog service that is valid globally in the cluster is only counted if the user is signed on.
open_asyn_services
The number of asynchronous services currently open.
dial_ta_per_100sec
The current number of dialog transactions executed in the last closed 100 second interval.
asyn_ta_per_100sec
The current number of asynchronous transactions executed in the last closed 100 second interval.
dial_step_per_100sec
The current number of dialog steps executed in the last closed 100 second interval.
max_dial_ta_per_100sec
The maximum number of dialog transactions that were executed within a 100 second interval. The value is specified for the current application run.
It can be reset with KC_MODIFY_OBJECT (see "obj_type=KC_CURR_PAR").
max_asyn_ta_per_100sec
The maximum number of asynchronous transactions that were executed within a 100 second interval. The value is specified for the current application run. It can be reset with KC_MODIFY_OBJECT (see "obj_type=KC_CURR_PAR").
max_dial_step_per_100sec
The maximum number of dialog steps that were executed within a 100 second interval. The value is specified for the current application run. It can be reset with KC_MODIFY_OBJECT (see "obj_type=KC_CURR_PAR").
max_pool_size
The maximum amount of the page pool in use in percent. For UTM-S applications the maximum page pool size since the most recent KDCDEF generation is returned, for UTM-F applications the size since the last application start is returned. The value can be reset with KC_MODIFY_OBJECT (see "obj_type=KC_CURR_PAR").
curr_pool_size
The current amount of the page pool in use in percent.
avg_pool_size
For UTM-S applications the maximum page pool size since the most recent KDCDEF generation is returned, for UTM-F applications the size since the last application start is returned. The value can be reset with KC_MODIFY_OBJECT (see "obj_type=KC_CURR_PAR").
cache_hit_rate
The hit rate when searching for a page in the cache. Specified in percent.The value refers to the current application run. It can be reset with KC_MODIFY_OBJECT (see "obj_type=KC_CURR_PAR"). If this value is reset then the values cache_wait_buffer, nr_cache_rqs and nr_cache_searches are also implicitly reset to 0.
cache_wait_buffer
The percentage of queries from buffers in the cache that have resulted in a wait state. cache_wait_buffer gives you the amount of buffer queries since the counter was last reset.
UTM automatically resets the counter to 0 each time application is started and on each hour, if MAX STATISTICS-MSG=FULL-HOUR (default value) was generated in the KDCDEF generation.
You can reset the counter using KC_MODIFY_OBJECT (see "obj_type=KC_CURR_PAR"). If this value is reset then the values cache_hit_rate, nr_cache_rqs and nr_cache_searches are also implicitly reset to 0.
unproc_atacs
The number of background jobs currently stored in UTM but not yet completely processed. This corresponds to the number of messages temporarily stored at the present time in all of the message queues of asynchronous services.
unproc_prints
The number of messages temporarily stored at the present time in the message queues of all of the printers.
wait_dputs
The number of time-driven jobs currently waiting (DPUTs).
abterm_services
The number of abnormally terminated services since the value was last reset.You can reset abterm_services with KC_MODIFY_OBJECT.
wait_resources
This value indicates the mean lock conflict rate for the GSSB, ULS and TLS memory areas during the last closed 100 second interval as an amount per thousand, i.e. the total number of wait situations on lock requests as a ratio of GSSB, ULS and TLS lock requests in the last closed 100 second interval multiplied by 1000.
A higher value in wait_resources can be caused by the following:
processes with run times or wait times that are too long
resources that have been locked for too long, for example, due to many PEND KP or PGWT calls in KDCS program units.
If a lock holder enters the status PEND KP then all "waiters" are informed and all further locks are rejected immediately. I.e. the value of wait_resources does not increase as a result.
deadlocks
The number of deadlocks of UTM resources that have been recognized and resolved since the value was last reset.
You can reset deadlocks using KC_MODIFY_OBJECT.
periodic_writes
The number of periodic writes since the last start of the application or since the value was last reset with KC_MODIFY_OBJECT. (periodic write = the saving of all relevant administration data of the UTM application.)
pages_pwrite
The number of UTM pages that are saved during a periodic write on the average. All periodic writes since the value was last reset are registered. You can reset the value using KC_MODIFY_OBJECT. UTM automatically resets pages_pwrite to zero each time the application is started.
logfile_writes
The number of request to write log entries to the user log file (USLOG) since the value was last reset
UTM automatically resets the counter to 0 each time application is started and on each hour, if MAX STATISTICS-MSG=FULL-HOUR (default value) was generated in the KDCDEF generation.
You can reset the counter using KC_MODIFY_OBJECT (see "obj_type=KC_CURR_PAR").
curr_jr
Only for distributed processing:
The current number of simultaneously addressed job-receiving services relative to the generated value MAXJR in percent.
(MAXJR = maximum number of remote job-receiving services that may be addressed simultaneously in the local application; see kc_utmd_par_str in chapter "kc_utmd_par_str - Parameters for distributed processing").
maximum_jr
Only in the case of distributed processing:
The current number of simultaneously addressed job-receiving services in the local application relative to the generated value MAXJR (see kc_utmd_par_str in chapter "kc_utmd_par_str - Parameters for distributed processing"). Specified in percent.
maximum_jr returns all requests to the remote job-receiving service since the value was last reset. You can reset maximum_jr to zero with KC_MODIFY_OBJECT.
program_fgg
On Unix, Linux and Windows systems: The number of file generations of the application program currently loaded.
On BS2000 systems: 0
uslog_fgg
The number of file generations of the user log file (USLOG) currently being written to.
max_load
Indicates as a percentage the maximum load on the UTM application since the start of the application or the last reset was registered.
The value in max_load can be reset to the value in curr_load.
curr_load
Indicates as a percentage the current load on the UTM application registered during the last closed 100 second intervall.
max_wait_resources
Maximum conflict rate for user data locks across the application run. The value is specified as an amount per thousand.
You can reset this value with KC_MODIFY_OBJECT. 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 implicitly reset to 0.
wait_system_resources
Average conflict rate in the last closed 100 second interval for the most heavily loaded system resource during this interval. The output can refer to different system resources in different intervals. The value is specified as an amount per thousand.
max_wait_system_resources
Maximum conflict rate for system resource requests (system locks) across the application run. The value is specified as an amount per thousand.
You can reset this value with KC_MODIFY_OBJECT. 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
Number of buffer requests taken into account to calculate the value cache_wait_buffer.
You can reset the value using KC_MODIFY_OBJECT. 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
Number of search operations for UTM pages in the cache taken into account to calculate the value cache_hit_rate.
You can reset the value using KC_MODIFY_OBJECT. 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
Number of requests for transaction resources in the last closed 100 second interval taken into account to calculate the value wait_resources.
nr_res_rqs_for_max
Number of requests for transaction resources in the 100 second interval during which the maximum conflict rate max_wait_resources was reached.
You can reset the value using KC_MODIFY_OBJECT. 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.
The values nr_res_rqs and nr_res_rqs_for_max are useful when assessing the relevance of a high lock conflict rate, in particular with regard to losses due to lock conflicts.
Example:
nr_res_rqs=100, wait_resources=5
nr_res_rqs_for_max=10, max_wait_resources=50.
I.e. the maximum lock conflict rate of 50 was reached with 10 locks being requested in 100 seconds, 5 of which led to wait times due to conflicts. In addition, the current lock conflict rate of 5 percent at 100 requested locks was also reached in100 seconds, with it again being necessary to wait for 5 locks.
nr_sys_res_rqs
Number of requests for system resources in the last closed 100 second interval taken into account to calculate the value wait_system_resources
nr_sys_res_rqs_for_max
Number of requests for system resources in the 100 second interval during which the maximum conflict rate max_wait_system_resources was reached.
You can reset the value using KC_MODIFY_OBJECT. 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.
curr_system_tasks
Number of UTM system processes that are currently running.
data_compression
Specifies whether data compresion is currently enabled:
'Y' | Data compresion is enabled. |
'N' | Data compresion is not enabled. |
You can modify the value with KC_MODIFY_OBJECT if data compression is permitted by means of generation (see section "kc_max_par_str - Maximum values for the application (MAX parameters)" and openUTM manual “Generating Applications”, MAX DATA-COMPRESSION=).
A modification applies beyond the application run; in UTM cluster applications it applies for all node applications.
avg_saved_pgs_by_compr
Average value for the UTM pages saved per data compression. The writing of areas in which UTM performs no compression because, for example, the data length is less than one UTM page is not included in this statistics value. Two digits to the left of the decimal point and one decimal digit of the statistics value are displayed, i.e. a content of 010 corresponds to an average saving of 1.0 UTM pages.
The value can be reset with KC_MODIFY_OBJECT.
If no statistics values for data compression are available for the application, binary zero is output. This is possible in the following situations.
Data compression is disabled.
The value was reset with KC_MODIFY_OBJECT.
No data compression was performed because the application uses "small" data areas in which it does not make sense to use compression.
If the value output for avg_saved_pgs_by_compr is less than 5 - which corresponds to 0.5 saved UTM pages per compression attempt -, for performance reasons data compression should be disabled for this application.
gen_date_year
gen_date_month
gen_date_day
Date of the generation run of the application.
gen_time_hour
gen_time_min
gen_time_sec
Time of the generation run of the application.