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.

Extract file

This file is the output from the extract process and the input for the Load and Delete process.

The extract file has the following characteristics:

File organization

Sequential (DSORG=PS) or partitioned (DSORG=PO)

Record format

Variable-blocked (RECFM=VB)

Logical record length

Maximum LRECL determined by File-AID/RDX (default = 27994)

Important

  • File-AID/RDX will dynamically reallocate a sequential extract file to adjust to the needed space. Dynamic reallocation is only available for sequential files (DSORG=PS).
  • The maximum data record length (LRECL) that can be extracted into the extract file is 32,748 (max. of 32,756 minus 4 bytes RDX data, minus 4 bytes VB data). File-AID/RDX will issue a message when an object file has a longer LRECL, but allow you to start the extract. However, when a record to be extracted exceeds 32,748, the extract will fail.

For more information, see Extract about how File-AID/RDX uses this file. For more information, see File-AID/RDX Extract File about the structure of this file.

Dynamic Reallocation of Extract File

File-AID/RDX will dynamically reallocate a sequential extract file to adjust to the needed space. Dynamic reallocation is only available for sequential files (DSORG=PS).

When during an extract the allocated space for an extract file is exceeded (X37 abend), File-AID/RDX initiates a reallocation routine (X37 abend recovery) that creates an intermediary file and copies the extracted data into it. Then the routine deletes and redefines the original extract file with increased primary and secondary quantities of the originally allocated space units (BLK, TRK or CYL). File-AID/RDX uses a multiplier to increase the quantities. The data is then copied from the intermediary file into the newly allocated extract file, the intermediary file is deleted and File-AID/RDX continues to add extracted data.

If the extract requires additional space, this routine repeats until the extract file can hold all of the extracted data or the reallocation attempts a second multi-volume allocation. The dynamic reallocation routine can request a multi-volume allocation only once during an extract. Multi-volume allocation is requested when there is no space left on single volume.

Important

When creating the intermediary file, the routine changes the last character of the file name to a letter between J and R, for example, FRSAMP.EXTRACT to FRSAMP.EXTRACK. If these files already exist, File-AID/RDX will not create the intermediary file and the dynamic reallocation will fail.

Related topics

Extract-function

Load-function

Delete-function

 

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