Is the workload being separated?

After you know which workload is active on the routing region, the next step is to find out if the workload is being separated based on TRANSID, USERID, LUNAME, or a combination of these.

To do that, take the request in question (the one defined as dynamic, initiated by terminal input) and see whether it is a member of any active transaction groups:
  • From the main menu, click Active workload views > Dynamic transactions.
  • The "Active workload dynamic transactions" tabular view (WLMATRAN object) is displayed.

If the transaction in question is listed in this view, the routing decision is possibly based on a workload definition associated with the transaction group of which the transaction is a member. Note the name of the transaction group.

Now look at the active workload definitions:
  • From the main menu, click Active workload views > Definitions.
  • The "Active workload definitions" tabular view (WLMAWDEF object) is displayed.
This view shows you which workload definition, if any, applies to the routing request in question. You know the USERID and LUNAME from which the routing request came. You also know whether the transaction is a member of an active transaction group, and, if it is, you know the name of the transaction group. Given these three things, you can tell which workload definition, if any, controls the routing decision. The following pseudocode explains the logic:
IF dynamic transaction in question is a member of an active transaction group
 
 THEN  IF there is a workload definition associated with that transaction group
        THEN  IF the USERID and NAME match the pattern on that workload definition
               THEN  that workload definition will control the routing decision
               ELSE  the workload default controls the routing decision
        ELSE  the workload default controls the routing decision
 
 ELSE  IF there is a workload definition not associated with a transaction group
        THEN  IF the USERID and NAME match the pattern on that workload definition
               THEN  that workload definition will control the routing decision
               ELSE  the workload default controls the routing decision
        ELSE  the workload default controls the routing decision
To illustrate this logic, here are some examples using the data on the "Active workload definitions" tabular view, which is shown in Table 1.
Table 1. Tabular representation of an "Active workload definitions" view (WLMAWDEF object)
Name System ID of workload owner Workload definition Transaction group Terminal LU name User ID Process type Scope name of set of target regions
T123DEF EYUWLS02 HTC1   .++++T123 *   EYUMAS1B
WMDFAFFA EYUWLS02   HTC1 WMTAFFA .*   EYUMAS1B
WMDFAAB EYUWLS02 HTC1 WMTAFFB .* DEPT02*   EYUMAS2B
WDMFAFFC EYUWLS02 HTC1 WMTAFFC .* *   EYUCSG02
Example 1
The transaction is a member of active transaction group WMTAFFA. The USERID is DEPT01DZ. The LUNAME is NET1.IYJFT123. The routing decision is controlled by workload definition WMDFAFFA.
Example 2
The transaction is not a member of an active transaction group. The USERID is DEPT01DZ. The LUNAME is NET1.IYJFT123. The routing decision is controlled by workload definition T123DEF.
Example 3
The transaction is a member of active transaction group WMTAFFB. The USERID is DEPT01DZ. The LUNAME is NET1.IYJFT123. The routing decision is controlled by the workload default.

When you know which workload definition is controlling the routing decision, the Target Scope field on that same "Active workload definitions" view (WLMAWDEF object) shows you the target region or target region group to which the transaction is routed. If the workload default is controlling the routing decision, the Default target scope field on the "Active workloads" view (WLMAWORK object) shows where the transaction is routed.



eyus1c0061.html | Timestamp icon Last updated: Monday, 5 June 2017