The Debugging Process

Use the debugging process to determine where problems occur and then fix those problems. Isolate each problem to a particular area, and then examine exactly how the program operates in that area.

If you change your program while you are debugging with the JD Edwards EnterpriseOne Event Rules Debugger, you must:

Exit the application.
Rebuild debug information.
Reset breakpoints.
Rerun the application.

Features available in the event rule debugger are listed and described in this table:

Feature	Description
Go	Command that resumes program execution after a breakpoint is reached.
Breakpoint	Command that tell the debugger to stop when a particular line is reached. You can set breakpoints on lines of code where you want to start debugging.
Delete Breakpoint	Command that removes all breakpoints that you currently have set.
Step, Step Over	Command that executes the current line of code. Step lets you run the program one line at a time. You can use this feature to determine the results of every line of code as it is executed.
Step Into	Command used when the current line of code contains a function call. The debugger will step into the function so that it can be debugged line by line. When the function is complete, the debugger returns to the next line of code after the function call in the calling routine. Step Into can be used to debug a second application that is called from within an application.
Disconnect	Command that disconnects the debugger from the current application. The application continues to run as if the debugger had not been started.