How to route transactions started by terminal-related START commands

You can set a number of options on a terminal-related START command that can affect the set of regions to which the transaction can be routed.

For a transaction started by a terminal-related START command to be eligible for the enhanced routing method, all of the following conditions must be met:
  • The START command must be a member of the subset of eligible START commands; that is, it must meet all the following conditions:
    • The START command specifies the TERMID option, which names the terminal associated with the current task.
    • The principal facility of the task that issues the START command is a terminal. The principal facility is not a terminal if, for example, the program that issues the START command has a DPL link; in this case, the principal facility is the intersystem session.
    • The principal facility of the task that issues the START command is not a surrogate client virtual terminal.
    • The SYSID option of the START command does 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.

    The requesting region and the TOR can be the same region.

  • The requesting region and the TOR, if they are different, must be connected by one of the following links:
    • An MRO link
    • An APPC parallel-session link
    • An IPIC link. For IPIC links, both regions must be at CICS® TS for z/OS®, Version 4.1 or later
  • The TOR and the target region must be connected by one of the following links:
    • An MRO link
    • An IPIC link. For IPIC links, both regions must be at CICS TS for z/OS, Version 4.1 or later
    • An APPC single- or parallel-session link. If an APPC link is used, at least one of the following must be true:
      • Terminal-initiated transaction routing has previously taken place over the link.
      • CICSPlex® SM is being used for routing.
  • The transaction definition in the requesting region must specify ROUTABLE(YES).
  • If the requesting region and the TOR are different, the transaction definition in the requesting region must not specify the REMOTESYSTEM option. If the requesting region and the TOR are the same region, you may use REMOTESYSTEM in the transaction definition for static routing.
  • If the transaction is to be routed dynamically, the transaction definition in the TOR must specify DYNAMIC(YES).
    Important: When considering which START-initiated transactions are candidates for dynamic routing, you must take particular care if the START command specifies any of the following options:
    • AT, AFTER, INTERVAL, or TIME; that is, there is a delay before the START is run.
    • QUEUE.
    • REQID.
    • RTERMID.
    • RTRANID.