Changing the generation dynamically

You can change the static UTM generation (created using KDCDEF) dynamically without interrupting the application run. The WinAdmin and WebAdmin graphical administration programs are available to you for this purpose. These allow you to modify objects in the generation, add new objects to it or delete objects from it. However, you can also write your own administration programs on the basis of the KDCADMI program interface.

The following table provides an overview of which object types of a UTM generation can be created, modified and deleted in the current version of UTM (Cluster-related object types are only available on Linux, Unix and Windows systems):

KDCDEF statement and operand for object type	Meaning of the object type	Create	Modify	Delete
CLUSTER	Parameters for a UTM cluster application	No	Yes	No
CLUSTER-NODE	Address components and base names of a node application	No	Yes	No
CON	LU6.1 connections	Yes	No	Yes
DATABASE/DB_INFO (BS2000 systems)	Database systems	no	yes	no
KSET (+ LOCK operand)	Access authorizations (key sets) (+ access protection)	Yes	Yes	Yes
MAX	Application parameters and maximum values	--*	Yes*	--*
LOAD-MODULE (BS2000 systems)	Load modules	No	Yes	No
LPAP	LPAP partners for LU6.1	No	Yes	No
LSES	Sessions for LU6.1	Yes	Yes	Yes
LTAC	TACs for LU6.1 partners and OSI TP partners	Yes	Yes	Yes
LTERM	LTERM partners of clients and printers	Yes	Yes	Yes
MUX (BS2000 systems)	Multiplex connection	No	Yes	No
OSI-CON	Connection for OSI TP partners	No	Yes	No
OSI-LPAP	OSI LPAP partners for OSI TP	No	Yes	No
PROGRAM	Program units	Yes	No	Yes
PTERM	Clients and printers	Yes	Yes	Yes
SHARED-OBJECT (Unix, Linux and Windows systems)	Shared objects	No	Yes	No
TAC	Transaction code and TAC queues	Yes	Yes	Yes
TACCLASS	TAC classes	No	Yes	No
TPOOL	LTERM pools	No	Yes	No
USER	User IDs	Yes	Yes	Yes

* It does not make sense to create or delete the application parameters. The openUTM manual “Administering Applications” and the WinAdmin and WebAdmin online help systems describe which parameters can be changed.

It is also possible to delete RSA keys and create new keys. By default, RSA keys are created in the KDCDEF run in accordance with the entries for PTERM, TAC and TPOOL.

All dynamic changes to the UTM generation are subject to transaction management. In other words, the change is carried out either in its entirety or not at all. If you use WinAdmin, you can also group a number of steps together in a transaction (change the properties of multiple users at once, for example).

When objects are to be created dynamically, sufficient storage space must be reserved at generation with KDCDEF.

The openUTM manual “Administering Applications” tells you which objects and parameters can be changed dynamically and how this is done (look for information on the KDCADMI program interface and transaction management).