Your Browser is not longer supported

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

{{viewport.spaceProperty.prod}}

Components of the application program

A UTM application program is made up of a set of modules which must be linked as a program at runtime or before.

The following modules are required for execution:

  • root module

    Compiled ROOT table module which you must store in a program library or object module library. If you use the root dynamic loading technique, specify this library in the start parameter TABLIB= and the module name in the start parameter ROOTNAME=.

  • ROOT system modules

    Modules required by the UTM application for execution. They are contained in the library SYSLNK.UTM.070.

  • Program units

    The application program units you created which must be compiled and entered in one or more program libraries or object module libraries.

  • Database connection module

    Used for connecting the UTM application to the database system specified in the TYPE operand of the DATABASE statement during KDCDEF generation. The manuals for the corresponding database systems describe how this module is provided by the database system.

  • Connection module for the format handling system

    Used for connecting the UTM application to the format handling system generated in the TYPE operand of the FORMSYS statement. The manuals for the corresponding format handling systems describe how this module is provided by the format handling system.

  • Administration and UTM-SAT administration program unit

    Programs for administering the UTM application. You can either write this type of program yourself using the program interface for administration, or you can use the standard administration programs KDCADM and KDCSADM supplied with openUTM. Each administration program must be generated in a separate PROGRAM statement. The object modules of the administration programs are available in the library SYSLNK.UTM.070. The administration program KDCADM is always needed, even if you are using an administration program which you have created yourself.

  • Runtime system for KDCROOT

    This is always required and is supplied in the library SYSLNK.UTM.070.SPLRTS. In addition, KDCROOT needs one of the libraries SYSLNK.CRTE or SYSLNK.CRTE.PARTIAL-BIND, whereby the second library provides performance advantages and is therefore the preferred option. CRTE is the software prerequisite for openUTM and contains the C runtime system, the ILCS, and the COBOL runtime system. The C runtime system and the ILCS are always required by UTM.

  • Runtime systems of the programming languages

    These are required if at least one program unit of the application is written in a higher programming language. If the application contains ILCS-capable program units, you must ensure that the highest available ILCS version is incorporated. Further linking information can be found in the description of ILCS in the CRTE User Guide. The ILCS modules are contained in the CRTE library.

    The section "Compiler versions, runtime systems, KDCDEF options" describes which runtime systems can be used with which compiler versions.

  • Language connection modules

    These are needed for every generated programming language or its linkage. For SPL, Assembler, COB1 and ILCS linkage, these connection modules are already incorporated in the runtime system for KDCROOT. For all other programming languages, the connection modules must be incorporated from language-specific libraries when the application starts or before.

  • Shared areas

    (see AREA statement of KDCDEF)

  • User-specific message modules

    If user-specific message modules are to be linked statically.