UDS/SQL supports the accounting interface provided by openUTM to the databases. The CPU utilization and the number of I/Os per openUTM job is recorded as long as the openUTM application requests accounting information.
The recording of accounting data itself consumes CPU time and should therefore be carried out according to the requirements of the application. Individual utilization values are highly dependent on the current status of the UDS/SQL session.
UDS/SQL also executes subfunctions asynchronously, which means that the values passed to openUTM do not represent the total utilization.
The CPU time consumed by the master task and the administrator task is not taken into account, neither are initialization or termination phases of the UDS/SQL session.
The number of I/Os is determined at the end of a openUTM transaction. I/0s that occur after the end of a openUTM transaction are not counted.
UDS-D takes into account only the local configuration; it does not report the total amount of CPU time utilized over a number of different systems.