Middleware News

You are having trouble connecting a WebSphere MQ client to a MQ server, receiving errors that you can not connect to the MQ queue manager. One of the first things to determine is if the two machines can communicate, and using the telnet tool is one way to accomplish it. Symptom Receiving errors which state that a queue manager is not found or not available. Connection errors. For example: AMQ9213, AMQ9524, AMQ9202 or AMQ9508 or MQRC =2059 0x0000080b MQRC_Q_MGR_NOT_AVAILABLE. Please note, this is by no means an exclusive list of errors related to this type a problem but just a sample of some of the more common error messages and codes that might occur. Cause One possible cause is that the two machines can not communicate. May be the IP address or hostname was not properly specified by the MQ client. The port number might be incorrect. A queue manager is not running at the desired host. The queue manager could be running, but the corresponding listener is not runnin

Queue manager stores the client connection channel information in client channel definition table (CCDT). This table is updated whenever a client connection channel is defined or altered.  MQ client applications uses the client channel definition table (CCDT) to determine the channel definitions and authentication information to connect to a queue manager.  For a client application to use the CCDT , it must either be copied to the client machine or the file should be placed in a location from where the client can access it. However, there is no traditional file system available on the appliance. Hence the file needs to be copied to a directory from where it can be downloaded.  Here are the steps to do it. Run the below command on the appliance to create the required MQ objects and a user account under which the client connection will be established. usercreate -u maya -p passw0rd crtmqm QM1 strmqm QM1 runmqsc QM1     DEFINE QLOCAL(‘Q1’)     DEFINE CHANNEL