Do you develop applications that use MQ?  Is your machine of choice a Mac?  Previously you’ve needed to create yourself another environment, maybe Linux, running in a virtual machine or a Docker container to be able to build and run your applications during the development phase.  We are very pleased to announce that the IBM MQ MacOS toolkit for developers is now available. This toolkit provides the ability to develop and interact directly with MQ from your Mac, for developers using the language interfaces; such as C, C++, COBOL, GoLang, and Node.js; which are built on the platform-native C library (libmqm) .  This extends the capability we already provide for Java developers on Mac, with the IBM MQ

What it lets you do

The MacOS toolkit includes native client runtime libraries, to run IBM MQ applications using the MQI written in C based languages. It also includes the elements required to build C based language applications, that is the header files and copybooks.  From your Mac you can now:

  • Get up and running with MQ faster, by being able to follow education material and undertake tutorials, directly from your Mac.
  • Run many of the samples you’ve been able to exercise MQ with from other platforms, such as classics like amqsput and amqsget.
  • Administer your queue manager, whether it is running in a Docker container, Cloud platform, VM, or supported on-premise solution, with MQSC commands via the provided runmqsc tool.
  • Develop MQ applications natively on Mac, using the provided C libraries to compile and unit test your code.
  • Use mqrc to get extra information on any error you see with MQ.
  • Utilise the new Node.js bindings (, Go bindings ( and JMS-like API for Golang (, which all build on the full C MQI library.

What it doesn’t do

What this doesn’t give you is a queue manager running natively on MacOS. So we suggest you spin up a queue manager in a Docker container (Ready, set, connect! MQ in Docker) or provision yourself a totally free trial queue manager on the Cloud (MQoC Lite plan) and point the applications you’re developing on the Mac at these.

This also won’t give you a supported way to run applications, for that you’ll need to take the code you’ve developed on the Mac and build it on your production platform of choice (MQ system requirements).

Where to get it from

The IBM MQ MacOS toolkit for developers is available as a free download from  It comes with a developer license, which allows you to use the program for internal development and unit testing on a developer machine.

How to install

After downloading the toolkit to your Mac machine, uncompress and untar the contents to your chosen directory.

Add the location of the bin directories,
<install location>/IBM-MQ-Toolkit-Mac-x64- and
<install location>/IBM-MQ-Toolkit-Mac-x64-, to the PATH by editing /etc/paths.

You can test your install by issuing an MQ command in a terminal window, for example dspmqver which will output information about your client installation.

The default data path is $HOME/IBM/MQ/data. You can change the default directory of the data path, by using the MQ_OVERRIDE_DATA_PATH environment variable. Note you must create the directory first, as the directory is not created automatically.


9 comments on"IBM MQ MacOS toolkit for developers now available"

  1. Hello, I have uncompressed and untarred the toolkit, and added the path to my samp/bin and bin (the IBM Toolkit folder is in my downloads folder) to both my .bash_profile and $PATH but i still get command not found errors when i attempt to issue dspmqver

    • RachelKing July 04, 2019

      Hi Luke,

      Thanks for your comment. Could you please run echo $PATH on the terminal you’re issuing dspmqver from, to check that the PATH settings have been picked up correctly.

      Thank you,

  2. Kazumichi Hatakeyama March 01, 2019

    in my case, amqsputc failed with MQRC_CHANNEL_CONFIG_ERROR and FDC shows user name too long (more than 13 characters). Actually my user name is 19 chars…. Is there any workaround?

  3. what about dmpmqcfg and dmpmqmsg ?

Join The Discussion

Your email address will not be published.