15.0.4 is now available for IBM z/OS Debugger! In addition to many fixes (18 APARs between host and client), this release has some key new features:

IBM Open Enterprise SDK for Go

z/OS Debugger continues its commitment to IBM Open Enterprise SDK for Go, now supporting version 1.17.  See my previous blog Debugging a Go program with z/OS Debugger for details on debugging Go.

Improved Decimal point support for COBOL

When debugging in Eclipse IDEs using Debug Tool compatibility mode, if the DECIMAL-POINT IS COMMA clause is specified in a COBOL program compiled with Enterprise COBOL for z/OS Version 6 Release 3 (UI78163) or later, in the Variables and Monitors views, the debugger will display decimals as commas.  Expressions can also be specified with commas, in addition to periods, as decimal points.

Host configuration

There are several updates to the z/OS Debugger configuration you can now enable:

• Configure the eqahcc.env file to start Code Coverage Service as part of Remote Debug Service. For more information, see Customizing with the sample job EQARMTSU.
• For Debug Manager, leverage Dynamic Virtual IP Addressing (DVIPA) available in IBM Explorer for z/OS to concurrently run identical setups on different systems in your sysplex, and have TCP/IP, optionally with the help of WLM, distribute the client connections among these systems. Ensure that each Debug Manager has a unique external port per system and the port is explicitly defined in TCP/IP definitions. For more information, see Distributed Dynamic VIPA.
• And for IMS users, the MVS data set userid.EQATIOUT is no longer needed when you install and configure the IMS transaction isolation extension for usage with the Eclipse IDE.

Code coverage

Multiple code coverage results can be merged and exported on z/OS from command line into a single file of various formats with the new ccexport.sh command.

This can help you get a better idea of your overall code coverage as part of a build pipeline or multiple test runs. For more information, see Merging and exporting code coverage results from z/OS.
When started via the headless code coverage collector, Code Coverage Service now supports secured connections, and when running on z/OS requires authentication. Secured connections can now be added in the Code Coverage Results view, and users will be prompted when the certificate to secure CCS is untrusted. A new preference page is added to manage certificates.

For more information, see Working with result locations.

Hope y'all enjoy the latest z/OS Debugger!