Previous topic |
Next topic |
Contents |
Index |
Contact z/OS |
Library |
PDF
![]() Using the Routing Manager Services z/OS MVS Programming: Workload Management Services SC34-2663-00 |
|
Using the Routing Manager ServicesA routing manager is a subsystem that establishes and manages connections between a client and a server address space. The routing manager handles these connections rather than individual work requests; the requests are processed only after they arrive in the server address space. The routing manager is responsible for balancing the client connections across a set of eligible servers, with the assistance of the routing manager services. Routing manager services perform two main functions:
Routing manager services differ from sysplex routing services in the following ways:
This chapter presents a model of how the routing manager services are intended to be used. Routing manager services combines the use of the “find server” function with application environments and enclaves. See Updating a Service Definition with Application Environment Information for a discussion of defining policy for application environments. Note:
When defining an application environment,
you must specify whether workload management can start multiple or single address
spaces for the subsystem. In the case of a routing manager, both Option 1, Managed
by WLM, and Option 3, Limited to a single address space per sysplex
are valid. For
more information, see the “Defining Application Environments”
chapter in z/OS MVS Planning: Workload Management. It is strongly recommended that server address spaces associated with a routing manager use enclave services to manage the work requests according to goals set by the customer. Be aware that enclaves are mutually exclusive with the execution delay monitoring services described in earlier chapters. For a discussion of enclaves and a comparison to delay monitoring, see Creating and Using Enclaves. ![]() ![]() ![]() |
![]() |