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.

PSB tailoring in File-AID for IMS

All PSBs used by File-AID for IMS must contain four PCBs for the CLT and LTM control databases, as well as PCBs for the user databases. If the Audit Trail feature is going to be activated for any of the user databases accessed through a given PSB, then a fifth PCB must be coded for the AUD control database. In a single transaction configuration there is only one PSB that will contain these PCBs.However, in a multiple transaction configuration, there are usually multiple PSBs, each with PCBs for the control databases and PCBs for a subset of the user databases. Some thought must be given to grouping the user database PCBs into the PSBs. Following are some suggestions:

  1. Provide each programming group with its own PSB, which contains PCBs for the databases that the group uses.
  2. Group each set of application related databases into its own PSB.
  3. Group databases that have strict access security in a PSB separate from databases that have more lenient access.
  4. Group test database PCBs in one PSB, production database PCBs in another.

Important

  • Remember, a separate transaction code must be created for each PSB defined.
  • Each PCB within a PSB requires storage in the IMS PSB pool. In some situations, depending on the number of PCBs in the PSB, the installation limit for the IMS PSB pool size can be exceeded. If this limit is exceeded, you must either split the PSB into smaller PSBs and create a separate transaction for each PSB, or increase the IMS PSB pool size.

Following are some guidelines for creating PSBs:

  1. The first four PCBs in the source code must be exactly as shown in Modify PSBs in Customizing-File-AID-for-IMS-CICS. The fifth PCB is optional for the AUD control database.
  2. The PROCOPT parameter on all user database PCBs should be A and should be specified on the PCB macro and not the SENSEG macro. If you want to enforce security using the PSBs, you can specify a PROCOPT parameter of G, GO, or GOT on the user databases. This action causes File-AID for IMS to display an abend screen with an AM status code and then the Primary Option Menu screen whenever one of these user databases is edited.
  3. To exclude a segment from processing by File-AID for IMS, simply leave the segment out of the PCB. The excluded segment is not displayed nor updated.
  4. Do not code more than one PCB per database within a single PSB. File-AID for IMS cannot differentiate between them.

Related topics

BMC Compuware File-AID for IMS

 

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