Home

 

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:

    • If the cluster queue is opened for inquire plus one or more of input, browse, or set, there must be a local instance of the cluster queue for the open to succeed. In this case the attributes that can be inquired are those valid for local queues.

    • If the cluster queue is opened for inquire alone, or inquire and output, only the attributes listed below can be inquired; the QType attribute has the value MQQT_CLUSTER in this case:

      • MQCA_Q_DESC

      • MQCA_Q_NAME

      • MQIA_DEF_BIND

      • MQIA_DEF_PERSISTENCE

      • MQIA_DEF_PRIORITY

      • MQIA_INHIBIT_PUT

      • MQIA_Q_TYPE

      If the cluster queue is opened with no fixed binding (that is, MQOO_BIND_NOT_FIXED specified on the MQOPEN call, or MQOO_BIND_AS_Q_DEF specified when the DefBind attribute has the value MQBND_BIND_NOT_FIXED), successive MQINQ calls for the queue might inquire different instances of the cluster queue, although usually all the instances have the same attribute values.

    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:




 

Home