How to run your business transaction request in asynchronous mode

At build time you need to take the following steps to run a business transaction request in asynchronous mode.

  1. The request type in the Properties file must be set to 0. This indicates that the request will run in asynchronous mode.
  2. The service requestor should not load data into the following fields of the MQMD Message Descriptor:
    • ReplyToQ
    • ReplyToQMgr
    These two fields control the WebSphere® MQ-CICS bridge program response. When you run your business transaction in asynchronous mode, the WebSphere MQ-CICS bridge cannot issue the resultant reply to the original request. This is accomplished directly from the Navigation Manager, run as DFHROOT within the BTS process.
  3. The service requestor must load the ReplyToQ and ReplyToQMgr in the DFHMAH message header.
  4. Optional: The service requestor can optionally load message ID MSGID and correlation ID CORRELID in the DFHMAH message header. By convention, the CORRELID of the reply message will contain the message ID of the request message.
If an error occurs before initiating a BTS process, the DPL stub program can also issue replies in asynchronous mode.