Usage notes

  1. The values returned are a snapshot of the selected attributes. There is no guarantee that the attributes will not change before the application can act upon the returned values.
  2. When you open a model queue, a dynamic local queue is created. This is true even if you open the model queue to inquire about its attributes.

    The attributes of the dynamic queue (with certain exceptions) are the same as those of the model queue at the time that the dynamic queue is created. If you subsequently use the MQINQ call on this queue, the queue manager returns the attributes of the dynamic queue, and not those of the model queue. See Table 82 for details of which attributes of the model queue are inherited by the dynamic queue.

  3. If the object being inquired is an alias queue, the attribute values returned by the MQINQ call are those of the alias queue, and not those of the base queue to which the alias resolves.
  4. If the object being inquired is a cluster queue, the attributes that can be inquired depend on how the queue is opened:

    For more information about cluster queues, refer to WebSphere MQ Queue Manager Clusters.

  5. If you want to inquire a number of attributes, and subsequently set some of them using the MQSET call, you might want to position the attributes to be set at the beginning of the selector arrays, so that the same arrays (with reduced counts) can be used for MQSET.
  6. If more than one of the warning situations arise (see the CompCode parameter), the reason code returned is the first one in the following list that applies:
    1. MQRC_SELECTOR_NOT_FOR_TYPE
    2. MQRC_INT_ATTR_COUNT_TOO_SMALL
    3. MQRC_CHAR_ATTRS_TOO_SHORT
  7. For more information about object attributes, see: