To debug on enterprise server
-
Prepare for debugging.
-
Click
Project >
myprojectProperties and go to the
Debug tab.
-
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.
-
Click
Debug > Start Debugging
.
-
Start the service or application on your enterprise server. How you do this depends on what type of application it is. For example:
- For a Web Service, you can run the client program and enter some input. You cannot run the client module from within your debug session. However, if the client program is part of a different project to the one that you are using for debugging, you can start another session, open the client project and run the client module.
- For a CICS application, you can start a TN3270 terminal session and run your transaction.
-
Step through the deployed programs in the usual manner.
When debugging reaches the
exit program statement and no line is highlighted, the service or application has exited. The debugger now waits for the next matching service or application to start.
-
When you have finished debugging, click
Debug > Stop Debugging
.
