Writing a distributed routing program

Considerations common to all user-replaceable programs

Note that the comments contained in General notes about user-replaceable programs apply to this section.

This section 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 and Java™ Applications in CICS manuals.

You can use the distributed routing program to route:

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 Writing a dynamic routing program.

  2. The dynamic routing program and the distributed routing program may 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 section is divided as follows:

  1. Differences between the distributed and dynamic routing interfaces
  2. Routing BTS activities
  3. Routing method requests for enterprise beans and CORBA stateless objects
  4. Routing non-terminal-related START requests
  5. Routing inbound Web service requests
  6. Routing by user ID
  7. Dealing with an abend on the target region
  8. Some processing considerations
  9. Parameters passed to the distributed routing program
  10. Naming your distributed routing program
  11. Distributed transaction routing sample programs
[[ Contents Previous Page | Next Page Index ]]