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.

File-AID/MVS exits

File-AID is shipped with sample exits. The sample exits are functionally inert unless you modify them. If you modify the Audit Trail Exit after installation, you need to compile and relink it using the appropriate JCL (see Sample Audit Exits and JCL).

Important

All exits must be compiled and linked with AMODE(31),RMODE(24).

File-AID allows exits written in COBOL, PL/I, and Assembler in compilers that are covered by BMC’s support policy. It is highly recommended that all exits be written in compilers and assemblers that are currently supported by their suppliers.

Security and I/O exits are not automatically linked at installation time. Use the appropriate JCL listed in Sample Security Exits and JCL or Sample I/O Exits and JCL to install these File-AID user exits.

If you intend to use your own I/O, Security, and/or Audit exit with File-AID/Eclipse, make sure they are included in the customized hlq.CXVJLOAD load library.

Important

Exit routines must be assembled or compiled and then link-edited to a library in the system search order (that is, a library searched when the load macro is issued).

This section provides information about the following topics:

 

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