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.

Temporary file defaults

The Temporary File Defaults screen shown in the following figure is displayed when you select Option 6 from the RDX Profile Screen. Use this screen to specify the default values for Temporary File-AID/RDX files when using the current profile. File-AID/RDX uses temporary files during extract, load, delete, and disguise processing.

Important

When running an Extract or Load from Topaz, nine additional temporary files are allocated: a PDSE and 8 sequential files. All nine files will be allocated using the same SMS storage and management classes, if specified.

The format of a temporary file name with prefix and suffix is:

7 character user ID:

userid.prefix.XXXXXXXX.Dnnnnnn.Tnnnnnn.suffix

where the 3rd level data set name qualifier XXXXXXXX is a constant indicating the type of the temporary file, for example, SPLIT001 or CKSRTOUT.

8 character user ID1:

userid.prefix.XXXXXXX.Dnnnnnn.Tnnnnnn.suffix

Important

1: Only if 8 character TSO user ID has been implemented at your site with z/OS 2.3 or later.

where the 3rd level data set name qualifier XXXXXXX is a constant indicating the type of the temporary file, for example, SPLT001 or CKSROUT.

Important

Only when an 8 character TSO user ID is used, any 8 character long 3rd level data set name qualifier for dynamically generated or dynamically allocated data sets will change for these cases (DDNAMEs are unaffected):

  1. Data disguise with a File-AID XREF data set: The 3rd qualifier changes from S001B001 to S001001.
  2. Extract chase key processing: The SORTOUT data set 3rd qualifier changes from CKSRTOUT to CKSROUT. For chase key files to be sorted, the 3rd qualifier changes from R000001P to R00001P.
  3. Loading XML columns to a Db2 table: The work data set 3rd qualifier changes from XMLFR001 to XMFR001

Temporary File Defaults Screen

 File-AID/RDX ------------  Temporary File Defaults  ---------------------------
 COMMAND ===>                                            SITE Profile: RDXMENU
                                                                    More:    +
 ------------------------ Temporary File Defaults ------------------------------
 Temporary file allocations:
  UNIT                           ===> SYSDA                
  Storage Class                  ===>    
  Management Class               ===>     

  File Prefix                    ===> RDX                               
  File Suffix                    ===>                                

 Sort Work File Allocation:                                       
  Space Units                    ===> CYL     (BLK, TRK, or CYL)  
  Primary Quantity               ===> 6                           
  Secondary Quantity             ===> 1                           
  Number of Sort Work files      ===> 3       (3 - 6)             
  Use ICETOOL for Batch Sorts    ===> N       (Y = Yes; N = No)
                                                                 
 Temp Work File Allocation:                                       
  Space Units                    ===> CYL     (BLK, TRK, or CYL)  
  Primary Quantity               ===> 1                           
  Secondary Quantity             ===> 1                           
                                                                 
 Chase Key File Allocation:                                       
  Space Units                    ===> CYL     (BLK, TRK, or CYL)  
  Primary Quantity               ===> 1                           
  Secondary Quantity             ===> 1 

Temporary file allocations Area

UNIT

Specify the default unit for the temporary files. File-AID/RDX will verify that the unit specified is a valid generic unit (for example, SYSDA) on the LPAR where you are currently logged on.

Storage Class

Specify the default storage class for the temporary files.

Management Class

Specify the default management class for the temporary files.

File Prefix

Specify the default file prefix for all temporary files for this profile. This is the prefix used for files that must be allocated for batch functions. File-AID/RDX will prefix temporary files with userid.prefix. To prefix a file without a userid, place one double quote as the first character of the pattern. For example, “RDX will prefix a temporary file with RDX. only. If the resulting file name exceeds 44 characters, the specified prefix will be truncated to fit the maximum name length.

Entering the string &USERID will substitute the current userid at the time a temporary file is allocated. For example, “RDX.&USERID will generate temporary files beginning with RDX, followed by the current userid, followed by the rest of the generated data set name.

File Suffix

Specify a file suffix for all temporary files for this profile, if one is desired. This is the suffix used for files that must be allocated for batch functions. File-AID/RDX will append this suffix to the names of generated file names for batch jobs.

Important

The combined length of the file prefix and suffix cannot exceed 19 characters.

Sort Work, Temp Work and Chase Key File Allocation Areas

You can specify different default file allocation values for each of the Sort Work, Temp Work and Chase Key files.

Number of Sort Work files

Specify the default number of sort work files (3 or 6) to be used with this profile.

Use ICETOOL for Batch Sorts

Specify whether Load JCL should be generated to use the ICETOOL utility for sorting. If set to Yes, generate JCL for ICETOOL. If set to No, generate JCL for SORT.

Space Units

Specify whether space for the new file will be allocated in blocks (BLK), tracks (TRK), or cylinders (CYL).

Primary QTY

Specify the initial number of space units that will be allocated for the new file.

Secondary QTY

Specify the number of space units that will be allocated for each secondary extent.

Important

If your extract exceeds the size of these temporary file allocations (B37 abend) change the allocation parameters here and repeat the extract (see Extract).

File-AID/RDX will dynamically reallocate temporary work files, key tree and chase key files only when running extracts using 64 bit memory (above the bar) processing support.

 

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