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 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 56 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 in order 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 QTCLUS in this case:

     • CAQD

     • CAQN

     • IADBND

     • IADPER

     • IADPRI

     • IAIPUT

     • IAQTYP

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

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

5. If a number of attributes are to be inquired, and subsequently some of them are to be set using the MQSET call, it may be convenient to position at the beginning of the selector arrays the attributes that are to be set, 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 CMPCOD parameter), the reason code returned is the first one in the following list that applies:

   1. RC2068

   2. RC2022

   3. RC2008

7. For more information about object attributes, see:

   • Attributes for queues

   • Attributes for namelists

   • Attributes for process definitions

   • Attributes for the queue manager

8. A new local queue SYSTEM.ADMIN.COMMAND.EVENT is used for queuing messages that are generated whenever commands are issued. Messages are put onto this queue for most commands, depending on how the CMDEV queue manager attribute is set:

   • ENABLED -- command event messages are generated and put onto the queue for all successful commands.

   • NODISPLAY -- command event messages are generated and put onto the queue for all successful commands other than the DISPLAY (MQSC) command, and the Inquire (PCF) command.

   • DISABLED -- command event messages are not generated (this is the queue manager's initial default value).