Skip to Content

Writer instructions

Page title

For most spaces, this page must be titled Space announcements.

For spaces with localized content, this page must be titled Space announcements l10n.

Purpose

Provide an announcement banner on every page of your space.

Location

Move this page outside of your home branch.

Guidelines

Information
Limited support BMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see MainView Middleware Monitor 9.2.

Message Body MQRFH2 Buffer

(Optional) The message format is the MQRFH2 portion of the message. This format must be a top-level field (not a sub-field). While technically part of the message body, considers the RFH2 header separately from the message.

The MQRFH2 header contains information about the structure of a message, and its intended consumers. This enables a message broker to process the message and deliver or publish the message to those consumers.

Message formats using different message buffer types (MQMD, MQDLH, MQRFH2, MQXQH, MQIIH, Body, etc.) can reside in separate message formats and do not need to be combined. This allows common usage across activities for messages sent or received by a regular application, channel or end up on the dead letter queue as the header and content is placed into separate buffers for access via common definition.

The table in Common parameters lists the parameters the RFH2 Buffer type shares with other types.

Warning

Note

To extract information from an RF2H field, use XPath subfields.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

MainView Middleware Monitor 9.0