Which BTS activities can be dynamically routed?

Not all activations of BTS processes and activities can be routed. Processes and activities that are activated asynchronously with the requestor, with a RUN ASYNCHRONOUS command, can be routed either dynamically or statically.

Processes and activities that are activated synchronously with the requestor, with a RUN SYNCHRONOUS or LINK command, are always run locally. They cannot be routed dynamically or statically. A RUN SYNCHRONOUS or LINK command issued against an activity whose associated transaction is defined as DYNAMIC(YES), or as remote, results in the activity being run locally. When an activity is activated by a LINK command, all the attributes of its associated transaction are ignored, because the activity runs under the TRANSID of the parent - there is no context-switch.

Thus, to be eligible for dynamic routing:
  • A process or activity must be run asynchronously with the requestor, with a RUN ASYNCHRONOUS command.
  • The TRANSACTION definition for the CICS® transaction associated with the process or activity must specify DYNAMIC(YES).

"Daisy-chaining" is not supported. Once a BTS process or activity has been routed to a target region it cannot be rerouted from the target to a third region, even though its associated transaction is defined as DYNAMIC(YES) in the target.



dfhp94v.html | Timestamp icon Last updated: Sunday, 4 June 2017