Workload separation
Workload separation routes work from a requesting or routing region among a set of target regions, but the requirements of users, terminals, the transactions themselves, and their BTS process type, can influence which target region set is used.
The routing of particular transactions or programs to a particular group of target regions is based on any combination either of user ID, terminal ID, and transaction group. For BTS processes, routing is based on a combination of transaction group and process type. For enterprise bean-related transactions, routing is based on transaction group. For Link3270 bridge requests, separating by terminal luname is subject to some restrictions. See Separating Link3270 bridge workloads for more information.
- Any transaction initiated by users whose user IDs begin with the characters "PAY" must be routed to a target region in CICS® system group AORPAY1.
- Any transaction initiated from a terminal whose LU name begins with the characters "NYORK" must be routed to a target region in CICS system group AORNYORK.
- Any transaction belonging to the transaction group ACCOUNTS must be routed to a target region in CICS system group AORACCNT.
- All processes associated with a BTS process type TRAVEL are routed to a target region in one BTS-set, and all processes associated with BTS process-type PAYROLL are routed to another BTS-set.
- All enterprise bean-related transactions belonging to transaction group STOCK are routed to any target region in CICS system group STOCKTG, if the user id matches that in the workload definition.
The decision as to which region is selected from the group of target regions that meet the workload separation criteria is based on the same routing criteria as described in Workload routing. The algorithm that is applied when making the routing decision can either be specified at the individual workload separation level or can be left to default to the algorithm used by basic workload routing.