Skip to main content

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?

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.
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.
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
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



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

adsrerrapop

Popular posts from this blog

IBM Websphere MQ interview Questions Part 5

MQ Series: - It is an IBM web sphere product which is evolved in 1990’s. MQ series does transportation from one point to other. It is an EAI tool (Middle ware) VERSIONS:-5.0, 5.1, 5.3, 6.0, 7.0(new version). The currently using version is 6.2 Note: – MQ series supports more than 35+ operating systems. It is platform Independent. For every OS we have different MQ series software’s. But the functionality of MQ series Default path for installing MQ series is:- C: programfiles\BM\clipse\SDK30 C: programfiles\IBM\WebsphereMQ After installation it will create a group and user. Some middleware technologies are Tibco, SAP XI. MQ series deals with two things, they are OBJECTS, SERVICES. In OBJECTS we have • QUEUES • CHANNELS • PROCESS • AUTHENTICATION • QUERY MANAGER. In SERVICES we have LISTENERS. Objects: – objects are used to handle the transactions with the help of services. QUEUE MANAGER maintains all the objects and services. QUEUE: – it is a database structure

IBM Websphere MQ Reason code list / mq reason codes / websphere mq error codes / mq error messages

Reason code list ================= The following is a list of reason codes, in numeric order, providing detailed information to help you understand them, including: * An explanation of the circumstances that have caused the code to be raised * The associated completion code * Suggested programmer actions in response to the code * 0 (0000) (RC0): MQRC_NONE * 900 (0384) (RC900): MQRC_APPL_FIRST * 999 (03E7) (RC999): MQRC_APPL_LAST * 2001 (07D1) (RC2001): MQRC_ALIAS_BASE_Q_TYPE_ERROR * 2002 (07D2) (RC2002): MQRC_ALREADY_CONNECTED * 2003 (07D3) (RC2003): MQRC_BACKED_OUT * 2004 (07D4) (RC2004): MQRC_BUFFER_ERROR * 2005 (07D5) (RC2005): MQRC_BUFFER_LENGTH_ERROR * 2006 (07D6) (RC2006): MQRC_CHAR_ATTR_LENGTH_ERROR * 2007 (07D7) (RC2007): MQRC_CHAR_ATTRS_ERROR * 2008 (07D8) (RC2008): MQRC_CHAR_ATTRS_TOO_SHORT * 2009 (07D9) (RC2009): MQRC_CONNECTION_BROKEN * 2010 (07DA) (RC2010): MQRC_DATA_LENGTH_ERROR * 2011 (07DB) (RC2011): MQRC_DYNAMIC_Q_NAME_ERROR * 2012 (07DC) (RC201

IBM WebSphere MQ – Common install/uninstall issues for MQ Version on Windows - Middleware News

Creating a log file when you install or uninstall WebSphere MQ WebSphere MQ for Windows is installed using the Microsoft Installer (MSI). If you install the MQ server or client through launchpad , MQPARMS or setup.exe , then a log file is automatically generated in %temp% during installation. Alternatively you can supply parameters on the installation MSI command msiexec to generate a log file, or enable MSI logging system-wide (which generates MSI logs for all install and uninstall operations). If you uninstall through the Windows Add/Remove programs option, no log file is generated. You should either uninstall from the MSI command line and supply parameters to generate a log file, or enable MSI logging system-wide (which generates MSI logs for all install and uninstall operations). For details on how to enable MSI logging, see the following article in the WebSphere MQ product documentation: Advanced installation using msiexec For details on how to enable system-w