Rational Developer for System z, Version 7.6


Debug the DB2® application with generated JCL

This lesson describes how to debug the application using the JCL generated during the previous module.
The JCL that is generated from the Generate JCL > For Compile, Link, Go action creates a batch job to run the application. Because you selected the Run in batch with debugger radio button, the JCL is generated with an additional inline Assembler CSECT, which is linked into the application. This CSECT, called CEEUOPT, contains Language Environment® (LE) runtime options. These runtime options cause the program to be run in the debugger at each invocation.

To debug the application using the generated JCL, do these steps:

  1. Select Window > Open Perspective > Other.
  2. In the Open Perspective window, select Debug and then click OK.
  3. In the Debug view, check that the debug daemon is listening. If the Debug toolbar shows the icon
    Debug daemon not listening icon
    , then the daemon is not listening. Select Start listening on port from the drop-down menu to start the debug daemon.
  4. In the Remote Systems view, right-click the generated JCL file and select Submit from the pop-up menu. If you receive JCL errors, fix these errors and resubmit the JCL file. If there were no JCL errors, a debug session should begin.
  5. Set a breakpoint on the GOBACK statement and press F8 to run to that breakpoint.
  6. Look in the Variables view and expand the plus sign on FRIENDZRECORD. You should see the following:
    DB2 variables in Debug perspective
  7. Run the program to completion.

Terms of use | Feedback



This information center is powered by Eclipse technology. (http://www.eclipse.org)