MsgId, CorrelId, and UOWControl fields for DPL programs
If your non-CICS application is using the CICS-WebSphere MQ bridge to run a single DPL program, set the value of the MQCIH.UOWControl field to MQCUOWC_ONLY. However, if your application is sending and receiving multiple messages, you must set alternative options to handle units of work correctly.
- MQCUOWC_FIRST in the first request
- MQCUOWC_MIDDLE in any intermediate requests
- MQCUOWC_LAST in the last request
Your application can send multiple request messages in a unit of work before receiving any reply messages. At any time after the first message, you can stop the unit of work by sending a message with the MQCIH.UOWControl field set to MQCUOWC_COMMIT or MQCUOWC_BACKOUT.
The first message must specify MQMD.CorrelId = MQCI_NEW_SESSION and subsequent messages must set the MQMD.CorrelId field to the message id of the first message. When you are running more than one user DPL program using the CICS-WebSphere MQ bridge, the MsgId field in the request message is set by the queue manager (to M1 in the example shown here), and subsequently copied to the CorrelId field.
The following diagram summarizes the values to use and expect in key fields in the MQMD and MQCIH for typical CICS® DPL programs that you run using the CICS-WebSphere MQ bridge.
