Stepping out of source code

Before you start

To complete this task, you must have completed the following tasks:

The flow being debugged must be paused at a breakpoint containing ESQL code or Java code, and you must have stepped into the code.

In a message flow there are three types of node that can contain source code:
  • Nodes that contain ESQL code: Compute node, Filter node, or Database node that contains ESQL code.
  • Nodes that contain Java code: User-defined node containing Java code.
  • Nodes used to access and maintain mappings: a Mapping node, DataInsert node, DataUpdate node, DataDelete node, Extract node, or Warehouse node that contains mapping routines.
When you stop at a breakpoint at a piece of source code, you can choose how to step past the code:

To step out of source code:

  1. Switch to the Debug perspective.
  2. In the Debug view, click the Step Return icon Step return on the toolbar (or right-click the flow stack frame, then click Step return Step Return). The source code runs, but the flow pauses at the next breakpoint within the source code, if there is one. If there is no breakpoint, or if the debugger is stepping out of the last line of code, the perspective switches to the Debug perspective and the flow automatically pauses at the next location where a breakpoint either exists or can be added.
Related concepts
Flow debugger overview
Related tasks
Debugging a message flow
Stepping into source code
Related reference
Flow debugger shortcuts
Flow debugger icons and symbols