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

Limited supportBMC 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.

WebSphere MQ return codes

Not every application regards the WebSphere MQ warnings as warnings. Therefore, MainView Middleware Monitor does not include them by default. When you create your activity implementation, you can add additional return codes.

If MainView Middleware Monitor receives a return code that is not defined in the list or is not valid, MainView Middleware Monitor returns its own error telling you that the return code it just received is unknown. To read the return code of a transaction, click the status cell of that transaction. Unknown return codes are treated as failures.

Note

If your WebSphere MQ application accepts truncated messages, set MQRC_TRUNCATED_MSG_ACCEPTED (2079) and MQRC_TRUNCATED_MSG_FAILED (2080) as successful return codes. If your WebSphere MQ does not accept truncated messages, set those return codes as failures. Other MQRC reason codes can be added as success or failure, depending on your needs.

 

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