Creating a BTS-set

The recommended method of using BTS in a sysplex is to have several sets of BTS regions (BTS-sets). Each set is designed to deal with one or more process-types (types of business transaction). The easiest way to create the sets is by cloning individual regions.

Figure 53 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 53. 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 picture shows the scenario described in the preceding text. It shows a sysplex containing two BTS-sets. BTS-set 1 is the PAYROLL BTS-set. It contains three interconnected CICS regions which all have access to the PAYROLL repository data set. BTS-set 2 is the TRAVEL and MISCELLANEOUS BTS-set. It contains three interconnected CICS regions which all have access to the TRAVEL and MISCELLANEOUS repository data set.

The number of regions in a BTS-set will be related to:

To create each BTS-set, on each of the regions in the set:

  1. 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.
  2. 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).

  3. 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 the CICS Intercommunication Guide.

  4. Enable the distributed routing program--see the next section.

Naming the routing program

You specify which distributed routing program CICS is to use on the DSRTPGM system initialization parameter. The name you specify might be that of the CICSPlex® SM routing program, EYU9XLOP, or of your own user-written program. For information about DSRTPGM, see Naming the routing program.

After CICS has initialized, you can discover which distributed routing program, if any, is in use by issuing an EXEC CICS or CEMT INQUIRE SYSTEM command. The DSRTPROGRAM option returns the program name.

After CICS has initialized, you can change the distributed routing program currently in use by issuing an EXEC CICS or CEMT SET SYSTEM command. The DSRTPROGRAM option specifies the program name.

Related concepts
The scope of a BTS-set
Dynamic routing of BTS activities
Sysplex support in BTS
Related tasks
Using a CICS distributed routing program
Using CICSPlex SM with BTS
[[ Contents Previous Page | Next Page Index ]]