Rational Developer for System z

Step A4. Edit the generation properties file for each invoked flow

If your program falls within Scenario 2, then for each generation properties file that you created for an invoked flow in Step A3, use the generation properties editor to verify or set the generation properties of the flow node and the invoke nodes contained in the generation properties file. (If your program falls within Scenario 1, then you can skip this step.)
Scenario 1 and Scenario 2 refer to the two scenarios described earlier (see Two development scenarios: (1) Main flow; (2) Main flow with invoked flows):

If your program falls within Scenario 2, then you need to make sure that the generation properties in the generation properties file for the invoked flow have the same values as the generation properties for the same invoked flow in the generation properties file for the main flow (see Requirement for the generation properties of invoked flows).

Tip: An easy way to make the two sets of generation properties have the same values is to set an option in the New Generation Properties wizard that allows you to reuse existing generation properties. You can set this option either when you create the generation properties file for the main flow or when you create the generation properties files for the invoked flows (see Reusing properties from the most recently saved generation properties file).
To edit a generation properties file for an invoked flow:
  1. Use the generation properties editor to edit the generation properties file for the invoked flow, following the same steps that you followed to edit a generation properties file for the main flow in Step A2 (see Step A2. Edit the generation properties file for the main flow).
    • The generation properties file for an invoked flow contains a flow node and invoke nodes that you can select and modify just as you did for the nodes of the main flow in Step A2.
    • The generation properties file for an invoked flow does not contain nodes from any other invoked flow, because an invoked flow cannot invoke another flow (an invoked flow must have a flow type of either FEPI or Link3270 Bridge, and these flow types cannot invoke another flow -- see About flow types).

  2. For the flow node:
    1. You must set the Flow Type field to either FEPI or Link3270 Bridge.
    2. Make sure that the generation properties of the flow node (including the flow type) are the same as the generation properties for the same node in the generation properties file for the main flow (see Reusing properties from the most recently saved generation properties file).
  3. For each invoke node:
    1. Make sure that the generation properties of the invoke node (including the invoke type) are the same as the generation properties for the same node in the generation properties file for the main flow (see Reusing properties from the most recently saved generation properties file).


Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)