Implementing External Action Blocks

This chapter describes how External Action Blocks access processing logic contained in subroutines that are not generated by CA Gen. You can create an external subroutine to fit a specific need, or you can use code that existed before development of your application system. You create and compile the subroutine independently of CA Gen.

For example, you may want your application system to use a standard date manipulation or security routine defined specifically for your organization. Alternatively, the application may need to access databases that are either not supported by CA Gen toolsets (such as DL/I), or that contain entities (tables) not defined in the model's Data Model.

External Action Blocks are part of a procedure step and have the following characteristics:

Called from a procedure step or from an action block
Allow view matching
Return to the calling procedure step or action block when completed

This chapter discusses:

Prerequisites for using External Action Blocks
Terms that help you understand the process
Overview of the procedure to create and implement an External Action Block
Load module structure
Creating CA Gen External Action Blocks and the calling procedure steps or action blocks
Creating your own External Action Block source