The components of the iSeries™ System Debugger work together to provide a powerful debugging tool.
IBM® iSeries System Debugger consists of the following components:
The following descriptions provide only general information about the iSeries System Debugger components. To learn more about the components, run iSeries System Debugger, and from any iSeries System Debugger window, click Help. For more information about running iSeries System Debugger, see Running iSeries System Debugger.
Debug Manager registers the client with the Debug Hub, which enables using the graphical debugging mode for the selected systems. A registered client that issues the Start Debugging (STRDBG) CL command from an emulation session starts System Debugger.
Use Debug Manager to manage your debugging operations and connections:
Use System Debugger to debug programs written in ILE and OPM languages and Java™ that run on the iSeries server. You can debug programs that are running in existing jobs on the server or use System Debugger to open and then debug programs in a system batch job.
You can configure System Debugger to start automatically, manually from a workstation command prompt, or by using the Debug Manager interface.
Use System Debugger to perform debugging activities that include:
Use i5/OS PASE Debugger to debug programs that run in an i5/OS PASE environment. You can debug programs that are running in an existing process on the system or use i5/OS PASE Debugger to open and then debug a program.
You can start i5/OS PASE Debugger directly from the command line or by using the Debug Manager interface.
In addition to the debugging activites listed previously for System Debugger, you can use i5/OS PASE Debugger to perform i5/OS PASE-specific debugging activities that include:
Debug Hub provides the following functions:
Use the Debug Manager interface to register your client with Debug Hub. Registering a client stores both the user information and the TCP/IP address of the client in the registry. Using the Start Debugging (STRDBG) CL command from an emulation session contacts Debug Hub to see if the user executing the command is registered with Debug Manager. It also checks to see if the command being executed is from the same TCP/IP addess as Debug Manager. If these qualifications are met, iSeries System Debugger (the graphical application) is started instead of the traditional debug environment.
Debug Hub also serves as a single point of contact for all iSeries System Debugging applications. When an iSeries System Debugger component performs a start debug operation, Debug Hub submits a Debug Server job on behalf of the user and passes the associated TCP/IP connection to the job.