This section discusses the following topics:
CICS transaction routing allows terminals connected to one CICS system to run with transactions in another connected CICS system. This means that you can distribute terminals and transactions around your CICS systems and still have the ability to run any transaction with any terminal.
This feature aims that TMA SNA supports inbound terminal initiated transaction routing in MF CICS/ART CICS integration, in such a scenario, MF CICS can only be TOR and ART CICS can only be AOR.
Transactions can be triggered from a TOR terminal and run on AOR; the execution process is exactly as same as it running local.
ARTCICS
servers and GWSNAX
server in the UBBCONFIG
file.DMCONFIG
for TMA SNA, and define ARTSTRN
exported services in the DM_EXPORT
section, which corresponds to the TOR-invoked transactions.
"CONV=Y
" is mandatory here because ARTSTRN
is a conversational server.
Figure 8-2 shows a typical example.
There is a TOR
with terminals on mainframe, and an ART AOR
on open system, they communicate each other via APPC connection provided by TMA SNA.
A pseudo conversation transaction HAI1
starts from a TOR
terminal. This transaction is defined as a remote transaction on AOR
, so TOR
forwards the request to AOR
. This causes the transaction to execute; the terminal and transaction exchange screen data via the transaction routing mechanism.
Note: CR01
is a CICA connection, which points to TMA SNA LU
Note: | The relevant mapset definition is not mandatory in ARTKIX . |