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.

Check Extract Warning panel

When the CHECK extract path routine (see primary command CHECK (CHE)) finds a possibly problematic path, File-AID/RDX displays the Check Extract Warning.

Review the findings and use the Accept and Ignore primary and line commands to ACCEPT or IGNORE the suggestions.

Important

Once the problematic relationship(s) have been ignored or accepted, and you exited this window, File-AID/RDX retains your choices and you must enter the CHECK primary command to change the resulting status.

Check Extract Warning

File-AID/RDX ------------  Check Extract Warning  ------------ Row 1 to 1 of 1  
Command ===>                                              Scroll ===> PAGE      
                                                                                
Primary Commands: Accept, Ignore, VIew                     (END = Ignore)      
   Line Commands: A = Accept path   I = Ignore path                           
Driving Object: FRSAMP.ORDER_TABLE                                             
          SSID: DSN   Location: DSNLOCAT                                       
  Object Name                                    Status                        
  ---------------------------------------------- -------------------------      
_ FRSAMP.CUSTOMER_TABLE                          Excl User                     
    FRSAMP.ORDER_TABLE                           Parent path required           
******************************* Bottom of data ******************************** 

Object Name (Parent)

Displays the codename of the object defined as the parent in a relationship in the upper row (the row with the line command input field).

Object Name (Dependent)

Displays the name of the object defined as the dependent in a relationship in the lower row, under its parent.

Status

Displays one of the navigation status messages as described on here.

The lower, second Status row for each relationship displays the check extract path status:

Message

Explanation

Parent path required

This relationship is required to ensure that extracted dependent records maintain relational integrity. If ignored, extracted orphan records might not be loadable without their corresponding parent records.

Parent path required - Excl Miss

Because the excluded object is missing you cannot include it with the ACCEPT line or primary command.

Relational error ignored

You marked this relationship with the IGNORE line or primary command and it will remain excluded for the extract.

Primary Commands

The following File-AID/RDX-specific primary commands are valid on this screen:

ACCEPT (A)

Accept all suggested relationships to be included in the extract. When you press Enter, you return to the previous Extract Scope Detailed View screen where you entered the CHECK command or the Extract Scope screen when you exited the “Extract Scope Detailed View” screens.

IGNORE (I)

Ignore all suggested relationships, they will not be included in the extract and their status changes to “Relational error ignored”. You can still use the Accept Path line command to change the status individually or enter the ACCEPT primary command.

VIEW (VI)

The VIEW command allows you to easily switch between the object and relationship views. SAMPLE, STATUS and NAVIGATION can be used to go directly to the corresponding format of the relationship view.

Line Commands

The following File-AID/RDX-specific line commands are valid on this screen:

A (Accept Path)

Accept an individual relationship to be included in the extract.

I (Ignore Path)

Ignore an individual relationship, it will not be included in the extract and its status changes to “Relational error ignored”. You can still use the Accept Path line command to change the status individually or enter the ACCEPT primary command.

 

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