Prepare C programs

 

Work in your usual Windows environment; WebSphere MQ for Windows requires nothing special. For further information on programming 64 bit applications see Coding standards on 64 bit platforms.

• Link your programs with the appropriate libraries provided by WebSphere MQ:

  Library file	Program/exit type
  MQM.LIB	server
  MQIC32.LIB	client for 32-bit C

  The following command gives an example of compiling the sample program amqsget0 (using the Microsoft Visual C++ compiler):

  cl -MD amqsget0.c /Fc amqsget.exe mqm.lib

  1. If you are writing an installable service (see the WebSphere MQ System Administration Guide for further information), we need to link to the MQMZF.LIB 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 MQMXA.LIB or MQMXA64.LIB library.

  3. If you are writing a CICS exit, link to the MQMCICS4.LIB library.

  4. If an application is to make changes to environment variables, such as MQSERVER, link it to the same C run-time libraries as those used by WebSphere MQ. Use the -MD compile switch to accomplish this.

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

• The DLLs must be in the path (PATH) that you have specified.

• If you use lowercase characters whenever possible, we can move from WebSphere MQ for Windows to WebSphere MQ on UNIX systems, where use of lowercase is necessary.

• Preparing CICS and Transaction Server programs
  

 

Parent topic:

Building a WebSphere MQ application

fg16670_