Rational Developer for System z

CRRZE7343W

The flow contains multiple output paths. Web service artifacts can be generated only for a single input path and a single output path. Web service artifacts for the output path resulting in a Reply node were generated, and the other output paths were ignored

Explanation

Restriction: When the Generate Runtime Code wizard creates COBOL source code for a Web service, and the flow from which the wizard creates the Web service contains a Throw node, then the wizard ignores the Throw node and does not create a return point for the Web service at the corresponding point in the COBOL source code.

The reason is that the generated COBOL source code for a Web service can include only two interface points with the invoking program:
  • One input point, corresponding to the Receive node in the flow.
  • One output point, corresponding with the Reply node in the flow.

The source code cannot contain additional return points associated with Throw nodes.

It is completely valid for a flow to contain one or more Throw nodes. But currently, when the Generate Runtime Code wizard is creating a Web service and encounters a Throw node, the wizard ignores the Throw node and does not create a corresponding return point in the COBOL source code.

User response

Modify the design of the flow so that it does not rely on a Throw node as a return point to the program that invokes the flow.

See Restrictions on execution within flows.


Terms of use | Feedback

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