Routing non-terminal-related START requests

You can use a distributed routing program to dynamically route non-terminal-related EXEC CICS START requests.

Which requests can be dynamically routed?
When the distributed routing program is invoked
Changing the target CICS region
Telling CICS whether to route the request
When the routing program is invoked for routing, if you want the request to be routed (whether you have changed any values or not) return a zero value to CICS in field DYRRETC of the communications area.
If an error occurs in route selection
If an error occurs in route selection—for example, if the sysid returned by the distributed routing program is unavailable or unknown—the routing program is invoked again.
Using the XICERES exit to check the availability of resources on the target region
You can use an XICERES global user exit program to check that all resources required by the started transaction are available on the target region.
Invoking the distributed routing program on the target region
The route selection, notification, route selection error, and routing complete invocations of the distributed routing program all occur on the routing region. If you want the routing program to be re-invoked on the target region, set the DYROPTER field in the communications area to 'Y'. You must do this on the program's initial (route selection or notification) invocation—and again, if it is reinvoked for a route selection error.

Parent topic: Writing a distributed routing program

Related concepts

Routing BTS activities
Routing by user ID
Dealing with an abend on the target region
Link checks and information for distributed routing programs

Related tasks

Naming your distributed routing program
Assembling and link-editing user-replaceable programs

Related reference

Differences between the distributed and dynamic routing interfaces
Parameters passed to the distributed routing program
Distributed transaction routing sample programs