Conversation initiation and transaction hierarchy

A transaction starts a conversation by requesting the use of a session to a remote system. Having obtained the session, it causes an attach request to be sent to the other system to activate the transaction that is to be the conversation partner.

A transaction can initiate any number of other transactions, and hence, conversations. In a complex process, a distinct hierarchy emerges, with the terminal-initiated transaction at the very top. Figure 1 shows a possible configuration. Transaction TRAA is attached over the terminal session. Transaction TRAA attaches transaction TRBB, which, in turn, attaches transactions TRCC and TRDD. Both these transactions attach the same transaction, SUBR, in system CICSE. This gives rise to two different tasks of SUBR.
Figure 1. DTP in a multisystem configuration
The picture shows the scenario described in the preceding text. It shows five CICS regions, CICSA through CICSE, arranged in a hierarchical, pyramid structure, with CICSA at the top and CICSE at the base. CICSB is below CICSA; CICSC and CICSD are on the same level, below CICSB. A terminal starts a transaction, TRAA, in CICSA. TRAA attaches transaction TRBB, in CICSB. TRBB attaches transactions TRCC, in CICSC, and TRDD, in CICSD. TRCC and TRDD both attach transaction SUBR, in CICSE.

The structure of a distributed process is determined dynamically by program; it cannot be predefined. Notice that, for every transaction, there is only one inbound attach request, but there can be any number of outbound attach requests. The session that activates a transaction is called its principal facility. A session that is allocated by a transaction to activate another transaction is called its alternate facility. Therefore, a transaction can have only one principal facility, but any number of alternate facilities.

When a transaction initiates a conversation, it is the front end on that conversation. Its conversation partner is the back end on the same conversation. (Some books refer to the front end as the initiator and the back end as the recipient.) It is normally the front end that dominates, and determines the way the conversation goes. You can arrange for the back end to take over if you want, but, in a complex process, this can cause unnecessary complication. This is further explained in the discussion on synchronization later in this section.



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