Difference between revisions of "MONITOR MQ: Monitoring MQ/204"

From m204wiki
Jump to navigation Jump to search
 
Line 12: Line 12:
 
   [SUBTASKS] [SUMMARY] [EVERY <span class="term">n</span>]</p>
 
   [SUBTASKS] [SUMMARY] [EVERY <span class="term">n</span>]</p>
  
====Where====
+
<p>Where:</p>
 
<ul>
 
<ul>
 
<li>
 
<li>
Line 53: Line 53:
 
</ul>
 
</ul>
  
====Usage====
+
==Usage==
 
<p>
 
<p>
 
Output from the MONITOR MQ command goes to USE output, if USE is active.</p>
 
Output from the MONITOR MQ command goes to USE output, if USE is active.</p>
Line 71: Line 71:
 
</ul>
 
</ul>
  
====Examples====
+
==Examples==
 
<p>
 
<p>
 
The following example shows output from a MONITOR MQ command:</p>
 
The following example shows output from a MONITOR MQ command:</p>
Line 120: Line 120:
  
 
&gt; </p>
 
&gt; </p>
 +
 +
[[Category:Commands]]

Latest revision as of 23:25, 17 December 2021

Summary

Privileges
System manager or User 0
Function
Aids the system manager in controlling an Online that is using MQ/204. The MQ option provides information on the MQ/204 features.

Syntax

MONITOR MQ [(QUEUEMANAGER | QM) qmanager_entity_name | (QUEUE | Q) queue_entity_name] [SUBTASKS] [SUMMARY] [EVERY n]

Where:

  • QUEUEMANAGER (or QM) and QUEUE (or Q) can be used to filter the output of MONITOR MQ:
    • If a QUEUEMANAGER clause is specified, output is restricted to that queue manager.
    • If a QUEUE clause is specified, output is restricted to the specified queue.

    The QUEUEMANAGER, QUEUE, and SUBTASK clauses are mutually exclusive. To monitor the clauses in succession, you must issue a separate MONITOR MQ command for each clause.

  • SUBTASKS produces a report of WebSphere MQ subtask activity. The report includes the following numeric output about subtasks:
    • Allocated
    • Currently in use
    • Free, but connected to a queue manger
    • Free and unconnected

    This report also lists the queue managers to which subtasks are currently connected and indicates how many are connected to each.

  • SUMMARY limits the output produced by MONITOR MQ:
    • If SUMMARY is specified, the list of users who have each queue open is omitted from the report.
    • If both SUBTASKS and SUMMARY are specified, the list of queue managers and count of subtasks connected to each are omitted from the subtask report.
  • EVERY n clause provides the command refresh capability.

Usage

Output from the MONITOR MQ command goes to USE output, if USE is active.

The MONITOR MQ command lists defined queue managers by both entity and external name, and whether they have been stopped or started. After each queue manager, a list of all queues for that queue manager is displayed, also by entity and external name. After each queue name, a list of the current users is displayed with the following data:

  • User number.
  • User name.
  • Last WebSphere MQ API call made.
  • CompCode and Reason display headings for the last call separated by a slash (/) or the word PENDING, if the call has not yet completed. CompCode and Reason values are returned by all WebSphere MQ API calls.
  • Number of bytes of data transferred on the last put or get.

Examples

The following example shows output from a MONITOR MQ command:

> MONITOR MQ QUEUEMANAGER: PRODUCTION EXTERNAL NAME: SYS1.PRODUCTION STATUS: STARTED QUEUE: INCOMING EXTERNAL NAME: INQUEUE.FOR.WORK USER USERID LASTCALL STATUS DATALEN ------ ---------- -------- ------- ------- 25 JOE MQGET 0/0 50 QUEUE: OUTGOING EXTERNAL NAME: OUTQUEUE.FOR.WORK USER USERID LASTCALL STATUS DATALEN ------ ---------- -------- ------- ------- 25 JOE MQPUT 0/0 50 56 FRED MQPUT1 PENDING 50 QUEUEMANAGER: TEST EXTERNAL NAME: SYS1.TEST STATUS: STOPPED QUEUE: INBOX EXTERNAL NAME: TEST.INBOX USER USERID LASTCALL STATUS DATALEN ------ ---------- -------- ------- ------- 15 SALLY MQGET 0/0 1000 23 MIKE MQGET 2/2033 0 QUEUE: OUTBOX EXTERNAL NAME: TEST.OUTBOX QUEUEMANAGER: TEST2 EXTERNAL NAME: SYS1.TEST2 STATUS: DEFINED QUEUE: INBOX2 EXTERNAL NAME: TEST2.INBOX QUEUE: OUTBOX2 EXTERNAL NAME: TEST2.OUTBOX >