The events TASK-ON, TASK-OFF, CHG-PROG and, with restrictions END-PU (see section “Security-related UTM events”) are always logged when SAT logging is not switched off for the UTM application.
All other events are logged when logging is not switched off for the particular event and when at least one of the three criteria of event-specific, user-specific, or job-specific preselection is fulfilled for this event.
UTM logs an event as successful (SUCC) when it has successfully passed the UTM authorization check and the action can be performed by UTM. Otherwise, the event is logged as failed (FAIL).
UTM events initiated by KDCS calls (e.g. DATA-ACCESS) are not logged if the function cannot be executed due to an illegal value of KCOM, KCLA, KCLM, etc. (see the openUTM manual „Programming Applications with KDCS”). These areas can only be incorrectly assigned by a faulty program unit.
UTM events initiated by KDCS calls are logged as failed if the assignment of KCRN, KCUS, or KCLT is incorrect. The incorrect assignment of KCRN, KCUS and KCLT can be caused not only by a faulty UTM program unit but also by a UTM user (e.g. if the user does not have authorization for the function called).
From the SAT log records, you can identify whether an event was rendered ineffective by the subsequent rollback of the transaction:
The log data record of the respective event contains the identification number of the transaction which initiated the event (log field UTMTAID).
You can use the transaction identification to find the associated “end of transaction” log record (END-PU in the log field UTMSUBC). The transaction status is specified there in the UTMSTAT field.
The structure of the log records is described in the Appendix in the section “Structure of SAT log records” ("Structure of SAT log records").
The KDCS call RSET (roll back the transaction while continuing the program unit run) implicitly initiates the “end of transaction” event with the transaction status “rollback” (OBJECT2= or UTMSTAT= R), and then initiates the “start of transaction” event (START-PU).