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.

File-AID/RDX Product Configuration


Overview

File-AID/RDX enables programmers and database administrators to easily extract and load a complete subset of related MVS and/or Db2 data. Data related by referential integrity or application-defined relationships can be copied within the MVS and/or Db2 environment with full support for all relational constraints.

File-AID/RDX allows programmers to use a familiar ISPF-like format to create and populate test files and/or Db2 tables that accurately reflect the production relationships, yet contain only a relevant subset of the data—without coding SQL or writing programs. DBAs can migrate related sets of data from one Db2 subsystem to another, confident that all parent/child relationships are properly maintained—without extensive manual procedures.

Configuration Procedures

Sample PARMLIB member FAFR00 in hlq.SXVJSAMP provides the core parameters required for File-AID/RDX and should be used as a skeleton for parameters for your particular installation.

Important

Sample PARMLIB member FAFRALL includes all available parameters. If your site requires non-core parameters, you only need to copy those individual parameters to your site PARMLIB member that require non-default parameter values.

Edit the parameter values to configure File-AID/RDX to your site’s desired settings.

File-AID/RDX Core Parameters (FAFR00)

RDX_SITE_PROFILE_DSN

Description: File-AID/RDX Site Profile. Max. length 44.
Specify the name of the File-AID/RDX Site Profile data set (for example: FR.SITE.PROFILE).
If the Profile data set does not exist, you must allocate one. Modify the sample JCL member XFRPROF in hlq.SXVJSAMP with site appropriate information and submit the job.

Default: FR.SITE.PROFILE

Required: yes

File-AID/RDX Additional Parameters (FAFRALL)

Important

Review the ALL PARMLIB member to see which of the additional parameters require site specific changes. You only need to copy those individual parameters to your site PARMLIB member that require non-default parameter values.

ALLOW_EXTRACT_FROM_DB2_IMAGE_COPY

Description: Allow extract from image copy. Max. length 1.
(Y=Yes,N=No)
Y allows users to extract Db2 data from Db2 Image Copy data sets. Either the Load Libraries (hlq.CXVJLOAD and hlq.SXVJLOAD) must be AUTHORIZED or all of the Load Library modules must be copied into an authorized library.
N disables extract Db2 data from Db2 Image Copy and locks the SITE profile variable Extract from Image Copy to No.

Default: N

 

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