Dynamic routing of non-terminal-related START requests

Dynamic routing of non-terminal-related START requests uses the distributed routing model. The transaction definition in the requesting region specifies DYNAMIC(YES). If the request is eligible for dynamic routing, the distributed routing program is invoked for routing. The START request is function-shipped to the target region returned by the routing program.

Note:
  1. If the request is ineligible for dynamic routing, the distributed routing program is not invoked. Unless the SYSID option specifies a remote region explicitly, the START request is function-shipped to the AOR named in the REMOTESYSTEM option of the transaction definition in the requesting region; if REMOTESYSTEM is not specified, the START executes locally, in the requesting region.
  2. If the request is eligible for dynamic routing, but the SYSID option of the START command names a remote region, the distributed routing program is invoked for notification only; it cannot route the request. The START executes on the remote region named on the SYSID option.
  3. If the return code from the distributed routing program is not zero, the request fails with the following response code:
    eibrcode=SYSIDERR, eibresp2=1

    The dynamic routing program rejected the START request.

The dynamic routing program can indicate daisy-chaining support of non-terminal-related START requests. If you want to support this feature, return a value of Y in the DYRDCYN field in the communications area or container for the dynamic routing program (mapped by the DFHDYPDS copybook). You must ensure that your dynamic routing program performs appropriate workload routing and that unpredictable routing does not take place. For more information, see Telling CICS whether daisy-chaining of non-terminal-related START requests is supported.