get next considerations for WebSphere® MQ message queues

In WebSphere® MQ message queues, the get next statement reads the first record in the queue.

When a get next statement reads from a message queue, the first record in the queue is read into the MQRecord variable. This placement occurs because the get next invokes one or more WebSphere® MQ API calls:

  • MQCONN connects the generated code to the default queue manager and is invoked when no connection is active.
  • MQOPEN establishes a connection to the queue and is invoked when a connection is active but the queue is not open.
  • MQGET removes the record from the queue and is always invoked unless an error occurred in an earlier WebSphere® MQ call.