The Message Queue Interface overview
Learn about the Message Queue Interface (MQI) components.
The Message Queue Interface consists of the following:- Calls through which programs can access the queue manager and its facilities
- Structures that programs use to pass data to, and get data from, the queue manager
- Elementary data types for passing data to, and getting data from, the queue manager
- Two extra calls through which z/OS batch programs can commit and back out changes.
- Data definition files (sometimes known as copy files, macros, include files, and header files) that define the values of constants supplied with IBM MQ for z/OS.
- Stub programs to link-edit to our applications.
- A suite of sample programs that demonstrate how to use the MQI on the z/OS platform. For further information about these samples, see Use the sample programs for z/OS.
- Data definition files (sometimes known as copy files, macros, include files, and header files) that define the values of constants supplied with IBM MQ for IBM i.
- Three stub programs to link-edit to your ILE C, ILE COBOL, and ILE RPG applications.
- A suite of sample programs that demonstrate how to use the MQI on the IBM i platform.
- Calls through which IBM MQ for Windows and IBM MQ on UNIX and Linux systems programs can commit and back out changes.
- Include files that define the values of constants supplied on these platforms.
- Library files to link our applications.
- A suite of sample programs that demonstrate how to use the MQI on these platforms. For further information about these samples, see Use the sample programs on Multiplatforms.
- Sample source and executable code for bindings to external transaction managers.
- MQI calls
- Sync point calls
- Data conversion, data types, data definitions, and structures
- IBM MQ stub programs and library files
- Parameters common to all the calls
- Specifying buffers
- z/OS batch considerations
- UNIX and Linux signal handling