Historically, MCP system resources have been allocated among running programs by means of a priority–based process scheduler. Each process is assigned a priority, and available processors are allocated to the highest priority processes waiting for processors. Determining a suitable set of process priorities and system parameter settings for a given workload is often a matter of trial and refinement. An adjustment is made to one or more parameters, the effect is observed, and further adjustments are made. But increasingly, organizations don’t have the manpower to constantly retune their systems.
In addition, process priority and other system balancing parameters are not an end in themselves, but rather a means to an end. The desired outcome can and should be expressed in more business–oriented terms. For example, transactions for a certain application should exhibit an average response time of 1.5 seconds or a batch job should be completed by a certain time. Once the desired outcomes have been determined, the system should manage resource allocation to ensure the specified goals are achieved. That’s what Workload Management for ClearPath MCP adds to your system. For brevity throughout this paper, "Workload Manager" is synonymous with "Workload Management for ClearPath MCP."