Previous Topic: MFS SourceNext Topic: External Action Blocks


Procedure Steps and Action Blocks

CA Gen generates a source module for each procedure step and action block. If the application uses databases, the generated source code includes the SQL/DML statements to access the tables. Each generated source module includes a listing of its action diagram, its views, and related dialog flow details. In the COBOL source, this listing is at the end of the module and is cross-referenced to the generated source code to help analyze problems that result from errors in the action diagram logic. You can also generate a listing of the action diagram separately, without generating the source code.

The procedure steps in each load module are selected from a list of all the procedure steps that are defined for the business system during load module packaging. Recall that online transactions have no restrictions on the number of procedure steps you can package in each load module. Batch applications require that you package only one procedure step per single load module.

Action blocks are included in load modules when the procedure steps packaged in the load module use them, or when other action blocks use them.

Procedure steps and action blocks are statically linked with the load module or dynamically linked when the load module executes.

An other action block or action diagram in that model uses an action block that is defined in a model.

Although many business systems USE an action block, generate it only in the business system that owns it. After generation, other business systems can successfully install modules that USE the action block. The business system that owns an action block is established when it is first USEd, when it is scoped, or if it is copied with CA Gen COPY function. These activities occur on the workstation.

When an action block owned by one business system is USEd by an action block in another business system, it is referred to as a foreign action block. If a foreign action block was not generated and installed, you get an error. If the foreign action block is statically linked, the error is an unresolved reference during the installation. If the foreign action block is dynamically linked, the error is an indication that the program is not found during execution.

It is sometimes necessary to generate an action block in a business system other than the one that owns it. For example, if the owning business system has no load modules that contain the action block, it cannot be generated there.

More information:

Load Module Packaging in HE

List a Procedure Action Diagram