You have to perform the following operations to implement transaction
routing in your installation:
- Install MRO or ISC support, or both, as described in Installing intercommunication support.
- Define MRO or ISC links between the systems that are to be connected,
as described in Defining links to remote systems.
- Define the terminals and transactions that will participate in
transaction routing, as described in Defining remote resources.
- Ensure that the local communication profiles, transactions, and
programs required for transaction routing are defined and installed
on the local system, as described in Defining local resources.
- If you want to use dynamic transaction routing, customize the
supplied dynamic routing program, DFHDYP, or write your own version.
For programming information about how to do this, see the CICS® Customization Guide.
- If you want to route to shippable terminals
from regions where those terminals might be ‘not known’, code
and enable the global user exits XICTENF and XALTENF. For programming information about coding
these exits, see the CICS Customization Guide.
If the link to a remote region is established, but there are no
free sessions available, transaction routing requests may be queued
in the issuing region. Performance problems can occur if the queue
becomes excessively long.
For guidance information about controlling intersystem queues,
see Intersystem session queue management.
[[ Contents Previous Page | Next Page Index ]]