2034 (07F2) (RC2034): MQRC_NO_MSG_UNDER_CURSOR


Explanation

An MQGET call was issued with either the MQGMO_MSG_UNDER_CURSOR or the MQGMO_BROWSE_MSG_UNDER_CURSOR option. However, the browse cursor is not positioned at a retrievable message. This is caused by one of the following:

  • The cursor is positioned logically before the first message (as it is before the first MQGET call with a browse option has been successfully performed).
  • The message the browse cursor was positioned on has been locked or removed from the queue (probably by some other application) since the browse operation was performed.
  • The message the browse cursor was positioned on has expired.


Completion code

MQCC_FAILED


Programmer response

Check the application logic. This may be an expected reason if the application design allows multiple servers to compete for messages after browsing. Consider also using the MQGMO_LOCK option with the preceding browse MQGET call.

Parent topic: API reason codes