Determining concurrent manager utilization

You can use the Concurrent Manager Utilization report to determine the percentage of processing time for the concurrent managers. The report can indicate one of the following situations:

• The utilization of a specific concurrent manager is low.
• The utilization report shows that a specific concurrent manager uses a low percentage of the processing time. You might want to adjust the work shift or the number of target processes in a concurrent manager to run on a limited basis, or even deactivate the concurrent manager.
• The utilization of a specific concurrent manager is high.
• The utilization report shows that a specific concurrent manager uses a high percentage of the processing time. If in addition, concurrent requests are pending too long, the concurrent manager can be bottlenecked.

The Concurrent Manager Utilization report displays the percentage of time that all concurrent managers spent processing assigned concurrent requests during the specified date interval. The report includes all defined concurrent managers and sorts the information in descending order of the utilization.
In addition, you can review the Concurrent Manager Utilization report for a single concurrent manager. The report displays the percentage of time this specific concurrent manager spent processing concurrent requests during the specified date interval.

For the Concurrent Manager Utilization report there is also a parameter with which you can review the percentage of time a single concurrent manager. The ConMgrUtilization graph, located within the concurrent_manager_name (OA_MGR) application, shows percentage of time this concurrent manager spent processing requests since the last performance statistics polling. The data displays a graphical time line which allows you to observe peak running times.

Click the task you are interested in:

• • To determine utilization of all concurrent managers
  • To determine utilization of specific concurrent managers
  • Related topics

To determine utilization of all concurrent managers

1. Follow the applicationID (OA_SYSTEM) > CONC_MGR (OA_CONM) pathway.
2. From the CONC_MGR (OA_CONM) menu, select the Performance Analysis > Concurrent Manager Utilization command.
   The Enter Start Date and End Date dialog box appears.
3. Type the beginning and end dates for the report interval. You can delete and override the default date interval.
   The date must be in the DD-MON-YYYY format, with MON in uppercase format (JAN for January, FEB for February, etc.).
4. Click Accept.
   The interval for the concurrent manager utilization is now set.

To determine utilization of specific concurrent managers

1. Follow the applicationID (OA_SYSTEM) > CONC_MGR (OA_CONM) > CONMGR_nodeName (OA_CONM_HOST) > concurrent_manager_name (OA_MGR) pathway.
2. From the concurrent_manager_name (OA_MGR) menu, select the Concurrent Manager Utilization command.
   The Enter Start Date and End Date dialog box appears.
3. Type the beginning and end dates for the report interval. You can delete and override the default date interval.
   The date must be in the DD-MON-YYYY format, with MON in uppercase format (JAN for January, FEB for February, etc.).
4. Click Accept.
   The interval for the concurrent manager utilization of the selected concurrent manager is now set. You can view the results by double-clicking the Concurrent Manager Utilization report.
   In addition, you can view the graph of the ConMgrUtilization parameter, showing shows the percentage of time the selected concurrent manager spent processing requests. This parameter is located within the concurrent_manager_name (OA_MGR) application.

Related topics

Identifying-bottlenecks
Resolving-bottlenecks
Identifying-the-number-of-active-target-processes
Identifying running and pending requests 
Determining-concurrent-request-history