Non-terminal-related START commands

For a non-terminal-related START request to be eligible for dynamic routing, all of the following conditions must be met.

  • The requesting region and the target region are connected in one of the following ways:
    • An MRO link.
    • An APPC single-session or parallel-session link. If an APPC link is used and the distributed routing program is called on the target region, CICSPlex® SM must be used for routing.
    • An IPIC link.
  • The transaction definition in the requesting region specifies DYNAMIC(YES).
In addition, if the request is to be routed dynamically, the SYSID option of the START command must not specify the name of a remote region. (That is, the remote region on which the transaction is to be started must not be specified explicitly.)
Note: When considering which START-initiated requests are candidates for dynamic routing, you must take particular care if the START specifies any of the following options:
  • AT, AFTER, INTERVAL(non-zero), or TIME. That is, there is a delay before the START is performed.

    If the request is delayed, the interval control element (ICE) created by the START request is kept in the requesting region with a transaction ID of CDFS. When the ICE expires, the CDFS transaction runs; it retrieves any data specified by the user and reissues the START request without an interval. The request will be routed based on the state of the transaction definition and the sysplex at that moment. Ensure that security for CDFS is correctly configured.

  • QUEUE.
  • REQID.
  • RTERMID.
  • RTRANID.

You must understand how these options are being used; whether, for example, they affect the set of regions to which the request can be routed.