IBM Support

Basic troubleshooting guidelines for WebSphere MQ Workflow Servers

Troubleshooting


Problem

How can I perform problem determination on a WebSphere MQ Workflow Server?

Resolving The Problem

    Here are some initial things to do for problem determination on a WebSphere MQ Workflow for AIX server.

    The commands given here are samples, based on a default AIX installation, and it may be necessary to change them depending on your local setup. The same (or similar) commands can be used for WebSphere MQ Workflow on HP-UX and Solaris.

    1. Check the Workflow status:
          ps -ef | grep fmc
      check that:
      fmcamain and fmcemain are up.
    2. Check database status:
        db2 connect to FMCDB user fmc using <password>
    It should display something like:
        DB2 connection information
       Database server           = DB2/6000 7.2.5
       SQL authorization ID      = FMC
       Local database alias      = FMCDB


    3. Check client conectivity:
        fmcautil -uADMIN -ppassword
    should work.

    4. Check Administration server functionality:
        fmcautil -uADMIN -ppassword
    command input sequence
        m; e; q
    should lead to the answer:
    ... Execution Server is 'active' (2 instance(s) running)

    5. Check some error logs:
        /var/mqm/errors/AMQERR01.LOG (WebSphere MQ complaints)
        /var/mqm/qmgrs/FMCQM/errors/AMQERR01.LOG (WebSphere MQ complaints)
        /home/db2inst1/sqllib/db2dump/db2diag.log (DB2 complaints)
        /var/fmc/fmcerr.log (WebSphere MQ Workflow complaints)
        /var/fmc/fmcsys.log (WebSphere MQ Workflow system history)

    6. Check the the client-server connection, using WebSphere MQ test programs:
    6.1. Check the WebSphere MQ Workflow profile named fmcrc on your machine.
        It is in /var/fmc/cfgs/FMC and named fmcrc
    6.2. The channel table name and the path is
        /var/fmc/chltabs/MQWFCHL.TAB
    If the WebSphere MQ Workflow servers are active, they will read all messages put in their queues, and you will not retrieve any messages, so WebSphere MQ Workflow must be stopped before you perform the following test:

    6.3. To run the commands amqsputc and amqsgetc, change to the user ID fmc or root, then:
     a) Go to the path, where these commands can be found:
        cd /usr/mqm/samp/bin
     b) There, you need to perform the two export steps:
        export MQCHLLIB=/var/fmc/chltabs
       export MQCHLTAB=MQWFCHL.TAB

    c) Do not leave this session and then enter:
        ./amqsputc RTSINPUTQ FMCQM
    d) Type in any string.
    e) Press the Enter key twice.
    f) Do not leave this session and then enter:
        ./amqsgetc RTSINPUTQ FMCQM
    The first line should display the string you typed in.
    The next line displays  ... no more messages ...

[{"Product":{"code":"SSVLA5","label":"WebSphere MQ Workflow"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Maintenance","Platform":[{"code":"PF002","label":"AIX"}],"Version":"3.6","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
15 June 2018

UID

swg21058191