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

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.