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.

Generating CREATE DDL

When DDL has been captured during extract for Db2 objects, File-AID/RDX generates DDL that matches the source objects and puts it in the load JCL (member Db2CREAT in the control card PDSE). This DDL is used to create new target objects during load. When building DDL, File-AID/RDX uses certain information from the extracted tables as follows:

  • Column information is used unaltered. File-AID/RDX does not create Distinct types (UDTs). If the source UDT does not exist in the target system, File-AID/RDX will create the columns using only the UDT’s built-in data type.
  • FIELDPROC and VALIDPROC information is used in the CREATE DDL unaltered.
  • Primary key information is used unaltered. File-AID/RDX generates an index that reflects the primary key.
  • The table name is modified to reflect the table name specified on the Target Environment screen.
  • The IN statement is modified to reflect the database and tablespace specified on the Target Environment screen.
  • EDITPROC and OBID statements are not used to build the CREATE DDL.

File-AID/RDX saves foreign key information from extracted tables and adds it to new tables using ALTER statements after the new tables have been created.

For all indexes for all tables in the extract file, File-AID/RDX uses certain information as follows:

  • The index creator name is modified to match the table creator name specified on the Target Environment screen.
  • Column and cluster information is used unaltered.
  • Partition information is used if the tablespace associated with the new table is partitioned. Otherwise, partition information is ignored.
  • The ON statement is modified to reflect the table name specified on the Target Environment screen.
  • USING information is used unaltered.
  • USING information is not used to build the CREATE DDL.

After File-AID/RDX successfully creates all the tables and indexes, it executes ALTER statements to add referential constraints. Constraints are added only to tables that are part of the load. Constraints added to tables within the load are used unaltered.

 

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