What's removed from IBM z/OS Debugger

Deprecation announcement

The following features are superseded by newer features and will be removed in a future release.

16.0.0

  • Standard mode is no longer supported. Debug Tool compatibility mode is now the only remote debug mode and is referred to as remote debug mode directly. If you use DIRECT or DBM in the TEST runtime option, Debug Tool compatibility mode is invoked instead.
  • Debug Tool plug-ins are removed. If you migrate from previous releases, any Debug Tool plug-in views are automatically closed in workspaces.
    The same functions are available with other features.
    • You can use the z/OS Debugger Profiles view in the Eclipse IDE or the z/OS Debugger Profiles view provided with Z Open Debug to create and manage debug profiles. If you are a system programmer, you can use z/OS Debugger Profile Management to manage CICS (DTCN) profiles from all users.
    • You can use the z/OS Batch Application with existing JCL launch configuration to dynamically instrument and submit JCL to the host.
    • You can use the Code Coverage Results view to work with code coverage results.
  • Load Module Analyzer is no longer bundled with z/OS Debugger.
  • Generating code coverage for Java applications is no longer supported. You can import Java results that are generated by open source packages, in particular JaCoCo, into the Code Coverage Results view.
  • Jython Debugger is no longer supported.
  • Team debug is no longer supported.
  • IMS message region templates (IBM® z/OS Debugger Utilities options 4.3 Swap IMS Transaction Class and Run Transaction and option 4.4 Manage IMS Message Region Templates) are removed. Use options 4.5 IMS Transaction Isolation and option 4.6 Administer IMS Transaction Isolation Environment instead.
  • TEST runtime suboption VADTCPIP& is no longer supported. Use TCPIP& instead.