During the load module packaging portion of construction, you can include external action blocks in your load modules in the same manner as other CA Gen procedure steps and action blocks. When generation occurs for that load module, information identifying the action block is included in the ICM for that remote file. However, the action block stub is not included in the resulting remote file. It must be moved to your target system separately. Similarly, if you hand-edit code into the external stubs, you should move the stubs out of the source code component subdirectory so that subsequent generations do not overwrite the edited stubs.
For example, on the Windows code generation platform, the external action block code must be moved from the source code component subdirectory (\c for the C language) associated with the model being implemented. The file containing external action block code is named using the action block name and a file extension appropriate to the language being used (.C).
|
Copyright © 2013 CA.
All rights reserved.
|
|