Rational Developer for System z

Intermixed cycles

You can model intermixed cycles on the activity diagram, but their generation as COBOL statements is not easy.

Because their generation as COBOL statements is difficult, intermixed cycles are broken in order to keep one cycle that would be interpreted as a COBOL loop, and other intermixed cycles would be interpreted as pieces of sequential statements followed by a GOTO statement.


Feedback