IBM MQ queue properties

None: No index is maintained. Use this when retrieving messages sequentially. This is the default.

Correl ID: An index of correlation identifiers is maintained. Use this when retrieving messages using the CorrelId field as a selection criterion on the MQGET call.

Message token: An index of message tokens is maintained.

For model queues, this property is editable; To specify that a permanent dynamic queue is created from this model queue, select Permanent dynamic (on z/OS, the dynamic queue has a disposition of Queue manager); to specify that a temporary dynamic queue is created, select Temporary dynamic (on z/OS, the dynamic queue has a disposition of Queue manager); on z/OS only, to specify that a permanent dynamic queue is created with a disposition of Shared, select Shared dynamic.

To configure the queue so that non-persistent messages are not automatically read ahead by the client, select No. This is the default value. Messages are not automatically read ahead by the client ahead of an application requesting them. Messages are only read ahead if requested by the client. A maximum of one non-persistent message might be lost if the client ends abnormally.

To disable read ahead at the queue level, select Disabled. Messages are not read ahead by the client ahead of an application requesting them, regardless of whether read ahead is requested by the client application.

(Only on Local queues, Alias queues, and Model queues)

To contain all the properties of the message, except those contained in the message descriptor (or extension), select All. The All value means that all properties of the message are included with the message when it is sent to the remote queue manager. The properties, except those properties in the message descriptor (or extension), are placed in one or more MQRFH2 headers in the message data.

To allow applications that expect JMS related properties to be in an MQRFH2 in the message data to continue to work unmodified, select Compatibility. This is the default value. Compatibility means that if the message contains a property with a prefix of mcd., jms., usr., or mqext. then all message properties are delivered to the application in an MQRFH2 header. Otherwise all properties of the message, except those contained in the message descriptor (or extension), are discarded and are no longer accessible to the application.

To ensure that properties are always returned in the message data in an MQRFH2 header, regardless of whether the application specifies a message handle, select Force MQRFH2. A valid message handle supplied in the MsgHandle field of the MQGMO structure on the MQGET call is ignored. Properties of the message are not accessible via the message handle.

To discard all the properties of a message, except those contained in the message descriptor (or extension), select None. This value prevents applications that do not support message properties from being affected by the inclusion of any property in a message.

V6COMPAT - MQRFH2 headers are not modified by the properties code. If message properties have been provided and are not contained in the original MQRFH2 headers, they are returned in a message handle or otherwise discarded. This behavior can be overridden by supplying one of the MQGMO_PROPERTIES options.

• CUSTOM('')
• CUSTOM('A(B)')
• CUSTOM('C(D) E(F)')
• CUSTOM('G(5000) H(''9.20.4.6(1415)'')')

The queue manager parses the value, but if the string cannot be parsed according to these rules, or if it contains properties or values that are not recognized, the queue manager ignores the errors.

The default is for all cluster-sender channels to transfer messages from a single cluster transmission queue, SYSTEM.CLUSTER.TRANSMIT.QUEUE. We can change the default for the queue manager, so that all cluster-sender channels transfer messages from separate transmission queues. The queue manager property is Default cluster transmission queue. The queue manager creates separate transmission queues automatically, when they are required. The queue manager does not set the Cluster channel name parameter

Set the Cluster channel names parameter to the name of a single cluster-sender channel, or to a generic name. A generic name associates multiple cluster-sender channels with this transmission queue. A generic name has wildcard characters, *, in any positions in the name. All cluster-sender channels that match the name transfer messages from this transmission queue and no other.

On z/OS, if this parameter is set, the queue must be shareable, be indexed by correlation ID, and must not be a dynamic or a shared queue.

Select Queue manager to use the value specified by the CLWL use queue property of the queue manager that the selected queue belongs to. This is the default value.

Select Any to use local and remote queues.

Select Local to use only local queues

For more information, see Distributed queuing and clusters.

This is the name of a process instance that identifies the application started by the queue manager when a trigger event occurs. The process does not have to be defined when the local queue is defined, but it must be available for a trigger event to occur.

We can configure IBM MQ to collect online monitoring data about the current performance of the queue. To inherit the value of the queue manager's Queue monitoring property (see Queue manager properties), select Queue manager. If the queue manager's Queue monitoring property is None, the queue's Queue monitoring property is ignored.

• To override the queue manager's settings and prevent data collection for this queue, select Off.
• To collect data at a low rate, select Low.
• To collect data at a medium rate, select Medium.
• To collect data at a high rate, select High.

For more information, see Monitor and performance.