Indirect links for transaction routing

Because CICS® does not support indirect links for transaction routing, each region in a chain of three or more regions must contain a WD entry and TD entry for the ATI started transaction and the terminal against which it is to be started. These definitions must name the neighboring system, such that the terminal and transaction can be found. For example, consider the following three regions: REGIONA, REGIONB, and REGIONC. REGIONA is the terminal-owning region and REGIONC is the application-owning region. A terminal that is attached to REGIONA is starting a transaction called XXXA, which results in REGIONC trying to start a transaction on REGIONC called XXXC, as shown in Table 1:

Table 1. Indirect links for transaction routing
REGIONA REGIONB REGIONC

RD: LocalSysId="REGA"
CD: REGB
WD: RemoteSysId=""
NetName="TERM0001"

TD: Entry for transaction\
       "XXXA"
RemoteName="XXXB"
RemoteSysId="REGB"

RD: LocalSysId="REGB"
CD: REGA
CD: REGC
WD: RemoteSysId= \
         "REGIONA"
NetName="TERM0001"
          
TD: Entry for transaction\
        "XXXB"
RemoteName="XXXC"
RemoteSysId="REGC"
      

RD: LocalSysId="REGC"
CD: REGB
WD: RemoteSysId="REGB"
NetName="TERM0001"
  
TD: Entry for transaction\
      "XXXC"
RemoteName=""
RemoteSysId=""
In this table:
  • REGA, REGB, and REGC are the entries for REGIONA, REGIONB, and REGIONC respectively.
  • The RemoteName defaults to transaction entry name if not specified.
Parent topic: Communications