This section lists the key changes
made to Debug Tool for z/OS® and
the locations in the publications describing these changes.
- You can now download a plug-in, called
the IBM Debug Tool plug-in for Eclipse, from the IBM® website
that adds a remote debugger to CICS Explorer™.
The following changes were made to the topic Remote debug mode:
- This plug-in was added to the list of products providing
supported remote debuggers. This list was also updated to remove remote
debuggers in products that are no longer supported.
- A link to the website with more information about the plug-in
and download instructions was added.
- Cross-references to online topics that help you get started
with the remote debuggers have been added.
- A new mode, called explicit debug mode, has
been added to help improve performance while debugging large, complex
applications by loading debug information for only the compile units
that you indicate. To learn more about explicit debug mode, see Optimizing the debugging of large applications.
A
new command, SET EXPLICITDEBUG, has been created and several
existing commands have been modified. The following list summarizes
the changes made to the Debug Tool Reference and Messages:
- A usage note has been added to the AT ENTRY command;
see "AT ENTRY command".
- The description of the LOADDEBUGDATA command has been
modified; see "LOADDEBUGDATA
command".
- A usage note has been added to the NAMES INCLUDE command;
see "NAMES INCLUDE
command".
- A new option, EXPLICITDEBUG, has been added to the QUERY command;
see "QUERY command".
- A new usage note has been added to the SET DISASSEMBLY command;
see "SET DISASSEMBLY
command".
- A description of the SET EXPLICITDEBUG command has
been added; see "SET EXPLICITDEBUG
command".
- A new usage note has been added to the SET IGNORELINK command;
see "SET IGNORELINK
command".
- Several new panels have been added to the
Terminal Interface Manager to help you create the TEST runtime options
data set. To learn how to use these panels, see Creating and managing the TEST runtime options data set.
- The Terminal Interface Manager has been enhanced
to remove the need for a site to set up a separate TN3270E port or
to customize a set of terminal LUs. The topic "Debug Tool Terminal
Interface Manager" in the Debug Tool Customization Guide has been updated.
- Debug Tool provides a new plug-in,
called the IBM Debug Tool DTCN and DTSP Profile Manager, that adds the DTCN
Profiles and DTSP Profile view
to the Debug perspective of your Eclipse
applications. These views help you manage your DTCN
profiles and the TEST runtime options data set (EQAUOPTS) on your z/OS system, respectively.
Before
you can use the DTCN Profiles view,
the system administrator must do the tasks described in the topic "Adding support
for the DTCN Profiles view and APIs" in the Debug Tool Customization Guide.
Before
you can use the DTSP Profile view,
the system administrator must do the tasks described in the topic "Adding
support for the DTSP Profile view" in the Debug Tool Customization Guide.
The following changes were made to the Debug Tool User’s Guide:
- You can now use the Debug Tool Language Environment® user
exit for DB2® (EQADDCXT) to debug DB2 stored procedures of type SUB
invoked by the call_sub function. The following topics in the Debug Tool User’s Guide were updated to describe how to do this:
- An additional method for specifying EQAOPTS options has been added.
You can now supply EQAOPTS options at run time by specifying a data
set containing EQAOPTS options. Information about the EQAOPTS options
has been reorganized and renamed. EQAOPTS options are now called EQAOPTS commands. Information about the EQAOPTS commands
is located in the following topics:
- In the Debug Tool Customization Guide, information previously found in "Defining
EQAOPTS options: checklist and instructions" has been moved to "EQAOPTS commands".
This topic is also included in Debug Tool Reference and Messages.
- A new option, EQAOPTS, has been added to the QUERY command;
see "QUERY command" in the Debug Tool Reference and Messages.
- The panels for DTCN have been updated to include a field where
you can specify the data set name of the EQAOPTS file; see Creating and storing a DTCN profile.
- A description of the EQAOPTS file has been added to Appendix A. Data sets used by Debug Tool.
- A new XML tag (<EQAOPTSFILE>) has been added to the topic "Definition
of XML tags" in the Debug Tool API User's Guide and Reference.
- Debug Tool now supports accessing the high-order
32 bits of the 64-bit General Purpose Registers (GPRs). In
the Debug Tool Reference and Messages, the following topics were updated:
- The following new symbols for the high-order bits were
added to the description of the symbol element; see "Common
syntax elements": RH0, RH1, RH2, RH3, RH4, RH5, RH6, RH7, RH8,
RH9, RH10, RH11, RH12, RH13, RH14, RH15.
- The description of the "LIST REGISTERS command" has
been updated.
- The description of new variables, %GPRHn, has been added
to "Debug Tool variables".
- Debug Tool changed the way it handles nested blocks
in C and C++ programs, which enhances performance. In the Debug Tool Reference and Messages, usage notes were added to the following topics:
- "AT ENTRY command"
- "AT EXIT command"
- "AT GLOBAL command"
- "AT PATH command"
The description of the BLOCK parameter of the SET CHANGE command
was changed; see "SET CHANGE command".
The topic "Changes in
behavior of some commands" describes this change in behavior.
- A new window, called the List pop-up
window, has been added that displays the results of the LIST expression command
when the Log window is closed. To learn how the window works, see List pop-up window.
- For PL/I programs, you can now use the PL/I
ADDRDATA built-in function and the "=>" operator.
In the Debug Tool User’s Guide, the following changes were made:
- For PL/I programs compiled with Enterprise
PL/I for z/OS, Version 4.1
or later, another scenario has been added to Choosing TEST or NOTEST compiler suboptions for PL/I programs to describe the
impact of specifying the GONUMBER(SEPARATE) compiler option.
- For programs compiled with any level of Enterprise PL/I,
you can now list a single element of an array of structures. For programs
compiled with Enterprise PL/I for z/OS,
Version 4.1, you can list a single element of an array of structures
in automonitor or use the L prefix command in the Source
window to list a single element of an array of structures.
The following
changes were made to the Debug Tool Reference and Messages:
- The description of the "SET AUTOMONITOR
command" was updated.
- The description of the "LIST expression
command" was updated.
In the Debug Tool User’s Guide, the topic Accessing PL/I structures was updated.
- For programs compiled with any level of Enterprise PL/I,
you can now change the format in which Debug Tool displays an array.
By using the new SET LIST BY SUBSCRIPT ON command, you
can have Debug Tool display the array as it is stored in memory.
The
description of "SET LIST BY SUBSCRIPT command" was added
to the Debug Tool Reference and Messages.
- A new keyword, LABELS, was added
to the LIST NAMES command where you can list the names
of all section and paragraph names in a COBOL program, and the names
of all instruction labels in an assembler program; see "LIST
NAMES command" in the Debug Tool Reference and Messages.
- New options, GLOBAL and LOCAL,
have been added to the AT CHANGE command so that you can
indicate that the command applies to all compile units or only to
a specific compile unit.
In Debug Tool Reference and Messages, "AT CHANGE command (full screen mode, line mode,
batch mode)" was updated.
- A new option, LOCAL, has been added
to the AT LABEL * command so that you can limit the scope
of the command to a specific compile unit.
In Debug Tool Reference and Messages, "AT LABEL command" was updated.
- A new option, OCCURRENCE, has been
added to the AT GLOBAL command so that you can set a breakpoint
that gives Debug Tool control whenever a valid condition occurs or an
exception is raised.
In Debug Tool Reference and Messages, the topic "AT GLOBAL command" was updated.
- You can now change the subscripts of an array
directly in the Monitor window. Instructions have been added to Replacing a variable in the Monitor window with another variable.
- The CLEAR MONITOR command has been
updated so you can specify a range of monitors to remove from the
Monitor window and so you can use the cursor to indicate which monitor
to remove from the Monitor window. In the Debug Tool Reference and Messages, see "CLEAR command". In the Debug Tool User’s Guide,
the list of prefix commands in Entering prefix commands on specific lines or statements has been updated.
- The QUERY LOCATION command has
been updated so that it displays the former and current value, in
hexadecimal format, of a variable when you set a breakpoint on the
variable with the AT CHANGE command.
In Debug Tool Reference and Messages, "QUERY command" was updated.
- A method for automatically allocating a SAVESETS
and SAVEBPS file and enabling the saving and restoring of settings,
breakpoints, and monitor specifications has been added.
If you are
not familiar with saving and restoring settings, breakpoints, and
monitor specifications, see Saving and restoring settings, breakpoints, and monitor specifications.
To
learn how this new method works and compare it to the previous method,
see Saving and restoring automatically.
Implementing
this method requires EQAOPTS commands. If you are not familiar with
EQAOPTS commands, see "EQAOPTS commands" in
the Debug Tool Reference and Messages or Debug Tool Customization Guide.
The descriptions
in the Debug Tool Reference and Messages for the following commands were updated:
- A new usage note has been added to the SET RESTORE command;
see "SET RESTORE command".
- A new usage note has been added to the SET SAVE command;
see "SET SAVE command".
The EQAOPTS commands SAVEBPDSNALLOC and SAVESETDSNALLOC were
added and described in "SAVEBPDSNALLOC,
SAVESETDSNALLOC" of both the Debug Tool Reference and Messages and Debug Tool Customization Guide.
- A method for establishing a naming pattern
for a log file, creating the log file, and, in a CICS® environment, enabling writing to a log file
has been added.
Implementing this method requires EQAOPTS commands.
If you are not familiar with EQAOPTS commands, see "EQAOPTS
commands" in the Debug Tool Reference and Messages or Debug Tool Customization Guide.
The following EQAOPTS commands were added and descriptions are located
in both the Debug Tool Reference and Messages and Debug Tool Customization Guide:
In the Debug Tool Reference and Messages, a new usage note has been
added to the SET LOG command to explain under which circumstances Debug Tool creates
a log file, and the initial setting for the SET LOG command;
see "SET LOG command".
In the Debug Tool User’s Guide, the following changes were made:
- A method for establishing a naming pattern
for preferences and commands files that Debug Tool can use to find and
read those files has been added.
Implementing this method requires
EQAOPTS commands. If you are not familiar with EQAOPTS commands, see "EQAOPTS commands" in the Debug Tool Reference and Messages or Debug Tool Customization Guide. The following EQAOPTS commands
were added and descriptions are located in both the Debug Tool Reference and Messages and Debug Tool Customization Guide:
- "COMMANDSDSN"
- "PREFERENCESDSN"
A new key word, NULLFILE, was added to the commands_file
and preferences_file sections of the TEST runtime options string so
you can suppress any system wide settings for the naming patterns.
The new key word is described in "Syntax of the TEST run-time
option".
In the Debug Tool User’s Guide, the following
changes were made:
- New functions have been added to Debug Tool
Utilities to help you more easily start debugging IMS™ applications running in BTS. In the Debug Tool User’s Guide, the topic Debug Tool Utilities has
been updated to provide an overview of option 9, IMS BTS Debugging. In the Debug Tool Customization Guide,
the topic "Customizing IMS BTS Debugging" has been
added.
- A new CICS transaction,
called DTNP, has been added that can run the NEWCOPY batch command
to reload application programs into an active CICS region. This transaction is described in the
topic Appendix H. Running NEWCOPY on programs by using DTNP transaction.
- You can now debug Java native methods and the Language Environment programs they
call. To learn how to do this, see Debugging programs called by Java native
methods in
the Debug Tool User’s Guide.
- In the Debug Tool Customization Guide, all information about customizations
required for remote debug mode have been consolidated into one topic called "Adding
support for remote debug users".
Most of the information
in topic "Customizing your z/OS system
to give the API access to DTCN profiles" of the Debug Tool API User's Guide and Reference has
been moved into this new topic and renamed to "Adding support for
the DTCN Profiles view and APIs".
- In the Debug Tool User’s Guide, some information that was previously
in the appendix "Notes® on
debugging in remote debug mode" has been moved to the online help
for the compiled language debugger component of Rational Developer for System z and the IBM Debug Tool plug-in for Eclipse. Information that was previously
in the appendix "Running a sample plug-in that uses the API" of
the Debug Tool API User's Guide and Reference has been moved to the topic Appendix I. Installing the IBM Debug Tool DTCN and DTSP Profile Manager plug-in.
- Reference cards that were previously in the Debug Tool Reference and Messages have been moved to Debug Tool Reference Summary. A new reference
card specifically for assembler users has been added.