About workload view route fields

Use the "Active workload target distribution factors" and "Summarized active target region distribution trends" views together with route fields statistics displayed in the active workload views to understand what is happening in workload management.

You can use the route fields statistics information in the "Summarized active target region distribution trends" view to verify that your existing workload is running correctly, and that it is not losing transactions. The "Summarized active target region distribution trends" view also provides a new perspective on events inside WLM during the routing process.

Using the "Active workload views", you can highlight potential issues with your setup. For example, if routing is called and continually retrying to discover other available targets.

You can see counts of what is happening inside WLM; for example, the number of Route completes versus the number of Route selects. An example of this is the Route notifies field which shows you when you are linking to a program that is defined as DYNAMIC(YES) and you have provided a SYSID.

Using the "Summarized active target region distribution trends" view with the "Active workload target distribution factors" view can help you understand WLM routing decisions and behavior of CICSPlex SM. You might want to understand why some regions are receiving more work than others, and an analysis of Route Selections shows which regions are receiving more work than others.

Figure 1 illustrates the route field processes involved in distributed routing.

Figure 1. Conceptual view of distributed routing
This diagram shows a Routing Region (TOR) and a Target Region (AOR). The routing region (TOR) contains five actions, a Route select, Route error, Route complete, a Route notify and a second Route complete action. The target region (AOR) contains 4 actions, a Route initiate, an Execute, a Route abend and a Route terminate action. The process flow starts with the Route select action which is passed from the routing region (TOR), to run in the target region (AOR) and then the Route terminate stops the action.

Figure 2 illustrates the route field processes involved in dynamic routing.

Figure 2. Conceptual view of dynamic routing
This diagram shows a Routing Region (TOR) and a Target Region (AOR). The routing region (TOR) contains two actions, a Route select action and a Route terminate action. The target region (AOR) contains an Execute action. The process flow starts with the Route select action which is passed from the routing region (TOR), to run in the target region (AOR) and then the Route terminate stops the action.
These definitions describe the route fields:
Route select
Route select is updated when this region is selected as a target by CICSPlex SM workload management.
Route initiate
Route initiate is updated when a task routed using the distributed workload model starts on a target system.
Route error
Route error is updated when the region selected by CICSPlex SM is unreachable; for example, the connection is out of service, or no sessions are available. CICSPlex SM then attempts to select another region. This reselection is not counted as a Route select, and the Route select count for any subsequent region is not updated. A high number of route errors can indicate that there are insufficient sessions to run the workload. The lack of sessions can cause increased response time and CPU time because CICSPlex SM must try the routing again, potentially several times.
Route complete
Route complete is updated when a task that is routed using the distributed workload model starts on the target system. Route complete indicates to the routing system that its responsibility for this task is complete.
Route notify
Route notify is updated when a task is routed to a target region that is selected by the SYSID option on the LINK or START command. Route notify informs CICSPlex SM of the routing; CICSPlex SM does not choose the region. Route notify is a variant of static routing, in which the program or transaction is defined as Dynamic, but the API that calls it specifies a SYSID.
Route abend
Route abend is updated when a task is routed to a target region and subsequently abends; for example, because the transaction is not defined in that system or the program is unavailable.
Route terminate
Route terminate is updated when a task has completed in a target region, whether at the end of a distributed program link (DPL) or a dynamic transaction routing (DTR) request, or when a task that is routed using the distributed workload model finishes.



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