Using External Action Blocks › Why this Step is Necessary › Compiling, Binding, and Storing an External Action Block › Add the External Action Block to the External Library File

Add the External Action Block to the External Library File

When you install a CA Gen load module that uses external action blocks, the installation process requires an external library file. This file contains all compiled external action blocks and all subroutines called by them.

You must create the external library file in the extrn directory for UNIX and Linux. The directory in which the external library file resides is located in the same directory level in which CA Gen models are stored.

For UNIX and Linux, the library file must be named with the extension .a for C applications. You create the library file outside of the CA Gen with the ar command. For more information about the ar command and usage, see the UNIX and Linux compiler documentation.

If the external library file resides in a different location other than the extrn directory, use the Build Tool token LOC.EXTERNAL_LIB to point to the location of that library.

When you install an application from the Build Tool and set the LOC.EXTERNAL_LIB token, the Build Tool uses the external library file pointed to by that token.

The Build Tool adds optional levels to external library management. Traditionally, a single external library is referenced at the model level. Models referencing external objects to perform differing tasks may cause a conflict. The CA Gen Build Tool will additionally reference an external library in the EXTRN subdirectory subordinate to the generated code directory so that model-specific objects are managed better.

You can also process external action blocks for remote installations. For more information, see the Windows Implementation Toolset User Guide, the UNIX and Linux Implementation Toolset User Guide, the NonStop Implementation Toolset User Guide, or the z/OS Implementation Toolset User Guide.