You need to take into consideration if you are building 32-bit or 64-bit applications and whether or not you are in a threaded or non threaded environment.
The loadable object must have its name in upper case, for example MYFORMAT. Use the libmqm library to resolve the calls to MQXCNVC.
In addition to creating the data-conversion exit for the basic environment, another is required in the threaded environment. This loadable object must be followed by _r (on AIX(R), HP-UX, and Linux) to indicate that it is a threaded version. Use the libmqm_r library to resolve the calls to MQXCNVC. Note that both loadable objects (non-threaded and threaded) are required for a threading environment.
If you are running MQI clients, all data conversion is performed by the proxy running on the machine to which the client is attached. This means that any data conversion exits are run on the server, in the environment of the proxy, and not as part of the client application.
For most platforms, the proxy/responder program is a threaded program. Consequently, the data conversion exit must be compiled with appropriate options to run in this threaded environment. Whether or not the client application is threaded is irrelevant.
On the WebSphere MQ for UNIX(R) systems, the proxy is threaded.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
unenv |