Services for Multiple Address Space Work Managers

The structure of the subsystem work manager dictates which workload management services can be used. A multiple address space work manager normally consists of three kinds of address spaces: router, execution, and supporting. The router address space receives incoming work requests, and passes them off to execution address spaces, which might use the services of supporting address spaces. Figure 5 shows the sequence of functions in a multiple address space work manager.

Figure 5. Sequence of function in a multiple address space work manager.

There are several groups of services that are useful to a multiple address space work manager:

• Creating and Using Enclaves

  The enclave services let you manage transactions across multiple address spaces in the same service class as the original request. The customer can assign a response time, discretionary, or a velocity goal to work, and can define period switching.

• Using the Queueing Manager Services

  The queueing manager services make it possible for the system to dynamically start and stop server address spaces based on the workload, and manage the work queues associated with the server address spaces to meet service class goals. The customer can assign a response time, discretionary, or a velocity goal to work, and can define period switching.

• Execution Delay Monitoring Services for Multiple Address Space Work Managers.

  The execution delay monitoring services let you associate a service class with work, and the customer can assign a response time goal. You can also get response time and delay information about how well the work did to meet the goal. However, if you want to have the advantages of enclaves (such as having a single transaction that spans multiple address spaces and is managed to the goal of the originating address space), you should use enclave services rather than execution delay monitoring services.