With the new Enterprise COBOL for z/OS V6.2 compiler and the IBM z/OS Debugger V14.1, you can now use the actual source used during the compilation to populate the source view in the Eclipse user interface when debugging. This functionality is available in standard mode. Standard mode refers to the merged architecture of the RD/z Integrated Debugger where a significant amount of debug engine processing is performed on the client, along with the z/OS engine based on Debug Tool.
Prior to IBM z/OS Debugger V14.1, the only view of the source available to the users when they debug or run code coverage on a COBOL application was the Expanded Source view. The Expanded Source view replaces the COPY statements in the COBOL source with the actual contents of the copybook for which they are referencing. This can lead to a very bloated view of your source with all this additional information. In comparison, the Source view shows the original content of a source file with the COPY statements not expanded, making the source easier to navigate compared to the Expanded Source view.
With the addition of this brand-new Source view and some other enhancements, you can now perform the following actions:
â€˘ Switch between the actual source view and the Expanded Source view during a debug session. You still have access to the Expanded Source view.
â€˘ Gather code coverage statistics which identify executed and unexecuted statements in the actual source instead of the expanded source.
â€˘ Set the default view and subsequent debug sessions will use the selected view as the default view.
Standard mode users will also continue to have access to the Mixed view (shows the expanded source along with the machine instructions) and the Disassembly view (shows just the machine instructions).
In summary, you can now use the actual source used during the compilation to populate the source view in the Eclipse user interface, which makes the source easier to navigate compared to the Expanded Source view.
For more information about using the Source view, see Switching between different debug views.