openUTM provides you with information functions with which you can obtain an overview of the configuration of your application, the settings for application parameters and the current utilization level of the application. You can call the information functions of UTM administration with:
 | KDCINF |
| KC_GET_OBJECT |
These information functions can also be utilized by users who do not have administration privileges (see chapter "Access rights and data access control").
With the aid of information functions, you can, for instance, arrange for output of the following information:
Application and system parameters defined during KDCDEF generation with the MAX statement
(section "type=SYSPARM" in chapter "Output from KDCINF" / "kc_max_par_str - Maximum values for the application (MAX parameters)").Number of processes currently active for the application, maximum number of processes that can be available for asynchronous processing at one time, maximum number of processes that are available for processing services at one time and that contain blocking calls, such as the KDCS call PGWT or the XATMI call tpcall
(section "type=SYSPARM" in chapter "Output from KDCINF" / "kc_tasks_par_str - Number of processes").Data about the current utilization level of the application. This information can, for example, include utilization of the page pool or the cluster page pool, the total number of messages being exchanged, the number of users and clients signed on, the number of services open at the present time, the number of transactions performed per unit of time, the number of jobs buffered in the message queues etc.
(see sections "type=STATISTICS" and "type=SYSPARM" in chapter "Output from KDCINF" / "kc_curr_par_str - Current values of the application parameters").Current settings for the timers. In UTM, for example, timers are defined for assigning and waiting for resources, waiting for an answer from a dialog partner both during and outside of a transaction, waiting for confirmations, and waiting for a connection or session to be established (see section "type=SYSPARM" in chapter "Output from KDCINF" / "kc_timer_par_str - Timer settings").
Configuration data on all objects which appear in the configuration. This includes the names and logical properties defined when adding objects to the configuration. It also includes control values for the message queues, the number of LTERM partners in an LTERM pool or the maximum number of parallel connections generated to an OSI TP partner application.
Status of individual communication partners and printers in the application, and of connections to these. For example, the output can show whether the communication partner is connected to the application and the length of time that such a connection has been in existence, as well as whether or not the communication partner is currently disabled, the number of messages exchanged on the connection, and whether automatic connection setup is generated.
Maximum number of objects of a given type that the configuration of the application can maintain.
Number of objects that can still be added dynamically to the configuration.
Details of which specific data are returned is described in section "Data structures used to pass information" for queries with KC_GET_OBJECT and as of "Output from KDCINF" for queries using the administration command KDCINF.
With information queries you can specify the selection criteria, i.e. you can request information on objects which have particular properties, e.g.:
all LU6.1 connections currently established
the association ID of all associations currently established to an OSI TP partner application
all clients and printers currently connected to the application
all users currently connected to the application
all LTERMs of a connection bundle or all (OSI-)LPAPs of a LPAP bundle