Workload management allocates resources to meet goals of the work
that arrives. System programmers must use the existing methods of
routing and scheduling work for subsystems except for those listed.
For subsystems not exploiting workload balancing or routing services,
if you want to balance your work across all MVS™ images in a sysplex, the system programmer
must set the routing controls to either balance the arrival of work,
or to ensure that all MVS images
are equal candidates for processing work.
Examples of subsystems that can automatically balance work in a
sysplex include:
- CPSM provides
goal-oriented routing based on the goal defined for CICS® work in the workload management service
policy.
- DB2 V 4.1 provides
automatic and dynamic work balancing in a sysplex for distributed
data facility (DDF) work.
- DB2® V 5 provides additional
automatic work balancing through its sysplex query parallelism function.
- SOMobjects® uses application
environments to help balance object class binding requests in a sysplex.
- CICS V 4.1, DB2 V 4.1, TSO/E V 2.5, and APPC cooperate with VTAM® 4.4 and workload management in a sysplex
to manage session placement. New sessions for these subsystems are
directed to the appropriate systems in the sysplex to balance work
and meet performance goals.
- JES2 and JES3 provides automatic and dynamic placement of initiators
for WLM-managed job classes. z/OS® 1.4
together with JES2 1.4, and z/OS 1.5
together with JES3 1.5 provide Initiator Balancing, so that already
available WLM managed initiators can be reduced on fully loaded systems
and increased on low loaded systems to improve overall batch work
performance and throughput over the sysplex.
- WebSphere® Application
Server cooperates with WLM in a sysplex to balance work among application
control regions and to meet performance goals.