The CA Gen software does not require an understanding of load module structure to generate and install application systems. However, an understanding of the structure of load modules is an important aid in performance tuning and in the investigation of runtime error messages.
Creating a load module that is ready for execution in a specific environment has the following stages:
In the first stage, you implement the business rules of your organization with action statements.
In the second stage, you package the procedure steps and action blocks into load modules or batch jobs. This is influenced by the characteristics of the target operating system. Some systems are more efficient with fewer but larger load modules while other environments are more efficient with more but smaller load modules.
In the third stage, you generate source code which integrates:
In the fourth stage, TP monitor-specific constructs are included within the load module when it is installed. CA Gen-supplied user exits are linked to by the load module during execution.
An analogy can be made between the top-down approach to programming and the usage of procedure steps and action blocks. In a Top-Down Structured program, all code is contained within paragraphs. Control does not simply flow from the top of the program to the bottom, and there are no explicit GO TO commands. One main paragraph placed at the beginning of the procedural section controls the flow within the program by calling paragraphs. Each paragraph returns to the main paragraph upon completion. A procedure step performs the function of the main control paragraph by issuing USE statements which invoke specific action blocks.
The term load module means the same thing in the IBM host environment as it does in CA Gen. Other operating systems have their own terms for executable code.
|
Copyright © 2013 CA.
All rights reserved.
|
|