Building your procedural application on Windows

The Windows systems publications describe how to build executable applications from the programs that you write.

This topic describes the additional tasks, and the changes to the standard tasks, that we must perform when building IBM MQ for Windows applications to run under Windows systems. C, C++, COBOL, and Visual Basic programming languages are supported. For information about preparing your C++ programs, see Use C++.

The tasks that we must perform to create an executable application using IBM MQ for Windows vary with the programming language that your source code is written in. In addition to coding the MQI calls in your source code, we must add the appropriate language statements to include the IBM MQ for Windows include files for the language that we are using. Make yourself familiar with the contents of these files. See IBM MQ data definition files for a full description.

• Building 64-bit applications on Windows
  Both 32-bit and 64-bit applications are supported on IBM MQ for Windows. The IBM MQ executable and library files are supplied in both 32-bit and 64-bit forms, use the appropriate version depending on the application we are working with.
• Preparing C programs in Windows
  Work in your typical Windows environment; IBM MQ for Windows requires nothing special.
• Preparing COBOL programs in Windows
  Use this information to learn to prepare COBOL programs in Windows, and preparing CICS and Transaction Server programs.
• Preparing Visual Basic programs in Windows
  Information to consider when using Microsoft Visual Basic programs on Windows.
• SSPI security exit
  IBM MQ for Windows supplies a security exit for both the IBM MQ MQI client and the IBM MQ server. This is a channel-exit program that provides authentication for IBM MQ channels by using the Security Services Programming Interface (SSPI). The SSPI provides the integrated security facilities of Windows systems.

Parent topic: Building a procedural application