The inverse KDCDEF either writes all control statements to one file or it writes the control statements for each group of objects to separate files.
On BS2000 systems, the control statements can also be written to an LMS library element instead of a file.
You can pass the files written by inverse KDCDEF as input to KDCDEF when the application is regenerated. To do so, you must enter the control statement OPTION DATA=filename for each of these files.
You can pass the files generated by inverse KDCDEF as input files direct to KDCDEF. However, you can also edit the files as well, i.e. you can modify them before the next KDCDEF run.
Whether or not LMS library elements on BS2000 systems can be modified depends on their type – only text-type elements can be modified.
You define the names of files generated by inverse KDCDEF when starting the inverse KDCDEF. If no file with this name exists, a new one is created automatically. If a file of this name does exist, you can define whether it should be overwritten or appended.