Storage
change breakpoints are not available when debugging interpreted Java programs. They are
available when debugging High Performance Compiled (HPC) Java programs.
Storage change breakpoints halt execution of your program whenever storage at a specific address is changed. For example, if a byte being watched contains X'40' and the program writes X'40' to that byte, the storage change breakpoint is not triggered. If the program writes X'41', the storage change breakpoint is triggered.
To set a storage change breakpoint from the Breakpoints menu:
Caution: If you set a storage change breakpoint for any address that is on the call stack, be sure to remove the breakpoint before leaving the routine associated with it. Otherwise, when you return from the routine, the routine's stack frame will be removed from the stack, but the breakpoint will still be active. Any other routine that gets loaded on the stack will then contain the breakpoint.
Setting multiple breakpoints
Setting a conditional breakpoint
Modifying breakpoint properties
Enabling and disabling breakpoints
Deleting a breakpoint
Viewing breakpoints