Workload separation routes work from a requesting
or routing region among a set of target regions. You can define the
routing criteria for the default rule.
Procedure
- In the Targets section of the Workload
Specification editor, specify the default routing criteria
from the following values.
- Targets
- The name of the CICS® system,
or CICS system group that is
the target for any transactions that are not associated with an installed
transaction group. Type the name of the system group that you want
to use for the default rule, or click Browse to
select from a list of all the CICS systems,
or CICS system groups in the
CICSplex.
- Algorithm
- The algorithm that is used when you select the best target region
in the target scope to which a transaction is routed. The default
routing algorithm is applied to every routed dynamic transaction in
the workload, except those transactions that are associated with a
transaction group that has a routing algorithm specified. You can
choose one of the following routing algorithms:
- GOAL
- QUEUE
- LN_GOAL (Link neutral goal )
- LN_QUEUE (Link neutral queue)
- Primary search criterion
- Identifies whether the user name (USERID) or the logical unit
name (LUNAME) is used as the primary search criteria for transactions
that are not associated with an installed transaction group.
- Event
- The name of an analysis definition (RTADEF) or status definition
(STATDEF) that might affect transactions using the default transaction
group for this workload specification. If a real-time analysis event
is generated by this definition, WLM uses the information to select
the best routing for those transactions.
If this field is blank,
no analysis or status definition is associated with the default transaction
group.
- If the transactions establish affinities, then select These
transaction establish affinities in the Affinities section
of the Workload Specification editor. Provide
the affinity criteria from the following values.
Relationship- GLOBAL
- When you define an affinity relation of GLOBAL, all instances
of all the transactions started from any terminal, by any START command,
or by any CICS BTS process,
must run in the same target region for the lifetime of the affinity.
Valid Lifetimes are:
- LUNAME
- When you define an affinity relation of LUNAME, all instances
of all the transactions in the group that are associated with the
same terminal must run in the same target region for the lifetime
of the affinity. Valid Lifetimes are:
- USERID
- When you define an affinity relation of USERID, all instances
of the transactions that are initiated from a terminal, by a START
command, or by a CICS BTS activity,
and executed on behalf of the same user ID, must execute in the same
target region for the lifetime of the affinity. Valid Lifetimes are:
- BAPPL
- When you define an affinity relation of BAPPL, all instances
of transactions that are associated with the same BTS process must
run in the same target region for the lifetime of the affinity. Valid
Lifetimes are:
- SYSTEM
- PERMANENT
- ACTIVITY
- PROCESS
- LOCKED
- When you define an affinity relation of LOCKED, all instances
of transactions in the group that are associated with dynamically-linked
programs that have the same unit of work must run in the same target
region for the lifetime of the unit of work. Valid Lifetimes are:
- To set abend thresholds, click These transactions
have abend thresholds. Move the sliders to the required
threshold values.
- Press Ctrl+S (cmd+S for OS X) to save your changes.