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.

Db2 delete job steps

This section describes the steps in the Db2 delete job.

  1. CLEAN1ST—File Cleanup (IDCAMS)This step ensures that all temporary files used in this job are deleted. This enables you to keep and rerun a JCL stream.
  2. DLDRV—Delete Driver (XFREXEC)This step ensures that the tables from which data is to be deleted exist. In addition, this step checks user authorization for subsequent steps and separates the extract file into multiple files, one file per table to be deleted.

  3. DELETE—Delete Rows (XFREXEC)This step deletes data from the tables listed on the Delete Confirmation screen.

    The DELETE step uses Db2 SQL with all the data that was extracted included in the WHERE clause. File-AID/RDX deletes rows based on exact matches instead of index values.

    File-AID/RDX determines the order in which to delete rows such that rows from dependent tables are deleted first. Then, rows from parent tables are deleted. This continues until all rows are either deleted or discarded.

  4. CLEANLST—File Cleanup (IDCAMS)This step deletes all File-AID/RDX temporary files used in this job. Deleting these files in the last job step enables the job to be restarted in any prior step.

  5. CLEANCTL—File Cleanup (IEFBR14) - OptionalThis step deletes the File-AID/RDX control card PDSEs. Whether step CLEANCTL is commented out or executed is determined by the global job option Delete in-stream data datasets at EOJ. If the job option is set to NO, File-AID/RDX control card PDSEs created in the load and delete jobs will NOT be deleted. Keeping the data sets until all steps run successfully allows for the restarting of the JCL at any step.

  6. CLEANEXT—File Cleanup (IDCAMS) - Optional

This step deletes the File-AID/RDX EXTPARMS parameter file. Whether step CLEANEXT is commented out or executed is determined by the global job option Delete in-stream data datasets at EOJ. If the job option is set to NO, File-AID/RDX EXTPARMS files created in the load and delete jobs will NOT be deleted. Keeping the data sets until all steps run successfully allows for the restarting of the JCL at any step.

 

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