Structures of 3270 reply messages (outbound) using the CICS-WebSphere MQ bridge

These examples show the possible structures of reply messages sent by the CICS-WebSphere MQ bridge on behalf of 3270 transactions to non-CICS applications, known as outbound messages.

Outbound messages from the CICS-WebSphere MQ bridge have one of three structures, depending on whether an error occurred. Although only a single vector is shown in each of these examples, messages can contain several concatenated vectors, except when an error occurs.
  • This structure is used when CICS-WebSphere MQ bridge processing concludes normally, no errors were detected, and no data is to be returned to the non-CICS application:
    -------------------------------
    | MQMD | MQCIH |
    BRMQ structure
    |
    -------------------------------
    
    Even a CICS application abend is regarded as normal completion by the CICS-WebSphere MQ bridge. The abend code issued by the CICS application is given in the MQCIH.
  • This structure is used when CICS-WebSphere MQ bridge processing concludes normally, no errors were detected, and data is to be returned to the non-CICS application:
    --------------------------------------
    | MQMD | MQCIH |
    BRMQ structure
    |
    data
    |
    --------------------------------------
    
    BRMQ structure represents any of the architected outbound reply or request vector structures.
  • This structure is used when CICS-WebSphere MQ bridge processing concludes abnormally, after an error was detected by the CICS-WebSphere MQ bridge monitor:
    ------------------------------
    | MQMD | MQCIH |
    DFHMQ* message
    |
    ------------------------------
    
    DFHMQ* message represents an error message that indicates the error type. The value of field MQCIH.Format is set to MQFMT_STRING, to ensure that the message can be properly converted if the final destination uses a different CCSID and encoding. The MQCIH also contains other fields that you can use to diagnose the problem.

For CICS transactions that issue explicit syncpoint or rollback requests, the CICS-WebSphere MQ bridge also generates an additional message on the reply queue, showing the result of the syncpoint in the TaskEndStatus field in the MQCIH. This extra message is sent with an MQMD MsgType of MQMT_DATAGRAM. No input from the application is expected and the additional message is followed by the normal task end message.



fg15560_.html | Timestamp icon Last updated: Monday, 5 June 2017