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.

Allocate relationship file

The following figure is displayed when you select Option A, ALLOCATE, from the Db2 Relationship Facilitator or MVS Relationship Facilitator menu.

Use this screen to create a new Relationship file in addition to the one(s) created during the installation of File-AID/RDX.

Allocate Relationship File

 File-AID/RDX -----------  Allocate Relationship File  ---------------------
 Command ===>

 New VSAM Component names:
   Cluster                ===> 'FRSAMP.R44.RELATION'
   Data Component LLQ     ===> DATA                
   Index Component LLQ    ===> INDEX
   Data component . . : 'FRSAMP.R44.RELATION.NEW.DATA'                
   Index component . .: 'FRSAMP.R44.RELATION.NEW.INDEX'               

 Specify SMS Class Information:
   Storage  ===> S           Data  ===>             Management  ===> T

 Space Allocation:   DATA Component  KSDS INDEX Component (Blank for default)
   Volume serial       ===>            ===>   
   Units               ===> TRK        ===>           (TRKs; CYLs; RECs; K; M)
   Primary             ===> 1          ===>           (Amount in above units)
   Secondary           ===> 1          ===>           (Amount in above units)


           When parameters are complete, use END to continue.

Use this screen to allocate the new Relationship file that File-AID/RDX uses as a repository to store the RI and AR relationship definition so you can extract related data.

Press END (PF3) to allocate the SMS file, or use the CANCEL command to cancel the allocation. When allocation is complete, File-AID/RDX displays a message: FILE ALLOCATED in the upper-right corner of the screen.

After allocating a new Relationship file, you can use Option L, Batch RI Load, from the Db2 Relationship Facilitator to load Db2 RI information from a Db2 subsystem (see Batch RI Load).

New VSAM Component Names

Cluster

Specify the name of the VSAM cluster for the Relationship file to be allocated. If you don’t use quotes around the name, File-AID/RDX will add your TSO ID as the prefix.

Data component LLQ

Low level qualifier for the data component. You may overtype this field, if your installation uses a different data component LLQ.

Index component LLQ

Low level qualifier for the index component. You may overtype this field, if your installation uses a different index component LLQ.

Data component

Displays the name of the data component as it will be allocated. It reflects the new cluster name and low level qualifier after you press Enter.

Index component

Displays the name of the index component as it will be allocated. It reflects the new cluster name and low level qualifier after you press Enter.

Important

If a long cluster name results in data and index component names longer than 44 characters, the cluster name portion in front of the component LLQ is truncated.

Specify SMS Class Information

Storage

Specify the SMS storage class to use for the allocation of the file. The storage class describes the hardware requirements of the file.

Data

Specify the SMS data class to use for the allocation of the file. The data class describes the attributes of the file such as RECORG, KEYLEN, KEYOFF, SPACE, etc.

Management

Specify the SMS management class to use for the allocation of the file. The management class describes the migration, backup, and retention for the file.

Space Allocation

Specify the space allocation values for the data and index components. Leave fields blank for defaults.

Volume serial

Specify the volume serial of the direct access device that contains the file.

Space units

Specify one of the following storage unit types depending on how the file size is expressed:

TRK - Tracks
CYL - Cylinders
K - Kilobytes

M - Megabytes
REC - Records

Primary quantity

Specify the primary allocation quantity as specified in the space units field.

Secondary quantity

Specify the secondary allocation quantity as specified in the space units field.

 

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