The status attributes of multiplatform queue managers, and
z/OS® queue managers.
![[UNIX, Linux, Windows, IBM i]](./ngmulti.gif)
Multiplatform queue manager status attributes
The following table lists the status attributes of multiplatform queue managers, and gives the
equivalent MQSC parameter for the DISPLAY QMSTATUS command. For more
information about MQSC commands, see Administration using MQSC commands in IBM® Knowledge Center.
Table 1. Multiplatform queue manager status attributes
Attribute |
Meaning |
MQSC parameter |
Queue manager name |
The name of the queue manager. |
|
Queue manager status |
The status of the queue manager, which can be: Starting ,
Running , or Quiescing . |
STATUS |
Connection count |
The current number of connections to the queue manager. |
CONNS |
Channel initiator status |
The status of the channel initiator, which can be: Stopped ,
Starting , Running , or Stopping . |
CHINIT |
Command server status |
The status of the command server, which can be: Stopped ,
Starting , Running , or Stopping . |
CMDSERV |
Installation description |
Description of the installation associated with the queue manager. |
|
Installation name |
Name of the installation associated with the queue manager. |
|
Installation path |
Path of the installation associated with the queue manager. |
|
Archive log extent name |
Name of the oldest log extent for which the queue manager is waiting for archive
notification. |
ARCHLOG |
Archive size |
The amount of space occupied, in megabytes, by log extents no longer required for restart or
media recovery, but waiting to be archived. |
ARCHSZ |
Current log extent name |
The name of the log extent that is being written to at the time that you open the status
dialog. |
CURRLOG |
Log in use |
The percentage of the primary log space in use for restart recovery at this point in
time. |
LOGINUSE |
Log utilization |
A percentage estimate of how well the queue manager workload is contained within the primary
log space. |
LOGUTIL |
Restart recovery log extent name |
The name of the oldest log extent required by the queue manager to perform restart
recovery. |
RECLOG |
Media recovery log extent name |
The name of the oldest log extent required by the queue manager to perform media
recovery. |
MEDIALOG |
Media size |
Size of the log data required for media recovery in megabytes. |
MEDIASZ |
Restart recovery size |
Size of the log data required for restart recovery in megabytes. |
RECSZ |
Reuse size |
The amount of space occupied, in megabytes, by log extents available to be reused. |
REUSESZ |
Log path |
The path of the queue manager event log. The path is of this format:
installationlocation\WebSphere MQ\log\queuemanager\active\
where installationlocation is the location where IBM MQ is installed, and queuemanager is the
name of the queue manager. |
LOGPATH |
Start date |
The date on which the queue manager was started. |
STARTDA |
Start time |
The time at which the queue manager was started. |
STARTTI |
![[z/OS]](./ngzos.gif)
z/OS queue manager status attributes
Channel initiator
The following table lists the channel initiator status attributes of
z/OS queue managers. The equivalent MQSC command is DISPLAY
CHINIT.
For more information about MQSC commands, see Administration using MQSC commands in IBM Knowledge Center.
Table 2. Channel initiator status attributes of z/OS
queue managers.
Attribute |
Meaning |
TCP name |
The TCP system name. |
Active adapters |
The number of active adapter subtasks. |
Active adapters requested |
The requested number of adapter subtasks. |
Active dispatchers |
The number of active dispatchers. |
Active dispatchers requested |
The requested number of dispatchers. |
Active SSL tasks |
The number of active TLS server subtasks. |
Active SSL tasks requested |
The requested number of TLS server subtasks. |
Current® channel connections |
The number of current channel connections. |
Channel connections requested |
The requested number of channel connections. |
Current TCP/IP channels |
The number of current TCP/IP channel connections. |
Current LU6.2 channels |
The number of current LU6.2 channel connections. |
Active channel connections |
The number of active channel connections. |
Active channel connections requested |
The requested number of active channel connections |
Active channels paused |
The number of active channel connections that have been paused, waiting to become active,
because the limit for active channels has been reached. |
Active channels started |
The number of active channel connections that have started. |
Active channels stopped |
The number of active channel connections that have stopped, requiring manual
intervention. |
Active channels retrying |
The number of active channel connections that are attempting to reconnect following a
temporary error. |
Channel initiator status |
The status of the channel initiator, which can be: Stopped ,
Starting , Running , or Stopping . |
Log
The following table lists the log status attributes of
z/OS queue managers. The equivalent MQSC command is DISPLAY
LOG.
For more information about MQSC commands, see Administration using MQSC commands in IBM Knowledge Center.
Table 3. Log status attributes of z/OS queue
managers.
Attribute |
Meaning |
Parameter type |
This attribute shows which type of information is displayed in the table. |
Queue manager start time |
The time that the queue manager was started. |
Queue manager start date |
The date on which the queue manager was started. |
RBA of queue manager start |
The Relative Byte Address (RBA) from which logging began when the queue manager was started.
|
RBA of log |
The Relative Byte Address (RBA) of the most recently written log record. |
Logging suspended |
Specifies whether logging is suspended. |
Status of the offload task |
The status of the offload task. Alloc archive means that the offload task is
busy allocating the archive data set, which could indicate that a tape mount request is pending;
Copying BSDS means that the offload task is busy copying the BSDS data set;
Busy means that the offload task is busy with other processing;
Available means that the offload task is waiting for work. |
Active logs |
The number of active log data sets. |
Full active logs |
The total number of full active log data sets that have not yet been archived. |
Usage
The following tables list the Usage status attributes of z/OS queue managers. For each attribute, there is a brief
description of what information the attribute shows. The equivalent MQSC command is DISPLAY USAGE,
which displays information about the current state of a page set, or displays information about the
log data sets. For more information about MQSC commands, see Administration using MQSC commands in IBM Knowledge Center.
Table 4. Dataset records usage for z/OS queue
managers.
Attribute |
Meaning |
Usage type |
This attribute shows which type of information is displayed in the table. |
RBA of log |
The Relative Byte Address (RBA) of the most recently written log record. |
Data set type |
The type of data set, and circumstance. Oldest Active UOW means that the log
data set contains the start RBA of the oldest active unit of work for the queue manager;
Oldest pageset recovery means that the log data set contains the oldest restart RBA
of any page set for the queue manager; Oldest CF struc recovery means that the log
data set contains the LRSN which matches the time of the oldest current backup of any CF structure
in the queue sharing group. |
LRSN of log |
The Log Record Sequence Number (LRSN) of the most recently written log record. |
Data set name |
The name of the data set. |
Table 5. Buffer Pool records usage for z/OS queue
managers.
Attribute |
Meaning |
Usage type |
This attribute shows which type of information is displayed in the table. |
Buffer pool ID |
The buffer pool identifier, which identifies the buffer pool being used by the page set.
|
Buffers defined |
The number of buffers defined for the buffer pool. |
Page class |
The type of virtual storage pages used for backing the buffers in the buffer
pool. The values for page class are:
- Pageable 4 KB pages
- Fixed 4 KB pages
|
Buffer pool location |
Information about the LOCATION value for individual buffer pools. The values
for LOCATION are:
- Above the bar (64 bit storage)
- Below the bar (31 bit storage)
- Switching to above the bar (64 bit storage)
- Switching to below the bar (31 bit storage)
|
Free buffers |
The number of unused buffers in the buffer pool. |
Free buffers (%) |
The percentage of unused buffers in the buffer pool. |
Table 6. Page set records usage for z/OS queue
managers.
Attribute |
Meaning |
Usage type |
This attribute shows which type of information is displayed in the table. |
Expand type |
How the queue manager expands a page set when it becomes nearly full, and further pages are
required within it. None means that no further page set expansion is to take place.
User means that the secondary extent size that was specified when the page set was
defined is used. If no secondary extent size was specified, or it was specified as zero, then no
dynamic page set expansion can take place. System means that the secondary extent
size that was specified when the page set was defined is ignored. Instead, the queue manager sets a
value that is approximately 10 per cent of the current size of the page set. The new extent size is
rounded up to the nearest cylinder of DASD. If no secondary extend size was specified, or was
specified as zero, dynamic page set expansion can still take place. The queue manager sets a value
that is approximately 10 per cent of the current size of the page set. The new extent size is
rounded up depending on the characteristics of the DASD. If the value is User or
System , page set expansion occurs when the space in the page is 90 per cent used,
and is performed asynchronously to any other page set activity. At restart, if a previously used
page set has been replaced with a data set that is smaller, it is expanded until it reaches the size
of the previously used data set. Only one extent is required to reach this size. |
Page set ID |
The page set identifier. This is an optional number from 00 to 99. An asterisk on its own
specifies all page set identifiers. |
Pages |
The total number of 4 KB pages in the page set. |
Unused pages |
The number of pages that are not use (that is, available page sets). |
Pages holding persistent data |
The number of pages holding persistent data. These pages are being used to store object
definitions and persistent message data. |
Pages holding nonpersistent data |
The number of pages holding nonpersistent data. These pages are being used to store
nonpersistent message data. |
Extents used at restart |
The number of extents used by the page set at restart. |
Expand count |
The number of times the page set has been dynamically expanded since restart. The maximum
number of times the page set can be expanded is 123, provided that enough space is available.
|
Page set status |
The current status of the page set. Available means that the page set is
available; Defined means that the page set has been defined but has never been
used; Offline means that the page set is currently not accessible by the queue
manager, for example because the page set has not been defined to the queue manager; Not
defined means that the page set is not defined to the queue manager. |
Buffer pool ID |
The buffer pool identifier, which identifies the buffer pool being used by the page set.
|
Table 7. Shared message data set records usage for z/OS
queue managers.
Attribute |
Meaning |
Status |
The status of the shared message data set records for the selected queue manager. |
Application structure |
This is the name of the application structure for the selected queue manager. |
Offloaded messages |
This shows the number of shared messages in the structure for which the message data has been
stored in the data set owned by this queue manager. |
Total blocks |
This is the current total size of the owned data set in logical blocks, including blocks used
to store the space map. |
Total data blocks |
This is the total number of blocks in the owned data set which can be used to store data,
excluding those used to store the space map. |
Used data blocks |
This is the number of blocks in the owned data set which are currently in use (that is, one
or more pages of those blocks contain active message data). |
Used part (%) |
This is the percentage of used data blocks to the total data blocks. |
Block size (KB) |
This shows the size of each buffer in KB. This is equal to the logical block size of the
shared message data set. |
Total buffers |
This is the number of buffers in the pool |
In use buffers |
This is the number of buffers which are currently being used by requests to transfer data to
or from the data set. |
Saved buffers |
This is the number of buffers which are free but currently contain saved data for recently
accessed blocks. |
Empty buffers |
This is the number of buffers which are free and empty. When a new buffer is
required, empty buffers are used first, but if there are no empty buffers, the least recently used
saved buffer is reset to empty and used instead. |
Reads saved (%) |
This is he percentage of read requests (during the current statistics
interval) where the current block was found in a saved buffer, avoiding the need to read the data
from the data set. |
Lowest free |
This is the smallest number of free buffers during the current statistics
interval. |
Wait rate (%) |
This is the percentage of requests to acquire a buffer which had to wait for a
free buffer. |