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.

SQL Analysis Summary

The SQL Analysis Summary screen provides a quick reference of your SQL statements and enables you to easily identify the SQL you want to analyze. It displays the Db2 cost threshold, enabling you to identify SQL requiring performance improvements. It also displays the processing service units, thereby minimizing the need to print the Cost Detail Report. (The Cost Detail Report, requested as part of Explain Detail, has many output lines.) From this screen, you can select a DBRM/Package for more analysis.

The screen displays when you request an online explain by entering the X line command on the screens listed below. It is not displayed if there is only one SQL statement.

SQL Plan Selection screen (SQL Plan Selection).
DBRM Selection screen (DBRM Selection Screen).
Collection ID Selection screen (Collection ID Selection Screen).
Package Selection screen (Package Selection Screen).
DBRM/Package Selection screen (DBRM/Package Selection Screen).

This screen is also displayed when you request an online report from the SQL Explain Report Specification screen (SQL Explain Report Specification Screen).

Important

In the event that File-AID for Db2 detects a syntax error, the original unmodified SQL statement is passed to Db2 for an explain. No literal substitution or object qualification is done in this case. This can cause different explain results.

SQL Analysis Summary

CMD

Enter S to select a SQL statement for more analysis. The Plan Table Analysis screen (Plan Table Analysis Screen) displays.

DBRM/Package

Name of the DBRM/Package for the plan.

Statement

Statement number within the plan or package.

Type

Type of SQL statement.

DB2 Cost

If the cost exceeds the threshold for the plan, an asterisk (*) displays next to this field. The value of the DB2 cost threshold is determined at the time File-AID for Db2 is installed.

PROCSU

The estimated processor cost, in service units, for the SQL statement. The estimate is rounded up to the next integer value. If a DSN_STATEMENT_TABLE is not defined, then the PROCSU field displays N/A.

The maximum value for this cost is 2147483647 service units. If the estimated value exceeds this maximum, then the maximum value is reported.

Access Type

Access type.

Sorting DBRM/Package Entries

The SORT primary command can be used to change the order in which the DBRM/Package entries are displayed. Multiple column names are not accepted. The selected columns are sorted in ascending sequence. The valid column names that can be used with the SORT command are listed below. Abbreviations are noted within parentheses.

DBRM/Package (DBRM)
Statement (ST)
Type (TYPE)
DB2 Cost (COST)
Access Type (AC)
PROCSU (PR)

For example, to sort the display by statement, enter the command SORT ST.