Inverse KDCDEF for version migrations

When migrating to a new version of openUTM, you must first generate the KDCDEF control statements in the previous version, i.e. you must start the inverse KDCDEF in the previous version. You can use the files this KDCDEF generates as input files for KDCDEF in the new version of openUTM.