Processing patterns for a passthrough reply

Upon passthrough processing completion, any application response/reply data is written to the Link3270 Passthrough Manager activity's output data container ADAPTER.OUTPUT.

The Link3270 Passthrough Manager activity status information is written to the status container ADAPTER.STATUS.

Once passthrough processing has completed processing and the Link3270 Passthrough Manager BTS activity has ended normally, a BTS completion event is fired and control is returned to the Navigation Manager (DFHMAMGR).

The Navigation Manager will perform the following reply processing steps:
  1. Performs a check on the Link3270 Passthrough Manager activity completion status by issuing the BTS 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 adapter state information from process container ADAPTER.PROCESS.
  3. Reads the Link3270 Passthrough Manager activity status information from container ADAPTER.STATUS.
  4. Reads the Link3270 Passthrough Manager activity output container, if normal completion, from container ADAPTER.OUTPUT.
  5. Writes the root activity output data container containing the application response/reply data. The output container name is ADAPTER.OUTPUT.
  6. Writes adapter completion status and state information to process container ADAPTER.PROCESS.
  7. Issues an EXEC CICS RETURN ENDACTIVITY command returning control to the DPL Passthrough Stub program (DFHMADPP) and completing the process.
Once the Navigation Manager (DFHMAMGR) has completed processing and the BTS process has ended normally, a BTS completion event is fired and control is returned to the DPL Passthrough Stub program (DFHMADPP). The DPL stub will perform the following processing steps:
  1. Performs a check on the process completion status by issuing the BTS CHECK ACQPROCESS command.
  2. Reads the state information from process container ADAPTER.PROCESS.
  3. Reads the Navigation Manager (DFHMAMGR) output data container ADAPTER.OUTPUT.
  4. Builds XML or fixed format reply message to include the header structure (DFHMAH) and any output data container application response/reply data.
    Note: The DPL Passthrough Stub program (DFHMADPP) calls the ADS to XML Converter program (DFHMAXPI) to convert the COBOL fixed format outbound application reply structure to XML application reply tag data. The outbound application reply structure in passthrough mode includes the screen header (CIA-SCREEN-HEADER) and map header (CIA-MAP-HEADER) structures.

    The DPL Passthrough Stub program will then call the COBOL to XML Converter program (DFHMAXMO) to convert the COBOL fixed format header structures (DFHMAH and DFHMAH2) to XML header tag data to format the XML reply message.

    See XML request and response processing for passthrough and XML message formats for passthrough requests for further information.

  5. Moves outbound reply message to DFHCOMMAREA and issues an EXEC CICS RETURN command returning control to the service requestor.