External Action Blocks access processing logic that is contained in subroutines that are not generated by CA Gen. You can create the external subroutine to fit a specific need, or it can exist previous to development of your application system. You create and compile the subroutine independent of CA Gen.
For example, you may want your application system to use a standard date manipulation or security routine that is defined specifically for your organization. Or the application may need to access databases that CA Gen toolsets do not support, 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:
CA Gen External Action Blocks are created using the workstation Design Toolset. An External Action Block contains no logic of its own. It contains only an EXTERNAL statement. The External Action Block is called by a USE statement in a procedure step or action block that is also created with the Design Toolset.
When you generate the External Action Block using the Host Encyclopedia Construction Tools, a program skeleton that is called a stub is created that includes much of the working storage and linkage for a framework for the External Action Block. External action block stubs are generated once, then modified by the user, and later maintained by hand.
The External Action Block is a modified stub that accesses or contains an external subroutine. Modify the stub by adding a call to the external subroutine or the subroutine logic itself.
The External Subroutine is the non-CA Gen program logic or transaction you want to access from the CA Gen generated application.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|