To make changes to the application, you must change the CA Gen model, not the generated code, to generate the updated application. After changing the model regenerate that portion of the application on the development platform.
When the change does not update the load module definition, only select the necessary load module components for regeneration instead of the complete model. Move the regenerated components to the target system, overlaying the old versions of the components and rebuild the load module. This saves time and resources required to split a remote file whose definition has not changed.
Note: Verify file names, especially suffixes, before overlaying files. If file names differ, change the name of the new file to match the old one so the MAKE command procedure used during the rebuild searches for the correct file.
If a load module definition changes or most of its components change, generate a new remote file, move it to the target system, and rebuild the application.
After testing an application, you can regenerate it without the trace code and install it for production use.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|