Breakpoints and the Breakpoints View

When a debug session is launched, an initial breakpoint is automatically set on the first line of the program that was executed as specified in your launch configuration. All breakpoints set in Code Debug are before breakpoints.

Using Breakpoints

Breakpoints can be set and removed either within an active debug session or within your source before you launch a debug session. However, only new Before breakpoints can be set outside of an active session.

Each breakpoint is displayed in the Breakpoints view.

Breakpoints are retained after an active session ends.

Methods for loading modules into memory

There are two methods for loading modules into memory:

Automatically load modules and set associated existing breakpoints upon session start. Load modules specified on the Breakpoints tab are loaded into memory upon session start and associated breakpoints are automatically set that time. The default is to load all load modules associated with existing breakpoints.
Note
Note: The main module is loaded at the session start regardless of any settings in the Breakpoints tab.

Manually load modules and set breakpoints during a debug session. Breakpoints can be set at any time during a debug session. Existing breakpoints whose load modules were excluded by the Breakpoints tab settings have disabled (dark grey) text for their associated breakpoints’ text in the Breakpoints view.

To manually load modules and set breakpoints during a debug session

These breakpoints can be enabled by loading their associated load modules in one of the following ways:

Open the DDIO source listing via the Open DDIO view. Double-click on the CSECT or right-click it and select Open.
Right-click the breakpoint(s) in the Breakpoints view and select Load Associated Module(s).

Considerations

Loading modules other than the main module should be done with caution. Please be aware of the following before choosing to load such modules into memory:

Memory limitations with your program’s address space
Possible load module conflicts between multiple load libraries
Code Coverage activation of load modules that get loaded into your program’s address space

To group breakpoints in the Breakpoints view

To group breakpoints by type (such as Before and When), click in the Breakpoints view and select Group by>Breakpoint Types.
To list all breakpoints in one list, click in the Breakpoints view and select Group by>Breakpoints.

To add or remove breakpoints

Do either of the following to add or remove breakpoints:

Right-click the vertical ruler of a source display and select Toggle Breakpoint.
Double-click the vertical ruler next to a line.

The Breakpoints view shows all breakpoints that currently exist in the debug session.

Note

If a breakpoint is set on a non-executable line in a CICS debug session, it is automatically placed on the next available executable line. For instance, a breakpoint set on line 1 of a program will automatically be placed at the first executable line of the program.

To enable or disable breakpoints

Breakpoints can be enabled and disabled. A disabled breakpoint is still considered set, but will not interrupt program execution.

Do either of the following in the Breakpoints view to enable or disable breakpoints:

Select (to enable) or clear (to disable) the breakpoint's check box.
Right-click a breakpoint and select Enable or Disable.

To enable Code Debug TSO exit breakpoints

Users can choose to display and honor Code Debug TSO exit breakpoints or, more precisely, to emulate the functionality of Code Debug TSO for exit breakpoints within Code Debug. By default, these breakpoints are not displayed or honored.

To enable Code Debug TSO exit breakpoints, from the Window menu, select Preferences>BMC >Code Debug. Select the Enable Code Debug/TSO exit breakpoints check box.

Note

Changes to this setting do not take effect until a new debug session is started.

To close Compuware source listings after debug session terminates

By default, Compuware source listings are closed after the debug session terminates. To instead keep source listings open, from the Window menu select Preferences>BMC>Code Debug and clear the Close BMC Source Listings after debug session termination check box.

The Breakpoints View Toolbar

The following toolbar buttons are available on the Breakpoints view toolbar.

Button	Description
	Remove Selected Breakpoint - Removes the selected breakpoints from your debug session.
	Remove All Breakpoints - Removes all existing breakpoints from your debug session.
	Go to File for Breakpoint - Points the source display of the breakpoint’s associated CSECT at the line where the breakpoint is. You can achieve the same results by double-clicking on a given breakpoint in the Breakpoints view.
	Skip all Breakpoints - Directs Code Debug to bypass or ignore all breakpoints.