Preparing C programs

Work in your normal environment; WebSphere MQ for Windows requires nothing special.

• You need to link your programs with the appropriate libraries provided by WebSphere MQ:
  

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

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

  cl amqsget0.c /link mqm.lib
  

  Notes:

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

  2. If you are producing an XA switch load file for external coordination by an XA-compliant transaction manager such as IBM TXSeries, Transarc Encina, or Novell Tuxedo, use the MQRMIXASwitch structure and link to the MQMXA.LIB library.

  3. If you are producing an XA switch load file using the MQRMIXASwitchDynamic structure, link to the Encina MQMENC.LIB library.

  4. To build the Encina sample, link against the following libraries:
     • MQM.LIB
     • MQMENC.LIB

     Also, link against the Encina and DCE libraries:

     • libEncServer.lib
     • libEncina.lib
     • libdce.lib

  5. If you are writing a CICS exit, link to the MQMCICS.LIB library.

  6. If an application is to make changes to environment variables, such as MQSERVER, you must link it to the same C run-time libraries as those used by WebSphere MQ. Use the '-MD' compile switch to accomplish this.
• For DOS only: Your application must also be linked with two of the following libraries, one for each protocol, indicating whether you do or do not require it. If you require TCP/IP you must also link to SOCKETL from the DOS TCP/IP product.
  

  Library file	Protocol
  MQICN.LIB	NetBIOS required
  MQICDN.LIB	NetBIOS not required
  MQICT.LIB	TCP/IP required
  MQICDT.LIB	TCP/IP not required

• You must ensure that you have specified adequate run-time heap and stack sizes. A heap size of 8 KB and stack size of 16 KB are the recommended minimum size.
• The DLLs must be in the path (PATH) you have specified.
• If you use lowercase characters whenever possible, you 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

Sample C source for a CICS WebSphere MQ transaction is provided by AMQSCIC0.CCS. You build it using the standard CICS facilities:

For CICS for Windows NT V2:

1. Add the following lines to the CICSENV.CMD file:

     UserWork = 'c:\mqm\dll'
     UserIncl = 'c:\mqm\tools\c\include;c:\mqm\tools\c\samples'
   

   If necessary replace c:\mqm with the path on which you installed the sample code.

2. Edit the CICSCCL.CMD file (found in <drive>:\CNT200\UTIL) and add the library mqm.lib to the set of libraries.
3. To the LIB environment variable add:

     <drive>:\MQM\TOOLS\LIB
   

4. To the INCLUDE environment variable add:

     <drive>:\MQM\TOOLS\C\INCLUDE
     <drive>:\CNT200\INCLUDE
   

5. Compile using the command:

     CICSCTCL AMQSCIC0
   

   This is described in the CICS for Windows NT V2.0 Application Programming Guide.

For TXSeries for Windows NT, V4:

1. Set the environment variable (enter the following on one line):

     set CICS_IBMC_FLAGS=-IC:\Program Files\IBM\WebSphere MQ\Tools\C\Include;
     %CICS_IBMC_FLAGS%
   

2. Set the USERLIB environment variable:

     set USERLIB=MQM.LIB;%USERLIB%
   

3. Translate, compile, and link the sample program:

     cicstcl -l IBMC amqscic0.ccs
   

This is described in the Transaction Server for Windows NT Application Programming Guide (CICS) V4.

You can find more information about supporting CICS transactions in WebSphere MQ System Administration Guide.