Scenario

Imagine that when testing your modernized application, you decide you want to change how the server program drives your user interface. Suddenly, you discover that the program does not work the way you want.

You need to know what is happening in your program, but you do not know how to find this information. Debugging might be the magic word for a programmer, but you do not know how to tell the debugger that you want to examine the server program in a server job started by the WebFacing environment. This is difficult because the program is not interactive, and you cannot start it from the debugger or from a command line. The job where the program runs is created on the fly, as a server job on your iSeries host. You need a way to point the debugger to the program in a certain job.

In this exercise, you use the debugger to examine the server program, but you will also start to understand how you can use this debugger for your other interactive and batch programs as well. If you have already used the built-in integrated iSeries debugger, this should be very familiar for you. However, the instructions on how to locate the job where your WebFaced application runs will be new.