Changing the configuration of an application dynamically

This chapter describes what to note in the KDCDEF generation of the application if you want to use the dynamic configuration functions in your application. On the program interface, openUTM provides KDCADMI functions as well as functions available at the administration workstation WinAdmin or the web application WebAdmin with which you can enter objects in the configuration of the application or delete them from the configuration while the application is running. This increases the availability of UTM applications, because a regeneration of the application with KDCDEF, which necessitates an interruption to operation, is required much less often. In order to use the functions for dynamic configuration, you must reserve table locations in the object tables of openUTM when generating with the KDCDEF control statement RESERVE.

This means that services as well as clients and printers can be entered dynamically in the configuration with the assigned LTERM partners, and also means that user IDs can be created dynamically. All of these objects can also be deleted dynamically.

You can dynamically create and delete the following objects:

• transaction codes and TAC queues

• program units and VORGANG exits (only in applications with load modules, shared objects or DLLs)

• user IDs

• LTERM partners

• key sets

• local service names

• transport connections to LU6.1 partner applications and LU6.1 session names

• communication partners that are TS applications, UPIC clients or terminals

• printers.

To be able to use the functions of dynamic configuration, you must create administration programs or use the openUTM components WinAdmin or WebAdmin. By calling KC_CREATE_OBJECT on the program interface for administration you can enter new objects in the configuration, and by calling KC_DELETE_OBJECT you can delete objects from the configuration. The openUTM manual “Administering Applications” describes what to note when creating administration programs for dynamically entering objects and when deleting objects from the configuration of the application.

The dynamic configuration functions can also be used in full in the function variant UTM-F. openUTM logs all changes to the configuration in the KDCFILE. The modified configuration data then also remains available for the next application run, as with UTM-S.

To allow you to incorporate objects into the configuration of your UTM application dynamically, you must make certain preparations (see "Reserving locations in the KDCFILE object tables" and "Prerequisites for entering objects dynamically") when generating the application with KDCDEF.

No preparations are necessary in the KDCDEF generation for deleting objects from the configuration.