Describes the changes introduced with Debug Tool V9.1 that affect the compiled language debugger.
Additional commands that were previously available only in full-screen mode are now available in remote debug mode. A list of Debug Tool commands supported in remote debug mode has been moved from Debug Tool User's Guide to the topic "Debug Tool commands supported in remote debug mode" in Debug Tool Reference and Messages. This topic has been updated to include instructions on how to enter these commands in the compiled language debugger.
If you are debugging a program compiled with Enterprise COBOL for z/OS, V3.4 or later, or Enterprise PL/I for z/OS, V3.5 or later, you can now show the data type of variables in the Variables window or Monitors window. To do this, first you disable viewing variables by columns, then you enable the display of data type names.
To enable the display of data type names in the Variables or Monitors window, click on Show Types Names. The compiled language debugger displays the data type name to the left of the variable name.
You can now display the value of a variable on a statement before or after the statement runs. This feature is available only for variables in a local scope.
Before you run the statements that contain the variables you want to monitor (or watch), right-click in the Variables window, then click on Filter Locals. The compiled language debugger displays a list of filters you can use to display fewer variables in the Variables window. If you want the compiled language debugger to display the value of a variable after a statement is run, make sure there is a check next to Automonitor Previous. If you want the compiled language debugger to display the value of a variable before a statement is run, make sure there is a check next to Automonitor current. You can enable both filters to show you how variables values change as you step through statements.
Describes the changes introduced to Debug Tool V9.1 when the PTF for APAR PK72833 is applied that affect the compiled language debugger.
Describes the changes introduced to Debug Tool V9.1 when the PTF for APAR PK72833 is applied that affect the compiled language debugger.
When the compiled language debugger stops at a breakpoint set in an Enterprise PL/I INCLUDE file or C/C++ header file, the Debugger editor now displays the source of that file and marks that line with the breakpoint.
The compiled language debugger now saves and restores breakpoints set in these files.
For PL/I programs compiled with the SEPARATE compiler option, when you click on the Debugger editor that is displaying the INCLUDE file, the compiled language debugger now displays the source of the INCLUDE file.
The compiled language debugger displays the source of the INCLUDE or header file in one Debugger editor. For example, if you have three compile units (PROGA, PROGB, and PROGC) in a single load module, and all three compile units reference the INCLUDE file INCLZ, the compiled language debugger displays the source for INCLZ in one Debugger editor. If you set a breakpoint in INCLZ while debugging PROGA, the compiled language debugger marks that breakpoint in the Debugger editor. If you debug PROGB or PROGC and then click on the Debugger editor showing INCLZ, the compiled language debugger displays the mark for the breakpoint you set while debugging PROGA. However, the compiled language debugger stops at that breakpoint only when it runs PROGA.
In the CICS environment, you can set Debug Tool to ignore enclaves created by EXEC LINK or EXEC XCTL statements. Enter the SET IGNORELINK ON command in the Debug Console. To find out how to debug programs created in new enclaves, see the topic "SET IGNORELINK command" in Reference and Messages. To find out if the IGNORELINK setting is on, enter the command QUERY IGNORELINK in the Debug Console.