MQSeries.net :: View topic

kristinneibuhr@bc.com · Posted: Fri Mar 11, 2005 9:32 am Post subject:

Getting this error when putting messages from a windows 2k server to mainframe s/390.
We are trying to send over 60,000 records from the local win2k server to the mainframe. The mainframe limit is set at 60,000 and our mainframe support said they had changed this to 90,000.
Here is what the mainframe help files are telling me. I passed this along to our mainframe systems programmer, who tells me he has done what the corrective action suggests. However, something is still missing since I got the same error on the 2k server last night.
(Our mainframe guy was thrown into supporting MQSeries out of necessity and has no background in supporting MQSeries.)
I think he's missed something but don't know what. Any help would be GREATLY appreciated.

An MQGET, MQPUT, or MQPUT1 call failed because it
would have caused the number of uncommitted messages
in the current unit of work to exceed the limit
defined for the queue manager (see the MaxUncommittedMsgs queue-manager attribute). The
number of uncommitted messages is the sum of the
following since the start of the current unit of work:

t Messages put by the application with the
MQPMO_SYNCPOINT option

t Messages retrieved by the application with the
MQGMO_SYNCPOINT option

t Trigger messages and COA report messages generated
by the queue manager for messages put with the
MQPMO_SYNCPOINT option

t COD report messages generated by the queue manager for messages retrieved with the MQGMO_SYNCPOINT
option

Corrective action: Check whether the application is
looping. If it is not, consider reducing the
complexity of the application. Alternatively,
increase the queue-manager limit for the maximum
number of uncommitted messages within a unit of work.

t On OS/390, the limit for the maximum number of
uncommitted messages can be changed by using the
DEFINE MAXSMSGS command.