This section lists the key changes made to Debug Tool for z/OS®.
All references to z/OS XL C/C++, Version 1.11, have been changed to z/OS XL C/C++, Version 1.10.
The following topics in the Debug Tool User’s Guide have been updated to describe the PTFs you must apply to z/OS XL C/C++ and the runtime environment:
The following changes, if applicable, are marked with revision bars:
If you are not familiar with .mdbg files and how to create them, see the topics "dbgld - Create a module map for debugging" or "CDADBGLD - Create a debug side file for the module map" in z/OS XL C/C++ User’s Guide.
You can indicate that Debug Tool always search through .mdbg files for source and debug information by setting the EQAXOPT option MDBG to YES in the EQAOPTS options file. To learn how to set the MDBG option, see "MDBG" in Debug Tool Customization Guide. In situations where you can specify environment variables, you can set the environment variable EQA_USE_MDBG to YES or NO, which overrides any setting (including the default setting) of the EQAXOPT MDBG option.
To learn how .mdbg files can help Debug Tool locate source and debug information, see "How does Debug Tool locate source, listing, or separate debug files?" in Debug Tool User’s Guide.
You need to apply several PTFs to the compiler and the runtime environment, which are listed in the following topics of the Debug Tool User’s Guide:
To learn what compiler options to choose to create .dbg files, which the dbgld command or CDADBGLD utility use to build the .mdbg files, see the following topics in Debug Tool User’s Guide:
There are several different methods of specifying the location of .dbg and .mdbg files. The following list summarizes each method:
After you specify the location of the .dbg and .mdbg files, you can use the following commands to verify the location:
The following topics have been added to or updated in the Debug Tool Customization Guide:
In the Debug Tool User’s Guide, the topic "Starting a debugging session in full-screen mode using a dedicated terminal" has been updated.
In the Debug Tool Reference and Messages and Debug Tool Reference Summary, the descriptions and syntax diagrams of the following commands have been updated:
In Debug Tool User’s Guide, the topic "Displaying the Working-Storage Section of a COBOL program in the Monitor window" has been added to describe how to add these variables to the Monitor window.
In Debug Tool Reference and Messages, the topic MONITOR command has been updated to describe the new suboption WSS.
In Debug Tool Reference Summary, the syntax diagram in "MONITOR command" has been updated to include the new suboption WSS.
In Debug Tool User’s Guide, the following topics have been added or updated:
In Debug Tool Reference Summary and Debug Tool Reference and Messages, the following topics have been added:
In Debug Tool User’s Guide, an item on the list in "Restrictions for modifying variables in the Monitor window" has been removed.
In Debug Tool User’s Guide, phrases that describe this limitation have been removed from the following topics:
In Debug Tool Reference and Messages, phrases that describe this limitation have been removed from the following topics:
In Debug Tool User’s Guide, the following topics have been updated to clarify how to scroll to a particular line:
In Debug Tool Reference and Messages and Debug Tool Reference Summary, the commands FINDBP and POSITION are described in topics FINDBP command and POSITION command.
Previously, you identified a program through the Program ID field. This has changed to two fields: LoadMod and CU.
In Debug Tool Reference Summary, the following syntax diagrams have been updated to describe the new options:
In Debug Tool Reference and Messages, the following syntax diagrams have been updated to describe the new options:
In Debug Tool User’s Guide, the instructions in "Creating and storing a DTCN profile" have been updated to describe the new fields.
In Debug Tool Customization Guide, DTCNFORCELOADMODID and DTCNFORCECUID have been added to "Defining EQAOPTS options: checklist and instructions".
In Debug Tool Reference Summary and Debug Tool Reference and Messages, the description of the following commands have been updated to describe how you cannot use them in browse mode:
The topic QUERY command has been updated to describe the new option BROWSE MODE.
In Debug Tool User’s Guide, the topic "Choosing a debugging mode" has been updated to describe how browse mode works and how you control browse mode.
In Debug Tool Customization Guide, the following topics have been added to describe the customization tasks you must do for this feature:
In Debug Tool Reference and Messages, the usage note that describes this limitation has been removed from MONITOR command.
In Debug Tool Reference and Messages and Debug Tool Reference Summary, the following topics have been updated:
In the Debug Tool User’s Guide, the topic "Monitor window" has been updated to describe how to increase the number of lines that the Monitor window displays and the implications of monitoring large volumes of data.
In Debug Tool Reference and Messages, an existing usage note has been modified and a new usage note has been added to AT CHANGE command (full screen mode, line mode, batch mode) that describes how Debug Tool monitors these variables.
In the Debug Tool User’s Guide, the following topics have been updated:
In the Debug Tool User’s Guide, the following topics have been updated to describe how to use the L and M prefix commands on assembler and disassembly programs:
Some of these topics also describe a slight change in terminology. These topics use the word "operand" to mean a variable in C, C++, COBOL, or PL/I, or the operand of an assembler instruction.
In Debug Tool Reference and Messages, the topics L prefix command (full-screen mode) and M prefix (full-screen mode) have been updated to describe how to identify operands or variables on a statement, describe the limitations of this support, and show a new example.