Processing modes

There are four different ways that a service flow request can be processed by CICS SFR. The processing mode of the service flow is set in service flow project tools, but can be overridden by the service requester when it invokes the service flow.

Each mode is a combination of the processing required by the service requester and the processing of the BTS activities that run the flow navigator and the server adapters.

Table 1. Processing modes
Mode name Mode number Service requester mode Activity mode
Asynchronous 0 Asynchronous Asynchronous
Link 4 Synchronous Synchronous using LINK ACTIVITY
Synchronous 1 Synchronous Synchronous
Synchronous roll back 2 Synchronous Synchronous with additional error processing

service flow project tools defaults to process requests in synchronous mode. The processing associated with each mode is as follows:

Asynchronous mode
The service requester must be a WebSphere MQ-enabled application that uses the WebSphere MQ-CICS bridge to invoke a service flow asynchronously. The CICS SFR interface program, DFHMADPL, initiates the BTS process to start the navigation manager asynchronously and returns to the bridge task. The bridge task also returns, committing the GET of the request message.
The navigation manager invokes the flow navigator and waits for it to complete its processing. The flow navigator runs all of the server adapters asynchronously and handles the completion events of the server adapters until all of the request processing is complete. The flow navigator returns to the navigation manager, which in turn reads any reply message from the flow navigator's output data-container, and puts the reply message on the queue specified in the REPLYTOQ field of the request message.
Link mode
The service requester invokes a service flow synchronously and DFHMADPL defines the BTS process for the navigation manager synchronously. The request processing is also synchronous, but the navigation manager and flow navigator use an EXEC CICS LINK ACTIVITY command for creating child activities.
Use Link mode if you have a large service flow with many server adapters. All of the activities run in the same unit of work, so there are fewer tasks for the service flow, but an error in any server adapter causes all of the updates to roll back to the state prior to the start of the failed request.
Synchronous mode
The service requester invokes a service flow synchronously and DFHMADPL defines the BTS process for the navigation manager synchronously. The navigation manager waits for the flow navigator and server adapter processing to complete before returning to DFHMADPL. DFHMADPL sends a response message to the service requester. When the BTS process completes, the unit of work is committed, even if there are system errors.
Synchronous roll back mode
This processing mode is the same as the synchronous mode with one exception. If a failure occurs in any activity within the BTS process, the unit of work is not committed. If an error occurs, all recoverable resources that are updated during the request processing are returned to the state prior to the start of the failed request. For example, if your service flow has a series of DPL requests that run as a single unit of work and are committed and if any one of the DPL requests is unsuccessful, the unit of work is not committed.


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