View the status of your concurrent managers (including any transaction managers) and, if you wish, change the status of any manager by issuing a control command. For example, you can deactivate a manager that is currently active, then view its new status after the change takes effect.
Use the Refresh button to refresh the data shown.
In a parallel concurrent processing environment, a manager's processes are targeted to run on this node.
If a concurrent manager is defined to use a platform-specific system queue, this field displays the name of the queue to which the manager submits its processes.
Each manager process can run one concurrent request (start one concurrent program). Typically, the number of actual processes equals the number of target processes (the maximum number of requests a manager can run).
However, the number of actual processes may be less than the number of target processes due to manager deactivation or manager migration.
This field displays the maximum number of manager processes that can be active for this manager.
Typically, when there are requests pending, this number should be the same as the number of actual processes. However, if there are no pending requests, or requests were just submitted, the number of requests running may be less than the number of actual processes.
Moreover, if a concurrent program is incompatible with another program currently running, it does not start until the incompatible program has completed. In this case, the number of requests running may be less than number of actual processes even when there are requests pending.
This field displays the status of a manager after you have chosen a specific action for it using the top row of buttons near the bottom of the window.
You can control concurrent managers individually or collectively by controlling the Internal Concurrent Manager. This field is blank when managers have been activated by the Internal Concurrent Manager.
In a parallel processing environment, this field displays Target node/queue unavailable when the primary and secondary nodes (or system queues) are not available.
| Terminate | When you terminate requests and deactivate the Internal Concurrent Manager, all running requests (running concurrent programs) are terminated, and all managers are deactivated. Managers previously deactivated on an individual basis are not affected. You can terminate requests and deactivate individual managers. All running requests (running concurrent programs) handled by the manager are terminated. Once deactivated, a manager does not restart until you select the manager and choose the Activate button. |
| Deactivate | When you deactivate the Internal Concurrent Manager, all other managers are deactivated as well. Managers previously deactivated on an individual basis are not affected. You can deactivate individual managers. Once deactivated, a manager does not restart until you select the manager and choose the Activate button. When you deactivate a manager, including the Internal Concurrent Manager, all requests (concurrent programs) currently running are allowed to complete before the manager(s) shut down. |
| Verify | This choice appears only when you select the Internal Concurrent Manager. The Internal Concurrent Manager periodically monitors the processes of each concurrent manager. You can force this process monitoring or PMON activity to occur by choosing the Verify button. Another result of selecting this choice is that the Internal Concurrent Manager rereads concurrent program incompatibility rules. |
| Restart | This choice appears only when you select an individual manager. When you restart a concurrent manager, the manager rereads its definition. You should restart a manager when you have made the following changes using the Define Concurrent Manager form, and you wish those changes to take effect:
|
| Fixed | This choice appears only when a manager has been down due to an underlying issue beyond the concurrent manager startup threshold and the Internal Concurrent Manager has stopped attempting to restart it. After the underlying problem has been fixed, this choice is available so that you can indicate that it has been fixed and the ICM should try to restart the concurrent manager again. |
| Activate | When you activate the Internal Concurrent Manager, you activate all other managers as well, except those managers that were deactivated on an individual basis. You cannot activate the Internal Concurrent Manager from the PC client. The Internal Concurrent Manager is only activated from the server. You can also activate an individual concurrent manager that is currently deactivated, so long as the Internal manager is active. If the manager is defined to work in the current work shift, then the Internal manager starts it immediately. |
| Processes | You can view the details of the processes of a given concurrent manager. Processes that are currently active, migrating, or terminating, as well as processes that have been terminated or deactivated, are displayed. |
| Requests | For a selected manager you can view all running and pending requests handled by the manager. |
The following actions are available only for certain services managed Generic Service Management. These services must be defined to accept commands to suspend their operations.
| Suspend | Suspend the operations of the service. |
| Resume | Resume the operations of the service. |