The system as a terminal

Because the resource definitions for APPC devices can take the CONNECTION and SESSIONS form, it is easy to confuse them with the definitions for the intersystem links.

It is important to remember that definitions for the intersystem links are either direct or indirect, while those for APPC devices are direct in the TOR and remote in the AOR and any intermediate systems. Note also that remote CONNECTION definitions do not need corresponding SESSIONS definitions.

Figure 1 shows a network of three CICS systems chained together, of which the first is linked to an APPC terminal.
Figure 1. Transaction routing to an APPC terminal across daisy-chained systems
The picture shows an APPC terminal or system, A, and three CICS regions, B, C, and D. B is a TOR, C an intermediate system, and D an AOR. There is a direct link between A and B, between B and C, and between C and D. B has defined an indirect link to D via C. D has defined an indirect link to B via C. C and D both have a remote definition for A. On the AOR, D, a transaction is defined as local . On the intermediate region, C, the same transaction is defined as owned by D. On the TOR, B, it is defined as owned by C.
Note:
  1. The remote link definitions for A could either be defined by the user or be shipped from system B during transaction routing.
  2. The indirect links are not necessary to this example, but are included to complete all possible linkage combinations. See Defining indirect links for transaction routing.
  3. The links B-C and C-D may be either MRO or APPC.
System A (or any one of the four systems) can take on the role of a terminal. This is a technique that allows a pair of transactions to converse across intermediate systems. Consider this sequence of events:
  1. A transaction running in A allocates a session on the link to B and makes an attach request for a particular transaction.
  2. B sees that the transaction is on C, and initiates the relay program in conjunction with the principal facility represented by the link definition to A.
  3. The attach request arrives at C together with details of the terminal; that is, B's link to A. C builds a remote definition of the terminal and goes to attach the transaction.
  4. C also finds the transaction remote and defined as owned by D. C initiates the relay program, which tries to attach the transaction in D.
  5. D also builds a remote definition of B's link to A, and attaches the local transaction.
  6. The transaction in A that originated the attach request can now communicate with the target transaction through the transaction routing mechanism.
Note these points:
  • APPC terminals are always shippable. There is no need to define them as such.
  • Attach requests on other sessions of the A-B link could be routed to other systems.
  • Neither partner to a conversation made possible by transaction routing knows where the other resides, although the routed-to transaction can find out the TERMINAL/CONNECTION name by using the EXEC CICS ASSIGN PRINSYSID command. This name can be used to allocate one or more additional sessions back to A.
  • The transaction in D could start with an EXEC CICS (GDS) EXTRACT PROCESS command, but it is more usual for the transaction to start with an EXEC CICS (GDS) RECEIVE command.


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