Debugging the IMS Application

Debugging requires that your project is associated with the IMSDEMO Enterprise Server and that the Enterprise Server is configured to enable dynamic debugging, which you performed in the previous steps.

Start Debugging

To start a debugging session and open your TN3270 emulator:

  1. In the Team Developer Tree view, select DEMO001T.cbl, and then selectDebug As > IMS on COBOL Enterprise Server on the main menu.

    This starts the Confirm Perspective Switch dialog - click Yes to switch to the Debug perspective. The debugger is now waiting for the application to start.

  2. In the Debug view, right-click the COBOL Debugger thread, and click Show Rumba Terminal.

    This opens the Rumba Mainframe Display view within the IDE and connects it to the enterprise server. If necessary, right-click in the toolbar of the view, and click Detached, on order to reposition or resize the window.


    If the Rumba Mainframe Display view does not connect automatically, you can connect to the server manually as follows:

    1. Click the New Rumba Mainframe Display button, New Rumba Mainframe Display, in the toolbar of the Rumba Mainframe Display view.
    2. Specify the host name, localhost, and the TN3270 port number, 5239, for the IMSDEMO server in the TN3270 Connection Properties dialog box.
    3. Click Connect.

      This connects the display to the IMSDEMO server and loads the start screen of the application.

Run the IMS Application and Debug It

Run the IMS application again as follows:

  1. Clear the screen of the Rumba Mainframe Display view, pressing CTRL+SHIFT+Z.
  2. Enter MFDEMO (with a trailing space).
  3. Press Enter.

    At this point, the IDE opens DEMO001T.CBL in a debug session and highlights the line of code that is part of the initialization.

  4. Continue debugging the application as required.

Stop Debugging

When you have finished debugging, end the debug session as follows:

  1. Click Run > Terminate.
  2. Close the IDE.

    You receive a notification that the IMS server is still running.

    Click Set default behavior to configure how Eclipse manages the enterprise servers, or click Yes to stop the server.