Transaction routing summary

Before you define terminals for transaction routing, you must consider which of the various methods of defining terminals is most suitable for your CICS configuration.

  • Use the shipping method, unless you use terminals that are known by different names in different systems. For ATI to work with the shipping method in a transaction owning system, you might need to use the XALTENF and XICTENF global exits. See Terminal not known condition exits XALTENF and XICTENF for programming information on these exits.
  • Use the sharing method for systems with a shared CSD file, if you use the same names in different systems and you do not want to use global exits to ensure that ATI works.
  • Use the duplicating method if you use terminals that are known by different names in different systems, or if you use ATI to acquire terminals but do not have a shared CSD file, and you do not want to use the XALTENF and XICTENF global user exits.

You could use a mixture of methods: perhaps shipping for display terminals, and duplicating for printers that need ATI to acquire them but without the use of the XALTENF and XICTENF global user exits.

Before you start creating definitions for intercommunication resources, see Defining connections to remote systems for further information. There, you can find useful examples of the attributes you must specify for different types of links and sessions.