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.

Load object specifications

The Load Object Specifications screen shown in the following figure is displayed when you select Option 1 from the Load Menu.

Load Object Specifications

 File-AID/RDX  --------------- Load Object Specification ------------------------
 Command ===>                                            

 Specify Target DB2 Environment:                                                 
   SSID                 ===> DSN
   Location             ===> DSNLOCAT    
   DB2 Load Method      ===> DB2      (SQL = SQL Insert Statement;                                        
                                       DB2 = IBM DB2 Batch Load Utility)
   Preserve Temporal    ===> N        Retain original temporal time data?
                                      (Y/N)
 Specify Object Name Modifiers:             (/ entry to apply modification)
   _ DB2 Creator              ===> TSOID01  (Creator for ALL DB2 objects)
   _ DB2 Index name prefix    ===>          
   _ DB2 Index name suffix    ===>       
   _ MVS high level qualifier ===> TSOID01  (HLQ for ALL MVS objects)
   _ MVS file name suffix     ===> NEW      
 
   _ Revert to source names   ===>          (D = DB2 objects;
                                             M = MVS objects;
                                             B= Both)

Use this screen to specify information about the objects (location, subsystem, creator, tables, and index name modifier for Db2 objects, high level qualifier and file name modifier for MVS objects) to which data from the extract file will be loaded. You also specify which load method (Db2 load utility or SQL Insert) to use for the load of Db2 data.

Specify Target DB2 Environment Area

SSID

Specify the name of the Db2 subsystem to which Db2 data will be loaded. If you leave the Location field blank, the tables you specify to be loaded must exist in the Db2 subsystem displayed in this field.

Location

Specify the location of the tables you want to load if they are in a remote Db2 subsystem. The location you enter must be defined in the Db2 system catalog table SYSIBM.LOCATIONS. You must use the SQL Insert Load Option to use the remote location.

Leave this field blank if the tables you want to load reside in the Db2 subsystem displayed in the target SSID field.

DB2 Load Method

Specify whether you want to load Db2 data using SQL INSERT statements or the IBM Db2 Batch Load Utility. See also SQL Insert and Db2 Load Utility Load Options.

SQL

Perform the load using SQL INSERT statements. This option allows you to update rows if they already exist.

DB2

Perform the load using the IBM Db2 Batch Load Utility.

Important

Interactive mode is not allowed with Db2 Load Utility.

Preserve Temporal

Specify whether to generate the PERIODOVERRIDE clause when Db2 loads data to SYSTEM TEMPORAL tables.

Y

For all SYSTEM TEMPORAL tables in this load, preserve the contents of the source base and history table regarding the versioning timestamp columns, ignoring the GENERATE ALWAYS clause.

N

For all SYSTEM TEMPORAL tables in this load, adhere to the GENERATE ALWAYS clause on the versioning timestamp columns, consequently updating those columns as the rows are loaded.

Important

DB2 Load Method (see Db2 Load Method) must be set to Db2 for Temporal Table support.

Specify Object Name Modifiers

The following fields allow you to apply global object name modifiers.

Initially, these modifiers are set as specified in your profile or load request file and have already been applied to the current load request. In order to change to new modifier values, type the new modifier value, then enter the / (slash) in front of the field(s) to select the desired modifier(s). The selected modifiers are applied when you enter the END command, after the Revert to source names option, if also selected.

DB2 Creator

Specify the authorization ID of the owner of the Db2 target tables. The value in this field defaults to the last value used or entered in your current profile. If you enter a value in this target Db2 Creator field, File-AID/RDX globally updates all Db2 Target table entries with this value. To retain the creator ID from the extract file do not select (slash) this field, but slash the Revert to source names option.

Note

The Db2 load utility does NOT support enclosing lowercase creator IDs with quotes.

DB2 Index name prefix

Specify the prefix to be added to the index names in the target environment. Leave blank if you don’t want to specify a prefix.

DB2 Index name suffix

Specify the suffix to be added to the index names in the target environment. Leave blank if you don’t want to specify a suffix.

If an index were named XDEPT1, adding a prefix of T would make the new index name T_XDEPT1, adding a suffix of T would make it XDEPT1_T, adding both prefix and suffix would make it T_XDEPT1_T.

Do not select (slash) the prefix or suffix field but select (slash) the Revert to source names option to preserve the index names as extracted.

MVS high level qualifier

Specify the high level qualifier for the MVS target files. The value in this field defaults to the last value used or entered in your current profile. If you enter a value in this target high level qualifier field, File-AID/RDX globally updates all MVS target file name entries with this value. To retain the high level qualifier as specified in the extract file do not select (slash) this field but slash the Revert to source names option.

MVS file name suffix

Specify the suffix you want to add when creating MVS files in the target environment.

If a file were named FRSAMP.PARTTABL, adding a suffix of TEST would make the new file name FRSAMP.PARTTABL.TEST.

Do not select (slash) the MVS suffix field but slash the Revert to source names option to retain the file name as specified in the extract file.

Important

Remember that the pre- and suffix modifiers are added to the current values, so also select Revert to source names to change previously applied pre- and suffixes. File-AID/RDX will remove the previously applied pre- and suffixes and then add the new ones.

Revert to source names

Specify which object types should have all their target object names reverted to the names as specified in the extract file:

M

(MVS objects only) File-AID/RDX reverts all MVS object names to the source names as specified in the extract file.

D

(Db2 objects only) File-AID/RDX reverts all Db2 object names to the source names as specified in the extract file.

B

(Both Db2 and MVS objects) File-AID/RDX reverts all object names to the source names as specified in the extract file.

When Revert to source names is slashed all object names of the specified object type(s) revert to the extracted (source) names. If any other modifier items are slashed they will be applied after the source revert.

Primary Commands

The following File-AID/RDX-specific primary command is valid on this screen:

SQLID

Enter the SQLID primary command to change or view the Db2 SQLID for the current load session. Each load session starts with the default SQLID as specified in the load profile (see also Default SQLID). In the Set SQLID window, enter the desired SQLID. USER is a valid entry and changes the SQLID to match the current userid. If you blank out the SQLID, it defaults to the SQLID as specified in the load profile.

SQL Insert and DB2 Load Utility Load Options

File-AID/RDX enables you to specify whether the load is performed using SQL INSERT statements or the Db2 Load utility. You can use either method to load data to new tables, empty tables, or tables that contain data. Either method allows you to delete all existing rows or add rows to tables that contain data.

Use SQL Insert when any of the following are true:

  • You want to be able to update existing rows.
  • You have limited Db2 authorities. SQL Insert requires only INSERT, UPDATE, and possibly DELETE privileges.
  • You want to insert data into single table views.
  • You want to insert data into tables at remote locations.
  • Tables must be available for other applications to access when File-AID/RDX is loading data.
  • You want to insert data into tables or views for lowercase creator IDs enclosed with quotes.

Use Db2 LOAD when any of the following are true:

  • You have a large quantity of data to load and require a faster method for loading the data.
  • You want to load to tables in a cyclical relationship.
  • You want to load to TEMPORAL tables.

 

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