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.

MFS tailoring

MFS formats for 3270 Model 2 devices and symbolic device types of 3270-A2, 3270-A3, 3270-A4, and 3270-A7 are supplied with File-AID for IMS/DC. The following screen sizes are assumed for these symbolic devices.

Device

Screen Size

3270-A2

24 x 80

3270-A3

32 x 80

3270-A4

43 x 80

3270-A7 *

27 x 132


Important

* Display will be 24 x 80

If your installation has defined these symbolic device types differently, you must change the TYPE= operand on the DEV macro in the MFS source code. If you are not sure how your installation has defined the symbolic device types, the MFS Service Utility can produce a report that lists the device characteristics table.

If your installation does not have all the previously mentioned symbolic devices defined to IMS, you must modify the MFS source code before it is assembled. Either comment out or delete the DIF/DOFs for the symbolic terminal types that are not supported.

If you change the length of the MFS MOD prefix (that is, from IXDO to IXD) in the MFS source code, you must also change the length of the MFS MID prefix to match that of the MOD prefix (that is, from IXDI to IXI) in the MFS source code.

 

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