Using IBM Application Development Tools for z/OS and OS/390

334 Using IBM Application Development Tools for z/OS and OS/390

15.4 A debug session with the remote debugger

To show off the remote debugger, we will finish up debugging this problem with the IBM

Distributed Debugger. The first step is to start the distributed debugger listening using the

command:

C:\IBMDebug\bin\idebug.exe -qdaemon -quiport=8000

Our new intermediate PL/I program is called KNIGHTM and we invoke the remote debugger

to debug it using the following command as shown in Figure 15-12.

Figure 15-12 Invoking the remote debugger for our program with the interim fix

Chapter 15. Debug Tool and debugging PL/I 335

At this point the remote debugger is displayed as shown in Figure 15-13.

Figure 15-13 Remote debugger with PL/I source on entry

336 Using IBM Application Development Tools for z/OS and OS/390

The next recommended step is to place a breakpoint at the beginning of the actual program.

The remote debugger can sometimes jump directly to completion if you attempt to step at this

point without having a breakpoint, as shown in Figure 15-14.

Figure 15-14 After setting the breakpoint for before the call to initialize_Rankings

Chapter 15. Debug Tool and debugging PL/I 337

Figure 15-15 shows the local variables as when the breakpoint is triggered:

Figure 15-15 Local Variable display at our initial breakpoint

338 Using IBM Application Development Tools for z/OS and OS/390

Now the land array is the array that will hold the results (the final path across the chess

board), and we would like to monitor the changes in the land array. So we go to the

Breakpoints menu and select the Set Storage Change... Entry as shown in Figure 15-16.

Figure 15-16 Setting a storage change breakpoint