When system maintenance is required, make CA Gen model changes on the workstation or mainframe, regenerate the changed elements into remote files, and move the files to the target system. This allows enhancements and modifications to implemented systems without changing the generated code.
After an application is tested and ready for production, move it to the proper environment and introduce it into production. Each organization using the Implementation Toolset may perform these tasks differently. Some elements are common to all installations.
To run a generated application in production requires the application, the DBMS the application uses, and the AEFN. The AEFN serves as an operating environment to handle communication between the operating system and the generated application.
Many CA Gen operating environment elements can be customized for the target system. The CA Gen runtime user exits allow access to certain system functions, such as retrieving a user ID or handling errors that may be changed to fit a specific target system configuration. The user exits are source language routines in which to add customized code. When compiled and placed in the proper library, the load module's dialog manager accesses them as the generated application executes.
|
Copyright © 2013 CA.
All rights reserved.
|
|