To debug on Enterprise Server

  1. Prepare for debugging, see To prepare for debugging on Enterprise Server.
  2. Click Project > myprojectProperties and go to the Debug tab.
  3. Click the tab for the type of service or application that you want to debug and enter its details, as follows:
    • For a Web Service, enter the IP address of the client that will make the service request. You can also enter the fully qualified name of the service. This is formed by taking the name of the service and appending a pound or hash character (#) followed by the name of the operation that you want to debug. For example, if the service name for the web service that you deployed is http://tempuri.org/wmapserv, and the operation to be debugged is Read, the fully qualified service name is http://tempuri.org/wmapserv#Read.
    • For CICS, you can enter the CICS terminal ID, the CICS transaction for the application and so on. For non-facility tasks (those not running on a terminal or printer) specify '....' for the value of the terminal ID.
    • For JCL, you can enter job name, job number, top-level program and so on.
  4. Click Debug > Start Debugging .
  5. Start the Web service or the application you want to debug on the enterprise server region. The way you do this depends on the type of application, for example:
    • For a Web Service, run the client program and enter some input to trigger the service. It is not possible to run the client module from within your debug session. However, if the client program is also part of a different project than the one that you are debugging, you can start another debug session, open the client project and run the client module.
    • For a CICS application, start a TN3270 terminal session and run your transaction.

      If you have Micro Focus Rumba installed, you can run the application in a mainframe session of Rumba Desktop, or in the Rumba Mainframe Display view within the IDE.

  6. Step through the application in the usual manner. When the debugger reaches the exit program statement and no line is highlighted, the service or the application exits. The debugger now waits for the next matching service or application to start.
  7. When you have finished debugging, click Debug > Stop Debugging . If specified in your Enterprise Server preferences, when closing the project it will stop and delete the enterprise server used to debug the application.
Parent topic: Debugging Mainframe Applications and Services on Enterprise Server