Adding support for remote debug users

Remote debug is a general term that covers multiple client scenarios. Each scenario has its own setup steps.

• Eclipse client using the TEST(,,,DBMDT) parameter to start a debug session. Here the program-under-test and the Eclipse client communicate with each using the Debug Manager, avoiding the need for outgoing TCP/IP connections from z/OS. Debug Manager is the recommended way to start a remote debug session.
• Eclipse clients using the TEST(,,,TCPIP) parameter to start a debug session. Here the program-under-test on the z/OS host connects to a server running in the Eclipse client.
• Other clients, such as Visual Studio Code (VS Code), utilizing the Remote Debug Service.
• Other products, such as IBM Test Accelerator for Z, using an Eclipse client to drive services offered by z/OS® Debugger.

Note: EQAOPTS commands are commands that alter some of the basic behavior of z/OS Debugger. They can be specified dynamically by the user or in a customized version of the EQAOPTS load module. For more information, see EQAOPTS commands.

If you have users running z/OS Debugger in remote debug mode, review the following list and complete the applicable tasks:

• Create an OMVS segment for each user ID that uses the remote debugger.
• If your TCP/IP stack name is not TCPIP, you can use the TCPIPDATADSN EQAOPTS command to instruct z/OS Debugger to dynamically allocate the correct SYSTCPD DD.
• If the source or compiler uses a code page other than 037, see the CODEPAGE EQAOPTS command.
• If you want z/OS Debugger to switch to full-screen mode or batch mode if the remote debugger is not available, see the NODISPLAY EQAOPTS command.
• For your CICS users, see Activating the TCP/IP Socket Interface for CICS.
• Eclipse clients communicate with the host using the RSED started task of z/OS Explorer, FMID HALGxxx. z/OS Debugger must make itself known to RSED for its services to become available. For more information, see RSED integration.
• With Debug Manager, remote Eclipse users do not need to open an outgoing port for the debug daemon on the z/OS system, or supply an IP address and port for debugging. For the differences between using Debug Manager and Debug Daemon port 8001, see TCP/IP ports. For more information, see Enabling communication with Debug Manager and Understanding Debug Manager.
• To enable interactive debugging in IBM Z® Open Debug, see Adding support for Remote Debug Service.
• If your users create and manage debug profiles in the z/OS Debugger Profiles view, see Adding support for Debug Profile Service. For your CICS users, you can set up Debug Profile Service to use external CICS interface (EXCI) or add support for the DTCN profiles API.
• To enable secure communication for incoming debug and code coverage sessions in the remote Eclipse IDE, see Enabling secure communication between z/OS Debugger and the remote debugger for incoming debug sessions.
• To enable authentication for incoming debug sessions in the remote Eclipse IDE, see Enabling authentication for incoming TCP/IP connections.

• Related references
• Remote debug mode in the IBM® z/OS Debugger User's Guide