Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Changing the configuration dynamically

openUTM provides you with functions at the administration program interface with which you can create new objects in the configuration or delete them from the configuration during application runtime.

These functions further increase the availability of UTM applications. Regeneration of the application with KDCDEF, for which operation has to be interrupted, is now required much less frequently. In addition, regeneration of a UTM application is now much easier and a great deal less time-consuming. You will find appropriate recommendations for regenerating a UTM application in section “Recommendations for regeneration of an application”.

Using the functions UTM provides for changing the configuration dynamically, you can create and delete the following objects:

  • user IDs, including the associated queues

  • key sets

  • transport connections to remote LU6.1 applications

  • LU6.1 sessions

  • transaction codes for your own application

  • transaction codes, via which service programs can be started in partner applications

  • LTERM partners

  • clients, printers

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

  • TAC queues

To add and delete objects, use either the administration tools WinAdmin and WebAdmin or administration programs you have generated yourself. Using the KC_CREATE_OBJECT call at the administration program interface, you can add new objects to the configuration. With the KC_DELETE_OBJECT call, you can delete objects from the configuration. The KC_MODIFY_OBJECT call allows you to change individual object properties.

The full range of functions for dynamically changing the configuration can also be used in the function variant UTM-F. openUTM saves all the changes made to the configuration (including the entry, deletion and modification of dynamic objects) in the KDCFILE. The modified configuration data is then available for the next application run.

The following section describes a number of things you need to be aware of during KDCDEF generation of the application if you wish to add or delete objects to/from the configuration at runtime. It also describes points you must consider when dynamically creating objects from your application configuration.