There are two methods of defining transactions that are to be statically
routed.
Using separate local and remote definitions
You create a remote definition for the transaction, and install it on the
requesting region: the REMOTESYSTEM option must specify the name of
the target region (or the name of an intermediate system, if the request is
to be “daisy-chained”).
Using dual-purpose definitions
A dual-purpose transaction definition is shared between
the requesting region and the target region (and possibly between
intermediate systems too, if “daisy chaining” is involved). The REMOTESYSTEM
attribute specifies the name of the target region.