Reply processing pattern for complex service flows
When each server adapter completes normally, it stores the application response and its status in data-containers and returns control to the flow navigator.
Program link and Queue server adapters put status information in a COMMAND.STATUS data-container. FEPI and Link3270 server adapters put status information in a NAVIGATOR.STATUS data-container.
The flow navigator performs the following processing steps each time a
server adapter completes:
- Performs a check on the server adapter activity completion status by issuing the BTS CHECK ACTIVITY command.
- Reads the adapter state information from the ADAPTER.PROCESS data-container.
- Reads the server adapter status information from the appropriate data-container.
- Reads the appropriate server adapter output data-container, if it successfully completed.
If the service flow has completed processing successfully, the flow navigator
performs the following reply processing steps:
- Puts the application response data in the ADAPTER.OUTPUT data-container.
- Updates the data-container ADAPTER.STATUS to indicate that the service flow completed successfully.
- Issues an EXEC CICS RETURN ENDACTIVITY command, returning control to the navigation manager.
The navigation manager performs the following reply processing:
- Checks the flow navigator completion status by issuing the CHECK ACTIVITY command.
- Reads the state from the ADAPTER.PROCESS data-container.
- Reads the service flow status from the ADAPTER.STATUS data-container.
- Reads the service flow container from the ADAPTER.OUTPUT data-container, if the flow navigator completed successfully.
- Puts the application response in the root activity data-container. This data-container is also called ADAPTER.OUTPUT.
- Writes adapter completion status and state information to data-container ADAPTER.PROCESS.
- Optionally issues an MQPUT command if the client application interface is WebSphere® MQ-CICS bridge. Otherwise, the navigation manager issues an EXEC CICS RETURN ENDACTIVITY command, returning control to the CICS SFR interface program DFHMADPL and completing the process.
The CICS SFR interface
program performs the following processing steps:
- Performs a check on the process completion status by issuing the CHECK ACQPROCESS command.
- Reads the state information from data-container ADAPTER.PROCESS.
- Reads the navigation manager output data-container ADAPTER.OUTPUT.
- Builds a reply message, including the application response data.
- Moves the outbound reply message to a COMMAREA or container and issues an EXEC CICS RETURN command, returning control to the service requester.