This report provides detailed information on a UTM application.
Report output
The UTM APPLICATION report is output only at the explicit request of the SM2 user with the help of the SELECT-UTM-APPLICATION statement. This statement is used to output a UTM report together with a UTM APPLICATION report for the selected applications. The UTM APPLICATION report supplies detailed information on the UTM applications.
It is possible to output data on up to 16 applications.
An overflow screen with additional data for the UTM application can be requested for this report, see "Report output (overflow screen)".
HOST0001 SM2 UTM APPLICATION CYCLE: 300 S <date> >time>
APPL: SEI10 JOBN: SEI UTM-VERS: <version> MODE: UTM-S # DB'S: 0
+-------------------+---------+
+-------------------------+---------+---------+ | # DIAL STEPS (1/S)| 11.3 |
| MEAN VALUE FOR | DIALOG | ASYNCH | | # DIAL TA'S (1/S)| 11.3 |
+-------------------------+---------+---------+ | # ASYN TA'S (1/S)| 0.0 |
| TOTAL TIME (MS/ST)| 0.1 | 0.0 | | # ASYN CONV (1/S)| 0.0 |
| TOT TIME WITH DB (MS/ST)| 0.0 | 0.0 | +-------------------+---------+
| STEPS WITH DB (1/S)| 0.0 | 0.0 | | # TASKS | 10 |
| TIME IN DB (MS/ST)| 0.0 | 0.0 | | # MAX ASYN TASKS | 3 |
| # DB CALLS (1/ST)| 0.0 | 0.0 | | # CONNECTED USERS | 12 |
| CPU TIME IN DB (MS/ST)| 0.000 | 0.000 | | # WAITING PRINTS | 0 |
| # IO IN DB (1/ST)| 0.0 | 0.0 | | # WAITING ATACS | 0 |
| TOT TIME WITH DDP (MS/ST| 0.0 | 0.0 | | # WAITING DPUTS | 0 |
| STEPS WITH DDP (1/S)| 0.0 | 0.0 | | # DIAL CURR CONV | 9 |
| TIME IN DDP (MS/ST)| 0.0 | 0.0 | | # ASYN CURR CONV | 0 |
| CPU TIME (MS/ST)| 1.53 | 0.000 | | CACHE HIT RATE (%)| 97 |
| # IO (1/ST)| 8.7 | 0.0 | | FREE PAGE POOL (%)| 99 |
+-------------------------+---------+---------+ | BOURSE WAIT T (MS)| 0 |
+-------------------+---------+
Monitoring information
APPL | Name of the UTM application |
JOBN | BS2000 job name for the first task started for the UTM application |
UTM-VERS | UTM version |
MODE | UTM-S or UTM-F mode |
# DB'S | Number of database systems the application works with |
The following entries are all average values which refer to dialog steps (DIALOG) and asynchronous conversations (ASYNCH). In the explanations of the fields, “step” is used as a generic term for this. It is abbreviated in the report as “ST”. | |
TOTAL TIME | For dialog steps: the total time in milliseconds for each dialog step from acceptance of the entry by UTM to the sending of a dialog message by UTM. |
TOT TIME WITH DB | Value analogous to TOTAL TIME, but only for steps with database calls (*) |
STEPS WITH DB | Number of steps per millisecond with database calls |
TIME IN DB | Time per millisecond per step UTM waits for the execution of database calls (*) |
# DB CALLS | Number of database calls per step (*) |
CPU TIME IN DB | CPU time per millisecond consumed per step in database systems (*)(***) |
# IO IN DB | Number of I/Os per step in the called database systems (*)(***) |
TOT TIME WITH DDP | Value analogous to TOTAL TIME, but only for steps with distributed processing calls (**) |
STEPS WITH DDP | Number of steps per second with distributed processing calls |
TIME IN DDP | Time per millisecond per step UTM waits for the arrival of a message from a remote application (**) |
CPU TIME | CPU time per millisecond consumed by UTM for processing the step, including user subroutines |
# IO | Number of I/Os to/from UTM tasks which occur during processing of the step, including user subroutines |
(*) | Only those steps are included where database calls occur |
(**) | Only those requests are included where distributed processing calls occur |
(***) | Not all database systems which coordinate with UTM supply these values. Some database systems allow the database administrator to activate the provision of monitoring data by issuing a statement. For further details see the “Using openUTM Applications under BS2000” manual [11 (Related publications)] and the relevant database system manuals. |
The next four values show the application’s throughput (performance data). | |
# DIAL STEPS | Number of completed dialog steps per second |
# DIAL TA'S | Number of completed dialog transactions per second |
# ASYN TA'S | Number of completed asynchronous transactions per second |
# ASYN CONV | Number of completed asynchronous conversations per second |
The remaining values indicate the current status of the application. | |
# TASKS | Number of tasks running for the application |
# MAX ASYN TASKS | Maximum number of tasks available for asynchronous processing |
# WAITING PRINTS | Number of print jobs waiting for execution |
# WAITING ATACS | Number of jobs for asynchronous programs waiting for processing |
# WAITING DPUTS | Number of time-driven jobs waiting (background and output jobs) |
# DIAL CURR CONV | Number of open dialog conversations |
# ASYN CURR CONV | Number of open asynchronous conversations |
CACHE HIT RATE | Hit rate in % when searching for a UTM page in the UTM cache |
FREE PAGE POOL | Percentage of free pages in the UTM page pool |
BOURSE WAIT T | Time in milliseconds a request waits in the job queue for a UTM application. This value is approximated by generating an internal test message. |
Asterisks (***) are output in place of invalid or unavailable monitoring data.
Report output (overflow screen)
D017ZE29 SM2 UTM APPLICATION CYCLE: 300 S 14-09-03 16:00:00 APPL: SEI10 JOBN: SEI TACCLASS INFO +----------+--------+--------+ +--+--------+--------+--------+--------+-------+ |VALUE FOR | MEAN | CNT | |NR| ELAPSED TIME | WAIT TIME |WAITING| +----------+--------+--------+ | | MEAN | CNT | MEAN | CNT | MSG | |CACHE WAIT| 0.0| 22.6| +--+--------+--------+--------+--------+-------| |CACHE HIT | 1.0| 9.2| |01| 111.4| 13.5| 0.0| 0.0| 0| |PER WRITE | 0.0| 9.2| |02| 0.0| 0.0| 0.0| 0.0| 0| |USER RES W| 0.4| 4.4| |03| 0.0| 0.0| 0.0| 0.0| 0| |SYS RES W | | 680| |04| 0.0| 0.0| 0.0| 0.0| 0| |INPUT MSG | | 11.3| |05| 0.0| 0.0| 0.0| 0.0| 0| |OUTPUT MSG| | 11.3| |06| 0.0| 0.0| 0.0| 0.0| 0| |LOGFILE WR| | 0.0| |07| 0.0| 0.0| 0.0| 0.0| 0| |CURR LOAD | | 14| |08| 0.0| 0.0| 0.0| 0.0| 0| | | | | |09| 0.0| 0.0| 0.0| 0.0| 0| | | | | |10| 0.0| 0.0| 0.0| 0.0| 0| | | | | |11| 0.0| 0.0| 0.0| 0.0| 0| | | | | |12| 0.0| 0.0| 0.0| 0.0| 0| | | | | |13| 0.0| 0.0| 0.0| 0.0| 0| | | | | |14| 0.0| 0.0| 0.0| 0.0| 0| | | | | |15| 0.0| 0.0| 0.0| 0.0| 0| | | | | |16| 0.0| 0.0| 0.0| 0.0| 0| +----------+--------+--------+ +--+--------+--------+--------+--------+-------+
Monitoring information
CACHE WAIT | |
MEAN | Percentage of the wait situations when requesting cache buffers. |
CNT | Number of requests for cache buffers per second. |
CACHE HIT | |
MEAN | Percentage of the found cache buffers. |
CNT | Number of cache buffers searched for per second. |
PER WRITE | |
MEAN | In the case of periodic writes, number of pages written per periodic write. |
CNT | Number of periodic writes per second. |
USER RES W | |
MEAN | Percentage of the wait situations when accessing secondary storage areas (GSSB, TLS, ULS). |
CNT | Number of transaction resource requests per second. |
SYS RES W | |
CNT | Percentage of the wait situations for system locks in the entire number of lock requests in requests per thousand. The value is updated by UTM every 100 seconds. |
INPUT MSG | |
CNT | Number of all messages which the application has received from clients or partner applications (per second). |
OUTPUT MSG | |
CNT | Number of all messages which the application has sent to clients, printers or partner applications (per second). |
LOGFILE WR | |
CNT | Number of requests to write log records in the user log file (USLOG) (per second). |
CURR LOAD | |
CNT | Utilization of the application in percent in the last completed interval (100 seconds). The value is updated by UTM every 100 seconds. |
TACCLASS INFO | |
NR | Contains values for 16 TAC classes. |
ELAPSED TIME | |
MEAN | Mean duration of the subroutine runs in milliseconds. |
CNT | Number of subroutine runs per second. |
WAIT TIME | |
MEAN | Mean wait time of messages in milliseconds. |
CNT | Number of wait situations per second. |
WAITING MSG | |
CNT | Number of waiting messages (status at the end of the monitoring period). |