Policy attributes: receive

Specify the attributes you require by typing them in the boxes, or selecting them from the drop-down lists provided.

Attribute Comments
Implicit Open The queue is opened implicitly (must be set to 'Yes' for the C high-level interface).
Leave Queue Open The queue is left open after use.
Delete On Close Dynamic queues are deleted when closed. 'Purge' causes deletion even if there are messages on the queue.
Wait Interval A period of time (in milliseconds) that the receive waits for a message to be available. The default is 'Unlimited'.
Wait Interval Read Only If set to 'No', an application can override the Wait Interval value in the policy object (using 'setWaitTime').
Convert The message is code page converted by the message transport.
Wait For Whole Group All messages in a group must be available before any message is returned by the receive.
Handle Poison Message Enables poison message handling (see note).
Accept Truncated Messages Truncated messages are accepted.
OpenShared The queue is opened as a shared queue.

Note: A poison message is one for which the count of the number of times it has been backed-out exceeds the maximum backout-limit specified by the underlying MQSeries transport queue object. If poison message handling is enabled during a receive request the AMI will handle it as follows:

If a poison message is successfully requeued to the backout-requeue queue (specified by the underlying MQSeries transport queue), the message is returned to the application with completion code MQCC_WARNING and reason code MQRC_BACKOUT_LIMIT_ERR.

If a poison message requeue attempt (as described above) is unsuccessful, the message is returned to the application with completion code MQCC_WARNING and reason code MQRC_BACKOUT_REQUEUE_ERR.

If a poison message is part of a message group (and not the only message in the group), no attempt is made to requeue the message. The message is returned to the application with completion code MQCC_WARNING and reason code MQRC_GROUP_BACKOUT_LIMIT_ERR.


(C) IBM Corporation 1999. All Rights Reserved