Use 'runmqras' to gather your WebSphere MQ diagnostic information
Rich_Montjoy 120000EPN0 Comments (4) Visits (14155)
If you are using WebSphere MQ (WMQ) 220.127.116.11 or later on UNIX®, Linux, Windows, and IBM i, you can use a Java™ based utility called 'runmqras' shipped with the product to gather typical WMQ diagnostic information into a zip file.
'runmqras' was first introduced in WMQ v18.104.22.168 as a proof of concept but did not come up to speed until versions 22.214.171.124, 126.96.36.199 and 7.5. It is really easy to use so we'd like to encourage everyone to give it a try as It can lessen the burden of manually collecting the various diagnostic files. Previously these files were gathered manually and we found that it was common for files to be unintentionally omitted when submitted to IBM Support.
WHAT IT CAN DO
To display the 'runmqras' options use the -help as follows but I'll give a few examples below.
Depending on the flags used, 'runmqras' will gather the contents of the WMQ errors directory, FDCs, outputs from 'ipcs' and 'ps', and directory listings to verify installation integrity, (plus more). For example running 'runmqras' from the bin directory will run for a bit and bundle the files into a zip files. The last few lines on the console report whether it completed successfully and where the output resides.
'runmqras' also allows you to filter what you wish to gather with the 'section' flag. For example to gather information relating to clustering and include a previously invoked WMQ trace along with the queue manager configuration and current status.
$runmqras -qmlist QM1,QM2 -section defs,cluster,trace
You can even control the name of the output file and location with the flags:
By default with no '-section' requested, it will not gather trace files nor does it do runmqsc outputs. To include those you need the <defs> or <trace> sections as demonstrated above.
$runmqras -zipfile SampleRunmqras.zip -outputdir /tmp/MyRunmqras
In addition there are flags that allow you to ftp the documentation directly to IBM and even names the file appropriately by prefixing the problem record number (pmr) in the file name.
$runmqras -ftp IBM -pmrno 01234,567,890
WHAT IT CAN'T DO
It is important to remember that 'runmqras' it not a substitution for a proper problem description. When submitting diagnostic information to IBM Support it is important to always take a few moments to give some context to the documentation you are sending in to be reviewed. Timestamps, relevant object names for the expected message flow, and errors observed are all helpful in the problem determination process.
Here is a link to a technote describing 'runmqras' in more detail: Using "runmqras" to collect problem determination data and files
Read more about 'runmqras' in the WMQ Information Center
So remember, when opening a new WMQ problem record or even with an existing one, use 'runmqras' to make your life easier.