What's new in IBM z/OS Debugger
16.0.5
- New support
-
- Support is added for CICS Transaction Server for z/OS 6.2.
- Debug Profile Service
-
- The configuration section was refactored to provide better experience. For more information, see Adding support for Debug Profile Service.
- The default number of requests per second to allow or deny into the Debug Profile Service
(
requestsPerSec
) is increased from 20 to 1000. For more information, see Customizing the eqaprof.env file. - A new optional property
corAllowedOrigins
is added to define the allowed origins for Cross-Origin Resource Sharing (CORS). For more information, see Establishing security for Cross-Origin Resource Sharing (CORS) and Customizing the eqaprof.env file.
16.0.4
- New support
-
- Support is added for IBM Open Enterprise SDK for Go 1.22.
- LangX COBOL now includes programs compiled with Enterprise COBOL for z/OS® 6.
- Debug Profile Service
-
- Debug Profile Service can now be used with Java 17, but IBM z/OS Liberty Embedded 23.0.0.12 or later is required.
- Debug Manager
-
- You can now configure Debug Manager by using environment variables. For more information, see Running Debug Manager as a started task by using environment variables.
- You can now set the TRUSTEDTCP parameter to
ON
so that Debug Manager supports authentication of other Debug Manager instances connecting to its hub port using trusted TCP. For more information, see Trusted TCP authentication for sysplex connections. - An example is added to show an overview of how an Eclipse client connects and communicates to the system in a DVIPA environment with multiple LPARs. For more information, see Distributed Dynamic VIPA: Communication example.
16.0.3
- New support
-
- Support is added for z/OS 3.1.
- Support is added for IMS 15.4.
- Support is added for CICS Transaction Server for z/OS 6.2 (open beta).
- Support is added for IBM Open Enterprise SDK for Go 1.21.
- Code Coverage
-
- In the code coverage report, you can switch to the tree view for a graphical representation of the hierarchy of files, modules, and flow points. In this tree view, you can click the name beside any node to open the source in the editor. For more information, see Viewing coverage information in the tree view.
- You can now optimize collection to include only the modules being tested by ZUnit with the
z,zunit
parameters. For more information, see Starting and stopping the headless code coverage collector and Specifying code coverage options in the startup key.
- Eclipse debugger
-
- When you debug CICS applications, you can now specify
QUIT DEBUG
orQUIT DEBUG TASK
in the z/OS Debugger Preferences page. For more information, see Setting debug preferences. - During playback, the Variables view now displays values collected during recording. Variables cannot be updated during replay. For more information, see Using the Playback toolbar.
- When you debug CICS applications, you can now specify
- IMS Transaction Isolation
-
- You can perform any operation from a single connection and IMS Transaction Isolation facility will notify other LPARs of the configuration changes. For more information, see Using IMS Transaction Isolation to create a private message-processing region and select transactions to debug and Scenario F: Enabling the Transaction Isolation Facility.
- The EQAZDFLT settings are now used when you start the IMS Transaction Isolation Facility with the batch interface, Debug Profile Service and ADFz Common Components server, as they already are with the z/OS Debugger Utilities. For more information, see Scenario F: Enabling the Transaction Isolation Facility.
- EQAN0DBG
-
- EQAN0DBG is now available as an alias of EQANMDBG. It passes the unmodified input parameter list to the application and collects all debugger parameters from EQANMDBG DD. For more information, see Starting z/OS Debugger for programs that start outside of Language Environment and Passing parameters to EQANMDBG or EQAN0DBG using only the EQANMDBG DD statement.
- EQAOPTS command
-
- Command
LDDAUTOLANGX
can now be specified to control whether LDD is automatically run on LangX COBOL compile units. For more information, see LDDAUTOLANGX.
- Command
- Remote Debug Service
-
- Remote Debug Service can now be secured with AT-TLS. For more information, see Customizing with the sample job EQARMTSU and Enabling secure communication with AT-TLS.
- Debug Profile Service
-
- Debug Profile Service now runs on IBM z/OS Liberty Embedded instead of Apache Tomcat on z/OS. Refresh the eqaprof.env with the latest sample file to include environment variable liberty_dir. For more information, see Customizing with the sample job EQAPRFSU.
- In addition to JCERACFKS, you can now also use a JCECCARACFKS keyring managed by RACF for secure communication. For more information, see Enabling secure communication with a RACF managed key ring.
- You can now configure the number of requests per second to allow or deny into the Debug Profile Service. For more information, see Customizing with the sample job EQAPRFSU.
- Documentation updates
-
- A new page is added to list the requisites to use debug functions. For more information, see Requisite products.
- Details of environment variables in eqaprof.env for Debug Profile Service and eqarmtd.env for Remote Debug Service are now documented. For more information, see Customizing with the sample job EQAPRFSU (Debug Profile Service) and Customizing with the sample job EQARMTSU (Remote Debug Service).
16.0.2
- Compiler support
-
- Support is added for IBM Open Enterprise SDK for Go 1.20.
- Interoperability is now supported between 64-bit Java and 31-bit PL/I programs if you use 64-bit PL/I programs in between. Use delay debug mode to improve efficiency. For more information about delay debug, see Using delay debug mode to delay starting of a debug session.
- Debug Profile Service
- In addition to an SSL or a CA certificate, you can now enable Debug Profile Service to communicate with AT-TLS. For more information, see Enabling secure communication with AT-TLS.
16.0.1
- Installation Manager
-
- You can now install the Eclipse IDE via Installation Manager again:
- For IBM® Developer for z/OS, you can install the Eclipse IDE via Installation Manager as in Version 15.0 and before. For more information, see Installing the IBM Developer for z/OS client by using IBM Installation Manager.
- For IBM Debug for z/OS, you can now install the Eclipse IDE via Installation Manager as an extension offering to the IBM Explorer for z/OS offering, and you no longer need to install via IBM Developer for z/OS. For more information, see Installing the IBM Debug for z/OS Eclipse IDE with IBM Installation Manager.
- You can now install the Eclipse IDE via Installation Manager again:
- Compiler support
-
- Support is added for IBM Open Enterprise SDK for Go 1.19.
- Support is added for 31-bit PL/I applications compiled with
TEST(SOURCE)
.The following APARs are required for this support:- z/OS Language Environment® APAR PH49423
- Enterprise PL/I for z/OS 6.1 APAR PH50085
- Code Coverage
-
- The multiple import menu actions and buttons in the Code Coverage Results
view are now consolidated into a single menu action and button to import code coverage results. With
the new Code Coverage Import wizard, you can select the following result
formats to import into any result location in the Code Coverage Results view:
- CCZIP: Import coverage results with a file extension of .cczip, which are produced by headless code coverage collection or via the Eclipse UI. Older formats ending with .clcoveragedata, .ccresult, or .zip are also supported with this option.
- JaCoCo: Import coverage results data execution files with a file extension of .exec, which are produced by JaCoCo.
- z/OS Debugger: Import coverage information that is stored in a sequential data set, which is
produced in z/OS Debugger using
CC
orDCC
in theTEST
runtime option via MFI. - Java Code Coverage: Import legacy Java code coverage results with a file extension of .coveragedata. This option is available only in IBM Developer for z/OS and IBM Developer for z/OS Enterprise Edition.
.cczip
format during import. - With Code Coverage Service, you can now download exporter formats PDF, SonarQube, and Cobertura, in addition to CCZIP. For more information, see Code Coverage Service API Documentation.
- The summary section in the code coverage reports now provides more useful statistics and improved usability.
- You can now customize the colors that are used to indicate the threshold statuses (failure, warning, passed) for code coverage results in the code coverage reports.
- The multiple import menu actions and buttons in the Code Coverage Results
view are now consolidated into a single menu action and button to import code coverage results. With
the new Code Coverage Import wizard, you can select the following result
formats to import into any result location in the Code Coverage Results view:
- z/OS Debugger Profiles view
-
- In the Debug Profile Editor, the CICS user ID field is now pre-populated with the reserved keyword &USERID, which is substituted with the currently logged-in user ID upon profile activation.
- On the IBM z/OS Debugger Preferences page, you can now choose whether to automatically synchronize debug profiles in the view with those in the remote system when you establish an RSE connection. For more information, see Setting debug preferences.
- Debug Manager
-
- Debug Manager can now establish communication between the client and the debugger when the LPAR the client is connect to and the LPAR that the debug session is started are different. The sysplex support requires Eclipse IDE 16.0.1 or later. For more information, see Enabling sysplex support.
- You can now use a configuration file to start Debug Manager. With a configuration file, you can start Debug Manager even when the length of command line with all necessary options exceeds 100 characters limit, for example, in the sysplex environment. For more information, see Running Debug Manager as a started task using a configuration file.
16.0.0
- Compiler support
-
- Support is added for IBM Open XL C/C++ for z/OS 1.1. z/OS Language Environment APAR PH46617 is required for this support.
- Support is added for IBM Open Enterprise SDK for Go 1.18.
- Interoperability is now supported between 31-bit and 64-bit PL/I programs. Use delay debug mode
to improve efficiency. For more information about delay debug, see Using delay debug mode to
delay starting of a debug session.The following APARs are required for this support:
- z/OS Language Environment APARs PH48829 and PH48239
- Enterprise PL/I for z/OS 6.1 APAR PH49506
- 64-bit support
-
- With the removal of standard mode, 64-bit PL/I programs are now supported in Debug Tool compatibility mode with some limitations. For the limitations, see Limitations of 64-bit support in remote debug mode.The following APARs are required for this support:
- z/OS Language Environment APARs PH48829 and PH48239
- Enterprise PL/I for z/OS 6.1 APAR PH49506
- Enterprise PL/I for z/OS 5.3 APAR PH49425
- With the removal of standard mode, 64-bit PL/I programs are now supported in Debug Tool compatibility mode with some limitations. For the limitations, see Limitations of 64-bit support in remote debug mode.
- Code Coverage
-
- New web-based code coverage reports and comparison reports are available. You can now view the compared source files line by line. For more information, see Working with a code coverage report and Working with a code coverage comparison report.
- Java code coverage is now strategically based on open source packages, in particular JaCoCo. You can import JaCoCo results into the Code Coverage Results view and work with the imported results. You can still import results previously generated with IBM Java code coverage tools into the view. The Java code coverage results already in the workspace will be migrated automatically. For more information, see Working with Java code coverage results.
- You can now specify a warning threshold, in addition to failure threshold for code coverage result status. For more information, see Setting the code coverage acceptance level.
- When you export code coverage results in SonarQube format, you can now specify a different encoding than the default UTF-8. For more information, see Exporting code coverage results in SonarQube format, Starting and stopping the headless code coverage collector, Specifying code coverage options in the startup key, and Merging and exporting code coverage results from z/OS.
- Source level debug
-
- If you debug programs compiled with Enterprise COBOL for z/OS
Version 6 Release 2 and later, you can now specify compiler option
TEST(NOSOURCE)
to use the Source view as the default in the Eclipse IDE, or you can switch to the Source view during the debug session if you compile withTEST(SOURCE)
. WithTEST(NOSOURCE)
, the compiler does not include the source of your program as part of your debug data whether the location of the debug data is in the load module or in the SYSDEBUG file. For more information, see Working with different debug views.
- If you debug programs compiled with Enterprise COBOL for z/OS
Version 6 Release 2 and later, you can now specify compiler option
- IMS Transaction Isolation
-
- You can now access IMS Transaction Isolation Facility with Debug Profile Service. ADFzCC configuration is no longer needed when Debug Profile Service is running on the selected RSE connection with z/OS Debugger 16.0.0 or later. The system programmer needs to configure the IMS Transaction Isolation API to enable this function. For more information, see Configuring the IMS Transaction Isolation API for Debug Profile Service.
- Pattern matching used to filter transactions for isolation can now be limited to a range within a transaction message. For more information, see Using IMS Transaction Isolation to create a private message-processing region and select transactions to debug.
- Debug Profile Service
-
- On the IBM z/OS Debugger Preferences page, you can specify to ignore the SSL certificate errors when the Debug Profile Service that you want to connect to does not have a valid SSL certificate. For more information, see Setting debug preferences.
- As a system programmer, you can now set up Debug Profile Service to use external CICS interface (EXCI) to manage debug profiles stored in the region’s repository instead of using the DTCN API. For more information, see Defining the CICS EXCI CONNECTION and SESSIONS resources.
- EQAOPTS command
-
- Command
CICSASMPGMND
can now be specified to control whether z/OS Debugger allows debugging assembler programs when the language attribute of the program resource is not defined. For more information, see CICSASMPGMND and Starting z/OS Debugger for non-Language Environment programs under CICS.
- Command