Debug Manager provides communication-related
services to z/OS® Debugger and the remote Eclipse
IDE. It circumvents the need to open outbound ports from z/OS and for users to track their IP
address. For differences between usages with and without Debug Manager, see the figures in TCP/IP ports.
Figure 1 shows a schematic
overview of how an Eclipse client uses Debug Manager
when you debug an application.Figure 1. Debug
Manager
The client connects to the host by using a z/OS connection in the Remote Systems view.
As part of the logon, Debug Miner registers the user with Debug Manager, which is active within the DBGMGR started task.
When the program to be debugged starts, z/OS Debugger sends the debug request to Debug Manager.
Debug Manager checks whether the
debug session user is registered. If the user is not registered at this moment, the debug session
goes dormant. z/OS Debugger will wait
up to 300 seconds in standard mode, and up to two times of $VALUE in
Debug Tool compatibility mode. If the user still has not signed on to the z/OS connection in the
Remote Systems view and is not registered with Debug Manager, the debug session will time out.
If the user is registered, Debug Manager notifies the Eclipse client that a new debug session is available.
The Eclipse client makes a TCPIP connection to the external Debug Manager port.
Debug Manager passes the TCPIP
connection to z/OS Debugger, which allows the user
to control the debug session.
For more information about TCPIP/DIRECT and DBM/DBMDT options and the
user_id option for DBM/DBMDT, see Syntax of
the TEST runtime option.
