0 / 0
Local subflows in DataStage

Local subflows in DataStage

The main purpose of using a local subflow is to simplify a complex design visually to make it easier to understand.

If the data flow has lots of stages and links, it might be easier to create local subflows to describe a particular sequence of steps. Subflows are linked to other stages or subflows in the flow by input and output stages.

Creating a local subflow

If your job design is becoming complex, you can modularize the design by grouping stages and links into a subflow. To save an existing group of stages and links in a local subflow:

  1. Click shift, select each stage that you want included, and right-click in the white space.
  2. Choose Create local subflow. The group is replaced by a Local subflow stage.

Palette and canvas in Orchestration Pipelines

Viewing or modifying a local subflow

To view or modify a local subflow, double-click the subflow. You can then modify the existing stages or links or you can add new ones.

Deconstructing a local subflow

If required, you can convert a local subflow back into a group of discrete stages and links in the job where it is used. To deconstruct a local subflow:
  1. Select a local subflow in the DataStage® design canvas.
  2. Right-click on the subflow and select Deconstruct.
  3. Click OK to confirm the action.

The constituent parts of the subflow appear on the DataStage design canvas, with existing stages and links shifted to accommodate them.

Deconstructing a local subflow is not recursive. If the subflow you are deconstructing contains other subflows, they move up a level but are not themselves deconstructed.

Generative AI search and answer
These answers are generated by a large language model in watsonx.ai based on content from the product documentation. Learn more