Linking libraries

 

You need to link your programs with the appropriate library provided by WebSphere MQ. The following table shows which library to use in different environments

Hardware platform Threaded or non-threaded environment Program/exit type Library file
PA-RISC Threaded Server for C libmqm.sl
PA-RISC Threaded Client for C libmqic.sl
PA-RISC Non-threaded Server for C libmqm_r.sl
PA-RISC Non-threaded Client for C libmqic_r.sl
IA64 (IPF) Threaded Server for C libmqm.so
IA64 (IPF) Threaded Client for C libmqic.so
IA64 (IPF) Non-threaded Server for C libmqm_r.so
IA64 (IPF) Non-threaded Client for C libmqic_r.so

  1. If you are writing an installable service (see the WebSphere MQ System Administration Guide for further information), we need to link to the libmqmzf.sl library.

  2. If you are producing an application for external coordination by an XA-compliant transaction manager such as IBM TXSeries Encina, or BEA Tuxedo, we need to link to the libmqmxa.sl (or libmqmxa64.sl if your transaction manager treats the 'long' type as 64-bit) and libmqz.sl libraries in a non-threaded application and to the libmqmxa_r.sl (or libmqmxa64_r.sl) and libmqz_r.sl libraries in a threaded application.

  3. You must link WebSphere MQ libraries before any other product libraries.

 

Parent topic:

Preparing C programs


fg16300_