Invoking a service flow using a CICS-supplied interface

You can use the External Call Interface (ECI), External CICS® Interface (EXCI), or Distributed Program Link (DPL), potentially with CICS Transaction Gateway (CTG) or a distributed version of CICS, to invoke a service flow. When you use a CICS-supplied interface, the request can be processed only in synchronous mode.

About this task

To invoke a service flow using a CICS-supplied interface, follow these steps:

Procedure

  1. Select the interface that is appropriate for your service requester.
    1. To use CTG to invoke the service flow, use the ECI interface. If CTG is installed on z/OS®, the EXCI interface is used.
    2. To use DPL, use the EXEC CICS LINK command to link from the service requester to the CICS SFR interface program with a request message. If you use DPL, you can use a channel and containers to pass the request message, rather than a COMMAREA.
  2. Decide on the data conversion that is required. It might be necessary to perform data conversion in the CICS Service Flow Runtime routing region, using a customized version of the standard CICS conversion table DFHCNV. For details, see Data conversion.
  3. Decide how you want to send the request message from the service requester to invoke the service flow. The service requester can send the message in a COMMAREA or, if you are using a PROGRAM LINK command, a channel and set of containers. The service requester then waits for a response if required.
  4. When the service flow has completed its processing of the request message, the CICS SFR interface program passes the response message back to the service requester. The CICS-supplied interface requires a response, but the request message might not require an application reply.

Results



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