Separating by process type

You can create a CICS® BTS workload that routes requests associated with a certain process type to a specific target region or set of target regions. For example, you may want to route all the requests associated with the STOCK process type to a special subset of target regions.

Figure 1 illustrates what such a workload might look like, if the process type associated with a CICS BTS transaction is STOCK, the transaction is routed to a set of target regions identified as EYUCSG05. If the process type is anything other than STOCK, the transaction is routed to the default set of target regions identified as EYUCSG01 in the workload specification.
Figure 1. Sample definition separating a workload by process type
The diagram illustrates separation of a workload by process type. Two MVS systems, System A and System B are shown. System A has a CMAS, EYUCMS1A and four MASs, EYUMAS1A (a TOR), EYUMAS2A (an AOR), EYUMAS3A (an AOR) and EYUMAS4A (a FOR). System B has a CMAS, EYUCMS1B and a MAS, EYUMAS1B (an AOR). Sysplex EYUPLX01 contains all the MASs from both systems. System Group EYUCSG01 contains all three AORs (across both systems) and the FOR.. EYUMAS1B is also contained in system group EYUCSG05. EYUCMS1A is the maintenance point for CICSplex EYUPLX01. There is a connection between the two CMASs. The workload definition , EYUWMD04 in the data repository specifies Luname as * Userid as * and Process Type as STOCK. The Target Scope is EYUCSG05. The workload group definition, EYUWMG04 associates workload definition EYUWMD04 with workload specification EYUWMS05. The workload specification , EYUWMS05 specifies Target Scope as EYUCSG01, Routing scope as EYUMAS1A and Group as EYUWMG04.

If you choose to separate a workload by process type, you must set the Luname and Userid fields to *. If you separate a workload by LU name and user ID, you must set the Process Type field to *. If you want to separate an enterprise bean workload, the Luname and Process Type fields must be set to *. You can separate a workload only either by process type or by LU name and user ID.

You can specify either a specific or a generic process type. During workload separation processing, CICSPlex® SM evaluates the process type supplied by CICS to determine to where the transaction should be routed.
  • If the process type matches the selection criteria specified in an installed definition, the request is routed to the target regions identified in the definition.
  • If the process type does not match the selection criteria, a match may be found based on the transaction's associated LU name and user ID. If a match is found based on these criteria, the request is routed to the target regions identified in the associated definition.
  • If no match is found using the process type, LU name and user ID, the request is routed to the default set of target regions identified in the specification.
Note: Separation by process type takes precedence over separation by LU name and user ID. Thus, if a transaction's associated process type, LU name and user ID mean that it satisfies the selection criteria specified in two workload definitions, one specifying separation by process type and the other separation by LU name and user ID, the transaction is routed to a region in the target scope specified in the workload definition specifying separation by process type.


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