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 SVC

File-AID products with an SMF audit trail option require the File-AID SVC. If you do intend to use any of these options that require the File-AID SVC, then you need to install the SVC, and there may be authorized library requirements. Setting up the SVC for use does not automatically cause SMF records to be written. Refer to the individual product sections regarding the creation of SMF records.

Important

Install File-AID SVC using the File-AID Common Components PARMLIB member (see SVC-information). A File-AID SVC generated by a release prior to Release 10.01.00 is not compatible with File-AID Release 21.01.00. It must be replaced with an SVC generated with the current File-AID Release. The new File-AID SVC is compatible with all current and prior releases of File-AID for IMS, File-AID/Data Solutions, and File-AID/MVS. Releases of File-AID for Db2 prior to Release 10.01.00 cannot use an SVC generated by File-AID Release 21.01.00.

File-AID supplies two variations of the SVC:

  • One contains validation code that, among other things, checks that the module that issued the SVC came from an authorized File-AID library.
  • The other variation does not make this check.

Related topics

BMC Compuware File-AID/MVS
BMC Compuware File-AID/Data Solutions
BMC Compuware File-AID for Db2
BMC Compuware File-AID for IMS

Task-5-Finalizing-the-configuration

File-AID-Common-Components

Task 1.3 Link Edit File-AID SVC/ESR

If your File-AID products use the SMF Audit option and don’t already have a File-AID SVC created with File-AID Release 10.2 or later, perform this task, otherwise skip this task.

Important

Roles involved for this task:

  • File-AID Installer

File-AID SVC is required when writing audit trail records to SMF. This SMF Audit option is available for File-AID/MVS, File-AID/Data Solutions, File-AID for Db2, and File-AID for IMS.

If you specified SVC usage SVC_USAGE=SVC or SVC_USAGE=ESR in the File-AID Common Components PARMLIB member you must have a File-AID SVC.

Sample library hlq.SXVJSAMP includes the following sample JCL members:

  • LNKESRAU - sample JCL used to link edit ESR as authorized.
  • LNKESRNA - sample JCL used to link edit ESR as non-authorized.
  • LNKSVCAU - sample JCL used to link edit SVC as authorized.
  • LNKSVCNA - sample JCL used to link edit SVC as non-authorized.
  1. Follow the instructions in the appropriate members.
  2. Submit the appropriate job(s).

Additional File-AID SVC Considerations

If the File-AID SVC is installed as a user SVC (IGC00nnn), the MVS SVC table (IEASVC00 in SYS1.PARMLIB) must be updated to include the new SVC number. For example:

   SVCPARM 253,REPLACE,TYPE(3)   /* FILEAID SVC */

After link-editing the File-AID SVC module, copy the module (IGC00nnn) from hlq.CXVJLOAD into SYS1.LPALIB. Then perform an IPL (with a CLPA) or use the SETPROG command to make the SVC available.

 

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