Introducing the Message Queue Interface
This chapter introduces the features of the Message Queue Interface (MQI).
The remaining chapters in this part of the book describe how to use these features. Detailed descriptions of the calls, structures, data types, return codes, and constants are given in the Application Programming Reference.
The MQI is introduced under these headings:
- What is in the MQI?
- Parameters common to all the calls
- Specifying buffers
- Programming language considerations
- z/OS batch considerations
- UNIX signal handling
Note
The Application Messaging Interface (AMI) provides a simpler and higher-level programming interface than the MQI. Although it has some limitations compared with the MQI, its function should be sufficient for the majority of users. The AMI supports both point-to-point and publish/subscribe messaging models, and includes support for both WebSphere MQ Integrator V1 and WebSphere MQ Integrator V2. The AMI eliminates the need for application programmers to understand all the options and functions available in the MQI. The Application Messaging Interface for C, C++, and Java™ runs on the following operating systems or environments: i5/OS, AIX, HP-UX, Solaris, Windows, and z/OS™. The Application Messaging Interface for COBOL runs on the z/OS operating system. Further information about the AMI is outside the scope of this book. For full details, refer to WebSphere MQ Programmable Command Formats and Administration Interface.
- What is in the MQI?
- Parameters common to all the calls
- Specifying buffers
- Programming language considerations
- z/OS batch considerations
- UNIX signal handling
Parent topic:
Writing a WebSphere MQ application
fg11380_