Setting the routing criteria for a routing rule
Workload separation routes work from a requesting or routing region among a set of target regions. You can define the routing criteria for a specific routing rule.
Procedure
- In the Rules section of the Workload Specification editor, click the routing rule that you want to define routing criteria for.
- In the Targets section of the Workload
Specification editor, specify the 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.
- Terminal LU name
- The specific or generic logical unit name that is used to match a transaction with a workload definition.
- User ID
- The specific or generic user ID that is used to match a transaction with the workload definition.
- BTS process type
- The specific or generic process type that is used to match a transaction
with the workload definition.
Terminal LU name and User ID must both be set to '*' if a specific process type is defined. A Transaction group of blanks or a specific name can be specified. You can separate a workload only by Transaction group and Process type, or by Transaction group, Terminal LU name, and User ID.
- The Transactions section identifies
the specific transactions that the workload separation rules are applied
to. If there are no transactions specified for the workload, click Select
transaction group to add an existing transaction group
and associated transactions. Alternatively, click Create
transaction group to create a new group. Edit the field
values for the transaction group as required:
- Name
- The name of the transaction group. For a new group, you can enter a name before you save the group, or CICS Explorer® can generate a name when you save the group. After you save the transaction group, you cannot change the name.
- Description
- The description for the transaction group. You can change the description at any time.
- Transactions
- A list of the transactions in the transaction group is shown.
You can add transactions in one of the following ways:
- Type the name of the transaction in the Transactions field, then click Add.
- Click Browse to show a list of the local transactions that are available to add. Select one or more transactions, then click OK.
- Algorithm
- The algorithm that is used to select the best target region to
which a transaction in the current transaction group will be routed.
Valid options are as follows:
- QUEUE
- LNQUEUE
- GOAL
- LNGOAL
- INHERIT
- Primary search criterion
- Identifies whether the user name or the logical unit name is
used as the primary search criteria for transactions associated with
the transaction group. Valid options are as follows:
- USERID
- LUNAME
- Status
- Indicates how an AOR is to be selected for transactions that
are associated with the transaction group. Valid options are as follows:
- ACTIVE
- DORMANT
- Event
- The name of an analysis definition (RTADEF)
or status definition (STATDEF) that might affect
transactions that use 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, 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:
- SYSTEM
- PERMANENT
- 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:
- SYSTEM
- PERMANENT
- 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:
- SYSTEM
- PERMANENT
- 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:
- UOW
- 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.
Parent topic: Working with routing rules
Related reference: