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.

Processing options

The following figure is displayed when you select Option 5 from the Load Menu.

Processing Options

 File-AID/RDX ---------------- Processing Options ------------------------------
 Command ===>                                                                   
                                                                               
 Extract File:    TSOID01.FRSAMP.EXTRACT                                      
 Objects to Load: DB2 only                                                        
 DB2 Load Method: SQL Insert                                                   
                                                                              
                                                                            
 Specify DB2 Load Utility Options:                                              
   Log Option              ===> 4          (1 = Log;    2 = Image Copy;        
                                            3 = Repair; 4 = Inline Image Copy)  
                                                                               
                                                                            
 When DB2 SQL Insert and/or loading MVS objects,                                
 Specify Discard Processing Options:                                            
   Save Discarded Rows     ===> N          (Y = YES; N = NO)                    
   Maximum Rows to Discard ===> *          (* for no maximum)                  
   File for Discarded Rows ===>                                                 
                                                                             
                                                                               
 Specify DB2 SQL Insert Commit Interval:                                        
   Commit Every Nth Row    ===> 300        (1-2002) 

Use this screen to specify processing options for MVS files and Db2 tables to be loaded with the SQL insert or Db2 load utility option.

When the load option is Db2, use this screen to specify whether or not you want Db2 logging in effect during the load of the Db2 objects and whether or not existing data should be deleted before Db2 tables and/or MVS file are loaded.

The upper part of this screen displays the following fields:

Extract File

Displays the name of the file from which data will be loaded.

Objects to Load

Displays whether the load includes Db2 only, or MVS only, or both Db2 and MVS objects.

DB2 Load Method

Displays which load method you selected in the Load Object Specifications screen either SQL INSERT or IBM Db2 Batch Load Utility.

Specify DB2 Load Utility Options

This section provides information about the following fields:

Log Option

Specify which log option to use during the execution of the Db2 LOAD utility for the Db2 objects.

1

Log Db2 logging will occur during the load process.

2

Image Copy Db2 logging of data will not occur during the load process. Db2 sets a COPY PENDING restriction against the tablespace being loaded. An IMAGECOPY step is generated to remove the COPY PENDING status.

3

Repair Db2 logging of data will not occur during the load process. Db2 sets a COPY PENDING restriction against the tablespace being loaded. A REPAIR step is generated to set NOCOPYPEND for the tablespace(s). To execute this utility, the privilege set of the process must include one of the following:



      • REPAIR privilege for the database
      • DBADM or DBCTRL authority for the database
      • SYSCTRL or SYSADM authority.

4

Inline Image Copy When “Delete All” is also set to ‘YES’ this option will invoke inline image copy. Db2 logging of data will not occur during the load process. The tablespace into which the data is being loaded will not be placed into a copy pending state.

If there are multiple tables in a tablespace then inline image copy is not used; instead an IMAGECOPY step is generated to remove the COPY PENDING status.

Specify Discard Processing Options

Discard processing is available when the load includes MVS objects or Db2 objects with Load Method Db2 SQL Insert.

Maximum Rows to Discard

Specify the maximum number of errors encountered before processing stops. Specify an asterisk (*) for no maximum or a value greater than 0. Specify 1 if you want processing to stop if any errors are encountered. Specify YES in the Save Discarded Rows field to save these rows for future use. The discard file need not exist to specify a value in this field.

Save Discarded Rows

Specify whether or not to save rows, or records, that could not be inserted or updated.

Yes

Save rows that cannot be inserted or updated in the discard file.

No

Do not save rows that cannot be inserted or updated.

File for Discarded Rows

Specify the name of the file to which discarded rows will be saved. The discard file must be sequential. If you specify YES in the Save Discarded Rows field and specify a file that does not exist, File-AID/RDX will display the Create New File screen.

The discard file can be used as input to the load process if a previous load job was completed normally, but rows were discarded. See SQL INSERT Load JCL.

Specify SQL Insert Processing Options

This section provides information about the following field:

Commit Every Nth Row

Specify the number of rows File-AID/RDX should insert or update before it performs a Db2 COMMIT. This value must be less than or equal to the value specified for the Max Commit Interval installation parameter.

 

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