If changes need to be made to the application, the CA Gen model must be changed to generate the updated application, not the generated code. This applies whether the change is made to correct a problem or enhance the application. After the model is changed, regenerate that portion of the application on the development platform.
If the load module definition has not been updated by the changes, then only the necessary load module components need to be selected for regeneration instead of the complete model. The regenerated components can then be moved to the target system, overlaying the old versions of the components. The load module is then rebuilt. This saves the time and resources required to split a remote file whose definition has not changed.
Note: Make sure that file names and suffixes to file names are carefully verified before overlaying files. If file names differ, change the name of the new file to match the old one so that the MAKE command procedure used during the rebuild will search for the correct file.
If a load module definition has been changed, or if most of its components have been changed, then an entirely new remote file can be generated. The resulting remote file can then be moved to the target system, and the application built again.
After an application is tested, it can be regenerated without the trace code (if required) and installed for production use.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|