Example 7. IMS-to-IMS application routing with MFS

The following figure can be understood in two contexts based upon an understanding of previous examples—the case shown in which ISC edit is used to edit the input in IMSB or the case in which MFS DPM-Bn is used to edit the input in IMSB.

Figure 1. ISC example for IMS-to-IMS application routing with MFS
Message flows from terminal to MID in IMS A Control Region, to TRANX in IMS A MPP Region, to ISCE in IMS B Control Region, to TRANY in IMS B MPP, to MOD in IMS A Control Region, and back to terminal.
Example 7 emphasizes several points:
  • Terminal T is completely handled by the front-end subsystem. Therefore, in this example, Terminal T can be held in response mode with IMSA.
  • The data sent from IMSA is inserted (ISRT) by an alternate PCB and is asynchronous to the response mode transaction.
  • IMSA could be connected to many IMS subsystems and, based on the input transaction, route the ISC traffic to the appropriate back-end IMSB.
  • The MPP in IMSA can provide any required message routing information, such as selecting the appropriate back-end subsystem through an ISRT to an alternate PCB.
  • MFS can be used in either or both subsystems to provide data stream formatting and routing.