The Dialog Manager uses a dialog flow transaction code to manage flows, that is links and transfers, between procedure steps. During load module packaging, a dialog flow transaction code must be assigned to every procedure step that is flowed to from another procedure step. The dialog flows are identified in the Dialog Flow Diagram.
Every procedure step that is not a first procedure step must have a dialog flow transaction code. This type of procedure step is always accessed (flowed to) from another procedure step. It cannot be invoked from a clear screen or another program.
First procedure steps require a dialog flow transaction code if they can be flowed to from another procedure step. The clear screen and dialog flow transaction code can be the same. A first procedure step that is accessed only from a clear screen does not require a dialog flow transaction code.
Dialog flow transaction codes do not have to be unique. You can assign the same code to more than one procedure step. However, a dialog flow transaction code must uniquely identify a load module. This means that all procedure steps associated with the same dialog flow transaction code must be packaged in the same load module.
The TP monitor uses the dialog flow transaction code to determine which load module to execute. However, in this case, the Dialog Manager that is based on information that is passed on the message queue determines the procedure step. Therefore, the dialog flow transaction code must uniquely identify the load module, but does not be associated with only one procedure step in the load module.
Note: The dialog flow transaction code is not used to determine the load module to execute on a return from a link. The transaction code that is used on a return from link is the transaction code that was active when the link was initiated.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|