Writer instructions

Purpose

Use this page to display a banner announcement on each page of the space. Create the Space announcements page in the master space, outside of the Home branch.

You can version the Space announcements page to enable different banners to be published into different target spaces, however, the banner that is displayed in the versioned (master) space itself only displays the most recently-published banner.  If you find errors in the banner area of your versioned space and you are sure the Space announcements page is set up correctly, try publishing the page to the same space.

For more information, see Space-announcements-banners.

Removing

When an announcement is no longer needed, remove the BMC Space Banner macro.

Translation

Localized spaces using the L10n Viewport theme must change the name of this page to Space announcements l10n.  See Configuring-the-Scroll-ViewPort-theme-for-translated-spaces.

Usage

Choose one or none of the following BMC Space Banner macros.

If your space requires another kind of announcement, you can use this page in coordination with your team lead and editors.

When should I use a space announcement banner?

Use the space organization announcement after you change the content from a book-like organization (such as User Manual, Configuration Manual, and Administration Guide) to the product model.

Use the latest version announcement to push traffic to later versions. You do not need to add this to every previous version, but if you have a specific reason that you want users to be aware—for example, Google searches show content for an obsolete version—use the banner to help users find a relevant version.

When an announcement is no longer needed, remove the BMC Space Banner macro.

Space announcement This documentation space provides the same content as before, but the organization of the content has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

IMS message queues

Because IMS does not allow an MFS output message to span logical records, the system large message queue record length must be long enough to contain the messages produced by File-AID for IMS/DC and the system prefix. The following table outlines these requirements.

IMS Large Message Queue Requirements

Screen Size

Message Length

LGMSG Queue Size Required*

24 x 80

1764

1852

32 x 80

2404

2492

43 x 80

3353

3441

Important

Add 48 bytes if MSC is installed.

Large message queue sizes that are less than these will cause unpredictable results. The large message queue size at your installation can be verified with the IMS command /DISPLAY POOL QBUF. If the queue is not large enough, the value on the IMS system macro MSGQUEUE must be increased. Refer to IMS/ESA Installation Guide for more information.

 

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