Filter
Top Products
Chapter 17. Writing a dynamic 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 435 apply to this chapter.
This chapter describes the CICS default dynamic routing program and tells you how
to write your own version. It assumes you are familiar with the principles of CICS
transaction routing, CICS distributed program link (DPL), and Introduction to CICS
dynamic routing described in the CICS Intercommunication Guide.
You can use the dynamic routing program to route:
v Transactions initiated from user terminals
v Transactions initiated by a subset of terminal-related EXEC CICS START
commands
v Program-link requests
v Program-link requests to DFHL3270 to execute a CICS transaction using the
bridge.
For detailed information about which transactions initiated by START commands,
and which program-link requests, are eligible for dynamic routing, see Routing
transactions invoked by START commands, in the CICS Intercommunication Guide.
Note:
1. You cannot use the dynamic routing program—that is, the program
named on the DTRPGM system initialization parameter—to route:
v CICS business transaction services activities and processes.
v Method requests for enterprise beans or CORBA stateless objects.
v Non-terminal-related EXEC CICS START requests.
v Inbound Web services requests.
To route these types of request you must use the distributed routing
program named on the DSRTPGM system initialization parameter. How
to write a distributed routing program is described in Chapter 18, “Writing
a distributed routing program,” on page 623.
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 dynamic routing program. CICSPlex SM
provides a fully-functioning dynamic 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 dynamic
routing, and define any transaction affinities that govern the target regions to which
particular transactions 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. “Routing transactions dynamically” on page 590
2. “Routing DPL requests dynamically” on page 597
© Copyright IBM Corp. 1977, 2011 589