Please note the following when using UTM accounting:
Transaction logging is not implemented when writing accounting information; this means that accounting units may be lost if an application crashes. The maximum value per user can be limited in the UTM generation.
For applications with distributed processing, each LTAC call is counted in the calculation phase. No account is taken of whether or not a session could be opened following PEND processing.
The recording of resource utilization begins before a program unit starts and ends with the processing of the PEND call. The remaining processing power (basic utilization) of the UTM processes is not charged to the users.
Rolling back a transaction has the following effects: All values except for CPU are reset. Since openUTM accumulates the utilization values in the PEND processing, a rollback action can only reset utilization values if they originate in the current program unit run.
If only asynchronous jobs have been processed for the user since the last application start, the sign-on time to the application is shown as zero in the accounting record.
For the event exit VORGANG, the resource utilization is only recorded at the start of the service.
For the event service BADTACS, the program unit weight cannot be taken into account in the accounting phase.