Starting inverse KDCDEF

Inverse KDCDEF can be started online or offline.

The inverse KDCDEF run is started online by issuing the KC_CREATE_STATEMENTS call via the program interface for administration. Further information can be found in the openUTM manual “Administering Applications”. Inverse KDCDEF can only be started offline if the application is not running, i.e. outside the application runtime. Since inverse KDCDEF reads data from the KDCFILE, you must ensure that this data is not modified during the inverse KDCDEF run.

Inverse KDCDEF can be started offline by calling the KDCDEF generation tool and issuing the control statement CREATE-CONTROL-STATEMENTS. This statement is described in section "CREATE-CONTROL-STATEMENTS - Create KDCDEF control statements". You can start inverse KDCDEF such that KDCDEF control statements are created either for all permitted object types, or only for those object types combined in the object groups CON, DEVICE, KSET, LSES, LTAC, PROGRAM and USER.

• CREATE-CONTROL-STATEMENTS *ALL

  KDCDEF control statements are created for all objects of type TAC, PROGRAM, PTERM, LTERM USER, KSET, LTAC, CON and LSES.

• CREATE-CONTROL-STATEMENTS DEVICE

  LTERM and PTERM statements are created for LTERM partners, clients and printers.

• CREATE-CONTROL-STATEMENTS PROGRAM

  PROGRAM and TAC statements are created for program units, conversation exits, and transaction codes.

• CREATE-CONTROL-STATEMENTS USER

  USER statements are created for user IDs.

• CREATE-CONTROL-STATEMENTS KSET

  KSET statements are created for key sets.

• CREATE-CONTROL-STATEMENTS LTAC

  LTAC statements are created for transaction codes. These are used to start the service programs in partner applications.

• CREATE-CONTROL-STATEMENTS CON

  CON statements are created for transport connections to remote LU6.1 applications.

• CREATE-CONTROL-STATEMENTS LSES

  LSES statements are created for assigning new LU6.1 session names.