When a UTM-F application is running, openUTM saves a large portion of the administrative changes in the administration file for the restart. This includes the changed passwords, new users and the locking of TACs, for example. See also the openUTM manual “Administering Applications”. These changes are also made available after a new start of the UTM-F application.
In contrast, in UTM-F
No user data from standalone applications is stored in the KDCFILE. Correspondingly, all user data is “forgotten” in UTM-F during a normal as well as during an abnormal termination of the application. This includes, for example, secondary storage areas such as the GSSBs, information on open dialogs or background jobs.
In UTM cluster applications, the user’s service data is not saved until the user signs off in the cluster page pool. If, for example, a user is signed on at a node application that terminates abnormally then his or her user data is “forgotten”. In contrast, in the case of UTM-F cluster applications, GSSB and ULS are saved in UTM cluster files when the transaction is terminated - unlike in the case of standalone applications.
For this reason, the consistency of the data in a UTM-F application after a restart can only be guaranteed when only local transactions are used and when all user data is maintained in a single database.