NOTICE: Our Community is moving. Get more information. Updated information on a New Login Process
In a project with Natural/ADABAS programs loaded and verified, the CRUD report fails to capture Table and File operations, such as UPDATE/FIND/STORE statements. Why does this happen?
This is caused by an incomplete project.
If a Natural program reads from a certain ADABAS file, then the corressponding .DDM is expected by Enterprise Analyzer. If the file is not in the project, the database / file access is not shown on the CRUD report.All items/entities of the project are expected to be available in Enterprise Analyzer, so that the correct relationships can be created.
The DDM is required to complete the relationships to the database, if it is not present in the project, then CRUD cannot report correctly.
By making sure all required items/entities are included in the project, the CRUD report will contain the required information.