MQ on the command line

I have installed MQ on my computer (checked it with regedit32) But I get an "can't recognize command" error when I type "runmqsc" in the command line (environment variable is set to mqjms.jar) What am I missing? I want to create quemanagers and a queue via command line in a window

+3


source to share


3 answers


What version of MQ are you using? (You can check by typing dspmqver

on the command line)

To create a queue manager, you must use the command crtmqm

. If you want to create a queue manager using the defaults and name it MyQueueManager, you must enter the following command:

crtmqm MyQueueManager

      

In any case, I would recommend creating queue managers via MQ Explorer, assuming you have it installed. It's much easier and stupid.

If you still want to work with the command line, after creating the queue manager, enter the following:



runmqsc MyQueueManager

      

This command will open the MQSC shell, which you can use to create objects (such as queues) in the queue manager.

To create a queue with default values ​​named "MyQueue", enter:

DEFINE QLOCAL('MyQueue')

      

+3


source


You look like a newbie to MQ. I suggest you read MQ first and then start learning. Information about MQ v7.5 can be found here: http://www-01.ibm.com/support/knowledgecenter/SSFKSJ_7.5.0/com.ibm.mq.pro.doc/q001010_.htm?cp=SSFKSJ_7.5.0% 2F1 .



By the way, there is no runmqm command. You can use the "dspmqver" command to display the version of MQ you have installed and "dspmq" to display a list of the queue managers running on this computer.

+2


source


For Windows installations, it is always a good idea to reboot the server before starting to preserve the registry and mitigate the effects of programs with poor memory leaks, etc.

Then, after installing MQ and the latest Fix Pack, reboot again. This saves the registry again and also displays the new environment variables.

Finally, at this point, run the setmqinst command. This sets the default values ​​pointing to the correct directory for this installation. If your bin directory is not recognized and Windows cannot find executables, then I suspect this is the part you missed.

+2


source







All Articles