Transaction routing

Stabilized feature: Service Flow Runtime and Service Flow Modeler capability in IBM Developer for z/OS 14.2.3 are stabilized. Consider exposing and orchestrating applications as API services by using z/OS Connect Enterprise Edition or CICS® web services, or by writing web applications in Java or Node.js. See also Stabilization notices and discontinued functions.

Link3270 server adapters support both dynamic transaction routing and transaction routing. You can define the target CICS application transactions as remote or they can be dynamically routed to remote regions using the CICS dynamic transaction routing facility.

The Link3270 server adapter uses the Link3270 bridge mechanism to run 3270 transactions by linking to the DFHL3270 program and passing a COMMAREA that identifies the transaction to run and the data used by the target CICS application.

The Link3270 server adapter performs the following steps:

  1. Runs terminate processing in the current target CICS region, with the bridge facility allocated.
  2. Deallocates the currently allocated bridge facility.
  3. Allocates a new bridge facility in the target CICS region
  4. Runs request processing where the transaction is either a remote CICS system name with a remote name of CMAI, or the local CICS system name with a program name of DFHMALIN in the target CICS region.
  5. Runs the target CICS application transaction routed to the target CICS region.

For further information regarding CICS function request shipping (transaction routing method), see CICS function shipping. For programming information about the dynamic transaction routing program, see Writing a dynamic routing program.

For further information about the Link3270 bridge mechanism and its support for these types of intercommunication methods, see Developing for external interfaces and Administering the Link3270 bridge.