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.

Referential Integrity (RI)

An RI relationship is one in which the dependent table rows contain a foreign key, the value of which is the primary key of the parent table. Referential Integrity shows an RI relationship. The value of every WORKDEPT in the EMP table must appear as a DEPTNO in the DEPT table. The value of every RESPEMP in the PROJ table must appear as a EMPNO in the EMP table. The rules that define RI relationships are enforced by Db2. The following definitions help to explain it in more detail:

  • Primary Key: The column or set of columns that provide the unique identifiers of the rows.
  • Foreign Key: A column or set of columns that refer to a primary key. Establishing a foreign key defines a relationship between two tables.
  • Referential Constraint: The rule that a value of a foreign key must appear as a value of the primary key of some specific table.
  • Parent Table: The table referenced in a referential constraint that contains the primary key.
  • Dependent Table: The table referenced in a referential constraint that containing the foreign key.
  • Descendant Table: A dependent of a dependent table.
  • Referential Integrity: The enforcement of all referential constraints.

Referential Integrity

image2021-3-10_14-3-11.png

 

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