Adding workload separation requirements
To implement workload separation in the same workload, by any combination either of user id, terminal id, and transaction group, or of process type and transaction group, do the following:
- Create a CICS system group for each set of target regions,
using the System group definitions view (CSYSGRP object). For example,
if:
- Transactions initiated by users ABC* from terminals NETA* must be routed to target regions 2 through 7
and
- Transactions initiated by users HIJ* from any terminal must be routed to target regions 5 through 9
- Define a transaction group, using the Transaction groups view (TRANGRP object), if workload separation by transaction is to be implemented. For example, if transactions EFG1, EFG2, and EFG3 must be routed to a specific group of target regions, you must define a transaction group to include those transactions.
- Create one workload definition, using the Workload definitions view
(WLMDEF object), for each user, terminal, and transaction group combination.
For the example in item 1 (above):
- One workload definition would be required for the combination of any transaction, users ABC*, and terminals NETA*.
- One workload definition would be required for the combination of any transaction, users HIJ*, and any terminal.
- If the workload definitions are to be installed automatically when the
first requesting region in the workload starts, you should use the Workload
groups view (WLMGROUP object) to:
- Create a workload group.
- Add the workload definitions to the workload group.
- Associate the workload group with the workload specification.
Automatic installation of the workload definitions is likely to be required, because workload separation is usually a regular and consistent requirement. However, you can also install a workload group or individual workload definitions manually for immediate effect.