Doubts about transactions

[zeconslab]

Is there any focus on transactions within the examples?

I have researched and I understand that to use the approach it is necessary to create several connections (I have no problem with this), what happens is that when creating different clients and opening the queues, at the time of performing a rollback in 1 queue it ends up affecting the other queues

Does anyone have a solution or example that can help me understand better?

• MQ 9.2, GO 1.23

[ibmmqmet]

https://www.ibm.com/docs/en/ibm-mq/9.4?topic=queuing-committing-backing-out-units-work is documentation describing MQ's transaction models. It's essentially the same regardless of application language. As I said before, local (one-phase) transactions are scoped to the hConn.

XA, two-phase, transactions have further rules on who can participate and how.

In this repo, the amqsbo.go sample is one that does some work with transactions. And in the MQ product itself, you'll find a bunch of samples in different languages that use MQCMIT/MQBACK or equivalent. Since the model is the same, it would be trivial to apply that knowledge to a Go program.