Unix and Linux 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:
   utm-path/ex.
   The kdcdef program used to start the KDCDEF generation tool is located in this directory.

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

3. Create the filebase directory (base directory of the application) in which openUTM stores the KDCFILE and other application-specific files. Enter the following command to create this directory:

   mkdir filebase

   You must create the directory before starting KDCDEF. filebase is the directory that you specified in the MAX statement in the FILEBASE= operand.

4. You start the KDCDEF tool with the kdcdef program.

   By default, KDCDEF reads the KDCDEF control statements from stdin. Only the control options for the KDCDEF run are read in from a shell script (see OPTION statement in section "OPTION - manage the KDCDEF run"), while the actual generation statements for KDCDEF are read from the files created in Step 2. You can specify these files directly at the start of KDCDEF:

   kdcdef < definput

   or after KDCDEF has been started using the KDCDEF statement OPTION:

   OPTION DATA=definput

   END

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 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.