IBM Websphere MQ : Using "runmqras" to collect problem determination data and files (MQ 7.0.1.8 or later; MQ 7.1.0.1 or later; MQ 7.5 or later) - Middleware News
You are using WebSphere MQ 7.0.1.8 or later (MQ 7.1.0.1 or
later; MQ 7.5 or later) and you have opened an IBM Service Request ticket (PMR)
to report a problem and you need to provide the MQ error logs, FDC files,
version/fix pack of MQ, etc.
Is there a tool that you could use to gather those files and optionally send them to IBM Support via ftp?
Is there a tool that you could use to gather those files and optionally send them to IBM Support via ftp?
Yes, you can use the MQ "runmqras" tool. The utility
"runmqras" is a Java based tool shipped with WebSphere MQ.
Note:
Although runmqras is available since 7.0.0.0 as a proof of concept, not until 7.0.1.8, 7.1.0.1 and 7.5 did the tool became fully functional.
Although runmqras is available since 7.0.0.0 as a proof of concept, not until 7.0.1.8, 7.1.0.1 and 7.5 did the tool became fully functional.
a) If you are going to gather information from all the queue
managers, issue the following, assuming that the PMR number is 01234,567,890
(for the flag "-pmrno").
The flag "-ftp IBM" indicates that the resulting zip file will be sent via ftp to the IBM ftp server used for receiving PMR data.
The flag "-ftp IBM" indicates that the resulting zip file will be sent via ftp to the IBM ftp server used for receiving PMR data.
runmqras -ftp IBM -pmrno 01234,567,890
This level of diagnostics is ideal when a problem is first raised, as it gives a lot of background on the product version, machine information, etc and can speed up the initial investigation.
Using the 'ftp' flag to ftp the resulting zip file directly to IBM is optional. For example, to collect the information and leave it as a zip file for manual submission you can remove the -ftp and -pmrno options. The location of the collected file is written to the console at the end of processing. Thus, the command would be simply:
runmqras
This level of diagnostics is ideal when a problem is first raised, as it gives a lot of background on the product version, machine information, etc and can speed up the initial investigation.
Using the 'ftp' flag to ftp the resulting zip file directly to IBM is optional. For example, to collect the information and leave it as a zip file for manual submission you can remove the -ftp and -pmrno options. The location of the collected file is written to the console at the end of processing. Thus, the command would be simply:
runmqras
b) Similar to (a), but you want to collect additional
information for the MQ queue manager QM_TEST. To collect important definition
information from "runmqsc" (section "defs"), cluster information (section
"cluster") and the MQ trace files (section "trace"), you would issue:
runmqras -qmlist QM_TEST -section defs,cluster,trace -ftp IBM
-pmrno 01234,567,890
Note: The list of sections to run for a particular problem would normally be provided by IBM support as they vary depending on the type of problem
c) You do not always need to specify all the sections. For
example, if the PMR is not related to clusters, then you do not need to specify
the section "clusters" and you can specify only the definitions in runmqsc
(section "defs") and the traces (section "trace"):
runmqras -qmlist QM_TEST -section defs,trace -ftp IBM -pmrno
01234,567,890
The following link of the WebSphere MQ Information Center has
more information on the options to be used with runmqras:
WebSphere MQ > Reference > Administration reference > WebSphere MQ control commands > The control commands
runmqras
WebSphere MQ > Reference > Administration reference > WebSphere MQ control commands > The control commands
runmqras
This section shows examples on how to use the tool and typical messages that you see when using it. Also, it shows what type of files are collected.
1) Example of using runmqras in Linux Intel 32-bit to collect
the data for all queue managers and send the resulting zip file to IBM via ftp,
using PMR 01234,567,890.
$ runmqras -ftp IBM -pmrno 01234,567,890
java version "1.5.0"
Java(TM) 2 Runtime Environment, Standard Edition (build pxi32dev-20111020 (SR13 ))
IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Linux x86-32 j9vmxi3223-20111020 (JIT enabled)
J9VM - 20111017_92807_lHdSMr
JIT - 20110916_20782_r8
GC - 20110524_AA)
JCL - 20111019
/opt/mqm/java/jre/bin/java -cp /opt/mqm/java/lib/com.ibm.mq.commonservices.jar:/opt/mqm/java/lib/com.ibm.mq.tools.ras.jar -Djava.library.path=/opt/mqm/lib:/opt/mqm/java/lib -DdefaultRasInput=/opt/mqm/bin/isa.xml -DdefaultRasWork=/tmp/runmqras_120525_150110 crtmqras.Zipper -ftp IBM -pmrno 01234,567,890
crtmqras v1.15.1.19 starts...
Using default Input path:
/opt/mqm/bin/isa.xml
Using default Work path:
/tmp/runmqras_120525_150110
Using default output path:
/tmp/runmqras_120525_150110
Using Zip File path:
/tmp/runmqras_120525_150110/01234.567.890.runmqras_201205251401.zip
Running on Linux
Editor Note: ... you may see a slight delay at this time while the tool gathers the files
crtmqras has successfully finished
Editor Note: ... the following 2 lines provide the full path of the resulting zip file.
The zip file can be found at /tmp/runmqras_120525_150110/01234.567.890.runmqras_201205251401.zip
FTP HANDLER: Opening connection to the server.
FTP HANDLER: Connection established for user -anonymous.
FTP HANDLER: Starting file transfer.
Transferred: 10 %.
Transferred: 20 %.
Transferred: 30 %.
Transferred: 40 %.
Transferred: 50 %.
Transferred: 60 %.
Transferred: 70 %.
Transferred: 80 %.
Transferred: 90 %.
Transferred: 100 %.
FTP HANDLER: File transfer complete.
2) Excerpt from the listing of files included in the zip file obtained by the above runmqras invocation (item 1)
Notes:
- To keep the listing short in this technote, files with size of 0 were omitted.
- The queue manager QMGRMI is a multi-instance queue manager and the queue manager data is located in a different path: /var/mqm/data/
- The file names and number of files that you will see, might be different than the ones shown below.
$ unzip -l /tmp/runmqras_120525_150110/01234.567.890.runmqras_201205251401.zip
Archive: /tmp/runmqras_120525_150110/01234.567.890.runmqras_201205251401.zip
Length Date Time Name
-------- ---- ---- ----
18634 04-30-12 12:14 var/mqm/errors/ffst.out
265502 04-27-12 07:26 var/mqm/errors/AMQERR01.LOG
2732 05-25-12 08:28 var/mqm/mqs.ini
1296 11-22-11 09:28 var/mqm/qmgrs/QM_TEST/qm.ini
1298 05-25-12 08:28 var/mqm/data/QMGRMI.000/qm.ini
509 01-16-12 15:00 var/mqm/qmgrs/QM_TEST/qmstatus.ini
556 05-25-12 08:28 var/mqm/data/QMGRMI.000/qmstatus.ini
56 01-16-12 15:00 var/mqm/qmgrs/QM_TEST/amqalchk.fil
56 05-25-12 08:28 var/mqm/data/QMGRMI.000/amqalchk.fil
52904 01-16-12 15:00 var/mqm/qmgrs/QM_TEST/errors/AMQERR01.LOG
7066 05-25-12 08:28 var/mqm/data/QMGRMI.000/errors/AMQERR01.LOG
6256 01-16-12 15:00 var/mqm/log/QM_TEST/amqhlctl.lfh
6256 05-25-12 08:28 var/mqm/log/QMGRMI.000/amqhlctl.lfh
6286 01-25-12 11:38 home/userx/.mqdata/.metadata/.log
... more files for MQ Explorer (if applicable)
939 05-25-12 14:01 dspmqver_-a.stdout
79 05-25-12 14:01 idmqm.stdout
20176 05-25-12 14:01 ps_eo.stdout
2388 05-25-12 14:01 amqicdir-a.stderr
338 05-25-12 14:01 ipcs_u.stdout
234 05-25-12 14:01 binrpm.stdout
91 05-25-12 14:01 uname.stdout
109 05-25-12 14:01 dspmqver.stdout
4636 05-25-12 14:01 ipcs_t.stdout
3305 05-25-12 14:01 netstat-s.stdout
4684 05-25-12 14:01 javalibfiles_sum.stdout
2291 05-25-12 14:01 javalibfiles.stdout
65 05-25-12 14:01 lib64files.stderr
7185 05-25-12 14:01 binfiles.stdout
498 05-25-12 14:01 mount.stdout
9 05-25-12 14:01 stamp_hostname.stdout
498 05-25-12 14:01 ipcs_l.stdout
125 05-25-12 14:01 netstat-anp.stderr
3996 05-25-12 14:01 ipcs_a.stdout
70 05-25-12 14:01 javalib64files.stderr
81552 05-25-12 14:01 libfiles_sum.stdout
58 05-25-12 14:01 stamp_dspmqver.stdout
53 05-25-12 14:01 dmpmqaut.stderr
59 05-25-12 14:01 lib64files_sum.stderr
53 05-25-12 14:01 gsk8ver.stderr
17877 05-25-12 14:01 ps_efl.stdout
251 05-25-12 14:01 df.stdout
3377 05-25-12 14:01 binfiles_sum.stdout
47339 05-25-12 14:01 netstat-anp.stdout
839 05-25-12 14:01 dspmq.stdout
64 05-25-12 14:01 javalib64files_sum.stderr
264 05-25-12 14:01 netstat-i.stdout
376 05-25-12 14:01 explorerFiles.stdout
399 05-25-12 14:01 errors.stdout
54 05-25-12 14:01 gsk75ver.stderr
831 05-25-12 14:01 dspmqver_-p_15.stdout
53 05-25-12 14:01 gsk7ver.stderr
6880 05-25-12 14:01 libfiles.stdout
59 05-25-12 14:01 amqoamd.stdout
3785 05-25-12 14:01 ipcs_c.stdout
4048 05-25-12 14:01 usrlibsymlinks.stdout
394 05-25-12 14:01 autopdzip/autopd/autopd-collection-environment-v2.xml
41975 02-22-12 10:18 isa.xml
139474 05-25-12 14:01 console.log
-------- -------
2763148 170 files
3) Example of running runmqras for only the QM_TEST queue manager, gathering runmqsc, clustering data and trace files.
$ runmqras -qmlist QM_TEST -section defs,cluster,trace -ftp IBM -pmrno 01234,567,890
... Similar to item (1) ... Notice the path for the zip file.
Using Zip File path:
/tmp/runmqras_120525_154125/01234.567.890.runmqras_201205251441.zip
Running on Linux
crtmqras has successfully finished
The zip file can be found at /tmp/runmqras_120525_154125/01234.567.890.runmqras_201205251441.zip
FTP HANDLER: Opening connection to the server.
FTP HANDLER: Connection established for user -anonymous.
FTP HANDLER: Starting file transfer.
...
4) Example of the contents for the zip file obtained in item 3:
Note: To keep the illustration short, only few representative files are shown in the output.
$ unzip -l /tmp/runmqras_120525_154125/01234.567.890.runmqras_201205251441.zip
Archive: /tmp/runmqras_120525_154125/01234.567.890.runmqras_201205251441.zip
Length Date Time Name
-------- ---- ---- ----
18634 04-30-12 12:14 var/mqm/errors/ffst.out
265502 04-27-12 07:26 var/mqm/errors/AMQERR01.LOG
2732 05-25-12 08:28 var/mqm/mqs.ini
1296 11-22-11 09:28 var/mqm/qmgrs/QM_TEST/qm.ini
500 05-25-12 14:39 var/mqm/qmgrs/QM_TEST/qmstatus.ini
56 05-25-12 14:39 var/mqm/qmgrs/QM_TEST/amqalchk.fil
63635 05-25-12 14:39 var/mqm/qmgrs/QM_TEST/errors/AMQERR01.LOG
6256 05-25-12 14:39 var/mqm/log/QM_TEST/amqhlctl.lfh
6286 01-25-12 11:38 home/rivera/.mqdata/.metadata/.log
13857 01-27-12 15:29 home/userx/.mqdata/.metadata/.plugins/com.ibm.mq.explorer.ui/WMQ_Navigator.xml
4284 05-25-12 14:40 var/mqm/trace/AMQ30089.0.TRC
16060 05-25-12 14:40 var/mqm/trace/AMQ29730.0.TRC
939 05-25-12 14:41 dspmqver_-a.stdout
367 05-25-12 14:42 runmqsc_PUBSUB_QM_TEST.stdout
132 05-25-12 14:41 amqsbcg_QM_TEST_SCTQ.stdout
494 05-25-12 14:41 runmqsc_PROCESS_QM_TEST.stdout
65815 05-25-12 14:41 runmqsc_QUEUE_QM_TEST.stdout
614 05-25-12 14:41 runmqsc_SERVICE_QM_TEST.stdout
62874 05-25-12 14:41 amqsbcg_QM_TEST_SCRQ.stdout
79 05-25-12 14:41 idmqm.stdout
21988 05-25-12 14:41 ps_eo.stdout
2388 05-25-12 14:41 amqicdir-a.stderr
833 05-25-12 14:41 runmqsc_QALIAS_QM_TEST.stdout
340 05-25-12 14:41 ipcs_u.stdout
234 05-25-12 14:41 binrpm.stdout
91 05-25-12 14:41 uname.stdout
603 05-25-12 14:42 runmqsc_LSSTATUS_QM_TEST.stdout
2432 05-25-12 14:41 runmqsc_QMGR_QM_TEST.stdout
4821 05-25-12 14:41 runmqsc_CONN_QM_TEST.stdout
109 05-25-12 14:41 dspmqver.stdout
1066 05-25-12 14:41 runmqsc_NAMELIST_QM_TEST.stdout
5786 05-25-12 14:41 ipcs_t.stdout
3305 05-25-12 14:41 netstat-s.stdout
4684 05-25-12 14:41 javalibfiles_sum.stdout
2291 05-25-12 14:41 javalibfiles.stdout
65 05-25-12 14:41 lib64files.stderr
7185 05-25-12 14:41 binfiles.stdout
3716 05-25-12 14:42 runmqsc_TOPIC_QM_TEST.stdout
283 05-25-12 14:41 runmqsc_CLUSQMGR_QM_TEST.stdout
498 05-25-12 14:41 mount.stdout
867 05-25-12 14:41 runmqsc_LISTENER_QM_TEST.stdout
765 05-25-12 14:41 runmqsc_QREMOTE_QM_TEST.stdout
9 05-25-12 14:41 stamp_hostname.stdout
498 05-25-12 14:41 ipcs_l.stdout
15 05-25-12 14:41 amqrfdm_QM_TEST.stderr
284 05-25-12 14:42 runmqsc_SVSTATUS_QM_TEST.stdout
15482 05-25-12 14:41 runmqsc_QSTATUS_QM_TEST.stdout
125 05-25-12 14:41 netstat-anp.stderr
6823 05-25-12 14:41 runmqsc_QMODEL_QM_TEST.stdout
5016 05-25-12 14:41 ipcs_a.stdout
70 05-25-12 14:41 javalib64files.stderr
82095 05-25-12 14:41 libfiles_sum.stdout
58 05-25-12 14:41 stamp_dspmqver.stdout
11221 05-25-12 14:41 dmpmqaut.stderr
59 05-25-12 14:41 lib64files_sum.stderr
53 05-25-12 14:41 gsk8ver.stderr
19479 05-25-12 14:41 ps_efl.stdout
251 05-25-12 14:41 df.stdout
798 05-25-12 14:41 runmqsc_AUTHINFO_QM_TEST.stdout
3377 05-25-12 14:41 binfiles_sum.stdout
50907 05-25-12 14:41 netstat-anp.stdout
829 05-25-12 14:41 dspmq.stdout
287 05-25-12 14:42 runmqsc_TPSTATUS_QM_TEST.stdout
272 05-25-12 14:41 runmqsc_CHS_QM_TEST.stdout
64 05-25-12 14:41 javalib64files_sum.stderr
264 05-25-12 14:41 netstat-i.stdout
58095 05-25-12 14:41 runmqsc_QLOCAL_QM_TEST.stdout
131 05-25-12 14:41 amqsbcg_QM_TEST_SCCQ.stdout
11341 05-25-12 14:41 runmqsc_CHANNEL_QM_TEST.stdout
376 05-25-12 14:41 explorerFiles.stdout
2440 05-25-12 14:42 runmqsc_SUB_QM_TEST.stdout
561 05-25-12 14:42 runmqsc_QMSTATUS_QM_TEST.stdout
399 05-25-12 14:41 errors.stdout
54 05-25-12 14:41 gsk75ver.stderr
1330 05-25-12 14:42 runmqsc_SBSTATUS_QM_TEST.stdout
2842 05-25-12 14:41 amqrfdm_QM_TEST.stdout
831 05-25-12 14:41 dspmqver_-p_15.stdout
284 05-25-12 14:41 runmqsc_QCLUSTER_QM_TEST.stdout
53 05-25-12 14:41 gsk7ver.stderr
6880 05-25-12 14:41 libfiles.stdout
284 05-25-12 14:42 runmqsc_TCLUSTER_QM_TEST.stdout
15588 05-25-12 14:41 amqoamd.stdout
4709 05-25-12 14:41 ipcs_c.stdout
4048 05-25-12 14:41 usrlibsymlinks.stdout
394 05-25-12 14:42 autopdzip/autopd/autopd-collection-environment-v2.xml
41975 02-22-12 10:18 isa.xml
134131 05-25-12 14:42 console.log
-------- -------
1970140 183 files
Comments
Post a Comment