You can identify all unresponsive tasks that originated from a specific TCP/IP service. For example, your system might be configured such that all transactions from your WebSphere® Application Server come in on a specific TCP/IP service. Using transaction tracking you can identify all unresponsive tasks from the one source.
This procedure describes how to identify all the tasks that originate from a specific TCP/IP service.
The results are displayed in the Search view. The view shows all the currently active tasks that originated from the TCP/IP service.
You can run the search again by clicking
the Search again icon , or by clicking F5.