What is workload management?

The workload management (WLM) function provides the capability to control where your work requests are run, in order to optimize performance and workload throughput. WLM uses the CICSPlex® SM dynamic routing program EYU9XLOP to route work requests to the most suitable target region from a predefined set of target regions.

In a CICSplex or BTS-set, resources such as transactions and programs required in one region may be owned by another. For example, you may have a terminal-owning region (TOR) that requires access to transactions owned by an application-owning region (AOR).

You can specify the location of a resource when you are designing your system. Then, requests of a specific resource are always routed to the same region. Typically, the location of the resource is specified in the installed resource definition. This is known as static routing.

With dynamic routing, the decision on where to run a piece of work is made by the user-replaceable dynamic routing program (called the dynamic transaction routing program in previous releases). The user-replaceable program EYU9XLOP creates the environment necessary for CICSPlex SM dynamic routing, and sets up the runtime environment.

The CICSPlex SM dynamic routing program supports:
The dynamic routing program can route:
  • Transactions initiated at a terminal
  • Eligible EXEC CICS START requests that are associated with a terminal
  • Eligible EXEC CICS START requests that are not associated with a terminal
  • Dynamic program link (DPL) requests that are received using:
    • The CICS Web Interface
    • CICS® Transaction Gateway
    • External CICS interface (EXCI) client programs
    • Any CICS client workstation products using the External Call Interface (ECI)
    • Distributed Computing Environment (DCE) remote procedure calls (RPCs)
    • Open Network Computing (ONC) RPCs
    • The Link3270 bridge
    • Any function that issues an EXEC CICS LINK PROGRAM request
  • CICS business transaction services (BTS) processes and activities

In CICSPlex SM, dynamic routing is managed by the Workload Manager component of CICSPlex SM.

The CICS regions involved in dynamic routing may act as one or more of the following:
Requesting region
The CICS region in which the work request originates.
Routing region
The CICS region in which the decision is taken on where the work will run.
Target region
The CICS region where the request is actioned.

For dynamic transaction routing, the requesting region and the routing region are typically TORs, and the target region is typically an AOR.

For inbound DPL client requests, the requesting region and the routing region are typically TORs, and the target region is typically an AOR.

For EXEC CICS START commands associated with a terminal, the requesting region is typically an AOR, the routing region is typically a TOR, and the target region is typically an AOR.

For peer-to-peer DPL requests, for EXEC CICS START commands that are not associated with a terminal, for CICS business transaction services processes and activities, and for Link3270 bridge requests, the requesting region, routing region, and target region are typically AORs.



eyue3c2.html | Timestamp icon Last updated: Sunday, 4 June 2017