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.

BIND (BIND Subcommand) - Row commands


The BIND row command generates a command statement for the BIND DSN subcommand. This command is valid for packages and plans.

The DSN subcommand BIND builds an application plan, which allocates Db2 resources and supports SQL requests made during execution. BIND can also be executed using the following methods:

When BIND executes, a parameter window opens (BIND Statement Generation Options for Plans and BIND Statement Generation Options for Packages. In the Edit Plan Parms window, a small inner window indicates if the plan has associated DBRMs, package lists, or plan systems. To create a DBRM, package list, or plan system, use one of these primary commands to request an additional parameter window:

  • DBRM primary command: Displays the DBRM data sets and DBRM member windows.
  • PKL primary command: Displays the Package List window.
  • PLS primary command: Displays the Plan Systems List window.

In the Edit Package Parms window, a small inner window indicates if the package has associated package systems. To create a package by copying another package or a package system, use one of these primary commands to request an additional parameter window:

  • PKCOPY primary command: Displays the Edit Package Copy Parms window.
  • PKS primary command: Displays Edit Package System Parms window.

Also in the Edit Package Bind Parms window, you can make global changes to the bind location. The PKLOC primary command opens the Edit Location Entries window, where you can enter changes.

To generate the BIND statements, put the cursor in the outermost window and press <Go>. The DSN subcommand statements generated by this command are placed in the DSN subcommand work buffer. See Generating DSN Subcommands.

BIND Statement Generation Options for Plans

image2021-5-6_17-16-31.png

BIND Statement Generation Options for Packages

image2021-5-6_17-18-32.png

 

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