Make the display and operation of breakpiont controls consistent and/or clearly documented in RDz.

While working with tech support on a related issue (PMR 62618,756) a new issue was discovered (PMR 62862,756) relating to the behavior of breakpoint controls in RDz. According to tech support, the breakpoint controls in the 'Run menu' are only for Java development and should be disabled for other languages (like COBOL). However, once debugging a COBOL application, these menu items are re-enabled and have limited functionality. Specifically, 'Toggle Breakpoint' can only place a breakpoint on the line immediately following the current execution point, not on the currently selected line (which is he Eclipse default behavior). 'Toggle Method Breakpoint' produced an error message indicating that the current method could not be resolved. 'Toggle Line Breakpoint' produced an error message indicating that the current line could not be resolved. The behavior of the breakpoint controls should be more consistent. While there are numerous alternatives for this behavior, I would like to see (in order or highest preference to lowest preference): 1. Enable the breakpoint menu items for all languages supported by RDz and have them work in the 'default Eclipse manner'. 2. Remove the breakpoint menu options from the Run menu if the current project/language does not support their use. 3. have the breakpoint menu items remain disabled at all times with a floating tooltip that indicates that "breakpoint menu items are disabled for non-Java languages". Also, the documentation should very clearly state that run menu breakpoint menu items are only supported for the Java language; the closest that I have seen is the document "RDz Workbench - Debugging zOS COBOL-1.ppt", page 23, that states: "However, not all Run menu functionality enabled for COBOL/PL1", next to a screen shot of the Run menu with all breakpoint menu items enabled. This documentation is unclear on this point and can lead to wasted time (and tech support contacts) to determine why the functionality does not work as expected.