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.

Load function

This section describes Option 3, Load. The Load option is used to load data from the File-AID/RDX extract DASD or tape file into multiple related objects. The objects can be MVS files and/or Db2 tables. The Load option consists of an interactive phase and an execution phase.

Important

Before you can load an extract file on tape you must specify an extract summary file, previously known as an extract tape control file (see Extract File Specification in section Request-File-Member-List-panel-in-the-Load-function).

The interactive phase takes place online and consists of a File-AID/RDX Load menu that allows you to provide information about the following:

  • The DASD or tape file from which to load data.
  • The target objects.
  • Db2 LOAD or SQL Insert processing options.

Using this information, File-AID/RDX builds a series of steps to be performed during the execution phase. You can then edit and save the load JCL created by File-AID/RDX before you submit it. Your installation may also permit interactive (online) execution of the load.

In addition, you can create a single request member combining extract and load specifications. For more information about combining extract and load specifications, see Extract and  Checkpoint/Resumption.

During the execution phase, you can load data into objects that contain data or load it into empty objects. When loading into Db2 objects you have the choice of using either IBM’s Db2 LOAD utility or SQL INSERT processing.

Target objects that do not exist can be created automatically as long as their create information was obtained during the extract.

You can delete all existing data before loading, replace existing rows with records from the extract file, or leave existing rows intact, only adding rows to the object. You can perform column-to-column mapping to insert or load data to objects that are defined differently from the extracted objects.

File-AID/RDX verifies user authority before performing certain operations. For more information, see Db2 Privileges.

During load processing, File-AID/RDX uses temporary files. For information about temporary file naming conventions and allocation values, see Temporary File Defaults.

Support for Db2 XML and LOB data type

You can load extracted data from XML and/or LOB columns to target objects using either SQL Insert or Db2 Load options. When loading an extract disguised with DCF (see also Using File-AID/RDX with File-AID/Data Solutions (Using DCF)), be aware that the extracted XML and/or LOB data is not disguised and will be loaded unmasked in its proper format.

Support for Db2 temporal tables

Temporal Table support requires Db2 Version 10 Release 1 or higher. You can load extracted data from Temporal Tables to existing target Temporal Tables using Db2 Load Method only. You can specify whether File-AID/RDX generates the PERIODOVERRIDE clause when loading data to SYSTEM TEMPORAL tables (see Preserve Temporal).

Support for Db2 archive tables

In File-AID/RDX table lists, Archive Table Type ‘R’ is identified as Type ARCHV. You can load extracted data from Archive Tables to existing target Archive Tables using SQL Insert Method (see Db2 Load Method) only.

Important

  • The Load Auto Create feature does not support Archive tables.
  • Using the DB2 Load option with an archive-enabled table is not supported.

GDG considerations

The name displayed for the source object is the absolute generation of the GDS extracted. File-AID/RDX generates relative generation numbers for objects in the target environment, keeping the generations in the same order as they were in the source environment. You may overtype the generated name with a different name. The target object can be a GDS with either a relative or absolute generation or it can be a regular non-GDG data set. Specifying the GDG base without a version is invalid for a Target object.

Important

File-AID/RDX does not support extracting from and loading to tape data sets.

This section provides information about the following topics:

 

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