When using BTS in a sysplex, you must have several
sets of BTS regions (BTS-sets). Each set deals with one or more process-types (types of business
transaction). You can create these sets by cloning individual regions.
About this task
Figure 1 shows a sysplex
that contains two BTS-sets. BTS-set 1 handles all processes of type
PAYROLL. All the regions in BTS-set 1 are interconnected and have
access to the BTS repository that contains details of PAYROLL-type
processes. BTS-set 2 handles all processes of types TRAVEL and MISC.
All the regions in BTS-set 2 are interconnected and have access to
the BTS repository that contains details of TRAVEL and MISC-type processes.
Figure 1. A sysplex containing two BTS-sets. BTS-set
1 handles all processes of type PAYROLL. BTS-set 2 handles all processes
of types TRAVEL and MISC.
The number of regions in a BTS-set is related to:
The number of process-types handled by the BTS-set
The workload associated with each process-type.
To create each BTS-set, perform the following steps on
each of the regions in the set.
Procedure
Define a connection to every other region in the BTS-set.
For performance reasons, you are recommended to use MRO or MRO/XCF
rather than APPC connections.
Give the region access to the BTS repository that contains
details of the process-types it is servicing.
The name
of the repository file is specified on the PROCESSTYPE definition
or definitions.
If you are using VSAM RLS to share the repository
file, on the FILE definition that defines the repository file to CICS®,
specify RLSACCESS(YES).
If you are using function-shipping to
share the repository file, on the FILE definition that defines the
repository file to CICS, specify REMOTESYSTEM(name_of_file-owning_region).
On the TRANSACTION definition for each transaction associated
with a BTS activity, specify DYNAMIC(YES).
Do not specify the REMOTESYSTEM option.
For general information about defining transactions
for transaction routing, and specific information about defining transactions associated with BTS
activities, see Defining transactions for transaction routing.