The TCLASS list contains an overview of job processing of TACs in the individual TAC classes (1 through 6) in tabular form. In the evaluation, all dialog TACs to which no TAC class was assigned during generation with KDCDEF are combined into TAC class 0.
In the UTM generation, the user can define the maximum number of tasks that can operate for a TAC class at any one time. When this number is reached, subsequent jobs are placed in a TAC class-specific queue.
|------------------------------------------------------------------------------|
| TAC- | NUMBER | DISTRIBUTION IN PERCENT | AVERAGE | MAXIMUM | MINIMUM |
| CLASS | CALLS |---------------------------|WAIT TIME |WAIT TIME |WAIT TIME |
| | | NUMBER | WAIT- | WAIT- | | | |
| | | CALLS | TIME=0 | TIME>0 |(IN MSEC) |(IN MSEC) |(IN MSEC) |
|------------------------------------------------------------------------------|
| 0 | 10 | 0,04 | | | | | |
|------------------------------------------------------------------------------|
| 1 | 21646 | 99,27 | 97,90 | 2,10 | 184| 1010| 1|
| 2 | 0 | 0,00 | | | 0| 0| 0|
| 3 | 3 | 0,01 | 66,66 | 33,34 | 296| 296| 296|
| 4 | 0 | 0,00 | | | 0| 0| 0|
| 5 | 0 | 0,00 | | | 0| 0| 0|
| 6 | 0 | 0,00 | | | 0| 0| 0|
| 7 | 0 | 0,00 | | | 0| 0| 0|
| 8 | 0 | 0,00 | | | 0| 0| 0|
|------------------------------------------------------------------------------|
| 9 | 145 | 0,66 | 2,75 | 97,25 | 1| 2| 1|
| 10 | 0 | 0,00 | | | 0| 0| 0|
| 11 | 0 | 0,00 | | | 0| 0| 0|
| 12 | 0 | 0,00 | | | 0| 0| 0|
| 13 | 0 | 0,00 | | | 0| 0| 0|
| 14 | 0 | 0,00 | | | 0| 0| 0|
| 15 | 0 | 0,00 | | | 0| 0| 0|
| 16 | 0 | 0,00 | | | 0| 0| 0|
|------------------------------------------------------------------------------|
| | 97,26 | 2,74 | 141| |
|------------------------------------------------------------------------------|
21659 DIALOG TACS WERE CALLED
145 ASYNCHRONOUS TACS WERE CALLED
The TCLASS list contains the following information:
The NUMBER CALLS column indicates the number of TAC calls in the evaluation period for a TAC class.
The DISTRIBUTION IN PERCENT column contains percentage values.
The subcolumn NUMBER CALLS specifies the percentage of calls of a TAC class within the number of all TAC calls. The next two columns contain a percentage breakdown of the calls of this TAC class into the following categories:calls that were processed immediately (WAITTIME=0), and
calls that had to be placed in a TAC class-specific queue (WAITTIME>0).
The values in the columns AVERAGE / MINIMUM / MAXIMUM WAIT TIME refer to the jobs which openUTM temporarily placed in a TAC class-specific queue. The average minimum or maximum wait time of a job per TAC class is displayed.
Wait time for dialog jobs
In the case of dialog jobs, the wait time is the period between the acceptance of the job by the application (job retrieved from the queue of the application) and the start of the program unit. Displacement can also occur between individual program units.
Wait times for asynchronous jobs
openUTM also records the wait time of asynchronous jobs. The wait time is defined as follows:
Asynchronous job | Definition of “wait time” |
Input asynchronous TAC | Period between the acceptance of the job by openUTM and the start of the asynchronous service. |
FPUT call in the program unit | Period between the end of the transaction in which the FPUT job was executed, and the start of the asynchronous service. |
DPUT job in the program unit | Period between the conversion of the DPUT into FPUT and the start of the asynchronous service. |
If the asynchronous job was not created in the current application run, the asynchronous wait time is always taken to be the time difference between the start of the application and the start of the asynchronous job.