To modify an application you can change your design model as necessary, revisit any function designs that need to take account of the changes, and regenerate all elements dependent on the changes to the files.
For instance, let us say that you want to add a field to a file. CA 2E will automatically add the field to all the necessary access paths (except for those you have earmarked as being unalterable) and make it available on all of the device designs dependent on the access paths. You can use the panel and report design tools to place the field where you want it on these existing designs. The appropriate logic will be added to the function to handle referential integrity checking where appropriate.
You can assess the implications of the changes using interactive inquiries as well as the model documentation reports.
In most cases, regeneration becomes a routine matter. Using the batch generation facilities of CA 2E, it is possible to have an entire system regenerate itself to take account of a database modification.
For example, when a field is used in a function, the function keeps a reference to the field that is resolved when the function is generated. If you make a change, such as to the length of the field, it is reflected within the function's program logic and panel or report design when you next generate the function. This unique feature of CA 2E allows a massive reduction in the maintenance of CA 2E generated applications.
|
Copyright © 2014 CA.
All rights reserved.
|
|