Your Browser is not longer supported

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

{{viewport.spaceProperty.prod}}

Windows systems

Proceed as follows to start the KDCDEF too and to execute a KDCDEF generation:

  1. Add the directory below to the PATH environment variable: utmpath\ex.The kdcdef.exe program used to start the KDCDEF generation tool and other utility programs and DLLs are located in this directory. Proceed as follows:

    • In the Control Panel, open the dialog box Environment Variables. Possible access: In the search box enter the term Environment Variables, continue with Edit the system environment variables / System Properties / Advanced / Environment Variables.

    • Enter the path listed above to the PATH variable and click on the "Set" button.

  2. Create one or more source files with control statements using an ASCII editor such as the NOTEPAD for the UTM generation. You must observe the information stated in section "Order of the control statements" and in section "Format of the control statements".

  3. Create the filebase directory (project directory) in which openUTM stores the KDCFILE and other application-specific files. You must create the directory before starting KDCDEF. filebase is the directory that you specified in the MAX statement in the FILEBASE= operand.

  4. Now start the KDCDEF tool. Open a command prompt window. KDCDEF reads the KDCDEF control statements from stdin by default, i.e. directly from the command prompt. Enter the following to have KDCDEF read the control statements from a file (e.g. definput.txt):

    kdcdef < definput.txt

    or start KDCDEF with kdcdef and pass the file using the KDCDEF statement OPTION:

    OPTION DATA=definput.txt

The messages and logs from KDCDEF are written to stdout and stderr, i.e. everything is displayed on the screen if you have not redirected the output. You can redirect the output to a file as follows (you can select any name you want for the files):

kdcdef < definput.txt 2>def.err 1>def.prot

All UTM messages are recorded in def.err and def.prot contains the complete log of the KDCDEF run.