Identifying running and pending requests
A group of parameters help to identify requests that are running or pending. You can encounter concurrent managers with excessive waiting times. In addition to identifying peak waiting time periods during the work shift, you migth want to identify the specific running or pending requests that cause the excessive waiting times.
Click the task you are interested in:
To identify running and pending requests on all concurrent managers
Four parameters in the CONC_REQUEST (OA_REQUEST) application enable you to identify running and pending requests within all concurrent managers:
Parameter | Type | Description |
---|---|---|
NumRunningPendingReq | Graph | Displays the total number of running or pending requests in Normal status. |
ListRunningPendingReq | Report (text) | Shows a list of the running and pending requests in Normal status. Requests are listed for each concurrent manager along with the user application ID and the number of running and pending requests. |
NumRunningPendingPausedReq | Graph | Displays the total number of running or pending requests in Paused, Waiting or No Manager status. |
ListRunningPendingPausedReq | Report (text) | Shows a list of the running and pending requests in Paused, Waiting or No Manager status. Requests are listed for each concurrent manager along with the user application ID and the number of running and pending requests. |
To identify running requests on specific concurrent managers
Two parameters in the concurrent_manager_name (OA_MGR) application enable you to identify running requests on specific concurrent managers:
Parameter | Type | Description |
---|---|---|
NumMgrRunPendReq | Graph | Displays the total number of running requests on a specific concurrent manager, and the pending requests that entered a pending status after they started to run on this concurrent manager. |
ListMgrRunPendReq | Report (text) | Shows a list of running requests on a specific concurrent manager, and the list of the pending requests that entered a pending status after they started to run on this concurrent manager. The generated report will list of all the running requests within the selected concurrent manager, including the user application ID and the number of running requests. |
Related topics
Managing-bottlenecks
Monitoring-long-running-and-long-pending-requests
Identifying-long-running-and-long-pending-requests
Alleviating-long-running-and-long-pending-requests
Setting-thresholds-for-concurrent-requests
Determining-concurrent-request-history