API exits not linked with an MQI library

Under certain circumstances, you should link your existing API exit, that cannot be re-coded to use the MQIEP function pointers, with an IBM® MQ API library.

This is necessary, so that your existing API exit can be successfully loaded, by the runtime linker of your system, into programs that do not already have the function pointers loaded.

Note: This information is limited to those existing API exits that make MQI calls directly. That is, those exits that do not use , MQIEP. Where possible, you should plan to re-code the exit to use the MQIEP entry points instead.

From IBM MQ 8.0, runmqsc is an example of a program that does not link directly with an MQI library.

Therefore, an API exit that has not been linked with its required IBM MQ API library, or re-coded to use the MQIEP, fails to load into runmqsc.

You see errors in the queue manager error log, for example, AMQ6175: The system could not dynamically load the shared library, together with qualifying text such as undefined symbol: MQCONN.

and AMQ7214: The module for API Exit 'myexitname' could not be loaded.