The following changes were added for IBM® z/OS® Debugger Version 14.1.10.
The following changes were added for IBM z/OS Debugger Version 14.1.9.
The following changes were added for IBM z/OS Debugger Version 14.1.7.
The following changes were added for IBM z/OS Debugger Version 14.1.6.
For a list of debug features in this combination, see IBM z/OS Debugger as a component.
For installation information, see Product Registration.
The following changes were added for IBM z/OS Debugger Version 14.1.5.
A new preference is added so that you can set or clear the global engine search path on the Compiled Debug preference page. This preference applies to all incoming debug sessions that cannot be matched to a launch.
The following changes were added for IBM z/OS Debugger Version 14.1.3.
An option is added to IMS Transaction Isolation to preserve the original PSB. For more information, see the new EQAOPTS command IMSISOORIGPSB.
The Load Module Analyzer is enhanced to support Toolkit for Swift on z/OS.
The Step option list is added on the Remote Profile tab for you to control the step in the remote debug profile. You can now override the computed step with a custom step, or choose not to include the step in the remote profile. For more information on the step option, see Remote Profile Tab.
A topic is added to introduce how to use the Playback toolbar. For more information, see Using the Playback toolbar.
The following changes were added for IBM z/OS Debugger Version 14.1.2.
IBM z/OS Debugger is progressing towards one remote debug mode based on Debug Tool compatibility mode. In support of this direction, Debug Tool compatibility mode, when available in the user interface, is selected by default for V14.1.2 or later. Any existing launches, property groups, or updated preferences remain unchanged. For more information on Debug Tool compatibility mode, see Remote debugging with IBM z/OS Debugger.
Structures and arrays are no longer limited to 100 entries when you inspect variables in the debug hover help during a debug session.
When you use line mode, batch mode, full screen mode, and remote mode with Debug Tool compatibility mode, and compile with the TEST(SEPARATE,SOURCE) option of the Enterprise COBOL for z/OS Version 6 Release 2 compiler, if the name of the side file does not match the PROGRAM-ID, the debugger can now locate the side file, as long as it is in the specified data sets or directories.
When you specify the side file location, you can now specify a z/OS UNIX System Services directory through a SET SOURCE command, EQAUEDAT user exit, SET DEFAULT LISTINGS command, EQADEBUG DD name, or EQA_DBG_SYSDEBUG environment variable.
For more information, see Choosing TEST or NOTEST compiler suboptions for COBOL programs.
You can now use CEETEST to restart z/OS Debugger after you use QUIT DEBUG. To start z/OS Debugger when a CEETEST call is encountered, set the EQAOPTS CEEREACTAFTERQDBG command to YES. For more information, see Additional notes about starting z/OS Debugger with CEETEST.
An Other run-time options field is added to the Manage Additional Libraries and Delay Debug panel (EQAPMPRG). With this new field, you can specify Language Environment® options for the private message region. For more information, see Using IMS Transaction Isolation to create a private message-processing region and select transactions to debug.
The following changes were added for IBM z/OS Debugger Version 14.1.1.
Remote debugging can now be used on macOS. For limitations, see macOS limitations and differences.
Code Coverage API (CCAPI) Javadoc is now included. Use CCAPI to parse and merge code coverage results programmatically and integrate the results with your custom tools. For more information, see Code Coverage API.
The following changes were added for IBM z/OS Debugger Version 14.1.
New installation verification programs are available for standard mode. For more information, see Running the installation verification programs for SVCs, Running the installation verification programs in a CICS region, and Running the installation verification programs for Debug Manager.
Variable values can be changed in the hovering Debug editor window. For more information, see Inspecting variables.