Reply processing pattern for a simple service flow

When a Link3270 or FEPI server adapter completes its processing, the application response is stored in a data-container called ADAPTER.OUTPUT. The status of the server adapter processing is also stored in a data-container called ADAPTER.STATUS.

After the server adapter has completed processing and the service flow activity has ended normally, a BTS completion event returns control to the navigation manager, DFHMAMGR. The navigation manager performs the following processing steps:
  1. Performs a check on the server adapter activity completion status by issuing the CHECK ACTIVITY command:
    EXEC CICS CHECK ACTIVITY (ADC-NAV-ACTIVITY)
                  COMPSTATUS (CICS-COMPSTATUS)
                      ABCODE (CICS-ABCODE)
                   ABPROGRAM (CICS-ABPROGRAM) 
                        MODE (CICS-MODE) 
                  SUSPSTATUS (CICS-SUSPSTATUS) 
                        RESP (CICS-RESP) 
                       RESP2 (CICS-RESP2) 
    END-EXEC. 
  2. Reads the appropriate server adapter status information from data-container ADAPTER.STATUS. If the server adapter completed successfully, the navigation manager reads the output container ADAPTER.OUTPUT.
  3. Writes the root activity output data-container containing the application response or reply data. The output container name is ADAPTER.OUTPUT.
  4. Writes adapter completion status and state information to process container ADAPTER.PROCESS.

After the Navigation Manager has completed processing and the BTS process has ended normally, a BTS completion event returns control to DFHMADPL.

DFHMADPL performs the following processing steps:
  1. Performs a check on the process completion status by issuing the CHECK ACQPROCESS command.
  2. Reads the adapter state information from process container ADAPTER.PROCESS
  3. Reads the output data-container ADAPTER.OUTPUT.
  4. Builds a reply message that includes any output application data and sends it to the service requester.

    DFHMADPL can invoke a user-defined program to convert the application data to XML. The used-defined program name is determined by the service flow. DFHMADPL then calls the COBOL to XML converter program, DFHMAXMO, to convert the COBOL header structure (DFHMAH) to XML, to format the XML reply message.



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