Properties specified as MQRFH2 elements

Non-message descriptor properties can be specified as elements in MQRFH2 header folders. Overview of MQRFH2 elements being specified as properties.

This retains compatibility with the previous versions of the IBM MQ JMS and XMS clients. This section describes how to specify properties in MQRFH2 headers.

To use MQRFH2 elements as properties, specify the elements as described in Use IBM MQ classes for Java . This information supplements the information described in MQRFH2 - Rules and formatting header 2.

• Mapping property data types to MQRFH2 data types
  This topic provides information on message property types mapped to their corresponding MQRFH2 data types.
• Supported MQRFH2 folders
  Overview of the use of message descriptor fields as properties.
• Generation of MQRFH2 headers
  If IBM MQ converts message properties to their MQRFH2 representation, it must add the MQRFH2 to the message. It adds the MQRFH2 either as a separate header, or merges it with an existing header.
• MQRFH2 folder restrictions
  Overview of folder restrictions in MQRFH2 headers
• MQRFH2 element name conflicts
  Overview of conflicts within MQRFH2 element names.
• Mapping from property names to MQRFH2 folder and element names
  Overview of the differences between property names and element names in the MQRFH2 header.
• Mapping property descriptor fields into MQRFH2 headers
  When a property is translated into an MQRFH2 element the following element attributes are used to specify the significant fields of the property descriptor: This describes how MQPD fields are translated to MQRFH2 element attributes.
• MQRFH2 headers that are not valid
  At the time an MQPUT, MQPUT1, or MQGET call processes, a partial parsing of any MQRFH2 headers in the message can occur to check what folders are included, and to determine if the folders contain properties. Overview of MQRFH2 headers that are not valid.

Parent topic: MQI applications reference