Ensure that you have specified the correct operating system, programming language, database management system (DBMS), screen format type, and teleprocessing monitor to be used for implementation.
Generate Referential Integrity trigger modules before generating load modules. Generating the RI triggers adds the source member names for the trigger modules to the model. The names are required when you generate action blocks that call the RI modules.
If you select Delete Source After Install when installing load modules, ensure that the load modules are installed in the same order in which they are generated. When more than one load module uses the same common action block, the first load module to be generated contains the actual code. After this first module is generated, the source code is deleted and all other load modules contain only the reference to this action block. If the load modules are installed in an order different from the order in which they were created, a load module that references the action block may be installed before the load module that actually contains the action block. In that case, the installation will fail.
If your application uses external action blocks and you are installing locally, compile all of them before installing the load modules, which reference them. The external action blocks are compiled outside of the CA Gen.
If your application uses external action blocks and you are installing remotely, note that external action block code is not included in the remote module. It must be located and moved to your target system separately. You must compile all external action blocks used by your application before installing the load modules that reference them. The external action blocks are compiled outside of CA Gen. They must then be moved to the location defined for them in your Target Configuration so that your application can find them.
