openUTM provides the following functions which assist you during the diagnosis of performance bottlenecks and incorrect program behavior:
You can check the maximum utilization of an application in a particular period.
You can log events in the form of UTM messages in the SYSLOG.
In order to diagnose bottlenecks and errors in connections to communication partners, you can activate the UTM BCAM trace or the OSS trace. The UTM BCAM trace can be activated for all connections, for a specific user only or just for connections to specific partner applications and clients.
You can enable the CPI-C trace, TX trace or XATMI trace to diagnose errors that occur in program units that use the X/Open interfaces CPI-C, TX or XATMI.
You can enable the ADMI trace to diagnose errors that occur at the administration program interface (KDCADMI).
You can activate test mode. Test mode is used to generate diagnostic documentation when errors occur in the UTM system code. Since test mode has a negative impact on UTM application performance, you should only activate test mode when requested to do so by Systems Support. In test mode, additional internal UTM plausibility checks are conducted and internal trace information is logged.
You can request a diagnostic dump without having to interrupt the execution of the application. In this case, you can do the following by issuing a command or via the program interface:
immediately request a general diagnosis dump. This has the ID DIAGDP.
or request a dump as soon as a particular event (message, KDCS return code, signon return code) is generated by openUTM. The dump ID is dependent on the event. You must first activate test mode since the dump is only written when test mode is active.
| KDCDIAG |
| KC_MODIFY_OBJECT with obj_type=KC_DIAG_AND_ACCOUNT_PAR |
