Queue status attributes
The status attributes of queues and handles that are accessing the queues.
For each attribute, there is a brief description of what information the attribute shows. The table also gives the equivalent MQSC parameter for the DISPLAY QSTATUS command. For more information about MQSC commands, see Administration using MQSC commands.
Attribute | Meaning | MQSC parameter |
---|---|---|
Queue name | The name of the queue. | |
Current queue depth | The number of messages currently on the queue. | CURDEPTH |
Open input count | This is the number of applications that are currently connected to the queue to get messages from the queue. | IPPROCS |
Open output count | This is the number of applications that are currently connected to the queue to put messages on the queue. | OPPROCS |
Uncommitted messages | This indicates whether there are any uncommitted changes (puts and gets) pending for the queue. If there are uncommitted changes pending, the value is a number corresponding to the number of uncommitted messages that there are pending (1, 2, 3, 4, 5, etc). If there are no uncommitted changes pending, the value is No. For z/OS shared queues, the value applies only to the queue manager that is generating the reply. The value does not apply to all of the queue managers in the queue sharing group. | UNCOM |
Media recovery log extent name | The name of the oldest log extent required by the queue to perform media recovery. | MEDIALOG |
Queue monitoring | The log extent or journal receiver needed for media recovery of the queue. On queue managers on which circular logging is in place, this attribute has no value. This attribute is valid on UNIX, Linux, and Windows. | MONQ |
Queue time | The interval, in microseconds, between messages being put on the queue and then being
destructively read. The maximum displayable value is 999 999 999; if the interval exceeds this
value, 999 999 999 is displayed. The interval is measured from the time that the message is placed
on the queue until it is destructively retrieved by an application and includes the following times:
The cell displays two values: a value based on recent activity over a short period of time, and a value based on activity over a longer period of time. These values depend on the configuration and behavior of our system and the levels of activity within it, and serve as an indicator that your system is performing normally. A significant variation in these values might indicate a problem with the system. For z/OS queues that have the disposition Shared, the value shown is for measurements collected on this queue manager only. |
QTIME |
Oldest message age | The age, in seconds, of the oldest message on the queue. | MSGAGE |
Last put date | The date on which the last message was put to the queue since the queue manager started. When no put date is available, perhaps because no message has been put to the queue since the queue manager was started, the value is shown as a blank. For z/OS queues that have the disposition Shared, the value shown is for measurements collected on this queue manager only. | LPUTDATE |
Last put time | The time at which the last message was put to the queue since the queue manager started. When no put time is available, perhaps because no message has been put to the queue since the queue manager was started, the value is shown as a blank. For z/OS queues that have the disposition Shared, the value shown is for measurements collected on this queue manager only. | LPUTTIME |
Last get date | The date on which the last message was retrieved from the queue since the queue manager started. A message being browsed does not count as a message being retrieved. When no get date is available, perhaps because no message has been retrieved from the queue since the queue manager was started, the value is shown as a blank. For z/OS queues that have the disposition Shared, the value shown is for measurements collected on this queue manager only. | LGETDATE |
Last get time | The time at which the last message was retrieved from the queue since the queue manager started. A message being browsed does not count as a message being retrieved. When no get time is available, perhaps because no message has been retrieved from the queue since the queue manager was started, the value is shown as a blank. For z/OS queues that have the disposition Shared, the value shown is for measurements collected on this queue manager only. | LGETTIME |
Current file size | The current size of the file used by this queue (in megabytes). | CURFSIZE |
Current maximum file size | The maximum size that the queue file is currently able to grow to (in megabytes). This value can be lower than the configured value of MAXFSIZE if the queue file has not yet been reconfigured by the queue manager to support larger files. | CURMAXFS |
Queue handle status objects
The following table lists the queue handle status attributes, which are shown in the second table in the Queue status dialog.
Attribute | Meaning | MQSC parameter |
---|---|---|
Queue name | The name of the queue. | |
Application name | A string containing the tag of the application connected to
the queue manager. It is one of the following:
The application name represents the name of the process or job that has connected to the queue manager. In the instance that this process or job is connected through a channel, the application name represents the remote process or job rather than the local channel process or job name. |
APPLTAG |
Process ID | The identifier of the process that opened the queue. This attribute is not valid on HP Integrity NonStop Server and z/OS. | PID |
Thread ID | The identifier of the thread within the application process that has opened the queue. An asterisk indicates that this queue was opened with a shared connection. This attribute is not valid on HP Integrity NonStop Server and z/OS. | TID |
Application type | A string indicating the type of the application that is connected to the queue manager. Batch means an application using a batch connection; RRSBATCH means an RRS-coordinated application using a batch connection; CICS means a CICS transaction; IMS means an IMS transaction; CHINIT means a channel initiator; System means a queue manager; User means a user application. | APPLTYPE |
Application description | A string containing a description of the application, where it is known, connected to the queue manager. If the application is not recognized by the queue manager the description returned consists of blanks. The application description is filterable (for example with a WHERE clause) to allow an administrator to display only certain connections. | APPLDESC |
Browse access | This indicates whether the handle is providing browse access to the queue. If the handle is providing browse access, the value is Yes; if the handle is not providing browse access, the value is No. | BROWSE |
Inquire access | This indicates whether the handle is providing inquire access to the queue. If the handle is providing inquire access, the value is Yes; if the handle is not providing inquire access, the value is No. | INQUIRE |
Input access | This indicates whether the handle is providing input access to the queue. No means that the queue is not open for input; Shared means that the queue is open for shared input; Exclusive means that the queue is open for exclusive input. | INPUT |
Output access | This indicates whether the handle is providing output access to the queue. If the handle is providing output access, the value is Yes; if the handle is not providing output access, the value is No. | OUTPUT |
Set access | This indicates whether the handle is providing set access to the queue. If the handle is providing set access, the value is Yes; if the handle is not providing set access, the value is No. | SET |
User ID | The user identifier that is associated with the handle. | USERID |
Channel name | The name of the channel that owns the handle. If there is no channel associated with the handle, this value is empty. This value is shown only when the handle belongs to the channel initiator. | CHANNEL |
Connection name | The connection name that is associated with the channel that owns the handle. If there is no channel associated with the handle, this value is empty. This value is shown only when the handle belongs to the channel initiator. | CONNAME |
Unit of work type | The type of unit of recovery as seen by the queue manager. It is one of the following: CICS (z/OS only); XA; RRS (z/OS only); IMS (z/OS only); Queue manager. | URTYPE |
Queue manager unit of work ID | The unit of recovery assigned by the queue manager. This is an 8 byte transaction identifier, displayed as 16 hexadecimal characters. On z/OS, this is an 8 byte log RBA, displayed as 16 hexadecimal characters. | QMURID |
Asynchronous state | The state of the asynchronous consumer on this object handle. There are five
possible values:
Active: An MQCB call has set up a function to call-back to process messages asynchronously and the connection handle has been started so that asynchronous message consumption can proceed. Inactive: An MQCB call has set up a function to call-back to process messages asynchronously but the connection handle has not yet been started, or has been stopped or suspended, so that asynchronous message consumption cannot currently proceed.Suspended: The asynchronous consumption call-back has been suspended so that asynchronous message consumption cannot currently proceed on this object handle. This can be either because an MQCB call with Operation MQOP_SUSPEND has been issued against this object handle by the application, or because it has been suspended by the system. If it has been suspended by the system, as part of the process of suspending asynchronous message consumption the call-back function is called with the reason code that describes the problem resulting in suspension. This is reported in the Reason field in the MQCBC structure that is passed to the call-back function. For asynchronous message consumption to proceed, the application must issue an MQCB call with the Operation parameter set to MQOP_RESUME. |
ASTATE |
Susptemp: The asynchronous consumption call-back has been
temporarily suspended by the system so that asynchronous message consumption cannot currently
proceed on this object handle. As part of the process of suspending asynchronous message
consumption, the call-back function is called with the reason code that describes the problem
resulting in suspension. This is reported in the Reason field in the MQCBC
structure passed to the call-back function. The call-back function is called again when asynchronous
message consumption is resumed by the system, when the temporary condition has been
resolved.
None: An MQCB call has not been issued against this handle, so no asynchronous message consumption is configured on this handle. This is the default value. |
||
External unit of work ID | The external unit of recovery identifier associated with the connection. It is the recovery identifier known in the external sync point coordinator. Its format is determined by the value of the Unit Of Work type attribute. | URID |
Address-space ID | A 4-character address-space identifier of the application that is identified by the Application name attribute. It distinguishes duplicate values of Application name. This value is displayed only when the queue manager that owns the queue is running on z/OS, and the Application type attribute does not have the value System. | ASID |
Program specification block name | The 8-character name of the program specification block (PSB) associated with the running IMS transaction (z/OS only). We can use the Program specification block name and Program specification table ID attributes to purge the transaction using IMS commands. A value is displayed only when the Application type attribute has the value IMS. | PSBNAME |
Program specification table ID | The 4-character IMS program specification table (PST) region identifier for the connected IMS region (z/OS only). A value is displayed only when the App type attribute has the value IMS. | PSTID |
CICS transaction ID | A 4-character CICS transaction identifier (z/OS only). A value is displayed only when the App type attribute has the value CICS. | TRANSID |
Related concepts
Related tasks