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.

Application Relationship (AR)

An AR is similar to referential integrity in that references from one table to another are valid. However, the relationships are defined internally within the logic of application programs, rather than externally through Db2. Since application programs are not involved in an Edit session under File-AID for Db2, an external definition is required. You can meet this requirement by defining application relationships through File-AID for Db2’s Option 6, Relationships, or through Option 2, Edit. The relationship you define lets File-AID for Db2 simultaneously access tables with application relationships.

Application Relationship shows an application relationship. Every CUSTNO in the ORDER table must be a CUSTNO in the CUSTOMER table. Every ORDERNO in the PARTS table must be a ORDERNO in the ORDER table.

You define the relationship to relate columns from one table to another: The CUSTOMER table is a parent to the ORDER table. The ORDER table is a dependent to the CUSTOMER table, and a parent to the PARTS table. The PARTS table is a dependent to the ORDER table and a descendant to the CUSTOMER.

Application Relationship

image2021-3-10_14-4-10.png

Unlike referential integrity, an application relationship has no external control to enforce the specified relationships. Only the application program can prevent a user from entering a foreign key in a dependent table that does not exist in the parent table. However, once an AR is defined to File-AID for Db2 (see Creating-a-new-relationship), Related Table Edit can provide this control.

Related topics

Referential-Integrity-RI


 

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