Use sync point coordination in a client application

An application running on the base client can issue MQCMIT and MQBACK, but the scope of the sync point control is limited to the MQI resources. We can use an external transaction manager with an extended transactional client.

Within IBM MQ, one of the roles of the queue manager is sync point control within an application. If an application runs on an IBM MQ base client, it can issue MQCMIT and MQBACK, but the scope of the sync point control is limited to the MQI resources. The IBM MQ verb MQBEGIN is not valid in a base client environment.

Applications running in the full queue manager environment on the server can coordinate multiple resources (for example databases) via a transaction monitor. On the server we can use the Transaction Monitor supplied with IBM MQ products, or another transaction monitor such as CICS . We cannot use a transaction monitor with a base client application.

We can use an external transaction manager with an IBM MQ extended transactional client. See What is an extended transactional client? for details.