Defining terminals for transaction routing

Terminal-related transaction routing is the routing of transactions started from user-terminals, and transactions started by terminal-related ATI requests. There are a number of rules that define whether a terminal is eligible for transaction routing.

Most of the terminal and session types supported by CICS® are eligible for transaction routing. However, the following terminals are not eligible, and cannot be defined as remote resources:
  • LUTYPE6.1 connections and sessions
  • MRO connections and sessions
  • IBM® 7770 or 2260 terminals
  • Pooled 3600 or 3650 pipeline logical units
  • MVS™ system consoles.
Both the terminal and the transaction must be defined in both CICS systems, as follows:
  1. In the terminal-owning region:
    1. The terminal must be defined as a local resource (or must be autoinstallable).
    2. The transaction must be defined as a remote resource if it is to be initiated from a terminal or by ATI.
  2. In the application-owning region:
    1. The terminal must be defined as a remote resource, unless a shipped terminal definition is available; see Shipping terminal and connection definitions) for more information.
    2. The transaction must be defined as a local resource.

If transaction routing requests are to be “daisy-chained” across intermediate systems, the same rules apply. In addition, both the terminal and the transaction must be defined as remote resources in the intermediate CICS systems. If you are using non-z/OS Communications Server terminals, you also need to define indirect links to the TOR on the AOR and the intermediate systems (see Defining indirect links for transaction routing).



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