To establish bottleneck situations, openUTM inserts measuring jobs into the job queue at regular intervals if KDCMON is activated. The wait time of the jobs in the UTM queue can be determined on the basis of the time at which the job was introduced and the time of processing. The time difference between the individual pseudo jobs is approximately 10 seconds.
The following information is logged in the WAIT list:
The WAITING TIME column indicates the established wait time for each pseudo job in seconds.
For these wait times, the evaluation tool KDCEVAL also calculates the maximum, minimum, and mean value in seconds and outputs these values under UTM WAITING TIMES.
The NUMBER OF TASKS column indicates the number of processes available in the application at this time. The UTM system processes are not included in this number.
The BCAM wait times are output in seconds in the BCAM WAITING TIMES section. BCAM V12.0 or later measures the time spent in the BCAM transport system by input messages for the application before they are retrieved by openUTM.
NUMBER OF MESSAGES indicates the number of messages for which BCAM supplied a wait time. When KDCMON recording is activated (and hence also time recording in BCAM), there are generally messages already in the BCAM message pool. When openUTM retrieves these messages from BCAM, openUTM does not receive a wait time for them. These messages are not included in the value for NUMBER OF MESSAGES.
If the wait time is too long, the number of UTM tasks should be increased.
The WAIT list has the following format:
UTM WAITING TIMES:
TIME STAMP : 10:33:35.742 WAITING TIME MAXIMUM : 0.018
TIME STAMP : 10:33:41.740 WAITING TIME MINIMUM : 0.007
NUMBER OF ENTRIES: 7 WAITING TIME AVERAGE : 0.009
BCAM WAITING TIMES:L
TIME STAMP : 10:23:35.742 WAITING TIME MAXIMUM : 0.728
TIME STAMP : 10:39:35.740 WAITING TIME MINIMUM : 0.027
NUMBER OF MESSAGES: 200 WAITING TIME AVERAGE : 0.125
|