Overview for MQIIH

The MQIIH structure describes the header information for a message sent to IMS across the IMS bridge. For any IBM MQ supported platform we can create and transmit a message that includes the MQIIH structure, but only an IBM MQ for z/OS queue manager can use the IMS bridge. Therefore, for the message to get to IMS from a non-z/OS queue manager, your queue manager network must include at least one z/OS queue manager through which the message can be routed.

Availability: All IBM MQ systems and IBM MQ clients.

Purpose: The MQIIH structure describes the information that must be present at the start of a message sent to the IMS bridge through IBM MQ for z/OS.

Format name: MQFMT_IMS.

• Applications that connect to the queue manager that owns the IMS bridge queue must provide an MQIIH structure that is in the character set and encoding of the queue manager. This is because data conversion of the MQIIH structure is not performed in this case.
• Applications that connect to other queue managers can provide an MQIIH structure that is in any of the supported character sets and encodings; the receiving message channel agent connected to the queue manager that owns the IMS bridge queue converts the MQIIH.
• The application message data following the MQIIH structure must be in the same character set and encoding as the MQIIH structure. Do not use the CodedCharSetId and Encoding fields in the MQIIH structure to specify the character set and encoding of the application message data.

  We must provide a data-conversion exit to convert the application message data if the data is not one of the built-in formats supported by the queue manager.

Parent topic: MQIIH - IMS information header