The Transaction Manager, which is generated during installation of each load module, acts as an executive to control the flow between procedure steps. The following lists shows the types of transaction managers:
TIRMAIN is a CA Gen-supplied runtime module that is the entry point of all load modules. TIRMAIN calls the appropriate Transaction Manager, which then takes over the control of the dialog flow (links and transfers) between procedure steps.
The Transaction Manager maintains execution context using a mechanism called the Profile Manager. To accomplish this, the Transaction Manager uses information from procedure step import and export views, screen definitions, dialog flow, and load module packaging.
For character-based (block mode) applications, the Transaction Manager contains cross-reference tables of procedure steps, exit states, and transaction codes for the procedure steps packaged in the load module. The procedure steps to which the load module procedure steps link or transfer are also cross-referenced. The Transaction Manager uses all of this information to select the target procedure step within its load module. If the target procedure step is in another load module, the information is used to select the transaction code that invokes the load module containing the target procedure step.
When a load module is executed, the Transaction Manager determines the procedure step to execute. It then populates the import view of the procedure step using screen input and data passed from another procedure step or data taken from the Profile Manager. This allows each procedure step to reference data in its input view without having to perform the processing required to gather it.
Note: Window Managers do not use the names TIRMAIN and TIRMSG, but the transaction concepts for GUI applications are the same.
|
Copyright © 2013 CA.
All rights reserved.
|
|