What can I do if a WebSphere MQ Workflow client cannot connect to the server?

Resolving The Problem

To test the client-to-server connection, first make sure that the basic communication via WebSphere MQ works. To do this, test if you can put messages into and get messages from the WebSphere MQ queue by doing the following:

1. Find the WebSphere MQ Workflow profile named fmcrc on your machine. If you set up a default installation and configuration, then this is in /var/fmc/cfgs/FMC and named fmcrc
2. In the fmcrc profile, you will find the channel table name and the path on the machine where this one is located. If you set up a default installation and configuration then this is in /var/fmc/chltabs and named MQWFCHL.TAB
3. Log on as either root or the default Workflow user ID fmc.
4. Change to the directory where the commands amqsputc and amqsgetc can be found. If you set up a default installation and configuration then this is /usr/mqm/samp/bin.
5. Enter the commands:
• export MQCHLLIB=/var/fmc/chltabs
• export MQCHLTAB=MQWFCHL.TAB
  Note: If you are not using the default values, substitute the above with your values.
6. In the same session, enter the command:
7. ./amqsputc RTSINPUTQ FMCQM
8. Type in any characters, then press Enter twice.
9. In the same session, enter the command:
10. ./amqsgetc RTSINPUTQ FMCQM
11. The first line of output should display the characters that you typed.
12. The next line should display ... no more messages ...