KDCDEF carries out syntax and plausibility checks for all control statements entered. If KDCDEF does not detect any serious errors, then KDCDEF creates the KDCFILE and/or the source code for the ROOT tables, depending on what you have specified in OPTION.
In the case of UTM cluster applications, the UTM cluster files are also created where necessary.
KDCDEF always executes the plausibility checks for all control statements. If only one ROOT table source is created in a KDCDEF run, for example, then KDCDEF also checks the control statements that only affect the KDCFILE.
For this reason you should execute every KDCDEF run using all generation information, regardless of whether on the source code for the ROOT tables or only the KDCFILE is to be created.
Inconsistencies arising during the creation of the ROOT table module and KDCFILE that would otherwise only be detected once the application is started can be detected much earlier when complete plausibility checks are used. Errors are avoided.