Dynamic routing with channels

EXEC CICS LINK and EXEC CICS START commands, which pass channels, can be dynamically routed.

The following types of channel-related request can therefore be dynamically routed:
  • Program-link (DPL) requests
  • Transactions started by terminal-related START requests
  • Non-terminal-related START requests
The routing program is passed, in the DYRCHANL field of its communication area, the name of the channel, if any, associated with the program-link or START command. The DYRCHANL field applies only to the three types of request as previously listed. For other types of request, or if there is no channel associated with the request, it contains blanks.
Note: The routing program's communication area is mapped by the DFHDYPDS DSECT.

Note that the routing program is given the name of the channel, not its address, and so is unable to use the DYRCHANL field to inspect or change the contents of the containers.

An application that uses a channel can create, within the channel, a special container named DFHROUTE. If the application issues a LINK or terminal-related START request (but not a non-terminal-related START request) that is to be dynamically routed, the dynamic routing program is given, in the DYRACMAA field of DFHDYPDS, the address of the DFHROUTE container, and can inspect and change its contents.

If you are migrating a program to pass a channel rather than a COMMAREA, you could use its existing COMMAREA structure to map DFHROUTE.



dfhp3_routing.html | Timestamp icon Last updated: Monday, 5 June 2017