The default log size is tiny 48MB and isn't really intended for a production deployment involving persistent messages. It's a bit historical and MQ tries not to change defaults in order not to spring any surprises on someone expecting the "old" behaviour.
While you can simply increase the number of extents it's a bit more difficult to increase the extent size (a bigger extent size would be preferable).
The transaction has already been backed out, and any messages locked to the transaction (by a destructive MQGET) released, but the transaction has not been "closed" and an MQBACK needs to be issued on the hConn that started this transaction before it can start a new transaction.
LOGINUSE is a point in time thing, and LOGUTIL represent a more general estimate of log space usage (as per the documentation).
------------------------------
Andrew Hickson
------------------------------
Original Message:
Sent: Fri May 20, 2022 04:54 PM
From: Jim Creasman
Subject: Understanding MQ log file size.
During a load test exercise one of our consumer clients reported the following error:
MQError: CMIT: MQCC = MQCC_FAILED [2] MQRC = MQRC_BACKED_OUT [2003]
In our case the error came from issuing a CMIT command to close out a transaction begun with GET. I have several questions as I work through understanding this, and what actions we should take.
Thanks,
Jim
------------------------------
Jim Creasman
------------------------------