StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Several C samples at <a href="http://www.capitalware.biz/mq_code_c.html" rel="nofollow noreferrer">Capitalware</a>. Look for the ones that use the MQAI interface. Nothing there that enumerates queues but the MQAI programs all use Programmable Command Format (PCF) messages. Enumerating the list of queues is a PCF equivalent of DIS Q(*).</p> <p>You will also want to review the PCF manual in the <a href="http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/topic/com.ibm.mq.csqzac.doc/pc10120_.htm" rel="nofollow noreferrer">Infocenter</a></p> <p>Tried to add this as a comment but the links didn't markup as expected:</p> <p>One way or another you end up at PCF commands if you are doing this remotely. You can run MQSC script commands remotely if you install the <a href="http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg24019253&loc=en_US&cs=utf-8&lang=en" rel="nofollow noreferrer">WMQ client</a> and use <a href="http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg24007769&loc=en_US&cs=utf-8&lang=en" rel="nofollow noreferrer">SupportPac MO72</a> to convert them to PCF if you want but at the QMgr it's ultimately PCF. I do a lot of central inquiry and reporting on WMQ with scripts that iterate over a list of QMgrs and execute MO72. I once used CGI and wrote a web front-end over MO72.</p> <p>By the way, <a href="http://www.ibm.com/support/docview.wss?rs=171&uid=swg24000142&loc=en_US&cs=utf-8&lang=en" rel="nofollow noreferrer">SupportPac MO71</a> will do the type of monitoring that you are describing. It's compiled C so it needs the WMQ client installed but it can be set up to monitor depth of queues and even has a mini web server so many people can use the same MO71 instance.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload