The administrative data area contains configuration information, such as application runtime parameters, lists of all objects that can be addressed by name, administrative data on the page pool and restart area, and tables of user IDs, clients, LTERM partners, transaction codes, key and lock codes, and function keys.
All tasks and work processes of the application work with the administrative data and use the application to exchange information.
The administrative data itself is initialized using the KDCDEF generation tool. When starting the application, it is loaded into a shared memory, which can then be accessed by all tasks/work processes of the application.
On BS2000 systems this memory is located in a Common Memory Pool.
On Unix, Linux and Windows systems the administrative data is put into a shared memory segment.
In a UTM-S application, openUTM writes the administrative data (including any modifications made in the meantime) back to the KDCFILE at certain intervals (Periodic Write). This also occurs at the end of the application run. This version of the administrative data then forms the basis for the next application run.
In a UTM-F application, openUTM writes only certain modified administrative data back to the KDCFILE, e.g. changed user passwords and configuration data incorporated by means of dynamic administration.