Chapter 17. writing a distributed routing program – IBM SC33-1683-02 User Manual

Page 607

Advertising

Chapter 17. Writing a distributed routing program

Considerations common to all user-replaceable programs

Note that the comments contained in “Chapter 5. General notes about
user-replaceable programs” on page 401 apply to this chapter.

This chapter describes the CICS default distributed routing program and tells you
how to write your own version. It assumes you are familiar with the principles of
dynamic and distributed routing described in the

CICS Intercommunication Guide,

and that you have read the

CICS Business Transaction Services manual.

You can use the distributed routing program to route:

CICS business transaction services (BTS) processes and activities

Non-terminal-related EXEC CICS START requests.

For detailed information about which non-terminal-related START requests are
eligible for distributed routing, see the

CICS Intercommunication Guide.

Notes:

1. You cannot use the

distributed routing program—that is, the program named on

the DSRTPGM system initialization parameter—to route:

Transactions initiated from user terminals

Transactions initiated by terminal-related EXEC CICS START commands

Program-link requests.

To route these, you must use the

dynamic routing program named on the

DTRPGM system initialization parameter. How to write a dynamic routing
program is described in “Chapter 16. Writing a dynamic routing program” on
page 549.

2. The dynamic routing program and the distributed routing program may, of

course, be the same program.

Important

If you use the CICSPlex System Manager (CICSPlex SM) product to manage
your CICSplex, you may not need to write a distributed routing program.
CICSPlex SM provides a fully-functioning routing program that supports
workload balancing and workload separation. All you have to do is to tell
CICSPlex SM, through its user interface, which regions in the CICSplex can
participate in the workload, and define any transaction affinities that govern the
regions to which particular requests must be routed. For introductory
information about CICSPlex SM, see the

CICSPlex SM Concepts and

Planning manual.

The rest of the chapter is divided into the following sections:

1. “Differences from the dynamic routing interface” on page 576

2. “Distributed routing of BTS activities” on page 577

3. “Routing of non-terminal-related START requests” on page 581

4. “Parameters passed to the distributed routing program” on page 585

5. “Naming your distributed routing program” on page 593

575

|
|

|
|
||

|
|
|
|